ZXSDR Bts Alarm Handling 1 Training Manual 201010 PDF

ZXSDR BTS
Alarm Handling
ZTE UNIVERSITY
ZTE University, Dameisha
YanTian District, Shenzhen,
P. R. China
518083
Tel: (86) 755 26778800
Fax: (86) 755 26778999
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2006 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or distribution of
this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPO-
RATION is prohibited. Additionally, the contents of this document are protected by contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE CORPORATION
or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions are dis-
claimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose, title or non-in-
fringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the use of or reliance on the
information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications covering the subject
matter of this document. Except as expressly provided in any written license between ZTE CORPORATION and its licensee,
the user of this document shall not acquire any license to the subject matter herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Publishing Date (MONTH/DATE/YEAR) : 20091111

SDR BTS Structure and Principle .................................. 1
1 Overview ................................................................... 2
1.1 Overview of Fault Management................................................ 2
1.2 Alarm Management Interface .................................................. 2
1.3 Alarm Representation............................................................. 4
1.3.1 Alarm .......................................................................... 4
1.3.2 Notification................................................................... 4
1.4 Alarm Structure..................................................................... 4
1.5 Notification Structure ............................................................. 6
2 Baseband Unit Alarm ................................................. 7
2.1 CC Alarm.............................................................................. 7
2.1.1 198084024 E1/T1 remote receiving fault .......................... 7
2.1.2 198084020 E1/T1 Link Loss of Frame Alarm ..................... 8
2.1.3 198084034 PPP Link Broken ........................................... 9
2.1.4 198084035 PPP Links are All Unavailable .........................10
2.1.5 198084019 E1/T1 LOS (Loss Of Signal) Alarm..................11
2.1.6 198084021 E1/T1 Loss of Cell Delineation Alarm ..............12
2.1.7 198084025 E1/T1 Link Self-loop.....................................13
2.1.8 198084250 IQ Config Failed...........................................13
2.1.9 198084030 SCTP Association is Interrupted .....................14
2.1.10 198084004 Clock Reference Source is Lost ....................15
2.1.11 198084006 Clock Reference Source is Degraded .............17
2.1.12 198084109 SNTP Time Adjustment Failure Alarm............18
2.1.13 198084271 Ethernet Light and Electricity Lose................19
2.2 UBPG Alarm.........................................................................19
2.2.1 198084325 Antenna Data Link Error Alarm ......................19
2.3 FS Alarm .............................................................................20
2.3.1 198084013 Loss of Signal at Ir interface .........................20
2.4 PM Alarm ............................................................................21
2.4.1 198084284 Under-voltage of External Power Supply .........21
2.5 SA Alarm.............................................................................22
2.5.1 198084068 Environmental Temperature is High ................22
2.5.2 198084070 Device Temperature is High...........................23
2.6 Common Board Alarm ...........................................................23
2.6.1 198084117 Application Software Monitoring Alarm............23
2.6.2 198084123 Board Communication Link is
Interrupted.....................................................................................24
2.6.3 198084129 Board Reboots.............................................25
3 Radio Unit Alarm ..................................................... 27
3.1 198084123 Board communication link is interrupted .................27
3.2 198084117 Application software monitoring alarm ....................28
3.3 198084056 Downlink digital IF pre-distortion alarm ..................29
3.4 198084119 Board configuration parameter error.......................29
3.5 198084094 Remote antenna VSWR alarm ................................30
3.6 198084093 Remote antenna over VSWR alarm .........................31
3.7 198084297 The configured operating frequency is out of
range.............................................................................................31
3.8 198084282 Lost of frame number at optical port.......................32
3.9 198084296 60ms tag lost alarm .............................................33
3.10 198084235 Ir signal of port 0 lost .........................................33
3.11 198084295 DL IQ channel checking block alarm .....................34
3.12 198084283 Lost of frame rate and frame number....................35
SDR BTS Structure and
Principle
After you have completed this course, you
will be able to:

>> Learn the SDR alarm information archi-
tecture
>> Learn the alarms about baseband unit
>> Lerarn the alarms about radio unit
Confidential and Proprietary Information of ZTE CORPORATION 1

ZXSDR BTS Alarm Handling
Chapter 1 Overview
After you have completed this chapter, you will know:
>> Overview of Fault Management
>> Alarm Management Interface
>> Alarm Representation
>> Alarm Structure
>> Notification Structure
1.1 Overview of Fault Management
1.2 Alarm Management Interface

The interface of alarm management parameter is shown in Figure
1.
FIGURE 1 ALARM MANAGEMENT INTERFACE
1. Main Menu 4. Alarm Message View

2. Toolbar 5. Hint Message Bar
3. Resource view, management view 6. Status Bar
Main Menu Table 1 shows the description of main menu functions.
2 Confidential and Proprietary Information of ZTE CORPORATION

Chapter 1 Overview
TABLE 1 DESCRIPTION OF MAIN MENU FUNCTIONS
Menu item Function
System Set the property of system func-

tion
View Access to the initial interface menu

in different system modules.
Alarm Inspection View current alarm, history alarm,

and notification messages; view
the alarm monitoring; the function
of alarm synchronization.
Alarm Setting Alarm processing rule, alarm box,

alarm jitter rule, and NE filtering
rule.
Help System help information
Toolbar Table 2 shows the description of shortcut button about alarm man-
agement toolbar.
TABLE 2 DESCRIPTION OF SHORTCUT BUTTON ABOUT ALARM MANAGEMENT

TOOLBAR
Meaning Description
Lock Screen To lock the screen
Logout Logout current user
Query current Based on user demands, query current alarm

alarms. information according to specific conditions.
Alarm History Query Based on user demands, query history alarm

information according to specific conditions.
Notification Query Based on user demands, query the notification

message according to specific conditions.
Help Topics Provide the help information for users.
Resource View Resource view and management view are similar to the tree struc-
and Management ture of Windows system.
View
Resource view is an organization shape to indicate the NE by using
a tree. The different functional objects in the NE corresponds to
different tree nodes. The objects represented in adjacent nodes
in the tree have the upper/lower or parallel relationship. Resource
view shows the interactive relation between the objects for man-
aged elements physically.
Management view is an organization shape to represent the func-
tions of alarm management by using a tree. The different nodes in
the tree represents the different function objects for alarm man-
agement. The view clearly shows the functions about alarm man-
agement. Through management view, the user can easily view
and configure the alarms.

Alarm Message Alarm message view is the main window of alarm management
View client interface. Based on different operations, it can display varied
alarm messages.
Hint Message Bar It shows the information of administrator operation.
Status Bar It shows the information about current login users and servers.
1.3 Alarm Representation

The alarm type is divided into alarm and notification message.
1.3.1 Alarm
Alarm is the prompt message about some faults that occur contin-
uously and impact the proper service and system reliability. Usu-
ally, the alarm messages last some time and will not disappear
until all the problems or faults have been removed.
This kind of fault may impact the normal system operation. Once
it occurs, the user shall timely find the reason and solve it.
1.3.2 Notification
Notification refers to unrepeated or transient fault or event oc-

curred during system operation. For instance, board reset and
signaling overload.
The fault is caused by severe environment, so the special handling
is not required, waiting for system recovery. The user only need
find the reason and solve it if a notification frequently occurs.
1.4 Alarm Structure

Alarm Property 1. Alarm Code
It is the identifier to distinguish the alarms.
The alarm code is defined by 32 bits field, indicating the value
of specific alarm code.
2. Description
It reflects the fault reason and symptom.
3. Severity
Alarm can be divided into four levels based on severity.
� Critical. Critical alarm causes system breakdown and ser-
vice interruption. It requires immediate troubleshooting.

Chapter 1 Overview
� Major. Major alarm significantly affects system operation

or weakens network service capability. It requires trou-
bleshooting as soon as possible.
� Minor. Minor alarm affects system operation and network
service capability in a insignificant way. It requires timely
troubleshooting so as to avoid severity escalation.
� Warning. Warning poses a potential hazard to system op-
eration and network service capability. It requires trou-
bleshooting at an appropriate time so as to avoid severity
escalation.
The degree of impact as described in the definition of alarm
severity refers to the impact of a single index, such as reliability
and security. Once the impact on any of the index reaches
the specified threshold, the severity level of the alarm can be
roughly determined. If an alarm has an impact on multiple
indices, alarm severity should be escalated accordingly.
Note:
The alarm level can be modified in NetNumen M31 if necessary.
In general, the default value of alarm level is a reasonable
value. The user shall be careful and do not modify it randomly.
In addition, the severity of a few alarms is undetermined. It is

up to users to define the severity of such alarms.
4. Alarm Type
Alarm is classified into six types according to alarm trigger con-
dition and its system impact:
� Equipment alarm: related with device hardware.
� Communication alarm: related with information transmis-
sion (ITU-T Recommendation X.733).
� Processing alarm: related with software or process fault
(ITU-T Recommendation X.733).
� Environment alarm: related with the environment where
the equipment is located (ITU-T Recommendation X.733).
� QoS alarm: related with degradation of service quality
(ITU-T Recommendation X.733).
� NetNumen alarm: related with the NetNumen M31.
Probable Cause It lists all probable causes. Probable alarm causes are enumerated
to help users troubleshoot, find preventive measures, and restore
the system to normal state in a timely manner.
System Impact System impact refers to the impact that the alarm incurs on sys-
tem or services.
Handling Troubleshooting measures and suggestions are provided.
Suggestion
Pay attention to the following tips when handling alarms.
� After operation & maintenance staff records the fault and
symptom, they shall handle it in order according to the meth-
ods described in this manual. If no other special description

and the fault disappears, the alarm handling terminates. If

the fault still remains, go to the next step.
� If the fault cannot be removed, contact the local ZTE office as
soon as possible.
1.5 Notification Structure

Notification 1. Notification Code
Property
It is the identifier to distinguish the notifications.
The notification code is defined by 32 bits field, indicating the
value of specific notification code.
2. Notification Name
It reflects the event or fault reason and symptom.
3. Notification Rank
It consists of ordinary and important grades according to its
importance.
4. Notification Type
There is no notification type.
Probable Cause It lists all probable causes. The purpose to give out the reason is
to learn the trigger condition of the notification, to get the trou-
bleshooting methods and precautions, so the system can restore
as soon as possible.
System Impact It lists the influences and effects for the system or service by the
notification.
Handling It provides the useful actions and suggestions for troubleshooting.
Suggestion
In practice, you shall note the following points that will not be
explained more in this manual.
� After operation & maintenance staff records the fault and
symptom, they shall handle it in order according to the meth-
ods described in this manual. If no other special description
and the fault disappears, the notification handling terminates.
If the fault still remains, go to the next step.
� If the system can not restore or the fault can not be solved for
a long time, contact local ZTE office.

Chapter 2 Baseband Unit Alarm
>> CC Alarm
>> UBPG Alarm
>> FS Alarm
>> PM Alarm
>> SA Alarm
>> Common Board Alarm
2.1 CC Alarm
2.1.1 198084024 E1/T1 remote
receiving fault
Alarm Property � Alarm Code: 198084024

� Description: E1/T1 remote receiving fault
� Severity: Minor
� Alarm Type: Communication alarm
Probable Cause 1. The E1/T1 transmission link is improper (higher probability).
2. The PPP related configuration is wrong at BTS or BSC side
(higher probability).
3. The local or remote PPP software module is exceptional (lower
probability).
4. The local or remote PPP device fails (lowest probability).
System Impact 1. E1 can not receive and transmit properly.
2. For PPP mode, it may interrupt the service carried by this E1/T1
link, that is, the service on whole site interrupted.
3. For ML-PPP mode, if there is proper E1/T1 link for same group,
the service interruption is impossible, but it may reduce the
bandwidth.
4. It may impact the clock extracted on E1 line, along with the
alarm of reference source degraded or lost.
Handling 1. Check E1/T1 connection at BBU side, keeping proper connec-
Suggestion tion, tight connector, intact pins and cables.
i. Check whether the SA board is inserted properly.
ii. Check whether the E1 connector is ok.

iii. Check whether the connector pins are intact. If any prob-
lem, replace the connector.
iv. Check whether the E1 transmission cable is compliant with
engineering specification and no any external force. If it
is incompliant or any external force, you shall change the
connection.
2. Check the mode and impedance jumpers on SA/SE board (cor-
responding to three modes and jumper methods: E1 75 ohms,
E1 120 ohms, and T1). For twisted pairs, the negative end can
not be grounded.
3. Check whether the configuration of E1 and T1 modes at two
ends is consistent.
4. Check whether the frame structure is matched and the two
ends of the cable shall be working in bi-frame or multi-frame
mode. Check whether two ends are consistent and keep the
two ends matched.
5. Do self-loop for this E1/T1 link. If the alarm still remains af-
ter self-loop, it indicates it is the hardware fault at BBU side,
gradually replace E1/T1 cable, SA board, and CC board till the
alarm disappears. If the alarm appears after self-loop, check
remote E1 cable.
2.1.2 198084020 E1/T1 Link Loss of

Frame Alarm

� Description: E1/T1 Link Loss of Frame Alarm
� Severity: Critical
probability).
System Impact 1. The impact to the clock: 2Mbis clock is lost if the alarm occurs
with the 8th E1; the line clock is lost if the alarm occurs to all
E1s.
2. For the Iub/Abis: if E1 can not receive or transmit, then pe-
riodical slide code might occur at Iub/Abis and loss of packet
may occur for the service.
3. The impact to the inter-site handover: the accuracy of the BTS
clock might degenerate and fail to meet the 3GPP requirement,
along with the alarm of reference degraded or lost, and reduces
the success rate of the handover.


connection.
not be grounded.
ends is consistent.
two ends matched.
remote E1 cable.
2.1.3 198084034 PPP Link Broken

� Description: PPP Link Broken
� Alarm Type: Equipment Alarm
probability).
System Impact All services carried by this PPP link are unavailable.


connection.
not be grounded.
ends is consistent.
two ends matched.
remote E1 cable.
2.1.4 198084035 PPP Links are All

Unavailable

� Description: PPP Links are All Unavailable
probability).
System Impact All services carried by this PPP link are unavailable.
connection.
not be grounded.


ends is consistent.
two ends matched.
remote E1 cable.
2.1.5 198084019 E1/T1 LOS (Loss Of

Signal) Alarm

� Description: E1/T1 LOS (Loss Of Signal) Alarm
probability).
System Impact The available physical bandwidth is reduced, and it has no influ-
ence on the service. If the Telecom signal for all links are lost, it
may cause all bearing services interrupted.
connection.
not be grounded.
ends is consistent.

two ends matched.
remote E1 cable.
2.1.6 198084021 E1/T1 Loss of Cell

Delineation Alarm

� Description: E1/T1 Loss of Cell Delineation Alarm
probability).
2. For PPP mode, it may interrupt the service carried by this E1/T1
link, that is, the service on whole site interrupted.
bandwidth.
connection.
not be grounded.
ends is consistent.

two ends matched.
remote E1 cable.
2.1.7 198084025 E1/T1 Link Self-loop

� Description: E1/T1 Link Self-loop
� Severity: Minor
Probable Cause 1. E1/T1 link self-loop exists.
2. Set self-loop at near end or remote end for E1/T1 link.
2. For PPP mode, it may cause the site service interrupted.
bandwidth.
Handling Check if hardware or software self-loop is set at different nodes,
Suggestion such as power distribution frame and transmission equipment for
E1/T1 connection. If yes, cancel the self-loop.
2.1.8 198084250 IQ Config Failed

� Description: IQ Config Failed
� Severity: Major
� Alarm Type: Processing Alarm
Probable Cause 1. The number of UBPG board is insufficient or the board is faulty.
2. The optical link is faulty.
3. RRU is not started or RRU can not start.
4. The configuration is wrong.
System Impact The unsuccessful carrier is unavailable.
Handling 1. Check if baseband resource are sufficient. If insufficient, check
Suggestion if UBPG configuration is proper.
2. Check if the connection between BBU and RRU is correct.
3. Check if the LOS alarm exists at optical interface for FS and
RRU. If yes, replace the fiber or optical module, or handle the
alarm according to relevant handling suggestion.

Relevant Alarms:
� 198084013 Loss of Signal at Ir interface
� 198084235 Ir signal of port 0 lost
� 198084271 Ethernet light and electricity lose
4. Check if RRU is improperly running and there are board restart
alarm and application monitoring alarm. If yes, handle the
alarm according to relevant handling suggestion.
Relevant Alarms:
� 198084129 Board reboots
� 198084117 Application software monitoring alarm
5. Check if the configured board is not in correct location. If yes,
modify the configuration.
6. Reset CC board.
2.1.9 198084030 SCTP Association is

Interrupted

� Description: SCTP Association is Interrupted
Probable Cause 1. Local transmission configuration is wrong.
2. Bottom layer can not communicate with peer side.
3. CC board is faulty.
4. The configured port number conflicts.
System Impact It may cause signaling received/transmitted improperly, leading to
the service carried by this SCTP interrupted.
Handling 1. 1. Check the Fault Management window for the correspond-
Suggestion ing alarms. Perform the recommended solution to process the
alarm, if any.
Relevant Alarms:
� 198084019 E1/T1 LOS (Loss Of Signal) Alarm
� 198084020 E1/T1 Link Loss of Frame Alarm
� 198084021 E1/T1 Loss of Cell Delineation Alarm
� 198084024 E1/T1 remote receiving fault
� 198084271 Ethernet Light and Electricity Lose
2. Check the state of indicators on CC board. For FE connection,
check the state of ETH0 (ABIS) indicator. If normal off, check
the network connection. For E1/T1 connection, there is no
proper flashing indication for this alarm.
3. In configuration management interface, check local address,
local port, remote address, remote port for SCTP configured at

B8200 side, which shall be consistent with that configured at

BSC side. For FE mode, check FE, global port, IP, and SCTP.
For E1 and T1 modes, check E1/T1, HDLC, PPP, global port, IP,
and SCTP.
4. Configure SCTP again.
i. Delete this faulty SCTP on the configuration interface.
ii. Add SCTPs on the configuration interface. Relevant config-
uration shall be consistent with that at remote side.
5. Reset CC board.
6. Replace CC board.
2.1.10 198084004 Clock Reference

Source is Lost

� Description: Clock Reference Source is Lost
� Severity: Minor
Probable Cause 1. The configured clock reference source does not exist.
2. External reference clock fails.
4. Cable connection fails.
System Impact 1. Case 1: When multiple clock references are configured, select
the available clock reference per priority sequence, and the
system will operate normally.
2. Case 2: when all the clock references configured are lost, the
system clock will choose to remain or return to free-run mode
and the impact to the system is as below:
i. For the Iub/Abis: if E1 is used by Iub/Abis, then periodical
slide code might occur at Iub/Abis. When FE connection is
used at Iub, then there is no system impact.
ii. The impact to soft handover between Node B/BTS: over a
long period of the alarm, the accuracy of the Node B/BTS
clock might degenerate and fail to meet the 3GPP require-
ment and reduces the success rate of handover.
iii. For synchronizing the GPS frame number in whole network,
GPS clock source lost may impact the synchronization of
frame number, reduce the frequency utilization, and lead
to the KPI dropping (RQ/handover/call completion rate).
Handling 1. In alarm management interface, view the alarm details. The
Suggestion detailed information of the alarm presents the detailed infor-
mation of lost clock reference source.
2. Check if an unavailable reference source is configured (such as
a GPS configuration whereas no actual GPC source is available
in the system.) If yes, open the clock priority configuration in

the configuration management interface, modify the setting of

clock reference source to the actual system condition.
3. Check if the external clock reference is correct.
i. When the clock reference is a line clock:
When active/standby main control board is used, reset the
local board if no alarm occurs to the corresponding board;
check the E1 interface for any physical connection failure if
a same alarm occurs to the corresponding board, such as
the secure connection of each connector, the open-circuitry
in the cables. Use loopback method to test the connec-
tion by directly connecting the RX end to the TX end. If a
198084025 E1/T1 link self-loop alarm occurs on the alarm
monitor interface of the network management application,
it means the link is physically connected, otherwise means
a physical connection failure.
ii. When the clock reference is a GPS clock:
a) CC0 board supports GPS, and CC2 board does not sup-
port GPS. Check whether CC board supports GPS.
b) When active/standby main control board is used, re-
place the GPS card if no alarm occurs to the correspond-
ing board; check the power divider and the cables for
any physical connection failure if a same alarm occurs
to the corresponding board, such as the connector be-
tween the GPS antenna and the GPS feeder, the con-
nector between the GPS jumper and the GPS feeder. If
a lightning arrestor exists, check for any damage to it,
and check the proper and secure connection between
the SMA connector of GPS jumper and the REF inter-
face on the main control board.
iii. When the clock reference is a BITS-2MHz clock:
a) CC2 board supports BITS 2MHz, and CC0 does not sup-
port BITS 2MHz. Check whether CC board supports
BITS 2MHz.
b) When active/standby main control board is used, reset
the main control board if no alarm occurs to the cor-
responding board; if a same alarm occurs to the cor-
responding board, check the BITS-2MHz clock connec-
tion interface for any physical connection failure, such
as the secure connection of each connector, the proper
and secure connection between the SMA connector of
GPS jumper and the REF interface on the main control
board, and the operation status of the BITS-2MHz clock
source and its output to the board.
iv. When the clock reference is a BITS-2Mbit clock:
When active/standby main control board is used, reset the
main control board if no alarm occurs to the corresponding
board; if a same alarm occurs to the corresponding board,
check the BITS-2Mbps clock connection interface for any
physical connection failure, such as the secure connection
of each connector, the cable, and the operation status of the
BITS-2MHz clock source and its output to the board. Use
loopback method to test the connection by directly con-
necting the RX end to the TX end. Please refer to the case

of line clock as BITS-2Mbps clock uses the 8th channel of

E1 channel.
2.1.11 198084006 Clock Reference

Source is Degraded

� Description: Clock Reference Source is Degraded
� Severity: Minor
Probable Cause 1. The quality of transmission clock is poor.
3. Cable connection fails.
System Impact The system clock is under free oscillating mode. It causes the
following service impact.
1. For the Iub/Abis: if E1 is used by Iub/Abis, then periodical slide
code might occur at Iub/Abis. When FE connection is used at
Iub, then there is no system impact.
2. The impact to soft handover between Node B/BTS: over a long
period of the alarm, the accuracy of the Node B/BTS clock
might degenerate and fail to meet the 3GPP requirement and
reduces the success rate of handover.
Handling In alarm management interface, view the alarm details. The de-
Suggestion tailed information of the alarm presents the detailed information
of Clock reference source degeneration.
1. In the case of degeneration of the GPS clock integrated or ex-
ternally connected.
i. Check the GPS feeder and the GPS card. Check the con-
nector between the GPS antenna and the GPS feeder, the
connector between the GPS jumper and the GPS feeder. If
a lightning arrestor exists, check for any damage to it, and
check the proper and secure connection or the feeder for
possible damage. SMA connectors of GPS jumper are prop-
erly and securely connected to the REF interface on the CC
board.
ii. If alarms occur to both the active board and the standby
board, check the lightning arrestor and the GPS antenna.
If the connection and feeder are both proper, replace the
lightning arrestor and/or the GPS antenna.
iii. Reinstall the GPS card and the antenna feeder.
2. In the case of degeneration of the cascaded GPS clock:
i. Check if the high level device has lock the clock. Check
whether the status of clock reference output device is under
the clock locking status.
ii. Reinstall the cable.
3. In the case of degeneration of the BITS-2MHz clock:

i. Check if the external clock reference is correct.

ii. Reinstall the cable.
4. In the case of degeneration of the BITS-2MBps clock:
i. Check whether the clock reference is ok. Check whether
the status of clock reference output device is under the
clock locking status.
ii. Check whether the transmission device is ok.
iii. Reinstall the cable.
5. In the case of degeneration of the line clock on local board:
i. Check if the external clock reference is correct. Check
whether the status of external clock reference output de-
vice is under the clock locking status.
ii. Check if the synchronization networks is normal. Check if
the external transmission equipment is properly wired and
configured.
iv. Contact transmission engineer to check for possible failure
with the external transmission equipment.
6. In the case of degeneration of the line clock on other board or
the IEEE1588 clock:
i. Check if the external clock reference is correct. Check
whether the status of clock reference output device is un-
der the clock locking status.
ii. Check if the synchronization networks is normal. Check if
the wiring and configuration for transmission device is ok.
iv. Contact transmission engineer to check for possible failure
with the external transmission equipment.
2.1.12 198084109 SNTP Time

Adjustment Failure Alarm

� Description: SNTP Time Adjustment Failure Alarm
� Severity: Minor
Probable Cause 1. SNTP sever is disabled.
2. The link is faulty.
System Impact System time is incorrect. It does not impact the specific service.
Handling 1. Check and correct SNTP Server address.
Suggestion
2. Check and correct the link between SNTP server and site.
3. Check whether SNTP Service is started properly.

4. Check whether Windows Time service is disabled.

5. Check the firewall does not exclude the UDP 123 port. If no,
exclude UDP 123 port.
6. Forcedly adjust the time on LMT/OMCB.
2.1.13 198084271 Ethernet Light and

Electricity Lose

� Description: Ethernet Light and Electricity Lose
Probable Cause 1. The network cable is failed.
2. Remote network interface is failed.
3. Local network interface is failed.
System Impact Data Rx/Tx is interrupted at network interface, and the service is
interrupted.
Handling 1. Check the fault of network cable.
Suggestion
i. Check local and remote network cable, and guarantee the
network cable inserted tightly.
ii. Replace the network cable. If GE Ethernet port is config-
ured, use GE network cable.
2. Check the fault at remote network interface.
Use a good network cable to directly connect remote network
interface and another network interface. Check the both net-
work connection. If the network connection is ok, it is caused
by local network interface. If both network connection are dis-
connected, handle the fault at remote network interface, and
re-connect the site after proper operation.
3. Check the fault at local network interface.
Reset the board.
2.2 UBPG Alarm

2.2.1 198084325 Antenna Data Link
Error Alarm

� Description: Antenna Data Link Error Alarm
� Severity: Major


Probable Cause 1. Uplink is improper.
2. Downlink is improper.
System Impact The proper IQ channel is blocked due to uplink error, carried ser-
vice is interrupted, and downlink error leads to the carrier on whole
board unavailable. For warning, it has no influence on uplink and
downlink services.
Handling 1. Check the optical fiber at FS side. If it can not be judged
Suggestion whether the fiber is in good condition according to its appear-
ance, then replace the fiber.
2. Replace the optical module at FS side.
3. Check the fiber and optical module for proper RF unit.
4. Check the optical fiber at RF unit. If it can not be judged
whether the fiber is in good condition according to its appear-
ance, then replace the fiber.
5. Replace the optical module at RF unit.
� If FS board and RF unit restart properly, but the alarm per-
sists after replacing the fiber and optical module, it may be
caused by RF unit, and do troubleshooting for the fauty RF
unit.
� If the RF unit is proper, it may be caused by FS board, so
do troubleshooting by FS board fault.
2.3 FS Alarm
2.3.1 198084013 Loss of Signal at Ir
interface

� Description: Loss of Signal at Ir interface
Probable Cause 1. The physical link between FS and RRU is broken.
2. The optical module is damaged or of bad contact.
3. The LMT configuration is incorrect.
System Impact The board on which the fault occurs works normally, but the board
connected by the optical port becomes faulty.
The "Loss of Signal at Ir interface" alarm is reported for the FS
board temporarily during the RRU resetting process. It is a con-
comitant alarm. Services that the system bear will be interrupted
during the resetting process.
When the alarm occurs on the FS functional board, all services
carried at this optic interface will be interrupted.

When the alarm occurs on RTR, the service that the lower-level
RRU bears will be interrupted.
Handling 1. In the Fault Management interface, check whether RRU has
Suggestion alarms related to resetting. If it has, then handle the alarm
according to relevant alarm's handling suggestion.
Relevant alarm: 198084129 Board reboots
2. In LMT, check whether the RRU is configured in the topology
structure. If the RRU is not configured, then configure the
RRU. (The optical port is configured in the toplogy structure
but is not connected actually, which causes this alarm. Solution
1: Delete this optical port from the configuration. Solution 2:
Connect the RRU with the optical port.
3. Check whether RRU is powered on.
4. Perform changeover for the transceiving fiber at the optical port
on BBU's FS interface board. If the fault is eliminated, then it
indicates that the fiber is connected reversely. If the system
adopts anti-reverse fiber, then it is impossible that the fiber is
connected reversely, and this step can be omitted.
5. Use a spare fiber to connect Tx and Rx at the optical port of FS
to perform fiber loopback. If the alarm is not removed, then
it indicates that the optical module at FS is faulty. Replace the
optical module.
6. Make sure that the fiber at RRU is connected to optical port 1
at RRU, not optical port2 at RRU. Optical port 2 of RRU does
not support connection to BBU. The optical port description is
based on the equipment ID.
7. Make sure that the RRU's fiber is of good contact with the op-
tical module. If the outdoor fiber is of bad contact, it might
be due to the following two causes: the screw is not fastened;
the port does not support blind-mating. It is necessary to align
the fiber before insert it.
8. Use the spare fiber on the faulty RRU. If the fault is eliminated,
then it indicates that the fault is due to the damaged fiber.
9. Replace the RRU's optical module. If the fault is eliminated,
then it indicates that the fault is due to the damaged optical
module of RRU.
10. Reset the lower-level RRU.
11. Replace the lower-level RRU.
2.4 PM Alarm
2.4.1 198084284 Under-voltage of
External Power Supply

� Description: Under-voltage of External Power Supply

Probable Cause The primary power supply's output voltage is too low.
System Impact It may not impact the service. The board may be power-down. It
causes that the system fails to work properly and services inter-
rupted.
Handling 1. Check whether the power cable is inserted correctly.
Suggestion
2. Check whether the system has input voltage, and measure the
input voltage to see whether it is larger than 40 V. If not, check
the input power supply.
3. Replace the power board.
2.5 SA Alarm
2.5.1 198084068 Environmental
Temperature is High

� Description: Environmental Temperature is High
� Alarm Type: Environment Alarm
Probable Cause 1. The fan is faulty.
2. The environment temperature is out of the allowed tempera-
ture range.
3. The dustproof net is not clean and obstructed.
4. The temperature of the environment where the cabinet is lo-
cated is less than the lower limit of environment temperature
alarm.
5. The air conditioner is faulty.
6. The BS8900 heat exchanger is faulty.
System Impact It might cause boards or the system to work abnormally and ser-
vice performance to degrade, and even cause the service to inter-
rupt sometimes.
Handling 1. Check whether the dustproof net is installed. If it is installed,
Suggestion then check whether the dustproof net is clean. If the dustproof
net is obstructed, then clean it.
2. Check whether the equipment is BS8900. If it is, then check
whether there is any alarm for heat exchanger. If the alarm
exists, handle the problem according to the heat exchanger
troubleshooting guide.
3. Check whether the equipment is installed in the equipment
room. If it is, then check whether the air conditioning sys-
tem of the euqipment room works normally.

4. In the environment monitoring of equipment resource, check

whether the upper limit is set to be 50℃. If it is not, then
modify the upper limit to be 50℃.
5. In environment monitoring of the test management interface,
right-click on SA-13 > Execute Test to query the temperature
at the wind entry of the control shelf. If the temperature at the
wind entry of the control shelf is higher than or equal to 50℃,
then replace the fan control module FA.
2.5.2 198084070 Device Temperature

is High

� Description: Device Temperature is High
� Severity: Minor
� Alarm Type: Environment Alarm
Probable Cause 1. The fan is faulty.
2. The environment temperature is out of the allowed tempera-
ture range.
3. The dustproof net is not clean and obstructed.
System Impact It might cause boards or the system to work abnormally and ser-
vice performance to degrade, and even cause the service to inter-
rupt sometimes.
Handling 1. Check whether there is the "198084068 Environmental tem-
Suggestion perature is high" alarm. If there is, then handle the alarm
according to relevant handling suggestion.
Relevant alarm: 198084068 Environmental temperature is
high.
2. Replace FA.
2.6 Common Board Alarm

2.6.1 198084117 Application Software
Monitoring Alarm

� Description: Application Software Monitoring Alarm
� Severity: Major
Probable Cause 1. The communication between the board and the active main-
control board is faulty.

2. The board's parameter configuration is incorrect.

System Impact Services that the board bears are completely interrupted.
Handling 1. Check whether the board is inserted properly.
Suggestion
2. Check whether the board has any relevant alarm. If there is,
then handle the alarm according to relevant alarm's handling
suggestion.
Relevant Alarms: 198084123 Board Communication Link is In-
terrupted
3. Check if the board slot configured currently is consistent with
the actual slot. If inconsistent, insert the board into the correct
slot.
4. Check whether the RRU is configured with central frequency
parameters at background. If the parameters are not config-
ured, then add such configurations for the RRU.
5. Check whether the RRU is configured with GSM RU parameters
at background. If the parameters are not configured, then add
such configurations for the RRU.
6. Reset the board.
2.6.2 198084123 Board Communication

Link is Interrupted

� Description: Board Communication Link is Interrupted
� Severity: Major
Probable Cause The standby CC or the peripheral board is disconnected from the
active CC board, thus the communication fails.
If the fault persists for a long period of time, then it is usually
caused by fiber connection problems or incorrect configurations.
System Impact The board is faulty.
The board can not communicate with the current active main-con-
trol board, which causes services that the board bears to interrupt.
Handling 1. Check whether the board is inserted in the cabinet.
Suggestion
2. Check whether the board's upper-layer software is downloaded
successfully.
3. Reset the board.
4. Check whether the physical link connection between the board
and the active main-control board is normal, for example,
whether RRU's fiber is connected properly.
5. Check whether the fiber is connected reversely in uplink and
downlink. Exchange uplink fiber and downlink fiber, and ob-
serve. For uplink/downlink engineering fibers, because they
are fixed, this operation can be omitted.

6. Check whether the optical module of R8860 is in correct posi-

tion (including LC2 optical module of the cascaded upper-level
R8860).
7. Replace the fiber.
8. Replace the optical module (including LC2 optical module of
FS/R8860/cascaded upper-level R8860).
9. Check the topology configured for the RRU. Make sure that the
physical connection is consistent with the logical configuration.
10. Check the fiber at the outlet of LC1 of R8860 to see whether it
is correctly connected to the corresponding optical port of FS or
the outlet of LC2 of the cascaded upper-level R8860 according
to the topology configuration. If the physical connection differs
from the logical configuration, then modify the configuration or
the physical connection mode.
11. Check whether the alarm is reported and eliminated (i.e. the
fault is handled) repetitively, and whether the duration from
the alarm being eliminated to the alarm being reported is very
short. If it is, then it is usually due to software version down-
load failure. Check BBU's software package to see whether it
includes the DTR board's software version.
2.6.3 198084129 Board Reboots

� Description: Board Reboots
� Severity: Warning
Probable Cause 1. User executes the board resetting command.
2. The board is powered on and starts.
3. The software is abnormal and causes the board to reset auto-
matically.
System Impact The board is initialized. Services that the board bears are inter-
rupted.
Handling Check the board's history alarms in alarm management interface
Suggestion to decide why the board is reset. If the board is reset due to user's
operation, then it needs no handling.

This page is intentionally blank.

Chapter 3 Radio Unit Alarm
>> 198084123 Board communication link is interrupted
>> 198084117 Application software monitoring alarm
>> 198084056 Downlink digital IF pre-distortion alarm
>> 198084119 Board configuration parameter error
>> 198084094 Remote antenna VSWR alarm
>> 198084093 Remote antenna over VSWR alarm
>> 198084297 The configured operating frequency is out of range
>> 198084282 Lost of frame number at optical port
>> 198084296 60ms tag lost alarm
>> 198084235 Ir signal of port 0 lost
>> 198084295 DL IQ channel checking block alarm
>> 198084283 Lost of frame rate and frame number
3.1 198084123 Board

communication link is interrupted
� Description: Board communication link is interrupted
� Alarm Type: Operation Alarm
Probable Cause The standby CC or the peripheral board is disconnected from the
active CC board, thus the communication fails.
If the fault persists for a long period of time, then it is usually
caused by fiber connection problems or incorrect configurations.
The board can not communicate with the current active main-con-
trol board, which causes services that the board bears to interrupt.
Handling 1. Check whether the board is inserted in the cabinet.
Suggestion
2. Check whether the board's upper-layer software is downloaded
successfully.
3. Reset the board.
4. Check whether the physical link connection between the board
and the active main-control board is normal, for example,
whether RRU's fiber is connected properly.

5. Check whether the fiber is connected reversely in uplink and

downlink. Exchange uplink fiber and downlink fiber, and ob-
serve. For uplink/downlink engineering fibers, because they
are fixed, this operation can be omitted.
6. Check whether the optical module of R8860 is in correct posi-
tion (including LC2 optical module of the cascaded upper-level
R8860).
7. Replace the fiber.
8. Replace the optical module (including LC2 optical module of
FS/R8860/cascaded upper-level R8860).
9. Check the topology configured for the RRU. Make sure that the
physical connection is consistent with the logical configuration.
10. Check the fiber at the outlet of LC1 of R8860 to see whether it
is correctly connected to the corresponding optical port of FS or
the outlet of LC2 of the cascaded upper-level R8860 according
to the topology configuration. If the physical connection differs
from the logical configuration, then modify the configuration or
the physical connection mode.
11. Check whether the alarm is reported and eliminated (i.e. the
fault is handled) repetitively, and whether the duration from
the alarm being eliminated to the alarm being reported is very
short. If it is, then it is usually due to software version down-
load failure. Check BBU's software package to see whether it
includes the DTR board's software version.
3.2 198084117 Application

software monitoring alarm
� Description: Application Software Monitoring Alarm
� Severity: Major
Probable Cause 1. The communication between the board and the active main-
control board is faulty.
2. The board's parameter configuration is incorrect.
System Impact Services that the board bears are completely interrupted.
Handling 1. Check whether the board is inserted properly.
Suggestion
2. Check whether the board has any relevant alarm. If there is,
then handle the alarm according to relevant alarm's handling
suggestion.
Relevant Alarms: 198084123 Board Communication Link is In-
terrupted
3. Check if the board slot configured currently is consistent with
the actual slot. If inconsistent, insert the board into the correct
slot.

4. Check whether the RRU is configured with central frequency

parameters at background. If the parameters are not config-
ured, then add such configurations for the RRU.
5. Check whether the RRU is configured with GSM RU parameters
at background. If the parameters are not configured, then add
such configurations for the RRU.
6. Reset the board.
3.3 198084056 Downlink digital IF

pre-distortion alarm
� Description: Downlink digital IF pre-distortion alarm
Probable Cause Error occurs in DPD during the process of initialization, training,
and startup.
It influences RF's output quality, and services that the board bears
are completely interrupted.
Handling 1. Start the power amplifier at background, and wait for 5 min-
Suggestion utes.
2. At background, make RRU power off and reset it, and wait for
5 minutes.
3. Restart the RF board.
4. Replace the RF board.
3.4 198084119 Board configuration

parameter error
� Description: Board configuration parameter error
Probable Cause 1. Some parameters are not configured.
2. Some parameters are configured incorrectly.
3. Hardware is faulty.
4. The central frequency is incorrect.
System Impact The board is faulty. Also, services that the board bears are com-
pletely interrupted.

Handling 1. Check whether the configured central frequency is within the

Suggestion range of the RRU's working frequency. If it is out of the range,
then re-configure the central frequency.
2. In the radio resource management interface, check whether
the value of "number of carriers" is no less than the number
of actual carriers on this RRU. If not, modify the number of
carriers or the number configured on this RRU, to enable the
number of carriers no less than the number of actual physical
carriers.
3. Reset the board.
3.5 198084094 Remote antenna

VSWR alarm
� Description: Remote antenna over VSWR alarm
Probable Cause 1. The connection of the antenna feeder system is faulty.
2. The antenna feeder system's connection does not match RRU.
3. The antenna feeder is faulty.
4. The board is faulty.
5. The configured operating frequency is out of range.
System Impact It does not influence services that the board bears.
Handling 1. In the Fault Management interface, check whether relevant
Suggestion alarms exist. If yes, then handle the alarm according to rele-
vant alarm's handling suggestion.
Relevant Alarms: 198084297 The configured operating fre-
quency is out of range
2. Remotely make the RRU power off and reset it.
3. Use Sitemaster and high-power matching load to handle the
problem at the site. Test VSWR at the access port of RRU. If
VSWR is out of the normal range, then perform troubleshooting
from the antenna feeder connection to the antenna.
4. Check whether the antenna is CNB antenna and is connected
to port B. If CNB antenna's port B is connected, then it is di-
agnosed that the antenna's VSWR is incorrect and the antenna
should be replaced.
5. Connect the matching load to RRU's Tx/Rx output port, and
make the RRU power on.
6. Replace the RRU.

3.6 198084093 Remote antenna

over VSWR alarm
� Description: Remote antenna over VSWR alarm
Probable Cause 1. The connection of the antenna feeder system is faulty.
2. The antenna feeder system's connection does not match RRU.
3. The antenna feeder is faulty.
4. The board is faulty.
5. The configured operating frequency is out of range.
System Impact It causes the board or the system unable to work normally, and it
also causes services that the board bears to interrupt.
Handling 1. In the Fault Management interface, check whether relevant
Suggestion alarms exist. If yes, then handle the alarm according to rele-
vant alarm's handling suggestion.
Relevant Alarms: 198084297 The configured operating fre-
quency is out of range
2. Remotely make the RRU power off and reset it.
3. Use Sitemaster and high-power matching load to handle the
problem at the site. Test VSWR at the access port of RRU. If
VSWR is out of the normal range, then perform troubleshooting
from the antenna feeder connection to the antenna.
4. Check whether the antenna is CNB antenna and is connected
to port B. If CNB antenna's port B is connected, then it is di-
agnosed that the antenna's VSWR is incorrect and the antenna
should be replaced.
5. Connect the matching load to RRU's Tx/Rx output port, and
make the RRU power on.
6. Replace the RRU.
3.7 198084297 The configured

operating frequency is out of
range
� Description: The configured operating frequency is out of
range

Probable Cause The difference between the carrier's frequency and the central fre-
quency is over 5 MHz.
System Impact The service corresponding to the faulty frequency is interrupted.
Handling 1. Calculate the central frequency.
Suggestion
Relationship between frequency point and frequency:
900 MHz: frequency (MHz) = 935.2 MHz + (frequency point
- 1) * 0.2 MHz, the frequency point is within the range of [1,
124].
1800 MHz: frequency MHz = 1805.2 MHz + (frequency point
- 512) * 0.2 MHz, the frequency point is within the range of
[512, 885].
For example,
If the central frequency is configured as 1825.8 MHz, then the
corresponding frequency point is 615.
The carrier's frequency point configured at background must
be within the range of [615-25, 615+25].
Note: 25 = 5 MHz/0.2 MHz
2. Modify the frequency point configuration.
3.8 198084282 Lost of frame

number at optical port
� Description: Lost of frame number at optical port
� Severity: Minor
� Alarm Type: Communications Alarm
Probable Cause 1. The board's optical module is not in the position.
2. The frame number at optical port used for connecting the board
and FS board or upper-level board is lost.
3. The optical port is not connected properly.
The board's communication link is broken, and services that the
board bears is interrupted completely.
Handling 1. Extract and insert the fiber, and wait for 2 minutes.
Suggestion
2. Replace fiber, replace local optical module and upper-level op-
tical module, and wait for 2 minutes.
3. Replace the RRU.

3.9 198084296 60ms tag lost alarm

� Description: 60ms Tag Lost Alarm
Probable Cause RRU fails to get the correct 60 ms clock signal.
System Impact It might cause the downlink communication from UBPG to RRU to
become abnormal and the service carried by this carrier is inter-
rupted.
Handling 1. Check whether the UBPG board is being reset or being started.
Suggestion If it is, then wait for it to complete the startup.
2. Check whether the optical port has any relevant alarm. If it
has, then handle the alarm according to relevant alarm's han-
dling suggestion.
Relevant Alarms:
� 198084282 Lost of frame number at optical port
3.10 198084235 Ir signal of port 0

lost
� Description: Ir signal of port 0 lost
� Severity: Major
Probable Cause 1. (The local RRU is of the first level) fiber and optical module
between the FS functional board and the local RRU are faulty.
2. (The local RRU is not of the first level) fiber and optical module
of RRU is faulty.
3. (The local RRU is not of the first level) the upper-level RRU is
faulty.
4. FS is reset during the normal system running.
During the normal system running, the FS functional board is re-
set, RRU will report the alarm, and the alarm will disappear after
the FS functional board is powered on. It does not influence ser-
vices. In other cases, the board's communication link is broken
and can not bear any service. The communication between local
RRU and cascaded lower-level RRU interrupts.
Handling 1. Check whether FS is reset during the normal system running.
Suggestion If it is, then no handling is needed.

2. (The local RRU is of the first level) Check whether fiber and
optical module between the FS functional board and the local
RRU are faulty.
i. Check whether the fiber between the FS functional board
and the local RRU is inserted properly and whether it is
broken. If it can not be judged whether the fiber is in
good condition according to its appearance, then replace
the fiber.
ii. Replace the FS functional board and the local RRU's optical
module.
3. (The local RRU is not of the first level) Check whether fiber and
optical module of the upper-level RRU is faulty.
i. Check whether the fiber between the local RRU and the up-
per-level RRU is inserted properly and whether it is broken.
If it can not be judged whether the fiber is in good condi-
tion according to its appearance, then replace the fiber.
ii. Replace optical modules of the local RRU and the upper-
level RRU.
4. (The local RRU is not of the first level) Check whether the up-
per-level RRU is faulty.
i. Check the upper-level RRU's power-on status, and make
sure that the power-on of upper-level RRU is normal.
ii. Reset the upper-level RRU.
3.11 198084295 DL IQ channel

checking block alarm
� Description: DL IQ channel checking block alarm
Probable Cause 1. RRU fails to get the correct 60 ms clock signal.
2. Data receiving at the downlink IQ channel is incorrect.
System Impact It might cause the downlink communication from UBPG to RRU to
become abnormal and the service carried by this carrier is inter-
rupted.
Handling 1. Check whether the UBPG board is being reset or being started.
Suggestion If it is, then wait for it to complete the startup.
2. Check whether the optical port has any relevant alarm. If it
has, then handle the alarm according to relevant alarm's han-
dling suggestion.
Relevant Alarms:
� 198084282 Lost of frame number at optical port

3.12 198084283 Lost of frame rate

and frame number
� Description: Lost of frame rate and frame number
� Severity: Minor
Probable Cause 1. The board's optical module is not in the position.
2. The frame number at optical port used for connecting the board
and FS board or upper-level board is lost.
3. The optical port is not connected properly.
System Impact 1. The frame number received at the optical port used for con-
necting the board and FS board or upper-level board is lost.
2. The optical port, which is used for connecting the board and
the FS board, has not received frame rate for a consecutive
160 ms.
3. The service carried by the board is interrupted.
Handling 1. Extract and insert the fiber, and wait for 2 minutes.
Suggestion
2. Replace fiber, replace local optical module and upper-level op-
tical module, and wait for 2 minutes.
3. Replace the RRU.

ZXSDR Bts Alarm Handling 1 Training Manual 201010 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ZXSDR Bts Alarm Handling 1 Training Manual 201010 PDF

Uploaded by

Copyright:

Available Formats

ZXSDR BTS

Copyright © 2006 ZTE CORPORATION.

The ultimate right to interpret this product resides in ZTE CORPORATION.

Publishing Date (MONTH/DATE/YEAR) : 20091111

will be able to:

Confidential and Proprietary Information of ZTE CORPORATION 1

1.1 Overview of Fault Management

1.2 Alarm Management Interface

FIGURE 1 ALARM MANAGEMENT INTERFACE

1. Main Menu 4. Alarm Message View

Main Menu Table 1 shows the description of main menu functions.

2 Confidential and Proprietary Information of ZTE CORPORATION

TABLE 1 DESCRIPTION OF MAIN MENU FUNCTIONS

Menu item Function

System Set the property of system func-

View Access to the initial interface menu

Alarm Inspection View current alarm, history alarm,

Alarm Setting Alarm processing rule, alarm box,

Help System help information

TABLE 2 DESCRIPTION OF SHORTCUT BUTTON ABOUT ALARM MANAGEMENT

Lock Screen To lock the screen

Logout Logout current user

Query current Based on user demands, query current alarm

Alarm History Query Based on user demands, query history alarm

Notification Query Based on user demands, query the notification

Help Topics Provide the help information for users.

Confidential and Proprietary Information of ZTE CORPORATION 3

1.3 Alarm Representation

Notification refers to unrepeated or transient fault or event oc-

1.4 Alarm Structure

4 Confidential and Proprietary Information of ZTE CORPORATION

� Major. Major alarm significantly affects system operation

In addition, the severity of a few alarms is undetermined. It is

Confidential and Proprietary Information of ZTE CORPORATION 5

and the fault disappears, the alarm handling terminates. If

1.5 Notification Structure

6 Confidential and Proprietary Information of ZTE CORPORATION

Alarm Property � Alarm Code: 198084024

Confidential and Proprietary Information of ZTE CORPORATION 7

2.1.2 198084020 E1/T1 Link Loss of

Alarm Property � Alarm Code: 198084020

8 Confidential and Proprietary Information of ZTE CORPORATION

i. Check whether the SA board is inserted properly.

2.1.3 198084034 PPP Link Broken

Alarm Property � Alarm Code: 198084034

Confidential and Proprietary Information of ZTE CORPORATION 9

is incompliant or any external force, you shall change the

2.1.4 198084035 PPP Links are All

Alarm Property � Alarm Code: 198084035

10 Confidential and Proprietary Information of ZTE CORPORATION

3. Check whether the configuration of E1 and T1 modes at two

2.1.5 198084019 E1/T1 LOS (Loss Of

Alarm Property � Alarm Code: 198084019

Confidential and Proprietary Information of ZTE CORPORATION 11

2.1.6 198084021 E1/T1 Loss of Cell

Alarm Property � Alarm Code: 198084021

12 Confidential and Proprietary Information of ZTE CORPORATION

2.1.7 198084025 E1/T1 Link Self-loop

Alarm Property � Alarm Code: 198084025

2.1.8 198084250 IQ Config Failed

Alarm Property � Alarm Code: 198084250

Confidential and Proprietary Information of ZTE CORPORATION 13

2.1.9 198084030 SCTP Association is