ZXSDR Node B Troubleshooting-89

(1)

ZXSDR Node B

Troubleshooting

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: [email protected]

(2)

Chapter 1...1

Maintenance Overview...1

Maintenance Description...1

Maintenance Requirements...1

Maintenance Principles...1

Right Management...1 Data Observation...2 Data Modification...3 Data Synchronization...3 Man-machine Commands...3 Board Operations...4 Update...4

Maintenance Classification...5

Analysis Methods...5

Indicator Status Analysis...5

Signaling Tracing Analysis...6

Alarm Logs Analysis...6

Replacement Analysis...8

Precautions...9

Personnel Qualifications...9

Maintenance Management...10

Data Maintenance...10

Equipment Room Environment...10

Tools and Instruments/Meters...11

Spare Materials and Parts...11

Technical Documents...11

Technical Support...11

Chapter 2...13

(3)

Weekly Routine Maintenance Items...14

Monthly Routine Maintenance Items...15

Semiannual Routine Maintenance Items...16

Other Recommended Maintenance Items...17

Chapter 3...21

Notification and Handling...21

Notification Messages...21

Board Notification...21

SSCOP Error...21

ALCAP Link Error...21

AAL5_MAC Error...22

RS232 Serial Port Error...22

STM-1 B1 Error Code...22

STM-1 B2 Error Code...23

STM-1 Remote B2 Error Code Indication...23

Examples of Other Maintenance Items STM-1 B3 Error Code...23

STM-1 B3 Remote Error Code Indication...24

STM-1 Multiplex Section Remote Defect Indication (MSRDI)...24

STM-1 Higher-order Path Defect Indication (HPRDI)...24

STM-1 Higher-order Path Lady Type Mismatching (HPPLM)...25

Loss of STM-1 Cell Delimitation (LCD)...25

STM-1 Received Cell with CRC Error...25

E1 Link HDB3 Coding Violation...25

E1 Link Slip...26

Too-Heavy ATM Traffic...26

Chapter 4...27

Alarm and Handling...27

Alarm Messages...27

CCS Alarms...28

SSCOP Signaling Link Disconnected...28

Clock Reference Source Lost...29

Clock Module Error...29

Board Communication Link Disconnected...30

(4)

Software Version Error...31

Software Operation Failure...31

Board Parameter Synchronization Abnormal...31

Application Software Monitoring Alarm...32

Database Save Failure...32

Reference Resource PRI Configuration Failure...32

SSCOP Delivery Buffer Overflow...33

Board Configuration Error Alarm...33

SNTP Time Alignment Failure Alarm...33

Clock Reference Source Deterioration...34

CPU Overload Alarm...34

Board Hardware Error...34

RBI Alarms...35

Clock Module Alarm...35

Downlink LVDS Link Error...35

Uplink LVDS Link Error...36

Board Configuration Parameter Error...36

Remote Clock Reference Alarm...37

Optical Module Not-in-position...38

Optical Module Receiving Failure...38

IIA Alarms...39

Loss Of Signal (LOS) of STM-1...39

Loss Of Frame (LOF) of STM-1...39

Multiplex Section Alarm Indication of STM-1 (MSAIS)...39

Loss Of Pointer (LOP) of STM-1 AU4...40

Loss Of Electrical Signal (LOS) of E1 Link...40

Loss Of Frame (LOF) Synchronization of E1 Link...41

Loss of Cell Delimitation (LCD) of E1 Link...41

Loss of IMA Frame (LIF) of E1 Link...41

E1 IMA Group in Non-Working Status...42

PVC Error...42

Transmission Clock Abnormal...43

Configuring IMA Group Failure...44

(5)

Optical Module Not-in-position...46

TAC Alarms...46

Board Hardware Local Channel Error...47

EMU Alarms...47

Ambient Temperature Abnormal...47

Whole Equipment Temperature Rise Alarm...48

Clock Reference Source Loss...48

Rack Power Abnormal...49

Board Communication Link Disconnected...49

Fan Alarm...50

Temperature Sensor Not-in-position...51

Father Node External Equipment Error...51

TRXU Alarms...52

Downlink LVDS Link Error...53

Board Hardware Local Channel Error...54

BP Alarms...55

Uplink LVDS Link Error...55

Uplink Path Operation Abnormal...56

Downlink Path Operation Abnormal...56

(6)

Signal Receiving Path Quality Abnormal Alarm...58

RDM Alarms...58

Antenna VSWR Exceeding 3.0...58

Antenna VSWR Exceeding 1.8...59

Calibration Interface Over-power Alarm...59

LPA30 Alarms...61

Link Disconnected between LPA30 and EMC...61

Over-power Alarm...61 Over-VSWR Alarm: VSWR≥2.8...62 Over-Temperature Alarm...62 Over-Current Alarm...63 LPA30 VSWR Alarm, 2.8>VSWR≥1.8...63

Chapter 5...65

Troubleshooting Examples...65

Overview...65

System Monitoring...66

High CPU Utilization...66

Decreased Radius of BTS Coverage...67

User Complaints...67

Difficult Call Connection...67

Poor Call Quality...69

Slow to Access Internet...70

Chapter 6...73

Emergent Fault Handling...73

Definition of Emergency Fault...73

Handling...73

On-site Handling Procedure...74

Sudden System Breakdown...75

(7)

Chapter 7...77

Terms...77

Appendix A...79

(8)

C h a p t e r

1 Maintenance Overview

This chapter introduces common maintenance types,

maintenance principles and analysis methods and provides

precautions for routine maintenance.

Maintenance Description

Maintenance Requirements

Maintenance personnel must receive systematic training to be

qualified in system maintenance, master fundamentals of ZXWR

B09, and know overall structure and functions of each board, in

addition to some knowledge about network optimization and

network maintenance.

Maintenance Principles

This section introduces what maintenance personnel must pay

attention to in ZXWR B09 maintenance. Any operation against

following principles may have a negative impact on system

operation.

Right Management

Assign personnel-specific usernames and passwords for system

login, operation and maintenance, to restrict operation rights of

maintenance individuals and find operation history through

system logs in case of system malfunction.

(9)

Different users are able to perform different groups of

operations, depending on their levels and rights. Operation and

maintenance software classifies operators into four levels, root

user, advanced user, medium-level user, and ordinary user in

descending order of rights.

1. Root user, with highest level of right, can perform any

operations, including creating users, modifying user

information, deleting users, setting rights and modifying

system configuration. Change initial password of root user

immediately after logging in to the system, for security of

the system

2. Advanced user has the same rights as a root user, except

that it cannot manage user accounts, add/delete boards and

add/delete local cells.

3. Medium-level user, with basic viewing right, can view alarm

and system information. In addition, a medium-level user

can only perform limited types of configuration operations.

4. Ordinary user, with lowest right, can only view information

rather than perform any configuration operation.



Caution



Use right management function to set ordinary equipment

maintenance personnel as medium-level users.



Do not log into the system as root user unless absolutely

necessary.



Do not change network settings of NMS server and Client.



Do not run and operate any other programs not related to

operation and maintenance on NMS server or Client.



Follow general principles of network management to guard

against any virus.

Data Observation



Caution



Perform data observation operations carefully with large

quantities of data to report, including signaling tracing,

running information observation, all users of service

observation, and alarm refreshing. Excessive data report

during data observation may cause system breakdown in

extreme cases.



Caution



Select appropriate time (low traffic period) for data

observation operation, take appropriate measures, save

results in time and clean temporary data in time.

(10)

Chapter 1 Maintenance Overview

Data Modification



Caution



Take care in modifying data, particularly wireless data.



Observe carefully whether there is any effect on system

operation after modifying data.



Caution



Be sure to perform backup before modifying any data, to

ensure rapid restoration when any problem occurs.



Do not perform data synchronization at rush hours (at 10 AM

or 5 PM, Time varies from place to place).



Do not modify foreground database during daytime.

Data Synchronization



Caution



Be sure to backup data before modifying configuration.



Caution



Do not perform data synchronization in daytime unless

necessary.



Check operation log to identify the source if finding any data

of an unknown source.

Man-machine Commands



Caution



Be careful in using commands that lead to foreground

actions, including restart, reset, changeover, save, hardware

test, software download and cell block/unblock.



Do not delete current alarms and history alarms unless

absolutely necessary.



Be sure to lock background man-machine interface after

maintenance personnel leave operation and maintenance

console, to avoid any accidents.

(11)

Board Operations



Caution



Do not reset a board, plug/unplug it or power it off unless

absolutely necessary.



Prepare spare board before replacing a board. Make sure

there are sufficient technicians present for unexpected

emergencies in the case of major operations, such as

changing versions of important boards, or plugging,

unplugging and replacing key boards. Maintenance personnel

working on boards in the foreground must have support from

background personnel.



Caution:



Always wear an antistatic wrist strap before operating boards

on the rack and connect it to the rack before touching a

board.



Touch a metal object first to release static electricity on

hands.



Reduce power gradually (to change users in conversation or

in network access and to prevent users off-conversation from

accessing) when replacing LPA (Linear Power Amplifier).

Update



Caution



Perform upgrade at midnight when there is low traffic.



Keep contact information available for relevant personnel

(like transmission and power supply) to get their timely

assistance when required.



Formulate upgrade plan in advance, covering all emergency

measures.



Do not change procedures set forth in the plan, unless

necessary.



Inform supervisors before upgrading for necessary technical

support.



Assign a person to closely monitor the system for any faults

(12)

Maintenance Classification

Maintenance falls into routine maintenance, notification message

handling, alarm message handling and troubleshooting, by

contents.

1. Routine maintenance

Routine maintenance refers to checking equipment running

status periodically. It is to find out and handle problems in

time to prevent potential damage or fault.

2. Notification message handling

Notification message handling is to analyze all kinds of

notifications during running of the system, to judge whether

anything is abnormal and to take appropriate measures.

3. Alarm message handling

Alarm message handling is to analyze different alarm

messages during running of the equipment, to judge

equipment running condition and to take appropriate

measures.

4. Troubleshooting

Troubleshooting is to analyze, handle and remove detected

faults.

Analysis Methods

Common maintenance analysis methods:



Analysis of indicator status



Analysis of signalling tracing



Analysis of alarm logs



Analysis through instruments and meters



Comparison by replacement



Others

Indicator Status Analysis

Analyze running of a board by statuses of its indicators.

Boards need frequent observation, for the ZXWR B09, are:

control clock switching board CCS, Iub-ATM interface board IIA,

baseband processing board BP and transceiver unit TRXU.

(13)

Signaling Tracing Analysis

Signaling tracing analysis is to check whether signaling flow is

correct. All services have their own signaling flows. It is

acceptable to diagnose system problems according to experience

by viewing differences between current flow and correct flow,

when a service is abnormal.

Important workflow, for the ZXWR B09, includes: cell setup,

common transmission channel setup, paging, random access,

system information update and wireless link setup.

Alarm Logs Analysis

Alarm log analysis is to query history alarms and current alarms

of the system at NM interface, and to analyze and determine

running status of the equipment. Instruments and Meters

Analysis

Commonly-used instruments and meters in routine maintenance

include signaling meters, line testers and power meters.

Signaling Meter Analysis

Signaling meter is to monitor signaling interaction between Node

B and RNC in real time. Figure 1 shows the connection mode of

signaling meter with the equipment.

(14)

Chapter 1 Maintenance Overview FI G U R E 1 AP P L I C AT I O N O F SI G N A L L I N G ME T E R AT R N S RNC RNC Node B Node B Laptop computer 1 2 90% 100% 1₀ % 100_% Optical splitter 90% Signaling meter 10%

RNC and Node B setup several AAL5 links to bear ALCAP,

common NBAP, dedicated NBAP and IPoA after powering on the

equipment. It is acceptable to query VPI and VCI corresponding

to each AAL5 link from OMC background man-machine interface.

It is also acceptable to monitor signaling of corresponding AAL5

link after configuring appropriate VPI and VCI on signaling

meter.

Set up appropriate VPI, VCI and CID on signaling meter, when

AAL2 bears common transport channels (FACH, PCH, and RACH)

and DCH and observes AAL2 signaling. Similarly, it is acceptable

to query its signaling from WOMCR background man-machine

interface. Signaling meter can resolve RRC message of Uu

interface and non-access layer messages.

Signaling meter analysis allows monitoring signaling flows

between Node B, RNC and UE in real time and saving results.

Line Tester Measurement

Line tester supports:

1. To measure information of common channels.

2. To measure related items in coverage area, such as

locations, signal strength and signal quality.

3. To measure energy of each synchronization code in each

timeslot on synchronization channel.

(15)

4. To measure channel power.

5. To measure scramble of the cell.

Power Meter Measurement

Power meter is to measure output power of TRXU and LPA and

to judge whether TRXU and LPA are working normally.

Replacement Analysis

Replace a board module or possibly a faulty connection cable

with a normal board module or connection cable of same type,

and observe whether the fault is recovered after the

replacement.

Use the following replacement analysis methods to rectify faulty

boards or a subsystem.

Active/Standby Switchover

This method applies to active and standby boards configured on

the ZXWR B09 rack, such as CCS.

Operate on background man-machine interface or press

active/standby switchover key on front panel of the board to

reset the board and to trigger active/standby switchover

function.

Perform a switchover again when traffic is light and observe

whether system is normal if the system recovers after

active/standby switchover. Circuit or interface of currently active

board may fail if system is not normal. Replace it and perform

further tests.

Board Resource Block

This method applies to BP.

Block, possibly a faulty BP and check the working status of the

system. Fault resides in BP or interface of the board if system

recovers. Replace the board, unblock it and perform further

tests.

Slot Exchange

This method applies to BP and TRXU. There is need to configure

multiple BPs and TRUXs on the ZXWR B09 rack.

(16)

Exchange slot of a normal board with a possibly faulty board,

and check working states of boards to determine whether fault

resides in the board or interface of the board.

Board Replacement

This method applies to EMU and TRXU configured for single

carrier and single fan. Directly replace a possibly faulty board

with a new board verified as normal.

Cable Replacement

Cables that easily fail include TRXU RF cable, IIA port fiber/E1

line and rack fan connection line. Specific method:

1. Connect RF cable of the TRXU, parts of which are possibly

faulty, to DDL of another normal cell, and check status of the

cell. TRXU and related parts are normal if the cell is still

normal. Otherwise, replace them.

2. Remove connected optical fiber and check it through

self-loop if an optical interface of IIA is blocked. This optical

interface is faulty if self-check is abnormal. Connect the fiber

to another available optical interface of IIA and reconfigure

the data. Replace the optical fiber or check peer equipment if

the other optical interface is found normal in self-loop test.



Caution



Do not direct optical fiber interface to eyes, this may result in

a serious injury.



Do not look at IIA board optical interface directly, this may

result in a serious injury.

It is very difficult to remove fans on the rack. Check power cable

first by connecting it to another slot or using other methods

when finding that a fan is not working normally.

Precautions

Personnel Qualifications

Maintenance personnel must receive pre-service training to learn

necessary knowledge about the equipment and related network,

and they must follow instructions given in related manuals of the

ZXWR B09 to conduct maintenance.

Maintenance personnel must have earnest attitudes and high

competence.

(17)

Maintenance Management

Make a complete set of equipment room maintenance

regulations to standardize daily work of the maintenance

personnel. Forbid non-maintenance management personnel to

perform any maintenance operation.

Make a detailed on-duty log to provide detailed records about

system running, version status, data change, upgrade and

problem handling for easy analysis and troubleshooting once any

fault occurs.

Make a work shift record to clearly define responsibilities.

Do not play games or access the Internet through computer

terminal. Do not install, run and copy any other software not

related to the system at the terminal. Do not use the computer

terminal for other purposes.

Set NM passwords by level. Put them under strict management

and change them periodically so that they are only accessible to

maintenance personnel.

Data Maintenance

Do not reset the equipment, load or change any data unless

absolutely necessary. Do not change background database at

will.

Backup the data before making any changes. Do not delete

backup data after changing data until observation period

(usually one week) expires and be sure that the equipment is

running normally.

Equipment Room Environment

Maintain normal temperature/humidity in the equipment room.

Keep the environment tidy and clean, free from dust and

moisture. Keep rodents or insects out of the equipment room.

Ensure that primary power of the system is stable and reliable,

and check system grounding and lightning protection ground

periodically. Check lightning protection system to make sure all

facilities are in good condition, especially before storm seasons

and after thunderstorms.

The equipment room must have sufficient luminance compliant

with relevant standards. Repair lamps damaged in time and

make sure that light reaches all around the equipment room.

(18)

Tools and Instruments/Meters

All common-use tools, instruments and meters must be

available.

Instruments and meters must be subject to periodic checking

and calibration to ensure function availability and accuracy.

Spare Materials and Parts

Check spare materials and parts regularly to ensure sufficient

stocks and to prevent them from mold.

Store spare materials and parts and faulty ones separately. Mark

them properly for easy identification.

Technical Documents

Store maintenance-related application software and technical

documents by category at a specified location for easy access

when necessary.

Technical Support

Handle faults immediately when they occur. Contact local office

of ZTE Corporation for any faults you cannot solve.

Display contact information of local office of ZTE at a

conspicuous location in the equipment room. Make it known to

all maintenance management personnel, and update it regularly.

(19)

Routine Maintenance

This chapter introduces basic contents for routine maintenance

of the ZXWR B09 and lists daily, weekly, monthly and

semiannual routine maintenance items.

Overview

Routine maintenance refers to periodic preventive maintenance

and check on the equipment so that the equipment can run in a

stable state for long. Routine maintenance includes:

1. Periodic maintenance check: Make routine check and test the

BTS equipment running, required functions, important

performance indices and hardware in compliance with

prescribed operation steps and methods through various

designated background operations or with necessary

instruments and meters on regular and scheduled basis.

2. Periodic check: Check hardware parts of BTS equipment and

its attached equipment one by one. Adjust, correct or replace

any defective part promptly to ensure equipment hardware is

in good condition. Regularly maintain and clean components

with high dust-proof requirements. Clean important

components of other peripherals regularly for normal

running.



Caution



Not all routine maintenance items described apply to all

kinds of possible cases. It is acceptable to refer to them and

work out routine maintenance items according to actual

situation.



RNC (Radio Network Controller), in WCDMA system, controls

all radio parameters, so following maintenance items do not

include network quality analysis and statistics.

(20)

Daily Routine Maintenance

Items

Table 1 shows daily routine maintenance items of the ZXWR

B09.

TA B L E 1 DA I LY RO U T I N E MA I N T E N A N C E IT E M S

Item Sub-item Contents Remar_ks

Alarms and notifications check Alarm message handling

Check all alarms at the NM terminal, and handle them according to alarm level

Notification message handling

Analyze notification messages that frequently occur and it is acceptable to ignore common ones

Troubleshooti ng

Handle common faults such as transmission fault and board fault

Handle faults reflected by the users

Analyze and handle network quality problem reflected by the user

Weekly Routine Maintenance

Items

Table 2 shows weekly routine maintenance items of ZXWR B09.

TA B L E 2 WE E K LY RO U T I N E MA I N T E N A N C E IT E M S

Item Sub-item Contents Remarks

NM

Data backup Backup configuration_{data for OMCB NMS}

Perform system backup at low-traffic

Check and update operating system, anti-virus

software and firewall software

Install a patch for operation system of OMCB system Update virus library and check firewall record Update operating system immediately when there is a key update for it Disk capacity

check

Check whether disk space satisfies system running requirements

(21)

Monthly Routine

Maintenance Items

Table 3 shows monthly routine maintenance items of ZXWR B09.

TA B L E 3 MO N T H LY RO U T I N E MA I N T E N A N C E IT E M S

Radio parameters Engineering parameters Check BTS location parameters Check antenna parameters Update parameters according to project situation. Save parameters for at least two years NM Hardware check

Check whether host and peripherals are in good condition Check whether network communication is normal Software check Check whether operating system is running normally Checking whether NMS process is normal Check whether database system is running normally Data backup Complete backup log files Complete backup data files

Backup the files every time before system upgrade, patching or network structure adjustment BTS equipment Check BTS equipment and its accessories Clean the equipment rack Clean the air filter Check the cable tree

Check DDF, E1/fiber and all connectors Check BTS equipment indicators

(22)

ZXSDR Node B Troubleshooting

Equipment room environment Temperature and humidity Check temperature in the equipment room Check humidity in the equipment room Spare materials and parts Spare parts check

Check spare parts for boards

Check spare parts for racks

Check other spare parts

Semiannual Routine

Maintenance Items

Table 4 shows semiannual routine maintenance items of the

ZXWR B09.

TA B L E 4 SE M I A N N U A L RO U T I N E MA I N T E N A N C E IT E M S

Lightning grounding

Check working ground of the equipment Check protection ground of the equipment room Check grounding trunk line of BTS Check lightning grounding of the building

Test each type of grounding resistance

Check all items before and after a natural disaster Antenna feeder system Iron tower

Check tower light Check structure and foundation for any distortion or sinking Check uprightness and height of the tower

Check all types of bolts

Check anticorrosion and rustproof measures

Check all items comprehensively when meeting gale force above 8, earthquake or other natural disaster

Pole Check installation of

(23)

Item Sub-item Contents Remarks fixing parts

Check stress on the pole, pull wire of pull wire tower and ground anchor Check anticorrosion and rustproof measures Check uprightness of the pole Antenna Check antenna installation parameters

Check fixing status of the antenna

Check pitch angle of the antenna

Feeder

Check installation of feeder and jumper Check feeder connectors

Check waterproof and airproof measures for antenna feeder system

Check grounding status for feeder Check water-dropping bend

Other Recommended

Maintenance Items

Daily Routine Maintenance Items and Semiannual Routine

Maintenance Items list maintenance items closely related to the

ZXWR B09. There are still other maintenance items that affect

the running of the network in daily operations. Refer to Table 5

for examples and recommended maintenance periods.

TA B L E 5 EX A M P L E S O F OT H E R MA I N T E N A N C E IT E M S

Item Sub-item Contents Recommended_Period

BTS equipment

Standing wave ratio test

Test standing wave

ratio of each cell Semiannual

(24)

ZXSDR Node B Troubleshooting

Item Sub-item Contents Recommended

Period

room environment

doors, windows, cabinets and other parts Lighting Check routine lighting and emergency lighting facilities Sockets Check whether AC sockets are complete and in good condition Safety

Check to find out hidden safety troubles

Check fire-control facilities

Check protection measures for the equipment Devices in the equipment room Air conditioner Clean outdoor machine

Clean the air filter Check all alarm messages Check installation of air conditioners Check drainages of air conditioners Measure input voltage and current

Semiannual

Environment monitoring system

Check running status of each type of sensor

Check the power display.

Check the battery display. Clean chassis of monitoring system Monthly Low-voltage power distribution and switch power supply Check whether switch and connector are in good condition Check whether signal indicator and alarm are normal Clean power distribution device Check AC feeder and connection

Monthly

(25)

Item Sub-item Contents Recommended Period parts Measure temperature rise of the fuser Battery Clean batteries Measure voltage of a single battery Measure end voltage of each battery and ambient temperature

Check whether there is any liquid leakage

Check whether contact of leading wire and terminal are well and whether there is erosion Check whether connection pieces between batteries are tight Quarterly Capacity discharging test Yearly Diesel generator Charge startup battery, and add distilled water when necessary Semimonthly Clean the equipment Check startup, cooling, lubricating and fuel systems Run the machine for 20 minutes, without any load

(26)

C h a p t e r

3 Notification and Handling

This chapter introduces types of notification messages that may

occur during running of the ZXWR B09, and gives possible

causes of them.

Notification Messages

When any unrepeatable or transient abnormality occurs during

the running of ZXWR B09, the system reports in the form of

notification. Maintenance management personnel learn running

status of each part of Node B from notification message.

Board Notification

SSCOP Error

Item Contents

Description SSCOP error

Alarm level Alarm notification

Alarm type Communication alarm

Cause SSCOP receives error PDU

ALCAP Link Error

Description ALCAP link error

(27)

Alarm type Error handling alarm

Cause ALCAP receives invalid message or the status is_error

AAL5_MAC Error

Description AAL5_MAC error

Cause Packet loss or error packet occurs on this link, or_{the switching network is error}

RS232 Serial Port Error

Description RS232 serial port error

Alarm level Notification

Cause

1. GPS RS232 serial port receiving frame CRC error;

2. GPS RS232 serial port sending data error; 3. Micro-Control Unit (MCU) RS232 serial port receiving frame CRC error;

4. Micro-Control Unit (MCU) RS232 serial port sending data error.

STM-1 B1 Error Code

Description STM-1 B1 error code alarm

Cause Quality of transmission line is deteriorated (optical

power is too big or too small); there is strong electromagnetic interference near the optical interface; optical connector is not clean; ambient temperature where the equipment works is too

(28)

Chapter 3 Notification and Handling

high.

STM-1 B2 Error Code

Cause

Quality of transmission line is deteriorated (optical power is too big or too small); there is strong electromagnetic interference near the optical interface; optical connector is not clean; ambient temperature where the equipment works is too high.

STM-1 Remote B2 Error Code

Indication

Description STM-1 remote B2 error code indication alarm

Cause This alarm is the reply alarm when peer end _{detects received B2 error codes.}

Examples of Other Maintenance

Items STM-1 B3 Error Code

Cause Quality of transmission line is deteriorated (optical

power is too big or too small); there is strong electromagnetic interference near the optical interface; optical connector is not clean; ambient temperature where the equipment works is too

(29)

Item Contents high.

STM-1 B3 Remote Error Code

Indication

Description STM-1 B3 remote error code indication alarm

Cause This alarm is the reply alarm when peer end _{detects received B2 bit error.}

STM-1 Multiplex Section Remote

Defect Indication (MSRDI)

Description STM-1 Multiplex Section Remote Defect Indication_(MSRDI)

Cause Peer end returns MSRDI alarm to this end when_{receiving LOS, LOF or MSAIS alarm.}

STM-1 Higher-order Path Defect

Indication (HPRDI)

Description STM-1 Higher-order Path Defect Indication

(HPRDI)

Cause

Remote end returns HPRDI alarm to this end when receiving HP-AIS, AU-LOP or path tracing byte mismatching message.

(30)

Chapter 3 Notification and Handling

STM-1 Higher-order Path Lady Type

Mismatching (HPPLM)

Description STM-1 Higher-order Path Lady Type Mismatching_(HPPLM)

Cause Load type (C2 byte) borne by higher-order path inSTM-1 frame structure received by this end is not

ATM. This alarm occurs along with other alarms.

Loss of STM-1 Cell Delimitation

(LCD)

Description Loss of Cell Delimitation (LCD) of STM-1

Cause

The clock is not synchronized or there is a bit error. Other STM-1 alarms occur at the same time usually.

STM-1 Received Cell with CRC

Error

Description STM-1 received cell with CRC error

Cause

The clock is not synchronized or there are error codes. Other STM-1 alarms occur at the same time generally.

(31)

E1 Link HDB3 Coding Violation

Description E1 link HDB3 coding violates the rule

Cause IIA board interface performance; E1 cable quality_{is poor; equipment shares the ground.}

E1 Link Slip

Description E1 link slip alarm

Cause The E1 clock is out of synchronization.

Too-Heavy ATM Traffic

Description ATM traffic is too heavy.

(32)

C h a p t e r

4 Alarm and Handling

This chapter introduces types of alarm messages that may occur

during running of the ZXWR B09, and gives severities (levels),

possible causes and troubleshooting methods.

Alarm Messages

Any problem or fault that occurs during running of the ZXWR

B09 is reported in form of an alarm message.

Usually, alarm messages last some time and do not disappear

until corresponding problems or faults disappear.

Alarm messages fall into four levels, level 1: Critical, level 2:

Major, level 3: Minor and level 4: Alarming.

1. Critical alarm

It is an alarm for board failure.

For example: related resources of a board are blocked,

functions of the system are fatally affected, and maintenance

and management personnel need to replace the board or

perform other troubleshooting procedures to clear the fault.

2. Major alarm

It is an alarm for a serious fault, and it will last for some

time.

Functions of the system are seriously affected, with signs of

services being affected. For example, QoS of a type of

equipment severely degrades, and maintenance and

management personnel need to perform emergency repair to

eliminate the fault.

3. Minor alarm

It is an alarm for a minor fault.

Functions of the system are slightly affected, indicating

existence of factors that do not affect normal services. It is

(33)

fault.

4. Alarming alarm

It is an alarm that indicates existence of potential problems

or problems that are about to affect normal services. It is

necessary to take measures to prevent them from

developing into faults that may severely affect normal

services.

Following sections details possible alarms in the system for

user’s reference. Contact Customer Support Center of ZTE in

time if failing to handle a generated alarm.

CCS Alarms



Note



When handling with alarms, perform in the order of

“Handling” until alarm vanish. For example, if there are 5

steps in “Handling” and alarms vanish when you go on with

Step 3, Seps 4 and 5 are unnecessary.

SSCOP Signaling Link Disconnected

Description SSCOP signaling link is disconnected.

Alarm level Major alarm

Cause

1. Transmission layer parameters are not configured consistent for Node B, RNC and cascaded Node B;

2. Node B transmission layer error; 3. Communication cable error; 4. Peer RNC or cascaded Node B fails.

Handling

1. Check whether transmission layer parameters are configured consistent for Node B, RNC and cascaded Node B. Modify configurations if not consistent;

2. Reset IIA or CCS;

3. Check whether communication cable gets faulty;

4. Check whether peer RNC or cascaded Node B fails.

(34)

Chapter 4 Alarm and Handling

Clock Reference Source Lost

Description Clock reference source lost

Alarm level Alarming alarm

Alarm type Equipment alarm

Cause

1. IIA1 clock reference source lost; 2. IIA2 clock reference source lost; 3. GPS clock lost;

4. BITS clock lost,

Handling

If it is the line clock reference source lost, check whether the system configures the line clock reference source by mistake;

If it is GPS 1pps reference source lost: 1. Check whether there are alarms with GPS. Handle with them if there are any;

2. Check whether connection between EMC and CCS is normal;

3. Replace GPS.

If it is 8 kHz clock reference source lost:

1. Check whether connection between EMU and CCS is normal;

2. Check the external clock.

Clock Module Error

Description Clock module error

Alarm level Critical alarm

Cause 1. 61.44 M clock alarm; 2. 10 M clock alarm; 3. FR alarm; 4. FN alarm. Handling

1. Check whether system clock signal are abnormal;

2. Check whether there are clock signals input on boards;

3. Check whether connection between boards and backplane is abnormal;

4. Check whether board clock receiving module is abnormal.

(35)

Board Communication Link

Disconnected

Description Board communication link is disconnected.

Cause 1. Communication cables error;

2. Board error.

Handling

1. Configuration board must be inserted in the slot. If it is the middle transfer board error, unplug the middle link disconnected board first; 2. Unplug the link disconnected board;

3. Replace the link disconnected board or middle transfer board.

Active/Standby Synchronization

Failure

Description Active/Standby synchronization failure

Alarm level Minor alarm

Cause

1. Database active/standby synchronization failure;

2. Operation software version synchronization failure;

3. Backup software version synchronization failure.

Handling

1. Confirm whether there are active/standby link disconnected alarm;

2. Confirm there are version error alarms on MS board and hardware error on backup board; 3. Not intervene, waiting for the system to restore automatically;

4. Reset the board if the system fails to restore automatically;

(36)

Software Version Error

Description Software version error

Cause There are correlated records of this software onthe foreground or the file of this type software

saved on the foreground is damaged.

Handling Re-download faulty software version.

Software Operation Failure

Description Software operation failure

Cause Software version error or board error

Handling

1. Check whether software version alarm exits; 2. Reset the board;

3. Replace the board.

Board Parameter Synchronization

Abnormal

Description Board parameter synchronization abnormal

Cause

1. Board is configured but not plugged; 2. Board link is disconnected;

3. Board software is abnormal.

Handling 1. Check whether there are board link alarms. If

so, handle with the alarm and repeat the configuration process or restart the board; 2. Check whether there are board application software monitoring alarms. If so, handle with the alarm and reset the board;

3. Re-configure parameters on the background;

(37)

4. Re-start the board.

Application Software Monitoring

Alarm

Description Application software monitoring alarm

Cause 1. Communication line error;

2. Board error. Handling

1. Check whether there are board link alarms; 2. Reset;

3. Replace the board with alarms.

Database Save Failure

Description Database save failure

Cause 1. Harddisk error;

2. Harddisk is full.

Handling Replace the board.

Reference Resource PRI

Configuration Failure

Description Reference resource PRI configuration failure

Cause The system configures the reference source that is

not supported.

Handling Check whether the system has configured the

(38)

delete it and reset the board and the switching.

SSCOP Delivery Buffer Overflow

Description SSCOP delivery buffer overflow

Cause The message is abnormal.

Handling Reset the CCS.

Board Configuration Error Alarm

Description Board configuration error alarm

Cause

1. The board on the left RBI slot is configured error;

2. The board on the right RBI slot is configured error;

3. The board on the BP slot is configured error.

Handling Modify the background configurations.

SNTP Time Alignment Failure Alarm

Description SNTP time alignment failure alarm

Alarm level Alarming alarm

Cause 1. IP address of SNTP server is configured faulty;

2. Link with SNTP server error.

Handling

1. Check whether the link with SNTP server is error;

2. Check whether the IP address of SNTP server is configured faulty.

(39)

Clock Reference Source

Deterioration

Description Clock reference source deterioration

Cause The reference clock quality is too bad.

Handling

1. If current reference source is a line clock, inform RNC-related personnel of normal clock input;

2. Replace the reference source.

CPU Overload Alarm

Description Board configuration error alarm

Cause High-layer software operation abnormal or board

error, which results in frequent alarm reports.

Handling Check whether there are alarms on the board and_{isolate the faulty board.}

Board Hardware Error

Description Board hardware error

Cause Equipment hardware is abnormal.

(40)

RBI Alarms

Clock Module Alarm

Description RBI clock module alarm

Cause

1. System clock signal is abnormal;

2. Connection between board and backplane is abnormal;

3. Board clock receiving module gets abnormal.

Handling

1. Check whether CCS has a clock alarm. Solve it first if such a clock alarm exists;

2. Reset the RBI;

3. Unplug and plug the RBI; 4. Replace the RBI.

Downlink LVDS Link Error

Description Downlink LVDS link error

Cause

1. LVDS transmitting module of upstream board is abnormal;

2. LVDS link of corresponding backplane is abnormal;

3. Interface between board and backplane is abnormal;

4. LVDS receiving module gets abnormal.

Handling

1. Make sure corresponding board and backplane are in good contact;

2. Reset the RBI;

3. Reset upstream boards (BP and TRXU); 4. Replace the RBI;

5. Replace upstream boards.

(41)

Uplink LVDS Link Error

Description Uplink LVDS link error

Cause

1. LVDS transmitting module of corresponding TRXU is abnormal;

2. LVDS link of corresponding backplane is abnormal;

3. Interface between board and backplane is abnormal;

4. LVDS receiving module gets abnormal.

Handling

1. Make sure corresponding board and backplane are in good contact;

2. Reset the RBI;

3. Reset corresponding TRXU; 4. Replace the RBI;

5. Replace corresponding TRXU.

Software Operation Failure

Handling

1. Check whether there are software version alarm;

2. Reset the board; 3. Replace the board.

Board Configuration Parameter Error

Description Board configuration parameter error

Cause Configuration parameter error or hardware error

(42)

CPU Overload Alarm

Description CPU overload alarm

Cause High-layer software operation abnormal or board _{error, which results in frequent alarm reports.}

Handling Observe whether there are alarms on the board

and isolate the faulty board.

Remote Clock Reference Alarm

Description Remote clock reference alarm

Cause

1. System clock signals are abnormal;

2. Connection between the board and the backplane is abnormal;

3. Board clock receiving module is abnormal.

Handling

1. Check whether there are clock type alarms on the CCS. If so, handle with it first;

2. Reset the RBI; 3. Unplug the RBI; 4. Replace RBI.

Board Hardware Error

Cause Equipment hardware is abnormal.

(43)

Handling Replace the error board.

Optical Module Not-in-position

Description Optical module is not in position.

Cause Corresponding optical module is not in position or_abnormal.

Handling

Check whether the corresponding optical module is in position. If so, replace the corresponding optical module.

Optical Module Receiving Failure

Description Optical module receiving failure

Cause

1. The corresponding RF remote is abnormal; 2. Fibers on corresponding optical interface are abnormal;

3. Connection of optical interface that the board corresponds to is abnormal;

4. Optical module that the board corresponds to is abnormal.

Handling

1. Confirm that the connection of the corresponding optical interface is well;

2. Self-loop corresponding optical interface. If the alarm still exists, go on with Step 3. If the alarm disappears, it proves that it is the fiber or corresponding RF remote error. Check the fibers. If the fibers are normal, go on with Step 6; 3. Reset the RBI;

4. Replace RBI alarm optical module; 5. Replace the RBI;

6. If conditions permit, check whether corresponding RF remote is normal.

(44)

IIA Alarms

Loss Of Signal (LOS) of STM-1

Description Loss Of Signal (LOS) of STM-1

Cause

The fiber is not corrected or connected with inverse receiving and transmitting; the fiber is disconnected; local optical module is damaged; peer end does not send optical interface.

Handling

1. Connect the fiber with Node B if not already connected. Exchange receiving and transmitting fibers if the alarm still exists;

2. Make self-loop for Node-B optical interface with a fiber. Replace optical module of IIA or replace IIA if the alarm still exists. Node B is OK if the alarm disappears. Go on with Step 3;

3. Check status of RNC or optical transmission equipment connecting Node B. Loop back with fiber level by level to locate the fault.

Loss Of Frame (LOF) of STM-1

Description Loss Of Frame (LOF) of STM-1

Cause The clock is not synchronized.

Handling

1. Check CCS alarm status. Eliminate clock alarm first if it exists;

2. Check whether clock status of RNC or transmission equipment is normal.

Multiplex Section Alarm Indication of

STM-1 (MSAIS)

Description Multiplex Section Alarm Indication of STM-1 (MSAIS)

(45)

Cause

MS-AIS alarm is sent to downstream equipment when LOS and LOF alarms occur to upstream equipment of Node B. It is also possible that NMS inserts an MSAIS alarm in transmission equipment.

Handling Check alarm status of upstream equipment of Node B _{and eliminate the alarm.}

Loss Of Pointer (LOP) of STM-1 AU4

Description Loss Of Pointer (LOP) of STM-1 AU4

Cause Unsynchronized clock of transmission equipment

results in pointer adjustment. Handling

1. Check whether CCS has a clock alarm;

2. Check whether RNC or transmission equipment has a clock alarm.

Loss Of Electrical Signal (LOS) of E1

Link

Description Loss Of electrical Signal (LOS) of E1 Link

Cause

E1 line is not connected or connected with inverse receiving and transmitting; E1 cable is disconnected; local E1 receiving module or peer E1 transmitting module is damaged.

Handling

1. Check whether E1 line of the alarm link is connected properly or connected with inverse receiving and transmitting;

2. Make self-loop for the alarm link with E1 line. Node B is OK if the alarm disappears. Check whether peer equipment is normal;

3. Insert IIA to another slot, and make self-loop with E1 line. E1 cable or E1 transfer board fails and must be replaced if the alarm disappears and replace IIA if the alarm still exists.

(46)

Loss Of Frame (LOF)

Synchronization of E1 Link

Description Loss Of Frame (LOF) synchronization of E1 Link

Cause The clock is out of synchronization.

Handling

1. Check whether there are Loss of electric Signal (LOS) alarm on IIA;

2. Check whether there are lock alarms on the IIA; 3. Check the alarm status of CCS;

4. Reset the IIA;

5. Check whether the clock status of RNC or transmission equipment is normal.

Loss of Cell Delimitation (LCD) of E1

Link

Description Loss of Cell Delimitation (LCD) of E1 link

Cause

1. The clock is out of synchronization;

2. The TC layer parameters for IMA connecting both parties are inconsistent.

Handling

1. Check the TC layer parameters for IMA

connecting both parties. Modify them consistent if they are inconsistent;

2. Check whether the RNC has a clock alarm.

Loss of IMA Frame (LIF) of E1 Link

Description Loss of IMA Frame (LIF) of E1 link

Cause 1. The scrambling/descrambling parameters for

IMA connecting dual-transmitting are set

(47)

Item Contents inconsistent;

2. The clock is out of synchronization.

Handling

1. Check scrambling/descrambling parameters for IMA connecting dual-transmitting. Modify them consistent if they are inconsistent;

2. Check whether the CCS has a clock alarm; 3. Check whether RNC has a clock alarm.

E1 IMA Group in Non-Working

Status

Description The E1 IMA group is not in a working status.

Cause

This alarm indicates E1 link in IMA group gets faulty, and IMA group is not in a working state, unable to receive/send data. All above E1 alarms may result in this alarm.

Handling

1. Make self-loop for E1 link in IMA group at Node-B side. Node Node-B fails if the alarm still exists. Solve the problem step by step by with the method for solving other E1 alarms. Go on with Step 2 if the alarm disappears

2. Check whether both parties’ IMA settings (IMA version, scrambling/descrambling or not and frame length) are consistent. Modify them if they are inconsistent. Set IMA clock mode of Node B as ITC if doubting the clock fails. The clock is error and check clock boards of the peer end and local end if the alarm disappears. Make loop-back level by level to locate the section where the problem occurs if doubting E1 connection line fails.

PVC Error

Description PVC error

Cause ATM link error

Handling Perform the link self-loop. If the alarm disappears,

(48)

opposite equipment. If the alarm still exists, replace the board.

Transmission Clock Abnormal

Description Transmission clock abnormal

Cause The board is not inserted tight. CCS clock unit _{error. Board error. Backplane error, etc.}

Handling

1. Check whether there are clock type alarm on CCS;

2. Unplug and plug the IIA; 3. Replace the IIA.

Software Operation Failure

Handling

Board Configuration Parameter Error

Handling 1. Reset the board;

(49)

Configuring IMA Group Failure

Description Configuring IMA group failure

Cause Iub port already exists or parameter error

Handling

1. Confirm that parameter configurations are correct;

2. Delete this IMA group and configure again; 3. Reset the board;

Configuring STM-1 Port Failure

Description Configuring STM-1 port failure

Cause Iub port already exists or parameter error

Handling

2. Delete this IMA group and configure again; 3. Reset the board;

Configuring TC Port Failure

Description Configuring TC port failure

Cause Parameter error

Handling

2. Delete this TC group and configure again; 3. Reset the board;

(50)

Configuring PVC Failure

Description Configuring PVC failure

Cause 1. Parameter error;

2. Hardware error.

Handling

2. Delete this PVC and configure again; 3. Reset the board;

CPU Overload Alarm

Description CPU overload alarm

Cause High-layer software operation abnormal or board

error, which results in frequent alarm reports.

Handling Observe whether there are alarms on the board _{and isolate the faulty board.}

Board Hardware Error

Cause Equipment hardware error

Handling Replace the error board

(51)

Optical Module Not-in-position

Description Optical module is not in position.

Cause Corresponding optical module is not in position or _abnormal.

Handling Check whether the corresponding optical module is in position. If so, replace the corresponding

optical module.

TAC Alarms

Software Operation Failure

Handling

Board Configuration Parameter Error

Handling 1. Reset the board;

(52)

Board Hardware Local Channel

Error

Description Board hardware local channel error

Cause Error of tower amplifier that TA corresponds to

Handling Replace the tower amplifier

Board Hardware Error

Cause Equipment hardware error

Handling Replace the error board.

EMU Alarms

Ambient Temperature Abnormal

Description Ambient temperature is abnormal.

Alarm type Ambient alarm

Cause

1. The temperature is too high or too low (out of the temperature range that the system

configures); 2. EMU board error

Handling 1. Check whether the threshold of configuration

parameters is too high or too low;

2. Check whether the ambient temperature is too high (low) with the thermometer;

3. Reset the EMU;