S.N.

Service Affecting Alarm

Base Station Frame Number

1
Synchronization Error

2 BBU CPRI Interface Error

BBU CPRI Optical Module or Electrical

3
Port Not Ready

4 BBU DC Output Out of Range

BBU Optical Module Transmit/Receive

5
Fault

6 Board Hardware Fault

7 Board Powered Off

8 Board Type and Configuration Mismatch

9 Cell Unavailable

eNodeB Control Plane Transmission

10
Interruption

Inter-Board CANBUS Communication

11
Failure

12 IP Address Conflict
13 Local Cell Capability Decline

14 Local Cell Unusable

15 No License Running in System

16 RF Unit ALD Current Out of Range

17 RF Unit Hardware Fault

RF Unit RX Channel RTWP/RSSI Too

18
Low

RF Unit RX Channel RTWP/RSSI

19
Unbalanced

20 RF Unit TX Channel Gain Out of Range

21 RF Unit VSWR Threshold Crossed

22 Transmission Optical Interface Error

Transmission Optical Module Not In

23
Position

24 SCTP Link Fault

eNodeB Control Plane Transmission

25
Interruption

26 S1 Interface Fault

27 X2 Interface Fault
28 System Clock Failure

29 SCTP Link IP Address Unreachable

30 RF Unit Software Program Error

31 RF Unit Maintenance Link Failure

Inter-System Site-Level Configuration

32
Conflict

33 Inter-System Control Rights Conflict

Inter-System Cabinet Configuration

34
Conflict

35 IKE Negotiation Failure

36 Configuration File Damaged

37 Cell Capability Degraded

38 Cell Blocked

39 Automatic Version Rollback

40 Automatic Certificate Update Failed

41 Inter-System Communication Failure

42 MAC Excessive Frame Error Rate

43 System Clock Unlocked

Alarm Description

This alarm is reported when the frame number received on the board
for synchronization has errors

This alarm is reported when the link between the BBU and the lower-
level RF units malfunctions. This alarm is cleared when the link can
function properly and remains functional for a period of time (90s by
default). The alarm filtering parameters can be set by running the SET
ALMFILTER command

This alarm is reported when the optical module on the port of

the BBU connecting to the lower-level RF units or
the CPRI electrical cable is not in position.

This alarm is reported when the 12 V DC output of the power module

in the BBU is out of range (overvoltage or undervoltage)

This alarm is reported when the BBU cannot properly receive signals
on the fiber optic cable from the lower-level RF units. This alarm is
cleared when the BBU can properly receivesignals on the
fiber optic cable from the lower-level RF units and the signal reception
lasts for a period of time (150s by default). The alarm filtering
parameters can be set by running the SET ALMFILTER command.

This alarm is reported when the board hardware is faulty

This alarm is reported when a board is powered off or cannot

be powered on.
This alarm is reported when the actual type of a board or
daughter board or the working mode of a board differs from
the configuration.

The cell status is related to physical resources such as baseband

resources, RF resources, CPRI resources, clock resources,
transmission resources, and also license resources. When the
physical resources are insufficient, faulty, incorrectly configured, or
blocked, a cell becomes unavailable due to physical resource
unavailability. When the physical resources are available, a cell can
also be unavailable due to license resource insufficiency. This alarm
is reported when a cell is unavailable for 90 seconds (default value)
continuously.
This alarm is cleared when the cell becomes available again and
stays available for 15 seconds (default value). The cell unavailable
duration and cell available duration for reporting and clearing this
alarm, respectively, can be set by running the SET ALMFILTER
command

This alarm is reported when the status of all the SCTP links (no less
than two) that carry the S1 and X2 interfaces is abnormal. This alarm
is cleared when the status of an SCTP link that carries S1 and X2
interfaces becomes normal and the status remains normal for 90
seconds (default value)

CANBUS is a communication bus which is used for device

management in the base station.
This alarm is reported when the CANBUS communication fails
between the main control board and other boards. This alarm is
cleared when the CANBUS communication recovers and remains
functional for a period of time (180s by default). The alarm filtering
parameters can be set by running the SET ALMFILTER command.

This alarm is reported when the IP address of the device conflicts with
the IP address of an external device.
This alarm is reported when the RF resources or baseband resources
of a base station do not meet the specifications of the cell
configuration, or configurations for carrier aggregation (CA) are
inconsistent. For example, the serving cell is configured with
4TX+4RX. If two transmit channels become unusable unexpectedly,
the antenna configuration of the serving cell will be degraded to
2TX+2RX; if the baseband resources are insufficient, the serving cell
will be reestablished with degraded performance on the baseband
processing unit. Therefore, the serving cell can continue service
provisioning. In multimode base stations, if resources such as
frequencies or power are insufficient, some antennas cannot be fully
utilized, and therefore the cell capability is degraded. In BBU
interconnection-based CA, if configurations of the CaGroupCell MO in
different BBUs are inconsistent, CA cannot function properly.

This alarm is reported when a system does not have a valid license.
This alarm is cleared 2 minutes (by default) after a valid license is
loaded.
The alarm filtering parameters can be set by running the SET
ALMFILTER command

This alarm is reported when the current supplied by the RF unit to the
antenna device through feeder or multi-wire cable is beyond the
normal range.

This alarm is reported when the RF unit hardware is faulty

This alarm is reported when the RTWP/RSSI on the RX channel of

the RF unit is lower than the predefined threshold. For the eNodeB,
this alarm detects only the RTWP on the RX channel of the RF unit.
RTWP is short for received total wideband power, which consists of
signal power and noise power. RSSI is short for received signal
strength indicator.
This alarm is reported when the difference between the RTWP/RSSI
of the main RX channel and the RTWP/RSSI of the diversity RX
channel exceeds a specified threshold. For the eNodeB, this alarm
detects only the RTWP on the RX channel of the RF unit. RTWP is
short for received total wideband power, which consists of signal
power and noise power. RSSI is short for received signal strength
indicator

This alarm is reported when the difference between the actual gain
and the standard gain on the TX channel of the RF unit is greater
than 2.5 dB
The voltage standing wave ratio (VSWR) measures the signal power
that the load actually receives from the transmission line. This alarm
is reported when the VSWR at the antenna port of the TX channel of
an RF unit is greater than the preset threshold. The VSWR at the
antenna port is calculated based on the sampled forward power and
reverse power.

This alarm is reported when the link to the transmission port fails to
transmit or receive optical signal.

This alarm is reported when the optical module on the transmission

port is not in position

This alarm is reported when the base station detects that the Stream
Control Transmission Protocol (SCTP) link cannot process services

This alarm is reported when the status of all the SCTP links (no less
than two) that carry the S1 and X2 interfaces is abnormal. This alarm
is cleared when the status of an SCTP link that carries S1 and X2
interfaces becomes normal and the status remains normal for 90
seconds (default value

If the SCTP link is available, the eNodeB sends an S1 link setup

request to the MME. The MME checks the request validity. If the
check fails, the S1 link cannot be set up. If the eNodeB receives a
response from the MME, but an MME code (MMEC) collision occurs,
the S1 link cannot be set up, either.
This alarm is reported when the S1 link bearing the SCTP is faulty, or
when the S1 link cannot be set up because the configuration data of
the S1 Application Protocol (S1AP) layer is incorrect or the MME is
abnormal.

If the SCTP link is available, the eNodeB sends an X2 link setup

request to the peer eNodeB. The peer eNodeB checks the validity of
the request. If the check fails, the X2 link cannot be set up. If the local
eNodeB receives the response from the peer eNodeB, but the local
eNodeB detects that the peer eNodeB is on the blacklist, the X2 link
cannot be set up, either.
This alarm is reported when the X2 link bearing the SCTP is faulty, or
when the X2 link cannot be set up because the configuration data of
the X2 Application Protocol (X2AP) layer is incorrect or the peer
eNodeB is abnormal
The main control board uses the phase-locked loop (PLL) to
synchronize with the external reference clock and provides the
system clock to service processing boards. This alarm is reported
when the base station uses the local crystal oscillator longer than its
duration limit. For details about how to set this duration limit, see
related descriptions in Common Clock Feature Parameter
Description.
This alarm is generated when the SCTP link is configured with two
destination IP addresses and one of them is unreachable.
This alarm is reported when the software program of the RF unit runs
improperly, such as suspension.

A BBU connects to an RF unit by using CPRI electrical cables or

CPRI fiber optic cables. This alarm is reported when the maintenance
link between a BBU and an RF unit malfunctions. This alarm is
cleared when the maintenance link recovers and remains functional
for a period of time (3 minutes by default). The alarm filtering
parameters can be set by running the SET ALMFILTER command.

In a multimode base station, this alarm is reported when the site-level

configurations are inconsistent between different modes, such as the
reference clock type and deployment ID (DID).

In a multimode base station, this alarm is reported when the loading

control rights are not configured or are inconsistent between different
modes in the base station.

In a multimode base station, this alarm is reported when the cabinet

configurations are inconsistent between different modes, such as the
cabinet type.

This alarm is reported when the base station detects that the Internet
Key Exchange (IKE) negotiation with the peer device fails.
 After the user activated the configuration file, the system performs
validity check on the configuration file in the case of startup. This
alarm is reported when the configuration file is invalid. Note: If the
alarm is not cleared with the recommended actions, the alarm will be
automatically cleared after the base station is reset. In this case, the
base station works based on the default configuration.

This alarm is reported when the RF resources or baseband resources

of a base station do not meet the specifications of the cell
configuration, or configurations for carrier aggregation (CA) are
inconsistent. For example, the serving cell is configured with
4TX+4RX. If two transmit channels become unusable unexpectedly,
the antenna configuration of the serving cell will be degraded to
2TX+2RX; if the baseband resources are insufficient, the serving cell
will be reestablished with degraded performance on the baseband
processing unit. Therefore, the serving cell can continue service
provisioning. In multimode base stations, if resources such as
frequencies or power are insufficient, some antennas cannot be fully
utilized, and therefore the cell capability is degraded. In BBU
interconnection-based CA, if configurations of the CaGroupCell MO in
different BBUs are inconsistent, CA cannot function properly.

This alarm is reported when the user blocks a cell through a

command. The purpose of blocking a cell is for service testing or fault
isolation. After the test is complete or the faulty is rectified, the cell
needs to be unblocked.
This alarm is reported when the NE detects that the current version is
improper and performs an automatic version rollback.

This alarm is reported when the base station fails to update the
certificate.

The main control boards in different modes of a multimode base

station periodically exchange handshake messages. If the main
control board in one mode does not receive a handshake response
message from its counterpart within about 45s, this alarm is reported.
This alarm is cleared when the main control board in one mode
successfully receives a handshake response message from its
counterpart within about 30s.

When the BBU interconnection cable or main control board of a peer

mode is removed, the peer mode cannot be detected. In this case,
the system will delete the peer mode about 3 minutes later and
therefore this alarm will also be cleared.
 This alarm is reported when the frame error rate (FER) at the MAC
layer on an Ethernet port exceeds the preset threshold (10 per mill by
default, user-configurable). This alarm is cleared when the FER at the
MAC layer is less than the alarm clear threshold in 10 minutes. The
alarm trigger threshold and alarm clear threshold are set by running
the SET ETHPORT command.
This alarm is reported when the phase-locked loop (PLL) of the
system clock becomes unlocked and remains unlocked for a period of
time (30s by default). This alarm is cleared when the system clock
PLL becomes locked and remains locked for a period of time (180s
by default). The alarm filtering parameters can be set by running the
SET ALMFILTER command.
Alarm Impact

The ongoing services carried on the board are disrupted

In chain topology, the link for the lower-level RF units is disconnected and the
services carried on the lower-level RF units are interrupted. In CPRI MUX, the
services of the peer mode are interrupted when the local mode is a converging party
and the faulty port provides the convergence function.
In ring topology, the reliability of the links for the RF units decreases. In this case, the
standby link becomes the activated link for the lower-level RF units and the services
are switched over to the standby link. If a hot ring is used, the ongoing services are
not affected. If a cold ring is used, the ongoing services are interrupted temporarily

In chain topology, the link for the lower-level RF units is disconnected and the
services carried on the lower-level RF units are interrupted. In CPRI MUX, the
services of the peer mode are interrupted when the local mode is a converging party
and the faulty port provides the convergence function.
In ring topology, the reliability of the links for the RF units decreases. In this case, the
standby link becomes the activated link for the lower-level RF units and the services
are switched over to the standby link. If a hot ring is used, the ongoing services are
not affected. If a cold ring is used, the ongoing services are interrupted temporarily

The boards in the BBU may be reset or powered off unexpectedly. In this case, the
ongoing services carried on the BBU are interrupted.

In chain topology, the link for the lower-level RF units is disconnected and the
services carried on the lower-level RF units are interrupted. In CPRI MUX, the
services of the peer mode are interrupted when the local mode is a converging party
and the faulty port provides the convergence function.
In ring topology, the reliability of the links for the RF units decreases. In this case, the
standby link becomes the activated link for the lower-level RF units and the services
are switched over to the standby link. If a hot ring is used, the ongoing services are
not affected. If a cold ring is used, the ongoing services are interrupted temporarily.

The board fails to work properly. The ongoing services carried on the board may be
interrupted. The services of the peer mode are interrupted when the following
conditions are met:
The RF units use CPRI MUX.
The local mode is the converging party.
The faulty board is a baseband board that provides the convergence function
The ongoing services carried on the board are interrupted. The service processing
capability of the peer mode decreases or the services of the peer mode are
interrupted when the following conditions are met:
The RF units use CPRI MUX.
The local mode is the converging party.
The faulty board is a baseband board that provides the convergence function
The board cannot carry services. The services of the peer mode are interrupted when
the following conditions are met:
The RF units use CPRI MUX.
The local mode provides the aggregation function. The faulty board is a baseband
board that provides the aggregation function

The cell where the alarm is reported cannot provide services.

The status of all the SCTP links (no less than two) that carry the S1 and X2 interfaces
is abnormal. As a result, all the S1 and X2 interfaces of the base station cannot be
established, cells cannot be activated, and UEs cannot access the network

The user fails to power on/off the board or obtain the board electronic label. The
voltage and temperature of the board cannot be monitored. In this case, the board
reliability decreases.
If this alarm is reported in the base station to be upgraded, the faulty board may fail to
be activated during the upgrade.

Services over the conflicting IP address of the device are interrupted.

 The radio resource capability of the cell available for operators derating.

The system enters default license mode. Services are subject to the default license.

The antenna device cannot work normally. In the case of an RET antenna, the
antenna tilt cannot be regulated. In the case of a TMA, the receive sensitivity
decreases. In the case of a RAE, the files storied in the equipment cannot be updated
or read
The RF unit may work improperly. The ongoing services carried on the RF unit may
be disrupted.

The receive sensitivity of the RF unit decreases. The demodulation performance of

the cell deteriorates. The uplink coverage shrinks.
If the RTWP/RSSI on all RX channels of the cell is too low, the ongoing services of
the cell may be interrupted.

The receive sensitivity of the RF unit decreases. The demodulation performance of

the cell deteriorates. The uplink coverage shrinks.

When the gain on the TX channel is extremely high, the downlink coverage of the cell
is excessive. In this case, the interference caused by cross coverage occurs.
When the gain on the TX channel is extremely low, coverage holes exist in the
downlink coverage of the cell. In serious cases, the ongoing services carried on the
RF unit may be disrupted.
The return loss at the antenna port is excessive. When the detected VSWR exceeds
the major alarm threshold, the system determines whether to switch off the TX
channel of the RF unit based on the actual configurations. When the VSWR alarm
post-processing switch is set to ON, the TX channel of the RF unit is switched off and
the alarm cannot be automatically cleared, and the ongoing services carried on the
TX channel are interrupted. When the VSWR alarm post-processing switch is set to
OFF, the power of the RF unit is automatically decreased (by 3 dB by default. The
specific value depends on service status.) to avoid hardware damage, and the alarm
can be automatically cleared.

The transmission link to the faulty port is disconnected. If a backup transmission port
or backup route exists, a switchover occurs and the ongoing services are not
affected. If the transmission load sharing function is configured on the faulty port, the
available transmission bandwidth decreases and data throughput is reduced

The transmission link to the faulty port is disconnected. If a backup transmission port
or backup route exists, a switchover occurs and the ongoing services are not
affected. If the transmission load sharing function is configured on the faulty port, the
available transmission bandwidth decreases and data throughput is reduced.

The SCTP link cannot process signaling messages.

The status of all the SCTP links (no less than two) that carry the S1 and X2 interfaces
is abnormal. As a result, all the S1 and X2 interfaces of the base station cannot be
established, cells cannot be activated, and UEs cannot access the network.

The base station releases all UEs that have accessed the network over the faulty S1
interface.If no functional S1 interface is available and MNTMODE in the EQUIPMENT
MO is set to TESTING, the base station could activate the cells, and new UEs cannot
access these cells.If no functional S1 interface is available and MNTMODE in the
EQUIPMENT MO is not set to TESTING, the base station will deactivates the cells

The local base station releases the UEs involved in the inter-base station handover
procedure on the correlated X2 interface. Before the alarm is cleared, the local base
station cannot allow the inter-base station handover on the faulty X2 interface, and
the local base station does not support the inter-cell interference coordination with the
corresponding base station on the correlated X2 interface.
The quality of base station services decreases, resulting in handover failures and call
drops. In worst cases, the base station cannot provide services.

If another destination IP address becomes unreachable, the upper-layer services will

be released.

The RF unit may work improperly. The RF unit will be automatically reset. The
ongoing services carried on the RF unit are disrupted during reset.

The ongoing services carried on the RF unit are interrupted.

When the reference clock type is incorrectly configured for a mode, the reference
clock from the mode is unusable. In this case, the system clock works in free-run
mode. Services are not affected during a short period of time. When the DID
configured for a mode is incorrect, users cannot manage the mode by the DID.

When the loading control rights conflict, the software version of the USCU and the RF
unit shared between different modes may be incorrect. In this case, some functions of
the multimode base station fail and the reliability decreases.

The cabinet types are inconsistent between different modes, affecting the cabinet
configuration, cabinet maintenance, and the inventory information recording.

System Actions

The system cannot perform services.

When the configuration file is invalid, part of or all the data configuration of the NE is
lost. In this case, the NE may fail to carry services.

The radio resource capability of the cell available for operators derating.

The cell where the alarm is reported cannot provide services.

Version rollback leads to NE reset. During the reset, the ongoing services carried on
the NE are interrupted.
The certificate cannot be automatically updated as scheduled, which may bring
security risks. If this alarm is not handled immediately, the certificate will expire in a
period of time and services will be interrupted.

The consistency check cannot be performed for inter-system configuration, and

common alarms cannot be identified, affecting alarm monitoring.
The transmission quality of the Ethernet link deterioarates. The ongoing services may
even be interrupted.

The hardware clock fails. The ongoing services carried on the board are interrupted.
Possible Cause

The system clock phase-locked loop in the main control board is unlocked,This board is not securely installed,Th

Inappropriate data configurations,Hardware fault,Software fault,Optical ports carry the CPRI link. The optical con
installed in the BBU or RF unit, or the cable is faulty.

A redundant RRU chain/ring is configured,The optical module on the CPRI port of the BBU is not in position, or th
module or electrical port is faulty,The connecting piece on the CPRI port of the BBU is faulty.

The AC mains supply fails or the power cabinet is faulty, resulting in an improper -48 V DC input supplied for the

The optical module on the CPRI port of the BBU is faulty or not installed securely, or the cable connection on the
RF unit, in terms of type (single-mode or multi-mode) and rate, The optical module on the CPRI port of the lower
the connected optical fiber, in terms of type (single-mode or multi-mode) and rate,The CPRI interface board in th
optical connector of the lower-level RF unit is dirty,The optical module on the CPRI port of the lower-level RF uni
lower-level RF unit is faulty,The electrical module is faulty.

The active or standby network port is faulty,The active-standby arbitration component is faulty,The GE link inside
component is faulty,The GE switching unit is faulty, The forwarding component is faulty,The board communicatio
is faulty.

The board is automatically powered off to prevent burnout in the case of a too high board temperature, The boa
A mistaken board is configured on the M2000, A mistaken board is installed in the slot.

The board (non-control board) to which the alarm pertains to is not installed or is not properly installed,The boa
control board is faulty,The BBU hardware is faulty.

The IP address of the device is incorrectly configured,The IP address of the external device is incorrectly configur
The license file is not activated.

The preset ALD current threshold of the RF unit is incorrect,The feeder connector is loose or waterlogged,The fe

The RF unit hardware is faulty.

The setting of attenuation of the RF unit is incorrect,The TMA is faulty,The feeder installation is improper. For ex

The main RX channel or diversity RX channel of the RF unit is faulty,The setting of attenuation on the RX channel
intermodulation power of the main antenna,Antenna cables are connected incorrectly.

Hardware fault,The transmit channel is faulty, which decreases the transmit gain,Software fault,The software us
Inappropriate data configuration,Hardware fault

The optical module on the transmission port of the BBU is faulty or not installed securely, or the cable connectio
module on the transmission port of the peer transmission device is faulty or not installed securely, the cable con
The optical connection between the BBU and the peer transmission device is faulty.

Redundant transmission links are configured on the BBU,The optical module on the transmission port of the BBU

The transmission equipment is faulty,The data configuration of the link is erroneous,The link at the peer end is fa
The clock reference is not configured,The clock reference malfunctions.

The transmission equipment is faulty,The data configuration of the link is erroneous,The link at the peer end is a

The software program of the RF unit runs improperly, such as suspension.

External causes,There is a high probability that the AC power supply to the RF units failed or that there is no pow
between the BBU and an RF unit or between upper-level and lower-level BBUs is faulty,There is a low probability
faulty,When the dual-mode CPRI MUX topology is adopted, the backplane link between the aggregating and agg
aggregates data has hardware faults, is not installed, is not powered on, or is not configured,When the dual-mod
adopted, the hardware CPRI capability of the mode whose data is aggregated is insufficient,Software fault

There is a low probability that the software is faulty.

Inappropriate data configurations
N/A

The clock reference type of a mode is incorrect,The DID of a mode is incorrect.

The loading control rights are not configured after the multi-mode base station is deployed,The loading control r
other mode.

In a multi-mode base station, the cabinet type of one mode is incorrectly configured.

The Ethernet link is faulty,The parameters configured for the local device are inconsistent with the parameters c
The current software version has problems.

The transmission network is faulty,The task used to automatically update the certificate is not configured accord

The main control board of the other mode is running improperly,The main control board of the current mode is
main control board of the other mode is faulty,The hardware of the main control board of the current mode is fa
The local equipment works improperly,The peer equipment works improperly,The transmission cable is subject t

The clock reference malfunctions,The clock reference is not configured,The main control board hardware is fault
S.N. Service Affecting Alarm
1 Base Station Frame Number Synchronization Error
2 BBU CPRI Interface Error
3 BBU CPRI Optical Module or Electrical Port Not Ready
4 BBU DC Output Out of Range
5 BBU Optical Module Transmit/Receive Fault
6 Board Hardware Fault
7 Board Powered Off
8 Board Type and Configuration Mismatch
9 Cell Unavailable
10 eNodeB Control Plane Transmission Interruption
11 Fan Stalled
12 Inter-Board CANBUS Communication Failure
13 IP Address Conflict
14 Local Cell Capability Decline
15 Local Cell Unusable
16 No License Running in System
17 RF Unit Hardware Fault
18 RF Unit RX Channel RTWP/RSSI Too Low
19 RF Unit RX Channel RTWP/RSSI Unbalanced
20 RF Unit TX Channel Gain Out of Range
21 RF Unit VSWR Threshold Crossed
22 Transmission Optical Interface Error
23 Transmission Optical Module Not In Position
24 SCTP Link Fault
25 S1 Interface Fault
26 X2 Interface Fault
27 System Clock Failure
28 SCTP Link IP Address Unreachable
29 RF Unit Software Program Error
30 RF Unit Maintenance Link Failure
31 Monitoring Device Maintenance Link Failure
32 Inter-System Site-Level Configuration Conflict
33 Inter-System Control Rights Conflict
34 Inter-System Cabinet Configuration Conflict
35 Configuration File Damaged
36 Cell Capability Degraded
37 Cell Blocked
38 Automatic Version Rollback
39 Automatic Certificate Update Failed
40 Inter-System Communication Failure
41 Monitoring Device Hardware Fault
42 System Clock Unlocked
43 NE Is Disconnected
44 External Clock Reference Problem
45 IP Clock Link Failure
46 eNodeB S1 Control Plane Transmission Interruption
47 RF Unit Optical Module Fault
48 RF Unit Optical Interface Performance Degraded
49 RF Unit Optical Module Transmit/Receive Fault
50 Cell RX Channel Interference Noise Power Unbalanced
51 Time Synchronization Failure
52 RF Unit CPRI Interface Error
S.N. Service Affecting Alarm Alarm ID Impact Service Comment
1 Base Station Frame Number Synchronization Error 26265 Y GUL
2 BBU CPRI Interface Error 26234 Y GUL
3 BBU CPRI Optical Module or Electrical Port Not Ready 26231 Y GUL
4 BBU DC Output Out of Range 26112 Y GUL
5 BBU Optical Module Transmit/Receive Fault 26232 Y GUL
6 Board Hardware Fault 26200 Y GUL
7 Board Powered Off 26214 Y GUL
8 Board Type and Configuration Mismatch 26251 Y GUL
9 Cell Unavailable 29240 Y GUL
10 eNodeB Control Plane Transmission Interruption 29207 Y L
11 Fan Stalled 25673 Y GUL
12 Inter-Board CANBUS Communication Failure 26101 Y GUL
13 IP Address Conflict 25885 Y GUL
14 Local Cell Capability Decline 28206 Y UL
15 Local Cell Unusable 28203 Y UL
16 No License Running in System 26818 Y L
17 RF Unit Hardware Fault 26532 Y GUL
18 RF Unit RX Channel RTWP/RSSI Too Low 26521 Y GUL
19 RF Unit RX Channel RTWP/RSSI Unbalanced 26522 Y GUL
20 RF Unit TX Channel Gain Out of Range 26520 Y GUL
21 RF Unit VSWR Threshold Crossed 26529 Y GUL
22 Transmission Optical Interface Error 26222 Y GUL
23 Transmission Optical Module Not In Position 26221 Y GUL
24 S1 Interface Fault 29201 Y L
25 System Clock Failure 26260 Y GUL
26 SCTP Link IP Address Unreachable 25955 Y GUL
27 RF Unit Software Program Error 26533 Y GUL
28 RF Unit Maintenance Link Failure 26235 Y GUL
29 Inter-System Control Rights Conflict 26277 Y GUL
30 Configuration File Damaged 26242 Y GUL
31 Cell Capability Degraded 29243 Y L
32 Cell Blocked 29245 Y L
33 Automatic Version Rollback 26255 Y GUL
34 Automatic Certificate Update Failed 26842 Y GUL
35 Inter-System Communication Failure 26270 Y GUL
36 System Clock Unlocked 26264 Y GUL
37 NE Is Disconnected 25623 Y GUL
38 External Clock Reference Problem 26262 Y GUL
39 IP Clock Link Failure 26263 Y GUL
40 eNodeB S1 Control Plane Transmission Interruption 29213 Y L
41 RF Unit Optical Module Fault 26507 Y GUL
42 RF Unit Optical Interface Performance Degraded 26506 Y GUL
43 RF Unit Optical Module Transmit/Receive Fault 26503 Y GUL
44 Cell RX Channel Interference Noise Power Unbalanced 29250 Y L
45 Time Synchronization Failure 26266 y GUL
46 RF Unit CPRI Interface Error 26504 Y GUL