Umtsrns 210 rnc commissioning preparation

RNC CommisioningPreparation
Version1.00
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech IndustrialPark,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900 800-9830-9830
Fax: (86) 755 26772236
URL: http://support.zte.com.cn
E-mail: doc@zte.com.cn

LEGAL INFORMATION
Copyright © 2006 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
contractualconfidentiality 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.
The contents of this document and all policies of ZTE CORPORATION, including without limitation policies related to
support or training are subject to change without notice.
Revision History
Date Revision No. Serial No. Reason for Revision
7/15/2009 R1.0 sjzlyyyyxxxx First edition

ZTE CORPORATION
We Values Your Comments & Suggestions!
Your opinion is of great value and will help us improve the quality of our product
documentation and offer better services to our customers.
Please fax to: (86) 755-26772236; or mail to Documentation R&D Department,
ZTE CORPORATION, ZTE Plaza, A Wing, Keji Road South, Hi-Tech Industrial Park,
Shenzhen, P. R. China 518057.
Thank you for your cooperation!
Document
Name
RNC Commisioning Preparation
Product Version V1.00
Document Revision
Number
R1.0
Equipment Installation Date
Your evaluation
of this
documentation
Presentation:
(Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization,
Appearance)
 Good  Fair  Average  Poor  Bad  N/A
Accessibility:
(Contents, Index, Headings, Numbering, Glossary)
Intelligibility:
(Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)
Your
suggestions for
improvement of
this
documentation
Please check the suggestions which you feel can improve this documentation:
 Improve the overview/introduction  Make it more concise/brief
 Improve the Contents  Add more step-by-step procedures/tutorials
 Improve the organization  Add more troubleshooting information
 Include more figures  Make it less technical
 Add more examples  Add more/better quick reference aids
 Add more detail  Improve the index
 Other suggestions
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
# Please feel free to write any comments on an attached sheet.
If you wish to be contacted regarding your comments, please complete the following:
Name Company
Postcode Address
Telephone E-mail

This page is intentionally blank.

Contents
About this Manual.........................................................................i
Purpose........................................................................................ i
Intended Audience ....................................................................... i
Prerequisite Skill and Knowledge .................................................. i
What is in This Manual.................................................................. i
Related Documentation ................................................................ii
Conventions .................................................................................ii
How to Get in Touch....................................................................iii
Chapter 1........................................................................................5
RNC Commissioning Overview................................................5
Overall Flow of RNC Commissioning...................................5
Chapter 2........................................................................................7
RNC Power-up ..............................................................................7
RNC Power-up Flow ........................................................7
Check before Power-up ...................................................8
Hardware Check..........................................................................8
Check of Rack Cable Location (Internal/External/Inter-Rack) .....17
Check of Cabinet Power Supply .................................................33
Check List before Power-up.......................................................35
Equipment Power-up .................................................... 38
Power-up Procedure ..................................................................38
Power-down Procedure..............................................................39
Check After Power-up ................................................... 40
Hardware Check........................................................................40
Check List.................................................................................42
Table of Board Information........................................................43
Chapter 3.....................................................................................45
Software Version Management............................................45

Overview.................................................................... 45
Operation Flow Description........................................................ 45
Frequently Used Terms ............................................................. 45
Descriptions of the Toolbar Icons............................................... 46
Lib Version Management ............................................... 47
Lib Version Information............................................................. 47
Putting a Single Version into the Library.................................... 48
Putting Batch Versions into the Library...................................... 50
Lib Version Functions ................................................................ 53
Default Version Management ......................................... 60
Single Default Version Switching ............................................... 60
Batch Default Version Switching ................................................ 62
Appointed Version Management...................................... 64
Appointed Version Loading ........................................................ 65
Canceling Appointed Version ..................................................... 68
Other functions of Software Version Management .............. 70
OMP Version Query ................................................................... 70
OMP Startup Mode Query.......................................................... 70
Software Version Backup........................................................... 70
Software Version Recovery........................................................ 72
Software Version Consistency Comparison................................. 72
Query Foreground and Background Versions by Logical Board Type
................................................................................................ 76
Synchronizing Version Data from the Foreground to the
Background............................................................................... 77
Configuring OMC FTP Parameter................................................ 79
Figures.........................................................................................81
Tables...........................................................................................87

Confidential and Proprietary Information of ZTE CORPORATION i
About this Manual
Purpose
This Manual provides procedures and guidelines that support the
operation of the ZXWR RNC commissioning preparation.
Intended Audience
This document is intended for engineers and technicians who
perform operation activities on RNC commissioning preparation.
Prerequisite Skill and Knowledge
To use this document effectively, users should have a general
understanding of wireless telecommunications technology.
Familiarity with the following is helpful:
 OMM operation
 RNC hardware
What is in This Manual
This Manual contains the following chapters:
TAB L E 1 CH APTER SU MMAR Y
Chapter Summary
Chapter 1 RNC
Commissioning
Overview
Introduces the overall information of RNC
commissioning.
Chapter 2 RNC Power-
up
Introduces RNC power-up procedures.
Chapter 3 Software
Version Management
Introduces software version management
in RNC.
Figures Provides figure list in this manual.

RNC Commissioning Preparation
ii Confidential and Proprietary Information of ZTE CORPORATION
Chapter Summary
Tables Provides table list in this manual.
Related Documentation
The following documentation is related to this manual:
 ZXWR RNC (V3.07.310) Radio Network Controller Software
Management Operation Guide
 ZXWR RNC (V3.07.310) Radio Network Controller Hardware
Description
 ZXWR RNC (V3.07.310) Radio Network Controller Hardware
Installation Guide
Conventions
ZTE documents employ the following typographical conventions.
TAB L E 2 TYPOGR APH I C AL CON VEN TI ON S
Typeface Meaning
Italics References to other Manuals and documents.
“Quotes” Links on screens.
Bold Menus, menu options, function names, input
fields, radio button names, check boxes, drop-
down lists, dialog box names, window names.
CAPS Keys on the keyboard and buttons on screens
and company name.
Constant width Text that you type, program code, files and
directory names, and function names.
[ ] Optional parameters.
{ } Mandatory parameters.
| Select one of the parameters that are delimited
by it.
Note: Provides additional information about a
certain topic.
Checkpoint: Indicates that a particular step needs
to be checked before proceeding further.
Tip: Indicates a suggestion or hint to make things
easier or more productive for the reader.
Typographical
Conventions

About this Manual
Confidential and Proprietary Information of ZTE CORPORATION iii
TAB L E 3 M OU SE OPER ATI ON CON VEN TI ON S
Typeface Meaning
Click Refers to clicking the primary mouse button (usually
the left mouse button) once.
Double-click Refers to quickly clicking the primary mouse button
(usually the left mouse button) twice.
Right-click Refers to clicking the secondary mouse button
(usually the right mouse button) once.
Drag Refers to pressing and holding a mouse button and
moving the mouse.
How to Get in Touch
The following sections provide information on how to obtain
support for the documentation and the software.
If you have problems, questions, comments, or suggestions
regarding your product, contact us by e-mail at
support@zte.com.cn. You can also call our customer support
center at (86) 755 26771900 and (86) 800-9830-9830.
ZTE welcomes your comments and suggestions on the quality
and usefulness of this document. For further questions,
comments, or suggestions on the documentation, you can
contact us by e-mail at doc@zte.com.cn; or you can fax your
comments and suggestions to (86) 755 26772236. You can also
browse our website at http://support.zte.com.cn, which contains
various interesting subjects like documentation, knowledge
base, forum and service request.
Mouse
Operation
Conventions
Customer
Support
Documentation
Support

iv Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION 5
C h a p t e r 1
RNC Commissioning
Overview
Overall Flow of RNC
Commissioning
The debugging consists of a series of steps. Those independent
steps are also interwoven. To finish the work smoothly, the
engineers shall operate according to the whole flow.
Overall flow of RNC commissioning is shown in Figure 1.

6 Confidential and Proprietary Information of ZTE CORPORATION
FI GU R E 1 ZXWR RNC COMMI SSI ON I N G FL OW C H AR T
Start
Database
Installation
OMM Server
Installation
OMM Client
Installation
O&M setting
RNC data
configuration
RNC
interconnection &
debugging
RNC power-up
check
RNC service
debugging
End
Every step must be made correctly and pass the corresponding
check. Otherwise, return to the last step.
Every step in the flowchart is independent.
1. OMM database installation.
2. OMM server installation.
3. OMM client installation.
4. RNC power-up, including checking before power-up, power-
up/power-down steps, and check criteria after power-up.
5. RNC data configuration, including configuration specifications
in the template mode, tool mode and manual mode.
6. Interconnection and debugging, including the interconnection
debugging specifications for Iub, Iu_CS, Iu_PS and Iur
interfaces.
7. Service debugging, including CS domain 12.2K voice service,
CS domain 64K data service, PS domain 384K service – FTP
downloading, CS domain 12.2K and PS domain 384K
concurrent service, soft handover, hard handover, etc.
8. Operation & maintenance setting, including network status
observation, network performance statistics, and real-time
maintenance.

C h a p t e r 2
RNC Power-up
RNC Power-up Flow
RNC power-up flow is shown in Figure 2.
FI GU R E 2 FL OW C H AR T OF CH EC K B EF OR E POW ER -U P
Start
Hardware
check
Rack
check
Board
check
Shelf
check
Cable location
check
Internal
cable
connection
Inter-
rack
cable
conn.
External
cable conn.
Equipment
power-up
Board
status
check
Check record table
Check record table
End
Fan
status
check
Cabinet power
input check

Check before Power-up
Hardware Check
Check of Racks
1. Confirm with the power system personnel to ensure that the
-48V power supply from the DC power distribution box to the
RNC cabinet is disconnected.
2. Turn off the two-way -48V power switch in the power
distribution box for the RNC cabinet, as shown in Figure 3.
FI GU R E 3 SW I TC H ES I N TH E TOP-L EF T COR N ER OF CAB I N ET FR ON T PAN EL
3. Turn off the -48V power switches of all the sub-rack filters in
the rear panel of the RNC cabinet, as shown in Figure 4.

Chapter 2 RNC Power-up
FI GU R E 4 SW I TC H F OR TH E CAB I N ET REAR SU B -R AC K
4. Check whether the rack-top filters are connected to the
power distribution sub-rack securely and whether the
connectors are firm (usually made before they leave the
factory), as shown in Figure 5.
FI GU R E 5 FI L TER S AN D POW ER DI STR I B U TI ON SU B -R AC K AT TH E CAB I N ET
REAR -TOP SI D E
5. Check whether the bus-bar at the cabinet rear side is
connected to the power distribution sub-rack firmly and
whether all the wiring terminals on the bus-bar are sealed

with insulating tubes (usually made before they leave the
factory).
FI GU R E 6 CON N EC TI ON DI AGR AM OF BU S-B AR AN D POW ER DI STR I B U TI ON
SU B -R AC K
Check of Shelves
1. Check if all the switches for the shelves are in the OFF state,
as shown in Figure 7.
2. Check if the -48V power cables for all the fan sub-racks are
connected correctly and firmly (usually made before they
leave the factory), as shown in Figure 7 below.

FI GU R E 7 CON N EC TI ON DI AGR AM OF FAN POW ER CAB L ES
3. According to the following DIP switch description, check if all
the DIP switches for all the shelves are in the correct state
and if they correspond with the proper shelf numbers.
4. For the latest boards, their DIP switches shall adopt the
short-circuit cap setting: 0 for short-circuit and 1 for
disconnected circuit. The setting method is similar to DIP.
Here the DIP setting is taken as the example:
i. The RNC shelf DIP setting is described as follows:
The shelf numbers are decided by the DIP switches at
their rear side rather than their locations. Every shelf has
a DIP switch in its top-left corner. Usually the DIP switch
of the new shelf is covered by a metal plate. Therefore,
before seeing the switch, the engineers and technicians
should first remove the screw, as shown in Figure 8.

FI GU R E 8 DI AGR AM OF RNC SH EL F DIP SW I TC H
There are three DIP switches in Figure 2 6. From the left to the
right are the office number DIP switch, the rack number DIP
switch and the shelf number DIP switch. For each DIP switch,
the left represents the low bit and the right represents the high
bit. So the DIP switch takes a left-low and right-high manner. If
the switch is dialed to the upper side, it indicates 0 and if it is
dialed to the lower side, it indicates 1.Here is a brief introduction
to the setting of the three DIP switches:
(Y represents the valid BIT, X fills the invalid BIT, the left side
represents low BIT and the right represents high BIT (110X
means 3, 100X means 1). If the switch is turned ON, then
BIT =0; if it is turned OFF, then BIT =1. For the current shelves,
usually ON is at the top while OFF at the bottom.)
Office number TRIB: 3BIT YYYX
Rack number RACK: 4BIT YYYY
Shelf number SHELF: 3BIT YYYX (a rack contains four shelves
at most)

Note:
Office number: the DIP value on the backplane is the target
value. If Office No. 3 is required, the TRIB switch should be set
to 110X (invalid bit X=0).
Rack number: The DIP value on the backplane plus 1 is the
target value. If Rack No.1 is required, the RACK switch should
be set to 0000.
Shelf number: The DIP value on the backplane plus 1 is the
target value. If Shelf No.2 is required, the SHELF switch should
be set to 100X.
ROMP must be set in Shelf No.2 in Rack No.1, i.e., SHELF 1,
RACK 0.
ii. For example:
As shown in Figure 9, the switches mean SHELF 1, RACK
1, TRIB 0.
FI GU R E 9 DIP SW I TC H V AL U E OF SHELF 1, RACK 1, TRIB 0
ON
OFF
Trib Rack Shelf
三
As shown in Figure 10, the switches mean SHELF 2, RACK 1,
TRIB 0.
FI GU R E 10 DIP SW I TC H V AL U E OF SHELF 2, RACK 1, TRIB 0
ON
OFF
Trib Rack Shelf
三

Check of Boards
1. Check the number of boards according to the system
configuration list.
2. Check if the board BOOT chips have been mounted securely,
FI GU R E 11 LOC ATI ON OF BOOT CH I P ON TH E BOAR D
3. Check the board PCB version numbers as shown in Figure 12,
and according to 0 Check List, record the PCB version
numbers and information of EPLD, sub-card EPLD and
quantity.

FI GU R E 12 LOC ATI ON OF BOAR D PCB NU MB ER
4. As shown in Figure 13, check the power input end of the
board and make sure the contact point is clean, without
congestion or short circuit.
FI GU R E 13 POW ER IN PU T EN D OF TH E BOAR D
5. Check the DIP switch on the DTB board according to the E1
impedance matching resistances provided by the
telecommunications operator.
i. The structure of the DTB board is as shown in Figure 14.

FI GU R E 14 STR U C TU R E OF TH E DTB B OAR D
321
X23
ONS11
S10 ON
S8 ON
ONS7
S2
ON
ON
S4
S6
ON
ON
S12
S9
ON
ON
S5
S3
ON
ON
S1
RDTB
DTB
ii. Front view 2. Layout of DTB board 3.Rear View
The switch settings are as shown in Table 4 below when
the E1 impedance matching resistances are 75 ohm and
120 ohm.
TAB L E 4 DTB SW I TC H SETTI N GS F OR 75  /120  RESI STAN C E
DIP
Switch
Usage
Switch Setting Default Location
Mode 1 2 3 4 1 2 3 4
S1~S6
S9
S12
To select
impedance
matching
resistances (75
/120 ) for E1
links
75  ON ON ON ON
ON ON ON ON
120  OFF OFF OFF OFF
Note:
If the E1 link adopts 75Ω PCM-line unbalanced transmission
mode, then the DIP switches of S1-S6, S9 and S12 shall all be
set to the ON state.
If the E1 link adopts 120Ω PCM-line balanced transmission mode,
then the DIP switches of S1-S6, S9 and S12 shall all be set to
the OFF state.

6. Check the RDT B board jumpers according to the E1
impedance matching resistances provided by the
telecommunications operator. The diagram of the RDTB
board jumpers is as shown in Figure 15 below.
FI GU R E 15 DI AGR AM OF TH E RDTB BOAR D JU MPER S
X16
X15
X14
X13
X12
X11
X10
X9
1 2
3 4
5 6
7 8
9 10
11 12
13 14
15 16
1615
1413
1211
109
7 8
65
43
21
1 2
3 4
5 6
87
9 10
11 12
13 14
15 16
1615
1413
1211
109
7 8
65
43
21
1 2
3 4
5 6
87
9 10
11 12
13 14
15 16
1615
1413
1211
109
7 8
65
43
21
1 2
3 4
5 6
87
9 10
11 12
13 14
15 16
1615
1413
1211
109
7 8
65
43
21
1615
1413
1211
109
87
65
43
21
Note:
If the E1 link adopts 75Ω PCM-line unbalanced transmission
mode, then it is required to INSERT all the short-circuit blocks
from Jumper X9 to Jumper X16 on the RDTB backplane.
If the E1 link adopts 120Ω PCM-line balanced transmission mode,
then it is required to REMOVE the short-circuit blocks from
Jumper X9 to Jumper X16 on the RDTB backplane.
If the DIP switches and jumpers of the RNC boards are set
according to the E1 impedance matching resistances, then
corresponding settings shall also be made for the NodeB boards.
Refer to related NodeB documents for detailed information.
Check of Rack Cable Location
(Internal/External/Inter-Rack)
Internal Cable
1. Diagram of internal cable connection
Figure 16 shows the connection of internal cables between
RNC control frame and resource frame:

i. Clock cable connection: To provide clock for the
whole RNC, firstly the APBE board in the resource frame
acquires clock source from the Iu interface, and transmit
it from the 8KOUT/DEBUG-232 output in its rear board
RGIM1 to the 8KIN1 input in the rear board RCKG1 in the
control frame through a H-CLK-004 cable;
Then the RNC control frame connects the CLKOUT output
of the rear board RCKG1 to the CLKIN inputs of the
boards through a 1-to-6 H-CLK-003 clock cable and
provides clock reference for those boards. In this
example, the boards that ask RCKG1 for clock reference
include RUIM1 in Slot 9 and Slot 10 of the resource
frame, RUIM2 and RUIM3 in Slot 9 and Slot 10 of the
control frame.
ii. As for the Ethernet cable connection, FE-C1/2 in Slot 9
and Slot 10 in the resource frame shall be connected with
CHUB in the control frame through an H-ETH-008 cable
to realize the connection with UIMC. If there is no CHUB,
then the two frames shall be connected with the RUIM1
FE-C1/2 in Slot 9 of the resource frame and the RUIM2
FE1 in Slot 9 of the control frame.
FI GU R E 16 CON N EC TI ON OF IN TER N AL CAB L ES
Slot 11 rear
board RGIM1
8KOUTDEBUG-232
Rear
board of
resource
frame 3
Slot 10 rear
board RUIM1
FE-U
FE-C3/4
FE-C1/2
CLKIN
DEBUG-FE
DEBUG-232
2-
4
1-
2
Slot 9 rear
board RUIM1
FE-U
FE-C3/4
FE-C1/2
CLKIN
DEBUG-FE
DEBUG-232
2-
3
1-
1
Rear
board of
control
frame
Slot 10 rear
board RUIM3
FE10
FE8
FE6
CLKIN
FE4
FE2
2-
2
Slot 9 rear
board RUIM2
FE9
FE7
FE5
CLKIN
FE3
FE1
2-
1
Slot 15 rear
board RCHB1
FE17-24
FE9-16
FE1-81
Slot 13 rear
board RCKG1
2Mbps/2MHz
8KIN1
8KIN2
CLKOUT2
CLKOUT
3
Note: Red Port 2 should connect the H-CLK-003 clock cable;
Black Port 3 should connect the H-CLK-004 cable;
Blue Port 1 should connect the H-ETH-008 cable
2. Introduction to Internal Cable Connection
i. Connection of System Clock Cables
The CLKG end is the DB44 (pin-type) plug and the
UIMC/U end is the DB9 (pin-type) plug. H-CLK-003 cable
structure is as shown in Figure 17.

FI GU R E 17 STR U C TU R E OF SYSTEM CL OC K CAB L E H-CLK-003
Connecting directions:
End A of the cable shall be connected to “CLKOUT” of the
RCKG1/RCKG2 in backplane.
End B of the cable can be classified into 3 groups:
B1~B2, B3~B4 and B5~B6. Each group shall be
connected to one frame with two pins respectively
connecting to the active/standby UIMC or the UIMU
backplane as shown in Figure 18.
FI GU R E 18 CON N EC TI ON OF CL OC K CAB L E

The left figure shows End A, which is connected to RCKG1
And the right figure shows End B, which is connected to RUIM1

ii. 8K Clock Cable
The structure of H-CLK-004 8K clock cable is shown in
Figure 19.
FI GU R E 19 STR U C TU R E OF H-CLK-004 8K CL OC K CAB L E
The connecting directions are shown in Figure 20.
End A shall be connected to “8KOUT/DEBUG-232” of
RDTB/RSPB/RGIM1 or the”8KOUT/ARM232” of RMNIC;
End B shall be connected to the “8KIN1” or ”8KIN2” of
RCKG1.

FI GU R E 20 CON N EC TI ON OF 8K CL OC K CAB L E

The left figure shows End B, which is connected to RCKG1
And the right figure shows End A, which is connected to RGIM1
iii. Inter-connected Cables in Control Plane
Inter-connected cables in the control plane realize the
connection between the Ethernet of the system internal
resource frame/exchange frame and the CHUB of the
control frame.
End A of the cable shall be the DB44 connector (pin-
type), End B be the 8P8C straight shielded cable plug.
The cable shall be the FTP Super Category 5 shielded
data cable. The structure of the H-ETH-008 cable is
shown in Figure 21.
FI GU R E 21 H-ETH-008 CAB L E STR U C TU R E I N CON TR OL PL AN E
标签
标签
标签
标签
标签
标签
标签
标签
标签
A端
B1端
B2端
B3端
B4端
B5端
B6端
B7端
B8端
End A shall be connected to any one of “FE1-8”, ”FE9-
16”, ”FE17-24”, ”FE25-32”, ”FE33-40” and ”FE41-46” of
the rear board RCHB1/RCHB2.
End B1-B8 shall be classified into 4 groups: B2n-1 and
B2n (n=1...4) form a group. Each group shall be
connected with one frame and have two physical
connection modes. Let’s take End B1 and End B2 for
example, when the cable connects the resource frame,
End B1 shall be connected to the “FE-C1/3” of one RUIM1
board; End B2 shall be connected to the “FE-C1/3” of
another RUIM1 board. When the cable connects the
control/exchange frame of another cabinet, End B1 shall
be connected to the “FE2n-1” of RUIM2, and End B2 to
“FE2n” (n=1..5) of RUIM3.
The H-ETH-008 cable in the control plane shall not be
used in the dual-frame configuration. Currently our
experimental sites are all with dual-frame configuration.
The cable between the control frame and the resource

frame for a dual-frame configured site shall be connected
as shown in Error! Reference source not found..
FI GU R E 22 CAB L E CON N EC TI ON B ETW EEN CON TR OL FR AME AN D RESOU R C E
FR AME
The left figure shows the RUIM2 interface of the control frame.
And the right figure shows the RUIM1 interface of the resource frame.
iv. PD485 Cable and Fan Monitoring Cable
These cables complete the 485 connection from ROMB
board to the power distribution sub-rack of the local
cabinet and the connection from the power distribution
sub-rack to the fan sub-rack, and monitor the PWRD
board and fan from system.
H-ETH-009 structure of the PD485 cable is shown in
Figure 23.
FI GU R E 23 H-ETH-009 STR U C TU R E OF PD485 CAB L E
END B
END A
LABEL
LABEL

End A shall be connected to “PD485” of RMPB board or
the “FANBOXn” (n=1..4) of backboard in the power
distribution sub-rack.
End B shall be connected to “RS485” (the upper port) in
the backboard of the power distribution sub-rack, the
RJ45 connector in the left of the back of the fan sub-rack,
or the RJ45 connector in the left of the fan rack, as
shown in Figure 24 and Figure 25.
FI GU R E 24 CON N EC TI ON OF PD485 CAB L E

The upper figure shows End A, which is connected to “PD485” of RMPB
board.
The lower figure shows End B, which is connected to “RS485” of the
backboard in power distribution sub-rack.
FI GU R E 25 CON N EC TI ON OF FAN M ON I TOR I N G CAB L E
The top-right corner is ”FANBOXn” (n=1..4) at the back of the power
distribution sub-rack.
The bottom-left corner is the left RJ45 at the back of the fan sub-rack.
External Cables
The connection between the RNC system and the external
network management equipment is shown as Figure 26: the
network cable of background OMCR shall be connected to the
OMC2 port of the RMPB board, and that of OMCB shall be
connected to the first FE1 port of RMINC from the top down. The
structure and debugging serial-port cable shall be connected to
the DEBUG2 port of RMPB.

FI GU R E 26 EXTER N AL CON N EC TI ON OF RNC RAC K
FE1
FE2
FE3
FE4
DEBUG-FE
PrPMC232
8KOUT/ARM232
Slot 11 Back-Card
RMPB
OMC1
OMC2
GPS485
PD485
RS232
DEBUG1-232
DEBUG2-232
Resource
Frame
Backboard
Control
Frame
Backboard
External Connection of RNC Rack
Cutline
B09
139.1.0.0/16
ROMP
constructor
RS232 serial-port cable
WOMCR server WOMCR client
129.0.0.0/8
10/100M UTP
network cable
RS232 cable
LC/LC fiber
.3
Slot 12 Back-Card
RMNIC
Note:
During the construction of WCDMA testing environment,
attention shall be paid to the following points: the client and the
server of the network management background are connected
with the RNC via the Ethernet switch. Because currently RNC
and CN are using the unified platform for 3G network
management, the RNC network management background cannot
share the same Ethernet switch with CN. Otherwise, the
confliction of the server processes will occur, which may cause
login failure at the client.
Inter-Rack Cables
1. Optical Cable Connection from RNC Rack to CN:
i. Connection to MGW NE (Network Element): It is from the
first optical port of the APBE board in the RNC resource

frame to the first optical port of the APBE board of the
MGW NE at the CN side. Pay attention to the receiving
and sending polarities. The ACT and SD green indicators
of the two APBE boards will be on if the connection is
correct, as shown in Figure 27. (If it is wrong, reverse the
receiving and sending polarities of the optical cable.)

FI GU R E 27 OPTI C AL CAB L E CON N EC TI ON F R OM RNC TO M GW
The left is the APBE board interface of RNC and the right is that of MGW
ii. Connection to SGSN NE: It is from the second optical port
of the APBE board in the RNC resource frame to the first
optical port of the SIUP board of the SGSN NE at the CN
side. Pay attention to the receiving and sending

polarities. The ACT and SD green indicators of the APBE
board and the SIUP board will be on if the connection is
correct, as shown in Figure 28. (If it is wrong, reverse the
receiving and sending polarities of the optical cable.)
FI GU R E 28 OPTI C AL CAB L E CON N EC TI ON F R OM RNC TO SGSN
The left figure is the APBE board interface of RNC and the right is the
SIUP board interface of SGSN.
iii. Connection from RNC to BME: It is realized by a network
cable whose ends are respectively connected to the back-
cards of two GIPI boards. The back-cards of the GIPI
boards can also be RMNIC. The difference is that RGBR is
a kilomega port and RMNIC is a 1/10 kilomega port.
2. Connection from RNC to NodeB: There are 2 connection
modes - optical cable connection and E1 connection.
i. Optical connection from RNC to NodeB: It is from the
third optical port of the APBE board in the RNC resource
frame to the OF1 port of the IIA board at the NodeB side.
Pay attention to the receiving and sending polarities. The
ACT and SD green indicators of the APBE board will be on
if the connection is correct, as shown in Figure 29. (If it is
wrong, reverse the receiving and sending polarities of the
optical cable.)

FI GU R E 29 OPTI C AL CAB L E CON N EC TI ON F R OM RNC TO NOD EB
The left figure is the APBE board interface of RNC and the right is the
IIA board interface of NodeB
ii. E1 Connection from RNC to NodeB:
It is from RDT B, the backboard corresponding to the DTB
board in the RNC resource frame, to E1 (1-8) and E1 (9-
16) of NodeB rack top. Pay attention to the receiving and

sending polarities. The E1 indicator of the DTB board will
flash at 1Hz if the connection is correct, as shown in
Figure 30.
FI GU R E 30 E1 CON N EC TI ON F R OM RNC TO NOD EB
The upper figure shows the RDTB board interface of RNC and the lower
figure shows the E1 connectors at the top of NodeB.
3. Connection of PWRD485: It is as shown in Figure 31.

FI GU R E 31 CON N EC TI ON OF PWRD485
Racks are connected one by one to form a cascade.
If racks are connected in cascade, it is required to configure the
485 address of PWRD board, the jumper working mode, and DIP
switch for each rack:
1. Set the 485 address of the last rack to the terminal
connection mode: set jumper switch at X8, and connect 1
with 2 and 9 with 10.
2. Except for the last rack, set the 485 address of racks to the
middle node connection mode: set jumper switch at X8, and
connect 3 with 4 and 7 with 8.
3. Set the 485 address of each rack according to the DIP switch
S3 of each rack PWRD in order: 0, 1, 2……15, with totally
sixteen rack addresses supported. For DIP switch, the upper
bits are of higher validity and lower ones are of lower validity.
Check of Cabinet Power Supply
1. Check whether the connection of the rack power cable is
correct according to the following steps: check whether the
power cable between the DC power distribution sub-rack and
the cabinet is well connected, whether the ground cable is
secure, and whether the polarities are correct (generally,
blue for -48V, black for -48VGND, and yellow-green for
protection GND), as shown in Figure 32.

FI GU R E 32 POW ER CAB L E CON N EC TI ON AT TH E RAC K TOP
2. Make sure all the boards are unplugged.
3. Check the RNC Hardware Installation Inspection Report to
make sure all the installation work has been finished.
4. Ask the related person to power on the RNC equipment. After
it is powered on, at the power inlet at the top of the RNC
cabinet backside, use a multimeter to measure the -48V
power of the DC distribution frame. Make sure the voltage is
-57V~-40V, as shown in Figure 33. Figure 34 shows the
cable connection of the multimeter.
FI GU R E 33 M EASU R E TH E CAB I N ET IN PU T V OL TAGE

FI GU R E 34 CAB L E CON N EC TI ON OF M U L TI METER (B L AC K F OR COM
I N TER F AC E AN D R ED F OR VOL TAGE I N TER F AC E)
Check List before Power-up
TAB L E 5 CH EC K LI ST B EF OR E POW ER -U P
Item Content and Criteria Result
Remar
k
Racks
Switch off the -48V power output from
the DC distribution frame to the cabinet
□ Pass
□ Fail
Switch off the two channels of -48V
power of the distribution frame
□ Pass
□ Fail
Switch off the -48V power of the filter
at the back of the distribution frame
□ Pass
□ Fail
Check whether the connection between
the filter on the top of a rack and the
power distribution sub-rack is tight and
whether any connector is loosened
(generally it is duly done upon delivery)
□ Pass
□ Fail

Remar
k
Make sure whether the connection
between the bus-bar at the back of the
cabinet and the power distribution sub-
rack is tight and whether all connecting
points on the bus-bar are sealed with
insulating sleeves (generally it is duly
done upon delivery)
□ Pass
□ Fail
Shelve
s
Make sure that the switch of each shelf
is in the state of OFF
□ Pass
□ Fail
Check whether the -48V power cable of
each fan sub-rack is correctly
connected and tight (generally it is duly
done upon delivery
□ Pass
□ Fail
Check whether the DIP switches of
each sub-rack are correct
□ Pass
□ Fail
Boards
Check the number of boards against
the configuration list of the system
□ Pass
□ Fail
Check whether the BOOT chip of each
board is installed and secure.
□ Pass
□ Fail
Check the PCB version number of the
boards and record the PCB version
number, the EPLD information, and the
EPLD and number information of the
sub-card
□ Pass
□ Fail
Check the input end of board power:
make sure the joint point is clean, and
there is no jam or short circuit
□ Pass
□ Fail
Check the DIP switch of the DTB board
according to the matching resistance of
E1 impedance provided by the
authority.
□ Pass
□ Fail
Check the jumper of the RDTB board:
check the jumper of RDTB board
according to the matching resistance of
E1 impedance provided by the
authority.
□ Pass
□ Fail
Interna
l
Cables
Check system clock cable connection
□ Pass
□ Fail
Check 8K clock cable
□ Pass
□ Fail

Remar
k
Check the cable connection in control
plane (if it is double-box configuration,
check the cable connection between the
two boxes)
□ Pass
□ Fail
Check PD485 cable
□ Pass
□ Fail
Check the fan monitor cable
□ Pass
□ Fail
Externa
l
Cables
Check the network cable of the network
management background OMCR (it
should be inserted into the OMC2 port
of RMPB)
□ Pass
□ Fail
Check the OMCB network cable (it
should be inserted into the first FE1
port of RMINC from upper to lower)
□ Pass
□ Fail
Check the structure and debugging
serial port cable (it shall be plugged
into the DEBUG2 port of the RMPB.)
□ Pass
□ Fail
Inter-
rack
Cables
Check the cable connection from RNC
to MGW NE
□ Pass
□ Fail
Check the cable connection from RNC
to SGSN NE
□ Pass
□ Fail
Check the optical cable connection from
RNC to NodeB
□ Pass
□ Fail
Check the E1 connection from RNC to
NodeB
□ Pass
□ Fail
Power
supply
Check whether the polarity of the -48V
power cable between the DC
distribution frame and the cabinet and
the -48VGND cable is correct
□ Pass
□ Fail
Check whether the connectors of the -
48V power cable between the DC
distribution frame and the cabinet and
the -48VGND cable are correct and
tight
□ Pass
□ Fail
Check whether the connection of the
ground cable between the DC
distribution frame and the cabinet is
correct and tight
□ Pass
□ Fail

Remar
k
Make sure all the boards are
unplugged.
□ Pass
□ Fail
Check the RNC hardware Installation
Quality Report to make sure all the
installation is done.
□ Pass
□ Fail
Switch on the -48V power output of the
DC distribution frame, and use a
multimeter to measure the -48V power
of the DC distribution frame, to make
sure the voltage shall be within -57V~-
40V
□ Pass
□ Fail
Check
Result
Is the equipment qualified for power-
up?
□Yes
□No
Remark
Equipment Power-up
Power-up Procedure
1. Firstly unplug all the boards from the slots.
2. Turn on the two-way -48V power switches on the panel of
the power distribution sub-rack at the rack top (sometimes
one-way in the experimental environment), as shown in
Figure 35.

FI GU R E 35 SW I TC H ES I N TH E TOP-L EF T COR N ER OF CAB I N ET
3. Turn on the -48V power switch on the filter at the back of
each sub-rack as shown in Figure 36.
FI GU R E 36 SU B -R AC K SW I TC H AT TH E BAC K OF CAB I N ET
4. Insert each board to the proper slot carefully.
Procedure of power on: Power on the racks---- Power on the
shelves--- Insert the boards one by one.
Power-down Procedure
The power-off procedure is reverse to the power-up procedure:

1. Turn off the -48V power switch on the filter at the back of
each sub-rack.
2. Turn off the two-way -48V power switches on the panel of the
power distribution sub-rack at the rack top.
Check After Power-up
Hardware Check
Fan Test
When the cabinet is powered on, perform fan power-on test in
the following procedure:
1. Plug out all the boards and fan modules;
2. Insert the fan modules one by one (Each rack has 9 fans.).
3. Observe the front top of the cabinet, the FAN indicator shall
be off and the RUN indicator of each fan should be always on, as
shown in Figure 37.
FI GU R E 37 CAB I N ET FAN RU N S NOR MAL L Y W I TH OU T AL AR MS
4. Check the fans one by one according to the steps below:
i. Insert a fan sub-rack into the rack;
ii. When the FAN indicator runs normally, draw out the
board if it exists right under the fan sub-rack;

iii. Dip a piece of narrow scrip with a length of about 20cm
into the sub-rack under the fan.
iv. For the group of fan sub-racks at the bottom of the rack,
dip a piece of narrow scrip to the sub-rack above the fan
sub-rack.
If the rotation direction is correct, the result shall be as
follows:
 The FAN indicator is always green;
 If the scrip is blowing upwards, indicating that the wind is
blowing from the rack bottom to the top.
 If the scrip is blowing downwards, the direction is wrong.
You shall change the fan sub-rack or check the power
cable connection inside the rack.
Board Status
Insert the boards properly one by one. The board status
indicators on the front panels of the boards shall be on. Ten
minutes later, when all the boards are running stably, the RUN
indicators of the boards shall flash periodically at 1Hz. If the
boards are in the active-standby configuration, the ACT indicator
of the active board shall be always on.
1. Because the ROMP board has two units - OMP and RPU, the
RUN1 and RUN2 indicators should flash normally and the
ACT1 and ACT2 indicators should be always on.
2. If there are only one RCB board, and since the two CPUs are
identical, the ACT1 and ACT2 indicators should be always on.
If there is more than one RCB board, they may be in the
alternative active mode. For example, if the ACT1 indicator is
of RCB1 is on and its ACT2 indicator is off, then the ACT2
indicator of RCB2 shall be on and its ACT1 indicator be off.
3. If there is more than one RUB board, they may be in the
load-sharing mode, which means the ACT indicators of all the
RUB boards shall be always on.
4. If the transmission is normal, the E1 indicator for the DTB
board shall flash normally at 1Hz.
If the board runs improperly, check the slot position and the
board power input. Refer to ZXWR RNC (V3.07.310) Radio
Network Controller Hardware Manual for detailed information
about board running status.
After the power-on of the system has been completed and
the system is in a stable running status, the indicator of each
board shall flash normally as shown in Figure 38 and Figure
39.

FI GU R E 38 NOR MAL IN D I C ATOR STATU S OF BOAR D S I N RNC RESOU R C E
FR AME
FI GU R E 39 NOR MAL IN D I C ATOR STATU S OF BOAR D S I N RNC CON TR OL
FR AME
Check List
TAB L E 6 CH EC K LI ST
Item Content and Criteria Result Remark

Item Content and Criteria Result Remark
Fan Status
The FAN indicator of every
running fan is off.
The RUN indicator of every
running fan is on.
□ Pass □
Fail
Fan Direction The fan direction is normal. □ Pass □
Fail
GIPI The fan direction is normal. □ Pass □
Fail
UIMU Board indicators are on. □ Pass □
Fail
RGUB Board indicators are on. □ Pass □
Fail
APBE Board indicators are on. □ Pass □
Fail
RUB The fan direction is normal. □ Pass □
Fail
RCB Board indicators are on. □ Pass □
Fail
UIMC Board indicators are on. □ Pass □
Fail
ROMP Board indicators are on. □ Pass □
Fail
CLKG Board indicators are on. □ Pass □
Fail
CHUB Board indicators are on. □ Pass □
Fail
Check
Result
Is the equipmentnormal
after power-up? □ Yes □ No
Remarks
Table of Board Information
The following is a table containing detailed information of the
boards.
TAB L E 7 TAB L E OF BOAR D IN F OR MATI ON
Na
me
PCB Version No. EPLD Information
Sub-card
EPLD
Quant
ity
AP
BE
H010APBE-
4SM_040600
APBE.0406.D21.101/APBE.
0406.D32.100
MPB0.040
3.D10.050
402
1
RU
B
H0101RUB_0405
01
VTCD.0405.D11.102 1

Na
me
PCB Version No. EPLD Information
Sub-card
EPLD
Quant
ity
GIP
I
H0101MNIC/2_0
60201
GLIQV.0402.D12.101 1
RG
UB
H0101RGUB_04
0202
MNIC.0402.D3.107/MNIC.0
402.D4.107
1
RO
MB
H0101ROMB_04
0202
MPX86.0402.D36.106 1

C h a p t e r 3
Software Version
Management
Overview
This chapter describes the functions of the software version
management of the 3.07.310 network management system,
particularly including the operations related to the lib version,
default version, and appointed version.
Operation Flow Description
The foreground and background software version manage ment
has undergone big changes since V3.05.120. In the past, version
management used to take an all-table flow. That is, through all-
table synchronization, the data of software version management
was transferred in the form of zdb to the foreground by FTP. In
this way, the foreground provided FTP service, while the
background served as the client. Since the 120 series, the all-
table flow has been replaced by a message flow, that is, the
background sends a message to the foreground, and the
foreground responds to the message, writes the result into the
foreground ZDB table, and returns the results of processing to
the background; according to the results, the background
operates the background database.
Frequently Used Terms
Lib Version
A lib version is a version that needs to be loaded before it runs
when the foreground OMP and boards start. By configuring a lib

version, we can ensure normal running of the foreground
network elements and provide stable and reliable operation and
maintenance functions, so as to guarantee smooth version
replacement and satisfy version loading requirements during
version upgrade and expansion.
Default Version
To load a version of any foreground board, we need to configure
a default version. That is, when a peripheral board requests the
OMP to load a version, the OMP will check the foreground default
version table to see whether there is an appropriate version type
needed by this peripheral board. If there is such a version type,
we can use it to find its filename and checksum in t he
foreground library table, and download this version to the
peripheral board. If the default version has no version type
needed by the peripheral board, the peripheral board will
continuously request the OMP for a version until it obtains an
executable version. In this case, it is a peripheral board that
requests actively the OMP to load a version, and when the OMP
default version table is updated, the OMP will broadcast to
peripheral boards that there are updated version types for them
to request. As for default version switching, it means the
background sends to the foreground a default version switching
request that indicates seven property values: logical board type,
version type, functional board type, physical board type, CPU,
PCB, and version number. Upon receipt of this request, the
foreground, according to these seven property values, will check
the library version table to see whether there is such a version.
If there is, the foreground will write the foreground default
version table and multicast it to peripheral board.
Appointed Version
An appointed version is relative to a default version, and is
applicable for the specified physical board to load, that is, the
version is appointed for a certain specified board.
The CPU version of the ROMP must be appointed.
Descriptions of the Toolbar Icons
FI GU R E 40 TOOL B AR IC ON S

Chapter 3 Software Version Management
Description of the icons:
: Create Version File (to put a
single version into the library)
: Batch Create Version File (to put
batch versions into the library)
: Query OMP Version (to
query the initial OMP version)
: Query Startup Mode of ROMP (to
query the startup mode of the foreground
board)
: Set OMC FTP Parameter (to
setthe OMC FTP parameters)
: Software Backup (to make a
backup of the software)
: Software Recovery (to
restore the software)
: Software Consistency Comparison
(to compare software consistency)
: Query by logical board type
(to query a logical version)
: Synchronize versions from NE (to
synchronize version data from the
foreground to the background)
Lib Version Management
Lib Version Information
Table 8 lists the version files that need to be loaded for all the
RNC boards at present.
TAB L E 8 RNC BOAR D WAR EH OU SI N G IN F OR MATI ON
No
.
RNC Board
Information
Parts of the Board Requiring
Version Warehousing
Remarks
Logic
al
Board
Name
Physic
al
Board
Name
CPU
(exten
sion
name)
FPGA
(exten
sion
name)
Microco
de
(extensi
on
name)
DSP
(exten
sion
name)
1
ROM
P
MPX86
_2
BIN RBF
Indicating
these boards
use the
physical board
2 RPU
MPX86
_2
BIN RBF

3 RCP
MPX86
_2
BIN RBF
MPX86_2.
And for these
boards, it is
required to
warehouse
software
respectively
for CPU and
FPGA.
4 UIM UIM_2 BIN BIN
5 DTB DTB BIN
6 SDTB SDTB BIN
7 RUB VTCD BIN BIN
8 RAP APBE BIN PKG
9 IMAB IMAB BIN BIN PKG
10 GIPI MNIC BIN UOF
11 CHUB CHUB BIN
12 CLK
13 PSN PSN
14 GLI GLI
15 PWB
Note: For the parts crossed with a slash,software warehousing is unneeded.
Putting a Single Version into the
Library
Click the <Create Version File> icon in the toolbar, and a
dialogue box will pop up. Select a file that needs to be put into
the library, as shown in Figure 41.

FI GU R E 41 PU T A SI N GL E V ER SI ON I N TO TH E LI B R AR Y
Click <Open> to shown the version contents, as shown in Figure
42.
FI GU R E 42 LI B V ER SI ON IN F OR MATI ON
Input a User Label, and click <Confirm> to start loading the
version.
When the version is loaded completely, a prompt dialogue box
pops up, as shown in Figure 43.

FI GU R E 43 PR OMPT IN F OR MATI ON
If the loading is successful, one more entry will be added into
the lib version list.
Putting Batch Versions into the
Library
File version consists of two parts: 1) the CPU file of each board;
2) the FPGA file for the ROMB, RCB and UIM boards. The process
of putting all the board software versions into the library is as
follows:
Click the <Batch Create Version File> icon in the toolbar,
and a dialogue box will pop up, as shown in Figure 44.
FI GU R E 44 PU T BATC H V ER SI ON S I N TO LI B R AR Y
Select the path of the file that needs to be put into the library.
For the 3010 version, the user only needs to select the directory
of the version file, which contains a CPU version file and a FPGA
version file, as shown in Figure 45.

FI GU R E 45 PATH OF PU TTI N G BATC H V ER SI ON S I N TO TH E LI B R AR Y
Click <Confirm> to show the Batch Put Version to Lib
dialogue box, as shown in Figure 46.
FI GU R E 46 IN F OR MATI ON OF TH E BATC H V ER SI ON FI L ES TO B E PU T I N TO TH E
LI B R AR Y
Select the version files that need to put into the library, and
input a User Label, as shown in Figure 47.

FI GU R E 47 IN F OR MATI ON OF TH E BATC H V ER SI ON S TO B E PU T I N TO TH E
LI B R AR Y
Click <Confirm>, and a loading progress box pops up, as shown
in Figure 48. The version files will then be transferred to the
server.
FI GU R E 48 BATC H V ER SI ON UPL OAD I N G
When the versions are loaded completely, a prompt box will pop
up, indicating the results of this batch version loading, as shown
in Figure 49.

FI GU R E 49 RESU L TS OF BATC H WAR EH OU SI N G
For the successfully loaded files, their corresponding entries are
added into the Lib Version tab, including the CPU and FPGA
files, as shown in Figure 50.
FI GU R E 50 IN F OR MATI ON OF TH E BATC H LI B V ER SI ON S
Lib Version Functions
The Lib Version tab displays all the entries of the background
lib version table, and the lib version provides six functions as
follows:
 Create Version File: Only one version can be selected to
warehouse to the background at a time.
 Batch Create Version File: One directory can be selected at a
time, and all available versions under this directory will be
warehoused to the background.
 Add Version To ROMP: When a version is downloaded to the
foreground successfully, modify its file state to downloaded.
 Delete Version File From ROMP: For a version in the
downloaded state, start deleting it from the foreground, that
is, delete this version from the foreground lib version list.
When it is deleted successfully from the foreground, its
version state turns into not downloaded.
 Create OMP Version: Select both CPU version and FPGA
version needed for constructing the ROMP startup version.

Click the Create OMP Version menu. Upon successful
creation, the files needed for startup of the ROMP are saved
under the directory $[ums-svr] of the server. These files
include the ompcfg.ini file, CPU version file, and FPGA file
without header.
 Modify User Label: This function is used to modify a user
label.
 Export Table Data: This function is used to export data to a
specified Excel table.
The Add Version To ROMP and Delete Version File From
ROMP operations provide batch operation functions, that is,
more than one version can be selected for these operations.
Adding Version to ROMP
In the Lib Version tab, select the version files you want to add,
right-click to show the shortcut menu, as shown in Figure 51.
FI GU R E 51 AD D V ER SI ON TO ROM P
Click Add Version To ROMP to show the version adding
progress box, as shown in Figure 52.
FI GU R E 52 V ER SI ON LOAD I N G PR OGR ESS
When the version is added completely, a result box will pop up,

FI GU R E 53 RESU L TS OF AD D I N G BATC H V ER SI ON S TO ROM P
When the versions are added successfully, the Lib Version tab
displays these versions in the downloaded state, as shown in
Figure 54.
FI GU R E 54 STATE OF TH E FI L ES AD D ED TO ROM P
Deleting Version File from ROMP
In the Lib Version tab, select a version in the downloaded
state, right-click to select Delete Version File From ROMP, as
shown in Figure 55.

FI GU R E 55 DEL ETE V ER SI ON FI L E F R OM ROM P
Click Delete Version File From ROMP, and a confirmation
dialogue box will pop up, as shown in Figure 56.
FI GU R E 56 DI AL OGU E BOX F OR CON F I R MI N G DEL ETI ON F R OM ROM P
Click <OK> to delete the selected version file, and soon a
prompt box will pop up, indicating the operation result, as shown
in Figure 57.
FI GU R E 57 RESU L T OF DEL ETI N G TH E V ER SI ON F R OM ROM P
Note:
The version file appointed by the foreground as a default version
cannot be deleted from the foreground. It is necessary to
perform default version switching first to change this version file
to a non-default version, and then delete it from ROMP.
Otherwise, the deletion may fail. If there is only one default
version file, the ROMP forbids the operation of deleting it.

Creating OMP Version
Select the CPU version file of the ROMP and the FPGA version file
with the corresponding PCB number, and right-click to select
Create OMP Version, as shown in Figure 58.
FI GU R E 58 CR EATE OM P V ER SI ON
Click Create OMP Version to construct the ROMP version, and
a dialogue box will pop up, as shown in Figure 59.
FI GU R E 59 DI AL OGU E BOX F OR CR EATI N G OM P V ER SI ON
Upon successful creation, the files needed for startup of the
ROMP are saved under the directory $[ums-svr] of the server.
These files include the ompcfg.ini file, CPU version file, and FPGA
file without header, as shown in Figure 60.

FI GU R E 60 IN F OR MATI ON OF CR EATED V ER SI ON FI L ES
Modifying User Label
Select the file whose user label needs to be changed, right -click
to show the shortcut menu, and click Modify User Label, as
shown in Figure 61.
FI GU R E 61 M OD I F Y USER LAB EL
Type a new label, and click <Confirm>, as shown in Figure 62.
FI GU R E 62 CON F I R M USER LAB EL M OD I F I C ATI ON

The label is modified successfully, as shown in Figure 63.
FI GU R E 63 USER LAB EL M OD I F I C ATI ON COMPL ETED
Exporting Table Data
Right-click to show the shortcut menu, and clic k Export Table
Data, as shown in Figure 64.
FI GU R E 64 EXPOR T TAB L E DATA
Type the name and path of the file, and click <Save>, as shown
in Figure 65.
FI GU R E 65 TYPE TH E FI L E NAME
The file is saved successfully.

Default Version Management
When the version file in the Lib Version tab is added into the
foreground successfully, its corresponding entry will be added in
the Default Version tab, as shown in Figure 66. At that time,
the default version has not been activated yet, the version File
name is empty, and the New Version No. is Not configured.
FI GU R E 66 DEF AU L T V ER SI ON
Single Default Version Switching
Select the version file to be switched, and right-click Default
Version Switching, as shown in Figure 67.
FI GU R E 67 SI N GL E DEF AU L T V ER SI ON SW I TC H I N G
Click Default Version Switching to show the Default Version
Switching dialogue box, as shown in Figure 68.

FI GU R E 68 DEF AU L T V ER SI ON SW I TC H I N G
Select a version number, change all the options to No, and click
<Confirm> to switch the version file.
When the version is loaded completely, a dialogue box will pop
up, indicating the default version switch result, as shown in
Figure 69.
FI GU R E 69 DEF AU L T V ER SI ON SW I TC H I N G RESU L T

Batch Default Version Switching
Select the version files to be switched, and right-click Default
FI GU R E 70 BATC H DEF AU L T V ER SI ON SW I TC H I N G
Click Default Version Switching to show the Default Version
Switching dialogue box, as shown in Figure 71.
Select the version number to be switched, set if restart
immediately to No, and click <Confirm> to show the switching
progress dialogue box.
The Default Version tab will display the File name and New
version No. of the successfully switched versions, as shown in
Figure 72.

FI GU R E 72 STATE OF TH E SU C C ESSF U L L Y SW I TC H ED DEF AU L T V ER SI ON S
When the versions are switched completely, a dialogue box will
pop up, indicating the default version switching result, as shown
in Figure 73.
FI GU R E 73 BATC H DEF AU L T V ER SI ON SW I TC H RESU L T
Manually start the switched boards to enable them to obtain the
new versions from the ROMP, that is, to activate the newly
switched version files.
Query whether the foreground boards have been switched
correctly, as shown in Figure 74.

FI GU R E 74 QU ER Y I F TH E FOR EGR OU N D BOAR D H AS B EEN SW I TC H ED
SU C C ESSF U L L Y
Appointed Version
Management

Appointed Version Loading
In the Appointed Version tab, right-click to select Appointed
FI GU R E 75 APPOI N TED V ER SI ON
Click Appointed Version Switching to show the Appointed
Version Switching dialogue box, as shown in Figure 76.
FI GU R E 76 APPOI N TED V ER SI ON SW I TC H I N G
Click the dropdown menu of the version file name option, and
select a version file you want to appoint, as shown in Figure 77
and Figure 78.

FI GU R E 77 IN F OR MATI ON OF TH E CPU FI L E OF TH E APPOI N TED V ER SI ON
FI GU R E 78 IN F OR MATI ON OF TH E FPGA FI L E OF TH E APPOI N TED V ER SI ON

Input Rack No., Shelf No., Slot No., and CPU No., and click
<Confirm> to switch the appointed version. Upon successful
switching, a corresponding entry is added in the Appointed
Version tab.
If the ROMP works in the active-standby mode, the user just
needs to repeat Steps 3 and 4, as shown in Figure 79 and Figure
80.
FI GU R E 79 IN F OR MATI ON OF TH E CPU FI L E OF TH E APPOI N TED V ER SI ON

FI GU R E 80 IN F OR MATI ON OF TH E FPGA FI L E OF TH E APPOI N TED V ER SI ON
Canceling Appointed Version
In the Appointed Version tab, select the version file you want
to cancel, and right-click to select Appointed Version
Switching Cancel, as shown in Figure 81.
FI GU R E 81 CAN C EL APPOI N TED V ER SI ON SW I TC H I N G
Click Appointed Version Switching Cancel, and a confirmation
dialogue box will pop up, as shown in Figure 82.

FI GU R E 82 CON F I R M W H ETH ER TO CAN C EL APPOI N TED V ER SI ON SW I TC H I N G
Click <OK> to send to the foreground a request to cancel
appointed version switching, and cancel the version appointed
for the CPU. The foreground will feed back operation
performance result, as shown in Figure 83.
FI GU R E 83 RESU L T OF CAN C EL I N G APPOI N TED V ER SI ON SW I TC H I N G
Upon successful cancellation of appointed version switching, the
corresponding entry will be deleted from the Appointed
Version.
Note:
For the appointed version of ROMP, appointed version switching
cannot be cancelled.

Other functions of Software
Version Management
OMP Version Query
Click the <Query OMP Version> icon in the toolbar to view
the OMP startup version, as shown in Figure 84.
FI GU R E 84 QU ER Y OM P V ER SI ON
OMP Startup Mode Query
Click the <Query Startup Mode of ROMP> icon in the
toolbar to check the startup mode of the construction OMP. The
startup mode interface also provides the option of “Restart from
RNC”, as shown in Figure 85.
FI GU R E 85 QU ER Y TH E STAR TU P M OD E OF ROM P
Software Version Backup
Click the <Software Backup> icon in the toolbar, and a
confirmation dialogue box will pop up, as shown in Figure 86.

FI GU R E 86 SOF TW AR E BAC K U P
Click <OK> to show the software backup address dialogue box,
FI GU R E 87 SOF TW AR E BAC K U P PATH
Select the path for saving the file, and click <Confirm> to
perform software backup, as shown in Figure 88.
FI GU R E 88 QU ER Y OM P V ER SI ON
When the backup is completed, the backup result is displayed,

FI GU R E 89 SOF TW AR E BAC K U P PR OMPT
Software Version Recovery
Click the <Software Recovery> icon in the toolbar, and a
dialogue box will pop up. Select the software backup address, as
shown in Figure 90.
FI GU R E 90 SOF TW AR E R EC OVER Y
Select the software backup address, and click <Confirm> to
start recovery of the software version.
Software Version Consistency
Comparison
Click the <Software Consistency Comparison> icon in the
toolbar to show an interface displaying the consistency between
the foreground and background lib versions, and between the
entries in the default version and appointed version table, as
shown in Figure 91.

FI GU R E 91 SOF TW AR E V ER SI ON CON SI STEN C Y COMPAR I SON
Lib Version Comparison
The consistency comparison interface provides two operations of
Synchronize to ROMP and Delete From ROMP in the Lib
Version tab, as shown in Figure 92.
FI GU R E 92 LI B V ER SI ON CON SI STEN C Y COMPAR I SON
Synchronize to ROMP means to download the version to the
ROMP; while Delete From ROMP means to delete this version
from the ROMP. Both operations support the batch mode.

Default Version Comparison
Like the Lib Version tab, the Default Version tab also
provides two operations: Synchronize to ROMP and
Delete Default Version From OMC, as shown in Figure
93.
FI GU R E 93 DEF AU L T V ER SI ON CON SI STEN C Y COMPAR I SON
Synchronize to ROMP means to originate default version
switching for once. During this operation, the system pops up
the default version switching interface, in which users can
reselect a version number, as shown in Figure 94, to initiate
version switching to the ROMP.

Delete Default Version From OMC allows users to delete the
entries from the OMC default versions in the case of the Only
Exist on OMC state. This operation will not send any message
to ROMP.
Appointed Version Comparison
The Appointed Version tab provides the operations of
Synchronize to ROMP and Cancel Appointed Version, as
shown in Figure 95.

FI GU R E 95 APPOI N TED V ER SI ON CON SI STEN C Y COMPAR I SON
Synchronize to ROMP means to initiate appointed version
switching for once, that is, to send to the ROMP a request for
appointed version switching. Cancel Appointed Version means
to send to the ROMP a request for canceling an appointed
version. Neither of these operations supports the batch mode.
When a version is in the Consistency state, both of these
operations are in gray, indicating they are disabled.
Note:
For an appointed version of ROMP, the foreground does not write
an appointed table, but a boot configuration file. Comparison of
consistency between foreground and background is intended to
compare the consistency of the corresponding table of ROMP, so
the appointed version of ROMP is not included in this comparison.
Query Foreground and Background
Versions by Logical Board Type
Click the <Query by logical board type> icon in the toolbar,
and an interface will pop up to display the version entries of the
DEFAULT type in the background lib version, default version, and
appointed version, as shown in Figure 96. This interface provides
query of foreground and background versions by logical board
type.

FI GU R E 96 LOGI C AL V ER SI ON QU ER Y
Note:
This function queries entries from the foreground and
background corresponding tables. For the appointed version of
ROMP, the background writes the appointed version table, while
the foreground writes the configuration file, so it is possible that
there is an entry of the appointed version of ROMP when queried
from the background, while this entry cannot be found when
queried from the foreground.
Synchronizing Version Data from the
Foreground to the Background
Click the <Synchronize versions from NE> icon in the
toolbar, and a dialogue box will pop up, as shown in Figure 97.
FI GU R E 97 SYN C H R ON I Z E V ER SI ON DATA F R OM TH E FOR EGR OU N D TO TH E
BAC K GR OU N D

Click <OK> to show the progress bar, as shown in Figure 98.
FI GU R E 98 PR OGR ESS BAR (1)
The progress bar indicates the ongoing loading of the foreground
version to the background temporary directory, as shown in
Figure 99.
Figure 99 Progress Bar (2)
The progress bar displays deletion of the background version
file, and copying the foreground version to the background, as
shown in Figure 100.
FI GU R E 100 DI SPL AY BAC K GR OU N D V ER SI ON FI L ES AF TER DEL ETI ON

When the operation succeeds, a prompt dialogue box will pop
up, as shown in Figure 101.
FI GU R E 101 OPER ATI ON SU C C ESSF U L
Configuring OMC FTP Parameter
Click the icon in the toolbar, and a dialogue box will pop up,
FI GU R E 102 CON F I GU R E OM C FTP PAR AMETER
Input the parameters, and click <Confirm> to complete the
configuration.

Figures
Figure 1 ZXWR RNC Commissioning Flowchart .......................6
Figure 2 Flowchart of Check before Power-up ........................7
Figure 3 Switches in the Top-left Corner of Cabinet Front Panel 8
Figure 4 Switch for the Cabinet Rear Sub-rack.......................9
Figure 5 Filters and Power Distribution Sub-rack at the Cabinet
Rear-top Side ...................................................................9
Figure 6 Connection Diagram of Bus-bar and Power Distribution
Sub-rack........................................................................ 10
Figure 7 Connection Diagram of Fan Power Cables ............... 11
Figure 8 Diagram of RNC Shelf DIP Switch.......................... 12
Figure 9 DIP Switch Value of SHELF 1, RACK 1, TRIB 0 ......... 13
Figure 10 DIP Switch Value of SHELF 2, RACK 1, TRIB 0........ 13
Figure 11 Location of BOOT Chip on the Board..................... 14
Figure 12 Location of Board PCB Number ............................ 15
Figure 13 Power Input End of the Board ............................. 15
Figure 14 Structure of the DTB board................................. 16
Figure 15 Diagram of the RDT B Board Jumpers.................... 17
Figure 16 Connection of Internal Cables ............................. 18
Figure 17 Structure of System Clock Cable H-CLK-003.......... 19
Figure 18 Connection of Clock Cable .................................. 19
Figure 19 Structure of H-CLK-004 8K Clock Cable ................ 21
Figure 20 Connection of 8K Clock Cable.............................. 22
Figure 21 H-ETH-008 Cable Structure in Control Plane .......... 23
Figure 22 Cable Connection between Control Frame and
Resource Frame .............................................................. 24
Figure 23 H-ETH-009 Structure of PD485 Cable ................... 24
Figure 24 Connection of PD485 Cable................................. 25
Figure 25 Connection of Fan Monitoring Cable ..................... 26
Figure 26 External Connection of RNC Rack......................... 27

Figure 27 Optical Cable Connection from RNC to MGW .......... 29
Figure 28 Optical Cable Connection from RNC to SGSN ......... 30
Figure 29 Optical Cable Connection from RNC to NodeB ........ 31
Figure 30 E1 Connection from RNC to NodeB ...................... 32
Figure 31 Connection of PWRD485 .................................... 33
Figure 32 Power Cable Connection at the Rack Top .............. 34
Figure 33 Measure the Cabinet Input Voltage ...................... 34
Figure 34 Cable Connection of Multimeter (black for COM
interface and red for voltage interface) ............................... 35
Figure 35 Switches in the Top-left Corner of Cabinet ............ 39
Figure 36 Sub-rack Switch at the Back of Cabinet ................ 39
Figure 37 Cabinet Fan Runs Normally without Alarms ........... 40
Figure 38 Normal Indicator Status of Boards in RNC Resource
Frame ........................................................................... 42
Figure 39 Normal Indicator Status of Boards in RNC Control
Frame ........................................................................... 42
Figure 40 Toolbar Icons................................................. 46
Figure 41 Put a Single Version into the Library .................... 49
Figure 42 Lib Version Information ..................................... 49
Figure 43 Prompt Information .......................................... 50
Figure 44 Put Batch Versions into Library ........................... 50
Figure 45 Path of Putting Batch Versions into the Library ....... 51
Figure 46 Information of the Batch Version Files to be Put into
the Library ..................................................................... 51
Figure 47 Information of the Batch Versions to be Put into the
Library .......................................................................... 52
Figure 48 Batch Version Uploading .................................... 52
Figure 49 Results of Batch Warehousing ............................. 53
Figure 50 Information of the Batch Lib Versions ................... 53
Figure 51 Add Version to ROMP ........................................ 54
Figure 52 Version Loading Progress ................................... 54
Figure 53 Results of Adding Batch Versions to ROMP ............ 55
Figure 54 State of the Files Added to ROMP ........................ 55
Figure 55 Delete Version File from ROMP ............................ 56
Figure 56 Dialogue Box for Confirming Deletion from ROMP ... 56
Figure 57 Result of Deleting the Version from ROMP ............. 56
Figure 58 Create OMP Version .......................................... 57
Figure 59 Dialogue Box for Creating OMP Version ................ 57

Figure 60 Information of Created Version Files .................... 58
Figure 61 Modify User Label ............................................. 58
Figure 62 Confirm User Label Modification........................... 58
Figure 63 User Label Modification Completed....................... 59
Figure 64 Export Table Data ............................................. 59
Figure 65 Type the File Name ........................................... 59
Figure 66 Default Version ................................................ 60
Figure 67 Single Default Version Switching ......................... 60
Figure 68 Default Version Switching................................... 61
Figure 69 Default Version Switching Result ......................... 61
Figure 70 Batch Default Version Switching .......................... 62
Figure 71 Default Version Switching................................... 62
Figure 72 State of the Successfully Switched Default Versions 63
Figure 73 Batch Default Version Switch Result ..................... 63
Figure 74 Query if the Foreground Board has been Switched
Successfully ................................................................... 64
Figure 75 Appointed Version............................................. 65
Figure 76 Appointed Version Switching ............................... 65
Figure 77 Information of the CPU File of the Appointed Version
.................................................................................... 66
Figure 78 Information of the FPGA File of the Appointed Version
.................................................................................... 66
Figure 79 Information of the CPU File of the Appointed Version
.................................................................................... 67
Figure 80 Information of the FPGA File of the Appointed Version
.................................................................................... 68
Figure 81 Cancel Appointed Version Switching ..................... 68
Figure 82 Confirm whether to Cancel Appointed Version
Switching....................................................................... 69
Figure 83 Result of Canceling Appointed Version Switching .... 69
Figure 84 Query OMP Version ........................................... 70
Figure 85 Query the Startup Mode of ROMP ........................ 70
Figure 86 Software Backup .............................................. 71
Figure 87 Software Backup Path........................................ 71
Figure 88 Query OMP Version ........................................... 71
Figure 89 Software Backup Prompt .................................... 72
Figure 90 Software recovery............................................. 72
Figure 91 Software Version Consistency Comparison ............ 73

Figure 92 Lib Version Consistency Comparison .................... 73
Figure 93 Default Version Consistency Comparison............... 74
Figure 94 Default Version Switching .................................. 75
Figure 95 Appointed Version Consistency Comparison........... 76
Figure 96 Logical Version Query........................................ 77
Figure 97 Synchronize Version Data from the Foreground to the
Background.................................................................... 77
Figure 98 Progress Bar (1) ............................................... 78
Figure 99 Progress Bar (2) ............................................... 78
Figure 100 Display Background Version Files after Deletion.... 78
Figure 101 Operation Successful ....................................... 79
Figure 102 Configure OMC FTP Parameter........................... 79

Tables
Table 1 Chapter Summary ..................................................i
Table 2 Typographical Conventions...................................... ii
Table 3 Mouse Operation Conventions ................................. iii
Table 4 DTB Switch Settings for 75 /120  Resistance ........ 16
Table 5 Check List before Power-up ................................... 35
Table 6 Check List .......................................................... 42
Table 7 Table of Board Information.................................... 43
Table 8 RNC Board Warehousing Information ...................... 47

Umtsrns 210 rnc commissioning preparation

Recommended

Recommended

More Related Content

Similar to Umtsrns 210 rnc commissioning preparation

Similar to Umtsrns 210 rnc commissioning preparation (20)

More from Jose Asuncion Silva Vasquez

More from Jose Asuncion Silva Vasquez (20)

Recently uploaded

Recently uploaded (20)

Umtsrns 210 rnc commissioning preparation