ZXG10 iBSC (V6.20.71) Base Station Controller Emergency Maintenance PDF

ZXG10 iBSC
Base Station Controller
Emergency Maintenance
Version: V6.20.71
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2011 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited.
Additionally, the contents of this document are protected by
contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No.
Revision Date
Revision Reason
R1.1
2011-09-30
Updated to V6.20.711C
R1.0
2011-07-14
First Edition
Serial Number: SJ-20110531095035-006

Publishing Date: 2011-09-30(R1.1)
Contents
About This Manual ......................................................................................... I
Chapter 1 Overview of Emergency Maintenance .................................... 1-1
1.1 Scope of Emergency Maintenance ...................................................................... 1-1
1.2 Guide Concept of Emergency Maintenance ......................................................... 1-3
1.3 Flow of Emergency Maintenance......................................................................... 1-3
1.3.1 Determine the fault scope ......................................................................... 1-4
1.3.2 Locate fault reason and record exceptions ................................................. 1-5
1.3.3 Fault Analysis .......................................................................................... 1-5
1.3.4 Critical solution......................................................................................... 1-5
1.3.5 Restore service ........................................................................................ 1-6
1.3.6 Observe restored services ........................................................................ 1-6
1.3.7 Feedback information about emergency maintenance ................................ 1-6
1.3.8 Communication with customer .................................................................. 1-6
1.4 Precautions of Emergency Maintenance .............................................................. 1-6
1.5 Contact Information of Technical Support from ZTE .............................................. 1-6
Chapter 2 Preparation of Emergency Maintenance ................................ 2-1

2.1 Daily Preparation of Emergency Maintenance ...................................................... 2-1
2.1.1 Data Backup and System Inspection ......................................................... 2-1
2.1.2 Establish Remote Maintenance Station...................................................... 2-3
2.1.3 Preparation of important spare parts.......................................................... 2-3
2.2 Holiday Preparation of Emergency Maintenance .................................................. 2-3
2.2.1 Load Monitoring ....................................................................................... 2-3
2.2.2 Load reduction measures.......................................................................... 2-4
Chapter 3 Guide of Emergency Maintenance .......................................... 3-1

3.1 Maintenance Guide about Major Alarm ................................................................ 3-1
3.1.1 Board Alarm............................................................................................. 3-1
3.1.2 Clock alarm.............................................................................................. 3-3
3.1.3 Alarms related with interface A .................................................................. 3-4
3.1.4 Alarms on flow control .............................................................................. 3-5
3.1.5 Transmission alarms ................................................................................ 3-6
3.2 Maintenance Guide about NM Faults ................................................................... 3-7
3.2.1 Can't login NM system .............................................................................. 3-7
3.2.2 Disconnection between OMM and NM servers ........................................... 3-8
3.2.3 Disconnection between equipment and OMM server .................................. 3-8

3.3 Maintenance Guide about CS Service Faults ....................................................... 3-9
3.3.1 Mass users can't call normally................................................................... 3-9
3.3.2 All sites under BSC can't call normally ....................................................... 3-9
3.3.3 All sites under certain module in BSC can't call normally........................... 3-10
3.3.4 All sites under certain 100M/GB resource frame can't call normally.............3-11
3.3.5 All sites under certain BIPB/BIPB2/AIPB/AIPB2 can't call normally .............3-11
3.3.6 All sites under certain LAPD/LAPD2 can't call normally..............................3-11
3.3.7 Mass users belonging to other type can't call normally .............................. 3-12
3.4 Maintenance Guide about PS Service Faults...................................................... 3-12
3.4.1 Mass user can't use GPRS service.......................................................... 3-12
3.4.2 All users under whole BSC can't use GPRS service ................................. 3-13
3.4.3 Some cells can't use GPRS service......................................................... 3-13
Chapter 4 Fault Feedback Information ..................................................... 4-1

4.1 Prerequisite of fault feedback .............................................................................. 4-1
4.2 Feedback Data That Shall be Recorded............................................................... 4-3
4.3 The method to get system record ........................................................................ 4-6
4.3.1 Get device printing file .............................................................................. 4-6
4.3.2 Get ZDB file ............................................................................................. 4-6
4.3.3 Get data backup ztd file from OMM ........................................................... 4-8
4.3.4 Get software setting ................................................................................. 4-8
4.3.5 Get alarm file ........................................................................................... 4-9
4.3.6 fanGet notification file ............................................................................. 4-13
4.3.7 Get 1 hour's performance data before and after fault ................................ 4-17
4.3.8 Get tracing signal at interface A............................................................... 4-20
4.3.9 Query dynamic data at interface A........................................................... 4-23
4.3.10 Get tracing signal at interface Abis......................................................... 4-24
4.3.11 Query dynamic data at site .................................................................... 4-26
4.3.12 Trace PS service signal ........................................................................ 4-26
4.3.13 Query BVC and NSVC state.................................................................. 4-28
4.3.14 Get operation log of preset machine ...................................................... 4-28
4.3.15 Check whether overstocked data exists ................................................. 4-28
4.3.16 Query disk space.................................................................................. 4-29
4.3.17 Get NM printing file............................................................................... 4-30
4.3.18 Get NM profile...................................................................................... 4-30
4.3.19 Get operation log at client ..................................................................... 4-30
4.3.20 View system time zone ......................................................................... 4-32
II
4.3.21 View NM version .................................................................................. 4-32

4.3.22 Maintenance Record List ...................................................................... 4-32
Figures............................................................................................................. I
Tables ............................................................................................................ III
Glossary .........................................................................................................V
III
IV
About This Manual

Purpose
This manual introduce the process of ZXG10 iBSC emergency maintenance, including the
preparation, typical emergency maintenance case and fault feedback information.
Intended Audience
l
l
System engineer
Maintenance engineer
What Is in This Manual

This manual contains the following chapters:
Chapter
Description
Chapter 1 Overview of
Describes applicable scope, guideline, and process of ZXG10 iBSC
emergency maintenance.
Chapter 2 Preparation of
Describes preparation of ZXG10 iBSC emergency maintenance.
Chapter 3 Guide of
Describes guideline of ZXG10 iBSC emergency maintenance on
different faults.
Chapter 4 Fault Feedback
Describes the methods to send fault feedback and get system log of
Information
ZXG10 iBSC emergency maintenance.
II
Chapter 1
Overview of Emergency
Maintenance
Table of Contents
Scope of Emergency Maintenance .............................................................................1-1
Guide Concept of Emergency Maintenance................................................................1-3
Flow of Emergency Maintenance................................................................................1-3
Precautions of Emergency Maintenance ....................................................................1-6
Contact Information of Technical Support from ZTE....................................................1-6
1.1 Scope of Emergency Maintenance

During system running, you can confirm whether emergency maintenance shall be started
through user complaint, alarm inspection, and performance report analysis.
1. User complaint
Table 1-1 shows user complaints about emergency maintenance.
Table 1-1 User complaint
Complaint content
Description
After receiving user complaints, you shall fur-
Lots of speech user can't access;
ther check alarm information and KPI measure-
Lots of MS can't be acted as called/caller;
ment result, to determine whether emergent
Lots of users can't use GPRS service
fault occurs.
2. Alarm inspection
Table 1-2 shows the alarm report that shall be viewed on emergency maintenance.
Table 1-2 Alarm report on emergency maintenance
Alarm Type
Alarm Description
Alarms on spare boards, such as OMP/OMP2
and CMP/CMP2.
Active board alarm in active/standby mode
Board alarm
Board alarm out of non-active/standby mode
1-1
SJ-20110531095035-006|2011-09-30(R1.1)
ZTE Proprietary and Confidential
ZXG10 iBSC Emergency Maintenance
Alarm Type
Alarm Description
Abnormal access clock
Phase-locked loop out of lock
Clock alarm
Level 1 alarm on lost clock reference source

Alarm on unreachable MTP3 office
Alarms related with interface A
SCCPSubsystem unavailable
MSCOverload
Congestion at signalling point
Alarms on flow control
CPUToo high load

Loss of trunk frame
Loss of trunk signal
Relevant transmission alarms
SDH/SONET: loss of signal
3. Analyzing a performance report

Normally, KPI indicator is not a direct condition to start emergency maintenance.
Table 1-3 shows the important KPI indicators that shall be viewed and analyzed on
l
While KPI is changed exceptionally, you shall confirm whether emergency

maintenance process shall be started, in combination with user complaint, test,
and alarm analysis.
While starting emergency maintenance process under critical alarm and user
complaint, KPI indicator shall be used as a subsidiary analysis tool and
troubleshooting method.
Table 1-3 KPI Indicator

Indicator Type
Indicator Name
SDCCH Congestion rate
TCH Congestion rate
TCH traffic
Congestion
TCH availability
TCH Assignment success rate
Channel occupation
Call success rate
Changeover related
Handover success rate
Call drop
TCH call drop rate
1-2
SJ-20110531095035-006|2011-09-30(R1.1)
Chapter 1 Overview of Emergency Maintenance
1.2 Guide Concept of Emergency Maintenance

Emergency maintenance is suitable for the faults that shall be handled and restored
immediately and have great influence on service. For more information on daily
maintenance, see ZXG10 iBSC (V6.20.71) Base Station Controller Routine Maintenance.
For more information on normal troubleshooting, see ZXG10 iBSC (V6.20.71) Base
Station Controller Troubleshooting.
Prior to maintenance, you shall fully consider and follow below principles about emergency
maintenance.
l
l
You shall firstly determine fault scope prior to maintenance, to do troubleshooting from
inner to outer or from entire to local.
Daily maintenance shall refer to ZXG10 iBSCand relevant equipment data, along
with historical fault analysis and experience, and then you shall prepare for
emergent schedule; the operator shall periodically organize relevant managers and
maintenance personnel for training and demonstration.
When system or equipment encounters emergent faults, maintenance personnel shall
keep calm; then check BSC hardware and transmission to determine whether the fault
is caused by BSC. If yes, you shall do troubleshooting according to emergent schedule
or relevant process in referential manual.
Relevant maintenance personnel shall learn more about the system in daily
maintenance assignments, especially to be familiar with common exceptional
information about NM alarm and indicator conditions on BSC panel, and to master
common tools about data backup/restore.
Before, in the process of, or after emergency maintenance, maintenance personnel
shall collect the alarm information about this fault, and send troubleshooting report,
equipment alarm file, and log file to ZTE office for analysis and locating, so ZTE can
provide better after-sale service for the operator.
1.3 Flow of Emergency Maintenance

Emergency maintenance contains the following several steps:
1.
2.
3.
4.
5.
6.
7.
8.
Determine the fault scope;

Locate fault reason and record exceptions;
Fault analysis;
Critical solution;
Restore service;
Observe restored services;
Feedback information about emergency maintenance;
Communication with customer.
Figure 1-1 shows the flow of emergency maintenance.
1-3
SJ-20110531095035-006|2011-09-30(R1.1)
Figure 1-1 Flow of Emergency Maintenance
1.3.1 Determine the fault scope

Determine fault scope based on three following aspects.
1-4
SJ-20110531095035-006|2011-09-30(R1.1)
Chapter 1 Overview of Emergency Maintenance
1. Service faults often begin with user claims, so you shall register user number. Analyze
the site for user based on different tools at BSC and CN sides, to determine the
influence scope of the fault.
l Use signaling trace and probe to find out CN, BSC, or BTS that is claimed by user.
The aim is to reduce and determine fault related equipment.
l If you can't determine the location of claiming user at BSC side, you shall search
for help from CN side.
2. Determine fault scope through analysis of KPI indicator.
l Query relevant indicators in KPI to judge the affected site scope about the fault.
l Determine whether it is global fault based on affected site.
l Determine whether it is associated with module and special board based on based
on affected site.
3. Test arrangement.
If possible, arrange test at specific area, and provide more accurate information on
1.3.2 Locate fault reason and record exceptions

Pick up relevant data about alarm, performance, and printing, and analyze obvious
phenomenon about network fault. Observe the information of equipment operation, board
indicator. Check the fault caused by BSS equipment or other reasons, and determine its
involved scope.
1.3.3 Fault Analysis

If locating fault is caused by BSS equipment, you shall analyze field alarms, performance,
signal, and printing log, and do troubleshooting after finding proper fault point.
1.3.4 Critical solution

Search for emergency help from ZTE customer support center, which provides 7*24 hours
hotline service and remote technical support service.
1. ZTE hotline service
Customer support center hotline: (fixed line) 8008301118; (cellphone) 4008301118.
2. Remote support
Based on the information provided by service hotline, technical expert remotely logins
at problematic site and assists customer to solve problems through phone; if the
problem is too complicated, ZTE will direclty appoint technical support engineer to
the field for troubleshooting.
3. Field Technical Support
Technical expert shall make emergency measures to restore normal communication
as soon as possbile.
1-5
SJ-20110531095035-006|2011-09-30(R1.1)
1.3.5 Restore service

Find out fault reason and quickly restore normal service through remote or field ZTE
technical support. If you can't timely find the reason, you shall restore system service
as soon as possible. If necessary, you shall try to solve the problem through board
switchover, resetting, and restarting.
1.3.6 Observe restored services

After the service is restored, you shall confirm whether normal operation state has been
restored, and arrange relevant persons to do test. If necessary, you shall arrange some
persons on duty within peak traffic period, to closely monitor network operation. As such,
if the problem occurs again, you shall solve it as soon as possible.
1.3.7 Feedback information about emergency maintenance

After the service is restored, you shall collect BSS network statistics report, operation log,
and signaling tracing data, and send troubleshooting results to local ZTE customer service
center.
1.3.8 Communication with customer

For level 1 faults, based on feedback data on site, ZTE mobile customer service
department will submit fault analysis report to local office, and local office will communicate
with customer about involved faults.
1.4 Precautions of Emergency Maintenance

Precautions of emergency maintenance are as follows.
l
You shall quickly find the fault location during emergency maintenance. Some
restoration (such as board resetting) may have a great influence on system operation,
so it shall be performed by a experienced operator or under the guide from an
operator with certain maintenance experience.
If the fault has a great influence on network operation, no matter whether maintenance
personnel can solve it or not, they shall immediately contact ZTE customer service
center or local ZTE office, so we can timely and quickly find the fault location and
solve it.
1.5 Contact Information of Technical Support from ZTE

Contact information of technical support from ZTE is as follows.
1. Telephone at global ZTE customer service center
l Fixed phone: 8008301118.
l Mobile phone: 4008301118.
2. Local ZTE office
1-6
SJ-20110531095035-006|2011-09-30(R1.1)
Chapter 2
Preparation of Emergency
Maintenance
Table of Contents
Daily Preparation of Emergency Maintenance ............................................................2-1
Holiday Preparation of Emergency Maintenance ........................................................2-3
2.1 Daily Preparation of Emergency Maintenance

Daily preparation of emergency maintenance contain the following three contents:
l
l
l
Data Backup and System Inspection

Establish Remote Maintenance Station
Preparation of important spare parts
2.1.1 Data Backup and System Inspection

Maintenance personnel does data backup in daily maintenance. They can restore
configuration data during system faults, to enable the system restore normal service.
Maintenance personnel can find significant faults and potential risks through daily system
inspection.
Data Backup
Maintenance personnel shall backup daily data.
Configuration data can be manually or automatically backed-up.
l
Automatic Backup
By default, the system backs-up OMM configuration data everyday.
Path
to
save
configuration
data:
/home/xxxxxxx/ums-svr/backup/sysmanager/cm.
OMM
server
Manual Backup
1. Right-click the NE in physical view of topology management, select NE
Management > Configuration Management in floating menu, to call
configuration management interface.
2. Select Management > Data Management > Data Backup.
3. Data Backup interface pops up, as shown in Figure 2-1.
2-1
SJ-20110531095035-006|2011-09-30(R1.1)
Figure 2-1 Data Backup Interface
4. Select NE, configure save path and backup NE, and click Ok button.
5. Data Backup Result interface pops up, as shown in Figure 2-2. Click Close
button.
Figure 2-2 Data Backup Result Interface
2-2
SJ-20110531095035-006|2011-09-30(R1.1)
Chapter 2 Preparation of Emergency Maintenance
The
directory
for
data
backup
server/home/xxxxxxx/ums-svr/backup/sysmanager.
is
OMM
Checking the system

System inspection contains:
l
l
l
l
l
l
l
l
l
l
l
View board indicators

Check communications link between the NMS and NE.
Query current BSC alarm
Query the historical alarms within 24 hours at BSC
Query the historical notifications within 24 hours at BSC
Query important performance indicators at BSC
Check the state at interface A
Check the state at interface Gb
View the active/standby status of the board.
Query BSC operation log
Check the alarm box
For system inspection, refer to "Check Operation State at BSC" in ZXG10 iBSC (V6.20.71)
Base Station Controller Routine Maintenance, focusing on checking operation state at BSC
and analyze performance indicator & historical alarms.
If major alarm exists while checking historical alarms (within 1 week) and current alarms,
you shall handle it immediately. If the alarms still continue, you shall contact local ZTE
office or customer service center.
2.1.2 Establish Remote Maintenance Station

To guarantee quickly locate and solve the faults under the support of ZTE technicians,
PCAnyWhere or VPN remote access shall be always kept normal on different fields. You
can contact local ZTE office while commissioning remote access.
2.1.3 Preparation of important spare parts

You shall prepare for sufficient spare parts for important boards on BSC, such as
OMP/OMP2, CMP/CMP2, CLKG/ICM, CHUB, UIMC, UIMU/GUIM/GUIM2, PSN, and
GLI/GLI4.
2.2 Holiday Preparation of Emergency Maintenance

Preparation in holiday mainly aims the case of large traffic, not just the specific holiday
period.
2.2.1 Load Monitoring

User shall monitor the load as follows.
2-3
SJ-20110531095035-006|2011-09-30(R1.1)
1. View daily CPU load on BSC at busy time in holiday. CMP/CMP2 load at BSC can't
exceed 70%.
2. Focus on CPU load on each board within whole monitoring period. Referential
threshold is 70%.
3. Do your best to reduce the action of signaling trace during large traffic, to reduce the
influence on MP load.
4. During large traffic, to reduce CPU load, you shall stop or close probe software.
5. Monitor load value at no.7 signaling link at interface A on BSC, which shall be lower
than 0.4. If more than this value, you shall add more no.7 signaling links.
6. Monitor load value of service timeslot at interface A on BSC, which shall be lower than
0.6 Erlang. If more than this value, you shall add more circuits at interface A.
7. Monitor the signaling load at interface IPA on BSC, view "the number of received SCTP
packet", "the byte of received SCTP packet", "the number of transmitted SCTP packet",
and "the byte of transmitted SCTP packet" in performance counters of SCTP coupling
measurement. Its sum of SCTP coupling flow is lower than general signaling flow of
CMP/CMP2. If it is more than this value, you shall add more links at interface IPA.
Sum of SCTP coupling flow = (the byte of received SCTP packet + the byte of
transmitted SCTP packet + (the number of received SCTP packet + the number of
transmitted SCTP packet) * the bytes of protocol header in each packet)*8/ granularity
of statistical report time.
The protocol header in each packet has 48 bytes.
Total signaling flow of CMP/CMP2 = 4Mbps* the number of CMP/CMP2.
8. Monitor the flow at interface IP A on BSC. The sum of received flow and the sum of
transmitted flow at different ports shall be lower than 80% of general flow at IP port.
The max flow at each 100M port is 80Mbps, and that at each GB port is 700Mbps. If
it is higher than this value, you shall add more links at interface IPA.
9. Monitor the traffic at interface IPA on BSC. Check the available average number of
UDP ports and total time occupied by UDPPort in performance management. Total
time occupied by UDPPort (hours) / available average number at UDP port. The ratio
shall be lower than 0.8. If more than this value, you shall add links at interface IPA.
10. It is recommended to monitor load condition at CN side. If the load at CN side is
exceptional, you shall inform maintenance personnel as soon as possible.
2.2.2 Load reduction measures

User can use the following measures to reduce load.
1. Measures at BSC side.
l Check whether FUC flow control at BSC side is opened.
l Check whether SIM card for field mobile phones are classified according to
specified requirements. If it is classified, you can check whether system message
about flow control at BSC side is opened.
l For individual site with large traffic, it is recommended to open handover for
preprocessing.
2-4
SJ-20110531095035-006|2011-09-30(R1.1)
Chapter 2 Preparation of Emergency Maintenance
l
l
l
Pause or delete unnecessary observation tasks.

Pause or delete unnecessary measurement tasks.
Get no.7 signaling link at interface A and working load at service timeslot. The
one near or over upper limit shall be expanded timely.
l Get working load about SCTP coupling at interface A. The one near or over upper
limit shall be expanded timely.
l Temporarily modify two or more paging as one paging mode for CN.
2. Measures at CN side.
l Don't send lots of paging messages at the same time.
l Too heavy load at switching device. You shall check which BSC NE has the
heaviest traffic. You can block some circuits at interface A for this BSC, to reduce
processing load at CN side.
l Timely start flow control function at CN side, preventing from too high load leading
to equipment degradation.
2-5
SJ-20110531095035-006|2011-09-30(R1.1)
This page intentionally left blank.
2-6
SJ-20110531095035-006|2011-09-30(R1.1)
Chapter 3
Guide of Emergency
Maintenance
Table of Contents
Maintenance Guide about Major Alarm.......................................................................3-1
Maintenance Guide about NM Faults..........................................................................3-7
Maintenance Guide about CS Service Faults .............................................................3-9
Maintenance Guide about PS Service Faults............................................................3-12
3.1 Maintenance Guide about Major Alarm

Maintenance guide about major alarm contains the following contents:
l
l
l
l
l
Board alarm;
Clock alarm;
Alarms related with interface A;
Alarms on flow control;
Relevant transmission alarms.
3.1.1 Board Alarm

3.1.1.1 Active board alarm in active/standby mode
1. Symptoms
The following alarms are found in real-time alarm for active board.
l 198005379 Board offline or CPU in long-term resetting state
l 198005390 Wrong (CPU) sub-card position configured by database
l 198066004 Communication blocked between module and OMP
2. Troubleshooting steps:
a. View the working state of standby board.
active/standby switchover happens.
If the standby board is normal,
b. View board state after switchover, to check whether the board is normal. If the
alarm continues on the active board after switchover, go to step 3.
c.
If the fault also exits on standby board, reset active/standby board at the same
time.
d. Replace relevant boards.

3-1
SJ-20110531095035-006|2011-09-30(R1.1)
e. If the alarms still continue, you shall contact local ZTE office or customer service
center.
3. Post inspection
The alarm is removed after checking on NM system.
3.1.1.2 Alarms related with OMP/OMP2 standby board

1. Symptoms
The following alarms are found in real-time alarm for OMP/OMP2 backup board.
l
l
198005379 Board offline or CPU in long-term resetting state

198005122 Communication link disconnected at control plane between
active/standby boards
a. View OMP/OMP2 board indicators to check whether red alarm indicator, ALM, is
on and the fault exists on OMP/OMP2.
b. Check whether the board is inserted in proper slot. If the board is not at proper
position, or wrongly inserted, you shall plug/unplug the board again.
c.
Check whether micro switch (ENUM) of the board is opened. If ENUM switch is
opened, you shall close it.
d. If above steps can't solve the fault, reset the board. First try to reset remotely from
NM. If the problem continues, you can reset it by manually plugging/unplugging
the board.
e. Replace OMP/OMP2 board.
f.
If the alarms still continue, you shall contact local ZTE office or customer service
center.
3. Post inspection
l The alarm is removed after checking on NM system.
l If possible, switch the original standby OMP/OMP2 to active one while the service
traffic is minimum, and check whether the board is normal.
3.1.1.3 Alarms related with CMP/CMP2 standby board

1. Symptoms
The following alarms are found in real-time alarm for CMP/CMP2 backup board.
l
l
l
198005379 Board offline or CPU in long-term resetting state

198005390 Wrong (CPU) sub-card position configured by database
198005122 Communication link disconnected at control plane between
active/standby boards
a. View rack board indicators at BSC side to check whether red alarm indicator, ALM,
is on and the fault exists on NM.
3-2
SJ-20110531095035-006|2011-09-30(R1.1)
Chapter 3 Guide of Emergency Maintenance
position, or wrongly inserted, you shall plug/unplug the board again.
c.
d. If above steps can't solve the fault, reset the board. First try to reset remotely from
NM. If the problem continues, you can reset it by manually plugging/unplugging
the board.
e. Replace CMP/CMP2 board.
f.
center.
3. Post inspection
3.1.1.4 Board alarm out of active/standby mode

1. Symptoms
The following alarms are found in real-time alarm for OMP/OMP2 active board.
l
198066003 Abnormal communication at control plane between board and its

module
l 198005379 Board offline or CPU in long-term resetting state
l 198005390 Wrong (CPU) sub-card position configured by database
a. View rack board indicators at BSC side to check whether red alarm indicator is on
and the fault exists on the board.
position, or wrongly inserted, you shall plug it properly again.
c.
d. Reset relevant boards. First try to reset remotely from NM. If the problem
continues, you can reset it by manually.
e. Replace this board.
f.
center.
3. Post inspection
3.1.2 Clock alarm

1. Symptoms
The following alarms are found in real-time alarm.
3-3
SJ-20110531095035-006|2011-09-30(R1.1)
l 198005381 Abnormal access clock

l 198005646 Phase-locked loop out of lock
l 198026129 Level 1 alarm on lost clock reference source
a. Check whether CLKG/ICM board is running normally. Board Alarm shows the
steps of inspection and troubleshooting.
b. Check whether SDTB/SDTB2, DTB, or SPB/SPB2 board to get clock at interface
A is normal. Board Alarm shows the steps of inspection and troubleshooting.
c.
Check whether cable connection from A-interface board to CLKG/ICM is normal.

If the cable is loose or abnormal, you shall re-connect it or replace the clock cable
from A-interface board to CLKG/ICM.
d. Check whether STM-1 and E1 are normal on the board to get clock at interface
A. Check whether trunk interruption, high BER, or slide code alarm exist, such
as "SDH/SONET: signal missing", "trunk signal missing". If yes, you shall contact
transmission engineer to solve it.
e. If getting GPS clock, you shall check the connection condition from GPS antenna
feeder to ICM board, and login the board through serial port mode, to check the
condition of satellite signal received.
f.
If ICM board directly connects DDF to get A-interface clock at core side, you
shall check ICM board followed by SDTB/SDTB2, DTB, or SPB/SPB2 board and
in-between wiring.
g. Switchover CLKG/ICM board.

h. If the alarms still continue, you shall contact local ZTE office or customer service
center.
3. Post inspection
3.1.3 Alarms related with interface A

1. Symptoms
l 198066010 Alarm on unreachable MTP3 office
l 198066005 SCCP Subsystem Unavailable
a. Check E1/IP alarm at interface A to view whether all PCM/networks are interrupted
at this interface.
b. Check whether the clock state at BSC side is exceptional.
troubleshooting in Clock Alarm.
c.
If yes, refer to
Check whether global data at BSC and CN sides is changed. If yes, you shall
restore the data prior to changing.
3-4
SJ-20110531095035-006|2011-09-30(R1.1)
d. Gradually switchover UIMU, UIMC, GUIM/GUIM2, CLKG/ICM boards. You shall

check whether the service is restored while you switchover each board. If the fault
continues, you can continue switchover the next board.
center.
3. Post inspection
l Through dynamic data observation at interface A, test whether all signals, trunks,
signaling trace analysis and service test at interface A are normal.
3.1.4 Alarms on flow control

3.1.4.1 MSC overload
1. Symptoms
l 198087344 Overload of MSC FUC control mode
l 198087347 Alarm on system message method during MSC overload
a. Inform MSC engineer to check whether MSC is overloaded and sends
corresponding overload message to BSC side.
b. Check whether FUC bitmap at BSC side is configured properly. If not, FUC flow
control will not work.
c.
Check whether SIM card for field mobile phones are classified according to
specified requirements. If no classfication, FUC flow control hasn't any influence
on user service.
d. Contact local ZTE office or customer service support center.

3. Post inspection
l Transmission is restored through testing.
3.1.4.2 Congestion at signalling point

1. Symptoms
l 198087349 Alarm on system message method during SP congestion.
l 198087346 Alarm on FUC control method during SP congestion.
a. Notify MSC engineers of checking whether no.7 signaling link is overloaded.
3-5
SJ-20110531095035-006|2011-09-30(R1.1)
b. Query whether TCH traffic and the number of TCH request in KPI indicators are
greatly increased. If it is greatly increased, you can confirm SP congestion is
caused by higher traffic.
c.
Check whether all no.7 signals are normal at this link, or any interruption or flash
symptom exist.
d. Check whether FUC bitmap at BSC side is configured properly. If not, FUC flow
e. Check whether SIM card for field mobile phones are classified according to
on user service.
f.
Contact local ZTE office or customer service support center.
3. Post inspection
3.1.4.3 Too high CPU load

1. Symptoms
l 198087348 Alarm on system message control mode due to higher CPU load.
l 198087345 Alarm on FUC control mode due to higher CPU load.
a. Query whether TCH traffic and the number of TCH request in KPI indicators are
greatly increased. If it is greatly increased, you can confirm whether CPU overload
is caused by higher traffic.
b. Block corresponding cells in the region by using NM tools.
c.
Check whether FUC bitmap at BSC side is configured properly. If not, FUC flow
d. Check whether SIM card for field mobile phones are classified according to
on user service.
e. Contact local ZTE office or customer service support center.
3. Post inspection
previously, you shall unblock the cell.
If the cell is blocked
3.1.5 Transmission alarms

1. Symptoms
3-6
SJ-20110531095035-006|2011-09-30(R1.1)
l 198000512 Loss of trunk frame

l 198000513 Loss of trunk signal
l 198001792 SDH/SONET: loss of signal
a. Check E1/IP alarm to view whether all PCM/networks are interrupted at this
interface.
b. Check whether transmission cable is correct, connector is properly contacted, or
cable is normal.
c.
Inform transmission engineer to check transmission equipment and its link.
d. Replace relevant DTB, SDTB/SDTB2, and GIPI/GIPI4 boards.

center.
3. Post inspection
l Transmission is restored.
3.2 Maintenance Guide about NM Faults

Maintenance guide about NM faults contains the following contents:
l
l
l
Can't login NM system;

OMM Disconnection between OMM and NM servers;
Disconnection between OMP/OMP2 and OMM server.
3.2.1 Can't login NM system

1. Symptoms
Login from the client to the NM server fails.
There are two cases: all clients can't login or individual client can't login. So the
troubleshooting can be categorized into two types.
l
All clients can't login.

a. Check running condition of server programs, and view whether all NM
processes are normal.
b. check if server database is running properly.
c.
Check operation condition of server operating system.
d. Restart the server.

e. If the alarms still continue, you shall contact local ZTE office or customer
service center.
l
Individual client can't login.

3-7
SJ-20110531095035-006|2011-09-30(R1.1)
a. check if client database is running properly.

b. Check if the client IP communicates normally with the server.
c.
check if required Java packet exists and is normal during client operation.
d. Is client attacked by virus? check if operating system is normally running. If

any virus is detected, kill it.
e. If the alarms still continue, you shall contact local ZTE office or customer
service center.
3. Post inspection
Successfully log in client and you can use it normally.
3.2.2 Disconnection between OMM and NM servers

1. Symptoms
Can't start NE agent.
a. Check whether the physical link between NM server and OMM server is
connected.
b. Check whether the firewall ports of NM server and OMM server are opened.
c.
Check whether OMM FTP server is available, and check whether FTP port
definition of profile is correct.
d. If the alarms still continue, you shall contact local ZTE office or customer service
center.
3. Post inspection
NE agent is successfully enabled, and you can use it normally.
3.2.3 Disconnection between equipment and OMM server

1. Symptoms
In configuration management, it is found the link between equipment and OMM is
disconnected, and configuration data can't be distributed normally.
a. Check whether IP network from OMP/OMP2 to HUB is normal.
l Check the network cable from OMP/OMP2 to HUB.
l Check configuration of OMP/OMP2 IP address in OMM server data.
b. Check whether the MP is running normally. If no, refer to troubleshooting in Board
Alarm.
c.
Restart OMM server.

3-8
SJ-20110531095035-006|2011-09-30(R1.1)
center.
3. Post inspection
Check the NMS and find the communications link between the NMS and NE is
established. The alarm is removed.
3.3 Maintenance Guide about CS Service Faults

Maintenance guide about CS service faults contains the following contents:
l
l
l
l
l
l
l
Mass users can't call normally;

All sites under BSC can't call normally;
All sites under certain module in BSC can't call normally;
All sites under certain 100M/GB resource frame can't call normally;
All sites under certain BIPB/BIPB2/AIPB/AIPB2 can't call normally;
All sites under certain LAPD/LAPD2 can't call normally;
Mass users belonging to other type can't call normally.
3.3.1 Mass users can't call normally

1. Symptoms
Mass users can't call normally
2. Troubleshooting
Based on quantity and domain of claiming users and in combination with KPI analysis
and test, you can determine the influence scope of this fault. According to different
service scope, you can use the following troubleshooting methods.
For more information, refer to All Sites Under BSC Can't Call Normally, All Sites
Under Certain Module In BSC Can't Call Normally, All Sites Under Certain 100M/GB
Resource Frame Can't Call Normally, All Sites Under Certain BIPB/BIPB2/AIPB/AIPB2
Can't Call Normally, All Sites Under Certain LAPD/LAPD2 Can't Call Normally, and
Mass Users Belonging To Other Type Can't Call Normally.
3. Post inspection
l The result is normal during calling test.
l KPI index restores the level prior to the fault.
3.3.2 All sites under BSC can't call normally

1. Symptoms
All sites under BSC can't call normally.
2. Troubleshooting
3-9
SJ-20110531095035-006|2011-09-30(R1.1)
a. Check whether the link at interface A is disconnected and global alarm issues. If
it is disconnected at interface A, refer to troubleshooting in Alarms Related With
Interface A.
b. Check whether clock alarm exists by viewing global alarms. If yes, refer to
troubleshooting in Clock Alarm.
c.
Check whether the active/standby boards for switching shelf, such as GLI/GLI4,
PSN, or UIMC, or control shelf, such as OMP/OMP2 and CMP/CMP2 can't work
normally. If yes, refer to troubleshooting in Board Alarm.
d. Enable signaling trace based on test condition. Check whether ring message is
distributed or ground resource can be allocated normally.
If signal is complete, and no sound exists at one channel or in bidirection, you shall
check whether there is any alarm on AIPB/AIPB2 and BIPB/BIPB2 logical board.
If yes, reset the board.
e. Switchover OMP/OMP2 board.
f.
center.
3. Post inspection
l You can call normally at all sites under BSC.
3.3.3 All sites under certain module in BSC can't call normally
1. Symptoms
All sites under certain module in BSC can't call normally.
2. Troubleshooting
a. View CMP/CMP2 alarm on this module to check whether the board or certain CPU
on it can't normally function. If yes, refer to troubleshooting in Board Alarm.
b. View whether flow control alarm occurs due to CPU overload on this module. If
yes, refer to troubleshooting in Alarms On Flow Control.
c.
Replace the module on CMP/CMP2.
d. Reset or replace this CMP/CMP2 module.

center.
3. Post inspection
l You can call normally at all sites under this module in BSC.
3-10
SJ-20110531095035-006|2011-09-30(R1.1)
3.3.4 All sites under certain 100M/GB resource frame can't call
normally
1. Symptoms
All sites under certain 100M/GB resource frame can't call normally.
2. Troubleshooting
a. Check the UMIU/GUIM/GUIM2 alarm of this shelf to view whether the board can't
work normally. If yes, refer to troubleshooting in Board Alarm.
b. Check whether ethernet cable from UIMU/GUIM/GUIM2 to CHUB is normally
connected.
c.
Check whether clock cable from UIMU/GUIM/GUIM2 to CLKG/ICM is normally

connected.
d. Switchover this UIMU/GUIM/GUIM2 board.

e. Reset this UIMU/GUIM/GUIM2 board.
f.
center.
3. Post inspection
l You can call normally at all sites under this resource shelf.
3.3.5 All sites under certain BIPB/BIPB2/AIPB/AIPB2 can't call

normally
1. Symptoms
All sites under BIPB/BIPB2/AIPB/AIPB2 can't call normally.
2. Troubleshooting
a. Check the BIPB/BIPB2/AIPB/AIPB2 alarm to view whether the board can't work
normally. If yes, refer to troubleshooting in Board Alarm.
b. Reset this BIPB/BIPB2/AIPB/AIPB2 board.
c.
center.
3. Post inspection
l You can call normally at all sites under BIPB/BIPB2/AIPB/AIPB2.
3.3.6 All sites under certain LAPD/LAPD2 can't call normally

1. Symptoms
3-11
SJ-20110531095035-006|2011-09-30(R1.1)
All sites under LAPD/LAPD2 can't call normally.

2. Troubleshooting
a. Check the LAPD/LAPD2 alarm to view whether the board can't work normally. If
yes, refer to troubleshooting in Board Alarm.
b. Reset this LAPD/LAPD2 board from equipment.
c.
center.
3. Post inspection
l You can call normally at all sites under LAPD/LAPD2.
3.3.7 Mass users belonging to other type can't call normally

1. Symptoms
Mass users belonging to other type can't call normally.
2. Troubleshooting
a. Check whether data is changed at BSN or CN side. If yes, you shall restore original
backup data.
b. Trace and record messages at interface Abis and A to analyze it. Determine it is
caused by the problem at BSC or CN side based on signaling process.
c.
Analyze SDCCH assignment failure rate, TCH allocation failure rate, TCH
assignment failure rate, SDCCH congestion rate, and TCH congestion rate in KPI
indicators, to determine which phase the fault occurs.
d. Contact local ZTE office or customer service support center.

3. Post inspection
l user can call normally.
3.4 Maintenance Guide about PS Service Faults

Maintenance guide about PS service faults contains the following contents:
l
l
l
Mass user can't use GPRS service;

All users under whole BSC can't use GPRS service;
Some cells can't use GPRS service.
3.4.1 Mass user can't use GPRS service

1. Symptoms
3-12
SJ-20110531095035-006|2011-09-30(R1.1)
Lots of users can't use GPRS service

2. Troubleshooting
Based on quantity and domain of claiming users and in combination with KPI analysis
and test, you can determine the influence scope of this fault. According to different
service scope, you can use the following troubleshooting methods.
For more information, refer to All Users Under Whole BSC Can't Use GPRS Service
and Some Cells Can't Use GPRS Service.
3. Post inspection
l You can normally use GPRS service.
3.4.2 All users under whole BSC can't use GPRS service
1. Symptoms
Lots of users under whole BSC can't use GPRS service
2. Troubleshooting
a. Check the DTB or GIPB/GIPB2 alarm at interface Gb to view whether the board
can't work normally. If yes, refer to troubleshooting in Board Alarm.
b. Check the UPPB/UPPB2 alarm to view whether the board can't work normally. If
yes, refer to troubleshooting in Board Alarm.
c.
View E1 alarm at interface Gb to check whether E1 transmission is interrupted. If

yes, check E1 cable, and inform transmission engineer to check E1 transmission.
d. Check whether IP network at interface Gb is disconnected. If yes, you shall check

whether IP cable is normal, office direction from BSC to SGSN is normal, NSVC
state is normal, and relevant configuration is correct.
e. Reset GIPB/GIPB2 or DTB board at interface Gb.
f.
Reset UPPB/UPPB2 board.
g. If the alarms still continue, you shall contact local ZTE office or customer service
center.
3. Post inspection
l You can normally use GPRS service of this BSC.
3.4.3 Some cells can't use GPRS service

1. Symptoms
Lots of users in some cells can't use GPRS service
2. Troubleshooting
3-13
SJ-20110531095035-006|2011-09-30(R1.1)
a. Check the UPPB/UPPB2 alarm to view whether the board or certain CPU can't
work normally. If yes, refer to troubleshooting in Board Alarm.
b. In dynamic data management interface, view BVC state in the cell and check
whether BVC is blocked. If yes, unblock the BVC.
c.
Confirm whether lots of GRPS data are changed prior to the fault. If yes, you shall
restore the data firstly.
center.
3. Post inspection
l You can normally use GPRS service in this cell.
3-14
SJ-20110531095035-006|2011-09-30(R1.1)
Chapter 4
Fault Feedback Information

Table of Contents
Prerequisite of fault feedback .....................................................................................4-1
Feedback Data That Shall be Recorded .....................................................................4-3
The method to get system record ...............................................................................4-6
4.1 Prerequisite of fault feedback

Prerequisite of fault feedback:
1.
2.
3.
4.
5.
Fault time
Fault description
Detailed troubleshooting steps
System record
Fault feedback report
Presented below are a brief description of different elements.

1. Fault time
Describes specific time of the fault, including start/end time of the fault.
2. Fault description
a. Describes the fault symptom, such as board state, dynamic state, NM alarm,
messages, and calling state. These are the basis of field troubleshooting.
b. It describes the fault scope, such as whole BSC or site.
c.
If you can't express it clearly, you shall copy the pictures. For the channel state in
dynamic management and error messages occurred during operation, you shall
copy it in picture mode.
3. Detailed troubleshooting steps

a. Steps and time about field troubleshooting.
b. It includes the operation cases that may cause the fault.
c.
It is recommended that field operators keep a good habit to record operation

procedures for the server, so it can provide a convenience to check whether there
is any operation error. For the operations on the server, you can use the record
function of NETTERM to remember the operation procedures.
4. System record
It records system operation state and error messages, which is the primary method to
find system errors.
4-1
SJ-20110531095035-006|2011-09-30(R1.1)
5. Fault feedback report

Table 4-1 shows fault feedback report.
Table 4-1 Field Fault Feedback Report
Feed-
Re-
back
ceived
by
Feedback time
Con-
by
Con-
tact
tact
person
Phone No.
e-mail
Source
unit
Model
Fault
Ver-
time,
Network capacity
sion
symptom,
and
description
Attached pages
Description of
field
procedure
and
handling
Attached pages
Field
data
feedback
Attached pages
Analysis and
preliminary
Attached pages
com-
Han-
ments
dled by
Day
4-2
SJ-20110531095035-006|2011-09-30(R1.1)
Chapter 4 Fault Feedback Information
Final
comments
and
conclusion
4.2 Feedback Data That Shall be Recorded

Table 4-2 shows the feedback data required by BSC faults.
Table 4-2 Feedback data required by BSC faults
System feedback records
The method to get system
required
Purpose of Record
record
The indicators contain the elBoard indicator conditions on
ementary
fault
board operation.
information
about
Omitted
Printing file of the equipment

(including
active/standby
MP
Record exceptional cases oc-
for central peripheral modules):
curred during BSC operation in
Exc_Omp.txt, Exc_pp.txt
equipment printings.
Configuration
information
Refer to Get Device Printing File.

in
ZDB file in all active MP for the
BSC, to learn configuration in-
equipment or ZDB file for NM.
formation.
Refer to Get ZDB File.
Configuration information in NM,

ZTD backup files in NM.
to learn configuration informa-
Refer to Get Data Backup Ztd
tion.
File From OMM.
Screenshot if board in-stock version, general software version,
Software settings about the
and specified version settings.
board
Refer to Get Software Setting.
Alarm file, picking up historical

alarms within a week and current
Alarm file records all alarms in
alarms.
the system.
Notification file, picking up his-
Notification file is the supple-
torical files within a week.
ment of system alarm.
Refer to Get Alarm File.
Refer to Get Notification File.
Different version has different

Equipment and NM version
functions, so you shall return
Feedback shall be sent based
number.
feedback.
on the version of field records.
4-3
SJ-20110531095035-006|2011-09-30(R1.1)
required
Purpose of Record
record
Performance report within 1

hour before and after the fault.
Refer to Get 1 Hour's Perfor-
Do measurement according to
You can find system operation
mance Data Before And After
cell level.
state in performance statistics.
Fault.
about signaling tracing at inter-
Signaling is a very useful tool to
Refer to Get Tracing Signal At
face A.
locate questions.
Interface A.
For the fault related with interface A, you shall send feedback
If the problem is related with interface A or whole BSC, you

shall send feedback about dynamic state of the link at interface A.
Refer to Query Dynamic Data At

State of the link at interface A.
Interface A.
back about signaling tracing at
interface Abis.
locate questions.
Interface Abis.
state, including cell, carrier, and
Channel state is another path to
channel.
judge system state.
Site.
state, including cell, carrier, and
BVC and NSVC states of the cell
Refer to Query BVC And NSVC
channel.
is used to judge system state.
State.
vice, you shall send feedback
Refer to Trace PS Service Sig-
about signaling about PS.
locate questions.
nal.
For the fault related with interface Abis, you shall send feed-
If it involves calling faults at site,

you shall return the feedback
information about dynamic site
If it involves calling faults at site,

you shall return the feedback
information about dynamic site
For the fault related with PS ser-
Operation log of preset machine

Check
whether
data exists
Operation condition of preset
Refer to Get Operation Log Of
machine
Preset Machine.
overstocked
Refer to Check Whether OverAnalyze incomplete data
stocked Data Exists.
Table 4-3 shows the feedback data required by NM faults.
4-4
SJ-20110531095035-006|2011-09-30(R1.1)
Table 4-3 Feedback data required by NM faults

required
Check the disk space
Purpose of Record
record
Reflect the disk condition
Refer to Query Disk Space.
Record the operation conditions

NM printing file
of NM system.
Refer to Get NM Printing File.
Configuration information in NM,

ZTD backup files in NM.
to learn configuration informa-
Refer to Get Data Backup Ztd
tion.
File From OMM.
Important configuration in the

NM profile
system.
Refer to Get NM Profile.

Refer to Get Operation Log At
Operation log at client.
Record NM operations on site.
Client.
For international office, locate
Refer to View System Time
System time zone
specific time.
Zone.
Different version supports differNE version
ent functions.
Refer to View NM Version.
Table 4-4 shows the feedback data required by site faults.

Table 4-4 Feedback data required by site faults
required
Purpose of Record
record
Identify the relation between site

name and its number, so you
Identify site name, number and
can find corresponding site in
its model.
ZDB file.
Omitted
including cell, carrier, and chan-
Channel state is another path to
nel.
judge system state.
Site.
Reflect the information while the
O&M signaling trace
site is starting.
Interface Abis.
Signaling trace at interface Abis.
Record call cases in the system.
Interface Abis.
Dynamic observation condition,
Historical alarm file within a

week and historical notification
Refer to Get Alarm File and Get
file within a week.
Record fault information.
Notification File.
Different version supports differ-
Refer to Get BTS Software Set-
Site version
ent functions.
ting.
4-5
SJ-20110531095035-006|2011-09-30(R1.1)
required
NE ZDB file
Purpose of Record
record
Record and confirm NE configu-
Refer to Get Equipment ZDB
ration information.
File.
4.3 The method to get system record

4.3.1 Get device printing file
Steps
1. Create a directory to save files on OMM server.
2. Use command ftp to connect OMP/OMP2 on OMM. Both username and password are
zte at specified port 21.
3. Use command cd /DOC0 to enter into DATA0 directory.
4. Use command "get" to get Exc_Omp.txt and Exc_pp.txt files.
5. After the files are downloaded onto OMM server, you can use ftp tool, such as
CUTEFTP, to upload the files to client.
End of Steps
Example
1.
2.
3.
4.
5.
6.
7.
mkdir bsc1
cd bsc1
ftp 172.20.6.1 21
cd /DOC0
get Exc_pp.txt
get Exc_Omp.txt
bye
4.3.2 Get ZDB file

4.3.2.1 Get equipment ZDB file
Context
ZDB file is under /DOC0/DATA1 on OMP/OMP2. 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.
4-6
SJ-20110531095035-006|2011-09-30(R1.1)
Steps
1. Creat a directory to save files on OMM server.
2. Use command ftp to connect OMP/OMP2 on OMM. Both username and password are
zte at specified port 21.
3. Get required ZDB files under DATA1 directory.
a. Use command cd to enter into /DOC0/DATA1.
b. Use command get filename to download CFGTABLE.ZDB, VERTABLE.ZDB, and
DBVER.ZDB one by one.
4. After the files are downloaded onto OMM server, you can use ftp tool, such as
CUTEFTP, to upload the files to client and compress it.
End of Steps
Example
1.
2.
3.
4.
5.
6.
7.
8.
cd $OMCHOME
mkdir bsc1
cd bsc1
ftp 172.20.6.1 21
cd /DOC0/DATA1
get CfgTable.ZDB
get DBVer.ZDB
get VERTABLE.ZDB
4.3.2.2 Get OMM ZDB file

Context
OMM 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.
Steps
1. Generated file is too small during incremental synchronization. You can use ls l
command to veiw the file size. If current ZDB file belongs to the one genereated on
incremental synchronization, you can do a synchronization action on whole table on
NM client, this will generate new complete ZDB file.
2. Use ftp tool, such as CUTEFTP, to transfer ZDB file to client.
End of Steps
4-7
SJ-20110531095035-006|2011-09-30(R1.1)
4.3.3 Get data backup ztd file from OMM

Steps
1. Right-click the NE in physical view of topology management, select NE Management
> Configuration Management in floating menu, to call configuration management
interface.
2. Select Management > Data Management > Data Backup.
3. In displayed Data Backup window, select backup path, /CM, (normally on OMM
server). Input prefix of backup filename, and backup description, and select a NE to
be backed-up. After acknowledgement, click OK button.
4. Use ftp tool with username/password as sysbak and port 21, to download backed-up
ztd file from OMM server through ftp mode.
End of Steps
4.3.4 Get software setting

4.3.4.1 Get BSC software setting
Steps
> Software Version Management in floating menu, to call configuration management
interface.
2. In Software Version Management interface, select BSC Software Management.
3. For setting of software version, equipment data may be inconsistent with NM data, so
if you can't determine whether it is consistent, you shall do the action of "synchronize
version data from NE to OMC". synchronization operation may remove NM software
setting, operate the data based on actual equipment condition, and re-establish NM
software settings.
4. After the synchronization, snap three screenshots for version file, common version,
and special version of BSC. Save it as jpg file and send feedback.
End of Steps
4.3.4.2 Get BTS software setting

BTS software setting can fed back by getting VerTable.ZDB. For detailed operations, refer
to Get equipment ZDB file.
4-8
SJ-20110531095035-006|2011-09-30(R1.1)
4.3.5 Get alarm file

Steps
1. Start Alarm Management at client. Select View History Alarms in View Alarm menu
option of Alarm Management interface, as shown in Figure 4-1.
Figure 4-1 Select View History Alarms
2. Select Quick Search in Query Setting of History Alarm.

3. Select System Type in Query History Alarm window, and select all alarm types in
System Type.
4. 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 4-2.
4-9
SJ-20110531095035-006|2011-09-30(R1.1)
Figure 4-2 Set query time of alarm
5. In NE Type, enter IBSC%. You can use % to do fuzzy searching, as shown in Figure
4-3.
4-10
SJ-20110531095035-006|2011-09-30(R1.1)
Figure 4-3 Set the Type of Alarm NE
6. Click OK to output alarm data.

7. Click Export button to export queried alarms.
8. In Save window, select the proper path and click Save, as shown in Figure 4-4.
4-11
SJ-20110531095035-006|2011-09-30(R1.1)
Figure 4-4 Alarm Save Window
Note:
You also can right-click the NE in resource view of alarm management, select Show
History Alarms in floating menu to view history alarm, as shown in Figure 4-5. You
can't select alarm Happen Time by using this method.
Figure 4-5 Displaying history alarms of the selected NE
End of Steps
4-12
SJ-20110531095035-006|2011-09-30(R1.1)
4.3.6 fanGet notification file

Steps
1. Start Alarm Management at client. Select View Notifications in View Alarm menu
option of Alarm Management interface, as shown in Figure 4-6.
Figure 4-6 Select View Notifications
2. Select Quick Search in Query Setting of Notification, as shown in Figure 4-7.
Figure 4-7 Select Quick Search
3. Select System Type in Query Notification window, and select all notification types in
System Type, as shown in Figure 4-8.
4-13
SJ-20110531095035-006|2011-09-30(R1.1)
Figure 4-8 Query Notification Window
4. Select start/end time in Happen Time, as shown in Figure 4-9.
4-14
SJ-20110531095035-006|2011-09-30(R1.1)
Figure 4-9 Set query time of notification
5. In NE Type, enter IBSC%. You can use % to do fuzzy searching, as shown in Figure
4-10.
4-15
SJ-20110531095035-006|2011-09-30(R1.1)
Figure 4-10 Set the Type of Nofication NE
6. Click OK to output notification data.

7. Click Export button to export queried notifications.
8. In Save window, select the proper path and click Save, as shown in Figure 4-11.
4-16
SJ-20110531095035-006|2011-09-30(R1.1)
Figure 4-11 Notification Save Window
End of Steps
4.3.7 Get 1 hour's performance data before and after fault

Steps
1. Start Performance Management at client, select the NE to be viewed in resource
view. Select Performance Management > Performance Data Query menu, as
shown in Figure 4-12.
Figure 4-12 Select Performance Management and Performance Data Query
2. In Query Index of Integrated Query interface, select NE type as BSC Elements, and
select object type as CellFunction Type, select KPI index and PI index, as shown in
Figure 4-13.
4-17
SJ-20110531095035-006|2011-09-30(R1.1)
Figure 4-13 Integrated Query Interface
3. Select customized time in Query Time tab, query granularity is 15 minutes, as shown
in Figure 4-14.
Figure 4-14 Set Query Time of Performance Data
4. Select the NE to be queried in Query Object tab, and query mode is Cell. Select the
cell to be queried in measurement object, and summary mode is Cell (Original Polled
Object), as shown in Figure 4-15.
4-18
SJ-20110531095035-006|2011-09-30(R1.1)
Figure 4-15 Set Query Object of Performance Data
5. Queried data shall be exported as EXCEL report.

6. Repeat above steps, query basic measurement data of CS and export it as EXCEL
report, as shown in Figure 4-16.
Figure 4-16 Select Basic Measurement Data of CS
End of Steps
4-19
SJ-20110531095035-006|2011-09-30(R1.1)
4.3.8 Get tracing signal at interface A

Steps
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 System Setting, and access to Parameter Setting interface to configure
signaling trace. In Record Setting tab, configure Capacity of Signal Window as
20000. Select File Spliting, 5000 for each file. Click Save button, as shown in Figure
4-17.
Figure 4-17 Parameter Setting interface
3. Configure in Trace Setting interface, select the BSC to be traced, and click Update
Configuration button, as shown in Figure 4-18.
4-20
SJ-20110531095035-006|2011-09-30(R1.1)
Figure 4-18 Trace Setting interface
4. After successfully updating configuration, select SCCP. In SCCP option, select

Module No, and select Subsystem No. as 254, as shown in Figure 4-19.
Figure 4-19 Select SCCP
5. Select M3UA . In M3UA, select coupling ID, corresponding coupling SCCP, and
direction, as shown in Figure 4-20.
4-21
SJ-20110531095035-006|2011-09-30(R1.1)
Figure 4-20 Select M3UA
6. After stopping trace, select File > Save all as .tra. Save all signaling trace result as
tra format, as shown in Figure 4-21.
Figure 4-21 Save Signaling Trace Result
7. 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 4-22.
4-22
SJ-20110531095035-006|2011-09-30(R1.1)
Figure 4-22 Signaling Trace Save Window
Note:
Trace at interface A has great influence on system load. Each trace can't exceed 5
minutes.
End of Steps
4.3.9 Query dynamic data at interface A

Steps
1. Login in NM client, right-click the NE in physical view of topology management, select
NE Management Dynamic Data Management in floating menu, to call Dynamic Data
Management interface.
2. In configuration resource tree, select and expand management NE node, double-click
corresponding dynamic data management node, enter dynamic data management
interface, and you can do A-interface PCM, A-interface trunk management, and IPA
resource management.
3. 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.
4. If using IP A-interface, in IPA Management tab, click Query button to query DSP state.
End of Steps
4-23
SJ-20110531095035-006|2011-09-30(R1.1)
4.3.10 Get tracing signal at interface Abis

Steps
1. Configure server procedure for signaling trace, start server program, start and logon
signaling trace client.
Note:
20000. Select File Spliting, 5000 for each file. Click Save button, as shown in Figure
4-23.
Figure 4-23 Parameter Setting interface at Abis
3. Configure in Trace Setting interface, select the BSC to be traced, and click Update
Configuration button.
4. After successfully updating configuration, select CS and OAM, select the site to be
traced in CS and OAM interfaces. Select all traced entries in Tracing Entry of CS,
select a site in OAM, as shown in Figure 4-24 and Figure 4-25.
4-24
SJ-20110531095035-006|2011-09-30(R1.1)
Figure 4-24 CS interface
Figure 4-25 OAM interface
5.
End of Steps
4-25
SJ-20110531095035-006|2011-09-30(R1.1)
4.3.11 Query dynamic data at site

Steps
> Dynamic Data Management in floating menu, to enter Dynamic Data Management
interface.
2. In configuration resource tree, select and expand BSC management NE node.
3. Double-click corresponding dynamic data management node at site, enter into
Dynamic Data Management interface.
So you can perform radio resource
management and BTS equipment management.
Table 4-5 shows dynamic data management function.
Table 4-5 Dynamic Data Management Function
Category
Function
Description
Cell management
query the status of cell
TRX management
Query the state of TRX
Channel Management
Query channel state

Query channel statistics on a mod-
Radio Resources Management
Module Management
ule
BVC Management
Query the BVC status of cell
Cell channel management
Query channel statistics of a cell

Query timeslot state measure-
Timeslot management at Abis
BTS equipment management operation
ment of resource pool at Abis
Timeslot resource management at
Query timeslot state of resource
Abis
pool at Abis
LAPD state management
Query LAPD link state at site
Loopback Management
Query the loopback state
End of Steps
4.3.12 Trace PS service signal

Steps
1. Configure server procedure for signaling trace, start server program, start and logon
signaling trace client.
4-26
SJ-20110531095035-006|2011-09-30(R1.1)
Note:
20000. Select File Spliting, 5000 for each file. Click Save button.
3. In Trace Setting interface, select the BSC to be traced, and click Update
Configuration 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, and
NSVC to be traced in SNS (optional). Click OK button, as shown in Figure 4-26.
Figure 4-26 Trace Setting of PS service signal
6. After stopping trace, select File Save all as .tra. Save all signaling trace result as tra
format.
4-27
SJ-20110531095035-006|2011-09-30(R1.1)
7. Select the path to save in Save window, saved files contain .tra and .idx files. If
feedback, you shall send the both files.
End of Steps
4.3.13 Query BVC and NSVC state

Steps
> Dynamic Data Management in floating menu, to enter Dynamic Data Management
interface.
2. In configuration resource tree, select and expand management NE 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 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 Wireless Resource Management tab of Dynamic Data Management interface,
select BVC Management to query BVC state.
End of Steps
4.3.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.
4.3.15 Check whether overstocked data exists

Steps
1. Check
whether
OMM
server
data
is
$OMCHOME/gsmomcr/ibsc/zxgomcr-emf-pm.par/x-y/err.
GERAN subnet, x, and BSC management NE, y.
overstocked
in
x-y
represents
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.
Solution is as follows:
4-28
SJ-20110531095035-006|2011-09-30(R1.1)
i.
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.
ii.
Exceptional operation modes of oracle are diversified, and it is complicated to

solve it. It is recommend 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 NM 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 NM directory.
3. Check
whether
backed-up
configuration
management
files
under
/home/xxxxxxx/ums-svr/backup/sysmanager/cm in OMM server are overstocked.
4. Check
whether
backed-up
alarm
management
files
under
/export/home/xxxxxxx/ums-server/backup/sysmanager/fm on the server are
overstocked.
5. Check
whether
backed-up
performance
management
files
under
/export/home/xxxxxxx/ums-server/backup/sysmanager/pm on the server are
overstocked.
6. Check
whether
backed-up
log
management
/export/home/xxxxxxx/ums-server/backup/sysmanager/log on
overstocked.
files
under
the server are
7. Check
whether
backed-up
performance
configuration
files
under
/export/home/xxxxxxx/ums-server/backup/sysmanager/ueppm on the server are
overstocked.
End of Steps
4.3.16 Query disk space

Steps
1. For the Linux or Solaris system, use the commands df k and vmstat to query the
current disk space.
2. Use NETTERM to save operation procedure.
3. For the AIX system, use the commands df k and vmstat to query the current disk
space. For the AIX system, step 2 is unnecessary.
End of Steps
4-29
SJ-20110531095035-006|2011-09-30(R1.1)
4.3.17 Get NM printing file

Steps
1. Process printing file related with NM 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.
2. Use ftp tool, such as cuteftp, to get log file within NM fault period.
End of Steps
Example
1. bash-3.00$ cd $OMCHOME/log
2. bash-3.00$ ls
3. boot.log
server-20080117-0623-28443.log
server-20080117-1005-13029.log
server-20080117-1436-53392.log
4. consoleagent.log.0
server-20080117-0812-56822.log
server-20080117-1048-52694.log server-20080117-1516-54067.log
5. consoleagent.log.0.lck
6. bash-3.00$ pwd
7. /export/home/iomcr/iOMCR6.00.02f/ums-svr/log
4.3.18 Get NM profile

NM 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:
l
l
deploy-010muep.properties
deploy-*.properties
Real-time alarm file related with server and NM system is saved in

$OMCHOME/ums-svr/minos/minos-naf-rtalarm.par/conf. On OMM server, this file is
saved in $OMCHOME/gsmomcr/ibsc/zxgomcr-naf-rtalarm.par/conf. Required profile is
as follows:
l
l
fmmgr.properties
nafproc.properties
4.3.19 Get operation log at client

Steps
1. Right-click the NE in physical view of topology management, select Query NE Log >
Operation Log in floating menu, to call log management tool at NM client, as shown
in Figure 4-27.
4-30
SJ-20110531095035-006|2011-09-30(R1.1)
Figure 4-27 Select Query Operation Log
2. In Query Operation Log window, customize operation time to query, or query all
operation log, and click OK button, as shown in Figure 4-28.
Figure 4-28 Query Operation Log window
4-31
SJ-20110531095035-006|2011-09-30(R1.1)
3. After successfully querying, export the log to excel.

End of Steps
4.3.20 View system time zone

Steps
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.
End of Steps
4.3.21 View NM version

On client interface of NM system, click Help > About, and display NM version information.
4.3.22 Maintenance Record List

4.3.22.1 Emergency Maintenance Record List
ReFeed-
ceived
back by
Feedback time
Contact
by
Contact
person
Phone No.
e-mail
Source
unit
Fault
Model
Network capacity
Version
time,
symptom,
and description
Attached pages
4-32
SJ-20110531095035-006|2011-09-30(R1.1)
Description
of
field
procedure
and
handling
Attached pages
Field
data
feedback
Attached pages
Analysis and
preliminary
Attached pages
com-
Han-
ments
dled by
Day
Final
comments
and
conclusion
4-33
SJ-20110531095035-006|2011-09-30(R1.1)
4-34
SJ-20110531095035-006|2011-09-30(R1.1)
Figures
Figure 1-1 Flow of Emergency Maintenance ............................................................. 1-4
Figure 2-1 Data Backup Interface ............................................................................. 2-2
Figure 2-2 Data Backup Result Interface................................................................... 2-2
Figure 4-1 Select View History Alarms.................................................................... 4-9
Figure 4-2 Set query time of alarm .......................................................................... 4-10
Figure 4-3 Set the Type of Alarm NE....................................................................... 4-11
Figure 4-4 Alarm Save Window .............................................................................. 4-12
Figure 4-5 Displaying history alarms of the selected NE.......................................... 4-12
Figure 4-6 Select View Notifications ..................................................................... 4-13
Figure 4-7 Select Quick Search ............................................................................. 4-13
Figure 4-8 Query Notification Window .................................................................. 4-14
Figure 4-9 Set query time of notification .................................................................. 4-15
Figure 4-10 Set the Type of Nofication NE .............................................................. 4-16
Figure 4-11 Notification Save Window .................................................................... 4-17
Figure 4-12 Select Performance Management and Performance Data
Query ................................................................................................... 4-17
Figure 4-13 Integrated Query Interface.................................................................. 4-18
Figure 4-14 Set Query Time of Performance Data .................................................. 4-18
Figure 4-15 Set Query Object of Performance Data ................................................ 4-19
Figure 4-16 Select Basic Measurement Data of CS ................................................ 4-19
Figure 4-17 Parameter Setting interface................................................................ 4-20
Figure 4-18 Trace Setting interface........................................................................ 4-21
Figure 4-19 Select SCCP........................................................................................ 4-21
Figure 4-20 Select M3UA ....................................................................................... 4-22
Figure 4-21 Save Signaling Trace Result ................................................................ 4-22
Figure 4-22 Signaling Trace Save Window ............................................................. 4-23
Figure 4-23 Parameter Setting interface at Abis .................................................... 4-24
Figure 4-24 CS interface......................................................................................... 4-25
Figure 4-25 OAM interface...................................................................................... 4-25
Figure 4-26 Trace Setting of PS service signal........................................................ 4-27
Figure 4-27 Select Query Operation Log .............................................................. 4-31
Figure 4-28 Query Operation Log window ............................................................ 4-31
Figures
Tables
Table 1-1 User complaint .......................................................................................... 1-1
Table 1-2 Alarm report on emergency maintenance .................................................. 1-1
Table 1-3 KPI Indicator.............................................................................................. 1-2
Table 4-1 Field Fault Feedback Report ..................................................................... 4-2
Table 4-2 Feedback data required by BSC faults ...................................................... 4-3
Table 4-3 Feedback data required by NM faults ........................................................ 4-5
Table 4-4 Feedback data required by site faults ........................................................ 4-5
Table 4-5 Dynamic Data Management Function...................................................... 4-26
III
Tables
Glossary
CPU
- Central Processing Unit
IP
- Internet Protocol
MSC
- Mobile Switching Center
NE
- Network Element
NMS
- Network Management System
OMM
- Operation & Maintenance Module
SCCP
- Signaling Connection Control Part
SDCCH
- Stand alone Dedicated Control Channel
TCH
- Traffic Channel

ZXG10 iBSC (V6.20.71) Base Station Controller Emergency Maintenance PDF

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

ZXG10 iBSC (V6.20.71) Base Station Controller Emergency Maintenance PDF

Caricato da

Copyright:

Formati disponibili

ZXG10 iBSC

Base Station Controller

Additionally, the contents of this document are protected by

contractual confidentiality obligations.

Serial Number: SJ-20110531095035-006

Chapter 2 Preparation of Emergency Maintenance ................................ 2-1

Chapter 3 Guide of Emergency Maintenance .......................................... 3-1

3.2.3 Disconnection between equipment and OMM server .................................. 3-8

Chapter 4 Fault Feedback Information ..................................................... 4-1

4.3.21 View NM version .................................................................................. 4-32

About This Manual

What Is in This Manual

Describes applicable scope, guideline, and process of ZXG10 iBSC

Describes preparation of ZXG10 iBSC emergency maintenance.

Describes guideline of ZXG10 iBSC emergency maintenance on

Chapter 4 Fault Feedback

ZXG10 iBSC emergency maintenance.

1.1 Scope of Emergency Maintenance

Lots of speech user can't access;

ther check alarm information and KPI measure-

Lots of MS can't be acted as called/caller;

ment result, to determine whether emergent

Lots of users can't use GPRS service

Board alarm out of non-active/standby mode

ZTE Proprietary and Confidential

ZXG10 iBSC Emergency Maintenance

Level 1 alarm on lost clock reference source

Alarms related with interface A

Alarms on flow control

CPUToo high load

Relevant transmission alarms

SDH/SONET: loss of signal

3. Analyzing a performance report

While KPI is changed exceptionally, you shall confirm whether emergency

Table 1-3 KPI Indicator

Call success rate

Handover success rate

TCH call drop rate

ZTE Proprietary and Confidential

Chapter 1 Overview of Emergency Maintenance

1.2 Guide Concept of Emergency Maintenance

1.3 Flow of Emergency Maintenance

Determine the fault scope;

Figure 1-1 shows the flow of emergency maintenance.

ZTE Proprietary and Confidential

ZXG10 iBSC Emergency Maintenance

Figure 1-1 Flow of Emergency Maintenance

1.3.1 Determine the fault scope

ZTE Proprietary and Confidential

Chapter 1 Overview of Emergency Maintenance

1.3.2 Locate fault reason and record exceptions

1.3.3 Fault Analysis

1.3.4 Critical solution

ZTE Proprietary and Confidential

ZXG10 iBSC Emergency Maintenance

1.3.5 Restore service

1.3.6 Observe restored services

1.3.7 Feedback information about emergency maintenance

1.3.8 Communication with customer

1.4 Precautions of Emergency Maintenance

1.5 Contact Information of Technical Support from ZTE

ZTE Proprietary and Confidential