ZXUR 9000 UMTS Troubleshooting

ZTE University

Content

Troubleshooting Overview
Operation and Maintenance Faults Handling
Hardware Faults Handling
Software Initiation Faults Handling
System Communication Faults Handling

Troubleshooting Flow
Collect fault
information

Start

Is it a local fault

Handle according to the

major fault processing flow

Y
Help the maintenance
Engineer to handle

Is it a hardware fault

Is the equipment Fault?

Y

Handle according to the

major fault processing flow

Locate the fault

and handle it

Locate the fault

and handle it

N
Query the operation logs
and configuration data

Major fault?
Y
Any alarm information?

Is the data correct

N

Y
Handle the alarm

Does the fault still exist?

Does the fault still exist?

N
Does the alarm
disappear?

Record the fault

Contact ZTE
Support Center

Share the experience

End

Y
Does the fault still exist?
N

Troubleshooting Principle

Check

Find out in which

component the fault
occurs, what type of
alarm are given, what the
grade of the alarm is,
what the damage is.

Query

Query the on-site

personnel about the fault
causes. Question them
about the data change,
file deletion, circuit board
replacement, power
failure, lightening strike or
improper operations.

Consider

According to the fault

alarms and the
information from the
query, determine the
cause.

Work

Locate the fault.

Eliminate the fault by
modifying the data or
replacing the circuit
boards.
The operation on the
equipment must not be
conducted in rush time,
which will cause serious
problems.

Common Methods to Locate Faults

Analysis of Alarm
Information

Analysis of
Performance

Analysis of Status
Indicator

Testing and SelfLooping

Analysis of
Signaling Tracing

Common
Methods

Plugging/Unpluggin
g and Pressing

Operation Log
Query

Configuration
Modification

Instruments and
Meters

Comparison and
Replacement

Contact Information of ZTE Technical Support

ZTE Customer Support Center International Hotline: +8675526771900

Content

Troubleshooting Overview
Operation and Maintenance Faults Handling
Hardware Faults Handling
Software Initiation Faults Handling
System Communication Faults Handling

Improper Display on Client Interface

Phenomena

Cause

The client operation interface is not fully displayed, and the pop-up
window or dialogue box oversteps the display area on screen.

The display resolutions for the NM client interface is designed to be

1024 * 768 pixel. Therefore, if the display resolutions is set as 800
* 600 pixel, the pop-up windows on the NM interface oversteps the
display area of screen.

Troubleshooting

Right-click the desktop of the client side and select Property. The
Property dialogue box pops up. Select Setting tab and set the
display resolution for the screen area as 1024 * 768 pixel.

Abnormal Start of NM Server

Phenomena

Cause

The NM Server starts as abnormally and the Client cannot

connect to the NM Server.
Oracle database connection may not be proper, or the properties
file is not configured correctly.

Troubleshooting
1.
2.

3.

Check whether the connected database is initiated.

Check whether Oracle Client connection is created. Run Oracle
Enterprise Console and check whether the SID_*.*.*.* connection
is established.
In ums-svr/deploy/deploy-*.properties file under NM server
installation directory, check whether the configuration of the
database connection is correct.

Start Failure of NM Server FTP

Phenomena

Cause

NM Server starts abnormally and the startup of FTP

fails.
The port required for FTP startup is occupied by third
party FTP software.

Troubleshooting
1.

2.

Check all started processes to see whether any

process occupies the FTP port. If so, close the
process and restart the server.
Check all services of the operation system to see
whether any services occupies FTP port. If so, close
the services and restart the server.

Inconsistent Configuration Data in NE and NMS

Phenomena

Cause

The configuration data displayed

at NM Client is inconsistent with
that on NE.
The configuration data modified in
NMS is not synchronized to NE in
time.

Troubleshooting
1.

2.

3.

Perform alltables
synchronization to synchronize the
NM configuration data to NE.
Perform the following steps:
Confirm the correctness of NM
configuration data.
On the configuration resource tree,
select a network element. . Rightclick it and select Data
Synchronization > All Table
Synchronization.

Inconsistent Status Data in Network Element (NE)

and Network Management System (NMS)
Phenomena

Cause

The board status on the rack diagram displayed at NM

Client is inconsistent with the actual status.
The status data of the NE and NMS is inconsistent.

Troubleshooting

Perform status synchronization operation to

synchronize status data between NE and NMS. Perform
the following steps:
On the NMS interface, reopen the status page or
refresh the status.

Different Alarm Time in NE and NMS

Phenomena

Cause

The alarming time displayed on Client interface is different from the actual
time when the NE gives alarm.
Inconsistent clocks in NE and NMS.

Troubleshooting
1.
2.
3.

4.

5.
6.

Perform the following steps to synchronize the clocks:

Log in to the NM client.
On the configuration resource tree, select Subnetwork > NE > Config Set
> Ground Resource Management.
Select Ground Resource Management > SNTP and System Log
Configuration. The IP address of SNTP server should be OMM
subnetwork IP that can be ping through OMP. The SNTP networking mode
should be OMM Server Access The source of time synchronization should
be obtained from NTP server. The Using Configuration Synchronization
Mode of 3G option should be set Yes.
Perform All Table Synchronization or Incremental Synchronization.
On the toolbar of NM status management interface, click . On then pop-up
dialog box, click NTP Clock Synchronization.

Content

Troubleshooting Overview
Operation and Maintenance Faults Handling
Hardware Faults Handling
Software Initiation Faults Handling
System Communication Faults Handling

Clock Fault Overview

EGFS Clock Distribution

Phenomena

Cause

K/F indicator, 1 Hz
flash

Clock source not configured or

invalid

K/F indicator,
constantly on

Current clock source lost

GPS indicator, 0.5

Hz flash

GPS initialization failed

GPS indicator, 1 Hz
flash

GPS in satellite searching status or

unknown status

GPS indicator, 2 Hz
flash

Antenna and feeder short-circuited.

GPS indicator, 5 Hz
flash

Antenna and feeder broken

GPS indicator, Off

Master shelf: GPS in unknown

status;
Slave shelf: GPS not in use

Communication Link Fault Overview

Symptom

Cause

E1 link fault

Check the configurations of the network management system.

Check the cable link. Make a self-loop back
on the E1 cables and check whether the alarm
disappears.

E1 link slip code

Check the EDTT/EDTI/EDTA board.

Check the clock reference source for the EGFS
board.
Check lock phase for the EGFS board.

Optical link fault

Check the optical fiber link. The SD indicators should be lit.

Check that the optical fibers are single-mode multiple fibers.
Check the optical unit.

Ethernet Link Fault

Check the IP address.

Check the EGPB board.

Shelf Management Fault Overview

Board start up flow
The boards communicate
with ECMM through IPMC.
ECMM controls the
POWER ON for the boards
in each slot.
The boards ask for the
version files from
UMP(OMP) for startup.

Phenomena

Cause

ECMM startup
failure

Improper ECMM status

Board startup
failure

1.
2.

3.

Wrench not closed

Board hardware faults (wrong BOOT
version, or problems on
memory/power unit/hard disk)
ECDM not configured

Slave shelf
startup failure

ECDM configuration error

EGBS connection error

FAN ALM red

light/big noise/no
indicator

Fan failure

OMP Version File Fault

Phenomena

Cause

OMP cannot get version files from OMM.

Not configured in ECMM.

Troubleshooting
1.
2.

Check whether the OMM fire wall is closed.

Based on the installation of OMM (internal/external),
Telnet to the 24 port of ECMM. In ddm-syscfg menu,
do the query and configurations.

H/S Blue Light ON for a Slot

Phenomena

Cause

H/S blue light on for one slot

The slot not configured in ECMM
Wrench not closed

Troubleshooting
1. Check the slot configuration in ECMM.
2. Check whether the wrench is closed.

Fan Noise/Fan Indicators Off

Phenomena

Cause

Big fan noise

Fan indicators off
The dummy panel is not installed.
Version error of SIPMC/FRU

Troubleshooting
1. Check whether the dummy board is properly installed.
2. Check whether the SIPMC/FRU version files are
burned.

OK Red Light ON for Fan Unit

Phenomena

Cause

OK red light ON for Fan unit

Fan failure

Troubleshooting
1. Check the fan alarms.
2. Check whether an internal fan stops working. If so,
replace it.

Cautions

The fan unit supports hot swap.

Optical Fiber Communication Fault

Phenomena

Cause

The indicator for the optical port is not lit on a board

(including EAPB, ESDTA, ESDTT, ESDTG, EGPB,
ESDTI, EGFS).
Board failure or optical fiber failure

Troubleshooting
1. Replace the optical fiber.
2. Replace the optical module. The replaced one must be
of the same type with the peer end, and must be
supported by the current system.
3. Replace the board.

EGFS Unable to Lock Clock Reference from

Optical Port

Phenomena

Cause
1.
2.

3.
4.
5.

EGFS unable to lock clock reference from the optical port

Low CN clock precision
No CN clock for Dual Mode Controller. Cable connection error or NMS
data
management error.
EGFS do not have correctly burned single-chip program and logical files.
Clock extraction cable error.

Troubleshooting
1.
2.
3.

4.
5.

Check interface A of Dual Mode Controller.

Check the clock extraction on Dual Mode Controller Network Management.
Check whether the single-chip program for EGFS is correctly burned, and
whether the logic is correct.
Check if the CN clock is transferred to Dual Mode Controller.
Check the configurations of optical interface board.

Slip Code on Communication Link at Base Station Connected

with Dual Mode Controller Through E1 Cable

Phenomena

Cause
1.

2.
3.

4.

Slip codes are generated on the communication link at the Base Station connected
with
Dual Mode Controller through the E1 cable.
The Base Station does not use the high-precision clock uploaded through the E1
cable. The clocks are not synchronized.
No EGFS board is installed in the Dual Mode Controller system.
The clock board for Dual Mode Controller is not operating properly, or there is no
clock distribution cables to send the clock reference to the EGFS board.
The input standard set for the Dual Mode Controller system is poor, or the EGFS
board is in the state of fast capture of quality deterioration.

Troubleshooting
1.

2.

3.
4.

Check that the Base Station gets the clock reference through the E1 cable. The
clocks at the Base Station and the Dual Mode Controller system must be
synchronized.
Check that the E1 interface board of Dual Mode Controller uses the clock of the
EGFS board.
Check that EGFS is operating properly.
Check that the clock source for the EGFS board is obtained from CN. Do not make
it obtain the clock reference from the Base Station and then send the reference
back to the Base station after synchronization.

Content

Troubleshooting Overview
Operation and Maintenance Faults Handling
Hardware Faults Handling
Software Initiation Faults Handling
System Communication Faults Handling

Software Initiation Flow

OMP Startup

Not OMP Startup

Request version
form OMM

Request version
form OMP

The version is
consistent with local?

The version is
consistent with local?

Yes

No

Start with
local file

Start with
new file

End

Yes

No

Start with
local file

Start with
new file

End

Fault Handling Steps

1.
2.

Check the physical connections. Check the cable connections at the

ECMM, OMP and OMC interfaces.
Check the configurations of each board:

3.

4.
5.

6.
7.

Check the configurations of the racks, shelves and slots.

Check the module number, module type, unit number, and unit type.

Check on the NM server to see whether the DHCP requests and IP

requests are received from ECMM. If not, close the OMM firewall and
reactivate the control plane network port of OMM.
Load the new version files to the NM server.
Check the IP address configuration of NE. If the IP is modified, the
OMM media plane network port should be reactivated. Check on the
NM server to see whether the DHCP requests and IP requests are
received from OMP.
Check the radio data configuration.
If possible, restart the EGBS board.

Content

Troubleshooting Overview
Operation and Maintenance Faults Handling
Hardware Faults Handling
Software Initiation Faults Handling
System Communication Faults Handling

Iu/Iur Interface Protocol----ATM

CN/RNC

RNC

ATM
RNAP/RNSAP

RNAP/RNSAP(CMP)

SCCP

SCCP(CMP)

MTP3B

MTP3B(CMP)

SSCS

SSCS(EAPB)

ATM

ATM(EAPB)

Iu/Iur Interface Protocol----IP

CN/RNC

RNC

IP
RNAP/RNSAP

RNAP/RNSAP(DMP)

SCCP

SCCP(CMP)

M3UA

M3UA(CMP)

SCTP

SCTP(CMP)

IP

IP(EGPB)

Iub Interface Protocol----ATM

Node B

RNC

ATM
NBAP(CMP)

NBAP

SSCS(EAPB)

SSCS

ATM(EAPB)

ATM

Iub Interface Protocol----IP

Node B

RNC

IP
NBAP(CMP)

NBAP

SCTP(CMP)

SCTP

IP(EGPB)

IP

Fault Troubleshooting Procedure

Check the physical connection to see whether the abnormality at IU/IUR
interface is caused by the cable connection. Especially, check the cable
connection on IP interface board.
2. Check the data configuration related to IU/IUR interface on ZXUR 9000 GU.
1.

Local office configuration

Adjacent office configuration
Port IP address configuration
SIGTRAN data configuration.

Check whether the status of CMP that manages the association module is
normal and whether EGPB status is normal. Check whether there are related
alarm.
4. Activate/De-activate the association with the dynamic data management
provided by NM and then check whether the alarm disappears.
5. Locate the fault with the alarm provided by NM steps by steps according to the
protocol layers. Minimize the range and eliminate the fault.
6. If after trying all above methods, the fault still exists. If conditions allow, reboot
EGPB, CMP, and OMP to see whether the link failure is repaired.
3.

M3UA Layer Association Connected but ASP not

Activated

Symptom

Analysis
1.
2.

The association to the Core Network is connected, bur ASP is not

activated.
AS properties at the both ends are not consistent.
AS RC (Routing Context) and the service mode are configured
inconsistent at the both ends.

Troubleshooting

1.

In the OMC configuration management window, expand Config Set >

Ground Resource Management > Transport Configuration > 3G Office
Configuration >IUCS Configuration tab.
Check AS Property in AS Information tab.

2.

The configuration rule is: at the Iur interface, one end is configured as
IPSP_CLIENT and the other end is configured as IPSP_SERVER. At the Iu
interface, the CN is configured as SGP, while the RNC is configured as ASP.

Check whether parameters related to AS routing context and AS Traffic

Mode are consistent with the corresponding parameters at the peer end.

SCTP Layer Association Setup Failure

Phenomena

SCTP association is set up unsuccessfully and the notification is

reported.

Cause

The four elements (localend IP address, peer-end port No., peerend IP address, and peer-end port No.) that decide the association
and the association protocol properties (CLIENT/SERVER) are not
configured correctly.
The route is configured incorrectly (if the peer service address and
the interface
address of the association are not in the same network segment,
the route should be configured).
The network cable is plugged error or the network cable is
disconnected.
The transmission is delayed. The transmission is delayed.

SCTP Layer Association Setup Failure

Troubleshooting

Association configuration

Routing configuration

On NM configuration management interface, check whether the static route is

correctly configured in IP stack. If the RNC connects to the peer element via
Ethernet, the next-hopping address of the static routing should be configured as
the interface board address of the peer element, instead of the address of EGPB
at the local end.

Network cable error or disconnected

In the OMC configuration management window, check the four elements of the
association are correctly configured and whether consistent with the
configurations at the peer end.
Doubleclick Config Set > Ground Resource Management > Transport
Configuration > 3G Office Configuration > IUCS Configuration > Association, and
check the association configuration on the Association tab and Port and IP
Configuration tab.
Select IP Configuration of SCTP Association tab and check whether IP address is
correctly set.

Re-plug the network cable or replace the network cable.

Transmission delay

Adjust the cable connection between the two offices and do not use more
switching devices between the two offices.

SSCS Layer SSCOP Link Constantly

Disconnected

Phenomena

Analysis

On NM configuration management interface, click NE Configuration

Information. Select one piece of signaling link configuration and find that
the corresponding SSCOP link is constantly unavailable.
The fiber connection is error.
The local optical interface is configured error.
PVC interconnection parameters are error.

Troubleshooting

Fiber connection error

Local optical interface configuration error

Check whether the fiber connection on EAPB is normal.

Make sure that the optical interface where the configured link locates (high-end
ATM Sunit No. in PVC configuration) is configured same as the optical interface
where the fiber is plugged (the optical interface where the fiber is plugged is,
from up down, 4,5, 6, 7).

Interconnection parameter error

Check the interconnection parameters of both ends in the OMC client. On the
Broadband Signaling Link tab, check VPI on High Port and VCI on High Port.

ALCAP Layer Repeated Common Transport

Channel Deletion and Setup
Phenomena

The Node B OMC indicates that the common transport

channel is set up and deleted repeatedly.

Cause

AAL2PATH interconnection parameters are

inconsistent.
ATM address is invalid.
AAL2 Path type and the service type are inconsistent.
Transport path bandwidth is inadequate.
On the signaling tracing, the end that initiates the link
setup request sends ERQ and receives RLC.

ALCAP Layer Repeated Common Transport

Channel Deletion and Setup
Troubleshooting

Inconsistent interconnection parameters

In the OMC configuration management window, expand Config

Set > Ground Resource Management > Transport Configuration
> 3G Office Configuration >IUCS Configuration, and doubleclick IUCS Configuration. In the right pane, select the AAL2 Path
tab. Check the settings of AAL2 Path basic properties.
The AAl2 Path ID is the interconnection parameter, which
should be same as the path ID at the peer end.
In the OMC Status Management window, click the AAL2 Path
Management tab. check whether AAL2 Path is available.
In the configuration management window, double-click the path
record to open the AAL2 Path dialog box. Check PVC ID, VPI
on High Port, and VCI on High Port.

ALCAP Layer Repeated Common Transport

Channel Deletion and Setup

Troubleshooting

Invalid ATM address

AAl2 Path type inconsistent with service type

In NM configuration management, check whether the ATM address of

the local office is configured same as that of the target office.
On NM configuration management interface, doubleclick Config Set >
Ground Resource Management > Transport Configuration > 3G Office
Configuration >IUCS Configuration. Click a record on the IUCS
Configuration pane to open the ATM Adjacent Office dialog box, and
check whether ATM address configuration is the same as that at the
peer NE.
In NM configuration management, check whether AAl2 Path type
matches the service type.

Inadequate transport path bandwidth

On IUCS Configuration window, Click the Tr Path tab, and double-click

a record on the tab. In the pop-up dialog box, check whether the
transport path bandwidth is adequate. Forward bandwidth corresponds
to the transmitting direction of the NE, while ackward bandwidth
corresponds to the receiving direction of the NE.

SCCP Subsystem Unavailable

Phenomena

Cause
1.

2.

3.

The system gives alarm about SCCP subsystem unavailable.

Check on the NM configuration interface that the adjacent office
state is reachable.
After the adjacent office signaling point receives the SST
messages from Dual Mode Controller, no SSA is returned back.
Therefore the corresponding SSN is not available.
Check whether the subsystem is manually blocked.

Troubleshooting
1.
2.

Locate the faults that the signaling points is not reachable.

If the signaling point to the adjacent office can be reached, check
with the signaling tracing tool whether the adjacent cell sent SST.
If no SSA is received, check the routing configuration and the
subsystem configuration.

Association Establishment Failed

Phenomena

Cause

The alarming interface informs that the association

setup failed.
SCTP cannot set up a link.

Troubleshooting
1.

2.
3.

Check that the EGPB interface board is operating

normally.
Check that the physical link is good.
Check that the configurations of the association are
correct.

Association Link Broken Alarm

Phenomena

Cause
1.
2.
3.

The alarming interface reports that the association link is broken.

The association is deleted.
The association is released manually.
The transportation link between the two end of association is
broken.

Troubleshooting

Configure an IP on the debug computer that is in the same

network element with EGPB. Connect this debug computer to the
network in which the EGPB interface board resides. Ping the IP
address for the interface board at both ends. Check that the
network is good.

M3UA Office Not Reachable

Phenomena

Cause
1.

2.

The NM alarming interface reports that the M3UA

office is not reachable.
The coupling link is released, or the AS is not in
service.
The routing to this office is not configured.

Troubleshooting
1.

2.

Check the association status. If it is operating

normally, query the status of the serving AS.
Check the routing configuration.