GU - TS3051 - E01 - 0 ZXUR 9000 UMTS Troubleshooting 90P

ZXUR 9000 GU
Dual Mode Controller

Troubleshooting Guide
Version: V1.01.00
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2012 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 2012-07-12 First edition

Contents
About This Manual ......................................................................................... I
Chapter 1 Safety Instruction...................................................................... 1-1
1.1 Prerequisites for Maintenance Personnel ............................................................. 1-1
1.2 Safety Symbols .................................................................................................. 1-1
1.3 Safety Specifications .......................................................................................... 1-3
Chapter 2 Overview .................................................................................... 2-1

2.1 Trouble Shooting Flow ........................................................................................ 2-1
2.1.1 Information Collection ............................................................................... 2-2
2.1.2 Fault Analysis .......................................................................................... 2-3
2.1.3 Fault Location .......................................................................................... 2-3
2.1.4 Fault Elimination ...................................................................................... 2-3
2.1.5 Fault Record ............................................................................................ 2-3
2.1.6 Experience Sharing .................................................................................. 2-3
2.2 Trouble Shooting Principles ................................................................................ 2-4
2.3 Common Methods to Locate Faults ..................................................................... 2-4
2.3.1 Analysis of Alarm Information.................................................................... 2-4
2.3.2 Analysis of Status Indicator ....................................................................... 2-4
2.3.3 Analysis of Performance ........................................................................... 2-5
2.3.4 Analysis of Signaling Tracing .................................................................... 2-5
2.3.5 Operation Log Query ................................................................................ 2-5
2.3.6 Analysis with Instruments and Meters ........................................................ 2-5
2.3.7 Testing and Self-Looping .......................................................................... 2-5
2.3.8 Plugging/Unplugging and Pressing ............................................................ 2-6
2.3.9 Configuration Analysis and Modification..................................................... 2-6
2.3.10 Comparison and Replacement ................................................................ 2-7
2.4 Contact Information of ZTE Technical Support...................................................... 2-7
Chapter 3 Troubleshooting for Operation and Maintenance

problems ................................................................................................. 3-1
3.1 Improper Display on Client Interface .................................................................... 3-1
3.2 Abnormal Start of NM Server .............................................................................. 3-2
3.3 Start Failure of NM Server FTP ........................................................................... 3-2
3.4 Inconsistent Configuration Data in NE and NMS................................................... 3-3
I
3.5 Inconsistent Status Data in Network Element (NE) and Network Management
System (NMS).................................................................................................. 3-4
3.6 Different Alarm Time in NE and NMS ................................................................... 3-4
3.7 Improper Server IP Binding ................................................................................. 3-5
Chapter 4 Troubleshooting for Hardware Problems ............................... 4-1

4.1 Introduction........................................................................................................ 4-1
4.1.1 Clock Fault .............................................................................................. 4-1
4.1.2 Communication Link Fault......................................................................... 4-2
4.1.3 Shelf Management Fault........................................................................... 4-3
4.2 Typical Cases .................................................................................................... 4-4
4.2.1 OMP Version File Fault ............................................................................. 4-4
4.2.2 Slave Shelf Startup Failure ....................................................................... 4-4
4.2.3 H/S Blue Light ON for All Boards ............................................................... 4-5
4.2.4 H/S Blue Light ON for a Slot...................................................................... 4-5
4.2.5 Fan Noise/Fan Indicators Off..................................................................... 4-6
4.2.6 OK Red Light ON for Fan Unit ................................................................... 4-6
4.2.7 Optical Fiber Communication Fault............................................................ 4-7
4.2.8 EGFS Unable to Lock Clock Reference from Optical Port ........................... 4-7
4.2.9 Slip Code on Communication Link at Base Station Connected with Dual
Mode Controller Through E1 Cable .......................................................... 4-8
Chapter 5 Troubleshooting for Software Initiation Problems ................ 5-1

5.1 Introduction........................................................................................................ 5-1
5.1.1 Background Information............................................................................ 5-1
5.1.2 Symptom ................................................................................................. 5-1
5.1.3 Troubleshooting Procedure ....................................................................... 5-2
5.1.4 Fault Handling Steps ................................................................................ 5-2
5.2 Typical Cases .................................................................................................... 5-3
5.2.1 FTP Failure Given During Version Operation.............................................. 5-3
Chapter 6 Troubleshooting for System Communication Problems....... 6-1

6.1 Communication Error at Interface A ..................................................................... 6-1
6.1.1 Introduction.............................................................................................. 6-1
6.1.2 Typical Cases .......................................................................................... 6-4
6.2 Communication Error at Interface Gb................................................................. 6-10
6.2.1 Introduction............................................................................................ 6-10
6.2.2 Typical Cases .........................................................................................6-11
6.3 Communication Error at Interface Abis............................................................... 6-13
6.3.1 Introduction............................................................................................ 6-13
II
6.3.2 Typical Cases ........................................................................................ 6-14
6.4 Communication Error at Interface IU/IUR ........................................................... 6-15
6.4.1 Overview of Communication Fault at IU/IUR Interface............................... 6-15
6.4.2 Typical Communication Faults at IU/IUR Interface .................................... 6-18
6.5 Communication Faults at IUB Interface .............................................................. 6-23
6.5.1 Overview of Communication Faults at Iub Interface .................................. 6-23
6.5.2 Typical Communication Faults at IUB Interface......................................... 6-25
6.6 NM Alarms....................................................................................................... 6-27
6.6.1 Signaling Point Unreachable Alarm ......................................................... 6-27
6.6.2 SCCP Subsystem Unavailable ................................................................ 6-27
6.6.3 Association Establishment Failed ............................................................ 6-28
6.6.4 Association Link Broken Alarm ................................................................ 6-28
6.6.5 Association Congestion Alarm................................................................. 6-29
6.6.6 M3UA Office Not Reachable ................................................................... 6-29
Appendix A Troubleshooting Record Table............................................ A-1

Appendix B Board and Component Replacement ................................. B-1
B.1 Overview to Board and Part Replacement ........................................................... B-1
B.2 Replacing Board ................................................................................................ B-1
B.3 Replacing Components ...................................................................................... B-2
B.4 Replacing Fan Unit ............................................................................................ B-3
B.5 Replacing Optical Model..................................................................................... B-4
B.6 M/S Switchover.................................................................................................. B-4
B.7 Resetting Board ................................................................................................. B-4
Appendix C Running Information Description ....................................... C-1

C.1 Introduction .......................................................................................................C-1
C.2 Indicator............................................................................................................C-1
C.2.1 Types of Indicators on Board Panel...........................................................C-1
C.2.2 Common Indicator Statuses .....................................................................C-1
C.2.3 Common Indicators..................................................................................C-2
C.2.4 Board Power ON .....................................................................................C-6
C.2.5 Hardware Reset ......................................................................................C-6
Figures............................................................................................................. I
Tables ............................................................................................................ III
Glossary .........................................................................................................V
III
IV
About This Manual
Purpose
This manual introduces common troubleshooting methods and typical cases concerning
ZXUR 9000 GU.
Intended Audience
l Maintenance engineer
l System Engineer
What Is in This Manual

This manual contains the following chapters.
Chapter Description
Chapter 1, Safety Introduces the safety issues during the ZXUR 9000 GU
Instructions troubleshooting.
Chapter 2, Overview Introduces the ZXUR 9000 GU troubleshooting procedure.
Chapter 3, Troubleshooting Introduces the troubleshooting methods and typical cases concerning
for Operation and operation and maintenance problems of ZXUR 9000 GU.
Maintenance problems
for Hardware Problems hardware problems of ZXUR 9000 GU.
for Software Initiation software loading problems of ZXUR 9000 GU.
Problems
for System Communication system communication problems of ZXUR 9000 GU.
Problems
Appendix A, Troubleshooting Introduces the Troubleshooting Record Table.

Record Table
Appendix B, Board and Introduces the operations of component replacement and impact on
Component Replacement services for ZXUR 9000 GU.
Appendix C, Running Introduces the indicators for ZXUR 9000 GU.

Information Description
I
II
Chapter 1
Safety Instruction
Table of Contents
Prerequisites for Maintenance Personnel ...................................................................1-1
Safety Symbols ..........................................................................................................1-1
Safety Specifications ..................................................................................................1-3
1.1 Prerequisites for Maintenance Personnel

1. Knowledge
l Familiar with GSM/WCDMA theory and relative professional communication
knowledge.
l Familiar with the related signaling protocols, such as, broadband/narrowband No.
7 signaling.
l Familiar with the related communication protocol, such as, TDM, ATMTCP/IP.
l Familiar with the product knowledge, such as basic structure, calling flow, and
service flow.
2. System networking and operation environment
l Thorough understanding of networking of ZTE products
l Understanding of hardware structure of Dual Mode Controller system
l Understanding of performance parameters of Dual Mode Controller system
l Understanding of the operation and data configuration rules of ZXUR 9000 GU
Network Management System
l Understanding of network hierarchy of transmission equipments
3. Equipment operation
l Familiar with the basic operations of PC
l Familiar with the routine operations of ZXUR 9000 GU Network Management
System
l Knowing what operations may cause the interruption of some or all services
l Knowing what operations may cause the damages to the equipment
l Familiar with the emergent and backup measures
4. Using the meters and instruments
Quick fault location ability using test cell phone and signaling analyzer.
1.2 Safety Symbols

Table 1-1 lists the safety symbols.
1-1
SJ-20101108155417-007|2011-08-17(R1.0) ZTE Proprietary and Confidential

ZXUR 9000 GU Troubleshooting Guide
Table 1-1 Safety Symbols Description
Safety Symbol Meaning
Universal alerting symbol: General safety

attentions.
Electrostatic: Device may be sensitive to static

electricity.
Electric shock: There is a risk of electric shock.
High temperature: Surface is hot and may cause

personal injury if touched.
Laser: Beware of strong laser beam.
Microwave: Beware of strong electromagnetic

field.
Among these safety symbols, the universal alarm symbols are classified into four levels:
danger, warning, caution, and note. The meanings of the four levels are described as
below:
Danger!
Indicates an imminently hazardous situation, which, if not avoided, could result in death or
serious injury. Limit its use to only extreme situations.
Warning!
Indicates a hazardous situation, which, if not avoided, could result in serious injuries,
equipment damages or interruption of major services.
Caution!
Indicates a potentially hazardous situation, which, if not avoided, could result in moderate
injuries, equipment damages or partial service interruption.
1-2

Chapter 1 Safety Instruction
Note:
Indicates helpful information which if ignored, could result in minor injuries, equipment
damages or partial service interruption.
1.3 Safety Specifications

Electrical Safety
Danger!
Never install or uninstall power cables while they are live because when touched with a
conductor may produce sparks, resulting in fire or damage to eyes.
Do shut off power supply before connecting or disconnecting a power cable.

Before connecting a cable, make sure that the cable and its label meet the actual
installation requirements.
Warning!
It is not allowed to drill cabinet holes without permission. Unqualified drilling could damage
wiring inside the cabinet. Additionally, the metal pieces inside the cabinet created by drilling
could result in a shorted circuit board.
Antistatic
Caution!
Static electricity produced by human body can damage static-sensitive components on
circuit board, such as large-scale integrated circuits (IC).
Friction caused by human body activities is the root cause of electrostatic charge
accumulation. Static voltage carried by a human body in a dry environment can be up
to 30 kV, and can remain in there for a long time. An operator with static electricity
may discharge electricity through a component when he/she touches the conductor and
causing damage.
1-3

Wear an antistatic wrist strap (the other end of wrist strap must be well grounded) before
touching the equipment or holding a plug-in board, circuit board, Integrated Circuit (IC) chip
or other devices, to prevent human static electricity from damaging sensitive components.
Laser
Warning!
Avoid looking straight at the laser beam from the outlet of the optical transceiver or inside
the optical fiber to avoid eye damage.
High Temperature
Danger!
Avoid touching the surface area of some devices due to high temperature to avoid a scald
injury.
Fans
Warning!
Do not put fingers or any tools into the running fan to avoid an injury. Keep tools away
from the running fan.
Put parts, screws, and tools away from the fan when replacing related parts, to avoid
damage to the fan or related devices.
Keep fingers and board away from the fan when replacing devices around the fan, to avoid
damage to the equipment or fingers.
Hoisting Heavy Objects
Warning!
Do not walk or stay under the hoisted objects during hoisting operations.
1-4

Chapter 1 Safety Instruction
l Ensure a proper hoisting capability of the hoister when disassembling heavy

equipment moving, and replacing equipment.
l The operator must receive the training and qualification for hoisting operations.
Inspect and complete the hoisting tools before getting into service.
l Make sure to fix the hoisting tools firmly on a sufficiently secured object or wall before
the hoisting operation.
l Use brief oral instructions during the hoisting operations to prevent mistaken
operation.
Plugging/Unplugging Modules
The modules mentioned in this document include front board, rear board, and fan module.
Caution!
l Wear antistatic wrist strap.
l Align the module with the guide rail and push it gently to the backplane.
l Plug the module properly into the slot to prevent short circuit due to contact between
the module and the circuit surface.
l Avoid touching the circuits, components, connectors, and cable troughs when holding
a module.
l RF module turns hot when running. Avoid being scalded when plugging and
unplugging an RF module.
Personnel
Caution!
Do not conduct internal maintenance or equipment debugging without prior permission.
Replacing parts or changing equipment may incur extra danger, therefore, do not replace
parts or change the equipment without prior permission. To ensure safety, please contact
ZTE in case of any problem.
1-5

This page intentionally left blank.
1-6

Chapter 2
Overview
Table of Contents
Trouble Shooting Flow................................................................................................2-1
Trouble Shooting Principles........................................................................................2-4
Common Methods to Locate Faults ............................................................................2-4
Contact Information of ZTE Technical Support............................................................2-7
2.1 Trouble Shooting Flow

Generally, the trouble shooting flow consists of six steps: Information collection, fault
analysis, fault location, fault elimination, fault recording and experience sharing.
The typical trouble shooting flow is shown in Figure 2-1.
2-1

Figure 2-1 TROUBLE SHOOTING FLOW
2.1.1 Information Collection

Obtaining the fault information is the first step in trouble shooting. You can get the fault
information through the following methods:
l Fault complaints from user or customer centre

l Traffic statistic index analysis
l Alarm output of alarm system
l Abnormality discovered in routine maintenance of patrol inspection
For the maintenance personnel, it is recommended to fill in Trouble Shooting Record Tables
to note down the fault phenomena for those confirmed faults in time.
2-2

Chapter 2 Overview
2.1.2 Fault Analysis

When a fault occurs, maintenance personnel should analyze the fault based on fault
symptoms first.
In this manual, common faults fall into the following types:
l OMC fault
l Hardware fault
l Software loading fault
l System communication fault
The maintenance personnel can analyze fault causes according to fault symptoms.
2.1.3 Fault Location

Fault location is the process to find out the problem cause from all possible causes. The
maintenance personnel can exclude the incorrect caused and confirm the exact one.
The correct fault location requires experiences and knowledge.
2.1.4 Fault Elimination

Fault elimination is the process to get rid of the fault and restore the proper running of
the system with certain measures or steps, for example, line check, board replacement,
configuration data modification, system switchover, and board reset. During the
troubleshooting, strictly follow the measures and steps specified in the operation manual
or maintenance manual. It must be carried out with care in case other system faults are
brought up.
2.1.5 Fault Record

The maintenance personnel should record when and where a fault occurs, who does the
troubleshooting, what symptoms the fault shows, and what measures are taken to get rid
of the fault. Good fault records can help the maintenance personnel gain troubleshooting
experience and shorten the time to locate and clear a fault, and help equipment suppliers
improve product and service quality.
Refer to Appendix A, Trouble Shooting Record Table, for the template of fault record.
2.1.6 Experience Sharing

After eliminating the faults and making the fault record, the maintenance personnel
should share the debugging experience to enhance the skills. To improve the after-sales
service and product performance optimization, the fault record should also be sent to
ZTE CORPORATION with email or fax in time. These fault records will enrich the fault
maintenance instances, and help to find methods to improve product quality and stability.
2-3

2.2 Trouble Shooting Principles

When dealing with system faults, follow the troubleshooting flow and comply with the
principle of Check > Query > Consider > Work.
Check
First check the system. Find out in which component the fault occurs, what type of alarms
are given, what the grade of the alarm is, what the damage is.
To get the information about a fault, you can use the tools that the system provides, such as,
performance statistics, signaling tracing, alarm query, log query, and service observation.
Query
Query the on-site personnel about the fault causes. Question them about the data
change, file deletion, circuit board replacement, power failure, lightening strike or improper
operations.
Consider
According to the fault alarms and the information from the query, determine the cause.
Work
Locate the fault. Eliminate the fault by modifying the data or replacing the circuit boards.
The operation on the equipment must not be conducted in rush time, which will cause
serious problems. For details, contact the technical engineers in ZTE.
2.3 Common Methods to Locate Faults

2.3.1 Analysis of Alarm Information
Alarm information is the output from NM alarm system. The maintenance personnel can
identify the alarms by audio, light, and output on the screen. The alarm information should
be brief and clear, involving the hardware, link, trunk, and CPU load. The alarm information
is the important basis for the fault analysis and location.
Alarm information that OMCR generates helps to find out the precise location or cause of
the system fault.
If several alarms are given, the alarms with higher severity should be handled first and the
event alarm is treated with the lowest priority.
2.3.2 Analysis of Status Indicator

The analysis of the indicator status is a common method used by the maintenance
personnel when a fault is happens. The indicator status on each board panel in the rack
is observed for fault finding and troubleshooting.
2-4

Chapter 2 Overview
This method requires maintenance personnel to be familiar with the status and
corresponding meaning for indicators on each board.
2.3.3 Analysis of Performance

Performance analysis is conducted through the performance management interface of
NetNumen U31.
Tools are provided to measure the traffic performance and KPIs of the system. Frequently
used along with signaling tracing, the performance measurement tools plays an important
role in finding inter-office signaling interaction failures and incorrect transmission
parameter settings.
The performance management interface helps to create performance measurement tasks,
obtain performance reports, and view the performance indices of the system. By analyzing
the information, maintenance personnel assess the load allocation in the network and
adjust parameters in time to improve network performance.
2.3.4 Analysis of Signaling Tracing

Signaling tracing helps to analyze the user calling and interoffice signaling.
ZXUR 9000 GU provides multiple methods to trace signaling.
2.3.5 Operation Log Query

Operation log query is a method to detect errors in complicated Dual Mode Controller data
configurations and the faults caused by negligence.
ZXUR 9000 GU provides the log query function. The logs contain all the operation records.
2.3.6 Analysis with Instruments and Meters

During the maintenance, the personnel can analyze, locate, and eliminate the faults with
auxiliary instruments, such as, test MS, signaling analyzer and BER analyzer.
2.3.7 Testing and Self-Looping

1. Test
Testing is to measure the technical parameters of user lines, transmission channels,
and trunk devices by using instruments, meters, and software measurement tools. The
measurement results can help users judge whether such lines, channels, or devices
are faulty or almost faulty.
2. Self-looping
Self-looping is to perform a self-transceiving test to a piece of transmission equipment
or transmission channel through hardware or software. By checking whether
the transmission equipment, transmission channel, service status, and signaling
2-5

interaction are normal after the self-looping, users can know whether the hardware
equipment status and software parameter settings are normal. Self-looping is
commonly used to check whether transmission and trunk parameters are set correctly.
Testing and self-looping are often used together. Self-looping falls into software
self-looping and hardware self-looping. Software self-looping is easy and flexible to use,
but is less reliable than hardware self-looping. Moreover, in new site commissioning and
trunk capacity expansion, the trunk self-looping is often used to check whether the trunk
parameters in the local office and the outgoing routing data is set correctly.
Caution!
Software self-looping should be stopped as soon as the troubleshooting completes. To
avoid forgetting this, maintenance personnel should always keep maintenance records.
2.3.8 Plugging/Unplugging and Pressing

If the fault exist in a board, loosen the fixation screws on the front panel of the board
and plug/unplug the board and external interface connectors. This method removes faults
caused by poor contacts or processor faults.
Pressing the cable connectors after power-off helps in eliminating the fault due to insecure
contact.
To plugging/unplugging a board, turn on the ENUM switch. If the rack is with electricity, do
not power off until the H/S indicator flashes three times.
When plugging/unplugging a board, strictly comply with the operation rules. Otherwise, it
may cause the damages on the board or other problems.
2.3.9 Configuration Analysis and Modification

The configured data determines the working and cooperation mode of the system. Usually,
the data cannot be modified.
Some special cases, such as, the surrounding change or the mis-operation, may cause
the damages or changes on the configuration data, or service interruption.
If the fault happens in the local system, locate it by querying or analyzing the current
configuration data. For the mis-operation on NM, locate the fault by viewing the user
operation log.
The configurations that can be modified include the time slot, slot, board parameter, and
protocol type. Therefore, the configuration modification can eliminate the fault caused by
the improper configuration after the fault is located to a site.
For example, the signaling link of a certain office is abnormal and it affects the signaling
transmitted on this link, and thus the correlated services are impacted. Modify the following
configurations:
2-6

Chapter 2 Overview
1. Modify the signaling route. The new route does not use the signaling link to this office.
If the alarm disappears, the fault happens on the previous route.
2. Modifying the signaling link group. The new link group does not use the signaling link
to this office. If the fault disappears, the fault is happens in the previous link group.
During the update and expansion, if the new configuration is doubted faulty, restore the
previous configuration to test whether the fault is related to the new configuration.
When you cannot decide which board is faulty by modifying the time slot, replace each
board for testing until the exact location of the fault is found.
Doing modifications on configuration data needs high skill requirement for maintenance
personnel. Just experienced personnel can try this method.
2.3.10 Comparison and Replacement

Comparison: A possible faulty board can be compared with a normal board with similar
functions in the system (for example, a board in the same slot in a multi-module system)
in running status, jumpers and connection cables.
Replacement: A possible faulty board can be replaced with a spare board or another
normally-running board of the same type to detect the fault location.
With comparison or replacement method, the plug/unplug of a board should comply to the
certain rules described in this manual.
2.4 Contact Information of ZTE Technical Support

l Hotline
à ZTE Customer Support Center Hotline: 800-830-1118
à ZTE Customer Support Center International Hotline: +86–755–26771900
à Fax: (0755)26770801
à International Fax: +86–755–26770801
Please provide the on-site abnormality record table.
l Remote Support
The technical support engineers can remote log on the problematic office to help users
solve the problem.
l On-site technical Support
The maintenance engineers can solve the problem on-site.
2-7

2-8

Chapter 3
Troubleshooting for
Operation and Maintenance
problems
Table of Contents
Improper Display on Client Interface...........................................................................3-1
Abnormal Start of NM Server......................................................................................3-2
Start Failure of NM Server FTP ..................................................................................3-2
Inconsistent Configuration Data in NE and NMS.........................................................3-3
Inconsistent Status Data in Network Element (NE) and Network Management
System (NMS)............................................................................................................3-4
Different Alarm Time in NE and NMS..........................................................................3-4
Improper Server IP Binding ........................................................................................3-5
3.1 Improper Display on Client Interface

Phenomena
The client operation interface is not fully displayed, and the pop-up window or dialogue
box oversteps the display area on screen.
Cause
The display resolutions for the NM client interface is designed to be 1024 * 768 pixel.
Therefore, if the display resolutions is set as 800 * 600 pixel, the pop-up windows on the
NM interface oversteps the display area of screen.
Troubleshooting
Right-click the desktop of the client side and select Property. The Property dialogue box
pops up. Select Setting tab and set the display resolution for the screen area as 1024 *
768 pixel.
Cautions
None
3-1

3.2 Abnormal Start of NM Server

Phenomena
The NM Server starts as abnormally and the Client cannot connect to the NM Server.
Cause
Oracle database connection may not be proper, or the properties file is not configured
correctly.
Troubleshooting
1. Check whether the connected database is initiated.
2. Check whether Oracle Client connection is created. Run Oracle Enterprise Console
and check whether the SID_*.*.*.* connection is established.
3. In ums-svr/deploy/deploy-*.properties file under NM server installation directory, check
whether the configuration of the database connection is correct.
Cautions
None
3.3 Start Failure of NM Server FTP

Phenomena
NM Server starts abnormally and the startup of FTP fails.
Cause
The port required for FTP startup is occupied by third party FTP software.
Troubleshooting
1. Check all started processes to see whether any process occupies the FTP port. If so,
close the process and restart the server.
2. Check all services of the operation system to see whether any services occupies FTP
port. If so, close the services and restart the server.
Cautions
None
3-2

Chapter 3 Troubleshooting for Operation and Maintenance problems
3.4 Inconsistent Configuration Data in NE and NMS

Phenomena
The configuration data displayed at NM Client is inconsistent with that on NE.
Cause
The configuration data modified in NMS is not synchronized to NE in time.
Troubleshooting
Perform all—tables synchronization to synchronize the NM configuration data to NE.
Perform the following steps:
1. Confirm the correctness of NM configuration data.

2. On the configuration resource tree, select a network element. . Right-click it and select
Data Synchronization > All Table Synchronization, as shown in Figure 3-1.
Figure 3-1 All Table Synchronization
Note:
Incremental synchronization also works.
3-3

Cautions
None
3.5 Inconsistent Status Data in Network Element (NE)

and Network Management System (NMS)
Phenomena
The board status on the rack diagram displayed at NM Client is inconsistent with the actual
status.
Cause
The status data of the NE and NMS is inconsistent.
Troubleshooting
Perform status synchronization operation to synchronize status data between NE and
NMS.
Perform the following steps:
On the NMS interface, reopen the status page or refresh the status.
Cautions
None
3.6 Different Alarm Time in NE and NMS

Phenomena
The alarming time displayed on Client interface is different from the actual time when the
NE gives alarm.
Cause
Inconsistent clocks in NE and NMS
Troubleshooting
Perform the following steps to synchronize the clocks:
1. Log in to the NM client.
2. On the configuration resource tree, select Subnetwork > NE > Config Set > Ground
Resource Management.
3. Select Ground Resource Management > SNTP and System Log Configuration,
as shown in Figure 3-2.
3-4

Chapter 3 Troubleshooting for Operation and Maintenance problems
Figure 3-2 SNTP and System Log Configuration
The IP address of SNTP server should be OMM subnetwork IP that can be ping
through OMP. The SNTP networking mode should be OMM Server Access The
source of time synchronization should be obtained from NTP server. The Using
Configuration Synchronization Mode of 3G option should be set Yes.
4. Perform All Table Synchronization or Incremental Synchronization.
5. On the toolbar of NM status management interface, click . On then pop-up dialog
box, click NTP Clock Synchronization.
Cautions
None
3.7 Improper Server IP Binding

Phenomena
In the split OMM environment of Dual Mode Controller and Base Station, system fault
appears when two NM server starts simultaneously. If one of them is initiated, the server
will be working properly.
Cause
After OMM split, the NM server will bind the configured IP. If the two servers are configured
with the same binding IP, the second server started cannot use the IP already occupied by
the previously started server.
Troubleshooting
1. Check /etc/hosts, which contains the master IP for the two servers.
3-5

2. Check ums-svr/deploy/deploy-999split.properties to see whether it

contains the correct information of the binding IP. The infomation of Dual Mode
Controller OMM is as follows:
ums.systemproperty.com.zte.ums.uep.localaddress=eth4
ums.systemproperty.com.zte.ums.bind.socket.client.ip=eth6:1
ums.services.bind.multi.local.addresses =eth6,eth6:1,128.0.30.1,128.0.30.9
The information of Base Station OMM is as follows:

ums.systemproperty.com.zte.ums.uep.localaddress=eth4:1
ums.systemproperty.com.zte.ums.bind.socket.client.ip=eth6:2
ums.services.bind.multi.local.addresses = eth6:2,128.0.30.1,128.0.30.9
Cautions
None
3-6

Chapter 4
Troubleshooting for
Hardware Problems
Table of Contents
Introduction ................................................................................................................4-1
Typical Cases.............................................................................................................4-4
4.1 Introduction
Based on different hardware components, hardware faults are classified into three types:
l Clock fault
l Communication Link fault
l Shelf Management Fault
The following describes the system faults mentioned above.
4.1.1 Clock Fault

4.1.1.1 Background Information
Generation and distribution of Synchronization Clock is completed by EGFS and
relevant backplane and service boards. EGFS implements the clock reference input and
distribution. It supports the cable, BITS standards and GPS function.
The clock reference for the system with EGFS includes BITS (2 Mbps/2 MHz) line clock
extraction (2 MHz) and that obtained from the external GPS antenna.
During operation, EGFS selects clock reference source based on defined priority to
generate required 25 M, 8 K, PP2S clocks, and distribute the clock to master-shelf boards
and the Clock board on the slave shelf.
4.1.1.2 Phenomena and Cause

The common phenomena and causes of clock fault are shown in Table 4-1.
Table 4-1 COMMON PHENOMENA AND CAUSE OF CLOCK FAULT
Phenomena Cause
K/F indicator, 1 Hz flash Clock source not configured or invalid
K/F indicator, constantly on Current clock source lost
4-1

Phenomena Cause
GPS indicator, 0.5 Hz flash GPS initialization failed
GPS indicator, 1 Hz flash GPS in satellite searching status or unknown

status
GPS indicator, 2 Hz flash Antenna and feeder short-circuited.
GPS indicator, 5 Hz flash Antenna and feeder broken
GPS indicaor, Off Master shelf: GPS in unknown status;

Slave shelf: GPS not in use
4.1.2 Communication Link Fault

Except for voice and data link exchange, ZXUR 9000 GU carries out a large amount of
internal and external signaling interaction. The signals are sent to corresponding units via
different links. Therefore, the telecommunication links fall into two types: external links
and internal links.
The internal link means the communication links among the inner modules of Dual Mode
Controller. The external link means the communication links of Dual Mode Controller and
other external equipment, including each interface. These interfaces are described as
follows:
l A Interface: is between BSC and CN in GSM mode, and performs CN-BSC signaling
interaction and data transmission.
l Gb interface: is between BSC and SGSN in GSM mode, and performs the data
transmission in the PS domain.
l Abis interface: is between BSC and the base station in GSM mode, and performs the
signaling interaction and data transmission between BSC and the base station.
l Ater interface: is between BSC and TC in GSM mode when TC is separated from
BSC and installed externally.
l Iu: is between RNC and CN in UMTS mode, including the Iu-CS and Iu-PS
interfaces. The Iu interface is in charge of the RNC-CN signaling interaction and data
transmission.
l Iub: is between RNC and the base station in UMTS mode. The Iub interface is in
charge of the signaling interaction and data transmission between RNC and the base
station.
l Iur: is between two RNCs in UMTS mode. The Iur interface is in charge of the
RNC-RNC signaling interaction and data transmission.
l Iur-g: is between RNC (UMTS mode) and BSC (GSM mode). The Iur-g interface
is in charge of the signaling interaction and data transmission between two mode
controllers in UMTS mode or the GSM mode.
4-2

Chapter 4 Troubleshooting for Hardware Problems
4.1.2.2 Symptom and Cause

The common symptoms and causes of link fault are shown in Table 4-2.
Table 4-2 COMMON SYMPTOM AND CAUSE OF COMMUNICATION LINK FAULT
Symptom Cause
E1 link fault Check the configurations of the network manage-

ment system..
Check the cable link. Make a self-loop transceiv-

ing on the E1 cables and check whether the alarm
disappears.
E1 link slip code Check the EDTT/EDTI/EDTA board.
Check the clock reference source for the EGFS

board.
Check lock phase for the EGFS board.
Optical link fault Check the optical fiber transceiving link. The SD
indicators should be lit.
Check that the optical fibers are single-mode mul-

tiple fibers.
Check the optical unit.
Ethernet Link Fault Check the IP address configuration.
Check the EGPB board.
4.1.3 Shelf Management Fault

The procedure of the board startup is the following: the boards communicate with ECMM
through IPMC. ECMM controls the POWER ON for the boards in each slot and the boards
ask for the version files from UMP(OMP) for startup.
The shelf management fault is usually reflected by ECMM startup failure, board startup
failure, slave shelf startup failure, FAN ALM red light/big noise/no indicator.
The common causes are as follows:
l Improper ECMM status

l Wrench not closed
l ECDM configuration error
l Board hardware problem (wrong BOOT version, memory error, power module error,
hard-disk error).
l Fan failure
4-3

4.1.3.2 Phenomena and Cause

The common phenomena and causes of shelf management fault are shown in Table 4-3.
Table 4-3 COMMON PHENOMENA AND CAUSE OF SHELF MANAGEMENT FAULT
Phenomena Cause
ECMM startup failure Improper ECMM status
Board startup failure Wrench not closed

Board hardware faults (wrong BOOT version, or
problems on memory/power unit/hard disk)
ECDM not configured
Slave shelf startup failure ECDM configuration error

EGBS connection error
FAN ALM red light/big noise/no indicator Fan failure
4.2 Typical Cases

4.2.1 OMP Version File Fault
Phenomena
OMP cannot get version files from OMM.
Cause
Not configured in ECMM
Troubleshooting
1. Check whether the OMM fire wall is closed.
2. Based on the installation of OMM (internal/external), Telnet to the 24 port of ECMM.
In ddm-syscfg menu, do the query and configurations.
Cautions
None
4.2.2 Slave Shelf Startup Failure

Phenomena
The slave shelf cannot start.
4-4

Cause
l ECDM configuration error
l EGBS link error
Troubleshooting
1. Check the ECDM configurations.
2. Check the EGBS link.
Cautions
None
4.2.3 H/S Blue Light ON for All Boards

Phenomena
Blue light ON for all boards.
Cause
ECMM startup failure on EGBS
Troubleshooting
Check whether ECMM on EGBS starts successfully.
Cautions
None
4.2.4 H/S Blue Light ON for a Slot

Phenomena
H/S blue light on for one slot
Cause
l The slot not configured in ECMM
l Wrench not closed
Troubleshooting
1. Check the slot configuration in ECMM.
2. Check whether the wrench is closed.
4-5

Caution
None
4.2.5 Fan Noise/Fan Indicators Off

Phenomena
l Big fan noise
l Fan indicators off
Cause
l The dummy panel is not installed.
l Version error of SIPMC/FRU
Troubleshooting
1. Check whether the dummy board is properly installed.
2. Check whether the SIPMC/FRU version files are burned.
Cautions
None
4.2.6 OK Red Light ON for Fan Unit

Phenomena
OK red light ON for Fan unit
Cause
Fan failure
Troubleshooting
1. Check the fan alarms.
2. Check whether an internal fan stops working. If so, replace it.
Cautions
The fan unit supports hot swap.
4-6

4.2.7 Optical Fiber Communication Fault

Symptom
The indicator for the optical port is not lit on a board (including EAPB, ESDTA, ESDTT,
ESDTG, EGPB, ESDTI, EGFS).
Cause
Board failure or optical fiber failure
Troubleshooting
1. Replace the optical fiber.
2. Replace the optical module. The replaced one must be of the same type with the peer
end, and must be supported by the current system.
3. Replace the board.
Cautions
For the details of the board and component replacements, please refer to Appendix B,
Board and Component Replacement.
4.2.8 EGFS Unable to Lock Clock Reference from Optical Port

Phenomena
EGFS unable to lock clock reference from the optical port
Cause
l Low CN clock precision
l No CN clock for Dual Mode Controller. Cable connection error or NMS data
management error.
l EGFS do not have correctly burned single-chip program and logical files.
l Clock extraction cable error.
Troubleshooting
1. Check interface A of Dual Mode Controller.
2. Check the clock extraction on Dual Mode Controller Network Management.
3. Check whether the single-chip program for EGFS is correctly burned, and whether the
logic is correct.
4. Check if the CN clock is transferred to Dual Mode Controller.
5. Check the configurations of optical interface board.
Cautions
None
4-7

4.2.9 Slip Code on Communication Link at Base Station Connected

with Dual Mode Controller Through E1 Cable
Symptom
Slip codes are generated on the communication link at the Base Station connected with
Dual Mode Controller through the E1 cable.
Cause
1. The Base Station does not use the high-precision clock uploaded through the E1 cable.
The clocks are not synchronized.
2. No EGFS board is installed in the Dual Mode Controller system.
3. The clock board for Dual Mode Controller is not operating properly, or there is no clock
distribution cables to send the clock reference to the EGFS board.
4. The input standard set for the Dual Mode Controller system is poor, or the EGFS board
is in the state of fast capture of quality deterioration.
Troubleshooting
1. Check that the Base Station gets the clock reference through the E1 cable. The clocks
at the Base Station and the Dual Mode Controller system must be synchronized.
2. Check that the E1 interface board of Dual Mode Controller uses the clock of the EGFS
board.
3. Check that EGFS is operating properly.
4. Check that the clock source for the EGFS board is obtained from CN. Do not make it
obtain the clock reference from the Base Station and then send the reference back to
the Base station after synchronization.
Cautions
None
4-8

Chapter 5
Troubleshooting for Software
Initiation Problems
Table of Contents
Introduction ................................................................................................................5-1
Typical Cases.............................................................................................................5-3
5.1 Introduction
5.1.1 Background Information
Software initiation is the operations on the software version usually triggered by NM,
including the operations on the version files and the version configuration information.
ZXUR 9000 GU uses the unified hardware platform. According to the board type, the
software initiation process is executed under two circumstances: With the OMP board,
and not with the OMP board.
l With the OMP Board
During the startup, the OMP board requests the configuration file from the OMM
address allocated during the serial port debugging. If the file obtained is consistent
with the local file after comparison, the OMP starts after invoking the version file on
the local hard disk. Otherwise, the OMP starts after obtaining the version file from
the OMM and simultaneously modifies the local configuration file. If the configuration
file is unavailable, the OMP starts with the local configuration file.
l Not with the OMP board
During the startup, the software requests the version file from the active OMP board
instead of from OMM. The board compares the version information on the local FLASH
and the version information configured on OMP. If the version files are the same, the
software uses the version file stored on FLASH. If the version files are different, the
software uses the version file obtained from the OMP board.
5.1.2 Symptom
l The indicators on the board is not lit.
l The NM alarm system prompts that the board is offline, or the board status is unstable.
l All services related to the board are interrupted.
5-1

5.1.3 Troubleshooting Procedure

The troubleshooting flow of the board loading fault is shown in Figure 5-1.
Figure 5-1 Troubleshooting flow of the board loading fault
5.1.4 Fault Handling Steps

1. Check the physical connections. Check the cable connections at the ECMM, OMP
and OMC interfaces.
2. Check the configurations of each board:
l Check the configurations of the racks, shelves and slots.
l Check the module number, module type, unit number, and unit type.
3. Check on the NM server to see whether the DHCP requests and IP requests are
received from ECMM. If not, close the OMM firewall and reactivate the control plane
network port of OMM.
4. Load the new version files to the NM server.
5. Check the IP address configuration of NE. If the IP is modified, the OMM media plane
network port should be reactivated. Check on the NM server to see whether the DHCP
requests and IP requests are received from OMP.
6. Check the radio data configuration.
7. If possible, restart the EGBS board.
5-2

Chapter 5 Troubleshooting for Software Initiation Problems
5.2 Typical Cases

5.2.1 FTP Failure Given During Version Operation
The FTP is used when the version files are imported, deleted or downloaded to the NE.
This failure is probably caused by inactivated FTP service.
Check the configuration of FTP port.
5-3

5-4

Chapter 6
Troubleshooting for System
Communication Problems
Table of Contents
Communication Error at Interface A............................................................................6-1
Communication Error at Interface Gb .......................................................................6-10
Communication Error at Interface Abis .....................................................................6-13
Communication Error at Interface IU/IUR .................................................................6-15
Communication Faults at IUB Interface ....................................................................6-23
NM Alarms ...............................................................................................................6-27
6.1 Communication Error at Interface A

6.1.1 Introduction
At A interface, TDM transmission or IP transmission can be applied. 3GPP TS48 protocol
is adopted. There are three layers.
Layer 1 is physical layer, adopting 2M PCM digital channel and each 2M line having 31
64Kbps channel is used for service and signaling channel.
Layer 2 is data link layer and network layer, i.e. No. 7 signaling MTP2, MTP3, and SCCP
part.
Layer 3 is BSS Application Part (BSSAP), which is divided into BSS Management
Application Part (BSSMAP) and Direct Transfer Application Part (DTAP), transfers
information of BSS management, mobile management, and connection control.
Above mentioned is the case at TDM A and IP A. Layer 1 in above interface protocol uses
IP transmission, and layer 2 is SCTP, M3UA and SCCP.
1. The signaling link under TDM mode is shown in Figure 6-1.
6-1

Figure 6-1 Service Stream at Interface A Radio Network Control Layer Under TDM
Mode
• The words in the

brackets indicate the
names of boards.
2. The signaling link under IP mode is shown in Figure 6-2.
Figure 6-2 Service Stream at Interface A Radio Network Control Layer Under
IP Mode

names of boards.
6.1.1.2 Common Fault Phenomena

l The peer subsystem is not available.
l The peer office cannot be reached.
l All SS7 Links are broken.
l The coupling is down.
l The coupling is running, but the ASP is not activated.
6.1.1.3 Troubleshooting Procedure

Taking IP transmission as an example, this section describes the troubleshooting
procedure when communication failure occurs at interface A, as shown in Figure 6-3.
6-2

Chapter 6 Troubleshooting for System Communication Problems
Figure 6-3 Troubleshooting Procedure for Communication Failure at Interface A
6.1.1.4 Fault Handling Steps

1. Check the physical connections. Check the cables on the interface board.
2. Check the data configurations for interface A on ZXUR 9000 GU.
l Configure Local Office.
l Configure adjacent offices.
l Configure IP Address for the ports.
l Configure Sigtran.
3. Check the status of CMP and interface board.
4. Activate/deactivate the coupling in the status management interface of the NM client
to see whether the fault is cleared.
5. Check through the protocol layers.
If the fault still cannot be removed, try to restart the interface board, CMP board or the
OMP board if possible.
6-3

6.1.2 Typical Cases

6.1.2.1 MTP3 Layer -- Signaling Link Unavailable
Phenomena
The SS7 link is not available.
Cause
l The physical link is unavailable.
l The configurations of the signaling point code at both ends are inconsistent.
l The SLC configurations at both ends are inconsistent.
l The signaling test is set at the local end, but the signaling test code is null (0).
Troubleshooting
l Physical link failure: check the transmission.
l Point code configuration: check the consistency of the configurations at both ends.
à Signaling point configurations of the local office: On the configuration resource
tree, select Config Set > Ground Resource Management > transport
Configuration. Select the Local Office tab, and check the configuration.
à Signaling point configurations of the adjacent office: On the configuration
resource tree, select Config Set > Ground Resource Management > Transport
Configuration > 2G Office Configuration > A Office Configuration. select
the A Office tab and check the configuration.
l SLC configurations: check the data configuration. The link selection code for both
ends should be consistent.
SLC configuration: On the configuration resource tree, select Config Set > Ground
Resource Management > Transport Configuration > 2G Office Configuration >
A Office. Select the SS7 Link tab. Check the configurations.
l Signaling test code is null: Set the test code.
On the configuration resource tree, select Config Set > Ground Resource
Management > Transport Configuration. Select Local Office tab. Check the Test
Code.
6.1.2.2 MTP3 Layer -- Signaling Link Available While Office Status Not Reachable
Cause
The office and the routing configuration is incorrect.
6-4

Troubleshooting
l Open the configuration management interface and check the SS7 link state.
Check SS7 link state: On the configuration management interface, select Config
Set > Ground Resource Management > Transport Configuration > 2G Office
Configuration > A Office Configuration . Select the SS7 Link tab.
l Open the configuration management interface and modify the route configuration.
Modify the office Routing configuration: On the configuration management interface,

select Config Set > Ground Resource Management > Transport Configuration >
2G Office Configuration > A Office Configuration > SS7 Office Routing. Check
the routing configuration.
6.1.2.3 M3UA Layer -- Coupling Running While ASP Not Activated
Phenomena
The coupling to CN office is running, but the ASP is not activated.
Cause
1. The AS property configurations at both ends are not correct.
2. The RC and service mode configurations for AS at both ends are not correct.
Troubleshooting
1. Configure the AS properties. Select Config Set > Ground resource Management
> Transport Configuration > 2G Office Configuration > A Office Configuration >
AS Information. Check the label of application server AS.
One end of IUR should be configured with the IPSP client, and the other end should
be the IPSP server. At IU interface, CN is configured as SGP and BSC is configured
as ASP.
2. Configure the AS routing context. Select Config Set > Ground Resource
Management > transportation Management > 2G Office Configuration > A Office
Configuration > AS Information. Check the AS routing configuration. The routing
context at both ends should be consistent.
3. Configure the AS service modes. Select Config Set > ground Resource
Management > Transport Configuration > 2G Office Configuration > A Office
Configuration > AS Information. Check the AS mode configuration,which consists
of Over-ride and load sharing. The configuration at both ends should be consistent.
6-5

6.1.2.4 SCTP Layer -- Association Establishment Not Successful
Phenomena
SCTP association establishment not successful.
Cause
1. The association-related configurations are not correct.
2. The routing is not configured correctly.
3. The network cables are not connected properly.
4. Transfer Delay
Troubleshooting
1. Check the association configurations.
Select Config Set > Ground Resource Management > transport Configuration
> 2G Office Configuration > A Office Configuration > Association. Select
Association and Port and IP Configuration tabs to check the configurations.
2. Check the static routing configurations.

3. Reconnect the network cable or replace it.
4. Adjust the connection of the two office. Avoid using too many switch devices.
6.1.2.5 Service Unavailable at E1 Port
Phenomena
The E1 port of A-interface can not enter into service status, and E1 alarm occurs on EDTT
board.
Cause
1. It is possibly the transmission problem or MSC-side problem.
2. It is possibly the EDTT board fault.
Troubleshooting
1. Implement self-loop at the distribution frame to troubleshoot the local end problems.
2. Check transmission and MSC hardware.
Cautions
None
6-6

6.1.2.6 No. 7 Signaling Disconnected
Phenomena
No. 7 signaling is in non-service status.
Cause
1. Transmission fault, with the symptom of alarm of E1 connecting EDTT board and MSC.
2. EDTT boards failure
3. Data configuration is inconsistent with that of the opposite end, including signaling
timeslot, SLC, and signaling point type.
Troubleshooting
1. Confirm whether fault exists in transmission.
2. Check whether configurations of both sides are consistent.
3. Troubleshoot the hardware problem by replacing relevant EDTT board.
Cautions
If it is diagnosed to be hardware problem and requires replacing board, then implement
the operation during non-busy hour in consideration of the influence range.
6.1.2.7 Unstable No. 7 Signaling
Phenomena
No. 7 signaling is unstable, sometimes connected and sometimes disconnected.
Cause
1. Transmission problems, including high bit error ratio of transmission equipment and
bad contact of connectors
2. The fault is possibly due to message overflow resulting from high signaling load.
Usually, the unidirectional signaling link load should not exceed 0.2 ERL.
Troubleshooting
1. Check whether connections are reliable. Test the bit error ratio of transmission.
2. Check the signaling link load through performance measurement. Expand the link if
the load is too high.
Cautions
None
6-7

6.1.2.8 Office is Available and BSC Message Cannot Reach MSC Server
Phenomena
During coupling trace of BSC M3UA, the message has been sent to BSC, and BSC sends
message to IP domain from exchange domain; but in M3UA coupling trace on MSC Server,
it is found that BSC message cannot reach MSC Server.
Cause
Normally, this problem may occurs on BSC SigTran configuration, including these two
following cases:
1. SI0 location is inaccurate, the message transferred from exchange domain by BSC is
implemented by keywords record in index SI0 location. If SI0 location is inaccurate,
BSC may discard relevant messages.
2. Network appearance configuration of BSC is inconsistent with that of MSC Server.
M3UA transmitting message carries network appearance parameters. If it is inconsis-
tent at two sides, it may be discarded.
Troubleshooting
1. Use NM client to view whether "Original point code" that configures "SIO location" at
interface A is correct.
2. Use NM client to view whether "network appearance" that configures "local office point"
is consistent with network appearance setting on MSC Server. If inconsistent, you shall
modify it to be consistent.
Cautions
None
6.1.2.9 Service Fault I Due to Wrong Configuration at CN Side
Fault Description
When connecting WCN, both sides cannot connect successfully at the begining, SCCP
user at this office point MTP3 is wrongly added for MGW. Signaling and subsystem at
MTP3 layer on ZXUR 9000 GU are normal, and opposite side also finds normal signaling
state in ZXUR 9000 GU. However, it cannot connect at service aspect, and ZXUR 9000
GU cannot receive SCCP layer signaling returned from MGW.
Cause
View WCN data, when MSC SERVER is directly connected to ZXUR 9000 GU, signaling
point in local office for MGW and MSC SERVER is same, and MGW as SG signaling
gateway is working under agent mode. Local signaling point for MGW can' configure SCCP
user.
6-8

Troubleshooting
Delete SCCP user at local signaling point MTP3 for MGW, and connection for service
signal at high layer is restored.
Cautions
To guarantee successfully connection, you shall block/unblock relay circuit at interface A
by NM status management interface. Connection can be considered as success after
you find "block", "block acknowledgement", "unblock", and "unblock acknowledgement"
message from signaling trace. You'd better use test-purpose MS to call each other, if call
can be connected, the signaling connection at interface A is successful.
6.1.2.10 Service Faults from Wrong Configuration at CN Side
Phenomena
After configuration, signaling at MTP3 layer is connected and test message can be
successfully sent. After sending message, error message is received. The fault reason is
unavailable opposite end from CN side.
Link is blocked in Dynamic Data Management at the NM client.
Cause
CN is 3 in 1. The signaling point with 24 bits is used for 3G, and the signaling point with
14 bits is used for 2G. During configuration, you shall configure a coupling from 14 bits
to 24bits between MGW and MSC. One missing SCTP coupling configuration between
MGW and MSC at CN side leads to SSN disconnection at adjacent office in ZXUR 9000
GU MSC.
Troubleshooting
After adding a SCTP coupling configuration between MGW and MSC, the problem is
solved.
6.1.2.11 Association Disconnection Due to Data Configuration
Phenomena
When certain BSC connects CN, coupling can not be connected.
Cause
Check process parameters on application server for local office point in background
configuration management, "Application property" is configured as "server"; verify it with
the engineer at CN side, this property for MSC Server is also configured as "Server", if
the settings for both parties are same, coupling is impossible to connect.
6-9

Troubleshooting
After changing "application property" on application server at BSC side to "Client", the
problem is solved.
6.2 Communication Error at Interface Gb

6.2.1 Introduction
The Gb interface is the interface between SGSN and BSS. SGSN establishes a packet data
connection to BSS and MS through the Gb interface to perform packet data transmission,
mobility management, and session management. The Gb interface is mandatory for GPRS
networking. The TDM transmission and IP transmission can be applied at the Gb interface.
1. For the TDM mode, the service stream of Gb interface radio network control layer is
shown in Figure 6-4.
Figure 6-4 Service Stream of Gb Interface Radio Network Control Layer in TDM
mode

names of boards.
2. For the IP mode, the service stream of Gb interface radio network control layer is
6-10

Figure 6-5 Service Stream of Gb Interface Radio Network Control Layer in IP mode

names of boards.
6.2.1.2 Common Symptoms of Gb Faults

l The public control channel for PS domain services is overloaded.
l The link of service plane (PS service) is broken
l The peer subsystem is not available.
l The peer office cannot be reached.
l The association is down.
l The association is running, but the ASP is not activated.

For the details, refer to Section 6.1.1.3, Troubleshooting Procedure for interface A.

For the details, refer to Section 6.1.1.4, Fault Handling Steps for interface A.
6.2.2 Typical Cases

6.2.2.1 NSVC Disconnection
Symptom
NSVC is disconnected.
Cause
1. The transmission system is in fault.
2. The Gb interface board is in fault.
3. The configuration parameters at BSS are inconsistent with that at SGSN, for example,
NSEI, NSVCI, DLCI and the time-slot number for BRCH.
4. The E1 transmission line is self-looped at the remote end.
5. SGSN is in fault.
6-11

Troubleshooting
For a link fault, two possible cases should be considered: link establishment failure and
link breaking.
1. Link establishment failure
l Check that the data configurations at both ends of Gb interface are consistent.
l Check whether the Gb interface board has "signal loss" alarm and whether the
Gb transmission system is in fault.
l Query the alarm information of the Gb interface board to find out the causes.
l Select multiple loop points for self-loop test.
2. Link breaking
l Check whether the Gb interface board has any "signal loss" alarm and whether
the Gb transmission system is in fault.
l Query the alarm information of the Gb interface board to find out the causes
Cautions
For the interface problem between communication NEs, personnels at both sides should
work together to troubleshoot the problem.
In addition, self-loop test is often used for quick locating of the fault range. Multiple loop
points can be selected for the self-loop test, for example, near-end E1 port, near-end DDF,
and far-end DDF.
6.2.2.2 Intermittent NSVC Connection
Symptom
The NSVC connection is intermittent.
Cause
1. Impedances of the frame relay interface boards on both ends of ZXUR 9000 GU and
SGSN do not match.
2. The Gb interface board is in fault.
3. Connectors of the distribution frame or the E1 cables are not stable, and the bit error
ratio of E1 transmission line is too high. Therefore the bit errors on the link increase
and the transmission of the upper-layer link becomes unstable.
Troubleshooting
1. Check whether the bit error ratio of the transmission system is too high. Particularly in
the case of the link from ZXUR 9000 GU to SGSN being long and passing area with
harsh natural environment, use a BER tester or a PCM analyzer to test E1 channel for
accurate bit error ratio. Usually, the bit error ratio cannot exceed 10-6.
2. Query the alarm information of the Gb interface board to check whether the board fails
and find out the cause. Replace the board to locate the fault if necessary.
6-12

Cautions
None
6.3 Communication Error at Interface Abis

6.3.1 Introduction
The Abis interface is defined as an interface between BSC and the base station. This
interface supports all services provided to users, especially radio resource management
including the base station radio equipment control and radio frequency allocation. TDM
transmission and IP transmission can be applied at Abis interface.
1. Under TDM mode, the service stream of Abis interface radio network control layer is
Figure 6-6 Service Stream of Abis Interface Radio Network Control Layer Under
TDM Mode
2. Under IP mode, the service stream of Abis interface radio network control layer is
6-13

IP Mode
6.3.1.2 Common Fault Phenomena

l The transportation link is broken.
l Channels are added or deleted repeatedly.
l The Abis link is broken.
l The LAPD communication link is broken.
l The call cannot be connected.
l The call can only be connected for several times.

For the procedure, please refer to the troubleshooting procedure for interface A.

For the steps, please refer to fault handling steps for interface A communication.
6.3.2 Typical Cases

6.3.2.1 SCTP Layer
Refer to the corresponding section for interface A.
6.3.2.2 Calling Faults Caused by E1 Configuration Error
Phenomena
Calling is failed at certain site.
Cause
1. Check and analyze the phenomenon by using alarm management and status
management functions.
6-14

2. Do intentional inspection based on background phenomenon. First check hardware

board and transmission link, check data configuration after confirmation, and check
whether data configuration is wrong.
3. If errors on data configuration of transmission link is found, you shall modify data. If E1
frame format is wrongly configured, or parameters at CSTM-1 optical port is wrongly
configured, the service may be affected.
Troubleshooting
Modify wrong data based troubleshooting analysis steps.
6.4 Communication Error at Interface IU/IUR

6.4.1 Overview of Communication Fault at IU/IUR Interface
Background Knowledge
At IU/IUR interface, RNC connects with CN, or connects with the adjacent RNC through
No.7 signaling, and the corresponding link is called as No.7 signaling link. When IU/IUR
interface uses ATM transmission, No.7 link is borne on SSCOP link. When IU/IUR interface
uses IP transmission, No,7 link is borne on the association.
1. Signaling procedure in ATM mode is shown in Figure 6-8. The boards where the
protocols are processed are illustrated in the brackets.
Figure 6-8 IU/IUR INTERFACE RADIO NETWORK CONTROL LAYER SERVICE

FLOW IN ATM MODE
2. Signaling procedure in IP mode is shown in Figure 6-9.
6-15


FLOW IN IP MODE
Fault Description
l No response after CR message being sent
l Peer subsystem unavailable
l Peer office inaccessible
l No.7 link disconnected
l Association disconnected
l Association connected but ASP inactivated
Troubleshooting flow
Taking IP transmission mode as example, the common Troubleshooting flow for IU/IUR
interface communication faults is as shown in Figure 6-10.
6-16

Figure 6-10 IU/IUR INTERFACE COMMUNICATION FAULT Troubleshooting FLOW
Troubleshooting steps
1. Check the physical connection to see whether the abnormality at IU/IUR interface is
caused by the cable connection. Especially, check the cable connection on IP interface
board.
2. Check the data configuration related to IU/IUR interface on ZXUR 9000 GU.
l Local office configuration
l Adjacent office configuration
l Port IP address configuration
l SIGTRAN data configuration.
3. Check whether the status of CMP that manages the association module is normal and
whether EGPB status is normal. Check whether there are related alarm.
4. Activate/De-activate the association with the dynamic data management provided by
NM and then check whether the alarm disappears.
5. Locate the fault with the alarm provided by NM steps by steps according to the protocol
layers. Minimize the range and eliminate the fault.
6-17

If after trying all above methods, the fault still exists. If conditions allow, reboot EGPB,
CMP, and OMP to see whether the link failure is repaired.
6.4.2 Typical Communication Faults at IU/IUR Interface

6.4.2.1 MTP3B Layer – Signaling Link Unavailable
Symptom
The No.7 signaling link is unavailable.
Analysis
l The Service Specific Connection Oriented Protocol (SSCOP) link is disconnected.
l The configurations of the signaling point codes at both ends are not consistent. The
related parameters include point code type, point code, and sub-service field (SSF).
l The configurations of Signaling Link Code (SLC) at both ends are not consistent.
l The signaling test is configured at the local end, but the test code is null (0). This
causes the failure of sending the SLTM message.
Troubleshooting
l For disconnected SSCOP link, refer to the section “SSCS Layer - SSCOP
Link Constantly Disconnected” and the section “SSCS Layer — SSCOP Link
Discontinuously Connected”.
l Checking the configuration of signaling point codes
Check the interconnection data configuration, and make sure that the signaling point
configurations (signaling point type, signaling point and SSF) are the same at both
ends.
à Check the signaling point configuration at the local office: On the navigation tree
of the OMC configuration management window, expand Config Set > Ground
Resource Management > Transport Configuration , and double-click the
Transport Configuration node.
Next, click the Signalling Points at Local Office tab in the right pane, and
double-click the record on the tab. In the pop-up dialog box, check whether the
signaling point at the local office is correctly configured.
à Check the signaling point configuration at the adjacent office: On the navigation
tree of the OMC configuration management window, expand Config Set >
Ground Resource Management > Transport Configuration > 3G Office
Configuration > IUCS Configuration, and double-click the IUCS Configuration
node.
Next, click the Basic Information tab in the right pane, and check whether the
signaling point configuration, sub-service field, and signaling point coding type
are correctly configured.
6-18

l Checking the SLC configuration.

Check the consistency of signaling link codes at the two ends.
Check the signaling link code in the adjacent signaling link configuration: On NM
configuration management interface, expand Config Set > Ground Resource
Management > Transport Configuration > 3G Office Configuration > IUCS
Configuration, and double-click IUCS Configuration.
Next, click the Broadband Signaling Links tab in the right pane. Double-click a
record, and check whether signaling link code is the same as the code configured at
the peer end in the pop-up dialog box.
l Signaling test code is null.

In the OMC configuration management window, set the test code to a non-zero value.
Expand Config Set > Ground Resource Management > Transport Configuration,
and double-click the Transport Configuration node.
Next, click the Local Office tab, and check whether Test Code is 0. If yes, set it to
a non-zero value.
Precautions
None
6.4.2.2 MTP3B Layer – Signaling Link Available but Office Inaccessible
Analysis
The Office routing configuration is incorrect.
Solution
l Open the OMC configuration management window, and check the status of No.7
signaling link.
Check the No.7 signaling link: expand Config Set > Ground Resource Management
> Transport Configuration > 3G Office Configuration > IUCS Configuration, and
double-click the IUCS Configuration node.
In the right pane, click the No.7 Link tab to check the No.7 link status.
l In the OMC configuration management window, check whether the routing

configuration is incorrect. If yes, modify the configuration.
Expand Config Set > Ground Resource Management > Transport Configuration
> 3G Office Configuration > IUCS Configuration, and double-click the IUCS
Configuration node. Next, click the No.7 Office Route tab. Check the routing
configurations.
6-19

The signaling routing office number must be the same as the direct-connect office
number of the link group corresponding to the normal routing.
6.4.2.3 M3UA Layer – Association Connected but ASP not Activated
Symptom
The association to the Core Network (CN) is connected, bur ASP is not activated.
Analysis
l AS properties at the both ends are not consistent.
l AS RC (Routing Context) and the service mode are configured inconsistent at the
both ends.
Solution
1. In the OMC configuration management window, expand Config Set > Ground
IUCS Configuration, and double-click IUCS Configuration.
Next, click the AS Information tab, and check whether AS Property is configured
correctly.
The configuration rule is: at the Iur interface, one end is configured as IPSP_CLIENT
and the other end is configured as IPSP_SERVER. At the Iu interface, the CN is
configured as SGP, while the RNC is configured as ASP.
2. Check whether AS routing context is properly configured.
Expand Config Set > Ground Resource Management > Transport Configuration
> 3G Office Configuration > IUCS Configuration, and double-click IUCS
Configuration.
Next, click the AS Information tab, and check whether parameters related to AS
routing context are consistent with the corresponding parameters at the peer end.
3. Check whether the AS traffic mode is the same as the corresponding parameter
configured at the peer end.
The AS Traffic Mode is on the AS Information tab.
6.4.2.4 SCTP Layer – Association Setup Failure
Symptom
SCTP association is set up unsuccessfully and the notification is reported.
6-20

Analysis
l The four elements (local–end IP address, peer-end port No., peer-end IP address, and
peer-end port No.) that decide the association and the association protocol properties
(CLIENT/SERVER) are not configured correctly.
l The route is configured incorrectly (if the peer service address and the interface
address of the association are not in the same network segment, the route should
be configured).
l The network cable is plugged error or the network cable is disconnected.
l The transmission is delayed. The transmission is delayed.
Troubleshooting
l Association configuration
In the OMC configuration management window, check the four elements of the
association are correctly configured and whether consistent with the configurations
at the peer end.
Double–click Config Set > Ground Resource Management > Transport

Configuration > 3G Office Configuration > IUCS Configuration > Association,
and check the association configuration on the Association tab and Port and IP
Configuration tab.
Select IP Configuration of SCTP Association tab and check whether IP address is
correctly set.
l Routing configuration
On NM configuration management interface, check whether the static route is correctly
configured in IP stack. If the RNC connects to the peer element via Ethernet, the
next-hopping address of the static routing should be configured as the interface board
address of the peer element, instead of the address of EGPB at the local end.
l Network cable error or disconnected
Re-plug the network cable or replace the network cable.
l Transmission delay
Adjust the cable connection between the two offices and do not use more switching
devices between the two offices.
6.4.2.5 SSCS Layer – SSCOP Link Constantly Disconnected
Symptom
On NM configuration management interface, click NE Configuration Information. Select
one piece of signaling link configuration and find that the corresponding SSCOP link is
constantly unavailable.
6-21

Analysis
l The fiber connection is error.
l The local optical interface is configured error.
l PVC interconnection parameters are error.
Troubleshooting
l Fiber connection error
Check whether the fiber connection on EAPB is normal. If the indicator at the optical
interface is not ON, the fiber connection with the peer end is faulty.
l Local optical interface configuration error
Make sure that the optical interface where the configured link locates (high-end ATM
Sunit No. in PVC configuration) is configured same as the optical interface where the
fiber is plugged (the optical interface where the fiber is plugged is, from up down, 4,
5, 6, 7).
Transmission Configuration
Double–click Config Set > Ground Resource Management > > Transport
Configuration > 3G Office Configuration > IUCS Configuration, and click the
Broadband Signalling Link tab in the right pane. Check the optical port the link
connects to (High Port of PVC).
l Interconnection parameter error

Check the interconnection parameters of both ends in the OMC client. On the
Broadband Signalling Link tab, check VPI on High Port and VCI on High Port.
6.4.2.6 SSCS Layer – SSCOP Link Discontinuously Connected
Symptom
In the OMC configuration management window, click NE Configuration Information.
Select one piece of signaling link configuration and find that the corresponding SSCOP
link is switching between available and unavailable.
Analysis
l IU interface MTP3B error: SSCOP link at NNI side needs generating the link setup
requests at the both ends. CMP fault at the RNC side may result in mtp3b not
generating link setup request at ZXUR 9000 GU side. After SSCOP link receives the
BGN PDU link setup request from the peer end, the upper-layer sends the ReleaseReq
message.
l IU interface link setup validation failure: After sscop is set up at NNI side, some SD
packets are sent to validate the link transmission quality. If packet loss occurs, the
6-22

link release request is sent. Sscop link setup is normal at NNI end but immediately,
sscop receives ReleaseReq from the upper-layer or the peer end, which causes the
link release. Or, Test code on Mtp3b layer is not filled in, which cause the NNI link
validation failure.
Troubleshooting
l IU interface mtp3b error
Check whether CMP that Mtp3b belongs to is running normally.

Checking methods: In the OMC, check whether OSS communication disconnection
alarm is reported by the CMP board. Check whether the RUN indicator on the CMP
board is in normal state. If the CMP board is abnormal, repair the board fault first.
l IU interface link setup validation failure

Check whether the fiber connection at IU interface is normal. Check whether the test
code is filled in and the value can not be 0.
In the OMC configuration management window, click Config Set > Ground Resource
Management > Transport Configuration . Click the Local Office tab, and check
whether Test Code is zero.
6.5 Communication Faults at IUB Interface

6.5.1 Overview of Communication Faults at Iub Interface
NM knowledge introduction
At IUB interface, ZXUR 9000 GU connects with the base station through NBAP signaling,
and the corresponding link is called as NCP link and CCP link. When IUB interface uses
ATM transmission, NCP link and CCP link are borne on SSCOP link. When IUB interface
uses IP transmission, NCP link and CCP link are borne on the association.
1. Signaling path in ATM mode
The words in the brackets are the name of the board where the protocol layer locates.
6-23

Figure 6-11 Radio Network Layer Control Plane Signaling Procedure (ATM)
Figure 6-12 Transport Network Layer Control Plane Signaling Procedure
2. Signaling path in IP mode
Figure 6-13 Radio Network Layer Control Plane Signaling Procedure (IP)
Fault description
l NCP link error
l CCP link error
l Repeated common channel deletion and creation
6-24

l Call failure after common channel successfully created

l Call failure after several succeeded
Troubleshooting flow
Refer to IU/IUR INTERFACE COMMUNICATION FAULT Troubleshooting FLOW.
6.5.2 Typical Communication Faults at IUB Interface

6.5.2.1 ALCAP Layer – Repeated Common Transport Channel Deletion and Setup
Symptom
The Node B OMC indicates that the common transport channel is set up and deleted
repeatedly.
Analysis
l AAL2PATH interconnection parameters are inconsistent.
l ATM address is invalid.
l AAL2 Path type and the service type are inconsistent.
l Transport path bandwidth is inadequate.
l On the signaling tracing, the end that initiates the link setup request sends ERQ and
receives RLC.
Troubleshooting
l Inconsistent interconnection parameters
In the OMC configuration management window, expand Config Set > Ground
IUCS Configuration, and double-click IUCS Configuration. In the right pane, select
the AAL2 Path tab. Check the settings of AAL2 Path basic properties.
The AAl2 path ID Path ID is the interconnection parameter, which should be same as
the path ID at the peer end.
In the OMC Status Management window, check whether AAL2 Path is available.
Double-click Status Management to open the Status Management tab in the right
pane. Next, click the AAL2 Path Management tab. Right-click a path record, and
select To query all path status from the shortcut menu.
In the configuration management window, double-click the path record to open the
AAL2 Path dialog box. Check PVC ID, VPI on High Port, and VCI on High Port.
l Invalid ATM address
In NM configuration management, check whether the ATM address of the local office
is configured same as that of the target office.
6-25

On NM configuration management interface, double–click Config Set > Ground

IUCS Configuration. Click a record on the IUCS Configuration pane to open the
ATM Adjacent Office dialog box, and check whether ATM address configuration is
the same as that at the peer NE.
l AAl2 Path type inconsistent with service type

In NM configuration management, check whether AAl2 Path type matches the service
type.
On NM configuration management interface, expand Config Set > Ground
IUCS Configuration, and double-click IUCS Configuration. Click the AAL2 Path
tab, and double-click a record in the right pane to open the AAL2 Path dialog box.
Check whether Service Type matches that of the subscriber.
l Inadequate transport path bandwidth
On NM configuration management interface, expand Config Set > Ground
Resource Management > Transport Configuration > 3G Office Configuration
> IUCS Configuration, and double-click IUCS Configuration. Click the Tr Path
tab, and double-click a record on the tab. In the pop-up dialog box, check whether
the transport path bandwidth is adequate. Forward bandwidth corresponds to
the transmitting direction of the NE, while ackward bandwidth corresponds to the
receiving direction of the NE.
6.5.2.2 ALCAP Layer – Call Failure after Common Transport Channel Created
Symptom
Fail to make calls after the common transport channel is created.
Analysis
l AAL2 path type is inconsistent with the service type.
l The bandwidth of the transport path is inadequate.
Troubleshooting
Refer to ALCAP Layer – Repeating Common Transport Channel Deletion and Setup.
6.5.2.3 SCTP Layer

Refer to SCTP Layer – Association Setup Failure.
6.5.2.4 SSCS Layer

Refer to SSCS Layer – SSCOP Link Constantly Disconnected and SSCS Layer – SSCOP
Link Discontinuously Connected.
6-26

6.6 NM Alarms
6.6.1 Signaling Point Unreachable Alarm
Phenomena
The system gives alarms.
Cause
l All the corresponding No. 7 links for the signaling points have not been established.
Check on the NM management interface that the No. 7 link to this No. office is
available.
l The routing to the peer end signaling is not configured. Check on the NM management
interface that the routing information for this office is correct.
l The channel is manually blocked.
Troubleshooting
1. If all the No. 7 signaling links are broken, check them to resolve the faults.
2. If at least one No. 7 signaling link is normal, check the configuration data that the
routing to the peer end signaling point is correct.
3. If the link and routing are both normal, check the NM configuration data whether the
adjacent office is manually blocked. If so, do the manually unblock operation.
Cautions
If all the No. 7 links to this office are broken, the adjacent signaling point cannot be
reached. First check the transportation system or the A/Iu interface board at the Dual
Mode Controller side.
If this is the first time the data configuration is performed, check the configuration carefully.
6.6.2 SCCP Subsystem Unavailable

Phenomena
The system gives alarm about SCCP subsystem unavailable.
Cause
1. Check on the NM configuration interface that the adjacent office state is reachable.
2. After the adjacent office signaling point receives the SST messages from Dual Mode
Controller, no SSA is returned back. Therefore the corresponding SSN is not available.
3. Check whether the subsystem is manually blocked.
6-27

Troubleshooting
1. Locate the faults that the signaling points is not reachable.
2. If the signaling point to the adjacent office can be reached, check with the signaling
tracing tool whether the adjacent cell sent SST. If no SSA is received, check the routing
configuration and the subsystem configuration.
Cautions
None
6.6.3 Association Establishment Failed

Phenomena
The alarming interface informs that the association setup failed.
Cause
SCTP cannot set up a link.
Troubleshooting
1. Check that the EGPB interface board is operating normally.
2. Check that the physical link is good.
3. Check that the configurations of the association are correct.
Cautions
None
6.6.4 Association Link Broken Alarm

Phenomena
The alarming interface reports that the association link is broken.
Cause
1. The association is deleted.
2. The association is released manually.
3. The transportation link between the two end of association is broken.
Troubleshooting
Configure an IP on the debug computer that is in the same network element with EGPB.
Connect this debug computer to the network in which the EGPB interface board resides.
Ping the IP address for the interface board at both ends. Check that the network is good.
6-28

Cautions
None
6.6.5 Association Congestion Alarm

Phenomena
The alarming interface reports that the association link is in congestion.
Cause
The sending buffering for SCTP association is in congestion.
Troubleshooting
The upper layer uses reduce the sending stream.
Cautions
None
6.6.6 M3UA Office Not Reachable

Phenomena
The NM alarming interface reports that the M3UA office is not reachable.
Cause
1. The coupling link is released, or the AS is not in service.
2. The routing to this office is not configured.
Troubleshooting
1. Check the association status. If it is operating normally, query the status of the serving
AS.
2. Check the routing configuration.
Cautions
None
6-29

6-30

Appendix A
Troubleshooting Record
Table
Office Name: __________________
Time of Fault Occurrence: (HH-MM-DD-YY) Time of Solution: (HH-MM-DD-YY)
Device name Equipment No.
□ OMC □ Major alarm
□ Routine
□ Radio load
maintenance
□ User complaint
□ Hardware
□ Others
□ Radio service bearer

Fault type Fault source
□ Switch
□ Radio global resource
□ Software load
□ Access
□ System communication
Symptom
Fault causes
Trouble shooting
method
A-1

Cautions
Summary
Outstanding problems:
Maintenance personnel’s advice and Supervisor’s comment and signature:

signature:
A-2

Appendix B
Board and Component
Replacement
Table of Contents
Ÿ Overview to Board and Part Replacement .............................................................. B-1
Ÿ Replacing Board ..................................................................................................... B-1
Ÿ Replacing Components .......................................................................................... B-2
Ÿ Replacing Fan Unit ................................................................................................. B-3
Ÿ Replacing Optical Model......................................................................................... B-4
Ÿ M/S Switchover ...................................................................................................... B-4
Ÿ Resetting Board...................................................................................................... B-4
B.1 Overview to Board and Part Replacement

In the process of routine maintenance, replacing the faulty boards and parts is a common
yet important maintenance means. Pay attention to the following principles during the
board replacement:
1. Keep the spare parts in antistatic bags (attached with desiccant) and store in cardboard
boxes. Label the bags and boxes for convenience.
2. Be sure to wear antistatic wrist straps when plugging/unplugging the board. When
holding a board, keep your hands off the board circuit, components, and cabling. Do
not apply too much force on the board to prevent damaging the connectors of the
board and the backplane.
3. Mark the fault information on the replaced faulty board before storing it in the antistatic
bag.
4. When plugging the board, make sure it completely fits into the shelf.
5. Never plug or unplug power boards with the power switched on.
B.2 Replacing Board

Preparations
1. Analyze the fault causes and determine the faulty board to be replaced.
2. Make sure that the spare parts for replacement is in good condition and their models
are consistent. Confirm that the physical board versions, logical board configuration,
programmable logic versions, and boot version tags are same as on the faulty board.
B-1

3. Prepare antistatic bags, desiccant, right cardboards and labels.

4. Prepare the straight screwdriver and cross screwdriver.
Steps
1. Properly wear the antistatic strap and make sure that the other end of the strap is
grounded.
2. To replace a master board or an optical module of the master board, perform M/S
switching first, to make the current slave board or slave optical path turn to master.
Perform M/S switching to the faulty board or faulty link through NM. When the ACT
indicator in the faulty board becomes off and ACT indicator on slave board becomes
on, the board successfully changed the M/S status.
3. To just replace the optical module
Record the optical fiber type and the connection locations at two ends. Unplug the two
optical fibers of faulty optical paths, open the lock device of the faulty optical module,
unplug the faulty optical module, then plug the spare optical module, close the lock
device, and then connect the optical fibers according to the corresponding connection
relationship.
4. Use a screwdriver to screw off the screws at the board levers, turn outside both
extractor levers to plug off the board from the rack. After the H/S blue light is lit, draw
out the board slowly. During this process, avoid touching the components and circuits
on the board.
5. Align the spare board with the slot, press the lever on it and gently push it in along
the track until the lever is locked, which indicates that the board has been properly
plugged in position. Screw on the captive screws at the board levers.
6. Place the faulty board or optical module into an antistatic bag attached with desiccant.
Label the bag marking the board’s or optical module model number, slot number,
program version and fault information, and then store it in the right category.
Verification
Observe the power-on and startup process of the replaced board. If self-test is passed, the
panel indicators display the normal running status, the fault alarm is cleared, and related
services are normal during the test, the replacement is successful.
If the board self-check fails, it performs the self-check again and finally shows abnormality,
and the relevant unit service is not resumed. This indicates the unsuccessful replacement.
In this case, first check whether the replaced spare part is damaged. If it is normal, continue
with fault analysis.
B.3 Replacing Components

Here, parts refer to the whole layer of shelf or the whole layer of fan shelf.
B-2

Appendix B Board and Component Replacement
Preparation
The preparation process is consistent with that before board replacement. Refer to Board
Replacement for details.
Steps
1. Wear the antistatic strap and power off the shelf or the rack.
2. Record the cables, optical fiber types, the connection locations at two ends, and DIP
switch locations on the backplane. Unplug all cables from back boards and all optical
fibers from front boards.
3. Record the current front board, back board and its slot. Unplug all boards in the shelf.
4. Unscrew the fixing screws of this whole layer of shelf from the front of the rack, and
then the fixation screws for shelf grounding. Pull out the power cable of the shelf and
then the whole shelf from the front.
5. Pull the replaced shelf into the rack properly, and then tighten all fixing screws.
6. Plug all boards and back boards into the slots properly according to the record.
7. Restore cables and optical fiber connections of the system according to the record.
8. Check whether all cable and optical fiber connections, and DIP switch locations on the
backplane are correct.
9. Power on the shelf or the rack again and restart the system.
Verification
Observe the power-on and startup process of the system after replacement. If MP and
board self-tests are passed, the panel indicators display the normal running status, the fault
alarm is cleared, and related services are restored normally, the replacement is successful.
If an MP or a board cannot pass the self-test, the original fault cannot be cleared, and
related system services cannot be restored, the replacement fails. In this case, check
whether the shelf or backplane is damaged. If the new parts are normal, continue with
fault analysis.
B.4 Replacing Fan Unit

Preparation
The preparation work is the same as that of the board replacement. For details, refer to
Appendix B.2 Replacing Board.
Steps
1. Wear an antistatic wrist strap.
2. Press the shielding finger switch on the fan unit with your thumb and then extract the
fan unit.
3. Install a new fan or replace the circuit board in fault.
4. Insert the fan unit into the fan shelf.
B-3

Check
Check the panel indicator of the replaced fan unit. If the indicator shows the normal and
the fault alarms are cleared, the replacement is successful.
B.5 Replacing Optical Model

Preparation
The preparation work is the same as that of the board replacement. For details, refer to
Appendix B.2 Replacing Board.
Steps
1. Wear an antistatic wrist strap.
2. Extract the optical fiber.
3. Lift the iron ring of the optical module (vertical to the panel).
4. Extract the optical module through the iron ring.
5. Insert the optical module to be replaced and press the iron ring (parallel with the panel).
Check
Insert the optical fiber. If the indicator is lit, the contact is fine.
B.6 M/S Switchover

From the NM status management interface, right-click the board, and select Normal
Switchover or Force Switchover.
Check
If the ACT indicator on the slave board is lit and that of the master board is not lit, the
switchover is successful.
B.7 Resetting Board

There are two methods to reset a board: reset operation on NM, or on hardware equipment.
1. Reset operation on NM
Select the board to be reset from the NM status management interface, right-click the
board node (rack diagram) and select Normal Reset or Force Reset from the shortcut
menu to send the reset command.
2. Reset on hardware equipment
Click the RST button on the panel to send the reset command.
3. Check
B-4

Appendix B Board and Component Replacement
If the H/S indicator and OK indicator is not lit and the OOS indicator is lit in green, the
board is reset and powered on.
B-5

B-6

Appendix C
Running Information
Description
Table of Contents
Ÿ Introduction ............................................................................................................ C-1
Ÿ Indicator ................................................................................................................. C-1
C.1 Introduction
You can determine the board running status by observing the indicators. Currently, the
rear board indicators are classified into two types: IPMC controlled and upper software
controlled.
C.2 Indicator
C.2.1 Types of Indicators on Board Panel
In the ZXUR 9000 GU system, the indicators on the board panel fall into common indicators
and special indicators.
1. Common indicators
l OOS
l OK
l H/S
l ACT
l HOST
OOS, OK and H/S indicators are controlled by IPMC. ACT and HOST indicators are
controlled by upper-layer software.
2. Special indicators
Except for the common indicators, different boards have their special indicators. For
details, please refer to ZXUR 9000 GU (V1.01.00) Dual Mode Controller Hardware
Discription.
C.2.2 Common Indicator Statuses

The statuses of the common indicators are shown in Table C-1.
C-1

Table C-1 Statuses of Common Indicators
Type Status Description
1 Constantly ON The indicator is constantly ON

at a specific status.
2 Constantly OFF The indicator is constantly OFF

at a specific status.
3 Flashing at 5 Hz The period is 0.2 second and

the vacant period ratio is 50%:
ON for 0.1 second and OFF for
0.1 second.
4 Flashing at 2 Hz The period is 0.5 second and

ON for 0.25 second and OFF
for 0.25 second.
5 Flashing at 1 Hz The period is 1 second and the

vacant period ratio is 50%: ON
for 0.5 second and OFF for 0.5
second.
The vacant period ratio is 90%:
ON for 0.9 second and OFF for
0.1 second.
6 Flashing at 0.5 Hz The period is 2 seconds and

ON for 1 second and OFF for 1
second.
C.2.3 Common Indicators

The common indicators on the front board and the rear board are shown in Table C-2.
Table C-2 Common Indicators
Common Color Meaning Description

Indicator
Descrip-
tion
OOS Dual-color Board service alarm Different alarms with flashing of different
indicator frequencies.
(red/green)
OK Dual-color Health status Indicates the health status of the board.

indicator indicator
(red/green)
C-2

Appendix C Running Information Description
Common Color Meaning Description

Indicator
Descrip-
tion
H/S Blue Hotswap indicator Indicates the hotswap status
ACT Dual-color The active/standby Indicates the active/standby status.

indicator status indicator
(red/green)
HOST Dual-color Running/Alarm The green indicator describes the running
indicator indicator status of the board; the red indicator
(red/green) describes alarms of the board.
C.2.3.1 ACT Indicator Description

The ACT indicator is the M/S indicator, indicating that whether a service is running on the
current boards. The description of ACT is shown in Table C-3.
Table C-3 ACT Indicator
Status Name ACT Status Description
Working Constantly ON (Green) 1. No backup is configured for

the board.
2. If the board is in 1+1 backup
mode and the ACT indicator
is ON, the board is active.
3. If the board is in 1:1 backup
mode and the ACT indicator
is ON, the board is active, or
resources (APS and optical
interfaces) of the board are
active.
Backup Constantly OFF If the board is in 1+1 backup

mode, the board is standby.
Switchover Flashing at 1 Hz Active/Standby changeover
C.2.3.2 HOST Indicator Description

HOST is the Run/Alarm indicator. The description of the HOST indicator is shown in Table
C-4.
C-3

Table C-4 HOST Description
Status Name RUN Status Priority Description
Initial status Constantly OFF 1 The board is in initial

status
Normal running Flashing at 1 Hz 2 The board is running

(green) normally.
BOOT is running Flashing at 5 Hz 3 BOOT is running

properly (green) properly (the version is
being downloaded or
the version download
fails).
General alarm Flashing at 1 Hz (red) 4 The service is

applicable (in M/S
switchover).
Critical alarm Flashing at 2 Hz (red) 5 Media plane network

port disconnects.
6 HW disconnects
7 The link with OMP

disconnects.
8 The version does not

match the hardware
configurations.
Fault that shall be Flashing at 5 Hz (red) 9 The version download

restored fails.
10 The board self-check

fails.
11 Support startup fails.
12 Obtaining logic address

fails.
13 The basic process

power-on fails or times
out.
14 The initialized core

data district fails.
C.2.3.3 H/S, OOS and OK Indicators

H/S, OOS and OK indicator status is described in Table C-5.
C-4

Appendix C Running Information Description
Table C-5 H/S, OOS and OK Indicators
H/S (Blue) OOS (Red/Green) OK (Red/Green)

Status Phenome- Duty Phenom- Duty Phenom- Duty Meaning
non ratio enon ratio enon ratio
Solid Board Power

Off – – Off –
green ON reset
Hardware
address error
Red light
(The rear
Off – Off – flashes at 50%
board does
5 Hz
not have this
state).
The board is
inserted to
Constantly Red, con- the bottom of
– – Off –
ON stantly on shelf, but the
extractor is
not closed.
Board
inserted into
Power-on
the bottom
and
Flashes with Red, con- of the shelf,
Power-off 90% – Off –
1 Hz stantly on extractor
closed,
power ON
requested.
Ready to
Red, con-
Off – – Off – Power ON the
stantly on
board.
Board
Off – Off – Reserve – Powered ON
successful
Board
Flashes at 1 extractor is
90% Reserve – Reserve –
Hz opened for
power off.
Flashes at 1 Board ready

90% Reserve – Reserve –
Hz to shut down,
Red light
Alarm Reserve – Reserve – flashes at 50% Alarm occurs
1 Hz
C-5

H/S (Blue) OOS (Red/Green) OK (Red/Green)

Status Phenome- Duty Phenom- Duty Phenom- Duty Meaning
non ratio enon ratio enon ratio
Run Reserve – Green light The card

Reserve – flashes at 50% is running
1 Hz normally.
• Reserve: indicator status not changed.
C.2.4 Board Power ON

The indicator status for board power ON is shown in Table C-6.
Table C-6 Indicator Status for Board Power ON
Status HOST (Green) ACT (Green) OK (Green) Description
ACT indicator is lit under the

following circumstances:
Constantly No backup board
Normal Flashes at 1 Hz ON Flashes at 1 Hz 1 1 back up.
C.2.5 Hardware Reset

The hardware reset indicator is shown in Table C-7.
Table C-7 Hardware Reset Indicator
Status OOS (Green) H/S (Blue) OK (Green)
Hardware reset Lit Not lit Not lit
C-6

Figures
Figure 2-1 TROUBLE SHOOTING FLOW................................................................. 2-2
Figure 3-1 All Table Synchronization ......................................................................... 3-3
Figure 3-2 SNTP and System Log Configuration....................................................... 3-5
Figure 5-1 Troubleshooting flow of the board loading fault ........................................ 5-2
Figure 6-1 Service Stream at Interface A Radio Network Control Layer Under TDM
Mode ...................................................................................................... 6-2
Figure 6-2 Service Stream at Interface A Radio Network Control Layer Under IP
Mode ...................................................................................................... 6-2
Figure 6-3 Troubleshooting Procedure for Communication Failure at Interface
A............................................................................................................. 6-3
Figure 6-4 Service Stream of Gb Interface Radio Network Control Layer in TDM
mode .................................................................................................... 6-10
Figure 6-5 Service Stream of Gb Interface Radio Network Control Layer in IP
mode .................................................................................................... 6-11
TDM Mode............................................................................................ 6-13
IP Mode ................................................................................................ 6-14
FLOW IN ATM MODE ........................................................................... 6-15
FLOW IN IP MODE............................................................................... 6-16
Figure 6-10 IU/IUR INTERFACE COMMUNICATION FAULT Troubleshooting
FLOW ................................................................................................... 6-17
Figure 6-11 Radio Network Layer Control Plane Signaling Procedure (ATM) ........... 6-24
Figure 6-12 Transport Network Layer Control Plane Signaling Procedure ............... 6-24
Figure 6-13 Radio Network Layer Control Plane Signaling Procedure (IP) .............. 6-24
I
Figures

Tables
Table 1-1 Safety Symbols Description....................................................................... 1-2
Table 4-1 COMMON PHENOMENA AND CAUSE OF CLOCK FAULT ...................... 4-1
Table 4-2 COMMON SYMPTOM AND CAUSE OF COMMUNICATION LINK
FAULT...................................................................................................... 4-3
Table 4-3 COMMON PHENOMENA AND CAUSE OF SHELF MANAGEMENT
FAULT...................................................................................................... 4-4
Table C-1 Statuses of Common Indicators ............................................................... C-2
Table C-2 Common Indicators.................................................................................. C-2
Table C-3 ACT Indicator........................................................................................... C-3
Table C-4 HOST Description.................................................................................... C-4
Table C-5 H/S, OOS and OK Indicators ................................................................... C-5
Table C-6 Indicator Status for Board Power ON ....................................................... C-6
Table C-7 Hardware Reset Indicator ........................................................................ C-6
III
Tables

Glossary
AAL2
- ATM Adaptation Layer type 2
ATM
- Asynchronous Transfer Mode
BSS
- Base Station System
CCP
- Communication Control Port
CN
- Core Network
CPU
- Central Processing Unit
CS
- Circuit Switched
FTP
- File Transfer Protocol
GSM
- Global System for Mobile Communication
IC
- Integrated Circuit
IP
- Internet Protocol
MTP3B
- B-ISDN Message Transfer Part level 3
NBAP
- Node B Application Part
NCP
- Node B Control Port
NNI
- Network Node Interface
OMCR
- Operations & Maintenance Center–Radio
PS
- Packet Switched
V
RLC
- Radio Link Control
SCTP
- Stream Control Transmission Protocol
SGSN
- Service GPRS Supporting Node
SLC
- Signaling Link Code
SSCOP
- Service Specific Connection Oriented Protocol
SSF
- Session Service Function
TCP
- Transfer Control Protocol
WCDMA
- Wideband Code Division Multiple Access
VI

GU - TS3051 - E01 - 0 ZXUR 9000 UMTS Troubleshooting 90P

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GU - TS3051 - E01 - 0 ZXUR 9000 UMTS Troubleshooting 90P

Uploaded by

Copyright:

Available Formats

ZXUR 9000 GU

Dual Mode Controller

Revision No. Revision Date Revision Reason

R1.0 2012-07-12 First edition

Chapter 2 Overview .................................................................................... 2-1

Chapter 3 Troubleshooting for Operation and Maintenance

Chapter 4 Troubleshooting for Hardware Problems ............................... 4-1

Chapter 5 Troubleshooting for Software Initiation Problems ................ 5-1

Chapter 6 Troubleshooting for System Communication Problems....... 6-1

Appendix A Troubleshooting Record Table............................................ A-1

Appendix C Running Information Description ....................................... C-1

What Is in This Manual

Chapter 2, Overview Introduces the ZXUR 9000 GU troubleshooting procedure.

Appendix A, Troubleshooting Introduces the Troubleshooting Record Table.

Appendix C, Running Introduces the indicators for ZXUR 9000 GU.

1.1 Prerequisites for Maintenance Personnel

1.2 Safety Symbols

SJ-20101108155417-007|2011-08-17(R1.0) ZTE Proprietary and Confidential

Table 1-1 Safety Symbols Description

Safety Symbol Meaning

Universal alerting symbol: General safety

Electrostatic: Device may be sensitive to static

Electric shock: There is a risk of electric shock.

High temperature: Surface is hot and may cause

Laser: Beware of strong laser beam.

Microwave: Beware of strong electromagnetic

SJ-20101108155417-007|2011-08-17(R1.0) ZTE Proprietary and Confidential

1.3 Safety Specifications

Do shut off power supply before connecting or disconnecting a power cable.

SJ-20101108155417-007|2011-08-17(R1.0) ZTE Proprietary and Confidential

Hoisting Heavy Objects

SJ-20101108155417-007|2011-08-17(R1.0) ZTE Proprietary and Confidential

l Ensure a proper hoisting capability of the hoister when disassembling heavy

SJ-20101108155417-007|2011-08-17(R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20101108155417-007|2011-08-17(R1.0) ZTE Proprietary and Confidential

2.1 Trouble Shooting Flow

SJ-20101108155417-007|2011-08-17(R1.0) ZTE Proprietary and Confidential

Figure 2-1 TROUBLE SHOOTING FLOW

2.1.1 Information Collection

l Fault complaints from user or customer centre

SJ-20101108155417-007|2011-08-17(R1.0) ZTE Proprietary and Confidential

2.1.2 Fault Analysis

2.1.3 Fault Location

The correct fault location requires experiences and knowledge.

2.1.4 Fault Elimination

2.1.5 Fault Record

2.1.6 Experience Sharing

SJ-20101108155417-007|2011-08-17(R1.0) ZTE Proprietary and Confidential

2.2 Trouble Shooting Principles

2.3 Common Methods to Locate Faults

2.3.2 Analysis of Status Indicator

SJ-20101108155417-007|2011-08-17(R1.0) ZTE Proprietary and Confidential

2.3.3 Analysis of Performance

2.3.4 Analysis of Signaling Tracing

2.3.5 Operation Log Query

2.3.6 Analysis with Instruments and Meters

2.3.7 Testing and Self-Looping

SJ-20101108155417-007|2011-08-17(R1.0) ZTE Proprietary and Confidential

2.3.8 Plugging/Unplugging and Pressing

2.3.9 Configuration Analysis and Modification

SJ-20101108155417-007|2011-08-17(R1.0) ZTE Proprietary and Confidential

2.3.10 Comparison and Replacement