ZXG10 B8018 Troubleshooting

Goal

 After learning this course, you will:

 Master the troubleshooting principles of GSM BSS.
 Master common fault analysis and location methods of
GSM BSS.
 Master the troubleshooting methods of general faults of
B8018.
 Master the troubleshooting methods of typical faults of
B8018 through case studies.
Contents

 Troubleshooting Principles
 Fault analysis and location methods
 General troubleshooting methods of hardware
faults
 Fault troubleshooting cases
Equipment Operations

 Strictly follow the operation rules of the

equipment.
 Put on anti-static wrist straps before touching any
hardware of the equipment.
 All operations that is outside the daily
maintenance scope are forbidden.
 The following operations are strictly forbidden: plug/unplug, reset or
switch between the equipment at will; load or modify data at will; modify
data in the NMS database at will.
Board Operations

 Wear the antistatic strap when handling the

boards;
 Before plugging/unplugging or replacing key
critical boards, prepare sufficient personnel and
boards to deal with unexpected events;
 Check spare materials and parts regularly to
ensure their sufficient stocks and integrity and
prevent them from molding;
 The damaged parts should be marked and kept in
antistatic bags, separated from spare parts.
Data Maintenance
 Data synchronization and modification should not be done in
the daytime; such operations should be performed in the
low-traffic hours (i.e. midnight);
 Operations involving mass data submission should be
conducted in the low-traffic hours (i.e. midnight) if possible;
 Before data modification, data backup should be made.
During data modification, timely records should be made.
After data modification, the backup data should not be
deleted until it is confirmed that the system is running
normally in a certain period of time (normally one week);
 Periodically backup all data for any emergency needs;
 All databases, especially the performance measurement
and alarm databases should be observed periodically (once
every two weeks). If the database size is too large, please
delete old useless data to avoid disk overflow errors.
Permission management
 Only one super administrator is allowed in system management.
 The rights and passwords of the OMC are managed by the super
administrator.
 The rights to log on to the OMC server and client shall be set by
different levels.
 The passwords to log on to the server and client shall be changed
periodically.

 The maintenance person in charge of the equipment room provides different rights
for the maintenance personnel with varied levels, and allocates accounts and
passwords.
•
The super administrator has the highest rights of the system, and can
perform all operations;
•
The senior operator has no right of user management, but has the
following rights: data configuration and modification, diagnostic test,
performance measurement, and alarm query and status query.
•
The operator only has alarm query and status query rights.
Virus Prevention
 The maintenance personnel cannot change network settings
and other settings on the O&M server and client without
guidance from the technical personnel.
 Do not use external disks or CDs on the O&M server and
client without permission from the technical personnel.
 Do not run programs that are not related with O&M
operations on the server and client. Do not play games on
terminal computers.
 Install legal copies of the antivirus software for each client
and never deactivate the real-time detection function. Keep
the virus database updated regularly each week.
 Install original antivirus software for the server with NT
system and never deactivate the real-time detection
function. Keep the virus database updated timely (weekly).
Reporting Faults
 The maintenance personnel should settle the
problems and faults detected as soon as possible.
If they find serious problems, they should report to
the responsible supervisor immediately and
contact the local ZTE office. The whole fault
dealing process should be recorded in detail.
Contents

 Troubleshooting Principles
 Fault analysis and location methods
 General troubleshooting methods of hardware
faults
 Fault troubleshooting cases
Alarm and operation log view
 Viewing alarm and operation logs is the first method to be
adopted when a fault is detected by the maintenance
personnel. It is implemented through the alarm
management and operation log view interface of the BSS
operation & maintenance subsystem iOMCR.
 Through the alarm management interface, we can observe
and analyze alarm messages reported from each NE such
as current alarms, historical alarms and general
notifications. In this way, we can detect any fault during
network running in time and then locate, isolate and
remove it.
 By viewing operation logs in user management, we can
investigate modifications on system parameters, locate the
relevant responsible terminal and operator as well as
detect faults caused by individual operations in time.
Analysis of status indicator
 Indicator status analysis is a common method
used by the maintenance personnel when a fault
is found. With this method, we can locate and
remove faults by observing the indicator status on
each board panel in the rack.
 This method requires the maintenance personnel
to be familiar with statuses and their meanings of
indicators on each board.
Performance Analysis
 It is implemented through the performance management interface of
the BSS operation & maintenance subsystem iOMCR. Through this
interface, maintenance personnel can perform BSS performance
management and signaling tracing.
 With the performance management interface, users can create
different performance measurement tasks, generate different
performance reports and understand different performance indices of
BSS. By analyzing the information, maintenance personnel can detect
load distribution in the network and adjust network parameters in time
to increase the network performance.
 Through the signaling tracing interface, we can trace signaling
involved in BSS (including Gb port signaling), thus facilitating
consulting of different signaling flows in the debugging and
maintenance processes as well as detection of problems in the
signaling interworking process.
Analysis with instruments and meters
 In the BTS maintenance process, the
maintenance personnel can use auxiliary
instruments such as the test MS, signaling
analyzer and error analyzer for fault analysis,
location and removal.
Plugging/unplugging and pressing
 When detecting a board fault, we can loosen the
fixation screw in the front panel and plug or unplug
the board and external interface connector. In this
way, we can remove faults caused by poor
contact or processor faults.
 Pressing the cable connectors after power-off may
also eliminate faults caused by insecure contact.
Comparison and replacement
 The comparison method means to compare a
possible faulty board with a board at the similar
position in the system (for example, a board in the
same slot in a multi-module system) from aspects
such as the running status, jumper and connection
cables. We can determine whether the board fails
through comparison.
 Replacement means to replace a possible faulty
board with a standby part or another board of the
same type running normally in the system, so as
to determine if the board is faulted.
Isolation method
 When a part of the system fails, it can be isolated
from other relevant boards or racks to determine
whether the fault is caused by mutual influence.
Contents

 Troubleshooting Principles
 Fault analysis and location methods
 General troubleshooting methods of hardware
faults
 Fault troubleshooting cases
Analysis and handling:
 Based on our on-site maintenance experience, most
hardware faults are related to the following reasons:
 Insecure connection of the RF jumper from the DTRU to the CDU
(including loose jumper and broken cables)
 Poor heat dissipation (including damaged fans, long-time failure of
air-conditioners, and non-installed blank modules)
 Insecure of the 8-core socket of the carrier (including poor contact
or oxidization)
 Poor antenna feeder connection (including unfastened feeder or
poor waterproof conditions)
 Site breakdown caused by E1 transmission reasons (Most E1
reasons are transmission reasons, including engineering quality
problems such as poor contact of the E1 interface )
Solution
 The AEM standing wave alarms are mainly caused by poor contact
of the antenna feeder and poor contact of the RF jumper from the
DTRU to the CDU. Generally, it can be solved by examining cable
or antenna feeder connection.
 Link breakdown between the carrier and the CMB HDLC is mainly
caused by poor contact of the 8-core socket of the carrier. It can be
solved by improving the 8-core socket.
 The LAPD breakdown alarm is usually related to transmission. It
can be solved by checking transmission quality and the
engineering quality of the equipment room.
 If the TCH assignment has a high failure rate, check the RF
jumpers.
 Poor heat dissipation may cause various faults, especially the life
shortening or even damage of the power amplifier and the built-in
power source of the carrier. Therefore, alarm and temperature
related alarms should be addressed in the earliest time possible.
General Operations
 If the following cases occur, the RF jumper from the DTRU
to the CDU should be replaced:
 The heat-shrinkable tube is loose.
 The RF jumper from the DTRU to the CDU is over-twisted.
 The RF jumper from the DTRU to the CDU has an obvious feeling
of heat upon hand touch.
 During the check of E1 lines, the following conditions of the
BNC connectors should be improved:
 Exposure of copper at the connector end.
 Open joints, dry joints, missed-out joints, wrong joints, or reverse
joints in welding soldering.
 The soldering joint has lumps, or is not fully filled.
General Operations
 To check fan faults, you can check the air
ventilation volume of the third-level carrier shelf at
the back door of the BTS rack. If there is no wind
or a weak wind, check if the fan subrack is
plugged in position or the power cable is well
connected. Replace the fans immediately if any of
them is faulty.
General Operations
 To fix the CDU and the N-type head of the
cabinet top jumper with a spanner.
General Operations
 To fix the SMA head of the RF jumper between
the DTRU and the CDU with a small spanner.
Contents

 Troubleshooting Principles
 Fault analysis and location methods
 General troubleshooting methods of hardware
faults
 Fault troubleshooting cases
Fault troubleshooting cases
 Learn the fault troubleshooting cases and
conduct discussions.