PDF ZXWR RNC v31110 Radio Network Controller Calling Trace Operation Guide - Compress PDF

ZXWR RNC
Radio Network Controller

Calling Trace Operation Guide
Version: V3.11.10
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2011 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.
Revision History
Revision No. Revision Date Revision Reason
R1.1 2011-11-30 The manual structure and all sections are modified
R1.0 2011-07-26 First Edition (V3.11.10.05)
Serial Number: SJ-20110704093842-017
Publishing Date: 2011-07-26 (R1.1)

Contents
About This Manual ......................................................................................... I
Chapter 1 Overview .................................................................................... 1-1
1.1 Software Functions............................................................................................. 1-1
1.2 User Interface of the RNC Call Trace Software..................................................... 1-1
1.3 Software Modules .............................................................................................. 1-3
1.3.1 Overview of Software Modules .................................................................. 1-3
1.3.2 CT Client Module ..................................................................................... 1-4
1.3.3 CT Server Module .................................................................................... 1-4
1.3.4 CT Manager Module................................................................................. 1-4
1.3.5 CT Agent Module ..................................................................................... 1-4
1.3.6 RNL/TNL Module ..................................................................................... 1-5
1.4 Deployment Methods.......................................................................................... 1-5
1.4.1 Overview of Deployment Methods ............................................................. 1-5
1.4.2 Independent Server Deployment ............................................................... 1-5
1.4.3 Sharing EMS Server Deployment .............................................................. 1-6
1.4.4 Local NE Deployment ............................................................................... 1-7
1.5 Basic Concepts about Tasks ............................................................................... 1-8
1.5.1 Overview ................................................................................................. 1-8
1.5.2 Life Cycle of a Task .................................................................................. 1-8
1.5.3 Task Types .............................................................................................. 1-9
Chapter 2 Basic Operations ...................................................................... 2-1

2.1 Starting the RCT Server...................................................................................... 2-1
2.2 Starting the RCT Client ...................................................................................... 2-2
2.3 Network Element Management ........................................................................... 2-2
2.3.1 Adding an NE........................................................................................... 2-2
2.3.2 Connecting to an NE ................................................................................ 2-4
2.4 Subscriber Trace ................................................................................................ 2-4
2.4.1 Opening the Subscriber Trace Window ...................................................... 2-4
2.4.2 Creating Tasks ......................................................................................... 2-5
2.4.3 Call Trace Task Management .................................................................... 2-8
2.4.4 Viewing a Data File ................................................................................ 2-12
Appendix A Installation of the RCT Software ......................................... A-1

A.1 Overview ........................................................................................................... A-1
I
A.2 Installing the RCT Software ................................................................................ A-1
A.3 Configuring Port Offset ..................................................................................... A-11
A.4 Configuring and Starting the Message Route Module ......................................... A-13
Appendix B Troubleshooting ................................................................... B-1

B.1 Task Status Is Always Starting ............................................................................ B-1
B.2 RCT Server Fails to Be Started........................................................................... B-1
Figures............................................................................................................. I
Tables ............................................................................................................ III
Glossary .........................................................................................................V
II
About This Manual
Purpose
This manual presents the basic concepts and operation instructions on the RNC Call Trace
(RCT) software. It also provides methods for troubleshooting common faults.
Intended Audience
l Network optimization engineers
l Maintenance engineers
l Test engineers
What Is in This Manual

This manual includes four chapters and two appendixes.
Chapter Summary
Chapter 1, Overview Describes the basic functionality, modules,

deployment, and of the RCT software, and
explains the basic concepts of tasks .
Chapter 2, Basic Operations Describes the basic operations of the RCT

software.
Appendix A, Software Installation Describes the installation procedures of the RCT

software.
Appendix B, Troubleshooting Describes the solutions to two common faults.
I
II
Chapter 1
Overview
Table of Contents
Software Functions.....................................................................................................1-1
User Interface of the RNC Call Trace Software...........................................................1-1
Software Modules ......................................................................................................1-3
Deployment Methods .................................................................................................1-5
Basic Concepts about Tasks.......................................................................................1-8
1.1 Software Functions

The RNC Call Trace (RCT) software is an independent software for managing the call trace
tasks of multiple NEs. The server supports simultaneous access of multiple clients.
When errors occur with the network, calls break down, services become abnormal, or users
are optimizing the network, the call trace software can be used to locate and analyze faults.
For those faults that can not be traced, the call trace software can help users determine
the troubleshooting procedures with the traced signaling.
With the call trace software, users can easily trace the real-time signaling of RNCs and
view related measurement reports. In addition, it can help the maintenance personnel
locate faults and debug the system.
The tasks included in the call trace software include the call trace tasks and measurement
trace tasks, aiming at such objects as mobile stations, cells and each network interface.
The system can provide call trace tasks at both radio network layer and transmission
network layer at the same time.
For such functions as system monitoring, rights control, and log management related to
the call trace software, refer to the following documents:
l NetNumen U31 Unified Element Management System Security Management
Operation Guide
l NetNumen U31 Unified Element Management System System Management
Operation Guide
1.2 User Interface of the RNC Call Trace Software

This section illustrates the different parts of the user interface of the RNC Call Trace (RCT)
software, with details about the buttons on the tool bar.
Figure 1-1 shows the RCT software.
1-1
SJ-20110704093842-017|2011-07-26 (R1.1) ZTE Proprietary and Confidential

ZXWR RNC Calling Trace Operation Guide
Figure 1-1 RCT Client Interface
1. Menu bar 3. Navigation tree 5. Status bar

2. Tool bar 4. Working area
As shown in Figure 1-1, the call trace software client is made up of five parts. The function
of each part is described as follows:
1. Menu bar
The call trace software menu provides the commands for call trace operations and
related operations. Users can perform different call trace tasks and related tasks by
using the menu commands.
2. Tool bar
The tool bar of the RCT software provides six shortcut buttons, as described in Table
1-1.
Table 1-1 Description of Shortcut Buttons
Name Short Icon
Logout
Lock Screen
Window Back
Window Forward
1-2

Chapter 1 Overview
Name Short Icon
Subscriber Trace
NE Management
3. Navigation tree
The navigation tree provides command nodes for the current open module.
Double-click a command node in the tree to perform a specific operation.
4. Working area
The working area has two tabs: Signaling, Task Manager, which displays signaling
information and task list.
5. Status bar
The status bar displays the status of the communication between the RCT client and
the RNC.
1.3 Software Modules

1.3.1 Overview of Software Modules
The call trace software consists of the following modules:
l Call Trace (CT) Client module
l CT Server Module
l CT Manager module, located on the ROMP board
l CT Agent module, located on each board of the RNC
l Radio Network Layer (RNL)/Transmission Network Layer (TNL) module
The relationships among all modules are shown in Figure 1-2.
Figure 1-2 Module Architecture of the Call Trace Software
1-3

1.3.2 CT Client Module

The Call Trace (CT) client is an independent module. It refers to the client of the call trace
software , which needs to be connected to the server to perform call trace operations,
including
l Customizing signaling trace tasks
l Starting signaling trace tasks
l Querying signaling trace results
1.3.3 CT Server Module

The CT Server module is an independent module . It refers to the call trace software
server, which connects to the RNC and forwards the signaling trace tasks of the CT Client
module.
The CT Server connects to the ROMP board of the RNC, communicating with the CT
Manager module on the ROMP board, and obtaining target signaling messages for call
trace tasks.
1.3.4 CT Manager Module

The CT Manager module is located on the ROMP board. The function of the module is
to trace the forwarding of control messages and the summary of data messages. The
procedure is described as follows:
l The CT Manager receives the trace control messages from the CT Server and
forwards the messages to the CT Agent module of corresponding boards.
l The CT Manager receives the trace data messages from CT Agent modules on RNC
boards and forwards the messages to the CT Server.
l The CT Manager module is the unique path between CT board software module and
CT Server. The system controls the data flow and limits the trace control parameters in
the CT Manager module. The signaling trace message traffic at the client, for example,
is limited via this module.
l CT Manager module informs CT Server about the configuration data modification
reported from the CT boards, detects and traces the connection and disconnection
of the communication link at the client in real time.
1.3.5 CT Agent Module

The Call Trace (CT) Agent module is distributed on all boards. It connects with the Radio
Network Layer (RNL) application module. The CT Agent module forwards the trace control
messages and trace data messages. The specific procedure is described as follows:
l The CT Agent module receives the trace control messages from the CT Manager, and
forwards the messages to the corresponding RNL application modules.
l CT Agent module receives the trace data messages from the RNL application modules
on all boards, and forwards the messages to the CT Manager.
l The CT Agent aids the CT Manager in controlling the data flow.
1-4

Chapter 1 Overview
1.3.6 RNL/TNL Module

The Radio Network Layer (RNL) or Transmission Network Layer (TNL) module has the
following functions:
l Receiving the call trace control messages from the CT Agent.
l Starts the radio signaling or transmission signaling processing modules on the
corresponding boards
l Processing the signaling data and sending the processed data to the CT Agent
module.
1.4 Deployment Methods

1.4.1 Overview of Deployment Methods
The RNC Call Trace (RCT) software, with a client-server architecture, is a real-time
signaling trace tool supporting multiple NEs. The software needs to be deployed
separately, and supports multiple clients.
According to the location of the server program, the deployment of the RCT software has
the following three methods:
l Independent server deployment

l Sharing EMS server deployment
l Local NE deployment
1.4.2 Independent Server Deployment

Networking
For the independent server deployment, the call trace server is deployed at the EMS side
(in the same network segment as the EMS). The CT server, separate from the EMS server,
operates independently.
If the EMS is not in the same network segment as the OMM, deploy a Message Routing
Module (MRM) on the OMM. The CT server traces signaling messages by connecting to
the RNC via the MRM on the OMM. The specific deployment is illustrated in Figure 1-3.
Figure 1-3 Independent Deployment of the Call Trace Server
1-5

Requirement on Resources
For the independent server deployment, the requirement on resources is shown in .
Item Requirement
Recommended server sun v4 SPARC Enterprise T5220 (number of

virtual CPUs: 64, physical memory: 32G)
CPU usage of the client 10%
Memory usage of the client 2 G (The RCT software occupies 1200M; the
database instance occupies 800M)
Disk space 49546 M
Bandwidth 0.32 Mbps
Limitations
For the independent server deployment, the call trace software has the following
limitations:
l Supports the 7*24 hour UE signaling trace. The signaling trace tasks of at most 20
UEs are supported.
l Supports at most 4-hour continuous observation of such real-time tasks as RRM Trace
Viewer (RTV) and MTM.
l Supports at most 0.5-hour continuous trace of signaling at the Iu interface transmission
layer.
l Supports at most 3-day continuous trace for other signaling tasks, such as cell
signaling tasks and office signaling tasks.
l The code stream trace tasks on the user plane needs to be performed in offline mode.
1.4.3 Sharing EMS Server Deployment

Networking
The CT Server module can be integrated into the EMS server to perform centralized
management on multiple NEs. If it can be guaranteed that the EMS server has enough
processing capability, this deployment saves cost. The specific deployment is illustrated
inFigure 1-4.
Figure 1-4 Calling Trace Software Server is Integrated Into EMS Server
1-6

Chapter 1 Overview
Note:
The server shared by EMS and the CT software can be installed with such operating
systems as Windows 2003, Linux, or Solaris, while the CT client must use the Windows
operating system.
Requirement on Resources
For the sharing EMS Server deployment, the requirement on resources is shown in .
Item Requirement
CPU usage of the client 10%
Memory usage of the client 2 GB (The RCT software occupies 1200 M; the
database instance occupies 800 M)
Disk space usage of the client 49546 M
Bandwidth 0.32 Mbps
Limitations
For the sharing EMS Server deployment, the call trace software has the following
limitations:
l Does not support the 7*24 hour UE signaling trace. The trace of at most 3 consecutive
days is supported. The signaling trace tasks of at most 20 UEs are supported.
l Supports at most 2-hour continuous observation of such real-time tasks as RRM Trace
Viewer (RTV) and MTM.
l Supports at most 0.5-hour continuous trace of signaling at the Iu interface transmission
layer.
l Supports at most 1-day continuous trace for other signaling tasks, such as cell
signaling trace tasks and office signaling trace tasks.
l The code stream trace tasks on the user plane needs to be performed in offline mode.
1.4.4 Local NE Deployment

For subscribers that do not need signaling trace of the whole network, such as subscribers
in the lab or during on-site commissioning, the call trace software is required as an online
signaling monitoring tool. In such cases, deployment at local NEs can be used.
For the local NE deployment, one MRM needs to be deployed on the OMM to avoid
influences on the operation of the OMM. The CT Server module and the Client module
can operate on two PCs or on one PC. The specific deployment mode is shown in Figure
1-5.
1-7

Figure 1-5 Deployment of the Call Trace Software at the Local NE
1.5 Basic Concepts about Tasks

1.5.1 Overview
Call trace is achieved by call trace tasks. To create a call trace task, users need to define
the task name, task description, task type, the call trace object corresponding to the task
type, and call trace parameters.
1.5.2 Life Cycle of a Task

The whole life cycle of a call trace task starts from the creation, and ends with its deletion.
During the life cycle, the task status changes when a user suspends or starts the task.
The whole life cycle is illustrated in Figure 1-6.
1-8

Chapter 1 Overview
Figure 1-6 Life Cycle of the Call Trace Task
Only call trace tasks in the running status can be operated. Users can obtain the signaling
messages and measurement graphs corresponding to tasks.
1.5.3 Task Types

The RNC Call Trace (RCT) software supports six types of tasks, which are described in
Table 1-2.
Table 1-2 Task Types
Type Home Board Purpose
UE Trace ROMP/RCP Traces the signaling of the UE (treated as the

tracing object).
OFFICE-IU Trace ROMP/RAP Traces the signaling between RNC and Core
Network (CN), including the signaling in the PS
domain and the CS domain.
1-9

Type Home Board Purpose
OFFICE-IUR Trace ROMP/RCP Traces the signaling between an RNC and the
adjacent RNC.
OFFICE-IUB Trace ROMP/RCP Traces the signaling between the RNC and
Node B.
CELL Trace ROMP/RCP Traces the signaling of the CELL (treated as

the tracing object).
MBMS Trace ROMP/RCP Traces the signaling related to MBMS with

designated session ID of MBMS or the cell
where MBMS is located.
1-10

Chapter 2
Basic Operations
Table of Contents
Starting the RCT Server .............................................................................................2-1
Starting the RCT Client ..............................................................................................2-2
Network Element Management ..................................................................................2-2
Subscriber Trace ........................................................................................................2-4
2.1 Starting the RCT Server

Abstract
This section describes how to start the RCT Server.
Prerequisites
The RCT software has been installed. The installation procedure is described in the
appendix of this manual.
Steps
1. Start the RCT Server using one of the following three methods.
a. Enter the directory where the RCT software is installed, and then double-click the
file \ums-server\console.bat.
b. On the desktop, double-click the RCT System Console icon.
c. Select Start > Program > RCT Unified Management System > RCT System
Console.
2. The console window is open, and all processes of the server are started automatically.
– End of Steps –
Follow-Up Action
l To stop a process, select the process, and then click Stop.
l To start a process, select the process, and then click Start.
2-1

Note:
The UEP Process and RCT Process can be started or stopped separately.
2.2 Starting the RCT Client

Abstract
This section describes how to start the RCT Client.
Prerequisites
The RCT Server is started.
Steps
1. Start the RCT client using one of the following three methods:
a. Open the directory where the RCT software is installed. Double-click the file \um
s-client\client.exe.
b. On the desktop, double-click the RCT Client icon.
c. Select Start > Program > RCT Unified Management System > RCT Client.
2. The Login dialog box opens. Enter the information needed for login.
3. Click OK.
2.3 Network Element Management

2.3.1 Adding an NE
Abstract
The section provides the procedure to add the RNC information, including the IP address
and port number.
Steps
1. In the main menu of the RCT client, select Maintenance > NE Management. The NE
Management window opens, as shown in Figure 2-1.
2-2

Chapter 2 Basic Operations
Figure 2-1 NE Management Window
2. Click . The Add dialog box opens, as shown in Figure 2-2.
Figure 2-2 Add Dialog Box
3. Set the parameters according to the network plan. The parameters are described as
follows:
l Name: Indicates the NE name. The name can not be the same as any existing
NE.
l Type: Indicates the NE type. Keep the default value.
l IP address: Indicates the IP address of the NE.
à The RCT connects to NEs directly: Set the IP address to that of the OMP.
2-3

à The RCT connects to NEs via the MRM: Set the IP address to that of the
MRM, which is also the bound IP address configured in the “Configuring the
Message Routing Module“ section.
l Port Number
à The RCT connects to NEs directly: Keep the default value 5057.
à The RCT connects to NEs via MRM: Set the port number to the listener port
(35059 by default) of the computer where the MRM is located.
4. Click OK.
2.3.2 Connecting to an NE
Abstract
This section provides the procedure to connect the RCT software to an RNC by setting
up a Socket connection. This operation establishes the physical link for transmitting the
control information and data information.
Steps
1. In the NE Management window, select an NE to be connected.
2. Click the button.
Result
After the connection is established, the State of the NE changes from Off to On.
2.4 Subscriber Trace

2.4.1 Opening the Subscriber Trace Window
Abstract
This section describes how to open the Subscriber Trace window.
Steps
l In the main menu of the RCT client, select Maintenance > Subscriber Trace. The
Subscriber Trace window opens, as shown in Figure 2-3.
2-4

Figure 2-3 Subscriber Trace Window
2.4.2 Creating Tasks

Abstract
Before call trace, users need to create a call trace task. This section describes how to
create such a call trace task.
Prerequisites
The NE is successfully connected to the RCT Server.
Steps
1. In the left pane of the Subscriber Trace window, double-click Create Task. The
Create Task dialog box opens, as shown in Figure 2-4.
2-5

Figure 2-4 Create Task Dialog Box
2. Set the parameters according to the network plan. The parameters are described as
follows:
l Task Name: Enter a task name, which cannot be the same as any existing task.
l Task Type: Select a task type from the drop-down box.
Note:
The subsequent steps show the example when Cell is selected as the Task Type.
3. Click Next. The NE List area appears in the Create Task dialog box, as shown in
Figure 2-5.
2-6

Figure 2-5 NE List Area
4. Select the NE related to the task, and then select a sub-task type under SubTask
Type. Click Add. The parameters of the sub-task are listed, as shown in Figure 2-6.
2-7

Figure 2-6 Sub-Task Parameters
5. Set the sub-task parameters, and click Finish.

2.4.3 Call Trace Task Management

2.4.3.1 Opening the Task Manager Window
Abstract
This section describes how to open the Task Manager window.
Steps
1. In the Subscriber Trace window, double-click the Trace Task Management node in
the navigation tree. The Task Manager window appears in the right pane, listing the
call trace tasks, as shown in Figure 2-7.
2-8

Figure 2-7 Task Manager Window
2.4.3.2 Starting a Task
Abstract
This section describes how to manually start a call trace task in the task list.
Steps
l In the Task Manager window, right-click a task to be started, and then select Start
Task from the shortcut menu.
Figure 2-8 Selecting Start Task
Note:
Users can either start a single sub-task or start all sub-tasks under one object task at
the same time.
Result
In the task list, the Task State of the task changes from STOP to START.
2-9

2.4.3.3 Monitoring a Task
Abstract
This section describes how to monitor a started task.
Steps
1. In the Task Manager window, right-click a task to be monitored, and then select
Monitor from the shortcut menu. A window opens in the right pane, listing related
signaling messages, as shown in Figure 2-9.
Figure 2-9 Signaling Messages of a Task
Follow-Up Action
To view the details and tree information of a message, double-click the corresponding row
of the message in the message list.
2.4.3.4 Viewing Data
Abstract
This section describes how to view the signaling trace files of a task saved on the server.
Prerequisites
The signaling trace files are saved on the server.
2-10

Steps
1. In the Task Manager window, right-click a task, and then select View Data from the
shortcut menu. The View Data dialog box opens, as shown in Figure 2-10.
Figure 2-10 View Data
2. Select a data file, and then click Show. A new window opens, listing the signaling data
saved in the file.
2-11

2.4.4 Viewing a Data File

Abstract
This section describes how to view the historical signaling trace data saved in a data file,
which should have a suffix of .csv.
Steps
1. In the Subscriber Trace window, double-click the Open Data File node in the
navigation tree. An Open dialog box appears.
2. Select the target signaling trace file in the CSV format, and click Open.
3. A window opens in the right pane, listing the signaling data saved in the selected file,
as shown in Figure 2-11.
Figure 2-11 Opening Signaling Trace File
2-12

Appendix A
Installation of the RCT
Software
Table of Contents
Ÿ Overview ................................................................................................................ A-1
Ÿ Installing the RCT Software .................................................................................... A-1
Ÿ Configuring Port Offset ......................................................................................... A-11
Ÿ Configuring and Starting the Message Route Module ........................................... A-13
A.1 Overview
The RNC Call Trace (RCT) software consists of the Message Route Module (MRM), the
client, and the server. The RCT software installation package includes both the server and
client. The MRM installation is included in the OMM installation package.
Note:
The installation of the RCT software is the same for different operating systems, including
the Windows, Linux, and Solaris systems.
In the Windows system, the installation procedures are as follows:

1. Install the RCT software
2. Configure the port offset
3. Configure and start the MRM
A.2 Installing the RCT Software

Abstract
This section describes the procedure for installing the RCT software.
A-1

Note:
The RCT software is not integrated in the NetNumen Unified Element Management
System, so users need to install the RCT software separately.
Prerequisites
1. The Oracle 10g server has been installed.
2. A new database instance has been created for the RCT software.
Steps
1. Open the directory of the RCT installation package, and then double-click setup.bat.
The Administrator: Installation window opens.
2. Press the ENTER key to start decompressing files.
3. After all files are decompressed, the Select Language window opens, as shown in
Figure A-1. Select English from the drop-down box.
Figure A-1 Select Language Window
Note:
The language selected in this window is the one used for the user interface of the RCT
software.
A-2

Appendix A Installation of the RCT Software
4. Click Next. The License Agreement window appears. Select I accept the license
agreement.
5. Click Next. The Select Installation Style window appears, as shown in Figure A-2.
Users can select the installation style according to the description in the right pane.
Figure A-2 Select Installation Style Window
6. Click Next. The Network Scale window appears, as shown in Figure A-3. Users can
select the network scale according to the description in the right pane.
Figure A-3 Network Scale Window
A-3

7. Click Next. The Select Product window opens, as shown in Figure A-4. Select All
Products, and set the path for program files in the Program Area Path box by entering
a path or clicking the Browse button.
Figure A-4 Select Product Window
Note:
The Program Area Path and the Data Area Path are the same by default. Users can
set a different path for the former.
8. Click Next. The Database Connection Config window opens, as shown in Figure
A-5. The related parameters are described in Table A-1.
A-4

Figure A-5 Database Connection Config Window
Table A-1 Parameters for Establishing the Database Connection
Parameter Configuration Description
Database type Select Oracle from the drop-down box.
Database IP or hostname The IP address of the Oracle server.
Database port Set the port number to the default value 1521.
SID (Only for oracle) The database instance ID for the RCT software.
Database superuser name The system user in the Oracle environment.
Password The password of the superuser.
Tip:
Users can click the Test Database Connection button to check whether the
configured database can be connected.
9. Click Next. The Database Config window opens, as shown in Figure A-6.
A-5

Figure A-6 Database Config Window
10. Click Next. The Host Information Config window opens, as shown in Figure A-7.
Set the server IP address in the text box after The master server address.
Figure A-7 Host Information Config Window
11. Click Next. The System Information Detection window opens, as shown in Figure
A-8.
A-6

Figure A-8 System Information Detection Window
12. Click Next. The Installation Information Confirm window opens.

13. Click Install. The Unzip and Copy File window opens, as shown in Figure A-9.
Figure A-9 Unzip and Copy File Dialog Box
14. After the file unzipping and copying process is completed, click Next. A Confirm dialog
box opens, asking whether to execute SQL scripts immediately, as shown in Figure
A-10.
A-7

Figure A-10 Confirm Dialog Box
15. Click Yes. The Installation Database window opens, as shown in Figure A-11.
Figure A-11 Installation Database Window
16. After the database installation is completed, click Next. The Parameter Set window
opens, as shown in Figure A-12.
A-8

Figure A-12 Parameter Set Window
17. Expand Global Configuration > Basic Configuration, click Main node IP, and enter
the server IP address in the Value of config box. Figure A-13 shows the expanded
parameters.
Figure A-13 Parameter Set Dialog Box
18. Click Save, and click OK in the pop-up message box.
A-9

19. Click Next. A Confirm dialog box opens, asking whether to initialize all client scenes,
as shown in Figure A-14.
Figure A-14 Confirm Dialog Box
20. Click Yes. The System Initialization window opens, as shown in Figure A-15.
Figure A-15 System Initialization Window
21. After the initialization is completed, click Next. The Installation Finished window
opens, as shown in Figure A-16.
A-10

Figure A-16 Installation Finished Window
22. Click Finish.

A.3 Configuring Port Offset

Abstract
The port offset configuration is necessary for the sharing EMS server deployment of the
RCT software.
Log in to the EMS server as a root user, and modify the RCT configuration files according
to Table A-2.
Table A-2 Port Offset Configuration Files (1)
File Path File Name Modification
ums-server\utils\consol deploy-console.properti console.server-

e\conf es socket.port=32101
console.rmi.port=32102
10-rct-hostAgent.xml <port>32103</port>
A-11

ums-server\utils\consol deploy-console.properti console.rmi.port=32106

e\works\console1\conf es console.server-
socket.port=32103
ums-server\works\globa deploy-usf.properties usf.usf.ems.baseport=10000

l\deploy usf.components.ftp.server.inter-
nalport=31111
/uep/snmp-
proxy/conf/V1/port=31165
/uep/snmp-
proxy/conf/V2C/port=31161
/uep/snmp-
proxy/conf/V3/port=31164
jboss.tomcat.http.internal-
port=31108
jboss.tomcat.https.internal-
port=31127
usf.compo-
nents.clocksync.sync.internal-
port=31124
global-ftpserver-proxy. Ftp.proxy.service.con-
properties fig.port=31121
ums-server\works\uep\d deploy-web.properties usf.core.web.base.port=31750

eploy
deploy-uep-port.propert usf.core.uep.base.port=31400
ies
If the RCT software has been configured with the Secure File Transfer Protocol (SFTP),
users need to modify another 3 files under the ums-server\works\sftpd\deploy
directory according to Table A-3.
Table A-3 Port Offset Configuration Files (2)
ums-server\works\sftpd deploy-sftpd.properties SFtpServer.server.con-

\deploy fig.port=31128
deploy-sftpd-consoleage usf.consoleagent.process.sftpd.
nt.properties agent.serversocket.port=31128
deploy-sftpd-proxy.prop SFtp.proxy.service.con-
erties fig.port=31129
A-12

A.4 Configuring and Starting the Message Route

Module
The operation object of the Message Route Module (MRM) is the OMM.
Configuration of the MRM

Open the config.properties file under the OMM installation directory ums-svr/too
ls/rct_v2_server_w/conf.
The config.properties file contents are shown as follows:
#Thu May 20 15:58:06 CST 2010

bindAddr=127.0.0.1
port = 35059
ip_port=127.0.0.1:5057
Note:
The parameters in the config.properties file include the IP address of the OMM
server and the address of the OMP board of the RNC. The MRM should be restarted
before the configurations take effect.
Set the related parameters according to the following description:

1. bindAddr: Indicates the IP address of the OMM server where the MRM is operating.
For example, to set the OMM server IP address to 10.9.1.129, modify the parameter
as follows:
bindAddr=10.9.1.129
2. port: Indicates the port number of the OMM server where the MRM is operating. Keep
the default value 35059.
3. ip_port: Indicates the IP address of the OMP board of the RNC. For example, to set
the IP address of the OMP board to 127.0.0.1, with 5057 as the port number, modify
the parameter as follows:
ip_port=127.0.0.1:5057
Note:
The MRM is started automatically with the RCT software, so it does not need to be started
manually.
A-13

Starting and Stopping the MRM

The methods for starting and stopping the MRM are decided by whether the OMM server
console is started with GUI. The methods in different conditions are described as follows:
l Console started with GUI
Start or stop the signaling transfer process in the console window.
l Console started without GUI
à Stopping the MRM
1. Log into the OMM system as the root user.
2. Open the command terminal.
3. Open the ums-svr/bin/consolemml directory.
4. Execute the #./pstop-linux.sh tf command.
5. When prompted to confirm, type Y, and press the ENTER key.
à Starting the MRM
1. Log into the OMM system as the root user.
2. Open the command terminal.
3. Open the ums-svr/bin/consolemml directory.
4. Execute the #./pstart-linux.sh tf command.
5. When prompted to confirm, type Y, and press the ENTER key.
A-14

Appendix B
Troubleshooting
Table of Contents
Ÿ Task Status Is Always Starting ................................................................................ B-1
Ÿ RCT Server Fails to Be Started............................................................................... B-1
B.1 Task Status Is Always Starting

Phenomenon
The Task Status of a task is Starting in the Task List.
Analysis
When a task is in the Starting status, users cannot start the task again.
Solution
1. Stop the task.
2. When the Task Status changes to STOP, start the task again.
B.2 RCT Server Fails to Be Started

Phenomenon: Main Process Fails to Be Started
Solution
1. Check the operation details of the main process to see whether there is any message
indicating that the database cannot be connected.
2. In the Windows operating system, right-click My Computer > Management, and the
Computer Management dialog box opens.
3. In the left pane, expand Service and Application Program > Service. In the right
pane, check whether the RCT service and listener of the database are started, as
shown in Figure B-1.
B-1

Figure B-1 RCT Service and Listener of the Database
4. If the RCT service and the listener of the database are started, stop and restart them.
Phenomenon: FTP Process Fails to Be Started

Solution
Check whether the IP address of the local computer is the same as that of the RCT Server
console.
If they are different, modify the IP address of the local computer to that of the RCT Server
console.
B-2

Figures
Figure 1-1 RCT Client Interface ................................................................................ 1-2
Figure 1-2 Module Architecture of the Call Trace Software........................................ 1-3
Figure 1-3 Independent Deployment of the Call Trace Server ................................... 1-5
Figure 1-4 Calling Trace Software Server is Integrated Into EMS Server................... 1-6
Figure 1-5 Deployment of the Call Trace Software at the Local NE ........................... 1-8
Figure 1-6 Life Cycle of the Call Trace Task .............................................................. 1-9
Figure 2-1 NE Management Window ........................................................................ 2-3
Figure 2-2 Add Dialog Box ........................................................................................ 2-3
Figure 2-3 Subscriber Trace Window ........................................................................ 2-5
Figure 2-4 Create Task Dialog Box ........................................................................... 2-6
Figure 2-5 NE List Area ............................................................................................ 2-7
Figure 2-6 Sub-Task Parameters .............................................................................. 2-8
Figure 2-7 Task Manager Window............................................................................. 2-9
Figure 2-8 Selecting Start Task ................................................................................. 2-9
Figure 2-9 Signaling Messages of a Task................................................................ 2-10
Figure 2-10 View Data ............................................................................................ 2-11
Figure 2-11 Opening Signaling Trace File ............................................................... 2-12
Figure A-1 Select Language Window ........................................................................A-2
Figure A-2 Select Installation Style Window ..............................................................A-3
Figure A-3 Network Scale Window............................................................................A-3
Figure A-4 Select Product Window ...........................................................................A-4
Figure A-5 Database Connection Config Window .....................................................A-5
Figure A-6 Database Config Window ........................................................................A-6
Figure A-7 Host Information Config Window .............................................................A-6
Figure A-8 System Information Detection Window ....................................................A-7
Figure A-9 Unzip and Copy File Dialog Box ..............................................................A-7
Figure A-10 Confirm Dialog Box................................................................................A-8
Figure A-11 Installation Database Window ................................................................A-8
Figure A-12 Parameter Set Window..........................................................................A-9
Figure A-13 Parameter Set Dialog Box .....................................................................A-9
Figure A-14 Confirm Dialog Box..............................................................................A-10
Figure A-15 System Initialization Window ...............................................................A-10
I
Figure A-16 Installation Finished Window ............................................................... A-11

Figure B-1 RCT Service and Listener of the Database ..............................................B-2
II
Tables
Table 1-1 Description of Shortcut Buttons ................................................................. 1-2
Table 1-2 Task Types ................................................................................................ 1-9
Table A-1 Parameters for Establishing the Database Connection..............................A-5
Table A-2 Port Offset Configuration Files (1) ........................................................... A-11
Table A-3 Port Offset Configuration Files (2) ...........................................................A-12
III
Tables
This page intentionally left blank.

Glossary
CS
- Circuit Switched
CT
- Call Trace
IP
- Internet Protocol
MBMS
- Multimedia Broadcast/Multicast Service
MRM
- Message Route Module
OMM
- Operation & Maintenance Module
PS
- Packet Switched domain
RCT
- RNC Call Trace
RNC
- Radio Network Controller
RNL
- Radio Network Layer
RTV
- RRM Trace Viewer
SFTP
- Secure File Transfer Protocol
TNL
- Transmission Network Layer
UE
- User Equipment

PDF ZXWR RNC v31110 Radio Network Controller Calling Trace Operation Guide - Compress PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PDF ZXWR RNC v31110 Radio Network Controller Calling Trace Operation Guide - Compress PDF

Uploaded by

Copyright:

Available Formats

ZXWR RNC

Radio Network Controller

Revision No. Revision Date Revision Reason

R1.0 2011-07-26 First Edition (V3.11.10.05)

Serial Number: SJ-20110704093842-017

Publishing Date: 2011-07-26 (R1.1)

Chapter 2 Basic Operations ...................................................................... 2-1

Appendix A Installation of the RCT Software ......................................... A-1

Appendix B Troubleshooting ................................................................... B-1

What Is in This Manual

Chapter 1, Overview Describes the basic functionality, modules,

Chapter 2, Basic Operations Describes the basic operations of the RCT

Appendix A, Software Installation Describes the installation procedures of the RCT

Appendix B, Troubleshooting Describes the solutions to two common faults.

1.1 Software Functions

1.2 User Interface of the RNC Call Trace Software

Figure 1-1 shows the RCT software.

SJ-20110704093842-017|2011-07-26 (R1.1) ZTE Proprietary and Confidential

Figure 1-1 RCT Client Interface

1. Menu bar 3. Navigation tree 5. Status bar

Table 1-1 Description of Shortcut Buttons

Name Short Icon

SJ-20110704093842-017|2011-07-26 (R1.1) ZTE Proprietary and Confidential

Name Short Icon

1.3 Software Modules

The relationships among all modules are shown in Figure 1-2.

Figure 1-2 Module Architecture of the Call Trace Software

SJ-20110704093842-017|2011-07-26 (R1.1) ZTE Proprietary and Confidential

1.3.2 CT Client Module

1.3.3 CT Server Module

1.3.4 CT Manager Module

1.3.5 CT Agent Module

SJ-20110704093842-017|2011-07-26 (R1.1) ZTE Proprietary and Confidential

1.3.6 RNL/TNL Module

1.4 Deployment Methods

l Independent server deployment

1.4.2 Independent Server Deployment

Figure 1-3 Independent Deployment of the Call Trace Server

SJ-20110704093842-017|2011-07-26 (R1.1) ZTE Proprietary and Confidential

Recommended server sun v4 SPARC Enterprise T5220 (number of

CPU usage of the client 10%

Disk space 49546 M

Bandwidth 0.32 Mbps

1.4.3 Sharing EMS Server Deployment

SJ-20110704093842-017|2011-07-26 (R1.1) ZTE Proprietary and Confidential

CPU usage of the client 10%

Disk space usage of the client 49546 M

Bandwidth 0.32 Mbps

1.4.4 Local NE Deployment

SJ-20110704093842-017|2011-07-26 (R1.1) ZTE Proprietary and Confidential

Figure 1-5 Deployment of the Call Trace Software at the Local NE

1.5 Basic Concepts about Tasks

1.5.2 Life Cycle of a Task

SJ-20110704093842-017|2011-07-26 (R1.1) ZTE Proprietary and Confidential

Figure 1-6 Life Cycle of the Call Trace Task

1.5.3 Task Types

Table 1-2 Task Types

Type Home Board Purpose

UE Trace ROMP/RCP Traces the signaling of the UE (treated as the

SJ-20110704093842-017|2011-07-26 (R1.1) ZTE Proprietary and Confidential

Type Home Board Purpose

CELL Trace ROMP/RCP Traces the signaling of the CELL (treated as

MBMS Trace ROMP/RCP Traces the signaling related to MBMS with