sjzl20083719-zxg10 ibsc (v6.10) maintenance manual (emergency maintenance)

8/13/2019 Sjzl20083719-ZXG10 iBSC (V6.10) Maintenance Manual (Emergency Maintenance)

1/75

ZXG10 iBSCBase Station Controller

Maintenance Manual(Emergency Maintenance)

Version 6.10

ZTE CORPORATIONZTE Plaza, Keji Road South,Hi-Tech Industrial Park,Nanshan District, Shenzhen,

P. R. China518057Tel: (86) 755 26771900 800-9830-9830Fax: (86) 755 26772236URL: http://support.zte.com.cn

E-mail: [email protected]
http://support.zte.com.cn/mailto:[email protected]:[email protected]://support.zte.com.cn/


2/75

LEGAL INFORMATION

Copyright 2006 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction ordistribution of this document or any portion of this document, in any form by any means, without the prior writtenconsent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected bycontractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTECORPORATION 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 theuse 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 ZTECORPORATION 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


3/75

ZTE CORPORATIONValues Your Comments & Suggestions!

Your opinion is of great value and will help us improve the quality of our productdocumentation and offer better services to our customers.

Please fax to (86) 755-26772236 or mail to Technical Delivery Department, ZTEUniversity, Dameisha, Yantian District, Shenzhen, Guangdong, P. R. China 518083.

Thank you for your cooperation!

DocumentName

ZXG10 iBSC (V6.10) Base Station Controller Maintenance Manual (Emergency Maintenance)

Product Version V6.10Document RevisionNumber

R1.0

Serial No. sjzl20083719Equipment

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 evaluationof thisdocumentation

Intelligibility:

(Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)


Yoursuggestions forimprovement ofthisdocumentation

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


4/75


5/75

Contents

About This Manual ............................................................iPurpose................................................................................ iIntended Audience................................................................. iPrerequisite Skill and Knowledge.............................................. iWhat Is in This Manual ........................................................... iRelated Documentation.......................................................... iiConventions......................................................................... iiHow to Get in Touch............................................................. iii

Chapter 1..........................................................................1Overview of Emergency Maintenance.............................1

Scope of Emergency Maintenance......................................1Guide Concept of Emergency Maintenance..........................3Flow of Emergency Maintenance........................................3

Determine the Fault Scope .....................................................5Find Fault Reason and Record Exceptions .................................6Fault Analysis.......................................................................6Critical Solution ....................................................................6Restore Service ....................................................................7Observe Restored Services.....................................................7Feedback Information about Emergency Maintenance.................7Communication with Customer................................................7Precautions of Emergency Maintenance....................................8Contact Information of Technical Support from ZTE ...................8

Chapter 2..........................................................................9Preparation of Emergency Maintenance.........................9

Daily Preparation of Emergency Maintenance ......................9Data Backup and System Inspection........................................9Establish Remote Maintenance Station ................................... 13Preparation of Important Spare Parts..................................... 13


6/75

Holiday Preparation of Emergency Maintenance.................13Load Monitor ......................................................................13Load Reduction Measures .....................................................14

Chapter 3........................................................................15Emergency Maintenance Guide .....................................15

Maintenance Guide about Major Alarm .............................15Board Alarm.......................................................................15Clock Alarms ......................................................................17Alarms Related with Interface A ............................................18Alarms on Flow Control ........................................................19

Maintenance Guide about ISMG Faults .............................20Maintenance Guide about CS Service Faults ......................21

Mass Users Can Not Call Normally..........................................21All Sites under BSC Can Not Call Normally ..............................22All Sites under Certain Module in BSC Can Not Call Normally .....22All Sites under Certain Resource Shelf Can Not Call Normally.....23All Sites under Certain BIPB Can Not Call Normally...................23All Sites under Certain LAPD Can Not Call Normally ..................23Mass Users Belonging To Other Type Can Not Call Normally.......24

Maintenance Guide about PS Service Faults ......................24Mass Users Can Not Use GPRS Service ...................................24All Users under Whole BSC Can Not Use GPRS Service..............25Some Cells Can Not Use GPRS Service ...................................25

Chapter 4........................................................................27Fault Feedback Information ..........................................27

Prerequisite of Fault Feedback ........................................27Feedback Data That Shall be Recorded.............................29Methods to Get System Records......................................32

Get Device Printing File ........................................................32Get ZDB File.......................................................................33Get Data Backup ztd File from ISMG ......................................34Get Software Setting ...........................................................35Get Alarm File.....................................................................35Get Notification File .............................................................39Get 1 Hour's Performance Data Before and After Fault ..............42Get Tracing Signal at Interface A ...........................................45


7/75


8/75

This page is intentionally blank.


9/75

Confidential and Proprietary Information of ZTE CORPORATION i

About This Manual

Purpose

This manual introduces the definitions, formulas, and influencefactors of common KPI, and introduces the typical cases in KPIoptimization project.

Intended Audience

This document is intended for engineers and technicians whoperform operation activities on ZXG10 iBSC.

Prerequisite Skill and Knowledge

To use this document effectively, users should have a generalunderstanding of wireless telecommunications technology.

What Is in This Manual

This manual contains the following chapters:

TA B L E 1 - C H A P T E R SUM M ARY

Chapter Summary

Chapter 1, Introductionof KPI in CS Domain

Introduces descriptions, definitions,formulas, and units for several kinds ofKPI in CS domain.

Chapter 2, Introductionof KPI in PS Domain

Introduces description, definition, formula,and unit for several kinds of KPI in PSdomain.

Appendix A, ReferenceKPI

Lists some reference KPIs.

Appendix B,Abbreviation

Lists all abbreviations used in this manual.

Appendix C

Tables

Lists the tables in this manual.


10/75


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 DocumentationGuide

ZXG10 iBSC (V6.10) Base Station Controller Technical

Manual

ZXG10 iBSC (V6.10) Base Station Controller HardwareManual

ZXG10 iBSC (V6.10) Base Station Controller InstallationManual

ZXG10 iBSC (V6.10) Base Station Controller PerformanceCounters Manual Volume I

ZXG10 iBSC (V6.10) Base Station Controller Performance

Counters Manual Volume II

ZXG10 iBSC (V6.10) Base Station Controller MaintenanceManual (Troubleshooting)

ZXG10 iBSC (V6.10) Base Station Controller KPI ReferenceManual

ZXG10 iBSC (V6.10) Base Station Controller Maintenance

Manual (Routine Maintenance)

ZXG10 BSS (V6.10) Base Station Subsystem Alarm HandlingManual

ZXG10 BSS (V6.10) Base Station Subsystem Notification

Handling Manual

Conventions

ZTE documents employ the following typographical conventions.

TA B L E 2 - T Y P O G R A P H I C A L CO NVENT I O NS

Typeface Meaning

Italics References to other Manuals and documents.

Quotes Links on screens.

Bold Menus, menu options, function names, inputfields, radio button names, check boxes, drop-down lists, dialog box names, window names.

CAPS Keys on the keyboard and buttons on screens

TypographicalConventions


11/75

AboutThis Manual

Confidential and Proprietary Information of ZTE CORPORATION iii

Typeface Meaning

and company name.

Const ant wi dth Text that you type, program code, files and

directory names, and function names.

[ ] Optional parameters.

{ } Mandatory parameters.

| Select one of the parameters that are delimitedby it.

Note: Provides additional information about acertain topic.

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

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

TA B L E 3 - MO USE O P E R A T I O N C O NVENT I O NS

Typeface Meaning

Click Refers to clicking the primary mouse button (usuallythe 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 andmoving the mouse.

How to Get in Touch

The following sections provide information on how to obtainsupport for the documentation and the software.

If you have problems, questions, comments, or suggestionsregarding your product, contact us by e-mail [email protected]. You can also call our customer supportcenter at (86) 755 26771900 and (86) 800-9830-9830.

ZTE welcomes your comments and suggestions on the qualityand usefulness of this document. For further questions,comments, or suggestions on the documentation, you cancontact us by e-mail at [email protected]; or you can fax yourcomments and suggestions to (86) 755 26772236. You can alsobrowse our website at http://support.zte.com.cn, which containsvarious interesting subjects like documentation, knowledge base,

forum and service request.

MouseOperation

Conventions

CustomerSupport

DocumentationSupport


12/75


iv Confidential and Proprietary Information of ZTE CORPORATION

This page is intentionally blank.


13/75

Confidential and Proprietary Information of ZTE CORPORATION 1

C h a p t e r

1

Overview of EmergencyMaintenance

This chapter mainly introduces applicable scope, flow, guideline,and precautions about emergency maintenance.

Scope of EmergencyMaintenanceDuring system running, you can confirm whether emergency

maintenance shall be started through user complaint, alarminspection, and performance report analysis.

1. User complaint

Table 4shows user complaints about emergency maintenance.

TA B L E 4 - U S E R C O M P L A I N T

Complaint content Description

Lots of speech user cannot access;

Lots of MS can not beacted as called/caller;

Mass Users can not UseGPRS Service

After receiving user complaints,you shall further check alarm

information and KPImeasurement result, todetermine whether emergentfault occurs.

2. Alarm inspection

Table 5 shows the alarm report that shall be viewed onemergency maintenance.

TA B L E 5 - A L A R M R E P O R T O N E M E R G E N C Y M A I N T E N A N C E

Alarm Type Alarm Description


14/75


2 Confidential and Proprietary Information of ZTE CORPORATION

Alarm Type Alarm Description

Alarms on spare boards, such asOMP and CMP.

Active board alarm inactive/standby modeBoard Alarm

Board alarm out of non-active/standby mode

Abnormal access clock

Phase-locked loop out of lockClock Alarms

Level 1 alarm on lost clockreference source

Alarm on unreachable MTP3 officeAlarms Related with Interface A

SCCP Subsystem Unavailable

MSC Overload

Congestion at Signaling PointAlarms on flow control

Too High CPU Load

3. Analyzing a performance report

Normally, KPI index is not a direct condition to start emergencymaintenance. Table 6shows the important KPI indices that shallbe viewed and analyzed on emergency maintenance.

While KPI is changed exceptionally, you shall confirmwhether 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 asubsidiary analysis tool and troubleshooting method.

TA B L E 6 - K PI I ND I CES

Indicator Type Indicator Name

SDCCH Congestion rate

TCH Congestion rate

TCH trafficCongestion

TCH availability

TCH Assignment success rateChannel occupation

Call success rate

Changeover related Handover success rate (%)

Call drop TCH call drop rate


15/75

Chapter 1 - Overviewof Emergency Maintenance


Guide Concept of

Emergency MaintenanceEmergency maintenance is suitable for the faults that shall behandled and restored immediately and have great influence onservice. For more information on daily maintenance, see ZXG10iBSC (V6.10) Base Station Controller Maintenance Manual(Routine); for more information on normal troubleshooting, seeZXG10 iBSC (V6.10) Base Station Controller TroubleshootingManual.

Prior to maintenance, you shall fully consider and follow belowprinciples about emergency maintenance.

You shall firstly determine fault scope prior to maintenance,

to do troubleshooting from inner to outer or from entire tolocal.

During daily maintenance, the operator shall refer to ZXG10iBSC and relevant equipment data, along with historical faultanalysis and experience, and then you shall prepare foremergent schedule; the operator shall periodically organizerelevant managers and maintenance personnel for trainingand demonstration.

When system or equipment encounters emergent faults,maintenance personnel shall keep calm; then check BSChardware and transmission to determine whether the fault is

caused by BSC. If yes, you shall do troubleshootingaccording to emergent schedule or relevant process inreferential manual.

Relevant maintenance personnel shall learn more about thesystem in daily maintenance assignments, especially to befamiliar with common exceptional information about ISMGalarm and indicator conditions on BSC panel, and to mastercommon tools about data backup/restore.

Before, in the process of, or after emergency maintenance,maintenance personnel shall collect the alarm informationabout this fault, and send troubleshooting report, equipmentalarm file, and log file to ZTE office for analysis and locating,so ZTE can provide better after-sale service for the operator.

Flow of EmergencyMaintenanceEmergency maintenance contains the following several steps:

1. Determine the fault scope;

2. Locate fault reason and record exceptions;


16/75



3. Fault analysis;

4. Critical solution;

5. Restore service;

6. Observe restored services;

7. Feedback information about emergency maintenance;

8. Communication with customer.

Figure 1shows the flow of emergency maintenance.


17/75



F I G URE 1 - F L O W O F EM ERG ENCY MA I N TE NA NCE

Determine the Fault Scope

1. Service faults often begin with user claims, so you shallregister user number. Analyze the site for user based ondifferent tools at BSC and CN sides, to determine theinfluence scope of the fault.


18/75



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 BSCside, 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 sitescope about the fault.

Determine whether it is global fault based on affected site.

Determine whether it is associated with module and specialboard based on based on affected site.

3. Test arrangement.

If possible, arrange test at specific area, and provide moreaccurate information on emergency maintenance.

Find Fault Reason and RecordExceptions

Pick up relevant data about alarm, performance, and printing,and analyze obvious phenomenon about network fault. Observethe information of equipment operation, board indicator. Checkthe fault caused by BSS equipment or other reasons.

Fault Analysis

If locating fault is caused by BSS equipment, you shall analyzefield alarms, performance, signal, and printing log, and dotroubleshooting 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 technicalsupport 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


19/75



assists customer to solve problems through phone; if theproblem is too complicated, ZTE will directly appointtechnical support engineer to the field for troubleshooting.

3. Field Technical Support

Technical expert shall make emergency measures to restorenormal communication as soon as possible.

Restore Service

Find out fault reason and quickly restore normal service throughremote or field ZTE technical support. If you can not timely findthe reason, you shall restore system service as soon as possible.If necessary, you shall try to solve the problem through boardswitchover, resetting, and restarting.

Observe Restored Services

After the service is restored, you shall confirm whether normaloperation state has been restored. If necessary, you shallarrange some persons on duty within peak traffic period, toclosely monitor network operation. As such, if the problemoccurs again, you shall solve it as soon as possible.

Feedback Information aboutEmergency Maintenance

After the service is restored, you shall collect BSS networkstatistics report, operation log, and signaling tracing data, andsend troubleshooting results to local ZTE customer servicecenter.

Communication with Customer

For level 1 fault, based on feedback data on site, ZTE mobilecustomer service department will submit fault analysis report tolocal office, and local office will communicate with customerabout involved faults.


20/75



Precautions of EmergencyMaintenance

Precautions of emergency maintenance are as follows.

You shall quickly find the fault location during emergencymaintenance. Some restoration (such as board resetting)may have a great influence on system operation, so it shallbe performed by a experienced operator or under the guidefrom an operator with certain maintenance experience.

If the fault has a great influence on network operation, nomatter whether maintenance personnel can solve it or not,they shall immediately contact ZTE customer service centeror local ZTE office, so we can timely and quickly find the fault

location and solve it.

Contact Information of TechnicalSupport from ZTE

1. Telephone at global ZTE customer service center

Fixed phone: 8008301118.

Mobile phone: 4008301118.

2. Local ZTE office


21/75


C h a p t e r

2

Preparation of EmergencyMaintenance

This chapter comprises of preparations for daily and holidayemergency maintenance, mainly introduces the preparationcontent and process about emergency maintenance, forreference during troubleshooting by maintenance personnel.

Daily Preparation ofEmergency MaintenanceDaily preparation of emergency maintenance contains thefollowing 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, toenable the system restore normal service.

Maintenance personnel can find significant faults and potentialrisks through daily system inspection.

Data backup

Maintenance personnel shall backup daily data.


22/75



Log in the database in configuration management interface atISMG client. Configuration data can be manually or automaticallybacked-up.

Automatic Backup

1. Select Oracle node, click DatabaseServer Table

Collection, as shown in Figure 2.

F I G URE 2 - TA B L E C O L L E C T I O N

2. In Table Collection, right-click Table Collection and select

Create,as shown in Figure 3.

F I G URE 3 - CR E A T E TA B L E C O L L E C T I O N

Note:

Right-click Table Collection, select and click View in floating

menu, so you can view the content of the table collection.


23/75

Chapter 2 - Preparationof Emergency Maintenance


You can select not to create a new table collection, and directlyuse default table collection task "Table Backup".Right-click a table collection task, select and click "ManuallyExecute" in floating menu, a interface to manually execute table

collection task pops up, and you can manually execute tablecollection task according to tips.

3. Create Table Collection pops up, as shown in Figure 4.

F I G URE 4 - CR E A T E TA B L E CO L L E C T I O N 1

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


24/75



F I G URE 5 - CR E A T E TA B L E C O L L E C T I O N 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 RoutineMaintenance Manual, focusing on checking operation state atBSC and analyze performance indicator & historical alarms.

If major alarm exists while checking historical alarms (within 1week) and current alarms, you shall handle it immediately. If


25/75

Chapter 2 - Preparationof Emergency Maintenance


the alarms still continue, you shall contact local ZTE office orcustomer service center.

Establish Remote MaintenanceStation

To guarantee quickly locate and solve the faults under thesupport of ZTE technicians, PCAnyWhere or VPN remote accessshall be always kept normal on different fields. You can contactlocal ZTE office while commissioning remote access.

Preparation of Important Spare Parts

You shall prepare for sufficient spare parts for important boardson BSC, such as OMP, CMP, CLKG, CHUB, UIMC, UIMU, PSN, andGLI.

Holiday Preparation ofEmergency MaintenancePreparation 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. CMPload at BSC can not exceed 70%.

2. Focus on CPU load on each board within whole monitoringperiod. Referential threshold is 70%.

3. Do your best to reduce the action of signaling trace duringlarge traffic, to reduce the influence on MP load.

4. During large traffic, to reduce CPU load, you shall stop orclose probe software.

5. Monitor load value at no.7 signaling link at interface A onBSC, 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.


26/75



7. It is recommended to monitor load condition at CN side. Ifthe load at CN side is exceptional, you shall informmaintenance 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 classifiedaccording to specified requirements. If it is classified, youcan check whether system message about flow control atBSC 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 atservice timeslot. The one near or over upper limit shall beexpanded timely.

Temporarily modify two or more paging as one paging modefor 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 circuitsat interface A for this BSC, to reduce processing load at CNside.

Timely start flow control function at CN side, preventing fromtoo high load leading to equipment degradation.


27/75


C h a p t e r

3

Emergency MaintenanceGuide

This chapter mainly introduces the process and commonmethods about emergency maintenance for reference bymaintenance personnel.

Maintenance Guide aboutMajor Alarm

Board Alarm

Active Board Alarm in Active/Standby Mode

The following alarms are found in real-time alarm for activeboard.

198005379 Board offline or CPU in long-term resetting state

198005390 Wrong (CPU) sub-card position configured by

database

198066004 Communication blocked between module andOMP

1. View the working state of standby board. If the standbyboard is normal, active/standby switchover happens.

2. View board state after switchover, to check whether theboard is normal. If the alarm continues on the active boardafter switchover, go to step 3.

3. If the fault also exits on standby board, reset active/standbyboard at the same time.

Symptoms

Steps


28/75



4. Change board;

5. If the alarms still continue, you shall contact local ZTE officeor 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 OMPbackup board.


198005122 Communication link disconnected at controlplane 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 theboard is not at proper position, or wrongly inserted, you shallplug/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. Firsttry 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 whilethe service traffic is minimized, and check whether the board isnormal.

Alarms related with CMP standby board

The following alarms are found in real-time alarm for CMPbackup board.


198005390 Wrong (CPU) sub-card position configured bydatabase

198005122 Communication link disconnected at controlplane between active/standby boards

1. View rack board indicators at BSC side to check whether redalarm indicator, ALM, is on and the fault exists on ISMG.

Post inspection

Symptoms

Steps

Post inspection

Symptoms

Steps


29/75

Chapter 3 - EmergencyMaintenance Guide


2. Check whether the board is inserted in proper slot. If theboard is not at proper position, or wrongly inserted, you shallplug/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. Firsttry 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 activeboard.

198066003 Abnormal communication at control planebetween board and its module


198005390 Wrong (CPU) sub-card position configured bydatabase

1. View rack board indicators at BSC side to check whether red

alarm indicator is on and the fault exists on the board.

2. Check whether the board is inserted in proper slot. If theboard is not at proper position, or wrongly inserted, you shallplug it properly again.

3. Check whether micro switch (ENUM) of the board is opened.If ENUM switch is opened, you shall close it.

4. Reset the board. First try to reset remotely from ISMG. If theproblem continues, you can reset it by manually.

5. Replace this board.

6. If the alarms still continue, you shall contact local ZTE office

or customer service center.


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


30/75



1. Check whether CLKG board is running normally. Board Alarmshows the steps of inspection and troubleshooting.

2. Check whether SDTB, DTB, or SPB board to get clock atinterface A is normal. Board Alarm shows the steps of

inspection and troubleshooting.

3. Check whether cable connection from A-interface board toCLKG is normal. If the cable is loose or abnormal, you shallre-connect it or replace the clock cable from A-interfaceboard to CLKG.

4. Check whether STM-1 and E1 are normal on the board to getclock at interface A. Check whether trunk interruption, highBER, or slide code alarm exist, such as "SDH/SONET: signalmissing", "trunk signal missing". If yes, you shall contacttransmission 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 areinterrupted at this interface.

2. Check whether the clock state at BSC side is exceptional. Ifyes, 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 CLKGboards. You shall check whether the service is restored whileyou switchover each board. If the fault continues, you can

continue switchover the next board.



Through dynamic data observation at interface A, testwhether all signals, trunks, signaling trace analysis andservice test at interface A are normal.

Steps

Post inspection

Symptoms

Steps

Post inspection


31/75



Alarms on Flow Control

MSC Overload


198087344 Overload of MSC FUC control mode

198087347 Alarm on system message method during MSCoverload

1. Inform MSC engineer to check whether MSC is overloadedand sends corresponding overload message to BSC side.

2. Check whether FUC bitmap at BSC side is configuredproperly. If not, FUC flow control will not work.

3. Check whether SIM card for field mobile phones are classifiedaccording to specified requirements. If no classification, thiskind 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 SPcongestion.

198087346 Alarm on FUC control method during SPcongestion.

1. Notify MSC engineers of checking whether no.7 signaling linkis overloaded.

2. Query whether TCH traffic and the number of TCH request inKPI 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 anyinterruption or flash symptom exist.






Symptoms

Steps

Post inspection

Symptoms

Steps

Post inspection


32/75



Too High CPU Load


198087348 Alarm on system message control mode due tohigher CPU load.

198087345 Alarm on FUC control mode due to higher CPUload.

1. Query whether TCH traffic and the number of TCH request inKPI 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 thecell is blocked previously, you shall unblock the cell.


Maintenance Guide aboutISMG 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 theserver.

2. Check whether the disk is full at client.

3. Is client attacked by virus? Check whether operating systemis 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


33/75



Successfully log in client and you can use it normally.

Disconnection between Equipment and ISMG

Server

In configuration management, it is found the link betweenequipment and ISMG is disconnected, and configuration data cannot 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 totroubleshooting steps in Board Alarm.

3. Restart the ISMG server.



Maintenance Guide about

CS Service FaultsMass Users Can Not Call Normally

Mass users can not call normally

Based on quantity and domain of claiming users and incombination with KPI analysis and test, you can determine theinfluence 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 CallNormally, All Sites under Certain Module in BSC Can Not CallNormally, All Sites under Certain Resource Shelf Can Not CallNormally, All Sites under Certain BIPB Can Not Call Normally, AllSites under Certain LAPD Can Not Call Normally, and Mass UsersBelonging 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


34/75



All Sites under BSC Can Not CallNormally

All sites under BSC can not call normally.

1. Check whether the link at interface A is disconnected andglobal alarm issues. If it is disconnected at interface A, referto 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 andCMP can not work normally. If yes, refer to troubleshootingsteps 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 boardor certain CPU on it can not normally function. If yes, refer totroubleshooting steps in Board Alarm.

2. View whether flow control alarm occurs due to CPU overloadon this module. If yes, refer to troubleshooting steps inAlarms 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


35/75



All Sites under Certain ResourceShelf Can Not Call Normally

Many users complain all sites under certain resource shelf cannot call normally.

1. Check the UMIU alarm of this shelf to view whether theboard can not work normally. If yes, refer to troubleshootingsteps in Board Alarm.

2. Check whether Ethernet cable from UIMU to CHUB isnormally connected.

3. Check whether clock cable from UIMU to CLKG is normallyconnected.

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 NotCall Normally

All sites under certain BIPB can not call normally.

1. Check the BIPB alarm to view whether the board can notwork normally. If yes, refer to troubleshooting steps in BoardAlarm.

2. Reset this BIPB board.



You can call normally at all sites under this BIPB.


All Sites under Certain LAPD CanNot Call Normally

All sites under certain LAPD can not call normally.

Symptoms

Steps

Post inspection

Symptoms

Steps

Post inspection

Symptoms


36/75



1. Check the LAPD alarm to view whether the board can notwork normally. If yes, refer to troubleshooting steps in BoardAlarm.

2. Reset this LAPD board from equipment.



You can call normally at all sites under LAPD.


Mass Users Belonging To OtherType 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 toanalyze it. Determine it is caused by the problem at BSC orCN side based on signaling process.

3. Analyze SDCCH assignment failure rate, TCH allocationfailure rate, TCH assignment failure rate, SDCCH congestionrate, and TCH congestion rate in KPI indices, to determine

which phase the fault occurs.



User can call normally.


Maintenance Guide about

PS Service Faults

Mass Users Can Not Use GPRSService

Lots of users can not use GPRS service

Based on quantity and domain of claiming users and incombination with KPI analysis and test, you can determine the

Steps

Post inspection

Symptoms

Steps

Post inspection

Symptoms

Steps


37/75



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 CanNot Use GPRS Service and Some Cells Can Not Use GPRS

Service.

You can normally use GPRS service.


All Users under Whole BSC Can NotUse GPRS Service

Lots of users under whole BSC can not use GPRS service

1. Check the DTB or GIPB alarm at interface Gb to viewwhether the board can not work normally. If yes, refer totroubleshooting steps in Board Alarm.

2. Check the UPPB alarm to view whether the board can notwork normally. If yes, refer to troubleshooting steps in BoardAlarm.

3. View E1 alarm at interface Gb to check whether E1transmission is interrupted. If yes, check E1 cable, andinform 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 certainCPU can not work normally. If yes, refer to troubleshootingsteps in Board Alarm.

2. In dynamic data management interface, view BVC state inthe cell and check whether BVC is blocked. If yes, unblockthe 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


38/75





You can normally use GPRS service in this cell. KPI index restores the level prior to the fault.

Post inspection


39/75


C h a p t e r

4

Fault FeedbackInformation

If the fault can not be solved individually, you shall findassistance from ZTE. The feedback on field symptom andrelevant information data is the basis to analyze and locate thefault. To quickly solve the troubleshooting process and preventrepeated data feedback, this chapter introduces how to sendfault data feedback, which is favorable to locate and solve fieldfaults.

Prerequisite of FaultFeedbackPrerequisite 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 ofthe fault.

1. Describes the fault symptom, such as board state, dynamicstate, ISMG alarm, messages, and calling state. These arethe 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

Faultdescription


40/75



messages occurred during operation, you shall copy it inpicture 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 providea convenience to check whether there is any operation error.For the operations on the server, you can use the recordfunction of NETTERM to remember the operation procedures.

It records system operation state and error messages, which isthe primary method to find system errors.

Table 7shows fault feedback report.

TA B L E 7 - F I E L D FA UL T FE E D B A C K R EPO RT

Feedback byFeedbacktime

Receivedby

Contact person Phone No.Contact e-mail

Source unit Model

Networkcapacity

Version

Fault time,symptom, anddescription

Attached pages

Description of fieldprocedure andhandling

Attached pages

Field datafeedback

Attached pages

Attached pages

Analysis andpreliminarycomments

Handledby

Day

Final comments

and conclusion

Troubleshootin

g steps

System record

Feedbackreport


41/75

Chapter 4 - FaultFeedback Information


Feedback Data That Shall be

RecordedFor feedback data required by BSC faults, refer to Table 8.TA B L E 8 - F E E D B A C K D A T A R E Q U I R E D B Y B SC F A U L T S

System feedbackrecords required

Purpose ofRecord

The method to getsystem record

Board indicatorconditions on fault

The indicatorscontain theelementaryinformation aboutboard operation.

Omitted

Printing file of theequipment (includingactive/standby MP forcentral peripheralmodules): Exc_Omp.txt,Exc_pp.txt

Recordexceptional casesoccurred duringBSC operation inequipmentprintings.

Refer to Get DevicePrinting File

ZDB file in all active MPfor the equipment orZDB file for ISMG.

Configurationinformation inBSC, to learnconfigurationinformation.

Refer to Get ZDB File

ZTD backup files inISMG.

Configuration

information inISMG, to learnconfigurationinformation.

Refer to Get DataBackup ztd File from

ISMG

Screenshot if board in-stock version, generalsoftware version, andspecified versionsettings.

Software settingsabout the board

Refer to Get SoftwareSetting

Alarm file, picking uphistorical alarms withina week and currentalarms.

Alarm file recordsall alarms in thesystem.

Refer to Get AlarmFile

Notification file, pickingup historical files withina week.

Notification file isthe supplementof system alarm.

Refer to GetNotification File

Equipment and ISMGversion number.

Different versionhas differentfunctions, so you

shall returnfeedback.

Feedback shall besent based on theversion of fieldrecords.

Performance reportwithin 1 hour beforeand after the fault. Do

measurement according

You can findsystem operationstate in

performance

Refer to Get 1 Hour'sPerformance DataBefore and After Fault


42/75



System feedbackrecords required

Purpose ofRecord


to cell level. statistics.

For the fault relatedwith interface A, youshall send feedbackabout signaling tracingat interface A.

Signaling is avery useful toolto locatequestions.

Refer to Get TracingSignal at Interface A

If the problem is relatedwith interface A orwhole BSC, you shallsend feedback about

dynamic state of thelink at interface A.

State of the linkat interface A.

Refer to QueryDynamic Data atInterface A

For the fault relatedwith interface Abis, you

shall send feedbackabout signaling tracingat interface Abis.


Refer to Get Tracing

Signal at InterfaceAbis

If it involves callingfaults at site, you shallreturn the feedbackinformation aboutdynamic site state,including cell, carrier,and channel.

Channel state isanother path tojudge systemstate.

Refer to QueryDynamic Data at Site

If it involves callingfaults at site, you shall

return the feedbackinformation aboutdynamic site state,including cell, carrier,and channel.

BVC and NSVC

states of the cellis used to judgesystem state.

Refer to Query BVCand NSVC State

For the fault relatedwith PS service, youshall send feedbackabout signaling aboutPS.


Refer to Trace PSService Signal

Operation log of presetmachine

Operationcondition ofpreset machine

Refer to GetOperation Log ofPreset Machine

Check whetherOverstocked Data Exists

Analyzeincomplete data

Refer to Check

Whether OverstockedData Exists

For feedback data required by ISMG faults, refer to Table 9.

TA B L E 9 - F E E D B A C K D A T A R E Q U I R E D ON ISM G FA UL T S

Systemfeedbackrecordsrequired

Purpose ofRecord



43/75




Purpose ofRecord


Check the diskspace

Reflect the diskcondition

Refer to Query Disk Space

ISMG printingfile

Record theoperation conditionsof ISMG system.

Refer to Get ISMG PrintingFile

ZTD backupfiles in ISMG.

Configurationinformation inISMG, to learnconfigurationinformation.

Refer to Get Data Backupztd File from ISMG

ISMG profileImportantconfiguration in the

system.

Refer to Get ISMG Profile

Operation log atclient.

Record ISMGoperations on site.

Refer to Get Operation Logat Client

System timezone

For internationaloffice, locatespecific time.

Refer to View System TimeZone

NE versionDifferent versionsupports differentfunctions.

Refer to View ISMG version

For feedback data required by site faults, refer to Table 10.

TA B L E 10 - FE E D B A C K D A T A R E Q U I R E D O N S I T E FA U L T S


Purpose ofRecord


Identify sitename, number

and its model.

Identify the relationbetween site name

and its number, soyou can findcorresponding sitein ZDB file.

Omitted

Dynamicobservationcondition,including cell,carrier, and

channel.

Channel state isanother path tojudge system state.

Refer to Query DynamicData at Site

O&M signalingtrace

Reflect theinformation whilethe site is starting.

Refer to Get Tracing Signalat Interface Abis

Signaling traceat interfaceAbis.

Record call cases inthe system.

Refer to Get Tracing Signalat Interface Abis


44/75




Purpose ofRecord


Historical alarmfile within aweek andhistoricalnotification filewithin a week.

Record faultinformation.

Refer to Get Alarm FileandGet Notification File.

Site versionDifferent versionsupports differentfunctions.

Refer to Get BTS SoftwareSetting

ZDB file atforeground.

Record and confirmconfigurationinformation at

foreground.

Refer to Get EquipmentZDB File

Methods to Get SystemRecords

Get Device Printing File

1. Create a directory to save files on server.

2. Execute the ftp command at ISMG to connect OMP. Both theuser 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 andExc_pp.txt file.

5. Download the file to server, then use ftp tool (such asCUTEFTP) 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


45/75



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 properdirectory for each module on each BSC, to transfer the ZDB filesinto proper directory.

1. Create a directory to save files on server.

2. Execute the ftp command at ISMG to connect OMP. Both theuser 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 ftptool, such as CUTEFTP, to upload the files to client andcompress it.

Example:

1. cd $OMCHOME

2. mkdir bsc1

3. cd bsc14. 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 (XXindicates BSCID). Each time you perform whole tablesynchronization or incremental synchronization, it may generatenew CFGTABLE.ZDB, VERTABLE.ZDB, and DBVER.ZDB files, andadd generation time postfix for the file generated at last time forbackup.

Generated file is too small during incremental synchronization.You can use ls l command to view the file size. If current ZDBfile belongs to the one generated on incremental synchronization,you can do a synchronization action on whole table on ISMGclient, this will generate new complete ZDB file.

Use ftp tool, such as CUTEFTP, to transfer ZDB file to client.


46/75



Get Data Backup ztd File from ISMG

1. Select View Configuration Management.

2. Select Data Management Data Backup, as shown in

Figure 6.

F I G URE 6 - SE L E C T DA T A BA C K UP

3. In Data Backup window, select storage path/CM (onlybackuped in the server), input filename prefix and backupdescription, and select the NE to be backuped. Afteracknowledgement, click OKbutton, as shown in Figure 7.

F I G URE 7 - DA T A BA CK UP W I NDO W

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

mode.


47/75



Get Software Setting

Get BSC Software Setting

1. Start Software Version Management at client, and click BSCSoftware Version Management after selecting BSC NE onConfiguration Resource Tree.

2. For setting of software version, equipment data may beinconsistent with ISMG data, so if you can not determinewhether it is consistent, you shall do the action of"synchronize version data from NE to OMC". Synchronizationoperation may remove ISMG software setting, operate thedata based on actual equipment condition, and re-establishISMG software settings, as shown in Figure 8.

F I G URE 8 - SYNCHRO NI Z E VERSI O N DA T A F RO M NE T O OMC

3. After the synchronization, snap three screenshots for versionfile, 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 forfeedback. For specific procedure, refer to Get Equipment ZDBFile.

Get Alarm File

1. Start Alarm Management at client. Select View HistoryAlarms in Query menu option of Alarm Managementinterface, as shown in Figure 9.


48/75



F I G URE 9 - SE L E C T V I EW H I ST O RY A L A R M S

2. Select Quick Query in History Alarm Query Conditions,as shown in Figure 10.

F I G URE 10 - SE L E C T QU I C K SE A R C H

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


49/75



F I G URE 11 - Q UERY H I ST O RY A L A R M W I NDO W

4. Select a relative time in Happen Time. The date shall be aday within a recent week or a customized day, as shown inFigure 12.


50/75



F I G URE 12 - SET Q UERY T I M E O F A L A R M

5. Click OKto output alarm data.

6. Click Exportbutton to export queried alarms.

7. In Savewindow, select the proper path and click Save, asshown in Figure 13.

F I G URE 13 - A L A R M SA VE W I NDO W


51/75



Get Notification File

1. Start Alarm Management at client. Select View

Notifications] in View Alarm menu option of AlarmManagementinterface, as shown in Figure 14.

F I G URE 14 - SE L E C T V I EW NO T I F I CAT I O NS ]

2. Select Quick Queryin Notification Query Conditions, asshown in Figure 15.

F I G URE 15 - SE L E C T QU I C K SE A R C H

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


52/75



F I G URE 16 - Q UERY N O T I F I CAT I O N W I NDO W

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


53/75



F I G URE 17 - SET Q UERY T I M E O F NO T I F I CAT I O N

5. Click OKto output notification data.

6. Click Exportbutton to export queried notifications.

7. In Savewindow, select the proper path and click Save, asshown in Figure 18.

F I G URE 18 - NO T I F I CAT I O N SA VE W I NDO W


54/75



Get 1 Hour's Performance DataBefore and After Fault

1. Start Performance Management at client, and selectPerformance ManagementPerformance Data Query

in the menu, as shown in Figure 19.

F I G URE 19 - SE L E C T PERF O RM ANCE MA N A G E M EN T PERF O RM ANCE DA T A

Q UERY

2. In Query Index tab of Query, select object type asCellFunction Type, and select KPI Index and PI Index,as shown in Figure 20.


55/75



F I G URE 20 - Q UERY I NT ERF ACE

3. Select user-defined in Query Timetab, query granularity isOriginal Granularity Data (15 minutes), as shown in Figure21.

F I G URE 21 - SET Q UERY T I M E O F PERF O RM ANCE DA T A

4. In Query Objecttab, select the NE to be queried, select thecell that shall be queried in measurement objects, summarymode is None, as shown in Figure 22.


56/75



F I G URE 22 - SET Q UERY OB J E C T O F PERF O RM ANCE DA T A

5. Queried data shall be exported as EXCEL report.

6. Repeat above steps, query CSBasicMeasurement and exportit as EXCEL report, as shown in Figure 23.

F I G URE 23 - SE L E C T CSBA S I CME A S U R E M E N T


57/75



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 isconfigured at server side, and server.exe program is running;clientcfg.xml file is configured.

2. Select ToolsParameter Set, and access to Parameter

Setinterface to configure signaling trace. In Record Settab,configure Items Showed in the Trace Windowas 20000.

Select File Divide 5000 items in one file. Click Savebutton, as shown in Figure 24.

F I G URE 24 - PA R A M ET ER SET I NT ERF ACE

3. Configure in Trace Setinterface, select the BSC to be traced,

and click Update Configbutton, as shown in Figure 25.


58/75



F I G URE 25 - TR A C E SET I NT ERF ACE

4. After successfully updating configuration, select SCCP. InSCCP option, select Module No., and select BSN No. as 254,as shown in Figure 26.

F I G URE 26 - SE L E C T SCCP

5. After stopping trace, select FileSave all as .tra. Save all

signaling trace results as tra format, as shown in Figure 27.


59/75



F I G URE 27 - SA V E S I G N A L I N G TR A C E RE S U L T

6. Select the path to save in Save window, saved filescontain .tra and .idx files. If feedback, you shall send theboth files, as shown in Figure 28.

F I G URE 28 - S I G N A L I N G T R A C E SA V E W I NDO W

Note:Trace at interface A has great influence on system load. Eachtrace 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 Managementinterface. Select and expand proper BSC managed elements,


60/75



access to BSC Dynamic Data Management interface, andyou can manage PCM at interface A and trunk at interface A.

2. In A-Interface PCMtab, click Querybutton to query PCMstate; in A-Interface Trunk Circuit Management tab,

click All Queriesbutton, or select some circuits, click QueryTimeslot Circuit Statebutton to query the state of timeslot.

Get Tracing Signal at Interface Abis

1. Configure server procedure for signaling trace, start serverprogram, start and logon signaling trace client.

Note:

Signaling trace tool shall use server/client architecture.Requirement of using signaling trace tool: servercfg.xml file isconfigured at server side, and server.exe program is running;clientcfg.xml file is configured.


Setinterface to configure signaling trace. In Record Settab,configure Items Showed in the Trace Windowas 20000.Select File Divide 5000 items in one file. Click Savebutton, as shown in Figure 29.

F I G URE 29 - PA R A M ET ER SET I N T E R F A C E A T A B I S

3. Configure in Trace Setinterface, select the BSC to be traced,and click Update Configbutton.

4. After successfully updating configuration, select CS and OAM,select the site to be traced in CS and OAM interfaces. Select


61/75



all trace items in Trace Itemof CS, select a site in OAM, asshown in Figure 30and Figure 31.

F I G URE 30 - CS INT ERF ACE

F I G URE 31 - O A M I NT ERF ACE

5. After tracing, the traced signal can be saved.

Query Dynamic Data at Site

1. Click View->Dynamic Data Management to enter thedynamic data management interface.


62/75



2. In configuration resource tree, select and expand BSCmanagement elements node.

3. Double-click corresponding dynamic data management nodeat site, enter into Dynamic Data Managementinterface, so

you can do radio resource management and site equipmentmanagement operation.

For dynamic data management functions at site, refer to Table11.

TA B L E 11 - DY N A M I C DA T A MA N A G EM ENT F UNCT I O N

Category Function Description

Cell managementQuery the status ofcell

TRX management

Query the state of

TRX

ChannelManagement

Query channel state

Module ManagementQuery channelstatistics on amodule

BVC ManagementQuery the BVC statusof cell

Radio ResourcesManagement

Cell channelmanagement

Query channelstatistics of a cell

Timeslotmanagement at Abis

Query timeslot statemeasurement ofresource pool at Abis

Timeslot resourcemanagement at Abis

Query timeslot stateof resource pool atAbis

BTS equipmentmanagementoperation

LAPD statemanagement

Query LAPD linkstate at site

Query BVC and NSVC State

1. Click View->Dynamic Data Management to enter thedynamic data management interface.

2. In configuration resource tree, select and expandmanagement elements node to be queried.

3. Double-click corresponding dynamic data management node,enter into Dynamic Data Managementinterface.

4. In NSVC Management of Dynamic Data Managementinterface, you can query NSVC state.

5. In configuration resource tree, double-click corresponding

dynamic data management node under management NE


63/75



node to be queried, enter into dynamic data managementinterface.

6. In Radio Resource Management tab of Dynamic DataManagementinterface, select BVC Management to query

NSVC state.

Trace PS Service Signal

1. Configure server procedure for signaling trace, start serverprogram, start and logon signaling trace client.

Note:

Signaling trace tool shall use server/client architecture.

Requirement of using signaling trace tool: servercfg.xml file isconfigured at server side, and server.exe program is running;clientcfg.xml file is configured.


Setinterface to configure signaling trace. In Record Settab,configure Items Showed in the Trace Windowas 20000.Select File Divide 5000 items in one file. Click Savebutton.

3. Configure in Trace Setinterface, select the BSC to be traced,and click Update Configbutton.

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 andBVCIO to be traced in BSSGP and LLC, NSVC link to betraced in NS, BRCH link to be traced in FR. Click OKbutton,as shown in Figure 32.


64/75



F I G URE 32 - TR A C E SET T I NG O F PS S ERVI CE S I G N A L

6. After stopping trace, select FileSave all as .tra. Save all

signaling trace result as tra format.

7. Select the path to save in Save window, saved filescontain .tra and .idx files. If feedback is required, you shallsend the both files.

Get Operation Log of PresetMachine

Operation log of preset machine is saved inX:\FTPRoot\nfsDev\iBSC\OMS\log. You can get it through ftptools. 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 DataExists

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

Data accumulation is caused by exceptional oracle, full tablespace in performance library and performance index. For


65/75



specific information, you can get error reasons from serverlog.

Solution is as follows:

Check the space size of performance table and indextable, if it is full, you can expand it based on server disk

space, or delete relevant performance data and re-createindex.

Exceptional operation modes of oracle are diversified, andit is complicated to solve it. It is recommended you shallreturn server log to ZTE for analysis. You can try torestart ORACLE on site.

2. Check whether data file is overstocked inX:FTPRoot\nfsDev\iBSC\OMCR of preset machine. Where, Xis the label of data file disk.

Check whether communication between ISMG server andpreset machine is normal and whether ftp service of presetmachine is normal. You can try to preset machine throughftp 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 intothis directory to get corresponding LOG file.

Example:

bash-3.00$ cd $OMCHOME/log

bash-3.00$ lsboot.log server-20080117-0623-28443.logserver-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


66/75



1 Use ftp tool, such as cuteftp, to get log file within OMCR

fault period.

Get ISMG ProfileISMG profile is saved in $OMCHOME/deploy. You can use ftptools, such as CUTEFTP, to download it to local client. Requiredprofile 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 Managementat client, access to Operation Loginterface, select Query Operation Log, as shown in Figure33.


67/75



F I G URE 33 - SE L E C T QU E R Y OP E R A T I O N L O G

2 In Query Operation Log window, customize operation

time period to query, or query all operation logs, and click OK,as shown in Figure 34.

F I G URE 34 - Q UERY O P E R A T I O N L O G W I NDO W


68/75



2. After successfully querying, export th

sjzl20083719-zxg10 ibsc (v6.10) maintenance manual (emergency maintenance)

Documents