BTS3202E V100R011C10SPC230

Alarm Changes

Issue 01

Date 2016/10/08

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2016. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei
Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the
products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise
specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties,
guarantees or representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to
ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute a warranty of
any kind, express or implied.

Huawei Technologies Co., Ltd.

Huawei Industrial Base
Bantian, Longgang
Address:
Shenzhen 518129
People's Republic of China
Web site: http://www.huawei.com
Email: support@huawei.com
Purpose
The Alarm Change Statement in this document provides alarm changes between different eNodeB
versions.

Intended Audience
This document is intended for:
Field engineers
System engineers
Network operators
Network planners

Structure

Change Type Alarm change type, for example, added, modified, or deleted.

Alarm ID ID of the changed alarm in a new version.

Alarm Name Name of the changed alarm in a new version.

Describes the changes in alarms of a new version from the following aspects:
● Alarm severity: Describes the changes in the alarm severity.
● Location information: Describes the changes in location information of alarms, including the addition,
modification, and deletion of location parameters. The changes in value ranges must be mainly described for
Change Description
modified location parameters, including addition, modification, and deletion of values.
● Alarm generation and clearance mechanism: Describes the changes in the alarm generation and clearance
mechanism. With these changes, alarms may be different before and after an update.
●Others: Describes other changes, such as changes in the alarm name and NMS type.

Describes whether the changes involve the northbound interface (NBI). The value of this field can be Yes or No.

● Yes: The changes involve the NBI. For example, the NBI reporting data changes if alarms are added or
Involve the NBI
deleted or if alarm parameters are modified.
● No: The changes do not involve the NBI. For example, the NBI reporting data does not change if the alarm
detection mechanism or alarm trigger threshold is changed.

Describes whether the changes are compatible with the NBI. This field applies only to the changes that involve
the NBI. The value of this field can be Yes, No, or N/A.
● Yes: The changes are compatible with the NBI. For example, new alarms or new alarm parameters are
Compatible with the compatible with the NBI.
NBI ● No: The changes are incompatible with the NBI. For example, deleted alarms, modified alarm names,
modified alarm parameter names, changed value type of alarm parameters, or deleted alarm parameters are
incompatible with the NBI.
● N/A: not involved.

Change Reason Describes change reasons and benefits brought by these changes to users.

Describes scenarios in which alarms are inconsistent before and after an upgrade, including the following
scenarios:
● An alarm does not exist before an upgrade but occurs after the upgrade.
● Alarm A is changed to alarm B after an upgrade.
Upgrade Impact ● An alarm exists before an upgrade but is cleared after the upgrade.
Impacts of an upgrade can be described from the following aspects:
● Upgrade impact: Describes the scenarios in which the inconsistency occurs.
● Preventive measures: Describes measures of avoiding the inconsistency.
● Suggestions: Describes suggestions on how to handle the inconsistency after an upgrade.
Applicable Mode Indicates the applicable mode of a alarm.
The Alarm Change Statement in this document provides alarm changes between different eNodeB
versions.

udience
This document is intended for:
Field engineers
System engineers
Network operators
Network planners

Alarm change type, for example, added, modified, or deleted.

ID of the changed alarm in a new version.

Name of the changed alarm in a new version.

Describes the changes in alarms of a new version from the following aspects:
● Alarm severity: Describes the changes in the alarm severity.
● Location information: Describes the changes in location information of alarms, including the addition,
modification, and deletion of location parameters. The changes in value ranges must be mainly described for
modified location parameters, including addition, modification, and deletion of values.
● Alarm generation and clearance mechanism: Describes the changes in the alarm generation and clearance
mechanism. With these changes, alarms may be different before and after an update.
●Others: Describes other changes, such as changes in the alarm name and NMS type.

Describes whether the changes involve the northbound interface (NBI). The value of this field can be Yes or No.

● Yes: The changes involve the NBI. For example, the NBI reporting data changes if alarms are added or
deleted or if alarm parameters are modified.
● No: The changes do not involve the NBI. For example, the NBI reporting data does not change if the alarm
detection mechanism or alarm trigger threshold is changed.

Describes whether the changes are compatible with the NBI. This field applies only to the changes that involve
the NBI. The value of this field can be Yes, No, or N/A.
● Yes: The changes are compatible with the NBI. For example, new alarms or new alarm parameters are
compatible with the NBI.
● No: The changes are incompatible with the NBI. For example, deleted alarms, modified alarm names,
modified alarm parameter names, changed value type of alarm parameters, or deleted alarm parameters are
incompatible with the NBI.
● N/A: not involved.

Describes change reasons and benefits brought by these changes to users.

Describes scenarios in which alarms are inconsistent before and after an upgrade, including the following
scenarios:
● An alarm does not exist before an upgrade but occurs after the upgrade.
● Alarm A is changed to alarm B after an upgrade.
● An alarm exists before an upgrade but is cleared after the upgrade.
Impacts of an upgrade can be described from the following aspects:
● Upgrade impact: Describes the scenarios in which the inconsistency occurs.
● Preventive measures: Describes measures of avoiding the inconsistency.
● Suggestions: Describes suggestions on how to handle the inconsistency after an upgrade.
Indicates the applicable mode of a alarm.
Alarm Changes
BTS3202E V100R011C10SPC230 Compared with BTS3202E V100R011C10SPC210
Change Description
Change Type Alarm ID Alarm Name Alarm Location Alarm Generation and
Others
Severity Information Clearance Mechanism

External Clock Reference Problem

Modified 26262 - - Display of the value of th -

Modified 26260 System Clock F- - An alarm detection scenario-

Added 25897 IP Excessive F - - - -

C210
Upgrade Description
Compatible with Change
Involve the NBI
the NBI Reason Upgrade Impact Preventive Measure
The alarm
reporting
mechanism
No N/A is optimized The value of Specific-
to improve
O&M
efficiency.
The alarm
detection
mechanism
No N/A is optimized If an alarm indicatin -
for improving
the O&M
efficiency.
This alarm
parameter is
added to
facilitate fault
Yes Yes When the IP frame err-
location and
improve
O&M
efficiency.
cription
Applicable Mode
Suggestion

Handle this alarm L

Handle this alarm L

Handle this alarm L

Alarm Changes
BTS3202E V100R011C10SPC210 Compared with BTS3202E V100R011C10SPC183
Modified the
following Change Description
Change Type Alarm ID Alarm Name Alarm parameters:
Location Alarm Generation and
Others
Severity 1.Information
Add the Clearance Mechanism
value of
parameter
Local Access
Type of the
Maintenance
Modified 26844 - device - -
Device
WLAN.
Abnormal
2. Add the
value of
parameter
Type of the
device SD
Card.
C183
Upgrade Description
Compatible with AnChange
alarm
Involve the NBI
the NBI Reason
parameter Upgrade Impact Preventive Measure
value is
added, and
therefore the
fault can be
Yes Yes - -
more
accurately
located and
the O&M
efficiency is
improved.
cription
Applicable Mode
Suggestion

Handle this alarm

with
recommended L
actions based on
system impact.
Alarm Changes
BTS3202E V100R011C10SPC183 Compared with BTS3202E V100R011C10SPC180
Change Description
Change Type Alarm ID Alarm Name Alarm Location Alarm Generation and
Others
Severity Information Clearance Mechanism
None None None None None None None
C180
Upgrade Description
Compatible with Change
Involve the NBI
the NBI Reason Upgrade Impact Preventive Measure

None None None None None

cription
Applicable Mode
Suggestion

None None
Alarm Changes
BTS3202E V100R011C10SPC180 Compared with BTS3202E V100R011C10SPC160
Change Description
Change Type Alarm ID Alarm Name Alarm Location Alarm Generation and
Others
Severity Information Clearance Mechanism
None None None None None None None
C160
Upgrade Description
Compatible with Change
Involve the NBI
the NBI Reason Upgrade Impact Preventive Measure

None None None None None

cription
Applicable Mode
Suggestion

None None
Alarm Changes
BTS3202E V100R011C10SPC160 Compared with BTS3202E V100R011C10SPC150
Change Description
Change Type Alarm ID Alarm Name Alarm Location Alarm Generation and
Others
Severity Information Clearance Mechanism
None None None None None None None
C150
Upgrade Description
Compatible with Change
Involve the NBI
the NBI Reason Upgrade Impact Preventive Measure

None None None None None

cription
Applicable Mode
Suggestion

None None
Alarm Changes
BTS3202E V100R011C10SPC150 Compared with BTS3202E V100R011C10SPC112
Change Description
Change Type Alarm ID Alarm Name Alarm The Location Alarm Generation and
alarm Others
Severity parameters
Information Clearance Mechanism
are modified
as follows:
The value
Cell
Modified 29240 - "other causes" - -
Unavailable
has been
added to the
Specific
Problem
parameter.
C112
Upgrade Description
Compatible with Change
Involve the NBI
the NBI Reason Upgrade Impact Preventive Measure
Values are
added for
Alarm
Parameters
of this alarm
Yes Yes - -
to accurately
locate faults
and improve
O&M
efficiency.
cription
Applicable Mode
Suggestion

Handle the alarm

according to the
impact of the
L
alarm on the
system in the
alarm reference.
Alarm Changes
BTS3202E V100R011C10SPC112 Compared with BTS3202E V100R011C10SPC100
Change Description
Change Type Alarm ID Alarm Name Alarm Location Alarm Generation and
Others
Severity Information Clearance Mechanism
Excessive
Added 26822 License - - - -
Usage
C100
Upgrade Description
Compatible with This
Change
alarm is
Involve the NBI When excessive lic
the NBI Reason
reported to al Upgrade Impact Preventive Measure
ense usage occurs,
ert operators
this alarm is not re
to excessive
Yes Yes ported before a ver
license usag
sion upgrade but is
e, thereby i
reported after a ver
mproving O&
sion upgrade.
M efficiency.
cription
Applicable Mode
Suggestion
Handle this alarm
with
recommended L
actions based on
system impact.
Alarm Changes
BTS3202E V100R011C10SPC100 Compared with BTS3202E V100R011C10SPC060
Change Description
Change Type Alarm ID Alarm Name Alarm Location Alarm Generation and
Others
Severity Information Clearance Mechanism

Cell RX
Channel
Interference
Added 29250 - - - -
Noise Power
Unbalanced
C060
Upgrade Description
Compatible with Change
Involve the NBI Before the upgrade,
the NBI Reason Upgrade Impact Preventive Measure
ALM-26522 RF Unit
The
RX Channel
detection
RTWP/RSSI
mechanism
Unbalanced is
of ALM-
reported if the
26522 RF
trigger conditions
Unit RX
are met. After the
Channel
Yes Yes upgrade, ALM- -
RTWP/RSSI
29250 Cell RX
Unbalanced
Channel
in the LTE
Interference Noise
mode differs
Power Unbalanced
from that in
is reported instead
other modes.
if the trigger
conditions are met
in the LTE mode.
cription
Applicable Mode
Suggestion

- L
Alarm Changes
BTS3202E V100R011C10SPC060 Compared with BTS3202E V100R011C10SPC050
Change Description
Change Type Alarm ID Alarm Name Alarm Location Alarm Generation and
Others
Severity Information Clearance Mechanism
None None None None None None None
C050
Upgrade Description
Compatible with Change
Involve the NBI
the NBI Reason Upgrade Impact Preventive Measure

None None None None None

cription
Applicable Mode
Suggestion

None None
Alarm Changes
BTS3202E V100R011C10SPC050 Compared with BTS3202E V100R011C10
Change Description
Change Type Alarm ID Alarm Name Alarm Location Alarm Generation and
Others
Severity The Downlink Clearance Mechanism
Information
Frequency
Cell PCI Modified
Extension the
Modified 29247 - following - -
Conflict Flag
parameters:
parameter is
Add the value
added.
IKE
of parameter
Modified 25891 Negotiation - - -
specific
Failure
problem
IPSec SA
Negotiation
Failure.
 Before the upgrade, Upgrade Description
Compatible with Band66
Changeis Downlink Frequency
Involve the NBI
the NBI supported.
Reason Extension
UpgradeFlag is
Impact Preventive Measure
Thealarm
An not in the alarm
EARFCNs
parameter in location information.
Yes Yes ALM-29247
value is After the upgrade, -
Cell PCIand
added, Downlink
Conflict are
therefore the Frequency
modified
fault can be Extension Flag is
Yes Yes accordingly. -in the alarm location -
more
accurately information.
located and
the O&M
efficiency is
improved.
cription
Applicable Mode
Suggestion

- L

Handle this alarm

with recommended
L
actions based on
system impact.
 n to
Incorrect
frequency
configuratio
n.
Alarm Changes 4. The value
BTS3202E V100R011C10 Compared with BTS3202E of the V100R010C10SPC220
specific Change Description
Change Type Alarm ID Alarm Name Alarm problem Locationis Alarm Generation and
Others
Severity changed Information Clearance Mechanism
from The alarm detection
Base Station
Modified 25950 Being - Abnormal
-
mechanism is optimized
-
RF module for the flood attack of LTE
Attacked
to RF control-plane
The alarm detectionprotocols.
The alarm mechanism has been
RF Out of module
parameters
Modified 29248 - -abnormal. optimized: The alarm is -
Service are modified reported when an RRU
5.
as The value
follows: object is removed.
of
The the
value of
Cell
Modified 29240 - Specific
specific - -
Unavailable
Problem
problem is is
optimized
changed in
RF Out of The certain
from Fault
Modified 29248 - - -
Service severity of scenarios.
on the BBP
this alarm
to Baseband
is
changed equipment
X2 Interface
Modified 29204 - - -
Fault abnormal.
from
eNodeB S1 "Major" to 6. The value
Control Plane "Warning. of the
Added 29213 - -specific - -
Transmission " The mechanism for
Interruption problem is reporting and clearing this
S1 Interface
changed alarm is optimized to
Modified 29201 - -from Clock become compatible with -
Fault
resource ALM-29213 eNodeB S1
The Local is Control Plane
not usable
Description
Modified 29201
S1 Interface
- to Clock not Transmission
alarm -
Interruption.
-
Fault usable. is
parameter
7. Added the
added.
M1 Interface The mechanism for
Added 29223 eMBMS - value
- The - -
reporting
The this alarm
mechanism for is
Session Loss BBP optimizedthis
reporting to indicate
alarm isa
capability is optimized
failure to set up an S1a link
to indicate
S1 Interface insufficient fault because
of anthere
SCTP is link
a license
that
Modified 29201 - -to the -
Fault limit on an
carries S1-flex, RAN
eX2 interface
parameter Sharing
when thewith Common
specific Carriers, RAN Sharing
BASED_ON_EX2_NON_I
The blacklisted
SCTP Link with Dedicated Carriers,
Modified 25888
Fault
- -problem. DEAL_MODE
neighboring type is or
celloption -
8. Added the Hybrid
under
added. RAN
the
This Sharing.
alarm is
value eX2DynBlackListSwitch
reported when the PCI
Cell PCI Alarm parameter
conflicts is selected
between and
Modified 29247 - -External link the BackhaulType -
Conflict parameters blacklisted neighboring
fault to the parameter is set to
X2Interface
Modified the cells or between a
parameter NON_IDEAL(Non-Ideal
blacklisted neighboringand
ID, CN
following The alarm generation
X2 Interface specific Backhaul).
cell and a common
Modified 29204 _ Operator ID, clearance
parameters: mechanism is _
Fault problem. neighboring cell.
and the value improved.
Add
Board 9. Added the
Description
of parameter
Software Added
value
are the
no longer
Modified 26254 - Possible - -
Synchronizatio following
Incorrect
used.
Cause
n Failure
Automatic parameters:
cell
Automatic
Modified 26255 Version - 1. Detail of
recovery - -
networking
Rollback Information.
hot patches
to
2. the
Rollback
failed.
parameter
Version.
specific
problem.
10. Added
the value RF
Link
 1.An alarm detection
scenario is added:
the configuration of the
Modified the base station clock
The
following synchronization mode or
value of
parameters: frame synchronization
the Alarm
Add the value switch is incorrect.
External Clock Level is
of parameter 2.For scenarios in which
Modified 26262 Reference changed Modified the -
specific
following SYNCETH clock quality
Problem from
problem levels are unavailable, the
Minor to parameters:
Abnormal
1. The value alarm detection
Major/Min
Peer
of theSystem mechanism is optimized.
or.
Clock.
Certificate 3.An alarm detection
Base Station Type is scenario is added: clock
Frame changed from desynchronization
Added 26265 Number - CRL
- to interference.
- -
Synchronizatio The Added the
CERTWHITEL
n Error on following
STFILE. 1. The time switch validity check
controlling
License value of
Modified 26817 - parameters:
2. Add the -mechanism
is added to the certificate
is optimized -
Trial the Alarm Grace Period
value
Modifiedof the validity
for check
reporting
1. The reporting for
this files
alarm. of
Level is Modified
Expire Date.the
Certificate parameter trust
2. The certificates.
reporting
Modified 26841 changed following
following mechanism of this alarm is -
Invalid Certificate
parameters: 2. The dateforvalidity
mechanism
optimized ofthe checkis
thisscenario
alarm
from parameters:
Modified the
Type
1. The CRL.
value is added
optimized
where for
for
ALM-25888 the
the device
scenario
SCTP
Major to Delete the
Modified 25886 IP Path Fault -Major,Sug following
3.
of Add
the ofthe
Service certificate
where
Link referenced
ALM-25886
Fault is by
IP Path -
value
parameters:
value of the IKEPEER MO.
gestion. Type is Fault and
simultaneously
1. The reportingALM-29204 reported X2
parameter
1. The value
parameter
SCTP Link changed Interface
from with Fault
ALM-29201
mechanism are
of this S1alarm is
Modified 25888 - Service
of the
specific Type
Service -
Fault NULL
Modifiedto uX2-
the reported
Interface
optimized simultaneously.
Fault
in or
scenariosALM-
M1.
Type
problemis Not The alarm correlation with
AP.
following
Modified the 3. The aX2
29204 restriction
Interface. onpath
the
SCTP Link changed
Exist.
2. Add thefrom where
the
number
2. The
user-plane
following
that
alarm alarm
this alarm
reporting is is is
Modified 25889 - parameters:
following -
Congestion NULL
4. Add
value to
the
of uX2- faulty.
added:
reported
The
mechanism ALM-25888
is
reporting lifted.
is mechanism
optimizedSCTPin
Add
AP. the
parameters:value 2. The
Link switch controlling
Fault.
Base Station value of of this alarm
Modified 25950 Being -
parameter
of
1.
2. parameter
Delete
Add the the scenarios
mechanism
- isisoptimized
where modified:
the eX2
-
parameter
Service Type Before
Interface the upgrade,
Backhaul this
Type
specific
value
value of
of for reporting this alarm.
Attacked specific alarm
NULL.
Modified
problem
parameter
parameter
the 3. Theisreporting
parameter reported
is set to when
IDEAL.the
User Plane problem
following
Source MAC total number of ALM-
Modified 25952 - Service
Service Type
Type mechanism of this alarm is -
Path Fault Revoked.
parameters:
Address 25886 IP Path fault and
M1.
Added
NULL. the optimized for the scenario
1.
2. The
Attack.
Add value
the ALM-25952
where ALM-25952User Plane User
User Plane following
Modified 25954 - of Service Path
the of
value PlaneFault Pathexceeds
Fault and 16; -
Fault parameters:
Type is
parameter After
ALM-29204the upgrade, this
SCTP Link IP Service Type. 1. The alarmX2 Interface
detection
changed
Service Typefrom alarm
Fault
mechanism
is reported
are reported when the
is optimized
Modified 25955 Address - -total number of ALM- -
NULL
uX2. to uX2- simultaneously.
for the chip soft failure.
Unreachable 25886 IP Path fault
DNS AP. 4.
2. The restriction
alarm detection onandthe
Added 25958 Resolution - 2.
- Add the ALM-25952
-mechanism
number User
that isthis Planeis -
alarm
added for
Failure value of Path Fault
reported is exceeds
lifted. 16 for
Board the problem that the BRU
parameter the same service type.
Modified 26200 Hardware - -Service Type is reset repeatedly in a
Fault short period of time. -
NULL.
 Upgrade Description
Compatible with Change
Involve the NBI
the NBI Reason Upgrade Impact Preventive Measure

The Before the upgrade,

No N/A correlation this alarm is not -
detection generated when
mechanism LTE control-plane
The alarm
between Before
protocols theare upgrade,
under
No N/A detection
alarms has this
flood attack. not
alarm is The -
mechanism
been generated
alarm is generated when an
has been to
optimized RRU object
after theand is
upgrade.
The alarm to
optimized Before
removed. The after alarm the
Yes Yes improve O&M
parameter upgrade, the -
make the
efficiency. is generated after
values
alarm have Specific
the upgrade Problem when
been
locating more parameter
an RRUand changes
object isthe
The alarm
optimized to Before
in certain scenarios. after
Yes Yes accuracy,
parameter removed.
upgrade, the -
make the
improving the
values
alarm have Specific Problem
O&M
been parameter changes
locating
The
efficiency.more
severity Before thescenarios.
upgrade,
optimized
accuracy, to in certain
Yes Yes of this
make alarm
the the severity of this -
improving
has been the alarm is "Major."
alarm
O&M
modified
locating to
more After the upgrade,
This alarm
efficiency.
improve After the upgrade,
the severity of this
Yes Yes accuracy,
has been this alarm is -
alarm
improving alarm is "Warning."
added
accuracy.to the reported when the
O&M
improve O&M status of all the
The alarm
efficiency. Before
SCTP links the upgrade,
(no
No N/A detection ALM-29213
fewer than two) eNodeB that -
mechanism S1 Control
carry S1 interfaces Plane
has been Transmission
in an eNodeB is
The alarm to
optimized Before
Interruption the upgrade,
does
Yes Yes parameter abnormal.
no Local This -
improve not
alarm exist. After the
is cleared
has
alarm been Description
upgrade, ALM- alarm
added to when
parameter
1.When thethe status
is NE of
reporting
This alarm 29201
Before
an SCTP S1
thelinkInterface
upgrade,
that
improve
accuracy. available.
detects
Fault is an thatAfter
cleared the
the for
Yes Yes has
alarm been this
carriesalarm
upgrade, is
S1not
the Local -
added current
all S1 version
interfaces is
locationto reported
interface
Description
improper
when
when
becomes
and
ALM-29213
the
alarm
improve
accuracy. O&M eNodeB
normal
parameter anddetects
is the that
The alarm
efficiency. Before
performs
eNodeB
SYNC the an
S1
packets upgrade,
Controlare
No N/A detection status
available.
this alarm
automatic remains is not
version -
Plane
lost
normal for Transmission
an
for evolved
90alarm
mechanism reported
rollback,
Interruption
multimedia when
this is an
has been seconds
S1
is link
not (default
fails
reported to be
The alarm to reported.
broadcast/multicast
Before
value). the ALM-upgrade,
optimized set
before
29201 up
service because
a
S1 version
Interface
(eMBMS)
No N/A detection
improve no
theredynamic
is aover eX2
license -
rollback
Fault
session will but
be is the M1
mechanism
alarm blacklist
limit function
on S1-flex, is
reported
reported
interface. after
again
After athe
for a
has been
reporting available.
1.When
RAN SharingtheAfter the
with
This alarmtois version
After
faulty the rollback.
upgrade,
interface
this alarm after
optimized
accuracy. upgrade,
software
Common the
of aU2000
Carriers,
No N/A reported 2.When
this alarm
ALM-29213
is reported the iswhen
eNodeB the -
improve eNodeB
secondary
RAN
links down
Sharing checks
board
or the
with
when
alarm the PCI reported
S1 Control
eNodeB
whether when
an Plane
detects
SCTP the that
component
Dedicated
system resets fails
Carriers, to
conflicts
Value is
reporting
The alarm
PCI
link
Before
conflicts
Transmission
the number
that thecarries of after
version an
between be
or activated,
upgrading
Hybrid RAN
the this
hot
Yes Yes added
accuracy.
detectionfora between
Interruption
SYNC
eX2
upgrade,interface blacklisted
packets
this isalarmlost
meets -
blacklisted alarm
Sharing.
patch
neighboring
cleared. is not
and After
performs the or
cells
Alarm
mechanism is for
the
is an
reportedeMBMS
dynamic wheneX2
neighboring reported
upgrade,
an automatic
between before
athis alarm
hot a
Parameters
optimized to session
blacklist
each X2 over
conditions
interface the M1
is
cell and a version
is reported
patch
blacklisted upgrade
version with but
the
of this
This alarm
alarm
increase the interface
within
faulty. the
Alarm exceeds a
Yes Yes common is reported
Specific
rollback,
neighboring after
Problem
this alarm
cell a
and -
to accurately
parameter
alarm is specified
measurement
parameters threshold.
neighboring version
alarm
is
a not reported
common upgrade.
parameter
locate
added
reportingfaults
to period
X2Interface of about ID, 2CN
cell. Thisfault 2.If
being
beforeautomatic
neighboring License
a hot hot
patch
cell.
Yes Yes and improve
facilitate
accuracy. minutes
Operator if the
ID, -
improves
O&M and
patch
limitedrecovery
rollback in
but the isand of a
location following
Description
board fails, conditions
nocan
alarm
efficiency. preceding
reported scenario.
after aalarm
hot
improve O&M are met:
identify specific
reporting is reported
After
patch the S1before
rollback. linkX2 for
efficiency. The link
interfaces.
the upgrade fails to be
but this
accuracy and which
3.When thethe alarm is
set
After
alarm upthe
reported isupon
configuration version
reported
is the first
of the
O&M setup attempt.
efficiency. upgrade,
after isthe
removed,
NE modifiedthis
upgrade.
or the alarm
and
The
is generated
license
leads tolimit
the is baseno
BASED_ON_EX2_
depending
longer imposed
station on the
satisfying tothe
NON_IDEAL_MOD
specific
allow the S1
condition X2 ofinterface
link
 enabled
clock quality or if level
the
added for setting of link
configured on GTP-the
supporting U
NEstatic detection
is unavailable
frame switch follows that
and ALM-25880
synchronizati of the global GTP-U
Ethernet Link Fault
on and static detection
is reported, no
improving switch
alarm isand the latter
reported
O&M is enabled.
before the upgrade
efficiency. 2.
butIfthis
1.After thethe X2(X2)
alarmupgrade,is
2. The alarm check box is
reported
this alarm after
is the
detection selected under
upgrade.If
reported when the athe
scenario is Service Interface
SYNCETH
trust certificate clock or a
Yes Yes optimized for Alarm Configure -
quality level
device certificate
improving Switch parameter
configured on
by the
fault reporting referenced
in the
NE
IKEPEERis unavailable
MO
accuracy
1.The alarm and ENODEBALMCFG
and
expires.the SYNCETH
O&M
reporting 1.If
MO, aALM-25886
cross-R-
clock
2.This isalarm the is IP
mechanism is 1.
efficiency. Before
version upgrade
Path
reported
upgrade, Fault
reconfigured with
with
this after
alarmis
To
3. support
The
modified, alarmand occurs, this alarm
Service
being
Certificate
is reported Type
removed, Type
when being
no the
GUL
detection the not
therefore reported before
This alarm X2
alarm
being will is
corresponding be masked.
reported fault
Yes Yes maintenance,
scenario is
O&M - version upgrade
a -
3. When if the number
parameter
this
added alarm
efficiency to is isis before
CERTWHITELSTFI
occurs
but
the
is reportedtheupgrade
global
after
added to of
but
LE this
this
and alarm
alarm
Alarm is
added.
facilitate
improved.
The invalid fault GTP-U
a version
reported
static
upgrade.
on a board
Yes Yes facilitate
Alarm fault detection
Severity the after
being
switch theis -
identification
2.To
alarm addand the 2.When
reaches 32, license
this
location
parameter upgrade.
Suggestion
enabled. Afterwhen the
and improve
whitelist
parameter is file
alarm expires, notthis
willalarm be
improveare
values O&M 3.
the Iffollowing
upgrade,this this is
alarm
Yes Yes the O&M and alarm
filtering
removed reported is notbefore the -
Alarm
efficiency.
optimized conditions
is reported are
when met: the
efficiency.
function
the alarm reported
upgrade before
but will astill
parameter
and the alarm 1) The
corresponding and
IKE clock
fault
when
reporting digital version
aare be reported upgrade after but
Yes Yes values
reporting desynchronization
verification
occurs
is reported if theafterlink athe
switch is -
certificate
mechanism
optimized is is upgrade.
interference occurs
mechanism enabled
GTP-U
is version upgrade. by
static running
used
modified,
and foralarm
the IKEand after the CERTCFG
upgrade,
optimized, the SET
detection switch is
Yes Yes negotiation,
Alarm
therefore the 1.
reporting Before
-enabled
the severity the -
and therefore If the
command. number or ifofthe
ofthis
the alarm is After
parameter
O&M
mechanism upgrade,
alarm
the upgrade,
is this
changed alarm
the faultarecan IKEv2
2) The
setting redirections
current
of link GTP-base
parameter
values
efficiency
optimized, is this is
from
exceeds
station
U
alarm
reported
minor
static
iswhen
the
does to
not
detection major
IKEv2
not the
Yes Yes be more
added,
and alarm
optimized
improved. and reported when ALM- -
and therefore switch baseband
after the chip
upgrade.
in redirection
accurately have
25888 an SCTP DOS
activated
follows that
Link
A scenario
therefore
severity
and are
the alarm the When
experiences the total aGTP-U
soft
the fault
located can
and attack
certificate
of the threshold
global whitelist in
which
fault can
modified.
reporting thisbe Fault number
failure. isAfter
reported.
of IP thepath
Yes Yes be
An
the more
alarm
O&M 300
file.
static consecutive
detection -
alarm
more
mechanism is is upgrade,
faults and user-
this alarm
accurately
parameter
efficiency isis seconds,
3) After
switch and this
one the alarm
hour,
latter
reported
accurately
optimized, is plane
is path
reported faults
when the
located
added,
improved. and
and the
is not
EMS reported
enabled. still does
Yes Yes Alarm
added
located
and so
and
therefore that exceeds
baseband 16,
chip both -
the O&M the 2.
is before
therefore
parameter notThe the upgrade
download
Service and
this
the alarmcan
O&M
fault ALM-25886
experiences IP Path
a soft
efficiency
fault
values can beis but is
activate
Interface reported
a valid
Alarm after
be moreareis failure
reported
efficiency
improved. Fault
the and and
upgrade. ALM-
its self-
Yes Yes more
optimized,
when
improved. the digital
Configure
If the DNS certificate
Switch
client -
accurately 25952 User
accurately
and
DNStherefore
client
healing
whitelist
parameter
initiates isPlane
fails.
file.
domain added
located and 2. PathWhenFault theare BRU is
located
the fault
initiates and
can to
namethe resolution to
Yes Yes the O&M reported
reset
-ENODEBALMCFG before the
repeatedly in a -
the
be O&M
more
domain name
efficiency is short the DNS server and
upgrade period but only
of time,
efficiency
improved. is
accurately
resolution to MO. a Whenname
domain
this alarm is
X2(X2)
not fails
Yes Yes improved.
located
the DNS and under
to be this
resolved, switch thisis -
reported
selected, instead
before
ALM- the
the O&M
server and a upgrade alarm
after the is notupgrade.
andPlane is
efficiency
domain nameis 25952 reported
reported
Userbefore
after the the
improved.
fails to be Path
upgradeFault butwithis
No N/A The alarm deteupgrade. -
resolved, and Service reported Type after the being
therefore the upgrade. X2-AP is masked.
alarm can be 3. When the number
more of this alarm
accurately reported on a board
reported and reaches 32, this
O&M alarm will not be
efficiency is reported before the
improved. upgrade but will still
be reported after the
upgrade.
cription
Applicable Mode
Suggestion
Handle the alarm
according to the
impact of the
GUL
alarm on the
Handle thethe
system in alarm
according to the
alarm reference.
impact of the
L
alarm on the
Handle thethe
system in alarm
according to the
alarm reference.
impact of the
L
alarm on the
Handle thethe
system in alarm
according to the
alarm reference.
impact of the
L
alarm on the
system in the
alarm reference.
- L
Handle this alarm
according to the
instructions in the L
alarm reference for
the eNodeB.
- L

- L

- L

- L

- L
Handle this alarm
based on the
impact on the
L
system as
described in the
alarm reference.
- L
Handle this alarm
with recommended
L
actions based on
Handle this alarm
system impact.
with recommended
L
actions based on
system impact.
Handle this alarm
with recommended
L
actions based on
system impact.

- L
Handle this alarm
with recommended
L
actions based on
Handle this alarm
system impact.
with recommended
L
actions based on
Handle this alarm
system impact.
with recommended
L
actions based on
Handle this alarm
system impact.
with recommended
L
actions based on
Handle this alarm
system impact.
with recommended
L
actions based on
Handle this alarm
system impact.
with recommended
L
actions based on
Handle this alarm
system impact.
with recommended
L
actions based on
Handle this alarm
system impact.
with recommended
L
actions based on
Handle this alarm
system impact.
with recommended
L
actions based on
Handle this alarm
system impact.
with recommended
L
actions based on
system impact.
L
Handle this alarm
 1. The value
of the specific
problem is
changed from
Incorrect
Alarm Changes bandwidth When the Distance based
configuratio
BTS3202E V100R011C10 Compared with BTS3202E inter-RAT handover to
V100R009C00SPC280
n to GERAN(FDD) and
Change Description
Distance based inter-RAT
Incorrect
Change Type Alarm ID Alarm Name Alarm Location handover to UTRAN(FDD)
Alarm Generation and
cell license itemsMechanism
are Others
System Severity Information Clearance
bandwidth unavailable and the
Dynamic configuratio distance-based handover
Modified 26812 Traffic - -n. After the faultstarget in the object -
measurement
Exceeding SCTP
2. The value type is set to EUTRAN, link of an S1
Licensed Limit interface are rectified,
of the the mechanisms for
S1 Interface ALM-29201
reporting andS1clearing
Interface
Modified 29201 - -specific After the faults in the -
Fault Fault
ALM-26812with the Specific
problem is SCTP
Problem ofSystem
linkalarm anparameter
S1
changed Dynamic
interface Traffic
are Exceeding
rectified,
set to Lower-layer
Licensed Limit link fault
X2 Interface The value ALM-29204 X2areInterface
Modified 29204 - -from
1. is cleared.
optimized. -
Fault Incorrect RS In
Physical Fault
thewith
combinedthe Specific
RRU
resource fault Problem
scenario, alarm
if one parameter
RRU is
power
of the Specific set to Lower-layer
unavailable, linkRF
only the fault
Modified 29243
Cell Capability
-
configuratio
-Problem alarm In is cleared.
Unit Service Unavailable -
Degraded the CA group scenario,
n to alarm is reported. andThe Cell
System parameter is the generation
Incorrect Capability
clearance Degraded
mechanism alarm
of
Dynamic divided into
power
RF module is noSystem
the
When longer
all the reported.
Dynamic
LTE FDD or
Modified 26812 Traffic - -configuratio -
abnormal and Trafficcells
TDD Exceeding
are deleted,
Exceeding n.
Baseband Licensed
ALM-26819 LimitDataalarm is
Licensed Limit
Data When the forCDMA
3.
equipmentThe value improved
Configuration CA-related
Exceeding
Configuration optimization
license. Limit switch on the
Modified 26819 - -of the
abnormal.2. Licensed that is -
Exceeding eNodeB is turned on,
specific
The value reported because the data
Licensed Limit reported ALM-26819
Data Incorrect
problem is configuration exceedsData the
Configuration
limit of the Exceeding
corresponding
Configuration settings of
Modified 26819 - -changed Licensed
license item Limit is cleared
is cleared. -
Exceeding cell-level
from after the license file
Licensed Limit parameters
Incorrect of containing the license item
the Specific for E-UTRAN-to-
Modified 29240
Cell
-
EARFCN
Problem alarm -CDMA2000 hanover is -
Unavailable configuratio
parameter is loaded.
n to ALM-
changed
Added to
eNodeB Out Incorrect
Invalid
29249
Added 29249 - frequency
parameter - -
of Service eNodeB Out
configuratio
setting.3.
of Service.The
values The alarm detection
Base Station n.
License mechanism is optimized
Modified 25950 Being - -4. The value -
limitation for the flood attack of LTE
Attacked of the and The control-plane
alarm detection protocols.
multi-mode
specific
license mechanism has been
RF Out of
Modified 29248 - -problem is
limitation of optimized: The alarm is -
Service changed
the Specific reported when an RRU
from object isthe
Problem alarm Added removed.
correlation
Modified 29248
RF Out of
-
Abnormal
parameter
- for between this alarm and
-
Service alarm are ALM-26200 Board
RF module
this
to RF
combined Hardware Fault.
The alarm into Added the correlation
Cell Insufficient
module
parameters between this alarm and
Modified 29240 - -license.
abnormal. -
Unavailable are modified ALM-26200 Board
5. The
as value Hardware Fault.
follows:
of
The the
value of
Cell
Modified 29240 - Specific
specific - -
Unavailable
Problem
problem isis
optimized in
changed
RF Out of certain
from Fault
Modified 29248 - scenarios. - -
Service on the BBP
to Baseband
equipment
abnormal.
6. The value
of the
 The
severity of
this alarm
is
X2 Interface
Modified 29204 changed - - -
Fault
from
eNodeB S1 "Major" to
Control Plane "Warning.
Added 29213 - - - -
Transmission " The mechanism for
Interruption reporting and clearing this
alarm is optimized to
S1 Interface
Modified 29201 - - become compatible with -
Fault
ALM-29213 eNodeB S1
The Local Control Plane
Description Transmission Interruption.
S1 Interface
Modified 29201 - alarm - -
Fault
parameter is
added.
M1 Interface The mechanism for
Added 29223 eMBMS - - -
reporting
The this alarm
mechanism for is -
Session Loss optimizedthis
reporting to indicate
alarm isa
failure to set
optimized up an S1a link
to indicate
S1 Interface because
fault of anthere
SCTP is link
a license
that
Modified 29201 - - -
Fault limit on an
carries S1-flex, RAN
eX2 interface
Sharing
when thewith Common
Carriers, RAN Sharing
BASED_ON_EX2_NON_I
The blacklisted
SCTP Link with Dedicated Carriers,
Modified 25888
Fault
- - DEAL_MODE
neighboring type is or
celloption -
Hybrid
under the
added. RAN Sharing.
This alarm is
eX2DynBlackListSwitch
reported when the PCI
Cell PCI Alarm
Modified the parameter
conflicts is selected and
between
Modified 29247 - - the BackhaulType -
Conflict parameters
following blacklisted neighboring
X2Interface
parameters: parameter
cells is set to
or between a
ID,Add
1. CN the NON_IDEAL(Non-Ideal
blacklisted
The neighboringand
alarm generation
X2 Interface Backhaul).
cell and a common
Modified 29204 _ Operator
value of ID, clearance mechanism is _
Fault neighboring cell.
and
parameter improved.
An alarm detection
Description
Possible scenario is added:the
Board are no longer
Cause heartbeats of the slave
Modified 26203 Software - -used. -
Secondary core on an LMPT are lost
Program Error
Board for 5 minutes,then this
Board alarm is reported.
Component
Software 1.An alarm detection
Modified 26254 - Software - -
Synchronizatio Added the scenario is added:
Activation
n Failure following the configuration of the
Failure.
Automatic parameters:
Modified
2. Add thethe base station clock
Modified 26255 Version -The 1. Detail
following
value of the -
synchronization mode or -
Rollback value of Modified
Information.
parameters:
parameter frame synchronization
the Alarm following
2. Rollback
Add the value
Possible switch is incorrect.
External Clock Level is parameters:
Version.
of parameter
Cause 2.For scenarios in which
Modified 26262 Reference changed 1. The value -
specific
Automatic SYNCETH clock quality
Problem from of the
Base Station Minor to problem
recovery of levels are unavailable, the
Frame Certificate
Abnormal alarm detection
Major/Min hot
Type patches
is
Added 26265 Number -or. Peer
-failed.System mechanism
- is optimized. -
Synchronizatio changed
Clock. from 3.An alarm detection
n Error Added
CRL tothe scenario is added: clock
following
CERTWHITEL desynchronization
License on
Modified 26817 -The parameters:
STFILE. -interference.
1. The time validity check -
Trial value of Grace
2. Add thePeriod is added to the certificate
the Alarm ExpireofDate.
value validity check for files of
Level is
Certificate parameter trust certificates.
Modified 26841 changed -
Invalid Certificate 2. The date validity check
from
Type CRL. is added for the device
Local Access Major to 3. Add the certificate referenced by
Maintenance Major,Su value of the
Added 26844 -ggestion. - - IKEPEER MO. -
Device parameter
Abnormal specific
problem Not
Exist.
4. Add the
value of
 following
parameters:
The
Parameter
meaning of
Configuration the
Modified Receive the
Added 26247 - -following
Bc. Packets - -
Failure
Per Sec. is
parameters:
Ethernet Port The method of measuring
changed
1. The value from
Broadcast Modified the the average number of
Average
of the Service
Modified 25879 Packets - following receive broadcast packets -
number
Type is of
Exceeding parameters: onThe
1. an Ethernet port is
switch controlling
broadcast
changed from
Alarm
MAC Added
1. The the corrected.
mechanism is optimized
Excessive
packets
RSL
following tovalueper
GSM for
Modified 25881 - of
second the Service
Modified
Signaling the - reporting this alarm. -
Frame Error parameters:
Type
Modified
within is30s the 2.
1. The reporting
Rate following
Link.
Trunk No..
changed
following
after
parameters:this from mechanism of this alarm is
2. The value
RSL to
parameters:
alarm
Delete isGSM
the optimized for the scenario
Modified 25886 IP Path Fault - of the Service ALM-25886 SCTP IP Path -
Signaling
The
reported where ALM-25888
value
Type isof to FaultFault
and ALM-29204 X2
Link.
Parameter
Average from
parameter Link is
changed Interface Fault are
2.
meaning
number
ServiceThe to value
of
of
Type simultaneously reported
NULL eX2- reported simultaneously.
SCTP Link of
the the
broadcast
M1. PeerService
IP with ALM-29201 S1
Modified 25888 - AP. 3. The restriction -
Fault Type
Address is Interface Fault or onALM-the
3. Add theis
Packets
numberX2 that this alarm is
changed 29204 Interface.
received
value of from
in a The alarm is correlation
NULL
Peer
second IPto eX2- reported
2. The alarm reportingwith
lifted.
SCTP Link parameter the following alarm is
Modified 25889 - AP.
address
among to 30 mechanism is optimized in -
Congestion Servicethe Type added:
3.
Peer
secondsAdd IP the scenarios where theSCTP
ALM-25888 eX2
So-AP. Link Fault.Backhaul Type
value Interface
IKE 4. Addof
address
before
Modified
(If
the
thethe
parameter
IKE
alarm of
Modified is the parameter is set to IDEAL.
Modified 25891 Negotiation - value
following - -
Service
redundancy
generated.
following
parameter Type
Failure parameters:
So-AP.
backup
parameters:
Service Type 1. The reporting
1.
4.
becomesAdd
Add the
thethe The reporting mechanism
IP PM 1. Delete the mechanism
Modified
uX2-AP.
value
value
invalid ofduring
of of this alarmof is this alarm is
optimized
Modified 25900 Activation - -following
value
5. Add the of optimized in scenarios -
parameter
parameter
IPSec in scenarios where the
Failure parameter where
parameters:
value
specific
Service
redirection,
of
Type DSCP a user-plane
value path is
is modified.
Base Station Service
1. The
parameter
problem Type
value
DOS faulty.
uX2-AP.
the
M1.
of IP
the
Service Service
Type 2. The switch controlling
Modified 25950 Being - Attack. -The reporting -
Attacked
5.
Type
NULL.
2.
Addisthe
address
2. Add
Add
thein
the is mechanism is mechanism
optimized
value
the
value of
alarm
of of this alarm
for reporting thisis modified:
alarm.
changed
value of from Before the upgrade, this
parameter
peer
parameter
RSL IP
to GSM 3. The reporting
User Plane parameter alarm is reported
Modified 25952 - Service
addresses
Service
Signaling
specific
Type
Type mechanism of thiswhen
alarmthe
is -
Path Fault NULL.
configured total number of ALM-
uX2.
Link.
problem optimized for the scenario
by
3. the value
Add master
the 25886 IP Path faultUser
where ALM-25952 and
2.
SourceThe MAC ALM-25952 User Plane
User Plane IKEPEER.).
value
of of
the Service Plane Path Fault and
Added 25954 - Address
-parameter Path Fault exceeds 16; -
Fault Type
Attack. is ALM-29204 X2 Interface
Service Type After the upgrade,
Fault are reported this
changed from alarm is reported when the
SCTP Link IP eX2. to eX2-
NULL simultaneously.
4. total number of ALM-
Modified 25955 Address - AP.Add the 4. The restriction
-25886 IP Path
on the
fault andis -
Unreachable value
3. Addof the number that this alarm
parameter ALM-25952 User
reported is lifted. Plane
value of Path Fault exceeds 16 for
DNS Service Type
parameter
Added 25958 Resolution - -Service
X2&eX2.Type the
- same service type. -
Failure So-AP.
4. Add the
Board Memory value of
Deleted 26201 - - - -
Soft Failure parameter
Board Flash Service Type
Available uX2-AP.
Deleted 26209 - -5. Add the - -
Space
Insufficient value of
Board parameter
Configuration Service Type
Deleted 26243 - - - -
Data NULL.
Ineffective
ESN Read
Deleted 26102 - - - -
Failed
 1. The alarm detection
mechanism is optimized
for the chip soft failure.
Board
2. The alarm detection
Modified 26200 Hardware - - -
mechanism is added for
Fault
the problem that the BRU
is reset repeatedly in a
short period of time.
 when the Distance
based inter-RAT
handover to
GERAN(FDD) and
Distance based
inter-RAT handover
to UTRAN(FDD)
license items are
unavailable and the Upgrade Description
Compatible with TheChange
alarm
Involve the NBI distance-based
Before the upgrade,
the NBI detection
Reason Upgrade Impact Preventive Measure
handover
after the faults in the
mechanism
measurement
SCTP link of an target
S1
has been
The alarm to object type
interface areis set to
No N/A optimized Before the upgrade, -
detection EUTRAN,
rectified, ALM-
ALM-
increase the after the faults in the
mechanism 26812 System
29201 S1 Interface
alarm SCTP link
has been
reporting
Dynamic
Fault the X2
withTrafficof an
No N/A The alarm to
optimized interface
Exceeding
Specific are Licensed
Problem -
accuracy.
detection rectified,
In theisparameterALM- set
combined
increase the Limit
alarm mistakenly
mechanism
alarm 29204
RRU
reported.
to X2After
scenario,
Lower-layer Interface if
the
link
has been Before
Fault
one RRUwiththeis upgrade,
the
reporting
The alarm to upgrade,
fault ALM-
may persist.
No N/A optimized if ALM-29240
Specific
unavailable Problem Cell
before -
accuracy.
detection 26812
After
Before the System
the upgrade,
upgrade,
increase the Unavailable
alarm
the parameter
upgrade, with
the the
set
RF
mechanism Dynamic
this
when alarm
the Traffic
is cleared
CDMA
alarm Specific
to
UnitLower-layer
Before Service Problem
the upgrade, link
has been Exceeding
in the preceding
optimization Licensed
switch
reporting
The alarm to alarm
fault may
Unavailable
when parameter
all persist.
the and
LTE set
No N/A optimized Limit
scenario.
switch willon not
the be -
accuracy.
detection to
Cell
FDD Physical
After the
Capability
or TDD resource
upgrade, cells
increase the mistakenly
eNodeB isis reported
turned
mechanism fault
this
Degraded
are is reported,
alarm
deleted, cleared
alarms
ALM- the
alarm in
on the
and preceding
the license
has been Specific
in
are the
26819 reported. Problem
preceding
Data After
reporting
The alarm to scenario.
on
No N/A optimized
accuracy. - the
alarm
scenario.
the eNodeB
parameter
upgrade,
Configuration onlywill -
detection
increase the expires
be set toor
the Cell CapabilityRFthe module
Exceeding Licensed
mechanism
alarm license
abnormal
Degraded fileor on theis
alarm
Limit may persist,
has been eNodeB
reporting
The alarm to and the does not
Baseband
reported.
No N/A optimized
accuracy. contain
equipment the license -
detection corresponding
increase the item
abnormalfor E-UTRAN-
after the
mechanism license item cannot
alarm to-CDMA2000
upgrade.The value
has been be queried by
reporting hanover,
Incorrect reported
settings
No N/A optimized to running the CHK of -
accuracy. ALM-26819
This alarm
increase the DATA2LIC Data
cell-level
Before the upgrade,
has been Configuration
parameters
this alarm isAfter
command. of
not the the
alarm
optimized Exceeding Licensed
reporting to Specific
upgrade,Problem
reported when
this all
alarm
Yes Yes improve Limit isparameter
not incleared
accuracy.the alarm
cells are
is cleared abnormalthe in -
alarm after
ALM-29240
and a
the license
base
preceding scenario. Cell file
station
This alarm
locating containing
Unavailable this item
works in single
has
The been is loaded. After
capability. reported
mode. Afterbefore the the the
Yes Yes added to
correlation Before
upgrade,
upgrade the upgrade,
isreported
changed -
if the
improve O&M
detection this alarm
ALM-26819
to Invalid is Data
not
The alarm switch for parameter
reporting
efficiency.
mechanism generated
Configuration
setting after whenthe
detection ALM-29249
Assume that eNodeB
both
between LTE
Before control-plane
Exceeding
upgrade.The
Out of the
Service upgrade,
Licensed
value
isOut on,
No N/A mechanism ALM-29248 RF -
alarms has protocols
this
Limit
License
this alarm
is cleared
alarm are
is
limitation
is notunder
in or
has
beenbeen of Service
flood attack. and ALM-
The an
generated
the preceding
multi-mode
reported inwhenlicense
the
optimized
optimized toto 26200
Assume
alarm isBoard
that
generated both
The RRU
scenario.
limitation
preceding object is
ofFault
the
scenario.
make
improve theO&M Hardware
ALM-29240
after the Problem
upgrade.Cell
No N/A correlation removed.
Specific The alarm -
alarm
efficiency. exist on the and
Unavailable
detection is generated
alarm parameter afterin
locating more eNodeB,
ALM-26200 andBoard ALM-
mechanism the upgrade
ALM-29240 when
Cell
accuracy, 29248
The
between an RRU object of
Hardware
Unavailable
RF Out
Fault is
No N/A improving the
correlation Service
exist on is the triggered -
alarms has removed.
reported before the
O&M
detection by a baseband
eNodeB, and ALM-
been
The alarm
efficiency. upgrade is changed
mechanism resource
29240 Cell problem.
optimized to
parameter to Insufficient
between Before
Unavailable the upgrade,is
No N/A improvehave
values O&M license -
alarms has the two after
triggered by atheare
alarms
efficiency.
been upgrade.
been
The alarm not correlated.
baseband
Before andresource
after Afterthe
optimized
optimized to the upgrade,
parameter to problem.
upgrade, the the the
Before
make
improve theO&M two alarms
upgrade, the are two
Yes Yes values have Specific Problem -
alarm
efficiency. correlated.
alarms are changes not
been parameter
locating more Before
correlated. and after the
After the
optimized in certain scenarios.
accuracy, to upgrade,
upgrade, the two the
make the the
improving
Yes Yes Specific
alarms are Problem -
alarm
O&M parameter
correlated. changes
locating
efficiency.more
in certain scenarios.
accuracy,
improving the
O&M
efficiency.
 After the upgrade,
this
Before alarm theisupgrade,
The severity reported when
ALM-29213 eNodeB the
Before
status
S1 Control ofthe allupgrade,
the
Plane
of this alarm
the severity
SCTP
Transmission links (no of this
has been
alarm
fewer than
Interruption is "Major." two)
doesthat
Yes Yes modified to -
After
carry
not exist. the upgrade,
S1 interfaces
After the
improve
This the severity of is this
alarmalarm in an
upgrade, eNodeB
Before theALM- upgrade,
has been alarm
abnormal.
29201
thisdynamic
no isS1 "Warning."
alarm is eX2 This
Interface
not
accuracy.
The alarm
Yes Yes added to alarm
Fault
reported
blacklist isiscleared
cleared
when an
function foris -
detection
improve O&M when the status of
all
Before
S1 S1
link interfaces
the
fails
available. After the upgrade,
to be
mechanism
efficiency. an SCTP link that
when
this
set up
upgrade, ALM-29213
alarm because is not
the
has been carries an S1
eNodeB
Before
Beforeisthe
reported
there
eNodeB the S1
when
achecks
licenseControl
upgrade,
version the
No N/A optimized
The alarm to interface becomes -
Plane
no
eNodeB
limit
whether
upgrade, onTransmission
Local detects
S1-flex,
anthis SCTP alarm that
improve
parameter normal and the
Interruption
Description
SYNC
RAN
link
is that
reported packets
Sharing carries isalarm
when with are
an
alarm
has been status remains
reported.
parameter
lost
eX2 for
Common
each ALM-
X2aninterface
interface is meets
evolved
Carriers, is
reporting
added to normal forAfter 90eX2
Yes Yes 29201
available.
multimedia
RAN S1
faulty. Alarm with
the Sharing
dynamic Interface the -
accuracy.
improve seconds (default
Fault
upgrade, willconditions
broadcast/multicast
Dedicated
blacklist
parameters be
the Local
Carriers,
alarmalarm
This value).
reported again for a
Description
service
or
withinHybrid
X2Interface the (eMBMS)
RAN alarm
ID, CN
location
has been faulty interface after
The alarm parameter
session
Sharing. After
measurement
Operator over is
ID, and the
the M1
Yes Yes accuracy.
added to ALM-29213 eNodeB -
detection available.
interface.
upgrade,
period of about
Description After
this the
alarm
can 2
improve O&M S1 Control Plane
mechanism upgrade,
is reported
minutes
identify specific X2ifthis
thewith alarm the
efficiency. Transmission
has been
This alarm is is reported
Specific
following
interfaces. when
Problem
conditions the
No N/A The alarm
optimized to Interruption
1.When
eNodeB
alarm the
detects
parameter is
NE that -
reported are
After met:
the version
detection cleared.
detects
the number that the
improve
when the
mechanism PCI being
The
upgrade, linkLicense thisof
fails to
alarmbe
alarm
conflicts 1.
SYNC If
current
limited heartbeats
setgenerated
After
is upthe version
packets
in
upon the
upgrade, thelost of
is
first
has been
reporting the
improper
for anslave
preceding eMBMS core
andscenario. on an
between ato setup
this
depending
1. attempt.
alarm
If a clock is onsource the
No N/A optimized
accuracy. LMPT
performs
session
After theare an
over
S1 lost the
link for M1
for5 -
blacklisted The
reported
specific
that does when
X2not interface the
improve minutes,
automatic
interface
which no
theexceeds alarm
version
alarm a
neighboring
alarm
BASED_ON_EX2_
PCI
fault
support conflicts
cause, frame suchisas
cell and a are not reported
rollback,
specified
reported
NON_IDEAL_MOD
between
lower-layer this
threshold.
is
blacklisted
link alarm
reporting synchronization
before
is not setup the
reported upgrade is
No N/A common
The alarm removed,
E option
neighboring
fault, or
under thetheor
cells
failure, -
accuracy. activated,
but this alarm no alarm
neighboring
detection before
license alimit
eX2DynBlackListS
between
and CPBEARER version
a beforeis is no
is reported
reported
rollback after
but is the
cell. This is
mechanism longer
witch
blacklisted
subscription imposed
parameter failure. tois
the
upgrade.
1.When upgrade but this
improves
optimized
An alarm to allow thethe
reported
selected.
neighboring
ALM-29204 after
S1X2 cella and
link
Yes Yes alarm
2. If an
software
version is reported
LBBPcof
rollback. a or -
1. An alarm
alarm
increase
detection the setup,
The
a common
Interface this
BackhaulType alarm
Fault with
after
LBBPd
secondary
2.When theboard upgrade.
the board
U2000
detection
reporting is
alarm
scenario with
parameterthe
neighboring
different Specific
is
specific set
cell. to
2. If the
performs
component
links down SYNCETH
aalarm
self-
orfailstheto
scenario
accuracy
reporting
added
Values forisand
are Problem
NON_IDEAL(Non-
causes can coexist.
clock
healing
be
system quality
activated, reset
resets level
after
this
after
No N/A added
O&M
accuracy.
improving
added for
for parameter
Ideal
When Backhaul).
one being
or -
configured
detecting
alarm
upgrading is not the the
loseon ofare
hot
supporting
efficiency.
fault reporting
Alarm License
If the
multiple conditions
X2limited is
NE is unavailable
heartbeats
reported
patch and beforeon
performs the a
frame
accuracy
Parameters and cleared.
met,
interfacesthe eNodeB
are faulty
and
slave ALM-25880
synchronizati
O&M
of this alarm
version
an
due
Ethernet tocore
automatic
removes theupgrade
the and
same
Link
hot but
link
Fault
Yes Yes on and heartbeats
is
patch
and reported
cause, doesversion
only nonot are
after
one still
report a -
efficiency.
to
Thisaccurately
alarm is reported,
improving lost
version
rollback,
this
1.After
ALM-29204within
alarm. the 1
upgrade.
this hour
alarm
upgrade,
X2
locate faults
parameter is alarm
after theis reported
self-healing
O&M 2.If
is
If
this not
the automatic
Interface reported
conditions
alarm is
Fault hotisare
and improve
added to before
reset, the
ALM-26200 upgrade
efficiency. patch
before
not
reportedmet,
generated. recovery
a hot
this
when The patch
alarm aof a
Yes Yes O&M
facilitate fault but
Board thisfails,alarm
Hardware isalarm -
2. The alarm board
rollback
is
trust
alarmreported but
certificate
is cleared nois
for the theor a
efficiency.
location and reported
Fault after
iscertificate
reported
detection is
link.reported
reported
device
only when after before
all a hot
the X2
improve O&M upgrade.If
before
the upgradethe recoverthe
upgrade
scenario
efficiency.is
patch
referenced
interfaces
SYNCETH
rollback. bybut
clock thethis
Yes Yes optimized for but
alarm
3.When
IKEPEER
from thisisalarmthe MO is
reported -
1.The alarm
improving
quality
1.If
reported
after a the
the
configuration level
cross-R- preceding
after
upgrade. the
of the
To support expires.
fault.
configured
version In upgrade
thison alarm,
the
reporting
fault reporting upgrade.
NE is modified and
GUL 2.This
X2Interface
NE
occurs, alarmalarm
is unavailable is and
ID
mechanism
accuracy and is leads
reported
CN tothis
Operator the
with base ID are
is
Yes Yes maintenance,
modified, and and
-station
not thesatisfying
reported SYNCETH before the -
O&Malarm
This Certificate
displayed Type
as F, and
this alarmthe
therefore is clock
a version
condition is of upgrade
efficiency.
parameter is being
Description is
added.
O&M reconfigured
but is reported
configuration afterafter
3. The to
added alarm CERTWHITELSTFI
displayed as NULL.
efficiency is being
a version
rollback removed,
and upgrade. no
Yes Yes detection
facilitate fault LE andisAlarm -
improved. alarm
2.When
performing reported
the an license
scenarioand
location is Severity being
2.To add the before
file expires,
automatic the upgrade
this
added
improve toO&M Suggestion when
whitelist but
alarm this is
configuration alarm
not is
facilitate fault
efficiency. the following
Yes Yes filtering reported
rollback, after
before
this the a -
identification conditions
upgrade.
version upgrade arealarm met: but
function
and improve is1)not reported
To support 3.
is The
If this
reported IKE
alarm after is a
when
the a digital
O&M before a switch is
GUL verification
reported
version before the
upgrade.
certificate
efficiency. is configuration
Yes Yes maintenance, enabled
-
upgrade by
and running -
used for IKE
this alarm is rollback
the SET but
CERTCFG isclock
negotiation, desynchronization
reported after a
added. command.
interference occurs
the alarm configuration
2) The
after the current
upgrade, base
parameter rollback.
station
the severity doesof not this
and alarm
have
alarman activated
is changed
severity are
certificate
from minorwhitelist to major
modified.
 This alarm is occurs if the global
added to alert GTP-U static
operators to detection switch is
When
enabled. theAfter datathe
data
configuration
upgrade, this alarm
configuration
An alarm becomes
is reportedabnormal, when the
becomes
parameter is this alarm is notfault
corresponding
Yes Yes abnormal and -
added, and reported
occurs if before the linka
to improve
therefore the version
GTP-U static upgrade but
alarm
An alarm
fault can be is reportedswitch
detection after ais
reporting
parameter is
Yes Yes more version
-
enabled upgrade.
or if the -
accuracy
added and and
accurately
O&Minvalid setting of link GTP-
therefore
The
located andthe
efficiency.
fault can be U static detection
alarm
the O&M
Yes Yes Alarm
more switch
- follows that -
parameter
efficiency isis
parameter
accurately of the global GTP-U
removed
improved. and
values
located are
and static detection
the alarm
optimized
the O&M switch and the latter
reporting
Alarm
Yes Yes and the alarm
efficiency is is is enabled. -
mechanism
parameter
reporting
improved. 2. If the X2(X2)
modified,
values are and
mechanism check
1. If thebox is and
therefore theis
optimized local
optimized, selected
peer under
IP addresses the
Yes Yes O&Mthe alarm
and -Service -
and therefore When
of an IP the Interface
pathbase are the
efficiency
reporting is
the
The fault
alarm can Alarm
After
station
same Configure
the
as and upgrade,
thosethe of peeran
improved.
mechanism is
be more
reporting Switch
this alarm
equipment
automatically parameter not in
issupport
optimized,
accurately the
Yes Yes mechanism is reported
different
established when
IP PMuser-ALM- -
and therefore
located and ENODEBALMCFG
optimized, 25888path,
versions
plane SCTP andonly Link
the
the
the fault
O&M can MO, ALM-25886 IP
and therefore Fault
transport
ALM-25886 is reported.
network
IP Path
be more
efficiency is Path Fault with
the fault can
accurately between
Fault them
is reported
Yes No improved. -Service Type being -
be more
located and modifies
before the the DSCP
upgrade
The alarm
accurately X2 will be masked.
Alarm
the O&M of
but the
bothIP PM
ALM-25886
reporting
located and If
3. the
When number the numberof this
parameter
Alarm
efficiency is is session
IP Path packet,
Fault and
mechanism
the O&M IKEv2
of this redirections
alarm
No N/A values
parameter are
improved. to alarm is reported.
ALM-25952 User -
optimized
efficiency is exceeds
reported theupgrade,
on aIKEv2
board
added,
values and
are BeforePath
Plane the Fault
improve
improved. O&M redirection
reaches 32, DOS
this
therefore
added
A andthe
scenario in the
are reported "Alarm
afterin
efficiency. attack
alarm threshold
will
fault can
the alarm
which thisbe Cause"
the upgrade is not
"Peer be
when
Yes Yes 300 consecutive
reported
version before
is not the -
more
reporting
alarm is this
When IP the
path is alarm
total faulty.
seconds,
upgrade
supported" this
but will
orpath still
accurately
mechanism
reported is is 2. Before
number oftheIP
A scenario in is
be not
"DSCPand reported
reported modified."after the
located
optimized,
added and
so that upgrade,
faults this
user- alarm
which this before
upgrade.
After thetheupgrade,
upgrade
Yes Yes the O&M
and
this therefore
alarm is is reported
plane path faults when the -
alarm is can but
the is reported
reported after
"Alarm
efficiency
the fault
reported is corresponding
exceeds 16, bothfault
Alarm
reported is the
Cause"upgrade.
improved.
be
when more
user- occurs
ALM-25886 ifisthe"DSCPglobal
IP Path
parameter
added
accurately
plane so that
faults modified."
GTP-U
Fault and staticALM-
Yes Yes values
this are
alarm
located and is detection switch is -
occur, and 25952 User Plane
optimized,
reported
the O&M the
therefore enabled.
Path Fault After
are the
and
when
alarm therefore
the
efficiency
can isbe If the DNS
upgrade,
reported client
this
before alarmthe
the
DNS fault
improved.
more can
client initiates
is reported
upgrade domain
butwhen only the
Yes Yes - -
be more
initiates
accurately name resolution
corresponding
this alarm is fault to
accurately
domain
reportedname and the DNS
occurs if instead
reported server
the link and
located
O&M and
resolution to a domain
GTP-U
after thestatic name fails
upgrade.
Yes Yes the O&M
DNS
efficiency is to
detection switchthis
be resolved, is -
efficiency
server
The andisa
invalid
improved. alarm
enabled is not or if the
improved.
domain
alarm is name reported
setting ofbefore link GTP- the
fails to be
deleted to upgrade
U but
static detection is
Yes No resolved,the and -reported after the -
improve switch follows that
The
O&M invalid
therefore the upgrade.
alarm is of the global GTP-U
alarm can be
efficiency. static detection
deleted
more to
Yes No -
switch and the latter -
improve
accurately the
The
O&M invalid is enabled.
reported
alarm is and
efficiency.
O&M to
deleted
Yes No efficiency is - -
improve the
The invalid
improved.
O&M
alarm is
efficiency.
deleted to
Yes No - -
improve the
O&M
efficiency.
 baseband chip
experiences a soft
failure. After the
upgrade, this alarm
The alarm
is reported when the
detection
baseband chip
mechanism is
experiences a soft
No N/A optimized for -
failure and its self-
improving the
healing fails.
O&M
2. When the BRU is
efficiency.
reset repeatedly in a
short period of time,
this alarm is not
reported before the
upgrade and is
reported after the
upgrade.
cription
Applicable Mode
Suggestion

- G,U,L

- L

- L

Handle this alarm

by referring to the
L
alarm reference for
the eNodeB.
Handle this alarm
by referring to the
L
alarm reference for
the eNodeB.

- G,U,L

- L
Handle this alarm
based on the
impact on the
L
system as
described
Handle thisinalarm
the
alarm
by reference.
referring to the
alarm reference for L
the eNodeB
Handle after
the alarm
the upgrade.
according to the
impact of the
GUL
alarm on the
Handle thethe
system in alarm
according to the
alarm reference.
impact of the
L
alarm on the
Handle thethe
system in alarm
according to the
alarm reference.
impact of the
L
alarm on the
Handle thethe
system in alarm
according to the
alarm reference.
impact of the
L
alarm on the
Handle thethe
system in alarm
according to the
alarm reference.
impact of the
L
alarm on the
Handle thethe
system in alarm
according to the
alarm reference.
impact of the
L
alarm on the
system in the
alarm reference.
- L
Handle this alarm
according to the
instructions in the L
alarm reference for
the eNodeB.
- L

- L

- L

- L

- L
Handle this alarm
based on the
impact on the
L
system as
described in the
alarm reference.
- L

Handle this alarm

with recommended
L
actions based on
system impact.
Handle this alarm
with recommended
L
actions based on
system impact.
Handle this alarm
with recommended
L
actions based on
system impact.
Handle this alarm
with recommended
L
actions based on
system impact.

- L

Handle this alarm

with recommended
L
actions based on
system impact.
Handle this alarm
with recommended
L
actions based on
system impact.

- L
Handle this alarm
with recommended
L
actions based on
system impact.
Handle this alarm
with recommended
L
actions based on
system impact.
Handle this alarm
with recommended
L
actions based on
system impact.
Handle this alarm
with recommended
L
actions based on
system impact.
Handle this alarm
with recommended
L
actions based on
system impact.
Handle this alarm
with recommended
L
actions based on
system impact.
Handle this alarm
with recommended
L
actions based on
system impact.
Handle this alarm
with recommended
L
actions based on
system impact.
Handle this alarm
with recommended
L
actions based on
system impact.
Handle this alarm
with recommended
L
actions based on
system impact.
Handle this alarm
with recommended
L
actions based on
system impact.
Handle this alarm
with recommended
L
actions based on
system impact.
Handle this alarm
with recommended
L
actions based on
system impact.

- L

- L

- L

- L
Handle this alarm
with recommended
L
actions based on
system impact.