Sjzl20083719-ZXG10 iBSC (V6.10) Maintenance Manual (Emergency Maintenance)

ZXG10 iBSC
Base Station Controller

Maintenance Manual
(Emergency Maintenance)
Version 6.10
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900 800-9830-9830
Fax: (86) 755 26772236
URL: http://support.zte.com.cn
E-mail: doc@zte.com.cn

LEGAL INFORMATION

Copyright 2006 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
Date Revision No. Serial No. Reason for Issue
April 10, 2009 R1.0 sjzl20083719 First Edition

ZTE CORPORATION
Values Your Comments & Suggestions!
Your opinion is of great value and will help us improve the quality of our product
documentation and offer better services to our customers.
Please fax to (86) 755-26772236 or mail to Technical Delivery Department, ZTE
University, Dameisha, Yantian District, Shenzhen, Guangdong, P. R. China 518083.
Thank you for your cooperation!
Document
Name
ZXG10 iBSC (V6.10) Base Station Controller Maintenance Manual (Emergency Maintenance)
Product Version V6.10
Document Revision
Number
R1.0
Serial No. sjzl20083719
Equipment
Installation Date

Presentation:
(Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization,
Appearance)
Good Fair Average Poor Bad N/A
Accessibility:
(Contents, Index, Headings, Numbering, Glossary)
Your evaluation
of this
documentation
I ntelligibility:
(Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)
Your
suggestions for
improvement of
this
documentation
Please check the suggestions which you feel can improve this documentation:
Improve the overview/introduction Make it more concise/brief
Improve the Contents Add more step-by-step procedures/tutorials
Improve the organization Add more troubleshooting information
Include more figures Make it less technical
Add more examples Add more/better quick reference aids
Add more detail Improve the index
Other suggestions
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
__________________________________________________________________________
# Please feel free to write any comments on an attached sheet.
If you wish to be contacted regarding your comments, please complete the following:
Name Company
Postcode Address
Telephone E-mail

This page is intentionally blank.
Contents

About This Manual ............................................................ i
Purpose................................................................................ i
Intended Audience ................................................................. i
Prerequisite Skill and Knowledge.............................................. i
What Is in This Manual ........................................................... i
Related Documentation.......................................................... ii
Conventions......................................................................... ii
How to Get in Touch............................................................. iii
Chapter 1.......................................................................... 1
Overview of Emergency Maintenance............................. 1
Scope of Emergency Maintenance......................................1
Guide Concept of Emergency Maintenance..........................3
Flow of Emergency Maintenance........................................3
Determine the Fault Scope ..................................................... 5
Find Fault Reason and Record Exceptions ................................. 6
Fault Analysis....................................................................... 6
Critical Solution .................................................................... 6
Restore Service .................................................................... 7
Observe Restored Services..................................................... 7
Feedback Information about Emergency Maintenance................. 7
Communication with Customer................................................ 7
Precautions of Emergency Maintenance.................................... 8
Contact Information of Technical Support from ZTE ................... 8
Chapter 2.......................................................................... 9
Preparation of Emergency Maintenance......................... 9
Daily Preparation of Emergency Maintenance ......................9
Data Backup and System Inspection........................................ 9
Establish Remote Maintenance Station ................................... 13
Preparation of Important Spare Parts..................................... 13

Holiday Preparation of Emergency Maintenance................. 13
Load Monitor ......................................................................13
Load Reduction Measures .....................................................14
Chapter 3........................................................................15
Emergency Maintenance Guide.....................................15
Maintenance Guide about Major Alarm............................. 15
Board Alarm.......................................................................15
Clock Alarms ......................................................................17
Alarms Related with Interface A ............................................18
Alarms on Flow Control ........................................................19
Maintenance Guide about ISMG Faults ............................. 20
Maintenance Guide about CS Service Faults ...................... 21
Mass Users Can Not Call Normally..........................................21
All Sites under BSC Can Not Call Normally ..............................22
All Sites under Certain Module in BSC Can Not Call Normally .....22
All Sites under Certain Resource Shelf Can Not Call Normally.....23
All Sites under Certain BIPB Can Not Call Normally...................23
All Sites under Certain LAPD Can Not Call Normally ..................23
Mass Users Belonging To Other Type Can Not Call Normally.......24
Maintenance Guide about PS Service Faults ...................... 24
Mass Users Can Not Use GPRS Service ...................................24
All Users under Whole BSC Can Not Use GPRS Service..............25
Some Cells Can Not Use GPRS Service ...................................25
Chapter 4........................................................................27
Fault Feedback Information..........................................27
Prerequisite of Fault Feedback ........................................ 27
Feedback Data That Shall be Recorded............................. 29
Methods to Get System Records...................................... 32
Get Device Printing File ........................................................32
Get ZDB File.......................................................................33
Get Data Backup ztd File from ISMG ......................................34
Get Software Setting ...........................................................35
Get Alarm File.....................................................................35
Get Notification File .............................................................39
Get 1 Hour's Performance Data Before and After Fault ..............42
Get Tracing Signal at Interface A ...........................................45

Query Dynamic Data at Interface A ....................................... 47
Get Tracing Signal at Interface Abis....................................... 48
Query Dynamic Data at Site ................................................. 49
Query BVC and NSVC State.................................................. 50
Trace PS Service Signal ....................................................... 51
Get Operation Log of Preset Machine ..................................... 52
Check Whether Overstocked Data Exists................................. 52
Query Disk Space ............................................................... 53
Get ISMG Printing File ......................................................... 53
Get ISMG Profile ................................................................. 54
Get Operation Log at Client .................................................. 54
View System Time Zone....................................................... 56
View ISMG version.............................................................. 56
Appendix A..................................................................... 57
List of Emergency Maintenance Records ...................... 57
Appendix B..................................................................... 59
Abbreviations................................................................. 59
Appendix C..................................................................... 61
Figures............................................................................ 61
Tables............................................................................. 63


Confidential and Proprietary Information of ZTE CORPORATION i
About This Manual

Purpose
This manual introduces the definitions, formulas, and influence
factors of common KPI, and introduces the typical cases in KPI
optimization project.
Intended Audience
This document is intended for engineers and technicians who
perform operation activities on ZXG10 iBSC.
Prerequisite Skill and Knowledge
To use this document effectively, users should have a general
understanding of wireless telecommunications technology.
What Is in This Manual
This manual contains the following chapters:
TAB L E 1 - CHAPTER SUMMARY
Chapter Summary
Chapter 1, Introduction
of KPI in CS Domain
Introduces descriptions, definitions,
formulas, and units for several kinds of
KPI in CS domain.
Chapter 2, Introduction
of KPI in PS Domain
Introduces description, definition, formula,
and unit for several kinds of KPI in PS
domain.
Appendix A, Reference
KPI
Lists some reference KPIs.
Appendix B,
Abbreviation
Lists all abbreviations used in this manual.
Appendix C
Tables
Lists the tables in this manual.


ii Confidential and Proprietary Information of ZTE CORPORATION

Chapter Summary
Index Lists the index of this manual.
Related Documentation
The following documentation is related to this manual:
ZXG10 iBSC (V6.10) Base Station Controller Documentation
Guide
ZXG10 iBSC (V6.10) Base Station Controller Technical
Manual
ZXG10 iBSC (V6.10) Base Station Controller Hardware
Manual
ZXG10 iBSC (V6.10) Base Station Controller Installation
Manual
ZXG10 iBSC (V6.10) Base Station Controller Performance
Counters Manual Volume I
ZXG10 iBSC (V6.10) Base Station Controller Performance
Counters Manual Volume II
ZXG10 iBSC (V6.10) Base Station Controller Maintenance
Manual (Troubleshooting)
ZXG10 iBSC (V6.10) Base Station Controller KPI Reference
Manual
ZXG10 iBSC (V6.10) Base Station Controller Maintenance
Manual (Routine Maintenance)
ZXG10 BSS (V6.10) Base Station Subsystem Alarm Handling
Manual
ZXG10 BSS (V6.10) Base Station Subsystem Notification
Handling Manual
Conventions
ZTE documents employ the following typographical conventions.
TAB L E 2 - TYPOGRAPHI CAL CONVENTI ONS
Typeface Meaning
Italics References to other Manuals and documents.
Quotes Links on screens.
Bold Menus, menu options, function names, input
fields, radio button names, check boxes, drop-
down lists, dialog box names, window names.
CAPS Keys on the keyboard and buttons on screens
Typographical
Conventions

About This Manual

Confidential and Proprietary Information of ZTE CORPORATION iii
Typeface Meaning
and company name.
Const ant wi dt h
Text that you type, program code, files and
directory names, and function names.
[ ] Optional parameters.
{ } Mandatory parameters.
| Select one of the parameters that are delimited
by it.

Note: Provides additional information about a
certain topic.

Checkpoint: Indicates that a particular step needs
to be checked before proceeding further.

Tip: Indicates a suggestion or hint to make things
easier or more productive for the reader.

TAB L E 3 - MOUSE OPERATI ON CONVENTI ONS
Typeface Meaning
Click Refers to clicking the primary mouse button (usually
the left mouse button) once.
Double-click Refers to quickly clicking the primary mouse button
(usually the left mouse button) twice.
Right-click Refers to clicking the secondary mouse button
(usually the right mouse button) once.
Drag Refers to pressing and holding a mouse button and
moving the mouse.

How to Get in Touch
The following sections provide information on how to obtain
support for the documentation and the software.
If you have problems, questions, comments, or suggestions
regarding your product, contact us by e-mail at
support@zte.com.cn. You can also call our customer support
center at (86) 755 26771900 and (86) 800-9830-9830.
ZTE welcomes your comments and suggestions on the quality
and usefulness of this document. For further questions,
comments, or suggestions on the documentation, you can
contact us by e-mail at doc@zte.com.cn; or you can fax your
comments and suggestions to (86) 755 26772236. You can also
browse our website at http://support.zte.com.cn, which contains
various interesting subjects like documentation, knowledge base,
forum and service request.
Mouse
Operation
Conventions
Customer
Support
Documentation
Support


iv Confidential and Proprietary Information of ZTE CORPORATION


Confidential and Proprietary Information of ZTE CORPORATION 1
Ch a p t e r 1
Overview of Emergency
Maintenance

This chapter mainly introduces applicable scope, flow, guideline,
and precautions about emergency maintenance.
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 4 shows user complaints about emergency maintenance.
TAB L E 4 - USER COMPL AI NT
Complaint content Description
Lots of speech user can
not access;
Lots of MS can not be
acted as called/caller;
Mass Users can not Use
GPRS Service
After receiving user complaints,
you shall further check alarm
information and KPI
measurement result, to
determine whether emergent
fault occurs.
2. Alarm inspection
Table 5 shows the alarm report that shall be viewed on
emergency maintenance.
TAB L E 5 - AL ARM REPORT ON EMERGENCY MAI NTENANCE
Alarm Type Alarm Description


2 Confidential and Proprietary Information of ZTE CORPORATION
Alarm Type Alarm Description
Alarms on spare boards, such as
OMP and CMP.
Active board alarm in
active/standby mode
Board Alarm
Board alarm out of non-
active/standby mode
Abnormal access clock
Phase-locked loop out of lock
Clock Alarms
Level 1 alarm on lost clock
reference source
Alarm on unreachable MTP3 office
Alarms Related with Interface A
SCCP Subsystem Unavailable
MSC Overload
Congestion at Signaling Point Alarms on flow control
Too High CPU Load
3. Analyzing a performance report
Normally, KPI index is not a direct condition to start emergency
maintenance. Table 6 shows the important KPI indices that shall
be viewed and analyzed on emergency maintenance.
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 index shall be used as a
subsidiary analysis tool and troubleshooting method.
TAB L E 6 - KPI I NDI CES
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

Chapter 1 - Overview of Emergency Maintenance
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.10) Base Station Controller Maintenance Manual
(Routine); for more information on normal troubleshooting, see
ZXG10 iBSC (V6.10) Base Station Controller Troubleshooting
Manual.
Prior to maintenance, you shall fully consider and follow below
principles about emergency maintenance.
You shall firstly determine fault scope prior to maintenance,
to do troubleshooting from inner to outer or from entire to
local.
During daily maintenance, the operator shall refer to ZXG10
iBSC and 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 ISMG
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.
Flow of Emergency
Maintenance
Emergency maintenance contains the following several steps:
1. Determine the fault scope;
2. Locate fault reason and record exceptions;


3. Fault analysis;
4. Critical solution;
5. Restore service;
6. Observe restored services;
7. Feedback information about emergency maintenance;
8. Communication with customer.
Figure 1 shows the flow of emergency maintenance.

FI GURE 1 - FL OW OF EMERGENCY MAI NTENANCE

Determine the Fault Scope
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.


Using signaling trace and probe facilities, find out proper CN,
BSC, BTS and relevant devices.
If you can not 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 index.
Query relevant indicators in KPI to judge the affected site
scope about the fault.
Determine whether it is global fault based on affected site.
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 emergency maintenance.
Find 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.
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.
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;
Mobile phone: 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 directly 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 possible.
Restore Service
Find out fault reason and quickly restore normal service through
remote or field ZTE technical support. If you can not 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.
Observe Restored Services
After the service is restored, you shall confirm whether normal
operation state has been restored. 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.
Feedback Information about
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.
Communication with Customer
For level 1 fault, 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.


Precautions of Emergency
Maintenance
Precautions of emergency maintenance are as follows.
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.
Contact Information of Technical
Support from ZTE
1. Telephone at global ZTE customer service center
Fixed phone: 8008301118.
Mobile phone: 4008301118.
2. Local ZTE office

Ch a p t e r 2
Preparation of Emergency
Maintenance

This chapter comprises of preparations for daily and holiday
emergency maintenance, mainly introduces the preparation
content and process about emergency maintenance, for
reference during troubleshooting by maintenance personnel.
Daily Preparation of
Daily preparation of emergency maintenance contains the
following three contents:
Data Backup and System Inspection
Establish Remote Maintenance Station
Preparation of Important Spare Parts
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.


Log in the database in configuration management interface at
ISMG client. Configuration data can be manually or automatically
backed-up.
Automatic Backup
1. Select Oracle node, click DatabaseServer Table
Collection, as shown in Figure 2.
FI GURE 2 - TAB L E COL L ECTI ON

2. In Table Collection, right-click Table Collection and select
Create, as shown in Figure 3.
FI GURE 3 - CREATE TAB L E COL L ECTI ON

Note:
Right-click Table Collection, select and click View in floating
menu, so you can view the content of the table collection.

Chapter 2 - Preparation of Emergency Maintenance
You can select not to create a new table collection, and directly
use default table collection task "Table Backup".
Right-click a table collection task, select and click "Manually
Execute" in floating menu, a interface to manually execute table
collection task pops up, and you can manually execute table
collection task according to tips.

3. Create Table Collection pops up, as shown in Figure 4.
FI GURE 4 - CREATE TAB L E COL L ECTI ON 1

4. Finish the setting based on prompts, select Plan Types as
Every Week, as shown in Figure 5.


FI GURE 5 - CREATE TAB L E COL L ECTI ON 2

Manual Backup
Refer to Get Data Backup ztd File from ISMG.
System Inspection
System inspection contains:
Board indicator status
Checking Foreground-Background Communication Link
Current alarms of BSC
The past 24-hour history alarms of BSC
The past 24-hour notifications of BSC
KPIs of BSC
A-interface status
Gb interface status
Board active/standby status
BSC operation log
Checking the alarm box
For system inspection, refer to "Check Operation State at BSC"
in ZXG10 iBSC (V6.10) Base Station Controller Routine
Maintenance Manual, 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

Chapter 2 - Preparation of Emergency Maintenance
the alarms still continue, you shall contact local ZTE office or
customer service center.
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.
Preparation of Important Spare Parts
You shall prepare for sufficient spare parts for important boards
on BSC, such as OMP, CMP, CLKG, CHUB, UIMC, UIMU, PSN, and
GLI.
Holiday Preparation of
Preparation in holiday mainly aims the case of large traffic, not
just the specific holiday period.
Load Monitor
1. View daily CPU load on BSC at busy time in holiday. CMP
load at BSC can not 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. 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.
Load Reduction Measures
1. Measures at BSC side.
Check whether FUC flow control at BSC side is opened.
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.
For individual site with large traffic, it is recommended to
open handover for preprocessing.
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.
Temporarily modify two or more paging as one paging mode
for CN.
2. Measures at CN side.
Don't send lots of paging messages at the same time.
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.
Timely start flow control function at CN side, preventing from
too high load leading to equipment degradation.

Ch a p t e r 3
Guide

This chapter mainly introduces the process and common
methods about emergency maintenance for reference by
maintenance personnel.
Maintenance Guide about
Major Alarm
Board Alarm
Active Board Alarm in Active/Standby Mode
The following alarms are found in real-time alarm for active
board.
198005379 Board offline or CPU in long-term resetting state
198005390 Wrong (CPU) sub-card position configured by
database
198066004 Communication blocked between module and
OMP
1. View the working state of standby board. If the standby
board is normal, active/standby switchover happens.
2. 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.
3. If the fault also exits on standby board, reset active/standby
board at the same time.
Symptoms
Steps


4. Change board;
5. If the alarms still continue, you shall contact local ZTE office
or customer service center.
The alarm is removed after checking on ISMG system.
Alarms related with OMP standby board
The following alarms are found in real-time alarm for OMP
backup board.
198005122 Communication link disconnected at control
plane between active/standby boards
1. View OMP board indicators to check whether red alarm
indicator, ALM, is on and the fault exists on OMP.
2. 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.
3. Check whether micro switch (ENUM) of the board is opened.
If ENUM switch is opened, you shall close it.
4. If above steps can not solve the fault, reset the board. First
try to reset remotely from ISMG. If the problem continues,
you can reset it by manually.
5. Replace OMP board.
If possible, switch the original standby OMP to active one while
the service traffic is minimized, and check whether the board is
normal.
Alarms related with CMP standby board
The following alarms are found in real-time alarm for CMP
backup board.
database
198005122 Communication link disconnected at control
plane between active/standby boards
1. View rack board indicators at BSC side to check whether red
alarm indicator, ALM, is on and the fault exists on ISMG.
Post inspection
Symptoms
Steps
Post inspection
Symptoms
Steps

Chapter 3 - Emergency Maintenance Guide
plug/unplug the board again.
4. If above steps can not solve the fault, reset the board. First
try to reset remotely from ISMG. If the problem continues,
you can reset it by manually.
5. Replace CMP board.
Board Alarm out of Active/Standby Mode
The following alarms are found in real-time alarm for OMP active
board.
198066003 Abnormal communication at control plane
between board and its module
database
1. View rack board indicators at BSC side to check whether red
alarm indicator is on and the fault exists on the board.
plug it properly again.
4. Reset the board. First try to reset remotely from ISMG. If the
problem continues, you can reset it by manually.
5. Replace this board.
Clock Alarms
The following alarms are found in real-time alarm.
198005381 Abnormal access clock
198005646 Phase-locked loop out of lock
198026129 Level 1 alarm on lost clock reference source
Post inspection
Symptoms
Steps
Post inspection
Symptoms


1. Check whether CLKG board is running normally. Board Alarm
shows the steps of inspection and troubleshooting.
2. Check whether SDTB, DTB, or SPB board to get clock at
interface A is normal. Board Alarm shows the steps of
inspection and troubleshooting.
3. Check whether cable connection from A-interface board to
CLKG 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.
4. 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.
5. Switchover CLKG board.
Alarms Related with Interface A
198066010 Alarm on unreachable MTP3 office
198066005 SCCP Subsystem Unavailable
1. Check E1 alarm at interface A to view whether all PCMs are
interrupted at this interface.
2. Check whether the clock state at BSC side is exceptional. If
yes, refer to troubleshooting steps in Clock Alarms.
3. Check whether global data at BSC and CN sides is changed.
If yes, you shall restore the data prior to changing.
4. Gradually switchover PSN, GLI, UIMU, UIMC, and CLKG
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.
Through dynamic data observation at interface A, test
whether all signals, trunks, signaling trace analysis and
service test at interface A are normal.
Steps
Post inspection
Symptoms
Steps
Post inspection

Alarms on Flow Control
MSC Overload
198087344 Overload of MSC FUC control mode
198087347 Alarm on system message method during MSC
overload
1. Inform MSC engineer to check whether MSC is overloaded
and sends corresponding overload message to BSC side.
2. Check whether FUC bitmap at BSC side is configured
properly. If not, FUC flow control will not work.
3. Check whether SIM card for field mobile phones are classified
according to specified requirements. If no classification, this
kind of flow control hasn't any influence on user service.
4. Contact local ZTE office or customer service support center.
Transmission is restored through testing.
Congestion at Signaling Point
198087349 Alarm on system message method during SP
congestion.
198087346 Alarm on FUC control method during SP
congestion.
1. Notify MSC engineers of checking whether no.7 signaling link
is overloaded.
2. Query whether TCH traffic and the number of TCH request in
KPI indices are greatly increased. If it is greatly increased,
you can confirm SP congestion is caused by higher traffic.
3. Check whether all no.7 signals are normal at this link, or any
interruption or flash symptom exist.
Symptoms
Steps
Post inspection
Symptoms
Steps
Post inspection


Too High CPU Load
198087348 Alarm on system message control mode due to
higher CPU load.
198087345 Alarm on FUC control mode due to higher CPU
load.
1. Query whether TCH traffic and the number of TCH request in
KPI indices are greatly increased. If it is greatly increased,
you can confirm SP congestion is caused by higher traffic.
2. Block some cells by using ISMG tools.
The alarm is removed after checking on ISMG system. If the
cell is blocked previously, you shall unblock the cell.
ISMG Faults
Can Not Log in ISMG system
To login from the client to the ISMG server fails.
1. Check whether the client communicates normally with the
server.
2. Check whether the disk is full at client.
3. Is client attacked by virus? Check whether operating system
is normally running.
4. Check whether the disk is full at server.
5. Check whether the ISMG process is normal.
6. Check whether the database is running normally.
7. Restart the server.
Symptoms
Steps
Post inspection
Symptoms
Steps

Successfully log in client and you can use it normally.
Disconnection between Equipment and ISMG
Server
In configuration management, it is found the link between
equipment and ISMG is disconnected, and configuration data can
not be distributed normally.
1. Check whether IP network from OMP to HUB is normal.
Check the network cable from OMP to HUB.
Check configuration of OMP IP address in ISMG server data.
2. Check whether the MP is running normally. If no, refer to
troubleshooting steps in Board Alarm.
3. Restart the ISMG server.
CS Service Faults
Mass Users Can Not Call Normally
Mass users can not call normally
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 Not Call
Normally, All Sites under Certain Module in BSC Can Not Call
Normally, All Sites under Certain Resource Shelf Can Not Call
Normally, All Sites under Certain BIPB Can Not Call Normally, All
Sites under Certain LAPD Can Not Call Normally, and Mass Users
Belonging To Other Type Can Not Call Normally.
The result is normal during calling test.
KPI index restores the level prior to the fault.
Post inspection
Symptoms
Steps
Post inspection
Symptoms
Steps
Post inspection


All Sites under BSC Can Not Call
Normally
All sites under BSC can not call normally.
1. Check whether the link at interface A is disconnected and
global alarm issues. If it is disconnected at interface A, refer
to troubleshooting steps in Alarms Related with Interface A.
2. Check whether clock alarm exists by viewing global alarms.
If yes, refer to troubleshooting steps in Clock Alarms.
3. Check whether the active/standby boards for switching shelf,
such as GLI, PSN, or UIMC, or control shelf, such as OMP and
CMP can not work normally. If yes, refer to troubleshooting
steps in Board Alarm.
4. Switchover OMP board.
You can call normally at all sites under BSC.
All Sites under Certain Module in
BSC Can Not Call Normally
All sites under certain module in BSC can not call normally.
1. View CMP alarm on this module to check whether the board
or certain CPU on it can not normally function. If yes, refer to
2. View whether flow control alarm occurs due to CPU overload
on this module. If yes, refer to troubleshooting steps in
Alarms on Flow Control.
3. Switchover the CMP module.
4. Reset the CMP module.
You can call normally at all sites under this module in BSC.
Symptoms
Steps
Post inspection
Symptoms
Steps
Post inspection

All Sites under Certain Resource
Shelf Can Not Call Normally
Many users complain all sites under certain resource shelf can
not call normally.
1. Check the UMIU alarm of this shelf to view whether the
board can not work normally. If yes, refer to troubleshooting
2. Check whether Ethernet cable from UIMU to CHUB is
normally connected.
3. Check whether clock cable from UIMU to CLKG is normally
connected.
4. Switchover this UIMU board.
5. Reset this UIMU board.
You can call normally at all sites under this resource shelf.
All Sites under Certain BIPB Can Not
Call Normally
All sites under certain BIPB can not call normally.
1. Check the BIPB alarm to view whether the board can not
work normally. If yes, refer to troubleshooting steps in Board
Alarm.
2. Reset this BIPB board.
You can call normally at all sites under this BIPB.
All Sites under Certain LAPD Can
Not Call Normally
All sites under certain LAPD can not call normally.
Symptoms
Steps
Post inspection
Symptoms
Steps
Post inspection
Symptoms


1. Check the LAPD alarm to view whether the board can not
Alarm.
2. Reset this LAPD board from equipment.
You can call normally at all sites under LAPD.
Mass Users Belonging To Other
Type Can Not Call Normally
Mass users belonging to other type can not call normally.
1. Check whether data is changed at BSN or CN side. If yes,
you shall restore original backup data.
2. 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.
3. Analyze SDCCH assignment failure rate, TCH allocation
failure rate, TCH assignment failure rate, SDCCH congestion
rate, and TCH congestion rate in KPI indices, to determine
which phase the fault occurs.
User can call normally.
PS Service Faults
Mass Users Can Not Use GPRS
Service
Lots of users can not use GPRS service
Based on quantity and domain of claiming users and in
combination with KPI analysis and test, you can determine the
Steps
Post inspection
Symptoms
Steps
Post inspection
Symptoms
Steps

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
Not Use GPRS Service and Some Cells Can Not Use GPRS
Service.
You can normally use GPRS service.
All Users under Whole BSC Can Not
Use GPRS Service
Lots of users under whole BSC can not use GPRS service
1. Check the DTB or GIPB alarm at interface Gb to view
whether the board can not work normally. If yes, refer to
2. Check the UPPB alarm to view whether the board can not
Alarm.
3. 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.
4. Reset GIPB or DTB board at interface Gb.
5. Reset UPPB board.
You can normally use GPRS service of this BSC.
Some Cells Can Not Use GPRS
Service
Lots of users in some cells can not use GPRS service
1. Check the UPPB alarm to view whether the board or certain
CPU can not work normally. If yes, refer to troubleshooting
2. In dynamic data management interface, view BVC state in
the cell and check whether BVC is blocked. If yes, unblock
the BVC.
3. Confirm whether lots of GRPS data are changed prior to the
fault. If yes, you shall restore the data firstly.
Post inspection
Symptoms
Steps
Post inspection
Symptoms
Steps


You can normally use GPRS service in this cell.

Post inspection

Ch a p t e r 4
Fault Feedback
Information

If the fault can not be solved individually, you shall find
assistance from ZTE. The feedback on field symptom and
relevant information data is the basis to analyze and locate the
fault. To quickly solve the troubleshooting process and prevent
repeated data feedback, this chapter introduces how to send
fault data feedback, which is favorable to locate and solve field
faults.
Prerequisite of Fault
Feedback
Prerequisite of fault feedback contains:
1. Fault time
2. Fault description
3. Detailed troubleshooting steps
4. System record
5. Fault feedback report
Presented below is a brief description of different elements.
Describes specific time of the fault, including start/end time of
the fault.
1. Describes the fault symptom, such as board state, dynamic
state, ISMG alarm, messages, and calling state. These are
the basis of field troubleshooting.
2. Describes the fault scope, such as whole BSC or site.
3. If you can not express it clearly, you shall copy the pictures.
For the channel state in dynamic management and error
Fault time
Fault
description


messages occurred during operation, you shall copy it in
picture mode.
1. Steps and time about field troubleshooting.
2. It includes the operation cases that may cause the fault.
3. 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.
It records system operation state and error messages, which is
the primary method to find system errors.
Table 7 shows fault feedback report.
TAB L E 7 - FI EL D FAUL T FEEDB ACK REPORT
Feedback by
Feedback
time

Received
by

Contact person Phone No.
Contact e-
mail

Source unit Model
Network
capacity
Version

Fault time,
symptom, and
description

Attached pages
Description of field
procedure and
handling

Attached pages
Field data
feedback

Attached pages

Attached pages
Analysis and
preliminary
comments
Handled
by
Day
Final comments
and conclusion

Troubleshootin
g steps
System record
Feedback
report

Chapter 4 - Fault Feedback Information
Feedback Data That Shall be
Recorded
For feedback data required by BSC faults, refer to Table 8.
TAB L E 8 - FEEDB ACK DATA REQUI RED B Y BSC FAUL TS
System feedback
records required
Purpose of
Record
The method to get
system record
Board indicator
conditions on fault
The indicators
contain the
elementary
information about
board operation.
Omitted
Printing file of the
equipment (including
active/standby MP for
central peripheral
modules): Exc_Omp.txt,
Exc_pp.txt
Record
exceptional cases
occurred during
BSC operation in
equipment
printings.
Refer to Get Device
Printing File
ZDB file in all active MP
for the equipment or
ZDB file for ISMG.
Configuration
information in
BSC, to learn
configuration
information.
Refer to Get ZDB File
ZTD backup files in
ISMG.
Configuration
information in
ISMG, to learn
configuration
information.
Refer to Get Data
Backup ztd File from
ISMG
Screenshot if board in-
stock version, general
software version, and
specified version
settings.
Software settings
about the board
Refer to Get Software
Setting
Alarm file, picking up
historical alarms within
a week and current
alarms.
Alarm file records
all alarms in the
system.
Refer to Get Alarm
File
Notification file, picking
up historical files within
a week.
Notification file is
the supplement
of system alarm.
Refer to Get
Notification File
Equipment and ISMG
version number.
Different version
has different
functions, so you
shall return
feedback.
Feedback shall be
sent based on the
version of field
records.
Performance report
within 1 hour before
and after the fault. Do
measurement according
You can find
system operation
state in
performance
Refer to Get 1 Hour's
Performance Data
Before and After Fault


System feedback
records required
Purpose of
Record
The method to get
system record
to cell level. statistics.
For the fault related
with interface A, you
shall send feedback
about signaling tracing
at interface A.
Signaling is a
very useful tool
to locate
questions.
Refer to Get Tracing
Signal 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.
State of the link
at interface A.
Refer to Query
Dynamic Data at
Interface A
with interface Abis, you
shall send feedback
about signaling tracing
at interface Abis.
Signaling is a
very useful tool
to locate
questions.
Refer to Get Tracing
Signal at Interface
Abis
If it involves calling
faults at site, you shall
return the feedback
information about
dynamic site state,
including cell, carrier,
and channel.
Channel state is
another path to
judge system
state.
Refer to Query
Dynamic Data at Site
If it involves calling
faults at site, you shall
return the feedback
information about
dynamic site state,
including cell, carrier,
and channel.
BVC and NSVC
states of the cell
is used to judge
system state.
Refer to Query BVC
and NSVC State
with PS service, you
shall send feedback
about signaling about
PS.
Signaling is a
very useful tool
to locate
questions.
Refer to Trace PS
Service Signal
Operation log of preset
machine
Operation
condition of
preset machine
Refer to Get
Operation Log of
Preset Machine
Check whether
Overstocked Data Exists
Analyze
incomplete data
Refer to Check
Whether Overstocked
Data Exists
For feedback data required by ISMG faults, refer to Table 9.
TAB L E 9 - FEEDB ACK DATA REQUI RED ON I SMG FAUL TS
System
feedback
records
required
Purpose of
Record
The method to get
system record

System
feedback
records
required
Purpose of
Record
The method to get
system record
Check the disk
space
Reflect the disk
condition
Refer to Query Disk Space
ISMG printing
file
Record the
operation conditions
of ISMG system.
Refer to Get ISMG Printing
File
ZTD backup
files in ISMG.
Configuration
information in
ISMG, to learn
configuration
information.
Refer to Get Data Backup
ztd File from ISMG
ISMG profile
Important
configuration in the
system.
Refer to Get ISMG Profile
Operation log at
client.
Record ISMG
operations on site.
Refer to Get Operation Log
at Client
System time
zone
For international
office, locate
specific time.
Refer to View System Time
Zone
NE version
Different version
supports different
functions.
Refer to View ISMG version
For feedback data required by site faults, refer to Table 10.
TAB L E 10 - FEEDB ACK DATA REQUI RED ON SI TE FAUL TS
System
feedback
records
required
Purpose of
Record
The method to get
system record
Identify site
name, number
and its model.
Identify the relation
between site name
and its number, so
you can find
corresponding site
in ZDB file.
Omitted
Dynamic
observation
condition,
including cell,
carrier, and
channel.
Channel state is
another path to
judge system state.
Refer to Query Dynamic
Data at Site
O&M signaling
trace
Reflect the
information while
the site is starting.
Refer to Get Tracing Signal
at Interface Abis
Signaling trace
at interface
Abis.
Record call cases in
the system.
Refer to Get Tracing Signal
at Interface Abis


System
feedback
records
required
Purpose of
Record
The method to get
system record
Historical alarm
file within a
week and
historical
notification file
within a week.
Record fault
information.
Refer to Get Alarm File and
Get Notification File.
Site version
Different version
supports different
functions.
Refer to Get BTS Software
Setting
ZDB file at
foreground.
Record and confirm
configuration
information at
foreground.
Refer to Get Equipment
ZDB File
Methods to Get System
Records
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:
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

Get ZDB File
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
6. get CfgTable.ZDB
7. get DBVer.ZDB
8. get VERTABLE.ZDB
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.


Get Data Backup ztd File from ISMG
1. Select View Configuration Management.
2. Select Data Management Data Backup, as shown in
Figure 6.
FI GURE 6 - SEL ECT DATA BACK UP

3. 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 7.
FI GURE 7 - DATA BACK UP WI NDOW

4. Use ftp tool with username/password as sysbak and port 21,
to download backed-up ztd file from ISMG server through ftp
mode.

Get Software Setting
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 8.
FI GURE 8 - SYNCHRONI ZE VERSI ON DATA FROM NE TO OMC

3. After the synchronization, snap three screenshots for version
file, common version, and special version of BSC. Save it as
jpg file and send feedback.
Get BTS Software Setting
BTS software setting can get Vertable.zdb equipment file for
feedback. For specific procedure, refer to Get Equipment ZDB
File.
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 9.


FI GURE 9 - SEL ECT VI EW HI STORY AL ARMS

2. Select Quick Query in History Alarm Query Conditions,
as shown in Figure 10.
FI GURE 10 - SEL ECT QUI CK SEARCH

3. Select System Type in Query History Alarm, and select all
alarm types in System Type, as shown in Figure 11.

FI GURE 11 - QUERY HI STORY AL ARM WI NDOW

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 12.


FI GURE 12 - SET QUERY TI ME OF AL ARM

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 13.
FI GURE 13 - AL ARM SAVE WI NDOW

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 14.
FI GURE 14 - SEL ECT VI EW NOTI FI CATI ONS]

2. Select Quick Query in Notification Query Conditions, as
shown in Figure 15.
FI GURE 15 - SEL ECT QUI CK SEARCH

3. Select System Type in Query Notification, and select all
notification types in System Type, as shown in Figure 16.


FI GURE 16 - QUERY NOTI FI CATI ON WI NDOW

4. Select start/end time in Happen Time, as shown in Figure
17.

FI GURE 17 - SET QUERY TI ME OF NOTI FI CATI ON

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 18.
FI GURE 18 - NOTI FI CATI ON SAVE WI NDOW


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 19.
FI GURE 19 - SEL ECT PERFORMANCE MANAGEMENT PERFORMANCE DATA
QUERY

2. In Query Index tab of Query, select object type as
CellFunction Type, and select KPI Index and PI Index,

FI GURE 20 - QUERY I NTERFACE

3. Select user-defined in Query Time tab, query granularity is
Original Granularity Data (15 minutes), as shown in Figure
21.
FI GURE 21 - SET QUERY TI ME OF PERFORMANCE DATA

4. 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 22.


FI GURE 22 - SET QUERY OB J ECT 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 23.
FI GURE 23 - SEL ECT CSBASI CMEASUREMENT

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 24.
FI GURE 24 - PARAMETER SET I NTERFACE

3. Configure in Trace Set interface, select the BSC to be traced,
and click Update Config button, as shown in Figure 25.


FI GURE 25 - TRACE SET I NTERFACE

4. After successfully updating configuration, select SCCP. In
SCCP option, select Module No., and select BSN No. as 254,
FI GURE 26 - SEL ECT SCCP

5. After stopping trace, select File Save all as .tra. Save all
signaling trace results as tra format, as shown in Figure 27.

FI GURE 27 - SAVE SI GNAL I NG TRACE RESUL T

6. 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 28.
FI GURE 28 - SI GNAL I NG TRA CE SAVE WI NDOW

Note:
Trace at interface A has great influence on system load. Each
trace can not exceed 5 minutes.
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 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.
Get Tracing Signal at Interface Abis
1. Configure server procedure for signaling trace, start server
program, start and logon signaling trace client.
Note:
button, as shown in Figure 29.
FI GURE 29 - PARAMETER SET I NTERFACE AT AB I S

and click Update 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 30 and Figure 31.
FI GURE 30 - CS I NTERFACE

FI GURE 31 - OAM I NTERFA CE

5. After tracing, the traced signal can be saved.
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
11.
TAB L E 11 - DYNAMI C DATA MANAGEMENT FUNCTI ON
Category 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
Radio Resources
Management
Cell channel
management
Query channel
statistics of a cell
Timeslot
management at Abis
Query timeslot state
measurement of
resource pool at Abis
Timeslot resource
management at Abis
Query timeslot state
of resource pool at
Abis
BTS equipment
management
operation
LAPD state
management
Query LAPD link
state at site
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 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.
Trace PS Service Signal
1. Configure server procedure for signaling trace, start server
program, start and logon signaling trace client.
Note:
button.
and click Update 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,


FI GURE 32 - TRACE SETTI NG OF PS SERVI CE SI GNAL

6. 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.
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.
Check Whether Overstocked Data
Exists
1. Check whether data is overstocked in
$OMCHOME/gsmomcr/ibsc/zxgomcr-emf-pm.par/x-y/err. x-y
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.
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.
Query Disk Space
1. Use command df k and vmstat to query current disk space.
2. Use NETTERM to save operation procedure.
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
/export/home/iomcr/iOMCR6.00.02f/ums-svr/log


1 Use ftp tool, such as cuteftp, to get log file within OMCR
fault period.
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
Get Operation Log at Client
1. Start Log Management at client, access to Operation Log
interface, select Query Operation Log, as shown in Figure
33.

FI GURE 33 - SEL ECT QUERY OPERATI ON L OG

2 In Query Operation Log window, customize operation
time period to query, or query all operation logs, and click OK,
FI GURE 34 - QUERY OPERA TI ON L OG WI NDOW


2. After successfully querying, export the log to excel.
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.
View ISMG version
On client interface of ISMG system, click Help About, and
display ISMG version information.

A p p e n d i x A
List of Emergency
Maintenance Records
Feedback by
Feedback
time

Received
by

Contact person Phone No.
Contact e-
mail

Source unit Model
Network
capacity
Version

Fault time,
symptom, and
description

Attached pages
Description of field
procedure and
handling

Attached pages
Field data
feedback

Attached pages

Attached pages
Analysis and
preliminary
comments
Handled
by
Day
Final comments
and conclusion



A p p e n d i x B
Abbreviations

Abbreviation Full Spelling Name
B
BSC Base Station Controller
BTS Base Transceiver Station
C
CPU Central Processing Unit
CLKG Clock Generator
D
DRTB Dual Rate Transcoder Board
DTB Digital Trunk Board
F
FAQ Frequently Asked Questions
G
GLI Gigabit Line Interface
GIPB Gb Interface Processing board
H
HW High Way line
I
IP Internet Protocol
ISMG Infrastructure Server for O&M for GSM
L
LAPD Link Access Protocol of D-Channel
O
OMP Opepercentagen Main Processor
S
SMTP Simple Message Transfer Protocol
SPB Signaling Processing Board


Abbreviation Full Spelling Name
T
TMN Telecommunication Management Network
U
UIMC
Universal Interface Module for Control plane (BCTC
or BPSN)
UIMU Universal Interface Module for User plane
UPPB User Plane Processing Board

A p p e n d i x C
Figures

Figure 1 - Flow of Emergency Maintenance.............................5
Figure 2 - Table Collection ................................................. 10
Figure 3 - Create Table Collection ....................................... 10
Figure 4 - Create Table Collection 1..................................... 11
Figure 5 - Create Table Collection 2..................................... 12
Figure 6 - Select Data Backup ............................................ 34
Figure 7 - Data Backup Window.......................................... 34
Figure 8 - Synchronize Version Data from NE to OMC ............ 35
Figure 9 - Select View History Alarms.................................. 36
Figure 10 - Select Quick Search.......................................... 36
Figure 11 - Query History Alarm Window ............................. 37
Figure 12 - Set Query Time of Alarm................................... 38
Figure 13 - Alarm Save Window.......................................... 38
Figure 14 - Select View Notifications] .................................. 39
Figure 15 - Select Quick Search.......................................... 39
Figure 16 - Query Notification Window................................. 40
Figure 17 - Set Query Time of Notification............................ 41
Figure 18 - Notification Save Window .................................. 41
Figure 19 - Select Performance Management Performance
Data Query...................................................................... 42
Figure 20 - Query Interface................................................ 43
Figure 21 - Set Query Time of Performance Data .................. 43
Figure 22 - Set Query Object of Performance Data ................ 44
Figure 23 - Select CSBasicMeasurement .............................. 44
Figure 24 - Parameter Set Interface .................................... 45
Figure 25 - Trace Set Interface........................................... 46
Figure 26 - Select SCCP..................................................... 46
Figure 27 - Save Signaling Trace Result ............................... 47


Figure 28 - Signaling Trace Save Window............................. 47
Figure 29 - Parameter Set Interface at Abis.......................... 48
Figure 30 - CS Interface.................................................... 49
Figure 31 - OAM Interface ................................................. 49
Figure 32 - Trace Setting of PS Service Signal ...................... 52
Figure 33 - Select Query Operation Log ............................... 55
Figure 34 - Query Operation Log Window............................. 55

Tables

Table 1 - Chapter Summary..................................................i
Table 2 - Typographical Conventions ..................................... ii
Table 3 - Mouse Operation Conventions ................................ iii
Table 4 - User complaint .....................................................1
Table 5 - Alarm report on emergency maintenance..................1
Table 6 - KPI indices ...........................................................2
Table 7 - Field Fault Feedback Report .................................. 28
Table 8 - Feedback data required by BSC faults .................... 29
Table 9 - Feedback data required on ISMG Faults.................. 30
Table 10 - Feedback data required on Site Faults .................. 31
Table 11 - Dynamic Data Management Function.................... 50

Sjzl20083719-ZXG10 iBSC (V6.10) Maintenance Manual (Emergency Maintenance)

Caricato da

Informazioni sul documento

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

Sjzl20083719-ZXG10 iBSC (V6.10) Maintenance Manual (Emergency Maintenance)

Caricato da

Copyright:

Formati disponibili

ZXG10 iBSC

Base Station Controller

Potrebbero piacerti anche