Académique Documents
Professionnel Documents
Culture Documents
Alarm Manual
for SLR 3.1
Provides a detailed reference and resolution guide for alarms that can be raised on
the Samsung MBS(LTE). This includes the CDU, SDU and radio units.
SNMTC-v2-0214
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
viii
Relevance .......................................................................................................................................viii
Conventions in this Document .......................................................................................................viii
New and Changed Information ....................................................................................................... ix
Revision History ............................................................................................................................... ix
Organization of This Document ....................................................................................................... x
Related Documentation .................................................................................................................. xi
Chapter 1
Introducing Alarms
1
Overview .......................................................................................................................................... 1
Alarm Codes ..................................................................................................................................... 2
Unit Types ........................................................................................................................................ 3
Alarm Categories .............................................................................................................................. 3
Alarm Severities ............................................................................................................................... 3
Auto Alarm Suppression ................................................................................................................... 4
Inhibiting Alarms .............................................................................................................................. 4
Monitoring Alarms ........................................................................................................................... 5
Dealing with an Alarm ...................................................................................................................... 5
Chapter 2
iii
Contents
iv
Contents
Contents
vi
List of Tables
Table 1.
Table 2.
Table 3.
vii
Preface
This manual is a detailed reference and resolution guide for all alarms that can be
raised by the Samsung MBS(LTE). It covers alarms raised by the Samsung SDU10,
CD10, and by the radio units.
Each alarm is identified by a unique alarm code that starts with the letter A and is
followed by a seven-digit number and ends with the letter R, as seen in the LTE
System Manager (LSM) view window. To resolve a particular alarm, look it up in
this manual and follow the recommended resolution procedure.
Relevance
This manual applies to the following products/software.
Name
Type
SLR 3.1
Software
LSM 3.1
Software
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.
Samsung MBS(LTE) Alarm Manual for SLR 3.1 v2.0
Samsung Proprietary and Confidential
viii
Preface
Revision History
The following table lists all versions of this document.
Document Number
Product/Software
Version
Document Version
Publication Date
2600-00G1LYGAB
SLR 2.4
1.0
31 Oct 2014
2600-00GAEAGAB
SLR 3.1
1.0
14 Feb 2014
2600-00GAEAGAB
SLR 3.1
2.0
29 Oct 2014
ix
Preface
Title
Description
Chapter 1
Introducing Alarms
Chapter 2
Chapter 3
Appendix
Acronyms
Preface
Related Documentation
Samsung MBS(LTE) Hardware Addition and Replacement Manual for SLR 3.1
xi
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
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
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,
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
xx: NE type. The NE type value for the Samsung MBS is 21.
Unit Types
The following table shows types of units that can raise alarms:
Table 1. Unit Types
Code
Unit Type
Description
00
03
16
49
84
PTPM
92
SYNCE
99
SYS
eNB
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 2. Alarm Categories
Category
Meaning
COMMUNICATIONS (COM)
QOS
PROCESSING (PROC)
EQUIPMENT (EQUIP)
ENVIRONMENT (ENV)
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.
Meaning
MINOR
MAJOR
CRITICAL
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.
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.
Monitoring Alarms
You can monitor the alarm by the following methods:
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.
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).
Chapter 2
CDU Alarm
Reference
Name
Severity
Relates to
Category
A2100102R
Major
Software
PROC
A2100217R
Major
Hardware
ENV
A2100300R
All
Software
QOS
A2100301R
All
Software
QOS
A2100302R
UMP OVERLOAD
All
Software
QOS
A2100351R
Major
Hardware
EQUIP
A2100370R
Major
Hardware
EQUIP
A2100380R
Major
Hardware
EQUIP
A2103100R
Critical
Software
PROC
A2103102R
Major
Software
PROC
A2103217R
Major
Hardware
ENV
A2103300R
All
Software
QOS
A2103301R
All
Software
QOS
A2103302R
IMP OVERLOAD
All
Software
QOS
A2103351R
Major
Hardware
EQUIP
A2103370R
Major
Hardware
EQUIP
A2103372R
Critical
Software
EQUIP
A2103376R
Major
Hardware
EQUIP
A2103378R
Major
Hardware
EQUIP
A2103379R
Major
Hardware
EQUIP
A2103380R
Major
Hardware
EQUIP
A2103607R
Critical
Hardware
EQUIP
A2103627R
IMP SOCFAIL
Critical
Software
EQUIP
A2103628R
Critical
Software
PROC
A2116100R
Critical
Software
PROC
A2116102R
Major
Software
PROC
A2116300R
All
Software
QOS
A2116301R
All
Software
QOS
A2116302R
ECP OVERLOAD
All
Software
QOS
A2116351R
Major
Hardware
EQUIP
A2116366R
ECP BOARD_DELETION
Critical
Hardware
EQUIP
A2116367R
Major
Hardware
EQUIP
A2116368R
Major
Hardware
EQUIP
A2116372R
Critical
Software
EQUIP
Name
Severity
Relates to
Category
A2116376R
Major
Hardware
EQUIP
A2116378R
Major
Hardware
EQUIP
A2116379R
Major
Hardware
EQUIP
A2116381R
Major
Software
EQUIP
A2116607R
Major
Hardware
EQUIP
A2149210R
Minor
Hardware
ENV
A2149216R
Major
Hardware
ENV
A2149351R
Major
Hardware
EQUIP
A2149368R
Major
Hardware
EQUIP
A2149381R
Critical
Software
EQUIP
A2149384R
Major
Hardware
EQUIP
A2149385R
RRH DISABLED
Major
Hardware
EQUIP
A2149388R
Minor
Hardware
EQUIP
A2149389R
Major
Hardware
EQUIP
A2149391R
Major
Hardware
EQUIP
A2149392R
Major
Hardware
EQUIP
A2149395R
Minor
Hardware
EQUIP
A2149408R
Minor
Hardware
EQUIP
A2149609R
Minor
Hardware
EQUIP
A2149610R
Minor
Hardware
EQUIP
A2149649R
Major
Hardware
EQUIP
A2180001R
UCR TOD_MSG_MISSED
Major
Software
COM
A2180350R
UCR ANTENNA_FAIL
Major
Hardware
EQUIP
A2180361R
Major
Hardware
EQUIP
A2180368R
UCR FUNCTION_FAIL
Critical
Hardware
EQUIP
A2180424R
Major
Hardware
EQUIP
A2184001R
Major
Software
COM
A2184003R
Major
Hardware
COM
A2184320R
Minor
Hardware
EQUIP
A2184321R
Critical
Hardware
EQUIP
A2184424R
Critical
Hardware
EQUIP
A2184430R
Critical
Hardware
EQUIP
A2192025R
Major
Hardware
COM
A2192321R
Critical
Hardware
EQUIP
A2192423R
Major
Hardware
EQUIP
A2192424R
Critical
Hardware
EQUIP
A2192428R
Critical
Hardware
EQUIP
A2192430R
Critical
Hardware
EQUIP
A2199202R
SYS UDA
All
Hardware
EQUIP
A2199209R
Major
Hardware
ENV
A2199365R
Major
Software
EQUIP
A2199460R
Critical
Software
EQUIP
Name
Severity
Relates to
Category
A2199600R
Critical
Software
EQUIP
A2199602R
Major
Software
PROC
A2199605R
Major
Software
EQUIP
Basic Information
Severity MAJOR
Relates to Software
Category PROCESSING
Possible Cause(s)
This happens when a process is deactivated. You can find the cause by analyzing
the core file and log file uploaded to the LSM.
Impact
If an alarm is generated continuously in a specific software block, service may not
be available.
Remedy
Whenever a process becomes deactivated, the process will be restarted
automatically within 3 seconds.
To identify whether you need to take action and to correct the problem:
Monitor the alarm status to see if the process restarts 10 times within 3
minutes.
If the process restarts more than 10 times during 3 minutes, run the INIT-SW
command to manually initiate the process restart.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
Basic Information
Severity MAJOR
Relates to Hardware
Category ENVIRONMENT
Possible Cause(s)
The CPU temperature exceeds the threshold.
Impact
There may be damage to the board.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Check if the alarm is cleared. If the alarm is cleared, record the current status
and observe any reoccurrence.
If the alarm is not cleared, inspect the UMP at the installation site, and perform
on-site actions.
10
On-site Actions
To identify and correct the problem:
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.
If the PWR/ALM LED is green, check that the fan is rotating normally.
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.
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. The
CPU location is shown in the following figure.
C
P
U
Mount the UMP and check if an alarm (is generated after loading completes.
0
If the alarm is not cleared, replace the UMP.
For information about UMP replacement, see the Samsung MBS(LTE) Hardware
Addition and Replacement Manual for SLR 3.1.
11
Basic Information
Severity CRITICAL/MAJOR/MINOR
Relates to Software
Category QOS
Possible Cause(s)
The disk usage exceeds the threshold.
The threshold value can be retrieved using the RTRV-ALM-THR COMMAND.
Impact
Some software blocks may operate abnormally.
Defaults
Minor: 85 %, Major: 90 %, Critical: 95 %
Remedy
To identify and correct the problem:
If the alarm is not cleared even after UMP is reset, replace the UMP.
For information about UMP replacement, see the Samsung MBS(LTE) Hardware
Addition and Replacement Manual for SLR 3.1.
12
Basic Information
Severity CRITICAL/MAJOR/MINOR
Relates to Software
Category QOS
Possible Cause(s)
The memory usage exceeds the threshold.
The threshold value can be retrieved using the RTRV-ALM-THR COMMAND.
Impact
Some software blocks may operate abnormally.
Defaults
Minor: 95 %, Major: 96 %, Critical: 97 %
Remedy
To identify and correct the problem:
If there is no software application with a high memory usage, reset the UMP.
If the alarm is not cleared even after the UMP is reset, replace the UMP.
For information about board replacement, see the Samsung MBS(LTE) Hardware
Addition and Replacement Manual for SLR 3.1.
13
Basic Information
Severity CRITICAL/MAJOR/MINOR
Relates to Software
Category QOS
Possible Cause(s)
The CPU usage exceeds the threshold.
The threshold value can be retrieved using RTRV-ALM-THR COMMAND.
Impact
Some software blocks to operate abnormally. If an alarm is generated continuously,
the UMP board may reset.
Defaults
Minor: 85 %, Major: 90 %, Critical: 95 %
Remedy
To identify and correct the problem:
If there is no software application with a high CPU usage, reset the UMP.
If the alarm is not cleared even after the UMP is reset, replace the UMP.
For information about UMP replacement, see the Samsung MBS(LTE) Hardware
Addition and Replacement Manual for SLR 3.1.
14
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The clock frequency (10 MHz, Even) of the clock module has a deviation beyond
normal parameters or there is no clock.
Impact
Service may not be available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
In the CLI window, run the INIT-PRC:UMP command to reset the UMP.
Check if an alarm is generated.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, inspect the UMP at the installation site and perform
on-site actions.
15
On-site Actions
To identify and correct the problem:33
Check if the external link cable that is used to provide the clock and that is
mounted on the UMP front side is correctly connected. If the cable is not
properly connected or there is a problem with the connector, disconnect and
reconnect the cable, or replace the cable.
If the clock device is IEEE1588, check the setting and communication status
of the UMP and IEEE1588 master. If the clock device is Sync-E, check the
setting and communication status of the UMP and Sync-E master.
Unmount and remount the UMP and check if an alarm is generated after
loading completes.
If the alarm is cleared, record the current status and observe any reoccurrence.
For the information about UMP replacement, see the Samsung MBS(LTE)
Hardware Addition and Replacement Manual for SLR 3.1.
16
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
Operation errors (data read/write) of the memory device occur.
Impact
Some software blocks may operate abnormally.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
In the CLI window, run the INIT-PRC:UMP command to reset the UMP and
then check if an alarm is generated.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, inspect the UMP at the installation site and perform
on-site actions.
17
On-site Actions
To identify and correct the problem:
Mount the UMP and check if an alarm is generated after loading completes.
If the alarm is cleared, record the current status and observe any reoccurrence.
DDR
(SOC1)
Unmount the UMP. Disassemble and reassemble the DDR memory module.
Check if there is any foreign material in the memory connector (socket). The
DDR location is shown below
DDR
(SOC2)
For information about UMP replacement, see the Samsung MBS(LTE) Hardware
Addition and Replacement Manual for SLR 3.1.
18
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
A link down failure (for example, due to a bad port connection) of the backhaul
port occurs.
Impact
The board cannot communicate with the LSM or external devices.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
In the CLI window, run the INIT-PRC:UMP command to reset the UMP and
then check if an alarm is generated.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, inspect the UMP at the installation site and perform
on-site actions.
19
On-site Actions
To identify and correct the problem:
Status
Description
Orange blinking (Left)
Green on (Right)
Off
Cable Open
Copper Port
Green
LED
Status
Description
Green On (Left)
Off
Orange
LED
Optical Port
Check that the Ethernet cable is correctly connected and that there is no
external damage.
Check that the optical cable is correctly connected and that there is no external
damage or bending.
Check that the connected optical cables (Single or Multi-Mode) are suitable
for the installed optical module type (Single or Multi-Mode).
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.
Check the status of the equipment connected to the backhaul port (for example,
router, switch).
If the equipment connected to the backhaul port is not working properly, reset
or replace the equipment.
Unmount the UMP. Disassemble and reassemble the DDR memory module.
Check if there is any foreign material in the memory connector (socket). The
DDR location is shown in the following figure.
20
DDR
(SOC1)
DDR
(SOC2)
10 Mount the UMP and check if an alarm is generated after loading completes.
11 If the alarm is cleared, record the current status and observe any reoccurrence.
12 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, etc.
For information about UMP replacement, see the Samsung MBS(LTE) Hardware
Addition and Replacement Manual for SLR 3.1.
21
Basic Information
Severity CRITICAL
Relates to Software
Category PROCESSING
Possible Cause(s)
The DSP resets and restarts (by using the DSP Reset command or replacing the
DSP image).
Impact
Cell services related to the IMP are not available during restart.
Remedy
To identify and correct the problem:
If the alarm is not cleared after taking the described actions, or if the alarm
occurs repeatedly, contact Samsung.
22
Basic Information
Severity MAJOR
Relates to Software
Category PROCESSING
Possible Cause(s)
This happens when a process is deactivated. You can find the cause by analyzing
the core file and log file uploaded to the LSM.
Impact
If an alarm generates continuously in a specific software block, service may be not
available.
Remedy
Whenever a process becomes deactivated, the process will be restarted
automatically within 3 seconds.
To identify whether you need to take action and to correct the problem:
Monitor the alarm status until the process restart occurs 10 times within 3
minutes.
If the process restart occurs more than 10 times during 3 minutes, run the
INIT-SW command to restart the process.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
23
Basic Information
Severity MAJOR
Relates to Hardware
Category ENVIRONMENT
Possible Cause(s)
The CPU temperature exceeds the threshold.
Impact
There may be damage to the board.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Check if the alarm is cleared. If the alarm is cleared, record the current status
and observe any reoccurrence.
If the alarm is not cleared, inspect the IMP at the installation site, and perform
on-site actions.
24
On-site Actions
To identify and correct the problem:
Check the status of the PWR/ALM LED on the fan module at the front of the
DU.
Green: Normal
If an air filter is mounted on the DU shelf, check that the air filter is in proper
working condition.
If air filter is not in proper working condition, replace the air filter.
If the fan module is not in proper working, replace the fan module.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about IMP replacement, see the Samsung MBS(LTE) Hardware
Addition and Replacement Manual for SLR 3.1.
25
Basic Information
Severity CRITICAL/MAJOR/MINOR
Relates to Software
Category QOS
Possible Cause(s)
The disk usage exceeds the threshold.
The threshold value can be retrieved using the RTRV-ALM-THR COMMAND.
Impact
Some software blocks may operate abnormally.
Defaults
Minor: 85 %, Major: 90 %, Critical: 95 %
Remedy
To identify and correct the problem:
If the alarm is not cleared even after the IMP is reset, replace the IMP.
For information about IMP replacement, see the Samsung MBS(LTE) Hardware
Addition and Replacement Manual for SLR 3.1.
26
Basic Information
Severity CRITICAL/MAJOR/MINOR
Relates to Software
Category QOS
Possible Cause(s)
The memory usage exceeds the threshold.
The threshold value can be retrieved using the RTRV-ALM-THR COMMAND.
Impact
Some software blocks may operate abnormally.
Defaults
Minor: 95 %, Major: 96 %, Critical: 97 %
Remedy
To identify and correct the problem:
If there is no software application with a high memory usage, reset the IMP.
If the alarm is not cleared even after the IMP is reset, replace the IMP.
For information about board replacement, see the Samsung MBS(LTE) Hardware
Addition and Replacement Manual for SLR 3.1.
27
Basic Information
Severity CRITICAL/MAJOR/MINOR
Relates to Software
Category QOS
Possible Cause(s)
The CPU usage exceeds the threshold.
The threshold value can be retrieved using RTRV-ALM-THR COMMAND.
Impact
Some software blocks to operate abnormally. If an alarm is generated continuously,
the UMP board may reset.
Defaults
Minor: 85 %, Major: 90 %, Critical: 95 %.
Remedy
To identify and correct the problem:
If there is no software application with a high CPU usage, reset the IMP.
If the alarm is not cleared even after the IMP is reset, replace the IMP
For information about IMP replacement, see the Samsung MBS(LTE) Hardware
Addition and Replacement Manual for SLR 3.1.
28
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The clock frequency (10 MHz, Even) of the clock module has a deviation beyond
normal parameters or there is no clock.
Impact
Service may not be available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
In the CLI window, run the INIT-PRC:IMP command to reset the IMP.
Check if an alarm is generated.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, inspect the IMP at the installation site and perform
on-site actions.
29
On-site Actions
To identify and correct the problem:
b Red: Alarms
CLOCK_DEV_NOT_INIT, STARTUP LOCKING FAIL
FREQUENCE_HOLDOVER_EXCEED, TOD_MSG_MISSED
(IEEE1588 only), CLOCK_DEV_FAIL (SYNCE only)
Check if the external link cable that is used to provide the clock and that is
mounted on the IMP front side is correctly connected. If the cable is not
properly connected or there is a problem with the connector, disconnect and
reconnect the cable, or replace the cable.
If the clock device is IEEE1588, check the setting and communication status
of the LUA and IEEE1588 master. If the clock device is Sync-E, check the
setting and communication status of the LUA and Sync-E master.
Unmount and remount the IMP and check if an alarm is generated after
loading completes.
If the alarm is cleared, record the current status and observe any reoccurrence.
For the information about IMP replacement, see the Samsung MBS(LTE)
Hardware Addition and Replacement Manual for SLR 3.1.
30
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
Operation errors (data read/write) of the memory device occur.
Impact
Some software blocks may operate abnormally.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
In the CLI window, run the INIT-PRC:IMP command to reset the IMP and
then check if an alarm is generated.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, inspect the IMP at the installation site and perform
on-site actions.
31
On-site Actions
To identify and correct the problem:
Unmount the IMP. Disassemble and reassemble the DDR memory module.
Check if there is any foreign material in the memory connector (socket).
Mount the IMP and check if an alarm is generated after loading completes.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about IMP replacement, see the Samsung MBS(LTE) Hardware
Addition and Replacement Manual for SLR 3.1.
32
Basic Information
Severity CRITICAL
Relates to Software
Category EQUIPMENT
Possible Cause(s)
This alarm may occur when:
The CPU cannot receive the Keep-Alive response from the DSP,
The Core, the Modem or the FPGA of the DSP is not operating normally.
Impact
Cell services related to the DSP are not available.
Remedy
To identify whether you need to take action and to correct the problem:
After the onset of the alarm, monitor the system to see if the alarm clears. If
the alarm is not cleared, go to step 2.
If the alarm is not cleared even after the DSP reset, contact Samsung.
33
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
Loss of Signal (LOS) or Loss of Frame (LOF) occurs in the Common Platform
Radio Interface (CPRI) layer.
Impact
Cell services related to the RRH that is connected to the relevant IMP port are not
available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Using LOS and LOF, you can check if the Rx path is normal. When an alarm
is generated, run the RTRV-RRH-STS command to check if the RRH is
normal.
34
Run the INIT-RRH command to reset the RRH, and monitor if the alarm is
cleared.
If the alarm is not cleared, run the INIT-PRC:IMP command to reset the
RRH, and monitor if the alarm is cleared.
If the alarm is not cleared, visit the site to perform on-site actions.
On-site Actions
To identify and correct the problem:
If the optical module is not properly mounted, unmount and remount the
optical module.
If the optical module of the IMP board and the RRH is properly mounted,
check the optical cable connection between the IMP and the RRH.
If the optical cable is not properly connected, disconnect and reconnect the
optical cable. Clean the optical cable connector if necessary.
If the optical cable is properly connected and the optical cable connector is
clean, unmount and remount the IMP.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared even after replacing the optical module, replace the
IMP.
For information about IMP (LUA) replacement, see the Samsung MBS Hardware
Addition & 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 IMP.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
35
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The optical cable is disconnected or the optical signal level is below the normal
parameters.
Impact
Service is disabled for the link.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Run the INIT-PRC:IMP command to reset the IMP, and monitor if the
alarm is cleared.
If the alarm is not cleared, visit the site and perform on-site actions.
36
On-site Actions
To identify and correct the problem:
If the optical module is not properly mounted, unmount and remount the
optical module.
If the optical module is properly mounted, check the optical cable connection.
If the optical cable is not properly connected, disconnect and reconnect the
optical cable. Clean the optical cable connector if necessary.
If the optical cable is properly connected and the optical cable connector is
clean, unmount and remount the IMP.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared even after replacing the optical module, replace the
IMP.
For information about IMP (LUA) replacement, see the Samsung MBS Hardware
Addition & 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 IMP.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
37
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The monitored power level of the laser diode signal in the optical module
(Modulation Current, Bias Current) is abnormal.
Impact
Service is disabled for the link.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Run the INIT-PRC:IMP command to reset the IMP, and monitor if the
alarm is cleared.
If the alarm is not cleared, visit the site and perform on-site actions.
38
On-site Actions
To identify and correct the problem:
If the optical module is not properly mounted, unmount and remount the
optical module.
If the optical module is properly mounted, check the optical cable connection.
If the optical cable is not properly connected, disconnect and reconnect the
optical cable. Clean the optical cable connector if necessary.
If the optical cable is properly connected and the optical cable connector is
clean, unmount and remount the IMP.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared even after replacing the optical module, replace the
IMP.
For information about IMP (LUA) replacement, see the Samsung MBS Hardware
Addition & 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 IMP.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
39
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
A link down failure (for example,. due to a bad port connection) of the backhaul
port occurs.
Impact
The board cannot communicate with the LSM or external devices.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Run the RTRV-ALM-LIST command to check the Clock Device alarms are
generated.
In the CLI window, run the INIT-PRC:IMP command to reset the IMP and
then check if an alarm is generated.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, inspect the IMP at the installation site and perform onsite actions.
40
On-site Actions
To identify and correct the problem:
Status
Description
Orange blinking (Left)
Green on (Right)
Off
Cable Open
Copper Port
Green
LED
Status
Description
Green On (Left)
Off
Orange
LED
Optical Port
Check that the Ethernet cable is correctly connected and that there is no
external damage.
Check that the optical cable is correctly connected and that there is no external
damage or bending.
Check that the connected optical cables (Single or Multi-Mode) are suitable
for the installed optical module type (Single or Multi-Mode).
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.
Check the status of the equipment connected to the backhaul port (for example,
router, switch).
If the equipment connected to the backhaul port is not working properly, reset
or replace the equipment.
Unmount the IMP. Disassemble and reassemble the DDR memory module.
Check if there is any foreign material in the memory connector (socket).
10 Mount the IMP and check if an alarm is generated after loading completes.
11 If the alarm is cleared, record the current status and observe any reoccurrence.
12 If the alarm is not cleared, record the failure details to the RMA TAG and
replace the IMP. Record the details including port connection configuration
status, the part number of mounted optical module, the optical cable type, etc.
For information about IMP replacement, see the Samsung MBS(LTE) Hardware
Addition and Replacement Manual for SLR 3.1.
41
Basic Information
Severity CRITICAL
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The SFN is measured every 10 ms. If there is no increase or decrease in SFN for
more than 10 consecutive measurements, an alarm is generated.
Impact
None.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
42
If the Clock Device (IEEE1588 or Sync-E) is normal, run the INITPRC:IMP command to reset the IMP, and monitor if the alarm is cleared.
If the alarm is not cleared, visit the site and perform on-site actions.
On-site Actions
To identify and correct the problem:
For information about IMP (LUA) replacement, see the Samsung MBS Hardware
Addition & 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 IMP.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
43
Basic Information
Severity CRITICAL
Relates to Software
Category EQUIPMENT
Possible Cause(s)
This alarm may occur when:
The CPU cannot receive the Keep-Alive response from the SOC,
The Core, the Modem or the FPGA of the SOC is not operating normally.
Impact
Cell services related to the SOC are not available.
Remedy
To identify whether you need to take action and to correct the problem:
After the onset of the alarm, monitor the system to see if the alarm clears. If
the alarm is not cleared, go to step 2.
If the alarm is not cleared even after the SOC reset, contact Samsung.
44
Basic Information
Severity CRITICAL
Relates to Software
Category PROCESSING
Possible Cause(s)
The SOC resets and restarts (by using the SOC Reset command or replacing the
SOC image).
Impact
Cell services related to the SOC are not available during restart.
Remedy
To identify and correct the problem:
If the alarm is not cleared after taking the described actions, or if the alarm
occurs repeatedly, contact Samsung.
45
Basic Information
Severity CRITICAL
Relates to Software
Category PROCESSING
Possible Cause(s)
The DSP resets and restarts (by using the DSP Reset command or replacing the
DSP image).
Impact
Cell services related to the ECP are not available during restart.
Remedy
To identify and correct the problem:
If the alarm is not cleared after taking the described actions, or if the alarm
occurs repeatedly, contact Samsung.
46
Basic Information
Severity MAJOR
Relates to Software
Category PROCESSING
Possible Cause(s)
This happens when a process is deactivated. You can find the cause by analyzing
the core file and log file uploaded to the LSM.
Impact
If an alarm generates continuously in a specific software block, service may not be
available.
Remedy
Whenever a process becomes deactivated, the process will be restarted
automatically within 3 seconds.
To identify whether you need to take action and to correct the problem:
Monitor the alarm status until the process restart occurs 10 times within 3
minutes.
If the process restart occurs more than 10 times during 3 minutes, run the
INIT-SW command to restart the process.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
47
Basic Information
Severity CRITICAL/MAJOR/MINOR
Relates to Software
Category QOS
Possible Cause(s)
The disk usage exceeds the threshold.
The threshold can be retrieved using the RTRV-ALM-THR COMMAND.
Impact
Some software blocks may operate abnormally.
Defaults
Minor: 85 %, Major: 90 %, Critical: 95 %
Remedy
To identify and correct the problem:
If the alarm is not cleared even after ECP reset, replace the ECP.
For information about board replacement, see the Samsung MBS(LTE) Hardware
Addition and Replacement Manual for SLR 3.1.
48
Basic Information
Severity CRITICAL/MAJOR/MINOR
Relates to Software
Category QOS
Possible Cause(s)
The memory usage exceeds the threshold.
The threshold can be retrieved using the RTRV-ALM-THR COMMAND.
Impact
Some software blocks may operate abnormally.
Defaults
Minor: 95 %, Major: 96 %, Critical: 97 %
Remedy
To identify and correct the problem:
Restart the software application whose memory usage is high, and then check
if the alarm is cleared.
If the alarm is not cleared even after ECP reset, replace the ECP.
49
For information about board replacement, see the Samsung MBS(LTE) Hardware
Addition and Replacement Manual for SLR 3.1.
50
Basic Information
Severity CRITICAL/MAJOR/MINOR
Relates to Software
Category QOS
Possible Cause(s)
The CPU usage exceeds the threshold.
The threshold value can be retrieved using the RTRV-ALM-THR COMMAND.
Impact
Some software blocks may operate abnormally. If an alarm is generated
continuously, the ECP board may reset.
Defaults
Minor: 85 %, Major: 90 %, Critical: 95 %
Remedy
To identify and correct the problem:
If the alarm is not cleared even after the ECP is reset, replace the ECP.
For information about board replacement, see the Samsung MBS(LTE) Hardware
Addition and Replacement Manual for SLR 3.1.
51
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
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
Service may be not available due to a CPRI Failure (RRU Interface).
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
52
If the frequency of the Clock Device (IEEE1588 or Sync-E) is normal, run the
INIT-PRC:ECP command to reset the ECP, and monitor if the alarm is
cleared.
If the alarm is not cleared, check the number of ECP boards in the system. If
an alarm is generated only for one ECP when there are two or more ECPs in
the system, visit the site immediately. If all the mounted ECPs are generating
alarms regardless of the number of ECPs (1 ECP or more), run the INITPRC:UMP command to reset the UMP, and monitor if the alarm is cleared.
If the alarm is not cleared, visit the site to perform on-site actions.
On-site Actions
To identify and correct the problem:
Unmount the ECP. Inspect the ECP edge pin and the backboard. If the ECP
edge pin is damaged, replace the ECP. If the backboard is damaged, replace
the shelf. Record the damage details.
If there is no apparent damage to the ECP and the backboard edge pin,
remount the ECP, and monitor if the alarm is cleared.
For information about ECP replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
If the alarm is cleared after replacing the ECP, record the current status and
observe any reoccurrence.
Prior to replacing the ECP, check the Fail Safe Boot Mode switch in the ECP
board.
If the board is replaced but was not loaded correctly because the Fail Safe
Boot switch (S1 switch) was in the OFF position, unmount the board, change
the switch position to ON and remount the board. If the board is loaded
correctly, you do not need to perform RMA.
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 following figure.
53
The default position of the S1 switch is ON. However, if the switch is the OFF
position, the board cannot be loaded. Make sure the switch is set to ON before
mounting the board.
54
Basic Information
Severity CRITICAL
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The board is unmounted.
Impact
Cell services related to the ECP are not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
You may not be able to collect status information during a board deletion failure
because connection to the ECP may not be possible.
Run the INIT-PRC:ECP command to reset the ECP, and monitor if the
alarm is cleared.
If the alarm is not cleared after the ECP is reset, run the INIT-PRC:UMP
command to reset the UMP.
If the alarm is not cleared after the UMP is reset, visit the site to perform onsite actions.
55
On-site Actions
To identify and correct the problem:
If the LED is off, remount the ECP. After remounting the ECP, go to Step 6.
If the alarm is not cleared even when the LED is on, unmount the ECP. Inspect
the ECP edge pin and the backboard. If the ECP edge pin is damaged, replace
the ECP. If the backboard is damaged, replace the shelf. Record the damage
details.
If there is no apparent damage to the ECP and the backboard edge pin,
remount the ECP, and monitor if the alarm is cleared.
If the alarm is not cleared even after remounting, unmount the ECP and mount
it on another slot.
If the alarm is cleared when the ECP is mounted on another slot, unmount the
UMP and inspect the UMP edge pin. In addition, inspect all the backboard
edge pins. If the UMP edge pin is damaged, replace the UMP. If the backboard
is damaged, replace the shelf. Record the damage details.
If the alarm is not cleared even when the ECP is mounted on another slot,
replace the ECP.
If the alarm is cleared, record the current status and observe any reoccurrence.
Record the fault details and affix them to the faulty ECP.
For information about replacement of ECP and other parts, see the Samsung MBS
Hardware Addition & Replacement Manual.
Alarms generated on the board are filtered and will not be reported while the
BOARD DELETION alarm remains active.
56
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
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
Cell services related to the ECP are not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Run the RTRV-PRC-STS, RTRV-ALM-LIST commands to check ECP
status.
Provide log files to Samsung for further analysis.
To correct the problem:
Run the INIT-PRC:ECP command to reset the ECP, and monitor if the
alarm is cleared.
If the alarm is not cleared, visit the site and perform on-site actions.
57
On-site Actions
To identify and correct the problem:
Unmount the ECP. Check the LED status to see if the alarm is cleared
(Normal: Blinking Green).
If the alarm is not cleared even after unmounting the ECP, replace the ECP.
For information about ECP replacement, see the Samsung MBS Hardware
Addition & 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.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
58
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
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
Cell services related to the ECP are not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Run the INIT-PRC:ECP command to reset the ECP, and monitor if the
alarm is cleared.
If the alarm is not cleared, visit the site to perform on-site actions.
59
On-site Actions
To identify and correct the problem:
Unmount and remount the ECP. Check the LED status for 5 minutes to see if
the alarm is cleared (Normal: Blinking Green).
If the alarm is not cleared after unmounting/mounting the ECP, replace the
ECP.
For information about ECP replacement, see the Samsung MBS Hardware
Addition & 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 occurs repeatedly after taking the described actions, please notify
Samsung.
60
Basic Information
Severity CRITICAL
Relates to Software
Category EQUIPMENT
Possible Cause(s)
This alarm may occur when:
The UMP cannot receive the Keep-Alive response from the DSP,
The Core, the Modem or the FPGA of the DSP is not operating normally.
Impact
Cell services related to the DSP are not available.
Remedy
To identify whether you need to take action and to correct the problem:
After the onset of the alarm, monitor the system to see if the alarm clears. If
the alarm is not cleared, go to step 2.
If the alarm is not cleared even after the DSP reset, contact Samsung.
61
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
Loss of Signal (LOS) or Loss of Frame (LOF) occurs in the Common Platform
Radio Interface (CPRI) layer.
Impact
Cell services related to the RRH that is connected to the relevant ECP port are not
available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Using LOS and LOF, you can check if the Rx path is normal. When an alarm
is generated, run the RTRV-RRH-STS command to check if the RRH is
normal.
62
Run the INIT-RRH command to reset the RRH, and monitor if the alarm is
cleared.
If the alarm is not cleared, run the INIT-PRC:ECP command to reset the
RRH, and monitor if the alarm is cleared.
If the alarm is not cleared, visit the site to perform on-site actions.
On-site Actions
To identify and correct the problem:
If the optical module is not properly mounted, unmount and remount the
optical module.
If the optical module is properly mounted, check the optical cable connection.
If the optical cable is not properly connected, disconnect and reconnect the
optical cable. Clean the optical cable connector if necessary.
If the optical cable is properly connected and the optical cable connector is
clean, unmount and remount the ECP.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared even after replacing the optical module, replace the
ECP.
For information about ECP replacement, see the Samsung MBS Hardware
Addition & 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.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
63
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The optical cable is disconnected or the optical signal level is below the normal
parameters.
Impact
Service is disabled for the link.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Run the INIT-PRC:ECP command to reset the ECP, and monitor if the
alarm is cleared.
If the alarm is not cleared, visit the site and perform on-site actions.
64
On-site Actions
To identify and correct the problem:
If the optical module is not properly mounted, unmount and remount the
optical module.
If the optical module is properly mounted, check the optical cable connection.
If the optical cable is not properly connected, disconnect and reconnect the
optical cable. Clean the optical cable connector if necessary.
If the optical cable is properly connected and the optical cable connector is
clean, unmount and remount the ECP.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared even after replacing the optical module, replace the
ECP.
For information about ECP replacement, see the Samsung MBS Hardware
Addition & 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.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
65
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The monitored power level of the laser diode signal in the optical module
(Modulation Current, Bias Current) is abnormal.
Impact
Service is disabled for the link.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Run the INIT-PRC:ECP command to reset the ECP, and monitor if the
alarm is cleared.
If the alarm is not cleared, visit the site and perform on-site actions.
66
On-site Actions
To identify and correct the problem:
If the optical module is not properly mounted, unmount and remount the
optical module.
If the optical module is properly mounted, check the optical cable connection.
If the optical cable is not properly connected, disconnect and reconnect the
optical cable. Clean the optical cable connector if necessary.
If the optical cable is properly connected and the optical cable connector is
clean, unmount and remount the ECP.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared even after replacing the optical module, replace the
ECP.
For information about ECP replacement, see the Samsung MBS Hardware
Addition & 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.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
67
Basic Information
Severity MAJOR
Relates to Software
Category EQUIPMENT
Possible Cause(s)
The main processor (UMP) did not receive the Keep-Alive response from the ECP.
Impact
Cell services related to the ECP are not available.
Remedy
To identify and correct the problem:
For information about board replacement, see the Samsung MBS(LTE) Hardware
Addition and Replacement Manual for SLR 3.1.
For information about board replacement, see the Samsung MBS(LTE) Hardware
Addition and Replacement Manual for SLR 3.1.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
68
Basic Information
Severity CRITICAL
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The SFN is measured every 10 ms. If there is no increase or decrease in SFN for
more than 10 consecutive measurements, an alarm is generated.
Impact
None.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
69
If the Clock Device (IEEE1588 or Sync-E) is normal, run the INITPRC:ECP command to reset the ECP, and monitor if the alarm is cleared.
If the alarm is not cleared after the ECP is reset, check the number of ECP
boards in the system. If an alarm is generated only for one ECP when there are
two or more ECPs in the system, visit the site immediately. If all the mounted
ECPs are generating alarms regardless of the number of ECPs (one or more
ECPs), run the INIT-PRC:UMP command to reset the UMP, and monitor if
the alarm is cleared.
If the alarm is not cleared, visit the site and perform on-site actions.
On-site Actions
To identify and correct the problem:
Unmount the ECP. Inspect the ECP edge pin and the backboard. If the ECP
edge pin is damaged, replace the ECP. If the backboard is damaged, replace
the shelf. Record the damage details.
If there is no apparent damage to the ECP and the backboard edge pin,
remount the ECP, and monitor if the alarm is cleared.
For information about ECP replacement, see the Samsung MBS Hardware
Addition & 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.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
70
Basic Information
Severity MINOR
Relates to Hardware
Category ENVIRONMENT
Possible Cause(s)
The actual operation speed (varies depending on the temperature) is lower than
compared to the target speed.
There is a communication problem between the fan and the fan controller
board.
Impact
None.
Remedy
Off-site Actions via LSM Before Site Visit
Do the following:
Run the RTRV-ALM-LIST: RRH command to check FAN alarm occurrence
information.
On-site Actions
To identify and correct the problem:
If the fan is working normally, record the current status and observe any
reoccurrence
71
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
72
Basic Information
Severity MAJOR
Relates to Hardware
Category ENVIRONMENT
Possible Cause(s)
The value of the RF unit temperature sensor is above the threshold value.
Impact
Service (call) is not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version and observe if the alarm occurs again.
If the alarm occurs after the firmware update, run the INIT-RRH command to
reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, visit the site and perform on-site actions.
73
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, check if the same alarm is generated in an adjacent
RRH, to rule out a problem related to the ambient temperature.
If the same alarm is not generated in an adjacent RRH, replace the RRH.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
74
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
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
Service (call) is not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
75
If the alarm is not cleared, visit the site and perform on-site actions.
On-site Actions
To identify and correct the problem:
If the optical cable is not properly connected, disconnect and reconnect the
optical cable. Clean the optical cable connector if necessary.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
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(or
IMP), replace the ECP(or IMP).
For information about ECP(or IMP) replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
76
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
RU power cycles or all the paths are shut down.
Impact
Service (call) is not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, visit the site and perform on-site actions.
77
On-site Actions
To identify and correct the problem:
If the optical cable is not properly connected, disconnect and reconnect the
optical cable. Clean the optical cable connector if necessary.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
78
Basic Information
Severity CRITICAL
Relates to Software
Category EQUIPMENT
Possible Cause(s)
The main processor (UMP) did not receive the Keep-Alive response from the RRH.
Impact
Cell services related to the RRH are not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If a CPRI_FAIL alarm occurs, visit the site and perform on-site actions.
On-site Actions
To identify and correct the problem:
Check the cable connection. Disconnect and reconnect the cable. If the cable is
properly connected, inspect the cable for damage. Replace the cable if
necessary.
If the alarm is not cleared after taking the described actions, power-cycle the
RRH.
If the alarm is not cleared even after the RRH is power-cycled, replace the
RRH.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
79
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The DC power input of the RF unit is not normal.
Impact
Service (call) is not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, visit the site and perform on-site actions.
80
On-site Actions
To identify and correct the problem:
Disconnect the power cable from the RRH and check the voltage of the power
connector.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
81
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The RRH is disabled due to the following reasons.
Initial status
Impact
Service (call) is not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, visit the site and perform on-site actions.
82
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
83
Basic Information
Severity MINOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
LNA Fail condition is maintained. This occurs when the LNA Fail (< 100 mA or >
250 mA) state lasts for 10 or more seconds.
Impact
Cell services related to the RRH are not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Run the RTRV-RRH-STS command to check the RRH status information and
RSSI level.
To identify and correct the problem:
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, visit the site and perform on-site actions.
84
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
85
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The gain estimated from the measured RF output power is below the threshold.
Impact
Cell services related to the RRH are not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, visit the site and perform on-site actions.
86
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
87
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The output power is more than 1.5 dB higher than the rated power.
Impact
Cell services related to the RRH are not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
88
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, visit the site and perform on-site actions.
On-site Actions
To identify and correct the problem:
If the optical cable is not properly connected, disconnect and reconnect the
optical cable. Clean the optical cable connector if necessary.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
89
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The VSWR measurement (return loss) is below the threshold.
Impact
Cell services related to the RRH are not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, visit the site and perform on-site actions.
90
On-site Actions
To identify and correct the problem:
Change the tilting of the antenna that is connected to the RRH that is
experiencing the alarm. Observe the changes in the VSWR fail alarm and
determine if the problem is due to the Tx output of an adjacent sector.
Check the antenna cables. Check the antenna for defects. Check the assembly
condition and the degree of protection against rain. If water entered between
the antenna cable and the connectors, a VSWR fail alarm may occur. Use a
hair dryer to thoroughly dry each connector, and test again.
If the VSWR returns to the normal level, apply rainproof silicone molding to
the RRH antenna port, antenna RF cable, and antenna port.
If the VSWR does not return to the normal level, connect an antenna and
antenna cable that do not have defects.
If an alarm persists after taking the described actions, power-cycle the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
91
Basic Information
Severity MINOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The digital input power level is at the threshold or higher.
Impact
None.
Defaults
18,022,000 IQ level
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If the threshold value is set too low, run the CHG-RRH-CONF command to
change it to an appropriate value.
92
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, visit the site and perform on-site actions.
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
If the alarm is not cleared even after the RRH is replaced, check the status of
the ECP(or IMP) that is connected to the RRH. If there is a problem with the
ECP(or IMP), replace the ECP(or IMP).
For information about ECP(or IMP) replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
93
Basic Information
Severity MINOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The digital input power level is the threshold or less.
Impact
None.
Defaults
16,900 IQ level
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If the threshold value is set too low, run the CHG-RRH-CONF command to
change it to an appropriate value.
94
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, visit the site and perform on-site actions.
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
If the alarm is not cleared even after the RRH is replaced, check the status of
the ECP (or IMP) that is connected to the RRH. If there is a problem with the
ECP (or IMP), replace the ECP(or IMP).
For information about ECP (or IMP) replacement, see the Samsung MBS
Hardware Addition & Replacement Manual.
95
Basic Information
Severity MINOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The Received Signal Strength Indication (RSSI) value, measured at a fixed
interval, is higher than the high threshold that is set by the operator.
Use the RTRV-RRH-CONF to retrieve the threshold value.
Impact
None.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If the threshold value is set too low, run the CHG-RRH-CONF command to
change it to an appropriate value.
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
96
If the alarm is not cleared, visit the site and perform on-site actions.
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
97
Basic Information
Severity MINOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The Received Signal strength indication (RSSI) value, measured at a fixed interval,
is lower than the low threshold that is set by the operator.
Use the RTRV-RRH-CONF to retrieve the threshold value.
Impact
None.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If the threshold value is set too high, run the CHG-RRH-CONF command to
change it to an appropriate value.
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
98
If the alarm is not cleared, visit the site and perform on-site actions.
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
99
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
Connected RRH H/W type did not match the configured RRH H/W type.
Impact
Cell services related to the RRH are not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Check if the RRH type of the result from step 2 and step 3 are the same. If
they are different, degrow and regrow the RRH using CHG-RRH-CONF.
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
100
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
10 If the alarm is not cleared, visit the site and perform on-site actions.
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
101
Basic Information
Severity MAJOR
Relates to Software
Category COMMUNICATIONS
Possible Cause(s)
The main processor does not receive the TOD message from the UCR.
Impact
None
Remedy
Off-site Actions via LSM Before Site Visit
To identify and correct the problem:
On-site Actions
To identify and correct the problem:
If the alarm is not cleared, replace the UMP (or IMP) board.
For information about UMP (or IMP) board replacement, see the Samsung MBS
(LTE) Hardware Addition and Replacement Manual.
102
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The feeding current to the antenna side is at the specified open or short
level.
Impact
No impact to the system directly, but it can be the reason for UCR LOCKING
FAIL and UCR FREQUENCY HOLDOVER EXCEED alarm messages.
Remedy
Off-site Actions via LSM Before Site Visit
To identify and correct the problem:
Run the RTRV-UCR-STS command to check the UCR status information.
If the GPS clock is not received due to the UCR antenna disconnection, the
internal HOLDOVER clock is used. If, however, the HOLDOVER status
continues for more than 1 week, the clock input may not be stable.
On-site Actions
To identify and correct the problem:
Check the alarm is cleared after replacing GPS Antenna system including GPS
Arrestor, Line amplifier and so on.
If the alarm is not cleared after step 1 and step 2, reset the UMP (or IMP).
If the alarm is not cleared after a reset of the UMP (or IMP), replace the UMP
(or IMP).
103
For information about UMP (or IMP) board replacement, see the Samsung MBS
(LTE) Hardware Addition and Replacement Manual.
104
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
Impact
No impact to System directly but it can be the reason for UCR FREQUENCY
HOLDOVER EXCEED.
Remedy
Off-site Actions via LSM Before Site Visit
To identify and correct the problem:
On-site Actions
To identify and correct the problem:
Check if the alarm is cleared after replacing GPS Antenna system including
GPS Arrestor, Line amplifier and so on.
Check the status of GPS Antenna parts, if no error is found, replace the UMP
(or IMP).
If the alarm is not cleared after step 1 and step 2, reset the UMP (or IMP).
105
Basic Information
Severity CRITICAL
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The UCR is reset by restarting the UCR or when a UCR module failure occurs.
Power failure (when the input power is 5.2 V or lower and 5.8 V or higher).
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
All cell services are not available
Remedy
Off-site Actions via LSM Before Site Visit
To identify and correct the problem:
Run the RTRV-UCR-STS command to check the UCR status information.
On-site Actions
To identify and correct the problem:
Replace the board if the alarm persists after re-initializing the board.
106
For information about UMP (or IMP) board replacement, see the Samsung MBS
(LTE) Hardware Addition and Replacement Manual.
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
1 week has passed since the transition to the holdover state.
Impact
N/A.
Remedy
Off-site Actions via LSM Before Site Visit
To identify and correct the problem:
If the alarms are generated, they are the reasons for UCR FREQUENCY
HOLDOVER EXCEED. See UCR ANTENNA FAIL or UCR LOCKING
FAIL.
107
On-site Actions
To identify and correct the problem:
Although UCR ANTENNA FAIL and UCR LOCKING FAIL alarm are not
generated, if UCR FREQUENCY HOLDOVER EXCEED is generated, reset
the UMP (or IMP).
After reset, if the alarm is not cleared, replace UMP (or IMP).
If the holdover clock mode of the UCR continues for more than 1 week, the clock
is unreliable.
Basic Information
Severity MAJOR
Relates to Software
Category COMMUNICATIONS
Possible Cause(s)
The main processor (UMP or IMP) does not receive the TOD message from the
PTPM.
Impact
None.
Remedy
Off-site Actions via LSM Before Site Visit
To identify and correct the problem:
If there are problems with the GM(Grand Master) configuration, run the CHGGM-INFO command to change the configuration as necessary.
108
If there are problems with the PTPM domain configuration, run the CHGPTPM-CONF command to change the domain as necessary.
If there are problems with the PTPM slave IP configuration, run the CHG-IPADDR command to change the IP of slave IP by checking IEEE1588 attribute.
Run the ping command to check the communication setting and status between
the MBS and the IEEE1588 Master.
Check if the PTP packet count on the PTP interface is increasing normally.
If the alarm is not cleared, replace the UMP (or IMP) board.
For information about UMP(or IMP) board replacement, see the Samsung MBS
Hardware Addition & Replacement Manual.
109
Basic Information
Severity MAJOR
Relates to Hardware
Category COMMUNICATIONS
Possible Cause(s)
The IEEE1588 clock slave module fails to collect information from the grand
master clock when normal communication between the two is available.
Impact
This may cause to the IEEE1588 clock to fail.
Remedy
To check the status of the IEEE1588 Grand Master Clock and to take
corrective actions:
If there are problems with the GM(Grand Master) configuration, run the CHGGM-INFO command to change the configuration as necessary.
If there are problems with the PTPM domain configuration, run the CHGPTPM-CONF command to change the domain as necessary.
If there are problems with the PTPM slave IP configuration, run the CHG-IPADDR command to change the IP of slave IP by checking IEEE1588 attribute.
Run the ping command to check the communication setting and status between
the MBS and the IEEE1588 Master.
Check if the PTP packet count on the PTP interface is increasing normally.
110
111
Basic Information
Severity MINOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The SPLL state in the IEEE1588 clock module is abnormal.
Impact
None.
Remedy
To check the status of the IEEE1588 Grand Master Clock and to take
corrective actions:
If there are problems with the GM(Grand Master) configuration, run the CHGGM-INFO command to change the configuration as necessary.
If there are problems with the PTPM domain configuration, run the CHGPTPM-CONF command to change the domain as necessary.
If there are problems with the PTPM slave IP configuration, run the CHG-IPADDR command to change the IP of slave IP by checking IEEE1588 attribute.
Run the ping command to check the communication setting and status between
the MBS and the IEEE1588 Master.
Check if the PTP packet count on the PTP interface is increasing normally.
112
113
Basic Information
Severity CRITICAL
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The initial state in the IEEE1588 clock module is abnormal.
Impact
All cell services are not available.
Remedy
On-site Actions
To identify and correct the problem:
(In case UAMA) Check the connection between the PSCM-P (Packet
Synchronization Clock Module - Plus) and the motherboard. The location of
the connection is shown in the following figure.
c
3
Check the BH interface used for 1588 PTPM communication with GM.
In case of UMP, Check the interface setting between UMP and PTP and take
actions.
If the alarm lasts over 3 minutes, reset and restart the board.
114
In case of IMP, Check the interface setting between IMP and PTP and take
actions.
After unmount and remount the IMP board, check if the alarm is clear.
For information about UMP (or IMP) board replacement, see the Samsung MBS
Hardware Addition & Replacement Manual.
115
Basic Information
Severity CRITICAL
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The threshold time is exceeded after transition to a holdover state.
Impact
All cell services may be not available.
Remedy
To check the status of the IEEE1588 Grand Master Clock and to take
corrective actions:
If there are problems with the GM(Grand Master) configuration, run the CHGGM-INFO command to change the configuration as necessary.
If there are problems with the PTPM domain configuration, run the CHGPTPM-CONF command to change the domain as necessary.
If there are problems with the PTPM slave IP configuration, run the CHG-IPADDR command to change the IP of slave IP by checking IEEE1588 attribute.
Run the ping command to check the communication setting and status between
the MBS and the IEEE1588 Master.
Check if the PTP packet count on the PTP interface is increasing normally.
116
117
Basic Information
Severity CRITICAL
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
This alarm is generated in unlocking 1588 system initialization.
Impact
All cell services may be not available.
Remedy
To check the status of the IEEE1588 Grand Master Clock and to take
corrective actions:
If there are problems with the GM(Grand Master) configuration, run the CHGGM-INFO command to change the configuration as necessary.
If there are problems with the PTPM domain configuration, run the CHGPTPM-CONF command to change the domain as necessary.
If there are problems with the PTPM slave IP configuration, run the CHG-IPADDR command to change the IP of slave IP by checking IEEE1588 attribute.
Run the ping command to check the communication setting and status between
the MBS and the IEEE1588 Master.
Check if the PTP packet count on the PTP interface is increasing normally.
118
119
Basic Information
Severity MAJOR
Relates to Hardware
Category COMMUNICATIONS
Possible Cause(s)
The quality of the SyncE master clock is lower than the Stratum 2 grade.
Impact
None.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If the QL SELECTED value is not one of the values below, check the SyncE
master status or configuration.
If there are problems with the SyncE master configuration, run the CHGSYNCE-CONF command to change the configuration as necessary.
120
On-site Actions
To identify and correct the problem:
If the alarm is not cleared after 15 minutes, run the INIT-SYS command to
reset and restart the UMP(or IMP).
For further information about checking the site environment, contact Samsung.
For information about board replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
121
Basic Information
Severity CRITICAL
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
IEEE1588 clock module initialization is abnormal.
Impact
All cell services may not be available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
(In case UAMA) Check the connection between the PSCM-P (Packet
Synchronization Clock Module - Plus) and the motherboard. The location of
the connection is shown in the following figure.
If the QL SELECTED value is not one of the values below, check the SyncE
master status or configuration.
122
If there are problems with the SyncE master configuration, run the CHGSYNCE-CONF command to change the configuration as necessary.
On-site Actions
To identify and correct the problem:
Check the System LED Status to determine the initialization status. If the LED
is not blinking green, unmount the UMP(or IMP) card from the shelf and
remount.
Check the SyncE related port LED Status to determine the synchronization
system status in the eNB.
If LED is not working, disconnect the link cable from the external port and
connect the cable to the external port.
If the alarm is not cleared after 15 minutes, reset and restart the board by INITSYS command.
Check the System LED Status. If the LED is not blinking green, unmount and
then remount the UMP (or IMP) card.
If the alarm is not cleared, replace the UMP (or IMP) board.
For information about board replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
123
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
Connection to the SyncE master (reference) is abnormal.
Impact
None.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If there are problems with the SyncE master configuration, run the CHGSYNCE-CONF command to change the configuration as necessary
124
On-site Actions
To identify and correct the problem:
Check the status of the SyncE port LED on the SyncE Master Server. If the
LED is off, disconnect the SyncE link cable from the port and re-connect it
again.
If the alarm is not cleared after 15 minutes, reset and restart the board.
If the alarm is not cleared after reset and restart, run INIT-SYS to reinitialize.
Check the System LED Status. If the LED is not blinking green, unmount and
then remount the UMP (or IMP) board.
If the alarm is not cleared, replace the UMP (or IMP) board.
For information about board replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
125
Basic Information
Severity CRITICAL
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
One week passes after a SyncE NO_CURRENT_MASTER or a SyncE
NO_CLOCK_REF_SIGNAL occurs.
Impact
All cell services may not be available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If there are problems with the SyncE master configuration, run the CHGSYNCE-CONF command to change the configuration as necessary.
126
On-site Actions
To identify and correct the problem:
Check the status of the SyncE port LED on the SyncE Master Server. If the
LED is off, disconnect the SyncE link cable from the port and re-connect it
again.
Check the status of the SyncE port LED on the eNB. If the LED is off,
disconnect the SyncE link cable from the external port and re-connect it again.
127
Basic Information
Severity CRITICAL
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The Hardware block related SyncE is unlocked.
Impact
All cell services may be not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If there are problems with the SyncE master configuration, run the CHGSYNCE-CONF command to change the configuration as necessary.
128
On-site Actions
To identify and correct the problem:
Check the status of the SyncE port LED on the eNB. If the LED is off,
disconnect the SyncE link cable from the external port and re-connect it again.
If the alarm is not cleared after 15 minutes, reset and restart the board.
If the alarm is not cleared after reset and restart, run INIT-SYS to re-initialize.
Check the System LED Status. If the LED is not blinking green, unmount and
then remount the UMP(or IMP) board.
For information about board replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
129
Basic Information
Severity CRITICAL
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
This alarm is generated when system is initialized by INIT-SYS and it stays in
the unlock state.
Impact
All cell services may not be available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If there are problems with the SyncE master configuration, run the CHGSYNCE-CONF command to change the configuration as necessary.
130
On-site Actions
To identify and correct the problem:
Check the status of the SyncE port LED on the eNB. If the LED is off,
disconnect the SyncE link cable from the external port and re-connect it again.
If the alarm is not cleared after 15 minutes, reset and restart the board.
If the alarm is not cleared after reset and restart, run INIT-SYS to re-initialize.
Check the System LED Status. If the LED is not blinking green, unmount and
then remount the UMP (or IMP) board.
If the alarm is not cleared, replace the UMP (or IMP) board.
131
Basic Information
Severity CRITICAL/MAJOR/MINOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
A user-defined alarm (UDA) is generated.
Impact
Varies with each UDA.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
In the CLI window, run the INIT-PRC:UMP command to reset the UMP.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, visit the site and perform on-site actions.
132
On-site Actions
To identify and correct the problem:
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 installation manual.
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
door of the enclosure and check if the alarm is cleared.
Unmount and remount the UMP and check if an alarm is generated after
loading completes.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about UMP replacement, see the Samsung MBS(LTE) Hardware
Addition and Replacement Manual for SLR 3.1.
133
Basic Information
Severity MAJOR
Relates to Hardware
Category ENVIRONMENT
Possible Cause(s)
The actual operation speed is lower than 60 % compared to the target speed
(varying depending on the temperature).
Impact
System cooling is impacted due to fan failure.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Run the RTRV-ALM-LIST:SYS command to view system alarms.
To correct the problem:
Visit the site and perform on-site actions.
On-site Actions
To identify and correct the problem:
If there is a FANM-C4 alarm, replace the fan. This alarm indicates the fan has
reached end of life and needs replacement.
For information about fan replacement, see the Samsung MBS(LTE) Hardware
Addition and Replacement Manual for SLR 3.1.
134
Basic Information
Severity MAJOR
Relates to Software
Category EQUIPMENT
Possible Cause(s)
The system time cannot be updated due to an incorrect server configuration or to a
lack of connectivity with the NTP server.
Impact
None.
Remedy
To identify and correct the problem:
If the IP address of the NTP server is not configured correctly, run the CHGNTP-CONF command to modify the IP address of the NTP server.
Run the ping command to verify connectivity between the eNB and NTP
server or LSM
After connecting to the LSM via the console. Check if the ntpdate to the NTP
server is working properly (ntpdate server IP).
If the NTP daemon is not working properly on the NTP server or the LSM,
restart the NTP service. (service ntpd restart)
135
Basic Information
Severity CRITICAL
Relates to Software
Category EQUIPMENT
Possible Cause(s)
All cells for the eNB are disabled.
Impact
All cell services are not available.
Remedy
To identify and correct the problem:
If all the cells are locked, run the CHG-CELL-CONF command to change the
cell configuration and unlock the cells.
If the alarm is not cleared, run the RTRV-CELL-STS command to check cell
status.
If an alarm is generated in the ECP (or IMP), take corrective measures specific
to the ECP(or IMP).
If the alarm is not cleared after taking the appropriate corrective measures, contact
Samsung.
136
Basic Information
Severity CRITICAL
Relates to Software
Category EQUIPMENT
Possible Cause(s)
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
Out of LTE service.
Remedy
To identify and correct the problem:
Check if the failure is caused by a connection problem with the SCTP or with
the S1AP.
If the alarm is not cleared after taking the described actions, contact Samsung.
137
Basic Information
Severity MAJOR
Relates to Software
Category PROCESSING
Possible Cause(s)
There is no response to the paging call transmitted by the eNB call processing
block to the idle UE after TRIGGERING_CONDITION_TIMER of PLD
DIAG_CALL_CONF.
Impact
None.
Defaults
The default value of TRIGGERING_CONDITION_TIMER is 1 hour.
138
Remedy
To identify and correct the problem:
If an alarm is generated although there is a call connection to the cell, then the
alarm is caused by incorrect operation. Run the CHG-DIAG-CONF command
to change the DIAG_CALL_ENABLE value to OFF.
139
Basic Information
Severity MAJOR
Relates to Software
Category EQUIPMENT
Possible Cause(s)
The S1 interface is in an abnormal state or the eNB cannot receive the SCTP
heartbeat response from the MME.
Impact
None.
Remedy
To identify and correct the problem:
Check if the failure is caused by a connection problem with the SCTP or with
the S1AP.
If the alarm is not cleared after taking the described actions, contact Samsung.
140
Chapter 3
SDU Alarm
Reference
Name
Severity
Relates to
Category
A2100102R
Major
Software
PROC
A2100217R
Major
Hardware
ENV
A2100300R
All
Software
QOS
A2100301R
All
Software
QOS
A2100302R
UMP OVERLOAD
All
Software
QOS
A2100351R
Major
Hardware
EQUIP
A2100370R
Major
Hardware
EQUIP
A2100380R
Major
Hardware
EQUIP
A2103100R
Critical
Software
PROC
A2103102R
Major
Software
PROC
A2103217R
Major
Hardware
ENV
A2103300R
All
Software
QOS
A2103301R
All
Software
QOS
A2103302R
IMP OVERLOAD
All
Software
QOS
A2103351R
Major
Hardware
EQUIP
A2103370R
Major
Hardware
EQUIP
A2103372R
Critical
Software
EQUIP
A2103376R
Major
Hardware
EQUIP
A2103378R
Major
Hardware
EQUIP
A2103379R
Major
Hardware
EQUIP
A2103380R
Major
Hardware
EQUIP
A2103607R
Critical
Hardware
EQUIP
A2103627R
IMP SOCFAIL
Critical
Software
EQUIP
A2103628R
Critical
Software
PROC
A2116100R
Critical
Software
PROC
A2116102R
Major
Software
PROC
A2116300R
All
Software
QOS
A2116301R
All
Software
QOS
A2116302R
ECP OVERLOAD
All
Software
QOS
A2116351R
Major
Hardware
EQUIP
A2116367R
Major
Hardware
EQUIP
A2116368R
Major
Hardware
EQUIP
A2116372R
Critical
Software
EQUIP
A2116376R
Major
Hardware
EQUIP
141
Name
Severity
Relates to
Category
A2116378R
Major
Hardware
EQUIP
A2116379R
Major
Hardware
EQUIP
A2116381R
Major
Software
EQUIP
A2116607R
Major
Hardware
EQUIP
A2149210R
Minor
Hardware
ENV
A2149216R
Major
Hardware
ENV
A2149351R
Major
Hardware
EQUIP
A2149368R
Major
Hardware
EQUIP
A2149381R
Critical
Software
EQUIP
A2149384R
Major
Hardware
EQUIP
A2149385R
RRH DISABLED
Major
Hardware
EQUIP
A2149388R
Minor
Hardware
EQUIP
A2149389R
Major
Hardware
EQUIP
A2149391R
Major
Hardware
EQUIP
A2149392R
Major
Hardware
EQUIP
A2149395R
Minor
Hardware
EQUIP
A2149408R
Minor
Hardware
EQUIP
A2149609R
Minor
Hardware
EQUIP
A2149610R
Minor
Hardware
EQUIP
A2149649R
Major
Hardware
EQUIP
A2180001R
UCR TOD_MSG_MISSED
Major
Software
COM
A2180350R
UCR ANTENNA_FAIL
Major
Hardware
EQUIP
A2180361R
Major
Hardware
EQUIP
A2180368R
UCR FUNCTION_FAIL
Critical
Hardware
EQUIP
A2180424R
Major
Hardware
EQUIP
A2184001R
Major
Software
COM
A2184003R
Major
Hardware
COM
A2184320R
Minor
Hardware
EQUIP
A2184321R
Critical
Hardware
EQUIP
A2184424R
Critical
Hardware
EQUIP
A2184430R
Critical
Hardware
EQUIP
A2192025R
Major
Hardware
COM
A2192321R
Critical
Hardware
EQUIP
A2192423R
Major
Hardware
EQUIP
A2192424R
Critical
Hardware
EQUIP
A2192428R
Critical
Hardware
EQUIP
A2192430R
Critical
Hardware
EQUIP
A2199202R
SYS UDA
All
Hardware
EQUIP
A2199209R
Major
Hardware
ENV
A2199216R
Major
Hardware
ENV
A2199365R
Major
Software
EQUIP
A2199460R
Critical
Software
EQUIP
142
Name
Severity
Relates to
Category
A2199600R
Critical
Software
EQUIP
A2199602R
Major
Software
PROC
A2199605R
Major
Software
EQUIP
143
Basic Information
Severity MAJOR
Relates to Software
Category PROCESSING
Possible Cause(s)
This happens when a process is deactivated. You can find a cause by analyzing the
core file and log file uploaded to the LSM.
Impact
If an alarm is generated continuously in a specific software block, service may not
be available.
Remedy
Whenever a process becomes deactivated, the process will be restarted
automatically within 3 seconds.
To identify whether you need to take action and to correct the problem:
Monitor the alarm status to see if the process restarts10 times within 3 minutes.
If the process restarts more than 10 times during 3 minutes, run the INIT-SW
command to manually initiate the process restart.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
144
Basic Information
Severity MAJOR
Relates to Hardware
Category ENVIRONMENT
Possible Cause(s)
The CPU temperature exceeds the threshold.
Impact
There may be damage to the system.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Check if the alarm is cleared. If the alarm is cleared, record the current status
and observe any reoccurrence.
If the alarm is not cleared, inspect the SDU at the installation site, and perform
on-site actions.
145
Check the outside of the SDU to find any element or foreign material that may
have blocked the air flow.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU10 replacement, see the Samsung SDU10 Installation
Manual.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
Check the status of the STS LED on the fan module at the front of the SDU.
Green indicates Normal and Red indicate fan failure.
If the STS LED is green, check that the fan is rotating normally.
Check the outside of the SDU to find any element or foreign material that may
have blocked the air flow.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the Samsung SDU11 Installation
Manual.
146
Basic Information
Severity CRITICAL/MAJOR/MINOR
Relates to Software
Category QOS
Possible Cause(s)
The disk usage exceeds the threshold.
The threshold value can be retrieved using the RTRV-ALM-THR command.
Impact
Some software blocks may operate abnormally.
Defaults
Minor: 85 %, Major: 90 %, Critical: 95 %
Remedy
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
147
Basic Information
Severity CRITICAL/MAJOR/MINOR
Relates to Software
Category QOS
Possible Cause(s)
The memory usage exceeds the threshold.
The threshold value can be retrieved using the RTRV-ALM-THR command.
Impact
Some software blocks may operate abnormally.
Defaults
Minor: 95 %, Major: 96 %, Critical: 97 %
Remedy
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
148
Basic Information
Severity CRITICAL/MAJOR/MINOR
Relates to Software
Category QOS
Possible Cause(s)
The CPU usage exceeds the threshold.
The threshold value can be retrieved using RTRV-ALM-THR command.
Impact
Some software blocks to operate abnormally. If an alarm is generated continuously,
the UMP board may reset.
Defaults
Minor: 85 %, Major: 90 %, Critical: 95 %
Remedy
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
149
Basic Information
Severity MAJOR
Relates to Hardware.
Category EQUIPMENT
Possible Cause(s)
The clock frequency (10 MHz, Even) of the clock module has a deviation beyond
normal parameters or there is no clock.
Impact
Service may be not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
150
In the CLI window, run the INIT-PRC:UMP command to reset the UMP.
Check if an alarm is generated.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, inspect the UMP at the installation site and perform
on-site actions.
Check if the backhaul connection cables are connected properly to the front
side of the SDU. If a cable is disconnected or damaged, reconnect or replace
the cable.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU10 replacement, see the SDU10 Installation Manual
Check if the backhaul connection cables are connected properly to the front
side of the SDU. If a cable is disconnected or damaged, reconnect or replace
the cable.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU11 Installation Manual.
151
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
Operation errors (data read/write) of the memory device occur.
Impact
Some software blocks may operate abnormally.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
In the CLI window, run the INIT-PRC:UMP command to reset the UMP and
then check if an alarm is generated.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, inspect the UMP at the installation site and perform
on-site actions.
152
On-site Actions
To correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
153
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
A link down failure (for example, due to a bad port connection) of the backhaul
port occurs.
Impact
The system cannot communicate with the LSM or external devices.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Run the RTRV-ALM-LIST command to check the Clock Device alarms are
generated.
In the CLI window, run the INIT-PRC:UMP command to reset the UMP and
then check if an alarm is generated.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, inspect the UMP at the installation site and perform
on-site actions.
154
On-site Actions
To identify and correct the problem:
Check that the Ethernet cable is correctly connected and that there is no
external damage.
Check that the optical cable is correctly connected and that there is no external
damage or bending.
Check the status of the equipment connected to the backhaul port (for example,
router, switch)
If the equipment connected to the backhaul port is not working properly, reset
or replace the equipment.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, Record the failure details to the RMA TAG and
replace the SDU. Record the details including port connection configuration
status, the optical cable type, etc.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
155
Basic Information
Severity CRITICAL
Relates to Software
Category PROCESSING
Possible Cause(s)
The DSP resets and restarts (by using the DSP Reset command or replacing the
DSP image).
Impact
Cell services related to the IMP are not available during restart.
Remedy
To identify and correct the problem:
If the alarm is not cleared after taking the described actions, or if the alarm
occurs repeatedly, contact Samsung
156
Basic Information
Severity MAJOR
Relates to Software
Category PROCESSING
Possible Cause(s)
This happens when a process is deactivated. You can find the cause by analyzing
the core file and log file uploaded to the LSM.
Impact
If an alarm generates continuously in a specific software block, service may not be
available.
Remedy
Whenever a process becomes deactivated, the process will be restarted
automatically within 3 seconds.
To identify whether you need to take action and to correct the problem:
Monitor the alarm status until the process restart occurs 10 times within 3
minutes.
If the process restart occurs more than 10 times during 3 minutes, run the
INIT-SW command to restart the process.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
157
Basic Information
Severity MAJOR
Relates to Hardware
Category ENVIRONMENT
Possible Cause(s)
The CPU temperature exceeds the threshold.
Impact
There may be damage to the board.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Check if the alarm is cleared. If the alarm is cleared, record the current status
and observe any reoccurrence.
If the alarm is not cleared, inspect the IMP at the installation site, and perform
on-site actions.
158
On-site Actions
To identify and correct the problem:
Check the outside of the SDU to find any element or foreign material that may
have blocked the air flow.
For information about fan replacement, see the Samsung MBS(LTE) Hardware
Addition and Replacement Manual for SLR 3.1.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual .
Check the status of the STS LED on the fan module at the front of the DU.
Green: Normal
Check the outside of the SDU to find any element or foreign material that may
have blocked the air flow.
For information about fan replacement, see the Samsung MBS(LTE) Hardware
Addition and Replacement Manual for SLR 3.1.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about IMP replacement, see the SDU11 Installation Manual.
159
Basic Information
Severity CRITICAL/MAJOR/MINOR
Relates to Software
Category QOS
Possible Cause(s)
The disk usage exceeds the threshold.
The threshold value can be retrieved using the RTRV-ALM-THR command.
Impact
Some software blocks may operate abnormally.
Defaults
Minor: 85 %, Major: 90 %, Critical: 95 %
Remedy
To identify and correct the problem:
If the alarm is not cleared even after IMP is reset, replace the IMP.
For information about IMP replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
160
Basic Information
Severity CRITICAL/MAJOR/MINOR
Relates to Software
Category QOS
Possible Cause(s)
The memory usage exceeds the threshold.
The threshold value can be retrieved using the RTRV-ALM-THR command.
Impact
Some software blocks may operate abnormally.
Defaults
Minor: 95 %, Major: 96 %, Critical: 97 %
Remedy
To identify and correct the problem:
If there is no software application with a high memory usage, reset the IMP.
If the alarm is not cleared even after the IMP is reset, replace the IMP.
For information about board replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
161
Basic Information
Severity CRITICAL/MAJOR/MINOR
Relates to Software
Category QOS
Possible Cause(s)
The CPU usage exceeds the threshold.
The threshold value can be retrieved using RTRV-ALM-THR command.
Impact
Some software blocks to operate abnormally. If an alarm is generated continuously,
the IMP board may reset.
Defaults
Minor: 85 %, Major: 90 %, Critical: 95 %
Remedy
To identify and correct the problem:
If there is no software application with a high CPU usage, reset the IMP.
If the alarm is not cleared even after the IMP is reset, replace the IMP
For information about IMP replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
162
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The clock frequency (10 MHz, Even) of the clock module has a deviation beyond
normal parameters or there is no clock.
Impact
Service may not be available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
In the CLI window, run the INIT-PRC:IMP command to reset the IMP.
Check if an alarm is generated.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, inspect the IMP at the installation site and perform
on-site actions.
163
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
164
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
Operation errors (data read/write) of the memory device occur.
Impact
Some software blocks may operate abnormally.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
In the CLI window, run the INIT-PRC:IMP command to reset the IMP and
then check if an alarm is generated.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, inspect the IMP at the installation site and perform
on-site actions.
165
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
166
Basic Information
Severity CRITICAL
Relates to Software
Category EQUIPMENT
Possible Cause(s)
This alarm may occur when:
The CPU cannot receive the Keep-Alive response from the DSP,
The Core, the Modem or the FPGA of the DSP is not operating normally.
Impact
Cell services related to the DSP are not available.
Remedy
To identify whether you need to take action and to correct the problem:
After the onset of the alarm, monitor the system to see if the alarm clears. If
the alarm is not cleared, go to step 2.
If the alarm is not cleared even after the DSP reset, contact Samsung.
167
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
Loss of Signal (LOS) or Loss of Frame (LOF) occurs in the Common Platform
Radio Interface (CPRI) layer.
Impact
Cell services related to the RRH that is connected to the relevant IMP port are not
available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Using LOS and LOF, you can check if the Rx path is normal. When an alarm
is generated, run the RTRV-RRH-STS command to check if the RRH is
normal.
168
Run the INIT-RRH command to reset the RRH, and monitor if the alarm is
cleared.
If the alarm is not cleared, run the INIT-PRC:IMP command to reset the
RRH, and monitor if the alarm is cleared.
If the alarm is not cleared, visit the site to perform on-site actions.
On-site Actions
To identify and correct the problem:
If the optical cable is not properly connected, disconnect and reconnect the
optical cable. Clean the optical cable connector if necessary.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
169
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The optical cable is disconnected or the optical signal level is below the normal
parameters.
Impact
Service is disabled for the link.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Run the INIT-PRC:IMP command to reset the IMP, and monitor if the
alarm is cleared.
If the alarm is not cleared, visit the site and perform on-site actions.
170
On-site Actions
To identify and correct the problem:
If the optical cable is not properly connected, disconnect and reconnect the
optical cable. Clean the optical cable connector if necessary.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
171
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The monitored power level of the laser diode signal in the optical module
(Modulation Current, Bias Current) is abnormal.
Impact
Service is disabled for the link.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Run the INIT-PRC:IMP command to reset the IMP, and monitor if the
alarm is cleared.
If the alarm is not cleared, visit the site and perform on-site actions.
172
On-site Actions
To identify and correct the problem:
If the optical cable is not properly connected, disconnect and reconnect the
optical cable. Clean the optical cable connector if necessary.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
173
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
A link down failure (for example, due to a bad port connection) of the backhaul
port occurs.
Impact
The board cannot communicate with the LSM or external devices.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Run the RTRV-ALM-LIST command to check the Clock Device alarms are
generated.
In the CLI window, run the INIT-PRC:IMP command to reset the IMP and
then check if an alarm is generated.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, inspect the IMP at the installation site and perform
on-site actions.
174
On-site Actions
To identify and correct the problem:
Check that the Ethernet cable is correctly connected and that there is no
external damage.
Check that the optical cable is correctly connected and that there is no external
damage or bending.
Check the status of the equipment connected to the backhaul port (for example,
router, switch)
If the equipment connected to the backhaul port is not working properly, reset
or replace the equipment.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, Record the failure details to the RMA TAG and
replace the SDU. Record the details including port connection configuration
status, the optical cable type, etc.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
175
Basic Information
Severity CRITICAL
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The SFN is measured every 10 ms. If there is no increase or decrease in SFN for
more than 10 consecutive measurements, an alarm is generated.
Impact
None.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
176
If the Clock Device (IEEE1588 or Sync-E) is normal, run the INITPRC:IMP command to reset the IMP, and monitor if the alarm is cleared.
If the alarm is not cleared, visit the site and perform on-site actions.
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
177
Basic Information
Severity CRITICAL
Relates to Software
Category EQUIPMENT
Possible Cause(s)
This alarm may occur when:
The CPU cannot receive the Keep-Alive response from the SOC,
The Core, the Modem or the FPGA of the SOC is not operating normally.
Impact
Cell services related to the SOC are not available.
Remedy
To identify whether you need to take action and to correct the problem:
After the onset of the alarm, monitor the system to see if the alarm clears. If
the alarm is not cleared, go to step 2.
If the alarm is not cleared even after the SOC reset, contact Samsung.
178
Basic Information
Severity CRITICAL
Relates to Software
Category PROCESSING
Possible Cause(s)
The SOC resets and restarts (by using the SOC Reset command or replacing the
SOC image).
Impact
Cell services related to the SOC are not available during restart.
Remedy
To identify and correct the problem:
If the alarm is not cleared after taking the described actions, or if the alarm
occurs repeatedly, contact Samsung.
179
Basic Information
Severity CRITICAL
Relates to Software
Category PROCESSING
Possible Cause(s)
The DSP resets and restarts (by using the DSP Reset command or replacing the
DSP image)
Impact
Cell services related to the ECP are not available during restart.
Remedy
To identify and correct the problem:
Run the INIT-DSP command to reset the DSP.
If the alarm is not cleared after taking the described actions, or if the alarm occurs
repeatedly, contact Samsung.
180
Basic Information
Severity MAJOR
Relates to Software
Category PROCESSING
Possible Cause(s)
This happens when a process is deactivated. You can find a cause by analyzing the
core file and log file uploaded to the LSM.
Impact
If an alarm generates continuously in a specific software block, service may be not
available.
Remedy
Whenever a process becomes deactivated, the process will be restarted
automatically within 3 seconds.
To identify whether you need to take action and to correct the problem:
Monitor the alarm status until the process restart occurs 10 times within 3
minutes.
If the process restart occurs more than 10 times during 3 minutes, run the
INIT-SW command to restart the process.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
181
Basic Information
Severity CRITICAL/MAJOR/MINOR
Relates to Software
Category QOS
Possible Cause(s)
The disk usage exceeds the threshold.
The threshold can be retrieved using the RTRV-ALM-THR command.
Impact
Some software blocks may operate abnormally.
Defaults
Minor: 85 %, Major: 90 %, Critical: 95 %
Remedy
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
182
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
183
Basic Information
Severity CRITICAL/MAJOR/MINOR
Relates to Software
Category QOS
Possible Cause(s)
The memory usage exceeds the threshold.
The threshold can be retrieved using the RTRV-ALM-THR command.
Impact
Some software blocks may operate abnormally.
Defaults
Minor: 95 %, Major: 96 %, Critical: 97 %
Remedy
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
184
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
185
Basic Information
Severity CRITICAL/MAJOR/MINOR
Relates to Software
Category QOS
Possible Cause(s)
The CPU usage exceeds the threshold.
The threshold value can be retrieved using the RTRV-ALM-THR command.
Impact
Some software blocks may operate abnormally. If an alarm is generated
continuously, the SDU may reset.
Defaults
Minor: 85 %, Major: 90 %, Critical: 95 %
Remedy
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
186
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
187
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
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
Service may not be available due to a CPRI Failure (RRU Interface).
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If the frequency of the Clock Device (IEEE1588 or Sync-E) is normal, run the
INIT-PRC:ECP command to reset the ECP, and monitor if the alarm is
cleared.
If the alarm is not cleared, run the INIT-PRC:UMP command to reset the
UMP, and monitor if the alarm is cleared.
188
If the alarm is not cleared, visit the site to perform on-site actions.
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
189
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
Any 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
Cell services related to the ECP are not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Run the RTRV-PRC-STS, RTRV-ALM-LIST commands to check the ECP
status.
Provide log files to Samsung for further analysis.
190
Run the INIT-PRC:ECP command to reset the ECP, and monitor if the
alarm is cleared.
If the alarm is not cleared, visit the site and perform on-site actions.
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
191
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
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
Cell Services related to the ECP are not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Run the INIT-PRC:ECP command to reset the ECP, and monitor if the
alarm is cleared.
If the alarm is not cleared, visit the site to perform on-site actions.
192
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
193
Basic Information
Severity CRITICAL
Relates to Software
Category EQUIPMENT
Possible Cause(s)
This alarm may occur when:
The UMP cannot receive the Keep-Alive response from the DSP,
The Core, the Modem or the FPGA of the DSP is not operating normally.
Impact
Cell services related to the DSP are not available.
Remedy
After checking the alarm message, take the following action to clear the alarm that
is not cleared for a long time.
To identify whether you need to take action and to correct the problem:
After the onset of the alarm, monitor the system to see if the alarm clears. If
the alarm is not cleared within go to step 2.
If the alarm is not cleared even after the DSP reset, contact Samsung.
194
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
Loss of Signal (LOS) or Loss of Frame (LOF) occurs in the Common Platform
Radio Interface (CPRI) layer.
Impact
Cell services related to the RRH that is connected to the relevant ECP port are not
available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Using LOS and LOF, you can check if the Rx path is normal. When an alarm
is generated, run the RTRV-RRH-STS command to check if the RRH is
normal.
195
Run the INIT-RRH command to reset the RRH, and monitor if the alarm is
cleared.
If the alarm is not cleared, run the INIT-PRC:ECP command to reset the
RRH, and monitor if the alarm is cleared.
If the alarm is not cleared, visit the site to perform on-site actions.
On-site Actions
To identify and correct the problem:
If the optical cable is not properly connected, disconnect and reconnect the
optical cable. Clean the optical cable connector if necessary.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
196
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The optical cable is disconnected or the optical signal level is below the normal
parameters.
Impact
Service is disabled for the link.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Run the INIT-PRC:ECP command to reset the ECP, and monitor if the
alarm is cleared.
If the alarm is not cleared, visit the site and perform on-site actions.
197
On-site Actions
To identify and correct the problem:
If the optical cable is not properly connected, disconnect and reconnect the
optical cable. Clean the optical cable connector if necessary.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
198
Basic Information
Severity MAJOR
Relates to Hardware
Category
EQUIPMENT
Possible Cause(s)
The monitored power level of the laser diode signal in the optical module
(Modulation Current, Bias Current) is abnormal.
Impact
Service is disabled for the link.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Run the INIT-PRC:ECP command to reset the ECP, and monitor if the
alarm is cleared.
If the alarm is not cleared, visit the site and perform on-site actions.
199
On-site Actions
To identify and correct the problem:
If the optical cable is not properly connected, disconnect and reconnect the
optical cable. Clean the optical cable connector if necessary.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
If the alarm occurs repeatedly after taking the described actions, please notify
Samsung.
200
Basic Information
Severity MAJOR
Relates to Software
Category EQUIPMENT
Possible Cause(s)
The main processor (UMP) did not receive the Keep-Alive response from the ECP.
Impact
Cell services related to the ECP are not available.
Remedy
To identify and correct the problem:
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
201
Basic Information
Severity CRITICAL
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The SFN is measured every 10 ms. If there is no increase or decrease in SFN for
more than 10 consecutive measurements, an alarm is generated.
Impact
None.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If the frequency of the Clock Device (IEEE1588 or Sync-E) is normal, run the
INIT-PRC:ECP command to reset the ECP, and monitor if the alarm is
cleared.
If the alarm is not cleared, run the INIT-PRC:UMP command to reset the
UMP, and monitor if the alarm is cleared.
If the alarm is not cleared, visit the site and perform on-site actions.
202
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
203
Basic Information
Severity MINOR
Relates to Hardware
Category ENVIRONMENT
Possible Cause(s)
The actual operation speed (varies depending on the temperature) is lower than
compared to the target speed.
There is a communication problem between the fan and the fan controller
board.
Impact
None.
Remedy
Off-site Actions via LSM Before Site Visit
Do the following:
Run the RTRV-ALM-LIST: RRH command to check FAN alarm occurrence
information.
On-site Actions
To identify and correct the problem:
If the fan is working normally, record the current status and observe any
reoccurrence
204
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
205
Basic Information
Severity MINOR
Relates to Hardware
Category ENVIRONMENT
Possible Cause(s)
The value of the RF unit temperature sensor is above the threshold value
Impact
Service (call) is not available.
Remedy
Off-site Actions via LSM Before Site Visit
To identify and correct the problem:
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version and observe if the alarm occurs again.
If the alarm occurs after the firmware update, run the INIT-RRH command to
reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, visit the site and perform on-site actions.
206
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, check if the same alarm is generated in an adjacent
RRH, to rule out a problem related to the ambient temperature.
If the same alarm is not generated in an adjacent RRH, replace the RRH.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
207
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The clock used inside the RF unit is not normal.
Impact
Service (call) is not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
208
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, visit the site and perform on-site actions.
On-site Actions
To identify and correct the problem:
If the optical cable is not properly connected, disconnect and reconnect the
optical cable. Clean the optical cable connector if necessary.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
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 SDU.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
209
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
RU power cycles or all the paths are shut down.
Impact
Service (call) is not available
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
210
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, visit the site and perform on-site actions.
On-site Actions
To identify and correct the problem:
If the optical cable is not properly connected, disconnect and reconnect the
optical cable. Clean the optical cable connector if necessary.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
211
Basic Information
Severity CRITICAL
Relates to Software
Category EQUIPMENT
Possible Cause(s)
The main processor (UMP) did not receive the Keep-Alive response from the RRH.
Impact
Cell services related to the RRH is not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If a CPRI_FAIL alarm occurs, visit the site and perform on-site actions.
On-site Actions
To identify and correct the problem:
Check the cable connection. Disconnect and reconnect the cable. If the cable is
properly connected, inspect the cable for damage. Replace the cable if
necessary.
If the alarm is not cleared after taking the described actions, power-cycle the
RRH.
If the alarm is not cleared even after the RRH is power-cycled, replace the
RRH.
212
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
213
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The DC power input of the RF unit is not normal.
Impact
Cell services related to the RRH are not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
214
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, visit the site and perform on-site actions.
On-site Actions
To identify and correct the problem:
Disconnect the power cable from the RRH and check the voltage of the power
connector.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
215
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The RRH is disabled due to the following reasons.
Initial status,
Impact
Cell services related to the RRH are not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, visit the site and perform on-site actions.
216
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
217
Basic Information
Severity MINOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
LNA Fail condition is maintained. This occurs when the LNA Fail (< 100 mA or >
250 mA) state lasts for 10 or more seconds.
Impact
Cell services related to the RRH are not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Run the RTRV-RRH-STS command to check the RRH status information and
RSSI level.
To identify and correct the problem:
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, visit the site and perform on-site actions.
218
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
219
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The gain estimated from the measured RF output power is below the threshold.
Impact
Cell services related to the RRH are not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, visit the site and perform on-site actions.
220
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
221
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The output power is more than 1.5 dB higher than the rated power
Impact
Cell services related to the RRH are not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
222
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, visit the site and perform on-site actions.
On-site Actions
To identify and correct the problem:
If the optical cable is not properly connected, disconnect and reconnect the
optical cable. Clean the optical cable connector if necessary.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
223
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The VSWR measurement (return loss) is below the threshold.
Impact
Cell services related to the RRH are not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, visit the site and perform on-site actions.
224
On-site Actions
To identify and correct the problem:
Change the tilting of the antenna that is connected to the RRH that is
experiencing the alarm. Observe the changes in the VSWR fail alarm and
determine if the problem is due to the Tx output of an adjacent sector.
Check the antenna cables. Check the antenna for defects. Check the assembly
condition and the degree of protection against rain. If water entered between
the antenna cable and the connectors, a VSWR fail alarm may occur. Use a
hair dryer to thoroughly dry each connector, and test again.
If the VSWR returns to the normal level, apply rainproof silicone molding to
the RRH antenna port, antenna RF cable, and antenna port.
If the VSWR does not return to the normal level, connect an antenna and
antenna cable that do not have defects.
If an alarm persists after taking the described actions, power-cycle the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
225
Basic Information
Severity MINOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The digital input power level is at the threshold or higher.
Impact
Cell services related to the RRH are not available.
Defaults
18,022,000 IQ level
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
226
If the threshold value is set too low, run the CHG-RRH-CONF command to
change it to an appropriate value.
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, visit the site and perform on-site actions.
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
If the alarm is not cleared even after the RRH is replaced, check the status of
the ECP (or IMP) that is connected to the RRH. If there is a problem with the
ECP (or IMP), replace the SDU.
For information about ECP replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
227
Basic Information
Severity MINOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The digital input power level is at the threshold or less.
Impact
None.
Defaults
16,900 IQ level
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
228
If the threshold value is set too low, run the CHG-RRH-CONF command to
change it to an appropriate value.
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, visit the site and perform on-site actions.
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
If the alarm is not cleared even after the RRH is replaced, check the status of
the ECP (or IMP) that is connected to the RRH. If there is a problem with the
ECP (or IMP), replace the SDU.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
229
Basic Information
Severity MINOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The Received Signal Strength Indication (RSSI) value, measured at a fixed
interval, is higher than the high threshold that is set by the operator.
Use the RTRV-RRH-CONF command to retrieve the threshold value.
Impact
None.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If the threshold value is set too low, run the CHG-RRH-CONF command to
change it to an appropriate value.
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
230
If the alarm is not cleared, visit the site and perform on-site actions.
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
231
Basic Information
Severity MINOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The Received Signal strength indication (RSSI) value, measured at a fixed interval,
is lower than the low threshold that is set by the operator.
Use the RTRV-RRH-CONF command to retrieve the threshold value.
Impact
None.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If the threshold value is set too high, run the CHG-RRH-CONF command to
change it to an appropriate value.
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
232
If the alarm is not cleared, visit the site and perform on-site actions.
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
233
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
Connected RRH H/W type did not match the configured RRH H/W type.
Impact
Cell services related to the RRH are not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
Check if the RRH type of the result step 2 and step 3 are the same. If they are
different, degrow and regrow the RRH using CHG-RRH-CONF.
234
If the firmware version is not the latest, run the UDT-RRH-FW command to
update the firmware to the latest version, and observe if the alarm occurs again.
If the alarm occurs again after the firmware update, run the INIT-RRH
command to reset the RRH.
If the alarm is cleared, record the current status and observe any reoccurrence.
10 If the alarm is not cleared, visit the site and perform on-site actions.
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about RRH replacement, see the Samsung MBS Hardware
Addition & Replacement Manual.
235
Basic Information
Severity MAJOR
Relates to Software
Category COMMUNICATIONS
Possible Cause(s)
The main processor does not receive the TOD message from the UCR.
Impact
None
Remedy
Off-site Actions via LSM Before Site Visit
To identify and correct the problem:
On-site Actions
To identify and correct the problem:
If the alarm is not cleared, replace the UMP (or IMP) board.
For information about UMP (or IMP) board replacement, see the SDU Insallation
Manual.
236
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The feeding current to the antenna side is at the specified open or short
level.
Impact
No impact to the system directly, but it can be the reason for UCR LOCKING
FAIL and UCR FREQUENCY HOLDOVER EXCEED alarm messages.
Remedy
Off-site Actions via LSM Before Site Visit
To identify and correct the problem:
Run the RTRV-UCR-STS command to check the UCR status information.
If the GPS clock is not received due to the UCR antenna disconnection, the
internal HOLDOVER clock is used. If, however, the HOLDOVER status
continues for more than 1 week, the clock input may not be stable.
On-site Actions
To identify and correct the problem:
Check the alarm is cleared after replacing GPS Antenna system including GPS
Arrestor, Line amplifier and so on.
If the alarm is not cleared after step 1 and step 2, reset the UMP (or IMP).
If the alarm is not cleared after a reset of the UMP (or IMP), replace the UMP
(or IMP).
237
For information about UMP (or IMP) board replacement, see the SDU Installation
Manual.
238
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
Impact
No impact to System directly but it can be the reason for UCR FREQUENCY
HOLDOVER EXCEED.
Remedy
Off-site Actions via LSM Before Site Visit
To identify and correct the problem:
On-site Actions
To identify and correct the problem:
Check if the alarm is cleared after replacing GPS Antenna system including
GPS Arrestor, Line amplifier and so on.
Check the status of GPS Antenna parts, if no error is found, replace the UMP
(or IMP).
If the alarm is not cleared after step 1 and step 2, reset the UMP (or IMP).
239
240
Basic Information
Severity CRITICAL
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The UCR is reset by restarting the UCR or when a UCR module failure occurs.
Power failure (when the input power is 5.2 V or lower and 5.8 V or higher).
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
All cell services are not available
Remedy
Off-site Actions via LSM Before Site Visit
To identify and correct the problem:
Run the RTRV-UCR-STS command to check the UCR status information.
On-site Actions
To identify and correct the problem:
Replace the board if the alarm persists after re-initializing the board.
For information about UMP (or IMP) board replacement, see the SDU Installation
Manual.
241
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
1 week has passed since the transition to the holdover state.
Impact
N/A.
Remedy
Off-site Actions via LSM Before Site Visit
To identify and correct the problem:
If the alarms are generated, they are the reasons for UCR FREQUENCY
HOLDOVER EXCEED. See UCR ANTENNA FAIL or UCR NO GPS
SIGNAL.
On-site Actions
To identify and correct the problem:
Although UCR ANTENNA FAIL and UCR NO GPS SIGNAL alarm are not
generated, if UCR FREQUENCY HOLDOVER EXCEED is generated, reset
the UMP (or IMP).
After reset, if the alarm is not cleared, replace UMP (or IMP).
242
If the holdover clock mode of the UCR continues for more than 1 week, the clock
is unreliable.
243
Basic Information
Severity MAJOR
Relates to Software
Category COMMUNICATIONS
Possible Cause(s)
The main processor (UMP or IMP) does not receive the TOD message from the
PTPM.
Impact
None.
Remedy
Off-site Actions via LSM Before Site Visit
To identify and correct the problem:
If there are problems with the PTPM configuration, run the CHG-PTPMCONF command to change the configuration as necessary.
If the alarm is not cleared, visit the site and perform on-site actions.
Run the INIT-PRC:UMP (or IMP) command in the CLI window to reset the
UPM (or IMP). Check if an alarm is generated.
244
On-site Actions
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
245
Basic Information
Severity MAJOR
Relates to Hardware
Category COMMUNICATIONS
Possible Cause(s)
The IEEE1588 clock slave module fails to collect information from the grand
master clock when normal communication between the two is available.
Impact
None.
Remedy
To check the status of the IEEE1588 Grand Master Clock and to take
corrective actions:
Check the PTPM device state. The value of the PTPM device state should be
PTPM_RUNNING.
Check the lock state. The clock signal should be in the PTP_UNLOCKING
state.
246
11 Run the RTRV-PTPM-STS command to check the PTPM status and current
Grand Master IP address.
12 If there are problems with the PTPM or the Grand Master Clock configuration,
run the CHG-PTPM-CONF or the CHG-GM-INFO command to change the
configuration as necessary.
13 If the problem cannot be solved by changing the PTPM or the Grand Master
Clock configuration, continue to the next step.
14 Run the ping command to check the communication setting and status
between the UMP PTP and the IEEE1588 Master.
15 If the alarm persists for more than 2 minutes, power-cycle the SDU.
16 Check if the PTP packet count on the PTP interface is increasing normally.
17 Check the Grand Master state and check if it is operating normally.
18 Check the network state and quality.
247
Basic Information
Severity MINOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The SPLL state in the IEEE1588 clock module is abnormal.
Impact
None.
Remedy
To check the status of the IEEE1588 Grand Master Clock and to take
corrective actions:
Run the RTRV-PTPM-STS command to check the PTPM status and current
Grand Master IP address.
If there are problems with the PTPM or the Grand Master Clock configuration,
run the CHG-PTPM-CONF or the CHG-GM-INFO command to change the
configuration as necessary.
If the problem cannot be solved by changing the PTPM or the Grand Master
Clock configuration, continue to the next step.
Run the ping command to check the communication setting and status
between the UMP PTP and the IEEE1588 Master.
10 Check if the PTP packet count on the PTP interface is increasing normally.
Samsung MBS(LTE) Alarm Manual for SLR 3.1 v2.0
Samsung Proprietary and Confidential
248
249
Basic Information
Severity CRITICAL
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The initial state in the IEEE1588 clock module is abnormal.
Impact
All cell services are not available.
Remedy
On-site Actions
To identify and correct the problem:
Check the interface setting between UMP (or IMP) and PTP and take actions.
If the alarm is not cleared after 15 minutes, run the INIT-PRC:UMP (or IMP)
command in the CLI window to reset the UPM (or IMP). Check if an alarm is
generated.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
250
Basic Information
Severity CRITICAL
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
The threshold time is exceeded after transition to a holdover state.
Impact
All cell services may not be available.
Remedy
To check the status of the IEEE1588 Grand Master Clock and to take
corrective actions:
Run the RTRV-PTPM-STS command to check the PTPM status and current
Grand Master IP address.
If there are problems with the PTPM or the Grand Master Clock configuration,
run the CHG-PTPM-CONF or the CHG-GM-INFO command to change the
configuration as necessary.
If the problem cannot be solved by changing the PTPM or the Grand Master
Clock configuration, continue to the next step.
251
Run the ping command to check the communication setting and status
between the UMP PTP and the IEEE1588 Master.
10 Check if the PTP packet count on the PTP interface is increasing normally.
11 Check the Grand Master state and check if it is operating normally.
12 Check the network state and quality.
252
Basic Information
Severity CRITICAL
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
This alarm is generated in unlocking 1588 system initialization.
Impact
All cell services may not be available.
Remedy
To check the status of the IEEE1588 Grand Master Clock and to take
corrective actions:
Run the RTRV-PTPM-STS command to check the PTPM status and current
Grand Master IP address.
If there are problems with the PTPM or the Grand Master Clock configuration,
run the CHG-PTPM-CONF or the CHG-GM-INFO command to change the
configuration as necessary.
If the problem cannot be solved by changing the PTPM or the Grand Master
Clock configuration, continue to the next step.
Run the ping command to check the communication setting and status
between the UMP PTP and the IEEE1588 Master.
10 Check if the PTP packet count on the PTP interface is increasing normally.
Samsung MBS(LTE) Alarm Manual for SLR 3.1 v2.0
Samsung Proprietary and Confidential
253
254
Basic Information
Severity MAJOR
Relates to Hardware
Category COMMUNICATIONS
Possible Cause(s)
The quality of the SyncE master clock is lower than the Stratum 2 grade.
Impact
None.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If the QL SELECTED value is not one of the values below, check the SyncE
master status or configuration.
If there are problems with the SyncE master configuration, run the CHGSYNCE-CONF command to change the configuration as necessary.
If the alarm persists, visit the site and perform on-site actions.
255
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
256
Basic Information
Severity CRITICAL
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
IEEE1588 clock module initialization is abnormal.
Impact
All cell services may be not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If the QL SELECTED value is not one of the values below, check the SyncE
master status or configuration.
If there are problems with the SyncE master configuration, run the CHGSYNCE-CONF command to change the configuration as necessary.
257
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
258
Basic Information
Severity MAJOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
Connection to the SyncE master (reference) is abnormal.
Impact
None.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If there are problems with the SyncE master configuration, run the CHGSYNCE-CONF command to change the configuration as necessary.
If the alarm persists, visit the site and perform on-site actions.
259
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
260
Basic Information
Severity CRITICAL
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
One week passes after a SyncE NO_CURRENT_MASTER or a SyncE
NO_CLOCK_REF_SIGNAL occurs.
Impact
All cell services may not be available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If there are problems with the SyncE master configuration, run the CHGSYNCE-CONF command to change the configuration as necessary.
If the alarm persists, visit the site and perform on-site actions.
261
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
262
Basic Information
Severity CRITICAL
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
IEEE1588 clock module initialization is abnormal.
Impact
All cell services may be not available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If there are problems with the SyncE master configuration, run the CHGSYNCE-CONF command to change the configuration as necessary.
If the alarm persists, visit the site and perform on-site actions.
263
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
264
Basic Information
Severity CRITICAL
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
This alarm is generated when the system is initialized by INIT-SYS and it stays in
the unlock status.
Impact
All cell services may not be available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
If there are problems with the SyncE master configuration, run the CHGSYNCE-CONF command to change the configuration as necessary.
265
On-site Actions
To identify and correct the problem:
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
266
Basic Information
Severity CRITICAL/MAJOR/MINOR
Relates to Hardware
Category EQUIPMENT
Possible Cause(s)
A user-defined alarm (UDA) is generated.
Impact
Varies with each UDA.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
In the CLI window, run the INIT-PRC:UMP command to reset the UM P (or
IMP).
If the alarm is cleared, record the current status and observe any reoccurrence.
If the alarm is not cleared, visit the site and perform on-site actions.
267
On-site Actions
To identify and correct the problem:
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 installation manual.
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
door of the enclosure and check if the alarm is cleared.
If the alarm is cleared, record the current status and observe any reoccurrence.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
268
Basic Information
Severity MAJOR
Relates to Hardware
Category ENVIRONMENT
Possible Cause(s)
The actual operation speed is lower than 60 % compared to the target speed
(varying depending on the temperature).
Impact
System cooling is impacted due to a fan failure.
Remedy
On-site Actions
To identify and correct the problem:
Connect to the debug port and check the communication status with the FANC
module. If the communication status with the FANC is not normal, replace the
SDU.
A Harting debug cable with waterproof USB connectors should be used to connect
to the DBG0/DBG1 port of the SDU. The DBG0/DBG1 port of the SDU may
become damaged if a universal USB debugging cable is used. (Debug Cable SEC
code: EP39-01874A)
If the communication with the FANC module is normal, check the fan module
cable. Reconnect the cable if disconnected.
If the alarm is not cleared after taking the described actions, replace the SDU.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
269
Basic Information
Severity MAJOR
Relates to Hardware
Category ENVIRONMENT
Possible Cause(s)
The temperature of the unit is higher than the high threshold.
Impact
Service may not be available.
Remedy
Off-site Actions via LSM Before Site Visit
To collect the LSM log and current status information:
On-site Actions
To identify and correct the problem:
If the cable is not properly connected, reconnect the cable. If the cable is
damaged, replace the cable.
If the cable is properly connected, and there is no damage to the cable, replace
the temperature sensor.
270
If the fan alarm (SYS FAN FAIL) is generated, check the fan status. If the fan
does not operate normally, replace the SDU.
For information about SDU replacement, see the SDU10 Installation Manual or
SDU11 Installation Manual.
271
Basic Information
Severity MAJOR
Relates to Software
Category EQUIPMENT
Possible Cause(s)
The system time cannot be updated due to an incorrect server configuration or to a
lack of connectivity with the NTP server.
Impact
None.
Remedy
To identify and correct the problem:
If the IP address of the NTP server is not configured correctly, run the CHGNTP-CONF command to modify the IP address of the NTP server.
272
Basic Information
Severity CRITICAL
Relates to Software
Category EQUIPMENT
Possible Cause(s)
All cells for the eNB are disabled.
Impact
All cell services are not available.
Remedy
To identify and correct the problem:
If all the cells are locked, run the CHG-CELL-CONF command to change the
cell configuration and unlock the cells.
If the alarm is not cleared, run the RTRV-CELL-STS command to check cell
status.
If the alarm is not cleared after taking the appropriate corrective measures, contact
Samsung.
273
Basic Information
Severity CRITICAL
Relates to Software
Category EQUIPMENT
Possible Cause(s)
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
Service may not be available.
Remedy
To identify and correct the problem:
Check if the failure is caused by a connection problem with the SCTP or with
the S1AP.
If the alarm is not cleared after taking the described actions, contact Samsung.
274
Basic Information
Severity MAJOR
Relates to Software
Category PROCESSING
Possible Cause(s)
There is no response to the paging call transmitted by the eNB call processing
block to the idle UE after TRIGGERING_CONDITION_TIMER of PLD
DIAG_CALL_CONF
Impact
None.
Defaults
The default value of TRIGGERING_CONDITION_TIMER is 1 hour
275
Remedy
To identify and correct the problem:
If an alarm is generated although there is a call connection to the cell, then the
alarm is caused by incorrect operation. Run the CHG-DIAG-CONF command
to change the DIAG_CALL_ENABLE value to OFF.
276
Basic Information
Severity MAJOR
Relates to Software
Category EQUIPMENT
Possible Cause(s)
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
None.
Remedy
To identify and correct the problem:
Check if the failure is caused by a connection problem with the SCTP or with
the S1AP.
If the alarm is not cleared after taking the described actions, contact Samsung
277
Appendix Acronyms
CLI
CPRI
CPU
DDR
DU
ECP
eNB
FPGA
IMP
IP
LNA
LOF
LOS
LSM
LTE
MBS
MME
PLD
PLMN
PTP
RAN
RRH
RSSI
S1AP
SCTP
SDU
SFN
SYNCE
TOD
UAMA
UBMA
UDA
UMP
USB
VSWR
278
Samsung MBS(LTE)
Alarm Manual for SLR 3.1
Document Version 2.0
2014 Samsung Electronics Co., Ltd.
All rights reserved.