GSM-BSS - II - 09 - 200909 ZXG10 BSS (V3) System Maintenance Criterion 185 PDF

ZTE GSM-BSS Products
After-Sales Competency Certification

Training Manual
ZXG10 BSS (V3) System Maintenance
Criterion
Course Objectives
Grasp normal running features of ZXG10 BSS (V3) equipment;
Understand the common fault information feedback methods;
Understand the emergency fault troubleshooting methods
Understand
the
routine
BSS(V3)
equipment
maintenance
criterion
of
ZXG10
Contents
1 BSS Maintenance Specification ................................................................................................................ 1
1.1 Guide to ZXG10-BSS System Maintenance ..................................................................................... 1
1.1.1 Emergent Fault Handling Flow .............................................................................................. 1
1.1.2 Emergent Fault Notification and Update Stipulations ............................................................ 1
1.1.3 Flow of Emergency Maintenance........................................................................................... 3
1.2 Emergent Handling Solution for ZXG10-BSS Major Fault .............................................................. 8
1.2.1 Features of Normal System Running ..................................................................................... 8
1.2.2 Emergent Handling Flow for System Abnormality .............................................................. 10
1.2.3 Critical solution .................................................................................................................... 24
1.3 Feedback Method of ZXG10-BSS Fault Information ..................................................................... 41
1.3.1 Necessary Factors for Fault Feedback ................................................................................. 41
1.3.2 Feedback data required by BSC faults and its collection methods....................................... 42
1.3.3 Feedback data required by CS service faults and its collection methods ............................. 43
1.3.4 Feedback data required by PS service faults and its collection methods ............................. 45
1.3.5 Feedback data required by ISMG faults and its collection methods .................................... 46
1.3.6 Feedback data required by Minos faults and its collection methods .................................... 47
1.3.7 Feedback data required by upper OMCR faults and its collection methods ........................ 48
1.3.8 Feedback data required by PI report faults and its collection methods ................................ 48
1.3.9 Feedback data required by alarm report faults and its collection methods........................... 49
1.3.10 Feedback data required by BS equipment faults and its collection methods ..................... 50
1.4 Methods to Get System Records ..................................................................................................... 51
1.4.1 Get Device Printing File....................................................................................................... 51
1.4.2 Get ZDB File ........................................................................................................................ 52
i
1.4.3 Get Data Backup ztd File from ISMG ..................................................................................53

1.4.4 Get Software Setting .............................................................................................................54
1.4.5 Get Alarm File ......................................................................................................................55
1.4.6 Get Notification File .............................................................................................................58
1.4.7 Get 1 Hour's Performance Data Before and After Fault .......................................................61
1.4.8 Get Tracing Signal at Interface A..........................................................................................64
1.4.9 Query Dynamic Data at Interface A......................................................................................66
1.4.10 Get Tracing Signal at Interface Abis ...................................................................................67
1.4.11 Query Dynamic Data at Site ...............................................................................................69
1.4.12 Query BVC and NSVC State ..............................................................................................69
1.4.13 Trace PS Service Signal ......................................................................................................70
1.4.14 Get Operation Log of Preset Machine ................................................................................71
1.4.15 Check Whether Overstocked Data Exists ...........................................................................71
1.4.16 Query Disk Space ...............................................................................................................72
1.4.17 Get ISMG Printing File.......................................................................................................72
1.4.18 Get ISMG Profile ................................................................................................................73
1.4.19 Get Operation Log at Client................................................................................................73
1.4.20 View System Time Zone .....................................................................................................75
1.4.21 View ISMG version ............................................................................................................75
2 Routine Maintenance................................................................................................................................77
2.1 Overview .........................................................................................................................................77
2.1.1 Purpose of Routine Maintenance ..........................................................................................77
2.1.2 Classification of Routine Maintenance .................................................................................77
2.1.3 Precautions............................................................................................................................78
2.2 Daily Maintenance ...........................................................................................................................80
2.2.1 Equipment Room Environment Check .................................................................................80
ii
2.2.2 BSC Running Status Check.................................................................................................. 84

2.2.3 BTS Check ......................................................................................................................... 121
2.2.4 Inspection and Maintenance on Indoor/Outdoor Cables .................................................... 124
2.3 Weekly Maintenance ..................................................................................................................... 124
2.3.1 Cleaning Equipment ........................................................................................................... 124
2.3.2 BSC Check ......................................................................................................................... 124
2.3.3 BTS Check ......................................................................................................................... 141
2.3.4 Inspection and Maintenance on Indoor/Outdoor Cables .................................................... 143
2.4 Monthly Routine Maintenance...................................................................................................... 143
2.4.1 Inspection and Maintenance in equipment room ............................................................... 143
2.4.2 BSC Check ......................................................................................................................... 143
2.4.3 BTS Check ......................................................................................................................... 148
2.4.4 Indoor and Outdoor Cables Check ..................................................................................... 149
2.5 Quarterly Maintenance .................................................................................................................. 149
2.5.1 Equipment Room Maintenance .......................................................................................... 149
2.5.2 BSC Check ......................................................................................................................... 153
2.5.3 BTS Check ......................................................................................................................... 157
2.5.4 Indoor and Outdoor Cables Check ..................................................................................... 171
iii
1 BSS Maintenance Specification

Knowledge Point
This chapter describes ZXG10-BSS (V2) system maintenance specification under
different circumstances, including routine maintenance, emergent fault handling folw,
and feedback methods.
1.1 Guide to ZXG10-BSS System Maintenance

1.1.1 Emergent Fault Handling Flow
When an emergent fault (level-1 fault) occurs to the user equipment, the fault must be
eliminated in the shortest time to recover the system, minimize the accident loss and
protect the customer interests ultimately. In view of occurrence of the emergent fault
and the actual handling status, the emergent fault occurs abruptly and generates a big
influence, so the site personnel is confronted with a pressure of troubleshooting. The
troubleshooting capabilities are limited when an emergent fault occurs as a result of
different technical levels of the site personnel, so powerful advanced technical support
at home must provide effective remote instructions. In addition, after an emergent fault
occurs, the site response time is affected by the journey and transportation, so remote
technical support appears indispensable. Fast site response from the office and remote
diagnosis support of the sub-center form the solid support mode in case of emergent
fault. When necessary, it is preferable to start the emergent fault handling team of the
Product Division level, fully dispatch company resources to handle the emergent fault
with full efforts, shorten the fault lasting time, and avoid unnecessary deterioration of
the fault due to insufficient use of resources.
1.1.2 Emergent Fault Notification and Update Stipulations

1.1.2.1 Emergent Fault Notification
Emergent fault notification:
Upon reception of the emergent fault complained by the customer, any
department or member must report it to the Customer Support
1
ZXG10 BSS (V3) System Maintenance Criterion
Upon reception of the emergent fault report, the Customer Support Center must
immediately inform the on-duty manager of Office and the on-duty manager of
Sub-center
After receiving the emergent fault report, the on-duty manager of Office should
appoint the relevant technical support engineer of Office within 5 minutes, and
inform the vice manager of Office within half an hour.
After receiving the emergent fault report, the on-duty manager of Sub-center
should appoint the remote support engineer within 5 minutes, and inform the
secretary of Customer Service Dept. within half an hour.
After receiving the emergent fault complaint for half an hour, the Customer
Service Support Center should trace to specify the Office and Sub-center
technical engineers. If the fault is not solved yet, inform the team leader of the
emergent fault handling team and the manager of Customer Service Support
Center
1.1.2.2 Emergent Fault Update

Once finding an equipment fault and judging it is an emergent fault, notify relevant
members to handle it. If the fault is not solved in a certain period, report it to the
relevant department leader in the following time limit:
If the emergent fault is not recovered within two hours after emergent support,
the vice manager of Office must report the information to the vice engineering
president of Marketing Division, and the secretary of Product Customer Service
Dept. must report it to the vice president of Product Quality Dept.
If the emergent fault is not recovered within four hours, the vice engineering
president of Marketing Division must report the information to the general
manager of Marketing Division, and the vice president of Product Quality Dept.
must report it to the general manager of Product Division.
If the emergent fault is not recovered within six hours, the person in charge of
ZTE Customer Service Support Center must report the information to the senior
vice president of marketing, senior vice president of product R&D and the
companys quality strategy workgroup.
Chapter 1
BSS Maintenance Specification
1.1.3 Flow of Emergency Maintenance

Emergency maintenance contains the following several steps, as shown in Figure 1.1-1:
Start
Collecting
fault infor
Is RAN fault?
Inform relevant
persons
Y
Exceptional
records table
Record
exceptions
Locating and
analyze fault
reason
Emergency Note
N
Can be solved?
Y
Emergency
assistance
Restore
service
Observe service
Troubleshootin
g records
Info records
End
Figure 1.1-1
Flow of Emergency Maintenance
1. Collecting fault information

On emergency fault, collect the fault information about the following aspects:
3
1 Confirm whether power supply works properly.

2 Determine the fault scope. In combination with user claims, check the call
information from different offices on performance measurement platform at CN
side, to quickly determine the fault scope, in whole network or individual BSC.
If it is whole CN office, immediately inform relevant persons to handle it based
on the flow of CN emergency maintenance.
3 Check the hardware of BSC system. View whether the status of panel indicators
on different boards is proper; check whether the status of different radio
resource cells and physical connections or links with other NE are proper. If all
are ok, immediately inform the staff related with equipment NE (such as
transmission, core network) to do troubleshooting.
4 Confirm whether it is caused by software and data. For data problem, attempt to
quick conditional restore. If check it through operation logs, confirm whether
the system is down due to wrong modification or deletion.
Note
It is key to determine the fault scope, to distinguish the fault at radio side or network
side, to quickly restore the system.
Based on practical measurement, over 50% significant faults are caused by human.
2 Record exceptions
In the process of starting emergency restore scheme or troubleshooting
according to this manual, you shall record the running version and exceptional
information based on Fault Feedback Report. Especially, record and archive the
information collected in previous step "Collecting Fault Information".
Field maintenance staff shall fill in corresponding portion of fault feedback
report based on actual conditions.
Table 1.1-1 Fault Feedback Report

Source unit, field contact
person, and his/her contact
information (filled in by
who gives the feedback)
Chapter 1
Version number and patch
omcr/iomcr/minos:
number (filled in by who
BSC/iBSC:
gives the feedback)
BTSBTS:
Fault time, symptom, and

description (filled in by who
gives the feedback)
Description
procedure
of
and
field
handling
(filled in by who gives the
Do feedback based on "Fault information collection and feedback"
feedback)
Field data feedback (filled in
by who gives the feedback)
Fault
analysis
Do feedback based on "Fault information collection and feedback"
and
preliminary comments
Deadline time (Filled in by
general
engineer
from
customer service depart.)

Handled by (Filled in by the
R&D staff)
Field prevention methods

(Filled in by the R&D staff)
Analysis
and
comments
(Filled in by the R&D staff)

Version planning to solve
the problem (Filled in by the
R&D staff)
Caution
Records on exceptions are very useful for emergent assistance and post fault analysis,
so everyone shall do exceptional records.
3 Analysis and localization
Determine fault reason and its measures based on the methods provided in
5
"Emergency Troubleshooting Scheme".

4 Emergency assistance
If the service can not be restored or significant system fault occurs after doing
emergency troubleshooting scheme, immediately call 24h ZTE service hotline to
get remote support and field technical support.
1 Service hotline
ZTE provides 7X24 technical support service. Call ZTE Customer Support
Center Hotline.
7X24 Technical Service

China Hotline:
800-830-1118
400-830-1118
Website: Support.zte.com.cn
Email: 800@zte.com.cn
Figure 1.1-2
ZTE Service Hotline
2 Remote support
Depending on the information provided by service hotline, technical experts will
remotely log in the fault point. For normal problem, the expert will guide the
customer to solve it through telephone. For complicated problem, ZTE assigns
maintenance experts to provide field technical support.
3 Field Technical Support
After the technical expert arrives, he/she will do emergency maintenance
measures to restore the communication as soon as possible.
5 Restore Service
If the fault reason can no be located and service can not be restored quickly
according to the methods provided in this manual, to quickly restore the system
6
Chapter 1
service, attempt to switchover, reset, and replace the board if necessary. For
significant maintenance operation, coordination and confirmation shall be gotten
first from the customer side.
Caution
First back up system data prior to restoring service.
To change hardware configuration, such as cable connection or board slots, record
the current conditions.
It is necessary to record any step and symptoms encountered on field.

6 Service observation
After restoring the service, further inspection on the system is required to check
whether the whole system is restored. Check the items based on Routine
Maintenance. Meanwhile, assign some staff on-duty at service peak time.
7 Information records
After restoring the service, collect fault recovery steps and analyze fault reasons
based on Troubleshooting Record Table. If emergency assistance is started, you
shall feedback to ZTE service hotline, to enable ZTE provide the better
after-sale service.
Table 1.1-2
Troubleshooting Records
Equipment Name
Fault Time
Equipment ID
YYYYMMDDHH
Settlement Time
Fault type:
Fault source:
YYYYMMDDHH
Symptom:
Fault Solution:
Summary:
Person on duty:
Handled by:
1.2 Emergent Handling Solution for ZXG10-BSS Major Fault

1.2.1 Features of Normal System Running
1.2.1.1 Judging Criteria for Normal OMCR Status
The client can log in to the server.
The performance statistic report is normal.
Alarm management and dynamic management can be viewed normally.
Configuration management can normally configure data.
1.2.1.2 Judging Criteria for Normal BSC Status
1.
Check the running status of the BSC through OMCR.

Boards in the alarm management interface of OMCR have no alarm.
Chapter 1
The active/standby statuses of all the boards in the alarm management interface
of OMCR are normal.
In the dynamic data management of OMCR, all the A interface circuits are
normal (except the A interfaces manually blocked or not configured with links).
In the dynamic data management of OMCR, al the channels of all the BSs work
normally, without blocking phenomenon.
The MP communication link of the OMCR server with each foreground module
OMCR is normal (checked through MPINFO).
2.
Observe running conditions of indicators on the boards at the BSC rack side.
None red indicator on the boards is on.

For two MPs of each module, one has its active indicator on, and the other has
its standby indicator on. The running indicator flashes slowly at frequency (on
for 1 second and then off, the same as below). The active and standby slots are
consistent with the OMCR background display.
The running indicator of MTP communication board (SS7 board with panel ID
as COMM, configured at slots 17 and 18 of the control layer) flashes fast.
The running indicator of MPPP communication board (each PP communication
board of MP and BSC, with the panel ID as ECOM) flashes slowly.
For the two BOSN boards, one has its active indicator on, and the other has its
standby indicator on. The running indicator flashes slowly.
For the two SYCK boards, one has its active indicator on, and the other has its
standby indicator on. The running indicator flashes slowly. The reference
selection and hold indicator is always on.
The DSNI board running indicator flashes slowly. The active indicator of DSNI
in slots 13 and 14 is always on. The active and standby indicators of DSNI board
in slots 15~22 are always on alternatively, that is, they are in the active/standby
status.
The running indicator of Lapd communication board (BTS signaling processing
board) flashes slowly.
COMI boards work in the active/standby mode, with the active indicator always
9
on.
GPP boards work in the active/standby mode, with the active indicator always
on.
The running indicator of TIC board flashes slowly, and the E1 indicator flashes
fast.
1.2.1.3 Judging Criteria for Normal BTS Status
No alarm appears at the OMCR alarm management site.
The OMCR statistic performance index data are normal.
The channel status and occupation of the OMCR dynamic management BTS are
normal.
Boards at the BTS side have no alarm, and all the indicators are in normal
conditions.
1.2.2 Emergent Handling Flow for System Abnormality

1.2.2.1 Handling Flow for OMCR Abnormality and Interruption
[Symptom]
The client fails to log on to the server.
[Handling flow chart]
If the clientserver
communication is
normal
Check network
configuration and
physical
connection
If the client
harddisk space is
full
Delete surplus
files
Eliminate
possibilities of virus
infection of the
client and operating
system abnormality
If the server space

is full
Delete surplus
files and logs
Kill virus and

reinstall the
operating system
If the database runs

normally
Omcps check if the

process is normal
Exit all OMCR

processes
Exit all OMCR

processes
Exit the database
Restart the database
Restart OMCR
Restart OMCR
SUN server restarts
Restart the database
Start OMCR
Figure 1.2-1
Handling Flow for OMCR Abnormality and Interruption

10
Chapter 1
[Flow Description]
1. Check if the client-server communication is normal.
1)
Ping the client and the server IP addresses to check whether the communication
between them is normal.
2)
If the client or the server cannot be pinged through, check whether the client and
the server are securely connected.
3)
Check whether the configuration for the router is correct.
2.
Check the hard disk space of the client.

Make sure that the harddisk where the system client software is installed and the
system tray have enough space. If the space is insufficient, delete excessive files.
3.
Kill virus on the client and check if the operating system is normal.
1)
Use the latest anti-virus software to check and kill the virus on the client.
2)
Check whether the operating system is normal. If not, reinstall the operating
system or install the client software on another computer.
4.
Check the hard disk space of the server.
1)
Execute the command df-k to check whether the disk space of any partition of
the server overflows.
2)
If yes, delete excess log files. For example, delete the log files under the
directory $OMCHOME/tmp/log and the temporary files under the directory
$OMCHOME/tmp/ftp (note: the VERSION directory under it cannot be
deleted).
5.
Check if the OMCR processes are normal.
1)
Execute the command omcps to check whether the processes of the OMCR
server are running normally.
2)
If there are some of the processes only or there is no output, execute the
command ps Cuomc to check where there is residual OMCR process. If yes,
execute the command kill-9 to stop the OMCR residual process.
6.
Check whether the database is running normally.
1)
Check whether the database is started normally.

11
2)
Check whether the database can be accessed normally.
3)
If the database is running normally, restart the OMCR.
4)
If the database is running abnormally, quit the database.
5)
Restart the database.
6)
Restart the OMCR.
7.
If the fault cannot be removed through the above operations, restart the server.
1)
Shut down and restart the server.
2)
Start the database.
3)
Start the OMCR.
1.2.2.2 Handling Flow for BSC Abnormality and Interruption

[Symptom]
Call failure in the sites under all the modules
Call failure in the site under a module
Call failure in the site of the left or right unit of a module.
Call failure in the site under a LAPD board
12
Chapter 1
If the MP of each
module runs
normally
If SYCK runs
normally
MP active/
standby
switchover
Replace MP
SYCK board
active/standby
switchover
Replace SYCK
board
Call failure in the

sites attached to
all the modules
If this module
runs normally
Call failure in the
sites attached to
this module only
MP active/
standby
switchover and
replacement
If MPMP, MPPP and

MTP boards run
Normally
If BOSN board runs

Normally
BOSN board active/

standby switchover
Replace BOSN board
Check if BIPP
boards of left and
right units run
normally
Check if COMI
board runs
normally
Restart BSS system
Plug/unplug board a
the same time
Replace the
corresponding board
Check if the
corresponding
DSNI board runs
normally
COMI board
active/standby
switchover
BIPP board
active/standby
switchover
Reset active/standby
MP of each board at
the same time
Check if BOS
board runs
normally
BOSN board
active/standby
switchover
DSNI active
standby
switchover
Check if BIPP
board of the
corresponding
unit runs normally
Call failure in
sites attached at
the left or right
unit of the same
module
BIPP board
active/standby
switchover
Check if the
corresponding
LAPD runs
Normally
Call failure in
sites attached to
the same LAPD
Reset LAPD
Replace LAPD
Figure 1.2-2
Handling Flow for BSC Abnormality and Interruption
[Flow Description]
1.
Call failure in the sites under all the modules
1)
Check if the active and standby MPs of each module work normally.
The abnormal statuses of the MP board indicators are described in Table 1.2-1.
Table 1.2-1
Category
Board in the
control layer
Board
MP board
Location
2
Abnormal Statuses of MP Board Indicators
Name
HL2
Note
Red
indicator
Meaning
Board fault
Working Mode
It is always on when the
board is faulty.
If the running indicators of the active and standby MPs in each module fail to
flash slowly, or the red indicator is always on or flashes, manually switch over
13
the active and standby MPs. If the standby MP can function as the active one,
check after 2 or 3 minutes if it works normally.
If the switchover fails, and the standby MP works normally (the running
indicator is flashing slowly, the standby indicator is always on, and the fault
indicator is off), reset the active MP directly. Now, the standby MP will become
the active one automatically. Check whether the active MP works normally.
2)
Check whether the SYCK board is running normally.

The abnormal statuses of the SYCK board indicators are described in Table
1.2-2.
Table 1.2-2
Category
Board
Board in the
network
SYCK
switching
board
layer
Abnormal Statuses of SYCK Board Indicators
Locati
Name
on
1
HL1
HL2
Note
Meaning
Working Mode
Green
Running
Always off:
indicator
status
Abnormal
Red
indicator
Board fault
Always on: Board

fault
If almost the red indicators of all the boards are on, and the alarm of board fault
is generated at the background alarm management, switch SYCK boards. If the
fault cannot be removed, replace the SYCK board.
3)
Check whether the BOSN (DSN) board is running normally.

The abnormal statuses of the BOSN board indicators are described in Table
1.2-3.
Table 1.2-3
Category
Board
Location
1
Board in
network
switching layer
Abnormal Statuses of BOSN Board Indicators
Name
HL1
Note
Meaning
Green
Running
indicator
status
Working Mode
Always on/off: Abnormal
Slow flashing: The communication
BOSN
board
between the board and the

2
HL2
Red
Board
upper-level is faulty. If it is not
indicator
fault
recovered in a certain period, the

board will be reset. On: The board
is faulty, such as loss of clock.
14
Chapter 1
If the network board indicator is abnormal or the BOSN alarm management

displays the alarm of a network board, then:
Reset the standby network board. Check whether the standby network board
works normally (the running indicator is flashing slowly; the standby indicator
is always on; the fault indicator is off) in two or three minutes after the running
indicator of the standby network board flashes slowly.
Reset the active network board. At that time, the standby network board
becomes the active one automatically.
If the standby network board cannot work normally for a long time (five
minutes), check the cables on its backplane or replace the board.
4)
Check whether the MPMP, MPPP and MTP boards are running normally.
The abnormal statuses of the COMM (MPPP/MPMP) board indicators are
described in Table 1.2-4.
Table 1.2-4
Category
Abnormal Statuses of COMM (MPPP/MPMP) Board Indicators
Board
Location
Name
Note
Meaning
Working Mode
On together with the
1
Board in
the control
layer
HL1
Green
Running
fault indicator: Board
indicator
status
fault, for example,

clock loss
COMM board
(MPPP/MPMP)
On together with the

2
HL2
Red
Board
running indicator:
indicator
fault
Board fault, for

example, clock loss
Table 1.2-5 lists the abnormal statuses of the COMM (MTP2) indicators.
Table 1.2-5
Category
Board in
the
control
layer
Abnormal Statuses of COMM(MTP2) Indicators
Board
Location
Name
COMM
HL1
HL2
board
(MTP2)
Note
Meaning
Working Mode
Green
Running
Flashing
indicator
status
obstructed
Red
indicator
Board fault
slowly:
SS7
link
Flashing slowly: The board is

faulty, such as loss of clock
If the MPMP, MPPP or MTP fails, pull the faulty board out and then insert it in.
15
If the fault cannot be removed, replace the faulty board.

5)
If the fault cannot be removed yet, restart the BSS system.
Restart of the BSS is of paramount importance. Therefore, inform ZTE local

Representative Office before restart.
After resetting the MP, pull out the LAPDs (ensure that only two LAPDs are
inserted). After the system operation is stable, insert the remaining LAPDs one
by one.
Note:
After the resetting, 8 minutes are needed for the system to restore normal conversations
due to existence of a protection period.
2.
Call failure in the site under a module
1)
Check if the active and standby MPs of the module work normally.
If the running indicator of the active MP is not flashing slowly or the red
indicator is on or flashing, then:
Press the changeover button to manually perform active-standby MP

changeover.
If the standby MP can function as the active one, check after 2 or 3 minutes if it
works normally.
If the switchover fails, and the standby MP works normally (the running
indicator is flashing slowly, the standby indicator is always on, and the fault
indicator is off), reset the active MP directly. Now, the standby MP will become
the active one automatically. Check the current active MP. If it does not work
normally, reset it after the MP reset just now resumes normal operation.
2)
Check whether the BIPP board is running normally.

Table 1.2-6 lists the abnormal statuses of the BIPP indicators.
Table 1.2-6
Board
Location
Name
Abnormal Statuses of BIPP Indicators
Note
Meaning
16
Working Mode
Chapter 1
Fast flashing: If the red indicator is flashing

1
HL1
Green
Running
slowly together, it indicates interruption of
indicator
status
HDLC communication.
BIPP
2
HL2
Red
Board
indicator
fault
Flashing slowly: HDLC communication

interruption
On: The board is faulty, such as loss of clock
If the BIPP fails, perform active-standby BIPP changeover.

Replace the faulty BIPP.
3)
Check whether the COMI board is running normally.

The abnormal statuses of the COMI board indicators are described in Table
1.2-7.
Table 1.2-7
Category
Board
Loca
Nam
tion
1
Boardin the
network
switching
layer
Abnormal Statuses of COMI Board Indicators
HL1
Note
Meaning
Green
Running
indicator
status
Working Mode
Flashing
fast:
Communication
failure with MP Always on/off:

Abnormal
DSNI/
Flashing slowly: Communication
COMI
between this board and the upper
board
HL2
Red
Board
level is faulty. If it is not
indicator
fault
recovered in a certain period, the

board will be reset. On: The board
is faulty, such as loss of clock
If the COMI fails, perform active-standby BIPP changeover.

Replace the faulty COMI.
4)
Check whether the corresponding DSNI board is running normally.

The abnormal statuses of the DSNI board indicators are described in Table
1.2-8.
Table 1.2-8
Category
Board
Location
Name
Abnormal Statuses of DSNI Board Indicators

Note
17
Meaning
Working Mode
HL1
Green
Running
indicator
status
Flashing
fast:
Communication
failure with MP
Board in the
network
DSNI/
switching
COMI board
layer
HL2
Red
Board
indicator
fault
level is faulty. If it is not recovered

in a certain period, the board will be
reset.
On: The board is faulty, such as loss
of clock
If the DSNI fails, perform active-standby BIPP changeover.

Replace the faulty DSNI.
5)
Check whether the BOSN (DSN) board is running normally.

The abnormal statuses of the BOSN board indicators are described in Table
1.2-9.
Table 1.2-9
Category
Board
Location
Name
HL1
Board in
the
network
switching
Abnormal Statuses of BOSN Board Indicators
Note
Meaning
Green
Running
indicator
status
Working Mode
Slow
BOSN
board
flashing:
The
communication
between the board and the upper-level is

2
HL2
layer
Red
Board
faulty. If it is not recovered in a certain
indicator
fault
period, the board will be reset.

On: The board is faulty, such as loss of
clock
If the network board indicator is abnormal or the BOSN alarm management

displays the alarm of a network board, then:
Reset the standby network board. After the running indicator of the network
board flashes slowly, wait for two or three minutes.
After the standby network board is normal (the running indicator flashes slowly;
the standby indicator is on; the fault indicator off), reset the active network
board. At that time, the standby network board becomes the active board
automatically.
18
Chapter 1
If the standby network board cannot work normally for a long time (five
minutes), check the cables on its backplane or replace the board.
3.
Call failure in the site under the left or right unit of a module
Table 1.2-10 lists the abnormal statuses of the BIPP indicators.
Table 1.2-10
Board
Location
Name
Note
Abnormal Statuses of BIPP Indicators

Meaning
Working Mode
Fast flashing: If the red indicator is flashing
HL1
Green
Running
slowly together, it indicates interruption of
indicator
status
HDLC communication.
BIPP
2
HL2
Red
Board
indicator
fault
Flashing slowly: HDLC communication

interruption
On: The board is faulty, such as loss of clock
If the BIPP fails, perform active-standby BIPP changeover.

Replace the faulty BIPP.
4.
Call failure in the site under an LAPD board

Table 1.2-11 lists the abnormal statuses of the COMM (LAPD) indicators.
Table 1.2-11
Category
Board
Location
Abnormal Statuses of COMM (LAPD) Indicators
Name
Note
Meaning
Working Mode
Flashing slowly together with the
1
Board in the
control layer
HL1
Green
Running
indicator
status
fault indicator: Board fault, for

example, clock loss
COMM
board
(LAPD)
2
HL2
Red
Board
indicator
fault
failure with MP
Flashing slowly together with the
running indicator: Board fault, for
example, clock loss
Reset the LAPD.
19
If the fault cannot be removed yet, replace the LAPD board.

1.2.2.3 Handling Flow of BTS Interruption
[Symptom]
The site in OMCR alarm management is displayed in gray.
The site is interrupted, and call cannot be connected.
Eliminate faults
rising from
transmission and
BTS side
If the
corresponding E1
indicator of TIC
board is normal?
If E1 indicator of
BTS side is
normal?
Check if there is
ransmission alarm
at transmission
NM
Coordinate with
BSC side to check
transmission,
perform loopback
at each side
If site runs normally

after data change, it
indicates data
abnormal
Change a set of
configuration data
Eliminate faults
arising from BSC
and data
Jump to this site

with normally
running data of
the same type
Reconfigure data
Figure 1.2-3
Test E1
transmission
Test site
grounding
resistance
Transmission
error rate- <
10 6
Grounding
esistance < 5
ohm
It does not work yet, it

means LAPD timeslot
fails
If the
board fails
Replace the
faulty board
Doubt fault of
some timeslots
of transmission
Redo data and
skip original
occupied
timeslots
If all timeslots on this

LAPD board fail
Reconfigure data
without deleting
original data
Replace this LAPD

board
Handling Flow of BTS Interruption
[Flow Description]
1.
Check E1 indicator flashing condition of the TIC board.

The abnormal statuses of the TIC board indicators are described in Table 1.2-12.
Table 1.2-12
Category
TC
board
unit
Board
TIC/DTI
board
Location
Name
HL1
Abnormal Statuses of TIC Board Indicators

Note
Meaning
Green
Running
indicator
status
20
Working Mode
Flashing fast: Communication with
MP is faulty.
Chapter 1
Category
Board
Location
Name
Note
Meaning
Working Mode
HL2
Red
indicator
level is faulty. If it is not recovered

Board fault
in a certain period, the board will

be reset.
On: The board is faulty, such as
loss of clock
TC
board
unit
TIC/DTI
board
HL3
HL4
HL5
2.
HL6
Green
indicator
Green
indicator
Green
indicator
Green
indicator
DT1
DT2
DT3
DT4
Always on: Alarm

Off: E1 interface not initialized
Always on: Alarm
Always on: Alarm
Always on: Alarm
Check E1 indicator status at the site side.

Table 1.2-13 lists the abnormal statuses of the indicators on the CMM module
panel.
Table 1.2-13
Name
Abnormal Statuses of Indicators on CMM Module Panel
Meaning
Color
PWR
Power indicator
Green/red
RUN
Running indicator
Green
System
SYN
synchronization
Clock indicator
1. The red indicator is on/an alarm exists

2. The red indicator is off/power failure or other reasons
The red indicator is on or flashes system abnormal
1. The red indicator flashes (4 Hz)/E1 out of frame
Green/red
mode indicator
CLK
Abnormal Status
2. The red indicator is on/E1 line broken or

disconnected
Green/red
The red indicator is on/clock failure

1. The red indicator flashes (1 Hz)/LAPD link broken
STA
Status indicator
Green/red
2. The red indicator flashes (4 Hz)/HDLC link broken

3. The red indicator is on/other alarms related to
temperature, clock and frame number
If E1 is abnormal, check transmission by means of self-loop, and check if the

opposite end is in the normal state. For self-loop at the BTS side, and the E1
21
indicator at the BTS side should be normal. Fro self-loop at the BTS side, the
TIC board indicator at the BSC side should be normal.
3.
Check the bit error rate of E1 transmission.

Sue a bit error meter to check the bit error rate of transmission, which should be
less than 10 6.
4.
Check the grounding resistance of the site.

Check the grounding resistance of the site with an earth resistance tester. It
should be less than 5 ohm.
5.
Check if there is nay faulty board.

Replace the faulty board with the replacement method.
6.
Check if there is nay faulty board.

Replace the faulty board with the replacement method.
7.
Eliminate the data problem at the BSC side.
Jump to the faulty site with the normally running data of the same model and
same site type. If it is normal, possible the site data is faulty. Delete the data of
the faulty site, and reconfigure it.
If data reconfiguration does not work, the corresponding LAPD timeslot may get
faulty. It is advisable to reconfigure a set of data without deleting the original
faulty data. If still fails, try to reset the LAPD board and replace the LAPD
board.
Note:
Resetting and replacing of LAPD board may lead to temporary interruption of other
sites allocated at this LAPD board.
There is another possibility that some timeslots of transmission are obstructed,
so the site is interrupted. Skip over the timeslot occupied by the original site via
the transparent channel mode, and then configure site data.
1.2.2.4 Handling Flow of BSC Overload
[Symptom]
The CPU overload alarm of MP occurs.
22
Chapter 1
The average load value of MP is above 60 in performance statistics.

Make statistics of performance report and check traffic

of corresponding period
For MP load rise

caused by traffic
increase
MP load cannot be
lowered yet
Adjust
corresponding
parameters and
reduce
corresponding load
Unplug
corresponding
LAPD board or
disconnect some
BTSs
Figure 1.2-4
Check if MP runs
normally
View history
alarms of MP
Return
corresponding log
file
Switch over
active/
standby MP or
replace MP
Mobile Division
analyzes
accordingly and
provides a
solution
Handling Flow of BSC Overload
[Flow Description]
1.
Analysis of traffic data of the performance statistic report
1)
For the high MP load caused by increase of traffic, adjust the corresponding
parameters.
Modify access parameter to reduce the signaling flow accessed each time at the
MS, improve the access success rate, and reduce malicious redialing times.
Modify location update parameter to reduce periodical location update times.
Modify handoff parameter to reduce handoff times and reduce measurement
report handling times.
2)
If the above operations fail to work yet, unplug some LAPD boards or
disconnect some BSs.
2.
Analysis of traffic data of the performance statistic report, too high MP load not
caused traffic increase
Check the MP running status and history alarm.

If anything is abnormal, attempt to reset and switch over the active and standby
MPs, or replace the MP.
23
Return to MP and print the log. Feed it back to ZTE Mobile Division to make
log analysis and provide the corresponding solution.
1.2.3 Critical solution

1.2.3.1 Common Handling Methods
For emergent fault, first determine fault scope, then find fault point, and do emergency
maintenance measures for different fault points.
1 Determine the fault scope
Fault information is the evidence to determine the fault scope. After getting
emergency fault information, the maintenance staff shall quickly determine the
fault scope by collecting network management information. In general, you can
ask and query dynamic data to collect network management alarms, to quickly
determine the fault scope.
Attention: determine the fault scope in conjunction with the information from
core network.
You shall learn the content in Table 1.2-14 while collection fault information by
asking.
Table 1.2-14
Collection fault information by asking
SN
What to ask
Fault time and symptom
Service affecting range, some sites, a BSC, or whole network
Any significant actions at BSC side prior to the fault
Any significant action at core network or about transmission prior to the fault
Finished measures
2 Determine fault point based on fault scope

Table 1.2-15 lists the reasons and fault points for some faults for reference.
Table 1.2-15
Fault Symptom
Client can not login
to the server due to
Determine Fault Point
fault scope
Fault reason/possible position
One or more OMC servers can not login
24
IP transmission network fault;

OMC server fault
Chapter 1
Fault Symptom
fault scope
Fault reason/possible position
OMC exceptions
All sites under BSC can not call properly
All sites under a BSC can not call properly
BSC
voice
service
improperly
Site interrupted, can

not call
Fault at core network

Fault on MP, clock, or level I switching
board
All sites under a module can not call properly
MP module fault
All sites under a BIPB can not call properly
BIPB board fault
All sites under a LAPD board can not call properly
LAPD board fault
Bidirectional mute/unidirectional connection/noise
BIPB or DRTB board fault; level I
within a large area
switching board fault

Transmission fault at Abis
Large area or individual site interrupted
Fault at BTS side;

Data Configuration Error
MP CPU overload;
average
above
MP
load
60
in
Traffic increasing dramatically;
One or more MP overload
MP MP fault
performance
measurement
Transmission problem
Exceptional PS service at all sites under BSC
PS service exception
GIPB/UPPB
board
fault
software
running improperly
PS data problem
Exceptional PS service at some sites
1.2.3.2 iSMG&Minos exception and interruption handling

[Symptom]
Login from the client to the server fails.
[Handling Flow]
25
Data error
The software is running abnormally
Whether
client
and
server
are
ok
Check network
configuration
&
physical
connections
Learn it is not
caused
by virus
at
client
Kill
virus and
the
re-install
OS
Whether the
disk space is
client
full
at
Delete
files
additional
Whether the
disk space is
full at server
Check whether the
process is ok
Check whether the

is ok
database
Delete
logs
additional
Quit the iOMCR

iOMCR
process and restart
iOMCR
it
Quit
the iOMCR
iOMCR
process,
restart
database
and
iOMCR
iOMCR
Restart SUN
server
Sun server restarts
Database
starts
iOMCR
iOMCR
starts
Figure 1.2-5
iOMCR exception and interruption handling flow
[Description of Handling Flow]

1 Check whether the client communicates properly with the server
1 PING IP addresses of the client and server to check the communication.
If PING successfully but with high packet lost and network intermittent, check
whether the IP of other machine is repeated, dhcp function is enabled on any
intranet machine, or the physical connections of different NEs are ok.
2 If ping fails, check whether the physical connection between client and server is
improper.
If the server is in different subnetwork from the client, use netstat r to check
whether the server router and client are reachable. Otherwise, add more routers
to add routes: route add ip address -netmask subnet mask gateway address. For
example:
#route add 192.168.0.0 -netmask 255.255.255.0 10.11.201.254
Add a route to 192.168.0.0 segment, gateway address is 10.11.201.254. The
route added in this way will not exist after system restarts, so write proper route
config command into start script, such as the end of /etc/rc3 file.
3 Check whether the relevant router configuration is correct.
2 Use other clients to login the server for attempt.
If log in, it is client problem; if not, it is server problem.
26
Chapter 1
3 Check whether the disk is full at client.

Ensure the system disk and the disk with client software have sufficient free
space. If free space is less, delete additional files and release more space.
4 Is client attacked by virus? Check whether operating system is normally
running.
1 Search and kill virus by using the newest virus library.
2 If OS is exceptional, reinstallation is required, or find another computer to install
client software.
5 Check whether the disk is full at server.
1 Run the df -k command to check whether the disk space of any partition of the
Server overflows.
2 If no sufficient free space, use rm -r command to delete unnecessary files or
unused folders. Such as the log files under $OMCHOME/log.
$rm 123.txt
$rm r 1234
6 Check whether the server process is ok.
1 Check whether the server process is running.
Use ps u gomcr to check iOMCR process in real-time. For instance, below
section indicates iOMCR process is ok:
bash-3.00$ ps -ugomcr
PID TTY
TIME CMD
5844 ?
00:00:00 run-linux.sh
5851 ?
00:00:00 ftpserver-linux
5855 ?
00:18:44 java
5872 ?
00:00:00 java
For Minos server, you also can use similar methods to check process condition:
bash-3.00$ ps u omc
2 Check whether the server log is printing:
27
Logs about iSMG and Minos server are stored under $OMCHOME/log. Use the
following command to check log output:
bash-3.00$ tail -f server-20090112-0935-00020.log
2009-01-12
15:16:03,108
INFO
[class
com.zte.ums.zxgomcr.emf.fm.bsc.MsgsDispatcher] Receive msg: -2

2009-01-12
15:16:03,108
INFO
[class
com.zte.ums.zxgomcr.emf.fm.bsc.MsgsDispatcher] Receive link break message.

If iOMCR log has not any output, use ps ef|grep java to check whether omc
user has remained java process, and use kill 9 command to exit from iOMCR
remained java process. Such as, if java process id is 1209, the command to quit
java is as follows:
kill -9 1209
The system may have more java processes, kill all these processes.
7 Check Whether the Database Is Running Normally
1 Check whether the database has been started.
Use $ps ef|grep oracle command to view database process, output example as
follows:
oracle
1273
1 15 ?
0:00 ora_q000_gomcr
oracle
1275
1 15 ?
0:01 ora_q001_gomcr
oracle
1338
1 15 ?
0:07 oraclegomcr (LOCAL=NO)
iomcr 13141 13127
0 21:11:39 pts/3
0:00 grep oracle
oracle 13134
0 21:10:42 ?
0:00 ora_j000_gomcr
oracle 12274
0 16:44:02 ?
oracle
1273
1 15 ?
0:00 ora_q000_gomcr
oracle
1275
1 15 ?
0:01 ora_q001_gomcr
oracle
1338
1 15 ?
iomcr 13141 13127
oracle 13134
0 21:11:39 pts/3
0 21:10:42 ?
28
0:00 grep oracle
0:00 ora_j000_gomcr
Chapter 1
oracle 12274
0 16:44:02 ?
0:47 oraclegomcr
(LOCAL=NO)
2 Check whether it can connect to database, use sqlplus /nolog to log in under
oracle user, and then input connect sys/oracle as sysdba to connect. If it is
connected, it indicates connection success.
$ sqlplus /nolog
SQL*Plus: Release 10.2.0.1.0 Production on Thu Jan 17 16:42:43 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> connect sys/oralce as sysdba
Connected.
SQL>
3 If database is running properly, only restarting OMC server program is ok.
4 If database is running improperly, quit the database.
5 Restart the database.
Connect database based on the methods introduced in (2), then use "shutdown
immediate" to close ORACLE, then connect database, use startup command to
start the database. Note that ORACLE user may close ORACLE while he logs in
sqlplus.
Connected.
SQL>shutdown immediate
Start ORACLE
Connected.
SQL>startup
6 Restart iOMCR
8 If above procedures do not function, restart the server.
1 The server shutdowns and restarts.
29
It is recommended OMCR process and database shall be closed prior to

restarting.
The command to restart the server is (Only root user can shutdown the server):
#/usr/sbin/shutdown -y -g 0 -i 6 or #init 6
2 Start the database.
3 Start the OMCR program.
1.2.3.3 iBSC Exception and Interruption Handling
[Symptom]
All sites under all modules can not call properly.
All sites under a module can not call properly.
All sites under a BIPB can not call properly.
All sites under a LAPD board can not call properly.
Bidirectional mute/unidirectional connection/noise within a large area.
[Handling Flow]
All sites under

all modules
can not call
properly
Is CMP/OMP
is ok
Is CLKG ok?
Do CMP/OMP
switchover
Replace MP
Do CLKG
switchover
Replace CLKG
If all are mute,

check if level I
switching board is
ok
Check if fiber
connection is
loosen, Rx/Tx
indicator are ON
normally, and
switchover the
board
Is CMP Ok?
The sites under
this module can
not call
normally
Reset CPU on
CMP
Replace or
switchover
active/standby
CMP
Reset active/
standy CPU of
this module
30
Restart BSS
Reset CMP and

OMP
Chapter 1
Check if BIPP
board of the
corresponding
unit runs normally
Call failure in
sites attached at
the left or right
unit of the same
module
BIPP board
active/standby
switchover
Check if the
corresponding
LAPD runs
Normally
Call failure in
sites attached to
the same LAPD
Reset LAPD
Replace LAPD
Bidirectional
mute/
/
unidirectional
within
connection
a large area
DRTB
Check DRTB
DSP
and its DSP
BIPB
Check BIPB
DSP
and its DSP
DRTB
Reset/replace
DRTB
DRTB
BIPB
Reset/replace
BIPB
BIPB
Figure 1.2-6
Check resource
frame and level 1
switching
connection
UIMUGLI
Check fiber
connections of
UIMU and GLI,

Rx/Tx
indicators,
and
fiber switchover
condition
iBSC exception and interruption handling flow

1 All sites under all modules can not call properly.
1 Check whether all MPs are running properly (check foreground indicator and
background alarm): iBSC is discrete architecture, without service center module,
so if call fails in whole netowrk, check whether all MPs are improper, do
switchover for the OMP. It is recommended that OMP switchover shal be done
through background or foreground (for the methods of foreground switchover,
refer to the steps of CMP switchover below).
Log in iOMCR client -> View -> Dynamic Data Management -> Primary Config
Set -> BSC function -> BSC device config -> BSC rack: check whether the
color or status of MP board is ok, click MP board to select normal switchover.
31
2 Check whether all SPBs (no.7 processing board) are ok (check indicator at
foreground and alarm at background, if all are ok, check no.7 signaling status in
dynamica data management), namely, link at interface A.
Log in iOMCR client -> View -> Dynamic Data Management -> BSC Dynamic
Data Management: do status query on PCM management at interface A, trunk
circuit management at interface A, NSVC management, N7 signaling status
management, to confirm whether the link is ok.
3 Check whether the indicator on these boards are normal. Reset all MPs
(including active/standby CPU of CMP/OMP) at background.
4 If the fault continues, restart BSS system. Attention: it is a significant operation
to restart BSS system, so you shall inform local ZTE office in advance.
5 If call is connected but without voice heard, check whether the fiber connection
for level 1 switching is loosen and Rx & Tx indicators are ok, do switchover for
PSN board if necessary.
2 All sites under a single module can not call properly.
1 Check whether active/standby CMP for this module is running properly.
If the running indicator of active CMP does not flash slowly, red indicator keeps
on, and red indicator flashes for this module, do switchover for CMP board.
Switchover operation shall be done at background. If the background can not
finish switchover, you can do the action at foreground.
Set -> BSC function -> BSC device config -> BSC rack: click MP board to
select normal switchover.
Perform manual active/standby CMP switchover by pressing the switchover key
of the active CMP. If the standby CMP can be switched over to active CMP, wait
for 2~3 minutes and then check whether the active CMP is running properly.
If the switchover fails and the standby CMP is running normally (running
indicator slowly flashing, standby indicator normally on and fault indicator off),
directly reset the active CMP. In this case, the standby CMP will be
automatically switched over to the active one. Check whether the new active
CMP is ok, if not ok, reset current active CMP after the previous CMP is ok.
32
Chapter 1
2 If active & standby CMPs are running improperly, reset them directly to check
whether it can start properly.
3 All sites under a BIPB cannot call properly.
Check whether BIPB board is running properly. Reset the board if necessary.
4 All sites under a LAPD cannot call properly.
Check whether LAPD board is running properly. Reset the board if necessary.
5 Bidirectional mute/unidirectional connection within a large area.
1 If voice problem occurs in whole network, check whether DRTB and its DSP are
working properly through alarms and notifications, reset/replace the DRTB.
2 If voice problem occurs at some base stations, check whether the BSs are
centralized on a BIPB board; check whether BIPB and its DSP are working
properly through alarms and notifications, reset/replace the BIPB.
3 If the voice problem occurs in whole network, and DRTB board does not restore
after resetting, it may be cause by level 1 switching frame. Check whether PSN
and GLI have exceptional alarms and notifications, check the fiber connection
and reset/switchover the board.
1.2.3.4 Site Interruption Handling flow
[Symptom]
Site interrupts in iOMCR alarm management.
[Handling Flow]
33
Eliminate faults
rising from
transmission and
BTS side
If the
corresponding E1
indicator of TIC
board is normal?
If E1 indicator of
BTS side is
normal?
Test E1
transmission
Test site
grounding
resistance
If the
board fails
Doubt fault of
some timeslots
of transmission
Check if there is
ransmission alarm
at transmission
NM
Coordinate with
BSC side to check
transmission,
perform loopback
at each side
Transmission
error rate- <
10 6
Grounding
esistance < 5
ohm
Replace the
faulty board
Redo data and

skip original
occupied
timeslots
If site runs normally

after data change, it
indicates data
abnormal
Change a set of
configuration data
Eliminate faults
arising from BSC
and data
Jump to this site

with normally
running data of
the same type
It does not work yet, it

means LAPD timeslot
fails
Reconfigure data
without deleting
original data
Reconfigure data
Figure 1.2-7
If all timeslots on this

LAPD board fail
Replace this LAPD
board
Site Interruption Handling Flow

1 Check E1 indicator on DTB board.
Refer to Table 1.2-16 for the abnormal running status of the DTB board
indicator.
Table 1.2-16
Name
Color
DTB Board Indicators

Description
Meaning
RUN
green
Running indicator
Refer to Table 1.2-17
ALM
Red
Alarm indicator

ON: Indicates that the micro switch is
turned on; the board is not inserted to the
correct position, software version is not
downloaded.
ENUM
Yellow
Board
extraction
Indicator
Flashing at 5 Hz: Indicates the micro switch

alarm; during the boards running, the
micro switch is turned on and has alarm.
Flashing at 1 Hz: Indicates that the board
can be extracted; during the boards
running, the micro switch is turned on, the
board, which is standby or does not use
34
Chapter 1
Name
Color
Description
Meaning
resource, can be extracted.

OFF: Indicates that the micro switch is
normal.
ACTACT
green
Active/standby
ON: Indicates the board is active
indicator
OFF: Indicates the board is standby

OFF: indicates unconfigured database at this
E1/T1
Always ON: indicates configured database
L1~L32L1~L32
green
32xE1 Indicators
at this E1/T1 but E1/T1 disconnected

Flashing in the frequency of 1Hz (slowly
flash): indicates configured database at this
E1/T1 and E1/T1 is connected
Table 1.2-17
State name
RUN status
Running
Periodically
normally
flashing at 1 Hz
Alarm status
Periodically
flashing at 5 Hz
VERSION
Downloading
RUN/ALM Combination Meanings

Meaning
Always OFF
Normal running
Always OFF
Version being downloaded
Periodically
Periodically
flashing at 1 Hz
flashing at 5 Hz
Version download fails: the board

version is inconsistent with the
configuration.
RELEASE version indicates that the
Always ON
Always OFF
version download succeeds and the

version is being started.
Periodically
Always OFF
flashing at 5 Hz
Self-test fails
Always OFF
Alarm
running
faults
on
Board self-test failure.
Periodically
Operation support system startup
flashing at 2Hz
failure.
Periodically
Periodically
flashing at 5 Hz
flashing at 5 Hz
Periodically
Periodically
Basic process power-on failure or
flashing at 5 Hz
flashing at 2 Hz
timeout.
Periodically
Periodically
flashing at 5 Hz
flashing at 1 Hz
Periodically
Periodically
Version
flashing at 5 Hz
flashing at 0.5 Hz
inconsistent with the configuration.
Periodically
Periodically
Media
flashing at 2Hz
flashing at 5 Hz
disconnected.
35
Logical address obtaining failure.
Core data area initialization.

and
plane
hardware
communication
are
is
State name
RUN status
Alarm status
Meaning
Periodically
Periodically
flashing at 2Hz
flashing at 2Hz
Periodically
Periodically
flashing at 1 Hz
flashing at 2Hz
Periodically
Periodically
Active/standby changeover is being
flashing at 1 Hz
flashing at 1Hz
performed.
Always ON
Hardware clock is lost.
Periodically
flashing at 1 Hz
HW is disconnected.
Link break with OMP.
2 Check E1 indicator at site side

Table 1.2-18 lists the abnormal status of the indicators on the CMB module
panel.
Table 1.2-18
Indicator
Color
green/red
green
Name
Definition of CMB Indicators
Meaning
PWRPW Power
R
indication
RUNRU Running
N
indication
Working Mode
Green: normal
Red ON: alarm
Off: power failure or other causes
Green flash (4 Hz): Boot operation
Green flash (1 Hz): Application operation
Other: the system is abnormal
Green
BTS
synchronizati
3
green/red
SYNSY
on reference
process
Mode
indication
ON:
Abis
interface
network
synchronization clock
Green
flash
(1
Hz):
Network
clock
synchronization via SDH

Red flash (1 Hz): Alarm for E1 frame
out-of-synchronization
Red indicator On: E1 line is broken or
unconnected.
OFF: free oscillating
Green ON: network synchronization is in
green/red
CLKCL
Clock
locked status
indication
Green flash (1 Hz): Phase being locked

Red ON: clock fault
green
MSTMS Master/slave
Green ON: active status
Green OFF: standby status
indication
36
Chapter 1
Indicator
Color
Name
Meaning
Working Mode
OFF: normal running
Green flash (1 Hz): system initialization
(Low), see Note 3
Green flash (4 Hz): Loading software
green/red
STASTA
Status
Red flash (1Hz): LAPD link broken (High), see
indication
note 1
Red flash (4 Hz): HDLC link broken (Low),
see note 2
Red ON: all other alarms such as temperature,
clock and frame id
If E1 is abnormal, check the transmission by taking measures such as self-loop

and check whether the peer status is proper. Do self-loop at BTS side, and E1
indicator flashes properly at BTS side; Do self-loop from BTS side, and the
indicator on DTB board flashes properly at iBSC side.
3 Check BER of E1 transmission
Use BER meter to check transmission, the BER shall be less than 106.
4 Check the grounding resistance on the site.
Check grounding resistance by using earth resistance tester, less than 5 ohms.
5 Check whether any faulty board exists.
Replace the faulty board.
6 Check whether any faulty board exists.
Replace the faulty board.
7 Exclude the data problem at iBSC side
Jump to fault point by using the normal data for same model and site, if ok, the
data at fault point may be wrong, delete the data at fault point and re-configure
the data.
If you can not re-configure the data, wrong LAPD timeslot may exist, you can
re-configure a set of data and do not delete original fault data. If still not
working, try to reset/replace LAPD board.
Caution
37
To reset/replace LAPD board may cause temporary interruption of other sites allocated
on this LAPD board.
1.2.3.5 iBSC Overload Handling Flow
[Symptom]
MP CPU overload occurs; average MP load above 60 in performance measurement.
[Handling Flow]
Make statistics of performance report and check traffic

of corresponding period
For MP load rise

caused by traffic
increase
MP load cannot be
lowered yet
Adjust
corresponding
parameters and
reduce
corresponding load
Unplug
corresponding
LAPD board or
disconnect some
BTSs
Figure 1.2-8
Check if MP runs
normally
View history
alarms of MP
Return
corresponding log
file
Switch over
active/
standby MP or
replace MP
Mobile Division
analyzes
accordingly and
provides a
solution
iBSC Overload Handling Flow

1 Analyze traffic data in performance measurement report. It is found that MP
overload due to increasing traffic.
1 During MP overload, closely check the load of MP. If the load is increasing
dramatically or above 80%, manually block some carrier, or unplug some LAPD
or disconnect some sites. So the load can be reduced.
2 Adjust corresponding parameters while the MP load is lower.
Modify access parameters, to reduce the signaling traffic of each access on
mobile station, increase the ratio of access success, and reduce the number of
maligious redialing.
Modify location update parameters, and reduce the number of periodical
location update. Note that it shall be lower than the value configured by MSC, in
38
Chapter 1
conjunction with MSC.

Modify handover parameter and reduce the times of handover.
Change the value of preprocessing to 4 in measurement report.
2 Analyze traffic data in performance measurement report. It is found that MP
load higher while traffic remains same.
1 Check the operation of MP, and its historical alarms.
Log in iOMCR client -> View -> Alarm Management -> View Alarm -> Query
Historical Alarm.
2 If exception occcurs, try to do reset/switchover for active/standby MP, or replace
the MP.
Set -> BSC function -> BSC device config -> BSC rack: check whether the
color or status of MP board is ok, click MP board to select normal switchover.
3 Return MP to print the log, and feedback it to ZTE mobile depart for log
analysis.
1.2.3.6 Handling PS service exception
[Symptom]
Exceptional PS service at all sites under BSC
Exceptional PS service at some sites
[Handling Flow]
Does
transmission
alarm occur at
Gb
PS service is
abnormal for
All sites under
BSC
Check GIPB
alarm. If any,
do
troubleshooting
at transmission
and SGSN side
39
Is the board ok
at Gb
Reset/Replace
GIPB and
UPPB
Is PS
configuration data
proper
Check
interconnection
data at Gb and
PS service
specification
Is BVCI blocked
in the cell
Reset BVCI and

its service in
dynamic
management
PS service is
abnormal at
some sites
Is configuration
data proper in the
cell
Check BIPB,
UPPB, and its
DSP timeslot
Figure 1.2-9
Is BVCI blocked
in the cell
Reset BVCI and

its service in
dynamic
management
Flow of handling PS service exception

1 Exceptional PS service at all sites under BSC
1 Check whether GIPB board has transmission alarm, if yes, do troubleshooting
and inform SGSN side for cooperation.
2 Check the indicators on GIPB and UPPB panels, status of board operation; if
exception occurs, reset the board, and if the fault continues, replace the faulty
board.
3 Configure data inspection:
Check interconnection parameters at Gb with SGSN (NSE ID, NSVC ID,
BRCH, DLCI)
Check PS service configuration:
For BIPB board, check DSP timeslot configuration on UPPB board. The number
of timeslots configured on each DSP of UPPB board is over 160.
Check T3192/T3193 settings. T3193 value is higher that of T3192.
Check BVC flow control mode. For the equipment made by Huawei and MOTO,
it is 2 for flow control mode.
Check the burst packet size at Gb. the value of burst packet size = access rate
value * 640.
4 Query the status of BVCI in dynamic management. Reset the BVCI in all cells,
and perform BVCI signaling reset once.
2 Exceptional PS service at some sites
1 For BIPB board, check DSP timeslot configuration on UPPB board. The number
40
Chapter 1
of timeslots configured on each DSP of UPPB board is over 160.

2 Query the status of BVCI in dynamic management. Reset the BVCI in all cells,
and perform BVCI signaling reset once.
1.3 Feedback Method of ZXG10-BSS Fault Information

1.3.1 Necessary Factors for Fault Feedback
1.
Fault occurring time:

Describe the specific time when the fault occurs.
2.
Fault symptom
Describe the phenomenon observed when the fault occurs, including the board
status, dynamic status, alarms generated at the background, signaling, and call
status. These statuses provide the basis for site fault location and handling.
Provide the influence scope of the fault, for example, the whole BSC or a single
site.
When it is difficult to express the fault clear, copy the related picture, for
example, the channel status through dynamic observation, error prompt during
the operation and other contents that cannot be saved.
3.
Detailed operation procedure:

The troubleshooting steps on site and the time of each step
The operations that may cause the fault
For the operation performed at the server, record the operation process with the
file saving function of NETTERM.
To facilitate the query in the future, it is recommended that the operator raise the
habit of recording the operations performed on the server.
4.
System record data:

The system record data cover the system running status and problems occurred.
It is a major means to locate the system fault.
The system record data fall into:
41
Feedback data required by BSC faults

Feedback data required by CS service
Feedback data required by OMCR faults
Feedback data required by upper OMC faults
Feedback data required by GPRS faults
Feedback data required by PI report faults
Feedback data required by site faults
5 Fault feedback report
1.3.2 Feedback data required by BSC faults and its collection methods
The equipment mainly includes the following faults:
Board Cannot Get Started
Fault occurs during board operation
For feedback data required by BSC faults and its collection methods, refer to Table
1.3-1.
Table 1.3-1 Feedback data required by BSC faults and its collection methods
Purpose of Record
System feedback records required
The method to get system record
Indicators flashing can reflect

the
elementary
information
about the status of board
Indicator flashing on faulty board
operation.
Record
exceptional
cases
Printing files at foreground.
occurred during BSC operation
Exc_Omp.txt,Exc_pp.txt,EXCINFO
in foreground printings.
Exc_Omp.txt, Exc_pp.txt, EXCINFO files
Check board startup records
Board hardware information

Configuration information in
BSC, to learn configuration
information.
Get log files at foreground
Print the serial port information on board
Get board printing files at serial port of
startup
board
Board PCB number, serial number, board

DIP
ZDB file in active OMP at foreground.
ZDB file at background
42
Get board hardware information
Get ZDB File
Chapter 1
OMCR, to learn configuration
ZTD backup files in ISMG.
Get Data Backup ztd File
information.
Screenshot if board in-stock version,
Learn software settings about
general software version, and specified
the board
version settings. Foreground version file
Get Software Setting
records relever
Alarm file records all alarms in
Alarm file, picking up historical alarms and
the system.
current alarms during faults.
Notification
file
is
the
supplement of system alarm.
Notification file, picking up historical files

during the faults.
Different version has different

functions, so you shall return
Foreground and background version
feedback.
Get Alarm File
Get Notification File
Feedback shall be sent based on the version

of field records.
1.3.3 Feedback data required by CS service faults and its collection methods
The CS service mainly include the following faults:
Can not call or difficult to call during equipment operation
Call failure during interconnection at interface A
Degraded performance index for CS service
Other relevant problems with CS call
For feedback data required by CS service and its collection methods, refer toTable
1.3-2.
Table 1.3-2 Feedback data required by CS service and its collection methods
Purpose of Record
Indicators flashing can

reflect the elementary
information about the
status
of
board
Indidcator flashing information of all boards in iBSC and

the indicator showing exceptions.
operation.
Configuration
information in BSC, to
ZDB file in all active OMPs at foreground.
learn
ZDB file at background
configuration
Get ZDB File
information.
Configuration

43
Purpose of Record
information in OMCR,
to learn configuration
information.
Alarm file records all
Alarm file, picking up historical alarms within a week and
alarms in the system.
current alarms.
Get Alarm File
Notification file is the

supplement of system
Notification file, picking up historical files within a week.
KPI/PI/CS reports on the faulty day. Based on 15 minutes
Current performance data on
granularity, do measurement at cell and BSC levels.
faulty day
alarm.
You can find system
operation
state
in
performance statistics.
Signaling is a very
useful tool to locate
Get tracing signal at interface A

Get the signaling at interface A and Abis during fault.
questions.
Get tracing signal at interface

Abis
State of the link at

interface A.
If the problem is related with interface A or whole BSC,

you shall send feedback about dynamic state of the link at
interface A.
Channel state is another

path to judge system
state.
Query dynamic data at interface

A
If it involves calling faults at site, you shall return the

feedback information about dynamic site state, including
cell, carrier, channel, LAPD status, and resource pool
Query dynamic data at site
status at Abis.
CMP
and
board
printings are the most

useful data to learn the
reason causing service
Printings that feedback CMP and other service related
Get printings about CS service
board.
board
fault.
Record
exceptional
cases occurred during

BSC
operation
in
foreground printings.
Printing files at foreground.

Exc_Omp.txt,Exc_pp.txt,EXCINFO Exc_Omp.txt,
Get log files at foreground
Exc_pp.txt, EXCINFO files
Detailed record about

symptom
recorded
during CQT and DT
CQT and DT test records
test
Determine whether the
version
problems
has
known
Foreground
and
background
version
number
number/patch
Feedback shall be sent based on

the version of field records.
44
Chapter 1
1.3.4 Feedback data required by PS service faults and its collection methods
The PS service mainly include the following faults:
Interconnection faults at interface Gb
Can not do PS service during iBSC equipment operation
PS service has slow speed and unstable
Other relevant problems with PS service
For feedback data required by PS service and its collection methods, refer toTable
1.3-3.
Table 1.3-3 Feedback data required by PS service and its collection methods
Purpose of Record
Indicators flashing can

reflect the elementary
information about the
status
of
Indicator flashing for all boards in iBSC
board
operation.
Configuration
information in BSC, to
learn
Or ZDB file at background
configuration
Get ZDB File
information.
Configuration
information in OMCR,
to learn configuration
information,
used
BVC state in the cell and NSVC state on iBSC,
Query the information of NSVC/BVC
PD channel state in the cell
tranferring and PD channel state.
to
restore the environment.

BVC state in the cell,
NSVC state on iBSC,
and PD channel state in
the cell can determine
whether
the
resource
required by PS service is
available.
Signaling
useful
is
tool
very
to locate
questions.
For the fault related with PS service, you shall

send feedback about signaling about PS.
Alarm file records all
Alarm file, picking up historical alarms within
alarms in the system.
a week and current alarms.

45
Trace PS service signaling
Get Alarm File
Notification file is the

supplement of system
alarm.
granularity at cell and BSC levels.
printings
can
reflect
the
directly
problems occurred in the

process
of
within a week.
Pick up PS basic measurement at 15min
PS performance data.
These
Notification file, picking up historical files
Get PS basic measurement
Get printings about the board related with
PS service printing
PS service.
GPRS
operation.
PS service test records
can
reflect
the
fault
information in detail.
Determine whether the
version
has
known
problems
PS service test record (ping test results/ftp test

rate record)
Foreground
and
background
version
number/patch number
Feedback shall be sent based on the version

of field records.
1.3.5 Feedback data required by ISMG faults and its collection methods
The ISMG mainly include the following faults:
ISMG server/client program quits automatically.
ISMG Server Startup Failure
ISMG Client Cannot Log in
Legal inspection failure and foreground storage failure during data
synchronization
Data configuration failure
For feedback data required by ISMG faults and its collection methods, refer toTable
1.3-4.
Table 1.3-4 Feedback data required by ISMG faults and its collection methods
Purpose of Record
Reflect the disk condition
Record
the
conditions of ISMG.
operation
Check the disk space
Query Disk Space
Log files at background
Get log files at ISMG background.
46
Chapter 1
information.
BSC, to learn configuration
Or ZDB file at background (required on
information.
storage failure)
Important configuration in the
Background profile (deploy, /etc/hosts, oracle
system.
net profiles)
Record OMCR operations on

field.
Determine whether the version
has known problems
Operation Log
Get ZDB File
Get ISMG profile
Get operation log
Foreground and background version

Snagshot of the errors occurred during OMCR
Trouble snagshot
operation
1.3.6 Feedback data required by Minos faults and its collection methods
The Minos mainly include the following faults:
Minos server/client program quits automatically.
Minos Server Startup Failure
Minos Client Cannot Log in
Lower NE agent/NE can not start up or can not use properly
Other relevant problems with Minos
For feedback data required by Minos faults and its collection methods, refer to Table
1.3-5.
Table 1.3-5 Feedback data required by Minos faults and its collection methods
Purpose of Record
Reflect the disk condition
Check the disk space
Query Disk Space
Table space
Table space
Utilization of table space
Get log files at Minos background.
Background profile (deploy, oracle net profiles)
Get Minos profile
Record
the
operation
conditions
Important configuration in
the system.
The state of upper and lower
links
Conditions of Ping and ftp lower-level
47
Check Minos and ISMG link setup and

tranferring state
Different version supports
Foreground
and
background
version
different functions.
number/patch number at upper/lower level

Snagshot of the errors occurred during OMCR
Trouble snagshot
operation
1.3.7 Feedback data required by upper OMCR faults and its collection methods
The upper OMCR mainly include the following faults:
Real-time Alarms Report Abnormal
Upper OMCR can not collect all/part of performance and configuration data
The performance data collected at upper OMCR is different from that at local
(Minos, ISMG)
Other relevant problems with upper OMCR
For feedback data required by upper OMCR faults and its collection methods, refer
toTable 1.3-6.
Table 1.3-6 Feedback data required by upper OMCR faults and its collection methods
Purpose of Record
Confirm whether ZTE database
Query relevant fields from upper OMCR
has this content
database.
Reflect the symptom found by

upper OMCR
Record the operation conditions
of OMCR
Important configuration in the
system.
Learn Link establishment
Learn
specific
indices
different OMCR, and confirm

which OMCR has the problem.
Query upper OMCR table
The exceptions found by upper OMCR
Profile at background
Get Minos profile
Link setup with upper OMCR

of
Query specific indices (upper OMCR,

Minos, and ISMG)
Check link setup at Minos and upper

OMCR.
Current performance data on faulty day
1.3.8 Feedback data required by PI report faults and its collection methods
The PI report mainly include the following faults:
All/some performance indices can not be reported
48
Chapter 1
In normal case, the indices become great different.

Other relevant problems with PI report
For feedback data required by PI report faults and its collection methods, refer toTable
1.3-7.
Table 1.3-7 For feedback data required by PI report faults and its collection methods
Purpose of Record
Extract relevant performance

report
Performance indices during Minos and

ISMG faults, and mark the problem
column manually.
Alarm Notification
Alarm file and notification file during the
Get Alarm File
fault.
information.
For report generating problem,
it
can
record
relevant
information in the log.

Profile related with foreground
performance
Background setting related
OMP Zxg10.cfgZxg10.cfg in OMP

Nfsdev permission, shared nfs, user uid
Get zxg10.cfg File at foreground
View relevant NFSDev permission
with NFS
and gid
files in Nfsdev directory
files in Nfsdev directory
Check relevant files under NFS
Nfsdetect Nfsdetect log
Nfsdetect log
Check Nfsdetect process
OS environment variable
OS environment variable
Check OS environment variable
Check table space
Check on disk space
Query Disk Space

Configure foreground timezone, ISMG
Time zone setting
timezone, minos timezone, and client
Check system timezone
timezone
1.3.9 Feedback data required by alarm report faults and its collection methods
The alarm report mainly include the following faults:
Real-time alarms on ISMG and Minos can not report
Upper-level OMCR fails to collect real-time alarms.
The alarms reported by ISMG and Minos are inconsistent with actual equipment
49
status.
Other problems related with alarms.
For feedback data required by alarm report faults and its collection methods, refer
toTable 1.3-8.
Table 1.3-8 Feedback data required by data configuration faults and its collection methods
Purpose of Record
Alarm Notification
Alarm file and notification file.
Get Alarm File
Table space
Table space of Minos and ismg alarms
Check filtering rule
Setting of Alarm Filtrate Rule
Check alarm filter rule
Check on disk space
Query Disk Space
Time zone setting
Configure
foreground
timezone,
minos
timezone,
timezone,
and
ISMG
client
Check system timezone
timezone
Record the operation conditions
of OMCR
Query foreground alarms.
Get log files at ISMG background.
Query foreground alarms.
Check alarm records at foreground
1.3.10 Feedback data required by BS equipment faults and its collection

methods
The BS equipment mainly includes the following faults:
Interruption station during BS operation
Exceptional alarms occurs during BS operation
Can not call or difficult to call during individual BS equipment operation
PS service can not operate during individual equipment operation.
Degraded performance index for individual CS or PS service
Other problems related with BS operation.
For feedback data required by BS equipment faults and its collection methods, refer
toTable 1.3-9.
Table 1.3-9 Feedback data required by BS equipment faults and its collection methods
Purpose of Record
50
Chapter 1
Identify
the
relation
between site name and

its number, so you can
find corresponding site
Identify site name, number and its model (BTS

V2).
in ZDB file.
You can find system
KPI/PI/CS reports on the faulty day. Based on 15
operation
minutes granularity, do measurement at cell and
state
in
performance statistics.
Channel state is another
path to judge system
state.
Reflect the information
while the site is starting.
Record call cases in the
system.
Record
BSC levels.
fault
information.
Dynamic observation condition, including cell,

carrier, and channel.
O&M signaling trace
Get O&M tracing signal at interface Abis
Signaling trace at Abis.
Get CS tracing signal at interface Abis
Historical alarm file within a week and historical

notification file within a week.
Different
version
supports
different
Query dynamic data at site
Get Alarm File
Site/BSC version
Get Software Setting
ZDB file at foreground.
Get ZDB File at foreground
functions.
Record
and
confirm
configuration
information
at
foreground.
1.4 Methods to Get System Records

1.4.1 Get Device Printing File
1.
Create a directory to save files on server.
2.
Execute the ftp command at ISMG to connect OMP. Both the user name and
password are zte, and the specified port is 21.
3.
Execute the cd/DOC0 command to enter the DATA0 directory.
4.
Execute the get command to get Exc_Omp.txt file and Exc_pp.txt file.
5.
Download the file to server, then use ftp tool (such as CUTEFTP) to transmit the
file to client.
Example:
51
1.
mkdir bsc1
2.
cd bsc1
3.
ftp 172.20.6.1 21
4.
cd /DOC0
5.
get Exc_pp.txt
6.
get Exc_Omp.txt
7.
bye
1.4.2 Get ZDB File

1.4.2.1 Get Equipment ZDB File
ZDB file is under /DOC0/DATA1 on OMP. While getting ZDB file, if there are too
many files, you had better establish a proper directory for each module on each BSC, to
transfer the ZDB files into proper directory.
1.
Create a directory to save files on server.
2.
Execute the ftp command at ISMG to connect OMP. Both the user name and
password are zte, and the specified port is 21.
3.
Get required ZDB files under DATA1 directory.
i.
Use command cd to enter into /DOC0/DATA1.
ii.
Use command get filename to download CFGTABLE.ZDB, VERTABLE.ZDB,

and DBVER.ZDB one by one.
4.
After the files are downloaded onto server, you can use ftp tool, such as
CUTEFTP, to upload the files to client and compress it.
Example:
1.
cd $OMCHOME
2.
mkdir bsc1
3.
cd bsc1
4.
ftp 172.20.6.1 21
5.
cd /DOC0/DATA1
52
Chapter 1
6.
get CfgTable.ZDB
7.
get DBVer.ZDB
8.
get VERTABLE.ZDB
1.4.2.2 Get ISMG ZDB File

ISMG ZDB files are saved in $OMCHOME/tmp/ftp/zdb/ibscXX (XX indicates
BSCID). Each time you perform whole table synchronization or incremental
synchronization, it may generate new CFGTABLE.ZDB, VERTABLE.ZDB, and
DBVER.ZDB files, and add generation time postfix for the file generated at last time
for backup.
Generated file is too small during incremental synchronization. You can use ls l
command to view the file size. If current ZDB file belongs to the one generated on
incremental synchronization, you can do a synchronization action on whole table on
ISMG client, this will generate new complete ZDB file.
Use ftp tool, such as CUTEFTP, to transfer ZDB file to client.
1.4.3 Get Data Backup ztd File from ISMG

1.
Select View Configuration Management.
2.
Select Data Management Data Backup, as shown in Figure 1.4-1.
Figure 1.4-1
3.
Select Data Backup
In Data Backup window, select storage path/CM (only backuped in the server),
input filename prefix and backup description, and select the NE to be backuped.
After acknowledgement, click OK button, as shown in Figure 1.4-2.
53
Figure 1.4-2
4.
Data Backup Window
Use ftp tool with username/password as sysbak and port 21, to download
backed-up ztd file from ISMG server through ftp mode.
1.4.4 Get Software Setting

1.4.4.1 Get BSC Software Setting
1.
Start Software Version Management at client, and click BSC Software Version
Management after selecting BSC NE on Configuration Resource Tree.
2.
For setting of software version, equipment data may be inconsistent with ISMG
data, so if you can not determine whether it is consistent, you shall do the action
of "synchronize version data from NE to OMC". Synchronization operation may
remove ISMG software setting, operate the data based on actual equipment
condition, and re-establish ISMG software settings, as shown in Figure 1.4-3.
54
Chapter 1
Figure 1.4-3
3.
Synchronize Version Data from NE to OMC
After the synchronization, snap three screenshots for version file, common
version, and special version of BSC. Save it as jpg file and send feedback.
1.4.4.2 Get BTS Software Setting

BTS software setting can get Vertable.zdb equipment file for feedback. For specific
procedure, refer to Get Equipment ZDB File.
1.4.5 Get Alarm File

1.
Start Alarm Management at client. Select View History Alarms in Query

menu option of Alarm Management interface, as shown in Figure 1.4-4.
Figure 1.4-4
2.
Select View History Alarms
Select Quick Query in History Alarm Query Conditions, as shown in Figure

55
1.4-5.
Figure 1.4-5
3.
Select Quick Search
Select System Type in Query History Alarm, and select all alarm types in
System Type, as shown in Figure 1.4-6.
Figure 1.4-6
4.
Query History Alarm Window
Select a relative time in Happen Time. The date shall be a day within a recent
week or a customized day, as shown in Figure 1.4-7.
56
Chapter 1
Figure 1.4-7
Set Query Time of Alarm
5.
Click OK to output alarm data.
6.
Click Export button to export queried alarms.
7.
In Save window, select the proper path and click Save, as shown in Figure 1.4-8.
57
Figure 1.4-8
Alarm Save Window
1.4.6 Get Notification File

1.
Start Alarm Management at client. Select View Notifications] in View Alarm

menu option of Alarm Management interface, as shown in Figure 1.4-9.
Figure 1.4-9
2.
Select View Notifications]
Select Quick Query in Notification Query Conditions, as shown in Figure

1.4-10.
58
Chapter 1
Figure 1.4-10
3.
Select Quick Search
Select System Type in Query Notification, and select all notification types in
System Type, as shown in Figure 1.4-11.
Figure 1.4-11
4.
Query Notification Window
Select start/end time in Happen Time, as shown in Figure 1.4-12.
59
Figure 1.4-12
Set Query Time of Notification
5.
Click OK to output notification data.
6.
Click Export button to export queried notifications.
7.
In Save window, select the proper path and click Save, as shown in Figure
1.4-13.
60
Chapter 1
Figure 1.4-13
Notification Save Window
1.4.7 Get 1 Hour's Performance Data Before and After Fault

1.
Start Performance Management at client, and select Performance

Management Performance Data Query in the menu, as shown in Figure
1.4-14.
Figure 1.4-14
2.
Select Performance Management Performance Data Query
In Query Index tab of Query, select object type as CellFunction Type, and
select KPI Index and PI Index, as shown in Figure 1.4-15.
61
Figure 1.4-15
3.
Query Interface
Select user-defined in Query Time tab, query granularity is Original Granularity

Data (15 minutes), as shown in Figure 1.4-16.
Figure 1.4-16
4.
Set Query Time of Performance Data
In Query Object tab, select the NE to be queried, select the cell that shall be
queried in measurement objects, summary mode is None, as shown in Figure
62
Chapter 1
1.4-17.
Figure 1.4-17
Set Query Object of Performance Data
5.
Queried data shall be exported as EXCEL report.
6.
Repeat above steps, query CSBasicMeasurement and export it as EXCEL report,

as shown in Figure 1.4-18.
63
Figure 1.4-18
Select CSBasicMeasurement
1.4.8 Get Tracing Signal at Interface A

1.
Configure server procedure for signaling trace tool, start server program, start
and logon signaling trace client.
Note
Signaling trace tool shall use server/client architecture.
Requirement of using signaling trace tool: servercfg.xml file is configured at server
side, and server.exe program is running; clientcfg.xml file is configured.
2.
Select Tools Parameter Set, and access to Parameter Set interface to

configure signaling trace. In Record Set tab, configure Items Showed in the
Trace Window as 20000. Select File Divide 5000 items in one file. Click Save
button, as shown in Figure 1.4-19.
Figure 1.4-19 Parameter Set Interface
3.
Configure in Trace Set interface, select the BSC to be traced, and click Update
Config button, as shown in Figure 1.4-20.
64
Chapter 1
Figure 1.4-20
4.
Trace Set Interface
After successfully updating configuration, select SCCP. In SCCP option, select

Module No., and select BSN No. as 254, as shown in Figure 1.4-21.
Figure 1.4-21
5.
Select SCCP
After stopping trace, select File Save all as .tra. Save all signaling trace
results as tra format, as shown in Figure 1.4-22.
65
Figure 1.4-22
6.
Save Signaling Trace Result
Select the path to save in Save window, saved files contain .tra and .idx files. If
feedback, you shall send the both files, as shown in Figure 1.4-23.
Figure 1.4-23
Signaling Trace Save Window
Note
Trace at interface A has great influence on system load. Each trace can not exceed 5
minutes.
1.4.9 Query Dynamic Data at Interface A

1.
Log in ISMG client, click View Dynamic Data Management, access to

Dynamic Data Management interface. Select and expand proper BSC managed
66
Chapter 1
elements, access to BSC Dynamic Data Management interface, and you can
manage PCM at interface A and trunk at interface A.
2.
In A-Interface PCM tab, click Query button to query PCM state; in

A-Interface Trunk Circuit Management tab, click All Queries button, or
select some circuits, click Query Timeslot Circuit State button to query the
state of timeslot.
1.4.10 Get Tracing Signal at Interface Abis

1.
Configure server procedure for signaling trace, start server program, start and
logon signaling trace client.
Note
2.

button, as shown in Figure 1.4-24.
Figure 1.4-24 Parameter Set Interface at Abis
67
3.
Config button.
4.
After successfully updating configuration, select CS and OAM, select the site to
be traced in CS and OAM interfaces. Select all trace items in Trace Item of CS,
select a site in OAM, as shown in Figure 1.4-25 and
Figure 1.4-26.
Figure 1.4-25
CS Interface
Figure 1.4-26
OAM Interface
68
Chapter 1
5.
After tracing, the traced signal can be saved.
1.4.11 Query Dynamic Data at Site

1.
Click View->Dynamic Data Management to enter the dynamic data

management interface.
2.
In configuration resource tree, select and expand BSC management elements

node.
3.
Double-click corresponding dynamic data management node at site, enter into

Dynamic Data Management interface, so you can do radio resource
management and site equipment management operation.
For dynamic data management functions at site, refer to Table 1.4-1.
Table 1.4-1
Category
Radio
Resources
Management
BTS
equipment
management operation
Dynamic Data Management Function
Function
Description
Cell management
Query the status of cell
TRX management
Query the state of TRX
Channel Management
Query channel state
Module Management
Query channel statistics on a module
BVC Management
Query the BVC status of cell
Cell channel management
Query channel statistics of a cell
Timeslot management at
Query timeslot state measurement of
Abis
resource pool at Abis
Timeslot
resource
Query timeslot state of resource pool at
management at Abis
Abis
LAPD state management
Query LAPD link state at site
1.4.12 Query BVC and NSVC State

1.
Click View->Dynamic Data Management to enter the dynamic data

management interface.
2.
In configuration resource tree, select and expand management elements node to

be queried.
3.
Double-click corresponding dynamic data management node, enter into

Dynamic Data Management interface.
4.
In NSVC Management of Dynamic Data Management interface, you can

69
query NSVC state.

5.
In configuration resource tree, double-click corresponding dynamic data

management node under management NE node to be queried, enter into
dynamic data management interface.
6. In Radio Resource Management tab of Dynamic Data Management interface,

select BVC Management to query NSVC state.
1.4.13 Trace PS Service Signal

1.
Configure server procedure for signaling trace, start server program, start and
logon signaling trace client.
Note
2.

button.
3.
Config button.
4.
For Trace Type, select PS and RLCMAC at interface Abis, and all options at
interface Gb.
5.
Select the cell to be traced in PS and RLCMAC, BVCI and BVCIO to be traced
in BSSGP and LLC, NSVC link to be traced in NS, BRCH link to be traced in
FR. Click OK button, as shown in Figure 1.4-27.
70
Chapter 1
Figure 1.4-27
6.
Trace Setting of PS Service Signal
After stopping trace, select File Save all as .tra. Save all signaling trace
result as tra format.
7.
Select the path to save in Save window, saved files contain .tra and .idx files. If
feedback is required, you shall send the both files.
1.4.14 Get Operation Log of Preset Machine

Operation log of preset machine is saved in X:\FTPRoot\nfsDev\iBSC\OMS\log. You
can get it through ftp tools. Where, X indicates the disk label of the log.
Meanwhile, you shall display the update date in \FTPRoot\nfsDev\iBSC\OMS\,
\FTPRoot\nfsDev\iBSC\OMCR, and \FTPRoot\nfsDev\iBSC\OMSZIP.
1.4.15 Check Whether Overstocked Data Exists

1.
Check
whether
data
is
overstocked
$OMCHOME/gsmomcr/ibsc/zxgomcr-emf-pm.par/x-y/err.
x-y
in
represents
GERAN subnet, x, and BSC management NE, y.

Data accumulation is caused by exceptional oracle, full table space in
performance library and performance index. For specific information, you can
get error reasons from server log.
71
Solution is as follows:
Check the space size of performance table and index table, if it is full, you can
expand it based on server disk space, or delete relevant performance data and
re-create index.
Exceptional operation modes of oracle are diversified, and it is complicated to
solve it. It is recommended you shall return server log to ZTE for analysis. You
can try to restart ORACLE on site.
2.
Check whether data file is overstocked in X:FTPRoot\nfsDev\iBSC\OMCR of

preset machine. Where, X is the label of data file disk.
Check whether communication between ISMG server and preset machine is
normal and whether ftp service of preset machine is normal. You can try to
preset machine through ftp and get performance file under ISMG directory.
1.4.16 Query Disk Space

1.
Use command df k and vmstat to query current disk space.
2.
Use NETTERM to save operation procedure.
1.4.17 Get ISMG Printing File

1.
Process printing file related with ISMG is located under $OMCHOME\log. The
log file is named by its generation time. If you use command cd
$OMCHOME\log, you can enter into this directory to get corresponding LOG
file.
Example:
bash-3.00$ cd $OMCHOME/log
bash-3.00$ ls
boot.log
server-20080117-0623-28443.log
server-20080117-1005-13029.log server-20080117-1436-53392.log
consoleagent.log.0
server-20080117-0812-56822.log
server-20080117-1048-52694.log server-20080117-1516-54067.log
consoleagent.log.0.lck
bash-3.00$ pwd
72
Chapter 1
/export/home/iomcr/iOMCR6.00.02f/ums-svr/log
3 Use ftp tool, such as cuteftp, to get log file within OMCR fault period.
1.4.18 Get ISMG Profile

ISMG profile is saved in $OMCHOME/deploy. You can use ftp tools, such as
CUTEFTP, to download it to local client. Required profile is as follows:
deploy-010muep.properties
deploy-gsmomcr01.properties
The
files
related
with
upper-level
ISMG
alarms
are
saved
into
$OMCHOME/gsmomcr/ibsc/zxgomcr-naf-rtalarm.par/conf. Required profile is as

follows:
fmmgr.properties
nafproc.properties
1.4.19 Get Operation Log at Client

1.
Start Log Management at client, access to Operation Log interface, select

Query Operation Log, as shown in Figure 1.4-28.
73
Figure 1.4-28
Select Query Operation Log
4 In Query Operation Log window, customize operation time period to query, or

query all operation logs, and click OK, as shown in Figure 1.4-29.
74
Chapter 1
Figure 1.4-29
2.
Query Operation Log Window
After successfully querying, export the log to excel.
1.4.20 View System Time Zone

1.
View time zone at server side by using command: echo $TZ.
2.
To view the time zone at client, you can perform as follows:
After opening control panel of client computer, you can find current time zone in the
option of region setting.
1.4.21 View ISMG version

On client interface of ISMG system, click Help About, and display ISMG version
information.
.
75
2 Routine Maintenance
This chapter provides procedures and guidelines for the routine maintenance of
ZXG10-BSS (V3).
2.1 Overview
2.1.1 Purpose of Routine Maintenance
To ensure stable and reliable operation of the BSC equipment, effective maintenance
measures are very important. Routine maintenance helps to discover and solve
problems in due time.
2.1.2 Classification of Routine Maintenance

According to maintenance period, routine maintenance can be classified into four
types:
Daily maintenance
Weekly maintenance
Monthly maintenance
Quarterly maintenance
Table 2.1-1 shows the check items in ZXG10 iBSC routine maintenance.
Table 2.1-1
Routine Maintenance Table
Maintenance Type
Check Item
Equipment room
environment check
Daily maintenance
BSC running status
check
77
Environment alarm
Temperature in equipment room
Humidity in equipment room
Burglarproof net, doors, and windows
Cabinet doors
Cleanness
Board indicators
Foreground-background communication link
BSC current alarms
BSC past 24-hour history alarm
Maintenance Type
Check Item
BSC past 24-hour notifications
BSC KPI
A-interface status
Gb-interface status
Boards active/standby status
BSC operation log
Alarm box
Weekly maintenance
Monthly maintenance
Quarterly maintenance
Equipment cleanness
BSC clock status
OMP and CMP status
Real-time BSC alarm statistics
Past-week history alarms
Performance indices
Server running status
Occupancy of iOMCR server
Configuration data backup
Virus scanning
Software version
Clock synchronization
Automatic backup clearing
OS patch update
Protective cap of optical interface
Power supply
Cable connection
Fan subrack working status
Anti-static wrist strap
Spare materials and parts
Grounding conditions
Dustproof mesh
2.1.3 Precautions
Perform the following steps during routine maintenance:
1.
Maintain normal temperature and humidity in the equipment room. Keep the
surrounding tidy and clean, free from dust and moisture. Keep rodents or insects
out of the equipment room.
2.
Ensure that the systems primary power is stable and reliable. Check the system
grounding and lightning ground periodically. Check the lightning protection
system to ensure good condition before the stormy season and after
thunderstorms.
3.
Establish complete rules for equipment room maintenance, and standardize daily
work of the maintenance personnel.
1)
A detailed attendants log should be maintained to provide detailed records

about system operation, version, data change, upgrading and troubleshooting,
78
Chapter 2
Routine Maintenance
for analysis and troubleshooting after the fault detection.

2)
Keep a record of the work shifts to specify the responsibility clearly.
4.
Every client should be installed with AntiVirus software, and real-time detection
function should be enabled. The virus library should be updated periodically.
The operation and maintenance computers should be used for special purposes
only. Usage of unauthorized disks or CDs, installation of unrelated software, or
playing games on the client terminals is prohibited.
5.
Only one user can have the super administrator rights. Other related persons can
be assigned corresponding rights according to their work contents, to guarantee
data security. Set different Network Management passwords for different access
rights, and keep them under strict management and change them periodically.
Network Management passwords should be accessible only to maintenance
personnel.
6.
Maintenance personnel should be well trained and should have adequate

equipment and network knowledge. During maintenance operations, follow the
instructions provided in the relevant BSC (V2.97) manual. Before touching
equipment hardware, wear an antistatic wrist strap to avoid any accidents.
Maintenance personnel should have a meticulous working attitude and
professional maintenance skills, which can be enhanced through constant
learning.
7.
Do not plug and unplug boards, change over boards, load or change data
casually, particularly the Network Management database. Back up data before
any changes, and make records of data modifications. Do not delete backup data
until the equipment has run properly for a specific period (usually a week) after
changing data. Even though data is not changed, backup should be taken once a
week for occasional requirements. Databases, especially the performance
measurement and alarm database, should be observed on regular basis (once
every two weeks). When there are too many occupations (beyond the
recommended OMC-R value), useless data should be deleted to avoid the error
of disk overflow.
8.
Never run the signaling trace program during busy traffic, especially during
daytime. The signaling trace is carried out only in low-traffic hours with the
permission of the ZTE customer service department.
79
9.
Prepare frequently used tools and meters such as screws (straight head and cross
head), signaling testers, network cable pliers, multi meter, AC power for
maintenance purposes, telephone line, network cables, antistatic wrist strap,
insulation tape and common tool kit. Periodically test and calibrate instruments
and meters to ensure their accuracy.
10. Check spare parts regularly, to maintain accurate inventory of frequently used
spare parts and their working condition. Ensure that the inventory contents are
unaffected by humidity or mould. Spare parts and articles must be separated
from defective ones replaced during maintenance, and labeled appropriately for
identification purposes. Frequently used spare parts and articles must be
replenished in time when out of stock.
11. Keep maintenance software and documentation at the site at designated position,
to ensure that software and documentation are available when necessary.
12. Ensure that lighting in the equipment room is bright enough for maintenance
operations.
13. Remove any detected faults immediately. For faults that cannot be resolved,
contact the local ZTE office.
14. Keep the ZTE CORPORATION local telephone number and address at an easily
identifiable place and inform all maintenance personnel, so that ZTE can be
contacted when there is a need. Remember to get the latest contact information.
2.2 Daily Maintenance

2.2.1 Equipment Room Environment Check
2.2.1.1 Checking Equipment Room Environment Alarms
[Preparation]
Prior to performing this task, make sure that the ZXG10 iBSC environment alarm
system has been installed and the system is running normally.
[Background Knowledge]
ZXG10 iBSC environment alarm system consists of the power distribution plug-in box,
smoke sensor, infrared sensor, temperature and humidity sensor, and access control
80
Chapter 2
Routine Maintenance
sensor.
The power distribution plug-in box is an important component of the alarm system. It
is installed with the Power Distribution Board (PWRD) and the Power Distributor
Backplane (PWRDB). The functions include power indication, environment
monitoring, and internal fan plug-in box monitoring.
PWRDB is located at the back of the power distribution plug-in box, leading out the
monitoring cable H-MON-009. The external sensor is connected with the power
distribution plug-in box through cable H-MON-009. PWRD performs alarm signal
processing. The alarm indicator on the power distribution plug-in box panel indicates
alarm if the following problems occur:
The -48 V power supply has problems such as over-voltage, under-voltage, or
power-down.
The fan becomes abnormal.
Smoke signal, intrusion signal, or signal of temperature/humidity exceeding
limit is detected.
[Operation Guide]
Check whether the alarm indicator on the power distribution plug-in box indicates
alarm. Check whether there is any environment alarm, including power supply system
alarm, fire alarm, and smoke alarm.
[Reference Standard]
Figure 2.2-1 shows the front panel of power distribution plug-in box.
POWER JUNCTION BOX
ON
OFF
RUN -48V(I) -48V(II) FAN
HOT SMOKE DOOR ARRESTER
-48V(I) -48V(II)
Figure 2.2-1
Front Panel of Power Distribution Plug-in Box
There are eight indicators on the panel. Table 5.2-1 describes these indicators.
81
Table 2.2-1
Name
RUN
Color
Green
Indicators on Power Distribution Plug-in Box

Meaning
Work Mode
Running indicator
Flashes at 1 Hz: normal running

OFF: abnormal
-48 V(I)
Red
The first -48 V alarm
ON: the first -48 V power supply has
indicator
under-voltage or over-voltage alarm

OFF: no alarm
-48 V(II)
Red
The second -48 V
ON: the second -48 V power supply has
alarm indicator
under-voltage or over-voltage alarm

OFF: no alarm
FAN
Red
Fan alarm indicator
ON: the fan has abnormal alarm

OFF: no alarm
HOT
Red
Temperature
alarm
indicator
ON: the environment temperature has abnormal

alarm
OFF: no alarm
SMOKE
DOOR
Red
Red
ARRESTER
Red
Smoke
alarm
ON: abnormal smoke alarm
indicator
OFF: no alarm
Access control alarm
ON: abnormal access control alarm
indicator
OFF: no alarm
Lightning
protector
alarm indicator
ON: the lightning protector has abnormal alarm

OFF: no alarm
[Abnormality Handling]
Different handling methods are applied to different alarms.
1.
If the power-supply system has under-voltage or over-voltage alarm, use

multimeter to check the -48 V power.
2.
If the equipment room has fire alarm or smoke alarm, check the inside
environment of equipment room.
Check whether there is any fire or smoke. If there is no smoke, the alarm might
be caused due to floating dust in the air. Purify the air or suppress the alarm.
Ensure that the air conditioner is normal.
Ensure that the sensor is normal.
Check whether the alarm box is faulty. Replace the alarm box if its hardware is
faulty.
82
Chapter 2
Routine Maintenance
2.2.1.2 Checking Equipment Room Temperature

[Operation Guide]
Observe the thermometer indication and record the temperature in the equipment room.
The working temperature for ZXG10 iBSC (V6.10) must satisfy the following
requirements:
Long-term working temperature: 0 C ~ 40 C
Short-term working temperature: -5 C ~ 45 C
Note
The values of working temperature and humidity in the equipment room must be
measured in the following conditions: the cabinet does not have front/rear protection
panel, and the measurement is performed 1.5 m above the ground and 0.4 m in front of
the cabinet.
It is advised to keep the equipment rooms temperature between 15 C and 30 C.
If the equipment room temperature is abnormal, check the air conditioner and make
sure that it works normally and satisfies the working temperature requirement.
2.2.1.3 Checking Equipment Room Humidity
[Operation Guide]
Observe the hygrometer indication and record the humidity in the equipment room.
The working humidity for ZXG10 iBSC (V6.10) must satisfy the following
requirements:
Long-term working humidity: 20% ~ 90%
Short-term working humidity: 5% ~ 95%
Note
If the phenomenon of condensed water is found, solve the problem immediately.
It is recommended to keep the equipment rooms humidity between 40% and 65%.
83
If the equipment rooms humidity is abnormal, check the air conditioner and make sure
that it works normally and satisfies the working humidity requirement.
2.2.1.4 Checking Equipment Room Burglarproof-Net, Doors and Windows
[Operation Guide]
Check and ensure the normal condition of equipment room burglarproof-net, doors,
and windows.
If the burglarproof-net, doors, or windows of the equipment room are damaged, make
records in the Daily Maintenance Record and replace the faulty ones immediately.
2.2.1.5 Checking Cabinet Doors
[Operation Guide]
Check the front and rear doors of the cabinet and ensure that they are closed.
If any of the front or the rear door is open, make records in the Daily Maintenance
Record and close the door.
2.2.1.6 Cleaning Equipment Room
[Operation Guide]
Check the equipments in the equipment room and the ground to ensure they are all
clean.
Clean the equipment room environment in time.
2.2.2 BSC Running Status Check

2.2.2.1 Checking Board Indicators
[Operation Guide]
Check the status of BSC panel indicators. If the checking result is as follows, then it
indicates that the board is running normally.
84
Chapter 2
Routine Maintenance
The running indicator RUN flashes at 1 Hz

The alarm indicator ALM is always OFF
If the board is 1+1 backup, the active/standby indicator ACT is in normal status:
- ACT is ON, indicating the board is active.
- ACT is OFF, indicating the board is standby.
For details of different iBSC board indicators, refer to the ZXG10 iBSC (V6.10) Base
Station Controller Hardware Manual.
1.
Enter Fault Management to view detailed alarms.
2.
Reset the board.
3.
Check the boards data configuration and version configuration to make sure
that they are correct, and the foreground and background configurations are
consistent.
4.
Unplug and plug the board to make sure that the board has good contact. If the
problem still exists, replace the board.
2.2.2.2 Checking Foreground-Background Communication Link

[Preparation]
Prior to performing this task, make sure that:
ISMG client is running normally.
Connection between the client and server is normal.
[Operation Guide]
1.
Enter Fault Management and view the detailed alarm (alarm code: 1000).
2.
Execute the ping command in ISMG server to check whether the foreground
OMPs IP address can be accessed, in other words, to check whether the
foreground-background communication is normal.
3.
Enter Dynamic Data Management to query the link status and to check
whether the foreground-background communication link is established
successfully.
As
shown
85
in
Figure
2.2-2,
indicates
that
the
foreground-background link is established successfully.
indicates that the
foreground-background link establishment is failed.
Figure 2.2-2
Link Status Query
1.
For link connected with the foreground, its status is OK.
2.
The foreground-background communication link succeeds.
1.
After executing the ping command, if it is found that the foreground OMPs IP
address can not be accessed, then check the cable connections and connectors
between the ISMG server and the foreground and ensure that they are normal.
Check whether the HUB or the switch has power-down and make sure that they
work normally.
2.
If the foreground-background communication link fails, check the OMP data

configurations and version configurations at foreground and background and
ensure that they are correct and consistent.
3.
Reset the OMP board.
4.
Unplug and plug the board to make sure that the board has good contact. If the
86
Chapter 2
Routine Maintenance
problem persists, replace the board.

5.
Observe the OMP panel indicators to check whether the foreground OMP runs
normally.
- If the running indicator RUN flashes at 1 Hz and the alarm indicator ALM is OFF,
then it indicates that OMP runs normally.
- If the running indicator RUN is always ON or always OFF, or the alarm indicator
ALM is red and ON, then it indicates that OMP runs abnormally. Replace the
board in this case.
2.2.2.3 Querying BSCs Current Alarms
[Preparation]
ISMG client is running normally
Fault Management interface is opened.
[Operation Guide]
1.
In the Fault Management tab, click Query View Current Alarms, as

shown in Figure 2.2-3.
Figure 2.2-3
87
Querying Current Alarms
2.
Current Alarm Query Conditions tab appears, as shown in Figure 2.2-4.
Figure 2.2-4
3.
Current Alarm Query Conditions Tab
In the Current Alarm Query Conditions tab, the current alarms can be queried
in two ways: rapid query and combination query. Also, operations such as
modification, deletion and refresh can be performed.
Rapid query
Through rapid query, the alarm information can be queried rapidly, but query
conditions are not saved after the query result is displayed.
1)
In the Current Alarm Query Conditions tab, click
in the toolbar, Query
Current Alarm dialog box pops up, as shown in Figure 2.2-5.
88
Chapter 2
Figure 2.2-5
2)
Routine Maintenance
Query Current Alarm Dialog Box
Select query conditions according to actual requirement, and click OK. The
system starts the current alarm query and displays the query result in the View
Current Alarms tab, as shown in Figure 2.2-6.
89
Figure 2.2-6
Current Alarm Query Result
Note
The current alarm query differs from other queries as the query result interface can be
refreshed automatically. If Visibility check box is not checked in the Query Current
Alarm dialog box, then the query result will not be refreshed automatically, and can
not be refreshed manually either
Combination query
In the Current Alarm Query Conditions tab, the query condition can be
created and displayed as a list. User can select one or multiple conditions to
perform query, and can also modify the query condition.
1)
In the Current Alarm Query Conditions tab, click
in the toolbar,
Current Alarm Query Condition dialog box pops up, as shown in Figure
2.2-7.
Figure 2.2-7
Current Alarm Query Condition Dialog Box
90
Chapter 2
2)
Routine Maintenance
In the Current Alarm Query Condition dialog box, enter Name and
Description, select query conditions in Selection area, and click OK.
3)
The set query condition appears in the Current Alarm Query Conditions tab,
Figure 2.2-8
4)
Created Current Alarm Query Conditions
Select and right-click on one or multiple query conditions, and click Execute on
the pop-up menu or click
91
in the toolbar, as shown in Figure 2.2-9.
Figure 2.2-9
5)
Combination Query of Current Alarms
The system performs query according to selected conditions, and displays the
query result in the form of list in View Current Alarms tab, as shown in Figure
2.2-10.
Figure 2.2-10
Combination Query Result of Current Alarms
1.
In the View Current Alarms tab, double-click an alarm or right-click an alarm,

and click Details in the pop-up menu, as shown in Figure 2.2-11.
92
Chapter 2
Routine Maintenance
Figure 2.2-11 Selecting Details Menu Item for Current Alarm
2.
In the Details dialog box, select the Details tab to view detailed information of
the alarm, as shown in Figure 2.2-12. User can click buttons on the right (Pre,
Next, Acknowledge, Unacknowledge, Clear, Forward, Comment) to perform
corresponding operations. In the Maintenance Suggestion tab, user can
customize the maintenance suggestion and save it.
93
Figure 2.2-12
Details of Current Alarm
Note
Users can also right-click an alarm in the query result of current alarms and click
Acknowledge, Unacknowledge, Clear, Forward in the pop-up menu to perform
corresponding operations.
2.2.2.4 Querying BSCs Past 24-Hour History Alarms
[Preparation]
Prior to performing this task, make sure that:
The Fault Management interface is opened.
The newly-generated alarm information exists in the form of current alarm. If user
performs the clearing operation, the current alarm becomes history alarm.
94
Chapter 2
Routine Maintenance
[Operation Guide]
1.
In the Fault Management tab, select Query View History Alarms, as

Figure 2.2-13
2.
History Alarm Query Conditions tab appears, as shown in Figure 2.2-14.
Figure 2.2-14
3.
Selecting View History Alarms
History Alarm Query Conditions Tab
In the History Alarm Query Conditions tab, the history alarm can be queried
in two ways: rapid query and combination query. Also, operations such as
Rapid query
95
Through rapid query, the alarm information can be queried rapidly, but query
conditions are not saved after the query result is displayed.
1)
In the History Alarm Query Conditions tab, click
History Alarm dialog box pops up, as shown in Figure 2.2-15.
Figure 2.2-15
2)
Query History Alarm Dialog Box
In the Query History Alarm dialog box, select Happen Time. Time options
appear on the right, as shown in Figure 2.2-16.
96
Chapter 2
Figure 2.2-16
3)
Routine Maintenance
Time Options for History Alarms
Select By Relative Time, enter 1 in the Latest spin box or click

appears in the spin box, as shown in Figure 2.2-17.
97
until 1
Figure 2.2-17
Setting Happen Time of History Alarm
Note
Users can also select By Time Range and set Begin Time and End Time. By default,
the duration between Begin Time and End Time is the past 24 hours.
4)
In the Query History Alarm dialog box, after setting Happen Time, click OK.
The system starts query and displays the query result as a list in the View
History Alarms tab, as shown in Figure 2.2-18.
98
Chapter 2
Figure 2.2-18
Routine Maintenance
Query Result of History Alarms
Combination query
In the History Alarm Query Conditions tab, the query condition can be created
and displayed as a list. User can select one or multiple conditions to perform
query, and can also modify the query condition.
1)
In the History Alarm Query Conditions tab, click
in the toolbar,
History Alarm Query Condition dialog box pops up, as shown in Figure
2.2-19.
99
Figure 2.2-19
2)
History Alarm Query Condition Dialog Box
In the History Alarm Query Condition dialog box, enter Name and
Description, select query conditions in Selection area (set Happen Time to be
the past 24 hours), and click OK.
3)
The set query condition appears in the History Alarm Query Conditions tab,
100
Chapter 2
Figure 2.2-20
4)
Created History Alarm Query Conditions
Select and right-click on one or multiple query conditions, and click Execute in
Figure 2.2-21
5)
Routine Maintenance
Combination Query of History Alarms
The system performs query according to selected conditions and displays the
query result as a list in View History Alarms tab, as shown in Figure 2.2-22.
Figure 2.2-22
Combination Query Result of History Alarms
101
1.
In the View History Alarms tab, double-click an alarm or right-click an alarm,

and click Details in the pop-up menu, as shown in Figure 2.2-23.
Figure 2.2-23
2.
Selecting Details Menu Item for History Alarm
the alarm, as shown in Figure 2.2-24. User can click buttons on the right (Pre,
Next) to perform corresponding operations. In the Maintenance Suggestion tab,
user can customize the maintenance suggestion and save it.
102
Chapter 2
Figure 2.2-24
Routine Maintenance
Details of History Alarm
2.2.2.5 Querying BSCs Past 24-Hour Notifications

[Preparation]
Connection between the client and the server is normal.
[Operation Guide]
1.
In the Fault Management tab, select Query View Notifications, as shown

in Figure 2.2-25.
103
Figure 2.2-25
2.
Notification Query Conditions tab appears, as shown in Figure 2.2-26.
Figure 2.2-26
3.
Selecting View Notifications
Notification Query Conditions Tab
In the Notification Query Conditions tab, the notifications can be queried in

two ways: rapid query and combination query. Also, operations such as
Rapid query
Through rapid query, the notification information can be queried rapidly, but
query conditions are not saved after the query result is displayed.
1)
In the Notification Query Conditions tab, click
Notification dialog box pops up, as shown in Figure 2.2-27.

104
Chapter 2
Figure 2.2-27
2)
Routine Maintenance
Query Notification Dialog Box
In the Query Notification dialog box, select Happen Time check box. Time
options appear on the right, as shown in Figure 2.2-28.
105
Figure 2.2-28
3)
Time Options for Notifications
Select By Time Range and set Begin Time and End Time. By default, the
duration between Begin Time and End Time is the past 24 hours. Select By
Relative Time, enter 1 in the Latest spin box or click
until 1 appears in the
spin box.
4)
In the Query Notification dialog box, after setting Happen Time, click OK.
The system starts query and displays the query result as a list in the View
Notifications tab, as shown in Figure 2.2-29.
106
Chapter 2
Figure 2.2-29
Routine Maintenance
Query Result of Notifications
Combination query
In the Notification Query Conditions tab, the query condition can be created
and displayed as a list. User can select one or multiple conditions to perform
query, and can also modify the query condition.
1)
In the Notification Query Conditions tab, click
in the toolbar,
Notification Query Condition dialog box pops up, as shown in Figure 2.2-30.
107
Figure 2.2-30
2)
Notification Query Condition Dialog Box
In the Notification Query Condition dialog box, enter Name and Description,
select query conditions in Selection area (set Happen Time to be the past 24
hours), and click OK.
3)
The set query condition appears in the Notification Query Conditions tab, as
Figure 2.2-31
Created History Alarm Query Conditions

108
Chapter 2
4)
Select and right-click on one or multiple query conditions, and click Execute on
Figure 2.2-32
5)
Routine Maintenance
Combination Query of History Alarms
The system performs query according to selected conditions and displays the
query result as a list in View Notifications tab, as shown in Figure 2.2-33.
Figure 2.2-33
Combination Query Result of Notifications
1.
In the View Notifications tab, double-click or right-click a notification, and

click Details in the pop-up menu, as shown in Figure 2.2-34.
109
Figure 2.2-34
2.
Selecting Details Menu Item for Notification
the notification, as shown in Figure 2.2-35. User can click buttons on the right
(Pre, Next) to perform corresponding operations.
Figure 2.2-35
110
Details of Notification
Chapter 2
Routine Maintenance
2.2.2.6 Querying BSC KPI

[Preparation]
[Operation Guide]
1.
In the Performance Management tab, click Performance Management

Performance Data Query, or click
in the toolbar.
Important KPI data are reported to the background ISMG from the foreground
equipment, users need not change any settings. Six types of KPI values should
be especially noticed: call drop rate, congestion rate, service rate, handover
success rate, CPU load, and traffic call drop ratio.
2.
Query dialog box pops up, as shown in Figure 2.2-36.
Figure 2.2-36
3.
Query Dialog Box
In the Query Index tab of Query dialog box, select BSC Managed Element in
Object Type drop down menu, and check CPU load Measurement check box.
4.
In the Query Index tab of the Query dialog box, select CELL in Object Type
drop down menu, and select KPI Index check box, as shown in Figure 2.2-37.
111
Figure 2.2-37
5.
Selecting KPI Index
Set the query time in Query Time tab, set the query object in the Query Object
tab, and click OK in the Query dialog box.
6.
Click
in the toolbar to save the query result.
Table 2.2-1 describes referenced KPI values of BSC.
Table 2.2-1
Referenced KPI Values of BSC
Performance Index
Reference Value
SDCCH in congestion rate (%)
1%
SDCCH in call drop rate (%)
0.5%
TCH in service rate (%)
99%
TCH in congestion rate (excluding handover) (%)
3%
TCH in congestion rate (including handover) (%)
2%
TCH in call drop rate (excluding handover) (%)
1%
TCH in call drop rate (including handover) (%)
0.8%
Traffic call drop ratio
90
Handover success rate (%)
95%
SDCCH in service rate (%)
99%
Radio switch rate (%)
97%
TCH assign failure rate (%)
2%
TCH allocate failure rate (%)
10%
112
Chapter 2
Average value of CPU load
80%
Peak value of CPU load
90%
Routine Maintenance
Note
The index values in Table 2.2-1 are for reference. User can customize KPI indices
according to actual network status and requirements.
Analyze KPI values. If a KPI value exceeds the normal range, perform troubleshooting
immediately.
2.2.2.7 Checking A-Interface Status
[Preparation]
[Operation Guide]
1.
In the Dynamic Data Management tab, double-click the BSC Dynamic data
management node in the left Configuration Resource Tree. BSC Dynamic
data management tab appears on the right, as shown in Figure 2.2-38.
Figure 2.2-38
113
BSC Dynamic Data Management Tab
2.
Select No. 7 Signal State Management tab to query the No. 7 signaling link
status.
3.
Select A PCM Management tab to query the PCM status.
4.
Select A Trunk Management tab to query status of all timeslots.
1.
The configured LINK is in the status of being activated or signaling occupation.
2.
The configured voice channel is in the status of being occupied or being idle.
1.
SC self-test
1)
Judge whether BSC is normal. During A-interface interconnection, if the No. 7

signaling link is disconnected, check BSC and ensure that BSC has no problem.
2)
Check the running status of all boards in BSC and ensure that all indicators are
in normal status.
3)
According to configuration data, find out PCMs where the No. 7 signaling link
is located.
4)
Perform self-loop test for these PCMs, and observe the status of SPB and DTB
indicators.
After the self-loop test is performed, if the E1 indicator on SPB and DTB flashes
rapidly, it indicates that no problem exists inside BSC; otherwise, it indicates
that some problem exists inside BSC.
2.
BSC internal problem troubleshooting
1)
Data problem
The probability of data configuration error is low. The configuration should be
performed very carefully. The correctness of data configuration is checked by
comparing ZDB files at the foreground and the background.
2)
Hardware problem
These problems include board problems and internal cable connection problems.
Some common fault symptoms are: board fault, E1 line position being
inconsistent with the configured serial number, etc.
114
Chapter 2
Routine Maintenance
For No. 7 signaling fault, check the boards where No. 7 signaling passes through,
unplug and plug these boards one by one to locate the fault.
3.
If no problem exists inside the BSC, check the interconnection data and ensure
that they are correct.
2.2.2.8 Checking Gb Interface Status

[Preparation]
[Operation Guide]
According to whether Gb interface uses IP or E1, the operation steps for checking Gb
interface status are divided into two types:
Gb interface uses IP
1.
data management tab appears on the right.
2.
Select the IP GB Management tab to query the end node status, NSVC status
and dynamic end node status.
1.
Gb interface uses E1
data management tab appears on the right.
2.
Select the NSVC Management tab to query the NSVC status.
The configured NSVC is in the status of being occupied or being idle, without
congestion or being blocked.
1.
BSC self-test
1)
Judge whether BSC is normal and ensure that BSC has no problem.
115
2)
Check the running status of all boards in BSC and ensure that all indicators are
in normal status.
3)
Perform self-loop test for PCM, and observe the status of SPB indicators.
After the self-loop test is performed, if the E1 indicator on SPB flashes rapidly,
it indicates that no problem exists inside BSC; otherwise, it indicates that some
problem exists inside BSC.
2.
BSC internal problem troubleshooting

1)
Data problem
The probability of data configuration error is low. The configuration should be
performed very carefully. The correctness of data configuration is checked by
comparing ZDB files at the foreground and the background.
2)
Hardware problem
These problems include board problems and internal cable connection problems.
Some common fault symptoms are: board fault, E1 line position being
inconsistent with the configured serial number, etc.
3.
If no problem exists inside the BSC, check the interconnection data and ensure
that they are correct.
2.2.2.9 Checking Boards Active/Standby Status

[Preparation]
[Operation Guide]
1.
In the Dynamic Data Management tab, select and double-click the rack where
the board is located. The rack view appears on the right, as shown in Figure
2.2-39.
116
Chapter 2
Figure 2.2-39
2.
Routine Maintenance
Checking Boards Active/Standby Status
Check the color of the board in the rack view. Green represents that the board is
active while blue represents that the board is standby.
For details of the active and standby status of all boards, refer to the Legend tab on the
right side of rack view.
1.
Check the active/standby status indicator on the board to ensure that it is

consistent with that displayed on the ISMG interface.
2.
If the active/standby status of all boards is unknown, check the

foreground-background communication link.
3.
If the active/standby status of some boards is unknown, enter Fault

Management to view alarm details.
2.2.2.10 Querying BSC Operation Log

[Preparation]
117
The operation log of BSC records the BSC operation details, which is often used to
locate the fault. Browsing and saving the operation log every day helps to find the
abnormality in system running and operation.
[Operation Guide]
1.
Click View Log Management to enter Log Management. In the Log

Management tab, user can query the operation log according to specified
condition or query all the operation logs, as shown in Figure 2.2-40.
Figure 2.2-40
Querying Operation Log
Querying the operation log according to specified condition

In the Log Management tab, right-click Operation Log and click Query
Operation Log in the pop-up menu. Query Operation Log dialog box pops up,
as shown in Figure 2.2-41. Select query conditions, and click OK.
118
Chapter 2
Figure 2.2-41
Routine Maintenance
Query Operation Log Dialog Box
Querying all the operation logs

In the Log Management tab, right-click Operation Log and click Query All
Operation Log in the pop-up menu.
2.
The query result of operation log is shown in Figure 2.2-42.
Figure 2.2-42
119
Operation Log Query Result
3.
Double-click an operation log to view the operation log details.
The operation log does not contain any unknown data configuration operation and
resetting operation, and the log information is normal.
If the operation log contains data configuration operation, check whether the operation
is correct and who performs the operation.
If the operation log contains the following maintenance operations, find out the reason
why they are included in the log: resetting board, board changeover, blocking link,
deactivating No.7 link, disabling signaling point and subsystem, and port loopback.
2.2.2.11 Checking Alarm Box
[Preparation]
[Operation Guide]
1.
In the Fault Management tab, click Setting Alarm Box Setting and check
whether the link between the alarm box and the server is established.
2.
Query the past 24-hour history alarms of BSC to see whether the alarm box has
any alarm.
3.
Check whether the critical alarm that satisfies the reporting conditions can be
correctly sounded and displayed on the alarm box.
The RUN indicator on the alarm box flashes regularly.
The alarm level indicated by the alarm indicator is consistent with the current
alarm level displayed in Fault Management.
The suppressed alarm is not displayed on the alarm box.
120
Chapter 2
Routine Maintenance
1.
If the alarm box has alarm, enter Fault Management to check the alarm details.
2.
Check the cable connection and connectors between the alarm box and server
and ensure that they are normal. Check whether the HUB and the switch is
power-down and ensure that they work normally.
3.
Check the alarm box configuration to ensure that the configuration is correct.
2.2.3 BTS Check

2.2.3.1 BTS Current Alarms Querying and Handling
[Tools]
ZXG10 Alarm Management interface in the iOMCR client
[Test Procedure]
1.
Click Fault Management in the iOMCR topological view and select Alarm
management.
2.
In the ZXG10 Alarm Management interface, select View > Physical View
from the menu bar.
3.
From the left pane, select GSM Equipment > Physical Site to view the current
alarms of the BTS site in the right pane.
[Normal Result]
There is no abnormal alarm of the BTS in the alarm view.
[Troubleshooting]
Double-click the alarm to get the alarm details. Resolve the alarm according to the
System method in Details window.
2.2.3.2 24-Hour BTS History Alarms Querying and Handling
[Tools]
[Test Procedure]
1.
management.
2.
In the ZXG10 Alarm Management interface, select File > Alarm History
121
Query from the menu bar to start Alarm Query Wizard.

i.
Select the History Alarm as Alarm Type.
ii.
Set the past 24 hours as the start time/end time, and then select the BTS to be
queried from the alarm source to query all history alarms.
[Normal Result]
No frequent abnormal alarm or alarms occur and the alarm history query displays
normal results.
Analyze the abnormal alarms or frequent alarms in detail. Find the causes, and resolve
the frequent or abnormal alarms as appropriate.
2.2.3.3 24-Hour BTS History Notification Messages Querying and Handling
[Tools]
[Test Procedure]
1.
management.
2.
i.
Select the Information as Alarm Type.
ii.
Set the past 24 hours as the start time/end time, and then select BSC and OMCR
Information from the source to query all history notification messages.
[Normal Result]
No frequent exception notification message occurs and the notification message query
displays normal results.
Analyze the frequent exception notification messages in detail. Find the causes, and
resolve the notification messages.
Important
122
Chapter 2
Routine Maintenance
Focus on history notification messages related to BTS and Abis interface transmission
during history notification messages analysis.
2.2.3.4 Real Time BTS Cells Status Querying and Handling
[Tools]
ZXG10 Dynamic data management interface in the iOMCR client
[Test Procedure]
1.
Click Configuration Management in the iOMCR topological view and select

Dynamic data management.
2.
In the left pane of ZXG10 Dynamic Data Management interface of the

iOMCR client, do the following:
i.
To display the configurations and real-time status of the traffic and signaling
channels of the current cell, right-click the BTS Site Manager > Cell, and select
QueryChanStastic.
ii.
To display the real-time status of the channels of transceivers, click Cell > TRX.
Right-click in the lower-right pane and click Refresh.
[Normal Result]
The status of the cell channel is normal and there is no blocked channel. Traffic
channels are seized in real-time.
Refer to BTS alarms in the alarm management interface to resolve the blocked
channels of the BTS. If there is no or abnormal channel seizure (for example, the
channel is released once it is seized), use alarm management with signaling tracing to
resolve.
2.2.3.5 Daily Cells Performance Report Analysis
[Tools]
ZXG10 Performance analyzer interface in the iOMCR client
[Test Procedure]
1.
Click Performance Management in the iOMCR topological view and select

Performance analyzer.
123
2.
In the ZXG10 Performance Analyzer interface, select Report > Create

Performance Report from the menu bar to create a cell performance report.
[Normal Result]
The performance indices in the report are normal.
Resolve the abnormal indices in the performance report as appropriate.
2.2.4 Inspection and Maintenance on Indoor/Outdoor Cables

This section describes the content and methods of daily routine inspection and
maintenance for indoor/outdoor cables (including antenna feeder system).
2.3 Weekly Maintenance

2.3.1 Cleaning Equipment
[Operation Guide]
In the equipment room, check the equipment and ensure that there is no cobweb or
dust.
The equipment should be clean and tidy.
Clean the equipment in time, especially the dust-proof plug-in box.
2.3.2 BSC Check

2.3.2.1 Checking BSC Clock Status
[Preparation]
[Operation Guide]
1.
Check the status of CLKG panel indicators, and make sure that external
connections of the CLKGs rear board are normal.
124
Chapter 2
Routine Maintenance
2.
Enter Fault Management to check whether there is any clock alarm.
3.
Check whether the system clock of boards is normal and whether the foreground
and background clock data are consistent.
Table 2.3-1 describes CLKG board panel indicators.
Table 2.3-1
Name
Color
Indicators on CLKG (CLKG) Panel
Meaning
Description
RUN
Green
Running indicator
ALM
Red
Alarm indicator
ENUM
Yellow
Board extraction
indicator
ON: Indicates that the micro switch is turned on; the

board is not inserted to the correct position, software
version is not downloaded.
Flashing at 5 Hz: Indicates that the micro switch alarm;
during the boards running, the micro switch is turned
on and has alarm.
Flashing at 1 Hz: Indicates that the board can be
extracted; during the boards running, the micro switch
is turned on, the board, which is standby or does not
use resource, can be extracted.
OFF: Indicates that the micro switch is normal.
ACT
Green
Active/standby indicator
ON: Indicates that the board is active.

OFF: Indicates that the board is standby.
CATCH
Green
Catching indicator
ON: Indicates that the board is in the catching status

(i.e. it has reference), and is not locked.
TRACE
Green
Tracing indicator
ON: Indicates that the board is in the tracing status (i.e.

it has reference), and is locked.
KEEP
Green
Keeping indicator
ON: Indicates that the board is locked, but then the

reference is lost.
FREE
Green
Free running indicator
ON: Indicates that the board is not locked and has no

reference, and the board is the status of free running.
Reference indicator
This indicator is used to indicate the clock reference

selected by the CLKG board.
ON: Indicates that the selected reference is the first 2
Mbps clock reference transmitted in the form of HDB3
coding, which is provided by BITS equipment.
2 Mbps1
Green
2 Mbps2
Green
Reference indicator

ON: Indicates that the selected reference is the second
2 Mbps clock reference transmitted in the form of
HDB3 coding, which is provided by BITS equipment.
2 MHz1
Green
Reference indicator

ON: Indicates that the selected reference is the first 2
125
Name
Color
2 MHz2
Green
8 K1
Green
8 K2
Green
8 K3
Green
Meaning
Description
MHz clock reference transmitted in the form of TTL
difference, which is provided by BITS equipment.
Reference indicator

ON: Indicates that the selected reference is the second
2 MHz clock reference transmitted in the form of TTL
difference, which is provided by BITS equipment.
Reference indicator

ON: Indicates that the selected reference is the line 8K
reference provided by board such as DTB and APBE.
Reference indicator

ON: Indicates that the selected reference is the 8K
clock reference provided by GPS board.
Reference indicator

ON: Indicates that the selected reference is the 8K
clock reference provided by UIMU or UIMC.
NULL
Green
Reference indicator

ON: Indicates that there is no available external
reference, and the system is in the status of free
oscillating.
QUTD
Red
Reference deterioration
indicator
ON: Indicates the currently selected reference

deterioration.
Green
Allow-manual-referenceselection indicator
ON: Indicates that the reference can be selected

manually.
OFF: Indicates that the reference can not be selected
manually.
MANI
The RUN indicator and ALM indicator are combined to indicate various status of the
board. Table 2.3-2 describes the meaning of various combinations of RUN and ALM.
Table 2.3-2 Meanings of RUN/ALM Indicator Combinations

Status
RUN Status
Normal
Periodically flashing at
running
1 Hz
Version
download
5 Hz
ALM Status
Meaning
Always OFF
Normal running
Always OFF
Version being downloaded
Periodically flashing at 5 Hz
Version download fails: the

boards version is inconsistent
1 Hz
with the configuration.

Always ON
Always OFF
126
RELEASE version indicates
Chapter 2
Routine Maintenance
that the version download

succeeds and the version is
being started.
Self-test failure
Always OFF
Boards self-test failure.
Always OFF
Operation
support
system
startup failure.
Fault
during
alarm
the
5 Hz
running
process
5 Hz
Logical
address
obtaining
failure.
Basic process power-on failure

or timeout.
Core data area initialization.
Periodically flashing at 0.5
Version and hardware are
5 Hz
Hz
inconsistent
5 Hz
with
the
configuration.
2 Hz
Media plane communication is

disconnected.
HW is disconnected.
Link break with OMP.
Active/standby changeover is
2 Hz
1 Hz
1 Hz
being performed.
Always ON
Hardware clock is lost.
1 Hz
1.
Check whether the TRACE indicator is ON and decide whether the CLKG
board is in the tracing status.
2.
Check the external clock cables of the rear board RCKG1 and ensure that the
connection is normal.
CLKG gets the clock from A-interface. Check connections at the clock input
interface of the rear board RCKG1 and ensure that they are consistent with the
configuration data. Check the connections and connectors and ensure that they
are normal.
3.
Perform CLKG active/standby changeover.
4.
Replace the other external clock reference or reset the corresponding A-interface
127
PCM.
5.
Replace the board.
2.3.2.2 Checking OMP/CMP

[Preparation]
[Operation Guide]
1.
Check whether the link between foreground and background can be established
successfully, and check whether the active/standby status of OMP/CMP is
normal.
2.
Enter Dynamic Data Management and open the BSC rack view. Right-click
OMP or CMP and click CPU1 or CPU2 in the pop-up menu, and click Query
CPU occupation rate in the pop-up menu. The CPU occupancy is displayed in
the Operation Result dialog box.
3.
Check whether OMP/CMP has any abnormal alarm.
The link between foreground and background is established successfully. There is no
abnormal alarm. It is recommended that CPU occupancy is not larger than 80%.
1.
If the boards CPU occupancy is too large, check whether there is any traffic
peak. If CPU occupancy exceeds 95%, unplug some LAPD boards to reduce the
traffic.
2.
Enter Fault Management to view alarms.
3.
If
the
boards
active/standby
status
is
unknown,
check
the
foreground-background communication link and ensure that the link is normal.

Check connections and connectors between the ISMG server, foreground, and
OMP (or CMP), and ensure that they are normal. Check whether the HUB and
the switch is power-down, and ensure that they work normally.
4.
Check the data and version configuration of OMP (or CMP) at foreground and
128
Chapter 2
Routine Maintenance
background, and ensure that the configurations at foreground and background

are consistent.
5.
Perform OMP or CMP active/standby changeover.
6.
Reset OMP or CMP.
7.
Unplug and plug OMP or CMP and ensure that the board is plugged in properly.
If problem still exists, replace the board.
2.3.2.3 Querying BSC Alarms Real-Time Statistics

[Preparation]
[Operation Guide]
1.
To query the statistics of current and history alarms, enter Fault Management
and click Query Realtime Alarm Monitor.
2.
In the Realtime Alarms tab, click
in the toolbar, as shown in Figure 2.3-1,
and Save dialog box pops up.
Figure 2.3-1
3.
Saving Realtime Statistics Alarm (1)
In the Save dialog box, select the saving path and click Save.
Real-time alarms of BSC are saved successfully.
129
2.3.2.4 Analyzing History Alarms of the Past Week

[Preparation]
[Operation Guide]
1.
Enter Fault Management and click Query History Alarm Statistics.
2.
Report Management tab appears, as shown in Figure 2.3-2.
Figure 2.3-2
3.
Report Management Tab
Create a new report template and then double-click the new template, or
double-click an existing template. The report parameter input interface pops up,
130
Chapter 2
Figure 2.3-3
4.
Routine Maintenance
Report Parameter Input Interface
Select appropriate parameters, set Happen Time to be the past week, and click
OK.
5.
The statistics result is generated automatically, as shown in Figure 2.3-4.
131
Figure 2.3-4
Alarm Statistics Result
Analyze history alarms according to actual requirements.
2.3.2.5 Analyzing Performance Indices
[Preparation]
[Operation Guide]
1.
Enter Performance Management, and establish the performance statistics

measurement task.
2.
Perform the measurement task. There are two types of measurement tasks.
1)
KPI
KPI data are provided by foreground equipment to the background ISMG,
operation personnel do not have to change any setting.
2)
Performance measurement statistics

Check the collected performance measurement data, and terminate unnecessary
performance measurement tasks.
3.
Implement the performance data query, and the query time is the past week.
4.
Export the data. Select appropriate export options and save the performance data
query result.
1.
KPI data can be reported to background ISMG.
2.
Performance measurement data can be reported correctly. For details of

performance counters, refer to ZXG10 iBSC (V6.10) Performance Counter
Manual.
3.
The performance statistics result can be generated into report, and all indices in
the report are normal.
132
Chapter 2
Routine Maintenance
Check and ensure that the data configuration is correct. Check and ensure that the
hardware is not faulty.
2.3.2.6 Checking Server Running Status
[Preparation]
[Operation Guide]
1.
Click View System Management to enter System Management.
2.
In the System Management tab, select Self Office:OMC node and click
ApplicationServer Server Performance, as shown in Figure 2.3-5.
Figure 2.3-5
3.
Querying Server Performance
The server performance query interface pops up, as shown in Figure 2.3-6.
133
Figure 2.3-6
Server Performance Query Interface
For Windows, the usage of system directory C:\ on the hard disk can not be 100%.
For SOLARIS, the usage of directory / and /export/home can not be 100%.
For LINUX, the usage of all directories can not be 100%.
CPU usage and RAM usage can not be 100% for a long time.
Clear unnecessary files such as log files, redundant backup data, or software.
2.3.2.7 Checking Occupied Space of Database at ISMG Server
[Preparation]
134
Chapter 2
Routine Maintenance
[Operation Guide]
1.
Click View System Management to enter System Management. In the

System Management tab, log in the database.
2.
Select the Oracle node, and click DatabaseServer View Database

Resources, as shown in Figure 2.3-7.
Figure 2.3-7 View Database Resources
3.
View Database Resources dialog box pops up, as shown in Figure 2.3-8.
Figure 2.3-8 View Database Resources Dialog Box
4.
In View Database Resources dialog box, pay attention to the following eight
table spaces and calculate the percentage of remaining space of each table space:
GSM_CBC,
GSM_CBCINDEX,
135
GSM_PM,
GSM_PMINDEX,
UEP,
UEPINDEX, UEP_CAF_FM, and UEP_CAF_FMINDEX.

Note
There might be two or more table spaces that have the same name.
For each table space, the percentage of remaining space is equal to the remaining space
/ the allocated space.
The percentage of remaining space of each table space can not be lower than 20%.
Notify the local ZTE office to expand the database table space.
2.3.2.8 Configuration Data Backup
[Preparation]
[Operation Guide]
Enter Configuration Management and log in the database. Then perform
configuration data backup.
Manual backup
1.
Click Data Management Data Backup.
2.
Data Backup dialog box pops up, as shown in Figure 2.3-9.
136
Chapter 2
Figure 2.3-9
3.
Routine Maintenance
Data Backup Dialog Box
Set Storage path and select the Network Element (NE) to backup from the tree
in the Select managed elements to backup area, and click OK.
4.
Data Backup Result dialog box pops up, as shown in Figure 2.3-10. Click
Close.
Figure 2.3-10
137
Data Backup Result Dialog Box
Automatic backup
1.
In the System Management tab, select the Oracle node, and click
DatabaseServer Table Collection Operations, as shown in Figure 2.3-11.
Figure 2.3-11 Selecting Table Collection Operations
2.
In the pop-up Table Collection Operations dialog box, right-click the Table
collection of CM Management node, and click Create in the pop-up menu, as
Figure 2.3-12
Creating Table Collection of CM Management
Note
The content of Table Collection of CM Management can be viewed by right-clicking
138
Chapter 2
Routine Maintenance
the Table Collection of CM Management node and clicking Detail in the pop-up
menu.
Creating new table collection task might be unnecessary, Instead, the default table
collection task, Table backup of CM Management can be used.
Right-click a table collection task and click Manually Execute in the pop-up menu,
Table Collection Manually Execute dialog box pops up. Modify settings according to
the dialogs prompt (Step 1 ~ Step 3) to manually execute the table collection backup
task, and the execution result.
3.
Create Table Collection Task dialog box pops up, as shown in Figure 2.3-13.
Figure 2.3-13
4.
Create Table Collection Task Dialog Box (1)
Complete the settings according to the dialogs prompt (Step 1 ~ Step 4), set
Periods Model to Week, and click Finish, as shown in Figure 2.3-14.
139
Figure 2.3-14
Create Table Collection Task Dialog Box (2)
Configuration data backup is performed successfully.
2.3.2.9 Virus Scanning
[Preparation]
Virus scanning is mainly performed at ISMG client. If SVR or SBCX adopts Windows
operating system, virus protection must be implemented.
[Operation Guide]
1. Make sure that the automatic update function of the antivirus software is enabled,
or update the virus library periodically.
2.
Make sure to customize the periodical virus-scanning task and real-time virus
monitoring task.
The virus library is updated successfully.
140
Chapter 2
Routine Maintenance
The periodical virus-scanning task and real-time virus monitoring task are
performed normally.
2.3.3 BTS Check

2.3.3.1 Past Week History Alarms Querying and Handling
[Tools]
ZXG10 Alarm management interface in the iOMCR client
[Test Procedure]
1.
Click Fault management in the iOMCR topological view and select Alarm
management.
2.
i.
Select the History Alarm as Alarm Type.
ii.
Set the past week as the start time/end time, and then select BSC to be queried
from the alarm source to query all history alarms.
[Normal Result]
The indices in the alarm query result are normal. There is no alarm that occurs often.
Analyze in detail the alarms that occur often. Find their causes and remove them.
2.3.3.2 Past Week History Notification Messages Querying and Handling
[Tools]
ZXG10 Alarm management interface in the iOMCR client
[Test Procedure]
1.
Click Fault management in the iOMCR topological view and select Alarm
management.
2.
i.
Select the Information as the Query Type.
141
ii.
Set the past week as the start time/end time, and then select BSC to be queried
from the alarm source to query all common notification messages.
[Normal Result]
No frequent exception notification message occurs and alarm query displays normal
results.
Analyze in detail the exception notification messages that often occur, find their causes
and remove them. Check the quality of the relevant transmission link for the
notification messages that often occur at the Abis transmission interface, such as slip
notification message and Rx alarms.
2.3.3.3 Alarm Frequency Analysis
[Tools]
Alarm management interface in the iOMCR client
[Test Procedure]
1.
Click ZXG10 Fault management in the iOMCR topological view and select
Alarm management.
2.
In the ZXG10 Alarm Management interface, select File > Alarm Statistics >
Alarm Frequency Statistics from the menu bar to see Alarm Frequency
Statistics window.
i.
Select relevant BTS from the Source tab.
ii.
Set the past week as the start time/end time from the Time tab. Click on the
Custom radio option below and select 30 from the list item to be read as The
Most 30 Kinds of Alarms.
[Normal Result]
Alarm frequency analysis results are normal.
Analyze in detail the alarms that often occur, find their causes and remove them.
2.3.3.4 Weekly Cell Performance Report Analysis
[Tools]
142
Chapter 2
Routine Maintenance
ZXG10 Performance Analyser interface in the iOMCR client

[Test Procedure]
1.

Performance analyser.
2.
In the ZXG10 Performance Analyser interface, select Report > Create

[Normal Result]
The performance indices in the report are normal.
Resolve the abnormal indices in the performance report as appropriate.
2.3.4 Inspection and Maintenance on Indoor/Outdoor Cables

This section describes the content and methods of weekly routine inspection and
maintenance for indoor/outdoor cables (including antenna feeder system).
2.4 Monthly Routine Maintenance

2.4.1 Inspection and Maintenance in equipment room
This section describes the content and methods of monthly routine inspection and
maintenance for equipment room.
2.4.2 BSC Check

2.4.2.1 Checking Board Software Version
[Operation Guide]
1.
In the Software Version Management tab, double-click the BSC rack node in
the left Configuration Resource Tree. BSC rack tab appears on the right.
Right-click the board of which the software version is to be checked, and click
relevant software version query in the pop-up menu, as shown in Figure 2.4-1.
143
Figure 2.4-1
2.
Querying Software Version of Board
Appointed Board Running Version Query dialog box pops up, as shown in
Figure 2.4-2.
Figure 2.4-2
3.
Appointed Board Running Version Query Dialog Box
Double-click the BSC software management node in the left Configuration

Resource Tree, and select BSC general software tab on the right to view the
information of BSC general software, as shown in Figure 2.4-3.
144
Chapter 2
Figure 2.4-3
4.
Routine Maintenance
Board Database Version Information
Select the BSC specific software tab to view the information of some specific
software version.
5.
Compare the boards database version information and the boards running
version information.
6.
The process of checking the site software version and database configuration
version is similar to that of BSC. Double-click relevant site rack node and site
software management node in the Configuration Resource Tree to view the
corresponding information.
None
Upgrade the software if the following two cases are found:
BSCs running software version is inconsistent with the configured software
version.
The sites running software version is inconsistent with the database
configuration information.
2.4.2.2 Checking Clock Synchronization
[Operation Guide]
1.
Check the Clock check setting of each shelf and ensure that the Clock check
145
drop down menu is set to Yes, as shown in Figure 2.4-4.
Figure 2.4-4
2.
Setting Clock Check Property
Check A-interface configuration of SPB/DTB. Check input cables of the CLKG

board and make the external standard clock extracted by SPB/DTB reach the
CLKG board.
The TRACE indicator on the active CLKG board panel is ON and green.
1.
Check indicators on the CLKG board panel to decide the running status of
CLKG. If the FREE indicator is green and ON, it indicates that the CLKG is in
free oscillating status and it is required to reset the corresponding A-interface E1
circuit.
2.
Check and ensure that the external cable connections of the CLKGs rear board
RCLKG are normal.
3.
Perform CLKG active/standby changeover and check the board working status.
4.
Replace the CLKG board if the board is faulty.

146
Chapter 2
Routine Maintenance
2.4.2.3 Checking Automatic Backup Clearing Function of Database

[Operation Guide]
1.
Check
the
configuration
management
backup
files
under
/home/iomcr/ums-svr/backup/sysmanager/cm at the server and ensure that there

is no backlog of files.
2.
Check
the
fault
management
backup
files
under
/home/iomcr/ums-svr/backup/sysmanager/fm at the server and ensure that there

3.
Check
the
performance
management
backup
files
under
/home/iomcr/ums-svr/backup/sysmanager/pm at the server and ensure that there

4.
Check
the
log
management
backup
files
under
/home/iomcr/ums-svr/backup/sysmanager/log at the server and ensure that there

5.
Check the performance configuration management backup files under

/home/iomcr/ums-svr/backup/sysmanager/ueppm at the server and ensure that
there is no backlog of files.
There is no backlog of backup files.
If backup files are not deleted in time, click DatabaseServer Table Collection
Operations. Set the backup file to be deleted periodically. For details, refer to the
contents related to database table collection operations in the ZXG10 ISMG (V6.10)
Operation & Maintenance Center Operation Manual (Security Management and
System Management.
2.4.2.4 Updating Operating System Patch
The operating system patch upgrade includes upgrading ISMG servers patch and
upgrading ISMG clients patch.
[Operation Guide]
147
ZTE Corporation issues technical notice periodically. The operating system patch is
upgraded with the aid of local ZTE office.
2.4.2.5 Checking Optical Interface Protective Cap
[Operation Guide]
Check the idle optical interface of the board and ensure that it has the protective cap.
2.4.3 BTS Check

2.4.3.1 Monthly Cell Performance Report Analysis
[Tools]
ZXG10 Performance Analyser interface in the iOMCR client
[Test Procedure]
1.

Performance analyser.
2.
In the ZXG10 Performance Analyser interface, select Report > Create

[Normal Result]
The performance indices of the cells are stable.
Focus on the optimization on the cell with the poorest performance. Analyze the cells
with significant index changes in detail, and locate the causes.
2.4.3.2 Spare Parts Check
[Tools]
None
[Test Procedure]
1.
Check the spare part warehouse and conditions against the spare parts list.
2.
Keep the damaged parts separate from the new and good-conditioned parts.
Mark the items for convenience.
[Normal Result]
148
Chapter 2
Routine Maintenance
The spare parts are complete and in good condition.

Arrange supplementary common spare parts in time before these parts are used.
2.4.4 Indoor and Outdoor Cables Check

This section describes how to check and maintain indoor and outdoor cables (including
feeder system) during monthly maintenance.
2.5 Quarterly Maintenance

2.5.1 Equipment Room Maintenance
2.5.1.1 Burglarproof Nets, Windows, Doors, and Other Items Check
[Tools]
None
[Test Procedure]
Check the burglar nets, windows, doors and other items.
[Normal Result]
The burglar nets, windows and doors are intact.
Repair the items in time if they are damaged.
2.5.1.2 Equipment Room Temperature Check
[Tools]
None
[Test Procedure]
Observe the temperature in the equipment room from the thermometer.
Long-term operating temperature: 15 C to 30 C
Short-term operating temperature: 0 C to 45 C
149
Adjust the air conditioner(s) to maintain the normal temperature conditions.
2.5.1.3 Equipment Room Humidity Check
[Tools]
None
[Test Procedure]
Check the humidity in the equipment room from the hygroscope.
Long-term operating room-humidity: 40 %
65 %
Short-term operating room-humidity: 20 % to 90 %

Adjust the air conditioner(s) to maintain the normal humidity conditions.
2.5.1.4 Equipment Room Air Conditioner(s) Check
[Tools]
None
[Test Procedure]
Check the operation of the air conditioner(s) in the equipment room and clean the air
filters periodically.
[Normal Result]
Air conditioner(s) ensures the normal and effective cooling of the equipment room.
Repair the air conditioner(s) in time.
[Exit from Test]
None
2.5.1.5 Equipment Room Cleanliness Check
[Tools]
150
Chapter 2
Routine Maintenance
None
[Test Procedure]
Check if the equipment room floor, cabinets, doors and windows, equipment
documentation, and equipment interior and floor are clean.
[Normal Result]
All facilities remain clean and tidy without obvious dust.
Clean the dust. Find out the reasons of poor dust conditions and take the corresponding
dustproof measures.
[Precautions]
None
2.5.1.6 Equipment Room Lighting Check
[Tools]
None
[Test Procedure]
Check the general lighting and emergency lighting in the equipment room.
[Normal Result]
The lighting is normal and covers every corner.
Repair the damaged lighting facilities in time.
[Exit from Test]
None
2.5.1.7 Equipment Room Sockets Check
[Tools]
None
[Test Procedure]
Check if the sockets in the equipment room are normal.
151
[Normal Result]
The sockets in the equipment room are normal.
Repair the sockets in time if the sockets are damaged.
2.5.1.8 Equipment Room Safety Check
[Tools]
None
[Test Procedure]
Check for the disaster protection facilities, equipment protection, and firefighting
facilities in the equipment room.
[Normal Result]
The equipment room includes handheld fire extinguishers that have normal pressure
and fall within the validity period. The equipment room is rodent-free and insect-free.
Repair or replace the damaged firefighting facilities in time.
[Precautions]
None
2.5.1.9 Environmental Alarm Collection Facilities Check
[Tools]
None
[Test Procedure]
Check the environment alarm collection items such as temperature, humidity, fire
alarm, power supply, and burglarproof facilities in the equipment room.
[Normal Result]
The environment alarm collection facilities in the equipment room are normal.
Repair or replace the damaged environment alarm collection facilities in time.
152
Chapter 2
Routine Maintenance
[Precautions]
None
2.5.2 BSC Check

2.5.2.1 Checking Power Supply
[Operation Guide]
1.
Check and ensure that the AC power of server and client is normal.
3.
Check and ensure that the -48 V power supply of rack equipment is normal.
4.
Check and ensure that the standby battery (if there is any) is normal.
5.
Check the batteries and ensure that there is no leaking liquid, and make sure that
the cable connections are reliable.
6.
Keep the batteries clean. For long-term storage, charge the battery periodically.
1.
The power supply for the server, the client, and BSC rack is normal. There is no
power alarm.
2.
The power cable is not old.
3.
There is no corrosion at the connection point.
2.5.2.2 Checking Cable Connections

Table 2.5-1 describes the types of ZXG10 iBSC cables.
Table 2.5-1 ZXG10 iBSC Cable Types

Category
BSC internal cables
Type
Clock cable
Control-plane interconnection cable
User-plane interconnection cable
PD485 cable and fan monitoring cable
Power supply system cable
Grounding system cable
BSC external cables
Monitoring system cable

Transmission system cable
153
Power system cable

Grounding system cable
ISMG Ethernet cable
[Operation Guide]
1.
Check and ensure that the cable layout (such as power cable, grounding cable,
transmission cable, and jumper) is clean and tidy. Make sure that the label is
stuck on the cable firmly.
2.
Make sure that the cable connections are correct.
If the cable label falls off, stick the label to the cable in time. The equipment name (ID)
and detailed interface position should be marked on the label as: Rack number Shelf
number Board number Interface number, or, Equipment name (ID) Interface
number.
2.5.2.3 Checking Fan Plug-in Box Working Condition
The fan plug-in box monitors and performs automatic rate adjustment, forming a
closed wind channel through which wind comes in from the bottom and goes out from
the top in the cabinet. The fan plug-in box cools the equipment with wind flow.
[Operation Guide]
1.
Check whether there is any fan plug-in box alarm.
2.
Check the running condition of each fan in the fan system and ensure that there
is no abnormality such as abnormal sound or the vane touching the cabinet.
3.
Clean the fan system periodically.
The fan plug-in box has no alarm and all fans work normally.
If abnormality is found in the fan, replace the faulty fan. For operation details, refer to
ZXG10 iBSC (V6.10) Base Station Controller Installation Manual.
154
Chapter 2
Routine Maintenance
2.5.2.4 Checking Anti-Static Wrist Strap

In dry environment, the static electricity accumulated in human body might cause
high-voltage static electricity. If the operator touches the electronic devices with static
electricity in the body, the device might be damaged. Wearing the anti-static wrist strap
can discharge the static electricity in human body and avoid device damage. Therefore,
the operator must wear the anti-static wrist strap before touching the equipment, and
holding the board, circuit board, or IC chip. The other end of the anti-static wrist strap
must be grounded.
[Operation Guide]
Check the anti-static wrist strap of each rack and make sure that they are installed in
correct positions and have good contact.
2.5.2.5 Checking Spare Materials and Parts
[Operation Guide]
1.
Check the spare materials and parts with the list of spare materials and parts.
2.
For common spare materials and parts, supplement them in time if they are used
up.
The spare materials and parts are sufficient and not damaged.
2.5.2.6 Checking Grounding Conditions
[Operation Guide]
1.
Check
various
grounding
cables
(PGND,
-48
VGND),
user
grounding-connector-bar connections, and DDF grounding cables, and ensure

that they are safe and reliable.
2.
Use the grounding resistance tester to measure the grounding resistance and
record the value.
1.
All connections are safe and reliable, and there is no corrosion at the connection
point.
155
2.
The grounding cable is not old.
3.
The grounding connector bar has no corrosion. The corrosion protection is

performed appropriately.
4.
The joint grounding resistance is less than 1 .
1.
Check the grounding connector bar and ensure that it is normal.
2.
Check the grounding cable. If it is old, replace the grounding cable.
3.
Check the connector. If it has corrosion, remove the corrosion. If the corrosion is
critical, replace the relevant part.
4.
Measure the joint grounding resistance and ensure that it is less than 1 .
2.5.2.7 Cleaning Air Filter

The air filter must be cleaned periodically, usually once a month or once a quarter,
according to the equipment room environment conditions.
1.
The air filter which is added to the air intake at the rack bottom: it uses ABS
plastic as the frame, with nylon net inside. The air filter is flexible.
2.
The door air filter: it uses metal as the frame, with polyurethane second foaming
plastic inside.
Both types of air filters can be reused after cleaning, and are easy for installation and
disassembling.
[Operation Guide]
1.
Remove the fixing screws of the dust-proof plug-in box on the rack and then
pull the dust-proof plug-in box out of the rack, as shown in Figure 2.5-1.
156
Chapter 2
Routine Maintenance
Figure 2.5-1 Pulling Dust-Proof Plug-in Box out of Rack
2.
Disassemble the dust-proof plug-in box and take out the air filter.
3.
Clean the air filter with lukewarm water (less than 40 C) and dry it.
4.
Install the air filter into the dust-proof plug-in box.
5.
The air filter installation is the reverse of the process of taking the air filter out.
6.
Install the dust-proof plug-in box into the rack. The dust-proof plug-in box
installation is the reverse of the process of taking the dust-proof plug-in box out.
7.
For the door air filter, the cleaning process is similar to that of the air filter
inside the dust-proof plug-in box.
Caution
The air filter must be dried before being installed into the dust-proof plug-in box.
2.5.3 BTS Check

2.5.3.1 Conversation, Coverage, and Handover Test
[Tools]
Test MS and drive testing tools
[Test Procedure]
Test the conversation, coverage and handover of the BTS with a test MS and drive
testing tools.
157
[Normal Result]
The conversation quality is good. There is no call loss during the handover, and the
BTS coverage is normal.
Resolve the problems found during the tests.
2.5.3.2 Amplifiers Output Power Measurement
[Tools]
1.
One 3 1/2 digital multimeter
2.
One 150 W through-line power meter
3.
Several RF cables
4.
Other metals
[Test Procedure]
1.
Turn off the DTRU power supply, which is located on the front panel of the
PDM, as shown in Figure 2.5-1.
Figure 2.5-1
DTRU Power Supply
Table 2.5-2 shows the relation between power supplies DTRU1~DTRU9 and the
frequencies they control.
Table 2.5-2 Power Supply DTRU1~DTRU9 and Frequencies
158
Chapter 2
Power
Supply
DTRU1
DTRU2
DTRU3
DTRU4
DTRU5
DTRU6
2.
Power
Frequency
Layer-3
frequency
Layer-3
frequency
frame,
frame,
Frequency module 2
Layer-3
frequency
frame,
Frequency module 3
Layer-2
frequency
frame,
Frequency module 1
Layer-2
frequency
frame,
Frequency module 2
Layer-2
frequency
Frequency module 3
Frequency
Supply
Frequency module 1
frame,
DTRU7
DTRU8
DTRU9
Routine Maintenance
Layer-1
frequency
frame,
Frequency module 1
Layer-1
frequency
frame,
Frequency module 2
Layer-1
frequency
frame,
Frequency module 3
If Transceiver Unit (TRU) does not output power on turning off the power
supply, loosen the cable connectors from the amplifier output end to AEM, and
connect the cable connectors with a through-line power meter and a large-power
load.
Caution
If the connector is not connected with any antenna, it must be connected with a 100 W
microwave power load. If power load is connected with an antenna, then it does not
need to be connected with any load
3.
Turn on the power and add the stimulation (there is output from the DTRU).
4.
Read the power of the set frequency band (GSM900: 925 MHz 960 MHz;
GSM1800: 1805 MHz 1880 MHz). In the case of full power, read the output
power and the gain flatness.
[Normal Result]
GMSK: 60 W;
8PSK: 40 W.
1.
Check if the power control parameters are correctly configured.
2.
Check if the RF cables between module and feeder antenna are reliably
connected.
159
3.
Measure the output power from module to antenna. Determine the fault and
replace faulty modules.
Common problems of a power amplifier include power amplifier module damages and
amplifier tube damages. These problems are caused by low gain and decreased output
power. If the power amplifier causes the fault, replace the module.
[Exit from Test]
Remove the connections between the through-line power meter, large power load, and
the amplifier output end. Restore the connection between the amplifier output end and
the AEM.
2.5.3.3 VSWR Measurement
[Tools]
1.
SiteMaster
2.
50 SMA (M) matching load
3.
SMA torque spanner
4.
One N(M), -N(M) testing cable
[Test Procedure]
1.
Turn on the power switch of SiteMaster.
2.
Select OPT in the main menu.
3.
Select the items to be measured (SWR, RL, CL) by pressing the B1 key.
4.
Select the FREQ key in the main menu, and enter start and stop scanning
frequencies.
5.
Select the START CAL key to calibrate the measuring instrument as follows:
1)
Connect the circuit breaker (OPEN) with TEST PORT and select ENTER.
2)
Connect the shorter (SHORT) with TEST PORT and select ENTER.
3)
Connect the 50 load with TEST PORT and select ENTER.
6.
In SCALE of the main menu, enter the values of TOP, BOTTOM, and LIMIT.
For convenient query, the recommended value of TOP is 1.5 and BOTTOM is
1.0.
160
Chapter 2
7.
Routine Maintenance
In the FREQ menu, select MARKER and then select EDIT. Read the values.
Examine if these values meet the requirements and then save them.
[Normal Result]
VSWR is less than 1.5.
If the test result is not normal, use the fault location function (DTF) to find the position
of the fault and its cause. Remove the fault as appropriate.
[Exit from Test]
Reconnect the connector of the equipment and restore the system.
[Precautions]
1.
Calibrate the measuring instrument before power-on for measurement
2.
If measurement is conducted during equipment running, it is necessary to notify

the customer or get the customer's approval. Lock the relevant sectors then
switch off the relevant power and perform the test (measurement during
equipment running is not recommended).
3.
During measurement, observe the running status of the equipment with care.
2.5.3.4 Clock Calibration (Optional for the BTSs with Internal Synchronization)
[Tools]
Frequency meter, notebook computer installed with LMT software
[Test Procedure]
1.
Set the BTS to the internal synchronization mode in iOMCR.

In iOMCR, select Configuration Management > Integrated Configuration
Management > PhyView. Right-click Physical Site, select Site Attribute from
the popup menu and set the synchronization mode after entering the Attribute
interface.
2.
Connect the frequency meter to the 13 MHz clock test port at the cabinet top.
3. Connect the serial port on the notebook computer to the External Test Port (ETP)
of the CMM.
161
4.
Start LMT in the computer and click
(the CLK Calibrate icon) in the
menu to enter the CKU calibration interface.

5.
Press Start to start communication with the BSC. When the program starts, only
the Start button is available and all other buttons are unavailable. After the
communication with BSC starts, the Start button becomes available and all
other buttons such as Calibrate becomes unavailable.
6.
The current CKU values shown in the CKU calibration interface include DAC
value and voltage.
Note
Calibrate the DAC value in the calibration group box. Enter a DAC value manually or
use the arrows to adjust the DAC value. The Step value determines the length of each
increase or decrease in the DAC value. Three options are available: 1, 3 and 10. After
specifying the DAC value, the system calculates the corresponding voltage
automatically. Press the Calibrate button to notify the BSC to start calibration.
Observe the frequency meter until the clock adjusts to 13 MHz.
7.
Press Save to save the DAC value in the Flash memory, and the system adopts
the value saved in Flash memory at the reboot. Save the new DAC value before
rebooting the system otherwise the system uses the old DAC value saved earlier
in Flash memory.
8.
Press End to terminate the calibration.
[Normal Result]
The clock calibrates to 13.000000 MHz 0.025 ppm.
If the clock calibration is not possible to be in the above given range, then replace
CMM.
[Exit from Test]
Reset the BTS to its original mode if previously it works in the eternal synchronization
mode.
2.5.3.5 Cabinets Power Supply Check
[Tools]
162
Chapter 2
Routine Maintenance
Mutilmeter
[Test Procedure]
Check the DC input voltage at the cabinet top using multimeter. Check if any power
cable is aged and need to be changed.
[Normal Result]
1.
Nominal DC voltage: -48 V

Allowed fluctuation range: -57 V to -40 V
2.
No DC power cable is aged.
In case of DC power abnormalities, check for the power alarm. If there is any power
alarm, troubleshoot according to the meanings of the alarm LED and instructions of the
power equipment. Replace the aged DC power cable if any.
[Precautions]
None
2.5.3.6 Fans Check
[Tools]
None
[Test Procedure]
Check for the normal running of the fans, and the alarm on the iOMCR client.
[Normal Result]
The fans work normal with even rotational speed. There is no alarm on the iOMCR
client.
In case of the fan alarms, replace the fan plug-in box or fans.
[Precautions]
None
163
2.5.3.7 Boards (CMB, DTRU, and AEM) Running Status Check

[Tools]
None
[Test Procedure]
Check for the alarms by observing the LEDs on the CMB, DTRU, and AEM panels
and in the iOMCR client. Refer to ZXG10-B8.18 (V1.0) Base Transceiver Station
Technical Manual, for the meaning of LEDs.
[Normal Result]
The boards run normal and there is no alarm.
Table 2.5-3 shows the normal status of indicators on CMB panel.
Table 2.5-3
Name
PWR
Normal Status of Indicators on CMB Panel
Meaning
Color
Power LED
Green/Red
Normal Status
Green ON: Normal
1. Green blinking at 4 Hz/second: Boot is
RUN
Running LED
Green
running
2. Green flashing at 1 Hz/second: Application
is running
1.
SYN
Clock
synchronization
mode LED
Green
ON:
Abis
interface
network
synchronization clock
Green/Red
2. Green blinking at 1 Hz per second: SDH

network synchronization clock
3. OFF: Free oscillating
1. Green ON: Network synchronization is
locked
CLK
Clock LED
Green/Red
2. Green blinking at 1 Hz per second: Locking

the phase
3. OFF: Free oscillating
MST
Active/Standby LED
Green
1. Green ON: Active state

2. Green OFF: Standby state
1. OFF: Running normally
2. Green blinking at 1 Hz per second: System
STA
Status LED
Green/Red
initialization.
3. Green blinking at 4 Hz per second:
Software loading
164
Chapter 2
Routine Maintenance
Table 2.5-4 shows the normal status of indicators on DTRU panel.
Table 2.5-4
Name
PWR
Normal Status of Indicators on DTRU Panel
Meaning
Power LED
Color
Green/Red
Normal Status
Green ON: Normal
1. Green blinking at 1 Hz/second: Boot is running
RUN
Running LED
Green
2. Green flashing at 4 Hz/second: Application is

running
1. Green ON: BCCH indication. See table note.
MOD
Mode
Green/Red
2. Green blinking at 1 Hz: BCCH indication.

System Info is broadcasting
3. OFF: Non-BCCH indication
1. Green flashing: Channel activation (SDCCH,
ACT1,
ACT2
Active
Green/Red
TCH, etc.)
2. OFF: None of the channels has traffic and is
activated.
1. OFF: running normally
2. Green blinking at 1 Hz/second: System
STA
Status
Green/Red
initialization
3. Green blinking at 4 Hz/second: Loading
software
Note: If the green MOD is always on, it indicates that DTRU does not receive System Info.
The ACT LED displays the number of activated channels. DTRU adjusts the LED control pulse width according to the
number of activated channels and thus displays the number. For details, see Table
Table 2.5-5
2.5-5.
Display of the Channel Activation LED (ACT)
Number of Activated Timeslots
LED Display
00000000,00000000
10000000,00000000
10100000,00000000
10101000,00000000
10101010,00000000
10101010,10000000
10101010,10100000
10101010,10101000
10101010,10101010
Description:
165
1.
0 indicates off and 1 indicates on.
2.
Each bit display time is Td and temporarily defined as 4 Hz (0.25 s) while the
entire status display period is 16 * Td = 4 s.
3.
For combined channels such as TCH/F, SDCCH/8, and SDCCH/4, Td can be

regarded as activated, as long as one logical sub-channel (such as an SDCCH
sub-channel) in this channel combination is activated.
4.
When some timeslots are allocated as common control channels and private
control channels (such as main BCCH channel combination and extBCCH
channel combination), the status of these timeslots is defined as inactivated and
not included in the display statistics of ACT.
5.
If extBCCH channel combination is used, the green LED flashes only when all
configured BCCH channels are normal and system messages are being sent. If
one or several extBCCH channels are blocked or defective, the red LED will
flash according to the number of channels blocked or defective. The flashing
time is the same as described above. If all the allocated extBCCHs are blocked
or defective, the red LED will be solid on.
Table 2.5-6 lists the normal status of the LEDs on Combiner Distribution Unit
(CDU) panel.
Table 2.5-6
Normal Status of the LEDs on CDU Panel
Name
Description
Color
Normal Status
FPO
Forward power output
Green
On: Normal
SWR1
VSWR level-1 alarm
Red
Off: No alarm
SWR2
VSWR level-2 alarm
Red
Off: No alarm
PWR
LNA power supply
Green
On: Normal
LNA
LNA alarm
Red
Off: No alarm
Table 2.5-7 lists the normal status of the LEDs on EDCU panel.
Table 2.5-7
Name
Normal Status of the LEDs on EDCU Panel
Description
Color
Normal Status
FPO
Green
ON: Normal
SWR1
VSWR level-1 alarm
Red
OFF: No alarm
SWR2
VSWR level-2 alarm
Red
OFF: No alarm
166
Chapter 2
Routine Maintenance
PWR
LNA power supply
Green
ON: Normal
LNA1
LNA1 alarm
Red
OFF: No alarm
LNA2
LNA2 alarm
Red
OFF: No alarm
Table 2.5-8 lists the normal status of the LEDs on CMB panel.
Table 2.5-8
Name
Description
Normal Status of the LEDs on CMB Panel

Color
PWR
Power LED
Green/Red
RUN
Running LED
Green
synchronization
Green/Red
mode LED
CLK
Clock LED
1. Red LED is on: Alarm

2. Off: Power off or other reasons
Red LED is on or flashes: The system is abnormal
1. Red LED flashes at 4 Hz: The E1 out-of-frame
System
SYN
Normal Status
alarm
2. Red LED is on: The E1 line is broken or not
connected
Green/Red
Red LED is on: Clock fault

1. Red LED flashes at 1 Hz: LAPD link
disconnection
STA
Status LED
Green/Red
2. Red LED flashes at 4 Hz: HDLC link

disconnection
3. Red LED is on: Other alarms such as temperature,
clock or frame number alarms
1.
PWR
If the red PWR LED is on or off, check through the background (or Local
Maintenance Terminal (LMT)) for LAPD link disconnection, power
over-voltage or power under-voltage alarm.
2.
RUN
If the red RUN LED is on or flashes, check through the background (or LMT)
for LAPD link disconnection alarm.
3.
SYN
1)
If the red SYN LED flashes at 4 Hz, it indicates an E1 out-of-frame alarm.
2)
If the red SYN LED is on, it indicates the E1 line broken or not connected,
check through the background (or LMT) for LAPD link disconnection alarm.
167
4.
CLK
When the red CLK LED is on, check through the background or LMT weather
there is LAPD link interruption alarm or clock abnormality alarm.
5.
STA
1)
Red STA LED flashes at 1 Hz: It indicates LAPD link interruption.
2)
Red STA LED flashes at 4 Hz: It indicates that the HDLC link is broken. Check
through the background or LMT for the alarms of the following: long HW link
disconnection, Active/standby communication link failure, communication link
failure from the extended rack to the basic rack, and communication link failure
between the basic rack and the left and right extended racks
3)
Red STA LED is on: Check through the background or LMT for the indications
of the following: forward code slip at the transmit end of an E1 interface,
reverse code slip at the transmit end of an E1 interface, forward code slip at the
receive end of an E1 interface, Reverse code slip at the receive end of an E1
interface .
Table 2.5-9 lists the abnormal status of the LEDs on DTRU panel.
Table 2.5-9
Name
Description
Abnormal Status of the LEDs on DTRU Panel

Color
PWR
Power LED
Green/Red
RUN
Running LED
Green
MOD
Channel Mode LED Green/Red
ACT1,
Channel Activation
ACT2
LED
Normal Status
1. Red LED is on: Alarm
2. Off: Power off or other reasons
Red LED is on or flashes: The system is abnormal
Red ON: BCCH blockage(including blockage on
any extBCCH)
1. Red flashes: Channel blockage (SDCCH, TCH,
Green/Red
etc)
2. Red ON: CU is forbidden
1. Red blinking at 1 Hz: LAPD disconnection
STA
Status LED
Green/Red
2. Red blinking at 4 Hz: HDLC disconnection

3. Red ON: Alarm of temperature, clock, frame
No, etc
1.
PWR
If the red PWR LED is red or off, check through the background (or Local
168
Chapter 2
Routine Maintenance
Maintenance Terminal (LMT)) for LAPD link disconnection, broken connection

between CMB and DFUC, or TPU power alarm.
2.
RUN
If the red RUN LED is on or flashes, check through the background (or LMT)
for alarm of LAPD link disconnection between DFUC and BSC, alarm of
disconnection between CMB and DFUC.
3.
MOD
If the red MOD LED is on, unblock BCCH through dynamic data management.
If the alarm persists, reset or replace the DTRU.
4.
ACT
1)
If the red ACT LED flashes, unblock BCCH through dynamic data management.
If the alarm persists, reset or replace the DTRU.
2)
If the red ACT LED flashes, reset the DTRU. If the alarm persists, replace the
DTRU.
5.
STA
1)
If the red STA LED blinking at 1 Hz, it indicates that LAPD disconnection
between DFUC and BSC.
2) If the red STA LED blinking at 4 Hz, it indicates HDLC disconnection of DTRU.
Check through the background (or LMT) for disconnection alarm between CMB
and DFUC.
3)
If the red STA LED flashes, check through the background (or LMT) for alarms
related to temperature, clock, or frame No.
Table 2.5-10 lists the abnormal status of the LEDs on CDU panel.
Table 2.5-10 Abnormal Status of the LEDs on CDU Panel

Name
Meaning
Color
Abnormal Working Status
FPO
Green
OFF: Abnormal
SWR1
VSWR level-1 alarm
Red
ON: Alarm
SWR2
VSWR level-2 alarm
Red
ON: Alarm
PWR
LNA power supply
Green
OFF: Abnormal
LNA
LNA alarm
Red
ON: Alarm
169
Table 2.5-11 lists the abnormal status of the LEDs on ECDU panel.
Table 2.5-11
Name
Abnormal Status of the LEDs on ECDU Panel

Meaning
Color
Abnormal Working Status
FPO
Green
OFF: Abnormal
SWR1
VSWR level-1 alarm
Red
ON: Alarm
SWR2
VSWR level-2 alarm
Red
ON: Alarm
PWR
LNA power supply
Green
OFF: Abnormal
LNA1
LNA1 alarm
Red
ON: Alarm
LNA2
LNA2 alarm
Red
ON: Alarm
2.5.3.8 Rack Dustproof Mesh Cleaning

There are two dustproof meshes. One is installed in the dustproof subrack and the other
is installed on the front door.
1.
To clean the dustproof mesh at the cabinet bottom, do as follows:
1)
Open the cabinet door. Loosen the two screws at the dustproof subrack. Hold the
handles and pull the dustproof subrack out of the cabinet.
2)
Loosen the fastening screws. Remove the structural components and then
remove the dustproof mesh.
3)
Clean the dustproof mesh with water or use a new one.
4)
Install the mesh to the dustproof subrack smoothly.
5)
Push the dustproof subrack to the cabinet along the guide rail. Fasten the screws
and close the cabinet door.
6)
Correctly ground the cabinet.
Caution
When removing and placing the dustproof subrack, take care not to damage the RF
cables.
2.
To clean the dustproof mesh on the cabinet door, do as follows:
1)
Open the cabinet door, remove the springs on the dustproof mesh with caution.
2)
Remove the fastening screws on the press strips and then remove the press strips
and the dustproof mesh.
170
Chapter 2
Routine Maintenance
3)
Clean the dustproof mesh with water or use a new one.
4)
Install the dustproof mesh on the cabinet door smoothly. Close the door.
2.5.4 Indoor and Outdoor Cables Check

2.5.4.1 Lightning Arresters Check
[Tools]
1.
SiteMaster
2.
50 N(F) matching load
3.
One testing cable
4.
Adapters N(M)-7/16DIN(M), N(M)-7/16DIN(F)
[Test Procedure]
The following steps describe how to check lightning arresters:
1.
Switch off the power of all TRMs of the corresponding carrier shelf on the PDM
front panel.
2.
Loosen the jumper connectors connected to both ends of the lightning arrester.
3.
Calibrate the SiteMaster.
i.
Press the START CAL button to perform zero calibration prior to the test.
ii.
Connect the short calibration terminal (OPEN) to RF/REFLECTION on the

backplane, and press ENTER.
iii. Connect the open-circuit calibration terminal (OPEN) to RF/OUT, and press
ENTER to calibrate the load.
iv. Select SAVE SETUP to save the calibration value (optional).
4.
Connect the SiteMaster to a port on the lightning arrester via testing cable.
5.
Connect the other port on the lightning arrester to the matching load.
6.
Read the SiteMaster and examine whether the return loss of the lightning
arrester is within the valid range.
7.
Repeat Steps (4) through (6) to measure the return loss of the other port on the
lightning arrester.
171
8.
Adjust the multimeter to X10K to measure the resistance of the conductor in the
high-frequency sockets at both ends of the lightning arrester.
9.
Adjust the multimeter to X1 to measure the resistance between the conductor in

the antenna and the ground.
[Normal Result]
The technical indices of the lightning arrester comply with the product specifications.
The measured value is more than 20 dB.
The resistance of the conductor in the high-frequency sockets at both ends of the
lightning arrester is more than 20 M.
The resistance between the conductor in the antenna and the ground is approximately 0
.
If the measured value is beyond the valid range, replace the lightning arresters.
[Exit from Test]
Connect the jumper connectors to the two ports on the lightning arrester. Power-on the
TRMs of the carrier shelf on the PDM panel to recover the system.
[Precautions]
Take care of the grounding connection of the lightning arrester, so that they may not be
damaged.
2.5.4.2 Grounding Cables Check
[Tools]
None
[Test Procedure]
Check if connectors of the grounding cables are loose, rusty or aged.
[Normal Result]
The connectors are not loose, rusty or aged.
Replace the grounding cables and reconnect them.
172
Chapter 2
Routine Maintenance
[Exit from Test]

None
2.5.4.3 Grounding Resistance Measurement
[Tools]
Earth resistance tester (model ZC-8)
[Test Procedure]
1.
Disconnect the grounding down-lead from the equipment, and connect it to the
earth resistance tester.
2.
Mount two auxiliary piles 20 m and 40 m away from the testing point (remote
voltage/remote current). To ensure good contact between the piles and the earth,
sprinkle water around them.
3.
Connect the two auxiliary piles and terminals of the earth resistance tester with a
conducting wire. Shake the handle of the tester to measure the grounding
resistance. For the battery power supply, you can read the grounding resistance
directly by pressing the button.
[Normal Result]
Grounding resistance 5
Measure the grounding resistance according to the design requirements, if any.
1.
Check for the reliable connection of the grounding down-lead to the ground grid.
2.
Check if the ground grid system complies with the design, and if any
resistance-reducing agent is applied on regular basis.

2.5.4.4 Antenna Feeder System Check
[Tools]
None
[Test Procedure]
1.
Observe the LEDs on the AEM panel and check for SWR1 and SWR2 alarms.
2.
Check if the RF cables of the antenna feeder system are aged.

173
[Normal Result]
1.
The LEDs on the AEM panel show no SWR alarms.
2.
The RF cables of the antenna feeder system are not aged.
1.
According to the VSWR measuring method, check the VSWR of the jumpers,
main feeders and antennas. Check segment by segment from the output port of
the combiner to locate the defective parts. Replace the defective parts until the
fault is removed.
2.
If the RF cables are aged, replace them.
[Exit from Test]

None
2.5.4.5 Antennas and Towers Firmness Check
[Tools]
Spanner
[Test Procedure]
1.
Check for the proper setting of fixing clips of antennas and antenna supports.
2.
Check for the proper setting of fixing clips of the tower top amplifiers.
[Normal Result]
The fixing clips of antennas and tower top amplifiers are reliable and do not shake or
slide.
Tighten the fastening screws with a spanner.
[Exit from Test]
None.
2.5.4.6 Directional Antennas Tilt Check
[Tools]
Angle gauge
174
Chapter 2
Routine Maintenance
[Test Procedure]
Check the tilt of a directional antenna by using the rotary angle gauge with a bubble
tube as shown in Figure 2.5-2. If using other instrument, refer to the corresponding
instruments instructions.
DIAL
0
5
21
21
2
20
10
10
30
40
8
3210 12345
54
67
76
8
50
20
50
50
60
60
70
70
80
80
90
90
80
80
70
70
60
60
50
2 10 1234
4 3
56
78
6 5
30
40
51
Figure 2.5-2
1.
Angle Gauge
Press the angle gauge against the object to be measured, as shown in Figure
2.5-3.
2 3 4 5 6 7 8
0 1
2 1
90
80
70
60
50
80
1 1
2
15
40
30
10
50
20
60
70
10
20
40
2 15 12
30
50
60
70
7
6
DIA
80
90
80
70
60
50
1 2 3 4 5 6 7 8
1 0
32
2.
Figure 2.5-3
Measuring the Object With an Angle Gauge (I)
Rotate the dial until the bubble in the air bleeder is located in the middle of two
175
indication rings.
3.
Read the scale on the dial.
[Normal Result]
The tilt conforms to the network planning requirements.
1.
Rotate the dial to set the angle.
2.
Press the object to be measured against the dial chassis firmly. Move the object
and chassis together until the bubble in the air bleeder moves to the middle of
the two indication rings, as shown in Figure 2.5-4.
2 3 4 5 6 7 8
0 1
2 1
90
80
70
60
50
80
11
21
52
40
30
10
50
20
60
70
10
20
40
2 15 12
30
50
60
70
8
7
80
DIA
90
80
70
60
50
1 2 3 4 5 6 7 8
10
32
Figure 2.5-4
Object measurement with the Angle Gauge (II)
[Exit from Test]

None
2.5.4.7 Waterproof Status of Antenna Feeder Connectors and Lightning Protection
Grounding Clips Check
[Tools]
Waterproof adhesive, sealant, insulation tape
176
Chapter 2
Routine Maintenance
[Test Procedure]
Check for the water leakage and cracks on the antenna feeder connectors and the
lightening protection grounding kit.
[Normal Result]
No leakages or cracks found.
Follow the steps below to make waterproof treatment:
1.
Switch off the power of all TRMs/ETRMs of the corresponding carrier shelf on
the PDM panel.
2.
Remove the existing waterproof material.
3.
Wrap the waterproof adhesive at the connector, apply the seal adhesive, and then
wrap the insulation tape.
4.
Wrap the adhesive tape layer by layer from the bottom to avoid rainwater
leakage.
5.
Power-on the TRMs of the corresponding carrier shelf on the PDM panel.
[Exit from Test]

None
2.5.4.8 Iron Towers Check (Optional)
[Tools]
None
[Test Procedure]
Check the tower lamps.
Check the tower structure and the base by measuring the verticality and height of the
iron tower.
Check the stronghold of structure bolts.
Check the corrosion-proof and rust-proof conditions.
[Normal Result]
177
The structure distortion, base sinking and verticality of the iron tower all satisfy the
design requirements. The bolts are fixed tightly and there is no corrosion or rust on
them.
Handle the abnormalities as per procedure.
[Precautions]
None
2.5.4.9 Mast Check (Optional)
[Tools]
None
[Test Procedure]
Check the following: installation of the mast fasteners, stresses of the mast, cables on
the cabling wire tower and anchors, corrosion-proof and rust-proof conditions, mast
verticality.
[Normal Result]
The mast is firmly fixed and there is no corrosion or rust. The mast is vertical.
Resolve the exceptions as per procedure.
[Precautions]
None
2.5.4.10 Transmission Equipment Running Status Check
[Tools]
None
[Test Procedure]
Observe whether LEDs on the transmission equipment indicate any alarm.
[Normal Result]
No alarm is present.
178
Chapter 2
Routine Maintenance
Refer to Users Manual of the transmission equipment.
[Exit from Test]
None
2.5.4.11 Storage Batteries Running Status Check
[Tools]
None
[Test Procedure]
Check for battery leakage and reliable contact of the connection lines.
[Normal Result]
There is no battery leakage and the connection is normal.
Refer to the battery instructions.
[Exit from Test]
None
179

GSM-BSS - II - 09 - 200909 ZXG10 BSS (V3) System Maintenance Criterion 185 PDF

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

GSM-BSS - II - 09 - 200909 ZXG10 BSS (V3) System Maintenance Criterion 185 PDF

Transféré par

Droits d'auteur :

Formats disponibles

ZTE GSM-BSS Products

After-Sales Competency Certification

Grasp normal running features of ZXG10 BSS (V3) equipment;

Understand the common fault information feedback methods;

Understand the emergency fault troubleshooting methods

1.4.3 Get Data Backup ztd File from ISMG ..................................................................................53

2.2.2 BSC Running Status Check.................................................................................................. 84

1 BSS Maintenance Specification

1.1 Guide to ZXG10-BSS System Maintenance

1.1.2 Emergent Fault Notification and Update Stipulations

ZXG10 BSS (V3) System Maintenance Criterion

1.1.2.2 Emergent Fault Update

BSS Maintenance Specification

1.1.3 Flow of Emergency Maintenance

Flow of Emergency Maintenance

1. Collecting fault information

ZXG10 BSS (V3) System Maintenance Criterion

1 Confirm whether power supply works properly.

Table 1.1-1 Fault Feedback Report

Version number and patch

number (filled in by who

gives the feedback)

BSS Maintenance Specification

Fault time, symptom, and

(filled in by who gives the

Do feedback based on "Fault information collection and feedback"

Do feedback based on "Fault information collection and feedback"

customer service depart.)

Field prevention methods

(Filled in by the R&D staff)

ZXG10 BSS (V3) System Maintenance Criterion

"Emergency Troubleshooting Scheme".

7X24 Technical Service

ZTE Service Hotline

BSS Maintenance Specification

First back up system data prior to restoring service.

To change hardware configuration, such as cable connection or board slots, record

the current conditions.

It is necessary to record any step and symptoms encountered on field.

ZXG10 BSS (V3) System Maintenance Criterion

1.2 Emergent Handling Solution for ZXG10-BSS Major Fault

Check the running status of the BSC through OMCR.

BSS Maintenance Specification

None red indicator on the boards is on.

ZXG10 BSS (V3) System Maintenance Criterion

1.2.2 Emergent Handling Flow for System Abnormality

If the server space

Kill virus and

If the database runs

Omcps check if the

Exit all OMCR

Exit all OMCR

Handling Flow for OMCR Abnormality and Interruption

BSS Maintenance Specification

Check whether the configuration for the router is correct.

Check the hard disk space of the client.

Check the hard disk space of the server.

Check if the OMCR processes are normal.

Check whether the database is running normally.

Check whether the database is started normally.

ZXG10 BSS (V3) System Maintenance Criterion

Check whether the database can be accessed normally.