Chapter 1 Overview of System Commissioning ...........................................

1-1
1.1 Explanation of System Commissioning .................................................. 1-1
1.2 Flow of System Commissioning ............................................................. 1-1
Chapter 2 Preparations for System Commissioning.................................... 2-1
2.1 Introduction to This Chapter ................................................................... 2-1
2.2 Checking Construction Conditions ......................................................... 2-1
2.3 Checking Technical Documents ............................................................. 2-2
2.4 Checking Hardware Configuration and Power Supply ........................... 2-2
2.4.1 Checking Hardware Configuration ................................................. 2-2
2.4.2 Checking Power Supply ................................................................. 2-3
2.5 Checking Versions and Running of Software ......................................... 2-4
2.5.1 Checking Software of BAM ............................................................ 2-5
2.5.2 Checking Software of Emergency Workstation.............................. 2-6
2.5.3 Checking Software of LMT ............................................................. 2-7
2.5.4 Checking Software of iGWB .......................................................... 2-7
2.6 Checking Network Communication ........................................................ 2-9
2.6.1 Networking of O&M System ........................................................... 2-10
2.6.2 Method for Checking Network Communication.............................. 2-13
2.6.3 Checking Communication of Internal LAN ..................................... 2-13
2.6.4 Checking Communication of External LAN .................................... 2-14
2.6.5 Checking Communication of WAN ................................................. 2-15
2.7 Making a Backup of the Empty BAM Database ..................................... 2-16
Chapter 3 Data Configuration ......................................................................... 3-1
3.1 Introduction to This Chapter ................................................................... 3-1
3.2 Data Configuration for Newly-Deployed Office....................................... 3-1
3.2.1 Data Configuration Mode ............................................................... 3-1
3.2.2 Data Configuration Sequence ........................................................ 3-1
3.2.3 Method for Executing Data Script .................................................. 3-2
3.3 Data Collection and Planning ................................................................. 3-2
3.4 Editing and Checking Data Script ........................................................... 3-3
3.4.1 Editing Data Script ......................................................................... 3-3
3.4.2 Checking Data Script ..................................................................... 3-3
Chapter 4 Local Office Commissioning......................................................... 4-1
4.1 Chapter Contents in Brief ....................................................................... 4-1
4.2 Description of Related Concepts ............................................................ 4-1
4.2.1 Method of Loading ......................................................................... 4-1
4.2.2 Description of Board Loading Software Switches .......................... 4-1
4.2.3 Board Loading for Newly-Built Office ............................................. 4-2
 4.2.4 Description of Source Files Related to Loading ............................. 4-2
4.3 Configuring Data Offline and Preparing for Data Loading ...................... 4-3
4.4 Loading Board ........................................................................................ 4-4
4.4.1 Preparations for Loading ................................................................ 4-4
4.4.2 Loading Process ............................................................................ 4-4
4.4.3 Checking Whether Loading Is Successful ..................................... 4-7
4.4.4 Handling of Loading Problems ....................................................... 4-7
4.5 Clock Commissioning ............................................................................. 4-8
4.5.1 Description of Clock System Networking ....................................... 4-9
4.5.2 Checking Clock Cable Connection ................................................ 4-11
4.5.3 Commissioning Steps for Locking BITS Clocks ............................. 4-12
4.5.4 Commissioning Steps for Locking Peer Office Clocks ................... 4-13
4.6 Commissioning of Local Office Hardware .............................................. 4-13
4.6.1 Checking Indicator Status .............................................................. 4-13
4.6.2 Checking the Running of Hardware ............................................... 4-14
4.6.3 Hardware Switchover Verification .................................................. 4-16
4.6.4 Self-Loop Test for Local Office E1 Cables ..................................... 4-16
4.7 Modifying Settings of Loading Software Switch of Board ....................... 4-17
4.8 Setting Time for the Switch .................................................................... 4-17
Chapter 5 Interconnection Commissioning .................................................. 5-1
5.1 Introduction to This Chapter ................................................................... 5-1
5.2 Connecting with MG ............................................................................... 5-1
5.2.1 Description of Relevant Concepts .................................................. 5-1
5.2.2 Steps of Commissioning ................................................................ 5-2
5.2.3 Locating of H.248/SCTP Problems ................................................ 5-4
5.2.4 Treating SCTP Common Problems ............................................... 5-6
5.3 Connecting with BSC ............................................................................. 5-7
5.3.1 Description of Relevant Concepts .................................................. 5-7
5.3.2 Steps of Commissioning ................................................................ 5-7
5.3.3 Locating MTP Problems ................................................................. 5-10
5.3.4 Locating SCCP/TCAP Problems .................................................... 5-11
5.4 Connecting with HLR, SMC, SCP and SGSN ........................................ 5-13
5.4.1 Description of Relevant Concepts .................................................. 5-13
5.4.2 Steps of Commissioning ................................................................ 5-14
5.4.3 Locating and Treating Problems .................................................... 5-16
5.5 Connecting with MSC through ISUP & MAP/MTP ................................. 5-16
5.5.1 Description of Relevant Concepts .................................................. 5-16
5.5.2 Steps of Commissioning ................................................................ 5-17
5.5.3 Locating and Treating Problems .................................................... 5-19
5.6 Connecting with MSC through ISUP/M3UA ........................................... 5-19
 5.6.1 Description of Relevant Concepts .................................................. 5-19
5.6.2 Steps of Commissioning ................................................................ 5-21
5.6.3 Locating M3UA Problems .............................................................. 5-22
5.6.4 Treating M3UA Common Problems ............................................... 5-24
5.7 Connecting with MSC through BICC/SCTP ........................................... 5-27
5.7.1 Description of Protocol ................................................................... 5-27
5.7.2 Steps of Commissioning ................................................................ 5-29
5.7.3 Locating BICC Problems ................................................................ 5-32
5.7.4 Treating BICC Common Problems ................................................ 5-33
5.8 Connecting with RNC ............................................................................. 5-34
5.8.1 Description of Relevant Concepts .................................................. 5-34
5.8.2 Steps of Commissioning ................................................................ 5-35
5.8.3 Locating and Treating Problems .................................................... 5-36
Chapter 6 Service Commissioning ................................................................ 6-1
6.1 Introduction to This Chapter ................................................................... 6-1
6.2 Executing Data Script ............................................................................. 6-1
6.3 Implementing Service Test ..................................................................... 6-2
6.3.1 Preparations ................................................................................... 6-2
6.3.2 Method of Implementing Service Test ........................................... 6-2
6.3.3 Service Tests ................................................................................. 6-3
6.4 Handling of Common Problems ............................................................. 6-3
6.4.1 Handling of Call Abnormality .......................................................... 6-3
6.4.2 Handling of BICC Call Problems .................................................... 6-4
6.4.3 Handling of CPU Overload Problem .............................................. 6-6
Appendix A Commissioning Records of Newly-Built Office ....................... A-1
A.1 Preparations for System Commissioning ............................................... A-1
A.2 Data Configuration ................................................................................. A-3
A.3 Local Office Commissioning .................................................................. A-3
A.4 Interconnection Commissioning ............................................................. A-5
A.5 Service Commissioning ......................................................................... A-7
Index .................................................................................................................
HUAWEI

HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Installation Manual – System Commissioning

V100R002
HUAWEI MSOFTX3000 Mobile SoftSwitch Center
Installation Manual

Volume System Commissioning

Manual Version T2-030435-20041115-C-2.00

Product Version V100R002

BOM 31041535

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: [email protected]
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

The manual applies to HUAWEI MSOFTX3000 Mobile SoftSwitch Center V100R002.

Organization

The manual introduces operations about MSOFTX3000 commissioning.

There are six chapters and an appendix in the manual.

z Chapter 1 Overview of System Commissioning introduces the contents and
flow of system commissioning.
z Chapter 2 Preparations for System Commissioning describes the
preparations required before commissioning, including checking the construction
conditions, preparing technical documents, checking the hardware, software, and
network communication, and making an empty BAM database backup.
z Chapter 3 Data Configuration introduces the data configuration method and
sequence and script execution of a newly built office; explains the key points for
data collection, and points out the check points for data script.
z Chapter 4 Local Office Commissioning introduces the internal data
configuration, board loading, and checking and commissioning of the
MSOFTX3000.
z Chapter 5 Interconnection Commissioning introduces the data configuration
and commissioning of the MSOFTX3000 for connection with the MG and MSC.
z Chapter 6 Service Commissioning introduces the configuration and testing of
service data of the MSOFTX3000.
z Appendix A Commissioning Records of Newly Built Office presents the
configuration and testing of service data of the MSOFTX3000.

Intended Readers

The manual is intended for the following readers:

z WCDMA/UMTS system engineers
z Operation and maintenance engineers
z WCDMA/UMTS network administrators

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 and the keywords of a command line are in Boldface.
Courier New Terminal Display is in Courier New.

II. 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.
Right-click Press the right button quickly.

III. GUI conventions

Convention Description

<> Button names are inside angle brackets. For example, click <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.
V. 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.

 Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Table of Contents

Table of Contents

Chapter 1 Overview of System Commissioning ........................................................................ 1-1

1.1 Explanation of System Commissioning ............................................................................. 1-1
1.2 Flow of System Commissioning......................................................................................... 1-1

Chapter 2 Preparations for System Commissioning ................................................................. 2-1

2.1 Introduction to This Chapter .............................................................................................. 2-1
2.2 Checking Construction Conditions..................................................................................... 2-1
2.3 Checking Technical Documents ........................................................................................ 2-2
2.4 Checking Hardware Configuration and Power Supply ...................................................... 2-2
2.4.1 Checking Hardware Configuration .......................................................................... 2-2
2.4.2 Checking Power Supply .......................................................................................... 2-3
2.5 Checking Versions and Running of Software .................................................................... 2-4
2.5.1 Checking Software of BAM ..................................................................................... 2-5
2.5.2 Checking Software of Emergency Workstation....................................................... 2-6
2.5.3 Checking Software of LMT...................................................................................... 2-7
2.5.4 Checking Software of iGWB.................................................................................... 2-7
2.6 Checking Network Communication.................................................................................... 2-9
2.6.1 Networking of O&M System .................................................................................. 2-10
2.6.2 Method for Checking Network Communication..................................................... 2-13
2.6.3 Checking Communication of Internal LAN ............................................................ 2-13
2.6.4 Checking Communication of External LAN........................................................... 2-14
2.6.5 Checking Communication of WAN........................................................................ 2-15
2.7 Making a Backup of the Empty BAM Database............................................................... 2-16

Chapter 3 Data Configuration ...................................................................................................... 3-1

3.1 Introduction to This Chapter .............................................................................................. 3-1
3.2 Data Configuration for Newly-Deployed Office.................................................................. 3-1
3.2.1 Data Configuration Mode ........................................................................................ 3-1
3.2.2 Data Configuration Sequence ................................................................................. 3-1
3.2.3 Method for Executing Data Script ........................................................................... 3-2
3.3 Data Collection and Planning ............................................................................................ 3-2
3.4 Editing and Checking Data Script ...................................................................................... 3-3
3.4.1 Editing Data Script .................................................................................................. 3-3
3.4.2 Checking Data Script .............................................................................................. 3-3

Chapter 4 Local Office Commissioning ...................................................................................... 4-1

4.1 Chapter Contents in Brief .................................................................................................. 4-1
4.2 Description of Related Concepts ....................................................................................... 4-1
4.2.1 Method of Loading .................................................................................................. 4-1
4.2.2 Description of Board Loading Software Switches ................................................... 4-1

i
 Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Table of Contents

4.2.3 Board Loading for Newly-Built Office ...................................................................... 4-2

4.2.4 Description of Source Files Related to Loading...................................................... 4-2
4.3 Configuring Data Offline and Preparing for Data Loading ................................................. 4-3
4.4 Loading Board.................................................................................................................... 4-4
4.4.1 Preparations for Loading......................................................................................... 4-4
4.4.2 Loading Process...................................................................................................... 4-4
4.4.3 Checking Whether Loading Is Successful .............................................................. 4-7
4.4.4 Handling of Loading Problems ................................................................................ 4-7
4.5 Clock Commissioning ........................................................................................................ 4-8
4.5.1 Description of Clock System Networking ................................................................ 4-9
4.5.2 Checking Clock Cable Connection........................................................................ 4-11
4.5.3 Commissioning Steps for Locking BITS Clocks.................................................... 4-12
4.5.4 Commissioning Steps for Locking Peer Office Clocks.......................................... 4-13
4.6 Commissioning of Local Office Hardware ....................................................................... 4-13
4.6.1 Checking Indicator Status ..................................................................................... 4-13
4.6.2 Checking the Running of Hardware ...................................................................... 4-14
4.6.3 Hardware Switchover Verification ......................................................................... 4-16
4.6.4 Self-Loop Test for Local Office E1 Cables............................................................ 4-16
4.7 Modifying Settings of Loading Software Switch of Board................................................ 4-17
4.8 Setting Time for the Switch.............................................................................................. 4-17

Chapter 5 Interconnection Commissioning................................................................................ 5-1

5.1 Introduction to This Chapter .............................................................................................. 5-1
5.2 Connecting with MG .......................................................................................................... 5-1
5.2.1 Description of Relevant Concepts........................................................................... 5-1
5.2.2 Steps of Commissioning ......................................................................................... 5-2
5.2.3 Locating of H.248/SCTP Problems ......................................................................... 5-4
5.2.4 Treating SCTP Common Problems......................................................................... 5-6
5.3 Connecting with BSC......................................................................................................... 5-7
5.3.1 Description of Relevant Concepts........................................................................... 5-7
5.3.2 Steps of Commissioning ......................................................................................... 5-7
5.3.3 Locating MTP Problems........................................................................................ 5-10
5.3.4 Locating SCCP/TCAP Problems........................................................................... 5-11
5.4 Connecting with HLR, SMC, SCP and SGSN ................................................................. 5-13
5.4.1 Description of Relevant Concepts......................................................................... 5-13
5.4.2 Steps of Commissioning ....................................................................................... 5-14
5.4.3 Locating and Treating Problems ........................................................................... 5-16
5.5 Connecting with MSC through ISUP & MAP/MTP........................................................... 5-16
5.5.1 Description of Relevant Concepts......................................................................... 5-16
5.5.2 Steps of Commissioning ....................................................................................... 5-17
5.5.3 Locating and Treating Problems ........................................................................... 5-19
5.6 Connecting with MSC through ISUP/M3UA .................................................................... 5-19
5.6.1 Description of Relevant Concepts......................................................................... 5-19

ii
 Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Table of Contents

5.6.2 Steps of Commissioning ....................................................................................... 5-21

5.6.3 Locating M3UA Problems ..................................................................................... 5-22
5.6.4 Treating M3UA Common Problems ...................................................................... 5-24
5.7 Connecting with MSC through BICC/SCTP..................................................................... 5-27
5.7.1 Description of Protocol .......................................................................................... 5-27
5.7.2 Steps of Commissioning ....................................................................................... 5-29
5.7.3 Locating BICC Problems....................................................................................... 5-32
5.7.4 Treating BICC Common Problems........................................................................ 5-33
5.8 Connecting with RNC ...................................................................................................... 5-34
5.8.1 Description of Relevant Concepts......................................................................... 5-34
5.8.2 Steps of Commissioning ....................................................................................... 5-35
5.8.3 Locating and Treating Problems ........................................................................... 5-36

Chapter 6 Service Commissioning .............................................................................................. 6-1

6.1 Introduction to This Chapter .............................................................................................. 6-1
6.2 Executing Data Script ........................................................................................................ 6-1
6.3 Implementing Service Test ................................................................................................ 6-2
6.3.1 Preparations ............................................................................................................ 6-2
6.3.2 Method of Implementing Service Test..................................................................... 6-2
6.3.3 Service Tests........................................................................................................... 6-3
6.4 Handling of Common Problems......................................................................................... 6-3
6.4.1 Handling of Call Abnormality................................................................................... 6-3
6.4.2 Handling of BICC Call Problems ............................................................................. 6-4
6.4.3 Handling of CPU Overload Problem ....................................................................... 6-6

Appendix A Commissioning Records of Newly-Built Office.....................................................A-1

A.1 Preparations for System Commissioning ..........................................................................A-1
A.2 Data Configuration.............................................................................................................A-3
A.3 Local Office Commissioning..............................................................................................A-3
A.4 Interconnection Commissioning ........................................................................................A-5
A.5 Service Commissioning.....................................................................................................A-7

Index ................................................................................................................................................ i-1

iii
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 1 Overview of System Commissioning

Chapter 1 Overview of System Commissioning

1.1 Explanation of System Commissioning

System commissioning refers to a series of testing and verification operations to be
performed after the installation of hardware and software. The purpose of system
commissioning is to ensure that the system can meet the design requirements and
can work stably, reliably, and securely.
Before system commissioning, make sure that the following conditions are met:
z Hardware installation and checking have been done, and the equipment is
powered on.
z Software installation and checking have been done (excluding board loading).

1.2 Flow of System Commissioning

This manual describes the method of system commissioning for a newly-deployed
office with the MSOFTX3000. Table 1-1 is the flow of the system commissioning.

Table 1-1 Flow of system commissioning for a newly-deployed office with the MSOFTX3000

Procedure Overview
Check the construction condition, get related technical files ready,
Preparations
check system hardware, software and network communication, and
1 for system
make an empty backup file for the backend administration module
commissioning
(BAM) database.
Data
2 Perform data collection and planning, and make and check data script.
configuration
Configure internal data (hardware data and local office data) for the
Local office
3 MSOFTX3000, load boards and check them, and perform
commissioning
commissioning to the local office equipment.
Perform data configuration and commissioning for the connection
Interconnection between the MSOFTX3000 and the media gateway (MGW), mobile
4
commissioning switching center (MSC), as well as home location register (HLR), and
so on.
Service
5 Perform configuration and commissioning for service data.
commissioning

1-1
Installation Manual - System Commissioning Chapter 2 Preparations for System
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Commissioning

Chapter 2 Preparations for System

Commissioning

2.1 Introduction to This Chapter

In view of complexity of system commissioning, necessary preparations must be
made before commissioning, in order that subsequent commissioning can be done
smoothly.
The preparations include:
z Checking construction conditions
z Checking whether technical files needed for deployment are complete
z Checking hardware configuration and power supply
z Checking versions and running of software
z Checking the network communication of the operation and maintenance system
z Making a backup of the empty BAM database for emptying the configured data of
the BAM database, if necessary

2.2 Checking Construction Conditions

Table 2-1 Checking the construction conditions

Item Description Result Remarks

Whether the hardware
□ Y; □ N
installation is completed
Whether the installation of
Hardware □ Y; □ N
hardware has been checked
Whether the equipment is
□ Y; □ N
powered on For the installation of hardware and
software, refer to HUAWEI
Whether the software for the MSOFTX3000 Mobile SoftSwitch
BAM, local maintenance Center Installation Manual.
terminal (LMT) and □ Y; □ N
emergency workstation has Software installation does not include
been installed data configuration and board software
loading.
Software Whether the virtual local
area network (VLAN) of the
□ Y; □ N
core LAN Switch has been
configured
Whether the installation of
□ Y; □ N
software has been checked

2-1
Installation Manual - System Commissioning Chapter 2 Preparations for System
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Commissioning

2.3 Checking Technical Documents

Table 2-2 Technical documents needing to be prepared

<Item Result Remarks

This document is to be completed by the design unit designated
Network Plan □ Y; □ N by the customer, and should be sent to the vendor in duplicate
before product delivery.
This document is to be filled out by Huawei technicians while
Site Survey Report □ Y; □ N
doing the site survey.
This document is to be prepared by the engineering department
Engineering
□ Y; □ N of Huawei according to the office configuration and networking of
Documents
the customer, and to be delivered to the site with the equipment.
These documents include the Installation Manual, Operation
Package of Manual, Hardware Description Manual, Maintenance Manual,
□ Y; □ N
Documents and iGWB User Manual. They are to be delivered to the site with
the equipment.
Software and Data
□ Y; □ N This document is to be supplied by Huawei.
Script
Other Engineering These documents include the contract agreement, system
□ Y; □ N
Documents configuration table and delivery list.

2.4 Checking Hardware Configuration and Power Supply

You need to check hardware and power supply after the hardware installation, but
before data configuration and board loading. This will ensure that the subsequent
commissioning can be done smoothly.

2.4.1 Checking Hardware Configuration

Warning:

z Before touching any board, you must wear an electrostatic discharge (ESD) preventive wrist strap,
which should be properly grounded.
z Be careful not to touch the circuits and components on a board while checking the board version and
the setting of Dual in-line package switches (DIP switch).

2-2
Installation Manual - System Commissioning Chapter 2 Preparations for System
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Commissioning

Caution:

z When inserting a board into a subrack, if the plugging indicator (in blue) is on, it indicates that the
board is in contact with the backplane. Then you can press the ejector levers of the front panel to
completely insert the board into the backplane.
z To plug out the board, press the ejector levers of the front panel. Then the plugging indicator (in blue)
is on. You can only plug out the board when this indicator is on.

Table 2-3 Checking the hardware configuration

Item Description Result Remarks

Check the Whether the BAM server, iGWB
server and server, LMT, emergency
□ Y; □ N
auxiliary workstation, and alarm box are
equipment consistent with the delivery list
Check the Whether the number of cabinets and
cabinets subracks is consistent with that
□ Y; □ N If hardware configuration is
and written in the delivery list and
inconsistent with the delivery list
subracks Engineering documents.
and Engineering Documents,
Whether the configuration of boards contact Huawei technical support
Check personnel for help immediately.
in subracks is consistent with the
board
delivery list and the Engineering □ Y; □ N For description of DIP switches of
configurati
Documents, and whether board the Wireless System Interface Unit
on
positions are correct. (WSIU), refer to HUAWEI
MSOFTX3000 Mobile SoftSwitch
Check software versions and Center Hardware Description
Check
hardware versions of boards Manual.
board □ Y; □ N
according to the version
versions
configuration information.
Check the
Whether the setting of DIP switch S3
setting of
of the WSIU is consistent with the □ Y; □ N
subrack
subrack number.
numbers

2.4.2 Checking Power Supply

2-3
Installation Manual - System Commissioning Chapter 2 Preparations for System
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Commissioning

Table 2-4 Checking the power supply

Item Description Result Remarks

Whether all the –48 V power output
switches in the power distribution □ Y; □ N
subrack are set to “ON”.
Whether the green “RUN” indicator Note:
on the front panel of the power When the wireless system
□ Y; □ N
Check the distribution subrack flashes, and the management unit (WSMU) has not
power red “ALM” indicator is off. been powered on or the software of
distribution it has not been loaded, the “ALM”
subrack indicator of the power distribution
Whether the alarm sound stopping subrack will flash at 4-Hz) rate with
switch on the front panel of the an alarm sound. This indicates that
□ Y; □ N the communication between the
power distribution subrack is on, and
the alarm buzzer is silent. power distribution subrack and the
WSMU is interrupted. You need not
worry about it.
Note:
When the WSMU is not powered
on or the software of it is not
Check Whether the fans run normally, and loaded, the “STATUS” indicator of
subrack the “STATUS” fan indicator flashes □ Y; □ N the fan box will blink fast, indicating
fans in green. that the communication between
the fan box and the WSMU is
interrupted. You need not worry
about it.
Check Whether the green “RUN” indicator
power on the UMSC PSM power module
□ Y; □ N
boards in (UPWR) is on, and the red “ALM”
subracks indicator is off.
Check the Whether the indicator of the BAM If this indicator is in orange, it
□ Y; □ N
server and iGWB power switch is in green. indicates that the server is standby.
hCheck Whether the green “POWER” If the “POWER” indicators are not
the LAN indicators on the panels of LAN □ Y; □ N on, it indicates that power supply
Switch Switch 0 and LAN Switch 1 are on. for the LAN Switches is faulty.

2.5 Checking Versions and Running of Software

You need to check the version information and running status of the software installed
on the BAM, LMT, and emergency workstation after checking the software installation.
This is important for the subsequent commissioning.

2-4
Installation Manual - System Commissioning Chapter 2 Preparations for System
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Commissioning

2.5.1 Checking Software of BAM

Table 2-5 Checking the software of the BAM

Item Description Result Remarks

On the BAM, start “MSOFTX3000
If the version of the BAM server
Operation and Maintenance
software does not meet the
Check the Center”, select [Help/About], check
requirement of site deployment,
software the version number of the BAM □ Y; □ N
contact Huawei technicians for help
version server software, and confirm
timely, and re-install the BAM
whether the version meets the
server software if necessary.
requirement of site deployment.
Check the
On the BAM, check whether the icon If the icon is there, it indicates that
running
the SQL Server 2000 service
state of the is in the taskbar on the bottom □ Y; □ N
manager can start automatically
SQL right corner of the desktop. and can run normally.
Server
If the status of any service is
On the BAM, select
“Stopped” or its startup type is not
[Start/Programs/Administrative
“Automatic”, you can start the
Tools/Services] to display the
service or modify its startup type in
Check the [Services] window. Check services
the [Services] window which pops
running of “BAM Service”, “Smirror”, and □ Y; □ N
up when you double-click the
services “Performance Logs and Alerts” to
service. If the problem still exists,
see if their statuses are displayed as
contact Huawei technicians for help
“Started” and their startup types are
immediately, and re-install the BAM
“Automatic”.
software if necessary.

On the BAM, double-click the If the status of a process is

icon in the taskbar on the bottom “Exception”, it indicates that the
right corner of the desktop to display process is abnormal. You can solve
Check the the [BAM Manager] window. Check this problem by closing the BAM
running of service processes, including “Warn”, □ Y; □ N server program and then restarting
processes “DataMan”, “Maintain”, “Stats”, it. If the problem still exists, contact
“MML”, “Exchange”, “FTPMan”, Huawei technicians for help
“XSman”, and “SNTPClient”, to see immediately, and re-install the BAM
if their statuses are all “Started”. software if necessary.

On the BAM, open the log file under

the installation directory of
Check the SetWin2000 to check whether
The default installation directory is:
SetWin200 security items have been
C:\ Program Files \ Huawei
0 security customized. For example, “Setting □ Y; □ N
Technologies Co., Ltd \ Windows
customizat directory access authority control
2000 security customization tools
ion tool completed” indicates that you have
set directory access authority
control.
On the BAM, select [Start /
Programs / Administrative Tools /
Services]. The [Service] window
Check
appears. Check □ Y; □ N
SysPatron
“_UM_PPT_Service”. Its status
should be “Started” and its startup
type “Automatic”.

2-5
Installation Manual - System Commissioning Chapter 2 Preparations for System
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Commissioning

Item Description Result Remarks

If you are prompted to press the
On the BAM, select [Start/Shut combination keys <Ctrl+Alt+Del>
Down…] to display the [Shut Down for login, it indicates that the setting
Windows] window, select “Restart” for automatic login to Windows
for operation type, and then restart 2000 Server is not successful.
□ Y; □ N
the BAM. After restart, the system Refer to the HUAWEI
will automatically log in to the BAM MSOFTX3000 Mobile SoftSwitch
server as the Administrator. You Center Installation Manual –
need not input the login password. Software Installation to redo the
setting.
If the icon is there, it indicates that
Check After BAM restart, the icon the SQL Server 2000 service
appears in the taskbar on the bottom □ Y; □ N
BAM manager can start automatically
restart right corner of the desktop. and can run normally.

After BAM restart, the [BAM

If BAM Manager cannot run
Manager] window will pop up
automatically or some service
automatically, and the icon processes are in the “Exception”
appears in the taskbar on the bottom status, it indicates that the system
right corner of the desktop, cannot run normally or the
indicating that BAM Manager can □ Y; □ N
installation of the BAM server
run automatically. software fails. If this is true, contact
Huawei technicians for help
Check all the service processes on
immediately and re-install the BAM
the [BAM Manager] window to see if
software if necessary.
their statuses are all “Started”.

2.5.2 Checking Software of Emergency Workstation

Table 2-6 Checking the software of the emergency workstation

Item Description Result Remarks

On the emergency workstation, start
“MSOFTX3000 Operation and
If the software version is not
Maintenance Center”, select
identical with that of the BAM
Check [Help/About], check the version of
server software or cannot meet site
software the software, and confirm whether □ Y; □ N
deployment requirement, contact
version the version is identical with that of
Huawei technicians for help
the BAM server software and
immediately.
whether it meets the requirement of
site deployment.

Check the On the emergency workstation, If the icon is there, it indicates that
running of check whether the icon appears the SQL Server 2000 service
□ Y; □ N
the SQL in the taskbar on the bottom right manager can start automatically
Server corner of the desktop. and can run normally.

2-6
Installation Manual - System Commissioning Chapter 2 Preparations for System
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Commissioning

Item Description Result Remarks

On the emergency workstation,
select
[Start/Programs/Administrative You can start a service or modify its
Tools/Services] to display the startup type in the [Services]
[Services] window, check the status window by double-clicking this
Check the
of services “BAM Service” and service. If this fails, contact Huawei
running of □ Y; □ N
“Smirror”. The status of “Smirror” technicians for help immediately,
services
should be “Started” and its startup and re-install the software of the
type should be “Automatic”. The emergency workstation if
status of “BAM Service” should be necessary.
“Stopped”, and its startup type
should be “Manual”.

2.5.3 Checking Software of LMT

Table 2-7 Checking the software of the LMT

Item Description Result Remarks

On the LMT, start “MSOFTX3000
If the version of the software is not
Operation and Maintenance
identical with that of the BAM
Center”, select [Help/About], check
Check server software or does not meet
the version of the software, and
software □ Y; □ N the requirement of site deployment,
confirm whether the version is
version contact Huawei technicians for help
identical with that of the BAM server
immediately; and re-install the BAM
software and meets the requirement
software if necessary.
of site deployment.

2.5.4 Checking Software of iGWB

Note:
For the principles and operations of iGWB, refer to iGWB User Manual.

Table 2-8 Checking the software of the iGWB

Item Description Result Remarks

On the iGWB operation and
maintenance terminal, select If the version of the software does
[Start/Programs/iGateway Bill V200 not meet the requirement of site
Check
Client/iGWB Client] to start and log deployment, contact Huawei
software □ Y;□ N
in to the bill console. Select technicians for help immediately;
version
[Help/About] to check if the software and re-install the iGWB software if
version meets the deployment necessary.
requirement.

2-7
Installation Manual - System Commissioning Chapter 2 Preparations for System
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Commissioning

Item Description Result Remarks

On the iGWB operation and This operation is only applicable to

maintenance terminal, select dual-system configuration office.
Check [Start/Programs/iGateway Bill V200 For “2/2”, the denominator
dual-syste Client/iGWB Client] to start and log indicates the total number of
□ Y;□ N
m in to the bill console. Select heartbeat links, and the numerator
heartbeat [Operation/State Query] to check indicates the number of current
the heartbeat state. Normally, the available links, which should be the
heartbeat state should be “2/2”. same.

On the active iGWB server, all the

processes should be running.
On the standby iGWB server, only
Start Windows 2000 task manager
the process cls_proc.exe should be
on the active and standby iGWB
running.
Check the servers, and then click [Processes]
running of tab to check if such processes as □ Y;□ N The number of the process
processes cls_proc.exe, ap_proc.exe, ap_proc.exe on the active iGWB
knl_proc.exe, and om_proc.exe are server should be the same as the
running. value set for the parameter
“APCount”. This parameter is under
the configuration item [Common] in
the configuration file igwb.ini.

On the active and standby iGWB

servers, select [Start/Shut Down…] If you are prompted to press the
to display the [Shut Down Windows] combination keys <Ctrl+Alt+Del>
Check window, select “Restart” for for login, it indicates that the setting
iGWB operation type, and then restart the □ Y;□ N for automatic login to Windows
restart iGWB. After restart, the system will 2000 Server is not successful.
automatically log in to the iGWB Refer to the iGWB User Manual to
server as the Administrator. You redo the setting.
need not input the login password.
Close the active iGWB (iGWB If the switchover between the active
0).After five minutes, the standby and standby iGWB servers fails, or
iGWB server (iGWB 1) becomes the some processes cannot run
Check
active one, its power indicator is on normally, or the currently active
iGWB □ Y;□ N
in green, and the processes iGWB is not normal, it indicates that
switchover
cls_proc.exe, ap_proc.exe, the MSOFTX3000 has problems in
knl_proc.exe, and om_proc.exe are operation or the installation of the
running normally. iGWB server software is not
successful. In this case, contact
On the iGWB operation and Huawei technicians for help
maintenance terminal, select immediately and re-install the
[Start/Programs/iGateway Bill V200 iGWB software if necessary.
Client/iGWB Client] to start and log □ Y;□ N
in to the bill console. Select
[Operation/State Query] to check if
the active iGWB is in normal state.

2-8
Installation Manual - System Commissioning Chapter 2 Preparations for System
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Commissioning

Item Description Result Remarks

Restart iGWB 0. After restart, it
takes over the services
automatically, and the processes
cls_proc.exe, ap_proc.exe,
knl_proc.exe, and om_proc.exe are
running normally. □ Y;□ N
At the same time, iGWB 1 is
standby, its power indicator is in
orange, and only the process
cls_proc.exe is running.
On the iGWB operation and
maintenance terminal, select
[Start/Programs/iGateway Bill V200
Client/iGWB Client] to start and log
in to the bill console. Select □ Y;□ N
[Operation/State Query] to check if
the active iGWB is in normal state
and if the dual-system heartbeat
state is normal.

2.6 Checking Network Communication

Since system commissioning is performed through the operation and maintenance
(O&M) system, you must assure that the communication of the O&M system is normal
first.

2-9
Installation Manual - System Commissioning Chapter 2 Preparations for System
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Commissioning

2.6.1 Networking of O&M System

Figure 2-1 illustrates the O&M system of the MSOFTX3000.

W W
S S
M M
U U
Service processing frame
W W W W
S H S H
I S I S
U C U C

LAN Switch 0 LAN Switch 1

Bound to
Bound to
Billing
Billing
WAN Center
Center WAN

standby iGWB BAM Emergency active iGWB

workstation

HUB or LAN Switch Bound to

NMC WAN

LMT LMT

Figure 2-1 The O&M system of the MSOFTX3000

I. IP Address of the BAM Server

Table 2-9 Setting the IP addresses of the BAM

Network card
Opposite equipment IP address/mask
ID
It is bound to LAN Switch 0, and communicates
Ethernet card 0 172.20.200.0/16
with the active plane of the host.
It is bound to LAN Switch 0, and communicates
Ethernet card 1 172.30.200.0/16
with the standby plane of the host.
Ethernet card 2 Standby –
It communicates with the LMT and the emergency
To be provided by the
Ethernet card 3 workstation through an external HUB or LAN
customer
Switch.

2-10
Installation Manual - System Commissioning Chapter 2 Preparations for System
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Commissioning

II. IP Address of Emergency Workstation

Table 2-10 Setting the IP addresses of the emergency workstation

Network card ID Opposite equipment IP address/mask

It is standby. In emergency cases, it is connected
Ethernet card 0 172.20.200.0/16
to LAN Switch 0 for communicating with the host.
It is standby. In emergency cases, it is connected
Ethernet card 1 172.30.200.0/16
to LAN Switch 1 for communicating with the host.
Ethernet card 2 Standby –
It communicates with the BAM through an To be provided by the
Ethernet card 3
external HUB or LAN Switch. customer

III. IP Address of LMT

Table 2-11 Setting the IP address of the LMT

Network card ID Opposite equipment IP address

It communicates with the BAM through an To be provided by the
Ethernet card
external HUB or LAN Switch. customer

IV. IP Address of WSMU

The WSMU is connected with the WSIU through an internal wire, and the WSIU
provides external Ethernet ports. Since what is adopted is biplane communication,
two IP addresses will be configured for each WSMU either before or after board
loading, as described in Table 2-12.

Table 2-12 Setting the IP addresses of the WSMU

Slot IP address 1 / mask IP address 2 / mask

172.20.subrack
Before WSMU in slot 6 172.30.subrack number.100/16
number.100/16
board
loading 172.20.subrack
WSMU in slot 8 172.30.subrack number.101/16
number.101/16
After board WSMUs in slot 6 and 172.20.200.module
172.30.200.module number/16
loading slot 8 number/16

2-11
Installation Manual - System Commissioning Chapter 2 Preparations for System
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Commissioning

Note:
z Subrack numbers range from 0 to 9, which are to be determined by DIP switch S3 of the WSIU. For
details, refer to HUAWEI MSOFTX3000 Mobile SoftSwitch Center Hardware Description Manual.
z The WSMU module numbers range from 2 to 21, which is allocated by the MSOFTX3000
automatically according to the setting of the DIP switches of the WSIU. The module number of the
WSMU in subrack 0 is 2, the WSMU in subrack 1 is 3, and so on.

V. IP Address of iGWB

Table 2-13 lists the default IP addresses of the iGWB. You can set the IP addresses as
needed during deployment by the following principles:
z iGWB applies dual-host configuration. It communicates with external devices
through virtual IP addresses. Its actual IP addresses need to be set, but this IP
address is insignificant for external communication.
z The customer needs to provide the virtual IP addresses for communication with
the bill console and billing center.
z The IP addresses must be the same as those set in the file igwb.ini.

Table 2-13 IP addresses of the iGWB

Network card Network card IP Network card IP of Virtual

Opposite equipment
ID of active iGWB standby iGWB IP/mask
It is bound to LAN Switch
Netcard0 to 0, and communicates with 172.20.2
130.1.1.1 130.1.1.2
0#LAN Switch the active plane of the 00.1/16
host.
It is bound to LAN Switch
Netcard1 to 1, and communicates with 172.30.2
130.1.2.1 130.1.2.2
1#LAN Switch the standby plane of the 00.1/16
host.
It is bound to the bill
console and network To be
Netcard2 to management system provided
130.1.3.1 130.1.3.2
Office LAN interface, and acts as the by the
first heartbeat link of the customer
iGWB dual-host system.
To be
It is bound to the billing
Netcard3 to provided
center, and provides 130.1.4.1 130.1.4.2
Billing Center by the
billing interface.
customer

2-12
Installation Manual - System Commissioning Chapter 2 Preparations for System
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Commissioning

2.6.2 Method for Checking Network Communication

The BAM, LMT, emergency workstation, and iGWB server all use the Windows 2000
operation system. The command line window of Windows provides the PING
command, which can be used to check network communication. Normally, if an IP
address can be pinged successfully, it indicates that the communication is normal.
For example, to check the communication between the BAM and the WSMU of
subrack 0 (before board loading, the IP addresses of the WSMU in slot 6 are
172.20.0.100 and 172.30.0.100, those of the WSMU in slot 8 are 172.20.0.101 and
172.30.0.101), proceed as follows:
1) On the BAM, select [Start/Run], and execute the CMD command to display the
MML window.
2) Execute the command PING 172.20.0.100. If the information returned is "Reply
from 172.20.0.100: byte=32 time<10ms TTL=128", it indicates that the
communication is normal. If the time in the returned information is too long or the
information returned is "Request Timed out", it indicates that the communication
is abnormal.
3) Repeat Step 2 to ping the other three IP addresses in sequence to check the
communication.

2.6.3 Checking Communication of Internal LAN

As shown in Figure 2-1, the BAM and host (board) form an internal local area network
(LAN), and both communicate through LAN Switch 0 and LAN Switch 1 in the
cabinet. .As adopting biplane communication, MSOFTX3000 uses two network
segments: 172.20.xxx.xxx; and 172.30.xxx.xxx. The IP address of each component
has been set within the two network segments. For details, refer to Section 2.6.1
“Networking of O&M System”.

Table 2-14 Checking the communication of the internal LAN

Item Description Result Remarks

Check whether the IP addresses of
Check the
the BAM and iGWB are correctly set In the internal LAN, the IP address of each
setting of the □ Y; □ N
based on the description in 2.6.1 I. component is fixed.
IP address
IP Address of the BAM Server.

On the BAM, ping the IP address of If the ping command is executed

the WSMU in each subrack (for the successfully, it indicates that the
Check the IP address setting, refer to 2.6.1 IV. communication is abnormal. Check the
communication IP Address of WSMU). If the ping connection of Ethernet cables, whether
□ Y; □ N
between the command is executed successfully, it the IP addresses of the BAM and iGWB
BAM and host indicates that the communication are correctly set, and whether the DIP
between the BAM and host is switch on the WSIU that determines
normal. subrack numbering is correctly set.

2-13
Installation Manual - System Commissioning Chapter 2 Preparations for System
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Commissioning

Item Description Result Remarks

Check the Ping the IP addresses of the iGWB
communication 172.20.200.1 and 172.30.200.1 from
between the the BAM. If the ping command is □Y; □ N
BAM and executed successfully, it indicates
iGWB that the communication is normal.
On the iGWB, ping the IP address of
the WSMU in each subrack (for the
Check the
IP address setting, refer to 2.6.1 IV.
communication
IP Address of WSMU). If the ping □ Y;□ N
between the
command is executed successfully, it
iGWB and host
indicates that the communication is
normal.
Based on the description in HUAWEI
MSOFTX3000 Mobile SoftSwitch
Center Installation Manual – For details, refer to the description on
Check the
Software Installation, log in to the setting VLAN in HUAWEI MSOFTX3000
setting of □ Y; □ N
LAN Switch through a serial port, Mobile SoftSwitch Center Installation
VLAN
execute the command display vlan Manual – Software Installation.
all, and check whether VLAN is
correctly set.
Turn off the power switch (SW3) of
LAN Switch 1. Check whether the
communication between the BAM
□ Y; □ N
and the host is normal or not
according to the related description Caution:
above. Before turning off the power switch of LAN
Check the
Ethernet Switch, make sure you have saved the
Turn on the power switch of LAN
biplane current configured data of the LAN Switch.
Switch 1 (SW3), and turn off the
switchover power switch (SW2) of LAN Switch 0. Note:
function Check the communication state After logging in to the LAN Switch, you can
between the BAM and the host □ Y; □ N execute the save command to save the
according to the related description current configuration of the LAN Switch.
above..
After the check, turn on the power
switch (SW2) of LAN Switch 0.

2.6.4 Checking Communication of External LAN

As shown in Figure 2-1, the BAM server, iGWB server, LMT, and the emergency
workstation together form an external LAN, which communicate through an external
HUB or LAN Switch. The IP address of each component is to be provided by the
customer.

2-14
Installation Manual - System Commissioning Chapter 2 Preparations for System
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Commissioning

Caution:

The network segment and IP addresses used by the external LAN are to be provided by the customer.
They are different from those of the internal LAN (172.20.xxx.xxx, 172.30.xxx.xxx).

Table 2-15 Checking the communication of the external LAN

Item Description Result Remarks

In the external LAN, the IP
Check the Check whether the IP addresses of the
address of each component
setting of IP BAM, LMT, emergency workstation, □ Y; □ N
is to be provided by the
addresses and iGWB are correctly set.
customer.
Check the Ping the IP address of the LMT on the
communicat BAM; ping the IP address of the BAM
ion between from the LMT. If the ping command is □ Y; □ N
the BAM executed successfully, it indicates that
and LMT the communication is normal.
Check the Ping the IP address of the emergency If the communication is
communicat workstation on the BAM; ping the IP abnormal, check whether the
ion between address of the BAM from the IP address of each
the BAM emergency workstation. If the ping □ Y; □ N component is correctly set,
and the command is executed successfully, it whether Ethernet cables are
emergency indicates that the communication is correctly connected, and
workstation normal. whether the external HUB or
LAN Switch works normally.
Ping the IP address of the iGWB from
Check the
the BAM; ping the IP address of the
communicat
BAM from the iGWB. If the ping
ion between □ Y; □ N
command is executed successfully, it
the BAM
indicates that the communication is
and iGWB
normal.

2.6.5 Checking Communication of WAN

As shown in Figure 2-1, the BAM server is connected to the network management
center (NMC) over the wide area network (WAN), and the iGWB connects to the
billing center through WAN. The IP addresses of the NMC and billing center are to be
provided by the customer.

2-15
Installation Manual - System Commissioning Chapter 2 Preparations for System
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Commissioning

Table 2-16 Checking the communication of the WAN

Item Description Result Remarks

Ping the IP address of the NMC
Check the
server (to be provided by the
communicat
customer) on the BAM. If the ping If the communication is abnormal,
ion between □ Y; □ N
command is executed check whether the IP address is
BAM and
successfully, it indicates that the correct, whether Ethernet cables
NMC
communication is normal. are correctly connected, whether
Check the Ping the IP address of the billing devices connected to the WAN (like
communicat center server (to be provided by routes) can work normally, and
ion between the customer) from the iGWB. If whether route data is correctly
□ Y; □ N configured.
the iGWB the ping command is executed
and billing successfully, it indicates that the
center communication is normal.

2.7 Making a Backup of the Empty BAM Database

Note:
For details on database backup and recovery, refer to HUAWEI MSOFTX3000 Mobile SoftSwitch Center
Operation Manual – Routine Operation.

Before data configuration, you need to make a backup of the empty BAM database
with SQL Server Enterprise Manager, for emptying the configured data in the BAM
database if necessary.
Proceed as follows:
1) On the BAM server, select [Start/Programs/Microsoft SQL Server/Enterprise
Manager]. Then the window [SQL Server Enterprise Manager] will pop up.
2) As shown in Figure 2-2, after entering [Console Root/Microsoft SQL
Servers/SQL Server Group/(Local)(Windows NT)/Databases/BAM], right-click
and select [All Tasks/Backup Database] from the shortcut menu. Then the
window shown in Figure 2-3 will appear.

2-16
Installation Manual - System Commissioning Chapter 2 Preparations for System
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Commissioning

Figure 2-2 [SQL Server Enterprise Manager] window

Figure 2-3 [SQL Server Backup- Bam] dialog box

2-17
Installation Manual - System Commissioning Chapter 2 Preparations for System
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Commissioning

3) In the “Database” field, select “Bam”. In the “Backup” field, select “Database –
complete”. In the “Overwrite” field, select “Append to media”. In the “Destination”
field, select the default backup file and click <Remove> to delete the default
value. Click <Add> and set the path and name of backup file, as shown in
Figure 2-4.

Figure 2-4 [Select Backup Destination] dialog box

4) Click <OK> to start data backup. A backup progress dialog box appears. When
the backup is completed, the system will give a prompt indicating the success of
the backup.
5) Go to the directory of the backup file and modify the name of the backup file just
generated, so that this file will not be overwritten by subsequent backup
operations.

2-18
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Data Configuration

Chapter 3 Data Configuration

3.1 Introduction to This Chapter

Data configuration for an office with the MSOFTX3000 is an important part of the
system. Data configuration is critical to the normal running of the system and
determines the quality of a communication network.
To complete data configuration fast and effectively, do the following:
1) Data collection and planning: understand the networking, collect equipment
configuration data, external interface data and interworking negotiation data, and
plan the distribution of resources and describes it in a chart.
2) Data script editing and checking: based on the actual situation, make/edit data
script files, and check their correctness.

Note:
For detail on data configuration, refer to HUAWEI MSOFTX3000 Mobile SoftSwitch Center Operation
Manual – Data Configuration.

3.2 Data Configuration for Newly-Deployed Office

3.2.1 Data Configuration Mode

For a newly-deployed office, the first data configuration is done usually by loading data
script files. This will raise efficiency and reduce errors. A data script file is a text-only file,
containing human machine language (MML) commands that can be executed
successively.

3.2.2 Data Configuration Sequence

The sequence of data configuration for a newly-deployed office is: internal data,
external interface data, and service data. The process is as follows:
1) Configure internal data, including hardware data and local office data (for example,
signaling point code).
2) Configure external interface data, including interface data for the interworking
between the local office and other network elements (for example, interface data
for the interworking with other MSCs).

3-1
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Data Configuration

3) Configure service data, including number analysis data, mobile service data and
intelligent network (IN) service data.

3.2.3 Method for Executing Data Script

Usually, data configuration is done on the LMT. The method is described below:
1) Copy data script files to be executed to the hard disk of the LMT.
2) On the LMT, start the client program of the MSOFTX3000 O&M software, and log
in to the BAM.
3) Select [System/Execute Batch Commands...], or press <Ctrl + E>. The [Execute
Batch File] window will pop up. Select a data script file to be executed, set the
execution mode as “Immediate Execution”, and click <OK>.
4) The system will check the syntax of the data script file. If no error is found, the
[Execute Batch Process Immediately] window will pop up, on which the data script
contents to be executed will be listed.
5) From the lower part of the window, select “Execute All” for the execution type.
Click <Go> to execute the script file.
6) During the execution, if any error is found with the MML commands, parameters or
grammar in the data script file, an alarm window will appear. The system inquires
whether to go on the execution.
7) After the execution of the data script file, the number of the MML commands that
succeeded and failed in the execution will be given in the “Execution result of” box
in the lower part of the window.
8) Close the [Execute Batch Process Immediately] window.

3.3 Data Collection and Planning

To complete data configuration fast and effectively, data collection and planning are
required before data configuration. Follow the description in HUAWEI MSOFTX3000
Mobile Softswitch Center Operation Manual – Data Configuration for data collection.
And complete corresponding data collection forms about the following:
z Networking mode.
z Equipment configuration: board configuration in subracks, links provided by
boards, and so on.
z Data for external interfaces and interworking negotiation: signaling link, IP
addresses, port numbers, and so on.
z Service data.

3-2
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Data Configuration

3.4 Editing and Checking Data Script

3.4.1 Editing Data Script

At deployment, Data Center of Huawei will provide the data script file. These files are
required based on the data configuration sequence, each being responsible for a
specified part of the data configuration.
Data script files need to be edited/modified on site according to the actual need. Also,
they should be checked for errors.
A data script file is a text-only file, its contents being MML commands that can be
executed successively. It can be edited with a text editing tool (like Notepad) or
generated on the O&M interface (selecting [System/Save Input Commands...] for
inputting and saving MML commands in the data script file).
Before editing data script, you must be familiar with the network structure and read
through the data provided by the customer, including the routing plan, caller number
analysis plan, trunk data, link data, number resource for every office direction and
signaling point code. Also, they must try to rationally plan resources, make a point of
the system reliability, effectiveness and maintainability and have future capacity
expansion in mind.

3.4.2 Checking Data Script

After editing the data script, you must check it with reference to the networking data,
external interface data, interworking and negotiation data, and service data collected
on site.

3-3
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Local Office Commissioning

Chapter 4 Local Office Commissioning

4.1 Chapter Contents in Brief

This chapter describes the internal data configuration, board loading and checking,
and commissioning of clock and hardware for a newly-deployed office. The contents
include:
1) Offline execution of data script, including hardware data and local office data
2) Board loading
3) Clock commissioning (optional)
4) Commissioning of local office hardware
5) Modification of loading software switch of a board
6) Setting of MSOFTX3000 time

4.2 Description of Related Concepts

4.2.1 Method of Loading

When a board of the MSOFTX3000 restarts because of power-on or resetting, the

board will always be loaded. Loading is a process during which software and data are
loaded from an external memory to the memory of the MSOFTX3000 host (board).
According to the location for storing source files, loading will be performed in two
modes:
1) From BAM
In this mode, the source file to be loaded is stored in the hard disk of the BAM, which
loads programs and data to memories of boards across the internal Ethernet
connected with the host.
2) From the Flash memory
In this mode, the source file to be loaded is stored in Flash memories of boards, from
where programs and data are loaded to memories of boards through the internal data
buses of boards.

4.2.2 Description of Board Loading Software Switches

The mode of board loading is controlled by the loading software switch of a board. In
fact, the software switch is a software parameter, which can be set with the MOD LSS
command. It is used to select program and data loading path.
Factory setting of the board loading software switch:

4-1
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Local Office Commissioning

z PE=NO (program unavailable): The program in the Flash memory of the board is
unavailable. The program has to be loaded to the board from the BAM.
z DE=NO (data unavailable): The data in the Flash memory of the board is
unavailable. Data has to be loaded from the BAM.
z DW=NO (data not writable): It is not allowed to write data to the Flash memory.
z PW=NO (program not writalbe): It is not allowed to write programs to the Flash
memory.

4.2.3 Board Loading for Newly-Built Office

By default, there is no program and data in the Flash memory of a board. For a newly
built office, software and data are usually loaded from the BAM hard disk to the
memory of a board:
z Before loading a board, modify the settings of the loading software switch of a
board as “program unavailable, data unavailable, data writable, program
writable.” Thus, program and data can be loaded to the board from the BAM and
written to the Flash memory of the board.
z After board loading, modify the settings of the loading software switch of a board
as “program available, data available, data writable, program not writable.” This
ensures that programs and data can be quickly loaded from the Flash memory of
a board, when a board is restarted because of power-on or resetting.
z For effective fault locating, software and data are usually loaded by powering off
frames one by one.

4.2.4 Description of Source Files Related to Loading

I. Host Software Files

After the installation of the software of the BAM, the software required for the running
of the MSOFTX3000 host is copied to the hard disk of the BAM. By default, these files
are stored under D:\Data\ of the BAM in the DOS format.
Under D:\Data\, all the binary files with a suffix other than “.dat” are host software files.
They may have such suffixes as “.bin”, “.elf”, “.map”, “.smu”, and “.ifm”.

II. Host Data Files

After data configuration and the execution of the format conversion command FMT,
data required by the running of the MSOFTX3000 host is also stored under D:\Data\
of the BAM in the DOS format.
Under D:\Data\, all the binary files with the suffix “.dat” are host data files. These files
have a prefix of “DB_”.

4-2
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Local Office Commissioning

III. Loading Files

All the host data files will be compressed before loading software and data from the
BAM to the host. This will reduce the communication between the host and BAM and
increase the loading rate. In addition, host software files with board names (for
example, “.smu” and “.ifm”) as their suffixes will also be compressed. For
discrimination purpose, these compressed files will have new filenames. That is, the
character “$” will be added in the front of the name.

4.3 Configuring Data Offline and Preparing for Data Loading

For a newly-deployed office, follow the steps listed in Table 4-1 to perform data
configuration offline and make preparations for board loading.

Table 4-1 Steps for the internal data configuration

Step Operation Remarks

If you cannot log in to the BAM, check
On the LMT, start the client
whether the LMT is logging in on the BAM,
Start the LMT program of the MSOFTX3000
1 whether the username and password are
client O&M software, and log in to the
correct, and whether the cable between
BAM.
LMT and BAM is properly connected.
Open the MML window and
The meanings of the commands:
execute the following commands:
Offline, alarm LOF: Offline
2 off, and format LOF:;
conversion SET CWSON: local alarm on/off
SET CWSON: SWT=OFF;
SET FMT: format conversion on/off
SET FMT: STS=OFF;
Press shortcut keys <Ctrl + E> to For detail on operations to data script files,
display the [Execute Batch File] refer to “Method for Executing Data Script”
window, and execute data script in Chapter 3.
files in sequence. For commands that fail in the execution,
Execute data Upon completing every script, use the empty BAM database backup to
3
script files check the “Execution result of” recover the database, so as to clear the
box in the lower part of the configuration data. For detail on database
window, to see if the MML backup and recovery, refer to HUAWEI
commands are all executed MSOFTX3000 Mobile Softswitch Center
successfully. Operation Manual – Routine Operation.
Execute the following commands
The meanings of the commands:
Alarm on and in the MML window:
format SET CWSON: local alarm on/off
4 SET CWSON: SWT=ON;
conversion, SET FMT: format conversion on/off
online SET FMT: STS=ON;
LON: online
LON:;

Modify the The meaning of this command:

Execute the following command
loading modify the loading software switch of a
in the MML window: MOD LSS:
5 software board as “program unavailable, data
PE=NO, DE=NO, DW=YES,
switch of a unavailable, data writable, program
PW=YES;
board writable.”

4-3
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Local Office Commissioning

Step Operation Remarks

It will take quite a long time to execute the
Execute the following commands command FMT. If the system prompts
on the MML window: executing command timeout, select
6 Format data
[System / Command Timeout Setting...] on
FMT:; the LMT client to extend the time-out
setting.

4.4 Loading Board

4.4.1 Preparations for Loading

Table 4-2 Preparations for loading boards

Item Description Result Remarks

On the BAM, double-click the icon in

the taskbar on the lower right corner of
Check the the desktop to display the [BAM Refer to “Checking
running of BAM Manager] window. Check service ‫ ڤ‬Y; ‫ ڤ‬N BAM Software” in
processes processes, including “Exchange” and Chapter 2.
“DataMan”, to see if their statuses are all
“Started”.

Check the Ping the WSMU of each subrack on the Refer to “Checking
communication BAM. If the ping command is executed Communication of
‫ ڤ‬Y; ‫ ڤ‬N
between the successfully, it indicates that the Internal LAN” in
BAM and host communication is normal. Chapter 2.
Refer to “4.2.4
Check the directory “D:\Data\” of the
Check the files Description of Source
BAM to see if the load source files are ‫ ڤ‬Y; ‫ ڤ‬N
loaded Files Related to
there.
Loading”.

4.4.2 Loading Process

I. Operation Steps

Table 4-3 Steps for loading boards

Step Operation Remarks

Set SW4, SW5, and SW6 of the power For the relations between
Power off distribution subrack in the integrated processing cabinet components and
1 all cabinet to “off”; and set SW1–SW6 of the power switches of the power
subracks distribution subrack in the service processing distribution subrack, refer to
cabinet to “off”. Table 4-4.

4-4
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Local Office Commissioning

Step Operation Remarks

Set SW4 of the power distribution subrack in !Caution:
the integrated processing cabinet to “on”, and
2 power on the basic subrack. If the system works At this time, do not set SW5 to
normally, software and data will be “on” for fear that expansion
automatically loaded from the BAM. subrack 1 is powered on.

If there is no loading request,

check the connection of
Ethernet cables and the
>On the BAM, double-click the icon in the
setting of SWIU DIP switches.
taskbar on the lower right corner of the desktop
to open the [BAM Manager] window. Select the !Note:
3 “Exchange” process in the “Service” column. The default setting in the
Click the “Show windows” icon in the toolbar to [Exchange] process window is
Power on open the [Exchange] window. Check if there is not to show loading
the basic any loading request for the basic subrack. information. Refer to the
subrack
MSOFTX3000 Deployment
and start
Guide to modify the setting.
loading
Load the synchronous digital hierarchy map unit Blinking frequency of the
(SMU) first, and then the other front boards, “RUN” indicator for different
excluding the UPWR and wireless alarm unit cases:
4 (WALU). Program loading: 4 Hz;
Observe the green “RUN” indicator on the front Normal running: 0.5 Hz;
board. Its blinking frequency during loading is 4 Standby board indication: 0.25
Hz. Hz.
If the loading fails, find the
After loading, check whether the loading is
remove the fault first. Then go
5 successful by referring to 4.4.3 Checking
on loading the boards in the
Whether Loading Is Successful.
other subracks.
After confirming the basic subrack has been
successfully loaded, set SW5 and SW6 of the
power distribution subrack in the integrated
6 processing cabinet to “on”, and power on
expansion subrack 1. If the system works If there is no loading request,
normally, it will load the software and data check the connection of
Power on automatically from the BAM. Ethernet cables and the
expansion setting of SWIU DIP switches.
subrack 1 Refer to Step 3. Open the [Exchange] process
7
and start window and check if there is any load request. If the loading fails, solve the
loading problem. Go on loading other
Refer to Step 4. Observe the green “RUN” expansion subracks only after
8 indicator on the front board. Its blinking the problem has been solved.
frequency during loading is 4 Hz.
After loading, check whether the loading is
9 successful by referring to 4.4.3 Checking
Whether Loading Is Successful.
Power on
For the relations between
other
Follow the above steps to power on other cabinet components and
expansion
10 expansion subracks and restart them one by switches of the power
subracks
one, and check whether loading is successful. distribution subrack, refer to
and start
Table 4-4.
loading

4-5
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Local Office Commissioning

Caution:

For cases such as failure in loading the boards a subrack, loading the boards of a subrack for several
times or boards of a subrack working abnormally after loaded, timely contact Huawei technicians for help.
Do not change any hardware configuration at will.

II. Description of Switches of Power Distribution Subrack

Table 4-4 Relations between cabinet components and switches of the power distribution subrack

Cabinet type Component Switch

iGWB 0 SW2, SW4
iGWB 1 SW1, SW3
BAM SW3, SW4

Integrated configuration LAN Switch 0 SW3

cabinet LAN Switch 1 SW2
KVM/LCD SW4
Basic subrack 0 SW4, SW5
Expansion subrack 1 SW5, SW6
Expansion subrack 2 SW5, SW6

Service processing Expansion subrack 3 SW3, SW4

cabinet Expansion subrack 4 SW2, SW3
Expansion subrack 5 SW1, SW2

4-6
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Local Office Commissioning

4.4.3 Checking Whether Loading Is Successful

Table 4-5 Checking after loading boards

Item Description Result Remarks

On the LMT client maintenance
console, click the [Management] Relations between board indicator
tab, select [System colors and board running statuses:
Navigator/Device Green: The board is running normally
Management/Device and in the active state.
Management], open the
equipment panel view, and check Blue: The board is running normally and
Check the running of boards. in the standby state.
the Red: The board has fault.
! Note:
running ‫ ڤ‬Y; ‫ ڤ‬N
On the front view of a subrack, Gray: No board has been configured for
of
there are some small squares, this slot.
boards
indicating the statuses of back Also, there are two small squares on the
boards in corresponding slots. To wireless calling control unit and
find detailed information of a back signaling process unit (WCSU), which
board, double-click the triangle on indicates the running of the upper pinch
the left side of the subrack view. A card and lower pinch card on the
subrack status diagram of the back WCSU.
board will be displayed.

If not, run the LST LSS command to

check whether the switches for software
On the LMT client, execute the loading of the board are correctly set,
Check DSP EXVER command to query that is, whether they are set to “program
board the software versions of all boards unavailable”, “data unavailable”, “data
softwar (modules) that can be loaded, and ‫ ڤ‬Y; ‫ ڤ‬N writable”, and “program writable”
e confirm whether they are respectively.
version consistent with the software
version of the BAM. If the switches are not in such statuses,
adjust them accordingly. After that,
reset the board and reload it.

If the check fails, reset the board and

reload it.
On the LMT client, run the !Note:
Verify command STR CRC:MN=255; to It will take quite a long time to execute
board perform the cyclic redundancy ‫ ڤ‬Y; ‫ ڤ‬N the command STR CRC. If the system
data check (CRC) on the data of boards prompts executing command timeout,
(modules) that can be loaded. select [System / Command Timeout
Setting...] on the LMT client to extend
the time-out setting.

4.4.4 Handling of Loading Problems

I. Basic Solution

In most cases, check the following items when problems occur in loading:

4-7
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Local Office Commissioning

z Whether the load path is correct. Whether the physical connection (including
Ethernet cables) is correct, and whether the status of each board under the load
path is normal.
z Whether data configuration is correct. Whether there are errors in critical data
configuration, which may lead to loading failure.
z Whether loading files in the BAM are complete.
z What about software parameters such as the maximum number of tuples.
z Whether the setting of DIP switch S3 of the WSIU is consistent with the subrack
number.
z Does such a case that a board cannot be loaded when you have confirmed that
the load path, data configuration, and DIP switch setting are correct exist? If yes,
perform loading with a replaced board. If loading still fails, it is only possible that
the slot is faulty.

II. Handling of Common Problems

During troubleshooting for board loading, besides observing the board indicator
status, you should pay attention to the information and alarms on the [Exchange]
window of the BAM server, because you may find clues to problems that occur.
1) Failure in loading the WSMU board
For the WSMU, program and data are loaded from the BAM through Ethernet cable.
WSMU loading failure is usually caused by interruption of the communication
between the WSMU and BAM. When failure occurs, an alarm will be generated to
indicate the communication being interrupted.
If the WSMU in slot 6 cannot be loaded, executing commands PING 172.20.subrack
number.100 and PING 172.30.subrack number.100 on the BAM will fail. If the
WSMU in slot 8 cannot be loaded, executing commands PING 172.20.subrack
number.101 and PING 172.30.subrack number.101 on the BAM will fail.
In such cases, check whether the DIP switches of the WSIU that determine the
subrack number are correctly set, and whether Ethernet cables are properly
connected. Also, errors in configuring some critical data may lead to board loading
failure.
2) Failure in loading other boards
Other boards are loaded from the BAM through the WSMU. So if failure occurs in
loading other boards, check whether the WSMU runs normally.

4.5 Clock Commissioning

4-8
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Local Office Commissioning

Note:
The following clock commissioning is unnecessary if no wireless clock interface unit (WCKI) and wireless
E1_pool interface unit (WEPI) are configured for the MSOFTX3000.

4.5.1 Description of Clock System Networking

I. MSOFTX3000 Locking BITS Clocks

If a building integrated timing supply (BITS) device is configured at the office where
the MSOFTX3000 is located, the MSOFTX3000 can introduce the 2-MHz or 2-Mbit/s
clock reference source signal from BITS through a 2M clock cable. The networking is
illustrated in Figure 4-1.
2M clock cable

W W W W
C C E E
BITS BITS K K P P
I I I I
Basic frame (rear view)

8K clock cable

W W W W
E E E E
P P P P
I I I I
Expansion frame A (rear view) Expansion frame B (rear view)

Figure 4-1 Networking for the MSOFTX3000 locking BITS clocks

2) External clock cable and reference source

The MSOFTX3000 introduces the 2-MHz or 2-Mbit/s clock reference source signal
from BITS through a 2M clock cable, connected to BITS1 or BITS2 interface on the
WCKI.
3) Internal clock cable and reference source
z Basic subrack: The WCKI provides a clock, which will be locked by WEPIs
through the backplane bus.
z Extension subrack: One pair of WEPIs (by default, slots 0 and 1) in each
extension subrack is connected to the WCKI in the basic subrack through an
8-Kbit/s clock cable. This pair of WEPIs locks the clock of the WCKI; while other
WEPIs lock the clocks of these two WEPIs through bus on the backplane.

4-9
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Local Office Commissioning

Note:
Usually, you need not set the clock reference source of the WEPI. If the real situation does not conform
to the above specifications, you must run the SET CLKSRC command to set the clock reference source
of the WEPI.

II. MSOFTX3000 Locking Peer Office Clocks

If no BITS clock synchronization device is configured at the office where the

MSOFTX3000 is located, the MSOFTX3000 can only obtain E1 clocks of the peer
office through the WEPI. The networking is shown in Figure 4-2.

2M clock cable

W W W W
C C E E
K K P P
I I I I
Basic frame (rear view)

E1 to peer office
8K clock cable

W W W W
E E E E
P P P P
I I I I
Expansion frame A (rear view) Expansion frame B (rear view)

Figure 4-2 Networking for the MSOFTX3000 locking peer office clocks

1) External clock cable and reference source

The MSOFTX3000 obtains E1 clocks of the peer office through the WEPI, and then
introduces the clock reference source signal to the WCKI through a 2M clock cable,
connected to LINE1 or LINE2 interface of the WCKI.
Only the active WEPI can export 2-MHz clock signals. In Figure 4-2, if the WEPI in slot
0 of the basic subrack is active, the 2-MHz clock cable connecting the WCKI can only
be exported from the WEPI in slot 0 (only two channels can be exported). In the actual
networking, if four WEPIs are configured in the basic subrack, you can introduce four
2-MHz clock signals from two active WEPIs to the active/standby WCKI.
2) Internal clock cable and reference source
z Basic subrack: The WCKI provides a clock, which will be locked by WEPIs
through the backplane bus.

4-10
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Local Office Commissioning

z Extension subrack: One pair of WEPIs (by default, slots 0 and 1) in each
extension subrack is connected to the WCKI in the basic subrack through an
8-Kbit/s clock cable. This pair of WEPIs locks the clock of the WCKI; while other
WEPIs lock the clocks of these two WEPIs through bus on the backplane.

Note:
Usually, you need not set the clock reference source of the WEPI. If the real situation does not conform
to the above specifications, you must run the SET CLKSRC command to set the clock reference source
of the WEPI.

4.5.2 Checking Clock Cable Connection

For detail on the connection of clock cables, refer to HUAWEI MSOFTX3000 Mobile
SoftSwitch Center Installation Manual – Hardware Installation.

Warning:

Before touching any board and plugging/unplugging cables, you must wear an ESD-preventive wrist
strap, which should be properly grounded.

Table 4-6 Checking the connection of clock cables

Item Description Result Remarks

If the MSOFTX3000 locks
If the MSOFTX3000 locks the BITS clock, the the peer office clock, this
2M clock cables outputted from BITS should needs not to be checked.
be respectively connected to sub-miniature B A 2M clock cable is a
‫ ڤ‬Y; ‫ ڤ‬N
(SMB) connectors BITS1 and BITS2, double shielded coaxial
corresponding to the active and standby cable. The cable connector
WCKIs of the basic subrack. is a 75-ohm SMB
Check external connector.
clock cables If the MSOFTX3000 locks
If the MSOFTX3000 locks the peer office the BITS clock, this needs
clock, in the basic subrack, one end of the 2M not to be checked.
clock cable should be connected to LINE1 A 2M clock cable is a
‫ ڤ‬Y; ‫ ڤ‬N
and LINE2 corresponding to the active and double shielded coaxial
standby WCKIs, and the other end, the active cable. The cable connector
WEPI of the basic subrack. is a 75-ohm SMB
connector.

4-11
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Local Office Commissioning

Item Description Result Remarks

The 8k clock cable is a
The 8k clock cables outputted from the active twisted pair cable with
and standby WCKIs of the basic subrack shielded crystal
should be respectively connected to a pair of connectors, like a straight
active and standby WEPIs of each expansion through cable.
Check internal clock
subrack (defaulted as slots 0 and 1). The ‫ ڤ‬Y; ‫ ڤ‬N If the WEPI connected with
cables
8K-A interface of the WEPI is connected to the 8k clock cable is not in
the WCKI in slot 13 of the basic subrack, and slots 0 and 1 of expansion
the 8K-B interface of the WEPI is connected subracks, data needs to be
to the WCKI in slot 15 of the basic subrack. modified using the SET
CLKSRC command.

4.5.3 Commissioning Steps for Locking BITS Clocks

Table 4-7 Commissioning steps for the MSOFTX3000 to lock BITS clocks

Item Operation Remarks

Run the DSP CLKPH command to
check the status of the clock
phase-locked loop circuit of the If the status is “Free Run”, it indicates that the
WCKI. clock phase-locked loop circuit on the WCKI
cannot normally trace the BITS clock.
If the status is “Trace Mode”, it
Check the status of the clock indicates that the clock Then, run the LST CKICFG command to
phase-locked loop circuit of phase-locked loop circuit on the carefully check whether the configuration for
the WCKI WCKI can normally trace the BITS the following parameters is correct: clock level,
clock. work mode, priority of each clock source,
signal type of the BITS1 interface, and signal
!Note:
type of the BITS2 interface.
The phase-locking time of the WCKI
is relatively long, about half an hour.
If the clock status of a WEPI is abnormal,
Run the DSP CLKSTAT command proceed as follows:
to sequentially check the clock
statuses of WEPIs (as clock Run the LST CLKSRC command to check
sources) in expansion subracks to whether the clock reference sources of WEPIs
Check the clock status of the see if they are normal. of each subrack are correctly configured.
WEPI If the clock data is correct, check whether the
!Note:
clock wiring inside the device is correct.
By default, WEPIs in slots 0 and 1 of
each expansion subrack act as If both the clock data configuration and clock
clock sources. wiring are correct, check if WEPIs as clock
sources can work normally.

4-12
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Local Office Commissioning

4.5.4 Commissioning Steps for Locking Peer Office Clocks

Table 4-8 Commissioning steps for the MSOFTX3000 to lock peer office clocks

Item Operation Remarks

Run the DSP PORT command to check
The WEPI can introduce the E1 clock of the
Check the statuses of the status of the E1 port on a WEPI of
peer office only when the E1 port of this office is
E1 ports this office that locks the E1 clock of a
in the “Normal” status.
peer office and see if it is normal.
Run the DSP CLKPH command to
check the status of the clock
phase-locked loop of the WCKI. If the status is “Free Run”, it indicates that the
clock phase-locked loop circuit on the WCKI
If the status is “Trace Mode”, it indicates
Check the status of the cannot normally trace the peer office clock.
that the clock phase-locked loop circuit
clock phase-locked on the WCKI can normally trace the peer Then, run the LST CKICFG command to
loop of the WCKI office clock. carefully check whether the configuration for the
following parameters is correct: clock level, work
!Note:
mode, and priority of each clock source.
The phase-locking time of the WCKI is
relatively long, about half an hour.
If the clock status of a WEPI is abnormal,
Run the DSP CLKSTAT command to proceed as follows:
sequentially check the clock statuses of Run the LST CLKSRC command to check
WEPIs (as clock sources) in expansion whether the clock reference sources of WEPIs
Check the clock status subracks to see if they are normal. of each subrack are correctly configured.
of the WEPI !Note: If the clock data is correct, check whether the
By default, WEPIs in slots 0 and 1 of clock wiring inside the device is correct.
each expansion subrack act as clock If both the clock data configuration and clock
sources. wiring are correct, check if WEPIs as clock
sources can work normally.

4.6 Commissioning of Local Office Hardware

4.6.1 Checking Indicator Status

Table 4-9 Checking the statuses of indicators

Item Description Result Remarks

Normal statuses of the indicators of
Ethernet interfaces:
Whether the power indicators of
The yellow “Link/Active” indicator
LAN Switch 0 and LAN Switch 1
flashes. This indicates that the
are on, and whether the indicators
Check the LAN Switch ‫ ڤ‬Y; ‫ ڤ‬N connection and data sending and
of all Ethernet interfaces that have
receiving are normal.
been properly connected and put
into use are in normal statuses. The green “Speed” indicator is on. This
indicates that the Ethernet interface is
in the 100Mbit/s work mode.

4-13
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Local Office Commissioning

Item Description Result Remarks

If the “RUN” indicator is off, it indicates
Whether the green “RUN” indicator
that there is no power input or the
on the front panel of the power
power distribution subrack is faulty. If
distribution subrack flashes at ‫ ڤ‬Y; ‫ ڤ‬N
the “ALM” indicator is on, it indicates
0.5-Hz rate, and the red “ALM”
Check the power that the power distribution subrack is
indicator is off.
distribution subrack faulty.

Whether the alarm sound stopping If the alarm sound stopping switch is
switch on the front panel of the off, there will be no alarm prompt tone
‫ ڤ‬Y; ‫ ڤ‬N
power distribution subrack is on, when the power distribution subrack is
and the alarm buzzer is silent. faulty.
Whether fans run normally, and
Check fans the green “STATUS” indicator ‫ ڤ‬Y; ‫ ڤ‬N
flashes at 0.5-Hz rate.
If the “RUN” indicator is off, it indicates
that the board is faulty. If it is red, it
Whether the “RUN” indicator on
‫ ڤ‬Y; ‫ ڤ‬N indicates that the communication
the WALU is on.
between the board and the WSMU is in
trouble.

Blinking frequency of the “RUN”

Except on the UPWR and WALU,
indicator for different cases:
Check the indicators on whether the green “RUN”
front boards indicators on the front panels flash, ‫ ڤ‬Y; ‫ ڤ‬N Program loading: 4 Hz;
and the red “ALM” indicators are Normal running: 0.5 Hz;
off.
Standby board indication: 0.25 Hz.
The “LINK” indicator is a network
Whether the green Ethernet port
connection indicator. It is on when the
indicator, “LINK”, on the IP forward ‫ ڤ‬Y; ‫ ڤ‬N
physical connection is normal, and is
module (WIFM) is on.
off in other cases.
Whether the green “RUN” indicator
on the WEPI flashes at 0.5-Hz If the “ALM” indicator flashes, it
‫ ڤ‬Y; ‫ ڤ‬N
rate, and the red “ALM” indicator is indicates that the board is faulty.
Check indicators on off.
back boards Whether the green “RUN” indicator
on the WCKI flashes at 0.5-Hz If the “ALM” indicator is always on, it
‫ ڤ‬Y; ‫ ڤ‬N
rate, and the red “ALM” indicator is indicates that the board is faulty.
off.

4.6.2 Checking the Running of Hardware

Table 4-10 Checking the running of hardware

Item Operation Remarks

Run the DSP ENVSTAT command to
check the statuses of the power
Check the power distribution The statuses should all be “Normal”
distribution subrack, input power,
subrack under normal conditions.
temperature, humidity and the output
switch.

4-14
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Local Office Commissioning

Item Operation Remarks

When the subrack temperature is
Run the DSP FAN command to check the
Check fans above 28°C, the fan speed should be
running of fans.
“High speed”.
They should be “Main OK”, “Standby
Run the DSP FRM command to check the
OK”, “Normal” or Uninstalled” under
statuses of fans.
normal conditions.
Run the DSP BRD command to check the For example:
status of the WALU of each subrack and
the subrack temperature. DSP BRD: FN = 0, SN = 16;

Run the DSP COMM command and select For example:

“TCP” for port type (COMT) to check the
Check boards communication between the WSMU and DSP COMM: FN = 0, SN = 6, COMT =
BAM. TCP;

Usage of each serial port:

Run the DSP COMM command and select 0–16: back boards in corresponding
“SP” for port type (COMT) to check the slots;
communication between the WSMU and
17: WALU;
the serial ports of the back boards, WALU,
fan, and power distribution subrack. 18: fan;
19: power distribution subrack.
Run the DSP PORT command to check Statuses of FE ports (service Ethernet
Check FE ports
the statuses of FE ports. ports) should all be “Normal”.

On the LMT client, use the “PING” function If the returned information is “Reply
to check whether the connection between from *.*.*.* ... time<10ms ...”, it
the WIFM and the default gateway is indicates that the communication is
Check the communication normal. normal.
between the WIFM and the If the time in the returned information
!Note:
default gateway. is too long, or if the returned
The IP address, mask and default gateway information is “Request Timed out”, it
of the WIFM have been defined in the ADD indicates that the communication is
FECFG command. abnormal.

4-15
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Local Office Commissioning

4.6.3 Hardware Switchover Verification

Table 4-11 Operation steps for the verification of hardware switchover

Item Operation Remarks

(1) Run the SWP BRD command to perform switchover for a
front board with active/standby configuration.
(2) Open the equipment panel view of the LMT client to check
the running of the active and standby boards after the
switchover. The active board should be indicated in red, while
the standby in blue.
(3) Observe the board indicators. The frequency of the “RUN” Caution:
indicator of the active board should be 0.5 Hz, and that of the After the initial
Verification of the RUN” indicator of the standby 0.25 Hz. switchover for a board,
active/standby (4) Run the DSP FRM command to check the statuses of the perform switchover again
switchover for the front active and standby boards after the switchover. The status of to restore the original
boards the active board should be “Main OK”, and that of the standby configuration, and at the
board “Standby OK”. same time observe
(5) Run the SWP BRD command again to perform whether the switchover is
active/standby switchover. successful.
(6) Follow Steps 2–4 and observe the statuses of the active and
standby boards after the switchover.
(7) Repeat the above steps to perform switchover for all front
boards with active/standby configuration, and observe whether
the switchover is successful.

4.6.4 Self-Loop Test for Local Office E1 Cables

Note:
The following operations are required only when the WEPI board is configured for the MSOFTX3000.

Warning:

Do not try to change or open any device or connection hardware provided by a telecom operator.
Hardware connection must be done by the telecom operator’s staff or its authorized engineers.

Table 4-12 The self-loop test for E1 cables of the local office

Step Operation Remarks

1 Take out the connectors of the E1 system on the distribution subrack.

4-16
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Local Office Commissioning

Step Operation Remarks

2 Perform local self-loop test on the first E1 with a connector.
Run the DSP PORT command to check the status of the first E1. Its
status should be “Normal”.
3
If not, check the connection of the E1 cable on the distribution
subrack.
When the first E1 is normal, repeat the above steps to perform
4
self-loop test for other E1s and check their statuses.
5 After the test, change all connectors to normal statuses.

4.7 Modifying Settings of Loading Software Switch of Board

When a board runs normally after successful loading, open the MML command
window on the LMT client to run the following command:
MOD LSS: PE=YES, DE=YES, DW=YES, PW=NO;

This command will set the loading software switch of a board as:
z PE=YES (program available): The program will be loaded from the Flash
memory when a board restarts.
z DE=YES (data available): Data will be will be loaded from the Flash memory
when a board restarts.
z DW=YES (data writable): It is allowed to write data into the Flash memory.
z PW=NO (program not writable): It is not allowed to write a program into the Flash
memory.

4.8 Setting Time for the Switch

On the LMT client, open the MML command window to execute the SET TIME
command for setting time for the switch.

Caution:

The error for the time of the switch must not be over ±30 seconds off the local standard time.

4-17
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

Chapter 5 Interconnection Commissioning

5.1 Introduction to This Chapter

This chapter describes data configuration and commissioning for the MSOFTX3000
when it is connected with other devices on the wireless network. The contents include:
z Connecting with the media gateway (MG);
z Connecting with the base station controller (BSC);
z Connecting with home location register (HLR), short message center SMC),
service control point (SCP) and serving GPRS support node (SGSN);
z Connecting with other mobile switching centers (MSC) through ISDN user part
(ISUP) and mobile application part (MAP);
z Connecting with other MSCs through ISUP/M3UA;
z Connecting with other MSCs through bearer independent call control protocol
(BICC);
z Connecting with the radio network controller (RNC).

5.2 Connecting with MG

5.2.1 Description of Relevant Concepts

I. Description of Protocol

The MG cooperates with the MSOFTX3000 to fulfill the mobile switching function of the
core network. Usually, Huawei’s UMG8900 is used as the MG.
The protocol between the MSOFTX3000 and MG is H.248 (Mc interface). Currently,
SCTP/IP bearer is adopted in networking. The protocol stack structure is shown in
Figure 5-1.

5-1
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

MSOFTX3000

H.248/SCTP
H.248
IP
SCTP
IP

UMG8900

Figure 5-1 The protocol stack structure between the MSOFTX3000 and MG

II. Interaction Between MSOFTX3000 and MG

After the MG are started, the MG initiates a registration request to the MSOFTX3000.
The registration will trigger the establishment of an SCTP link. The MSOFTX3000
returns a message indicating the registration is successful. Then the MG can fulfill the
resources management and calling under the control of the MSOFTX3000.

5.2.2 Steps of Commissioning

I. Configuring Online Data

For a newly-deployed office, follow the steps listed in Table 5-1 to perform online data
configuration on the LMT.

Table 5-1 Steps of the configuration of online data

Step Operation Remark

If you cannot log in to the BAM, check
On the LMT, start the client whether the LMT has been registered
Start the LMT program of the MSOFTX3000 with the BAM, whether the username
1
client O&M software, and log in to the and password are correct, and whether
BAM. the cable between LMT and BAM is
properly connected.

Open the MML window and The meanings of the commands:

Enable alarm
execute the following SET CWSON: enable or disable local
function and
commands: alarm function
format
2 SET CWSON: SWT=ON;
conversion SET FMT: enable or disable format
function, and get SET FMT: STS=ON; conversion function
online
LON:; LON: get online

5-2
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

Step Operation Remark

Press shortcut keys <Ctrl + E> to
open the [Execute Batch File]
window, and execute data script
file. For detail on operations on data script
Execute data
3 Upon completing, check the file, refer to “Method for Executing Data
script
“Execution result of” box in the Script” in Chapter 3.
lower part of the window, to see if
the MML commands are all
executed successfully.
If the verification fails, reset the board
and reload it.
On the MML window, run the
command STR CRC: MN=255; It will take quite a long time to execute
Perform CRC on the command STR CRC. If the system
4 to perform CRC on the data of
board data prompts executing command timeout,
boards (modules) that can be
loaded. select [System/Command Timeout
Setting...] on the LMT client to extend
the time-out setting.

II. H.248/SCTP Commissioning

Table 5-2 Steps of the configuration for connecting with the MG through H.248/SCTP

Step Operation Remark

The “LINK” indicator is on when the physical
Observe the indicators on the WIFM. connection is normal, and is off in other cases.
The green Ethernet port connection
indicator “LINK” should be on, while When the “ACT” indicator flashes, it indicates
the yellow Ethernet port data traffic that there is data being sent/received. The
Check the indicator “ACT” should flash. blinking frequency indicates the amount of data
network traffic.
connectio
n On the LMT client, use the interface In case of failure, check whether the Ethernet
tracing function “PING” to check the cables are correctly connected, whether the
communication between the WIFM WIFM works normally, whether devices
and MG. If the ping command is connected with the WIFM (such as a LAN
executed successfully, it indicates Switch) works normally, and whether the MG
that the communication is normal. works normally.

5-3
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

Step Operation Remark

If the display is “Disconnected”, it indicates that
the MG has registered, but currently quits
running. Check whether the data configuration of
the MSOFTX3000 and MG has been modified. If
the data configuration has not been modified, it is
Check the On the LMT client, run the DSP MGW possible that the link communication of the Mc
registratio command to check the registration interface is faulty. Check the SCTP link, analyze
n status of status of gateway. If the display is the interaction of the Mc interface message, and
the “Normal”, it indicates that the take countermeasures.
gateway registration is successful. If the display is “Fault”, it indicates that the MG
has not registered. In this case, run the LST
MGW command to check whether such
parameters as the equipment ID, peer end IP
address, peer end port number and encode type
are correct.
If the SCTP link is abnormal, start the SCTP
message tracing to check whether the message
On the LMT client, run the DSP flow is correct and whether the contents of the
Check the
MCLNK command to check the message is legal. Based on what is shown in the
statuses
status of the SCTP link. If it is “Valid”, message tracing, decide other locating means,
of SCTP
it indicates that the SCTP link is such as checking configured parameters.
links
normal.
Refer to “Treatment of SCTP Common
Problems” in this chapter.

5.2.3 Locating of H.248/SCTP Problems

I. Checking Network Connection

Use the interface tracing function “PING” on the maintenance console to check if the
MG can be pinged successfully. If not, check whether the physical channel is faulty by
observing the Ethernet cable connection, the working of the WIFM and the status of the
Ethernet port indicator of the WIFM. Check whether the MG is normal.

II. Checking Data Configuration

1) Run the LST FECFG command to check whether the interface IP address of the
MSOFTX3000 is consistent with that in the data configuration planning. If not,
modify it.
2) If the MSOFTX3000 is not directly connected with the MG, run the LST FECFG
command to see if the gateway address is correct. You can use the interface
tracing function “TRACERT” to trace the IP path (specify the module number of the
WIFM and the IP address of the MG to check the route passed and find the
location where a packet is lost).
3) Run the LST MCLNK command to check whether the client and server configured
on the two ends of the SCTP connection are consistent with the planned data.
Make sure that one end of the SCTP connection is the client, while the other end is

5-4
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

the server. If both ends are configured as clients or servers, no connection can be
established. Normally, the MSOFTX3000 is configured as the “Server”, while the
MG the “Client”. If they are configured wrongly, run the MOD MGW command to
modify.
4) If the MSOFTX3000 is configured as the SCTP server, it is found, through the
SCTP message tracing function, that the local end receives the “INIT” message,
but it gives no response. First, run the LST SCTPPARA command to check
whether the “Checksum Arithmetic” parameter of the local end is consistent with
that of the remote end. If not, modify it. The default checksum algorithm of the
MSOFTX3000 is “CRC32”. The modification on the MSOFTX3000 side is
implemented through the SET SCTPPARA command.

III. Observing Message Interaction

On the MG side, first run the DEA MGW command to deregister the MG, then run the
ACT MGW command to start the MG. During the starting, the MG will register with the
MSOFTX3000, and accordingly trigger the establishment of the SCTP link. On the LMT
client, use the interface tracing “H248” and “SCTP” function to observe whether the
SCTP message and H248 message interact correctly.
1) H248 message tracing: The MSOFTX3000 receives the “service change request”
message, and then sends the “service change reply” message.
2) SCTP message tracing: The MSOFTX3000 receives the “INIT” message and
returns the “INIT ACK” message. And then it receives the “COOKIE” message and
returns the “COOKIE ACK” message, as shown in Figure 5-2.

Figure 5-2 SCTP message proceeding flow

IV. Querying Status

Table 5-3 Commands for querying H.248/SCTP statuses

Command Function Remark

DSP MGW To query the registration status of MG “Normal” for normal status
DSP MCLNK To query the status of Mc interface link “Valid” for normal status
DSP PORT To query the status of FE port “Normal” for normal status
DSP H248VER To query the version information of H.248 None

5-5
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

5.2.4 Treating SCTP Common Problems

I. No Response from Local End After Receiving “INIT” Message

1) Fault description
When the local end is configured as the SCTP server by an upper level user, it is found,
through the SCTP message tracing function, that the local end receives the INIT
message, but it gives no response.
2) Causal analysis
The problem is caused largely by the disparity of the checksum mode of the local end
with that of the peer end. SCTP supports two checksum modes: ADLER32 and CRC32.
If the SCTP checksum algorithm of the local end is inconsistent with that of the peer
end, the message sent over will be regarded as invalid and therefore be discarded. To
analyze the problem, run the LST SCTPPARA command to see if the checksum
algorithm of the local end is consistent with that of the peer end.
3) Troubleshooting
Modify the checksum algorithm of the local or peer end. To modify the checksum
algorithm of the local end, run the SET SCTPPARA command. Be careful of the effect
of the command on other SCTP connections.

II. Local End Responding with “Abort” Message After Receiving the INIT
Message

1) Fault description
When the local end is configured as the SCTP server by an upper level user, it is found,
through the SCTP message tracing function, that the local end receives the “INIT”
message, but responds with the “Abort” message.
2) Causal analysis
When the local end establishes an interception port but fails, if the SCTP upper level
user provides a maintenance command for querying the server successfully
established, use the command to check whether the server is established successfully.
Failure in establishing an interception port is largely caused by errors in setting
connection parameters, for example, invalid numbers of incoming and outgoing
streams and invalid congestion levels. For details on this information, refer to the error
output messages provided by the upper level user.
3) Troubleshooting
Modify corresponding parameters configured. In most cases, the fault comes from the
inconsistency of the checksum mode of the local end with that of the peer end. Be
careful of the effect of modified parameters on other SCTP connections.

5-6
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

5.3 Connecting with BSC

5.3.1 Description of Relevant Concepts

The MSOFTX3000 is connected with the BSC through BSSAP (A interface) with MTP
bearer. The A interface messages between BSC and MSOFTX3000 are transparently
transmitted through E1 semi-permanent connections (SPC) established on the MG.
The protocol stack is illustrated in Figure 5-3.

MSOFTX3000

BSSAP/MTP
BSSAP
MTP
SCCP
MTP3
MTP2
MTP1
UMG8900

MTP
Trunk (A interface)

BSC

Figure 5-3 Protocol stack between the MSOFTX3000 and BSC

5.3.2 Steps of Commissioning

Note:
Before system commissioning, you must have fulfilled commissioning of clocks of the local office, self-loop
test of E1 cables of the local office, and commissioning for connecting with the MG, and must have
configured the E1 SPC on the MG.

5-7
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

Caution:

Do not try to make changes to or open any device or connected hardware components provided by the
telecom operator by yourself. Operations on hardware connections must be done by the staff of the
telecom operator or engineers authorized by the telecom operator.

Table 5-4 Steps of commissioning for connecting with the BSC through BSSAP/MTP

Item Operation Remark

Configuri
On the LMT client, executethe data script Refer to Section 5.2.2 I. Configuring Online
ng online
file. Data.
data
Before the commissioning of the MTP link,
Checking you must make sure that the clock of the
clock MSOFTX3000 is synchronous with that of Refer to Section 4.5 Clock Commissioning.
status the peer device. If they are not
synchronous, MTP cannot work normally.
Checking
On the LMT client, run the DSP MGW
the
command to check the registration status
registrati Refer to Section 5.2.2 Steps of
of gateway. If “Normal” is displayed, it
on status Commissioning.
indicates the MG has been registered
of
successfully.
gateway

5-8
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

Item Operation Remark

(1) Take out the connectors of all the E1
cables on the distribution frame.
(2) Perform remote self-loop test to the first
E1 cable with the connectors.
(3) The peer office checks whether the first
E1 is normal and notifies the local office of
the result of checking. If this E1 is
abnormal, the peer office records the
number of the E1.
Caution:
(4) Set the connectors to their normal
If it is found during the self-loop test that an
connection states.
E1 is abnormal while the other normal, it
(5) Follow Steps 2–4 to perform remote may be that the two E1s are wrongly
Remote self-loop test to other E1 cables in connected. Such a case must also be
self-loop sequence. recorded down.
test of E1
(6) Notify the peer office and the If an E1 is normal while another E1, which
cables
transmission office of the numbers of E1s was abnormal, becomes normal, it may be
that fail in the self-loop test and are that the two E1s are cross-connected. The
wrongly connected, in order to solve problem can be solved by adjusting the
problems through negotiation among the cables on the cabling rack of the local or
three parties. peer office.
(7) After rearranging those abnormal E1s,
conduct commissioning again in the way
stated above, until all the E1s pass the
remote self-loop test.
(8) On the LMT client of the local office, run
the DSP PORT command to check the
statuses of all E1 ports. If the display is
“Normal”, it indicates the E1 port is normal.
If the status of the link is abnormal, run the
On the LMT client, run the DSP N7LNK or
LST N7LNK command to check whether
DSP N7DLNK command to check the
the configuration of the following
status of the relevant MTP link. If the status
parameters is correct: module number, link
is “In Use, Healthy”, it indicates the link is
type, start circuit number, signaling link
normal.
code and signaling link code sending.

On the LMT client, run the DSP N7DSP

MTP
command to check the status of relevant
commissi If the statuses are abnormal, run the
MTP destination signaling point. If the
oning commands such as LST N7DSP, LST
status is “Accessible”, it indicates that the
status is normal. N7LKS and LST N7RT to check whether
the index relations of the following
On the LMT client, run the DSP N7RT parameters are correct: signaling point
command to check the status of the code, destination signaling point index and
relevant MTP route. If the status is link set index.
“Healthy” and “In Service”, it indicates that
the status is normal.

On the LMT client, run the DSP SCCPDSP

If the status is abnormal, run the LST
SCCP command to check the status of the SCCP
SCCPDSP command to check whether the
commissi remote signaling point. If the status is
parameters such as DPC and OPC are
oning “Allow”, it indicates the SCCP remote
correctly configured.
signaling point is normal.

5-9
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

Item Operation Remark

On the LMT client, run the DSP SCCPSSN
If the status is abnormal, run the LST
command to check the status of the
SCCPSSN command to check whether the
relevant SCCP subsystem. If the status is
parameters such as DPC, OPC and
“Allow”, it indicates the SCCP remote
subsystem code are correctly configured.
signaling point is normal.
Commiss If the status is abnormal, run the commands
ioning of On the LMT client, run the DSP AIETKC or such as LST OFC, LST BSC, LST
A DSP OFTK command to check whether ACPOOL, and LST AIETG to check
interface the status of relevant A interface trunk whether parameters such as the office
trunk circuit is normal. direction, equipment ID, OPC, and DPC are
circuit correctly configured.

5.3.3 Locating MTP Problems

I. Message Tracing

The interface tracing function “MTP3” provided by the system is an important means of
locating MTP problems. It can trace MTP upper layer user messages, test messages
and route management messages as well as commands between the second layer and
third layer of MTP. The results of MTP message tracing is displayed in Figure 5-4.

Figure 5-4 Results of MTP message tracing

In Figure 5-4, the mark “>” (black) in the front of a message indicates an MTP message
received from a link; the mark "<” (blue) in the front of a message indicates an MTP
message sent from a link. To view the detailed description of the contents of a message,
select the message and press <Enter> or right-click the message.

5-10
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

II. Querying Status

Table 5-5 Commands for querying MTP statuses

Command Function Remark

DSP N7LNK
To the query status of the MTP “In Use, Healthy” indicates the status is
DSP N7DLNK
link normal.
DSP N7LSLNK
To query the status of the MTP
DSP N7DSP “Accessible” indicates the status is normal.
destination signaling point
To query the status of the MTP “Healthy, In Service” indicates the status is
DSP N7RT
route normal.
To query the status of
DSP COMM “Normal” indicates the status is normal.
communication between boards
To query the status of the E1
DSP PORT “Normal” indicates the status is normal.
port

III. Self-Loop Test

Table 5-6 Commands for self-loop test

Command Function Remark

STR MTP2LNKLB To start MTP2 self-loop These commands are used for MTP link software
self-loop to test whether the sending and receiving
STP MTP2LNKLB To stop MTP2 self-loop of the link are normal.
After the self-loop command is sent, if there are
To query the status of test messages observed being sent/received from
DSP MTP2LNKLB
MTP2 self-loop the link tracing window, it indicates that the
sending and receiving of the local link are normal.
STR PORTLOP To start E1 port self-loop These commands are used for E1 port self-loop to
test whether the sending and receiving of bottom
STP PORTLOP To stop E1 port self-loop hardware messages are normal.

5.3.4 Locating SCCP/TCAP Problems

I. Message Tracing

The SCCP and TCAP modules provide a number of interface tracing functions, as
shown in Table 5-7. If any problem occurs, enable the tracing function of every layer.
This will quickly locate the layer where the message is lost or returned. Every message
tracing function has message explanations. You can easily understand why the
message is faulty or returned.

5-11
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

Table 5-7 SCCP message tracing

Message tracing
Description
function
To trace the interactive messages between the SCCP of the specified signaling
SCCP DPC point and the bottom layer.
The signaling point is determined by the input parameters NI, DPC and OPC.
To trace the primitive for interacting between SCCP and the users above SCCP
SCCP User
(for example, TCAP, BSSAP and RANAP)

To trace the management primitive sent from the bottom layer to SCCP, including
SCCP MTP MG
signaling point prohibition and allowing.
TCAP SCCP To trace the primitive for interacting between TCAP and SCCP.
TCAP User To trace the primitive for interacting between TCAP and the upper layer users.

II. Querying Status

Table 5-8 Commands for querying SCCP statuses

Command Function Remark

“Allow” indicates that the communication of the
To query the status of the
signaling point is normal. “Prohibit” indicates that
DSP SCCPDSP SCCP destination
the communication of the signaling point is
signaling point
interrupted and the signaling point is not reachable.
“Allow” indicates that the communication of the
To query the status of the subsystem is normal. “Prohibit” indicates that the
DSP SCCPSSN
SCCP subsystem communication of the subsystem is interrupted and
the subsystem is not reachable.
Contents of the test results:
GT Index;
GT Matching Length;
To test the translation of GT Matching Content;
SCCP GT and check Translating Result Type, including SPC+old GT,
whether the configured SPC+SSN, SPC+new GT and SPC;
TST SCCPGT
SCCP GT can be NI: network identification;
translated to the desirable
results. SPC: signaling point code;
SSN: subsystem number, which exists the the
translating result type is SPC+SSN;
New GT: new GT code, which exists when the
translating result type is SPC+new GT.

5-12
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

5.4 Connecting with HLR, SMC, SCP and SGSN

5.4.1 Description of Relevant Concepts

I. Connecting with HLR and SMC through MAP/MTP

The MSOFTX3000 is connected with the HLR through MAP (C/D interface), and with
the SMC through MAP (E interface). MTP link bearer is usually used in current
networking. The protocol stack is illustrated in Figure 5-5.

HLR SMC

MAP/MTP MAP/MTP
M

MAP TP MAP
TP

M
TCAP TCAP
SCCP SCCP
MTP3 MTP3
MTP2 MTP2
MTP1 MSOFTX3000 MTP1

Figure 5-5 Structure of the protocol stack between the MSOFTX3000 and HLR/SMC

II. Connecting with SCP through CAP/MTP

The MSOFTX3000 is connected with the SCP through CAP. The SCP is the database
entity. It is transferred through the signaling access unit (SAU), the front end processor
of the SCP, rather than directly connected with MSOFTX3000. MTP link bearer is
usually used in current networking. The protocol stack is illustrated in Figure 5-6.

5-13
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

SAU SCP

CAP/MTP
MTP CAP
TCAP
SCCP
MTP3
MTP2
MTP1

MSOFTX3000

Figure 5-6 Structure of the protocol stack between the MSOFTX3000 and SCP

III. Connecting with SGSN through BSSAP+/MTP

The MSOFTX3000 is connected with the SGSN through BSSAP+protocol (Gs

interface). MTP link bearer is usually used in current networking. The protocol stack is
illustrated in Figure 5-7.

MSOFTX3000 SGSN

MTP

BSSAP+/MTP
BSSAP+
SCCP
MTP3
MTP2
MTP1

Figure 5-7 Structure of the protocol stack between the MSOFTX3000 and SGSN

5.4.2 Steps of Commissioning

Note:
Before system commissioning, you must have fulfilled commissioning of clocks of the local office and
self-loop test of E1 cables of the local office.

5-14
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

Warning:

Do not try to make changes to or open any device or connected hardware components provided by the
telecom operator by yourself. Operations on hardware connections must be done by the staff of the
telecom operator or engineers authorized by the telecom operator.

Table 5-9 Steps of commissioning for connecting with HLR/SMC/SCP/SGSN

Item Operation Remark

Configuri
On the LMT client, execute the data Refer to Section 5.2.2 I. Configuring Online
ng online
script file. Data.
data
Before the commissioning of the MTP
link, you must make sure that the
Checking
clock of the MSOFTX3000 is
clock Refer to Section 4.5 “Clock Commissioning”.
synchronous with that of the peer
status
device. If they are not synchronous,
MTP cannot work normally.
(1) Take out the connectors of all the
E1 cables on the distribution frame.
(2) Perform remote self-loop test to
the first E1 cable with the connectors.
(3) The peer office checks whether
the first E1 is normal and notifies the
local office of the result of checking. If
this E1 is abnormal, the peer office
records the number of the E1.
(4) Set the connectors to their normal
connection states. Caution:
(5) Follow Steps 2–4 to perform If it is found during the self-loop test that an E1 is
remote self-loop test to other E1 abnormal while the other normal, it may be that
Remote the two E1s are wrongly connected. Such a case
self-loop cables in sequence.
must also be recorded down.
test of E1 (6) Notify the peer office and the
cables transmission office of the numbers of If an E1 is normal while another E1, which was
E1s that fail in the self-loop test and abnormal, becomes normal, it may be that the
are wrongly connected, in order to two E1s are cross-connected. The problem can
solve problems through negotiation be solved by adjusting the cables on the power
among the three parties. distribution subrack of the local or peer office.
(7) After rearranging those abnormal
E1s, conduct commissioning again in
the way stated above, until all the E1s
pass the remote self-loop test.
(8) On the LMT client of the local
office, run the DSP PORT command
to check the statuses of all E1 ports. If
the display is “Normal”, it indicates the
E1 port is normal.

5-15
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

Item Operation Remark

On the LMT client, run the DSP If the status of the link is abnormal, run the LST
N7LNK or DSP N7DLNK command N7LNK command to check whether the
to check the status of the relevant configuration of the following parameters is
MTP link. If the status is “In Use, correct: module number, link type, start circuit
Healthy”, it indicates the link is number, signaling link code and signaling link
normal. code sending.

On the LMT client, run the DSP

MTP N7DSP command to check the status
commissi of the relevant MTP destination
oning signaling point. If the status is If the statuses are abnormal, run the commands
“Accessible”, it indicates that the such as LST N7DSP, LST N7LKS and LST
status is normal. N7RT to check whether the index relations of the
following parameters are correct: signaling point
On the LMT client, run the DSP N7RT code, destination signaling point index and link
command to check the status of the set index.
relevant MTP route. If the status is
“Healthy” and “In Service”, it indicates
that the status is normal.
On the LMT client, run the DSP
SCCPDSP command to check the
If the status is abnormal, run the LST SCCPDSP
status of the SCCP remote signaling
command to check whether the parameters such
point. If the status is “Allow”, it
as DPC and OPC are correctly configured.
indicates the SCCP remote signaling
point is normal.
SCCP On the LMT client, run the DSP
commissi SCCPSSN command to check the If the status is abnormal, run the LST SCCPSSN
oning status of the relevant SCCP command to check whether the parameters such
subsystem. If the status is “Allow”, it as DPC, OPC and subsystem code are correctly
indicates the SCCP remote signaling configured.
point is normal.
On the LMT client, run the TST If not correct, run the LST SCCPGT command to
SCCPGT command to check whether check wheterh parameters are correctly
the translation of SCCP GT is correct. configured.

5.4.3 Locating and Treating Problems

Refer to Section 5.3.3 Locating MTP Problems and Section 5.3.4 Locating
SCCP/TCAP Problems”.

5.5 Connecting with MSC through ISUP & MAP/MTP

5.5.1 Description of Relevant Concepts

The MSOFTX3000 is connected with other MSCs through ISUP/MAP over MTP link
bearer. An E1 SPC will be established on the MG for transparently transmit ISUP and
MAP messages. The protocol stack is illustrated in Figure 5-8.

5-16
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

MSOFTX3000 MSC

k
un
ISUP&MAP/MTP ISUP&MAP/MTP

Tr
TP

TP
MAP MAP

M
ISUP ISUP
TCAP TCAP
SCCP SCCP
MTP3 MTP3
MTP2 MTP2
MTP1 MTP1
UMG8900

Figure 5-8 Structure of ISUP & MAP/MTP protocol stack

5.5.2 Steps of Commissioning

Note:
Before system commissioning, you must have fulfilled commissioning of clocks of the local office, self-loop
test of E1 cables of the local office, and commissioning for connecting with the MG, and must have
configured the E1 SPC on the MG.

Warning:

Do not try to make changes to or open any device or connected hardware components provided by the
telecom operator by yourself. Operations on hardware connections must be done by the staff of the
telecom operator or engineers authorized by the telecom operator.

Table 5-10 Steps of commissioning for connecting with MSC through ISUP & MAP/MTP

Item Operation Remark

Configuri
On the LMT client, execute the data Refer to Section 5.2.2 I. Configuring Online
ng online
script file. Data.
data

5-17
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

Item Operation Remark

Before the commissioning of the MTP
link, you must make sure that the
Checking
clock of the MSOFTX3000 is
clock Refer to Section 4.5 “Clock Commissioning”.
synchronous with that of the peer
status
device. If they are not synchronous,
MTP cannot work normally.

Checking
On the LMT client, run the DSP MGW
the
command to check the registration
registrati
status of gateway. If “Normal” is Refer to Section 5.2.2 Steps of Commissioning.
on status
displayed, it indicates the MG has
of
been registered successfully.
gateway
(1) Take out the connectors of all the
E1 cables on the distribution frame.
(2) Perform remote self-loop test to
the first E1 cable with the connectors.
(3) The peer office checks whether
the first E1 is normal and notifies the
local office of the result of checking. If
this E1 is abnormal, the peer office
records the number of the E1.
(4) Set the connectors to their normal
connection states. Caution:
(5) Follow Steps 2–4 to perform If it is found during the self-loop test that an E1 is
remote self-loop test to other E1 abnormal while the other normal, it may be that
Remote the two E1s are wrongly connected. Such a case
self-loop cables in sequence.
must also be recorded down.
test of E1 (6) Notify the peer office and the
cables transmission office of the numbers of If an E1 is normal while another E1, which was
E1s that fail in the self-loop test and abnormal, becomes normal, it may be that the
are wrongly connected, in order to two E1s are cross-connected. The problem can
solve problems through negotiation be solved by adjusting the cables on the power
among the three parties. distribution subrack of the local or peer office.
(7) After rearranging those abnormal
E1s, conduct commissioning again in
the way stated above, until all the E1s
pass the remote self-loop test.
(8) On the LMT client of the local
office, run the DSP PORT command
to check the statuses of all E1 ports. If
the display is “Normal”, it indicates the
E1 port is normal.
On the LMT client, run the DSP If the status of the link is abnormal, run the LST
N7LNK or DSP N7DLNK command N7LNK command to check whether the
MTP
to check the status of the relevant configuration of the following parameters is
commissi
MTP link. If the status is “In Use, correct: module number, link type, start circuit
oning
Healthy”, it indicates the link is number, signaling link code and signaling link
normal. code sending.

5-18
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

Item Operation Remark

On the LMT client, run the DSP
N7DSP command to check the status
of the relevant MTP destination
signaling point. If the status is If the statuses are abnormal, run the commands
“Accessible”, it indicates that the such as LST N7DSP, LST N7LKS and LST
status is normal. N7RT to check whether the index relations of the
following parameters are correct: signaling point
On the LMT client, run the DSP N7RT code, destination signaling point index and link
command to check the status of the set index.
relevant MTP route. If the status is
“Healthy” and “In Service”, it indicates
that the status is normal.
On the LMT client, run the DSP
SCCPDSP command to check the
If the status is abnormal, run the LST SCCPDSP
status of the SCCP remote signaling
command to check whether the parameters such
point. If the status is “Allow”, it
as DPC and OPC are correctly configured.
indicates the SCCP remote signaling
point is normal.
SCCP On the LMT client, run the DSP
commissi SCCPSSN command to check the If the status is abnormal, run the LST SCCPSSN
oning status of the relevant SCCP command to check whether the parameters such
subsystem. If the status is “Allow”, it as DPC, OPC and subsystem code are correctly
indicates the SCCP remote signaling configured.
point is normal.
On the LMT client, run the TST If not correct, run the LST SCCPGT command to
SCCPGT command to check whether check wheterh parameters are correctly
the translation of SCCP GT is correct. configured.

Checking
If the status is abnormal, run commands such as
the status On the LMT client, run the command
LST TG and LST TKC to check whether the
of the DSP OFTK or DSP N7TKC to check
following parameters are correctly configured:
SS7 whether the status of the SS7 trunk
equipment ID, OPC, DPC, start CIC and terminal
trunk circuit is normal.
endpoint ID.
circuit

5.5.3 Locating and Treating Problems

Refer to Section 5.3.3 Locating MTP Problems and Section 5.3.4 Locating
SCCP/TCAP Problems.

5.6 Connecting with MSC through ISUP/M3UA

5.6.1 Description of Relevant Concepts

I. Description of Networking

When the MSOFTX3000 interconnects with other MSCs using the ISUP signaling, the
signaling gateway (SG) embedded in the UMG8900 is used. Between the UMG8900

5-19
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

and MSOFTX3000, M3UA protocol over IP/SCTP is used. The UMG8900 is connected
with other MSCs through ISUP signaling over time division multiplexing (TDM).
MSOFTX3000 TMSC/GMSC

ISUP/M3UA ISUP/MTP

ISUP ISUP

k
un
MTP3

Tr
IP
M3UA

TP
M
SCTP MTP2
IP MTP1

M3UA MTP3
SCTP MTP2
IP MTP1
UMG8900 (SG)

Figure 5-9 Structure of the ISUP/M3UA protocol stack

II. Basic Concept of SG

The SG is a signaling agent, mostly doing the interpretation of switched circuit network
(SCN) signaling to IP signaling and the termination at IP signaling.

III. SCTP Association in Client/Server Work Mode

Since M3UA protocol adopts SCTP as its transmission layer, while SCTP association
works in the Client/Server mode, the user is required to specify the work mode for each
device in SCTP association to ensure that M3UA protocol can work normally.

IV. Peer/Non-Peer Networking with M3UA

For two signaling devices using M3UA protocol in communication, if one end is in the
application server (AS) mode, while the other end the SG mode, the networking is
called non-peer networking; if both ends are in the AS mode or SG mode, however, the
networking is called peer networking.

V. Four Parameters Identifying SCTP Association

In M3UA protocol, the local end IP address, local end port number, peer end IP address
and peer end port number are four parameters used for uniquely identifying an SCTP
association. Therefore, the following principle should be observed while adding M3UA
links:
1) The local end IP address, local end port number, peer end IP address and peer
end port number are data for interconnection of M3UA protocol. They should be
negotiated for consistency.

5-20
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

2) After the local end IP address and peer end IP address have been determined,
links between the two signaling devices will be determined by the local end port
number and the peer end port number. In other words, if the peer end port
numbers used by links are the same, the local end port numbers should not be in
duplicate. And this is true conversely.
3) If the MSOFTX3000 is the server of M3UA protocol, it is recommended that all
links use the same local end port number with no identical peer end port numbers.
This requires uniform planning.
4) If the MSOFTX3000 is the client of M3UA protocol, it is recommended that all links
use the same peer end port number with no identical local end port numbers. This
requires uniform planning.

VI. M3UA Local Entity and Destination Entity

The M3UA local entity and destination entity can be regarded as the mirroring of the
local office signaling points (SP) and destination SPs of SS7 signaling in M3UA protocol.
And the adjacent destination entity and non-adjacent destination entity and other
concepts can be regarded as the extension of such concepts of SS7 signaling in M3UA
protocol. Therefore, the data configuration for M3UA protocol resembles that for
message transfer part (MTP).

5.6.2 Steps of Commissioning

Table 5-11 Steps of commissioning for connecting with MSC through ISUP/M3UA

Step Operation Remark

Configuri
On the LMT client, execute the data Refer to Section 5.2.2 I. Configuring Online
ng online
script file. Data.
data
The “LINK” indicator is on when the physical
Observe the indicators on the WIFM. connection is normal, and is off in other cases.
The green Ethernet port connection
indicator, “LINK”, should be on, while When the “ACT” indicator flashes, it indicates
the yellow Ethernet port data traffic that there is data being sent/received. The
Check blinking frequency indicates the amount of data
the indicator, “ACT”, should flash.
traffic.
network
connectio On the LMT client, use the interface In case of failure, check whether the Ethernet
n tracing function “PING” to check the cables are correctly connected, whether the
communication between the WIFM WIFM works normally, whether devices
and UMG8900. If the ping command connected with the WIFM (such as a LAN
is executed successfully, it indicates Switch) works normally, and whether the
that the communication is normal. UMG8900 works normally.
Check
On the LMT client, run the DSP MGW
the status
command to check the status of
of
gateway registration. If the display is Refer to Section 5.2.2 “Steps of Commissioning”.
gateway
“Normal”, it indicates that the
registrati
UMG8900 registers successfully.
on

5-21
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

Step Operation Remark

On the LMT client, run the DSP
M3LNK command to check the
statuses of relevant M3UA links. If
they are “Active”, it indicates that the
links are normal. If the statuses are abnormal, first run the LST
M3LKS command to check whether the
On the LMT client, run the DSP transmission mode of the link set is correctly
M3LKS command to check the status configured. Then, use the LST M3LNK
of the M3UA link set. If they are command to check whether the following
“Active”, it indicates that the links are parameters are correct: the local end port
M3UA normal. number, local end IP address, peer end port
commissi number, peer end IP address, and C/S work
oning On the LMT client, run the DSP M3DE mode.
command to check the status of the
M3UA destination entity. If the display
is “Accessible”, it indicates that the
status is normal.
If the statuses are abnormal, use commands
On the LMT client, run the DSP M3RT LST M3LE, LST M3DE and LST M3LKS to
command to check the statuses of check whether such parameters as the local
relevant M3UA routes. entity index, destination entity index and link set
index have correct relations.
Check
If the statuses are abnormal, use commands like
the
On the LMT client, run the DSP OFTK LST TG and LST TKC to check whether the
statuses
or N7TKC command to check the following parameters are correct: the equipment
of SS7
statuses of relevant SS7 signaling ID, origination point code (OPC), destination
signaling
trunk circuits. point code (DPC), start circuit identification code
trunk
(CIC), and start circuit terminal ID.
circuits

5.6.3 Locating M3UA Problems

I. Most of the problems in M3UA are due to human factors, including errors in
data configuration and manually deactivating an M3UA link. Checking
Network Connection

Use the interface tracing function “PING” on the console to check whether the peer
device can be pinged successfully. If the peer device cannot be pinged through, check
whether physical connections are normal, including the connection of the Ethernet
cable, the running of the WIFM, the status of the Ethernet port of the WIFM and the
running of the peer device.

II. Checking Data Configuration

1) Run the LST FECFG command to check whether the IP address of the interface of
the MSOFTX3000 is consistent with that in the planned data. If not, modify the IP
address accordingly.

5-22
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

2) If the MSOFTX3000 is not directly connected with the peer device, use the LST
FECFG command to check whether the address of the gateway is correctly
configured. You can use the interface tracing function “TRACERT” to trace IP
packets (specify the module number of the WIFM and the IP address of the peer
device to check the route of packets, so as to identify locations where packets are
lost).
3) Use the LST M3LNK command to check whether such parameters as the local
port number, local IP address, remote port number, remote IP address, and C/S
work mode are correctly configured.
4) Run the LST M3LE, LST M3DE and LST M3LKS commands to check whether
such parameters as the local entity index, destination entity index and link set
index are correctly configured.

III. Tracing Messages

Enable a message tracing function such as M3UA message tracing or SCTP message
tracing to check whether a message flow is correct. As shown in Figure 5-10, a normal
M3UA message proceeding flow is as follows:
z SCTP reports “UP”;
z Application Service Party (ASP) sends “ASP UP “ to the SG, and the SG responds
“ASP UP ACK”;
z The ASP sends “ASP ACTIVE” to the SG, and the SG responds “ASP ACTIVE
ACK”, until now, the M3UA link is activated.

Figure 5-10 M3UA message proceeding flow

IV. Viewing Alarm Information

Query relative alarm and maintenance information on the maintenance console.

V. Querying Status

Table 5-12 Commands for querying M3UA statuses

Command Function Remark

DSP M3LNK To query the status of the M3UA link “Active” indicates the normal status.
DSP M3DLNK

5-23
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

Command Function Remark

DSP M3LSLNK
DSP M3LKS To query the status of the M3UA link set “Active” indicates the normal status.
To query the status of the M3UA “Accessible” indicates the normal
DSP M3DE
destination entity status.
DSP M3RT To query the status of the M3UA route None
To query the version information of
DSP M3VER None
M3UA

5.6.4 Treating M3UA Common Problems

I. M3UA Link Status Displayed as “Link Unestablished”

1) Fault description
The M3UA link cannot be established. The status of the M3UA link is displayed as “Link
Unestablished".
2) Causal analysis
Cause 1: Data configuration errors exist. Mainly check the following parameters: the
parameter route context in the ADD M3LE command, service mode in ADD M3LKS,
C/S mode in ADD M3LNK, local end IP address, peer end IP address, local end port
number and peer end port number.
Cause 2: Check whether an M3UA link has been removed manually on the client, as
shown below:
%%DSP M3LNK: MN=133, M3LNK=0,CONFIRM=Y;%%
RETCODE = 0 Operation succeeded

M3UA Link Status

----------------
Module Number = 133
Link Number = 0
SCTP Association ID = 4294967295
Lock Information = Unlocked
Local Inactive Info = Link Not Inactivated Manually
Local Release Info = Release Ungracefully
Link Congestion Info = Not Congested
Real In Stream Num = 0
Real Out Stream Num = 0
Status = Link Unestablished.

5-24
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

If “Local Release Info” is “Release Ungracefully” or “Release Gracefully”, it indicates

that an M3UA link has been removed manually.
Cause 3: The inability of SCTP to work normally causes the status of M3UA to be “Link
Unestablished”. For detail, refer to Section 5.2.4.
3) Troubleshooting
For Cause 1, modify data configuration on the two ends.
For Cause 2, run the EST M3LNK command on the client to manually establish M3UA
links, as shown below:
%%EST M3LNK: MN=133, M3LNK=0,CONFIRM=Y;%%
RETCODE = 0 Operation succeeded

For Cause 3, refer to Section 5.2.4.

II. M3UA Link Status Displayed as “Link DOWN”

1) Fault description
The M3UA link can be established. But on the ASP side, the status of the M3UA link is
displayed as “Link DOWN".

2) Causal analysis
Cause 1: Whether to lock relevant M3UA links on the SG side, as shown below:
%%DSP M3LNK: MN=132, M3LNK=0,CONFIRM=Y;%%
RETCODE = 0 Operation succeeded

M3UA Link Status

-------------------------
Module Number = 133
Link Number = 0
SCTP Association ID = 101
Lock Information = Locked
Local Inactive Info = Link Not Inactivated Manually
Local Release Info = Link Not Released Manually
Link Congestion Info = Not Congested
Real In Stream Num = 0
Real Out Stream Num = 0
Status = Link Down.

Cause 2: The status of the SG is not consistent with that of the AS, for example, the
status on the ASP is “Link Active”, and that of the signaling gateway part (SGP) “is Link
Down”.
3) Troubleshooting

5-25
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

For Cause 1, manually remove the locking to M3UA links using the command ULK
M3LNK on the SG side, as shown below:
%%ULK M3LNK: MN=133, M3LNK=0,CONFIRM=Y;%%
RETCODE = 0 Operation succeeded

For Cause 2, first manually remove the M3UA links on the client side, and then
re-establish, as shown below:
%%REL M3LNK: MN=133, M3LNK=0,CONFIRM=Y;%%
RETCODE = 0 Operation succeeded

%%EST M3LNK: MN=133, M3LNK=0,CONFIRM=Y;%%

RETCODE = 0 Operation succeeded

III. M3UA Link Status Displayed as “Link Inactive”

1) Fault description
The M3UA link can be established, but cannot be activated. The status of M3UA link is
displayed as “Link Inactive".

2) Causal analysis
Cause 1: Data configuration errors exist on both sides. Mainly check the following
parameters: the parameter route context in the ADD M3LE command, service mode in
ADD M3LKS, C/S mode in ADD M3LNK, local end IP address, peer end IP address,
local end port number and peer end port number. At the same time, enable the M3UA
message tracing function to check the message flow, and locate problems with
reference to the error cause in the error message.
Cause 2: Check whether an M3UA link has been deactivated manually on the ASP side,
as shown below:
%%DSP M3LNK: MN=132, M3LNK=0,CONFIRM=Y;%%
RETCODE = 0 Operation succeeded

M3UA Link Status

-------------------------
Module Number = 132
Link Number = 0
SCTP Association ID = 108
Lock Information = Unlocked
Local Inactive Info = Link Inactivated Manually
Local Release Info = Link Not Released Manually
Link Congestion Info = Not Congested
Real In Stream Num = 17
Real Out Stream Num = 17

5-26
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

Status = Link Inactive

3) Troubleshooting
For Cause 1, modify data configuration on both ends according to the error code type in
the error message.
If the error code is “Invalid Routing Context”, it indicates that the route contexts of the
two ends are inconsistent. Then modify and make them consistent.
If the error code is “Unsupported Traffic Handling Mode”, it indicates that the service
modes of the two ends are inconsistent. Then modify the service modes in link set
tables to keep consistent.
For Cause 2, manually activate M3UA links with the command ACT M3LNK on the
ASP side, as shown below:
%%ACT M3LNK: MN=132, M3LNK=0,CONFIRM=Y;%%
RETCODE = 0 Operation succeeded

5.7 Connecting with MSC through BICC/SCTP

5.7.1 Description of Protocol

I. Description of Networking and Interface Protocol

Between the MSOFTX3000 and MSC, as the peer end, Bearer Independent Call
Control Protocol (BICC) signaling is adopted with the bearer mode as SCTP/IP. Figure
5-11 illustrates the networking with interface protocols under the BICC message
transmission mode.

MSOFTX3000 MSOFTX3000

IP

BICC/SCTP
BICC
SCTP
IP
IP IP

Trunk (BICC)

UMG8900 UMG8900

Figure 5-11 Structure of the BICC/SCTP protocol stack

5-27
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

II. Introduction to BICC

BICC is developed from ISUP protocol. Its basic feature lies in the separation of call
control from bearer control, making the call service function (CSF) and bearer control
function (BCF) independent of each other.
1) Office direction
This is identical with the concept in ISUP signaling.
2) Route, subroute and load sharing
This is identical with the concept in ISUP signaling.
3) Route selection code, route selection source code
This is identical with the concept in ISUP signaling.
4) BICC trunk group
The BICC trunk group is not a collection of circuit identification codes or circuits, but
only an MG for selecting BICC signaling control. In the BICC trunk group table, a field,
“MGW Index”, is added.
5) BICC CIC
BICC is a protocol with the call and bearer separated. Here, the concept of CIC differs
from that of ISUP. CIC of BICC just identifies a call, so it is called a call instance code. It
does not correspond to the bearer resources controlled.
The BICC CIC module table contains all the CIC resources to an office direction. For
each call, a CIC will be selected from the table according to the office direction.

III. Basic Concept of Dual Homing

1) Mutual aid function: In the system are exchange office A and exchange office B.
When B is faulty, A can take over part or all services of B. In this case, it is
regarded that exchange office A has the mutual aid function.
2) Mutual aid active state: When exchange office A has the mutual aid function, and it
has taken over the service control of exchange office B which enjoys the aid of A,
it is regarded to be in the mutual aid active state.
Mutual aid inactive state: When exchange office A has the mutual aid function, but it
has not taken over the service control of exchange office B which enjoys the aid of A, it
is regarded to be in the mutual aid inactive state.

5-28
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

5.7.2 Steps of Commissioning

I. Steps of BICC Commissioning (Independent Work Mode)

Table 5-13 Steps of the BICC commissioning (independent work mode)

Step Operation Remark

Configuri
On the LMT client, execute the data
ng online Refer to Section 5.2.2 I. Configuring Online Data.
script file.
data
Observe the indicators on the The “LINK” indicator is on when the physical
WIFM. The green Ethernet port connection is normal, and is off in other cases.
connection indicator, “LINK”, should
be on, while the yellow Ethernet port When the “ACT” indicator flashes, it indicates that
data traffic indicator, “ACT”, should there is data being sent/received. The blinking
Check frequency indicates the amount of data traffic.
the flash.
network On the LMT client, use the interface
connectio In case of failure, check whether the Ethernet
tracing function “PING” to check the
n cables are correctly connected, whether the WIFM
communication between the WIFM
works normally, whether devices connected with
and the peer MSC. If the ping
the WIFM (such as a router) works normally,
command is executed successfully,
whether route data is correctly configured, and
it indicates that the communication
whether the peer MSC works normally.
is normal.

Check
On the LMT client, run the DSP
the status
MGW command to check the status
of
of gateway registration. If the display Refer to Section 5.2.2 “Steps of Commissioning".
gateway
is “Normal”, it indicates that the
registrati
gateway registers successfully.
on
If the statuses are abnormal, run the LST
BICCSCTPLNK command to check whether
BICC SCTP links are correctly configured,
including the following parameters: the module
number, link number, office direction, local end
On the LMT client, run the DSP port number, local end IP address, peer end port
BSCTP command to check the number, peer end IP address, and C/S work
statuses of relevant BICC SCTP mode.
links. If they are “Active”, it indicates
BICC If data configuration for the local office has no
that the links are normal.
commissi problem, check whether data of the peer MSC is
oning correctly configured.
If the data configuration of the peer MSC also has
no problem, run the ACT BSCTP command to
activate BICC SCTP links.

If the statuses are abnormal, run the command

On the LMT client, run the command
LST BICCCICMDU to check whether the
DSP BICCCIC or DSP BICCOFC to
parameters such as the office direction, module
check the statuses of relevant BICC
number, start CIC, and CIC transformation mode
CICs.
are correct.

5-29
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

II. Steps of BICC Commissioning (Mutual Aid Work Mode)

Table 5-14 Steps of the BICC commissioning (mutual aid work mode)

Step Operation Remark

Configuring On the LMT client, execute the data Refer to Section 5.2.2 I. Configuring
online data script file. Online Data.
The “LINK” indicator is on when the
Observe the indicators on the WIFM. physical connection is normal, and is off in
The green Ethernet port connection other cases.
indicator, “LINK”, should be on, while the When the “ACT” indicator flashes, it
yellow Ethernet port data traffic indicator, indicates that there is data being
“ACT”, should flash. sent/received. The blinking frequency
Check the indicates the amount of data traffic.
network
connection In case of failure, check whether the
On the LMT client, use the interface Ethernet cables are correctly connected,
tracing function “PING” to check the whether the WIFM works normally,
communication between the WIFM and whether the device connected with the
the peer MSC. If the ping command is WIFM (such as a router) works normally,
executed successfully, it indicates that whether route data is correctly configured,
the communication is normal. and whether the peer MSC works
normally.
Check the
work mode
If data has been configured for the peer
of the local If the status of a link is abnormal, use the
MSC, run the command DSP DHSTA to
office and LST DHHCFG command to check whether
check whether the local office is in the
the statuses the peer end IP address, local UDP port
mutual aid inactive state and whether the
of dual number, peer end UDP port number, and
two dual homing heartbeat links are
homing key are correctly configured.
normal.
heartbeat
links

On the LMT client, run the DSP MGW

command to check the status of gateway
registration.
Check the
status of At this time, the local office should work Refer to Section 5.2.2 “Steps of
gateway in the mutual aid inactive state, gateways Commissioning".
registration primarily homed to the local office should
all be normal in registration, while
gateways secondarily homed to the local
office abnormal in registration.
On the LMT client, run the DSP BSCTP
command to check the statuses of BICC
SCTP links. In case of abnormality, solve the problem
by referring to “Steps of BICC
BICC At this time, the local office should work Commissioning (Independent Work
commissioni in the mutual aid inactive state, links Mode)” in this chapter, and check whether
ng primarily homed to the local office should data configuration for the local office and
all be normal, while gateways peer MSC is correct.
secondarily homed to the local office
abnormal.

5-30
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

Step Operation Remark

If the statuses are abnormal, run the
On the LMT client, run the command
command LST BICCCICMDU to check
DSP BICCCIC or DSP BICCOFC to
whether the parameters such as the office
check the statuses of relevant BICC
direction, module number, start CIC, and
CICs.
CIC transformation mode are correct.
Power off the basic subrack of the peer
MSC, and the local office will enter the
mutual aid inactive state automatically. In case of abnormality, check whether data
Activate the
On the LMT client, run the DSP DHSTA has been correctly configured for the local
local office
command to check the work mode of the office.
local office and the statuses of dual
homing heartbeat links.
On the LMT client, run the DSP MGW
Check the command to check the status of gateway
status of registration.
gateway Refer to Section 5.2.2 “Steps of
registration At this time, the local office should work Commissioning".
(mutual aid in the mutual aid active state, and
active state) gateways should all be normal in
registration.
On the LMT client, run the DSP BSCTP
command to check the statuses of BICC In case of abnormality, solve the problem
SCTP links. by referring to “Steps of BICC
Commissioning (Independent Work
At this time, the local office should work Mode)” in this chapter, and check whether
BICC in the mutual aid active state, and the
commissioni data configuration for the local office and
links, except that to the peer MSC peer MSC is correct.
ng (mutual (powered off), should all be normal.
aid active
state) If the statuses are abnormal, run the
On the LMT client, run the command
command LST BICCCICMDU to check
DSP BICCCIC or DSP BICCOFC to
whether the parameters such as the office
check the statuses of relevant BICC
direction, module number, start CIC, and
CICs.
CIC transformation mode are correct.
(1) On the LMT of the local office,
execute the command SET DHWM:
WM=ASSIST, SM=AUTO,
TM=MODE1-1&MODE2-1; to set the
mutual aid takeover mode to “Two-way
auto switch”.
(2) Power on the basic subrack of the ! Note:
Deactivate peer MSC, and the local office will On the LMT client, run the DSP DHSTA
the local automatically enter the mutual aid command to check the work mode of the
office inactive state when the basic subrack of local office and the statuses of dual homing
the peer MSC works normally, heartbeat links.
(3) On the LMT of the local office, run the
command SET DHWM: WM=ASSIST,
SM=AUTO, TM=MODE1-1&MODE2-0;
to restore the setting of the original
mutual aid takeover mode of the local
office.

5-31
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

5.7.3 Locating BICC Problems

I. Checking Network Connection

Use the interface tracing function “PING” on the console to check whether the peer
device can be pinged through. If the peer device cannot be pinged through, check
whether physical connections are normal, including the connection of the Ethernet
cable, the running of the WIFM, the status of the Ethernet port of the WIFM, the
statuses of network devices (for example, routes) connected with the WIFM, the
configuration of route data and the running of the peer device.

II. Checking Data Configuration

1) Run the LST FECFG command to check whether the IP address of the interface of
the MSOFTX3000 is consistent with that in the planned data. If not, modify the IP
address accordingly.
2) If the MSOFTX3000 is not directly connected with the peer device, use the LST
FECFG command to check whether the address of the gateway is correctly
configured. You can use the interface tracing function “TRACERT” to trace IP
packets (specify the module number of the WIFM and the IP address of the peer
device to check the route of packets, so as to identify locations where packets are
lost).
3) Use the LST BICCSCTPLNK command to check whether the client and server
configured on the two ends of the SCTP connection are consistent with the
planned data. Make sure that one end of the SCTP is configured as the client, and
the other end the server. Otherwise, you cannot establish the connection.
4) Suppose the MSOFTX3000 is configured as the SCTP server. Through the SCTP
message tracing, you will see that the local end receives the “INIT” message, but
gives no response. Use the LST SCTPPARA command to check the checksum
algorithm parameter “Checksum Arithmetic”, and then check the checksum
algorithm of the peer end. If they are not consistent, modify them. The default
checksum algorithm of the MSOFTX3000 is “CRC32”, which can be modified by
using the SET SCTPPARA command.

III. Querying Status

Table 5-15 Commands for querying BICC statuses

Command Function Remark

DSP BSCTP
To query the status of the BICC link “Active” indicates the normal status.
DSP BSCTPOFC
DSP BICCCIC
DSP BICCOFC To query the status of BICC CIC None

DSP BICCSTA

5-32
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

5.7.4 Treating BICC Common Problems

I. BICC CIC Status Abnormality

1) Fault description
When checking the statuses of CICs using the DSP BICCCIC command, the returned
information shows the operation is time-out or some CICs have not been installed.
2) Causal analysis
Cause 1: Data configuration for one end is inconsistent with that for the other.
Cause 2: The lower layer signaling bearer is faulty.
3) Troubleshooting
For Cause 1, check whether data configuration is normal. Common data configuration
errors include:
The CIC configuration range for one end is not consistent with that for the other end;
The corresponding CICs are not configured for the correct office directions.

Note:
The range of CICs for one office direction can overlay that for another. So, if some CICs are configured for
the correct office direction, operations on this office direction will lead to erroneous result.

For Cause 2, check whether the BICC signaling bearer is normal.

When the lower layer signaling bearer (SCTP/MTP3/MTP3B/M3UA) is faulty, the
maintenance command of CICs cannot reach the peer end. Then, use commands DSP
BSCTPOFC, DSP N7DSP and DSP MTP3BDSP respectively to check lower layer
signaling links.

II. BICC Signaling Bearer Fault

1) Fault description
SCTP link messages cannot be traced.
2) Causal analysis
Currently, BICC can be over MTP/MTP3B/M3UA/SCTP. This can be set with the ADD
OFC command. When BICC is over MTP/MTP3B/M3UA, the configuration for the
lower lay signaling bearer is the same as that for ISUP. When BICC is over SCTP, office
directions should be associated with SCTP links with the ADD BICCSCTPLNK
command.
Cause 1: The BICC signaling bearer type configured for an office direction does not
conform to the signaling bearer type actually used.

5-33
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

Cause 2: Parameters of SCTP links on one end is inconsistent with that of the other
end.
Cause 3: Client/Server parameters on one end of SCTP are set identical with that on
the other end.
3) Troubleshooting
If there is no message on signaling links during calls, check whether the BICC signaling
bearer type for an office direction is identical with that configured for the office direction.
If MTP3/MTP3B/M3UA is configured for this office direction, check whether correct
DPCs have been configured in the office direction table.
If the SCTP link is configured, run the LST BICCSCTPLNK command to check whether
this link is configured for the correct office direction; and run the DSP BSCTP command
to check whether the link status is normal.
If the link status is abnormal, check whether SCTP links, IP addresses and port
numbers and Client/Server parameters on one end are configured identical with that on
the other end.
Use the SCTP link tracing message to observe the establishment of SCTP links. If
there are only requests in one direction, check data configuration of both directions. If
data configuration has no problem, check whether the physical connection is correct.
Run the ACT BSCTP command to activate the BICC SCTP link, and run the DEA
BSCTP command to deactivate the BICC SCTP link.

5.8 Connecting with RNC

5.8.1 Description of Relevant Concepts

The MSOFTX3000 is connected with RNC through RANAP. Protocol conversion and
adaptation are done through the signaling gateway (SG) built in the UMG8900. The
protocol between the UMG8900 and MSOFTX3000 is M3UA over SCTP/IP. The
protocol between the UMG8900 and RNC is MTP3B over ATM. The structure of
protocol stack is illustrated in Figure 5-12.

5-34
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

MSOFTX3000 RANAP/M3UA
RANAP
SCCP
M3UA
IP SCTP
IP

M3UA MTP3B
UMG8900 (SG) SAAL
SCTP
IP ATM

ATM RANAP/MTP3B

RANAP
SCCP
MTP3B
RNC SAAL
ATM

Figure 5-12 Structure of the RANAP/M3UA protocol stack

The signaling sent by the RNC is RANAP over MTP3B. The SG built in the UMG8900
adapts MTP3B to M3UA and sends MTP3B to the MSOFTX3000 over IP.
M3UA is implemented through SCTP over IP. M3UA links are identified as IP address +
port number. Therefore, when configuring M3UA links, you need specify the port
number different from the port that bears H.248.
In this mode of network, the work mode of M3UA is SGP-ASP. Define the
MSOFTX3000 as the application server (AS), and the UMG8900 (with an SG built in)
as the SG.

5.8.2 Steps of Commissioning

Table 5-16 Steps of commissioning for connecting with RNC through RANAP/SCTP

Item Operation Remark

Configuri
On the LMT client, execute the data Refer to Section 5.2.2 I. Configuring Online
ng online
script file. Data.
data
The “LINK” indicator is on when the physical
Check Observe the indicators on the WIFM. connection is normal, and is off in other cases.
the The green Ethernet port connection
network indicator, “LINK”, should be on, while When the “ACT” indicator flashes, it indicates
connectio the yellow Ethernet port data traffic that there is data being sent/received. The
n indicator, “ACT”, should flash. blinking frequency indicates the amount of data
traffic.

5-35
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning

Item Operation Remark

On the LMT client, use the interface
In case of failure, check whether the Ethernet
tracing function “PING” to check the
cables are correctly connected, whether the
communication between the WIFM
WIFM works normally, whether devices
and the UMG8900. If the ping
connected with the WIFM (such as a LAN
command is executed successfully, it
Switch) works normally, and whether the
indicates that the communication is
UMG8900 works normally
normal.
Check
On the LMT client, run the DSP MGW
the status
command to check the status of
of Refer to Section 5.2.2 “Steps of
gateway registration. "Normal”
gateway Commissioning".
indicates that the UMG8900 has
registrati
registered successfully.
on
On the LMT client, run the DSP
M3LNK command to check the status
of M3UA link. “Active” indicates that
the status is normal.
If the status is abnormal, run the LST M3LKS
On the LMT client, run the DSP command to check whether the correct
M3LKS command to check the status transmission mode has been configured for the
of the M3UA link set. link set. Use the LST M3LNK command to check
“Active” indicates that the status is whether such parameters as the local port
M3UA normal. number, local IP address, remote port number,
commissi remote IP address, and C/S work mode are
oning correctly configured.
On the LMT client, run the DSP M3DE
command to check the status of the
M3UA destination entity. “Accessible”
indicates that the status is normal.
If the statuses are abnormal, run the LST M3LE,
On the LMT client, run the DSP M3RT LST M3DE and LST M3LKS commands to check
command to check the statuses of whether such parameters as the local entity
relevant M3UA links. index, destination entity index and link set index
are correctly configured.
On the LMT client, run the DSP
If the statuses are abnormal, run the LST
SCCPDSP command to check the
SCCPDSP command to check whether such
statuses of remote SCCP signaling
parameters as DPC and OPC are correctly
points. “Allow” indicates that the
SCCPco configured.
status is normal.
mmission
ing On the LMT client, run the DSP
If the statuses are abnormal, run the LST
SCCPSSN command to check the
SCCPSSN command to check whether such
statuses of SCCP subsystems.
parameters as DPC, OPC and subsystem code
“Allow” indicates that the status is
are correctly configured.
normal.

5.8.3 Locating and Treating Problems

Refer to Section 5.3.4 “Locating SCCP/TCAP Problems”, Section 5.6.3 “Locating

M3UA Problems”, and Section 5.6.4 “Treating M3UA Common Problems”.

5-36
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Service Commissioning

Chapter 6 Service Commissioning

6.1 Introduction to This Chapter

This chapter describes service commissioning for the MSOFTX3000. The contents
include:
1) Executing data script and configuring service data
2) Implementing service test

6.2 Executing Data Script

For a newly-deployed office, follow the steps listed in Table 6-1 to perform online data
configuration on the LMT.

Table 6-1 Steps for the configuration of service data

Step Operation Remarks

If you cannot log in to the BAM, check
whether the LMT is logging in on the
On the LMT, start the client program
Start the BAM, whether the username and
1 of the MSOFTX3000 O&M software,
LMT client password are correct, and whether the
and log in to the BAM.
cable between LMT and BAM is
properly connected.

Enable The meanings of the commands:

Open the MML window and execute
alarm SET CWSON: enable or disable local
the following commands:
function and alarm function
2 format SET CWSON: SWT=ON;
conversion SET FMT: enable or disable format
SET FMT: STS=ON;
function, and conversion function
LON:;
get online LON: get online
Execute the
number
3
analysis
Press shortcut keys <Ctrl + E> to
data script
open the [Execute Batch File] dialog
Execute the box, and execute data script files in
mobile sequence. For detail on operations onto data script
4
service data Upon completing every script, check files, refer to “Method for Executing
script the [Execution result of] pane in the Data Script” in Chapter 3.
lower part of the dialog box, to see if
Execute the the MML commands are all executed
intelligent successfully.
5 network
service data
script

6-1
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Service Commissioning

Step Operation Remarks

If the verification fails, reset the board
and reload it.
On the MML window, run the It will take quite a long time to execute
Perform
command STR CRC: MN=255; to the command STR CRC. If the system
6 CRC on
perform CRC on the data of boards prompts timeout in executing the
board data
(modules) that can be loaded. command, select [System/Command
Timeout Setting...] on the LMT client to
extend the time-out time.

6.3 Implementing Service Test

6.3.1 Preparations

Before implementing service test, make the following preparations:

z Make a dialing test plan and send copies of it to exchange offices involved;
z Configure test data of the local office according to the negotiation with relevant
offices;
z Configure service data for relevant offices;
z Get the right version of HUAWEI MSOFTX3000 Mobile SoftSwitch Center Factory
Test Manual.

6.3.2 Method of Implementing Service Test

I. Call Test of Trunk

If commissioning is not performed for the peer office, get one or two time slots from
each E1 of the office to perform call test on trunks. Search for monologs and echoes.

II. Service Dialing Test for Local Office

If the local office is a Visited Mobile Switching Center (VMSC), the test operator also
needs to perform the following tests according to the dialing test plan: the local office
initiating a call, local office terminating a call, various switching functions and roaming
barring.
If the local office is a tandem mobile switching center (TMSC) or gateway mobile
switching center (GMSC), the test engineer can, with a mobile phone, perform dialing
test through the VMSC the commissioning location belongs to, and through the public
switched telephony network (PSTN) with a fixed-line phone.

III. Service Dialing Test for Related Office

Personnel of the related offices are asked to perform dialing test according to the
dialing test plan of Huawei. They should make records about whether a test item is
successful, and the caller number, called number, call initiating time and call

6-2
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Service Commissioning

terminating time. If a test item fails, notify the deployment engineer of it as soon as
possible. The deployment engineer can locate the problem using signaling tracing
during dialing test.

6.3.3 Service Tests

Note:
Before service tests, you must log on to the relevant traffic measurement task, so as to observe the traffic
measurement result after test.

Service tests include:

z Basic service test
z Supplementary service test
z Intelligent service test
z Feature service test
z Data service test
z Mobility management test
z CDR function test
Refer to the acceptance manual of the local office for test items and methods for
various services.

6.4 Handling of Common Problems

6.4.1 Handling of Call Abnormality

I. Monolog

1) Fault description
Monolog occurs when performing call test on trunks.
2) Causal analysis
Monolog is mostly caused by cross-connected lines. In other words, one E1 is wrongly
connected with another E1, as illustrated in Figure 6-1.
3) Troubleshooting
Disconnect this E1 on the cable distribution subrack and check the codes of the two
E1s in abnormal statuses. This will locate the two E1s causing cross-connected lines.
Change the E1 connections on the cabling rack to solve the problem.

6-3
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Service Commissioning

Local office Peer office

Receive Send
System A System A
Send Receive

Send Receive
System B System B
Receive Send

Figure 6-1 Cross-connected lines

II. Signaling Is Correct, but No RBT or Voice Can Be Heard

1) Fault description
While performing call test on trunks, the signaling procedure is correct, but no ring back
tone can be heard, and neither party can hear the voice of the other party.
2) Causal analysis
It is possible that the CIC configuration of this trunk at the local office is different from
the peer office.
3) Troubleshooting
Check the CIC configuration at the peer office. If the peer office indicates that the CIC
configuration at that office is different from that at the local office, it is possible that this
E1 is wrongly connected with another E1, as shown in Figure 6-2. Disconnect this E1
on the distribution subrack and check the number of the E1 in abnormal status at the
peer office. This will locate the E1 wrongly connected with this E1. To solve the problem,
inform the optical transmission personnel to modify data settings.

Local office Peer office

Receive Send
System A System A
Send Received

Receive Send
System B System B
Send Receive

Figure 6-2 Wrong E1 connection

6.4.2 Handling of BICC Call Problems

A structure with bearer separated from control requires more hardware components.
The interfaces between these components are all possible fault points. Therefore.,

6-4
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Service Commissioning

when call failure occurs, locate the problem according to the cause value. Typically,
improperly configured call data (including number analysis and routes), trunk data and
gateway attributes can all be causes to faults.

I. When Performing BICC Outgoing Call Test on UE, no IAM Is Sent Out, so Call
Fails

Handling:
1) Trace the lu interface to see if the access side is faulty.
2) If the provisioning of the lu interface is successful, check whether the configuration
of the call prefix is correct. On the MSOFTX3000 client, run the command LST
CNACLD to check the call prefix settings of the called number.
If it is a PSTN number, check whether the route analysis index corresponding to the
prefix is correct.
If it is an MSISDN, trace the mobile application part (MAP) message to acquire the
MSRN of the called number, and then use the LST CNACLD command to check
whether the prefix of this MSRN is correctly configured.
3) If no problem is found in number analysis, use the LST RTANA command to
check whether the route analysis data is correctly configured. Normally, “ALL” is
selected for the calling party type, address information indicator and transmission
ability. Note that the signaling as prior should be configured to match the circuit
type described in the corresponding CIC trunk group.
4) Check the trunk group table to see if there is any BICC trunk group configured on
this subroute and if the gateway in the trunk group table has been configured.
5) If no problem is found in the above checking, use the DSP MGW command to see
if the Mc interface is normal and check the tracing message. If the Mc interface is
abnormal, the MSOFTX3000 will fail to receive any response after sending the
ADD.req message to MGW. The call is then released.
6) If the Mc interface is normal, but the “ADD.req” message is not found on the Mc
interface, use the LST MGW command to check the support ability of the MG and
see if the codec type of this call has been configured correctly.
7) If the Mc interface is normal, but the returning of the “ADD.req” message fails
when tracing the message on the Mc interface, then check:
Check whether the MGW supports the bearer type and codec list type sent by the
MSOFTX3000. If not, run the MOD MGW command to remove the codec not supported
by the MG.
Check whether the trunk resources of the MG are correctly configured. If the current
call is of IP bearer type, check whether relative IP data has been correctly configured
on the MG, whether corresponding physical ports have been activated, and whether
cables are correctly connected. If the current call is of ATM bearer type, check whether
the MG supports ATM, whether relative data has been correctly configured, and
whether statuses of resources are normal.

6-5
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Service Commissioning

II. When Performing BICC Outgoing Call Test on UE, an IAM Is Sent, but the
Call Is not Connected

Handling:
1) Check the cause value of the release and use the cause value to roughly locate
the fault.
2) If the cause value is “Network not work normally,” the cause of release may relate
to the MG. If the “release (REL)” message is returned immediately after “initial
address message (IAM)” is sent, it is possible that sending the “ADD.req”
message at the incoming office fails. Then check if the Mc interface at the
incoming office is normal and if the codec type supported by the MG is compatible
with the Codec list for the current call.
3) If the cause value is “No route available”, check such data as the called number
analysis on the incoming office.
4) If the cause value is “No route to terminal”, it is possible that there is no response
to the paging of the user equipment (UE) on the called party side.
5) If the cause value is “No resource available”, and the “REL” message is sent
immediately after the “IAM” message, use the LST MGW command to check the
MG configuration on the incoming office and see if the codec type supported by
the MG is compatible with that of the current call.

6.4.3 Handling of CPU Overload Problem

When the CPU seizure ratio is too high, the MSOFTX3000 will control traffic flow,
leading to higher call loss and lower call completion rate.

I. Common Causes of CPU Overload

The common causes are

z Too heavy traffic
z Too short traffic measurement task period
z Irrational location area
z Unregulated operation and maintenance
z Incorrect data configuration
z Incorrect setting of CPU overload thresholds

II. Handling of CPU Overload

1) Check whether maintenance and operations are properly done.

When there are many operation and maintenance tasks, the CPU usage rate will be
high, and CPU overload might occur. To avoid CPU overload caused by O&M during
heavy traffic, the following points should be kept in mind:
Do not run too many modification commands at busy hours.
Do not run commands at busy hours that bring out lengthy display.

6-6
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Service Commissioning

Do not export statistics to the terminal at busy hours.

Do not perform too much dynamic tracing to links at busy hours.

Caution:

Avoid broadcasting short messages in heavy traffic. Limit and split the number of receivers.

2) Check traffic.
You can observe the traffic of an MSOFTX3000 in real time in the following ways:
Query the recent traffic measurement report. Analyze critical information such as call
attempts, call completion times and average seizure duration that are related to call
loss and traffic. Form the traffic pattern.
Query the seizure of trunk circuits. If the trunk circuit seizure ratio is over 70%, it
indicates that there is heavy inter-office traffic.
For CPU overload caused by heavy traffic, just observe. When the CPU overload
caused by heavy traffic frequently appears, negotiate with the related offices, scatter
the traffic, and expand the capacity of the MSOFTX3000.
3) Check the measurement period of traffic measurement tasks.
The measurement period of traffic measurement tasks will also greatly affect the CPU
seizure ratio. Due to their close relation with calls, most traffic measurement tasks
require a long measurement period. The shorter measurement period increases the
CPU overload. Currently, we recommend one hour for a measurement period.
Note that the modification of the measurement cycle of traffic measurement tasks can
affect the measurement results. That is, there will be no measurement result for the first
measurement period after modification. So be careful to modify the measurement
period.
4) Check data configuration.
There can be two types of data configuration errors causing the CPU overload. One is
that the load of signaling links and trunks is not evenly balanced. As a result, some
signaling links are overloaded, and so are the service boards responsible for the
processing of these signaling links. If this is the case, adjust the link configuration.
The other is that the MAP functions are not correctly configured. For example, the
parameter “Periodical location update time” is set too short. Usually it is set as 1.5–3
times that of base station controller (BSC)/radio network controller (RNC). As a result,
the A/Iu-CS interface link will be overloaded.
5) Split the location areas that are not correctly set.

6-7
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Service Commissioning

Because the subscriber location information in the visitor location register (VLR) is
stored in the location area form, when the MSOFTX3000 sends a paging message to
the subscriber, it sends to the corresponding BSC/RNC according to the location area.
If the MSOFTX3000 has n BSCs/RNCs, but has only one location area, the message
will be sent to all BSCs/RNCs. Thus, if one BSC/RNC corresponds to one location area,
the message will be multiplied by n times.
Therefore, it is recommended to split a location area that has heavy traffic and contains
a number of BSCs/RNCs. This lessens the load of the system during traffic peak hours.
It is recommended to spilt a location area when it contains more than four BSCs/RNCs.
6) Check the setting of the CPU overload thresholds.
The setting of the CPU overload thresholds directly affects the alarming and recovery
when a CPU overload fault occurs. So make sure that the threshold is correctly set.
Use the following commands to query and modify the threshold information:
Use the command LST CPUTHD, input a module number, and press <F9>. Then, CPU
overload thresholds and recovery thresholds of this module for all the four levels will be
listed.
Use the command SET CPUTHD, and input a module number and CPU overload
thresholds and recovery thresholds of this module for all levels. The corresponding
settings will be listed.
Table 6-2 lists the current default CPU overload thresholds.

Table 6-2 Default CPU overload thresholds

Overload Overload Overload Overload Resume Resume Resume Resume

Threshold
Level 1 Level 2 Level 3 Level 4 Level 1 Level 2 Level 3 Level 4
Default 80 85 90 95 75 80 85 90

6-8
Installation Manual - System Commissioning Appendix A Commissioning Records of
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Newly-Built Office

Appendix A Commissioning Records of

Newly-Built Office

A.1 Preparations for System Commissioning

Table A-1 Preparations for system commissioning

Item Result Remarks

The installation and checking of hardware are
Check the ‫ ڤ‬Y; ‫ ڤ‬N
finished, and the equipment is powered on.
construction
condition The installation and checking of software are
‫ ڤ‬Y; ‫ ڤ‬N
finished.
Check
The complete technical documents for deployment
technical ‫ ڤ‬Y; ‫ ڤ‬N
are ready.
documents

The numbers of servers and matching devices are

‫ ڤ‬Y; ‫ ڤ‬N
correct.

The numbers of cabinets and subracks are correct. ‫ ڤ‬Y; ‫ ڤ‬N

Check the
The number of boards and board locations are
hardware ‫ ڤ‬Y; ‫ ڤ‬N
correct.
configuration
Board versions are correct. ‫ ڤ‬Y; ‫ ڤ‬N
The subrack numbers of the WSIU boards are
‫ ڤ‬Y; ‫ ڤ‬N
correctly set.
The status of the power distribution box is normal. ‫ ڤ‬Y; ‫ ڤ‬N

The statuses of subrack fans are normal. ‫ ڤ‬Y; ‫ ڤ‬N

Check the The statuses of power boards of subracks are
‫ ڤ‬Y; ‫ ڤ‬N
power supply normal.
The power status of the server is normal. ‫ ڤ‬Y; ‫ ڤ‬N

The power status of the LAN Switch is normal. ‫ ڤ‬Y; ‫ ڤ‬N

Check the Software versions are correct. ‫ ڤ‬Y; ‫ ڤ‬N

software of
BAM The SQL Server runs normally. ‫ ڤ‬Y; ‫ ڤ‬N

Services are in normal condition. ‫ ڤ‬Y; ‫ ڤ‬N

Processes are in normal condition. ‫ ڤ‬Y; ‫ ڤ‬N

The BAM can log in after restarting, the SQL Server
and services and processes are all in good ‫ ڤ‬Y; ‫ ڤ‬N
condition.

A-1
Installation Manual - System Commissioning Appendix A Commissioning Records of
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Newly-Built Office

Item Result Remarks

System customization has been fulfilled by using the
‫ ڤ‬Y; ‫ ڤ‬N
SetWin2000 security customization tool.
SysPatron runs normally. ‫ ڤ‬Y; ‫ ڤ‬N

Check the Software versions are correct. ‫ ڤ‬Y; ‫ ڤ‬N

software of the
The SQL Server runs normally. ‫ ڤ‬Y; ‫ ڤ‬N
emergency
workstation Services are in normal condition. ‫ ڤ‬Y; ‫ ڤ‬N

Check the
software of the Software versions are correct. ‫ ڤ‬Y; ‫ ڤ‬N
LMT
The version of software is correct. ‫ ڤ‬Y; ‫ ڤ‬N

The status of the dual system heartbeat is normal. ‫ ڤ‬Y; ‫ ڤ‬N

All processes run normally. ‫ ڤ‬Y; ‫ ڤ‬N

Check iGWB
software It is possible to automatically log on to the active and
standby iGWBs after they have been restarted. And ‫ ڤ‬Y; ‫ ڤ‬N
processes run normally.

It is possible to switch between the active and

‫ ڤ‬Y; ‫ ڤ‬N
standby iGWB. And processes run normally.
The IP addresses of the BAM and iGWB are
‫ ڤ‬Y; ‫ ڤ‬N
correctly set.

The BAM can communicate normally with the

‫ ڤ‬Y; ‫ ڤ‬N
foreground host.
Check the
communicatio The communication between the BAM and iGWB is
‫ ڤ‬Y; ‫ ڤ‬N
n of the normal.
internal LAN The communication between the iGWB and the host
‫ ڤ‬Y; ‫ ڤ‬N
is normal.

The configuration of the VLAN is correct. ‫ ڤ‬Y; ‫ ڤ‬N

The Ethernet biplane switchover function is normal. ‫ ڤ‬Y; ‫ ڤ‬N

The IP addresses of the BAM, LMT, iGWB and

‫ ڤ‬Y; ‫ ڤ‬N
emergency workstation are correctly set.
Check the The BAM can normally communicate with the LMT. ‫ ڤ‬Y; ‫ ڤ‬N
communicatio
n of the The BAM can normally communicate with the
‫ ڤ‬Y; ‫ ڤ‬N
external LAN emergency workstation.
The communication between the BAM and iGWB is
‫ ڤ‬Y; ‫ ڤ‬N
normal.

Check the The BAM can normally communicate with the NMC. ‫ ڤ‬Y; ‫ ڤ‬N
communicatio The communication between the iGWB and the
n of the WAN ‫ ڤ‬Y; ‫ ڤ‬N
charging center is normal.

A-2
Installation Manual - System Commissioning Appendix A Commissioning Records of
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Newly-Built Office

Item Result Remarks

Make an
Make an empty backup of the BAM database using
empty backup
SQL Server Enterprise Manager before data ‫ ڤ‬Y; ‫ ڤ‬N
of the BAM
configuration.
database

A.2 Data Configuration

Table A-2 Data configuration

Item Result Remarks

Understand the networking mode, be clear of the
equipment configuration, and collect external
Data collection
interface data, consult with the peer office about ‫ ڤ‬Y; ‫ ڤ‬N
and planning
the data needing negotiation and service data, and
fill out the data collection form.
Edit/modify data script files according to the
Make data script ‫ ڤ‬Y; ‫ ڤ‬N
situation on site.
Check data script Data script is correct. ‫ ڤ‬Y; ‫ ڤ‬N

A.3 Local Office Commissioning

Table A-3 Local office commissioning

Item Result Remarks

Execute data
Executing data script files offline succeeds. ‫ ڤ‬Y; ‫ ڤ‬N
script offline
Service processes of the BAM (especially the
‫ ڤ‬Y; ‫ ڤ‬N
Exchange process) are normal.
Make
preparations The BAM can communicate normally with the
‫ ڤ‬Y; ‫ ڤ‬N
before loading foreground host.
boards
There are load source files under the directory
‫ ڤ‬Y; ‫ ڤ‬N
D:\Data\ of the BAM.
Boards run normally. ‫ ڤ‬Y; ‫ ڤ‬N
Load and check Software versions of boards are correct. ‫ ڤ‬Y; ‫ ڤ‬N
basic subracks
Data verification for boards (modules) that can be
‫ ڤ‬Y; ‫ ڤ‬N
loaded is successful.
Load and check Boards run normally. ‫ ڤ‬Y; ‫ ڤ‬N
expansion
subracks Software versions of boards are correct. ‫ ڤ‬Y; ‫ ڤ‬N
Data verification for boards (modules) that can be
‫ ڤ‬Y; ‫ ڤ‬N
loaded is successful.

A-3
Installation Manual - System Commissioning Appendix A Commissioning Records of
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Newly-Built Office

Item Result Remarks

All expansion subracks can be successfully
‫ ڤ‬Y; ‫ ڤ‬N
loaded.
Clock cables are correctly connected. ‫ ڤ‬Y; ‫ ڤ‬N
Perform clock The status of the clock phase-locked loop circuit
‫ ڤ‬Y; ‫ ڤ‬N
commissioning of the WCKI is normal.
The clock statuses of the WEPIs are normal. ‫ ڤ‬Y; ‫ ڤ‬N

The statuses of the LAN Switch indicators are

‫ ڤ‬Y; ‫ ڤ‬N
normal.

The statuses of the power distribution box

‫ ڤ‬Y; ‫ ڤ‬N
indicators are normal.
Check indicator Subrack fans run normally and the statuses of
‫ ڤ‬Y; ‫ ڤ‬N
statuses their indicators are normal.

The statuses of indicators on front boards are

‫ ڤ‬Y; ‫ ڤ‬N
normal.

The statuses of indicators on back boards are

‫ ڤ‬Y; ‫ ڤ‬N
normal.

The power distribution box runs normally. ‫ ڤ‬Y; ‫ ڤ‬N

Subrack fans run normally. ‫ ڤ‬Y; ‫ ڤ‬N

Check the Boards run normally. ‫ ڤ‬Y; ‫ ڤ‬N
running of
hardware The statuses of Fast Ethernet (FE) ports are
‫ ڤ‬Y; ‫ ڤ‬N
normal.
The communication between the WIFM and the
‫ ڤ‬Y; ‫ ڤ‬N
default gateway is normal.

Verify hardware The active/standby switchover for the front board

‫ ڤ‬Y; ‫ ڤ‬N
switchover is normal.

Perform
self-loop test of The self-loop test of E1 cables of the local office is
‫ ڤ‬Y; ‫ ڤ‬N
E1 cables of the passed.
local office
Modify the After the successful loading of a board and when
loading it runs normally, modify the settings of the loading
‫ ڤ‬Y; ‫ ڤ‬N
software switch software switch to “program available, data
of a board available, data writable, program not writable”.
The time of the switch is correctly set with an error
Set the time for
less than ±30 seconds against the local standard ‫ ڤ‬Y; ‫ ڤ‬N
the switch
time.

A-4
Installation Manual - System Commissioning Appendix A Commissioning Records of
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Newly-Built Office

A.4 Interconnection Commissioning

Table A-4 Interconnection commissioning

Item Result Remarks

Executing data script files succeeds. ‫ ڤ‬Y; ‫ ڤ‬N

The network connection between the WIFM and MG is

Connect with ‫ ڤ‬Y; ‫ ڤ‬N
normal.
the MG
The status of gateway registration is normal. ‫ ڤ‬Y; ‫ ڤ‬N
Statuses of Mc-interface links are normal. ‫ ڤ‬Y; ‫ ڤ‬N

Executing data script files succeeds. ‫ ڤ‬Y; ‫ ڤ‬N

The statuses of clocks are normal. ‫ ڤ‬Y; ‫ ڤ‬N

The registration status of the gateway is normal. ‫ ڤ‬Y; ‫ ڤ‬N

The remote self-loop test of E1 cables is normal. ‫ ڤ‬Y; ‫ ڤ‬N

Connect with
BSC Statuses of MTP links, signaling points and routes are
‫ ڤ‬Y; ‫ ڤ‬N
normal.
Statuses of SCCP remote signaling points and
‫ ڤ‬Y; ‫ ڤ‬N
subsystems are normal.
Statuses of A-interface trunk circuits are normal. ‫ ڤ‬Y; ‫ ڤ‬N

Executing data script files succeeds. ‫ ڤ‬Y; ‫ ڤ‬N

The statuses of clocks are normal. ‫ ڤ‬Y; ‫ ڤ‬N

The remote self-loop test of E1 cables is normal. ‫ ڤ‬Y; ‫ ڤ‬N

Connect with
HLR Statuses of MTP links, signaling points and routes are
‫ ڤ‬Y; ‫ ڤ‬N
normal.
Statuses of SCCP remote signaling points and
‫ ڤ‬Y; ‫ ڤ‬N
subsystems are normal. GT translation is correct.
Executing data script files succeeds. ‫ ڤ‬Y; ‫ ڤ‬N

The statuses of clocks are normal. ‫ ڤ‬Y; ‫ ڤ‬N

The remote self-loop test of E1 cables is normal. ‫ ڤ‬Y; ‫ ڤ‬N

Connect with
SMC Statuses of MTP links, signaling points and routes are
‫ ڤ‬Y; ‫ ڤ‬N
normal.
Statuses of SCCP remote signaling points and
‫ ڤ‬Y; ‫ ڤ‬N
subsystems are normal. GT translation is correct.
Connect with Executing data script files succeeds. ‫ ڤ‬Y; ‫ ڤ‬N
SCP
The statuses of clocks are normal. ‫ ڤ‬Y; ‫ ڤ‬N

The remote self-loop test of E1 cables is normal. ‫ ڤ‬Y; ‫ ڤ‬N

A-5
Installation Manual - System Commissioning Appendix A Commissioning Records of
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Newly-Built Office

Item Result Remarks

Statuses of MTP links, signaling points and routes are
‫ ڤ‬Y; ‫ ڤ‬N
normal.
Statuses of SCCP remote signaling points and
‫ ڤ‬Y; ‫ ڤ‬N
subsystems are normal. GT translation is correct.
Executing data script files succeeds. ‫ ڤ‬Y; ‫ ڤ‬N

The statuses of clocks are normal. ‫ ڤ‬Y; ‫ ڤ‬N

The remote self-loop test of E1 cables is normal. ‫ ڤ‬Y; ‫ ڤ‬N

Connect with
SGSN Statuses of MTP links, signaling points and routes are
‫ ڤ‬Y; ‫ ڤ‬N
normal.
Statuses of SCCP remote signaling points and
‫ ڤ‬Y; ‫ ڤ‬N
subsystems are normal. GT translation is correct.
Executing data script files succeeds. ‫ ڤ‬Y; ‫ ڤ‬N

The statuses of clocks are normal. ‫ ڤ‬Y; ‫ ڤ‬N

The registration status of the gateway is normal. ‫ ڤ‬Y; ‫ ڤ‬N

Connect with
The remote self-loop test of E1 cables is normal. ‫ ڤ‬Y; ‫ ڤ‬N
MSC through
ISUP&MAP/ Statuses of MTP links, signaling points and routes are
MTP ‫ ڤ‬Y; ‫ ڤ‬N
normal.
Statuses of SCCP remote signaling points and
‫ ڤ‬Y; ‫ ڤ‬N
subsystems are normal. GT translation is correct.
The status of SS7 trunk circuit is normal. ‫ ڤ‬Y; ‫ ڤ‬N

Executing data script files succeeds. ‫ ڤ‬Y; ‫ ڤ‬N

The network connection between the WIFM and

‫ ڤ‬Y; ‫ ڤ‬N
UMG8900 is normal.
Connect with
the MSC The status of gateway registration is normal. ‫ ڤ‬Y; ‫ ڤ‬N
using
ISUP/M3UA Statuses of M3UA links, link set, and route are normal. ‫ ڤ‬Y; ‫ ڤ‬N

SS7 trunk circuits are in normal statuses. ‫ ڤ‬Y; ‫ ڤ‬N

Executing data script files succeeds. ‫ ڤ‬Y; ‫ ڤ‬N

Connect with The network connection between the WIFM and MSC is
the MSC ‫ ڤ‬Y; ‫ ڤ‬N
normal.
using
BICC/SCTP The registration status of the gateway is normal. ‫ ڤ‬Y; ‫ ڤ‬N
(independent
work mode) Statuses of BICC links are normal. ‫ ڤ‬Y; ‫ ڤ‬N
BICC CIC statuses are normal. ‫ ڤ‬Y; ‫ ڤ‬N

Connect with Executing data script files succeeds. ‫ ڤ‬Y; ‫ ڤ‬N

the MSC
using The network connection between the WIFM and MSC is
‫ ڤ‬Y; ‫ ڤ‬N
BICC/SCTP normal.

A-6
Installation Manual - System Commissioning Appendix A Commissioning Records of
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Newly-Built Office

Item Result Remarks

(mutual aid The statuses of dual homing heartbeat links are normal.
work mode) ‫ ڤ‬Y; ‫ ڤ‬N
The local office is in the mutual aid inactive status
The registration status of the gateway controlled by the
‫ ڤ‬Y; ‫ ڤ‬N
local office is normal.
The statuses of BICC links controlled by the local office are
‫ ڤ‬Y; ‫ ڤ‬N
normal.
BICC CIC statuses are normal. ‫ ڤ‬Y; ‫ ڤ‬N

The local office is activated successfully and is in the

‫ ڤ‬Y; ‫ ڤ‬N
mutual aid active status.
Registration statuses of all gateways are normal. ‫ ڤ‬Y; ‫ ڤ‬N

Statuses of all BICC links are normal. ‫ ڤ‬Y; ‫ ڤ‬N

The statuses of BICC CICs are normal. ‫ ڤ‬Y; ‫ ڤ‬N

Deactivating the local office succeeds. The local office is in
the mutual aid inactive state. The status of dual homing ‫ ڤ‬Y; ‫ ڤ‬N
heartbeat link is normal.
Executing data script files succeeds. ‫ ڤ‬Y; ‫ ڤ‬N

The connection between the WIFM and UMG8900 is

‫ ڤ‬Y; ‫ ڤ‬N
normal.
Connect with The registration status of the gateway is normal. ‫ ڤ‬Y; ‫ ڤ‬N
RNC
The statuses of M3UA links, link set, destination entity and
‫ ڤ‬Y; ‫ ڤ‬N
route are normal.
The statuses of SCCP remote signaling points and
‫ ڤ‬Y; ‫ ڤ‬N
subsystems are normal.

A.5 Service Commissioning

Table A-5 Service commissioning

Item Result Note

Basic service test ‫ ڤ‬Y; ‫ ڤ‬N

Supplementary service test ‫ ڤ‬Y; ‫ ڤ‬N

Intelligent service test ‫ ڤ‬Y; ‫ ڤ‬N

Feature service test ‫ ڤ‬Y; ‫ ڤ‬N

Data service test ‫ ڤ‬Y; ‫ ڤ‬N

Mobility management test ‫ ڤ‬Y; ‫ ڤ‬N

CDR function test ‫ ڤ‬Y; ‫ ڤ‬N

A-7
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Index

Index

connecting with HLR

B protocol stack, 5-12
BICC steps of commissioning, 5-14
introduction, 5-28 connecting with MG
locating problems, 5-32 H.248/SCTP commissioning, 5-3
treating common problems, 5-33 interaction between MSOFTX3000 and MG, 5-2
board loading locating H.248/SCTP problems, 5-4
checking whether loading is successful, 4-7 protocol stack, 5-1
description of software switches, 4-1 step of commissioning, 5-2
description of source files, 4-2 treating SCTP common problems, 5-5
description of switches of power distribution connecting with MSC
subrack, 4-6 protocol stack (BICC/SCTP), 5-27
for newly-built office, 4-2 protocol stack (ISUP&MAP/MTP), 5-16
handling of loading problems, 4-8 protocol stack (ISUP/M3UA), 5-19
introduction, 4-1 steps of commissioning (BICC/SCTP), 5-29
method of loading, 4-1 steps of commissioning (ISUP&MAP/MTP), 5-17
operation steps, 4-5 steps of commissioning (ISUP/M3UA), 5-21
preparations, 4-4 through BICC/SCTP, 5-27
BSSAP/MTP through ISUP&MAP/MTP, 5-16
protocol stack, 5-6 through ISUP/M3UA, 5-19
BSSAP+/MTP connecting with RNC
protocol stack, 5-13 protocol stack, 5-34
steps of commissioning, 5-35
C connecting with SCP
CAP/MTP protocol stack, 5-13
protocol stack, 5-13 steps of commissioning, 5-14
clock commissioning connecting with SGSN
checking clock cable connection, 4-11 protocol stack, 5-13
description of clock system networking, 4-9 steps of commissioning, 5-14
MSOFTX3000 locking BITS clocks, 4-9 connecting with SMC
MSOFTX3000 locking peer office clocks, 4-10 protocol stack, 5-12
steps for locking BITS clocks, 4-12 steps of commissioning, 5-14
steps for locking peer office clocks, 4-13
connecting with BSC D
locating MTP problems, 5-9 data collection and planning, 3-2
locating SCCP/TCAP problems, 5-11 data configuration
protocol stack, 5-6 method for executing data script, 3-2
steps of commissioning, 5-7 mode, 3-1

i-1
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Index

sequence, 3-1 configure data offline, 4-3

data script description of related concepts, 4-1
editing and checking, 3-3 hardware commissioning, 4-14
method for executing, 3-2 modifying settings of loading software switch, 4-17
dual homing prepare for loading, 4-3
basic concept, 5-28 setting time for MSOFTX3000, 4-17

H M
H.248/SCTP M3UA
commissioning, 5-3 locating problems, 5-22
locating problems, 5-4 treating common problems, 5-24
protocol stack, 5-1 MAP/MTP
hardware commissioning protocol stack, 5-12
checking indicator status, 4-14 MTP
checking the running of hardware, 4-15 locating problems, 5-9
hardware switchover verification, 4-16
self-loop test for local office E1 cables, 4-16 O
O&M system
I checking communication, 2-9
interconnection commissioning checking communication of external LAN, 2-15
connecting with BSC, 5-6 checking communication of internal LAN, 2-13
connecting with HLR, 5-12 checking communication of WAN, 2-16
connecting with MG, 5-1 description, 2-10
connecting with MSC through BICC/SCTP, 5-27 IP address of BAM, 2-10
connecting with MSC through ISUP&MAP/MTP, IP address of emergency workstation, 2-11
5-16 IP address of iGWB, 2-12
connecting with MSC through ISUP/M3UA, 5-19 IP address of LMT, 2-11
connecting with RNC, 5-34 IP address of WSMU, 2-11
connecting with SCP, 5-12 method for checking communication, 2-13
connecting with SGSN, 5-12
connecting with SMC, 5-12 P
IP address preparations for system commissioning, 2-1
BAM, 2-10 checking communication of O&M system, 2-9
emergency workstation, 2-11 checking construction conditions, 2-1
iGWB, 2-12 checking hardware configuration, 2-2
LMT, 2-11 checking power supply, 2-4
WSMU, 2-11 checking software, 2-4
checking technical documents, 2-2
L making a backup of BAM database, 2-16
local office commissioning protocol stack
board loading, 4-4 BICC/SCTP, 5-27
clock commissioning, 4-9 BSSAP/MTP, 5-6

i-2
Installation Manual - System Commissioning
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Index

BSSAP+/MTP, 5-13 handling of BICC call problems, 6-5

CAP/MTP, 5-13 handling of call abnormality, 6-3
H.248/SCTP, 5-1 handling of CPU overload, 6-6
ISUP&MAP/MTP, 5-16 implementing service test, 6-2
ISUP/M3UA, 5-19 system commissioning
MAP/MTP, 5-12 commissioning records of newly-built office, A-1
RANAP/M3UA, 5-34 conditions, 1-1
data configuration, 3-1
R definition, 1-1

RANAP/M3UA flow, 1-1

protocol stack, 5-34 interconnection commissioning, 5-1

local office commissioning, 4-1
S overview, 1-1
preparations, 2-1
SCCP
service commissioning, 6-1
locating problems, 5-11
SCTP
T
treating common problems, 5-5
service commissioning TCAP
handling common problems, 6-3 locating problems, 5-11

i.

i-3