ZXWR RNC Trouble Shooting

(Equipment Class)

ZTE University
Content

 Troubleshooting Tools Introduction

 Troubleshooting Methods
 Troubleshooting Flow
 LED Indicators Introduction
 Boards Replacement
 Emergency Faults Handling
 FE Interfaces Faults Handling
 Typical Troubleshooting Cases
Troubleshooting Tools Introduction

 Fault Management
 Configuration Management

 Dynamic Data Management

 Signaling Trace
Troubleshooting Tools Introduction

 Fault Management
Troubleshooting Tools Introduction
 Configuration Management
Troubleshooting Tools Introduction

 Dynamic Data Management

Troubleshooting Tools Introduction

 Signaling Trace
Troubleshooting Tools Introduction

 Reference Documents
 NetNumen M31(RAN) Mobile Network Element
Management System Fault Management Operation
Guide
 ZXWR RNC (V3.07.310) Configuration Tool Operation
Guide
 ZXWR RNC (V3.07.310) Dynamic Data Management
Operation Guide
 ZXWR RNC (V3.07.310) Signaling Trace Operation
Guide
Fault Management

 The fault management module provides the

following functions:
 General Functions
 Alarm Query
 Setting of Alarm Box
 Configuration of the Alarm System
 Setting of Management Rules
 Setting of Handling Suggestions
 Resetting of Alarm Severity
 Alarm Statistics
Fault Management

 In the NetNumen M31(RAN) client, choose View >

Fault Management on the menu bar

 Click exit Fault Management

Fault Management

 The Fault Management interface

 1. Main menu 4. Alarm information view

 2. Toolbar 5. Message area
 3. Resource/management view 6. Status bar
Configuration Management
 The Configuration Management module provides
the following functions:
 Configuration Data Management Operation
 Mutex Management
 Configuration Data Synchronization
 Data Backup
 Data Recover
 Data Upload
 OMM Configuration Data
 Import Configuration Data
 Add Configuration Data
 Delete Configuration Data
 Query Configuration Data
 Modify Configuration Data
Dynamic Data Management

 The Dynamic Data Management module provides

the following functions:
 Query the state of the current resources
 Implement operation to current resources
 block/unblock
 Spy/De-spy
 Prohibit/De-prohibit
 Reset
 Status Refresh
Dynamic Data Management
 Click on the toolbar of RNC Managed Element tab
Dynamic Data Management

 Choose Dynamic Data Management Object >

PVC
Dynamic Data Management

 PVC state, as shown in figure

Signaling Trace

 Function Introduction
 Trace and observe the real-time signaling messages
that the system reports.
 It facilitates the maintenance personnel to locate faults
and debug the system.
 Signaling trace exists in the form of signaling trace task.
The system can provide signaling trace tasks at both
radio network layer and transmission network layer at
the same time.
Signaling Trace

 Basic Operations
 Software Interface Software Startup
 Link Operation
 Signaling File Operation
 Decode Lib Operation Viewing
 Task Management
 Data Management Tools
 Window
 Exit
Content

 Troubleshooting Tools Introduction

 Troubleshooting Methods
 Troubleshooting Flow
 LED Indicators Introduction
 Boards Replacement
 Emergency Faults Handling
 FE Interfaces Faults Handling
 Typical Troubleshooting Cases
Troubleshooting Methods

 Alarm Information Analysis

 Indicator Status Analysis
 Signaling Tracing Analysis
 Performance Analysis
 Operation Log Query
 Instrument and Meter Analysis
 Test and Loop
 Plugging/Unplugging and Pressing
 Configuration Analysis and Modification
 Comparison and Replacement
Content

 Troubleshooting Tools Introduction

 Troubleshooting Methods
 Troubleshooting Flow
 LED Indicators Introduction
 Boards Replacement
 Emergency Faults Handling
 FE Interfaces Faults Handling
 Typical Troubleshooting Cases
Troubleshooting Flow
Collect Information
Inform and help the
N
on the equipment? maintenance personnel to
Y handle
Y Handle according to the major
major fault?
fault processing flow
N
N
any alarm information?
Y
Analyze and handle the alarm
information
N
alarm disappear?
Y
fault still exist?
Y
N
local fault?
Y Check the function modules
hardware fault? according to the possible cause
N and fault location method
Query the operation logs and
configuration data
Locate the fault according to Record the fault
Y
Is this data correct? the fault handling method
N N
fault exist? Share the experience
Does the fault still exist after Y
the data is modified? Y
Contact ZTE Corporation End
N Support Centre
Content

 Troubleshooting Tools Introduction

 Troubleshooting Methods
 Troubleshooting Flow
 LED Indicators Introduction
 Boards Replacement
 Emergency Faults Handling
 FE Interfaces Faults Handling
 Typical Troubleshooting Cases
LED Indicators Introduction

 Two types of LED indicators on the board panel

 1. Common LED indicators
 The common LED indicators exist on most boards, including:
– ENUM
– RUN
– ALM
– ACT
 2. Special LED indicators
 Except for the common LED indicators, different boards have
their special LED indicators.
LED Indicators Introduction
 [ENUM Description]
 ENUM is independent of other LED indicators on the
board panel.
 It indicates the board status related to the Micro-control
switch, as shown in table
Status Name ENUM Status Description

Tact switch ON Constantly ON The board is not in position or the

version is not downloaded
Tact switch alarm Flashing at 5 Hz The tact switch is ON when the board is
running. The System gives alarms

Pluggable Flashing at 1 Hz The tact switch is ON when the board is

running. The Board is the slave board
or is giving out the resources, so it is pluggable.
Tact switch normal Constantly OFF The tact switch of the board is normal.
LED Indicators Introduction

 [ACT Description]
 ACT indicates the M/S status of the board.
 The master board is not backed up by default. The
description of ACT is as shown in table

Status Name ACT Status Description

Master board Constantly ON The board is the master board
currently.

Slave board Constantly OFF The board is the slave

board currently.
LED Indicators Introduction

 [Combination of RUN and ALM]

 RUN and ALM are on all boards. The description of
their combination is as shown in table
Status RUN Status ALM Status Description
Name
Normal Flashing at 1 Hz Constantly OFF The board is running normally.
running
Flashing at 5 Hz Constantly OFF The version is being downloaded.
Flashing at 1 Hz Flashing at 5 Hz The version download fails, the board is
inconsistent with the configurations, or the
Version can not be downloaded.
Version
Constantly ON Constantly OFF If it is DEBUG version, it indicates that
download
VxWorks succeeds to be downloaded,
waiting to download and run the version.
If it is RELEASE Version, it indicates that
the version succeeds to be Downloaded
and is being started.
LED Indicators Introduction

 [Combination of RUN and ALM]

Status RUN Status ALM Status Description
Name
Constantly Flashing at 5
Self-check The board self-check fails.
OFF Hz
failure
Constantly Flashing at 2 The Operating Support System
OFF Hz startup fails.
Flashing at 5 Flashing at 5
Obtaining logic address fails
Hz Hz
Flashing at 5 Flashing at 2 The basic process power-on
Running Hz Hz Fails or times out.
faults Flashing at 5 Flashing at 1
The initialized core data district
Hz Hz
Flashing at 2 Flashing at 5 The version does not match the
Hz Hz hardware and the configurations.
LED Indicators Introduction

 [Combination of RUN and ALM]

Status ALM Status Description

RUN Status
Name
The medium plane
Flashing at 2 Hz Flashing at 2 Hz Communication
disconnects.
Flashing at 2 Hz Flashing at 1 Hz HW disconnects.
Running The link with OMP
Flashing at 1 Hz Flashing at 2 Hz
faults disconnects.
Flashing at 5 Hz Flashing at 1 Hz In M/S switchover
Keep the
The hardware clock is
previous status Constantly ON
lost.
Content

 Troubleshooting Tools Introduction

 Troubleshooting Methods
 Troubleshooting Flow
 LED Indicators Introduction
 Boards Replacement
 Emergency Faults Handling
 FE Interfaces Faults Handling
 Typical Troubleshooting Cases
Boards Replacement

 [Preparations]
 1. Make sure that the spare parts for replacement is in
good condition and their models are consistent.
 2. Prepare antistatic bags, desiccant, right cardboards
and labels.
 3. Prepare the straight screwdriver and cross
screwdriver.
Boards Replacement

 [Steps] Antistatic ready

work

replace a master replace a slave

board board

originating M/S hardware

switching from NM switching

Draw out the

faulty board

Plug the new

board

Verification
Boards Replacement

 [M/S Switchover]
 Method of originating switching from NM
 Select the board to be switched from OMM client
 Right-click the master board node (rack diagram)
 Click M/S Switching the pop-up menu to send the M/S switching
command.
 Method of M/S hardware switching
 Confirm that M/S boards exist at the same time and run
normally
 Click EXCH to originate the switching.
 Verification
 The ACT indicator on the slave board becomes on
 The master board indicator becomes OFF
Content

 Troubleshooting Tools Introduction

 Troubleshooting Methods
 Troubleshooting Flow
 LED Indicators Introduction
 Boards Replacement
 Emergency Faults Handling
 FE Interfaces Faults Handling
 Typical Troubleshooting Cases
Emergency Faults Handling
Start

Service check

Notify relevant
RNC fault? No personnel to solve
the fault
Yes
Abnormally record
table Abnormality record

Fault cause location

and analysis
Equipment emergency
maintenance advice No Can eliminate the fault
note at ones own?
Yes

Emergency aid Service recovery

Emergency Faults
Service observation Handling Flow
Troubleshooting
record table Information record

End
Content

 Troubleshooting Tools Introduction

 Troubleshooting Methods
 Troubleshooting Flow
 LED Indicators Introduction
 Boards Replacement
 Emergency Faults Handling
 FE Interfaces Faults Handling
 Typical Troubleshooting Cases
FE Interfaces Faults Handling -Association
link broken
 [Fault Phenomenon]
 Association link broken alarm
 [Probable Cause]
 The association is released in dynamic data
management.
 Association configuration is modified at local end.
 Association is released at opposite end.
 Bottom layer link is faulty.
 [Handing Suggestions]
 Check the route information
 Check network cable
FE Interfaces Faults Handling -Association
link broken
 [Handing Suggestions]
 Check association configuration at local end and
opposite end. Checking items include protocol type of
SCTP association, SMP module No, local IP address,
local port No., remote IP address, remote port No., the
number of in/out streams. If the configuration at both
ends is inconsistent, modify configuration to keep
consistency.
 Check if the association is released at opposite end. If
yes, troubleshoot according to the corresponding cause.
Content

 Troubleshooting Tools Introduction

 Troubleshooting Methods
 Troubleshooting Flow
 LED Indicators Introduction
 Boards Replacement
 Emergency Faults Handling
 FE Interfaces Faults Handling
 Typical Troubleshooting Cases
Typical Troubleshooting Cases-- MTP3 link
unavailable
 [Fault Phenomenon]
 MTP3 link unavailable alarm

 [Probable Cause]
 Bottom layer physical link is down or link quality is poor.

 Link test fails to be passed.

 Link deactivation is performed in dynamic data management.

 The link is released at opposite end.

 SMP SPB/SPB2/APBE/APBE2 board resets.

 [Handing Suggestions]
 Check PVC configuration. Configuration of CVPI and CVCI

at both ends should be consistent.

 Check link status in dynamic data management.
Typical Troubleshooting Cases-- MTP3 link
unavailable
 [Handing Suggestions]
 If link interruption occurs now and then, link
unavailability might be caused by MTP3 link test failure.
 check the signaling point code configuration at both ends.
Ensure that the configuration at both ends is consistent.
 check the signaling link configuration at both ends. Ensure that
the SLC (signaling Link Code) configuration at both ends is
consistent.
 Reactivate the link in dynamic data management.
 Check board status. If board status is abnormal,
reset/replace the board.
 The relevant link is released at opposite end. Ask the
opposite end to perform handling as link is unavailable.
Typical Troubleshooting Cases-- Loss of
Optical Transceiver Module Signal
 [Fault Phenomenon]
 Loss of Optical Transceiver Module Signal Alarm
 [Cause analysis]
 The receiving optical fiber/module of local equipment is
faulty.
 The transmitting optical fiber of opposite equipment is
faulty.
 The local receiving optical power is excessively low.
 Operation of LOS insertion is performed at opposite end.
 Optical fiber and optical module is incompatible.
Typical Troubleshooting Cases-- Loss of
Optical Transceiver Module Signal
 [Handing Suggestions]
 Carry out loop test to determine whether the alarm is
caused by local end or opposite end. Perform fiber self-
loop at local equipment. If the alarm persists, fault might
lie in local equipment. If the alarm disappears, inform
the opposite end to troubleshoot.
 Replace the optical module.
 Replace fiber.
 Replace board.
Typical Troubleshooting Cases--Input Clock
Abnormal
 [Fault Phenomenon]
 Input Clock Abnormal alarm

 [Probable Cause]
 The Clock board is not completely operational.

 The clock board is not synchronized with reference clock.

 The clock reference error.

 [Handing Suggestions]
 Reconnect the board and clock reference firmly.

 Replace the cable between the board and the clock

reference.
 Check the signal output from the reference clock source.

 Replace the board.

Typical Troubleshooting Cases--Repeating Common
Transport Channel Deletion and Setup
 [Fault Phenomenon]
 The common transport channel is set up and deleted repeatedly at

Node B side.
 [Probable Cause]
 AAL2 Path 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.

 [Handing Suggestions]
 Check the AAL2 path configuration

 Check the AAL2 path state information

 Check the PVC configuration

Typical Troubleshooting Cases--Repeating Common
Transport Channel Deletion and Setup
 [Handing Suggestions]
 Check the ATM office configuration
 Check the checking path bandwidth
 Checking ALCAP signaling tracing task
Typical Troubleshooting Cases--ROMB Hardware
Startup Fault
 [Fault Phenomenon]
 The board panel indicator is not in operating status all along and
there is the ZXWR RNC/NM link broken alarm.
 [Cause analysis]
 ROMB board is not started normally. It might be related to memory
bank or hard disk.
 [Handing Suggestions]
 Unplug and plug the ROMB board memory bank again.
 Replace the memory bank if ROMB board is still unable to start as
normal after pulling and plugging the memory bank.
 Replace the ROMB board hard disk if the board is still unable to

start after change ROMB board memory bank.

 If the board is still unable to start as normal after replacing

ROMB memory bank and hard disk replace ROMB.