Maintenance

Signaling

MMN:SSNC

A50016-D3104-M470-3-7620
MMN:SSNC Maintenance
Signaling

f Important Notice on Product Safety

Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the
parts may also have elevated operating temperatures.
Non-observance of these conditions and the safety instructions can result in personal injury or in prop-
erty damage.
Therefore, only trained and qualified personnel may install and maintain the system.
The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply
with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit
In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Spannung. Einige Teile
können auch eine hohe Betriebstemperatur aufweisen.
Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverletzungen und
Sachschäden führen.
Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und
wartet.
Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Geräte
müssen die zutreffenden Sicherheitsbestimmungen erfüllen.

Trademarks:
All designations used in this document can be trademarks, the use of which by third parties for their
own purposes could violate the rights of their owners.

Copyright (C) Siemens AG 2005.

Issued by the Communications Group

Hofmannstraße 51
D-81359 München

Technical modifications possible.

Technical specifications and features are binding only insofar as
they are specifically and expressly agreed upon in a written contract.

2 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling

Reason for Update

Summary:
Issue 3

Details:
Issue Chapter/Section Reason for Update

01 First issue

02 LI02 Inserting of missing procedure

02 SW06 Table for variables: MP number becomes Site ID

03 all procedures Particular links to CH:SSNC combined into one link

in the introduction of each procedure;
Explanations to terms ’own’ and ’connected’

03 HW14, HW16, LI02 Fixed value YES for Parameter Hazard check of
CONF ASN/AMX to Admin. State locked

03 DATA:MPU Correction of YES/NO branch for exchange -

specific data (step 3)

03 TM:01 Update for step ’Activate Radio Clock’

Issue History
Issue Date of issue Reason for Update

01 06/04 Issue 1

02 08/04 Issue 2

03 02/05 See above

A50016-D3104-M470-3-7620 3
MMN:SSNC Maintenance
Signaling

4 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling

This document consists of a total of 268 pages. All pages are issue 3.

Contents
1 Introduction (IN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.1 References to Additional Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
PROCIN
2.1 Comments and Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
CH:SSNC
2.2 Communication Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
COMAL
2.3 Temperature Alarm reported by ACCG . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
EY03
2.4 Failures of both MDDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
EY06
2.5 Double Disk Failure on MP(SA*) in F:SCB(E) / SXCB(E) . . . . . . . . . . . . . . 33
EY07
2.6 Faulty Generation File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
GE01
2.7 Simple HW Fault Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
HW01
2.8 Extended HW Fault Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
HW02
2.9 MDD/MOD Fault Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
HW03
2.10 Interface Fault MDD/MOD - MPU(SA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
HW05
2.11 Interface Fault MPU(SA) - MDD/MOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
HW06
2.12 MPU ETHERNET Interface Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
HW07
2.13 Interface Fault MPU(SA) - ALI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
HW08
2.14 Fault in MPU(SA), not System-Verified. . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
HW10
2.15 Fault in MPU(D), not System-Verified . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
HW11
2.16 PLL0 Faults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
HW14
2.17 Clock Source Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
HW15
2.18 Reference Clock Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
HW16
2.19 Statistical Limit for Transient Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
HW17
2.20 Customer-Specific Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
HW19

A50016-D3104-M470-3-7620 5
MMN:SSNC Maintenance
Signaling

2.21 Fuse Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

HW20
2.22 Fan Alarm (top) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
HW21
2.23 Fan Alarm (bottom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
HW22
2.24 ALI Fault. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
HW23
2.25 Inconsistency in ASN (ASN20/ASN40) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
HW30
2.26 Radio Clock Fault. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
HW41
2.27 Cabling Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
HW98
2.28 Nonstandard Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
HW99
2.29 Fault in a Signaling Link Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
LI01
2.30 Fault in a Signaling Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
LI02
2.31 Fault in a Combined Signaling Link Set . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
LI03
2.32 Overload on the Signaling Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
LI04
2.33 GA Signalling Link Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
LI05
2.34 Association Management for SCTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
LI06
2.35 Setting the MPU(SA) Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
DATA:MPU
2.36 Congestion on the Signaling Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
OVERLOAD
2.37 Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
NOTI
2.38 Quality of Service Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
QOSAL
2.39 DPC Not Accessible. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
RO01
2.40 Discarded MSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
RO02
2.41 Security Alarm, Threshold for Security Trace File Reached . . . . . . . . . . . 144
SE01
2.42 Security Alarm, Cannot Write to File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
SE02
2.43 Threshold Value for Log Instance Reached. . . . . . . . . . . . . . . . . . . . . . . . 147
SE03
2.44 Threshold for Occupancy Level of MOD/MDD reached. . . . . . . . . . . . . . . 149

6 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling

SE04
2.45 Simple AMXE Fault Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
SNC02
2.46 Simple MPU Fault Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
SNC03
2.47 Simple LIC Fault Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
SNC04
2.48 Simple ASN Fault Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
SNC06
2.49 ALI Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
SNC07
2.50 Extended AMXE Fault Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
SNC12
2.51 Extended MPU Fault Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
SNC13
2.52 Extended LIC Fault Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
SNC14
2.53 Extended ASN Fault Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
SNC16
2.54 Isolation of the Signaling Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
SP01
2.55 Total CCS7 Outage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
SW01
2.56 Total Outage of (CALLP) NP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
SW02
2.57 Total Outage of Mobile Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
SW04
2.58 SAMAR Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
SW05
2.59 Transfer of SAMAR Data (Multiple File View) . . . . . . . . . . . . . . . . . . . . . . 205
SW05B
2.60 Transfer of SAMAR Data (One File View) . . . . . . . . . . . . . . . . . . . . . . . . 208
SW05C
2.61 MP/Buffer failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
SW06
2.62 HOP Communication failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
SW07
2.63 Software Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
SW99
2.64 Invalid Time and Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
TM01
2.65 Trunk Group Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
TR01

3 TABIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
3.1 Table of L3 and L4 Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
MSG:DISCARD
3.2 Reasons for Discarded MSUs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

A50016-D3104-M470-3-7620 7
MMN:SSNC Maintenance
Signaling

REAS:DISCARD
3.3 Reasons for Signaling Link Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
REAS:LINK
3.4 Recovery Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
REC:SYNCHRON
3.5 SSNC Alarm and Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
ALARM INFO
3.6 Additional Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
3.7 Clock Distribution over MUT 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
CLOCK

8 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling

1 Introduction (IN)
1.1 References to Additional Documentation

• If you are familiar with the basic principles of fault clearance used in this manual, you
can start with fault clearance at once. Otherwise we advise that you read the appro-
priate register in Guide to Documentation in order to be able to make efficient use of
the manual when working on fault clearance. The Documentation Overview contains
detailed information on all general aspects of fault clearance.
• When replacing or handling modules and cables, always observe the regulations
concerning the handling of electrostatic-sensitive devices and the Safety Instruc-
tions for Personal and Products (EN60950/IEC60950).

A50016-D3104-M470-3-7620 9
MMN:SSNC Maintenance
Signaling

10 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling PROCIN

2 Procedures
PROCIN
PROC: CH:SSNC Comments and Hints
PROC: EY03 Temperature Alarm reported by ACCG
PROC: EY06 Failures of both MDDs
PROC: EY07 Double Disk Failure on MP(SA*) in F:SCB(E) / SXCB(E)
PROC: GE01 Faulty Generation File
PROC: HW01 Simple HW Fault Clearance
PROC: HW02 Extended HW Fault Clearance
PROC: HW03 MDD/MOD Fault Clearance
PROC: HW05 Interface Fault MDD/MOD - MPU(SA)
PROC: HW06 Interface Fault MPU(SA) - MDD/MOD
PROC: HW07 MPU ETHERNET Interface Fault
PROC: HW08 Interface Fault MPU(SA) - ALI
PROC: HW10 Fault in MPU(SA), not System-Verified
PROC: HW11 Fault in MPU(D), not System-Verified
PROC: HW15 Clock Source Fault
PROC: HW16 Reference Clock Fault
PROC: HW17 Statistical Limit for Transient Faults
PROC: HW19 Customer-Specific Alarms
PROC: HW20 Fuse Alarm
PROC: HW21 Fan Alarm (top)
PROC: HW22 Fan Alarm (bottom)
PROC: HW23 ALI Fault
PROC: HW30 Inconsistency in ASN (ASN20/ASN40)
PROC: HW41 Radio Clock Fault
PROC: HW98 Cabling Fault
PROC: HW99 Nonstandard Maintenance
PROC: LI01 Fault in a Signaling Link Set
PROC: LI02 Fault in a Signaling Link
PROC: LI03 Fault in a Combined Signaling Link Set
PROC: LI04 Overload on the Signaling Link
PROC: LI05 GA Signalling Link Alarm
PROC: LI06 Association Management for SCTP
PROC: NOTI Notification
PROC: QOSAL Quality of Service Alarm
PROC: OVERLOAD Congestion on the Signaling Link

A50016-D3104-M470-3-7620 11
MMN:SSNC Maintenance
PROCIN Signaling

PROC: RO01 DPC Not Accessible

PROC: RO02 Discarded MSU
PROC: SE01 Security Alarm, Threshold for Security Trace File Reached
PROC: SE02 Security Alarm, Cannot Write to File
PROC: SE03 Threshold Value for Log Instance Reached
PROC: SNC02 Simple AMXE Fault Clearance
PROC: SNC03 Simple MPU Fault Clearance
PROC: SNC04 Simple LIC Fault Clearance
PROC: SNC06 Simple ASN Fault Clearance
PROC: SNC07 ALI Fault
PROC: SNC12 Extended AMXE Fault Clearance
PROC: SNC13 Extended MPU Fault Clearance
PROC: SNC14 Extended LIC Fault Clearance
PROC: SNC16 Extended ASN Fault Clearance
PROC: SP01 Isolation of the Signaling Point
PROC: SW01 Total CCS7 Outage
PROC: SW02 Total Outage of (CALLP) NP
PROC: SW04 Total Outage of Mobile Switching
PROC: SW05 SAMAR Failure
PROC: SW05B Transfer of SAMAR Data (Multiple File View)
PROC: SW05C Transfer of SAMAR Data (One File View)
PROC: SW06 MP/Buffer failure
PROC: SW07 HOP Communication failure
PROC: SW99 Software Errors
PROC: TM01 Invalid Time and Date
PROC: TR01 Trunk Group Alarm

12 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling CH:SSNC

2.1 Comments and Hints

CH:SSNC

1 General notes

– Message controller h ... 2

– Command not executed h ... 3
– ALI h ... 4
– Alarm indications (ALI) h ... 5
– Local or remote operation over LAN using Switch Commander h ... 6
– Self-test h ... 7
– Order of priority in fault clearance h ... 8
– Conditions for replacing MP platform units h ... 9
– Reported / affected module h ... 10
– Under repair bit h ... 11
– Interchange unit h ... 12
– Identical interchange unit h ... 13
– Reactivation h ... 14
– Power failure h ... 15
– Fuse failure h ... 16
– Switch settings h ... 17
– Protective measures h ... 18
– FAN tray and FAN box h ... 19
– Cables h ... 20
– Replacing cables h ... 21
– Replacing FOTE/FOTX modules h ... 22
– Module MPU* h ... 23
– Replacing module M:MPU* h ... 24
– Configuration and replacement of module M:MPU* h ... 25
– Removing/replacing module M:AMXE h ... 26
– Test and diagnosis h ... 27
– Returning faulty modules h ... 28
– Automatic resumption of signaling h ... 29
– Basic F:SCB / SXCB and extended basic F:SCB(E) / SXCB(E) h ... 30
– Deactivation and activation of MPU*(SA) in F:SCB(B) / SXCB(B) h ... 31
– Deactivation and activation of MPU*(SA) in F:SCB(E) / SXCB(E) h ... 32
– MDD and MOD h ... 33
– Failure on both MDDs h ... 34
– Interface fault h ... 35

A50016-D3104-M470-3-7620 13
MMN:SSNC Maintenance
CH:SSNC Signaling

– Cable connector positions h ... 36

– MP(SA) and MP(D) h ... 37
– Administrative states h ... 38
– Operational states h ... 39
– Availability states h ... 40
– Alarm states h ... 41
– Standby states h ... 42
– Diagnosis AMX h ... 43
– MP(SA) and MP(SM) h ... 44
– Display status of units (STAT *) h ... 45
– Alarm / availability state of MPU are inconsistent h ... 46
– Configuration, diagnosis and test of ATMB and AMP h ... 47
– Ethernet fault h ... 48
– Configuration and diagnose ASN h ... 49
– End h ... END
2 Message controller

The message controller should be configured in such a way that all MP platform
messages are output on the network management terminal in the system. h ... 1

3 Command not executed

The cause of a command’s non-execution can be an out-of-range value, an im- h ... 46
permissible change in the operational state, or a change in the operational state
which is not possible in combination with the redundant unit or ... . Repeat the
non-executed command after the cause of non-execution has been cleared.

4 ALI

The configuration and the maintenance for the ALI module is implemented in the
MPU(SA). Therefore the registered state by command STAT ALI is not always
correct.

A change in operational status or a fault in the ALI module is not detected or re-
ported by the system until the next fault message. h ... 1

5 Alarm indications
The LED indicators (CR, MJ, MN) on the faceplate of the ALI module provide the
following additional information:
• CR = critical alarm (failure of a central unit with no redundancy)
• MJ = major alarm (failure of a central unit with redundancy)
• MN = minor alarm (loss of redundancy in the periphery) h ... 1

14 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling CH:SSNC

6 Local or remote operation over LAN using Switch Commander

Local operation using Switch Commander requires the provision of a CT (e.g.

laptop with SC) connected to the corresponding LAN/V.24 interface. Remote op-
eration using SC calls for a connection to be set up to the remote network node
over a LAN interface. Instructions on how to set up a connection can be found in
the Manuals for the Switch Commander. h ... 1

7 Self-test
A self-test is started when a module is inserted in the frame. The progress of the
test is indicated by the LEDs as follows:
• 0 - 0.5 seconds: red and green LEDs on.
• 0.5 - 30 seconds: red LED on, green LED off.
• 30 - 60 seconds: red LED on, green LED flashing.
• 60 - approx. 150 seconds: red LED off, green LED flashing.
The test has been completed successfully if both LEDs are off after about 2.5 ☞ ......Construction
Modules SSNC
minutes. If none of the LEDs lights when the module is inserted, there is proba-
bly a fault in the power supply.

8 Order of priority in fault clearance

If several units have ’failed’, specify the order for clearing the faulty units accord-
ing to priority. If there are ‘redundant pair’ units in the operating state “failed’ and
’degraded’ (e.g.: in a LIC pair, one LIC is in the ‘failed’ state and the other in the
‘degraded’ state), the unit in the ‘failed’ state must be cleared first. Hardware
faults must be cleared before software errors.
The order of priority in fault clearance is:
• MP(SA) in basic frame
• MP(SM)
• MP(SA) in extended basic frame
• MP(D) all dependent MP
• then ASN, AMX, LIC, ATMB (CP) in order of alarm priority h ... 1
9 Conditions for replacing MP platform units

MP platform units are only permitted to be replaced if the Under repair bit is set
for the corresponding unit or if the unit is in state Locked. The Under repair bit
can only be set if the unit is in the error state failed or degraded. h ... 11

10 Reported/affected module

The reported/affected module is the suspect or ’own’ module. The affected mod-
ule is the module connected to the reported unit or ’the connected module’. h ... 1

A50016-D3104-M470-3-7620 15
MMN:SSNC Maintenance
CH:SSNC Signaling

11 Under repair bit

Setting the Under repair bit prevents the alarm status from being changed when ☞ ......46
the module is removed, starts automatic diagnosis when a new module is insert-
ed, and starts automatic activation when diagnosis has been completed without
error. If it is not possible to complete automatic diagnosis without error, the unit
is configured to ‘failed’ without any change being made to the alarm status. The
Under repair bit cannot be displayed. If the Under repair bit is already set, or if
the unit is not in the ’failed’ / ’degraded’ state, the corresponding command will
not be executed.
If the Under repair bit already set, or the unit is not in the ’failed’ / ’degraded’ h ... 1
state the corresponding command will not be executed.

12 Interchange unit

Interchange units are modules, connections (cables) and/or FOTE/FOTX mod-

ules to be exchanged or tested during fault clearance. h ... 1

13 Identical interchange unit

If the same interchange unit is to be exchanged once again as part of fault clear-
ance, nonstandard maintenance must be initiated. h ... 1

14 Reactivation

Reactivation of a unit can take up to five minutes (MPU up to 20 minutes). At

least this period must be allowed to elapse before any other actions are per-
formed after replacing a module. The green LED on the module faceplate flash-
es throughout the processor’s load time. h ... 25

15 Power failure

If a power failure occurs when a new module is inserted, this module must be
removed again immediately. Insert a new module after checking the corre-
sponding fuse. h ... 1

16 Fuse failure

If a new fuse fails (short circuits) on being inserted, determine and clear the
cause before inserting yet another fuse, or initiate nonstandard maintenance. ☞ ......Construction
Rack SSNC

h ... 1

16 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling CH:SSNC

17 Switch settings

When interchanging modules, existing jumper or switch settings for the module
previously inserted in the mounting unit may need to be adopted for the new
module. h ... 1

18 Protective measures

The ESD precautionary measures must be complied with when removing and
inserting modules. h ... 1

19 FAN tray and FAN box

Before replacing a FAN tray or FAN box, units located underneath must be cov-
ered to protect them against parts falling on them from above (e.g. washers).
Voltage-carrying cables must be protected against contact on being disconnect-
ed. h ... 1

20 Cables

Appropriate safety measures must be observed when disconnecting/contacting

cable connections as part of fault clearance. Uncovered cable connectors must
be protected against contact with other conducting parts. h ... 21

21 Replacing cables

Replacement of the cables is not dealt with in this MMN. However, the cables
and cable connectors can be visually inspected with reference to the CLL (cable
laying list) for correct, secure positioning of the connectors and for checking the
cable type used. If a fault is detected during the check and if it can be cleared,
the affected interface has to be tested. This is done by configuring the reported
unit to Locked and then activating it (state Unlocked). The Under repair bit is re-
set once a test finds no errors.
Cables/FOTE/FOTX modules can only be removed with special tools. ☞ ...... 36
h ... 1
22 Replacing FOTE/FOTX modules

Cables/FOTE/FOTX modules can only be removed with special tools. This activ-
ity therefore belongs to the domain of nonstandard maintenance. After replace-
ment of a FOTE module, the affected interface has to be tested. This is done by
configuring the reported unit to Locked and then activating it (state Unlocked).
The Under repair bit is reset if no errors are detected. h ... 1

A50016-D3104-M470-3-7620 17
MMN:SSNC Maintenance
CH:SSNC Signaling

23 Module MPU*

Q-No MPU* as MPU

Q85 MPUD MPU(SA) (1GB)
Q208 MPUD MPU(SA) (10/100 Mbit/s)
Q202 MPUD MPU(D) (1GB)
h ... 24
24 Replacing module M:MPU*
When replacing module M:MPU*, make sure the new module is compatible with
the module which is still active. If a module compatible with the active MPU is
unavailable, replace both M:MPU*s. The new modules have to be mutually com-
patible. Modules that are not mutually compatible are detailed in an incompati-
bility list provided by Development/Manufacturing. To be sure that modules in an
MP are compatible, only combine modules that are not included in the list. Dif-
ferent code numbers indicate possible incompatibility. If this rule is not ob-
served, synchronization errors may occur over XLink. The MP cannot be
activated. If, for reasons of compatibility, both MP modules are replaced, only
the faulty (reported) module should be returned for repair.
Replacing both MPU*s in an MP is only possible as a nonstandard maintenance
procedure. As this procedure cannot be carried out without a failure of signaling
links or a system outage, both M:MPU* modules should be replaced at a time of
low traffic volume.
In cases where both MPU(SM)s are replaced, the status of the signaling links ☞ ......25
cannot be guaranteed after 10 minutes.
After replacement of module MPU(SA) in basic frame check the office data of ☞ ......DATA:MPU
MPU.

25 Configuration and replacement of the MPU*

An MPU module may only be extracted (again) if a manually started configura-
tion job or automatic reactivation after insertion of a module has been complet-
ed.
An MPU may also only be configured if automatic reactivation after insertion of a
module has been completed.
If these warnings are disregarded, the system performance may be affected,
and this can even cause a total failure in the case of MP(SA).
Depending on the type of MPU concerned, activation can take up to 15 minutes.
If there is any doubt, check the status of the MPU by means of a command be-
fore carrying out further actions.
• Reactivation is not yet complete if:
– the Admin. State=unlocked and
– the Operational State=disabled and
– no value has been entered yet for the Availability State. ☞ ......44
h ... 1

18 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling CH:SSNC

26 Removing/replacing module M:AMXE

If it is necessary to remove/replace an AMXE module during a maintenance pro-

cedure, it must be configured to Locked before being removed and configured
back to Unlocked after the (new) module has been inserted and connected. h ... 1

27 Test and diagnosis

If a unit is in the error state failed or degraded and if the Under repair bit is set, a
module is reactivated when it makes contact. As a result, a diagnosis of the af-
fected unit is performed. If the diagnosis detects no faults, the unit is reconfig-
ured to active. If a fault is detected, however, the current state is maintained. If a
unit is in state Locked, no diagnosis is carried out after a module has made con-
tact. Diagnosis is only performed for configuration to Unlocked. h ... 1

28 Returning faulty modules

Faulty modules should only be returned for repair in the containers provided for
this purpose. Diagnosis results and fault descriptions must be enclosed with the
modules. If, for reasons of compatibility, both modules of an MP were replaced,
they should be returned for repair. h ... 1

29 Automatic resumption of signaling

The status of signaling links, signaling link sets and signaling points is periodi-
cally checked and corrected by an audit. If the audit finds an active signaling
link, signaling link set or signaling point that has not yet been reported as active,
the audit sends an “end-of-failure” message to report this fact. The end time
stated in these messages does not correspond to the actual time of reactivation,
but is the current audit time. h ... 1

30 Basic F:SCB(B) / SXCB(B) and extended basic F:SCB(E) / SXCB(E)

The basic frame is a basic part of SSNC. The extended basic frame is only nec- ☞ ...... 31
essary, if the capacity of MDD in basic F:(SCB(B) / SXCB(B)) is not sufficient.
☞ ...... 32
31 Deactivation and activation of MPU(SA) in F:SCB(B) / SXCB(B)
System operation is no longer possible if both MPU(SA)s are deactivated (both
! MPUs of the MP = 1).

A50016-D3104-M470-3-7620 19
MMN:SSNC Maintenance
CH:SSNC Signaling

If it is necessary to deactivate an MPU(SA) during a maintenance procedure,

any MDD/MOD connected to this MPU must be deactivated first. When they are
reactivated, the MPU must be activated first, and then the connected
MDD/MOD.
The activation of MDD is only possible with Label=Yes.
If none of the MDDs/MODs has been replaced, the MDDs must be activated
with Label=No. The MMD/MOD has been replaced must be activated with La-
bel=Yes.

☞ ......44
h ... 33
32 Deactivation and activation of MPU(SA) in F:SCB(E) / SXCB(E)
System operation is no longer possible if both MPU(SA)s are deactivated (both
! MPUs of the MP =..).

If it is necessary to deactivate an MPU(SA) during a maintenance procedure,

any MDD/MOD connected to this MPU must be deactivated first. When they are
reactivated, the MPU must be activated first, and then the connected MDD/MOD
and then the connected MDD / MOD.
If none of the MDDs/MODs has been replaced, the MDDs must be activated
with Label=No. The MMD/MOD has been replaced must be activated with La-
bel=Yes.

☞ ......44
33 MDD and MOD

When replacing the MDD/MOD care must be taken that the MDD/MOD connect-
ed to an MPU is also deactivated. This prevents write or read errors on the oth-
erwise still active MDD/MOD when removing/inserting the MDD/MOD. However,
this is not necessary if the appropriate MPU has to be deactivated beforehand.
After replacement, the new MDD/MOD must be activated with Label=Yes. When
replacing an MOD, make sure that the write protection is removed from the new
MOD. If the write protection is not removed, it is not possible to reactivate the
MOD.

Before start another action, wait of the update reports for the activated MDD. h ... 34

20 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling CH:SSNC

34 Failure of both MDDs

If a failure occurs on both MDDs, then start the fault clearance procedure EY06
first, before starts the procedures HW03, HW05 or HW06.
During a fault on both MDD’s it is not possible to configure, create, delete any
MPU or to enter any patches. Otherwise the command REP DDISKOUT can not
be executed, because the snapshot data and the MP data are not compatible
any more.
After the repair of an failure on both MDD the configuration of the first MDD to h ... 1
unlocked is only with LABEL=YES possible.You should first check which MDD
contains data might be necessary to produce a new valid APS generation or
might provide information for fault clearance (error symptom saving) before you
start clearance the fault. This MDD should not be formatted DIAG/CONF (LA-
BEL=YES) because this would destroy all data on the MDD. The MDD with
these important data should always be replaced. Then is should be kept ready
for error symptom saving or to produce a valid APS generation.

35 Interface fault

For an interface fault, the sequence of the suspect modules or those to be re-
placed is given in the fault report. Usually, the reporting unit is replaced first fol-
lowed by the affected/connected unit. If the fault is not cleared after a module
has been replaced, i.e. the same fault pattern still exists, then the module which
was replaced last can be reinserted or remain inserted according to customer-
specific requirements. ☞ ...... 36
h ... 1
36 Cable connector positions
When there is an interface fault, the fault report only identifies the affected sub- h ... 20
unit, and does not give any direct indication of which cable or cable connector
positions are affected by this fault (see CLL cable laying list).

37 MP(SA) and MP(D)

MP(SA) (MP=1) refers to the main processor that provides the interfaces to
MDD/MOD, SC and ALI. Without MP(SA) it is not possible to communicate with
the MP platform. The OAM function is implemeted in the MP(SA), therefore is
also named MP:OAM.

MP(D) ’dependent’ refers to all main processors that are dependent on the
MP(SA). These processors can be set to function as MP(PD), MP(MM),
MP(RANAP), MP(CAP), MP(ACC), MP(SLT), MP(SM), MP(STATS) by loading
the appropriate software. ☞ ...... 44
h ... 1

A50016-D3104-M470-3-7620 21
MMN:SSNC Maintenance
CH:SSNC Signaling

38 Administrative states
• Locked
– the unit has been configured to ’locked’ by means of a command and is
consequently not available for call traffic.
• Unlocked
– the unit has been configured to ’unlocked’ by means of a command and is
thus available for call traffic.
• Shutting down
– the task requested by a user will be executed before the configuration to h ... 1
’locked’ is executed.

39 Operational states
• Enabled,
– the unit is installed and available
• Disabled,
– the unit is installed but not available

Operator information: Only in case of oper. state=enabled the standby status

shows the correct value standby status=providing service. In some other case is
does not generate very suitable response. ☞ ......42
☞ ......45
h ... 1
40 Availability states
• Failed,
– the unit is faulty
• Degraded,
– the unit is partially faulty
• Dependency,
– the unit is not available due to the state of a higher-ranking unit
• In test,
– the unit is undergoing a test
• Power off,
– the unit is not being supplied with power
• Off line,
– the unit is not loaded
• Off duty
–
• Not installed,
– the unit is not loaded h ... 1

22 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling CH:SSNC

41 Alarm states
• Cleared,
– there is no alarm reported for this unit
• Major,
– a major alarm has been raised for this unit
• Critical,
– a critical alarm has been raised for this unit
• Minor,
– a minor alarm has been raised for this unit
• Under repair,
– the ’under repair’ bit has been set for this unit
• Empty set,
– for this unit there are no unprocessed alarms, nor is it under repair
• Alarm outstanding,
– at least one reason for a possible alarm has been detected h ... 1
42 Standby states
• Hot standby,
– the unit is loaded and is synchronized with the active unit
• Cold standby,
– the unit must be loaded before it can assume a standby function
• Providing service,
– the unit is active and acting as master

Operator information: Only in case of oper. state=enabled the standby status

shows the correct value standby status=providing service. In some other case is
does not generate very suitable response. ☞ ...... 39
☞ ...... 45
h ... 1
43 Diagnosis AMX
Ports 34 and 38 of the AMX in the basic frame are short-circuited in order to h ... 1
check MP > ASIC. The diagnosis of the AMX in the basic frame reports the
ports to be non-testable. This is not an error.

44 MP(SA) and MP(SM)

The two system-relevant main processors are installed in the basic frame. The
MP(SA) also MP:OAM is always addressed as MP=1 (MPU via side=0/1) and
the MP(SM) as MP= 2 (MPU via side=0/1). h ... 1

A50016-D3104-M470-3-7620 23
MMN:SSNC Maintenance
CH:SSNC Signaling

45 Display status of units (STAT *)

Operator information: Only in case of oper. state=enabled the standby status h ... 1
shows the correct value standby status=providing service. In some other case is
does not generate very suitable response. Is the oper. state=disabled, then is
the value standby state not relevant (X731).

46 MPU Alarm- / Availability Status inconsistent

If HW faults occur during an overload situation in the system, inconsistencies
may occur between the alarm and availability status of the units concerned.
As a result it can happen that
• an MPU alarm (Critical/Major/Minor) is indicated, but the MPU is not faulty (in
this case the UR bit cannot be set for this MPU, the command is not execut-
ed).
• an MPU is faulty and no alarm (cleared) is indicated.
The inconsistent statuses can be cleared by means of NM:SSNC ALARM:MPU. ☞ ......NM:SSNC
ALARM:MPU
h ... 1
47 Configuration, diagnosis and test of ATMB and AMP
Both AMP’s of one ATMB represent a redundancy pair. The active AMP transfers
the message. The redundant is standby and transfers no messages. The AMP’s
working not micro synchronously. Occurs a switch over for the AMPs, messages
might get lost. For the following commands a switch over is possible:
• COM AMP
• CONF AMP (act AMP to MBL/locked)
• PRUE AMP
• CONF ATMB (act ATMBU to MBL/locked) h ... 1
48 Ethernet fault
’ping’ is not an system specific command, but it can be used to determine the h ... 1
fault location. Necessary for this command is to know the IP addresses of the
HUBs and MPU.

49 Configuration and diagnose ASN

Different values for parameter ACCG for ASN20 / ASN40 and ASN5.
• set the parameter ACCG=2 for ASN20 / ASN40
• set the parameter ACCG=1 for ASN5 h ... 1

END

24 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling COMAL

2.2 Communication Alarm

COMAL

1 Trouble description and hints

A communication alarm is an indication of abnormal system behavior which may

also interfere with the system performance. The faults concerned are usually
not to be found in the exchange sending the alarm but in one of the adjacent ex-
changes. Communication alarms are spontaneous messages that are displayed
in the surveillance. Normally no further action is necessary. Therefore no entry
to the maintenance manual is provided.
Action may be necessary for the following communication alarms:
– Probable Cause: Loss of signal h ...PROC: LI02
– Probable Cause: Far end received error h ...PROC: LI02
– Probable Cause: Alarm indication signal (AIS) h ...PROC: LI02

END

A50016-D3104-M470-3-7620 25
MMN:SSNC Maintenance
EY03 Signaling

2.3 Temperature Alarm reported by ACCG

EY03

General notes
This procedure may only be carried out by appropriately trained TAC personnel.
i
The temperature sensor connected to the ALI detected an excessive temperature and
was reported by the ACCG. An interruption of the indication line from the sensor to the
ALI is also evaluated as a temperature alarm.
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Decision block

Were faulty fan units also reported beforehand? Y h ... 3

N h ... 2

2 Decision block
Was a faulty ACCG reported? Y h ... 3
N h ... 7

3 Preparation the fault clearance on-site

Provide the modules/units that are reported in the error message and are given
in the fault clearance procedure.
Start the fault clearance on-site. h ... 4
4 Decision block
Was a very high temperature noticed on entering the rooms or after opening the
doors of the rack? Y h ... 6
N h ... 5

5 HW fault
The faulty HW must be cleared according to the failure message. h ...PROC: PRO-
CIN

6 HW fault
Start the repair actions only for system relevant units, e.g. Fan/Box Tray and
MDD, MP, MOD, AMX, ASN without redundancy.
Wait until the temperature is normal again, before taking in service units that are h ...PROC: PRO-
defective/out of service but not system relevant CIN

26 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling EY03

7 Preparation the fault clearance on-site

Provide the modules/units that are reported in the error message and are given
in the fault clearance procedure.
Start the fault clearance on-site. h ... 8
8 Decision block
Was a very high temperature noticed on entering the rooms or after opening the
doors of the rack? Y h ... 9
N h ... 10

9 Temperature Alarm
Provide additional ventilate, e.g. open the doors.
Wait until the temperature is normal again, before taking in service units that are h ... END
defective/out of service but not system relevant.

10 Indication line
Check sensor temperature indication line ALI.
Was a fault detected? Y h ... 11
N h ... 12

11 Decision block
Could the fault be cleared? Y h ... END
N h ... 12

12 Special fault clearance

The fault could not be cleared with standard fault clearance. h ...NM:SSNC

END

A50016-D3104-M470-3-7620 27
MMN:SSNC Maintenance
EY06 Signaling

2.4 Failures of both MDDs

EY06

General notes and fault description

This procedure may only be carried out by appropriately trained TAC personnel.
i
Both MDDs that are connected to the MP (SA) (MP=1) are faulty or are no longer acces-
sible. This may be due to failure of an MDD and a redundant MPU. The fault should be
cleared as quickly as possible.
Only the MDD that failed last can be activated on MPU side 0 or 1 with LABEL=NO. A
new MDD or the MDD that failed first can only be activated with LABEL=YES because
the timestamp (MPU/MDD) does not match.
During a double disk failure, do not configure an MPU to locked and do not cancel an
MPU. Otherwise it will not be possible to execute the command REP DDISKOUTMDD
because when the MP data are compared with the snapshot data they do not match.
Before starting REP DDISKOUTMDD, check the actual state of the MPs. Use not the
command REP DDISKOUTMDD if any MPU(D) has changed its operational state to dis-
abled after the double disk outage occurred. The data snapshot would fail and the Star-
tup-Generation would be lost. Start a nonstandard maintenance
Before fault clearance, find out which MDD failed last (current timestamp). Do not format
this MDD (i.e. do not use LABEL=YES) during the fault clearance procedure, because
you would lose all the data on the MDD. Even if diagnosis shows no faults, this MDD
must be replaced and sent in for subsequent data backup or kept ready, or re-activated
as the first MDD with LABEL=NO (possibly after re-connection to a fault-free MPU).
During fault clearance, make sure that both MPUs (SA) do not fail.
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Determine MPU state

Determine the operational states of all MPUs

b STAT MP; h ... 2

2 Operator error: decision block
Was a fault-free MDD pulled by mistake (redundant MPU/MDD in locked/failed?) Y h ... 3
N h ... 4

28 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling EY06

3 Operator error: re-connect MDD

Re-connect the MDD that was pulled by mistake
b CONF MDDMP:MP=1,Side=..,Administrative State=unlocked,Label=No
Is the MDD active again? Y h ... 8
N h ... 6

4 Operator error: decision block

Was a fault-free MPU pulled by mistake (redundant MPU/MDD in locked/failed?) Y h ... 5
N h ... 9

5 Operator error: re-connect MPU

Re-connect the MPU that was pulled by mistake
Are the MPU and the MDD active again? Y h ... 6
N h ... 8

6 Decision block
b STAT MP;
Has any MPU(D) changed the operational state after the double disk outage? Y h ...NM:SSNC
N h ... 7

7 Operator error: update system files

Update the reactivated MDD with the data in the MPU memory.

REP DDISKOUTMDD
Wait for the MDD to be updated
Was the MDD updated again without faults? Y h ... 29
N h ... 8

8 Operator error: error

The operator error is now a double error h ... 9

9 LABEL=NO: decision block

Find out which MDD failed last (current time stamp)
Is this MDD faulty (failure message)? Y h ... 17
N h ... 10

10 LABEL=NO: decision block

Have you already tried to activate this MDD on both MPUs? Y h ... 17
N h ... 11

A50016-D3104-M470-3-7620 29
MMN:SSNC Maintenance
EY06 Signaling

11 LABEL=NO: decision block

Is/are the necessary MPU(s) active? Y h ... 14
N h ... 12

12 LABEL=NO: activate the MPU

Is the necessary MPU faulty? Y h ... 13
N h ... 17

13 LABEL=NO: activate the MPU

Replace the faulty MPU
Wait for the MPU to be reactivated
Was the MPU reactivated without faults? Y h ... 14
N h ... 10

14 LABEL=NO: activate the MDD

Replace the MDD on this MPU (connect MDD with valid timestamp)
b CONF MDDMP:MP=1,Side=..,Administrative State=unlocked,Label=No;
Was the MDD activated without faults? Y h ... 15
N h ... 10

15 Decision block
b STAT MP;
Has any MPU(D) changed the operational state after the double disk outage? Y h ...NM:SSNC
N h ... 16

16 LABEL=NO: update the system files

Update the reactivated MDD with the data in the MPU memory.

REP DDISKOUTMDD;
Wait for the MDD to be updated
Was the MDD updated again without faults? Y h ... 29
N h ... 8

17 LABEL=YES: information block

The double disk failure is caused by a hardware fault. It does not matter in this
case whether an MDD / MPU was blocked beforehand by means of a command,
because this previously deactivated MDD can only be reactivated with LA-
BEL=YES. The MDD with the current timestamp that failed last could not be re-
activated on any of the available MPUs. This MDD must be kept ready for
symptom saving. h ... 18

30 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling EY06

18 LABEL=YES: RSET INPLOG

Before activating the first MDD with LABEL=YES you must reset the LOG func-
tion so that no new LOG file can be created without a master file.

b RSET INPLOG; h ... 19

19 LABEL=YES: decision block
Connect a new MDD to an active MPU
b CONF MDDMP:MP=1,Side=..,Administrative State=unlocked,Label=Yes;
Was the MDD reactivated? Y h ... 25
N h ... 20

20 LABEL=YES: decision block

Have you already tried to activate a new MDD on both MPUs? Y h ... 32
N h ... 21

21 LABEL=YES: decision block, MPU faulty

Is the (redundant) MPU faulty? Y h ... 22
N h ... 23

22 LABEL=YES: reactivate the MPU

Replace the faulty MPU
Was the MPU reactivated without faults? Y h ... 19
N h ... 32

23 LABEL=YES: decision block, MPU locked

Is the MPU locked? Y h ... 24
N h ... 19

24 LABEL=YES: activate the MPU

Replace the faulty MPU
b CONF MP:MP=1,Side=..,Admin. state=Unlocked;
Was the MPU reactivated without faults? Y h ... 19
N h ... 32

25 Prepare for symptom saving

The replaced MDD must be made available for symptom saving. h ... 26
26 Prepare for recovery from backup medium: decision block
Is an active MOD available?
Please insert MO! Y h ... 28
N h ... 27

A50016-D3104-M470-3-7620 31
MMN:SSNC Maintenance
EY06 Signaling

27 Prepare for recovery from backup medium: activate MOD

Activate the MOD on the active MPU side.
b CONF MODMP:Side=..,Administrative State=unlocked; h ... 28
28 Prepare for recovery from backup medium
An MDD has been reactivated with LABEL=YES.

For restoring the APS and post-processing

– MP h ...EMCYMN
EY504
After the system side that failed first or last has been restored, fault clearance h ...PROCIN
can now be carried out on the redundant system side.
After the APS has been successfully restored and the fault clearance of the re- h ...DATA:MPU
dundant MDD / MPU is finished, check the ’Office Data’ of MPU(SA) in case of
an MPU(SA) replacement.

29 Decision block
b STAT INPLOG;
Is the input log file ’disabled’? Y h ... 30
N h ... 31

30 Reset and open a new log file

b RSET INPLOG;
b SET INPLOG:Log file name=..,Swap file size=..; h ... 31
31 Clear faults on the redundant MDD
After the system side that failed first or last has been restored, fault clearance h ...PROCIN
can now be carried out on the redundant system side.
After the APS has been successfully restored and the fault clearance of the re- h ...DATA:MPU
dundant MDD / MPU is finished, check the ’Office Data’ of MPU(SA) in case of
an MPU(SA) replacement.
After the fault clearance of the redundant MDD an advance quarterly APS sav- h ...MMN:SW
ing is necessary. SW210

32 Special fault clearance

It was not possible to reactivate an MDD on either system side. h ...NM:SSNC

END

32 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling EY07

2.5 Double Disk Failure on MP(SA*) in F:SCB(E) / SXCB(E)

EY07

General notes and description of faults

This procedure may only be carried out by suitably trained TAC personnel.
i
Both MDDs (OAMD) that are connected to the MP(SA) are faulty or are no longer ac-
cessible. This may be due to failure of an MDD and a redundant MPU. The fault should
be cleared as quickly as possible.
It can be assumed that the MDD that failed last, due to failure of an MPU, still contains
(current) data. Do not activate this MDD with LABEL=YES.
An MDD (OAMD) can be activated at any time with LABEL=NO. The relevance of the
data on the MDD depends on how long the MDD has been out of service.
If you do not succeed in reactivating either of the current MDDs, you must insert a new
MDD. If this is an MDD with a backup status of the AMA data, the MDD can be activated
with LABEL=NO.
An MDD of ’unknown origin’ should always be activated with LABEL=YES (when the
MDD is activated with LABEL=YES the content of the MDD is erased - the AMA data
are lost as far as the last backup).
AMA data are also lost if the AMA buffers in the memory overflow and cannot be stored
on the MDD (because it is still not accessible).
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Operator error: decision block

Was a fault-free MDD pulled by mistake (redundant MPU / MDD in ’locked’ /

’failed’?) Y h ... 2
N h ... 3

2 Operator error: connect MDD

Re-connect the MDD that was pulled by mistake
b CONF MDDMP:MP=..,Side=..,Administrative State=unlocked,Label=No;
Is the MDD active again? Y h ... 5
N h ... 6

3 Operator error: decision block

Was a fault-free MPU pulled by mistake (redundant MPU / MDD in ’locked’ /
’failed’?) Y h ... 4
N h ... 7

A50016-D3104-M470-3-7620 33
MMN:SSNC Maintenance
EY07 Signaling

4 Operator error: re-connect MPU

Re-connect the MPU that was pulled by mistake
Are the MPU and the MDD active again? Y h ... 5
N h ... 6

5 Operator error: update system files

Wait for the MDD to be updated
Was the MDD updated again without faults? Y h ... 23
N h ... 6

6 Operator error: error

The operator error is now a double error h ... 7

7 LABEL=NO: decision block

Find out which MDD failed last
Is this MDD faulty (failure message)? Y h ... 14
N h ... 8

8 LABEL=NO: decision block

Have you already tried to activate this MDD on both MPUs? Y h ... 14
N h ... 9

9 LABEL=NO: decision block

Is / are the necessary MPU(s) active? Y h ... 12
N h ... 10

10 LABEL=NO: activate the MPU

Is the necessary MPU faulty? Y h ... 11
N h ... 14

11 LABEL=NO: activate the MPU

Replace the faulty MPU
Wait for the MPU to be reactivated
Was the MPU reactivated without faults? Y h ... 12
N h ... 8

34 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling EY07

12 LABEL=NO: activate the MDD

Replace the MDD on this MPU
b CONF MDDMP:MP=..,Side=..,Administrative State=unlocked,Label=No;
Was the MDD activated without faults? Y h ... 13
N h ... 8

13 LABEL=NO: update the system files

Wait for the MDD to be updated
Was the MDD updated again without faults? Y h ... 23
N h ... 8

14 LABEL=NO: decision block

Could the redundant MDD be activated (e.g. because it was ’locked’ before-
hand) Y h ... 8
N h ... 15

15 LABEL=YES: information block

The double disk failure is caused by a hardware fault. h ... 16

16 LABEL=YES: decision block

Connect a new MDD to this MPU / an active MPU
b CONF MDDMP:MP=..,Side=..,Administrative State=unlocked,Label=Yes;
Was the MDD reactivated? Y h ... 22
N h ... 17

17 LABEL=YES: decision block

Have you already tried to activate a new MDD on both MPUs? Y h ... 24
N h ... 18

18 LABEL=YES: decision block, MPU faulty

Is the (redundant) MPU faulty? Y h ... 19
N h ... 20

19 LABEL=YES: reactivate the MPU

Replace the faulty MPU
Was the MPU reactivated without faults? Y h ... 16
N h ... 24

A50016-D3104-M470-3-7620 35
MMN:SSNC Maintenance
EY07 Signaling

20 LABEL=YES: decision block, MPU locked

Is the MPU locked? Y h ... 21
N h ... 16

21 LABEL=YES: activate the MPU

Replace the faulty MPU
b CONF MP:MP=..,Side=..,Admin. state=Unlocked;
Was the MPU reactivated without faults? Y h ... 16
N h ... 24

22 Prepare for recovery from backup medium

An MDD has been reactivated with LABEL=YES.

For post-processing of the AMA data h ...EMCYMN

EY504
After the system side that failed first or last has been restored, fault clearance h ...PROC: PRO-
can now be carried out on the redundant system side. CIN

23 Clear faults on the redundant MDD

After the system side that failed first or last has been restored, fault clearance h ...PROC: PRO-
can now be carried out on the redundant system side. CIN

24 Special fault clearance

It was not possible to activate an MDD on either system side. h ...NM:SSNC

END

36 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling GE01

2.6 Faulty Generation File

GE01

This procedure may only be executed by suitably trained TAC personnel.

i

1 General remarks and description of faults

A faulty system file has been discovered in an active/loaded generation. If a

generation on the system disk contains a faulty file, the generation is ’disabled’
and an alarm is sent. No alarm is issued for a faulty archive generation on MOD.
’Critical’ alarm is issued for a faulty active generation (on Boot Area Position 0)
’minor’ alarm is issued for a faulty fallback generation (on Boot Area Position 1)
and a ’warning’ alarm is issued for all other fallback generations, and the faults
are reported with MMN:SSNC, SW500 (GE01).
The faulty file is specified in EVENT INFORMATION.
((additionalInformation(identifier corruptFileNameParameter, information
KSQASCOC.FileName:”...........”)))
The alarm category (critical/minor/warning) indicates whether the loaded gener-
ation is involved: ’EVENT INFORMATION perceivedSeverity=critical’.
This procedure can be used to repair files belonging to the loaded generation. If
files from the fallback generations are involved, these can only be corrected by
producing a new fallback generation.
In case of double disk failure (EY06) this alarm will be set additionally. The
alarm is reset after the fault clearance of MDD and an update of MDD from the
MPU memory with the command REP DDISKOUTMDD.

For further information see also ☞ ......PROC:

CH:SSNC

h ... 4
2 Decision block
Was the ’critical’ alarm set in addition to a double disk failure (EY06)? Y h ... 3
N h ... 4

3 Double disk failure

The alarm is reset after the reactivation of the first MDD and an update of MDD h ...PROC: EY06
from the MPU memory with the command REP DDISKOUTMDD.

4 Decision block
Was a ’critical’ alarm set? Y h ... 6
N h ... 5

A50016-D3104-M470-3-7620 37
MMN:SSNC Maintenance
GE01 Signaling

5 Minor alarm or Warning

A faulty file was detected in a fallback generation. The fallback generation can-
not be repaired, and a new fallback generation must be produced.
To produce a new fallback generation, carry out the next scheduled save now
with the appropriate settings.
– For saving use: h ...MMN:SW
SW210

6 Decision block

A faulty file was detected in the loaded generation

The following files can be repaired:

– Code files SY.MPULIB, SY.AMXLIB, SY.ASNLIB or SY.LICLIB h ... 7
– Data files DBMS.DA.* h ... 8
– TRANSLOG file h ... 9
7 Repairing the code files

The following code files can be repaired: SY.MPULIB, SY.AMXLIB, SY.ASNLIB

or SY.LICLIB

b REP CODEFILE:Device Name=..,Code generation=..,Code file=..;

Device Name =MDD, MOD1, MOD0
Code generation=Enter the APS name here
Code file=Enter the faulty code file here
Post-processing: Check the patch statuses and if necessary import the missing h ... END
patches in accordance with the instructions provided.

8 Repairing DATA files

DATA files are all files with the stem DBMS.DA.*. The DATA files of the current
generation can be repaired with the following command.

b REP DATFILES; h ... END

38 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling GE01

9 Repairing the TRANSLOG file

The SY.TRANSLOG file of the current generation can be repaired by means of

the command specified below. In this process a new generation is produced (on
Boot Area Position 1) and this then has to be loaded by means of a LOAD
REC3. LOAD REC3 is carried out with REST GENMP.

b REP TRANSLOG:New generation=..,Device Name=..,Code generation=..;

Starting a LOAD REC3
– adjustment of the generation and post-processing is done for MP with i ...EMCYMN
EY190

After a successful LOAD REC3 and the corresponding post-processing h ... 10

10 Producing a new fallback generation

Since the previously up-to-date fallback generation (from Boot Area 1) has been
shifted to Boot Area 2 by means of REP TRANSLOG , after successful repair of
the TRANSLOG file a new fallback generation has to be generated.

To generate a fallback generation on Boot Area 1, carry out the next scheduled
save now with the appropriate settings.
– For saving use: h ...MMN:SW
SW210

END

A50016-D3104-M470-3-7620 39
MMN:SSNC Maintenance
HW01 Signaling

2.7 Simple HW Fault Clearance

HW01

1 General notes and fault description

If a number of units have failed, the order in which they are cleared must be de-
fined in accordance with the priority of the faults. If there are redundant units in
operating state failed/degraded, the unit in failed must be cleared first.

For further information see also ☞ ......PROC:

CH:SSNC

h ... 3
2 Check of PLL0 lock error on ACCG
Check alarm message: Is any ACCG with ’probably cause=equipment malfunc-
tion’ and with ’specific problem=non severe hardware fault’ detected? Y h ...PROC: HW14
N h ... 3

3 Decision block
Was a ’SporadicFaultsOverflow’ reported for the failed unit? Y h ...PROC: HW17
N h ... 4

4 Decision block
Was a total CCS7 outage also reported with the failure of the unit? Y h ...PROC: SW01
N h ... 5

5 Decision block
Was a total CALLP outage also reported with the failure of the unit? Y h ...PROC: SW02
N h ... 6

6 Decision block
Was a TOTAL OUTAGE OF MOBILE SWITCHING also reported with the failure
of the unit? Y h ...PROC: SW04
N h ... 7

7 Decision block
Is the location of the faulty unit known? Y h ... 15
N h ... 8

40 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW01

8 Decision block
For which unit is the location not reported and must be determined?
– MP h ... 9
– AMXE h ... 10
– ASMX h ... 11
– LIC h ... 12
– ASN5 h ... 13
– ASN h ... 14
9 Determine MP data
b DISP MP:MP=..,Side=..; ☞ ......PROC:
CH:SSNC

b STAT MP:MP=..,Side=..; h ... 15

10 Determine AMXE data
b DISP AMX:Side:=..,ACCG=..,AMX=1; ☞ ......PROC:
CH:SSNC

b STAT AMX:Side=..,ACCG=..,AMX=1; h ... 15

11 Determine ASMX data
b DISP AMX:Side:=..,ACCG=..,AMX=1; ☞ ......PROC:
CH:SSNC

b STAT AMX:Side=..,ACCG=..,AMX=1; h ... 15

12 Determine LIC data
b DISP LIC:LIC=..; ☞ ......PROC:
CH:SSNC

b STAT LIC:LIC=..; h ... 15

13 Determine ASN5 data
b DISP ASN:Side=..,ACCG=1,ASN=1; ☞ ......PROC:
CH:SSNC

b STAT ASN:Side=..,ACCG=1ASN=1; h ... 15

14 Determine ASN data
b DISP ASN:Side=..,ACCG=2,ASN=..; ☞ ......PROC:
CH:SSNC

b STAT ASN:Side=..,ACCG=2,ASN=..; h ... 15

A50016-D3104-M470-3-7620 41
MMN:SSNC Maintenance
HW01 Signaling

15 Decision block
Which unit has been configured to failed/degraded due to a fault?
– ASN (ACCG=2/GMX/ASMG16/16/PSAG) to failed h ...PROC: SNC06
– ASN (ACCG=2/GMX/ASMG16/16/AMXE) to degraded h ...PROC: SNC16
– ASN20 (ACCG=1/GMXE/ASMG8/8) to failed h ...PROC: SNC06
– ASN20 (ACCG=1/GMXE/ASMG8/8) to degraded h ...PROC: SNC16
– ASN5 (ACCG=1/GMXE/ASMX) to failed h ...PROC: SNC06
– ASN5 (ACCG=1/GMXE/ASMX) to degraded h ...PROC: SNC16
– AMX (AMXE/ ACCG) to failed h ...PROC: SNC02
– AMX (AMXE/ ACCG to degraded h ...PROC: SNC12
– Both MPU of one/more MP’s to failed h ... 16
– MPU to failed h ...PROC: SNC03
– MPU to degraded h ...PROC: SNC13
– LIC to failed h ...PROC: SNC04
– LIC to degraded h ...PROC: SNC14
16 Decision block
In the case of a "crossover breakdown" of ASN/AMX the MPs can no longer all
communicate via a communication ring. The MPs that cannot be reached via
the ring are reported with HW01, configured to failed and removed from the ring.
The ring is formed again via the MPs that can still be reached. ’Fault Verification’
and ’Configuration’ try at regular intervals (approx. every 15 minutes) to activate
these MPs again and to include them in the ring. When this takes place, the
alarm is canceled first, and if the MPs cannot be included in the ring, the alarm
is set again.
When the fault has been cleared in the ASN/AMX, the MPUs of the MPs are ac-
tivated again by means of ’Fault Verification’ and ’Configuration’ and included in
the ring again.
Are the units of AMX/ASN on system sides 0 and 1 not operational? Y h ... 17
N h ...SNC03

17 Clearing a failure of ASN/AMX

Clear the failed units of ASN and AMX before performing fault clearance on the
MPs. When fault clearance has been performed successfully on the ASN and
AMX, the MPs that failed because of the crossover breakdown are activated
again by means of ’Fault Verification’ and ’Configuration’ and included in the
ring.
Clear the ASN using MMN:SSNC, SNC06 i....SNC06
Clear the AMX using MMN:SSNC, SNC02 i....SNC02
Have the MPs concerned been activated again? Y h ... END
N h ... 15

END

42 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW02

2.8 Extended HW Fault Clearance

HW02

General notes and fault description

This error report is used to report interface errors or also to report units in which a fault
report has been lost. In the case of lost fault reports it is not possible to specify the lo-
cation of the suspect unit. This must be determined by means of a command.
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Decision block

Was a total CCS7 outage also reported with the failure of the unit? Y h ...PROC: SW01
N h ... 2

2 Decision block
Was a total CALLP outage also reported with the failure of the unit? Y h ...PROC: SW02
N h ... 3

3 Decision block
Was a TOTAL OUTAGE OF MOBILE SWITCHING also reported with the failure
of the unit? Y h ...PROC: SW04
N h ... 4

4 Decision block
Is the location of the faulty unit known? Y h ... 12
N h ... 5

5 Decision block
For which unit is the location not reported and must be determined?
– MPU h ... 6
– AMXE h ... 7
– ASMX h ... 8
– LIC h ... 9
– ASN5 h ... 10
– ASN h ... 11
6 Determine MP data
b DISP MP:MP=..,Side=..;
b STAT MPMP:=..,Side=..; h ... 12

A50016-D3104-M470-3-7620 43
MMN:SSNC Maintenance
HW02 Signaling

7 Determine AMXE data

b DISP AMX:Side:=..,ACCG=..,AMX=1;
b STAT AMX:Side=..,ACCG=..,AMX=1; h ... 12
8 Determine ASMX data
b DISP AMX:Side:=..,ACCG=..,AMX=1;
b STAT AMX:Side=..,ACCG=..,AMX=1; h ... 12
9 Determine LIC data
b DISP LIC:LIC=..;
b STAT LIC:LIC=..; h ... 12
10 Determine ASN5 data
b DISP ASN:Side=..,ACCG=1,ASN=1;
b STAT ASN:Side=..,ACCG=1ASN=1; h ... 12
11 Determine ASN data
b DISP ASN:Side=..,ACCG=2,ASN=..;
b STAT ASN:Side=..,ACCG=2,ASN=..; h ... 12
12 Decision block
Which unit has been configured to failed/degraded due to a fault?
– ASN (ACCG=2/GMX/ASMG16/16) to failed h ...PROC: SNC06
– ASN (ACCG=2/GMX/ASMG16/16) to degraded h ...PROC: SNC16
– ASN20 (ACCG=1/GMXE/ASMG8/8) to failed h ...PROC: SNC06
– ASN20 (ACCG=1/GMXE/ASMG8/8) to degraded h ...PROC: SNC16
– ASN5 (ACCG=1/GMXE/ASMX) to failed h ...PROC: SNC06
– ASN5 (ACCG=1/GMXE/ASMX) to degraded h ...PROC: SNC16
– AMX (AMXE/ ACCG) to failed h ...PROC: SNC02
– AMX (AMXE/ ACCG) to degraded h ...PROC: SNC12
– MP to failed h ...PROC: SNC03
– MP to degraded h ...PROC: SNC13
– LIC to failed h ...PROC: SNC04
– LIC to degraded h ...PROC: SNC14

END

44 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW03

2.9 MDD/MOD Fault Clearance

HW03

General notes and fault description

If a failure occurs on both MDDs, then start the fault clearance procedure EY06 first, be-
fore start the procedure HW03, HW05 or HW06
A MDD/MOD is configured to failed.
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Decision block

b STAT MDDMP;
Are both MDD of the MP(SA) in basic frame SCB failed or not available? Y h ...PROC: EY06
N h ... 2

2 Preparation the fault clearance on-site

Provide the modules/units that are reported in the error message and are given
in the fault clearance procedure.
Start the fault clearance on-site. h ... 3
3 Decision block
Which LED is on (see module faceplate MDD/MOD)?
– green only h ... 4
– green and red h ... 16
– red only h ... 6
– none h ... 5
4 Display status of affected units
b STAT MDDMP;

If an MOD is installed, then also

b STAT MODMP:Side=..;
Have all units the Operational State=Enabled and the Alarm State=Cleared? Y h ... END
N h ... 6

A50016-D3104-M470-3-7620 45
MMN:SSNC Maintenance
HW03 Signaling

5 Power supply fault

b CONF MDDMP:Side=..,Administrative State=locked;

An MOD connected to the same SCSI bus of the MPU must also be deactivat-
ed. If an MOD is installed and activated, then also

b CONF MODMP:Side=..,Administrative State=locked;

Check the fuse and if necessary switch the fuse on. ☞ ......Construction
Rack SSNC

After deactivation due to over voltage the module can only be switched on again
by removing and reinserting the module.

Pull the module and plug it in again.

If any LED on)? Y h ... 8
N h ... 7

6 Deactivate the MDD/MOD

b CONF MDDMP:Side=..,Administrative State=locked;

An MOD connected to the same SCSI bus of the MPU must also be deactivat-
ed.

b CONF MODMP:Side=..,Administrative State=locked;

If the MDD (MOD) was configured correctly, only the red LED on the faceplate of
MDD (MOD) is lit.

Is only the red LED lit on the MDD (MOD) module faceplate? Y h ... 7
N h ... 16

7 Replace the suspect MDD/MOD

Pull the suspect module for MDD/MOD
Connect the replacement module for MDD/MOD.
Which unit has been replaced?
– MDD h ... 8
– MOD h ... 12
8 MDD diagnosis
b DIAG MDDMP:Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 11
N h ... 9

46 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW03

9 Decision block
Was the MDD/MOD already replaced? Y h ... 10
N h ... 7

10 Reinsert the original module for MDD

Remove the replacement module and reinsert the original module for MDD. h ... 16
11 Activate MDD and MOD
b CONF MDDMP:Side=..,Administrative State=unlocked,Label=Yes

Was an MOD deactivated, then also.

b CONF MODMP:Side=..,Administrative State=unlocked,Label=No;

Could the unit(s) be reactivated without faults? Y h ... 15
N h ... 16

12 Diagnosis MOD
b DIAG MODMP:Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 14
N h ... 13

13 Reinsert the original module for MOD

Remove the replacement module and reinsert the original module for MOD. h ... 16
14 Activate MOD and MDD
b CONF MDDMP:Side=..,Administrative State=unlocked,Label=No;
b CONF MODMP:Side=..,Administrative State=unlocked,Label=Yes;
Could the units be reactivated without faults? Y h ... 15
N h ... 16

15 Decision block

If these actions have cleared the fault, the green LED on the front panel of the
replacement modules is lit, but the red LED is off. Another way to check whether
fault clearance has been successful is to see whether the alarm has been can-
celled in the alarm protocol (alarm state=Cleared).

Could the fault be cleared? Y h ... END

N h ... 16

A50016-D3104-M470-3-7620 47
MMN:SSNC Maintenance
HW03 Signaling

16 Nonstandard maintenance
It is not possible to clear the fault by the standard fault clearance procedures. h ...NM:SSNC

END

48 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW05

2.10 Interface Fault MDD/MOD - MPU(SA)

HW05

General notes and fault description

In the event of a failure on both MDDs, start the EY06 fault clearance procedure before
starting the HW03/HW05/HW06 procedure.
An interface fault has been detected between MDD/MOD and MPU(SA). The order in
which the units should be replaced is first MDD/MOD and then MPU.
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Decision block

b STAT MDDMP;
In an SCB frame, are both MDDs in the ’failed’ or unavailable state? Y h ...PROC: EY06
N h ... 2

2 Preparation the fault clearance on-site

Provide the modules/units that are reported in the error message and are given
in the fault clearance procedure.
Start the fault clearance on-site. h ... 4
3 Decision block
Is the MDD and the connected MOD on this MPU already in the state ’locked’? Y h ... 7
N h ... 4

4 Decision block
Which LED is lit (see module faceplate MDD/MOD)?
– green only h ... 5
– green and red h ... 27
– red only h ... 6
5 Display status of affected units
b STAT MP:MP=..;
b STAT MDDMP;

If an MOD is installed, then also

b STAT MODMP:Side=..;
Do all units have the Operational State=Enabled and the Alarm State=Cleared? Y h ... END
N h ... 6

A50016-D3104-M470-3-7620 49
MMN:SSNC Maintenance
HW05 Signaling

6 Deactivate MDD/MOD
b CONF MDDMP:Side=..,Administrative State=locked;

An MOD connected to the same SCSI bus of the MPU must also be deactivat-
ed. If an MOD is installed and activate then also

b CONF MODMP:Side=..,Administrative State=locked;

If the MDD (MOD) was configured correctly, only the red LED on the faceplate of
MDD (MOD) is on.

Is only the red LED lit on the MDD (MOD) module faceplate? Y h ... 7
N h ... 27

7 Check SCSI Terminator

The terminator on the SCSI interface is only contacted if an MOD available. The
terminator is connected on the backplane of the relevant MOD. ☞ ......Construction
Frame SSNC

Check the SCSI terminator

Were any faults detected Y h ... 8
N h ... 11

8 Decision block
Could the fault be cleared? Y h ... 9
N h ... 27

9 Diagnosis MDD
b DIAG MDDMP:Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 10
N h ... 11

10 Diagnosis MOD
b DIAG MODMP:Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 23
N h ... 11

11 Replace the suspect MDD/MOD

Remove the suspect module for MDD/MOD.
Connect the replacement module for MDD/MOD. h ... 12

50 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW05

12 Decision block (MDD/MOD)

Which unit has been replaced?
– MDD h ... 13
– MOD h ... 14
13 Diagnosis MDD
b DIAG MDDMP:Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 21
N h ... 15

14 Diagnosis MOD
Take over the storage medium (CD) in the new MOD.
b DIAG MODMP:Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 23
N h ... 15

15 Reinsert the original MDD/MOD module

The interface fault could not be cleared by replacing the module for MOD/MDD.
The associated MPU/cable must be replaced.

Remove the replacement module and reinsert the original module for h ... 16
MDD/MOD.

16 Replace module MPU*

b CONF MP:MP=1,Side=..,Admin. state=Locked,Hazard check=Yes;
Remove module MPU*.
Connect replaced module MPU*. h ... 17
17 Diagnosis MPU
b DIAG MP:MP=1,Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 18
N h ... 26

18 Configure MPU to Unlocked

b CONF MP:MP=1,Side=..,Admin. state=Unlocked; h ... 19
19 Decision block (MPU)
What other unit still has to undergo diagnosis?
– MDD h ... 20
– MOD h ... 22

A50016-D3104-M470-3-7620 51
MMN:SSNC Maintenance
HW05 Signaling

20 Diagnosis MDD
b DIAG MDDMP:Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 21
N h ... 26

21 Activate MDD
b CONF MDDMP:Side=..,Administrative State=unlocked,Label=Yes

Was an MOD deactivated, then also

b CONF MODMP:Side=..,Administrative State=unlocked,Label=No; h ... 24

22 Diagnosis MOD
b DIAG MODMP:Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 23
N h ... 26

23 Activate MOD
b CONF MODMP:Side=..,Administrative State=unlocked,Label=Yes;
b CONF MDDMP:Side=..,Administrative State=unlocked,Label=No; h ... 24
24 Decision block

If these actions have cleared the fault, the green LED on the front panel of the
replacement modules is lit, but the red LED is off. Another way to check whether
fault clearance has been successful is to see whether the alarm has been can-
celled in the alarm protocol (alarm state=Cleared).

Could the fault be cleared? Y h ... END

N h ... 27

25 Decision block
Was the module MPU(SA) replaced in the basic frame? Y h ...DATA:MPU
N h ... END

26 Reinsert the original associated MPU* module

It is not possible to clear the fault by replacing the MDD/MOD and/or MPU. The
original module must be reinserted.

Reinsert the original MPU* module. h ... 27

52 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW05

27 Nonstandard maintenance
The fault cannot be cleared using the standard fault clearance procedures. h ...NM:SSNC

END

A50016-D3104-M470-3-7620 53
MMN:SSNC Maintenance
HW06 Signaling

2.11 Interface Fault MPU(SA) - MDD/MOD

HW06

General notes and fault description

In the event of a failure on both MDDs, start the EY06 fault clearance procedure before
starting the HW03/HW05/HW06 procedure.
An interface fault has been detected between MPU(SA) and MDD/MOD. The order in
which the units should be replaced is first MPU and then MDD/MOD.
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Decision block

b STAT MDDMP;
Are both MDD of the MP(SA) in basic frame SCB failed or not available? Y h ...PROC: EY06
N h ... 2

2 Preparation the fault clearance on-site

Provide the modules/units that are reported in the error message and are given
in the fault clearance procedure.
Start the fault clearance on-site. h ... 3
3 Decision block
Which LED is lit (see module faceplate)?
– green only h ... 4
– green and red h ... 21
– red only h ... 5
4 Display status of MPU
b STAT MP:MP=1;
b STAT MDDMP;

If an MOD is installed, then also

b STAT MODMP:Side=..;
Have all units the Operational State=Enabled and the Alarm State=Cleared? Y h ... END
N h ... 5

54 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW06

5 Deactivate MDD/MOD
b CONF MDDMP:Side=..,Administrative State=locked;

An MOD connected to the same SCSI bus of the MPU must also be deactivat-
ed. If an MOD is installed and activated then also

b CONF MODMP:Side=..,Administrative State=locked;

If the MDD (MOD) was configured correctly, only the red LED on the faceplate of
MDD (MOD) is on.

Is only the red LED lit on the MDD (MOD) module faceplate? Y h ... 6
N h ... 21

6 Replace module MPU*

b CONF MP:MP=1,Side=..,Hazard check=Yes,Admin. state=Locked;
Pull module MPU*.
Connect replacement module MPU*.
b DIAG MP:MP=1,Side=..,Kind of diagnosis=Complete diagnosis;
Was the diagnosis completed without any faults being found? Y h ... 8
N h ... 7

7 Reinsert original module

Reinsert original module MPU* h ... 11
8 Diagnose MOD and MDD
b CONF MP:MP=1,Side=..,Admin. state=Unlocked;
b DIAG MDDMP:Side=..,Kind of diagnosis=Complete diagnosis;

Was an MOD deactivated, then also

b DIAG MODMP:Side=..,Kind of diagnosis=Complete diagnosis;

Were both diagnoses completed without any faults being found? Y h ... 9
N h ... 11

9 Activate MOD and MDD

b CONF MDDMP:Side=..,Administrative State=unlocked,Label=No;

Was an MOD deactivated, then also

b CONF MODMP:Side=..,Administrative State=unlocked,Label=No; h ... 18

10 Deactivate MPU
b CONF MP:MP=1,Side=..,Hazard check=Yes,Admin. state=Locked; h ... 11

A50016-D3104-M470-3-7620 55
MMN:SSNC Maintenance
HW06 Signaling

11 Decision block
Which unit is also affected by this interface fault?
– MDD h ... 12
– MOD (Storage medium inside) h ... 15
12 Replace MDD
Replace module MDD
b DIAG MP:MP=1,Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 13
N h ... 21

13 Diagnosis MDD
b CONF MP:MP=1,Side=..,Admin. state=Unlocked;
b DIAG MDDMP:Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 14
N h ... 21

14 Activate MDD and MOD

b CONF MDDMP:Side=..,Administrative State=unlocked,Label=Yes

Was an MOD deactivated, then also

b CONF MODMP:Side=..,Administrative State=unlocked,Label=No; h ... 18

15 Replace MOD
Replace module MOD
Take over the storage medium (CD) in the new MOD.
b DIAG MP:MP=1,Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 16
N h ... 20

16 Diagnosis MOD
b CONF MP:MP=1,Side=..,Admin. state=Unlocked;
b DIAG MODMP:Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 17
N h ... 20

17 Activate MOD and MDD

b CONF MODMP:Side=..,Administrative State=unlocked,Label=Yes;
b CONF MDDMP:Side=..,Administrative State=unlocked,Label=No; h ... 18

56 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW06

18 Decision block

If these actions have cleared the fault, the green LED on the front panel of the
replacement modules is lit, but the red LED is off. Another way to check whether
fault clearance has been successful is to see whether the alarm has been can-
celled in the alarm protocol (alarm state=Cleared).

Could the fault be cleared? Y h ... 19

N h ... 21

19 Decision block
Was the module MPU(SA) replaced in the basic frame? Y h ...DATA:MPU
N h ... END

20 Reinsert original module for MDD/MOD

The fault cannot be cleared by replacing MDD/MOD and/or MPU. The original
module must be reinserted.

Remove the replacement module and reinsert the original module for h ... 21
MDD/MOD.

21 Nonstandard maintenance
The fault cannot be cleared using the standard fault clearance procedures. h ...NM:SSNC

END

A50016-D3104-M470-3-7620 57
MMN:SSNC Maintenance
HW07 Signaling

2.12 MPU ETHERNET Interface Fault

HW07

For additional information concerning e.g. commands/tasks, modules and replace/re-

i exchange of modules etc. see 2.1 Comments and Hints.

1 Important hint

– Make sure, that all cables are checked before proceeding with HW07 h ...NM:SSNC CH-
CABLE (SSNC)

2 Decision block
Is the ETHERNET interface from MP (SA) affected Y h ... 3
N h ... 16

3 General notes and fault description

Before replacing the MPU(SA), make sure the redundant MPU has fully opera-
tional access to an MDD/MOD with valid APS.
The following procedure deals with faults affecting the ETHERNET interfaces.
The MP(SA) has two ETHERNET interfaces which may be grouped at a HUB or
switch and routed from there to the Switch commander or routed via a host to
the Switch commander. The connections are made either using ’Twisted Wires’
or using the AUI. If the connections are made through the AUI, a transceiver is
required on the backplane. The HUB receives its power supply via module ALI.
If both Ethernet interfaces have failed, then start the fault clearance with MPU in
state ’hot standby’ or ’failed’.
The verification of an Ethernet failure is only possible the MPU is unlocked and h ... 4
active.

4 Decision block (ALI)

Was the ALI module also reported as faulty? Y i....PROC: HW23
N h ... 5
After successful fault clearance of the ALI module:

Was it possible to reactivate the ETHERNET interface? Y h ... 26

N h ... 5

58 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW07

5 Preparation for fault clearance on site

Provide the module(s)/unit(s) that are reported in the error message and are
given in the fault clearance procedure.
Start fault clearance on site. h ... 6
6 Check the connectors of the LAN cables
Perform a visual inspection of the connections from the MPU that raised the
alarm to the ETHERNET. If any cables or connectors are faulty, they must be re-
placed. Replacing cables, connectors, transceivers, HUB or the switch is not a
standard fault clearance activity.
Is it necessary to replace any cables, connectors, transceivers, HUB or the
switch? Y h ... 28
N h ... 7

7 Decision block
Were any faults found? Y h ... 8
N h ... 9

8 Decision block
Could the fault be cleared? Y h ... 26
N h ... 28

9 Configure the MPU to Locked

b CONF MDDMP:Side=..,Administrative State=locked;

An MOD connected and activate to the same SCSI bus of the MPU must also
be deactivated.

b CONF MODMP:Side=..,Administrative State=locked;

b CONF MP:MP=1,Side=..,Admin. state=Locked,Hazard check=Yes;
Were the commands executed? Y h ... 11
N h ... 10

10 Decision block
The command was not executed because there is no redundant MPU or be- h ... 9
cause no active MDD/MOD with a valid APS is available after deactivation of
this MPU. Repeat the command when a redundant MPU has been provided or
after making sure that a valid APS is available via the remaining MPU*.

11 Replace the suspect MPU(SA)

Remove the suspect MPU module.
Insert the replacement module. h ... 12

A50016-D3104-M470-3-7620 59
MMN:SSNC Maintenance
HW07 Signaling

12 Activate the MPU

b CONF MP:MP=1,Side=..,Admin. state=Unlocked;
Could the unit be activated without faults (only the green LED is lit)? Y h ... 13
N h ... 14

13 Decision block
The verification of a fault free Ethernet is only possible with an active (unlocked)
MPU. If the Ethernet interface is not fault free, then the MPU will be alarmed
again.
Did the MPU report an Ethernet failure again? Y h ... 14
N h ... 15

14 Reinsert original MPU* module

The MPU could not be activated again. The fault cannot be cleared by replacing
M:MPU*. The original module must be reinserted.

Reinsert the original MPU* module.

In order to maintain the redundancy of MDD/MOD, MPU and MDD/MOD should

be activated again until nonstandard maintenance can be performed.

b CONF MP:MP=1,Side=..,Admin. state=Unlocked;

b CONF MDDMP:Side=..,Administrative State=unlocked,Label=No;

Was an MOD deactivated, then also

b CONF MODMP:Side=..,Administrative State=unlocked,Label=No; h ... 28

15 Activate MDD/MOD
b CONF MDDMP:Side=..,Administrative State=unlocked,Label=No;

Was an MOD deactivated, then also

b CONF MODMP:Side=..,Administrative State=unlocked,Label=No; h ... 26

60 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW07

16 General notes and fault description

Before replacing the MPU, make sure that the redundant MPU has fully opera-
tional access to the ETHERNET.
The following procedure deals with faults affecting the ETHERNET interfaces.
The MP has two ETHERNET interfaces which may be grouped at a HUB or
switch and routed from there to the Switch commander or routed via a host to
the Switch commander. The connections are made either using ‘Twisted Wires’
or using the AUI. If the connections are made through the AUI, a transceiver is
required on the backplane.
If both Ethernet interfaces have failed, then start the fault clearance with MPU in
state ’hot standby’ or ’failed’.
The verification of an Ethernet failure is only possible the MPU is unlocked and h ... 17
active.

17 Preparation the fault clearance on-site

Provide the modules/units that are reported in the error message and are given
in the fault clearance procedure.
Start the fault clearance on-site. h ... 18
18 Check the connectors of the LAN cables
Perform a visual inspection of the connections from the MPU that raised the
alarm to the ETHERNET. If any cables or connectors are faulty, they must be re-
placed. The replacement of cables, connectors, transceivers, HUB or the switch
is not a standard fault clearance activity.
Is it necessary to replace any cable, connector, transceiver, HUB or switch? Y h ... 28
N h ... 19

19 Decision block
Were any faults found? Y h ... 20
N h ... 21

20 Decision block
Could the fault be cleared? Y h ... 26
N h ... 28

21 Configure the MPU to Locked

b CONF MP:MP=...,Side=..,Admin. state=Locked,Hazard check=Yes; h ... 22
22 Replace the suspect MPU
Remove the suspect MPU module.
Insert the replacement module. h ... 23

A50016-D3104-M470-3-7620 61
MMN:SSNC Maintenance
HW07 Signaling

23 Activate the MPU

b CONF MP:MP=1,Side=..,Admin. state=Unlocked;
Could the unit be activated without faults (only the green LED is lit)? Y h ... 24
N h ... 25

24 Decision block
The verification of a fault free Ethernet is only possible with an active (unlocked)
MPU. If the Ethernet interface is not fault free, then the MPU will be alarmed
again.
Did the MPU report an Ethernet failure again? Y h ... 28
N h ... 26

25 Reinsert original MPU* module

The MPU could not be activated again. The fault cannot be cleared by replacing
M:MPU*. The original module must be reinserted.

b CONF MP:MP=...,Side=..,Admin. state=Locked,Hazard check=Yes;

Reinsert the original MPU* module. h ... 28
26 Decision block

If these actions have cleared the fault, the green LED on the front panel of the
replacement modules is lit, but the red LED is off. Another way to check whether
fault clearance has been successful is to see whether the alarm has been can-
celled in the alarm protocol (alarm state=Cleared).

Could the fault be cleared? Y h ... 27

N h ... 28

27 Decision block
Was the module MPU(SA) replaced in the basic frame? Y h ...DATA:MPU
N h ... END

28 Nonstandard maintenance
The fault cannot be cleared using the standard fault clearance procedures. h ...NM:SSNC

END

62 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW08

2.13 Interface Fault MPU(SA) - ALI

HW08

General remarks and description of fault

The ALI can no longer be reached and has been configured to “failed”
• because an interface fault was detected between the MPU (status=providing ser-
vice) and the ALI, while the redundant MPU (status=hot standby) has “degraded”
status, with the result that the MPUs cannot be switched over.
– Action: clear the fault on the “degraded” MPU.
– Action: replace ALI
• because the MPUs could not be switched over after a fault was detected on the ac-
tive MPU-ALI link. In this case the fault is attributed to the ALI. The ALI is configured
to “failed”, the status of the MPUs remains unchanged, availability state = providing
service and hot standby, and both MPUs are in the alarm state= cleared.
– Action: replace ALI
– Action: configure the MPU that is providing service to “locked”
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Decision block

b STAT MP:MP=..;
b DISP MP:MP=..;
Are both MPUs in the alarm state=cleared? Y h ... 2
N h ... 6

2 Clear fault on ALI

The ALI that is in availability state=failed’ must be cleared of faults first. i ...PROC: SNC07
After successful fault clearance on the ALI h ... 3

3 Decision block
Were you able to clear the fault? Y h ... END
N h ... 4

A50016-D3104-M470-3-7620 63
MMN:SSNC Maintenance
HW08 Signaling

4 Clear fault on MPU in standby state ’providing service’

b CONF MDDMP:MP=..,Side=..,Administrative State=locked;

An MOD connected and active to the same SCSI bus of the MPU must also be
deactivated.

b CONF MODMP:Side=..,Administrative State=locked;

b CONF MP:MP=..,Side=..,Admin. state=Locked;
Clear the fault on the deactivated MPU i....PROC: SNC13
After successful fault clearance on the MPU h ... 5

5 Decision block
Were you able to clear the fault? Y h ... END
N h ...NM:SSNC

6 Clear fault on MPU in availability state ’degraded’

b CONF MDDMP:MP=..,Side=..,Administrative State=locked;

An MOD connected and active to the same SCSI bus of the MPU must also be
deactivated.

b CONF MODMP:Side=..,Administrative State=locked;

b CONF MP:MP=..,Side=..,Admin. state=Locked;
Clear the fault on the deactivated MPU i....PROC: SNC13
After successful fault clearance on the MPU h ... 7

7 Clear faults on ALI

Now you can clear the interface fault or the fault on the ALI module. h ...PROC: SNC07

END

64 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW10

2.14 Fault in MPU(SA), not System-Verified

HW10

General notes and description

This alarm is triggered when a fault that is not verified by the system occurs in MP=1
(MPU(SA)). Verification is omitted in order to avoid double disk failure.
If both MPUs (SA) are in operating state “degraded”, you must first carry out fault clear-
ance on the STB MPU (oper. state=disabled and standby status=hot/cold standby). Do
not carry out fault clearance on the active MPU (standby status=providing service) until
you have successfully cleared the faults on the STB MPU.
In addition to this, you must wait for the update and synchronization messages.
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Decision block

Has the MPU already been replaced during last 24 hours? Y h ... 2
N h ... 3

2 Decision block
After the activation of this module, is a failure reported again? Y h ...NM:SSNC,
CH-MPU
N h ... 3

3 Status check
b STAT MP:MP=1;
What is the operating state of the MPU?
– MPU in Admin. State=Locked h ... 4
– MPU in Availability Status=degraded and Standby Status=hot/cold standby h ... 5
– MPU in Availability Status=failed h ... 5
– Alarm status=critical/major/minor and for availability status=no value h ...NM:SSNC,
ALARM:MPU
– Alarm status=cleared and for availability status=failed/degraded h ...NM:SSNC,
ALARM:MPU

4 Decision block
Has this MPU already been diagnosed as fault-free? Y h ... 10
N h ... 8

A50016-D3104-M470-3-7620 65
MMN:SSNC Maintenance
HW10 Signaling

5 Decision block
Is the Ethernet interface affected? Y h ...HW07
N h ... 6

6 Configure MDD/MOD to Locked

b CONF MDDMP:Side=..,Administrative State=locked;

If there is an MOD connected to the same SCSI bus of the MPU, this must also
be deactivated.

b CONF MODMP:Side=..,Administrative State=locked;

If the configuration was done correctly, only the red LEDs will be lit on the mod-
ule faceplates of MDD and MOD.

Are only the red LEDs lit on the module faceplates of MDD/MOD? Y h ... 7
N h ... 26

7 Configure MPU to Locked

b CONF MP:MP=1,Side=..,Admin. state=Locked,Hazard check=Yes; h ... 8
8 MPU diagnosis (fault verification)
b DIAG MP:MP=1,Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without faults? Y h ... 10
N h ... 9

9 Replace module MPU*

Replace module MPU*.
Connect replacement module MPU*.
b DIAG MP:MP=1,Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without faults? Y h ... 10
N h ... 11

10 Activate MPU

Configure MPU in Admin State=Locked to Unlocked.

b CONF MP:MP=1,Side=..,Admin. state=Unlocked; h ... 14

66 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW10

11 Decision block
What fault was indicated at the end of the diagnosis?
– Interface fault MDD/MOD (suspect units: MPU, MDD/MOD) i ...PROC: HW05
– Any other fault i ...PROC: SNC13
After working through the appropriate procedure, continue with h ... 12

12 Decision block
b STAT MP:MP=1;
Were you able to activate the MPU without faults in the procedure that was
called up? Y h ... 13
N h ... 26

13 Decision block
Is one MDD still in operating state Locked? Y h ... 14
N h ... 15

14 Activate MDD with formatting

b CONF MDDMP:Side=..,Administrative State=unlocked,Label=Yes; h ... 15
15 Decision block
Is a MOD connected to this MPU? Y h ... 16
N h ... 21

16 Decision block
Is one MOD still in operating state ’locked’? Y h ... 17
N h ... 23

17 Decision block
Was this MOD replaced? Y h ... 18
N h ... 20

18 Decision block
Are current data stored on the new MOD (e.g. a new APS)? Y h ... 20
N h ... 19

19 Activate MOD with formatting

b CONF MODMP:Side=..,Administrative State=unlocked,Label=Yes: h ... 21
20 Activate MOD without formatting
b CONF MODMP:Side=..,Administrative State=unlocked,Label=No: h ... 21

A50016-D3104-M470-3-7620 67
MMN:SSNC Maintenance
HW10 Signaling

21 Decision block

Do not continue fault clearance until an update (synchronization of MDD/MOD)

has been performed on the MPUs that have been cleared of faults so far. This
update can take up to 60 minutes. Synchronization is complete when the alarm
for this MDD/MOD has been canceled.

Now fault clearance can be carried out on the partner MPU.

Which LED is lit on the module faceplate of the partner MPU?

– only green h ... 22
– green and red h ... 6
– only red h ...PROC: SNC03
– none h ...PROC: SNC03
22 Decision block
b STAT MP:MP=1;
Are both MPUs of the MP(SA) in operating state=enabled, and is one MPU in
Standby Status=providing service and one MPU in Standby Status=hot stand-
by? Y h ... 23
N h ...PROC: SNC03

23 Decision block
b STAT MP
The fault has been cleared if,
– the associated alarm has been canceled
(alarm status=cleared and availability status=no entry) and
– only the green LED is lit on the faceplate of the affected/replaced modules
and
– the alarm has been canceled in the alarm log. (alarm state=cleared).
Has the fault been cleared? Y h ... 24
N h ... 26

24 Decision block
Was the module MPU(SA) replaced in the basic frame? Y h ...DATA:MPU
N h ... END

25 Decision block

For hints on inconsistency, see

Are the alarm and availability states inconsistent? Y h ... NM:SSNC

ALARM:MPU
N h ... 26

68 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW10

26 Nonstandard maintenance
The fault cannot be cleared using the standard fault clearance procedures. h ...NM:SSNC

END

A50016-D3104-M470-3-7620 69
MMN:SSNC Maintenance
HW11 Signaling

2.15 Fault in MPU(D), not System-Verified

HW11

General notes and description

This alarm is triggered when a fault that is not verified by the system occurs in an
MPU(D). This is caused by a missing or faulty partner MPU(D). Verification of the fault
is omitted in order to avoid failure of the remaining MPU(D).
If both MPUs of an MP(D) are in operating state “degraded”, you must first carry out fault
clearance on the STB MPU (Oper. State=disabled and Standby Status=hot/cold stand-
by). Do not carry out fault clearance on the active MPU (Standby Status=providing ser-
vice) until you have successfully cleared the faults on the STB MPU.
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Decision block

Was a total failure of CCS7 reported at the same time as the failure of the unit? Y h ...PROC: SW01
N h ... 2

2 Decision block
Was a total failure of CALLP reported at the same time as the failure of the unit? Y h ...PROC: SW02
N h ... 3

3 Status check
b STAT MP:MP=..;
What is the operating state of the MPU?
– MPU in Locked h ... 5
– MPU in Availability Status=degraded and Standby Status=hot/cold standby) h ... 4
– MPU in Availability Status=failed h ... 4
4 Deactivate MPU
b CONF MP:MP=..,Side=..,Admin. state=Locked; h ... 6
5 Decision block
Has this MPU already been diagnosed as fault-free? Y h ... 8
N h ... 6

70 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW11

6 Diagnosis of MPU (fault verification)

b DIAG MP:MP=..,Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without faults? Y h ... 8
N h ... 7

7 Replace module MPU*

Pull module MPU*.
Connect replacement module MPU*.
b DIAG MP:MP=..,Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without faults? Y h ... 8
N i ...PROC: SNC13
After successful fault clearance and activation of the MPU, the ACT/STB MPUs h ... 9
are switched over. Fault clearance cannot be continued until switchover has
been completed successfully.

8 Activate MPU
b CONF MP:MP=..,Side=..,Admin. state=Unlocked; h ... 9
9 Decision block
b STAT MP:MP=..;
Are both MPUs fault-free (Operational State=Enabled and Alarm
State=Cleared)? Y h ... 11
N h ... 10

10 Prepare fault clearance of the partner MPU

Is the partner MPU in Availability Status=degraded and Standby Status=hot/cold
standby? Y h ...PROC: SNC13
N h ...PROC: SNC03

11 Decision block

The fault has been cleared if the associated alarm has been canceled (alarm
state=Cleared) and only the green LED is lit on the faceplate of the affected/re-
placed module. To determine whether fault clearance was successful, you can
also check whether the alarm has been canceled in the alarm log.

Has the fault been cleared? Y h ... END

N h ... 12

12 Nonstandard maintenance
It is not possible to clear the fault using standard fault clearance measures. h ...NM:SSNC

END

A50016-D3104-M470-3-7620 71
MMN:SSNC Maintenance
HW14 Signaling

2.16 PLL0 Faults

HW14

For additional information concerning e.g. commands/tasks, modules and replace/re-

i exchange of modules etc. see 2.1 Comments and Hints.

1 General notes and fault description

The PLL (phase-locking loop) needed for clock generation is no longer able to
synchronize with the offered/received master clock.
This may be due to a fault in the PLL or the result of exceeding the permissible
frequency range of a reference source.
Initial alerting is for the ACCGs where it is no longer possible to synchronize us-
ing the master clock on account of component tolerances, temperature or age-
ing.
Fault clearance must include the higher-order clock supply stages even if they
have not reported a fault.

Clock distribution does not always have be performed by the ACCGs in MUT 9
of the rack; system-specific variants are possible.

If clock distribution is performed by the ACCGs in MUT 9, the synchronizing ☞ ......PROC: CLOCK
paths are as follows; see figure:
h ... 2
2 Decision block
Which ‘specific problem=non servere hardware fault’ alarm situation is present
throughout the system?
– Alarm from one ACCG(AMX) only h ...PROC: SNC12
– Alarm from one ACCG(ASN) only h ...PROC: SNC16
– Alarms from several ACCG(AMX), side 0 only h ... 3
– Alarms from several ACCG(AMX), side 1 only h ... 9
– Alarms from ACCG(ASN) and ACCG(AMX), side 0 only h ... 15
– Alarms from ACCG(ASN) and ACCG(AMX), side 1 only h ... 16
– Alarms from several ACCG(AMX), side 0 and 1, no alarm from ASN h ... 17
– Alarms from ACCG(ASN) and ACCG(AMX), side 0 and 1 h ... 17
3 Decision block (side 0)
Does the SSNC consist of several racks? Y h ... 4
N h ... 6

72 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW14

4 Decision block (side 0)

Are the reported ACCGs all in one rack? Y h ... 5
N h ... 6

5 Alarms from several ACCGs from a rack, side 0 (no ASN alarm)
The clock-distributing ACCG in this rack on system side 0 is possibly faulty and
must be replaced.
It is necessary to check whether the redundant units are fault-free and active
! (Operational state=Enabled, Standby state=Hot standby / Providing service,
Alarm state=Cleared, Under repair bit=false and no entry in Availability state)
before performing the following ACCG configuration with Hazard check=Yes!

b STAT ASN;
b STAT AMX;
Configure clock-distributing ACCGs in this rack to ‘locked’. ☞ ......PROC: CLOCK
b CONF AMX:ACCG=..,Side=0,Admin. state=Locked,Hazard check=Yes;
Exchange clock-distributing ACCGs in this rack, side 0
b CONF AMX:ACCG=..,Side=0,Admin. state=Unlocked;
Were all alarms cancelled after waiting 5 minutes? Y h ... 22
N h ... 24

6 Alarms from several ACCGs (AMX), side 0 only

It is necessary to check whether the redundant units are fault-free and active
! (Operational state=Enabled, Standby state=Hot standby / Providing service,
Alarm state=Cleared, Under repair bit=false and no entry in Availability state)
before performing the following ACCG configuration with Hazard check=Yes!

b STAT ASN;
b STAT AMX;
Configure ACCG of ASN 0 to ‘locked’
b CONF ASN:ACCG=...,Side=0,Admin. state=Locked,Hazard check=Yes;
Exchange clock-distribution ACCG in this rack, side 0
b CONF ASN:ACCG=...,Side=0,Admin. state=Unlocked;
Is the alarm situation unchanged after waiting 5 minutes? Y h ... 7
N h ... 22

7 Alarms from several ACCGs (AMX), side 0 only

The clock-distributing ACCGs in these racks on system side 0 are possibly de-
fective and must be replaced.
It is necessary to check whether the redundant units are fault-free and active
! (Operational state=Enabled, Standby state=Hot standby / Providing service,
Alarm state=Cleared, Under repair bit=false and no entry in Availability state)
before performing the following ACCG configuration with Hazard check=Yes!

A50016-D3104-M470-3-7620 73
MMN:SSNC Maintenance
HW14 Signaling

b STAT ASN;
b STAT AMX;
Configure clock-distributing ACCGs in this rack to ‘locked’. ☞ ......PROC: CLOCK
b CONF AMX:ACCG=..,Side=0,Admin. state=Locked,Hazard check=Yes;
Exchange clock-distributing ACCGs, side 0
b CONF AMX:ACCG=..,Side=0,Admin. state=Unlocked;
Could the alarm situation in this rack be cleared after 5 minutes? Y h ... 8
N h ... 24

8 Decision block (side 0)

Must other clock-distributing ACCG(AMX) be replaced? Y h ... 7
N h ... 22

9 Decision block (side 1)

Does the SSNC consist of several racks? Y h ... 10
N h ... 12

10 Decision block (side 1)

Are the reported ACCGs all in one rack? Y h ... 11
N h ... 12

11 Alarms from several ACCGs from a rack, side 1 (no ASN alarm)
The clock-distributing ACCG in this rack on system side 1 is possibly faulty and
must be replaced.
Before performing the following ACCG configuration with Hazard check=YesIt is
! necessary to check whether the redundant units are fault-free and active (Oper-
ational state=Enabled, Standby state=Hot standby / Providing service, Alarm
state=Cleared, Under repair bit=false and no entry in Availability state)!

b STAT ASN;
b STAT AMX;
Configure clock-distributing ACCGs in this rack to ‘locked’. ☞ ......PROC: CLOCK
b CONF AMX:ACCG=..,Side=1,Admin. state=Locked,Hazard check=Yes;
Exchange clock-distributing ACCGs in this rack, side 1
b CONF AMX:ACCG=..,Side=1,Admin. state=Unlocked;
Were all alarms cancelled after waiting 5 minutes? Y h ... 23
N h ... 24

74 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW14

12 Alarms from several ACCGs (AMX), side 1 only

It is necessary to check whether the redundant units are fault-free and active
! (Operational state=Enabled, Standby state=Hot standby / Providing service,
Alarm state=Cleared, Under repair bit=false and no entry in Availability state)
before performing the following ACCG configuration with Hazard check=Yes!

b STAT ASN;
b STAT AMX;
Configure ACCG of ASN 1 to ‘locked’
b CONF ASN:ACCG=...,Side=1,Admin. state=Locked,Hazard check=Yes;
Exchange ACCG of ASN 1
Configure ACCG of ASN1 to ‘unlocked’
b CONF ASN:ACCG=...,Side=1,Admin. state=Unlocked;
Is the alarm situation unchanged after waiting 5 minutes? Y h ... 13
N h ... 22

13 Alarms from several ACCGs (AMX), side 1 only

The clock-distributing ACCGs in these racks on system side 1 are possibly de-
fective and must be replaced.
It is necessary to check whether the redundant units are fault-free and active
! (Operational state=Enabled, Standby state=Hot standby / Providing service,
Alarm state=Cleared, Under repair bit=false and no entry in Availability state)
before performing the following ACCG configuration with Hazard check=Yes!

b STAT ASN;
b STAT AMX;
Configure clock-distributing ACCGs in this rack to ‘locked’. ☞ ......PROC: CLOCK
b CONF AMX:ACCG=..,Side=1,Admin. state=Locked,Hazard check=Yes;
Exchange clock-distributing ACCGs, side 1
b CONF AMX:ACCG=..,Side=1,Admin. state=Unlocked;
Could the alarm situation in this rack be cleared after 5 minutes? Y h ... 14
N h ... 24

14 Decision block (side 1)

Must other clock-distributing ACCG(AMX) be replaced? Y h ... 7
N h ... 22

15 Alarms from ACCG (ASN and AMX), side 0 only

It is necessary to check whether the redundant units are fault-free and active
! (Operational state=Enabled, Standby state=Hot standby / Providing service,
Alarm state=Cleared, Under repair bit=false and no entry in Availability state)
before performing the following ACCG configuration with Hazard check=Yes!

A50016-D3104-M470-3-7620 75
MMN:SSNC Maintenance
HW14 Signaling

b STAT ASN;
b STAT AMX;
Configure ACCG of ASN 0 to ‘locked’
b CONF ASN:ACCG=...,Side=0,Admin. state=Locked,Hazard check=Yes;
Exchange ACCG of ASN, side 0
b CONF ASN:ACCG=...,Side=0,Admin. state=Unlocked;
Were all alarms cancelled after waiting 5 minutes? Y h ... 22
N h ... 24

16 Alarms from ACCG (ASN and AMX), side 1 only

It is necessary to check whether the redundant units are fault-free and active
! (Operational state=Enabled, Standby state=Hot standby / Providing service,
Alarm state=Cleared, Under repair bit=false and no entry in Availability state)
before performing the following ACCG configuration with Hazard check=Yes!

b STAT ASN;
b STAT AMX;
Configure ACCG of ASN 1 to ‘locked’
b CONF ASN:ACCG=...,Side=1,Admin. state=Locked,Hazard check=Yes;
Exchange ACCG of ASN, side 1
b CONF ASN:ACCG=...,Side=1,Admin. state=Unlocked;
Were all alarms cancelled after waiting 5 minutes? Y h ... 22
N h ... 24

17 Alarms from several ACCGs (ASN and AMX), side 0 and 1

Interrogate master-slave configuration for ACCG(ASN) (the entry is ‘actual clock
master=true’ for master ACCG).
b DISP ASN;
Is the master ACCG(ASN) on system side 0? Y h ... 18
N h ... 20

18 Alarms from several ACCGs (ASN and AMX), side 0 and 1

(master ACCG side 0)
It is necessary to check whether the redundant units are fault-free and active
! (Operational state=Enabled, Standby state=Hot standby / Providing service,
Alarm state=Cleared, Under repair bit=false and no entry in Availability state)
before performing the following ACCG configuration with Hazard check=Yes!

76 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW14

b STAT ASN;
b STAT AMX;
Changing over the master ACCG by configuring the master ACCG
Configure ACCG of ASN 0 to ‘locked’
b CONF ASN:ACCG=...,Side=0,Admin. state=Locked,Hazard check=Yes;
Configure ACCG of ASN 0 to ‘unlocked’
b CONF ASN:ACCG=...,Side=0,Admin. state=Unlocked;
Were all alarms cancelled after waiting 5 minutes on the system side? Y h ... 19
N h ... 24

19 Alarms from several ACCGs (ASN and AMX), side 0 and 1.

Exchanging the ACCGs(ASN) side 0 (following slave changeover)
It is necessary to check whether the redundant units are fault-free and active
! (Operational state=Enabled, Standby state=Hot standby / Providing service,
Alarm state=Cleared, Under repair bit=false and no entry in Availability state)
before performing the following ACCG configuration with Hazard check=Yes!

b STAT ASN;
b STAT AMX;
Configure ACCG of ASN 0 to ‘locked’
b CONF ASN:ACCG=...,Side=0,Admin. state=Locked,Hazard check=Yes;
Exchange ACCG of ASN, side 0
b CONF ASN:ACCG=...,Side=0,Admin. state=Unlocked;
Were all alarms cancelled after waiting 5 minutes? Y h ... 22
N h ... 24

20 Alarms from several ACCGs (ASN and AMX), side 0 and 1

(master ACCG side 1)
It is necessary to check whether the redundant units are fault-free and active
! (Operational state=Enabled, Standby state=Hot standby / Providing service,
Alarm state=Cleared, Under repair bit=false and no entry in Availability state)
before performing the following ACCG configuration with Hazard check=Yes!

b STAT ASN;
b STAT AMX;
Changing over the master ACCG by configuring the master ACCG
Configure ACCG of ASN 1 to ‘locked’
b CONF ASN:ACCG=...,Side=1,Admin. state=Locked,Hazard check=Yes;
Configure ACCG of ASN 1 to ‘unlocked’
b CONF ASN:ACCG=...,Side=1,Admin. state=Unlocked;
Were all alarms cancelled after waiting 5 minutes on the system side? Y h ... 21
N h ... 24

A50016-D3104-M470-3-7620 77
MMN:SSNC Maintenance
HW14 Signaling

21 Alarms from several ACCGs (ASN and AMX), side 0 and 1.

Exchanging the ACCGs (ASN), side 1 (following slave changeover)
It is necessary to check whether the redundant units are fault-free and active
! (Operational state=Enabled, Standby state=Hot standby / Providing service,
Alarm state=Cleared, Under repair bit=false and no entry in Availability state)
before performing the following ACCG configuration with Hazard check=Yes!

b STAT ASN;
b STAT AMX;
Configure ACCG of ASN 1 to ‘locked’
b CONF ASN:ACCG=...,Side=0,Admin. state=Locked,Hazard check=Yes;
Exchange ACCG of ASN side 1
b CONF ASN:ACCG=...,Side=1,Admin. state=Unlocked;
Were all alarms cancelled after waiting 5 minutes? Y h ... 22
N h ... 24

22 Decision block
b STAT ASN;
b STAT AMX;
The fault has been cleared if
– the associated alarm has been cancelled
(Alarm Status=Cleared, Availability Status=no entry) and
– only the green LED is on at the front plate of the affected/replaced module(s),
and
– the alarm has been cancelled in the alarm log.
Could the fault be cleared? Y h ... END
N h ... 23

23 Decision block

For notes on inconsistency, see ☞ ......PROC:

CH:SSNC

Are the alarm and availability status inconsistent? Y h ...NM:SSNC

ALARM:ASN
N h ... 24

24 Special fault clearance

The fault cannot be cleared using the standard fault clearance procedure. h ...NM:SSNC

END

78 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW15

2.17 Clock Source Fault

HW15

1 General notes and description

A clock source has failed, but a redundant clock source is still available (HW15).
If the second clock source fails (or the last clock source used for synchroniza-
tion), this is reported additionally with MW16 and the system is set to ’holdover’
mode.
A maximum of 4 clock sources can be created, two via T3 clock supply cables
and two via T1/T2 clock supply cables.
If clock supply takes place via a T3 clock supply cable (external timed), an exter-
nal clock generator or a synchronization supply unit (SSU) can supply the re-
quired clock. The clock sources connected via T3 clock supply cables are linked
via a cable to the ESI ports (ES0/ES1) of the ACCGs of the ASN side 0 and 1.
This means that when the cable is pulled on the master ACCG both clocks fail
and the ’holdover’ mode is set as a result.
If the T1/T2 clock supply cable is used, the clock is supplied by means of a PCM
system (line timed) via an LIC, ACCG module of the AMX to the ACCG of the
ASN and distributed from there via the MP platform.
Of the offered clock sources, only the best two are used for further synchroniza-
tion, whereby the clock sources that are connected via T3 clock supply cables
are preferred. If the clock sources that are connected via T1/T2 clock supply ca-
bles (line timed) are to be used (or have to be used) for synchronization, the
clock sources that are connected via T3 clock supply cables must be canceled.
The return clock (T4) to the external SSU, if created, is supplied from the T1/T2
clock sources (line timed).
If both clock sources that are used for synchronization fail, the system does not h ... 2
switch over to another available clock source. Instead, the system goes into
’holdover’ mode. The ’holdover’ mode is also set if both clock sources of the
master ACCG fail, even if the clock slave ACCG could still supply a satisfactory
clock.

A50016-D3104-M470-3-7620 79
MMN:SSNC Maintenance
HW15 Signaling

2 Decision block
The possible causes of the fault are as follows:
• Fault on the clock-carrying PCM link (AIS, LOS, LOF...)
– Further hints: Observe the PCM failure report
– Measure: Clear faults on the PCM link, replace the LIC module (SNC04)
• The clock-carrying LIC module is faulty or is not supplying a clock
– Further hints: Observe the LIC failure report (HW01)
– Measure: Replace the LIC module (SNC04)
• Fault between the clock-carrying LIC and the ACCG module of the AMX
– Further hints: Observe the interface fault between LIC and AMX
(HW01/HW02).
– Measure: Clear the interface fault in accordance with the failure report.
• The clock-carrying ACCG module of the AMX is faulty.
– Further hints: Observe the failure report of the AMX (HW01)
– Measure: Clear faults on the AMX in accordance with the failure report.
• Fault between the clock-carrying ACCG module of the AMX and the ACCG
module of the ASN (HW01/HW02).
– Further hints: Observe the interface fault between AMX and ASN
(HW01/HW02)
– Measure: Clear the interface fault in accordance with the failure report.
• Fault between the clock-carrying redundant ACCG modules of the AMX.
– Further hints: Observe the AMX interface fault (HW01/HW02)
– Measure: Clear the interface fault in accordance with the failure report.
• Faulty ACCG module of the ASN (master).
– Further hints: Observe the failure report of the ASN (HW01/HW02)
– Measure: Clear faults on the ASN in accordance with the failure report.
• Fault in the external clock generator.
– Further hints: None
– Measure: Inform partner
• Faulty ESI port of the ACCG (ASN)
– Further hints: None
– Measure: Replace the ACCG of the ASN, check the clock supply cables
• Missing return clock (T4) from the ACCG (ASN) to the SSU.
– Further hints: None
– Measure: Check the clock supply cables, replace the ACCG of the ASN
(SNC06)
Initiate the appropriate action h ...PROCIN

END

80 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW16

2.18 Reference Clock Fault

HW16

1 General notes and description

The last clock source that can be used for synchronization has failed. The sys-
tem has been set to holdover’ mode.
A maximum of 4 clock sources can be created, two via T3 clock supply cables
and two via T1/T2 clock supply cables.
If clock is supplied via a T3 clock supply cable (externally timed), an external
clock generator or a synchronization supply unit (SSU) can supply the required
clock. The clock sources connected via T3 clock supply cables are linked via a
cable to the ESI ports (ES0/ES1) of the ACCGs of the ASN side 0 and 1. This
means that when the cable is pulled on the master ACCG both clocks fail and
the ’holdover’ mode is set as a result.
If the T1/T2 clock supply cable is used, the clock is supplied by means of a PCM
system (line-timed) via an LIC, ACCG module of the AMX to the ACCG of the
ASN and distributed from there via the MP platform.
Of the offered clock sources, only the best two are used for further synchroniza-
tion, the clock sources that are connected via T3 clock supply cables are pre-
ferred. If the clock sources that are connected via T1/T2 clock supply cables
(line-timed) are to be used (have to be used) for synchronization, the clock
sources that are connected via T3 clock supply cables must be canceled.
The return clock (T4) to the external, if created, is supplied from the T1/T2 clock
sources (line-timed).
If both clock sources that are used for synchronization fail, the system does not
switch over to another available clock source. Instead, the system goes into the
’holdover’ mode. The ’holdover’ mode is also set if both clock sources of the
master ACCG fail, even if the clock slave ACCG could still supply a satisfactory
clock.
The yellow LED on the face plate of ACCG starts the flashing when the input
clock on the ACCG fails.
The yellow LED is flashes also
• when the SSNC is created without external source clock
• during the warm-up / synchronization of the quartz after removing the ACCG h ... 2
(max. 6 minutes).

A50016-D3104-M470-3-7620 81
MMN:SSNC Maintenance
HW16 Signaling

2 Decision block
HW faults in the following units can also cause failure of the clock supply.
• Failure of the clock sources
• Clock-carrying PCM link (AIS, LOS, LOF...)
• Clock-carrying LIC module
• Clock-carrying ACCG module of the AMX
• ACCG module of the ASN (master).
Did the system report any other HW faults that point to failure of both clock
sources? Y h ...HW15
N h ... 3

3 Switch over of the master/slave function

In the following command the master ACCG must be configured to ’locked’ and
’unlocked’. This results in switch over of the master function.

Check that all units on the redundant units are fault-free and active (Operational
! state=Enabled, Standby state=Hot standby / Providing service, Alarm
state=Cleared, Under repair bit=false and no entry in Availability state) before
the configuration of ACCG(ASN) with Hazard check=Yes is executed.

b STAT AMX;
b STAT ASN;
b CONF ASN:Side=..,ACCG=..,Admin. state=Locked,Hazard check=Yes;
b CONF ASN:Side=..,ACCG=..,Admin. state=Unlocked;
Did you succeed in terminating the ’holdover’ mode? Y h ... 4
N h ... 5

4 Start fault clearance

It was possible to connect a clock source again for synchronization. For further
fault clearance of the redundant clock source, go to procedure HW15. h ...HW15

5 Start fault clearance

It was not possible to connect a clock source again for synchronization. For fur-
ther fault clearance go to procedure HW15. h ...HW15

END

82 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW17

2.19 Statistical Limit for Transient Faults

HW17

General notes and fault description

Transient faults are faults that occur during operation that cannot be verified by any di-
agnostics routine. Instead, these faults are registered by means of a statistical counter.
The statistical counter is incriminated by 1 if a fault is detected and decremented by 1 if
no further transient faults occur during the following 30 minutes. If the counter reaches
the threshold value 3, the relevant unit is configured to 'degraded' with an alarm, and to
'failed' if the threshold value 6 is reached. The fault message (HW17) is output whenever
either of these threshold values is reached. The unit can only be changed from the
'failed' state by manual intervention or by Periodic Fault Verification (PFV). In order to
prevent the 'failed' unit from being immediately reactivated by PFV, the process is delib-
erately delayed. The delay is achieved by incrementing the statistics counter (from 6, set
to 8) by a value of 1 every 30 minutes. On reaching the threshold value 8 the statistics
counter will be reset to 4 and periodic fault verification will be started. The unit is then
configured to 'enabled’ / ’degraded' and, once the statistics counter reaches the value
0, to the fault-free operational state (enabled / ...).
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Decision block

Which unit was reported as having reached a statistical limit or is still faulty?
– ASN-ACCG h ... 2
– AMXE-ACCG h ... 3
– MPU h ... 4
– both MPU from MP dependent h ... 9
– LIC h ... 5
– None h ... END
2 Statistics for ASN-ACCG
The reported and/or affected module is replaced using the procedure SNC16. i ...PROC: SNC16
When the module has been successful replaced, continue with h ... 6

3 Statistics for AMX-ACCG

The reported and/or affected module is replaced using the procedure SNC12. i ...PROC: SNC12
When the module has been successful replaced, continue with h ... 6

A50016-D3104-M470-3-7620 83
MMN:SSNC Maintenance
HW17 Signaling

4 Statistics for MPU

The reported and/or affected module is replaced using the procedure SNC13. i....PROC: SNC13
When the module has been successful replaced, continue with h ... 6

5 Statistics for LIC

The reported and/or affected module is replaced using the procedure SNC14. i....PROC: SNC14
When the module has been successful replaced, continue with h ... 6

6 Decision block
Is the statistical reporting limit reached again after replacing the module? Y h ... 7
N h ... 13

7 Decision block
Re-insert the previously replaced module.
– ASN modules using the procedure i....PROC: SNC16
– AMX modules using the procedure i....PROC: SNC12
– MPU module using the procedure i....PROC: SNC13
– LIC module using the procedure i....PROC: SNC14
– ALI module using the procedure i....PROC: HW23
Are other modules suspect? Y h ... 1
N h ... 8

8 Decision block
Was an dependent MPU changed/changed back? Y h ... 9
N h ... 14

84 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW17

9 Port errors (statistics for MPU)

A port error has occurred that is only detected if the MPU’s of an MP are operat-
ing micro synchronously. These transient port errors are always assigned to the
MPU. If the statistical limit is reached again after the MP modules have been re-
placed, it means the AMX modules may also be faulty.
The fault can be reported by both MPU’s of an MP. The MPU of an MP where
the statistical limit was reached first is configured to ‘failed’. If the statistical limit
is also reached with the redundant MPU, that MPU will be configured to ‘degrad-
ed’.
The associated AMX modules (side 0 and side 1, ’own’/reported module or ☞ ......Reported/affect-
ed module
’connected’ to the reported module) must be replaced one after the other using
procedure SNC12.
When the first (redundant) AMX module has been replaced, reactivation of the
MPU must be awaited or initiated by means of a command. Furthermore, when
an AMX module has been replaced it is necessary to wait and see if the statisti-
cal limit is reached again.
Have both AMX (side 0 and 1) been replaced? Y h ... 14
N i ...SNC12
Was the MPU in ‘failed’ reactivated? Y h ... 11
N h ... 10

10 Activating the MPU

The redundant MPU is configured from ‘degraded’ to ‘failed’ when the MPU in
‘failed’ is activated. If the statistics limit is reached again, The MPU which has
just been activated will be configured to ‘degraded’.

Determining the MPU in ‘failed’

b STAT MP:MP=..;

Activating the MPU in ‘failed’

b CONF MP:MP=..,Side=..,Admin. state=Locked,Hazard check=Yes;

b CONF MP:MP=..,Side=..,Admin. state=Unlocked; h ... 11
11 Decision block
Is the statistical limit reached again with this MPU? Y h ... 9
N h ... 12

12 AMX module faulty

The last replaced AMX module is faulty. h ... 13
13 Return module
Return the replaced module for repair with the remark ’Statistics fault’. h ... END

A50016-D3104-M470-3-7620 85
MMN:SSNC Maintenance
HW17 Signaling

14 Special fault clearance and statistical recording

The fault cannot be cleared using the standard fault clearance procedure. h ...NM:SSNC

END

86 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW19

2.20 Customer-Specific Alarms

HW19

General notes and fault description

A customer-specific alarm has been raised.This external alarm is reported through an
ASC interface (ALI module / Profi Bus Device) and forwarded to the MP(SA)
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Fault clearance

Take action in accordance with the customer’s working practice.

END

A50016-D3104-M470-3-7620 87
MMN:SSNC Maintenance
HW20 Signaling

2.21 Fuse Alarm

HW20

General notes and fault description

In every rack, it is the ACCG module in the first frame (MUT9) that detects the failure of
a circuit breaker (via the ALMC part of the fuse panel).
The units in frame SCE (MPU/LIC) are protected by one redundant fuse for each system
side. Consequently, the operation of a fuse in this frame does not result in the failure of
all MPU/LICs of a system side.
In frame F:SCB/SXCB, each system side is protected by one fuse.
Frame ASN contains 3 fuses per system side. Operation of one fuse results in the failure
of that system side of the ASN.
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Decision block

Is a fuse in the ASN frame affected? Y h ... 2

N h ... 6

2 ASN configuration
b CONF AMX:ACCG=..,Side=..,Side=Locked,Hazard check=Yes; h ... 3
3 Preparation the fault clearance on-site
Provide the module(s)/unit(s) that are reported in the error message and are
given in the fault clearance procedure.
Start fault clearance on site. h ... 4
4 ASN fuse
Switch the power supply module off
Switch the fuse off ☞ ......Construction
Rack:SSNC

Remove all modules in this frame (not power supply module PSAG)
Switch the fuse on
Switch on the power supply module
Does the fuse remain activated (green LED is on)? Y h ... 16
N h ... 5

88 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW20

5 ASN (power supply module)

Switch the power supply module off
Replace power supply module
Switch the fuse on ☞ ......Construction
Rack:SSNC

Switch on the power supply module.

Does the fuse remain activated? Y h ... 16
N h ... 29

6 Preparation for fault clearance on site

Provide the module(s)/unit(s) that are reported in the error message and are
given in the fault clearance procedure.
Start fault clearance on site. h ... 7
7 Switch the fuse on
Activate the fuse in the fuse panel.
Does the fuse remain activated? Y h ... 8
N h ... 10

8 Decision block
Were all of the failed units reactivated (green LED lit only)? Y h ... 28
N h ... 9

9 Start fault clearance

Start fault clearance as specified in fault report or in accordance with the unit h ...PROC: PRO-
that has failed. CIN

10 Decision block

All modules that receive their power supply via the ’failed’ fuse must be re-
moved. In the case of units that have a redundant fuse (in F:SCE), the unit must
be deactivated first. Before deactivating the unit, make sure that sufficient re-
dundancy still remains. To find out which units receive power via the failed fuse,
consult the Construction Manual. ☞ ......Construction
Rack:SSNC

Which module still has to be deactivated before being removed?

– MPU h ... 11
– LIC h ... 12
– ACCG (AMXE or ASMX) h ... 13
– none: all units are already disconnected from the power supply by the failure
of the fuse, or all affected units have already been deactivated. h ... 14

A50016-D3104-M470-3-7620 89
MMN:SSNC Maintenance
HW20 Signaling

11 Configure MPU
b CONF MP:MP=..,Side=..,Admin. state=Locked,Hazard check=Yes; h ... 10
12 Configure LIC
b CONF LIC:LIC=..,Admin. state=Locked; h ... 10
13 Configure AMX/ACCG
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Locked,Hazard check=Yes
b CONF AMX:ACCG=..,Side=..,Admin. state=Locked,Hazard check=Yes h ... 10
14 Remove module
Remove all deactivated modules or modules disconnected from the power sup- h ... 15
ply.

15 Activate fuse
Activate the fuse in the fuse panel.
Does the fuse remain activated? Y h ... 16
N h ... 29

16 Connect module
Reconnect the first (next) module.
Does the fuse remain activated? Y h ... 18
N h ... 17

17 Replace module
Remove the last connected module and, if necessary, reactivate the fuse.
Connect replacement module.
Does the fuse remain activated? Y h ... 18
N h ... 19

18 Decision block
Do any more modules need to be connected? Y h ... 16
N h ... 20

19 Replace module
Remove the last connected module and, if necessary, reactivate the fuse. h ... 29

90 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW20

20 Decision block
Which module has to be reactivated?
– MPU h ... 21
– LIC h ... 22
– ACCG (AMXE/ASMX) h ... 23
– ASN h ... 24
– none: all units have been activated. h ... 28
21 Configure MPU
b CONF MP:MP=..,Side=..,Admin. state=Unlocked; h ... 25
22 Configure LIC
b CONF LIC:LIC=..,Admin. state=Unlocked; h ... 25
23 Configure ACCG (AMXE/ASMX)
b CONF AMX:ACCG=..,Side=..,Admin. state=Unlocked;
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Unlocked; h ... 25
24 Configure ASN
b CONF ASN:ACCG=..,Side=..,Admin. state=Unlocked; h ... 25
25 Decision block
Could the unit be activated correctly? Y h ... 27
N h ... 26

26 Fault clearance of the faulty unit

The faulty unit is cleared by means of suitable procedures. i ...PROC: PRO-

CIN

After successful fault clearance h ... 27

27 Decision block
Do any more modules need to be activated? Y h ... 20
N h ... 28

A50016-D3104-M470-3-7620 91
MMN:SSNC Maintenance
HW20 Signaling

28 Decision block

If these actions have cleared the fault, the green LED on the front panel of the
replacement modules is lit, but the red LED is off. Another way to check whether
fault clearance has been successful is to see whether the alarm has been can-
celed in the alarm protocol (alarm state=Cleared).

Could the fault be cleared? Y h ... END

N h ... 29

29 Nonstandard maintenance
The fault cannot be cleared using the standard fault clearance procedures. h ...NM:SSNC

END

92 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW21

2.22 Fan Alarm (top)

HW21

General notes and fault description

The fans in a fan tray/box are temperature-regulated – i.e., the revolution rate increas-
es/decreases with rising/falling temperature. They cannot always be visually inspected
due to the protective grids and the module frame located above/below the fans. The fan
tray/box alarms and the external alarms are registered by the ALCM and switched to the
ALIB. The alarms are administered and reported by the ACCG. The ALCM (at the rear
of the fuse bar), ACCG and cable connection cannot be discounted as fault sources in
the event of a fan alarm. A genuine fan alarm is activated by the failure of a fan in the
fan tray or the complete failure of the fan tray.
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Preparation for fault clearance on site

Provide the module(s)/unit(s) that are reported in the error message and are
given in the fault clearance procedure.
Start fault clearance on site. h ... 2
2 Activate fuse and fan tray
Check fuse and activate if necessary.
Check fan tray on/off switch and switch on if necessary. ☞ ......Construction
Rack:SSNC
h ... 3
3 Decision block
Could the alarm be canceled? Y h ... 8
N h ... 4

4 Disconnect alarm line

Disconnect alarm line on the fan tray ☞ ......Construction
FAN

h ... 5
5 Decision block
Could the alarm be canceled? Y h ... 6
N h ... 7

A50016-D3104-M470-3-7620 93
MMN:SSNC Maintenance
HW21 Signaling

6 Replace the fan tray

The alarm is caused by a faulty fan.

Replacing a fan tray is not part of standard fault clearance. h ... 10

7 Configure module ACCG

Reconnect the alarm line to the fan tray
b CONF AMX:ACCG=..AMX=1,Side=Admin. state=Locked,Hazard check=Yes
b CONF AMX:ACCG=..,Side=..,Admin. state=Locked,Hazard check=Yes
Replace ACCG.
b CONF AMX:ACCG=..,Side=..,Admin. state=Unlocked,
b CONF AMX:ACCG=..AMX=1,Side=Admin. state=Unlocked,
Was diagnosis completed without any faults being found? Y h ... 8
N h ... 9

8 Decision block

These actions have cleared the fault, if the alarm is canceled (alarm
state=Cleared). Another way to check whether fault clearance has been suc-
cessful is to see whether the alarm has been canceled in the alarm protocol
(alarm state=Cleared).

Could the fault be cleared? Y h ... END

N h ... 10

9 Reinsert original module

Remove the replacement module and reinsert the original module. h ... 10
10 Nonstandard maintenance
The fault cannot be cleared using the standard fault clearance procedures. h ...NM:SSNC

END

94 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW22

2.23 Fan Alarm (bottom)

HW22

General notes and fault description

The fans in a fan tray / box are temperature-regulated – i.e. their revolution rate increas-
es / decreases with rising / falling temperature. They cannot always be visually inspect-
ed due to the protective grids and the module frame located above / below the fans. The
fan tray / box alarms and the external alarms are registered by the ALCM and switched
to the ALIB. The alarms are administered and reported by the ACCG. The ALCM (at the
rear of the fuse bar), ACCG and cable connection cannot be discounted as fault sources
in the event of a fan alarm. A genuine fan alarm is activated by the failure of a fan in the
fan tray or the complete failure of the fan tray.
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Preparation for fault clearance on site

Provide the module(s)/unit(s) that are reported in the error message and are
given in the fault clearance procedure.
Start the fault clearance on site. h ... 2
2 Activate fuse and fan box
Check fuse and activate if necessary.
Check fan box on/off switch and switch on if necessary. ☞ ......Construction
Rack:SSNC
h ... 3
3 Decision block
Could the alarm be canceled? Y h ... 8
N h ... 4

4 Disconnect alarm line

Disconnect alarm line on the fan box ☞ ......Construction
FAN

h ... 5
5 Decision block
Could the alarm be canceled? Y h ... 6
N h ... 7

A50016-D3104-M470-3-7620 95
MMN:SSNC Maintenance
HW22 Signaling

6 Replace the fan box

The alarm is caused by a faulty fan.

Replacing a fan box is not part of standard fault clearance. h ... 10

7 Configure module ACCG

Reconnect the alarm line to the fan box
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Locked,Hazard check=Yes;
b CONF AMX:ACCG=..,Side=..,Admin. state=Locked,Hazard check=Yes;
Replace ACCG.
b CONF AMX:ACCG=..,Side=..,Admin. state=Unlocked;
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Unlocked;
Was diagnosis completed without any faults being found? Y h ... 8
N h ... 9

8 Decision block

These actions have cleared the fault, if the alarm is canceled (alarm
state=Cleared). Another way to check whether fault clearance has been suc-
cessful is to see whether the alarm has been canceled in the alarm protocol
(alarm state=Cleared).

Could the fault be cleared? Y h ... END

N h ... 10

9 Reinsert original module

Remove the replacement module and reinsert the original module. h ... 10
10 Nonstandard maintenance
The fault cannot be cleared using the standard fault clearance procedures. h ...NM:SSNC

END

96 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW23

2.24 ALI Fault

HW23

General notes and fault description

This alarm is raised when a fault is suspected in module ALI.
Caution: The ETHERNET interface (HUB over AUI) is dependent on the power supply
to the ALI module, in other words: if the HUB over AUI is used in the ETHERNET inter-
face, there is no connection to the network management system after the ALI module
has been pulled.
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Preparation the fault clearance on-site

Provide the modules/units that are reported in the error message and are given
in the fault clearance procedure.
Start the fault clearance on-site. h ... 2
2 Decision block
Which LED is lit (see module faceplate)?
– green only (RUN) h ... 4
– green and red (RUN, ERROR) h ... 5
– red only (ERROR) h ... 5
– none h ... 3
3 Power faults
Check the fuse and activate if necessary. ☞ ......Construction
Rack SSNC

If the power was disconnected by the over voltage protection, the only way to re-
activate the fuse/module is to pull and reinsert the module.

Pull module and reinsert.

Was the module reactivated after its self-test (green LED lit only)? Y h ... 7
N h ... 5

A50016-D3104-M470-3-7620 97
MMN:SSNC Maintenance
HW23 Signaling

4 Reset the ALI

Pull module and reinsert.

After connection of the ALI module, the red LED is on for a short time before the
the green LED becomes on.

Was the module reactivated after its self-test (only green LED is on)? Y h ... 7
N h ... 5

5 Replace module ALI

Replace the reported module ALI.
Wait for it to be reactivated.
Has the unit been reactivated (only green LED is on)? Y h ... 7
N h ... 6

6 Reinsert original module ALI

It was not possible to reactivate the ALI. The replaced original module is there-
fore not the cause of the fault and can be reinserted.

Remove the replacement module and reinsert the original ALI module. h ... 8
7 Decision block

If these actions have cleared the fault, the green LED on the front panel of the
replacement modules is lit, but the red LED is off. Another way to check whether
fault clearance has been successful is to see whether the alarm has been can-
celled in the alarm protocol.

Could the fault be cleared? Y h ... END

N h ... 8

8 Nonstandard maintenance
It is not possible to clear the fault by the standard fault clearance procedures. h ...NM:SSNC

END

98 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW30

2.25 Inconsistency in ASN (ASN20/ASN40)

HW30

1 General notes and fault description

This fault can only occur during initial installation or when upgrading from
ASN20 to ASN40.
The ASN used in the system does not match the ASN expected in the database.
Either an ASN20 is installed in the system and an ASN40 is expected in the da-
tabase, or an ASN40 is installed and an ASN20 is expected in the database.

2 Step 1
Determine whether the correct ASN has been ordered and delivered.
If the wrong HW was delivered, then
- check the entire HW
- re-install the HW

3 Step 2
Verify that the correct SW has been ordered and delivered.
If the wrong SW was delivered, then
- re-order the SW

END

A50016-D3104-M470-3-7620 99
MMN:SSNC Maintenance
HW41 Signaling

2.26 Radio Clock Fault

HW41

General notes and fault description

• The following can cause this alarm:

– No radio signal was received at DCF77 for longer than 20 hours.
– No radio signal was received at GPS clock for longer than 4 hours.
– The MP detected 3 consecutive faulty time telegrams.
– The MP detected 6 faulty time telegrams within 1 hour
– Faulty radio clock
– Faulty antenna
– The ALI module was removed or is faulty
– Faulty interface (cable) between the radio clock receiver
– Faulty interface (cable) between the ALI and the MP.
– Faulty interface (cable) between the radio clock and the ALI.
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Decision block (ALI module)

Was the ALI module removed or reported to be faulty? Y h ... 2

N h ... 3

2 ALI module

Fault clearance of the ALI module according to the failure report h ...PROC: PRO-
CIN

3 Decision block (sporadic alarm)

Does this alarm only occur sporadically and for a short time? Y h ... 4
N h ... 5

4 Sporadic alarm

After 3 consecutive faulty/missing time telegrams, a correct time telegram was

again received by the MP and the alarm was reset. If this occurs repeatedly, a
statistical survey must be performed to determine further common features. h ... END

100 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW41

5 Decision block (radio)

Was a faulty radio signal DCF77 or radio signal GPS clock reported? Y h ... 6
N h ... 12

6 Failure of the radio service/signal

Was a faulty DCF77 radio signal or GPS radio signal detected at other radio
clocks? Y h ... 7
N h ... 8

7 Faulty sender

A faulty radio clock was not found in this exchange only. Presumably the sender
is faulty. h ... END

8 Preparation the fault clearance on-site

Provide the modules/units that are reported in the error message and are given
in the fault clearance procedure.
Start the fault clearance on-site. h ... 9
9 Radio clock
Check the receive direction of the radio clock (antenna).
Check the voltage supply of the radio clock.
Was a fault detected? Y h ... 10
N h ... 11

10 Decision block
Could the fault be eliminated? Y h ... 17
N h ... 18

11 Replace the radio clock

Replace the radio clock.
Was the alarm reset after the replacement? Y h ... 17
N h ... 18

12 Preparation the fault clearance on-site

Provide the modules/units that are reported in the error message and are given
in the fault clearance procedure.
Start the fault clearance on-site. h ... 13

A50016-D3104-M470-3-7620 101
MMN:SSNC Maintenance
HW41 Signaling

13 Interface fault (cable)

Check cable connection between the radio clock - ALI.
Was a fault detected? Y h ... 14
N h ... 15

14 Decision block
Could the fault be eliminated? Y h ... 17
N h ... 18

15 Interface fault (radio clock)

Replace the radio clock.
Was the alarm reset? Y h ... 17
N h ... 16

16 Interface fault (ALI)

Replace ALI.
Was the alarm reset? Y h ... 17
N h ... 18

17 Decision block

If these actions have cleared the fault, the green LED on the front panel of the
replacement modules is lit, but the red LED is off. Another way to check whether
fault clearance has been successful is to see whether the alarm has been can-
celled in the alarm protocol (alarm state=Cleared).

Could the fault be cleared? Y h ... END

N h ... 18

18 Nonstandard maintenance
It is not possible to clear the fault by the standard fault clearance procedures. h ...NM:SSNC

END

102 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling HW98

2.27 Cabling Fault

HW98

1 General notes and fault description

A fault in the cabling has been detected. This error can only occur during com-
missioning or when a switch is being expanded.

The replacement of cables and connectors is nonstandard maintenance. h ...NM:SSNC

END

A50016-D3104-M470-3-7620 103
MMN:SSNC Maintenance
HW99 Signaling

2.28 Nonstandard Maintenance

HW99

1 General notes and fault description

Using NM:SSNC for saving of Error Symptoms h ...NM:SSNC

NON

END

104 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling LI01

2.29 Fault in a Signaling Link Set

LI01

1 General notes and fault description

The last signaling link in a link set has failed.

Fault clearance is to be carried out for one failed signaling link of the alarmed
link set according to MMN:SSNC, procedure LI02. h ...PROC: LI02

END

A50016-D3104-M470-3-7620 105
MMN:SSNC Maintenance
LI02 Signaling

2.30 Fault in a Signaling Link

LI02

General notes and fault description

• Failure report
The failure reasons specified here are output only in the spontaneous system mes-
sages, i.e. the alarm message does not include this message. Should there be no
fault clearance notes because of this alarm message, the reason for the failure must
be taken from the appropriate spontaneous system message.
• Failure of one signaling link: (narrow band)
The failure of a single signaling link is generally caused by an external fault.
• Failure of more than one signaling link:
In the MP platform, there is redundancy for all L1 hardware units, and therefore there
must be a double fault before signaling links fail as the result of a hardware fault. But
this can then lead to mass failure of signaling links.
• Mass-out of service for signaling link
To avoid a mass of message overflow, in case of a mass out of service of signaling
links, not all signaling links that are out of service are reported. The number of mes-
sages is limited by a threshold value. Therefore it is possible that a link out of service
message is reported in a partner exchange but not in the local exchange. Other
messages of links still out of service that were kept back are reported as soon as the
threshold limit is not exceeded any more.
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Decision

Was this procedure entered from procedure LI01 (Signaling link set failure)? Y h ... 2
N h ... 3

2 Signaling link set failure

For a link set failure (no physical unit) a link of the alarmed link set must be
cleared first. Clearing the link failure will also reset the link set failure. h ... 52

106 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling LI02

3 Probable causes for failure are as follows:

Continue fault clearance in accordance with the reason for failure.
– Unreasonable BSN h ... 4
– Unreasonable FIB h ... 5
– AFM totally out of service h ... 6
– Alarm Indication Signal (AIS) h ... 7
– Alignment not possible h ... 8
– ATM cell loss h ... 9
– Blocked single channel transmission h ... 10
– Consecutive SSCP recoveries detection h ... 11
– HW fault detected MTCSM h ... 12
– Excessive delay of acknowledgement h ... 13
– Congestion lasts too long h ... 14
– Error rate high h ... 15
– Flag stream lasts too long h ... 16
– L2 internal job not processed h ... 17
– IWP not exist h ... 18
– IWP VC not exist. h ... 19
– Level 1 loop h ... 20
– L1 not switched h ... 21
– L3 changeover order from remote L2 h ... 22
– L3 test ackn. not received h ... 23
– L3 test ackn. not same link h ... 24
– L3 test pattern not ok h ... 25
– Lack of resources. h ... 26
– Lack of interworking trunk resources h ... 27
– LIC failure h ... 28
– LIC or LIC port not exist h ... 29
– No credit from peer h ... 30
– No ackn. from L2 to SLMC h ... 31
– No response from peer h ... 32
– No ackn. from SLMC to L2 h ... 33
– No ackn. from SLT h ... 34
– No ackn. from OAM h ... 35
– No ackn. from SM h ... 36
– Oscillating link h ... 37
– ATM port entry rejected h ... 38
– Remote L2 sends SIOS h ... 39
– Remote processor outage h ... 40
– Remote release h ... 41

A50016-D3104-M470-3-7620 107
MMN:SSNC Maintenance
LI02 Signaling

– SLT failure h ... 42

– TC adapt. not exist. h ... 43
– SM unavailable for more than ten minutes h ... 44
– Unknown internal failure h ... 45
– Unknown outward failure h ... 46
– Unreasonable SSCF PDU h ... 47
– Unreasonable SSCOP PDU h ... 48
– Unreasonable SU h ... 49
– VP not exist h ... 50
– No additional information h ... 51
– For any other entry, refer to: i....PROC:
REAS:LINK
h ... END
4 Unreasonable BSN

L2 has detected too many BSN faults. In 3 consecutive BSNs, 2 BSNs were re-
ceived which did not have the expected contents. This reaction can occur after a
changeover. However, L3 will automatically put this signaling link back into oper-
ation. Fault clearance must be carried out if L3 cannot automatically put this sig-
naling link into operation again.

Action:
– Reconnect the signaling link
– Inform partners h ... 52
5 Unreasonable FIB

L2 has detected too many FIB faults. In 3 consecutive FIBs, 2 FIBs were re-
ceived which did not have the expected contents. This reaction can occur after a
changeover. However, L3 will automatically put this signaling link back into oper-
ation. Fault clearance must be carried out if L3 cannot automatically put this sig-
naling link into operation again.

Action:
– Reconnect the signaling link
– Inform partners h ... 52
6 AFM totally out of service

Total AFM failure between two MPs of load type SLT or between an MP of load
type SM and the AMP processor.

Action:
– Check the affected cable connection(s).
– Check the affected MP. h ... 52

108 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling LI02

7 Alarm Indication Signal AIS

In case of AIS/RDI fault please check the VP_EP of the affected LIC. VP_EP h ... 52
must be defined on port 0. Otherwise RDI will not be generated.

8 Alignment not possible

Alignment was not achieved (L1). This can only occur during commissioning.
The creation data of the signaling link in this switch do not match those at the re-
mote end, or the routing is incorrect

Action:
– Check the data of the L1 path
– New start of L2
– Inform remote end. h ... 52
9 ATM cell loss

Loss of ATM cells from the LIC/MP. L2 is no longer receiving ATM cells from the
LIC. Fault in MP or LIC

Action:
– Reconfigure the affected MP
– Reconfigure the affected LIC
– Check the clock supply (ACCG) h ... 52
10 Blocked single channel transmission
Action:
– Check the data of the L1 path
– Check the corresponding port modes h ... 52
11 Consecutive SSCP recoveries detection

Consecutive SSCOP recoveries were detected on a high speed link. A protocol

fault was detected and by means of a recovery, an attempt is made to synchro-
nize the sequence number. The signaling link is deactivated within 1 hour after 2
recoveries.

Action:
– Inform partners h ... END

A50016-D3104-M470-3-7620 109
MMN:SSNC Maintenance
LI02 Signaling

12 HW fault detected MTCSM

The failure of a signaling link as the result of a hardware fault has been detect-
ed. The associated hardware reason for failure has been lost, and, as a substi-
tute, HW FAULT DETECTED MTCSM was recorded, or a MOD SIGLINK
command was only partially executed.

Action:
– Check the L1 hardware states.
– Check the data of the L1 path.
– New start of L2 h ... 52
13 Excessive delay of acknowledgement

L3 acknowledgment timeout. The remote end is not responding due to protocol

problems.

Action:
– Inform partner h ... END
14 Congestion lasts too long

Excessive overload duration.

Action:
– Perform statistical survey h ... END
15 Error rate high

L2 has detected an excessive number of transmission errors. There is a fault in

the local MPU(SLT) or in the remote MPU(SLT), or the signaling link is routed
over an unstable PCM link.

Action:
– Check the data of the L1 path.
– New start of L2. h ... 52
16 Flag stream lasts too long

Too many flags are being sent in succession.

Action:
– New start of L2 h ... 52

110 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling LI02

17 L2 internal job not processed

L2 internal job was not processed.

Action:
– New start of L2 h ... 52
18 IWP not exist

Interworking point does not exist. Or an incorrect IW point was created with CR
IWP.

Action:
– Check the data of the L1 path.
– Check the IWPSS7 data h ... 52
19 IWP VC not exist

Virtual channel to the interworking point does not exist. The IWP VC is used in-
ternally only and is created indirectly with CR IWPSS7. Only used for testing.

Action:
– none h ... END
20 Level 1 loop

L1 loop test ended unsuccessfully (loop is not released).

Action:
– Check the data of the L1 path.
– Reswitch signaling link h ... 52
21 L1 not switched

The internal L2 is reported, L1 is not switched

Action:
– Reconnect the signaling link h ... 52
22 L3 changeover order from remote L2

Change Over order received from the remote end. Signaling was changed over
to a redundant signaling link

Action:
– Check network data h ... 52

A50016-D3104-M470-3-7620 111
MMN:SSNC Maintenance
LI02 Signaling

23 L3 test ackn. not received

No L3 test acknowledgment received from remote end. No SLTA (Signal Link

Test Acknowledge) signal was received in response to sending an SLTM (Signal
Link Test Message). The signaling link does not terminate in the correct ex-
change, or the exchange to which the SLTM was addressed is not responding
(any more).

Action:
– Check network data h ... 52
24 L3 test ackn. not same link

L3 test acknowledgment was not received on the same signaling link. The sig-
naling link number in the SLTA (Signal Link Test Acknowledge) is incorrect. The
routing of the signaling link is faulty in the own exchange, in the remote ex-
change or on the transmission link.

Action:
– Check network data h ... 52
25 L3 test pattern not ok

Error during testing of the signaling link; the test pattern was incorrectly ac-
knowledged.

Action:
– Check affected MP(SLT) h ... 52
26 Lack of resources

Communication problem between different platforms

Action:
– Check the AMXE.
– Check the MP h ... 52
27 Lack of interworking trunk resources

The number of created trunks (IW trunks) is insufficient.

Action:
– Check the data of the L1 path.
– Check status of all affected IW trunks h ... 52

112 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling LI02

28 LIC failure

A fault was detected in the LIC.

Action:
– Carry out fault clearance as specified in the LIC failure message. h ...PROC: PRO-
CIN

29 LIC or LIC port not exist

LIC or LIC port does not exist. The LIC port has not been created or has been
created incorrectly.

Action:
– Check the data of the L1 path. h ... 52
30 No credit from peer

For a high speed link the ’No Credit’ timer expired before the synchronized SS-
COP entity could repeat the credit once by means of STAT PDU.

Action:
– Perform statistical survey h ... END
31 No ackn. from L2 to SLMC

No acknowledgment from L2 of the MP (SLT) to the SLMC of the MP (SM). The

communication between MP(SLT) and MP(SM) is disturbed. If all the signaling
links are affected, MP(SM) is the suspect unit. If only the signaling links of an
MP(SLT) are affected, only MP(SLT) is the suspect unit. Internal faults in
MP(SLT) caused, e.g., by recovery or (very rarely) by a double HW fault in
AMXE.

Action:
– Check affected MP(SM) and MP(SLT) or changeover h ... 52
32 No response from peer

For a high speed link the ’Keep Alive Function’ did not receive a STAT PDU in
reply to a POLL PDU for a longer period than specified in the ’No Response
Timer’ .

Action:
– Perform statistical survey h ... END

A50016-D3104-M470-3-7620 113
MMN:SSNC Maintenance
LI02 Signaling

33 No ackn. from SLMC to L2

No acknowledgment from the SLMC of the MP(SM) to L2 of the MP(SLT). The

MP(SM) or the MP(SLT) or the communication between both main processors is
disturbed.

Action:
– Check or change over the affected MP(SM) and MP(SLT)
– Check the affected cable connection h ... 52
34 No ackn. from SLT

No acknowledgment from MP(SLT).

Action:
– If this fault occurs for signaling links that work repeatedly with this MP, per- h ... 52
form diagnosis on the two MPUs, one after the other.

35 No ackn. from OAM

No acknowledgment from MP(OAM).

Action:
– If this fault occurs for signaling links that work repeatedly with this MP, per- h ... 52
form diagnosis on the two MPUs, one after the other.

36 No ackn. from SM

No acknowledgment from MP(SM).

Action:
– If this fault occurs for signaling links that work repeatedly with this MP(SLT), h ... 52
perform diagnosis on the two MPU(SLT), one after the other.

114 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling LI02

37 Oscillating link

The signaling link is unable to adopt a stable condition. Undefined signal se-
quences have been received on this signaling link (e.g. after recovery at the re-
mote end). Consequently, the signaling link was deactivated after ’X’ ms. L2
sends SIOS to the remote end, which responds likewise with SIOS. When the
remote end is ready to receive again (sending SIN, SLTM/SLTA, FISU), then the
signaling link is reactivated. If the remote end does not send SIN, SLTM/SLTA,
the own L2 sends SIOS to the remote end again. This alignment is repeated
continuously until it is possible to reactivate the signaling link.

If the signaling link oscillates for a time ’X’, the signaling link is deactivated for ’X’
ms.

Action:
– Check the PCM line h ... END
38 ATM port entry rejected

The connection manager was unable to switch an ATM path.

Action:
– Is usually corrected by an audit
– Reload the LIC (broadband)
– Reconnect the signaling link h ... 52
39 Remote L2 sends SIOS

The remote end sends SIOS. The send direction to the remote end is faulty; as
a result, the remote end does not receive any data and attempts to re-align
(sending SIOS).
The signaling link has failed.

Action:
– Inform remote end
– See also project specific operator hints h ... END
40 Remote processor outage

The processor (SLT) in the remote switch has failed.

Action:
– Inform remote end h ... END

A50016-D3104-M470-3-7620 115
MMN:SSNC Maintenance
LI02 Signaling

41 Remote release

The connection has been released in the remote switch.

Action:
– Inform remote end h ... END
42 SLT failure

An internal MP(SLT) has failed.

Action:
– Carry out fault clearance as specified in the MP/MPU failure message. h ...PROC: PRO-
CIN

43 TC adapt. not exist.

Transmission conversion adapter does not exist, only possible after set signaling
link (database error)

Action:
– Check the database. h ... END
44 SM unavailable for more than ten minutes

An internal MP(SM) has failed (for longer than 10 min.).

Action:
– Carry out fault clearance as specified in the MP/MPU failure message. h ...PROC: PRO-
CIN

45 Unknown internal failure

Unidentified internal fault. There are no error symptoms available. No hardware

fault has been reported, but nonetheless L2 is no longer working.

Action:
– Check the data of the L1 path.
– New start of L2
– Check the data of the NUC and the signaling link h ... 52
46 Unknown outward failure

Unidentified external fault.

Action:
– Inform remote end h ... END

116 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling LI02

47 Unreasonable SSCF PDU

Unreasonable SSCF PDUs (service-specific connection function protocol data

unit) were received on a high speed link.

Action:
– Reconnect the signaling link
– Inform partners h ... 52
48 Unreasonable SSCOP PDU

Unreasonable SSCOP PDUs (service-specific coordination protocol data unit)

were received on a high speed link.

Action:
– Reconnect the signaling link
– Inform partners h ... 52
49 Unreasonable SU

Unreasonable signaling unit. An SU was received which was not expected by

the protocol sequence.

Action:
– Reconnect the signaling link
– Inform partners h ... 52
50 VP not exist

Only for broadband signaling. Virtual path does not exist. The virtual path was
not created or created incorrectly.

Action:
– Check the virtual path h ... 52
51 No additional information
Action:
– Inform partners h ... 52

A50016-D3104-M470-3-7620 117
MMN:SSNC Maintenance
LI02 Signaling

52 Find and check the data for the internal L1 path

If necessary, the following commands can be used to obtain missing data.

b DISP SIGLINK:Link set name=..,Link code=..;

b DISP SIGDL:Net name=..,Data link name=..;
b DISP SIGDLLIC:Data link name=..;
b DISP SIGDLLIC:MP=..;
b DISP SIGDLLTG:Data link name=..;
b DISP SIGDLLTG:MP=..;
b DISP SIGLINKHW:MP=..,Net name=..;
b DISP IWP:IWP ID=..;
b DISP VPATH:TCS ID=..,VPI=..;

53 Perform fault clearance for the faulty unit

Which unit is not active and/or is to be tested, and/or which activity is to be car-
ried out next (see reason for failure block 2)?
– Test the cable connections h ... 54
– Check the clock supply (ACCG) h ... 55
– Reconnect the signaling link (NUC activation) h ... 58
– MPU diagnosis / new start of L2 h ... 64
– Switch over MPU / reload (STB to ACT) h ... 70
– Switch over LIC / reload (STB to ACT) h ... 76
– Congestion/overload situation h ... 83
– Check the network data h ... 84
– Check state of IW trunk h ... 85
– Check L1 data h ... 86
– Check virtual path h ... 87
– All units are active, no further action can be taken locally, inform remote end. h ... END
54 Test the cable connections
Check the cable connections between the affected units
using the standard cabling plan/installation documents.
Was a fault found? Y h ... 56
N h ... 82

118 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling LI02

55 Check the clock supply

b STAT AMX:Side=..,ACCG=..;
b DISP AMX:Side..,ACCG=..;
Make the following checks and correct where necessary:
– The ACCG must be active and alarm-free.
– Check the clock cable to AMXE and ACCG (reference clock)
– Check the LEDs on the module faceplate. ☞ ......Construction
Modules SSNC

Were any discrepancies found? Y h ... 56

N h ... 82

56 Decision block
Could the fault be cleared? Y h ... 57
N h ... 90

57 Decision block
Was it possible to reactivate the affected signaling link? Y h ... END
N h ... 82

58 Signaling link configuration

By configuring the signaling link, the L1 path through the SN is set up again and
the mismatch between operating states is resolved.
Execution of the modification command can take up to 30 seconds, so wait at
least that long before taking any further action.

b MOD SIGLINK:Link set name=..,Link code=..,Admin. state=Locked;

b MOD SIGLINK:Link set name=..,Link code=..,Admin. state=Unlocked;

If signaling is resumed after the deactivation and activation of the signaling link,
carry out a speech path test on the SN and diagnosis of the L1 units (LIC,
AMXE) that were previously involved in the L1 path, because it can be assumed
that the previously configured connection is faulty. This should be done at a time
when there is a low traffic load.

Did the signaling on the affected signaling link become active again on a new L1
path after deactivation/activation of the link? Y h ... 59
N h ... 82

A50016-D3104-M470-3-7620 119
MMN:SSNC Maintenance
LI02 Signaling

59 Identify changes to the L1 path

b DISP SIGLINK:Link set name=..,Link code=..;
b DISP SIGDL:Net name=..,Data link name=..;
b DISP SIGDLLIC:Data link name=..;
b DISP SIGDLLTG:Data link name=..;
b DISP SIGLINKHW:MP=..,Net name=..;
Compare the hardware units used in the L1 path.
Are different HW units in the L1 used in the new switching path? Y h ... 60
N h ... 89

60 Decision block
The suspect units must be diagnosed and/or replaced during a period of low
traffic load. Which HW unit(s) in the L1 path has (have) changed?
– AMXE
Diagnose/replace the AMXE module. h ... 61
61 Decision block (AMXE)
b STAT AMX:Side=..,ACCG=..,AMX=..;
Are both AMXEs (side 0/1) active? Y h ... 63
N h ... 62

62 AMXE fault clearance (AMXE)

Carry out AMXE fault clearance as specified in the failure message. i....PROC: PRO-
CIN
After completing fault clearance h ... 64
63 Replace the AMXE (AMXE)
b CONF AMX:Side=..,ACCG=..,AMX=..,Admin. state=Locked,Hazard check=Yes;
Replace the suspect AMXE.
b CONF AMX:Side=..,ACCG=..,AMX=..,Admin. state=Unlocked;
Was it possible to reactivate the AMXE without any error occurring? Y h ... END
N h ... 90

64 Decision block (MPU diagnosis)

b STAT MP:Side=..,MP=..;
Are both MPUs of the affected MP active? Y h ... 66
N h ... 65

65 MPU fault clearance (MPU diagnosis)

Carry out MPU fault clearance as specified in the failure message. i....PROC: PRO-
CIN
After completing fault clearance h ... 64

120 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling LI02

66 MPU diagnosis
b CONF MP:Side=..,MP=..,Admin. state=Locked,Hazard check=Yes;
b DIAG MP:Side=..,MP=..,Kind of diagnosis=Complete diagnosis;
Did the diagnosis end without faults? Y h ... 68
N h ... 67

67 Replace the MPU (MPU diagnosis)

Replace the suspect MPU
b CONF MP:Side=..,MP=..,Admin. state=Locked,Hazard check=Yes;
Was it possible to reactivate the MPU without any error occurring? Y h ... 68
N h ... 90

68 MPU activation (MPU diagnosis)

b CONF MP:Side=..,MP=..,Admin. state=Unlocked;
Was it possible to reactivate the MPU without any error occurring? Y h ... 69
N h ... 90

69 Decision block (MPU diagnosis)

Was it possible to reactivate the signaling link? Y h ... END
N h ... 82

70 Decision block (MPU reconfiguration)

b STAT MP:Side=..,MP=..;
Are both MPUs of the affected MP in state ACT/STB? Y h ... 72
N h ... 71

71 MPU fault clearance (MPU reconfiguration)

Carry out MPU fault clearance as specified in the failure message. i ...PROC: PRO-
CIN
After completing fault clearance: h ... 70
72 MPU reconfiguration

Deactivating the active MPU causes reconfiguration.

b CONF MP:Side=..,MP=..,Admin. state=Locked,Hazard check=Yes;

Did the signaling link become active again after reconfiguration? Y h ... 73
N h ... 74

A50016-D3104-M470-3-7620 121
MMN:SSNC Maintenance
LI02 Signaling

73 Replace the MPU (MPU reconfiguration)

Replace the faulty (deactivated) MPU.
b CONF MP:Side=..,MP=..,Admin. state=Unlocked;
Was it possible to reactivate the MPU without any error occurring? Y h ... END
N h ... 90

74 MPU activation (MPU reconfiguration)

b CONF MP:Side=..,MP=..,Admin. state=Unlocked;
Was it possible to reactivate the MPU without any error occurring? Y h ... 82
N h ... 75

75 Replace the MPU (MPU reconfiguration)

Replace the faulty (deactivated) MPU.
b CONF MP:Side=..,MP=..,Admin. state=Unlocked;
Was it possible to reactivate the MPU without any error occurring? Y h ... 82
N h ... 90

76 Decision block (LIC reconfiguration)

b STAT LIC:LIC=..;
Are the two LICs of the affected LIC pair in operating state ACT/STB? Y h ... 78
N h ... 77

77 LIC fault clearance (LIC reconfiguration)

Carry out LIC fault clearance as specified in the failure message. i....PROC: PRO-
CIN
After completing fault clearance: h ... 76
78 LIC reconfiguration

Deactivating the active LIC of the LIC pair causes reconfiguration.

b CONF LIC:LIC=..,Admin. state=Locked,Hazard check=Yes;

Did the signaling link become active again after reconfiguration? Y h ... 79
N h ... 80

79 Replace the LIC (LIC reconfiguration)

Replace the faulty (deactivated) LIC.
b CONF LIC:LIC=..,Admin. state=Unlocked;
Was it possible to reactivate the LIC without any error occurring? Y h ... END
N h ... 90

122 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling LI02

80 LIC activation (LIC reconfiguration)

b CONF LIC:LIC=..,Admin. state=Unlocked;
Was it possible to reactivate the LIC without any error occurring? Y h ... 82
N h ... 81

81 Reinsert the original LIC (LIC reconfiguration)

Remove the replacement unit and reinsert the original LIC. h ... 90
82 Decision block
Are there any further suspect units or can further fault clearance actions be per-
formed? Y h ... 53
N h ... 90

83 Overload
Overload protection is started automatically by the system.
Overload can be caused by any of the following:
– Circular routing
– Loading of one or more different processors in connection with high call pro-
cessing loads
– Recoveries in connection with high call processing loads
– Failure of one or more signaling links in connection with high call processing
loads
– Synchronization messages after partial or total failures
– Incorrectly planned alternative routes
Basically, overload is removed by the system - i.e., messages are held back by
the sending processors until the overloaded processor is no longer in the critical
area. However, messages may be discarded if the overload lasts too long. The
operator is informed in such cases by a separate message. All overload situa-
tions (apart from circular routing) usually last no longer than 2 minutes.
Was the overload situation cleared after about 2 minutes? Y h ... END
N h ... 84

84 Check the network data

Check the network data in consultation with the appropriate planning depart-
ments and/or cooperation partners.
Were any discrepancies found? Y h ... 88
N h ... 90

A50016-D3104-M470-3-7620 123
MMN:SSNC Maintenance
LI02 Signaling

85 Check the IW trunk state

Check the trunk state. If all trunks are busy, then this message is OK, otherwise
check the trunk data with the planning data. Discrepancies must be clarified with
the corresponding planning department and/or partner.

Was a discrepancy detected? Y h ... 88

N h ... 90

86 L1 Checking data
Check the following data with the planning departments and/or database. Make
any necessary corrections in accordance with the OMN:
– Trunk states must be active for the signaling link.
– Trunk data and position must match the signaling link.
– An IWPSS7 must also be created for each signaling link.
– The trunk group data must match the signaling link.
– The PCM system must match that of the remote end.
– The signaling link data must match those of the remote end.
– The signaling link must be assigned to the correct IWU group (0/1).
– The signaling link must interwork with the correct MP.
– The signaling link must be assigned to the correct trunk group.
Were any discrepancies found? Y h ... 88
N h ... 90

87 Check virtual path

Check the following data with the planning departments and/or database and
make any necessary corrections in accordance with the OMN:
– An IWPSS7 (LIC port) must also be created for each signaling link.
– The signaling link data must match those of the partner.
– The signaling link must interwork with the correct MP.
Was any discrepancy found? Y h ... 88
N h ... 90

88 Decision block
Depending on what actions need to be taken,
– Continue with OMN-TR h ...OMN-TR
– Or continue with OMN-SS7 h ...OMN-SS7

89 Maintain statistics
The fault is sporadic. Continue to observe the hardware used for the L1 path in h ... END
question.

124 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling LI02

90 Nonstandard maintenance
It is not possible to clear the fault by the standard fault clearance procedures. h ...NM:SSNC

END

A50016-D3104-M470-3-7620 125
MMN:SSNC Maintenance
LI03 Signaling

2.31 Fault in a Combined Signaling Link Set

LI03

1 General notes and fault description

Reserved for combined signaling link set

END

126 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling LI04

2.32 Overload on the Signaling Link

LI04

1 Fault description

The output list in the MP(SLT) for this signaling link has exceeded an occupancy
level limit. No more messages can be processed for destinations that are to be
routed via this signaling link. An overload message for these destinations is sent
to the originating SPC of the message. Basically, overload is removed by the
system, i.e. messages are held back by the sending processors until the over-
loaded signaling link (MP(SLT)) is no longer in the critical range. However, mes-
sages may be discarded if the overload lasts too long. Overload situations
(except for circular routing) do not normally last longer than 2 minutes. They are
reported to the operator as a quality of service alarm.
In the case of circular routing, any messages that have entered the loop will not
disappear but will circulate until the error has been cleared. This means that
overload persists until fault clearance has been performed.
Even brief overload situations, however, can also point to possible planning er-
rors, for example if (too) many OPCs have access to a destination via a single
alternative route or if circular routing only occurs when an alternative route is
used.
Overload can be caused by any of the following:
• Circular routing
– Action: Find out the origin and the destination of the messages and trace
the routing of the messages
• Loading of one or more processors on the partner’s side in conjunction with
a high call-processing load
– Action: None
• Recoveries on the partner’s side in conjunction with a high call-processing
load
– Action: None
• Failure of one or more signaling links in conjunction with a high call-process-
ing load.
– Action: Clear faults on signaling link
• Synchronization messages after partial or total failures
– Action: None
• Incorrectly planned alternative routes
– Action: Check the routing in the network, and modify the routing after con-
sultation with the partners and the planning departments.

END

A50016-D3104-M470-3-7620 127
MMN:SSNC Maintenance
LI05 Signaling

2.33 GA Signalling Link Alarm

LI05

1 General notes and fault description

This alarm is issued in case of total failure of a particular Ga link. When the pri-
mary and standby route for a particular Ga link fail (operational state transition
from “enabled” to “disabled”), the alarm is sent to the SC with parameters indi-
cating the primary and standby IP address of the link and whether GsFailure-
Buffering is enabled. If GaFailure Buffering is disabled, data loss may occur
during total Ga link failure.

END

128 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling LI06

2.34 Association Management for SCTP

LI06

General remarks and description of faults

The SCTP (Signaling Control Transfer Part) cannot route messages to the specified IP
address. The acronym is incorrect; it should read ’Stream Control Transmission Proto-
col’.
The alarm could be due to SCTP link congestion.
This may be due to a fault in the MPU(EN), MBIE, Ethernet, router, or in the partner unit.
Since all units are duplicated, there must be faults in two different units or components.
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Determine missing data

Use the following commands to find out whether any data is missing.

b DISP SCTPASSOC:SCTP association ID=..;

b STAT MP:MP=..;
b DISP SCTPASSOC:MP=..; h ... 2
2 Decision block
Is the own MP active (providing service, hot standby) and free of alarms? Y h ... 4
N h ... 3

3 Clear faults on MPU

Carry out fault clearance on the MP concerned, in accordance with the failure h ...PROC: PRO-
report. CIN

4 Decision block

For hints regarding inconsistency see ☞ ......CH:SSNC

Are there inconsistent states on the MP / MPU? Y h ...NM:SSNC
ALARM:MPU
N h ... 5

5 Decision block
Is the unit overloaded? Y h ... 6
N h ... 8

A50016-D3104-M470-3-7620 129
MMN:SSNC Maintenance
LI06 Signaling

6 SCTP Link Congestion

Congestion is regulated automatically by the system, so that any overloading

will disappear after a few minutes.

Was the end of overloading reported after approx. 3 minutes? Y h ... 7

N h ...PROC: OVER-
LOAD

7 Restore service
Was the resumption of SCTP traffic reported? Y h ... END
N h ... 8

8 Decision block
Was a fault reported between the MPU(EN) and the L2 switch? Y h ... 9
N h ... 12

9 Clear faults on Ethernet

Check the cable links between the MPU(EN) and the L2 switch
Check the L2 switch
Did you find a fault? Y h ... 10
N h ...NM:SSNC

10 Decision block
Were you able to clear the fault? Y h ... 11
N h ...NM:SSNC

11 Restore service
Was the resumption of SCTP traffic reported? Y h ... END
N h ... 12

12 Ethernet decision block

Check for failures within the Ethernet (Router...).
Are there any failures? Y h ... 13
N h ... 14

13 Clear faults on Ethernet

Pass on the fault to the appropriate department. h ... END

130 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling LI06

14 Inform the partner unit

No fault was identified in the own area. Notify the relevant partner unit. h ... END

END

A50016-D3104-M470-3-7620 131
MMN:SSNC Maintenance
DATA:MPU Signaling

2.35 Setting the MPU(SA) Data

DATA:MPU

General remarks and description of faults

This procedure only concerns the MPU(SA) in the Basic Frame/Rack and
i is not relevant for the MPU(SA) for OAMD used in the Extended Basic Frame

After replacement of an MPU(SA) module in the Basic Frame/Rack it is necessary to

check and/or correct the office data of the MPU(SA) concerned.
If these data are not checked and - if necessary - corrected, this may later result in un-
controllable system behavior.
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Decision block

Availability of exchange-specific installation data for the ’Communication setup

session’
Are the exchange-specific installation data available? Y h ... 2
N h ...NM:SSNC
INST:DATA

2 Connecting the local operating terminal (setting the installation data)

Connect the local operating terminal to the V24 interface of the MPU which had
to be replaced:
Start the Hyper Terminal program.
The following settings must be made
– Baud: 9600
– Data Bit: 8
– Parity: no
– Stop Bit: 1
– Flow Control: Xon/Xoff h ... 3

132 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling DATA:MPU

3 Resetting the MPU (setting the installation data)

Reset the MPU concerned by means of the Reset switch on the module face-
plate:
b Enter CTR X on the Hyper Terminal
The main menu is started
b Select: Communication Setup Session
The installation data are displayed
1. Change IP address of the switching MPU
from: ###.###.###.###...........................to: ??
2. Change Managed element id of the switching MPU
from: ###.###.###.###...........................to: ??
3. Change IP address of the nonswitching MPU
from: ###.###.###.###...........................to: ??
4. Change Managed element id of the non-switching MPU
from: ###.###.###.###...........................to: ??
5. Change the IP address of host
from: ###.###.###.###...........................to: ??
6. Change Load Type from: ####................to: ??
7. Change Core Configuration from: ##........to: ??
8. Change Type of Load Disk from: ##........to: ??
9. Change Project Name from: ## .............to: ??
19. Save and changed and return to parent menu
0. Discarded changes and return to patent menu
Please enter a digit to select an action and <CR> to proceed
Do the installation data match the exchange-specific data? Y h ... 4
N h ... 5

4 Installation data correct

Disconnect the Communication Setup with
b 0. Discarded changes and return to patent menu h ... 6
5 Correction and save installation data
b Please enter a digit to select an action and <CR> to proceed
b Write the correct data
b 19. Save and changed and return to parent menu h ... 6

A50016-D3104-M470-3-7620 133
MMN:SSNC Maintenance
DATA:MPU Signaling

6 End
End the Hyper Terminal program and disconnect the operating terminal
Reset the relevant MPU by means of the Reset switch on the module faceplate.
Before any other actions are carried out, all update and synchronization mea-
sures (after Reset) must have been completed and redundancy must have been
established for all system-relevant units.

END

134 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling OVERLOAD

2.36 Congestion on the Signaling Link

OVERLOAD

1 Fault description

The output list in the MP(SLT) for this signaling link has exceeded an occupancy
level limit. No further messages can be processed for destinations which are to
be routed via this signaling link. An congestion message for these destinations
is sent to the originating SPC of the message. Basically, congestion is removed
by the system, i.e. messages are held back by the sending processors until the
overloaded signaling link (MP(SLT)) is no longer in the critical range. However,
messages may be discarded if congestion lasts too long. Overload situations
(except for circular routing) do not normally last longer than 2 minutes.
A congestion quality of service alarm will only be reported if a traffic measure-
ment has been created for this signaling link (CR SIGFAIME:Measurement
type=Signaling link,Link set name=..,Link code=..;),
In the case of circular routing, any messages that have entered the loop will not
disappear but will circulate until the error has been cleared. This means that
overload persists until fault clearance has been performed.
Even brief overload situations, however, can also point to possible planning er-
rors, for example if (too) many OPCs have access to a destination via a single
alternative route or if circular routing only occurs when an alternative route is
used.
Hints:
The congestion is determined from system and registered and alarmed from the
traffic measurement. The alarm message will be repeated every 5 min., until the
overload is removed. If the overload can not be removed, the measurement can
be stopped. No further alarm messages are reported then. The following com-
mands are used to stop / start the measurement for a signaling link.
CAN SIGFAIME:Measurement type=Signaling link,Link set name=..,Link
code=..;
After the overload has been removed, the measurement can / must be started
again.
CR SIGFAIME:Measurement type=Signaling link,Link set name=..,Link code=..; h ... 2

A50016-D3104-M470-3-7620 135
MMN:SSNC Maintenance
OVERLOAD Signaling

2 Reason
Overload can be caused by any of the following:
• Circular routing
– Action: Find out the origin and the destination of the messages and trace
the routing of the messages
• Loading of one or more processors on the partner’s side in conjunction with
a high call-processing load
– Action: None
• Recoveries on the partner’s side in conjunction with a high call-processing
load
– Action: None
• Failure of one or more signaling links in conjunction with a high call-process-
ing load.
– Action: Clear faults on signaling link
• Synchronization messages after partial or total failures
– Action: None
• Incorrectly planned alternative routes
– Action: Check the routing in the network, and modify the routing after con-
sultation with the partners and the planning departments.

END

136 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling NOTI

2.37 Notification

NOTI

1 General remarks and fault description

A notification message is an indication of abnormal system behavior without in-

fluence on the system performance. Normally no further action is necessary.
Therefore no entry to the maintenance manual is provided.

Action may be necessary for the following notification message:

– EVENT TYPE clockAlarmNotification h ... 2
– EVENT TYPE relationschipChange h ... 3
2 EVENT TYPE clockAlarmNotification
MANAGED OBJECT CLASS clockSource
EVENT INFORMATION clockAvailable FALS h ...PROC: HW15
3 EVENT TYPE relationschipChange
MANAGED OBJECT CLASS clockSource
EVENT INFORMATION newAttributeValue ArtSource: holdover h ...PROC: HW16

END

A50016-D3104-M470-3-7620 137
MMN:SSNC Maintenance
QOSAL Signaling

2.38 Quality of Service Alarm

QOSAL

1 General remarks and fault description

A quality of service alarm is an indication of abnormal system behavior which

may also interfere with the system performance. The faults concerned are usu-
ally not to be found in the exchange sending the alarm but in one of the adjacent
exchanges. Quality of service alarms are spontaneous messages that are dis-
played in the surveillance. Normally no further action is necessary. Therefore no
entry to the maintenance manual is provided.

Action may be necessary for the following quality of service alarms:

– Signaling Link Congestion Data h ...PROC: LI04
– Signaling Point Data h ...PROC: RO02

END

138 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling RO01

2.39 DPC Not Accessible

RO01

General notes and fault description

A DPC has become inaccessible. Either the last signaling link to this DPC has failed, or
a TFP (transfer prohibited message) message from partner L3 for this DPC has been
received in the network.
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Decision block

Does the error message contain sufficient information on the fault to allow fault
clearance to be carried out? Y h ... 2
N h ... 8

2 Fault clearance
b DISP SIGROUTE:Net ID=..,DPC=..;
b DISP SIGLINK:Link set name=..;
Are there any signaling links in operating state Locked? Y h ... 3
N h ... 4

3 Links in Locked
b MOD SIGLINK:Link set name=..,Link code=..,Admin. state=Unlocked;
Are there any more signaling links in operating state Locked? Y h ... 3
N h ... 4

4 Links in Disabled
Are there any signaling links in operating state Disabled? Y h ... 5
N h ... 6

5 Link in Disabled

Determine the reason for the Disabled. state of the signaling link from the error
message and start fault clearance with LI02. h ...PROC: LI02

6 DPC with TFP (transfer prohibited message)

Has a TFP message been received for this DPC? Y h ... 7
N h ... 8

A50016-D3104-M470-3-7620 139
MMN:SSNC Maintenance
RO01 Signaling

7 DPC with TFP (transfer prohibited message)

The fault does not lie in this exchange. Report the fault to the DPC specified in h ... END
the error message.

8 Nonstandard maintenance
It is not possible to clear the fault by the standard fault clearance procedures. h ...NM:SSNC

END

140 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling RO02

2.40 Discarded MSU

RO02

1 General remarks and fault description

This quality of service alarm is output if messages are discarded because of a

routing data error. The first discarded MSU that occurs within a 5-minute period
is output.
The additional information that is output can be evaluated by means of the ta- ☞ ......PROC:
REAS:DIS-
bles REAS:DISCARD and MSG:DISCARD.
CARD

☞ ......MSG:DISCARD
These routing data or network errors can originate in the own exchange or in an
adjacent exchange, or even in a non-adjacent exchange. Whichever is the case,
the data must be corrected in cooperation with the partner exchanges and the
corresponding planning departments.
To create or modify routing data and to block or activate traffic relations, follow h ... 2
the instructions in the OMN.

A50016-D3104-M470-3-7620 141
MMN:SSNC Maintenance
RO02 Signaling

2 Cause of error
The following points must be clarified:
• Were incorrect values entered for the created CICs?
– Action: Correct the CIC data.
• Do the line types and the CIC no. of the created trunks differ from the data of
the partner exchange?
– Action: Correct the numbering of the CICs within the PCM system.
Correct the line type.
• Is the DPC (still) blocked?
– Action: Activate the DPC or block the traffic relation in the partner ex-
change.
• Is no trunk group assigned to this destination?
– Action: Create a link between USER and trunk group.
• Is the routing for the trunk signaling correct (i.e., do the messages reach the
CP in the destination exchange and do the corresponding acknowledge-
ments from the CP of the destination exchange get back to the own CP)?
– Action: Check the routing of the signaling link in all exchanges involved.
• Does the DPC have to be known in the own exchange?
– Action: Create and activate the DPC or deactivate and cancel the DPC.
• Is the traffic relation DPC-OPC allowed?
– Action: Create and activate the DPC
• Has the routing data been created correctly in the partner exchange?
– Action: Modify the routing table.
• In a signaling link set with several signaling links, have the signaling link num-
bers been mixed up?
– Action: If signaling links have been created incorrectly, cancel and create
them correctly.
• Is there a mistake in the signaling link connection?
– In the case of incorrect internal connections in the PCM system, cancel
and create them correctly again.
– In the case of incorrect external connections in the PCM system, pass on
the fault
• A subsystem number (SSN) was received that is not known here.
– Action: Check whether the sender is allowed to send this SSN or
whether this SSN has still to be enabled in the own exchange.
The actions suggested here may only be carried out if it is quite clear that there
are differences
– between the actual status and the desired status
– between the documents of the own exchange and the partner exchange
– in the database.
h ... 3

142 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling RO02

3 Determining the created routing data

If necessary, missing data can be determined by means of the following com-

mands. Choose the command sequence in such as way that missing parameter
values are provided by the outputs of the previous commands.

b DISP SIGPOINT
b DISP SIGDP
b DISP SIGDPGRP
b DISP SIGLSET
b DISP SIGLINK
b DISP SIGROUTE
b DISP SIGDLHW
b DISP SIGLINKHW
b DISP TGRP
b DISP TRUNK h ... 4
4 Decision block
Depending on what actions need to be taken,
– Continue with OMN-TR h ...OMN-TR
– Or continue with OMN-SS7 h ...OMN-SS7

END

A50016-D3104-M470-3-7620 143
MMN:SSNC Maintenance
SE01 Signaling

2.41 Security Alarm, Threshold for Security Trace File Reached

SE01

1 General remarks and description of faults

This occupancy level alarm for the file GT.Q3SECTR.LOG is sent after the 70%,
95% and 100% levels have been reached, whereby 70% and 95% are default
values and can be changed. When the occupancy level has reached 100% the
system automatically performs DMP SECTR, with the result that the existing
GT.Q3SECTR is overwritten. For this reason, the data should be saved at the
latest when the occupancy level has reached 95%.
This file contains all database-modifying Q3 Requests (M-Create, M-Set, M-De-
lete, M-Action) and the associated responses for the MP platform, which are
sent by the Switch Commander. h ... 3

2 Decision block
What capacity level has been reached?
– 70% h ... 3
– 95% h ... 3
– 100% h ... 4
3 Capacity levels of 70% and 95%

The file GT.Q3SECTR.LOG is 75 (95)% full. The following command can be

used to save the data in a file GT.Q3SECTR and to cancel the alarm.

The command will not be executed unless the file was previously copied to SC
with RCV FILE and deleted on MDD(MP) with the command DEL FILE.

b DMP SECTRC; h ... 4

144 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SE01

4 Occupancy levels 70%, 95% and 100%

The following command is used to copy file GT.Q3SECTR from the MDD(MP) to
the SC.

b RCV FILE:SOURCE FILE NAME=\GT.Q3SECTR,DESTINATION FILE

NAME=..,TRANSFER TYPE=..,FILE WRITING MODE=.., COPY MODE=BINA-
RY;

The following command is used to delete file GT.Q3SECTR on MDD(MP).

When an occupancy level of 100% is reached, the alarm is not ed until this file
has been deleted.

b DEL FILE:FILE=\GT.Q3SECTR;

END

A50016-D3104-M470-3-7620 145
MMN:SSNC Maintenance
SE02 Signaling

2.42 Security Alarm, Cannot Write to File

SE02

1 General remarks and description of faults

This alarm is set when the Security Tracer cannot write in the file
GT.Q3SECTR.LOG. This can only occur if the file system has been manipulat-
ed. h ... 2

2 Decision block

If, due to hardware faults in MPU(SA) and/or MDD, both MDDs are not available,
HW fault clearance must first be carried out using the appropriate procedure.

Are both MDDs unavailable, due to HW faults? Y h ... 3

N h ... 4

3 HW faults

Carry out hardware fault clearance first by means of a suitable failure report. h ...PROC: PRO-
CIN

4 Fault clearance

In order for fault clearance to be performed, an authorized administrator has to

cancel the file protection so that the file GT.Q3SECTR.LOG can be deleted.

Deactivate the Security Tracer

b MOD SECTRC:Tracer status=Disabled;

Delete the LOG file.

When the file is deleted, the system generates a new file.

b DEL FILE:FILE=\GT.Q3SECTR.LOG;

Activate the Security Tracer

b MOD SECTRC:Tracer status=Enabled;

END

146 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SE03

2.43 Threshold Value for Log Instance Reached

SE03

1 Description

A threshold has been exceeded for the log instance specified in the occupancy
level alarm. DISP EVLOG can be used to determine all log instances and the
associated data.
The threshold values are set between 1....100% when the log instance is creat-
ed. A maximum of 5 threshold values can be specified per log instance, and as
the occupancy level rises the corresponding alarm can be sent with a higher ur-
gency level. It is also possible to specify whether, when the 100% threshold is
reached, the log instance is to be overwritten cyclically or whether recording in
the log instance is to be stopped. Backup of the log instances should be com-
pleted before an occupancy level of 100% is reached.
Note:
Three log instances are created for alarm surveillance. These three instances
can be created with or without a threshold value, depending on the user. If they
are created with a threshold value, an alarm will be sent when the threshold val-
ue is reached. In this case, do not reset the occupancy level indicator of these
instances with CAN EVREC, because this will cause problems in the alarm sur-
veillance. The instances for which CAN EVREC cannot be used are:
• SAL_otto
• DET_otto
• otto
where the operator is free to enter any name for ’otto’ when creating the instanc-
es (’otto’ is the same for all three instances).

2 Decision block
Was a threshold value of 90% or more reached? Y h ... 4
N h ... 3

3 Decision block
Must/should backup of the log instance be performed, although the threshold
value of 90% has not yet been reached? Y h ... 4
N h ... 7

A50016-D3104-M470-3-7620 147
MMN:SSNC Maintenance
SE03 Signaling

4 Backup of the log instance

Backup of the log instance (copying the file to the SC) is performed by means of
the command shown below. Logging and storage of the log instances on the SC
may have a disruptive effect on further operation. For this reason it is advisable
to start the following command by means of a timer job via the ’Task Schedule’
of the SC.

b DISP EVREC:Event log=name..; h ... 5

5 Decision block

Determining the instances that must not be reset using CAN EVREC .

b DISP EVLOG;
Was a log instance SAL_’otto’, DET_’otto’ or ’otto’ saved (see note in block 1)? Y h ... 7
N h ... 6

6 Release of the log instance

The occupancy indicator is reset by means of the following command.

b CAN EVREC:Event log=name..;

When the command has been executed, the log instance is available again un-
der the same name. h ... 7

7 Resetting the alarm

Until the next threshold value is reached, the alarm can be canceled by means h ... END
of the cancel button in the Alarm Surveillance.

END

148 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SE04

2.44 Threshold for Occupancy Level of MOD/MDD reached

SE04

1 Description

A threshold has been exceeded for the ’Logical storage name’(MDD/MOD)

specified in the occupancy level alarm.

2 Decision block
Object Instance:
– Logical storage name= MODx h ... 3
– Logical storage name= MDDx h ... 4
3 Procedure for MOD
End all write processes on MOD.
Close all open files.
b CONF MODMP:Side=..,Administrative State=locked;
Replace storage medium (new CD).
b CONF MODMP:Side=..,Administrative State=unlocked,Label=Yes;
Keep the replaced storage medium (CD) for data backup.
Continue the process that was interrupted. h ... END
4 Procedure for MDD
Check for superfluous files
b LIST FILE:DIRECTORY NAME=..; h ... 5
5 Decision block
Were superfluous files found? Y h ... 6
N h ... 8

6 Cancel files
b CAN FILE:TRANSFER TYPE=..,FILE NAME=..; h ... 7
7 Reset alarm
Until the next threshold is reached the alarm can be reset by means of the reset h ... END
button in the alarm surveillance.

A50016-D3104-M470-3-7620 149
MMN:SSNC Maintenance
SE04 Signaling

8 Nonstandard maintenance
The fault cannot be cleared using the standard fault clearance procedures. h ...NM:SSNC

END

150 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SNC02

2.45 Simple AMXE Fault Clearance

SNC02

For additional information concerning e.g. commands/tasks, modules and replace/re-

i exchange of modules etc. see 2.1 Comments and Hints.

1 Preparation the fault clearance on-site

Provide the modules/units that are reported in the error message and are given
in the fault clearance procedure.
Start the fault clearance on-site. h ... 2
2 Decision block
Which module has to be replaced?
– ACCG h ... 3
– AMXE h ... 10
3 Deactivate ACCG
b CONF AMX:ACCG=..,SideAdmin. state=..,=Locked,Hazard check=Yes; h ... 4
4 ACCG power fault
Is any LED lit (see ACCG module face)? Y h ... 7
N h ... 5

5 ACCG power fault

If the power was disconnected by the over voltage protection, the only way to re-
activate the fuse/module is to pull and reinsert the module.

Check the fuse and activate if necessary. ☞ ......Construction

Rack SSNC

Pull ACCG module and reinsert (only necessary if no fuse fault).

Is a LED lit (see module face) after the module has been reinserted? Y h ... 6
N h ... 7

6 Diagnose ACCG
b DIAG AMX:ACCG=..,Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 9
N h ... 7

A50016-D3104-M470-3-7620 151
MMN:SSNC Maintenance
SNC02 Signaling

7 Replace module ACCG

Replace the module ACCG h ... 8
8 Diagnose ACCG
b DIAG AMX:ACCG=..,Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 9
N h ... 19

9 Activate ACCG
b CONF AMX:ACCG=..,Side=..,Admin. state=Unlocked; h ... 17
10 Deactivate AMXE
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Locked,Hazard check=Yes; h ... 11
11 AMXE power fault
Is any LED lit (see AMXE module face)? Y h ... 13
N h ... 12

12 AMXE power fault

If the power was disconnected by the over voltage protection, the only way to re-
activate the fuse/module is to pull and reinsert the module.

Check the fuse and activate if necessary. ☞ ......Construction

Rack SSNC

Pull AMXE module and reinsert (only necessary if no fuse fault).

Is a LED lit (see module face) after the module has been reinserted? Y h ... 13
N h ... 14

13 Diagnose AMXE
b DIAG AMX:ACCG=..,AMX=1,Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 16
N h ... 14

14 Replace module AMXE

Replace affected module h ... 15
15 Diagnose AMXE
b DIAG AMX:ACCG=..,AMX=1,Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 16
N h ... 19

152 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SNC02

16 Activate the AMXE

b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Unlocked; h ... 17
17 Decision block
b STAT AMX;
These actions have cleared the fault if,
– the alarm is canceled
(alarm status=cleared, availability status=no entry) and
– the green LED on the front panel of the replacement modules is lit and
– the alarm has been cancelled in the alarm protocol (alarm state=Cleared).
Could the fault be cleared? Y h ... END
N h ... 18

18 Decision block

For hints on inconsistency, see ☞ ......CH:SSNC

Are the alarm and availability states inconsistent? Y h ...NM:SSNC
ALARM:ASN
N h ... 20

19 Reinsert original module

It was not possible to reactivate the ACCG/AMXE. The replaced original module
is therefore not the cause of the fault and can be reinserted.

Remove the replacement module and reinsert the original module. h ... 20
20 Nonstandard maintenance
The fault cannot be cleared using the standard fault clearance procedures. h ...NM:SSNC

END

A50016-D3104-M470-3-7620 153
MMN:SSNC Maintenance
SNC03 Signaling

2.46 Simple MPU Fault Clearance

SNC03

General notes
If a number of MPUs have the error status failed or degraded, the MPU with the load
type SA (MPU of MP=1) must be cleared first, then the MPU with the load type SM or
SM/SLT (MPU of MP=2), followed by the MPU with the load type SLT (MPU of MP=>3).
For further information on the replacement of interchange units, see also
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Decision block

Has the MPU already been replaced during last 24 hours? Y h ... 2
N h ... 3

2 Decision block
After the activation of this module, is a failure reported again? Y h ...NM:SSNC
CH-MPU
N h ... 3

3 Decision block
Has the Under repair bit already been set for this fault clearance? Y h ... 5
N h ... 4

4 Set the Under repair bit

b CONF MP:MP=..,Side=..,Admin. state=Under repair;
Was the command executed? Y h ... 5
N h ... 16

5 Preparation the fault clearance on-site

Provide the modules/units that are reported in the error message and are given
in the fault clearance procedure.
Start the fault clearance on-site. h ... 6

154 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SNC03

6 Decision block
Which LED is lit (see module faceplate)?
– green only h ... 8
– green and red h ...PROC: SNC13
– red only h ... 9
– none h ... 7
7 Power faults
Check the fuse and replace if necessary. ☞ ......Construction
Rack SSNC

If the power was disconnected by the over voltage protection, the only way to re-
activate the fuse/module is to pull and reinsert the module.

Pull module and reinsert

Was the module reactivated after its self-test (only green LED lit)? Y h ... 12
N h ... 9

8 Display status of MP
b STAT MP:MP=..;
Is the affected MPU active? Y h ... 12
N h ... 9

9 Replace module M:MPU

Replace the reported M:MPU module.
Wait for it to be reactivated. h ... 10
10 Decision block
Did the unit become active again (only green LED is lit)? Y h ... 12
N h ... 11

11 Reinsert original affected module M:MPU

It was not possible to reactivate the MPU. The replaced original module is there-
fore not the cause of the fault and can be reinserted.

Remove the replacement module and reinsert the original MP module.

Wait for it to be reactivated. h ... 15

A50016-D3104-M470-3-7620 155
MMN:SSNC Maintenance
SNC03 Signaling

12 Decision block
b STAT MP:MP=..;
These actions have cleared the fault if
– the alarm is canceled
(alarm status=cleared, availability status=no entry) and
– the green LED on the front panel of the replacement modules is lit and
– the alarm has been canceled in the alarm protocol (alarm state=Cleared).
Could the fault be cleared? Y h ... 13
N h ... 14

13 Decision block
Was the module MPU(SA) replaced in the basic frame? Y h ...DATA:MPU
N h ... END

14 Decision block

For hints on inconsistency, see ☞ ......CH:SSNC

Are the alarm and availability states inconsistent? Y h ... NM:SSNC
ALARM:MPU
N h ... 15

15 Nonstandard maintenance
The fault cannot be cleared using the standard fault clearance procedures. h ...NM:SSNC
16 Decision block

For hints on inconsistency, see ☞ ......CH:SSNC

b STAT MP;
Determine all MPUs with inconsistent alarm and availability state.
Existing inconsistent states? Y h ... NM:SSNC
ALARM:MPU
N h ... 17

17 Fault clearance has already been started

Fault clearance has already been started. Continue with the actions. h ... END

END

156 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SNC04

2.47 Simple LIC Fault Clearance

SNC04

For additional information concerning e.g. commands/tasks, modules and replace/re-

i exchange of modules etc. see 2.1 Comments and Hints.

1 Decision block (Under repair bit)

Has the Under repair bit already been set for this fault clearance? Y h ... 3
N h ... 2

2 Set the Under repair bit

b CONF LIC:LIC=..,Admin. state=Under repair;
Was the command executed? Y h ... 3
N h ... 11

3 Preparation the fault clearance on-site

Provide the modules/units that are reported in the error message and are given
in the fault clearance procedure.
Start the fault clearance on-site. h ... 4
4 Decision block
Which LED is lit (see module faceplate)?
– green only h ... 6
– green and red h ...PROC: SNC14
– red only h ... 7
– none h ... 5
5 Power faults
Check the fuse and replace if necessary. ☞ ......Construction
Rack SSNC

If the power was disconnected by the over voltage protection, the only way to re-
activate the fuse/module is to pull and reinsert the module.

Pull module and reinsert.

Was the module reactivated after its self-test (only green LED is on)? Y h ... 9
N h ... 7

A50016-D3104-M470-3-7620 157
MMN:SSNC Maintenance
SNC04 Signaling

6 Display status of LIC

b STAT LIC:LIC=..;
Is the reported LIC active? Y h ... 9
N h ... 7

7 Replace module M:LIC

Replace the reported M:LIC module.
Wait for it to be reactivated.
Did the unit become active again? Y h ... 9
N h ... 8

8 Reinsert original module M:LIC

It was not possible to reactivate the LIC. The replaced original module is there-
fore not the cause of the fault and can be reinserted.

Remove the replacement module and reinsert the original M:LIC module. h ... 10
9 Decision block

If these actions have cleared the fault, the green LED on the front panel of the
replacement modules is lit, but the red LED is off. Another way to check whether
fault clearance has been successful is to see whether the alarm has been can-
celled in the alarm protocol (alarm state=Cleared).

Could the fault be cleared? Y h ... END

N h ... 10

10 Nonstandard maintenance
It is not possible to clear the fault by the standard fault clearance procedures. h ...NM:SSNC
11 Fault clearance has already been started
Fault clearance has already been started. Continue with the actions. h ... END

END

158 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SNC06

2.48 Simple ASN Fault Clearance

SNC06

For additional information concerning e.g. commands/tasks, modules and replace/re-

i exchange of modules etc. see 2.1 Comments and Hints.

1 Preparation for fault clearance on site

Provide the modules/units that are reported in the error message and are given
in the fault clearance procedure.
Start fault clearance on site. h ... 2
2 Decision block
Which module has to be replaced?
– ACCG (ASN) h ... 3
– GMX/GMXE h ... 7
– PSA or ASMG h ... 11
3 Deactivate the ACCG
b CONF ASN:ACCG=...,Side=..,Admin. state=Locked,Hazard check=Yes; h ... 4
4 Replace the suspect module
Replace the affected module. h ... 5
5 Diagnose M:ACCG
b DIAG ASN:ACCG=...,Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 6
N h ... 20

6 Activate the ACCG

b CONF ASN:ACCG=...,Side=..,Admin. state=Unlocked; h ... 18
7 Deactivate the GMX
b CONF ASN:ACCG=2,Side=..,ASN=..,Admin. state=Locked,Hazard check=Yes; h ... 8
8 Replace the suspect module
Replace the affected module. h ... 9

A50016-D3104-M470-3-7620 159
MMN:SSNC Maintenance
SNC06 Signaling

9 Diagnose M:GMX
b DIAG ASN:ACCG=2,ASN=..,Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 10
N h ... 20

10 Activate the GMX

b CONF ASN:ACCG=2,Side=..,ASN=..,Admin. state=Unlocked; h ... 18
11 Deactivate the ASMG/PSA
b CONF ASN:ACCG=2,Side=..,ASN=1,Admin. state=Locked,Hazard check=Yes; h ... 12
12 Power faults
Is any LED lit on the module faceplates for ASMG/PSA? Y h ... 15
N h ... 13

13 Power faults (over voltage)

If the power was disconnected by the over voltage protection, the only way to re-
activate the fuse/module is to remove and reinsert the module.

Check the fuse and if necessary switch the fuse on, and/or switch the power ☞ ......Construction,
Rack SSNC
supply module off and on.

Is an LED lit after the fuse or the power supply module has been switched on? Y h ... 14
N h ...HW20

14 Diagnose ASMG/PSA
b DIAG ASN:ACCG=2,ASN=1,Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 17
N h ... 15

15 Replace suspect module

Replace the affected module. h ... 16
16 Diagnose ASMG/PSA
b DIAG ASN:ACCG=...,ASN=1,Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 17
N h ... 20

17 Activate ASMG/ASMX/PSA
b CONF ASN:ACCG=...,ASN=1,Side=..,Admin. state=Unlocked; h ... 18

160 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SNC06

18 Decision block
b STAT ASN;
These actions have cleared the fault if,
– the alarm is canceled
(alarm status=cleared, availability status=no entry) and
– the green LED on the front panel of the replacement modules is lit and
– the alarm has been cancelled in the alarm protocol (alarm state=Cleared).
Could the fault be cleared? Y h ... END
N h ... 19

19 Decision block

For hints on inconsistency, see ☞ ......CH:SSNC

Are the alarm and availability states inconsistent? Y h ... NM:SSNC
ALARM:MPU
N h ... 21

20 Reinsert original module

It was not possible to reactivate the ASN. The replaced original module is there-
fore not the cause of the fault and can be reinserted.

Remove the replacement module and reinsert the original module. h ... 21
21 Nonstandard maintenance
The fault cannot be cleared using the standard fault clearance procedures. h ...NM:SSNC

END

A50016-D3104-M470-3-7620 161
MMN:SSNC Maintenance
SNC07 Signaling

2.49 ALI Fault

SNC07

General notes and fault description

Caution: The ETHERNET interface in F:SCB(B) / SXCB(B) (HUB over AUI) is depen-
dent on the power supply to the ALI module, in other words: if the HUB is used in the
ETHERNET interface, there is no connection to the Switch commander after the ALI
module has been removed (only MPU(SA) in F:SCB(B) / SXCB(B).
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Decision block

Has the ’locked’ state already been set for this fault clearance? Y h ... 3
N h ... 2

2 Configuration ALI
b CONF ALI:Admin. state=Locked h ... 3
3 Preparation for fault clearance on site
Provide the modules / units that are reported in the error message and are given
in the fault clearance procedure.
Start fault clearance on site. h ... 4
4 Decision block
Which LED is lit (see module faceplate)?
– red only (ERROR) h ... 7
– none h ... 5
5 Power faults
Check the fuse and activate if necessary. ☞ ......Construction,
Rack SSNC

If the power was disconnected by the overvoltage protection, the only way to re-
activate the fuse / module is to remove and reinsert the module.

Remove module and reinsert.

Is any LED lit (see ALI module face) Y h ... 6
N h ... 7

162 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SNC07

6 Diagnose ALI
b DIAG ALI:Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 8
N h ... 7

7 Replace module ALI

Replace the reported module ALI. h ... 8
8 Activating module ALI
b CONF ALI:Admin. state=Unlocked
Wait for it to be reactivated.
Has the unit been reactivated (only green LED is on)? Y h ... 10
N h ... 9

9 Reinsert original module ALI

It was not possible to reactivate the ALI. The replaced original module is there-
fore not the cause of the fault and can be reinserted.

b CONF ALI:Admin. state=Locked

Remove the replacement module and reinsert the original ALI module. h ... 11
10 Decision block

If these actions have cleared the fault, the green LED on the front panel of the
replacement modules is lit, but the red LED is off. Another way to check whether
fault clearance has been successful is to see whether the alarm has been can-
celled in the alarm protocol (alarm state=Cleared).

Could the fault be cleared? Y h ... END

N h ... 11

11 Nonstandard maintenance
The fault cannot be cleared using the standard fault clearance procedures. h ...NM:SSNC

END

A50016-D3104-M470-3-7620 163
MMN:SSNC Maintenance
SNC12 Signaling

2.50 Extended AMXE Fault Clearance

SNC12

For additional information concerning e.g. commands/tasks, modules and replace/re-

i exchange of modules etc. see 2.1 Comments and Hints.

1 Preparation the fault clearance on-site

Provide the modules/units that are reported in the error message and are given
in the fault clearance procedure.
Start the fault clearance on-site. h ... 2
2 Decision block for module replacement

The order in which the units are to be replaced has been defined by the system
and is indicated in the fault report.

Which unit has to be replaced first (next)?

– All suspect units have been checked or replaced. h ... 34
– AMX (M:AMXE/M:ASMX) ’reported module’ h ... 4
– AMX (M:AMXE/M:ASMX) ’connected to the reported module‘ h ... 6
– M:MPU* h ... 9
– M:LIC h ... 16
– AMX (M:ACCG) ’reported module’ h ... 19
– AMX (M:ACCG) ’connected to the reported module’ h ... 21
– ASN (M:GMX) h ... 23
– Cable h ... 26
After successful replacement of the module in MMN:CP/MMN:MBD h ... 3

3 Test the interface by configuration of the ’reported module’ AMXE/ASMX

b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Locked,Hazard check=Yes
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Unlocked;
Was diagnosis completed without any faults being found? Y h ... 29
N h ... 4

164 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SNC12

4 Replace the ’reported module’ AMXE/ASMX

b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Locked,Hazard check=Yes
Replace the ’reported module’ M:AMXE.
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Unlocked;
Wait for reactivation? Did the unit become active again? Y h ... 29
N h ... 5

5 Reinsert the original module

The AMXE/ASMX could not be reactivated. The replaced module is therefore

not the cause of the fault and can be reinserted.

b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Locked,Hazard check=Yes

einsert the originally replaced module.
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Unlocked; h ... 2
6 ’Replace the ’connected to the reported module’ AMXE

Before fault clearance of the ’connected to the reported module’ AMX/ASMX, it

must be ensured that the ’reported module’ AMX/ASMX is not in ’locked’ or
’failed’ or in any other state where it is not available.

b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Locked,Hazard check=Yes

Replace the ’connected to the reported module’ M:AMXE.
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Unlocked;
Was diagnosis completed without any faults being found? Y h ... 7
N h ... 34

7 Test the interface by configuration of the ’reported module’ AMXE

b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Locked,Hazard check=Yes;
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Unlocked;
Did the unit become active again (only green LED lights up? Y h ... 7
N h ... 8

8 ’Reinsert the ’connected to the reported module’ AMXE

The AMXE could not be reactivated. The replaced module is therefore not the
cause of the fault and can be reinserted.

b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Locked,Hazard check=Yes;

Reinsert the originally replaced module.
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Unlocked; h ... 2

A50016-D3104-M470-3-7620 165
MMN:SSNC Maintenance
SNC12 Signaling

9 Decision block (MPU*)

Is a MPU(SA) be replaced? Y h ... 10
N h ... 11

10 Deactivate MDD and MOD

Before a MPU(SA) is deactivated, the following MDD/MOD units must be deacti-

vated.

b CONF MDDMP:Side=..,Administrative State=locked;

If a MOD is installed and created, then also

b CONF MODMP:Side=..,Administrative State=locked; h ... 11

11 Replaced ’connected to the reported module’ MPU*
b CONF MP:MP=..,Side=..,Admin. state=Locked,Hazard check=Yes;
Replace suspect module MPU*
b CONF MP:MP=..,Side=..,Admin. state=Unlocked;
Wait for reactivation h ... 12
12 Test the interface by configuration of the ’reported module’ AMXE
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Locked,Hazard check=Yes
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Unlocked;
Wait for reactivation Y h ... 29
N h ... 13

13 ’Reinsert the MPU* module

The AMXE could not be reactivated. The replaced module is therefore not the
cause of the fault and can be reinserted.

b CONF MP:MP=..,Side=..,Admin. state=Locked,Hazard check=Yes;

Reinsert the originally replaced module.
b CONF MP:MP=..,Side=..,Admin. state=Unlocked;
Wait for reactivation h ... 14
14 Decision block (SA/D)
Was a MDD/MOD deactivated? Y h ... 15
N h ... 2

166 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SNC12

15 Activate MDD and MOD

b CONF MDDMP:Side=..,Administrative State=unlocked,Label=Yes;

Was an MOD deactivated, then also

b CONF MODMP:Side=..,Administrative State=unlocked,Label=No; h ... 2

16 Replace affected module M:LIC
b CONF LIC:LIC=..,Admin. state=Locked;
Replace the affected M:LIC module.
b CONF LIC:LIC=..,Admin. state=Unlocked; h ... 17
17 Test the interface by configuring the reported AMXE
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Locked,Hazard check=Yes
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Unlocked;
Was diagnosis completed without any faults being found? Y h ... 29
N h ... 18

18 Reinsert original affected LIC module

It was not possible to reactivate the AMXE. The replaced original module is
therefore not the cause of the fault and can be reinserted.

b CONF LIC:LIC=..,Admin. state=Locked;

Remove the replacement module and reinsert the original M:LIC module.
b CONF LIC:LIC=..,Admin. state=Unlocked; h ... 2
19 Replace ’reported module’ ACCG
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Locked,Hazard check=Yes;
b CONF AMX:ACCG=..,Side=..,Admin. state=Locked,Hazard check=Yes;
Replace the affected ACCG module.
b CONF AMX:ACCG=..,Side=..,Admin. state=Unlocked;
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Unlocked;
Did the unit become active again (only the green LED is on)? Y h ... 29
N h ... 20

A50016-D3104-M470-3-7620 167
MMN:SSNC Maintenance
SNC12 Signaling

20 Reinsert original ACCG module

It was not possible to reactivate the AMXE. The replaced original module is
therefore not the cause of the fault and can be reinserted.

b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Locked,Hazard check=Yes;

b CONF AMX:ACCG=..,Side=..,Admin. state=Locked,Hazard check=Yes;
Replace the original ACCG module.
b CONF AMX:ACCG=..,Side=..,Admin. state=Unlocked;
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Unlocked; h ... 2
21 ’Replace the ’connected to the reported module’ ACCG

Before fault clearance of the ’connected to the reported module’ AMX, it must be
ensured that the ’reported module’ AMX is not in ’locked’ or ’failed’ or in any oth-
er state where it is not available.

b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Locked,Hazard check=Yes;

b CONF AMX:ACCG=..,Side=..,Admin. state=Locked,Hazard check=Yes;
Replace the ’connected to the reported module’ ACCG.
b CONF AMX:ACCG=..,Side=..,Admin. state=Unlocked;
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Unlocked;
e unit become active again (only the green LED is on)? Y h ... 29
N h ... 22

22 Reinsert the original module (ACCG)

The ACCG could not be reactivated. The replaced module is therefore not the
cause of the fault and can be reinserted.

b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Locked,Hazard check=Yes;

b CONF AMX:ACCG=..,Side=..,Admin. state=Locked,Hazard check=Yes;
Replace the ’connected to the reported module’ ACCG.
b CONF AMX:ACCG=..,Side=..,Admin. state=Unlocked;
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Unlocked; h ... 2
23 Replace affected GMX /ASMG module
b CONF ASN:ACCG=...,ASN=..,Side=..,Admin. state=Locked,Hazard check=Yes;
Replace the affected GMX module.
b CONF ASN:ACCG=...,ASN=..,Side=..,Admin. state=Unlocked; h ... 24

168 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SNC12

24 Test the interface by configuring the ’reported module’ AMXE

b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Locked,Hazard check=Yes
b CONF AMX:ACCG=..,Side=..,Admin. state=Unlocked;
Did the unit become active again (only the green LED is on)? Y h ... 29
N h ... 25

25 Reinsert original module M:GMX

It was not possible to reactivate the AMXE. The replaced original module is
therefore not the cause of the fault and can be reinserted.

b CONF ASN:ACCG=...,ASN=..,Side=..,Admin. state=Locked,Hazard check=Yes;

Remove the replaced module and reinsert the original GMX module.
b CONF ASN:ACCG=...,ASN=..,Side=..,Admin. state=Unlocked; h ... 2
26 Check the cable
Perform a visual inspection of the cable connection.
Was any fault found? Y h ... 27
N h ... 2

27 Decision block (cable)

Could the fault be cleared? Y h ... 28
N h ... 34

28 Test the interface by configuring the reported AMXE

b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Locked,Hazard check=Yes
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Unlocked;
Did the unit become active again (only the green LED is on)? Y h ... 29
N h ... 2

29 Decision block (MDD/MOD)

Was a MDD/MOD deactivated? Y h ... 30
N h ... 31

30 Activate MDD/MOD
b CONF MDDMP:Side=..,Administrative State=unlocked, Label=Yes;

Was an MOD deactivated, then also

b CONF MODMP:Side=..,Administrative State=unlocked, Label=No; h ... 31

A50016-D3104-M470-3-7620 169
MMN:SSNC Maintenance
SNC12 Signaling

31 Decision block
b STAT AMX;
These actions have cleared the fault if,
– the alarm is canceled
(alarm status=cleared, availability status=no entry) and
– the green LED on the front panel of the replacement modules is lit and
– the alarm has been cancelled in the alarm protocol (alarm state=Cleared).
Could the fault be cleared? Y h ... 32
N h ... 33

32 Decision block
Was the module MPU(SA) replaced in the basic frame? Y h ...DATA:MPU
N h ... END

33 Decision block

For hints on inconsistency, see ☞ ......CH:SSNC

Are the alarm and availability states inconsistent? Y h ...NM:SSNC
ALARM:ASN
N h ... 34

34 Nonstandard maintenance
The fault cannot be cleared using the standard fault clearance procedures. h ...NM:SSNC

END

170 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SNC13

2.51 Extended MPU Fault Clearance

SNC13

For additional information concerning e.g. commands/tasks, modules and replace/re-

i exchange of modules etc. see 2.1 Comments and Hints.

1 General notes

If a number of MPUs have the error status failed or degraded, the MPU with the h ... 2
load type SA (MPU of MP=1) must be cleared first, then the MPU with the load
type SM or SM/SLT (MPU of MP=2), followed by the MPUs with the other load
types, (MPU of MP=>3).

2 Decision block
Has the MPU already been replaced during last 24 hours? Y h ... 3
N h ... 4

3 Decision block
After the activation of this module, is a failure reported again? Y h ...NM:SSNC
CH-MPU
N h ... 4

4 Decision block (Under repair bit)

Has the Under repair bit already been set for this fault clearance or is the MPU
already in status locked? Y h ... 6
N h ... 5

5 Set the Under repair bit

b CONF MP:MP=..,Side=..,Admin. state=Under repair;
Was the command executed? Y h ... 6
N h ... 35

6 Preparation for fault clearance on site

Provide the module(s)/unit(s) that are reported in the error message and are
given in the fault clearance procedure.
An MPU* (D)/MPU* (SA) must also be provided
Start fault clearance on site. h ... 7

A50016-D3104-M470-3-7620 171
MMN:SSNC Maintenance
SNC13 Signaling

7 Decision block
Which LED is lit on the module faceplate?
– green only h ... 8
– green and red h ... 9
– red only h ... 9
8 Display status of MPU
b STAT MP:MP=..;
Is the affected MPU active? Y h ... 31
N h ... 9

9 Decision block (SA/D)

Is an MP(SA) faulty? Y h ... 10
N h ... 12

10 Decision block
Are MDD and MOD that are connected to this MPU already deactivated? Y h ... 12
N h ... 11

11 Deactivate MDD/MOD

Before an MPU(SA) is deactivated, the following MDD/MOD units must be deac-

tivated.

b CONF MDDMP:Side=..,Administrative State=locked;

If an MOD is installed and activated, then also

b CONF MODMP:Side=..,Administrative State=locked; h ... 12

12 Decision block for module replacement

The order in which the units are to be replaced has been defined by the system
and is indicated in the fault report.

Which unit has to be replaced first (next)?

– No module is reported (Change order is MPU* ’reported module’) h ... 14
– M:MPU* ’connected to the reported module’ h ... 13
– M:MPU* ’reported module’ h ... 14
– AMXE/ASMX h ... 17
– Cable h ... 23
– All the suspect units were checked or replaced h ... 34

172 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SNC13

13 Replace ’connected to the reported module’ MPU*

If the ’reported module’ MPU is not active and the ’connected to the reported
module’ MPU has to be replaced, then the MP is completely out of service. For
this reason, fault clearance should be performed during a period of low traffic
volume. Replacing both MPUs of an MP is a nonstandard maintenance proce-
dure.

Must a connected to the reported module M:MPU* be replaced? Y h ... 34

N h ... 14

14 Replace module M:MPU*

Replace module M:MPU*.
Wait for it to be reactivated. h ... 15
15 Decision block
Was it possible to activate the MP without any errors occurring? Y h ... 29
N h ... 16

16 Reinsert original module M:MPU*

It was not possible to reactivate the MPU. The replaced original module is there-
fore not the cause of the fault and can be reinserted.

Remove the replacement module and reinsert the original MP module. h ... 12
17 Replace module M:AMXE/M:ASMX
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Locked,Hazard check=Yes
Replace the affected M:AMXE module.
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Unlocked; h ... 18
18 Decision block
Is the MPU already in locked? Y h ... 19
N h ... 20

19 Diagnose MPU
b DIAG MP:MP=..,Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 21
N h ... 22

20 Deactivate MPU (interface test)

b CONF MP:MP=..,Side=..,Admin. state=Locked,Hazard check=Yes; h ... 21

A50016-D3104-M470-3-7620 173
MMN:SSNC Maintenance
SNC13 Signaling

21 Activate MPU (interface test)

b CONF MP:MP=..,Side=..,Admin. state=Unlocked;
Did the unit become active again (only the green LED is on)? Y h ... 29
N h ... 22

22 Replace module M:AMXE/M:ASMX

It was not possible to reactivate the AMXE. The replaced original module is
therefore not the cause of the fault and can be reinserted.

b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Locked,Hazard check=Yes

Replace the affected M:AMXE module.
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Unlocked; h ... 12
23 Check the cable
Perform a visual inspection of the cable connection.
Was any fault found and was it possible to clear it? Y h ... 24
N h ... 12

24 Check the cable

Could the fault be cleared? Y h ... 25
N h ... 34

25 Decision block
Is the MPU already in locked? Y h ... 26
N h ... 27

26 Diagnose MPU
b DIAG MP:MP=..,Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 28
N h ... 34

27 Deactivate MPU (interface test)

b CONF MP:MP=..,Side=..,Admin. state=Locked,Hazard check=Yes; h ... 28
28 Activate MPU (interface test)
b CONF MP:MP=..,Side=..,Admin. state=Unlocked;
Did the unit become active again (only the green LED is on)? Y h ... 29
N h ... 12

174 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SNC13

29 Decision block (SA/D)

Was an MDD/MOD deactivated? Y h ... 30
N h ... 31

30 MDD/MOD activated
b CONF MDDMP:Side=..,Administrative State=unlocked,Label=;Yes;

Was an MOD deactivated, then also

b CONF MODMP:Side=..,Administrative State=unlocked,Label=No; h ... 31

31 Decision block
b STAT MP:MP=..;
These actions have cleared the fault if
– the alarm is canceled
(alarm status=cleared, availability status=no entry) and
– the green LED on the front panel of the replacement modules is lit and
– the alarm has been canceled in the alarm protocol (alarm state=Cleared)
Could the fault be cleared? Y h ... 32
N h ... 33

32 Decision block
Was the module MPU(SA) replaced in the basic frame? Y h ...DATA:MPU
N h ... END

33 Decision block

For hints regarding inconsistency, see ☞ ......CH:SSNC

Are the alarm and availability states inconsistent? Y h ... NM:SSNC
ALARM:MPU
N h ... 34

34 Nonstandard maintenance
The fault cannot be cleared using the standard fault clearance procedures. h ...NM:SSNC

A50016-D3104-M470-3-7620 175
MMN:SSNC Maintenance
SNC13 Signaling

35 Decision block

For hints regarding inconsistency, see ☞ ......CH:SSNC

b STAT MP:MP
Determine all MPUs with inconsistent alarm and availability states.
Existing inconsistent states? Y h ... NM:SSNC
ALARM:MPU
N h ... 36

36 Fault clearance has already been started

Fault clearance has already been started. Continue with the actions. h ... END

END

176 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SNC14

2.52 Extended LIC Fault Clearance

SNC14

For additional information concerning e.g. commands/tasks, modules and replace/re-

i exchange of modules etc. see 2.1 Comments and Hints.

1 Decision block (Under repair bit)

Has the Under repair bit already been set for this fault clearance? Y h ... 3
N h ... 2

2 Set the Under repair bit

b CONF LIC:LIC=..,Admin. state=Under repair;
Was the command executed? Y h ... 3
N h ... 18

3 Preparation the fault clearance on-site

Provide the modules/units that are reported in the error message and are given
in the fault clearance procedure.
Start the fault clearance on-site. h ... 4
4 Decision block
Which LED is lit on the module faceplate?
– green only h ... 5
– green and red h ... 6
– red only h ... 6
5 Display status of LIC
b STAT LIC:LIC=..;
Is the reported LIC active? Y h ... 16
N h ... 6

A50016-D3104-M470-3-7620 177
MMN:SSNC Maintenance
SNC14 Signaling

6 Decision block for module replacement

The order in which the units are to be replaced has been defined by the system
and is indicated in the fault report.

Which unit has to be replaced first (next)?

– M:LIC h ... 7
– AMXE/ASMX h ... 10
– Cable h ... 13
– All the suspect units were checked or replaced h ... 17
7 Replace module M:LIC
Replace module M:LIC
Wait for it to be reactivated. h ... 8
8 Decision block
Was it possible to activate the LIC without any errors occurring? Y h ... 16
N h ... 9

9 Reinsert original module M:LIC

It was not possible to reactivate the LIC. The replaced original module is there-
fore not the cause of the fault and can be reinserted.

Remove the replacement module and reinsert the original LIC module.
Wait for it to be reactivated. h ... 6
10 Replace module AMXE/ASMX
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Locked,Hazard check=Yes
Replace module AMXE.
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Unlocked; h ... 11
11 Test the interface and reset the Under repair bit
by configuring the reported LIC
b CONF LIC:LIC=..,Admin. state=Locked;
b CONF LIC:LIC=..,Admin. state=Unlocked;
Did the unit become active again (only the green LED is on)? Y h ... 16
N h ... 12

178 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SNC14

12 Reinsert original module M:AMXE/M:ASMX

It was not possible to reactivate the AMXE. The replaced original module is
therefore not the cause of the fault and can be reinserted.

b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Locked,Hazard check=Yes

Remove the replacement module and reinsert the original M:AMXE module.
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Unlocked; h ... 6
13 Check the cable
Perform a visual inspection of the cable connection.
Was any fault found and was it possible to clear it? Y h ... 14
N h ... 6

14 Check the cable

Could the fault be cleared? Y h ... 15
N h ... 17

15 Test the interface and reset the Under repair bit)

Test the interface and reset the Under repair bit by configuring the reported LIC

b CONF LIC:LIC=..,Admin. state=Locked;

b CONF LIC:LIC=..,Admin. state=Unlocked;
Did the unit become active again (only the green LED is on)? Y h ... 16
N h ... 6

16 Decision block

If these actions have cleared the fault, the green LED on the front panel of the
replacement modules is lit, but the red LED is off. Another way to check whether
fault clearance has been successful is to see whether the alarm has been can-
celled in the alarm protocol.

Could the fault be cleared? Y h ... END

N h ... 17

17 Nonstandard maintenance
The fault cannot be cleared using the standard fault clearance procedures. h ...NM:SSNC
18 Fault clearance has already been started
Fault clearance has already been started. Continue with the actions. h ... END

END

A50016-D3104-M470-3-7620 179
MMN:SSNC Maintenance
SNC16 Signaling

2.53 Extended ASN Fault Clearance

SNC16

For additional information concerning e.g. commands/tasks, modules and replace/re-

i exchange of modules etc. see 2.1 Comments and Hints.

1 Preparation for fault clearance on site

Provide the modules/units that are reported in the error message and are given
in the fault clearance procedure.
Start fault clearance on site. h ... 2
2 Decision block

The order in which the units are to be replaced has been defined by the system
and is indicated in the fault report.

Which unit has to be replaced first (next)?

– All suspect units have been checked or replaced. h ... 20
– ASN (ACCG) h ... 3
– ASN (ASMG16/16) h ... 6
– ASN (GMX) h ... 9
– AMX (AMXE/ASMX) h ... 12
3 Replace the module (ACCG)

Only ASN20/40, configure all GMX modules on defected system site to ’Locked’

b CONF ASN:ACCG=2,Side=..,ASN=..,Admin. state=Locked,Hazard check=Yes;

Configure ASMG / ASMX module on defected system site to ’Locked’

b CONF ASN:ACCG=...,Side=..,ASN=1,Admin. state=Locked,Hazard check=Yes;

Configure ACCG module on defected system site to ’Locked’

b CONF ASN:ACCG=...,Side=..,Admin. state=Locked,Hazard check=Yes;

Replace the first/next module
b DIAG ASN:ACCG=...,Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 4
N h ... 15

180 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SNC16

4 Activate the module ACCG

b CONF ASN:ACCG=...,Side=..,Admin. state=Unlocked;

Configure ASMG / ASMX module to ’Unlocked’

b CONF ASN:ACCG=...,Side=..,ASN=1,Admin. state=Unlocked;

Only ASN20/40, configure all GMX modules to ’Unlocked’

b CONF ASN:ACCG=2,Side=..,ASN=..,Admin. state=Unlocked;

Did the unit become active again (only the green LED is on)? Y h ... 16
N h ... 5

5 Reinsert original module ACCG

Only ASN20/40, configure all GMX modules on defected system site to ’Locked’

b CONF ASN:ACCG=2,Side=..,ASN=...,Admin. state=Locked,Hazard check=Yes;

Configure ASMG / ASMX module on defected system site to ’Locked’

b CONF ASN:ACCG=...,Side=..,ASN=1,Admin. state=Locked,Hazard check=Yes;

Configure ACCG module on defected system site to ’Locked’

b CONF ASN:ACCG=...,Side=..,Admin. state=Locked,Hazard check=Yes;

Remove the replacement module and reinsert the original module.
b CONF ASN:ACCG=...,Side=..,Admin. state=Unlocked;

Configure ASMG / ASMX module to ’Unlocked’

b CONF ASN:ACCG=..,Side=..,ASN=1,Admin. state=Unlocked;

Only ASN20/40, configure all GMX modules to ’Unlocked’

b CONF ASN:ACCG=2,Side=..,ASN=...,Admin. state=Unlocked; h ... 2

6 Replace the module (M:ASMG)
b CONF ASN:ACCG=...,ASN=1,Side=..,Admin. state=Locked,Hazard check=Yes;
Replace the module
b DIAG ASN:ACCG=...,ASN=1,Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 7
N h ... 15

A50016-D3104-M470-3-7620 181
MMN:SSNC Maintenance
SNC16 Signaling

7 Activate the module ASMG

b CONF ASN:ACCG=...,ASN=1,Side=..,Admin. state=Unlocked;
Did the unit become active again (only the green LED is on)? Y h ... 16
N h ... 8

8 Reinsert original module ASMG

b CONF ASN:ACCG=...,ASN=1,Side=..,Admin. state=Locked,Hazard check=Yes;
Remove the replacement module and reinsert the original module. h ... 2
9 Replace the module (M:GMX)
b CONF ASN:ACCG=2,ASN=..,Side=..,Admin. state=Locked,Hazard check=Yes;
Replace the module
b DIAG ASN:ACCG=2,ASN=..,Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 10
N h ... 15

10 Activate the module GMX

b CONF ASN:ACCG=2,ASN=..,Side=..,Admin. state=Unlocked;
Did the unit become active again (only the green LED is on)? Y h ... 16
N h ... 11

11 Reinsert original module GMX

b CONF ASN:ACCG=2,ASN=..,Side=..,Admin. state=Locked,Hazard check=Yes;
Remove the replacement module and reinsert the original module. h ... 2
12 Replace the module AMXE/ASMX
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Locked,Hazard check=Yes
Replace the module
b DIAG AMX:ACCG=..,AMX=1,Side=..,Kind of diagnosis=Complete diagnosis;
Was diagnosis completed without any faults being found? Y h ... 13
N h ... 15

13 Activate the AMXE/ASMX

b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Unlocked;
Did the unit become active again (only the green LED is on)? Y h ... 16
N h ... 14

14 Reinsert original module AMXE

b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Locked,Hazard check=Yes
Remove the replacement module and reinsert the original module. h ... 2

182 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SNC16

15 Reinsert original module

The diagnosis was not successful. The replaced original module is therefore not
the cause of the fault and can be reinserted.

Remove the replacement module and reinsert the original module. h ... 2
16 Decision block
Were any units deactivated during fault clearance which have not been reacti-
vated yet? Y h ... 17
N h ... 18

17 Follow-up treatment

Use one of the following commands to activate a unit that is not yet active:

b CONF ASN:ACCG=...,Side=..,Admin. state=Unlocked;

b CONF ASN:ACCG=...,ASN=..,Side=..,Admin. state=Unlocked;
b CONF AMX:ACCG=..,AMX=1,Side=..,Admin. state=Unlocked; h ... 18
18 Decision block
b STAT ASN;
These actions have cleared the fault if,
– the alarm is canceled
(alarm status=cleared, availability status=no entry) and
– the green LED on the front panel of the replacement modules is lit and
– the alarm has been cancelled in the alarm protocol (alarm state=Cleared).
Could the fault be cleared? Y h ... END
N h ... 19

19 Decision block

For hints on inconsistency, see ☞ ......CH:SSNC

Are the alarm and availability states inconsistent? Y h ...NM:SSNC
ALARM:ASN
N h ... 20

20 Nonstandard maintenance
The fault cannot be cleared using the standard fault clearance procedures. h ...NM:SSNC

END

A50016-D3104-M470-3-7620 183
MMN:SSNC Maintenance
SP01 Signaling

2.54 Isolation of the Signaling Point

SP01

General notes and fault description

The exchange has no more active signaling links. This situation may be caused by the
(rare) failure of the last active signaling link, or occur in combination with a hardware
fault that has made all MP(SA)s/MP(SM)s or MP(SLT)s inaccessible.
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Decision block (link in Locked)

b DISP SIGLINK:Admin. state=Locked;

Are there any signaling links in state Locked? Y h ... 2
N h ... 3

2 Fault clearance of link in Locked

First, all maintenance-blocked signaling links must be activated.

b MOD SIGLINK:Link set name=..,Link code=..,Admin. state=Unlocked;

Are there any more signaling links in operating state Unlocked? Y h ... 2
N h ... 3

3 Decision block (link in Disabled)

b DISP SIGLINK:Operational state=Disabled;
Are there any signaling links in operating state Disabled? Y h ... 4
N h ... 5

4 Fault clearance of link in Disabled

Fault clearance of signaling links that have failed due to a hardware fault

Signaling link fault clearance should be carried out in accordance with i....PROC: LI02
Are there any more signaling links in operating state Disabled? Y h ... 4
N h ... 5

184 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SP01

5 Decision block (MP in Failed or Dependency)

b STAT MP:MP=X;
Are both MPUs in MP(SA) or MP(SM) in operating state failed or is there no ac-
cessible MP(SA) or MP(SM) or MP(SLT) due to a combination of hardware fail-
ures? Y h ... 6
N h ... 8

6 Fault clearance of MP in Failed or Dependency

Carry out MP fault clearance as specified in the corresponding MP failure mes-

sage.

Carry out MP fault clearance using the MMN. h ...PROC: PRO-

CIN

7 Decision block
Could the fault be cleared, i.e. could signaling be restarted via at least one sig-
naling link? Y h ... END
N h ... 8

8 Nonstandard maintenance
It is not possible to clear the fault by the standard fault clearance procedures. h ...NM:SSNC

END

A50016-D3104-M470-3-7620 185
MMN:SSNC Maintenance
SW01 Signaling

2.55 Total CCS7 Outage

SW01

For additional information concerning e.g. commands/tasks, modules and replace/re-

i exchange of modules etc. see 2.1 Comments and Hints.

1 General notes and fault description

SpecificProblems=totalOutageCCS7
PerceivedSeverity=critical
The CCS7 signaling system has failed completely. Calls can no longer be
switched outside the home exchange. The fault is due to undershooting of the
threshold value (1) of active CCS7-related processors. (The configured thresh-
old value for all processors is 1.)

The following unit types are required for signaling:

– MP(SM)
– MP(SLT-GTT)
– MP(SLT-MTP)
– LIC
– ACCG / AMXE (Ultimate)
– ACCG / ASN
Determine the MP load types
b DISP MP; h ... 2
2 Analysis
What was the situation leading to the total CCS7 outage?
– during/after the upgrade h ... 3
– during/after the configuration h ... 4
– in connection with a HW fault h ... 5
– the system did not act unusually before the total outage h ... 5

186 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SW01

3 Total CCS7 outage during/after the upgrade

The upgrade could not be successfully completed. The threshold value (1) was
not reached for all system-relevant units. A manual fallback to the backup gener-
ation must be started.

The following TERMINATE command has the effect that the upgrade is termi-
nated in a controlled manner and that the system is restarted with a backup
generation.

The following command is only permitted with the approval of the relevant TAC
! personnel.

b TERMINATE;
Conduct postprocessing for
– UMTS network node h ...EMCYMN
EY190

4 Total CCS7 outage during/after the configuration

No system operation is possible after deactivation of both MPU(SA)s; a
! LOADREC3 is automatically started.

A system-relevant unit was configured to locked by a command with Hazard

check=no. Since there is deliberately no check for system outage-relevant units
in this case, it is to be assumed that the unit is to be deactivated.

Was the total outage deliberately initiated? Y h ... END

N h ... 5

5 Decision block

The following commands can be used to determine any missing operating

states.

b STAT MP;
b STAT LIC;
b STAT AMX;
b STAT ASN;
Is any system relevant unit to ’locked’ except definite faulty units? Y h ... 6
N h ... 8

6 Decision block
Does activation of the units resolve the total CCS7 outage? Y h ... 7
N h ... 8

A50016-D3104-M470-3-7620 187
MMN:SSNC Maintenance
SW01 Signaling

7 Activate the units set to ’locked’

Activate the deactivated units with one or more of the following commands until
the signaling restarts.

b CONF MP:MP=..,Admin. state=Unlocked;

b CONF LIC:LIC..,Admin. state=Unlocked;
b CONF AMX:Side=..,ACCG=..,AMX=..,Admin. state=Unlocked;
b CONF AMX:Side=..,ACCG=..,Admin. state=Unlocked;
b CONF ASN;Side=..,ACCG=..,ASN=..,Admin. state=..,Unlocked;
b CONF ASN;Side=..,ACCG=..,Admin. state=..,Unlocked;
Was the total CCS7 outage resolved (SpecificProblems=totalOutageCCS7, Per-
ceivedSeverity=Cleared)? Y h ... END
N h ... 8

8 Decision block
Are units relevant to the CCS7 outage still set to ’failed’? Y h ... 9
N h ...NM:SSNC

9 Fault clearance for the unit(s)

Correct the faulty units according to the failure message h ...PROC: PRO-
CIN

END

188 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SW02

2.56 Total Outage of (CALLP) NP

SW02

For additional information concerning e.g. commands/tasks, modules and replace/re-

i exchange of modules etc. see 2.1 Comments and Hints.

1 General notes and fault description

SpecificProblems=totalOutageCALLP, PerceivedSeverity=critical
The threshold value (1) for the accessibility of the NP function (Number Portabil-
ity) was undershot. Global network connections are no longer possible. The NP
function supports the call processing process CALLP for global number analysis
and translation.
The number of MPs required for the NP function is defined in a threshold value
(the configured value is 1).
The following units are needed for the NP function or accessibility of the MPUs:
– MP(NP)
– AMX
– ASN h ... 2
2 Determine load type of MP
b DISP MP; h ... 3
3 Analysis
What was the situation leading to the total outage of the NP function?
– during/after the upgrade h ... 4
– during/after the configuration h ... 5
– in connection with a HW fault h ... 6
– the system did not act unusually before the total outage h ... 6

A50016-D3104-M470-3-7620 189
MMN:SSNC Maintenance
SW02 Signaling

4 Total outage of (CALLP) NP during/after the upgrade

The upgrade could not be successfully completed. The threshold value (1) was
not reached for all system-relevant units. A manual fallback to the backup gener-
ation must be started.

The following TERMINATE command has the effect that the upgrade is termi-
nated in a controlled manner and that the system is restarted with a backup
generation.

The following command is only permitted with the approval of the relevant TAC
! personnel.

b TERMINATE;
Conduct postprocessing for
– UMTS network node h ...EMCYMN
EY190

5 Total outage of (CALLP) NP during the configuration

No system operation is possible after deactivation of both MPU(SA)s; a
! LOADREC3 is automatically started.

A system-relevant unit was configured to locked by a command with Hazard

check=no. Since there is deliberately no check for system outage-relevant units
in this case, it is to be assumed that the unit is to be deactivated.

Was the total outage deliberately initiated? Y h ... END

N h ... 6

6 Decision block

The following commands can be used to determine any missing operating

states.

b STAT MP;
b STAT AMX;
b STAT ASN;
Is any system relevant unit set to ’locked’ except definite faulty units? Y h ... 7
N h ... 10

7 Decision block
Does activation of the units resolve the total outage of the (CALLP) NP func-
tion? Y h ... 8
N h ... 9

190 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SW02

8 Activate the units set to ’locked’

Activate the deactivated units with one or more of the following commands until
the (CALLP) NP function restarts.

b CONF MP:MP=..,Side=..,Admin. state=Unlocked;

b CONF AMX:Side=..,ACCG=..,AMX=..,Admin. state=Unlocked;
b CONF AMX:Side=..,ACCG=..,Admin. state=Unlocked;
b CONF ASN;Side=..,ACCG=..,ASN=..,Admin. state=..,Unlocked;
b CONF ASN;Side=..,ACCG=..,Admin. state=..,Unlocked;
Was the total outage of the (CALLP) NP function resolved (SpecificProb-
lems=totalOutageCALLP, PerceivedSeverity=Cleared)? Y h ... END
N h ... 9

9 Decision block
Are units relevant to the (CALLP) NP function outage still set to ’failed’? Y h ... 10
N h ...NM:SSNC

10 Fault clearance for the unit(s)

Correct the faulty units according to the failure message h ...PROC: PRO-
CIN

END

A50016-D3104-M470-3-7620 191
MMN:SSNC Maintenance
SW04 Signaling

2.57 Total Outage of Mobile Switching

SW04

1 General notes and fault description

SpecificProblems=totalOutageMOBILE SWITCHING
PerceivedSeverity=critical
The MOBILE SWITCHING signaling system has failed completely. Calls can no
longer be switched outside the home exchange. The fault is due to undershoot-
ing of the threshold value (1) of active MOBILE SWITCHING-related proces-
sors. (The configured threshold value for all processors is 1.)

The following unit types are required for the signaling:

– MP(SM)
– MP(MM)
– MP(ACC)
– MP(PD)
– MP(RANAP) (only for UMSC)
– MP(SLT-GTT)
– MP(SLT-MTP)
– LIC
– ACCG / AMXE (Ultimate)
– ACCG / ASN
– ATMB to the CP (not in MP platform standalone mode)
– ATMB to the MBD (not in MP platform standalone mode)
Determine the MP load types
b DISP MP; h ... 2
2 Analysis
What was the situation leading to the total MOBILE SWITCHING outage?
– during/after the upgrade h ... 3
– during/after the configuration h ... 4
– in connection with a HW fault h ... 5
– the system did not act unusually before the total outage h ... 5

192 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SW04

3 Total MOBILE SWITCHING outage during/after the upgrade

The upgrade could not be successfully completed. The threshold value (1) was
not reached for all system-relevant units. A manual fallback to the backup gener-
ation must be started.

The following TERMINATE command has the effect that the upgrade is termi-
nated in a controlled manner and that the system is restarted with a backup
generation.

The following command is only permitted with the approval of the relevant TAC
! personnel.

b TERMINATE;
Conduct postprocessing for
– UMTS network node h ...EMCYMN
EY190

4 Total MOBILE SWITCHING outage during/after the configuration

No system operation is possible after deactivating both MPU(SA)s; a
! LOADREC3 is automatically started.

A system-relevant unit was configured to locked by a command with Hazard

check=no. Since there is deliberately no check for system outage-relevant units
in this case, it is to be assumed that the unit is to be deactivated.

Was the total outage deliberately initiated? Y h ... END

N h ... 5

5 Decision block

The following commands can be used to determine any missing operating

states.

b STAT MP;
b STAT LIC;
b STAT AMX;
b STAT ASN;
Is any fault-free unit relevant to the system set to ’locked’? Y h ... 6
N h ... 9

6 Decision block
Does activation of the units resolve the total MOBILE SWITCHING outage? Y h ... 8
N h ... 9

A50016-D3104-M470-3-7620 193
MMN:SSNC Maintenance
SW04 Signaling

7 Activate the units set to ’locked’

Activate the deactivated units with one or more of the following commands until
the signaling restarts.

b CONF MP:MP=..,Admin. state=Unlocked;

b CONF LIC:LIC..,Admin. state=Unlocked;
b CONF AMX:Side=..,ACCG=..,AMX=..,Admin. state=Unlocked;
b CONF AMX:Side=..,ACCG=..,Admin. state=Unlocked;
b CONF ASN;Side=..,ACCG=..,ASN=..,Admin. state=..,Unlocked;
b CONF ASN;Side=..,ACCG=..,Admin. state=..,Unlocked;
Was the total MOBILE SWITCHING outage resolved?
(SpecificProblems=totalOutageMOBILE SWITCHING
PerceivedSeverity=Cleared)? Y h ... END
N h ... 8

8 Decision block
Are units relevant to the MOBILE SWITCHING outage still set to ’failed’? Y h ... 9
N h ...NM:SSNC

9 Fault clearance for the unit(s)

Correct the faulty units according to the failure message h ...PROC: PRO-
CIN

END

194 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SW05

2.58 SAMAR Failure

SW05

2.58.1 Introduction

This procedure describes the necessary measures in case of a SAMAR failure.

2.58.2 Overview: Alarming

If the transfer of charging data from the MP to MP storage disks is interrupted, a Q3 pro-
cessing error alarm will be generated. In the additional text, more detailed information
about the alarm reason will be given.
The following table gives an overview of the possible errors and appropriate actions to
be taken.

2.58.2.1 Q3 alarm message table

The following alarm message table gives an overview of the possible alarms.
The column "necessary actions" includes only a short overview about the necessary ac-
tions to solve a specific problem. To fix the specific problem use the complete error solv-
ing procedure described in chapter “2.58.5 Procedure description”.

Alarm display and Alarm and error message Necessary actions

description

SAMAR full Q3 alarm: Transfer the data from SA-

Q3 Alarm Notification: MAR files to release the
The SAMAR is full, Event type: processingErrorAlarm these files.
all SAMAR files have probableCause: storageCapacityProblem
been completely additionalText: SAMAR FOR <usage> IS FULL: <sa-
filled with tickets, mar>
which have not yet
been released after
transfer.

SAMAR not found Q3 alarm: Create a new SAMAR. If it

Q3 Alarm Notification: already exists, cancel it and
SAMAR has not been Event type: processingErrorAlarm create it again.
created or has been probableCause: fileError
deleted. additionalText: SAMAR FOR <usage> NOT FOUND:
<samar>

Tab. 2.1 Error message table

A50016-D3104-M470-3-7620 195
MMN:SSNC Maintenance
SW05 Signaling

Alarm display and Alarm and error message Necessary actions

description

SAMAR damaged Q3 alarm: Transfer available data from

Q3 Alarm Notification: SAMAR files and release it.
A non-repairable er- Event type: processingErrorAlarm Cancel the SAMAR and cre-
ror has been detect- probableCause: fileError ate it again.
ed on the disk, e.g. additionalText: SAMAR FOR <usage> IS DAMAGED:
sector defect, files in- <samar>
consistent.

SAMAR invalid Pa- Q3 alarm: Compare SAMAR parame-

rameter Q3 Alarm Notification: ters.
Event type: processingErrorAlarm Cancel the SAMAR and cre-
Basic error in SA- probableCause: fileError ate it again.
MAR parameters, additionalText: SAMAR FOR <usage> HAS INVALID
e.g. data length is to PARAMETER: <samar>
large, record size and
record format not
compatible.

SAMAR already Q3 alarm: Change output to another

connected Q3 Alarm Notification: SAMAR or correct the data-
Event type: processingErrorAlarm base.
Another user is cur- probableCause: fileError
rently connected to additionalText: SAMAR FOR <usage> IS ALREADY
this SAMAR. Possi- CONNECTED: <samar>
ble reason for this er-
ror: wrong database.

Tab. 2.1 Error message table

196 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SW05

2.58.3 Variables

SAMAR parameters are project specific. Not all projects use the parameters listed be-
low. Ignore the steps of the procedure, that are not relevant for your project. In the fol-
lowing procedure steps dummy variables are used for tasks and displays. See the
following table:

Variable Meaning Example

<samar> Name of the SAM array. samar1

samar2
...
<samar>.<ext> Name of one file of the SAM array samar1.MAST
(SAMAR name and the extension). samar1.0001
samar1.0002
: : : :
samar1.nnnn
<usage> Accounting type the SAMAR/buffer CGP/Ga routes
is used for. CGP/GaFailureBuffering
PO_RPF:ASCDR

Tab. 2.2 Variables

2.58.4 Transfer mode and saving of SAMAR files

The parameter "Transfer mode" of SAMAR files is project specific. The possible values
are ONE FILE VIEW and MULTIPLE FILE VIEW.
The Q3 task DISP SAMAR:Name of SAM File Array=<samar>,Display action=attr; dis-
plays all attributes of a specific SAMAR.
Transfer mode ONE FILE VIEW handles SAMAR files as one file, transfer and release
of SAMAR files does not allow the manipulation of single SAMAR files.
In case of transfer mode MULTIPLE FILE VIEW each single SAMAR file must be trans-
ferred and released separately.
Projects can have own procedures for saving of the SAMAR files. Within these proce-
dures it is defined how the files should be saved (with an aspect of all regulations con-
cerning the file transfer, e.g. transfer ordered from BMD, saving on Modena computer,
transfer on MOD, transfer on SC, security rules and authorization,...).
In that case, instead of using procedures SW05b and SW05c, the project specific in-
structions for saving of SAMAR files should be used.

A50016-D3104-M470-3-7620 197
MMN:SSNC Maintenance
SW05 Signaling

2.58.5 Procedure description

1 Q3 alarms

Determine the Q3 alarm according to the AMD display and continue the proce-
dure at the given procedure block.

Event type: processingErrorAlarm

- SAMAR FOR <usage> IS FULL: <samar> h ... 6
- SAMAR FOR <usage> NOT FOUND: <samar> h ... 8
- SAMAR FOR <usage> IS DAMAGED: <samar> h ... 10
- SAMAR FOR <usage> HAS INVALID PARAMETER: <samar> h ... 9
- SAMAR FOR <usage> IS ALREADY CONNECTED: <samar> h ... 2

2 SAMAR FOR <usage> IS ALREADY CONNECTED - Information

Another user is already connected to the SAMAR. For safety reasons it is not al-
lowed to connect more than one user to a SAMAR at the same time. Possible
reason for the error: error in the DB.

3 Check user
Check the user of the SAMAR.
b LIST FILE:DIRECTORY NAME=\<samar>.MAST;
Is the value of USER = PO_CPG_FB or PO_RPF? Y h ... 4
N h ... 16

4 Check database
Check the database, therefore compare the outputs of the following commands:
b DISP SACC;
b DISP SCGP;
Do they refer to the same SAMAR? Y h ... 5
N h ... 16

5 Modify database
Make sure that the accounting object and charging gateway object refer not to
the same SAMAR.
b MOD SACC:Acc. user buffer=<samar-x>;
b MOD SCGP:Ga link failure buffering SAMAR ID=<samar-y>; h ... 18

198 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SW05

6 SAMAR FOR <usage> IS FULL - Information

The SAMAR is full, i.e. all SAMAR files have been completely filled with ac-
counting data, which have not been released yet after transfer. In addition to the
possible SAMAR threshold supervision this SAMAR response will be indicated.

7 Decision

In case of project specific instructions for saving of the SAMAR files, proceed
according to the given instructions.
Otherwise perform the following:

b DISP SAMAR:Name of SAM File Array=<samar>,Display action=attr;

Is the SAMAR transfer mode MULTIPLE FILE VIEW? Y i ...PROC: SW05B

N i ...PROC: SW05C

Continue in... h ... 18

8 SAMAR FOR <usage> NOT FOUND - Information

No SAMAR was found by the system. The SAMAR has not been created, or has
been deleted. h ... 17

9 SAMAR FOR <usage> HAS INVALID PARAMETER - Information

The system has detected a basic error, e.g. the data length is too large for the
SAMAR. h ... 16

10 SAMAR FOR <usage> IS DAMAGED - Information

A not repairable error on disk has been detected (e.g. sector defect, files incon-
sistent).

11 Decision
b DISP SAMAR:Name of SAM File Array=<samar>,Display action=attr;
Note the parameters TRANSFER MODE and FILE SIZE.

Is the SAMAR transfer mode MULTIPLE FILE VIEW? Y h ... 13

N h ... 12

A50016-D3104-M470-3-7620 199
MMN:SSNC Maintenance
SW05 Signaling

12 Transfer of SAMAR data

In case of project specific instructions for saving of the SAMAR files, proceed
according to the given instructions.
Otherwise continue according to... i....PROC: SW05C

Continue in... h ... 16

13 Transfer of SAMAR data

In case of project specific instructions for saving of the SAMAR files, proceed
according to the given instructions.
Otherwise continue according to... i....PROC: SW05B

Was the transfer of SAMAR data successful? Y h ... 16

N h ... 14

14 Decision
Have modified the maximum copy size? Y h ... 16
N h ... 15

15 Modify maximum copy size

Possibly only one file of the SAMAR is damaged. In this case it may be possible
to transfer and rescue the other files of the SAMAR. Therefore it is necessary to
set the “maximum copy size” to the smallest possible value. The smallest value
is the size in MByte of one SAM file inside to the SAM file array displayed as pa-
rameter FILE SIZE.

Modify the maximum copy size value of the alarmed SAMAR.

b MOD SAMAR:Name of SAM File Array=<samar>,Max size of copies=<file h ... 13
size>;

16 Cancel SAMAR
Cancel the alarmed SAMAR.
b CAN SAMAR:Name of SAM File Array=<samar>;

200 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SW05

17 Create new SAMAR

Create a new SAMAR.
b CR SAMAR:Name of SAM File Array=<samar>,Number of Files=<fno>,File
size=<fsize>,Record size=<rsize>,Record format=<rformat>,Transfer
mode=<transmod>,Max size of copies=<maxsize>,No. of safety copies=<sc-
no>,Alarm threshold minor=<atminor>,Alarm threshold major=<atmajor>,Alarm
threshold critical=<atcritical>,Alarm action minor=<aactminor>,Alarm action
major=<aactmajor>,Alarm action critical=<aactcritical>;

The needed values for SAM File Array, Number of Files, File Size and Alarm
thresholds should be entered according to the project specific documentation.

18 Transfer of accounting data

Force the transfer of accounting data to SAMAR. In case of GDC user for SA-
MAR files the command is rejected, do not worry.
b TRANS SACCB:Acc. user buffer=<usage>;

19 Check filling of SAMAR files

Check the filling of the SAMAR.
b LIST FILE:DIRECTORY NAME=\<samar>;
Note the value of "CURR-FSIZE".

Wait an adequate time.

The SAMAR files should be filled with billing data. Therefore their size should
swell.

b LIST FILE:DIRECTORY NAME=\<samar>;

Note the value of "CURR-FSIZE".

When the SAMAR files have been filled correctly, the value CURR-FSIZE must
increase.

Has the CURR-FSIZE swelled up during the waiting time? Y h ... 24

N h ... 20

A50016-D3104-M470-3-7620 201
MMN:SSNC Maintenance
SW05 Signaling

20 Execute MP:ACC recovery (PROREC3)

Execute a MP:ACC recovery of level PROREC3.

Insert in the following Q3 task the number of the MP:ACC for parameter
"MP=mpacc".

b RECOV MP:MP=<mpacc>,Scope=Platform,Depth=Selective recovery,Mea-

sures=No measures;

Wait a few minutes.

b LIST FILE:DIRECTORY NAME=\<samar>;

Has the CURR-FSIZE swelled up during the waiting time? Y h ... 24

N h ... 21

21 Execute MP:OAM recovery (PROREC3)

Execute a MP:OAM recovery of level PROREC3.

Insert in the following Q3 task the number of the MP:OAM for parameter
"MP=mpoam".

b RECOV MP:MP=<mpoam>,Scope=Platform,Depth=Selective recovery,Mea-

sures=No measures;

Wait a few minutes.

b LIST FILE:DIRECTORY NAME=\<samar>;

Has the CURR-FSIZE swelled up during the waiting time? Y h ... 24

N h ... 22

202 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SW05

22 Execute MP:ACC recovery (FULLREC)

Execute a MP:ACC of level FULLREC.

Insert in the following Q3 task the number of the MP:ACC for parameter
"MP=mpacc".

b RECOV MP:MP=<mpacc>,Scope=Platform,Depth=Full recovery,Measures=No

measures;

Wait a few minutes.

b LIST FILE:DIRECTORY NAME=\<samar>;

Has the CURR-FSIZE swelled up during the waiting time? Y h ... 24

N h ... 23

23 Execute MP:OAM recovery (FULLREC)

Execute a MP:OAM of level FULLREC.

Insert in the following Q3 task the number of the MP:OAM for parameter
"MP=mpoam".

b RECOV MP:MP=<mpoam>,Scope=Platform,Depth=Full recovery,Mea-

sures=No measures;

Wait a few minutes.

b LIST FILE:DIRECTORY NAME=\<samar>;

Has the CURR-FSIZE swelled up during the waiting time? Y h ... 24

N h ... 28

24 Check alarm
Was the alarm cleared automatically? Y h ... 26
N h ... 25

25 Clear alarm
Clear the alarm manually.

26 Decision
Were SAMAR files copied to the Switch Commander while performing this pro-
cedure? Y h ... 27
N h ... END

A50016-D3104-M470-3-7620 203
MMN:SSNC Maintenance
SW05 Signaling

27 Transfer data
Transfer charging data according to the project specific instructions to the billing h ... END
center.

28 Contact Siemens

! A serious fault in the system exists.

Contact immediately the responsible Siemens service department!

Continue according to the recommendations from Siemens service department. h ... END

END

204 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SW05B

2.59 Transfer of SAMAR Data (Multiple File View)

SW05B

2.59.1 Introduction

This procedure is a sub-procedure from SW05.

It describes
– transfer of SAMAR files in MULTIPLE FILE VIEW,
– release of SAMAR files

Please check carefully the transfer of SAMAR files to the billing center, local SC or file
! server.
As soon as the SAMAR file is deleted, all accounting data are lost!

A50016-D3104-M470-3-7620 205
MMN:SSNC Maintenance
SW05B Signaling

2.59.2 Procedure description

1 Inform billing center

Inform the billing center, that all accounting data have to be transferred yet.
Was the billing center able to transfer the accounting data? Y h ... 3
N h ... 2

2 Copy SAMAR files from MP-MDD to the Switch Commander

Copy the SAMAR files from MP-MDD into the Switch Commander user home di-
rectory.

Use UNC file names for the destination address. A DOS file path (such as
C:\TEMP\...) will not be accepted.

b RCV FILE:SOURCE FILE NAME=SYS:\<samar.ext>, DESTINATION FILE

NAME=\\<device>\SCBase\UserHomeDir\<user>\<samar.ext>.bin,TRANSFER
TYPE=FTP,FILE WRITING MODE=OVERWRITE,COPY MODE=BINARY;

For MULTIPLE FILE MODE this command must be performed for every
available SAM file inside of the SAM array which is filled or active!

3 Check copy counter

Check the execution copy counter to control, that all accounting data are trans-
ferred correctly.
b LIST FILE:DIRECTORY NAME=\<samar.ext>;
Compare the values of COPIES_REQU (required copies) and EXEC_COPIES
(executed copies).

All data are transferred correctly, when the value of executed copies is equal or
higher than the value of required.

For MULTIPLE FILE MODE this check must be performed for every avail-
able SAM file which is filled or active!

Were all data transferred correctly? Y h ... 4

N h ... 5

4 Release files
Release the just transferred files.
b CAN FILE:TRANSFER TYPE=FTP,FILE NAME=<samar.ext>;
Are there further files? Y h ... 5
N h ... 6

206 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SW05B

5 Repetition: Copy SAMAR files from MP-MDD to the Switch Commander

Repeat the copy of SAMAR files from MP-MDD into the Switch Commander
user home directory.
At repetition of the command, it is essential to change the DESTINATION FILE
! NAME!
Otherwise the old file will be overwritten and important accounting data will be
lost!
Count up the variable <x> in the DESTINATION FILE NAME with every repetition of
the command!

Use UNC file names for the destination address. A DOS file path (such as
C:\TEMP\...) will not be accepted.

b RCV FILE:SOURCE FILE NAME=SYS:\<samar.ext>, DESTINATION FILE

NAME=\\<device>\SCBase\UserHomeDir\<user>\<samar.ext>.<x>.bin,TRANS-
FER TYPE=FTP,FILE WRITING MODE=OVERWRITE,COPY MODE=BINARY;
h ... 3

6 Continue SW05
Continue procedure SW05 in the decision block in which it was left.

END

A50016-D3104-M470-3-7620 207
MMN:SSNC Maintenance
SW05C Signaling

2.60 Transfer of SAMAR Data (One File View)

SW05C

2.60.1 Introduction

This procedure is a sub-procedure from SW05.

It describes
– transfer of SAMAR files in ONE FILE VIEW,
– release of SAMAR files

Please check carefully the transfer of SAMAR files to the billing center, local SC or file
! server.
As soon as the SAMAR file is deleted, all accounting data are lost!

208 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SW05C

2.60.2 Procedure description

1 Inform billing center

Inform the billing center, that all accounting data have to be transferred yet.
Was the billing center able to transfer the accounting data? Y h ... 3
N h ... 2

2 Copy SAMAR files from MP-MDD to the Switch Commander

Copy the SAMAR files from MP-MDD into the Switch Commander user home di-
rectory.

Use UNC file names for the destination address. A DOS file path (such as
C:\TEMP\...) will not be accepted.

b RCV FILE:SOURCE FILE NAME=SYS:\<samar>, DESTINATION FILE

NAME=\\device\SCBase\UserHomeDir\user\<samar>.bin,TRANSFER
TYPE=FTP,FILE WRITING MODE=OVERWRITE,COPY MODE=BINARY;

3 Check copy counter

Check the execution copy counter to control, that all accounting data are trans-
ferred correctly.
b LIST FILE:DIRECTORY NAME=\<samar>;
Compare the values of COPIES_REQU (required copies) and EXEC_COPIES
(executed copies).

All data are transferred correctly, when the value of executed copies is equal or
higher than the value of required.

Note also the value of MAX COPY. It determines the maximum of data that can
be copied by a single RCV FILE. Depending of this maximum value, maybe the
RCV FILE command must be executed several times to copy all accounting da-
ta.

4 Release files
Release the just transferred files.
b CAN FILE:TRANSFER TYPE=FTP,FILE NAME=<samar>;
Are all SAM files transferred and released correctly? Y h ... 6
N h ... 5

A50016-D3104-M470-3-7620 209
MMN:SSNC Maintenance
SW05C Signaling

5 Repetition: Copy SAMAR files from MP-MDD to the Switch Commander

Repeat the copy of SAMAR files from MP-MDD into the Switch Commander
user home directory.
At repetition of the command, it is essential to change the DESTINATION FILE
! NAME!
Otherwise the old file will be overwritten and important accounting data will be
lost!
Count up the variable <x> in the DESTINATION FILE NAME with every repetition of
the command!

Use UNC file names for the destination address. A DOS file path (such as
C:\TEMP\...) will not be accepted.

b RCV FILE:SOURCE FILE NAME=SYS:\<samar>, DESTINATION FILE

NAME=\\device\SCBase\UserHomeDir\user\<samar>.<x>.bin,TRANSFER
TYPE=FTP,FILE WRITING MODE=OVERWRITE,COPY MODE=BINARY;
h ... 3

6 Continue SW05
Continue procedure SW05 in the decision block in which it was left.

END

210 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SW06

2.61 MP/Buffer failure

SW06

2.61.1 Introduction

This procedure describes the necessary measures in case of a MP or buffer failure.

2.61.2 Overview: Alarming

If the transfer of charging data from the MP to MP storage disks is interrupted, a Q3 pro-
cessing error alarm will be generated. In the additional text, more detailed information
about the alarm reason will be given.
The following table gives an overview of the possible errors and appropriate actions to
be taken.

2.61.2.1 Q3 alarm message table

The following alarm message table gives an overview of the possible alarms.
The column "necessary actions" includes only a short overview about the necessary ac-
tions to solve a specific problem. To fix the specific problem use the complete error solv-
ing procedure described in chapter “2.61.4 Procedure description”.

Alarm display and Alarm and error message Necessary actions

description

No response from Q3 alarm: Wait. If the problem still ex-

SAMAR Q3 Alarm Notification: ists recover the systems.
Event type: processingErrorAlarm If the problem still exists
SAMAR manage- probableCause: underlyingResourceNotAvailable contact Siemens service de-
ment does not re- additionalText: SAMAR FOR <usage> IS NOT RE- partment.
spond to write SPONDING: <samar>
charging data.

Tab. 2.3 Error message table

A50016-D3104-M470-3-7620 211
MMN:SSNC Maintenance
SW06 Signaling

Alarm display and Alarm and error message Necessary actions

description

LDC buffer Q3 alarm: Check for previously gener-

MP<xxx> 80% ex- Q3 Alarm Notification: ated alarms.
ceeded Event type: processingErrorAlarm
probableCause: storageCapacityProblem
LDC buffer filling lev- additionalText: LDC BUFFER MP<xxx> 80% EXCEED-
el exceeds 80%. ED, FEAT
Packet handling/flow GO_FORWARD_WITH_LACK_OF_ACC_RESOURCE
of existing PDP con- APPLIES
texts will not be
harmed. Depending
on feature 'Go for-
ward with Lack of Ac-
counting Resources'
activation of new
PDP contexts may be
blocked.

LDC buffer Q3 alarm: Check for previously gener-

MP<xxx> full Q3 Alarm Notification: ated alarms.
Event type: processingErrorAlarm
LDC buffer is full. probableCause: storageCapacityProblem
Packet handling/flow additionalText: LDC BUFFER MP<xxx> 80% EXCEED-
of existing PDP con- ED, FEAT
texts will not be GO_FORWARD_WITH_LACK_OF_ACC_RESOURCE
harmed. Depending APPLIES
on feature 'Go for-
ward with Lack of Ac-
counting Resources'
activation of new
PDP contexts may be
blocked. Accounting
data may get lost
LDC on MP<xxx> Q3 alarm: Check MP:ACC for ongoing
cannot connect Q3 Alarm Notification: recovery.
GDC Event type: processingErrorAlarm
probableCause: underlyingResourceNotAvailable
LDC cannot connect additionalText: LDC ON MP<xxx> CANNOT CONNECT
GDC service. LDC is GDC
buffering accounting
data. LDC buffer may
overflow subsequent-
ly.

Tab. 2.3 Error message table

212 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SW06

Alarm display and Alarm and error message Necessary actions

description

GDC resources full Q3 alarm: Contact Siemens service

Q3 Alarm Notification: department.
The GDC resources Event type: processingErrorAlarm
are completely filled. probableCause: storageCapacityProblem
additionalText: GDC RESOURCES FULL

The GDC resources Q3 alarm: No action - only for informa-

are filled to 60%. Q3 Alarm Notification: tion.
Alarm with minor se- Event type: processingErrorAlarm
verity. probableCause: storageCapacityProblem
additionalText: GDC 60% THRESHOLD REACHED

The GDC resources Q3 alarm: No action - only for informa-

are filled to 80%. Q3 Alarm Notification: tion.
Alarm with major se- Event type: processingErrorAlarm
verity. probableCause: storageCapacityProblem
additionalText: GDC 80% THRESHOLD REACHED

The GDC resources Q3 alarm: Contact Siemens service

are filled to 90%. Q3 Alarm Notification: department.
Alarm with major se- Event type: processingErrorAlarm
verity. probableCause: storageCapacityProblem
additionalText: GDC 90% THRESHOLD REACHED

GBM Buffer full or Q3 alarm: Check buffer destination

filling level reached Q3 Alarm Notification: (SAMAR, CGP Link). In
Event type: processingErrorAlarm case of SAMAR problem
Due to delayed out- probableCause: storageCapacityProblem see according alarm ac-
put, the GBM-buffer additionalText: OVERFLOW OF GBM BUFFER, USED tion.Check CGP communi-
became full, or nearly FOR <usage> cation. Check status of
full. Further charging MP:OAM/OAMD. Check if
data will be discard- the SAMAR fill state increas-
Q3 alarm:
ed! es. If the destination is avail-
Q3 Alarm Notification:
able recover MP:ACC
Event type: processingErrorAlarm
probableCause: storageCapacityProblem
additionalText: FILLING LEVEL REACHED IN GBM
BUFFER, USED FOR <usage>

Tab. 2.3 Error message table

A50016-D3104-M470-3-7620 213
MMN:SSNC Maintenance
SW06 Signaling

2.61.3 Variables

SAMAR parameters are project specific. Not all projects use the parameters listed be-
low. Ignore the steps of the procedure, that are not relevant for your project. In the fol-
lowing procedure steps dummy variables are used for tasks and displays. See the
following table:

Variable Meaning Example

<samar> Name of the SAM array. samar1

samar2
...
<xxx> Site ID 026
<usage> Accounting type the SAMAR/buffer CGP/Ga routes
is used for. CGP/GaFailureBuffering
PO_RPF:ASCDR

Tab. 2.4 Variables

214 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SW06

2.61.4 Procedure description

1 Q3 alarms

Determine the Q3 alarm according to the AMD display and continue the proce-
dure at the given procedure block.

Event type: processingErrorAlarm

- additionalText: SAMAR FOR <usage> IS NOT RESPONDING : <samar> h ... 9
- additionalText: LDC BUFFER MP<xxx> 80% EXCEEDED, FEAT h ... 4
GO_FORWARD_WITH_LACK_OF_ACC_RESOURCE APPLIES
- additionalText: LDC BUFFER MP<xxx> FULL, FEAT h ... 3
GO_FORWARD_WITH_LACK_OF_ACC_RESOURCE APPLIES
- additionalText: LDC ON MP<xxx> CANNOT CONNECT GDC h ... 2
- additionalText: GDC 60% THRESHOLD REACHED h ... 17
- additionalText: GDC 80% THRESHOLD REACHED h ... 17
- additionalText: GDC 90% THRESHOLD REACHED h ... 18
- additionalText: GDC RESOURCES FULL h ... 18
- additionalText: FILLING LEVEL REACHED IN GBM BUFFER, USED FOR h ... 7
<usage>
- additionalText: OVERFLOW OF GBM BUFFER, USED FOR <usage> h ... 7

2 LDC CANNOT CONNECT GDC - Information

LDC cannot connect GDC service. LDC is buffering arising accounting data.
LDC buffer may overflow subsequently. h ... 6

3 LDC BUFFER MP<xxx> FULL, FEAT GO_FORWARD_WITH_LACK_OF_

ACC_RESOURCE APPLIES - Information

LDC FIFO buffer is overflow. Since there is no buffer left, further arising charging
data will be discarded. This alarm is an escalation of alarm 'LDC FIFO Fill Level
Eighty Percent Exceeded', which should have been occurred previously.

Continue in block... h ... 4

A50016-D3104-M470-3-7620 215
MMN:SSNC Maintenance
SW06 Signaling

4 LDC BUFFER MPxxx 80% EXCEEDED, FEAT GO_FORWARD_WITH_

LACK_OF_ACC_RESOURCE APPLIES - Information

LDC is excessively buffering data. Reason is absence of GDC response. Activa-

tion of new PDP contexts will be blocked automatically by overload control when
feature 'Go forward with Lack of Resources' is deactivated. Overload control will
cancel blocking of PDP context activation, when LDC FIFO fill level turns back
below sixty percent. When GDC resource is available again the alarm should be
cleared automatically.

5 Decision
Check for following alarms, which should be occurred previously and may be still
unsolved.
Continue according to the found alarm:
– “SAMAR FOR <usage> IS NOT RESPONDING : <samar>” h ... 9
– “GDC RESOURCES FULL” h ... 18
– “FILLING LEVEL REACHED IN GBM BUFFER, USED FOR <usage>” h ... 7
– Any other SAMAR alarm h ...PROC: SW05
– No previous alarm h ... 6

6 No response from GDC

No response from GDC, even though there is no SAMAR and no GBM problem
reported.

Check MP:ACC for ongoing recovery.

Contact the responsible Siemens service department to get more information.
Continue according to the recommendations from Siemens service department. h ... END
7 OVERFLOW OF GBM BUFFER, USED FOR <usage> / FILLING LEVEL
REACHED IN GBM BUFFER, USED FOR <usage> - Information

GBM-buffer-overflow or reaching of a high filling level mostly is a result of an er-

ror in the data-output to MP-SAMAR-disk file or to CGP. In this case, further
alarms were started. If the reasons for these alarms will be removed, data out-
put will become possible again, and the overflow / filling level alarm will be
stopped automatically.

216 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SW06

8 Decision
Check for following alarms, which should be occurred previously and may be still
unsolved.
Continue according to the found alarm:
– “No response from SAMAR” h ... 9
– Any other SAMAR alarm h ...PROC: SW05
– CGP alarms h ...PROC: LI05

9 SAMAR FOR <usage> IS NOT RESPONDING - Information

No response was received from MP - SAMAR application within 1 minute.

Sometimes, it happens that SAMAR-application is busy with other tasks. In this
case, the alarm will be started, and data output will be repeated after a delay of
one minute. In most cases, the SAMAR-application then is able to handle the
data output, and therefore the alarm will be stopped automatically.

Wait a few minutes.

Check if alarm stays active for a longer time. Check also the ATM bus.

Check the filling of the SAMAR.

b LIST FILE:DIRECTORY NAME=\<samar>;
Note the value of "CURR-FSIZE".

Wait an adequate time.

The SAMAR files should be filled with billing data. Therefore their size should
swell.

b LIST FILE:DIRECTORY NAME=\<samar>;

Note the value of "CURR-FSIZE".

When the SAMAR files have been filled correctly, the value CURR-FSIZE must
increase.

Has the CURR-FSIZE swelled up during the waiting time? Y h ... 15

N h ... 10

A50016-D3104-M470-3-7620 217
MMN:SSNC Maintenance
SW06 Signaling

10 Execute MP:ACC recovery (PROREC3)

Execute a MP:ACC recovery of level PROREC3 and wait a few minutes.

Insert in the following Q3 task the number of the MP:ACC for parameter
"MP=mpacc".

b RECOV MP:MP=<mpacc>,Scope=Platform,Depth=Selective recovery,Mea-

sures=No measures;

Wait a few minutes.

b LIST FILE:DIRECTORY NAME=\<samar>;

Has the CURR-FSIZE swelled up during the waiting time? Y h ... 15

N h ... 11

11 Execute MP:OAM recovery (PROREC3)

Execute a MP:OAM recovery of level PROREC3 and wait a few minutes.

Insert in the following Q3 task the number of the MP:OAM for parameter
"MP=mpoam".

b RECOV MP:MP=<mpoam>,Scope=Platform,Depth=Selective recovery,Mea-

sures=No measures;

b LIST FILE:DIRECTORY NAME=\<samar>;

Has the CURR-FSIZE swelled up during the waiting time? Y h ... 15

N h ... 12

12 Execute MP:ACC recovery (FULLREC)

Execute a MP:ACC of level FULLREC and wait a few minutes.

Insert in the following Q3 task the number of the MP:ACC for parameter
"MP=mpacc".

b RECOV MP:MP=<mpacc>,Scope=Platform,Depth=Full recovery,Measures=No

measures;

b LIST FILE:DIRECTORY NAME=\<samar>;

Has the CURR-FSIZE swelled up during the waiting time? Y h ... 15

N h ... 13

218 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SW06

13 Execute MP:OAM recovery (FULLREC)

Execute a MP:OAM of level FULLREC and wait a few minutes.

Insert in the following Q3 task the number of the MP:OAM for parameter
"MP=mpoam".

b RECOV MP:MP=<mpoam>,Scope=Platform,Depth=Full recovery,Mea-

sures=No measures;

b LIST FILE:DIRECTORY NAME=\<samar>;

Has the CURR-FSIZE swelled up during the waiting time? Y h ... 15

N h ... 14

14 Contact Siemens
Contact the responsible Siemens service department to get more information.
Continue according to the recommendations from Siemens service department. h ... END

15 Check alarm
Is the fault cleared automatically? Y h ... END
N h ... 16

16 Clear alarm
Clear the alarm manually h ... END

17 GDC RESOURCE THRESHOLD 60% / 80% - Information

The for each call a GDCID from the MP:ACC is requested. Charging data is
stored into one or more probe data container (PDC). The PDC's, associated
with an unique GDCID are send to the MP:ACC. A release PDC indicates the
end of a call.
The MP:ACC reads the charging data out of the containers and releases the
GDCID and the containers, which are than available for further use. If the re-
lease PDC is missing or any other mismatch in the PDC containers occurs, the
MP:ACC does not release the GDCID and containers.
• Non released containers filling the GDC memory and initiate storage capac-
ity problems.
• A lack of resources occurs if all GDCID's are in use.

No further actions are required yet, but the alarm is to be observed. h ... END

A50016-D3104-M470-3-7620 219
MMN:SSNC Maintenance
SW06 Signaling

18 GDC RESOURCE THRESHOLD 90% / GDC RESOURCE FULL - Information

The for each call a GDCID from the MP:ACC is requested. Charging data is
stored into one or more probe data container (PDC). The PDC's, associated
with an unique GDCID are send to the MP:ACC. A release PDC indicates the
end of a call.
The MP:ACC reads the charging data out of the containers and releases the
GDCID and the containers, which are than available for further use. If the re-
lease PDC is missing or any other mismatch in the PDC containers occurs, the
MP:ACC does not release the GDCID and containers.
• Non released containers filling the GDC memory and initiate storage capac-
ity problems.
• A lack of resources occurs if all GDCID's are in use.

19 Contact Siemens

! A serious fault in the system exists.

Contact immediately the responsible Siemens service department!

Continue according to the recommendations from Siemens service department. h ... END

END

220 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SW07

2.62 HOP Communication failure

SW07

HOP Communication failure is not valid for PS switches!

i

1 Information

HOP Communication failure is not valid for PS switches.

END

A50016-D3104-M470-3-7620 221
MMN:SSNC Maintenance
SW99 Signaling

2.63 Software Errors

SW99

1 General notes and fault description

After numerous software errors and on reaching a threshold, a LOADREC2 ’lo-

cal’ recovery (according to the system output in MP/ACCG/LIC) was started for
the processor in question.
If system stability cannot be restored using the LOADREC2 (in one or more pro-
cessors), the units will be configured to ‘failed’ when the next threshold is
reached, with the exception of the last system-relevant MP of a load type.
If the escalation in the basic operation for the last system-relevant MP of a load
type (e.g.: MP(SA) MP=1, MP(SM) MP=2, not MP:STATS)) was unsuccessful, a
system-wide LOADREC2 is started.
If yet another threshold is exceeded, the system-wide LOADREC2 escalates to
a system-wide LOADREC3 with fallback to an older generation. A LOADREC3
with fallback to an older generation created an critical alarm. Only the command
RSET ALSSNCR can cancel the alarm.
• Exception MP:SA
– If the MP:SA reached the threshold for LOADREC2 (local) without suc-
cessful basic operation, a system-wide LOADREC2 is started instead.
– If the LOADREC2 ’local’ was unsuccessful, the last system-relevant MP of
the load type escalates to basic operation. Setting the basic operation
mode is an attempt to maintain switching operations, albeit in a restricted
manner.
Basic operation:
• If it is not possible to access any valid APS (generation) or any MDD, then
instead of executing a LOADREC2 ’local’ for the last MP of a load type, this
unit is set to the basic operation mode without MDD after FULLREC.
• Exception: MP:SA
– If the MP:SA reached the threshold after unsuccessful FULLREC, it is
switched to basic operation. This is regardless of whether a valid
APS(generation) or MDD can be accessed.
One consequence of a recovery in the MP(SA) is that no communication is pos-
sible between SSNC and Switch commander (over the Ethernet interface) until
recovery step SP3 has been reached. The time required to reach recovery step
SP3 varies according to the recovery level and amount of data to be reloaded,
and can be up to 1 hour. The Ethernet interface is monitored by means of polling
messages. If the polling messages are not received, a message is output indi-
cating failure of communication with the SSNC.
Units that are not reactivated following a recovery are subjected to post-pro-
cessing. Only if post-processing fails to solve the problem are the units that
could not be reactivated configured to ’failed’. Fault clearance must then be per-
formed in accordance with the appropriate hardware fault clearance procedure.

222 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SW99

However, as post-processing can take several hours it is advisable to determine

which units have not yet been reactivated by means of status interrogations and,
if necessary, to take action giving preference to activating operation-critical
units.

A50016-D3104-M470-3-7620 223
MMN:SSNC Maintenance
SW99 Signaling

2 Recovery
Action is required in connection with the following recoveries:
– LOAD REC2, local
This recovery is started if the number of software errors for a particular pro-
cessor platform exceeds a defined threshold. h ... 3
– LOAD REC2, system-wide
is a recovery without change of generation involving an MP platform outage
lasting about 10 min. A major alarm is set when this recovery is started, and
it is cleared if the recovery runs successfully. h ... 7
– LOAD REC3 in MP platform with change of generation,
is a system-wide recovery started automatically by the system when a
threshold for the number of unsuccessful attempts at system-wide LOAD
REC2 is exceeded. A change of generation in the MP platform area brings
with it a change of generation in the CP platform (ISTART 2G). This recovery
raises a critical alarm, which has to be cleared manually by the command
RSET ALSSNCR. h ... 8
– LOAD REC3 in MP platform without change of generation,
is a system-wide recovery without change of generation that can only be
started manually. This recovery raises a major alarm, which is cleared if the
recovery is executed successfully. h ... 9
3 LOAD REC 2 on platform

The symptom data are edited using h ...NM:SSNC

NON
Only if the LOAD REC 2 has been performed for the MP:PD or MP:MM or
MP:RANAP platform:
Was it possible to restore system stability for the MP:PD/MM/RANAP after
LOAD REC 2? Y h ... END
N h ... 4

4 MP activation (for PD-SH / MM / RANAP)

b CONF MP: MP=..., Side=..., Admin. state=Unlocked;
Did the unit become active again (only green LED is lit)? Y h ... END
N h ... 5

5 MPU fault clearance (for PD-SH / MM / RANAP)

Carry out extended MPU fault clearance i....PROC: SNC13
Did the unit become active again (only green LED is lit)? Y h ... END
N h ... 6

6 LOAD REC 2 system-wide (manually started)

A LOAD REC 2 system-wide has to be started manually. Perform this recovery

only with authorization from the appropriate service departments!

224 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling SW99

7 LOAD REC 2 system-wide

The symptom data are edited using h ...NM:SSNC

NON

8 LOAD REC 3 with change of generation

Post-processing i ...EMCYMN
EY190

The symptom data are edited using h ...NM:SSNC

NON

9 LOAD REC 3 without change of generation

This recovery is started manually and must not be started without authorization
from the appropriate service departments!

This recovery can be started manually in cases where repeated recoveries oc-
cur in the system without causing thresholds to be exceeded and hence without
triggering the automatic escalation of recovery levels.

The symptom data are edited using h ...NM:SSNC

NON

END

A50016-D3104-M470-3-7620 225
MMN:SSNC Maintenance
TM01 Signaling

2.64 Invalid Time and Date

TM01

General notes
This alarm only occurs in standalone mode.
There is no active radio clock available after system shutdown or cold reset with subse-
quent re-start of the system. The system time is insecure. The alarm is raised every 10
min., until time is set and confirmed.
If an active radio clock is available in the system the system time will refresh automati-
cally and an alarm is not raised. If the radio clock fails during normal operation an alarm
will not be raised as well.
For additional information concerning e.g. commands/tasks, modules and replace/re-
i exchange of modules etc. see 2.1 Comments and Hints.

1 Decision block

Is there a radio clock installed in the system? Y h ... 2

N h ... 5

2 Decision block
Is the radio clock de-activated? Y h ... 3
N h ... 4

3 Activate radio clock

Switch on the radio clock and assure that the radio clock data are correct.

Wait until the time synchronization is finished. h ... END

4 Nonstandard maintenance

Although an active radio clock is available the system time has not been syn-
chronized. h ...NM:SSNC

5 Set time and save

b MOD SYSTIME:System time=..; h ... END

END

226 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling TR01

2.65 Trunk Group Alarm

TR01

1 Description

A summation alarm for signaling and synchronization faults for trunks is set with
this message – i.e., no level-4 maintenance or synchronization messages are
acknowledged. The alarm is set for the trunk group in which one or more trunks
first failed. The alarm is not cancelled until there are no signaling or synchroni-
zation faults in trunks or until the values have fallen below the threshold set for
this kind of fault. Once the fault is cleared, it may take up to 15 minutes before
the alarm is reset. The alarm mask displays either the first message that was
not acknowledged or – if a threshold value <> 0 is set – the message that
caused the threshold value to be exceeded.
The cause of the alarm may be located in the exchange which activated the
summation alarm due to a HW fault. Fault clearance is then performed using the
corresponding MMN procedure matching the MMN number of the fault report.
The cause of these alarms often does not lie in the exchange in which the alarm
is set. Possible causes include
• circuits (CICs) are not (correctly) created in the destination exchange;
• there are problems in the network, causing messages or acknowledgments
not to reach their destination because of circular routing (often in conjunction
with CCS7 overload messages) or barred routes.
Temporary measures that can be taken if it is not possible to reach the mainte-
nance personnel in the adjacent exchange are:
• to set an administrative block for the CIC concerned in the own exchange or
• to modify the priorities of the routes.
The OMN contains instructions for these tasks.

If the alarm is triggered by a change in the threshold value, there are no entries
under CIC and SENT MSG. The alarm is not set or cancelled until the process
is initiated once again.

Continue h ... 2

2 Decision block
Could the alarm have been activated due to a HW fault in the MP platform? Y h ... 3
N h ... 4

3 HW fault in the MP platform

Perform fault clearance according to the failure message. h ...PROC: PRO-
CIN

A50016-D3104-M470-3-7620 227
MMN:SSNC Maintenance
TR01 Signaling

4 Decision block
b STAT TRUNK:TGNO=..,STATUS=NSYNP&NSYN;
The following states are taken into consideration in this procedure:
– Entered state = ... & C7SF (C7 signaling error): One (several) report(s) of a
blocked state (MBG, HGB, BLO or CGB, BLO) or an unblocked state (MGU,
HGU, UBL or CGU, UBL) was (were) not acknowledged. h ... 5
– Entered states = ... &NSYN & C7SF: One (several) reset message(s) (GRS
or RSC) was (were) not acknowledged. h ... 5
– Entered state = ... & NSYNP: The repeated transmission of reset messages
for a CIC with the status ... NSYN and C7SF was not acknowledged with a
valid acknowledgement within x minutes (definable threshold value). In the
state NSYNP the reset message is only repeated every 15 minutes. h ... 5
5 Analyze messages
Analyze messages
If necessary, the values for H0/H1 or the message type can be evaluated using i....PROC:
TAB:MSG. MSG:DISCARD
Is there enough information to allow the fault to be cleared? Y h ... 21
N h ... 6

6 Notes on CIC status NSYNP or NSYNP&C7SF or C7SF

In the following procedures, the home exchange is designated A and the desti-
nation exchange (DPC of the originating message) is designated B. All signaling
points situated in-between are designated A1, A2 etc. in a forward direction, and
B1, B2 in a backward direction. The commands used in the procedure are
EWSD-specific. In the case of partner exchanges which are not on EWSD, loca-
tion is with the aid of an appropriate command. All participating partner exchang-
es must be involved in clearing the error. Errors can originate as follows:
• CIC between the exchanges A-B have been set up differently.
• The reset message is missing or the reset messages are not
reaching the B exchange.
• Acknowledgments are missing or the acknowledgments are h ... 7
not reaching A exchange.

228 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling TR01

7 Locating the affected voice circuit

Determine the signaling link

b DISP C7TGREL:TGNO=..;

Determine the exchange B

b DISP SIGDP:Net name=..;

Process B exchange (DPC of the entry message).
Notify the service personnel at B exchange.
The exchange trunk groups must be determined in A exchange if the entry mes-
sage is valid for the following command).
b STAT TRUNK:TGNO=..,STATUS=..;
Check the data created in the exchanges A and B for trunks in the state NSYN
– The same CIC must be set up.
– The data of the exchange trunks must match each other. h ... 8
8 Decision block
Were irregularities ascertained when setting up the exchange trunks? Y h ... 9
N h ... 10

9 Correction of the created exchange trunks

The incorrectly created exchange trunks in the exchange must be corrected h ... 21
and/or correctly recreated according to OMN.

A50016-D3104-M470-3-7620 229
MMN:SSNC Maintenance
TR01 Signaling

10 Missing reset signals and acknowledgments (part 1)

If there are no irregularities in the CIC data, it must be assumed that there is an
error in the signaling network. All participating partner exchanges must be in-
volved in processing the error. In theory, there can be any number of exchanges
for routed signals, but normally, not more than ten exchanges will be involved in
routing. Tracing routed signals (acknowledgments) is done from exchange to ex-
change. It is now important to control the routing administration of the signaling
from exchange A to exchange B.
At the same time, a start can be made in exchange B to initiate tracing acknowl-
edgments from exchange B to exchange A.
The same path is used outwards and inwards, but it can happen that a different
routing administration has been set from exchanges B-A and A-B.
The DPC of exchange B must be given at exchange A for determining the route
and similarly the DPC of A at exchange B.
b DISP SIGROUTE:DPC=..,Net name=..;
The state of the DPC is requested with the following command. The DPC of ex-
change B must be specified at exchange A and the DPC of A at exchange B.
b DISP SIGDP:DPC=..,Net name=..;
Is the DPC active? Y h ... 12
N h ... 11

11 Continue fault clearance

The DPC should be activated or, if the traffic relation is to be initiated, it should h ... 21
be blocked.

12 Continue fault clearance

The link set name of the active route must be used in the following command in
order to check the state of the link set.
b DISP SIGLSET:Link set name=..; h ... 13
13 Cause of error part 1 (connection A-A1, B-B1)
Is an active route available? Y h ... 15
N h ... 14

14 Continue fault clearance

The route must be created or activated according to OMN. h ... 21
15 Continue fault clearance
The DPC must be entered as active in the output masks at DISP SIGROUTE
and DISP SIGDP.
Are different DPC states entered at the inputs? Y h ... 29
N h ... 16

230 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling TR01

16 Continue fault clearance

All states are correctly entered and active.

Had the destination exchange B (A) been reached? Y h ... 28

N h ... 17

17 Continue fault clearance

The course of the signaling between the home and destination exchange is to
be checked (forwards and backwards) in this way. h ... 18

18 Missing reset signals and acknowledgments (part 2)

If there are no irregularities in the CIC data, it must be assumed that there is an
error in the signaling network. All participating partner exchanges must be in-
volved in processing the error. In theory, there can be any number of exchanges
for routed signals, but normally, not more than ten exchanges will be involved in
routing. Tracing routed signals (acknowledgments) is done from exchange to ex-
change. It is now important to control the routing administration of the signaling
from exchange A to exchange B.
At the same time, a start can be made in exchange B to initiate tracing acknowl-
edgments from exchange B to exchange A.
The same path is used outwards and inwards, but it can happen that a different
routing administration has been set from exchanges B-A and A-B.
The DPC of exchange B must be given at exchange A for determining the route
and similarly the DPC of A at exchange B.
The data must be determined in exchanges A1 (A2...) and B1 (B2...) with the fol-
lowing commands:
b DISP SIGROUTE:DPC=..,Net name=..;
Ascertain the next exchanges A2 (A3...), B2 (B3....) and notify the service staff.
The entered state of the DPC is requested with the following command. The
DPC of exchange B must be entered in exchange A1, (A2...) and similarly the
DPC for exchange A in exchange B1, (B2...).
b DISP SIGDP:DPC=..,Net name=..;
The link set name of the active route must be used in the following command.
b DISP SIGLSET:Link set name=..; h ... 19
19 Cause of error part 2 (A1...B, B1...A)
Is an active path available? Y h ... 22
N h ... 20

A50016-D3104-M470-3-7620 231
MMN:SSNC Maintenance
TR01 Signaling

20 Continue fault clearance

The DPC-A (B) is still in a routing area, or is not created or not activated. The h ... 21
route must be created or activated according to OMN, or taken out of the routing
area and created as a DPC in its own area.

21 Decision block

Modify the data defining the units in the database, using OMN. Consult the plan-
ning departments before doing so.

Depending on the action to be executed,

– Continue with OMN-TR... h ...OMN-TR
– Or continue with OMN-SS7 manual h ...OMN-SS7

22 Continue fault clearance

The DPC must be actively entered in the output masks DISP SIGROUTE and
DISP SIGDP.
Are different states entered in the outputs? Y h ... 29
N h ... 23

23 Continue fault clearance

All states are correctly entered and are active.

Had the exchange B (A) been reached? Y h ... 28

N h ... 24

24 Continue fault clearance

Is the number of exchanges that are needed to carry out signaling > 10? Y h ... 27
N h ... 25

25 Continue fault clearance

Are the signals running in circuit (Hints of circuit MSUs are overload messages
in the affected exchanges)? Y h ... 27
N h ... 26

26 Continue fault clearance

Continue in the exchanges A2... (B2...) h ... 18

27 Continue fault clearance

The C7 route administration is to be checked in the planning office. The first h ... END
remedy is to inhibit the RSET in the available exchange until the route adminis-
tration can be modified or corrected in the planning office.

232 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling TR01

28 Further remarks

The route administration is set so that the signals reach the B exchange and the
acknowledgments reach the A exchange. h ... 29

29 Information block

The fault cannot be cleared with the standard fault clearance measures. The
task must be undertaken by a system specialist. h ...NM:SSNC

END

A50016-D3104-M470-3-7620 233
MMN:SSNC Maintenance
TR01 Signaling

234 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling

3 TABIN

MSG:DISCARD Table of L3 and L4 Messages

REAS:DISCARD Reasons for Discarded MSUs
REAS:LINK Reasons for Signaling Link Messages
REC:SYNCHRON Recovery Synchronization
ALARM INFO SSNC Alarm and Messages
CLOCK Clock Distribution over MUT 9

A50016-D3104-M470-3-7620 235
MMN:SSNC Maintenance
MSG:DISCARD Signaling

3.1 Table of L3 and L4 Messages

MSG:DISCARD

Message I4=ISUP L4 Value or Value or Description as defined by CCITT

T4=TUP L4 H1/H0 H1/H0
L3=Level 3 in Hex in Dec
SC=SCCP

ACB T4 A/5 10/ 5 Access barred signal

ACC T4 1/A 1/10 Automatic congestion control info. message

ACM I4 06 006 Address complete message

ACM T4 1/4 1/ 4 Address complete message

ADI T4 4/5 4/ 5 Address incomplete message

AK SC 08 008 Data acknowledgment

ANC T4 1/6 1/ 6 Answer signal charge

ANM I4 09 009 Answer message

ANN T4 2/6 2/ 6 Answer signal no charge

ANU T4 0/6 0/ 6 Answer signal unqualified

BLA I4 15 021 Blocking acknowledgment signal

BLA T4 3/7 3/ 7 Blocking acknowledgment signal

BLO I4 13 019 Blocking signal

BLO T4 2/7 2/ 7 Blocking signal

CBA L3 6/1 6/ 1 Changeback acknowledgment signal

CBD L3 5/1 5/ 1 Changeback declaration signal

CBK T4 3/6 3/ 6 Clear back signal

CC SC 02 002 Connection confirm message

CCF T4 4/2 4/ 2 Continuity failure signal

CCL T4 7/6 7/ 6 Calling party clear signal

CCR I4 11 017 Continuity check request

CCR T4 6/7 6/ 7 Continuity check request signal

CFL T4 5/5 5/ 5 Call failure signal

CFM T4 1/9 1/ 9 CCBS facility message

CFN I4 2F 047 Confusion

CGBA I4 18 024 Circuit group blocking acknowledgment signal

CGC T4 2/5 2/ 5 Circuit group congestion signal

CGU I4 19 025 Circuit group unblocking

CGUA I4 1B 027 Circuit group unblocking acknowledge

CHG T4 2/4 2/ 4 Charging message

CLF T4 4/6 4/ 6 Clear forward signal

CMC I4 1D 029 Call modification completed

Tab. 3.1 Table of L3 and L4 messages

236 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling MSG:DISCARD

Message I4=ISUP L4 Value or Value or Description as defined by CCITT

T4=TUP L4 H1/H0 H1/H0
L3=Level 3 in Hex in Dec
SC=SCCP

CMR I4 1C 028 Call modification request

CMRJ I4 1E 030 Call modification reject

CNP L3 4/8 4/ 8 Connection not possible signal

CNS L3 3/8 3/ 8 Connection not successful signal

COA L3 2/1 2/ 1 Changeover acknowledgment

CON I4 07 007 Connect

COO L3 1/1 1/ 1 Changeover order signal

COT I4 05 005 Continuity signal

COT T4 3/2 3/ 2 Continuity signal

CPA T4 3/9 3/ 9 Calling party answer

CPG I4 2C 044 Call progress

CPM T4 2/9 2/ 9 Calling party free message

CQM I4 2A 042 Circuit group query

CQR I4 2B 043 Circuit group query response

CR SC 01 001 Connection request message

CREF SC 03 003 Connection refused message

CRG I4 31 049 Charge information

CRM T4 6/9 6/ 9 CLG selec. and validation response message

CSS L3 2/8 2/ 8 Connection successful signal

CSV T4 4/9 4/ 9 CLG selec. and validation check message

CVM T4 5/9 5/ 9 Closed user group validation check message

DLC L3 1/8 1/ 8 Signal data link connection order signal

DPN T4 B/5 11/ 5 Digital path not provided signal

DRS I4 27 039 Delayed release

DT1 SC 06 006 Dataform 1

DT2 SC 07 007 Dataform 2

EA SC 0C 012 Expedited data acknowledgment

EAM T4 F/6 15/ 6 Extended answer message indication information

ECA L3 2/2 2/ 2 Emergency changeover acknowledgment

ECO L3 1/2 1/ 2 Emergency changeover order

ED SC 0B 011 expedited data

ERR SC 0F 015 Protocol data unit error

EUM T4 F/5 15/ 5 Extended unsuccessful backward set up

FAA I4 20 032 Facility accepted

FAR I4 1F 031 Facility request message

FOT I4 08 008 Forward transfer signal

Tab. 3.1 Table of L3 and L4 messages

A50016-D3104-M470-3-7620 237
MMN:SSNC Maintenance
MSG:DISCARD Signaling

Message I4=ISUP L4 Value or Value or Description as defined by CCITT

T4=TUP L4 H1/H0 H1/H0
L3=Level 3 in Hex in Dec
SC=SCCP

FOT T4 6/6 6/ 6 Forward transfer signal

FRJ I4 21 033 Facility reject message

GRA I4 29 041 Circuit group reset acknowledgment message

GRA T4 A/8 10/ 8 Circuit group reset acknowledgment message

GRQ T4 1/3 1/ 3 General request message

GRS I4 17 023 Circuit group reset message

GRS T4 9/8 9/ 8 Circuit group reset message

GSM T4 1/2 1/ 2 General forward set-up information message

HBA T4 6/8 6/ 8 HW failure oriented group blo. ackn. message

HGB T4 5/8 5/ 8 HW failure oriented group blocking message

HGU T4 7/8 7/ 8 HW failure oriented group unblocking message

HUA T4 8/8 8/ 8 HW failure oriented group unblo. ackn. message

IAI T4 2/1 2/ 1 Initial address message with additional info.

IAM I4 01 001 Initial address

IAM T4 1/1 1/ 1 Initial address message

INF I4 04 004 Information message

INR I4 03 003 Information request

IT SC 10 016 Inactivity test

LFU L3 6/6 6/ 6 Link forced uninhibited signal

LIA L3 3/6 3/ 6 Link inhibit acknowledgment signal

LID L3 5/6 5/ 6 Link inhibit denied signal

LIN L3 1/6 1/ 6 Link inhibit signal

LLT L3 7/6 7/ 6 Link local inhibit test signal

LOS T4 8/5 8/ 5 Line-out-of-service signal

LPA I4 24 036 loop back acknowledgment

LRT L3 8/6 8/ 6 Link remote inhibit test signal

LUA L3 4/6 8/ 6 Link uninhibited acknowledgment signal

LUN L3 2/6 2/ 6 Link uninhibited signal

MBA T4 2/8 2/ 8 Maint. orient. group blocking ackn. message

MGB T4 1/8 1/ 8 Maint. orient. group blocking message

MGU T4 3/8 3/ 8 Maint. orient. group unblocking message

MPR T4 C/5 12/ 5 Misdealed trunk prefix signal (nat.)

MRVT SCCP-UDT MTP routing verification test

MRVA SCCP-UDT MTP routing verification acknowledge

MRVR SCCP-UDT MTP routing verification result

MUA T4 4/8 4/ 8 Maint. orient. group unblocking ackn. message

Tab. 3.1 Table of L3 and L4 messages

238 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling MSG:DISCARD

Message I4=ISUP L4 Value or Value or Description as defined by CCITT

T4=TUP L4 H1/H0 H1/H0
L3=Level 3 in Hex in Dec
SC=SCCP

NNC T4 3/5 3/ 5 National network congestion signal

OLM I4 30 048 Overload message

PAM I4 28 040 Pass along message

RAN T4 5/6 5/ 6 Reanswer signal

RCT L3 1/3 1/ 3 Rout set congestion test message

REL I4 0C 012 Release

RES I4 0E 015 Resume

RLC I4 10 016 Release complete

RLC SC 05 005 Release complete message

RLG T4 1/7 1/ 7 Release guard signal

RLSD SC 04 004 Released message

RSC I4 12 018 Reset circuit signal

RSC SC 0E 014 Reset confirm message

RSC T4 7/7 7/ 7 Reset-circuit signal

RSR SC 0D 013 Reset request message

RSR L3 2/5 2/ 5 Rout set test signal for restricted destination

RST L3 1/5 1/ 5 Rout set test signal for prohibit destination

SAM I4 02 002 Subsequent address message

SAM T4 3/1 3/ 1 Subsequent address message

SAO T4 4/1 4/ 1 Subsequent address message with one signal

SBA T4 C/8 12/ 8 SW generated group blocked acknowledgment message

SEC T4 1/5 1/ 5 Switching equipment congestion signal

SGB T4 B/8 11/ 8 SW generated group blocking message

SGU T4 D/8 13/ 8 SW generated group unblocking message

SLTA L3 2/1 2/ 1 Signaling link test acknowledgment message

SLTM L3 1/1 1/ 1 Signaling link test message

SSB T4 6/5 6/ 5 Subscriber busy signal

SST T4 9/5 9/ 5 Sent special information tone signal

SUA T4 E/8 14/ 8 SW generated group unblocked acknowledgment message

SUS I4 0D 013 Suspend

TFA L3 5/4 5/ 4 Transfer allowed signal

TFC L3 2/3 2/ 3 Transfer controlled message

TFP L3 1/4 1/ 4 Transfer prohibited signal

TFR L3 3/4 3/ 4 Transfer restricted signal

TRA L3 1/7 1/ 7 Transfer restart allowed signal

UBA I4 16 022 Unblocking acknowledgment

Tab. 3.1 Table of L3 and L4 messages

A50016-D3104-M470-3-7620 239
MMN:SSNC Maintenance
MSG:DISCARD Signaling

Message I4=ISUP L4 Value or Value or Description as defined by CCITT

T4=TUP L4 H1/H0 H1/H0
L3=Level 3 in Hex in Dec
SC=SCCP

UBA T4 5/7 5/ 7 Unblocking acknowledgment signal

UBL I4 14 020 Unblocking signal

UBL T4 4/7 4/ 7 Unblocking signal

UCIC I4 2E 046 Unequipped CIC

UDT SC 09 009 Unit data message

UDTS SC 0A 010 Unit data service message

UNN T4 7/5 7/ 5 Unallocated number signal

UPU L3 1/A 1/10 User part unavailable

USR I4 2D 045 User to user information

XUDT SC 11 017 Extended unit data message

XUDTS SC 12 018 Extended unit data service message

Tab. 3.1 Table of L3 and L4 messages

240 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling REAS:DISCARD

3.2 Reasons for Discarded MSUs

REAS:DISCARD

Code Reason Long form Meaning

0 DPC-INVA DPC INVALID DPC invalid

1 OPC-INVA OPC INVALID OPC invalid

2 OPCNOSTP OPC IS NO STP OPC is not an STP

3 SPC-INVA SPC INVALID SPC invalid

4 H1H0INVA H1H0 INVALID H1H0 invalid

5 SLC-INVA SLC INVALID SLC invalid

6 NI-INVA NETWORK INDICATOR INVALID NI invalid

7 SIO-INVA SIO INVALID SIO invalid

8 MTYPINVA MESSAGE TYPE INVALID Message type invalid

9 CIC-INVA CIC INVALID CIC invalid

10 PIPO-MSU PING PONG MSU Ping-pong message

11 CIRCROUT CIRCULAR ROUTING Circular routing

12 PLFMINVA INVALID PLATFORM Platform invalid

13 no entry DEFAULT Default

14 ILGL-CMB ILLEGAL COMBINATION Illegal combination in screening table

Tab. 3.2 Reasons for discarded MSUs

A50016-D3104-M470-3-7620 241
MMN:SSNC Maintenance
REAS:LINK Signaling

3.3 Reasons for Signaling Link Messages

REAS:LINK

Q3 Reason Additional information Clearance

AFM total out of service Total AFM failure between two MPs of load type SLT or between an MP of load type LI02
SM and the AMP processor

Alignment not possible Alignment was not achieved (L1). This can only occur during commissioning. The LI02
creation data of the signaling link in this switch do not match those at the remote end,
or the routing is incorrect.

ATM cell loss Loss of ATM cells from the LIC / MP. L2 is no longer receiving ATM cells from the LI02
LIC. Fault in MP or LIC.

ATM part entry rejected The connecting manager was unable to switch an ATM path. Is usually corrected by LI02
an audit.

BSCT A single port in the own exchange is locked / blocked. LI02

Congestion last too long Excessive overload duration LI02

Consecutive SSCOP recoveries de- Successive SSCP recoveries were detected.
tection

Error rate high L2 has detected an excessive number of transmission errors. There is a fault in the LI02
local MPU(SLT) or in the remote MPU(SLT) or the signaling link is routed over an un-
stable PCM link.

Excessive delay of acknowledgment L3 acknowledgment timeout. The remote end is not responding due to protocol prob- LI02
lems.

Far end received error Remote end send error (no connection on link) COMAL

Flag stream lasts too long Too many flags are being sent in succession. LI02

HW fault detected MTCSM Failure of a signaling link as the result of a hardware fault has been detected. The LI02
associated hardware reason for failure has been lost, and can therefore not be out-
put, or a MOD SIGLINK command was only partially executed. The failed hardware
unit should be determined by displaying the L1 HW states, and the fault cleared.

IWP not exist Interworking point does not exist. No or an incorrect IW point was created with CR LI02
IWP .

IWP VC not exist Virtual channel to the interworking point does not exist. No IW point, or an incorrect LI02
one, was created with CR IWP , or no IWP VC or an incorrect one.
Is only used when testing.

Level 1 loop L1 loop test failure LI02

L1 not switched The internal L2 reported, the L1 is not switched LI02

L2 internal job not processed L2 internal job not processed LI02

L3 COO from remote L2 Changeover order received from remote end. Signaling was changed over to a re- LI02
dundant signaling link.

L3 test ack not received No L3 test acknowledgment received from remote end. No SLTA (Signal Link Test LI02
Acknowledge) signal was received in response to sending an SLTM (Signal Link Test
Message). The signaling link does not terminate in the correct exchange, or the ex-
change to which the SLTM was addressed is not responding (any more).

L3 test ack not same link L3 test acknowledgment was not received on the same signaling link. The signaling LI02
link number in the SLTA (Signal Link Test Acknowledge) is incorrect. The routing of
the signaling link is faulty in the own exchange, in the remote exchange or on the
transmission link.

Tab. 3.3 Reasons for signaling link failure messages

242 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling REAS:LINK

Q3 Reason Additional information Clearance

L3 test pattern not OK Error during testing of the signaling link; the test pattern was incorrectly acknowl- LI02
edged.

Lack of trunk resources The number of created trunks (IW trunks) is insufficient. LI02

LIC failure A fault was detected in the LIC LI02

LIC or LIC port not exist LIC or LIC port does not exist. The LIC port has not been created or has been created LI02
incorrectly.

Loss of signal LIC port to partner not connected. COMAL

No ack from L2 to SLMC No acknowledgment from L2 in the MP (SLT) to the SLMC in the MP (SM). There is LI02
a disturbance in MP(SM) (affecting all signaling links), or in MP(SLT) (affecting only
the signaling links served by this MP) or in the communication between the two pro-
cessors. Internal fault in MP(SLT) caused, e.g., by recovery or, very unlikely, by a
double fault in AMXE.

No ack from SLMC to L2 No acknowledgment from the SLMC in the MP of load type SM to L2 in the MP of LI02
load type SLT. There is a disturbance in the MP of load type SM or in the MP of load
type SLT or in the communication between two main processors.

No ack from SLT No acknowledgment from MP(SLT) LI02

No ack from SM No acknowledgment from MP(SM) LI02

No credit from peer For a high speed link the ’No Credit’ timer expired before the synchronized SSCOP LI02
entity could repeat the credit once by means of STAT PDU.

No response from peer For a high speed link the ’Keep Alive Function’ did not receive a STAT PDU as an- LI02
swer to a POLL PDU for a longer period than specified in the ’No Response Timer’

Oscillating link The signaling link is unable to adopt a stable condition. Undefined signal sequences LI02
have been received on this signaling link (e.g. after recovery at the remote end). Con-
sequently, the signaling link was deactivated after ’X’ ms. L2 sends SIOS to the re-
mote end, which responds likewise with SOIS. L2 then starts alignment (sending
SIO). When the remote end is ready to receive again (sending SIN, SLTM / SLTA,
FISU), then the signaling link is reactivated. If the remote end does not send SIN,
SLTM / SLTA, the own L2 sends SIOS to the remote end again. This alignment is
repeated continuously until it is possible to reactivate the signaling link.

Remote L2 send SIOS The remote end sends SIOS. The send direction to the remote end is faulty; as a re- LI02
sult, the remote end does not receive any data and attempts to re-align (sending
SIOS). The signaling link has failed or is blocked at the remote end.

Remote processor outage Failure of MP(SLT) at the partner remote end

Remote release Released by the partner remote end

SLT failure An internal MP of load type SLT has failed. LI02

SNC03
SNC13

SM failure An internal MP of load type SM has failed. LI02

SNC03
SNC13

Unknown internal failure Unidentified internal fault. There are no error symptoms available. No hardware fault LI02
has been reported, but nonetheless L2 is no longer working.

Unknown outward failure Unidentified external fault LI02

Unreasonable BSN L2 has detected too many BSN faults. In 3 consecutive BSNs, 2 BSNs were received LI02
which did not have the expected contents. This reaction can occur after a
changeover. However, L3 will automatically put this signaling link back into opera-
tion. Fault clearance must be carried out if L3 cannot automatically put this signaling
link into operation again.

Tab. 3.3 Reasons for signaling link failure messages

A50016-D3104-M470-3-7620 243
MMN:SSNC Maintenance
REAS:LINK Signaling

Q3 Reason Additional information Clearance

Unreasonable FIB L2 has detected too many FIB faults. In 3 consecutive FIBs, 2 FIBs were received LI02
which did not have the expected contents. This reaction can occur after a
changeover. However, L3 will automatically put this signaling link back into opera-
tion. Fault clearance must be carried out if L3 cannot automatically put this signaling
link into operation again.

Unreasonable SSCF PDU An unreasonable service-specific connection function protocol data unit was re- LI02
ceived on a high speed link
Unreasonable SSCOP PDU An unreasonable service-specific coordination protocol data unit was received on a LI02
high speed link

Unreasonable SU Unreasonable signaling unit. LI02

VP not exist Virtual path does not exist. The virtual path was not created or was created incorrect- LI02
ly

Tab. 3.3 Reasons for signaling link failure messages

244 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling REC:SYNCHRON

3.4 Recovery Synchronization

REC:SYNCHRON
A restart of process must be performed synchronized and monitored by startup. For this,
startup offers a central synchronization mechanism based on defined synchronization
points (SP). Every SP defines a particular platform state. In order to reach a SP, a series
of conditions have to be met. If all essential requirements are satisfied, specific actions
are started. Every process started by the OS performs startup of the SP it wants to be
started from. Until SP4, all of the system processes must have been started.

Synchronization Points Meaning

SP1 Scheduling started (OS initialization)

SP2 OS & Basic Maintenance available

SP3 Database available

SP4 Maintenance available

SP4/5 PCM open

SP5 Outside world known

SP6 Traffic allowed

SP7 System available, end of recovery

SP8 startup complete, postprocessing finished

Tab. 3.4 Table for Service Indicator Octet

A50016-D3104-M470-3-7620 245
MMN:SSNC Maintenance
REC:SYNCHRON Signaling

MP:SA

SP0
SP1 AMX/ASN
SP2 Ultimate
SP3
SP0
SP1
SP2
AMX
Dependants
SP3
SP0
SP1
SP2
MP:Dep’s
SP3
SP0
SP1
SP2
LIC’s
SP3
SP0
SP1
SP2
SP3

SP4 SP4 SP4 SP4 SP4

SP4.5 SP4.5 SP4.5 SP4.5 SP4.5
SP5 SP5 SP5 SP5 SP5
SP6 SP6 SP6 SP6 SP6
SP7 SP7 SP7 SP7 SP7
SP8 SP8 SP8 SP8 SP8

Fig. 3.1 System Recovery Synchronization

Recovery level Supervision time Error Escalation to

threshold

PROREC2 50s 10 PROREC3

PROREC3 50s 5 FULLREC

FULLREC 480s 3 FULLREC-BOP-etented(1) or LOADREC2-local(2)

FULLREC-BOP-extented 5 min 1 FULLREC-BOP-kernel or LOADREC2-system(3)

FULLREC-BOP-kernel 5min 1 LOADREC2-system(3)

LOADREC2-local 20 min 3 LOADREC2-BOP-extended

LOADREC2-BOP-extended 40 min 1 LOADREC2-BOP-kernel

LOADREC2-BOP-kernel 40 min 1 LOADREC2-system

LOADREC2-system 15 min 1 LOADREC3

Tab. 3.5 Recovery escalation table

1 in the MP:SA
2 in the dependant MPs (all MPs other than MP:SA)
3 without exception if a total outage is detected

246 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling ALARM INFO

3.5 SSNC Alarm and Messages

ALARM INFO

3.5.1 Administration MP

Object class: Managed Element MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Tab. 3.6 Alarm object: Administration, Object class: Managed Element

Object class: Managed Element R1 MMN:SSNC

Procedure

Alarm type Probable cause Specific problem

Tab. 3.7 Alarm object: Administration, Object class: Managed Element R1

3.5.2 Alarm object Alarm Interface

Object class: Input Interface MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Envir. alarm Air compressor failure HW19

Envir. alarm Air conditioning failure HW19

Envir. alarm Air dryer failure HW19

Envir. alarm Battery discharging HW19

Envir. alarm Battery failure HW19

Envir. alarm Commercial power failure HW19

Envir. alarm Cooling fan failure HW19

Envir. alarm Enclosure door open HW19

Envir. alarm Engine failure HW19

Envir. alarm Excessive vibration HW19

Envir. alarm Explosive gas HW19

Envir. alarm Fire detected HW19

Envir. alarm Fire detector failure HW19

Envir. alarm Flood detected HW19

Envir. alarm Fuse failure HW19

Tab. 3.8 Alarm object Alarm Interface, Object class: Alarm Input Interface

A50016-D3104-M470-3-7620 247
MMN:SSNC Maintenance
ALARM INFO Signaling

Object class: Input Interface MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Envir. alarm Generator failure HW19

Envir. alarm Heating, ventilation or cooling system problem HW19

Envir. alarm High humidity HW19

Envir. alarm High temperature HW19

Envir. alarm High wind HW19

Envir. alarm Humidity unacceptable HW19

Envir. alarm Ice build up HW19

Envir. alarm Indeterminate HW19

Envir. alarm Intrusion detection HW19

Envir. alarm Leak detected HW19

Envir. alarm Low battery threshold HW19

Envir. alarm Low cable pressure HW19

Envir. alarm Low fuel HW19

Envir. alarm Low humidity HW19

Envir. alarm Low temperature HW19

Envir. alarm Low water HW19

Envir. alarm Material supply exhausted HW19

Envir. alarm Power problem HW19

Envir. alarm Pressure unacceptable HW19

Envir. alarm Pump failure HW19

Envir. alarm Rectifier failure HW19

Envir. alarm Rectifier high voltage HW19

Envir. alarm Rectifier low F Voltage HW19

Envir. alarm Smoke detected HW19

Envir. alarm Temperature unacceptable HW19

Envir. alarm Toxic gas HW19

Envir. alarm Toxic leak detected HW19

Envir. alarm Ventilations system failure HW19

Tab. 3.8 Alarm object Alarm Interface, Object class: Alarm Input Interface

3.5.3 Alarm object ALI

Object class: ALI MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Equip. alarm Equipment malfunction MTC Connection Disturbed HW02

Equip. alarm Processor problem Board Not Available HW01

Tab. 3.9 Alarm object AL, Object class: ALI

248 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling ALARM INFO

Object class: ALI MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Equip. alarm Processor problem Central Outage HW01

Equip. alarm Processor problem Central Unit Fault HW01

Equip. alarm Processor problem Sporadic Faults Overflow HW17

Equip. alarm Processor problem Unit Activation Failed HW01

PE alarm Software error SW Error During Start Up SW99

Tab. 3.9 Alarm object AL, Object class: ALI

Object class: RCI MP MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm Loss of signal RCI outage HW41

Tab. 3.10 Alarm object ALI, Object class: RCI MP

3.5.4 Alarm object ASN

Object class: ACCG MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Envir. alarm External interface device problem Fan Tray Alarm HW21

Envir. alarm External interface device problem Fan Box Alarm HW22

Envir. alarm External interface device problem Fuse Alarm HW20

Envir. alarm External interface device problem High Temperature EY03

Equip. alarm Equipment malfunction Central Unit Fault HW01

Equip. alarm Equipment malfunction CLK Interface Disturbed HW01

Equip. alarm Equipment malfunction CLK Interface Disturbed HW02

Equip. alarm Equipment malfunction Cross Link Failure HW02

Equip. alarm Equipment malfunction Execution error HW01

Equip. alarm Equipment malfunction FEPROM Failure HW01

Equip. alarm Equipment malfunction Flash Checksum Error HW01

Equip. alarm Equipment malfunction MTC Connection Disturbed HW01

Equip. alarm Equipment malfunction Non severe HW Fault HW01

Equip. alarm Equipment malfunction Outage Line Failure HW02

Equip. alarm Equipment malfunction Sporadic Faults Overflow HW17

Equip. alarm Processor problem Central Unit Fault HW01

Equip. alarm Processor problem Cross Link Failure HW02

Equip. alarm Processor problem Execution error HW01

Equip. alarm Processor problem Flash Checksum Error HW01

Tab. 3.11 Alarm object ASN, Object class: ACCG

A50016-D3104-M470-3-7620 249
MMN:SSNC Maintenance
ALARM INFO Signaling

Object class: ACCG MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Equip. alarm Processor problem Hardware Equipment Mismatch HW01

Equip. alarm Processor problem Hardware Equipment Mismatch HW30

Equip. alarm Processor problem Hardware Reset Logic HW01

Equip. alarm Processor problem MTC Connection Disturbed HW01

Equip. alarm Processor problem Reset Logic HW01

Equip. alarm Processor problem Software Start Unsuccessful HW01

Equip. alarm Processor problem Sporadic Faults Overflow HW01

Equip. alarm Processor problem Sporadic Faults Overflow HW17

Equip. alarm Processor problem Unit Activation Failed HW01

Equip. alarm Processor problem Unit Under Repair But Not Fault Free HW01

PE alarm Software error Software Error SW99

PE alarm Software error Software Start Unsuccessful SW99

PE alarm Software error SW Error During Start Up SW99

PE alarm Equipment malfunction Software Error SW99

Tab. 3.11 Alarm object ASN, Object class: ACCG

Object class: AMX MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Equip. alarm Equipment malfunction ATM Interface Disturbed HW02

Equip. alarm Equipment malfunction Sporadic Faults Overflow HW01

Equip. alarm Equipment malfunction Switching Element Failure HW01

Equip. alarm Equipment malfunction Wrong Cabling HW98

Equip. alarm Processor problem ATM Interface Disturbed HW02

Equip. alarm Processor problem Board Not Available HW01

Equip. alarm Processor problem Hardware Equipment Mismatch HW01

Tab. 3.12 Alarm object ASN, Object class: AMX

Object class: ASN MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Equip. alarm Equipment malfunction ATM Interface Disturbed HW02

Equip. alarm Equipment malfunction ATM Interface Disturbed HW32

Equip. alarm Equipment malfunction ATM Interface Disturbed HW01

Equip. alarm Equipment malfunction ATM Interface Disturbed HW35

Equip. alarm Equipment malfunction ATM Interface Disturbed HW31

Equip. alarm Equipment malfunction Switching Element Failure HW01

Tab. 3.13 Alarm object ASN, Object class: ASN

250 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling ALARM INFO

Object class: ASN MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Equip. alarm Equipment malfunction Switching Element Failure HW31

Equip. alarm Equipment malfunction Wrong Cabling HW98

Equip. alarm Processor problem Board Not Available HW01

Equip. alarm Processor problem Board Not Available HW31

Equip. alarm Processor problem Central Unit Fault HW01

Equip. alarm Processor problem Central Unit Fault HW31

Equip. alarm Processor problem Hardware Equipment Mismatch HW01

Equip. alarm Processor problem Hardware Equipment Mismatch HW31

Equip. alarm Processor problem Switching Element Failure HW01

Equip. alarm Processor problem Switching Element Failure HW31

PE alarm Equipment malfunction Software Error SW99

Tab. 3.13 Alarm object ASN, Object class: ASN

3.5.5 Alarm object ATMB

Object class: ATMBU MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Equip. alarm Equipment malfunction ATM Interface Disturbed HW50

Equip. alarm Equipment malfunction ATM Interface Disturbed HW52

Equip. alarm Processor problem Negative response from ITPML during HW51

Equip. alarm Processor problem Negative response from ITPAL HW51

Equip. alarm Processor problem Negative response from ITPML HW51

Equip. alarm Processor problem Negative response from ITPML HW51

Equip. alarm Processor problem Negative response from ITPML HW51

Equip. alarm Processor problem Negative response from ITPML HW51

Equip. alarm Processor problem Pmpost to AMP not successful HW51

Equip. alarm Processor problem Timeout of ITPAL HW51

Equip. alarm Processor problem Timeout of ITPJL HW51

Equip. alarm Processor problem Timeout of ITPML HW51

Equip. alarm Processor problem Timeout of ITPML HW51

Equip. alarm Processor problem Timeout of ITPML HW51

Equip. alarm Processor problem Timeout of ITPML HW51

Equip. alarm Processor problem ATMTR checker error HW51

Equip. alarm Processor problem ATMTR failure during loop test HW51

Equip. alarm Processor problem ATMTR list full HW51

Equip. alarm Processor problem ATMTR memory violation error HW51

Tab. 3.14 Alarm object ATMB, Object class: ATMBU

A50016-D3104-M470-3-7620 251
MMN:SSNC Maintenance
ALARM INFO Signaling

Object class: ATMBU MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Equip. alarm Processor problem ATMTR no response HW51

Equip. alarm Processor problem ATMTR restart error HW51

Equip. alarm Processor problem ATMTR start failure HW51

Equip. alarm Processor problem ATMTR state failure HW51

Equip. alarm Processor problem ATMTR undefined failure HW51

Equip. alarm Processor problem ATMTR zero pointer HW51

Equip. alarm Processor problem DMA failure HW51

Equip. alarm Processor problem DMA memory violation error HW51

Equip. alarm Processor problem DMA undefined failure HW51

Equip. alarm Processor problem ITP negative response HW53

Equip. alarm Processor problem ITP timeout HW53

Equip. alarm Processor problem MTC Connection Disturbed HW51

Equip. alarm Processor problem Undefined failure HW51

PE alarm Software error Software Error SW99

PE alarm Software error SW Error During Start Up SW99

Tab. 3.14 Alarm object ATMB, Object class: ATMBU

3.5.6 Alarm object ATM Layer

Object class: Interworking point VC MMN:SSNC

Procedure

Alarm type Probable cause Specific problem

Comm. alarm AIS ALARM INFO

AIS

Comm. alarm Communications subsystem failure Buffer overflow ALARM INFO

Receiver Buffer

Comm. alarm Communications subsystem failure Buffer underflow ALARM INFO

Receiver Buffer

Comm. alarm Far end receiver failure ALARM INFO

Far End

Tab. 3.15 Alarm object ATM Layer, Object class: Interworking point VC

Object class: TC adaptor MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm Loss of cell delineation ALARM INFO Tc

Adaptor

Tab. 3.16 Alarm object ATM Layer, Object class: TC adaptor

252 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling ALARM INFO

Object class: VC CTP MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm AIS ALARM INFO

AIS

Comm. alarm Far end receiver failure ALARM INFO

Far End

Tab. 3.17 Alarm object ATM Layer, Object class: VC CTP

3.5.7 Alarm object Security

Object: Security tracer MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

PE alarm File error Security trace file error SE02

PE alarm Storage capacity problem File threshold SE01

Tab. 3.18 Alarm object Security, Object: Security tracer

3.5.8 Alarm object LIC

Object class: LIC MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Equip. alarm Equipment malfunction ATM Interface Disturbed HW02

Equip. alarm Equipment malfunction ATM Interface Disturbed HW01

Equip. alarm Equipment malfunction Central Unit Fault HW01

Equip. alarm Equipment malfunction CLK Interface Disturbed HW02

Equip. alarm Equipment malfunction CLK Interface Disturbed HW01

Equip. alarm Equipment malfunction Cross Link Failure HW02

Equip. alarm Equipment malfunction Execution error HW01

Equip. alarm Equipment malfunction FEPROM Failure HW01

Equip. alarm Equipment malfunction Flash Checksum Error HW01

Equip. alarm Equipment malfunction Line Port Clock Problem HW01

Equip. alarm Equipment malfunction Line Port Clock Problem HW02

Equip. alarm Equipment malfunction Line Port DCC Failure HW01

Equip. alarm Equipment malfunction Line Port Failure HW01

Equip. alarm Equipment malfunction Line Port Failure HW02

Equip. alarm Equipment malfunction Line Port Laser Failure HW01

Equip. alarm Equipment malfunction Non severe HW Fault HW01

Equip. alarm Equipment malfunction Outage Line Failure HW02

Tab. 3.19 Alarm object LIC, Object class: LIC

A50016-D3104-M470-3-7620 253
MMN:SSNC Maintenance
ALARM INFO Signaling

Object class: LIC MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Equip. alarm Equipment malfunction Sporadic Faults Overflow HW17

Equip. alarm Processor problem ATM ASIC Failure HW01

Equip. alarm Processor problem ATM Interface Disturbed HW01

Equip. alarm Processor problem Central Unit Fault HW01

Equip. alarm Processor problem Central Unit Fault HW02

Equip. alarm Processor problem CLK Interface Disturbed HW01

Equip. alarm Processor problem Execution error HW01

Equip. alarm Processor problem Flash Checksum Error HW01

Equip. alarm Processor problem Hardware Equipment Mismatch HW01

Equip. alarm Processor problem Hardware Reset Logic HW01

Equip. alarm Processor problem Line Port DCC Failure HW01

Equip. alarm Processor problem Line Port Failure HW01

Equip. alarm Processor problem Line Port Laser Failure HW01

Equip. alarm Processor problem MTC Connection Disturbed HW01

Equip. alarm Processor problem RAM Failure HW01

Equip. alarm Processor problem Reset Logic HW01

Equip. alarm Processor problem Software Start Unsuccessful HW01

Equip. alarm Processor problem Sporadic Faults Overflow HW01

Equip. alarm Processor problem Sporadic Faults Overflow HW17

Equip. alarm Processor problem Unit Activation Failed HW01

Equip. alarm Processor problem Unit Under Repair But Not Fault Free HW01

PE alarm Software error Software Error SW99

PE alarm Software error Software Start Unsuccessful SW99

PE alarm Software error SW Error During Start Up SW99

PE alarm Equipment malfunction Software Error SW99

Tab. 3.19 Alarm object LIC, Object class: LIC

3.5.9 Alarm object LIC Port

Object class: DS1 line TTP MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm Loss of signal LI02

Tab. 3.20 Alarm object LIC Port, Object class: DS1 line TTP

254 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling ALARM INFO

Object class: Continuity monitor MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm Communications subsystem failure ALARM INFO

Subsystem

Tab. 3.21 Alarm object LIC Port, Object class: Continuity monitor

Object class: DS1 path TTP MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm AIS ALARM INFO

AIS

Comm. alarm AIS AIS egress ALARM INFO

AIS

Comm. alarm AIS AIS ingress ALARM INFO

AIS

Comm. alarm Loss of frame ALARM INFO

Loss of Frame

Comm. alarm Loss of frame Loss of frame egress ALARM INFO

Loss of Frame

Comm. alarm Loss of frame Loss of frame ingress ALARM INFO

Loss of Frame

Comm. alarm Remote alarm interface ALARM INFO

Remote Alarm

Comm. alarm Remote alarm interface RAI egress ALARM INFO

Remote Alarm

Comm. alarm Remote alarm interface RAI ingress ALARM INFO

Remote Alarm

Tab. 3.22 Alarm object LIC Port, Object class: DS1 path TTP

Object class: DS3 path TTPI MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm AIS ALARM INFO

AIS

Comm. alarm AIS ALARM INFO

AIS

Comm. alarm Communications subsystem failure ALARM INFO

Subsystem

Comm. alarm Communications subsystem failure ALARM INFO

Subsystem

Comm. alarm Communications subsystem failure Idle signal detection ALARM INFO
Subsystem

Comm. alarm Communications subsystem failure Application ID channel mis- ALARM INFO
match Subsystem

Tab. 3.23 Alarm object LIC Port, Object class: DS3 path TTPI

A50016-D3104-M470-3-7620 255
MMN:SSNC Maintenance
ALARM INFO Signaling

Object class: DS3 path TTPI MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm Communications subsystem failure Idle signal detection ALARM INFO
Subsystem

Comm. alarm Loss of frame ALARM INFO

Loss of Frame

Comm. alarm Loss of frame ALARM INFO

Loss of Frame
Comm. alarm Remote alarm interface ALARM INFO
Remote Alarm

Comm. alarm Remote alarm interface ALARM INFO

Remote Alarm

Comm. alarm Remote alarm interface Far end equipm. failure ALARM INFO
Remote Alarm

Comm. alarm Remote alarm interface Far end AIS ALARM INFO
Remote Alarm
Comm. alarm Remote alarm interface Far end equipm. failure ALARM INFO
Remote Alarm

Comm. alarm Remote alarm interface Far end loss of frame ALARM INFO
Remote Alarm

Comm. alarm Remote alarm interface Far end loss of signal ALARM INFO
Remote Alarm

Tab. 3.23 Alarm object LIC Port, Object class: DS3 path TTPI

Object class: DS3 PLCP path TTP MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm Loss of frame ALARM INFO

Loss of Frame

Comm. alarm Remote alarm interface ALARM INFO

Remote Alarm

Tab. 3.24 Alarm object LIC Port, Object class: DS3 PLCP path TTP

Object class: E1 alarm TTP MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm AIS ALARM INFO

AIS

Comm. alarm Framing error ALARM INFO

Framing Error

Comm. alarm Framing error CRC4 interworking ALARM INFO

Framing Error

Comm. alarm Loss of frame ALARM INFO

Loss of Frame

Tab. 3.25 Alarm object LIC Port, Object class: E1 alarm TTP

256 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling ALARM INFO

Object class: E1 alarm TTP MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm Bit Error Rate exceeds threshold ALARM INFO

Bit Error

Comm. alarm Far end receiver failure ALARM INFO

Far End

Comm. alarm Loss of Multiframe ALARM INFO

Loss of Frame

Tab. 3.25 Alarm object LIC Port, Object class: E1 alarm TTP

Object class: E3 interworking TTP MMN:SSNC

Procedure

Alarm type Probable cause Specific problem

Comm. alarm AIS ALARM INFO

AIS

Comm. alarm Loss of frame ALARM INFO

Loss of Frame

Comm. alarm Far end receiver failure ALARM INFO

Far End

Comm. alarm SLM: Signal Label Mismatch ALARM INFO

SLM

Comm. alarm SLM: Signal Label Mismatch Unequipped ALARM INFO

SLM

Comm. alarm TIM: Path Trace Mismatch ALARM INFO

TIM

Tab. 3.26 Alarm object LIC Port, Object class: E3 interworking TTP

Object class: Electrical SPI TTP MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm Loss of signal LI02

Tab. 3.27 Alarm object LIC Port, Object class: Electrical SPI TTP

Object class: MS TTP MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm AIS ALARM INFO

AIS

Comm. alarm Degraded signal ALARM INFO

Bit Error

Comm. alarm Bit Error Rate exceeds threshold ALARM INFO

Bit Error

Tab. 3.28 Alarm object LIC Port, Object class: MS TTP

A50016-D3104-M470-3-7620 257
MMN:SSNC Maintenance
ALARM INFO Signaling

Object class: MS TTP MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm Far end receiver failure ALARM INFO

Far End

Tab. 3.28 Alarm object LIC Port, Object class: MS TTP

Object class: DS3 line TTP MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm Loss of signal LI02

Tab. 3.29 Alarm object LIC Port, Object class: DS3 line TTP

Object class: Optical SPI TTP MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm Loss of signal LI02

Comm. alarm Transmitter failure

Tab. 3.30 Alarm object LIC Port, Object class: Optical SPI TTP

Object class: PPI TTP MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm Loss of signal LI02

Tab. 3.31 Alarm object LIC Port, Object class: PPI TTP

Object class: VC4 TTP MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm Bit Error Rate exceeds threshold ALARM INFO

Bit Error

Comm. alarm Bit Error Rate exceeds threshold ALARM INFO

Bit Error

Comm. alarm Far end receiver failure ALARM INFO

Far End

Comm. alarm SLM: Signal Label Mismatch ALARM INFO

SLM

Comm. alarm SLM: Signal Label Mismatch Unequipped ALARM INFO

SLM

Comm. alarm TIM: Path Trace Mismatch ALARM INFO

TIM

Tab. 3.32 Alarm object LIC Port, Object class: VC4 TTP

258 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling ALARM INFO

Object class: AU4 CTP MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm AIS ALARM INFO AIS

Comm. alarm Loss of pointer

Tab. 3.33 Alarm object LIC Port, Object class: AU4 CTP

Object class: VC44C TTP MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm Bit Error Rate exceeds threshold ALARM INFO

Bit Error

Comm. alarm Far end receiver failure ALARM INFO

Far End

Comm. alarm SLM: Signal Label Mismatch ALARM INFO

SLM

Comm. alarm SLM: Signal Label Mismatch Unequipped ALARM INFO

SLM

Comm. alarm TIM: Path Trace Mismatch ALARM INFO

TIM

Tab. 3.34 Alarm object LIC Port, Object class: VC44C TTP

Object class: RS TTP MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm Loss of frame ALARM INFO

Loss of Frame

Tab. 3.35 Alarm object LIC Port, Object class: RS TTP

3.5.10 Alarm object Maintenance MP

Object class: Generation MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

PE alarm File error Corrupted generation file on system disk GE01

Tab. 3.36 Alarm object Maintenance MP, Object class: Generation

A50016-D3104-M470-3-7620 259
MMN:SSNC Maintenance
ALARM INFO Signaling

3.5.11 Alarm object MP

Object class: Logical backup storage MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Equip. alarm Equipment malfunction

Equip. alarm Output device error EY06

Equip. alarm Output device error

Equip. alarm Output device error EY07

QOS alarm Performance degraded

QOS alarm Threshold crossed Storage threshold SE04

Tab. 3.37 Alarm object MP, Object class: Logical backup storage

Object class: MP MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

PE alarm Performance degraded Basic operation SW99

PE alarm Performance degraded Total Outage of Call processing SW02

PE alarm Performance degraded Total Outage of CCS7 SW01

PE alarm Performance degraded Total Outage of PNNI SW03

PE alarm Performance degraded Total OutageMobileSwitching SW04

PE alarm Software error Loadrec 2 SW99

PE alarm Software error Loadrec 3 SW99

PE alarm Software error Loadrec 3 generation change SW99

PE alarm Software error Loadrec 3 no generation change SW99

Tab. 3.38 Alarm object MP, Object class: MP

Object class: MPU MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Equip. alarm Equipment malfunction Central Unit Fault HW01

Equip. alarm Equipment malfunction Central Unit Fault HW02

Equip. alarm Equipment malfunction CLK Interface Disturbed HW02

Equip. alarm Equipment malfunction CLK Interface Disturbed HW01

Equip. alarm Equipment malfunction Disk Interface Failure on MPU HW02

Equip. alarm Equipment malfunction Ethernet Interface Failure HW07

Equip. alarm Equipment malfunction Execution error HW01

Equip. alarm Equipment malfunction LED Failure HW01

Equip. alarm Equipment malfunction Non severe HW Fault HW01

Tab. 3.39 Alarm object MP, Object class: MPU

260 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling ALARM INFO

Object class: MPU MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Equip. alarm Equipment malfunction RAM Failure HW01

Equip. alarm Equipment malfunction Sporadic Faults Overflow HW17

Equip. alarm Equipment malfunction V24 Interface Failure HW01

Equip. alarm Processor problem ATM ASIC Failure HW01

Equip. alarm Processor problem ATM Interface Disturbed HW01

Equip. alarm Processor problem ATM Interface Disturbed HW02

Equip. alarm Processor problem Board Not Available HW01

Equip. alarm Processor problem Central Outage HW01

Equip. alarm Processor problem Central Unit Fault HW01

Equip. alarm Processor problem CLK Interface Disturbed HW02

Equip. alarm Processor problem CLK Interface Disturbed HW01

Equip. alarm Processor problem Cross Link Failure HW01

Equip. alarm Processor problem Execution error HW01

Equip. alarm Processor problem Failed to bring MP into Microsynchronism HW01

Equip. alarm Processor problem FEPROM Failure HW01

Equip. alarm Processor problem HardwareEquipment Mismatch HW01

Equip. alarm Processor problem MTC Connection Disturbed HW01

Equip. alarm Processor problem Non severe HW Fault HW01

Equip. alarm Processor problem RAM Failure HW01

Equip. alarm Processor problem Reset Logic HW01

Equip. alarm Processor problem Software Start Unsuccessful HW01

Equip. alarm Processor problem Sporadic Faults Overflow HW17

Equip. alarm Processor problem Unit Activation Failed HW01

Equip. alarm Processor problem Unit Under Repair But Not Fault Free HW01

PE alarm Software error Software Error SW99

PE alarm Software error SW Error During Start Up SW99

PE alarm Software error Synchronized Start Up Failed SW99

PE alarm Equipment malfunction Active Unit With Fault HW10

PE alarm Equipment malfunction Active Unit With Fault HW11

Tab. 3.39 Alarm object MP, Object class: MPU

Object class: PBS MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Equip. alarm Processor problem Disk Format Wrong HW03

Equip. alarm Processor problem Disk HW Failure HW03

Equip. alarm Processor problem Disk HW Failure HW05

Tab. 3.40 Alarm object MP, Object class: Disk device

A50016-D3104-M470-3-7620 261
MMN:SSNC Maintenance
ALARM INFO Signaling

Object class: PBS MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Equip. alarm Processor problem Disk Interface Failure on MPU HW06

Equip. alarm Processor problem Disk Medium Failure HW03

Equip. alarm Processor problem Execution error HW03

Equip. alarm Processor problem MO Cartridge Error HW03

Equip. alarm Processor problem Unit Activation Failed HW05

Equip. alarm Processor problem Unit Activation Failed HW03

Equip. alarm Processor problem Unit Under Repair But Not Fault Free HW03

PE alarm Software error Software Error SW99

PE alarm Software error SW Error During Start Up SW99

Tab. 3.40 Alarm object MP, Object class: Disk device

3.5.12 Alarm object Profibus

Object: Profibus Device MMN:

Alarm type Probable cause Specific problem

Envir. alarm Input device error MMN-PBD-CP470-0000

Envir. alarm Input device error MMN-PBD-CP170-0000

Tab. 3.41 Alarm object Profibus, Object class: Profibus Device

3.5.13 Alarm object SIGLINK MP

Object class: Signaling point MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm Communications subsystem failure SP01

Tab. 3.42 Alarm object SIGLINK MP, Object class: Signaling point

Object class: Signaling combined link set MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm Combined link set failure LI03

Tab. 3.43 Alarm object SIGLINK MP, Object class: Signaling combined link set

262 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling ALARM INFO

Object class: Signaling link set MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm Signaling link set failure LI01

Tab. 3.44 Alarm object SIGLINK MP, Object class: Signaling link set

Object class: Signaling link MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm Signaling link failure Abnormal FIBR or BSNR LI02

Comm. alarm Signaling link failure AFM totally out of service LI02

Comm. alarm Signaling link failure Alignment not possible LI02

Comm. alarm Signaling link failure ATM Cell loss LI02

Comm. alarm Signaling link failure ATM path entry rejected LI02
Comm. alarm Signaling link failure Blocked single channel transmission LI02

Comm. alarm Signaling link failure Consecutive sccop recovery detection LI02

Comm. alarm Signaling link failure DIU inward failure LI02

Comm. alarm Signaling link failure DIU outward failure LI02

Comm. alarm Signaling link failure Excessive delay of acknowledge LI02

Comm. alarm Signaling link failure Excessive duration of Congestion LI02

Comm. alarm Signaling link failure Excessive error rate LI02

Comm. alarm Signaling link failure Flag stream lasts too long LI02

Comm. alarm Signaling link failure HW fault detected MTC SM LI02

Comm. alarm Signaling link failure Inward EQN not available LI02

Comm. alarm Signaling link failure IWP not exist LI02

Comm. alarm Signaling link failure IWP VC not exist LI02

Comm. alarm Signaling link failure Lack of interworking trunk resources LI02

Comm. alarm Signaling link failure Lack of resources LI02

Comm. alarm Signaling link failure Level 1 loop LI02

Comm. alarm Signaling link failure Level 1 path not switched LI02

Comm. alarm Signaling link failure Level 2 internal job not processed LI02

Comm. alarm Signaling link failure Level 3 change over order from remote level2 LI02

Comm. alarm Signaling link failure Level 3 test acknowledgment not received LI02

Comm. alarm Signaling link failure Level 3 test acknowledgment not same link LI02

Comm. alarm Signaling link failure Level 3 test pattern not ok LI02

Comm. alarm Signaling link failure LIC failure LI02

Comm. alarm Signaling link failure LIC or LIC-port not exist LI02

Comm. alarm Signaling link failure No acknowledgment from CP LI02

Comm. alarm Signaling link failure No acknowledgment from level 2 to SLMC LI02

Tab. 3.45 Alarm object SIGLINK MP, Object class: Signaling link

A50016-D3104-M470-3-7620 263
MMN:SSNC Maintenance
ALARM INFO Signaling

Object class: Signaling link MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm Signaling link failure No acknowledgment from SLMC to level 2 LI02

Comm. alarm Signaling link failure No acknowledgment from SLT LI02

Comm. alarm Signaling link failure No acknowledgment from SM LI02

Comm. alarm Signaling link failure No Credit from peer LI02

Comm. alarm Signaling link failure No RESPONSE timer expiration LI02

Comm. alarm Signaling link failure Oscillating link LI02

Comm. alarm Signaling link failure Outward EQN not available LI02

Comm. alarm Signaling link failure PCM inward failure LI02

Comm. alarm Signaling link failure PCM outward failure LI02

Comm. alarm Signaling link failure Remote level 2 sends SIOS LI02

Comm. alarm Signaling link failure Remote release LI02

Comm. alarm Signaling link failure SLT failure LI02

Comm. alarm Signaling link failure SM unavailable for more than ten minutes LI02

Comm. alarm Signaling link failure SN failure LI02

Comm. alarm Signaling link failure STM NUC switch not successful LI02

Comm. alarm Signaling link failure TC adapt not exist LI02

Comm. alarm Signaling link failure Trunk semi establishment not successful LI02

Comm. alarm Signaling link failure Trunk trans establishment not successful LI02

Comm. alarm Signaling link failure Unknown internal failure LI02

Comm. alarm Signaling link failure Unknown outward failure LI02

Comm. alarm Signaling link failure Unreasonable SSCF PDU LI02

Comm. alarm Signaling link failure Unreasonable SSCOP PDU LI02

Comm. alarm Signaling link failure Unreasonable SU LI02

Comm. alarm Signaling link failure VP not exist LI02

Tab. 3.45 Alarm object SIGLINK MP, Object class: Signaling link

Object class: Signaling Route Set NE Part MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm Route set unavailable RO01

Tab. 3.46 Alarm object SIGLINK MP, Object class: Signaling Route set NE Part

Object class: SCTP association MMN:SSNC

Procedure
Alarm type Probable cause Specific problem

Comm. alarm SCTP association failure LI06

Tab. 3.47 Alarm object SIGLINK MP, Object class: SCTP association

264 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling ALARM INFO

3.6 Additional Information

3.6.1 AIS

The communication alarm AIS exists on different levels: the (path-)AIS is assigned to
e1attp or ds1pathttp and it is an "in-band" signal used by the sending (i.e. upstream) part
to report that it has detected a PHYL fault due to which it can no longer guarantee the
quality of the signal it must send downstream.
Action: Because this indicates a fault in the upstream equipment, check the alarms at
the remote end.
On ATML level an AIS exists for two levels, i.e virtual path and channel endpoints, and
serves a similar purpose on the ATML as the path-AIS does for the PHYL. The differen-
tiation between egress and ingress does not apply to E1 and DS1 interfaces (but to
DS3ch which is currently not supported in SSNC).

3.6.2 Loss of Frame

The communication alarm Loss of Frame (LOF) assigned to e1attp or ds1pathttp signals
that the TDM (Time Division Multiplex) structure is distorted, i.e. synchronization of the
basic framing is lost due to some bad transmission quality, or a configuration mismatch
or a fault at the Tx side of the framer on the sending side, or a fault at the Rx side of the
own framer (on the receiver side).
Action: Check the PHY settings (e.g. FrameFormat, LineCode,...) on both ends.

3.6.3 Framing Error

The communication alarm Framing error with the specific problem “CRC4 interworking”,
assigned to e1attp, signals that there is a problem with the FrameFormat adjustment be-
tween both sides. It is only relevant when FrameFormat = CRC4. It occurs when the own
framer is adjusted with FrameFormat = CRC4 and the remote end does not support this
format, so that the own framer can't synchronize on the CRC-4 frame structure. This has
the consequence that RDI (Remote Defect Indication) is also sent to the remote end.
Action: The operating person must configure the same FrameFormat at both ends. This
communication alarm Framing error could also occur due to a CRC4 alignment fault, i.e.
when both sides support CRC-4, and synchronization had been achieved after start-up,
afterwards a loss of CRC4 multiframe occurred for some reason.
Check (e.g. by applying loopbacks) the correct operation of the CRC-4 Tx side of the
framer on the sending side, and the CRC-4 Rx side of the own framer (on the receiver
side).

3.6.4 Remote Alarm

The communication alarm Remote alarm indication (instead of 'interface' in the table)
(RAI) assigned to ds1path is sent by the remote end back to the sender to inform the
sender that its transmitted signal has an unacceptable quality, i.e. it is an "in-band" way
of informing the originator of a fault condition of its sender equipment.

A50016-D3104-M470-3-7620 265
MMN:SSNC Maintenance
ALARM INFO Signaling

3.6.5 Far End

The communication alarm Far end receiver failure assigned to e1attp is not known for
E1 interfaces, instead a Remote Defect Indication (RDI) is defined which has a similar
purpose as RAI has for ds1path. The difference is that RDI responds to defects instead
of failures, i.e. faster.

3.6.6 Bit Error

The communication alarm “Bit Error Rate exceeds threshold” assigned to e1attp occurs
when the frame alignment pattern error ratio exceeds 1 in 10000. This is caused by a
bad transmission quality or a fault in the framer HW (Rx or Tx).
Action: Check this by means of loopbacks.

3.6.7 Receiver Buffer

The communication alarms assigned to interworking-point-vc are Receiver buffer over-

flow and Receiver buffer underflow. These are AAL1 (i.e. CBR, Constant Bit Rate) fail-
ures which are usually caused by a transmission rate mismatch between sender and
receiver. An overflow occurs when the sender (i.e. usually another LIC at the edge of
the node or an MP in the same node) sends ATM cells to an STM port of a LIC (e.g. an
E1 interface) with a rate which exceeds the fixed rate (nx64 kbit/s, with n = 1..24 for DS1
and 1..31 for E1) of the narrow band channel. An underflow occurs when the sender
sends ATM cells to an STM port with a rate which is lower than the fixed bandwidth of
nx64 kbit/s. Such a condition could occur due to:
– misrouted cells in the network (=> check for hanging connections, check for related
alarms)
– mismatch of clock frequency between sender and receiver (=> check clock distribu-
tion in the system)
– violation of negotiated bitrate (=> possibly policing was triggered on LIC at opposite
edge of the node, so that cells could have been discarded)
– connection parameter mismatch between sender and receiver, e.g. Parially Filling
Level (PFL)), bandwidth (number of time slots per channel)

3.6.8 TC Adaptor

The communication alarm assigned to tc-adaptor is Loss Of Cell Delineation (LCD). This
is relevant only for ports carrying ATM traffic. This alarm occurs when a sequence of
cells was received with a faulty HEC (Header Error Correction) field. It could be caused
by a poor transmission quality on the line or by a hardware error on the sender at the
remote end or the receiver itself.
Action: Check for other (i.e. higher level) PHYL intermittent defects or alarms on this port
and/or check performance parameters of ATML on this port (for the PHYL no SW is cur-
rently provided for this purpose). The fault can usually be located by making a line loop
back (must be done manually because this is currently not supported by SW.

266 A50016-D3104-M470-3-7620
Maintenance MMN:SSNC
Signaling ALARM INFO

3.6.9 Subsystem

Inform the partner

3.6.10 SLM

Check the adjusted value for signal label.

3.6.11 TIM

Check the value of ’Expected Trail Trace’ on both side and inform the partner of the re-
sult.

A50016-D3104-M470-3-7620 267
MMN:SSNC Maintenance
CLOCK Signaling

3.7 Clock Distribution over MUT 9

CLOCK

Only ACCG with external clock over CCG / .... for

120 Ohm cable - adjust the switch to 240 Ohm
75 Ohm cable - adjust the switch to 120 Ohm

Basic Rack
Clock 0 Clock 1

ACCG (ASN0) ACCG (ASN1)

Module ASN Module ASN
PLL PLL
Clock distribution Clock distribution

ACCG(MUT9, Side0) SCB Frame ACCG(MUT9, Side1)

Basic Rack
Clock distribution Only active if no clock from ACCG partner Clock distribution
PLL PLL
Module Module

If in MUT 5 is
a frame SCE Only active if no clock from ACCG MUT 9
PLL PLL
ACCG(MUT5) ACCG(MUT5)
Module Module

Only active if no clock from ACCG MUT 9

PLL ACCG(MUT3) ACCG(MUT3) PLL
Module Module

Clock distribution SSNC internal

120 Ohm cable - adjust the switch to 120 Ohm Extended Rack 1
75 Ohm cable - adjust the switch to 75 Ohm

Extended Rack n ACCG(MUT9, Side1)

ACCG(MUT9, Side0)
Rack internal clock distribution is system specific
and can be done over every ACCG pair in this rack
Clock distribution Only active if no clock from ACCG partner Clock distribution
PLL PLL
Module Module

Only active if no clock from ACCG MUT 9

PLL ACCG(MUT7) ACCG(MUT7) PLL
Module Module

Only active if no clock from ACCG MUT 9

PLL PLL
ACCG(MUT5) ACCG(MUT5)
Module Module

Only active if no clock from ACCG MUT 9

PLL ACCG(MUT3) PLL
ACCG(MUT3)
Module Module

Fig. 3.2 Clock distribution over MUT 9

268 A50016-D3104-M470-3-7620