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

ZXG10 iBSCBase Station Controller

Emergency Maintenance

Version: V6.20.71

ZTE CORPORATIONNO. 55, Hi-tech Road South, ShenZhen, P.R.ChinaPostcode: 518057Tel: +86-755-26771900Fax: +86-755-26770801URL: http://ensupport.zte.com.cnE-mail: [email protected]

LEGAL INFORMATIONCopyright 2011 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or

distribution of this document or any portion of this document, in any form by any means, without the prior written

consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by

contractual confidentiality obligations.

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE

CORPORATION or of their respective owners.

This document is provided as is, and all express, implied, or statutory warranties, representations or conditions

are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,

title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the

use of or reliance on the information contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications

covering the subject matter of this document. Except as expressly provided in any written license between ZTE

CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter

herein.

ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.

Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

R1.1 2011-09-30 Updated to V6.20.711C

R1.0 2011-07-14 First Edition

Serial Number: SJ-20110531095035-006

Publishing Date: 2011-09-30(R1.1)

ContentsAbout This Manual ......................................................................................... I

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

1.1 Scope of Emergency Maintenance ...................................................................... 1-1

1.2 Guide Concept of Emergency Maintenance ......................................................... 1-3

1.3 Flow of Emergency Maintenance......................................................................... 1-3

1.3.1 Determine the fault scope ......................................................................... 1-4

1.3.2 Locate fault reason and record exceptions ................................................. 1-5

1.3.3 Fault Analysis .......................................................................................... 1-5

1.3.4 Critical solution......................................................................................... 1-5

1.3.5 Restore service ........................................................................................ 1-6

1.3.6 Observe restored services ........................................................................ 1-6

1.3.7 Feedback information about emergency maintenance ................................ 1-6

1.3.8 Communication with customer .................................................................. 1-6

1.4 Precautions of Emergency Maintenance .............................................................. 1-6

1.5 Contact Information of Technical Support from ZTE .............................................. 1-6

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

2.1 Daily Preparation of Emergency Maintenance ...................................................... 2-1

2.1.1 Data Backup and System Inspection ......................................................... 2-1

2.1.2 Establish Remote Maintenance Station...................................................... 2-3

2.1.3 Preparation of important spare parts.......................................................... 2-3

2.2 Holiday Preparation of Emergency Maintenance .................................................. 2-3

2.2.1 Load Monitoring ....................................................................................... 2-3

2.2.2 Load reduction measures.......................................................................... 2-4

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

3.1 Maintenance Guide about Major Alarm ................................................................ 3-1

3.1.1 Board Alarm............................................................................................. 3-1

3.1.2 Clock alarm.............................................................................................. 3-3

3.1.3 Alarms related with interface A.................................................................. 3-4

3.1.4 Alarms on flow control .............................................................................. 3-5

3.1.5 Transmission alarms ................................................................................ 3-6

3.2 Maintenance Guide about NM Faults................................................................... 3-7

3.2.1 Can't login NM system.............................................................................. 3-7

3.2.2 Disconnection between OMM and NM servers ........................................... 3-8

I

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

3.3 Maintenance Guide about CS Service Faults ....................................................... 3-9

3.3.1 Mass users can't call normally................................................................... 3-9

3.3.2 All sites under BSC can't call normally ....................................................... 3-9

3.3.3 All sites under certain module in BSC can't call normally........................... 3-10

3.3.4 All sites under certain 100M/GB resource frame can't call normally.............3-11

3.3.5 All sites under certain BIPB/BIPB2/AIPB/AIPB2 can't call normally .............3-11

3.3.6 All sites under certain LAPD/LAPD2 can't call normally..............................3-11

3.3.7 Mass users belonging to other type can't call normally .............................. 3-12

3.4 Maintenance Guide about PS Service Faults...................................................... 3-12

3.4.1 Mass user can't use GPRS service.......................................................... 3-12

3.4.2 All users under whole BSC can't use GPRS service ................................. 3-13

3.4.3 Some cells can't use GPRS service......................................................... 3-13

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

4.1 Prerequisite of fault feedback .............................................................................. 4-1

4.2 Feedback Data That Shall be Recorded............................................................... 4-3

4.3 The method to get system record ........................................................................ 4-6

4.3.1 Get device printing file .............................................................................. 4-6

4.3.2 Get ZDB file ............................................................................................. 4-6

4.3.3 Get data backup ztd file from OMM ........................................................... 4-8

4.3.4 Get software setting ................................................................................. 4-8

4.3.5 Get alarm file ........................................................................................... 4-9

4.3.6 fanGet notification file ............................................................................. 4-13

4.3.7 Get 1 hour's performance data before and after fault ................................ 4-17

4.3.8 Get tracing signal at interface A............................................................... 4-20

4.3.9 Query dynamic data at interface A........................................................... 4-23

4.3.10 Get tracing signal at interface Abis......................................................... 4-24

4.3.11 Query dynamic data at site .................................................................... 4-26

4.3.12 Trace PS service signal ........................................................................ 4-26

4.3.13 Query BVC and NSVC state.................................................................. 4-28

4.3.14 Get operation log of preset machine ...................................................... 4-28

4.3.15 Check whether overstocked data exists ................................................. 4-28

4.3.16 Query disk space.................................................................................. 4-29

4.3.17 Get NM printing file............................................................................... 4-30

4.3.18 Get NM profile...................................................................................... 4-30

4.3.19 Get operation log at client ..................................................................... 4-30

4.3.20 View system time zone ......................................................................... 4-32

II

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

4.3.22 Maintenance Record List ...................................................................... 4-32

Figures............................................................................................................. I

Tables ............................................................................................................ III

Glossary .........................................................................................................V

III

About This ManualPurpose

This manual introduce the process of ZXG10 iBSC emergency maintenance, including thepreparation, typical emergency maintenance case and fault feedback information.

Intended Audience

l System engineerl Maintenance engineer

What Is in This Manual

This manual contains the following chapters:

Chapter Description

Chapter 1 Overview of


Describes applicable scope, guideline, and process of ZXG10 iBSC

emergency maintenance.

Chapter 2 Preparation of


Describes preparation of ZXG10 iBSC emergency maintenance.

Chapter 3 Guide of


Describes guideline of ZXG10 iBSC emergency maintenance on

different faults.

Chapter 4 Fault Feedback

Information

Describes the methods to send fault feedback and get system log of

ZXG10 iBSC emergency maintenance.

I

Chapter 1Overview of EmergencyMaintenanceTable of Contents

Scope of Emergency Maintenance .............................................................................1-1Guide Concept of Emergency Maintenance................................................................1-3Flow of Emergency Maintenance................................................................................1-3Precautions of Emergency Maintenance ....................................................................1-6Contact Information of Technical Support from ZTE....................................................1-6

1.1 Scope of Emergency MaintenanceDuring system running, you can confirm whether emergency maintenance shall be startedthrough user complaint, alarm inspection, and performance report analysis.

1. User complaint

Table 1-1 shows user complaints about emergency maintenance.

Table 1-1 User complaint

Complaint content Description

l Lots of speech user can't access;

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

l Lots of users can't use GPRS service

After receiving user complaints, you shall fur-

ther check alarm information and KPI measure-

ment result, to determine whether emergent

fault occurs.

2. Alarm inspection

Table 1-2 shows the alarm report that shall be viewed on emergency maintenance.

Table 1-2 Alarm report on emergency maintenance

Alarm Type Alarm Description

Alarms on spare boards, such as OMP/OMP2

and CMP/CMP2.

Active board alarm in active/standby mode

Board alarm Board alarm out of non-active/standby mode

1-1

SJ-20110531095035-006|2011-09-30(R1.1) ZTE Proprietary and Confidential

ZXG10 iBSC Emergency Maintenance

Alarm Type Alarm Description

Abnormal access clock

Phase-locked loop out of lock

Clock alarm Level 1 alarm on lost clock reference source

Alarm on unreachable MTP3 office

Alarms related with interface A SCCPSubsystem unavailable

MSCOverload

Congestion at signalling point

Alarms on flow control CPUToo high load

Loss of trunk frame

Loss of trunk signal

Relevant transmission alarms SDH/SONET: loss of signal

3. Analyzing a performance report

Normally, KPI indicator is not a direct condition to start emergency maintenance.Table 1-3 shows the important KPI indicators that shall be viewed and analyzed onemergency maintenance.

l While KPI is changed exceptionally, you shall confirm whether emergencymaintenance process shall be started, in combination with user complaint, test,and alarm analysis.

l While starting emergency maintenance process under critical alarm and usercomplaint, KPI indicator shall be used as a subsidiary analysis tool andtroubleshooting method.

Table 1-3 KPI Indicator

Indicator Type Indicator Name

SDCCH Congestion rate

TCH Congestion rate

TCH traffic

Congestion TCH availability

TCH Assignment success rate

Channel occupation Call success rate

Changeover related Handover success rate

Call drop TCH call drop rate

1-2


Chapter 1 Overview of Emergency Maintenance

1.2 Guide Concept of Emergency MaintenanceEmergency maintenance is suitable for the faults that shall be handled and restoredimmediately and have great influence on service. For more information on dailymaintenance, see ZXG10 iBSC (V6.20.71) Base Station Controller Routine Maintenance.For more information on normal troubleshooting, see ZXG10 iBSC (V6.20.71) BaseStation Controller Troubleshooting.

Prior to maintenance, you shall fully consider and follow below principles about emergencymaintenance.

l You shall firstly determine fault scope prior to maintenance, to do troubleshooting frominner to outer or from entire to local.

l Daily maintenance shall refer to ZXG10 iBSCand relevant equipment data, alongwith historical fault analysis and experience, and then you shall prepare foremergent schedule; the operator shall periodically organize relevant managers andmaintenance personnel for training and demonstration.

l When system or equipment encounters emergent faults, maintenance personnel shallkeep calm; then check BSC hardware and transmission to determine whether the faultis caused by BSC. If yes, you shall do troubleshooting according to emergent scheduleor relevant process in referential manual.

l Relevant maintenance personnel shall learn more about the system in dailymaintenance assignments, especially to be familiar with common exceptionalinformation about NM alarm and indicator conditions on BSC panel, and to mastercommon tools about data backup/restore.

l Before, in the process of, or after emergency maintenance, maintenance personnelshall 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 canprovide better after-sale service for the operator.

1.3 Flow of Emergency MaintenanceEmergency 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-1 shows the flow of emergency maintenance.

1-3



Figure 1-1 Flow of Emergency Maintenance

1.3.1 Determine the fault scopeDetermine fault scope based on three following aspects.

1-4


Chapter 1 Overview of Emergency Maintenance

1. Service faults often begin with user claims, so you shall register user number. Analyzethe site for user based on different tools at BSC and CN sides, to determine theinfluence scope of the fault.l Use signaling trace and probe to find out CN, BSC, or BTS that is claimed by user.

The aim is to reduce and determine fault related equipment.l If you can't determine the location of claiming user at BSC side, you shall search

for help from CN side.2. Determine fault scope through analysis of KPI indicator.

l Query relevant indicators in KPI to judge the affected site scope about the fault.l Determine whether it is global fault based on affected site.l Determine whether it is associated with module and special board based on based

on affected site.3. Test arrangement.

If possible, arrange test at specific area, and provide more accurate information onemergency maintenance.

1.3.2 Locate fault reason and record exceptionsPick up relevant data about alarm, performance, and printing, and analyze obviousphenomenon about network fault. Observe the information of equipment operation, boardindicator. Check the fault caused by BSS equipment or other reasons, and determine itsinvolved scope.

1.3.3 Fault AnalysisIf locating fault is caused by BSS equipment, you shall analyze field alarms, performance,signal, and printing log, and do troubleshooting after finding proper fault point.

1.3.4 Critical solutionSearch for emergency help from ZTE customer support center, which provides 7*24 hourshotline service and remote technical support service.

1. ZTE hotline service

Customer support center hotline: (fixed line) 8008301118; (cellphone) 4008301118.

2. Remote support

Based on the information provided by service hotline, technical expert remotely loginsat problematic site and assists customer to solve problems through phone; if theproblem is too complicated, ZTE will direclty appoint technical support engineer tothe field for troubleshooting.

3. Field Technical Support

Technical expert shall make emergency measures to restore normal communicationas soon as possbile.

1-5



1.3.5 Restore serviceFind out fault reason and quickly restore normal service through remote or field ZTEtechnical support. If you can't timely find the reason, you shall restore system serviceas soon as possible. If necessary, you shall try to solve the problem through boardswitchover, resetting, and restarting.

1.3.6 Observe restored servicesAfter the service is restored, you shall confirm whether normal operation state has beenrestored, and arrange relevant persons to do test. If necessary, you shall arrange somepersons on duty within peak traffic period, to closely monitor network operation. As such,if the problem occurs again, you shall solve it as soon as possible.

1.3.7 Feedback information about emergency maintenanceAfter 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 servicecenter.

1.3.8 Communication with customerFor level 1 faults, based on feedback data on site, ZTE mobile customer servicedepartment will submit fault analysis report to local office, and local office will communicatewith customer about involved faults.

1.4 Precautions of Emergency MaintenancePrecautions of emergency maintenance are as follows.

l You shall quickly find the fault location during emergency maintenance. Somerestoration (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 anoperator with certain maintenance experience.

l If the fault has a great influence on network operation, no matter whether maintenancepersonnel can solve it or not, they shall immediately contact ZTE customer servicecenter or local ZTE office, so we can timely and quickly find the fault location andsolve it.

1.5 Contact Information of Technical Support from ZTEContact information of technical support from ZTE is as follows.

1. Telephone at global ZTE customer service centerl Fixed phone: 8008301118.l Mobile phone: 4008301118.

2. Local ZTE office

1-6


Chapter 2Preparation of EmergencyMaintenanceTable of Contents

Daily Preparation of Emergency Maintenance ............................................................2-1Holiday Preparation of Emergency Maintenance ........................................................2-3

2.1 Daily Preparation of Emergency MaintenanceDaily preparation of emergency maintenance contain the following three contents:

l Data Backup and System Inspectionl Establish Remote Maintenance Stationl Preparation of important spare parts

2.1.1 Data Backup and System InspectionMaintenance personnel does data backup in daily maintenance. They can restoreconfiguration data during system faults, to enable the system restore normal service.

Maintenance personnel can find significant faults and potential risks through daily systeminspection.

Data Backup

Maintenance personnel shall backup daily data.

Configuration data can be manually or automatically backed-up.

l Automatic Backup

By default, the system backs-up OMM configuration data everyday.

Path to save configuration data: OMM server/home/xxxxxxx/ums-svr/backup/sysmanager/cm.

l Manual Backup1. Right-click the NE in physical view of topology management, select NE

Management > Configuration Management in floating menu, to callconfiguration management interface.

2. Select Management > Data Management > Data Backup.3. Data Backup interface pops up, as shown in Figure 2-1.

2-1



Figure 2-1 Data Backup Interface

4. Select NE, configure save path and backup NE, and click Ok button.5. Data Backup Result interface pops up, as shown in Figure 2-2. Click Close

button.

Figure 2-2 Data Backup Result Interface

2-2


Chapter 2 Preparation of Emergency Maintenance

The directory for data backup is : OMMserver/home/xxxxxxx/ums-svr/backup/sysmanager.

Checking the system

System inspection contains:

l View board indicatorsl Check communications link between the NMS and NE.l Query current BSC alarml Query the historical alarms within 24 hours at BSCl Query the historical notifications within 24 hours at BSCl Query important performance indicators at BSCl Check the state at interface Al Check the state at interface Gbl View the active/standby status of the board.l Query BSC operation logl Check the alarm box

For system inspection, refer to "Check Operation State at BSC" in ZXG10 iBSC (V6.20.71)Base Station Controller RoutineMaintenance, focusing on checking operation state at BSCand analyze performance indicator & historical alarms.

If major alarm exists while checking historical alarms (within 1 week) and current alarms,you shall handle it immediately. If the alarms still continue, you shall contact local ZTEoffice or customer service center.

2.1.2 Establish Remote Maintenance StationTo 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. Youcan contact local ZTE office while commissioning remote access.

2.1.3 Preparation of important spare partsYou shall prepare for sufficient spare parts for important boards on BSC, such asOMP/OMP2, CMP/CMP2, CLKG/ICM, CHUB, UIMC, UIMU/GUIM/GUIM2, PSN, andGLI/GLI4.

2.2 Holiday Preparation of Emergency MaintenancePreparation in holiday mainly aims the case of large traffic, not just the specific holidayperiod.

2.2.1 Load MonitoringUser shall monitor the load as follows.

2-3



1. View daily CPU load on BSC at busy time in holiday. CMP/CMP2 load at BSC can'texceed 70%.

2. Focus on CPU load on each board within whole monitoring period. Referentialthreshold is 70%.

3. Do your best to reduce the action of signaling trace during large traffic, to reduce theinfluence on MP load.

4. During large traffic, to reduce CPU load, you shall stop or close probe software.5. Monitor load value at no.7 signaling link at interface A on BSC, which shall be lower

than 0.4. If more than this value, you shall add more no.7 signaling links.6. Monitor load value of service timeslot at interface A on BSC, which shall be lower than

0.6 Erlang. If more than this value, you shall add more circuits at interface A.7. Monitor the signaling load at interface IPA on BSC, view "the number of received SCTP

packet", "the byte of received SCTP packet", "the number of transmitted SCTP packet",and "the byte of transmitted SCTP packet" in performance counters of SCTP couplingmeasurement. Its sum of SCTP coupling flow is lower than general signaling flow ofCMP/CMP2. If it is more than this value, you shall add more links at interface IPA.

Sum of SCTP coupling flow = (the byte of received SCTP packet + the byte oftransmitted SCTP packet + (the number of received SCTP packet + the number oftransmitted SCTP packet) * the bytes of protocol header in each packet)*8/ granularityof statistical report time.

The protocol header in each packet has 48 bytes.

Total signaling flow of CMP/CMP2 = 4Mbps* the number of CMP/CMP2.

8. Monitor the flow at interface IP A on BSC. The sum of received flow and the sum oftransmitted flow at different ports shall be lower than 80% of general flow at IP port.The max flow at each 100M port is 80Mbps, and that at each GB port is 700Mbps. Ifit is higher than this value, you shall add more links at interface IPA.

9. Monitor the traffic at interface IPA on BSC. Check the available average number ofUDP ports and total time occupied by UDPPort in performance management. Totaltime occupied by UDPPort (hours) / available average number at UDP port. The ratioshall be lower than 0.8. If more than this value, you shall add links at interface IPA.

10. It is recommended to monitor load condition at CN side. If the load at CN side isexceptional, you shall inform maintenance personnel as soon as possible.

2.2.2 Load reduction measuresUser can use the following measures to reduce load.

1. Measures at BSC side.l Check whether FUC flow control at BSC side is opened.l Check whether SIM card for field mobile phones are classified according to

specified requirements. If it is classified, you can check whether system messageabout flow control at BSC side is opened.

l For individual site with large traffic, it is recommended to open handover forpreprocessing.

2-4


Chapter 2 Preparation of Emergency Maintenance

l Pause or delete unnecessary observation tasks.l Pause or delete unnecessary measurement tasks.l Get no.7 signaling link at interface A and working load at service timeslot. The

one near or over upper limit shall be expanded timely.l Get working load about SCTP coupling at interface A. The one near or over upper

limit shall be expanded timely.l Temporarily modify two or more paging as one paging mode for CN.

2. Measures at CN side.l Don't send lots of paging messages at the same time.l Too heavy load at switching device. You shall check which BSC NE has the

heaviest traffic. You can block some circuits at interface A for this BSC, to reduceprocessing load at CN side.

l Timely start flow control function at CN side, preventing from too high load leadingto equipment degradation.

2-5



This page intentionally left blank.

2-6


Chapter 3Guide of EmergencyMaintenanceTable of Contents

Maintenance Guide about Major Alarm.......................................................................3-1Maintenance Guide about NM Faults..........................................................................3-7Maintenance Guide about CS Service Faults .............................................................3-9Maintenance Guide about PS Service Faults............................................................3-12

3.1 Maintenance Guide about Major AlarmMaintenance guide about major alarm contains the following contents:

l Board alarm;l Clock alarm;l Alarms related with interface A;l Alarms on flow control;l Relevant transmission alarms.

3.1.1 Board Alarm

3.1.1.1 Active board alarm in active/standby mode

1. Symptoms

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

l 198005379 Board offline or CPU in long-term resetting statel 198005390 Wrong (CPU) sub-card position configured by databasel 198066004 Communication blocked between module and OMP

2. Troubleshooting steps:

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

b. View board state after switchover, to check whether the board is normal. If thealarm continues on the active board after switchover, go to step 3.

c. If the fault also exits on standby board, reset active/standby board at the sametime.

d. Replace relevant boards.

3-1



e. If the alarms still continue, you shall contact local ZTE office or customer servicecenter.

3. Post inspection

The alarm is removed after checking on NM system.

3.1.1.2 Alarms related with OMP/OMP2 standby board

1. Symptoms

The following alarms are found in real-time alarm for OMP/OMP2 backup board.

l 198005379 Board offline or CPU in long-term resetting statel 198005122 Communication link disconnected at control plane between

active/standby boards2. Troubleshooting steps:

a. View OMP/OMP2 board indicators to check whether red alarm indicator, ALM, ison and the fault exists on OMP/OMP2.

b. Check whether the board is inserted in proper slot. If the board is not at properposition, or wrongly inserted, you shall plug/unplug the board again.

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

d. If above steps can't solve the fault, reset the board. First try to reset remotely fromNM. If the problem continues, you can reset it by manually plugging/unpluggingthe board.

e. Replace OMP/OMP2 board.

f. If the alarms still continue, you shall contact local ZTE office or customer servicecenter.

3. Post inspectionl The alarm is removed after checking on NM system.l If possible, switch the original standby OMP/OMP2 to active one while the service

traffic is minimum, and check whether the board is normal.

3.1.1.3 Alarms related with CMP/CMP2 standby board

1. Symptoms

The following alarms are found in real-time alarm for CMP/CMP2 backup board.

l 198005379 Board offline or CPU in long-term resetting statel 198005390 Wrong (CPU) sub-card position configured by databasel 198005122 Communication link disconnected at control plane between

active/standby boards2. Troubleshooting steps:

a. View rack board indicators at BSC side to check whether red alarm indicator, ALM,is on and the fault exists on NM.

3-2


Chapter 3 Guide of Emergency Maintenance

b. Check whether the board is inserted in proper slot. If the board is not at properposition, or wrongly inserted, you shall plug/unplug the board again.


d. If above steps can't solve the fault, reset the board. First try to reset remotely fromNM. If the problem continues, you can reset it by manually plugging/unpluggingthe board.

e. Replace CMP/CMP2 board.


3. Post inspection


3.1.1.4 Board alarm out of active/standby mode

1. Symptoms

The following alarms are found in real-time alarm for OMP/OMP2 active board.

l 198066003 Abnormal communication at control plane between board and itsmodule

l 198005379 Board offline or CPU in long-term resetting statel 198005390 Wrong (CPU) sub-card position configured by database


a. View rack board indicators at BSC side to check whether red alarm indicator is onand the fault exists on the board.

b. Check whether the board is inserted in proper slot. If the board is not at properposition, or wrongly inserted, you shall plug it properly again.


d. Reset relevant boards. First try to reset remotely from NM. If the problemcontinues, you can reset it by manually.

e. Replace this board.


3. Post inspection


3.1.2 Clock alarm1. Symptoms

The following alarms are found in real-time alarm.

3-3



l 198005381 Abnormal access clockl 198005646 Phase-locked loop out of lockl 198026129 Level 1 alarm on lost clock reference source


a. Check whether CLKG/ICM board is running normally. Board Alarm shows thesteps of inspection and troubleshooting.

b. Check whether SDTB/SDTB2, DTB, or SPB/SPB2 board to get clock at interfaceA is normal. Board Alarm shows the steps of inspection and troubleshooting.

c. Check whether cable connection from A-interface board to CLKG/ICM is normal.If the cable is loose or abnormal, you shall re-connect it or replace the clock cablefrom A-interface board to CLKG/ICM.

d. Check whether STM-1 and E1 are normal on the board to get clock at interfaceA. Check whether trunk interruption, high BER, or slide code alarm exist, suchas "SDH/SONET: signal missing", "trunk signal missing". If yes, you shall contacttransmission engineer to solve it.

e. If getting GPS clock, you shall check the connection condition from GPS antennafeeder to ICM board, and login the board through serial port mode, to check thecondition of satellite signal received.

f. If ICM board directly connects DDF to get A-interface clock at core side, youshall check ICM board followed by SDTB/SDTB2, DTB, or SPB/SPB2 board andin-between wiring.

g. Switchover CLKG/ICM board.

h. If the alarms still continue, you shall contact local ZTE office or customer servicecenter.

3. Post inspection


3.1.3 Alarms related with interface A1. Symptoms


l 198066010 Alarm on unreachable MTP3 officel 198066005 SCCP Subsystem Unavailable


a. Check E1/IP alarm at interface A to view whether all PCM/networks are interruptedat this interface.

b. Check whether the clock state at BSC side is exceptional. If yes, refer totroubleshooting in Clock Alarm.

c. Check whether global data at BSC and CN sides is changed. If yes, you shallrestore the data prior to changing.

3-4



d. Gradually switchover UIMU, UIMC, GUIM/GUIM2, CLKG/ICM boards. You shallcheck whether the service is restored while you switchover each board. If the faultcontinues, you can continue switchover the next board.


3. Post inspectionl The alarm is removed after checking on NM system.l Through dynamic data observation at interface A, test whether all signals, trunks,

signaling trace analysis and service test at interface A are normal.

3.1.4 Alarms on flow control

3.1.4.1 MSC overload

1. Symptoms


l 198087344 Overload of MSC FUC control model 198087347 Alarm on system message method during MSC overload


a. Inform MSC engineer to check whether MSC is overloaded and sendscorresponding overload message to BSC side.

b. Check whether FUC bitmap at BSC side is configured properly. If not, FUC flowcontrol will not work.

c. Check whether SIM card for field mobile phones are classified according tospecified requirements. If no classfication, FUC flow control hasn't any influenceon user service.

d. Contact local ZTE office or customer service support center.

3. Post inspectionl The alarm is removed after checking on NM system.l Transmission is restored through testing.

3.1.4.2 Congestion at signalling point

1. Symptoms


l 198087349 Alarm on system message method during SP congestion.l 198087346 Alarm on FUC control method during SP congestion.


a. Notify MSC engineers of checking whether no.7 signaling link is overloaded.

3-5



b. Query whether TCH traffic and the number of TCH request in KPI indicators aregreatly increased. If it is greatly increased, you can confirm SP congestion iscaused by higher traffic.

c. Check whether all no.7 signals are normal at this link, or any interruption or flashsymptom exist.

d. Check whether FUC bitmap at BSC side is configured properly. If not, FUC flowcontrol will not work.

e. Check whether SIM card for field mobile phones are classified according tospecified requirements. If no classfication, FUC flow control hasn't any influenceon user service.

f. Contact local ZTE office or customer service support center.

3. Post inspectionl The alarm is removed after checking on NM system.l Transmission is restored through testing.

3.1.4.3 Too high CPU load

1. Symptoms


l 198087348 Alarm on system message control mode due to higher CPU load.l 198087345 Alarm on FUC control mode due to higher CPU load.


a. Query whether TCH traffic and the number of TCH request in KPI indicators aregreatly increased. If it is greatly increased, you can confirm whether CPU overloadis caused by higher traffic.

b. Block corresponding cells in the region by using NM tools.

c. Check whether FUC bitmap at BSC side is configured properly. If not, FUC flowcontrol will not work.

d. Check whether SIM card for field mobile phones are classified according tospecified requirements. If no classfication, FUC flow control hasn't any influenceon user service.

e. Contact local ZTE office or customer service support center.

3. Post inspectionl The alarm is removed after checking on NM system. If the cell is blocked

previously, you shall unblock the cell.l Transmission is restored through testing.

3.1.5 Transmission alarms1. Symptoms


3-6



l 198000512 Loss of trunk framel 198000513 Loss of trunk signall 198001792 SDH/SONET: loss of signal


a. Check E1/IP alarm to view whether all PCM/networks are interrupted at thisinterface.

b. Check whether transmission cable is correct, connector is properly contacted, orcable is normal.

c. Inform transmission engineer to check transmission equipment and its link.

d. Replace relevant DTB, SDTB/SDTB2, and GIPI/GIPI4 boards.


3. Post inspectionl The alarm is removed after checking on NM system.l Transmission is restored.

3.2 Maintenance Guide about NM FaultsMaintenance guide about NM faults contains the following contents:

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

3.2.1 Can't login NM system1. Symptoms

Login from the client to the NM server fails.


There are two cases: all clients can't login or individual client can't login. So thetroubleshooting can be categorized into two types.

l All clients can't login.

a. Check running condition of server programs, and view whether all NMprocesses are normal.

b. check if server database is running properly.

c. Check operation condition of server operating system.

d. Restart the server.

e. If the alarms still continue, you shall contact local ZTE office or customerservice center.

l Individual client can't login.

3-7



a. check if client database is running properly.

b. Check if the client IP communicates normally with the server.

c. check if required Java packet exists and is normal during client operation.

d. Is client attacked by virus? check if operating system is normally running. Ifany virus is detected, kill it.

e. If the alarms still continue, you shall contact local ZTE office or customerservice center.

3. Post inspection

Successfully log in client and you can use it normally.

3.2.2 Disconnection between OMM and NM servers1. Symptoms

Can't start NE agent.


a. Check whether the physical link between NM server and OMM server isconnected.

b. Check whether the firewall ports of NM server and OMM server are opened.

c. Check whether OMM FTP server is available, and check whether FTP portdefinition of profile is correct.

d. If the alarms still continue, you shall contact local ZTE office or customer servicecenter.

3. Post inspection

NE agent is successfully enabled, and you can use it normally.

3.2.3 Disconnection between equipment and OMM server1. Symptoms

In configuration management, it is found the link between equipment and OMM isdisconnected, and configuration data can't be distributed normally.


a. Check whether IP network from OMP/OMP2 to HUB is normal.l Check the network cable from OMP/OMP2 to HUB.l Check configuration of OMP/OMP2 IP address in OMM server data.

b. Check whether the MP is running normally. If no, refer to troubleshooting in BoardAlarm.

c. Restart OMM server.

3-8




3. Post inspection

Check the NMS and find the communications link between the NMS and NE isestablished. The alarm is removed.

3.3 Maintenance Guide about CS Service FaultsMaintenance guide about CS service faults contains the following contents:

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

3.3.1 Mass users can't call normally1. Symptoms

Mass users can't call normally

2. Troubleshooting

Based on quantity and domain of claiming users and in combination with KPI analysisand test, you can determine the influence scope of this fault. According to differentservice scope, you can use the following troubleshooting methods.

For more information, refer to All Sites Under BSC Can't Call Normally, All SitesUnder Certain Module In BSC Can't Call Normally, All Sites Under Certain 100M/GBResource FrameCan't Call Normally, All Sites Under Certain BIPB/BIPB2/AIPB/AIPB2Can't Call Normally, All Sites Under Certain LAPD/LAPD2 Can't Call Normally, andMass Users Belonging To Other Type Can't Call Normally.

3. Post inspectionl The result is normal during calling test.l KPI index restores the level prior to the fault.

3.3.2 All sites under BSC can't call normally1. Symptoms

All sites under BSC can't call normally.

2. Troubleshooting

3-9



a. Check whether the link at interface A is disconnected and global alarm issues. Ifit is disconnected at interface A, refer to troubleshooting in Alarms Related WithInterface A.

b. Check whether clock alarm exists by viewing global alarms. If yes, refer totroubleshooting in Clock Alarm.

c. Check whether the active/standby boards for switching shelf, such as GLI/GLI4,PSN, or UIMC, or control shelf, such as OMP/OMP2 and CMP/CMP2 can't worknormally. If yes, refer to troubleshooting in Board Alarm.

d. Enable signaling trace based on test condition. Check whether ring message isdistributed or ground resource can be allocated normally.

If signal is complete, and no sound exists at one channel or in bidirection, you shallcheck whether there is any alarm on AIPB/AIPB2 and BIPB/BIPB2 logical board.If yes, reset the board.

e. Switchover OMP/OMP2 board.


3. Post inspectionl The alarm is removed after checking on NM system.l You can call normally at all sites under BSC.l KPI index restores the level prior to the fault.

3.3.3 All sites under certain module in BSC can't call normally1. Symptoms

All sites under certain module in BSC can't call normally.

2. Troubleshooting

a. View CMP/CMP2 alarm on this module to check whether the board or certain CPUon it can't normally function. If yes, refer to troubleshooting in Board Alarm.

b. View whether flow control alarm occurs due to CPU overload on this module. Ifyes, refer to troubleshooting in Alarms On Flow Control.

c. Replace the module on CMP/CMP2.

d. Reset or replace this CMP/CMP2 module.


3. Post inspectionl The alarm is removed after checking on NM system.l You can call normally at all sites under this module in BSC.l KPI index restores the level prior to the fault.

3-10



3.3.4 All sites under certain 100M/GB resource frame can't callnormally

1. Symptoms

All sites under certain 100M/GB resource frame can't call normally.

2. Troubleshooting

a. Check the UMIU/GUIM/GUIM2 alarm of this shelf to view whether the board can'twork normally. If yes, refer to troubleshooting in Board Alarm.

b. Check whether ethernet cable from UIMU/GUIM/GUIM2 to CHUB is normallyconnected.

c. Check whether clock cable from UIMU/GUIM/GUIM2 to CLKG/ICM is normallyconnected.

d. Switchover this UIMU/GUIM/GUIM2 board.

e. Reset this UIMU/GUIM/GUIM2 board.


3. Post inspectionl The alarm is removed after checking on NM system.l You can call normally at all sites under this resource shelf.l KPI index restores the level prior to the fault.

3.3.5 All sites under certain BIPB/BIPB2/AIPB/AIPB2 can't callnormally

1. Symptoms

All sites under BIPB/BIPB2/AIPB/AIPB2 can't call normally.

2. Troubleshooting

a. Check the BIPB/BIPB2/AIPB/AIPB2 alarm to view whether the board can't worknormally. If yes, refer to troubleshooting in Board Alarm.

b. Reset this BIPB/BIPB2/AIPB/AIPB2 board.

c. If the alarms still continue, you shall contact local ZTE office or customer servicecenter.

3. Post inspectionl The alarm is removed after checking on NM system.l You can call normally at all sites under BIPB/BIPB2/AIPB/AIPB2.l KPI index restores the level prior to the fault.

3.3.6 All sites under certain LAPD/LAPD2 can't call normally1. Symptoms

3-11



All sites under LAPD/LAPD2 can't call normally.

2. Troubleshooting

a. Check the LAPD/LAPD2 alarm to view whether the board can't work normally. Ifyes, refer to troubleshooting in Board Alarm.

b. Reset this LAPD/LAPD2 board from equipment.

c. If the alarms still continue, you shall contact local ZTE office or customer servicecenter.

3. Post inspectionl The alarm is removed after checking on NM system.l You can call normally at all sites under LAPD/LAPD2.l KPI index restores the level prior to the fault.

3.3.7 Mass users belonging to other type can't call normally1. Symptoms

Mass users belonging to other type can't call normally.

2. Troubleshooting

a. Check whether data is changed at BSN or CN side. If yes, you shall restore originalbackup data.

b. Trace and record messages at interface Abis and A to analyze it. Determine it iscaused by the problem at BSC or CN side based on signaling process.

c. Analyze SDCCH assignment failure rate, TCH allocation failure rate, TCHassignment failure rate, SDCCH congestion rate, and TCH congestion rate in KPIindicators, to determine which phase the fault occurs.

d. Contact local ZTE office or customer service support center.

3. Post inspectionl The alarm is removed after checking on NM system.l user can call normally.l KPI index restores the level prior to the fault.

3.4 Maintenance Guide about PS Service FaultsMaintenance guide about PS service faults contains the following contents:

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

3.4.1 Mass user can't use GPRS service1. Symptoms

3-12



Lots of users can't use GPRS service

2. Troubleshooting

Based on quantity and domain of claiming users and in combination with KPI analysisand test, you can determine the influence scope of this fault. According to differentservice scope, you can use the following troubleshooting methods.

For more information, refer to All Users Under Whole BSC Can't Use GPRS Serviceand Some Cells Can't Use GPRS Service.

3. Post inspectionl You can normally use GPRS service.l KPI index restores the level prior to the fault.

3.4.2 All users under whole BSC can't use GPRS service1. Symptoms

Lots of users under whole BSC can't use GPRS service

2. Troubleshooting

a. Check the DTB or GIPB/GIPB2 alarm at interface Gb to view whether the boardcan't work normally. If yes, refer to troubleshooting in Board Alarm.

b. Check the UPPB/UPPB2 alarm to view whether the board can't work normally. Ifyes, refer to troubleshooting in Board Alarm.

c. View E1 alarm at interface Gb to check whether E1 transmission is interrupted. Ifyes, check E1 cable, and inform transmission engineer to check E1 transmission.

d. Check whether IP network at interface Gb is disconnected. If yes, you shall checkwhether IP cable is normal, office direction from BSC to SGSN is normal, NSVCstate is normal, and relevant configuration is correct.

e. Reset GIPB/GIPB2 or DTB board at interface Gb.

f. Reset UPPB/UPPB2 board.

g. If the alarms still continue, you shall contact local ZTE office or customer servicecenter.

3. Post inspectionl The alarm is removed after checking on NM system.l You can normally use GPRS service of this BSC.l KPI index restores the level prior to the fault.

3.4.3 Some cells can't use GPRS service1. Symptoms

Lots of users in some cells can't use GPRS service

2. Troubleshooting

3-13



a. Check the UPPB/UPPB2 alarm to view whether the board or certain CPU can'twork normally. If yes, refer to troubleshooting in Board Alarm.

b. In dynamic data management interface, view BVC state in the cell and checkwhether BVC is blocked. If yes, unblock the BVC.

c. Confirm whether lots of GRPS data are changed prior to the fault. If yes, you shallrestore the data firstly.


3. Post inspectionl The alarm is removed after checking on NM system.l You can normally use GPRS service in this cell.l KPI index restores the level prior to the fault.

3-14


Chapter 4Fault Feedback InformationTable of Contents

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

4.1 Prerequisite of fault feedbackPrerequisite of fault feedback:

1. Fault time2. Fault description3. Detailed troubleshooting steps4. System record5. Fault feedback report

Presented below are a brief description of different elements.

1. Fault time

Describes specific time of the fault, including start/end time of the fault.

2. Fault description

a. Describes the fault symptom, such as board state, dynamic state, NM alarm,messages, and calling state. These are the basis of field troubleshooting.

b. It describes the fault scope, such as whole BSC or site.

c. If you can't express it clearly, you shall copy the pictures. For the channel state indynamic management and error messages occurred during operation, you shallcopy it in picture mode.

3. Detailed troubleshooting steps

a. Steps and time about field troubleshooting.

b. It includes the operation cases that may cause the fault.

c. It is recommended that field operators keep a good habit to record operationprocedures for the server, so it can provide a convenience to check whether thereis any operation error. For the operations on the server, you can use the recordfunction of NETTERM to remember the operation procedures.

4. System record

It records system operation state and error messages, which is the primary method tofind system errors.

4-1



5. Fault feedback report

Table 4-1 shows fault feedback report.

Table 4-1 Field Fault Feedback Report

Feed-

back

by Feedback time

Re-

ceived

by

Con-

tact

person Phone No.

Con-

tact

e-mail

Source

unit Model

Network capacity

Ver-

sion

Fault

time,

symp-

tom,

and

de-

scrip-

tion Attached pages

De-

scrip-

tion of

field

proce-

dure

and

han-

dling Attached pages

Field

data

feed-

back Attached pages

Attached pages

Analy-

sis and

prelim-

inary

com-

ments

Han-

dled by Day

4-2


Chapter 4 Fault Feedback Information

Final

com-

ments

and

conclu-

sion

4.2 Feedback Data That Shall be RecordedTable 4-2 shows the feedback data required by BSC faults.

Table 4-2 Feedback data required by BSC faults

System feedback records

required Purpose of Record

The method to get system

record

Board indicator conditions on

fault

The indicators contain the el-

ementary 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 oc-

curred during BSC operation in

equipment printings. Refer toGet Device Printing File.

ZDB file in all active MP for the

equipment or ZDB file for NM.

Configuration information in

BSC, to learn configuration in-

formation. Refer to Get ZDB File.

ZTD backup files in NM.

Configuration information in NM,

to learn configuration informa-

tion.

Refer to Get Data Backup Ztd

File From OMM.

Screenshot if board in-stock ver-

sion, general software version,

and specified version settings.

Software settings about the

board Refer to Get Software Setting.

Alarm file, picking up historical

alarmswithin a week and current

alarms.

Alarm file records all alarms in

the system. Refer to Get Alarm File.

Notification file, picking up his-

torical files within a week.

Notification file is the supple-

ment of system alarm. Refer to Get Notification File.

Equipment and NM version

number.

Different version has different

functions, so you shall return

feedback.

Feedback shall be sent based

on the version of field records.

4-3






record

Performance report within 1

hour before and after the fault.

Do measurement according to

cell level.

You can find system operation

state in performance statistics.

Refer to Get 1 Hour's Perfor-

mance Data Before And After

Fault.

For the fault related with inter-

face A, you shall send feedback

about signaling tracing at inter-

face A.

Signaling is a very useful tool to

locate questions.

Refer to Get Tracing Signal At

Interface A.

If the problem is related with in-

terface A or whole BSC, you

shall send feedback about dy-

namic state of the link at inter-

face A. State of the link at interface A.

Refer to Query Dynamic Data At

Interface A.

For the fault related with inter-

face Abis, you shall send feed-

back about signaling tracing at

interface Abis.


locate questions.


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.


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.

For the fault related with PS ser-

vice, you shall send feedback

about signaling about PS.


locate questions.

Refer to Trace PS Service Sig-

nal.

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 Over-

stocked Data Exists.

Table 4-3 shows the feedback data required by NM faults.

4-4



Table 4-3 Feedback data required by NM faults




record

Check the disk space Reflect the disk condition Refer to Query Disk Space.

NM printing file

Record the operation conditions

of NM system. Refer to Get NM Printing File.

ZTD backup files in NM.

Configuration information in NM,

to learn configuration informa-

tion.

Refer to Get Data Backup Ztd

File From OMM.

NM profile

Important configuration in the

system. Refer to Get NM Profile.

Operation log at client. Record NM 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 differ-

ent functions. Refer to View NM Version.

Table 4-4 shows the feedback data required by site faults.

Table 4-4 Feedback data required by site faults




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 chan-

nel.

Channel state is another path to

judge system state.


Site.

O&M signaling trace

Reflect the information while the

site is starting.


Interface Abis.

Signaling trace at interface Abis. Record call cases in the system.


Interface Abis.

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 differ-

ent functions.

Refer to Get BTS Software Set-

ting.

4-5






record

NE ZDB file

Record and confirm NE configu-

ration information.

Refer to Get Equipment ZDB

File.

4.3 The method to get system record

4.3.1 Get device printing file

Steps

1. Create a directory to save files on OMM server.

2. Use command ftp to connect OMP/OMP2 on OMM. Both username and password arezte at specified port 21.

3. Use command cd /DOC0 to enter into DATA0 directory.

4. Use command "get" to get Exc_Omp.txt and Exc_pp.txt files.

5. After the files are downloaded onto OMM server, you can use ftp tool, such asCUTEFTP, to upload the files to client.

End of Steps

Example

1. mkdir bsc12. cd bsc13. ftp 172.20.6.1 214. cd /DOC05. get Exc_pp.txt6. get Exc_Omp.txt7. bye

4.3.2 Get ZDB file

4.3.2.1 Get equipment ZDB file

Context

ZDB file is under /DOC0/DATA1 on OMP/OMP2. While getting ZDB file, if there are toomany files, you had better establish a proper directory for each module on each BSC, totransfer the ZDB files into proper directory.

4-6



Steps

1. Creat a directory to save files on OMM server.

2. Use command ftp to connect OMP/OMP2 on OMM. Both username and password arezte at specified port 21.

3. Get required ZDB files under DATA1 directory.

a. Use command cd to enter into /DOC0/DATA1.

b. Use command get filename to download CFGTABLE.ZDB, VERTABLE.ZDB, andDBVER.ZDB one by one.

4. After the files are downloaded onto OMM server, you can use ftp tool, such asCUTEFTP, to upload the files to client and compress it.

End of Steps

Example

1. cd $OMCHOME2. mkdir bsc13. cd bsc14. ftp 172.20.6.1 215. cd /DOC0/DATA16. get CfgTable.ZDB7. get DBVer.ZDB8. get VERTABLE.ZDB

4.3.2.2 Get OMM ZDB file

Context

OMM ZDB files are saved in $OMCHOME/tmp/ftp/zdb/ibscXX (XX indicates BSCID).Each time you perform whole table synchronization or incremental synchronization, itmay generate new CFGTABLE.ZDB, VERTABLE.ZDB, and DBVER.ZDB files, and addgeneration time postfix for the file generated at last time for backup.

Steps

1. Generated file is too small during incremental synchronization. You can use ls lcommand to veiw the file size. If current ZDB file belongs to the one genereated onincremental synchronization, you can do a synchronization action on whole table onNM client, this will generate new complete ZDB file.

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

End of Steps

4-7



4.3.3 Get data backup ztd file from OMM

Steps

1. Right-click the NE in physical view of topology management, select NE Management> Configuration Management in floating menu, to call configuration managementinterface.

2. Select Management > Data Management > Data Backup.

3. In displayed Data Backup window, select backup path, /CM, (normally on OMMserver). Input prefix of backup filename, and backup description, and select a NE tobe backed-up. After acknowledgement, click OK button.

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

End of Steps

4.3.4 Get software setting

4.3.4.1 Get BSC software setting

Steps

1. Right-click the NE in physical view of topology management, select NE Management> Software Version Management in floating menu, to call configuration managementinterface.

2. In Software Version Management interface, select BSC Software Management.

3. For setting of software version, equipment data may be inconsistent with NM data, soif you can't determine whether it is consistent, you shall do the action of "synchronizeversion data from NE to OMC". synchronization operation may remove NM softwaresetting, operate the data based on actual equipment condition, and re-establish NMsoftware settings.

4. After the synchronization, snap three screenshots for version file, common version,and special version of BSC. Save it as jpg file and send feedback.

End of Steps

4.3.4.2 Get BTS software setting

BTS software setting can fed back by getting VerTable.ZDB. For detailed operations, referto Get equipment ZDB file.

4-8



4.3.5 Get alarm file

Steps

1. Start AlarmManagement at client. Select View History Alarms in View Alarmmenuoption of Alarm Management interface, as shown in Figure 4-1.

Figure 4-1 Select View History Alarms

2. Select Quick Search in Query Setting of History Alarm.

3. Select System Type in Query History Alarm window, and select all alarm types inSystem Type.

4. Select a relative time in Happen Time. The date shall be a day within a recent weekor a customized day, as shown in Figure 4-2.

4-9



Figure 4-2 Set query time of alarm

5. In NE Type, enter IBSC%. You can use % to do fuzzy searching, as shown in Figure4-3.

4-10



Figure 4-3 Set the Type of Alarm NE

6. Click OK to output alarm data.

7. Click Export button to export queried alarms.

8. In Save window, select the proper path and click Save, as shown in Figure 4-4.

4-11



Figure 4-4 Alarm Save Window

Note:

You also can right-click the NE in resource view of alarm management, select ShowHistory Alarms in floating menu to view history alarm, as shown in Figure 4-5. Youcan't select alarm Happen Time by using this method.

Figure 4-5 Displaying history alarms of the selected NE

End of Steps

4-12



4.3.6 fanGet notification file

Steps

1. Start Alarm Management at client. Select View Notifications in View Alarm menuoption of Alarm Management interface, as shown in Figure 4-6.

Figure 4-6 Select View Notifications

2. Select Quick Search in Query Setting of Notification, as shown in Figure 4-7.

Figure 4-7 Select Quick Search

3. Select System Type in Query Notification window, and select all notification types inSystem Type, as shown in Figure 4-8.

4-13



Figure 4-8 Query Notification Window

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

4-14



Figure 4-9 Set query time of notification

5. In NE Type, enter IBSC%. You can use % to do fuzzy searching, as shown in Figure4-10.

4-15



Figure 4-10 Set the Type of Nofication NE

6. Click OK to output notification data.

7. Click Export button to export queried notifications.

8. In Save window, select the proper path and click Save, as shown in Figure 4-11.

4-16



Figure 4-11 Notification Save Window

End of Steps

4.3.7 Get 1 hour's performance data before and after fault

Steps

1. Start Performance Management at client, select the NE to be viewed in resourceview. Select Performance Management > Performance Data Query menu, asshown in Figure 4-12.

Figure 4-12 Select Performance Management and Performance Data Query

2. InQuery Index of Integrated Query interface, select NE type as BSC Elements, andselect object type as CellFunction Type, select KPI index and PI index, as shown inFigure 4-13.

4-17



Figure 4-13 Integrated Query Interface

3. Select customized time in Query Time tab, query granularity is 15 minutes, as shownin Figure 4-14.

Figure 4-14 Set Query Time of Performance Data

4. Select the NE to be queried in Query Object tab, and query mode is Cell. Select thecell to be queried in measurement object, and summary mode is Cell (Original PolledObject), as shown in Figure 4-15.

4-18



Figure 4-15 Set Query Object of Performance Data

5. Queried data shall be exported as EXCEL report.

6. Repeat above steps, query basic measurement data of CS and export it as EXCELreport, as shown in Figure 4-16.

Figure 4-16 Select Basic Measurement Data of CS

End of Steps

4-19



4.3.8 Get tracing signal at interface A

Steps

1. Configure server procedure for signaling trace tool, start server program, start andlogon signaling trace client.

Note:

Signaling trace tool shall use server/client architecture.

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

2. Select Tools SystemSetting, and access to Parameter Setting interface to configuresignaling trace. In Record Setting tab, configure Capacity of Signal Window as20000. Select File Spliting, 5000 for each file. Click Save button, as shown in Figure4-17.

Figure 4-17 Parameter Setting interface

3. Configure in Trace Setting interface, select the BSC to be traced, and click UpdateConfiguration button, as shown in Figure 4-18.

4-20



Figure 4-18 Trace Setting interface

4. After successfully updating configuration, select SCCP. In SCCP option, selectModule No, and select Subsystem No. as 254, as shown in Figure 4-19.

Figure 4-19 Select SCCP

5. Select M3UA . In M3UA, select coupling ID, corresponding coupling SCCP, anddirection, as shown in Figure 4-20.

4-21



Figure 4-20 Select M3UA

6. After stopping trace, select File > Save all as .tra. Save all signaling trace result astra format, as shown in Figure 4-21.

Figure 4-21 Save Signaling Trace Result

7. Select the path to save in Save window, saved files contain .tra and .idx files. Iffeedback, you shall send the both files, as shown in Figure 4-22.

4-22



Figure 4-22 Signaling Trace Save Window

Note:

Trace at interface A has great influence on system load. Each trace can't exceed 5minutes.

End of Steps

4.3.9 Query dynamic data at interface A

Steps

1. Login in NM client, right-click the NE in physical view of topology management, selectNEManagement Dynamic Data Management in floating menu, to call Dynamic DataManagement interface.

2. In configuration resource tree, select and expand management NE node, double-clickcorresponding dynamic data management node, enter dynamic data managementinterface, and you can do A-interface PCM, A-interface trunk management, and IPAresource management.

3. In A-Interface PCM tab, click Query button to query PCM state; in A-Interface TrunkCircuit Management tab, clickAll Queries button, or select some circuits, clickQueryTimeslot Circuit State button to query the state of timeslot.

4. If using IP A-interface, in IPAManagement tab, clickQuery button to query DSP state.

End of Steps

4-23



4.3.10 Get tracing signal at interface Abis

Steps

1. Configure server procedure for signaling trace, start server program, start and logonsignaling trace client.

Note:



2. Select Tools SystemSetting, and access to Parameter Setting interface to configuresignaling trace. In Record Setting tab, configure Capacity of Signal Window as20000. Select File Spliting, 5000 for each file. Click Save button, as shown in Figure4-23.

Figure 4-23 Parameter Setting interface at Abis

3. Configure in Trace Setting interface, select the BSC to be traced, and click UpdateConfiguration button.

4. After successfully updating configuration, select CS and OAM, select the site to betraced in CS and OAM interfaces. Select all traced entries in Tracing Entry of CS,select a site in OAM, as shown in Figure 4-24 and Figure 4-25.

4-24



Figure 4-24 CS interface

Figure 4-25 OAM interface

5.

End of Steps

4-25



4.3.11 Query dynamic data at site

Steps

1. Right-click the NE in physical view of topology management, select NE Management> Dynamic DataManagement in floatingmenu, to enterDynamic DataManagementinterface.

2. In configuration resource tree, select and expand BSC management NE node.

3. Double-click corresponding dynamic data management node at site, enter intoDynamic Data Management interface. So you can perform radio resourcemanagement and BTS equipment management.

Table 4-5 shows dynamic data management function.

Table 4-5 Dynamic Data Management Function

Category Function Description

Cell management query the status of cell

TRX management Query the state of TRX

Channel Management Query channel state

Module Management

Query channel statistics on amod-

ule

BVC Management Query the BVC status of cellRadio Resources Man-

agement Cell channel management Query channel statistics of a cell

Timeslot management at Abis

Query timeslot state measure-

ment of resource pool at Abis

Timeslot resourcemanagement at

Abis

Query timeslot state of resource

pool at Abis

LAPD state management Query LAPD link state at siteBTS equipment man-

agement operation Loopback Management Query the loopback state

End of Steps

4.3.12 Trace PS service signal

Steps

1. Configure server procedure for signaling trace, start server program, start and logonsignaling trace client.

4-26



Note:



2. Select Tools SystemSetting, and access to Parameter Setting interface to configuresignaling trace. In Record Setting tab, configure Capacity of Signal Window as20000. Select File Spliting, 5000 for each file. Click Save button.

3. In Trace Setting interface, select the BSC to be traced, and click UpdateConfiguration button.

4. For Trace Type, select PS and RLCMAC at interface Abis, and all options at interfaceGb.

5. Select the cell to be traced in PS and RLCMAC, BVCI and BVCIO to be traced inBSSGP and LLC, NSVC link to be traced in NS, BRCH link to be traced in FR, andNSVC to be traced in SNS (optional). Click OK button, as shown in Figure 4-26.

Figure 4-26 Trace Setting of PS service signal

6. After stopping trace, select File Save all as .tra. Save all signaling trace result as traformat.

4-27



7. Select the path to save in Save window, saved files contain .tra and .idx files. Iffeedback, you shall send the both files.

End of Steps

4.3.13 Query BVC and NSVC state

Steps

1. Right-click the NE in physical view of topology management, select NE Management> Dynamic DataManagement in floatingmenu, to enterDynamic DataManagementinterface.

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

3. Double-click corresponding dynamic datamanagement node, enter into dynamic datamanagement interface.

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

5. In configuration resource tree, double-click corresponding dynamic data managementnode under management NE node to be queried, enter into dynamic datamanagement interface.

6. In Wireless Resource Management tab of Dynamic Data Management interface,select BVC Management to query BVC state.

End of Steps

4.3.14 Get operation log of preset machineOperation log of preset machine is saved in X:\FTPRoot\nfsDev\iBSC\OMS\log. You canget it through ftp tools. Where, X indicates the disk label of the log.

Meanwhile, you shall display the update date in \FTPRoot\nfsDev\iBSC\OMS\,\FTPRoot\nfsDev\iBSC\OMCR, and \FTPRoot\nfsDev\iBSC\OMSZIP.

4.3.15 Check whether overstocked data exists

Steps

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

Data accumulation is caused by exceptional oracle, full table space in performancelibrary and performance index. For specific information, you can get error reasonsfrom server log.

Solution is as follows:

4-28



i. Check the space size of performance table and index table, if it is full, you canexpand it based on server disk space, or delete relevant performance data andre-create index.

ii. Exceptional operation modes of oracle are diversified, and it is complicated tosolve it. It is recommend you shall return server log to ZTE for analysis. You cantry to restart ORACLE on site.

2. Check whether data file is overstocked in X:FTPRoot\nfsDev\iBSC\OMCR of presetmachine. Where, X is the label of data file disk.

CheckWhether communication between NM server and preset machine is normal andwhether ftp service of preset machine is normal. You can try to preset machine throughftp and get performance file under NM directory.

3. Check whether backed-up configuration management files under/home/xxxxxxx/ums-svr/backup/sysmanager/cm in OMM server are overstocked.

4. Check whether backed-up alarm management files under/export/home/xxxxxxx/ums-server/backup/sysmanager/fm on the server areoverstocked.

5. Check whether backed-up performance management files under/export/home/xxxxxxx/ums-server/backup/sysmanager/pm on the server areoverstocked.

6. Check whether backed-up log management files under/export/home/xxxxxxx/ums-server/backup/sysmanager/log on the server areoverstocked.

7. Check whether backed-up performance configuration files under/export/home/xxxxxxx/ums-server/backup/sysmanager/ueppm on the server areoverstocked.

End of Steps

4.3.16 Query disk space

Steps

1. For the Linux or Solaris system, use the commands df k and vmstat to query thecurrent disk space.

2. Use NETTERM to save operation procedure.

3. For the AIX system, use the commands df k and vmstat to query the current diskspace. For the AIX system, step 2 is unnecessary.

End of Steps

4-29



4.3.17 Get NM printing file

Steps

1. Process printing file related with NM is located under $OMCHOME\log. The log fileis named by its generation time. If you use command cd $OMCHOME\log, you canenter into this directory to get corresponding LOG file.

2. Use ftp tool, such as cuteftp, to get log file within NM fault period.

End of Steps

Example

1. bash-3.00$ cd $OMCHOME/log2. bash-3.00$ ls3. boot.log server-20080117-0623-28443.log server-20080117-1005-13029.log

server-20080117-1436-53392.log4. consoleagent.log.0 server-20080117-0812-56822.log

server-20080117-1048-52694.log server-20080117-1516-54067.log5. consoleagent.log.0.lck6. bash-3.00$ pwd7. /export/home/iomcr/iOMCR6.00.02f/ums-svr/log

4.3.18 Get NM profileNM profile is saved in $OMCHOME/deploy. You can use ftp tools, such as CUTEFTP, todownload it to local client. Required profile is as follows:

l deploy-010muep.propertiesl deploy-*.properties

Real-time alarm file related with server and NM system is saved in$OMCHOME/ums-svr/minos/minos-naf-rtalarm.par/conf. On OMM server, this file issaved in $OMCHOME/gsmomcr/ibsc/zxgomcr-naf-rtalarm.par/conf. Required profile isas follows:

l fmmgr.propertiesl nafproc.properties

4.3.19 Get operation log at client

Steps

1. Right-click the NE in physical view of topology management, select Query NE Log >Operation Log in floating menu, to call log management tool at NM client, as shownin Figure 4-27.

4-30



Figure 4-27 Select Query Operation Log

2. In Query Operation Log window, customize operation time to query, or query alloperation log, and click OK button, as shown in Figure 4-28.

Figure 4-28 Query Operation Log window

4-31



3. After successfully querying, export the log to excel.

End of Steps

4.3.20 View system time zone

Steps

1. View time zone at server side by using command echo $TZ.

2. To view the time zone at client, you can perform as follows:

After opening control panel of client computer, you can find current time zone in theoption of region setting.

End of Steps

4.3.21 View NM versionOn client interface of NM system, click H

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

Documents

Transcript of ZXG10 iBSC (V6.20.71) Base Station Controller Emergency Maintenance.pdf