SG7000 Configuration Examples (V200R005C02 - 02)

U-SYS SG7000 Signaling Gateway
V200R005C02
Configuration Examples
Issue 02
Date 2009-12-14
HUAWEI TECHNOLOGIES CO., LTD.

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 trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
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 all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 02 (2009-12-14) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
Configuration Examples About This Document
About This Document
Purpose
This section describes the organization, related versions, intended audiences, conventions and
update history of U-SYS SG7000 Signaling Gateway – Configuration Examples.
Related Versions
The following table lists the product versions related to this document.
Product Name Version
U-SYS SG7000 V200R005C02
Intended Audience
The intended audiences of this document are:
l Installation engineers
l Commissioning engineers
l System engineers
Organization
This document is organized as follows.
Chapter Description
1 Configuring Hardware Introduces the basic data and local office data configuration
and Local Office Data steps and commissioning guide on SG7000.
2 Configuring SG7000 in Details the data configuration steps and commissioning guide
Signaling Transfer on the SG7000 when it is used in the signaling transfer mode.
Mode
Issue 02 (2009-12-14) Huawei Proprietary and Confidential iii

About This Document Configuration Examples
Chapter Description
3 Configuring SG in Details the data configuration steps and commissioning guide

Dual-Homing on the SG7000 when it is configured in dual-homing
Environment environment.
4 Configuring SG7000 in Introduces the data configuration steps and commissioning

STP Mode guide on the SG7000 when it is used as an independent STP in
the PSTN.
5 Configuring SG7000 in Details the data configuration steps and commissioning guide
Agent Mode on the SG7000 when it is used in the signaling agent mode.
Conventions
Symbol Conventions
The following symbols may be found in this document. They are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk which, if not

avoided, will result in death or serious injury.
DANGER
Indicates a hazard with a medium or low level of risk which,

if not avoided, could result in minor or moderate injury.
WARNING
Indicates a potentially hazardous situation that, if not

avoided, could cause equipment damage, data loss, and
CAUTION
performance degradation, or unexpected results.
TIP Indicates a tip that may help you solve a problem or save
your time.
NOTE Provides additional information to emphasize or

supplement important points of the main text.
General Conventions
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.
iv Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Configuration Examples About This Document
Courier New Terminal display is in Courier New.
Command Conventions
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italic.
[] Items (keywords or arguments) in square brackets [ ] are

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

vertical bars. One is selected.
[ x | y | ... ] Optional alternative items are grouped in square brackets

and separated by vertical bars. One or none is selected.
{ x | y | ... } * Alternative items are grouped in braces and separated by

vertical bars. A minimum of one or a maximum of all can
be selected.
GUI Conventions
Boldface Buttons, menus, parameters, tabs, window, and dialog titles are in
boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">" signs. For
example, choose File > Create > Folder.
Keyboard Operation
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressingCtrl+Alt+A means the
three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means the two keys
should be pressed in turn.
Issue 02 (2009-12-14) Huawei Proprietary and Confidential v

About This Document Configuration Examples
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.
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 02 (2009-12-14)

The PDB (DPD100-2-20) is added.
Updates in Issue 01 (2009-09-27)

Initial commercial release.
vi Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Configuration Examples Contents
Contents
About This Document...................................................................................................................iii

1 Configuring Hardware and Local Office Data.....................................................................1-1
1.1 Configuration Overview..................................................................................................................................1-4
1.1.1 Configuring Hardware Data...................................................................................................................1-4
1.1.2 Configuring Local Office Data .............................................................................................................1-6
1.2 Configuration Examples .................................................................................................................................1-6
1.2.1 Configuration Procedures ......................................................................................................................1-7
1.2.2 Configuration Script...............................................................................................................................1-8
1.3 Commissioning Guide ..................................................................................................................................1-10
1.3.1 Configuration Check ...........................................................................................................................1-10
1.3.2 Notes ....................................................................................................................................................1-10
2 Configuring SG7000 in Signaling Transfer Mode...............................................................2-1

2.1 Overview.........................................................................................................................................................2-4
2.1.1 Networking Mode .................................................................................................................................2-4
2.1.3 Configuring Interconnection Data .........................................................................................................2-5
2.2.2 Configuration Description......................................................................................................................2-7
2.3 Commissioning Guide...................................................................................................................................2-10
2.3.2 Notes ....................................................................................................................................................2-11
2.3.3 Configuration Rules ............................................................................................................................2-11
3 Configuring SG in Dual-Homing Environment..................................................................3-1

3.1 Configuration Overview..................................................................................................................................3-4
3.1.1 Networking Mode .................................................................................................................................3-4
3.1.2 Configuring Local Office Data..............................................................................................................3-5
Issue 02 (2009-12-14) Huawei Proprietary and Confidential vii

Contents Configuration Examples

3.3.2 Notes ....................................................................................................................................................3-12
4 Configuring SG7000 in STP Mode.........................................................................................4-1

4.1 Overview.........................................................................................................................................................4-4
4.1.1 Networking Mode .................................................................................................................................4-4
4.2 Configuration Examples..................................................................................................................................4-6
4.3 Commissioning Guide.....................................................................................................................................4-9
4.3.1 Configuration Check .............................................................................................................................4-9
4.3.2 Notes ......................................................................................................................................................4-9
5 Configuring SG7000 in Agent Mode......................................................................................5-1

5.1 Overview.........................................................................................................................................................5-4
5.1.1 Networking Mode .................................................................................................................................5-4
5.3.2 Notes ....................................................................................................................................................5-11
5.3.3 Configuration Rules ............................................................................................................................5-12
viii Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Configuration Examples Figures
Figures
Figure 1-1 Data configuration procedure.............................................................................................................1-2

Figure 1-2 Boards configuration.......................................................................................................................... 1-4
Figure 2-2 Networking of SG7000 in transfer mode........................................................................................... 2-4
Figure 3-2 Dual-homing networking mode..........................................................................................................3-4
Figure 4-2 Networking of SG when used as independent STP............................................................................4-4
Figure 5-2 Networking of SG7000 in agent mode...............................................................................................5-4
Issue 02 (2009-12-14) Huawei Proprietary and Confidential ix

Configuration Examples Tables
Tables
Table 1-1 Hardware data collection......................................................................................................................1-5

Table 1-2 Basic information of main boards........................................................................................................1-5
Table 1-3 Local office data collection..................................................................................................................1-6
Table 1-4 Configuration procedures.....................................................................................................................1-7
Table 2-1 Local office data...................................................................................................................................2-5
Table 2-2 Interconnection data.............................................................................................................................2-6
Table 3-2 Link sets and links................................................................................................................................3-6
Table 4-1 Data of SG_A.......................................................................................................................................4-5
Issue 02 (2009-12-14) Huawei Proprietary and Confidential xi

Configuration Examples 1 Configuring Hardware and Local Office Data
1 Configuring Hardware and Local Office

Data
About This Chapter
This chapter describes the configuration of the hardware data and local office data on the
SG7000. The method for configuring the hardware data also applies to the networking examples
in the subsequent chapters. You can configure the data according to actual conditions.
To configure the SG7000 data, follow the procedure as shown in Figure 1-1. In this way, the
key fields are defined before they are referenced by other data tables and no junk data is
generated.
Issue 02 (2009-12-14) Huawei Proprietary and Confidential 1-1

1 Configuring Hardware and Local Office Data Configuration Examples
Figure 1-1 Data configuration procedure
1.1 Configuration Overview

This section describes the planning of the hardware data and local office data.
1.2 Configuration Examples
This section describes the configuration of the hardware data and local office data on the
SG7000.
1.3 Commissioning Guide
1-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

This section describes the correctness check of the configured hardware data and the local office
data.


This section describes the planning of the hardware data and local office data.
1.1.1 Configuring Hardware Data
This section describes the planning of the hardware data including board types, board positions,
and active/standby mode of the boards.
1.1.2 Configuring Local Office Data
This section describes the planning of the local office data in a table.
1.1.1 Configuring Hardware Data

This section describes the planning of the hardware data including board types, board positions,
and active/standby mode of the boards.
This instance shows how to configure basic service frame 0.
The main control board, clock board, alarm board, and power board adopt the standard
configuration. See Figure 1-2 for details.
Two CKIIs work in the active and standby mode. The CKII uses the line clock from the SEPU
as its clock source. Each CKII extracts two channels of line clocks from the SEPUs in slots 0
and 1 respectively to back up the clock.
In addition, two SBPIs, working in the load sharing mode are configured in slots 5 and 10. Four
SBPUs/SBPEs are configured in slots 0-3. Each SBPU/SBPE has two SLPUs, providing 64-
kbit/s links.
NOTE
This section takes the configuration of SBPUs in slots 0-3 for an example. The configuration of the SBPE is the
same as that of the SBPU.
l When the front board of the SEPU is SBPU, only the SHPU or SLPU can be installed on the SBPU.
l When the front board of the SEPU is SBPE, the SHPU, SLPU, or SHPE can be configured on the SBPE.
Figure 1-2 Boards configuration
S S S S S V H H H H V U U
C C
Back E E E E E I B S B S I P P
K K
board P P P P P E I C I C E
I I
W W
U U U U U B U I U I B R R
Slot No. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
S S S S S S H H S A U U
Front B B B B B B S S B L P P
board P P P P P P Y Y P U W W
U U U U U I S S I I R R

See Table 1-1 and Table 1-2 for the basic information of the boards.
Table 1-1 Hardware data collection

Parameter Value
Cabinet No./Frame No./Cabinet 0/0/Main control frame

type
Clock reference of the CKII No. 0 and No. 1 E1 ports on the SEPU in slot 0
No. 0 and No. 1 E1 ports on the SEPU in slot 1
Table 1-2 Basic information of main boards

Frame No./ Board Board Active/Standby
Slot No. Position
0/0 Front SBPU -
0/0 Back SEPU -
0/1 Front SBPU -
0/1 Back SEPU -
0/2 Front SBPU -
0/2 Back SEPU -
0/3 Front SBPU -
0/3 Back SEPU -
0/4 Front SBPI -
0/4 Back VIEB -
0/6 Front HSYS Active
0/6 Back HBIU Active
0/7 Back HSCU Standby
0/8 Front HSYS Standby
0/8 Back HBIU Standby
0/9 Back HSCU Active
0/11 Front SBPI -
0/11 Back VIEB -
0/13 14 Back CKII Active
0/15 16 Back CKII Standby

Frame No./ Board Board Active/Standby

Slot No. Position
0/16 Front ALUI Independent
0/17 18 Front UPWR -
0/19 20 Front UPWR -
0/17 18 Back UPWR -
0/19 20 Back UPWR -
0/0 subboard Upper or SLPU -

of SBPU lower
subboard

of SBPU lower
subboard

of SBPU lower
subboard

of SBPU lower
subboard

This section describes the planning of the local office data in a table.
See Table 1-3 for collected local office data.
Table 1-3 Local office data collection
Parameter Value
Local IP address/Subnet mask l 10.0.3.10/255.255.255.0

l 10.0.3.11/255.255.255.0
Default gateway 10.0.3.1
Local office information National/A1111C

This section describes the configuration of the hardware data and local office data on the
SG7000.

Before configuring user access data, make sure that the basic data such as hardware data and
local office data is already configured. To ease description, all configuration examples in this
manual use the same basic data.
1.2.1 Configuration Procedures
This section details the configuration of the hardware data and the local office data. It also
introduces the related commands along with configuration examples based on the preceding data
planning.
1.2.2 Configuration Script
This section describes the configuration check after the hardware data and the office data are
configured, and the solutions for command problems.

This section details the configuration of the hardware data and the local office data. It also
planning.
See Table 1-4 for the steps.
Table 1-4 Configuration procedures

Step Operation Description
1 Configuration Run SET OPMODE to set the system offline.

preparations
2 HSYS and ALUI Run commission ADD BRD to configure the HSYS and
configuration the ALUI.
3 SBPU/SBPE Run ADD BRD to configure the SBPU/SBPE.

configuration
4 SHPU/SHPE Run ADD BRD to configure the SHPU/SHPE.

configuration
5 SEPU configuration Run ADD TRUNKSTAT and ADD BRD to configure

the trunk board status and add the SEPU.
6 CKII configuration Run ADD CKISTAT and ADD BRD to configure the
CKII status and add the CKII.
7 Local IP address and Run ADD LIP and ADD BRD to configure the local IP
SBPI configuration address and the SBPI.
8 Local office information Run SET OFI to configure the local office SPC.
configuration
9 Loading preparations Run SET OPMODE, and FMTconvert the format, and
set the software DIP switch.

1.2.2 Configuration Script

This section describes the configuration check after the hardware data and the office data are
configured, and the solutions for command problems.
Prerequisite
You must perform the following before the configuration:
Set the offline mode.

SET OPMODE: LN=LOFF;
Procedure
Step 1 HSYS and ALUI configuration
NOTE
By default, the data of the HSYSs in slots 6 and 8, and ALUI in slot 16 are configured. If the default data
can meet the actual needs, use it. If not, use RMV BRD to remove the default data and configure the data
on your own. When the default data is not configured, perform the following steps:
Add the active and standby HSYSs in slot 6 and slot 8.

ADD BRD: SHN=0, FN=0, FT=MAIN, SN=6, LOC=FPB, BT=HSYS;
ADD BRD: SHN=0, FN=0, FT=MAIN, SN=8, LOC=FPB, BT=HSYS;
Add the ALUI in slot 16.

ADD BRD: SHN=0, FN=0, FT=MAIN, SN=16, LOC=FPB, BT=ALUI;
Step 2 SBPU configuration
Add the SBPUs in slots 0-3.

ADD BRD: SHN=0, FN=0, FT=MAIN, SN=0, LOC=FPB, BT=SBPU;
Step 3 SLPU configuration
Add the upper SHPU-64K and lower SHPU-64K on the SBPUs in slots 0-3.
ADD BRD: SHN=0, FN=0, FT=MAIN, SN=0, LOC=UDB, BT=SHPU64K;
ADD BRD: SHN=0, FN=0, FT=MAIN, SN=0, LOC=DDB, BT=SHPU64K;
NOTE
When adding the SBPI, SEPU, and CKII, use commands ADD LIP, ADD TRUNKSTAT and ADD
CKISTAT to define the IP address of the SBPI, working status of the SEPU and the CKII. Otherwise,
these boards cannot be added.
Step 4 SEPU configuration

To configure the working status of the SEPU, set Link type to EI link, TDM chip clock source
selection to Crystal oscillation of the board, and Configuration of ports 0-15 to
DOUBLEFRAME format by default. Thus index 0 is obtained.
ADD TRUNKSTAT: BT=EU, LT=E1, CH110=LB, EP0=DF, EP1=DF, EP2=DF, EP3=DF,
EP4=DF, EP5=DF, EP6=DF, EP7=DF, EP8=DF, EP9=DF, EP10=DF, EP11=DF,
EP12=DF, EP13=DF, EP14=DF, EP15=DF;
NOTE
The index returned during the configuration can be used in the subsequent configuration. Therefore, you
must record the configuration information and its corresponding index.
To add SEPUs in slots 0-3, set the SEPU in slots 0 and 1 as the clock source board of the CKII
through the hardware DIP switch, and the board property indicator to 0.
ADD BRD: SHN=0, FN=0, FT=MAIN, SN=0, LOC=BPB, BT=SEPU, PI=0;
Step 5 CKII configuration

To add the CKII work state, set priority of clock sources 1 and 2 to 1, and priority of clock
sources 3 and 4 to 0. Thus index 0 is obtained.
ADD CKISTAT: SRCG=L2, PRI1=1, PRI2=1, PRI3=0, PRI4=0;
To add the CKIIs in slots 13 and 14, slots 15 and 16, set Board property indicator to 0.
ADD BRD: SHN=0, FN=0, FT=MAIN, SN=13, LOC=BPB, BT=CKII, PI=0;
ADD BRD: SHN=0, FN=0, FT=MAIN, SN=15, LOC=BPB, BT=CKII, PI=0;
Step 6 Local IP Address and SBPI configuration

To add two local IP address, set Local IP address of FE interface to 10.0.3.10 or 10.0.3.11,
IP mask of FE interface to 255.255.255.0, and Default gateway of FE interface to 10.0.3.1.
Thus index 0 or 1 is obtained.
ADD LIP: LIP="10.0.3.10", MSK="255.255.255.0", DGW="10.0.3.1"; //The
index 0 is obtained.
ADD LIP: LIP="10.0.3.11", MSK="255.255.255.0", DGW="10.0.3.1"; //The
index 1 is obtained.
Add the SBPIs in slots 5 and 10. The SBPIs work in the load sharing mode. Set Board property
indicator to the index returned with the command ADD LIP.
ADD BRD: SHN=0, FN=0, FT=MAIN, SN=5, LOC=FPB, BT=SBPI, PI=0;
ADD BRD: SHN=0, FN=0, FT=MAIN, SN=10, LOC=FPB, BT=SBPI, PI=1;
Step 7 Local Office Information configuration

To add local office information, set National network code to A1111C and SCCP function to
FALSE.
SET OFI: NPC="A1111C", SCCP=FALSE;
NOTE
The local SP belongs to a specified logical network whose index is 0. To modify or add a logical network,
use ADD LN or MOD LN.
Step 8 Loading Preparations

1. Set the online mode.

SET OPMODE: LN=LON;

2. Convert the format.
FMT;
3. Power off the board and then power it on to load the data.
----End

This section describes the correctness check of the configured hardware data and the local office
data.
1.3.1 Configuration Check
This section describes some special points that you need to care about when configuring the
hardware data and the local office data.
1.3.2 Notes
Many problems may occur during the configuration of the hardware data and local office data.
Take precautions against the following common problems.

hardware data and the local office data.
After the loading is complete, perform the following steps to ensure that the configuration of
board data is complete and the status is correct.
l Run LST BRD,LST OFI, and LST LIP to view data on the BAM.
l Run DSP BRD to check host board status.
l Run ACT CNSCHK to check the data consistency.
1.3.2 Notes
Many problems may occur during the configuration of the hardware data and local office data.
Take precautions against the following common problems.
Perform the following steps:
l Set status for the SBPI, SEPU/EPII, and CKII before you add them.
l Record the returned indexes and fill them in relevant fields.

Configuration Examples 2 Configuring SG7000 in Signaling Transfer Mode
2 Configuring SG7000 in Signaling Transfer

Mode
About This Chapter
The system uses complete SIGTRAN and SS7 protocols to implement the interworking between
broadband signaling and narrowband signaling. The SG7000 works in signaling transfer mode
with an independent signaling point code (SPC), and uses the M3UA or M2PA protocol to
interconnect with the softswitch and the ISUP protocol to interconnect with the STP. The SGs
are configured in pairs to provide reliability.
generated.

2 Configuring SG7000 in Signaling Transfer Mode Configuration Examples
2.1 Overview
This section describes the networking structure of the SG7000 working in transfer mode and the
planning of the local data and the interworking data.
This section describes the procedures for configuring the SG7000 working in transfer mode
based on the data planning.

This section describes the configuration check after the SG7000 data is configured, and the
solutions for command problems.

2.1 Overview
This section describes the networking structure of the SG7000 working in transfer mode and the
planning of the local data and the interworking data.
2.1.1 Networking Mode
This section introduces the networking structure in which the SG7000 interconnects with the
STP and the softswitch in transfer mode.
This section describes the data planning of the SG7000 working in transfer mode, including the
working mode, SPC, and IP address.
2.1.3 Configuring Interconnection Data
This section describes the planning of the interworking data on the SG7000 working in transfer
mode, including the route context, connection mode, and IP address.

STP and the softswitch in transfer mode.
As shown in Figure 2-2, SG_A is interconnected with SX_A through M3UA links at the
broadband side, and with the STP through MTP links at the narrowband side. The SG uses an
independent SPC. SG_A and SG_B are configured in a pair in active/standby mode, with C links
in between, names, M2PA links.
Figure 2-2 Networking of SG7000 in transfer mode
Take SG_A for example:
On the direction to SG_B, configure one M2PA link on an SBPU/SBPE.

On SX_A, two SBPIs have different IP address. They work in the load sharing mode. Two
M3UA associations should be set up on two SBPUs/SBPEs to share the load.
On STP_A, one semi-permanent link is configured on each of the two SEPUs, and one MTP
link on each of the two SLPUs mapping the SEPUs. Two links of a same kind adopt the load
sharing mode.
On STP_B, the configuration is the same as that on STP_A.
For information on configuring SG_B, see the configuration on SG_A.

This section describes the data planning of the SG7000 working in transfer mode, including the
working mode, SPC, and IP address.
Table 2-1 lists the data to be configured in the local office.
Table 2-1 Local office data
S Parameter Value
N.
1 Working mode of SG Transfer mode
2 Working mode of M3UA association Load-sharing mode
3 IP address of SG_A 10.0.3.10 / 255.255.0.0 /

10.0.3.1
4 Port number of SG_A 2904/2905/2906
5 SPC of SG_A A1111C
6 IP address of SG_B 10.0.4.10 / 255.255.0.0 /

10.0.4.1
7 Port number of SG_B 2907/2908
8 SPC of SG_B A1111D
9 SPC of SX_A A1111A
10 SPC of STP_A A1111E
11 SPC of STP_B A1111F
12 STP signaling point type ITU

This section describes the planning of the interworking data on the SG7000 working in transfer
mode, including the route context, connection mode, and IP address.
The interconnection data, as listed in Table 2-2, is configured after the coordination with the
peer office.

Table 2-2 Interconnection data

Parameter Value
SG_A SX_A STP
Routing context in 1234 1234 -

adding M3UA
application server
Working mode in adding SGP ASP -

M3UA association set
C/S mode in adding SERVER CLIENT -

M3UA association
IP address of SX_A - 10.0.1.10/255.255. -

0.0
Port number of SX_A - 2905/2906 -
MTP SLC 0-3 - 0-3
Occupied port and Timeslot 1 on ports 0 - Timeslot 1 of

timeslot and 1 in slot 0.Timeslot four trunks.
1 on ports 0 and 1 in slot
1.

This section describes the procedures for configuring the SG7000 working in transfer mode
This section describes the general procedures for configuring the SG7000 working in transfer
mode after the hardware data and local office data are configured.
2.2.2 Configuration Description
This section details the configuration of the SG7000 working in transfer mode. It also introduces
the related commands along with configuration examples based on the preceding data planning.

This section describes the general procedures for configuring the SG7000 working in transfer
mode after the hardware data and local office data are configured.
For details, see 1 Configuring Hardware and Local Office Data
See Table 2-3 for steps.


1 IP address Run ADD LIPC, ADD RIP, ADD RIPC, and ADD
IPDACL to configure the local IP address combination,
remote IP address, IP address combination and add all
RIPs to the Access control table. (The local IP address
has been configured in hardware data configuration.)
2 M3UA destination entity Run ADD N7DSP and ADD M3AS to configure the
remote SPC and application server.
3 M3UA association set Run ADD M3ASSOS and ADD M3RT to configure
and M3UA route M3UA association set and M3UA route.
4 M3UA association Run ADD M3ASSO to configure the M3UA

association.
5 M2PA DSP Run ADD N7DSP to configure M2PA destination

signaling point.
6 M2PA link set and route Run ADD N7LKS and ADD N7RT to configure M2PA
link set and route.
7 M2PA link Run ADD N7LNK to configure M2PA link.
8 MTP DSP Run ADD N7DSP to configure the MTP DSP for
STP_A and STP_B.
9 MTP link set and MTP Run ADD N7LKS and ADD N7RT to configure the
route MTP link set and MTP route.
10 MTP link Run ADD TDMCONN and ADD N7LNK to configure

the semi-permanent connection and MTP link.

This section details the configuration of the SG7000 working in transfer mode. It also introduces
Context
NOTE
The index returned during the configuration can be used in the subsequent configuration. Therefore, you
must record the configuration information and its corresponding index.
Perform the following steps to configure SG_A. You can perform similar configuration steps
on SG_B.
Procedure
Step 1 IP Address
1. Add a record in the Local IP address combination table. Use the index obtained after the
execution of ADD LIP.

ADD LIPC: DESC="SGC", FEX1=0;
The index 0 is obtained after the command is executed.

2. Add the IP address of SX_A.
ADD RIP: RIP="10.0.1.10";

3. Add the IP address of SX_A to the Remote IP address combination table.
ADD RIPC: RIPX1=0;

4. Add the IP address of SX_A to the Access control table.
ADD IPDACL: IP="10.0.1.10";
5. Add the IP address of SG_B.
ADD RIP: RIP="10.0.4.10";

6. Add the IP address of SG_B to the Remote IP address combination table.
ADD RIPC: DESC="SGB_C", RIPX1=1;

7. Add the IP address of SG_B to the Access control table.
Step 2 M3UA Destination Entity

1. To add an MTP DSP, set DSP title to SX_A, National network code to A1111A, STP to
FALSE, and SCCP function to Without SCCP function, and Route selection field to
0. Keep the values of other parameters unchanged. The index 0 is obtained.
ADD N7DSP: DESC="SX_A", NPC="A1111A", STP=FALSE, SLS=0, SCCPUSED=NONE;
2. To add an M3UA application server, set Network indication to National network,
Routing context to 1234. You need not configure Association set select mask code,
because there is only one route. The index 0 is obtained. Destination point code index
uses the index obtained after ADD N7DSP is carried out.
ADD M3AS: NI=NM, SWM=TM, DPCX=0, RC=1234;
Step 3 M3UA Association Set and M3UA Route

1. To add an M3UA association set, set Traffic mode to Load-share mode, and Association
select mask code to 1 because there are two links in this association set. The index 0 is
obtained.
ADD M3ASSOS: ASX=0, ASC=1 , TM=LOADSHARE, WM=SGP;
2. Add an M3UA route. The indexes for Application server index and Association set
index are those returned after the execution of ADD M3AS and ADD M3ASSOS.
ADD M3RT: ASX=0, ASSX=0;
NOTE
The M2UA, M3UA, IUA and M2PA protocols are transmitted based on SCTP. For easy management, you
must arrange the local SCTP port numbers for each link before data configuration. Do not try to use the
same port number repeatedly.
Step 4 M3UA Association

To add an M3UA association, set Board Assoc. number to 0, Local port and Remote port to
0, Priority to 0, C/S mode to Server side, Active_Standby flag to Active initially, and SCTP
index is 0. Keep the values of other parameters unchanged.

ADD M3ASSO: SN=0, FN=0, BN=0, PLNO=0, LIPCX=0, LP=2905, RIPCX=0, RP=2905,
CS=S, ASSI=0, ASF=YES, SCTPIDX=0;
ADD M3ASSO: SN=0, FN=0, BN=1, PLNO=0, LIPCX=0, LP=2906, RIPCX=0, RP=2906,
CS=S, ASSI=0, ASF=YES, SCTPIDX=0;
Step 5 M2PA DSP

To add an M2PA DSP, set Description to SG_B, National network code to A1111D, STP to
FALSE, Route selection field to 0 (only one route is configured), and SCCP function to
Without SCCP function. Keep the values of other parameters unchanged.
ADD N7DSP: DESC="SG_B", NPC="A1111D", STP=FALSE, SLS=0, SCCPUSED=NONE;

Step 6 M2PA link set and route
1. To add a link set from SG_A to SG_B, set Adjacent SP index to 1 (IP address index of
SG_B), Local SP index to 0 (the index obtained in ADD LIP), Network indication to
National, and Link selection field to 0 (the link set contains only one link).
ADD N7LKS: DESC="SGA_M2PA", APX=1, OFX=0, NI=NM;

2. To add a route from SG_A to SG_B, perform the following settings.
ADD N7RT: DESC="TO SG_B", LSX=0, DPX=1;
3. To add an alternative route from SG_A to SX_A, perform the following settings.
ADD N7RT: DESC="TO SX_A", LSX=0, DPX=0, PR=1;
Step 7 M2PA link

To add an M2PA link from SG_A to SG_B, perform the following settings.
ADD N7LNK: LN="SGA TO SGB", SHN=0, FN=0, SN=0, LOC=FPB, LPN=0, LSX=0,
CT=M2PALNK, TX=0, LP=2904, PP=2907, LIPCX=0, PIPCX=1, SCTPIDX=0;
Step 8 MTP DSP

To add DSPs for STP_A and STP_B, set STP to TRUE, and SCCP function to Without SCCP
function, Adjacent flag to TRUE, and Route selection field to 0. Keep the values of other
parameters unchanged.
ADD N7DSP: DESC="STP_A", NPC="A1111E", STP=TRUE, APF=TRUE, SCCPUSED=NONE;
ADD N7DSP: DESC="STP_B", NPC="A1111F", STP=TRUE, APF=TRUE, SCCPUSED=NONE;
Indexes 2 and 3 are obtained after the commands are executed.

Step 9 MTP Link Set and MTP Route
1. To add MTP link sets, set Link selection field to 1 because there are two links in each link
set, Link set title of STP_A to LS0, and Link set title of STP_B to LS1.
ADD N7LKS: DESC="LS0", APX=1, OFX=0, NI=NM, SLS=1;
ADD N7LKS: DESC="LS1", APX=2, OFX=0, NI=NM, SLS=1;
Indexes 1 and 2 are obtained after the commands are executed.

2. Add MTP routes
ADD N7RT: DESC="TO STP_A", LSX=0, DPX=1, PR=0, TX=0;
ADD N7RT: DESC="TO STP_B", LSX=1, DPX=2, PR=0, TX=0;
Step 10 MTP Link

1. Add TDM semi-permanent connections.

Set up two semi-permanent connections on the boards in slots 0 and 1 respectively and set
SPC attribute to Signaling timeslot connection. Set up MTP links together with the
SLPUs in the same slots. The indexes 0-3 are obtained after the commands are executed.
ADD TDMCONN: HLA=STSL, SHN=0, FN=0, SN=0, E1P=0, TS=1, TSN=1;
Indexes 0, 1, 2, and 3 are obtained after the commands are executed.

2. Add two MTP links on LS0 of STP_A and LS1 of STP_B respectively. The links are
numbered 0-4.
ADD N7LNK: LN="LS01-01", SHN=0, FN=0, SN=0, LOC=UDB, LPN=0, LSX=1,
SLC=0, CT=NOR64K, HLN=0;
----End

This section describes the correctness check of the data configured for the SG7000 working in
transfer mode.
2.3.2 Notes
SG7000 data.
2.3.3 Configuration Rules
This section describes the principles you must follow when configuring the SG7000 data,
including "M3UA route select mask code" and "M3UA association select mask code".

transfer mode.
Check M3UA Association

After M3UA associations are activated, perform the following steps to check whether the
configuration is correct:
l Use DSP MULM3AS to check the status of the application server.

l Use DSP MULM3ASSOS to check the status of the association set.
l Use DSP MULM3RT to check the status of the route.
l Use DSP MULM3ASSO to check the status of the association.

l Use DSP SCTPASSOC2 to check the status of the SCTP association.
Check MTP Link

Run the following commands to check the status of the MTP link set, MTP link, MTP route and
MTP DSP.
l DSP MULN7LNK
l DSP MULN7LKS
l DSP MULN7RT
l DSP MULN7DSP
2.3.2 Notes
SG7000 data.
Configuring M3UA Association

l The remote IP information should be added to the Access control table for accessing the
table.
l In configuring the M3UA application server on the SG, the value of Routing context
should be consistent with that configured on the application server.
l Configure the client or server mode and ASP or SGP mode at both sides correctly.
Generally, the side working in the SGP mode acts as the server.
l Reach an agreement before configuring the interconnection data for the ports at both sides.
l Perform link activation or deactivation operations on the MSOFTX3000 because the SG
serves as the signaling gateway and cannot perform these operations.
Configuring MTP Link

l The route selection field should be set based on the number of routes, thus load sharing is
realized.
l When adding the semi-permanent connection, the E1 port number must be consistent with
the number of the physical cable. The occupied timeslots at both ends of a link must be
consistent. The signaling link codes should be consistent at both sides.
l The link selection field should be set based on the number of contained links; otherwise,
the status of a certain link in the link set may be Unused.

This section describes the principles you must follow when configuring the SG7000 data,
including "M3UA route select mask code" and "M3UA association select mask code".
M3UA Route Select Mask Code

To achieve balance of the traffic to a specific application server, a certain algorithm must be
defined to distribute the traffic over different routes. In the SG7000, the route select mask code
participates in the algorithm for load sharing of the traffic. The value is a decimal value of 4-bit
binary number. For example, the route select mask code is 1001 and the corresponding decimal
value is 9. The default value of this parameter is 0.

The configuration principles of the parameter are as follows:
l Set all bits to 0 if there is only one M3UA route.

l Set one bit to 1 if there are two M3UA routes.
l Set two bits to 1 if there are three or four M3UA routes.
l Set three bits to 1 if there are five to eight M3UA routes.
l Set all four bits to 1 if there are more than eight routes.
l Do not set the route select mask code the same as the association select mask code of each
association set to avoid the system always selecting the same route. It is recommended to
stagger the places of "1" in the two mask codes. For example, if the route select mask code
is 0110, the association select mask code can be set to 1001.
M3UA Association Select Mask Code

It indicates how to distribute the traffic load over several M3UA links to the same M3UA
application server. In fact, the value of this filed is the load sharing mask. The value is a decimal
value of a 4-bit binary number. For example, for the link select mask code 1001, the
corresponding decimal value is 9. The default value of this parameter is 0.
l Set all bits to 0 if there is only one M3UA association.

l Set one bit to 1 if there are two M3UA associations.
l Set two bits to 1 if there are three or four M3UA associations.
l Set three bits to 1 if there are five to eight M3UA associations.
l Set all four bits to 1 if there are more than eight associations.
l Do not set the route select mask code and this parameter to the same value to avoid the
system always selecting the same route. It is recommended to stagger the places of "1" of
the two mask codes. For example, if the route select mask code is 0110, the link select mask
code can be set to 1001.
MTP Route Selection Field

It indicates how to implement load sharing of the signaling traffic between multiple signaling
routes to the DSP. The value is an 8-bit binary number and it ranges from 0 to 255. The default
value is 0.
The configuration principle of the parameter is as follows:
l When there is only one route between the SG7000 and the DSP, set Route Selection
Field to 0, which is the default value.
l Try to use the upper four bits of the route selection field, and thus all the MTP links in the
same link set sent to different non-adjacent signaling points can be selected to share the
signaling traffic load.
l Do not set the lower four bits of Route Selection Field the same value as the value of Link
Selection Field in each link set to avoid the system always selecting the same route. It is
recommended to stagger the places of "1" in the two fields. For example, if Route Selection
Field is set to 0110 (upper four bits are 0000), the Link Selection Field can be set to 1001.

MTP Link Selection Field

links in a signaling link set. In fact, the value of this filed is the load sharing mask. The value is
a decimal value of a 4-bit binary number and it ranges from 1 to 15. The default value is 0.
l When there is only one link in a link set, set all bits of Field Selection Field to 0, which is
the default value.
l Set one bit to 1 if there are two MTP routes.
l Set two bits to 1 if there are three or four MTP links.
l Set three bits to 1 if there are five to eight MTP links.
l Set all four bits to 1 if there are more than eight MTP links.

Configuration Examples 3 Configuring SG in Dual-Homing Environment
3 Configuring SG in Dual-Homing
Environment
About This Chapter
To ensure service reliability, the softswitch uses the dual-homing solution. The dual-homing
solution is a disaster tolerance mechanism, in which the two softswitches work in the mutual-
aid mode. When softswitch A is faulty, softswitch B replaces softswitch A to process services.
The SG can use a similar solution. Thus, when the softswitch switches over or switches back,
the SG can send services to the correct softswitch.
generated.

3 Configuring SG in Dual-Homing Environment Configuration Examples

This section describes the data configuration on the SG7000 working in dual-homing mode. It
also introduces the networking structure and the planning of the SG7000 data and the
interworking data.
This section describes the procedures for configuring the signaling gateway in dual-homing
softswitching environment based on the data planning.




This section describes the data configuration on the SG7000 working in dual-homing mode. It
also introduces the networking structure and the planning of the SG7000 data and the
interworking data.
STP and the softswitch in dual-homing mode. For the sake of disaster tolerance, the softswitches
are configured in dual-homing mode.
This section describes the data configuration on the SG7000working in dual-homing mode.
This section describes the configuration of the interworking data on the SG7000. The
interworking data must be configured under the negotiations with the peer side.

STP and the softswitch in dual-homing mode. For the sake of disaster tolerance, the softswitches
are configured in dual-homing mode.
Figure 3-2 Dual-homing networking mode
Networking
As shown in Figure 3-2, SX_A and SX_B are two softswitches working in the mutual-aid mode,
and SG_A and SG_B are mutual-backup SGs working in the load-sharing mode. Both SG_A
and SG_B are homed to SX_A and SX_B. This is called dual-homing.
The softswitch interworks with PSTN equipment through the SG. The links to both SX_A and
SX_B are configured on the SG. Thus, when SX_A takes over SX_B, the SG can distribute

signaling messages that have been sent to SX_B to SX_A. When SX_B is restored, the SG can
distribute signaling messages to SX_B again.
For the connection between the SG and the softswitch, the load-sharing mode based on link
priorities is recommended. It means that the links between the SG and two softswitches work
in the load-sharing mode and the service is switched over between the active and the standby
softswitches based on link priorities. The following configuration examples are based on the
load-sharing mode.
Configuration on Softswitch
On SX_A, configure the master source signaling point A1111A and the slave one A1111B, and
set them in the mutual-aid mode. Set the links from the two signaling points to both SG_A and
SG_B in four respective link sets. Generally, the links between the slave signaling point A1111B
and the SG are disabled. They are enabled only when SX_A takes over SX_B in the case that
SX_B is faulty. Thus, the service on SX_B is restored.
Similarly, configure the master source signaling point A1111B and the slave one A1111A on
SX_B. Set the links from the two signaling points to both SG_A and SG_B in four respective
link sets.
Configuration on SG
On SG_A, configure link set 1 (LS1) to connect to signaling point A1111A. The link LS1-1,
which has higher priority, is connected to the master signaling point A1111A of SX_A. The link
LS1-2, which has lower priority, is connected to the slave signaling point A1111A of SX_B.
Generally, SG_A uses LS1-1 to send messages to SX_A and LS1-2 is disabled. When SX_A is
faulty, LS1-1 is faulty. SX_B takes over SX_A. As a result, LS1-2 is enabled and SG_A sends
the messages that have been sent to the A1111A of SX_A to the A1111A of SX_B.
Similarly, configure LS2 on SG_A to connect with signaling point A1111B. The configuration
of LS2 and its links are similar with that of LS1 and its links.
On SG_B, configure LS3 to connect with signaling point A1111A and LS4 to connect to
signaling point A1111B. The configuration is the same as that conducted on SG_A. Half of the
links in a link set have higher priority and are connected to the master signaling point A1111A,
and half of them have lower priority and are connected to the slave signaling point A1111B.
Configure link set 5 (LS5) between SG_A and SG_B. The link type is of the C link, namely,
M2PA links.

This section describes the data configuration on the SG7000working in dual-homing mode.
Table 3-1 and Table 3-2 list the data to be configured in the local office.

S Parameter Value
N.

S Parameter Value
N.
3 IP address of SG_A 10.0.3.10/255.255.0.

0
4 Port number of SG_A 2905
6 IP address of SG_B 10.0.4.10/255.255.0.

0
7 Port number of SG_B 2906
9 IP address of SX_A 10.0.1.10/255.255.0.

0
10 Active/standby port number of SX_A 2907/2908
11 SPC of SX_A A1111A
12 IP address of SX_B 10.0.2.10/255.255.0.

0
13 Active/standby port number of SX_B 2909/2910
14 SPC of SX_B A1111B
15 SPC of STP_A A1111E
16 SPC of STP_B A1111F
17 STP signaling point type ITU
Table 3-2 Link sets and links
To master To slave To master To slave

signaling point signaling point signaling signaling point
A1111A of A1111A of SX_B point A1111B A1111B of SX_A
SX_A of SX_B
SG_A link LS1, index 0 LS2, index 1

sets
SG_A Higher priority, Lower priority, Higher priority, Lower priority,

links index 0 index 1 index 2 index 3
SG_B link LS3, index 1 LS4, index 0

sets
SG_B Higher priority, Lower priority, Higher priority, Lower priority,

links index 2 index 3 index 0 index 1


This section describes the configuration of the interworking data on the SG7000. The
interworking data must be configured under the negotiations with the peer side.
Table 3-3 lists the interconnection data to be configured.

Parameter Value
SG7000_A SX_A STP

adding M3UA
application server


M3UA association
MTP SLC 0-3 - 0-3
Occupied port and Timeslot 1 on port 0 of - Timeslot 1 of

timeslot trunk boards in slots four trunks.
0-3.

This section describes the procedures for configuring the signaling gateway in dual-homing
softswitching environment based on the data planning.
This section describes the general procedures for configuring the SG7000 working in dual-
homing mode after the hardware data and local office data are configured.
This section details the configuration of the SG7000 working in dual-homing mode. It also
planning.

This section describes the general procedures for configuring the SG7000 working in dual-
homing mode after the hardware data and local office data are configured.
For details, see 1 Configuring Hardware and Local Office Data

IPDACL to configure the remote IP address, IP address
combination and add them to the Access control
table.(The local IP address is configured in hardware
data configuration.)
2 M3UA destination entity Run ADD N7DSP and ADD M3AS to configure the
remote SPC and application server.
3 M3UA association set Run ADD M3ASSOS and ADD M3RT to configure
and M3UA route M3UA association set and M3UA route.

association.
5 M2PA DSP Run ADD N7DSP to configure M2PA destination

signaling point.
6 M2PA link set and route Run ADD N7LKS and ADD N7RT to configure M2PA
link set and route.
7 M2PA link Run ADD N7LNK to configure M2PA link.
STP_A and STP_B.
9 MTP link set and MTP Run ADD N7LKS and ADD N7RT to configure the
route MTP link set and MTP route.
10 MTP link Run ADD TDMCONN and ADD N7LNK to configure

the semi-permanent connection and MTP link.

This section details the configuration of the SG7000 working in dual-homing mode. It also
planning.
Context
NOTE
The index returned during the configuration is generally used in the subsequent configuration. Therefore,
you must record the configuration information and its corresponding index.
on SG_B.
Procedure
Step 1 IP Address

execution of ADD LIP. The index 0 is obtained.
ADD LIPC: DESC="SG7000C", FEX1=0;
2. Add IP addresses for remote SX_A and SX_B.
ADD RIP: DESC="SX_A", RIP="10.0.1.10"; (The index 0 is obtained after
the command is executed.)
ADD RIP: DESC="SX_B", RIP="10.0.2.10"; (The index 1 is obtained after
the command is executed.)
3. Add IP address combination for remote SX_A and SX_B.
DD RIPC: RIPX1=0; (The index 0 is obtained after the command is
executed.)
ADD RIPC: RIPX1=1; (The index 1 is obtained after the command is
executed.)
4. Add the IP addresses to the Access control table.
5. Add the IP address of SG_B.
ADD RIP: RIP="10.0.4.10";

6. Add the IP address of SG_B to the Remote IP address combination table.
ADD RIPC: DESC="SGB_C", RIPX1=2;

7. Add the IP address of SG_B to the Access control table.

1. To add an MTP DSP, set DSP title to SX_A and SX_B respectively, National network
code to A1111A and A1111B respectively, STP to FALSE, and SCCP function to
Without SCCP function, and Route selection field to 0. Keep the value of other
ADD N7DSP: DESC="SX_A", NPC="A1111A", STP=FALSE, SLS=0,
SCCPUSED=NONE; (The index 0 is obtained after the command is
executed.)
ADD N7DSP: DESC="SX_B", NPC="A1111B", STP=FALSE, SLS=0,
SCCPUSED=NONE; (The index 1 is obtained after the command is executed.)
2. To add an M3UA application server, set Network indication to National network,
Routing context to 1234. Keep the default value of Association set select mask code.
ADD M3AS: NI=NM, SWM=TM, DPCX=0, RC=1234; (The index 0 is obtained
after the command is executed.)
ADD M3AS: NI=NM, SWM=TM, DPCX=1, RC=1234;(The index 1 is obtained
after the command is executed.)

1. To add an M3UA association set, set Traffic mode to Load-share mode, Work mode to
SGP, and Association select mask code to 1because there are two links.
ADD M3ASSOS: DESC="LS1", ASX=0, ASC=1 , TM=LOADSHARE, WM=SGP; (The
index 0 is obtained after the command is executed.)
ADD M3ASSOS: DESC="LS2", ASX=1, ASC=1 , TM=LOADSHARE, WM=SGP; (The
2. To add an M3UA route, proceed as follows:
Configure an M3UA route to SX_A passing over LS1.

Configure an M3UA route to SX_B passing over LS2.


Configure SG as the client and the softswitch as the server. SG_A is connected to A1111A of
SX_A through LS1-1 and that of SX_B through LS1-2, with A1111B of SX_A through LS2-1
and that of SX_B through LS2-2.
1. Configure two M3UA associations on LS1, and LS1-1 has higher priority.
ADD M3ASSO: SN=0, FN=0, BN=0, PLNO=0, DESC="LS1-1", LIPCX=0, LP=2905,
RIPCX=0, RP=2905, CS=S, ASSI=0, ASF=YES, PRI=0, SCTPIDX=0;
ADD M3ASSO: SN=0, FN=0, BN=1, PLNO=0, DESC=" LS1-2", LIPCX=0, LP=2905,
2. Configure two M3UA associations on LS2, and LS2-1 has higher priority.
Step 5 M2PA DSP

To add an M2PA DSP, set Description to SG_B, National network code to A1111D, STP to
FALSE, Route selection field to 0 (only one route is configured), and SCCP function to
Without SCCP function. Keep the values of other parameters unchanged.
ADD N7DSP: DESC="SG_B", NPC="A1111D", STP=FALSE, SLS=0, SCCPUSED=NONE;

Step 6 M2PA link set and route
1. To add a link set from SG_A to SG_B, set Adjacent SP index to 2 (IP address index of
SG_B), Local SP index to 0 (the index obtained in ADD LIP), Network indication to
National, and Link selection field to 0 (the link set contains only one link).
ADD N7LKS: DESC="LS5", APX=2, OFX=0, NI=NM;

2. To add a route from SG_A to SG_B, perform the following settings.
ADD N7RT: DESC="TO SG_B", LSX=0, DPX=2;
3. To add an alternative route from SG_A to SX_B, perform the following settings.
ADD N7RT: DESC="TO SX_A", LSX=0, DPX=0, PR=1;
4. To add an alternative route from SG_A to SX_A, perform the following settings.
ADD N7RT: DESC="TO SX_B", LSX=0, DPX=1, PR=1;
Step 7 M2PA link

To add an M2PA link from SG_A to SG_B, perform the following settings.
ADD N7LNK: LN="SGA TO SGB", SHN=0, FN=0, SN=0, LOC=FPB, LPN=0, LSX=0,
CT=M2PALNK, TX=0, LP=2905, PP=2906, LIPCX=0, PIPCX=2, SCTPIDX=0;
Step 8 MTP DSP

function, and Adjacent flag to TRUE, and Route selection field to 0. Keep the values of other

ADD N7DSP: DESC="STP_A", NPC="A1111E", STP=TRUE, APF=TRUE, SCCPUSED=NONE;

(The index 3 is obtained after the command is executed.)
ADD N7DSP: DESC="STP_B", NPC="A1111F", STP=TRUE, APF=TRUE, SCCPUSED=NONE;

1. To add MTP link sets, set Link selection field to 1because there are two links in each link
set. Link set title of STP_A to LS6, and Link set title of STP_B to LS7.
ADD N7LKS: DESC="LS6", APX=2, OFX=0, NI=NM, SLS=1; (The index 1 is
obtained after the command is executed.)
2. Add MTP routes based on created MTP DSP and the indexes obtained in adding MTP link
sets.
ADD N7RT: DESC="TO STP_A", LSX=1, DPX=3;
ADD N7RT: DESC="TO STP_B", LSX=2, DPX=4;
Step 10 MTP Link

Set up two semi-permanent connections for LS6 and LS7 respectively on SEPUs in slots
0-3 and set SPC attribute to Signaling timeslot connection. Set up MTP links together
with the SLPUs in the same slots as the SEPUs. The indexes 0-3 are obtained after the
command is executed.
ADD TDMCONN: HLA=STSL, SHN=0, FN=0, SN=0, E1P=0, TS=1, TSN=1; (The
2. Add MTP links.
Add two MTP links on LS6 and LS7 respectively. The SLCs of both the link sets are
numbered in the ascending order, starting from 0. TDM SPC index maps the index obtained
after ADD TDMCONN is executed.
----End

dual-homing mode.

3.3.2 Notes
SG7000 working in dual-homing mode.

dual-homing mode.
After M3UA associations are activated through ACT M3ASSO, perform the following steps to
check whether the configuration is correct:
l Use DSP MULM3ASSO to check the associations. Make sure that the active associations
are enabled and the standby ones are disabled.
l Use DSP SCTPASSOC2 to check the status of the SCTP associations.
l Set SX_A to faulty status. Make sure that all links to SX_B are enabled.
l Set links to self-loop mode and trace MTP messages. Make sure that the links work
normally.
l Send test messages to the peer office and trace the messages. Make sure that the links work
normally.
3.3.2 Notes
SG7000 working in dual-homing mode.
Note the following when configuring M3UA associations:
table.
l In configuring the M3UA application server on the SG, the value of Routing context should
be consistent with that configured on the application server.
l Correctly configure the client or server mode and ASP or SGP mode at both sides.
l Negotiate before configuring the interconnection data for the ports at both sides.
l Acting as the signaling gateway, the SG7000 cannot activate or deactivate a link. Instead,
the SoftX3000 conducts this operation.
Note the following when configuring MTP links:
realized.
l In adding the semi-permanent connection, the E1 port number must be consistent with the
number of the physical cable. The occupied timeslots at both ends of a link must be

Configuration Examples 4 Configuring SG7000 in STP Mode
4 Configuring SG7000 in STP Mode
About This Chapter
When used as an independent signaling transfer point (STP) in the PSTN, the SG7000 processes
and transfers SS7 messages only.
generated.

4 Configuring SG7000 in STP Mode Configuration Examples
4.1 Overview
When used as an independent signaling transfer point (STP) in the PSTN, the SG7000processes
and transfers SS7 messages only. It provides all functions of a traditional STP.
This section describes the procedures for configuring the SG7000 acting as the narrowband STP

This section describes the configuration check after the narrowband STP data is configured, and
the solutions for command problems.

4.1 Overview
When used as an independent signaling transfer point (STP) in the PSTN, the SG7000processes
and transfers SS7 messages only. It provides all functions of a traditional STP.
This section introduces the networking structure in which the SG7000 acts as the narrowband
STP to interconnect with the STP and the softswitch.
This section describes the data planning of the SG7000 acting as the narrowband STP.
This section describes the configuration of the interworking data on the SG7000 acting as the
narrowband STP. The interworking data must be configured under the negotiations with the peer
side.

This section introduces the networking structure in which the SG7000 acts as the narrowband
STP to interconnect with the STP and the softswitch.
As shown in Figure 4-2, a pair of SGs is configured in the mutual-backup mode. SG7000_A is
used as the active STP and SG_B the standby one. Similarly, a pair of STPs is configured in the
active and standby mode. The link between the two SGs or two STPs is of C link. SG_A and
SG_B transfer the signaling messages of local exchange A (LE_A) and LE_B.
Figure 4-2 Networking of SG when used as independent STP

This section describes the data planning of the SG7000 acting as the narrowband STP.
Table 4-1 lists the data to be configured on SG_A.

Table 4-1 Data of SG_A

SN. Parameter Value
1 SPC of STP_A A1111A
2 SPC of STP_B A1111B
5 SPC of LE_A A1111E
6 SPC of LE_B A1111F
7 All SP types ITU
For the data to be configured on SG_B, see Table 4-1.

This section describes the configuration of the interworking data on the SG7000 acting as the
narrowband STP. The interworking data must be configured under the negotiations with the peer
side.
The interconnection data, as listed in Table 4-2, is configured after the coordination with the
peer office.

Parameter Value
SG_A Peer Office
SLC of MTP 0-9 0-9
Port and timeslot of LS1 on SG_A Timeslot 1, port Timeslot 1 of

0, and slot corresponding
0Timeslot 1, port trunk
0, and slot 1

0, and slot 3

1, and slot 1

Parameter Value
SG_A Peer Office

1, and slot 3

2, and slot 1
For the data to be configured on SG_B, see Table 4-2.

This section describes the procedures for configuring the SG7000 acting as the narrowband STP
This section describes the general procedures for configuring the narrowband STP after the
hardware data and local office data are configured.
This section details the configuration of the narrowband STP. It also introduces the related
commands along with configuration examples based on the preceding data planning.

This section describes the general procedures for configuring the narrowband STP after the
hardware data and local office data are configured.
For details, see 1 Configuring Hardware and Local Office Data.
1 DSP ADD N7DSP
2 Link set and route ADD N7LKS

ADD N7RT
3 Semi-permanent connection and ADD TDMCONN

MTP link ADD N7LNK


This section details the configuration of the narrowband STP. It also introduces the related
commands along with configuration examples based on the preceding data planning.
Context
on SG_B.
Procedure
Step 1 DSP
To add DSPs for STP_A, STP_B, LE_A and LE_B, set STP to TRUE, and SCCP function to
Without SCCP function, Adjacent flag to TRUE, and Route selection field to 0. Keep the
values of other parameters unchanged.
ADD N7DSP: DESC="STP_A", NPC="A1111A", STP=TRUE, APF=TRUE, SCCPUSED=NONE;
ADD N7DSP: DESC="STP_B", NPC="A1111B", STP=TRUE, APF=TRUE, SCCPUSED=NONE;
ADD N7DSP: DESC="LE_A", NPC="A1111E", STP=FALSE, APF=TRUE, SCCPUSED=NONE;
ADD N7DSP: DESC="LE_B", NPC="A1111F", STP=FALSE, APF=TRUE, SCCPUSED=NONE;
ADD N7DSP: DESC="SG_B", NPC="A1111D", STP=TRUE, APF=TRUE, SCCPUSED=NONE;
Step 2 Link Set and Route

1. To add MTP link sets
set Link selection field to 1 because there are two links in each link set. Set Link set
title of STP_A to LS1, of STP_B to LS3, of LE_A to LS6, LE_B to LS7 and of SG_B to
LS5.
2. To add MTP route
Add MTP routes based on created MTP DSP and the indexes obtained in adding MTP link
sets.
Set higher priority for direct routes.
ADD N7RT: DESC="TO STP_A", LSX=0, DPX=0 , PR=0;
ADD N7RT: DESC="TO STP_B", LSX=1, DPX=1 , PR=0;
ADD N7RT: DESC="TO LE_A", LSX=2, DPX=2, PR=0;
ADD N7RT: DESC="TO LE_B", LSX=3, DPX=3, PR=0;
Set lower priority for routes directing to the DSP over C links.

ADD N7RT: DESC="TO STP_A", LSX=4, DPX=0 , PR=1;

ADD N7RT: DESC="TO STP_B", LSX=4, DPX=1 , PR=1;
Step 3 Semi-Permanent Connection and MTP Link

Set up two semi-permanent connections for LS1, LS3, LS6, LS7 and LS5 respectively on
SEPUs in slots 0-3. Set SPC attribute to Signaling timeslot connection. Set up MTP links
together with the SLPUs in the same slots as the SEPUs. The indexes 0-9 are obtained after
the command is executed.
2. Add MTP links.
Add two MTP links on LS1, LS3, LS6, LS7 and LS5 respectively. The links are numbered
0-9. TDM SPC index maps the index obtained after ADD TDMCONN is executed.
----End


This section describes the configuration check after the narrowband STP data is configured, and
the solutions for command problems.
This section describes the correctness check of the data configured for the narrowband STP.
4.3.2 Notes
narrowband STP.

This section describes the correctness check of the data configured for the narrowband STP.
Perform the following steps to check the configuration:
l Use DSP N7LNK or DSP MULN7LNK to query the status of the links.
l Set links to self-loop mode and trace MTP messages. Make sure that the links work
normally.
l Send test messages to the peer office and trace the messages. Make sure that the links work
normally.
4.3.2 Notes
narrowband STP.
Note the following during configuration:
realized.
l The DPC configured in a local office should be the same as the OPC configured in its peer
office.
l The signaling link codes at both sides of the link should be consistent; otherwise, the link
cannot be set up.

Configuration Examples 5 Configuring SG7000 in Agent Mode
5 Configuring SG7000 in Agent Mode
About This Chapter
The SG7000 uses complete SIGTRAN and SS7 protocols to implement the interworking
between the broadband signaling and narrowband signaling. Working in the agent mode, the
SG7000 uses the M3UA protocol to interconnect with the softswitch and the MTP link to
interconnect with the STP. The SG7000 shares a signaling point code (SPC) with the softswitch.
generated.

5 Configuring SG7000 in Agent Mode Configuration Examples
5.1 Overview
This section describes the data configuration on the SG7000 working in agent mode. It also
introduces the networking structure and the planning of the SG7000 data and the interworking
data.
This section describes the general procedures for configuring the SG7000 working in agent mode



5.1 Overview
This section describes the data configuration on the SG7000 working in agent mode. It also
introduces the networking structure and the planning of the SG7000 data and the interworking
data.
STP and the switch in agent mode.
This section describes the data planning of the SG7000 working in agent mode.
This section describes the configuration of the interworking data on the SG7000 working in
agent mode. The interworking data must be configured under the negotiations with the peer side.

STP and the switch in agent mode.
As shown in Figure 5-2, the SG_A is interconnected with the SX_A and SX_B through the
M3UA protocol at the broadband side, and with both the STPs through the No.7 protocol at the
narrowband side. The SG7000 uses the same signaling point code (SPC) with the softswitch.
Figure 5-2 Networking of SG7000 in agent mode

On SX_A, two SBPIs have the different IP address. They work in the load sharing mode. Four
M3UA associations should be set up on four SBPUs/SBPEs, with each association for each
board, to share the load. The link priority is set to 0.
On SX_B, four M3UA associations should be set up on four SBPUs/SBPEs, and they are
connected with SX_B. The link priority is set to 1.
On STP_A, one semi-permanent link is configured on each of the four SEPUs, and one MTP
link on each of the four SLPUs. Four links of a same kind take the load sharing mode.
On STP_B, the configuration is the same as that on STP_A.

This section describes the data planning of the SG7000 working in agent mode.
Table 5-1 lists the data to be configured in the local office.

S Parameter Value
N.
3 IP address of SG_A 10.0.1.10 (interworking with

active softswitch in the same
network range)/255.255.255.0
4 Port number of SG_A 2905/2906/2907/2908/2909/29

10/2911/2912
5 SPC of SG_A 000111 (international)/ 000555

(national)
6 SPC of SX_A 000111 (international)/ 000555

(national)
7 SPC of SX_B 000111 (international)/ 000555

(national)

This section describes the configuration of the interworking data on the SG7000 working in
agent mode. The interworking data must be configured under the negotiations with the peer side.
The interconnection data, as listed in Table 5-2, is configured after the negotiation with the peer
office.


Parameter Value
SG_A SX_A STP

adding M3UA
application server


M3UA association
IP address of SX_A - 10.0.1.20/255.255. -

255.0
Port number of SX_A - 2905/2906/2907/29 -

08
IP address of SX_B - 10.0.1.30/ -

255.255.255.0
Port number of SX_B - 2909/2910/2911/29 -

12
SPC of ISTP_A - - 000222
SPC of ISTP_B - - 000333
ISTP signaling point type - - ITU

This section describes the general procedures for configuring the SG7000 working in agent mode
This chapter focuses on the configuration of the SG7000 in the agent mode. Ensure that the
hardware data and local office data has been configured.
This section details the configuration of the SG7000 working in agent mode. It also introduces

This chapter focuses on the configuration of the SG7000 in the agent mode. Ensure that the
hardware data and local office data has been configured.


IPDACL to configure the local IP address combination,
remote IP address, IP address combination and add them
to the Access control table. (The local IP address has
been configured in hardware data configuration.)
2 Logical network Run MOD LNto configure a logical network.Set

configuration International network to 14 digits and National
network to 24 digits.Run ADD LN to add a logical
network.Set National network to 24 digits.Run ADD
LN to add a logical network.Set International
network to 14 digits.
3 M3UA destination entity Configure the local SPC and application server with the
following commands:
l SET OFI
l ADD OPC
l ADD OPC
l ADD M3AS
4 M3UA association set Configure M3UA association set and M3UA route with
and M3UA route the following commands:
l ADD M3ASSOS
l ADD M3RT

association.
STP_A and STP_B.
7 MTP link set and MTP Configure the MTP link set and MTP route with the
route following commands:
l ADD N7LKS
l ADD N7RT
8 MTP link Configure the semi-permanent connection and MTP

link with the following commands:
l ADD TDMCONN
l ADD N7LNK

This section details the configuration of the SG7000 working in agent mode. It also introduces

Context
NOTE
he index returned during the configuration is likely to be used in the subsequent configuration, so you need
to record the configuration information and its corresponding index.
Proceed as follows to configure SG_A.
Procedure
Step 1 IP Address
When adding a local IP address, configure the SG7000 by referring to softswitch configuration.
execution of ADD LIP.
ADD LIPC: DESC="SGC", FEX1=0; (The index 0 is obtained.)
2. Add a remote IP address. The index 0 is obtained.
ADD RIP: DESC="SX_A", RIP="10.0.1.20"; (The index 0 is obtained.)
ADD RIP: DESC="SX_B", RIP="10.0.1.30"; (The index 1 is obtained.)
3. Add the above IP address to the Remote IP address combination table.
ADD RIPC: DESC="SX_A", RIPX1=0; (The index 0 is obtained.)
ADD RIPC: DESC="SX_B", RIPX1=1; (The index 1 is obtained.)
4. Add the remote IP address to the IPDACL table.
ADD IPDACL: DESC="SX_A",IP="10.0.1.20";
ADD IPDACL: DESC="SX_B",IP="10.0.1.30";
Step 2 Logical Network Configuration
Run MOD LN to modify a logical network configuration.

MOD LN: IDX=0, INS=SP14, NNS=SP24;
Run ADD LN to add a logical network configuration.

ADD LN: NNS=SP24; (The index 1 is obtained.)
ADD LN: INS=SP14; (The index 2 is obtained.)

1. Because both National network code and International network code are contained, set
the former to 000111, the latter to 000555, STP to FALSE, and SCCP function to Without
SCCP function. Keep the values of other parameters unchanged.
SET OFI: IPC="000AAA", NPC="000BBB", SCCP=FALSE; (The OPC index is 0.)
(The SPC can be set according to the planning.)
ADD OPC: NPC="000555", LNI=1; (The index 1 is obtained.)
ADD OPC: IPC="000111", LNI=2; (The index 2 is obtained.)
2. To add an M3UA application server, set Network indication to National
network,Routing context to 1234. You do not need to configure Association set select
mask code because there is only one route.
Note that Destination point code index uses the index of the local SPC.
ADD M3AS: DESC="SX-N", NI=NM, SWM=AM, DPCX=1, RC=1234; (The index 0 is
obtained.)
ADD M3AS: DESC="SX-I", NI=IM, SWM=AM, DPCX=2, RC=4567; (The index 1 is
obtained.)


1. To add an M3UA association set, set Traffic mode to Load-share mode, and Association
select mask code to 7because there are eight links in this association set.
ADD M3ASSOS: DESC="SX-N", ASX=0, ASC=7 , TM=LOADSHARE, WM=SGP; (The
index 0 is obtained.)
ADD M3ASSOS: DESC="SX-I", ASX=1, ASC=7 , TM=LOADSHARE, WM=SGP; (The
index 1 is obtained.)
2. Add an M3UA route. The indexes for Application server index and Association set
index are those returned after the execution of ADD M3AS and ADD M3ASSOS.
ADD M3RT: DESC="SX", ASX=0, ASSX=0;
ADD M3RT: DESC="SX", ASX=1, ASSX=1;
NOTE
The M2UA, M3UA, IUA and M2PA protocols are transmitted based on SCTP. For easy management, you need
to arrange the local SCTP port numbers for each link before data configuration. Try not to use the same port
number repeatedly.

To add an M3UA association, set Board Assoc. number to 0, Local port and Remote port to
2905, Priority to 0, Connection to Load-share mode, C/S mode to Server side, and
Active_Standby flag to Active initially. Keep the values of other parameters unchanged.
1. The link configuration to SX_A is listed as follows:
ADD M3ASSO: SN=0, FN=0, BN=0, PLNO=0, DESC="SG_SXA_N1", LIPCX=0,
LP=2905, RIPCX=0, RP=2905, CS=S, ASSI=0, ASF=YES, PRI=0;
ADD M3ASSO: SN=0, FN=0, BN=1, PLNO=0, DESC="SG_SXA_N2", LIPCX=0,
ADD M3ASSO: SN=0, FN=0, BN=2, PLNO=0, DESC="SG_SXA_I1", LIPCX=0,
ADD M3ASSO: SN=0, FN=0, BN=3, PLNO=0, DESC="SG_SXA_I2", LIPCX=0,
2. The link configuration to SX_A is listed as follows:
ADD M3ASSO: SN=0, FN=0, BN=0, PLNO=1, DESC="SG_SXB_N1", LIPCX=0,
ADD M3ASSO: SN=0, FN=0, BN=1, PLNO=1, DESC="SG_SXB_N2", LIPCX=0,
ADD M3ASSO: SN=0, FN=0, BN=2, PLNO=1, DESC="SG_SXB_I1", LIPCX=0,
ADD M3ASSO: SN=0, FN=0, BN=3, PLNO=1, DESC="SG_SXB_I2", LIPCX=0,
Step 6 MTP DSP

function, Adjacent flag to TRUE, and Route selection field to 1. Keep the values of other
ADD N7DSP: DESC="STP_A",NPC="000222",STP=TRUE,APF=TRUE, SLS=8,
SCCPUSED=NONE, LNI=1; (The index 1 is obtained after the command is
executed.) (national network)
ADD N7DSP: DESC="STP_B",NPC="000333",STP=TRUE,APF=TRUE, SLS=8,
SCCPUSED=NONE, LNI=2; (The index 2 is obtained after the command is
executed.) (national network)

1. To add MTP link sets, set Link selection field to 3 because there are four links in each link
set, Link set title of STP_A to LS0, and Link set title of STP_B to LS1.


ADD N7LKS: DESC="LS1", APX=2, OFX=2, NI=IM, SLS=3; (The index 1 is
2. Add MTP routes.
ADD N7RT: DESC="TO STP_A", LSX=0, DPX=1, PR=0, TX=0;
ADD N7RT: DESC="TO STP_B", LSX=1, DPX=2, PR=0, TX=0;
Step 8 MTP Link

Set up eight semi-permanent connections on the boards from slots 0 to 3 respectively and
set SPC attribute to Signaling timeslot connection. Set up MTP links together with the
SLPUs in the same slots. The indexes 0-7 are obtained after the commands are executed.
2. Add four MTP links on LS0 of STP_A and LS1 of STP_B respectively. The links are
numbered 0-3.
For STP_A:
For STP_B:
----End


agent mode.
5.3.2 Notes
SG7000 working in agent mode.
This section describes the principles you must follow when configuring the SG7000 working in
agent mode, including "M3UA route select mask code" and "M3UA association select mask
code".

agent mode.
Check M3UA Association

After M3UA associations are activated through ACT M3ASSO, proceed as follows to check
whether the configuration is correct:
l Use DSP MULM3AS to check the status of the application server.

l Use DSP MULM3ASSOS to check the status of the association set.
l Use DSP MULM3RT to check the status of the route.
l Use DSP MULM3ASSO to check the status of the association.
l Use DSP SCTPASSOC2 to check the status of the SCTP association.
Check MTP Link

Use the following commands to check the status of the MTP link set, MTP link, MTP route and
MTP DSP.
l DSP MULN7LNK
l DSP MULN7LKS
l DSP MULN7RT
l DSP MULN7DSP
5.3.2 Notes
SG7000 working in agent mode.

Notes in Configuring M3UA Association

table.
l In configuring the M3UA application server on the SG, the value of Routing context should
be consistent with that configured on the application server.
l Correctly configure the client or server mode and ASP or SGP mode at both sides.
l Negotiate before configuring the interconnection data for the ports at both sides.
Notes in Configuring MTP Link

realized.

This section describes the principles you must follow when configuring the SG7000 working in
agent mode, including "M3UA route select mask code" and "M3UA association select mask
code".
M3UA Route Select Mask Code

To achieve balance of the traffic to a specific application server, a certain algorithm must be
defined to distribute the traffic over different routes. In the SG7000, the route select mask code
participates in the algorithm for load sharing of the traffic. The value is a decimal value of 4-bit
binary number. For example, the route select mask code is 1001 and the corresponding decimal
value is 9. The default value of this parameter is 0.
l Set all bits to 0 if there is only one M3UA route.
l Set one bit to 1 if there are two M3UA routes.
l Set two bits to 1 if there are three or four M3UA routes.
l Set three bits to 1 if there are five to eight M3UA routes.
l Set all four bits to 1 if there are more than eight routes.
l Do not set the route select mask code the same as the association select mask code of each
association set to avoid the system always selecting the same route. It is recommended to
stagger the places of "1" in the two mask codes. For example, if the route select mask code
is 0110, the association select mask code can be set to 1001.
M3UA Association Select Mask Code

It indicates how to distribute the traffic load over several M3UA links to the same M3UA
application server. In fact, the value of this filed is the load sharing mask. The value is a decimal
value of a 4-bit binary number. For example, for the link select mask code 1001, the
corresponding decimal value is 9. The default value of this parameter is 0.

l Set all bits to 0 if there is only one M3UA association.

l Set one bit to 1 if there are two M3UA associations.
l Set two bits to 1 if there are three or four M3UA associations.
l Set three bits to 1 if there are five to eight M3UA associations.
l Set all four bits to 1 if there are more than eight associations.
l Do not set the route select mask code and this parameter to the same value to avoid the
system always selecting the same route. It is recommended to stagger the places of "1" of
the two mask codes. For example, if the route select mask code is 0110, the link select mask
code can be set to 1001.
MTP Route Selection Field

routes to the DSP. The value is an 8-bit binary number and it ranges from 0 to 255. The default
value is 0.
The configuration principle of the parameter is as follows:
l When there is only one route between the SG7000 and the DSP, set Route Selection
Field to 0, which is the default value.
l When there are two or more MTP routes, the decimal value of Route Selection Field should
be no smaller than the number of total link sets minus 1.
l Try to use the upper four bits of the route selection field, and thus all the MTP links in the
same link set sent to different non-adjacent signaling points can be selected to share the
signaling traffic load.
MTP Link Selection Field

links in a signaling link set. In fact, the value of this filed is the load sharing mask. The value is
a decimal value of a 4-bit binary number and it ranges from 1 to 15. The default value is 0.
l When there is only one link in a link set, set all bits of Field Selection Field to 0, which is
the default value.
l Set one bit to 1 if there are two MTP routes.
l Set two bits to 1 if there are three or four MTP links.
l Set three bits to 1 if there are five to eight MTP links.
l Set all four bits to 1 if there are more than eight MTP links.


SG7000 Configuration Examples (V200R005C02 - 02)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SG7000 Configuration Examples (V200R005C02 - 02)

Uploaded by

Copyright:

Available Formats

U-SYS SG7000 Signaling Gateway

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2009-12-14) Huawei Proprietary and Confidential i

About This Document

Product Name Version

U-SYS SG7000 V200R005C02

Issue 02 (2009-12-14) Huawei Proprietary and Confidential iii

3 Configuring SG in Details the data configuration steps and commissioning guide

4 Configuring SG7000 in Introduces the data configuration steps and commissioning

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

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

Indicates a potentially hazardous situation that, if not

NOTE Provides additional information to emphasize or

Times New Roman Normal paragraphs are in Times New Roman.

Italic Book titles are in italics.

iv Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italic.

[] Items (keywords or arguments) in square brackets [ ] are

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

[ x | y | ... ] Optional alternative items are grouped in square brackets

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

Issue 02 (2009-12-14) Huawei Proprietary and Confidential v

Updates in Issue 02 (2009-12-14)

Updates in Issue 01 (2009-09-27)

vi Huawei Proprietary and Confidential Issue 02 (2009-12-14)

About This Document...................................................................................................................iii

2 Configuring SG7000 in Signaling Transfer Mode...............................................................2-1

3 Configuring SG in Dual-Homing Environment..................................................................3-1

Issue 02 (2009-12-14) Huawei Proprietary and Confidential vii

3.3.1 Configuration Check ...........................................................................................................................3-12

4 Configuring SG7000 in STP Mode.........................................................................................4-1

5 Configuring SG7000 in Agent Mode......................................................................................5-1

viii Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Figure 1-1 Data configuration procedure.............................................................................................................1-2

Issue 02 (2009-12-14) Huawei Proprietary and Confidential ix

Table 1-1 Hardware data collection......................................................................................................................1-5

Issue 02 (2009-12-14) Huawei Proprietary and Confidential xi

1 Configuring Hardware and Local Office

About This Chapter

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 1-1

Figure 1-1 Data configuration procedure

1.1 Configuration Overview

1-2 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Issue 02 (2009-12-14) Huawei Proprietary and Confidential 1-3

1.1 Configuration Overview

1.1.1 Configuring Hardware Data

Figure 1-2 Boards configuration

1-4 Huawei Proprietary and Confidential Issue 02 (2009-12-14)

Table 1-1 Hardware data collection

Cabinet No./Frame No./Cabinet 0/0/Main control frame

Table 1-2 Basic information of main boards

0/0 Front SBPU -

0/0 Back SEPU -

0/1 Front SBPU -

0/1 Back SEPU -

0/2 Front SBPU -

0/2 Back SEPU -

0/3 Front SBPU -

0/3 Back SEPU -

0/4 Front SBPI -