Documente Academic
Documente Profesional
Documente Cultură
Version: V4.15.10.20
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: 800@zte.com.cn
LEGAL INFORMATION
Copyright © 2016 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 the ZTE technical support website http://support.zte.com.cn to inquire for related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
R1.0 2016-04-30 The following are the changes that were made in this version
compared with the early version (V4.14.10.14).
Figures............................................................................................................. I
Tables ............................................................................................................ III
Glossary .........................................................................................................V
II
Intended Audience
This manual is intended for:
l System engineers
l Maintenance engineers
Chapter Summary
Appendix A, Link and Cell Faults Describes how to locate Link and Cell Faults.
Location
Appendix B, Reset and Board Switchover Describes how to reset and switchover board.
Related Documentation
The following documentation is related to this manual:
l ZXUR 9000 UMTS Radio Network Controller Hardware Description
l ZXUR 9000 UMTS Radio Network Controller Status Management Operation Guide
Conventions
This manual uses the following conventions.
Italics Variables in commands. It may also refer to other related manuals and
documents.
II
1.3 Precautions
The following precautions should be observed during emergency maintenance:
1-1
l Some restoration operations (for example, board reset) may greatly affect the system
operation, so these operations should be performed by experienced maintenance
personnel.
l Attach all contact information of ZTE CORPORATION in prominent positions in the
equipment room.
l If a fault greatly affects network operations, maintenance personnel should contact
ZTE Customer Support Center or local ZTE office immediately for technical support,
no matter whether they can resolve the fault.
On the status management tab of the NM system, all base stations are unblocked,
or without blocking.
1-2
2. Check whether the operation status of the board indicators at the RNC-rack side is
proper.
1-3
1-4
2-1
Table of Contents
Service Check ............................................................................................................2-3
Fault Records.............................................................................................................2-4
Initial Location and Analysis of Fault Causes..............................................................2-5
Emergency Aid...........................................................................................................2-5
Service Recovery .......................................................................................................2-6
Service Observation ...................................................................................................2-6
Fault Information Collection ........................................................................................2-6
2-2
2-3
No->10
10. Check the cells to see whether they are correctly connected to other NEs.
Yes->13
No->11
11. Check the operation log to see whether any data is modified or deleted incorrectly and
the system is crashed.
Note:
You can check the man-machine command operation log and alarm time to determine
the relevance between operations and faults.
Yes->12
No->13
12. Restore the data and check whether the fault is resolved.
Yes->End
No->13
13. Notify the maintenance personnel for other NEs, such as Node B and CN, to perform
joint troubleshooting, or refer to the emergency maintenance manuals for other NEs
to determine the possible causes.
Note:
After a fault occurs, it is very important to locate the fault as soon as possible. Determining
whether the fault is in the local office or other offices is especially helpful for resolving the
fault quickly.
Before handling ZXUR 9000 UMTS emergency faults, back up the configuration data of
OMM first, then after the fault recovery restore the configuration data from a data backup.
Refer to ZXUR 9000 UMTS Radio Network Controller Data Backup and Restoration Guide.
2-4
Note:
Fault records are very useful in emergency aid and subsequent fault analysis and
summary, so users should make an exhaustive fault record.
2-5
Before making a call, record the fault information in the emergency maintenance
notice (refer to "D.3 Equipment Emergency Maintenance Notice"), which may be
required by ZTE technical support engineers for troubleshooting.
l Remote technical support
According to the information provided at the service hotline, ZTE technical support
experts solve common problems on the phone by remotely logging in to the
problematic site, and provide on-site technical support for complex problems.
l On-site technical support
Upon arriving at the site, the maintenance experts from ZTE take emergency
maintenance measures to recover the communication as soon as possible.
Note:
Board switchover, reset, and replacement greatly influences system operation, so users
should properly perform these operations.
Make records of the current state before any board handover and physical location change.
Note:
Make records of each step and symptom occurring in the service recovery on the site.
2-6
Collecting fault information not only provides precious maintenance experience for
operators, but also provides good reference for manufactures to improve the equipment.
The information to collect includes the following:
1. Brief notice
The operator makes the brief notice, including the fault occurrence time, fault
properties, fault symptom, and detailed fault handling steps. If the fault is not
removed, provide the detailed handling steps for subsequent troubleshooting.
2. System debugging information
Copy all logs on the NM server and save to a new folder path.
Save the log files on the UMP board of ZXUR 9000 UMTS through the file manager.
3. Alarm information
Collect the history alarms from thirty minutes before to thirty minutes after the fault.
Maintenance personnel can query and save on the alarm browsing window. For
information on how to handle alarms, refer to ZXUR 9000 UMTS Radio Network
Controller Alarm and Notification Handling Reference.
4. Command log information
Collect the command log information about ZXUR 9000 UMTS from thirty minutes
before to thirty minutes after the fault, to facilitate maintenance personnel to query
the operation logs, safety logs, and system logs in the log management subsystem of
the NM. For information on how to handle logs, refer to NetNumen U31 R18 Unified
Element Management System Log Management Operation Guide .
5. Signalling trace information
Collect the signalling trace information aboutZXUR 9000 UMTS from thirty minutes
before to thirty minutes after the fault, to facilitate maintenance personnel to obtain the
signalling trace information through signalling trace tools. For information on signalling
tracing, refer to ZXUR 9000 UMTS Radio Network Controller Call Tracing Operation
Guide.
2-7
2-8
CS and PS services in the entire Power failure Check the power supply.
network are interrupted.
CN failure Perform troubleshooting on the
CN.
3-1
CS and PS services of a single Iu interface board failure Check the interface board
RNC are interrupted. and replace the board when
necessary.
CS services of a single RNC are Iu interface board failure Check the interface board
interrupted. and replace the board when
necessary.
PS services of a single RNC are Iu interface board failure Check the interface board
interrupted. and replace the board when
necessary.
The services of a single Node B Failure of the corresponding link Check and analyze the Iub link
are interrupted. status.
The services of a single cell are Incorrect cell configuration Check the cell configuration.
interrupted.
Manually blocked cell Unblock the cell.
3-2
3-3
Steps
1. Before the power supply in the equipment room recovers, to prevent from any accident,
power off all switches on the cabinet power distribution subrack which connects with
the external power supply system, and toggle the dual-path power switch on the rack
to off.
2. Check the power supply system in the equipment room.
3. After the power supply in the equipment room recovers, power on the system again.
The power-on order is as the following:
a. Power on the power distribution subrack. Check whether the power supply voltage
is within the proper range: -57 V to -40 V.
b. Power on the dual-path on the racks. Check whether the power supply voltage is
within the proper range: -57 V to -40 V.
c. Recover the power supply of the network cabinet and server cabinet. Start the
NM server, charging dual-machine server, and disk machine.
– End of Steps –
Steps
1. Check whether the power supply on the shelf is proper.
a. If all LED indicators on the shelf are off, the power supply on the shelf is improper.
3-4
b. If the switch on the shelf of the power distribution subrack is off, the power supply
on the shelf is improper.
2. Recover the power supply on the shelf.
Check whether the dual-path power supply voltage of the power distribution subrack
is within the proper range. If so, toggle the power switch on each shelf corresponding
to the power distribution subrack to on, to resume the power supply of the shelf.
– End of Steps –
Steps
1. Power on the rack, shelf, and boards of ZXUR 9000 UMTS.
Note:
For the power-on sequence, the main control shelf takes priority over other shelves.
2. Observe indicator statuses on boards to check whether the system is started properly.
3. Verify that the OMM server is started properly.
4. Check whether there is communication fault through the fault management. For
example, if the communication between modules is proper, remove the fault.
5. Check and remove the signalling link fault in the office direction through the fault
management.
6. Perform the basic service test, and ensure that services are recovered through the
signalling trace and failure observation.
– End of Steps –
Context
Table 3-2 describes the boards that are closely related to services.
3-5
Interface unit l EAPB and EAPB1b Provides Iu, Iub, or Iur interfaces
l EDTA and EDTA1b for service access over of IP,
l ESDTA and ESDTA1b STM-1/CSTM-1, or E1/T1.
l EDTI and EDTI2a
l ESDTI and ESDTI2a
l EGPB, EGPB2a, EGPB2c,
EGPB1a, and EGPB1b
,
System control board UMP and UMP1b Provides operation and maintenance
functions, support the processing of
global procedures, and controls the
operation and maintenance of the
entire system.
Steps
1. Log in to the EMS client, select View > Alarm Management and check whether any
alarm related to a board exists in the alarm list. If yes. view the details of the alarm to
obtain the board information, such as the board type.
2. Locate the board reporting the alarm and observe the statuses of indicators on the
board panel.
4. If the status of any indicator is unexpected when the board is operating properly or the
alarm cannot be cleared in the EMS, reset the board or replace the board.
3-6
Note:
Do not reset a board in the RNC unless absolutely necessary. Resetting a board in
the RNC has great impact on services. For example, if a CMP board is reset, all user
services on this board are interrupted. If an interface board is reset, all parameters
allocated to this board become unavailable.
– End of Steps –
Context
The clock system fault may result in global service interruption.
Steps
1. Check whether the external connection of the EGFS/EXFS1a board is proper.
2. Check whether the system clock of EFGS/EXFS1a is proper, and check whether the
NE and NM clock data are consistent.
– End of Steps –
3-7
2. If there is not abnormality, perform the self-loop on optical interface or IMA group at
ZXUR 9000 UMTS 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 persists after the self-loop, check the transmission cable for connection and
good contact, and cables for damages and exposing.
6. For IP network, when all equipment is running normally, if the global services
disconnect, the maintenance personnel should examine whether IP network is
running normally first.
a. Check the association status in NM configuration management. If the association
is not in service status, recreate the association. If the creation fails, connect the
cable from the interface to another PC. Set the IP address as the local interface IP
address and check the IP network through pinging the peer interface IP address.
b. In the performance management, check the office IP link type QoS statistics. Know
the accessibility of the peer IP address according to the packet loss rate.
c. With the dedicated instrument or software, test the transmission delay, error bit
rate, jitter of the IP network, confirming whether such faults as network blocking,
network thunderstorm, and virus attack, occur in the IP network.
7. If the problems fail to be solved with all the above methods, launch the emergency
aid, or reset the interface board with caution. For resetting details, refer to "Appendix
B Reset and Board Switchover".
Near-end alarms are reported by the optical interface board when it detects that the
signals received are improper. Far-end alarms are reported to the optical interface
board when the equipment at the peer end detects that the signals received are
improper. If the near-end alarms (original alarms) on the interface board is eliminated,
the remote alarms on the interface board disappear.
l Observe the commonness of alarms
When several optical interface boards generate alarms of the same type, or when
alarms of the same type occur on several E1 links, observe whether the board or E1
links are in the same office, or whether the switches at the peer end are the same
model.
3-8
3-9
These alarms (belonging to the remote-end alarms) indicate that near-end alarms
may exist on the corresponding layer. For the E1-RAI alarm, contact the maintenance
personnel of the peer-end switch to confirm whether the E1 frame format is consistent
with that at the local end.
l E1-SLIP
This alarm indicates the clock fault when the board is operating properly.
Recommended Solutions
1. Check to see if all tables are synchronized for the data modifications of the whole
network or a single RNC. If so, recover the data.
2. Check to see if there is any alarm about inaccessible calls or unreachable signals in
all RNCs. If so, check the CN side.
3-10
3. Check to see if there are frequent SSCOP link establishments and disconnections
(The message is "BGN, END".) Make sure that the PVC bandwidth and the PVC type
of both sides of the Iu interface are identical.
4.
5. Check the CN side if the problem persists after replacing the interface board.
Recommended Solutions
1. Check to see if the RNC data configuration is modified before the failure occurs. If so,
recover the configuration by importing the backup data.
2. Check the No.7 link status.
3. Reset or replace the interface board.
4. Conduct an active/standby changeover to the interface board.
5. Reset the interface board to which the failed cell belongs.
3-11
If users can hear their voice from the calling UE during the uplink loopback test, it
means that there is no problem from the UE to the RNC, and the problem possibly lies
in interface board or the CN side. If not, the problem possibly lies in the user plane or
the Iub interface.
Recommended Solutions
1. Check to see if a global data modification is made before the failure occurs. If so,
recover to the pre-modification data.
2. Replace the UE. If the failure does not occur any more, the problem lies in the UE.
Report it to the UE maker for solution.
3. Reset the Iu interface board.
4. If the fault persists, reset the service processing board where services are borne.
5. Reset the interface board to which the failed cell belongs.
6. If the problem still persists, contact personnel at the CN side for troubleshooting.
Recommended Solutions
1. Check to see if the data configuration is modified before the failure occurs. If so,
recover the configuration by importing the backup data.
2. Reset the interface board. If the failure persists, replace it.
3. If the changeover doesn’t work, reset the service board where the PS service is
established.
4. If the failure remains after all these resets, ask personnel at the CE and the CN sides
for troubleshooting to see if the problem is caused by the MTU packet limitation.
3-12
Recommended Solutions
1. Check whether a global parameter modification is made before the failure occurs. If
yes, recover the configuration by importing the backup data.
2. If all out-of-service cells belong to the same module and the transmission interface
board generates no alarms, perform active/standby changeover to the home
processing module.
3. If all out-of-service cells belong to the same shelf and the transmission interface board
generates no alarms, perform active/standby changeover to the EGFS or EXFS1a.
4. If all cells that belong to an interface board are out of service, reset or replace the
interface board.
3-13
Recommended Solutions
1. Check whether a global parameter modification is made before the failure occurs. If
yes, recover the configuration by importing the backup data.
2. If there are notifications about system message update failure, modify the SIB1 value
of the cell and trigger the system message once to refresh the updating process.
3. If the Node B fails to deliver broadcasts, or if the transmission allocation and FP
synchronization fails, block and unblock the cell.
4. If the problem persists, reset the Node B.
3-14
Note:
It is recommended not to modify the radio resource data without backing up the data,
because the data are based on the on-site call model, on-site landforms, and network
planning and optimization.
3-15
3-16
Steps
1. On the Status Management tab, expand UMTS Radio Resource and Transmission
Resource in the left navigation tree.
2. Double-click Iub Port under UMTS Radio Resource, and then check the statuses of
NCP links and CCP links in the right pane.
3. Double-click AAL2 Path under Transmission Resource, and then check the status
of the AAL2 path in the right pane.
– End of Steps –
Steps
1. On the Status Management tab, expand UMTS Radio Resource in the left navigation
tree.
2. Double-click Cell under UMTS Radio Resource, and then check the status of each
cell in the right pane.
A-1
3. Double-click Channel under UMTS Radio Resource, and then check the status of
each channel in the right pane.
– End of Steps –
A-2
EAPB/EAPB1b 1 + 1 backup -
EDTI/EDTI2a 1 + 1 backup -
ESDTA/ESDTA1b 1 + 1 backup -
ESDTI/ESDTI2a 1 + 1 backup -
EDTA/EDTA1b 1 + 1 backup -
B-1
Table of Contents
Ÿ Influence of Reset and Changeover........................................................................ B-2
Ÿ Changeover Modes ................................................................................................ B-2
Ÿ Reset Mode ............................................................................................................ B-2
à Resetting a USP, USP1b or USP2a board (Load sharing backup) may cause the
loss of services borne on that board currently, but new services can access after
successful changeover. Therefore, perform changeover to that board in the case
of low traffic.
à Resetting boards (such as EGBS/EGBS2a and EGFS/EXFS1a) in load-sharing
mode causes the decrease in the capacity of the control plane and user plane
between two boards (shelves), and in the interface bandwidth, rather than service
interruption.
l Resetting cells: All the user services in this cell are released after reset.
l Resetting the RNC: Restarting the RNC interrupts all the RNC services.
On the rack map, select the board to reset. For operation details, refer to the ZXUR
9000 UMTS (V4.14.10.09) Radio Network Controller Status Management Operation
Guide.
2. Manual changeover at the NE.
Reset the active board on the rack.
3. Automatic changeover due to NE faults.
The system initiates changeover after detecting faults.
B-2
3 Flashing at 5 Hz The period is 0.2 s and the duty ratio is 50%: on for 0.1
s, and off for 0.1 s .
4 Flashing at 2 Hz The period is 0.5 s and the duty ratio is 50%: on for 0.25
s and off for 0.25 s.
C-1
5 Flashing at 1 Hz The period is 1 s and the duty ratio is 50%: on for 0.5 s
and off for 0.5 s.
6 Flashing at 0.5 Hz The period is 2 s and the duty ratio is 50%: on for 1 s
and off for 1 s.
OOS Dual-color Board service and Indicates different levels of alarms through
indicator alarm indicator flashing at different frequencies.
(red/green)
HOST Tri-color indica- Operation/Alarm The indicator in green indicates that the
tor (red/green/or- indicator board is operating.
ange) The indicator in red indicates alarm
occurrence in the board.
The indicator in orange indicates that the
memory of the board is being initialized or
loading data.
ACT
ACT, the active/standby status indicator, indicates that whether a board is an active board
in service. The ACT indicator is described in Table C-3.
C-2
HOST
HOST, the operation/alarm indictor, is described in Table C-4.
C-3
C-4
C-5
C-6
Fault query information Including the resource name (such as cell ID,
ATM No.) whose status is abnormal through
query, and failure contents. Record it if there is
any.
D-1
Fault occurrence time Hour Day Month Year Fault handling time Hour Day Month Year
Fault type:
Fault source:
Fault symptom:
Solution:
Summary:
D-2
Handling result:
Handled by:
Chopped by the department:
Unresolved problems:
D-3
D-4
II
III
IV
BSC
- Base Station Controller
BTS
- Base Transceiver Station
CCP
- Communication Control Port
CE
- Channel Element
CMP
- Common signaling MP
CN
- Core Network
CS
- Circuit Switched
CSTM-1
- Channelized STM-1
DMP
- Dedicated signaling MP
DXC
- Digital Cross Connect
EAPB
- Enhanced ATM Process Board
EAPB1b
- Enhanced ATM Process Board 1b
EDTA
- Enhanced Digital Trunk Board ATM version
EDTA1b
- Enhanced Digital Trunk Board ATM version 1b
EDTI
- Enhanced Digital Trunk board IP version
EDTI2a
- Enhanced Digital Trunk board IP version 2a
EGBS
- Enhanced GE BASE Switch Board
EGBS2a
- Enhanced GE Base Switch board 2a
EGFS
- Enhanced GE FABRIC Switch Board
EGPB
- Enhanced GE Process Board
EGPB2a
- Enhanced GE Process Board 2a
EGPB2c
- Enhanced GE Process Board 2c
EGPB2d
- Enhanced GE Process Board 2d
EMS
- Element Management System
ESDTA
- Enhanced SDH Digital Trunk board ATM version
ESDTA1b
- Enhanced SDH Digital Trunk Board ATM version 1b
ESDTI
- Enhanced SDH Digital Trunk board IP version
ESDTI2a
- Enhanced SDH Digital Trunk board IP version 2a
VI
EXFS1a
- Enhanced XGE Fabric Switch board 1a
FP
- Frame Protocol
HW
- High speed data Way
IMA
- Inverse Multiplexing over ATM
IP
- Internet Protocol
KPI
- Key Performance Index
LED
- Light Emitting Diode
LMT
- Local Maintenance Terminal
LOF
- Loss of Frame
LOS
- Loss of Signal
MTP3B
- B-ISDN Message Transfer Part level 3
MTU
- Maximum Transfer Unit
NCP
- Network Control Protocol
NE
- Network Element
NM
- Network Management
NMS
- Network Management System
Node B
- Node B
ODF
- Optical Distribution Frame
OMC
- Operation & Maintenance Center
VII
OMM
- Operation & Maintenance Module
OMP
- Operation & maintenance Main Processor
PS
- Packet Switched
PTN
- Packet Transport Network
PVC
- Permanent Virtual Channel
QoS
- Quality of Service
RNC
- Radio Network Controller
RRC
- Radio Resource Control
RUP
- Rnc User plane Processor
SCTP
- Stream Control Transmission Protocol
SDH
- Synchronous Digital Hierarchy
SS7
- Signaling System No. 7
SSCOP
- Service Specific Connection Oriented Protocol
TU-AIS
- Tributary Unit Alarm Indication Signal
TU-LOP
- Tributary Unit-Loss of Pointer
UE
- User Equipment
UMP
- Universal Management Process Board
UMP1b
- Universal Management Process board 1b
UMP1c
- Universal Management Process board 1c
VIII
USP
- Universal Service Process Board
USP1b
- Universal Service Process board 1b
USP2a
- Universal Service Process board 2a
IX