Samsung LTE ENB Alarm Manual For PKG 5.0.0 - v1.0

Samsung LTE eNB
Alarm Manual
for PKG 5.0.0
Radio Access Network
Provides a detailed reference and resolution guide for alarms that can be raised on
the Samsung LTE eNB. This includes the DU and radio units.
Document Version 1.0

August 2015
Document Number: 2600-00I33NGAB
2015 SAMSUNG Electronics Co., Ltd.

All Rights Reserved. No part of this document may be photocopied, reproduced, stored in a retrieval
system, or transmitted, in any form or by any means whether, electronic, mechanical, or otherwise
without the prior written permission of SAMSUNG Electronics Co., Ltd.
No warranty of accuracy is given concerning the contents of the information contained in this
publication. To the extent permitted by law no liability (including liability to any person by reason of
negligence) will be accepted by SAMSUNG Electronics Co., Ltd., its subsidiaries or employees for
any direct or indirect loss or damage caused by omissions from or inaccuracies in this document.
SAMSUNG Electronics Co., Ltd. reserves the right to change details in this publication without notice.
SNMTC-v3-0312
This manual should be read and used as a guideline for properly installing and/or operating the
product. Owing to product variations across the range, any illustrations and photographs used in
this manual may not be a wholly accurate depiction of the actual products you are using.
This manual may be changed for system improvement, standardization and other technical
reasons without prior notice.
Samsung Networks documentation is available at http://www.samsungdocs.com
Contents
Preface
vii
Relevance ....................................................................................................................................... vii
Conventions in this Document ....................................................................................................... vii
Revision History ..............................................................................................................................viii
Personal and Product Safety ........................................................................................................... ix
Equipment Markings ...................................................................................................................... xiii
Chapter 1
Introducing Alarms
1
Overview .......................................................................................................................................... 1
Alarm Codes ..................................................................................................................................... 2
Unit Types ........................................................................................................................................ 2
Alarm Categories .............................................................................................................................. 3
Alarm Severities ............................................................................................................................... 3
Auto Alarm Suppression ................................................................................................................... 4
Inhibiting Alarms .............................................................................................................................. 4
Monitoring Alarms ........................................................................................................................... 4
Dealing with an Alarm ...................................................................................................................... 5
Log Collection Method ..................................................................................................................... 5
Chapter 2
Alarm Reference
6
A2100102R UMP PROCESS DOWN................................................................................................... 6
A2100217R UMP CPU TEMPERATURE HIGH .................................................................................... 9
A2100300R UMP DISK FULL ........................................................................................................... 14
A2100301R UMP MEMORY FULL ................................................................................................... 17
A2100302R UMP OVERLOAD ......................................................................................................... 20
A2100305R UMP PACKET ERROR ................................................................................................... 23
A2100351R UMP CLOCK FAIL ......................................................................................................... 25
A2100370R UMP MEMORY FAIL .................................................................................................... 30
A2100380R UMP PORT DOWN ...................................................................................................... 33
A2100439R UMP ETHERNET HALF DUPLEX DETECTED .................................................................. 37
A2116100R ECP DSP RESTART ........................................................................................................ 40
A2116102R ECP PROCESS DOWN .................................................................................................. 43
A2116300R ECP DISK FULL ............................................................................................................. 46
A2116301R ECP MEMORY FULL ..................................................................................................... 49
A2116305R ECP PACKET ERROR ..................................................................................................... 52
A2116302R ECP OVERLOAD ........................................................................................................... 55
A2116351R ECP CLOCK FAIL ........................................................................................................... 58
A2116366R ECP BOARD DELETION ................................................................................................ 62
A2116367R ECP POWER FAIL ......................................................................................................... 66
A2116368R ECP FUNCTION FAIL .................................................................................................... 70
A2116372R ECP DSP FAIL ............................................................................................................... 76
A2116376R ECP CPRI FAIL .............................................................................................................. 79
A2116378R ECP OPTIC TRANSCEIVER RX LOS ................................................................................ 84
A2116379R ECP OPTIC TRANSCEIVER TX FAULT ............................................................................ 88
A2116381R ECP COMMUNICATION FAIL ....................................................................................... 92
A2116607R ECP SFN FAIL ............................................................................................................... 96
A2149216R RRH TEMPERATURE HIGH ......................................................................................... 100
Samsung LTE eNB Alarm Manual for PKG 5.0.0 v1.0

Samsung Proprietary and Confidential
iii
Contents
A2149338R RET MOTOR JAM....................................................................................................... 104

A2149339R RET ACTUATOR JAM ................................................................................................. 108
A2149340R RET NOT CALIBRATED ............................................................................................... 112
A2149341R RET NOT CONFIGURED ............................................................................................. 116
A2149342R RET HW ERROR ......................................................................................................... 119
A2149343R RET ACTUATOR INTERFERENCE ................................................................................ 122
A2149351R RRH CLOCK FAIL ........................................................................................................ 125
A2149381R RRH COMMUNICATION FAIL..................................................................................... 129
A2149384R RRH DC INPUT FAIL ................................................................................................... 136
A2149385R RRH DISABLED ........................................................................................................... 140
A2149388R RRH LNA FAIL ............................................................................................................ 143
A2149389R RRH LOW GAIN ......................................................................................................... 146
A2149391R RRH OVER POWER .................................................................................................... 149
A2149392R RRH VSWR FAIL ......................................................................................................... 153
A2149408R RRH DIGITAL INPUT LOW .......................................................................................... 159
A2149630R ALD COMMUNICATION FAIL ..................................................................................... 164
A2149649R RRH HW TYPE MISMATCH ........................................................................................ 168
A2180001R GPSR TOD MSG MISSED ............................................................................................ 171
A2180350R GPSR ANTENNA FAIL ................................................................................................. 175
A2180360R GPSR HOLDOVER 24H ............................................................................................... 179
A2180361R GPSR LOCKING FAIL .................................................................................................. 183
A2180368R GPSR FUNCTION FAIL ................................................................................................ 187
A2180424R GPSR FREQUENCY HOLDOVER EXCEED..................................................................... 190
A2180624R GPSR CLOCK PHASE ABNORMAL............................................................................... 194
A2199202R SYS UDA .................................................................................................................... 198
A2199209R SYS FAN FAIL ............................................................................................................. 201
A2199365R SYS NTP UPDATE ERROR ........................................................................................... 205
A2199460R SYS SERVICE OFF ....................................................................................................... 208
A2199600R SYS MME COMMUNICATION FAIL ............................................................................ 211
A2199602R SYS SLEEPING CELL DETECTION ................................................................................ 214
A2199605R SYS IND MME COMMUNICATION FAIL ..................................................................... 217
A2199629R SYS MCE COMMUNICATION FAIL ............................................................................. 220
Chapter 3
Microcell Alarm Reference

223
A2100100R UMP DSP RESTART .................................................................................................... 223
A2100102R UMP PROCESS DOWN............................................................................................... 226
A2100217R UMP CPU TEMPERATURE HIGH ................................................................................ 229
A2100300R UMP DISK FULL ......................................................................................................... 232
A2100301R UMP MEMORY FULL ................................................................................................. 235
A2100302R UMP OVERLOAD ....................................................................................................... 238
A2100305R UMP PACKET ERROR ................................................................................................. 241
A2100351R UMP CLOCK FAIL ....................................................................................................... 243
A2100367R UMP POWER FAIL ..................................................................................................... 246
A2100370R UMP MEMORY FAIL .................................................................................................. 249
A2100372R UMP DSP FAIL ........................................................................................................... 252
A2100380R UMP PORT DOWN .................................................................................................... 255
A2100439R UMP ETHERNET HALF DUPLEX DETECTED ................................................................ 258
A2148389R RU LOW GAIN ........................................................................................................... 261
A2148391R RU OVER POWER ...................................................................................................... 264
A2148392R RU VSWR FAIL ........................................................................................................... 267
A2148408R RU DIGITAL INPUT LOW ............................................................................................ 271
A2148396R RU RX PATH FAIL ....................................................................................................... 274
A2180350R GPSR ANTENNA FAIL ................................................................................................. 277

iv
Contents
A2180360R GPSR TOD MSG MISSED ............................................................................................ 281

A2180361R GPSR LOCKING FAIL .................................................................................................. 284
A2180368R GPSR FUNCTION FAIL ................................................................................................ 288
A2180601R GPSR HOLDOVER 8H ................................................................................................. 291
A2180624R GPSR CLOCK PHASE ABNORMAL............................................................................... 295
A2184001R PTPM TOD MSG MISSED ........................................................................................... 298
A2184003R PTPM NO CURRENT PTP MASTER ............................................................................. 301
A2184320R PTPM NO PTP SIGNAL ............................................................................................... 305
A2184321R PTPM CLOCK DEV NOT INIT ...................................................................................... 309
A2184430R PTPM STARTUP LOCKING FAIL .................................................................................. 312
A2184438R PTPM HOLDOVER EXCEED ........................................................................................ 316
A2199216R SYS TEMPERATURE HIGH .......................................................................................... 320
A2199365R SYS NTP UPDATE ERROR ........................................................................................... 324
A2199460R SYS SERVICE OFF ....................................................................................................... 327
A2199600R SYS MME COMMUNICATION FAIL ............................................................................ 330
A2199602R SYS SLEEPING CELL DETECTION ................................................................................ 333
A2199605R SYS IND MME COMMUNICATION FAIL ..................................................................... 336
A2199629R SYS MCE COMMUNICATION FAIL ............................................................................. 339
Appendix
Acronyms

342
List of Tables
Table 1.
Table 2.
Table 3.
Table 4.
eNB Unit Types ................................................................................................................................. 2

Microcell Unit Types......................................................................................................................... 2
Alarm Categories .............................................................................................................................. 3
Alarm Severities ............................................................................................................................... 3

vi
Preface
Provides a detailed reference and resolution guide for alarms that can be raised on
the Samsung LTE eNB. This includes the DU and radio units. About this
document
Relevance
This manual applies to the following products/software.
Name
Type
PKG 5.0.0
Software
Conventions in this Document

Samsung Networks product documentation uses the following conventions.
Symbols
Symbol
Description
Indicates a task.
Indicates a shortcut or an alternative method.
Provides additional information.
Provides information or instructions that you should follow to avoid service
failure or damage to equipment.
Provides information or instructions that you should follow to avoid personal
injury or fatality.
Provides antistatic precautions that you should observe.
Menu Commands
menu | command
This indicates that you must select a command on a menu, where menu is the
name of the menu, and command is the name of the command on that menu.
File Names and Paths

These are indicated by a bold typeface. For example:
Copy filename.ext into the /home/folder1/folder2/bin/ folder.
vii
Preface
User Input and Console Screen Output Text

Input and output text is presented in the Courier font. For example,
context <designated epc-context-name>
CLI commands are presented in bold small caps. For example,
Type the RTRV-NE-STS command in the input field.
Revision History
The following table lists all versions of this document.
Document Number
Product/Software
Version
Document
Version
Publication
Date
Remarks
2600-00I33NGAB
PKG 5.0.0
1.0
31 Aug 2015
First version

viii
Preface
Personal and Product Safety

This product safety information includes European directives, which you must
follow. If these do not apply in your country, please follow similar directives that
do apply in your country.
Electrical
The product is designed to operate from a -48 V DC supply and is therefore
classified as SELV (Safe Extra Low Voltage) equipment.
All structural parts are grounded and all input and outputs have built-in isolation
from the network. All input and output ports that connect to external power
sources are designed to meet relevant national safety requirements.
The product contains hazardous energy levels as defined by EN 60950. Care must
be taken when maintaining this equipment as injury to personnel or damage to the
equipment could result from mistakes. Maintenance should only be carried out by
trained and competent engineers who are familiar with the relevant procedures and
instructions.
Lasers
The product is fitted with optic modules rated as Class 1 radiation-emitting devices
under EN 60825-1. During installation, operation, and maintenance, never look
into the end of an optical fiber directly or by reflection either with the naked eye or
through an optical instrument. Do not operate equipment with exposed fiber
connectors-cover these with fiber cables or blanking caps. Do not remove
equipment covers during operation unless requested to do so in the documentation.
Carry out normal safety precautions when trimming fibers during installation.
Manual Handling
Care should be taken when handling equipment. Give due consideration to the
weight of the equipment, the physical capability of the individual(s) handling the
equipment, and movements such as twisting, bending and stooping, which could
lead to skeletal and muscular injuries.
Installation
Installation must be carried out by trained and competent engineers only. All
relevant safety measures should be taken to ensure equipment is not connected to
live power and transmission sources during installation. Equipment must be
correctly installed in order to meet the relevant safety standards and approval
conditions.
Each power feed to the unit requires a separate fused feed from the provided
power supply. The cable between the power distribution point and the installed
equipment must have a minimum cross-sectional area of 2.5 mm2.
ix
Preface
Rack-mountable equipment must be placed in a standard 19-inch rack and secured

with the appropriate fixings as detailed in the installation manual.
Maintenance
Maintenance must only be carried out by a suitably trained and competent
technician. All safety instructions must be carefully observed at all times.
Equipment covers should not be removed while live power and transmission is
connected unless in a controlled environment by trained technicians.
Fire
The product is powered from a -48 V DC supply. To protect against fire, the
equipment is fused.
Environment
The product must be operated in an environment with the specified relative
humidity and ambient temperature ranges.
Keep all liquids away from the equipment as accidental spillage can cause severe
damage.
Cooling
The product cools down by its own set of cooling fans housed in a fan module.
Each fan module detects a fan that is not operating normally. LEDs on the front
panel of the fan tray provide an alarm indication in the event of fan failure.
In the event of fan failure, take urgent remedial action to restore full cooling
capacity.
Take appropriate measures to ensure that fan modules do not start spinning during
repair and maintenance procedures.
Anti-Static Precautions
The circuit boards and other modules in the product are sensitive to and easily
damaged by static electricity. If any card or sub-assembly is removed from the unit,
the following anti-static precautions must be observed at all times:
Service personnel must wear anti-static wrist straps.
Circuit boards and sub-assemblies must be placed on ground conductive mats

or in conductive bags.
All tools must be discharged to ground before use.
The anti-static wrist strap and cord must be checked at regular intervals for
their suitability for use.

Preface
Grounding
To comply with EN 60950, the equipment must be connected to a safety
grounding point via a permanent link. Grounding points are located on the product
for this purpose. Always connect the ground cable before fitting other cables. The
product must remain grounded continuously unless all connections to the power
supply and data network are all removed.
If equipment is grounded through a cabinet or rack, make sure it is done so
properly according to the installation instructions.
Power Supply Connection

The equipment is designed to be powered from a -48 V DC supply. Power
connections and installation of associated wiring must be carried out by a suitably
qualified technician.
Only devices that comply with all relevant national safety requirements should be
connected to the unit's power supply inlets. Other usage will invalidate any
approval given to this equipment.
Connection of this equipment to devices that are not marked with all relevant
national safety requirements may produce hazardous conditions on the network.
When the power supply is obtained by a rectifier/safety isolation transformer, the
supply must meet the requirements of EN 60950 providing double/reinforced
insulation between hazardous voltages and SELV/TNV circuits. Any battery must
be separated from hazardous voltages by reinforced insulation.
Indirect Connection
Before indirectly connecting any equipment to another device through a shared
power supply, ALWAYS seek advice from a competent engineer.
Devices that are not marked according to the relevant national safety standards
may produce hazardous conditions on the network.
Product Disposal
To reduce the environmental impact of products, Samsung has joined WEEE
compliance activities.
The WEEE symbol on the product indicates that the product is covered by the
European Directive 2002/96/CE for the disposal of Waste Electrical and Electronic
Equipment (WEEE). This means that the product should be disposed of separately
from the municipal waste stream via designated collection facilities appointed by
the government or the local authorities. This will help prevent potential negative
consequences for the environment and human health. Please check the terms and
conditions of the purchase contract for information about correct disposal.

xi
Preface
Battery Disposal
The product contains a battery on the processor card. The battery should not be
disposed of with other household waste. Where marked, the chemical symbols Hg,
Cd or Pb indicate that the battery contains mercury, cadmium or lead above the
reference levels in EC Directive 2006/66. The battery incorporated in this product
is not user replaceable. For information on its replacement, please contact your
service provider. Do not attempt to remove the battery or dispose it in a fire. Do
not disassemble, crush, or puncture the battery.
End of life recycling materials information is available from Samsung.
Chemical Warning
This product contains chemicals known to the State of California to cause cancer
and reproductive toxicity.

xii
Preface
Equipment Markings
This marking on the product, accessories or literature indicates that the
product and its electronic accessories (e.g. charger, headset, USB cable)
should not be disposed of with other household waste at the end of their
working life. To prevent possible harm to the environment or human health
from uncontrolled waste disposal, please separate these items from other
types of waste and recycle them responsibly to promote the sustainable
reuse of material resources.
For more information on safe disposal and recycling, visit our website
www.samsung.com/in or contact our Helpline numbers - 18002668282,
180030008282.
Correct disposal of batteries in this product

(Applicable in countries with separate collection systems.)
The marking on the battery, manual or packaging indicates that the battery
in this product should not be disposed of with other household waste. Where
marked, the chemical symbols Hg, Cd or Pb indicate that the battery
contains mercury, cadmium or lead above the reference levels in EC
Directive 2006/66.
The battery incorporated in this product is not user replaceable. For
information on its replacement, please contact your service provider. Do not
attempt to remove the battery or dispose it in a fire. Do not disassemble,
crush, or puncture the battery. If you intend to discard the product, the waste
collection site will take the appropriate measures for the recycling and
treatment of the product, including the battery.
This product is RoHS compliant.

xiii
Chapter 1
Introducing
Alarms
Overview
Alarms are events indicating problems or conditions that are worth highlighting.
An alarm can be raised by hardware or by software processes.
Hardware alarms are environmental alarms or alarms that are generated in a board.
These alarms are collected by all the sub-boards and are reported to the main board.
Software alarms are detected by other software blocks in each board and reported
to the fault management module running in the master board.
Alarms are graded into severities and require operator intervention. An alarm is
raised if, for example, a process in the equipment has failed or if the temperature
level around a hardware component has reached a defined threshold level.
Alarms are vital to the troubleshooting and diagnosis of hardware and software
problems.
All Alarms are reported in the LSM graphical user interface and are retained in an
alarm/fault history location for the following rolling periods:
Type of Alarm/Fault
Retention Period
Raw data
7 days
Hourly
60 days
Daily
60 days
Monthly
6 months
There are two types of output message:
Alarm occurred
Alarm cleared
In the LSM event viewer, the following colors are used to indicate the alarms and
their severity.
Critical: Red
Major: Orange
Minor: Yellow
Alarm Cleared: Green
Every alarm is uniquely identified by an alarm code and falls into a particular
category with an assigned severity.
Alarms are events indicating problems or conditions that are worth highlighting.
An alarm can be raised by hardware or by software processes. An alarm is raised if,
Chapter 1 Introducing Alarms
for example, a process in the equipment has failed. Another alarm might be raised
if the temperature level around a hardware component has reached a defined
threshold level.
Alarm Codes
An alarm is uniquely identified by an alarm code. The alarm code is an alphanumeric string that starts with the letter A, contains a unique 7-digit number and
ends with the letter R. The letter A stands for Alarm, and the letter R identifies that
the alarm is for the RAN (eNB).
A xxyyzzz R
Abbreviation of RAN (eNB)
Alarm number
Abbreviation of Alarm
A: Abbreviation of Alarm
xxyyzzz (7-digit number): Allocated to each alarm uniquely.

o
xx: NE type.
yy: Unit type. For unit type values, see Table 1 and Table 2.
zzz: Alarm type. For alarm type values, see Table 3.
R: Abbreviation of RAN (eNB)
Unit Types
The following table shows types of units that can raise alarms:
Table 1. eNB Unit Types
Code
Unit Type
Description
00
UMP
Universal Main Processor
16
ECP
ENB Channel Processor
49
RRH
Remote Radio Head
80
GPSR
GPS Clock
99
SYS
eNB System
Table 2. Microcell Unit Types

Code
Unit Type
Description


Code
Unit Type
Description
00
UMP
Universal Main Processor
48
RU
Radio Unit
49
RRH
Remote Radio Head
80
UCR
Universal Clock Receiver
84
PTPM
IEEE1588 Clock Device
92
SyncE
SyncE Clock Device
99
SYS
Microcell System
Alarm Categories
The category of the alarm denotes the component type that raised the alarm or the
type of service affected by the alarm. Every alarm falls into one of the following
categories and this is clearly stated under each alarm description in this manual.
Table 3. Alarm Categories
Category
Meaning
COMMUNICATIONS
A communication failure between equipment.
QOS
An adverse effect on device performance or quality of service.
PROCESSING
Software or processing failure.
EQUIPMENT
A device or equipment failure.
ENVIRONMENT
An environmental condition (such as excessive temperature or

humidity) causing an adverse effect on equipment.
Alarm Severities
The severity indicates the impact on the system and gives you an idea of how
quickly the alarm should be dealt with. Every alarm that can be raised is assigned
one of the following severities (from lowest to highest) and this is clearly stated
under each alarm description in this manual.
Table 4. Alarm Severities
Severity
Meaning
MINOR
Indicates errors that do not have an immediate impact on the

system but may do so if left unresolved.
MAJOR
Indicates errors pertaining to abnormalities in hardware or

software operation such as circuit or subscriber service errors,
immediate action is required although system operation is not
seriously hindered.
CRITICAL
Indicates errors that seriously hinder normal system operation

or greatly affect the system services. Immediate action is
required.

Some alarms can take on different severity levels over a period of time. The
occurrence of such an alarm clears any previously raised lower-severity
occurrences of the alarm. To illustrate this, consider the alarm that is raised when
disk usage reaches predefined thresholds defined by the operator such as Minor
when 85 % full, Major when 90 % full, and Critical when 95 % full. A minor
alarm will be raised when the disk is 85 % full. At 90 %, the severity will change
to major and, at 95 %, it will change to critical.
Auto Alarm Suppression

Some failures may raise several related alarms of different severities. A high
severity alarm demanding immediate attention will automatically cause related
lower severity alarms from being reported until it is cleared. This allows you to
focus your troubleshooting efforts on more immediate issues before being told
about the less important ones.
For example, when a Communication Fail alarm is generated on a channel card or
radio unit (RRH), other alarms that occur on these boards will not be reported.
This is because the Communication Fail alarm is a higher severity alarm. The
collection of the suppressed lower-severity alarms resumes after the
Communication Fail alarm is cleared.
Inhibiting Alarms
If, for any reason, you are not interested in being notified about particular alarms,
you can inhibit them so that they are not displayed in LSM. Inhibited alarms are
not saved to the alarm history location.
To view the inhabit alarms in the LSM:
1 Go to Rack Viewer.
2 Right click on the NE, and then select Alarm Inhibit/Allow from the pop-up
menu.
The list of inhibited alarms displays for the corresponding NE. For information
on inhibiting an alarm, refer to Samsung LSM 5.0 User Manual.
Monitoring Alarms
You can monitor the alarm by the following methods:
Alarm monitoring using the LSM Event Viewer.
Alarm monitoring by executing commands on the CLI window of the LSM.
Alarm Monitoring by LED.

Dealing with an Alarm

To ensure that your network is running properly at all times, you must deal with
alarms promptly.
To deal with an alarm:
Read the alarm information in the LSM and/or look up the alarm in this
manual to identify its cause and remedy. If the alarm is related to another
alarm of higher severity, then identify the cause of this higher severity alarm.
2 Use the information to try to resolve the underlying problem and thus clear the
alarm.
If you are still unable to clear an alarm, report the problem to your local Samsung
Electronics support desk (hereafter referred to as Samsung).
Log Collection Method

If any of the alarms remain active in LSM despite of taking all corrective actions,
you must collect the system log to analyze them thoroughly. The notification and
system logs are stored in the LSM and card. You can retrieve the logs for the date
of alarm declared or cleared from their default paths:
For LSM:
o
/log/msg/noti/
/log/system/syslog
For card:
o
/var/log/
/pkg/BufferLogger/
For more detailed log collection method, contact Samsung.

Chapter 2
Alarm Reference
This chapter explains the common alarms that may issue during eNB operation. A
description of the alarm, its possible cause, and resolving procedures are provided.
A2100102R UMP PROCESS DOWN

This alarm occurs when a process is deactivated.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Software
PROCESSING
RACK[a]/SHELF[b]/SLOT[c]-UMP[d]/BLOCK_NAME
Possible Cause
The process is deactivated. You can find the cause by analysing the core file and
log file uploaded to the LSM.
Impact
If an alarm is generated continuously in a specific software block, the service will
be unavailable.
Remedy
To analyze and resolve the alarm:

Chapter 2 Alarm Reference
Alarm Raised
Re-activate Alarm
Raised Block
Step 1
Yes
Alarm Cleared After

Repair?
No
Backup the Faulty

NE Block Image
Step 2
Replace Block Image
Yes
Alarm Cleared
After Repair?
No
Collect SW Log and

Restart Board
Step 3
Yes
Alarm Cleared
After Repair?
No
Step 4
Collect SW Log and

Restart NE
Step 5
Backup
LSM Log
End
Activate the block that has raised the alarm:
a Re-activate the disabled block by running the INIT-SW:UMP,

<block_name> command.
b Check whether the PROCESS_DOWN alarm has been raised for the
applicable block.
2 If the alarm remains, replace the block image. Backup the block image for
future analysis:
Backup the block image that continues to deactivate. Use the DNLD-SW
and UDT-SW to replace the block image.
applicable block.
3 If the problem cannot be solved by replacing a single block, restart the

applicable board to repair it:
After collecting the SW log, use board restart commands such as INITPRC to carry out the repair.
applicable block.
4 If the problem cannot be solved by restarting the board, restart the NE to repair
it:
After collecting the SW log, use NE restart commands such as INIT-SYS

to carry out the repair.
applicable block.
5 To analyze the step by step process of clearing the PROCESS_DOWN alarm,

backup the LSM log, by collecting the logs in /log/system/corelog &
/log/system/applog for the relevant time frame.
6 If the alarm persists, consult the next level of maintenance support with
Samsung.

A2100217R UMP CPU TEMPERATURE HIGH

This alarm occurs when the CPU temperature exceeds the threshold.
Basic Information
Severity
Relates to
Category
Location
CRITICAL/MAJOR
Hardware
ENVIRONMENT
RACK[a]/SHELF[b]/SLOT[c]-UMP[d]
Possible Cause
The CPU temperature exceeded the threshold.
The threshold value can be retrieved by using the RTRV-BDTEMPALM-THR
COMMAND.
Impact
The board will be damaged. To prevent heat-induced damage to the board, the
eNB performs these functions:
If a critical severity alarm occurs without a FAN_FAIL alarm, it lowers the

temperature by performing a power reset on the board.
When the critical severity alarm occurs together with the FAN_FAIL alarm, it
lowers the temperature by powering off the board.
Defaults
The default thresholds for issuing and clearing the alarm based on its severity are:
Critical alarms: Issuing 105 and clearing 100
Major alarms: Issuing 100 and clearing 95
Remedy
Off-site Actions via LSM before Site Visit

Alarm Raised
Step 1
Threshold < Default?
Yes
Run CHG-BDTEMPALM-THR
command
No
Keep Alarm?
Yes
No
No
Step 2
FW Update
FW Ver. NEW?
Step 3
Yes
Collect SW Logs
No
Yes
Step 4
UMP CPU
TEMPERATURE HIGH
Alarm Raised?
FAN Alarm Raised?
Yes
No
Actions to Clear FAN Alarm
UMP CPU
TEMPERATURE HIGH
Alarm Raised?
Yes
Step 5
No
Check UMP Temperature

Yes
Collect SW Log
Step 6
INIT-PRC(UMP)
Step 7
UMP CPU
TEMPERATURE HIGH
Alarm Raised?
No
Yes
On Site Action
End
Check the threshold values for the CPU_TEMPERATURE_HIGH alarm by

executing the TRV-BDTEMPALM-THR command.
If the threshold values are set lower than the default values specified in the
manual, do the following:
Enter the default threshold for each severity, and execute the CHG-

10
BDTEMPALM-THR command.
b If the CPU_TEMPERATURE_HIGH alarm clears within 30 seconds after

you change the threshold values, terminate the procedure. If not, collect
the SW log.
If the threshold values are set higher than the default values, collect the
SW logs.
2 Check whether the UMP firmware is the latest version by running the RTRVPRC-FW command.
Set the PRC_UNIT_TYPE to UMP, and then run this command.
b Check the output on whether the NAME, VERSION, and BUILD_TIME

of each firmware are the most recent one.
3 If the firmware is not the latest version, run the DNLD-FW command to
download the latest version and the UDT-FW command to update the firmware.
If the alarm is declared even when the firmware is up to date, collect the SW
log.
4 Run the RTRV-ALM-LIST command to check whether a A2199209R SYS

FAN alarm has been declared:
Check whether the output of ALARM_TYPE is FAN_FAIL. If it is,

follow the corrective actions of the A2199209R SYS FAN FAIL alarm.
b If there is no FAN_FAIL alarm, continue with the next step.

5 Run the RTRV-PRC-STS command to check the CPU temperature:
a
Set the UNIT_TYPE to UMP, and then run this command.
b Check whether the alarm generation conditions (when the threshold values
retrieved using the RTRV-BDTEMPALM-THR command are exceeded) are
met by checking the output parameter TEMPERATURE[C] value.
6 After collecting the SW log, run the INIT-PRC command to restart the UMP.
7 If the alarm remains, continue with the onsite actions.
On-site Actions

11
UMP CPU temperature high

alarm occurs
Entering the
base station
Step 1
Conduct visual inspection on

FANM-C4 PWR/ALM LED
Indicate the location of FANMC4 LED with a drawing
LED color is green?

Yes
Step 2

the air inlet/outlet of the CDU.
Check the existence of

foreign substances
Indicate the air inlet/outlet of the

shelf with a drawing
Eliminate foreign substances

in the air inlet/outlet of the
CDU shelf
Yes
No
Step 3
No
After dismounting the air filter,

conduct visual inspection on it
Check the alarm

clearance state
Yes
Check the existence of

foreign substances
After eliminating foreign

substances, mount the air
filter.
Yes
After recording the actions

taken, leave the station
No
Step 4
After dismounting UAMA/

LMA3, conduct visual
inspection on it
No
Check the alarm

clearance state.
Yes

taken, leave the station.
Check existence of
foreign substances.
Yes
Eliminate foreign substances

of UMP
Yes

No
Step 5
UAMA/LMA3 setting
Check alarm clearance

state.
No
Step 6
Replace UAMA/LMA3
Check the alarm

clearance state.
No
Entering Step 7
After replacing FANM-C4,

check if the alarm is cleared.
Yes

After entering the base station, check if the generated alarm of the base station
in LSM is maintained by contacting the operating center. If the alarm is

12
generated, conduct visual inspection on FANM-C4 PWR/ALM LED state. If

the alarm is cleared, execute sub-step (a) of Steps 2 and 3 to secure the normal
operation of the base station.
Items to be inspected: Record if FANM-C4 PWR/ALM LED is green or not.
If the LED is green, execute Step 2. If the LED is red or off, execute Step 7.
2 Conduct visual inspection on the air inlet/outlet of the DU shelf.

a
If any foreign substances preventing air flow found, eliminate them.
b If nothing significant to report is found or the alarm is not cleared even

after the removal, execute Step 3.
If the alarm is cleared after eliminating foreign substances, continue to

monitor the alarm state.
3 Check state of the air filter after dismounting it.

a
If any foreign substances preventing air flow found, remount the air filter
after eliminating them.
b If nothing significant to report is found or the alarm is not cleared even

after the removal, execute Step 4.
If the alarm is cleared after eliminating foreign substances, continue to

monitor the alarm state after recording history.
4 After dismounting UMP check if any foreign substances found in it.

If foreign substances are found, eliminate them. If not found, continue with the
Step 5.
5 After mounting UMP, check the alarm clearance state.

If the alarm is not cleared, continue with the Step 6. If cleared, continue to
6 After replacing the UMP, check the alarm clearance state.

If the alarm is not cleared, continue with the Step 7. If cleared, continue to
7 Replace the FANM-C4. After recording history, continue to monitor the alarm
state.
For information on UMP replacement, see LTE eNB Hardware Addition and
Replacement Manual.

13
A2100300R UMP DISK FULL

This alarm occurs when the disk usage exceeds the threshold.
Basic Information
Severity
Relates to
Category
Location
CRITICAL/MAJOR/MINOR
Software
QOS
Possible Cause
The disk usage exceeded the threshold.
The threshold value can be retrieved by using the RTRV-ALM-THR command.
Impact
Some software blocks will operate abnormally.
Defaults
The default thresholds for issuing the alarm based on its severity are:
Minor: 85 %
Major: 90 %
Critical: 95 %
Remedy

14
Alarm Raised
Step 1
Run RTRV-ALM-THR
No
Yes
Run CHG-ALM-THR
Alarm Still Raised?
No
Yes
Collect SW Log
Step 2
Check Other Items
Alarm Still Raised?
Step 3
Alarm Level = Minor
No
Yes
No
Delete LOG
Folder Files
Delete TEMP
Folder Files
Alarm Still Raised?
No
Yes
Replace Board
End
Run the RTRV-ALM-THR command to check the threshold for the

DISK_FULL alarm.

15
If the DISK_FULL threshold is lower than the default values, do the following:
Set the UNIT_TYPE to UMP and ALARM_TYPE to DISK_FULL for the

CHG-ALM-THR. Enter the default value for each threshold level.
b If the DISK_FULL alarm is cleared within 10 seconds after changing the

threshold value, terminate the procedure. If not, collect the SW log.
If the threshold is set higher than the default value, collect the SW log.
2 Check the following categories in which the DISK_FULL alarm can occur.
a
DISK_FULL alarm can occur if more than one passive package exists as a
result of an online upgrade. Use the RTRV-PKG-VER command to check
the number of passive packages.
b After an online upgrade, run the DLT-PASV-PKG command to delete the

passive packages.
Check whether the DISK_FULL alarm has been cleared.
3 If the alarm remains, do the following steps:

a
If the DISK_FULL alarm level is CRITICAL or MAJOR, delete the files

in LOG and TEMP folders of the UMP board.
b If the level is MINOR, then delete the files in TEMP folder of the UMP
board.
The locations of folders for the files to delete are: LOG: /var/log and TEMP: /tmp.
4 If the alarm remains, replace the faulty board.

Replacement Manual.

16
A2100301R UMP MEMORY FULL

This alarm occurs when the memory usage exceeds the threshold.
Basic Information
Severity
Relates to
Category
Location
Software
QOS
Possible Cause
The memory usage exceeded the threshold.
Impact
Defaults
Minor: 95 %
Major: 96 %
Critical: 97 %
Remedy

17
Alarm Raised
Step 1
Run RTRV-ALM-THR
No

Yes
Run CHG-ALM-THR
Alarm Still Raised?
No
Yes
Collect SW Log
Step 2
Check Other Items
Alarm Still Raised?
Step 3
Alarm Level = Minor
No
Yes
No
Delete LOG
Folder Files
Delete TEMP
Folder Files
Alarm Still Raised?
No
Yes
Replace Board
End

MEMORY_FULL alarm.

18
If the MEMORY_FULL threshold is lower than the default values, do the

following steps.
Set UNIT_TYPE to UMP and ALARM_TYPE to MEMORY_FULL for

the CHG-ALM-THR. Enter the default value for each threshold level.
b If the MEMORY_FULL alarm is cleared after changing the threshold,

terminate the procedure. If not, collect the SW log.
[If the threshold is set higher than the default value, collect the SW log.
2 Check the following categories in which the MEMORY_FULL alarm can

occur.
The MEMORY_FULL alarm can occur if more than one passive package
exists as a result of an online upgrade. Use the RTRV-PKG-VER
command to check the number of passive packages.
i
After an online upgrade, run the DLT-PASV-PKG command to delete

the passive packages.
ii
Check whether the MEMORY_FULL Alarm has been cleared.
b The MEMORY_FULL alarm can occur after the DNLD-FW-BAT

command is executed and completed.
i
Run the UDT-FW-BAT command to delete the firmware image.
ii
Check whether the MEMORY_FULL alarm is cleared after running

the UDT-FW-BAT command.
3 If the alarm remains, Do the following steps:

a

in LOG and TEMP folders of the UMP board.
b If the level is MINOR, then delete the files in TEMP folder of the UMP
board.
The locations of folders with for the files to delete are: LOG: /var/log and TEMP:
/tmp.
Check whether the MEMORY_FULL alarm has been cleared.

For information on board replacement, see LTE eNB Hardware Addition and
Replacement Manual.

19
A2100302R UMP OVERLOAD

This alarm occurs when the CPU usage exceeds the threshold.
Basic Information
Severity
Relates to
Category
Location
Software
QOS
Possible Cause
The CPU usage exceeded the threshold.
The threshold value can be retrieved by using RTRV-ALM-THR command.
Impact
Some software blocks will operate abnormally. If this alarm is generated
continuously, the UMP board will be reset.
Defaults
Minor: 85 %
Major: 90 %
Critical: 95 %
Remedy

20
Alarm Raised
Step 1
Check Threshold Value
No
Yes
Change Threshold Value
Alarm Still Raised?
No
Yes
Collect SW Log
Step 2
Check Other Items
Alarm Still Raised?
No
Yes
Step 3
Alarm Level = Critical
No
Yes
SESSION CLOSE
Alarm Still Raised?
No
Yes
Step 4
Replace Board
End

OVERLOAD alarm.

21
If the OVERLOAD threshold is lower than the default values, do the

following steps:
Set the UNIT_TYPE to UMP and ALARM_TYPE to OVERLOAD for the

b If the OVERLOAD alarm is cleared after changing the threshold,

2 Check the following categories in which the OVERLOAD alarm can occur.
a
The OVERLOAD alarm can occur if the data size is too large when
executing the UPLD-CONF-FILE command.
i
Wait until the UPLD-CONF-FILE command is completed. If the

OVERLOAD alarm is cleared level by level, terminate the procedure.
b The OVERLOAD alarm can occur if commands, such as On-Demand Test,

are repeated.
i
Stop the commands that are being repeated.
ii
If the OVERLOAD alarm is cleared, terminate the procedure.
3 If the alarm is critical, close all the terminals (Telnet, FTP, and dsh) that are
connected to the UMP. If it is cleared, terminate the procedure.

Replacement Manual.

22
A2100305R UMP PACKET ERROR

This alarm occurs when the error packets rate exceeds the threshold level.
Basic Information
Severity
Relates to
Category
Location
MINOR
Software
EQIPMENT
Possible Cause
The error packets rate exceeded the threshold level.
The threshold can be retrieved by using RTRV-INVALIDPKT-CONF command.
Impact
The service will be degraded due to the dropped packets.
Remedy
The alarm can be resolved in the following two ways.


23
Alarm Raised
Step 1
Is New F/W
No
UMP/ECP FW Update
Step 2
Yes
SW Log Collection
Step 3
Reset ECP and UMP
Step 4
Alarm Clear?
No
Yes
END
On Site Action
Check whether the firmware is the latest version.
3 Reboot the UMP board where the alarm occurred. And then, reboot the ECP
boards one at a time.
4 Check whether the alarm has been cleared. If yes, wait for 10 minutes and
recheck again. If not, collect the SW log and share with Samsung for the next
level of maintenance support.
The UMP and ECP collects all files under the /var/log folder, respectively.
On-site Actions
To resolve the alarm:
Replace the board.
Replacement Manual.

24
A2100351R UMP CLOCK FAIL

This alarm occurs when the clock frequency deviation exceeds normal parameters.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
Possible Cause
The clock module has a deviation or there is no clock.
Impact
The clock service will be unavailable.
Remedy


25
Alarm Raised
Step 1
UMP FW Ver. NEW?
No
UMP FW Update
Yes
Yes
Collect SW Log
UMP CLOCK FAIL

Alarm Raised?
No
Step 2
Reset UMP
UMP CLOCK FAIL Alarm

Raised?
No
Yes
Retrieve Alarm List
Step 3 No
GPSR Alarm Raised?
Step 4
Check GPS Status
Step 5
GPS FW Ver. NEW?
No
GPS FW Update
Yes
INIT-GPS
Step 6
UMP CLOCK FAIL Alarm

Raised?
No
Yes
Step 7
Collect SW Log
On Site Action
End
Check whether the UMP firmware is the latest version by running the RTRVPRC-FW command.

26
Set the PRC_UNIT_TYPE to UMP and LOC_TYPE to *, and then run

this command.

If the firmware is not the latest version, run the DNLD-FW command to
download the latest version and the UDT-FW command to update the
firmware.
d Run the RTRV-ALM-LIST command to check whether the alarm persists.

If yes, collect the SW log and continue with the next step.
2 Run the INIT-PRC command to restart the UMP.

a
Set the PRC_UNIT_TYPE to UMP and RESET_MODE to HW, and then

run this command.
b If the alarm remains, continue with the next step.

3 Run the RTRV-ALM-LIST to check whether a GPS related alarm has been
declared. If GPS related alarms exist, follow their respective remedies.
4 Run the RTRV-GPS-STS command to check the GPSR status.

Check whether the output of LOCK_STATE and HOLDOVER_STATE are
GPS_LOCKED and GPS_NOT_HOLDOVER.
5 Run the RTRV-GPS-INVT command to check whether the GPS firmware is

the latest version.
Check whether the FW_VERSION on the output window displays the latest
version.
If the alarm is declared even when the firmware is up to date, continue with
the next step.
7 Run the INIT-GPS command to restart the GPSR.

After the command has been run, check whether a UMP CLOCK_FAIL alarm
has been declared. If the alarm remains, collect the SW log and share with
Samsung for the next level of maintenance support.
On-site Actions

27
UMP clock fail alarm occurs

Entering the
base station
Step 1
Indicate the location of UAMA

GPS LED with a drawing.
Check UMP Clock LED
RED solid ?
Step 2
Yes
Execute the GPS inspection

procedure
Remount UAMA/LMA3 after

dismounting it.
Step 3
Check the alarm
disassembly state.
No
Replace UAMA/LMA3
Yes
After recording the actions taken,

leave the station.
After entering the base station, check if the generated alarm of the base station
is maintained and conduct visual inspection on the UMP GPS LED state.
o
Green Blinking: Normal
Red: Alarms (CLOCK_DEV_NOT_INIT, STARTUP LOCKING FAIL

FREQUENCE_HOLDOVER_EXCEED, HOLDOVER_24H,
TOD_MSG_MISSED)
Orange: Frequency holdover start status
Items to be inspected
Record the checked GPS LED state.
b After checking the UMP LED state, go to Step 2 if not in the LED solid
state.
If it is in RED solid, follow the GPS inspection procedure described in the

Hardware Addition and Replacement or MBS(eNB) Installation Manual.
2 Remount UMP after dismounting. If the alarm is not cleared, continue with the
Step 4. If it is cleared, record history and continue to monitor the alarm state.
3 Replace the UMP.

Replacement Manual.
If the alarm is cleared after replacing the UMP, record the current status and
28
observe any reoccurrence. Record the fault details and affix them to the faulty
UMP.
If the alarm remains, consult with Samsung for next level of maintenance support.

29
A2100370R UMP MEMORY FAIL

This alarm occurs when there are operation errors (data read/write) in the memory
device.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
Possible Cause
Operation errors (data read/write) in the memory device.
Impact
Remedy


30
Alarm Raised
FW Ver. NEW?
Step 1
No
FW Update
Step 2
Yes
Yes
Collect SW Log
UMP MEMORY FAIL

Alarm Raised?
No
INIT-PRC
(UMP, RESET MODE=HW)
Step 3
UMP MEMORY FAIL

Alarm Raised?
No
Yes
On Site Action
Step 4
End

log.
3 Run the INIT-SYS command to restart the system.

a
Set the RESET_MODE to HW, and then run this command.
b Check whether a UMP MEMORY_FAIL alarm has been declared.

4 If the alarm remains, collect the SW log and share with Samsung for the next
On-site Actions

31
Enter the station
Dismount/mount UMP
Alarm Clear?
Yes
No
1) Dismount the board.

2) Disassemble/assemble the
DDR module. (Check if there is a
foreign material in the socket.)
3) Mount the board.
No
Alarm Clear?
Yes
Clear the situation and

monitoring after logging history
Mount DDR module Conclude

that there is poor
End condition or
foreign material
Replace the board and leave the

station
Unmount the UMP. Disassemble and reassemble the DDR memory module.
Check if there is any foreign material in the memory connector (socket).
2 Mount the UMP and check if an alarm is generated after loading completes.
3 If the alarm is cleared, record the current status and observe any reoccurrence.
4 If the alarm remains, replace the UMP.
Replacement Manual.

32
A2100380R UMP PORT DOWN

This alarm occurs when the backhaul port is down.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
RACK[a]/SHELF[b]/SLOT[c]-UMP[d]/PORT[e]
Possible Cause
A link is down (for example, due to a bad port connection) of the backhaul port.
Impact
The board will not be able to communicate with the LSM or external devices.
Remedy


33
Alarm Raised
UMP FW Ver. NEW?
Step 1
No
UMP FW Update
Reset UMP
Step 2
Yes
No
Check ELINK Status
Step 3
Port Locked?
UMP PORT_DOWN
Clear?
Yes
Yes
Unlock Port
No
Step 4
UMP PORT_DOWN
Clear?
On Site Action
End
b Check the output on whether the VERSION of each firmware is the most
recent one.
After the update, run the INIT-PRC command with the input
PRC_UNIT_TYPE set to UMP to restart the UMP board.
3 Run the RTRV-ELINK-STS command to check whether

ADMINISTRATIVE_STATE is set to linkUnlocked.
4 If ADMINISTRATIVE_STATE is currently set to linkLocked, use the CHGELINK-CONF command to change STATUS to EQUIP and
ADMINISTRATIVE_STATE to linkUnlocked. Check whether the alarm has
been cleared after this.
On-site Actions
34
Enter the station
Check the link status using the

LED of the port (Green LED)
Step 1
Step 9
After checking cable connection
or optical module status,
remount, re-assemble, or
replace the module.
Check the status of an

equipment connected to the port
Step 7
1) Dismount the board.

2) Disassemble/assemble the
DDR module. (Check if there is a
foreign material in the socket.)
3) Mount the board.
Step 10
No
Alarm Clear?
Reset or replace
the module.
Step 8
Yes
Alarm Clear?
Yes
No
Conclude that there is poor

cable connection, poor item, or
poor optical module
Alarm Clear?
Step 11
No
Record the defects in detail to

the RMA TAG
Yes

monitoring after logging history

equipment connection and poor
equipment

installation of DDR module and
foreign material

station
Check the LED status of the port.
Status
Description
Orange blinking (Left)
Ethernet Packet Tx Activity
Green on (Right)
Link Up Status (Rx Activity)
Off
Cable Open
Copper Port
Green
LED
Status
Description
Green On (Left)
Link Up (physical link ready)
Off
Power off, link off, or critical fault

(Right LED is always off.)
Orange
LED
Optical Port
Green OFF
2 Check that the Ethernet cable is correctly connected and that there is no
external damage.
3 Check that the optical cable is correctly connected and that there is no external
damage or bending.
4 Check that the connected optical cables (Single or Multi-Mode) are suitable
for the installed optical module type (Single or Multi-Mode).
35
5 Check that the optical module is supported by the system.

6 Clean the optical module and measure its optical power. Check the measured
optical power against the product specifications in the LTE eNB Installation
Manual. Replace the optical module if necessary.
7 Check the status of the equipment connected to the backhaul port (for example,
router and switch).
8 If the equipment connected to the backhaul port is not working properly, reset
or replace the equipment.
9 Unmount the UMP. Disassemble and reassemble the DDR memory module.
Check if there is any foreign material in the memory connector (socket).
Mount the UMP and check if an alarm is generated after loading completes.
11 If the alarm is not cleared, record the failure details to the RMA TAG and
replace the UMP. Record the details including port connection configuration
status, the part number of mounted optical module, the optical cable type, and
so on.
Replacement Manual.

36
A2100439R UMP ETHERNET HALF DUPLEX

DETECTED
This alarm occurs when the backhaul port status is up and duplex mode is half
duplex.
Basic Information
Severity
Relates to
Category
Location
MINOR
Software
EQUIPMENT
Possible Cause
The backhaul port status is up and duplex mode is half duplex.
Impact
The call service will be degraded due to the high risk of packet loss.
Remedy


37
Alarm Raised
Step 1
retrieve autonego, speed, duplex

Config of both eNB BH and
oppsite Device
Step 2
Config mismatch?
No
Yes
Step 3
Make configure match and

Down and up BH link
Step 4
Clear Alarm ?
INIT-SYS
No
Yes
END
On Site Action
Check the Autonego, Speed, and Duplex settings of both the eNB and the
remote station equipment.
Run the RTRV-ELINK-CONF command.
b Run the RTRV-ELINK-CONF command.

The commands used on the remote stations equipment may differ depending on
the manufacturer, and the following are the commands relevant to each major
equipment manufacturer:
- Cisco: show running-conifig {interface name}
- NETGEAR: show port {<unit/slot/port> | all }
- 3Com: display interface [interface_type | interface_type interface_number]
2 Check whether the Autonego, Speed, and Duplex are all set to the same value.
3 If the Autonego, Speed, and Duplex settings are different from each other, set
them to the same value. If the alarm remains despite the above parameters
being set to the same value, reboot the eNB and check again if the alarm
occurs.
Run the INIT-SYS command.

38
On-site Actions
Check link aggregation status by disconnecting and then connecting the cable
again. If the alarm does not clear, continue with the next step.
2 Replace the cable.

3 If the alarm remains, replace the board.
Replacement Manual.

39
A2116100R ECP DSP RESTART

This alarm occurs when the DSP resets and restarts.
Basic Information
Severity
Relates to
Category
Location
CRITICAL
Software
PROCESSING
RACK[a]/SHELF[b]/SLOT[c]-ECP[d]/DSP[e]
Possible Cause
The DSP resets and restarts (by using the DSP Reset command or replacing the
DSP image).
Impact
Cell services related to the ECP will be unavailable during restart.
Remedy

40
Alarm Raised
Step 1
FW Ver. NEW?
No
FW Update
Step 2
Yes
Yes
Collect SW Log
ECP DSP RESTART

Alarm Raised?
No
Step 3
INIT-DSP (ECP)
Step 4
ECP DSP RESTART

Alarm Raised?
No
Yes
Step 5
INIT-SYS
ECP DSP RESTART

Alarm Raised?
No
Yes
Replace Board
End
Check whether the ECP firmware is the latest version by running the RTRVPRC-FW command.
Set the PRC_UNIT_TYPE to ECP and LOC_TYPE to *, and then run this
command.

After the firmware has been updated, check whether the alarm is raised. If
yes, continue with the next step.
b Run the RTRV-ALM-LIST command.

Check whether the ECP DSP_RESTART alarm has been declared.
3 Run the INIT-DSP command to restart the DSP.

a
Set the BD_ID ECP ID and DSP_ID to DSP ID, and then run this

41
command.
b Check whether the ECP DSP_RESTART alarm has been declared.

a
b Check whether the ECP DSP_RESTART alarm has been declared.

5 If the alarm remains, collect the SW log and replace the faulty board.

42
A2116102R ECP PROCESS DOWN

This alarm occurs when the ECP process is deactivated.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Software
PROCESSING
RACK[a]/SHELF[b]/SLOT[c]-ECP[d]/BLOCK_NAME
Possible Cause
The ECP process is deactivated. You can find the cause by analysing the core file
and log file uploaded to the LSM.
Impact
If the alarm generates continuously in a specific software block, the service will be
unavailable.
Remedy

43
Alarm Raised
Re-activate Alarm
Raised Block
Step 1
Yes
Alarm Cleared
After Repair?
No
Backup the Faulty

NE Block Image
Step 2
Replace Block Image
Yes
Alarm Cleared
After Repair?
No
Collect SW Log and

Restart Board
Step 3
Yes
Alarm Cleared
After Repair?
No
Step 4
Collect SW Log and

Restart NE
Step 5
Backup
LSM Log
End
Activate the block that has raised the alarm.
Re-activate the disabled block by running the INIT-SW:ECP,

applicable block.
44
2 If the alarm remains, replace the block image. Backup the block image for
future analysis.
Backup the block image that continues to deactivate. Use the DNLD-SW,
UDT-SW commands to replace the block image.
applicable block.
3 If the problem cannot be solved by replacing a single block, restart the

applicable board to repair it.
After collecting the SW log, use board restart commands such as INITPRC to carry out the repair.
applicable block.
4 If the problem cannot be solved by restarting the board, reset the NE to repair
it.

applicable block.
5 To analyse the step by step process of clearing the PROCESS_ DOWN alarm,
backup the LSM log.
If the alarm remains, consult with Samsung for the next level of maintenance
support.
The logs are collected in the /log/system/corelog and /log/system/applog paths for
the relevant time.

45
A2116300R ECP DISK FULL

This alarm occurs when the network processor is either not sending or receiving
packets.
Basic Information
Severity
Relates to
Category
Location
Software
QOS
RACK[a]/SHELF[b]/SLOT[c]-ECP[d]
Possible Cause
The threshold can be retrieved by using the RTRV-ALM-THR command.
Impact
Defaults
Minor: 85 %
Major: 90 %
Critical: 95 %
Remedy

46
Alarm Raised
Step 1
Run RTRV-ALM-THR
No

Yes
Run CHG-ALM-THR
Alarm Still Raised?
No
Yes
Collect SW Log
Step 2
Check Other Items
Alarm Still Raised?
Step 3
Alarm Level = Minor
No
Yes
No
Delete LOG
Folder Files
Delete TEMP
Folder Files
Alarm Still Raised?
No
Yes
Replace Board
End

DISK_FULL alarm.

47
If the DISK_FULL threshold is lower than the default value, do the following
steps:
Set the UNIT_TYPE to ECP and ALARM_TYPE to DISK_FULL for the


If the threshold is set higher than the default value, collect the SW Log.
2 Check the following categories in which the DISK_FULL Alarm can occur.
a
The DISK_FULL alarm can occur if more than one passive package exists
as a result of an online upgrade. Use the RTRV-PKG-VER command to
check the number of passive packages.
b After an online upgrade, run the DLT-PASV-PKG command to delete the

passive packages.

a

in LOG and TEMP folders of the ECP board.
b If the level is MINOR, then delete the files in TEMP folder of the ECP
board.

Replacement Manual.

48
A2116301R ECP MEMORY FULL

Basic Information
Severity
Relates to
Category
Location
Software
QOS
Possible Cause
The threshold can be retrieved using the RTRV-ALM-THR command.
Impact
Defaults
Minor: 95 %
Major: 96 %
Critical: 97 %
Remedy

49
Alarm Raised
Step 1
Run RTRV-ALM-THR
No
Yes
Run CHG-ALM-THR
Alarm Still Raised?
No
Yes
Collect SW Log
Step 2
Check Other Items
Alarm Still Raised?
Step 3
Alarm Level = Minor
No
Yes
No
Delete LOG
Folder Files
Delete TEMP
Folder Files
Alarm Still Raised?
No
Yes
Replace Board
End

MEMORY_FULL alarm.

50
If the MEMORY_FULL threshold is lower than the default value, do the

following steps:
Set the UNIT_TYPE to EPC and ALARM_TYPE to MEMORY_FULL

for the CHG-ALM-THR. Enter the default value for each threshold level.
b If the MEMORY_FULL alarm is cleared after changing the threshold

value, terminate the procedure. If not, collect the SW log.

occur.
i

ii

i
Run the UDT-FW-BAT command to delete the firmware image.
ii
Check whether the MEMORY_FULL Alarm is cleared after running


a

in LOG and TEMP folders of the ECP board.
b If the level is MINOR, then delete the files in TEMP folder of the ECP
board.
Check whether the MEMORY_FULL alarm has been cleared.

Replacement Manual.

51
A2116305R ECP PACKET ERROR

Basic Information
Severity
Relates to
Category
Location
MINOR
Software
EQUIPMENT
Possible Cause
The error packets rate exceeded the threshold level.
The threshold value can be retrieved by using RTRV-INVALIDPKT-CONF
command.
Impact
Remedy


52
Alarm Raised
Step 1
Is New F/W
No
Step 2
UMP/ECP FW Update
Yes
SW Log Collection
Step 3
Reset ECP and UMP
Step 4
Alarm Clear?
No
Yes
END
On Site Action
Check whether the firmware is the latest version.
2 If not, update the firmware to the latest version.

a
Check whether the UMP firmware is the latest version by running the
RTRV-PRC-FW command.
Check the output on whether the NAME, VERSION, and
BUILD_TIME of each firmware are the most recent one.
b If the firmware is not the latest version, run the DNLD-FW command to
firmware. If the alarm is declared even when the firmware is up to date,
collect the SW log.
3 Reboot the ECP board where the alarm occurred. After the reboot of the ECP
board completes, reboot the UMP board.
recheck again. If the alarm remains, collect the SW log and share with
Samsung for the next level of maintenance support.
The UMP and ECP collects all files under the /var/log folder, respectively.
On-site Actions
53
Replace the board.

Replacement Manual.

54
A2116302R ECP OVERLOAD

Basic Information
Severity
Relates to
Category
Location
Software
QOS
Possible Cause
Impact
Some software blocks will operate abnormally. If the alarm is generated
continuously, the ECP board will be reset.
Defaults
Minor: 85 %
Major: 90 %
Critical: 95 %
Remedy

55
Alarm Raised
Step 1
Threshold < Default ?
No
Yes
Alarm Still Raised?
No
Yes
Collect SW Log
Step 2
Check Other Items
Alarm Still Raised?
No
Yes
Step 3
No
Yes
SESSION CLOSE
Alarm Still Raised?
No
Yes
Replace Board
Step 4
End

OVERLOAD alarm.
If the OVERLOAD threshold is lower than the default value, do the following
steps:
Set the UNIT_TYPE to ECP and ALARM_TYPE to OVERLOAD for the

56
b If the OVERLOAD alarm is cleared after changing the threshold value,

a
i

alarm is cleared level by level, terminate the procedure.

are repeated.
i
ii
If the alarm is cleared level by level after changing the threshold value,
terminate the procedure.
connected to the ECP. If it is cleared, terminate the procedure.

Replacement Manual.

57
A2116351R ECP CLOCK FAIL

Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
Possible Cause
Any of the following clocks is out of the required frequency range, as monitored
on the EPLD clock monitoring block:
30.72 MHz
10 ms
BFN
Even clock
Impact
The service will be unavailable due to the CPRI failure (RRU interface).
Remedy


58
Alarm Raised
UMP/ECP FW Ver. NEW?
Step 1
No
UMP/ECP FW Update
Step 2
Yes
Yes
Collect SW Log
ECP CLOCK FAIL

Alarm Raised?
No
Step 3
Reset ECP or UMP
Step 4
ECP CLOCK FAIL

Alarm Raised?
No
Yes
On Site Action
End
Run the RTRV-PRC-FW command to check whether the UMP and ECP
firmware is the latest version.

this command.
b Set the PRC_UNIT_TYPE to ECP and LOC_TYPE to *, and then run the
command.
Check the output on whether the NAME, VERSION, and BUILD_TIME

After the firmware has been updated, check whether the alarm is raised:

c
Check whether the ECP CLOCK_FAIL alarm has been declared.
3 Run the INIT-PRC command to restart either the ECP or UMP.

a
When the alarm is raised only for a certain ECP:

Run the INIT-PRC command to restart only the ECP with the alarm
raised. Set the PRC_UNIT_TYPE, PRC_INIT_ID, and RESET_MODE to
ECP, ECP Number, and HW, and then run this command.
b When the alarm is raised for all ECPs:

Run the INIT-PRC command to restart the UMP. Set PRC_UNIT_TYPE
59
to UMP and RESET_MODE to HW, and then run this command.
If the alarm remains even after the UMP restart, run the INIT-PRC
command to restart each of the ECPs that have declared the alarm. Set the
PRC_UNIT_TYPE, PRC_INIT_ID, and RESET_MODE to ECP, ECP
Number, and HW, and then run the command.
On-site Actions
Alarm generated
Enter the base station
Step 1
After dismounting ECP, execute

visual inspection on ECP and
backboard edge pins.
Broken/damaged?
Step 3
Remount ECP
No
Alarm
Clear?
Yes
Step 2
Yes
No
When ECP damaged or broken:

replace ECP
Backboard damaged: Replace
UADU
Step 4
After replacing ECP, leave the

base station. Describe the
defects in detail on the defective
ECP.
After recording history, clear the

alarm situation and start
monitoring.
Check if the generated alarm of the base station is maintained in LSM after
entering the base station and conduct visual inspection on the DU shelf state.
o
Record if anything significant to report is found after inspecting the front

side of the DU shelf.
After dismounting the ECP, record if anything significant to report is

found such as damages, water mark etc. within the board.
Record if any damages are found on the ECP pin after inspection.
Record if any damages are found on the DU shelf backboard pin after
inspection.

60
If the ECP or the backboard of DU shelf found damaged, execute Step

2.
If no defects found in the ECP or in the backboard of the DU shelf,
execute Step 3.
2 Replace the broken or damaged part.

a
If the ECP found damaged or broken, replace the defective ECP.
b If the backboard of the DU shelf damaged, replace the defective DU shelf.

c
After recording the updated history, continue to monitor the alarm state.
3 If nothing significant to report found in the DU shelf or the ECP after visual
inspection, remount the ECP.
If the alarm is cleared after remounting the ECP, continue to monitor the
alarm state after recording history.
b If the alarm is maintained after remounting, continue with the Step 4.

4 Replace the ECP.
For information on ECP replacement, see LTE eNB Hardware Addition and
Replacement Manual.
If the alarm is cleared, record the current status and observe any reoccurrence.
Record the fault details and affix them to the faulty ECP.
support.

61
A2116366R ECP BOARD DELETION

This alarm occurs when a board is unmounted.
Basic Information
Severity
Relates to
Category
Location
CRITICAL
Hardware
EQUIPMENT
Possible Cause
The board is unmounted.
Impact
Cell services related to the ECP will be unavailable.
Remedy


62
Alarm Raised
No
Step 1
UMP-ECP Communication
Possible?
Yes
FW Ver. NEW?
Step 2
No
FW Update
Step 3
Yes
Yes
Collect SW Log
Step 4
ECP BOARD DELETION

Alarm Raised?
No
ECP Restart
ECP BOARD DELETION

Alarm Raised?
Step 5
No
Yes
System Restart
ECP BOARD DELETION

Alarm Raised?
Step 6
No
Yes
On Site Action
End
Run the RTRV-PRC-INVT command to check whether communication

between the UMP and ECP is normal.
Set the PRC_UNIT_TYPE to ECP and PRC_ID to ECP ID, and then run
this command.
b Check whether the output is No Data. If it is, perform the onsite actions, as
communication between the UMP and ECP is not possible.
2 If the Step 1 result is not No Data, run the RTRV-PRC-FW command to check
whether the ECP firmware is the latest version.
Set the PRC_UNIT_TYPE to ECP, and then run this command.

63
4 If the alarm is raised even when the firmware is the latest version, collect the
SW log and then restart the ECP by running the INIT-PRC command with
the ECP ID that has raised the alarm.
5 If the alarm is not cleared even after restarting the ECP, run the INIT-SYS
command to restart the system.
On-site Actions
Alarm Occurs
Step 2
Step 4
Site Visit
Conduct Visual Inspection on

ECP, Backboard, and Edge
Pin after ECP Remounting
Remove and Remount ECP
Damage/Defect ?
Step 6
Conduct Visual Inspection on
UMP, Backboard, and Edge
Pin after UMP Remounting
No
Damage/Defect ?
Yes
Step 3
No
Alarm
Clear?
Upon ECP Damage/Defect:

Replace ECP
Upon Backboard Damage:
Replace UADU
Replace ECP
No
Yes
Alarm
Clear?
Yes
No
Step 5
Step 7
Upon UMP Damage/Defect:

Replace UMP
Upon Backboard Damage:
Replace UADU
Remount the board before

ECP Replacement, Replace
UMP
Yes
Yes
Alarm
Clear?
No
Step 8
Clear Situation and Monitor

after Recording History
Replace the Entire UADU
At the site, check if the base station alarm remains activated in LSM. If the
alarm remains, remove and remount the ECP.
If the alarm is not cleared, continue with the Step 2. If cleared, record history
and continue to monitor the alarm state.
2 After removal and remounting of the ECP, check if there are any damages,
water stains, and other remarks inside the ECP and record the details.
Check if the DU shelf backboard pin against the ECP is damaged and record
damage Y/N. (If the environment is dark, use a lamp or torch light for
64
thorough visual check.)

o
If there are any damages found on the backboard of the DU shelf or ECP,
continue with the Step 3.
If there are no errors found on the backboard of the DU shelf or ECP,

3 When the ECP or the backboard of the DU shelf is damaged or defective,

replace it.
Record history and continue to monitor the alarm state.
4 After removing the UMP, check if there are any damages, water stain, or other
remarks inside it.
Check if the DU shelf backboard pin against the UMP is damaged and record
the results. (If the environment is dark, use a lamp or torch light for thorough
visual check.)
o
If there are any damages found on the backboard of the DU shelf or UMP,
If there are no errors found on the backboard of the DU shelf or UMP,

5 When the UMP or the backboard of the DU shelf is damaged or defective,

replace it.
Record action history and continue to monitor the alarm state.
6 Replace the ECP.

o
If the alarm is not cleared, continue with the Step 7.
If the alarm is cleared, record history log and continue to monitor the
alarm state.
7 Since the error has not been caused by ECP, re-mount the ECP before
replacement, and then replace the UMP.
Replace the UMP.
o
If it is cleared, record action history and continue to monitor the alarm

state.
8 Replace the entire UADU. After recording action history, continue to monitor
the alarm state.
For information on replacement of ECP and other parts, see LTE eNB Hardware
Addition and Replacement Manual.
If the highest-level alarm BOARD DELETION is generated, the previous alarms

that preceded it are all cleared. Alarms generated on the board are filtered and will
not be reported while the BOARD DELETION alarm remains active.

65
A2116367R ECP POWER FAIL

This alarm occurs when there is a problem with the power supply.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
Possible Cause
All of the voltage values monitored on the board have a deviation of more than
10 %. There are nine voltage values ranging from 0.9 V through 3.3 V that are
being monitored on the board.
Impact
Remedy


66
Alarm Raised
No
Step 1
Possible?
Yes
FW Ver. NEW?
Step 2
No
FW Update
Step 3
Yes
Yes
Collect SW Log
Step 4
ECP POWER FAIL

Alarm Raised?
No
ECP Restart
ECP POWER FAIL

Alarm Raised?
Step 5
No
Yes
System Restart
ECP POWER FAIL

Alarm Raised?
Step 6
No
Yes
On Site Action
End

Set the PRC_UNIT_TYPE to ECP and PRC_ID ECP ID, and then run this
command.
b Check whether the output is No Data. If it is, perform the on-site actions of,
as communication between the UMP and ECP is not possible.

67
5 If the alarm remains even after restarting the ECP, run the INIT-SYS
On-site Actions
Alarm Occurs
Alarm
Clear?
Site Visit
Yes
No
Step 2
Step 1
Remove ECP, Conduct Visual

Check, and Remount
LED On Y/N
Off
Remove and Remount ECP
On
Alarm
Clear?
No
Step 3
Replace ECP
Yes
Clear Situation and Monitor after

Recording History
At the site, check if the alarm remains activated in LSM. If the alarm is on,
remove the ECP.
After ECP removal, check if there are any damages, water stain, or other
remarks inside the board. Record the details and remount it.
o
If the LED is not on, replace the ECP. After recording action history,
continuously monitor the alarm state.
If the LED is on, however, the alarm is not cleared, continue with the Step
2.
If the LED is on and the alarm is cleared, record action history and
continue to monitor the alarm state.
2 Remove and remount the ECP.

68
If the alarm is cleared, record action history and continue to monitor the
alarm state.
3 Replace the ECP.

For information on ECP replacement, refer the LTE eNB Hardware Addition and
Replacement Manual.
If the alarm remains, consult the next level of maintenance with Samsung.

69
A2116368R ECP FUNCTION FAIL

This alarm occurs when a specific function fails in the software.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
Possible Cause
If a specific function fails in the software, the Hardware Function Fail alarm signal
occurs when the CPU writes it into the Function Fail Register of the PLD.
In addition, the Function Fail alarm signal occurs when a push button reset, a
watchdog reset, or a self-reset occurs.
Impact
Remedy


70
Alarm Raised
No
Step 1
Possible?
Yes
FW Ver. NEW?
Step 2
No
FW Update
Step 3
Yes
Yes
Collect SW Log
Step 4
ECP FUNCTION FAIL

Alarm Raised?
No
ECP Restart
ECP FUNCTION FAIL

Alarm Raised?
Step 5
No
Yes
System Restart
ECP FUNCTION FAIL

Alarm Raised?
Step 6
No
Yes
On Site Action
End

Set the PRC_UNIT_TYPE to ECP and PRC_ID ECP ID, and then run this
command.
b Check whether the output is No Data. If it is, perform the on-site actions of,
as communication between the UMP and ECP is not possible.
whether the ECP firmware is the latest version

71
5 If the alarm remains even after restarting the ECP, run the INIT-SYS

72
On-site Actions
Alarm Occurs
Step 2
Step 1
Site Visit (Check the Newest F/W

before Site Visit)
Use RS-232 Debug Cable to

Connect ECP to Laptop and
Obtain F/W Info, Remount ECP
Remove ECP, Conduct Visual

Check, and Remount
Alarm Cleared after 5

Minutes Y/N
Yes
No
Step 3
Alarm Cleared after 5
Minutes Y/N
No
Replace ECP
Yes
Clear Situation and Monitor after

Recording History
If the ECP F/W is not found before the site visit, carry along a laptop and
UART debug cable.
After ECP removal, check for any damages, water stains, other remarks inside
the board. Record details and re-mount it.
o
If the alarm is not cleared after 5 minutes, continue with the Step 2.
If the alarm is cleared after 5 minutes, record action history and continue
to monitor the alarm state.
2 Use a UART debug cable to connect the ECP DEGO port to the laptop and run
Tetraterm program.
[Teraterm Configurations]
-
Baudrate: 115200,
Data: 8bit,
Parity: none
Stop: 1bit
Flow control: none
Mount the laptop ECP.

When the Booter Message appears on Teraterm, press Ctrl+C twice. After
approximately 30 seconds, it will stop at Booter Prompt. Then, use the
command gettail 0and the F/W information will be obtained. (To be used in
the following analysis)

73
9 pin D-sub type
<ECP Board Connection>
USB Type
<UART Debug Cable>
<Laptop Connection>
[Connecting to a Laptop Using a UART Debug Cable]

Re-mount the ECP. Without a laptop, skip the previous procedures for
obtaining the firmware log.
o
If the alarm is not cleared after 5 minutes, continue with the Step 3.
alarm state.
3 Replace the ECP.

Replacement Manual.
If the alarm is cleared after replacing the ECP, record the current status and
observe any reoccurrence. Record the fault details and affix them to the faulty ECP.
If the alarm remains, consult the next level of maintenance with Samsung.
To check the Fail Safe Boot Mode switch:
Check the on/off status of the S1 switch on the board. The S1 switch location is
shown in the figure below.

74
If the switch is OFF, change it to the ON.

The default position of the S1 switch is ON. However, if the switch is OFF, the
board cannot be loaded. Make sure the switch is set to ON before mounting the
board.

75
A2116372R ECP DSP FAIL

This alarm occurs when there is a communication problem between the UMP and
DSP.
Basic Information
Severity
Relates to
Category
Location
CRITICAL
Software
EQUIPMENT
Possible Cause
This alarm issues when the:
DSP initialization is not completed.
UMP cannot receive the keep-alive response from the DSP.
Core, modem, or FPGA of the DSP is not operating normally.
Impact
Cell services related to the DSP will be unavailable.
Remedy

76
Alarm Raised
Step 1
FW Ver. NEW?
No
FW Update
Step 2
Yes
Yes
Collect SW Log
ECP DSP FAIL

Alarm Raised?
No
Step 3
INIT-DSP (ECP)
Step 4
ECP DSP FAIL

Alarm Raised?
No
Yes
Step 5
INIT-SYS
ECP DSP FAIL

Alarm Raised?
No
Yes
Replace Board
End
command.

After the firmware has been updated, check whether the alarm is raised:
Run the RTRV-ALM-LIST command.

Check whether the ECP DSP_FAIL alarm has been declared.

a
Set the BD_ID ECP ID and DSP_ID to DSP ID, and then run this
command.

77
b Check whether the ECP DSP_FAIL alarm has been declared.

a
b Check whether the UMP DSP_FAIL alarm has been declared.


78
A2116376R ECP CPRI FAIL

This alarm occurs when the Loss of Signal (LOS) or Loss of Frame (LOF) occurs
in the Common Platform Radio Interface (CPRI) layer.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
RACK[a]/SHELF[b]/SLOT[c]-ECP[d]/PORT[e]
Possible Cause
This alarm issues when:
LOS: More than 16 8B/10B violations are detected in the overall CPRI hyper
frame.
LOF: The hyper frame alignment (BYTE=K28.5 & Y=W=X=0) is not

achieved on the CPRI synchronization state.
Impact
Cell services related to the RRH that is connected to the relevant ECP port will be
unavailable.
Remedy


79
Alarm Raised
RRH/ECP FW Ver. NEW?
Step 1
No
RRH/ECP FW Update
Yes
Yes
Restart RRH
Step 2
ECP CPRI FAIL

Alarm Raised?
No
ECP CPRI FAIL

Alarm Raised?
No
Yes
Restart ECP
Step 3
ECP CPRI FAIL

Alarm Raised?
No
Yes
Step 4
Collect SW Log
On Site Action
End
Check whether the RRH firmware is the latest version by running the RTRVRRH-INVT command.
Set the CONN_BD_ID to ECP Number and CONN_PORT_ID to Port

Number, and then run this command.
b Check whether the FW_VERSION on the output window displays the

latest version.
firmware.
Check whether the ECP CPRI_FAIL alarm has been declared.
d If the alarm is not cleared, run the RTRV-PRC-FW command to check

i
Set the PRC_UNIT_TYPE to ECP and LOC_TYPE to *, and then run

this command.

80
ii
Check the output on whether the NAME, VERSION, and

BUILD_TIME of each firmware are the most recent one.
iii If the firmware is not the latest version, run the DNLD-FW command
to download the latest version and the UDT-FW command to update
the firmware.
Check whether the ECP CPRI_FAIL alarm has been declared.
2 Run the INIT-RRH command to restart the RRH connected to the ECP.
a
Set the CONN_BD_ID ECP Number and CONN_PORT_ID to Port

b Check whether the ECP CPRI_FAIL alarm has been declared.

3 If the alarm is not cleared, run the INIT-PRC command to restart the ECP.
a
Set PRC_UNIT_TYPE, PRC_INIT_ID, and RESET_MODE to ECP, ECP

Number, and HW, and then run this command.
b Check whether the ECP CPRI_FAIL alarm has been declared.

On-site Actions

81
Step 3
ECP mounting state
Alarm occurrence
Broken/damage ?
Yes
Replace ECP

No
Remount ECP
Step 1
Inspect optic modules and

connection state of optic cables
No
Alarm
Clear?
Optic modules and cables
are connected normally?
Yes
Step 5
Remount the optic module and

optic cable
Alarm
Clear?
Step 6
Alarm Clear?
No
Yes
No
Replace ECP
No
Step 2
Yes
Yes
No
Inspect RRH (refer to RRH

inspection manual)
As the ECP is not defective,
remount it.
After recording the history, clear

the alarm situation and start
monitoring.
o

side of the ECP.
Record the mounting state of the optical cable after inspection.

If mounting status of the optical cable or module is abnormal, continue
with the Step 2.
If mounting state of the optical cable or module is normal, continue
with the Step 3.
2 Remount the optical cable or module. After recording history, continue to

3 Check if any damages are found on the ECP after dismounting it.
After dismounting the ECP, record if anything significant to report is found
such as damages, water mark, and so on within the board.
o
If the ECP found damaged or broken, replace the defective ECP. After
recording the history, keep on monitoring its state.

82
If nothing significant to report found on the external side of the ECP,

4 Remount the ECP. If the alarm is cleared, continue to monitor the alarm state
after recording history. If the alarm remains, continue with the Step 5.
5 Replace the ECP.

o
If the alarm is cleared after replacement, continue to monitor the alarm

state after recording history.
If the alarm remains after replacement, continue with the Step 6.
6 As the ECP is not defective, remount the replaced ECP. As RRH probably
seems to be the main cause of the defect, inspect the RRH.
Replacement Manual.

83
A2116378R ECP OPTIC TRANSCEIVER RX LOS

This alarm occurs when the optical cable is disconnected or when the optical
signal level falls below the normal parameters.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
Possible Cause
The optical cable is disconnected or the optical signal level is below the normal
parameters.
Impact
The service will be disabled for the link.
Remedy


84
Alarm Raised
ECP FW Ver. NEW?
Step 1
No
ECP FW Update
Yes
Step 2
Yes
Restart ECP
ECP OPTIC
TRANSCEIVER RX LOS
Alarm Raised?
No
ECP OPTIC
TRANSCEIVER RX LOS
Alarm Raised?
No
Yes
Step 3
Collect SW Log
On Site Action
End
Run the RTRV-PRC-FW command to check whether the ECP firmware is the
latest version.
command.

firmware.
d Check whether the ECP OPTIC_TRANCEIVER_RX_LOS alarm has been

declared.
a
Set PRC_UNIT_TYPE, PRC_INIT_ID, and RESET_MODE to ECP, ECP

Number, and HW, and then run this command.
b Check whether the ECP OPTIC_TRANCEIVER_RX_LOS alarm has been

declared.

85
On-site Actions
Step 3
Step 1
Alarm occurrence
Visual inspection on ECP

mounting state
Broken/damaged ?
Yes
Replace the ECP.
No
Inspect optic modules
and connection status of
optic cables
Remount ECP
Step 4
Alarm
Clear?
Optic modules and
cables are connected
normally?
Step 2
No
Yes
Step 5
No
Yes
Change the location of

optic cables.
Remount the optic

module and optic cable
Alarm
Clear?
No
Measure the optic power,

inspect the environment
and RRH (Refer to RRH
manual)
Yes
Step 6 Replace the optic module.
Alarm
Clear?
No
Alarm
Clear?
Yes
Yes
No
Step 7
After recording history,

clear the situation and
start monitoring.
Replace the ECP.
check if the generated alarm is maintained in LSM after entering the base
station and conduct visual inspection on the state of DU shelf.
o
Record if anything significant to report is found on the front side of the

ECP.
Record the mounting state of optical cables or modules after inspection.

If mounting status of the optical cable or module is abnormal, continue

86
with the Step 2.

If mounting statue of the optical cable or module is normal, continue
with the Step 3.
2 Remount the optical cable or module. After recording history, continue to

3 Remount the optical cable or module. Check if any damages are found on the
ECP after dismounting it.
such as damages, water mark etc. within the board.
o
recording the history, continue to monitor its state.
If noting significant to report found on the external side of the ECP,

5 Check the optic module by connecting its cable from the defective port to
other optic module of a normal port.
o
If the alarm is cleared after the mounting, continue with the Step 6. After
recording history, continue to monitor the alarm state.
If the alarm is maintained after the mounting, measure the optic power as
the defect is not caused by the ECP or optic module. If the optic power
found abnormal, inspect the optic environment or RRH.
6 Replace the optic module, which is found to be abnormal.

o
If the alarm is cleared, record history and continue to monitor the alarm
state.
If the alarm is maintained, continue with the Step 7.
7 Replace the ECP.

Replacement Manual.
support.

87
A2116379R ECP OPTIC TRANSCEIVER TX

FAULT
This alarm occurs when the monitored power level of the signal generated by the
laser diode in the optical module is abnormal.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
Possible Cause
The monitored power level of the laser diode signal in the optical module
(modulation current and bias current) is abnormal.
Impact
The service will be disabled for the link.
Remedy


88
Alarm Raised
ECP FW Ver. NEW?
Step 1
No
ECP FW Update
Yes
Step 2
Yes
Reset ECP
ECP OPTIC
TRANSCEIVER TX
FAULT Alarm Raised?
No
ECP OPTIC
TRANSCEIVER TX
FAULT Alarm Raised?
No
Yes
Step 3
Collect SW Log
On Site Action
End
Run the RTRV-PRC-FW command to check whether the ECP firmware is the
latest version.
command.

firmware.
d If the alarm is raised even when the firmware is the latest version, continue
with the next step.
Check whether the ECP OPTIC_TRANSCEIVER_TX_FAULT alarm has

been declared.
a
Set the PRC_UNIT_TYPE, PRC_INIT_ID, and RESET_MODE to ECP,

ECP Number, and HW, and then run this command.
b Check whether the ECP OPTIC_TRANCEIVER_TX_FAULT alarm has

been declared.

89
On-site Actions
Step 3 Check ECP dismounting

and conduct visual
inspection
Alarm occurrence
Step 1
Broken/damaged?
Yes
Replace the ECP
No
Check mounting state of
the optic module
Step 4
Remount the ECP
Alarm
Clear?
Optic modules are
connected normally?
Step 2
No
Yes
Step 5
No
Yes
Change the location of

the optic module
Remount the optic

module
Alarm
Clear?
Yes
Replace the ECP
No
Step 6 Replace the optic module
Alarm
Clear?
After recording history,

clear the situation and
keep on monitoring
No
Yes
check if the generated alarm is maintained in LSM after entering the base
station and conduct visual inspection on the state of DU shelf.
o
Record if anything significant to report is found on the front side of the

ECP.
Record mounting state of optical cables or modules after inspection

If mounting state of the optic module is abnormal, continue with the
Step 2.
If mounting state of the optic module is normal, continue with the Step
3.

90
2 Remount the optic module. After recording history, continue to monitor the
alarm state.
3 Remount the optic module. Check if are any damages are found on the ECP
after dismounting it.
such as damages, water mark etc. within the board.
o
recording the history, continue to monitor its state.
If noting significant to report found on the external side of the ECP,

5 Mount the optical cable from the defective port to other optic module of a
normal port.
o
If the alarm is cleared after the optic module mounted on the other normal
port, replace the ECP as the optic module is not defective. After recording
history, continue to monitor the alarm state.
If the alarm occurs in the corresponding port after the optic module is
mounted to the other normal port, continue with the Step 6, as the optic
module seems defective.
6 Replace the optic module. After recording history, continue to monitor the
alarm state.
Replacement Manual.

91
A2116381R ECP COMMUNICATION FAIL

ECP.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Software
EQUIPMENT
Possible Cause
The main processor (UMP) did not receive the keep-alive response from the ECP.
Impact
Remedy

92
Alarm Raised
FW Ver. NEW?
Step 1
No
FW Update
Yes
Yes
ECP Restart
Step 2
ECP
COMMUNICATION FAIL
Alarm Raised?
No
ECP
COMMUNICATION FAIL
Alarm Not Cleared?
No
Yes
System Restart
Step 3
ECP
COMMUNICATION FAIL
Alarm Not Cleared?
No
Yes
Step 4
Restart FM Block
ECP
COMMUNICATION FAIL
Alarm Not Cleared?
No
Yes
Collect SW Log
Step 5
ECP
COMMUNICATION FAIL
Alarm Not Cleared?
No
Yes
Replace Board
Step 6
End
command.

93
download the latest version and the UDT-RRH-FW command to update the
firmware.
d After the firmware has been updated, check whether the alarm is raised.
e
Check whether the ECP COMMUNICATION FAIL alarm has been

declared.
2 If the alarm is not cleared, run the INIT-PRC command to restart the ECP
that has raised the alarm.
Check whether the alarm has been raised after the ECP restart. If not,
terminate the procedure. If yes, continue with the next step.

Check whether the alarm has been raised after the system restart. If not,
4 Reset the FM block.

a
Set the PRC_UNIT_TYPE, PRC_UNIT_ID, and SW_UNIT_NAME to

ECP, Unit Number, and FM respectively, and then run the INIT-SW
command to restart the FM block.
b Check whether the alarm has been raised after the FM restart. If not,
5 Collect the SW log and share with Samsung for the next level of maintenance
support.

Replacement Manual.
To check the Fail Safe Boot Mode switch:
Check the on/off status of the S1 switch on the board. The S1 switch location is
shown in the figure below.

94
S1
S1
ON
If the switch is OFF, change it to the ON.

The default position of the S1 switch is ON. However, if the switch is OFF, the
board cannot be loaded. Make sure the switch is set to ON before mounting the
board.

95
A2116607R ECP SFN FAIL

This alarm occurs when there is no increase or decrease in SFN for more than 10
consecutive measurements at 10 ms intervals.
Basic Information
Severity
Relates to
Category
Location
CRITICAL
Hardware
EQUIPMENT
Possible Cause
The SFN is measured at every 10 ms. If there is no increase or decrease in SFN for
more than 10 consecutive measurements, an alarm is generated.
Impact
This alarm does not have any impact on the system.
Remedy


96
Alarm Raised
GPSR Alarm, UMP/ECP

Clock Fail Alarm Raised?
Step 1
Yes
Actions To Clear Each Alarm
No
Step 2
Yes
DSP Restart
ECP SFN FAIL

Alarm Raised?
No
ECP SFN FAIL

Alarm Raised?
Step 3
ECP Restart
ECP SFN FAIL

Alarm Raised?
Step 4
System Restart
Step 5
ECP SFN FAIL

Alarm Raised?
Collect SW Log,
On Site Action
No
No
No
End
Run the RTRV-ALM-LIST command to check whether the GPSR alarm,

UMP Clock alarm, and ECP Clock alarm have been raised.
Check for alarms that have UNIT_TYPE set to GPSR, UMP, or ECP, and
ALARM_TYPE set to CLOCK_FAIL.
b If an alarm is on the list, follow the remedy.

2 If the alarms listed on Step 1 have not been declared or the SFN FAIL alarm
remains even after carrying out the remedy for each alarm, run the INIT-DSP
command to restart the DSP that has raised the alarm.
3 If the alarm is not cleared after the DSP restart, run the INIT- PRC command
to restart the ECP which has raised the alarm.
4 If the alarm is not cleared after the ECP restart, run the INIT-SYS command
97
to restart the system.
On-site Actions
Alarm generated
Step 1
After dismounting ECP, execute

visual inspection on ECP and
backboard edge pins.
Broken/damaged ?
Remount ECP
No
Alarm Clear?
Yes
Step 2
Step 3
Yes
No
When ECP damaged or broken:

replace ECP
Backboard damaged: Replace
UADU
Replace ECP
Alarm Clear?
Step 4
Yes
No
After replacing UMP, remounting

the ECP
Step 5
After recording history, clear the

alarm situation and start
monitoring.
o

side of the DU shelf.
After dismounting the ECP, record if anything significant to report is

found such as damages, water mark etc. within the board.

98
Record if any damages are found on the ECP pin after inspection.
Record if any damages are found on the DU shelf backboard pin after
inspection.
If the ECP or the backboard of DU shelf found damaged, continue with
the Step 2.
If no defects found in the ECP or in the backboard of the DU shelf,
2 Replace the broken or damaged part.

After record the updated history, continue to monitor the alarm state.
3 If nothing significant to report found in the DU shelf or the ECP after visual
inspection, remount the ECP.
o
If the alarm is cleared after the remounting the ECP, continue to monitor
the alarm state after recording history.
If the alarm is maintained after the remounting, continue with the Step 4.
4 Replace the ECP

o
If the alarm is not cleared, execute Step 5.
If the alarm is cleared after the replacing ECP, keep on monitoring the
alarm state after recording history.
5 After replacing the UMP, remounting the ECP.

After recording history, clear the alarm situation, and continue to monitor the
alarm state.
For information on ECP and UMP replacement, see LTE eNB Hardware Addition
and Replacement Manual.

99
A2149216R RRH TEMPERATURE HIGH

This alarm occurs when the value of the RF unit temperature sensor is above the
threshold.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
ENVIRONMENT
RRH[a_b_c]-RRH[a_b_c]
Possible Cause
The value of the RF unit temperature sensor is above the threshold.
Impact
The service (call) will be unavailable.
Remedy


100
Alarm Raised
FW Ver. NEW?
Step 1
No
FW Update
Yes
Yes
Run RTRV-RRH-STS
Check TEMP[C]
RRH TEMPERATURE
HIGH Alarm Raised?
No
Step 2
INIT-RRH
Step 3
RRH TEMPERATURE
HIGH Alarm Raised?
No
Yes
Collect SW, RRH Log
On Site Action
End


latest version.
firmware.
d Check whether the RRH DC_INPUT_FAIL alarm has been declared.

2 If the alarm is not cleared, run the RTRV-RRH-STS command to check the
RRH temperature.
Set the CONN_BOARD_ID and CONN_PORT _ID to the target RRH

values, and then run this command.
b Check the TEMPERATURE[C] value on the output window.

a

101
b Check whether the RRH TEMPERATURE_HIGH alarm has been

declared.
4 If the alarm remains, collect the SW and RRH logs and share with Samsung
for the next level of maintenance support.
On-site Actions
RRH Temperature High Alarm
Occurs
Check RRH Installed State and

External Environment
Installation/Environment
Normal Y/N
No
Take Action on Installation and

Environmental Issues
Yes
No
RRH Reset
Alarm Cleared Y/N

Yes
Alarm Cleared Y/N
Yes
Replace RRH
Record Action History and Leave
At the site, check if the alarm is still active in the LSM.
2 Check the state of the installed RRH and conduct visual inspection on the
external environment.
o
Check if the antenna cable to RRH is normally connected and if the RRH
is normally mounted to the pole. If not, take corrective actions.
If foreign substances are found on the radiation fin preventing the air flow,
eliminate them.

102
[RRH front
radiation
fin]
[ RRH
[RRH rear
radiation
fin] ]
[ RRH
Check if there are external radiation elements that may change temperature
around the RRH. If found, take a proper action to fix the condition.
3 If the installation state is normal, reset the corresponding RRH and check
whether it clears the alarm.
4 If the alarm remains, replace the RRH.

For information on RRH replacement, see LTE eNB Hardware Addition and
Replacement Manual.

103
A2149338R RET MOTOR JAM

This alarm occurs when the motor does not move.
Basic Information
Severity
Relates to
Category
Location
MINOR
Hardware
EQUIPMENT
Possible Cause
The motor does not move.
Impact
The RET controller will not be able to control the actuator for SET TILT,
CALIBRATION, and SELF TEST.
Remedy


104
Alarm Raised
FW Ver. NEW?
Step 1
No
FW Update
Yes
Step 2
Yes
INIT-ALD
Alarm Raised?
No
Alarm Raised?
Step 3
No
Yes
Collect Log
On Site Action
End
Check whether the RET firmware is the latest version by executing the RTRVALD-INVT command.


latest version.
download the latest version and the UDT-ALD-FW command to update the
firmware.
d Check whether the RET_MOTOR_JAM alarm has been declared.

2 Reboot the RET by executing the INIT-ALD command.
a

b Check whether the RET_MOTOR_JAM alarm has been declared.

On-site Actions
105
RET Motor Jam Alarm Raised
No
Check the antenna and the

external connection of the RET
Step 1
Step 2
Take action for abnormal

installation status and abnormal
environmental factors
No
Are the installation status

and external environment
status normal?
Yes
No
Step 3
Alarm Clear?
Unmount the RET unit
Yes
Check if the RET unit's

connecting part is normal
No
Check if the antenna is

abnormal
Yes
Step 4
Remount the RET unit
Yes
No
Yes
Replace the antenna and remove
the RET unit
Alarm Clear?
No
Replace the RET unit
Step 5
Summarize actions taken and

exit the station
2 Check the antenna installation status and the external environment where the
RET unit is installed.
Check if the RET unit and the AISG cable attached to it are connected
normally. If not, then take necessary actions.
3 If installation status is normal, unmount the RET unit and check if there is
damage to the connecting part or if connectivity is normal. If the part of the
antenna that connects to the RET unit is damaged, replace the antenna, connect
the new antenna to the RET unit, and then check if the alarm clears.
4 If the connecting parts of the antenna and the RET unit are not damaged, and
connectivity is normal, remount the RET unit and check if the alarm clears.
5 If the alarm remains, replace the RET unit.

106
For information on RET unit replacement, consult with Samsung.

107
A2149339R RET ACTUATOR JAM

This alarm occurs when the actuator jam has been detected.
Basic Information
Severity
Relates to
Category
Location
MINOR
Hardware
EQUIPMENT
Possible Cause
An actuator jam has been detected. There is no movement of the actuator; however
movement of the motor was detected.
Impact
The RET controller will not be able to control the actuator for SET TILT,
CALIBRATION, and SELF TEST.
Remedy


108
Alarm Raised
FW Ver. NEW?
Step 1
No
FW Update
Yes
Step 2
Yes
INIT-ALD
Alarm Raised?
No
Alarm Raised?
Step 3
No
Yes
Collect Log
On Site Action
End


latest version.
firmware.
d Check whether the RET_ACTUATOR_JAM alarm has been declared.

a

b Check whether the RET_ACTUATOR_JAM alarm has been declared.

On-site Actions
109
RET Actuator Jam Alarm Raised
No

Step 1
Step 2

No

status normal?
Yes
No
Step 3
Alarm Clear?
Yes

No

abnormal
Yes
Step 4
Yes
No
Yes
the RET unit
Alarm Clear?
No
Step 5

exit the station
normally. If not, take necessary actions.
3 If installation status is normal, unmount the RET unit and check if there is
connectivity is normal, remount the RET unit, and check if the alarm clears.

110

111
A2149340R RET NOT CALIBRATED

This alarm occurs when the device has not completed a calibration operation or
calibration has been lost.
Basic Information
Severity
Relates to
Category
Location
MINOR
Hardware
EQUIPMENT
Possible Cause
The device has not completed a calibration operation or calibration has been lost.
Impact
The commands for setting Tilt and Self-Test will not be executed.
Remedy


112
Alarm Raised
FW Ver. NEW?
Step 1
No
FW Update
Yes
Step 2
Yes
INIT-ALD
Alarm Raised?
No
Alarm Raised?
Step 3
No
Yes
Collect Log
On Site Action
End


latest version.
firmware.
d Check whether the RET_NOT_CALIBRATED alarm has been declared.

a

b Check whether the RET_NOT_CALIBRATED alarm has been declared.

On-site Actions
113
RET Not Calibrated Alarm

Raised
No

Step 1
Step 2

No

status normal?
Yes
Step 3
Is Alarm cleared after

calibration?
No
Yes
No

abnormal
Yes
Step 4
Yes
No
Yes
the RET unit
Is Alarm cleared after

calibration?
No
Step 5

exit the station
normally. If not, then take necessary actions.
3 If the installation status is normal, unmount the RET unit and check if there is
connectivity is normal, remount the RET unit and check if the alarm clears.

114

115
A2149341R RET NOT CONFIGURED

This alarm occurs when actuator configuration data is missing.
Basic Information
Severity
Relates to
Category
Location
MINOR
Hardware
EQUIPMENT
Possible Cause
Actuator configuration data is missing.
Impact
The commands for setting Tilt and Self-Test will not be executed.
Remedy


116
Alarm Raised
FW Ver. NEW?
Step 1
No
FW Update
Yes
Step 2
Yes
INIT-ALD
Alarm Raised?
No
Alarm Raised?
Step 3
No
Yes
Collect Log
On Site Action
End


latest version.
firmware.
d Check whether the RET_NOT_CONFIGURED alarm has been declared.

a

b Check whether the RET_NOT_CONFIGURED alarm has been declared.

On-site Actions
117
RET Not Configured Alarm

Raised
Step 1
Check the alarm is still active
Step 2
Perform a RET reset
Step 3
Alarm Clear?
Yes
No
Replace RET unit
Step 4

exit the station
2 Reset the RET unit.

3 Check if the alarm clears.

118
A2149342R RET HW ERROR

This alarm occurs when there is an error in the unclassified hardware.
Basic Information
Severity
Relates to
Category
Location
MINOR
Hardware
EQUIPMENT
Possible Cause
Any hardware error that cannot be classified may not be reported as an alarm until
the fault is likely to be persistent.
Impact
Remedy


119
Alarm Raised
FW Ver. NEW?
Step 1
No
FW Update
Yes
Step 2
Yes
INIT-ALD
Alarm Raised?
No
Alarm Raised?
Step 3
No
Yes
Collect Log
On Site Action
End


latest version.
firmware.
d Check whether the RET_HW_ALARM alarm has been declared.

a

b Check whether the RET_HW_ALARM alarm has been declared.

On-site Actions
120
RET HW Error Alarm Raised
Step 1
Step 2
Perform a RET reset
Step 3
Alarm Clear?
Yes
No
Replace RET unit
Step 4

exit the station


121
A2149343R RET ACTUATOR INTERFERENCE

This alarm occurs when an actuator movement outside the control of the RET unit
has been detected.
Basic Information
Severity
Relates to
Category
Location
MINOR
Hardware
EQUIPMENT
Possible Cause
An actuator movement outside the control of the RET unit has been detected.
Impact
Remedy


122
Alarm Raised
FW Ver. NEW?
Step 1
No
FW Update
Yes
Step 2
Yes
INIT-ALD
Alarm Raised?
No
Alarm Raised?
Step 3
No
Yes
Collect Log
On Site Action
End


latest version.
firmware.
d Check whether the RET_ACTUATOR_INTERFERENCE alarm has been

declared.

a
Set the CONN_BD_ID ECP Number and CONN_PORT_ID to Port

b Check whether the RET_ACTUATOR_INTERFERENCE alarm has been

declared.

123
On-site Actions
RET Actuator Interference Alarm
Raised
Step 1
Step 2
Perform a RET reset
Step 3
Alarm Clear?
Yes
No
Step 4
Execute Calibration
Step 5
Alarm Clear?
Yes
No
Replace RET unit
Step 6

exit the station

3 If the alarm does not clear, perform RET calibration.
For information on the connecting antenna module, see Samsung MBS (LTE)
Installation Manual.
For information on the antenna module replacement, see installation manual of

antenna vendor.
124
A2149351R RRH CLOCK FAIL

This alarm occurs when the clock used inside the RF unit is not normal.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
Possible Cause
The clock used inside the RF unit is not normal. When PLL in the RU is unlocked
or when reference clock supply from CPRI is abnormal.
Impact
Remedy


125
Alarm Raised
Step 1
FW Ver. NEW?
No
FW Update
Yes
Yes
RTRV-ALM-LIST
RRH CLOCK FAIL

Alarm Raised?
No
Step 2
ECP CLOCK
Alarm Raised?
Yes
No
Actions To Clear
ECP CLOCK Alarm
RRH CLOCK FAIL

Alarm Raised?
No
Yes
INIT-RRH
Step 3
RRH CLOCK FAIL

Alarm Raised?
No
Yes
Collect SW, RRH Log
On Site Action
End


latest version.
firmware.

126
d Check whether the RRH CLOCK_FAIL alarm has been declared.

2 If the alarm is not cleared even when the RRH firmware is the latest version,
run the RTRV-ALM-LIST and if an ECP CLOCK_FAIL alarm is on the list,
refer to the ECP CLOCK_FAIL Alarm Remedy.
If an ECP CLOCK_FAIL alarm has not been raised, run the INIT-RRH
command to restart the RRH connected to the ECP (by inputting the
CONN_BD_ID and CONN_PORT_ID).

b Check whether the RRH CLOCK_FAIL alarm has been declared.

On-site Actions
RRH Clock Fail Alarm Occurs
Check CPRI Cable Connection

and Disassemble/Reassemble
after Cleaning the Optic
Connector
Alarm Cleared ?
Yes
No
RRH Reset
Alarm Cleared ?
Yes
No
Replace RRH
Check the connection state between the optical cable and optic module of the
RRH and ECP.

127
[DUCPRI
CPRI Cable]
[ DU
Cable ]
CPRI Cable]
CPRI Cable]
[ RRH_V2
Cable ]
[[RRH_V1
RRH_V1
CPRI Cable
] [RRH_V2CPRI
2 If the connection of the optical cable and optic module is normal, clean the
optical cable connector. Then, re-connect to check for alarm recurrence Y/N.
[IBC Optic Cleaner: P/N 9393]
[IBC Optic Cleaner : P/N 9393]
3 If the alarm is not cleared, reset the corresponding RRH.

4 If the alarm remains, replace the corresponding RRH.
For information on RRH replacement, refer the LTE MBS(eNB) Installation
Manual.
o
If the alarm is not cleared even after the RRH is replaced, check the status
of the ECP that is connected to the RRH. If there is a problem with the
ECP, replace the optic module.
If the alarm remains, replace the ECP.
For information on ECP replacement, refer the LTE eNB Hardware Addition and
Replacement Manual.

128
A2149381R RRH COMMUNICATION FAIL

RRH.
Basic Information
Severity
Relates to
Category
Location
CRITICAL
Software
EQUIPMENT
Possible Cause
The main processor (UMP) has not received the keep-alive response from the
RRH.
Impact
Cell services related to the RRH will be unavailable.
Remedy


129
Alarm Raised
Step 1
FW Ver. New?
Yes
FW Update
NO
Yes
RRH COMMUNICATION
FAIL Alarm Raised?
No
Step 2
Actions To Clear
CPRI Alarm
CPRI Alarm Raised?

No
Yes
Step 3
RRH COMMUNICATION
FAIL Alarm Raised?
No
RRH Restart
RRH COMMUNICATION
FAIL Alarm Raised?
No
Yes
Step 4
Collect SW, RRH Log
On Site Action
End


latest version.
firmware.
d Check whether the RRH COMMUNICATION FAIL alarm has been

declared.
130
2 Run the RTRV-ALM-LIST to check whether the CPRI_FAIL,

OPTIC_TRANSCEIVER_RX_LOS, and OPTIC_TRANSCEIVER_TX_
FAULT alarms have been raised on the optic port of the target RRH. If any of
these alarms have been declared, refer to their remedies.
Check whether the RRH COMMUNICATION FAIL alarm is raised after
following the remedy.
3 If the above alarms have not been raised, run the INIT-RRH command to
restart the target RRH.

b Check whether the RRH COMMUNICATION FAIL alarm has been

declared.
On-site Actions

131
RRH Communication Fail Alarm

Occurs
Check Optic Port LED and

Alarm-occurred Sector
Swap Tx/Rx Connectors of

Defective Port CPRI Cable
Replace Defective Port Optic

Module
Check P/N of the Optic Module
upon Replacement
Yes
No
Alarm Cleared? Y/N
Yes
Alarm Cleared? Y/N
No
Check LED after Opening RRH

Window
LED Turn On?
No
Check RRU Input Voltage

[Normal Voltage: -40 to -57 V]
Yes
Replace Optic Cable and Optic
Module of RRH.
Check the Optic Module P/N
upon Replacement
Yes
Alarm Cleared? Y/N

No
RRH Reset
Yes
Normal Voltage Y/N

No
Yes
Take Corrective Action after

Rectifier/Power Cable Inspection
Alarm Cleared? Y/N

No
Replace RRH
No
Alarm Cleared? Y/N

Yes
2 Check the LED of the ECP optic port to identify the target sector where a
failure had occurred. The optic port for which LED is turned off indicates the
failure-occurred sector.
132
LED Green Light

Check Point
3 Swap the Tx connector of a defective port CPRI cable with its Rx connector,
and check if the alarm is cleared.
Rx
RXConnector
Connector
Tx
TXConnector
Connector
4 Clean the optic connector of the alarm-occurred port and replace the optic
module. Then, check whether the alarm is cleared.
When replacing the optic module, check its part number. Optic modules for
RJIL RRUs consist of two types: FTLF1326P3BTL-SG and SPP-8F-LRIDFP-SEC.
[IBC optic Cleaner: P/N 9393]

[IBC Optic Cleaner
: P/N 9393]
When the alarm is cleared, record the action history and leave the site. If the
optic module is defective, process RMA of the module.
5 If the alarm remains, check if the LED is on.

For RRH_V1, LED is placed inside and can be checked by opening the
window, whereas it is available from the outside for RRH_V2, as shown in
figures below.

133
LED Check
LED Check
Point
Point
[RRH_V1 LED
[ RRH_V1
LEDCheck]
Check ]
LED Check
Point
LED Check
point
[RRH_V2LED
LED Check]
[ RRH_V2
Check ]
6 If the LED light is turned off, check input voltage from the RRH power input
port (normal range: -40 to -57 V).
[RRH_V1 voltage check point]
[RRH_V2 voltage check point]
If the voltage is not normal, inspect the rectifier and power cable. When the
voltage returns to normal after inspection and proper measurement, continue
with the Step 7.
7 If the LED lamp is on, replace the corresponding optical cable and optic
module of the alarm-occurred RRH with new parts. Check if the alarm cleared.
o
When replacing the optic module, check its part number. Optic modules
used in RJIL RRUs consist of two types: FTLF1326P3BTL-SG and SPP8F-LR-IDFP-SEC.
If the alarm is cleared, record the action history and leave the site. When
an optic power meter is ready, use it to measure the strength of optic
signals received by the RRH and determine whether its optical cable is
defective.
The normal signal strength should be 0.5 to -10.6 dBm. Duplex-type
optical cables are used in the products for India; therefore, the optic signal
of dual Rx path should be measured.

134
Rx Cable
[Optic Power Meter]
Rx Cable
[RRH_V1 Optic cable]
[RRH_V2 Optic cable]
8 If the alarm is not cleared despite the actions taken in Steps 5 and 6, reset the
RRH.

Replacement Manual.

135
A2149384R RRH DC INPUT FAIL

This alarm occurs when the DC power input of the RF unit is not within the
normal parameters.
Basic Information
Severity
Relates to
Category
Location
MINOR
Hardware
EQUIPMENT
Possible Cause
The DC power input of the RF unit is not normal.
Impact
Remedy


136
Alarm Raised
FW Ver. NEW?
Step 1
No
FW Update
Yes
Step 2
Yes
INIT-RRH
RRH DC INPUT FAIL

Alarm Raised?
No
RRH DC INPUT FAIL

Alarm Raised?
Step 3
No
Yes
Collect SW, RRH Log
On Site Action
End


latest version.
firmware.

a

b Check whether the RRH DC_INPUT_FAIL alarm has been declared.

On-site Actions
137
DC Input Fail Alarm Occurs
Check Rectifier Output Voltage

Output Voltage Normal

Y/N?
No
Inspect Rectifier and Take

Corrective Action
No
Inspect Power Cable and Take

Corrective Action
Yes
Check RRH Input Voltage

Input Voltage Normal Y/N?

Yes
RRH Reset
Alarm Cleared Y/N?
Yes
No
Replace RRH
At the site, check input voltage of the rectifier (normal output voltage range is
from -40 to -57 V).
If the output voltage is not normal, the rectifier should be inspected and
appropriate measures need to be taken depending on the inspection result.
2 If the output voltage is normal, check the RRH input voltage (normal input
voltage range is from -40 to -57 V)

138
[RRH_V1 Voltage Checkpoint]
[RRH_V2 Voltage Checkpoint]
If the input voltage is not normal, conduct visual inspection on the power cable
for any disconnected and stripped wires. If defects are found in the inspection
process, replace the power cable. For replacement, refer to RRH Installation
Manual.
3 If the voltage is normal, reset the RRH. Then, check whether the alarm is
cleared.

Replacement Manual.

139
A2149385R RRH DISABLED

This alarm occurs when the RRH is disabled.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
RRH[a_b_c]-RRH[a_b_c]/PATH[d]
Possible Cause
The RRH is disabled due to the following reasons:
Initial status.
A command forced the RRH to shut down.
An alarm caused the RRH to shut down.
Impact
Remedy


140
Alarm Raised
FW Ver. NEW?
Step 1
No
FW Update
Yes
Step 2
Yes
RTRV-RRH-CONF
RRH DISABLED
Alarm Raised?
No
PATH_ENABLE_STATE
User Disabled?
Yes
No
Step 3
RTRV-CELL-STS
ADMIN STATE locked?
Yes
No
Step 4
Collect SW, RRH Logs
On Site Action
End


latest version.
firmware.

2 If the alarm is not cleared, run the RTRV-RRH-CONF command to check
whether the PATH_ENABLE_STATE on the PATH with the declared alarm
is set to UserDisabled.
Check whether the output of PATH_ENABLE_STATE on the PATH with the
declared alarm is set to UserDisabled.
141
3 Run the RTRV-CELL-STS command to check whether the

ADMINISTRATIVE_STATE of Cells allocated to the target RRH are set to
locked.
Check whether the ADMINISTRATIVE_STATE of cells allocated to the
target RRH are set to locked.
On-site Actions
RRH Disabled Alarm Occurs
RRH Reset
Alarm Cleared Y/N?
Yes
No
Replace RRH
Monitor Alarm Recurrence Y/N
At the site, check if the alarm is still active in the LSM. If yes, reset the RRH.
Then, check whether the alarm is cleared.
2 When the alarm is cleared, wait at the site for 30 minutes to make sure that it
does not recur.

Replacement Manual.

142
A2149388R RRH LNA FAIL

This alarm occurs when the LNA Fail state lasts for 10 or more seconds.
Basic Information
Severity
Relates to
Category
Location
MINOR
Hardware
EQUIPMENT
Possible Cause
LNA Fail condition is maintained. This occurs when the LNA Fail (< 100 mA or >
250 mA) state lasts for 10 or more seconds.
Impact
Remedy


143
Alarm Raised
FW Ver. NEW?
Step 1
No
FW Update
Yes
Run RTRV-RRH-STS
Check FA_RSSI[dBm],
FA_RSSI_IQ_LEVEL
Step 2
Yes
RRH LNA FAIL

Alarm Raised?
No
Step 3
On Site Action
End


latest version.
firmware.
d Check whether the RRH LNA_FAIL alarm has been declared.

2 If the alarm is not cleared, run the RTRV-RRH-STS command to check the
RSSI (dBm, IQ_LEVEL) value: (RU_V1: -95 to 101 dBm, RU_V2: -96 to 102 dBm)
Set the CONN_BD_ID and CONN_ PORT_ID to the target RRH values,
and then run this command.
b Check the FA_RSSI and FA_RSSI_IQ_LEVEL values on the output

window.
On-site Actions

144
LNA Fail Alarm Occurs
RRH Reset
Alarm Cleared Y/N?
Yes
No
Replace the RRH
At the site, check if the alarm is still active in the LSM. If yes, reset the RRH
and see whether the alarm is cleared.
2 When the alarm is cleared, wait at the site for 30 minutes and monitor alarm
recurrence.

Replacement Manual.

145
A2149389R RRH LOW GAIN

This alarm occurs when the gain estimated from the measured RF output power is
below the threshold.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
Possible Cause
The gain estimated from the measured RF output power is below the threshold.
Impact
Remedy


146
Alarm Raised
Step 1
Run RTRV-RRH-STS
Check TX_RF_POWER
Step 2
FW Ver. NEW?
No
FW Update
Yes
Yes
RTRV-RRH-STS
RRH LOW GAIN

Alarm Raised?
No
Step 3
OP STATE disabled?
Yes
No
INIT-RRH
RRH LOW GAIN

Alarm Raised?
No
Yes
Step 4
On Site Action
End
Check the TX_RF_POWER value by running the RTRV-RRH-STS command.

The value displays on the output window.
2 Check whether the RRH firmware is the latest version by running the RTRVRRH-INVT command.


latest version.
firmware.
d Check whether the RRH LOW_GAIN alarm has been declared.

147
3 If the alarm is not cleared, run the RTRV-CELL-STS command to check the
OPERATIONAL_STATE. If it is disabled, reset the RRH.
Check whether the OPERATIONAL_STATE on the output window is set

to disabled.
b Set the CONN_BD_ID to ECP Number and CONN_PORT_ID to Port

Number, and then run the INIT-RRH command.
On-site Actions
RRH Low Gain Alarm Occurs
RRH Reset
Alarm Cleared Y/N?
Yes
No
Replace RRH
At the site, check if the alarm is still active in the LSM. If it is still on, reset the
RRH and see whether the alarm is cleared.
recurrence.

Replacement Manual.

148
A2149391R RRH OVER POWER

This alarm occurs when the output power exceeds the threshold.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
Possible Cause
The output power is more than 1.5 dB, which is higher than the rated power.
Occurrence: Output Power 47.5 dBm
Alarm type: Over Power alarm.
Duration: 2 seconds or more.
Impact
Remedy


149
Alarm Raised
Step 1
FW Ver. NEW?
No
FW Update
Yes
Run RTRV-RRH-STS Check
TX_RF_POWER[dBm],
FA_TSSI_IQ_LEVEL
Yes
RRH OVER POWER

Alarm Raised?
No
Run RTRV-RRH-CONF Check

OVER_PWR_ALARM_TH
Step 2
FA_RSSI_IQ_LEVEL
Greater Than
OVER_PWR_ALARM_TH?
No
Yes
Step 3
Run CHG-RRH-CONF
Change
OVER_PWR_ALARM_TH
Step 4
Run CHG-RRH-CONF
Change PATH_ENABLE_STATE
to UserEnabled
RRH OVER POWER

Alarm Raised?
No
Yes
Step 5
RTRV-RRH-STS
OP STATE disabled?
Yes
No
INIT-RRH
RRH OVER POWER

Alarm Raised?
No
Yes
Step 6
On Site Action

End
150


latest version.
firmware.
d Check whether the RRH OVER_POWER alarm has been declared.

2 If the alarm is not cleared, compare the results of RTRV-RRH-STS and
RTRV-RRH-CONF.
Set the appropriate values to CONNECT_BOARD_ID,

CONNECT_PORT_ID, and PATH_ID, and then run the RTRV-RRH_STS
command.
Check the TX_RF_POWER [dBm] and FA_TSSI_IQ_LEVEL values on
the output window.
b Set the appropriate values to CONNECT_BOARD_ID and

CONNECT_PORT_ID, and then run the RTRV-RRH_CONF command.
Check the OVER_PWR_ALARM_TH value on the output window.
3 If FA_TSSI_IQ_LEVEL is higher than OVER_PWR_ALARM_TH, check the

recommended threshold and change the OVER_PWR_ALARM_TH to the
recommended level by using the CHG-RRH-CONF command.
4 After changing the recommended threshold, change the PATH_ENABL

E_STATE of the PATH with the declared alarm to UserEnabled by using the
CHG-RRH-CONF command.
Run the RTRV-RRH-STS command.

to disabled.
b Set the CONN_BD_ID to ECP Number and CONN_PORT_ID to Port

Number, and then run the INIT-RRH command.
On-site Actions

151
RRH Over Power Alarm Occurs
RRH Reset
Alarm Cleared Y/N?
Yes
No
Replace RRH
RRH and see whether the alarm is cleared.
recurrence.

Replacement Manual.

152
A2149392R RRH VSWR FAIL

This alarm occurs when the VSWR measurement (return loss) is below the
threshold.
Basic Information
Severity
Relates to
Category
Location
MAJOR/MINOR
Hardware
EQUIPMENT
Possible Cause
The VSWR measurement (return loss) is below the threshold.
Impact
When major alarm is occurred, cell services related to the RRH will be unavailable.
Remedy


153
Alarm Raised
FW Ver. NEW?
Step 1
No
FW Update
Yes
RTRV-RRH-STS
Check TX_RF_POWER[dBm],
FA_TSSI_IQ_LEVEL
Yes
RRH VSWR FAIL

Alarm Raised?
No
RTRV-RRH-CONF
Step 2 Check VSWR_FAIL_MAJOR_ALARM_THR
Check VSWR_FAIL_MINOR_ALARM_THR
VSWR Greater Than

VSWR_FAIL_MAJOR_ALARM_THR?
VSWR_FAIL_MINOR_ALARM_THR?
No
Yes
CHG-RRH-CONF
Modify VSWR_FAIL_MAJOR_ALARM_THR
Modify VSWR_FAIL_MINOR_ALARM_THR
Step 3
CHG-RRH-CONF
Change PATH_ENABLE_STATE
to UserEnabled
RRH VSWR FAIL

Alarm Raised?
No
Yes
Step 4
RTRV-RRH-STS
OP STATE disabled?
Yes
No
INIT-RRH
RRH VSWR FAIL

Alarm Raised?
Step 5
Collect SW, RRH Log
On Site Action
No
Yes
End

154


latest version.
firmware.
d Check whether the RRH VSWR_FAIL alarm has been declared.

RTRV-RRH-CONF.

command.
Check the VSWR value on the output window.

Check the VSWR_FAIL_MAJOR_ALARM_THR,
VSWR_FAIL_MINOR_ALARM_THR value on the output window.
3 If VSWR is greater than VSWR_FAIL_MAJOR_ALARM_THR or

VSWR_FAIL_MINOR_ALARM_THR, check the recommended threshold
and change VSWR_FAIL_MAJOR_ALARM_THR or
VSWR_FAIL_MINOR_ALARM_THR to the recommended threshold by
using the CHG-RRH-CONF command.
If the alarm is a major severity alarm, after changing the relevant threshold to
the recommended threshold, change PATH_ENABLE_STATE for the path
where the alarm is active to UserEnabled by using the CHG-RRH-CONF
command.
Run the RTRV-RRH-STS command.

to disabled.
b Set INIT-RRH inputs CONN_BD_ID and CONN_PORT_ID to the ECP

Number and Port Number and then run the command.
On-site Actions

155
VSWR Fail Alarm Occurs
Power Off RRH
Separate Antenna Cable from

RRH and Check Connector
Condition
Measure Antenna VSWR with

Site Master Equipment
VSWR < 1.5?
No
Yes
Without Site Master Equipment
or Terminator
Remove the Terminator after

RRH Power Off
Take Corrective Action by

Replacing Antenna and Jumper
Cable
Power On RRH after Connecting

a Terminator to RRH
Yes
VSWR < 1.5?
No
Power On RRH after Connecting

Antenna Cable to RRH
Yes
Alarm Cleared Y/N?

No
Power On RRH after Replacing

Antenna Cables Connected to
Normal and Abnormal Paths
Power Off RRH
Inspect and Replace Antenna/

Antenna Cables
Yes
Alarm Cleared Y/N?

No
Replace RRH
At the site, check if the alarm is still active in the LSM. Additionally, check
the information of target sector and path in which an alarm has occurred.
2 Power off the target RRH sector in which the alarm has occurred. From the
rectifier, switch off the circuit breaker connected to the corresponding RRH.
After turning off the RRH power, check if Communication Fail was found for
156
the corresponding RRH in LSM. If Communication Fail did not occur on the
corresponding RRH, however, on another RRH, it is interpreted as that a
wrong sample has been selected.
3 Separate the path cable, in which the alarm occurred, from the RRH and check
its condition. Check if the cable and RRH connectors are damaged. If so,
replace the cable or corresponding RRH. If moist or any foreign substances are
found inside the connector that links the cable to the RRH, remove them.
[Water Inflow Inside the Connector]
[Impurities Inside the Connector]
4 If the cable state is normal, continue with the Step 5. If site-master equipment
or a terminator is not prepared, continue with the Step 7.
5 Use site master equipment to measure VSWR of the antenna and jumper cable.
If VSWR value measured by the site master is 1.5:1 or more, an appropriate

measure needs to be taken such as replacement of the antenna and jumper
cable.
6 Connect a terminator to the RRH antenna port and check VSWR value in LSM.

157
[Terminator]
[Connecting a terminator to RRH]
If VSWR value is 1.5:1 or more, RRH needs to be replaced. If VSWR is less

than 1.5:1, power off the RRH and remove the terminator.
7 Connect the antenna cable to the RRH and turn on RRH from the rectifier.
Check if the alarm is cleared in LSM. When the alarm is cleared, record action
history and leave the site.
8 If the alarm is not cleared even after checking the normal state of the antenna
cable and cable connection state, power off the RRH again.
9 Replace the antenna cable with one from another path where no alarm has
occurred and power on the RRH to see if the alarm is still activated.
10 If the alarm is cleared after the action taken in Step 9, it can be interpreted that
the failure was caused by a defective cable, a connection issue or an antenna
issue. Therefore, take the corrective measures in an order of reassembly of the
antenna-side cable; replacement of the cable; and replacement of the antenna.

Replacement Manual.

158
A2149408R RRH DIGITAL INPUT LOW

This alarm occurs when the digital input power level is at or below the threshold.
Basic Information
Severity
Relates to
Category
Location
MINOR
Hardware
EQUIPMENT
RRH[a_b_c]-RRH[a_b_c]/PATH[d]/FA[0]
Possible Cause
The digital input power level is the threshold or less.
Impact
Defaults
This default value for this alarm is 16,900 IQ level.
Remedy


159
Alarm Raised
FW Ver. NEW?
Step 1
No
FW Update
Yes
Yes
Run RTRV-RRH-STS
Check FA_RSSI_IQ_LEVEL
RRH DIGITAL INPUT LOW

Alarm Raised?
No
Run RTRV-RRH-CONF
Check LOW_PWR_ALARM_TH
Step 2
FA_RSSI_IQ_LEVEL
Less Than
LOW_PWR_ALARM_TH?
No
Yes
Run CHG-RRH-CONF
Change
LOW_PWR_ALARM_TH
Step 3
RRH DIGITAL INPUT LOW

Alarm Raised?
No
Yes
Collect SW, RRH Log
On Site Action
End


latest version.
firmware.
d Check whether the RRH DIGITAL_INPUT_LOW alarm has been

declared.

160
RTRV-RRH-CONF.

command.
Check the FA_TSSI_IQ_LEVEL value on the output window by running
the RTRV-RRH-CONF command.

Check the LOW_PWR_ALARM_TH value on the output window.
If the FA_TSSI_IQ_LEVEL is lower than the LOW_PWR_ALARM_TH,

check the recommended threshold and change the
LOW_PWR_ALARM_TH to the recommended level by using the CHGRRH-CONF command.
On-site Actions

161
RRH Digital Input Low Alarm

Occurs
RRH Reset
Alarm Cleared Y/N?
Yes
No
Reset DSP Block of Failoccurred Cell
Alarm Cleared Y/N?
Yes
No
Replace RRH
Alarm Cleared Y/N?
Yes
No
Reset Channel Board and

Replace
RRH and check whether the alarm is cleared.
2 If the alarm is not cleared, reset the DSP block of the failure-occurred cell.
Then, check whether the alarm is cleared. Use the INIT-DSP command in the
LSM to reset only the targeted cell.

Replacement Manual.
4 If the alarm is still on despite the replacement of the RRH, reset the channel
board. Use the INIT-PRC:ECP command, to reset the channel board.
5 If the alarm persists, replace the ECP.

162
Replacement Manual.

163
A2149630R ALD COMMUNICATION FAIL

This alarm occurs when the main processor (UMP) cannot receive keep-alive
response from the ALD.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
Possible Cause
The main processor (UMP) cannot receive keep-alive response from the ALD.
Impact
Remedy


164
Alarm Raised
Step 1
FW Ver. New?
Yes
FW Update
NO
Yes
ALD COMMUNICATION
FAIL Alarm Raised?
No
Step 2
Take action for the CPRI Alarm
CPRI Alarm Raised?

No
Yes
Step 3
ALD COMMUNICATION
FAIL Alarm Raised?
No
INIT-ALD
ALD COMMUNICATION
FAIL Alarm Raised?
No
Yes
End
Step 4
Collect Log
On Site Action


latest version.
firmware.
d Check whether the ALD_COMMUNICATION_FAIL alarm has been

declared.
165
2 Check if the CPRI_FAIL, OPTIC_TRANSCEIVER_RX_LOS, and

OPTIC_TRANSCEIVER_TX_FAULT alarms have been issued in the optic
port to which the RET is connected by using the RTRV-ALM-LIST command.
If any of these alarms have been issued, follow their remedies, and then check
if the ALD_COMMUNICATION_FAIL alarm has been declared.
3 If none of the alarms have been issued, reboot the RET by using the INITALD command.

Number, and then run the INIT-ALD command.
b Check whether the ALD_COMMUNICATION_FAIL alarm has been

declared.
On-site Actions
ALD Communication Fail
Alarm Raised

external connection of the
RET
Step 1
Yes
Step 2
Take action for

abnormal installation
status and abnormal
No
Are the installation

status and external
environment status
normal?
Yes
Step 3
Alarm Clear?
No
RET Reset
Yes
Yes
Yes
Alarm Clear?
No
Check if RET unit is

supplied with power
Step 4
No
Detach the RU's AISG cable
Yes
Step 8
Step 6
Check if the RU RET
port outputs power
Replace RET Unit
Step 5
Step 7
Summarize actions taken
and exit the station
Yes
Replace the AISG

cable unit
No
Replace the RU or reset the

RU

166
2 Check if the RET unit and the AISG cable attached to it are connected
normally. If not, take necessary actions.
3 Reset the RET unit and check if the alarm clears.

4 If the alarm remains, check if power is supplied from the RET daisy chain port.
5 If power is being supplied, replace the RET unit.
6 If power is not being supplied, disconnect the RU AISG cable and check if
power is outputted from the RU RET port.
7 If power is not outputted from the RU, reset the RU.

o
Check if the alarm clears after the reset.
If the alarm remains, replace the RU.
8 If power is outputted from the RU, replace the AISG cable.

167
A2149649R RRH HW TYPE MISMATCH

This alarm occurs when the connected RRH hardware type mismatches with the
configured one.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Software
EQUIPMENT
Possible Cause
Connected RRH hardware type did not match the configured RRH hardware type.
Impact
Remedy

168
Alarm Raised
Step 1
Grown RRH Type Same As

Equipped RRH Type?
No
Grown RRH Type

the Problem?
Yes
On Site Action
Yes
Re-Grow as
Equipped RRH Type
Yes
Step 3
No
Alarm Raised?
Step 2
No
RRH FW update
FW Ver. NEW?
Yes
Yes
Step 4
Alarm Raised?
No
System Restart
Alarm Raised?
Collect SW Log
On Site Action
End
Check whether the grown RRH type matches the equipped RRH type by
running the RTRV-RRH-CONF and RTRV-RRH-INVT commands.
Run the RTRV-RRH-CONF command by selecting the

CONNECT_BOARD_ID and CONNECT_PORT_ID that has raised the
alarm as inputs. Run the RTRV-RRH-INVT command by selecting the
CONN_BD_ID and CONN_PORT_ID that has raised the alarm as inputs.
b Compare the BOARD_TYPE of RTRV-RRH-CONF and TYPE_NUM of

RTRV-RRH-INVT to check whether they are the same RRH. If the RRH
169
is the same, continue with the Step 3.
2 If the grown RRH type is the problem, continue with the Step 2. If the
equipped RRH type is the problem, continue to On-site Actions.
3 If the grown RRH type and equipped RRH type are not the same, run the
CHG-RRH-CONF to grow the equipped RRH type.
Run the RTRV-RRH-INVT command to check the equipped RRH type,

and then regrow the equipped RRH type.
b Check whether the alarm is raised after the regrow.

4 Check whether the RRH firmware is the latest version by running the RTRVRRH-INVT command. If the firmware is not the latest version, run the DNLDFW command to download the latest version and the UDT-RRH-FW command
to update the firmware.

Number, and then run the RTRV-RRH-INVT command.
b Check whether the RRH HW TYPE MISMATCH alarm has been declared.
5 If the alarm is not cleared, run the INIT-SYS command to restart the system.
If the alarm remains, collect the SW log and share with Samsung for the next

170
A2180001R GPSR TOD MSG MISSED

This alarm occurs when initialization due to GPSR restart or GPSR module failure
has occurred.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Software
COMMUNICATIONS
RACK[a]/SHELF[b]/SLOT[c]-GPSR[d]
Possible Cause
The main processor does not receive the TOD message from the GPSR.
Impact
Remedy


171
Alarm Raised
Step 1
UMP/GPS FW Ver. NEW?
No
UMP/GPS FW Update
Yes
Yes
Collect SW Log
GPS TOD MSG MISSED

Alarm Raised?
No
Step 2
UMP PROCESS DOWN

(scm)Alarm Raised?
Yes
Actions To Clear
UMP PROCESS DOWN (scm)
No
INIT-SW UMP scm
Step 3
GPS TOD MSG MISSED

Alarm Raised?
No
Yes
Restart GPS
Step 4
GPS TOD MSG MISSED

Alarm Raised?
No
Yes
INIT-PRC (UMP,
RESET MODE=HW)
Step 5
GPS TOD MSG MISSED

Alarm Raised?
No
Yes
Collect SW Log
On Site Action
End
Run the RTRV-PRC-FW command to check whether the UMP firmware is the
latest version. Run the RTRV-GPS-INVT command to check whether the
GPS firmware is the latest version.

172

this command.

firmware. If the alarm is being raised even when firmware is the latest
version, collect the SW log.
d Check whether the GPSR TOD MSG MISSED alarm has been declared.
e
Run the RTRV-GPS-INVT command.
Check whether the FW_VERSION on the output window displays the

latest versions.
g If the firmware is not the latest version, run the DNLD-FW command to
h Check whether the GPSR TOD MSG MISSED alarm has been declared.
2 Run the RTRV-ALM-LIST command to check the list of alarms, and then
restart the SCM block.
If the UMP PROCESS_DOWN (scm) alarm is on the list, follow its

remedy.
b If the SCM block is currently running, set the PRC_UNIT_TYPE to UMP

and SW_UNIT_NAME to SCM Image Name, and then run the INIT-SW
command
Check whether the GPSR TOD MSG MISSED alarm has been declared.
3 If the alarm remains, run the INIT-GPS command to restart the GPSR.
4 Run the INIT-PRC command to restart the UMP.

a
Set the PRC_UNIT_TYPE to UMP and RESET_MODE to HW, and then

run this command.
b Check whether the GPSR TOD MSG MISSED alarm has been declared.
On-site Actions

173
After entering the site
ANTENNA_FAIL, LOCKING
FAIL alarm actions
Yes
Antenna Fail/Locking fail

occurrence history
No
Reboot the UMP
Yes
The UMP error is

recovered? (Y/N)
No
Monitoring
Replace the UMP
Check the history of the ANTEANNA_FAIL or LOCKING_FAIL alarm

occurrence.
o
If any of these alarms are active in the LSM, follow their on-site actions.
If no record of the ANTEANNA_FAIL or LOCKING_FAIL alarm

occurrence is found, continue with the Step 2.
2 After powering on the UMP, check if the UCCM alarm is cleared.

o
If the alarm is cleared, monitor the UCCM status.
If the alarm remains, continue with the Step 3.
3 After replacing the UMP, check if the FUNCTION_FAIL alarm is inactivated

within the standard time. The maximum time for: GPS is 15 minutes and
IEEE1588v2 is 1H 15 minutes.
o
If the alarm does not activate, it is decided that the UCCM is defective,
and therefore leave the site.
If the alarm does not clear, go back to the Step 1 and repeat the process.
For information on replacement of UMP and other parts, see LTE eNB Hardware

174
A2180350R GPSR ANTENNA FAIL

This alarm occurs when the antenna cable is disconnected.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
Possible Cause
This alarm issues due to one of the following reasons:
The feeding current to the antenna side is at the specified open or short level.
The antenna cable is disconnected.
Impact
This alarm does not have any direct impact on the system. However, it can be the
reason for the GPSR LOCKING FAIL and GPSR HOLDOVER 24H alarms.
Remedy


175
Alarm Raised
Step 1
No
UMP/GPS
FW Update
Yes
Step 2
Yes
Collect SW Log
GPS ANTENNA FAIL

Alarm Raised?
No
Restart GPS
GPS ANTENNA FAIL

Alarm Raised?
No
Yes
Step 3
Collect SW Log
On Site Action
End

this command.

d Check whether the GPS ANTENNA_FAIL alarm has been declared.

e

latest version.
176
h Check whether the GPS ANTENNA_FAIL alarm has been declared.

2 Run the INIT_GPS command to restart the GPSR.
If the GPS clock is not received due to the GPSR antenna disconnection, the
internal HOLDOVER clock is used. If, however, the HOLDOVER status
continues for more than 24 hours, the clock input may not be stable.
On-site Actions
Any trace of lightning and

waterlogging Y/N?
Yes
Replace GPS antennal

installation materials.
No
Check voltage at the UMP GPS

port end.
4.5~5.5 V?
No
Yes
Yes
Error recovered after cable

replacement?
No
Yes
Error recovered after

splitter replacement?
No
Yes

antenna replacement?
No
End Process
Replace
Check for any traces of lightning in the GPS arrestor.

177
For lightning traces, look for burnt marks of the GPS arrestor or surrounding
cables.
o
If any traces of lightning are found, replace UMP and GPS antenna
If traces of lightning are NOT found, continue with the Step 2.
2 Separate the cable from the GPS port, and measure the voltage of the GPS port
connector.
Measure the voltage by touching (+) end of a Digital Voltage Meter (DVM) to the
core wire and (-) end to the outside of the connector.
o
If the measurement is between 4.5 to 5.5 V, continue with the Step 4.
If the measurement is not within this range, replace the UMP.
3 Check and replace the GPS installation materials and check if the alarm is
cleared.
If the errors/failures have been recovered after checking the cable

connection state and replacing the materials, terminate the inspection
procedure. If not, continue with the following steps.
b Check the divider connection state and replace the parts. If the
errors/failures have been recovered, terminate the inspection procedure. If
not, continue with the following step.
Check the GPS antenna connection state and replace the parts if needed.
When the errors/failures are recovered, terminate the inspection process.
4 After changing the UMP, check if the errors/failures are repaired.

o
If the alarm does not activate, it is decided that the part is defective, and
therefore leave the site.
If the GPS antenna and installation materials are found to be defective, the UMP is
not defective. Therefore, RMA will not be processed.
For information on UMP board replacement, see LTE eNB Hardware Addition and
Replacement Manual.

178
A2180360R GPSR HOLDOVER 24H

This alarm occurs when the threshold time is exceeded after transition to a
holdover state.
Basic Information
Severity
Relates to
Category
Location
CRITICAL
Hardware
EQUIPMENT
Possible Cause
24 hours have passed since the transition to the holdover state.
Impact
All cell services will be unavailable.
Remedy


179
Alarm Raised
Step 1
No
UMP/GPS FW Update
Yes
Yes
Collect SW Log
GPS HOLDOVER 24H

Alarm Raised?
No
Step 2
GPS ANTENNA FAIL,

LOCKING FAIL
Alarm Raised?
Yes
Actions To Clear
GPS ANTENNA FAIL,
LOCKING FAIL
No
RTRV-GPS-STS
Step 3
GPS HOLDOVER 24H

Alarm Raised?
No
Yes
Restart GPS
Step 4
GPS HOLDOVER 24H

Alarm Raised?
No
Yes
Collect SW Log
On Site Action
End
Set the PRC_UNIT_TYPE to UMP and LOC_TYPE to *, and then run the


180
d Check whether the GPS HOLDOVER 24H alarm has been declared.
e

latest versions.
h Check whether the GPS HOLDOVER 24H alarm has been declared.
2 Run the RTRV-ALM-LIST command to check the list of alarms.
a
If either the GPSR ANTENNA FAIL or the GPSR LOCKING_FAIL

alarm is on the list, follow the remedy.
b Run the RTRV-GPS-STS command.

c
Check the LOCK_STATE and HOLDOVER_STATE.
3 If a HOLDOVER 24H alarm is being raised when there is no ANTENNA

FAIL or LOCKING_FAIL alarm, run the INIT-GPS command to restart the
GPSR.
Check whether the GPSR alarm is being raised.
On-site Actions

181
FAIL alarm actions
Yes

occurrence history
No
Reboot the UMP
Yes
The UMP error is

recovered? (Y/N)
No
Monitoring
Replace the UMP

occurrence.
o
If no record of the ANTEANNA_FAIL or LOCKING_FAIL occurrence is

found, continue with the Step 2.
2 After powering on the UMP, check if the UCCM alarm is cleared.

o

o

182
A2180361R GPSR LOCKING FAIL

This alarm occurs when the normal GPS satellite signal cannot be received.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
Possible Cause
A normal GPS satellite signal is not received.
No GPS satellite tracking for one hour.
Impact
reason for the GPSR HOLDOVER 24H alarm.
Remedy


183
Alarm Raised
Step 1
No
UMP/GPS FW Update
Yes
Yes
Collect SW Log
GPS LOCKING FAIL

Alarm Raised?
No
Step 2
GPS ANTENNA FAIL

Alarm Raised?
Yes
Actions To Clear
GPS ANTENNA FAIL
No
RTRV-GPS-STS
Step 3
GPS LOCKING FAIL

Alarm Raised?
No
Yes
Restart GPS
Step 4
GPS LOCKING FAIL

Alarm Raised?
No
Yes
Collect SW Log
On Site Action
End


184
d Check whether the GPS LOCKING_FAIL alarm has been declared.

e

latest version.
h Check whether the GPS LOCKING_FAIL alarm has been declared.

2 Run the RTRV-ALM-LIST command to check whether the GPS
ANTENNA_FAIL alarm has been raised. If it has, follow the remedy.
After running the RTRV-GPS-STS command, check the LOCK_STATE,
HOLDOVER_STATE and SAT_N values to determine the number of GPS
satellites that are being used for tracking.
3 If a LOCKING_FAIL alarm is raised when there is no ANTENNA_ FAIL, run

the INIT-GPS command to restart the GPSR.
Check whether the GPSR alarm has been declared.
On-site Actions

185
Inspect installation environment

based on the GPS antenna
installation guide.
Is the satellite signal improved?
Yes
No
Yes
No
Replace the UMP
End process
Inspect installation environment for the GPS antenna and check if it clears the
alarm.
GPS antennas must be installed, securing as much open sky as possible (the
horizontal field of view to be 360, the vertical to be 160). If the field of view
is not secured sufficiently, change the location for GPS antenna installation.
If the alarm is not recovered or the satellite signals are not improved, replace
the UMP.
For improvement of the satellite signals, execute RTRV-GPS-STS command.

There should be more than 4 (longer than 1 minute) satellites (SATNs) observed.
2 After changing the UMP, check if the alarm is cleared.

o

186
A2180368R GPSR FUNCTION FAIL

This alarm occurs when the GPSR module fails.
Basic Information
Severity
Relates to
Category
Location
CRITICAL
Hardware
EQUIPMENT
Possible Cause
The GPSR is reset by restarting the GPSR or when the GPSR module failure
occurs due to one of the following reasons:
Power failure (when the input power is 5.2 V or lower and 5.8 V or higher).
The Electronic Frequency Control (EFC) value is either +100 % or -100 %.
Deviation failure: Even sec (or 1 PPS) jumps over 100 ns.
Time is not set: GPS time is not set and it is neither active nor standby.
Impact
All cell services will be unavailable
Remedy


187
Alarm Raised
Step 1
No
UMP/GPS FW Update
Yes
Yes
Collect SW Log
GPS FUNCTION FAIL

Alarm Raised?
No
Step 2
Restart GPS
Step 3
GPS FUNCTION FAIL

Alarm Raised?
No
Yes
Collect SW Log
On Site Action
End

d Check whether the GPS FUNCTION_FAIL alarm has been declared.

e

latest version.
188
h Check whether the GPS FUNCTION_FAIL alarm has been declared.

2 If an alarm is being raised, run the INIT-GPS command to restart the GPSR.
On-site Actions
After entering
Reboot the UMP
No
UMP error recovered Y/N

Yes
Monitoring
Change the UMP
Restart the UMP power and check if the FUNCTION_FAIL alarm is

inactivated within the standard time. The maximum time for: GPS is 15
minutes and IEEE1588v2 is 1H 15 minutes.
o
If the alarm is normally cleared off, monitor the UCCM state.

o

189
A2180424R GPSR FREQUENCY HOLDOVER

EXCEED
This alarm occurs when the threshold time (one week) is exceeded after transition
to a holdover state.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
Possible Cause
1 week have been passed since the transition to the holdover state.
Impact
Remedy


190
Alarm Raised
Step 1
No
UMP/GPS FW Update
Yes
Yes
Collect SW Log
GPS FREQUENCY
HOLDOVER EXCEED
Alarm Raised?
No
Step 2
GPS ANTENNA FAIL,

LOCKING FAIL
Alarm Raised?
Yes
Actions To Clear
GPS ANTENNA FAIL,
LOCKING FAIL
No
GPS FREQUENCY
HOLDOVER EXCEED
Alarm Raised?
RTRV-GPS-STS
No
Yes
Step 3
Restart GPS
Step 4
GPS FREQUENCY
HOLDOVER EXCEED
Alarm Raised?
No
Yes
Collect SW Log
On Site Action
End


191
d Check whether the GPS FREQUENCY HOLDOVER EXCEED alarm has

been declared.

latest versions.
h Check whether the GPS FREQUENCY HOLDOVER EXCEED alarm has

been declared.

If either the GPSR ANTENNA FAIL or the GPSR LOCKING_FAIL alarm is
on the list, follow the remedy.
Run the RTRV-GPS-STS command.
b Check the LOCK_STATE and HOLDOVER_STATE.

3 If a FREQUENCY HOLDOVER EXCEED alarm is being raised when there
is no ANTENNA FAIL or LOCKING_FAIL alarm, run the INIT-GPS
command to restart the GPSR.
Check whether a GPSR alarm is being raised.
On-site Actions

192
FAIL alarm actions
Yes

occurrence history
No
Reboot the UMP
Yes
The UMP error is

recovered? (Y/N)
No
Monitoring
Replace the UMP

occurrence.
o
If no record of ANTEANNA_FAIL/LOCKING_FAIL occurrence is found,

2 After powering on UMP check if the UCCM alarm is cleared or not.

o

o

193
A2180624R GPSR CLOCK PHASE ABNORMAL

This alarm occurs when the clock phase of the GPS is drifted abnormally.
Basic Information
Severity
Relates to
Category
Location
CRITICAL
Hardware
EQUIPMENT
Possible Cause
The clock phase of the GPS is drifted abnormally.
Impact
Remedy


194
Alarm Raised
Step 1
No
UMP/GPS FW Update
Yes
Yes
Collect SW Log
GPS CLOCK PHASE

ABNORMAL
Alarm Raised?
No
Step 2
GPS ANTENNA FAIL,

LOCKING FAIL
Alarm Raised?
Yes
Actions To Clear
GPS ANTENNA FAIL,
LOCKING FAIL
No
GPS CLOCK PHASE
ABNORMAL
Alarm Raised?
No
Yes
RTRV-GPS-STS
Step 3
Restart GPS
Step 4
GPS CLOCK PHASE

ABNORMAL
Alarm Raised?
No
Yes
Collect SW Log
On Site Action
End

195
d Check whether the GPS CLOCK PHASE ABNORMAL alarm has been
declared.

latest versions.
h Check whether the GPS CLOCK PHASE ABNORMAL alarm has been
declared.

3 If the alarm is not cleared, check the TINT value and then run the INIT-GPS
[Run] Run the RTRV-GPS-STS command.

Check the TINT value.
b Run the INIT-GPS command.

Check whether the GPS CLOCK PHASE ABNORMAL alarm has been
declared.
On-site Actions

196
FAIL alarm actions
Yes

occurrence history
No
Reboot the UMP
Yes
The UMP error is

recovered? (Y/N)
No
Monitoring
Replace the UMP

occurrence.
o
If no record of the ANTEANNA_FAIL or LOCKING_FAIL alarm

occurrence is found, continue with the Step 2.
2 After powering on UMP, check if the UCCM alarm is cleared.

o

o

197
A2199202R SYS UDA

This alarm occurs when a User-Defined Alarm (UDA) is generated.
Basic Information
Severity
Relates to
Category
Location
Hardware
EQUIPMENT
UDA[a]/UDA_NAME
Possible Cause
A UDA is generated.
Impact
The impact of this alarm depends on the user-configuration.
Remedy

Alarm Raised
Collect SW Log
Step 1
System Restart
Alarm Raised?
No
Yes
Step 2
On Site Action

End
198
After collecting the SW log, run the INIT-SYS command to restart the
system.
Check whether the alarm has been raised after the system restart.
2 If the alarm remains, share the log with Samsung for the next level of
maintenance support.
On-site Actions
Enter the station
Yes
UDA Is the cable correctly

connected?
Replace the UDA cable and

perform re-wiring
No
1) Reconnect the UDA cable.

2) Perform re-wiring by referring
to the installation instructions.
Alarm Clear?
Find out a cause for each alarm

and take a corrective measure
for each situation
No
Yes
No
Alarm Clear?
Yes
Alarm Clear?
Yes
No
Conclude that the UDA cable is

not properly connected

monitoring after history recording
Conclude that the UDA cable is

poor.
Alarm is generated
Record the details

station
Check if the UDA cable is properly connected to the UMP.
2 Check if the UDA cable is properly connected to each alarm device as

described in the installation manual.
3 If the UDA cable is not properly connected to the UMP or the alarm devices,
reconnect the cable to the UMP and the alarm devices, or re-wire the
connections to the alarm devices as described in the LTE CDU Installation
Manual. (check the file name)
4 Check if the UDA cable is damaged or entangled. If the UDA cable is

damaged, replace the UDA cable.
5 Take the appropriate action to correct the potential cause of the alarm, and
monitor the alarm status. For example, in case of a door open alarm, close the
199
door of the enclosure and check if the alarm is cleared.
6 Unmount and remount the UMP and check if an alarm is generated after
loading completes.
8 If the alarm remains, replace the UMP.
Replacement Manual.

200
A2199209R SYS FAN FAIL

This alarm occurs when the fan does not work normally.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
ENVIRONMENT
RACK[a]/FAN-FAN[b]/FAN_NAME
Possible Cause
The fan is not connected.
The actual operation speed is lower than 60% compared to the target speed
(varying depending on the temperature).
Impact
System cooling will be impacted due to the fan failure.
Remedy


201
Alarm Raised
Step 1
TEMPERATURE HIGH
Alarm Raised?
No
Yes
Check Temperature
Of Each Board
Step 2
Collect SW Log
On Site Action
Run the RTRV-ALM-LIST command to check whether the CPU

TEMPERATURE HIGH alarm has been raised due to the FAN FAIL alarm.
Check whether the CPU TEMPERATURE HIGH alarm has been raised.
2 If the CPU TEMPERATURE HIGH alarm is being raised, run the RTRVPRC-STS command to check the TEMPERATURE[C] value of each
UNIT_TYPE.
On-site Actions

202
Fan fail alarm occurrence
Write down LED color &

Remount Fan module
Step 1
Step 2
Contact failure between Fan

module and DU
Yes
Fan fail alarm is cleared

and LED green?
No
(RED or Off)
Replaced to normal Fan module
Step 3

and LED green?
Yes
Fan module is defective
No
(RED or Off)
Check DU
Step 4
No
(RED or Off)
Yes
As the fan module is

not defective,
RMA is not
conducted.
If DU judged
defective, the fan
module does not go
through the RMA
process.

and LED green?
Finished
RMA is conducted.
After recording LED color of the fan module, remount the module.
When dismounting the fan module, check if any foreign substances are found
in DU or fan module. If any foreign substances are found, remount it after
eliminating the foreign substance.
2 Check the LED of the fan module.

o
If the LED is red or off, continue with the Step3.
If LED is green and the alarm is kept cleared more than 2 minutes, leave
the site, judging the alarm is caused due to the contact failure between the
fan module and DU.
If the alarm is found out to be caused due to the contact failure, the fan module
does not go through the RMA process.
3 After replacing the fan module, check for the alarm state.
o
If the alarm is cleared for more than 2 minutes, leave the site with the
previously installed fan module, judging it is defective.
4 After checking and taking actions for the DU shelf, check for the alarm.
203
If the alarm is cleared for more than 2 minutes, leave the site with the
previously installed DU shelf, judging it defective.
If the DU judged defective, the fan module does not go through the RMA process.
For information on fan replacement, see LTE eNB Hardware Addition and
Replacement Manual.

204
A2199365R SYS NTP UPDATE ERROR

This alarm occurs when the system time cannot be updated due to an incorrect
server configuration or due to a lack of connectivity with the NTP server.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Software
EQUIPMENT
None
Possible Cause
The system time cannot be updated due to the incorrect server configuration or
lack of connectivity with the NTP server.
Impact
Remedy

205
Alarm Raised
Yes
Separate Time Server?
No
Check NTP Info
Step 1
Setting Normal?
Yes
No
Reconfigure
NTP Server Info
Step 2
Alarm Cleared?
No
Yes
NTP Util Test
EMS NTP Server Restart and

Check System SW Util
NTP Util test Success?
No
Yes
Restart SWM/FM Block
Step 3
Yes
Alarm Cleared?
No
End
Collect SW Log, Request

analysis
Step 4
If a NTP Sync server exists, check whether the setting is correct. If the
information is not set or different, reconfigure the information of the server.
If the NTP Sync server exists, run the RTRV-NTP-CONF to check the
address.
b If the server IP address and the command results are different, run the
CHG-NTP-CONF command to reconfigure the address.
206
Check in a few minutes to see if the alarm has been cleared.
2 If the alarm has not been cleared, login to the NE and carry out a NTP Util test
to check if NTP communication is occurring with the EMS. If the util is not
properly executing, check whether the ntpdate util for the EMS (or the clock
sync server) NTP server and system SW is working correctly.
Use the ntpdate util to check if ntp clock sync is possible.
o
ntpdate2 -<ipversion> -i <bindIp> <serverIp> In Case of Failure

ntpdate -<ipversion> <serverIp>
Ex> ntpdate2 -4 -i 10.1.1.11 10.1.1.10
If the ntpdate command execution fails, check whether the ntpdate util for the
EMS (or the clock sync server) NTP server and NE is working correctly. Then,
repeat the Step 2.
3 If ntpdate executed successfully, however, the alarm remains, check the alarm
status again after restarting the SWM and FM block.
Restart the block by running the INIT-SW: SWM and INIT-SW: FM.
b Check whether the alarm occurs after clearance.

4 If the alarm remains, collect the SW log and share with Samsung for
consulting next level of support.

207
A2199460R SYS SERVICE OFF

This alarm occurs when all the cells for the eNB are disabled.
Basic Information
Severity
Relates to
Category
Location
CRITICAL
Software
EQUIPMENT
None
Possible Cause
All cells for the eNB are disabled.
Impact
Remedy

208
Alarm Raised
Collect SW Log
Step 1
System Locked?
Yes
System Unlock
No
Yes
Step 2
All Cell Locked?
SYS SERVICE OFF

Alarm Raised?
Yes
No
Cell Unlock
No
Yes
Alarm Exist?
Step 3
SYS SERVICE OFF

Alarm Raised?
No
Check Remedy and

Actions To Clear Alarm
Yes
No
Yes
SYS SERVICE OFF

Alarm Raised?
No
Step 4
Request Analysis
End
Check whether the system admin state is set to locked, and take appropriate
actions if so.
Run the RTRV-SYS-CONF command.
b Check whether the output value of the ADMINISTRATIVE_STATE is

locked. If yes, do the following steps.
Change the value of ADMINISTRATIVE_STATE to unlocked, by

running the CHG-SYS-CONF command.
d Check whether the SERVICE_OFF alarm has been raised by running the
RTRV-ALM-LIST command.
2 Check whether the admin state of all cells is set to locked and take appropriate
actions if so.
209
Run the RTRV-CELL-CONF command.
b Check whether the output value of the ADMINISTRATIVE_STATE for

all cells is locked. If yes, do the following steps.
Change the value of ADMINISTRATIVE_STATE to unlocked, by

running the CHG-CELL-CONF command.
d Check whether the SERVICE_OFF alarm has been raised, by running the
RTRV-ALM-LIST command.
3 If the alarm is not cleared, check which alarms are still raised and take
appropriate actions.
b If an alarm is being raised, follow the remedy.

consulting next level of support.

210
A2199600R SYS MME COMMUNICATION FAIL

This alarm occurs when there is a communication problem between the eNB and
MME.
Basic Information
Severity
Relates to
Category
Location
CRITICAL
Software
EQUIPMENT
None
Possible Cause
The eNB does not receive a response for the SCTP heartbeat from all the
equipped MMEs.
The S1AP connection setup between the eNBand all the equipped MMEs has
not been completed.
Impact
The LTE services will be unavailable.
Remedy


211
Alarm Raised
Step 2
Step 1
Check S1 Status
Yes
SCTP_STATE ==
disabled
No
CHECK S1 STATUS
Check
SYSTEM SIG IP
Step 3
No
S1 IP Exists?
ADD S1 IP
Yes
No
Yes
Step 4
Alarm Cleared?
Check MME IP Info
Step 5
No
Correct IP?
Change IP
Yes
Step 6
Alarm Cleared?
Yes
No
Check PING STATUS
Step 7
No
PING OK ?
Check
Comm Status
Yes
Step 8
Alarm Cleared?
Yes
No
Collect SW Log
Request Analysis
End
Run the RTRV-S1-STS command to check the SCTP_STATE and

S1AP_STATE.
Check the SCTP_STATE and S1AP_STATE.
2 If SCTP_STATE is disabled, run the RTRV-SYS-SIGIP command and

check whether SIG IP exists.
Check whether the S1_PRI_IPV4_ADDR or S1_SEC_IPV4_ADDR exists.
212
If you are using IPv6, check if S1_PRI_IPV6_ADDR or

S1_SEC_IPV6_ADDR exists.
3 If S1 IP does not exist, add S1 IP.

a
Run the CHG-IP-ADDR command and change the LTE_SIGNAL_S1 to

True.
b Run the RTRV-SYS-SIGIP command and check whether the IP has been
added.
4 Run the RTRV-MME-CONF command and check the MME IP information.

Check whether the correct MME IP information is being displayed.
5 If the MME IP information is incorrect, change the IP information.

a
Run the CHG-MME-CONF command to change the IP information.
b Run the RTRV-MME-CONF command to check whether the information

has been updated correctly.
6 Check the ping status between the eNB-MME.

Run ping -I [eNB IP] [MME IP].
Check whether the ping status is normal.
7 If the ping status is abnormal, check the communication status.

a
Run the RTRV-IP-ROUTE command.
b Check the routing table of the MME IP.

level of maintenance support. On-site Actions
If the alarm remains, contact the owner of the MME.
2 If the alarm still persists, contact Samsung for the next level of maintenance
support.

213
A2199602R SYS SLEEPING CELL DETECTION

This alarm occurs when there is a sleeping cell.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Software
PROCESSING
CELL[a]
Possible Cause
The diagnosis call function is activated (diag_Call_Enable is set to ON).
The value of diagCallEnable can be retrieved by running the RTRV-DIAG-CONF

command.
There is no RRC connection during triggering_Condition_Timer while no call

is connected to the cell.
The value of triggering_Condition_Timer can be retrieved by running the RTRVDIAG-CONF command.
There is no response to the paging call transmitted by the eNB to the idle UE
after triggering_Condition_Timer of PLD DIAG_CALL_CONF.
Impact
Defaults
The default value of TRIGGERING_CONDITION_TIMER is 1 hour.
Remedy


214
SLEEPING CELL Alarm

Raised
Step 1
RECOVERY_MODE_SE
LECTION == AUTO?
No
Manual RESET Carried Out

by Operator
Yes
Step 2
Step 3
CELL_RELEASE
autoRecoveryMethod
value?
DSP_RESET_ONLY
Step 4
RU_RESET_ONLY
Alarm Cleared?
DSP_RU_RESET
No
Yes
Collect SW Log
End
Replace ECP, RRH
Run the RTRV-DIAG-CONF command to check the

RECOVERY_MODE_SELECTION value.
Check whether the RECOVERY_MODE_SELECTION value is set to AUTO

or MANUAL.
2 If the RECOVERY_MODE_SELECTION value is set to AUTO, check the

AUTO_ RECOVERY_METHOD value.
If RECOVERY_MODE_SELECTION is set to AUTO, check which value out of CELL_RELEASE, DSP_RESET_ONLY, RU_RESET_ONLY, or
DSP_RU_RESET-the AUTO_RECOVERY_METHOD is set to.
215
3 Check whether the alarm clears depending on the value for AUTO_
RECOVERY_METHOD.
o
If AUTO_RECOVERY_METHOD is set to CELL_RELEASE, check

whether the alarm clears after CELL RELEASE is completed.
If AUTO_RECOVERY_METHOD is set to DSP_RESET_ONLY, check

whether the alarm clears after DSP RESET is completed.
If AUTO_RECOVERY_METHOD is set to DSP_RU_RESET, check

whether the alarm clears after both the DSP and RU RESET is completed.
4 If RECOVERY_MODE_SELECTION is set to MANUAL, take the

Run the INIT-DSP command. Set the ECP Number and DSP ID that
have raised the alarm, and then run this command.
b Check whether the alarm is cleared.

c
d Check whether the alarm is cleared after the system reset.

5 If the alarm remains, collect the SW log and replace the ECP of the faulty cell.
If the alarm still does not clear, replace the RRH of the faulty cell.
On-site Actions
Replace ECP and RRH
2 If the alarm remains, consult the next level of maintenance with Samsung.

216
A2199605R SYS IND MME COMMUNICATION

FAIL
This alarm occurs when the S1 interface is in an abnormal state or the eNB cannot
receive the SCTP heartbeat response from the MME.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Software
EQUIPMENT
MME[e]
Possible Cause
The S1 interface is in an abnormal state or the eNB cannot receive the SCTP
heartbeat response from the MME.
Impact
Remedy


217
Alarm Raised
Step 2
Step 1
Check S1 Status
Yes
SCTP_STATE ==
disabled
No
CHECK S1 STATUS
Check
SYSTEM SIG IP
Step 3
No
S1 IP Exists?
ADD S1 IP
Yes
No
Yes
Step 4
Alarm Cleared?
Check MME IP Info
Step 5
No
Correct IP?
Change IP
Yes
Step 6
Alarm Cleared?
Yes
No
Check PING STATUS
Step 7
No
PING OK?
Check
Comm Status
Yes
Step 8
Alarm Cleared?
Yes
No
Collect SW Log
Request Analysis
End

S1AP_STATE.

check whether SIGIP exists.
Check whether S1_PRI_IPV4_ADDR or S1_SEC_IPV4_ADDR exists.
218


a
Run the CHG-IP-ADDR command and change LTE_SIGNAL_S1 to True.
b Run the RTRV-SYS-SIGIP command and check whether IP has been

added.

Check whether the correct MME IP information is being displayed.

a


a
b Check whether the ping status is normal.

a
b Check the routing table regarding the MME IP.

On-site Actions
support.

219
A2199629R SYS MCE COMMUNICATION FAIL

This alarm occurs when the eNB cannot receive the SCTP heartbeat response from
the MCE.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Software
EQUIPMENT
None
Possible Cause
The eNB cannot receive the SCTP heartbeat response from the MCE.
Impact
Remedy


220
Alarm Raised
Step 1
Yes
Step 2
Check M2 Status
SCTP_STATE ==
SCTP_OUT_OF_SE
RVICE
No
CHECK M2 STATUS
Check
SYSTEM SIG IP
Step 3
No
M2 IP Exists?
ADD M2 IP
Yes
No
Yes
Step 4
Alarm Cleared?
Check MCE IP Info
Step 5
No
Correct IP?
Change IP
Yes
Step 6
Alarm Cleared?
Yes
No
Check PING STATUS
Step 7
No
PING OK?
Check
Comm Status
Yes
Step 8
Alarm Cleared?
Yes
No
Collect SW Log
Request Analysis
End
Run the RTRV-M2-STS command to check the SCTP_STATE and

M2_AP_STATE.
Check the SCTP_STATE and M2_AP_STATE.
2 If SCTP_STATE is set to SCTP_OUT_OF_SERVICE, run the RTRV-SYSSIGIP command and check whether SIG IP exists.
Run the RTRV-SYS-SIGIP command.

221
b Check whether M2_PRI_IPV4_ADDR or M2_SEC_IPV4_ADDR exists.

c
If you are using IPv6, check if M2_PRI_IPV6_ADDR or

M2_SEC_IPV6_ADDR exists.
3 If M2 IP does not exist, add M2 IP.

a
Run the CHG-IP-ADDR command to change LTE_SIGNAL_M2 to True.

added.
4 Run the RTRV-MBMS-MCECONF command and check the MCE IP

information.
Check whether the correct MCE IP information is being displayed.
5 If the MCE IP information is incorrect, change the IP information.

a
Run the CHG-MBMS-MCECONF command to change the IP information.
b Run the RTRV-MBMS-MCECONF command to check whether the

information has been updated correctly.
6 Check the ping status between the eNB-MCE.

a
Run ping -I [eNB IP] [MCE IP].

a
b Check the routing table regarding the eNB/MCE IP.

8 If the alarm remains, collect the SW log, and consult the next level of
maintenance with Samsung.
On-site Actions
support.

222
Chapter 3
Microcell Alarm
Reference
This chapter explains the common alarms that may issue during microcell
operation. A description of the alarm, its possible cause, and resolving procedures
are provided.
A2100100R UMP DSP RESTART

This alarm occurs when the DSP resets and restarts.
Basic Information
Severity
Relates to
Category
Location
CRITICAL
Software
PROCESSING
RACK[a]/SHELF[b]/SLOT[c]-UMP[d]/DSP[e]
Possible Cause
The DSP resets and restarts (by using the DSP Reset command or replacing the
DSP image).
Impact
Cell services related to the UMP will be unavailable during restart.
Remedy

223
Chapter 3 Microcell Alarm Reference
Alarm Raised
Step 1
FW Ver. NEW?
No
FW Update
Step 2
Yes
Yes
Collect SW Log
UMP DSP RESTART

Alarm Raised?
No
Step 3
INIT-DSP(UMP)
Step 4
UMP DSP RESTART

Alarm Raised?
No
Yes
Step 5
INIT-SYS
UMP DSP RESTART

Alarm Raised?
No
Yes
Replace Board
End
Set the LOC_TYPE to *, and then run this command.

After the firmware has been updated, check whether the alarm is raised.

c
Check whether the UMP DSP_RESTART alarm has been declared.

Check whether the UMP DSP_RESTART alarm has been declared.
4 Run the INIT-SYS command to restart the System.

224
b Check whether the UMP DSP_RESTART alarm has been declared.


225
A2100102R UMP PROCESS DOWN

This alarm occurs when a process is deactivated.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Software
PROCESSING
RACK[a]/SHELF[b]/SLOT[c]-UMP[d]/BLOCK_NAME
Possible Cause
The process is deactivated. You can find the cause by analysing the core file and
log file uploaded to the LSM.
Impact
If an alarm is generated continuously in a specific software block, service will be
unavailable.
Remedy

226
Alarm Raised
Re-activate Alarm
Raised Block
Step 1
Yes
Alarm Cleared After

Repair?
No
Backup the Faulty

NE Block Image
Step 2
Replace Block Image
Yes
Alarm Cleared
After Repair?
No
Collect SW Log and Restart NE
Step 3
Backup
LSM Log
Step 4
End
Activate the block that has raised the alarm.
Re-activate the disabled block by running the INIT-SW:UMP,

applicable block.
2 If the alarm keeps reoccurring, replace the block image. Backup the block
image for future analysis.
Backup the block image that continues to deactivate. Use the DNLD-SW
and UDT-SW commands to replace the block image.
applicable block.
227
3 If the problem cannot be solved by restarting a single block, restart the NE to

repair it.

applicable block.
4 To analyse the step by step process of clearing the PROCESS_DOWN alarm,

backup the LSM log.
Collect the logs in /log/system/corelog & /log/system/applog for the relevant
time frame.
support.

228
A2100217R UMP CPU TEMPERATURE HIGH

This alarm occurs when the CPU temperature exceeds the threshold.
Basic Information
Severity
Relates to
Category
Location
MINOR
Hardware
ENVIRONMENT
Possible Cause
The CPU temperature exceeded the threshold.
Impact
The board will be damaged.
Remedy


229
Alarm Raised
No
Step 1
FW Update
FW Ver. NEW?
Step 2
Yes
Yes
Collect SW Log
UMP CPU
TEMPERATURE HIGH
Alarm Raised?
No
Step 3
Check UMP Temperature
Collect SW Log
Step 4
INIT-SYS
Step 5
UMP CPU
TEMPERATURE HIGH
Alarm Raised?
No
Yes
On Site Action
End
Check the output on whether the NAME, VERSION, and BUILD_TIME of
each firmware are the most recent one.
log.
3 Run the RTRV-PRC-STS command to check the CPU temperature.

Check the value of output TEMPERATURE[C] to determine if the alarm
declared condition (temperature over 97C) has been reached.
4 After collecting the SW log, run the INIT-SYS command to restart the
system.
230
On-site Actions
Check the status of the PWR/ALM LED on the fan module at the front of the
DU. Green indicates Normal and Red indicate fan failure.
2 If the PWR/ALM LED is green, check that the fan is rotating normally.
3 Unmount the board for which an alarm is generated and check the inside of the
DU shelf to find any element or foreign material that may have blocked the air
flow. If an air filter is mounted on the DU shelf, check that the air filter is in
proper working condition.
4 Unmount the CPU heat sink of the UMP. Check that the thermal pad size is
sufficient and that the contact between the CPU and heat sink is good.
5 Mount the UMP and check if an alarm is generated after loading completes.
o
If the alarm is cleared, record the current status and observe any
reoccurrence.
If the alarm remains, replace the UMP.
For information on Microcell replacement, see Samsung MBS (LTE) Outdoor

Microcell Installation Manual.

231
A2100300R UMP DISK FULL

This alarm occurs when the disk usage exceeds the threshold.
Basic Information
Severity
Relates to
Category
Location
Software
QOS
Possible Cause
The threshold value can be retrieved using the RTRV-ALM-THR command.
Impact
Defaults
Minor: 85 %
Major: 90 %
Critical: 95 %
Remedy

232
Alarm Raised
Step 1
Run RTRV-ALM-THR
No

Yes
Run CHG-ALM-THR
Alarm Still Raised?
No
Yes
Collect SW Log
Step 2
Check Other Items
Alarm Still Raised?
Step 3
Alarm Level = Minor
No
Yes
No
Delete LOG
Folder Files
Delete TEMP
Folder Files
Alarm Still Raised?
No
Yes
Replace Board
End

DISK_FULL alarm.

233
If the DISK_FULL threshold is lower than the default value, do the following
steps:
Set the ALARM_TYPE to DISK_FULL for the CHG-ALM-THR. Enter the

default value for each threshold level.

2 Check this category in which the DISK_FULL alarm can occur.

The DISK_FULL alarm can occur if more than one passive package exists as a
result of an online upgrade. Use the RTRV-PKG-VER command to check the
number of passive packages.
After an online upgrade, run the DLT-PASV-PKG command to delete the

passive packages.
b Check whether the DISK_FULL alarm has been cleared.

o
If the DISK_FULL Alarm level is CRITICAL or MAJOR, delete the files

in the LOG and TEMP folders for the UMP board.
If the level is MINOR, delete the files in the TEMP folder for the UMP
board.
If the alarm remains, replace the faulty board.For information on Microcell
replacement, see Samsung MBS (LTE) Outdoor Microcell Installation Manual.

234
A2100301R UMP MEMORY FULL

Basic Information
Severity
Relates to
Category
Location
Software
QOS
Possible Cause
Impact
Defaults
Minor: 95 %
Major: 96 %
Critical: 97 %
Remedy

235
Alarm Raised
Step 1
Run RTRV-ALM-THR
No

Yes
Run CHG-ALM-THR
Alarm Still Raised?
No
Yes
Collect SW Log
Step 2
Check Other Items
Alarm Still Raised?
Step 3
Alarm Level = Minor
No
Yes
No
Delete LOG
Folder Files
Delete TEMP
Folder Files
Alarm Still Raised?
No
Yes
Replace Board
End

MEMORY_FULL alarm.

236
If the MEMORY_FULL threshold is lower than the default value, do the

following steps:
Set the ALARM_TYPE to MEMORY_FULL for the CHG-ALM-THR.

Enter the default value for each threshold level.
b If the MEMORY_FULL alarm is cleared after changing the threshold

value, end the Remedy.
If the MEMORY_FULL alarm is not cleared after changing the threshold

value, collect the SW log.
d If the threshold is set higher than the default value, collect the SW Log.
occur.
i

ii

i
Run the UDT-FW-BAT command to delete the FW image.
ii
Check whether the MEMORY_FULL alarm is cleared after running


o
If the MEMORY_FULL Alarm level is CRITICAL or MAJOR, delete the

files in the LOG and TEMP folders of the UMP board.
If the Alarm level is MINOR, delete the files in the TEMP folder of the
UMP board.
The locations of folders for the files to delete are: LOG: /var/log and TEMP:
/tmp.

For information on system replacement, see Samsung MBS (LTE) Outdoor

237
A2100302R UMP OVERLOAD

Basic Information
Severity
Relates to
Category
Location
Software
QOS
Possible Cause
The threshold value can be retrieved by using RTRV-ALM-THR command.
Impact
Some software blocks will operate abnormally. If an alarm is generated
continuously, the UMP board will be reset.
Defaults
Minor: 85 %
Major: 90 %
Critical: 95 %
Remedy

238
Alarm Raised
Step 1
No
Yes
Alarm Still Raised?
No
Yes
Collect SW Log
Step 2
Check Other Items
Alarm Still Raised?
No
Yes
Step 3
No
Yes
SESSION CLOSE
Alarm Still Raised?
No
Yes
Step 4
Replace Board
End

OVERLOAD alarm.

239
If the OVERLOAD threshold is lower than the default value, do the following
steps:
Set the ALARM_TYPE OVERLOAD for the CHG-ALM-THR. Enter the

default value for each threshold level.
b If the OVERLOAD alarm is cleared level by level after changing the

a
OVERLOAD alarm is cleared level by level, terminate the procedure.

are repeated.
i
ii
If the OVERLOAD alarm is cleared level by level after changing the

threshold value, terminate the procedure.
connected to the UMP. If it is cleared, terminate the procedure.


240
A2100305R UMP PACKET ERROR

Basic Information
Severity
Relates to
Category
Location
MINOR
Software
EQIPMENT
Possible Cause
Error packets rate exceeded the threshold level.
The threshold value can be retrieved by using RTRV-PACKETERROR-CONF
command.
Impact
Remedy


241
Alarm Raised
Step 1
Is New F/W
No
UMP/ECP FW Update
Step 2
Yes
SW Log Collection
Step 3
Reset UMP
Step 4
Alarm Clear?
No
Yes
END
On Site Action
Check whether the FW is the latest version.
2 If not, update the FW to the latest version.

Run the DNLD-FW command to download the latest version and the UDT-FW
command to update the firmware. If the alarm is declared even when the
firmware is up to date, collect the SW log.
3 Reboot the UMP board where the alarm occurred.

recheck again. If not, collect the SW log and share with Samsung for the next
The UMP and ECP collects all files under the /var/log folder.
On-site Actions
Replace the board.
Replacement Manual.

242
A2100351R UMP CLOCK FAIL

Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
Possible Cause
The clock frequency (10 MHz, Even) of the clock module has a deviation beyond
normal parameters or there is no clock.
Impact
The service will be unavailable.
Remedy


243
Alarm Raised
UMP FW Ver. NEW?
Step 1
No
UMP FW Update
Step 2
Yes
Yes
Collect SW Log
UMP CLOCK FAIL

Alarm Raised?
No
Step 3
Restart system
UMP CLOCK FAIL

Alarm Raised?
No
Yes
Retrieve Alarm List
Step 4
RTRV-CLOCKSRC-DATA
Clock Source
Alarm Raised?
Yes
Actions To Clear Alarm
No
UMP CLOCK FAIL
Alarm Raised?
Yes
No
Step 5
No
Clock Source
GPS ?
Yes
RTRV-GPS-STS
Step 6
GPS FW Ver. NEW?
No
GPS FW Update
Yes
UMP CLOCK FAIL
Alarm Raised?
Yes
No
INIT-GPS
Step 7
UMP CLOCK FAIL

Alarm Raised?
No
Yes
Step 8
Collect SW Log
Notify Samsung
End
latest version.

244

If the alarm is being raised even when firmware is the latest version, collect
the SW log and continue with the next step.

Check whether the UMP CLOCK FAIL alarm has been declared.

Check whether the UMP CLOCK FAIL alarm is raised even after a system
restart.
4 Run the RTRV-CLOCKSRC-DATA command to check the clock source value.

Run the RTRV-ALM-LIST command to check whether an alarm related to the
Clock Source exists. If so, follow the remedy.
Check whether an alarm related to the clock source has been raised.
5 If the clock source is GPS, check the GPSR state by running the RTRV-GPSSTS command.
Check whether the outputs LOCK_STATE and HOLDOVER_STATE are
GPS_LOCKED and GPS_NOT_HOLDOVER.
6 Run the RTRV-GPS-INVT command to check whether the GPS firmware is

the latest version.
Check whether the FW_VERSION on the output window displays the latest
version.
If the alarm is being raised even when firmware is the latest version, continue
with the next step.
8 Run the INIT_GPS command to restart the GPSR.

Check whether the UMP CLOCK FAIL alarm is raised even after a GPS reset.

245
A2100367R UMP POWER FAIL

This alarm occurs when the power supply is in abnormal state.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
Possible Cause
Power supply is in abnormal state.
Impact
The service will be unavailable.
Remedy


246
Alarm Raised
FW Ver. NEW?
Step 1
No
FW Update
Step 2
Yes
Yes
Collect SW Log
UMP POWER FAIL

Alarm Raised?
No
Step 3
INIT-SYS
Step 4
UMP POWER FAIL

Alarm Raised?
No
Yes
Collect SW Log
On Site Action
End
latest version.
Check the output on whether the NAME, VERSION, and BUILD_TIME of
each firmware are the most recent one.
the SW log.
3 After collecting the SW log, run the INIT-SYS command to restart the
system.
On-site Actions
Power-cycle the system.

247
3 If the alarm remains, replace the system.

248
A2100370R UMP MEMORY FAIL

This alarm occurs when there are operation errors (data read/write errors) in the
memory device.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
Possible Cause
Operation errors (data read/write) in the memory device.
Impact
Remedy


249
Alarm Raised
FW Ver. NEW?
Step 1
No
FW Update
Step 2
Yes
Yes
Collect SW Log
UMP MEMORY FAIL

Alarm Raised?
No
Step 3
INIT-PRC (UMP,
RESET MODE=HW)
Step 4
UMP MEMORY FAIL

Alarm Raised?
No
Yes
On Site Action
End
latest version.

the SW log.

a
b Check whether the UMP MEMORY_FAIL alarm has been declared.

On-site Actions
To resolve the problem:
Replace the board.

250


251
A2100372R UMP DSP FAIL

This alarm occurs when there is a communication problem between the CPU and
DSP.
Basic Information
Severity
Relates to
Category
Location
CRITICAL
Software
EQUIPMENT
RACK[a]/SHELF[b]/SLOT[c]-UMP[d]/DSP[e]
Possible Cause
The DSP initialization is not completed.
The CPU cannot receive the keep-alive response from the DSP.
The core, modem, or the FPGA of the DSP is not operating normally.
Impact
Cell services related to the DSP will be unavailable.
Remedy


252
Alarm Raised
FW Ver. NEW?
Step 1
No
FW Update
Step 2
Yes
Yes
Collect SW Log
UMP DSP FAIL

Alarm Raised?
No
Step 3
INIT-DSP(UMP)
Step 4
UMP DSP FAIL

Alarm Raised?
No
Yes
Step 5
INIT-SYS
UMP DSP FAIL

Alarm Raised?
No
Yes
Replace Board
End

After the firmware has been updated, check whether the alarm is raised.

Check whether the UMP DSP_FAIL alarm has been declared.

253

On-site Actions
Replace the board.

254
A2100380R UMP PORT DOWN

This alarm occurs when the backhaul port is down.
Basic Information
Severity
Relates to
Category
Location
CRITICAL
Hardware
EQUIPMENT
Possible Cause
A link is down (for example, due to a bad port connection) of the backhaul port.
Impact
The board cannot communicate with the LSM or external devices.
Remedy


255
Alarm Raised
Step 1
UMP FW Ver. NEW?
No
UMP FW Update
Reset UMP
Step 2
Yes
Step 3
No
Check ELINK Status
Port Locked?
UMP PORT_DOWN
Clear?
Yes
Yes
Unlock Port
No
Step 4
UMP PORT_DOWN
Clear?
On Site Action
End
Run the RTRV-PRC-FW command to check whether the firmware is the latest
version. Check whether the VERSION of each firmware is the most recent one.
Then run the INIT-SYS command to restart the system.
3 Run the RTRV-ELINK-STS command to check whether the value of

ADMINISTRATIVE_STATE is linkUnlocked.
4 If the RTRV-ELINK-STS output ADMINISTRATIVE_STATE is set to

linkLocked, use the CHG-ELINK-CONF command to change STATUS to
EQUIP and ADMINSTRATIVE_STATE to linkUnlocked. Then check
whether the alarm has been cleared.
On-site Actions
Check that the Ethernet cable is correctly connected and that there is no
external damage.
2 Check that the optical cable is correctly connected and that there is no external
damage or bending.
256
3 Check that the connected optical cables (Single or Multi-Mode) are suitable
for the installed optical module type (Single or Multi-Mode).
4 Check that the optical module is supported by the system.

5 Clean the optical module and measure its optical power. Check the measured
optical power against the product specifications in the installation manual.
Replace the optical module if necessary.
6 Check the status of the equipment connected to the backhaul port (for example,
router and switch).
7 If the equipment connected to the backhaul port is not working properly, reset
or replace the equipment.
8 Power-cycle the system.

9 If the alarm is not cleared, record the failure details to the RMA TAG and
replace the system. Record the details including port connection configuration
status, the part number of mounted optical module, the optical cable type, and
so on.

257
A2100439R UMP ETHERNET HALF DUPLEX

DETECTED
This alarm occurs when the backhaul port status is up and duplex mode is half
duplex.
Basic Information
Severity
Relates to
Category
Location
MINOR
Software
EQUIPMENT
Possible Cause
The backhaul port status is up and duplex mode is half duplex.
Impact
The service will be degraded due to the high risk of packet loss.
Remedy


258
Alarm Raised
Step 1
Retrieve autonego, speed,

duplex Config of both eNB BH
and oppsite Device
Step 2
Config mismatch?
No
Yes
Step 3
Make configure match and

Down and up BH link
Step 4
Clear Alarm ?
INIT-SYS
No
Yes
END
On Site Action
Check the Autonego, Speed, and Duplex settings of both the eNB and the
remote station's equipment.
Run the RTRV-ELINK-CONF command.
The commands used on the remote stations equipment may differ depending on
the manufacturer, and the following are the commands relevant to each major
equipment manufacturer.
- Cisco: show running-conifig {interface name}
- NETGEAR: show port {<unit/slot/port> | all}
- 3Com: display interface [interface_type | interface_type interface_number]
2 Check whether the Autonego, Speed, and Duplex are all set to the same value.
3 If the Autonego, Speed, and Duplex settings are different from each other, set
them to the same value. If the alarm has occurred despite the above parameters
being set to the same value, reboot the eNB and check again if the alarm
occurs.
Execute the INIT-SYS command.
On-site Actions
259
Check link aggregation status by disconnecting and then connecting the cable
again.
2 If disconnecting and then connecting the cable does not clear the alarm,
replace the cable.
3 If alarm remains, replace the board.

Replacement Manual.

260
A2148389R RU LOW GAIN

This alarm occurs when the gain estimated from the measured RF output power is
below the threshold.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
RACK[a]/SHELF[b]/SLOT[c]-RU[d]/PATH[e]
Possible Cause
The RU is faulty.
Impact
Cell services related to the RU will be unavailable.
Remedy


261
Alarm Raised
Collect SW Log
Step 1
System Restart
Alarm Raised?
Step 2
No
Yes
On Site Action
End
After collecting the SW log, run the INIT-SYS command.

Check whether the alarm is raised after the system restart.
2 If the alarm remains, share the SW log with Samsung for the next level of
On-site Actions

262
Low gain alarm occured
Power off then Power on

cyclely
Alarm cleared?
Yes
No
Replace the smallcell
Recording actions and

leave the site
Observe the alarm reoccurrence

263
A2148391R RU OVER POWER

This alarm occurs when the output power exceeds the threshold.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
Possible Cause
The digital input power level or the RF output power level exceeded the threshold.
Impact
Cell services related to the RU will be unavailable.
Remedy


264
Alarm Raised
Collect SW Log
Step 1
TX PF POWER >= Alarm

Threshold?
No
Change Alarm Threshold
Yes
Yes
RU OVER POWER
Alarm Raised?
No
Step 2
System Restart
Step 3
On Site Action
End
After collecting the SW log, compare the values of RTRV-RU-CONF output

OVER_PWR_ALARM_TH and RTRV-RU-STS output TX_RF_POWER. If
the threshold value is abnormal, change the threshold to a normal level.
Run the RTRV-RU-CONF command to check the

OVER_PWR_ALARM_TH value for the RU_ID that has raised the alarm.
b Run the RTRV-RU-STS command to check the TX_RF_POWER value

for the RU_ID that has raised the alarm.
Run the CHG-RU-CONF command to change the OVER_PWR_ALARM

_TH value, for the RU that has raised the alarm, to a normal level
d After changing the threshold, check whether the alarm is raised.

2 If the alarm is not cleared, run the INIT-SYS command.
On-site Actions

265

cyclely
Alarm cleared?
Yes
No

leave the site

266
A2148392R RU VSWR FAIL

This alarm occurs when the VSWR measurement (return loss) is below the
threshold.
Basic Information
Severity
Relates to
Category
Location
MINOR
Hardware
EQUIPMENT
Possible Cause
The VSWR measurement (return loss) is below the threshold.
Impact
Remedy


267
Alarm Raised
Collect SW Log
Step 1
Threshold Normal?
No
Change Threshold
Yes
Yes
Alarm Raised?
No
Step 2
System Restart
Step 3
On Site Action
End

VSWR_FAIL_ALARM_THR and RTRV-RU-STS output VSWR. If the
threshold value is abnormal, change the threshold to a normal levels.

VSWR_FAIL_ALARM_THR value for the RU_ID that has raised the
alarm.
b Run the RTRV-RU-STS command to check the VSWR value for the
RU_ID that has raised the alarm.
Run the CHG-RU-CONF command to change the VSWR_FAIL_ALARM

_THR value, for the RU that has raised the alarm, to a normal level

On-site Actions

268
VSWR Fail Alarm occured
Change Antenna tilting
VSWR value changed?
Take actions after confirm

influence from nearby
Basestation
Yes
No
Connector check
- Connector damage or not?
- Water seepage in connector or not?
- Foreign substance infiltrated in connector or not?
Power off smallcell
Yes
Disconnect Antenna cable/check

the connector status/eliminate
the defect-causing element
Reassemble the antenna cable
Alarm cleared?
Power on smallcell
No
Swap the antenna cables
connection between normal and
abnormal path in smallcell
Power off smallcell
Power on smallcell
Inpsect the antenna and cable

and replace them
Yes
Alarm cleared
No
Recording actions and leave the

site
Check the VSWR value change by observing the change in the antenna tilting.
If any changes are found, take actions after checking if the effect is caused by
the nearby base station. If not, continue with the next step.
2 After turning SmallCell power off, check the state of the cable from the path
with the error by disconnecting it from the SmallCell. Check if the cable is
connected properly, damaged by moisture or foreign substances etc.
3 If moisture damage is found on the cable or connector, eliminate the moisture

by using cotton swaps or dry towels. If any foreign substances are found on
them, remove them. Replace the antenna cable or SmallCell if the connector is
269
damaged.
4 If the alarm is cleared after powering on the SmallCell, leave the site after
recording the actions taken.
5 If the alarm remains even though the cable and its connection state is normal,
turn the SmallCell power off.
6 After connecting a cable from the path where the alarm is not generated to the
SmallCell with the SmallCell power on, check if the alarm is maintained.
7 If the alarm is cleared, reassemble the cable near the antenna or replace the
cable or antenna as the alarm seems to be caused by the cable or its connection
failure.
8 If the alarm is maintained after step 6, replace the corresponding SmallCell.


270
A2148408R RU DIGITAL INPUT LOW

This alarm occurs when the digital input power level is at or below the threshold.
Basic Information
Severity
Relates to
Category
Location
MINOR
Hardware
EQUIPMENT
RACK[a]/SHELF[b]/SLOT[c]-RU[d]/PATH[e]/FA[f]
Possible Cause
The digital input power level is at the threshold or less.
Impact
Remedy


271
Alarm Raised
Collect SW Log
Step 1
TSSI <=
Alarm Threshold?
No
Yes
Yes
RU DIGITAL INPUT LOW

Alarm Raised?
No
Step 2
System Restart
Step 3
On Site Action
End

DIGITAL_INPUT_LOW_ALARM_TH and RTRV-RU-STS output
TSSI_IQ_LEVEL. If the threshold value is abnormal, change the threshold to
a normal level.

DIGITAL_INPUT_LOW_ALARM_TH value for the RU_ID that has
raised the alarm.
b Run the RTRV-RU-STS command to check the TSSI_IQ_LEVEL value

Run the CHG-RU-CONF command to change the

DIGITAL_INPUT_LOW_ALARM_TH value, for the RU that has raised
the alarm, to a normal level

On-site Actions
272

cyclely
Alarm cleared?
Yes
No

leave the site

273
A2148396R RU RX PATH FAIL

This alarm occurs when the RSSI measurement is below the threshold.
Basic Information
Severity
Relates to
Category
Location
MINOR
Hardware
EQUIPMENT
RACK[a]/SHELF[b]/SLOT[c]-RU[d]/PATH[e]/FA[f]
Possible Cause
The RSSI measurement is below the threshold.
Impact
Remedy


274
Alarm Raised
Collect SW Log
Step 1
RSSI >=
Alarm Threshold?
No
Yes
Yes
RU RX PATH FAIL Alarm

Raised?
No
Step 2
System Restart
Step 3
On Site Action
End

RX_PATH_FAIL_TH and RTRV-RU-STS output RSSI_IQ_LEVEL. If the
threshold value is abnormal, change the threshold to a normal level.
Run the RTRV-RU-CONF command to check the RX_PATH_FAIL_TH

value for the RU_ID that has raised the alarm.
b Run the RTRV-RU-STS command to check the RSSI_IQ_LEVEL value

Run the CHG-RU-CONF command to change the RX_PATH_FAIL_TH

value, for the RU that has raised the alarm, to a normal level

On-site Actions

275

cyclely
Yes
Alarm cleared?
No

leave the site

276
A2180350R GPSR ANTENNA FAIL

This alarm occurs when the antenna cable is disconnected.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
Possible Cause
The feeding current to the antenna side is at the specified open or short level.
The antenna cable is disconnected.
Impact
This alarm does not have direct impact on the system. However, it can be the
reason for the GPSR LOCKING FAIL and GPSR HOLDOVER 8H alarms.
Remedy


277
Alarm Raised
Step 1
No
UMP/GPS FW Update
Yes
Yes
Collect SW Log
Step 2
GPS ANTENNA FAIL

Alarm Raised?
No
Restart GPS
GPS ANTENNA FAIL

Alarm Raised?
No
Yes
Collect SW Log
Step 3
On Site Action
End
Set the LOC_TYPE to *, and then run the RTRV-PRC-FW command.

d Check whether the GPSR ANTENNA FAIL alarm has been declared.
e

latest versions.

278
g Check whether the GPSR ANTENNA FAIL alarm has been declared.
2 Run the INIT-GPS command to restart the GPSR.
On-site Actions
Any trace of lightning and

waterlogging Y/N
Yes
Replace GPS antennal

No
Check voltage at the SmallCell

GPS port end.
4.5~5.5 V?
No
Yes
Yes
Error recovered after cable

replacement?
No
Yes

splitter replacement?
No
Yes

No
End Process
Replace
Check for any traces of lightning in the GPS arrestor.

279
For lightning traces, look for burnt marks of the GPS arrestor or surrounding
cables.
o
If any traces of lightning are found, replace the SmallCell and GPS
antenna installation materials.
If traces of lightning are not found, continue with the Step 2.
2 Separate the cable from the GPS port, and measure the voltage of the GPS port
connector.
Measure the voltage by touching (+) end of a Digital Voltage Meter (DVM) to the
core wire and (-) end to the outside of the connector.
o
If the measurement is between 4.5 to 5.5 V, continue with the Step 3.
If the measurement is not within this range, replace the SmallCell.
3 Check and replace the GPS installation materials and check if the alarm is
cleared.
If the errors/failures have been recovered after checking the cable

connection state and replacing the materials, terminate the inspection
procedure. If not, continue with the following steps.
b Check the divider connection state and replace the parts. If the
errors/failures have been recovered, terminate the inspection procedure. If
not, continue with the following step.
Check the GPS antenna connection state and replace the parts if needed.
When the errors/failures are recovered, terminate the inspection process.
4 After changing the SmallCell, check if the errors or failures are repaired.
o
If the GPS antenna and installation materials are found to be defective, the
SmallCell is not defective. Therefore, RMA will not be processed.
For information on SmallCell replacement, see LTE eNB Hardware Addition and
Replacement Manual.

280
A2180360R GPSR TOD MSG MISSED

This alarm occurs when initialization fails due to the GPSR restart or GPSR
module failure.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Software
COMMUNICATIONS
Possible Cause
The main processor does not receive the TOD message from the GPSR.
Impact
Remedy


281
Alarm Raised
Step 1
No
UMP/GPS FW Update
Yes
Yes
Collect SW Log
GPSR TOD MSG MISSED

Alarm Raised?
No
Step 2
UMP PROCESS DOWN

(scm)Alarm Raised?
Yes
Actions To Clear
UMP PROCESS DOWN (scm)
No
INIT-SW UMP scm
Step 3
GPSR TOD MSG MISSED

Alarm Raised?
No
Yes
Restart GPS
Step 4
GPSR TOD MSG MISSED

Alarm Raised?
No
Yes
INIT-SYS
(RESET MODE=HW)
Step 5
GPSR TOD MSG MISSED

Alarm Raised?
No
Yes
Collect SW Log
Notify Samsung
End

282
Set the LOC_TYPE to * and then run the RTRV-PRC-FW command.

d Check whether the GPSR TOD MSG MISSED alarm has been declared.
e

latest versions.
h Check whether the GPSR TOD MSG MISSED alarm has been declared.
2 Run the RTRV-ALM-LIST command to check the list of alarms and then
If the UMP PROCESS_DOWN (scm) alarm is on the list, follow the

remedy.
b If the SCM block is currently running, set the PRC_UNIT_TYPE and

SW_UNIT_NAME to UMP and SCM Image Name respectively and then
run the INIT-SW command
3 If the alarm is being raised, run the INIT-GPS command to restart the GPSR.

a
b Check whether the GPSR TOD MSG MISSED alarm has been declared.

283
A2180361R GPSR LOCKING FAIL

This alarm occurs when the normal GPS satellite signal cannot be received.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
EQUIPMENT
Possible Cause
A normal GPS satellite signal is not received.
No GPS satellite tracking for one hour.
Impact
reason for the GPSR HOLDOVER 8H alarm.
Remedy


284
Alarm Raised
Step 1
No
UMP/GPS FW Update
Yes
Yes
Collect SW Log
GPS LOCKING FAIL

Alarm Raised?
No
Step 2
GPS ANTENNA FAIL

Alarm Raised?
Yes
Actions To Clear
GPS ANTENNA FAIL
No
RTRV-GPS-STS
Step 3
GPS LOCKING FAIL

Alarm Raised?
No
Yes
Restart GPS
Step 4
GPS LOCKING FAIL

Alarm Raised?
No
Yes
Collect SW Log
On Site Action
End


285
d Check whether the GPSR LOCKING FAIL alarm has been declared.
e

latest versions.
g [Check] Check whether the GPSR LOCKING FAIL alarm has been
declared.
2 Run the RTRV-ALM-LIST command to check whether the GPS ANTENNA

FAIL alarm has been raised. If it has, follow the remedy.
After running the RTRV-GPS-STS command, check the LOCK_STATE,
HOLDOVER_STATE, and SAT_N values to determine the number of GPS
satellites that are being used for tracking.
3 If a LOCKING_FAIL alarm is raised when there is no ANTENNA_ FAIL, run

the INIT-GPS command to restart the GPSR.
Run the INIT-GPS command.
b Check whether the GPSR alarm has been declared.

On-site Actions

286
Inspect installation environment

based on the GPS antenna
installation guide.
Is the satellite signal

improved?
Yes
No

Yes
No
Replace the SmallCell
End process
Inspect installation environment for the GPS antenna and check if it clears the
alarm.
GPS antennas must be installed, securing as much open sky as possible

(the horizontal field of view to be 360, the vertical to be 160). If the
field of view is not secured sufficiently, change the location for GPS
antenna installation.
b If the alarm is not recovered or the satellite signals are not improved,
replace the SmallCell.
For improvement of the satellite signals, execute RTRV-GPS-STS command.
There should be more than 4 (longer than 1 minute) satellites (SATNs) observed.
2 After changing the SmallCell, check if the alarm is cleared.

o
For information on replacement of SmallCell and other parts, see LTE eNB
Hardware Addition and Replacement Manual.

287
A2180368R GPSR FUNCTION FAIL

This alarm occurs when the GPSR module fails.
Basic Information
Severity
Relates to
Category
Location
CRITICAL
Hardware
EQUIPMENT
Possible Cause
The GPSR is reset by restarting the GPSR or when the GPSR module failure
occurs due to one of the following reasons:
Power failure (when the input power is 5.2 V or lower and 5.8 V or higher).
The Electronic Frequency Control (EFC) value is either +100 % or -100 %.
Deviation failure: Even sec (or 1 PPS) jumps over 100 ns.
Time not set: GPS time is not set and it is neither active nor standby.
Impact
Remedy


288
Alarm Raised
Step 1
No
UMP/GPS FW Update
Yes
Yes
Collect SW Log
GPS
FUNCTION FAIL
Alarm Raised?
No
Step 2
Restart GPS
Step 3
GPS
FUNCTION FAIL
Alarm Raised?
No
Yes
Collect SW Log
On Site Action
End

d Check whether the GPSR FUNCTION FAIL alarm has been declared.
e

latest versions.

289
g Check whether the GPSR FUNCTION FAIL alarm has been declared.
2 If the alarm is being raised, run the INIT-GPS command to restart the GPSR.
On-site Actions
After entering
Reboot the SmallCell
No
SmallCell error recovered Y/N

Yes
Monitoring
Change the SmallCell
Restart the SmallCell power and check if the FUNCTION_FAIL alarm is

o
If the alarm is cleared, monitor the UCCM state.
2 After replacing the SmallCell, check if the FUNCTION_FAIL alarm is

o
For information on replacement of SmallCell and other parts, see LTE eNB

290
A2180601R GPSR HOLDOVER 8H

This alarm occurs when the threshold time is exceeded after transition to a
holdover state.
Basic Information
Severity
Relates to
Category
Location
CRITICAL
Hardware
EQUIPMENT
Possible Cause
8 hours have passed since the transition to the holdover state.
Impact
Remedy


291
Alarm Raised
Step 1
No
UMP/GPS FW Update
Yes
Yes
Collect SW Log
GPS HOLDOVER 8H
Alarm Raised?
No
Step 2
GPS ANTENNA FAIL,

LOCKING FAIL
Alarm Raised?
Yes
Actions To Clear
GPS ANTENNA FAIL,
LOCKING FAIL
No
RTRV-GPS-STS
Step 3
GPS HOLDOVER 8H
Alarm Raised?
No
Yes
Restart GPS
Step 4
GPS HOLDOVER 8H
Alarm Raised?
No
Yes
Collect SW Log
On Site Action
End


292
d Check whether the GPSR HOLDOVER 8H alarm has been declared.

e

latest versions.
g Check whether the GPSR HOLDOVER 8H alarm has been declared.

b Check the LOCK_STATE and HOLDOVER_STATE.

3 If a HOLDOVER 8H alarm is being raised when there is no ANTENNA FAIL
or LOCKING_FAIL alarm, run the INIT-GPS command to restart the GPSR.
Check whether the GPSR alarm is being raised.
On-site Actions

293
FAIL alarm actions
Yes

occurrence history
No
Reboot the SmallCell
Yes
The SmallCell error is

recovered? (Y/N)
No
Monitoring

occurrence.
o
If no record of ANTEANNA_FAIL/LOCKING_FAIL occurrence is found,

2 After powering on the SmallCell, check if the UCCM alarm is cleared.

o
3 After replacing the SmallCell, check if the FUNCTION_FAIL alarm is

o


294
A2180624R GPSR CLOCK PHASE ABNORMAL

This alarm occurs when the clock phase of the GPS is drifted abnormally
Basic Information
Severity
Relates to
Category
Location
CRITICAL
Hardware
EQUIPMENT
Possible Cause
The clock phase of the GPS is drifted abnormally
Impact
All cell services will be unavailable
Remedy


295
Alarm Raised
Step 1
No
UMP/GPS FW Update
Yes
Yes
Collect SW Log
GPS CLOCK PHASE

ABNORMAL
Alarm Raised?
No
RTRV-GPS-STS
Step 2
Restart GPS
GPS CLOCK PHASE

ABNORMAL
Alarm Raised?
Step 3
No
Yes
Collect SW Log
Notify Samsung
End

d Check whether the GPSR CLOCK PHASE ABNORMAL alarm has been
declared.

latest versions.

296
g Check whether the GPSR CLOCK PHASE ABNORMAL alarm has been
declared.
2 If the alarm is not cleared, check the TINT value, and then run the INIT-GPS
b Check the TINT value.

c
Run the INIT-GPS command.
d Check whether the GPS CLOCK PHASE ABNORMAL alarm has been
declared.

297
A2184001R PTPM TOD MSG MISSED

This alarm occurs when the UMP does not receive the TOD message from the
PTPM.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Software
COMMUNICATIONS
RACK[a]/SHELF[b]/SLOT[c]-PTPM[d]
Possible Cause
The main processor does not receive the TOD message from the PTPM.
Impact
Remedy


298
Alarm Raised
Step 1
UMP FW Ver. NEW?
No
UMP FW Update
Yes
Yes
Collect SW Log
PTPM
TOD MSG MISSED
Alarm Raised?
No
Step 2
UMP PROCESS DOWN

(ptpm) Alarm Raised?
Yes
Actions To Clear
UMP PROCESS DOWN (ptpm)
No
INIT-SW UMP ptpm
PTPM
TOD MSG MISSED
Alarm Raised?
No
Yes
Step 3
PTPM Alarm Raised?
Yes
Actions To Clear PTPM Alarm
No
PTPM
TOD MSG MISSED
Alarm Raised?
No
Yes
Step 4
INIT-SYS
(RESET MODE=HW)
PTPM
TOD MSG MISSED
Alarm Raised?
No
Yes
Step 5
Collect SW Log
On Site Action
End

299

d Check whether the PTPM TOD MSG MISSED alarm has been declared.
2 Run the RTRV-ALM-LIST command to check the list of alarms and then
If the UMP PROCESS_DOWN (ptpm) alarm is on the list, follow the

remedy.
b If the PTPM block is currently running, set the SW_UNIT_NAME to

PTPM Image Name, and then run the INIT-SW command.
Check whether the PTPM TOD MSG MISSED alarm has been declared.
3 Run the RTRV-ALM-LIST command to check the list of alarms and whether
PTPM alarm is on the list.
If there are PTPM alarms besides the TOD MSG MISSED alarm, follow the
remedy. Then check whether the TOD MSG MISSED alarm has been raised.
4 If the alarm is being raised, run the INIT-SYS command to restart the system.
a
b Check whether the TOD MSG MISSED alarm has been raised.
On-site Actions
Reset the UMP (or IMP) board.
2 If the alarm remains, replace the UMP (or IMP) board.

For information on UMP (or IMP) board replacement, see Samsung MBS (LTE)

300
A2184003R PTPM NO CURRENT PTP MASTER

This alarm occurs when the IEEE1588 clock slave device fails to collect
information from the grand master clock when normal communication between the
two is available.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
COMMUNICATIONS
Possible Cause
The IEEE1588 clock slave device fails to collect information from the grand
master clock when normal communication between the two is available.
Impact
This will cause the IEEE1588 clock to fail.
Remedy


301
Alarm Raised
No
Step 1
PTPM Device State

Abnormal?
Yes
Action To Clear
Clock Dev Not Init Alarm
No
Change PTP Domain Number

(CHG-PTPM-CONF)
No
Step 2
PTP domain number

Available check?
No Current PTP Master

Alarm Cleared?
Yes
Step 3
No
No
GM IP available?
Change GM IP
(CHG-GM-IP)

Alarm Cleared?
Yes
Step 4
No
PTP Interface IP available?
No

Alarm Cleared?
IPAddrConf IEEE1588 attr

(CHG-IP-ADDR)
Yes
Step 5
Yes
Yes
No
No
PTP BH interface
available?
Yes
Step 6
GM & PTP Interface

Ping Test Successful?
No
Check Network Status
Yes
Step 7
Collect SW Log
Step 8
PTPM Restart

Alarm Cleared?
Yes
No
On Site Action
End
Check whether the PTPM device state is normal.
Run the RTRV-PTPM-STS command to check the PTPM device state.
b Check whether the PTPM device state displays as running.

c
If the state is not displayed as running, follow the ClockDev NotInit alarm
remedy.
2 Check the PTP domain number configuration.

a
Run the RTRV-PTPM-CONF command to check the PTP domain number

configuration value.

302
b If the PTP domain number value is not the right value, run the CHGPTPM-CONF command to change the PTP domain number.
3 Check the IEEE 1588 Grand master server IP configuration.

a
Run the RTRV-PTPM-STS command to check whether the grand master

IP address is correct.
b If the grand master IP address obtained from the RTRV-PTPM-STS

command is not valid, use the RTRV-GM-INFO command to check
whether the MASTER_IP_1 or the MASTER_IP_2 is the Grand master IP.
If it is not configurable through GM-INFO, run the CHG-GM-IP

command to change the Grand master IP address.
d Run the CHG-GM-INFO command to change the MASTER_IP_1 or the

MASTER_IP_2 address.
After 30 seconds, run the RTRV-PTPM-STS command to check whether

the current Grand master IP address is available.
4 Check the IEEE 1588 PTP Interface IP configuration.

a
Run the RTRV-PTPM-ADDR command to check the PTP slave IP

configuration.
b Run the RTRV-IP-ADDR command to check whether the IEEE 1588

attribute is correctly selected for the PTP interface.
Run the CHG-IP-ADDR command to select the IEEE 1588 attribute for
the BH interface.
5 Check the PTP BH Interface status.

Run the RTRV-ELINK-STS command to check the status of the PTP slave
interface.
6 Run a ping test to check the Grand master network status.

a
After connecting to the Enb, run a ping test from the Enb to the grand
master IP. If there is no ping, take appropriate actions to change the
network path status to normal.
b If the ping test fails, the network status must be checked first.
7 Collect the SW log and restart the PTPM.
a
Run the INIT-SW command to reset the input parameter PTPM.
b Check whether the StartUpLockingFail alarm is cleared within the lock

time.

Run the INIT-SYS command with the input RESET_MODE set to HW.

303
On-site Actions
Conduct the visual

inspection of B/H state
Abnormal
Replace the cable
Normal
Abnormal
Replace the site
Reconfigure the site
Normal
Normal
Monitoring
Monitoring
Not restored
Check if the backhaul cable of the SmallCell is in the fine state.
2 If the connection state of the backhaul cable is not fine, remount the backhaul
cable after disconnecting it.
3 If the alarm is cleared, continue to monitor and if the alarm is maintained,

replace the backhaul cable.
4 If the backhaul cable is connected normally, however, the alarm remains,

Replacement Manual.

304
A2184320R PTPM NO PTP SIGNAL

This alarm occurs when the SPLL state in the IEEE1588 clock device is abnormal.
Basic Information
Severity
Relates to
Category
Location
MINOR
Hardware
EQUIPMENT
Possible Cause
The SPLL state in the IEEE1588 clock device is abnormal.
Impact
Remedy


305
Alarm Raised
Step 1
StartUpLockingFail
Alarm Raised?
Yes
Action To Clear
StartUp LockingFail Alarm
No
Action To Clear
Yes
Action To Clear
No Current PTP Master Alarm
No

(CHG-PTPM-CONF)
No
Change GM IP
(CHG-GM-IP)
No
Select IPAddrConf IEEE1588

Attr (CHG-IP-ADDR)
No
Step 2
PTPM Device State

Normal?
Yes
Step 3

Alarm Raised?
No
Step 4
PTP Domain Number

Available?
Step 5
GM IP Available?
Yes
Step 6
PTP interface IP Available?

Yes
No PTP Signal Alarm
Cleared Within
Lock Time?
Yes
No
Step 7
GM & PTP Interface

No
Yes
Yes
Step 8
Collect SW Log
End
Check whether the StartUpLocking Fail alarm has been raised.
Check whether the StartUpLocking Fail alarm has been raised.
b Carry out the remedy for the PTPM STARTUP LOCKING FAIL alarm.
c
If the StartUpLocking Fail alarm has not been raised, continue with the
Step 2.

306
2 Check whether the PTPM device state is normal.

a
Run the RTRV-PTPM-STS command to check the communication status

with the PTPM.

c
If the state is not displayed as running, carry out the ClockDev NotInit
alarm remedy.
3 Check whether the No Current PTP Master alarm has been raised.
If the No Current PTP master alarm has been raised, follow the remedy of this
alarm.

a


a


whether the MASTER_IP_1 or the MASTER_IP_2 is the grand master IP.



the current Grand master IP address is available.

a

configuration.

the BH interface.
d Check whether the Holdover Exceed alarm is cleared within the lock time.
7 Run a ping test to check the grand master network status.
a
After connecting to the Enb, run the ping test from the Enb to the grand
master IP. If there is no ping, take appropriate actions to change the
network path status to normal.
307
On-site Actions
To identify and correct the problem:
Conduct the visual

inspection of B/H state
Abnormal
Replace the cable
Normal
Abnormal
Replace the site
Reconfigure the site
Normal
Normal
Monitoring
Monitoring
Not restored
Check if the backhaul cable of the SmallCell is in the fine state.
2 If the connection state of the backhaul cable is not fine, remount the backhaul
cable after disconnecting it.
3 If the alarm is cleared, continue to monitor, and if the alarm is maintained,

replace the backhaul cable.
4 If the backhaul cable is connected normally, however, the alarm remains,

Replacement Manual.

308
A2184321R PTPM CLOCK DEV NOT INIT

This alarm occurs when the initial state in the IEEE1588 clock device is abnormal.
Basic Information
Severity
Relates to
Category
Location
CRITICAL
Hardware
EQUIPMENT
Possible Cause
The initial state in the IEEE1588 clock device is abnormal.
Impact
Remedy


309
Alarm Raised
Step 1
System Clock
IEEE 1588 Selected?
No
Yes
Step 2
PTPM Device State

Normal?
Step 3
GM IP Available?
Yes
No
No
Collect SW Log
GM IP Change
(CHG-GM-IP)
ClockDevNot Init Cleared?
Yes
Step 4
Yes
No
PTP interface IP Available?
No

Attr (CHG-IP-ADDR)
ClockDevNot Init Cleared?
Yes
Yes
No
Collect SW Log
Step 5
System Restart
On Site Action
End
Check whether System Clock IEEE 1588 has been selected.

Check whether IEEE 1588 has been configured for the RTRV-CLOCKSRCDATA output Clock Source.

a

c
If the state is set to running, collect the SW log.
d If the state is not set to running, continue with the Step 3.

e
Carry out the remedy for the ClockDev NotInit alarm.
If the ClockDevNotInit alarm has not been raised, continue with the Step 2.
3 Check the IEEE 1588 grand master server IP configuration.

a


310


command to change the grand master IP address.


the current grand master IP address is available.

a

configuration.

the BH interface.
5 Collect SW log and run the INIT-SYS command to restart the System.
On-site Actions
Turn on or off the SmallCell power.
2 If the defective state is not restored, replace the SmallCell.

Replacement Manual.

311
A2184430R PTPM STARTUP LOCKING FAIL

This alarm is generated in unlocking 1588 system initialization.
Basic Information
Severity
Relates to
Category
Location
CRITICAL
Hardware
EQUIPMENT
Possible Cause
This alarm is generated in unlocking 1588 system initialization.
Impact
Remedy

312
Alarm Raised
Restart Executed?
Step 1
ClockDevNotInit
Alarm Raised?
Yes
Action To Clear
Yes
Action To Clear Clock Dev Not

Init Alarm Or No Current PTP
Master Action
No

(CHG-PTPM-CONF)
No
Change GM IP
(CHG-GM-IP)
No

Attr (CHG-IP-ADDR)
No
Step 2
PTPM Device State

Abnormal? Or No Current
PTP Alarm Raised?
No
Step 3
PTP Domain Number

Available?
Step 4
GM IP Available?
Yes
Step 5
PTP Interface IP Available?
Step 6
StartUpLocking Fail
Alarm Cleared
Within Lock Time?
Yes
No
Step 7
GM & PTP Interface

No
Yes
Step 8
Collect SW Log
Step 9
PTPM Restart
StartUpLocking Fail
Alarm Cleared
Within Lock Time?
Yes
No
On Site Action
End
During the SW restart, it is inevitably possible for the PTPM Startup Locking Fail
alarm to be raised. Therefore, when running the INIT-SW command, carry out
313
corrective actions after the lock time.
Check whether the ClockDevNotInit alarm has been raised.
Check whether the ClockDevNotInit alarm has been raised.
b Carry out the remedy for the ClockDevNotInit alarm.

c
If the ClockDevNotInit alarm has not been raised, continue with the Step 2.

a

c
remedy.
3 Check whether the No Current PTP Master alarm has been raised. If yes,
follow the remedy of this alarm.

a

5 Check the IEEE 1588 grand master server IP configuration.

a


whether the MASTER_IP_1 or the MASTER_IP_2 is the grand master IP.




a

configuration.

the BH interface.
d Check whether the Startup Locking Fail alarm is cleared within the lock
time.
314
7 Run a ping test to check the Grand master network status.

a
After connecting to the eNB, run the ping test from the eNB to the Grand
Master IP. If there is no ping, take appropriate actions to change the
Network Path status to normal.
8 Collect the SW log and reset the PTPM.
a
b Check whether the Startup Locking Fail alarm is cleared within the lock
time.
9 Run the INIT-SYS command to restart the System.

Run the INIT-SYS command with the input RESET_MODE set to HW.Because
the IEE 1588 network status and quality measurements differ per equipment and
operator requirement, the network quality measurement is to be carried out after a
discussion.
The IEEE 1588 PTPM Lock Time is to comply with operator requirement.

315
A2184438R PTPM HOLDOVER EXCEED

This alarm occurs when the threshold time exceeds after transition to a holdover
state.
Basic Information
Severity
Relates to
Category
Location
CRITICAL
Hardware
EQUIPMENT
Possible Cause
The threshold time is exceeded after transition to a holdover state.
Impact
Remedy

316
Alarm Raised
Step 1
StartUpLockingFail
Alarm Raised?
Yes
Action To Clear
StartUp LockingFail Alarm
No
Action To Clear
No
Step 2
PTPM Device State

Normal?
Step 3
PTPM Device State

Normal?
No Current PTP Master Alarm

action
Yes
Step 4
PTP Domain Number

Available Check?
Step 5
GM IP Available ?
No

(CHG-PTPM-CONF)
No
Change GM IP
(CHG-GM-IP)
No

Attr (CHG-IP-ADDR)
Yes
Step 6
PTP Interface IP Available?
HOLDOVER EXCEED
Alarm Cleared
Within Lock Time?
Yes
No
Step 7
GM & PTP Interface

No
Yes
Step 8
Collect SW Log
PTPM Restart
HOLDOVER EXCEED
Alarm Cleared
Within Lock Time?
Yes
No
Step 9
On Site Action
End
Check whether the Startup Locking Fail alarm has been raised.
Check whether the Startup Locking Fail alarm has been raised.

317
b Carry out the remedy for the Startup Locking Fail alarm.
c
If the Startup Locking Fail alarm has not been raised, continue with the
Step 2.

a
Run the RTRV-PTPM-STS command to check the communication status

with the PTPM.
b Check whether the PTPM status displays as running.

c
remedy.
3 Check whether the No Current PTP Master alarm has been raised.
If the No Current PTP master alarm has been raised, follow the remedy of this
alarm.

a


a



command to change the grand master IP address.



a

configuration.

the BH interface.
d Check whether the Holdover Exceed alarm is cleared within the lock time.
7 Run a ping test to check the grand master network status.
a
After connecting to the eNB, run the ping test from the eNB to the grand

318
Master IP. If there is no ping, take appropriate actions to change the

Network Path status to normal.
8 Collect the SW log and restart the PTPM.
a
b Check whether the Holdover Exceed alarm is cleared within the lock time.
Because the IEE 1588 network status and quality measurements differ per
equipment and operator requirement, the network quality measurement is to be
carried out after a discussion.
The IEEE 1588 PTPM Lock Time is to comply with operator requirement.

319
A2199216R SYS TEMPERATURE HIGH

This alarm occurs when the temperature of the unit is higher than the high
threshold (outdoor only).
Basic Information
Severity
Relates to
Category
Location
MAJOR
Hardware
ENVIRONMENT
None
Possible Cause
The temperature of the unit is higher than the high threshold.
Impact
Service will be unavailable.
Remedy


320
Alarm Raised
No
Step 1
Alarm Threshold
Abnormal &&
Env Temp >= Alarm
Threshold
Yes
Change Threshold
SYS TEMPERATURE
HIGH Alarm Raised?
Step 2
No
Yes
Collect SW Log
System Restart
SYS TEMPERATURE
HIGH Alarm Raised?
Step 3
No
Yes
On Site Action
End
Check the temperature threshold and if there is a problem, take appropriate

action.
Run the RTRV-ENV-TEMP command.
b Run the RTRV-ENVTEMP-THR command.

c
If the environment temperature threshold is abnormal, check the

recommended threshold level and change the threshold to this value.
2 If the alarm is not cleared, collect the SW log and restart the system.
a
b Run the RTRV-ALM-LIST command and check whether an alarm exists

with values of SYS and TEMPERATURE HIGH for outputs UNIT_TYPE
and ALARM_TYPE.
3 If the alarm remains, share the SW log with Samsung for the next level of

321
On-site Actions
SYS Temperature High Alarm

Occurs
Step 1
Check LED Color
LED Green Y/N
Yes
No
Step 2
Conduct Visual Check for

Foreign Substances near Unit
Foreign Substances/
Hampering Elements Y/N
No
Yes
Step 3
Yes
Eliminate Foreign Substances/

Elements
Alarm Cleared Y/N

No
Step 4
No
Replace L7MU
Alarm Cleared Y/N

Yes
At the site, check if the alarm is still active in the LSM. Then, check the LED
color.
If the alarm is activated and the LED color is green, continue with the Step
4.
b If the LED is not green, continue with the Step 2.

322
2 Check if there are any foreign substances hampering heat radiation near the
Microcell unit.
If foreign substances or hampering elements are found, continue with the

Step 3.
b If the alarm continues to be activated without the substances hampering

heat radiation, continue with the Step 4.
3 Eliminate all of the foreign substances and hampering elements near the
Microcell unit.
o
alarm state.
4 Replace the Microcell.

After recording action history, continue to monitor the alarm state.

323
A2199365R SYS NTP UPDATE ERROR

This alarm occurs when the system time cannot be updated either due to an
incorrect server configuration or lack of connectivity with the NTP server.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Software
EQUIPMENT
None
Possible Cause
The system time cannot be updated due to an incorrect server configuration or to a
lack of connectivity with the NTP server.
Impact
Remedy

324
Alarm Raised
Yes
Separate Time Server?
No
Check NTP Info
Step 1
Setting Normal?
Yes
No
Reconfigure
NTP Server Info
Step 2
Alarm Cleared?
No
Yes
NTP Util Test
EMS NTP Server Restart and

Check System SW Util
NTP Util test Success?
No
Yes
Restart SWM/FM Block
Yes
Alarm Cleared?
Step 3
No
Collect SW Log, Request

Analysis
End
Step 4
If a NTP Sync server exists, check whether the information setting is correct.
If the information is not set or set with different information, reconfigure the
info to the NTP server.
If the NTP Sync server exists, run the RTRV-NTP-CONF to check the

325
server address.
b If the NTP Sync server IP address and the command results are different,
run the CHG-NTP-CONF command to reconfigure the address.
Check in a few minutes to see if the alarm has been cleared.
2 If the alarm has not been cleared, login to the NE and carry out a NTP Util test
to check if NTP communication is occurring with the EMS. If the util is not
properly executing, check whether the ntpdate util for the EMS (or the clock
sync server) NTP server and System SW is working correctly.
Use the ntpdate util to check if ntp clock sync is possible.
o
ntpdate2 -<ipversion> -i <bindIp> <serverIp> In Case of Failure
ntpdate -<ipversion> <serverIp>
Ex> ntpdate2 -4 -i 10.1.1.11 10.1.1.10
If the ntpdate command execution fails, check whether the ntpdate util for the
EMS (or the clock sync server) NTP server and NE is working correctly. Then
repeat the Step 2.
3 If ntpdate executed successfully but the alarm was not cleared, check the alarm
status again after restarting the SWM and FM block.
Restart the block by running INIT-SW: SWM and INIT-SW: FM.
b Check whether the alarm remains after clearance.

consulting the next level of maintenance support.

326
A2199460R SYS SERVICE OFF

This alarm occurs when all the cells for the eNB are disabled.
Basic Information
Severity
Relates to
Category
Location
CRITICAL
Software
EQUIPMENT
None
Possible Cause
All cells for the eNB are disabled.
Impact
Remedy

327
Alarm Raised
Collect SW Log
Step 1
System Locked?
Yes
System Unlock
No
Yes
Step 2
All Cell Locked?
SYS SERVICE OFF

Alarm Raised ?
Yes
No
Cell Unlock
No
Yes
Alarm Raised?
Step 3
SYS SERVICE OFF

Alarm Raised ?
No
Check Remedy and Actions To

Take for Each Alarm
Yes
No
Yes
SYS SERVICE OFF

Alarm Raised ?
No
Step 4
Request Analysis
End
Check whether the system admin state is set to locked, and take appropriate
actions if so.
Run the RTRV-SYS-CONF command.
b Check whether the value of output ADMINISTRATIVE_STATE is locked.

If yes, do the following steps:
i
Change the value of ADMINISTRATIVE_STATE to unlocked by

running the CHG-SYS-CONF command.
ii
Check whether the SERVICE_OFF alarm has been raised by running

the RTRV-ALM-LIST command.
2 Check whether the admin state of all cells is set to locked and take appropriate
actions if so.
328
Run the RTRV-CELL-CONF command.
b Check whether the value of output ADMINISTRATIVE_STATE for all

cells is locked. If yes, do the following steps:
i
Change the value of ADMINISTRATIVE_STATE to unlocked by

running the CHG-CELL-CONF command.
ii
Check whether the SERVICE_OFF alarm has been raised by running

the RTRV-ALM-LIST command.
3 If the alarm is not cleared, check which alarms are still raised and take
b If an alarm is being raised, follow the remedy.

Check if an alarm is generated in the ECP, DSP, or RF units.
If an alarm is generated in the ECP, take corrective measures specific
to the ECP.
If an alarm is generated in the clock module (PTPM or GPSR), take a
corrective measures specific to the clock module (PTPM or GPSR).
If an alarm is generated in the DSP, take corrective measures specific
to the DSP.
If an alarm is generated in the RF unit, take corrective measures
specific to the RF unit.
If the alarm remains, collect the SW log and share with Samsung for consulting the
next level of maintenance support.

329
A2199600R SYS MME COMMUNICATION FAIL

This alarm occurs when there is a communication problem between the eNB and
MME.
Basic Information
Severity
Relates to
Category
Location
CRITICAL
Software
EQUIPMENT
None
Possible Cause
The eNB does not receive a response for the SCTP heartbeat from all the
equipped MMEs.
The S1AP connection setup between the eNBand all the equipped MMEs has
not been completed.
Impact
The LTE services will be unavailable.
Remedy


330
Alarm Raised
Step 2
Step 1
Check S1 Status
Yes
SCTP_STATE ==
disabled
No
CHECK S1 STATUS
Check
SYSTEM SIG IP
Step 3
No
S1 IP is exist ?
ADD S1 IP
Alarm Cleared?
No
Yes
Step 4
Yes
Check MME IP Info
Step 5
No
IP is correct ?
Change IP
Alarm Cleared?
Yes
Step 6
Yes
No
Check PING STATUS
Step 7
No
PING OK ?
Check
Comm Status
Alarm Cleared?
Yes
Step 8
Yes
No
Collect SW Log
Request Analysis
End

S1AP_STATE.
Run the RTRV-S1-STS command.
b Check the SCTP_STATE and S1AP_STATE.

331
Run the RTRV-SYS-SIGIP command.
b Check whether S1_PRI_IPV4_ADDR or S1_SEC_IPV4_ADDR exists.


a

added.

a
Run the RTRV-MME-CONF command.
b Check whether the correct MME IP information is being displayed.

a


a

a
b Check the routing table regarding the MME/MCE IP.

On-site Actions
support.

332
A2199602R SYS SLEEPING CELL DETECTION

This alarm occurs when there is a sleeping cell.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Software
PROCESSING
CELL[a]
Possible Cause
The diagnosis call function is activated (diag_Call_Enable is set to ON).
The value of diagCallEnable can be retrieved by running the RTRV-DIAG-CONF

command.
There is no RRC connection during triggering_Condition_Timer while no call

is connected to the cell.
The value of triggering_Condition_Timer can be retrieved by running the RTRVDIAG-CONF command.
There is no response to the paging call transmitted by the eNB to the idle UE
after triggering_Condition_Timer of PLD DIAG_CALL_CONF.
Impact
Defaults
The default value of TRIGGERING_CONDITION_TIMER is 1 hour.
Remedy


333
SLEEPING CELL Alarm

Raised
RECOVERY_MODE_SE
LECTION == AUTO?
Step 1
No
Manual RESET Carried Out

by Operator
Yes
autoRecoveryMethod
value?
Step 2
DSP_RESET_
ONLY
CELL_RELEASE
Step 3
Alarm Cleared?
Step 4
No
Yes
Collect SW Log
End
Replace Board
Run the RTRV-DIAG-CONF command to check the

RECOVERY_MODE_SELECTION value.
Check whether the RECOVERY_MODE_SELECTION value is set to AUTO

or MANUAL.
2 If the RECOVERY_MODE_SELECTION value is set to AUTO, check the

AUTO_RECOVERY_METHOD value.
If RECOVERY_MODE_SELECTION is set to AUTO, check which value-out
of CELL_RELEASE and DSP_RESET_ONLY-the
AUTO_RECOVERY_METHOD is set to.
3 Check whether the alarm clears depending on the value for AUTO_
334
RECOVERY_METHOD.
o
If AUTO_RECOVERY_METHOD is set to CELL_RELEASE, check

whether the alarm clears after CELL RELEASE is completed.
If AUTO_RECOVERY_METHOD is set to DSP_RESET_ONLY, check

whether the alarm clears after DSP RESET is completed.
4 If RECOVERY_MODE_SELECTION is set to MANUAL, take the

Run the INIT-DSP command. Set the DSP ID that has raised the alarm,
and then run this command..
b Check whether the alarm is cleared.

c
d Check whether the alarm is cleared after the system restart.

5 If the alarm remains, collect the SW log, and replace the faulty board.
On-site Actions
Replace the board.
support.

335
A2199605R SYS IND MME COMMUNICATION

FAIL
This alarm occurs when the S1 interface is in an abnormal state or the eNB cannot
receive the SCTP heartbeat response from the MME.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Software
EQUIPMENT
MME[e]
Possible Cause
The S1 interface is in an abnormal state or the eNB cannot receive the SCTP
heartbeat response from the MME.
Impact
Remedy


336
Alarm Raised
Step 2
Step 1
Check S1 Status
Yes
SCTP_STATE ==
disabled
No
CHECK S1 STATUS
Check
SYSTEM SIG IP
Step 3
No
S1 IP Exists?
ADD S1 IP
Yes
No
Yes
Step 4
Alarm Cleared?
Check MME IP Info
Step 5
No
Correct IP?
Change IP
Yes
Step 6
Alarm Cleared?
Yes
No
Check PING STATUS
Step 7
No
PING OK?
Check
Comm Status
Yes
Step 8
Alarm Cleared?
Yes
No
Collect SW Log
Request Analysis
End

S1AP_STATE.

337


a

added.

a
Run the RTRV-MME-CONF command.
b Check whether the correct MME IP information is being displayed.

a


a

a

On-site Actions
2 If the alarm still persists, consult with Samsung for the next level of

338
A2199629R SYS MCE COMMUNICATION FAIL

This alarm occurs when the eNB cannot receive the SCTP heartbeat response from
the MCE.
Basic Information
Severity
Relates to
Category
Location
MAJOR
Software
EQUIPMENT
None
Possible Cause
The eNB cannot receive the SCTP heartbeat response from the MCE.
Impact
Remedy


339
Alarm Raised
Step 2
Step 1
Check M2 Status
Yes
SCTP_STATE ==
SCTP_OUT_OF_
SERVICE
No
CHECK M2 STATUS
Check
SYSTEM SIG IP
Step 3
No
S1 IP Exists?
ADD S1 IP
Yes
No
Yes
Step 4
Alarm Cleared?
Check MCE IP Info
Step 5
No
Correct IP?
Change IP
Yes
Step 6
Alarm Cleared?
Yes
No
Check PING STATUS
Step 7
No
PING OK?
Check
Comm Status
Yes
Step 8
Alarm Cleared?
Yes
No
Collect SW Log
Request Analysis
End
Run the RTRV-M2-STS command to check the SCTP_STATE and

M2_AP_STATE.
Check the SCTP_STATE and M2_AP_STATE.
2 If SCTP_STATE is set to SCTP_OUT_OF_SERVICE, run the RTRV-SYSSIGIP command and check whether SIG IP exists.
340


a
Run the CHG-IP-ADDR command to change LTE_SIGNAL_S1 to True.

added.
4 Run the RTRV-MBMS-MCECONF command and check the MCE IP

information.
Check whether the correct MCE IP information is being displayed.
5 If the MCE IP information is incorrect, change the IP information.

a
Run the CHG-MBMS-MCECONF command to change the IP information.
b Run the RTRV-MBMS-MCECONF command to check whether the

information has been updated correctly.
6 Check the ping status between the eNB-MCE.

a
Run ping -I [eNB IP] [MCE IP].

a

On-site Actions
support.

341
Appendix Acronyms
CMC
CPU
CLI
EMS
FM
GUI
IMM
LTE
LSM
MMP
NE
NMS
NTP
QoS
SCTP
SWM
Chassis Management Controller

Central Processing Unit
Command Line Interface
Element management system
Fault Management
Graphic User Interface
Integrated Management Module
Long Term Evolution
LTE System Manager
MCE Main Processor
Network Element
Network Management System
Network Time Protocol
Quality of Service
Stream Control Transmission Protocol
Software Management

342
Samsung LTE eNB

Alarm Manual for PKG 5.0.0
Document Version 1.0
2015 Samsung Electronics Co., Ltd.
All rights reserved.

Samsung LTE ENB Alarm Manual For PKG 5.0.0 - v1.0

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Samsung LTE ENB Alarm Manual For PKG 5.0.0 - v1.0

Încărcat de

Drepturi de autor:

Formate disponibile

Samsung LTE eNB

Radio Access Network

Document Version 1.0

Document Number: 2600-00I33NGAB

2015 SAMSUNG Electronics Co., Ltd.

Samsung LTE eNB Alarm Manual for PKG 5.0.0 v1.0

A2149338R RET MOTOR JAM....................................................................................................... 104

Microcell Alarm Reference

Samsung LTE eNB Alarm Manual for PKG 5.0.0 v1.0

A2180360R GPSR TOD MSG MISSED ............................................................................................ 281

Samsung LTE eNB Alarm Manual for PKG 5.0.0 v1.0

eNB Unit Types ................................................................................................................................. 2

Samsung LTE eNB Alarm Manual for PKG 5.0.0 v1.0

Conventions in this Document

File Names and Paths

User Input and Console Screen Output Text

Samsung LTE eNB Alarm Manual for PKG 5.0.0 v1.0

Personal and Product Safety

Rack-mountable equipment must be placed in a standard 19-inch rack and secured

Service personnel must wear anti-static wrist straps.

Circuit boards and sub-assemblies must be placed on ground conductive mats

All tools must be discharged to ground before use.

Samsung LTE eNB Alarm Manual for PKG 5.0.0 v1.0

Power Supply Connection

Samsung LTE eNB Alarm Manual for PKG 5.0.0 v1.0

Samsung LTE eNB Alarm Manual for PKG 5.0.0 v1.0

Correct disposal of batteries in this product

This product is RoHS compliant.

Samsung LTE eNB Alarm Manual for PKG 5.0.0 v1.0

There are two types of output message:

Alarm Cleared: Green

Chapter 1 Introducing Alarms

xxyyzzz (7-digit number): Allocated to each alarm uniquely.

zzz: Alarm type. For alarm type values, see Table 3.

R: Abbreviation of RAN (eNB)

Universal Main Processor

ENB Channel Processor

Remote Radio Head

Table 2. Microcell Unit Types

Samsung LTE eNB Alarm Manual for PKG 5.0.0 v1.0

Chapter 1 Introducing Alarms

Universal Main Processor

Remote Radio Head

Universal Clock Receiver

IEEE1588 Clock Device

SyncE Clock Device

A communication failure between equipment.

An adverse effect on device performance or quality of service.

Software or processing failure.

A device or equipment failure.

An environmental condition (such as excessive temperature or

Indicates errors that do not have an immediate impact on the

Indicates errors pertaining to abnormalities in hardware or

Indicates errors that seriously hinder normal system operation

Samsung LTE eNB Alarm Manual for PKG 5.0.0 v1.0

Chapter 1 Introducing Alarms

Auto Alarm Suppression

Alarm monitoring using the LSM Event Viewer.

Alarm monitoring by executing commands on the CLI window of the LSM.

Alarm Monitoring by LED.

Samsung LTE eNB Alarm Manual for PKG 5.0.0 v1.0

Chapter 1 Introducing Alarms

Dealing with an Alarm