sjzl20073803-zxg10 itc (v6[1].10) maintenance manual

8/12/2019 Sjzl20073803-ZXG10 ITC (V6[1].10) Maintenance Manual

1/39

ZXG10 iTCTranscoder Pool

Maintenance Manual

Version 6.10

ZTE CORPORATIONZTE Plaza, Keji Road South,Hi-Tech Industrial Park,Nanshan District, Shenzhen,P. R. China518057Tel: (86) 755 26771900 800-9830-9830Fax: (86) 755 26772236URL: http://support.zte.com.cnE-mail: [email protected]
http://support.zte.com.cn/mailto:[email protected]:[email protected]://support.zte.com.cn/


2/39

LEGAL INFORMATION

Copyright 2006 ZTE CORPORATION.

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

All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTECORPORATION or of their respective owners.

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

are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from theuse of or reliance on the information contained herein.

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

covering the subject matter of this document. Except as expressly provided in any written license between ZTECORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter

herein.

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

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

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

Revision History

Date Revision No. Serial No. Reason for Issue

Jan 18, 2008 R1.0 sjzl20073803 First edition


3/39

ZTE CORPORATIONValues Your Comments & Suggestions!

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

Please fax to (86) 755-26772236 or mail to Documentation R&D Department, ZTECORPORATION, ZTE Plaza, A Wing, Keji Road South, Hi-Tech Industrial Park,Shenzhen, P. R. China 518057.

Thank you for your cooperation!

DocumentName

ZXG10 iTC (V6.10) Transcoder Pool Maintenance Manual

Product Version V6.10Document RevisionNumber

R1.0

Serial No. sjzl20073803 EquipmentInstallation Date

Presentation:

(Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization,Appearance)

Good Fair Average Poor Bad N/A

Accessibility:

(Contents, Index, Headings, Numbering, Glossary)


Your evaluationof thisdocumentation

Intelligibility:

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


Yoursuggestions forimprovement ofthisdocumentation

Please check the suggestions which you feel can improve this documentation:

Improve the overview/introduction Make it more concise/brief

Improve the Contents Add more step-by-step procedures/tutorials

Improve the organization Add more troubleshooting information

Include more figures Make it less technical

Add more examples Add more/better quick reference aids

Add more detail Improve the index

Other suggestions

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

__________________________________________________________________________

# Please feel free to write any comments on an attached sheet.

If you wish to be contacted regarding your comments, please complete the following:

Name Company

Postcode Address

Telephone E-mail


4/39

This page is intentionally blank.


5/39

Contents

About This Manual ............................................................i

Purpose................................................................................ i

Intended Audience ................................................................. i

Prerequisite Skill and Knowledge.............................................. i

What Is in This Manual ........................................................... i

Related Documentation.......................................................... ii

Conventions......................................................................... ii

How to Get in Touch............................................................. iii

Declaration of RoHS Compliance.....................................v

Chapter 1..........................................................................1

Maintenance Overview....................................................1

Safety Instructions................................................................1

Maintenance Content.............................................................1

Common Methods.................................................................2

Precautions..........................................................................3

Chapter 2..........................................................................7

Routine Maintenance.......................................................7

Routine Maintenance Classification ..........................................7

Daily Maintenance...........................................................7

Checking Equipment Room Environment ..................................8

Checking Communication between NM Server and Foreground ....9

Checking Current Alarms........................................................9

Checking History Alarms ...................................................... 10

Checking Real-time Virus Monitoring Alarm............................. 10

Checking Log Information .................................................... 11

Checking Alarm Box ............................................................ 11

Weekly Maintenance......................................................11

Checking NM Server Running Status ...................................... 12

Checking NM Server Hard Disk Space .................................... 12


6/39

Monthly Maintenance.....................................................13

Checking Remote Maintenance..............................................13

Checking Diagnostic Test......................................................13

Quarterly Maintenance...................................................14

Checking Backup Data Dump ................................................14

Checking Grounding Resistance.............................................14

Chapter 3........................................................................15

Emergency Maintenance................................................15

Emergency Maintenance Procedure ........................................15

NMS Emergency Handling.....................................................16

Chapter 4........................................................................19

Troubleshooting.............................................................19

Common Troubleshooting Procedure ......................................19

Troubleshooting Guide...................................................20

Handling OMP Board Hardware Fault ......................................20

Handling Inconsistent Active/Standby Clock Board Locked States........................................................................................21

Appendix A.....................................................................23

Abbreviations.................................................................23

Appendix B .....................................................................25

Tables.............................................................................25

Index .............................................................................. 105H27


7/39

Confidential and Proprietary Information of ZTE CORPORATION i

About This Manual

Purpose

This manual provides specifications, procedures and guidelines

that support maintenance of ZXG10 iTC (V6.10), includingroutine maintenance, emergency maintenance, and

troubleshooting.

Intended Audience

This document is intended for engineers and technicians whoperform maintenance operations on the ZXG10 iBSC and ZXG10iTC (V6.10).

Prerequisite Skill and Knowledge

To use this document effectively, users should have a generalunderstanding of wireless telecommunications technology.Familiarity with the following is helpful:

ZXG10 system and its various components

User interface on Base Station Controller (iBSC)

Local operating procedures

What Is in This Manual

This manual contains the following chapters:

TA B L E 1 - MA NU A L S UM M ARY

Section Summary

Chapter 1, MaintenanceOverview

Introduces safety instructions,maintenance content, common methods

and precautions.

Chapter 2, RoutineMaintenance

Describes routine maintenanceclassification, daily maintenance, weekly

maintenance, monthly maintenance and


8/39


ii Confidential and Proprietary Information of ZTE CORPORATION

Section Summary

quarterly maintenance.

Chapter 3, EmergencyMaintenance

Describes emergency maintenanceprocedure and NMS emergency handling.

Chapter 4,Troubleshooting

Describes the common troubleshootingprocedure and troubleshooting guide.

Appendix A,Abbreviations

List of abbreviations used in the manual.

Appendix B, Tables List of tables in the manual.

Index Contains the index of the manual.

Related Documentation

The following documentation is related to this manual:

ZXG10 iTC (V6.10) Transcoder Pool Documentation Guide

ZXG10 iTC (V6.10) Transcoder Pool Hardware Manual

ZXG10 iTC (V6.10) Transcoder Pool Hardware Installation

Manual

ZXG10 iTC (V6.10) Trnscoder Pool Technical Manual

Conventions

ZTE documents employ the following typographical conventions.

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

Typeface Meaning

Italics References to other Manuals and documents.

Quotes Links on screens.

Bold Menus, menu options, function names, inputfields, radio button names, check boxes, drop-

down lists, dialog box names, window names.CAPS Keys on the keyboard and buttons on screens

and company name.

Const ant wi dt h Text that you type, program code, files anddirectory names, and function names.

[ ] Optional parameters.

{ } Mandatory parameters.

| Select one of the parameters that are delimitedby it.

Note: Provides additional information about a

certain topic.

TypographicalConventions


9/39

About This Manual

Confidential and Proprietary Information of ZTE CORPORATION iii

Typeface Meaning

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

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

TA B L E 3 MO USE OP E R A T I O N CO NVENT I O NS

Typeface Meaning

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

Double-click Refers to quickly clicking the primary mouse button

(usually the left mouse button) twice.

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

Drag Refers to pressing and holding a mouse button andmoving the mouse.

How to Get in Touch

The following sections provide information on how to obtain

support for the documentation and the software.

If you have problems, questions, comments, or suggestions

regarding your product, contact us by e-mail [email protected]. You can also call our customer supportcenter at (86) 755 26771900 and (86) 800-9830-9830.

ZTE welcomes your comments and suggestions on the quality

and usefulness of this document. For further questions,comments, or suggestions on the documentation, you can

contact us by e-mail at [email protected]; or you can fax yourcomments and suggestions to (86) 755 26772236. You can alsobrowse our website at http://support.zte.com.cn, which contains

various interesting subjects like documentation, knowledge base,forum and service request.

Mouse

OperationConventions

CustomerSupport

DocumentationSupport


10/39


iv Confidential and Proprietary Information of ZTE CORPORATION



11/39

Confidential and Proprietary Information of ZTE CORPORATION v

Declaration of RoHSCompliance

To minimize the environmental impact and take moreresponsibility to the earth we live, this document shall serve asformal declaration that the ZXG10 iTC (V6.10) Transcoder Pool,manufactured by ZTE CORPORATION, is in compliance with the

Directive 2002/95/EC of the European Parliament - RoHS(Restriction of Hazardous Substances) with respect to thefollowing substances:

Lead (Pb)

Mercury (Hg)

Cadmium (Cd)

Hexavalent Chromium (Cr (VI))

PolyBrominated Biphenyls (PBBs)

PolyBrominated Diphenyl Ethers (PBDEs)

The ZXG10 iTC (V6.10) Transcoder Pool, manufactured by ZTECORPORATION meet the requirements of EU 2002/95/EC;however, some assemblies are customized to clientspecifications. Addition of specialized, customer-specifiedmaterials or processes which do not meet the requirements ofEU 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 CORPORATIONin written form.

This declaration is issued based on our current level of

knowledge. Since conditions of use are outside our control, ZTECORPORATION makes no warranties, express or implied, and

assumes no liability in connection with the use of thisinformation.


12/39


vi Confidential and Proprietary Information of ZTE CORPORATION



13/39

Confidential and Proprietary Information of ZTE CORPORATION 1

C h a p t e r

1

Maintenance Overview

This chapter describes the following topics:

Safety Instructions

Maintenance Content

Common Methods

Precautions

Safety Instructions

Only those professional personnel who have received BSSsystem training can perform maintenance for this equipment.

The basic requirements for BSS equipment maintenancepersonnel are:

Grasp basic theories of BSS system

Be familiar with BSS equipment principles and networking

Have proficient network optimization skills

Obey the local safety regulations and relevant operation

specifications during the maintenance and operation process toavoid injuries or equipment damage. The safety instructionsmentioned in this manual are supplementary to any local safety

regulations in place. In case of any conflict, local safetyregulations shall prevail.

ZTE shall not bear any liabilities incurred by violation ofuniversal safety operation requirements, or violation of safetystandards for designing, manufacturing and equipment usage.

Maintenance Content

Maintenance of ZXG10 iTC equipment includes:

Routine maintenance


14/39


2 Confidential and Proprietary Information of ZTE CORPORATION

Troubleshooting

Emergency maintenance

Routine maintenance refers to daily periodic maintenance,

including periodically checking the equipment running conditionsand handling problems. The purpose of routine maintenance isto find potential faults and handle them as early as possible.

Troubleshooting is the process of analyzing problems, handlingproblems and solving problems.

The purpose of emergency maintenance is to make theequipment rapidly restore normal running status and services.All problems that cause most users of the equipment unable towork normally or even the entire system failure are known asmajor problems. Emergency maintenance is applied in handlingsuch major problems to reduce users loss to the minimum

extent.

Common Methods

During maintenance, faults can be located through the following

methods:

Alarm monitoring is performed through alarm management and

operation log view interfaces in ZXG10 iTCM (V6.10), the localoperation and maintenance system.

The alarm management interface allows viewing and analyzingcurrent alarms, history alarms and common notificationsreported by the Network Element (NE). This ensures detectingnetwork operation abnormities in time, locating, isolating andtroubleshooting the fault as early as possible.

The operation log in user management allows tracing systemparameter modifications, locating relevant terminals andoperators, and detecting faults caused by improper operations.

Analyzing LED indicator status helps in fault detection. LEDindicators on the boards are observed to identify the faultposition.

This method requires familiarity with status of all LED indicatorsand their respective meanings.

This is done in the performance management interface of ZXG10iTCM (V6.10), including the following operations:

iTC system performance management and signaling tracing.

Routing

Maintenance

Troubleshooting

Emergency

Maintenance

Viewing Alarm

and OperationLogs

LED IndicatorStatus Analysis

Performance

Analysis


15/39

Chapter 1 - Maintenance Overview


Creating performance measurement tasks and generating

various performance reports. Through such informationanalysis, maintenance personnel can learn the load

distribution in the network and adjust network parameters in

time to improve network performance. Tracing iTC-related signaling through the signal tracing

interface. It facilitates checking various signaling flowsduring the commissioning and debugging process.

During iTC (V6.10) maintenance, the maintenance personnel use

test mobile phone, signaling analyzer, bit error analyzer, andother instruments to analyze, locate and troubleshoot faults.

When a fault occurs in a board, loosen the screws on the front

panel, unplug and plug the board or external connectors. Thismethod helps ensure good contact or handle abnormal processorproblems.

Comparison method refers to comparing the possibly faultyboard with another board in similar condition in the system(such as another board in the same slot of a different module).

Compare the running status, jumpers, and cable connections. Itcan be diagnosed through comparison whether the board isfaulty.

Interchange method refers to replacing the possibly faulty board

with a spare board or another identical normally-running board.If the fault disappears after replacement, then the board is

faulty.

When a system component is faulty, related boards or shelf canbe separated to judge whether the fault is caused by theparticular component.

This method refers to fault judgment through self-test after thesystem or board is powered-on again. Generally, during the

power-on and self-test process, LED indicators flash according tocertain rules, which can be used to diagnose whether the board

is faulty.

In practical operations, the above methods are often combinedwith maintenance personnels work experience to handle faults.

Precautions

Pay attention to the following aspects during maintenance:

Analysis UsingTools

Plugging and

Unplugging

Comparisonand

Interchange

IsolationMethod

Self-test

UsingExperience


16/39



Maintain normal temperature and humidity in the equipment

room. Keep the environment clean and tidy and free fromdust and moisture. Keep rodents or insects out of the

equipment room.

Keep common tools and instruments available in theequipment room. Such tools and instruments includeflathead screwdriver and cross screwdriver, signaling tester,

network cable pliers, multimeter, AC power supply,telephone line, network cable, antistatic wrist strap,

insulating tape, and common toolkit.

Keep software and documentation that may be used duringmaintenance in designated positions that are easy to reachto ensure they are available when needed.

Establish complete rules for equipment room maintenance andstandardize daily work of the maintenance personnel.

Maintain a detailed attendants log to provide detailedrecords about system operation, version, data change,upgrading and troubleshooting. It facilitates analysis and

troubleshooting after fault detection.

Keep a record of work shifts to specify the responsibilityclearly.

Ensure that the systems primary power is stable and reliable.Check the system grounding and lightning protection ground

periodically. Check the lightning protection system especiallybefore the stormy season and after thunderstorms to ensureit is in good conditions.

Strictly follow the equipment operation specifications.

Wear an antistatic wrist strap before touching any equipment

hardware.

All operations beyond daily maintenance are prohibited.

Note:

Operations beyond daily maintenance here mainly refer tocasually plugging/unplugging board, resetting, starting,changing over equipment, loading data or modifying data.Particularly, the Network Management database data can not bemodified casually.

Wear an antistatic wrist strap before performing any

operation on board.

Always prepare sufficient spare parts for boardplugging/unplugging or replacement.

EquipmentRequirements

MaintenanceRules

EquipmentOperations

BoardOperations


17/39

Chapter 1 - Maintenance Overview


Check spare parts periodically and maintain accurate

inventory of frequently used spare parts to ensure they arein good conditions. Ensure that the inventory contents are

unaffected by moisture or mould.

Keep spare parts and the replaced faulty parts in antistaticbags separately and label them appropriately foridentification purposes.

Never perform data synchronization and data modificationduring daytime when traffic is heavy; instead, perform such

operations in low-traffic hours such as midnight.

Perform operations that may cause large amount of datareported in low-traffic hours such as midnight.

Backup data before doing any data modification and make

records of data modifications. Do not delete backup datauntil the equipment has run properly for a period of time(usually a week) after data modification. Restore data in timeif there is any abnormality.

Perform backup for all data periodically for handing anypossible exception.

Databases, especially the performance measurement and

alarm database, should be observed on a regular basis (onceevery two weeks). If data volume of the database exceeds

the threshold value recommended in iTCM, delete uselessdata to avoid the error of disk overflow.

Only one user can have the super administrator right.

The super administrator sets different Network Management

passwords for different access rights.

The rights of login into server and client should be graded.

Note:

Maintenance personnel with different right levels are assignedwith different operation rights. Usually, there are three levels ofuser operation right:

Super administrator: user of this right level has the highestright and can perform all operations.

Advanced operator: user of this right level can performoperations including data configuration and modification,diagnosis and test, performance statistics, alarm query, andstatus query. The advanced operator can not manage otherusers.

Operator: user of this right level can only perform operationsincluding alarm query and status query.

DataMaintenance

Operation RightManagement


18/39



Passwords used to login into server and client should be

changed periodically.

Maintenance personnel can not casually change networkconfiguration of the server or the client.

Usage of unauthorized disks or CDs, installation of unrelatedsoftware, or playing games on the server or client terminalsis prohibited.

Each client should have a licensed antivirus software, and thereal-time detection function should be enabled. The viruslibrary should be updated in time (once a week).

A Windows NT server should have a licensed antivirussoftware, and the real-time detection function should beenabled. The virus library should be updated in time (once a

week).

Remove any detected faults as soon as possible. For faults thatcan not be resolved, contact the local ZTE office, and record thetroubleshooting procedure in details.

SystemAntivirus

ReportingFaults


19/39


C h a p t e r

2

Routine Maintenance

This chapter describes the following sections:

Routine Maintenance Classification

Daily Maintenance

Weekly Maintenance

Monthly Maintenance

Quarterly Maintenance

Routine Maintenance Classification

According to maintenance cycle, the routine maintenance ofZXG10 iTC falls into four categories:

Daily maintenance

Weekly maintenance

Monthly maintenance

Quarterly maintenance

Daily MaintenanceDuring daily maintenance for ZXG10 iTC, the following aspectsshould be checked:

Equipment room environment

Communication between Network Management (NM) serverand foreground

Current alarms

History alarms

Real-time virus monitoring alarms

Log information


20/39



Alarm box

Checking Equipment Room

Environment

Table 4 lists the items that should be checked for equipmentroom environment.

TA B L E 4 - DA I L Y MA I NT EN A NCE CH E C K IT EM S

Check Item Operation Guide Reference Standard

Temperature

Observe thethermometer indication

and make records toensure the equipmentworking in appropriatetemperature. Check therunning of airconditioners if thetemperature isabnormal.

Long-term workingtemperature: 0 C ~40 C

Short-term workingtemperature: -5 C ~45 C

Humidity

Observe the hygrometer

indication and makerecords to ensure theequipment working inappropriate humidity.

Check the running of airconditioners if thehumidity is abnormal.

Long-term workingrelative humidity: 20%~ 90%

Short-term working

relative humidity: 5%~ 95%

Lightingconditions

Check the normallighting conditions and

emergency lightingconditions. Repairdamaged lighting devicein time if there is any.

Lighting conditions arenormal and there is noplace in the equipmentroom with poor light.

Air conditioners

Check the running of airconditioners in theequipment roomperiodically and clean

the dustproof net of airconditioners periodically.Repair faulty airconditioner in time ifthere is any.

Air conditioners work

normally and can cooleffectively.

Cabinet doors

Check front door andback door of the cabinet

to ensure they areclosed.

Front door and backdoor of the cabinet areclosed.


21/39

Chapter 2 - Routine Maintenance


Checking Communication betweenNM Server and Foreground

To ensure normal foreground-background communication

Note:

Functions of ZXG10 iTC NM server are realized by Single BoardComputer of X86 (SBCX) at foreground. Checkingcommunication between NM server and foreground is actually

checking communication between SBCX and foreground.

Perform the following checking steps:

1. Enter DOS operation interface from NM server.

2. Run the pi ngcommand to check whether the IP address of

foreground OMP can be accessed, and check whethercommunication with the foreground is normal. If the IPaddress can not be accessed, check connectors and cableconnections between NM server and foreground to ensurethey are normal.

3. Use the dynamic management tool at NM client to query linkstatus to check whether foreground-backgroundcommunication link is established successfully. If the linkestablishment fails, check node configurations to ensure theyare correct.

END OF STEPS

The status of link connected with foreground IP address isOK.

Foreground-background communication link is establishedsuccessfully.

Checking Current AlarmsTo find potential faults by checking current alarms


1. Start Fault Managementin ZXG10 iTCM.

2. In the current alarm column, query whether there is anycurrent alarm. If there is current alarm, analyze the alarmcause and solve the problem.

END OF STEPS

Purpose

Operation

Guide

ReferenceStandard

Purpose

OperationGuide


22/39



There is no current real-time alarm.

Checking History Alarms

To find potential faults by checking history alarms within thepast 24 hours


1. Start Fault Management in ZXG10 iTCM and start thehistory alarm query.

2. Select all modules and all alarm levels, and set the querytime segment as from 0:00 of the day before to the currenttime.

3. Perform history alarm query. If there is any history alarm,record the process from alarm being reported to alarm beingrecovered. Analyze alarm causes and handle possiblepotential faults.

END OF STEPS

There is no history alarm.

Checking Real-time Virus MonitoringAlarm

To check whether NM server and client are infected by virus

Check the anti-virus real-time monitoring system installed on

NM server and client. If there is any virus detected, remove thevirus immediately by the anti-virus software.

The anti-virus real-time monitoring system has detected no virus.

ReferenceStandard

Purpose

OperationGuide

ReferenceStandard

Purpose

Operation

Guide

ReferenceStandard


23/39



Checking Log Information

To find abnormality in system running and operation process in

time

Check log information at NM client, including NM server startupand running log and foreground OMP running log. If there is anyabnormality in log information, analyze possible causes andhandle the problem.

Log information is normal.

Checking Alarm Box

To ensure acousto-optic alarm functions of the alarm box arenormal by checking working status and alarm status of thealarm box


1. Check RUN indicator and ALM indicator of the alarm box.

2. Compare the displayed alarm levels with those displayed inFault Management.

3. If the comparison result shows any abnormality, analyzepossible causes and handle the problem.

END OF STEPS

RUN indicator flickers regularly.

Alarm levels indicated by the ALM indicator are consistentwith those displayed in the current alarms in Fault

Management. Alarms that are suppressed are not displayed on the alarm

box.

Weekly MaintenanceDuring weekly maintenance for ZXG10 iTC, the following aspectsshould be checked:

NM server running status

Purpose

OperationGuide

ReferenceStandard

Purpose

OperationGuide

ReferenceStandard


24/39



NM server hard disk space

Checking NM Server Running Status

To check whether ZXG10 iTCM server works normally


1. Check the DOS operation interface at NM server during NMserver running to see whether there is any abnormal printinginformation.

2. Check relevant processes by the task manager.

3. If there is any abnormality, analyze possible causes and

handle the problem.

END OF STEPS

There is no abnormal message such as communication link

break or state machine down.

Checking NM Server Hard DiskSpace

To check whether hard disk space at NM server is sufficient


1. Open the explorer of NM server, right-click on each drive andselect Property.

2. Check each hard disk for the total space and remaining space.Especially check the system drive and the drive where NMserver program and database are installed.

For a hard disk of which the remaining space is less than2 GB, delete some useless files.

For a disk of which the occupied space increases rapidly,

find the reason and perform appropriate handlings.

Delete out-of-date logs if they occupy too much diskspace.

3. Check the occupancy of NM servers CPU and memory. Ifthere is any abnormal process, check the process details andperform appropriate handlings.

END OF STEPS

Purpose

OperationGuide

ReferenceStandard

Purpose

OperationGuide


25/39



The remaining spaces of system drive and the drive where NM

server program and database are installed are more than 2 GB.

Monthly MaintenanceDuring monthly maintenance for ZXG10 iTC, the followingaspects should be checked:

Remote maintenance

Diagnostic test

Checking Remote Maintenance

To check installation and usage of PCAnywhere to ensure thatequipment running can be checked remotely and remotetechnical support can be obtained successfully.


1. Ensure that the drivers of PCAnywhere and the modem areinstalled on NM server and client.

2. Ensure PCAnywhere runs normally and there is telephone

line dedicated for dial-up access.

3. Ensure that maintenance personnel in the equipment roomare proficient in using PCAnywhere.

4. For any abnormality, contact the local ZTE office.

END OF STEPS

PCAnywhere connection is normal and runs normally.

Checking Diagnostic TestTo check system performance through diagnostic test

Perform diagnostic test through the diagnostic test function.

Considering that diagnostic test would bring some load tosystem running, it is recommended to perform the diagnostictest at 2:00 in the morning to avoid traffic peak hours.

If there is any problem that can not be located, keep thediagnostic test result and contact the local ZTE office

ReferenceStandard

Purpose

OperationGuide

Reference

Standard

Purpose

OperationGuide


26/39



immediately to get technical support. Notify the project principal

in case that CPU load is more than 75%,

The diagnostic test result is normal.

Quarterly MaintenanceDuring quarterly maintenance for ZXG10 iTC, the following

aspects should be checked:

Backup data dump

Grounding resistance

Checking Backup Data Dump

To ensure backup data is backed up to other media to guaranteedata backup security

Copy the backup data to other media.

If there is any backup data, copy them to other media.

Checking Grounding Resistance

To ensure that the grounding resistance is within normal range

Measure the value of grounding resistance in equipment room. If

the value is too large, readjust the grounding bus bar.

It is required that the grounding resistance in equipment roomshould be less than 1 . If conditions permit, connect the

grounding cable to ground with independent grounding stub.

ReferenceStandard

Purpose

OperationGuide

ReferenceStandard

Purpose

OperationGuide

ReferenceStandard


27/39


C h a p t e r

3

Emergency Maintenance

This chapter describes the following topics:

Emergency Maintenance Procedure

NMS Emergency Handling

Emergency Maintenance Procedure

Steps of emergency maintenance are described as follows:

1. Check service

Collect users complaints, observe NM alarm information anddynamic data management, and confirm the emergency faultoccurred.

2. Locate fault

Extract data related to system performance and printingsand analyze the network faults. Observe the equipmentrunning and board indicators status. Determine whether thefault is caused by iTC equipment or other causes.

3. Analyze fault

If the fault is due to iTC equipment, perform analysis for on-site data, signaling and printing logs to troubleshoot the fault.

4. Get emergency helpCall ZTE customer support center for emergency help. ZTE

customer support center provides 24-hour hot line serviceand remote technical support.

ZTE customer support center hot line: 80098309830 or(86755) 26771900

Remote technical support:

According to information provided by the hot line,technical expert logs in the faulty local office remotely

and guides the customer to solve the problem. If theproblem is complex and difficult to handle, technical


28/39



support engineers will go to the site to perform

troubleshooting.

On-site technical support:

After arriving at the site, technical support engineers willtake emergency measures to restore normal

communication as soon as possible.

5. Restore services

Through ZTE remote telephone guidance or on-site technicalsupport, faults can be located and services can be restoredquickly. In case a fault can not be located in time, performboard changeover, resetting or restarting to restore systemservices.

6. Observe restored services

After services are restored, confirm that the system runningbecomes normal. Arrange attendants on duty during heavytraffic hours to monitor the network running to find problems

as early as possible if there is any.

7. Feed back results

After services are restored, collect data such as networkstatistics reports, system running logs and signaling tracingresults and feed back the troubleshooting results to ZTEcustomer support center. Relevant data should also be sentto ZTE Customer Service Department for analysis.

8. Communicate with customers

For level-1 faults, ZTE Customer Service Department submitsthe fault analysis report to the local ZTE office according tothe data obtained on the site. The local ZTE office then

communicates with customers about such faults.

NMS Emergency Handling

After catastrophic failure occurs in Network Management System(NMS), maintenance personnel should perform emergency

handling according to the following steps:

1. Check NM server status

In case any of the following fault symptoms occurs, checkNM server status:

All NM clients can not log in to NM server normally or NMclient status becomes abnormal after login to NM server.

All foreground NEs status become normal.

All alarm data and performance statistics data can not bereported normally.

The checking steps are described as follows:


29/39

Chapter 3 - Emergency Maintenance


i. Check whether there is any abnormal output information

in the DOS interface where NM server software is running.If it is found that NM server software has not run or run

abnormally, restart NM server software.

ii. Check the running status of Oracle database. UseSQLPLUS to check whether Oracle database can belogged in normally. If Oracle database can not be logged

in normally, restart the database instance of NM serversoftware in Services in Windows control panel. Check

whether the database configuration is correct throughOracle enterprise manager, and especially ensure that IPaddress of the server has not been modified incorrectly.For any abnormality, correct it in time.

iii. If NM server software can not run normally after theabove handling, power off the server and restart it.

iv. Use the latest antivirus software to check whether theoperating system has any virus. If there is any virusdetected, remove it in time.

Note:

Perform system configuration data backup before killing thevirus.

2. Check OMP running status

In case the following fault symptom occurs, check OMP

running status:

A few NEs in NMS have abnormal status. After modifyingconfiguration data, the configuration data fails to be

transmitted to foreground, and diagnostic test and dynamicdata management all fail.

The checking steps are described as follows:

i. On OMP panel, check RUN indicator to see whether itflicks normally at 1 Hz, and check whether ALM indicatoris OFF.

ii. If RUN indicator flickers abnormally and ALM indicator is

ON, it indicates that OMP board is faulty. Perform OMPboard changeover or resetting.

3. Check NM IP network status

If both NM server and foreground OMP board has normalstatus but NMS runs abnormally, check NM IP network status.The following are some common checking methods:

Run pi ng command at NM server to check whether IP

address of OMP can be accessed.

Run net st at command at NM server to view status of all

connections between NM server and foreground NEs, and

between NM server and NM clients.


30/39



Run pi ngcommand and t r acer command at NM client to

check whether the network is normal.

4. Check NM client status

The checking steps are described as follows:i. Check whether there is any abnormal output information

in the DOS interface where NM client software is running.If it is found that NM client software has not run or runabnormally, restart NM client software.

ii. Restart NM client and log in to NM server.

iii. After NM client logs in to NM server, enter the securitymanagement subsystem of NMS. Check whether it hasany login restriction policy such as forbidden IPs or

forbidden users. Delete relevant login restriction policyand login to NM server from the faulty NM client.


31/39


C h a p t e r

4

Troubleshooting

This chapter describes the following sections:

Common Troubleshooting Procedure

Troubleshooting Guide

Common Troubleshooting Procedure

Usually, the troubleshooting procedure contains the following

four stages:

1. Collect fault information

Fault information mainly comes from alarms and notificationsat NM clients, board indicator status, or customers faultcomplaints.

2. Analyze fault causes

After getting fault information, maintenance personnelanalyze fault causes and judge the probability of eachpossible fault cause, which is used as reference fortroubleshooting sequence.

3. Locate fault

After analyzing fault causes, maintenance personnel perform

troubleshooting, gradually exclude those causes that might

not cause the fault, and finally determine the fault cause.

4. Troubleshoot fault

After locating fault, maintenance personnel perform

troubleshooting with appropriate steps to make the systemrestore normal running.


32/39



Troubleshooting GuideThis section introduces the following two topics:

Handling OMP Board Hardware Fault

Handling Inconsistent Active/Standby Clock Board Locked

States

Handling OMP Board HardwareFault

OMP board is the system O&M center. It performs the followingfunctions:

Operation, maintenance and management of all foregroundNEs.

Receives NM server commands.

Reports various alarm information, traffic statisticsinformation, and tracing messages specified by user to NMserver.

Manages and distributes all foreground boards software

versions. All boards should load needed version files fromOMP during startup process.

RUN indicator on OMP panel does not flicker normally at 1 Hz,

instead, it repeats the process of flickering rapidly andturning OFF.

The NM alarm system indicates abnormal communication

with foreground. Data transmission to foreground fails.

Maintenance tools of foreground NEs such as signalingtracing and failure observation can not be used normally.

OMP board is down.

Perform the following troubleshooting steps:

1. Observe the status of RUN indicator on OMP board and judgewhether the board running is normal.

2. Perform active/standby OMP board changeover. Replace thefaulty board.

3. Check pins on the backplane to ensure they are of good

contact. Make sure that the IP address of OMP board has notbeen changed and DIP switches on the backplane are normal.

END OF STEPS

BackgroundKnowledge

FaultSymptoms

Troubleshooting


33/39

Chapter 4 - Troubleshooting


Handling InconsistentActive/Standby Clock Board Locked

States

When CLKG board adopts active/standby configuration, if thetwo CLKG boards have different clock tracing status, the system

running status can be normal but potential faults might exist. Inthis case, checking and appropriate handling are necessary toguarantee the active and standby clock boards are in normalstatus.

Note:

In this case, clock networking problem or clock source problemcan be excluded as the fault cause.

When CLKG board adopts active/standby configuration, theCLKG board inserted in one slot can not be locked (CATCHindicator is constantly ON, or CATCH indicator and TRACE

indicator flicker synchronously). However, the other CLKG boardinserted in another slot can be locked normally.

Two cases should be considered in handling this fault:

The reference clock is BITS clock

The reference clock is 8 Kbps line clock

Different troubleshooting steps should be performed for theabove two cases respectively.

If the reference clock is BITS clock, the troubleshootingrange can be limited to the slot and CLKG board. Perform thefollowing troubleshooting steps:

i. Make the CLKG board that can not be locked as thestandby board. Unplug and plug it again to decidewhether the fault is due to bad contact.

ii. After unplugging the board, check J5 connector in the slotto ensure that the pins of row 24 and row 25 are not bent.

iii. If reference is permitted, change the reference clock forCLKG to see whether CLKG can be locked. This helpsdecide whether the fault is due to CLKG board fault.

If the reference clock is 8 Kbps line clock, because its cabling

is independent, the active and standby CLKG boards have nocertain relations in 8 Kbps reference clock. It can not besimply diagnosed that CLKG board is faulty and furthertroubleshooting should be performed.

BackgroundKnowledge

FaultSymptoms

Troubleshooting


34/39



Note:

Although 8 Kbps line clock cablings of the two CLKG boards at

backplane are separate, they are from the same point, thus

clock networking problem and clock level problem can beexcluded as the fault cause.

Perform the following troubleshooting steps:

i. Insert the rear board RCKG1 firmly and connect to thecrystal connector of RJ45 to ensure good contact. If thefault still exists, perform the following steps.

ii. If there is another reference 8 Kbps line clock, change

the currently traced reference of CLKG to the standbyreference clock manually or through background.

Observe whether CLKG can be locked. If CLKG is locked,then it can be diagnosed that the fault range is in the slotor the rear board; otherwise, the fault is due to CLKGboard.

iii. If there is only one 8 Kbps line clock, unplug it from the

rear board RCKG1, replace it with a normal clockreference cable, and extract clock from another interfaceboard.

If the fault disappears, then it can be diagnosed that thefault range is in the clock cable, the interface board

extracting clock, and the rear board of interface board.

If the fault still exists, then it can be diagnosed that thefault range is in the CLKG board, the slot where CLKGboard is inserted, and RCKG1.

Use the interchange method to find the faulty parts andreplace them with normal ones.

END OF STEPS


35/39


A p p e n d i x

A

Abbreviations

Abbreviation Full Form

A

AIU Ater Interface Unit

AMR Adaptive MultiRate

B

BRS Bearer Subsystem

BSC Base Station Controller

BSP Board Support Package

C

CLKG Clock Generator

D

DBS Database Subsystem

DDN Defense Data Network

DSP Digital Signal Processor

E

EFR Enhanced Full Rate

F

FR Frame Relay

FSMU Far Sub-multiplexing Unit

G

GSM Global System for Mobile

H

HR Half Rate

I

IP Internet Protocol

L

LMT Local Maintenance Task


36/39



Abbreviation Full Form

M

MSC Mobile Switching Center

MTP Message Transfer Part

N

NE Network Element

O

OSS Operation Support Subsystem

OMS Operation & Maintenance Subsystem

P

PCM Pulse Code Modulation

PRCBU Pool Resource Configuration Basal Unit

R

RPE-LTP Regular Pulse Excitation-Long Term Prediction

S

SBCX Single Board Computer of X86

SCS System Control Subsystem

SIG Signaling Subsystem

SPB Signaling Processing Board

T

TCC Transcoder (iTC) Control Plane

TCSS Transcoder (iTC) Service Support Subsystem

TCU Transcoder and Rate Adaptation Unit

TCUP Transcoder (iTC) User Plane

TFO Tandem Free Operation

TS Time Slot

TRAU Transcoder Rate Adaptor Unit


37/39


A p p e n d i x B

Tables

Table 1 Chapter Summary ...................................................i

Table 2 Typographical Conventions ......................................ii

Table 3 Mouse Operation Conventions ................................. iii

Table 4 - Daily Maintenance Check Items...............................8


38/39





39/39

Index

8 Kbps line clock .................21Alarm Box.......................... 11backup ................................5Backup Data Dump .............14BITS clock..........................21BSS system..........................1CLKG.................................21common tools.......................4

Comparison method ..............3Current Alarms .....................9Daily Maintenance.................7data volume.........................5Diagnostic Test ...................13DOS operation interface ... 9, 12emergency help ..................15Emergency maintenance .. 2, 15equipment room ...................4Equipment Room Environment 8Grounding Resistance ..........14hard disk space...................12

History Alarms....................10Interchange method..............3

Isolation Method ...................3LED indicator........................2

licensed antivirus software .....6local safety regulations..........1Log Information.................. 10Monthly Maintenance........... 13occupancy ......................... 12OMP.................................. 20operation log........................2operation right .....................5

Oracle database.................. 17Quarterly Maintenance......... 14

Real-time Virus MonitoringAlarm............................ 10

Remote Maintenance........... 13right level............................5RJ45 ................................. 22Routine maintenance.............2SBCX ..................................9

self-test ..............................3task manager..................... 12Troubleshooting....................2troubleshooting procedure.... 19Weekly Maintenance............ 11

work experience ...................3

sjzl20073803-zxg10 itc (v6[1].10) maintenance manual

Documents