ZXG10-BSC(V2) Maintenance Manual

ZXG10 Z T E G S M W L L S Y S T E M

GGSSMM WWLLLL SSYYSSTTEEMM

MMaaiinntteennaannccee MMaannuuaall OOFF

ZZXXGG1100--BBSSCC ((VV22))

SSHHEENNZZHHEENN,, CCHHIINNAA

Maintenance Manual of ZXG10-BSC(V2)

Preface

ZXG10 is the GSM mobile communications system independently developed by ZTE Corporation, consisting of the ZXG10-MSS switching subsystem and the ZXG10-BSS base station subsystem. The ZXG10-BSS base station subsystem is in charge of providing and managing wireless transmission system in GSM, made up of the ZXG10-BSC base station controller and the ZXG10-BTS base station transceiver, etc. Whether the ZXG10-BSS base station subsystem can run normally on the network greatly depends on whether the system is in correct usage and maintenance. Therefore, it is especially important to have a good command of correct maintenance methods and be capable enough to handle problems properly as well.

ZXG10-BSC (VB Base Station Controller Maintenance Manual is to guide users on how to perform the daily maintenance and deal with faults encountered when using ZXG10-BSC (VB base station controller system, mainly with respect to daily maintenance, alarm processing, and operation information processing.

This manual is divided into three distinct parts:

Part 1: Equipment Maintenance gives you an introduction of how to perform routine maintenance, emergent maintenance and common maintenance.

Part II: Troubleshooting lists alarm types, containing detailed information about message alarm code, alarm level, alarm reason, alarm impact, alarm processing time limit, alarm processing flow, etc.

Part III: Running Information Processing describes in detail the operation information and processing method about MP, COMM modules.

Appendix A: Replacement of Boards and Components provides procedures of replacing boards and components and the cautious items.

Appendix B Abbreviations lists all the abbreviated words present in this book to help you use this manual.

ZXG10-BSC (VB base station controller is BSC (VB in short.


This set of manuals include documents as follows:

ZXG10-BSC (VB Base Station Controller Technical Manual

ZXG10-BSC (VB Base Station Controller Installation Manual.

ZXG10-BSC (VB Base Station Controller Operation Manual

Statement: Since products and technologies keep on developing and upgrading, the information contained herein may not be in perfect compliance with the specific products. Please contact our local offices for updating or renewing information about products.


Page I of III

Table of Contents

1 EQUIPMENT MAINTENANCE .....................................................................................................1

1.1 INTRODUCTION ...................................................................................................................................1 1.2 ROUTINE MAINTENANCE....................................................................................................................3 1.2.1 Daily Routine Maintenance............................................................................................................3 1.2.2 Periodical Routine Maintenance...................................................................................................3 1.3 EMERGENT MAINTENANCE ................................................................................................................4 1.4 COMMON MAINTENANCE MEASURES ...............................................................................................5 1.5 RELATED MAINTENANCE TABLE ........................................................................................................7 1.5.1 Routine Maintenance & Operation Record.................................................................................7 1.5.2 Emergent Maintenance & Operation Record .............................................................................9

2 TROUBLESHOOTING.................................................................................................................10

2.1 ALARM INFORMATION AND HANDLING.............................................................................................10 2.2 BSC(V2) EQUIPMENT ALARM .........................................................................................................12 2.2.1 MP Equipment Alarm ....................................................................................................................12 2.2.2 SYCK Equipment Alarm ...............................................................................................................17 2.2.3 Power Supply Equipment Alarm .................................................................................................19 2.2.4 TIC Board Error .............................................................................................................................22 2.2.5 Other Alarms ..................................................................................................................................24 2.3 BSC(VB COMMUNICATION ALARM .................................................................................................40 2.3.1 MODULE Communication Alarm................................................................................................40 2.3.2 LAPD Communication Error ........................................................................................................45 2.3.3 BOARD Communication Alarm...................................................................................................47 2.3.4 Other Communication Faults ......................................................................................................49 2.4 BSC (VB ENVIRONMENTAL ALARM.................................................................................................52 2.4.1 Equipment Room Environmental Temperature Overhigh Alarm...........................................52 2.4.2 Equipment Room Environmental Temperature Overlow Alarm ............................................53 2.4.3 Equipment Room Environmental Humidity Overhigh Alarm..................................................54 2.4.4 Equipment Room Environmental Humidity Overlow Alarm ...................................................55 2.4.5 Equipment Room Infrared Alarm ................................................................................................56 2.4.6 Equipment Room Smog Alarm ...................................................................................................57 2.5 GPRS COMMUNICATION FAULT ......................................................................................................58 2.5.1 FRP Communication Alarm .........................................................................................................58 2.5.2 BRP Communication Fault ..........................................................................................................63


Page II of III

2.5.3 Other Communication Faults ......................................................................................................67 2.6 BSC（V2）INFORMATION NOTIFICATION......................................................................................70 2.6.1 Reset PP board..............................................................................................................................70 2.6.2 Notification of Times of PCM Slide Code on TIC/SMB ..........................................................70 2.6.3 Services Operation Status Notification ......................................................................................70 2.6.4 PP Automatic Loading Failure Notification ...............................................................................71 2.6.5 PP Compulsory Loading Failure Notification............................................................................71 2.6.6 DSP Automatic Loading Failure Notification ............................................................................71 2.6.7 DSP Compulsory Loading Failure Notification.........................................................................71 2.6.8 System’s Once Encounter of Error ............................................................................................72 2.6.9 Reset Notification of Certain DSP on DRT ...............................................................................72 2.6.10 Receive Alarm on Certain PCM of TIC......................................................................................72 2.6.11 Receive Frame Architecture Loss of PCM on TIC ..................................................................72 2.6.12 Board Status Change Notification ..............................................................................................72 2.6.13 Changes of Environmental Parameters (Temperature/Humidity/Voltage)..........................73 2.6.14 Elimination of Maximum Alarm Number Upon POWP-on or Changeover..........................73 2.6.15 Active/Standby GPPs Handover Notification ...........................................................................73 2.6.16 Outdoor BTS Environment Temperature Notification .............................................................73 2.6.17 Notification of Network Communication Status Changes between MP and PCM.............74 2.6.18 BCCH Switchover Failure Notification .......................................................................................74 2.6.19 Bus Code Error Notification .........................................................................................................74 2.6.20 Board Connection Error Notification ..........................................................................................75 2.6.21 Flow Control Startup Notification ................................................................................................75 2.6.22 No Traffic in the Cell......................................................................................................................75 2.6.23 MP and PCOM Board Handshake Failure................................................................................75 2.6.24 X.25 Protocol Startup on the PCOM ..........................................................................................76 2.6.25 X.25 Protocol Disable on the PCOM .........................................................................................76 2.6.26 PP Board Version Loading Failure .............................................................................................76 2.7 GPRS NOTIFY INFORMATION..........................................................................................................78 2.7.1 Wrong Links Label.........................................................................................................................78 2.7.2 Wrong Entities Label.....................................................................................................................79 2.7.3 Process Number of Transmitting BSSGP Data Packet ..........................................................79 2.7.4 Receive the Status Data Packet of NS Layer Transmitted from the SGSN side ...............79 2.7.5 LAN Error inside SPCU ................................................................................................................80 2.8 RUNNING INFORMATION CLASSIFICATION.......................................................................................81 2.9 RUNNING INFORMATION OF EACH BOARD......................................................................................81


Page III of III

2.9.1 Running Information of Control Layer Board ...........................................................................82 2.9.2 Board Running Information on Network Switching Layer ......................................................87 2.9.3 TC Unit Panel Indicator Information...........................................................................................91 2.9.4 GPRSPP Board Running Information........................................................................................94 2.9.5 POWB Board Running Information ............................................................................................97 2.9.6 Other Boards Running Information ............................................................................................99

APPENDIX A REPLACEMENT OF BOARDS AND COMPONENTS..................................................100

A.1 OVERVIEW ......................................................................................................................................100 A.2 PROCEDURES OF REPLACING PUBLIC BOARDS...........................................................................100 A.3 REPLACEMENT OF OTHER COMPONENTS ....................................................................................102

APPENDIX B ABBREVIATIONS .............................................................................................................105


Page 1 of 106

1 Equipment Maintenance 1.1 Introduction

The purpose of daily maintenance is to completely ensure that the product is in its best condition at any moment so as to guarantee the proper running of the whole system.

1. Maintenance classification

The daily maintenance of ZXG10-BSC (VB consists of two types: routine maintenance and emergent maintenance.

Routine maintenance is a periodical task. It can be regarded as daily routine operation and periodical work based on the length of each maintenance period. Emergent maintenance refers to emergent measures taken to deal with the sudden failures of equipment, or network adjustment such as equipment failure, user notification fault, and unexpected faults in performing routine maintenance. Since the sudden failures befall unexpectedly and usually have serious effect on the service quality, decisive and cautious processing by maintenance personnel are rather important. Also, detailed records are kept afterwards to help analyze the reason of fault, solve the problem, and avoid encountering similar troubles in the future.

2. Requirements and suggestions

The daily maintenance of ZXG10-BSC (VB equipment is considered as the primary task of the maintenance personnel in the equipment room. Since the sound daily maintenance is a crucial factor of guaranteeing the stable operation of the system in the long term, equipment room maintenance related byelaws should be made to standardize and guide the maintenance personnel. Some basic requirements and suggestions about daily maintenance are described as follows:

1) Maintenance personnel should strictly implement the daily and periodical routine check; Keep detailed records without any careless omissions.

2) Maintenance personnel should guarantee the security, the tidiness, and the fitness of temperature/humidity of the equipment room


Page 2 of 106

environment.

3) Maintenance personnel should strictly follow the equipment-operation regulations; Whatever operations and activities (such as arbitrary plug/unplug, reset, initialization, equipment switch-off, data modification, etc.) not included in the daily maintenance scope are all absolutely forbidden. Be sure to wear anti-static wrist straps before touching the hardware system. Ruined or spare parts should be put in the anti-static bags, classified, labeled and stored in safe places.

4) The person in charge of the equipment room maintenance predominates the users’ account, password and authority used to log on the local O&M console and the network management system. He assigns users’ account, password and authority to related maintenance personnel according to the authorities and responsibilities specified to the maintenance personnel.

5) Once problems and troubles are detected, the maintenance personnel should take measures immediately to get rid of them. If encountering more serious problems, maintenance personnel should notify it to related executives, and contact local offices of ZTE Corporation for urgent solutions, and keep detailed records afterwards.

6) Maintenance personnel should receive necessary trainings before on duty. Different technical personnel are put in different positions varying with technical grades.

7) Periodically examine and calibrate those common-use tools and instruments to ensure they are in good condition. The equipment room is recommended to have tools and instruments prepared as follows:

A Preferable tools and auxiliary materials are recommended as follows: flat-pin/cross-pin screwdrivers, diagonal pliers, nipper pliers, wire strippers, unpacking pliers, electric irons, chip extractors, tweezers, spanners, electric drivers, tape measures, insulating rubberized fabrics, binding strips, etc.

B Standby meters are recommended as follows: multi-meter, thermometer, hygrometer, optical power meter, signaling meter,


Page 3 of 106

resistance tester, etc.

8) Guarantee the stable and reliable operation of the power supply system; Check the system grounding status periodically.

9) To prevent the wires from damages , periodically check the wires connecting systems to make sure no weighty objects are laying over them.

1.2 Routine Maintenance

1.2.1 Daily Routine Maintenance

Daily routine maintenance is to check the running condition of the equipment.

1. Querying Alarm Information

By means of faults management system in the ZXG10-OMCR (VB O&M system, the supervision of the entire ZXG10-BSS (VB operation status is enabled. Equipment room watchers should examine site alarms, rack alarms or other alarms via alarm inquiry window, record them in detail and keep constant contact with technical personnel so as to locate and resolve troubles. Refer to ZXG10-BSC (VB Base Station

Controller Operation Manual for methods related to alarm information inquiry.

2. Module Running Status

View the indicator lights of each module on the rack to see whether their display is all right (See Section 3. B; if any of the alarm lights is on, contact technical personnel immediately so as to relocate and resolve troubles.

1.2.2 Periodical Routine Maintenance

1. Check BSC modules

Check the amount, type and version of standing modules once week; make sure their storage conditions comply with requirements; the amount is sufficient and easily available. Remember to check the exchanges and repairs of faulty modules as well.


Page 4 of 106

2. Faults statistics

Make statistics of faulty modules in detail every week.

3. Hardware test: check once a month.

1) Check whether the power lines are connected stably; Make sure the wires are rusty yet.

2) Check whether the grounding lines are connected stably; Make sure the wires are not rusty yet.

3) Periodically check the system-connecting wires to make sure there are no weighty objects laying over them, thus preventing the wires from damages.

4. Transmission

Check the connectors of transmission wires between optical terminals, from the microwave rack to the BSC rack to make sure they still remain fixed without twisted, extruded, distorted or tightened. Test the standing port.

1.3 Emergent Maintenance

Emergent maintenance refers to the immediate measures necessary for dealing with sudden failures of ZXG10-BSC (VB equipment. As the sudden failures turn up unexpectedly and usually have serious effect on the service quality, decisive and cautious processing by maintenance personnel are rather important. Also, detailed records are kept afterwards to serve as reference for avoiding similar troubles in days to come.

In general cases, the processing flow and the processing measures of sudden failures can be classified as follows:

1. Sudden failures and disasters in equipment room

1) Primary faults

Power supply system failure; Flood and Fire; Air-conditioning system failure, as a result, temperature and humidity severely exceeds the standard specifications.


Page 5 of 106

2) Maintenance measures

After viewing the alarm message from the OMCR system of BSS the subsystem, check the equipment room environment immediately, locate the fault and confirm the reason, rapidly resolve the fault and notify it to the higher-level executives. Keep detailed records to help clear out the hidden troubles.

2. Sudden failures of equipment itself

1) Primary faults

Include hardware parts, such as damages, designated positions unavailable, poor contact found in modules and unit module. Also included are software parts like disordered data or programs, etc.

2) Maintenance measures

A Via plug/unplug, partial problems such as designated position unavailable and poor contact can be solved. Or by means of replacement or isolation, you estimate the damages of hardware. Data disorder can be inquired and corrected via operation in the OMCR system of the BSS base station controller subsystem

B Software/ hardware faulty phenomena are quite complicated. If problems remain unresolved even though simple measures listed above have already been taken, please contact technical personnel or local offices of ZTE immediately and notify it to related executives at the same time. Keep records in detail afterwards so as to help clear out similar hidden troubles in the days to come.

1.4 Common Maintenance Measures

In daily maintenance, common measures are classified as follows:

1. Observation

This is mainly to locate the trouble via viewing the alarm message from the OMCR management terminal. Observation is a first-of-all method that


Page 6 of 106

the maintenance personnel use when encountering troubles. The correct judging of the observed result is a key factor of correctly analyzing and resolving problems. Therefore, maintenance personnel must be quite familiar with indicator lights on each module and be fully aware of the meanings of alarm information at different levels displayed on the management terminal.

2. Plug/unplug

At the very beginning of finding faults in a certain module, unclose the fastener on the front panel, then plug/unplug the connector between the module and the external interface so as to remove the faults resulting from improper contact or processor abnormality.

3. Replacement

Using a functionally proper module to replace the module to be checked to confirm whether the latter has gone wrong. If plug-unplug method doesn’t work, choose the replacement way.

Warning: When plugging/unplugging/replacing modules, refer to Appendix A for cautious items and operation procedures in the case of replacing boards and components.

4. Isolation

If only partial system has gone wrong, you isolate this part from related modules or racks to judge whether the fault results from interaction between then. The common isolation way is to self-loop the in/output interface of a certain module so as to isolate and remove the problems of the related system.

5. Self-test

When the system or module is powered on again, judge if there is any fault y way of self-test. In normal cases, when a module is powered on and self tested, the indicator lights on its panel will flash regularly. This way will tell whether the module itself is faulty.

6. Press

Turn off the power and then press the cable connectors. This will help remove the troubles resulting from improper contact.


Page 7 of 106

7. Combination

Combining all the methods listed above with one’s experience accumulated in routine maintenance can clear whatever faults.

1.5 Related Maintenance Table

1.5.1 Routine Maintenance & Operation Record

Table 1-1 shows a daily maintenance record. Table 1-2 is a periodical maintenance record.


Page 8 of 106

Table 1-1 Daily Maintenance Record

Item Operation Items Running and

processing result

Operator Remarks

Querying Alarm Information Operatio

n status Module Running Status

Table 1-2 Periodical Maintenance Record

Item Operation Items Maintenance

Period

Running and

processing

Results

Operator Remarks

BSC Module Check

Check BSC module

Fault

Statistics

Faults statistics

Check the power

cables connection

Check the grounding

cables connection

Check the cables

connecting

equipment

Check the equipment

installation

Hardware

Check

Check the auxiliary

equipment

Transmission Check the

transmission


Page 9 of 106

1.5.2 Emergent Maintenance & Operation Record

An emergent maintenance record is as Table 1-3 shows:

Table 1-3 Emergent Maintenance Record

Office name: Processor:

Occurring Time: Solution time:

Fault notification source:

□ user call □ alarm system □ discover in routine maintenance □ Others

Fault types:

Description:

Solution:

Result:

Opinions from the person in charge:


Page 10 of 106

2 Troubleshooting 2.1 Alarm Information and Handling

The ZXG10-OMCR (VB fault management system monitors the entire running status of ZXGQO-BSS (VB system in concentrative mode, by testing, notifying and processing the abnormal happenings of telecom networks and environments. These functions are realized via fault alarm and fault diagnosis. The alarm management system is to locate the accurate position of the trouble. By means of relevant judging performance, the display of alarm on the user end interface is enabled, realizing the real-time notification of actual alarms.

In terms of real-time property, the alarm issue method is divided into general notification and emergent notification. The former merely indicates the unrepeatable or instantaneous troubles arising while the system is running. Usually, if the notification of this kind of troubles is not so frequent, that means this trouble might be caused by accidentally environmental factors, and the maintenance personnel do not need any processing actions; however, if the notification becomes frequent and even long-playing, it tells that the maintenance personnel must immediately locate the reason and solve it in time.

The alarm may last for some time, so, it usually affects the normal services, maintenance and running reliability of the system in different degrees; the alarm can be divided into four levels varying with severity as follows: Principles of rating four levels of alarm are listed in Table 2-1:


Page 11 of 106

Table 2-1 Alarm levels

Alarm level

Range of services seriously affected

Range of equipment

security seriously affected

Range of system

operation reliability seriously affected

Range of system maintainability

seriously affected

1 The whole BSS The whole BSS

2 One or more sites

BSC or a site The whole BSS The whole BSS

3 One or more carrier frequencies

One or more carrier frequencies

BSC or a site BSC or a site

4 One or more channels

No influence. One or more carrier frequencies

One or more carrier frequencies

Notes: in the definition of alarm levels, the affected range only refers to the influence on a single item, i.e., the level of a certain alarm can be determined if a certain index such as the reliability and security reaches the specified range. If an alarm item has influence on more than one index, the alarm level may be increased.

This chapter discusses the notification code of BSC (2.0) and GPRS, and the reason of alarm information. The processing flow is also included. Please refer to relevant maintenance manuals for the alarm information of BTS，MB，BS21 and OBTS respectively.

Main alarm modules are: MP, COMM, etc. The alarm information, notification information and the processing flow of BSC (VB system are described in detail as follows:


Page 12 of 106

2.2 BSC(V2) Equipment Alarm

In the following descriptions, if the alarm reason is defined as “unknown,

reason code: 10”, it shows that the alarm possibly results from various reasons

and is difficult to define.

2.2.1 MP Equipment Alarm

2.2.1.1 BSCMP Alarm

1. Alarm code:0

2. Alarm level: 2

3. Alarm cause

1) The opposite end MP powers down or is not installed yet, cause code: 46.

2) The opposite end Watchdog overflows, cause code:48.

3) The opposite end MP software goes wrong, cause code: 49.

4) The standby MP goes wrong, cause code: 50.

4. Effect: If the standby MP goes wrong, the system operation reliability will be seriously reduced.

5. Processing time limit: Instant processing.

6. Processing flow: Power on or reset or replace standby MP.

7. Remarks: None.


Page 13 of 106

2.2.1.2 Disk Alarm

1. Alarm code:1

2. Alarm level: 2

3. Alarm cause: The space available of MP runs short, with cause code: 51.

4. Effect: Affects the normal operation of system software, with respect to alarm data, temporary data storage, etc.


6. Processing flow: Delete the files no more useful on MP, release the disk space to guarantee that the space available accounts for at least one fifth of the whole MP disk space.

7. Remarks: None.


Page 14 of 106

2.2.1.3 BSC CPU Bus Alarm

1. Alarm code: 3

2. Alarm level: 1

3. Alarm cause

1) Share memory board bus error, cause code: 56.

2) COMM board bus error, cause code: 57.

3) Unknown, cause code: 10.

4. Effect: The normal operation of BSC system fails, as a result, the system or the board is disabled and the transmission data is in disorder.


6. Processing flow:

1) Replace the faulty memory board.

2) Replace the faulty COMM board.

3) Replace MP.

4) Replace the backplane at the control layer of BSC rack

7. Remarks: None.


Page 15 of 106

2.2.1.4 Data Loading Error

1. Alarm code: 4

2. Alarm level: 2

3. Alarm cause

1) Database loading errs, with cause code: 58.

2) Database synchronization errs, with cause code: 59.

3) Unknown, cause code: 10.

4. Effect: The normal operation of BSC system is disabled; data transmission is in disorder.


6. Processing flow:

1) MP reset.

2) If errors still exist after MP is reset, reconfigure and adjust the synchronization data.

7. Remarks: None.


Page 16 of 106

2.2.1.5 CPU Overload of MP

1. Alarm code: 6

2. Alarm level: 2

3. Alarm cause: Unknown, cause code: 10.

4. Effect: Service access is limited.


6. Processing flow: Contact the local office of ZTE Corporation.

7. Remarks: None.


Page 17 of 106

2.2.2 SYCK Equipment Alarm 2.2.2.1 BSC Synchronization Clock (SYCK) Board Alarm (serious)

1. Alarm code: 0x200

2. Alarm level: 1

3. Alarm cause 1) The 8M frame header signal output errs, with cause code: 11.

2) The 8M clock output errs, with cause code: 12.

3) The 16M frame header signal output errs, with cause code: 13.

4) The 16M clock output errs, with cause code: 14.

5) Communication breaks off, with cause code: 1.

6) Power down, with cause code: 2.

4. Effect: Communication is partially instable inside the BSC system, generally accompanied by multiple of other alarms; If no multiple alarms arise, it shows that the faulty part doesn’t affect the normal work configured via BSC system for the moment.

5. Processing time limit: If two clock boards encounter alarms at the same time, both should be processed immediately. If merely the active board encounters the alarm, the system will start to use the standby board, but the alarmed clock board must be replaced within three days. As the system can still run in the case of only one clock board, no influences will be brought to the system for the moment.

6. Processing flow: 1) If merely the active board alarms, the active/standby boards

will automatically switch off to initiate the standby board. Please give the faulty boards to the local office for immediate replacement.

2) If both boards alarm, orderly replace active/standby boards for immediate measures.

7. Remarks: None.


Page 18 of 106

2.2.2.2 BSC Synchronization Clock (SYCK) Board Alarm (general)


2. Alarm level: 3

3. Alarm cause: D/A conversion goes beyond its range, with cause code: 16.

4. Effect: Interface slip code, error code and out-of-frame possibly cause the alarm; the SS7 and LAPD link err. But they don’t affect the normal operation of services in general cases.

5. Processing time limit: Replace them within 15 days.

6. Processing flow:

1) Check the MSC clock source to see whether it deviates; If so, calibrate it immediately.

2) Replace the board.

7. Remarks: Usually caused by the aging of the clock.


Page 19 of 106

2.2.3 Power Supply Equipment Alarm

2.2.3.1 POWB board alarm (serious)


2. Alarm level: 2

3. Alarm cause

1) Power supply output 5V undervoltage, with cause code: 22.

2) Power supply output 5V overvoltage, with cause code: 28.

3) Power supply output 12V undervoltage, with cause code: 26.

4) Power supply output 12V overvoltage, with cause code: 32.

5) Power supply output -12V undervoltage, with cause code: 27.

6) Power supply output -12V overvoltage, with cause code: 33.

4. Effect: If this fault happens, each board will remain in the status of under or overvoltage. This will seriously affect the life of the board, which will stop working if situation becomes worse.


6. Processing flow:

1) If both of the active and standby power boards exist at this layer, you should pull out the alarmed board immediately and replace it within 15 days.

2) If only one power board is available at this layer, you should pull out the alarmed board immediately, and unplug a standby board from other layers to plug it into this layer as a temporary substitute. Fill up the vacancies of the power boards in other layers within 15 days.

7. Remarks: None.


Page 20 of 106

2.2.3.2 POWB board alarm (common)


2. Alarm level: 4

3. Alarm cause: The board switch disconnects itself; the board can’t supervise; or location unavailable / power down happens, with cause code: 62.

4. Effect: The power boards usually back up each other in active/standby mode; if one of the boards alarm, it is unnecessary to handle it in a hurry. But the alarm will affect the test and maintenance of the power boards.

5. Processing time limit: Be sure of reset within 15 days.

6. Processing flow:

1) Check the power board to see whether it is its position; If not, leave it alone temporarily or shield it.

2) Check whether the COMM cables are connected to this power board; if not, reconnect related cables.

3) Check whether the RS485 cables on the backplane are loose.

4) Check whether the MONI board is faulty; If so, replace the board.

7. Remarks: None.


Page 21 of 106

2.2.3.3 POWP board alarm (common)


2. Alarm level: 1

3. Alarm cause

1) Neither of the dual lines on the power board works ,with cause code: 152.

2) The POW P fan system errs, with cause code: 153.

3) POWP over/undervoltage, with cause code: 154.

4) The left line of POWP boards stops working, with cause code: 155.

5) The right line of POWP board stops working ,with cause code: 156.

4. Effect: This error will affect the proper operation and equipment security of the BSC system.


6. Processing flow:

1) Check if the power supply is normal.

2) Check whether the RS485 cables on the backplane are loose, if so, fasten the cables.

3) If it is difficult to locate the trouble, contact the local office of ZTE.

7. Remarks: None.


Page 22 of 106

2.2.4 TIC Board Error

2.2.4.1 Trunk Interface Circuit 8M8K Clock Loss


2. Alarm level: 2


4. Effect: The 8M and 8K clock of trunk interface circuit drops, causing the trunk interface circuit to err in communication. If the trunk interface goes wrong, it might lead to failure in partial modules of the BSC system.


6. Processing flow:

1) Check whether the clock unit works properly. If the clock unit alarms, remove the alarm first.

2) Check whether the backplane cables are normal. If abnormal, handle it immediately.

3) Try to plug and unplug the board once more to see whether the system can recover.

4) If the measures listed above still don’t work, contact the related local office of ZTE.

7. Remarks: None.


Page 23 of 106

2.2.4.2 Trunk Interface Circuit 8K Clock Loss


2. Alarm level: 2


4. Effect: The 8K clock of trunk interface circuit drops, causing the trunk interface circuit to err in communication. If the trunk interface goes wrong, it might lead to failure in partial modules of the BSC system.


6. Processing flow:

1) Perform self-loop check on corresponding 2M ports.

2) Check whether the clock unit in the BSC system works properly. If the clock unit alarms, remove the alarm first.

3) Check whether the backplane cables are normal. If abnormal, handle it immediately


5) If the measures listed above still don’t work, replace the board.

7. Remarks: None.


Page 24 of 106

2.2.5 Other Alarms

2.2.5.1 DSNI Network Drive Board Alarm


2. Alarm level: 2

3. Alarm cause

1) Communication with MP breaks off, with cause code: 1.


4. Effect: The direct aftereffect is transmission failure in the boards of corresponding positions, in that the communication links of multiple boards disconnect and generate alarm.


6. Processing flow:

1) If this faulty board is the original active board, the system will automatically switch the standby board into the active board. If the faulty board is the standby one, unplug it first and replace it as soon as possible.

2) If no standby board is available, you should immediately unplug a standby board form other DSNI boards equipped with active/standby boards, and plug it into the position absent from standby board, simultaneously make adjustment at the background.

Warning: Never unplug the DSNI-C board to replace the faulty DSNI board.

7. Remarks: The wobble state and the position unavailable of DSNI board, or the hardware error will result in alarms as well.


Page 25 of 106

2.2.5.2 CKI Clock Interface Board Alarm


2. Alarm level: 3

3. Alarm cause: Power down, with cause code: 2.

4. Effect: The direct aftereffect is that the BSC clock system will use the SYCK clock source of its own or the clock source synchronized from the MSC system. In this case, the system will occasionally encounter error codes and SS7 error.

5. Processing time limit: If the equipment room doesn’t offer BITS clock, just leave as it is. If the BITS clock is available in the equipment, settle it within 7 days.

6. Processing flow:

1) Check whether there is BITS clock and whether the BITS clock source has gone wrong.

2) If the BITS clock is all right, try to plug the CKI board again.

3) If the fault is still there after the CKI board is tightly plugged, then replace it with another board.

7. Remarks: The BITS clock reference loss or the hardware error might generate alarms as well.


Page 26 of 106

2.2.5.3 Fan Alarm


2. Alarm level: 2

3. Alarm cause: The POWP fan system errs, with cause code: 153.

4. Effect: Both of the routine work and the equipment security in the whole BSC system will be affected.


6. Processing flow:

1) Check whether the power supply system is normal. If both of the power module and the power supply system are abnormal, handle them immediately.

2) If the trouble can still not be located, contact the local office of ZTE.

7. Remarks: None.


Page 27 of 106

2.2.5.4 MPPP(COMM board between MP and PP) Error


2. Alarm level: 2

3. Alarm cause



4. Effect: The MPPP board is usually in active/standby status. If one of the boards errs, it won’t affect the system operation but the reliability of the system will be affected. If both MPPP boards go wrong, the operation & maintenance link between MP and relevant PP boards will break off, thus, losing control of relevant PP boards.


6. Processing flow:

1) Check whether the MPPPP board is powered on.

2) Check whether the clock board generates alarm; If so, remove the clock error first.

3) Reset MPPP board and see whether the fault still exists.

4) Check whether the connection lines at the backplane become loose.


7. Remarks: The disconnection between MPPP board and MP, power down, hardware fault, clock loss, out of position and so on will also generate alarms.


Page 28 of 106

2.2.5.5 MTP SS7 Board Error


2. Alarm level: 3

3. Alarm cause



4. Effect: The MTP board is usually in active/standby status. If one of the boards errs, it won’t affect the system operation but the reliability of the system will be affected. If both MTP boards go wrong, the communication link between BSC and MSC systems will break off, resulting in the interrupt of related services of this SS7 board.


6. Processing flow:

1) Check whether the MTP board is powered on.


3) Reset MTP board and view whether the fault still exists.



7. Remarks: The disconnection between MTP board and MP, power down, hardware fault, clock loss, out of position and so on will also generate alarms.


Page 29 of 106

2.2.5.6 MONI（BSC MONI Board）Error


2. Alarm level: 3

3. Alarm cause



4. Effect: The monitoring of these boards such as power supply board, the clock board and the network drive board will be disabled.


6. Processing flow:

1) Check whether the MONI board is powered on or tightly plugged.

2) Check whether the clock board generates alarm; if so, remove the clock error first.

3) Reset MONI board and view whether the fault still exists.



7. Remarks: The disconnection between MONI board and MP, power down, hardware fault, clock loss, out of position and so on will also generate alarms.


Page 30 of 106

2.2.5.7 SMEM Share Memory Board Error


2. Alarm level: 2

3. Alarm cause



4. Effect: The direct aftereffect is the disconnection between the active and standby MP boards, which generates alarm.


6. Processing flow:

1) Check whether the SMEM board is powered on or tightly plugged in its position.

2) Reset SMEM board and view whether the fault still exists.

3) Check whether the backplane is normal.


7. Remarks: The disconnection between SMEM board and MP, power down, hardware fault, clock loss, out of position and so on will also generate alarms.


Page 31 of 106

2.2.5.8 Environmental Monitoring Board (PEPD) Alarm


2. Alarm level: 2

3. Alarm cause



4. Effect: it is impossible to monitor the equipment room environment with respect to: temperature, humidity, smog, etc. In this case, the maintainability of the system will be affected.


6. Processing flow:

1) Check whether the PEPD board is powered on or too tightly plugged in its position.




7. Remarks: The disconnection between PEPD board and MP, power down, hardware fault, clock loss, out of position and so on will also generate alarms.


Page 32 of 106

2.2.5.9 LAPD COMM Board Alarm


2. Alarm level: 2

3. Alarm cause



4. Effect: The LAPD communication link breaks off; then the communication links of all the sites related to LAPD board stop, as a result, the system operation can’t proceed.


6. Processing flow:

1) Check whether the LAPD board is powered on or too tightly plugged in its position.

2) Check whether the clock board is all right. If not, remove the clock fault first.

3) Reset the LAPD board and see whether the fault still exists.



7. Remarks: The disconnection between LAPD board and MP, power down, hardware fault, clock loss, out of position and so on will also generate alarms.


Page 33 of 106

2.2.5.10 MPMP Inter-module Communication Board Alarm


2. Alarm level: 1

3. Alarm cause



4. Effect: Communication links between modules disconnect. The signaling links of all the related modules break off; as a result, the normal operation of the system is disabled.


6. Processing flow:

1) Check whether the MPMP board is powered on or too tightly plugged in its position.

2) Check whether the clock board is all right. If not, remove the clock fault first.

3) Reset MPMP board and see whether the fault still exists.

4) Check whether the connection lines at the backplane become loose or improper.

5) If the measures listed above still don’t work, replace the board and contact the related local office of ZTE.

7. Remarks: The MPMP board out of position, the hardware fault and the clock loss will also bring about alarms.


Page 34 of 106

2.2.5.11 PCOM Board Alarm


2. Alarm level: 1

3. Alarm cause



4. Effect: The cell broadcast short message service breaks off.


6. Processing flow:

1) Check whether the PCOM board is powered on or tightly plugged in its position.


3) Reset PCOM board and see whether the fault still exists.

4) Check whether the connection lines at the backplane become loose or improper.


7. Remarks: The disconnection between PCOM board and MP, power down, hardware fault, clock loss, out of position and so on will also generate alarms.


Page 35 of 106

2.2.5.12 Module Load Control Alarm


2. Alarm level: 2

3. Alarm cause

1) The module overload leads to flow control, with cause code: 3.

2) The central module overload leads to flow control, with cause code: 4.

4. Effect: Service access is limited.

5. Processing time limit: Wait for self-recovery.

6. Processing flow: When load reduces, the system will automatically recover. If the system doesn’t recover still, contact the local office of ZTE.

7. Remarks：None.


Page 36 of 106

2.2.5.13 PCM Alarm of TIC/SMB/DTI


2. Alarm level: 3

3. Alarm cause

1) The receive signal lost, with cause code:150.

2) All of 1s alarm, with cause code: 151.

4. Effect: Related TC units can’t work properly, affecting the communication of the SS7 link between BSC and MSC systems.

5. Processing time limit: Wait for self-recovery.

6. Processing flow:

1) Check whether the faulty E1 is properly connected.

2) Check whether the E1 line is intact.

3) Using the intact E1 to self loop the faulty E1, then see if the alarm disappears. If the alarm no longer exists, it means this board is all right, only replace the E1 line.

4) If the measures listed above still don’t work, replace the board and contact the related local office of ZTE.

7. Remarks: A certain chip on the TIC/SMB/DTI board or an external connection error may also lead to alarms.


Page 37 of 106

2.2.5.14 DSP Alarm on DRT/EDRT/BRP


2. Alarm level: 3


4. Effect: The board will partially work improperly.


6. Processing flow:

1) Reload correct software version to this DSP.

2) If the alarm still occurs frequently, replace the board.

7. Remarks: It is possibly because of the software error or hardware problem in this DSP.


Page 38 of 106

2.2.5.15 COMI Alarm


2. Alarm level: 2


4. Effect: The 8M or 8K clock of the COMM interface board lost, causing the abnormality of COMM interface board. If the COMM interface board goes wrong, it may result in the partial breakdown of the BSC system.


6. Processing flow:





7. Remarks: The software error or hardware problems in this DSP will probably lead to alarm.


Page 39 of 106

2.2.5.16 SMB Board Error


2. Alarm level: 2


4. Effect: The BTS related to SMB board works improperly.


6. Processing flow:

1) Check whether the faulty SMB board is in its position and other related BIPP boards.

2) Check whether the related cables are properly connected or become loose or abnormal. If not, adjust them.

3) Check whether the clock board works properly.

4) Reset the faulty SMB board manually. Start from the background alarm interface to check and confirm whether the SMB board is in proper status. If the alarm no longer exists, it means that fault is removed.


7. Remarks: The disconnection between SMB board and BIPP, power down, hardware fault, clock loss, out of position and so on will also generate alarms.


Page 40 of 106

2.3 BSC(VB Communication Alarm

2.3.1 MODULE Communication Alarm

2.3.1.1 Signaling Point Unreachable


2. Alarm level: 1


4. Effect: SS7 initiation is disabled.


6. Processing flow:

1) Check the signaling link status, corresponding MTP boards, or physical connection lines.

2) Check the office-direction data, MTP data and link connection data to see whether they are correctly configured.

7. Remarks: Problems in data or physical configuration may lead to alarms.


Page 41 of 106

2.3.1.2 SS7 L3 Alarm


2. Alarm level: 2


4. Effect: One of the SS7 links is disabled.


6. Processing flow:

1) Check the signaling link status, corresponding MTP boards, or physical connections.

2) Check the office-direction data, MTP data and link connection data to see whether they are correctly configured.

7. Remarks: Poor communication quality of SS7 link, increasingly faulty signaling received, MTP 2 notification of “Out of service ” or physical configuration error, etc. might result in the alarm.


Page 42 of 106

2.3.1.3 SS7 SCCP Alarm


2. Alarm level: 2


4. Effect: The proper operation of SS7 might be disabled.


6. Processing flow: Check whether the office-direction data or the network is correctly configured, focusing on the setting of the signaling point.

7. Remarks: When the SCCP sets the status of SSN, if the office-direction is not available according to DPC, this may cause the occurrence of alarm.


Page 43 of 106

2.3.1.4 BSC CPU Active/Standby Communication Halt


2. Alarm level: 2

3. Alarm cause: Active/standby communication links break off, with cause code: 53.

4. Effect: Communication or handover between active/standby MPs is disabled, reducing the system reliability.


6. Processing flow:

1) Check whether the active/standby MPs work properly. If not, remove the fault.

2) Check whether the share memory board works properly. If not, remove the fault.


7. Remarks: If the standby MP doesn’t work properly, or if the share memory board encounters an error, there will be alarms.


Page 44 of 106

2.3.1.5 BSC Inter-module Communication Failure Alarm


2. Alarm level: 2


4. Effect: A part of modules are disabled.


6. Processing flow:

1) Check the connection lines between modules to see whether they are correctly connected. If not, correct them.

2) Check and see whether the clock alarms. If it does, remove the alarm first.

3) View the communication interface board. If it raises the alarm, remove it first.

4) If it is still not worked out , contact the local office of ZTE.

7. Remarks: None.


Page 45 of 106

2.3.2 LAPD Communication Error

2.3.2.1 The LAPD Link of TRX and BSC Disconnect


2. Alarm level: 3


4. Effect: All services of this TRU cease.


6. Processing flow:

1) View this base station and other FUCs to see whether they raise the alarm. If all the FUCs inside the base station raise this alarm, view the base station BIE to see whether it raises the alarm; see whether the EI line is correctly connected and whether the BIU unit, LAPD board in the BSC system raise the alarm. If these alarms exist, remove these faults first.

2) Check the BSC data to see whether they are correct.

3) Switch off BIPP or COMI.

4) 3. If merely the LAPD at one of the TRU layers is disconnected, check if the cable on the backplane is correctly connected.

5) If nothing but the LAPD in one of the TRMs is disconnected, reset the FUC

6) If problems still remain unresolved, contact the local office of ZTE.

7. Remarks: None.


Page 46 of 106

2.3.2.2 COMM Link Disable Between O&M Unit and LAPD of BSC


2. Alarm level: 2


4. Effect: The normal operation and maintenance of the whole site is affected.


6. Processing flow:

1) View the 2M indicator light of corresponding TIC and see whether the light flashes normally. If the light flashes abnormally, you self loop the BSC system. If the flashing status remains unchanged, it shows that the fault is being transferred or at the BTS side; if the light flashes normally, check the LAPD, TIC or COMI board and see whether they work properly.

2) Check whether the LAPD timeslot of OMU is correctly allocated.

3) Check whether the E1 lines are correctly connected.

4) Check whether the BTS rack is powered on and whether the OMU is properly initiated.

5) Check the BIE of BTS. If it raises the alarm, remove it first.

6) If problems still remain unresolved, contact the local office of ZTE.

7. Remarks: None.


Page 47 of 106

2.3.3 BOARD Communication Alarm

2.3.3.1 Standby Communication Link Inside BSC System Disable


2. Alarm level: 4

3. Alarm cause: The fault found in the transmission or board by which the node HDLC link passes, with cause code: 1.

4. Effect: It won’t affect the routine function of the base station, but it can play the role of mutual backup for active and standby.

5. Processing time limit: Within 24 hours.

6. Processing flow:

1) Check the board by which the HDLC link passes and see whether it works normally.

2) Check all the connection lines (or transmission) by which the HDLC link passes and see whether they are in proper status.


7. Remarks: None.


Page 48 of 106

2.3.3.2 Board Overtime No Notification


2. Alarm level: 3


4. Effect: It will disable the operation and maintenance of this board. If this situation lasts long, it will affect the normal operation of services.


6. Processing flow:

1) Check whether there are still other alarms not removed on this board. If so, remove them first.

2) Reset, plug/unplug the board.

3) Replace the board.

7. Remarks: The disconnection between PP board and MP, power down, hardware fault, clock loss, out of position and so on will also generate alarms.


Page 49 of 106

2.3.4 Other Communication Faults

2.3.4.1 Disconnect between TIC and MPPP


2. Alarm level: 3


4. Effect: Affect the operation and maintenance of TIC and result in the operation abnormality.


6. Processing flow:

1) Check whether the PP board is powered on and see whether it raises the alarm.


3) Reset PP and TIC to view whether the fault still exists.


5) Replace TIC and MPPP boards.

7. Remarks: Possible reasons are disconnection between TIC and MPPP, power down, hardware fault or clock loss.


Page 50 of 106

2.3.4.2 Disconnection between COMI and MPPP


2. Alarm level: 3


4. Effect: Affect the operation and maintenance of COMI and result in the operation abnormality.


6. Processing flow:

1) Check whether the PP board is powered on and see whether it raises the alarm.

2) Check whether the clock raises the alarm, whether the COMI board raises the alarm for clock loss. If so, remove the clock board fault first.

3) Reset PP and COMI to view whether the fault still exists.


5) If the measures listed above still don’t work, replace the COMI board.

7. Remarks: The disconnection between COMI board and BIPP, power down, hardware fault, clock loss, out of position and so on will also generate alarms.


Page 51 of 106

2.3.4.3 Disconnection between DRT/EDRT and MPPP

1. Alarm code: 0x256B（DRT）; 0x259D（EDRT）;

2. Alarm level: 3


4. Effect: The communication between DRT/EDRT and MPPP fails, impacting the operation and maintenance management of DRT/EDRT. If this case goes on, the normal operation of this system will be disabled.


6. Processing flow:

1) Check whether the MPPP board raises the alarm.

2) Check whether the clock raises the alarm, whether the DRT/EDRT board raises the alarm for clock loss. If so, remove the clock board fault first.

3) Reset, plug/unplug the related MPPP and DRT/EDRT; See whether they are faulty.



7. Remarks: The disconnection between DRT/EDRT board and TCPP, power down, hardware fault, clock loss, out of position and so on will also generate alarms.


Page 52 of 106

2.4 BSC (VB Environmental Alarm

Environmental alarms listed in the following are all found in modules.

2.4.1 Equipment Room Environmental Temperature Overhigh Alarm


2. Alarm level: 2


4. Effect: The equipment will work abnormally. If the alarm lasts long, the equipment might be damaged.


6. Processing flow:

1) Check whether there is fire alarm. If there is, remove the fire alarm first.

2) Check if the air conditioner is normal.

3) If it is a false alarm, it might be because the temperature range is not set properly.

4) If the temperature range is set properly, then check whether the temperature/humidity sensor is faulty.

5) If the problem is still unable to be located, contact the local office of ZTE.

7. Remarks: None.


Page 53 of 106

2.4.2 Equipment Room Environmental Temperature Overlow Alarm


2. Alarm level: 2




6. Processing flow:

1) Check if the air conditioner is normal.

2) If it is a false alarm, it might be because the temperature range is not set properly.

3) If the temperature range is set properly, check whether the temperature/humidity sensor is faulty.

4) If the problem location is still unavailable, contact the local office of ZTE.

7. Remarks: None.


Page 54 of 106

2.4.3 Equipment Room Environmental Humidity Overhigh Alarm


2. Alarm level: 2




6. Processing flow:

1) Check if the humid extractor is normal.

2) If it is a false alarm, it might be because the humidity range is not set properly.

3) If the temperature range is set properly, check whether the temperature/humidity sensor is faulty.

4) If the alarm is true and still exists, lower the humidity.


7. Remarks: None.


Page 55 of 106

2.4.4 Equipment Room Environmental Humidity Overlow Alarm


2. Alarm level: 2




6. Processing flow:

1) Check if the humid adding system is normal.

2) If it is a false alarm, it might be because the humidity range is not set properly

3) If the temperature range is set properly, then check whether the temperature/humidity sensor is faulty.

4) If the alarm is true and still exist, raise the humidity.


7. Remarks: None.


Page 56 of 106

2.4.5 Equipment Room Infrared Alarm


2. Alarm level: 1


4. Effect: If the environmental heat objects are located, it shows that human beings, animals or other heat sources have entered the room. If the equipment is not spoiled, it won’t impact the operation.


6. Processing flow:

1) View the operation record. If it is due to the maintenance personnel who forget to close the alarm, it is unnecessary to handle it.

2) If uncommitted personnel have entered the room, check whether the equipment parameters are modified and whether the equipment is affected.


7. Remarks: None.


Page 57 of 106

2.4.6 Equipment Room Smog Alarm

1. Alarm code: 0x204A

2. Alarm level: 1


4. Effect: If the air purity around the BSC equipment is poor, there might flow heavy smog or dust. If the dust is too heavy, it might impact the lifespan of the equipment.


6. Processing flow:

1) Check whether there is smog or fire alarm.

2) If there is no smog, the alarm is possibly caused by the overmuch grain floating in the air. In this case, you take measures to purify the air as much as possible or shield this alarm in line with the equipment room environment.


7. Remarks: None.


Page 58 of 106

2.5 GPRS Communication Fault

2.5.1 FRP Communication Alarm

2.5.1.1 FRP 8M8K Clock Loss


2. Alarm level: 2


4. Effect: The 8M and 8K clock on the FRP board loss results in the abnormality of communication. If FRP fails, partial modules of BSC system will fail to run properly.


6. Processing flow:

1) Check whether the clock unit in the BSC system works properly. If the clock unit alarms, remove the alarm first.

2) Check whether the connection lines at the backplane of BSC become loose.

3) Try to plug and unplug the board once more to see whether the fault can be removed.


7. Remarks: None.


Page 59 of 106

2.5.1.2 FRP 8K Clock Loss


2. Alarm level: 2


4. Effect: The 8M and 8K clock on the FRP board loss results in the abnormality of communication. If FRP fails, partial modules of BSC system will fail to run properly.


6. Processing flow:




4) If the measures listed above still don’t work ,contact the related local office of ZTE.

7. Remarks: None.


Page 60 of 106

2.5.1.3 FRP Board’s HDLC Communication Interrupt


2. Alarm level: 2


4. Effect: Affect the operation and maintenance of this board. If this effect continues, the services’ operation will be spoiled.


6. Processing flow:


2) Reset this board.


7. Remarks: None.


Page 61 of 106

2.5.1.4 NSVC Fault


2. Alarm level: 3

3. Alarm cause:

1) The NSVCI in the received reset data package errs, with cause code: 160.

2) The NSEI in the received reset data package errs, with cause code: 161.

3) No reply at the SGSN side; Cause code:162.

4. Effect: If merely one individual NSVC link disconnects, the data on this faulty link will be shared by other links. If all NSVC links disconnect, the Gb port communication will be disabled.


6. Processing flow:

1) Check the carrier channel on this channel and see whether it works properly.

2) Check whether the SGSN is configured in the same manner as is the NSVC of the BSC system.

3) Reset the FRP board.

7. Remarks: None.


Page 62 of 106

2.5.1.5 Frame Trunk PVC Communication Fault


2. Alarm level: 2

3. Alarm cause: Gb port PVC communication errs; cause code: 163.

4. Effect: PVC acts as the carrier channel of NSVC. The PVC error might lead to failure of one or multiple NSVC links.


6. Processing flow:

1) Check whether the E1 line is correctly connected into the Gb port.

2) Check whether the DLCI of PVC is correctly configured.

7. Remarks: None.


Page 63 of 106

2.5.2 BRP Communication Fault

2.5.2.1 BRP Board’s 8M8K Clock Loss


2. Alarm level: 2


4. Effect: The 8M and 8K clock on the BRP board loss results in the abnormality of communication. If BRP fails, partial modules of the BSC system will fail to run properly.


6. Processing flow:





7. Remarks: None.


Page 64 of 106

2.5.2.2 BRP Board’s 8K Clock Loss


2. Alarm level: 2

3. Alarm cause: Unknown, cause code:

4. Effect: The 8M and 8K clock on the BRP board loss results in the abnormality of communication. If BRP fails, partial modules of BSC system will fail to run properly.


6. Processing flow:





7. Remarks: None.


Page 65 of 106

2.5.2.3 BRP Board’s HDLC Communication Interrupt


2. Alarm level: 3


4. Effect: It will disable the operation and maintenance of this board. If the alarm lasts long, it will affect the normal operation of services.


6. Processing flow:


2) Check whether related cables become loose or abnormal.

3) Reset boards.


7. Remarks: None.


Page 66 of 106

2.5.2.4 UDP Ethernet Communication Interrupt between BRP board and MP

1. Alarm code: 0x710A

2. Alarm level: 3


4. Effect: The data packet communication of this board is disabled. If the alarm lasts long, it will affect the operation of services.


6. Processing flow:


2) Reset boards.

3) Check whether the HMS communicates with the MP properly.

4) Check whether the two Ethernet lines are correctly connected behind MP.


7. Remarks: None.


Page 67 of 106

2.5.3 Other Communication Faults

2.5.3.1 UDP Ethernet Communication Disable between PUC boards


2. Alarm level: 3


4. Effect: Data packets communication between SPCUs is disabled, affecting the system operation.


6. Processing flow:

1) Reset PUC boards.

2) View whether the lines between PUCs are correctly connected.


7. Remarks: None.


Page 68 of 106

2.5.3.2 UDP Ethernet Communication Interrupt between PUC and GDPP


2. Alarm level: 3


4. Effect: Data packets communication both inside GDPP and between SPCUs is disabled, affecting the system operation.


6. Processing flow:

1) Reset PUC boards.

2) Check whether related cables become loose or abnormal.

3) Check whether the backplane is normal.


7. Remarks: None.


Page 69 of 106

2.5.3.3 LAN Error Between SPCUs of HMS Board


2. Alarm level: 2


4. Effect: Communication between SPCUs is disabled, possibly reducing the system reliability.


6. Processing flow:

1) Make sure that at least two SPCUs work properly.


7. Remarks: None.


Page 70 of 106

2.6 BSC（V2）Information Notification

The concept of information notification is described as this: if the system encounters unrepeatable or instantaneous errors, some of which wait for the system self recovery instead of being handled while other faults need maintenance personnel’s intervention by taking some measures. If the system still remains disabled for a long time, contact the local office of ZTE.

Since part of the reasons can’t be located by the system, the notified cause code is 10, unless specifically noted, specific causes can be decided on actual situation.

2.6.1 Reset PP board

1. Notification code: 0x2300

2. Relative components: PP

3. Notified cause and cause code: Unknown, cause code: 10.

4. Solution: None.

5. Remarks: None.

2.6.2 Notification of Times of PCM Slide Code on TIC/SMB


2. Relative components: TIC/SMB


4. Solution: Check lines or self loop to test the code error rate.

5. Remarks: None.

2.6.3 Services Operation Status Notification


2. Relative components: MP


4. Solution: None.


Page 71 of 106

5. Remarks: None.

2.6.4 PP Automatic Loading Failure Notification


2. Relative component: BOARD


4. Solution: None.

5. Remarks: None.

2.6.5 PP Compulsory Loading Failure Notification




4. Solution: None.

4. Remarks: None.

2.6.6 DSP Automatic Loading Failure Notification

1. Notification code: 0x230A



4. Solution: None.

5. Remarks: None.

2.6.7 DSP Compulsory Loading Failure Notification

1. Notification code: 0x230B



4. Solution: None.

5. Remarks: None.


Page 72 of 106

2.6.8 System’s Once Encounter of Error

1. Notification code: 0x230C

2. Relative component: MP


4. Solution: Contact the local office of ZTE Corporation.

5. Remarks: None.

2.6.9 Reset Notification of Certain DSP on DRT

1. Notification code: 0x230D

2. Relative component: DRT/EDRT


4. Solution: None.

5. Remarks: None.

2.6.10 Receive Alarm on Certain PCM of TIC

1. Notification code: 0x230E

2. Relative component: TIC


4. Solution: Check the transmission or opposite-end equipment.

5. Remarks: None.

2.6.11 Receive Frame Architecture Loss of PCM on TIC

1. Notification code: 0x230F，0x2310

2. Relative component: TIC


4. Solution: Check the E1 interface and transmission lines.

5. Remarks: None.

2.6.12 Board Status Change Notification



Page 73 of 106



4. Solution: None.

5. Remarks: None.

2.6.13 Changes of Environmental Parameters (Temperature/Humidity/Voltage)


2. Relative component: MODULE


4. Solution: Check the environment related.

5. Remarks: None.

2.6.14 Elimination of Maximum Alarm Number Upon POWP-on or Changeover




4. Solution: None.

5. Remarks: None.

2.6.15 Active/Standby GPPs Handover Notification


2. Relative component: GPP


4. Solution: None.

5. Remarks: None.

2.6.16 Outdoor BTS Environment Temperature Notification


2. Relative component: SITE


Page 74 of 106


4. Solution: Check the environment of the site.

5. Remarks: None.

2.6.17 Notification of Network Communication Status Changes between MP and PCM




4. Solution: None.

5. Remarks: None.

2.6.18 BCCH Switchover Failure Notification



3. Notified cause and cause code: BCCH switchover fails; cause code: 5.

4. Solution: Check the BCCH carrier frequency and the connection of BCCH carrier frequency.

5. Remarks: None.

2.6.19 Bus Code Error Notification



3. Notified cause and cause code:

1) Odd and even check fails; cause code: 17.

2) Bus error; cause code: 18.

3) External clock ceases; cause code: 19.

4) Internal clock ceases; cause code: 20.


Page 75 of 106

4. Solution: Filter is needed,

5. Remarks: None.

2.6.20 Board Connection Error Notification




4. Solution: Check data configuration or board.

5. Remarks: None.

2.6.21 Flow Control Startup Notification

1. Notification code: 0x231A



4. Solution: None.

5. Remarks: None.

2.6.22 No Traffic in the Cell

1. Notification code:0x231B

2. Relative component: FU

3. Notified cause and cause code: The cell has no traffic; cause code: 10.

4. Solution: None.

5. Remarks: None.

2.6.23 MP and PCOM Board Handshake Failure

1. Notification code: 0x231C

2. Relative component: PCOM

3. Notified cause and cause code: The PCOM board runs improperly; MP errs in handshake with the PCOM board, with cause code: 10.

4. Solution: Check the board status.


Page 76 of 106

5. Remarks: None.

2.6.24 X.25 Protocol Startup on the PCOM

1. Notification code: 0x231D


3. Notified cause and cause code: The X.25 Protocol starts up on the PCOM, with cause code: 10.

4. Solution: None.

5. Remarks: None.

2.6.25 X.25 Protocol Disable on the PCOM

1. Notification code: 0x231E


3. Notified cause and cause code: The X.25 Protocol disables on the PCOM, with cause code: 10.

4. Solution: None.

5. Remarks: None.

2.6.26 PP Board Version Loading Failure

1. Notification code: 0x231F

2. Relative component: BOSN，AIPP，BIPP，TCPP，NSPP，FSPP，DRT，EDRT，DTI，SMB，SMT1，SMT2，PUC，BRP，FRP，GIPP.


1) PP response overtime, with cause code: 220.

2) File no exist; cause code: 221.

3) File length error; cause code: 222.

4) File check error; cause code: 223.

5) Accessing to foreground database fails; cause code: 224.

6) Deletion of file fails; cause code: 225.


Page 77 of 106

7) Background message entity parameter error; cause code: 226.

8) It is not the command of the reset BSC board; cause code: 227.

9) Modifying of file fails; cause code: 228.

10) Active/standby MP communication breaks off, with cause code: 229.

11) Application program check error; cause code: 300.

12) FLASH removal error; cause code: 301.

13) FLASH write error; cause code: 302.

14) FLASH read error; cause code: 303.

15) BOOT check error; cause code: 304.

16) Parameter area check error; cause code: 305.

17) Download data check error; cause code: 306.

18) Data download overtime; cause code:307.

19) Edge error; cause code:308.

20) Version type error; cause code: 309.

21) Version error; cause code: 310.

22) Version too long; cause code: 311.

23) Version length error; cause code: 312.

24) Version request serial number error; cause code: 313.

25)This version does not exist; cause code: 314.

4. Solution: Make adjustment based on cause code.

1) PP response overtime: Check whether the boards run normally.

2) File does not exist: Check whether the background has entry version


Page 78 of 106

and whether the version file exists. Otherwise, you reenter or wait for 2 or 3 minutes before the file is automatically transferred onto the MP

3) File length error: Use the correct version file or reenter the version.

4) File check and error: Use the correct version file or reenter the version.

5) Accessing to the foreground database fails: Check if the version configurations are correct.

6) Application program check error: Check if the version files are correct.

7) Flash removal error: Reload. If it still doesn’t work, replace the board.

8) Flash write error: Reload. If it still doesn’t work, replace the board.

9) Flash read error: Reload. If it still doesn’t work, replace the board.

10) Version type error: Check if the version files are correct.

11) Version error: Check if the version files are correct.

12) Version too long: Check if the version files are correct.

13) Version length error: Check if the version files are correct.

5. Remarks: None.

2.7 GPRS Notify Information

2.7.1 Wrong Links Label

1. Notification code: 0x7A00

2. Relative component: FRP

3. Notified cause and cause code: The NSVC link receives wrong links label; cause code: 164.

4. Solution: First check whether the NSVCI at the BSC side is configured in the same manner as the NSVCI at the SGSN side. If it is all right, check whether the E1 line is wrongly connected.


Page 79 of 106

5. Remarks: None.

2.7.2 Wrong Entities Label



3. Notified cause and cause code: The NSVC link receives a wrong entity label; cause code: 165.

4. Solution: First check whether the NSVCI at the BSC side is configured in the same manner as the NSVCI at the SGSN side. If it is all right, check whether the E1 line is wrongly connected.

5. Remarks: None.

2.7.3 Process Number of Transmitting BSSGP Data Packet



3. Notified cause and cause code: The BRP board route error; cause code: 166.

4. Solution: Make sure that you reset the signaling BVC of this cell provided that the data in the database table is correct a.

5. Remarks: None.

2.7.4 Receive the Status Data Packet of NS Layer Transmitted from the SGSN side




1) Transmission network error; cause code: 170.

2) Background operation and maintenance; cause code: 171.

3) Equipment error, cause code: 172.

4) Link blocked; cause code: 173.


Page 80 of 106

5) Link label VCI error; cause code: 174.

6) Receive faulty BVCI label; cause code: 175.

7) PDU solecism; cause code: 178.

8) Receive the unexpected PDU; cause code: 180.

9) Unknown PDU type; cause code: 181.

10) Illegal message unit; cause code: 182.

11) Loss of important message unit; cause code:183.

4. Solution: Against (A, (B and (C, check whether the corresponding NSVC links are normal. Or manually reset it from the background if necessary. Against (D, you check whether the NSVC status at the board complies with that of the background database. Against (E and (F, you check whether the background configuration is wrong; If it is correct, you can reset manually the corresponding NSVC and BVCI from the background. Against from (G to (1A, clarify the transmitted NS PDU en/decode errors. If the operations mentioned above still don’t work against (A- (F, reset the FRP board or reinitiate P0.

5. Remarks: None.

2.7.5 LAN Error inside SPCU


2. Relative component: PUC


4. Solution: Check whether the network goes wrong or changes over to HMS.

5. Remarks: The active PUC tests it and notifies the fault.


Page 81 of 106

2.8 Running Information Classification

The ZXG10-BSC (VB running information is originated from the panel indicator lights on such modules as MP, COMM. By giving different definitions to the display of indicator lights, the running status of equipment can be located. Please refer to relevant maintenance manuals for the running information of BTS，MB，BS21 and OBTS .

Based on the board types, the running information can be classified into six types as follows: control layer board, network switching layer board, TC unit, GPRSPP board, power supply board, and other boards.

2.9 Running Information of Each Board

In the following, the fast on/out of indicator lights are defined as 5 times per second, namely the interval between “on” and “out” of the indicator lights is 100ms. The slow flash takes place once per second, namely the interval between “on” and “out” of the lights is 500ms.

Unless specially noted, the indicator lights, switches on the panel are orderly arrayed from the top to the bottom, numbered in 1, 2, 3…


Page 82 of 106

2.9.1 Running Information of Control Layer Board

1. Running Information of MP Board

There are 4 indicator lights and 3 switches on the MP board as Table 3-1 shows:

Table 3-1 MP Indicator Light Names and Their Meanings

Position Name Descript

ion Meaning Work mode

1 HL1 Green Run status Slowly flash if the board runs normally

2 HL2 Red Board failure The light remains on in the case of board

error

3 HL3 Green

The board is

in active

status

The light remains on if the board is in active

status.

4 HL4 Green

The board is

in standby

status

The light remains on if the board is in

standby status.

5 SW1 Switch

Unlock

button

switchoff

switch

Press this switch to changeover between

active and standby

6 SW2 Switch

Unlock

button reset

switch

Press this button to trigger the board for

reset.

7 SW3 Switch

Lock-button

power

supply

switch

Press it, power on;

flip it, power down.

Note: There is a key interface and a monitor interface on the MP board applied in the software version debugging.


Page 83 of 106

2. Running information of SMEM Board

There are 2 indicator lights on the SWEM board as Table 3-2 shows:

Table 3-2 SMEM Indicator Light Names and Their Meanings

Position Name Description Meanings Work mode

1 HL1 Green Run status: Flash slowly if the board runs

normally.

2 HL2 Red Board failure The light remains on if the board

errs.

3. COMM (MPPP/MPMP) Board Running Information

There are 2 indicator lights and 1 switch on the COMM（MPPP/MPMP） board as Table 3-3 shows:

Table 3-3 COMM（MPPP/MPMP）Indicator Light Names and Their Meanings


1 HL1 Green Run status:

Flash slowly: Running properly Flash simultaneously with the alarm light:

The board errs, e.g. clock loss.

2 HL2 Red Board

failure

Out: Running

Flash simultaneously with the running

light: The board errs, e.g. clock loss.

3 SW1 Switch

Unlock

button reset

switch


reset.


Page 84 of 106

4. COMM (NO.G Board Running Information

There are 2 indicator lights and 1 switch on the COMM（NO.7） board as Table 3-4 shows:

Table 3-4 COMM（NO.7）Indicator Light Names and Their Meanings


1 HL1 Green Run status: Flash slowly: The SS7 link disconnected. Flash fast: The No.7 link is normal

2 HL2 Red Board failure

Remain on: Running

Flash slowly: The board errs, e.g. clock

loss.

3 SW1 Switch nlock button reset

switch


reset.

5. ECOM (NO.G Board Running Information

There are 2 indicator lights and 1 switch on the ECOM（NO.7） board as Table 3-5 shows:

Table 3-5 ECOM（NO.7）Indicator Light Names and Their Meanings

Positio

n Name Description Meanings Work mode

1 HL1 Green Run

status:

Flash fast: Running Flash slowly: If the red light is on, the SS7 link

disconnects; If the green light flashes

simultaneously with the alarm light, it means that

the ECOM board disconnects from MP.

Remain on: Abnormal

2 HL2 Red Board

failure

Remain on: Running

Flash slowly: If the run light flashes simultaneously

with the alarm light, it means that the ECOM board

disconnects from MP. Other abnormal cases

Remain on: When the light flashes simultaneously

with the run light, it notifies of clock loss and other

abnormal cases

3 SW1 Switch

Unlock

button

reset

switch

Press this button to trigger the board for reset.


Page 85 of 106

6. COMM（LAPD）Board Running Information

There are 2 indicator lights and 1 switch on the COMM (LAPD) board as Table 3-6 shows:

Table 3-6 COMM（LAPD）Indicator Light Names and Their Meanings

Position Name Descriptio

n Meanings Work mode


Flash slowly: Running Flash simultaneously with the alarm light: The board errs, e.g. clock loss. Remain on, remain out: Abnormal


Remain on: Running Flash slowly: This board fails to communicate with MP. Flash slowly and simultaneously with the running light: The board errs, e.g. clock loss.

3 SW1 Switch Unlock

button reset switch


7. ECOM (LAPD/MPPP/MPMP) Board Running Information

There are 2 indicator lights and 1switch on the ECOM（LAPD/MPPP/MPMP） board as Table 3-7 shows:

Table3-7 ECOM（LAPD/MPPP/MPMP）Indicator Light Names and Their Meanings



Flash slowly: Running

Flash simultaneously with the alarm light: The

ECOM board fails to communicate with MP.

Remain on: Abnormal

Remain on together with the alarm light: Clock

loss.

Remain on: Abnormal

HL2 Red Board

failure

Remain on: Normal.

Flash slowly and simultaneously with the

running light: The ECOM board fails to

communicate with MP.

Remain on and simultaneously with the running

light: Clock loss.

3

SW1 Switch Unlock

button reset

switch



Page 86 of 106

8. PEPD (MON) Running Information

There are 2 indicator lights and 1 switch on the PEPD（MON） board as Table 3-8 shows:

Table 3-8 PEPD（MON）Indicator Light Names and Their Meanings

Position Name Descripti

on Meanings Work mode

1 HL1 Green Run status: Flash slowly: Running Flash fast: Sensor warm-up Remain on, remain out: Abnormal

2 HL2 Red Board failure Remain on: Running On: Board failure, e.g. dual-port RAM check error

3 SW1 Switch Unlock button reset switch


9. PCOM Board Running Information

There are 6 indicator lights and 1 switch on the PCOM board as Table 3-9 shows:

Table 3-9 PCOM Indicator Light Names and Their Meanings

Pos Name Des. Meanings Work mode


Flash slowly: Running Flash simultaneously with the alarm light: disconnect from MP. Remain on, remain out: Abnormal


Remain on: Running Flash slowly and simultaneously with the running light: Disconnect from MP. Remain on: Hardware clock loss or other hardware failures

3 HL3 Green Dial-MODEM transmit data

Remain on: PCOM transmits data to dial-MODEM Remain on: PCOM doesn’t transmit data to dial-MODEM

4 HL4 Green Dial-MODEM receive data

Remain on: PCOM receives data from dial-MODEM Remain on: PCOM doesn’t receive data from dial-MODEM

5 HL5 Green Baseband MODEM transmit data

Remain on: PCOM transmits data to baseband-MODEM Remain on: PCOM doesn’t transmit data to baseband-MODEM

6 HL6 Green Baseband MODEM receives data

Remain on: PCOM receives data to baseband-MODEM Remain on: PCOM doesn’t receive data to baseband-MODEM




Page 87 of 106

2.9.2 Board Running Information on Network Switching Layer

1. BOSN Board Running Information

There are 4 indicator lights and 2 switches on the BOSN board as Table 3-10 shows:

Table 3-10 BOSN Indicator Light Names and Their Meanings



Flash slowly: Running Flash fast: Data load synchronization Remain on, remain out: Abnormal


Remain on: Running Flash slowly: This board fails to

communicate with the previous level. If

it is still disabled within a certain

amount of time, reset it.

On: The board errs, e.g. clock loss.

3 HL3 Green The board is in

active status

Remain on: The light remains on if the

board is in active status.


standby status


board is in standby status.

5 SW1 Switch Unlock button

handover switch

Press this switch to changeover

between active and standby


reset switch

Press this button to trigger the board

for reset.


Page 88 of 106

2. DSNI/COMIBoard Running Information

There are 4 indicator lights and 2 switches on the DSNI/COMI board as Table 3-11 shows:

Table 3-11 DSNI/COMI Indicator Light Names and Their Meanings

Position Name Descripti

on Meanings Work mode


Flash slowly: Running Flash fast: This board fails to

communicate with MP. Remain on, remain out: Abnormal


Remain on: Running Flash slowly: This board fails to


the board is still disabled ,reset it.



active status


board is in active status.


standby status


board is in standby status.


handover switch



6 SW2 Switch Unlock button reset

switch


for reset.


Page 89 of 106

3. Running Information of CKI Board

There are 11 indicator lights and 3 switches on the CKI board as Table 3-12 shows:

Table 3-12 DSNI/COMI Indicator Light Names and Their Meanings


1 HL1 Green Run status: Remain on: Running Flash fast: Abnormal communication with SYCK board.


Remain on: Running On: Board failure

3 HL3 Green 8KHz clock reference

On: 8K clock available Out: 8K clock reference unavailable

4 HL4 Green 2MHz clock reference

On: 2M clock reference unavailable Out: 2M clock reference unavailable

5 HL5 Green 5MHz clock reference

On: 2M clock reference unavailable Out: 5M clock reference unavailable

6 HL6 Green 2Mb clock reference

On: 2Mb clock reference unavailable Out: 2Mb clock reference unavailable

7 HL7 Green

8 HL8 Green

9 HL9 Green

10 HL10 Green

Reference selection indication

Using binary system, the four lights show the selected reference from the 16 ones, from top to bottom and from high to low. If the light is on, it is 1; if the light is out, it is 0. 0～3：E8K 0～3； 4～7：2MHz 0～3； 8～11：5MHz 0～3； 12～15：2MBT 0～3

11 HL11 Green Manual indication

On: Indicate that manual selection of clock reference is enabled. Out: Indicate that manual selection of clock reference is disabled.

12 SW1 Switch Manual selection:

Reference selection button; if you press this button continuously, you can orderly select 16 references.

13 SW2 Switch Manual enable

Press this button to enable the CKI to be in manual enable and disable status by turns.




Page 90 of 106

4. SYCK Board Running Information

There are 12 indicator lights and 4 switches on the SYCK board as Table 3-13 shows:

Table 3-13 SYCK Indicator Light Names and Their Meanings

Position Name Description Meanings Work mode 1 HL1 Green Run status: Remain on: Running

2 HL2 Red Board failure Out: Running On: Board failure

3 HL3 Green The board is in active status

On: The board is in active status Out: The board is in standby status

4 HL4 Green The board is in standby status

On: The board is in standby status Out: The board is in active status

5 HL5 Green Fast capture

status On: The board is in fast capture status Out: The board is not in fast capture status

6 HL6 Green Tracing status On: The board is in tracing status Out: The board is not in tracing status

7 HL7 Green Holding status On: The board is in holding status Out: The board is not in holding status

8 HL8 Green Random run

status On: The board runs in random status On: The board runs in none-random status

9 HL9 Green

10 HL10 Green

11 HL11 Green

Select reference

Three indicator lights from (HL9～HL1A form a 3-bit binary coding. HL9 is the highest bit. HL11 is the lowest bit. 1 indicates the light is on while 0 indicate the light is out. Their meanings are specified as below: HL9 ～ HL11 is 000 ： Clock has no reference. HL9～HL11 is: 001～100 are selected clock references of this board. This board has four lines of clock references to be selected. HL9 ～ HL11 is 101: Choose the clock reference sent from CKI


Page 91 of 106

Continued table 3-13


12 HL12 Green Manual enable

On: Indicate that manual selection of clock reference is enabled. Out: Indicate that manual selection of clock reference is disabled.

13 SW1 Switch Unlock button select switch

Press this button to orderly select the clock reference

14 SW2 Switch Unlock button enable switch

Press this switch. Manually select the clock reference to enable indicator light (on or out). The manual selection of this switch becomes valid only when this light is on.


handover switch Press this switch to changeover between active and standby



2.9.3 TC Unit Panel Indicator Information

1. DRT/EDRT Board Run Information

There are 3 indicator lights and 1 switch on the DRT/EDRT board as Table 3-14 shows:

Table 3-14 DRT/EDRT Indicator Light Names and Their Meanings



Flash slowly: Running Flash fast: This board fails to communicate with MP. Remain on, remain out: Abnormal


Out: Running Flash slowly: This board fails to communicate with the previous level. If the board is still disabled, reset it. On: The board errs, e.g. clock loss.

3 HL3 Green Idle status

On: None of the DSPs has speech channels being processed. Out: Speech- channels are in processing status.




Page 92 of 106

2. TIC/DTI Board Running Information

There are 6 indicator lights and 1 switch on the TIC/DTI board as Table 3-15 shows:

Table 3-15 TIC/DTI Indicator Light Names and Their Meanings




Flash slowly: Running Flash fast: This board fails to

communicate with MP. Remain on, remain out: Abnormal


Out: Running

Flash slowly: This board fails to


the board is still disabled ,reset it. On: The board errs, e.g. clock loss.

3 HL3 Green DT1

Flash fast: Running

Remain on: Alarms

Out: E1 interface is not initiated yet.

4 HL4 Green DT2

Flash fast: Running

Remain on: Alarms


5 HL5 Green DT3

Flash fast: Running

Remain on: Alarms


6 HL6 Green DT4

Flash fast: Running

Remain on: Alarms



reset switch


reset.


Page 93 of 106

3. GPP Board Running Information

There are 4 indicator lights and 2 switches on the GPP board as Table 3-16 shows:

Table 3-16 GPP Indicator Light Names and Their Meanings

Position Nam

e Description Meanings Work mode

1 HL1 Green Run status

Flash slowly: Running

Flash fast: If it flashes slowly with the red light, it means HDLC communication ceases, otherwise, it means it is extracting data from the database.

Remain on, remain out: Abnormal


Out: Running

Flash slowly: HDLC communication failure


3 HL3 Green

The board is

in active

status

On: The light remains on if the board is in

active status.

Out: The light remains on if the board is in

standby status.

4 HL4 Green

The board is

in standby

status


standby status.

Out: The light remains on if the board is in

active status.

5 SW1 Switch

Unlock

button

handover

switch


active and standby

6 SW2 Switch

Unlock

button reset

switch


2.9.4


Page 94 of 106

2.9.5 GPRSPP Board Running Information

1. PUC Board Running Information

There are 4 indicator lights and 2 switches on the PUC board as Table 3-17 shows:

Table 3-17 PUC Indicator Light Names and Their Meanings



HL1 flashes slowly, HL2 out Running

HL1 flashes fast, HL2 out Wait for

data synchronization

HL1 and HL2 slowly flash at the same

time: Program loading


Out: Running

Flash fast: This board disconnects with

the previous HDLC.

Remain on: Clock loss


active status

On: The light remains on if the board is

in active status.

Out: The light remains on if the board

is in standby status.


standby status

On: The light remains on if the board is

in standby status.

Out: The light remains on if the board

is in active status.


handover switch




reset switch


for reset.


Page 95 of 106

2. BRP Board Running Information

There are 4 indicator lights and 1 switch on the BRP board as Table 3-18 shows:

Table 3-18 BRP Indicator Light Names and Their Meanings

Pos Name Description Meanings Work mode



HL1 flashes fast, HL2 out Wait for data

synchronization

HL1 and HL2 slowly flashes at the same time:

Program loading


Out: Running

Flash fast: This board disconnects with the

previous HDLC.


3 HL3 Green DSP1 Flash slowly: ESP1 program is in execution

Other statuses: Abnormal

4 HL4 Green DSP2 Flash slowly: ESP2 program is in execution


5 SW1 Switch

Unlock

button reset

switch



Page 96 of 106

3. FRP Board Running Information

There are 4 indicator lights and 1 switch on the FRP board as Table 3-19 shows:

Table 3-19 FRP Indicator Light Names and Their Meanings

Pos. Name Description Meanings Work mode




synchronization

HL1 and HL2 slowly flashes at the same



Out: Running

Flash fast: This board disconnects with the

previous HDLC.


3 HL3 Green DSP1

Flash slowly: ESP1 program is in

execution


4 HL4 Green DSP2

Flash slowly: ESP2 program is in

execution



reset switch


reset.


Page 97 of 106

4. GIPP Board Running Information

There are 4 indicator lights and 2 switches on the GIPP board as Table 3-20 shows:

Table 3-20 GIPP Indicator Light Names and Their Meanings



HL1 flashes slowly, HL2 out: Running


synchronization

HL1 and HL2 slowly flash at the same



Out: Running

Flash fast: This board disconnects with

the previous HDLC.



active status


active status.

Out: The light remains on if the board is

in standby status.


standby status


standby status.

Out: The light remains on if the board is

in active status.


handover switch


active and standby


reset switch


reset.

2.9.6 POWB Board Running Information

1. POWB Board Running Information

There are 2 indicator lights on the POWB board as Table 3-21 shows:


Page 98 of 106

Table 3-21 POWB Indicator Light Names and Their Meanings



1 HL1 Green Run status On: Running Out: Board failure

2 HL2 Red Board failure On: Board failure Out: Running

2. POWP Rack Distributor Running Information

The POWP rack distributor has 4 indicator lights and 1 switch, I antistatic wrist strap, with meanings as Table 3-22 shows:

Table 3-22 POWP Indicator Light Names and Their Meanings


1 HL1 Green Fan power

indicator light

On: Running

2 HL2 Green Power supply

indicator light

On: Running

3 HL3 Red

Power

undervoltage

indication

On: Input undervoltage

Out: Normal input voltage

4 HL4 Red

Power

overvoltage

indication

On: Input overvoltage

Out: Normal input voltage

5 SW1 Switch Power switch Power switch, turn upwards to power

on; turn downwards to power down.

Note: POWP indicator lights and switches are orderly arrayed as 1, 2, 3, …,5.


Page 99 of 106

2.9.7 Other Boards Running Information

1. SMB Board running information

There are 5 indicator lights and 1 switch on the SMB board as Table 3-23

shows:

Table 3-23 SMB Indicator Light Names and Their Meanings


1 HL1 Green Run status Flash slowly: Running Remain on, remain out: Abnormal


Out: Running Flash slowly: This board fails to communicate

with the previous level. If the board is still

disabled, reset it.


3 HL3 Green E1-1

Flash fast: Running

On: E1 alarm

Out: E1 port is not configured yet.

4 HL4 Green E1-2

Flash fast: Running

On: E1 alarm


5 HL5 Green E1-3

Flash fast: Running

On: E1 alarm



reset switch


2. running information of each board during version loading

During the version loading, each board has 2 indicator lights: HL1 and HL2, with meanings shown in Table 3-24.

Table 3-24 Version loading Indicator Lights and Their Meanings

Position Nam

e Description Meanings Work mode


Flash slowly: Ready for loading Flash fast: Loading is in process. Remain on, remain out: Abnormal


Flash fast: Running in BOOT. Merely targeting the boards demanding for version loading, e.g. BOSN, DRT, EDRT, GPP, ECOM, etc.


Page 100 of 106

Appendix A Replacement of Boards and Components A.1 Overview

In daily maintenance operation, replacing faulty boards is a common and also an important maintenance mode. When replacing boards, the maintenance personnel are recommended to contact relevant technical professionals or the local office personnel of ZTE Corporation so as to get technical instructions.

In the process of replacing boards, it is necessary to follow rules as follows:

1. In the usual time, the unopened spare parts should be kept in antistatic packages (Drier bags are preferred inside the bag) classified and saved in cartons. Types and models should be labeled clearly on the antistatic bags or cartons for the convenience of identification.

2. Wear antistatic wrist straps before plugging/unplugging boards. When holding boards in hand, be cautious enough to keep away from circuits, components, connection slots, etc. Never overexert yourself when you plug/unplug boards so as to prevent from distorting boards or the pins and slots on the backplane.

3. The removed faulty boards should be labeled with fault causes before put into the antistatic bags and should be kept in classification.

4. After the faulty boards are removed, if no spare parts are available at the moment, put an idle dam board onto the vacant position in order to keep clear of dust or play an ornate role.

5. Make sure to mount the module into its position.

6. Hot plug/unplug operation is strictly prohibited when replacing power boards or MP.

A.2 Procedures of Replacing Public Boards

1. Preparations before replacement


Page 101 of 106

1) By observing and analyzing errors, locate the faulty boards and replace them.

2) Make sure that spare parts are functionally intact and their models comply with the faulty boards.

3) A sufficient provision of antistatic bags, drier bags and assorted cartons is available for convenience of labeling faulty components.

2. Replacement procedures

1) Wear antistatic wrist straps.

2) When using the standby board to replace the active board, perform the active/standby changeover first so as to enable the standby board to be in active status beforehand.

3) Using one hand to forcefully turn the fastener on the faulty board outwards and downwards; when the board is removed from the insertion slot and flip outwards, you use the other hand to hold the lower edge of the board and then gently pull the board out from its slot. In the process of this operation, you should try your best to avoid contacting the parts and circuits on the board

4) Put the removed faulty boards into the antistatic bags with drier bags and label them clearly according to their models, attributed slots, program versions and words “fault”. Put the faulty boards in the cartons in category and label them clearly on the cover of the cartons so as not to confuse them next time.

5) First aim at the slot labeled on the insertion box in line with the spare board name, then use the thumb to press the fastener on the circuit board and push the circuit into the slot with average force until the fastener locks it up. This shows the circuit board has reached its position.

6) If the active board is to be replaced, perform another active/standby changeover after the replacement is over, thus enabling the new board to run in active status.

3. Confirmation after replacement


Page 102 of 106

When the circuit board is freshly inserted, there will be a self-test process lasting for some time. If the self-test succeeds, the indicator lights will be in normal status; if services operation recovers, it becomes a symbol of replacement success. For more information on how to distinguish the display status of indicator lights, read Chapter 3 in this manual. If the self-test fails in that the self-test proceeds continuously or indicates abnormality and the related unit has not recovered its services, this shows the replacement fails. Check and confirm whether the spare board is damaged or whether the fault is on other boards instead of on this one. Locate the fault by observing the alarm of fore/background.

A.3 Replacement of Other Components

In most cases, the components here refer to the whole layer shelf or the backplane. The office party and the related technical personnel should acknowledge the replacement operation beforehand.

1. Preparations before replacement

Preparations to be made are the same as those before the replacement of public boards. Read A.2 for more details.

2. Procedures of replacing shelves and backplanes

1) Wear wrist straps and turn off power supply system.

2) Write down the specific boards and their corresponding slots and remove all the boards at this layer.

3) Write down the slots and positions where cables are located, remove all the cables connected at the backplane, including the 3×8 cable and the 6-chip POWP cables on both sides.

4) Remove the front door from t he rack and be careful to put it down lightly.

5) Loosen the 4 screws on the shelf of this layer by starting from the front of the shelf. Pull out the shelf out from the front.

6) Remove the backplane of the this layer after unscrewing it.


Page 103 of 106

7) Mount the new backplane onto the idle shelf (or install the backplane onto the new shelf). Make sure not to reverse the top/bottom directions of the backplane.

8) Exactly in the same manner as the removed backplane, install the short circuit chip on the left and right sides of the new backplane. If the 3×8 cable lock chip is unavailable on the 96-core socket of the new backplane, install the cable lock chip onto it in exactly the same manner as is with the old backpane.

9) Mount the shelf with new backplane onto the rack.

10) Put back the front door of the rack.

11) Based on the previous records, connect the power supply lines to the corresponding cables on the backplane. Be careful with the two (left/right) directions of the 3×8 cable. Merely the left or the right of the two directions can be locked if inserted by a lock chip, so does the 6-core power supply cable. Only one of its directions (left and right) can be inserted. If it fails, you try the other direction.

12) Insert each board corresponding to the recorded slots. In the process of this operation, you should try your best to avoid contacting the parts and circuits on the board

13) Be sure the cable connections and board slots are inerrable.

Warning: MP’ s power supply is –48V. Other boards will be burnt if inserted to the MP slot.

14) Power on the rack and initiate the system.

3 Confirmation after replacement

There will be a self-test process lasting for some time before the system powers on after the replacement, MP initiation, board version loading and version running takes place respectively. If the self-test succeeds, the indicator lights will be in normal status. If services’ operation recovers, it symbolizes the replacement success. For more information on how to distinguish the display status of indicator lights, read Chapter 3 in this manual. If the self-test fails in that the self-test proceeds continuously or


Page 104 of 106

indicates abnormality and the related unit has not recovered its services, this shows the replacement fails. Check and confirm whether the spare board is damaged or whether the fault is on other boards instead of on this one. Locate the fault by observing the alarm of the fore/background.


Page 105 of 106

Appendix B Abbreviations Abbreviations Full Names in English

AIPP A Interface Environmental Processor

AIU A Interface Unit

BATC Backplane of A interface and TransCoder

BBIU Backplane of Abis Interface Unit

BCTL Backplane of ConTroL

BIE Base station Interface Equipment

BIPP aBis Interface Environmental Processor

BIU aBis Interface Unit

BNET Backplane of NET

BOSN Bit-Oriented Switching Network

BRP BSSGP RLC/MAC Protocol processor

BSC Base Station Controller

BSMU Backplane of SubMultiplexing Unit

BSS Base Station Subsystem

BTS Base Transceiver Station

CKI ClocK Interface board

COMI COMmunication Interface board

COMM COMMunication board

DRT Dual-Rate Transcoder

DSNI Digital Switch Network Interface

DSP Digital Signal Processor

DTI Digital Trunk Interface

EDRT Enhanced DRT

EGSM Enhanced Global System for Mobile

communication

FRP Frame Relay Protocol Processor

FSMU Far SubMultiplexing Unit

FSPP Far Submultiplexing Environmental Processor

GIPP Gb Interface Environmental Processor

GPP General Environmental Processor

GPRS General Packet Radio Service

GSM Global System for Mobile communication

HW HighWay

LAPD Link Access Protocol on the D channel

LED Low Emitting Diode

LMT Local Maintain Terminal

MON MONitor board

Table Continued


Page 106 of 106

Abbreviations Full Name in English

MPMP MP To MP

MPPP MP To PP

MS Mobile Station

MSC Mobile Switching Center

MSS Mobile Switch System

MTP Message Transfer Protocol

NSMU Near SubMultiplexing Unit

NSPP Near Submultiplexing Environmental Processor

NSU Net Switching Unit

PCB Printed Circuit Board

PCM Pulse Code Modulation

PCU Packet Control Unit

PDCH Packet Data CHannel

PEPD Environmental Environment &Power Detecting board

POWB POWer B

POWP POWer P

PUC Packet Unit Controller

PSTN Public Switching Telephone Network

RMU Radio Manage Unit

RXLE Rx Level

RXQUA Rx QUAlity

SCCP Signaling Connection Control Part

SCM System Control Module

SCU System Control Unit

SM SubMultiplexing

SMB Subrate Multiplexing to Bts

SMEM Share MEMory

SMPP Subchannel Multiplexing Environmental Processor

SMU Subchannel Multiplexing Unit

SUBPP SUB Environmental Processor

SYCK SYnchronous ClocK board

TC Trans Coder

TCP Transfer Control Protocol

TCPP TransCoder unit Environmental Processor

TCU TransCoder Unit

TIC Trunk Interface Circuit

ZXG10-BSC(V2) Maintenance Manual

Documents

Transcript of ZXG10-BSC(V2) Maintenance Manual