07 ZXUR 9000 Troubleshooting

ZTE UR9000 Troubleshooting
Contents
 General Troubleshooting Overview

 Equipment Alarms
 Communication Alarms
 QoS Alarms
 Processing error alarms
2
Troubleshooting Principle
Check Query Consider Work
Query the on-site

Locate the fault.
personnel about the
Find out in which Eliminate the fault by
fault causes. Question
component the fault modifying the data or
them about the data According to the fault
occurs, what type of replacing the circuit
change, file deletion, alarms and the
alarm are given, what boards.
circuit board information from the
the grade of the alarm The operation on the
replacement, power query, determine the
is, what the damage is. equipment must not be
failure, lightening strike cause.
conducted in rush time,
or improper
which will cause serious
operations.
problems.
© ZTE All rights reserved 3

Common Methods to Locate Faults
Analysis of Analysis of
Alarm Performance
Information
Analysis of Status Testing and Self-
Indicator Looping
Analysis of
Common Plugging/
Signaling Tracing Methods Unplugging and
Pressing
Operation Log Configuration
Query Modification
Instruments and Comparison and

Meters Replacement
Contact Information of ZTE Technical Support

ZTE Customer Support Center International Hotline: +86–755–26771900

Basic Operation-Checking Input Power
The input power should be checked in case of power supply failure in the
cabinet.
Use a multimeter to measure the input terminal voltage for the cabinet po
wer distribution subrack. Verify that the input voltage meets the require
ment of ZXUR 9000 power supply.
The rated input voltage for ZXUR 9000 is -48 V DC. The allowed voltage f
luctuation range is from -57 V DC to -40 V DC.
© ZTE All rights reserved

Basic Operation-Checking Power Distribution
The power distribution subrack

provides power supply for all t
he ZXUR 9000 service subracks.
Make sure that the power distri
bution subrack is connected pro
perly to service subracks throu
gh power cables.
In case of power supply failure
in subracks, the subracks shoul
d be checked from top to bottom.

Basic Operation-Checking Cable Connections(1)
Line clock reference cable

BITS Reference Clock Cables

Inter-Shelf Clock Cables

Interconnection Fibers for inter-shelf

Medium Plane

Interconnection Ethernet cables for inter-shelf

Control Plane

Interface Network Cables For
Abis&IUB&A&Gb&IUCS&IUPS&IUR

OMC Cables between BSC/RNC and UME
RNC
ETH-MP1
ETH-MP1
E E
G G
B B
S S
ETH-MP2
ETH-MP2
x Switch

PD485 Cable Connection
Querying Software Versi

on Information

Basic Operation-Querying Software Version
1. On the Software Version Management window, expand a subnetwork node. Double-cl
ick Controller-OMP on the resource tree. The imported version packages of the controller
type is displayed
2. Right-click a package of the Controller-OMP type, select the command to display the
detailed information of the package.

on Information

Basic Operation-Querying Hardware Version
1. On the Status Management window, expand a subnetwork node. Double-click Board
on the resource tree.
2.Right-click a record and select Board hardware version query. The board hardware
version information is displayed

on Information

Basic Operation-Resetting a Board
1. On the Status Management window, expand a subnetwork node. Double-click Board.
The Board tab is displayed,
2. Right-click a board record and select Normal Reset by Board,

on Information

Basic Operation-Resetting an RNC
1. In the right pane of the Status Management window, double-click Subnetwork > ME
> Physical Resource > Controller Rack. The Controller Rack tab is displayed.
2. On Controller Rack tab, double-click a record. The Rack tab is displayed.
3. On the toolbar of the Rack tab, click All NE reboot
4. Input a verification code. After the resetting, the operation result will be displayed.
Click OK. Querying Software Versi
on Information

Basic Operation-Restoring a Backed-Up Data
Configuration File
1. From the main menu of the Configuration Management window, select
Configuration Management > Data Restoration. The Data Restoration dialog box is
displayed
2. In the Data Restoration dialog box, select a data configuration file to be restored from
the local or server. Click Restore

on Information

Basic Operation-Querying Logs
1. From the main menu of the ZXUR 9000 network management system, select Security >
Log Management. The Log Management window is displayed
2. Double-click a log type node in the log management tree. The log information of the
server is displayed in the right pane.

on Information

Contents

 QoS Alarms
21
199026129 Clock reference source lost (Level 1 alarm)
 Alarm Description:
 This alarm is raised if the clock reference source is lost for more than 24
hours.
 Alarm Cause :
 The input clock information is abnormal. The clock reference is not configured
correctly.
 Impact :
 When all configured references are lost, the clock board enters free operating
status or Hold status, and the output clock accuracy is determined by the
clock board crystal oscillator. This fault may have no impact on services.

 Alarm analysis:
1.Check whether "Type of the lost reference" in the alarm information is consistent
with the requirement.In accordance with the physical position of the board, check
the "Master Shelf Flag (IsMastFlag)" parameter of the "Shelf (Shelf)" object. If the
board is in a main shelf, modify the clock reference configuration as required in
"Independent Board Configuration Online".

 Alarm analysis:
2. If the clock reference is extracted by the line in accordance with the clock networking
requirement(SynE).Check whether the connection line from the clock extraction board to
the clock board is correct.Connect the clock extraction board to the clock board with a
good cable. Check whether the alarm is cleared.

 Alarm analysis:
3. Verify the type of the interface that extracts the clock according to the clock networking requirement.If the
interface is an Ethernet port,Check whether the "Distill Clock Flag (ClockSource)" parameter of the Ethernet
port is "Distill clock". Configure the clock extraction function for the Ethernet port, and then check
whether the alarm is cleared.

 Alarm analysis:
4. Check whether the Ethernet port has the following alarms:
199005672 Clock source for SyncE is not available
199005760 Ethernet port's link is down
199005718 Two master clock ports is directly connected
Handle the above alarms, and check whether the alarm is cleared.

 Alarm analysis:
5. If adopted GPS or BITS,Confirm cable connections are correct.
GPS:EGFS boarsd use ports “GPS”
BITS: EGFS boards use ports “REF”

This alarm is raised if the board cannot obtain clock information from the peer end .
 Alarm Cause :
No clock synchronization packet is received from the peer end within five seconds.
The clock resource advertised by the peer end is unavailable.
The port rate is 10 Mbps.
The physical link of the port is disconnected.
 Impact :
The clock of the NE may fail to be synchronized, and thus services may be affected.

 Alarm analysis:
 1.Check whether "Reason of unavailable clock source" in the alarm information is "Physical
link is down",Handle the alarm:199005760 Ethernet port's link is down
Check whether the "Negotiate Mode(NegotiateMode)","Port Speed(Speed)","Duplex
Mode(Duplex)","Master or Slave mode(Master)", and "Cable Type(WireType)" parameters of
the "Ethernet Port(EthernetPort)" object are set as required

 Alarm analysis:
2.Check whether "Reason of unavailable clock source" in the alarm information is "Not
received ESMC PDU message for 5 seconds".
Contact the maintenance personnel of the peer device, and check whether the
interconnected port is in master mode.
Modify the peer-end configuration, and check whether the alarm is cleared.
3.Check whether "Reason of unavailable clock source" in the alarm information is "Received
SSM code is DNU".
After the maintenance personnel of the peer device resolve the fault, check whether the
alarm is cleared.

 Alarm analysis:
4.Check whether "Reason of unavailable clock source" in the alarm information is "Port
speed mode is 10M".
Modify the "Negotiate Mode(NegotiateMode)" and "Port Speed(Speed)" parameters of the
"Ethernet Port(EthernetPort)" object (the "Port Speed(Speed)" parameter must not be set
to 10 Mbps). Check whether the alarm is cleared.

199005407 The board is power off
This alarm is raised if the CMM detects that an OMM, OMP, EGBS, EGFS, EXFS, or
USCC board is powered off..
 Alarm Cause :
A board's ejector lever is unlocked
The physical link of the port is disconnected.
A board is powered off manually.
The board hardware is faulty.
 Impact :
The corresponding board cannot provide services.

199005407 The board is power off
 Alarm analysis:
1.Check whether the board is manually powered off by any maintenance personnel by
checking EMS operation logs.
2.Check whether any extractor of the board is open.

Close the board extractors, and check whether the alarm is cleared.
3.Power on the board, and check whether the alarm is cleared.
4.Remove and reinstall the board, wait for 2 minutes, and check whether the alarm is
cleared,refer to Removing a Board.

Contents

 QoS Alarms
34
199066019 Association broken
 Alarm Description
This alarm is raised if the association is disconnected.
 Probable Cause :
The association is released manually.
The association channels on both ends are faulty.
The association configurations on the local end and the peer end are not consistent.
 Impact :
If the association is disconnected, and upper-layer services of the association may be
affected (signaling link). For example, the signaling office is inaccessible, or the load on
other available associations is increased.

 Alarm analysis:
1.Check the parameters of the "Association (SctpAssociation)" object, including "peer end IP
address 1 (RemoteIp1Addr)", "peer end IP address 2 (RemoteIp2Addr)", "peer end IP
address 3 (RemoteIp3Addr)", "peer end IP address 4 (RemoteIp4Addr)", and "Remote
Port (RemotePort)" meet the actual requirements in accordance with the alarm object.
Modify the association configuration as required, and check whether the alarm is cleared.
2.Contact the maintenance personnel of the peer device to check whether the related
configuration of the peer end is the same with the real requirement.
After the peer maintenance personnel modifies the configuration as required, check whether
the alarm is cleared.
SCTP Four Critical Parameters:Local Port/IP&Remote Port/IP

 Alarm analysis:
3.Perform ping test,Confirm peer IP address is reachable.Also check static route
configuration

 Alarm analysis:
4.Check whether the "ucReason" parameter in the alarm information is "Establishment timer
timed out" or "All paths are inactive".If yes,handle below alarms and whether the alarm
is cleared.
5.Ping 1200 packets in accordance with "Association peer IP Address" in the alarm
information, and check whether packet loss occurs.
Contact the maintenance personnel of the peer device to check whether the peer device is
faulty.
Contact the maintenance personnel of the peer device to remove the fault, and check
whether the alarm is cleared

199066014 M3UA office inaccessible
 Alarm Description :
This alarm is raised if the board detects that the M3UA office is inaccessible.
 Alarm Cause :
The association is disconnected or the AS does not enter service status.
The destination signaling point that receives the signaling transfer point notification is
inaccessible.
 Impact :
The upper level service cannot send or receive messages from a specific office.
New services cannot access an office.
service of the office is released abnormally.

 Alarm analysis:
1.Check whether the "M3ua RouteSet (M3uaRouteSet)" object that uses the "Adjacent
Office Information (RemoteSp)" object is configured in accordance with the alarm object.

 Alarm analysis:
2.Check whether existed alarm “199066019 Association broken”
Handle the above alarm, and check whether the alarm is cleared.
3.Check whether the AS serving for the office is activated.

 Alarm analysis:
4.Query the SCTP association status (activated or not).

 Alarm analysis:
5.Check whether the ASP serving for the office is activated.

 Alarm analysis:
6.Query the "Adjacent Office Information (RemoteSp)" object in accordance with the alarm
object.Contact the maintenance personnel of the peer device to check the connection
between the adjacent SP and destination SP. Ensure that the destination SP is reachable
from the point of the adjacent SP, and check whether the alarm is cleared.

Contents

 QoS Alarms
45
199105050 The CPU utilization rate of processing units in
the USP board is high
This alarm is reported if the USP board detects that the CPU utilization of any one of
the following internal processing units is above the alarm threshold:
Cu exceeds the alarm threshold
Du exceeds the alarm threshold
Dum exceeds the alarm threshold
 Alarm Cause :
The alarm threshold is too low.
The traffic to be currently processed is too high.
 Impact :
The system performance is affected and consequently the system operates slowly.

 Alarm analysis:
1.Check alarm threshold of Cu/Duc/Dum.

 Alarm analysis:
2.In the System Configuration window, check whether "Indication Of Cpu Load Control
Policy" is set to "No", and whether "Switch Of Cpu Access Control" is set to "OFF".
set "Indication Of Cpu Load Control Policy" to "Yes" and "Switch Of Cpu Access Control" to
"ON", and check whether the alarm is cleared.

 Alarm analysis:
3.Check whether the number of currently accessed subscribers is too large.
If yes, Capacity expansion is recommended.
4.Contact the next level of maintenance support.

199105024 IU traffic over load alarm
The base station controller (traffic control policy type: "Mix flow control over IU CS and
IU PS interface") detects that the IU CS+PS mixed traffic exceeds the threshold that
the license permits.
 Alarm Cause :
The IU CS+PS mixed traffic exceeds the threshold that the license permits.
 Impact :
The excess flow cannot guarantee the service quality, which may result in new CS users
failing to access the system and a decline of the PS service quality.

 Alarm analysis:
1.Check whether the "IU traffic flow control type(UIuFlowCtrl)" attribute of the "Flow
Control of Iu Interface(UIuFlowCtrl)" object is set to "IU CS and PS Mix Flow Control".

 Alarm analysis:
2.Check whether the setting of "Authorized threshold(kbps)" in the alarm information is
consistent with the setting of "IU PS and CS traffic mix control low
threshold(IuMixLowThres)" in the "Flow Control of Iu Interface(UIuFlowCtrl)" obje

Contents

 QoS Alarms
53
199003584 Memory insufficient alarm
This alarm is raised if the board detects that the memory usage exceeds the set
threshold (Physical CPU(PhysCpu) object).
 Alarm Cause :
The alarm threshold is too low.
Services are busy, so the memory usage is high.
The board cannot operate properly.
The memory is damaged.
 Impact :
The system performance is affected and thus the system operates slowly.

199003584 Memory insufficient alarm
 Alarm analysis:
Check whether the "Memory alarm threshold" in the alarm information of the faulty board
meets the actual requirements.
modify the "Threshold of Memory lack alarm(MEMAlmThr)" parameter as required. Check
whether the alarm is cleared.

199105051 The configuration of master and slave logservice
is inconsistent
When the active log server detects that its configuration data is not the same as that of
the standby log server, this alarm is raised.
 Alarm Cause :
The differences in the configuration data include:
The versions of the active and standby log servers are different.
The network interface channels of the active and standby log servers are differently
configured.
The processes of the active and standby log servers are differently configured.
 Impact :
If the active and standby log servers are switched over, the new active log server after
switchover may fail to operate properly.

is inconsistent
 Alarm analysis:
1.Syn data from master OMM to slave OMM as below.Check alarms whether cleared

is inconsistent
 Alarm analysis:
2.From alarm information,check log storage path,telnet to OMM board
and analyse logs and reasons.
3.Contact the next level of maintenance support.

Thank you

07 ZXUR 9000 Troubleshooting

Uploaded by

Document Information

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

07 ZXUR 9000 Troubleshooting

Uploaded by

Copyright:

Available Formats

ZTE UR9000 Troubleshooting

 General Troubleshooting Overview

Check Query Consider Work

Query the on-site

© ZTE All rights reserved 3

Instruments and Comparison and

Contact Information of ZTE Technical Support

© ZTE All rights reserved 4

© ZTE All rights reserved

The power distribution subrack

© ZTE All rights reserved

© ZTE All rights reserved

© ZTE All rights reserved

Inter-Shelf Clock Cables

© ZTE All rights reserved

Interconnection Fibers for inter-shelf

© ZTE All rights reserved

Interconnection Ethernet cables for inter-shelf

© ZTE All rights reserved

© ZTE All rights reserved

© ZTE All rights reserved

Querying Software Versi

© ZTE All rights reserved

Querying Software Versi

© ZTE All rights reserved

Querying Software Versi

© ZTE All rights reserved

Querying Software Versi

© ZTE All rights reserved

© ZTE All rights reserved

Querying Software Versi

© ZTE All rights reserved

Querying Software Versi

© ZTE All rights reserved

 General Troubleshooting Overview

© ZTE All rights reserved 22

© ZTE All rights reserved 23

© ZTE All rights reserved 24

© ZTE All rights reserved 25

© ZTE All rights reserved 26

© ZTE All rights reserved 27

© ZTE All rights reserved 28

© ZTE All rights reserved 29

© ZTE All rights reserved 30

© ZTE All rights reserved 31

© ZTE All rights reserved 32

2.Check whether any extractor of the board is open.

3.Power on the board, and check whether the alarm is cleared.

© ZTE All rights reserved 33

 General Troubleshooting Overview

© ZTE All rights reserved 35

SCTP Four Critical Parameters:Local Port/IP&Remote Port/IP

© ZTE All rights reserved 36

© ZTE All rights reserved 37

© ZTE All rights reserved 38

© ZTE All rights reserved 39

© ZTE All rights reserved 40

3.Check whether the AS serving for the office is activated.

© ZTE All rights reserved 41

© ZTE All rights reserved 42

© ZTE All rights reserved 43

© ZTE All rights reserved 44

 General Troubleshooting Overview