sj-20110411154055-008-zxmbw r9110

ZXMBW R9110802.16e BTS(48)

Operation and Maintenance Manual

Version: V4.02

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.0 08/10/2009 First Edition

R1.1 05/30/2010 The procedures of common maintenance operations are modified.

R1.2 08/30/2010 The procedures of common maintenance operations are modified

according to OMC(V3.33/V4.02).

Serial Number: SJ-20110411154055-008

Publishing Date: 08/30/2010

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

Declaration of RoHS Compliance ................................................................. I

Chapter 1 Safety Description .................................................................... 1-1

1.1 Safety Specifications Guide ................................................................................ 1-1

1.2 Safety Symbols .................................................................................................. 1-2

1.3 Safety Instructions.............................................................................................. 1-3

Chapter 2 Maintenance Overview ............................................................. 2-1

2.1 Maintenance Categories ..................................................................................... 2-1

2.2 Common Maintenance Methods.......................................................................... 2-2

2.3 Common Maintenance Precautions ..................................................................... 2-3

2.4 Maintenance Information Collection..................................................................... 2-4

2.4.1 Basic Maintenance Information Collection Table ......................................... 2-4

2.4.2 Version Information Collection Table .......................................................... 2-5

Chapter 3 Routine Maintenance................................................................ 3-1

3.1 Routine Maintenance Definition........................................................................... 3-1

3.2 Routine Maintenance Items................................................................................. 3-2

3.3 Routine Maintenance Schedule........................................................................... 3-2

3.4 Monthly Maintenance Items ................................................................................ 3-2

3.5 Quarterly Maintenance Items .............................................................................. 3-4

3.6 Annual Maintenance Items.................................................................................. 3-6

Chapter 4 Troubleshooting........................................................................ 4-1

4.1 Troubleshooting Definition................................................................................... 4-1

4.2 Frequent Alarms ................................................................................................ 4-1

4.2.1 No WTRX Detected.................................................................................. 4-1

4.2.2 No WRFE Detected ................................................................................. 4-1

4.2.3 No WDPA Detected .................................................................................. 4-2

4.2.4 Inconsistent Board Type ........................................................................... 4-2

4.2.5 PA is Abnormal ........................................................................................ 4-2

4.2.6 VSWR Alarm ........................................................................................... 4-2

4.2.7 PA Shutdown Alarm.................................................................................. 4-3

4.2.8 No 802.16e BTS Detected ........................................................................ 4-3

Chapter 5 Common Operations ................................................................ 5-1

I

5.1 Starting the Server ............................................................................................. 5-1

5.2 Viewing Alarm Summary through Monitoring Window ........................................... 5-2

5.3 Acknowledging and Deleting Active Alarms.......................................................... 5-3

5.4 Quickly Querying Alarm Information..................................................................... 5-4

5.5 Customizing Alarm Query Conditions .................................................................. 5-7

5.6 Exporting Cleared Alarm Information ................................................................... 5-9

5.7 Setting Forwarding Rule ................................................................................... 5-10

5.8 Collecting Alarm Statistic by Alarm Code ........................................................... 5-13

5.9 Collecting Alarm Statistics by NE....................................................................... 5-14

5.10 Collecting Alarm Statistics by Time .................................................................. 5-16

5.11 Customizing Alarm Statistics ........................................................................... 5-18

5.12 Viewing Board CPU Usage ............................................................................. 5-21

5.13 Querying Original Performance Data ............................................................... 5-24

5.14 Collecting Service Data................................................................................... 5-26

5.15 Saving Signaling and Global Data ................................................................... 5-29

5.16 Customizing Auto-Test Task ............................................................................ 5-30

5.17 Spectrum Analysis.......................................................................................... 5-33

5.18 Auto Calibration.............................................................................................. 5-35

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

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

Index ...............................................................................................................V

Glossary .......................................................................................................VII

II

About This ManualPurpose

Thank you for choosing 802.16e radio network system of ZTE Corporation!

ZXMBWR9110 is a 802.16e BTS developed by ZTECorporation and applied to large-scaleoutdoor coverage and blind and hot spots such as basements and squares.

This manual describes the ZXMBW R9110 maintenance methods. It provides themaintenance personnel with detailed information to discover and solve faults and potentialtroubles.

Intended Audience

This document is intended for maintenance engineers who perform maintenance activitieson ZXMBW R9110.

Prerequisite Skill and Knowledge

To use this document effectively, users should have a general understanding of ZXMBWR9110 equipment and its components. Familiarity with the following is helpful:

l Network Management System operationsl ZXMBW R9110 hardware structure

What is in This Manual

This manual contains the following chapters:

Chapter Summary

Chapter 1 Safety

Description

Describes safety symbols and safety specification.

Chapter 2

Maintenance

Overview

Describes ZXMBW R9110 common maintenance method, precautions and

some information collection tables.

Chapter 3 Routine

Maintenance

Describes the tasks involved in ZXMBW R9110 maintenance.

Chapter 4

Troubleshooting

Describes handling methods of commonly occurred faults of ZXMBW R9110.

Chapter 5 Common

Operations

Describes common operations in maintaining ZXMBW R9110.

Conventions

ZTE documents employ the following typographical conventions.

I

Typeface Meaning

Italics References to other Manuals and documents.

Quotes Links on screens.

Bold Menus, menu options, function names, input fields, radio button names, check

boxes, drop-down lists, dialog box names, window names.

CAPS Keys on the keyboard and buttons on screens and company name.

Note: Provides additional information about a certain topic.

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

proceeding further.

Tip: Indicates a suggestion or hint to make things easier or more productive

for the reader.

Mouse operation conventions are listed as follows:

Typeface Meaning

Click Refers to clicking the primary mouse button (usually the left mouse button) once.

Double-click Refers to quickly clicking the primary mouse button (usually the left mouse button)

twice.

Right-click Refers to clicking the secondary mouse button (usually the right mouse button)

once.

II

Declaration of RoHSComplianceTo minimize the environmental impact and take more responsibility to the earth we live,this document shall serve as formal declaration that ZXMBW R9110 manufactured byZTE CORPORATION are in compliance with the Directive 2002/95/EC of the EuropeanParliament - RoHS (Restriction of Hazardous Substances) with respect to the followingsubstances:

l Lead (Pb)l Mercury (Hg)l Cadmium (Cd)l Hexavalent Chromium (Cr (VI))l PolyBrominated Biphenyls (PBBs)l PolyBrominated Diphenyl Ethers (PBDEs)

The ZXMBW R9110 manufactured by ZTE CORPORATION meets the requirements of EU

2002/95/EC; however, some assemblies are customized to client specifications. Addition of

specialized, customer-specified materials or processes which do not meet the requirements of

EU 2002/95/EC may negate RoHS compliance of the assembly. To guarantee compliance of the

assembly, the need for compliant product must be communicated to ZTE CORPORATION in written

form. This declaration is issued based on our current level of knowledge. Since conditions of use are

outside our control, ZTE CORPORATION makes no warranties, express or implied, and assumes no

liability in connection with the use of this information.

I

Chapter 1Safety DescriptionTable of Contents

Safety Specifications Guide........................................................................................1-1Safety Symbols ..........................................................................................................1-2Safety Instructions......................................................................................................1-3

1.1 Safety Specifications GuideThese safety instructions must be considered as supplementary for local safetyregulations. The priority must be given to local safety regulations if there is any conflictbetween the two.

The maintenance personnel must have the knowledge of safety operations andmaintenance with required qualification and technical background.

Warning!

This device complies with part 15 of the FCC Rules. Operation is subject to the followingtwo conditions: (1) This device may not cause harmful interference, and (2) this devicemust accept any interference received, including interference that may cause undesiredoperation. Changes or modifications not expressly approved by the party responsible forcompliance could void the user's authority to operate the equipment.

All the operation and maintenance personnel must follow the safety precautions andinstructions provided by ZTE Corporation to avoid any accident.

Note:

ZTE Corporation does not bear any liabilities incurred because of violation of theuniversal safety operation requirements, or violation of safety standards for designing,manufacturing and using the equipment.

FCC Radiation Exposure Statement:

1-1

SJ-20110411154055-008|08/30/2010 ZTE Proprietary and Confidential

ZXMBW R9110 Operation and Maintenance Manual

This equipment complies with FCC radiation exposure limits set forth for an uncontrolledenvironment. This equipment should be installed and operated with minimum distance 3mbetween the radiator and your body.

1.2 Safety SymbolsTable 1-1 lists safety symbols. They are to prompt the user of the safety precautions to beobserved during ZXMBW R9110 operation and maintenance.

Table 1-1 Safety Symbols Description

Safety Symbols Meaning

No smoking: Smoking is forbidden

No flammables: No flammables can be stored.

No touching: Do not touch.

Universal alerting symbol: General safety attentions.

Electric shock: Risk of electric shock.

Electrostatic: The device may be sensitive to static electricity.

Microwave: Beware of strong electromagnetic field.

Laser: Beware of strong laser beam.

Scald: Beware of scald.

Amongst these safety symbols, the universal alarm symbols are classified into three levels:danger, warning, and caution. The formats and meanings of the three levels are describedas below:

1-2


Chapter 1 Safety Description

Danger!

Indicates a potentially hazardous situation which, if not avoided, will result in death orserious injury of people, or equipment damages and breakdown.

Warning!

Indicates a potentially hazardous situation which, if not avoided, could result in death orserious injury.

Caution!

Indicates a potentially hazardous situation which, if not avoided, could result in seriousinjuries, equipment damages or interruption of part services.

1.3 Safety InstructionsThis section describes the safety instructions related to electrical safety, antistatic, heavyobjects and modules.

Electrical Safety Instructions

The following are the electrical safety instructions about tools, high voltage, power cables,holes and lightning:

l Tools

Use special tools rather than common tools for high-voltage and AC operations.

l High Voltage

Danger!

High voltage is hazardous. Direct or indirect contact with high voltage or main supplyusing a wet object could result in death.

Strictly follow local safety rules to install AC power devices.

Installation staff must be qualified for performing high-voltage and AC operations.

1-3



Do not wear any watch, hand chain, bracelet, ring or any other conductive objectsduring such operations.

Prevent moisture from accumulating on the equipment during operations in adamp environment.

l Power Cable

Warning!

Never install or uninstall power cables while they are live. Otherwise, the power cable,when contacting a conductor, may result in sparks or electric arc causing a fire or evendamage to eyes.

Make sure of shutting off power supply before installing or disconnecting a powercable.

Before connecting the power cable, make sure that the connecting cable and itslabel are appropriate for the actual installation requirements.

l Drilling Holes

Warning!

It is not allowed to drill chassis holes without permission.

Unqualified drilling could damage wiring and cables inside the chassis.Additionally, metal pieces inside the chassis created by the drilling could resultin a short circuit. Use insulation protection gloves and first move cables inside achassis away when drilling is necessary on a chassis.

Protect eyes during drilling as dust or flying debris may damage eyes.

Clean any debris in time after drilling.

l Lightning

Danger!

Do not perform high-voltage, AC, iron tower or mast operations in a thunderstorm.

Thunderstorms would give rise to a strong electromagnetic field in the atmosphere.Therefore, the equipment must be grounded and protected in time against lightningstrikes.

1-4



Antistatic Safety Instructions

Caution!

Static electricity produced by human body can damage static-sensitive components oncircuit board, such as large-scale integrated circuits.

l Friction caused by human body activities is the root cause of electrostatic chargeaccumulation. Static voltage carried by a human body in a dry environment can beup to 30 kV, and can remain there for a long time. An operator with static electricitymay discharge electricity through a component when he/she touches the conductorand cause damage.

l Wear an antistatic wrist strap (the other end of wrist strap must be well grounded)before touching the equipment or holding a plug-in board, circuit board, IntegratedCircuit (IC) chip or other devices, to prevent human static electricity from damagingsensitive components.

l The antistatic wrist strap used must be subject to regular check. Do not replace thecable of an antistatic wrist strap with any other cables.

l Do not contact static-sensitive modules with any object that easily generates staticelectricity. For example, friction of package bag, transfer box and transfer belt madefrom insulation plastic may cause static electricity on components. Discharge of staticelectricity may damage components when they contact a human body or the ground.

l Modules should only contact materials such as an antistatic bag. Keep modules inantistatic bags during storage and transportation.

l Discharge static electricity of the test device before use, that is, ground the test devicefirst.

l Do not place the module near a strong DC magnetic field, such as the cathode-raytube of a monitor. Keep the module at least 10 cm away.

Hoisting Heavy Objects

Warning!

When hoisting heavy objects, ensure that nobody is standing or walking under the hoistedobject.

l Ensure the hoister can meet hoisting requirements when disassembling heavyequipment, or moving and replacing equipment.

l The installation personnel must be duly trained and qualified for hoisting operations.l Hoisting tools must be inspected and complete before service.

1-5



l Make sure that hoisting tools are fixed firmly on a sufficiently secured object or wallbefore the hoisting operation.

l Give brief oral instructions during hoisting operations to prevent any mishap.

Unplugging/Plugging a Module

l Never plug a module with excessive force, to ensure that the pins on the backplanedo not get deformed.

l Plug the module right into the slot and make sure module circuit faces do not contacteach other lest any short circuit may occur.

l Keep hands off the module circuit, components, connectors and cable trough whenholding a module.

Rack-mounting Safety Instructions

Rack-mounting Instructions - The following or similar rack-mount instructions are includedwith the installation instructions:

l Elevated Operating Ambient - If installed in a closed or multi-unit rack assembly, theoperating ambient temperature of the rack environment may be greater than roomambient. Therefore, consideration should be given to installing the equipment in anenvironment compatible with the maximum ambient temperature (Tma) specified bythe manufacturer.

l Reduced Air Flow - Installation of the equipment in a rack should be such that theamount of air flow required for safe operation of the equipment is not compromised.

l Mechanical Loading - Mounting of the equipment in the rack should be such that ahazardous condition is not achieved due to uneven mechanical loading.

l Circuit Overloading - Consideration should be given to the connection of theequipment to the supply circuit and the effect that overloading of the circuits mighthave on overcurrent protection and supply wiring. Appropriate consideration ofequipment nameplate ratings should be used when addressing this concern.

l Reliable Earthing - Reliable earthing of rack-mounted equipment should bemaintained. Particular attention should be given to supply connections other thandirect connections to the branch circuit (e.g. use of power strips).

Other Safety Instructions

Note:

Do not perform maintenance or debugging independently, unless a qualified person ispresent.

l Perform an airtight test before 802.16e BTS delivery, and prohibit disassembling the802.16e BTS on site.

1-6



l Replacing any parts or making any changes to the equipment might result in anunexpected danger. Therefore, be sure not to replace any parts or perform anychanges to the equipment unless authorized otherwise.

l Due to that 802.16e BTS is in high temperature during running, the 802.16e BTSshould be installed in some regions out of operators' reach or strictly restricted.

l Contact ZTE office if you have any question, to ensure your safety.

1-7



This page intentionally left blank.

1-8


Chapter 2Maintenance OverviewTable of Contents

Maintenance Categories.............................................................................................2-1Common Maintenance Methods.................................................................................2-2Common Maintenance Precautions............................................................................2-3Maintenance Information Collection............................................................................2-4

2.1 Maintenance CategoriesMaintenance is categorized into following two types:

l Routine Maintenancel Emergency Maintenance

Routine Maintenance

Routine maintenance tasks come under the preventive maintenance operation tasks. Thepreventive maintenance operations are performed on a scheduled basis to monitor thesystem regularly, and to get sustained service from ZXMBW R9110. Routine maintenanceallows maintenance personnel to identify potential sources of hazards, which enable themaintenance personnel to resolve these problems in time. Performing these tasks in atimely manner can lengthen the life of components and therefore reduce system-downtime.

The goal of routine maintenance is to enhance the system performance and service fora longer period of time at minimum usage of resources. Resources that are minimizedinclude minimization of unnecessary initialization, diagnostics, and ZXMBW R9110 sitevisits.

Emergency Maintenance

Emergency maintenance is a kind of unpredictable maintenance. It means the immediatetroubleshooting for the failed equipments when there is an emergency. The key target ofemergency maintenance is to restore the service as soon as possible. Network operatorshould refer to this guide to prepare the emergency failure handling regulation and providetrainings for staff.

Determine the potential causes of the fault, if possible, perform troubleshooting accordingto this guide. In addition, contact the ZTE customer support center for advanced technicalsupport.

2-1



Collect the alarm information and hard copies of the failure. Send the related failurehandling report and event logs to ZTE for analysis.

2.2 Common Maintenance MethodsThis section describes some common methods for analyzing and troubleshootingfaults, which are different from the troubleshooting methodology. The troubleshootingmethodology is a kind of thinking rule, which guides the practice of detailed troubleshootingmethods. Following is the detailed description of common maintenance methods.

Fault Analysis

Generally, a wireless network consists of various equipment entities. The fault symptomof a kind of equipment entity is different from that of other kinds. Therefore, whenmaintenance personnel finds a fault or receives a fault report, he/she should analyze thefault symptom and judge from what kind of equipment entity the fault comes first. Thencheck the equipment entity further.

The analysis of fault symptom is important especially for emergent faults. To avoid wrongmaintenance operations on normal equipment entities, maintenance personnel shouldanalyze fault symptoms carefully and locate faulty equipment entity correctly. Moreover,it costs less time to troubleshoot faults on the basis of correct analysis.

Replacement Method

The replacement method is used to locate fault. For example, when a fault occurs, replacea possible faulty part with a normal spare one. If the fault disappears, it can be judged thatthe replaced part is faulty.

The principle of part replacement is as follows: Replace the part which reports alarm witha good one. If the alarm disappears, it indicates that this part is the faulty one. If the alarmstill exists after the part is replaced, analyze the fault further and replace other parts whichare possibly faulty.

The replacement method is simple and practical. Moreover, it can be used to compare thestatus, parameters, logs and parameter configuration of same parts for inconsistency.

Note:

The replacement operation is only carried out in safe time period to avoid serviceinterruption.

2-2


Chapter 2 Maintenance Overview

2.3 Common Maintenance Precautions

Overview

Before and during maintenance, take necessary precautionary measures to ensure safetyof the maintenance personnel and smoothness of maintenance tasks.

Safety Precautions

The power supply input voltage exceeds safety limits for human contact. Ensure adequatesafety measures to avoid any electric shock risk or equipment damage.

Operation Precautions

Ensure the following precautions during maintenance:

l ESD Procedures

The proper ESD procedures must be followed before working with the ZXMBWR9110modules.

l Handling RF Cables and Connections

Avoid sharp bends.

Follow required procedures while handling with connections, especially whichrequire the use of torque wrenches.

Never apply power to a RF cable or disconnect a RF cable, when it is in workingmode.

l Other Precautions

Make record of all maintenance procedures and steps including versionupgrades, data backup and troubleshooting.

Ensure the availability of frequently used tools and meters, screw drivers(Philips-/Flathead-screwdrivers), signaling meter, network cable pliers,multimeter, and network cables. Check and calibrate meters to ensure accuracy.

Check spare parts and components frequently to ensure their availability andintactness. Mark and store damaged parts after maintenance at some separateplace. Avoid storing of damaged parts with new spare parts.

Maintenance personnel should analyze the cause of every particular fault, andfigure out the potential source of hazard before proceeding further.

Check the availability of system documents, including the technology, installation,operation, and maintenance manuals for reference at maintenance time.

2-3



2.4 Maintenance Information Collection

2.4.1 Basic Maintenance Information Collection TableTable 2-1 gives the information that should be collected during ZXMBW R9110maintenance.

Table 2-1 Maintenance Information Collection Table

Maintenance Information Collection Table

ZXMBW R9110

name

North latitude

ZXMBW R9110

type

East longitude

ZXMBW R9110

No.

Height above sea

level

ZXMBW R9110

ID (configured in

OMC)

ASN where the

ZXMBW R9110

belongs

Administrative

County/city

Room phone num-

ber

Detailed room lo-

cation

In daisy-link mode

(link structure)

The first carrier frequency The second car-

rier frequency

Antenna position

Sector S0/S1 S1/S2

Antenna type

Antenna gain

(dBi)

Antenna horizon-

tal beam width

Antenna vertical

beam width

Antenna height

Diversity mode

Antenna azimuth

Antenna downtilt

2-4


Chapter 2 Maintenance Overview

Maintenance Information Collection Table

Electrical downtilt

length of main

feeder

Surrounding to-

pography descrip-

tion

2.4.2 Version Information Collection TableCollection and recording of ZXMBW R9110 version information facilitates ZXMBW R9110maintenance. Because only the WTRX and WDPA modules in the ZXMBWR9110 containsoftware, only WTRX and WDPA version information needs to be collected.

Table 2-2 gives the ZXMBW R9110 version information that needs to be collected.

Table 2-2 Version Information Collection Table

Module Version

WTRX

WDPA

Description:

2-5



This page intentionally left blank.

2-6


Chapter 3Routine MaintenanceTable of Contents

Routine Maintenance Definition..................................................................................3-1Routine Maintenance Items........................................................................................3-2Routine Maintenance Schedule..................................................................................3-2Monthly Maintenance Items........................................................................................3-2Quarterly Maintenance Items......................................................................................3-4Annual Maintenance Items .........................................................................................3-6

3.1 Routine Maintenance DefinitionRoutine maintenance is to periodically perform preventative maintenance and detectionon equipment, so as to make the equipment in a stable operation for a long time.

Routine maintenance includes the following tasks:

l Regular maintenance and detection. The maintenance personnel is required toregularly check and test the running status, functions, major performance indicesand hardware of the ZXMBW R9110 equipment using necessary instruments andtools according to the OMM operation specification and ZXMBW R9110 equipmenttechnical specifications.

l Regular check and cleaning. The maintenance personnel is required to regularlycheck the ZXMBW R9110 equipment and its auxiliary devices, and replace faulty orunsatisfactory parts in time. The maintenance personnel should regularly maintainand clean the parts that are damageable or require a high level anti-dust protection,as well as the key parts of the peripherals.

A proper work cycle plan for ZXMBW R9110 routine maintenance is recommended.

Note:

The running status of ZXMBW R9110 can be observed at the OMM, for it is anunmanned monitoring device. The OMM maintenance personnel is responsible forroutine maintenance of ZXMBW R9110.

3-1



3.2 Routine Maintenance ItemsRoutine maintenance is to keep equipment in the best operation status so as to meetvarious service requirements.

The ZXMBW R9110 routine maintenance involves the following fundamental tasks:

l Work environment inspection of the equipmentl Performance statistics of the equipmentl Maintenance of the alarm systeml Data backupl Backup inspectionl Board maintenancel Log inspectionl Inspection of the grounding and lightning systeml Inspection of the running status of the power systeml Inspection of the antenna feeder systeml Preparations before holidays and festivals

3.3 Routine Maintenance ScheduleDepending upon the tasks to be performed, routine maintenance is scheduled on periodicbasis. These are:

l Monthly Maintenancel Quarterly Maintenancel Yearly Maintenance

3.4 Monthly Maintenance ItemsTable 3-1 gives ZXMBW R9110 monthly maintenance items.

Table 3-1 Monthly Maintenance Table

Item Description

Checking tempera-

ture and humidity

View temperature and humidity through the OMC alarm management system.

(The concrete content can be found in ZXMBW R9110 Remote Radio Unit

(48) Technical Manual)

Checking module

running states

View module running states through the OMC alarm management system. Per-

form a diagnostic test on the module that runs abnormally to find out the cause.

Checking voice and

data services

Perform voice and data service tests using an MS on site and carry out ASN

service observation to check services of all the sectors. Check whether call

drops, discontinuity or abnormal throughputs occur.

Checking the power

supply

Check the power supply of the ZXMBW R9110.


(48) Technical Manual

3-2


Chapter 3 Routine Maintenance

Item Description

Checking the

grounding system

and lightning sys-

tem

Check whether the grounding system and lightning system work well.


(48) Technical Manual

Checking the power

of WDPA Check the WDPA power of each sector through the OMC system.

Checking antenna

feeder standing

wave ratios

Check whether VSWR alarms are available. Measure the standing waving ratio

of every antenna feeder system.

Other descriptions:

Table 3-2 gives a ZXMBW R9110 monthly maintenance record table.

Table 3-2 Monthly Maintenance Record Table

Equipment name: Maintenance date:

Maintained by:

Item State Remarks

Temperature and humidity NormalAbnormal

Module running states NormalAbnormal

Voice service and data service NormalAbnormal

Power supply NormalAbnormal

Grounding system and lightning

system NormalAbnormal

Power of WDPA NormalAbnormal

Antenna feeder standing wave ratio NormalAbnormal

Failure description and

handling

3-3




Unsolved problems

Review of the person

in charge

3.5 Quarterly Maintenance ItemsTable 3-3 describes quarterly maintenance items for ZXMBW R9110.

Table 3-3 Quarterly Maintenance Items

Item Description

Checking module running status View module running states through the OMC alarm man-

agement system. Perform a diagnostic test on the module

that runs abnormally to find out the cause.

Checking data service Perform voice and data service tests using an MS on site

and carry out ASN service observation to check services of

all the sectors. Check whether call drops, discontinuity or

abnormal throughputs occur.

Checking the power supply Check the power supply of the ZXMBW R9110.

Checking the grounding system and

lightning system

Check whether the grounding system and lightning system

work well.

Checking the power of WDPA

Check the WDPA power of each sector through the OMC

system.

Checking antenna feeder standing wave

ratios

Check whether VSWR alarms are available. Measure the

standing waving ratio of every antenna feeder system.

Make sure the feeder is in good contact after performing

the standing wave ratio test.

Measure the grounding resistance using a resistance

tester.

Checking grounding resistance and

grounding cable

Check whether each grounding cable connector is loosed

or aged.

3-4



Item Description

Checking feeder connectors, waterproof

protection and grounding connection of

the lightning grounding kit

Check the appearance of each feeder connector or un-

wrap the insulation tapes to check the appearance if nec-

essary. Do remember wrapping every connector with insu-

lation tapes after making sure it is in good condition.

Checking the antenna installation and

pitch angle and azimuth of each direc-

tional antenna

Check whether the antenna is tightly fixed and whether its

pitch angle and azimuth are in the range required in network

planning using proper tools, for example, wrench and angle

instrument.

Checking the lightning grounding cable Check whether the lightning grounding cable is reliably con-

nected and whether the joints are free of rust.

Other descriptions:

Table 3-4 gives a quarterly maintenance record table for the ZXMBW R9110.

Table 3-4 Quarterly Maintenance Record Table


Maintained by:

Item State Remarks

ZXMBW R9110 module running states NormalAbnormal

Data service NormalAbnormal


Grounding system and lightning system NormalAbnormal

Power of the WDPA NormalAbnormal


Grounding resistance and grounding cable NormalAbnormal

Feeder connectors, waterproof protec-

tion and grounding connection of lightning

grounding kit NormalAbnormal

Antenna installation and pitch angle and az-

imuth of directional antenna NormalAbnormal

Lightning grounding cable NormalAbnormal

3-5




Failure description and handling

Unsolved problems

Review of the person in charge

3.6 Annual Maintenance ItemsTable 3-5 describes annual maintenance items for the ZXMBW R9110.

Table 3-5 Annual Maintenance Items

Item Description

Checking cleanness and sealing perfor-

mance of the case

Carefully clean the case using a vacuum cleaner and

a cloth without touching the switch or power supply.

Open the case to check whether it is watered and check

the sealing performance of the case.

Checking temperature and humidity View temperature and humidity through the OMC alarm

management system.

Checking module running states View module running states through the OMC alarm

management system. Perform a diagnostic test on the

module that runs abnormally to find out the cause.

Checking voice and data services Perform voice and data service tests using an MS on

site and carry out ASN service observation to check

services of all the sectors. Check whether call drops,

discontinuity or abnormal throughputs occur.

Checking the power supply Check the power supply of the ZXMBW R9110.

Checking the grounding system and lightning

system

Check whether the grounding system and lightning sys-

tem work well and whether the arrester is in good con-

dition.

Checking the power of WDPA

Check the WDPA power of each sector through the

OMC system.

3-6



Item Description

Checking antenna feeder standing wave ra-

tios

Check whether VSWR alarms are available. Measure

the standing waving ratio of every antenna feeder sys-

tem. Make sure the feeder is in good contact after com-

pleting the standing wave ratio test.

Measure the grounding resistance using a resistance

tester.

Checking grounding resistance and ground-

ing cable

Check whether each grounding cable connector is

loosed or aged.

Checking feeder connectors, waterproof pro-

tection and grounding connection of the light-

ning grounding kit

Check the appearance of each feeder connector or un-

wrap the insulation tapes to check the appearance if

necessary. Do remember wrapping every connector

with insulation tapes after making sure it is in good con-

dition.

Checking the antenna installation and pitch

angle and azimuth of each directional an-

tenna

Check whether the antenna is tightly fixed and whether

its pitch angle and azimuth are in the range required

in network planning using proper tools, for example,

wrench and angle instrument.

Checking the lightning grounding cable Check whether the lightning grounding cable is reliably

connected and whether the joints are free of rust.

Other descriptions:

Table 3-6 gives an annual maintenance record table for the ZXMBW R9110.

Table 3-6 Annual Maintenance Record Table


Maintained by:

Item State Remarks

Case cleanness NormalAbnormal

Temperature and humidity NormalAbnormal

Module running states NormalAbnormal

Voice service and data service NormalAbnormal


Grounding system and lightning system NormalAbnormal

3-7




Power of WDPA NormalAbnormal


Grounding resistance and grounding cable NormalAbnormal

Feeder connectors, waterproof protec-

tion and grounding connection of lightning

grounding kit NormalAbnormal

Antenna installation and pitch angle and az-

imuth of directional antenna NormalAbnormal

Lightning grounding cable NormalAbnormal

Failure description and handling

Unsolved problems

Review of the person in charge

3-8


Chapter 4TroubleshootingTable of Contents

Troubleshooting Definition ..........................................................................................4-1Frequent Alarms.........................................................................................................4-1

4.1 Troubleshooting Definition

Definition

Troubleshooting refers to the procedures, which maintenance personal should perform toremedy a potential source of failure. Procedures for remedying a failure, no matter it is apart of routine or corrective maintenance are same after the potential source of failure isidentified.

Scope of this Manual

It is behind the scope of this manual to deal with actual repairs and adjustments of ZXMBWR9110 equipments.

Example: Repairing of faulty units require special tools and repairing expertise, so it mustbe carried out at appropriate place or manufacturing plant.

Handling Principle

The principle for handling these abnormalities is that, abnormalities that occur veryfrequent must be dealt before the ones that occur less frequently.

4.2 Frequent Alarms

4.2.1 No WTRX DetectedPerform the following steps to clear this alarm.

1. Check whether the WTRX board is inserted properly and the cables are connectedfirmly.

2. If the alarm still persists, replace the WTRX board.

4.2.2 No WRFE DetectedPerform the following steps to clear this alarm.

4-1



1. Check whether the WRFE board is inserted properly and the cable connections arefirm.

2. If the alarm still persists, replace the WRFE board.

4.2.3 No WDPA DetectedPerform the following steps to clear this alarm.

1. Check whether the WDPA board is inserted properly and the cables are firmlyconnected.

2. If the alarm still persists, replace the WDPA board.

4.2.4 Inconsistent Board TypePerform the following steps to clear this alarm.

1. Modify the configuration in OMC.2. If the problem still persists, change the corresponding board in the rack.

4.2.5 PA is AbnormalThis alarm occurs because of any of the following reasons.

l PA is not plugged.l Communication with PA is abnormall VSWR is abnormal.

There are two options to clear this alarm. They are:

1. The 802.16e BTS side has to inform the OMC to maintain PAs.2. Replace the WDPA board.

4.2.6 VSWR Alarm

Context

A VSWR alarm appears in the OMC system.

The cause may be:

1. The feeder connector is loosed.2. The feeder is watered.3. The feeder is improperly routed.

Steps

1. Check whether the feeder connectors are in good contact. If no, tighten them.

2. Check whether the feeder is properly waterproofed and whether it is watered. If thefeeder is watered, properly waterproof it according to the specification after it getsair-dry.

4-2


Chapter 4 Troubleshooting

3. Test the standing wave ratio of the feeder with a standing wave ratio tester. Thestanding wave ratio should be less than 1.3. Otherwise the feeder should be replaced.

End of Steps

4.2.7 PA Shutdown Alarm

Context

A PA shutdown alarm appears in the OMC alarm interface.

The cause may be:

1. High standing wave ratio results in the WDPA protective shutdown.2. The WDPA is faulty.

Steps

1. Check whether a concurrent VSWR alarm exists. If yes, clear the VSWR alarm first.

2. Enable the PA through theOMC client to check whether the PA can be started normally.

3. View the scaling attenuation value in the OMC client to check whether the value is toolow.

4. If the alarm remains, replace the 802.16e BTS.

End of Steps

4.2.8 No 802.16e BTS Detected

Context

A No 802.16e BTS Detected alarm appears in the OMC alarm interface.

The cause may be that:

1. The physical link between the 802.16e BTS and Indoor Supplementary Component isbroken due to a fiber failure or a trunk failure.

2. The 802.16e BTS power supply is faulty, resulting in 802.16e BTS power-off.3. Board type configuration is wrong or the running version of a board is inconsistent with

that in the Indoor Supplementary Component.4. An 802.16e BTS internal module is faulty.

Steps

1. Check the physical link between the 802.16e BTS and Indoor SupplementaryComponent.

2. Check the power supply of the 802.16e BTS.

3. Check the board type configuration in OMC and board type consistency.

4-3



4. If all checks above are OK, one or more 802.16e BTS internal modules are abnormal.Reset the 802.16e BTS.

5. If the failure remains, replace the 802.16e BTS.

End of Steps

4-4


Chapter 5Common OperationsTable of Contents

Starting the Server .....................................................................................................5-1Viewing Alarm Summary through Monitoring Window.................................................5-2Acknowledging and Deleting Active Alarms ................................................................5-3Quickly Querying Alarm Information ...........................................................................5-4Customizing Alarm Query Conditions .........................................................................5-7Exporting Cleared Alarm Information..........................................................................5-9Setting Forwarding Rule ...........................................................................................5-10Collecting Alarm Statistic by Alarm Code..................................................................5-13Collecting Alarm Statistics by NE..............................................................................5-14Collecting Alarm Statistics by Time...........................................................................5-16Customizing Alarm Statistics ....................................................................................5-18Viewing Board CPU Usage.......................................................................................5-21Querying Original Performance Data........................................................................5-24Collecting Service Data ............................................................................................5-26Saving Signaling and Global Data ............................................................................5-29Customizing Auto-Test Task .....................................................................................5-30Spectrum Analysis....................................................................................................5-33Auto Calibration........................................................................................................5-35

5.1 Starting the Server

Steps

l On the desktop of the host, Starting the server in the Start > Program.

The NetNumen(TM) Console window appears, as shown in Figure 5-1. UMS serviceis starting.. shows in the Detailed Specification pane means the main control andmanagement service UMS which consists of a series of modules is starting.

5-1



Figure 5-1 Server Console

Note:

All the service will start automatically when you open the service console. When aservice is being started the stop button which use to stop the service is not available.

End of Steps

5.2 Viewing Alarm Summary through MonitoringWindow

Prerequisites

Context

The monitoring window presents bar charts to display alarm information, facilitating routinemaintenance. Alarm monitors can be customized. The system provides seven monitorsby default to monitor all events, last 10 minutes, escalated, repeated , acknowledged ,OMC status and dry contact.

Steps

1. Choose Views > Fault Management > Alarm Management to open the AlarmManagement window.

5-2


Chapter 5 Common Operations

2. Click corresponding node in the left pane of the Alarm Management window and allthe bar-type monitors are displayed in the right pane.

3. Select an alarm type by clicking a All drop-down menu.

The operation is as shown in Figure 5-2.

Figure 5-2 Selecting an Alarm Type

4. From the Alarm Management window, click the View button to display the summaryalarm information in the right pane.

End of Steps

5.3 Acknowledging and Deleting Active Alarms

Short Description

This section describes how to acknowledge and delete active alarms.

Steps

1. Acknowledge one or more active alarms.

a. Choose Views > Fault Management > Alarm Management to open the AlarmManagement window.

b. Click Rack in the left pane of the Alarm Management window and a rack diagramappears in the right pane.

c. Click the Active Alarms tab to view the alarm list.

d. Right-click one or more alarm messages and choose Acknowledge from theshortcut menu. The Acknowledge dialog box appears.

5-3



Note:

Only the alarms that are not acknowledged can be acknowledged.

An acknowledged alarm message contains acknowledge time and the one whoacknowledged this message. Meanwhile, the Acknowledge option is checked.

To select multiple alarms, press Shift and click any two alarm messages at thesame time and all alarm messages between the two messages will be selected,or press Ctrl and click the alarm messages that you want to choose one by oneat the same time to select multiple messages.

e. Click Acknowledge.

2. Delete active alarms. From the Active Alarms tab, right-click one or more alarms andchoose Delete Alarm from the shortcut menu.

End of Steps

Result

Acknowledged active alarms and deleted the alarm which was acknowledged.

5.4 Quickly Querying Alarm Information

Short Description

This section describes how to quickly query active alarms, history alarms, and alarmnotifications. The query window contains common query conditions so that users canset the conditions efficiently. In this section, active alarms are queried as an example ofquickly querying alarm information.

Context

The alarm fast query function organizes the database query statement based on the queryconditions specified by the user, sends the query command to the server, and then displaysthe query result in the window.

Steps

1. Choose Views > Fault Management > Alarm Management to display the AlarmManagement window.

2. Choose Query > Quick Query > Query Active Alarms to display the Query ActiveAlarms window.

3. Click the Location tab, and set the target query parameters. Table 5-1 shows thedescription of the parameters.

5-4



Table 5-1 Location Parameter Description

Parameter Description

System type Indicates the system type of the alarm

Location Indicates the location of the alarm

Visibility Indicates the visibility of the alarm. For a visible alarm, the

attribute is available. For a masked alarm, the attribute is

unavailable

4. Click the Code tab, and set Alarm code and Reason code, as shown in Figure 5-3.

Figure 5-3 Code

Note:

The available items inAlarm code andReason code are determined by System typein step 3.

5-5



5. Click the Other Conditions tab, and set the target query conditions, as shown inFigure 5-4.

Figure 5-4 Other Conditions

Table 5-2 shows the description of the parameters.

Table 5-2 Parameter Description of Other Conditions


Occurrence time Indicates the time when the alarm is generated

Acknowledge time Indicates the time when the user acknowledges the alarm

Severity Indicates the severity of the alarm

Type Indicates the type of the alarm

Acknowledge state Indicates whether the alarm has been acknowledged by the user

6. Click OK to display the query result, as shown in Figure 5-5.

5-6



Figure 5-5 Active Alarm Query Result

End of Steps

Follow-Up Action

l Click on the toolbar to save the query result to a file.l Click on the toolbar to print the query result.l Click on the toolbar to set the query conditions again.l Click on the toolbar to refresh the query result.

5.5 Customizing Alarm Query Conditions

Short Description

This function is to save common query conditions so that users can query alarm informationbased on the saved conditions without repeatedly specifying query conditions.

Prerequisites

The ZXMBW R9110 server should be running and the client has accessed the server.

Context

The following functions are provided.l Adding an alarm query condition: Saves an alarm query condition to the server for

later use.l Deleting an alarm query condition: Deletes a useless alarm query condition from the

server.l Modifying an alarm query condition: Modifies an alarm query condition as required.l Using an alarm query condition: Query active alarms, cleared alarms or alarm

notifications based on a saved alarm query condition.

5-7



Steps


2. Choose Operation > SQL Statement Management to display the SQL StatementManagement window.

3. Click button to display the New dialog box, as shown in Figure 5-6. Set theparameters and click OK to save the alarm query condition.

Figure 5-6 Creating New Alarm Query Condition

4. Delete an alarm query condition.

a. Open the SQL Statement Management window.

b. Select the alarm query condition to be deleted and click button or right-click therequired alarm query condition and choose Delete.

c. In the deletion confirm dialog box, click OK to delete the alarm query condition.

5. Modify an alarm query condition.


b. Select the alarm query condition to be modified and click button to display thealarm query condition modification dialog box. You can modify all the parametersexcept for the alarm query condition name.

c. After the modification, click OK to save the modification result.

6. Use an alarm query condition.


5-8



b. Select the alarm query condition to be used, right-click and chooseQuery > ActiveAlarms.

Note:

The method for query cleared alarms and alarm notifications are similar.

End of Steps

5.6 Exporting Cleared Alarm Information

Short Description

Exporting cleared alarm information is to export the queried cleared alarms into a text orExcel file for later query, copying, analysis, and report generation.

Prerequisites


Steps

1. Choose Views > Fault Management > Alarm Management to open the AlarmManagement window.

2. ChooseQuery >QuickQuery >Query ClearedAlarms to display theQuery ClearedAlarms dialog box.

3. Specify the query conditions in the Location, Time,Code andOther Conditions tabs.

4. ClickOK and the system returns to theQuery Cleared Alarms window which displaysthe query result, as shown in Figure 5-7.

Figure 5-7 Cleared Alarm Query Result

5-9



5. Click button to display the Export Original Data dialog box, as shown in Figure 5-8.

Figure 5-8 Exporting Original Data

6. Set the parameters in the Export Original Data dialog box, and then click OK todisplay the Save dialog box. Specify the path to which you want to save the file andspecify the file format (text or Excel).

7. Click Save. After data saving is complete, a message dialog box is prompted showingthat data saving is successful.

If the file name already exists in step 6, the system prompts whether to overwrite theexisting file.

End of Steps

Result

Cleared alarm information was exported.

5.7 Setting Forwarding Rule

Short Description

A lot of alarm information is reported during equipment operation. Some alarm messagesare very useful for equipment maintenance and need to be automatically sent to therelevant personnel.

Context

The alarm mail notification function defines an alarm condition and an Email address.When detecting an alarm that satisfies the condition, the system generates a mail in acertain format and sends it to the specified mail box through a mail proxy server.

Steps


5-10



2. Choose Rules > Forwarding Rule Management to display the Forwarding RuleManagement window.

3. Rightclick a rule whose rule name is Email and choose Modify from the shortcutmenu. The Modify Rule dialog box appears, as shown in Figure 5-9.

Figure 5-9 Modifying Rules

4. Specify mail notification conditions in the Condition tab.

5. Specify mail notification parameters in the Parameter tab, as shown in Figure 5-10.

5-11



Figure 5-10 Modifying Rule Parameters

a. ClickModify in the Parameter tab and the Properties Edit dialog box appears, asshown in Figure 5-11. Set mail agent server parameters in the dialog box. Table5-3 describes these parameters.

Figure 5-11 Editing Properties

Table 5-3 Properties Edit


SMTP server Specifies the IP address of the mail proxy server.

SMTP port Specifies the port of the mail proxy server.

Mail sender Specifies the name of the mail sender.

5-12



b. The Add, Modify and Delete icons in the Parameter tabs can be used to add,modify and delete contents of the mail list.

End of Steps

Result

With the set mail notification rule, the system generates a mail in a certain format andsends it to the specified mail box through a mail proxy server when detecting an alarmsatisfying the rule.

5.8 Collecting Alarm Statistic by Alarm Code

Short Description

There are a large number of cleared alarms, so it is difficulty for the user to find out usefulinformation of the large number of cleared alarms. To help the user to analyze the largenumber of cleared alarms so as to find out useful information, the OMM provides the alarmmeasurement and analysis function. Measuring alarms based on alarm code helps themaintenance personnel to know which alarm occur frequently so as to understand whattypes of problems the system suffers.

Prerequisites


Context

Alarm measurement and analysis function adopt a mode similar to data mining. Itmeasures and analyzes the cleared alarms in the database to find out useful information.

Steps


2. Choose Analysis > Alarm Analysis > By Alarm Code > Top 10 to display theAnalysis window, as shown in Figure 5-12.

5-13



Figure 5-12 Ten Most Frequent Alarm Codes

3. Click button or press to display the statistics result in a graph.

4. Click button or press to display all the cleared alarms of this code.

5. To view 50 most frequent alarm codes, choose Analysis > Alarm Analysis > ByAlarm Code > Top 50.

6. To view 100 most frequent alarm codes, choose Analysis > Alarm Analysis > ByAlarm Code > Top 100.

End of Steps

Result

Viewed 10, 50 and 100 most frequent alarm codes.

5.9 Collecting Alarm Statistics by NE

Short Description

There are a large number of cleared alarms, so it is difficulty for the user to find out usefulinformation of the large number of cleared alarms. To help the user to analyze the largenumber of cleared alarms so as to find out useful information, the OMM provides thealarm measurement and analysis function. Measuring alarms based on NE helps themaintenance personnel to know on which NEs alarms are generated most frequentlystrengthen monitoring on the NEs.

Prerequisites


5-14



Context


Steps


2. ChooseAnalysis > AlarmAnalysis > ByNE > Top 10 to display theAnalysiswindowas shown in Figure 5-13.

Figure 5-13 Top 10 NEs

3. Click button or press to display the statistics result in a graph, as shownin Figure 5-14.

5-15



Figure 5-14 Statistics Result Displayed in Graph

4. Select a record and click button or press . All the cleared alarms that aregenerated on the NE are displayed.

5. To view the top 50 NEs on which alarms are generated most frequently, chooseAnalysis > Alarm Analysis > By NE > Top 50.

6. To view the top 100 NEs on which alarms are generated most frequently, chooseAnalysis > Alarm Analysis > By NE > Top 100.

End of Steps

Result

Viewed the top 10, top 50 and top 100 NEs on which alarms are generated most frequently.

5.10 Collecting Alarm Statistics by Time

Short Description

There are a large number of cleared alarms, so it is difficulty for the user to find out usefulinformation of the large number of cleared alarms. To help the user to analyze the largenumber of cleared alarms so as to find out useful information, the OMM provides thealarm measurement and analysis function. Measuring alarms based on time helps themaintenance personnel to know the period when alarms are generated frequently so as tostrengthen monitoring during the period.

Prerequisites


5-16



Context


Steps


2. Choose Analysis > Alarm Analysis > By Time > By Hour to display the Analysiswindow, as shown in Figure 5-15.

Figure 5-15 Alarm Statistics by Hour

3. Click button or press to display the statistics result in a graph, as shownin Figure 5-16.

5-17



Figure 5-16 Statistics Result Displayed in Graph

4. Select a record and click button or press . All the cleared alarms that aregenerated in this period of time are displayed.

5. To view the dates when alarms are generated frequently, choose Analysis > AlarmAnalysis > By Time > By Date.

6. To view the weeks when alarms are generated frequently, choose Analysis > AlarmAnalysis > By Time > By Week.

End of Steps

Result

Viewed alarms with different cycle.

5.11 Customizing Alarm Statistics

Short Description

There are a large number of cleared alarms, so it is difficulty for the user to find out usefulinformation of the large number of cleared alarms. To help the user to analyze the largenumber of cleared alarms so as to find out useful information, the OMM provides thealarm measurement and analysis function. The function includes three measurement andanalysis modes (by alarm code, by NE, and by time). The user can also customize themeasurement and analysis mode.

Prerequisites


5-18



Context


Steps


2. Choose Analysis > Alarm Analysis > Statistic to display the Analysis window.

3. Click button on the toolbar or press to display the Add Statistic window,as shown in Figure 5-17.

Figure 5-17 Add Statistic

4. On the Stat. Parameter tab of the Add Statistic dialog box, specify the occurrencetimes or average period for Stat. indicator and set the statistics object (alarm code,location, severity, alarm type, or time).l Alarm measurement and analysis is conducted based on the option specified in

the Stat. indicator pane.

5-19



l Alarm measurement and analysis measures the index specified in Stat. Objectpane, obtains the index values and then sort them.

5. On the Stat. Range tab in the Add Statistic dialog box, set the parameters, as shownin Figure 5-18.

Figure 5-18 Statistics Range

6. Specify a name and click OK. The customized measurement and analysis mode issaved for later use.

7. After the measurement and analysis conditions are set, you can start measurementand analysis, and then query the statistics result, as shown in Figure 5-19.

5-20



Figure 5-19 Customized Statistics Result

End of Steps

Result

Viewed alarm result which has customized.

Follow-Up Action

After finish the statistic configuration, click Export as Task in Add Statistic dialog boxcan save those setting into a task template which will be added to the Alarm Stat. Taskmanagement list. Also, you can create a statistic task by Alarm Stat. Task management.In the Alarm Management view, select Analysis > Alarm Analysis > Statistic Taskmenu to open Alarm Stat. Task management window.

5.12 Viewing Board CPU UsageShort Description

This function is helpful to conveniently observe the CPU usages of boards.

Context

The diagnosis management module sends a command to observe the CPU of a specifiedboard, requiring to report the CPU usage of the board every 2 seconds to the networkmanagement system for data analysis. The networkmanagement system presents a curveto indicate the CPU usage.

Steps

1. Choose Views > Fault Management > Diagnosis Management to open theDiagnosis Management window.

2. Select a 802.16e BTS node for CPU observation from the navigation tree in the leftpane.

5-21



3. Choose Operation > CPU Observation to open the CPU Observation window, asshown in Figure 5-20.

Figure 5-20 CPU Observation

4. Click button on the toolbar or choose Command > Set and the Set dialog boxappears, as shown in Figure 5-21.

Figure 5-21 Setting the Observation Object

5. Select a board to be observed and click OK.

6. Click button on the toolbar or choose Command > Start to start a CPU observationprocess. The result is as shown in Figure 5-22.l CPU observation can be performed on only one client at a time.l Observation objects can be selected only once. If the same object is selected

repeatedly, the systemwill gives amessage saying The observation task has beencreated or is running in another window.

5-22



l A maximum of 8 objects can be observed at the same time. To observe multipleobjects simultaneously, enable CPU observation tasks one by one. The longestinterval of starting observation tasks is 10 s.

l If the connection is broken during a CPU observation, the system will give a noti-fication.

Figure 5-22 CPU Observation Result

7. Click button on the toolbar or choose Command > Option and the Option dialogbox appears, as shown in Figure 5-23.l Save overthreshold data: Save only the CPU usage data that exceeds the

threshold.l Save all data: Save all data of the CPU usage.l Do not save any data: Do not save any data of the CPU usage.l Threshold information: Set a CPU usage threshold, which is a global threshold.

Figure 5-23 Setting CPU Usage Data Save Mode and Threshold

8. Click button on the toolbar or choose Command > Query History Data and theQuery History Data dialog box appears, as shown in Figure 5-24.l Only the history CPU usage data of the object that is being observed can be

queried.l Only the top 1000 records meeting the conditions can be queried.

5-23



l History data can be saved as a text file or an Excel file.l If no result is available, the system will give a message saying no data to save

when you click Save.

Figure 5-24 Querying History CPU Usage Data

End of Steps

5.13 Querying Original Performance Data

Short Description

This function is helpful to query performance data collected by the performance moduleaccording to the customized conditions.

Context

The performance module supports query by NE location and query by time and groupquery. Performance objects and indices can be customized.

Steps

1. ChooseViews > PerformanceManagement to open thePerformanceManagementwindow.

2. Choose Performance Management > Query Raw Data to open theQuery Raw Datawindow.

5-24



3. Choose Query by Performance Object from the drop-down list in the QueryCondition tab and click Advanced. The Advance window appears, as shown inFigure 5-25.

Figure 5-25 Advanced Query

4. Set query conditions in Select position, Select date, Select hour interval, Selectperformance object attributes and specify group query conditions, as shown inFigure 5-26.

5-25



Figure 5-26 Setting Query Conditions

5. Click OK to return to the Query Raw Data window.

6. Click Local Query to display the query result.

End of Steps

5.14 Collecting Service Data

Short Description

The signaling and data collection function is to trace signaling and data over variousinterfaces such as R1 and R6, monitor initial access, traffic flows, release and handoffprocedures in real time and provide user level or NE level success/failure causes,resource occupation and other key information.

Prerequisites

l The ZXMBW R9110 client has been started and has logged on to the server.l Signaling and global data have been collected.

5-26



Context

Configure the task to be observed in the , including the NE whose data has beencollected, service options, user's MAC address, cell number and segment number andthen synchronize the task to the service analysis tool. The NE agent judges and filtersthe task and sends the data reported by services to the to resolve, display and save.

Steps

1. Choose Views > System Tools > Service Analysis to open the Service Analysiswindow.

2. Click or choose Service Analysis > Service Data Collection to open the ServiceData Collection window.

3. Select NE.

a. Click button or choose Operation > Select NE to open the Select NE window.

b. On the topology tree in the left pane, select NE and click button, the NE whichwas selected appear in the right pane.

c. Click OK, select NE is completed.

d. Delete NE. select NE in the right pane and click button.

4. Choose service item in the Service ltem tab.

5. Input filter parameter in the Filter Parameter pane.

6. Input user which need tailed in the MAC address, click Insert, add user which needobserved.

Note:l This filter parameter is not obligatory.l Collecting Data must before Input MAC address.l Click the drop-down menu to the right side of MAC address to check all input

MAC addresses. You can query these MAC addresses using key word filtering,or copy and paste them. This feature helps to significantly increase the monitoringtask creation efficiency when some terminals need to be traced repeatedly.

7. Select an NE in NE drop-down list and click add to add it to the candidate box below.

Note:

This filter parameter is not obligatory.

5-27



8. Set Task time and Auto save option in the Common Setting pane, as shown inFigure 5-27.

Figure 5-27 Common Setting

Note:

Defaulted Max. duration is one hour. Task will pause, when Max. duration arrive. Thefiles which auto saved have been saved in ums-svr\rundata\zxcomc\cbwa\sapin the server,according tosession ID of client and IP of client.

9. Click button or choose Operation > Synchronize task, the Ordinary Work Modeappear in the foot of Service Data Collection pane,as shown in Figure 5-28.

Figure 5-28 Ordinary Work Mode

Note:

NE Status will turn yellow from green, when task setting become. It represent taskbecomed. User need synchronize task again.

End of Steps

Result

When subscriber station was connected and accorded with NE task which user setting, thedata appear in Signaling Access Service Flow Release Handoff and Pro-Handoffpane.

5-28



5.15 Saving Signaling and Global Data

Short Description

The collected signaling and global data can be saved for further analysis.

Prerequisites

Signaling and global data have been collected.

Context

Configure the task to be observed in the OMC, including the NE whose data has beencollected, service options, user's MAC address, cell number and Segment number andthen synchronize the task to the service analysis tool NE agent. The NE agent judges andfilters the task and sends the data reported by services to the OMC to resolve, display andsave.

Steps

1. Choose Views > System Tools > Service Analysis to open the Service Analysiswindow.

2. Click button or choose Service Analysis > Service Data Collection to open theService Data Collection window.

3. Double-click a data to be expanded in the Service Data table in right pane of theService Data Collection window to expand the data tree.

4. In the Service Data Collection window, click button or button on the toolbar orchoose Tools > Save All or Tools > Save Selected, the Save dialog box appears.Enter a file name and click Save.

Note:

Service analysis support that file style be saved compressed file(.sap ) or text file (.txt).

l Compressed file has been opened by Serverice Data Reade.l Text file has been opend by text editor.

End of Steps

5-29



5.16 Customizing Auto-Test Task

Short Description

On the site, when the maintenance personnel want to learn the running of multiple boards,they can customize a diagnosis task for auto test. In this way, the onsite information canbe obtains efficiently.

Context

Create a task for testing certain boards automatically through the task managementfunction in diagnosis test. You can set a period for the system to automatically start thetest.

Task Management provides two functions:

l Auto: The newly created task can be automatically executed according to the specifiedtime.

l Batch: A task can contain multiple board test tasks at a time.

Steps

1. Choose Views > Fault Management > Diagnosis Management to display theDiagnosis Management window.

2. Choose Management > Task Management to open the Task Management window,as shown in Figure 5-29.

Figure 5-29 Task Management

5-30



3. Choose Command > New Task and the New Task dialog box appears.

4. Enter a task name and specify Period, Run time, Start date and End date, as shownin Figure 5-30.

Figure 5-30 Creating a Test Task

5. Click OK. The new task is displayed in the task list of the Task Management window,as shown in Figure 5-31.

Figure 5-31 Task List

Note:l If the Status of a task is Idle, it indicates that the task is in the idle state and no

object is specified.l If the Status of a task is Overtime, it indicates that the task execution time is

earlier than the current time.

6. Create test objects for the created task.

5-31



a. Expand the node tree in the left pane of the window and select the required racknode. The rack diagram is displayed in the right pane of the window. Select theboard to be tested, right-click, and then choose Add to Task to display the SelectTask dialog box.

b. In the Select Task dialog box, select the new task board auto-test task from theTask List, and then click OK.

7. Open the Task Management view of Diagnosis management, select the new taskin the Task List. The new test object is displayed in the Test Object List, and theStatus of the object is Idle, as shown in Figure 5-32.

Figure 5-32 Test Object List

In the Test Object List, select the test object record, right-click, and then chooseModify. Then you can view the selected board for the test. Right-click and chooseDelete, then you can delete the board selected for the test.

8. Select a test task in the Task List, right-click and choose Run to start the auto-test.

9. After the board test is complete, select the required object in the Test Object List,right-click, and then choose Query Result to display the Period Board Test Resultwindow.

Note:

If the link break happens to the system, the test result shows timeout.

10. In the Board Test Result list, select the required board type. Then the detailed testinformation is displayed in the Element Test Result list. The running states of theboards are marked with different colors.

11. In the Board test time drop-down list, select different test time segments. Then youcan view the corresponding test results.

End of Steps

5-32



5.17 Spectrum Analysis

Short Description

For broadband interference, you can make a judgment by observing RSSI. Therefore,only narrowband interference is provided for spectrum analysis. Baseband analyses thespectrum features of each symbol to determine whether interference exists. If interferenceexists, the average value (sub-carrier number) at the peak value position (interferenceposition), variance with the peak value, and the percentage at which the threshold isexceeded are reported to the OMC.

Prerequisites

The OMC client must be started and must have accessed the server.

Context

Spectrum analysis analyzes the spectrum features of each symbol within theuser-specified scan cycle. When the user-specified threshold is exceeded, the result isreported to the OMC.

Steps

1. Choose Views > System Tools > RF Analysis to display the RF Analysis window.

2. Click button on the toolbar or choose RF Analysis > Spectrum Analysis. Then,the Spectrum Analysis window is displayed, as shown in Figure 5-33.

Figure 5-33 Spectrum Analysis

3. Click button on the toolbar or choose Operation > Set. Then, the Set dialog box isdisplayed, as shown in Figure 5-34.

5-33



Figure 5-34 Settings

4. Set the parameters on the Spectrum Scan and Interference Analysis tabs, and thenclick OK. Table 5-4 shows the description of the parameters.

Table 5-4 Spectrum Analysis Parameters


Report working duration Indicates the working hours of baseband interference analysis.

Report period Indicates the report interval of baseband interf

sj-20110411154055-008-zxmbw r9110

Documents