GU - ST - ZTE UniPOS NDS-GU V13.40 Installation Configuration Acceptance Guide - R1.3

Operator Logo
ZTE UniPOS NDS-GU V13.40

Installation Configuration
Acceptance Guide
ZTE UniPOS NDS-GU V13.40 Installation Configuration Acceptance Guide Restricted▲
LEGAL INFORMATION
By accepting this certain document of ZTE CORPORATION you agree to the following terms. If you
do not agree to the following terms, please notice that you are not allowed to use this document.
Copyright © 2018 ZTE CORPORATION. Any rights not expressly granted herein are reserved. This
document contains proprietary information of ZTE CORPORATION. Any reproduction, transfer,
distribution, use or disclosure 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.
and are registered trademarks of ZTE CORPORATION. ZTE’s company name, logo
and product names referenced herein are either trademarks or registered trademarks of ZTE
CORPORATION. Other product and company names mentioned herein may be trademarks or trade
names of their respective owners. Without the prior written consent of ZTE CORPORATION or the
third party owner thereof, anyone’s access to this document should not be construed as granting,
by implication, estopped or otherwise, any license or right to use any marks appearing in the
document.
The design of this product complies with requirements of environmental protection and personal
security. This product shall be stored, used or discarded in accordance with product manual,
relevant contract or laws and regulations in relevant country (countries).
This document is provided “as is” and “as available”. Information contained in this document is
subject to continuous update without further notice due to improvement and update of ZTE
CORPORATION’s products and technologies.
ZTE CORPORATION
Address: NO. 55
Hi-tech Road South
ShenZhen
P.R.China
518057
Website
http://support.zte.com.cn
:
Email: 800@zte.com.cn
ZTE Confidential & Proprietary. © ZTE CORPORATION. All rights reserved.

Revision History
Document Serial
Product Version Reason for Revision
Version Number
UniPOS NDS-GU V13.40 R1.0 First published
UniPOS NDS-GU V13.40 R1.1 Revised
Author
Date Document Version Prepared by Reviewed by Approved by

Li Wei, Chen Taiming,
2014-04-10 R1.0 Kou Zhanchuan Zhang Zhongqi
Chen Qi
Chen Qi
Chen Qi
Chen Qi
Intended audience: GU product after-sales engineers

About This Document
Summary
Chapter Description
1 Introduction Introduces the purpose of this guide.
2 Terms, Definitions, and Describes the terms, definitions, and abbreviations used in
Abbreviations this guide.
3 Principles Describes the related flow and principles in brief.
4 Supported Versions Lists the RNC versions, BSC versions, and NetMax versions
supported by NDS-GU V13.40.
5 NDS Server Installation and Describes the preparations needed before NDS installation
Uninstall and how to install/uninstall NDS in Linux OS and Solaris OS.
6 NDS Service Configuration Introduces data collection related configuration, northbound
file configuration, MR preliminary statistics configuration, MR
positioning accuracy configuration, etc.
7 System Acceptance and Describes how to check whether NDS service is normal.
Maintenance
8 FAQs and Solutions Introduces some FAQs and solutions.

TABLE OF CONTENT
1 Introduction......................................................................................................1
1.1 Background........................................................................................................1
1.2 Overview............................................................................................................1
2 Terms, Definitions, and Abbreviations...........................................................2

2.1 Terms and Definitions........................................................................................2
2.2 Abbreviation.......................................................................................................2
3 Principles.......................................................................................................... 3
3.1 Principle of NDS.................................................................................................3
3.2 Principles of MR.................................................................................................3
3.3 Principles of CDT...............................................................................................4
3.4 Principles of DPS...............................................................................................6
3.5 Principles of EMI................................................................................................6
4 Supported Versions.........................................................................................8
4.1 BSC and RNC Versions Supported....................................................................8
4.2 NetMax Versions Supported..............................................................................8
5 NDS Server Installation and Uninstall............................................................9

5.1 Requirements for NDS Server Software/Hardware............................................9
5.2 Preparations Before Installation.......................................................................10
5.2.1 Checking Operating System (OS)....................................................................10
5.2.2 Checking Database Software (When NDS and NetMax Are Installed on the
Same Server)...................................................................................................11
5.2.3 Checking Disk Array Configuration...................................................................11
5.2.4 Network Planning:............................................................................................12
5.2.5 Hardware Space Planning...............................................................................18
5.2.6 Applying for License File in Advance (Important).............................................19
5.3 Installing NDS in Linux OS...............................................................................19
5.3.1 Uploading Installation Package........................................................................19
5.3.2 Checking the MD5 of the Installation Package.................................................19
5.3.3 Unzipping Installation Package........................................................................20
5.3.4 Executing the NDSInstall.sh Installation Script.................................................20
5.3.5 Checking Service.............................................................................................21
5.4 Uninstalling NDS in Linux OS..........................................................................22
5.4.1 Execute the uninstall script..............................................................................22
5.5 Installing NDS in Solaris OS............................................................................22
5.5.1 Uploading Installation Package........................................................................22
5.5.2 Checking the MD5 of the Installation Package.................................................23
5.5.3 Unzipping Installation Package........................................................................23
5.5.4 Executing the NDSInstall.sh Installation Script.................................................23
5.5.5 Checking Services...........................................................................................24
5.6 Uninstalling NDS in Solaris OS........................................................................25

5.6.1 Executing the Uninstall Script..........................................................................25
6 NDS Service Configuration...........................................................................26

6.1 Configuring NDS in the Web Mode..................................................................26
6.2 Description of Application Scenarios................................................................27
6.2.1 Scenario 1: GSM V3 NE..................................................................................28
6.2.2 Scenario 2: GSM V4 NE..................................................................................28
6.2.3 Scenario 3: UMTS V3 NE................................................................................29
6.2.4 Scenario 4: UMTS V4 NE................................................................................30
6.3 Configuring NDS Data Collection.....................................................................30
6.3.1 Overview of NDS Data Collection Configuration..............................................30
6.3.2 Configuring FTP Connection Configuration of SBCX.......................................34
6.3.3 Data Source Configuration for GSM BSC V6.30..............................................38
6.3.4 DSP Configuration...........................................................................................41
6.3.5 Configuring GSM V3 Data................................................................................44
6.4 Configuring Northbound Files..........................................................................51
6.4.1 Web Configuration Mode.................................................................................52
6.4.2 Configuration File.............................................................................................53
6.4.3 Configuration Description.................................................................................53
6.4.4 Configuration Content......................................................................................53
6.4.5 GSM Frequency Change Sample Configuration..............................................57
6.5 Configuring UMTS CT Files.............................................................................59
6.6 Configuring MR Preliminary Statistics File.......................................................60
6.7 Configuring MR Positioning Accuracy Improvement File..................................63
6.8 Configuring Specific Versions..........................................................................64
6.8.1 Configuring GSM V3 RAP Installation..............................................................64
6.8.2 Configuring Time Zone.....................................................................................65
7 System Acceptance and Maintenance.........................................................68

7.1 Observing System Operation Status................................................................68
7.1.1 Checking System Installation State..................................................................68
7.1.2 Checking Service Processes...........................................................................68
7.1.3 Starting, Stopping, and Restarting NDS Software............................................69
7.2 Checking the NE Data on SBCX......................................................................74
7.3 Check File Acquisition State on NDS...............................................................75
7.3.1 UMTS Product.................................................................................................77
7.3.2 GSM Product...................................................................................................78
7.3.3 Factors Affecting File Size................................................................................79
7.3.4 Checking Data Integrity in the Data Directory..................................................80
7.4 Checking File Generation on NDS...................................................................81
7.4.1 Checking GSM BSCV6.20 Series....................................................................82

7.4.2 Checking GSM BSCV6.30 and V6.50 Series...................................................83

7.4.3 Checking Data Integrity in the FTP Directory...................................................83
7.5 Checking Log File............................................................................................84
7.5.1 Searching Errors in the Log.............................................................................86
7.6 Backing up Files Manually...............................................................................86
7.7 Clearing Files Automatically.............................................................................86
7.8 Daily Inspection................................................................................................86
8 FAQs and Solutions.......................................................................................88

8.1 User Root Locked to Ftp Home Directory (Linux).............................................88
8.2 NDS Related Processes Are in Abnormal State...............................................88
8.3 NDS Cannot Be Installed and the System Prompts It Already Exists...............89
8.4 Checking NE Status.........................................................................................90
8.5 SBCX Board Configuration..............................................................................90
8.6 Notices in Data Download................................................................................90
8.7 The RNCID in the File Name Generated on RNC Is Inconsistent with the RNCID
Configured.......................................................................................................91
8.8 Number of Data-keep Days..............................................................................92
8.9 Packaging Log Files.........................................................................................93
8.10 System Version Information.............................................................................93
8.11 Matters for Attention in Multi-Partition..............................................................93
8.12 NetMAX-GU Data Import Failure Check Steps................................................96

1 Introduction
1.1 Background
Modern mobile communications technology is a very complex system. Due to the

complexity of the wireless transmission environment, the mobility of the subscribers, and
the differences of the terminals, wireless network optimization is facing a lot of
difficulties, such as technology difficulties, lack of analysis method and tool, and low
work efficiency, which increasingly restricts the improvement of network performance.
For the operator, the functions of the equipment are not made full use of, and this
hinders the further development of the services and subscribers. Meanwhile, the
equipment provider faces two problems, i.e., a larger number of highly-skilled engineers
are needed for network planning & optimization, and it is still difficult to meet the
operator’s requirement for high-quality network.
1.2 Overview
UniPOS NDS-GU SERVER is the system for collecting and preprocessing data in the
CDT/MR system. It can automatically collect the CDT/MR data of more than one
RNC/BSC, store the raw data, and perform data preprocessing/statistics/conversion
according to certain rules. Besides, it can provide the data file interface, which provides
data for the third-party system. This guide introduces how to install and deploy UniPOS
NDS-GU product and how to perform troubleshooting according to the check on service
operation status, file generation, and log.
2 Terms, Definitions, and Abbreviations
2.1 Terms and Definitions
Northbound: Refers to the third-party network optimization system. It is above the NDS
system in the network architecture, and acquires data from NDS. Because it is in the
south of NDS, it is called the northbound system sometimes.
2.2 Abbreviation
The following table shows the abbreviations (alphabetical) used in this guide.
Abbreviation Full Name
NetMAX brand of ZTE’s new intelligent optimization tool
NDS Network Data Service
CDT Call Detail Trace
MR Measurement Report
DPS Data Process System/Service
EMI Evaluation MOS Index

3 Principles
3.1 Principle of NDS
After the BSC/RNC generates the raw/basic data file needed by the network
optimization system, NDS (Network Data Service) collects the data periodically and then
stores and preprocesses the data. NDS also provides a unified interface (FTP file
interface) for the third-party network analysis system, and third-party system and
NetMax acquires the processed data from NDS periodically. For different versions of
BSC V3 and V4, the protocol for the communications with NDS is different.
3.2 Principles of MR
MR function: UR can report intra-frequency measurement, inter-frequency

measurement, inter-system measurement, service volume information, quality
information, internal measurement information, and location information in the
measurement result (MR) it reports. With these MR records, we can diagnose the
coverage and interference of the wireless network with the network planning &
optimization analysis tool on the basis of the MRs of subscribers in the current network,
so as to replace the high-cost network optimization method such as DT.
The MR function supports MR data collection, storage, and output.
With the serving cell measurement synchronization data, RSCP and Ec/N0 information
provided by MR data, the geographical-based display method adopted can show the
areas with weak coverage or coverage holes clearly, based on which the advices for
adding sites can be made.
Based on the inter-system measurement data in the MR data, we can learn the inter-
system coverage state conveniently, which provides a reference for configuring neighbor
cells for inter-system. Based on the statistical analysis of the MR data in the entire
network, we can learn the overall RSCP and Ec/N0 coverage state of the entire network
and the interference of the network.
With the associated measurement data of the serving cell and the neighbor cells and
UE’s TX power data, the network coverage problems such as weak coverage,
overshooting, and pilot pollution can be located very quickly. They can also be used for
the diagnosis and improvement of outside interference, and neighbor cell optimization.
Currently, the MR reported by RNC contains the standard interface (Uu/Iub) code
stream, as detailed below:
1. MR-UE coverage measurement.
i. Handover measurement due to event: UE intra-frequency/inter-

frequency/inter-system measurement
ii. Traffic measurement due to event: UE traffic measurement result
iii. Internal event measurement: UE TX power measurement result
iv. Periodical handover measurement: UE intra-frequency measurement result
v. Internal periodical measurement: UE TX power measurement result
vi. Periodical quality measurement: UE DL DCH BLER measurement result,

RNLU UL DCH BLER measurement result
2. MR-UE location measurement: Select one of the following modes.
i. UEB AGPS: Periodical UEB AGPS location measurement result. Select this
mode when the UE supports this mode.
i. CELL-ID+RTT mode: Periodical Node B RTT measurement, periodical UE

Rx-Tx time difference type 1 measurement
3.3 Principles of CDT
CDT (Call Detail Trace) function: It is an important feature of ZTE’s telecommunications

management network. By storing the key information of the call, the third-party system
can analyze the history traffic data to acquire the main information.
The CDT function falls into two parts, CDT control and CDT data storage.
1. CDT control: Configure CDT parameters to the CMP board by configuring and
modifying the RNC configuration parameters on EMS.
2. CDT data storage: Control which part of the CDT data to be stored on the CMP
board according to the data configuration, and save the CDT data to SBCJ through
the platform.
Basic flow: The user sends the CDT configuration parameters to RNC through OMMR;
RNC sends the parameters to CMP through the internal database system; CMP saves
the key information collected in the call to the CDT buffer area provided by the platform
according to the configuration parameters. Each CDT buffer area corresponds to a UE
call processing instance. When the call ends, the platform sends the CDT data to the file
storage module of SBCJ, which stores the CDT data in the file.
Finally, the subsequent processing system acquires files from SBCJ and makes the
follow-up analysis and processing.
Currently, the information reported by CDT includes mainly the following:
 Control-plane information:
1. IMEI
2. UE capability: includes UE radio access capability, PDCP capability, and physical

channel capability.
3. UE RRC info: includes RRC setup time, RRC release time, RRC setup cause,
RRC release cause, RRC connection setup cell info, and RRC release cell info.
4. UE key message info

5. UE channel type info
6. UE handover info
7. UE RAB info
 User-plane information: records the user-plane physical board resource related

information of the call.
3.4 Principles of DPS
It is a specific function of UMTS. Versions supported by DPI:

V4.11.20.06/V4.12.10.08p05/V4.12.10.14. (There is no DPI data in V3). Only the DPI
information of non-VIP subscribers is processed.
3.5 Principles of EMI
It is a specific function of UMTS. The versions supported by EMI include V4.11.20.06/

V3.12.10.08p05/ V4.12.10.08p05/ V3.12.10.14/ V4.12.10.14. Both VIP and non-VIP
subscribers support this function.
UMTS CS service perception assessment is mainly to assess the CS user experience

related KPIs for the predefined VIP user group, VAP user group, and the users of the
entire network according to the analysis of UMTS CDT CallLog, MR, and the associated
log. The assessment is made from the following perspectives:
Wireless signal coverage (focus on the wireless signal in the access state at the earlier
phase).
Service accessibility (including access success rate, access duration, and abnormal
interruption in the access process)
Service retainability (including MOC/MTC call drop rate, abnormal release rate, and CN
abnormal release rate)
CS service integrity (including the statistical analysis of uplink/downlink EMI and the
display mode)
Among the above KPIs, EMI is a newly-added one, i.e., equivalent MOS indicator. It is
also a core KPI of CS service perception assessment. It is used mainly to perform
statistical analysis to network-level and cell-level (user data of a cell) EMIs, display EMS
statistics geographically, show the change of EMI with the change of time that the user
makes a call, trace back the geographical data of uplink/downlink EMI when there is
some CS service quality problem or the users complain about call drops, and
troubleshoot suspected one-way audio problem according to the uplink/downlink based
EMI statistics algorithm and short call record in complicated CS quality problem.
4 Supported Versions
4.1 BSC and RNC Versions Supported
For the information of the versions supported, refer to the ZTE UniPOS NDS-GU
V13.40.06 Release Notes for details.
4.2 NetMax Versions Supported
Because this version is changed greatly, only NetMax-GU V13.40 XX series are
supported currently. For the information of the versions supported, refer to the ZTE
UniPOS NDS-GU V13.40.06 Release Notes for details.
5 NDS Server Installation and Uninstall
5.1 Requirements for NDS Server

Software/Hardware
The requirements for the basic performance of hardware configuration are as shown in
the table below. The gap between the configured value and the required value should
not be too great. Otherwise, the data may not be processed timely, and the data may
even get lost.
Remarks :
1. The configuration is divided into three scales, i.e., large, medium, and small scales.
Perform the configuration according to the pre-sales requirements.
2. Currently, the supported OS versions include RedHat linux Enterprise V6.0, V6.1,
V6.2, V6.3 and Solaris10 u8, u9, u10.
Note:
1. Deployment of NDS on SBCJ/SBCX is not supported.
2. Red Hat Enterprise Linux V6.4 is not supported.
3. Solaris10 u8 does not support RNCV4.11.20.06.

Busy-hour
Typical RNC
CS Traffic Cell Qty Min. Server Configuration
Configuration Qty
(Erl)
CPU: 2 Xeon E5-2630 2.3G

Memory: DDR3 16G
Four 1000 M adapters
Small scale <=2000 <=2 <=2000 There is 2T free space after
the RAID operation on the
hardware
Redundant power supply
CPU: 4 Xeon E5-2630 2.3G

Memory: DDR3 32G
2000~50
Medium scale 2000~6000 2~5 There is 2T free space after
00
hardware
CPU: 4 Xeon E7-4850 2.3G

Memory: DDR3 64G
5000~80
Large scale 6000~10000 6~8 There is 4T free space after
00
hardware
5.2 Preparations Before Installation
5.2.1 Checking Operating System (OS)
Operating System Version:
Default user name/password: root/netmax
IP and masks of the ports on the adapter:
Static route configuration:

Hardware equipment alarm information:
OS hard disk raid (recommended raid: 1):
Storage mounting state (including the disk array):
If no disk array is configured, check also the raid of the data area (recommended: raid5):
5.2.2 Checking Database Software (When NDS and NetMax Are Installed
on the Same Server)
Database software version:
Username/Password:
Installation directory:
Formal License typed in or not (authorized or not):
5.2.3 Checking Disk Array Configuration

Note:
1. If the disk array is not configured with optical fiber port (the server is not configured
with HBA accordingly), use a high-quality Cat5e cable to connect the disk array and
NDS server. NDS server and NetMax (or northbound interface) should also be
connected with a high-quality Cat5e cable to guarantee the transmission bandwidth and
quality. 1. Eight pieces of high-quality Cat5e cables are needed, which are shown in
the red lines in the following figure. 2. Three pieces of common-quality Ethernet
cables are needed, which are shown in the blue lines in the following figure. High-
quality Cat5e cables can be used for the common cables if it takes too much time to
distinguish the cables.
2. Use two switches as the relay to increase the reliability.
Disk array model, SN:
Configuration and maintenance username and password:
Hardware Qty, specific raid:
Number of hot standby disks:

IP and master of controller SPA/SPB:
Access mode, username, and password of controller SPA/SPB:
Data transmission mode:
Corresponding data cable interface:
Corresponding management cable interface:
Logical partition status:
Are there alarms or not:

5.2.4 Network Planning:
5.2.4.1 Firewall Port

Port
Defaul
TCP/UD Port Connection Usage Port
t Port Occupier
P Direction Descriptio Type
Value
n
FTP data
Logservice(SBCX) Mandator Logservice(SBC
TCP 21 transmissio
=> NDS y X)
n port
FTP data
Logservice(SBCJ) Logservice(SBC
TCP 10021 transmissio Optional
=> NDS J)
n port
SFTP data
Logservice(RNC Mandator Logservice(SBC
TCP 22 transmissio
SBCX)=> NDS y X)
n port
Socket
CMP(BSC V3 data Mandator CMP(BSC V3
TCP 15000
V6.20) = > NDS transmissio y V6.20)
n port
Socket
CMP(BSC V3 data Mandator CMP(BSC V3
TCP 15006
V6.20) = > NDS transmissio y V6.20)
n port
TCP/UD Defaul Port Connection Port Usage

Port Type Port Occupier
P t Value Direction Description
FTP data
Mandator
TCP 21 NDS => NetMAX transmissio NDS
y
n port
SFTP data
Mandator
TCP 22 NDS => NetMAX transmissio NDS
y
n port
Mandator
TCP 18222 NDS => NetMAX ICE NetMAX
y
Mandator
TCP 24200 NDS <= NetMAX ICE NDS
y
5.2.4.2 Requirements for the Communications Between Nodes
The NDS server needs to communicate with the NEs (BSC/RNC). The network ports
are as shown in the table above.
NDS needs to communicate with NetMax or the third-party network optimization system.
NetMax or the third-party network optimization system may acquire northbound data
from EMS, so make sure the communications with EMS are connected.
The network optimization command of NetMax or the third-party network optimization

system is sent to the NEs through EMS, so make sure the communications with EMS
are connected.
There is no direct interaction between the NEs and NetMax or the third-party network
optimization system, so they do not need to cummunicate with each other.
The data interface of the disk array controller needs only to communicate with NDS or
NetMax server.
The management interface of the disk array controller can communicate with either NDS
or NetMax server. The external network IP may be configured for the management and
monitoring in the later phase.
5.2.4.3 Requirement for Bandwidth
The following calculation is based on the data model acquired from the Shenzhen
project. The busy-hour traffic is 10000erl, and the CDT data volume is 210M. The part in
bond fonts shows the requirement for the bandwidth. The calculation method is as
shown below:
The percentage of different data types:
Raw MR data = CDT * 3.75 (set MR Data Collection Rate to 100%)
Raw CT data = CDT * 2
Size for Netmax interface directory = MR * 0.5 + CDT * 2.5 = 4.375 * CDT
Data volume calculation:
RNC-NDS: MR + CDT + CT = 6.75 CDT = 6.75 * 210M = 1418M
NDS-NetMAX Server: NetMAX reads all data1 and data3, and use them as CDT data.
Based on "data1 : data3 = 1 : 2,” NetMAX needs to read 2.7 times of CDT data, 570M in
total. With data3, CT data, VIP data, and complaint user data counted in, NetMAX
needs to read at least 600M data.
Bandwidth calculation:
Network bandwidth calculation: Data volume (number of bytes) X 8 (bits/bytes)

÷Network Utilization Rate ÷3600 (seconds), use “0.6” as the value of Network Utilization
Rate.
NDS-RNC bandwidth (10000erl/hour in busy hours): 5.25M is needed
NDS-NetMAX Server (10000erl/hour in busy hours): 2.2M is needed

Note:
1. The above calculation is based on CS+PS 10000erl. If there is more than one NE, add
up the traffic volume of all NEs for the calculation.
2. Consult with the field engineer for the confirmation of traffic model.
5.2.4.4 IP and Hostname Planning
The following are some examples for reference. Perform planning and configuration
according to the on-site network and the number of ports on the server.
Ethern Connection Descripti
Object IP/Mask Remarks
et Port Object on
NetMax or
10.10.1.1(inter If there are not
third-party
NDS nal network Bind Eth1 enough Ethernet
Eth1 network
Server 1) / with Eth2 ports, do not bind
optimization
255.255.255.0 these two ports.
system
NetMax or
third-party
Eth 2 network
optimization
system

Eth 3 RNC or BSC

Eth 4 RNC or BSC
If there are not

enough Ethernet
ports, do not bind
192.168.1.1(in
Data1 port of these two ports.
NDS ternal network Bind Eth5
Eth 5 disk array Some disk arrays
Server 3) / with Eth6
controller SPA need IP
255.255.255.0
configuration,
while some do
not.
If there are not

enough Ethernet
ports, do not bind
192.168.1.1(in
Data1 port of these two ports.
NDS ternal network Bind Eth5
Eth 6 disk array Some disk arrays
Server 3) / with Eth6
controller SPB need IP
255.255.255.0
configuration,
while some do
not.
If there are not

enough Ethernet
5.2.5 Hardware Space Planning
Perform Raid1 on at least two physical hard disks, and perform Raid5 on the other
disks, which are used as the data disks.
If the disk array is connected, store the NDS application software and data on the disk
array.
5.2.5.1 Requirement for NDS Application Software Space
Because the temporary files need to be saved, it is recommended that 100G space be
allocated to the disk where the NDS application software is installed.
5.2.5.2 Requirement for NDS Data Space
The following calculation is based on the data model acquired from the Shenzhen
project.
The busy-hour traffic is 10000erl, and the CDT data volume is 210M.
The percentage of different data types:
Raw MR data = CDT * 3.75
Raw CT data = CDT * 2
Size for Netmax interface directory = MR * 0.5 + CDT * 2.5 = 4.375 * CDT
Data volume calculation (10000erl/hour in busy hours):
RNC-NDS: MR + CDT + CT = 6.75 CDT = 6.75 * 210M = 1418M
NDS-NetMAX Server: NetMAX reads all data1 and data3, and use them as CDT data.
Based on "data1 : data3 = 1 : 2,” NetMAX needs to read 2.7 times of CDT data, 570M in
total. With data3, CT data, VIP data, and complaint user data counted in, NetMAX
needs to read at least 600M data.
Note:
1. The above calculation is based on CS+PS 10000erl. If there is more than one NE, add
up the traffic volume of all NEs, and then multiply the result by the number of days.
2. Consult with the field engineer for the confirmation of traffic model.
5.2.6 Applying for License File in Advance (Important)
Refer to the ZTE UniPOS NDS-GU V13.40 Authorization Guide for details. Apply for the
License file of V13.40 series in advance. Otherwise, before the License file is imported
after the installation is completed, NDS cannot output any data to the northbound
interface or NetMAX because the NDS functions are restricted.
5.3 Installing NDS in Linux OS
Requirement for OS version: Redhat V6.0/V6.1/V6.2/V6.3, Redhat V6.3 is

recommended.
Note:
Deployment of NDS on SBCJ/SBCX is not supported.
Red Hat Enterprise Linux V6.4 is not supported.
5.3.1 Uploading Installation Package
Use the file transmission function provided by Filezilla FTP Client, log on to the ftp/sftp
service of the server OS as the root user, and upload
NDS_GU_V13.20.01_Release_Redhat.tar.gz to the /NDS/install directory in
the bin mode.
5.3.2 Checking the MD5 of the Installation Package
Check the MD5 of NDS_GU_V13.20.01_Release_Redhat.tar.gz with the md5sum

command, and make sure the file transmission is correct.
# cd /NDS/install
# md5sum NDS_GU_V13.20.01_Release_Redhat.tar.gz
e768e31d1feb9b4701e37bf6ae784486 NDS_GU_V13.20.01_Release_Redhat.tar.gz
The above example is only for reference. Because MD5 is different for different NDS-
GU versions released, if there is some problem with md5, contact the technical engineer
to confirm the correct MD5 and get the correct installation package.
5.3.3 Unzipping Installation Package
Log in to the server as user root, open the path of the installation package, and unzip
the installation package file with the following commands.
# cd /NDS/install
# gtar xvfz NDS_GU_V13.20.01_Release_Redhat.tar.gz
The NDS-GU.tar installation package and the NDSInstall.sh script are generated
under the original directory after the package is unzipped.
5.3.4 Executing the NDSInstall.sh Installation Script
The NDSInstall.sh command can be attached with one or two parameters, as shown
below.
# ./NDSInstall.sh /NDS
or
# ./NDSInstall.sh /NDS --sftp
Parameter 1: /NDS. This is the NDS installation path, and it is recommended that the
installation space should be large enough. If the path does not exist, it will be created by
default.
Parameter 2: --sftp. It means the sftp server is used, and the system will not check
whether ftp server is installed anymore. If this parameter is not configured, NDS will
check whether ftp service is installed, if not, the ftp service will be installed automatically.
Note: Parameter 1 must be filled in, while parameter 2 is optional according to the
requirement.
Are you sure to install NDS_GU_V13.20.01_Release_Redhat to /NDS? [y..n]y
yes is selected
start install NDS_GU_V13.20.01_Release_Redhat
Begin check hardware condition...
/NDS
Free Disk Space(GByte):
488
CPU num:
16
System Memory Size(MByte):
32768
Hardware conditon check success!
install NDS to /NDS
/home/install
add group nds success
create user nds success
create user zte success
create user netmax success
start NDS service
starting NDS service
start NDS service success
If the hardware does not meet the requirement, the software cannot be installed
successfully. In this case, check whether is some hardware configuration fault.
In the installation process, if the system prompts that NDS has existed and the
installation cannot be continued, refer to Section 8.3 to handle this problem.
5.3.5 Checking Service
After the installation is completed, check whether NDS-GU service is started normally. If
there is some problem, refer to Section 7.1.3.1 to restart related services.
Check the key NDS service. If the service is is normal, the following will be
displayed:
# service ndsd status
ndsd service is running
Check the dps service. If the service is normal, the following will be displayed:
# service ndsdpsd status
ndsdpsd service is running
Check the mrserver service. If the service is normal, the following will be displayed:
# service ndsgv3mrd status
ndsmrserverd service is running
Check the cdtserver service. If the service is normal, the following will be
displayed:
# service ndsgv3cdtd status
ndscdtserverd service is running
Check the v3rap service. If the service is normal, the following will be displayed:
# service ndsv3rapd status
ndsv3rapd service is running
5.4 Uninstalling NDS in Linux OS
5.4.1 Execute the uninstall script.
Open the NDS-GU installation path, and execute the NDSUnInstall.sh script to
uninstall NDS.
# ./NDSUnInstall.sh
In the uninstall process, a prompt will pop up, querying whether to delete the MR/CDT
and other data files under the Data and FTP directories. Input “y” to delete them and “n”
to cancel the deletion.
Note: If “n” is typed in, all the MR/CDT data downloaded under the Data directory as
well as the interface files under the FTP directory will be deleted.
5.5 Installing NDS in Solaris OS
Requirement for OS version: Solaris 10 u8/u9/u10 for sparc; Solaris 10 u10 is

recommended.
Note: Solaris10 u8 does not support RNCV4.11.20.06.
5.5.1 Uploading Installation Package
Use the root user and the ftp/sftp service of the OS to upload
NDS_GU_V13.20.01_Release_Solaris.tar.gz to the /NDS/install path of the
server in the bin mode through Filezilla FTP Client.
5.5.2 Checking the MD5 of the Installation Package
Log in to the server as user root, open the path of the installation package, and check
the MD5 of the NDS_GU_V13.20.01_Release_Solaris.tar.gz installation
package file with the digest commands to make sure the file transmission is correct.
# cd /NDS/install
# digest -v -a md5 NDS_GU_V13.20.01_Release_Solaris.tar.gz
md5 (NDS_GU_V13.20.01_Release_Solaris.tar.gz) = 272bca06d36622937f78868e9b928990
The above example is only for reference. Because MD5 is different for different NDS-
GU versions released, if there is some problem with md5, contact the technical engineer
to confirm the correct MD5 and get the correct installation package.
5.5.3 Unzipping Installation Package
Unzip the installation package with the following commands:

# cd /NDS/install
# gunzip NDS_GU_V13.20.01_Release_Solaris.tar.gz
# tar xvf NDS_GU_V13.20.01_Release_Solaris.tar
The NDS-GU.tar installation package and the NDSInstall.sh script are generated
under the original directory after the package is unzipped.
5.5.4 Executing the NDSInstall.sh Installation Script
The NDSInstall.sh command can be attached with one or two parameters, as shown
below.
# ./NDSInstall.sh /NDS
or
# ./NDSInstall.sh /NDS --sftp
Parameter 1: /NDS. It is the installation path. If the path does not exist, it will be created
by default. Install NDS in this folder, of which the space should be large enough.
Parameter 2: --sftp. It means the sftp server is used, and the system will not check
whether ftp server is installed anymore. If this parameter is not configured, NDS will
check whether ftp service is installed, if not, the ftp service will be installed automatically.
Note: Parameter 1 must be filled in, while parameter 2 is optional according to the
requirement.
Check whether the hardware meets the requirement before the installation. If the
hardware meets the requirements, the following information will appear, and the service
will be started automatically.
Are you sure to install NDS_GU_V13.20.01_Release_Solaris to /NDS? [y..n]y
yes is selected
start install NDS_GU_V13.20.01_Release_Solaris
Begin check hardware condition...
/NDS
Free Disk Space(GByte):
488
CPU num:
16
System Memory Size(MByte):
32768
Hardware conditon check success!
install NDS to /NDS
/export/home/install
add group nds success
create user nds success
create user zte success
create user netmax success
start NDS service
starting NDS service
start NDS service success
If the hardware does not meet the requirement, the software cannot be installed
successfully. In this case, check whether is some hardware configuration fault.
In the installation process, if the system prompts that NDS has existed and the
installation cannot be continued, refer to Section 8.3 to handle this problem.
5.5.5 Checking Services
After the installation is completed, check whether NDS-GU service is started normally. If
there is some problem, refer to Section 7.1.3.2 to restart related services.
# svcs |grep NDS
online 10:19:22 svc:/application/NDS/NDSService:NDSD
online 10:19:22 svc:/application/NDS/NDSWatchService:NDSWATCHD
online 10:19:23 svc:/application/NDS/NDSICEService:NDSICED
online 10:19:23 svc:/application/NDS/NDSDPSService:NDSDPSD
online 10:19:25 svc:/application/NDS/NDSMRSERVERService:NDSMRSERVERD
online 10:19:31 svc:/application/NDS/NDSCDTSERVERService:NDSCDTSERVERD
5.6 Uninstalling NDS in Solaris OS
5.6.1 Executing the Uninstall Script
Open the NDS-GU installation path, and execute the NDSUnInstall.sh script to
uninstall NDS.
# ./NDSUnInstall.sh
In the uninstall process, a prompt will pop up, querying whether to delete the MR/CDT
and other data files under the Data and FTP directories. Input “y” to delete them and “n”
to cancel the deletion.
Note: If “n” is typed in, all the MR/CDT data downloaded under the Data directory as
well as the interface files under the FTP directory will be deleted.
6 NDS Service Configuration
The Web configuration mode is added in NDS-GU V13.40. To avoid the fault due to the
manual modification of configuration files, use the Web mode to modify the configuration
items.
Note:
If the corresponding file needs to be modified manually, modify it as the nds user (the user
created automatically when NDS is installed). Otherwise, the owner of NDS related
configuration files tends to change, and consequently NDS cannot read these files.
6.1 Configuring NDS in the Web Mode
Because manual modification of configuration file is likely to cause some error, NDS
provides the Web configuration mode for common items.
The method of entering the NDS Web configuration interface is as shown below, with
NDS ip=10.67.23.59 as the example:
Use a browser (such as IE, Chrome, etc.) to visit http://10.67.23.59:8000. IE7, IE8, and
Chrome are recommended, because there may be some display problem if other
browsers are used.
For the first login, type in user name “netmax” and password “netmax123.”
The following interface appears if the login succeeds.

Configure NDS file, data sources, and disk manager in the General tab.
Configure UMTS northbound switch and NetMax switch in the UMTS tab.
Configure GSM northbound switch and NetMax switch in the GSM tab.
Configure UMTS VIP user and complaint user related items in the DPS tab.
The Advance tab is only for the commissioning of development engineers.
6.2 Description of Application Scenarios
Refer to the following sections for the reference documents needed for each scenario.
Note:
If several scenarios need to be configured at the same time, check the configuration
chapter of each of the following related scenarios. For different NE versions, if there are
no special descriptions about NE version, it is necessary to configure related chapters.
If it is necessary to modify the XML file, modify it on the server with the vi tool. After the
modification is completed, download the file to the local Windows client, and open it with
IE or xml editor to see whether the format is correct. It is forbidden to upload the
modified file to the server directly. Otherwise, there may be some illegal characters (the
coding mode varies in different OSs, and the coding modes may be incompatible with
each other sometimes).
The contents of the configuration file are case-sensitive.
The ftp/sftp user for the northbound is “zte” and the password is “zte123.” Whether it is
ftp or sftp depends on which protocol is used when NDS is installed. The main directory
on NDS is [NDS-GU installation path]/Ftp/.
During the installation of NDS, another user is created automatically, i.e., nds, of which
the password is “nds123.” The main directory on NDS is [NDS-GU installation
path].
6.2.1 Scenario 1: GSM V3 NE
6.2.1.1 For NetMax-G
6.3 Configuring NDS Data Collection
6.4 Configuring Northbound Files
6.6 Configuring MR Preliminary Statistics File
6.7 Configuring MR Positioning Accuracy Improvement File
6.8.1 Configuring GSM V3 RAP Installation
6.2.1.2 For Northbound

6.2.2 Scenario 2: GSM V4 NE
6.2.2.1 For NetMax-G
6.8 Configuring Specific Version
6.2.3 Scenario 3: UMTS V3 NE
6.2.3.1 For NetMax-U
6.5 Configuring UMTS CT Files Download
6.8.2 Configuring Timezone

6.8.2 Configuring Timezone
6.2.4 Scenario 4: UMTS V4 NE
6.2.4.1 For NetMax-U
6.5 Configuring UMTS CT Files Download
This section introduces the basic configuration of NDS commissioning data collection.
Configure the data according to the scenario.
6.3.1 Overview of NDS Data Collection Configuration
This section describes the configuration of common parameters, which are different for
different GSM BSC versions.
6.3.1.1 Web Configuration Mode
Click General > DiskManager configuration, and modify Data Keep Days and Disk
Maintain Period of the northbound files.
Note:
Click the submit button to submit the modification to the server. Note: If this configuration
is modified, it is necessary to restart NDSD service.
6.3.1.2 Configuration File
Note: If the configuration is made by the Web configuration mode, it is not necessary to
modify the configuration files. Just in case, check the configuration files and make sure
the Web configuration mode has taken effect.
[NDS-GU installation path]/Config/NDS_Config.xml: Restart the key NDS service (ndsd)

after the modification, and check the [NDS-GU installation
path]/Log/NDSPy_JobSchedule.log file. Check whether there is some error in the
configuration file.
[NDS-GU Installation Path]/Config/NDS_ProcessJobs.xml: Restart the key NDS service

(ndsd) and DPS service (ndsdpsd) after the modification. Do not modify this
configuration file without R&D engineers’ permission. The configuration file supports
regular expression and there will be some special matching characters.
Note:
Check this configuration file, and delete inexistent NE information to avoid wasting system
resources. The configuration information of each NE starts with “<UMTSFtpSourceConfig”
or “<GSMFtpSourceConfig” and ends with “</UMTSFtpSourceConfig>” or
“</GSMFtpSourceConfig>”.
6.3.1.3 Configuration Description
NDS supports multi-task parallel processing, which can make full use of the advantage
of multi-CPU on the server and improve the system processing and response speed.
The configuration of NDS_Config.xml consists of disk maintenance, RNC/BSC data
source configuration, etc.
<NDSConfig NDSVersion="13.2" CpuPercent="70">

<DiskManagerConfig DataKeepDays="15" DiskMaintainPeriod="6" DiskUpRate="80"
DiskMaintainDirs="../FTP" />
<SourcesConfig>
<UMTSFtpSourceConfig RNCID="346" Area="021" MiningHours="12" Period="15"
HasSubDateDir="true">
<FtpInfo IpAddr="10.67.23.72" Port="21" Username="oracle" Password="oracle"
DefaultDir="/home/zte/data" SFtp="false"/>
</UMTSFtpSourceConfig>
<GSMFtpSourceConfig BSCID="53" Area="021" MiningHours="12" Period="5"
<FtpInfo IpAddr="10.67.23.85" Port="21" Username="ndsg" Password="ndsg"
DefaultDir="/home/zte/data" SFtp="false"/>
</GSMFtpSourceConfig>
<GSMLocalSourceConfig BSCID="54" Area="021" MiningHours="12" Period="5"
<LocalInfo Dir="../NDS-GV3RAP/data" Link="false"/>
</GSMLocalSourceConfig>
</SourcesConfig>
</NDSConfig>
Item Description Example
This is the version information of the system.

NDSVersion NDSVersion="13.2"
Do not modify it unless absolutely necessary.
CpuPercent="70":
CpuPercent The maximum percent of CPU used by NDS The upper limit of
CPU usage is 70%
It defines the number of days during which

the northbound interface data is saved.
DataKeepDa Monitor the number of data storage days in
DataKeepDays="15"
ys DiskMaintainDir. The directories outside the
defined days will be deleted in the disk
maintenance process.
DiskMaintainPeriod="
It is the period for executing disk 6"
maintenance. Disk maintenance is executed It means the
at the first minute after the program is maintenance is
DiskMaintain
started, and is executed once every two performed every six
Period
periods defined. (this configuration takes hours. The
effect at the next execution period after the recommended
modification) configuration is 6
hours or 12 hours.
The threshold of disk utilization rate (0-100).

When the utilization rate of the disk on which DiskUpRate="80": If
the directory is located exceeds the the disk utilization
DiskUpRate threshold, the directory of the earliest day will rate exeeds 80, the
be deleted until the disk utilization rate is earliest data files will
lower than the value. Recommended value: be deleted.
80 or above.
DiskMaintain The northbound interface file directory that DiskMaintainDirs="../

Dirs needs disk maintenance. FTP"
Defines the number of hours before which

MiningHours the data should be collected. The default MiningHours="12"
data storage directory is Data.
Period Data collection period. Period="15"
HasSubDateDir=”true
”: divided into
subdirectories by
HasSubDate Whether the data directory structure is date.
Dir divided into subdirectories by date. HasSubDateDir=”fals
NDS_ProcessJobs.xml is used to configure the time range information and the file
matching rules during the NDS decoding period.
NDS will calculate the number of hours

before which the data is to be decoded DecodeHours="4",
DecodeHours
according to the current system time, and unit: hour
generate the file under the FTP directory.
DecodePerid="5",
DecodePeriod The period of file refreshing.
unit: minute
6.3.2 Configuring FTP Connection Configuration of SBCX
The configuration of this section is required for GSM BSC V6.50 series and all UMTS
versions. Skip this section for other versions. The information of username, password,
path, and port should be acquired from NE engineers in advance.
In the NDS Web configuration, select General > Sources configuration to open the
Sources configuration interface, in which the configuration items can be added,
deleted, and modified.
Select UMTS Ftp, click the “add” button, and click Check in the pop-up UMTS Ftp
dialog box to check whether the link is connected.
Note:
1. Click OK to add an item, which is only added on the local interface and can be added
on the server by clicking the Submit button. Note: If this configuration is modified, it
is necessary to restart NDSD service.
2. Select GSM V6.50 for GSM, and select UMTS Ftp for UMTS.
If the configuration is made by the Web configuration mode, it is not necessary to modify
the configuration files. Just in case, check the configuration files and make sure the Web
configuration mode has taken effect.
Subnodes UMTSFtpSourceConfig and GSMFtpSourceConfig can be configured under

subnode SourcesConfig in the [NDS-GU Installation
Path]/Config/NDS_Config.xml file. They are used to configure UMTS data Ftp
download and GSM data FTP download respectively. Restart the key NDS service
(ndsd) after the modification.
Because NDS-GU communicates with the SBCX on RNC/BSC and collects RNC/BSC
data through the FTP protocol, it is necessary to make sure the TCP/IP network
connection between the server of NDS and the SBCX of RNC/BSC and the server can
be connected to the FTP server of SBCX. For the purpose of visiting different
RNCs/BSCs correctly, the IP, port No., username, and password of the SBCX on
RNC/BSC can be modified in the configuration file according to the on-site configuration.
The collected file will be saved in the format of [Date]/[Area]/[Format]/[RNCID/BSCID]/
[Data file]. The configuration content is as detailed below:
The Ftp configuration file consists of two parts, i.e., UMTS part and GSM part. The
configuration items of these two parts are almost the same. In the following description,
the configuration of RNC is taken as the example.
<UMTSFtpSourceConfig RNCID="346" Area="021" MiningHours="12" Period="15"
<FtpInfo IpAddr="10.67.23.72" Port="21" Username="oracle" Password="oracle"
DefaultDir="/" SFtp="false"/>
</UMTSFtpSourceConfig>
Default
Item Description Value Range
Value
Defines the number of

MiningHours="12"
hours within which the
MiningHours Integer: Min. value: 1; Max. 12
data should be
value: 72
collected.
Defines the period of

data collection. Unit:
minute
Period="15"
It is recommended that
It is recommended that this
this parameter be set
parameter be set to an
Period to an integral multiple 15
integral multiple of 15. It
of 15. (this
must be smaller than
configuration takes
“MiningHours*60.”
effect at the next
execution period after
the modification)
HasSubDateDir=”true”:
Whether the data divided into subdirectories
HasSubDateDi directory structure is by date.
true
r divided into HasSubDateDir=”false”: not
subdirectories by date. divided into subdirectories
by date.
RNCID="346". Configure Configure

The RNCID configured
this item as needed. Its this item
RNCID on the target RNC
value should not be the as
same as that of Area. needed
Area="021". Configure this Configure

The Area parameter in
item as needed. Its value this item
Area the file storage
should not be the same as as
directory
that of RNCID. needed
IpAddr="10.67.23.72".
Configure
The IP of the Ftp Configure this item as
this item
IpAddr service of the target needed. Do not fill in “0”
as
RNC SBCX before each byte, like
needed
010.067.023.072.
Configure
The listener port of the
Port="21". Configure this this item
Port Ftp service of the
item as needed. as
target RNC SBCX
needed
6.3.3 Data Source Configuration for GSM BSC V6.30
The configuration of this section is required for GSM BSC V6.50 series. Skip this section
for other GSM versions and UMTS versions.
In the NDS Web configuration, select General > Sources configuration to open the
Sources configuration interface, in which the configuration items can be added,
deleted, and modified (only for GSM V6.30).
Select GSM V6.30, click the “add” button, and click Check in the pop-up GSM V6.30
dialog box to check the path of the data sources.
Note:
Click OK to add an item, which is only added on the local interface and can be added on the
server by clicking the Submit button. Note: If this configuration is modified, it is necessary
to restart NDSD service.
Configure the local download parameter LocalInfo under subnode GSMLocalSourceConfig in the
[NDS-GU installation path]/Config/NDS_Config.xml file. Restart the key NDS
service (ndsd) after the modification.

<GSMLocalSourceConfig BSCID="54" Area="021" MiningHours="12" Period="5"
<LocalInfo Dir="../NDS-GV3RAP/data" Link="false"/>
</GSMLocalSourceConfig>
Item Description Value Range Default Value
Defines the number of

MiningHours="12"
hours within which the
MiningHours Integer: Min. value: 1; 12
data should be
Max. value: 72
collected.
Defines the period of

data collection. Unit:
minute Period="15"
It is recommended that It is recommended that
this parameter be set this parameter be set
Period to an integral multiple to an integral multiple 15
of 15. (this of 15. It must be
configuration takes smaller than
effect at the next “MiningHours*60.”
execution period after
the modification)
HasSubDateDir=”true”:
Whether the data divided into
HasSubDateD directory structure is subdirectories by date.
true
ir divided into HasSubDateDir=”false
subdirectories by date. ”: not divided into
subdirectories by date.
BSCID="54".
Configure this item as
The BSCID of the BSC
needed. The Configure this
BSCID SBCX for data
combination of BSCID item as needed.
collection
and Area should be
unique.
Area="021". Configure
The Area parameter in this item as needed.
Configure this
Area the file storage The combination of
item as needed.
directory BSCID and Area
should be unique.
The local path of the

data source can be an
LocalInfo Dir="../NDS-
absolute path or a
GV3RAP/data" LocalInfo
relative path. The
LocalInfo Dir It means using the Dir="../NDS-
relative path is the Bin
relative path as the GV3RAP/data"
directory under the
data source.
corresponding NDS
6.3.4 DSP Configuration
The configuration in this section is required if NetMAX-U is connected. Skip this section
if it is not connected. It is only for UMTS.
Click DPS > VIP configuration/Complaint configuration, and configure VIP user and
complaint user function related NetMAX IP and collection period, as shown in the figures
below:
Note:
There is no Submit button in this interface. The configuration is submitted once it is
modified. If the configuration in this interface is modified, it is necessary to restart the
DPSD service.
Path of configuration file: [NDS-GU installation path]/Config/DPS_DataCollectOptions.ini
Required item: NetMAXIP = 127.0.0.1 //Configure this item according to the

configuration of the existing network.
Unchangeable item: NDSFTPPath = ../Data //This item cannot be modified.
Unchangeable item: AnalyziedDataPath = ../Data/VIPData/UMTS //This item cannot be

modified.
Other items can be configured as needed, for which the default values are
recommended. Restart DPS service (ndsdpsd) after the configuration is modified. As to
the restart method, refer to Sections 7.1.3.1.3 (Linux) and 7.1.3.2.3 (Solaris) for details.

[Main]
;Note: Whether DPS needs to import data into NetMAX-U Server. 0-not import, 1-import,
default: 1
IsImport = 1
;Note: the IP of the NetMAX-U Server connected with DPS. It should be configured
according to the configuration in the existing network.
NetMAXIP = 127.0.0.1
;Note: the port of the NetMAX-U Server connected with DPS. Default: 18222.
NetMAXPORT = 18222
;Note: DPS collection period. Unit: minute; default: 15 minutes:

CollectCycle = 15
;Note: The path of the raw data of the DPS to be processed. The configuration here
cannot be modified.
NDSFTPPath = ../Data
;Note: Whether offline collection is supported. 0-Not supported,1-Supported. Default:
0.
IsOfflineCollection = 0
;Note: If offline collection is supported, fill in the IMSI list, and separate the
IMSIs with comma, e.g., IMSI1,IMSI2,IMSI3....
OfflineCollectionUserList =
;Note: The storage path of the data processed by DPS The configuration here cannot be
modified.
AnalyziedDataPath = ../Data/VIPData/UMTS
;Note: Min. disk space & file cut size. Unit: MB. Default: 5000MB, 20MB
MinDiskFreeSpace = 5000
FileCutSize = 20
;Note:the number of days that DPS processes data; unit: day Default: three days, i.e.,
DPS processes three days of data.
CollectDays = 3
;Note: the time limit of a single DPS sampling task. Unit: second. Default: 3600
seconds
ThreadMaxLiveTime = 3600
; Note: the maximum number of buffer days of the temporary DPS collection data
directory NDSTemp. Unit: day. Default: 2 days
NDSTempBufferDays = 2
;DPS ID: if there is more than one DPS, configure a different value to the DPS. The
range of DPS ID is 1-99.
DPSID = 1
UploadRegExp = ^ZTE_MUMRU_UMTS.*dat$|^ZTE_MUCDTEX_UMTS.*data1$
DecoderDetailRegExp = ^ZTE_MUCDTEX_UMTS.*dat$
FilterDatas = ^ZTE_MRU_UMTS.*dat(.*.gz){0,1}$|^ZTE_CDTEX_UMTS.*dat(.*.gz){0,1}$
6.3.5 Configuring GSM V3 Data
The configuration in this section is required for GSM BSC V6.20 series. Skip this section
for other series.
Note: Web configuration mode is not available for the contents in this section. The files
must be modified manually. The configuration file is case-sensitive and the contents are
in English characters.
6.3.5.1 MR Data
Note: After the mrcfg.ini parameter is modified, it is necessary to restart mrserver

(ndsgv3mrd) and key NDS service (ndsd). Refer to Sections 7.1.3.1.3 (Linux) and
7.1.3.2.3 (Solaris) for the restart method.
Path of configuration file: [NDS-GU installation path]/NDS-GV3/mr/mrcfg.ini
The parameters of the mrcfg.ini configuration file are as shown below:

#Note: After parameter mrcfg.ini is modified, restart MR Server and key NDS service,
and execute the following commands:
# For Solaris, execute the following commands:
#svcadm disable NDSMRSERVERD
#svcadm enable NDSMRSERVERD
#svcadm disable NDSD
#svcadm enable NDSD
# For Linux, execute the following commands:

#service ndsgv3mrd stop
#service ndsgv3mrd start
#service ndsd stop
#service ndsd start
[GENERAL]
#OMCR ID: it is used to generate the MR data file, and the value should be smaller
than “256.”
OMCRID = 129
#MR version: the valid length is one byte, i.e., a figure or a character.
VERSION = 1
#Number of BSCs, including BSC and iBSC.

BSCNum = 3
#Local listener port of MR server

MRPort = 15000
#Log level
#0 Trace Off
#2 BASE
#4 DEBUG
TraceLevel = 2
#Whether to generate the raw data

#0 off
#1 on
RAW = 0
#Whether to collect the statistics

#0 off
#1 on
STATISTIC = 1
#Statistics type
#NOP
#Actix
#Optimi
#Ucell
#ChinaMobile
STATTYPE = Actix
#The number of days that the data files are kept in system:
LRetained = 3
#Electrical level correction switch

#0 off
#1 on
MRCorrect=0
#correct value
CorrectValue=12
#The period of merging statistics files

#Currently, only Active statistics files can be merged.
#-1 Not merge
#0~23 It is recommended that the files be merged in the wee hours like 3:00 am or
4:00 am.
StatMerge = -1
#When STATTYPE is Ucell, the following two parameters take effect
DB_Value_High=6
DB_Value_Low=0
[BSC1]
#The following configuration is for BSCV2
#BSC ID
BSCID = 190
#The number of modules: it refers to the RRM module, not including the slave module.
ModuleNum = 4
#Module ID = Module ID
ModuleID1 = 2
ModuleID2 = 3
ModuleID3 = 4
ModuleID4 = 5
#The IP of each module; if there is the slave module, fill in the IP of the slave
module after that of the master module, and separate the IPs with space.
#If there is no slave module, there is no need to fill in the IP
IP1 = 192.168.190.2 192.168.190.34
IP2 = 192.168.190.3 192.168.190.35
IP3 = 192.168.190.4 192.168.190.36
IP4 = 192.168.190.5 192.168.190.37
#The BSC peak traffic estimated

ERL = 1000
#When STATTYPE is ChinaMobile, if NE does not report base station TX power, the
following parameter takes effect.
#BTS Tx power dbm (with the combiner’s wastage deducted)
BtsMaxPwr = 47
[BSC2]
#The following configuration is for iBSC
#iBSC ID
BSCID = 1
#When STATTYPE is Ucell, the following three parameters take effect
ServerID = 10001
SubNetworkID= 1
UserLabel =
#Number of CMPs (excl. the slave CMP)

ModuleNum = 1
#CMP ID = CMP Module ID. One CPM has two Module IDs, which are separated by space.
#Fill in the Module ID of the master CMP. The IP and Module ID of the salve CMP are
the same as those of the master CMP.
ModuleID1 = 3 4
#The IP of each CMP

IP1 = 192.168.190.101
#The iBSC peak traffic estimated

ERL = 6200
[BSC3]
#The following configuration is for iBSC
#iBSC ID
BSCID = 2

ModuleNum = 2
ModuleID1 = 3 4
ModuleID2 = 5 6
#The IP of each CMP

IP1 = 192.168.190.253
IP2 = 192.168.190.253
#The iBSC peak traffic estimated

ERL = 6000
Pay attention to the following points when modifying the mrcfg.ini file.
1. Configure mrcfg.ini as needed. If too many inexistent modules are configured,

the execution efficiency of MR Server will be reduced.
2. When filling in IP addresses, do not complement “0,” e.g., for 10.9.7.4, do not fill it
in as 010.009.007.049.
3. If there is no data on some NE, check whether the link between NDS and the
existing CMP is established.
#netstat -n |grep 15000
(15000 is the communications port configured on NDS and BSC), if the following
information is prompted, the link is established.
192.168.1.1.15000 192.168.190.101.14467 65535 0 64440 0 ESTABLISHED
The files used by the northbound interface are exported to the following directories:
1. The source file outputted is under the [NDS-GU installation

path]/FTP/raw directory.
2. The statistics file outputted is under the [NDS-GU installation

path]/FTP/stat directory.
The file used by NetMax is exported to the following directory:
The source file outputted is under the [NDS-GU installation path]/Data/…/

MR/ directory.
6.3.5.2 CDT Data
Note: After the cdtcfg.ini parameter is modified, it is necessary to restart mrserver

(ndsgv3mrd) and key NDS service (ndsd). Refer to Sections 7.1.3.1.3 (Linux) and
7.1.3.2.3 (Solaris) for the restart method.
Path of configuration file: [NDS-GU installation path]/NDS-GV3/CDT/cdtcfg.ini.
The parameters of the cdtcfg.ini configuration file are as shown below:

#Note: After parameter cdtcfg.ini is modified, restart CDT Server and key NDS service,
#svcadm disable NDSCDTSERVERD
#svcadm enable NDSCDTSERVERD
#svcadm enable NDSD

#service ndsgv3cdtd stop
#service ndsgv3cdtd start
#service ndsd stop
#service ndsd start
[GENERAL]
#Cityarea ID
cityarea = 021
#For CDT Server, only one version is allowed to be configured.

#6.20.614 series, configure it to 6.20.614c or 6.20.614d as needed (the c and d must
be in the lower case).
#For 6.20.620 series, the version should be configured to 6.20.620f (the f must be in
the lower case).
#For 6.20.711 series, the version should be configured to 6.20.711d (the d must be in
the lower case).
#For 6.20.712 series, the version should be configured to 6.20.712c (the c must be in
the lower case).
#For 6.20.713 series, the version should be configured to 6.20.713d (the d must be in
the lower case).
VERSION = 6.20.614c
#Number of iBSC: the iBSCs that have CDT enabled should be configured in the CDT
configuration files.
BSCNum = 2
#The local listener port of CDT Server. Modify the configuration of this port, as well
as the settings of iBSC.
CDTPort = 15006
#Log level: usually the default “#2 BASE” is configured. If “#4 DEBUG” is
configured, a large amount of log information will be printed.
#0 Trace Off
#2 BASE
#4 DEBUG
TraceLevel = 2
#The number of days that the data files are kept in system:
LRetained = 3
#Waiting time (seconds) for call timeout, default=10800s

CallTimeOut = 10800
#Maximum data file size (M), default=64M

MaxFileSize = 10
#CDT supports iBSC only, and does not support BSCV2.

[BSC1]
#iBSC ID. Set it to the BSC ID actually used. Note: The first digit should not be
“0.”
BSCID = 1

ModuleNum = 1
#Note: Do not set this item to “12.”
ModuleID1 = 3 4
#The IP address of a CMP: for V3, each CMP corresponds with one IP address.
IP1 = 127.0.0.1
[BSC2]
#iBSC ID. Note: The first digit should not be “0.”
BSCID = 2

ModuleNum = 2
#Note: Do not set this item to “12.”
ModuleID1 = 3 4
ModuleID2 = 5 6
#The IP address of a CMP: for V3, each CMP corresponds with one IP address.
IP1 = 127.0.0.1
IP2 = 127.0.0.1
Pay attention to the following points when modifying the cdtcfg.ini file.
Configure the cdtcfg.ini based on the actual information. If too many modules that do not
exist are virtually configured, the CDT Server execution efficiency will be decreased and
CPU and memory will be wasted.
When filling in IP addresses, do not complement “0,” e.g., for 10.9.7.49, do not fill it in as
010.009.007.049.
The CDT source file outputted is under the [NDS-GU installation

path]/Data/Date/Area ID/GSM/BSCID/CDTEX/ directory, e.g.,
[NDS-GU installation path]/Data/20140310/021/GSM/1502/CDTEX/
The contents of this section need to be configured only when the operator requires the
northbound configuration. The files outputted are under the [NDS-GU installation
path]/FTP/ subdirectory. Note: Sometimes, the network optimization team (NetMax
team) also requires the configuration of these parameters and needs the file of the
corresponding format for analysis.
6.4.1 Web Configuration Mode
Select UMTS > North Interface Configuration, and there is the UMTS northbound
interface switch, as shown in the figure below:
Select GSM > North Interface Configuration, and there is the northbound interface
switch of GSM V6.50 and V6.30 series, as shown in the figure below:
Note: Only one value can be typed in for OMCRID, and it must be an integer.

modified.
After the configuration in this interface is modified, it is not necessary to restart any
service.
The Web configuration mode is not available for the NEs of GSM V6.20 series, and the
mrcfg.ini configuration file needs to be modified manually.
6.4.2 Configuration File
After [NDS-GU installation path]/Config/DataManage.ini or [NDS-GU

installation path]/NDS-GV3/mr/mrcfg.ini is modified, there is no need to
restart any services, which will take effect when the next task is started.
6.4.3 Configuration Description
DataManage.ini is used mainly to configure the parameters of the northbound file.

This configuration file falls into two parts, i.e., GSM northbound configuration and UMTS
northbound configuration. Note: For GSM BSCV6.20, the mrcfg.ini configuration file,
instead of DataManage.ini needs to be modified.
6.4.4 Configuration Content
6.4.4.1 GSM Northbound Configuration
For GSM 6.30 and 6.50 series, it is necessary to configure the [NDS-GU
installation path] / Config/ DataManage.ini file.
For GSM 6.20 series, it is necessary to configure the [NDS-GU installation

path]/NDS-GV3/ mr/ mrcfg.ini file.
The following are the examples of the DataManage.ini file and the mrcfg.ini file.
The following is the example of the DataManage.ini file.

#======================GSM Configuration Start====================================
[Summary]#Internal use,Forbidden to modify
#Optional parameter. By default, the data of the previous hour before the current time
is collected.
#To collect the data of a certain time, fill in the following parameter, in the
“2012-04-28-08” format, which means collecting the data of 8’o clock, Apr. 28 th,
2012.
TimePoint =
[LOG_Param]#GSM V4 MR decoding log/Log switch, 1:off, 0:on

#GSM V4 MR decoding log, 1: disable, 0:enable, default: disable
LogLevel = 1
[GSM_Param]#GSM MR statistical configuration
OMCRID = 129
#Statistical type
#NOP
#Actix
#Optimi
#Ucell
#CMCC
#STATTYPE equal empty means can't output statistical files
STATTYPE = Actix
#Electrical level correction switch,0:off, 1:on

#0 off
#1 on
MRCorrect=0
#Correction value
CorrectValue=12
#When STATTYPE=Ucell,the following two parameters take effect

DB_Value_High=6
DB_Value_Low=0
#///////GSM CMCC Param start////////////

#When STATTYPE=CMCC,section 'BSC CMCC Num' and 'BSC CMCC Param' take effect
#If user don't need this parameter, use the default configuration
[BSC CMCC Num]
CMCCBSCNUM = 2
#When STATTYPE=CMCC and BSC is not reported to base station transmission power, user
can config the 'BtsMaxPwr' value
[BSC1 CMCC Param]

BSCID = 1
BtsMaxPwr = 47
[BSC2 CMCC Param]

BSCID = 53
BtsMaxPwr = 47
#///////GSM CMCC Param end ////////////
#///////GSM UCell Param start////////////

#When STATTYPE=Ucell,section 'BSC UCell Num' and 'BSC UCell Param' take effect
#If user don't need this parameter, use the default configuration
[BSC UCell Num]
UCellBSCNUM = 2
[BSC1 UCell Param]

BSCID = 1
ServerID = 10001
SubNetworkID= 1
UserLabel = label1
[BSC2 UCell Param]

BSCID = 53
ServerID = 10001
SubNetworkID = 1
UserLabel =
#///////GSM UCell Param end////////////
[Netmax_Param]#GSM MR CI Configuration switch, 0:off, 1:on

mrci=0
#GSM MR China Unicom North Interface switch, 0:off, 1:on

mr=0
#output Dir
OutDir = ../FTP
[GSM_VIP_CONFIG]#VIP output switch, 0:off, 1:on

OutputFlg=0
The following is an example of the mrcfg.ini file:

#Note: After parameter mrcfg.ini is modified, restart MR Server and key NDS service,
#svcadm disable NDSMRSERVERD
#svcadm enable NDSMRSERVERD
#svcadm enable NDSD
#service ndsgv3mrd stop
#service ndsgv3mrd start
#service ndsd stop
#service ndsd start
……
#Whether to generate the raw data

#0 off
#1 on
RAW = 0

#0 off
#1 on
STATISTIC = 1
#Statistics type
#NOP
#Actix
#Optimi
#Ucell
#ChinaMobile
STATTYPE = Actix
……
#-1 Not merge
4:00 am.
StatMerge = -1
6.4.4.2 UMTS Northbound Interface Configuration
Check whether the stat switch under the NetMAX_UMTSMR line in the
DataManage.ini file on NDS is enabled. This switch determines whether to output the
MR interface file (this switch is available for NDSV13.2 and later versions). If the
CT/DPI/EMI is to be outputted, it is also necessary to check whether the switch is
enabled.
#======================UMTS Configuration Start====================================
[MR_LianTong]#UMTS MR China Unicom North file switch, 0:off, 1:on

OutPut=0
[CDT_LianTong]#UMTS CDT China Unicom North file switch, 0:off, 1:on

OutPut=0
6.4.5 GSM Frequency Change Sample Configuration
This section deals with the configuration in the GSM AFP frequency change scenario.
CI data is needed in frequency change, and it can be acquired from MR northbound

data. For the NEs of GSM V6.30 and V6.50 series, STATTYPE must be set to “Actix” in
Web configuration, as shown in the figure below:
This parameter can also be modified in the DataManage.ini file. The parameter in red
must be set to the value in the following example, as shown below:
#======================GSM Configuration Start====================================
[GSM_Param]#GSM MR statistical configuration

OMCRID = 129
#Statistical type
#NOP
#Actix
#Optimi
#Ucell
#CMCC
#STATTYPE equal empty means can't output statistical files
STATTYPE = Actix
For the NEs of the GSM V6.2 0 series, it is necessary to configure the mrcfg.ini file,
which can only be modified manually because the Web configuration mode is not
available. The following is an example:
……
#0 off
#1 on
STATISTIC = 1
#Statistics type
#NOP
#Actix
#Optimi
#Ucell
#ChinaMobile
STATTYPE = Actix
……
#-1 Not merge
4:00 am.
StatMerge = -1
……
6.5 Configuring UMTS CT Files
The configuration of this section is required only when NetMAX-GU is connected and
UMTS related functions are used. In other cases, skip this section.
Select UMTS > NetMAX Parameter Configuration, and configure the UMTS CT, EMI,
and DPI download switches, as shown in the figure below.
Note:
modified.
After the configuration in this interface is modified, it is not necessary to restart any service.
After [NDS-GU installation path]/Config/DataManage.ini is modified,

there is no need to restart the services, which will take effect when the next download
task is started.
Whether NDS downloads the CT, DPI, and EMI files of UMTS can be configured. By
default, it does not download the CT file, and downloads only the DPI and EMI files.
[NetMAX_UMTSCT]#UMTS non-vip CT configuration switch, 0:off, 1:on
DownloadCT = 0
#non-vip abnormal event correlation analysis switch, 0:off, 1:on

AbnomalParse = 1
[NetMAX_UMTSDPI]#UMTS DPI configuration

#DPI switch, 0:off, 1:on
DownloadDPI = 1
[NetMAX_UMTSEMI]#UMTS EMI configuration

#EMI switch, 0:off, 1:on
DownloadEMI = 1
[NetMAX_UMTSCDT]#NetMAX UMTS CDT output switch, 0:off, 1:on

output=1
The configuration in this section is required only when NetMAX-GU is connected. Skip
this section if it is not connected.
Select UMTS > NetMAX Parameter Configuration, and configure the UMTS MR
preliminary statistics switch, as shown in the figure below.
Select GSM > NetMAX Parameter Configuration, and configure the GSM MR
preliminary statistics switch, as shown in the figure below.
Note:
modified.
After the configuration in this interface is modified, it is not necessary to restart any service.
After [NDS-GU installation path]/Config/DataManage.ini is modified,

there is no need to restart any services, which will take effect when the next task is
started.
The DataManage.ini file contains the NetMAX MR preliminary statistics related

configuration items. It has two parts, i.e., GSM MR preliminary statistics configuration
and UMTS MR preliminary statistics configuration.
Pay attention to the label in the configuration: whether it is [Netmax_GSMMR] or

[Netmax_UMTSMR], which is highlighted in red in the following two sections.
6.6.4.1 GSM MR Preliminary Statistics Configuration

[NetMAX_GSMMR]#NetMAX GSM MR preliminary statistics switch, 0:off, 1:on
stat=0
#MR positioning switch,0:off, 1:on
location=0
#BSC control switch, 0:off, 1:on

bscctrl=0
#BSC control list, partition with semicolon. e.g.53;54;55
bsclist=
#Time control switch, 0:off, 1:on
hourctrl=0
#Time control list, partition with semicolon. e.g.08;09;10
hourlist=
6.6.4.2 UMTS MR Preliminary Statistics Configuration

[NetMAX_UMTSMR]#NetMAX UMTS MR preliminary statistics switch, 0:off, 1:on
stat=0
#RNC control switch, 0:off, 1:on

rncctrl=0
#RNC control list, partition with semicolon. e.g.201;202;203
rnclist=
#Time control switch, 0:off, 1:on
hourctrl=0
#Time control list, partition with semicolon. e.g.08;09;10
hourlist=
#MR positioning switch,0:off, 1:on

location=0
6.7 Configuring MR Positioning Accuracy

Improvement File
The configuration in this section is required only when NetMAX-GU is connected. Skip
this section if it is not connected.
This configuration is required for NodeB V4.12.10.15 and previous versions. Skip this
section for NodeB V4.12.10.15P01/4.12.10.15P10 and later versions. Web configuration
mode is not available for this configuration. The configuration file can only be modified
manually.
After [NDS-GU installation path]/Config/Location.ini is modified, there

is no need to restart any services, which will take effect when the next task is started.
In UMTS NodeB V4.12.10.15 and previous versions, the RTT data reported by NodeB
has the protection interval of 7-7 chips (BPC:5chips, BPK:7chips). In this case, the RTT
distance calculated by the formula will be increased by over 200 meters, leading to
inaccurate positioning. Modify the Location.ini file to perform RTT compensation by
reducing 5 chips (set RTTMinusMeters “195” manually; default: 0).
For the upgrade of NodeB version to 4.12.10.15P01/4.12.10.15P10 or a later version,

this configuration is not needed.
Normally, configuration items RTTDiscountPercent and DirectionType do not need to be

modified. RTTDiscountPercent: unit: percent; range: 0-100DirectionType: not enabled
currently.
Configure the maximum distance of indoor base stations. By default, the value of
MaxDis is “50,” i.e., the distance of the indoor base station is 50 meters by default.

[Position]
#0~100
RTTDiscountPercent = 100
#>0
RTTMinusMeters = 0
#0 or 1
DirectionType = 0
#Set position distance when no RTT,-1 means postion RTT as (-999,-999)

[NoRTTPositionDistance]
#MR position distance when no RTT,default:-1
MR = -1
#CDT last MR position distance when no RTT,default:1000
CDT_MR = 1000
[StationInRoom]
MaxDis=50
6.8 Configuring Specific Versions
Note: This section is applicable only to GSM BSC V6.30 series.
After GSM V3 RAP installation is started, if the data from a BSC needs to be received,
make sure the BSC is connected with the GSM V3 RAP server. If the communications
are not connected in some subnetwork, it is necessary to add the route to the BSC on
the GSM V3 RAP server. Ping the IP of the BSC to check whether the communications
between the BSC and the GSM V3RAP server are connected. If the communications
are not connected, add the route with the following method.
6.8.1.1 Installation Configuration in Linux OS
In the Linux OS, execute the following command to add the route.
route add -net 118.18.1.30 gw 128.0.0.10 netmask 255.255.255.255
Note 1: 118.18.1.30 is used to configure dynamic SCTP.
128.0.0.10 is the interface IP of the interface board that communicates with NDS.
Note 2: BSC and NDS are connected through a switch. Therefore, the IP of the interface
board and NDS should be in the same subnet.
6.8.1.2 Installation Configuration in Solaris OS
In the Solaris OS, execute the following command to add the route.
route add -net 118.18.1.30 -netmask 255.255.255.255 128.0.0.10
6.8.1.3 V3 RAP Disk Maintenance
V3 RAP data generation disk is maintained independently. It is necessary to edit the

SysArchiveCtrl.conf file under the [NDS-GU installation path]/NDS-
GV3RAP/logservice/bin/conf/ directory. After the configuration is modified, it is
necessary to restart v3rap service (ndsv3rapd). Refer to Sections 7.1.3.1 (Linux OS)
and 7.1.3.2 (Solaris OS) for the restart method.
[DataFileSave]
SAVEDAY=1 //the number of days that the data under [NDS-GU installation
path]/NDS-GV3RAP/data is saved.
6.8.2 Configuring Time Zone
The configuration in this section is required only for the NEs of UMTS V3.11.10.11P04
and earlier versions. Skip this section for the NEs of other versions. There is no need to
configure timezone for UMTS V3.11.10.11P05.
After [NDS-GU installation path]/Config/TimeZoneOffset.ini is modified,

there is no need to restart any services, which will take effect when the next task is
started.
TimeZoneOffset.ini is used mainly to configure the timezone compensation of

different RNC versions. Timezone compensation is not performed by default. The
timezone, DST, and clock of the NEs managed by NDS should be consistent, and the
system clock of NE, NDS, and NetMAX should be the same. Otherwise, some problems
may occur, such as, data cannot be collected, or the data is displayed incorrectly.
For the NEs of UMTS V3.11.10.11P04 and earlier versions, both timezone and DST
need to be taken into account when timezone compensation is made. For other
versions, the time reported by the NEs already contains the timezone and DST, so it is
not necessary to perform compensation for these NEs.
6.8.2.3 Configuration Content

[UMTS_Time_Zone_Offset]
V3.11.10.11=8
V3.11.10.08=0
V3.11.10.12=0
V4.11.20.06=0
V4.12.10.08=0
V4.12.10.14=0
For example:
The configuration for V3.11.10.11 data in the Shenzhen project:
V3.11.10.11=8
The configuration for V3.11.10.11 data in the Austria project:
V3.11.10.11=2 (The “2” here is calculated by adding 1 hour of DST. For non-DST
months, set it to “1.)
7 System Acceptance and Maintenance
This chapter introduces the check and maintenance method of the NDS-GU software
system.
7.1 Observing System Operation Status
7.1.1 Checking System Installation State
Check the services registered automatically after system installation and the services
started automatically after the server is started. Refer to Section 7.1.3.1.4 (Linux OS)
and Section 7.1.3.2.4 (Solaris OS) to check service status. Check the service operation
status of Linux and Solaris respectively.
7.1.2 Checking Service Processes
When the system runs normally, there are some resident processes, such as
NDS_JobSchedule, NDS_MUDataCollect, mrserver, and cdtserver. Execute the
following commands to see whether these processes run properly.
$ ps –eaf | grep NDS_JobSchedule
$ ps –eaf | grep NDS_MUDataCollect
$ ps –eaf | grep mrserver
$ ps –eaf | grep cdtserver

7.1.3 Starting, Stopping, and Restarting NDS Software
This section introduces the method of starting, stopping, and restarting NDS-GU
software.
7.1.3.1 Linux Version
The NDS-GU services can be started or stopped by the service command of Linux. It is
recommended that the operations to NDS services be performed as the root user.
Note: The service related commands are under the /sbin directory of OS by default.
7.1.3.1.1 Starting Services
NDS Linux has six services. After the OS is restarted, all the services of NDS will be
started automatically. If the services are stopped manually, it is necessary to restart the
services. The methods of starting the six services are as listed below:
1. Start the NDS service with the following command:

# service ndsd start
2. Start the DPS service with the following command:

# service ndsdpsd start
3. Start the ICE service with the following command:

# service ndsiced start
4. Start the mrserver service with the following command:

# service ndsgv3mrd start
5. Start the cdtserver service with the following command:

# service ndsgv3cdtd start
6. Start the v3rap service with the following command:

# service ndsv3rapd start
7.1.3.1.2 Stopping Services
Execute the following commands to stop the services manually:

1. Stop the NDS service with the following command:
# service ndsd stop
2. Stop the DPS service with the following command:

# service ndsdpsd stop
3. Stop the ICE services with the following command:

# service ndsiced stop
4. Stop the mrserver service with the following command:

# service ndsgv3mrd stop
5. Stop the cdtserve service with the following command:

# service ndsgv3cdtd stop
6. Stop the v3rap service with the following command:

# service ndsv3rapd stop
7.1.3.1.3 Restarting Services
1. Restart the NDS service with the following command:

# service ndsd restart
2. Restart the DPS services with the following command:

# service ndsdpsd restart
3. Restart the ICE service:

# service ndsiced restart
4. Restart the mrserver service with the following command:

# service ndsgv3mrd restart
5. Restart the cdtserver service with the following command:

# service ndsgv3cdtd restart
6. Restart the v3rap service with the following command:

# service ndsv3rapd restart
7.1.3.1.4 Checking the Service State
1. Check the NDS service status with the following command:

# service ndsd status
2. Check the DPS service status with the following command:

# service ndsdpsd status
3. Check the ICE service status with the following command:

# service ndsiced status
4. Check the mrserver service status with the following command:

# service ndsgv3mrd status
5. Check the cdtserver service status with the following command:

# service ndsgv3cdtd status
6. Check the v3rap service with the following command:

# service ndsv3rapd status
7.1.3.2 Solaris Version
In the Solaris OS, the operations to the NDS service must be performed as the root
user.
7.1.3.2.1 Starting Services
NDS Solaris has six services. After the OS is restarted, all the services of NDS will be
started automatically. If the services are stopped manually, it is necessary to restart the
services. The methods of starting the six services are as listed below:
1. Start the NDS service with the following command:

# svcadm enable NDSService
2. Start the DPS service with the following command:

# svcadm enable NDSDPSService
3. Start the ICE service with the following command:

# svcadm enable NDSICEService
4. Start the mrserver service with the following command:

# svcadm enable NDSMRSERVERService
5. Start the cdtserver service with the following command:
# svcadm enable NDSCDTSERVERService
6. Start the v3rap service with the following command:

# svcadm enable NDSV3RAPService
7.1.3.2.2 Stopping Services
1. Stop the NDS service with the following command:

# svcadm disable NDSService
2. Stop the DPS service with the following command:

# svcadm disable NDSDPSService
3. Stop the ICE services with the following command:

# svcadm disable NDSICEService
4. Stop the mrserver service with the following command:

# svcadm disable NDSMRSERVERService
5. Stop the cdtserve service with the following command:

# svcadm disable NDSCDTSERVERService
6. Stop the v3rap service with the following command:

# svcadm disable NDSV3RAPService
7.1.3.2.3 Restarting Services
To restart a service, stop it first, and then start it. Refer to Sections 7.1.3.2.1 and
7.1.3.2.2 for the operation details of each service.
7.1.3.2.4 Checking the Service State
# svcs | grep NDS
If the services are normal, the following information will be displayed.

7.2 Checking the NE Data on SBCX
For UMTS and GSM V4 (i.e., BSC V6.50 series), the data is downloaded directly from
the SBCX of RNC/BSC. Therefore, if there is no data under the Data directory of NDS,
check first whether there is data on the SBCX.
1. Log in to the SBCX with the FtpInfo data configured in NDS_Config.xml, e.g., the
connection configuration information of UMTS Ftp is as shown in the figure below:
2. Open the local FTP tool (e.g., FileZilla), and fill in the above information. If the
board can be connected, the link between NDS and SBCX is connected.
Otherwise, the link is not connected, and it is necessary to make the link
connected.
3. After the board is connected, open the directory of “DefaultDir" in the above figure.
If there are some folders named by date, as shown in the figure below, it means
DefaultDir is configured correctly. Otherwise, it means DefaultDir is configured
incorrectly, and it is necessary to configure DefaultDir again.
4. Open the folder named by date, in which the MR/CDT files are stored, as shown in
the figure below. If the files of a type do not exist, it means the files of this type are
not generated on the SBCX, and it is possible that the switch of this type is not
enabled on RNC/BSC. Contact the on-site customer service engineer for details.
It should be noted that NDS can only recognize the files with the .gz extension. If there
is a file with the .dat extension, and the file size is “0,” it will be deleted by Logservice
later. If the file size is not “0,” the file will be compressed to a .gz file later and then be
downloaded by NDS. When to delete and compress the file is controlled by Logservice.
7.3 Check File Acquisition State on NDS
The system downloads the dat.gz/.dat data file from RNC/BSCV4/BSCV3 through the
FTP/TCP/UDP protocol. The storage path of the file is defined by the LocalDir in
NDS_Config.xml. The default path is [NDS-GU installation path ]/Data.
Then, save the files in the YYYYMMDD/Area ID/Mode/RNCID or BSCID
Directory Name Functions
The data of complaint subscribers, which is newly added in NDS-

CMData
GUV13.4.
The folder of this date format contains the data downloaded from
20131223 SBCX and the data used by Netmax, including UMTS data and
GSM data.
The storage path of the MRCI file: It is for NetMAX-GU to import

stat
the MRCI file.
rpt The temporary folder used when the MRCI file is generated.
It is the folder of the UMTS VIP data. When NetMax imports VIP
data, the data is acquired from this folder.
Remarks:
If there is the MR/CDT source data under the Data directory, but
no data under the VIPData directory, restart DPS service
(ndsdpsd) to check whether the DPS service is normal.
VIPData If there are data files under the VIPData directory, but no VIP data
on NetMax, check whether NETMAXIP is configured in [NDS-GU
Installation
Path]/Config/DPS_DataCollectOptions.ini. Note:
Restart the DPS service after the modification.
The corresponding log file on NDS is [NDS-GU installation
path]/Log/NDS_MUDataCollect.log. Check whether there is
some error in the file.
upload The folder of the files uploaded from NetMax to NDS.
In the above directories, the directories named by date store the data downloaded from
the boards and the data used by NetMAX, including UMTS data and GSM data. Refer to
the following two sections for details.
7.3.1 UMTS Product
The meaning of each directory:

The storage location of the NetMAX-U interface file, i.e., the root
directory of the data downloaded by NetMax-U. After NDS
decodes the data of different types, it generates the data under
the netmax directory. The type of the data can be viewed in the
netmax file name. If the NetMAX directory is not displayed, it means
NDS does not start decoding and generating the corresponding
file for NexMAX. In this case, check whether NetMax has
imported the engineering parameter file, and whether
NDS_Config.xml is configured correctly.
The raw CDT data downloaded from SBCX. It is not packaged

CDTEXTEMP
and includes VIP users (CDTV) and common users (CR)
Packet the data in CDTEXTEMP. The data packeted can be

CDTEX
decoded by NDS.
CT The source file of the associated log downloaded from the board.
MR The MR source data downloaded from the board.
EMI The EMI source data downloaded from the board.
DPI The DPI source data downloaded from the board.

7.3.2 GSM Product
The following table shows the description of each directory:

The storage location of the NetMAX-GU interface file, i.e., the root
directory of the data downloaded by NetMax-GU. After NDS
netmax decodes the data of different types, it generates the data under
the netmax directory. The type of the data can be viewed in the file
name.
Includes the MR data of common users and VIP users.

For BSC V6.50 series, it is used to store the MR source file
MRTEMP downloaded from the board.
For BSC V6.30 series, it is used to store the MR file copied from
the NDS-GV3RAP/data directory.
For BSC V6.50/V6.30 series, convert the files in folder MRTEMP

to the MR files directly.
MR
For BSCV6.20 series, MRServer directly generates MR file under
the folder.
Includes the CDT data of VIP users (CDTV) and common users
(CR).
For BSC V6.50 series, it is used to store the CDT source file
CDTEXTEMP
downloaded from the board.
For BSC V6.30 series, it is used to store the CT/CR file copied
from the NDS-GV3RAP/data directory.
Packet the files in the CDTEXTEMP folder. The data packeted can
CDTEX
be decoded by NDS.
7.3.3 Factors Affecting File Size
Path of viewing License: select Help > About > License Info on OMM Client.
7.3.4 Checking Data Integrity in the Data Directory
The check method is as detailed below, with the check of UMTS CDT file as the
example:
Check whether the SBCX data exists, e.g.,
/
DailyBuild/ndsdata/UMTSData/20131223/ZTE_CR_UMTS_354_201312231300
00_V3.12.10.08P06_P328c8d35e.dat.gz
Check whether the source data exists, e.g.,
[NDS-GU installation path] /Data /20131223 /021 /UMTS /354

/CDTEXTEMP
/ZTE_CR_UMTS_354_20131223130000_V3.12.10.08P06_P328c8d35e.dat.gz
Check whether the packeted data exists, e.g.,
[NDS-GU installation path] /Data /20131223 /021 /UMTS /354 /CDTEX

/ZTE_CR_UMTS_354_20131223130000_V3.12.10.08P06_P328c8d35e.dat.gz
Check whether there is data generated under the netmax directory, e.g.,

/netmax /ZTE_CR_UMTS_354_20131223130000_V2.00_P328c8d35e.data1
/netmax /ZTE_CR_UMTS_354_20131223130000_V2.00_P328c8d35e.data2
7.4 Checking File Generation on NDS
After the files are processed by NDS, the files generated are stored under the FTP
directory under [NDS-GU installation path] (in the YYYYMMDD/Area ID/Mode/RNCID or
BSCID format), or MR subdirectory (MR data file), or CDT subdirectory(CDT data file),
or NetMAX subdirectory (Data file provided for NetMAX. Default FTP connection
information for NetMAX: IP: NDS IP; Port: 21; UserName: netmax; Pwd: netmax123;
Home=[NDS-GU installation path]/Ftp/). The contents of the FTP directory are used by
the third-party FTP system (northbound interface):
The following table shows the description of each directory:
Directory
Functions Remarks
Name
It is the storage path of the GSM MR The MR statistics file is

statistics file. The operator is defined by generated per hour under
the STATETYPE parameter in the the stat directory of NDS.
stat
mrcfg.ini or the DataManage.ini The CI files generated by
file. The file is generated at the hour can be merged into
beginning of each hour. one file for each day.
BSCV6.20
The storage path of GSM MR and CDT
raw BSCV6.30
raw data
BSCV6.50
GSMVIP Reserved directory
The storage path of UMTS MR

20140102
northbound data
The storage path of UMTS CDT

021
northbound data
7.4.1 Checking GSM BSCV6.20 Series
If one of BSC V6.20 series is used and MR Server and CDTServer are used on NDS to
generate data, the data storage directories are as listed below:
1. Check whether there is MR data under the [NDS-GU installation

path]/Data/date/AreaID/GSM/BSCID/MR directory.
2. Check whether there is CDT data under the [NDS-GU installation

path]/Data/date/AreaID/GSM/BSCID/CDTEX directory.
3. Check whether there is MRCI data under the [NDS-GU installation

path]/Data/stat directory.
If there is the MR/CDT/MRCI data under the above directories, it means the source data
is normal. If there is no data under the above directories, it means MRServer and
CDTServer do not generate data. In this case, it is necessary to check why the two
services are abnormal.
7.4.2 Checking GSM BSCV6.30 and V6.50 Series
If one of GSM BSCV6.30 and V6.50 Series is used, perform the following steps to check
whether the source data is generated:
1. Check whether there is MR/CDT data under the [NDS-GU installation

path]/NDS-GV3RAP/data directory.
2. Check whether local download is configured in the NDS_Config.xml file. It is only

necessary to configure the BSCID in GSMLocalSourceConfig, as shown in the
figure below:
3. After the configuration is modified, be sure to restart NDS service. By this

operation, NDS will copy the files under the [NDS-GU installation
path]/NDS-GV3RAP/data directory to the [NDS-GU installation
path]/Data/Date/Area/GSM/BSCID directory.
If there is no MR/CDT data under the [NDS-GU installation path]/NDS-
GV3RAP/data directory, it means the V3Rap function is abnormal. In this case, perform
troubleshooting according to the corresponding installation guide.
7.4.3 Checking Data Integrity in the FTP Directory
The check method is as detailed below, with the check of UMTS MR file as the example:
Check whether there is data on SBCX, e.g.,

/DailyBuild/ndsdata/UMTSData/20131223/
ZTE_MRU_UMTS_362_20131223113000_V3.11.10.11_P37a67db21.dat.gz
Check whether there is data under the Data directory of NDS, e.g.,
[NDS-GU installation path] /Data /20131223 /021 /UMTS /362 /MR

/ZTE_MRU_UMTS_362_20131223113000_V3.11.10.11_P37a67db21.dat.gz
Check whether there is northbound data under the FTP directory, e.g.,
[NDS-GU installation directory] /FTP /20131223 /362

/ZTE_MRR_UMTS_362_2013-12-23-11-30-00.dat.gz
7.5 Checking Log File
The log file is saved under the Log directory, as shown in the figure below:
The following table shows the description of each log file:
Log Name Description
GSMV3 directory It is used to store the GSMV3 NDS process log.
CDT timing task log: records the execution state

of log file deletion. Modify the date (highlighted in
GSMV3/cdtcron_20140106.log
blue) according to the field configuration.
Normally, only one log file is generated each day.
CDT service process execution log: Modify the

date (highlighted in blue) according to the field
GSMV3/cdtserver.20140106.log
configuration. Normally, only one log file is
generated each day.
MR timing task log: records the execution state of

log file deletion. Modify the time highlighted in blue
GSMV3/mrcron_20140106.log
to the actual time. Normally, only one log file is
generated each day.
MR service process execution log: Modify the date

(highlighted in blue) according to the field
GSMV3/mrserver.20140106.log
configuration. Normally, only one log file is
generated each day.
NDS decoding program execution log: it is for

NDS_CDT_Decoder_GSM*.log GSM CDT data. * is null or debug. The debug log
has more detailed information.

NDS_CDT_Decoder_UMTS*.log UMTS CDT data. * is null or debug. The debug log

NDS_DPI_Decoder_UMTS *.log UMTS DPI data. * is null or debug. The debug log

NDS_EMI_Decoder_UMTS *.log UMTS EMI data. * is null or debug. The debug log

NDS_MR_Decoder_UMTS *.log UMTS MR data. * is null or debug. The debug log

NDS_MR_Decoder_GV3*.log GSMV3 MR data. * is null or debug. The debug
log has more detailed information.
* is null or debug. The debug log has more

NDS_MR_G_LT*.log
detailed information.
7.5.1 Searching Errors in the Log
Check the log files mentioned above in the Log directory to see whether there is some
error. If there is some error that cannot be understood or fixed, describe the symptom
and send related logs to our R&D engineer for analysis.
# cd /[NDS-GU installation path]/Log
# grep error NDS_MR_Decoder_UMTS.log
7.6 Backing up Files Manually
If the downloaded file or the northbound file needs to be kept for a long time, copy it
from the above-mentioned directory.
7.7 Clearing Files Automatically
The system supports auto-deletion of either stale data or the data of the earliest day
according to the disk use rate threshold. By default, the data under the FTP directory is
deleted. Check the log directory to view the data clearing state.
7.8 Daily Inspection
This section introduces the main contents and method of NDS-GU software inspection
in detail.
Inspection steps:
1. Check the hardware of the server to see whether it runs properly and whether
there is some alarm information.
2. Check the security update and anti-virus software update state of the operating
system.
3. Check the operating system log to see whether there is some error information.
4. Check the network environment and whether the network connection with
RNCs/BSCs is normal through Ping and FTP.
5. Check whether the services are registered.
6. Check the operation state of the processes.
7. Check whether FTP service is normal (connect to the FTP service of the current
system from another computer).
8. Check the log file to see whether there is some error information.
9. Check whether the disk space is sufficient.

8 FAQs and Solutions
This chapter introduces some common problems found when NDS-GU software is used
and the solutions.
8.1 User Root Locked to Ftp Home Directory (Linux)
Because three FTP users will be created when NDS is installed, the global parameter
(Linux OS, the “#” before chroot_list_enable=YES in /etc/vsftpd.conf is
deleted) is modified to “YES,” so as to lock a certain user to a certain directory (control
its access permission).
There are two solutions:
(Applicable to Linux OS) Modify /etc/passwd with the vi command, and set the
home directory of user root to /. Log on the system again through Ftp as user root.
(Applicable to Linux OS) Modify /etc/vsftpd.conf with the vi command, add “#” before
chroot_list_enable=YES, and restart the vsftpd service with the service vsftpd
restart command. Then, log on to the system through Ftp as user root.
8.2 NDS Related Processes Are in Abnormal State
If there is some process staying in the Maintenance state or switching repeatedly

between online state and offline state, it means some problem occurred when the
process is started, which may be caused by some mistake in the related configuration
file. In this case, check the modified configuration file carefully.
If the fault cannot be found in the configuration file, check the following process log file.
In the Solaris OS, check the log of the processes under /var/svc/log/ to find the
cause of the fault, as shown in the figure below.
In the Linux OS, check /var/log/messages and other log files.
For example: solaris application-NDS-

NDSCDTSERVERService_NDSCDTSERVERD.log
[ Feb 19 11:13:49 Executing start method ("/lib/svc/method/NDSCDTSERVERD start") ]

uid=0(root) gid=0(root) open cdt.lck error:Permission denied
If the above print appears, it means there is some error in the NDSCDTSERVERD
process. It is possible that other user starts this service and the permission of the
cdt.lck file is modified.
8.3 NDS Cannot Be Installed and the System

Prompts It Already Exists
When NDS is installed, the system prompts it has existed and the installation cannot be
continued.
A possible cause of this problem is that NDS was installed before but was not
uninstalled according to the normal procedure.
Find the original installation version. Execute the following steps (the following method is
valid only for the verification of V13.20 and V13.40 series. In the following description,
V13.20 is taken as the example).
1. Find the installation package of the original installation version.
2. After the installation package is unzipped, unzip the NDS_GU.tar package with
the following command.
gunzip NDS_GU_V13.20.01P02_Release_Solaris.tar.gz
tar -xvf NDS_GU_V13.20.01P02_Release_Solaris.tar
tar -xvf NDS-GU.tar
3. Enter the NDS-GU directory, and execute the NDSUnInstall.sh script.

cd NDS-GU
./NDSUnInstall.sh
8.4 Checking NE Status
If the NE signaling is normal, the NE runs properly.
8.5 SBCX Board Configuration
RNCID/BSCID configuration file: modify the RNCID/BSCID corresponding to the board

in the /home/zte/LogService/bin/conf/LogService.conf configuration file;
otherwise, the RNCID/BSCID in the data file generated by the board may be incorrect.
8.6 Notices in Data Download
If the data fails to be downloaded, check whether there is an extra “/” added before the
DefaultDir in the NDSConfig.xml configuration file.
The data storage path on RNC/BSC SBCX is the relative path of the Home directory of
the Ftp user, e.g., if the default root directory of the ftp user is /home and MR data is
saved under the /home/zte/Data directory on RNC/BSC SBCX, set this
configuration item to zte/Data.
8.7 The RNCID in the File Name Generated on RNC

Is Inconsistent with the RNCID Configured
Due to RNCID modification or board replacement, the RNCID in the MR/CDT data file
name generated on the NEs is inconsistent with the RNCID configured, and
consequently NDS cannot get data from the NEs. In this case, it is necessary to perform
related NE operations to validate the correct RNCID. If RNCID is modified, it is
required that the whole system be rebooted.
If RNCID is inconsistent with what is configured on the NE, there are two solutions:
1. Reboot the master and slave OMPs simultaneously. After both are started up,
reboot the master LogService and then the slave LogService.
2. Modify the RNCID in the memory (this method is risky and is not recommended).
i. Collect the RAPMGT process of the master OMP, and modify the address
according to the IP actually acquired.
[RAPMGT_W_OMP_SBCJ_L_X86_64_64_R_V4.12.10.14P06B00]# g_wRncId
[RAPMGT_W_OMP_SBCJ_L_X86_64_64_R_V4.12.10.14P06B00]0x1ca1df90:
value = 75 = 0x4b = 'K'(32);value = 75=0x4b(64)
[RAPMGT_W_OMP_SBCJ_L_X86_64_64_R_V4.12.10.14P06B00]ushell command
finished
The address acquired is 0x1ca1df90. Modify the low bit to “0,” i.e., 0x1ca1df00.
Input the modified IP as a parameter.
[RAPMGT_W_OMP_SBCJ_L_X86_64_64_R_V4.12.10.14P06B00]#
d(0x1ca1df00,100,4)
ii. Modify “1089” to the RNCID actually used.

[RAPMGT_W_OMP_SBCJ_L_X86_64_64_R_V4.12.10.14P06B00]# g_wRncId =
1089
[RAPMGT_W_OMP_SBCJ_L_X86_64_64_R_V4.12.10.14P06B00]# g_wRncId
[RAPMGT_W_OMP_SBCJ_L_X86_64_64_R_V4.12.10.14P06B00]#
d(0x1ca1df00,100,4)
iii. Stop the Logservice of the slave board, and then reboot the Logservice of the
master board. Reboot the Logservice of the slave board after the master
board is powered on.
iv. Wait for five minutes and check whether the RNCID in the generated MR data
is correct.
8.8 Number of Data-keep Days
When NetMAX-GU is connected, the number of days for keeping the raw data files and
the NetMax data file (i.e., the data files under the [NDS-GU installation
path]/Data/ directory) does not need to be configured on NDS. Instead, it is
configured on NetMAX-GU by the user and then transferred to NDS automatically by
NetMAX-GU, so that the number of data-keep days on NDS is consistent with that on
NetMAX-GU.
When NetMAX-GU is not connected, NDS keeps 15 days of raw data files by default.
The user can modify the [NDS-GU installation
path]/Data/upload/NetMAXKeepDays.ini file and configure the number of days
for keeping raw data files (i.e., the data files under the [NDS-GU installation
path]/Data/ directory). It is not necessary to restart the services after the
modification.
[KeepDays]
# The number of days for keeping CDT data.
CDTData = 15
# The number of days for keeping VIP user data.
VIPData = 30
# The number of days for keeping CM user data.
CMData = 30
The number of days for keeping raw data

CDTData = 15: Keep the
file and NetMax data file, including CDT
data files under the
CDTData data file, MR data file, etc., i.e., the data
Data/date/ directory
files under the [NDS-GU installation
for 15 days.
path]/Data/date/ directory.
The number of days for keeping UMTS VIP VIPData = 30: Keep the
user data files, i.e., the data files under the data files under the
VIPData
[NDS-GU installation /Data/VIPData
path]/Data/VIPData directory. directory for 30 days.
The number of days for keeping UMTS CMData = 30: Keep the
complaint user data files, i.e., the data files data files under the
CMData
under the [NDS-GU installation /Data/CMData directory
path]/Data/CMData directory. for 30 days.
8.9 Packaging Log Files
If there is some problem in the system, it is necessary check the system operation
information. Execute the InfoCollect.sh script under the [NDS-GU
installation path]/Tools installation directory and generate the
InfoCollect20111110.tar.gz file under the [NDS-GU installation
path]/Tools directory. Send the package back.
8.10 System Version Information
The content of NDSVersion in the [NDS-GU installation

path]/Config/NDS_Config.xml file is the system version information.
8.11 Matters for Attention in Multi-Partition
If there is more than one partition on the disk (applicable only when the old server is
reused) and the disk space is insufficient for NDS data generated by NDS installation,
some problem tends to occur because the disk space utilization rate is low when all the
data is placed in the same partition.
Note:
1. This section is applicable to NDS-GU V12.4 and NDS-GU V13.2.
2. For all the above operations, the Data directory of NDS is taken as the example. If
the location of the FTP directory needs to be changed, modify the “Data” in the
above steps to “FTP” and keep other information unchanged.
3. The following screenshot is from Redhat Linux. The commands of service

startup/shutdown in Solaris OS are different from those in Linux OS. Other
commands are almost the same.
Operation Procedure:
Log on to the OS with putty as the root user.
1. Stop the NDS service.

[Solaris] svcadm disable ndsd
[RHEL] service ndsd stop
2. Create the following directory under the new directory where the data is to be
stored.
[Solaris & RHEL] mkdir [new directory]/NDS_Data
3. Modify the authorization of the directory.
[Solaris & RHEL] chmod 777 [new directory]/NDS_Data
4. Modify the user of the directory newly created.

[Solaris & RHEL] chown nds [new directory]/NDS_Data
5. Modify the group of the directory newly created.

[Solaris & RHEL] chgrp nds [new directory]/NDS_Data
6. Switch user.
[Solaris & RHEL] su nds
7. Copy files (including the sub-directory).

[Solaris & RHEL] cp -r [NDS installation path]/Data/* [new dirctory]/NDS_Data/
8. After the files are copied, delete the original directory.

[Solaris & RHEL] rm -r -f [NDS installation path]/Data
9. Create soft connection.

[Solaris & RHEL] ln -s [New path]/NDS_Data [NDS installation path]/Data
10. Switch to the root user.
[Solaris & RHEL] su root
11. Start the NDS service.
[Solaris] svcadm enable ndsd
[RHEL] service ndsd start
8.12 NetMAX-GU Data Import Failure Check Steps
If the MR/CDT/DPI/EMI/MRCI data import fails, perform the following check steps.
1. Check whether NDS link is configured successfully through the NetMAX-GU client,
as shown in the figure below:
2. Check whether the engineering parameters are imported into NetMAX-GU. Only
when these parameters are imported will NDS start decoding. For UMTS, check
whether there are the gsmproject.xls and gsmncellinfo.csv files under
the Data/upload directory on NDS. For GSM, check whether there are the
gsmproject.xls and gsmncellinfo.csv files under the Data/upload
directory. The size of the two files should be above “0.” If these two files do not
exist, it means NetMax does not import the engineering parameters and the radio
parameters.
3. For UMTS, check whether the “stat” switch under NetMAX_UMTSMR is enabled in
the DataManage.ini file on NDS. For GSM, check whether the “stat” switch
under NetMAX_GSMMR is enabled in the DataManage.ini file on NDS. This
switch determines whether NDS outputs the MR interface file (this switch is
available in NDSV13.2 and later versions).
4. If the CT/DPI/EMI is to be outputted, it is also necessary to check whether the

switch is enabled.
If the UMTS VIPData data import fails, perform the following check steps.
VIPData is generated under the [NDS-GU installation path]/Data/VIPData

directory. For versions prior to RNCV3.11, check the [NDS-GU installation
path]/Config/DPS_DataCollectOptions.ini file to see whether NetMAXIP is
configured. Restart the DPS service after the configuration is modified.

GU - ST - ZTE UniPOS NDS-GU V13.40 Installation Configuration Acceptance Guide - R1.3

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

GU - ST - ZTE UniPOS NDS-GU V13.40 Installation Configuration Acceptance Guide - R1.3

Enviado por

Direitos autorais:

Formatos disponíveis

Operator Logo

ZTE UniPOS NDS-GU V13.40

ZTE Confidential & Proprietary. © ZTE CORPORATION. All rights reserved.

Date Document Version Prepared by Reviewed by Approved by

Intended audience: GU product after-sales engineers

ZTE Confidential & Proprietary. © ZTE CORPORATION. All rights reserved.

About This Document

ZTE Confidential & Proprietary. © ZTE CORPORATION. All rights reserved.

2 Terms, Definitions, and Abbreviations...........................................................2

5 NDS Server Installation and Uninstall............................................................9

ZTE Confidential & Proprietary. © ZTE CORPORATION. All rights reserved.

5.6.1 Executing the Uninstall Script..........................................................................25

6 NDS Service Configuration...........................................................................26

7 System Acceptance and Maintenance.........................................................68

ZTE Confidential & Proprietary. © ZTE CORPORATION. All rights reserved.

7.4.2 Checking GSM BSCV6.30 and V6.50 Series...................................................83

8 FAQs and Solutions.......................................................................................88

ZTE Confidential & Proprietary. © ZTE CORPORATION. All rights reserved.

Modern mobile communications technology is a very complex system. Due to the

2.1 Terms and Definitions

Abbreviation Full Name

NetMAX brand of ZTE’s new intelligent optimization tool

NDS Network Data Service

CDT Call Detail Trace

DPS Data Process System/Service

EMI Evaluation MOS Index

3.1 Principle of NDS

MR function: UR can report intra-frequency measurement, inter-frequency

The MR function supports MR data collection, storage, and output.

1. MR-UE coverage measurement.

i. Handover measurement due to event: UE intra-frequency/inter-

ii. Traffic measurement due to event: UE traffic measurement result

iii. Internal event measurement: UE TX power measurement result

iv. Periodical handover measurement: UE intra-frequency measurement result

v. Internal periodical measurement: UE TX power measurement result

vi. Periodical quality measurement: UE DL DCH BLER measurement result,

2. MR-UE location measurement: Select one of the following modes.

i. CELL-ID+RTT mode: Periodical Node B RTT measurement, periodical UE

CDT (Call Detail Trace) function: It is an important feature of ZTE’s telecommunications

Currently, the information reported by CDT includes mainly the following:

2. UE capability: includes UE radio access capability, PDCP capability, and physical

4. UE key message info

 User-plane information: records the user-plane physical board resource related

3.4 Principles of DPS

It is a specific function of UMTS. Versions supported by DPI:

3.5 Principles of EMI

It is a specific function of UMTS. The versions supported by EMI include V4.11.20.06/

UMTS CS service perception assessment is mainly to assess the CS user experience

4.1 BSC and RNC Versions Supported

4.2 NetMax Versions Supported

5.1 Requirements for NDS Server

1. Deployment of NDS on SBCJ/SBCX is not supported.

2. Red Hat Enterprise Linux V6.4 is not supported.

3. Solaris10 u8 does not support RNCV4.11.20.06.

CPU: 2 Xeon E5-2630 2.3G

CPU: 4 Xeon E5-2630 2.3G

CPU: 4 Xeon E7-4850 2.3G

5.2 Preparations Before Installation

5.2.1 Checking Operating System (OS)

Operating System Version:

Default user name/password: root/netmax

IP and masks of the ports on the adapter:

Static route configuration: