zxsdr_b8200_gu360_(v4.09.21)_maintenance_guide

ZXSDR B8200 GU360Indoor GSM&UMTS Dual Mode Baseband

UnitMaintenance Guide

Version 4.09.21

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 INFORMATION

Copyright 2010 ZTE CORPORATION.

The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution ofthis document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-RATION 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 CORPORATIONor of their respective owners.

This document is provided as is, and all express, implied, or statutory warranties, representations or conditions are dis-claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on theinformation contained herein.

ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subjectmatter 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.0 20100619 First Edition

R1.1 20100819 Topic LED Indicator Analysis has been modified.

Serial Number: SJ-20100510160815-015

Contents

Preface.............................................................. I

Maintenance Overview ......................................1Requirements for Maintenance Personnel ........................... 1

Maintenance Principles .................................................... 1

Overview................................................................... 1

Rights Management .................................................... 2

Data Observation........................................................ 2

Data Modification........................................................ 3

Data Synchronization .................................................. 3

Man-Machine Command .............................................. 3

Board Operations........................................................ 3

System Update .......................................................... 4

Maintenance Category..................................................... 4

Maintenance Analysis Methods ......................................... 5

LED Indicator Analysis................................................. 5

Signaling Tracing Analysis...........................................11

Alarm Log Analysis ....................................................11

Instrument and Meter Analysis ....................................11

Comparison by Replacement .......................................12

Attention Items .............................................................13

Personnel Qualifications..............................................13

Maintenance Management ..........................................13

Data Maintenance......................................................14

Equipment Environment .............................................14

Tools and Instruments................................................14

Spare Parts...............................................................14

Technical Documents..................................................15

Technical Support .....................................................15

Routine Maintenance.......................................17Overview......................................................................17

Daily Maintenance Items ................................................18

Confidential and Proprietary Information of ZTE CORPORATION I

ZXSDR B8200 GU360 Maintenance Guide

Monthly Maintenance Items ............................................18

Semi-Yearly Maintenance Items.......................................19

Other Recommended Maintenance Items ..........................20

Troubleshooting Examples ..............................21Overview......................................................................21

System Monitoring ........................................................21

High CPU Utilization ...................................................21

Decreased BS Coverage Radius ...................................22

User Complaints ............................................................22

Low Call Completion Rate ...........................................22

Poor Call Quality........................................................24

Slow Internet Access..................................................25

Emergency Maintenance..................................27Overview......................................................................27

Fault Evaluation.............................................................27

Evaluation Standard of Complete Equipment

Breakdown .......................................................27

Service Impact of the Fault .............................................28

Fault Report Flow...........................................................28

Emergency Fault Handling ..............................................29

Manual Master/Slave Switch........................................29

Power-Off Reset on Faulty Board..................................29

FAN Operation Check .................................................29

Use of Slave FS Board ................................................30

Service Restoration Flow.................................................30

General Flow of Service Restoration .............................30

Detailed Flow of Service Restoration.............................32

Checking PM Power Supply.................................32

Checking Power Supply System...........................32

Checking Key Board Power Supply ......................32

Checking Service Board Operation.......................32

Resetting or Replacing Board ..............................33

Checking Relationship between Configuration

Modification and the Fault .......................33

Restoring Configuration Data ..............................33

Collecting Fault Information................................34

Common Operations of BS Emergency Maintenance via

NM Software .........................................................34

Application Scenario of NM Software ............................34

Emergency Maintenance Operations Via LMT .................35

II Confidential and Proprietary Information of ZTE CORPORATION

Master/Slave Switchover and Reset .....................35

Perform Board Diagnosis Test .............................35

Exporting Operation Log of Node B ......................36

Exporting Current and History Alarms of Node

B .........................................................37

Exporting Foreground Log Information .................39

Emergency Maintenance Operations Via NetNu-

menM31(RAN)/OMMB ........................................40

Master/Slave Switch and Reset/Power-Off

Reset ...................................................40

Exporting Operation Log of Node B ......................42

Querying and Exporting Current Alarms of Node

B .........................................................45

Replacing Board ........................................................50

Maintemance Record Tables ............................53Daily Maintenance Record Table.......................................53

Monthly Maintenance Record Table...................................54

Semi-Yearly Maintenance Record Table .............................55

Emergency Handling Record Table....................................55

Module Replacement Record Table ...................................56

Figures ............................................................59

Tables .............................................................61

Glossary ..........................................................63

Confidential and Proprietary Information of ZTE CORPORATION III


This page is intentionally blank.

IV Confidential and Proprietary Information of ZTE CORPORATION

Preface

Purpose This manual introduces the maintenance method for ZTE SDR se-ries base station product ZXSDR B8200 GU360 Indoor GSM&UMTSDual Mode Baseband Unit, including routine maintenance, compo-nents replacing etc.

What is in ThisManual Chapter Summary

Chapter 1 Maintenance Overview Introduces the maintenanceclassification, maintenanceprinciple, maintenance analysismethod of ZXSDR B8200 GU360,as well as the precautions duringmaintenance of ZXSDR B8200GU360.

Chapter 2 Routine Maintenance Introduces the basic contentsof ZXSDR B8200 GU360 routinemaintenance.

Chapter 3 TroubleshootingExamples

Introduces some possible faultsin ZXSDR B8200 GU360 routinemaintenance, their causes andsolutions.

Chapter 4 Emergency Maintenance Introduces the method ofservice restoration and faultremoval when complete or partialbreakdown of ZXSDR B8200GU360 occurs.

Appendix A Replacing Board Introduces the precautions duringboard replacement.

Appendix B Maintenance RecordTables

Provides maintenance recordtables for reference.

Intended Reader Maintenance Engineer

Confidential and Proprietary Information of ZTE CORPORATION I



II Confidential and Proprietary Information of ZTE CORPORATION

C h a p t e r 1

Maintenance Overview

Table of ContentsRequirements for Maintenance Personnel ............................... 1Maintenance Principles ........................................................ 1Maintenance Category......................................................... 4Maintenance Analysis Methods ............................................. 5Attention Items .................................................................13

Requirements forMaintenance PersonnelZXSDR B8200 GU360 system maintenance engineer should:

have received equipment training and be qualified.

have mastered the basic knowledge of ZXSDR B8200 GU360.

have known the system structure of ZXSDR B8200 GU360 andthe basic functions of all boards.

have some basic network optimization and maintenanceknowledge.

Maintenance Principles

Overview

This section introduces the principles that maintenance person-nel must observe during ZXSDR B8200 GU360 maintenance. Anyoperation against the following principles may have a negative im-pact on system operation.

Confidential and Proprietary Information of ZTE CORPORATION 1


Rights Management

Personnel-specific user names and passwords should be assignedfor system login, operation and maintenance, to restrict the oper-ation rights of maintenance individuals and to easily locate opera-tion history through system log in case of system malfunction.

Different users are able to perform different groups of operations,depending on their levels and rights. Operation and maintenancesoftware classifies operators into four levels: root user, advanceduser, medium-level user, and ordinary user in descending order ofrights.

Root user, with highest level of right, can perform any oper-ations, including creating users, modifying user information,deleting users, setting rights and modifying system configura-tion. Change initial password of root user immediately afterlogging in to the system, for security of the system.

Advanced user has the same rights as a root user, exceptthat it cannot manage user accounts, add/delete boards andadd/delete local cells.

Medium-level user, with basic viewing right, can view alarmand system information. In addition, a medium-level user canonly perform limited types of configuration operations.

Ordinary user, with lowest right, can only view informationrather than perform any configuration operation.

Precautions:

Use right management function to set ordinary equipmentmaintenance personnel as medium-level users.

Do not log into the system as root user unless absolutely nec-essary.

Do not modify the network configuration of NMS Server andClient.

Do not run and operate any program not related to operationand maintenance on NMS Server or Client.

Follow general principles of network management to guardagainst any virus.

Data Observation

Perform data observation operation carefully when with largequantities of data to report. The operations include signalingtracing, running information observation, service observationof all users, and alarm refreshing. Excessive data report dur-ing data observation may cause system breakdown in extremecases.

Select appropriate time (low traffic period) for data observationoperation; take appropriate measures; save results in time andclear temporary data in time.

2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Maintenance Overview

Data Modification

Take care in modifying data, particularly wireless data.

Observe carefully whether there is any effect on system oper-ation after modifying data.

Be sure to perform backup before modifying any data, to en-sure rapid restoration when any problem occurs.

Do not perform data synchronization at rush hours (at 10 AMor 5 PM, Time varies from place to place).

Do not modify foreground database during daytime.

Data Synchronization

Be sure to backup data before modifying configuration.

Do not perform data synchronization in daytime unless neces-sary.

Check operation log to identify the source if finding any dataof an unknown source.

Man-Machine Command

Be careful in using commands that lead to foreground actions,including restart, reset, changeover, save, hardware test, soft-ware download and cell block/unblock.

Do not delete current alarms and history alarms unless abso-lutely necessary.

Be sure to lock background man-machine interface after main-tenance personnel leave operation and maintenance console,to avoid any accidents.

Board Operations

Do not reset a board, plug/unplug it or power it off unless ab-solutely necessary.

Prepare spare board before replacing a board. Confirm thereare sufficient technicians present for unexpected emergenciesin the case of major operations, such as changing versions ofimportant boards, or plugging, unplugging and replacing keyboards. Maintenance personnel working on boards in the fore-ground must have support from background personnel.

Always wear an antistatic wrist strap before operating boardson the rack and connect it to the rack before touching a board.Touch a metal object first to release static electricity on hands.



System Update

Perform upgrade at midnight when there is low traffic.

Keep the contact information of relevant personnel (like trans-mission and power supply) available to get their timely assis-tance when required.

Formulate upgrade plan in advance, covering all emergencymeasures.

Do not change procedures set forth in the plan, unless neces-sary.

Inform supervisors before upgrading for necessary technicalsupport.

Assign a person to closely monitor the system in case of anyfaults occurring since the upgrade.

Maintenance CategoryIn terms of maintenance content, maintenance falls into the fol-lowing categories.

Routine maintenance

Notification handling

Alarm handling

Troubleshooting

RoutineMaintenance

Routine maintenance is a periodical maintenance in which the reg-ular check of equipment operation is performed and the detectedproblems are handled. Routine maintenance enables problemsdiscovered and handled in time so that potential damage or faultis prevented.

NotificationHandling

Notification handling is to analyze the notification informationemerging during system operation, decide the notification nature,and take appropriate measures.

Alarm Handling Alarm handling is to analyze the alarm information emerging dur-ing system operation, decide the alarm nature, and take appropri-ate measures.

Troubleshooting Troubleshooting refers to the analysis, handling, and removal ofdetected faults.



Maintenance AnalysisMethods

LED Indicator Analysis

Analyze the board's running status by the indicator light's status.

For ZXSDR B8200 GU360, CC board, UBPG board, and BPC boardneed to be observed often.

Panel Indicators Description of PM panel indicators is shown in Table 1.

TABLE 1 PM PANEL INDICATOR DESCRIPTION

IndicatorName

Color Meaning Description

RUN Green Runningindicator

RUN indicator and ALM indicatorflashing alternately: board MMC isin module initializing.Flashing (0.3 s on, 0.3 s off): theboard is in normal running state.Off: board self-test fails.

ALM Red Alarmindicator

Quick flash (0.15 s on, 0.15 s off):critical or major alarm occurs.Slow flash (1 s on, 1 s off): minoror warning alarm occurs.Off: no board alarm occurs.

PWR Blue Power onindicatorwhich isonly onPM3 panel

Always on: board is power on.Off: board is power off.

Description of CC panel indicators is shown in Table 2.

TABLE 2 CC PANEL INDICATOR DESCRIPTION

IndicatorName


RUN Green RunningIndicator

RUN indicator andALM indicator flashingalternately: board MMC isin module initializing.Flashing (0.3 s on, 0.3 soff): the board is in normalrunning state.Off: board self-test fails.

ALM Red AlarmIndicator

Quick flash (0.15 s on, 0.15s off): critical or majoralarm occurs.Slow flash (1 s on, 1 s off):minor or warning alarm



IndicatorName


occurs.Off: no board alarm occurs.

E0S Green E1/T1 StatusIndicator(Link 0-3)

Alternate flash for differentlinks; the max 4 flashesper second; 0.125 s on,0.125 s off.The first second: one flashmeans Link 0 is normal andOff means Link 0 is not inuse.The third second: twoflashes means Link 1 isnormal and Off means Link1 is not in use.The fifth second: threeflashes means Link 2 isnormal and Off means Link2 is not in use.The seventh second: fourflashes means Link 3 isnormal and Off means Link3 is not in use.Recycle. Each cycle lastsfor eight seconds.


Ditto


Ditto


Ditto

MS Green Master/SlaveIndicator

On: the board is in masterstate.Off: the board is in slavestate.

REF Green GPS AntennaState or 2MHz State,Connectionstate of SMAInterface oncorrespond-ing panel

Always On: antenna feederis normal.Always Off: antenna feederand satellite are normal, ininitialization state.Slow Flash (1.5 s on, 1.5s off): antenna feeder isbroken.Quick Flash (3 s on, 3 soff): antenna feeder isnormal but cannot receivesatellite signal.Slowest Flash (2.5 s on,2.5 s off): antenna shortcircuitQuickest Flash (70 ms on,70 ms off): no message isreceived at the initializationstage.



IndicatorName


ETH0 Green ABIS/IubInterface LinkState

On: physical link ofABIS/Iub network interface(optical or electrical) isnormal.Off: physical link ofABIS/Iub network interfaceis broken.Flashing: there is receivedor sended data at ABIS/Iubnetwork interface.

DEBUG/CAS-/LMT

Green Link State ofDEBUG/CAS-/LMT NetworkInterface

On: physical link ofDBG/CAS/OMC networkinterface is normal.Off: physical link ofDBG/CAS/OMC networkinterface is broken.Flashing: there is receivedor sended data atDBG/CAS/OMC networkinterface.

UBPG panel is illustrated in Table 3.

TABLE 3 UBPG PANEL INDICATOR DESCRIPTION

Indi-catorName



Flashing (0.3 s on 0.3 s off):the board is in normal runningstate.Off: board self-test fails.


Quick flash (0.15 s on0.15 soff): critical or major alarmoccurs.Slow flash (1 s on1 s off):minor or warning alarm occurs.Off: no board alarm occurs.

CST Green CPU RunningIndicator

Flashing at frequency of 1 Hz:main version has been bootedsuccessfully.

SCS Green System ClockIndicator

Always onsystem clock is innormal state.Offsystem clock is in abnormalstate.



Indi-catorName


LS Green If there areoptical inter-facesthe linkstate of op-tical commu-nicating withRRUIf there is nooptical inter-facethe linkstate of back-board

Flashing at frequency of 8Hzand flashing ordinally atdifferent time, the max 3flashes per secondThe first second: oneflash means Link 0optical/backboard link isnormal and Off means Link 0is faulty.The fourth second: twoflashes means Link 1optical/backboard link isnormal and Off means Link 1is faulty.The seventh second: threeflashes means Link 2optical/backboard link isnormal and Off means Link 2is faulty.Recycle. Each cycle lasts fornine seconds.

SS Green If there areoptical in-terfacesex-istence of op-tical signal atoptical inter-faceIf there is nooptical inter-facephysicallink state ofGTP in back-board

Flashing at frequency of 8Hzand flashing ordinally atdifferent time, the max 3flashes per secondThe first second: one flashmeans there is signal at Link0 optical/backboard link andOff means there is no signal atLink 0.The fourth second: two flashesmeans there is signal at Link1 optical/backboard link andOff means there is no signal atLink 1.The seventh second: threeflashes means there is signalat Link 2 optical/backboardlink and Off means there is nosignal at Link 2.Recycle. Each cycle lasts fornine seconds.

Description of BPC panel indicators is shown in Table 4.

TABLE 4 BPC PANEL INDICATOR DESCRIPTION

Indi-catorName



RUN indicator and ALMindicator flashing alternately:board MMC is in moduleinitializing.Flashing (0.3 s on, 0.3 s off):the board is in normal running



Indi-catorName


state.Off: board self-test fails.


Quick flash (0.15 s on, 0.15 soff): critical or major alarmoccurs.Slow flash (1 s on, 1 s off):minor or warning alarmoccurs.Off: no board alarm occurs.

Description of FS panel indicators is shown in Table 5.

TABLE 5 FS PANEL INDICATOR DESCRIPTION

IndicatorName



RUN indicator and ALM indicatorflashing alternately: board MMCis in module initializing.Flashing (0.3 s on, 0.3 s off):the board is in normal runningstate.Off: board self-test fails.


Quick flash (0.15 s on, 0.15s off): critical or major alarmoccurs.Slow flash (1 s on, 1 s off):minor or warning alarm occurs.Off: no board alarm occurs.

SCS ClockIndicator

For possible future use

FLS ForwardLinkIndicator


RLS ReverseLinkIndicator


Description of SA panel indicators is shown in Table 6.

TABLE 6 SA PANEL INDICATOR DESCRIPTION

IndicatorName



RUN indicator andALM indicator flashingalternately: board MMC isin module initializing.Flashing (0.3 s on, 0.3 s



IndicatorName


off): the board is in normalrunning state.Off: board self-test fails.


Quick flash (0.15 s on, 0.15s off): critical or majoralarm occurs.Slow flash (1 s on, 1 s off):minor or warning alarmoccurs.Off: no board alarm occurs.

Description of SE panel indicators is shown in Table 7.

TABLE 7 SE PANEL INDICATOR DESCRIPTION

IndicatorName



RUN indicator andALM indicator flashingalternately: board MMC isin module initializing.Flashing (0.3 s on, 0.3 soff): the board is in normalrunning state.Off: board self-test fails.


Quick flash (0.15 s on, 0.15s off): critical or majoralarm occurs.Slow flash (1 s on, 1 s off):minor or warning alarmoccurs.Off: no board alarm occurs.

The indicators on TAM panel are described in Table 8.

TABLE 8 TAM PANEL INDICATOR EXPLANATION

N-a-me

Col-or

Meaning Description

RU-N

gree-n

Runningindicator

Flashing(on for 0.3 s, off for 0.3 s): theboard is running properly.

Slowly flashing(on for 1.5 s, off for 1.5s): indicating the indicator disconnectswith CC.

Quickly Flashing(on for 70 ms, off for 70ms): the board is downloading versions orthe process is powered on.



N-a-me

Col-or

Meaning Description

AL-M

red Alarmindicator

Quickly Flashing (on for 0.15s, off for0.15s) means the alarm is critical or major.

Slowly Flashing (on for 1s, off for 1s)means the alarm is ordinary or minor.

No Flashing means the board is runningproperly.

Signaling Tracing Analysis

Signaling tracing analysis is to check whether signaling flow is cor-rect. All services have their own signaling flows. When a service isabnormal, it is acceptable to diagnose system problems by view-ing differences between current flow and correct flow.

Important workflow, for ZXSDR B8200 GU360, includes: cellsetup, common transmission channel setup, paging, randomaccess, system information update and wireless link setup.

Alarm Log Analysis

Query the history alarms and current alarms at background inter-face, and analyze the equipment's running status.

Instrument and Meter Analysis

Commonly-used instruments and meters in routine maintenanceinclude signaling meters, line testers and power meters.

Signaling MeterAnalysis

Signaling meter is to monitor signaling interaction betweenBS andRNC in real time. The connection mode of signaling meter with theequipment is as shown in Figure 1.



FIGURE 1 APPLICATION OF SIGNALING METER AT RNS

Signaling meter analysis allows monitoring signaling flows be-tween BS, RNC and UE in real time and saving results.

Drive TestInstrument

Drive test instrument has the following functions.

To measure information of common channels.

To measure related items in coverage area, such as locations,signal strength and signal quality.

To measure energy of each synchronization code in each times-lot on synchronization channel.

To measure channel power.

To measure scramble of the cell.

Comparison by Replacement

Comparison by replacement is replacing the suspected faultyboards or cables with normal boards or cables, and observingwhether the fault disappears after the replacement.

Refer to Appendix for the replacing method of boards.

Normally, field engineers judge the faulty board by other analysismethod at first, then use the replacement analysis to confirm theresult. The analysis method includes:

Board resource block

This method is applicable to baseband processing board.

At first, block the suspected board and observe the system'sworking status. If the system recovers, the fault probably liesin the baseband processing board or board interface. It is ad-



visable to replace the board, unblock the ports and take furthertest.

Board replacement

This method is applicable to baseband processing board, in-terface board, and etc. Use normal boards to replace the sus-pected board.

Cable replacement

The cables which may be faulty include fiber cable, E1 cable,lightning arrester cable (for external connection) and interfaceboard cable.

For example, a fiber interface is obstructed. The field engineerscan remove the fiber cable and self-loop the fiber interface. Ifthe fiber interface is abnormal in the self-loop, the interfaceis faulty, and the field engineer can connect the fiber cable toother normal fiber interfaces and modify the configuration. Ifthe fiber interface is normal in the self-loop, replace the fibercable or check the opposite equipment.

Laser:

It is forbidden to aim the fiber at somebody's eyes. The laser inthe fiber cable is probable to make people blind if looking straight.

Attention Items

Personnel Qualifications

Maintenance personnel must receive pre-service training to learnnecessary knowledge about the equipment and related network,and they must follow instructions given in related manuals ofZXSDR B8200 GU360 to conduct maintenance.

Maintenance personnel must have earnest attitudes and high com-petence.

Maintenance Management

Make a complete set of equipment room maintenance regulationsto standardize routine work of the maintenance personnel. Forbidnon-maintenance management personnel to perform any mainte-nance operation.

Make a detailed on-duty log to provide detailed records about sys-tem running, version status, data change, upgrade and problemhandling for easy analysis and troubleshooting once any fault oc-curs.



Make a work shift record to clearly define responsibilities.

Do not play games or access the Internet through computer ter-minal. Do not install, run and copy any other software not relatedto the system at the terminal. Do not use the computer terminalfor other purposes.

Set NM passwords by level. Manage them strictly and change themperiodically to ensure them only accessible to maintenance per-sonnel.

Data Maintenance

Do not reset the equipment, load or change any data unless ab-solutely necessary. Do not change background database at will.

Backup the data before making any changes. Do not deletebackup data after changing data until observation period (usuallyone week) expires and be sure that the equipment is runningnormally.

Equipment Environment

Maintain normal temperature/humidity in the equipment room.Keep the environment tidy and clean, free from dust and mois-ture. Keep rodents or insects out of the equipment room.

Ensure that primary power of the system is stable and reliable,and check system grounding and lightning protection ground peri-odically. Check lightning protection system to Confirm all facilitiesare in good condition, especially before storm seasons and afterthunderstorms.

The equipment room must have sufficient luminance compliantwith relevant standards. Repair damaged lamps in time and Con-firm that light reaches all around the equipment room.

Tools and Instruments

All common-use tools, instruments and meters must be available.

Instruments and meters must be subject to periodic checking andcalibration to ensure function availability and accuracy.

Spare Parts

Check spare materials and parts regularly to ensure sufficientstocks and to prevent them from mold.



Store spare materials and parts and faulty ones separately. Markthem properly for easy identification.

Technical Documents

Place technical documents and equipment software by categoriesin specified place.

Technical Support

Treat with the faults in time once a fault occurs. Please contact ZTECorporation once the fault is too troublesome and no maintenancepersonnel can solve it.

You can contact the local office.

You can dial the hotline of ZTE global customer support center.The phone numbers are:

800-830-1118

400-830-1118

860755-26770800

You can log in ZTE technical support website (http://ensup-port.zte.com.cn) to submit technical support application.

It is recommended to mark the contact approach of ZTE local officein an eye-catching position of the equipment room, and notify allmaintenance personnel. Make sure that the contact approach islatest.


C h a p t e r 2

Routine Maintenance

Table of ContentsOverview..........................................................................17Daily Maintenance Items ....................................................18Monthly Maintenance Items ................................................18Semi-Yearly Maintenance Items...........................................19Other Recommended Maintenance Items ..............................20

OverviewRoutine maintenance is the periodical and preventive check ofequipment. This check can ensure the equipment in reliablestatus. Routine maintenance includes the following aspects:

Routine Test

Follow the technical specifications to check and test the equip-ment's running status, functions, key performance index andhardware usability regularly with specified meters, instrumentsand operations.

Routine Check and Cleaning

Check the hardware of BS and its accessories one by one. Ad-just and replace the faulty parts to ensure all hardware in goodcondition. Periodical cleaning and maintenance is necessary toboth main equipment and peripheral equipment.

It is recommended to make a reasonable periodical maintenanceplan and carry out the plan strictly.

Note:

The following sections describes some routine maintenance items.These items may be not applicable to every situation. Customerscan refer to these contents to make a practical routine mainte-nance plan.



Daily Maintenance ItemsThe daily maintenance items of ZXSDR B8200 GU360 equipmentare shown in Table 9.

TABLE 9 DAILY MAINTENANCE ITEMS

Item Sub-item Contents

Alarm handling Check all alarms atNM terminal from lastcheck to current time,and handle by alarmlevel.

Alarms and notifica-tions check

Notification handling Usually, analyze no-tifications that fre-quently occur andignore common ones.

Common faults Handle common faultssuch as transmissionfault and board fault.

Troubleshooting

User complaints Analyze and handlenetwork quality prob-lem that users com-plain about.

Monthly Maintenance ItemsThe monthly maintenance items of ZXSDR B8200 GU360 equip-ment are shown in Table 10.

TABLE 10 MONTHLY MAINTENANCE ITEMS

Item Sub-item Contents Remarks

Radio Parame-ter

Engineering pa-rameter

Verify the BSconfigurationparameters

Update the pa-rameter dy-namically. Theparameter is re-quired to bekept for at leasttwo years.

Main equipmentand accessoriescheck

Clean thecabinet;

Check thecabling rack;

CheckE1/T1/Fiberand variousinterfaces;

Check theequipment'sindicators;

BS equipment


Chapter 2 Routine Maintenance


Check FANstatus;

Clean dust filter

Power System Check power;

Check battery

Spare PartCheck

Check spareboards;

Check sparecabinets;

Check otherspare parts.

Semi-Yearly MaintenanceItemsThe semiyearly maintenance items of ZXSDR B8200 GU360equipment are shown in Table 11.

TABLE 11 SEMI-YEARLY MAINTENANCE ITEMS


Lightninggrounding

Lightninggrounding

Checkprotectionground of theequipment;

Checkprotectionground of theequipmentroom;

Checkgrounding trunkline of BS;

Check lightninggrounding ofthe building;

Test each typeof groundingresistance.

Check all itemsbefore and aftera natural disas-ter



Other RecommendedMaintenance ItemsSome other recommended maintenance items and their period areshown in Table 12.

TABLE 12 OTHER MAINTENANCE ITEMS

Item Content RecommendedPeriod

Storage Battery Discharge capacitytest

Yearly

Environment Safety Check hidden safetyhazards;

Check fireextinguishers;

Check the equipmentprotection status.

Semi-Yearly


C h a p t e r 3

TroubleshootingExamples

Table of ContentsOverview..........................................................................21System Monitoring ............................................................21User Complaints ................................................................22

OverviewThe possible faults that may occur during ZXSDR B8200 GU360routine maintenance are as shown in Table 13.

TABLE 13 POSSIBLE FAULTS

Category Fault

High CPU utilizationSystem monitoring

Decreased BS coverage radius

Low call completion rate

Poor call quality

Customer complaint

Slow Internet access

System Monitoring

High CPU Utilization

Symptom andEffect

The alarm man-machine interface of the operation and mainte-nance (O&M) console has CPU utilization alarm reported, or CPUutilization exceeds normal value for a long time as displayed atperformance management man-machine interface.

High CPU utilization is of great concern. Processing capability ofthe system decreases if CPU of CC board is at a high utilization



for a long time. It results in sharp rise of call loss and may causememory exhaustion or system breakdown.

Cause Rise of CPU utilization of a board (particularly CC board) may resultfrom:

The system is busy currently, for example, high traffic.

Too many measurement tasks are set, and there are moremeasurement report messages.

The system has a local emergency fault, causing a large num-ber of alarms reported.

Handling Analyze the cause and take appropriate measures in case of highCPU utilization ratio for a long time.

Locate the fault and isolate it by blocking failed board and partsor using other methods if there is a large amount of burst alarmreports.

Adjust measurement strategy properly if there are too manymeasurement messages reported, for example, cancel someless important measurement tasks or change the period whenperforming measurement tasks.

Decreased BS Coverage Radius

Symptom andEffect

Call quality at the edge of cell decreases, and measurement withinstruments shows that coverage radius of BS signals decreases.

Cause Some radio parameters are set improperly, particularly pilotchannel transmitting power and downlink transmitting power,which affect actual BS coverage.

Surrounding landform and geographical feature changes, forexample, urban construction, also affect actual coverage.

Electromagnetic interference in space causes pilot pollution.

RRU system gets faulty.

Handling Conduct an on-site survey and detailed spectrum test near the site,and configure radio parameters again based on ambient charac-teristics and test result. It is better to let professional networkoptimization personnel perform this task.

User Complaints

Low Call Completion Rate

Symptom andEffect

Users complain that call completion rate (successfully connectedto the called party) decreases significantly and calls cannot be con-nected at all in extreme cases.


Chapter 3 Troubleshooting Examples

Cause Call completion rate is a basic index to evaluate overall perfor-mance of the system. A great variety of factors may affect it,including:

Boards and parts of access side equipment (including BS andRNC) fail, or parts of core network side equipment (such asMSC) fail, so fewer resources are available and users' accessrequests are mostly rejected.

Software version mismatch exists among some equipment orparts, for operation mistakes at system upgrade or versionupdate. It affects normal working of the system, particularlyputting interactive flow of important signaling or message intodisorder. As a result, user access becomes difficult.

Early-stage network planning or network construction is notperfect or resource configuration is incorrect, so allocation ofsystem service resources is not reasonable. There are insuf-ficient resources in some areas, particularly those with largetraffic, which reduce success rate of user access.

User access is more likely to fail in the propagation environ-ment with electromagnetic interference (for example, pilot pol-lution) and SNR downgrade.

Handling 1. Set statistical tasks on performance statistics man-machine in-terface of operation and maintenance background, to measurecall completion rate in user complaint area, and compare theresult with old statistical data.

2. There is a large possibility of external electromagnetic inter-ference if statistical indices do not decrease significantly.

i. Use a radio signaling analyzer to observe radio signalingprocess, and record characteristics of abnormal interrup-tions.

ii. Use a spectrum analyzer to scan frequency band in use totest whether any external electromagnetic contaminationexists.

iii. Locate interference source and try to eliminate it.

3. Check equipment faults, resource configurations and softwareversions if statistical indices decrease significantly.

i. Determine whether the whole network, a BS, or a sectoris affected according to problem area reported by the userfirst.

ii. Check current alarms and history alarms. Check work-ing status of equipment parts, transmission equipment andclock source. Eliminate any fault found.

iii. Observe utilization of related sources continuously, for ex-ample, board CPU utilization, link load, cell traffic, and radiochannel utilization. Adjust resource configuration data andexpand capacity of the equipment if necessary.

iv. Check software/hardware versions of each equipment andpart, to eliminate version mismatch.

4. It may be a sign that the system is to be down if performanceindices of the whole network degrade. Handle the problemimmediately, and report it to ZTE in time.



Poor Call Quality

Symptom andEffect

The common symptoms of poor conversation quality are:

Call Drop

There is frequent abnormal interruption during conversation ofusers.

One-Way Conversation

One party cannot hear the other party during the conversation.

Intermittent Voice

The voice is intermittent when users are in conversation.

Cause Mobile terminal has poor demodulation performance (receivingsensitivity), and fluctuation of receiving field strength affectsconversation quality.

Either or both parties of the call are on edge of cell(s) or the callis blocked by landform or buildings, so signal field strength isweak and fluctuates greatly. They result in a high frame errorrate and affecting voice quality.

Strong electromagnetic interference is present in the space, in-cluding pilot pollution, carrier interference, and abnormal sec-tor power of adjacent BS. They result in decreased voice qual-ity.

Pilot Pollution

Surplus pilot frequencies become a strong interferencesource when there are three or more pilot frequencies withnearly equal magnitude in coverage area.

Carrier Interference

It is strong signal interference if a frequency close to theBS carrier frequency exists in the BS coverage area. Theinterference may be continuous or in a burst.

Abnormal sector power of adjacent BS

Power output of sectors of adjacent BS is fluctuating of-ten at amplitude over 3 dB, producing interference to over-lapped soft handover area of corresponding sector of otherBS or adjacent BS.

Users are moving during the conversation. Signals are seri-ously blocked suddenly, and air links undergo fast fading orreceiving signal strength undergoes sudden change when thereare obstacles in the surrounding. They affect continuity ofvoice because rapid power control function cannot effectivelyfollow up.

Resources occupied during the conversation, such as carrierfrequency, link, board, switching network and transmissionequipment have faults and do not work stably. They affectstability of the conversation.

Data configurations are incorrect or versions of hardware andsoftware do not match. They affect stability of the conversa-tion.


Chapter 3 Troubleshooting Examples

Handling 1. Check mobile terminal used for conversation. Use multiple ter-minals of different models for comparison if possible, to deter-mine whether the terminal has any problem.

2. Test signal field strength in conversation area to evaluate cov-erage effect. Optimize the network if the area has weak signalfield strength.

3. Monitor with instruments to see whether any pilot pollution orcarrier interference exists in the region. Find out interferencesource and handle it properly if so.

4. Query recent downlink power output status of all adjacent BS atoperation and maintenance console. Check the correspondingBS and eliminate related fault if finding any abnormal poweroutput.

5. Usual reason for voice quality degradation only occurring dur-ing motion is that power control mechanism in special geo-graphical and ambient system cannot accommodate the appli-cation. There is need to optimize the network in this case, forexample, by adjusting the antenna.

6. Use a signaling monitoring meter or start signaling tracing atoperation and maintenance background, and perform on-sitedialing test, to monitor signaling flow. Query history alarmsand current alarms simultaneously as a supplement to locatethe fault. Check corresponding data configuration and hard-ware/software versions to eliminate the fault if locating thefault at a specific board or part.

Slow Internet Access

Symptom andEffect

Connection speed is relatively slow when users access the Internetthrough packet service.

Cause Signals on downlink radio link are of poor quality. For exam-ple, received power at the edge is below -90 dBm, or receivedpower is high but FER is above 10%, which limits rate of theforward link.

Fail to provide the bandwidth that high-speed download re-quires because system resources are insufficient.

The equipment other than ZXSDR B8200 GU360 fails.

Handling 1. Use instruments to test received power and BER of downlinkradio link, and perform network optimization if required.

2. View current occupation and allocation of system resources,such as carrier frequencies, links, boards and switching net-work, to find out bottleneck of resources. Upgrade the equip-ment or expand capacity if condition permits.


C h a p t e r 4

Emergency Maintenance

Table of ContentsOverview..........................................................................27Fault Evaluation.................................................................27Service Impact of the Fault .................................................28Fault Report Flow...............................................................28Emergency Fault Handling ..................................................29Service Restoration Flow ....................................................30Common Operations of BS Emergency Maintenance via NMSoftware ..........................................................................34

OverviewThis chapter helps maintenance personnel to restore service andhandle faults when complete or partial breakdown of ZXSDR B8200GU360 equipment occurs.

The emergency handling method introduced in this chapter is ap-plicable to the case in which complete or partial service interrup-tion suddenly occurs.

Fault Evaluation

Evaluation Standard of CompleteEquipment Breakdown

If maintenance personnel observes the critical or major alarms (aslisted in Table 14) on NetNumenM31(RAN) network managementsystem, fault nature can be determined as complete breakdown ofZXSDR B8200 GU360.



TABLE 14 EVALUATION STANDARD OF COMPLETE EQUIPMENT BREAKDOWN

NetNu-menM31(RAN)Alarm Code

Alarm Description Remark

198084117 Application softwaremonitoring alarm

None

198084123 Board communicationlink is interrupted.

None

198084012 Board hardware fault None

198084263 RRU LOS alarm None

198084019 E1/T1 LOS (Loss OfSignal) alarm

Transmission mediumis E1 or T1.

Note:

It is recommended to use NetNumenM31(RAN) NM system to man-age the BS. OMMB BS configuration function can be performed viathe remotely connected NetNumenM31(RAN).

Caution:

O&M personnel should have a basic knowledge of the operationand maintenance of ZXSDR B8200 GU360 equipment, as well asequipment configuration, related alarm codes and handling meth-ods.

Service Impact of the FaultThe service impact of ZXSDR B8200 GU360 fault involves:

Failure in receiving RNC signaling

Repeated cell setup failure

Service access failure despite cell setup success

Fault Report FlowMaintenance personnel should report the fault in a timely manneras required by related regulations.


Chapter 4 Emergency Maintenance

Emergency Fault HandlingZXSDR B8200 GU360 adopts the redundancy backup of clock, I/Qexchange, and transmission. When the redundant slave board isnot faulty:

If one CC board is faulty, an automatic cold switch will occur.Service interruption lasts for about 10 s.

If one FS board is faulty, operation of the RRU connected withthe FS will be affected. In the case of ring networking, an auto-matic switch to another FS I/Q occurs, and service interruptionlasts for about 10 s.

In the case of transmission breakdown, a manual switch is re-quired. The switch time is within 30 s.

Manual Master/Slave Switch

Perform manual master/slave switch when a fault occurs in trans-mission or clock.

1. Log in the NetNumenM31(RAN) NM of ZXSDR B8200 GU360equipment.

2. Right-click the master CC board. A shortcut menu appears.Initiate master/slave switch.

Power-Off Reset on Faulty Board

1. Log in the NetNumenM31(RAN) NM of ZXSDR B8200 GU360equipment.

2. Right-click the faulty board. A shortcut menu appears. Performpower-off reset.

FAN Operation Check

1. Log in the LMT of ZXSDR B8200 GU360 equipment.

2. Right-click the SA/SE (site alarm extender) and RTR/DTR(dual-mode transceiver board)/FCE board. The shortcutmenu appears. Initiate environment information query to seewhether the temperature is in normal range (usually below 55C).



Use of Slave FS Board

In the load sharing mode, if one FS board is faulty, it will be outof use, and the slave FS board will be used in non-load sharingmode.

1. Plug out the input fiber of the faulty FS board, and connect thefiber to the slave FS board.

2. Log in the LMT/OMMB/ NetNumenM31(RAN) NM of ZXSDRB8200 GU360 equipment.

3. Delete the radio resource of the faulty FS board. Re-configurethe resource on the normal FS board.

Service Restoration FlowPlease dial the ZTE 800 service hotline or contact the technicalsupport engineers at local ZTE office before performing servicerestoration. Maintenance personnel should operation under theguidance of professional engineers.

Contact information of technical support from ZTE is listed below.

ZTE global customer service center hotline:

86-0755-26770800

800-8301118

400-8301118

Complaint Hotline: 86-0755-26771776

E-Mail: [email protected]

General Flow of Service Restoration

General flow of service restoration is shown in Figure 2.



FIGURE 2 GENERAL FLOW OF SERVICE RESTORATION



Detailed Flow of Service Restoration

Checking PM Power Supply

Context Check whether the cabinet power supply is normal by the followingmethod.

Steps 1. At the real rack, check the RUN indicator on PM board.

2. If the indicator is green, PM power supply is normal. Otherwise,check PM board.

END OF STEPS

Checking Power Supply System

Context Abnormal cabinet power supply is usually caused by fault in thepower supply system of the equipment room. In this case, main-tenance personnel should restore the fault by taking the followingmeasures.

Steps 1. Switch off all the power supply on the power distribution panelof the cabinet to ensure safety.

2. Troubleshoot the power supply system of the equipment room.

3. Restart the power supply system.

END OF STEPS

Checking Key Board Power Supply

Prerequisites The cabinet power supply is normal

Steps 1. Check the power supply of key boards.

i. At the real rack, check the RUN indicator on CC board. Ifthe indicator is not OFF, power supply of CC board is normal.

ii. At the real rack, check the RUN indicator on SA/SE board.If the indicator is not OFF, power supply of SA/SE board isnormal.

2. If the power supply of key boards is abnormal (RUN indica-tor in OFF status), contact ZTE corporation to obtain technicalsupport. Do not perform any operation before location of thefault cause.

END OF STEPS

Checking Service Board Operation

Prerequisites The cabinet power supply is normal.



Context

Steps 1. Check the power supply of service boards.

i. At the real rack, check the RUN indicator on FS board. Ifthe indicator is not OFF, power supply of FS board is normal.

ii. At the real rack, check the RUN indicator on BPC board.If the indicator is not OFF, power supply of BPC board isnormal.

iii. At the real rack, check the RUN indicator on UBPG board.If the indicator is not OFF, power supply of UBPG board isnormal.

2. Check whether the corresponding board has been configuredin NetNumenM31(RAN).

i. If the board has been configured and its RUN indicator is inOFF status, unplug the board. Then insert the board back.

ii. If the fault persists, replace the board.

END OF STEPS

Resetting or Replacing Board

Prerequisites A certain board is down. The RUN indicator status of the boardsignifies abnormal board operation, and Alarm indicator flasheson and off.

Steps 1. Access the board via NetNumenM31(RAN) and view currentalarms. Troubleshoot the fault according to the related alarmcode reference manual.

END OF STEPS

Checking Relationship between ConfigurationModification and the Fault

Context If configuration data are unreasonable or software/patch upload isincorrect, board or system failure occurs after loading such con-figuration data or software.

Steps 1. Use NetNumenM31(RAN) operation log to perform log analysisand comparison.

END OF STEPS

Restoring Configuration Data

Prerequisites The fault is determined as caused by unreasonable data configu-ration

Steps 1. Fetch the backup data created before the configuration opera-tion.



2. Restore the data formerly configured, or restore the correctconfiguration data under the guide of ZTE technical supportengineers.

END OF STEPS

Collecting Fault Information

Context No matter whether the fault is successfully handled, maintenancepersonnel should collect fault information, which is convenient forfurther analysis.

Export the operation log of Node B.

Export the current and history alarms of Node B.

Export the service failure statistics of Node B.

Export all the information under the CC-1 and CC-2 Log direc-tory of Node B.

Export the exceptional probe information of Node B.

Common Operations of BSEmergency Maintenance viaNM Software

Application Scenario of NM Software

The NM software of ZXSDR B8200 GU360 includes LMT, OMMB,and NetNumenM31 (RAN), via which BS maintenance personnelmay perform maintenance operations.

Local maintenance operations can be performed on the singleZTE BS via the corresponding LMT software.

Maintenance operations on ZTE BS in UMTS network can beperformed via OMMB software. The BS configuration functionof OMMB can be performed via the remotely connected NetNu-menM31 (RAN). Common OMMB operations are also applicableto NetNumenM31 (RAN).

Maintenance operations can be performed on various kinds ofZTE BS in 2G/3G network via the NetNumenM31 (RAN) soft-ware. It is recommended to use NetNumenM31 (RAN) to man-age the BS.



Emergency Maintenance OperationsVia LMT

Master/Slave Switchover and Reset

Short Description To perform master/slave switch, or reset of the board via LMT.

Prerequisites LMT has been logged in.

Link between LMT and ZXSDR BS8700 is normal.

Steps 1. On ZXSDR BS8700 interface, right-Click on CC board and theshortcut menu appears. Click on Master/Slave Switchoveror Reset. The related interface is shown in Figure 3.

FIGURE 3 MASTER/SLAVE SWITCHOVER AND RESET

END OF STEPS

Perform Board Diagnosis Test

Short Description To perform board diagnosis test via LMT

Prerequisites LMT DMS interface is open.


Steps 1. On LMT DMS interface, double-click on Board Diagnosis Teston Maintain navigation tree. Board Diagnosis Test inter-face appears.

2. Right-Click on SA, or other board and the shortcut menu ap-pears. Click on Start Test. The related interface is shown inFigure 4.



FIGURE 4 BOARD DIAGNOSIS TEST

END OF STEPS

Exporting Operation Log of Node B

Short Description To export Node B operation log via LMT

Prerequisites LMT EOMS interface is open.


Steps 1. On LMT EOMS interface, click on System > Log > Export, asshown in Figure 5.

FIGURE 5 EXPORT OPERATION LOG OF NODE B

END OF STEPS



Exporting Current and History Alarms of Node B

Short Description To export current and history alarms via LMT

Prerequisites LMT EFMS interface is open.


Context

Note:

This topic takes exporting history alarms as an example. The op-eration of exporting current alarms is basically the same with thatof exporting history alarms.

Steps 1. Open History Alarms interface. Right-Click on the alarm andthe shortcut menu appears, as shown in Figure 6. Click ExportRecords.

FIGURE 6 EXPORT HISTORY ALARMS

2. Fill in file name and select save path to save history alarms, asshown in Figure 7.



FIGURE 7 SAVE HISTORY ALARMS

3. Click Save. An interface appears to indicate file save success,as shown in Figure 8.



FIGURE 8 SAVE SUCCESS

END OF STEPS

Exporting Foreground Log Information

Short Description To export foreground log information via LMT

Prerequisites LMT has been logged in.


Steps 1. FTP login to the foreground. No user name and password (Null)are required. The command format is ftp+BS IP.

2. Execute the ftp>cd /ROOT/log command to open the logdirectory.

3. Fetch the files under the log directory to local computer via ftp.

The related interface is shown in Figure 9.



FIGURE 9 EXPORT FOREGROUND LOG INFORMATION

END OF STEPS

Emergency Maintenance OperationsVia NetNumenM31(RAN)/OMMB

Master/Slave Switch and Reset/Power-Off Reset

Short Description To perform master/slave switch, reset, or power-off reset of theboard via NetNumenM31(RAN)/OMMB

Prerequisites NetNumenM31(RAN)/OMMB has been logged in.

Link between NetNumenM31(RAN)/OMMB and ZXSDR B8200GU360 is normal.

Steps 1. Open ZXSDR B8200 GU360 main rack view. Right-Click on CCboard and the interface that appears is shown in Figure 10.



FIGURE 10 MASTER/SLAVE SWITCH OF CC BOARD

2. Perform master/slave switch.

If merely one CC-1 board is configured. Master/SlaveSwitch is unavailable in the shortcut menu, as shown inFigure 11.

FIGURE 11 MASTER/SLAVE SWITCH UNAVAILABLE

Master/Slave Switch would be available only when twoCC boards are configured (one in master status and theother in slave status). As shown in Figure 12, CC-1 boardis in master status; CC-2 board is in slave status; andMas-ter/Slave Switch is available in the shortcut menu.



FIGURE 12 MASTER/SLAVE SWITCH AVAILABLE

END OF STEPS

Exporting Operation Log of Node B

Short Description To export Node B operation log via NetNumenM31(RAN)/OMMB



Steps 1. On NM interface, click on View > Log Management to openLog Management interface, as shown in Figure 13.



FIGURE 13 LOG MANAGEMENT INTERFACE

2. Click Operation Log on Query Log tree in the left pane. Click

the (Query and Export Result According to CurrentCondition) icon, as shown in Figure 14.

FIGURE 14 QUERY AND EXPORT RESULT ACCORDING TO CURRENT CONDITION

3. In the interface that appears, select the save path and file type,as shown in Figure 15. The default save path is the client logfolder.



FIGURE 15 SAVE THE EXPORTED LOG

Available file types are shown in Figure 16.

FIGURE 16 AVAILABLE FILE TYPES

4. Click Save. The interface that prompts log export success isshown in Figure 17.

FIGURE 17 EXPORT SUCCESS

END OF STEPS



Querying and Exporting Current Alarms of Node B

Short Description To query and export Node B current alarms via NetNu-menM31(RAN)/OMMB. The two operation methods are listedbelow.



Steps 1. On NM interface, click on View > Fault Management to openFault Management interface.Method One

i. Right-click the NE to be queried in the left pane. The short-cut menu appears. Click on Show Current Object Alarm,as shown in Figure 18.

FIGURE 18 SHOW CURRENT OBJECT ALARM

Query result is shown in Figure 19.



FIGURE 19 QUERY RESULT

ii. Click the (Export) icon to export data. Select the savepath. Click Save to save the current alarms of Node B. Therelated interface is shown in Figure 20.

FIGURE 20 SAVE CURRENT ALARMS

Method Two

i. Click Query > View Current Alarms, as shown in Figure21.



FIGURE 21 QUERY CURRENT ALARMS

ii. Current Alarm Query Conditions interface appears, asshown in Figure 22.

FIGURE 22 SET CURRENT ALARM QUERY CONDITIONS

iii. Click the (Quick Search) icon on Current AlarmQuery Conditions interface, as shown in Figure 23.

FIGURE 23 QUICK SEARCH

iv. Query Current Alarm interface appears. Specify thequery conditions, as shown in Figure 24. If Visibilitycheck box is ticked, the data filtered away by Alarm UserFiltering Rule and Alarm Global Filtering Rule will be madevisible and can be queried.



FIGURE 24 SPECIFY QUERY CONDITION

v. Specify the location of the NE to be queried, as shown inFigure 25. Click OK to query the current alarms of theselected NE.



FIGURE 25 SPECIFY NE LOCATION

The query result is shown in Figure 26.

FIGURE 26 QUERY RESULT

vi. Click the (Export) icon to export data. Select the savepath. Click Save to save the current alarms of Node B NE.The related interface is shown in Figure 27.



FIGURE 27 SAVE CURRENT ALARMS

The interface that prompts log export success is shown inFigure 28.

FIGURE 28 EXPORT SUCCESS

END OF STEPS

Replacing Board

Caution:

Wear a grounded antistatic wrist strap before replacing aboard.

Plug/unplug a board in normal order to avoid bent or brokenpins.

Make sure that the components on the board do not rub otherboards in adjacent slots.



ReplacingSA/CC/BPC/UBP-

G/FS/SE/PM Note:

Cut external 48 V power supply before replacing.

1. Wear anti-static wrist strap.

2. Pull out handle switch on the left of the board until it cannotbe pulled out anymore to unlock the board.

Note:

The lock handle has three gears and the lock handle must bepulled at the outerest gears before unplugging the module, orelse plane may be damaged when unplugging.

3. Hold the right and left handles with hands to pull out the mod-ule along the upper/lower guide rails slowly and evenly.

4. Put it into an antistatic bag and put the bag into a packagingbox.

5. Take a new board, and remove the antistatic bag.

6. Slowly and evenly insert and align the module with the left andright guide rails of the insertion box. When module touchesplug base on backboard, push the module into plug base. mod-ule plane and rack plane are flat after plugging successfully.

7. Push handle switch on the left of the board until it cannot bepushed into anymore to lock the board.

Note:

The lock handle has three gears and the lock handle must bepushed into at the deepest gears to lock the module effectively.

Replacing FA

Note:

New FA board needs to be plugged into rack as soon as possiblewhen replacing FA, since the temperature of the other modulesmay be too high to work normally.

1. Wear anti-static wrist strap.

2. Push the lock button on the bottom of FA to the right side withright hand, and at the same time hold the handle on plane topull out module with left hand.

3. Put it into an antistatic bag and put the bag into a packagingbox.

4. Take a new board, and remove the antistatic bag.

5. Slowly and evenly insert and align the module with the leftand right guide rails of the insertion box. When FA touches



plug base on backboard, push the module into plug base. FAplane and rack plane are flat after plugging successfully.


C h a p t e r 5

Maintemance RecordTables

Table of ContentsDaily Maintenance Record Table...........................................53Monthly Maintenance Record Table.......................................54Semi-Yearly Maintenance Record Table .................................55Emergency Handling Record Table........................................55Module Replacement Record Table .......................................56

Daily Maintenance RecordTableDate:

On-duty period: Current engineer in charge: Next engineer incharge:

Current BS Alarm Handling Record:

BS No. Alarm contents Starttime

Finish time Remark

BS History Alarm Handling Record:

BS No. Alarm contents and handling Remark

BS History Notice Handling Record:

BS No. Alarm contents and handling Remark



Customer Complaint Handling

BS No. Complaint content and handling Remark

shift duty contents:

Monitor:

Check:

Monthly MaintenanceRecord TableDate: Maintenance engineer:

Item Record Handling Remark

Check whetherthe BS positionparameter isconsistent withreal situation

Check whetherthe cabinet isclean

Check whetherthe cabling rackis firm enough

Check whetherE1/T1/Fiberinterfaces arein good contact

Check whetherthe equipmentindicatorsstatus is normal

Spare parts Whether allspare parts arein good state.

Yes No


Chapter 5 Maintemance Record Tables

Monitor:

Check:

Semi-Yearly MaintenanceRecord TableDate: Maintenance engineer:

Item Result Remark

Whether the workinggrounding is reliable

Yes No

Whether theequipment room'sgrounding cable isreliable

Yes No

Whether the BSgrounding cable isreliable

Yes No

Grounding resistancetest

Grounding resistance:

Emergency Handling RecordTableEmergency Handling Record Table

Office Name: Field Engineer:

Occurrence Time: Recovery Time:

Fault is found by: Customer Complaint Alarm System Found inroutine maintenance Else

Fault category:



Fault Description:

Handling Method:

Result:

Supervisor's comments:

Module ReplacementRecord TableBoard replacement record table

BS No. Maintenance Engineer

Modulename

ModuleSlot

Fault Oc-currenceTime

Replace-mentTime

SerialNo. ofthe faultymodule

SerialNo. ofthe Newmodule


Chapter 5 Maintemance Record Tables


Figures

Figure 1 Application of Signaling Meter at RNS.......................12

Figure 2 General Flow of Service Restoration .........................31

Figure 3 Master/Slave Switchover and Reset .........................35

Figure 4 Board Diagnosis Test .............................................36

Figure 5 Export Operation Log of Node B ..............................36

Figure 6 Export History Alarms ............................................37

Figure 7 Save History Alarms ..............................................38

Figure 8 Save Success........................................................39

Figure 9 Export Foreground Log Information .........................40

Figure 10 Master/Slave Switch of CC Board ...........................41

Figure 11 Master/Slave Switch Unavailable............................41

Figure 12 Master/Slave Switch Available ...............................42

Figure 13 Log Management Interface ...................................43

Figure 14 Query and Export Result According to Current

Condition..........................................................43

Figure 15 Save the Exported Log .........................................44

Figure 16 Available File Types..............................................44

Figure 17 Export Success....................................................44

Figure 18 Show Current Object Alarm ..................................45

Figure 19 Query Result.......................................................46

Figure 20 Save Current Alarms............................................46

Figure 21 Query Current Alarms ..........................................47

Figure 22 Set Current Alarm Query Conditions.......................47

Figure 23 Quick Search ......................................................47

Figure 24 Specify Query Condition .......................................48

Figure 25 Specify NE Location .............................................49

Figure 26 Query Result.......................................................49

Figure 27 Save Current Alarms............................................50

Figure 28 Export Success....................................................50


Tables

Table 1 PM Panel Indicator Description................................... 5

Table 2 CC Panel Indicator Description................................... 5

Table 3 UBPG Panel Indicator Description............................... 7

Table 4 BPC Panel Indicator Description ................................. 8

Table 5 FS Panel Indicator Description ................................... 9

Table 6 SA Panel Indicator Description................................... 9

Table 7 SE Panel Indicator Description ..................................10

Table 8 TAM PANEL INDICATOR EXPLANATION.......................10

Table 9 Daily Maintenance Items..........................................18

Table 10 Monthly Maintenance Items....................................18

Table 11 Semi-Yearly Maintenance Items ..............................19

Table 12 Other Maintenance Items.......................................20

Table 13 Possible Faults ......................................................21

Table 14 Evaluation Standard of Complete Equipment

Breakdown .......................................................28


Glossary

BER- Bit Error Rate

BPC- Baseband Processing Board Type C

BS- Base Station

CC- Control and Clock Module

CPU- Central Processing Unit

FCE- Fan Control Element

FER- Frame Error Rate

FS- Fabric Switch Module

I/Q- In-phase/Quadrature

LMT- Local Maintenance Terminal

MSC- Mobile Switching Center

NE- Network Element

NM- Network Management

NMS- Network Management System

OMMB- Operation & Maintenance Moudle (Node B)

PM- Power Module

RNC- Radio Network Controller

RRU- Remote Radio Unit

RTR- RRU Transceiver

SA- Site Alarm Module

SNR- Signal to Noise Ratio



UBPG- Universal Baseband Processing Board for GSM

UE- User Equipment

UMTS- Universal Mobile Telecommunication System


PrefaceMaintenance OverviewRequirements for Maintenance PersonnelMaintenance PrinciplesOverviewRights ManagementData ObservationData ModificationData SynchronizationMan-Machine CommandBoard OperationsSystem Update

Maintenance CategoryMaintenance Analysis MethodsLED Indicator AnalysisSignaling Tracing AnalysisAlarm Log AnalysisInstrument and Meter AnalysisComparison by Replacement

Attention ItemsPersonnel QualificationsMaintenance ManagementData MaintenanceEquipment EnvironmentTools and InstrumentsSpare PartsTechnical DocumentsTechnical Support

Routine MaintenanceOverviewDaily Maintenance ItemsMonthly Maintenance ItemsSemi-Yearly Maintenance ItemsOther Recommended Maintenance Items

Troubleshooting ExamplesOverviewSystem Monitoring High CPU UtilizationDecreased BS Coverage Radius

User ComplaintsLow Call Completion RatePoor Call QualitySlow Internet Access

Emergency MaintenanceOverviewFault EvaluationEvaluation Standard of Complete Equipment Breakdown

Service Impact of the FaultFault Report FlowEmergency Fault HandlingManual Master/Slave SwitchPower-Off Reset on Faulty BoardFAN Operation CheckUse of Slave FS Board

Service Restoration FlowGeneral Flow of Service RestorationDetailed Flow of Service RestorationChecking PM Power SupplyChecking Power Supply SystemChecking Key Board Power Supply Checking Service Board OperationResetting or Replacing BoardChecking Relationship between Configuration Modification and theRestoring Configuration DataCollecting Fault Information

Common Operations of BS Emergency Maintenance via NM SoftwareApplication Scenario of NM SoftwareEmergency Maintenance Operations Via LMTMaster/Slave Switchover and ResetPerform Board Diagnosis TestExporting Operation Log of Node BExporting Current and History Alarms of Node BExporting Foreground Log Information

Emergency Maintenance Operations Via NetNumenM31(RAN)/OMMBMaster/Slave Switch and Reset/Power-Off ResetExporting Operation Log of Node BQuerying and Exporting Current Alarms of Node B

Replacing Board

Maintemance Record TablesDaily Maintenance Record TableMonthly Maintenance Record TableSemi-Yearly Maintenance Record TableEmergency Handling Record TableModule Replacement Record Table

FiguresTablesGlossary