Installation Manual-System 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.1 Introduction to This Chapter 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.1 Introduction to This Chapter 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.................................5.5.1 Description of Relevant Concepts 5-23..................................................5.5.2 Steps of Commissioning 5-24................................................................

5.5.3 Locating and Treating Problems 5-26....................................................5.6 Connecting with MSC through ISUP/M3UA 5-27...........................................

5.6.1 Description of Relevant Concepts 5-27..................................................5.6.2 Steps of Commissioning 5-29................................................................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.2 Steps of Commissioning 5-36................................................................5.7.3 Locating BICC Problems 5-40................................................................5.7.4 Treating BICC Common Problems 5-41................................................

5.8 Connecting with RNC 5-42.............................................................................5.8.1 Description of Relevant Concepts 5-42..................................................5.8.2 Steps of Commissioning 5-44................................................................5.8.3 Locating and Treating Problems 5-45....................................................

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

6.1 Introduction to This Chapter 6-1...................................................................6.2 Executing Data Script 6-1.............................................................................6.3 Implementing Service Test 6-2.....................................................................

6.3.1 Preparations 6-2...................................................................................6.3.2 Method of Implementing Service Test 6-2...........................................6.3.3 Service Tests 6-3.................................................................................

6.4 Handling of Common Problems 6-3.............................................................6.4.1 Handling of Call Abnormality 6-3..........................................................6.4.2 Handling of BICC Call Problems 6-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 Technologies Proprietary

HUAWEI

HUAWEI MSOFTX3000 Mobile SoftSwitch Center Installation Manual – System Commissioning

V100R003


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


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:

WCDMA/UMTS system engineers Operation and maintenance engineers 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

<Key> Press the key with the key name inside angle brackets. For example, <Enter>, <Tab>, <Backspace>, or <A>.

<Key1+Key2> Press the keys concurrently. For example, <Ctrl+Alt+A> means the three keys should be pressed concurrently.

<Key1, Key2> Press the keys in turn. For example, <Alt, A> means the two keys should be pressed in turn.

IV. Mouse operation

Action Description

Click Select and release the primary mouse button without moving the pointer.

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


Action Description

Drag Press and hold the primary mouse button and move the 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.

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


i

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.1 Introduction to This Chapter .............................................................................................. 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



ii

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.1 Introduction to This Chapter .............................................................................................. 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 5.5.1 Description of Relevant Concepts......................................................................... 5-23 5.5.2 Steps of Commissioning ....................................................................................... 5-24 5.5.3 Locating and Treating Problems ........................................................................... 5-26



iii

5.6 Connecting with MSC through ISUP/M3UA .................................................................... 5-27 5.6.1 Description of Relevant Concepts......................................................................... 5-27 5.6.2 Steps of Commissioning ....................................................................................... 5-29 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.2 Steps of Commissioning ....................................................................................... 5-36 5.7.3 Locating BICC Problems....................................................................................... 5-40 5.7.4 Treating BICC Common Problems........................................................................ 5-41

5.8 Connecting with RNC ...................................................................................................... 5-42 5.8.1 Description of Relevant Concepts......................................................................... 5-42 5.8.2 Steps of Commissioning ....................................................................................... 5-44 5.8.3 Locating and Treating Problems ........................................................................... 5-45

Chapter 6 Service Commissioning.............................................................................................. 6-1 6.1 Introduction to This Chapter .............................................................................................. 6-1 6.2 Executing Data Script ........................................................................................................ 6-1 6.3 Implementing Service Test ................................................................................................ 6-2

6.3.1 Preparations ............................................................................................................ 6-2 6.3.2 Method of Implementing Service Test..................................................................... 6-2 6.3.3 Service Tests........................................................................................................... 6-3

6.4 Handling of Common Problems......................................................................................... 6-3 6.4.1 Handling of Call Abnormality................................................................................... 6-3 6.4.2 Handling of BICC Call Problems............................................................................. 6-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

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


1-1

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:

Hardware installation and checking have been done, and the equipment is powered on.

Software installation and checking have been done (except board loading).

Note:

For detailed hardware installation and checking, see HUAWEI MSOFTX3000 Mobile SoftSwitch Center Installation Manual – Hardware Installation.

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.

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


1-2

Preparations

Data configuration

Local officecommissioning

Interconnectioncommissioning

Servicecommissioning

Start

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

1 Preparations for SM

The step consists of the following: Checking the construction condition Getting related technical files ready Checking system hardware, software and network

communication Making an empty backup file for the BAM database

2 Data configuration Perform data collection and planning, and make and check data script.

3 Local office commissioning

The step consists of the following: Configure internal data (hardware data and local office data) Load boards and check them Perform commissioning to the local office equipment

4 Interconnection commissioning

Perform data configuration and commissioning for the connection between the MSOFTX3000 and the MGW, MSC, as well as HLR.

5 Service commissioning Perform configuration and commissioning for service data.

Installation Manual – System Commissioning HUAWEI MSOFTX3000 Mobile SoftSwitch Center

Chapter 2 Preparations for System Commissioning


2-1


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:

Checking construction conditions Checking if technical files needed for deployment are complete Checking hardware configuration and power supply Checking versions and running of software Checking the network communication of the operation and maintenance system 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 installation is completed Y; N

Whether the installation of hardware has been checked

Y; N Hardware

Whether the equipment is powered on Y; N

For the installation of hardware and software, refer to HUAWEI MSOFTX3000 Mobile SoftSwitch Center Installation Manual. Software installation does not include data configuration and board software loading.




2-2


Whether the software for the BAM, local maintenance terminal (LMT) and emergency workstation (EWS) has been installed

Y; N

Whether the virtual local area network (VLAN) of the core LAN Switch has been configured

Y; N

Software

Whether the installation of software has been checked

Y; N

2.3 Checking Technical Documents

Table 2-2 Technical documents needing to be prepared

<Item Result Remarks

Network Plan Y; N This document is to be completed by the design unit designated by the customer, and should be sent to the vendor in duplicate before product delivery.

Site Survey Report Y; N This document is to be filled out by Huawei technicians while doing the site survey.

Engineering Documents Y; N

This document is to be prepared by the engineering department of Huawei based on the office configuration and networking of the customer, and to be delivered to the site with the equipment.

Package of Documents Y; N

The documents include the Installation Manual, Operation Manual, Hardware Description Manual, Maintenance Manual, and iGWB User Manual. They are to be delivered to the site with the equipment.

Software and Data Script Y; N This document is to be supplied by Huawei.

Other Engineering Documents Y; N The documents include the contract agreement, system

configuration table and delivery list.




2-3

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:

Before touching any board, you must wear an electrostatic discharge (ESD) preventive wrist strap, which should be properly grounded.

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:

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.

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 server and auxiliary equipment

Whether the BAM server, iGWB server, LMT, EWS, and alarm box are consistent with the delivery list

Y; N

Check the cabinets and subracks

Whether the number of cabinets and subracks is consistent with that written in the delivery list and Engineering documents.

Y; N

Check board configuration

Whether the configuration of boards in subracks is consistent with the delivery list and the Engineering Documents, and whether board positions are correct.

Y; N

If hardware configuration is not consistent with the delivery list and Engineering Documents, contact Huawei technical support staff for help at once. For description of DIP switches of the WSIU, refer to HUAWEI MSOFTX3000 Mobile SoftSwitch Center




2-4


Check board versions

Check software versions and hardware versions of boards according to the version configuration information.

Y; N

Check the setting of subrack numbers

Whether the setting of DIP switch S3 of the WSIU is consistent with the subrack number.

Y; N

Hardware Description Manual.

2.4.2 Checking Power Supply

Table 2-4 Checking the power supply


Whether all the –48 V power output switches in the power distribution subrack are set to “ON”.

Y; N

Whether the green “RUN” indicator on the front panel of the power distribution subrack flashes, and the red “ALM” indicator is off.

Y; N Check the power distribution subrack

Whether the alarm sound stopping switch on the front panel of the power distribution subrack is on, and the alarm buzzer is silent.

Y; N

Note: When the WSMU has not been powered on or the software of it has not been loaded, the “ALM” indicator of the power distribution subrack will flash at 4-Hz rate with an alarm sound. This shows that the communication between the power distribution subrack and the WSMU is interrupted. You need not worry about it.

Check subrack fans

Whether the fans run normally, and the “STATUS” fan indicator flashes in green.

Y; N

Note: When the WSMU is not powered on or the software of it is not loaded, the “STATUS” indicator of the fan box will blink fast. It shows that the communication between 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.

Check power boards in subracks

Whether the green “RUN” indicator on the UMSC PSM power module (UPWR) is on, and the red “ALM” indicator is off.

Y; N

Check the server

Whether the indicator of the BAM and iGWB power switch is in green.

Y; N If this indicator is in orange, it shows that the server is standby.




2-5


hCheck the LAN Switch

Whether the green “POWER” indicators on the panels of LAN Switch 0 and LAN Switch 1 are on.

Y; N If the “POWER” indicators are not on, it shows that power supply for the LAN Switches is faulty.

2.5 Checking Versions and Running of Software

You need to check the version information and running status of the software installed on the BAM, LMT, and 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


Check the software version

On the BAM, start “HUAWEI Local Maintenance Terminal”, select [Help/About], check the version number of the BAM server software, and confirm if the version meets the requirement of site deployment.

Y; N

If the version of the BAM server software does not meet the requirement of site deployment, contact Huawei technicians for help timely, and re-install the BAM server software if necessary.

Check the running state of the SQL Server

On the BAM, check if the icon is in the taskbar on the

bottom right corner of the desktop.

Y; N

If the icon is there, it shows that the SQL Server 2000 service manager starts automatically and runs normally. If the icon is not there, it shows that the SQL Server 2000 service manager is not started. Select [Start/Programs/Service Manager] on the BAM to start the SQL Server 2000 service manager.

Check the running of services

On the BAM, select [Start/Programs/Administrative Tools/Services] to display the [Services] window. Check services “BAM Service”, “Smirror”, and “Performance Logs and Alerts” to see if their statuses are displayed as “Started” and their startup types are “Automatic”.

Y; N

If the status of any service is “Stopped” or its startup type is not “Automatic”, you can start the service or modify its startup type in the [Services] window which pops up when you double-click the service. If the problem still exists, contact Huawei technicians for help at once, and re-install the BAM software if necessary.




2-6


Check the running of processes

On the BAM, double-click the icon in the taskbar on the

bottom right corner of the desktop to display the [BAM Manager] window. Check service processes, including “Warn”, “DataMan”, “Maintain”, “Stats”, “MML”, “Exchange”, “FTPMan”, “XSman”, and “NTPClient”, to see if their statuses are all “Started”.

Y; N

If the status of a process is “Exception”, it shows that the process is abnormal. You can solve the problem by closing the BAM server program and then restarting it. If the problem still exists, contact Huawei technicians for help at once, and re-install the BAM software if necessary.

Check the SetWin2000 security customization tool

On the BAM, open the log file under the installation directory of SetWin2000 to check if security items have been customized. For example, “Setting directory access authority control completed” shows that you have set directory access authority control.

Y; N

The default installation directory is: C:\Program Files\Huawei Technologies Co., Ltd\Windows 2000 security customization tools

Check SysPatron

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

Y; N

Check BAM restart

On the BAM, select [Start/Shut Down…] to display the [Shut Down Windows] window, select “Restart” for operation type, and then restart the BAM. After restart, the system will automatically log in to the BAM server as the Administrator. You need not input the login password.

Y; N

If you are prompted to press the combination keys <Ctrl+Alt+Del> for login, it shows that the setting for automatic login to Windows 2000 Server fails. Refer to the HUAWEI MSOFTX3000 Mobile SoftSwitch Center Installation Manual – Software Installation to redo the setting.




2-7


After BAM restart, the icon appears in the taskbar on the bottom right corner of the desktop.

Y; N

If the icon is there, it shows that the SQL Server 2000 service manager can start automatically and can run normally.

After BAM restart, the [BAM Manager] window will pop up automatically, and the icon appears in the taskbar on the bottom right corner of the desktop, indicating that BAM Manager can run automatically.

Check all the service processes on the [BAM Manager] window to see if their statuses are all “Started”.

Y; N

If BAM Manager cannot run automatically or some service processes are in the “Exception” status, it shows that the system cannot run normally or the installation of the BAM server software fails. If this is true, contact Huawei technicians for help at once and re-install the BAM software if necessary.

2.5.2 Checking Software of Emergency Workstation

Table 2-6 Checking the software of the EWS


Check software version

On the EWS, start “HUAWEI Local Maintenance Terminal”, select [Help/About], check the version of the software, and confirm if the version is identical with that of the BAM server software and if it meets the requirement of site deployment.

Y; N

If the software version is not the same as that of the BAM server software or cannot meet site deployment requirement, contact Huawei technicians for help at once.

Check the running of the SQL Server

On the EWS, check if the icon appears in the taskbar on the

bottom right corner of the desktop.

Y; N

If the icon is there, it shows that the SQL Server 2000 service manager can start automatically and can run normally.

Check the running of services

On the EWS, select [Start/Programs/Administrative Tools/Services] to display the [Services] window, check the status of services “BAM Service” and “Smirror”. The status of “Smirror” should be “Started” and its startup type should be “Automatic”. The status of “BAM Service” should be “Stopped”, and its startup type should be “Manual”.

Y; N

You can start a service or modify its startup type in the [Services] window by double-clicking this service. If this fails, contact Huawei technicians for help at once, and re-install the software of the EWS if necessary.




2-8

2.5.3 Checking Software of LMT

Table 2-7 Checking the software of the LMT



On a MSOFTX3000 client, start “HUAWEI Local Maintenance Terminal”, select [Help/About], check the version of the software, and confirm if the version is identical with that of the BAM server software and meets the requirement of site deployment.

Y; N

If the version of the software is not the same as that of the BAM server software or does not meet the requirement of site deployment, contact Huawei technicians for help at once; and re-install the BAM software if 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 [Start/Programs/iGateway Bill V200 Client/iGWB Client] to start and log in to the bill console. Select [Help/About] to check if the software version meets the deployment requirement.

Y; N

If the version of the software does not meet the requirement of site deployment, contact Huawei technicians for help at once; and re-install the iGWB software if necessary.

Check dual-system heartbeat

On the iGWB operation and maintenance terminal, select [Start/Programs/iGateway Bill V200 Client/iGWB Client] to start and log in to the bill console. Select [Operation/State Query] to check the heartbeat state. Normally, the heartbeat state should be “2/2”.

Y; N

This operation only applies to dual-system configuration office. For “2/2”, the denominator shows the total number of heartbeat links, and the numerator shows the number of current available links, which should be the same.




2-9


Check the running of processes

Start Windows 2000 task manager on the active and standby iGWB servers, and then click [Processes] tab to check if such processes as cls_proc.exe, ap_proc.exe, knl_proc.exe, and om_proc.exe are running.

Y; N

On the active iGWB server, all the processes should be running. On the standby iGWB server, only the process cls_proc.exe should be running. The number of the process ap_proc.exe on the active iGWB server should be the same as the value set for the parameter “APCount”. This parameter is under the configuration item [Common] in the configuration file igwb.ini.

Check iGWB restart

On the active and standby iGWB servers, select [Start/Shut Down…] to display the [Shut Down Windows] window, select “Restart” for operation type, and then restart the iGWB. After restart, the system will automatically log in to the iGWB server as the Administrator. You need not input the login password.

Y; N

If you are prompted to press the combination keys <Ctrl+Alt+Del> for login, it shows that the setting for automatic login to Windows 2000 Server fails. Refer to the iGWB User Manual to redo the setting.

Close the active iGWB (iGWB 0).After five minutes, the standby iGWB server (iGWB 1) becomes the active one, its power indicator is on in green, and the processes cls_proc.exe, ap_proc.exe, knl_proc.exe, and om_proc.exe are running normally.

Y; NCheck iGWB switchover

On the iGWB operation and maintenance terminal, select [Start/Programs/iGateway Bill V200 Client/iGWB Client] to start and log in to the bill console. Select [Operation/State Query] to check if the active iGWB is in normal state.

Y; N

If the switchover between the active and standby iGWB servers fails, or some processes cannot run normally, or the currently active iGWB is not normal, it shows that the MSOFTX3000 has problems in operation or the installation of the iGWB server software fails. In this case, contact Huawei technicians for help at once and re-install the iGWB software if necessary.




2-10


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. At the same time, iGWB 1 is standby, its power indicator is in orange, and only the process cls_proc.exe is running.

Y; N

On the iGWB operation and maintenance terminal, select [Start/Programs/iGateway Bill V200 Client/iGWB Client] to start and log in to the bill console. Select [Operation/State Query] to check if the active iGWB is in normal state and if the dual-system heartbeat state is normal.

Y; N

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

WAN

WAN WAN

LAN Sw itch 0 LAN Sw itch 1

Bound toBilling Center

Bound toBilling Center

standby iGWB BAM Emergencyw orkstation active iGWB

HUB or LANSw itch Bound to

NMC

WSMUWSIU

WHSC

WSMUWSIU

WHSC

Service processing frame

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 adapter ID Opposite equipment IP address/mask

Network adapter 0

It communicates with the LMT and the EWS through an external HUB or LAN Switch.

To be provided by the customer

Network adapter 1

It is bound to LAN Switch 0, and communicates with the active plane of the host.

172.20.200.0/ 255.255.0.0

Network adapter 2

It is bound to LAN Switch 1, and communicates with the standby plane of the host.

172.30.200.0/ 255.255.0.0

Network adapter 3 Standby –




2-12

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 ID Opposite equipment IP address/mask

Network adapter 0 It communicates with the BAM through an external HUB or LAN Switch.


Network adapter 1 It is standby. In emergency cases, it is connected to LAN Switch 0 for communicating with the host.

172.20.200.0/ 255.255.0.0

Network adapter 2 It is standby. In emergency cases, it is connected to LAN Switch 1 for communicating with the host.

172.30.200.0/ 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 adapter ID Opposite equipment IP address

Network adapter

It communicates with the BAM through an external HUB or LAN Switch.


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

WSMU in slot 6 172.20.subrack number.100/16

172.30.subrack number.100/16 Before

board loading WSMU in slot 8 172.20.subrack

number.101/16 172.30.subrack number.101/16




2-13

Slot IP address 1 / mask IP address 2 / mask

WSMU in slot 6 172.20.200.module number/16

172.30.200.module number/16 After

board loading WSMU in slot 8 172.20.200.module

number/16 172.30.200.module number/16

Note:

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.

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:

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.

The customer needs to provide the virtual IP addresses for communication with the bill console and billing center.

The IP addresses must be the same as those set in the file igwb.ini.

Table 2-13 IP addresses of the iGWB

Network adapter ID

Opposite equipment

Network adapter IP of active iGWB

Network adapter IP of

standby iGWB

Virtual IP/mask

Netcard0 to Office LAN

It is bound to the bill console and network management system interface, and acts as the first heartbeat link of the iGWB dual-host system.

130.1.3.1 130.1.3.2





2-14

Network adapter ID

Opposite equipment

Network adapter IP of active iGWB

Network adapter IP of

standby iGWB

Virtual IP/mask

Netcard1 to 0#LAN Switch

It is bound to LAN Switch 0, and communicates with the active plane of the host.

130.1.1.1 130.1.1.2

172.20.200.1/ 255.255.0.0

Netcard2 to 1#LAN Switch

It is bound to LAN Switch 1, and communicates with the standby plane of the host.

130.1.2.1 130.1.2.2

172.30.200.1/ 255.255.0.0

Netcard3 to Billing Center

It is bound to the billing center, and provides billing interface.

130.1.4.1 130.1.4.2


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

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 the setting of the IP address

Check if the IP addresses of the BAM and iGWB are correctly set based on the description in 2.6.1 I. IP Address of the BAM Server.

Y; N In the internal LAN, the IP address of each component is fixed.

Check the communication between the BAM and host

On the BAM, ping the IP address of the WSMU in each subrack (for the IP address setting, refer to 2.6.1 IV. IP Address of WSMU). If the ping command is executed successfully, it shows that the communication between the BAM and host is normal.

Y; N

Check the communication between the BAM and iGWB

Ping the IP addresses of the iGWB 172.20.200.1 and 172.30.200.1 from the BAM. If the ping command is executed successfully, it shows that the communication is normal.

Y; N

Check the communication between the iGWB and host

On the iGWB, ping the IP address of the WSMU in each subrack (for the IP address setting, refer to 2.6.1 IV. IP Address of WSMU). If the ping command is executed successfully, it shows that the communication is normal.

Y; N

If the ping command is not executed successfully, it shows that the communication is abnormal. Check the connection of Ethernet cables, if the IP addresses of the BAM and iGWB are correctly set, and if the DIP switch on the WSIU that determines subrack numbering is correctly set.

Check the setting of VLAN

Based on the description in HUAWEI MSOFTX3000 Mobile SoftSwitch Center Installation Manual – Software Installation, log in to the LAN Switch through a serial port, execute the command display vlan all, and check if VLAN is correctly set.

Y; N

For details, refer to the description on setting VLAN in HUAWEI MSOFTX3000 Mobile SoftSwitch Center Installation Manual – Software Installation.




2-16


Turn off the power switch (SW6) of LAN Switch 1. Check if the communication between the BAM and the host is normal or not according to the related description above.

Y; N

Check the Ethernet biplane switchover function

Turn on the power switch of LAN Switch 1 (SW6), and turn off the power switch (SW5) of LAN Switch 0. Check the communication state between the BAM and the host according to the related description above.. After the check, turn on the power switch (SW5) of LAN Switch 0.

Y; N

Caution: Before turning off the power switch of LAN Switch, make sure you have saved the current data of the LAN Switch.

Note: After logging in to the LAN Switch, you can enter the save command to save the current configuration of the LAN Switch.

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


Check the setting of IP addresses

Check if the IP addresses of the BAM, LMT, EWS, and iGWB are correctly set.

Y; N

In the external LAN, the IP address of each component is to be provided by the customer.




2-17


Check the communication between the BAM and LMT

Ping the IP address of the LMT on the BAM; ping the IP address of the BAM from the LMT. If the ping command is executed successfully, it shows that the communication is normal.

Y; N

Check the communication between the BAM and the EWS

Ping the IP address of the EWS on the BAM; ping the IP address of the BAM from the EWS. If the ping command is executed successfully, it shows that the communication is normal.

Y; N

Check the communication between the BAM and iGWB

Ping the IP address of the iGWB from the BAM; ping the IP address of the BAM from the iGWB. If the ping command is executed successfully, it shows that the communication is normal.

Y; N

If the communication is abnormal, check if the IP address of each component is correctly set, if Ethernet cables are correctly connected, and if the external HUB or LAN Switch works normally.

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


Check the communication between BAM and NMC

Ping the IP address of the NMC server (to be provided by the customer) on the BAM. If the ping command is executed successfully, it shows that the communication is normal.

Y; N

Check the communication between the iGWB and billing center

Ping the IP address of the billing center server (to be provided by the customer) from the iGWB. If the ping command is executed successfully, it shows that the communication is normal.

Y; N

If the communication is abnormal, check if the IP address is correct, if Ethernet cables are correctly connected, if devices connected to the WAN (like routes) can work normally, and if route data is correctly set.




2-18

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

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

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.

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


3-1

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:

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

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

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:

Networking mode Equipment configuration: board configuration in subracks, links provided by

boards Data for external interfaces and interworking negotiation: signaling link, IP

addresses, port numbers 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-3

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:

Networking data External interface data Interworking and negotiation data Service data collected on site

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


4-1

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

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.

DE=NO (data unavailable): The data in the Flash memory of the board is unavailable. Data has to be loaded from the BAM.

DW=NO (data not writable): It is not allowed to write data to the Flash memory. 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-3

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

1 Start the LMT client

On the LMT, start the client program of the MSOFTX3000 O&M software, and log in to the BAM.

If you cannot log in to the BAM, check if the username and password are correct, and if the cable between LMT and BAM is properly connected.

2

Offline, and format conversion off

Open the MML window and execute the following commands: LOF:; SET FMT: STS=OFF;

The meanings of the commands: LOF: Offline SET FMT: format conversion on/off

3 Execute data script files

Press shortcut keys <Ctrl + E> to display the [MML Batch] window, and execute data script files in sequence. Upon completing every script, check the “Total Result” box in the lower part of the window, to see if the MML commands are all executed successfully.

For detail on operations to data script files, refer to section 3.2.3 “Method for Executing Data Script” in Chapter 3. For commands that fail in the execution, use the empty BAM database backup to recover the database, so as to clear the configuration data. For detail on database backup and recovery, refer to HUAWEI MSOFTX3000 Mobile Softswitch Center Operation Manual – GUI guide.

4 Format conversion on, online

Execute the following commands in the MML window: SET FMT: STS=ON; LON:;

The meanings of the commands: SET FMT: format conversion on/off LON: online



4-4


5

Modify the loading software switch of a board

Execute the following command in the MML window: MOD LSS: PE=NO, DE=NO, DW=YES, PW=YES;

The meaning of this command: Modify the loading software switch of a board as “program unavailable, data unavailable, data writable, program writable.”

6 Format data

Execute the following commands on the MML window: FMT:;

It will take quite a long time to execute the command FMT. If the system prompts executing command timeout, select [System/Command Timeout 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


Check the running of BAM processes

On the BAM, double-click the icon in the taskbar on the lower right corner of the desktop to display the [BAM Manager] window. Check service processes, including “Exchange” and “DataMan”, to see if their statuses are all “Started”.

Y; N

Refer to section 2.5.1 “Checking Software of BAM” in Chapter 2.

Check the communication between the BAM and host

Ping the WSMU of each subrack on the BAM. If the ping command is executed successfully, it shows that the communication is normal.

Y; N

Refer to section 2.6.3 “Checking Communication of Internal LAN” in Chapter 2.

Check the files loaded

Check the directory “D:\Data\” of the BAM to see if the load source files are there.

Y; N

Refer to section 4.2.4 “Description of Source Files Related to Loading”.



4-5

4.4.2 Loading Process

I. Operation Steps

Table 4-3 Steps for loading boards


1 Power off all subracks

Set SW4, SW5, and SW6 of the power distribution subrack in the integrated processing cabinet to “off”; and set SW1–SW6 of the power distribution subrack in the service processing cabinet to “off”.

For the relations between cabinet components and switches of the power distribution subrack, refer to Table 4-4.

2

Set SW4 of the power distribution subrack in the integrated processing cabinet to “on”, and power on the basic subrack. If the system works normally, software and data will be automatically loaded from the BAM.

Caution: At this time, do not set SW5 to “on” for fear that expansion subrack 1 is powered on.

3

On the BAM, double-click the icon in the taskbar on the lower right corner of the desktop to open the [BAM Manager] window. Select the “Exchange” process in the “Service”

column. Click the icon in the toolbar to open the [Exchange] window. Check if there is any loading request for the basic subrack.

If there is no loading request, check the connection of Ethernet cables and the setting of SWIU DIP switches.

4

Load the WSMU first, and then the other front boards, excluding the UPWR and wireless alarm unit (WALU). Observe the green “RUN” indicator on the front board. Its blinking frequency during loading is 4 Hz.

Blinking frequency of the “RUN” indicator for different cases: Program loading: 4 Hz; Normal running: 0.5 Hz; Standby board indication: 0.25 Hz.

5

Power on the basic subrack and start loading

After loading, check if the loading is successful by referring to 4.4.3 Checking If Loading Is Successful.

If the loading fails, find and remove the fault first. Then go on loading the boards in the other subracks.

6

Power on expansion subrack 1 and start loading

After confirming the basic subrack has been successfully loaded, set SW5 and SW6 of the power distribution subrack in the integrated processing cabinet to “on”, and power on expansion subrack 1. If the system works normally, it will load the software and data automatically from the BAM.

If there is no loading request, check the connection of Ethernet cables and the setting of SWIU DIP switches. If the loading fails, solve the problem. Go on loading other expansion



4-6


7 Refer to Step 3. Open the [Exchange] process window and check if there is any load request.

8

Refer to Step 4. Observe the green “RUN” indicator on the front board. Its blinking frequency during loading is 4 Hz.

9 After loading, check if the loading is successful by referring to 4.4.3 Checking If Loading Is Successful.

subracks only after the problem has been solved.

10

Power on other expansion subracks and start loading

Follow the above steps to power on other expansion subracks and restart them one by one, and check if loading is successful.

For the relations between cabinet components and switches of the power distribution subrack, 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-7

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

SW5 LANS-0

SW1, SW6 ARRAY (Hard disk array)

SW2, SW3 SERVER-3 (BAM)

SW2, SW3 SERVER-2 (iGWB 1)

SW1, SW2 SERVER-1 (iGWB 0)

Integrated configuration cabinet

SW1, SW2 SERVER-0 (A server for other services, Optional)




Service processing cabinet




4-8

4.4.3 Checking If Loading Is Successful

Table 4-5 Checking after loading boards


Check the running of boards

On the LMT client maintenance console, click the [Device Panel] tab, select [Device Management], open the equipment panel view, and check the running of boards.

Note: On the front view of a subrack, there are some small squares, indicating the statuses of back boards in corresponding slots. To find detailed information of a board, double-click the triangle on the left side of the subrack view. A subrack status diagram of the board will be displayed.

Y; N

Relations between board indicator colors and board running statuses: Green: The board is running normally and in the active state. Blue: The board is running normally and in the standby state. Red: The board has fault. Gray: No board has been configured for this slot. Also, there are two small squares on the wireless calling control unit and signaling process unit (WCSU), which shows the running of the upper pinch card and lower pinch card on the WCSU.

Check board software version

On the LMT client, execute the DSP EXVER command to query the software versions of all boards (modules) that can be loaded, and confirm if they are consistent with the software version of the BAM.

Y; N

If not, run the LST LSS command to check if the switches for software loading of the board are correctly set, that is, if they are set to “program unavailable”, “data unavailable”, “data writable”, and “program writable” respectively. If the switches are not in such statuses, adjust them accordingly. After that, reset the board and reload it.

Verify board data

On the LMT client, run the command STR CRC:MN=255; to perform the cyclic redundancy check (CRC) on the data of boards (modules) that can be loaded.

Y; N

If the check fails, reset the board and reload it. !Note: It will take quite a long time to execute the command STR CRC. If the system prompts executing command timeout, select [System/Command Timeout Setting…] on the LMT client to extend the time-out setting.



4-9

4.4.4 Handling of Loading Problems

I. Basic Solution

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

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.

Whether data configuration is correct. Whether there are errors in critical data configuration, which may lead to loading failure.

Whether loading files in the BAM are complete. What about software parameters such as the maximum number of tuples. Whether the setting of DIP switch S3 of the WSIU is consistent with the subrack

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

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.

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

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.

Expansion frame B(rear view)

Basic frame(rear view)

BITS

2M clock cable

Expansion frame A(rear view)

8K clock cable

WEPI

WEPI

BITS

WCKI

WCKI

WEPI

WEPI

WEPI

WEPI

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

Basic subrack: The WCKI provides a clock, which will be locked by WEPIs through the backplane bus.

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.

Expansion frame B(rear view)

Basic frame(rear view)

Expansion frame A(rear view)

8K clock cable

WEPI

WEPI

WCKI

WCKI

WEPI

WEPI

WEPI

WEPI

E1 to peer office

2M clock cable

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

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 Basic subrack: The WCKI provides a clock, which will be locked by WEPIs through

the backplane bus. 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-13

Table 4-6 Checking the connection of clock cables


If the MSOFTX3000 locks the BITS clock, the 2M clock cables outputted from BITS should be respectively connected to sub-miniature B (SMB) connectors BITS1 and BITS2, corresponding to the active and standby WCKIs of the basic subrack.

Y; N

If the MSOFTX3000 locks the peer office clock, this needs not to be checked. A 2M clock cable is a double shielded coaxial cable. The cable connector is a 75-ohm SMB connector. Check external

clock cables

If the MSOFTX3000 locks the peer office clock, in the basic subrack, one end of the 2M clock cable should be connected to LINE1 and LINE2 corresponding to the active and standby WCKIs, and the other end, the active WEPI of the basic subrack.

Y; N

If the MSOFTX3000 locks the BITS clock, this needs not to be checked. A 2M clock cable is a double shielded coaxial cable. The cable connector is a 75-ohm SMB connector.

Check internal clock cables

The 8k clock cables outputted from the active and standby WCKIs of the basic subrack should be respectively connected to a pair of active and standby WEPIs of each expansion subrack (defaulted as slots 0 and 1). The 8K-A interface of the WEPI is connected to the WCKI in slot 13 of the basic subrack, and the 8K-B interface of the WEPI is connected to the WCKI in slot 15 of the basic subrack.

Y; N

The 8k clock cable is a twisted pair cable with shielded crystal connectors, like a straight through cable. If the WEPI connected with the 8k clock cable is not in slots 0 and 1 of expansion subracks, data needs to be modified using the SET CLKSRC command.



4-14

4.5.3 Commissioning Steps for Locking BITS Clocks

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

Item Operation Remarks

Check the status of the clock phase-locked loop circuit of the WCKI

Run the DSP CLKPH command to check the status of the clock phase-locked loop circuit of the WCKI. If the status is “Trace Mode”, it shows that the clock phase-locked loop circuit on the WCKI can normally trace the BITS clock.

Note: The phase-locking time of the WCKI is relatively long, about half an hour.

If the status is “Free Run”, it shows that the clock phase-locked loop circuit on the WCKI cannot normally trace the BITS clock. Then, run the LST CKICFG command to carefully check if the configuration for the following parameters is correct: clock level, work mode, priority of each clock source, signal type of the BITS1 interface, and signal type of the BITS2 interface.

Check the clock status of the WEPI

Run the DSP CLKSTAT command to sequentially check the clock statuses of WEPIs (as clock sources) in expansion subracks to see if they are normal. !Note: By default, WEPIs in slots 0 and 1 of each expansion subrack act as clock sources.

If the clock status of a WEPI is abnormal, proceed as follows: Run the LST CLKSRC command to check if the clock reference sources of WEPIs of each subrack are correctly configured. If the clock data is correct, check if the clock wiring inside the device is correct. If both the clock data configuration 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


Check the statuses of E1 ports

Run the DSP PORT command to check the status of the E1 port on a WEPI of this office that locks the E1 clock of a peer office and see if it is normal.

The WEPI can introduce the E1 clock of the peer office only when the E1 port of this office is in the “Normal” status.



4-15


Check the status of the clock phase-locked loop of the WCKI

Run the DSP CLKPH command to check the status of the clock phase-locked loop of the WCKI. If the status is “Trace Mode”, it shows that the clock phase-locked loop circuit on the WCKI can normally trace the peer office clock. !Note: The phase-locking time of the WCKI is relatively long, about half an hour.

If the status is “Free Run”, it shows that the clock phase-locked loop circuit on the WCKI cannot normally trace the peer office clock. Then, run the LST CKICFG command to carefully check if the configuration for the following parameters is correct: clock level, work mode, and priority of each clock source.

Check the clock status of the WEPI

Run the DSP CLKSTAT command to sequentially check the clock statuses of WEPIs (as clock sources) in expansion subracks to see if they are normal.

Note: By default, WEPIs in slots 0 and 1 of each expansion subrack act as clock sources.

If the clock status of a WEPI is abnormal, proceed as follows: Run the LST CLKSRC command to check if the clock reference sources of WEPIs of each subrack are correctly configured. If the clock data is correct, check if the clock wiring inside the device is correct. If both the clock data configuration and 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


Check the LAN Switch

Whether the power indicators of LAN Switch 0 and LAN Switch 1 are on, and whether the indicators of all Ethernet interfaces that have been properly connected and put into use are in normal statuses.

Y; N

By pressing the MODE button on the front board, the port state indicator is switched to A/L. The normal state of the Ethernet port indicator is as follows: The yellow "Active" indicator at the left side of the port flashes, it shows data sending and receiving is normal. The green "Link” indicator at the right side of the port lights up, it shows the link is normal.



4-16


Whether the green “RUN” indicator on the front panel of the power distribution subrack flashes at 0.5-Hz rate, and the red “ALM” indicator is off.

Y; N

If the “RUN” indicator is off, it shows that there is no power input or the power distribution subrack is faulty. If the “ALM” indicator is on, it shows that the power distribution subrack is faulty. Check the power

distribution subrack Whether the alarm sound stopping switch on the front panel of the power distribution subrack is on, and the alarm buzzer is silent.

Y; N

If the alarm sound stopping switch is off, there will be no alarm prompt tone when the power distribution subrack is faulty.

Check fans

Whether fans run normally, and the green “STATUS” indicator flashes at 0.5-Hz rate.

Y; N

If the "STATUS" indicator flashes fast in green, it shows that the communication between the fan and the WSMU is faulty. If the "STATUS" indicator flashes in red, it shows that the fan is faulty.

Whether the “RUN” indicator on the WALU is on.

Y; N

If the “RUN” indicator is off, it shows that the board is faulty. If it is red, it shows that the communication between the board and the WSMU is in trouble.

Except on the UPWR and WALU, whether the green “RUN” indicators on the front panels flash, and the red “ALM” indicators are off.

Y; N

Blinking frequency of the “RUN” indicator for different cases: Program loading: 4 Hz; Normal running: 0.5 Hz; Standby board indication: 0.25 Hz.

Check the indicators on front boards

Whether the green Ethernet port indicator, “LINK”, on the IP forward module (WIFM) is on.

Y; N

The “LINK” indicator is a network connection indicator. It is on when the physical connection is normal, and is off in other cases.

Whether the green “RUN” indicator on the WEPI flashes at 0.5-Hz rate, and the red “ALM” indicator is off.

Y; N If the “ALM” indicator flashes, it shows that the board is faulty.

Check indicators on back boards Whether the green “RUN”

indicator on the WCKI flashes at 0.5-Hz rate, and the red “ALM” indicator is off.

Y; NIf the “ALM” indicator is always on, it shows that the board is faulty.



4-17

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


Check the power distribution subrack

Run the DSP ENVSTAT command to check the statuses of the power distribution subrack, input power, temperature, humidity and the output switch.

The statuses should all be “Normal” under normal conditions.

Check fans Run the DSP FAN command to check the running of fans.

The statuses should all be “Normal” under normal conditions.

Run the DSP FRM command to check the statuses of fans.

The statuses must not be “Fault” under normal conditions.

Run the DSP BRD command to check the status of the WALU of each subrack and the subrack temperature.

For example: DSP BRD: FN = 0, SN = 16;

Run the DSP COMM command and select “TCP” for port type (COMT) to check the communication between the WSMU and BAM.

For example: DSP COMM: FN = 0, SN = 6, COMT = TCP;

Check boards

Run the DSP COMM command and select “SP” for port type (COMT) to check the communication between the WSMU and the serial ports of the back boards, WALU, fan, and power distribution subrack.

Usage of each serial port: 0–16: back boards in corresponding slots; 17: WALU; 18: fan; 19: power distribution subrack.

Check FE ports Run the DSP PORT command to check the statuses of FE ports.

Statuses of FE ports (service Ethernet ports) should all be “Normal”.



4-18


Check the communication between the WIFM and the default gateway.

On the LMT client, use the “PING” function to check if the connection between the WIFM and the default gateway is normal. !Note: The IP address, mask and default gateway of the WIFM have been defined in the ADD FECFG command.

If the returned information is “Reply from *.*.*.* ... time<10ms ...”, it shows that the communication is normal. If the time in the returned information is too long, or if the returned information is “Request Timed out”, it shows that the communication is abnormal.

4.6.3 Hardware Switchover Verification

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


Verification of the active/standby switchover for the front boards

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 the “RUN” indicator of the active board should be 0.5 Hz, and that of the RUN” indicator of the standby 0.25 Hz.

4) Run the DSP FRM command to check the statuses of the active and standby boards after the switchover. The status of the active board should be “Main OK”, and that of the standby board “Standby OK”.

5) Run the SWP BRD command again to perform active/standby switchover.

6) Follow Steps 2–4 and observe the statuses of the active and standby boards after the switchover.

7) Repeat the above steps to perform switchover for all front boards with active/standby configuration, and observe if the switchover is successful.

Caution: After the initial switchover for a board, perform switchover again to restore the original configuration, and at the same time observe if the switchover is successful.



4-19

4.6.4 Self-Loop Test for Local Office E1 Cables

Note:

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

Warning:

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

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


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

2 Perform local self-loop test on the first E1 with a connector.

3

Run the DSP PORT command to check the status of the first E1. Its status should be “Normal”. If not, check the connection of the E1 cable on the distribution subrack.

4 When the first E1 is normal, repeat the above steps to 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:

PE=YES (program available): The program will be loaded from the Flash memory when a board restarts.



4-20

DE=YES (data available): Data will be loaded from the Flash memory when a board restarts.

DW=YES (data writable): It is allowed to write data into the Flash memory. 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.

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


5-1

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:

Connecting with the media gateway (MGW); Connecting with the base station controller (BSC); Connecting with home location register (HLR), short message center (SMC),

service control point (SCP) and serving GPRS support node (SGSN); Connecting with other mobile switching centers (MSC) through ISDN user part

(ISUP) and mobile application part (MAP); Connecting with other MSCs through ISUP/M3UA; Connecting with other MSCs through bearer independent call control protocol

(BICC); 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, Huawei’s 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-2

SCTP

IP

H.248

MSOFTX3000

IP

MGW

H.248/SCTP

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




2

Enable format conversion function, and get online

Open the MML window and execute the following commands: SET FMT: STS=ON; LON:;

The meanings of the commands: SET FMT: enable or disable format conversion function LON: get online



5-3


3 Execute data script

Press shortcut keys <Ctrl + E> to open the [MML Batch] window, and execute data script file. Upon completing, check the “Total Result” box in the lower part of the window, to see if the MML commands are all executed successfully.

For detail on operations on data script file, refer to section 3.2.3 “Method for Executing Data Script” in Chapter 3.

4 Perform CRC on board data

On the MML window, run the command STR CRC: MN=255; to perform CRC on the data of boards (modules) that can be loaded.

If the verification fails, reset the board and reload it. It will take quite a long time to execute the command STR CRC. If the system prompts executing command 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


Observe the indicators on the WIFM. The green Ethernet port connection indicator “LINK” should be on, while the yellow Ethernet port data traffic indicator “ACT” should flash.

The “LINK” indicator is on when the physical connection is normal, and is off in other cases. When the “ACT” indicator flashes, it shows that there is data being sent/received. The blinking frequency shows the amount of data traffic. Check the

network connection On the LMT client, use the

interface tracing function “PING” to check the communication between the WIFM and MGW. If the ping command is executed successfully, it shows that the communication is normal.

In case of failure, check if the Ethernet cables are correctly connected, if the WIFM works normally, if devices connected with the WIFM (such as a LAN Switch) works normally, and if the MGW works normally.



5-4


Check the registration status of the gateway

On the LMT client, run the DSP MGW command to check the registration status of gateway. If the display is “Normal”, it shows that the registration is successful.

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 possible that the H. 248 link communication of the Mc interface is faulty. Check the SCTP link, analyze the interaction of the Mc interface message, and take countermeasures. 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.

Check the status of the H. 248 link on Mc-interface

On the LMT client, run the DSP H248LNK command to check the status of the Mc-interface link. If it is “Valid”, it shows that the link is normal.

If the link is abnormal, start the SCTP message tracing to check if the message flow is correct and if the contents of the message is legal. Based on what is shown in the message tracing, decide other locating means, such as checking configured parameters. 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-5

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.

H248 message tracing: The MSOFTX3000 receives the “service change request” message, and then sends the “service change reply” message.

SCTP message tracing: The MSOFTX3000 receives the “INIT” message and returns the “INIT ACK” message. And then it receives the “COOKIE” message and returns the “COOKIE ACK” message, as shown in Figure 5-2.

Figure 5-2 SCTP message proceeding flow

IV. Querying Status

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

Command Function Remark

DSP MGW To query the registration status of MGW “Normal” for normal status



5-6


DSP H248LNK To query the status of H.248 link of Mc-interface “Valid” for normal status

DSP PORT To query the status of FE port “Normal” for normal status

DSP H248VER

To query the version information of H.248 None

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

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

UMG8900

BSSAP/MTP

BSC

SCCP

MTP3

MTP2MTP1

MTP

MTPTrunk (A interface)

BSSAP

Figure 5-3 Protocol stack between the MSOFTX3000 and BSC



5-8


Note:

Before system commissioning (SM), you must have completed the following: 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”. 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 online data

On the LMT client, execute the data script file.

Refer to section 5.2.2 I. “Configuring Online Data”.

Checking clock status

Before the commissioning of the MTP link, you must make sure that the clock of the MSOFTX3000 is synchronous with that of the peer device. If they are not synchronous, MTP cannot work normally.

Refer to section 4.5 “Clock Commissioning”.

Checking the registration status of gateway

On the LMT client, run the DSP MGW command to check the registration status of gateway. If “Normal” is displayed, it shows the MGW has been registered successfully.

Refer to section 5.2.2 “Steps of Commissioning”.



5-9


Remote self-loop test of E1 cables

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 connection states.

5) Follow Steps 2–4 to perform remote self-loop test to other E1 cables in sequence.

6) Notify the peer office and the transmission office of the numbers of E1s that fail in the self-loop test and are wrongly connected, in order to solve problems through negotiation among the three parties.

7) After rearranging those abnormal E1s, conduct commissioning again in the way stated above, until all the E1s pass the remote self-loop test.

8) On the LMT client of the local office, run the DSP PORT command to check the statuses of all E1 ports. If the display is “Normal”, it shows the E1 port is normal.

Caution: If it is found during the self-loop test that an E1 is abnormal while the other normal, it may be that the two E1s are wrongly connected. Such a case must also be recorded down. If an E1 is normal while another E1, which was abnormal, becomes normal, it may be that the two E1s are cross-connected. The problem can be solved by adjusting the cables on the cabling rack of the local or peer office.

On the LMT client, run the DSP N7LNK or DSP N7DLNK command to check the status of the relevant MTP link. If the status is “In Use, Healthy”, it shows the link is normal.

If the status of the link is abnormal, run the LST N7LNK command to check if the configuration of the following parameters is correct: module number, link type, start circuit number, signaling link code and signaling link code sending.

On the LMT client, run the DSP N7DSP command to check the status of relevant MTP destination signaling point (DSP). If the status is “Accessible”, it shows that the status is normal.

MTP commissioning

On the LMT client, run the DSP N7RT command to check the status of the relevant MTP route. If the status is “Healthy” and “In Service”, it shows that the status is normal.

If the statuses are abnormal, run the commands such as LST N7DSP, LST N7LKS and LST N7RT to check if the index relations of the following parameters are correct: signaling point code, destination signaling point index and link set index.

SCCP commissioning

On the LMT client, run the DSP SCCPDSP command to check the status of the SCCP remote signaling point. If the status is “Allow”, it shows the SCCP remote signaling point is normal.

If the status is abnormal, run the LST SCCPDSP command to check if the parameters such as DPC and OPC are correctly configured.



5-10


On the LMT client, run the DSP SCCPSSN command to check the status of the relevant SCCP subsystem. If the status is “Allow”, it shows the SCCP remote signaling point is normal.

If the status is abnormal, run the LST SCCPSSN command to check if the parameters such as DPC, OPC and subsystem code are correctly configured.

Commissioning of A interface trunk circuit

On the LMT client, run the DSP AIETKC or DSP OFTK command to check if the status of relevant A interface trunk circuit is normal.

If the status is abnormal, run the commands such as LST OFC, LST BSC, LST ACPOOL, and LST AIETG to check if parameters such as 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-11

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

DSP N7LSLNK

To the query status of the MTP link

“In Use, Healthy” shows the status is normal.

DSP N7DSP To query the status of the MTP destination signaling point

“Accessible” shows the status is normal.

DSP N7RT To query the status of the MTP route

“Healthy, In Service” shows the status is normal.

DSP COMM To query the status of communication between boards

“Normal” shows the status is normal.

DSP PORT To query the status of the E1 port

“Normal” shows the status is normal.

III. Self-Loop Test

Commands for self-loop test are listed in Table 5-6.

Table 5-6 Commands for self-loop test


STR PORTLOP To start E1 port self-loop

STP PORTLOP To stop E1 port self-loop

These commands are used for E1 port self-loop to test if the sending and receiving of bottom hardware messages are normal.



5-12

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:

Wrong data configuration Interruption of inter-board communication 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:

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

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.

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.

Check if the two ends are consistent when satellite links are used. If not, use MOD N7LNK to modify the tag of satellite links.

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.

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.

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:

Check the status of front boards. If it is FAULT, reset the front boards. Check the status of EPI. If it is FAULT, reset the EPI. 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:

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.

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

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

function Description

SCCP DPC

To trace the interactive messages between the SCCP of the specified signaling point and the bottom layer. The signaling point is determined by the input parameters NI, DPC and OPC.

SCCP User To trace the primitive for interacting between SCCP and the users above SCCP (for example, TCAP, BSSAP and RANAP)

SCCP MTP MG

To trace the management primitive sent from the bottom layer to SCCP, including signaling point prohibition and allowing.

TCAP SCCP To trace the primitive for interacting between TCAP and SCCP.

TCAP User To trace the primitive for interacting between TCAP and the upper layer users.

II. Querying Status

Table 5-8 Commands for querying SCCP statuses


DSP SCCPDSP

To query the status of the SCCP destination signaling point

“Allow” shows that the communication of the signaling point is normal. “Prohibit” shows that the communication of the signaling point is interrupted and the signaling point is not reachable.



5-15


DSP SCCPSSN

To query the status of the SCCP subsystem

“Allow” shows that the communication of the subsystem is normal. “Prohibit” shows that the communication of the subsystem is interrupted and the subsystem is not reachable.

TST SCCPGT

To test the translation of SCCP GT and check if the configured SCCP GT can be translated to the desirable results.

Contents of the test results: GT Index; GT Matching Length; GT Matching Content; Translating Result Type, including SPC+old GT, SPC+SSN, SPC+new GT and SPC; NI: network identification; 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:

Cause 1: The message is wrong. When test devices are used to simulate the RNC or BSC, it is easy to get wrong messages.

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.

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.

Cause 4: There are not enough connection resources. Cause 5: Upper layer subscribers do not send connection response after

timeout. Cause 6: Refused messages are sent by upper layer subscribers.



5-16

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:

Check if the offset of compulsory parameters matches the start position of the actual called address parameter.

Check if the length of the called address is the same as the actual length of the address in the message.

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.

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.

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:

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.

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

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

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.

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.

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:

The DSP or subsystem is not configured. The DSP is inaccessible. 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:

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

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.

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:

The local subsystem is not configured. The local subsystem is inaccessible. The configuration of the GT code is wrong.

3) Troubleshooting



5-19

Enable SCCP DPC tracing and analyze SCCP messages sent by the peer end. Analyze the called address in the messages:

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

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

MTPMTP

MSOFTX3000

SMC

TCAP

SCCP

MTP3

MTP2

MTP1

MAP/MTPMAP

TCAP

SCCP

MTP3

MTP2

MTP1

MAP

HLR

MAP/MTP

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.

MSOFTX3000

SCP

TCAPSCCP

MTP3

MTP2

MTP1

CAPCAP/MTP

SAU

MTP

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

MSOFTX3000

BSSAP+/MTP

SGSN

SCCP

MTP3

MTP2MTP1

MTP

BSSAP+

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










5-22











Caution: If it is found during the self-loop test that an E1 is abnormal while the other normal, it may be that the two E1s are wrongly connected. Such a case must also be recorded down. If an E1 is normal while another E1, which was abnormal, becomes normal, it may be that the two E1s are cross-connected. The problem can be solved by adjusting the cables on the power distribution subrack of the local or peer office.



5-23




On the LMT client, run the DSP N7DSP command to check the status of the relevant MTP destination signaling point. If the status is “Accessible”, it shows that the status is normal.

MTP commissioning







SCCP commissioning

On the LMT client, run the TST SCCPGT command to check if the translation of SCCP GT is correct.

If not correct, run the LST SCCPGT command to check wheterh parameters 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-24

MTPMTP

MSOFTX3000

UMG8900

MSC

TrunkISUP&MAP/MTP

ISUP

MTP3

MTP2MTP1

SCCP

MAP

TCAP

ISUP&MAP/MTP

ISUP

MTP3

MTP2MTP1

SCCP

MAP

TCAP

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

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








Checking the registration status of gateway

On the LMT client, run the DSP MGW command to check the registration status of gateway. If “Normal” is displayed, it shows the MGW has been registered successfully.











Caution: If it is found during the self-loop test that an E1 is abnormal while the other normal, it may be that the two E1s are wrongly connected. Such a case must also be recorded down. If an E1 is normal while another E1, which was abnormal, becomes normal, it may be that the two E1s are cross-connected. The problem can be solved by adjusting the cables on the power distribution subrack of the local or peer office.



5-26




On the LMT client, run the DSP N7DSP command to check the status of the relevant MTP destination signaling point. If the status is “Accessible”, it shows that the status is normal.

MTP commissioning







SCCP commissioning

On the LMT client, run the TST SCCPGT command to check if the translation of SCCP GT is correct.

If not correct, run the LST SCCPGT command to check wheterh parameters are correctly configured.

Checking the status of the SS7 trunk circuit

On the LMT client, run the command DSP OFTK or DSP N7TKC to check if the status of the SS7 trunk circuit is normal.

If the status is abnormal, run commands such as LST TG and LST TKC to check if the following parameters are correctly configured: 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-27

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

IP

MTPM3UA

SCTP

ISUP

MSOFTX3000

UMG8900 (SG)

IP

M3UA

SCTPIP

MTP3

MTP2MTP1

ISUP

MTP3

MTP2MTP1

ISUP/M3UA

TMSC/GMSC

ISUP/MTP

Trunk

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

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:

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.

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.

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.

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


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





Observe the indicators on the WIFM. The green Ethernet port connection indicator, “LINK”, should be on, while the yellow Ethernet port data traffic indicator, “ACT”, should flash.


network connection On the LMT client, use the interface

tracing function “PING” to check the communication between the WIFM and UMG8900. If the ping command is executed successfully, it shows that the communication is normal.

In case of failure, check if the Ethernet cables are correctly connected, if the WIFM works normally, if devices connected with the WIFM (such as a LAN Switch) works normally, and if the UMG8900 works normally.

Check the status of gateway registration

On the LMT client, run the DSP MGW command to check the status of gateway registration. If the display is “Normal”, it shows that the UMG8900 registers successfully.


On the LMT client, run the DSP M3LNK command to check the statuses of relevant M3UA links. If they are “Active”, it shows that the links are normal.

On the LMT client, run the DSP M3LKS command to check the status of the M3UA link set. If they are “Active”, it shows that the links are normal.

On the LMT client, run the DSP 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, first run the LST M3LKS command to check if the transmission mode of the link set is correctly configured. Then, use the LST M3LNK command to check if the following parameters are correct: the local end port number, local end IP address, peer end port number, peer end IP address, and C/S work mode.

M3UA commissioning

On the LMT client, run the DSP M3RT command to check the statuses of relevant M3UA routes.

If the statuses are abnormal, use commands LST M3LE, LST M3DE and LST M3LKS to check if such parameters as the local entity index, destination entity index and link set index have correct relations.



5-30


Check the statuses of SS7 signaling trunk circuits

On the LMT client, run the DSP OFTK or N7TKC command to check the statuses of relevant SS7 signaling trunk circuits.

If the statuses are abnormal, use commands like LST TG and LST TKC to check if the following parameters are correct: the equipment ID, origination point code (OPC), destination point code (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-31

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

DSP M3LSLNK

To query the status of the M3UA link

“Active” shows the normal status.

DSP M3LKS To query the status of the M3UA link set


DSP M3DE To query the status of the M3UA destination entity

“Accessible” shows the normal status.

DSP M3RT To query the status of the M3UA route None

DSP M3VER To query the version information of M3UA None



5-32

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

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

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


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.

BICC

SCTP

MSOFTX3000

UMG8900

IP

BICC/SCTP

MSOFTX3000

UMG8900

Trunk (BICC)

IP

IP IP

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

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)








tracing function “PING” to check the communication between the WIFM and the peer MSC. If the ping command is executed successfully, it shows that the communication is normal.

In case of failure, check if the Ethernet cables are correctly connected, if the WIFM works normally, if devices connected with the WIFM (such as a router) works normally, if route data is correctly configured, and if the peer MSC works normally.



5-37



On the LMT client, run the DSP MGW command to check the status of gateway registration. If the display is “Normal”, it shows that the gateway registers successfully.


On the LMT client, run the DSP BSCTP command to check the statuses of relevant BICC SCTP links. If they are “Active”, it shows that the links are normal.

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 number, local end IP address, peer end port number, peer end IP address, and C/S work mode. If data configuration for the local office has no problem, check if data of the 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.

BICC commissioning

On the LMT client, run the command DSP BICCCIC or DSP BICCOFC to check the statuses of relevant BICC CICs.

If the statuses are abnormal, run the command LST BICCCICMDU to check if the parameters such as the office direction, module number, start CIC, 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-38





tracing function “PING” to check the communication between the WIFM and the peer MSC. If the ping command is executed successfully, it shows that the communication is normal.

In case of failure, check if the Ethernet cables are correctly connected, if the WIFM works normally, if the device connected with the WIFM (such as a router) works normally, if route data is correctly configured, and if the peer MSC works normally.

Check the work mode of the local office and the statuses of dual homing heartbeat links

If data has been configured for the peer MSC, run the command DSP DHSTA to check if the local office is in the mutual aid inactive state and if the two dual homing heartbeat links are normal.

If the status of a link is abnormal, use the LST DHHCFG command to check if the peer end IP address, local UDP port number, peer end UDP port number, and key are correctly configured.


On the LMT client, run the DSP MGW command to check the status of gateway registration. At this time, the local office should work in the mutual aid inactive state, gateways primarily homed to the local office should all be normal in registration, while gateways secondarily homed to the local office abnormal in registration.


On the LMT client, run the DSP BSCTP command to check the statuses of BICC SCTP links. At this time, the local office should work in the mutual aid inactive state, links primarily homed to the local office should all be normal, while gateways secondarily homed to the local office abnormal.

In case of abnormality, solve the problem by referring to “Steps of BICC Commissioning (Independent Work Mode)” in this chapter, and check if data configuration for the local office and peer MSC is correct. BICC

commissioning





5-39


Activate the local office

Power off the basic subrack of the peer MSC, and the local office will enter the mutual aid inactive state automatically. On the LMT client, run the DSP DHSTA command to check the work mode of the local office and the statuses of dual homing heartbeat links.

In case of abnormality, check if data has been correctly configured for the local office.

Check the status of gateway registration (mutual aid active state)

On the LMT client, run the DSP MGW command to check the status of gateway registration. At this time, the local office should work in the mutual aid active state, and gateways should all be normal in registration.


On the LMT client, run the DSP BSCTP command to check the statuses of BICC SCTP links. At this time, the local office should work in the mutual aid active state, and the links, except that to the peer MSC (powered off), should all be normal.

In case of abnormality, solve the problem by referring to “Steps of BICC Commissioning (Independent Work Mode)” in this chapter, and check if data configuration for the local office and peer MSC is correct.

BICC commissioning (mutual aid active state)



Deactivate the local office

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 peer MSC, and the local office will automatically enter the mutual aid inactive state when the basic subrack of the peer MSC works normally,

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.

Note: On the LMT client, run the DSP DHSTA command to check the work mode of the local office and the statuses of dual homing heartbeat links.



5-40

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

DSP BSCTPOFC To query the status of the BICC link


DSP BICCCIC

DSP BICCOFC

DSP BICCSTA

To query the status of BICC CIC None



5-41

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

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

M3UA

SCTP

SCCP

MSOFTX3000

UMG8900 (SG)

IP

M3UA

SCTPIP

RANAP/M3UA

RNC

RANAP

IP

ATM

MTP3BSAAL

ATM

SCCP

RANAP

RANAP/MTP3B

MTP3BSAAL

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


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








tracing function “PING” to check the communication between the WIFM and the UMG8900. If the ping command is executed successfully, it shows that the communication is normal.

In case of failure, check if the Ethernet cables are correctly connected, if the WIFM works normally, if devices connected with the WIFM (such as a LAN Switch) works normally, and if the UMG8900 works normally


On the LMT client, run the DSP MGW command to check the status of gateway registration. "Normal” shows that the UMG8900 has registered successfully.




5-45


On the LMT client, run the DSP M3LNK command to check the status of M3UA link. “Active” shows that the status is normal.

On the LMT client, run the DSP M3LKS command to check the status of the M3UA link set. “Active” shows that the status is normal.

On the LMT client, run the DSP M3DE command to check the status of the M3UA destination entity. “Accessible” shows that the status is normal.

If the status is abnormal, run the LST M3LKS command to check if the correct transmission mode has been configured for the link set. 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.

M3UA commissioning

On the LMT client, run the DSP M3RT command to check the statuses of relevant M3UA links.

If the statuses are abnormal, 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.

On the LMT client, run the DSP SCCPDSP command to check the statuses of remote SCCP signaling points. “Allow” shows that the status is normal.

If the statuses are abnormal, run the LST SCCPDSP command to check if such parameters as DPC and OPC are correctly configured.

SCCPcommissioning On the LMT client, run the DSP

SCCPSSN command to check the statuses of SCCP subsystems. “Allow” shows that the status is normal.

If the statuses are abnormal, run the LST SCCPSSN command to check if such parameters as DPC, OPC and subsystem code are correctly 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”.

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


6-1

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





2

Enable format conversion function, and get online

Open the MML window and execute the following commands: SET FMT: STS=ON; LON:;

The meanings of the commands: SET FMT: enable or disable format conversion function LON: get online

3

Execute the number analysis data script

4

Execute the mobile service data script

5

Execute the intelligent network service data script

Press shortcut keys <Ctrl + E> to open the [MML Batch] dialog box, and execute data script files in sequence. Upon completing every script, check the [Total Result] field in the lower part of the dialog box, to see if the MML commands are all executed successfully.

For detail on operations onto data script files, refer to “Method for Executing Data Script” in Chapter 3.



6-2


6 Perform CRC on board data

On the MML window, run the command STR CRC: MN=255; to perform CRC on the data of boards (modules) that can be loaded.

If the verification fails, reset the board and reload it. It will take quite a long time to execute the command STR CRC. If the system prompts timeout in executing the command, select [System/Command Timeout Setting...] on the LMT client to extend the time-out time.

6.3 Implementing Service Test

6.3.1 Preparations

Before carrying out service test, make the preparations below:

Make a dialing test plan and send copies of it to exchange offices involved; Configure test data of the local office according to the negotiation with relevant

offices; Configure service data for relevant offices; 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-3

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:

Basic service test Supplementary service test Intelligent service test Feature service test Data service test Mobility management test 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-4

System A

System B

System A

System B

Local office

Receive

Send

Send

Receive

Peer office

Send

Receive

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

System A

System B

System A

System B

Local office

Receive

Send

Receive

Send

Peer office

Send

Receive

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

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

I. Common Causes of CPU Overload

The common causes are

Too heavy traffic Too short traffic measurement task period Irrational location area Unregulated operation and maintenance Incorrect data configuration 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:

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.

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

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.5–3 times that of base station controller (BSC)/radio network controller (RNC). As a result, the A/Iu-CS interface link will be overloaded.

5) Split the location areas that are not correctly set.

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

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

Threshold Overload Level 1

Overload Level 2

Overload Level 3

Over-load Level 4

Resu-me Level 1

Resu-me Level 2

Resume Level 3

Resume Level 4

Default 80 85 90 95 75 80 85 90


Appendix A Commissioning Records of Newly-Built Office


A-1


A.1 Preparations for SM

Table A-1 Preparations for system commissioning (SM)

Item Result Remarks

The installation and checking of hardware are finished, and the equipment is powered on.

Y; N Check the construction condition The installation and checking of software

are finished. Y; N

Check technical documents

The complete technical documents for deployment are ready. Y; N

The numbers of servers and matching devices are correct. Y; N

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

The number of boards and board locations are correct. Y; N

Board versions are correct. Y; N

Check the hardware configuration

The subrack numbers of the WSIU boards are correctly set. Y; N

The status of the power distribution box is normal. Y; N

The statuses of subrack fans are normal. Y; N

The statuses of power boards of subracks are normal. Y; N

The power status of the server is normal. Y; N

Check the power supply

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




A-2

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

The BAM can log in after restarting, the SQL Server and services and processes are all in good condition.

Y; N

System customization has been fulfilled by using the SetWin2000 security customization tool.

Y; N

Check the software of BAM

SysPatron runs normally. Y; N


The SQL Server runs normally. Y; N

Check the software of the emergency workstation Services are in normal condition. Y; N

Check the software of the LMT


The version of software is correct. Y; N

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

All processes run normally. Y; N

It is possible to automatically log on to the active and standby iGWBs after they have been restarted. And processes run normally.

Y; N

Check iGWB software

It is possible to switch between the active and standby iGWB. And processes run normally.

Y; N

The IP addresses of the BAM and iGWB are correctly set. Y; N

The BAM can communicate normally with the foreground host. Y; N

The communication between the BAM and iGWB is normal. Y; N

The communication between the iGWB and the host is normal. Y; N

The configuration of the VLAN is correct. Y; N

Check the communication of the internal LAN

The Ethernet biplane switchover function is normal. Y; N




A-3

Item Result Remarks

The IP addresses of the BAM, LMT, iGWB and emergency workstation are correctly set.

Y; N

The BAM can normally communicate with the LMT. Y; N

The BAM can normally communicate with the emergency workstation. Y; N

Check the communication of the external LAN

The communication between the BAM and iGWB is normal. Y; N

The BAM can normally communicate with the NMC. Y; N Check the

communication of the WAN

The communication between the iGWB and the charging center is normal. Y; N

Make an empty backup of the BAM database

Make an empty backup of the BAM database using SQL Server Enterprise Manager before data configuration.

Y; N

A.2 Data Configuration

Table A-2 Data configuration

Item Result Remarks

Data collection and planning

Understand the networking mode, be clear of the equipment configuration, and collect external interface data, consult with the peer office about the data needing negotiation and service data, and fill out the data collection form.

Y; N

Make data script

Edit/modify data script files according to the situation on site. Y; N

Check data script Data script is correct. Y; N




A-4

A.3 Local Office Commissioning

Table A-3 Local office commissioning

Item Result Remarks

Execute data script offline Executing data script files offline succeeds. Y; N

Service processes of the BAM (especially the Exchange process) are normal. Y; N

The BAM can communicate normally with the foreground host. Y; N

Make preparations before loading boards

There are load source files under the directory D:\Data\ of the BAM. Y; N

Boards run normally. Y; N

Software versions of boards are correct. Y; N Load and check basic subracks Data verification for boards (modules) that can

be loaded is successful. Y; N


Software versions of boards are correct. Y; N

Data verification for boards (modules) that can be loaded is successful. Y; N

Load and check expansion subracks

All expansion subracks can be successfully loaded. Y; N

Clock cables are correctly connected. Y; N

The status of the clock phase-locked loop circuit of the WCKI is normal. Y; N Perform clock

commissioning

The clock statuses of the WEPIs are normal. Y; N

The statuses of the LAN Switch indicators are normal. Y; N

The statuses of the power distribution box indicators are normal. Y; N

Subrack fans run normally and the statuses of their indicators are normal. Y; N

The statuses of indicators on front boards are normal. Y; N

Check indicator statuses

The statuses of indicators on back boards are normal. Y; N




A-5

Item Result Remarks

The power distribution box runs normally. Y; N

Subrack fans run normally. Y; N


The statuses of Fast Ethernet (FE) ports are normal. Y; N

Check the running of hardware

The communication between the WIFM and the default gateway is normal. Y; N

Verify hardware switchover

The active/standby switchover for the front board is normal. Y; N

Perform self-loop test of E1 cables of the local office

The self-loop test of E1 cables of the local office is passed. Y; N

Modify the loading software switch of a board

After the successful loading of a board and when it runs normally, modify the settings of the loading software switch to “program available, data available, data writable, program not writable”.

Y; N

Set the time for the switch

The time of the switch is correctly set with an error less than ±30 seconds against the local standard time.

Y; N

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 MGW is normal. Y; N

The status of gateway registration is normal. Y; N Connect with the MGW

Statuses of H.248 links of Mc-interface are normal. Y; N




A-6

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

Statuses of MTP links, signaling points and routes are normal. Y; N

Statuses of SCCP remote signaling points and subsystems are normal. Y; N

Connect with BSC

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





Connect with HLR

Statuses of SCCP remote signaling points and subsystems are normal. GT translation is correct. Y; N





Connect with SMC






Connect with SCP





A-7

Item Result Remarks





Connect with SGSN








Connect with MSC through ISUP&MAP/MTP

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


The network connection between the WIFM and UMG8900 is normal. Y; N

The status of gateway registration is normal. Y; N

Statuses of M3UA links, link set, and route are normal. Y; N

Connect with the MSC using ISUP/M3UA

SS7 trunk circuits are in normal statuses. Y; N


The network connection between the WIFM and MSC is normal. Y; N


Statuses of BICC links are normal. Y; N

Connect with the MSC using BICC/SCTP (independent work mode)

BICC CIC statuses are normal. Y; N




A-8

Item Result Remarks


The network connection between the WIFM and MSC is normal. Y; N

The statuses of dual homing heartbeat links are normal. The local office is in the mutual aid inactive status

Y; N

The registration status of the gateway controlled by the local office is normal. Y; N

The statuses of BICC links controlled by the local office are normal. Y; N

BICC CIC statuses are normal. Y; N

The local office is activated successfully and is in the mutual aid active status. Y; N

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

Connect with the MSC using BICC/SCTP (mutual aid work mode)

Deactivating the local office succeeds. The local office is in the mutual aid inactive state. The status of dual homing heartbeat link is normal.

Y; N


The connection between the WIFM and UMG8900 is normal. Y; N


The statuses of M3UA links, link set, destination entity and route are normal. Y; N

Connect with RNC

The statuses of SCCP remote signaling points and subsystems are normal. Y; N

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

Item Result Note

Mobility management test Y; N

CDR function test Y; N

Installation Manual – System Commissioning HUAWEI MSOFTX3000 Mobile SoftSwitch Center Index


i-1

Index

B BICC

introduction, 5-35

locating problems, 5-40

treating common problems, 5-41

board loading

checking whether loading is successful, 4-8

description of software switches, 4-1

description of source files, 4-2

description of switches of power distribution

subrack, 4-6

for newly-built office, 4-2

handling of loading problems, 4-9

introduction, 4-1

method of loading, 4-1

operation steps, 4-5

preparations, 4-4

BSSAP/MTP

protocol stack, 5-7

BSSAP+/MTP

protocol stack, 5-20

C CAP/MTP


clock commissioning

checking clock cable connection, 4-12

description of clock system networking, 4-10

MSOFTX3000 locking BITS clocks, 4-10

MSOFTX3000 locking peer office clocks, 4-11

steps for locking BITS clocks, 4-14

steps for locking peer office clocks, 4-14

connecting with BSC

locating MTP problems, 5-10

locating SCCP/TCAP problems, 5-14

protocol stack, 5-7

steps of commissioning, 5-8

connecting with HLR



connecting with MGW

H.248/SCTP commissioning, 5-3

interaction between MSOFTX3000 and MGW,

5-2

locating H.248/SCTP problems, 5-4

protocol stack, 5-1

step of commissioning, 5-2

treating SCTP common problems, 5-6

connecting with MSC

protocol stack (BICC/SCTP), 5-35

protocol stack (ISUP&MAP/MTP), 5-23

protocol stack (ISUP/M3UA), 5-27

steps of commissioning (BICC/SCTP), 5-36

steps of commissioning (ISUP&MAP/MTP),

5-24

steps of commissioning (ISUP/M3UA), 5-29

through BICC/SCTP, 5-35

through ISUP&MAP/MTP, 5-23

through ISUP/M3UA, 5-27

connecting with RNC



connecting with SCP



connecting with SGSN



connecting with SMC



D data collection and planning, 3-2

data configuration



i-2

method for executing data script, 3-2

mode, 3-1

sequence, 3-1

data script

editing and checking, 3-2

method for executing, 3-2

dual homing

basic concept, 5-36

H H.248/SCTP

commissioning, 5-3


protocol stack, 5-1

hardware commissioning

checking indicator status, 4-15

checking the running of hardware, 4-17

hardware switchover verification, 4-18

self-loop test for local office E1 cables, 4-19

I interconnection commissioning

connecting with BSC, 5-7

connecting with HLR, 5-19

connecting with MGW, 5-1

connecting with MSC through BICC/SCTP, 5-35

connecting with MSC through ISUP&MAP/MTP,

5-23

connecting with MSC through ISUP/M3UA, 5-27

connecting with RNC, 5-42

connecting with SCP, 5-19

connecting with SGSN, 5-19

connecting with SMC, 5-19

IP address

BAM, 2-11

emergency workstation, 2-12

iGWB, 2-13

LMT, 2-12

WSMU, 2-12

L local office commissioning

board loading, 4-4

clock commissioning, 4-10

configure data offline, 4-3

description of related concepts, 4-1

hardware commissioning, 4-15

modifying settings of loading software switch,

4-19

prepare for loading, 4-3

setting time for MSOFTX3000, 4-20

M M3UA



MAP/MTP


MTP


O O&M system

checking communication, 2-10

checking communication of external LAN, 2-16

checking communication of internal LAN, 2-14

checking communication of WAN, 2-17

description, 2-10

IP address of BAM, 2-11

IP address of emergency workstation, 2-12

IP address of iGWB, 2-13

IP address of LMT, 2-12

IP address of WSMU, 2-12

method for checking communication, 2-14

P preparations for system commissioning

checking communication of O&M system, 2-10

checking construction conditions, 2-1

checking hardware configuration, 2-3

checking power supply, 2-4

checking software, 2-5

checking technical documents, 2-2

making a backup of BAM database, 2-18



i-3

protocol stack

BICC/SCTP, 5-35

BSSAP/MTP, 5-7

BSSAP+/MTP, 5-20

CAP/MTP, 5-20

H.248/SCTP, 5-1

ISUP&MAP/MTP, 5-23

ISUP/M3UA, 5-27

MAP/MTP, 5-19

RANAP/M3UA, 5-42

R RANAP/M3UA


S SCCP


SCTP


service commissioning

handling common problems, 6-3

handling of BICC call problems, 6-5

handling of call abnormality, 6-3

handling of CPU overload, 6-6

implementing service test, 6-2

system commissioning

commissioning records of newly-built office, A-1

conditions, 1-1

data configuration, 3-1

definition, 1-1

flow, 1-1

interconnection commissioning, 5-1

local office commissioning, 4-1

preparations, 2-1

service commissioning, 6-1

T TCAP


i.