MSS Commissioning PDF

Chapter 1 Overview of System Commissioning ...........................................
1-1
1.1 Explanation of SM .................................................................................. 1-1
1.2 Flow of SM ............................................................................................. 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-3
2.4.1 Checking Hardware Configuration ................................................. 2-3
2.4.2 Checking Power Supply ................................................................. 2-4
2.5 Checking Versions and Running of Software ......................................... 2-5
2.5.1 Checking Software of BAM ............................................................ 2-5
2.5.2 Checking Software of Emergency Workstation.............................. 2-7
2.5.3 Checking Software of LMT ............................................................. 2-8
2.5.4 Checking Software of iGWB .......................................................... 2-8
2.6 Checking Network Communication ........................................................ 2-10
2.6.1 Networking of O&M System ........................................................... 2-10
2.6.2 Method for Checking Network Communication.............................. 2-14
2.6.3 Checking Communication of Internal LAN ..................................... 2-14
2.6.4 Checking Communication of External LAN .................................... 2-16
2.6.5 Checking Communication of WAN ................................................. 2-17
2.7 Making a Backup of the Empty BAM Database ..................................... 2-18
Chapter 3 Data Configuration ......................................................................... 3-1
3.2 DC for Newly-Deployed Office ............................................................... 3-1
3.2.1 DC Mode ........................................................................................ 3-1
3.2.2 DC 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-2
3.4.1 Editing Data Script ......................................................................... 3-2
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-5
4.4.3 Checking If Loading Is Successful ................................................. 4-8
4.4.4 Handling of Loading Problems ....................................................... 4-9
4.5 Clock Commissioning ............................................................................. 4-10
4.5.1 Description of Clock System Networking ....................................... 4-10
4.5.2 Checking Clock Cable Connection ................................................ 4-12
4.5.3 Commissioning Steps for Locking BITS Clocks ............................. 4-14
4.5.4 Commissioning Steps for Locking Peer Office Clocks ................... 4-14
4.6 Commissioning of Local Office Hardware .............................................. 4-15
4.6.1 Checking Indicator Status .............................................................. 4-15
4.6.2 Checking the Running of Hardware ............................................... 4-17
4.6.3 Hardware Switchover Verification .................................................. 4-18
4.6.4 Self-Loop Test for Local Office E1 Cables ..................................... 4-19
4.7 Modifying Settings of Loading Software Switch of Board ....................... 4-19
4.8 Setting Time for the Switch .................................................................... 4-20
Chapter 5 Interconnection Commissioning .................................................. 5-1
5.2 Connecting with MGW ............................................................................ 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.3 Locating MTP Problems ................................................................. 5-10
5.3.4 Treating MTP Common Problems ................................................. 5-12
5.3.5 Locating SCCP/TCAP Problems .................................................... 5-14
5.3.6 Treating SCCP Common Problems ............................................... 5-15
5.4 Connecting with HLR, SMC, SCP and SGSN ........................................ 5-19
5.4.3 Locating and Treating Problems .................................................... 5-23
5.5 Connecting with MSC through ISUP & MAP/MTP ................................. 5-23
5.6 Connecting with MSC through ISUP/M3UA ........................................... 5-27
5.6.3 Locating M3UA Problems .............................................................. 5-30
5.6.4 Treating M3UA Common Problems ............................................... 5-32
5.7 Connecting with MSC through BICC/SCTP ........................................... 5-35
5.7.1 Description of Protocol ................................................................... 5-35
5.7.3 Locating BICC Problems ................................................................ 5-40
5.7.4 Treating BICC Common Problems ................................................ 5-41
5.8 Connecting with RNC ............................................................................. 5-42
Chapter 6 Service Commissioning ................................................................ 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-5
6.4.3 Handling of CPU Overload Problem .............................................. 6-6
Appendix A Commissioning Records of Newly-Built Office ....................... A-1
A.1 Preparations for SM ............................................................................... A-1
A.2 Data Configuration ................................................................................. A-3
A.3 Local Office Commissioning .................................................................. A-4
A.4 Interconnection Commissioning ............................................................. A-5
A.5 Service Commissioning ......................................................................... A-8
Index .................................................................................................................
HUAWEI
HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Installation Manual System Commissioning
V100R003
Huawei Technologies Proprietary

HUAWEI MSOFTX3000 Mobile SoftSwitch Center
Installation Manual
Volume System Commissioning
Manual Version T2-030410-20060425-C-3.05
Product Version V100R003
BOM 31042110
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support
and service. Please feel free to contact our local office or company headquarters.
Huawei Technologies Co., Ltd.
Address: Administration Building, Huawei Technologies Co., Ltd.,
Bantian, Longgang District, Shenzhen, P. R. China
Postal Code: 518129
Website: http://www.huawei.com
Email: support@huawei.com

Copyright 2006 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, and TopEng are trademarks of Huawei
Technologies Co., Ltd.
All other trademarks and trade names 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 V100R003.
Organization
The manual introduces operations about MSOFTX3000 commissioning.
There are six chapters and an appendix in the manual.
Chapter 1 Overview of System Commissioning introduces the contents and flow

of system commissioning.
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.
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.
Chapter 4 Local Office Commissioning introduces the internal data configuration,

board loading, and checking and commissioning of the MSOFTX3000.
Chapter 5 Interconnection Commissioning introduces the data configuration and

commissioning of the MSOFTX3000 for connection with the MG and MSC.
Chapter 6 Service Commissioning introduces the configuration and testing of

service data of the MSOFTX3000.
Appendix A Commissioning Records of Newly-Built Office presents the

configuration and testing of service data of the MSOFTX3000.
Intended Audience
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.
Boldface Headings are in Boldface.

Courier New Terminal Display is in Courier New.
II. GUI conventions
Convention Description
Button names are inside angle brackets. For example, click

<>
the <OK> button.
Window names, menu items, data table and field names
[] are inside square brackets. For example, pop up the [New
User] window.
Multi-level menus are separated by forward slashes. For
/
example, [File/Create/Folder].
III. Keyboard operation
Format Description
Press the key with the key name inside angle brackets. For
<Key>
example, <Enter>, <Tab>, <Backspace>, or <A>.
Press the keys concurrently. For example, <Ctrl+Alt+A>

<Key1+Key2>
means the three keys should be pressed concurrently.
Press the keys in turn. For example, <Alt, A> means the
<Key1, Key2>
two keys should be pressed in turn.
IV. Mouse operation
Action Description
Select and release the primary mouse button without

Click
moving the pointer.
Press the primary mouse button twice continuously and
Double-Click
quickly without moving the pointer.

Action Description
Press and hold the primary mouse button and move the
Drag
pointer to a certain position.
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, Warning: Means reader be extremely careful during the operation.
Note: Means a complementary description.

HUAWEI MSOFTX3000 Mobile SoftSwitch Center Table of Contents
Table of Contents
Chapter 1 Overview of System Commissioning ........................................................................ 1-1

1.1 Explanation of SM.............................................................................................................. 1-1
1.2 Flow of SM ......................................................................................................................... 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-3
2.4.1 Checking Hardware Configuration .......................................................................... 2-3
2.4.2 Checking Power Supply .......................................................................................... 2-4
2.5 Checking Versions and Running of Software .................................................................... 2-5
2.5.1 Checking Software of BAM ..................................................................................... 2-5
2.5.2 Checking Software of Emergency Workstation....................................................... 2-7
2.5.3 Checking Software of LMT...................................................................................... 2-8
2.5.4 Checking Software of iGWB.................................................................................... 2-8
2.6 Checking Network Communication.................................................................................. 2-10
2.6.1 Networking of O&M System .................................................................................. 2-10
2.6.2 Method for Checking Network Communication..................................................... 2-14
2.6.3 Checking Communication of Internal LAN ............................................................ 2-14
2.6.4 Checking Communication of External LAN........................................................... 2-16
2.6.5 Checking Communication of WAN........................................................................ 2-17
2.7 Making a Backup of the Empty BAM Database............................................................... 2-18
Chapter 3 Data Configuration ...................................................................................................... 3-1

3.2 DC for Newly-Deployed Office........................................................................................... 3-1
3.2.1 DC Mode ................................................................................................................. 3-1
3.2.2 DC 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-2
3.4.1 Editing Data Script .................................................................................................. 3-2
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
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-5
4.4.3 Checking If Loading Is Successful .......................................................................... 4-8
4.4.4 Handling of Loading Problems ................................................................................ 4-9
4.5 Clock Commissioning ...................................................................................................... 4-10
4.5.1 Description of Clock System Networking .............................................................. 4-10
4.5.2 Checking Clock Cable Connection........................................................................ 4-12
4.5.3 Commissioning Steps for Locking BITS Clocks.................................................... 4-14
4.5.4 Commissioning Steps for Locking Peer Office Clocks.......................................... 4-14
4.6 Commissioning of Local Office Hardware ....................................................................... 4-15
4.6.1 Checking Indicator Status ..................................................................................... 4-15
4.6.2 Checking the Running of Hardware ...................................................................... 4-17
4.6.3 Hardware Switchover Verification ......................................................................... 4-18
4.6.4 Self-Loop Test for Local Office E1 Cables............................................................ 4-19
4.7 Modifying Settings of Loading Software Switch of Board................................................ 4-19
4.8 Setting Time for the Switch.............................................................................................. 4-20
Chapter 5 Interconnection Commissioning................................................................................ 5-1

5.2 Connecting with MGW ....................................................................................................... 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-8
5.3.3 Locating MTP Problems........................................................................................ 5-10
5.3.4 Treating MTP Common Problems......................................................................... 5-12
5.3.5 Locating SCCP/TCAP Problems........................................................................... 5-14
5.3.6 Treating SCCP Common Problems ...................................................................... 5-15
5.4 Connecting with HLR, SMC, SCP and SGSN ................................................................. 5-19
5.4.1 Description of Relevant Concepts......................................................................... 5-19
5.4.2 Steps of Commissioning ....................................................................................... 5-21
5.4.3 Locating and Treating Problems ........................................................................... 5-23
5.5 Connecting with MSC through ISUP & MAP/MTP........................................................... 5-23
ii
5.6 Connecting with MSC through ISUP/M3UA .................................................................... 5-27

5.6.3 Locating M3UA Problems ..................................................................................... 5-30
5.6.4 Treating M3UA Common Problems ...................................................................... 5-32
5.7 Connecting with MSC through BICC/SCTP..................................................................... 5-35
5.7.1 Description of Protocol .......................................................................................... 5-35
5.7.3 Locating BICC Problems....................................................................................... 5-40
5.7.4 Treating BICC Common Problems........................................................................ 5-41
5.8 Connecting with RNC ...................................................................................................... 5-42
Chapter 6 Service Commissioning .............................................................................................. 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-5
6.4.3 Handling of CPU Overload Problem ....................................................................... 6-6
Appendix A Commissioning Records of Newly-Built Office.....................................................A-1

A.1 Preparations for SM ..........................................................................................................A-1
A.2 Data Configuration.............................................................................................................A-3
A.3 Local Office Commissioning..............................................................................................A-4
A.4 Interconnection Commissioning ........................................................................................A-5
A.5 Service Commissioning.....................................................................................................A-8
Index ................................................................................................................................................ i-1
iii
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 1 Overview of System Commissioning
Chapter 1 Overview of System Commissioning
1.1 Explanation of SM
System commissioning (SM) refers to a series of testing and verification operations to
be performed after installing the hardware and software. The purpose is to ensure that
the system can meet the design requirements and can work stably, reliably, and
securely.
Before SM, make sure that the conditions below are met:
z Hardware installation and checking have been done, and the equipment is
powered on.
z Software installation and checking have been done (except board loading).
Note:
z For detailed hardware installation and checking, see HUAWEI MSOFTX3000
Mobile SoftSwitch Center Installation Manual Hardware Installation.
z For detailed software installation and checking, see HUAWEI MSOFTX3000 Mobile
SoftSwitch Center Installation Manual Software Installation.
1.2 Flow of SM
This manual details the method of SM for a newly deployed office with the
MSOFTX3000. The flow of SM is as shown in Figure 1-1.
1-1
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 1 Overview of System Commissioning
Start
Preparations
Data configuration
Local office
commissioning
Interconnection
commissioning
Service
commissioning
End
Figure 1-1 Flow of SM for a newly deployed office with the MSOFTX3000
The description of each step in the flow is listed in Table 1-1.
Table 1-1 Description of each step in the flow of SM for a newly deployed office with
the MSOFTX3000
Procedure Description
The step consists of the following:
z Checking the construction condition
1 Preparations for SM z Getting related technical files ready
z Checking system hardware, software and network
communication
z Making an empty backup file for the BAM database
Perform data collection and planning, and make and check data
2 Data configuration
script.
The step consists of the following:

Local office z Configure internal data (hardware data and local office data)
3
commissioning z Load boards and check them
z Perform commissioning to the local office equipment
Interconnection Perform data configuration and commissioning for the connection
4
commissioning between the MSOFTX3000 and the MGW, MSC, as well as HLR.
Service
5 Perform configuration and commissioning for service data.
commissioning
1-2
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 (SM), preparations must be made in
order that subsequent commissioning can be done smoothly.
The preparations include:
z Checking construction conditions
z Checking if 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
The following sections tell about the preceding items of the preparations, providing
checking methods and operation procedures. If you find abnormal situations during the
preparations, contact technical support engineers of Huawei Technologies Co., Ltd.
(Huawei for short) in time.
2.2 Checking Construction Conditions

Table 2-1 Checking the construction conditions
Item Description Result Remarks

Whether the hardware For the installation of hardware and
Y; N
installation is completed software, refer to HUAWEI
MSOFTX3000 Mobile SoftSwitch
Whether the installation of Center Installation Manual.
Hardware hardware has been Y; N
checked Software installation does not include
data configuration and board software
Whether the equipment is loading.
Y; N
powered on
2-1

Whether the software for
the BAM, local
maintenance terminal
Y; N
(LMT) and emergency
workstation (EWS) has
been installed
Software Whether the virtual local
area network (VLAN) of
Y; N
the core LAN Switch has
been configured
Whether the installation of
software has been Y; N
checked
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
Network Plan Y; N designated 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
Engineering department of Huawei based on the office configuration and
Y; N
Documents networking of the customer, and to be delivered to the site
with the equipment.
The 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 The documents include the contract agreement, system

Y; N
Documents configuration table and delivery list.
2-2
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).
Caution:
z When inserting a board into a subrack, if the plugging indicator (in blue) is on, it
shows 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

Check the If hardware
Whether the BAM server, iGWB server,
server and configuration is not
LMT, EWS, and alarm box are Y; N
auxiliary consistent with the
consistent with the delivery list
equipment delivery list and
Engineering
Whether the number of cabinets and Documents, contact
Check the
subracks is consistent with that written Huawei technical
cabinets and Y; N
in the delivery list and Engineering support staff for help at
subracks
documents. once.
Whether the configuration of boards in For description of DIP
subracks is consistent with the delivery switches of the WSIU,
Check board
list and the Engineering Documents, Y; N refer to HUAWEI
configuration MSOFTX3000 Mobile
and whether board positions are
correct. SoftSwitch Center
2-3

Check software versions and hardware Hardware Description
Check board Manual.
versions of boards according to the Y; N
versions
version configuration information.
Check the
Whether the setting of DIP switch S3 of
setting of
the WSIU is consistent with the subrack Y; N
subrack
number.
numbers
2.4.2 Checking Power Supply
Table 2-4 Checking the power supply

Whether all the 48 V power
output switches in the power
Y; N
distribution subrack are set to
ON.
Whether the green RUN Note:

Check the indicator on the front panel of When the WSMU has not been
power the power distribution subrack Y; N powered on or the software of it
distribution flashes, and the red ALM has not been loaded, the ALM
subrack indicator is off. indicator of the power distribution
subrack will flash at 4-Hz rate with
Whether the alarm sound an alarm sound. This shows that
stopping switch on the front the communication between the
panel of the power distribution Y; N power distribution subrack and
subrack is on, and the alarm the WSMU is interrupted. You
buzzer is silent. need not worry about it.
Note:
When the WSMU is not powered
on or the software of it is not
loaded, the STATUS indicator of
Check Whether the fans run normally, the fan box will blink fast. It shows
subrack and the STATUS fan indicator Y; N that the communication between
fans flashes in green. the fan box and the WSMU is
interrupted. You need not worry
about it. If the STATUS indicator
blinks fast in red, it shows that the
fan is faulty.
Whether the green RUN
Check
indicator on the UMSC PSM
power
power module (UPWR) is on, Y; N
boards in
and the red ALM indicator is
subracks
off.
Whether the indicator of the

Check the If this indicator is in orange, it
BAM and iGWB power switch is Y; N
server shows that the server is standby.
in green.
2-4

Whether the green POWER
hCheck If the POWER indicators are not
indicators on the panels of LAN
the LAN Y; N on, it shows that power supply for
Switch 0 and LAN Switch 1 are
Switch the LAN Switches is faulty.
on.
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 EWS after checking the software installation. This is vital for the
commissioning.
2.5.1 Checking Software of BAM
Table 2-5 Checking the software of the BAM

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

On the BAM, double-click the
icon in the taskbar on the If the status of a process is
bottom right corner of the Exception, it shows that the
desktop to display the [BAM process is abnormal. You can
Manager] window. Check solve the problem by closing the
Check the
service processes, including BAM server program and then
running of Y; N
Warn, DataMan, restarting it. If the problem still
processes
Maintain, Stats, MML, exists, contact Huawei
Exchange, FTPMan, technicians for help at once, and
XSman, and NTPClient, to re-install the BAM software if
see if their statuses are all necessary.
Started.
On the BAM, open the log file
under the installation directory
of SetWin2000 to check if
Check the
security items have been The default installation directory
SetWin2000
customized. For example, is: C:\Program Files\Huawei
security Y; N
Setting directory access Technologies Co., Ltd\Windows
customizatio
authority control completed 2000 security customization tools
n tool
shows that you have set
directory access authority
control.
On the BAM, select [Start /

Programs / Administrative
Tools / Services]. The
Check [Service] window appears.
Y; N
SysPatron Check _UM_PPT_Service.
Its status should be Started
and its startup type
Automatic.
On the BAM, select [Start/Shut

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

Manager] window will pop up
If BAM Manager cannot run
automatically, and the automatically or some service
icon appears in the taskbar on processes are in the Exception
the bottom right corner of the status, it shows that the system
desktop, indicating that BAM cannot run normally or the
Manager can run Y; N
installation of the BAM server
automatically. software fails. If this is true,
contact Huawei technicians for
Check all the service help at once and re-install the
processes on the [BAM BAM software if necessary.
Manager] window to see if
their statuses are all Started.
2.5.2 Checking Software of Emergency Workstation
Table 2-6 Checking the software of the EWS

On the EWS, start HUAWEI
Local Maintenance Terminal, If the software version is not the
select [Help/About], check the same as that of the BAM server
Check
version of the software, and software or cannot meet site
software Y; N
confirm if the version is identical deployment requirement, contact
version
with that of the BAM server Huawei technicians for help at
software and if it meets the once.
requirement of site deployment.
Check the On the EWS, check if the icon If the icon is there, it shows that
running of appears in the taskbar on the the SQL Server 2000 service
Y; N
the SQL bottom right corner of the manager can start automatically
Server desktop. and can run normally.
On the EWS, select

[Start/Programs/Administrative
Tools/Services] to display the
You can start a service or modify
[Services] window, check the
its startup type in the [Services]
status of services BAM Service
Check the window by double-clicking this
and Smirror. The status of
running of Y; N service. If this fails, contact
Smirror should be Started
services Huawei technicians for help at
and its startup type should be
once, and re-install the software
Automatic. The status of BAM
of the EWS if necessary.
Service should be Stopped,
and its startup type should be
Manual.
2-7
2.5.3 Checking Software of LMT
Table 2-7 Checking the software of the LMT

On a MSOFTX3000 client, start If the version of the software is not
HUAWEI Local Maintenance the same as that of the BAM
Terminal, select [Help/About], server software or does not meet
Check
check the version of the software, the requirement of site
software Y; N
and confirm if the version is deployment, contact Huawei
version
identical with that of the BAM technicians for help at once; and
server software and meets the re-install the BAM software if
requirement of site deployment. necessary.
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

On the iGWB operation and
maintenance terminal, select
If the version of the software does
[Start/Programs/iGateway Bill
not meet the requirement of site
Check V200 Client/iGWB Client] to
deployment, contact Huawei
software start and log in to the bill Y; N
technicians for help at once; and
version console. Select [Help/About] to
re-install the iGWB software if
check if the software version
necessary.
meets the deployment
requirement.
maintenance terminal, select This operation only applies to
[Start/Programs/iGateway Bill dual-system configuration office.
V200 Client/iGWB Client] to
Check For 2/2, the denominator shows
start and log in to the bill
dual-system Y; N the total number of heartbeat
console. Select
heartbeat links, and the numerator shows
[Operation/State Query] to
check the heartbeat state. the number of current available
Normally, the heartbeat state links, which should be the same.
should be 2/2.
2-8

On the active iGWB server, all the
processes should be running.
On the standby iGWB server, only
Start Windows 2000 task
the process cls_proc.exe should
manager on the active and
be running.
standby iGWB servers, and
Check the The number of the process
then click [Processes] tab to
running of Y; N ap_proc.exe on the active iGWB
check if such processes as
processes server should be the same as the
cls_proc.exe, ap_proc.exe,
knl_proc.exe, and value set for the parameter
om_proc.exe are running. 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] to display If you are prompted to press the
the [Shut Down Windows] combination keys <Ctrl+Alt+Del>
window, select Restart for for login, it shows that the setting
Check iGWB
operation type, and then Y; N for automatic login to Windows
restart
restart the iGWB. After restart, 2000 Server fails. Refer to the
the system will automatically iGWB User Manual to redo the
log in to the iGWB server as setting.
the Administrator. You need
not input the login password.
Close the active iGWB (iGWB If the switchover between the

0).After five minutes, the active and standby iGWB servers
standby iGWB server (iGWB fails, or some processes cannot
1) becomes the active one, its run normally, or the currently
Check iGWB power indicator is on in green, active iGWB is not normal, it
Y; N
switchover and the processes shows that the MSOFTX3000 has
cls_proc.exe, ap_proc.exe, problems in operation or the
knl_proc.exe, and installation of the iGWB server
om_proc.exe are running software fails. In this case,
normally. contact Huawei technicians for
help at once and re-install the
On the iGWB operation and iGWB software if necessary.
start and log in to the bill Y; N
console. Select
check if the active iGWB is in
normal state.
2-9

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.

start and log in to the bill
console. Select Y; N
check if the active iGWB is in
normal state and if the
dual-system heartbeat state is
normal.
2.6 Checking Network Communication

Since SM 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.6.1 Networking of O&M System
Figure 2-1 shows the O&M system of the MSOFTX3000.
2-10
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 Sw itch 0 LAN Sw itch 1
Bound to Bound to
Billing Center Billing Center
WAN WAN
Emergency
standby iGWB BAM active iGWB
w orkstation
HUB or LAN
Sw itch Bound to
NMC WAN
LMT LMT
Figure 2-1 The O&M system of the MSOFTX3000
I. IP Address of the BAM Server
The BAM server has four network adapters. IP addresses of the BAM are listed in
Table 2-9.
Table 2-9 Setting the IP addresses of the BAM
Network
Opposite equipment IP address/mask
adapter ID
It communicates with the LMT and the
Network To be provided by the
EWS through an external HUB or LAN
adapter 0 customer
Switch.
It is bound to LAN Switch 0, and 172.20.200.0/

Network
communicates with the active plane of
adapter 1 255.255.0.0
the host.
It is bound to LAN Switch 1, and 172.30.200.0/

Network
communicates with the standby plane
adapter 2 255.255.0.0
of the host.
Network
Standby
adapter 3
2-11
II. IP Address of Emergency Workstation
The emergency workstation has four network adapters. IP addresses of the emergency
workstation are listed in Table 2-10.
Table 2-10 Setting the IP addresses of the EWS
Network adapter
Opposite equipment IP address/mask
ID
It communicates with the BAM through an To be provided by
Network adapter 0
external HUB or LAN Switch. the customer
It is standby. In emergency cases, it is 172.20.200.0/
Network adapter 1 connected to LAN Switch 0 for
communicating with the host. 255.255.0.0
It is standby. In emergency cases, it is 172.30.200.0/

Network adapter 2 connected to LAN Switch 1 for
communicating with the host. 255.255.0.0
Network adapter 3 Standby
III. IP Address of LMT
A client on which the LMT is installed has one network adapter. The IP address of the
LMT is listed in Table 2-11.
Table 2-11 Setting the IP address of the LMT
Network
Opposite equipment IP address
adapter ID
Network It communicates with the BAM through To be provided by the
adapter an 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 set for each WSMU either before or after board loading, as shown
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 172.30.subrack
Before WSMU in slot 6
number.100/16 number.100/16
board
loading 172.20.subrack 172.30.subrack
WSMU in slot 8
number.101/16 number.101/16
2-12
Slot IP address 1 / mask IP address 2 / mask

172.20.200.module 172.30.200.module
After WSMU in slot 6
number/16 number/16
board
loading 172.20.200.module 172.30.200.module
WSMU in slot 8
number/16 number/16
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
Network
Network Opposite adapter IP of Virtual
adapter IP of
adapter ID equipment standby IP/mask
active iGWB
iGWB
It is bound to the bill
console and network
To be
management system
Netcard0 to provided
interface, and acts as 130.1.3.1 130.1.3.2
Office LAN by the
the first heartbeat link
customer
of the iGWB
dual-host system.
2-13
Network
Network
Network Opposite adapter IP of Virtual
adapter IP of
adapter ID equipment standby IP/mask
active iGWB
iGWB
It is bound to LAN 172.20.20
Netcard1 to Switch 0, and 0.1/
0#LAN communicates with 130.1.1.1 130.1.1.2
Switch the active plane of 255.255.0
the host. .0
It is bound to LAN 172.30.20

Netcard2 to Switch 1, and 0.1/
1#LAN communicates with 130.1.2.1 130.1.2.2
Switch the standby plane of 255.255.0
the host. .0
It is bound to the To be
Netcard3 to
billing center, and provided
Billing 130.1.4.1 130.1.4.2
provides billing by the
Center
interface. customer
2.6.2 Method for Checking Network Communication
The BAM, LMT, EWS, 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 shows 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 shows that the
communication is normal. If the time in the returned information is too long or the
information returned is "Request Timed out", it shows 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
2-14
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

Check if the IP addresses of
Check the the BAM and iGWB are In the internal LAN, the IP
setting of the correctly set based on the Y; N address of each component is
IP address description in 2.6.1 I. IP fixed.
Address of the BAM Server.
On the BAM, ping the IP
address of the WSMU in
each subrack (for the IP
Check the address setting, refer to 2.6.1
communication IV. IP Address of WSMU). If
Y; N
between the the ping command is
BAM and host executed successfully, it
shows that the
communication between the
BAM and host is normal. If the ping command is not
executed successfully, it shows
Ping the IP addresses of the that the communication is
Check the iGWB 172.20.200.1 and abnormal. Check the connection
communication 172.30.200.1 from the BAM. of Ethernet cables, if the IP
between the If the ping command is Y; N addresses of the BAM and iGWB
BAM and executed successfully, it are correctly set, and if the DIP
iGWB shows that the switch on the WSIU that
communication is normal. determines subrack numbering is
correctly set.
On the iGWB, ping the IP
address of the WSMU in
each subrack (for the IP
Check the
address setting, refer to 2.6.1
communication
IV. IP Address of WSMU). If Y; N
between the
the ping command is
iGWB and host
executed successfully, it
shows that the
communication is normal.
Based on the description in

HUAWEI MSOFTX3000
Mobile SoftSwitch Center
For details, refer to the
Installation Manual
Check the description on setting VLAN in
Software Installation, log in to
setting of Y; N HUAWEI MSOFTX3000 Mobile
the LAN Switch through a
VLAN SoftSwitch Center Installation
serial port, execute the
Manual Software Installation.
command display vlan all,
and check if VLAN is
correctly set.
2-15

Turn off the power switch
(SW6) of LAN Switch 1.
Check if the communication
between the BAM and the Y; N
host is normal or not
according to the related Caution:
description above. Before turning off the power
Check the switch of LAN Switch, make sure
Ethernet Turn on the power switch of you have saved the current data
biplane LAN Switch 1 (SW6), and of the LAN Switch.
switchover turn off the power switch Note:
function (SW5) of LAN Switch 0.
After logging in to the LAN
Check the communication
Switch, you can enter the save
state between the BAM and Y; N command to save the current
the host according to the
configuration of the LAN Switch.
related description above..
After the check, turn on the
power switch (SW5) 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 EWS 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.
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

In the external LAN, the IP
Check the Check if the IP addresses of the
address of each component
setting of IP BAM, LMT, EWS, and iGWB are Y; N
is to be provided by the
addresses correctly set.
customer.
2-16

Ping the IP address of the LMT on
Check the
the BAM; ping the IP address of the
communicati
BAM from the LMT. If the ping
on between Y; N
command is executed successfully,
the BAM and
it shows that the communication is
LMT
normal.
If the communication is
Ping the IP address of the EWS on abnormal, check if the IP
Check the
the BAM; ping the IP address of the address of each component
communicati
BAM from the EWS. If the ping is correctly set, if Ethernet
on between Y; N
command is executed successfully, cables are correctly
the BAM and
it shows that the communication is connected, and if the
the EWS
normal. external HUB or LAN
Switch works normally.
Ping the IP address of the iGWB
Check the
from the BAM; ping the IP address
communicati
of the BAM from the iGWB. If the
on between Y; N
ping command is executed
the BAM and
successfully, it shows that the
iGWB
2.6.5 Checking Communication of WAN
As shown in Figure 2-1, the BAM server is connected to the NMC over the 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.
Table 2-16 Checking the communication of the WAN

Ping the IP address of the NMC
Check the server (to be provided by the
communication customer) on the BAM. If the ping If the communication is
Y; N abnormal, check if the IP
between BAM command is executed
and NMC successfully, it shows that the address is correct, if
communication is normal. Ethernet cables are
correctly connected, if
Ping the IP address of the billing devices connected to the
Check the
center server (to be provided by WAN (like routes) can
communication
the customer) from the iGWB. If work normally, and if route
between the Y; N
the ping command is executed data is correctly set.
iGWB and billing
successfully, it shows that the
center
2-17
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 GUI guide.
Before data configuration, you need to make a backup of the empty BAM database with
SQL Server Enterprise Manager, so that you can empty the 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.
Figure 2-2 [SQL Server Enterprise Manager] window
2-18
Figure 2-3 [SQL Server Backup- Bam] dialog box
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
2-19
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-20
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 3 Data Configuration
Chapter 3 Data Configuration

Data configuration (DC) for an office with the MSOFTX3000 is a key part of the
system. DC is vital to the normal running of the system. The quality of a network also
depends on it.
To complete DC fast and effectively, do the following:
z Data collection and planning:
Understanding the networking
Collecting equipment configuration data, external interface data and
interworking negotiation data
Planning the distribution of resources and describes it in a chart
z Data script editing and checking based on the actual situation:
Making/editing data script files
Checking the correctness
Note:
For details of DC, refer to HUAWEI MSOFTX3000 Mobile SoftSwitch Center
Operation Manual Configuration Guide.
3.2 DC for Newly-Deployed Office

3.2.1 DC Mode
For a newly deployed office, the first DC is often done by loading data script files. This
will raise efficiency and reduce errors. A data script file is a text-only file. It contains
MML commands that can be executed in a row.
3.2.2 DC Sequence
The order of DC for a new office is as follows:

1) Configuring internal data, including hardware data and local office data (for
example, signaling point code)
2) Configuring external interface data, including interface data for the interworking
between the local office and other network elements (for example, interface data
used to link with other MSCs)
3-1
3) Configuring service data, including number analysis data, mobile service data
and IN service data
3.2.3 Method for Executing Data Script
Usually, DC is done on the LMT. The method is detailed 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> to display the
[MML Batch] window.
4) On the [Immediate Batch Command] tab, click [Open]. Select a data script file to
be executed.
5) Set [Running Model] to "Manual Run" and [Execution Type] to "Execute All".
Click <Go>.
6) During the execution, if any error is found with the MML commands, parameters
or grammar in the data script file, a window prompting for confirmation 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 Total Result box in the
lower part of the window.
8) Close the [MML Batch] window.
3.3 Data Collection and Planning

To carry out DC fast and effectively, data collection and planning are required before
DC. Follow the description in HUAWEI MSOFTX3000 Mobile Softswitch Center
Operation Manual Configuration Guide for data collection. And fill out corresponding
data collection forms about the following:
z Networking mode
z Equipment configuration: board configuration in subracks, links provided by
boards
z Data for external interfaces and interworking negotiation: signaling link, IP
addresses, port numbers
z Service data
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. The files are
required based on the DC order, and each is in charge of a specified part of the DC.
3-2
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, and its contents are MML commands that can be
executed in a row. It can be edited with a text editing tool (like Notepad) or generated
on the LMT 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 given 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 the system
reliable, effective and maintainable and have future capacity expansion in mind.
3.4.2 Checking Data Script
After editing the data script, check it according to the following items:
z Networking data
z External interface data
z Interworking and negotiation data
z Service data collected on site
3-3
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 4 Local Office Commissioning
Chapter 4 Local Office Commissioning
4.1 Chapter Contents in Brief

This chapter is about 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, and the
BAM loads programs and data to memories of boards across the internal Ethernet
linked 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 choose program and data loading path.
Factory setting of the board loading software switch:
4-1
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 writable): 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 often loaded from the BAM hard disk to the memory
of a board:
1) 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. For details of the setting modification, see step 5
of Table 4-1.
2) 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. For details of
the setting modification, see section 4.7 Modifying Settings of Loading Software
Switch of Board.
To effectively locate faults occurred during loading process, power off and on frames
one by one.
4.2.4 Description of Source Files Related to Loading
I. Host Software Files
After installing 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, the 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 are set and the format conversion command FMT is entered, 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. The files have
a prefix of DB_.
4-2
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
quicken the loading speed. Besides, host software files with board names (for example,
.smu and .ifm) as their suffixes will also be compressed. To tell apart the files, you
need give them 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 prepare for board loading.
Table 4-1 Steps for the internal data configuration
Step Operation Remarks

On the LMT, start the client If you cannot log in to the BAM,
program of the check if the username and
Start the
1 MSOFTX3000 O&M password are correct, and if the
LMT client
software, and log in to the cable between LMT and BAM is
BAM. properly connected.
Open the MML window and
Offline, and The meanings of the commands:
execute the following
format commands: LOF: Offline
2
conversion SET FMT: format conversion
LOF:;
off on/off
SET FMT: STS=OFF;
For detail on operations to data

Press shortcut keys <Ctrl + script files, refer to section 3.2.3
E> to display the [MML Method for Executing Data
Batch] window, and Script in Chapter 3.
execute data script files in For commands that fail in the
Execute sequence. execution, use the empty BAM
3 data script Upon completing every database backup to recover the
files script, check the Total database, so as to clear the
Result box in the lower configuration data. For detail on
part of the window, to see if database backup and recovery,
the MML commands are all refer to HUAWEI MSOFTX3000
executed successfully. Mobile Softswitch Center
Operation Manual GUI guide.
Execute the following

commands in the MML The meanings of the commands:
Format SET FMT: format conversion
4 conversion window:
on/off
on, online SET FMT: STS=ON;
LON: online
LON:;
4-3
Modify the Execute the following The meaning of this command:

loading command in the MML Modify the loading software
5 software window: MOD LSS: switch of a board as program
switch of a PE=NO, DE=NO, unavailable, data unavailable,
board DW=YES, PW=YES; data writable, program writable.
It will take quite a long time to
Execute the following execute the command FMT. If the
commands on the MML system prompts executing
6 Format data window: command timeout, select
[System/Command Timeout
FMT:; Setting] on 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
On the BAM, double-click the

icon in the taskbar on the lower
Check the right corner of the desktop to Refer to section
running of display the [BAM Manager] 2.5.1 Checking
Y; N
BAM window. Check service Software of BAM
processes processes, including Exchange in Chapter 2.
and DataMan, to see if their
statuses are all Started.
Check the Ping the WSMU of each subrack Refer to section

communicati on the BAM. If the ping command 2.6.3 Checking
on between is executed successfully, it shows Y; N Communication of
the BAM and that the communication is Internal LAN in
host normal. Chapter 2.
Refer to section
Check the directory D:\Data\ of 4.2.4 Description
Check the
the BAM to see if the load source Y; N of Source Files
files loaded
files are there. Related to
Loading.
4-4
4.4.2 Loading Process
I. Operation Steps
Table 4-3 Steps for loading boards

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

subrack in the integrated processing
cabinet to on, and power on the At this time, do not set
2 SW5 to on for fear that
basic subrack. If the system works
normally, software and data will be expansion subrack 1 is
automatically loaded from the BAM. powered on.
On the BAM, double-click the icon

in the taskbar on the lower right corner
of the desktop to open the [BAM If there is no loading
Manager] window. Select the request, check the
3 Exchange process in the Service connection of Ethernet
cables and the setting of
Power on column. Click the icon in the SWIU DIP switches.
the basic toolbar to open the [Exchange]
subrack window. Check if there is any loading
and start request for the basic subrack.
loading
Load the WSMU first, and then the Blinking frequency of the
other front boards, excluding the RUN indicator for
UPWR and wireless alarm unit different cases:
4 (WALU). Program loading: 4 Hz;
Observe the green RUN indicator on Normal running: 0.5 Hz;
the front board. Its blinking frequency Standby board
during loading is 4 Hz. indication: 0.25 Hz.
If the loading fails, find

After loading, check if the loading is and remove the fault
5 successful by referring to 4.4.3 first. Then go on loading
Checking If Loading Is Successful. the boards in the other
subracks.
After confirming the basic subrack has If there is no loading
been successfully loaded, set SW5 request, check the
Power on
and SW6 of the power distribution connection of Ethernet
expansion
subrack in the integrated processing cables and the setting of
6 subrack 1
cabinet to on, and power on SWIU DIP switches.
and start
expansion subrack 1. If the system If the loading fails, solve
loading
works normally, it will load the software the problem. Go on
and data automatically from the BAM. loading other expansion
4-5

Refer to Step 3. Open the [Exchange] subracks only after the
7 process window and check if there is problem has been
any load request. solved.
Refer to Step 4. Observe the green

RUN indicator on the front board. Its
8
blinking frequency during loading is 4
Hz.
After loading, check if the loading is
9 successful by referring to 4.4.3
Checking If Loading Is Successful.
Power on For the relations
other Follow the above steps to power on between cabinet
expansion other expansion subracks and restart components and
10
subracks them one by one, and check if loading switches of the power
and start is successful. distribution subrack,
loading refer to Table 4-4.
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
Caution:
Relations between cabinet components and switches of the power distribution subrack
are listed in Table 4-4. The relations between them may vary with different equipment.
Take labels on the power distribution subrack of the actual delivered equipment as the
correct relation indications.
4-6
Table 4-4 Relations between cabinet components and switches of the power
distribution subrack
Cabinet type Switch Component

SW5, SW6 SUBRACK-1 (Expansion
subrack 1)
SW4, SW5 SUBRACK-0 (Basic subrack 0)

SW3 KVMS
SW6 LANS-1
Integrated SW5 LANS-0
configuration
cabinet SW1, SW6 ARRAY (Hard disk array)
SW2, SW3 SERVER-3 (BAM)
SW2, SW3 SERVER-2 (iGWB 1)
SW1, SW2 SERVER-1 (iGWB 0)
SW1, SW2 SERVER-0 (A server for other

services, Optional)
SUBRACK-3 (Expansion
SW1, SW2
subrack 5)
SW2, SW3
Service processing subrack 4)
cabinet SUBRACK-1 (Expansion
SW3, SW4
subrack 3)
SW5, SW6
subrack 2)
4-7
4.4.3 Checking If Loading Is Successful
Table 4-5 Checking after loading boards

Relations between board
On the LMT client
indicator colors and board
maintenance console, click
running statuses:
the [Device Panel] tab,
select [Device Green: The board is running
Management], open the normally and in the active
equipment panel view, and state.
check the running of Blue: The board is running
boards. normally and in the standby
Note: state.
Check the
running of On the front view of a Y; N Red: The board has fault.
boards subrack, there are some Gray: No board has been
small squares, indicating configured for this slot.
the statuses of back boards
Also, there are two small
in corresponding slots. To
squares on the wireless
find detailed information of
calling control unit and
a board, double-click the
signaling process unit
triangle on the left side of
(WCSU), which shows the
the subrack view. A
running of the upper pinch
subrack status diagram of
card and lower pinch card on
the board will be displayed.
the WCSU.
If not, run the LST LSS
command to check if the
On the LMT client, execute switches for software loading
the DSP EXVER command of the board are correctly
to query the software set, that is, if they are set to
Check program unavailable, data
versions of all boards
board unavailable, data writable,
(modules) that can be Y; N
software and program writable
loaded, and confirm if they
version respectively.
are consistent with the
software version of the If the switches are not in
BAM. such statuses, adjust them
accordingly. After that, reset
the board and reload it.
If the check fails, reset the
board and reload it.
!Note:
On the LMT client, run the
command STR It will take quite a long time
Verify CRC:MN=255; to perform to execute the command
board the cyclic redundancy Y; N STR CRC. If the system
data check (CRC) on the data of prompts executing
boards (modules) that can command timeout, select
be loaded. [System/Command Timeout
Setting] on the LMT client
to extend the time-out
setting.
4-8
4.4.4 Handling of Loading Problems
I. Basic Solution
In most cases, check the items below when problems occur in loading:
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 notice the information and alarms on the [Exchange] window of the BAM
server, for you may find clues to problems that occur.
z 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 appears to show that the
communication is 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 if the DIP switches of the WSIU that determine the subrack
number are correctly set, and if Ethernet cables are properly connected. Also, errors in
configuring some critical data may lead to board loading failure.
z Failure in loading other boards
Other boards are loaded from the BAM through the WSMU. So if failure occurs in
loading other boards, check if the WSMU runs normally.
4-9
4.5 Clock 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 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 as shown 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 Expansion frame B

(rear view) (rear view)
Figure 4-1 Networking for the MSOFTX3000 locking BITS clocks
1) 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.
2) Internal clock cable and reference source
4-10
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.
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 Expansion frame B

(rear view) (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.
4-11
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 get 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.
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.
4-12
Table 4-6 Checking the connection of clock cables

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

The 8k clock cables outputted from twisted pair cable with
the active and standby WCKIs of the shielded crystal
basic subrack should be respectively connectors, like a
connected to a pair of active and straight through cable.
standby WEPIs of each expansion
Check internal subrack (defaulted as slots 0 and 1). If the WEPI connected
Y; N with the 8k clock cable
clock cables The 8K-A interface of the WEPI is
connected to the WCKI in slot 13 of is not in slots 0 and 1
the basic subrack, and the 8K-B of expansion
interface of the WEPI is connected to subracks, data needs
the WCKI in slot 15 of the basic to be modified using
subrack. the SET CLKSRC
command.
4-13
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 If the status is Free Run, it shows
of the clock phase-locked that the clock phase-locked loop
loop circuit of the WCKI. circuit on the WCKI cannot normally
If the status is Trace Mode, trace the BITS clock.
Check the status of the it shows that the clock Then, run the LST CKICFG command
clock phase-locked phase-locked loop circuit on to carefully check if the configuration
loop circuit of the WCKI the WCKI can normally trace for the following parameters is correct:
the BITS clock. clock level, work mode, priority of
Note: each clock source, signal type of the
The phase-locking time of the BITS1 interface, and signal type of the
WCKI is relatively long, about BITS2 interface.
half an hour.
If the clock status of a WEPI is
abnormal, proceed as follows:
Run the DSP CLKSTAT
command to sequentially Run the LST CLKSRC command to
check the clock statuses of check if the clock reference sources of
WEPIs (as clock sources) in WEPIs of each subrack are correctly
expansion subracks to see if configured.
Check the clock status
of the WEPI they are normal. If the clock data is correct, check if the
!Note: clock wiring inside the device is
correct.
By default, WEPIs in slots 0
and 1 of each expansion If both the clock data configuration
subrack act as clock sources. and clock wiring are correct, check if
WEPIs as clock sources can work
normally.
4.5.4 Commissioning Steps for Locking Peer Office Clocks
Table 4-8 Commissioning steps for the MSOFTX3000 to lock peer office clocks

Run the DSP PORT command to
Check the check the status of the E1 port on The WEPI can introduce the E1 clock of
statuses of E1 a WEPI of this office that locks the peer office only when the E1 port of
ports the E1 clock of a peer office and this office is in the Normal status.
see if it is normal.
4-14

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 shows that
the clock phase-locked loop circuit on
If the status is Trace Mode, it
the WCKI cannot normally trace the
Check the status shows that the clock
peer office clock.
of the clock phase-locked loop circuit on the
phase-locked loop WCKI can normally trace the Then, run the LST CKICFG command
of the WCKI peer office clock. to carefully check if the configuration for
the following parameters is correct:
!Note:
clock level, work mode, and priority of
The phase-locking time of the each clock source.
WCKI is relatively long, about half
an hour.
If the clock status of a WEPI is

Run the DSP CLKSTAT abnormal, proceed as follows:
command to sequentially check
Run the LST CLKSRC command to
the clock statuses of WEPIs (as
check if the clock reference sources of
clock sources) in expansion
WEPIs of each subrack are correctly
Check the clock subracks to see if they are
configured.
status of the WEPI normal.
If the clock data is correct, check if 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 sources. clock 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

By pressing the MODE button
on the front board, the port state
Whether the power indicator is switched to A/L. The
indicators of LAN Switch 0 normal state of the Ethernet port
and LAN Switch 1 are on, indicator is as follows:
Check the LAN and whether the indicators The yellow "Active" indicator at
Y; N
Switch of all Ethernet interfaces the left side of the port flashes, it
that have been properly shows data sending and
connected and put into use receiving is normal.
are in normal statuses. The green "Link indicator at the
right side of the port lights up, it
shows the link is normal.
4-15

If the RUN indicator is off, it
shows that there is no power
indicator on the front panel
input or the power distribution
of the power distribution
Y; N subrack is faulty. If the ALM
subrack flashes at 0.5-Hz
indicator is on, it shows that the
rate, and the red ALM
power distribution subrack is
Check the power indicator is off.
faulty.
Whether the alarm sound
If the alarm sound stopping
stopping switch on the front
switch is off, there will be no
panel of the power
Y; N alarm prompt tone when the
distribution subrack is on,
power distribution subrack is
and the alarm buzzer is
faulty.
silent.
If the "STATUS" indicator
flashes fast in green, it shows
Whether fans run normally,
that the communication
and the green STATUS
Check fans Y; N between the fan and the WSMU
indicator flashes at 0.5-Hz
is faulty. If the "STATUS"
rate.
indicator flashes in red, it shows
that the fan is faulty.
If the RUN indicator is off, it
shows that the board is faulty. If
Whether the RUN
it is red, it shows that the
indicator on the WALU is Y; N
on.
board and the WSMU is in
trouble.
Blinking frequency of the RUN
Except on the UPWR and
indicator for different cases:
Check the WALU, whether the green
indicators on front RUN indicators on the Program loading: 4 Hz;
Y; N
boards front panels flash, and the Normal running: 0.5 Hz;
red ALM indicators are
Standby board indication: 0.25
off.
Hz.
The LINK indicator is a

Whether the green
network connection indicator. It
Ethernet port indicator,
Y; N is on when the physical
LINK, on the IP forward
connection is normal, and is off
module (WIFM) is on.
in other cases.

indicator on the WEPI
If the ALM indicator flashes, it
flashes at 0.5-Hz rate, and Y; N
shows that the board is faulty.
the red ALM indicator is
Check indicators on off.
back boards Whether the green RUN
indicator on the WCKI If the ALM indicator is always
flashes at 0.5-Hz rate, and Y; N on, it shows that the board is
the red ALM indicator is faulty.
off.
4-16
Note:
For detailed meanings of board indicators, see the "Boards" chapter of HUAWEI
MSOFTX3000 Mobile SoftSwitch Center Hardware Description Manual.
4.6.2 Checking the Running of Hardware
Table 4-10 Checking the running of hardware

Run the DSP ENVSTAT command
to check the statuses of the power The statuses should all be
Check the power
distribution subrack, input power, Normal under normal
temperature, humidity and the conditions.
output switch.
The statuses should all be
Run the DSP FAN command to
Check fans Normal under normal
check the running of fans.
conditions.
The statuses must not be
Run the DSP FRM command to
Fault under normal
check the statuses of fans.
conditions.
Run the DSP BRD command to
check the status of the WALU of For example:
each subrack and the subrack DSP BRD: FN = 0, SN = 16;
temperature.
Run the DSP COMM command
and select TCP for port type For example:
Check boards (COMT) to check the DSP COMM: FN = 0, SN = 6,
communication between the COMT = TCP;
WSMU and BAM.
Run the DSP COMM command Usage of each serial port:

and select SP for port type 016: back boards in
(COMT) to check the corresponding slots;
17: WALU;
WSMU and the serial ports of the
back boards, WALU, fan, and 18: fan;
power distribution subrack. 19: power distribution subrack.
Statuses of FE ports (service

Run the DSP PORT command to
Check FE ports Ethernet ports) should all be
check the statuses of FE ports.
Normal.
4-17
On the LMT client, use the PING If the returned information is

function to check if the connection Reply from *.*.*.* ...
between the WIFM and the default time<10ms ..., it shows that
Check the gateway is normal. the communication is normal.
communication between If the time in the returned
!Note:
the WIFM and the default information is too long, or if the
gateway. The IP address, mask and default returned information is
gateway of the WIFM have been Request Timed out, it shows
defined in the ADD FECFG that the communication is
command. abnormal.
4.6.3 Hardware Switchover Verification
Table 4-11 Operation steps for the verification of hardware switchover

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 shown in red, while the
standby in blue.
3) Observe the board indicators. The frequency of Caution:
the RUN indicator of the active board should After the initial
be 0.5 Hz, and that of the RUN indicator of the switchover for a
Verification of the standby 0.25 Hz. board, perform
active/standby 4) Run the DSP FRM command to check the switchover again to
switchover for the statuses of the active and standby boards after restore the original
front boards the switchover. The status of the active board configuration, and at
should be Main OK, and that of the standby the same time
board Standby OK. observe if the
5) Run the SWP BRD command again to perform switchover is
active/standby switchover. successful.
6) Follow Steps 24 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 if the switchover is
successful.
4-18
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 operators staff or its
authorized engineers.
Table 4-12 Self-loop test for E1 cables of the local office

Take out the connectors of the E1 system on the
1
distribution subrack.
Perform local self-loop test on the first E1 with a
2
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
4 perform 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.
4-19
z DE=YES (data available): Data 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-20
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 5 Interconnection Commissioning
Chapter 5 Interconnection Commissioning

This chapter details 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 (MGW);
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 MGW

5.2.1 Description of Relevant Concepts
I. Description of Protocol
The MGW works with the MSOFTX3000 to fulfill the mobile switching function of the
core network. Usually, Huaweis UMG8900 is used as the MGW.
The protocol between the MSOFTX3000 and MGW 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
MSOFTX3000
H.248/SCTP
H.248
IP
SCTP
IP
MGW
Figure 5-1 The protocol stack structure between the MSOFTX3000 and MGW
II. Interaction Between MSOFTX3000 and MGW
After the MGW is started, the MGW sends 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 MGW 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

On the LMT, start the client If you cannot log in to the BAM, check
Start the LMT program of the MSOFTX3000 if the username and password are
1
client O&M software, and log in to the correct, and if the cable between LMT
BAM. and BAM is properly connected.
Open the MML window and
Enable format The meanings of the commands:
execute the following
conversion commands: SET FMT: enable or disable format
2
function, and get conversion function
SET FMT: STS=ON;
online LON: get online
LON:;
5-2

Press shortcut keys <Ctrl + E>
to open the [MML Batch]
window, and execute data
script file. For detail on operations on data script
Execute data
3 Upon completing, check the file, refer to section 3.2.3 Method for
script
Total Result box in the lower Executing Data Script in Chapter 3.
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
4 to perform CRC on the data of
board data system prompts executing command
boards (modules) that can be
loaded. timeout, 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 MGW through
H.248/SCTP

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

If the display is Disconnected, it shows
that the MGW has registered, but currently
quits running. Check if the data
configuration of the MSOFTX3000 and
MGW has been modified. If the data
configuration has not been modified, it is
On the LMT client, run the DSP possible that the H. 248 link communication
Check the of the Mc interface is faulty. Check the
MGW command to check the
registration SCTP link, analyze the interaction of the
registration status of gateway. If
status of the Mc interface message, and take
the display is Normal, it shows
gateway countermeasures.
that the registration is successful.
If the display is Fault, it shows that the
MGW has not registered. In this case, run
the LST MGW command to check if such
parameters as the equipment ID, peer end
IP address, peer end port number and
encode type are correct.
If the link is abnormal, start the SCTP

message tracing to check if the message
On the LMT client, run the DSP flow is correct and if the contents of the
Check the message is legal. Based on what is shown
H248LNK command to check the
status of the in the message tracing, decide other
status of the Mc-interface link. If it
H. 248 link on locating means, such as checking
is Valid, it shows that the link is
Mc-interface configured parameters.
normal.
Refer to section 5.2.4 Treating 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
MGW can be pinged successfully. If not, check if 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 if the MGW is normal.
II. Checking Data Configuration
1) Run the LST FECFG command to check if the interface IP address of the
MSOFTX3000 is the same as that in the data configuration planning. If not,
modify it.
2) If the MSOFTX3000 is not directly connected with the MGW, 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 MGW to check the route passed
and find the location where a packet is lost).
5-4
3) Run the LST H248LNK command to check if 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 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
MGW as 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 if the
Checksum Arithmetic parameter of the local end is the same as 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 MGW side, first run the DEA MGW command to deregister the MGW, and then
run the ACT MGW command to start the MGW. During the starting, the MGW 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 if the SCTP message and H248 message interact correctly.
z H248 message tracing: The MSOFTX3000 receives the service change
request message, and then sends the service change reply message.
z 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

To query the registration status of
DSP MGW Normal for normal status
MGW
5-5

To query the status of H.248 link of
DSP H248LNK Valid for normal status
Mc-interface
DSP PORT To query the status of FE port Normal for normal status
DSP To query the version information of
None
H248VER H.248
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 different from 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 the same as 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
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 if 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
5-6
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.3 Connecting with BSC

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 MGW.
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-7
Note:
Before system commissioning (SM), you must have completed the following:
z Commissioning of clocks of the local office and self-loop test of E1 cables of the
local office. For details, see Chapter 4 Local Office Commissioning.
z Commissioning of interconnection with the MGW and the configuration of E1 SPC
on the MGW. For details, see HUAWEI UMG8900 Universal Media Gateway
Operation Manual Data Configuration.
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

Configuring On the LMT client, execute the data script Refer to section 5.2.2 I.
online data file. Configuring Online Data.
Before the commissioning of the MTP link,
you must make sure that the clock of the
Checking clock Refer to section 4.5 Clock
MSOFTX3000 is synchronous with that of
status Commissioning.
the peer device. If they are not synchronous,
MTP cannot work normally.
Checking the On the LMT client, run the DSP MGW
registration command to check the registration status of Refer to section 5.2.2 Steps
status of gateway. If Normal is displayed, it shows of Commissioning.
gateway the MGW has been registered successfully.
5-8

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 if the first E1 is
normal and notifies the local office of the
result of checking. If this E1 is abnormal,
Caution:
the peer office records the number of
the E1. If it is found during the
self-loop test that an E1 is
4) Set the connectors to their normal
abnormal while the other
connection states.
normal, it may be that the two
5) Follow Steps 24 to perform remote E1s are wrongly connected.
Remote self-loop test to other E1 cables in Such a case must also be
self-loop test of sequence. recorded down.
E1 cables 6) Notify the peer office and the If an E1 is normal while
transmission office of the numbers of another E1, which was
E1s that fail in the self-loop test and are abnormal, becomes normal, it
wrongly connected, in order to solve may be that the two E1s are
problems through negotiation among cross-connected. The problem
the three parties. can be solved by adjusting the
7) After rearranging those abnormal E1s, cables on the cabling rack of
conduct commissioning again in the way the local or peer office.
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 shows the E1 port is normal.
If the status of the link is
abnormal, run the LST N7LNK
command to check if the
On the LMT client, run the DSP N7LNK or
configuration of the following
DSP N7DLNK command to check the status
parameters is correct: module
of the relevant MTP link. If the status is In
number, link type, start circuit
Use, Healthy, it shows the link is normal.
number, signaling link code
and signaling link code
sending.
MTP
commissioning On the LMT client, run the DSP N7DSP If the statuses are abnormal,
command to check the status of relevant run the commands such as
MTP destination signaling point (DSP). If the LST N7DSP, LST N7LKS and
status is Accessible, it shows that the LST N7RT to check if the index
status is normal. relations of the following
On the LMT client, run the DSP N7RT parameters are correct:
command to check the status of the relevant signaling point code,
MTP route. If the status is Healthy and In destination signaling point
Service, it shows that the status is normal. index and link set index.
On the LMT client, run the DSP SCCPDSP If the status is abnormal, run
command to check the status of the SCCP the LST SCCPDSP command
SCCP
remote signaling point. If the status is to check if the parameters
commissioning
Allow, it shows the SCCP remote signaling such as DPC and OPC are
point is normal. correctly configured.
5-9

If the status is abnormal, run
On the LMT client, run the DSP SCCPSSN
the LST SCCPSSN command
command to check the status of the relevant
to check if the parameters
SCCP subsystem. If the status is Allow, it
such as DPC, OPC and
shows the SCCP remote signaling point is
subsystem code are correctly
normal.
configured.
the commands such as LST
OFC, LST BSC, LST
Commissioning On the LMT client, run the DSP AIETKC or
ACPOOL, and LST AIETG to
of A interface DSP OFTK command to check if the status
check if parameters such as
trunk circuit of relevant A interface trunk circuit is normal.
the office direction, equipment
ID, OPC, and DPC are
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 shows an MTP message
received from a link; the mark "< (blue) in the front of a message shows 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
II. Querying Status
Commands for querying MTP statuses are listed in Table 5-5.
Table 5-5 Commands for querying MTP statuses

DSP N7LNK
DSP N7DLNK To the query status of the MTP In Use, Healthy shows the
link status is normal.
DSP
N7LSLNK
To query the status of the MTP Accessible shows the status
DSP N7DSP
destination signaling point is normal.
To query the status of the MTP Healthy, In Service shows the
DSP N7RT
route status is normal.
To query the status of Normal shows the status is
DSP COMM
communication between boards normal.
To query the status of the E1 Normal shows the status is
DSP PORT
port normal.
III. Self-Loop Test
Commands for self-loop test are listed in Table 5-6.
Table 5-6 Commands for self-loop test

To start E1 port These commands are used for E1 port
STR PORTLOP
self-loop self-loop to test if the sending and
To stop E1 port receiving of bottom hardware messages
STP PORTLOP are normal.
self-loop
5-11
5.3.4 Treating MTP Common Problems
I. MTP Link Normal but MTP DSP Inaccessible
When DSP N7LNK is used to query the status of the link to a DSP, it is normal. When
DSP N7DSP is used to query the status of the MTP DSP, it is inaccessible.
2) Causal analysis
In general, the cause of the problem is that the MTP route is not configured or it is
wrongly configured.
If the route to a signaling point is transferred by the STP, check if the STP can access
the DSP.
3) Troubleshooting
Use LST N7RT to query the route to the DSP. If the route does not exist, add a route
to the DSP.
If the route exists, but the link set index is for a link set to the STP (alternative route),
not the DSP, check if the STP can access the DSP. If not, check the data configuration
between the STP and the DSP.
II. Unable to Establish MTP Link
After the data is configured, the MTP link cannot be established.
2) Causal analysis
The cause of the problem includes:
z Wrong data configuration
z Interruption of inter-board communication
z High bit error rate in transmission
In general, check data configuration and then the status of boards, inter-board
communication, and EPI port. Check if there is any alarm indicating high bit error rate
or slip frame. Finally, use the MTP message tracing function to analyze the MTP2
layer messages.
3) Troubleshooting
If the link that is just configured cannot be established, it is quite possible that the data
configuration is wrong. In this case, check as follows:
z Check if the receiving end and sending end of the E1 port match those of the
peer end. If the two receiving ends are connected, the two sending ends are
connected, or the sending and receiving ends do not share an E1 port, reconnect
them.
5-12
z Check if the link slot is the same as that used by the peer end. If it is a 2M link,
check if the counts of slots of the two ends are the same. If the slots are not the
same, remove the link and reconfigure it.
z Check if the link code and link code sending of the local end are the same as
those of the peer end. If not, remove the link and reconfigure it.
z Check if the two ends are consistent when satellite links are used. If not, use
MOD N7LNK to modify the tag of satellite links.
z Check if the DSP of the local link matches the code of the signaling point of the
peer end and if the DSP of the peer link matches the code of the signaling point
of the local end. If not, remove the links and reconfigure the DSPs, link sets,
routes, and links.
z Use LST OFI to check if the network indicator (NI) and signaling point code (SPC)
structure (24-bit code or 14-bit code) of the local end are the same as those of
the peer end. If not, use SET OFI to reconfigure local office information or
request the peer end to modify its information. Restart boards after you modify
the local office information.
z Use LST EPICFG to check if the configuration of E1 port is complete and its work
mode is the same as that of the peer end. Balanced mode: 120 ohm.
Non-Balanced mode: 75 ohm.
After you have confirmed that the data configuration is correct, use DSP FRM to query
the status of boards:
z Check the status of front boards. If it is FAULT, reset the front boards.
z Check the status of EPI. If it is FAULT, reset the EPI.
z Check the status of sub-boards. If it is FAULT, reset the sub-boards. For E1s
from No. 0 to 3, lower sub-boards are used. For E1s from No. 4 to 7, upper
sub-boards are used.
If the status of boards is normal, check the status of inter-board communication and
EPI port:
z Use DSP COMM to check the status of communication between the front board
and sub-board: DSP COMM: FN=0, SN=15, COMT=CPCI, CPCI=21. If the
parameter CPCI is set to 21, it indicates to query the communication of the lower
sub-board. If it is set to 22, it indicates to query the communication of the upper
sub-board.
z Use DSP PORT to query the status of EPI port: DSP PORT: FN=0, SN=15,
PT=E1, PN=0. If the status is not "Normal", check if the connections between E1
cables and connectors are correct. If the status is "Signal bit loss", check if the
clock has been synchronized with that of the peer end.
Check the alarm window. If there are alarms indicating high bit error rate or slip frame,
check if the transmission is normal and contact hardware maintenance staff for help.
5-13
If the data and environment are shown to be correct, and the link cannot be
established, you can enable MTP3 interface tracing and choose MTP2 layer message
tracing to locate the fault.
5.3.5 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.
Table 5-7 SCCP message tracing
Message
tracing Description
function
To trace the interactive messages between the SCCP of the
specified signaling point and the bottom layer.
SCCP DPC
The signaling point is determined by the input parameters NI, DPC
and OPC.
To trace the primitive for interacting between SCCP and the users
SCCP User
above SCCP (for example, TCAP, BSSAP and RANAP)
SCCP MTP To trace the management primitive sent from the bottom layer to
MG SCCP, including signaling point prohibition and allowing.
TCAP SCCP To trace the primitive for interacting between TCAP and SCCP.
To trace the primitive for interacting between TCAP and the upper
TCAP User
layer users.
II. Querying Status
Table 5-8 Commands for querying SCCP statuses

Allow shows that the communication of
To query the status
the signaling point is normal. Prohibit
DSP of the SCCP
shows that the communication of the
SCCPDSP destination signaling
signaling point is interrupted and the
point
signaling point is not reachable.
5-14

Allow shows that the communication of
To query the status the subsystem is normal. Prohibit shows
DSP
of the SCCP that the communication of the subsystem
SCCPSSN
subsystem is interrupted and the subsystem is not
reachable.
Contents of the test results:
GT Index;
GT Matching Length;
GT Matching Content;
To test the
Translating Result Type, including
translation of SCCP
SPC+old GT, SPC+SSN, SPC+new GT
GT and check if the
TST SCCPGT and SPC;
configured SCCP GT
can be translated to NI: network identification;
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.3.6 Treating SCCP Common Problems
I. Request of Location Update or Call Rejected by SCCP
Location update requests or calls started by the RNC or BSC fail. In the SCCP DPC
tracing window, it is shown that the connection request (CR) message sent by the
RNC or BSC is received. The SCCP returns the connection refused (CREF)
message.
2) Causal analysis
According to the analysis of refusing reason in the CRFE message sent by the SCCP,
common causes are listed as follows:
z Cause 1: The message is wrong. When test devices are used to simulate the
RNC or BSC, it is easy to get wrong messages.
z Cause 2: The A interface or RANAP subsystem of the local end is not configured.
Therefore, the message cannot be send to upper layer subscribers.
z Cause 3: The status of the A interface or RANAP subsystem of the local end is
"Disable". Therefore, the message cannot be send to upper layer subscribers.
z Cause 4: There are not enough connection resources.
z Cause 5: Upper layer subscribers do not send connection response after
timeout.
z Cause 6: Refused messages are sent by upper layer subscribers.
5-15
3) Troubleshooting
Enable SCCP DPC message tracing, and type the correct NI. The DSP routes to the
RNC or BSC. The CR message from the RNC or BSC and CRFE message returned
by the SCCP can be traced.
Check if the traced CR message is correct:
z Check if the offset of compulsory parameters matches the start position of the
actual called address parameter.
z Check if the length of the called address is the same as the actual length of the
address in the message.
z Check if the called address is correct. The routing flag is set to "route on SSN".
The address has no GT. It has subsystem number.
z If the called address has a DPC, it is a local DPC. The bytes of the DPC are
determined by the format of the SPC used by the access network: If the format is
a 14-bit code, the DPC is two bytes; if the format is a 24-bit code, the DPC is
three bytes. You can use LST OFI to query the structure of the SPC of the local
office. If the bytes of the DPC in the message do not match the structure of the
SPC at the local end, the called address is wrong. Use a same format for SPCs
of the local and peer ends.
z The subsystem number of the called address should be located behind the
signaling point. It is the RANAP subsystem (0x8E) or A interface subsystem
(0xFE) respectively when the peer end is the RNC or BSC. If the subsystem
number is wrong, negotiate with the peer end.
If the CR message is correct, check the refusing reason after analyzing the traced
CREF message:
z If the refusing reason is "Unequipped User", it is related to the preceding cause 2.
Use LST SCCPSSN to check if the local RANAP or BSSAP subsystem has been
configured. The parameters SPC and OPC of the local subsystem must be local
SPCs. If the subsystem is not configured, add it.
z If the refusing reason is "Subsystem Failure", it is related to the preceding cause
3. Use DSP SCCPSSN to check the status of the local RANAP or BSSAP
subsystem. If the status is "Disable", check if SET SCCPSSN has been used to
set the status of the subsystem to "Disable". If yes, use SET SCCPSSN to set
the status to "Enable"; otherwise, use LST SCCPDSP to check if the local
signaling point is configured in the SCCP DSP table as the DSP. If yes, remove
the record and use SET SCCPSSN to set the status of the subsystem to
"Enable".
z If the refusing reason is "Network Resource - QOS Not Available/Transient", it is
related to the preceding cause 4. If there are many calls going on at the same
time, release calls and wait for a period. Then the calls can be reconnected after
they are restarted. This is because a module can set up a limited count of
5-16
connections at a time. In addition, the SCCP has timer to protect the connection
resources so that they are not allocated immediately after call release.
z If the refusing reason is "Expiration of the Connection Establishment Timer", it is
related to the preceding cause 5. In this case, when you enable the SCCP
subscriber tracing, you can find the N_CONNECT_IND primitive sent from the
SCCP to subscribers. However, subscribers do not return the
N_CONNECT_RSP response primitive. Therefore, the SCCP connection timer
times out. Contact maintenance personnel for the RANAP or A interface to locate
the problem.
z If the refusing reason is "End User Originated" or other value, it is related to the
preceding cause 6. In this case, when you enable the SCCP subscriber tracing,
you can find the N_CONNECT_IND primitive sent from the SCCP to subscribers
and the N_DISCONNECT_REQ primitive returned by subscribers. Refused
messages are sent by upper layer subscribers. Contact maintenance personnel
for the RANAP or A interface to locate the problem.
II. Messages Sent by Upper Layer Subscribers Reaching SCCP but SCCP
Unable to Send Messages to Peer End
In the SCCP subscriber tracing window, messages sent by upper layer subscribers
(including BSSAP, RANAP, and TCAP) to the SCCP can be found. However,
messages sent by the SCCP to the peer end cannot be traced.
2) Causal analysis
Messages sent by upper layer subscribers are routed by the SCCP. If the DSP is
accessible, the messages are sent to lower layer subscribers who then send them to
the peer end. If the messages are lost in the SCCP layer or returned, possible
reasons are:
z The DSP or subsystem is not configured.
z The DSP is inaccessible.
z The configuration of GT code is wrong.
3) Troubleshooting
Enable SCCP subscriber tracing and analyze messages sent by upper layer
subscribers. Analyze the called address in the messages:
z Called address with DPC and SSN
If the called address has DPC and SSN in it, use LST SCCPDSP to query if the
signaling point is configured. If not, add the signaling point.
If the signaling point has been configured, use DSP SCCPDSP to query its status. If
the signaling point is inaccessible, use DSP N7DSP (for MTP bearer) to query its
status at the lower layer. If the status is inaccessible, check data configuration and link
5-17
transmission. If the lower layer signaling point is accessible, the SCCP signaling point
can be restored and the messages can be sent to the DSP.
If the DSP is accessible, use LST SCCPSSN to check if the subsystem has been
configured. (OPC is the SPC in the calling address.) If not, add it.
If the subsystem is configured, use DSP SCCPSSN to query its status. If it is
inaccessible, check if SET SCCPSSN has been used to disable the subsystem. If yes,
use SET SCCPSSN to enable the subsystem; otherwise, check if the SCCP SCMG
subsystem at both ends has been configured. If not, add it. Enable SCCP DPC tracing.
The SST message (borne over UDT) sent by the local SCCP can be found. The SSA
message returned by the peer end cannot be found. Contact the peer end to check
the reason.
z Called address with GT and SSN
If the called address has GT and SSN in it, use TST SCCPGT to check if the result of
GT is correct. (The number plan specified must be the same as that of the GT in the
message.) If not, modify the GT configuration.
If the result of GT is correct, use DSP SCCPDSP to query the status of the signaling
point. If it is inaccessible, check its status at the lower layer. If the status is
inaccessible, check data configuration and link transmission. If the lower layer
signaling point is accessible, the SCCP signaling point can be restored and the
messages can be sent to the DSP.
If the GT result is correct and the DSP is accessible, check the calling address. If it
has GT and SSN in it, use LST SCCPGT to check if the GT code of the caller is
configured and the translation result is the local SPC. If not, add the configuration of
caller GT. (The number plan specified must be the same as that in the GT of the
message.) Use SPC as the type of translation result. Type the local SPC.
III. Local End Receiving SCCP Message from Remote End but Unable to Send
It to Upper Layer Subscribers
In the SCCP DPC tracing window, messages sent by remote end can be traced.
However, in the SCCP subscriber tracing window, primitives sent by the SCCP to
subscriber cannot be traced.
2) Causal analysis
The SCCP needs to route the message sent by the remote end and send it to upper
layer subscribers. The routing may fail because:
z The local subsystem is not configured.
z The local subsystem is inaccessible.
z The configuration of the GT code is wrong.
3) Troubleshooting
5-18
Enable SCCP DPC tracing and analyze SCCP messages sent by the peer end.
Analyze the called address in the messages:
z Addressing according to SSN
If the route label indicates "Route on SSN", use LST SCCPSSN to check if the local
subsystem has been configured. The SPC and OPC are signaling point codes of the
local office. If the local subsystem is not configured, add it.
If the local subsystem is configured, use DSP SCCPSSN to check its status. If the
status is "Disable", check if SET SCCPSSN has been used to set it to "Disable". If yes,
use SET SCCPSSN to set the status to "Enable".
z Addressing according to GT
If the route label indicates "Route on GT", use LST SCCPGT to check if the GT has
been configured in the called address and the translation result is a signaling point at
the local end. If the GT is not configured at the local end, add it. The translation result
is SPC. Type the local SPC.
If the GT has been configured, use TST SCCPGT to check if the signaling point at the
local end can be translated. If it can be translated, the result is SPC + SSN, and the
SSN is not the same as that in the message, change the GT translation result to SPC.
If the translation result is correct, check if the SSN of the local signaling point has
been configured. If not, add the subsystem. If the local subsystem is configured, use
DSP SCCPSSN to check its status. If the status is "Disable", check if SET SCCPSSN
has been used to set it to "Disable". If yes, use SET SCCPSSN to set the status to
"Enable".
5.4 Connecting with HLR, SMC, SCP and SGSN

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.
5-19
HLR SMC
MAP/MTP MAP/MTP
TP
MAP
TP
MAP
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.
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.
5-20
MSOFTX3000 SGSN
MTP
BSSAP+/MTP
BSSAP+
SCCP
MTP3
MTP2
MTP1
Figure 5-7 Structure of the protocol stack between the MSOFTX3000 and SGSN
Note:
Before SM, you must have fulfilled commissioning of clocks of the local office and
self-loop test of E1 cables of the local office.
Warning:

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

Configuring On the LMT client, execute the data Refer to section 5.2.2 I. Configuring
online data script file. Online Data.
Before the commissioning of the
MTP link, you must make sure that
Checking clock the clock of the MSOFTX3000 is Refer to section 4.5 Clock
status synchronous with that of the peer Commissioning.
device. If they are not synchronous,
MTP cannot work normally.
5-21

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 if 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 Caution:
normal connection states. If it is found during the self-loop test that
5) Follow Steps 24 to perform an E1 is abnormal while the other
remote self-loop test to other normal, it may be that the two E1s are
E1 cables in sequence. wrongly connected. Such a case must
Remote also be recorded down.
self-loop test of 6) Notify the peer office and the
E1 cables transmission office of the If an E1 is normal while another E1,
numbers of E1s that fail in the which was abnormal, becomes normal,
self-loop test and are wrongly it may be that the two E1s are
connected, in order to solve cross-connected. The problem can be
problems through negotiation solved by adjusting the cables on the
among the three parties. power distribution subrack of the local
7) After rearranging those or peer office.
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 shows
the E1 port is normal.
5-22

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

MTP N7DSP command to check the
commissioning status of the relevant MTP If the statuses are abnormal, run the
destination signaling point. If the commands such as LST N7DSP, LST
status is Accessible, it shows that N7LKS and LST N7RT to check if the
the status is normal. index relations of the following
On the LMT client, run the DSP parameters are correct: signaling point
N7RT command to check the status code, destination signaling point index
of the relevant MTP route. If the and link set index.
status is Healthy and In Service,
it shows that the status is normal.
SCCPDSP command to check the If the status is abnormal, run the LST
status of the SCCP remote SCCPDSP command to check if the
signaling point. If the status is parameters such as DPC and OPC are
Allow, it shows the SCCP remote correctly configured.
signaling point is normal.

SCCP If the status is abnormal, run the LST
SCCPSSN command to check the
commissioning SCCPSSN command to check if the
status of the relevant SCCP
parameters such as DPC, OPC and
subsystem. If the status is Allow, it
subsystem code are correctly
shows the SCCP remote signaling
configured.
point is normal.
On the LMT client, run the TST If not correct, run the LST SCCPGT
SCCPGT command to check if the command to check wheterh parameters
translation of SCCP GT is correct. are correctly configured.
5.4.3 Locating and Treating Problems
Refer to section 5.3.3 Locating MTP Problems and section 5.3.5 Locating
SCCP/TCAP Problems.
5.5 Connecting with MSC through ISUP & MAP/MTP

The MSOFTX3000 is connected with other MSCs through ISUP/MAP over MTP link
bearer. An E1 SPC will be established on the MGW for transparently transmit ISUP
and MAP messages. The protocol stack is illustrated in Figure 5-8.
5-23
MSOFTX3000 MSC
k
un
ISUP&MAP/MTP ISUP&MAP/MTP
Tr
TP
TP
M
MAP MAP
ISUP ISUP
TCAP TCAP
SCCP SCCP
MTP3 MTP3
MTP2 MTP2
MTP1 MTP1
UMG8900
Figure 5-8 Structure of ISUP & MAP/MTP protocol stack
Note:
Before SM, 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 MGW, and must have configured the E1 SPC on the MGW.
Warning:

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

Configuring On the LMT client, execute the data Refer to section 5.2.2 I.
online data script file. Configuring Online Data.
Before the commissioning of the MTP

link, you must make sure that the clock
Checking clock of the MSOFTX3000 is synchronous Refer to section 4.5 Clock
status with that of the peer device. If they are Commissioning.
not synchronous, MTP cannot work
normally.
On the LMT client, run the DSP MGW
Checking the
command to check the registration
registration Refer to section 5.2.2 Steps of
status of gateway. If Normal is
status of Commissioning.
displayed, it shows the MGW has been
gateway
registered successfully.
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 if 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 Caution:
connection states. If it is found during the self-loop test
5) Follow Steps 24 to perform remote that an E1 is abnormal while the
self-loop test to other E1 cables in other normal, it may be that the two
sequence. E1s are wrongly connected. Such a
Remote case must also be recorded down.
self-loop test of 6) Notify the peer office and the
E1 cables transmission office of the numbers If an E1 is normal while another E1,
of E1s that fail in the self-loop test which was abnormal, becomes
and are wrongly connected, in order normal, it may be that the two E1s
to solve problems through are cross-connected. The problem
negotiation among the three can be solved by adjusting the
parties. cables on the power distribution
7) After rearranging those abnormal subrack of the local or peer office.
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 shows the
E1 port is normal.
5-25

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

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

If the status is abnormal, run the
SCCPDSP command to check the
LST SCCPDSP command to check
status of the SCCP remote signaling
if the parameters such as DPC and
point. If the status is Allow, it shows the
OPC are correctly configured.
SCCP remote signaling point is normal.
On the LMT client, run the DSP If the status is abnormal, run the
SCCP
SCCPSSN command to check the LST SCCPSSN command to check
commissioning
status of the relevant SCCP subsystem. if the parameters such as DPC,
If the status is Allow, it shows the OPC and subsystem code are
SCCP remote signaling point is normal. correctly configured.
On the LMT client, run the TST If not correct, run the LST SCCPGT
SCCPGT command to check if the command to check wheterh
translation of SCCP GT is correct. parameters are correctly configured.
Checking the On the LMT client, run the command commands such as LST TG and
status of the DSP OFTK or DSP N7TKC to check if LST TKC to check if the following
SS7 trunk the status of the SS7 trunk circuit is parameters are correctly configured:
circuit normal. equipment ID, OPC, DPC, start CIC
and terminal endpoint ID.
Refer to section 5.3.3 Locating MTP Problems and section 5.3.5 Locating
SCCP/TCAP Problems.
5-26
5.6 Connecting with MSC through ISUP/M3UA

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
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
Tr
IP
M3UA MTP3
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.
5-27
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:
z 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.
z 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.
z 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.
z 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-28
Table 5-11 Steps of commissioning for connecting with MSC through ISUP/M3UA

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

Check the
MGW command to check the status
status of Refer to section 5.2.2 Steps of
of gateway registration. If the
gateway Commissioning.
display is Normal, it shows that the
registration
UMG8900 registers successfully.

M3LNK command to check the
statuses of relevant M3UA links. If
they are Active, it shows that the
links are normal. If the statuses are abnormal, first run the
LST M3LKS command to check if the
On the LMT client, run the DSP transmission mode of the link set is
M3LKS command to check the correctly configured. Then, use the LST
status of the M3UA link set. If they M3LNK command to check if the
are Active, it shows that the links following parameters are correct: the
are normal. local end port number, local end IP
M3UA address, peer end port number, peer end
commissioning On the LMT client, run the DSP IP address, and C/S work mode.
M3DE command to check the
status of the M3UA destination
entity. If the display is Accessible,
it shows that the status is normal.
If the statuses are abnormal, use
commands LST M3LE, LST M3DE and
LST M3LKS to check if such parameters
M3RT command to check the
as the local entity index, destination
statuses of relevant M3UA routes.
entity index and link set index have
correct relations.
5-29

If the statuses are abnormal, use
commands like LST TG and LST TKC to
Check the On the LMT client, run the DSP
check if the following parameters are
statuses of OFTK or N7TKC command to
correct: the equipment ID, origination
SS7 signaling check the statuses of relevant SS7
point code (OPC), destination point code
trunk circuits signaling trunk circuits.
(DPC), start circuit identification code
(CIC), and start circuit terminal ID.
5.6.3 Locating M3UA Problems
Most of the problems in M3UA are due to human factors, including errors in data
configuration and manually deactivating an M3UA link. Methods for locating the
problems are described as follows.
Use the interface tracing function PING on the console to check if the peer device
can be pinged successfully. If the peer device cannot be pinged through, check
physical connections 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.
1) Run the LST FECFG command to check if the IP address of the interface of the
MSOFTX3000 is the same as 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 if 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 if 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 if 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 if a message flow is correct. As shown in Figure 5-10, a
normal M3UA message proceeding flow is as follows:
5-30
1) SCTP reports UP;

2) Application Service Party (ASP) sends ASP UP to the SG, and the SG
responds ASP UP ACK;
3) 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

DSP M3LNK
DSP M3DLNK To query the status of the M3UA Active shows the normal
link status.
DSP
M3LSLNK
To query the status of the M3UA Active shows the normal
DSP M3LKS
link set status.
To query the status of the M3UA Accessible shows the

DSP M3DE
destination entity normal status.
To query the status of the M3UA
DSP M3RT None
route
To query the version information

DSP M3VER None
of M3UA
5-31
5.6.4 Treating M3UA Common Problems
I. M3UA Link Status Displayed as Link Unestablished
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 if 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.
If Local Release Info is Release Ungracefully or Release Gracefully, it shows 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 details, refer to section 5.2.4 Treating SCTP Common
Problems.
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;%%
5-32
For Cause 3, refer to section 5.2.4 Treating SCTP Common Problems.
II. M3UA Link Status Displayed as Link DOWN
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:
M3UA Link Status

-------------------------
Module Number = 133
Link Number = 0
Lock Information = Locked
Local Inactive Info = Link Not Inactivated Manually
Local Release Info = Link Not Released Manually
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
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;%%
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;%%
%%EST M3LNK: MN=133, M3LNK=0,CONFIRM=Y;%%

5-33
III. M3UA Link Status Displayed as Link Inactive
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 if an M3UA link has been deactivated manually on the ASP side, as
shown below:
M3UA Link Status

-------------------------
Module Number = 132
Link Number = 0
Lock Information = Unlocked
Local Inactive Info = Link Inactivated Manually
Local Release Info = Link Not Released Manually
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 shows 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 shows 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;%%
5-34
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
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
3) Route selection code, route selection source code
4) BICC trunk group
5-35
The BICC trunk group is not a collection of circuit identification codes or circuits, but
only an MGW 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.
3) 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.
I. Steps of BICC Commissioning (Independent Work Mode)
Table 5-13 Steps of the BICC commissioning (independent work mode)


Observe the indicators on the WIFM. physical connection is normal, and is
The green Ethernet port connection off in other cases.
indicator, LINK, should be on, while When the ACT indicator flashes, it
the yellow Ethernet port data traffic shows that there is data being
indicator, ACT, should flash. sent/received. The blinking frequency
network
connection On the LMT client, use the interface In case of failure, check if the Ethernet
tracing function PING to check the cables are correctly connected, if the
communication between the WIFM WIFM works normally, if devices
and the peer MSC. If the ping connected with the WIFM (such as a
command is executed successfully, it router) works normally, if route data is
shows that the communication is correctly configured, and if the peer
normal. MSC works normally.
5-36

Check the
command to check the status of
gateway registration. If the display is
Normal, it shows that the gateway
registration
registers successfully.
If the statuses are abnormal, run the
LST BICCSCTPLNK command to
check if BICC SCTP links are correctly
configured, including the following
parameters: the module number, link
number, office direction, local end port
On the LMT client, run the DSP number, local end IP address, peer end
BSCTP command to check the port number, peer end IP address, and
statuses of relevant BICC SCTP C/S work mode.
links. If they are Active, it shows that
If data configuration for the local office
the links are normal.
BICC has no problem, check if data of the
commissioning peer MSC is correctly configured.
If the data configuration of the peer
MSC also has no problem, run the ACT
BSCTP command to activate BICC
SCTP links.

On the LMT client, run the command command LST BICCCICMDU to check
DSP BICCCIC or DSP BICCOFC to if the parameters such as the office
check the statuses of relevant BICC direction, module number, start CIC,
CICs. and CIC transformation mode are
correct.
II. Steps of BICC Commissioning (Mutual Aid Work Mode)
Table 5-14 Steps of the BICC commissioning (mutual aid work mode)

5-37

network
connection In case of failure, check if the
On the LMT client, use the interface Ethernet cables are correctly
tracing function PING to check the connected, if the WIFM works
communication between the WIFM and normally, if the device connected with
the peer MSC. If the ping command is the WIFM (such as a router) works
executed successfully, it shows that normally, if route data is correctly
the communication is normal. configured, and if the peer MSC
works normally.
Check the
If data has been configured for the peer If the status of a link is abnormal, use
work mode of
MSC, run the command DSP DHSTA the LST DHHCFG command to check
the local office
to check if the local office is in the if the peer end IP address, local UDP
and the
mutual aid inactive state and if the two port number, peer end UDP port
statuses of
dual homing heartbeat links are number, and key are correctly
dual homing
normal. configured.
heartbeat links

gateway registration.
Check the At this time, the local office should work
status of in the mutual aid inactive state, Refer to section 5.2.2 Steps of
gateway gateways primarily homed to the local Commissioning.
registration office should all be normal in
registration, while gateways
secondarily homed to the local office
abnormal in registration.

BSCTP command to check the
statuses of BICC SCTP links. In case of abnormality, solve the
problem by referring to Steps of
At this time, the local office should work BICC Commissioning (Independent
in the mutual aid inactive state, links Work Mode) in this chapter, and
primarily homed to the local office check if data configuration for the
should all be normal, while gateways local office and peer MSC is correct.
BICC secondarily homed to the local office
commissioning abnormal.

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

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 if data
Activate the On the LMT client, run the DSP has been correctly configured for the
local office DHSTA command to check the work local office.
mode of the local office and the
statuses of dual homing heartbeat
links.
Check the command to check the status of
status of gateway 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.

BSCTP command to check the In case of abnormality, solve the
statuses of BICC SCTP links. problem by referring to Steps of
BICC Commissioning (Independent
At this time, the local office should work Work Mode) in this chapter, and
in the mutual aid active state, and the check if data configuration for the
BICC links, except that to the peer MSC
commissioning local office and peer MSC is correct.
(powered off), should all be normal.
(mutual aid
active state) If the statuses are abnormal, run the
On the LMT client, run the command command LST BICCCICMDU to
DSP BICCCIC or DSP BICCOFC to check if the parameters such as the
check the statuses of relevant BICC office direction, module number, start
CICs. CIC, and 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:
peer MSC, and the local office will On the LMT client, run the DSP
Deactivate the automatically enter the mutual aid DHSTA command to check the work
local office inactive state when the basic mode of the local office and the
subrack of the peer MSC works statuses of dual homing heartbeat
normally, 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-39
5.7.3 Locating BICC Problems
Use the interface tracing function PING on the console to check if the peer device
can be pinged through. If the peer device cannot be pinged through, check if 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.
1) Run the LST FECFG command to check if the IP address of the interface of the
MSOFTX3000 is the same as 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 if 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 if 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

DSP BSCTP To query the status of the Active shows the normal
DSP BSCTPOFC BICC link status.
DSP BICCCIC
To query the status of BICC
DSP BICCOFC None
CIC
DSP BICCSTA
5-40
5.7.4 Treating BICC Common Problems
I. BICC CIC Status Abnormality
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 not consistent with that for the other.
Cause 2: The lower layer signaling bearer is faulty.
3) Troubleshooting
For Cause 1, check if 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 if 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
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.
5-41
Cause 1: The BICC signaling bearer type configured for an office direction does not
conform to the signaling bearer type actually used.
Cause 2: Parameters of SCTP links on one end is not consistent 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 if 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 if correct
DPCs have been configured in the office direction table.
If the SCTP link is configured, run the LST BICCSCTPLNK command to check if this
link is configured for the correct office direction; and run the DSP BSCTP command to
check if the link status is normal.
If the link status is abnormal, check if 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 if 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

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-42
MSOFTX3000 RANAP/M3UA
RANAP
SCCP
M3UA
IP SCTP
IP
M3UA MTP3B
UMG8900 (SG)
SCTP SAAL
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-43
Table 5-16 Steps of commissioning for connecting with RNC through RANAP/SCTP

network
connection On the LMT client, use the interface
In case of failure, check if the Ethernet
tracing function PING to check the
cables are correctly connected, if the
communication between the WIFM
WIFM works normally, if devices
and the UMG8900. If the ping
connected with the WIFM (such as a
command is executed successfully, it
LAN Switch) works normally, and if the
shows that the communication is
UMG8900 works normally
normal.

Check the
gateway registration. "Normal shows
that the UMG8900 has registered
registration
successfully.
5-44

M3LNK command to check the status
of M3UA link. Active shows that the
status is normal.
If the status is abnormal, run the LST
On the LMT client, run the DSP M3LKS command to check if the
M3LKS command to check the status correct transmission mode has been
of the M3UA link set. configured for the link set. Use the LST
Active shows that the status is M3LNK command to check if such
normal. parameters as the local port number,
local IP address, remote port number,
M3UA remote IP address, and C/S work mode
commissioning On the LMT client, run the DSP are correctly configured.
M3DE command to check the status
of the M3UA destination entity.
Accessible shows that the status is
normal.
LST M3LE, LST M3DE and LST
On the LMT client, run the DSP M3RT
M3LKS commands to check if such
command to check the statuses of
parameters as the local entity index,
relevant M3UA links.
destination entity index and link set
index are correctly configured.

SCCPDSP command to check the
LST SCCPDSP command to check if
statuses of remote SCCP signaling
such parameters as DPC and OPC are
points. Allow shows that the status
correctly configured.
SCCPcommis is normal.
sioning On the LMT client, run the DSP If the statuses are abnormal, run the
SCCPSSN command to check the LST SCCPSSN command to check if
statuses of SCCP subsystems. such parameters as DPC, OPC and
Allow shows that the status is subsystem code are correctly
normal. configured.
Refer to section 5.3.5 Locating SCCP/TCAP Problems, section 5.6.3 Locating

M3UA Problems, and section 5.6.4 Treating M3UA Common Problems.
5-45
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Chapter 6 Service Commissioning
Chapter 6 Service Commissioning

This chapter depicts 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

If you cannot log in to the BAM, check
On the LMT, start the client program
Start the if the username and password are
1 of the MSOFTX3000 O&M software,
LMT client correct, and if the cable between LMT
and log in to the BAM.
and BAM is properly connected.
Enable Open the MML window and execute The meanings of the commands:
format the following commands:
conversio
2 SET FMT: enable or disable format
n function,
and get SET FMT: STS=ON; conversion function
online LON:; LON: get online
Execute
the
3 number
analysis
data script Press shortcut keys <Ctrl + E> to
open the [MML Batch] dialog box, and
Execute execute data script files in sequence.
the mobile For detail on operations onto data
4 Upon completing every script, check
service script files, refer to Method for
data script the [Total Result] field in the lower Executing Data Script in Chapter 3.
part of the dialog box, to see if the
Execute MML commands are all executed
the successfully.
intelligent
5
network
service
data script
6-1

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 the command STR CRC. If the
command STR CRC: MN=255; to
6 CRC on system prompts timeout in executing
perform CRC on the data of boards
board data the command, select
(modules) that can be loaded.
[System/Command Timeout
Setting...] on the LMT client to extend
the time-out time.
6.3 Implementing Service Test

6.3.1 Preparations
Before carrying out service test, make the preparations below:

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 tests below based on 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
Staff of the related offices are asked to perform dialing test based on the dialing test
plan of Huawei. They should make records about whether a test item is successful,
6-2
and the caller number, called number, call initiating time and call 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
For test items and methods for various services, see HUAWEI MSOFTX3000 Mobile
SoftSwitch Center Acceptance Manual.
6.4 Handling of Common Problems

6.4.1 Handling of Call Abnormality
I. Monolog
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.
6-3
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
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.
II. Signaling Is Correct, but No RBT or Voice Can Be Heard
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 shows 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.
6-4
Local office Peer office
Receive Send
System A System A
Send Receive
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,
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 if 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 if 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 if the
prefix of this MSRN is correctly configured.
3) If no problem is found in number analysis, use the LST RTANA command to
check if 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
6-5
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 MGW
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 if 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 MGW.
Check if the trunk resources of the MGW are correctly configured. If the current call is
of IP bearer type, check if relative IP data has been correctly configured on the MGW,
if corresponding physical ports have been activated, and if cables are correctly
connected. If the current call is of ATM bearer type, check if the MGW supports ATM,
if relative data has been correctly configured, and if statuses of resources are normal.
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 MGW. If the release (REL) message is returned at once 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 MGW 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 at
once after the IAM message, use the LST MGW command to check the MGW
configuration on the incoming office and see if the codec type supported by the
MGW 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.
6-6
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 if 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.
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:
z Query the recent performance 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.
z Query the seizure of trunk circuits. If the trunk circuit seizure ratio is over 70%, it
shows 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 performance measurement tasks.
The measurement period of performance measurement tasks will also greatly affect
the CPU seizure ratio. Due to their close relation with calls, most performance
6-7
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:
The modification of the measurement cycle of performance 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.53
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.
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 split a location area when it contains more than four
BSCs/RNCs.
Note:
Contact Huawei for technical support when you want to divide, organize, and optimize
the network.
6-8
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
Over- Resu Resu-

Resum
Overload Overload Overload load -me me Resume
Threshold e Level
Level 1 Level 2 Level 3 Level Level Level Level 3
4
4 1 2
Default 80 85 90 95 75 80 85 90
6-9
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 SM

Table A-1 Preparations for system commissioning (SM)
Item Result Remarks

The installation and checking of hardware
Check the are finished, and the equipment is Y; N
construction powered on.
condition The installation and checking of software
Y; N
are finished.
Check
The complete technical documents for
technical Y; N
deployment are ready.
documents
The numbers of servers and matching
Y; N
devices are correct.
The numbers of cabinets and subracks
Y; N
are correct.
Check the
hardware The number of boards and board
Y; N
configuration locations are correct.
Board versions are correct. Y; N
The subrack numbers of the WSIU
Y; N
boards are correctly set.
The status of the power distribution box is

Y; N
normal.
The statuses of subrack fans are normal. Y; N

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

The power status of the LAN Switch is
Y; N
normal.
A-1
Item Result Remarks

Software versions are correct. Y; N
The SQL Server runs normally. Y; N
Services are in normal condition. Y; N
Processes are in normal condition. Y; N
Check the
software of The BAM can log in after restarting, the
BAM SQL Server and services and processes Y; N
are all in good condition.
System customization has been fulfilled
by using the SetWin2000 security Y; N
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 Software versions are correct. Y; N
the LMT
The version of software is correct. Y; N

The status of the dual system heartbeat is
Y; N
normal.
All processes run normally. Y; N
Check iGWB It is possible to automatically log on to the
software active and standby iGWBs after they
Y; N
have been restarted. And processes run
normally.
It is possible to switch between the active

and standby iGWB. And processes run Y; N
normally.
The IP addresses of the BAM and iGWB

Y; N
are correctly set.
The BAM can communicate normally with

Y; N
the foreground host.
Check the The communication between the BAM
communicati Y; N
and iGWB is normal.
on of the
internal LAN The communication between the iGWB
Y; N
and the host is normal.
The configuration of the VLAN is correct. Y; N

The Ethernet biplane switchover function
Y; N
is normal.
A-2
Item Result Remarks

The IP addresses of the BAM, LMT,
iGWB and emergency workstation are Y; N
correctly set.
Check the The BAM can normally communicate with
communicati Y; N
the LMT.
on of the
external LAN The BAM can normally communicate with
Y; N
the emergency workstation.
The communication between the BAM

Y; N
and iGWB is normal.
Check the The BAM can normally communicate with

Y; N
communicati the NMC.
on of the The communication between the iGWB
WAN Y; N
and the charging center is normal.
Make an
empty Make an empty backup of the BAM
backup of the database using SQL Server Enterprise Y; N
BAM Manager before data 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
Data
collect external interface data, consult
collection and Y; N
with the peer office about the data
planning
needing negotiation and service data, and
fill out the data collection form.
Make data Edit/modify data script files according to
Y; N
script the situation on site.
Check data
Data script is correct. Y; N
script
A-3
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
Software versions of boards are correct. Y; N
check basic
subracks Data verification for boards (modules) that can
Y; N
be loaded is successful.
Boards run normally. Y; N
Load and Software versions of boards are correct. Y; N

check Data verification for boards (modules) that can
expansion Y; N
be loaded is successful.
subracks
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
Y; N
commissioning circuit 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.
A-4
Item Result Remarks

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
The active/standby switchover for the front
hardware Y; N
board is normal.
switchover
Perform
self-loop test of The self-loop test of E1 cables of the local
Y; N
E1 cables of office is passed.
the local office
After the successful loading of a board and
Modify the
when it runs normally, modify the settings of the
loading
loading software switch to program available, Y; N
software switch
data available, data writable, program not
of a board
writable.
The time of the switch is correctly set with an
Set the time for
error less than 30 seconds against the local Y; N
the switch
standard time.
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
Y; N
Connect with the MGW is normal.
MGW The status of gateway registration is normal. Y; N
Statuses of H.248 links of Mc-interface are
Y; N
normal.
A-5
Item Result Remarks

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
Y; N
routes are normal.
Statuses of SCCP remote signaling points and

Y; N
subsystems are normal.
Statuses of A-interface trunk circuits are normal. Y; N

Connect with HLR
Y; N
routes are normal.

Y; N
subsystems are normal. GT translation is correct.
Connect with SMC
Y; N
routes are normal.

Y; N
Connect with SCP
Y; N
routes are normal.

Y; N
A-6
Item Result Remarks

Connect with
SGSN Statuses of MTP links, signaling points and
Y; N
routes are normal.
Y; N
Connect with MSC The remote self-loop test of E1 cables is normal. Y; N
through
ISUP&MAP/MTP Statuses of MTP links, signaling points and
Y; N
routes are normal.

Y; N
The status of SS7 trunk circuit is normal. Y; N

Y; N
UMG8900 is normal.
Connect with the The status of gateway registration is normal. Y; N
MSC using
ISUP/M3UA Statuses of M3UA links, link set, and route are
Y; N
normal.
SS7 trunk circuits are in normal statuses. Y; N

Connect with the The network connection between the WIFM and
Y; N
MSC using MSC is normal.
BICC/SCTP
(independent work
mode) Statuses of BICC links are normal. Y; N
BICC CIC statuses are normal. Y; N
A-7
Item Result Remarks

Y; N
MSC is normal.
The statuses of dual homing heartbeat links are

normal. The local office is in the mutual aid Y; N
inactive status
The registration status of the gateway controlled
Y; N
by the local office is normal.
Connect with the The statuses of BICC links controlled by the local
MSC using Y; N
office are normal.
BICC/SCTP
(mutual aid work BICC CIC statuses are normal. Y; N
mode)
The local office is activated successfully and is in
Y; N
the 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 Y; N
status of dual homing heartbeat link is normal.
The connection between the WIFM and
Y; N
UMG8900 is normal.

Connect with RNC
The statuses of M3UA links, link set, destination
Y; N
entity and route are normal.
The statuses of SCCP remote signaling points

Y; N
and 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
A-8
Item Result Note

Mobility management test Y; N
CDR function test Y; N
A-9
HUAWEI MSOFTX3000 Mobile SoftSwitch Center Index
Index
connecting with HLR

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

mode, 3-1 clock commissioning, 4-10
sequence, 3-1 configure data offline, 4-3
data script description of related concepts, 4-1
editing and checking, 3-2 hardware commissioning, 4-15
method for executing, 3-2 modifying settings of loading software switch,
dual homing 4-19
basic concept, 5-36 prepare for loading, 4-3
setting time for MSOFTX3000, 4-20
H
H.248/SCTP M
commissioning, 5-3 M3UA
locating problems, 5-4 locating problems, 5-30
protocol stack, 5-1 treating common problems, 5-32
hardware commissioning MAP/MTP
checking indicator status, 4-15 protocol stack, 5-19
checking the running of hardware, 4-17 MTP
hardware switchover verification, 4-18 locating problems, 5-10
self-loop test for local office E1 cables, 4-19
O
I O&M system
interconnection commissioning checking communication, 2-10
connecting with BSC, 5-7 checking communication of external LAN, 2-16
connecting with HLR, 5-19 checking communication of internal LAN, 2-14
connecting with MGW, 5-1 checking communication of WAN, 2-17
connecting with MSC through BICC/SCTP, 5-35 description, 2-10
connecting with MSC through ISUP&MAP/MTP, IP address of BAM, 2-11
5-23 IP address of emergency workstation, 2-12
connecting with MSC through ISUP/M3UA, 5-27 IP address of iGWB, 2-13
connecting with RNC, 5-42 IP address of LMT, 2-12
connecting with SCP, 5-19 IP address of WSMU, 2-12
connecting with SGSN, 5-19 method for checking communication, 2-14
connecting with SMC, 5-19
IP address P
BAM, 2-11 preparations for system commissioning
emergency workstation, 2-12 checking communication of O&M system, 2-10
iGWB, 2-13 checking construction conditions, 2-1
LMT, 2-12 checking hardware configuration, 2-3
WSMU, 2-12 checking power supply, 2-4
checking software, 2-5
L checking technical documents, 2-2
local office commissioning making a backup of BAM database, 2-18
i-2
protocol stack service commissioning

BICC/SCTP, 5-35 handling common problems, 6-3
BSSAP/MTP, 5-7 handling of BICC call problems, 6-5
BSSAP+/MTP, 5-20 handling of call abnormality, 6-3
CAP/MTP, 5-20 handling of CPU overload, 6-6
H.248/SCTP, 5-1 implementing service test, 6-2
ISUP&MAP/MTP, 5-23 system commissioning
ISUP/M3UA, 5-27 commissioning records of newly-built office, A-1
MAP/MTP, 5-19 conditions, 1-1
RANAP/M3UA, 5-42 data configuration, 3-1
definition, 1-1
R flow, 1-1
RANAP/M3UA interconnection commissioning, 5-1
protocol stack, 5-42 local office commissioning, 4-1

preparations, 2-1
S service commissioning, 6-1
SCCP
T
locating problems, 5-14
SCTP TCAP
treating common problems, 5-6 locating problems, 5-14
i.
i-3

MSS Commissioning PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

MSS Commissioning PDF

Hochgeladen von

Copyright:

Verfügbare Formate

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

HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Huawei Technologies Proprietary

Volume System Commissioning

Manual Version T2-030410-20060425-C-3.05

Product Version V100R003

Huawei Technologies Co., Ltd.

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

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

Postal Code: 518129

Huawei Technologies Proprietary

All Rights Reserved

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

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

Huawei Technologies Proprietary

The manual applies to HUAWEI MSOFTX3000 Mobile SoftSwitch Center V100R003.

The manual introduces operations about MSOFTX3000 commissioning.

There are six chapters and an appendix in the manual.

Chapter 1 Overview of System Commissioning introduces the contents and flow

Chapter 2 Preparations for System Commissioning describes the preparations

Chapter 3 Data Configuration introduces the data configuration method and

Chapter 4 Local Office Commissioning introduces the internal data configuration,

Chapter 5 Interconnection Commissioning introduces the data configuration and

Chapter 6 Service Commissioning introduces the configuration and testing of

Appendix A Commissioning Records of Newly-Built Office presents the

The manual is intended for the following readers:

Huawei Technologies Proprietary

The manual uses the following conventions:

Boldface Headings are in Boldface.

II. GUI conventions

Button names are inside angle brackets. For example, click

III. Keyboard operation

Press the keys concurrently. For example, <Ctrl+Alt+A>

IV. Mouse operation

Select and release the primary mouse button without

Huawei Technologies Proprietary

Caution, Warning: Means reader be extremely careful during the operation.

Note: Means a complementary description.

Huawei Technologies Proprietary

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

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

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

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

Huawei Technologies Proprietary

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

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

Huawei Technologies Proprietary

5.6 Connecting with MSC through ISUP/M3UA .................................................................... 5-27

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

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

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

Huawei Technologies Proprietary

Chapter 1 Overview of System Commissioning

Huawei Technologies Proprietary

The description of each step in the flow is listed in Table 1-1.

The step consists of the following:

Huawei Technologies Proprietary

Chapter 2 Preparations for System

2.1 Introduction to This Chapter

2.2 Checking Construction Conditions

Item Description Result Remarks

Huawei Technologies Proprietary

Item Description Result Remarks