Professional Documents
Culture Documents
06 ZXUR 9000 UMTS Configuration 85P
06 ZXUR 9000 UMTS Configuration 85P
Configuration
Contents
2
Introduction of Templates for Quick Data
Configuration
V4_Template_Equipment.xls
Data configuration related to rack, shelf,
board, office information, and basic
networking
V4_Template_TransportNetwork.xls
Parameter configuration for transmission
and integration on the IU/IUR/IUB
interfaces
The first sheet of all quick data configuration templates is the “Template Info” sheet, which
provides the basic template information for OMM. By this sheet, OMM can judge whether
the template matches with OMM and acquire the categorization information of templates.
Therefore, the content of this sheet must be kept complete no matter which of other sheets
are selected
R=Read
W= Write It can be modified.
R= Read it can be Read
I= Initial Must be configured during Data creation
Primary Key It is compulsory during data creation and modification.
The first and fifth lines of the template are not allowed to be modified;
otherwise the template cannot be imported normally.
© ZTE All rights reserved 10
Rows of the template files
1
2
3
4
All the sheets starts with three columns A,B and C which are as follow :
Column A : Result : it’s used to show the result of the import of the template
Column B : modification indication : it’s used to Add, delete, modify or pass (
ignore ) the data input
Column C : Managed element object ID : it’s used to indicate the NE ID ( RNC in
this case ) in the EMS
13
UR9000 UMTS Configuration
IMPORTANT
The following will describe the configuration steps and
parameters used by WINDTRE in the testbed.
The configuration steps will show first how to fill up the
templates files and which parameters to configure by default
values.
Each template will provides all sheets necessary to be configured
according to the testbed scenario
Each sheet will provide the parameter name in GUI ( 2nd row )
and its value used by WINDTRE in testbed scenario
PLMN CONFIG
Shelf Config
One pair of USP2a is used at slot 9/10 with logical module as CDR 3,64,65.
One EGPB2a is used at slot 17
4 interface boards EXGB1a are used at slots ( 23/24/25/26)
Board config
Sapshot from testbed RNC1/BSC1
Global Info
Interface IP
Interface board : An interface board should be mentioned by
rack/shelf/slot. If the interface is a loopback then 0/0/0. Common Ips
Port type : indicates if the port is physical or logical (
0:Interface, 1:Loopback port, 2:Virtual port)
MAC address : Mac address of interface board and ports
should be assigned manually according to plan .
Each interface ( Iu, Iur, Iub ) could be configured with one or
more Ips. Depending on the system capacity, dimensioning
and redundancy protection.
In this scenario we have 2 Ips for each interface ( Iub, Iucs,
Iups, Iur ) per CP and same per UP ( except Iucs and Iur CP
which share the same IP )
Iub require additional 2 ips for IUB common.
So 4 Interfaces *2 (CP +UP) * 2 ( Ips ) – 2 Ips shared + 2Ip for
Iub common = 16
Service IP
Member port
32
Transmission network configuration
RNC protocol Stack
Node B Iu-PS
domain
RNC
RNC Iu-CS
domain
© ZTE All rights reserved 33
Transmission network configuration
Local office
OPC : 16172
NRI CS : 0
NRI PS : 5
© ZTE All rights reserved 35
Contents
Introduction of Data Configuration File
Equipment template configuration
Transmission network configuration
IUB Integration
IU integration
IUR integration
36
Iub integration
IP Path group :
IUB office
43
IU integration
IuCS and IuPS integration flow is same. The sheets used will be as
follow :
1. Adjacent Office(CN)
2. Static Route
3. SCTP Config(CN)
4. M3uaAS Config(CN)
5. M3uaRoute
6. M3uaRouteSet
7. IP Path Group
8. IP Path(CN)
IP PATH Group
Path group ID 2002 and 2001 and created for GGSN2 and GGSN3
with 1Gbps bandwidth respectivly
Path group ID 2003 is created for MSC1 with 100Mbps
bandwidth
NE SCTPAdjacend
Config ( Associatio
CN ) Local Local IP Remote Remote IP ASP
office ID n ID port port number
192.168.187.106;1 10.10.10.24;10.1
SGSN3 3 2906 2906 92.168.187.107 2905 0.10.27 9
192.168.187.106;1 10.10.10.25;10.1
SGSN3 3 2907 2907 92.168.187.107 2905 0.10.26 10
192.168.187.106;1 10.10.10.5;10.10
SGSN2 2 2908 2906 92.168.187.107 2905 .10.8 11
192.168.187.106;1 10.10.10.6;10.10
SGSN2 2 2909 2907 92.168.187.107 2905 .10.7 12
192.168.187.104;1 192.168.173.49;
MSC+MGW 4 2910 2905 92.168.187.105 2921 192.168.173.65 14
192.168.187.104;1 192.168.173.49;
MSC+MGW 4 2911 2906 92.168.187.105 2922 192.168.173.65 15
192.168.187.104;1 192.168.173.49;
MSC+MGW 4 2912 2907 92.168.187.105 2923 192.168.173.65 16
192.168.187.104;1 192.168.173.49;
MSC+MGW 4 2913 2908 92.168.187.105 2924 192.168.173.65 17
M3uaAS Config
M3ua Route
M3ua RouteSet
IP Path ( CN)
56
IUR integration
IP PATH group
M3uaAs Config
M3ua RouteSet
IP PATH ( CN)
64
Radio network configuration
ULogicalCell
70
Configuration Data Import - Step 1
Configuration management :
Create subnetwork
Set subnetwork ID and
MCC
Import and execute the Equipment, TransportNetwork, and Radio Quick Configuration
Templates in the same way.
In the result file, the import result is shown in Column A (Result), and the
MODIND field for a successful record is automatically modified to “P” in
Column B.
79
Data Modification After Template Import
In the pop-up PTP Interface Configuration window, click the Edit button.
Modify the parameters according to the samples marked in red box in the
following figure: