Sjzl20073803-ZXG10 ITC (V6 (1) .10) Maintenance Manual

ZXG10 iTC
Transcoder Pool
Maintenance Manual
Version 6.10
ZTE CORPORATION
ZTE Plaza, Keji Road South,
Hi-Tech Industrial Park,
Nanshan District, Shenzhen,
P. R. China
518057
Tel: (86) 755 26771900 800-9830-9830
Fax: (86) 755 26772236
URL: http://support.zte.com.cn
E-mail: doc@zte.com.cn

LEGAL INFORMATION

Copyright 2006 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
Date Revision No. Serial No. Reason for Issue
Jan 18, 2008 R1.0 sjzl20073803 First edition

ZTE CORPORATION
Values Your Comments & Suggestions!
Your opinion is of great value and will help us improve the quality of our product
documentation and offer better services to our customers.
Please fax to (86) 755-26772236 or mail to Documentation R&D Department, ZTE
CORPORATION, ZTE Plaza, A Wing, Keji Road South, Hi-Tech Industrial Park,
Shenzhen, P. R. China 518057.
Thank you for your cooperation!
Document
Name
ZXG10 iTC (V6.10) Transcoder Pool Maintenance Manual
Product Version V6.10
Document Revision
Number
R1.0
Serial No. sjzl20073803
Equipment
Installation Date

Presentation:
(Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization,
Appearance)
Good Fair Average Poor Bad N/A
Accessibility:
(Contents, Index, Headings, Numbering, Glossary)
Your evaluation
of this
documentation
I ntelligibility:
(Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)
Your
suggestions for
improvement of
this
documentation
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

This page is intentionally blank.
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

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

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), including
routine maintenance, emergency maintenance, and
troubleshooting.
Intended Audience
This document is intended for engineers and technicians who
perform maintenance operations on the ZXG10 iBSC and ZXG10
iTC (V6.10).
Prerequisite Skill and Knowledge
To use this document effectively, users should have a general
understanding 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:
TAB L E 1 - MANUAL SUMMARY
Section Summary
Chapter 1, Maintenance
Overview
Introduces safety instructions,
maintenance content, common methods
and precautions.
Chapter 2, Routine
Maintenance
Describes routine maintenance
classification, daily maintenance, weekly
maintenance, monthly maintenance and


ii Confidential and Proprietary Information of ZTE CORPORATION

Section Summary
quarterly maintenance.
Chapter 3, Emergency
Maintenance
Describes emergency maintenance
procedure and NMS emergency handling.
Chapter 4,
Troubleshooting
Describes the common troubleshooting
procedure 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.
TAB L E 2 TYPOGRAPHI CAL CONVENTI ONS
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.
Const ant wi dt h
Text that you type, program code, files and
directory names, and function names.
[ ] Optional parameters.
{ } Mandatory parameters.
| Select one of the parameters that are delimited
by it.

Note: Provides additional information about a
certain topic.
Typographical
Conventions

About This Manual

Confidential and Proprietary Information of ZTE CORPORATION iii
Typeface Meaning

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.

TAB L E 3 MOUSE OPERATI ON CONVENTI ONS
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.
Drag Refers to pressing and holding a mouse button and
moving 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 at
support@zte.com.cn. You can also call our customer support
center 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 doc@zte.com.cn; or you can fax your
comments and suggestions to (86) 755 26772236. You can also
browse our website at http://support.zte.com.cn, which contains
various interesting subjects like documentation, knowledge base,
forum and service request.
Mouse
Operation
Conventions
Customer
Support
Documentation
Support


iv Confidential and Proprietary Information of ZTE CORPORATION


Confidential and Proprietary Information of ZTE CORPORATION v
Declaration of RoHS
Compliance

To minimize the environmental impact and take more
responsibility to the earth we live, this document shall serve as
formal 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 the
following 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 ZTE
CORPORATION meet 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.


vi Confidential and Proprietary Information of ZTE CORPORATION

Confidential and Proprietary Information of ZTE CORPORATION 1
Ch 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 BSS
system training can perform maintenance for this equipment.
The basic requirements for BSS equipment maintenance
personnel 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 to
avoid injuries or equipment damage. The safety instructions
mentioned in this manual are supplementary to any local safety
regulations in place. In case of any conflict, local safety
regulations shall prevail.
ZTE shall not bear any liabilities incurred by violation of
universal safety operation requirements, or violation of safety
standards for designing, manufacturing and equipment usage.
Maintenance Content
Maintenance of ZXG10 iTC equipment includes:
Routine maintenance


2 Confidential and Proprietary Information of ZTE CORPORATION
Troubleshooting
Emergency maintenance
Routine maintenance refers to daily periodic maintenance,
including periodically checking the equipment running conditions
and handling problems. The purpose of routine maintenance is
to find potential faults and handle them as early as possible.

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

The purpose of emergency maintenance is to make the
equipment rapidly restore normal running status and services.
All problems that cause most users of the equipment unable to
work normally or even the entire system failure are known as
major problems. Emergency maintenance is applied in handling
such 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 local
operation and maintenance system.
The alarm management interface allows viewing and analyzing
current alarms, history alarms and common notifications
reported by the Network Element (NE). This ensures detecting
network operation abnormities in time, locating, isolating and
troubleshooting the fault as early as possible.
The operation log in user management allows tracing system
parameter modifications, locating relevant terminals and
operators, and detecting faults caused by improper operations.

Analyzing LED indicator status helps in fault detection. LED
indicators on the boards are observed to identify the fault
position.
This method requires familiarity with status of all LED indicators
and their respective meanings.

This is done in the performance management interface of ZXG10
iTCM (V6.10), including the following operations:
iTC system performance management and signaling tracing.
Routing
Maintenance
Troubleshooting
Emergency
Maintenance
Viewing Alarm
and Operation
Logs
LED Indicator
Status Analysis
Performance
Analysis

Chapter 1 - Maintenance Overview
Creating performance measurement tasks and generating
various performance reports. Through such information
analysis, 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 flows
during the commissioning and debugging process.

During iTC (V6.10) maintenance, the maintenance personnel use
test mobile phone, signaling analyzer, bit error analyzer, and
other 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. This
method helps ensure good contact or handle abnormal processor
problems.

Comparison method refers to comparing the possibly faulty
board 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. It
can be diagnosed through comparison whether the board is
faulty.
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 can
be separated to judge whether the fault is caused by the
particular component.

This method refers to fault judgment through self-test after the
system or board is powered-on again. Generally, during the
power-on and self-test process, LED indicators flash according to
certain rules, which can be used to diagnose whether the board
is faulty.

In practical operations, the above methods are often combined
with maintenance personnels work experience to handle faults.
Precautions
Pay attention to the following aspects during maintenance:
Analysis Using
Tools
Plugging and
Unplugging
Comparison
and
Interchange
Isolation
Method
Self-test
Using
Experience


Maintain normal temperature and humidity in the equipment
room. Keep the environment clean and tidy and free from
dust and moisture. Keep rodents or insects out of the
equipment room.
Keep common tools and instruments available in the
equipment room. Such tools and instruments include
flathead 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 during
maintenance in designated positions that are easy to reach
to ensure they are available when needed.

Establish complete rules for equipment room maintenance and
standardize daily work of the maintenance personnel.
Maintain a detailed attendants log to provide detailed
records 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 responsibility
clearly.

Ensure that the systems primary power is stable and reliable.
Check the system grounding and lightning protection ground
periodically. Check the lightning protection system especially
before the stormy season and after thunderstorms to ensure
it 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 to
casually plugging/unplugging board, resetting, starting,
changing over equipment, loading data or modifying data.
Particularly, the Network Management database data can not be
modified casually.

Wear an antistatic wrist strap before performing any
operation on board.
Always prepare sufficient spare parts for board
plugging/unplugging or replacement.
Equipment
Requirements
Maintenance
Rules
Equipment
Operations
Board
Operations

Chapter 1 - Maintenance Overview
Check spare parts periodically and maintain accurate
inventory of frequently used spare parts to ensure they are
in good conditions. Ensure that the inventory contents are
unaffected by moisture or mould.
Keep spare parts and the replaced faulty parts in antistatic
bags separately and label them appropriately for
identification purposes.

Never perform data synchronization and data modification
during daytime when traffic is heavy; instead, perform such
operations in low-traffic hours such as midnight.
Perform operations that may cause large amount of data
reported in low-traffic hours such as midnight.
Backup data before doing any data modification and make
records of data modifications. Do not delete backup data
until the equipment has run properly for a period of time
(usually a week) after data modification. Restore data in time
if there is any abnormality.
Perform backup for all data periodically for handing any
possible exception.
Databases, especially the performance measurement and
alarm database, should be observed on a regular basis (once
every two weeks). If data volume of the database exceeds
the threshold value recommended in iTCM, delete useless
data 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 assigned
with different operation rights. Usually, there are three levels of
user operation right:
Super administrator: user of this right level has the highest
right and can perform all operations.
Advanced operator: user of this right level can perform
operations including data configuration and modification,
diagnosis and test, performance statistics, alarm query, and
status query. The advanced operator can not manage other
users.
Operator: user of this right level can only perform operations
including alarm query and status query.

Data
Maintenance
Operation Right
Management


Passwords used to login into server and client should be
changed periodically.

Maintenance personnel can not casually change network
configuration of the server or the client.
Usage of unauthorized disks or CDs, installation of unrelated
software, or playing games on the server or client terminals
is prohibited.
Each client should have a licensed antivirus software, and the
real-time detection function should be enabled. The virus
library should be updated in time (once a week).
A Windows NT server should have a licensed antivirus
software, and the real-time detection function should be
enabled. The virus library should be updated in time (once a
week).

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

System
Antivirus
Reporting
Faults

Ch 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 of
ZXG10 iTC falls into four categories:
Daily maintenance
Weekly maintenance
Monthly maintenance
Quarterly maintenance
Daily Maintenance
During daily maintenance for ZXG10 iTC, the following aspects
should be checked:
Equipment room environment
Communication between Network Management (NM) server
and foreground
Current alarms
History alarms
Real-time virus monitoring alarms
Log information


Alarm box
Checking Equipment Room
Environment
Table 4 lists the items that should be checked for equipment
room environment.
TAB L E 4 - DAI L Y MAI NTENA NCE CHECK I TEMS
Check Item Operation Guide Reference Standard
Temperature
Observe the
thermometer indication
and make records to
ensure the equipment
working in appropriate
temperature. Check the
running of air
conditioners if the
temperature is
abnormal.
Long-term working
temperature: 0 C ~
40 C
Short-term working
temperature: -5 C ~
45 C
Humidity
Observe the hygrometer
indication and make
records to ensure the
equipment working in
appropriate humidity.
Check the running of air
conditioners if the
humidity is abnormal.
Long-term working
relative humidity: 20%
~ 90%
Short-term working
relative humidity: 5%
~ 95%
Lighting
conditions
Check the normal
lighting conditions and
emergency lighting
conditions. Repair
damaged lighting device
in time if there is any.
Lighting conditions are
normal and there is no
place in the equipment
room with poor light.
Air conditioners
Check the running of air
conditioners in the
equipment room
periodically and clean
the dustproof net of air
conditioners periodically.
Repair faulty air
conditioner in time if
there is any.
Air conditioners work
normally and can cool
effectively.
Cabinet doors
Check front door and
back door of the cabinet
to ensure they are
closed.
Front door and back
door of the cabinet are
closed.

Chapter 2 - Routine Maintenance
Checking Communication between
NM Server and Foreground
To ensure normal foreground-background communication
Note:
Functions of ZXG10 iTC NM server are realized by Single Board
Computer of X86 (SBCX) at foreground. Checking
communication 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 ng command to check whether the IP address of
foreground OMP can be accessed, and check whether
communication with the foreground is normal. If the IP
address can not be accessed, check connectors and cable
connections between NM server and foreground to ensure
they are normal.
3. Use the dynamic management tool at NM client to query link
status to check whether foreground-background
communication link is established successfully. If the link
establishment fails, check node configurations to ensure they
are correct.
END OF STEPS

The status of link connected with foreground IP address is
OK.
Foreground-background communication link is established
successfully.
Checking Current Alarms
To find potential faults by checking current alarms

1. Start Fault Management in ZXG10 iTCM.
2. In the current alarm column, query whether there is any
current alarm. If there is current alarm, analyze the alarm
cause and solve the problem.
END OF STEPS
Purpose
Operation
Guide
Reference
Standard
Purpose
Operation
Guide



There is no current real-time alarm.

Checking History Alarms
To find potential faults by checking history alarms within the
past 24 hours

1. Start Fault Management in ZXG10 iTCM and start the
history alarm query.
2. Select all modules and all alarm levels, and set the query
time segment as from 0:00 of the day before to the current
time.
3. Perform history alarm query. If there is any history alarm,
record the process from alarm being reported to alarm being
recovered. Analyze alarm causes and handle possible
potential faults.
END OF STEPS

There is no history alarm.

Checking Real-time Virus Monitoring
Alarm
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 the
virus immediately by the anti-virus software.

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

Reference
Standard
Purpose
Operation
Guide
Reference
Standard
Purpose
Operation
Guide
Reference
Standard

Checking Log Information
To find abnormality in system running and operation process in
time

Check log information at NM client, including NM server startup
and running log and foreground OMP running log. If there is any
abnormality in log information, analyze possible causes and
handle the problem.

Log information is normal.

Checking Alarm Box
To ensure acousto-optic alarm functions of the alarm box are
normal by checking working status and alarm status of the
alarm box

1. Check RUN indicator and ALM indicator of the alarm box.
2. Compare the displayed alarm levels with those displayed in
Fault Management.
3. If the comparison result shows any abnormality, analyze
possible causes and handle the problem.
END OF STEPS

RUN indicator flickers regularly.
Alarm levels indicated by the ALM indicator are consistent
with those displayed in the current alarms in Fault
Management.
Alarms that are suppressed are not displayed on the alarm
box.
Weekly Maintenance
During weekly maintenance for ZXG10 iTC, the following aspects
should be checked:
NM server running status
Purpose
Operation
Guide
Reference
Standard
Purpose
Operation
Guide
Reference
Standard


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 NM
server running to see whether there is any abnormal printing
information.
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 Disk
Space
To check whether hard disk space at NM server is sufficient

1. Open the explorer of NM server, right-click on each drive and
select Property.
2. Check each hard disk for the total space and remaining space.
Especially check the system drive and the drive where NM
server program and database are installed.
For a hard disk of which the remaining space is less than
2 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 disk
space.
3. Check the occupancy of NM servers CPU and memory. If
there is any abnormal process, check the process details and
perform appropriate handlings.
END OF STEPS

Purpose
Operation
Guide
Reference
Standard
Purpose
Operation
Guide

The remaining spaces of system drive and the drive where NM
server program and database are installed are more than 2 GB.
Monthly Maintenance
During monthly maintenance for ZXG10 iTC, the following
aspects should be checked:
Remote maintenance
Diagnostic test
Checking Remote Maintenance
To check installation and usage of PCAnywhere to ensure that
equipment running can be checked remotely and remote
technical support can be obtained successfully.

1. Ensure that the drivers of PCAnywhere and the modem are
installed 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 room
are 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 Test
To check system performance through diagnostic test

Perform diagnostic test through the diagnostic test function.
Considering that diagnostic test would bring some load to
system running, it is recommended to perform the diagnostic
test at 2:00 in the morning to avoid traffic peak hours.
If there is any problem that can not be located, keep the
diagnostic test result and contact the local ZTE office
Reference
Standard
Purpose
Operation
Guide
Reference
Standard
Purpose
Operation
Guide


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 Maintenance
During 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 guarantee
data 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 room
should be less than 1 . If conditions permit, connect the
grounding cable to ground with independent grounding stub.

Reference
Standard
Purpose
Operation
Guide
Reference
Standard
Purpose
Operation
Guide
Reference
Standard

Ch 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 and
dynamic data management, and confirm the emergency fault
occurred.
2. Locate fault
Extract data related to system performance and printings
and analyze the network faults. Observe the equipment
running and board indicators status. Determine whether the
fault 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 help
Call ZTE customer support center for emergency help. ZTE
customer support center provides 24-hour hot line service
and 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 the
problem is complex and difficult to handle, technical


support engineers will go to the site to perform
troubleshooting.
On-site technical support:
After arriving at the site, technical support engineers will
take emergency measures to restore normal
communication as soon as possible.
5. Restore services
Through ZTE remote telephone guidance or on-site technical
support, faults can be located and services can be restored
quickly. In case a fault can not be located in time, perform
board changeover, resetting or restarting to restore system
services.
6. Observe restored services
After services are restored, confirm that the system running
becomes normal. Arrange attendants on duty during heavy
traffic 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 network
statistics reports, system running logs and signaling tracing
results and feed back the troubleshooting results to ZTE
customer support center. Relevant data should also be sent
to ZTE Customer Service Department for analysis.
8. Communicate with customers
For level-1 faults, ZTE Customer Service Department submits
the fault analysis report to the local ZTE office according to
the 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, check
NM server status:
All NM clients can not log in to NM server normally or NM
client status becomes abnormal after login to NM server.
All foreground NEs status become normal.
All alarm data and performance statistics data can not be
reported normally.
The checking steps are described as follows:

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. Use
SQLPLUS to check whether Oracle database can be
logged in normally. If Oracle database can not be logged
in normally, restart the database instance of NM server
software in Services in Windows control panel. Check
whether the database configuration is correct through
Oracle enterprise manager, and especially ensure that IP
address 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 the
above handling, power off the server and restart it.
iv. Use the latest antivirus software to check whether the
operating system has any virus. If there is any virus
detected, remove it in time.
Note:
Perform system configuration data backup before killing the
virus.

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 modifying
configuration data, the configuration data fails to be
transmitted to foreground, and diagnostic test and dynamic
data management all fail.
i. On OMP panel, check RUN indicator to see whether it
flicks normally at 1 Hz, and check whether ALM indicator
is OFF.
ii. If RUN indicator flickers abnormally and ALM indicator is
ON, it indicates that OMP board is faulty. Perform OMP
board changeover or resetting.
3. Check NM IP network status
If both NM server and foreground OMP board has normal
status 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.


Run pi ng command and t r acer command at NM client to
check whether the network is normal.
4. Check NM client status
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 run
abnormally, 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 security
management subsystem of NMS. Check whether it has
any login restriction policy such as forbidden IPs or
forbidden users. Delete relevant login restriction policy
and login to NM server from the faulty NM client.

Ch 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 notifications
at NM clients, board indicator status, or customers fault
complaints.
2. Analyze fault causes
After getting fault information, maintenance personnel
analyze fault causes and judge the probability of each
possible fault cause, which is used as reference for
troubleshooting 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 system
restore normal running.


Troubleshooting Guide
This section introduces the following two topics:
Handling OMP Board Hardware Fault
Handling Inconsistent Active/Standby Clock Board Locked
States
Handling OMP Board Hardware
Fault
OMP board is the system O&M center. It performs the following
functions:
Operation, maintenance and management of all foreground
NEs.
Receives NM server commands.
Reports various alarm information, traffic statistics
information, and tracing messages specified by user to NM
server.
Manages and distributes all foreground boards software
versions. All boards should load needed version files from
OMP during startup process.

RUN indicator on OMP panel does not flicker normally at 1 Hz,
instead, it repeats the process of flickering rapidly and
turning OFF.
The NM alarm system indicates abnormal communication
with foreground. Data transmission to foreground fails.
Maintenance tools of foreground NEs such as signaling
tracing 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 judge
whether the board running is normal.
2. Perform active/standby OMP board changeover. Replace the
faulty board.
3. Check pins on the backplane to ensure they are of good
contact. Make sure that the IP address of OMP board has not
been changed and DIP switches on the backplane are normal.
END OF STEPS

Background
Knowledge
Fault
Symptoms
Troubleshooting

Chapter 4 - Troubleshooting
Handling Inconsistent
Active/Standby Clock Board Locked
States
When CLKG board adopts active/standby configuration, if the
two CLKG boards have different clock tracing status, the system
running status can be normal but potential faults might exist. In
this case, checking and appropriate handling are necessary to
guarantee the active and standby clock boards are in normal
status.
Note:
In this case, clock networking problem or clock source problem
can be excluded as the fault cause.

When CLKG board adopts active/standby configuration, the
CLKG board inserted in one slot can not be locked (CATCH
indicator is constantly ON, or CATCH indicator and TRACE
indicator flicker synchronously). However, the other CLKG board
inserted 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 the
above two cases respectively.
If the reference clock is BITS clock, the troubleshooting
range can be limited to the slot and CLKG board. Perform the
following troubleshooting steps:
i. Make the CLKG board that can not be locked as the
standby board. Unplug and plug it again to decide
whether the fault is due to bad contact.
ii. After unplugging the board, check J5 connector in the slot
to ensure that the pins of row 24 and row 25 are not bent.
iii. If reference is permitted, change the reference clock for
CLKG to see whether CLKG can be locked. This helps
decide 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 no
certain relations in 8 Kbps reference clock. It can not be
simply diagnosed that CLKG board is faulty and further
troubleshooting should be performed.
Background
Knowledge
Fault
Symptoms
Troubleshooting


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 be
excluded as the fault cause.

Perform the following troubleshooting steps:
i. Insert the rear board RCKG1 firmly and connect to the
crystal connector of RJ45 to ensure good contact. If the
fault 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 standby
reference 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 slot
or the rear board; otherwise, the fault is due to CLKG
board.
iii. If there is only one 8 Kbps line clock, unplug it from the
rear board RCKG1, replace it with a normal clock
reference cable, and extract clock from another interface
board.
If the fault disappears, then it can be diagnosed that the
fault 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 the
fault range is in the CLKG board, the slot where CLKG
board is inserted, and RCKG1.
Use the interchange method to find the faulty parts and
replace them with normal ones.
END OF STEPS

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


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


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




Index

8 Kbps line clock................. 21
Alarm Box.......................... 11
backup ................................5
Backup Data Dump ............. 14
BITS clock.......................... 21
BSS system..........................1
CLKG................................. 21
common tools.......................4
Comparison method ..............3
Current Alarms .....................9
Daily Maintenance.................7
data volume.........................5
Diagnostic Test ................... 13
DOS operation interface... 9, 12
emergency help .................. 15
Emergency maintenance .. 2, 15
equipment room ...................4
Equipment Room Environment 8
Grounding Resistance .......... 14
hard disk space................... 12
History Alarms.................... 10
Interchange method..............3
Isolation Method ...................3
LED indicator........................2
licensed antivirus software ..... 6
local safety regulations .......... 1
Log Information.................. 10
Monthly Maintenance........... 13
occupancy ......................... 12
OMP.................................. 20
operation log........................ 2
operation right ..................... 5
Oracle database.................. 17
Quarterly Maintenance......... 14
Real-time Virus Monitoring
Alarm............................ 10
Remote Maintenance........... 13
right level ............................ 5
RJ45 ................................. 22
Routine maintenance............. 2
SBCX .................................. 9
self-test .............................. 3
task manager..................... 12
Troubleshooting.................... 2
troubleshooting procedure.... 19
Weekly Maintenance............ 11
work experience ................... 3

Sjzl20073803-ZXG10 ITC (V6 (1) .10) Maintenance Manual

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Sjzl20073803-ZXG10 ITC (V6 (1) .10) Maintenance Manual

Transféré par

Droits d'auteur :

Formats disponibles

ZXG10 iTC

Vous aimerez peut-être aussi