hlr9820-configuration guide(v900r003c02 04,db2)

5/25/2018 HLR9820-Configuration Guide(V900R003C02 04,Db2)

1/105

HUAWEI HLR9820 Home Location Register

V900R003C02

Configuration Guide

Issue 04

Date 2009-01-15

Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.


2/105

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any

assistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Copyright Huawei Technologies Co., Ltd. 2009. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written

consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but the statements, information, and

recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Proprietary and Confidential

http://www.huawei.com/


3/105

Contents

About This Document.....................................................................................................................1

1 Overview of Data Configuration............................................................................................1-1

1.1 Data Configuration Process.............................................................................................................................1-2

1.2 Introduction to MML Commands...................................................................................................................1-21.2.1 Meanings of Common MML Commands..............................................................................................1-2

1.2.2 Rules for Setting MML Command Parameters......................................................................................1-3

1.2.3 DataSetting Procedures.........................................................................................................................1-4

1.3 Precautions for Data Configuration.................................................................................................................1-6

1.3.1 Impact of the Maximum Number of Tuples on Data Configuration......................................................1-6

1.3.2 Impact of Value Ranges of Software Parameters on Data Configuration..............................................1-7

1.3.3 Impact of Software Parameters on Data Configuration.........................................................................1-8

1.3.4 Impact of Board Restarting on Data Configuration...............................................................................1-8

2 Hardware Data Configuration.................................................................................................2-12.1 Basic Concepts................................................................................................................................................2-2

2.1.1 Rack Number..........................................................................................................................................2-2

2.1.2 Subrack Number.....................................................................................................................................2-2

2.1.3 Slot Number...........................................................................................................................................2-4

2.1.4 ModuleNumber.............................................................................................. .......................................2-6

2.1.5 Cluster....................................................................................................................................................2-6

2.1.6 Node.......................................................................................................................................................2-6

2.2 Data Configuration Flow Chart.......................................................................................................................2-7

2.3 Hardware Data Table Relation........................................................................................................................2-92.4 Data Configuration Procedure.......................................................................................................................2-11

2.4.1 Adding a Rack......................................................................................................................................2-12

2.4.2 Adding an OSTA 1.0 Subrack..............................................................................................................2-12

2.4.3 Setting the OSTA 1.0 Board Type.......................................................................................................2-12

2.4.4 Adding an OSTA 1.0 Board.................................................................................................................2-12

2.4.5 Configuring the Hardware Data in TDM Networking.........................................................................2-12

2.4.6 Configuring the Hardware Data in IP Networking..............................................................................2-13

2.4.7 Configuring the Hardware Data in ATM-2M Networking..................................................................2-13

2.4.8 Adding an OSTA 2.0 Subrack..............................................................................................................2-13

2.4.9 Adding an OSTA 2.0 Board.................................................................................................................2-13


Configuration Guide Contents

Issue 04 (2009-01-15) Huawei Proprietary and Confidential


i


4/105

2.4.10 Setting the Local Office Information.................................................................................................2-13

2.4.11 Adding the Cluster Configuration......................................................................................................2-13

2.4.12 Adding the Node Configuration.........................................................................................................2-14

2.4.13 Setting the HDU Configuration..........................................................................................................2-14

2.4.14 Adding the Remote Node Configuration...........................................................................................2-14

2.4.15 Addingthe MEM Configuration........................................................................................................2-14

2.4.16 Generating SAU Data Loading Files.................................................................................................2-14

2.4.17 Synchronizing the HDU Configuration..............................................................................................2-14

2.5 Data Configuration Examples.......................................................................................................................2-15

2.5.1 Data Configuration in TDM Networking.............................................................................................2-15

2.5.2 Data Configuration in ATM-2M Networking......................................................................................2-19

2.5.3 DataConfiguration in IP Networking..................................................................................................2-23

3 Local Office Data Configuration.............................................................................................3-1

3.1 Basic Concepts................................................................................................................................................3-2

3.1.1 Local Office Information.......................................................................................................................3-2

3.1.2 Called Prefix...........................................................................................................................................3-2

3.1.3 SPC.........................................................................................................................................................3-2

3.2 Data Configuration Procedure.........................................................................................................................3-2

3.3 Data Configuration Example...........................................................................................................................3-4

3.3.1 Description.............................................................................................................................................3-5

3.3.2 Example..................................................................................................................................................3-5

4 Signaling Data Configuration................................................................................................. 4-1

4.1 Basic Concepts................................................................................................................................................4-2

4.1.1 MTP-Specific Concepts.........................................................................................................................4-2

4.1.2 MTP3B-Specific Concepts...................................................................................................................4-10

4.1.3 SIGTRAN-Specific Concepts..............................................................................................................4-13

4.1.4 SCCP-Specific Concepts......................................................................................................................4-16

4.1.5 Signaling Data Configuration Principles..............................................................................................4-21

4.2 Data Configuration Procedures.....................................................................................................................4-21

4.2.1 DataConfiguration Procedure in TDM Networking............................................................................4-21

4.2.2 Data Configuration Procedure in ATM-2M Networking.....................................................................4-22

4.2.3 Data Configuration Procedure in IP Networking.................................................................................4-23

4.3 MTP Data Configuration Procedure.............................................................................................................4-24

4.4 MTP3B Data Configuration Procedure.........................................................................................................4-26

4.5 M3UA Data Configuration Procedure..........................................................................................................4-27

4.6 SCCP Data Configuration Procedure............................................................................................................4-28

4.6.1 SCCP Data Configuration Principles...................................................................................................4-28

4.6.2 SCCP Data Table Relation...................................................................................................................4-28

4.7 Data Configuration Examples.......................................................................................................................4-29

4.7.1 Data Configuration in TDM Networking.............................................................................................4-30

4.7.2 Data Configuration in ATM-2M Networking......................................................................................4-32

4.7.3 Data Configuration in IP Networking..................................................................................................4-33

Contents


Configuration Guide

ii Huawei Proprietary and Confidential


Issue 04 (2009-01-15)


5/105

A Abbreviations...........................................................................................................................A-1

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


Configuration Guide Contents



iii


6/105


7/105

Figures

Figure 1-1Data configuration process.................................................................................................................1-2

Figure 1-2MML command input window...........................................................................................................1-4

Figure 2-1Data configuration flow chart.............................................................................................................2-8

Figure 2-2OSTA 1.0 hardware data table relation............................................................................................2-10

Figure 2-3OSTA 2.0 hardware data table relation............................................................................................2-11

Figure 2-4Board configuration of the OSTA 1.0 subrack ................................................................................2-16

Figure 2-5Board configuration of the OSTA 2.0 subrack ................................................................................2-16

Figure 2-6Board configuration of the OSTA 1.0 subrack.................................................................................2-19




Figure 4-1Structure of the MTP protocol stack...................................................................................................4-2

Figure 4-2Configuration of the DSPs..................................................................................................................4-4

Figure 4-3Associated mode........................................................................................................... ......................4-4

Figure 4-4Quasi-Associated mode......................................................................................................................4-5

Figure 4-5Inter-SP communication through the STP..........................................................................................4-5

Figure 4-6Direct route and alternative route.......................................................................................................4-7

Figure 4-7Load sharing in one link set................................................................................................................4-7

Figure 4-8Load sharing among different link sets..............................................................................................4-7

Figure 4-9Routing of signaling services.............................................................................................................4-9

Figure 4-10Broadband MTP structure..............................................................................................................4-10

Figure 4-11Configuration of the DSPs..............................................................................................................4-12

Figure 4-12Model of the SIGTRAN protocol stack..........................................................................................4-14Figure 4-13Inter-SP communication through the STP......................................................................................4-20

Figure 4-14DPC + GT addressing.....................................................................................................................4-20

Figure 4-15Procedure for configuring the signaling data in TDM networking................................................4-22

Figure 4-16Procedure for configuring the signaling data in ATM-2M networking.........................................4-23

Figure 4-17Procedure for configuring the signaling data in IP networking......................................................4-24

Figure 4-18MTP data table relation..................................................................................................................4-25

Figure 4-19MTP3B data table relation..............................................................................................................4-26

Figure 4-20M3UA data table relation...............................................................................................................4-27

Figure 4-21SCCP data table relation.................................................................................................................4-29

Figure 4-22Signaling networking......................................................................................................................4-30


Configuration Guide Figures



v


8/105



Figures


Configuration Guide

vi Huawei Proprietary and Confidential


Issue 04 (2009-01-15)


9/105

Tables

Table 1-1Frequently used MML commands.......................................................................................................1-3

Table 1-2Procedure for setting the SAU data online...........................................................................................1-5

Table 1-3Procedure for setting the HDU data online..........................................................................................1-5

Table 1-4Procedure for setting the SAU data offline..........................................................................................1-5

Table 1-5Procedure for setting the HDU data offline.........................................................................................1-6

Table 2-1Relation between the subrack numbers and the settings of S3............................................................2-3

Table 2-2Relation between the subrack numbers and the settings of the DIP switch.........................................2-3

Table 2-3Procedure for generating a .dat file....................................................................................................2-14

Table 2-4Procedure for synchronizing the HDU configuration........................................................................2-15

Table 3-1Data configuration procedure...............................................................................................................3-3

Table 3-2Data configuration of the local office..................................................................................................3-5

Table 4-1Mapping between the number of the links/link sets and the number of 1s in the mask.............. ........4-8

Table 4-2Example of the selection of link set and link by SLS..........................................................................4-9

Table 4-3Number assignment for the subsystems related to the HLR..............................................................4-17

Table 4-4GTindicator.......................................................................................................................................4-17

Table 4-5GTcomponents..................................................................................................................................4-19

Table 4-6Mapping between the translation result and the routing indicator.....................................................4-19

Table 4-7Procedure for configuring the MTP data...........................................................................................4-24

Table 4-8Procedure for configuring the MTP3B data.......................................................................................4-26

Table 4-9Procedure for configuring the M3UA data........................................................................................4-27

Table 4-10Procedure for configuring the SCCP data........................................................................................4-29


Configuration Guide Tables



vii


10/105


11/105

About This Document

Purpose

This section describes the related versions, intended audience, organization, conventions, and

update history of the Configuration Guideof the HLR9820.

Related Versions

The following table lists the product versions related to this document.

Product Name Version

HLR9820 V900R003C02

Intended Audience

The intended audiences of this document are:

l Technical support engineers

l Maintenance engineers

Organization

The Configuration Guidedescribes the data configuration of the HLR9820.

Chapter Description

1 Overview of Data

Configuration

This chapter describes the configuration process of the

HLR9820, MML commands, and precautions of the data

configuration.

2 Hardware Data

Configuration

This chapter describes how to configure the hardware data

of the HLR9820.


Configuration Guide About This Document



1


12/105

Chapter Description

3 Local Office Data

Configuration

This chapter describes how to configure the local site data

and system resource data of the HLR9820.

4 Signaling Data

Configuration

This chapter describes how to configure the TDMsignaling data, ATM-2M signaling data, and IP signaling

data of the HLR9820.

A Abbreviations This appendix lists all acronyms and abbreviations used

in this manual.

Conventions

Symbol Conventions

The symbols that may be found in this document are defined as follows.

Symbol Description

DANGER

Indicates a hazard with a high level of risk, which if not

avoided, will result in death or serious injury.

WARNING

Indicates a hazard with a medium or low level of risk, which

if not avoided, could result in minor or moderate injury.

CAUTION

Indicates a potentially hazardous situation, which if not

avoided, could result in equipment damage, data loss,

performance degradation, or unexpected results.

TIP Indicates a tip that may help you solve a problem or save

time.

NOTE Provides additional information to emphasize or supplement

important points of the main text.

General ConventionsThe general conventions that may be found in this document are defined as follows.

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.

Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are in

Courier New.

About This Document


Configuration Guide

2 Huawei Proprietary and Confidential


Issue 04 (2009-01-15)


13/105

Command Conventions

The command conventions that may be found in this document are defined as follows.

Convention DescriptionBoldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[ ] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.

{ x | y | ... }* Optional items are grouped in braces and separated byvertical bars. A minimum of one item or a maximum of all

items can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.

GUI Conventions

The GUI conventions that may be found in this document are defined as follows.

Convention Description

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.

> Multi-level menus are in boldfaceand separated by the ">"

signs. For example, choose File > Create> Folder.

Keyboard Operations

The keyboard operations that may be found in this document are defined as follows.

Format Description

Key Press the key. For example, press Enterand press Tab.

Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt

+Ameans the three keys should be pressed concurrently.

Key 1, Key 2 Press the keys in turn. For example, pressing Alt, Ameans

the two keys should be pressed in turn.

Mouse Operations

The mouse operations that may be found in this document are defined as follows.


Configuration Guide About This Document



3


14/105

Action Description

Click Select and release the primary mouse button without moving

the pointer.

Double-click Press the primary mouse button twice continuously andquickly without moving the pointer.

Drag Press and hold the primary mouse button and move the

pointer to a certain position.

Update History

Updates between document versions are cumulative. Therefore, the latest document version

contains all updates made to previous versions.

Updates in Issue 04 (2009-01-15)

Third commercial release. The updated contents are as follows:

Version information updated only.


Second commercial release. The updated contents are as follows:

The description of the 750C boards is added.


Initial commercial release. The updated contents are as follows:

2.5.1 Data Configuration in the TDM Networking

The reference to the IP address planning for the modules such as the SMU and HDU is modified.

The description of the ETU is added to the document.


Initial field trial release

About This Document


Configuration Guide

4 Huawei Proprietary and Confidential


Issue 04 (2009-01-15)


15/105

1Overview of Data ConfigurationAbout This Chapter

1.1 Data Configuration Process

1.2 Introduction to MML Commands

1.3 Precautions for Data Configuration


Configuration Guide 1 Overview of Data Configuration



1-1


16/105

1.1 Data Configuration Process

Figure 1-1shows the data configuration process of the HLR9820.

Figure 1-1Data configuration process

Start

Configure hardware data

Configure office data

Configure signaling data

End

1.2 Introduction to MML Commands

1.2.1 Meanings of Common MML Commands

1.2.2 Rules for Setting MML Command Parameters

1.2.3 Data Setting Procedures

1.2.1 Meanings of Common MML Commands

Generally, database operations are implemented using Human-Machine Language (MML)commands.

The MML commands are in the action + objectformat. For example, the ADD BRDcommand

consists of the action ADDand the object BRD. The action ADDindicates that a data record

will be added to the BAM database, and the object BRDindicates that the data record will be

added to the board data table.

The MML commands can be classified into two types, namely, configuration commands and

maintenance commands. The configuration commands apply to the BAM and SMU database.

The maintenance commands apply to the equipment, signaling links, and system resources.

Table 1-1lists the frequently used MML commands. The part from ADD to LST describes the

configuration commands. The part from ACT to SWP describes the maintenance commands.

1 Overview of Data Configuration


Configuration Guide

1-2 Huawei Proprietary and Confidential


Issue 04 (2009-01-15)


17/105

Table 1-1Frequently used MML commands

Command Description

ADD Adds a data record to the database.

RMV Removes an existing record from the database.

Note that the RMVcommand can remove only the data records added to the

database using the ADDcommand.

MOD Modifies certain fields of a data record in the database.

Note that the MODcommand can modify only the data records added to the

database using the ADDor SETcommand.

LST Lists the details of one or more records in the database.

ACT Activates a signaling link or service.

BLK Blocks a signaling link.

BKP Backs up the database or the configured data.

DEA Deactivates a signaling link or service.

DSP Displays the status of the specified equipment or signaling link, or the usage

of system resources.

RST Resets the specified equipment or signaling link or clears the system

resources.

SND Sends a message to the peer equipment.

SWP Switches over the active and the standby boards.

After the switchover, the active board changes to standby and the standby

board changes to active. This command is applicable to the active board only.

1.2.2 Rules for Setting MML Command Parameters

The HLR9820 provides a user-friendly Graphic User Interface (GUI). Through the GUI, you

can conveniently set the MML command parameters.

Figure 1-2shows the MML command input window of the HLR9820.





1-3


18/105

Figure 1-2MML command input window

When configuring data, pay attention to the following points:

l The parameters in red are the key parameters, for example, Shelf number, Position

number, Row number, and Column number, as shown in Figure 1-2. The parameters

of this type are mandatory. If these parameters are not specified, running the command

fails.

l The parameters in black are generally ordinary parameters, for example, Location title, as

shown in Figure 1-2. The parameters of this type are optional. They do not affect the

running of the command.

l Certain stable parameters are set with default values, for example, PDB location, as shownin Figure 1-2. This helps simplify the configuration. You can modify the values of the

parameters of this type as required.

l If you do not know the default value or value range of a certain parameter, you can place

the cursor over the input box of the parameter for about one second. The default value and

the value range are displayed, for example, PDB location, as shown in Figure 1-2.

1.2.3 Data Setting Procedures

Data setting refers to the process in which the operator configures the data in the database by

using MML commands during deployment, expansion, or maintenance. The HLR9820 supports

two types of data settings, namely, online setting and offline setting.

NOTE

The types of data settings are not distinguished when the configuration is performed through the SMU

client. The types of data settings are distinguished only when the configuration is performed through the

Local Maintenance Terminal (LMT).

l Online setting

Online setting refers to the procedure for refreshing the data in the BAM database, SAU,

or HDU by running MML commands on the LMT. It is mainly used for setting the data in

the BAM database during routine maintenance. The data volume involved is generally

small.

Table 1-2lists the steps of setting the SAU data online.



Configuration Guide



Issue 04 (2009-01-15)


19/105

Table 1-2Procedure for setting the SAU data online

Step Description Command

1 Enable the format conversion

switch.

SET FMT: STS=ON;

2 Switch to the online mode. LON:;

3 Run the data configuration

command (example).

ADD N7LNK: MN=22, LNKN=0,

LNKNAME="TO MSC", LNKTYPE=1,

TS=1, LSX=0, SLC=0, SLCS=0;

4

Table 1-3lists the steps of setting the HDU data online.

Table 1-3Procedure for setting the HDU data online


1 Enable the HDU configuration

switch.

SET CFGSWITCH: SW=ON;


command (example).

ADD MEMCFG: MN=22,

LIP1="172.16.200.22",

LIP2="172.17.200.22",

MSK="255.255.0.0";

3

l Offline setting

Offline setting refers to the procedure for refreshing only the data in the BAM database by

running MML commands on the LMT. During deployment or expansion, the data volume

involved is great because a large number of MML commands are run. In such a

circumstance, offline setting is recommended to improve the efficiency.

Table 1-4lists the steps of setting the SAU data offline.

Table 1-4Procedure for setting the SAU data offline


1 Switch to the offline mode. LOF:;

2 Disable the format conversion

switch.

SET FMT: STS=OFF;


command (example).

ADD SHF: SHN=0, LT="HLR", PN=0,

RN=0, CN=0;

4

5 Enable the format conversion

switch.

SET FMT: STS=ON;

6 Format all the data. FMT:;





1-5
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


20/105


7 Switch to the online mode. LON:;

8 Reset the board or the subrack

to reload the data.

-

Table 1-5lists the steps of setting the HDU data offline.

Table 1-5Procedure for setting the HDU data offline


1 Disable the HDU

configuration switch.

SET CFGSWITCH: SW=OFF;

2 Run the data configurationcommand (example).

ADD MEMCFG: MN=22,LIP1="172.16.200.22",

LIP2="172.17.200.22",

MSK="255.255.0.0";

3

4 Synchronize the HDU

configuration.

SYN HDUCFG: MN=250;

5 Enable the HDU configuration

switch.


1.3 Precautions for Data Configuration

1.3.1 Impact of the Maximum Number of Tuples on Data Configuration

1.3.2 Impact of Value Ranges of Software Parameters on Data Configuration

1.3.3 Impact of Software Parameters on Data Configuration

1.3.4 Impact of Board Restarting on Data Configuration

1.3.1 Impact of the Maximum Number of Tuples on DataConfiguration

Since the memory capacity and the CPU processing capability are limited, the system must

consider the memory space required for the software and the databases of various SAU boards

when allocating space for the memory zones of the boards. Thus, the system will not allocate

excessive storage space for the databases operating in the memory zones of the SAU boards,

that is, the system must restrict the maximum number of tuples stored in various data tables in

the database.

The HLR9820 manages the maximum number of tuples based on modules, including the

WSMU, WCCU, and WBSG. For the WCCU and the WBSG, the maximum number of tuplesconsists of two parts:



Configuration Guide



Issue 04 (2009-01-15)
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


21/105

l Maximum number of tuples of the special table: The maximum number of tuples of a certain

special table need not be the same for all the modules of the same type.

l Maximum number of tuples of the public table: The maximum number of tuples of the

public table must be the same for all the modules of the same type. If the system detects

that the maximum number of tuples stored in a certain public table is inconsistent amongmodules, an error occurs when the system formats all the data.

You can use the LST MAXTcommand to query the maximum number of tuples. If you specify

a module number, the system displays the maximum number of tuples of the special table in the

module. If you do not specify a module number, the system displays the maximum number of

tuples of the public table in the module.

Generally, avoid modifying the maximum number of tuples for the databases of the SAU boards.

If you modify the maximum number of tuples, the storage capability of other key data will be

affected. In addition, the database query efficiency will be reduced because the size of the

database is overlarge or even the reliability of the system will be degraded because the size of

the database exceeds the system design capability.

If it is necessary to modify the maximum number of tuples of the database, contact Huawei

technical support engineers.

1.3.2 Impact of Value Ranges of Software Parameters on DataConfiguration

To facilitate management and control, a theoretical value range is defined for each numerical

parameter during data configuration. Generally, if the field mapping a parameter is not the key

field, the system allows you to configure data as long as the value you set for the parameter is

within the theoretical value range.

Take the ADD M3LNKcommand forexample. When the ADD M3LNKcommand is run to

add an M3UA link, since Local portand Peer portare not the key fields used by the database

to sort and retrieve the data tables of the M3UA links, the actual values of Local portand Peer

portare restricted by their theoretical value ranges, respectively.

If the field mapping a parameter is the primary or secondary key field used by the database of

the SAU board to sort and retrieve the related data tables, the value you set for the parameter is

restricted by both the theoretical value range and the maximum number of tuples of the table

where the parameter exists. There are two cases as follows:

l Primary key field

If the field mapping a parameter (must be numbered globally) is the primary key field usedby the database to sort and retrieve the data records in a certain table, to improve the

efficiency, the system allocates the storage space for the data table in the database based

on the maximum index number of the parameter. In other words, the actual value of the

maximum index number of the parameter is equal to the maximum number of tuples of the

table. This can be verified through simple conversion.

For example, in the M3UA Link Settable configured by the ADD M3LKScommand,

Link set index(must be numbered globally) is the primary key field used by the database

to sort and retrieve data records in the M3UA Link Settable. Assume that the theoretical

value range of Link set indexis 0 - M and the maximum number of tuples of the M3UA

Link Settable is N for the ADD M3LKScommand. If the theoretical value range is not

considered, the actual value range of Link set indexis 0 - (N-1). Otherwise, the actualvalue range is the intersection of 0 - M and 0 - (N-1).





1-7
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


22/105

When you configure the M3UA link set using the ADD M3LKScommand, the actual value

range of Link set indexis 0 - 127 but not 0 - 65534 if M is 65534 and N is 128. If you set

the parameter to a value that is greater than 128, an error occurs.

l Secondary key field

If the field mapping a parameter (need not be numbered globally) is the secondary key fieldused by the database to sort and retrieve the data records in a certain table, the maximum

number of tuples limits only the maximum number of data records that can be configured.

In this case, the actual value range of the parameter is also restricted by its theoretical value

range.

For example, in the M3UA Linktable configured by the ADD M3LNKcommand, Module

number(must be numbered globally) is the primary key field and Link number(need be

numbered in the module only) is the secondary key field for the host database to sort and

retrieve data of the M3UA Linktable. Assume that the theoretical value range of Link

numberis 0 - M and the maximum number of tuples of the M3UA Linktable is N for the

ADD M3LNKcommand. The actual value range of Link numberis still 0 - M.

When you configure the M3UA link using the ADD M3LNKcommand, the actual valuerange of Link numberis 0 - 63 if M is 63 and N is 32. For a certain WBSG module, the

actual value range of Link numberis 0 - 63 but the total number of M3UA links, however,

cannot exceed 32. An error occurs when you add more than 32 M3UA links.

1.3.3 Impact of Software Parameters on Data Configuration

Software parameters are designed to solve specific problems. Each bit of a software parameter

has a unique meaning. Generally, you can directly use the default values. If you need to modify

a software parameter, contact Huawei technical support engineers.

1.3.4 Impact of Board Restarting on Data Configuration

If the SAU and the BAM of the HLR9820 are normal when you configure the databases of the

SAU boards on the LMT in online mode, the system can ensure data consistency between the

databases of the SAU boards and the database of the BAM.

In certain cases, for example, troubleshooting, software upgrade, or system expansion, you may

need to switch over or reset a board. At this point, the board loads programs and data from the

BAM again. This process is called board restarting.

The operation of the board is unstable during restarting. To be specific, the communication

between the board and the BAM is unstable; the communication between the board and other

boards is unstable; the board cannot respond to maintenance commands in time. At this point,do not carry out operations that may change the database data on the LMT. Otherwise, the

database data between the SAU board and the BAM may be inconsistent. This affects the security

and stability of the system.

After switching over or resetting a board, you must run the DSP BRDcommand to check the

operating status of the board and run the STR CRCcommand to check the data consistency.

You should configure data on the LMT only when the board is normal.



Configuration Guide



Issue 04 (2009-01-15)
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


23/105

2Hardware Data ConfigurationAbout This Chapter

Hardware data is the basic data of the HLR9820. The purpose of hardware data configuration

is to define the hardware of the HLR9820 and the related information. Hardware data

configuration is the basis for the configuration of other data.

2.1 Basic Concepts

2.2 Data Configuration Flow Chart

2.3 Hardware Data Table Relation

2.4 Data Configuration Procedure

2.5 Data Configuration Examples


Configuration Guide 2 Hardware Data Configuration



2-1


24/105

2.1 Basic Concepts

2.1.1 Rack Number

2.1.2 Subrack Number

2.1.3 Slot Number

2.1.4 Module Number

2.1.5 Cluster

2.1.6 Node

2.1.1 Rack Number

Each rack is allocated a number, which is called the rack number. The HLR9820 can be

configured with a maximum of six racks. The rack number ranges from 0 to 5.

Based on the internal components, the cabinets are classified into the integrated cabinet and the

extended cabinet.

l The integrated cabinet, also called the basic cabinet, houses the components such as the

power distribution box (PDB), OSTA 1.0 subrack, OSTA 2.0 subrack, LAN switch

(optional) and disk array. The integrated cabinet is mandatory and perpetually numbered

0.

l The extended cabinets are optional. They are numbered from 1 to 5 sequentially.

You can add a rack by running the ADD SHFcommand.

2.1.2 Subrack Number

Each subrack is allocated a number, which is called the subrack number.

Numbering of OSTA 1.0 Subracks

The HLR9820 can be configured with a maximum of 10 OSTA 1.0 subracks. The subracknumber ranges from 0 to 9. The basic subrack is perpetually numbered 0. The subracks are

numbered according to the following rules:

l The subracks in a cabinet are numbered in ascending sequence from the top to the bottom

of the cabinet.

l The subracks in multiple subracks are numbered in ascending sequence based on the cabinet

number.

You can set the subrack number through the DIP switch S3 (which comprises eight sub-switches)

on the Wireless System Interface Unit (WSIU). Table 2-1presents the relation between the

subrack numbers and the settings of S3.

2 Hardware Data Configuration


Configuration Guide



Issue 04 (2009-01-15)


25/105

Table 2-1Relation between the subrack numbers and the settings of S3

SubrackNumber

Sub-switch

1 2 3 4 5 6 7 8

0 on on on on on on on on

1 off on on on on on on on

2 on off on on on on on on

3 off off on on on on on on

4 on on off on on on on on

5 off on off on on on on on

6 on off off on on on on on

7 off off off on on on on on

8 on on on off on on on on

9 off on on off on on on on

The On position (at the lower side) denotes 0, and the Off position (at the upper side) denotes

1.

NOTE

l The OSTA 1.0 subrack housing the WCKI is the basic subrack.

l You can add an OSTA 1.0 subrack by running the ADD FRMcommand.

Numbering of OSTA 2.0 Subracks

The HLR9820 can be configured with a maximum of 16 OSTA 2.0 subracks. The subrack

number ranges from 30 to 45. The basic subrack is perpetually numbered 30.The subracks are

numbered according to the following rules:

l The subracks in a cabinet are numbered in ascending sequence from the bottom to the top

of the cabinet.

l The subracks in multiple subracks are numbered in ascending sequence based on the cabinet

number.

You can set the subrack number through the DIP switch on the Subrack Data Module (SDM).

Table 2-2presents the relation between the subrack numbers and the settings of the DIP switch.

Table 2-2Relation between the subrack numbers and the settings of the DIP switch

SubrackNumber

Sub-switch

1 2 3 4 5 6 7 8

30 Off Off Off On On On On Off

31 Off Off Off On On On On On





2-3
http://-/?-


26/105

SubrackNumber

Sub-switch

1 2 3 4 5 6 7 8

32 Off Off On Off Off Off Off Off

33 Off Off On Off Off Off Off On

34 Off Off On Off Off Off On Off

35 Off Off On Off Off Off On On

36 Off Off On Off Off On Off Off

37 Off Off On Off Off On Off On

38 Off Off On Off Off On On Off

39 Off Off On Off Off On On On

... ...

45 Off Off On Off On On Off On

The DIP switch on the SDM and the DIP switch on the WSIU indicate different values. The On

position (at the lower side) denotes 1, and the Off position (at the upper side, refer to Setting

the OSTA 2.0 Subrack Numbers) denotes 0.

NOTE

l The OSTA 2.0 subrack housing the INU is the basic subrack.

l For details on the SDM, refer to theHardware Description.

l You can add an OSTA 2.0 subrack by running the ADD SFRMcommand.

2.1.3 Slot Number

Different types of boards are configured in the slots of a subrack based on the functions to be

implemented. Each slot is allocated a slot number.

Rules for Configuring the OSTA 1.0 Boards

An OSTA 1.0 subrack has a maximum of 21 slots numbered from 0 to 20. The OSTA 1.0 subrack

is configured with the following boards:

l The WSMUs are permanently configured in front slots 6 and 8, and the Wireless System

Interface Units (WSIUs) are configured in the rear slots.

l The Wireless Hot-Swap and Control Units (WHSCs) are configured in rear slots 7 and 9,

whereas the front slots 7 and 9 are left empty.

l The Wireless Alarm Unit (WALU) is configured in front slot 16.

l The UMSC PSM Power Modules (UPWRs) are configured in front slots 17 to 20, and rear

slots 19 and 20.

NOTE

The rear slots 17-18 are reserved for a UPWR in the case of system expansion. By default, the two slotsare not configured with the UPWR.



Configuration Guide



Issue 04 (2009-01-15)
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


27/105

Different boards can be configured in the remaining slots based on the networking mode of the

HLR9820.

l If the HLR9820 adopts TDM networking, see OSTA 1.0 Board Configuration in TDM

Networkingfor the board configuration of the OSTA 1.0 subrack.

l If the HLR9820 adopts IP networking, see OSTA 1.0 Board Configuration in IPNetworkingfor the board configuration of the OSTA 1.0 subrack.

l If the HLR9820 adopts ATM-2M networking, see OSTA 1.0 Board Configuration in

ATM-2M Networkingfor the board configuration of the OSTA 1.0 subrack.

Rules for Configuring the OSTA 2.0 Boards

An OSTA 2.0 subrack has a maximum of 16 slots. The slot number ranges from 0 to 15, board

configuration refer toBoard Configuration for Different Product Applications.

The OSTA 2.0 subrack has 14 vertical slots, which are numbered from 0 to 13. The front slots

can be configured with the following types of boards:

l Data Management Unit (DMU)

l Data Routing Unit (DRU)

l Data Service Unit (DSU)

l Service Process Unit (SCU)

l Back Management Unit (BAM)

l Subscriber Management Unit (SMU)

l BAM and SMU Unit (BSU)

l Installation Unit (INU)l Emergency Takeover Unit (ETU)

The rear slots can be configured with the following types of boards:

l Service FC Interface (FCI, that is, USI3)

l Service GE Interface (GEI, that is, USI1)

l Switch Interface Unit (SWI)

The OSTA 2.0 subrack has two horizontal slots, which are numbered from 14 to 15. They are

perpetually configured with the Shelf Management Modules (SMMs).

The rules for configuring the OSTA 2.0 boards are as follows:

l The INU is perpetually configured in front slot 10 in OSTA 2.0 subrack 30, and the GEI

is configured in the rear slot.

l The DMUs are perpetually configured in front slots 0 and 2 in OSTA 2.0 subrack 30, and

the FCIs are configured in therear slots.

l The BSUs or BAMs are configured in front slots 11 and 13 in OSTA 2.0 subrack 30, and

the GEIs are configured in the rear slots.

l The ETU is perpetually configured in front slot 12 in OSTA 2.0 subrack 30, whereas the

rear slot is left empty.

l The SMUs are perpetually configured in front slots 11 and 13 in OSTA 2.0 subrack 31, andthe GEIs are configured in the rear slots.





2-5
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


28/105

l The DRUs are configured in front slots 1 and 3 in OSTA 2.0 subracks, whereas the rear

slots are left empty.

l The SCUs and DSUs are configured in the remaining slots. The SCUs are preferentially

configured in front slots 0, 2, 4, and 8. The DSUs are preferentially configured in front slots

1, 3, 5, 9, 11, and 13. The rear slots are left empty.

OSTA 2.0 Boardsshows the board configuration of the OSTA 2.0 subrack.

2.1.4 Module Number

A board in the HLR9820 is considered as a module. Each module is allocated a number, which

is called the module number.

The module number of each board is unique. The boards working in active/standby mode have

the same module number. The modules are numbered as follows:

l BAM: 0

l WSMU: 2 to 21 (automatically allocated)

l WCSU/WESU/WCCU: 22 to 101

l WIFM/WBSG/WEAM: 132 to 211

l BSU/SMU: 212 to 213

l DSU/DMU/SCU/DRU/ETU/INU: 216 to 249

2.1.5 Cluster

A cluster refers to a group of processes or nodes that provide the same service.

Generally, a cluster consists of one master node and several slave nodes. If the master node isfaulty, the services of the master node are switched to another node in the cluster for processing.

Thus, the service provisioning is not affected by the failure of a single node, and the system

reliability is improved.

The rules for numbering clusters are as follows:

l The HSU cluster ID is set to 1.

l The DRU cluster ID is set to 11.

l The DSU cluster ID ranges from 12 to 512.

The rules for configuring clusters are as follows:

l An HSU cluster is permanently configured. Therefore, you need not configure the HSU

cluster manually.

l A DRU cluster is permanently configured. Therefore, you need not configure the DRU

cluster manually.

l Three DSU clusters are configured for each pair of DSU boards.

2.1.6 Node

A node refers to a unit that can independently provide services. A host or board may have one

or more nodes. The nodes that manage the same subscriber data constitute a cluster.

Based on the node status, the nodes can be classified into two types:



Configuration Guide



Issue 04 (2009-01-15)
http://-/?-


29/105

l Master node: Each cluster can have only one master node. The master node implements

functions such as adding, deleting, modifying, and querying data.

l Slave node: Each cluster may have one or more or no slave nodes. The slave nodes can

only query data.

The nodes of the HLR can be classified into the HSU, DRU, and DSU nodes. The rules for

configuring the nodes are as follows:

l Each DMU board is permanently configured with one HSU node.

l Each SCU board is permanently configured with one HSU node.

l Each DRU board is permanently configured with one DRU node.

l Each DSU board is permanently configured with three DSU nodes.

2.2 Data Configuration Flow Chart

Figure 2-1shows the procedure for configuring the hardware data and the related commands.





2-7


30/105

Figure 2-1Data configuration flow chart

HDU

configuration

On the

SMU client

ATM-2M networking

End

Start

Add a rack(ADD SHF)

Add an OSTA 1.0 subrack(ADD FRM)

Add an OSTA 1.0 board(ADD BRD)

Add an OSTA 2.0 board(ADD SBRD)

Add the WIFM FE port

information

(ADD FECFG)

Add the MEM configuration(ADD MEMCFG)

Add an OSTA 2.0 subrack(ADD SFRM)

Set the local office information (SET LOCALSITE)

Add the cluster configuration(ADD CLUSTER)

Add the node configuration(ADD NODE)

Add the IMA group

information (ADD IMAGRP)

Add the IMA link information

(ADD IMALNK)

Add the PVC link information

(ADD PVCLNK)

Add the UNI link information

(ADD UNILNK)

Configure the clock reference

resource

(SET CKICFG)

Configure the E1 information

(ADD EPICFG)

Configure the clock

reference resource

(SET CKICFG)

Configure the E1

information

(ADD EPICFG)

TDM networking

IP networking

Add the remote node configuration (ADDREMOTENODE)(Optional)

Set the HDU configuration(SET HDU)

Loading SAU data files

Synchronizing the HDU Configuration

Set the OSTA 1.0 board type(ADD BRDTYPE)



Configuration Guide



Issue 04 (2009-01-15)


31/105

CAUTION

After configuring the Fabric network segments by using the SET LOCALSITEcommand,

perform one of the following operations for the configuration to take effect:l Run the IPMISTARTDEAMOND.sh script in the /etc/init.d/directory on all the boards

(except the INU).

l On the LMT, run the RST BRDcommand to restart all the USPs (except the INU) running

the Linux operating system.

l On all the USPs (except the INU) running the Linux operating system, run the

sync;rebootcommand to restart the USPs.

NOTE

l The procedures marked in blue in Figure 2-1are performed during the software installation, skip

these procedures during the data configuration.l If ATM-2M links are used to transfer inter-office signaling, select inverse multiplexing for ATM

(IMA) or user network interface (UNI) mode to configure the data of the system. The configuration

modes of both ends must be the same.

l Configuration of remote node data (by using the ADD REMOTENODEcommand) is required only

for the seamless geographic redundancy solution.

2.3 Hardware Data Table Relation

As shown in Figure 2-1, the hardware data is configured in the following sequence:

l Configuring a rack

l Configuring a subrack

l Configuring a board

Therefore, certain parameters are required to associate them. For example, during the

configuration of a subrack, a parameter is required to ensure that the subrack is configured in

the specified rack. During the configuration of a board, a parameter is required to ensure that

the board is configured in the specified subrack.

Figure 2-2and Figure 2-3show the relations between the hardware data tables.





2-9
http://-/?-


32/105

Figure 2-2OSTA 1.0 hardware data table relation

[Frame number][Slot number]

ADD EPICFG

[Frame number]

[Shelf number][Position number]

ADD FRM

[Shelf number]

[Location title]

[Position number]

[Row number]

ADD SHF

[IFM module number]

[IP address]

[Default gateway]

ADD FECFG

[Frame number]

[Slot number]

[Location title]

[Module number]

ADD BRD

ADD MEMCFG

[Module number]

[Local IP address]

[Column number]

[Mask address]



Configuration Guide



Issue 04 (2009-01-15)


33/105

Figure 2-3OSTA 2.0 hardware data table relation

[Cluster ID]

ADD CLUSTER

ADD NODE

[Cluster ID]

[Module number]

[Node ID]

[Cluster ID]

[Node ID]

ADD REMOTENODE

[Frame number]

[Shelf number]

[Position number]

ADD SFRM

[Frame number]

[Slot number]

[Location title]

ADD SBRD

[Shelf number][Location title]

[Position number]

[Row number]

ADD SHF

[Column number]

[Module number]

[IP address]

2.4 Data Configuration Procedure

2.4.1 Adding a Rack

2.4.2 Adding an OSTA 1.0 Subrack

2.4.3 Setting the OSTA 1.0 Board Type

2.4.4 Adding an OSTA 1.0 Board

2.4.5 Configuring the Hardware Data in TDM Networking





2-11


34/105

2.4.6 Configuring the Hardware Data in IP Networking

2.4.7 Configuring the Hardware Data in ATM-2M Networking



2.4.10 Setting the LocalOffice Information

2.4.11 Adding the Cluster Configuration

2.4.12 Adding the Node Configuration

2.4.13 Setting the HDU Configuration

2.4.14 Adding the Remote Node Configuration

2.4.15 Adding the MEM Configuration

2.4.16 Generating SAU Data Loading Files

2.4.17 Synchronizing the HDU Configuration

2.4.1 Adding a Rack

Add a rack by running the ADD SHFcommand. For details, refer to Adding a Shelf (ADD

SHF).

NOTE

The hardware data is configured in offline mode by default. Before adding a rack, switch the SAU and

HDU to the offline state by running the LOF:;command.


Add an OSTA 1.0 subrack by running the ADD FRMcommand. For details, refer to Adding

a Frame (ADD FRM).

2.4.3 Setting the OSTA1.0 Board Type

You can run the SET BRDTYPEcommand to set the type of the OSTA 1.0 board. For details

on the command description, refer to Set Local Office Board Type (SET BRDTYPE).


Add an OSTA 1.0 board by running the ADD BRDcommand. For details, refer to Adding a

Board (ADD BRD).

2.4.5 Configuring the Hardware Data in TDM Networking

As shown in Figure 2-1, the E1 information and clock reference source are also required to be

set in TDM networking.

For details on how to set the E1 information, refer to Adding the WEPI Configuration (ADDEPICFG).



Configuration Guide



Issue 04 (2009-01-15)
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


35/105

For details on how to set the clock reference source, refer to Setting the WCKI (SET

CKICFG).

2.4.6 Configuring the Hardware Data in IP Networking

As shown in Figure 2-1, the FE port information of the WIFM is also required to be set in IP

networking.

For details on how to add the FE port information, refer to Adding the FE Configuration (ADD

FECFG).

2.4.7 Configuring the Hardware Data in ATM-2M Networking

As shown in Figure 2-1, the information such as IMA group information or UNI link information

is also required to be set in ATM-2M networking.

For details on how to set the E1 information, refer to Adding the WEPI Configuration (ADD

EPICFG).

For details onhow to set the clock reference source, refer to Setting the WCKI (SET

CKICFG).

For details on how to add the IMA group information, refer to Adding the IMA Group

Configuration (ADD IMAGRP).

For details onhow to add the IMA link information, refer to Adding the IMA Link

Configuration (ADD IMALNK).

For details on how to add the UNI link information, refer to Adding the UNI Link

Configuration (ADD UNILNK).

For details on how to add the PVC link information, refer to Adding the PVC Link

Configuration (ADD PVCLNK).


Add an OSTA 2.0 subrack by running the ADDSFRMcommand. For details, refer to Adding

an OSTA 2.0 Frame (ADD SFRM).


Add an OSTA 2.0 boardby running the ADD SBRDcommand. For details, refer to Adding anOSTA 2.0 Board (ADD SBRD).

2.4.10 Setting the Local Office Information

Set the local office information by running the SET LOCALSITEcommand. For details, refer

to Setting the Local Site Information (SET LOCALSITE).

2.4.11 Adding the Cluster Configuration

A cluster consists of multiple logical nodes. Each node can provide services. During deploymentand expansion, you must add the cluster configuration.





2-13
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


36/105

Add the cluster configuration by running the ADD CLUSTERcommand. For details, refer to

Adding the Cluster Configuration (ADD CLUSTER).

2.4.12 Adding the Node Configuration

Add the node configuration by running the ADD NODEcommand. For details, refer to Adding

the Node Configuration (ADD NODE).

2.4.13 Setting the HDU Configuration

Set the HDU configuration by running the SET HDUcommand. For details, refer to Setting

the SMU-HDU Connection (SET HDU).

NOTE

This operation must be performed on the SMU client.

2.4.14 Adding the Remote Node Configuration

Add the remote node configuration by running the ADD REMOTENODEcommand. For

details, refer to Adding the Remote Node Configuration (ADD REMOTENODE).

2.4.15 Adding the MEM Configuration

Add the MEM configuration by running the ADD MEMCFGcommand. For details, refer to

Adding the MEM Configuration (ADD MEMCFG).

2.4.16 Generating SAU Data Loading Files

If the SAU hardware data is added offline, you must format the data of all the modules to

generate .dat files after the SAU hardware data configuration is complete. By default, the files

are stored in the path D:\HLR9820\Load.

Table 2-3lists the procedure for generating a .dat file.

Table 2-3Procedure for generating a .dat file

Step Command Function

1 SET FMT: STS=ON; Enable the format conversion switch.

2 FMT:; Format the data of all the modules.

3 LON:; Switch to the online mode.

2.4.17 Synchronizing the HDU Configuration

If the HDU hardware data is added offline, you must synchronize the data in the HDU database

with that in the BAM database after the HDU hardware data configuration is complete.

Table 2-4lists the procedure for synchronizing the HDU configuration.



Configuration Guide



Issue 04 (2009-01-15)
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


37/105

Table 2-4Procedure for synchronizing the HDU configuration

Step Command Function

1 SET CFGSWITCH: SW=ON; Enable the HDU configuration switch.

2 SYN HDUCFG: MN=250; Synchronize the data in the HDU database with

that in the BAM database.

2.5 Data Configuration Examples

2.5.1 Data Configuration in TDM Networking

2.5.2 Data Configuration in ATM-2M Networking

2.5.3 Data Configuration in IP Networking

2.5.1 Data Configuration in TDM Networking

Description

A rack named HLR9820 is configured. It is located in row 0 and column 0 in the equipment

room and numbered 0.

The rack is configured with an OSTA 1.0 basic subrack in TDM networking. In addition to the

WSMU, WALU, and UPWR, the WCSU and WEPI are configured in the subrack to implement

narrowband signaling processing. Figure 2-4shows the board configuration of the OSTA 1.0

basic subrack.

Clock signals are extracted from E1 0 on the WEPI in slot 0.

The rack is also configured with an OSTA 2.0 subrack. Figure 2-5shows the board configuration

of the OSTA 2.0 subrack.

The port of the maintenance plane is numbered 16504, and that of the service plane is numbered

16500.

The location ID of the local site is 1. The IP addresses of the Fabric network segment are

172.18.100.0 and 172.19.100.0.





2-15


38/105

Figure 2-4Board configuration of the OSTA 1.0 subrack

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Front

Back

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

W

C

S

U

W

C

S

U

W

S

M

U

W

S

M

U

W

A

L

U

U

P

W

R

U

P

W

R

UP

W

R

WC

K

I

WC

K

I

WH

S

C

WS

I

U

WH

S

C

WS

I

U

WE

P

I

WE

P

I


Front

Back

0 1 2 3 4 5 6 7 8 9 10 11 12 13

D

M

U

D

R

U

D

M

U

D

R

U

S

C

U

D

S

U

S

WU

S

W

U

S

C

U

D

S

U

I

NU

B

S

U

B

S

U

0 1 2 3 4 5 6 7 8 9 10 11 12 13

F

C

I

F

CI

S

W

I

S

WI

G

E

I

G

EI

G

E

I

14 15SMM SMM

ET

U

Example/*Enable the offline mode.*/

LOF:;

/*Disable the data formatting function.*/

SET FMT: STS=OFF;

/*Disable the online data configuration for the HDU.*/


/*Add a rack.*/



Configuration Guide



Issue 04 (2009-01-15)


39/105

ADD SHF: SHN=0, LT="HLR9820", PN=0, RN=0, CN=0;

/*You can run the LST SHFcommand to check whether the rack is added.*/

/*Add an OSTA 1.0 subrack.*/

ADD FRM: FN=0, SHN=0, PN=3;/*You can run the LST FRMcommand to check whether the OSTA 1.0 subrack

is added.*/

/*You can run the LST BRDcommand to query the boards added to the OSTA

1.0 subrack.*/

/*Set the board type.*/

SET BRDTYPE: BT=B;

/*The OSTA 1.0 subrack is already configured with the WSMU, WALU, and

UPWR. You need to add the WCSU, WEPI, and WCKI.*/

/*Add the WCSUs. The WCSUs in slots 0 and 1 work in active/standby mode.*/

*/

ADD BRD: FN=0, SLN=0, LOC=FRONT, BT=WCSU, MN=22, ASS=1;

/*Add the interface boards (WEPIs) for the WCSUs.*/ADD BRD: FN=0, SLN=0, LOC=BACK, BT=WEPI;

ADD BRD: FN=0, SLN=1, LOC=BACK, BT=WEPI;

/*Add the WCKIs.*/

ADD BRD: FN=0, SLN=13, LOC=BACK, BT=WCKI;

ADD BRD: FN=0, SLN=15, LOC=BACK, BT=WCKI;

/*You can run the LST BRDcommand to query the board configuration.*/

/*Add E1s.*/

ADD EPICFG: FN=0, SLN=0, E0=DF, E1=DF, E2=DF, E3=DF, E4=DF, E5=DF, E6=DF,

E7=DF, BM=BALANCE;

/*Configure the clock reference source and set its work mode toAutomatic.*/

SET CKICFG: WM=AUTO;

SET CLKSRC: FN=0, SN1=13, SN2=15;

/*Enable the system to use the clock reference source extracted from E1 0

on the WEPI in slot 0.*/

ADD BOSRC: FN=0, SLN=0, EN=0;


ADD SFRM: FN=30, SHN=0, PN=2;

/*You can run the LST SFRMcommand to check whether the OSTA 2.0 subrack

is added.*/

/*You can run the LST SBRDcommand to query the boards added to the OSTA

2.0 subrack.*/

/*Add OSTA 2.0 boards.*/

/*Add the DMUs in slots 0 and 2.*/

ADD SBRD: FN=30, SLN=0, LOC=FRONT, BT=DMU, MN=216, BAPORT=16504;

ADD SBRD: FN=30, SLN=2, LOC=FRONT, BT=DMU, MN=217, BAPORT=16504;

/*Add the DRUs in slots 1 and 3.*/

ADD SBRD: FN=30, SLN=1, LOC=FRONT, BT=DRU, MN=218, BAPORT=16504;

ADD SBRD: FN=30, SLN=3, LOC=FRONT, BT=DRU, MN=219, BAPORT=16504;

/*Add the SCUs in slots 4 and 8.*/

ADD SBRD: FN=30, SLN=4, LOC=FRONT, BT=SCU, MN=220, BAPORT=16504,

FBPORT=16500;ADD SBRD: FN=30, SLN=8, LOC=FRONT, BT=SCU, MN=221, BAPORT=16504,





2-17


40/105

FBPORT=16500;

/*Add the DSUs in slots 5 and 9.*/

ADD SBRD: FN=30, SLN=5, LOC=FRONT, BT=DSU, MN=222, BAPORT=16504;

ADD SBRD: FN=30, SLN=9, LOC=FRONT, BT=DSU, MN=223, BAPORT=16504;

/*Add two BSUs in slots 11 and 13 of subrack 30, and enable the two BAMs

to work in active/standby mode.*/

ADD SBRD: FN=30, SLN=11, LOC=FRONT, BT=BSU, MN=212, ASS=13;

/*Add an INU in slot 10.*/

ADD SBRD: FN=30, SLN=10, LOC=FRONT, BT=INU, MN=224, BAPORT=16504;

/*Add an ETU in slot 12.*/

ADD SBRD: FN=30, SLN=12, LOC=FRONT, BT=ETU, MN=249, BAPORT=16504;

/*You can run the LST SBRDcommand to query the board configuration.*/

/*Set the location ID of the local site.*/

SET LOCALSITE: LOCID=1, IP1="172.18.100.0", MSK1="255.255.255.0",IP2="172.19.100.0", MSK2="255.255.255.0";

/*Add a cluster.*/

ADD CLUSTER: CID=12, CT=DSU;



/*Add nodes.*/

ADD NODE: MN=216, NID=1, NT=HSU, NOFCF=0, NOFSMF=2, CID=1, IPPORTCODE=1;




ADD NODE: MN=218, NID=5, NT=DRU, NOFRDBS=2, CID=11, IPPORTCODE=1;

ADD NODE: MN=219, NID=6, NT=DRU, NOFRDBS=2, CID=11, IPPORTCODE=1;ADD NODE: MN=222, NID=7, NT=DSU, NOFRDBS=2, CID=12, IPPORTCODE=1;

ADD NODE: MN=223, NID=10, NT=DSU, NOFRDBS=2, CID=12, IPPORTCODE=1;





/*Configure the MEM module. Set the module number to 22, local IP address

1 to 172.16.200.22, local IP address 2 to 172.17.200.22, and the subnet

mask to 255.255.0.0.*/

ADD MEMCFG: MN=22, LIP1="172.16.200.22", LIP2="172.17.200.22",

MSK="255.255.0.0";

/*Load the configured data to the HDU.*/

SYN HDUCFG: MN=250;

/*Enable the online data configuration for the HDU.*/


/*Enable the data formatting function.*/

SET FMT: STS=ON;

/*Format the data.*/

FMT:;

/*Start the online mode.*/

LON:;



Configuration Guide



Issue 04 (2009-01-15)


41/105

/*Configure the HDU data on the SMU client. */

SET HDU: OPTYPE=ADD, HDUNAME="DMU0", HDUIP1="172.18.100.2",

HDUIP2="172.19.100.2";

SET HDU: OPTYPE=ADD, HDUNAME="DMU2", HDUIP1="172.18.100.4",

HDUIP2="172.19.100.4";

/*You can run the LST HDUcommand to query the HDU configuration.*/

/*Switch on or restart (switch off and then switch on) the OSTA 1.0

subrack to load the data to all modules.*/

For details on the IP address planning for the modules such as the SMU and the HDU, refer to

IP Addresses of the OSTA 2.0 Boards.

2.5.2 Data Configuration in ATM-2M Networking

Description

A rack named HLR9820 is configured. It is located in row 0 and column 0 in the equipment

room and numbered 0.

The rack is configured with an OSTA 1.0 basic subrack in ATM-2M networking. In addition to

the WSMU, WALU, and UPWR, the WEAM and its back board WEPI are configured in the

subrack to process IMA or UNI links. Figure 2-6shows the board configuration of the OSTA

1.0 basic subrack.

Clock signals are extracted from E1 0 on the WEPI in slot 0.

IMA group 0 with IMA group ID 0 is added. IMA link 0 is added for IMA group 0.

The rack is also configured with an OSTA 2.0 subrack. Figure 2-7shows the board configuration

of the OSTA 2.0 subrack.

The port of the maintenance plane is numbered 16504, and that of the service plane is numbered

16500.

The location ID of the local site is 1. The IP addresses of the Fabric network segment are

172.18.100.0 and 172.19.100.0.


0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Front

Back

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

W

C

K

I

W

E

A

M

W

E

A

M

W

C

C

U

W

C

C

U

W

S

M

U

W

S

M

U

W

B

S

G

W

B

S

G

W

A

L

U

U

P

W

R

U

P

W

R

U

P

W

R

W

C

K

I

W

H

S

C

W

S

I

U

W

H

S

C

W

S

I

U

W

E

P

I

W

E

P

I





2-19
http://-/?-


42/105


Front

Back

0 1 2 3 4 5 6 7 8 9 10 11 12 13

DM

U

D

R

U

D

M

U

DR

U

S

C

U

DS

U

S

W

U

S

W

U

S

C

U

DS

U

I

N

U

B

SU

B

SU

0 1 2 3 4 5 6 7 8 9 10 11 12 13

F

C

I

F

C

I

S

W

I

S

W

I

G

E

I

G

E

I

G

E

I

14 15SMM SMM

E

T

U

Example/*Enable the offline mode.*/

LOF:;

/*Disable the data formatting function.*/

SET FMT: STS=OFF;

/*Disable the online data configuration for the HDU.*/


/*Add a rack.*/

ADD SHF: SHN=0, LT="HLR9820", PN=0, RN=0, CN=0;

/*You can run the LST SHFcommand to check whether the rack is added.*/


ADD FRM: FN=0, SHN=0, PN=3;

/*You can run the LST FRMcommand to check whether the OSTA 1.0 subrack

is added.*//*You can run the LST BRDcommand to query the boards added to the OSTA

1.0 subrack.*/

/*Set the board type.*/

SET BRDTYPE: BT=B;

/*The OSTA 1.0 subrack is already configured with the WSMU, WALU, and

UPWR. You need to add the WEAM, WEPI, WCCU, WBSG, and WCKI.*/

/*Add the WEAMs in slots 0 and 1. The WEAMs work in load-sharing mode.*/

ADD BRD: FN=0, SLN=0, LOC=FRONT, BT=WEAM, MN=132;

ADD BRD: FN=0, SLN=1, LOC=FRONT, BT=WEAM, MN=133;

/*Add the interface boards (WEPIs) for the WEAMs.*/

ADD BRD: FN=0, SLN=0, LOC=BACK, BT=WEPI;ADD BRD: FN=0, SLN=1, LOC=BACK, BT=WEPI;



Configuration Guide



Issue 04 (2009-01-15)


43/105

/*Add a WCCU.*/

ADD BRD: FN=0, SLN=2, LOC=FRONT, BT=WCCU, MN=22, ASS=3;

/*Add the WBSGs.*/

ADD BRD: FN=0, SLN=10, LOC=FRONT, BT=WBSG, MN=134;ADD BRD: FN=0, SLN=11, LOC=FRONT, BT=WBSG, MN=135;

/*Add the WCKIs.*/

ADD BRD: FN=0, SLN=13, LOC=BACK, BT=WC

hlr9820-configuration guide(v900r003c02 04,db2)

Documents