Maintenance

SLD/T16-2.5

MMN

A30808-X3580-H504-1-7620
MMN Maintenance
SLD/T16-2.5

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 2000.

Issued by the Information and Communication Networks 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 A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

This document consists of a total of 174 pages. All pages are issue 1.

Contents
1 Notes on this Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.1 Documentation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2 Symbols Used in the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.2.1 Symbol for Warnings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.2.2 Symbols for Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.2.3 Symbols for Menu Displays and Text Inputs. . . . . . . . . . . . . . . . . . . . . . . . 12
1.3 Notes on Licensed Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.4 Form for Your Ideas, Proposals and Corrections . . . . . . . . . . . . . . . . . . . . 13

2 Protective Measures, Handling /

Schutzmaßnahmen, Handhabung . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.1 Protective Measures / Schutzmaßnahmen . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.1.1 Electrical Fuses / Elektrische Sicherungen. . . . . . . . . . . . . . . . . . . . . . . . . 15
2.1.2 Protection Against Excessive High Contact Voltages /
Schutz gegen zu hohe Berührungsspannungen. . . . . . . . . . . . . . . . . . . . . 15
2.1.3 Protection Against Excessive Overvoltage
on the 48 / 60-Volts Power Supply Input /
Schutz gegen Überspannungen
beim 48 / 60-Volt-Stromversorgungseingang . . . . . . . . . . . . . . . . . . . . . . . 16
2.1.4 Isolations and Isolation materials /
Isolierungen und Isoliermaterialien . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.1.5 Fire Protection / Brandschutz . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.1.6 Protection Against Extraneous Laser Light
and Protection of the Optical Modules Concerned /
Schutz gegen austretendes Laserlicht
und Schutz der betreffenden optischen Baugruppen . . . . . . . . . . . . . . . . . 16
2.1.7 Earthing or Grounding and Potential Balancing /
Erdung und Potenzialausgleich . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.2 Handling the Subrack /
Handhabung des Baugruppenträgers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.2.1 Front Door of the Device / Geräte-Vordertür. . . . . . . . . . . . . . . . . . . . . . . . 19
2.2.2 Equipment Cooling / Gerätekühlung . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.2.3 Weight Information / Gewichtsangaben . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.2.4 Components Subject to High Operating Temperatures /
Komponenten mit hoher Betriebstemperatur . . . . . . . . . . . . . . . . . . . . . . . 20
2.3 Handling Modules, FO Equipment and Batteries /
Handhabung von Baugruppen, LWL und Batterien . . . . . . . . . . . . . . . . . . 21
2.3.1 Handling Modules Containing Electrostatically-sensitive Components /
Handhabung von Baugruppen mit elektrostatisch gefährdeten Bauteilen . 21
2.3.2 Handling Optical Fiber Connectors and Cables /
Handhabung von LWL-Steckverbindungen und -Leitungen . . . . . . . . . . . . 22
2.3.3 Handling Batteries / Handhabung von Batterien. . . . . . . . . . . . . . . . . . . . . 23
2.4 Switching OFF and ON / Aus- und Einschalten . . . . . . . . . . . . . . . . . . . . . 24
2.4.1 Emergency Switching OFF / Notabschaltung “OFF”. . . . . . . . . . . . . . . . . . 24
2.4.2 Normal Switching OFF Procedure / Normales Abschalten “OFF” . . . . . . . 25
2.5 Switching ON / Einschalten “ON” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

1.Vorabzug:A30808-X3580-H504-1-7620 3
MMN Maintenance
SLD/T16-2.5

3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.1 General Information about Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.1.1 Requirements for Personnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.1.2 Test Equipment, Tools and Resources Required . . . . . . . . . . . . . . . . . . . . 27
3.2 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.3 Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.3.1 Sensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.3.2 External Test and Diagnostic Interfaces for Communication Traffic . . . . . . 29
3.3.3 Monitoring the Receive Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.3.3.1 Port Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.3.3.2 Connection Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.3.3.3 Termination Point Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.3.3.4 TTI Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.3.3.5 Unequipped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.3.4 Monitoring of Modules CS4, EBSL, LTU and PSUTP . . . . . . . . . . . . . . . . . 32
3.3.5 Monitoring of Optional Box CLA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.3.6 Monitoring of the NE Control Communication by LAN and TMN . . . . . . . . . 33
3.4 Alarm Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.4.1 Alarm Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.4.2 Alarm Types, Alarm Classes, Alarm Severities . . . . . . . . . . . . . . . . . . . . . . 35
3.4.3 Alarm Interrogation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.4.4 Alarm Displays on the Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.4.5 Bw7R Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.4.6 Customer-Specific Alarm Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.4.7 Sa-Bit Alarm in Case of an Optional Use of a CLA Box. . . . . . . . . . . . . . . . 41
3.5 Security Against Double Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.6 Operating Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.7 Module Equipping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.8 Card Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3.9 Log Records. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.9.1 Log Records for the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.9.2 Log Records for Individual Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.10 Performance Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.10.1 TCN List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.10.2 Performance Message Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.11 Protection Switching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.11.1 Line Protection Switching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.11.1.1 (1+1) Line Protection Switching for STM-16 Line Signals . . . . . . . . . . . . . . 52
3.11.1.2 (1:1) Line Protection Switching for STM-16 Line Signals. . . . . . . . . . . . . . . 53
3.11.1.3 (1+1) Line Protection Switching for Tributary Signals . . . . . . . . . . . . . . . . . 53
3.11.2 Bidirectional Self-Healing Ring Protection . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.11.2.1 2-Fiber Self-Healing Ring Protection (BSHR-2) . . . . . . . . . . . . . . . . . . . . . . 54
3.11.2.2 4-Fiber Self-Healing Ring Protection (BSHR-4) . . . . . . . . . . . . . . . . . . . . . . 54
3.11.3 Card Release Switching (CRS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3.11.4 Subnetwork Connection Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3.11.5 Card Protection Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3.12 Redundant Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

4 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

3.12.1 Supply Voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

3.12.2 LED Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.13 Clock Source Changeover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

4 Display of Alarms at the LCT Operator Interface . . . . . . . . . . . . . . . . . . . . 59

4.1 The Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.1.1 Main Menu Items of Relevance to Maintenance. . . . . . . . . . . . . . . . . . . . . 60
4.1.2 Areas of the Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.1.3 Main Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.2 Symbols at the Operator Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.2.1 Module Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.2.2 Functional Symbols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
4.2.3 Port Symbols. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4.3 Display of Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4.4 Effect of the Alarm Display at the Operating Terminal . . . . . . . . . . . . . . . . 72
4.4.1 Setting and Displaying Alarm Suppressions . . . . . . . . . . . . . . . . . . . . . . . . 74
4.4.1.1 Setting and Clearing Suppressions for Equipment Alarms . . . . . . . . . . . . . 75
4.4.1.2 Setting and Clearing Suppressions for Transmission Alarms . . . . . . . . . . . 75
4.4.1.3 Setting and Clearing Suppressions for Alarms of Module Functions . . . . . 75
4.4.1.4 Disabling and Enabling of SSF, AIS and RDI Alarm Reports . . . . . . . . . . . 75
4.4.1.5 Displaying Alarm Suppressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
4.5 Saving Alarm Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4.5.1 Alarm List and Alarm Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4.5.2 Event Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
4.5.3 Log Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

5 Maintenance Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
5.1 Preventive Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
5.1.1 Exchanging the Backup Battery in the SLD16/SLT16 . . . . . . . . . . . . . . . . 78
5.1.2 Preventive Maintenance on Optical Modules . . . . . . . . . . . . . . . . . . . . . . . 78
5.2 Corrective Maintenance (Fault Clearance) . . . . . . . . . . . . . . . . . . . . . . . . . 78
5.3 Quality Monitoring During Operation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

6 Procedure for Alarm Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

6.1 Alarm Evaluation at the TMN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
6.2 Alarm Evaluation on LCT/NCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
6.2.1 Procedures and Alarm Information in NE-UniGATE
When the Q-B3 Interface is Used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
6.2.2 Procedure in NE-UniGATE when the Q-F Interface is Used . . . . . . . . . . . 83
6.2.3 Alarm Evaluation with the Aid of the Network Element Application Software .
84
6.3 Generation of Bw7R Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
6.3.1 Default Settings for Bw7R Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
6.3.1.1 Transmission Alarms of the SLD/SLT and Associated (Local)
Bw7R Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
6.3.1.2 Equipment Alarms of the SLD/SLT and Associated (Local) Bw7R Alarms. 91
6.3.1.3 Module Function Alarms and Associated (Local) Bw7R Alarms . . . . . . . . . 92
6.3.2 Changing the Bw7R Alarm Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

1.Vorabzug:A30808-X3580-H504-1-7620 5
MMN Maintenance
SLD/T16-2.5

7 Fault Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
7.1 Alarm Messages at the Operating Terminal. . . . . . . . . . . . . . . . . . . . . . . . . 94
7.1.1 Collective Display of Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
7.1.2 Alarm List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
7.2 Fault Clearance Measures for Equipment Alarms . . . . . . . . . . . . . . . . . . . . 97
7.2.1 Equipment Alarms at the LCT: Fault Pinpointing and Clearance. . . . . . . . . 97
7.2.2 Serious Equipment Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
7.2.3 Transmission Alarms in Module View . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
7.3 Fault Clearance Measures for Transmission Alarms . . . . . . . . . . . . . . . . . 105
7.3.1 Fault Pinpointing for Transmission Alarms. . . . . . . . . . . . . . . . . . . . . . . . . 105
7.3.2 Evaluating Transmission Alarms at the LCT . . . . . . . . . . . . . . . . . . . . . . . 107
7.3.2.1 Interplay of SDH Maintenance Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
7.3.2.2 Fault Clearance Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
7.3.3 Transmission Alarms within an NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
7.3.4 Further Notes for Fault Pinpointing to Transmission Alarms . . . . . . . . . . . 138
7.3.4.1 Fault Patterns for Link Faults (Examples) . . . . . . . . . . . . . . . . . . . . . . . . . 139
7.3.4.2 Test Loops on Traffic Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
7.3.4.3 Measuring the Tributary Output Signals. . . . . . . . . . . . . . . . . . . . . . . . . . . 142
7.3.4.4 Test Loops on Equipment Control (LAN Access)
and Management Path (TMN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
7.4 Fault Clearance Measures for Alarms
of General NE Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
7.5 Faults Caused by External Add-On,
Devices and Something Else . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
7.6 Software Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
7.6.1 Software Errors in a Module with PCU. . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
7.6.2 Software Errors in Module SCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
7.7 Measures after Fault Clearance has been Performed . . . . . . . . . . . . . . . . 150
7.8 Special Fault Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

8 Module Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

8.1 Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
8.2 Replacing the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
8.2.1 Replacing a Module (with PCU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
8.2.2 Replacing Module SCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
8.2.3 Replacing Modules LTU, PSUTP, EBSL and TIF
and the Handset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
8.3 Making Settings on the Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
8.3.1 Hardware Settings on Clock Line Adapter Unit, CLA Box . . . . . . . . . . . . . 156
8.3.2 Hardware Settings on Module Telemetry Interface Unit, TIF . . . . . . . . . . . 157
8.3.3 Hardware Settings for the Optical Preamplifier Module, OP . . . . . . . . . . . 157
8.3.4 Hardware Settings on Module Optical Booster, OB . . . . . . . . . . . . . . . . . . 158
8.4 Measures after the Module has been Replaced . . . . . . . . . . . . . . . . . . . . 159

9 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

10 Supplements, Notes for Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

6 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Illustrations
Fig. 3.1 Subrack Alarm Panel / Phone Indication, SRAP-PI . . . . . . . . . . . . . . . 39
Fig. 3.2 Local Alarm Signaling for SRAP and External Signaling
Units via Module SCU (Shown with Power Supply Switched Off) . . . . . 40
Fig. 3.3 Slot Equipping Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Fig. 3.4 TCN List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Fig. 3.5 Performance Window, Using the MS Port of an OIS16/OIS16-2 Module as
an Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Fig. 3.6 Performance Window for MSP Protection Switching . . . . . . . . . . . . . . . 50
Fig. 3.7 (1+1)Line Protection Switching, Switched to Protection Line . . . . . . . . 52
Fig. 3.8 (1:1) Line Protection Switching, Switchover to Protection Line . . . . . . . 53
Fig. 3.9 2-fiber Self-Healing Ring Protection,
Interruption between Network Elements A and B (Example). . . . . . . . . 54
Fig. 3.10 4-Fiber Self-Healing Ring Protection,
Interruption to a Span (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Fig. 3.11 4-Fiber Self-Healing Ring Protection,
Interruption of the Ring (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Fig. 4.1 The Main Window with a View of the Alarm List (Example). . . . . . . . . . 59
Fig. 4.2 Settings using the Main Menu Items: <Options> <Settings> . . . . . . . . . 62
Fig. 4.3 Main Status Bar in the Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Fig. 4.4 Elements of the Module Symbol (Using the OIS16/OIS16-2 as an Example)
63
Fig. 4.5 Alarm Window (Example Showing Equipment Alarms) . . . . . . . . . . . . . 64
Fig. 4.6 Functional Symbols (Examples) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Fig. 4.7 Port Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Fig. 4.8 Disabling/Enabling SSF, AIS and RDI Alarm Reports Using the EIPS1
Module as an Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Fig. 7.1 View of All Individual Alarm Messages in the Alarm List (Example) . . . 96
Fig. 7.2 Module View, Displaying an Equipment Alarm not yet Acknowledged
(Example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Fig. 7.3 Module View: Calling Transmission Alarms (Example) . . . . . . . . . . . . 104
Fig. 7.4 Traffic View, Showing an Unacknowledged Transmission Alarm
(Example). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Fig. 7.5 Interplay of the SDH Maintenance Signals at the SL16. . . . . . . . . . . . 108
Fig. 7.6 Interruption in a Regeneration Section . . . . . . . . . . . . . . . . . . . . . . . . 139
Fig. 7.7 Interruption in a Multiplex Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Fig. 7.8 Interruption of the VC-4 Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Fig. 7.9 Interruption in 140-Mbit/s Signal Path . . . . . . . . . . . . . . . . . . . . . . . . . 141
Fig. 7.10 Module view, Display of Alarms (Example) . . . . . . . . . . . . . . . . . . . . . 143
Fig. 7.11 Detailed Alarm Information Window. . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Fig. 7.12 SCU Alarm Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Fig. 8.1 CLA Box Sa-Bit Selector Switch n=1 (A2), =2 (A4), =3 (A6) . . . . . . . . 156
Fig. 8.2 Optical Preamplifier Module: Position of the Jumper Plugs . . . . . . . . . 158
Fig. 8.3 Optical Booster Module: Position of the Jumper Plugs for the ICS Bus 158

1.Vorabzug:A30808-X3580-H504-1-7620 7
MMN Maintenance
SLD/T16-2.5

Tables
Tab. 3.1 Behavior of Module LEDs for Module SCU. . . . . . . . . . . . . . . . . . . . . . . 36
Tab. 3.2 Behavior of Module LEDs for all Modules with the Exception
of the SCU and LTU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Tab. 3.3 Bw7R Alarm Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Tab. 3.4 Alarm Displays of the SRAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Tab. 3.5 Possible Card States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Tab. 3.6 Performance-/TCN-Monitoring for the Individual Ports
(Example: Near End Performance). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Tab. 4.1 Display Field “A” for Alarm Suppressions . . . . . . . . . . . . . . . . . . . . . . . . 65
Tab. 4.2 Display Field “A” for Alarm Suppressions . . . . . . . . . . . . . . . . . . . . . . . . 67
Tab. 4.3 TCN Display Field “T” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Tab. 4.4 Indicator Field “A” for Alarm Suppressions . . . . . . . . . . . . . . . . . . . . . . . 69
Tab. 4.5 TCN Display Field “T” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Tab. 4.6 Alarm Display on the Operating Terminal, Overview . . . . . . . . . . . . . . . 70
Tab. 4.7 Meaning of the Alarm Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Tab. 4.8 Possible Effects of Alarm Displays at the Operating Terminal . . . . . . . . 72
Tab. 4.9 Functional Units where SSF, AIS and RDI Alarm Reports may be Activat-
ed/Deactivated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Tab. 6.1 Colors of the Icon Outline and Alarm Severities (Defaults). . . . . . . . . . . 82
Tab. 6.2 Bw7R Alarm Signaling for Transmission Alarms, Default Settings . . . . . 85
Tab. 6.3 Bw7R Alarm Signaling for Equipment Alarms,
Default Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Tab. 6.4 Bw7R Alarm Signaling for Alarms of general NE Functions
for Symbol “Subrack”, Default Settings. . . . . . . . . . . . . . . . . . . . . . . . . . 92
Tab. 7.1 Equipment Alarms and Module Fault Clearance . . . . . . . . . . . . . . . . . . 99
Tab. 7.2 Assignment of Modules LTU and EIPS1 in Subrack SLD16/SLT16 . . . 100
Tab. 7.3 Assignment of Modules LTU and EIPS1 in Subrack SLD16E/SLT16E 101
Tab. 7.4 Optical Preamplifier, Fault Clearance of Transmission Alarms. . . . . . . 109
Tab. 7.5 Optical Booster, Fault Clearance of Transmission Alarms . . . . . . . . . . 110
Tab. 7.6 STM-16 Alarms (OIS16/16-2), Fault Clearance . . . . . . . . . . . . . . . . . . 110
Tab. 7.7 STM-16 Alarms for (1+1) Line Protection Switching, Fault Clearance . 113
Tab. 7.8 STM-16 Alarms for (1:1) Line Protection Switching, Fault Clearance. . 113
Tab. 7.9 STM-16 Alarms for Ring Protection Switching 2F Without Extra Traffic,
Fault Clearance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Tab. 7.10 STM-16 Alarms for 2F Ring Protection with Extra Traffic,
Fault Clearance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Tab. 7.11 STM-16 Alarms for 4F-Ring Protection, Fault Clearance . . . . . . . . . . . 119
Tab. 7.12 AU4/VC4 Alarms (OIS16/16-2), Fault Clearance . . . . . . . . . . . . . . . . . 121
Tab. 7.13 STM-4 Alarms (OIS4/4-2), Fault Clearance . . . . . . . . . . . . . . . . . . . . . 124
Tab. 7.14 STM-4 Alarms for (1+1) Protection Switching on the Tributary Side,
Fault Clearance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Tab. 7.15 AU4/VC4 Alarms (OIS4/4-2), Fault Clearance . . . . . . . . . . . . . . . . . . . 127
Tab. 7.16 STM-1 Alarms (OIS1), Fault Clearance . . . . . . . . . . . . . . . . . . . . . . . . 129

8 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Tab. 7.17 STM-1 Alarms (OIS1) for (1+1) Protection on the Tributary Side,
Fault Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Tab. 7.18 AU4/VC4 Alarms (OIS1), Fault Clearance. . . . . . . . . . . . . . . . . . . . . . 131
Tab. 7.19 STM-1 Alarms (EIPS1), Fault Clearance . . . . . . . . . . . . . . . . . . . . . . . 133
Tab. 7.20 AU4/VC4 Alarms (EIPS1, SDH), Fault Clearance . . . . . . . . . . . . . . . . 134
Tab. 7.21 E4 Alarms (EIPS1, PDH), Fault Clearance . . . . . . . . . . . . . . . . . . . . . 136
Tab. 7.22 VC4 Alarms (EIPS1, PDH), Fault Clearance . . . . . . . . . . . . . . . . . . . . 136
Tab. 7.23 SEC Alarms (CLL), Fault Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Tab. 7.24 G.703 Alarms of OH Interface, Fault Clearance . . . . . . . . . . . . . . . . . 146
Tab. 7.25 TIF Alarms (OHA), Fault Clearance. . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Tab. 7.26 Subrack Alarms, Fault Clearance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Tab. 8.1 NE Behavior During Module Replacement . . . . . . . . . . . . . . . . . . . . . 151
Tab. 8.2 Channel 1 ... 3 Sa-Bit Configuration Switch (A2, A4, A6) Assignment 157
Tab. 8.3 64-kbit/s Channel Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Tab. 8.4 Jumper Setting on the Optical Preamplifier Module. . . . . . . . . . . . . . . 157

1.Vorabzug:A30808-X3580-H504-1-7620 9
MMN Maintenance
SLD/T16-2.5

10 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

1 Notes on this Documentation

1.1 Documentation Overview

The documentation of synchronous line equipment SLD16/SLT16, series 2,
release 5 (abbreviated to: SLD/T16-2.5) covers network elements SLD16, SLD16E,
SLT16 and SLT16E and comprises the following descriptions and manuals:

• Technical Description (TED)

The Technical Description TED gives an overview on the application, performance
features, interfaces and functions of the equipment. It also contains the most impor-
tant technical data and product code number.
The Technical Description contains no definite instructions for action.

• Installation and Test Manual (ITMN)

The Installation and Test Manual ITMN contains instructions to connect and install
the TransXpress Local Craft Terminal LCT and Network Craft Terminal NCT and in-
structions for installing synchronous line equipment (by using the LCT/NCT).
To work with the Installation and Test Manual ITMN, knowledge of the operating
manual OMN is required.
For specific tasks, additional documentation is required which has to be created sep-
arately; this is referred to in the ITMN.

• Operating Manual (OMN)

The OMN:SL operating part describes the operating elements of the synchronous
line equipment and operating and monitoring with the NCT and LCT operating ter-
minals (with explanation of the graphic user interface of the application software of
the network element).
For information about the gateway software UniGATE please refer to the dedicated doc-
i umentation.

• Maintenance Manual (MMN)

The Maintenance Manual MMN describes the procedure on the occurrence of
alarms and interference suppression of synchronous line equipment.
To work with the Maintenance Manual MMN, knowledge of the Installation and Test
Manual ITMN and the Operating Manual OMN is required.
Notes for the user of the documentation in paper form:
i This documentation can also be provided on CD-ROM.
Recommended system configuration:
In order to be able to read the PDF files properly, you need
Windows NT or
Windows 95/98 or
SUN Solaris V2.5 or later and
Acrobat Reader 4.0 with search function (integral part of the customer documentation
on CD-ROM)

A30808-X3580-H504-1-7620 11
MMN Maintenance
SLD/T16-2.5

1.2 Symbols Used in the Documentation

1.2.1 Symbol for Warnings

This symbol identifies notes which, if ignored, can result in personal injury or in perma-
! nent damage to the equipment.

1.2.2 Symbols for Notes

This symbol identified notes providing information which extends beyond the immediate
i context.

⇒ Notes on parts of the text which contain definite instructions for action.

☞ Cross reference to other chapters in this manual or cross reference to other

manuals.

Help Note on the on-line help system of the relevant software program.

1.2.3 Symbols for Menu Displays and Text Inputs

Menu options from pop-up menus or inputs to be made by the operator (texts, com-
mands) are displayed consecutively in their hierarchical sequence in pointed brackets:
<Menu> <Menu item> <Command text> <Parameter> etc.

1.3 Notes on Licensed Software

This documentation refers to software products which were taken over from other com-
panies as licenses.
Should problems arise, you should contact Siemens AG as the licensee and not the rel-
evant licenser.
In this documentation, the following designations of licensed products are mentioned:
• UNIX (registered trademark of UNIX System Laboratories Inc.)
• MS-Windows (identification of the Microsoft Corporation)

12 A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

1.4 Form for Your Ideas, Proposals and Corrections

We aim to provide clear, user-friendly documentation. To achieve this objective, your
practical experience is very important. We appreciate your suggestions.
To offer you, the user, a cost-effective opportunity to identify weak points or requests for
documentation, we have compiled a form for you on the next page. You can use it as a
master or as a printout in electronic documentation.

Please enter your ideas, proposals and corrections on the copy (enclose further
pages, if required).

The following points are of particular importance to us:

• Where are we offering too much or too little detail?
• Where should more explanatory graphics be used?
• Where is the description difficult to understand?
• How can the basic structure of the description or the manual be improved?

Please forward your feedback as a letter or fax to our address given overleaf.
If you want a reply or need to discuss anything with us, please complete the “Sender”
field in full.
Many thanks for your feedback!

A30808-X3580-H504-1-7620 13
MMN Maintenance
SLD/T16-2.5

To Sender

SIEMENS AKTIENGESELLSCHAFT Name:

Kundendokumentation ICN TR S C2
Hofmannstrasse 51 ..........................................................................
D-81359 München Address:

Fax +49 89 722 57315 ..........................................................................

..........................................................................
Department: Telephone/Fax:

................................... ....................................
Date: Signature:

................................... ....................................

I am using this documentation as I am responsible for the following areas

(...) Service document (...) Installation and testing
(...) Assembly/installation and test document (...) Operation
(...) General introduction (...) Maintenance
(...) Reference (...) Sales
(...) Textbook (...) Teaching
(...) _______________________________ (...) _______________________________

Page Remarks

14 A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

2 Protective Measures, Handling /

Schutzmaßnahmen, Handhabung
If the following rules are not observed,
! and if equipment damages or personnel
injuries are the result, the manufacturer
assumes no liability, and the warranty
will expire!
Bei Nichtbeachtung der nachfolgenden
Vorschriften und daraus resultierenden
Personen- oder Sachschäden wird kei-
ne Haftung seitens des Herstellers
übernommen, und die Gewährleistung
erlischt!

If you replace any parts of devices or ca-
bles, you must only use original spare
parts or parts which are explicitly licensed
by the manufacturer.
Falls Sie an den Geräten oder an der Ver-
kabelung irgendwelche Teile ersetzen,
dann dürfen Sie nur Original-Ersatzteile
oder solche Teile verwenden, die vom
Hersteller ausdrücklich zugelassen sind.

2.1 Protective Measures / Schutzmaßnahmen

2.1.1 Electrical Fuses / Elektrische Sicherungen

The power supply lines for each subrack
and for each external additional device (f.
e. an adapter box) within the rack are rout-
ed via separate circuit breakers which are
located in the fuse panel of the rack.
For each subrack or additional one circuit
breaker for the working power supply and
one circuit breaker for the protection pow-
er supply are used.
Die Stromversorgungsleitungen für jeden
Baugruppenträger und jedes externe Zu-
satzgerät (z.B. einen Adapterkasten) in-
nerhalb des Gestells sind über eigene
Sicherungsautomaten geführt. Diese be-
finden sich im Sicherungsfeld des Ge-
stells.
Pro Baugruppenträger oder Zusatz wird
für die Betriebs- und für die Ersatz-Strom-
versorgung je 1 Sicherungsautomat ver-
wendet.

2.1.2 Protection Against Excessive High Contact Voltages /

Schutz gegen zu hohe Berührungsspannungen

☞ When
handling the power supply or
working on it, observe the safety
measures described in the specifi-
cations VDE 0105 (Operation of
Heavy Current Systems) and DIN
EN 50110, part 1 (Operation of
electrical Systems).
☞
Beachten Sie bei der Handhabung
der Stromversorgung oder bei Ar-
beiten daran die Sicherheitsmaß-
nahmen der Normen VDE 0105
(Betrieb von Starkstromanlagen)
und DIN EN 50110, Teil1 (Betrieb
von elektrischen Anlagen).

1.Vorabzug:A30808-X3580-H504-1-7620 15
MMN Maintenance
SLD/T16-2.5

2.1.3 Protection Against Excessive Overvoltage

on the 48 / 60-Volts Power Supply Input /
Schutz gegen Überspannungen
beim 48 / 60-Volt-Stromversorgungseingang
A protection against excessive voltage is
built in on the 48 / 60-Volts power supply
input.
The equipment must only be used with
! SELV / TNV power supply units according
to VDE 0100-410 and DIN EN 60950!
Ein Schutz gegen Überspannung auf der
Stromversorgungs-Eingangseite 48 /
60 Volt ist eingebaut.
Das Gerät darf nur mit SELV / TNV-Strom-
versorgungen gemäß VDE 0100-410 und
DIN EN 60950 betrieben werden!

☞ Observe
before connecting other equipment ☞ weis insbesondere, bevor Sie an-
the above note especially Beachten Sie den obigen Warnhin-

to the user / customer interfaces! dere Geräte an die Anwender-/

Kunden-Schnittstellen anschlie-
ßen!

☞ You
protective grounding measures giv- ☞ Schutzerdungsmaßnahmen ent-
must observe without fail the Beachten Sie unbedingt die

en in Chapter 2.1.7! sprechend Kapitel 2.1.7!

2.1.4 Isolations and Isolation materials /

Isolierungen und Isoliermaterialien
The isolations and isolation materials Die verwendeten Isolierungen und die
used comply with DIN EN 60950. Isolationsmaterialien entsprechen DIN
EN 60950.

2.1.5 Fire Protection / Brandschutz

Fire protection complies with DIN EN Der Brandschutz entspricht DIN EN
60950. 60950.

2.1.6 Protection Against Extraneous Laser Light

and Protection of the Optical Modules Concerned /
Schutz gegen austretendes Laserlicht
und Schutz der betreffenden optischen Baugruppen
Depending on the device type, the laser Je nach Gerätetyp kann die Laserstrah-
! radiation may also be invisible for the lung für das menschliche Auge auch
human eye! unsichtbar sein!

Devices and modules displaying either of Geräte und Baugruppen, die eines der fol-
the following warning labels contain laser genden Warnzeichen tragen, enthalten
devices. Laser-Einrichtungen.

16 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance
SLD/T16-2.5
Warning Label
according to VDE 0105/DIN
EN 50110 / DIN 40008 T.1
and T.3, Reg. No. 2821, using
the laser symbol according to
7000-ISO-1329.
Warning Label
for hazard class 1 laser equip-
ment.
When operated in a closed system, the la-
ser equipment of the device conform to
class 1 safety level.
Nevertheless, in view of possible malfunc-
tions, transmission systems which are fit-
ted with optical fiber amplifier modules are
classified as hazard class 3A. This hazard
class is also applicable if the device is
opened.
The relevant amplifier modules are la-
belled as follows:
Class 3A Laser Product
Do not stare into beam or view
directly with optical instruments.
Operate in a closed optical loop only.
1.Vorabzug:A30808-X3580-H504-1-7620
MMN
Warnschild
nach VDE 0105 / DIN EN
50110 / DIN 40008 T.1 und
T.3, Reg. Nr. 2821 mit einem
Laser-Symbol nach 7000-
ISO-1329.
Warnschild
Class 1 Laser für Laser-Einrichtungen der
Gefährdungsklasse 1.
IEC 60825-1:98
Bei Betrieb im geschlossenen System
entsprechen die Laser-Einrichtungen des
Gerätes der Gefährdungsklasse 1.
Unter Berücksichtigung von vorhersehba-
ren Fehlerfällen sind mit optischen Licht-
wellenleiter-Verstärkerbaugruppen
bestückte Übertragungssysteme jedoch
der Gefährdungsklasse 3A zugeordnet.
Diese Gefährdungsklasse gilt auch bei
geöffnetem Gerät.
Die betreffenden Verstärkerbaugruppen
sind folgendermaßen beschildert:
Laser Klasse 3A Nicht in den Strahl blik-
ken, auch nicht mit optischen Instrumen-
ten. Sendebetrieb nur im geschlossenen
optischen System.
17
MMN
⇒ To ensure safe operation of the en-
tire optical path, the laser safety
shutdown must be activated and
the automatic cyclical laser start
must be disabled.
⇒ Commissioning should be per-
formed with fuse protection in the
closed system.
☞ Tomust ☞
avoid damage to health, you Zur Vermeidung gesundheitlicher
observe the regulations re- Schäden müssen Sie die Vorschrif-
garding protection against radiation ten zur Strahlungssicherheit von
from laser devices (DIN VDE 0837
/ DIN EN 60825 / IEC 825).
If it cannot be avoided − in an exceptional
! case − to apply the hazard class 3A regu-
lations (see above), you always must use
dedicated laser-protective goggles.
If an optical preamplifier is used, its input
! must never be directly connected to an
optical booster output − always intercon-
nect an optical attenuator.
If the automatic laser safety shutdown has
! been taken out of service with an optical
Booster output, the optical fiber connected
to it must not be disconnected − due to the
high optical output power.
In this case, the laser diodes are not
switched off automatically. The very high
optical power generated in this way is po-
tentially very harmful to the human eye.
In case of doubt always use dedicated la-
! ser-protective goggles!
18
Maintenance
SLD/T16-2.5
⇒ Für den sicheren Betrieb der ge-
samten optischen Strecke muss
die Lasersicherheitsabschaltung
aktiviert sein, und der automatische
zyklische Laserstart muss gesperrt
sein.
⇒ Die Inbetriebnahme soll abgesi-
chert im geschlossenen System er-
folgen.
Lasereinrichtungen (DIN VDE 0837
/ DIN EN 60825 / IEC 825) beach-
ten.
Falls die Gefährdungsklasse 3A im Aus-
nahmefall nicht vermieden werden kann
(siehe oben), müssen Sie stets eine Laser-
Schutzbrille tragen.
Bei Verwendung eines optischen Vorver-
stärkers darf dessen Eingang nie direkt
mit einem optischen Booster-Ausgang ver-
bunden werden − fügen Sie immer ein op-
tisches Dämpfungsglied ein.
Wenn bei einem optischen Booster-Aus-
gang die automatische Lasersicherheits-
abschaltung außer Betrieb genommen
wurde, darf − wegen der hohen optischen
Ausgangsleistung − der angeschlossene
Lichtwellenleiter nicht aufgetrennt werden.
In diesem Fall werden die Laserdioden
nicht automatisch abgeschaltet. Die dabei
entstehende sehr hohe optische Aus-
gangsleistung ist sehr gefährlich für das
menschliche Auge.
Tragen Sie im Zweifelsfall stets eine
Schutzbrille!
1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance
SLD/T16-2.5
2.1.7 Earthing or Grounding and Potential Balancing /
Erdung und Potenzialausgleich
Especially when running a combination of
! different communications equipment, it is
important to establish correct potential bal-
ancing between them − depending on the
local earthing measures.
⇒ If subracks are mounted in racks,
as a basic principle you must
ground the rack frame before you
connect the external cabling from
the telecommunications center to
the system rack.
⇒ The grounding must be effective as
long as external cables are con-
nected to the equipment.
2.2 Handling the Subrack /
Handhabung des Baugruppenträgers
2.2.1 Front Door of the Device / Geräte-Vordertür
A subrack being fitted with a front door
! must only be operated with this door
closed. There is danger of personal injury,
if the door of the subrack is open.
⇒ For this reason, before working on
the subrack, open the front door,
raise it and then remove it.
⇒ Once the work has been complet-
ed, refit the door belonging to this
subrack and close it.
When the front door is open − especially
! when additional covers have been re-
moved − components with high operating
temperatures (as per Chapter 2.2.4) may
also become accessible!
1.Vorabzug:A30808-X3580-H504-1-7620
MMN
Insbesondere bei gemeinsamer Verwen-
dung verschiedener Kommunikationsgerä-
te ist es wichtig − abhängig von den
örtlichen Erdungsmaßnahmen − auf kor-
rekten Potenzialausgleich zu achten.
⇒ Beim Einbau von Baugruppenträ-
gern in Gestelle müssen Sie grund-
sätzlich den Gestellrahmen erden,
bevor Sie die externe Verkabelung
von der Betriebsstelle an das
Systemgestell anschließen.
⇒ Die Erdung muss bestehen blei-
ben, solange Kabel von außen an
die Geräte angeschlossen sind.
Baugruppenträger, die eine Vordertür ha-
ben, dürfen nur betrieben werden, wenn
diese Tür geschlossen ist. Bei geöffneter
Vordertür des Baugruppenträgers besteht
Verletzungsgefahr.
⇒ Öffnen Sie deshalb, bevor Sie am
Baugruppenträger arbeiten, des-
sen Vordertür, heben Sie sie an
und nehmen Sie sie ab.
⇒ Bringen Sie nach Beendigung der
Arbeiten die zu diesem Baugrup-
penträger gehörende Vordertür
wieder an und schließen Sie sie.
Bei geöffneter Vordertür − insbesondere
nach dem Öffnen von zusätzlichen Abde-
ckungen − können auch Teile mit hoher
Betriebstemperatur (entsprechend
Kapitel 2.2.4) zugänglich sein!
19
MMN Maintenance
SLD/T16-2.5

2.2.2 Equipment Cooling / Gerätekühlung

If the device is mounted in a rack together
! with other devices and if the power con-
sumption of all devices − mounted one
above the other − exceeds 350 W, a
forced-ventilation equipment must be built
in and must be ready for operation.
Falls das Gerät zusammen mit anderen
Geräten in einem Gestell montiert ist und
die Leistungssumme aller übereinander
angeordneten Geräte 350 W übersteigt,
muss eine Vorrichtung zur Zwangsbelüf-
tung vorhanden und betriebsbereit sein.

2.2.3 Weight Information / Gewichtsangaben

Warning Labels Warnschilder

at the subrack in case of heavy am Baugruppenträger bei hohem
weight. Gewicht.

The maximum weight to be lifted Das maximale Hebegewicht für

by one person is fixed to 18 kg! eine Person ist auf 18 kg festge-
MAXIMUM
EQUIPMENT legt!

WT ... KG

UNEQUIPPED

WT ... KG

2.2.4 Components Subject to High Operating Temperatures /

Komponenten mit hoher Betriebstemperatur

! Warning Label Warnschild

for equipment components (e. g. für Geräteteile (z. B. Kühlkörper),
heat sinks) which may attain high die hohe Betriebstemperaturen er-
operating temperatures. reichen können.

Touching these components is lia- Beim Berühren solcher Teile be-

ble to result in personal injury! steht Verletzungsgefahr!

On extremely hot surfaces, a label Auf extrem heißen Oberflächen ist

! with red text “HOT POINT” on a
white background is added.
It indicates highest injury hazard.
zusätzlich ein Schild mit der roten
Schrift “HOT POINT” (“heißer
Punkt”) auf weißem Grund ange-
bracht.
Es kennzeichnet höchste Verlet-
zungsgefahr.

20 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance
SLD/T16-2.5
2.3 Handling Modules, FO Equipment and Batteries /
Handhabung von Baugruppen, LWL und Batterien
2.3.1 Handling Modules Containing Electrostatically-sensitive Compo-
nents / Handhabung von Baugruppen mit elektrostatisch gefährde-
ten Bauteilen
ESD symbol
Modules displaying this label are
fitted with electrostatically-sensi-
tive components, i.e. you must
handle them in accordance with
the necessary safety measures.
Grounding bracelets must always be worn
! when packing, unpacking, touching, pull-
ing, or inserting modules displaying the
ESD symbol. This will ensure the modules
not to be damaged.
The rack is equipped with marked
ESD
grounding sockets to accept the
connecting plug for the grounding
bracelet.
Every printed circuit board has a ground-
ing outer edge, which is connected to the
ground terminal of the module, and which
can be used to grasp the board.
⇒ Avoid touching any device termi-
nals, contacts of the connector strip
or printed conductors − even if you
are properly grounded.
1.Vorabzug:A30808-X3580-H504-1-7620
MMN
EGB-Symbol
Baugruppen, die dieses Zeichen
tragen, sind mit elektrostatisch
gefährdeten Bauteilen bestückt,
d. h. beim Umgang damit müssen
Sie die erforderlichen Sicherheits-
maßnahmen einhalten.
Wenn Baugruppen mit EGB-Symbol aus-
oder eingepackt, berührt, gezogen oder
gesteckt werden, dann müssen stets Er-
dungsarmbänder getragen werden. Da-
durch wird sichergestellt, dass die
Baugruppen nicht beschädigt werden.
Am Gestell sind gekennzeichnete
Erdungsbuchsen zur Aufnahme
des Anschlusssteckers für das Er-
dungsarmband vorhanden.
Jede Leiterplatte hat einen Erdungsau-
ßenrand, der mit dem Masseanschluss
der Baugruppe verbunden ist, und an
dem die Platte angefasst werden kann.
⇒ Vermeiden Sie es, irgendwelche
Bauelementeanschlüsse, Kontak-
te der Steckerleiste oder Leiterbah-
nen − auch bei vorschriftsmäßiger
Körpererdung − zu berühren.
21
MMN Maintenance
SLD/T16-2.5

⇒ When pulling and inserting mod- ⇒ Verwenden Sie beim Ziehen und
ules, use the integral plug and pull Stecken von Baugruppen die daran
aids (plastic levers). angebrachten Zieh- und Steckhil-
fen (Kunststoffhebel).

Modules which are located in a screened, Baugruppen, die sich in einem abge-
unopened housing are protected at any schirmten, ungeöffneten Gehäuse befin-
rate. den, sind in jedem Fall geschützt.

☞ The
European Standards EN
100015-1 to 4 contain instructions
how to handle electrostatically-sen-
sitive devices properly.
☞
Die Europa-Normen EN 100015-1
bis 4 geben Anleitungen zum sach-
gemäßen Umgang mit elektrosta-
tisch gefährdeten Bauelementen.

2.3.2 Handling Optical Fiber Connectors and Cables /

Handhabung von LWL-Steckverbindungen und -Leitungen
Optical connectors are precision-made Optische Steckverbindungen sind Präzisi-
components and must be handled ac- onsteile und müssen dementsprechend
cordingly. To ensure faultless function, behandelt werden. Eine einwandfreie
the following points must be observed. Funktion ist nur dann sichergestellt, wenn
nachfolgende Punkte berücksichtigt wer-
den.

The minimum bending radius for optical fi- Für LWL-Leitungen darf ein Biegeradius
! bers is 30 mm! von 30 mm nicht unterschritten werden!

Mechanical damage to the surfaces of op- Mechanische Beschädigungen der Stirn-

tical connectors impairs transmission
quality by higher attenuation.
⇒ For this reason, do not expose the
connectors to impact.
flächen von optischen Steckverbindungen
erhöhen die Dämpfung und mindern des-
halb die Übertragungsqualität.
⇒ Vermeiden Sie deshalb Stoßbean-
spruchungen der Steckverbinder.

22 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance
SLD/T16-2.5
⇒ Always fit optical fiber connectors
with protective caps to guard them
against mechanical damage and
contamination. The protective dust
caps should only be removed im-
mediately prior to installation.
⇒ Once the protective dust caps have
been removed, you must check the
surfaces of the optical fiber connec-
tors to ensure that they are clean,
and clean them if necessary.
For cleaning, the C42334-A380-
A926 optical fiber cleaning tool or a
clean, lint-free cellulose cloth or a
chamois leather is suitable. Freon
TF, isopropyl alcohol (99 %), or
white spirit can be used as cleaning
fluids.
2.3.3 Handling Batteries / Handhabung von Batterien
Some equipment may contain accumula-
tors or batteries of different technologies −
e. g. lithium batteries or others.
☞ Basically, ☞ Grundsätzlich
the VDE 0510
(DIN57510) regulations are valid. VDE 0510 (DIN57510).
☞ Also
ternational standards, if applicable: ☞ folgende internationale Normen:
observe also the following in- Beachten Sie gegebenenfalls auch
IEC 60130-17 (device interconnec-
tions)
IEC 61429 (recycling symbol)
IEC 61438 (safety and health haz-
ards)
IEC 60086-4 (handling lithium bat-
teries)
1.Vorabzug:A30808-X3580-H504-1-7620
MMN
⇒ Schützen Sie LWL-Steckverbinder
grundsätzlich mit einer Schutzkap-
pe vor mechanischen Beschädi-
gungen und Verschmutzungen. Die
Staubschutzkappe soll erst unmit-
telbar vor dem Einbau entfernt wer-
den.
⇒ Prüfen Sie nach Entfernen der
Staubschutzkappen die Stirnflä-
chen der LWL-Stecker auf Sauber-
keit und reinigen Sie sie
gegebenenfalls.
Zum Reinigen kann das LWL-Rei-
nigungswerkzeug C42334-A380-
A926 oder ein einwandfrei saube-
res, fusselfreies Zellstofftuch oder
Fensterleder verwendet werden.
Als Reinigungsflüssigkeit kann
Freon TF, Isopropylalkohol (99 %)
oder Spiritus verwendet werden.
Bestimmte Geräte können Akkumulato-
ren oder Batterien verschiedener Techno-
logien enthalten − z. B. Lithium-Batterien
oder andere.
gilt die Vorschrift
IEC 60130-17 (Geräteverbindun-
gen)
IEC 61429 (Recyclingsymbol)
IEC 61438 (Sicherheits- und
Gesundheitsrisiken)
IEC 60086-4 (Umgang mit Lithium-
Batterien)
23
MMN
⇒ Pay attention to error messages re-
ferring to the accumulator or the
battery.
Accumulators or batteries which are inte-
grated in the device should only be re-
placed by the equipment manufacturer.
⇒ If replacement is necessary, do not
remove the accumulator or the bat-
tery from the device, but send in the
complete device or the removable
battery pack.
Never shortcut batteries directly without
! using a discharging resistor! Without a re-
sistor very high current will flow causing a
risk of explosion!
If you depollute batteries, you must ob-
serve the local regulations applicable to
hazardous waste.
2.4 Switching OFF and ON / Aus- und Einschalten
2.4.1 Emergency Switching OFF / Notabschaltung “OFF”
⇒ Especially if smoke or fire escapes
from the device (or in other emer-
gency situations), switch OFF the
device immediately − by all relevant
circuit breakers in the connector
panel of the rack.
First, switch OFF the protection
power supply and then the working
power supply, if possible.
24
Maintenance
SLD/T16-2.5
⇒ Achten Sie auf Fehlermeldungen,
die sich auf den Akkumulator bzw.
die Batterie beziehen.
Ins Gerät eingebaute Akkumulatoren oder
Batterien sollen nur beim Gerätehersteller
ausgetauscht werden.
⇒ Wenn ein Austausch erforderlich
ist, dann bauen Sie nicht den Akku-
mulator oder die Batterie aus dem
Gerät aus, sondern schicken Sie
das komplette Gerät oder das her-
ausnehmbare Batteriepack ein.
Schließen Sie niemals Batterien direkt
ohne Entladewiderstand kurz! Ohne Wi-
derstand können so hohe Ströme fließen,
dass Explosionsgefahr besteht.
Beim Entsorgen von Batterien müssen
die örtlichen Vorschriften über Beseiti-
gung von Sondermüll eingehalten wer-
den.
⇒ Insbesondere falls Rauch oder
Feuer aus dem Gerät austritt (oder
in anderen Notsituationen), schal-
ten Sie das Gerät sofort aus − mit
allen zugehörigen Sicherungsauto-
maten im Gestell-Anschlussfeld.
Schalten Sie möglichst zuerst die
Ersatz-Stromversorgung aus, dann
die Betriebs-Stromversorgung.
1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance
SLD/T16-2.5
⇒ However, consider that such an
emergency shutdown can discon-
nect important communication lines
which may be required just in the
case of emergency.
. benötigt werden.
For this reason, shutdown the de-
vice only if it is inevitable. Other-
wise perform the normal switching-
off procedure (Chapter 2.4.2).
⇒ After the emergency shutdown,
check if the device is dead − either
by using a measuring device or by
the LED display of the device, if ap-
plicable.
2.4.2 Normal Switching OFF Procedure / Normales Abschalten “OFF”
⇒ 1. Make sure that the device does
no longer transmit any traffic
signals, or that they are trans-
mitted via a protection device.
⇒ 2. Save the local data base.
⇒ 3. Switch OFF the laser.
⇒ 4. Switch OFF the device − by all
relevant circuit breakers in the
connector panel of the rack.
⇒ First, switch OFF the protection
power supply and then the
working power supply.
⇒ 5. After the shutdown, check if the
device is dead − either by using
a measuring device or by the
LED display of the device, if ap-
plicable.
1.Vorabzug:A30808-X3580-H504-1-7620
MMN
⇒ Bedenken Sie jedoch, dass durch
solch eine Notabschaltung wichtige
Kommunikationsleitungen unter-
brochen werden können, die gera-
de im Notfall eventuell dringend
Nehmen Sie deshalb nur dann eine
Notabschaltung vor, wenn es un-
umgänglich ist. Verfahren Sie sonst
entsprechend der normalen Ab-
schaltprozedur (Kapitel 2.4.2).
⇒ Überprüfen Sie nach dem Notab-
schalten, ob das Gerät spannungs-
frei ist − entweder mit einem
Messgerät oder gegebenenfalls
durch eine LED-Anzeige am Gerät.
⇒ 1. Stellen Sie sicher, dass das ab-
zuschaltende Gerät keine Nutz-
signale mehr überträgt bzw.
dass diese über Ersatzeinrich-
tungen umgeleitet werden.
⇒ 2. Sichern Sie die lokale Daten-
basis.
⇒ 3. Schalten Sie den Laser ab.
⇒ 4. Schalten Sie das Gerät aus −
mit allen relevanten Siche-
rungsautomaten im Gestell-
Anschlussfeld.
⇒ Schalten Sie zuerst die Ersatz-
Stromversorgung aus, dann die
Betriebs-Stromversorgung.
⇒ 5. Überprüfen Sie nach dem Ab-
schalten, ob das Gerät span-
nungsfrei ist − entweder mit
Hilfe eines Messgerätes oder
gegebenenfalls durch die LED-
Anzeige am Gerät
25
MMN Maintenance
SLD/T16-2.5

2.5 Switching ON / Einschalten “ON”

⇒ 1. Switch ON the device using the ⇒ 1. Schalten Sie das Gerät mit dem
circuit breaker in the connector Sicherungsautomat im Gestell-
panel of the rack. Anschlussfeld ein.

⇒ 2. Start the LCT operating terminal ⇒ 2. Starten Sie das Bedienterminal

and carry out the commission- LCT und führen Sie die Inbe-
ing procedure as described in triebnahme entsprechend die-
this Installation and Test Manu- sem Inbetriebnahmehandbuch
al (ITMN). durch (ITMN).

⇒ 3. Switch ON the Laser. ⇒ 3. Schalten Sie den Laser ein.

26 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

3 Introduction

3.1 General Information about Maintenance

For the commissioning, the operation (including alarm supervision) and the mainte-
i nance, a TransXpress Local Craft Terminal T-LCT – abbreviated to LCT –
or a TransXpress Network Craft Terminal T-NCT – abbreviated to NCT – is used. In cas-
es where explanations relate to both, the LCT and the NCT, the generic term of the
“operating terminal” is used.

☞ The views and the configuration options, which are relevant to the operating ter-
minal are summarized in Chapter 4.
Details of operation can be found in the Operating Manual OMN:
– the OMN:SL as for the operating part.

☞ Are the following cards and modules mentioned in a general description it is also
stated for their extended and upgrade ones not named in detail:
CLL -> CLL64-2,
OIS4 -> OIS4-2,
OIS16 -> OIS16-2,
SCU -> SCU-R2 -> SCU-R2E.

3.1.1 Requirements for Personnel

To maintain all the SLD and SLT network elements the following personnel require-
ments must be complied with:
• Training as a service technician or a equivalent training in the telecommunications
• Sound basic knowledge of the telecommunications and the station installation tech-
nique
• Suitable, the unit-specific training by the equipment manufacturer who imparts the
knowledge of the units and the systems required for the planned activity.
• PC knowledge, additional basic knowledge of Windows-NT operation
• Basic knowledge of testing, the knowledge of how to use the measuring instruments
• Knowledge of how to work with the electrostatic-sensitive components
• Knowledge of how to work with the optical fibers and the laser light sources

3.1.2 Test Equipment, Tools and Resources Required

The following are required for corrective maintenance of the SLD and SLT net-
work elements:
• Opt. power meter (for checking the output power of the OIS1, of the OIS4/OIS4-2,
of the OIS16/OIS16-2 and of the OB), level >+15dBm
Note: The values for the output power can also be displayed using the application
software.
• Optical attenuation element for power level >+15dBm
• SDH-/PDH analyzer; for checking the electrical tributary output signals (EIPS1)
• ESD grounding strap
• Assembling tool

1.Vorabzug:A30808-X3580-H504-1-7620 27
MMN Maintenance
SLD/T16-2.5

3.2 Fault Management

Fault management deals with the monitoring of the correct functioning of all the HW and
SW components within a network element as well as monitoring all the incoming digital
signals.
Main tasks of the fault management for the SL16:
• Detecting all deviations from a fault-free required behavior; these are sometimes
communicated to the performance management function as well
• Preparing fault messages by eliminating the non-relevant deviations; these are
sometimes communicated to the performance management function as well
• Introducing the automatic maintenance processes, such as the laser safety cutout,
the protection switching, the alarm indication signal (AIS) insertion or the remote de-
fect/error indications
• Processing the operator-controlled maintenance measures
• Reducing the number of alarms for fault correlation (masking out follow-up faults)
and the persistence checks (masking out instantaneous alarms)
• Classifying the alarm events according to the alarm severities
• Marking the alarm events by indicating the time (time stamp)
• Signaling spontaneous alarms to the management facilities
• Signaling alarms to the local alarm system (in accordance with Bw7R)
• Filtering of the transmission alarms and the network alarms
• Indicating the module type to be used and fault status of the exchangeable units
(modules) and 2Mbit/s Clock Line supervision for module type CLL64-2
• Saving the alarm events in an “Historical Event Log” record for evaluation at a later
stage
• Supporting the fault pinpointing for corrective maintenance

3.3 Monitoring
To save time in restoring the transmission of the user information (traffic) when malfunc-
tioning occurs, it is necessary to monitor a number of the important functions continu-
ously in each module (= BG).
The monitored functions depend on the tasks of the module. The following are moni-
tored or checked:
• Supply voltages
• Internally-generated voltages
• Presence of the internal timing signals (fault-free functioning of PLLs)
• Presence of the digital signals at critical points
• Laser parameters
• Watchdog for the checking processor operation
• Integrity checks/checksums for RAM, NVRAM, EPROM, Flash-EPROM, EEPROM
etc.
• Communication tests between the SCU module and all the remaining modules
• Communication tests between the CLL module and all the remaining modules (ex-
cept for the SCU module)
• The bus systems ICB (internal control bus) and the P bus (protection bus), the T1
clock bus, the OH bus, the K bus (for protection switching) and the U-LED bus (for
supplying input to the fault indication LEDs)
• External Connection Port supervision
• Ethernet Connection failure

28 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

• EOW functions including the telephone

The System Control Unit (SCU) module plays a central role in the system monitoring. It
monitors all the internal functions of the synchronous line units (SEMF function) as well
as the system alarms. The Microcontrollers (slaves) in the peripheral data processing
unit PCU of every module transmit the alarm information to the SCU (master).
The SCU signals the alarms to the operating terminal (LCT or NCT), to the Telcommu-
nications Network Management System TMN and to the rack and the station alarm bus
(via relay contacts).
The correct SW execution sequence in the various modules is monitored by watchdogs.
After each violation of the watchdog conditions, the corresponding SW modules have to
be restarted.
The software-based monitoring concept allows flexible adaptation to customer’s re-
quests.

3.3.1 Sensors
Various monitoring points on the modules (sensors) test the condition of the important
parameters e.g. in the optical interfaces (the laser output power, the optical receiver out-
put power, the missing input signal etc.). This information is filtered and evaluated. The
results are made available via the central control unit to the Q-F and Q-B3 interfaces.
For all the SDH interfaces, the system data is tested during operation by evaluating the
fault monitoring bytes B1, B2 and B3 of the STM frame. Possible fault information arrives
at the SCU module which calculates the specific bit error rate of the link, evaluates it for
protection switching actions and forwards it on request as the current system parame-
ters to the TMN and to the operating terminal.

3.3.2 External Test and Diagnostic Interfaces for Communication Traffic

In addition to their integrated monitoring system, a number of modules of SL units have
the following external test and diagnostic interfaces:

Module EIPS1
On the EIPS1 module, there is one monitoring output (signals M1 to M4) for every four
electrical tributary output ports (140 Mbit/s or STM-1 signal). On the short-circuit-protect-
ed 75Ω coaxial sockets, the data streams to the LTU module (outgoing) can be moni-
tored without interrupting operation.

Modules OIS1, OIS4, OIS4-2, OIS16 and OIS16-2

A number of parameters of these modules which are important for purposes of diagnosis
(e.g. laser parameters) are monitored by the software of the PCU and can be interrogat-
ed by the management facilities (operating terminal or operations system).

1.Vorabzug:A30808-X3580-H504-1-7620 29
MMN Maintenance
SLD/T16-2.5

3.3.3 Monitoring the Receive Interfaces

For the special features of the operator interface see Chapter 4.
i

3.3.3.1 Port Monitoring

The monitoring of the STM-1, STM-4 and STM-16 receive ports for an incoming loss of
signal, (LOS) alarms and the loss of frame (LOF) alarms – for transmission faults from
other NEs – can be activated or deactivated on the modules OIS1, OIS4/OIS4-2,
OIS16/OIS16-2, OP and EIPS1 (described below using the STM-16 as an example):
1. At the operating terminal in the traffic view (menu items: <View> <Traffic View>), se-
lect functional symbol STM16. Use the right-hand mouse button to select the desired
port symbol and select <Subview> item in the context-sensitive menu.
2. In the traffic flow view window use the right-hand mouse button to select the symbol
STM16 and, in the context-sensitive menu, select <Configuration> <STM16> items.
3. By selecting the field for the “Port Monitoring” you can activate/deactivate the func-
tion. Execute the command with the <Apply> button.
The ports, used for a “Synchronization” having any signal fault, will conduct to a “Do not
use for synchronization” message. The same will happen if a CLA adapter is used and
its Sa-Bits are misaligned or faulty.

3.3.3.2 Connection Supervision

The monitoring of the incoming transmission alarms at VC-4 level of the STM-1, STM-4
and STM-16 signals can be configured as follows – described below using the STM1
(electrical) as an example:
1. At the operating terminal in the traffic view (menu items: <View> <Traffic View>), se-
lect the functional symbol STM1(el.). Use the right-hand mouse button to select the
desired port symbol and select <Subview> item in the context-sensitive menu.
2. In the traffic flow window, use the right-hand mouse button to select the symbol box
AU4/VC4 and in the context-sensitive menu select the items:
<Configuration> <AU4/VC4>.
3. Open the drop-down menu for Connection Supervision Mode and chose one of the
following:
– Normal Monitoring:
Monitoring the path overhead
– Supervisory UNEQ:
Monitoring for missing operating signal at the start of the VC-4 path
– Disabled:
Monitoring switched off
Execute the command with the <Apply> button.
The connection supervision functions can be configured independently of each other for
any path to monitored or not. The “not monitored” state can be useful for a path which
is not used for example.

3.3.3.3 Termination Point Monitoring

The Monitoring of the incoming transmission alarms at VC-4 level of the plesiochronous
140 Mbit/s signals can be configured as follows:

30 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

1. At the operating terminal in the traffic view (menu items: <View> <Traffic View>) se-
lect functional symbol E4. Use the right-hand mouse button to select the desired port
symbol and select <Subview> item in the context-sensitive menu.
2. In the traffic flow window use the right-hand mouse button to select the symbol VC4
and in the context-sensitive menu select the items: <Configuration> <VC4>.
3. Now you may activate or deactivate the selectable field for the Termination Point
Monitoring.
Execute the command with the <Apply> button.
The termination point monitoring functions can be switched on or off independently of
each other for any 140 Mbit/s path. The “deactivated” state can be useful for a path
which is not used for example.

3.3.3.4 TTI Processing

Trail Trace Identifier for the VC-4 Path
For the STM-1, STM-4 and STM-16 signals you can use the following procedure to
switch on and switch off the monitoring of the VC-4 path from the source to the monitor-
ing point using the Trail Trace Identifier (TTI) – described using the STM1(electrical) as
an example:
1. At the operating terminal in the traffic view (menu items: <View> <Traffic View>), se-
lect the functional symbol STM1(el.). Use the right-hand mouse button to select the
desired port symbol and select <Subview> in the context-sensitive menu.
2. In the Traffic Flow window use the right-hand mouse button to select the symbol
AU4/VC4 and in the context-sensitive menu select
<Configuration> <AU4/VC4>.
3. Open the drop-down menu for TTI (Trail Trace Identifier) Processing and chose one
of the following
– Disabled:
Monitoring switched off
– Enabled:
Monitoring switched on
– No Trace expected:
No path information is expected
Execute the command with the <Apply> button.
The VC-4 receive signal can be tested for deviations from the expected VC-4 path iden-
tification (Alarm TIM, Trace Identifier Mismatch).

Trail Trace Identifier for the Regeneration Section

For the STM-1, STM-4 and STM-16 interfaces you can switch on and switch off moni-
toring of the VC-4 path between two adjacent NEs (regeneration section) using path
identifiers (Regenerator Section Trail Trace Identifier, RS TTI). By this, cabling between
adjacent NEs can be monitored. Switching on and off the monitoring can be done as de-
scribed below using STM1(electrical) as an example:
1. At the operating terminal in the traffic view (menu item <View> <Traffic View>), se-
lect the functional symbol STM1(el.). Use the right-hand mouse button to select the
desired port symbol and select <Subview> in the context-sensitive menu.

1.Vorabzug:A30808-X3580-H504-1-7620 31
MMN Maintenance
SLD/T16-2.5

2. In the Traffic Flow window use the right-hand mouse button to select the symbol
STM1 and then select “enabled” or “disabled” in the context-sensitive menu to
RS TTI Processing. Confirm with the <Apply> button.
3. Define the values for the Trail Trace Identifier, Transmitted and Expected, in the win-
dow to the menu item:
<Configuration> <Trail Trace>.
Confirm with the <Apply> button.
Deviations between the values for received and expected a Trail Trace Identifier are re-
ported with the alarm RS TIM (in the alarm window to the STM1/4/16 functional unit).
See also Tab. 7.6, Tab. 7.13 and Tab. 7.16.

3.3.3.5 Unequipped
For the VC-4 path you can activate the monitoring which checks/signals the VC-4 path
for a faulty operating signal (cf. Chapter 3.3.3.2).
You can also (intentionally) insert the message “Unequipped” (STM-1 electrical as an
example):
1. At the operating terminal in the traffic view (menu item <View> <Traffic View>), se-
lect the functional symbol STM1(el.). Use the right-hand mouse button to select the
desired port symbol and select <Subview> item in the context-sensitive menu.
2. In the Traffic Flow window use the right-hand mouse button to select the symbol
AU4/VC4 and in the context-sensitive menu select:
<Configuration> <AU4/VC4>.
3. You can then select the field “Insert Supervisory UNEQ Signal”.
Execute the command with the <Apply> button.
This setting is also available for functional symbols STM1 (opt.), STM4 and STM16.
This setting does not work if contiguous concatenation is in operation.
i

3.3.4 Monitoring of Modules CS4, EBSL, LTU and PSUTP

The modules EBSL, LTU and PSUTP occupy a special position as regards module mon-
itoring, since – in contrast to all the other modules – the included practically no monitor-
ing functions of their own.
The module LTU, as an interface module of EIPS1 (required once for each EIPS1), gen-
erates the equipment alarm LTU in the alarm table of the assigned EIPS1 module when
an error occurs.
The modules required for an EIPS1 module protection switching EBSL (selector module
for working/protection EIPS1) and PSUTP (power supply for LTU and EBSL) generate
equipment alarms for EBSL and for PSUTP in the alarm table of the EIPS1-protection
module if an error occurs.
The connection module CS4 (required if an OIS16/OIS16-2 is to be used as a tributary
module) supervises its own internal power supply and signals a power supply failure
with a red fault LED on the module itself.

32 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

3.3.5 Monitoring of Optional Box CLA

The CLA box is located in the rack terminal panel and includes no direct monitoring, ex-
cept a CLA service status LED (green) on the front panel.
The LED is switched off (green light distinguished) with a reset of the internal control mi-
croprocessor and can be switched on (green light illuminated) by SW instruction after
error free start-up of the control processor.
Each channel of the CLA box has its own Sa-Bit selector switch.
If a CLA channel having any signal fault it will conduct to a
“Do not use for synchronization” message.
The same will happen if its Sa-Bits are misaligned or faulty.
If the synchronization using the CLA fails a “No 2MBit” alarm signal will be generated,
which primarily means that no CLL64-2 module is used..

3.3.6 Monitoring of the NE Control Communication by LAN and TMN

The monitoring of the control communication link using the LAN (Ethernet) and from it
to a Telecommunication Management System (TMN) done by the SCU.
If the communication or the link fails a “Ethernet Fail” alarm signal will be generated.

1.Vorabzug:A30808-X3580-H504-1-7620 33
MMN Maintenance
SLD/T16-2.5

3.4 Alarm Signaling

How alarms are displayed on the operating terminal and how they can be influenced –
i including alarm suppression – is summarized in Chapters 4.3 and 4.4.

3.4.1 Alarm Messages

The aim of the unit alarm and the monitoring philosophy is to make sufficient alarm in-
formations available for an efficient fault locating on the exchangeable system units, i.e.
the modules.
Alarm messages are either
• caused by faults in the own unit: Equipment or Unit Alarms
• or delivered by the transmission network, caused by fault events in a remote network
element or on the transmission path:
Transmission or Communication Alarms
• or generated by a General Malfunction of the NE (e.g. clock source function SEC).
The existing alarms are correlated and evaluated according to their importance and the
possible follow-up alarms – if required – suppressed. New alarm messages sometimes
have to be set up which notify the fault in the own unit to a neighboring network element
(=NE) (e.g. RDI, Remote Defect Indication).
According to the importance of the alarm messages and the alarm priorities which
have been allocated to them, they trigger different reactions. A minor fault can, for ex-
ample, lead to an impairment of data transmission, but will not influence operation sig-
nificantly. Therefore, a deferred alarm will be generated. On the other hand, serious
faults can interrupt the operation and therefore may generate a major alarm which re-
quires immediate fault clearance.
All activated alarms are signaled spontaneously at each time the alarm status changes.
If the signaling (operating) mode was configured for “Operation”, all the spontaneous
alarm messages of the functional units and the modules are signaled provided that no
masking with the alarm suppression has taken place.
If the “Maintenance” mode was configured for corrective maintenance measures, the
transmission of all the alarms of the functional units and modules is suppressed (from
the NE to the operating terminal). The NE state is configured using the main menu items:
<NE State> <Set to Operation> or <Set to Maintenance>
(see Chapter 4.4.1)
and is displayed in the main status bar
(see Chapter 4.1.3).
The main menu commands: <Window> <Update All Alarms> can also be used in main-
i tenance mode to update the alarm display.

The spontaneous alarm messages are also stopped when the NE is in the overload sta-
tus.
To display the alarms (see also Chapter 4.3) there are several possibilities available.
To display the alarms, the alarm messages are issued as follows:
• Via the Q-F interface to the local LCT (Local Craft Terminal)
• Via the Q-B3-interface either again to the local LCT or to a remote NCT (Network
Craft Terminal)
• Via the Q-B3 interface to the Telecommunications Network Management System
TMN

34 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

• For display on the local network element:

– on most modules a red fault LED signals device faults which have occurred
– a subrack alarm and a phone indication panel (SRAP-PI) on the subrack contains,
inter alia, the LEDs for Bw7R signaling (A and B alarms)
• The Bw7R alarm messages generated via an alarm interface for a rack row alarm
indication (light signal equipment, LZE) and for a station alarm indication (central
service observation ZBBeo).

3.4.2 Alarm Types, Alarm Classes, Alarm Severities

As regards generation, there are three different alarm types, namely:
• SPO alarms, these are spontaneous alarms which are triggered if one or more
alarms have changed their alarm status
• ABR alarms, these are alarms on demand; a display of the date/time information is
not required for these
• ANT alarms, this is an answer alarm information; besides the current alarm infor-
mation, the moment of interrogation is also displayed here
As regards the seriousness of a fault, the following different alarm classes can be dis-
tinguished according to the signaling image for a style 7R (see Chapter 3.4.5):
• major faults, class A: Cause a major impairment or an interruption of operation; fault
clearance is required immediately,
• deferred faults, class B: Cause a minor impairment of operation or a slight deterio-
ration of transmission data; faults need not be cleared immediately but can be
cleared at a favorable point in the time of the operating sequence is performed.
For alarm displays at the operating terminal, an overview alarm list and an alarm window
for individual context-sensitive menus, there are the following alarm severities:
• Critical: Critical alarms (not implemented in this version)
• Major: Major alarm
• Minor: Alarm of no great significance
• Warning: Alarm acting as a warning

3.4.3 Alarm Interrogation

All the equipment and transmission alarms which signaled in succession are logged in
the NE (see also Chapter 3.9). Each time an alarm status is changed in the NE, module
SCU updates this list. The management facilities use this list for their alarm display and
for synchronizing the alarm status.
The NE answers an alarm status interrogation with the currently available entries in the
list of the generated alarms, but filtered according to the alarm masks configured at
present.
For all the alarms of the physically-available modules, the functional units and the termi-
nation points, the current alarm status can be interrogated; a collective interrogation is
also possible.

3.4.4 Alarm Displays on the Modules

With the exception of the modules CLA box, CS4, EBSL, LTU, PSUTP and TIF, there is
a green service status LED and a red fault LED on the front of each module. The LEDs
are not lit when the module is operating normally and are only visible when the subrack
door is open.

1.Vorabzug:A30808-X3580-H504-1-7620 35
MMN Maintenance
SLD/T16-2.5

The service status LED shows the current service status of the module. It is activated
automatically by the SCU module if the latter takes the module out of service. The ser-
vice status LED cannot be influenced by the module itself, except the CLA module, or
by the commands from the operating terminal or from the OS. When the service status
LED lights the module may be pulled out of the subrack, either the SL16 subrack or the
rack terminal panel subrack containing the add on boxes like the CLA.
The fault LED shows the internal equipment alarms and the errors in the application SW
but does not show communication alarms. To ensure that the LED also lights if there are
faults in the module’s internal power supply it is fed by an external supply voltage (ULED
bus) except the CLA box. Alarms can be triggered by the faults in the following compo-
nents of a module:
• PCU hardware
If hardware faults occur a message is also sent to the SCU (if possible) and the de-
fective module is switched off.
• ASICs (including internal clock supervision) and the hardware for signal transmis-
sion.
If the clock signal is not present an attempt is initially made to switch over to the re-
placement clock bus. A message is sent to the SCU. Only if both the clock busses
are faulty the fault LED will be switched on.
• Power Supply
If the power supply on the module fails or the voltage is incorrect the fault LED is
switched on. If the power supply fails, power is supplied to the service status and
fault LEDs via the ULED bus of the subrack from other modules so that a display is
still ensured.
• Multiplexer Time Source (MTS), displayed only on the module SNL
• Internal Multiplexer Time Source (IMTS), displayed only on the interface modules
• PCU Software
If an error is detected in the PCU software an attempt is made to rectify it by per-
forming an automatic reset (and associated restart) of the module. If this process
fails, the fault LED is activated and the module is switched off.
The fault LEDs of the several modules cannot be effected by commands from the oper-
ating terminal or from the OS.
After the fault is rectified the fault LED light is automatically extinguished.
The behavior of the module LEDs in the different operating/fault states is summarized
in the Table 3.1 for the module SCU and in the Table 3.2 for all the other modules (these
contain PCUs).

Operating State Red Fault LED Green Service

Status LED

Power supply on / reset lights lights

“OpenBootProm” phase runs goes out/lights1) lights

First phase of SW start up (operating system starts up) goes out/lights1) goes out

Second phase of SW start up (start of application SW goes out/lights1) flashes

ASW) up to end of NE start up

Tab. 3.1 Behavior of Module LEDs for Module SCU

36 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Operating State Red Fault LED Green Service

Status LED

Operating phase (start phase finished) goes out/lights1) goes out

1)
During shut down procedure goes out/lights flashes
1)
“Shut down” without/with error goes out/lights lights

Module in wrong slot flashes flashes

1) ... Goes out: no fault, lights: Fault(s)

Tab. 3.1 Behavior of Module LEDs for Module SCU (Cont.)

Operating Status Red Fault LED Green Service

Status LED

SW start up lights lights

Error during the boot phase, error in boot SW lights goes out

SW download, boot SW ok, error in application SW lights lights

Operating phase, boot SW ok, application SW ok goes out goes out

Module out of service (CSO, card out of service) goes out goes out

“Disabled” by module SCU goes out lights (switched by

SCU)

“Disabled” by module SCU becomes unchanged unchanged

“Disabled_unavailable” because of timeout in internal con-
trol bus

in case of fault lights goes out/lights 1)

integrated self-test, boot SW ok goes out flashes

1) ... Lights: the green LED stays lit if it was activated before the error occurred

Tab. 3.2 Behavior of Module LEDs for all Modules with the Exception
of the SCU and LTU

The LTU, EBSL and PSUTP modules do not have either fault or service status LEDs,
they are monitored by the EIPS1 module to which they are assigned.
The CLA box in the rack terminal panel does not have a fault status LED but does have
a service LED, which only indicates fault free start-up of the box’s internal power supply
and control microprocessor however.
The CS4 module does not have a service status LED but does have a fault LED, which
only indicates faults in the module’s internal power supply however.
The SCU module also has a yellow LED on the front but this is not used in this version.
For the power supply for the LEDs see Chapter 3.12.2.

1.Vorabzug:A30808-X3580-H504-1-7620 37
MMN Maintenance
SLD/T16-2.5

3.4.5 Bw7R Alarms

See also Chapter 6.3.
i
In addition to the alarms which are signaled to the management facilities, the subrack
for SLD/SLT network elements supports an alarm indication interface which corre-
sponds to the alarm image which is standard for the style 7R (Bw7R) narrow racks.
The alarms raised in the subrack are combined into a summation alarm with two possi-
ble priority levels. The alarm is not specified in more detail. The SCU module forwards
the recognized fault message to the following alarm interfaces:
• to the central service observation ZBBeo (conventional central observation panel):
the central signal indicates that an alarm was raised in the operating station
• to the light signal equipment LZE at the end of the rack row (End of the rack row in-
dication): the fault is pinpointed to one rack row
• to the SRAP (SubRack Alarm Panel): the pinpointing to the subrack which is report-
ing the alarm signal
In the case of a clear unit faulting, the red LED INT on the front of the module causing
the fault LED illuminating; the LEDs of the modules are visible when the front cover of
the subrack (BGT) is open. See also Chapter 3.4.4.

Priority Levels
The priority of recognized faults is divided into three alarm levels:
• High severity alarms
• Low severity alarms
• Cleared alarms
Depending on the priority level of the incoming fault signal, the SEMF function of the
SCU module activates various local alarm interfaces (see also Fig. 3.2).

Location Alarm Message Alarm Type

LEDs go out, alarm Alarms extinguished

– contacts opened

Subrack alarm Red LED A lights See Tab. 6.2 to Tab. 6.4: columns Bw7R alarm signaling,
panel SRAP SRAP-PI
Yellow LED B lights

Light signal equip- a Contact closed

ment LZE As listed above for subrack alarm panel SRAP
b Contact closed

Central service ob- ZA(A) contact See Tab. 6.2 to Tab. 6.4: columns Bw7R alarm signaling,
servation closed ZA (for ZBBeo)
ZBBeo ZA(B) contact
closed

Tab. 3.3 Bw7R Alarm Messages

Set the alarm suppressions (see also Chapter 4.4.1) are also affect the signaling of the
Bw7R alarms.
If the alarm signaling operating mode (see Chapter 3.6) is set to “Maintenance” this has
no effect on the Bw7R alarms.

38 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Alarm displays on subrack alarm panel SRAP

The subrack alarm panel SRAP forms a unit with the Phone Indication PI display panel
and it is also visible when the BGT cover is not open. It serves to display a faulty system.
It contains the indicator LEDs A, B and EL for one or for two systems as well as a reset
button RT. The LEDs are fed from an external signaling voltage +S/-S which does not
depend on the central exchange power supply and the module voltage supply.

I II
A EL #1
RT
B #2

SRAP PI

Fig. 3.1 Subrack Alarm Panel / Phone Indication, SRAP-PI

Tab. 3.4 shows the importance of alarm displays of SRAP.

Name Element Color Alarm type Remarks

A LED Red High-priority alarm, Can be acknowledged with the RT button.

“major alarm” Function is automatically reactivated.

B LED Yellow Lower-priority alarm, Can be acknowledged with the RT button.

“deferred alarm” Function is automatically reactivated.

RT Reset Activation acknowledges A and/or B alarms. LEDs A

button – – and B are extinguished, LED EL is switched on.

EL LED Yellow Reminder that an Illuminates if the alarms were acknowledged which
alarm was raised were signaled with LED A and/or B. Is only extin-
guished if all alarms have been cleared.

Tab. 3.4 Alarm Displays of the SRAP

1.Vorabzug:A30808-X3580-H504-1-7620 39
MMN Maintenance
SLD/T16-2.5

SCU
ZA(A) za(a)
ZA(B) za(b)
SEMF

A A a
ICS
AZ B b
SRAP

Selection
B EL el
BZ

logic
Uc
RT1
RT2 RT button
+S
a1 A
A LED
SCU alarm b1 B
B LED

el EL
EL LED

Terminal panel
Connector E “Bw7R”
–S
+S
a2 LZE-a
b2 LZE-b to light signal
el2 LZE-el equipment LZE

za(a) ZA(A)
ZA(B) to central
za(b)
service observation
GND ZBBeo

Bw7R Style 7R SEMF Synchronous equipment management function

GND Ground SRAP Subrack alarm panel
ICS Internal communication channel Uc Operating voltage
LED Light-emitting diode ZA(A) Major alarm
LZE Light signal equipment ZA(B) Deferred alarm
SCU Synchronous control unit module ZBBeo Central service observation
RT Reset button

Fig. 3.2 Local Alarm Signaling for SRAP and External Signaling
Units via Module SCU (Shown with Power Supply Switched Off)

The Fig. 3.2 uses an example of the single-row subrack to show an overview diagram
of the local alarm signaling to the Subrack Alarm Panel (SRAP) and to the external sig-
naling equipment with the aid of the SCU module.

3.4.6 Customer-Specific Alarm Interface

The TIF and OHA modules support an alarm interface with up to 16 external alarms
which are inserted into two internal G.703 transmission channels (maximum 8 alarms
per channel). These alarms are also called as customer alarms or as environmental
alarms (e.g. door-open alarm, fire alarm).

40 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

The states of external alarm contacts are monitored here. The stationary alarm messag-
es alarm / no alarm are supported. The alarms are transferred from the NE directly to
the operating terminal. For each alarm it is possible to configure which of the alarm state
corresponds to a specific switching state of the alarm contact (open or closed).

3.4.7 Sa-Bit Alarm in Case of an Optional Use of a CLA Box

Check first for the use of a CLL64-2 module which must be there to allow an operation
of a external CLA box located in the rack terminal panel.
Sa-Bit mismatch or Sa-Bit fault should be isolated to the work of the CLA box operation.
Faults by the Sa-Bits will conduct a “Do not use for synchronization” message of the ap-
propriate channel.
Now check the switch setting of the Sa-Bit switches A2 (channel #1), A4 (channel #2)
and A6 (channel #3) in accordance to the net planning standards. In case of a match,
check and turn the switch by moving it forward and backward of the matched position
and see if the fault disappears. Else change the CLA box against a knowing good one
and check again. If fault is disappeared mark the defect box and send it to maintenance
service for repair.

3.5 Security Against Double Operation

A NE can be connected to up to the amount of 6 NE managers. In an online operation
it is therefore necessary to prevent two operating terminals or operating systems ac-
cessing one NE at the same time in a competition and for the purposes of making (e.g.
local LCT and remote NCT).
You can use the main menu items: <Security> <Access< to open a window which pro-
vides you with the following information or offers you the following configuration options:
• Message line “Current writing Element Manager”: which shows you who currently
has configuration access to the connected NE
• Message window “Current connected Element Manager”: The list of the current el-
ement managers connected to the NE
You can use the menu items: <Security> <Request Write Access> and <Security> <Re-
lease Write Access> to issue or cancel write access rights.
In the main status line (main window) you can see at the field for the access rights
whether you have read access only or whether you have both read and write access to
the NE.

3.6 Operating Mode

The (alarm signaling) operating mode of the NE governs the ability of the NE to issue
spontaneous messages to the operating terminal. However, it does not influence the
transmission functions.
The NE can assume one of two operating modes “Operation” and “Maintenance”. The
setting applies to the entire network element each time.
In the operating mode “Operation” all non-masked spontaneous alarm messages as
well as all messages about thresholds being crossed in performance monitoring are
sent to the operating terminal, displayed there and also stored in the “History Event Log”
file.

1.Vorabzug:A30808-X3580-H504-1-7620 41
MMN Maintenance
SLD/T16-2.5

In the “Maintenance” mode the NE does not send any alarm telegrams to the operating
terminal and the indication of spontaneous alarm reports on the operating terminal as
well as all messages about thresholds being crossed in performance monitoring are
suppressed. The alarm changes are stored in the “History Event Log” file. This prevents
a flood of alarms from appearing during the fault clearing measures. However, all appli-
cation functions, e.g. the configuration and the alarm interrogation are still possible.
Setting the maintenance mode does not cause any restrictions in the Bw7R signaling.
When the operating mode is changed over from “Maintenance” to “Operation” mode, the
alarm information and the configured alarm suppressions are called up once more.
The current operating mode appears in the main status line of the main window as either
“operation” or “maintenance” mode (in red letters).
To change the set Operating Mode, select the main menu items:
<NE State> <Set to Operation> or <Set to Maintenance>.

With <Set to Operation> you have the choice (in the Idle state of the NE) for two further
options:
– <Set to Default Configuration>, to set to a default configuration
– <Set to Previous Configuration>, to re-establish the previous configuration.
If the craft terminal, if it has been set for the maintenance mode of operation – and so
i as to ensure that during this period the NE outputs no alarm messages and no return
signals about alarms which have been cleared – the alarm display in the NE-UniGATE
(gateway software) user interface (UI) should be updated as follows after a change to
the “operation” mode:

In the UniGATE UI, select the NE symbol concerned, and select the following menu
commands (for operating details, see the OMN manual):
– <Symbol> <Fault> <Alarm Reset> to reset the alarm display
– <Symbol> <Fault> <Alarm Request> to interrogate the current alarm situation.
In this case, the alarm display for any operations system which is connected should also
be updated in a similar way, as appropriate.

3.7 Module Equipping

(see also the Chapter 4.2.1)
The following distinctions are made:
• Actual Equipping:
That is equipping with functional, the non-deactivated modules actually present in
the subrack when the call is made.
• Required Equipping:
This specifies the equipping of the BGT with the modules selected by the user at the
operating terminal from the specified possibilities (= possible equipping) – for EIPS1,
OIS1, OIS4/OIS4-2 and OIS16/OIS16-2 modules - with the details of an protection
switching in force as well.
For each individual module slot you can use the right-hand mouse button in the
“NE/Subrack view” to select the slot number and make your selection in the pick
list which then opens.
Required equipping is always displayed when <View> <Module View> items are
used to call up the module view on the operating terminal.

42 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

• Possible Equipping:
This specifies which of the equipping possibilities are permissible for the individual
BG slots and these are displayed as a pick list under View for each individual BG
slot. To open this list select the slot number (e.g. 402) with the right-hand mouse but-
ton.
This information is stored as a read only file (possible equipping table PET) in the
network element, activated by the SCU and made available to the operating termi-
nal.
Required equipping can be selected from a possible equipping.
The differences between a required and actual equipping are not allowed. An alarm
message of “Unavailable” causes the module location in the “Subrack view” to turn red
with this type of mis-equipping (and it may also be outlined in blue or be flashing).
Slot
n n+1 n+2 n+3
Note:
401 402 403 404
Module designations dis-
played on the module buttons
correspond to the required
A A
equipping selected.

Module button colored red and

(optionally) out-
EIPS1

EIPS1
lined in blue or
flashing

Required equipping: EIPS Empty EIPS1

Incorrect module

Actual equipping: EIPS1 Empty

EIPS1) or empty
equipped (not

Slot equipped Slot equipping

correctly incorrectly

Fig. 3.3 Slot Equipping Status

You can use the main menu items: <Window> <Update Window> to update the win-
dow being displayed.

3.8 Card Status

The current status of a module is displayed by selecting the module symbol box for it
with the right-hand mouse button under the “Module View” and then selecting the menu
items: <Information> <Card>.
For the currently equipped module - depending on the module type involved - an infor-
mation window supplies the information about the card (module) state (enabled / dis-
abled and the reason for “Disabled”), about the cross connections, the protection
switching, the OH connections and the clock bus selected etc.

1.Vorabzug:A30808-X3580-H504-1-7620 43
MMN Maintenance
SLD/T16-2.5

Card States Meaning

Enabled The card is in operation and fully functional

Disabled_Unavailable The card is not in operation

Disabled_WrongCardType The card is disabled since an incorrect card type was

used

Disabled_WrongCardVersion The card is disabled since an incorrect card version was

used

Disabled_WrongSoftware The card is disabled because of incorrect software; only

possible with the SCU

Tab. 3.5 Possible Card States

The states of all cards (modules) (except for the SCU) are suspended if the NE is in the
idle state. They are updated when the NE starts up (change from Idle to Active).

3.9 Log Records

For the continuous alarm monitoring, an operating terminal or a network management
system need not being continuously switched on for units of the SL16 series 2 fiber optic
system. All the raised alarm messages are stored in the SCU. Likewise all the already
acknowledged events are kept in log records.
After an operating terminal or a network management system has been connected with,
the user can request the saved events or alarms.

3.9.1 Log Records for the NE

The NE saves the last 100 history events and the last 100 configuration events. New
events always overwrite the oldest entries.

Interrogating Records from the NE Internal Logs

In an operating terminal view using (<View>) <Module view> select the functional sym-
bol Logs with the right-hand mouse button. The context-sensitive menu provides the fol-
lowing choice of log records:
• <NE Logs>
– <Configuration Log>:
A list of up to 100 configuration events (e.g. with details of the module, the module
slot and the date/time of the day of the configuration measures)
– <Historical Event Log>:
A list of the last maximum of 100 history events and the performance values ex-
ceeded. An history log message of this type contains information such as the
module, the module slot, the alarm name or the TCN name, the event status
(cleared/raised) and the date/time.
All the raised equipment and transmission alarms and all the alarms from the gen-
eral NE functions are stored in the Historical Event Log.
Use the “Update” button to update these lists.
Saving the log records: In the opened window select the title line and select the
items: <File> <Save As> from the main menu. Now define the path for saving the

44 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

file and confirm with “Save” command. The window contents are stored as an ASCII
file with the suffix ”.txt” and can subsequently be read with a suitable editor.
• <NE Startup Log>
Contains plain text information about the previous NE start:
up to ten items of fault information or the message “No faults”.
• <Subrack Logs>
The following three log record types are created during the NE start and are used
exclusively by the manufacturer’s service personnel for diagnostic purposes; a spe-
cial user class is reserved for their use:
– Exception Log Upload:
Contains exceptions which occur during SW operation. It is generated in the SCU
and it contains information about serious errors (e.g. the cause of resets).
– Trace Log Upload:
Generated during the normal SW operation in the SCU and may be helpful for de-
tection of errors.
Define a path and store the record.

3.9.2 Log Records for Individual Modules

These log records – like the three subrack log records listed above – can make diagno-
sis easier as with the use of complicated error patterns. In such cases you can save the
log files to a diskette and pass them on to one of the manufacturer’s service centers.
• Startup Log
This record function logs the events when the module starts up and is available for
all the modules with the exception of the SCU.
– Activation:
You can activate this log function for the module on a request by selecting the
module symbol with the right-hand mouse button in the module view using
(<View> <Module View>) and selecting the items: <Configuration> <Card> in the
context-sensitive menu. Now selecting the field “Enable Transfer Of Errorlog After
Startup” in the “Config” window and confirming your action by pressing the <Ap-
ply> button.
– Reading out the startup log:
To do this, you must have activated the function beforehand (see above).
In the (<View> <Module View>) select the module symbol with the right-hand
mouse button and in the context-sensitive menu chose the items <Upload> <Star-
tup Error Log>. You can then store the log file (on a diskette for example).
• Actual Log
This records current error information for a module.
Saving the record (on a diskette for example):
By using: <View> <Module View> select the module symbol with the right-hand
mouse button and in the context-sensitive menu chose the items:
<Upload> <Actual Error Log> and define the path for “Save”.

View
You can view these log records with the aid of the integrated viewer by calling the main
menu items: <File> <Script Configuration> and opening the log file using the symbol
bar of the window and the file name under which the user did previously store.

1.Vorabzug:A30808-X3580-H504-1-7620 45
MMN Maintenance
SLD/T16-2.5

3.10 Performance Management

The “Performance Management” monitors the line equipment for performance errors
in the order to obtain information about the transmission quality of the user data connec-
tions. The results can be used for preventive measures and to support a fault tracing
and a fault clearance.
The following performance / TCN information can be called up on the operating terminal:
• TCN list as the overview of all TCN messages (see Fig. 3.4)
• A window for the performance and the TCN messages of the individual ports (see
Fig. 3.5)
The performance information will be obtained by evaluating the B1, the B2 and the B3
bytes (with the exception of the AU4 and the protection switching information mentioned
below)
• In the Local NE:
– MS Near End:
Performance monitoring of the multiplex section between two multiplexers
– RS Near End:
Performance monitoring for the regeneration section between a multiplexer and
an adjacent regenerator or between two regenerators
– VC4 Near End:
Performance monitoring at the VC-4 level
– AU4:
Pointer information for the plesiochronous signals
– Counting the Protection Switching Events

• At the Far End:

– MS Far End:
Performance violations in the incoming signal (at the multiplexer level) are detect-
ed at the far end and are signaled back to the local NE as an REI (Remote Error
Indication) alarm
– VC4 Far End:
Performance violations in the incoming VC-4 signal are detected at the far end
and are signaled back to the local NE as an REI (Remote Error Indication) alarm
The performance evaluations are undertaken unidirectionally, i.e. independently for
each direction of the transmission.

3.10.1 TCN List

This list (see Fig. 3.4) shows detailed information about the crossed thresholds (TCN,
Threshold Crossing Notifications) for the entire network element.
Call via the main menu of the application software:
<Performance> <TCN List: file cards Current/History> items.

46 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Fig. 3.4 TCN List

The file card “Current” lists the current threshold crossing notifications (TCNs), the
“History” lists all the TCN events detected by the NE which have occurred since the
operating terminal has been in the online mode.
The History TCN list can contain up to 1000 entries.

3.10.2 Performance Message Window

Display on the Operating Terminal
For the individual traffic ports on the line side (modules OIS16/OIS16-2) and on the trib-
utary side (modules EIPS1, OIS1, OIS4/OIS4-2 and OIS16/OIS16-2) give different per-
formance and the TCN measured values can be displayed (see Fig. 3.5) for each
performance measuring point (see Tab. 3.6):

Call Performance Data

The display of the performance data can be initiated via the menu. The example is for
the calling OIS16/OIS16-2 module (working) and the container VC-4. To display this da-
ta, select the following menu items or the symbols in turn with the mouse (LM = left-hand
mouse button, RM = right-hand mouse button):
1. Main menu items: <View> <Module View> (LM)
2. Module symbol: OIS16/OIS16-2 (LM), appropriate port list is opened
3. The desired Port Symbol in the lower half of the window (RM)
4. Menu item: <Subview> (LM)
5. Container symbol: 16xAU4/VC4 (RM)
6. Menu item: <Subview> (LM)
7. The desired Container symbol (RM)
8. The menu items: <Performance> <VC4 Near End> or <VC4 Far End> or <AU4>
(LM)
9. One of the file cards: “Current”, “Previous 15min” or “Previous 24h” (LM)
10. Decide whether the Performance Monitoring should be performed or not
(Enable PM) and select the desired parameters (see section: “Activation of moni-
toring” below).

1.Vorabzug:A30808-X3580-H504-1-7620 47
MMN Maintenance
SLD/T16-2.5

Fig. 3.5 Performance Window, Using the MS Port of an OIS16/OIS16-2 Module as

an Example

Explanations for the performance windows

• “Current” file card: lists current Performance values.
– The “Current” field displays values for the current 15-minute and the current
24-hour time interval for the performance parameters BBE, ES, SES and UAS
(explained below) and for the AU4 function block values (+PJE/-PJE).
– In the “TCN 15min” field the upper and lower limit values for the number of 15-
minute performance events (BBE, ES and SES) can be configured and the mon-
itoring of these thresholds can be activated. If the upper threshold is crossed the
corresponding field is colored red and a TCN message is entered in the TCN list
(see Fig. 3.4). A TCN 15min message is only cancelled again if the lower thresh-
old is not crossed for at least 15 minutes.
Exception: with function block AU4 only parameters +PJE/-PJE are displayed for
the 15-minute interval, threshold values cannot be defined.
– As part of “TCN 24h” upper thresholds can be configured for the number of 24-
hour performance events BBE, ES and SES and monitoring of these threshold
values activated. If the upper threshold is crossed the corresponding field is col-
ored red and a TCN message is entered in the TCN list (see Fig. 3.4).

48 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

A “TCN 24h” message is not canceled again until a delete message is present
at the end of the 24-hour interval.
Exception: with the AU4 function block only the parameters +PJE/-PJE are dis-
played for the 24-hour interval, threshold values cannot be defined.
• “Previous 15min” file card: The list contains the performance data of the previous
sixteen 15-minute measurement intervals for the transport function.
• “Previous 24h” file card: The list contains the performance data of the previous
three 24-hour measurement intervals for the transport function.

Parameters monitored
The following parameters are determined for the regeneration section, for the multiplex
section and for the VC4 monitoring points of the transport functions:
• BBE (Background Block Error):
Counts within the time interval (15min/24h) all the errored blocks which are not clas-
sified as SES
• ES (Errored Seconds):
The number of the seconds in a time interval (15min/24h), in which – during the pe-
riod of one second in each case – at least one block error or a “one defective second”
was recognized
• SES (Severely Errored Seconds):
The number of the seconds in a time interval (15min/24h), in which – during the pe-
riod of one second in each case – 75% or 50% or 30% (depending on the SDH layer)
errored blocks are reached or exceeded or a “one defective second” occurred.
• UAS (Unavailable Seconds):
The seconds with an unavailable time (UAT).
The UAT starts after 10 consecutive SES events and ends after 10 consecutive sec-
onds without an SES event (these 10 seconds are not included in the count).
The TMP column displays the time which has already elapsed in the time interval con-
cerned (15min/24h).
Special case to TMP values for “Previous 15min”:
i If within one 15 minutes time interval the performance management of one layer is set
to enabled for the first time, for both, the near end and the far end, only one TMP val-
ue for the “Previous 15min” is available (for near end and far end) at the end of this
15 minute time interval. This value is assigned to the window in which the performance
management was enabled earlier (in the actual 15 minutes).
However the TMP values in the “Current” window are always displayed correctly. Also
counting the fault events (BBE, ES, SES, ...) is not influenced by this. In each case this
values are determined and displayed correctly.

For the protection switching functions Multiplex Section Protection (MSP):

Link, Ring and Module Protection Switching and the Sub-Network Connection Protec-
tion (SNCP) the following value is determined:
• PSC (Protection Switch Count), see Fig. 3.6:
The number of the protection switchings in the own NE (near end value) from the
working channel to the protection channel and vice versa. The TCN and UAT mes-
sages are not provided for this eventuality.

1.Vorabzug:A30808-X3580-H504-1-7620 49
MMN Maintenance
SLD/T16-2.5

Fig. 3.6 Performance Window for MSP Protection Switching

The positive and negative pointer values required for adapting the receive signal to the
system clock will be determined for the AU-4 monitoring points of the transport func-
tions:
• –PJE (Pointer Justification Events Negative):
Accumulated negative pointer values outgoing; only for the AU4 (in the regeneration
section)
• +PJE (Pointer Justification Events Positive):
Accumulated positive pointer values outgoing; only for the AU4 (in the regeneration
section)
Explanation:
A block (in the text above) is defined as an STM-N signal for the regeneration section
(e.g. an STM-16 frame corresponds to a block), in the multiplex section as an STM-N
signal it is considered as N blocks (e.g. one STM-16 frame comprises sixteen STM-1
blocks).

Activation of monitoring
The following monitoring activities can be switched on and switched off in the perfor-
mance windows:
• Monitoring the Performance Parameters (“Current”) using the selection field:
“Enable Performance Monitoring”
• Monitoring of the Parameters for the “TCN 15min”:
Using separate settings for the individual parameters
• Monitoring of the Parameters for the “TCN 24h”:
Using separate settings for the individual parameters
• Monitoring of the UnAvailable Times (TCN UAT)
Confirm your choice with the <Apply> button.
The <Update> button will refresh the users display.

Performance Monitoring Points

The Tab. 3.6 contains a list of the near-end performance monitoring points (without
monitoring the protection switching events) and the supported (marked with an “X”) per-

50 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

formance parameters in the “Current” performance window. For an explanation of the

parameters see above.

Performance
Performance monitoring point (BBE, ES, SES, TCN TCN TCN
UAS) “Current” “Current” “Current”
“Current” 15min 24h 15min/24h
(+/-PJE)
15min 24h

OIS16-2 STM16, MS X X X X –

STM16, RS X X X X –
VC4 X X X X –

AU4 – – – – X

OIS16 STM16, MS X X X X –

STM16, RS X X X X –

VC4 X X X X –
AU4 – – – – X

OIS4-2 STM4, MS X X X X –

STM4, RS X X X X –

VC4 X X X X –

AU4 – – – – X

OIS4 STM4, MS X X X X –

STM4, RS X X X X –

VC4 X X X X –

AU4 – – – – X

OIS1 STM1, MS X X X X –

STM1, RS X X X X –

VC4 X X X X –

AU4 – – – – X

EIPS1 STM1, MS X X X X –

VC4 X X X X –

AU4 – – – – X

X ... the specified function is supported

Tab. 3.6 Performance-/TCN-Monitoring for the Individual Ports

(Example: Near End Performance)

Message to the Operating Terminal

The performance parameters are determined for two time intervals and displayed on the
operating terminal:
• 15min performance data
• 24h performance data
The 15min performance data are automatically notified to the SCU after every 15min-
synchronization pulse. The SCU obtains the 24h performance data by summation from
the 15min performance data.

1.Vorabzug:A30808-X3580-H504-1-7620 51
MMN Maintenance
SLD/T16-2.5

The performance management is undertaken independently for each direction of the

transmission (unidirectional).

3.11 Protection Switching

In many cases, the protection switching equipment ensures that when faults and failures
occur as well as in the case of impermissible deterioration of the transmission quality,
the traffic can be switched over to the protection path and the operation can thereby con-
tinue to be maintained. This gives improved availability.
Alarms which trigger the protection switching are signaled briefly but disappear again
when data transmission can be continued uninterrupted on the protection path.
For details of the protection switching:
see Chapter 5 in the “Technical Description” TED.

3.11.1 Line Protection Switching

The line protection switching described below is available in two modes:
• Revertive mode:
After a transmission fault, which has occurred and has been rectified, there is an au-
tomatic switchover to the path which was used for the data transmission before the
fault occurred.
• Non-Revertive-Mode:
After a transmission fault, which has occurred and has been rectified, the operation
will be continued on the protection switching path.

3.11.1.1 (1+1) Line Protection Switching for STM-16 Line Signals

If a (1+1) line protection switching (= Linear Multiplex Section Protection MSP) is in
force, the same data signal will be transmitted simultaneously on the two optical fibers
on a multiplex section from one add/drop or from a terminal multiplexer to the partner
one (there can be regenerators between the two). For faults on the transmission link, the
data signal received better will be selected in each case. In this case one of the following
two modes of operation can be selected:
• Unidirectional or single-ended: The selection switches on the receive sides of the
outwards and return directions can have different settings (e.g. line 1 is selected for
the outwards direction and the line 2 for the return direction).
• Bidirectional or dual-ended: The receive-side selection switches select the same
line for both the outwards and the return direction (either line 1 or line 2). The “Syn-
chronization” process is undertaken using a communications protocol which is
transmitted as an overhead information.

52 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Protection line

For bidirectional / dual-ended:

Linkage via communications protocol
Switching matrix

Fig. 3.7 (1+1)Line Protection Switching, Switched to Protection Line

Switchover criteria for (1+1) line protection switching:

• Requirements of a craft terminal or of a TMN (OS)
• Signal Fail (SF)
• Signal Degraded (SD), the signal has exceeded the specified bit error rate threshold
• Only in bidirectional mode: The far end switchover request via the K1/K2 bytes
The alarms SF and SD will be monitored at any SDH interface.

3.11.1.2 (1:1) Line Protection Switching for STM-16 Line Signals

If a (1:1) line protection has been configured on the line side (only possible with config-
uration type SLT), then in a fault-free operation the protection line is used (extra traffic,
low-priority transmission) for the data transmission in addition to the transmission of the
main traffic. If a fault occurs, the main traffic on the send and receive side are switched
over to the protection line, the subordinate extra traffic can then no longer be transmit-
ted.
For the switchover criteria, similar to a (1+1) line protection switching, see Chapter
3.11.1.1. In addition, the K1/K2 bytes as incoming switchover requests from a distant
network element should be taken into account.

AIS AIS
No fault: Extra traffic
Fault: Protection line
Switching matrix

Fig. 3.8 (1:1) Line Protection Switching, Switchover to Protection Line

3.11.1.3 (1+1) Line Protection Switching for Tributary Signals

A (1+1) line protection on the tributary side is available for the STM-1, the STM-4 and
the STM-16 signals in the unidirectional/single-ended and bidirectional/dual-ended op-
erating modes (for explanation see Chapter 3.11.1.1).

1.Vorabzug:A30808-X3580-H504-1-7620 53
MMN Maintenance
SLD/T16-2.5

For the switchover criteria see 3.11.1.1.

3.11.2 Bidirectional Self-Healing Ring Protection

For an interruption in a ring-type network the bidirectional self-healing ring protection
(BSHR) can be used to direct the STM-16 data signals of the line side at both ends of
the interrupted multiplex section via a protection path in the reverse direction and thus
to the desired destination.
Protection criteria for a ring protection switching:
• Requests from the craft terminal or from the TMN (OS)
• Signal fail (SF) in the ring; in a 4-fiber ring signal the fail on the span as well
• Signal degraded (SD), the transmission signal in the ring has exceeded the specified
bit error threshold; in a 4-fiber ring also the impermissible signal degradation on the
span
• Requests from a remote network element (via K1/K2 bytes)
The ring protection switching is always revertive, after a transmission fault has been rec-
tified, the system switches back to the transmission path used before the fault occurred.

3.11.2.1 2-Fiber Self-Healing Ring Protection (BSHR-2)

For an interruption in a two-fiber ring the optical fiber pair in the reverse direction will be
used as the protection path. Since this also carries the payload in a normal operation,
the transmission capacity must be reserved for the protection switching purposes (eight
channels of STM-16).

West East West East

D C

A B

STM-16 STM-16

East West East West

8 STM-16 channels for payload

8 STM-16 channels for protection switching
Switching matrix

Fig. 3.9 2-fiber Self-Healing Ring Protection,

Interruption between Network Elements A and B (Example)

54 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

2-fiber self-healing ring precautions can be operated with and without extra traffic.
For BSHR/2-extra: West (East) extra traffic is set to contiguous concatenated and East
i (West) interface having FEC switched on.
This would be no problem but is prevented by the new preconditions.

3.11.2.2 4-Fiber Self-Healing Ring Protection (BSHR-4)

In a 4-fiber ring (with two optical fiber pairs) the protection switching can be provided for
both the interruptions of a span between two adjacent NEs of the ring and for the inter-
ruptions to the ring (working and protection path interrupted). The protection switching
is effective in both of the directions (west and east) of an NE.

West East West East

D C

Working
line

A B

STM-16 STM-16

STM-16 STM-16

East West East West

when operating
Switching matrix Protection path without traffic

Fig. 3.10 4-Fiber Self-Healing Ring Protection,

Interruption to a Span (Example)

1.Vorabzug:A30808-X3580-H504-1-7620 55
MMN Maintenance
SLD/T16-2.5

West East West East

Protection Working

Working Protection

Protection

Working

East West East West

Switching matrix

Fig. 3.11 4-Fiber Self-Healing Ring Protection,

Interruption of the Ring (Example)

3.11.3 Card Release Switching (CRS)

Whereas the line protection and the ring protection mainly take account of errors on the
transmission link, the card release switching also takes in the faulty optical interface
modules. If one of these OIS modules signals a hardware error, the card release switch-
ing automatically switches using the switching matrix (module SNL) to the “Protection”
OIS module.
The card release switching is active for the following types of protection:
• (1+1) and (1:1) line protection switching
• 2-fiber self-healing ring protection (BSHR-2)
• 4-fiber self-healing ring protection (BSHR-4)

3.11.4 Subnetwork Connection Protection

With a (1+1) subnetwork connection protection (SNCP) the same VC-4 data signal
is transmitted simultaneously over the two different subnetwork connections to the dis-
tant end. The signal which is more worthy of being received will be selected at this end.
The two connections can – depending on the configuration – lead using the same optical
fiber (on different channels) or the same fiber bundle or the separate cables / on sepa-
rate routes to the destination.
With the subnetwork connection protection in the single-ended / unidirectional operating
mode (independent path selected for both transmission directions) and in the non-rever-
tive mode (after the fault has been rectified the protection path will continue to be used)
are employed.

56 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Possible subnetwork connection protections:

• Line/line-subnetwork connection protection
• Line/tributary-subnetwork connection protection
• Tributary/tributary-subnetwork connection protection
The protection routes must be planned and configured from the start to the end of the
relevant VC-4 path. In the line equipment the VC-4 protection connection is configured
during the configuration of the switching matrix (module SNL).
Criteria for the initiating of a protection switching process.
• Switchover request from the operating terminal or the TMN (OS)
• Trail Signal Fail (TSF)
• Trail Signal Degraded (TSD)
• ISDH signal fail: Internal error of the module SNL

3.11.5 Card Protection Switching

The protection cards (modules) can be equipped in a network element for the following
modules so that if a module fails the operation can be continued with the protection mod-
ule:
• Module SNL:
(1+1) protection switching
• Module CLL:
(1+1) protection switching
• Modules OIS16, OIS16-2 on the line side:
For the STM-16 signals;
Protection switching of the OIS-16/OIS16-2 modules only in the connection with line
(multiplex section) and/or in the ring protection switching MSP; see also CRS, Chap-
ter 3.11.3
• Modules OIS1, OIS4, OIS4-2, OIS16 and OIS16-2 on the tributary side:
For the STM-1, the STM-4 and the STM-16 signals;
in conjunction with (1+1) protection switching.
• Modules EIPS1:
(1:n) protection switching for the 140 Mbit/s / STM-1 electrical interfaces (not sup-
ported in NE type SLT16BC). For a number of the EIPS1 working modules there is
a shared EIPS1 protection module available, to which the protection switching is
possible if a working module fails.
The OIS1/OIS4/...-2/OIS16/...-2 modules may be working with a OB or OP module. In
case Protection is used also this way must have a OB or OP module combined. The card
protection switching of the system switches automatically to the protection route if the
working OIS xx module combined with the working and faulty OB/OP module fails.
Switching over, thus, is initiated primary from the OIS xx module getting a faulty input
signal from the OP or a control signal of the malfunctioning OB or by a signaling back of
a bad receiving from the partner NE on the line.
Switchover criteria for card protection switching:
• For SNL:
Internal alarm messages LOF (loss of frame) and ISU-AIS (protection switching sig-
nal of the internal SDH switch unit in module EIPS1)
• For CLL:
See Chapter 3.13

1.Vorabzug:A30808-X3580-H504-1-7620 57
MMN Maintenance
SLD/T16-2.5

• For the OIS1/OIS4/...-2/OIS16/ ...-2:

As listed in the Chapter 3.11.1.1, this operation cannot be influenced via the operat-
ing terminal however
• For EIPS1:
Switchover requirements from the operating terminal and also card failure messag-
es from the protection and working modules.

3.12 Redundant Power Supply

3.12.1 Supply Voltage

In the upper part of the rack, in what is known as the rack terminal panel, there are two
blocks with circuit breakers to which one operating voltage source and one protection
source - coming from the O&M center - can be connected. For each subrack there is a
separate lead from the circuit breaker for the operating and the protection voltage to the
power supply connectors UBAT1 and UBAT2 in the terminal panel of the subrack. From
there two separate voltages (NUBAT1 and NUBAT2 together with PUBAT) are fed, di-
ode-decoupled via backplane connections to the individual module connectors and from
there via a fused connection to the power supply of the individual module in each case.
In each subrack the voltages NUBAT1 and NUBAT2 are monitored by the SCU.
If one supply voltage fails a Bw7R-”B” alarm is generated, the yellow LED on the SRAP-
PI lights for deferred alarms, a B alarm is issued to the light signal equipment LZE and
a ZA(B) messages is issued to the central service observation unit ZBBeo. For a failure
of the redundant power supply the operating terminal displays the alarm “2nd Power” in
the “Module view” under the Subrack symbol. You can activate/deactivate this monitor-
ing in the “Module view” by selecting the “Subrack” symbol with the right-hand mouse
button, choosing the menu item: <2nd Power Supply> and marking the “Monitoring of
second power supply” field.
If both power supplies are failing the NE is no longer operable. Provided that an external
signaling voltage exists, a Bw7R-”A” alarm will however be generated, the red LED for
the critical alarms will light on the SRAP-PI, an A-alarm will be sent to the light signal
equipment LZE and a ZA(A) alarm signal will be presented to the central service obser-
vation.
The separate signaling voltage fed in from an external source for the SRAP-PI panel is
i not duplicated.

3.12.2 LED Power Supply

With the exception of the external CLA box (located in the rack terminal panel), the CS4,
EBSL, LTU and PSUTP modules beside all other modules generate an auxiliary voltage
(ULED) and feed this voltage in, decoupled by diodes, onto the common ULED bus of
the backplane board. Via this bus all the module LEDs will be supplied with power. This
ensures that each hardware fault is displayed even if the power supply for a module fails.

3.13 Clock Source Changeover

To increase system availability two CLL modules can be operated simultaneously in one
network element. The internal system clock generators T0, on the two modules CLL,
synchronize with each other and ensure that there is a mutual protection switching. One

58 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

clock bus of the two CLL modules delivers (twice) clock signals 155.52 MHz, 6.48 MHz,
2 kHz and 1 Hz to the individual modules of the NE. However each module only ever
selects one of the clock sources (CLL), basically the one with the known best or next
best quality.
A changeover takes place in one of the situations mentioned:
• If a fault occurs in the VCO of one of the two CLL modules, the faulty module takes
over the VCO signal of the other module (MTG, Multiplexer Timing Generator Pro-
tection)
• The modules monitor all their clock inputs. If one of the T0 system clocks of a clock
source fails, the connected modules automatically changeover to the clock interfac-
es of the other CCL module.
• If an external CLA box is used and the CLA fails, the incoming clock signal(s) as
clock source(s) are protection switched by the SEC function to the next available
clock with an equal (if present) or to the one with the next best quality.
A “Do not use for synchronization” message is available in the events list for the clock
channel(s) used via the CLA. If the outgoing clock signals using the CLA are also
being involved, the partner NE(s) receiving the clock signals also generates the
above message for the appropriate channels.

1.Vorabzug:A30808-X3580-H504-1-7620 59
Maintenance MMN
SLD/T16-2.5

4 Display of Alarms at the LCT Operator Inter-

face
You will find a more detailed description of the operating terminal interface (application
i software of the NE) in the OMN, Register 1, OMN:SL.
You can also obtain considerable assistance from the help system on the operating ter-
minal under the menu item: <Help>. You can obtain a context-sensitive help by pressing
the “F1” key.

Listed below are a number of resources used by the operator interface (application soft-
ware of the NE) and of the operating terminal to present information which is of rele-
vance for maintenance tasks. These are followed by a description of alarm views and
the ways in which they can be influenced – including alarm suppressions – as well as
notes on saving alarms.

4.1 The Main Window

The main window is the topmost view level of the NE application software. The main
menu bar in this window can be used to open further windows.

Title Bar
Main Menu
Bar

Alarm List

Main Status Bar

Fig. 4.1 The Main Window with a View of the Alarm List (Example)

The alarm list shown as an example in Fig. 4.1 can be called up using menu item
i <Fault> <Alarm List>. You will find more detailed information about this in Chapter 7.1.2.

1.Vorabzug:A30808-X3580-H504-1-7620 59
MMN Maintenance
SLD/T16-2.5

4.1.1 Main Menu Items of Relevance to Maintenance

(see Fig. 4.1)

• Menu item: <View>

In the main window, the following three views of the network element can be set:
– Module View, see also Fig. 7.2
Menu items: <View> <Module View>.
Symbolic view of the subrack equipped with modules and their coordinated slot
numbers (Required Equipping). The lower part of the window shows the associ-
ated ports for the traffic-relevant modules (EIPS1, OIS1, OIS4/OIS4-2,
OIS16/OIS16-2, OB, OP) – visible after a module symbol is selected.

– Traffic View, see also Fig. 7.4

Menu items: <View> <Traffic View>.
Overview of the traffic functionalities of a network element. Each functional sym-
bol represents a specific traffic of transmission functionality. The lower part of the
window shows the individual ports of the function symbol selected in each case.
Black colored display fields “A” symbolize alarm suppressions which have been
set (see also Chapter 4.4.1 and 4.2). Display field “T” for TCN appears in red if
there have been one or more occurrences of performance thresholds being
crossed whereas black means TCN monitoring switched off and wheat means
switched on (see also Chapter 4.2.2 and 4.2.3).
– Module view, see also Fig. 7.10
Menu items: <View> <Module view>.
This window supplies information on important functionalities of the NE. Each
module function symbol has a context sensitive menu which can be opened by
clicking with the right-hand mouse button. A number of these symbols can indi-
cate alarms by being colored red. Alarm suppressions set for module functions
can be recognized from the black display field “A” in the symbol.
– Module function symbol “Protection”: The context-sensitive menu item: <Man-
agement> shows the protection switching possible on the basis of the existing
module equipping and the protection switching actually configured and it also al-
lows new protection switching to be configured and existing protection switching
to be canceled.
– Module function symbol “SEC”: The context-sensitive menu items: <Fault>
<Communication Alarms> supplies the current alarm window for functional unit
clock generation, with <Fault> <Acknowledge> items you can acknowledge the
corresponding alarms.
– Module function symbol “OHF-IF”: with context-sensitive menu item: <Acknowl-
edge> you can acknowledge all alarms of the OH interfaces. Menu item: <Sub-
view> opens the window Overhead Interfaces. You can use the right-hand mouse
button to select the symbol for one of the two channels Channel 1 or Channel 2
(G.703 or TIF). Context menu items. <Fault> <Communication Alarms> is used
to call the alarm window of the selected overhead channel, with <Fault> <Ac-
knowledge> items you can acknowledge the alarms of the relevant overhead
channel. (Only a “Configuration” context menu is assigned to the symbol Pbx
interface.)
– Module function symbol “Subrack”: Context menu items: <Fault> <Communica-
tion Alarms> is used to call the window NE alarm (clock alarms, bus alarms,
alarms of the redundant power supply, ...), <Fault> <Detailed alarm Informa-

60 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

tion> supplies detailed error information about HW connections, with <Fault>

<Acknowledge> items you can acknowledge these alarms.
Under the <2nd Power Supply> item you can activate or deactivate the monitor-
ing of a redundant power feeder.
• Menu item: <Symbol> (see also Chapter 4.2)
After you select a symbol (module, function, port symbol, ...) you are offered an as-
sociated context-sensitive menu; this is an equivalent alternative to selecting a sym-
bol with the right-hand mouse button.
• Menu item: <NE State>
You can use the submenu items to place the NE in the idle state (<Set to Idle>), in
the active state (<Set to Active>), you can set the state for alarm message signaling
to “normal mode” (<Set to Operation>) or “maintenance” (<Set to Maintenance>;
the NE does not send any more alarm messages to the operating terminal).
(After <Set to Active> a restart has to be initiated by a double mouse click to the NE
symbol in NE-UniGATE.)
• Menu item: <Fault>
– Submenu item: <Alarm List>
Collective view of all alarms both the current alarms and the previous alarms with
various selection criteria with regard to alarm severity and alarm acknowledg-
ment. See Chapter 7.1.2.
– Submenu item: <Acknowledge All>
Acknowledgment of all current NE alarms.
– Submenu item: <Persistency Time>
Window to configure the period during which an error message must at least be
present in order to be displayed as an alarm (Alarm Raise Delay) and also the
minimum duration during which an error message must have disappeared in or-
der to clear the alarm (Alarm Clear Delay).
• Menu items: <Performance> <TCN List>
see Chapter 3.10.1.
• Menu item: <Security>
– Submenu item: <Access>:
The window “Access Management” gives you information about configuration
access to a connected NE and offers you configuration options for NE access
(see Chapter 3.5).
– With the submenu items: <Request Write Access> and <Release Write Ac-
cess> you secure configuration access to the NE or make do with read access
only.
• Menu item <Options> <Settings>, see Fig. 4.2.
In the window area “Alarm Severity Threshold” you can define the severity (warn-
ing, minor, major) from which alarms are to be shown at the operating terminal in-
terface (the alarm type critical is currently not in use). Alarms which are below the
set severity level are not displayed.
Under “Open at Startup” for example you can define with the selection field “Alarm
List” that the (entire) alarm list will always be displayed at the operating terminal on
startup; the same applies to the TCN list.
With selection field “Alarm Severity Threshold” (in the “Save on Exit” area) you
can determine whether the chosen priority level for alarms is to be retained after the
application is closed or not.
Selecting the “Alarm Flash” field has the effect of making symbols with alarms flash
(and be colored red), otherwise they are outlined in blue.

1.Vorabzug:A30808-X3580-H504-1-7620 61
MMN Maintenance
SLD/T16-2.5

Fig. 4.2 Settings using the Main Menu Items: <Options> <Settings>

• Menu item: <Window>

Using the submenu item: <Update Window> you can have the display of the cur-
rently active window updated, with the <Update All Alarms> item the display of all
alarm messages.

4.1.2 Areas of the Main Window

The upper area of the actual main window represents that window to which the current
menu item that you have selected is assigned.
The lower area of the main window is used to display event messages in text form.

4.1.3 Main Status Bar

Acknowledged alarm
Alarm unacknowledged alarm NE state
status field alarm not shown in the symbols Access rights
Status field NE signaling status Status for data
transfer,
data semaphore

Fig. 4.3 Main Status Bar in the Main Window

The footer bar of the main window, called the main status bar, supplies information such
as that described below (from left to right):
• A status field is used for purposes such as notifying “Alarminfo incomplete” (in
red) if not all alarm information is available after the application software has started
up. If you see this message, update the alarm view via the main menu items:
<Window> <Update All Alarms>.

62 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

• In an alarm status field up to four (LED) symbols can show NE alarms of different
severity as a collective message. See Tab. 4.7.
The view depends on the settings made in the main menu items: <Options> <Set-
tings: Alarm Severity Thresholds> (see Chapter 4.1.1). An LED symbol with a
cross through it in the alarm status field indicates that the signaled alarm is below
this set alarm severity threshold and will thus not be signaled by the module or func-
tional symbol.
A blue frame around an LED symbol indicates one (or more) alarm(s) which has
(have) not be acknowledged.
• A display field for NE signaling status can display the following messages:
operation: the NE is supplying alarm information
maintenance (in red): the NE was placed in the maintenance state, i.e. it is not sup-
plying any spontaneous alarm messages
Overload (in red): Overload in NE-internal telegram traffic, messages can be lost.
• The field NE state distinguished between
active: all NE functions are available and
idle: all NE functions are blocked because of inconsistent data or as a result of a
menu setting: <NE State> <Set to Idle>.
• The field for access rights shows you whether you have read/write rights or just
read rights.
• The symbolic LED “Status for data transfer” = data semaphore (in the lower right
corner) is green when valid data is present or red if the NE is transferring data to the
operating terminal.

4.2 Symbols at the Operator Interface

Below is a summary of the alarm-relevant characteristics of these symbols.

4.2.1 Module Symbols

The module view - using the main menu items: <View> <Module View> – shows the
module slots in the required equipping. See also Fig. 7.2.
A module symbol is present for each inserted module.
“Slot” button for setting required module equipping

409

Alarm suppression
OIS16/16-2 (in MSP)

Module button
Module name
and - if applicable - protection mode

Fig. 4.4 Elements of the Module Symbol (Using the OIS16/OIS16-2 as an Example)

If you select the “Slot” button with the right-hand mouse button, you will be given a con-
text-sensitive menu with the equipping options from which you can chose the desired
equipping. With traffic-carrying modules you can also prepare protection switching ac-
tions via an additional choice.

1.Vorabzug:A30808-X3580-H504-1-7620 63
MMN Maintenance
SLD/T16-2.5

If the choice that you make does not match the current equipping of the subrack, the
module button turns red and flashes or is outlined in blue (depending on its default set-
ting).

Alarm display
Spontaneous equipment alarm messages for the module are indicated by the module
button turning red and – if you have made this setting in menu items:
<Options> <Settings: Alarm Flash> – by the module button flashing, otherwise by a
blue outline to this module button.

Alarm interrogation / alarm acknowledgment

Select the “Module button” with the right-hand mouse button, which will give you
two submenu items contained in the menu “Fault”:
• <Alarms>:
opens the "Fig. 4.5 Alarm Window (Example Showing Equipment Alarms)" of the
relevant module which lists details for all equipment alarm message possible for this
module (the listing does not contain any transmission alarms).
For an existing alarm on the left of the window in the line for the alarm concerned
there appears an LED symbol in the identifying color for the severity of the relevant
alarm: critical (red LED; not used in this version), major (orange LED), minor (yellow
LED) and warning (blue LED). A blue outline around the LED symbol means that this
alarm has not yet been acknowledged.
In the alarm window you can also set/reset suppressions for individual alarms of this
module (by selecting the field “Suppression” and the <Apply> button).
When you select the line for an alarm in the alarm list with the right-hand mouse but-
ton, you can make the choice from a context-sensitive menu for this individual alarm
between <Acknowledge>, acknowledging the alarm and between <Set Suppres-
sion> and <Remove Suppression>, setting and canceling the alarm suppression
(confirm with <Apply> button).

☞ See also Chapter "4.4 Effect of the Alarm Display at the Operating Termi-
nal".

Fig. 4.5 Alarm Window (Example Showing Equipment Alarms)

• <Acknowledge>:
With this menu item you can acknowledge all equipment alarms of a module.

64 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Displaying alarm suppressions

Display field A (see Fig. 4.4) is used to display alarm suppressions for equipment
alarms of this module (however not for any alarm suppressions for transmission alarms
set in this module).

Color of field “A” Meaning

black at least one equipment alarm suppression is set for the module

wheat no equipment alarm suppression is set for the module

Tab. 4.1 Display Field “A” for Alarm Suppressions

A suppression set for an equipment alarm prevents an alarm message to the operating
terminal if a corresponding error event occurs. The module button thus does not turn red
nor does it flash (or is outlined in blue).

4.2.2 Functional Symbols

T STM16 A

a) Functional symbol STM16 of Traffic View

SEC+
A

b) Functional symbol SEC of Module view

STM16 16xAU4/VC4+
T A T A

c) Functional symbols of window Traffic Flow (from Traffic View)

A = Indicator for alarm suppressions

T = Indicator for Performance Threshold Crossing Notifications (TCN)

Fig. 4.6 Functional Symbols (Examples)

The functional symbols are used in the various views:

• Traffic View:
To show a specific transmission or a traffic functionality (e.g. STM16 in Fig. 4.6 a)
• Module view:
To show a module function of the NE (e.g. SEC = SDH equipment clock, a functional
symbol for clock generation; see Fig. 4.6 b)
• Subviews:
To represent specific functional units.
For an example (see Fig. 4.6 c):
Using the main menu items: <View> <Traffic View>, selects the functional symbol

1.Vorabzug:A30808-X3580-H504-1-7620 65
MMN Maintenance
SLD/T16-2.5

STM16 and click on a port symbol in the lower area of the window with the right-hand
mouse button. After selection of the “Subview” a “Traffic Flow” window is dis-
played which contains one or more of the functional symbol(s) which in their turn
represent the traffic processing from the line interface (termination point) up to the
relevant cross connect termination point.
After a functional symbol is selected with the right-hand mouse button a context-sensi-
tive menu opens; in a number of cases there can be a further view level assigned in-
between.
Functional symbols of the Traffic View can also be shown in gray. This occurs if the cor-
i responding module in the module view (using the module slot button) was configured
as equipped but is not in its intended slot in the NE.

The module functional symbol SEC can be shown in yellow or gray after the power sup-
i ply is switched on in the NE state “Idle” and in the NE signal state “maintenance”.
After the change to the “Active” state the gray colour turns to yellow (if there are no
faults).

Alarm display
Alarms which are detected in a functional unit turn both the functional symbol assigned
to them and the higher-ranking port and/or the functional symbols red. Until it is acknowl-
edged the red symbol flashes or has a blue outline – depending on the setting made in
the main menu items: <Options> <Settings: Alarm Flash>.

Alarm interrogation / alarm acknowledgment

• Alarm interrogation on functional symbols of the Traffic View (described using the
STM16 as an example):
Using the main menu items: <View> <Traffic View>, selects the alarm signaling, the
red functional symbol (here: STM16) and click in the lower area of the window with
the right-hand mouse button on the (red) port symbol which is signaling the alarm.
After the <Subview> item is selected a Traffic Flow window appears. Click on the
(red) functional symbol which is signaling the alarm using the right-hand mouse but-
ton and it will then provide you with two submenu items contained in the menu
“Fault”:

– <Alarms>:
Opens the alarm window for the selected functional symbol which lists the details
for all the possible transmission alarm messages for this functional unit (this win-
dow does not contain any equipment alarms!). On the left of the window, in the
line for the alarm concerned, there appears an LED symbol in the identifying co-
lour for the severity of the relevant alarm:
Critical (red LED; not used in this version),
Major (orange LED),
Minor (yellow LED) and
Warning (blue LED).
A blue outline around the LED symbol means that this alarm has not yet been ac-
knowledged.
In the alarm window you can also set/reset suppressions for the individual alarms
of this functional unit (by selecting the field “Suppression” and clicking on the
<Apply> button).
Using the selection fields "No Alarm Report" you can define whether the NE may
signal alarms for the activated line or the ring protection switching.

66 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

When you select the line for an alarm in the alarm list using the right-hand mouse
button, you can make the choice between a context-sensitive menu for this indi-
vidual alarm or the <Acknowledge> item, acknowledging the alarm and between
<Set Suppression> or <Remove Suppression>, setting or canceling the alarm
suppression (confirm with the <Apply> button).

☞ See also the Chapter:

"4.4 Effect of the Alarm Display at the Operating Terminal".

– <Acknowledge>:
With this menu item you can acknowledge all the transmission alarms of this func-
tional unit.
• Interrogation of the transmission alarms in the “Module View”:
In a module with the traffic functionalities (e. g. the OIS16/OIS16-2) you can also
recognize a transmission alarm which was detected in this module using the <View>
<Module View> items companioned by a red port symbol in the lower window area
after you have selected the module button (here: OIS16/OIS16-2). Further proce-
dures are as described above in this section under the “Alarm interrogation on
functional symbols of Traffic View” (“... click in the lower area of the window with
the right-hand mouse button on the (red) port symbol signaling the alarm....”).
• Alarm interrogation at the module functional symbols of the “Module view”:
In this view only the symbols SEC, OH-IF and Subrack can signal alarms.
– For an interrogation select the (red) symbol signaling the alarm (e.g. SEC) with
the right-hand mouse button, select the menu items: <Fault> <Communications
Alarms> which causes the associated alarm window to open. Details for the dis-
play in the alarm window area are as described above.
– You can use the menu items: <Fault> <Acknowledge> to acknowledge all the
alarms which are assigned to this module functional symbol.
For alarms of the symbol OH-IF there is another view level inserted in-between.

Display of alarm suppressions

Field A in functional symbols is used to show suppressions which have been set
– For the transmission alarms in the “Traffic View” as well as
– For those alarms of the module functions in the Module view, for which a sensor is
present in the assigned functional unit.

Color of field “A” Meaning

black at least one alarm suppression is set for the functional symbol

wheat no alarm suppression is set for the functional symbol

Tab. 4.2 Display Field “A” for Alarm Suppressions

TCN display
Field T is used for performance monitoring. It is employed for traffic functional symbols.

Color of field “T” Meaning

red the set performance thresholds were exceeded

black at least one TCN monitoring is switched off

Tab. 4.3 TCN Display Field “T”

1.Vorabzug:A30808-X3580-H504-1-7620 67
MMN Maintenance
SLD/T16-2.5

Color of field “T” Meaning

wheat complete TCN monitoring is activated

Tab. 4.3 TCN Display Field “T”

If a functional unit does not contain an alarm sensor, then understandably no red alarm
i color is available for the functional symbol nor can any window be called up using the
context-sensitive menu and no field A is available to display alarm suppressions nor
field T for indicating TCNs (e.g. with the functional symbol CC (Cross Connections), in
the “Traffic View”).

4.2.3 Port Symbols

The port symbols used in the “Traffic View” and – for the modules which carry traffic
such as the OIS1, the OIS4/OIS4-2, the OIS16/OIS16-2, the EIPS1, the OB and the OP
– in the “Module View” as well. There are symbols available for the electrical and optical
ports.
Optical port Electrical port

T A T A

A = Indicator for alarm suppressions

T = Indicator for threshold crossing notifications (TCN)

Fig. 4.7 Port Symbols

Port symbols are shown in the lower area of the main window when
– a higher-ranking functional symbol (e.g. STM16) was selected in the “Module
View” or
– the symbol for a traffic-carrying module (e.g. OIS16/OIS16-2) was selected in “Mod-
ule View”.
For each port symbol - after it has been selected with the right-hand mouse button - a
context-sensitive menu opens with the two further menu items:
– <Subview>:
Opens the Traffic Flow window which shows the associated functional units/symbols
for this port.
– <Acknowledge>:
You can use this item to acknowledge all alarm messages of this port.

Alarm display
The transmission alarms detected at a port do color the port symbol red. Until the alarm
is acknowledged the red symbol flashes or is outlined in blue – depending on the setting
made using the menu items: <Options> <Settings: Alarm Flash>.

Alarm interrogation
Click with the right-hand mouse button on the (red) port symbol indicating the alarm. Fur-
ther procedures are as described in Chapter 4.2.2, the alarm interrogation under the

68 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

“alarm interrogation on functional symbols of Traffic View” (“... after selection of Sub-
view....”).

Display of alarm suppressions

Field A in a port symbol is used to indicate suppressions that have been set for trans-
mission alarms which are monitored at this port.

Color of field “A” Meaning

black at least one alarm suppression is set for this port

wheat no alarm suppression is set for this port

Tab. 4.4 Indicator Field “A” for Alarm Suppressions

TCN display
Field T is used for the performance monitoring at the relevant port.

Color of field “T” Meaning

red the set performance thresholds were exceeded

black at least one TCN monitoring is switched off

wheat complete TCN monitoring activated

Tab. 4.5 TCN Display Field “T”

4.3 Display of Alarms

Alarms are displayed in the following way at the operator interface:
• Collective alarm indication are available in the main status bar of the main window
(see Fig. 4.3):
up to four LED symbols in different colors – corresponding to the four alarm severi-
ties – can be displayed in an alarm status field. A specific LED is always shown if
there is at least one alarm present with this severity.
This collective indication includes the equipment, the transmission alarms and the
alarms from the general NE functions.
This alarm indication is automatic, the operator does not have to call it up. It remains
visible until the fault which triggered the alarm is cleared.
For more details see Chapter 4.1.3 under “Alarm Status Field”.
• Alarm List (see Fig. 4.3):
It contains a detailed listing of all individual alarms, both the current alarms and
those which have already occurred during the period that the operating terminal
monitoring has been in operation (see also Fig. 7.1).
You can call the alarm list using the main menu items: <Fault> <Alarm List>.
For more details see Chapter 7.1.2.
• Hierarchical alarm display are in the various views:
Subrack, Module, and STM-n Traffic Flow symbols are arranged in hierarchically or-
dered windows using such things as the alarm signaling and the fault tracing.
– Module view with using the “NE/Subrack” module symbol and menus items
<Fault> <Equipment Alarms> and the <Detailed Alarm Information ...> is for
displaying the alarms of the subrack of the NE (see Fig. 7.10). The Subrack can

1.Vorabzug:A30808-X3580-H504-1-7620 69
MMN Maintenance
SLD/T16-2.5

display alarms, assigned to an alarm window (“NE/Subrack - Alarm”), for de-

tailed display of the possible and current alarms.
– Module View is for displaying the <Equipment alarms> as module alarms (see
Fig. 7.2):
The module symbols signal a faulty module, the corresponding alarm windows
supply further error information about the module.
For the modules with traffic functions the following also applies:
A transmission alarm is detected in this module and signaled using a port symbol
(in the lower area of the Module View window). In a further Traffic Flow window a
symbol shows the functional unit which is signaling the fault assigned to an alarm
window. This contains the details of the possible and current transmission alarms.
– Module View with STM-n Traffic Flow window is for displaying the <Communi-
cation Alarms> (see Fig. 7.3) and (see Fig. 7.4):
A symbol for a traffic or transmission function signals an alarm, as does
– in hierarchical classification – the assigned port symbol (in the lower area of the
Traffic View window) and the corresponding functional symbol of the Traffic Flow
window. For the latter an alarm window provides details of the possible and cur-
rent alarms.
– Module View with the CLL module symbol is for the functional symbols SEC
(clock source) and with the OHA module symbol for the OH-IF (Overhead inter-
face).
– Module View with the SCU module symbol is for the functional symbols CLNS
(connection less network services), DCC (data communication channels), Ether-
net, IP Configuration(Addres, Gateway, and Routing), the Stack Parameters,
and for the Transport Connections.
The following table shows the alarm display in compressed form, however it cannot re-
i place the detailed chapter dealing with the individual alarm signaling functions.

Alarm Display Alarm sup-

pression,
Collective display LED in the alarm Module or func- LED in alarm win-
Function field A
for alarms = list tional symbol dow (for module in symbol
LEDs in alarm sta- or functional sym-
tus field bols)

Call function / assignment In main status bar Call in main window In windows Context menu In module,
of the main window; with <Fault> - Module View <Fault> <Alarms> function and
is displayed <Alarm List> - Traffic View port symbols
automatically - Module view and
- subordinate win-
dows

a) Signaled alarm is higher-priority than alarm severity threshold set with <Options> <Settings: Alarm Severity Threshold>, alarm signaling
status set to “operation” (i.e. normal mode is set)

Alarm signaled and not acknowl- LED in color of LED in color of Red, LED in color of Wheat color
edged alarm severity, blue alarm severity, blue blue outline or alarm severity, blue 1)
outline outline flashing outline

Alarm signaled and acknowl- LED in color of LED in color of red LED in color of Wheat color
edged alarm severity alarm severity alarm severity 1)

Tab. 4.6 Alarm Display on the Operating Terminal, Overview

70 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Alarm Display Alarm sup-

pression,
Collective display LED in the alarm Module or func- LED in alarm win-
Function field A
for alarms = list tional symbol dow (for module in symbol
LEDs in alarm sta- or functional sym-
tus field bols)

Suppression set for individual

alarm:
– if this alarm is generated in the Alarm will not be in- Alarm will not be in- Wheat color Alarm will not be in- Black
NE dicated dicated dicated

– if another alarm is generated in LED in color of LED in color of Red, (In the associated In the associ-
the NE alarm severity, blue alarm severity, blue blue outline or alarm window:) ated symbol:
outline outline flashing LED in color of black
alarm severity, blue
outline

b) Signaled alarm is lower-priority than alarm severity threshold set with <Options> <Settings: Alarm Severity Threshold>, alarm signaling
status set to “operation” (i.e. normal mode is set)

Alarm signaled and not acknowl- LED in color of LED in color of wheat color LED in color of Wheat color
edged alarm severity, blue alarm severity, blue alarm severity, blue 1)
outline and crossed outline outline
through
Alarm signaled and acknowl- LED in color of LED in color of wheat color LED in color of Wheat color
edged alarm severity and alarm severity alarm severity 1)
crossed through
Suppression set for individual
alarm:
– if this alarm is generated in the Alarm is not dis- Alarm is not dis- Wheat color Alarm is not dis- Black
NE played played played

– if another alarm is generated in LED in color of LED in color of wheat color LED in color of Black
the NE alarm severity, blue alarm severity, blue alarm severity, blue
outline and crossed outline outline
through

c) Alarm signal status set to “maintenance”

alarm in NE generated or can- No change to display if new alarms occur or if alarms are canceled. However the alarm display can be
celed again updated again using menu items: <Window> <Update All Alarms>.

1)... An alarm suppression was not set for any individual alarm

Tab. 4.6 Alarm Display on the Operating Terminal, Overview (Cont.)

1.Vorabzug:A30808-X3580-H504-1-7620 71
MMN Maintenance
SLD/T16-2.5

Alarm Status
Symbols Form in which the Alarm Alarm Severity
acknowl. not ac-
appears
knowl.

Module, function Red, flashing All X

and port symbols Red, blue outline X

Red X

Wheat color No alarm signaled – –

LED alarm symbols Orange Major alarm X

in the main status Yellow Minor alarm X
bar and also in the
Blue Warning alarm X
alarm list and in the
alarm windows Red/orange/yellow/blue and Critical/major/minor/warn- X
additional blue outline ing alarm

Only for the LED Red/orange/yellow/blue and Critical/major/minor/ X

alarm symbols in the blue outline and also black
main status bar crossed through
Red/orange/yellow/blue and
also black crossed through
warning alarm,
signaled alarm is below the
set alarm severity threshold
X

X ... Function applies to the specified form in which the alarm appears

Tab. 4.7 Meaning of the Alarm Colors

☞ The display of the alarm suppressions set is explained in Chapter 4.4.1.

4.4 Effect of the Alarm Display at the Operating Terminal

For alarm messages you can set the suppressions shown below in Tab. 4.8.

Type Purpose Handling of Spontaneous Settings to be

Alarm Telegrams made

Alarm display de- The signaling of low-severi- Alarms with a severity below the In main menu
pends on the alarm ty alarms can be prevented set threshold are not signaled by items: <Options>
severity, see also in the “View” windows. module and functional symbols. <Settings: Alarm
Chapter 4.1.1 Severity Thresh-
old>

Alarm suppression, Explicit masking out of indi-
see also Chapter vidual alarms at the operat-
4.4.1 ing terminal.
Can be used for all equip-
ment and transmission
alarms.
For correspondingly marked In the alarm win-
alarms the NE suppresses spon- dow for the rele-
taneous alarm telegrams to the vant functional
operating terminal and Bw7R group, can be set
alarm messages. in a checkbox

Tab. 4.8 Possible Effects of Alarm Displays at the Operating Terminal

72 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance
SLD/T16-2.5
Type Purpose
Disabling/Enabling of Command to suppress/re-
alarm messages with lease SSF, AIS and RDI
low priority, see also alarm messages.
Chapter 4.4.1.4
NE signaling status All spontaneous alarm
“Maintenance”, messages are suppressed.
see also Chapter 3.6 These setting can be made
while maintenance is being
carried out for example to
prevent a flood of alarms
being displayed.
Port Monitoring, For the optical ports of the
see also Chapter transmission functions
3.3.3.1 STM-16 (OIS16/OIS16-2),
STM-4 (OIS4/OIS4-2),
STM-1 (OIS1), Opt.
Preamp (OP) and the elec-
tr. ports for STM-1 and 140
Mbit/s (EIPS1) alarm moni-
toring can be set to inactive;
useful for example when
making cross connections
at the optical ports.
Connection Supervi- The monitoring of unoccu-
sion Mode, pied VC-4 channels can be
see also Chapter switched off to prevent
3.3.3.2 dummy alarms.
Termination Point The monitoring of unoccu-
Monitoring, pied VC-4 channels (plesio-
see also Chapter chronous signals) can be
3.3.3.3 switched off to prevent
dummy alarms.
Tab. 4.8 Possible Effects of Alarm Displays at the Operating Terminal (Cont.)
1.Vorabzug:A30808-X3580-H504-1-7620
MMN
Handling of Spontaneous Settings to be
Alarm Telegrams made
For accordingly marked In the alarm win-
SSF/AIS/RDI alarms the NE dow for the rele-
suppresses spontaneous alarm vant functional
telegrams to the operating termi- group, can be set
nal as well as Bw7R alarm re- in a checkbox
ports.
The NE suppresses alarm tele- In main menu
grams to the operating terminal. items: <NE-
The current alarm state is fixed. State> <Set to
However an alarm request is Maintenance>
possible (menu items: <Win-
dow> <Update All Alarms>).
Bw7R alarm messages are not
suppressed.
The monitoring of the input sig- In the configura-
nals from other network ele- tion menu for the
ments or transmission media is symbol for the rel-
activated or deactivated. evant transmis-
Bw7R alarm messages con- sion function
cerned are issued or sup- (STM16, STM-4,
pressed. STM1, E4; via
traffic flow win-
dow of the rele-
vant port symbol)
Alarm messages at the VC-4 In the configura-
connection supervision point are tion menu for the
not monitored or there is moni- AU4/VC4 symbol
toring of the path overhead or an (traffic flow win-
unequipped-monitoring. dow to the port
Bw7R alarm messages con- symbol of the
cerned are issued or sup- STM1 or STM-4
pressed. or STM16 func-
tional unit)
Alarm messages at the VC-4 ter- In the configura-
mination point are monitored / tion menu for the
not monitored. VC4 symbol of
Bw7R alarm messages con- EIPS1 (traffic flow
cerned are issued / suppressed. window to the
port symbol of the
E4 functional unit,
140 Mbit/s)
73
MMN Maintenance
SLD/T16-2.5

Type Purpose Handling of Spontaneous Settings to be

Alarm Telegrams made

Trail Trace Identifier The monitoring of the VC-4
(TTI) Processing path id. can be switched off,
VC-4, if for example there is
see also Chapter equipment assigned to the
3.3.3.4 signal path which does not
allow any TTI processing.
Signaling of transmission In the configura-
alarm TIM is activated or deacti- tion menu for the
vated. An alarm message TIM is AU4/VC4 symbol
only possible if connection su- (traffic flow win-
pervision mode or termination dow to the port
point mode is already active. symbol of the
STM1 or STM4 or
STM16 function-
al unit)

Trail Trace Identifier The monitoring of the ca- Signaling of transmission In the configura-
(RS TTI) Processing bling between two adjacent alarm RS TIM is activated or de- tion menu for the
in the regeneration network elements can be activated. STM1/4/16 sym-
section, switched on or off. bol (traffic flow
see also Chapter window to the
3.3.3.4 port symbol of the
STM1 or STM4 or
STM16 function-
al unit)

Tab. 4.8 Possible Effects of Alarm Displays at the Operating Terminal (Cont.)

The Bw7R alarms of the Subrack Alarm Panel (SRAP), the Light Signal Equipment
(LZE) and Central Service Observation (ZBBeo) are not affected by the “Maintenance”
setting.

4.4.1 Setting and Displaying Alarm Suppressions

A suppression set for an alarm has the effect of preventing the NE issuing an alarm mes-
sage to the operating terminal if there is a fault. No alarm can therefore be signaled at
the operating terminal interface.
Alarm suppressions can be set for each individual alarm in the alarm windows
• For all the modules (suppression of equipment alarms), see Chapter 4.4.1.1
• For the symbols for the transmission functions (suppression of transmission alarms),
see Chapter 4.4.1.2.
Alarm suppressions for the transmission alarms can be set for the following function-
al units of the modules listed below:
– Module EIPS1: Functional units STM1 and AU4/VC4
– Module OIS1: Functional units STM1 and AU4/VC4
– Module OIS4/OIS4-2: Functional units STM4 and AU4/VC4
– Module OIS16/OIS16-2: Functional units STM16 and AU4/VC4
– Module OP: Functional unit OPT-PREAMP
– Module OB: Functional unit OPT-BOOST
– Module OHA: Functional unit OH-IF, channel 1 and channel 2

• For the alarms of the following module functions (in the module view):
SEC, OH-IF and Subrack.
See Chapter 4.4.1.3.
In addition the suppressions can be set for the SSF, the AIS and the RDI alarm reports
(see Chapter 4.4.1.4).

74 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

4.4.1.1 Setting and Clearing Suppressions for Equipment Alarms

• Setting:
Main menu items: <View> <Module View>, select the module symbol with the right-
hand mouse button, the menu items: <Fault> <Communications Alarms>, select
relevant “Suppression” field in the alarm window.
• Clearing:
Select relevant “Suppression” field again.
Execute the setting and clearing command using <Apply> button in each case.

4.4.1.2 Setting and Clearing Suppressions for Transmission Alarms

• Setting (using module EIPS1 as an example):
Main menu items: <View> <Module View>, select the module symbol (here:
EIPS1), in the lower window area select the desired port symbol with the right-hand
mouse button, the menu item: <Subview>, select the functional symbol with the
right-hand mouse button (here: STM1 or AU4/VC4), the menu items: <Fault>
<Communications Alarms>, in alarm window select relevant “Suppression” field.
Alternatively you can use main menu items: <View> <Traffic View> to call the view
of the traffic functionalities of the NE, select the traffic symbol (e.g. STM1 el.). Then
open the context-sensitive menu by selecting it with the right-hand mouse button,
click on the desired port symbol, click on <Subview> item, chose the functional sym-
bol (here STM1 or AU4/VC4) with the right-hand mouse button, open the alarm win-
dow using the menu items: <Fault> <Communications Alarms> and select the
relevant “Suppression” field.
• Clearing:
Select relevant “Suppression” field again.
Execute the setting and clearing command using the <Apply> button in each case.

4.4.1.3 Setting and Clearing Suppressions for Alarms of Module Functions

• Setting (using function SEC as an example):
The main menu items: <View> <Module view>, select the functional symbol (SEC)
with the right-hand mouse button, the menu items: <Fault> <Communications
Alarms> and then select the relevant “Suppression” field in the alarm window.
• Clearing:
Select relevant “Suppression” field again.
Execute the setting and clearing command using the <Apply> button in each case.
You can also set/clear the alarm suppressions by selecting the desired alarm with the
i right-hand mouse button in the relevant alarm window and making your choice in the
context-sensitive menu which opens.

4.4.1.4 Disabling and Enabling of SSF, AIS and RDI Alarm Reports
For the following interface modules you may enable or disable the display of the incom-
ing transmission alarms SSF, AIS and RDI (see Tab. 4.9):

1.Vorabzug:A30808-X3580-H504-1-7620 75
MMN Maintenance
SLD/T16-2.5

Module Functional Units

EIPS1 STM1(el.), AU4/VC4

OIS1 STM1(opt.), AU4/VC4

OIS4/OIS4-2 STM4, AU4/VC4

OIS16/OIS16-2 STM16, AU4/VC4

Tab. 4.9 Functional Units where SSF, AIS and RDI Alarm Reports may be Acti-
vated/Deactivated

The following example for a module EIPS1 describes the procedure with which you en-
able/disable the alarm reports (see also Fig. 4.8):
1. Select the main menu items: <View> <Traffic View>.
2. Mark the functional symbol (for this example:) STM1(el.) and select the desired port
symbol with a right-hand mouse click. Chose he menu items: <Subview>.
3. In the traffic flow window which opens now, select the desired functional symbol (for
example STM1) with the right-hand mouse button and select the <Fault> <Commu-
nications Alarms> items in the context menu.
4. In the alarm window in selectable fields to the “No Alarm Report” column, you may
select for each of the SSF, AIS and RDI alarms whether an alarm report is forwarded
or not. Repeated selection turns the setting to the opposite. Confirm your choice with
the <Apply> button.

Fig. 4.8 Disabling/Enabling SSF, AIS and RDI Alarm Reports Using the EIPS1
Module as an Example

4.4.1.5 Displaying Alarm Suppressions

(see also Chapter 4.2)
– Equipment alarms:
A set alarm suppression turns the indicator field “A” in the corresponding module
button (e.g. EIPS1) to black.
– Transmission alarms:
A set alarm suppression turns the indicator field “A” in the corresponding functional

76 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

symbol (e.g. STM1), and at the same time in the higher-ranking port symbol and (in
Traffic View) in the higher-ranking traffic symbol (here: STM1), to black colour.
– Alarms of module functions:
A set alarm suppression turns the indicator field “A” in the corresponding functional
symbol (e.g. SEC) to black.

4.5 Saving Alarm Information

4.5.1 Alarm List and Alarm Window

The contents of the alarm list, as a collective display of all the current and previous alarm
messages and also the contents of the various alarm windows for the individual modules
(equipment alarms) and the functional symbols (transmission alarms and alarms of gen-
eral NE functions) can be saved as follows:
1. Select the title line in the opened window
2. Chose <File> <Save As> items from the main menu
3. Define the path for “Save”.
The contents of the window are stored as an ASCII file with the suffix ”.txt” and can then
be read in into a suitable editor.

4.5.2 Event Window

The lower area of the main window, the event window / Message Output Area, shows
the events and the messages coming from the NE.
You can save this information by calling the main menu items:
<File> <Save Message List> and specifying the path for “Save”.
The contents of the window are stored as an ASCII file with the suffix ”.txt” and can then
be read in into a suitable editor.

4.5.3 Log Records

For saving the log records see Chapter 3.9.

1.Vorabzug:A30808-X3580-H504-1-7620 77
MMN Maintenance
SLD/T16-2.5

5 Maintenance Concept
Maintenance activities are divided into:
• Preventive maintenance
• Fault-related (corrective) maintenance or fault clearance
• Quality monitoring during operation
• Decision between the real faults and the faults caused by misalignments of param-
eters
• Fault localization up to the module level

5.1 Preventive Maintenance

In general terms the SL16-2.4 fiber optic system does not require any regular preventive
maintenance or setting operations.

5.1.1 Exchanging the Backup Battery in the SLD16/SLT16

One exception as regards preventive maintenance is exchanging the backup battery on
the SCU of the SLD/SLT network element which does have a minimum life of 10 years.
Thereafter it should be replaced.
The battery is used to back up a real-time clock unit and an NVRAM which provide time
information and save test results and flags of the boot software.
To avoid data loss, the battery may only be exchanged by the manufacturer of the unit!
i Remove module SCU according to the information in Chapter 8.2 and send this in suit-
able packaging (ESD protection) to the manufacturer.

5.1.2 Preventive Maintenance on Optical Modules

As a further preventive measure – after the ageing process of the laser diodes in the
optical modules has reached an advanced stage – preventive exchange of these mod-
ules can be undertaken at a time when operating conditions are favorable for doing so.
This prevents any possible failure and the associated interruption to operation.
A preventive module exchange is recommended if any of the following transmission
alarm messages occur:
– Module OIS16/OIS16-2: Alarm TxDeg (see Tab. 7.6)
– Module OIS4/OIS4-2: Alarm TxDeg (see Tab. 7.13)
– Module OIS1: Alarm TxDeg (see Tab. 7.16)
– Module OB: Alarm TxDeg (see Tab. 7.5)
– Module OP: Alarm RxDeg (see Tab. 7.4)

5.2 Corrective Maintenance (Fault Clearance)

In the case of a fault, fault clearance is basically carried out according to the procedure
described in this manual (corrective maintenance).
Fault clearance means measures which are used to restore operation after a fault or an
failure.
Successful fault clearance requires the synchronous line equipment to have already
been operating correctly before the fault occurred.
Failure-specific maintenance work is initiated by signaling alarms.

78 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

The alarm signaling and monitoring circuits of the synchronous line equipment provide
information which is required to pinpoint down to module level any fault which occurs.
The corresponding maintenance procedures can in many cases be carried out without
impairing payload data transmission.
The concept of the SL16 fiber optic system, particularly the numerous protection switch-
ing options, allow fault clearance without interrupting operation in many cases.
Fault clearance within an NE generally consists in exchanging modules.
Fault monitoring and localizations can be carried out:
• on site, by using a Local Craft Terminal LCT connected to the Q-F- or Q-B3 interface
• remotely, using a Network Craft Terminal NCT connected to the Q-B3 interface. Al-
ternatively – again via the Q-B3 interface – (restricted) fault pinpointing can be per-
formed via the operations system OS of the TMN.
The alarm display on the operating terminal (LCT or NCT) is tailored to the alarm type:
• “Module View”: if the cause of alarms and error messages is in the own network
element then they are assigned to the modules involved → Equipment Alarms.
• “Module View”: for alarm and error messages which occur on the transmission
route → Transmission Alarms
• “Module view”: for general NE alarms → General Alarms

Fault Clearance
The fault clearance measures described in this manual are based on the alarm messag-
es at the operating terminal LCT/NCT as well as the indicator LEDs on the modules. In
some cases a fault is also realized by the automatic happened change from a mainly
used module, a channel or a communication path to a standby or protection one. For
example, if an external CLA box fails, the used clock sources are automatically switched
to the ones with an equal or the next best level and the indication is, if the channels re-
lated are checked by the operator, the message: “Do not use for synchronization”. On
the other hand, an increasing of bit-errors may be caused by the transmission line itself
or by the related equipment at both ends.
Fault cases are described in Chapter 7.2.
These measures are described in the following Chapters:

☞ Alarm Evaluation at the LCT/NCT is described in Chapter 6.2.

☞ For an Equipment-Alarm the fault pinpointing and the clearance is described

in Chapter 7.2.1. Serious equipment faults are dealt with are found in Chapter
7.2.2.

☞ For a Transmission-Alarm the fault pinpointing is described in Chapter 7.3.1

and a subsequent alarm evaluation according is found in Chapter 7.3.2. Chap-
ter 7.3.3 deals with “internal” transmission alarms and Chapter 7.3.4 contains
the further information about the transmission alarms (typical fault images etc.)

☞ For a NE General Alarms the fault pinpointing and the clearance is described
in Chapter 7.4.

☞ Information about SW Alarms can be found in Chapter 7.6.

1.Vorabzug:A30808-X3580-H504-1-7620 79
MMN Maintenance
SLD/T16-2.5

☞ Chapter 7.7 lists the settings which have to be made after a fault clearance has
terminated.

☞ Chapter 7.8 refers to the special fault clearance in the case of an unsuccess-
ful fault locating.

☞ The exchange of the modules is described in Chapter 8.

5.3 Quality Monitoring During Operation

The performance management functions provide the extensive options for the monitor-
ing, the collecting and the recording of operational quality data which gives the user a
permanent information about the quality of the telecommunications links. The possible
quality problems when transmitting messages can be easily determined in this way.
See Chapter 3.10 and the Operating Manual OMN (Register 1 OMN:SL) for more de-
tails.

80 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

6 Procedure for Alarm Evaluation

Depending on the setup and the size of a transmission network, various management
facilities can be available for the monitoring and the alarm signaling. Most larger net-
works will have extensive TMN facilities (Chapter 6.1), while in the smaller and medium-
sized networks a Network Craft Terminal NCT (Chapter 6.2) is best suited for the fault
management jobs e. g..
For an alarm detection and an fault evaluation on the site, the local craft terminal LCT
has been used (Chapter 6.2).
For the SL16, the alarm signaling scheme used for a Bw7R rack design is also available
for fault display and location (Chapter 6.3), which can then e.g. be put to good use if
there is no TMN, NCT or LCT.

6.1 Alarm Evaluation at the TMN

If there is a telecommunication network management (TMN) system, the alarms from
the NE are signaled to the operation system (e.g. EM-OS, SMN-OS). In this case, the
information about carrying out a fault pinpointing can be taken from the operating doc-
umentation about the operations system.

6.2 Alarm Evaluation on LCT/NCT

☞ For further details of the operation see the Operating Manual OMN.
For the detailed UniGATE operating instructions refer to the Register 2,
details of the NE application software can be found in Register 1 OMN:SL and
also in this Manual in the Chapter 4.

6.2.1 Procedures and Alarm Information in NE-UniGATE

When the Q-B3 Interface is Used
For a network access and for a viewing and an administration of the network alarms use
the gateway-software “NE-UniGATE” by the following way:
1. Connect the Network Craft Terminal NCT (desktop PC) or the Local Craft Terminal
LCT (Laptop) to the Ethernet (Q-B3 interface) and put it into operation.
2. Start the NE-UniGATE (in the LCT version for example) by double-clicking on the
symbol for the NE-UniGATE [LCT].
If you are going to use the NCT version of the UniGATE, choose either the UniGATE
LCT or the UniGATE NCT mode in the “Mode Selection” window.
3. The Logon under an user authorization class 4 with the user ID and the password
(for defaults see OMN Manual, Register 2).
4. The correct device address must already be set. You will find details of the settings
in the OMN Manual, Register 2, and in the Manual: ITMN.
5. Use the menu items: <Configuration> <Options> <Communication channel: QB3>
to select the Q-B3 interface. Click with the mouse in the “QB3” row under the “Action”
column and select “connect” from the context menu. Confirm with the <OK> button.
– If you have chosen the NCT mode when starting the NE-UniGATE:
The “Selectable devices via Q-B3 (Ethernet)” window or a corresponding icon ap-
pears on the screen: Depending on how the view was previously configured, the
window contains the icons for the NEs switched to active in the NCT or a sche-

1.Vorabzug:A30808-X3580-H504-1-7620 81
MMN Maintenance
SLD/T16-2.5

matic diagram of the selected transmission area, which is possibly overlaid over
a map.
– If you have chosen the LCT mode when starting the NE-UniGATE:
The “Selectable devices via Q-B3 (Ethernet)” window appears, with the icons of
the activated NEs. Select the desired NE (e.g. SLD16) by double clicking on its
icon and one or more of the previously defined windows will open. In addition the
notifications window will be displayed (possibly as an icon) containing the mes-
sages and the warnings about the connection setup and the network access.
The lower part of the “Selectable devices via Q-B3 (Ethernet)” window displays the “Cur-
rent Alarm Log” list window showing the current alarm messages.
The following windows (or icons in place of them) are also displayed:
– “Notifications”:
This window contains the messages and the warnings about the connection setup
and the network access.
– “Historical Event Log”:
The connection processes and the alarm messages are listed in a chronological or-
der in this window.
Under the menu path: <Symbol> <Fault> <Current alarm log> the appropriate “Current
Alarm Log” window shows alarms of an NE for which the icon has been selected in the
“Selectable devices via QB3 (Ethernet)” window. In contrast, the menu path <Network>
<Fault> <Current alarm log> lists all the network alarms.
Network elements which are not accessible are indicated as by their identifying text be-
i low the NE icon being grayed out. The menu items: <Network> <Refresh connections>
can be used to start a new connection setup for these NEs.

The initial alarm status is automatically interrogated (in the background).

In the “Selectable devices via QB3 (Ethernet)” window the color of the icon outline of an
NE shows the highest alarm status raised for this NE (Tab. 6.1).

Color of Icon Outline Alarm Severity Assigned

red critical

orange major

yellow minor

blue warning

white indeterminate

green no alarm

Tab. 6.1 Colors of the Icon Outline and Alarm Severities (Defaults)

The color of the icon outline can be changed using the menu items:
<Options> <Settings>.
Until an alarm, which is raised has been acknowledged, the icon outline flashes in dif-
ferent colors (e.g. red/green) and a yellow bell symbol is displayed next to the icon.
For each icon in the “Selectable devices via QB3 (Ethernet)” window you can use the
icon menu to call up the items of an alarm-relevant information such as those listed be-
low by selecting the icon and then choosing the desired menu path:

82 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

• <Symbol> <Fault> <Alarm information>:

Lists the alarms raised belonging to the selected NE in accordance with their sever-
ities
• <Symbol> <Fault> <Alarm request>:
Requests the alarm information and the alarm inhibitions of the selected NE again
• <Symbol> <Fault> <Current alarm log>:
Calls the alarm log for the selected NE
• <Symbol> <Fault> <Acknowledge all alarms>:
A window shows all the individual alarms of the NE concerned.
Use the “Acknowledge” button to acknowledge these alarms. The icon outline stops
flashing and the bell symbol disappears.
• <Symbol> <Fault> <Alarm reset>:
Clears the alarms raised belonging to the selected NE. The icon outline shows by
its color (green) that the alarms have been cleared. The entries in the current alarm
log are also deleted. Future alarms continue to be evaluated however.
For further handling of the alarms change to the SLD/SLT application software:
• Double click on the icon signaling the alarm in the NE and indicating the fault to log
on. This gives you the access to its operator interface.

Some help for the LAN access may be available also from the Windows NT system tools
and the driver and protocol system tools. For further handling of those helps change to
the MS-DOS system operation software:
• Single click on the Windows NT Start button and select from the shown menu the
Programs menu item and then double click the sub menu on the MS-DOS icon. This
opens a black window which gives you the access to the MS-DOS sub operating
system on typing in commands at the DOS-prompt of the DOS interface.
• IPCONFIG/ALL will give you the LAN interface parameters.
• OSIPING/? options give you specific test for reaching members on the LAN.
/? Option lists the available parameter options.
• Back to windows by <Exit> command the opwin.exe may be started also for tests.
Use the also the Enable Loop Back Flag of the “OSI Stack Configuration” window.

☞ For further procedures see Chapter 6.2.3.

6.2.2 Procedure in NE-UniGATE when the Q-F Interface is Used

For an access to the local network element use the gateway software NE-UniGATE:
1. Connect the Local Craft Terminal LCT (laptop) or the Network Craft Terminal NCT
(desktop PC) connected to the Q-F interface of the local network element SLD or
SLT.
2. Start the NE-UniGATE by double clicking on the symbol for the NE-UniGATE [LCT].
If you are going to use the NCT version of the UniGATE, choose the NCT mode in
the “Mode Selection” window.
3. Log on under the user authorization class 4 with the user ID and the password (for
defaults see OMN Manual).
4. Use the menu items: <Configuration> <Options> <Communication channel: Q-F> to
select the Q-F interface. Click with the mouse in the “Q-F” row under the “Action” col-
umn and select “connect” from the context menu. Confirm with <OK> button.
The operator interface of the local NE (e.g. SLD16) is then displayed and also the

1.Vorabzug:A30808-X3580-H504-1-7620 83
MMN Maintenance
SLD/T16-2.5

“Notifications” window (possibly as an icon) containing the messages and the notes
about the connection setup and the network access.

☞ For further procedures see Chapter 6.2.3.

6.2.3 Alarm Evaluation with the Aid of the Network Element Application
Software
Access Rights
If no other user with a write permission is registered at the NE, the read/write access to
the NE is activated automatically after you log on to the NE application software (of the
SLD16 for example); the “write” word appears in the indicator field for the access rights
in the main status bar.
If another user has secured access rights before you, you have read access only; the
main status bar indicates the “read” permission.

NE Alarm Signaling State

Check that in the main status bar at the indicator field for the NE alarm signaling state
showing “operation”. If it is not in this state, use the main menu item: <NE State> to set
the state to operation with its <Set to Operation> item.

Alarm Display
If an alarm is raised, at least one (LED) symbol of the alarm status field is lit in the cor-
responding alarm indicator color in the main status bar.
The deciding factor for a detailed alarm display at the operator interface of the NE ap-
plication software is the display that was set by default or called by using a menu com-
mand like:
• “Alarm List” window:
List of all “current” alarms and all previous alarms (“history”);
• “TCN List” window:
List showing crossing of important NE performance thresholds;
• “Module View” window:
To show the equipment alarms and the detailed alarm informations;
• “Traffic Flow View” window:
For signaling communication alarms or
• “Subrack View” window:
For displaying alarms of the general NE functions
Perform the fault clearance measures described in the Chapter 7.

6.3 Generation of Bw7R Alarms

See also Chapter 3.4.5.
i
Some of the alarm messages issued by the NE will be displayed by the Bw7R alarm fa-
cilities.

84 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

The Bw7R alarm displays are particularly useful when no TMN or no NCT are available
to display the alarms.

6.3.1 Default Settings for Bw7R Alarms

The alarms of the individual functional groups (transmission alarms) as well as the
equipment alarms and the alarms of general NE functions are displayed at the places
marked with an “X” in the tables below.
These tables summarize:
• The alarm displays in the individual alarm windows for the modules and the function-
al groups
• The corresponding designations for the Bw7R alarm configuration file as they will be
displayed in the window using the main menu items: <File> <Script Configuration>
• The associated Bw7R messages
The Tab. 6.2, Tab. 6.3 and Tab. 6.4 show the default settings, Chapter 6.3.2 describes
how these can be changed.

☞ The meaning of the alarm names is described in Chapter 7.3.2.2.

6.3.1.1 Transmission Alarms of the SLD/SLT and Associated (Local)

Bw7R Alarms

Alarm Display at Operating Terminal QST Designations in Window Bw7R Alarm Signaling
(Alarm Window) Script Configuration

Alarm name Name of the alarm win- Alarm Object class SRAP-PI ZA (for
dow in container ZBBeo)

LED LED (A) (B)

A B

LOS (OS) OIS16/16-2 FLos OsTtp in Mtf16 X – X –

_..(2.5G)_STM16

LOS (OS) OIS4/4-2_..(622M)_STM4 OsTtp in Mtf4 X – X –

LOS (OS) OIS1_..(155M)_STM1 OsTtp in Mtf1 X – X –

LOS (ES) EIPS1_..(155M)_STM1 EsTtp in Emtf1 X – X –

LOS (E4) EIPS1_..(140M)_E4 ETtp in Ltf140 X – X –

LOS (G703) OHA_.._G703 G703Ttp in Ohf – X – X

LOS (G703) OHA_.._G703 G703Ttp in OhfLim- – X – X

(to OHA-limited module = ited
OHA No. 2/3)

LOS (TIF) OHA_.._TIF TelemetryInterface – X – X

in Ohf

LOS (OAS) OP_.._OAS OasTtpPreamplifier X – X –

in OfaPreamplifier

Tab. 6.2 Bw7R Alarm Signaling for Transmission Alarms, Default Settings

1.Vorabzug:A30808-X3580-H504-1-7620 85
MMN Maintenance
SLD/T16-2.5

Alarm Display at Operating Terminal QST Designations in Window Bw7R Alarm Signaling
(Alarm Window) Script Configuration

Alarm name Name of the alarm win- Alarm Object class SRAP-PI ZA (for
dow in container ZBBeo)

LED LED (A) (B)

A B

LOA OIS16/16-2/4/4-2 FLof msaCsMux X – X –

(VCCTP) _..(2.5G/622M)_AU4/VC4_
STM16/4

LOF (RS) OIS16/16-2 Spap in Mtf16 X – X –

_..(2.5G)_STM16

LOM (RS) OIS16/16-2 Spap in Mtf16 X – X –

_..(2.5G)_STM16

LOF (RS) OIS4/4-2_..(622M)_STM4 Spap in Mtf4 X – X –

LOM (RS) OIS4/4-2_..(622M)_STM4 Spap in Mtf4 X – X –

LOF (RS) OIS1_..(155M)_STM1 Spap in Mtf1 X – X –

LOF (RS) EIPS1_..(155M)_STM1 Spap in Emtf1 X – X –

SQM (RS) OIS4/4-2_..(622M)_STM4 Spap in Mtf4 X – X –

TxFail (OS) OIS16/16-2 FTf OsTtp in Mtf16 X – X –

_..(2.5G)_STM16

TxFail (OS) OIS4/4-2_..(622M)_STM4 OsTtp in Mtf4 X – X –

TxFail (OS) OIS1_..(155M)_STM1 OsTtp in Mtf1 X – X –

TxFail (OAS) OB_.._OAS OasTtpBooster in X – X –

OfaBooster

TxDeg (OS) OIS16/16-2 FTd OsTtp inMtf16 – X – X

_..(2.5G)_STM16

TxDeg (OS) OIS4/4-2_..(622M)_STM4 OsTtp inMtf4 – X – X

TxDeg (OS) OIS1_..(155M)_STM1 OsTtp inMtf1 – X – X

TxDeg (OAS) OB_.._OAS OasTtpBooster in – X – X

OfaBooster

RxFail (OAS) OP_.._OAS FRf OasTtpPreamplifier X – X –

in OfaPreamplifier

RxDeg (OAS) OP_.._OAS FRd OasTtpPreamplifier – X – X

in OfaPreamplifier

Tab. 6.2 Bw7R Alarm Signaling for Transmission Alarms, Default Settings (Cont.)

86 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Alarm Display at Operating Terminal QST Designations in Window Bw7R Alarm Signaling
(Alarm Window) Script Configuration

Alarm name Name of the alarm win- Alarm Object class SRAP-PI ZA (for
dow in container ZBBeo)

LED LED (A) (B)

A B

SD (MS) OIS16/16-2 FDeg MsTtp in Mtf16 – – – X

_..(2.5G)_STM16
SD (MS) OIS4/4-2_..(622M)_STM4 MsTtp in Mtf4 – – – X

SD (MS) OIS1_..(155M)_STM1 MsTtp in Mtf1 – – – X

SD (MS) EIPS1_..(155M)_STM1 MsTtp in Emtf1 – – – X

SD (VC4) EIPS1_..(140M)_VC4 VcTtp in St140 – – – X

SD (VC4) EIPS1_..(155M)_AU4/ VcCtp in MsaCsMux – – – X

VC4

SD (VC4) OIS1_..(155M)_AU4/ VcCtp in MsaCsMux – – – X

VC4

SD (VC4) OIS4/4-2_..(622M)_AU4/ VcCtp in MsaCsMux – – – X

VC4

SQM (VC4) OIS4/4-2_..(622M)_AU4/ VcCtp in MsaCsMux – – – X

VC4

SD (VC4) OIS16/16-2_..(2.5G)_AU4/ VcCtp in MsaCsMux – – – X

VC4

SQM (VC4) OIS16/16-2_..(2.5G)_AU4/ VcCtp in MsaCsMux – – – X

VC4

AIS (P4) EIPS1_..(140M)_E4 FAis Ppap in Ltf140 – – – –

AIS (G703) OHA_.._G703 G703Ttp in Ohf – – – –

AIS (G703) OHA_.._G703 G703Ttp in OhfLim- – – – –

(to OHA-limited module = ited
OHA No. 2/3)

AIS (MS) OIS16/16-2 MsTtp in Mtf16 – – – –

_..(2.5G)_STM16

AIS (MS) OIS4/4-2_..(622M)_STM4 MsTtp in Mtf4 – – – –

AIS (MS) OIS1_..(155M)_STM1 MsTtp in Mtf1 – – – –

AIS (MS) EIPS1_..(155M)_STM1 MsTtp in Emtf1 – – – –

AIS (AU4) EIPS1_..(155M)_AU4/ Msap in MsaCsMux – – – –

VC4

AIS (AU4) OIS1_..(155M)_AU4/ Msap in MsaCsMux – – – –

VC4

AIS (AU4) OIS4/4-2_..(622M)_AU4/ Msap in MsaCsMux – – – –

VC4

AIS (AU4) OIS16/16-2_..(2.5G)_AU4/ Msap in MsaCsMux – – – –

VC4

Tab. 6.2 Bw7R Alarm Signaling for Transmission Alarms, Default Settings (Cont.)

1.Vorabzug:A30808-X3580-H504-1-7620 87
MMN Maintenance
SLD/T16-2.5

Alarm Display at Operating Terminal QST Designations in Window Bw7R Alarm Signaling
(Alarm Window) Script Configuration

Alarm name Name of the alarm win- Alarm Object class SRAP-PI ZA (for
dow in container ZBBeo)

LED LED (A) (B)

A B

RS-TIM OIS4/4-2_..(155M)_AU4 RS_Tim – – X –

(VC4)
TIM (VC4) EIPS1_..(140M)_VC4 FTim VcTtp in St140 – – X –

TIM (VC4) EIPS1_..(155M)_AU4/ VcCtp in MsaCsMux – – X –

VC4

TIM (VC4) OIS1_..(155M)_AU4/ VcCtp in MsaCsMux – – X –

VC4

TIM (VC4) OIS4/4-2_..(622M)_AU4/ VcCtp in MsaCsMux – – X –

VC4
TIM (VC4) OIS16/16-2_..(2.5G)_AU4/ VcCtp in MsaCsMux – – X –
VC4

TIM (RS) OIS1_..(155M)_STM1 RsTtp in Mtf1 – – X –

TIM (RS) OIS4/4-2_..(622M)_STM4 RsTtp in Mtf4 – – X –

TIM (RS) OIS16/16-2 RsTtp in Mtf16 – – X –

_..(2,5G)_STM16

TIM (RS) EIPS1_..(155M)_STM1 ERSTtp in Emtf1 – – X –

RDI (MS) OIS16/16-2 FRdi MsTtp in Mtf16 – – – X

_..(2.5G)_STM16

RDI (MS) OIS4/4-2_..(622M)_STM4 MsTtp in Mtf4 – – – X

RDI (MS) OIS1_..(155M)_STM1 MsTtp in Mtf1 – – – X

RDI (MS) EIPS1_..(155M)_STM1 MsTtp in Emtf1 – – – X

RDI (VC4) EIPS1_..(140M)_VC4 VcTtp in St140 – – – X

RDI (VC4) OIS16/16-2_..(2.5G)_AU4/ VcCtp in MsaCsMux – – – X

VC4

RDI (VC4) OIS4/4-2_..(622M)_AU4/ VcCtp in MsaCsMux – – – X

VC4

RDI (VC4) OIS1_..(155M)_AU4/ VcCtp in MsaCsMux – – – X

VC4

RDI (VC4) EIPS1_..(155M)_AU4/ VcCtp in MsaCsMux – – – X

VC4

Tab. 6.2 Bw7R Alarm Signaling for Transmission Alarms, Default Settings (Cont.)

88 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Alarm Display at Operating Terminal QST Designations in Window Bw7R Alarm Signaling
(Alarm Window) Script Configuration

Alarm name Name of the alarm win- Alarm Object class SRAP-PI ZA (for
dow in container ZBBeo)

LED LED (A) (B)

A B

UNEQ (VC4) OIS16/16-2_..(2.5G)_AU4/ FUneq VcCtp in MsaCsMux – – X –

VC4
UNEQ (VC4) OIS4/4-2_..(622M)_AU4/ VcCtp in MsaCsMux – – X –
VC4

UNEQ (VC4) OIS1_..(155M)_AU4/ VcCtp in MsaCsMux – – X –

VC4

UNEQ (VC4) EIPS1_..(155M)_AU4/ VcCtp in MsaCsMux – – X –

VC4

UNEQ (VC4) EIPS1_..(140M)_VC4 VcTtp in St140 – – X –

FOP (2F- OIS16/16-2_..(2.5G)_2F- FFop MspCo2RingCrs in – – – X
SPRING) SPRING MspCrs2RingPG

FOP (MSP- OIS16/16-2_..(2,5G)_2F- MspCo2RingExtra – – – X

CORINGEX- SPRING X Crs in MspCrs2-
TRA-CRS) RingExtraPG

FOP (4F- OIS16/16-2_..(2,5G)_4F- MspCo4RingCrs in – – – X

SPRING) SPRING MspCrs4RingPG

FOP OIS16/16-2_..(2.5G)_1+1 MspCoLineCrs in – – – X

(1+1MSP) MSP MspCrsLinePG

FOP OIS16/16-2_..(2.5G)_1:1 MspCoLineExtra – – – X

(1:1MSP) MSP Crs in MspCrsLine
ExtraPG

SSF-West OIS16/16-2_..(2.5G)_2F- FSsf- MspTtpRing in – – – –

SPRING West MspCrs2RingPG

SSF-West OIS16/16-2_..(2,5G)_2F- MspTtpRing in – – – –

SPRING X MspCrs2RingExtra-
PG

SSF-West OIS16/16-2_..(2,5G)_4F- MspTtpRing in – – – –

SPRING MspCrs4RingPG

SSF-West OIS16/16-2_..(2,5G)_2F- FSsf- MspTtpRingExtra in – – – –

Extra SPRING X West- MspCrs2RingExtra-
Extra PG

SSF-East OIS16/16-2_..(2.5G)_2F- FSsf- MspTtpRing in – – – –

SPRING East MspCrs2RingPG

SSF-East OIS16/16-2_..(2,5G)_2F- MspTtpRing in – – – –

SPRING X MspCrs2RingExtra-
PG

SSF-East OIS16/16-2_..(2,5G)_4F- MspTtpRing in – – – –

SPRING MspCrs4RingPG

Tab. 6.2 Bw7R Alarm Signaling for Transmission Alarms, Default Settings (Cont.)

1.Vorabzug:A30808-X3580-H504-1-7620 89
MMN Maintenance
SLD/T16-2.5

Alarm Display at Operating Terminal QST Designations in Window Bw7R Alarm Signaling
(Alarm Window) Script Configuration

Alarm name Name of the alarm win- Alarm Object class SRAP-PI ZA (for
dow in container ZBBeo)

LED LED (A) (B)

A B

SSF-East Ex- OIS16/16-2_..(2,5G)_2F- FSsf- MspTtpRingExtra in – – – –

tra SPRING X EastEx- MspCrs2RingExtra-
tra PG

SSF OIS16/16-2_..(2.5G)_1+1 FSsf MspTtpLine in – – – –

(1+1MSP) MSP MspCrsLinePG

SSF OIS16/16-2_..(2.5G)_1:1 MspTtpLine in – – – –

(1:1MSP) MSP MspCrsLineExtra
PG

SSF (1:1MSP OIS16/16-2_..(2,5G)_1:1 MspTtpLine in – – – –

with extra MSP MspCrsLineExtra
traffic) PG

SSF (MS) OIS16/16-2 MsTtp in Mtf16 – – – –

_..(2.5G)_STM16

SSF (MS) OIS4/4-2_..(622M)_STM4 MsTtp in Mtf4 – – – –

SSF (MS) OIS1_..(155M)_STM1 MsTtp in Mtf1 – – – –

SSF (MS) EIPS1_..(155M)_STM1 MsTtp in Emtf1 – – – –

SSF (VC4) EIPS1_..(140M)_VC4 VcTtp in St140 – – – –

SSF (VC4) OIS16/16-2_..(2.5G)_AU4/ VcTtp in MsaCsMux – – – –

VC4

SSF (VC4) OIS4/4-2_..(622M)_AU4/ VcCtp in MsaCsMux – – – –

VC4

SSF (VC4) OIS1_..(155M)_AU4/ VcCtp in MsaCsMux – – – –

VC4

SSF (VC4) EIPS1_..(155M)_AU4/ VcCtp in MsaCsMux – – – –

VC4

SSFExtra OIS16/16-2_..(2.5G)_1:1 FSsf-Ex- MspTtpLineExtra in – – – –

MSP tra MspCrsLineExtra
PG

LOP (AU4) OIS16/16-2_..(2.5G)_AU4/ FLop Msap in MsaCsMux – – X –

VC4

LOP (AU4) OIS4/4-2_..(622M)_AU4/ Msap in MsaCsMux – – X –

VC4

LOP (AU4) OIS1_..(155M)_AU4/ Msap in MsaCsMux – – X –

VC4

LOP (AU4) EIPS1_..(155M)_AU4/ Msap in MsaCsMux – – X –

VC4

TIF#1...TIF#4 OHA_.._TIF FTif1 TelemetryInterface X – X –

(TIF) ...FTif4 in Ohf

Tab. 6.2 Bw7R Alarm Signaling for Transmission Alarms, Default Settings (Cont.)

90 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Alarm Display at Operating Terminal QST Designations in Window Bw7R Alarm Signaling
(Alarm Window) Script Configuration

Alarm name Name of the alarm win- Alarm Object class SRAP-PI ZA (for
dow in container ZBBeo)

LED LED (A) (B)

A B

TIF#5...TIF#8 OHA_.._TIF FTif5 TelemetryInterface – X – X

(TIF) ...FTif8 in Ohf
PLM (VC4) EIPS1_..(140M)_VC4 FPlm VcTtp in St140 – – X –

LOS T1#1 CLL_SEC FLtsT11 Mts in Sets – – – X

LOS T1#2 CLL_SEC FLtsT12 Mts in Sets – – – X

LOS T1#3 CLL_SEC FLtsT13 Mts in Sets – – – X

LOS T1#4 CLL_SEC FLtsT14 Mts in Sets – – – X

LOS T3#1 CLL_SEC FLtsT31 Mts in Sets – – – X

LOS T3#2 CLL_SEC FLtsT32 Mts in Sets – – – X

T0 Quality CLL_SEC FT0 Mts in Sets – X – X
Quality

LOS T4 CLL_SEC FLT4 Mts in Sets – X – X

Tab. 6.2 Bw7R Alarm Signaling for Transmission Alarms, Default Settings (Cont.)

6.3.1.2 Equipment Alarms of the SLD/SLT and Associated (Local) Bw7R

Alarms

Alarm display at the operating terminal QST designations in window Bw7R alarm signaling
(alarm window) Script Configuration

Alarm name Name of the alarm win- Alarm Object class SRAP-PI ZA (for
dow in container ZBBeo)

LED LED (A) (B)

A B

Major Alarm window of all FMajor all “module objects” X – X –

moduls in EquipmentMan-
(equipment alarm) ager

Unavailable Alarm window of all FCard- all “module objects” X – X –

moduls Disabled in EquipmentMan-
(equipment alarm) ager

LTU EIPS1_... FLtu EIPS1 in X – X –

EquipmentManager

EBSL EIPS1_... FEbsl cpControl in cpPG – X – X

(CP CNTRL)

PSUTP EIPS1_... FPSUTP cpControl in cpPG – X – X

(CP CNTRL)

Tab. 6.3 Bw7R Alarm Signaling for Equipment Alarms,

Default Settings

1.Vorabzug:A30808-X3580-H504-1-7620 91
MMN Maintenance
SLD/T16-2.5

Alarm display at the operating terminal QST designations in window Bw7R alarm signaling
(alarm window) Script Configuration

Alarm name Name of the alarm win- Alarm Object class SRAP-PI ZA (for
dow in container ZBBeo)

LED LED (A) (B)

A B

LOA Tx CLL(64-2)_... FLoaTx CLL (64-2) in – X – X

EquipmentManager
LOL T0 CLL_... FLolT0 CLL in – X – X
EquipmentManager

LOL T4 CLL_... FLolT4 CLL in – X – X

EquipmentManager

LOM Tx CLL(64-2)_... FLomTx CLL(64-2) in – X – X

EquipmentManager

No 2Mbit CLL_... F2Mbit CLL/CLL64-2 in – X – X

EquipmentManager
Flash SW SCU_... FFlash SCU-R in X – X –
Sw EquipmentManager

Flash1 Cfg. SCU_... FFlash SCU-R in X – X –

1Vcdb EquipmentManager

Flash2 Cfg. SCU_... FFlash SCU-R in X – X –

2Vcdb EquipmentManager

Ethernet fail SCU_... FFlash SCU-R in X – X –

EquipmentManager

Tab. 6.3 Bw7R Alarm Signaling for Equipment Alarms,

Default Settings (Cont.)

6.3.1.3 Module Function Alarms and Associated (Local) Bw7R Alarms

Alarm Display at the Operating Terminal QST Designations in Window Bw7R Alarm Signaling
(Alarm Window) Script Configuration

Alarm name Name of the alarm win- Alarm Object class SRAP-PI ZA (for
dow in container ZBBeo)

LED LED (A) (B)

A B

Timing NE (Subrack) FTiming Ne in NeManager X – X –

2nd Power NE (Subrack) FPower- Ne in NeManager – X – X

Supply

P-Bus X&Y NE (Subrack) PBusX Ne in NeManager X – X –

andY

ICB X&Y NE (Subrack) IcbX Ne in NeManager X – X –

andY

Tab. 6.4 Bw7R Alarm Signaling for Alarms of general NE Functions

for Symbol “Subrack”, Default Settings

92 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Alarm Display at the Operating Terminal QST Designations in Window Bw7R Alarm Signaling
(Alarm Window) Script Configuration

Alarm name Name of the alarm win- Alarm Object class SRAP-PI ZA (for
dow in container ZBBeo)

LED LED (A) (B)

A B

Int HW Fail NE (Subrack) FInternal Ne in NeManager – X – X

HwLink

Tab. 6.4 Bw7R Alarm Signaling for Alarms of general NE Functions

for Symbol “Subrack”, Default Settings

6.3.2 Changing the Bw7R Alarm Assignment

You can change the default values for the Bw7R alarms using the following procedure:
1. In the main menu use: <View> <Module View> to select the module view.
2. With the right-hand mouse button select the “NE/Subrack” symbol and chose the
submenu items: <Configuration> <Bw7R>, which opens the “NE/Subrack - Bw7R
config”.
3. Select the alarm of the list that is to be changed using the right-hand mouse button
and choose the attribute that is to be changed. As decision there is to be decided
between “Subrack Alarm Panel” or “Central Alarm Panel” attribute.
4. Push the <Apply> button.
5. If necessary, save changes to the system’s database.

1.Vorabzug:A30808-X3580-H504-1-7620 93
MMN Maintenance
SLD/T16-2.5

7 Fault Clearance
For fault clearance measures it is vital to take note of the information given in
! Chapter "2 Protective Measures, Handling / Schutzmaßnahmen, Handhabung"

This Chapter describes how to pinpoint a fault detected as a result of an alarm message
at the operating terminal or identified with the assistance of the module fault LED.
In the case of faults having its cause within the modules of the local NE, i.e. the Equip-
ment Faults. Subsequent fault clearance is also described.
For the Communication and Transmission Alarms caused by the faults in the remote
NEs, on the transmission link or between the modules of an NE, the localization of the
faulty function and the possible fault causes and – if meaningful – the fault sources is
explained.

☞ Alarm-relevant displays at the LCT user interface are explained in Chapter 4.

☞ Preparatory measures at the LCT are described in Chapter 6.2.

A basic distinction is made between the following types of faults

• Faults which are displayed at the operating terminal (Chapter 7.1) and
• Serious faults which are signaled on the device with the indicator LEDs when it is no
longer possible to send a message to an external device (e.g. to the operating ter-
minal) (see Chapter 7.2.2).
Reset the clock via the LCT after the power supply of the SL device was switched off
i and on again as well as after a voltage drop (see Operating Manual OMN:SL).

7.1 Alarm Messages at the Operating Terminal

After the application software is started on the operating terminal (see Chapter 6.2.3)
the main window is displayed.
Using the main menu items: <Options> <Settings: Open at Startup;...> you can set the
view to being opened automatically. The type of an alarm view is also affected by the
settings which you make in the same menu item under: “Alarm Severity Threshold” (see
Chapter 4.1.1, using the menu items: <Options> <Settings> for more details).

Detecting Alarms at the Operator Interface

There are a number of options available for displaying and evaluating the alarms ap-
pearing at the operating terminal, like:
• Common display symbol for all the alarm messages, see Chapter 7.1.1
• Alarm list with a summary of all the alarms, independent of the alarm type, see
Chapter 7.1.2
• Display of the alarms of a group in the associated screen view:
Equipment alarms in the “Module View”, the Transmission alarms in the “Traffic
View” and the alarms of the module functions in the “Module view”; see Fig. 7.2,
Fig. 7.4 and Fig. 7.10.

94 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

7.1.1 Collective Display of Alarms

Regardless of which type of the view, the Module View or the Traffic Flow View, was set
using the main menu bar or whether the windows for all the view types were closed
(“empty” main window”), the current alarms are always shown in the right-hand, third of
the main status bar (at the bottom edge of the window), as the collective alarm”LEDs” in
the alarm status field (see Fig. 4.3).
The way in which the collective alarm LEDs are displayed provides the following infor-
mation:
• The color gives information about the severity of the alarm:
– Red: Critical alarm (not used in this version)
– Orange: Major alarm
– Yellow: Minor alarm
– Blue: Warning
• A blue outline around the LED symbol indicates that an alarm has not yet been ac-
knowledged
• An LED symbol with a cross through it means that the alarm which has been sig-
naled is less severe than the setting made using the menu items:
<Options> <Settings> under “Alarm Severity Threshold” which governs which of the
alarms will be displayed.
Additional fault information and the notes on the fault clearance are given in Chapters
7.1.2 through 7.8.

7.1.2 Alarm List

For a clear display of all the alarms of the NE which being and has been notified to the
operating terminal during the operation (“Current” view) and in the past (“History” view),
you can use the alarm list. The history alarm list can contain up to 1000 entries. It can
also prove useful for recording the alarms which are occurring in intervals.
You can display the alarm list by using the main menu items:
<Fault> <Alarm List> in the main window of the application software.

1.Vorabzug:A30808-X3580-H504-1-7620 95
MMN Maintenance
SLD/T16-2.5

Fig. 7.1 View of All Individual Alarm Messages in the Alarm List (Example)

Select the alarm severities to be taken into a consideration for displaying and whether
be acknowledged or be unacknowledged alarms for displaying. Only these alarms ap-
pear in the list.
Using the menu items: <Options> <Settings: Open at Startup; Alarm List> you can have
the alarm list opened each time the software starts.

Fault Clearance
If the message in the alarm list already tells you what type of an alarm this is, you will
find details of fault clearance in the following Chapters:
• Fault clearance measures for equipment alarms see Chapter 7.2
• Fault clearance measures for transmission alarms see Chapter 7.3
• Fault clearance measures for alarms for general NE functions, shown in the Module
view, see Chapter 7.4
If you are unclear as to which type of alarm is involved, call the three types of view in
turn:
• Select the main menu items: <View> <Module View>:
If the alarm indicates an equipment fault, the relevant module symbol is red and
flashes or has a blue outline around it, depending on the setting made using the
menu items: <Options> <Settings: Alarm Flash>.
For fault clearance see Chapter 7.2.1.
• Select the menu items: <View> <Traffic View>:
When a functional unit is signaling a transmission alarm the associated functional

96 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

symbol is red and flashes or is outlined in blue, depending on the settings made us-
ing the menu items: <Options> <Settings: Alarm Flash>.
For fault clearance see Chapter 7.3.
• Select the menu items: <View> <Module view>:
When there is a module function fault in the NE the associated functional symbol is
red and flashes or is outlined in blue. For fault clearance see Chapter 7.4.

7.2 Fault Clearance Measures for Equipment Alarms

Equipment faults are subdivided into three different categories which trigger different
messages and also require different actions to localize the fault.
• Faulty module and module reporting fault are the same
(the fault reporting sensor is arranged at the faulty module)
– Case A
Fault message:
At the LCT alarms are displayed in the “Module View”.
The function of the module is effected but in many cases the traffic signals can
still be processed (the module remains operational).
– Case B
Fault message:
The red fault LED on the front of the module and the “A” LED on the Subrack
Alarm Panel (SRAP) lights. A-alarm messages also appear at the Bw7R signaling
interface to the LZE and to the ZBBeo
This is how serious equipment faults being and are displayed.

☞ Fault location for case A is described in Chapter 7.2.1,

Fault rectification for case B is described in Chapter 7.2.2.

• Module reporting alarm is not the same as the faulty module

– Case C
Faults have occurred outside the module by which they were detected:
The sensor is possibly arranged at a module which is not faulty, the fault has oc-
curred on another defective module. The fault cannot be localized uniquely to an
individual module (e.g. the fault on the interface between two modules).

☞ Notes on fault pinpointing for case C see Chapter 7.3.3.

7.2.1 Equipment Alarms at the LCT: Fault Pinpointing and Clearance

To display equipment alarms the Module View window is used at the LCT.

Conditions
The LCT is ready for operation – according to the information given in Chapter 6.2 – and
the application SW of the NE is started. There is an equipment alarm message at the
LCT.

1.Vorabzug:A30808-X3580-H504-1-7620 97
MMN Maintenance
SLD/T16-2.5

Display on the LCT

Select the menu items: <View> <Module View>. If there is an equipment fault present
the module view shows (at least) one module symbol (= module button) in red and flash-
ing or with a blue outline (depending on the settings made in the menu items: <Options>
<Settings: Alarm Flash>).

Fig. 7.2 Module View, Displaying an Equipment Alarm not yet Acknowledged
(Example)

98 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Fault Pinpointing
1. In the “Module View” use the right-hand mouse button to select the module symbol
reporting the alarm.
2. From the context-sensitive menu choose: <Fault> <Alarms>.
3. The alarm window for the faulty module appears and shows the list of all possible
equipment alarm messages for the module. Current alarms are marked with an LED
symbol in the color of the alarm severity. A blue outline to the symbol indicates that
the alarm has not yet been acknowledged. The title line of the alarm window also
gives the slot for the faulty module.
4. Acknowledge the alarm message, by selecting the appropriate entry from the alarm
window for example, use the right-hand mouse button to call the context-sensitive
menu and choose the menu item: <Acknowledge>. The blue outline of the LED sym-
bol disappears.
5. You will find the fault clearance measures required in Tab. 7.1 in the maintenance
measure column.

Possible Equipment Alarms and Required Maintenance Measures

Alarm type Meaning Maintenance Measure Remarks

Major Major module alarm Replace module –

Unavailable The SEMF function has placed the module Replace module –
in the “unavailable” state.

LTU Hardware fault in LTU interface module. Replace module LTU 1) Message only available
for module symbol EIPS1

EBSL Hardware fault in the EBSL module. Replace module EBSL Alarm message only
available for EIPS1 card
protection switching.

PSUTP Hardware fault in the PSUTP power sup- Replace module PSUTP Alarm message only
ply module. available for EIPS1 card
protection switching.

LOL T0 Loss of Lock T0 1. Check the external T3 clock reference sig- Message only available
Internal clock generator not synchronized. nals #1 and #2 at D subminiature connectors for module symbol CLL
G1 and H1 (subrack terminal panel), connec-
tions 4 and 8 respectively.
2. When an STM-N line signal is used for syn-
chronization check its clock precision.
3. Otherwise replace module CLL (special
hints see chapter 8.2.1).

LOL T4 Loss of Lock T4 If an LOL T0 alarm appears simultaneously, Message only available
Reference clock output signal not synchro- see maintenance measures for this alarm. for module symbol CLL
nized. Otherwise replace module CLL (special hints
see chapter 8.2.1).

Tab. 7.1 Equipment Alarms and Module Fault Clearance

1.Vorabzug:A30808-X3580-H504-1-7620 99
MMN Maintenance
SLD/T16-2.5

Alarm type Meaning Maintenance Measure Remarks

No 2Mbit No use of a CLL64-2 module when using
an external CLA box or malfunction of CLA
and / or CLL64-2 module, or loss of syn-
chronize mechanism of the 2 MBit/s.
Reference clock output signal not synchro-
nized.
First check if a CLL64-2 module or two ones Message only available
is/are used. Exchange each CLL module in case a CLA box is used
against a CLL64-2 one. Replace CLL64-2 when the CLL module is
module against a known good one. not replaced by a CLL64-
If an LOL T0 alarm appears simultaneously, 2 one, which must be
see maintenance measures for this alarm. there to use the CLA.
Otherwise replace module CLL64-2 (special
hints see chapter 8.2.1).

Flash SW Fault in FEPROM of SCU. The red fault Replace module SCU. Message only available
LED on the module also lights and an A- for module symbol
class Bw7R alarm is generated. SCU-R

Flash 1 Cfg. Fault in FEPROM 1 on the backplane Fault rectification by manufacturer service per- Message only available
(contains a copy of the current NE config- sonnel. for module symbol
uration). An A-class Bw7R alarm is gener- SCU-R
ated also.

Flash 2 Cfg. Fault in FEPROM 2 on the backplane Message only available

(contains a second copy of the current NE for module symbol
configuration). An A-class Bw7R alarm is SCU-R
generated also.

Ethernet fail Fault in the Ethernet Connection. Replace defect part. Message only available
Fault between SCU and Ethernet Cabling. for module symbol
1) No connection at the MDI-side of the SCU-R
MAU.
2) No connection at the AUI-side of the
MAU.
3) Broken cable either on the AUI or the
MDI side of the MAU used for the subrack.
4) MAU fault.

Tab. 7.1 Equipment Alarms and Module Fault Clearance

1)... For the LTU fault message you can determine the slot occupied by the faulty LTU
from the slot number of module symbol EIPS1 reporting the alarm (Module View) from
Tab. 7.2 and Tab. 7.3:

LTU Slot EIPS1 Slot

201 402

202 403

203 404

204 405

205 410

206 411

207 412

208 413

Tab. 7.2 Assignment of Modules LTU and EIPS1 in Subrack SLD16/SLT16

100 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

LTU Slot EIPS1 Slot

201 401

202 402

203 403

204 404

205 411

206 412

207 413
208 414

209 415

Tab. 7.3 Assignment of Modules LTU and EIPS1 in Subrack SLD16E/SLT16E

Fault Rectification
After you have localized the faulty module and acknowledged the alarm message, re-
place the faulty module – as described below. The alarm display then disappears.
However, if a further module alarm is still displayed, then the relevant module also has
to be replaced. If all the alarm displays have still not yet disappeared, update the alarm
display with the main menu items: <Window> <Update All Alarms>.
If an alarm is still being indicated even after this measure, special fault clearance has to
be performed on the NE (see Chapter 7.8).
For an equipment fault of module SCU first press the SHUT button on the front of the
i module to shut down the SCU and then press it once more to restart the SCU. If this
does not clear the fault, replace the SCU – as specified in Chapter 8.

Acknowledging the Alarm Message

• Acknowledge all equipment alarms for this module:
Select the module button reporting the alarm with the right-hand mouse button and
select the menu items: <Fault> <Acknowledge>.
After this menu item is selected in the Module View the blue outline disappears from
the module symbol or – if activated – the module symbol stops flashing, i.e. the
alarm was acknowledged.
• Acknowledging an individual alarm:
In the opened alarm window (for the module reporting the fault) select the line for the
relevant alarm, use the right-hand mouse button to call the context-sensitive menu
and select the menu items: <Acknowledge>.
The blue outline for the symbol disappears.

Replacing the Module

Replace the module identified as being faulty according to the sequence specified in
Chapter 8.2. Perform the necessary settings on the new module as specified in Chapter
8.3 (if applicable).

Updating the Alarm Display

Alarms displayed in the alarm window can be updated by selecting the main menu
items: <Window> <Update Window>.

1.Vorabzug:A30808-X3580-H504-1-7620 101
MMN Maintenance
SLD/T16-2.5

Each spontaneous alarm message also updates the alarm display (provided that no
alarm suppression has been set).

Clearing the Alarm Message

Only after successful fault clearance will alarm displays on the operating terminal, on the
subrack alarm panel and at the module LEDs disappear.

Module Equipping
The cause of an equipment alarm can also be faulty module equipping.

Card State
The current card state is displayed to you after you have selected the module button with
the right-hand mouse button and chosen menu item <Information> <Card>.

☞ See also Chapter 3.8.

7.2.2 Serious Equipment Faults

Fault Situation:
A serious fault on a module causes it to fail. The module can no longer transmit an alarm
message. A fault can only still be reported to the LCT in a restricted way.

Fault Display:
The red fault LED on the front of the module lights. This does not affect the status of the
green service LED.
To prevent the transmission of undefined signals by the faulty module, the latter is
switched off automatically (disabled).

Fault Clearance:
Replace the fault-reporting module as described in Chapter 8.2. Make the necessary
settings on the new module as specified in Chapter 8.3 (if applicable).

7.2.3 Transmission Alarms in Module View

(see Fig. 7.3)
If the module reporting the fault is one that has interface functions in the line side direc-
tion or the tributary side direction, e.g. OIS4/4-2, you can also have transmission alarms
of this module displayed in the Module View.

Fault Pinpointing
1. Select the module button concerned (normally the module symbol is flashing for dis-
playing a transmission alarm but may be sometimes not colored red for a transmis-
sion alarm however). The lower part of the window displays a port list with
associated port symbols. The port symbol reporting the alarm is colored red and is
flashing or has a blue outline (depending on the settings made using the menu
items: <Options> <Settings: Alarm Flash>).

102 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

2. Select this port symbol with the right-hand mouse button and in the associated con-
text-sensitive menu select the menu item: <Subview>. The Traffic Flow window
opens.
3. Select the symbol reporting the alarm with the right-hand mouse button and select
the menu items: <Fault> <Alarms>.
4. The alarm window shows the possible transmission alarms which can be detected
by this module, the current alarm entries and/or the alarm suppressions set. In the
case of line or ring protection it is also possible to make settings for traffic-carrying
modules as to whether the corresponding alarm messages are to be displayed or
not (selection field “No Alarm Report”).
Current alarms are marked with an LED symbol in the color of the alarm severity. A
blue outline to the symbol indicates that the alarm has not yet been acknowledged.
The title line of the alarm window also gives the slot of the module which has detect-
ed the transmission fault as well as the relevant port.
5. Acknowledge the alarm message by selecting the corresponding entry in the alarm
window for example, call the context-sensitive menu with the right-hand mouse but-
ton and choose the menu item: <Acknowledge>. The blue outline for the symbol dis-
appears.
6. Details of the fault clearance measures necessary can be found in the tables in
Chapter 7.3.2.2.

☞ For additional information on acknowledging the alarm message, replacing

modules, updating the alarm display, clearing the alarm display etc., see
Chapter 7.2.1.

1.Vorabzug:A30808-X3580-H504-1-7620 103
MMN Maintenance
SLD/T16-2.5

Fig. 7.3 Module View: Calling Transmission Alarms (Example)

104 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

7.3 Fault Clearance Measures for Transmission Alarms

An SL16 device can transmit a faulty signal without detecting a fault itself. However, the
fault is detected by the SL16 receiving the faulty signal.
All faults in remote units transmitting incorrect signals can mostly be cleared by directly
replacing the module. Exceptions (examples):
• Transmission faults caused by the transmission medium (FO or copper cable) or
faulty regenerators in the transmission link. For a fiber optic (FO) transmission link a
fault can e.g. be caused by increased optical attenuation; for an electrical transmis-
sion link (copper cable), environmental conditions such as electromagnetic noise
pulses can also trigger transmission alarms.
For problems with an optical transmission link (FO), the optical receive power on the
optical connector of interface module OIS16/16-2 or OIS4/4-2 or OIS1 or OP (if
used) should always be checked.
• Hardware faults either in the exchange cabling (customer interface) or internally in
the subrack of the SLD/SLT or SLR16 (e.g. faults in backplane wiring).
• Faults caused by timing or synchronization problems, e.g. by incorrect configuration
of the synchronization sources of an NE in a line or ring network.
• Faults caused by incorrect cross-connections in functional unit CC.

7.3.1 Fault Pinpointing for Transmission Alarms

Conditions
The LCT is operational as specified in Chapter 6.2 and the application-SW of the NE has
been started. There is an alarm message at the LCT.

Display at the LCT

(see Fig. 7.4)
Select the main menu items: <View>. If there is a transmission alarm, there will be (at
least) one functional symbol colored red and flashing or with a blue outline (depending
on the settings made using the menu items: <Options> <Settings: Alarm Flash>) for a
specific traffic or transmission function.

1.Vorabzug:A30808-X3580-H504-1-7620 105
MMN Maintenance
SLD/T16-2.5

Fig. 7.4 Traffic View, Showing an Unacknowledged Transmission Alarm

(Example)

106 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Fault Pinpointing
1. In Traffic View select the functional symbol reporting the alarm.
2. The lower part of the window displays a port list with associated port symbols (does
not apply to functional symbol CC). The port symbol reporting the alarm is colored
red and is flashing or has a blue outline (depending on the settings made using
menu item <Options> <Settings: Alarm Flash>). Select this with the right-hand
mouse button and select menu item <Subview>.
3. Click on the traffic flow symbol reporting the alarm with the right-hand mouse button
and then in the context-sensitive menu select <Fault><Alarms>. In a number of cas-
es there is another level in-between to allow further sorting and you can reach this
using menu item Subview.
4. The appropriate alarm window is displayed and shows the list of all transmission
alarms monitored at this port and/or alarm suppressions set. In the case of line or
ring protection it is also possible to make settings for traffic-carrying modules as to
whether the corresponding alarm messages are to be displayed or not (selection
field “No Alarm Report”).
Current alarms are marked with an LED symbol in the color of the alarm severity. A
blue outline to the symbol indicates that the alarm has not yet been acknowledged.
The title line of the alarm window also gives the name and the slot of the module
which has detected the transmission fault as well as the relevant port.
5. Acknowledge the alarm message by selecting the corresponding entry in the alarm
window for example, call the context-sensitive menu with the right-hand mouse but-
ton and choose menu item <Acknowledge>.
6. Depending on the functional symbol and the traffic flow symbol reporting the alarm,
the possible fault clearance measures can be found in tables in Chapter 7.3.2.2.

☞ For additional information on acknowledging the alarm message, replacing

modules, updating the alarm display, clearing the alarm display etc., see
Chapter 7.2.1.

7.3.2 Evaluating Transmission Alarms at the LCT

7.3.2.1 Interplay of SDH Maintenance Signals

With reference to ITU-T Recommendation G.782, Fig. 7.5 shows which external mes-
sages an NE transmits for its part when it receives transmission alarms.
The Alarms LOA, LOM, and SQM are evaluated from switching network to line direction.

1.Vorabzug:A30808-X3580-H504-1-7620 107
MMN Maintenance
SLD/T16-2.5

Synchronous
Port
LOS AIS (AU4) AU4

LOF [A1, A2] AU to STM-1

AIS (MS) [K2]

NE
SD (Bit error MSOH)
“Line” level
AIS
RDI (MS) [K2]
(AU4)
RDI (MS) [K2]

SD (Bit error RSOH) [B1]

Plesiochronous
Port
AIS
(AU4)
AIS (AU4) [H1,H2=1] AIS H4

LOA (AU4) 140 Mbit/s

LOM (AU4)

LOP (AU4)

SQM (AU4)

RDI (VC4) [G1]

VC-4 level
RDI (VC4) [G1]

SD (Bit error VC-4) [B3]

TIM [J1]
[...] SOH bytes
Detection
UNEQ
Creation
UNEQ

Fig. 7.5 Interplay of the SDH Maintenance Signals at the SL16

7.3.2.2 Fault Clearance Tables

For the individual functional units/symbols the tables below specify the possible alarm
messages, their meaning, the probable fault causes and the recommended procedures
for fault clearance. The tables relate to how the alarms are displayed on the LCT.

☞ In the following tables the “maintenance measures” column lists the possible
causes of the fault and/or specifications for how to clear it. In cases where
these measures do not bring results you will find further information about fault
clearance in Chapter 7.3.4.

108 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Explanations and Notes on the Tables below:

Explanation 1 If for example an Alarm AIS (AU4) or RDI (MS) is detected in a

for internal com- functional unit, this functional unit transmits an AIS which gener-
munication ates follow-up alarm SSF in the downstream functional unit (no
alarm SSF own cause of the fault).
A synchronous input signal can never contain an SSF alarm
message.

Explanation 2 For a manual laser start click in <View> <Module View> on the
for Manual La- module button for the desired OIS16/16-2 (or OIS4/4-2 or OIS1),
ser Start select the corresponding port symbol with the right-hand mouse
button and choose <Subview>. Select symbol STM16 (or STM4
or STM1) with the right-hand mouse button and then menu item
<Configuration> <STM16> (or <STM4> or <STM1>). Select but-
ton “Update”, choose the setting “Normal” under “Manual Laser
Restart Duration” and confirm with the <Apply> button. However
the setting “Force Laser Shutdown” may not be activated for this.

Note 1 Alarm LOF is not permanently visible. If it is received the laser

transmitter is automatically switched off. This results in a forced
shutdown of the remote end. The local OIS16/16-2 (or OIS4/4-2
or OIS1) module then detects LOS, alarm LOF is suppressed.
For measurements at the output of module OB note the following: Allowable input level
! of the measuring equipment (optical power meter, optical attenuation element)
>+15 dBm.

Functional Symbol OPT-PREAMP, Alarm Window “OP_..._OAS Alarm”,

Transmission Alarms and Fault Clearance

Alarm Type Meaning Maintenance Measures

RxFail (OAS) Receiver Fail Replace OP.

Output power failure of OP.

RxDeg (OAS) Receiver Degraded Possible reason: Ageing of pump laser.

Output power of OP too small. Restricted operation still possible but replace OP as pre-
ventive maintenance measure.

Tab. 7.4 Optical Preamplifier, Fault Clearance of Transmission Alarms

1.Vorabzug:A30808-X3580-H504-1-7620 109
MMN Maintenance
SLD/T16-2.5

Alarm Type Meaning Maintenance Measures

LOS (OAS) Loss of input signal 1. Read off the slot from the alarm window of module OP
Loss of input signal at OP; e.g. with laser shutdown in the reporting the fault. Use an optical attenuation element to
transmitter at remote end. establish a loop between the assigned transmitter output
(OIS16/16-2, OIS4/4-2, OIS1 or OB, if present) and the in-
put of the OP.
Attenuation settings:
– No OB used: 30 dB
– OB used: 40 dB.
Perform manual laser start (see explanation 2).
2. Is the LOS alarm still present?
Yes: Replace the OP. No: See point 3.
3. Refit OP, fault clearance at the local NE is ended.
Check the FO transmission link for unidirectional or bidi-
rectional fiber break. Check the optical transmitter at the
remote end (next NE in the direction of the signal source).

OAS = Optical Amplifier Section

Tab. 7.4 Optical Preamplifier, Fault Clearance of Transmission Alarms (Cont.)

Functional Symbol OPT-BOOST, Alarm Window “OB_..._OAS Alarm”,

Transmission Alarms and Fault Clearance

Alarm Type Meaning Maintenance Measures

TxFail (OAS) Transmission Fail Replace OB

Output power failure at OB.

TxDeg (OAS) Transmission Degraded Possible reason: Ageing of pump laser.

Output power too low at OB. Restricted operation still possible but replace OP as pre-
ventive maintenance measure.

OAS = Optical Amplifier Section

Tab. 7.5 Optical Booster, Fault Clearance of Transmission Alarms

Functional Symbol STM16, Traffic Flow Symbol STM16, Alarm Window “OIS16/16-
2 _...(2.5G)_STM16 Alarm”, Transmission Alarms and Fault Clearance

Alarm Type Meaning Maintenance Measures

TxFail (OS) Transmit fail Read off from the alarm window the slot of the faulty
Transmit signal failure for OIS16/16-2 and replace this module.
laser output power too low (does not apply for automatic la- Fault clearance is ended.
ser shutdown) or too high.
Critical laser transmitter fault, replacement necessary im-
mediately.

Tab. 7.6 STM-16 Alarms (OIS16/16-2), Fault Clearance

110 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Alarm Type Meaning Maintenance Measures

TxDeg (OS) Transmit degraded Read off from the alarm window the slot of the faulty
Reduced transmit power because of OIS16/16-2 and replace this module as a preventive mea-
– laser current too high or sure.
– temperature of laser too high or Fault clearance is ended.
– laser modulation current too high
Non-urgent laser transmitter fault, rectify as soon as possi-
ble.
LOS (OS) Loss of signal Note: LOS does not appear if an OP is connected to a re-
Missing receive signal on the line side. ceiver input! (if LOS was still generated despite the pres-
ence of an OP, POP can be faulty.)
1. Read off from the alarm window the slot of the OIS16/16-
2 reporting the fault. Use an optical attenuation element to
establish a loop between the transmitter output (OIS16/16-
2 or OB if present) and the receiver input (OIS16/16-2).
Attenuation settings:
– No OB used:
a) For 1300 nm low power laser: 10 dB
b) For 1300 nm standard power laser as well as for
1550 nm standard and high power laser: 20 dB
– OB used (1550 nm laser): 30 dB
– OB and OP used (1550 nm laser): 40 dB
– For WDM applications (1550 nm laser): 15 dB.
Perform manual laser start (see explanation 2).
2. Is the LOS alarm still present?
Yes: Replace the OIS16/16-2. No: See point 3.
3. Refit OIS16/16-2, fault clearance at the local NE is end-
ed.
Check the FO transmission link for interruption or strong in-
crease in optical attenuation (connecting cable, connec-
tors). Check the optical transmitter at the distant end (next
NE in the direction of the signal source).

TIM (RS) Trace Identifier Mismatch of Regenerator Section. Check whether RS-TTI was configured and activated on
Fault in the cabling between NEs. TIM monitoring is only the adjacent NE.
possible if the trail trace has been configured and activated If yes: Test the cabling to the adjacent NE (on the tributary
at two adjacent NEs: side or on the line side – according to the application).
Traffic View: Functional symbol STM16, Traffic Flow win-
dow: Functional symbol STM16, <Configuration> <Trail
Trace...> and <Configuration> <STM16: RS TTI Process-
ing: Enabled>

LOF (RS) Loss of frame See also Note1.

Loss of synchronization in the received line signal
(STM-16) when signal is too low or too high.
1. Read off from the alarm window the slot of the OIS16/16-
2 reporting the fault and replace this module.
2. Fault rectified?
Yes: Fault clearance is ended. No: See point 3.
3. Refit original OIS16/16-2, fault clearance at the local NE
is ended.
The optical transmitter at the distant end or a regenerator
along the optical transmission path is faulty.

Tab. 7.6 STM-16 Alarms (OIS16/16-2), Fault Clearance (Cont.)

1.Vorabzug:A30808-X3580-H504-1-7620 111
MMN Maintenance
SLD/T16-2.5

Alarm Type Meaning Maintenance Measures

AIS (MS) Multiplex section AIS On the line side determine the regenerator or line multiplex-
In the multiplex section (in the direction of the signal er reporting the fault and process the alarm here.
source) a regenerator signals that it is receiving a heavily
disturbed or no STM-16 data signal (e.g. alarms LOS,
LOF). To avoid follow-up faults in subsequent signal flow it
inserts the AIS signal.

RDI (MS) Remote Defect Indicator (Multiplex section)
A remote NE (multiplexer) signals that it has detected a far-
end error (AIS-MS or SD). The message comes from the
next multiplexer along, not from a regenerator.
1. Read off from the alarm window the slot of
the OIS16/16-2 module reporting the fault, determine the
transmit level at the own NE (at OIS16/16-2/OP):
- Traffic View: Functional symbol STM16, Traffic Flow win-
dow: Functional symbol STM16, <Information> <STM16>,
Laser Data: Output Power Level or
- Traffic View: Functional symbol OPT-PREAMP, Traffic
Flow window: Functional symbol OPT-PREAMP, <Config-
uration> <OPT-PREAMP>, Laser Data: Output Power
Transmit level to low?
Yes: The local NE is causing the error message. Replace
OIS16/16-2/OP. Fault clearance is ended.
No: see point 2.
2. Process the alarm at the next multiplexer on the line side
(in the transmission direction).

SD (MS) Signal degraded 1. Read off from the alarm window slot of OIS16/16-2 re-
The specified bit error threshold (SD threshold) in the re- porting the fault, establish a loop via an optical attenuation
ceived line signal was exceeded. element between the transmitter output and the receiver in-
put.
Attenuation settings:
– No OB used:
a) For 1300 nm low power laser: 10 dB
b) For 1300 nm standard power laser as well as for
1550 nm standard and high power laser: 20 dB
– OB used (1550 nm laser): 30 dB
– OB and OP used (1550 nm laser): 40 dB
– For WDM applications (1550 nm laser): 15 dB.
Is the fault message SD still there?
Yes: Replace OIS16/16-2. Check too whether OB or OP
are causing the fault message, replace if necessary. Fault
clearance is ended.
No: See point 2.
2. Cancel loop again. fault clearance at the local NE is end-
ed.
Test connection or link attenuation on the line side.
In the optical transmission path test the transmit module in
the neighboring multiplexer and possibly any regenerators
assigned in-between.

Tab. 7.6 STM-16 Alarms (OIS16/16-2), Fault Clearance (Cont.)

112 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Alarm Type Meaning Maintenance Measures

SSF (MS) Server signal fail SSF is a follow-up alarm (see explanation 1) in the ongoing
The digital signal is not available; internal communication internal signal flow. Therefore perform fault clearance for
alarm. the additional (primary) alarms signaled as detailed in
these tables.

OS = Optical Section (optical transmitter – FO – optical receiver)

RS = Regenerator Section
MS = Mulltiplex Section

Tab. 7.6 STM-16 Alarms (OIS16/16-2), Fault Clearance (Cont.)

Functional Symbol STM16, Traffic Flow Symbol 1+1MSP,

Alarm Window “OIS16/16-2_... (2.5G)_1+1 MSP Alarm”,
Transmission Alarms and Fault Clearance

Alarm Type Meaning Maintenance Measures

FOP (MSP- Failure of MSP Protocol Possible causes:

COLINE- for (1+1) line protection bidirectional. 1. An external protection switching command - e.g. lockout
CRS) Note: FOP can only be created if protection module - is present.
OIS16/16-2 is fault-free and not in the “forced” state. 2. The protection switching configurations of different NEs
of a multiplex section are different.

SSF (MSP- Server Signal Fail Possible causes:

TTPLINE) 1. Both the working and the protection section are faulty or
are delivering too many bit errors.
2. The present protection switching configuration prevents
a necessary switchover to the fault-free path.
3. An SF alarm has occurred in a transmission area and
the traffic of the associated OIS16/16-2 is selected. In ad-
dition module protection switching is active for this
OIS16/16-2 (because of a module fault or because of a
menu command request).

Tab. 7.7 STM-16 Alarms for (1+1) Line Protection Switching, Fault Clearance

Function Symbol STM16, Traffic Flow Symbol 1:1MSP,

Alarm Window “OIS16/16-2_... (2.5G)_1:1 MSP Alarm”,
Transmission Alarms and Fault Clearance

Alarm Type Meaning Maintenance Measures

FOP (MSPCO- Failure of MSP Protocol Possible causes:

LINEEX- for (1:1) line protection. 1. An external protection switching command - e.g. lockout
TRACRS) Note: FOP can only be reported in application SLT16 and - is present.
SLT16E on the line side. 2. The protection switching configurations of different NEs
of a multiplex section are different.
3. The protection switching architectures used in the indi-
vidual NEs are different.
4. The wrong signal was switched to the protection path
(main traffic/extra traffic).

Tab. 7.8 STM-16 Alarms for (1:1) Line Protection Switching, Fault Clearance

1.Vorabzug:A30808-X3580-H504-1-7620 113
MMN Maintenance
SLD/T16-2.5

Alarm Type Meaning Maintenance Measures

SSF (MSPTTP- Server signal fail Possible causes:

LINE) for main traffic 1. Both links (working/protection) have failed.
2. The protection circuit configuration which is set prevents
a necessary switchover to the fault-free path.
3. In the main traffic transmission range, an SF alarm has
occurred and the OIS16/16-2 module associated with the
main traffic is selected. In addition, for this OIS16/16-2
module, card protection switching is active (due to a mod-
ule fault or because it has been selected by a menu com-
mand).
4. A forced switchover request is in effect for the working
link, but this is in the SF state.
5. Due to a request from the card protection circuit system,
the protection card has selected the main traffic link. How-
ever, this is barred to avoid misconnection to the extra traf-
fic.

SS- (MSPTTP- Server signal fail Possible causes:

FEx- LINEEX- for extra traffic 1. Both links (working/protection) have failed.
tra TRA) 2. The protection circuit configuration which is set prevents
a necessary switchover to the fault-free path.
3. In the extra traffic transmission range, an SF alarm has
occurred and the OIS16/16-2 module associated with the
extra traffic is selected. In addition, for this OIS16/16-2
module, card protection switching is active (due to a mod-
ule fault or because it has been selected by a menu com-
mand).
4. The protection link is in the SF state.
5. The extra traffic is suppressed due to
– protection being activated on the working link
– an external switchover request, or
– an external command for card protection switchover
6. The extra traffic is being suppressed due to a failure of
the working module.

Tab. 7.8 STM-16 Alarms for (1:1) Line Protection Switching, Fault Clearance (Cont.)

114 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Functional Symbol STM16, Traffic Flow Symbol 2F-SPRING,

Alarm Window “OIS16/16-2_... (2.5G)_2F-SPRING Alarm”,
Transmission Alarms and Fault Clearance

Alarm Type Meaning Maintenance Measures

FOP (2F- Failure of MSP Protocol Possible causes:

SPRING) (for ring protection) 1. NEs in the ring have different K1/K2 protocols or
Note: FOP can only be generated if module OIS16/16-2 is 2. The MSP function was not created and switched to ac-
fault-free. tive in all NEs concerned in the ring (Traffic View: STM16,
Traffic Flow window, 2F-SPRING symbol), <Configura-
tion>, MS Activation → activated)
3. The adjacent NEs have not yet been defined: Node ID
East/West in Config window for 2F protection
4. The far end does not respond to the protection switch-
ing protocol, error at the distant station.

SSF- (2F- Server Signal Fail East Possible causes:

East SPRING) 1. A ring protection has occurred in the ring segment
which adjoins the NE (reporting the alarm) to the east (be-
cause of a broken fiber or a defective distant station for
example) and in addition one of the following has oc-
curred in one of the other ring segments
– a “Lockout” command is active or
– a “Forced to east / to west” switchover is present *) or
– a ring protection is in effect/requested (cause: signal
fail) *)
2. *) For the adjoining eastern ring segment a “Forced to
west” was configured and in addition a ring protection is in
effect/requested in one of the remaining ring segments
3. A “Lockout” command is active for the NE and in addi-
tion a ring protection is in effect/requested for the ring seg-
ment which adjoins the NE (reporting the alarm) to the
east.
*) ... Does not apply to segmented rings (operating termi-

nal setting: Traffic View, Traffic Flow window for the rele-
vant OIS16/16-2 port symbol, functional symbol 2F-
SPRING, menu item <Configuration: Segmentation
mode: enabled/disabled>).

Tab. 7.9 STM-16 Alarms for Ring Protection Switching 2F Without Extra Traffic, Fault Clearance

1.Vorabzug:A30808-X3580-H504-1-7620 115
MMN Maintenance
SLD/T16-2.5

Alarm Type Meaning Maintenance Measures

SSF- (2F- Server Signal Fail West Possible causes:

West SPRING) 1. A ring protection request has occurred in the ring seg-
ment which adjoins the NE (reporting the alarm) to the
west (e.g. because of a fiber break or because the distant
station is defective) and in addition in one of the other ring
segments
– a lockout command is active or
– a forced to east/to west switchover is present *) or
– a ring protection is present/requested (cause: signal
fail) *)
2. *) For the adjoining segment to the west a "forced to
east" was configured and in addition a ring protection is
present/requested in one of the other ring segments.
3. A "lockout" command is active for the NE and in addi-
tion there is a a ring protection requested/present for the
ring segment which adjoins the NE (signaling the alarm)
to the west.
*) ... Does not apply to segmented rings (operating termi-

nal setting: Traffic View, Traffic Flow window for the rele-
vant OIS16/16-2 port symbol, functional symbol 2F-
SPRING, menu item <Configuration: Segmentation
Mode: enabled/disabled>).

Tab. 7.9 STM-16 Alarms for Ring Protection Switching 2F Without Extra Traffic, Fault Clearance (Cont.)

116 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Functional Symbol STM16, Traffic Flow Symbol 2F-SPRING X,

Alarm Window “OIS16/16-2_... (2,5G)_2F-SPRING X Alarm”,
Transmission Alarms and Fault Clearance

Alarm Type Meaning Maintenance Measure

SSF- (2F- Server Signal Fail East Possible causes:

East SPRING X) 1. In the ring segment which borders the NE (signaling the
alarm) to the west there has been a ring protection re-
quest (e.g. because of a fiber interruption or because the
distant station is defective) and in addition in one of the
other ring segments
– a “Lockout” command is active or
– a “Forced to east / to west” switchover is present *) or
– a ring protection is present/requested (cause: signal
fail) *)
2. *) For the adjoining ring segment to the west a "Forced
to east" was configured and in addition a ring protection is
present/requested in one of the other ring segments.
3. A "Lockout" command is active for the NE and in addi-
tion there is a a ring protection requested/present for the
ring segment which adjoins the NE (signaling the alarm)
to the west.
*)... Does not apply to segmented rings (operating termi-
nal setting: Traffic View, Traffic Flow window for the rele-
vant OIS16/16-2 port symbol, functional symbol 2F-
SPRING, menu item <Configuration: Segmentation
Mode: enabled/disabled>).

SSF- (2F- Server Signal Fail West Possible causes:

West SPRING X) 1. A ring protection request has occurred in the ring seg-
ment which adjoins the NE (signaling the alarm) to the
west (e.g because the fiber is interrupted or a defective
distant station) and in addition, in one of the remaining
ring segments
– a “Lockout” command is active or
– a “Forced to east / to west” switchover is present *) or
– a ring protection is present/requested (cause: signal
fail) *)
2. *) For the adjoining segment to the west a "Forced to
east" was configured and in addition a ring protection is
present/requested in one of the other ring segments
3. A "Lockout" command is active for the NE and in addi-
tion there is a a ring protection requested/present for the
ring segment which adjoins the NE (signaling the alarm)
to the west.
*) ... Does not apply to segmented rings (operating termi-

nal setting: Traffic View, Traffic Flow window for the rele-
vant OIS16/16-2 port symbol, functional symbol 2F-
SPRING, menu item <Configuration: Segmentation
Mode: enabled/disabled>).

Tab. 7.10 STM-16 Alarms for 2F Ring Protection with Extra Traffic,
Fault Clearance

1.Vorabzug:A30808-X3580-H504-1-7620 117
MMN Maintenance
SLD/T16-2.5

Alarm Type Meaning Maintenance Measure

SSF- (2F- Server Signal Fail East Possible causes:

East SPRING X) In any of the ring segments
Extra – “Forced to west / to east” switchover is active or
– a ring protection request is present/requested or
– a “Manual to east / to west” switchover command is
present.

SSF- (2F- Server Signal Fail West Possible causes:

West SPRING X) In any ring segment
Extra – a “Forced to west / to east” switchover is active or
– a ring switchover request is present/requested or
– a “Manual to east / to west” switchover command is
present.

FOP (2F- Failure of MSP Protocol Possible causes:

SPRING X) (for ring protection). 1. NEs in ring have different K1/K2 protocols or
Note: FOP can only be created, if module OIS16/16-2 2. The MSP function was not switched to active in all NEs
east is fault-free. involved:
Traffic View: STM16, Traffic Flow window, symbol 2F-
SPRING, <Configuration>, MS Activation → activated
3. The neighboring NEs have not yet been defined: Node
ID east/west in Config window for 4F protection
4. The far end is not responding to the protection switch-
ing protocol, error at the distant station.

Tab. 7.10 STM-16 Alarms for 2F Ring Protection with Extra Traffic,
Fault Clearance (Cont.)

118 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Functional Symbol STM16, Traffic Flow Symbol 4F-SPRING,

Alarm Window “OIS16/16-2_... (2,5G)_4F-SPRING Alarm”,
Transmission Alarms and Fault Clearance

Alarm Type Meaning Maintenance Measure

SSF- (4F- Server Signal Fail East Possible causes:

East SPRING) 1. A ring protection request has occurred in the ring seg-
ment which adjoins the NE (signaling the alarm) to the
east (e.g because both fibers are interrupted or a defec-
tive distant station) and in addition, in one of the remaining
ring segments
– a further ring protection is present/requested *) or
– a span protection is present/requested or
– a "Forced Switch Ring" *) or "Forced Switch Span" is
configured or
– a "Lockout Protection Span" command is active or
– a further SSF alarm is signaled
2. A span protection request has occurred in the ring seg-
ment which adjoins the NE (signaling the alarm) to the
east (e.g because one fiber is interrupted) and in addition,
in one of the remaining ring segments a "Forced Switch
Ring" is present/requested
3. *) For the adjoining ring segment to the east a "Forced
Switch Ring" (east) was configured and in addition a ring
protection is present/requested in one of the remaining
ring segments
4. For the adjoining ring segment to the east a "Forced
Switch Span" (east) was configured and in addition in this
segment
– a ring protection request has occurred or
– there is a "Lockout Protection Span” request present
5. A "Lockout Protection Span” (east) command is active
in the adjoining ring segment to the east and in addition in
this segment
– a ring protection request has occurred or
– in the working path there is a span protection request
present.
6. A "Lockout Working Span (east) command is active in
the adjoining ring segment to the east and in
addition a span protection request has occurred in this
segment
7. A "Lockout Working Ring (east) command is active in
the adjoining ring segment to the east and in
addition a ring protection request has occurred in this seg-
ment
*) ... Does not apply to segmented rings (operating termi-

nal setting: Traffic View, Traffic Flow window for the rele-
vant OIS16/16-2 port symbol, functional symbol 2F-
SPRING, menu item <Configuration: Segmentation
Mode: enabled/disabled>).

Tab. 7.11 STM-16 Alarms for 4F-Ring Protection, Fault Clearance

1.Vorabzug:A30808-X3580-H504-1-7620 119
MMN Maintenance
SLD/T16-2.5

Alarm Type Meaning Maintenance Measure

SSF- (4F- Server Signal Fail West Possible causes:

West SPRING) 1. A ring protection request has occurred in the ring seg-
ment which adjoins the NE (signaling the alarm) to the
west (e.g because both fibers are interrupted or a defec-
tive distant station) and in addition, in one of the remaining
ring segments
– a further ring protection is present/requested *) or
– a span protection is present/requested or
– a "Forced Switch Ring" *) or "Forced Switch Span" is
configured or
– a "Lockout Protection Span" command is active or
– a further SSF alarm is signaled
2. A span protection request has occurred in the ring seg-
ment which adjoins the NE (signaling the alarm) to the
west (e.g because one fiber is interrupted) and in addition,
in one of the remaining ring segments a "Forced Switch
Ring" is present/requested
3. *) For the adjoining ring segment to the west a “Forced
Switch Ring (west)” was configured and in addition a ring
protection is present/requested in one of the remaining
ring segments
4. For the adjoining ring segment to the west a "Forced
Switch Span" (west) was configured and in addition in this
segment
– a ring protection request has occurred or
– a "Lockout Protection Span" request is present
5. A "Lockout Protection Span (west) command is active
in the adjoining ring segment to the west and in addition in
this segment
– a ring protection request has occurred or
– in the working path there is a span protection request
present.
6. A "Lockout Working Span (west) command is active in
the adjoining ring segment to the west and in addition a
span protection request has occurred in this segment
7. A "Lockout Working Ring (west) command is active in
the adjoining ring segment to the west and in addition a
ring protection request has occurred in this segment
*) ... Does not apply to segmented rings (operating termi-

nal setting: Traffic View, Traffic Flow window for the rele-
vant OIS16/16-2 port symbol, functional symbol 2F-
SPRING, menu item <Configuration: Segmentation
Mode: enabled/disabled>).

Tab. 7.11 STM-16 Alarms for 4F-Ring Protection, Fault Clearance (Cont.)

120 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Alarm Type Meaning Maintenance Measure

FOP (4F- Failure of MSP Protocol Possible causes:

SPRING) Note: FOP can only be created if module OIS16/16-2 east 1. NEs in ring have different K1/K2 protocols or
for protection is fault-free. 2. The MSP function was not switched to active in all NEs
involved:
Traffic View: STM16, Traffic Flow window, Symbol 4F-
SPRING, <Configuration>, MS Activation → activated
3. The neighboring NEs have not yet been defined: Node
ID East/West in Config window for 4F protection
4. The distant station is not responding to the protection
switching protocol, error at the distant station.

Tab. 7.11 STM-16 Alarms for 4F-Ring Protection, Fault Clearance (Cont.)

Functional Symbol STM16, Traffic Flow Symbol AU4/VC4,

Alarm Window “OIS16/16-2 _...(2.5G)_AU4/VC4 #... Alarm”,
Transmission Alarms and Fault Clearance

Alarm Type Meaning Maintenance Measures

LOA (AU4) Loss of (AU) concatenation alignment;
The single VC-4s of a virtual concatenated signal arrive
with a time delay of more than 125 microseconds between
the slowest and the fastest VC-4. No concatenation con-
version to contigous is possible.
a) Local NE: SNCP switch not equal for all single VC-4s?
If TRUE: Switch all VC-4s manually to one direction.
When the OIS16/16-2 module reporting the fault is ar-
ranged on the line side:
Fault in preceding NE on the optical transmission link (but
not in the regenerator):
– error in alignments processing
– faulty connection to a neighboring chained VC-4.
b) VC-4s routed on different physical paths?
If TRUE: Reconfigure the path so that all VC-4s are trans-
mitted over the same physical fiber.
When the OIS16/16-2 module reporting the fault is ar-
ranged on the tributary side:
Fault in preceding NE on the tributary side:
– error in alignments processing
– faulty connection to a neighboring chained VC-4.

Tab. 7.12 AU4/VC4 Alarms (OIS16/16-2), Fault Clearance

1.Vorabzug:A30808-X3580-H504-1-7620 121
MMN Maintenance
SLD/T16-2.5

Alarm Type Meaning Maintenance Measures

LOP (AU4) Loss of AU pointers
8 consecutive, inconsistent pointers were received on the
line side / tributary side (depending on how the OIS16/16-
2 is used); this invalidates the VC-4 content.
1. In the local NE: Bit errors can produce pointer violations.
Read off from the alarm window the slot of module
OIS16/16-2 reporting the fault and replace this module.
2. Fault cleared?
Yes: Fault clearance is ended. No: see item 3.
3. Refit the original OIS16/16-2 module, fault clearance at
the local NE is ended.
a) When the OIS16/16-2 module reporting the fault is ar-
ranged on the line side:
Fault in preceding NE on the optical transmission link (but
not in the regenerator):
– error in pointer processing
– faulty connection to a neighboring chained VC-4.
b) When the OIS16/16-2 module reporting the fault is ar-
ranged on the tributary side:
Fault in preceding NE on the tributary side:
– error in pointer processing
– faulty connection to a neighboring chained VC-4.

LOM (AU4) Loss of (AU) concatenation multiframe
24 consecutive, inconsistent multiframes were received on
the line side / tributary side (depending on how the
OIS16/16-2 is used); this invalidates the VC-4-Xv content.
No concatenation conversion is possible.
a) Check Cross Connections. Wrong VC-4 arrived, wrong
path Configured? When the OIS16/16-2 module reporting
the fault is arranged on the line side:
Fault in preceding NE on the optical transmission link (but
not in the regenerator):
– error in multiframe processing
– faulty connection to a neighboring chained VC-4.
b) Bit Errors? When the OIS16/16-2 module reporting the
fault is arranged on the tributary side:
Fault in preceding NE on the tributary side:
– error in multiframe processing
– faulty connection to a neighboring chained VC-4.

SQM (AU4) Channel order of virtual concatenated signals is not cor- Check order of cross connections and sort VC-4 channels
rect. in the correct order.
– Correct order: 1, 2, 3, 4 in case of a VC-4-4v.
– Correct order: 1, 2, 3, ..., 15, 16 in case of a VC-4-16v. a) Check Cross Connections. Wrong VC-4 arrived. Wrong
path configured? When the OIS16/16-2 or OIS4/4-2 mod-
ule reporting the fault is arranged on the line side:
Fault in preceding NE on the optical transmission link (but
not in the regenerator):
– error in multiframe processing
– faulty connection to a neighboring chained VC-4
b) Bit Errors? When the OIS16/16-2 or OIS4/4-2 module
reporting the fault is arranged on the tributary side:
Fault in preceding NE on the tributary side:
– error in multiframe processing
– faulty connection to a neighboring chained VC-4.

Tab. 7.12 AU4/VC4 Alarms (OIS16/16-2), Fault Clearance (Cont.)

122 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Alarm Type Meaning Maintenance Measures

AIS (AU4) AIS (AU4) received No activities are necessary at the local NE.
In a preceding device on the line side / tributary side (de- a) The OIS16/16-2 reporting the fault is arranged on the
pending on how the OIS16/16-2 is used) an STM-1 digital line side (see module slot):
signal is faulty. The fault is caused – seen in the direction of the signal
source – by the first NE along the optical transmission path
which is not (yet) reporting any AIS (AU4) alarm by
– Fault between a port and the functional unit Multiplex
Section Adaptation in this NE
– Fault in the optical line to this NE (e.g. fiber break)
– Equipment fault in the NE which is upstream from the NE
defined above (without AIS alarm).
b) The OIS16/16-2 reporting the fault is arranged on the
tributary side (see module slot):
On the tributary side the fault is caused – seen in the direc-
tion of the signal source – by the first NE which is not (yet)
reporting any AIS (AU4) alarm by
– Fault in a tributary line to this NE
– Equipment faults in the NE which is upstream from the
NE defined above (without AIS alarm).

RDI (VC4) Remote Defect Indicator (VC4)
Message in VC-4 that on the line side / tributary side (de-
pending on how the OIS16/16-2 is used) the distant station
(end of the path) is receiving heavily disturbed data signals
- Alarms AIS (AU4), LOF, LOS, LOP (AU4) or SD.
1. At the distant station (multiplexer on the line side / NE on
the tributary side), localize which reverse direction alarm is
causing message RDI (VC4) and rectify fault there if nec-
essary.
2. Read off from the alarm window the slot of module
OIS16/16-2 reporting the fault and determine its transmit
level:
Traffic View: Functional symbol STM16, Traffic Flow win-
dow: Functional symbol STM16, <Information> <STM16>,
Laser Data: Output Power Level.
Transmit level to low?
Yes: The local NE is causing the fault message. Test/re-
place the optical modules involved in the faulty signal in
turn in the local NE. Fault clearance is ended.
No: see item 3.
3. Test whether the entire VC-4 path is configured correct-
ly, otherwise the distant station receives AIS (AU4) – caus-
es alarm RDI (VC4).

SSF (VC4) Server signal fail SSF is a follow-up alarm (see explanation 1) in the ongoing
The digital signal is not available; internal communication internal signal flow. Therefore perform fault clearance for
alarm. the additional (primary) alarms signaled as detailed in
these tables.

UNEQ (VC4) Unequipped No activities are necessary at the local NE.

The VC-4 path concerned contains no operating signal (in- (Depending on how the OIS16/16-2 is being used), this
advertently or intentionally) at its start. message comes from
– a remote multiplexer in the SDH network on the line side
or
– an NE on the tributary side.
No cross connection is created there for this VC-4 path for
example.

Tab. 7.12 AU4/VC4 Alarms (OIS16/16-2), Fault Clearance (Cont.)

1.Vorabzug:A30808-X3580-H504-1-7620 123
MMN Maintenance
SLD/T16-2.5

Alarm Type Meaning Maintenance Measures

SD (VC4) Signal degraded 1. Read off from the alarm window the slot of the
In an AU-4 path the specified bit error threshold was ex- OIS16/16-2 reporting the fault and replace this module.
ceeded on the route between the start of the path and the 2. Fault rectified?
monitoring point (in the OIS16/16-2). Yes: Fault clearance is ended. No: See point 3.
3. Refit OIS16/16-2, fault clearance at the local NE is end-
ed.
a) The OIS16/16-2 reporting the fault is arranged on the
line side (see module slot):
The multiplexer of the distant station (line side) or the opti-
cal transmission path is faulty. To pinpoint the fault, inves-
tigate the alarm lists and performance records at the
individual NEs in the direction of the signal source for fault
information.
b) The OIS16/16-2 reporting the fault is arranged on the
tributary side (see module slot):
An NE on the tributary side or a tributary line is faulty. To
pinpoint the fault, investigate the alarm lists of the individ-
ual NEs at the tributary side in the direction of the signal
source.

TIM (VC4) Trace Identifier Mismatch Check whether the entire VC-4 path from start to end is
Fault is path through connection. Monitoring by the path correctly configured/switched.
identification is only possible when the Trail Trace Identifier
(TTI) configuration has been undertaken and its evaluation
is switched on.

Tab. 7.12 AU4/VC4 Alarms (OIS16/16-2), Fault Clearance (Cont.)

Function Symbol STM4, Traffic Flow Symbol STM4,

Alarm Window “OIS4/4-2_...(622M)_STM4 Alarm”,
Transmission Alarms and Fault Clearance

Alarm Type Meaning Maintenance Measures

TxFail (OS) Transmit fail In the alarm window, read off the slot for the faulty OIS4/4-
Failure of the transmit signal when the laser output power 2 module and replace this module.
is too low (not after an automatic laser shutdown) or too This completes fault clearance.
high.
Urgent fault in the laser transmitter, immediate replace-
ment required.

TxDeg (OS) Transmit degraded In the alarm window, read off the slot for the faulty OIS4/4-
Reduced transmission power due to 2 module and replace this module as a preventive mea-
– excessive laser bias current or sure.
– laser temperature too high, or This completes fault clearance.
– excessive laser modulation current
Non-urgent fault in the laser transmitter, remedy as soon
as possible.

Tab. 7.13 STM-4 Alarms (OIS4/4-2), Fault Clearance

124 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Alarm Type Meaning Maintenance Measures

LOS (OS) Loss of signal 1. In the alarm window, read off the slot for the OIS4/4-2
There is no STM-4 receive signal at the tributary input port. module which is reporting the fault. Using an optical
attenuator, create a loop between the transmitter output
(OIS4/4-2 or OB, if there is one) and the receiver input
(OIS4/4-2).
Attenuation settings:
– No OB in use: 15 dB; but 30 dB if an OIS4/4-2 with a high
power laser (1550 nm) is being used
– OB in use: 40 dB.
Carry out a manual laser start (see explanation 2).
2. Does the LOS alarm persist?
Yes: replace the OIS4/4-2 module. No: see item 3.
3. Re-insert the OIS4/4-2 module, this completes fault
clearance on the local NE.
Investigate the tributary side of the FO cable link for a
break or for very excessive optical attenuation (connecting
cable, connector). Investigate the optical transmission
module at the far end (nearest NE towards the signal
source).

LOF (RS) Loss of frame See also note 1.

Loss of synchronization in the tributary input signal 1. In the alarm window, read off the slot for the OIS4/4-2
(STM-4). module which is reporting the fault and replace this
module.
2. Has the fault cleared?
Yes: fault clearance completed. No: see item 3.
3. Re-insert the OIS4/4-2 module, this completes fault
clearance on the local NE.
On the tributary side, one of the optical transmission
modules along the transmission path is faulty.

AIS (MS) Alarm indication signal Carry out alarm processing on the tributary side at the
The SDH distant end on the tributary side is reporting that distant end.
it is receiving a heavily disturbed data signal, or none at all.
To avoid secondary errors in the subsequent signal flow
(towards the local NE), it sends the AIS signal as a substi-
tute.

RDI (MS) Remote defect indicator 1. Read off from the alarm window the slot of module
The SDH distant end on the tributary side is reporting that OIS4/4-2 reporting the fault, at the own NE (at OIS4/4-2)
it has detected a return direction fault. determine transmit level:
Traffic View: Functional symbol STM4, Traffic Flow win-
dow: Functional symbol STM4, <Information> <STM4>,
Laser Data: Output Power Level.
Transmit level too low?
Yes: The local NE is the source of the fault report. Replace
the OIS4/4-2. This completes fault clearance.
No: see item 2.
2. Carry out alarm processing on the tributary distant end
(towards the subscriber). Check the corresponding
tributary lines.

Tab. 7.13 STM-4 Alarms (OIS4/4-2), Fault Clearance (Cont.)

1.Vorabzug:A30808-X3580-H504-1-7620 125
MMN Maintenance
SLD/T16-2.5

Alarm Type Meaning Maintenance Measures

SD (MS) Signal degraded 1. Read off from the alarm window the slot of module
The specified bit error threshold (SD threshold) for the OIS4/4-2 reporting the fault and on the tributary side create
tributary input signal has been exceeded. a test loop between the relevant transmitter output and re-
ceiver input via an optical attenuation element.
Attenuation settings:
– No OB used: 15 dB; but 30 dB if an OIS4/4-2 with high
power laser (1550 nm) is used
– OB used: 40 dB.
Does the SD fault message persist?
Yes: Replace OIS4/4-2. Fault clearance is ended.
No: see item 2.
2. Remove test loop. Fault clearance at the local NE is
ended.
On the tributary side, test the connection and line attenua-
tion and also the optical transmitter of the distant station.

SSF (MS) Server signal fail SSF is a secondary alarm (see Explanation 1) arising in
The digital signal is not available; internal communication the course of the internal signal flow. Consequently, fault
alarm. clearance should be performed for the additional (primary)
alarms which are reported, as specified in the tables.

TIM (RS) Trace Identifier Mismatch of Regenerator Section. Check on the tributary side whether RS-TTI was config-
Fault in the cabling between NEs. TIM monitoring is only ured and activated at the adjacent NE.
possible when the trail trace was configured and activated If it was: Test the cabling to the adjacent NE on the tribu-
on two adjacent NEs: tary side.
Traffic View: Functional symbol STM4, Traffic Flow win-
dow: Functional symbol STM4, <Configuration> <Trail
Trace...> and <Configuration> <STM4: RS TTI Process-
ing: Enabled>

OS = Optical section (optical transmitter - FO - optical receiver)

RS = Regenerator Section
MS = Mulltiplex Section

Tab. 7.13 STM-4 Alarms (OIS4/4-2), Fault Clearance (Cont.)

Function Symbol STM4, Traffic Flow Symbol 1+1MSP,

Alarm Window “OIS4/4-2_... (622M)_1+1 MSP Alarm”,
Transmission Alarms and Fault Clearance

Alarm Type Meaning Maintenance Measures

FOP (MSPCOLINECRS) Failure of MSP Protocol Possible causes:

1. There is an external protection switching command -
Note: FOP can only be created when pro- e.g. lockout - present.
tection module OIS4/4-2 is fault-free and 2. In the ongoing signal path on the tributary side there are
not in the “forced” state. conflicting protection switching configurations.

Tab. 7.14 STM-4 Alarms for (1+1) Protection Switching on the Tributary Side,
Fault Clearance

126 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Alarm Type Meaning Maintenance Measures

SSF (MSPTTPLINE) Server signal fail Possible causes:

1. Both the working and the protection links are faulty or
are giving excessive bit errors.
2. The protection switching configuration which is set pre-
vents a necessary switchover to the fault-free path.
3. In one of the transmission ranges, an SF alarm has
occurred and the traffic associated with the corresponding
OIS4/4-2 module is selected. In addition, the card protec-
tion switching is active for this OIS4/4-2 module (due to a
module fault).

Tab. 7.14 STM-4 Alarms for (1+1) Protection Switching on the Tributary Side,
Fault Clearance (Cont.)

Function Symbol STM4, Traffic Flow Symbol 4xAU4/VC4,

Alarm Window “OIS4/4-2 _...(622M)_AU4/VC4 #.. Alarm”,
Transmission Alarms and Fault Clearance

Alarm Type Meaning Maintenance Measures

LOP (AU4) Loss of AU-4 pointers 1. In the local NE: bit errors result in pointer corruption;
8 consecutive inconsistent pointers have been received on occurs at the STM-4 interface concerned. In the alarm
the tributary side; this invalidates the content of the VC-4. window, read off the slot for the OIS4/4-2 module which is
reporting the fault and replace this OIS4/4-2.
2. Has the fault been cleared?
Yes: fault clearance completed. No: see item 3.
3. Re-insert the OIS4/4-2 module, this completes fault
clearance on the local NE. Fault in the distant end
(tributary side):
– incorrect pointer processing
– misconnection to a neighboring, linked VC-4 path.

AIS (AU4) AIS (AU4) received No activities are required on the local NE.
On the tributary side, an STM-4 digital signal (towards the The fault occurred in the first multiplexer module along the
subscriber) has been corrupted in a preceding SDH tributary signal path - looking towards the signal source –
device. which has not (yet) issued an AIS (AU4) alarm, due to
– a fault in this multiplexer module,
– a fault on the link between the subscriber and this multi-
plexer module.

Tab. 7.15 AU4/VC4 Alarms (OIS4/4-2), Fault Clearance

1.Vorabzug:A30808-X3580-H504-1-7620 127
MMN Maintenance
SLD/T16-2.5

Alarm Type Meaning Maintenance Measures

RDI (VC4) Remote defect indicator (VC-4) 1. At the distant end on the tributary side, localize which
Message in the VC-4, indicating that the distant end (end return direction alarm is causing the RDI (VC4) message /
of VC-4 path on the tributary side) is receiving heavily dis- if necessary clear the fault there.
turbed data signals – AIS (AU4), LOF, LOS, LOP (AU4) or 2. Is the LCT (for the local NE) showing another alarm in
SD alarms. the “Traffic View” for the STM4 functional unit? If so, from
the alarm window read off the slot for the OIS4/4-2 module
which is reporting the fault and replace this module.
3. Otherwise, check the appropriate lines on the tributary
side.
4. Check that the entire VC-4 path is correctly configured,
or else the distant end will receive an AIS signal on the
tributary side.

SSF (VC4) Server signal fail SSF is a secondary alarm (see Explanation 1) arising in
The digital signal is not available; internal communication the course of the internal signal flow. Consequently, fault
alarm. clearance should be performed for the additional (primary)
alarms which are reported, as specified in the tables.

SQM (VC4) Server signal fail SSF is a secondary alarm (see Explanation 1) arising in
The digital signal is not available; internal communication the course of the internal signal flow. Consequently, fault
alarm. clearance should be performed for the additional (primary)
alarms which are reported, as specified in the tables.

UNEQ (VC4) Unequipped No activities are required on the local NE.

At the tributary side there is no operating signal at the start This message is issued by a multiplexer module in the
of the VC-4 path under consideration. tributary path. The VC-4 path is not equipped, not switched
through or interrupted.

SD (VC4) Signal degraded 1. In the alarm window, read off the slot for the OIS4/4-2
The specified bit error threshold (SD threshold) for the module which is reporting the fault and set up a test loop
tributary input signal has been exceeded. on the tributary side between the transmitter output con-
cerned and the receiver input, using an optical attenuator.
Attenuation settings:
– No OB in use: 15 dB; but 30 dB if an OIS4/4-2 with a high
power laser (1550 nm) is being used
– OB in use: 40 dB.
Does the SD error report persist?
Yes: replace the OIS4/4-2. This completes fault clearance.
No: see item 2.
2. Remove the test loop. This completes fault clearance on
the local NE.
The multiplexer module for the tributary distant end
(towards the signal source) or the corresponding tributary
FO cables are faulty.

TIM (VC4) Trace Identifier Mismatch Check that the entire VC-4 path has been correctly
Fault in path through connection. Monitoring by the path configured / connected from beginning to end.
identification is only possible when the Trail Trace Identifier
(TTI) configuration has been undertaken and its evaluation
is switched on.

Tab. 7.15 AU4/VC4 Alarms (OIS4/4-2), Fault Clearance (Cont.)

128 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Functional Symbol STM1 (opt.), Traffic Flow Symbol STM1, Alarm Window
“OIS1_...(155M)_STM1 Alarm”,
Transmission Alarms and Fault Clearance

Alarm Type Meaning Maintenance Measure

TxFail (OS) Transmit fail In the alarm window, read off the slot of the OIS1 module
Transmit signal failure for which is reporting the fault and replace this module.
laser output power too low (does not apply for automatic la- Fault clearance is ended.
ser shutdown) or too high.
Major laser transmitter fault, immediate replacement re-
quired.

TxDeg (OS) Transmit degraded In the alarm window, read off the slot of the OIS1 module
Transmit power reduced by which is reporting the fault and replace this module as a
– laser bias current too high or preventive measure.
– laser temperature too high or Fault clearance is ended.
– laser modulation current too high
Minor laser transmitter fault, rectify as soon as possible.

LOS (OS) Loss of signal 1. In the alarm window, read off the slot of the OIS1 module
Missing STM-1 receive signal at the tributary input port. which is reporting the fault and set up a test loop between
the OIS1 transmitter output and receiver intput using an
optical attenuator.
Attenuation setting: 15 dB.
Perform manual laser start (see explanation 2).
2. Does the LOS alarm persist?
Yes: Replace module OIS1. No: see item 3.
3. Refit the original module OIS1, fault clearance at the lo-
cal NE is completed.
On the tributary side, investigate the FO transmission link
for a break or very greatly increased optical attenuation
(connection cable, connector) . Investigate the distant sta-
tion optical transmit module (next NE in the direction of the
signal source).

LOF (RS) Loss of frame See also note 1.

Loss of synchronization in tributary input signal (STM-1).
1. In the alarm window, read off the slot of the OIS1 module
which is reporting the fault and replace this module.
2. Fault cleared?
Yes: Fault clearance is ended. No: see item 3.
3. Refit the original module OIS1, fault clearance at the lo-
cal NE is completed.
On the tributary side an optical transmit module along the
transmission path is faulty.

AIS (MS) Alarm Indication Signal On the tributary side at the distant station perform alarm
The SDH remote station on the tributary side signals that it processing.
is already receiving a heavily disturbed data signal or no
data signal. To avoid follow-up errors in the subsequent
signal flow (direction of local NE), it inserts this protection
signal AIS.

Tab. 7.16 STM-1 Alarms (OIS1), Fault Clearance

1.Vorabzug:A30808-X3580-H504-1-7620 129
MMN Maintenance
SLD/T16-2.5

Alarm Type Meaning Maintenance Measure

RDI (MS) Remote Defect Indicator 1. In the alarm window, read off the slot of the OIS1 module
The SDH distant station on the tributary side reports that it which is reporting the fault, at the own NE (at OIS1) deter-
has detected a remote defect. mine the transmit level:
Traffic View: Functional symbol STM1 (opt.), Traffic Flow
window: Functional symbol STM1, <Information>
<STM1>, Laser Data: Output Power Level.
Transmit level too low?
Yes: The local NE is causing the fault message. Replace
OIS1. Fault clearance is ended.
No: see item 2.
2. Perform alarm processing at the tributary distant station
(in the subscriber direction). Check the corresponding trib-
utary lines.

SSF (MS) Server signal fail SSF is a follow-up alarm (see explanation 1) in the ongoing
The digital signal is not available; internal communication internal signal flow. Therefore perform fault clearance in
alarm. accordance with the information given in the tables for ad-
ditional (primary) alarms reported.
SD (MS) Signal degraded 1. In the alarm window, read off the slot of the OIS1 module
The specified bit error threshold (SD threshold) for the trib- which is reporting the fault and on the tributary side, set up
utary input signal was exceeded. a test loop between the relevant transmitter output and re-
ceiver input using an optical attenuator.
Attenuation setting: 15 dB.
Does fault message SD persist?
Yes: Replace OIS1. Fault clearance is ended.
No: see item 2.
2. Remove test loop. Fault clearance at the local NE is
ended.
On the tributary side test the connection and the link atten-
uation and also the optical transmitter of the distant station

TIM (RS) Trace Identifier Mismatch of Regenerator Section. Check on the tributary side whether RS-TTI has been con-
Fault in the cabling between NEs. TIM monitoring is only figured and activated at the adjacent NE.
possible when the Trail Trace was configured and activat- If it has been: Check the cabling on the tributary side to the
ed at two adjacent NEs: adjacent NE.
Traffic View: Functional symbol STM1(opt.), Traffic Flow
window: Functional symbol STM1, <Configuration> <Trail
Trace...> and <Configuration> <STM1: RS TTI Process-
ing: Enabled>

OS = Optical Section (optical transmitter - FO - optical receiver)

RS = Regenerator Section
MS = Mulltiplex Section

Tab. 7.16 STM-1 Alarms (OIS1), Fault Clearance (Cont.)

130 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Functional Symbol STM1 (opt.), Traffic Flow Symbol 1+1MSP, Alarm Window
“OIS1_... (155M)_1+1 MSP Alarm”, Transmission Alarms and Fault Clearance

Alarm Type Meaning Maintenance Measure

FOP (MSPCOLINECRS) Failure of MSP Protocol Possible causes:

1. An external protection switching command
Note: FOP can only be created if protection - e.g. lockout - is present.
module OIS1 is fault-free and not in the 2. In the ongoing signal path on the tributary side there are
“forced” state. conflicting protection switching configurations.

SSF (MSPTTPLINE) Server Signal Fail Possible causes:

1. Both the working and the protection section are faulty or
are delivering too many bit errors.
2. The existing protection switching configuration is pre-
venting a necessary switchover to the fault-free path.
3. The alarm SF has occurred in one transmission area
and the traffic of the associated module OIS1 is selected.
In addition card release switching is active for this module
OIS1 (because of a module fault).

Tab. 7.17 STM-1 Alarms (OIS1) for (1+1) Protection on the Tributary Side,
Fault Clearance

Functional Symbol STM1 (opt.), Traffic Flow Symbol AU4/VC4, Alarm Window
“OIS1_...(155M)_AU4/VC4 Alarm”, Transmission Alarms and Fault Clearance

Alarm Type Meaning Maintenance Measure

LOP (AU4) Loss of AU-4 pointers 1. In the local NE: Bit errors produce pointer violations; oc-
8 consecutive, inconsistent pointers were received on the curs at the relevant STM-1 interface. In the alarm window,
tributary side; this invalidates the VC-4 content. read off the slot of the OIS1 module which is reporting the
fault and replace the OIS1 module.
2. Fault cleared?
Yes: Fault clearance is ended. No: see Item 3.
3. Refit original module OIS1, fault clearance at the local
NE is completed. Fault at the distant station (tributary
side):
– incorrect pointer processing
– bad connection to an adjacent, chained VC-4 path.

AIS (AU4) AIS (AU4) received No activities are necessary at the local NE.
On the tributary side an STM-1 digital signal is disturbed in The fault will be caused by the first multiplex module - seen
an upstream SDH device (in the subscriber direction). in the signal source direction - along the tributary signal
path which has not (yet) reported an AIS (AU4) alarm, by a
– fault in this multiplex module
– fault in the link between the subscriber and this multiplex
module.

Tab. 7.18 AU4/VC4 Alarms (OIS1), Fault Clearance

1.Vorabzug:A30808-X3580-H504-1-7620 131
MMN Maintenance
SLD/T16-2.5

Alarm Type Meaning Maintenance Measure

RDI (VC4) Remote Defect Indicator (VC-4) 1. On the tributary side localize at the distant station which
Message in the VC-4, indicating that the distant end (end reverse direction alarm is causing the RDI message (VC4)
of VC-4 path on the tributary side) is receiving heavily dis- and - if applicable - rectify the fault there.
turbed data signals – AIS (AU4), LOF, LOS, LOP (AU4) or 2. Does the LCT (for the local NE) show a further alarm for
SD alarms. functional unit STM1 in the Traffic View? Then, in the alarm
window, read off the slot of the OIS1 module which is re-
porting the fault and replace this module.
3. Otherwise check the corresponding lines on the tributary
side.
4. Check whether the entire VC-4 path is configured cor-
rectly, otherwise the distant station on the tributary side re-
ceives an AIS signal.

SSF (VC4) Server signal fail SSF is a follow-up alarm (see explanation 1) in the ongoing
The digital signal is not available; internal communication internal signal flow. Therefore perform fault clearance in
alarm. accordance with the information given in the tables for ad-
ditional (primary) alarms reported.

UNEQ (VC4) Unequipped No activities are necessary at the local NE.

The VC-4 path observed is not receiving any working sig- A multiplex module in the tributary path delivers this mes-
nal at its start on the tributary side. sage. The VC-4 path is not seized, not through connected
or is interrupted.

SD (VC4) Signal degraded 1. In the alarm window, read off the slot of the OIS1 module
The specified bit error threshold (SD threshold) for the trib- which is reporting the fault and, on the tributary side, set up
utary input signal was exceeded. a test loop between the relevant transmitter output and re-
ceiver input using an optical attenuator.
Attenuation setting: 15 dB.
Does fault message SD persist?
Yes: Replace OIS1. Fault clearance is ended.
No: see item 2.
2. Remove test loop. Fault clearance at the local NE is
ended.
The multiplex module of the tributary distant station (in the
direction of the signal source) or the corresponding tribu-
tary FO line are faulty.

TIM (VC4) Trace Identifier Mismatch Check whether the entire VC-4 path, from start to finish, is
Fault in path through connection. Monitoring by path iden- correctly configured/switched.
tifier is only possible if the Trail Trace Identifier (TTI) con-
figuration has been undertaken and its evaluation is
activated.

Tab. 7.18 AU4/VC4 Alarms (OIS1), Fault Clearance (Cont.)

132 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Functional Symbol STM1 (el.), Traffic Flow Symbol STM1, Alarm Window
“EIPS1_...(155M)_STM1-Alarm”, Transmission Alarms and Fault Clearance

Alarm Type Meaning Maintenance Measures

LOS (ES) Loss of signal 1. Read off from the alarm window the slot of the EIPS1 re-
Missing STM-1 receive signal at the tributary input port. porting the fault and replace this module, check/ if neces-
sary replace associated LTU (see Tab. 7.2 and Tab. 7.3).
2. Fault rectified?
Yes: Fault clearance is ended. No: See point 3.
3. Refit EIPS1/LTU, fault clearance at the local NE is end-
ed.
Check the corresponding tributary lines for interruptions.
Check the interface module of the tributary remote station
(in the direction of the signal source).

TIM (RS) Trace Identifier Mismatch of Regenerator Section. Check on the tributary side whether RS-TTI has been con-
Fault in the cabling between NEs. TIM monitoring is only figured and activated at the adjacent NE.
possible when the Trail Trace was configured and activat- If it has been: Check the cabling on the tributary side to the
ed at two adjacent NEs: adjacent NE.
Traffic View: Functional symbol STM1(el.), Traffic Flow
window: Functional symbol STM1, <Configuration> <Trail
Trace...> and <Configuration> <STM1: RS TTI Process-
ing: Enabled>

LOF (RS) Loss of frame 1. Read off from the alarm window the slot of the EIPS1 re-
Loss of synchronization in the tributary input signal porting the fault and replace this module, check/ if neces-
(STM-1). sary replace associated LTU (see Tab. 7.2 and Tab. 7.3).
2. Fault rectified?
Yes: Fault clearance is ended. No: See point 3.
3. Refit EIPS1, fault clearance at the local NE is ended.
Check the corresponding tributary lines for interruptions.
Check the interface module of the tributary remote station
(in the direction of the signal source).

AIS (MS) Alarm Indication Signal On the tributary side at the distant station perform alarm
The SDH remote end on the tributary side signals that it is processing.
already receiving a heavily disturbed data signal or no data
signal. To avoid follow-up errors in the subsequent signal
flow (direction of local NE) it inserts this protection signal
AIS.

RDI (MS) Remote Defect Indicator 1. Read off from the alarm window the slot of the EIPS1 re-
The SDH remote end on the tributary side signals that it porting the fault and replace this module (poss. faulty
has detected a defect on its receiving side. transmit signal), check/ if necessary replace associated
LTU (see Tab. 7.2 and Tab. 7.3).
2. Fault rectified?
Yes: Fault clearance is ended. No: See point 3.
3. Refit EIPS1/LTU, fault clearance at the local NE is end-
ed.
Carry out alarm processing at the tributary distant station
(in the direction of the subscriber). Test the corresponding
tributary lines.

Tab. 7.19 STM-1 Alarms (EIPS1), Fault Clearance

1.Vorabzug:A30808-X3580-H504-1-7620 133
MMN Maintenance
SLD/T16-2.5

Alarm Type Meaning Maintenance Measures

SSF (MS) Server signal fail SSF is a follow-up alarm (see explanation 1) in the ongoing
The digital signal is not available; internal communication internal signal flow. Therefore perform fault clearance for
alarm. the additional (primary) alarms signaled as detailed in
these tables.

SD (MS) Signal degraded 1. Read off from the alarm window the slot of the EIPS1 re-
The specified bit error threshold (SD threshold) for the trib- porting the fault and create a test loop between the rele-
utary input signal was exceeded. vant input and output ports of the tributary side. Is the SD
error message still there?
Yes: Replace EIPS1. Fault clearance is ended.
No: See point 2.
2. Remove test loop. Fault clearance at the local NE is
ended.
Test the corresponding tributary lines and check there con-
nectors for bad contact. Check the multiplex module of the
tributary distant station.

ES = Electrical Section (transmit interface – electr. line – receive interface)

RS = Regenerator Section
MS = Mulltiplex Section

Tab. 7.19 STM-1 Alarms (EIPS1), Fault Clearance (Cont.)

Functional Symbol STM1 (el.), Traffic Flow Symbol AU4/VC4, Alarm Window
“EIPS1_...(155M)_AU4/VC4 Alarm”, Transmission Alarms and Fault Clearance

Alarm Type Meaning Maintenance Measures

LOP (AU4) Loss of AU pointers 1. In the local NE: Bit errors can result in pointer violations;
8 consecutive inconsistent pointers were received on the occurs at the relevant STM-1 interface. Read off from the
tributary side; this invalidates the VC-4 content. alarm window the slot of the EIPS1 reporting the fault and
replace the EIPS1.
2. Fault rectified?
Yes: Fault clearance is ended. No: See point 3.
3. Refit EIPS1, fault clearance at the local NE is ended.
Fault in the adjacent multiplex module (tributary side):
– error in pointer processing
– faulty connection to an adjacent, chained VC-4 path.

AIS (AU4) AIS (AU4) received No activities are required at the local NE.
An STM-1 digital signal is faulty in a preceding SDH device Viewed in the direction of the signal source – from the first
on the tributary side (in the subscriber direction). multiplex module along the tributary signal path which is
not (yet) signaling any AIS (AU4) alarm – the fault is
caused by
– Fault in this multiplex module
– Fault on the route between subscriber and this multiplex
module.

Tab. 7.20 AU4/VC4 Alarms (EIPS1, SDH), Fault Clearance

134 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Alarm Type Meaning Maintenance Measures

RDI (VC4) Remote Defect Indicator (VC-4)
Message in VC-4, that the remote station (VC-4 path end
on the tributary side) is receiving heavily disturbed data
signals – alarms AIS (AU4), LOF, LOS, LOP (AU4) or SD.
1. On the tributary side locate at the remote station the
alarm which is causing the RDI message (VC4) / rectify the
fault there if necessary.
2. Does the LCT (for the local NE) display a further alarm
of functional unit STM1 in the Traffic View? Then read off
from the alarm window the slot of the EIPS1 reporting the
alarm and replace this module.
3. Otherwise test the corresponding lines of the tributary
side.
4. Test whether the entire VC-4 path is correctly config-
ured, otherwise the remote station on the tributary side re-
ceives an AIS signal.

SSF (VC4) Server signal fail SSF is a follow-up alarm (see explanation 1) in the ongoing
The digital signal is not available; internal communication internal signal flow. Therefore perform fault clearance for
alarm. the additional (primary) alarms signaled as detailed in
these tables.

UNEQ (VC4) Unequipped No activities are required at the local NE.

The VC-4 path concerned contains no operating signal on A multiplexer module on the tributary path delivers this
the tributary side at its start. message. The VC-4 path is not seized, not through con-
nected or interrupted.

SD (VC4) Signal degraded 1. Read off from the alarm window the slot of the EIPS1 re-
The specified bit error threshold (SD threshold) for the trib- porting the fault, create a test loop between the relevant in-
utary input signal was exceeded. put and output ports of the tributary side. Does the SD error
message still occur?
Yes: Replace EIPS1, check/if necessary replace associat-
ed LTU (see Tab. 7.2 and Tab. 7.3). Fault clearance is
ended.
No: See point 2.
2. Remove test loop. Fault clearance at the local NE is
ended.
The multiplexer module of the tributary distant station (in
the direction of the signal source) or the corresponding trib-
utary lines are faulty.

TIM (VC4) Trace Identifier Mismatch Check whether the entire VC-4 path from start to end is
Fault in path through connection. Monitoring by path iden- correctly configured/switched.
tifier is only possible if the Trail Trace Identifier (TTI) con-
figuration has been undertaken and its evaluation is
activated.

Tab. 7.20 AU4/VC4 Alarms (EIPS1, SDH), Fault Clearance (Cont.)

Functional group symbol CC (Cross-Connections) does not supply any transmission

i alarm information.

1.Vorabzug:A30808-X3580-H504-1-7620 135
MMN Maintenance
SLD/T16-2.5

Functional Symbol E4, Traffic Flow Symbol E4,

Alarm Window “EIPS1_...(140M)_E4 Alarm”,
Transmission Alarms and Fault Clearance

Alarm type Meaning Maintenance Measures

LOS (E4) Loss of signal 1. Read off from the alarm window the slot of the EIPS1 re-
Missing PDH receive signal (140 Mbit/s) on the tributary porting the fault and replace this module, check/if neces-
side. sary replace the associated LTU (see Tab. 7.2 and
Tab. 7.3).
2. Fault rectified?
Yes: Fault clearance is ended. No: See point 3.
3. Refit EIPS1n, fault clearance at the local NE is ended.
Test the corresponding tributary lines for interruptions.
Check the interface module of the tributary distant station
(in the direction of the signal source).

AIS (P4) (E4-)AIS received On the tributary side in the subsequent NE (in the direction
The 140-Mbit/s-PDH receive signal on the tributary side is of the signal source) investigate error messages.
disturbed the AIS protection signal is supplied.

Note: This alarm is also used to detect when a PDH chan-

nel is not occupied by traffic.

E4, P4 ... PDH area (140 Mbit/s)

Tab. 7.21 E4 Alarms (EIPS1, PDH), Fault Clearance

Functional Symbol E4, Traffic Flow Symbol VC4,

Alarm Window “EIPS1_...(140M)_VC4-Alarm”,
Transmission Alarms and Fault Clearance

Alarm type Meaning Maintenance Measures

RDI (VC4) Remote Defect Indicator (VC-4) 1. At the multiplexer reporting the fault, localize which re-
A remote multiplexer (at the path end of the line side) sig- verse direction alarm is causing the “RDI (VC4)” message
nals a distant end error – AIS (AU4), SD, LOF, LOP (AU4), and - if applicable - rectify the fault there.
LOS – in VC-4 path. 2. At the local NE, test the transmit level of the relevant
OIS16/16-2:
Traffic View: Functional symbol STM16, Traffic Flow win-
dow: Functional symbol STM16, <Information> <STM16>,
Laser Data: Output Power Level.
Transmit level too low?
Yes: The local NE is causing the error message. Check/re-
place the modules involved in the faulty signal (OIS16/16-
2, OP – if present) in the local NE in turn. Fault clearance
is ended.
No: See point 3.
3. Test whether the entire VC-4 path is configured correct-
ly, otherwise the distant station receives AIS (AU4) – caus-
es alarm RDI (VC4).

Tab. 7.22 VC4 Alarms (EIPS1, PDH), Fault Clearance

136 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Alarm type Meaning Maintenance Measures

SSF (VC4) Server signal fail SSF is a follow-up alarm (see explanation 1) in the ongoing
The digital signal is not available; internal communication internal signal flow. Therefore perform fault clearance for
alarm. the additional (primary) alarms signaled as detailed in
these tables.

SD (VC4) Signal degraded The fault is probably not in the local NE but on the line side
The specified bit error threshold (SD threshold) in the VC- in a preceding device or transmission subsection between
4 path was exceeded. the NE reporting the fault and the start of the path. Pinpoint
the error step-by-step from NE to NE with test loops (on
module SNL – Traffic View, symbol CC – set).

TIM (VC4) Trace Identifier Mismatch Check whether the entire VC-4 path, from start to finish, is
Fault in path through connection. Monitoring by path iden- correctly configured/switched.
tifier is only possible if the Trail Trace Identifier (TTI) con-
figuration has been undertaken and its evaluation is
activated.

PLM (VC4) Payload Mismatch Alarm appears with shared operation with non-
Payload type and composition not suitable. ETSI/ITU-T conformant NEs (deviations in path identifica-
tion pattern).
The path identification is wrongly configured, test/modify
the setting of the expected identification at the local device
too:
Traffic View, select functional symbol E4, open window
Traffic Flow via the port symbol, choose symbol VC4,
Menu item <Configuration> <Trail Trace>.
Other possible fault: The path types are different.

UNEQ (VC4) Unequipped The fault is outside the NE. The VC-4 path is not seized,
The own NE can show a fault in path through connection not through-connected or interrupted.
or a remote multiplexer in the SDH network (line side) sig-
nals that the corresponding VC-4 path contains no operat-
ing signal.

E4, P4 ... PDH area (140 Mbit/s)

Tab. 7.22 VC4 Alarms (EIPS1, PDH), Fault Clearance (Cont.)

Note on monitoring for the unequipped message:

i To test a path (e.g. during the commissioning phase when no traffic has yet been
switched) an unequipped message can be intentionally inserted at the beginning of a
VC-4 path, to discover incorrect circuits.
In this case the activated function HSUM/HSUG (Higher Order Supervisory Unequipped
Monitoring/Generator) allows full path monitoring since only the combination of the Un-
equipped message (Byte C2 carries an “all zero” signal) with the path information (TTI
= zero) causes alarm signaling. This occurs when the VC-4 path which is only occupied
by “unequipped” is interrupted at a particular point.

This requires the configurations listed below:

1. Select symbol STM1 (el./opt.) in Traffic View, then select the corresponding port
symbol with the right-hand mouse button and choose <Subview> to open the Traffic
Flow window.
2. VC-4 configuration:
Select symbol AU4/VC4 in the Traffic Flow window with the right-hand mouse button
and select menu item <Configuration> <AU4/VC4>.
In field VC4 for TTI processing select the setting “Enabled” and for

1.Vorabzug:A30808-X3580-H504-1-7620 137
MMN Maintenance
SLD/T16-2.5

Connection Supervision Mode the setting “Supervisory UNEQ”.

Confirm with Apply.
3. Configuration of the Trail Trace:
Select symbol AU4/VC4 in the Traffic Flow window with the right-hand mouse button
and select menu item <Configuration> <Trail Trace>. Mark selection fields “all binary
zero trace” for “Transmitted” and “Expected”. Confirm with Apply.
Possible VC-4 alarm: “TIM”.

7.3.3 Transmission Alarms within an NE

Faults in the transmission of signals between two modules of an NE (interface errors,
e.g. “Internal HW link error” or error between OP and OIS16/16-2) generate transmis-
sion alarms which are signaled by the own or by a neighboring NE.
When an error of this type is suspected the alarm messages should be read out from
the alarm list (see Chapter 7.1.2). From the type of alarm messages and the explana-
tions given in the tables in Chapter 7.3.2.2 for the alarms feedback about the faulty mod-
ules can be obtained.
Information such as “which channels are affected by the error message?”, “from which
direction did the message come (west/east/tributary)?” etc. can help to localize the error.
An LOS or LOF alarm points to an error in the module issuing the signal (e.g. OP),
whereas AIS points to a faulty receiver module (e.g. OIS16/16-2).

7.3.4 Further Notes for Fault Pinpointing to Transmission Alarms

The large number of possible network structures means that the information on fault lo-
calization given in Chapter 7.3.2 only covers some of the possible sources of faults. In
addition the maintenance personnel will be required to draw conclusions about the prob-
able location of an error from an available combinations of transmission alarm messag-
es at the LCT.
Typical fault patterns in Chapter 7.3.4.1 as well as the assigned alarm signaling scenar-
ios should provide support here.
In some case it makes sense to set up test loops (see 7.3.4.2).
An uninterrupted test of the outgoing (electrical) tributary signals (see 7.3.4.3) can also
be used for fault pinpointing.
Just as helpful can be information which you obtain from the alarm list “History” (see
Fig. 7.1), the TCN list (see Chapter 3.10.1), the performance log windows (see Chapter
3.10.2) and the various log records (see Chapter 3.9).

Fault Pinpointing in Regeneration Sections

For transmission faults you can use management facilities LCT/NCT/OS to request via
communication channel ECC as to whether the associated NEs can be reached or not.
In line networks you can scan NE by NE from the monitoring point to the regeneration
section affected by the fault and in doing so request the relevant alarm messages in the
individual NEs. NEs on that side of the interrupt point cannot be interrogated. With inter-
ruptions an error structure like that shown in Fig. 7.6 occurs.
In ring networks you can pinpoint the faulty NE by interrogations in both directions.
In intermeshed networks, after a specific reconfiguration time, each NE – even the two
NEs of a faulty regeneration section – will respond to an interrogation.

138 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

As a result of the automatic laser safety shutdown both adjacent NEs will signal an LOS
alarm for both unidirectional and bidirectional interruption. To distinguish between them
initiate a manual laser start at both NEs (see explanation 2 in Chapter 7.3.2.2): LOS
alarm at both NEs means bidirectional interruption (cable interrupted), LOS at only one
NE unidirectional interruption (fiber break).
You can undertake further fault pinpointing to HW faults (OIS16/16-2, if nec. OB) in one
of the two NEs or to cable faults by measuring the optical power at the transmitter output
and at the cable output (receive side) after a manual laser start.

Faults in the ECC Channel

Such faults don‘t generate alarms.Therefore it is recommended to periodically (e. g. ev-
ery six month) check all ECC channels in use as follows:
At the operating terminal select the functional symbol “MCF” in the “Module view” by a
right-hand mouse click and choose “Subview” in the context menu. A window “Message
Communication Functions” is opened in which you should select the desired DCC but-
ton (#1 to #15) with a right-hand mouse click. Choose menu item <Configuration>. In the
appropriate window you may read the actual state of the DCC connection (Enabled/Dis-
abled) in an indication area “MCF Linkage State”.

7.3.4.1 Fault Patterns for Link Faults (Examples)

STM-16 multiplex section

STM-16
regeneration
section outgoing
AIS (only
Alarm for ports,
Alarms Alarms SSF (VC-4), which are
LOS/LOF/TIM (RS) AIS (MS) if monitoring seized by
SSF (MS) active traffic from
interrupt-
AIS (MS),
ed MS)
AIS (MS)- (transmitted
generation transparently) SLT/ PDH port
SLD RDI (VC-4) AIS(PDH)
SLD/
SLR16 AIS (MS) SLR16 AIS (MS)
SLT
for RDI (MS) SDH port AIS(SDH)
remote ALS: ALS for LOS
AIS (SDH) for remote ALS:
Auxiliary AIS(AUX)
or AIS (PDH) LOS alarm,
port
local ALS and
RDI (MS) inser-
tion RDI (VC-4) alarm,
for remote
ALS: without remote ALS: when monitoring active
alarms RDI (MS) and additionally
SSF (MS) - for active monitoring - remote ALS = Automatic laser shutdown at the remote NE
SSF (VC-4) RDI (VC-4) alarm

Note: SSF alarms of a transmission function are only reported if no alarm suppression was set for them

Fig. 7.6 Interruption in a Regeneration Section

1.Vorabzug:A30808-X3580-H504-1-7620 139
MMN Maintenance
SLD/T16-2.5

outgoing
AIS (only
Alarms Alarm for ports,
LOS/LOF/ SSF (VC-4), which are
TIM (RS), when monitor- seized by
SSF (MS) ing active traffic from
interrupted
MS)
PDH port
RDI (VC-4) AIS (PDH)
SLD/ RDI (MS)
SLT
ALS SDH port AIS (SDH)
for
for LOS
remote ALS: for remote ALS:
AIS (SDH) LOS alarm, Auxiliary AIS (AUX)
SLT/
or AIS (PDH) local ALS and port
SLD
RDI (MS) insertion
for
remote ALS: without remote ALS: for active monitoring
alarms RDI (MS) and additionally Alarm RDI (VC-4)
SSF (MS) and - for active monitoring -
SSF (VC-4), RDI (VC-4) alarm
for active
monitoring
remote ALS = Automatic laser shutdown at the remote NE

Note: SSF alarms of a transmission function are only reported if no alarm suppression was set for them

Fig. 7.7 Interruption in a Multiplex Section

Alarms
LOS/LOF/TIM (RS)/AIS (MS)/ Alarms Alarms
LOP (AU4), SSF (MS)1) AIS (AU4), AIS (AU4),
SSF (VC-4) SSF (VC-4) SSF (VC-4)
AIS (AU4)- AIS (AU4)-
Insertion refreshed
RDI
SLT/ SLT/ SLT/ (VC4)
AIS (AU4) AIS (AU4) AIS (PDH)
SLD SLD SLD SLT/
SLD
140 Mbit/s STM-16 STM-16 STM-16 140 Mbit/s

Alarm Alarm Alarm

RDI (VC-4) RDI (VC-4) RDI (VC-4)

1) only in the case of LOS, LOF, TIM (RS) or AIS (MS)

AIS (MS) is only possible in the case of an MS section which contains regener-
ators or with a forced AIS insertion in a multiplexer which is suitable for it (e.g.
for test purposes)

Note: SSF alarms of a transmission function are only reported if no alarm suppression was set for them

Fig. 7.8 Interruption of the VC-4 Path

140 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Case 1: Failure of the 140-Mbit/s signal

Transmit AIS (PDH) transparently

no no
Alarm LOS (PDH) alarm alarm
AIS (PDH)- AIS1) AIS1) PDH-
insertion (PDH) (PDH) port
PDH-
MUX PDH PDH SLT/ SLT/ SLT/ AIS (PDH)
LT LT SLD SLD SLD
140 Mbit/s
140-Mbit/s source 140 Mbit/s STM-16 STM-16

no RDI (VC-4) inser-

tion
Case 2: Incoming AIS (PDH)
Transmit AIS (PDH) transparently

no no
AIS (PDH) alarm alarm alarm
AIS (PDH)-
insertion AIS1) AIS1) PDH-
AIS
(PDH) (PDH) (PDH) port
PDH-
MUX PDH PDH SLT/ SLT/ SLT/ AIS (PDH)
LT LT SLD SLD SLD
140 Mbit/s
140-Mbit/s- 140 Mbit/s 140 Mbit/s STM-16 STM-16
source AIS2)
(PDH)
no RDI (VC-4) in-
sertion
1) “mapped” in a valid VC-4
2) not “refreshed” but “mapped” in VC-4
PDH-LT: Line Termination 140 Mbit/s
PDH-MUX: PDH multiplexer

Fig. 7.9 Interruption in 140-Mbit/s Signal Path

7.3.4.2 Test Loops on Traffic Path

For support in fault pinpointing you can configure signal loopbacks at VC-4 level in mod-
ule SNL for each line and tributary port.
Create a test loop: In Traffic View select functional symbol CC with the right-hand mouse
button and select menu item <Cross Connections>. Then create a bidirectional connec-
tion for the desired termination point:
1. Action: Connect
2. CC type: Bidirectional
3. Termination points TPA and TPB are identical.
4. Confirm with apply.
Test loops cause TIM alarms in the entire area of the network for which the loop is ef-
i fective.
Reason: the transmitted and looped back path identification are different.

1.Vorabzug:A30808-X3580-H504-1-7620 141
MMN Maintenance
SLD/T16-2.5

7.3.4.3 Measuring the Tributary Output Signals

To monitor the electrical tributary output signals there are four coaxial monitor jacks M1
through M4 (channel 1 to 4) available on each EIPS1 module.
A suitable PDH and SDH analyzer can be used to check the functionality of the traffic
connections to be monitored. Checking of this type does not disturb the operation of the
system.

7.3.4.4 Test Loops on Equipment Control (LAN Access)

and Management Path (TMN)
For information (see 6.2.1) in its last paragraph.

7.4 Fault Clearance Measures for Alarms

of General NE Functions
(see Fig. 7.10)
The module function view is used at the LCT to display alarms of general NE functions.

Conditions
LCT is ready for operation according to the information given in Chapter 6.2 and the ap-
plication SW of the NE is started. There is an alarm message at the LCT.

Display at the LCT

Select the main menu items: <View>. If one of the NE functions shown in this view indi-
cates a fault its functional symbol will be colored red to show the alarm message. The
symbol is also flashing or has a blue outline (depending on the settings made using
menu items: <Options> <Settings: Alarm Flash>).

Fault Pinpointing
1. In Module view select the functional symbol reporting the alarm with the right-hand
mouse button.
2. If functional symbol SEC or Subrack is reporting the alarm:
Select <Fault> <Alarms> from the context-sensitive menu.
3. If functional symbol OH-IF is reporting the alarm:
Select menu item <Subview>, select the symbol reporting the alarm (Channel 1 or
Channel 2) with the right-hand mouse button and choose <Fault> <Alarms> from the
context-sensitive menu.
4. The associated alarm window appears and shows a list of all alarms monitored un-
der this function containing entries for current alarms or alarm suppressions. Current
alarms are marked with an LED symbol in the color of the alarm severity. A blue out-
line to the symbol points to the fact that this alarm has not yet been acknowledged.
The title line of the alarm window – for symbols SEC and OH-IF – gives the module
(and in some cases the slot) which detected the fault, as well as – in the case of sym-
bol OH-IF – the relevant port 1 or 2 as well.
5. Acknowledge the alarm message, by selecting the corresponding alarm entry from
the alarm list for example, call the context-sensitive menu with the right-hand mouse
button and choose menu item <Acknowledge>.
6. Depending on the functional symbol reporting the alarm, the tables below, 7.23
through 7.26 give possible fault clearance measures.

142 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Fig. 7.10 Module view, Display of Alarms (Example)

1.Vorabzug:A30808-X3580-H504-1-7620 143
MMN Maintenance
SLD/T16-2.5

Functional Symbol SEC, Alarm Window “CLL_SEC Alarm”,

Alarms and Fault Clearance

Alarm type Meaning Maintenance Measures

FCA The FEC and the CONCATENATION ACTIVE having a 1. Occurs in case of BSHR Ring in which one Span is set
fault. to FEC and one span is set to Concatenation.
Clearance with setting the function for all involved devices
The FEC and the Concatenation switches are Active at the in the ring for either FEC or Concatenation only.
same time. FEC and concatenation are not allowed on different spans
Concatenated traffic is lost. in a ring at the same time.
2. An error has occurred in the devices using FEC and
Concatenation at the same time.
Replace the involved modules using both functions.

LOST4 The T4 output clock signal will be suppressed since at the Are switches G2 and H2 on the terminal panel (T3/T4-
moment there is no reference source which meets the min- clock adaptation 75 Ω unsymmetrical or 120 Ω symmetri-
imum clock quality in automatic selection mode. cal) set correctly? Check available clock reference(s) for
clock deviations, rectify fault.
T0 Quality The reference clock source selected at the moment for T0 Check available clock reference(s) for clock deviations,
is worse than the defined minimum clock quality level (op- rectify fault.
erating mode: automat. selection). An alarm is generated if
no other clock reference of the required quality is available;
change to holdover mode.

LOS T3#1 No input signal at 2048-kHz reference clock interface 1. The electrical interface in the device which is connected
T3#1. to the reference clock interface T3#1 and also the connect-
ing line between the two should be checked/serviced.
2. Fault rectified?
Yes: Fault clearance is ended. No: See point 3.
3. On the local NE check the setting of switches G2 and H2
on the terminal panel (T3/T4 clock adaptation 75 Ω unsym-
metrical or 120 Ω symmetrical).
4. Replace module CLL which is reporting the fault (for slot
see alarm window).

LOS T3#2 No input signal at 2048-kHz reference clock interface 1. The electrical interface in the device which is connected
T3#2. to the reference clock interface T3#2 and also the connect-
ing line between the two should be checked/serviced.
2. Fault rectified?
Yes: Fault clearance is ended. No: See point 3.
3. On the local NE check the setting of switches G2 and H2
on the terminal panel (T3/T4 clock adaptation 75 Ω unsym-
metrical or 120 Ω symmetrical).
4. Replace module CLL which is reporting the fault (for slot
see alarm window).

Tab. 7.23 SEC Alarms (CLL), Fault Clearance

144 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Alarm type Meaning Maintenance Measures

LOS T1#1 Reference clock signal T1#1 failed. Probable sources of fault:
See also note 1 below. 1. The tributary or line signal (STM-1, STM-4 or STM-16)
selected for T1#1 is showing an LOF (MS) or AIS (MS)
alarm and is thus not suitable as a reference.
2. An SSM = “don‘t use for sync” message will be delivered
(the selected signal is not suitable as a reference)
3. The overhead bus is faulty.
4. The interface module (OIS16/16-2/OIS4/4-
2/OIS1/EIPS1) is faulty.
5. Fault in module CLL.
Rectify the error, assign another reference clock signal
where necessary.

LOS T1#2 Reference clock signal T1#2 failed. Same as measures given for LOS T1#1 above.
See also note 1 below.

LOS T1#3 Reference clock signal T1#3 failed. Same as measures given for LOS T1#1 above.
See also note 1 below.
LOS T1#4 Reference clock signal T1#4 failed. Same as measures given for LOS T1#1 above.
See also note 1 below.

Tab. 7.23 SEC Alarms (CLL), Fault Clearance (Cont.)

Note 1: Network elements which are arranged in a line or ring structure and for which
i clock synchronization is provided from the SDH route (line or tributary side), send a tim-
ing marker byte of “don’t use for sync” in the opposite direction. By this the subsequent
NE (in the opposite direction) signals an alarm LOST1#..., although the SDH signal is
error-free. You can mask out this alarm message in the NE of the opposite direction as
follows:
In alarm window “CLL_SEC Alarm” (accessible via the “Module view”, in symbol SEC,
menu item <Fault> <Alarms>) set an alarm suppression for LOST1#....

Both G.703 channels of the OH interface provide the option of being configured for TIF
i (use for customer alarms) or G.703 (use as Aux channel). The alarms are also displayed
accordingly (Tab. 7.24, Tab. 7.25).

1.Vorabzug:A30808-X3580-H504-1-7620 145
MMN Maintenance
SLD/T16-2.5

Functional Symbol OH-IF, Symbol Channel 1 or 2 (G.703),

Alarm Window “OHA_..._G703 Alarm”,
Alarms and Fault Clearance

Alarm type Meaning Maintenance Measures

AIS (G703) (E0-) AIS received Perform fault location at the device which is connected to
An alarm indication signal (all ones) occurs at a G.703 port the G.703 port (auxiliary channel 1 or 2).
(64 kbit/s).

LOS (G703) Loss of signal 1. In the alarm window, read off the slot of the OHA module
The input signal at a 64 kbit/s auxiliary channel (G.703) which is reporting the fault and replace this module.
does not indicate any signal transitions. 2. Fault cleared?
Yes: Fault clearance is ended. No; see item 3.
3. Refit original OHA module, fault clearance at the local
NE is ended.
Check the appropriate connecting lines at the G.703 port
for interruption. The interface module of the device con-
nected to the G.703 port can be faulty.

G703 ... Interface in accordance with G.703 Recommendations

Tab. 7.24 G.703 Alarms of OH Interface, Fault Clearance

Functional Symbol OH-IF, Symbol Channel 1 or 2 (TIF),

Alarm Window “OHA_..._TIF Alarm”,
Alarms and Fault Clearance

Alarm type Meaning Maintenance Measures

LOS (TIF) Module TIF has failed, all TIF alarms are cleared. Replace module TIF.

TIF#1 Customer alarm messages, e.g. fire alarm, message for Not applicable
opened door...
TIF#2
Up to eight alarm messages for each of the two channels
TIF#3 (Channel 1, Channel 2) are possible.
TIF#4

TIF#5

TIF#6

TIF#7

TIF#8

Tab. 7.25 TIF Alarms (OHA), Fault Clearance

Functional Symbol Subrack,

Alarm Window “NE Alarm”,
Alarms and Fault Clearance

146 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Alarm type Meaning Maintenance Measures

Timing Failure of both T0 timing bus systems. 1. Is there protection switching for the CLL?
Yes: See Point 4. No: Replace the CLL.
2. Fault rectified?
Yes: Fault clearance is ended. No: See point 3.
3. Refit CLL, see Point 4.
4. Replace the SCU.
If the fault is still present: Special Fault Clearance.
2nd Power The redundant power feed leading from the line circuit Check lead and line circuit breaker.
breaker (in the upper part of the rack) to the subrack is
faulty.

P-Bus X&Y Failure of both P bus systems. Pull the individual modules in turn. Each module can be the
cause of the fault. To localize the fault pull one module and
ICB X&Y Failure of both IC-B bus systems.
check whether the alarm has disappeared. If not, plug the
module back in, pull the next module etc. Use this method
to check all modules in turn. When pulling and plugging the
modules in sequence make sure that you start with mod-
ules which have little importance for your particular appli-
cation and cause the least possible interruption to traffic.
For example, start with modules with protection switching
facilities, then TIF, OHA...

Int Hw Fail Collective display of faults in internal HW connections (e.g. Look in the “Detailed Alarm Info” window for information on
timing bus T0). the faults. Refer also to the next chapter entitled “Internal
hardware link failures”.

Tab. 7.26 Subrack Alarms, Fault Clearance

1.Vorabzug:A30808-X3580-H504-1-7620 147
MMN Maintenance
SLD/T16-2.5

Internal Hardware Link Failure

For functional symbol “Subrack” you also have a window entitled “Detailed Alarm Info”
available, which – in the event of an alarm message “Int Hw Fail” (in the alarm window
for the Subrack symbol) – displays details of current internal hardware link failures for
you (e.g. P bus).

Fig. 7.11 Detailed Alarm Information Window

To call the window: Select the Subrack symbol with the right-hand mouse button and
select menu item <Fault> <Detailed Alarm Information>.
The display window contains information about the link failure, the module reporting the
fault (Detecting Card) and about any other module which might be faulty and its slot
(Possible Failed).
Since the faults involved here are interface faults it is not always possible to assign them
uniquely to the individual module. The cause of the fault can be in both the module re-
porting the fault and in the other module listed as “Possible Failed”. Investigate these
modules in turn.
This list can show a number of fault message at the same time.

148 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

7.5 Faults Caused by External Add-On,

Devices and Something Else
Faults caused by external add-on, cables, devices, lines and power supply, which do not
conduct in a total failing, are some-times difficult to reach their reasons.
A good practice is to compare the equipment, the module, the transmission line and the
power supply with a known good one.
First reach in this cases is to decide between power supply related, control lines, com-
munication lines and synchronization lines related failure reasons.
Basic is to check the power supply outputs to the equipment to be within their limits and
next with an oscilloscope for noise outside specifications. If this check is passed go
ahead for other fault reason localization.
Check now the synchronization lines if levels and waveform are within the specifica-
tions.
Check then the control lines, check match boxes if used and every interface and con-
nector point. Check for broken wire. If this check is passed go ahead with communica-
tion lines.
On communication lines check them first by using the local loop features inside and out-
side the equipment. Now check the related cables, connector points, interfaces, match
boxes (like a CLA adapter), and the attenuator used in the lines. If checking with an ex-
ternal loop cabling do not forget to use the attenuator to avoid destruction of receivers.

7.6 Software Errors

7.6.1 Software Errors in a Module with PCU

If the PCU of a module signals a SW error a reset is initiated in the module. If the error
is still present after the reset, the module is taken out of service, it is put into the disabled
state.
If a checksum error of the boot SW is detected when a module is starting up, the PCU
goes into error status, data exchange with the SCU is interrupted and the red fault LED
on the module starts to light. Replace this module as described in Chapter 8.2.1.

7.6.2 Software Errors in Module SCU

An SCU error mainly occurs when
• a checksum error for boot SW/EPROM / NVRAM or an error in the file check system
occurs during module start-up
• data is stored incorrectly.
SCU SW errors cause
• an interruption of the link to LCT/NCT/OS
• an interruption of data exchange with external interfaces
• an failure on the Ethernet or LAN communication
• all information supplied by the ICB bus to be ignored
• the red fault LED and the green service LED to light.

1.Vorabzug:A30808-X3580-H504-1-7620 149
MMN Maintenance
SLD/T16-2.5

An SW error in the SCU initiates a reset in this module. If this is not successful the mod-
ule is shut down. You can then initiate another hardware reset of the SCU manually by
pressing the SHUT button on the SCU.
If the error is still present, replace the SCU as described in Chapter 8.2.2.

Fig. 7.12 SCU Alarm Information Window

7.7 Measures after Fault Clearance has been Performed

When fault clearance is ended and the fault is rectified, make the following settings at
the LCT:
• Select the main menu items: <NE State> <Set to Operation>, to allow (newly) arriv-
ing alarm messages to be displayed at the LCT and then <NE State> <Set to Previ-
ous Configuration>.
• Select the main menu items: <NE State> <Set to Active>, to take the NE out of the
idle state and put it into the active state
• Select the main menu items: <Security> and select the field “Release Write Access”,
to release with the <Apply> button the NE to other users again for write access.

7.8 Special Fault Clearance

For fault states which cannot be rectified using the measures described in this Mainte-
nance Manual contact the relevant service representative at Siemens.
In such cases it is helpful for fault pinpointing to fill out a “SW Installation Checklist”. You
can obtain current copies of this list from your appropriate service representative.
Log Records (see Chapter 3.9) can be helpful for fault diagnosis.

150 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

8 Module Replacement

8.1 Foreword
When replacing modules, it is imperative to adhere to the requirements in
! Chapter "2 Protective Measures, Handling / Schutzmaßnahmen, Handhabung"!

At the LCT the access mode field in the main menu bar must be showing the word “write”
(for write access). If it is not, select main menu item <Security> <Request Write Ac-
cess>.
Set the NE to “Maintenance” mode to avoid fault messages being generated when pull-
ing-out and plugging-in modules. Do this at the LCT by selecting the main menu items:
<NE State> <Set to Maintenance>. In the field for the alarm signaling state in the main
menu bar the word “maintenance” appears (in red).

8.2 Replacing the Module

Modules may be removed from the subrack and plugged into it again under voltage.
The replacement modules must be pushed into the subrack as far as they will go and
locked.
The equipping of the subrack must always have an SNL module which is in the card
! State “Enabled” (at the LCT: “Module View”, select SNL module symbol with the right-
hand mouse button, the menu items: <Information> <Card, Card State: Enabled>).

The following table shows the influence of module replacement on the operating behav-
ior of the NE.

Replaced Module Consequences Remarks

OIS16/16-2 or Corresponding traffic interrupted Remedy: (1+1) or (1:1) line pro-

OB or tection switching combined with
OP card release switching for
OIS16/16-2, 2fiber or 4fiber ring
protection switching.
OIS16-2 concatenation and FEC

OIS4/4-2 Corresponding traffic interrupted on Remedy: (1+1) line protection

tributary side switching combined with card re-
lease switching for OIS4/4-2
OIS4-2 concatenation

OIS1 Corresponding traffic interrupted on Remedy: (1+1) line protection

tributary side switching combined with card re-
lease switching for OIS1

EIPS1 and/or appropriate LTU Corresponding traffic interrupted on (1:n) module protection switching
tributary side for EIPS1

SNL All the traffic of NE interrupted, SCU Remedy: SNL module protection
continues to control the remaining switching (but effects a short traf-
modules of NE fic interruption)

Tab. 8.1 NE Behavior During Module Replacement

1.Vorabzug:A30808-X3580-H504-1-7620 151
MMN Maintenance
SLD/T16-2.5

Replaced Module Consequences Remarks

CLA Access of 2MBit/s synchronization for 2 Mbit/s synchronization works

(external module located in the up to three subracks is not possible. only if CLL64-2 module in each
rack terminal panel) subrack is provided and T3/T4
connected by cable from the CLA
channels.

CLL or CLL64-2
(Measures for replacing the
CLL or CLL64-2 see chapter
8.2.1)
All the traffic of NE interrupted. Remedy: CLL or CLL64-2 module
Only with a CLL64-2 the 2MBit/s syn- protection switching
chronization coming and going to the
external CLA module box is interrupt-
ed.

SCU, Control of NE no longer possible, traf- Functionalities which need SCU

SCU-R2, fic not interrupted. are no longer possible, e.g. MCF
SCU-R2E TMN and LAN-Connection disrupted. and a few protection mechanisms.
Module protection switching for
SNL and CLL can still be per-
formed.
SCU-R2 has special release 2.
SCU-R2E has special release 2.
and RAM extension.
Replace Module with same re-
lease and extension. SCU-R2E is
a replacement of all SCU types.

OHA Access to a number of OH bytes is If a handset or a TIF module is

not possible. used, these are out of operation.

Tab. 8.1 NE Behavior During Module Replacement (Cont.)

8.2.1 Replacing a Module (with PCU)

This applies to all modules except SCU.
The green service LED on the front of the module lights and thereby indicates that the
module is no longer involved in traffic and that you may now pull the module. This ser-
vice LED cannot be affected by the LCT/OS.

Replacement
Open the front cover of the NE and replace the module. Make sure that the type and
version of the new module are correct.
For possible setting measures on the “new” module, see Chapter 8.3.
When the faulty module has been pulled out, the message that the module is no longer
i available appears at the LCT (and on the network management system): Card State =
“Disabled” (at the LCT: “Module View”, select the module button with the right-hand
mouse button, the menu items: <Information> <Card, Card State...>).

In rare cases it can occur that the green service LED does not light when a module alarm
i occurs. In this event, before replacing the module, set the required equipping for this
module to empty via the Module View (at the operating terminal). This is only possible
if this module is not involved in any cross connection, i.e. if it is not carrying any traffic.
Remove any cross connection for this module beforehand. After replacing the module,
reenter the setting for the original required equipping.

152 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

When replacing an OIS16-2 or OIS4-2 card in a system not running with

! SLD16/SLD16E R2.5 Software, ensure that the selection switch “FEC” / “concatenation
conversion” on the new card is set identically to that on the replaced card.
After plugging in the new card, modify the card label as described in the Operating Man-
ual OMN:SL.

Special Requirements when Replacing Module CLL

There are two different cases which can be identified here:
1. The subrack equipping includes only one CLL:
If a CCL fault occurs, traffic will have already been interrupted. You can thus replace
the CLL without taking any particular precautions.
2. The subrack equipping includes two CLLs:
Traffic will not be interrupted when the defective CLL is replaced.

Attention!
! The procedure described below should always be followed if two CLL modules are
included in the subrack:

In order not to disturb the synchronization process which starts automatically after
a CLL has been replaced, you may not do any of the following things for at least 45
minutes after the module is replaced:
– switch the operating voltage off and then back on again
– pull the SCU and plug it back in
– press the reset button on the SCU
– perform a VCDB download or an SW download
– initiate a state transition from idle to active
– make a system time setting in the application software
– pull the working CLL (which also remains fault-free after an alarm event).

It is also vital to adhere to this procedure when the required equipping of the CLL
was changed at the operating terminal!

Attention in Case of Using a CLL64-2 Card!

! Replace only with a CLL64-2!

Putting into Operation again

After the new module has been plugged into the corresponding slot of the subrack, a
spontaneous PCU message is sent to the system control unit SCU. The SCU checks
whether this type is permitted or not for the slot.
Should the required and actual value not correspond (card type or HW version is un-
known), the module will not be put into operation. If the module is permitted or not for
the current slot, it will go through an automatic start phase. A module test is run. The
SCU automatically loads the software configuration data and (if necessary) the applica-
tion SW.
The application SW download takes about 5 minutes, so please do not pull out the card
i again during this period.

This ends module replacement.

1.Vorabzug:A30808-X3580-H504-1-7620 153
MMN Maintenance
SLD/T16-2.5

8.2.2 Replacing Module SCU

Precondition: Before an SCU is plugged into the subrack (again) you must make sure
! that the CLL module is already plugged into the subrack to ensure that the SCU module
starts up correctly.

Usually the NE will be in the operational status “active” when the module SCU fails. An
appropriate message appears in the main status line. Then bring the NE into the idle
status by selecting the main menu items: <NE State> <Set to Idle>. Exchange the faulty
module SCU as described under 4. in the following.
In the special case that the SCU failed during operating status “idle” the possible ar-
rangements are as follows:
1. After the NE state changed from active (operating) to idle no further configuration
settings were made so that the FEPROMs of the backplane are storing the current
NE configuration:
→ Replace the SCU as described under 4.

2. After the NE state changed from active to idle, configuration changes were made but
these changes are to be canceled again (The current configuration data stored in
the FEPROMs of the backplane differs from the SCU data which is valid at present):
→ Replace the SCU as described under 4.

3. When the data stored in the backplane FEPROMs differs from the current SCU data
you can choose one of the following options:
– You accept that configuration changes which were made after the change to the
NE idle state will be lost:
→ Replace the SCU as described under 4.
– You attempt to retain the configuration changes made in the idle state even
though the module is replaced:
Do this by executing an upload of the VCDB (Virtual Configuration Data Block) of
the NE by selecting the symbol “Config DB” of the “Module view” with the right-
hand mouse button, choosing menu item <Upload>, defining a path and saving.
→ Replace the SCU as described under 4.
In the NE state idle then perform a VCDB Download (of the file stored during the
preceding VCDB Upload) by first selecting menu item <NE State> <Set to Default
Configuration> and then performing a right-hand mouse click to the “Config DB”
symbol of the Module view and by selecting menu item <Download>. Afterwards
select the “Stay Idle” button.
Mark symbol “Data” with a right-hand mouse click, select menu item <NE Data>
and fill in “NE Name” and “NE Location”. Mark symbol “MCF” by a right-hand
mouse click, select menu item <Subview”, mark symbol “Ethernet” with a right-
hand mouse click, select menu item <Configuration>, enter the actual “MAC
Ethernet Address” and confirm with Apply.
In this window also check the entries for Reachable Addresses and correct them
if necessary.
Select menu item <NE State> <Set to Active>.

For details on VCDB Upload / VCDB Download see operating manual OMN, Reg-
ister 1 OMN:SL chapter 6 and Online help / index (under “VCDB Upload”, “VCDB
Download”).
Note: If protection switching is configured you should perform a VCDB Download

154 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

only if traffic is routed via the working modules. Otherwise traffic could be inter-
rupted.

– You attempt to retain the configuration changes made in the idle state even
though the module is replaced by changing the NE state from idle to active and
back again to idle.
To do this select the main menu commands: <NE State> <Set to Active> (initiate
a restart of the NE by double-clicking the NE symbol in NE-UniGATE) and select
<Set to Idle> again.
Note: This process will only be successful if no further inconsistencies are discov-
ered during startup in the active state.
→ Then replace the SCU as described under 4.

Both last stated items suppose that the corresponding functional parts of the faulty
SCU still work.

4. To replace module SCU press the shutdown button on the SCU. This takes the NE
into the “down” state in an orderly manner (UNIX operating system).
The shutdown procedure can take a few minutes depending on system equipping. It
can be identified by the green flashing service LED on module SCU.
As soon as the green service LED lights permanently, pull the SCU out of the sub-
rack and replace it with a fault-free module.
After replacing the SCU also check the time set and correct this if necessary.

Important:
! 1. The new SCU must contain the APS (Application Program System) which belongs to
the specific module type (see APS label). Otherwise the operating terminal indicates a
fault.
Select <View> <Module view>, mark symbol Software with the right-hand mouse button
and select menu item <Management>.
2. Beyond this the HW/SW compatibility IDs of the new and the replaced module must
be identical or the APS which is active at the moment must support both the old and the
new compatibility number.
If none of these requirements is met the SCU reports HW/SW incompatibility and can
thus not start operating correctly.
Select <View> <Module view>, mark symbol Software with the right-hand mouse button
and select menu item <Compatibility>.

After the new SCU is plugged in it begins its startup sequence, accepts the last valid NE
configuration data (VCDB) from the backplane FEPROMs and ends by going into the
idle state.

1.Vorabzug:A30808-X3580-H504-1-7620 155
MMN Maintenance
SLD/T16-2.5

Then – if you wish – you can make further configuration changes via the LCT to adapt
the configuration. When main menu commands: <NE State> <Set to Active> is entered
the NE – if there are no further errors present – achieves its operational state.
In very rare cases the SCU module could perform a reboot if
i – a VCDB Download is performed
– the shutdown button of the SCU module is actuated
– the NE is forced to change to the active state
– a swap of the software is initialized.
This reboot only happens when the synchronization process was started directly before
or after a 15 minutes pulse.

8.2.3 Replacing Modules LTU, PSUTP, EBSL and TIF

and the Handset
If a LTU module (interface module for one EIPS1 module), modules PSUTP or EBSL
(required auxiliary modules for EIPS1 card release switching) or the handset for engi-
neering order wire call have to be replaced, there are no special actions to be taken into
consideration excepted the requirements in Chapter 2.
This also applies to replacing a module TIF, here however setting actions in accordance
with Chapter 8.3.1 have to be performed.

8.3 Making Settings on the Modules

When replacing the modules hardware settings need only be taken into account on
modules TIF, OP, OB.
The SW defaults of the replaced module are stored on the SCU. When the new module
is started up for the first time, these defaults are automatically transferred from the SCU
to the new module.

8.3.1 Hardware Settings on Clock Line Adapter Unit, CLA Box

The A2, A4 and A6 switches (Fig. 4.7) on the CLA module’s front panel which is mount-
ed in the rack terminal panel define the relevant Sa-Bit according to the net planning
specifications. Bit related positions are according to Tab. 8.2.

Fig. 8.1 CLA Box Sa-Bit Selector Switch n=1 (A2), =2 (A4), =3 (A6)

156 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

Switch A2, A4 and A6, 1) Sa-Bit Bit Level in Signal / BCD-Weight

Position

1 SASEL 0 High (1) / 1

2 SASEL 1 High (1) / 2

3 SASEL 2 High (1) / 4

4 not used High (1) / 8

1) Default value is OFF (0) position

Tab. 8.2 Channel 1 ... 3 Sa-Bit Configuration Switch (A2, A4, A6) Assignment

8.3.2 Hardware Settings on Module Telemetry Interface Unit, TIF

Switches CH1...8 and CH9...16 on the front panel of the TIF module define whether the
two codirectional 64-kbit/s channels of module OHA are used for customer-specific
alarms (CUST-AL = Customer Alarms and CUST-CT = Customer Control) (connected
to the TIF module) or lead to the interfaces of auxiliary channels AUX1, 3, 5 or AUX2,
4, 6. Switch settings are according to Tab. 8.3.

Switches Switches Custom Alarms Custom Alarms AUX 1, 3, 5 AUX 2, 4, 6

CH1...8 1) CH9...16 1) No. 01-08 No. 09-16

OFF OFF X X

ON OFF X X

OFF ON X X

ON ON X X

1) Default is OFF
X... Function is active

Tab. 8.3 64-kbit/s Channel Assignment

8.3.3 Hardware Settings for the Optical Preamplifier Module, OP

On the optical preamplifier module, a jumper plug is used to determine whether the OP
is being used in conjunction with an OIS16/16-2 module, or with an OIS4/4-2 module.

Jumper Setting Use of the OP

at Position X205

13 – 14 open In conjunction with module OIS4/4-2 1)

13 – 14 jumped In conjunction with module OIS16/16-2

1) In this version module OP is not used in conjunction with module OIS4/4-2.

Tab. 8.4 Jumper Setting on the Optical Preamplifier Module

Check in addition whether all eight jumpers are plugged in on jumper plug X106, thus
giving a connection to the ICS bus.

1.Vorabzug:A30808-X3580-H504-1-7620 157
MMN Maintenance
SLD/T16-2.5

Insertion and extraction aid

Laser unit

Fiber optic plug

connector
SIPAC-S connector strip

X205
13 1

14 2
X106
2 1

Mechanical
coding Insertion and extraction aid

Fig. 8.2 Optical Preamplifier Module: Position of the Jumper Plugs

8.3.4 Hardware Settings on Module Optical Booster, OB

Insertion and extraction aid

Laser unit
SIPAC-S connector strip

Fiber optic plug

connector

X106
2 1

Mechanical
coding Insertion and extraction aid

Fig. 8.3 Optical Booster Module: Position of the Jumper Plugs for the ICS Bus

158 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

When replacing the optical booster module, check whether all eight jumpers are plugged
into jumper strip X106 and thus that the required connection to the ICS bus exists
(see Fig. 8.3).

8.4 Measures after the Module has been Replaced

After the module has been replaced and the module startup sequence has completed,
test the status of the repaired module at the LCT:
In “Module View” select the module symbol with the right-hand mouse button and
choose menu item <Information> <Card>. “Card State“ must appear as “Enabled”.
If an OIS16/16-2, OIS4/4-2, OIS1 or OB module was replaced, determine the optical
transmit power of the replacement and log it:
Do this by marking functional symbol STM16/STM4/STM1(opt.)/OPT-BOOST in the
Traffic View, select an associated port symbol with the right-hand mouse button, chose
menu item <Subview>, mark symbol STM16/STM4/STM1/OPT-BOOST in the Traffic
Flow window with the right-hand mouse button, chose menu item <Information>
<STM16/STM4/STM1/OPT-BOOST…>. Under Laser data you will find the value for out-
put power level. Alternatively you can also check transmit power with the optical power
meter.
When the SCU module has been exchanged, reset the clock (see Register 1, OMN:SL
of the Operating Manual).

Check the Inventory Data for the New Module:

In the “Module View”, use the right-hand mouse button to select the module symbol, and
then select the menu items <Information> <Data> <Card Label>. The “Card Label Info”
window is used to provide details. Changes may only be made by the manufacturer’s
personnel (who have the “Admin” rights and password).
In order to enter user-specific data, use the right-hand mouse button to select the
module symbol and select the menu items <Configuration> <User Label>.
Finally carry out the actions listed in Chapter 7.7.

1.Vorabzug:A30808-X3580-H504-1-7620 159
MMN Maintenance
SLD/T16-2.5

160 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

9 Abbreviations
This chapter contains all the abbreviations of the operating documentation for
SLD/T16-2.5 and SLR16-2.2.

2F-SPRING 2-Fiber Shared Protection Ring

4F-SPRING 4-Fiber Shared Protection Ring
2WHS 2-Wire Handset Diensttelefon für
Zweidrahtschnittstelle
... R1 Release 1
... R2 Release 2
... R3 Release 3
... R4 Release 4
ABR Alarm on Request Alarm auf Abruf
ADC Analog Digital Converter Analog-/Digital-Umsetzer
AIS Alarm Indication Signal (G.783) Alarmmeldesignal (G.783)
ALS Automatic Laser Shutdown (G.783)
ANT Alarm Response Antwort-Alarminformation
APD Avalanche Photo Diode
APS Automatic Protection Switching Automatische Ersatzschaltung
AS Alarm Suppression Alarmunterdrückung
ASCII American Standard Code for
Information Interchange
ASIC Application Specific Integrated Anwendungsspezifischer IC
Circuit
ASW Application Software Anwendungssoftware
AU Administrative Unit Verwaltungseinheit
AU4 Administrative Unit for VC-4
AU4CTP AU-4 Connection Termination Point
AUAIS Administrative Unit Alarm Indication
Signal
AUI Attachment Unit Interface
AULOP Administrative Unit Loss of Pointer
(G.783)
AUX Auxiliary Channels
BASW Basic Software Basis-Software
BBE Background Block Error
BDM Background Debug Mode Interface
BER Bit Error Ratio Bitfehlerhäufigkeit
BG Module/Card Baugruppe
BGT Subrack Baugruppenträger
BSHR Bidirectional Self-Healing Ring
Bw7R Narrow-Rack Style 7R Schmalgestellbauweise Typ 7R
C-AL Customer Alarm Kundenalarm
CC Cross-Connection
CE Communautè Europèenne

1.Vorabzug:A30808-X3580-H504-1-7620 161
MMN Maintenance
SLD/T16-2.5

CEPT Confèrence Europèene des Konferenz europäischer Post-

Administrations des Postes et des und Telekommunikationsver-
Tèlècommunications waltungen
CF Card Failure Baugruppenfehler
CFG Configuration Konfiguration
CL Configuration Log
CLA Clock Line Adapter Module Box Taktleitungsadapter
(external; (extern;
from 2MBit/s to 2.048MHz) von 2Mbit/s auf 2,048 MHz)
CLL Clock Unit Line Module Taktleitungseinheit Baugruppe
CLL64-2 Clock Unit Line Module Typ 64-2 for Taktleitungseinheit Baugruppe
Clock-Sychronization using CLA Typ 64-2 für Takt-Sychronisation
mittels CLA
CLNS Connectionless Network Layer
Service
CONF Configuration Alarm Konfigurationsalarm
CPL Current Problem List Aktuelle Fehlerliste
CPU Central Processing Unit Zentraler Steuerungsrechner
CRC Cyclic Redundancy Check
CRS Card Release State
CS4 Connecting Switch 4xSTM-1
(Module)
CSO Card out of service Baugruppe außer Betrieb
CT Card Type Baugruppentyp
CTP Connection Termination Point
CUST-AL Customer Alarms
CUST-CT Customer Control
D4CTP Functional Unit “VC-4 Connection
Termination Point”
DB Data Base
DC Direct Current Gleichstrom
DCC Data Communication Channel Datenkommunikationskanal
DCCB Data Communication Channel Bus
DCCM Data Communication Channel for
Multiplex Section
DCCR Data Communication Channel for
Regeneration Section
DCN Data Communication Network
DEMUX Demultiplexer
DIN German Standards Institute Deutsches Institut für Normung
DNU Do Not Use
DRAM Dynamic Random Access Memory
DSP Domain Specific Part
DTMF Dual-Tone Multifrequency Mehrfrequenzwahlverfahren
E&M Exchange and Multiplex
E4 Eletrical Interface Signal 139264-kbit/s-Signal, das in
139264 kbit/s einen C3-Container eingefügt
wird
EBC Error Block Count

162 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

EBSL EIPS1 Backup Switch Line (Module)

ECC Embedded Communication Channel
ECCM ECC for Multiplex Section
ECCR ECC for Regeneration Section
EDFA Erbium Doped Fiber Amplifier Erbium-dotierter Faserverstärker
EDI Electronic Data Interchange Kommunikation zum Rückwand-
Flash-PROM
EEPROM Electrically Erasable Programmable Elektrisch löschbarer
Read-Only Memory programmierbarer
Festwertspeicher
EGB Electrostatic Discharge Elektrostatisch gefährdete
Bauteile
EIPS1 Electrical Interface
Plesiochronous/Synchronous
140 Mbit/s / STM-1 (Module)
EL Reminder of Alarm Erinnerungslampe
EM-OS Equipment Management Operations
System
EMC, EMV Electromagnetic Compatibility Elektromagnetische
Verträglichkeit
EOW Engineering Order Wire Dienstgesprächskanal
EPROM Erasable Programmable Read-Only
Memory
ES Electrical Section or
Errored Second(s)
ESD Electrostatic Discharge Elektrostatische Entladung
ESRT Equipment and Software Release Tabelle der HW- und
Table SW-Ausgabestände
ETS European Telecommunications
Standard
ETSI European Telecommunications Europäisches Institut für
Standards Institute Telekommunikationsstandards
EXC Excessive Bit Error Ratio
F Standardized Interface for Standardisierte Schnittstelle zum
Connection of the Operating Anschluß eines Bedienrechners
Terminal
FC/PC Connector Type Steckertyp
FCA FEC and Concatenation Active FEC und Verkettung aktiv ge-
schaltet
FE Functional Unit Funktionseinheit
FEBE Far-End Block Error
FEC Forward Error Correction Vorwärts Fehlerkorrektur
FEPROM Flash Eraseable Programmable
Read-Only Memory
FERF Far-End Receive Failure
FET Field Effect Transistor Feldeffekt-Transistor
FG Functional Group Funktionsgruppe
FIFO First-In First-Out
FO Fiber Optic Lichtwellenleiter

1.Vorabzug:A30808-X3580-H504-1-7620 163
MMN Maintenance
SLD/T16-2.5

FOD Fiber Optic Distributor

FOP Failure of (MSP) Protocol
FTA File Transfer Area
FTP File Transfer Protocol
FU Functional Unit Funktionseinheit
GMT Greenwich (Mean) Time Westeuropäische Zeit
GND Ground Masse
GUI Graphical User Interface Grafische Benutzeroberfläche
HCS Functional Unit “Higher Order
Connection Supervision”
HDI Hard Disk Interface Schnittstelle für Festplatte
HEL Historical Event Log Ereignisliste
HEX Hexadecimal Hexadezimal
HO Higher Order
HO-FERF Higher Order Far-End Receive
Failure
HOI140M Higher Order Interface 140 Mbit/s
HPC Functional Unit “Higher Order Path Funktionseinheit “Higher Order
Cross-Connect” Path Cross-Connect”
HPOM Functional Unit “Higher Order Path Funktionseinheit “Higher Order
Overhead Monitoring” Path Overhead Monitoring”
HPT Functional Unit “Higher Order Path Funktionseinheit “Higher Order
Termination” Path Termination”
HPT-4 Functional Unit “Higher Order Path Funktionseinheit “Higher Order
Termination (VC-4)” Path Termination (VC-4)”
HPX Functional Group “Higher Order Funktionsgruppe “Higher Order
Path Cross-Connection” Path Cross-Connection”
HPXVC4 Functional Unit “Higher Order Path Funktionseinheit “Higher Order
Cross-Connection VC-4” Path Cross-Connection VC-4”
HRL High Return Loss (Connector Type) Steckertyp
HSUG Functional Unit “Higher Order
Supervisory Unequipped Generator”
HSUM Functional Unit “Higher Order Funktionseinheit “Überwachung
Supervisory Unequipped Monitor” auf nicht belegten VC-4-Pfad”
HW Hardware
ICB Internal Control Bus Interner Steuerungsbus
ICS Internal Communication System Internes Kommunikationssystem
ICU Internal Control Unit Interne Steuereinheit
ID Identification (Service Status) Betriebsanzeige
IDI Initial Domain Identifier
IDP Initial Domain Part
IEC International Electrotechnical Internationaler Elektrotechnischer
Commission Ausschuß
IEEE Institute of Electrical and Electronic Internationaler Verband der
Engineers Inc. Elektro- und Elektronik-
Ingenieure
IMN Installation Manual Montagehandbuch
IMTS Internal Multiplex Timing Source Interne Zeitreferenz zur
Multiplexverarbeitung

164 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

INT Internal Supervision (Summary Fault Interne Überwachungsanzeige

Indication)
IS Intermediate System
ISDH Internal SDH Signal
ISF ISDH Signal Fail Fehlerhaftes ISDH-Signal
ISO International Standards Internationale Organisation für
Organization Normung
ISU ISDH-Switch Unit Layer
ITMN Installation and Test Manual Inbetriebnahmehandbuch
ITU International Telecommunication Internationale Fernmeldeunion
Union
ITU-T Telecommunication Standardization
Sector of ITU
K1, K2 Automatic Protection Switching
Channel defined in the SOH of a
STM-1
LAN Local Area Network
LAPD Link Access Procedure on
D Channel
LCT Local Craft Terminal Bedienrechner
LE Reminder Function for ZBBeo Erinnerungsfunktion für ZBBeo
LED Light Emitting Diode Lumineszenzdiode
LOA Loss of Alignment (G.783) Angleich-/Einstellverlust
LOF Loss of Frame (G.783) Rahmenverlust
LOL Loss of Lock Verriegelungsverlust
LOM Loss of Multiframe (G.783) Multirahmenverlust
LOP Loss of Pointer or Lower Order Path Zeigerverlust im untergeordneten
Pfad
LOS Loss of Signal (G.783) Signalverlust
LPA Functional Unit “Lower Order Path Funktionseinheit “Lower Order
Adaptation” Path Adaptation”
LPA-4 Functional Unit “Lower Order Path Funktionseinheit “Lower Order
Adaptation (VC-4)” Path Adaptation (VC-4)”
LPC Lower Order Path Connection
LSS Circuit Breaker Leitungsschutzschalter
LTU Line Termination Unit (Module)
LWL Optical Fiber Lichtwellenleiter
LZE Light Signal Equipment Lichtzeicheneinrichtung
MAC Media Access Control
MAU Medium Attachment Unit
MCF Message Communications Function
(Module)
MIB Management Information Base
MIS-PT Mismatch Path Trace Fehlerhafte Pfaddurchschaltung
MIS-RT Mismatch Regenerator Termination
MMI Man-Machine Interface Mensch-Maschine-Schnittstelle
MMN Maintenance Manual Wartungshandbuch
MS Multiplex Section (G.783)

1.Vorabzug:A30808-X3580-H504-1-7620 165
MMN Maintenance
SLD/T16-2.5

MSA Functional Unit “Multiplex Section Funktionseinheit “Anpassung des

Adaptation” Multiplexabschnittes”
MSAIS Multiplex Section Alarm Indication
Signal
MSFERF Multiplex Section Far-End Receive
Failure (G.782, G.783)
MSOH Multiplex Section Overhead
MSP Multiplex Section Protection
MSPCO Multiplexer Section Path Connection
MSPTF Multiplexer Section Protection Func-
tion
MSPTF-16 Multiplex Section Protection
Termination Function STM-16
MST Functional Unit “Multiplex Section Funktionseinheit “Multiplex
Termination” Section Termination”
MSTTP Functional Unit “Multiplex Section Funktionseinheit “Multiplex
Trail Termination Point” Section Trail Termination Point”
MTBF Mean Time Between Failures
MTG Multiplexer Timing Generator
MTS Multiplexer Timing Source Multiplexer Zeitbasis
NC/P Network Connection Protection
NCT Network Craft Terminal Erweiterter Bedienrechner
NE Network Element Netzelement
NE-UniGATE Basis-Management-Software for
Network Element
NRZ Non Return to Zero
NRZI Non Return to Zero Invert
NSAP Network Service Access Point Netzadresse
NUBAT Battery Voltage (negative)
NVRAM Non Volatile Random Access RAM für nichtflüchtige Daten
Memory
OAS Optical Amplifier Section Optischer Verstärker-Bereich
OB Optical Booster (Module)
OHA Overhead Access Module
OHCC Overhead Cross-Connection
OHF Overhead-Function
OH-IF Overhead Interface
OHX Overhead Cross-Connect Verschaltung der
Overhead-Kanäle
OIS1 Optical Interface Synchronous
STM-1 (Module)
OIS16 Optical Interface Synchronous
STM-16 (Module)
OIS16-2 Optical Interface Synchronous
STM-16 (Module) - 2nd Level HW
OIS16R Optical Interface Synchronous
STM-16 for Regenerator (Module)
OIS4 Optical Interface Synchronous
STM-4 (Module)

166 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

OIS4-2 Optical Interface Synchronous

STM-4 (Module) - 2nd Level HW
O&M Operation and Maintenance
OMN Operating Manual Bedienungshandbuch
O.N.E Optimized Network Evolution
(VISION O.N.E)
OP Optical Preamplifier (Module)
OS Operations System Betriebsführungssystem
OSC Oscillator Oszillator
OSNR Optical Signal/Noise Ratio Optisches Signal-/
Rauschverhältnis
P4 Plesiochronous Digital Signal
139264 kbit/s
PABX Private Automatic Branch Exchange
PBUS Protection Bus Ersatzschaltungsbus
PBX Private Branch Exchange Private Nebenstellenanlage
PCS Plesiochronous Connection
Supervision
PCU Peripheral Control Unit Baugruppenrechner
PCUC Peripheral Control Unit in SLR PCU im SLR
PDH Plesiochronous Digital Hierarchy Plesiochrone Digitale Hierarchie
(G.783)
PDH-LT Line Termination 140 Mbit/s
PDH-MUX PDH-Multiplexer
PDU Protocol Data Unit (G.784)
PE Protection Earthing Schutzerdung
PET Possible Equipping Table Tabelle zur möglichen
Bestückung
PJE Pointer Justification Event
PLL Phase Locked Loop Phasenregelschleife
PLM Payload Mismatch
PM Performance Management or
Performance Monitoring
POH Path Overhead (G.782) (G.783)
POM Path Overhead Monitoring
PPI Functional Unit “Plesiochronous Port Funktionseinheit “Plesiochronous
Interface” Port Interface”
PRC Primary Reference Clock
PROM Programmable Read-only Memory
PSU Power Supply Unit Stromversorgung
PSUTP Power Supply Unit Tributary
Protection Access (Module)
PUBAT Battery Voltage (positive)
Q Interface to a Telecommunication Schnittstelle zum TMN
Management Network
Q-B3 Q-Interface to Operations System Q-Schnittstelle für Bedienrechner
via Ethernet-LAN oder Netzmanagementsystem
über Ethernet-LAN

1.Vorabzug:A30808-X3580-H504-1-7620 167
MMN Maintenance
SLD/T16-2.5

QD2 RS485 TMN Interface for Deutsche RS485-TMN-Schnittstelle für

Telekom, Category 2 Deutsche Telekom, Kategorie 2
QD2B3 Q-Interface for Operating Q-Schnittstelle für Bedienrechner
Terminal or Network oder Netzmanagementsystem
Management System über Ethernet-LAN
QD2F Standardized Interface for Standardisierte Schnittstelle zum
Connection of the Operating Anschluß eines Bedienrechners
Terminal
QECC Q-Interface via DCC
Q-F Standardized Interface for Standardisierte Schnittstelle zum
Connection of the Operating Anschluß eines Bedienrechners
Terminal
QST-B3 QD2-Interface to LCT
Qx Interface to a Telecommunication
Management Network
RAM Random-Access Memory Schreib-/Lese-Speicher mit
direktem Zugriff
RDI Remote Defect Indicator
REI Remote Error Indicator
RISC Reduced Instruction Set Computer
ROM Read-Only Memory Lesespeicher
RS Regenerator Section
RS-TIM Regenerator Section - Timing Infor- Regeneratorabschnitt - Zeitifor-
mation Multiframe mation Mehrfachrahmen
RSOH Regenerator Section Overhead Regeneratorabschnitt - Overhead
Rows 1-3 from Section Overhead in Reihen 1-3 des Abschnitts-Over-
STM-1 (G.782) (G.783) head in STM-1 (G.782), (G.783)
RST Functional Unit “Regenerator Funktionseinheit “Regenerator
Section Termination” Section Termination”
RT Acknowledge Key Rückstelltaste
RTC Real Time Clock Echtzeituhr
RTF-16 Functional Group “Regenerator Funktionsgruppe für den
Transport Function” STM-16 optischen STM-16-Port
RTG Functional Unit “Regenerator Timing Funktionseinheit “Regenerator
Generator” Timing Generator”
RTI Regenerator Trace Identifier
RxDeg Receive Degraded Signal Abgeschwächtes Empfänger-
signal
SC Connector Type Steckertyp
SCU Synchronous Control Unit (Module)
SCU-R2 Synchronous Control Unit Release 2
(Module)
SCU-R2E Synchronous Control Unit Release 2
(Module) Extended RAM equipping
SD Signal Degrade (G.782) Abgeschwächtes Signal
SDH Synchronous Digital Hierarchy Synchrone Digitale Hierarchie
SDI Service and Diagnostic Interface Service und Diagnose Schnitt-
stelle
SEC SDH Equipment Clock SDH Gerätetakt

168 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

SEMF Synchronous Equipment Synchrongeräte Management

Management Function Funktionen.
SES Severely Errored Second(s)
SET2 Synchronous Equipment Timing Takterzeugung
SETG Synchronous Equipment Timing Taktgenerator
Generator
SETS Functional Group ”Synchronous Funktionsgruppe
Equipment Timing Source” “Takterzeugung”
SF Signal Fail Signalausfall
SHR Self-Healing Ring Selbstheilender Ring
SigVt Signal Distributor Signalverteiler
SISA Supervisory and Information System
for Local and Remote Areas
SISA-0 Functional Group for Software Funktionsgruppe “Software
Management, Date/Time Management, Datum/Uhrzeit”
SL Synchronous Line Equipment Synchrones LWL-System
SL series 1 First Generation of SDH Fiber-Optic SDH-Lichtwellenleitersystem der
System 1. Generation
SL series 2 Second Generation of SDH SDH-Lichtwellenleitersystem der
Fiber-Optic System 2. Generation
SL-1 First Generation of SDH Fiber-Optic SDH-Lichtwellenleitersystem der
System 1. Generation
SL-2 Second Generation of SDH SDH-Lichtwellenleitersystem der
Fiber-Optic System 2. Generation
SL16 Synchronous Fiber-Optic System for Synchrones Leitungssystem für
STM-16 Signals STM-16-Signale
SL16-2 Second Generation of SDH SDH-Lichtwellenleitersystem der
Fiber-Optic System for 2. Generation für STM-16-Signale
STM-16 Signals
SL4 Synchronous Fiber-Optic System for Synchrones Leitungssystem für
STM-4 Signals STM-4-Signale
SLD Synchronous Add/Drop Line Synchroner Add/Drop-Leitungs-
Multiplexer multiplexer
SLD16 Synchronous Add/Drop Line Synchroner Add/Drop-Leitungs-
Multiplexer STM-16 multiplexer STM-16
SLD16-2.4 Synchronous Add/Drop Line Synchroner Add/Drop-Leitungs-
Multiplexer of SL Series 2, multiplexer des SL16-Systems
Release 4 der 2. Generation, Release 4
SLD16E Synchronous Add/Drop Line
Multiplexer Extended
SLR16 Synchronous Line Regenerator Synchroner Leitungsregenerator
STM-16 STM-16
SLR16-2.2 Synchronous Line Regenerator Synchroner Leitungsregenerator
STM-16, Release 2.2 STM-16, Release 2.2
SLR4 Synchronous Line Regenerator Synchroner Leitungsregenerator
STM4 STM-4
SLT Synchronous Line Terminal Synchrones Leitungsendgerät
SLT16 Synchronous Line Terminal STM-16 Synchrones Leitungsendgerät
STM-16

1.Vorabzug:A30808-X3580-H504-1-7620 169
MMN Maintenance
SLD/T16-2.5

SLT4 Synchronous Line Terminal STM-4 Synchrones Leitungsendgerät

STM-4
SM Synchronous Multiplexer Synchroner Multiplexer
SM1/4 Synchronous Multiplexer, Hierarchy
Level STM-1/STM-4
SMA Synchronous Multiplexer Access
SMA1/4 Synchronous Multiplexer, Access
Level STM-1/STM-4
SMN-OS Synchronous Management Network
Operations System
SMPTF-16 Functional Group “Terminal Funktionsgruppe für optischen
Transport Function” STM-16-Port
SMT1D Synchronous Multiplexer Terminal, Synchroner Terminal-Multiplexer
Level 1
SNAP Sub-Network Attachment Point
SNCP Sub-Network Connection Protection
SNL Switching Network for Line Systems
(Module)
SOH Section Overhead (G.782)
S/P Serial to Parallel Converter Seriell/Parallel-Umsetzer
SPB-1 Functional Group “Synchronous Port Funktionsgruppe “Elektrischer
Block STM-1 (electrical) STM-1-Port”
SPB-1 Synchronous Port Block STM-1
SPI Functional Unit “SDH Physical Funktionseinheit “SDH Physical
Interface (G.782, G.783)” Interface (G.782, G.783)”
SPO Spontaneous Alarm Spontanalarm
SPRING Shared Protection Ring
SQM Sequence (of the conctenation Reihenfolge (der concatenation
channel numbers) Mismatch Kanalnummern) falsch
SR Synchronous Radio Richtfunk
SRAP Subrack Alarm Panel Baugruppenträger-Signalfeld
SRAP-PI Subrack Alarm Panel - Phone Baugruppenträger-Signalfeld und
Indication Telefonanzeigefeld
SSF Server Signal Fail Schwerwiegender Signalfehler
SSM Synchronization Status Message Meldung des
Synchronisationszustandes
SSMB Synchronization Status Message Byte SSM
Byte
SSU Synchronous Source Unit (Timing
Generator)
STM Synchronous Transport Module
STM-1 Synchronous Transport Module Basissignal der Synchronen
Level 1 Digitalen Hierarchie
(155,520 Mbit/s),
Hierarchiestufe 1
STM-16 Synchronous Transport Module
Level 16 (2.488 Mbit/s)
STM-N Synchronous Transport Module
Level N
SW Software

170 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

SXC Synchronous Cross-Connect

T0 System Clock Systemtakt
T3 Input for External Clock Reference Eingang für externes
Signal Takt-Referenzsignal
T4 Output for Clock Reference Signal Ausgang für Takt-Referenzsignal
TCN Threshold Crossing Notification Meldung für Schwellwertüber-
schreitung
TD Transmit Degraded Verringerte Sendeleistung
TDEG Transmit Degraded Verringerte Sendeleistung
TED Technical Description Technische Beschreibung
TELKAT Interface to TMN Schnittstelle zum TMN
TF Transmit Fail Ausfall des Sendesignals
TIF Telemetry Interface Access
(Module)
TIM Trace Identifier Mismatch
T-LCT TransXpress Local Craft Terminal Bedienrechner für
TransXpress-Netzelemente
TMN Telecommunications Management Netzmanagementsystem
Network
TMP Time Period/Total Measurement Dauer des gemessenen Intervalls
Period (in Sekunden)
T-NCT TransXpress Network Craft Terminal Erweiterter Bedienrechner für
TransXpress-Netzelemente
TP Termination Point
TransXpress Product Family Consisting of SL, Produktfamilie bestehend aus SL,
SMA, SR, SXC, WL SMA, SR, SXC, WL
TSAP Transport Service Access Point
TSD Trail Signal Degraded Gestörtes Pfadsignal
TSF Trail Signal Fail Fehlendes Pfadsignal
TSL Trail Signal Label
TTE Trail Trace Error Fehlerhafte Pfadkennung
TTF Functional Group “Transport Funktionsgruppe “Transport
Termination Function” Termination Function”
TTF-16 Functional Group “Transport Funktionsgruppe “Transport
Termination Function STM-16” Termination Function STM-16”
TTI Trail Trace Identifier Pfadkennung
TTIP Trail Trace Identifier Processing TTI-Verarbeitung
TTL Transistor-Transistor Logic Transistor-Transistor-Logik
TTP Trail Termination Point
TUG Tributary Unit Group (G.782)
TxDeg Transmit Degrade Signal Abgeschwächtes Sendesignal
TXFAIL Transmit Failure Fehlendes Sendesignal
UAS Unavailable Second(s)
UAT Unavailable Time (G.784)
UBAT Battery Voltage Batteriespannung
UCU Universal Control Unit Steuerung
ULED Feeding Bus for Card LEDs Hilfsspannung für die
Baugruppen-LEDs

1.Vorabzug:A30808-X3580-H504-1-7620 171
MMN Maintenance
SLD/T16-2.5

UNEQ Alarm “VC-4 Path Unequipped” Alarm “VC-4-Pfad nicht belegt”

UNIX Trademark of UNIX System
Laboratories Incorporated
USI User Interface
VC Virtual Container (G.782, G.783)
VC-4 Virtual Container Level 4
VC-4-UNEQ VC-4 Path Unequipped VC-4-Pfad nicht belegt
VC4TTP VC-4 Trail Termination Point
VCDB Variable Configuration Data Block
VCO Voltage Controlled Oscillator
VDD Operating Voltage Betriebsspannung
VDE Verein deutscher Elektrotechniker
VtM1 Distributor Module Verteilermodul
WDM Wavelength Division Multiplexing
WL8 Optical Multi-Wavelength Line Optisches Wellenlängen-
System Multiplexsystem
WLP Optical Line Amplifier Optischer Zwischenverstärker
ZA Disturbance Alarm Zentrale Anzeige
ZA(A) High-Priority Alarm Dringender Alarm für ZBBeo
ZA(B) Low-Priority Alarm Nichtdringender Alarm für ZBBeo
ZBBeo Central Service Observation Zentrale Betriebsbeobachtung
Equipment

172 1.Vorabzug:A30808-X3580-H504-1-7620
Maintenance MMN
SLD/T16-2.5

10 Supplements, Notes for Users

Dear reader,
this chapter provides you with a place in the manuals to keep documentation about any
corrections that have been identified or supplements.
You can also keep here any required error message corrections and notes for users is-
sued and distributed by the editorial team or by other departments.
If necessary we will include the list of corrections and supplements needed in a new edi-
tion of the manuals and the CD-ROM or take these into account for the next release.

1.Vorabzug:A30808-X3580-H504-1-7620 173
MMN Maintenance
SLD/T16-2.5

174 1.Vorabzug:A30808-X3580-H504-1-7620