Professional Documents
Culture Documents
Training Manual
Basic Data Configuration
ZTE UNIVERSITY
ZTE University, Dameisha
YanTian District, Shenzhen,
P. R. China
518083
Tel: (86) 755 26778800
Fax: (86) 755 26778999
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2010 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of
this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATION
or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the
information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject
matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,
the user of this document shall not acquire any license to the subject matter herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Contents
5 Physical Configuration............................................. 57
5.1 Concepts on Physical Configuration .........................................57
5.2 Adding a Rack ......................................................................59
5.3 Adding a Shelf .....................................................................60
5.4 Adding a Unit .......................................................................61
5.5 Adding a Module...................................................................63
5.6 Configuring TCP Transfer for TIPI ............................................65
5.7 Setting the IP of the OMP module ...........................................67
7 Office Configuration................................................. 73
7.1 Creating Signaling Points of the Local Office .............................73
7.2 Configuring the Local Office ...................................................75
7.3 Adding an Adjacent Office......................................................77
Glossary ....................................................................155
USPP_DC001_E1_0
Context
Steps
Description
Synchronization type
Operate Type
Sync Option
Sync OMM uploads the configuration data on EMS to the OMM network
management system only.
Sync MP uploads the configuration data on EMS to both the OMM
network management system and the foreground MPs.
Parameter
Options
Timeout (100ms)
Description
Save: Whether data are saved at once on each module after the
uploading
Toslave: Whether data are synchronized at once to each backup node
after the uploading
The upload request times out if the front-end processor does not make
any response in this period of time.
Range: 16000, default: 600
OF STEPS
Context
Loading the License file onto the EMS server is to save the License
file into the related folder, so that the License may be validated
later.
Steps
OF STEPS
When the License is loaded, the window is as shown in the following figure.
Postrequisite
Context
Steps
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 2 CREATE USPP PARAMETERS
Parameter
Description
TYPE
USERLABEL
OF STEPS
Context
Steps
10
3. Set the parameters. For details about the parameters, see the
following table.
TABLE 3 PARAMETERS FOR CREATING NE AGENT
Parameter
Basic
Attributes
Description
Name
Vendor
IP Address
Version
Location
Memo
11
Parameter
Extended
Attributes
Description
Port
Set it to 21125.
Protocol Type
Set it to Socket.
FTP Port
Set it to 21.
4. Click OK.
END
Postrequisite
OF STEPS
Context
Steps
Result
12
OF STEPS
After the NE agent has started up, you may see on the Physical View tab the lower topological levels of this NE. And the link
between the EMS and the NE agent displayed on the right pane
of the Topology Management window is green, as shown in the
following figure.
Postrequisite
Context
Updating USPP is to query and get the latest version of the OMM.
Steps
13
OF STEPS
Context
Steps
14
OF STEPS
Context
Steps
15
4. Select the OMM server from the AMO List and click
to move
it to the Preparation synchronized AMO list, and then click
OK.
END
Postrequisite
OF STEPS
16
The license on the OMM has been synchronized with the License
on the EMS.
Context
Steps
Description
Bureau No.
Bureau Type
Vendor
Equipment Vendor
Range: 050 characters
User State
User-defined state
Range: 065535
Position
User Label
OF STEPS
17
Context
Steps
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 5 ADD USPPNE PARAMETERS
Parameter
Description
AMO NAME
BNO
OF STEPS
18
Context
Steps
4. Click the
batch.
19
iv. Confirm that the latest version is what has been uploaded.
END
Postrequisite
20
OF STEPS
Context
This topic describes the procedure to add a database node for the
UDS subsystem. The database node may be for local storage or
transfer. The database node information is required to connect the
database when DSA nodes are starting up.
Steps
21
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 6 ADD DBNODE PARAMETERS
Parameter
Description
DB ID
Database Type
User Name
Password
DB Name
Connection
Service
DB IP
22
Parameter
Description
Slave
Connection
Service 1
Slave DB IP 1
Slave
Connection
Service 2
Slave DB IP 2
DBA Password
SYSTEM
Password
User Label
Note:
To avoid trouble caused by wrong database parameters, it is
recommended that you test the settings using the tools of the
database before adding the database node.
The local Net service of the database need also be configured
on the computers where the UDS node is on.
5. Click the Execute(F5) button or press F5 to execute this command.
END
OF STEPS
23
Postrequisite
Context
Steps
24
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 7 ADD DSANODE PARAMETERS
Parameter
Description
DSA Node ID
Relating
Bureau
Module
Module Type
IP Type
Internal IP
Address
Internal Port
25
Parameter
Description
External IP
Address
External Port
OF STEPS
Context
Steps
26
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 8 SET DSANODEOPT PARAMETERS
Parameter
Description
DSA Node ID
Run
Environment
Small Page
Size (KB)
Small Page
Num
27
Parameter
Description
Server Thread
Num
The total
number of DIR
transaction
data area
The Max
Number of
Received
Message Per
Second
The Max
Number
of Check
Resource
User Label
OF STEPS
Context
Steps
28
2. Select NetNumen > USPP > Device Configuration > Public Device Configuration.
USPP here is a USPP node created by the CREATE USPP command.
3. On the MML commands tree, select MML Commands > UDS
Dev Configuration > DSA Node Configuration > DSA
Node Storage Configuration > Create DSA Node Storage
Configuration (ADD DSANODESAV) to open the command
interface shown in the following figure.
FIGURE 19 ADD DSANODESAV COMMAND INTERFACE
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 9 ADD DSANODESAV PARAMETERS
Parameter
Description
DSA Node ID
Store Type
29
Parameter
Description
File Path
DB ID
Backup Time
Every Day
User Label
OF STEPS
Add DSA.
Context
Steps
30
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 10 ADD DSA PARAMETERS
Parameter
Description
DSA ID
DSA Type
ID DSA
Number Type
Home Bureau
No. 1
Home Bureau
No. 2
The election
mode PDS
31
Parameter
Description
DSA Node ID
of Master DST
User Label
OF STEPS
The Schema has been uploaded, and you have known its version.
Context
Steps
32
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 11 ADD DSACLU PARAMETERS
Parameter
Description
DSA Node ID
DSA ID
Schema
Version
Node Level
Dealing
Message
Capacity
User Label
OF STEPS
33
Context
Steps
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 12 SET DSAOPT PARAMETERS
Parameter
Description
DSA ID
34
Parameter
Description
Durable Flag
For Provision
Durable Policy
Consistent
Policy
User Label
OF STEPS
Context
Steps
35
2. Select NetNumen > USPP > Device Configuration > Public Device Configuration.
USPP here is a USPP node created by the CREATE USPP command.
3. On the MML commands tree, select MML Commands > UDS
Dev Configuration > DSA Configuration > DSA Subscriber Capacity Configuration > Create DSA Subscriber
Capacity Configuration to open the command interface
shown in the following figure.
FIGURE 23 ADD CAPSUB COMMAND INTERFACE
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 13 ADD CAPSUB PARAMETERS
Parameter
Description
DSA ID
Base Table
Name
Capacity
User Label
36
OF STEPS
Context
Steps
4. Set the parameters. For details about the parameters, see the
following table.
37
Description
IDSA ID
IDSA Group ID
User Label
OF STEPS
Context
Steps
38
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 15 ADD IDSAMAP PARAMETERS
Parameter
Description
Serial No.
Number Type
Begin Mapping
Code
End Mapping
Code
DSA ID
User Label
OF STEPS
39
Context
Steps
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 16 ADD DSAGRP PARAMETERS
Parameter
Description
Serial No.
PDSA Group
ID
PDSA ID
40
Parameter
Description
Capacity
Assigned to
Save Data in
the PDSA
User Label
OF STEPS
Context
When the load of the UDS subsystem exceeds the expected value,
the load control module functions according to the load control
configuration.
Before modifying the load control configuration, check and then
modify the current settings if necessary.
Note:
The default settings are recommended. Be cautions and make
sure you really need to modify the load control configuration.
Steps
41
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 17 SET LOADLEV PARAMETERS
Parameter
Description
Load Level
CPU Rate
Only Read
Discard Message
Rate(%)
Only Read
Transferring
Message Rate(%)
Update Discard
Message
Rates(%)
User Label
OF STEPS
42
Context
When the load of the UDS subsystem exceeds the expected value,
the load control module functions according to the load control
configuration.
Before modifying the load control configuration, check and then
modify the current settings if necessary.
Note:
The default settings are recommended. Be cautions and make
sure you really need to modify the UDS parameters.
Steps
43
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 18 SET UDSPARA PARAMETERS
Parameter
Description
Message distribution
policy
44
Parameter
Description
NO: Do not select another SSDS node for
asynchronous replication.
Synch replicate
Reliability Level
45
Parameter
Description
Support Synch
Compression
Intra-Bureau
Concurrent Resume
Limit
Inter-Bureau
Concurrent Resume
Limit
All Concurrent
Resume Limit
Concurrent Resume
Limit In Two Bureaus
User Label
OF STEPS
Context
46
This topic describes the procedure to modify the capacity of a configuration table.
Note:
The default configuration is recommended. Be cautions and make
sure you really need to modify the capacity of the configuration
table.
Steps
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 19 SET CAPCFG PARAMETERS
Parameter
Description
Table ID
Table Size
OF STEPS
47
Context
Note:
The default configuration is recommended. Be cautions and make
sure you really need to modify the capacity ratio of a subscriber
data table.
Steps
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 20 SET CAPSUBSCL PARAMETERS
Parameter
Description
Table ID
Scale
48
OF STEPS
Context
Steps
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 21 ADD DUANODE PARAMETERS
Parameter
Description
DUA Node ID
Relating Bureau
Module
49
Parameter
Description
Module Type
IP Type
Internal IP Address
Internal Port
External IP Address
External Port
User Label
OF STEPS
Context
Steps
50
Description
DMCC ID
UDS System
Including Bureau
No.
GT Address
Code Plan
Module No.
IP Type
Internal IP Address
Internal Port
51
Parameter
Description
External IP Address
External Port
User Label
52
OF STEPS
53
54
Context
The FE subsystem, the UDS subsystem and the Provision Subsystem are working properly.
After data configuration, it is necessary to synchronize the configuration data tables made on the OMM subsystem to DBIO, UDS
subsytem and provision subsystem.
You can synchronize all tables or only the changed tables.
Steps
4. Set the parameters. For details about the parameters, see the
following table.
55
Description
User Name
Sync Type
Module List
Response Timeout
(100ms)
Save When
Completed
56
OF STEPS
ZXUN USPP adopts BCTC shelves. BCTC shelves provide controlstream interconnection for resource shelves and switching shelves.
A BCTC shelf provides 2 or three fast Ethernet (FE) interfaces for
each slot. The following table shows the number of FE interfaces
available for each slot.
Slots 18 and 11, 12, 17 (general slots): For SMP, SPB, USI,
SIPI and TIPI boards
57
Slots 13 and 14 (clock slots): For CLKG boards. Also for the
SMP boards when CLKG boards are not needed.
The following is an example for setting Office ID, Rack No., and
Shelf No.
For Office 3, remove the pins of the left two pins and plug the
third pin, that is, set TRIBID to 110.
For Rack 1, plug all pins, that is, set RACKID to 0000.
For Shelf 2, remove the first pin from the left pin and plug the
second, that is, set SHELFID to 10XX.
Module
Module is a logical concept defined from a view of control. A
module may be a CPU of an OMP board or an SMP board, which
also means that CPUs of OMP or SMP board realize the functions
of modules. There are currently four types of modulesOMP,
SMP, RPU and CMP.
One CPU of an OMP or SMP board may be configured as one or
more modules.
Unit
Unit is a logical concept corresponding to board. Boards of a
same type may be configured as different units as needed. A
physical board may be configured as one unit only.
Boards of 1+1 redundancyfor example, UIMC boardsare
also taken as one unit. Therefore, a unit may correspond to
one or two boards.
Subunit
A subunit is a part of a unit which is relatively independent
in functions and relates to certain physical entities. A subunit
may be an E1 interface, GE interface, CPU or DSP (ASIC).
Every unit should contain one or more CPU subunits. CPU subunits are numbered from 1, while other units are generally
numbered from 9.
Besides CPU subunits, a unit may also contain DSP, ASIC, E1,
GE, FE, or FPGA subunits.
58
Context
The OMM system is correctly configured and connected according to the network planning.
The NE is created.
This topic describes the procedure to add a logical rack corresponding to the physical rack.
Note:
After an office is added, rack 1 is created automatically. You can
add a rack when necessary. For example, you can add a rack after
the rack deletion operations.
Steps
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 24 ADD RACK PARAMETERS
Parameter
Description
Rack No.
Rack Type
Alias
59
OF STEPS
Add shelves.
Context
Steps
Description
Rack No.
Shelf No.
60
Parameter
Description
Shelf Type
Shelf Version
Alias
OF STEPS
Context
The OMM system is correctly configured and connected according to the network planning.
This topic describes the procedure to add units such as UIMC, SPB
(for E1 access), SIPI (for IP access), HSL (for ATM access), USI(
when there is only one physical office) or TIPI (for intra-office or
inter-office communication, or both).
The sequence to create units and modules is as follows.
1. Add the UIMC unit.
2. Add modules other than OMP and RPU.
3. Add units other than UIMC.
Steps
61
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 26 ADD UNIT PARAMETERS
Parameter
Description
Unit Location
Module No.
Unit No.
Unit Type
62
Parameter
Description
Backup Mode
Backup Unit
E1/T1 Attribute
Channel Mode
Alias
OF STEPS
Context
Steps
63
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 27 ADD MODULE PARAMETERS
Parameter
Description
Location
Module No.
Module 1 Type
Module 2 Type
CPU Type
Backup Mode
64
Module 1 User
Alias
Module 2 User
Alias
OF STEPS
Add units other than UMIC with the ADD UNIT command.
Context
The OMM system is correctly configured and connected according to the network planning.
The Local Office Distribute Style option in global data configuration is set to SIPI.
Each module needs two IP addresses, one for internal use and
the other for external use.
Each internal IP address needs one entry, IP address + serverend internal port number.
The server-end internal port number should be 60000 + module number (1127).
Steps
65
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 28 ADD TCPTRANS PARAMETERS
Parameter
Description
ID
Module
IP Address Type
VPN ID
IP Address
Port
Alias
66
OF STEPS
Add service nodes, including the DBIO, DSA (if deployed on FE)
and DST by using the ADD BACKSVR command. Refer to topic
6.1 for details.
The OMM system is correctly configured and connected according to the network planning.
Context
Steps
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 29 SET OMP PARAMETERS
Parameter
Description
OMP Background ip
address
OMP Background ip
mask
OMP to OMC
GATEWAY
OMC SERVER
SUBNETWORK
67
68
OF STEPS
Context
The OMM system is correctly configured and connected according to the network planning.
Steps
4. Set the parameters. For details about the parameters, see the
following table.
69
Description
Module No.
Module Type
IP Address
Alias
OF STEPS
Add the connection between the service server node and the OMM
network management system.
The OMM system is correctly configured and connected according to the network planning.
Context
This topic describes the procedure to establish the connection between the a service node and the OMM so that the service node
may communicate with the OMM. Service nodes include DBIO, DSA
(when deployed in a server cabinet), and DST.
Steps
70
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 31 ADD HSERV PARAMETERS
Parameter
Description
User Label
OF STEPS
71
72
The OMM system is correctly configured and connected according to the network planning.
Context
Steps
73
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 32 ADD OPC PARAMETERS
Parameter
Description
Network Type
Alias
Area Code
Signaling Point
Code Format
14 bit Signaling
Point Code
74
Parameter
Description
24 bit Signaling
Point Code
Application Type
Dialing Prefix
Network
Appearance
Info
Other Attribute
Work Domain
Index
Range: 0255
The default value (0) is recommended.
OF STEPS
You have logged in to the OMM client and has the right to perform equipment configuration.
The OMM system is correctly configured and connected according to the network planning.
Context
Steps
75
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 33 ADD LOFC PARAMETERS
Parameter
Description
76
Network Type
Sequence In Area
Test Code
Local Office
Language
Reset Time(ms)
Parameter
Description
Signaling Point
Restart
Alias
OF STEPS
Context
Steps
The OMM system is correctly configured and connected according to the network planning.
77
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 34 ADD ADJOFC PARAMETERS
Parameter
Description
Office ID
Alias
78
Parameter
Description
Network Type
Office Type
Signaling Point
Code Format
Signaling Point
Code Type
Signaling Point
Code
Area Code
Association Type
Signaling Point
Type
Subservice
Function
Office Attribute
79
Parameter
Description
Subprotocol
Type
Test Flag
Broadband
Attribute
Domain Type
Protocol Type
Cluster ID
Receive CGN
Extend Info
Office Info
Related Office ID
Office Extend
Info
80
OF STEPS
If the ATM over E1 access mode is used, perform HSL connection configuration. (See topic .)
81
82
You have logged in to the OMM client and has the right to perform equipment configuration.
The OMM system is correctly configured and connected according to the network planning.
Context
Steps
83
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 35 ADD SCTPCONN PARAMETERS
84
Parameter
Description
Module No.
Remote Office ID
Bearer Protocol
Type
Parameter
Description
Application
Attribute
Local IP
Local Port
Remote IP
Remote Port
Alias
SCTP ID
MGW Remote
MSCS ID
Quantity Of
In-stream
Quantity Of
Out-stream
85
86
Parameter
Description
Maximum Value
Of RTO (10ms)
Minimum Value
Of RTO (10ms)
Initial Value Of
RTO (10ms)
Heartbeat
Interval (10ms)
Maximum Burst
Data Packet
Primary Path
OF STEPS
Configure ASPs.
You have logged in to the OMM client and has the right to perform equipment configuration.
The OMM system is correctly configured and connected according to the network planning.
Context
Steps
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 36 ADD ASP PARAMETERS
Parameter
Description
SCTP ID
Alias
ASP ID
87
Parameter
Description
Self-loop Flag
Locked Flag
OF STEPS
Configure ASs.
8.1.3 Adding an AS
Prerequisites
You have logged in to the OMM client and has the right to perform equipment configuration.
The OMM system is correctly configured and connected according to the network planning.
Context
Steps
88
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 37 ADD AS COMMAND PARAMETERS
Parameter
Description
Adaptation Layer
Protocol
ASP
Alias
AS ID
If Routing Context
exists
Routing Context ID
89
Parameter
Description
Usage Tag
User Type
Subsystem Types
No need to configure.
Service Mode
OF STEPS
90
You have logged in to the OMM client and has the right to perform equipment configuration.
The OMM system is correctly configured and connected according to the network planning.
Context
Steps
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 38 ADD M3UART PARAMETERS
Parameter
Description
M3UA Static
Route ID
AS ID
Route Array
Mode
Alias
OF STEPS
91
Context
The OMM system is correctly configured and connected according to the network planning.
SIO is the abbreviation of Service Information Octet, which identifies which protocols such as ISUP, SCCP, BICC and so on are
used on M3UA. Configuring SIO location AS is to locate a service
to M3UA static route. This configuration item describes the routing
information of signaling message. That is, When receiving a signaling message, the product determines to which AS the message
should be sent according to the network type, destination signaling point code, source signaling point code and service indicator.
This topic describes the procedure to add an SIO location AS for
IP-access mode.
Steps
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 39 ADD SIOLOCAS PARAMETERS
92
Parameter
Description
SIO Locate AS ID
Alias
Parameter
Description
Service Indication
Destination Office
ID
Origination Office
ID
OF STEPS
The OMM system is correctly configured and connected according to the network planning.
93
The office configuration (TDM access mode ) or ATM PVC configuration ("ATM over E1" access mode) is complete.
Context
Steps
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 40 ADD N7LKS PARAMETERS
Parameter
Description
Office ID
Linkset Type
94
Parameter
Description
the signaling link set based on IP connection,
select "M2PA Link Set". For the signaling link
set to ZXUN USPP, "64K Narrowband Link Set"
is selected.
This parameter must be consistent at the two
ends.
Linkset ID
Link Error
Revision
Alias
OF STEPS
Adding the E1/T1 signaling link when the TDM access mode is
used. This manual takes the E1 as an example.
Adding the ATM signaling link when the "ATM over E1" access
mode is used.
95
The OMM system is correctly configured and connected according to the network planning.
Context
Signaling links refer to signaling channels between two offices, including narrowband signaling links and broadband signaling links.
ZXUN USPP only has narrowband signaling links. This topic describes the procedure to create signaling links with E1 bearer type.
Steps
1. Click Views > Terminal on the menubar of the NetNumen(TM) M30 interface to enter the Terminal interface.
2. Select the current working office node under root.
3. On the MML commands navigation tree, select MML Commands > Signal Configuration > MTP Data Configuration
> Signaling Link Configuration > Create SPB Signaling
Link (ADD N7LNKE1) to open the interface as shown in the
following figure.
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 41 ADD N7LNKE1 PARAMETERS
Parameter
Description
Linkset ID
96
Parameter
Description
Alias
Link No.
SPB CPU
SPB E1
SPB E1 Timeslot
Start
SPB E1 Timeslot
Amount
SLC
Self Loop
Link Info
FCPL Threshold(ERL)
OF STEPS
97
Context
The OMM system is correctly configured and connected according to the network planning.
Steps
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 42 ADD N7ROUTE PARAMETERS
Parameter
Description
Alias
Linkset1 ID
98
Parameter
Description
Linkset2 ID
Signaling Route ID
99
Parameter
Description
Sort Manually
Link List
OF STEPS
Context
The OMM system is correctly configured and connected according to the network planning.
Steps
100
1. Click Views > Terminal from the menu bar of the NetNumen(TM) M30 main window.
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 43 ADD N7OFC PARAMETERS
Parameter
Description
Signaling Office ID
Direct Route ID
Alias
OF STEPS
101
Context
102
The OMM system is correctly configured and connected according to the network planning.
The configuration of SIO location AS (connection with the adjacent office in IP access mode ) or signaling office configuration
(connection with the adjacent office in TDM or "ATM over E1"
access mode) is complete.
Steps
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 44 ADD GTT PARAMETERS
Parameter
GT Type
Description
Range: 1-4
103
Parameter
Description
Numbering Plan
Nature
GT TransSelector ID
Country Code
Domestic Shortest
Bit
Domestic Longest
Bit
GT Translate
Property
Support Calling GT
Prefix
Alias
104
OF STEPS
The OMM system is correctly configured and connected according to the network planning.
Context
Steps
105
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 45 ADD GT PARAMETERS
Parameter
Description
Called GT
Calling GT
106
Parameter
Description
GT TransSelector
ID
GTDI
1st OFC-Turn
Times List
Office Group
Support
2nd OFC-Turn
Times List
3rd OFC-Turn
Times List
4th OFC-Turn
Times List
SSN
New GT
New GT Translator
Type
Routing Mode
New GT Attribute
107
Parameter
Description
MAP Stage
Virtual GT Support
TT Translation
Service Type
Alias
108
OF STEPS
109
110
Context
The user has logged in to the OMM client and has the right to
perform data configuration.
The OMM system is correctly configured and connected according to the network planning.
The connection between the OMM network management system and the OMP module is normal.
Steps
111
OF STEPS
If the IP addresses are not correct, configure the loopback interface or entering interface configuration mode to configure the interface addresses. Refer to topic 9.2 for procedures to configure
the interface IP address or topic 9.3 for procedures to configure
the loopback interface address.
If the IP addresses are correct, configure the interface group if
necessary. Refer to topic 9.5 for details.
112
The user has logged in to the OMM client and has the right to
perform data configuration.
The OMM system is correctly configured and connected according to the network planning.
The connection between the OMM network management system and the OMP module is normal.
Context
Only when you have entered the interface configuration mode can
you configure on line the interfaces of IP stack for SIPI board and
TIPI board.
Steps
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 46 INTERFACE PARAMETERS
Parameter
Description
Sub-System
Module
Unit
113
Parameter
Description
Sub-Unit
Subunit No.
Set it to 1.
Port
Port No.
The port No. of the external network interface
on the SIPI or TIPI rear board. Altogether four
interfaces, numbered 14 respectively from up
to down
OF STEPS
The user has logged in to the OMM client and has the right to
perform data configuration.
The OMM system is correctly configured and connected according to the network planning.
The connection between the OMM network management system and the OMP module is normal.
Context
Steps
114
4. Set the parameter. For details about the parameter, see the
following table.
TABLE 47 INTERFACE LOOPBACK PARAMETERS
Parameter
Description
Port
OF STEPS
Context
When IP-mode inter-connection is adopted, you need on line configure actual interfaces for SIPI boards, TIPI boards and the RPU
module. This topic describes the procedure to configure an IP address.
Steps
115
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 48 ADD IP ADDRESS PARAMETERS
Parameter
Description
IP
IP address
Set according to your networking plan.
Subnet Mask
Subnet Mask
Set according to your networking plan.
Broadcast
Address
CORBA ID
116
OF STEPS
Result
Postrequisite
Context
The user has logged in to the OMM client and has the right to
perform data configuration.
The OMM system is correctly configured and connected according to the network planning.
The connection between the OMM network management system and the OMP module is normal.
Steps
117
4. Set the parameters. For details about the parameters, see the
following table.
TABLE 49 ADD INTERFACE GROUP PARAMETERS
Parameter
Description
Interface1
Interface2
Backup Mode
Select ONEPLUSONE.
Note:
It is no need to specify which port is active and which is
standby. The system assigns automatically. The active port is
generally the one with a larger port number.
5. Click the Execute(F5) button or press F5 to execute this command.
END
OF STEPS
118
The user has logged in to the OMM client and has the right to
perform data configuration.
The OMM system is correctly configured and connected according to the network planning.
The connection between the OMM network management system and the OMP module is normal.
The IP interfaces, loopback interface, and the group of active/standby interfaces have been configured.
Context
This topic describes the procedure to create static route for IP interfaces.
For example, Office 14 adopts network segment 190, while Office 16 adopts network segment 191. And Module 3 of Office 14
(190.168.14.2, port 5003) needs to connect Module 4 of Office 16
(191.168.16.2, port: 50004). The following static routes should
be configured.
Steps
4. Set the parameters. For details about the parameters, see the
following table.
119
Description
Net Prefix
Mask
Next Hop IP
Tunnel ID
Loopback Port
Distance
VRF NAME
Global
CORBA ID
120
OF STEPS
121
122
123
124
Context
Steps
125
126
Parameter
Description
AdminDomain ID
AdminDomain Sub
Net
AdminDomain
property
Type of Mate
AdminDomain
Parameter
Description
HLRNumber of Mate
HLR
Takeover Method
Takeover Check
Interval(s)
Takeover Check
Volume Threshold
Allow Reliable
Service After
Takeover
Allow Transient
Service After
Takeover
Is Basic
AdminDomain for
Copying
User Label
OF STEPS
127
Context
This topic describes the procedure to configure the relation between an administration domain and a DUA.
Steps
Description
Serial No.
AdminDomain ID
DUA Node ID
User Label
128
OF STEPS
Context
Steps
129
Description
AdminDomain ID
ITEM ID
User Label
OF STEPS
Context
Steps
130
Description
AdminDomain ID
ITEM ID
ITEM Value
User Label
OF STEPS
131
132
Context
Steps
133
Description
Serial No.
PDSA Group ID
AdminDomain ID
User Label
OF STEPS
134
Context
Steps
Description
ID
Number Segment
Type
Beginning Number
Ending Number
135
Parameter
Description
AdminDomain ID
User Label
OF STEPS
Context
This topic describes the procedure to add a logical number segment (such as those of MSISDN or DN numbers) in an administration domain.
Steps
136
Description
ID
Beginning Number
Ending Number
AdminDomain ID
User Label
OF STEPS
137
Context
Steps
138
Parameter
Description
Serial No.
Number Type
Beginning Code
ending Code
IDSA Group ID
User Label
OF STEPS
Context
Steps
139
Description
Serial No.
Number Type
Beginning Code
ending Code
IDSA Group ID
User Label
OF STEPS
Context
Steps
140
3. On the MML commands navigation tree, select MML Commands > Subscriber Data Distributing Configuration >
PDSA Group Logical Number Distributing Configuration
> Create PDSA Group Logical Number Distributing Configuration (ADD DSAGRPSPN) to open the window as shown
in the following figure.
FIGURE 79 ADD DSAGRPSPN COMMAND INTERFACE
Description
ID
Number Segment
Type
Beginning Number
Ending Number
PDSA Group ID
User Label
OF STEPS
141
142
Context
An operator may have one or more roles and thus obtain some
operation authorities. The authorities of a role include operating
administration domains, number segment groups in the administration domain and operation codes.
The following figure shows the relation between operation authorities on number segment groups and roles.
143
Description
Number Group ID
AdminDomain ID
User Label
OF STEPS
144
Context
An operator may have one or more roles and thus obtain some
operation authorities. The authorities of a role include operating
administration domains, number segment groups in the administration domain and operation codes.
A number segment group may contain multiple number segments.
Within an administration domain, a number segment or a number
can not be contained by or overlaps with another number segment.
For the illustration of the relation between roles and agent authorities, refer to 13.1.
This topic describes the procedure to create a physical number
segment and assign it to a number segment group.
Steps
Description
ID
Beginning Number
Ending Number
145
Parameter
Description
Number Group ID
User Label
OF STEPS
Context
An operator may have one or more roles and thus obtain some
operation authorities. The authorities of a role include operating
administration domains, number segment groups in the administration domain and operation codes.
A number segment group may contain multiple number segments.
Within an administration domain, a number segment or a number
can not be contained by or overlaps with another number segment.
For the illustration of the relation between roles and agent authorities, refer to 13.1.
This topic describes the procedure to create a logical number segment and assign it to a number segment group.
Steps
146
Description
ID
Beginning Number
Ending Number
Number Group ID
User Label
OF STEPS
Context
Steps
147
148
Note:
OF STEPS
Add operators.
Context
When an operator having a role has all authorities of this role. One
operator can have multiple roles and thus have their authorities.
This topic describes the procedure to add an operator.
Steps
149
150
OF STEPS
Context
Steps
151
Description
Synchronization type
Changed Tables refer to the tables of
configuration data that have been changed since
last synchronization.
All Tables refer to all the tables of configuration
data on the EMS.
Sync Option
152
Parameter
Description
Options
Timeout
(100ms)
OF STEPS
153
154
Glossary
AS
Application Server
ASIC
Application Specific Integrated Circuit
ASP
Application Server Process
ATM
Asynchronous Transfer Mode
BCTC
Backplane of ConTrol Center
BE
Back End
CMP
Calling Main Processor
CORBA
Common Object Request Broker Architecture
CPU
Central Processing Unit
DBIO
DataBase Input & Output
DN
Directory Number
DPC
Destination signaling Point Code
DSA
Directory System Agent
DSP
Directory System Protocol
DSP
Digital Signal Processor
DST
Data Storage Transfer
DUA
Directory User Agent
EMS
Element Management System
FE
Front End
FE
Fast Ethernet
FPGA
Field Programmable Gate Array
155
FTP
File Transfer Protocol
GE
Gigabit Ethernet
GT
GSM/TD Dual Mode
HLR
Home Location Register
IDSA
Identity DSA
IMSI
International Mobile Subscriber Identity
IP
Internet Protocol
IPSP
IP Signaling Point
ISUP
ISDN User Part
LDAP
Lightweight Directory Access Protocol
LIC
Lawful Interception Center
LRN
Location Routing Number
M3UA
MTP3-User Adaptation layer protocol
MAP
Mobile Application Part
MGW
Media GateWay
MIN
Mobile station Identification Number
MSCS
Mobile Switching Center Server
MSISDN
Mobile Station International Subscriber Directory Number
MTP
MessageTransfer Part
NE
Network Element
OMC
Operation & Maintenance Center
OMM
Operation & Maintenance Module
PDSA
Profile DSA
PSID
156
Glossary
157
WCDMA
Wideband Code Division Multiple Access
158