Formal CSR Answer

CSR creation 10.04.2019 09:27:50 (CAT)

Ericsson Local Service Organisation

Reference 3526943
Telephone
FAX
Email

Customer
Reference
Contact Person Peter Paul Baale
Telephone 0788312376
FAX
Email PeterPaul.Baale@mtn.com

This is an automated message. You may reply to this e-mail without changes in the subject field. If you have any concerns or any further
Technical background
Network GSM
Service
Customized Service
Node CPP M-MGw 16A
Node Customization/Adaptation
Site GHMGW2
Sub-Product
Severity Low

CSR description:
System Check Detected Problem

CSR Answer

FORMAL ANSWER
=================
----------------------------------------------------
Ericsson Ref:CSR# 3526943
Customer : MTN RW
Ericsson contact: nitin.saini@ericsson.com
Name: Nitin Saini
Telephone: +919582111842
----------------------------------------------------

1.CSR SLOGAN:
--------------------------------
System Check Detected Problem

2.PROBLEM DESCRIPTION:
--------------------------------
After implementation of recommendations from CSR no.3472049 to clear the
alarm, that is reset and replacement of 2 MSBboards to restore the
device pool capacity, the pool capacity was restored but the alarm

This is an automated message. You may reply to this e-mail without changes in the subject field. If you have any concerns or any further
enquiries about this CSR, please contact the Ericsson Support Office.
"System Check Detected Problem" only reduced severity from critical to
minor.

3.Node Info:
--------------------------------
MGW

4i.Summary of investigations:
--------------------------------
As per system check report your concern is related to following
recommendations:
Synchronization status (Runtime:
<1 s) [MINOR ERROR]
MINOR ERROR: System clock is not in LOCKED_MODE state.
REMEDY: Check clock sources according to the User Guide for
Synchronization
WARNING: There is no active clock reference in OK state for system
clock
REMEDY: Check clock sources according to the User Guide for
Synchronization
WARNING: There is no synchronization redundancy. There is no
inactive clock reference in OK state
REMEDY: Check clock sources according to the User Guide for
Synchronization
From the node configuration we could see the following configuration not
reference is defined for synchronization:
========================================================================
=========================================
26 TransportNetwork=1
,Synchronization=1
========================================================================

This is an automated message. You may reply to this e-mail without changes in the subject field. If you have any concerns or any further
enquiries about this CSR, please contact the Ericsson Support Office.
=========================================
SynchronizationId 1
adminQuality i[8] = 16 16 16 16 16 16 16 16
(NOT_DEFINED NOT_DEFINED NOT_DEFINED NOT_DEFINED NOT_DEFINED NOT_DEFINED
NOT_DEFINED NOT_DEFINED)
degradationIsFault 0 (DEGR_NOT_FAULT)
featureStatePtpFreq 0 (DEACTIVATED)
featureStatePtpTime 0 (DEACTIVATED)
featureStateSyncEth 0 (DEACTIVATED)
fixedPosition true
licenseStatePtpFreq 0 (DISABLED)
licenseStatePtpTime 0 (DISABLED)
licenseStateSyncEth 0 (DISABLED)
minQualityLevel 1 (QL_SSU_A)
nodeSystemClock 4 (FREE_RUNNING_MODE)
operQualityLevel i[8] = 21 21 21 21 21 21 21 21
(NOT_DEFINED NOT_DEFINED NOT_DEFINED NOT_DEFINED NOT_DEFINED NOT_DEFINED
NOT_DEFINED NOT_DEFINED)
selectionProcessMode 0 (QL_DISABLED)
sfnInitializationTime 1980-01-06T00:00:19
syncRefActivity i[8] = 1 1 1 1 1 1 1 1 (INACTIVE
INACTIVE INACTIVE INACTIVE INACTIVE INACTIVE INACTIVE INACTIVE)
syncRefPriority i[8] = 0 0 0 0 0 0 0 0
syncRefStatus i[8] = 0 0 0 0 0 0 0 0 (FAILED
FAILED FAILED FAILED FAILED FAILED FAILED FAILED)
syncReference [8] =
>> syncReference =
>> syncReference =
>> syncReference =
>> syncReference =
>> syncReference =
>> syncReference =

This is an automated message. You may reply to this e-mail without changes in the subject field. If you have any concerns or any further
enquiries about this CSR, please contact the Ericsson Support Office.
>> syncReference =
>> syncReference =
telecomStandard 0 (OPTION_I)
useReceivedQl i[8] = 0 0 0 0 0 0 0 0 (FALSE FALSE
FALSE FALSE FALSE FALSE FALSE FALSE)
userLabel

As per ALEX User Guide for Synchronization

3.1 Network Synchronization
There are three main ways of designing a network synchronization
solution. All other designs are a combination of these.
A dedicated network that is based on a dedicated Primary Reference Clock
(PRC)
A non-dedicated synchronization network that is based on traffic links
to carry the reference timing
Asynchronous node that does not require any synchronization references

M-MGw supports all schemes. From a M-MGw point of view, the first
solution uses the dedicated frequency input on the Timing Unit Board
(TUB) board, whereas the second solution uses a port on a SDH or a PDH
ET board to extract the reference frequency. In this document a
synchronization reference connected to a TUB board is referred to as a
TU synchronization reference. Up to eight reference inputs can be
configured with a user-controlled priority. These reference inputs can
consist of any combination of non-dedicated (SDH and PDH ET) and
dedicated (TU synchronization reference) inputs. For redundancy reasons,
at least two reference inputs are mandatory.
The third solution is to have an asynchronous M-MGw node that is
operational without having to register a TU, or a PDH/SDH synchroni
zation reference. In this case the system clock signal is generated by the TUB board.
The frequency accuracy of the node is
decreased from 50 ppb to 4.6 ppm.
Depending on the network synchronization plan, if no synchronization

This is an automated message. You may reply to this e-mail without changes in the subject field. If you have any concerns or any further
enquiries about this CSR, please contact the Ericsson Support Office.
references are registered in a TUB based node, the system clock state is
in "Free running" mode.
Note:

The alarms System Clock Quality Degradation and System Clock in Holdover
Mode are not raised in "Free running" mode.
Synchronization reference based on time stamps carried by Network Time
Protocol (NTP) packets, IP Synchronization Reference (Managed Object
(MO), IpSyncRef) is not supported in the M-MGw.
The electrical reference on the TUB board is a coaxial input. The input
signal frequency can be 2048 kHz, 1544 kHz or 10 MHz. The 2048 kHz input
signal is recommended. Table 1 specifies the signal characteristics.
Table 1 Signal Characteristics
Signal frequency Signal format Signal level Impedance [Ohm]
2048 kHz According to ITU-T G.703 electrical specification According to
ITU-T G.703 electrical specification 75
1544 kHz Sine wave The signal level must be between 0.55Vpp and 1.22Vpp
(+3dBm to +10dBm) 75
10 MHz Sine wave The signal level must be between 0.20Vpp and 3.6Vpp
(-10dBm to +15dBm) 50
The reference frequency jitter and wander characteristic has to comply
to either ITU-T G.812 or G.813 standards.
Note:
1544 KHz and 10 MHz input signals can be used but they are not
recommended. This is because the 1544 KHz input is unframed and American
National Standards Institute (ANSI) requires 1.544 Mbps framed input.
The 10 MHz input is normally only used in conjunction with non-telecom
equipment and therefore this signal often does not fulfill telecom
requirements regarding robustness and reliability.

The M-MGw can also be used as a NS reference source for other telecom
equipment. In this case a traffic carrying SDH/PDH link should be used
to transfer the reference synchronization. The network synchronization

This is an automated message. You may reply to this e-mail without changes in the subject field. If you have any concerns or any further
enquiries about this CSR, please contact the Ericsson Support Office.
cannot be transported over an Ethernet connection.
In the M-MGw the system clock is locked to the primary reference clock
and distributed to all boards through the backplane. If the primary
reference input becomes faulty the system clock will automatically be
locked to the next synchronization reference in the priority list.

4ii.cause of problem:
--------------------------------
Workig as designed

5. Solution Description:
--------------------------------
To clear the alarm either have to have the node connected to a sync ref
(either via TUB or using TDM/ATM connection) or have the alert in the
system check.

6. Recommendation/Way forward (if applicable)

Connect a syn resouce to the node
------------------------------

This is an automated message. You may reply to this e-mail without changes in the subject field. If you have any concerns or any further
enquiries about this CSR, please contact the Ericsson Support Office.