ZXWR RNC (V3.07.200) Radio Network Controller Maintenance Manual (Emergency Maintenance) PDF

ZXW10 3G Mobile Communication WCDMA System
ZXWR RNC
Radio Network Controller
Maintenance Manual
(Emergency Maintenance)
Version 3.07.200
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 2005 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 noninfringement. 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.
The contents of this document and all policies of ZTE CORPORATION, including without limitation policies related to support
or training are subject to change without notice.
Revision History
Date
Revision No.
Serial No.
Description
2008/06/16
R1.0
sjzl20082064
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 Publications 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
ZXWR RNC Radio Network Controller Maintenance Manual (Emergency Maintenance)
Product
Version
V3.07.200
Document
Revision Number
R1.0
Equipment Installation Date

Presentation:
(Introductions, Procedures, Illustrations, Completeness, Level of Detail, Organization,
Appearance)
Good
Your
evaluation of
this
documentation
Fair
Average
Poor
Bad
N/A
Accessibility:
(Contents, Index, Headings, Numbering, Glossary)
Good
Fair
Average
Poor
Bad
N/A
Intelligibility:
(Language, Vocabulary, Readability & Clarity, Technical Accuracy, Content)
Good
Fair
Average
Poor
Bad
N/A
Please check the suggestions which you feel can improve this documentation:
Your
suggestions for
improvement
of 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 Maintenance Manual (Emergency Maintenance)..................vii
Purpose of this Maintenance Manual (Emergency Maintenance) ................................viii
Typographical Conventions..................................................................................... ix
Mouse Operation Conventions................................................................................. ix
Safety Signs........................................................................................................... x
How to Get in Touch .............................................................................................. xi
Customer Support.................................................................................................................. xi
Documentation Support.......................................................................................................... xi
Declaration of RoHS Compliance ............................................................ 13
Chapter 1...................................................................................... 15
Overview.................................................................................................. 15
Basic Principle ...................................................................................................... 16
Precaution............................................................................................................ 16
Chapter 2...................................................................................... 17
Emergency Maintenance Flow ................................................................ 17
Emergency Maintenance Flow................................................................................ 18
Service Check ...................................................................................................... 19
Fault Record......................................................................................................... 19
Fault Analysis and Location by Maintenance Personnel ............................................. 20
Asking for Emergency Aids .................................................................................... 20
Service Recovery.................................................................................................. 20
Service Observation.............................................................................................. 21
Information Record............................................................................................... 21
Chapter 3...................................................................................... 23
Emergency Maintenance on RNC Service Abnormality.......................... 23
Handling Flow....................................................................................................... 24
Check Equipment Room Environment..................................................................... 24
Handling User Service Interruption Caused by Abnormal Transmission...................... 25
Handling User Service Interruption Caused by Abnormal Radio Cell........................... 26
Handling User Service Interruption Caused by Wrong Modification of RNC Radio

Configuration Data................................................................................................ 26
Handling User Service Interruption Caused by RNC Board Fault ................................ 27
Chapter 4...................................................................................... 29
Data Backup and Recovery ..................................................................... 29
Appendix A ................................................................................... 31
Abnormality Record Table....................................................................... 31
Appendix B ................................................................................... 33
Troubleshooting Record Table................................................................ 33
Appendix C ................................................................................... 35
Equipment Emergency Maintenance Requisition................................... 35
Appendix D ................................................................................... 37
Common Indicators on RNC Panel ......................................................... 37
Appendix E ................................................................................... 39
Board Reset and Handover ..................................................................... 39
Influence of Reset and Handover ........................................................................... 39
Handover Mode .................................................................................................... 40
Appendix F.................................................................................... 41
Link/Cell Fault Confirmation Methods.................................................... 41
Checking whether NCP Link of Cell is Normal........................................................... 41
Checking whether Cell Establishment is Normal....................................................... 41
Figures.......................................................................................... 43
Tables ........................................................................................... 45
About this Maintenance

Manual (Emergency
Maintenance)
ZXW10 is a 3G mobile communications WCDMA system developed by ZTE
Corporation, which consists of ZXWN (ZTE WCDMA Core Network) and
ZXWR (ZTE WCDMA Radio Network Subsystem. ZXWR consists of ZXWR
RNC (Radio Network Controller), ZXWR BME (Base Multiplexing
Equipment), and ZXWR Node B radio base station.
The suite of manuals describes the working principles, installation,
operation and maintenance of ZXWR RNC software/hardware.
The whole suite of manuals includes:
Module
Manual
ZXWR RNC (V3.07.200) Radio Network Controller Documentation Guide
ZXWR RNC (V3.07.200) Radio Network Controller Technical Manual
ZXWR RNC (V3.07.200) Radio Network Controller Hardware Manual
ZXWR RNC (V3.07.200) Radio Network Controller
(Hardware)
RNC-related
Installation Manual
ZXWR RNC (V3.07.200) Radio Network Controller Maintenance Manual

(Troubleshooting)
(Routine Maintenance)
(Emergency Maintenance)
ZXWR RNC (V3.07.200) Radio Network Controller Feature Manual (DNC)
Confidential and Proprietary Information of ZTE CORPORATION
vii
ZXWR RNC (V3.07.200) Radio Network Controller Maintenance Manual (Emergency Maintenance)
Purpose of this Maintenance

Manual (Emergency Maintenance)
(Emergency Maintenance) is to help and guide carriers in emergency
maintenance, to help carriers rapidly locate the outburst system faults and
take necessary measures to recover the environment as soon as possible.
It also provides a better after-sales service for carriers through later stage
feedback of faults.
This manual contains the following chapters:
viii
Section
Summary
Chapter 1, Overview
Describes basic principles and precautions of emergency

maintenance.
Chapter 2, Emergency
Maintenance Flow
Describes the emergency maintenance flow and describes

each step in detail.
Chapter 3, Emergency
Maintenance on RNC Service
Abnormality
Describes the emergency handling methods on the

abnormality of RNC service.
Chapter 4, Data Backup and

Recovery
Describes the data backup and recovery before handling

with RNC faults.
Appendix A, Abnormality
Record Table
Provides abnormity record table during the maintenance.
Appendix B, Troubleshooting
Record Table
Provides troubleshooting record table during the

maintenance.
Appendix C, Equipment
Emergency Maintenance
Requisition
Provides equipment emergency maintenance requisition

during the maintenance.
Appendix D, Common
Indicators on RNC Panel
Describes status of common indicators on RNC panel.
Appendix E, Description of
Board Reset and Handover
Describes board reset and board handover.
Appendix F, Method of
Confirming Link/Cell Fault
Describes the method to confirm cell/link fault.
About this Maintenance Manual (Emergency Maintenance)
Typographical Conventions
ZTE documents employ with the following typographical conventions.
TABLE 1 TYPOGRAPHICAL CONVENTIONS
Typeface
Meaning
Italics
References to other guides 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.
Constant width
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.
Checkpoint: Indicates that a particular step needs to be
checked before proceeding further.
Tip: Indicates a suggestion or hint to make things easier or
more productive for the reader.
Mouse Operation Conventions

TABLE 2 MOUSE OPERATION CONVENTIONS
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.
ix
Safety Signs
TABLE 3 S AFETY SIGNS
Safety Signs
Meaning
Danger: Indicates an imminently hazardous situation, which if
not avoided, will result in death or serious injury. This signal
word should be limited to only extreme situations.
Warning: Indicates a potentially hazardous situation, which if
not avoided, could result in death or serious injury.
Caution: Indicates a potentially hazardous situation, which if not
avoided, could result in minor or moderate injury. It may also
be used to alert against unsafe practices.
Erosion: Beware of erosion.
Electric shock: There is a risk of electric shock.

Electrostatic: The device may be sensitive to static electricity.
Microwave: Beware of strong electromagnetic field.

Laser: Beware of strong laser beam.
No flammables: No flammables can be stored.
No touching: Do not touch.
No smoking: Smoking is forbidden.
About this Maintenance Manual (Emergency Maintenance)
How to Get in Touch

The following sections provide information on how to obtain support for
the documentation and the software.
Customer Support
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) 8009830-9830.
Documentation Support
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
explore
our
website
at
http://support.zte.com.cn, which contains various interesting subjects like
documentation, knowledge base, forum and service request.
xi
xii
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 ZXWR
RNC Radio Network Controller manufactured by ZTE CORPORATION are in
compliance with the SJ/T11364-2006 - RoHS (Restriction of Hazardous
Substances) with respect to the following substances:
Pb
Hg
Cd
Cr6+
PBB
PBDE
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.
For the specific RoHS, refer to ZTE CORPORATION Declaration Table of
RoHS Compliance.
13
14
Chapter
Overview
In this chapter, you will learn about:
Basic principles of emergency maintenance
Precautions of emergency maintenance
15
Basic Principle
Emergency maintenance is to recover the normal running of the
equipment quickly. The premise is that the system runs normally before
an emergent accident occurs. Refer to ZXWR RNC (V3.07.200) Radio
Network Controller Maintenance Manual (Troubleshooting) if the system
runs abnormally for a long time..
Observer the following basic emergency maintenance principles:
In the routine maintenance, the operators can refer to ZXWR RNC

emergency maintenance documents, past fault analysis and
experience in handling the faults.
When the emergent accident occurs, the maintenance personnel

should keep a sober mind first. Check whether the hardware and
transmission of RNC is normal, and judge whether this accident results
from RNC. If so, deal with the fault according to the emergency
accident handling plan or refer to the related procedures provided in
this manual.
Before/During/After handling the emergency, the maintenance

personnel should collect the equipment alarm information related to
this accident and send relevant fault handling report, equipment alarm
file and log file to ZTE CORPORATION for fault analysis and location, so
that it can provide better after-sales services for carriers.
Operators should, on a regular basis, organize related management

personnel and maintenance personnel for study and drill. Related
maintenance personnel should know more about the system in the
routine maintenance, especially the common exception information of
OMC alarm and the flashing of RNC panel indicators. They should
skilfully use the common tools such as data backup and recovery tool.
Precaution
Precautions during the emergency maintenance:
16
Locate the faults quickly. Some restoration operations (for example,

board reset) may have a huge impact on the running of the system, so
that such operations can be performed by or under the operators with
enough maintenance experience.
Attach all the contact information of ZTE CORPORATION in the

prominent positions, to facilitate user contact.
If the faults have a huge impact on the network running, the

maintenance personnel should contact ZTE Customer Support Center
or local ZTE office at the earliest possible time for technical support, no
matter whether they believe they can or cannot solve the fault.
Chapter
Emergency Maintenance Flow

Emergency maintenance flow
Handling methods of emergency maintenance
17
Emergency Maintenance Flow

The flow of the emergency maintenance is as shown in Figure 1.
FIGURE 1 EMERGENCY M AINTENANCE FLOW

Start
Service check
RNC fault?
Yes
Abnormality
record table
Abnormality record
Fault cause location and

analysis
Equipment emergency
maintenance advice note
No
Can eliminate the fault

at ones own?
Yes
Emergency aid
Service recovery
Service observation
Troubleshooting
record table
Information record
End
18
No
Notify relevant
personnel to solve the
fault
Chapter 2 - Emergency Maintenance Flow
It involves the following steps:

1. Service check
2. Record abnormalities and output Abnormality Record Table.
3. Make initial location and analysis of faults.
4. Launch the emergency aid, record and send Equipment Emergency
Maintenance Requisition.
5. Service recovery
6. Service observation
7. Information record, fill in Troubleshooting Record Table.
Service Check
When an emergency fault occurs, check whether there is any alarm for
board and link abnormality by watching OMC client alarm. If everything is
normal, check the status of radio resource cells. If their physical
connections and links with other NEs are normal (refer to Handling User
Service Interruption Caused by Abnormal Transmission). If everything is
normal, please notify NE (such as Node B, CN) personnel in charge of
other related equipment to assist in troubleshooting, or check the possible
source of faults according to other NE equipment emergency manuals.
If the connection between OMC client and RNC equipment is abnormal,
recover the links between OMC UMS and RNC first. For specific methods,
refer to Analysis and Troubleshooting of Hardware Fault in ZXWR RNC
(V3.07.200)
Radio
Network
Controller
Maintenance
Manual
(Troubleshooting).
Fault Record
Before/During the start of the emergency recovery plan or the fault
recovery, make records of the running version and phenomena in the
abnormality table (refer to Abnormality Record), especially information
referring to Service Check.
Back up OMC configuration data properly.
Caution: The abnormality record is very useful in emergency aid and the
subsequent problem analysis and summary. Therefore, be sure to fill a complete
abnormality record.
19
Fault Analysis and Location by

Maintenance Personnel
Determine the fault cause and take appropriate measures by referring to
Emergency Maintenance on RNC Service Abnormality.
Asking for Emergency Aids

If the services are not recovered after the start of the emergency recovery
plan or the troubleshooting procedure provided in this document, or it is a
critical system fault, ask for emergency aid immediately. ZTE
CORPORATION provides emergency aid channels through 7 x 24 hour
service hotlines, and remote and on-site technical support.
Service hotline
Hotline of ZTEs customer service center: 800-830-1118
Service fax: (0755)26770801.
In addition, provide the on-site fault record table wherever possible
(Refer to Equipment Emergency Maintenance) to allow ZTE
maintenance personnel to learn and locate the fault more easily.
Remote technical support

According to information provided at the service hotline, ZTE technical
support experts log on to the problematic site remotely. Experts can
solve common problems on the phone. If the problem is complex, ZTE
CORPORATION will send the maintenance experts to the site for onsite technical support.
On-site technical support

After the maintenance experts arrive at the site, they take emergency
maintenance actions to recover the communication as soon as possible.
Service Recovery
If the methods provided in this manual and remote emergency aid cannot
help to locate faults and recover services, switch, reset and replace boards
to recover the system service. These operations may give a great impact.
Refer to Appendix E and Appendix A of ZXWR RNC (V3.07.200) Radio
Network Controller Maintenance Manual (Troubleshooting) before the
operation.
20
Chapter 2 - Emergency Maintenance Flow
Caution:
Board handover, reset and replacement may have a great influence on the
system running. Therefore, refer to Appendix E and Appendix A of ZXWR RNC
(V3.07.200) Radio Network Controller Maintenance Manual (Troubleshooting)
before the operation.
Make records of the current status before any board handover and physical
location change.
Make records of each step and symptom occurring in the service recovery on
the site.
Service Observation
After the service recovery, make a further check to see whether the
system has recovered completely, to avoid any other problems. Refer to
(Troubleshooting).
In addition, arrange attendants in the period of service peak to make sure
to solve the problem in time (if any problem occurs).
Information Record
After the service recovery, collect the fault recovery procedures and
analyze the fault causes according to the fault handling record table. Refer
to Appendix B. If there is any emergency aid request, do feed back the
recovery results to ZTE service hotline.
21
22
Chapter
Emergency Maintenance on
RNC Service Abnormality
Emergency maintenance flow for RNC service abnormality
Maintenance procedures for RNC service abnormality
23
Handling Flow
The following describes procedures to check RNC emergency faults. The
handling procedure can change with specific situation. For example, skip
Steps 3 and 4 if there is no modifications on the configuration data.
1. Check the changes in the environment (such as temperature, humidity
and power supply) of the equipment room.
2. Handle the user service interruption caused by RNC board fault.
3. Handle the user service interruption caused by abnormal transmission.
4. Handle the user service interruption caused by abnormal radio cell.
5. Handle the user service interruption caused by the wrong modification
of RNC radio configuration data.
If the above steps cannot help in troubleshooting and solution, please
launch the emergency aid.
Check Equipment Room

Environment
The equipment runs normally within an appropriate temperature range.
Check whether the temperature in the equipment room, the running of the
rack fans, and the board temperature are normal. Check whether there
are any fan and temperature alarms via OMC UMS.
For the redundancy backup of the power supply, RNC supports two power
inputs. The failure of any one power supply will not impact the normal
running of the system. Any over-voltage/under-voltage and overcurrent/under-current on the input power will display on OMC UMS alarm
interface.
If there is any obvious abnormality, such as, the abnormal running of rack
fan, cool down the equipment by all means first and then replace the fan.
Handle other faults according to their specific causes.
24
Chapter 3 - Emergency Maintenance on RNC Service Abnormality
Handling
User
Service
Interruption Caused by Abnormal
Transmission
The methods to judge the user service interruption caused by abnormal
transmission:
1. On OMC unified UMS client, check whether the transmission links, such
as NCP, CCP, ALCAP, MTP3B links, fail (Refer to Checking whether NCP
Link of Cell is Normal).
2. On OMC unified UMS client, check whether there is any resource alarm
for the cell public transmission channel and No.7 link. Check whether
the alarm exists constantly and cannot recover.
3. Check the optical interface SD and E1 indicator of the interface board,
to judge the transmission line for normality.
i.
For APBE interface board, check the optical interface SD. The
indicator is solid on during the normal communication. Otherwise,
there may be faults with the optical fiber.
ii. For DTB interface board, check E1 indicator. The indicator is slowly
flashing (1 time/s) during the normal communication. Otherwise,
there may be faults on the connection. For example, solid on
indicates E1 link configuration but blocked.
Proposals to handling the link resource faults:
1. Check whether the data to be negotiated by such external NEs as Node
B, CN and RNC are consistent (such as NCP, CCP, MTP3B link, and ATM
address). If there is any abnormal configuration data, the cause may
be local NE or other NEs have modified the configuration data. Make
confirmation and modify them.
2. If there is not abnormality, perform the self-loop on optical interface or
IMA group at RNC side.
3. If the conditions allow (for example, the distance between NEs is very
small), perform the self-loop at the corresponding remote NE according
to link fault location. For example, for Iub link, perform the self-loop on
the optical interface of the interface board at Node B side. For Iu
interface, perform the self-loop on the optical interface of the interface
board at CN side.
4. If the fault disappears after the local self-loop, the cause may be the
abnormal running of the peer NE. If the peer NE becomes normal after
the self-loop, the cause is transmission network configuration fault.
5. If the fault still exists after the self-loop, check the optical fiber for
damages and exposing.
6. If the problems fail to be solved with all above methods, launch the
emergency aid, or reset the interface board (Please take care. For the
resetting operation, refer to Appendix E).
25
Handling User Service

Interruption Caused by Abnormal
Radio Cell
The methods to judge the user service interruption caused by abnormal
radio cell are:
1. On OMC unified UMS client, check whether the cell establishment is
normal (Refer to Method 2 in Appendix F).
2. Through Node B LMT, check whether the cell establishment is normal.
3. The abnormal activities take place in one or more cells, and all the
activities in this cell are abnormal or have a quite low success rate,
while radio processes originated in other cells run normally.
Proposals to handling radio cell establishment abnormality:
1. The possibility of RNC/CN failure is quite little if The radio processes
originated in other cells run normally pops up.
2. Check whether the cell is in block status.
3. Reset the cell.
4. Wait for the system to recover, and then check whether the fault still
exists.
Handling
User
Service
Interruption Caused by Wrong
Modification of RNC Radio
Configuration Data
The modification on radio configuration data may not immediately cause
the service abnormality. With the increase of users (such as the coming of
traffic peak time) and the change of user service types, various radio
problems can be caused, such as, low access rate of user service, unstable
service rate.
Proposals to handling such fault:
1. Log on to unified client of RNC OMC, click Tool Log Management,
and check RNC log management to see whether there is radio resource
configuration data modification.
26
Chapter 3 - Emergency Maintenance on RNC Service Abnormality
2. If there radio resource configuration data modification, back up the

current RNC configuration data.
3. Recover the data configuration of radio configuration.
4. Wait for the system to recover.
Caution: The radio resource data is based on such factors as onsite call model and
onsite landforms combining with network planning and optimization, so do not
modify it. To adjust the parameters, make a proper data backup beforehand.
Handling User Service

Interruption Caused by RNC
Board Fault
This section describes several types of board that have a close tie with the
normal running of services. They are to facilitate rapid location and
troubleshooting of faults.
1. Interface unit: APBE, DTB, IMAB, EIPI, GIPI which mainly provide the
data access of RNC Iu/Iub/Iur interface and are the termination of
AAL2/AAL5/ATM and IP over E1 link layer processing. Here, APBE
provides the optical fiber access (STM-1), and the optical interface SD
on the panel indicates its connection status. DTB supports E1 access
and E1 indicator on the panel indicates E1 connection status. IMAB and
EIPI are applied to RNC Iud, Iur, Iu-CS, and Iu-PS interface. They work
with DTB, providing ATM reversal multiplexing IMA E1 access and IP
over E1 access.
2. Switching unit: PSN, GLI, UIMC, UIMU and CHUB, which provide the
inter-board service exchange platform.
3. Processing unit: RCB and RUB, which process the upper layer protocols
of ZXWR RNC control plane and user plane.
Generally, the alarm function of OMC client and the flashing status of RNC
rack board can help to judge the failed board and its causes.
1. Log on to OMC unified client and click Tool Alarm Management.
Check OMC alarm function of RNC background, and then check
whether there is any board alarm the type of the alarm board.
2. Observe other indicators of the board.
The following is examples for the flashing of common indicators. For
detailed instructions, refer to Appendix D.
i.
Check ENUM on the board. In normal cases, it is solid off. If the

indicator is solid on or flashes, it indicates that the board is out of
position. Unplug and plug it to observe the status again.
27
ii. RUN indicator slowly flashes (frequency: 1 time/s) and ALM is solid
off, it indicates the normal running of the board. If other indicators
flash, it indicates that the board is not running normally at this time.
If RUN is solid off, it indicates the board self-test fails. If both RUN
and ALM flash slowly (1 time/s), it indicates that this board is under
active/standby handover. Wait for a while to see whether the board
recovers to its normal status.
iii. Check ACT on the board). If it is solid on, it indicates that this
board is an active board while if it is solid off, it indicates that it is a
standby one. This indicator is to locate active/standby handover
failure.
Proposals to handling such fault:
1. The alarm management information of RNC OMC background generally
indicates the alarm causes and recommended operation to eliminate
this alarm. Perform related operations according to such information.
2. Wait for RNC board to recover to its normal status, and observe
whether the user service restores to normal.
If indicators flash abnormally for long during the board running and the
background alarm still exists, try the following operations:
1. Reserve the alarm information.
2. Reset the alarm board or replace the board.
Caution: Resetting RNC boards may have a huge influence on services. Such as, to
reset RUB, it is necessary to re-create all cells and user services on this board. To
reset the interface board, it is necessary to re-create all bearers allocated on this
board. Therefore, do be careful when deciding to use this method.
28
Chapter
Data Backup and Recovery

Importance of data backup and recovery
Specific Operations of data backup and recovery
29
Before handling RNC emergency faults, back up the configuration data first.
On the one hand, the fault recovery may involve configuration data
modification, and the data can restore the onsite status to avoid the worse
case during the emergency fault recovery. On the other hand, reserve the
first-hand information for ZTEs maintenance and technical support
personnel and the technicians at the home front, to help to analyze and
locate problems better as well as to improve the system.
There are two methods to back up and recover RNC configuration data:
1. Create the database maintenance task.
After creating the database maintenance task, the system can
automatically back up the specified maintenance table according to the
maintenance time set by the task.
Refer to ZXWR RNC (V3.07.200) Radio
Maintenance Manual (Routine Operation).
Network
Controller
2. Manual backup and recovery of data table

If necessary, manually back up and recover the data table at any time.
Refer to ZXWR RNC (V3.07.200) Radio Network Controller Operation
Manual (Routine Operation). This method is quicker and more flexible,
better option in the emergency cases.
30
Appendix
Abnormality Record Table

The table below serves as an example only. It is better to optimize
according to actual RNC maintenance items.
Equipment name
Item
Fault
time
Equipment No.
Abnormality description
occurrence
Fault occurrence
scope
Program version
of active ROMP
Version
connected
B/CN
of
Node
OMC version
Board whose RNC
indicator
shows
abnormality
Serious alarm item

reported by OMC
Operation
information
OMC
log
of
31
For example, the environment of the equipment room: temperature

and humidity change. Record it if any.
Project
information
Abnormality query
information
Information
signal tracing
32
of
Including the resource name (such as service cell ID, ATM No.) whose
status is abnormal through query and abnormal contents. Record it if
there is any.
Obtain this part of information under the assistance of ZTEs remote

technical support personnel after emergency assistance request
launches.
Appendix
Troubleshooting Record Table

Equipment name
Fault
time
occurrence
Equipment No.
(HH-MM-DD-YY)
Fault elimination time
(HH-MM-DD-YY)
Fault type:
Fault source:
Fault phenomena:
Solution:
Summary:
Signature of the attendant:
Signature of the handling person:
33
34
Appendix
Equipment Emergency
Maintenance Requisition
This requisition is to notify ZTE technical support center by fax when the
carrier fails to solve the fault on his own. It is better to attach the on-site
fault record table with the fax, to allow ZTE personnel to locate and
eliminate the faults more easily.
The user should fill in the following fields.
Equipment
name
Complaint
time
(HH-MM-DD-YY)
Equipment
No.
Software
version
Complainant
Telephone
Complaint
company or
organization
Whether
in
warranty period
the
(
)
( )N
Abnormality Record Table (Please attach it on the blank below):
Details of the handling process (as detailed as possible):
Reviewed by:
Stamp of the department:
ZTE personnel should fill in the following fields:
Solution
Time of settlement
O Guide through telephone

O On-site support
O Remote maintenance
(HH-MM-DD-YY)
35
Handling result:
Handled by:
Stamp of the department:
Unresolved problems:
36
Appendix
Common Indicators on RNC

Panel
Status Name
RUN Status
ALM Status
Description
Normal
Flash at 1 Hz
Solid off
Normal running
Flash at 5 Hz
Solid off
The version is being downloaded
Flash at 5 Hz
The version download failed. The

board does not match the
configuration
and
cannot
download its version.
Flash at 1 Hz
Downloading
version
Solid on
Solid off
DEBUG version has successfully

downloaded VxWorks and is
waiting for downloading and
running the version.
RELEASE version indicates the
version download is successful
and the version is starting.
Self-test failure
Running
alarm
fault
Solid off
Flash at 5 Hz
The board self-test failed.
Solid off
Flash at 2 Hz
The startup of the operation

support system fails.
Flash at 5 Hz
Flash at 5 Hz
Getting the logical address fails.
Flash at 5 Hz
Flash at 2 Hz
The power-on of basic processes

fail or time out.
Flash at 5 Hz
Flash at 1 Hz
The kernel data area fails in

initialization.
Flash at 2 Hz
Flash at 5 Hz
Alarm of mismatch
version,
hardware
configurations.
Flash at 2 Hz
Flash at 2 Hz
The media plane communication

disconnects.
Flash at 2 Hz
Flash at 1 Hz
HW disconnects.
Flash at 1 Hz
Flash at 2 Hz
The link to OMP breaks.
among
and
37
Status Name
RUN Status
ALM Status
Description
Flash at 1 Hz
Flash at 1 Hz
Active/standby
under way.
No change
Solid on
handover
is
Hardware clock loses.
In addition to common indicators mentioned above, different boards have

their own indicators. For detailed description of the indicators, refer to
(Troubleshooting).
38
Appendix
Board Reset and Handover

Board reset is an operation that must be restarted in some faults. Hot
resetting means to restart the system when the system is being powered
on, so it is the software resetting. All related resets mentioned below are
hot ones.
To guarantee the normal system running and to avoid the abnormal
system running caused by resetting due to the board software and
hardware faults, back up important boards. At present, RNC boards that
support backup mode include ROMB, RCB, UIMC, UIMU, CHUB, CLKG, GLI
and PSN. The table below describes the board backup.
Backup Type
RNC Board Supporting Backup Mode
1+1 backup
ROMB, RCB, UIMC, UIMU, CHUB, CLKG
Load sharing (port backup)
GLI, PSN
Load sharing
RUB
Influence of Reset and Handover

In active/standby board configuration, boards whose reset do not have
influence on services include ROMB, UIMC, UIMU, CHUB, CLKG, GLI and
PSN.
In active/standby board configuration, resetting active RCB may cause the
loss of services borne on that board currently, but new services can access
after successful handover. Therefore, make RCB active/standby handover
in the case of low traffic. The resetting function of RUB is similar to that of
RCB, that is, the services borne on the current board may lose. Therefore,
reset with care.
39
Handover Mode
1. Normal manual handover at the background
Log on to OMC unified NM client, click Subnet Management NE
RNC ground resource management Rack Rack map to
expand the topology, and then right click the shortcut menu to select a
board.
2. Manual handover at the foreground
Reset the active board on RNC rack.
3. Automatic handover of the foreground faults
RNC system initiates switchover after detecting abnormalities.
40
Appendix
Link/Cell Fault Confirmation

Methods
The methods mentioned below should work with RNC OMC client.
The confirming method falls into two categories: One is for link (including
ALCAP, NCP, CCP, and AAL5) problem and the other is for normal
establishment of cell resources. The below will give examples.
Checking whether NCP Link of

Cell is Normal
Click OMC unified client Subnet-AA Manage NE $BBB$ RNC
ground
resource
management-BBB
NodeB
resource
management homing relation-x ATM configures xx, right click on
Status Query to check the operating and availability status of
NCP/CCP/ALCAP. If No fault, available pops up, it indicates normal link.
Checking whether Cell

Establishment is Normal
Click OMC unified client Subnet-AA Manage NE $BBB$ RNC
radio resource management-BBB Service cell CCC, right click on
Status Query to view the status of this cell. If it is in the status of
existing, unblocking, no failed resource, this cell runs normally. If No
existing or Resource fault, it indicates the cell does not establish or the
establishment fails.
AA indicates subnet No. BBB indicates RNC NE No. CCC indicates service
cell No. x indicates the resource flag to be queried. For more details, refer
41
to ZXWR RNC (V3.07.200) Radio Network Controller

(Routine Operation).
42
Operation Manual
Figures
Figure 1 Emergency Maintenance Flow ..........................................................18
43
44
Tables
Table 1 Typographical Conventions ................................................................ix
Table 2 Mouse Operation Conventions ............................................................ix
Table 3 Safety Signs.................................................................................... x
45

ZXWR RNC (V3.07.200) Radio Network Controller Maintenance Manual (Emergency Maintenance) PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ZXWR RNC (V3.07.200) Radio Network Controller Maintenance Manual (Emergency Maintenance) PDF

Uploaded by

Copyright:

Available Formats

ZXW10 3G Mobile Communication WCDMA System

ZXWR RNC Radio Network Controller Maintenance Manual (Emergency Maintenance)

Equipment Installation Date

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

This page is intentionally blank.

Declaration of RoHS Compliance ............................................................ 13

Handling User Service Interruption Caused by Wrong Modification of RNC Radio

About this Maintenance

ZXWR RNC (V3.07.200) Radio Network Controller Maintenance Manual

Confidential and Proprietary Information of ZTE CORPORATION

Purpose of this Maintenance

Describes basic principles and precautions of emergency

Describes the emergency maintenance flow and describes

Describes the emergency handling methods on the

Chapter 4, Data Backup and

Describes the data backup and recovery before handling

Provides abnormity record table during the maintenance.

Provides troubleshooting record table during the

Provides equipment emergency maintenance requisition

Describes status of common indicators on RNC panel.

Describes board reset and board handover.

Describes the method to confirm cell/link fault.

Confidential and Proprietary Information of ZTE CORPORATION

About this Maintenance Manual (Emergency Maintenance)

TABLE 1 TYPOGRAPHICAL CONVENTIONS

References to other guides and documents.

Menus, menu options, function names, input fields, radio

Keys on the keyboard and buttons on screens and company

Select one of the parameters that are delimited by it

Mouse Operation Conventions

Refers to clicking the primary mouse button (usually the left

Refers to quickly clicking the primary mouse button (usually

Refers to clicking the secondary mouse button (usually the

Refers to pressing and holding a mouse button and moving the

Confidential and Proprietary Information of ZTE CORPORATION

Erosion: Beware of erosion.

Electric shock: There is a risk of electric shock.

Microwave: Beware of strong electromagnetic field.

No flammables: No flammables can be stored.

No touching: Do not touch.

No smoking: Smoking is forbidden.

Confidential and Proprietary Information of ZTE CORPORATION

About this Maintenance Manual (Emergency Maintenance)

How to Get in Touch

Confidential and Proprietary Information of ZTE CORPORATION

This page is intentionally blank.

Confidential and Proprietary Information of ZTE CORPORATION

This declaration is issued based on our current level of knowledge. Since

Confidential and Proprietary Information of ZTE CORPORATION

This page is intentionally blank.

Confidential and Proprietary Information of ZTE CORPORATION