Crossconnect Multiplexer CMXC User Manual

User Manual
Crossconnect Multiplexer CMXC

UMN CMXC
A50010-A3-C800-5-7619
2 A50010-A3-C800-5-7619
UMN CMXC User Manual
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted
in any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given "as is" and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THIS DOCUMEN-
TATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT,
INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT
LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS
OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR
THE INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright Nokia Siemens Networks 2008-2012. All rights reserved.
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 property 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 zwangslufig bestimmte Teile der Gerte unter Span-
nung. Einige Teile knnen auch eine hohe Betriebstemperatur aufweisen.
Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Krperverlet-
zungen und Sachschden fhren.
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
Gerte mssen die zutreffenden Sicherheitsbestimmungen erfllen.
A50010-A3-C800-5-7619 3
User Manual
UMN CMXC
Reason for Update
Details:
Chapter/Section Reason for Update
All SUE replaced by SUE-E with Ethernet interface
Issue History
Issue Date of issue Reason for Update
4 2/2009 Rebranding
5 02/2012 SUE replaced by SUE-E with Ethernet interface
4 A50010-A3-C800-5-7619
A50010-A3-C800-5-7619 5
User Manual
UMN CMXC
This document consists of a total of 156 pages. All pages are issue 5.
Contents
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.1 Structure of the Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.2 Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.3 Additional Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.4 Protection Measures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.4.1 Protection Against Excessive High Contact Voltages. . . . . . . . . . . . . . . . . 15
1.4.2 Protection Against Escaping Laser Light . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.4.3 Protection Against Fire in Racks or Housings. . . . . . . . . . . . . . . . . . . . . . . 16
1.4.4 Components Subject to Electrostatic Discharge. . . . . . . . . . . . . . . . . . . . . 16
1.4.5 Handling Modules (General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.4.6 Handling Optical Fiber Connectors and Cables . . . . . . . . . . . . . . . . . . . . . 17
1.4.7 Protection against Foreign Voltages in the System . . . . . . . . . . . . . . . . . . 17
1.4.8 Virus Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.5 CE Declaration of Conformity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.6 Waste of Electrical and Electronic Equipment (WEEE) . . . . . . . . . . . . . . . 18
2 System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.2 Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.2.1 Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.2.2 External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.2.3 Internal Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.2.4 Clock Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.2.5 Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.2.6 Subrate Multiplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.2.7 Voice Channel in Common Frequency Radio Networks. . . . . . . . . . . . . . . 28
2.2.8 Redundancy Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.2.9 Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
2.3 Operation and Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.3.1 Access to CMXC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.3.2 Operating Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.3.3 Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.3.4 Diagnostic Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.4 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.4.1 Storage Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.4.2 Initializing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.2 SNUS Shelf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.2.1 SNUS Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.2.2 Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.2.3 QD2 Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.2.4 Position and Assignment of Connectors. . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.2.5 Technical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6 A50010-A3-C800-5-7619
3.3 Central Unit CUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.3.2 Supervision and Alarm Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.3.3 Operating Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.3.4 Technical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.4 Interface Unit PU16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.4.2 Supervision and Alarm Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.4.3 Operating Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
3.4.4 Technical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
3.5 Supervision Unit SUE and SUE-E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
3.5.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
3.5.2 Control and Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
3.5.3 Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
3.5.4 Connector Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
3.5.5 Technical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
4 Commissioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4.1.1 Scope of the ITMN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4.1.2 Error Reports on the Installation Test Manual . . . . . . . . . . . . . . . . . . . . . . . 81
4.1.3 Dealing with Defective Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4.1.4 Procedure in the Event of Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4.1.5 Procedure in the Event of Serious Faults. . . . . . . . . . . . . . . . . . . . . . . . . . . 81
4.2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4.2.1 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4.2.2 Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4.3 Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4.3.1 Sequences for Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4.3.2 Visually Inspection (Check List) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
4.3.3 Starting the LCT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
4.3.4 Commissioning of the SNUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
4.3.5 Commissioning of the SUE-E. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
4.3.6 Commissioning the CUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4.3.7 Commissioning the PU16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.3.8 Creating the Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
5 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
5.1.1 Notes for Working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
5.1.2 Overview of Operating Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
5.1.3 Overview of Function Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
5.1.4 Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
5.1.5 SISA Communication Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
5.1.6 Interfaces used for Operating Purposes . . . . . . . . . . . . . . . . . . . . . . . . . . 106
5.1.7 Operation Modes of SUE-E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
5.2 Software Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
5.3 Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
A50010-A3-C800-5-7619 7
User Manual
UMN CMXC
5.3.1 SISA-V/LMXV2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
5.3.2 CUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
5.3.3 PU16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
5.4 Crossconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
5.4.1 Crossconnections 2 Mbit/s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
5.4.2 Cross Connections 64 kbit/s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
5.4.3 Cross Connections 8 kbit/s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
5.4.4 Conference Mode (between 64 kbit/s Time Slots only) . . . . . . . . . . . . . . 141
5.4.5 Displaying the used 2-Mbit/s Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
5.4.6 Overview of the used 64 kbit/s Crossconnections . . . . . . . . . . . . . . . . . . 147
6 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
6.1 Terminals for Maintenance and Fault Rectification. . . . . . . . . . . . . . . . . . 149
6.2 Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
6.2.1 Hardware Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
6.2.2 Software Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
6.2.3 Adjustments for Service in System Module . . . . . . . . . . . . . . . . . . . . . . . 150
6.2.4 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
6.3 Representation of Alarms in OS and LCT. . . . . . . . . . . . . . . . . . . . . . . . . 151
6.4 Elimination of an Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
6.4.1 Localization of an Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
6.4.2 Alarm Elimination by Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
6.4.3 Branch to Maintenance Procedures from Alarm Lists of the ACI . . . . . . . 152
6.5 Branch to Maintenance Procedure from Graphical User Interface of the
OS/LCT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
6.6 Explanations of the Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
6.7 Alarm Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
7 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
8 A50010-A3-C800-5-7619
Illustrations
Fig. 2.1 CMXC Application (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Fig. 2.2 CMXC Application in an FMX2R3.2 Ring Connection . . . . . . . . . . . . . . 21
Fig. 2.3 CMXC Block Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Fig. 2.4 Allocation of Alarm Contacts, Example ZA(A) . . . . . . . . . . . . . . . . . . . . 23
Fig. 2.5 CMXC Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Fig. 2.6 Redundancy Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Fig. 2.7 Power Supply in Shelf SNUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Fig. 2.8 CMXC in Stand-alone Operation Mode (Example) . . . . . . . . . . . . . . . . . 30
Fig. 3.1 SNUS with Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Fig. 3.2 SNUS Front View with the DIL Switches S101 to S116 . . . . . . . . . . . . . 34
Fig. 3.3 DIL Switches S105 to S116 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Fig. 3.4 DIL Switch S101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Fig. 3.5 DIL Switches S103 and S104 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Fig. 3.6 Location of Connectors and Equipping of Units . . . . . . . . . . . . . . . . . . . 37
Fig. 3.7 CUC Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Fig. 3.8 CUC Operating Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Fig. 3.9 Position of the Jumpers on the Pin Strips X401 . . . . . . . . . . . . . . . . . . . 52
Fig. 3.10 PU16 Block Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Fig. 3.11 Local Loop and Remote Loop Test Loops . . . . . . . . . . . . . . . . . . . . . . . 59
Fig. 3.12 PU16 Operating Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Fig. 3.13 Position of the Jumpers on the Pin Strips. . . . . . . . . . . . . . . . . . . . . . . . 64
Fig. 3.14 Operation and Monitoring via SUE-E Interfaces. . . . . . . . . . . . . . . . . . . 67
Fig. 3.15 Controls of the SUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Fig. 3.16 Controls of the SUE-E. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Fig. 3.17 Connector 11 of the SUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Fig. 3.18 Connector 10 of the SUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Fig. 3.19 Connector X2 of the SUE-E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Fig. 3.20 Connector X1 of the SUE-E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Fig. 4.1 SUE-E Dialog Software Download . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Fig. 4.2 SUE-E Register Card Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Fig. 4.3 SUE-E Register Card General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Fig. 4.4 Example of TCP/IP Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Fig. 4.5 SUE-E Register Card Inventory Data . . . . . . . . . . . . . . . . . . . . . . . . . 88
Fig. 5.1 QD2 Structure (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Fig. 5.2 SISA Structure of FastLink System. . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Fig. 5.3 Example of a SUE-E Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Fig. 5.4 QD2-Operatiion Mode 1: Slave with QD2 Interface . . . . . . . . . . . . . . . 107
Fig. 5.5 QD2 Operation Mode 2: Slave with Ethernet Interface. . . . . . . . . . . . . 108
Fig. 5.6 QD2 Tunnel via TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Fig. 5.7 SUE-E Register Card Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Fig. 5.8 CUC Register Card for Setting the Clock Synchronization. . . . . . . . . . 112
Fig. 5.9 CUC Register Card for Configuring the Alarm Supervision . . . . . . . . . 113
Fig. 5.10 CUC Register Card for Configuring the Ports . . . . . . . . . . . . . . . . . . . . 114
A50010-A3-C800-5-7619 9
User Manual
UMN CMXC
Fig. 5.11 CUC Register Card for Setting the ECC Operation Mode . . . . . . . . . . 115
Fig. 5.12 CUC Register Card for Activation/Deactivation of the ports . . . . . . . . 116
Fig. 5.13 CUC Register Card for Displaying the State of the ECC Ports . . . . . . 117
Fig. 5.14 PU16 Register Card for setting the Operator Loop . . . . . . . . . . . . . . . 118
Fig. 5.15 PU16 Register Card for Setting the Alarm Criteria . . . . . . . . . . . . . . . 119
Fig. 5.16 PU16 Register Card for Setting the Frame structure. . . . . . . . . . . . . . 119
Fig. 5.17 PU16 Register Card for Setting the Sa Bit Control . . . . . . . . . . . . . . . 120
Fig. 5.18 PU16 Register Card for Setting the Operation Mode. . . . . . . . . . . . . . 121
Fig. 5.19 PU16 Register Card for Displaying the State off all Ports . . . . . . . . . . 122
Fig. 5.20 Register Card Connections 2Mbit/s. . . . . . . . . . . . . . . . . . . . . . . . . . 123
Fig. 5.21 Register Card for Setting Filter Parameter. . . . . . . . . . . . . . . . . . . . . . 126
Fig. 5.22 Dialog for Creating Crossconnection 2 Mbit/s
(Example with Filter setting Representation of Resources: FG-FE) . 127
Fig. 5.23 Dialog for Setting the Time Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Fig. 5.24 Dialog for Setting the Switching Criteria . . . . . . . . . . . . . . . . . . . . . . . 128
Fig. 5.25 Register Card Connections 64kbit/s . . . . . . . . . . . . . . . . . . . . . . . . . 131
Fig. 5.26 Dialog for Creating the Crossconnection 64 kbit/s
(Example with Filter setting Representation of Resources; FG-FE) . 134
Fig. 5.27 Displaying of the Time Slots assigned to a Group (Example) . . . . . . . 135
Fig. 5.28 Dialog for Creating the Crossconnection 64 kbit/s (Example) . . . . . . . 135
Fig. 5.29 Register Card Connections 8kbit/s . . . . . . . . . . . . . . . . . . . . . . . . . . 137
(Example with Filter setting Representation of Resources; FG-FE) . 139
Fig. 5.31 Dialog Configure Conferences - CMXII-CAS (Example) . . . . . . . . . . 141
Fig. 5.32 Dialog Add data Conference - CMXC#...:CUC#... . . . . . . . . . . . . . . 143
Fig. 5.33 Register Card 2Mbps Port Usage (Example) . . . . . . . . . . . . . . . . . . 145
Fig. 5.34 Register Card 64Kbps CC Overview (Example) . . . . . . . . . . . . . . . . 147
Fig. 6.1 Elements of the Maintenance Procedures. . . . . . . . . . . . . . . . . . . . . . 153
10 A50010-A3-C800-5-7619
Tables
Tab. 1.1 Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Tab. 2.1 Structure of a PCI Time Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Tab. 2.2 PCI Frame Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Tab. 2.3 Conference Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Tab. 3.1 SNUS Overview of Addressing and the Units. . . . . . . . . . . . . . . . . . . . . 35
Tab. 3.2 Assignment of Connectors X141 (left and ) X142 (right) . . . . . . . . . . . . 38
Tab. 3.3 Terminal Assignment of Jacks X101, X102 and X121 . . . . . . . . . . . . . . 38
Tab. 3.4 Terminal Assignment of 9-Contact Jacks X143 and X144 . . . . . . . . . . . 39
Tab. 3.5 Terminal Assignment of Jacks X122 and X131 . . . . . . . . . . . . . . . . . . . 39
Tab. 3.6 Terminal Assignment of Jacks X109, X110, X 113, X114, X129, X130,
X133, X134 and X115. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Tab. 3.7 CUC Signaling the active Operating Mode . . . . . . . . . . . . . . . . . . . . . . . 46
Tab. 3.8 CMXC Indication of the Operating Mode . . . . . . . . . . . . . . . . . . . . . . . . 46
Tab. 3.9 CUC Indication of the standby Operating Mode . . . . . . . . . . . . . . . . . . . 46
Tab. 3.10 CUC Alarm Table (Active). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Tab. 3.11 CUC Alarm Table (Standby) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Tab. 3.12 CUC Connector (bottom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Tab. 3.13 CUC Connector (top) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Tab. 3.14 PU16 Signaling the Operating Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Tab. 3.15 PU16 Alarm Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Tab. 3.16 PU16 Connector (bottom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Tab. 3.17 PU16 Connector (top) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Tab. 3.18 Visual Signals Output by the SUE-E. . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Tab. 3.19 Operating Modes QD2-Slave 1 T-port (QD2Txx1) . . . . . . . . . . . . . . . . . 73
Tab. 4.1 Pin Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Tab. 4.2 Sequence of the Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Tab. 4.3 Shelf Equipping with SUE-E and Units for CMXC . . . . . . . . . . . . . . . . . 84
Tab. 4.4 Sequence for Creating 2-Mbit/s Cross Connections. . . . . . . . . . . . . . . . 93
Tab. 4.5 Sequence for Creating 64-kbit/s Cross Connections . . . . . . . . . . . . . . . 94
Tab. 4.6 Sequence for Creating 8-kbit/s Cross Connections . . . . . . . . . . . . . . . . 94
Tab. 4.7 Sequence for Creating Conferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Tab. 5.1 Overview of Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Tab. 5.2 Network Element CMXC and its associated Function Groups . . . . . . . 102
Tab. 5.3 Name of the Function Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Tab. 5.4 F Interface of the System Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Tab. 5.5 Correlation between Unit and Load Files . . . . . . . . . . . . . . . . . . . . . . . 109
Tab. 5.6 Configuration Parameters for the Network Elements . . . . . . . . . . . . . . 110
Tab. 5.7 List Entries in the Clock Priority List . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Tab. 5.8 Explanation of the Buttons in the CUC Register Card Clock sync. . . 113
Tab. 5.9 Explanation of the CUC Register Card ECC Alarm Criteria . . . . . . . . 113
Tab. 5.10 Explanation of the CUC Register Card Frame . . . . . . . . . . . . . . . . . . 114
Tab. 5.11 Explanation of the CUC Register Card ECC Mode . . . . . . . . . . . . . . 115
Tab. 5.12 Explanation of the CUC Register Card General . . . . . . . . . . . . . . . . . 116
A50010-A3-C800-5-7619 11
User Manual
UMN CMXC
Tab. 5.13 Explanation of the CUC Register Card ECC Status . . . . . . . . . . . . . 117
Tab. 5.14 Explanation of the PU16 Register Card General. . . . . . . . . . . . . . . . 118
Tab. 5.15 Explanation of the Pu16 Register Card Alarm Criteria . . . . . . . . . . . 119
Tab. 5.16 Explanation of the PU16 Register Card Frame . . . . . . . . . . . . . . . . . 120
Tab. 5.17 Explanation of the PU16 Register Card Clock Control . . . . . . . . . . . 120
Tab. 5.18 Explanation of the PU16 Register Card General. . . . . . . . . . . . . . . . 121
Tab. 5.19 Explanation of the PU16 Register Card Status View. . . . . . . . . . . . . 122
Tab. 5.20 Explanation of the Register Card Connections 2Mbit/s . . . . . . . . . . . 123
Tab. 5.21 Explanation of the Buttons on the Register Card
Connections 2Mbit/s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Tab. 5.22 Switchable Function Groups for 2Mbit/s Cross Connections. . . . . . . . 129
Tab. 5.23 Assignment of IPMB64/2 to Associate TP. . . . . . . . . . . . . . . . . . . . . . 129
Tab. 5.24 Explanation of the Register Card Connections 64kbit/s . . . . . . . . . . 131
Connections 64kbit/s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Tab. 5.26 Switchable Function Groups for 64kbit/s Crossconnections . . . . . . . . 135
Tab. 5.27 Explanation of the Register Card Connections 8kbit/s . . . . . . . . . . . 137
Connections 8kbit/s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Tab. 5.29 Switchable Function Groups for 8kbit/s Cross Connections . . . . . . . . 140
Tab. 5.30 Explanation of the Register Card Data Conferences. . . . . . . . . . . . . 141
Tab. 5.31 Explanation of the Buttons
on the Register Card Data Conferences . . . . . . . . . . . . . . . . . . . . . . 142
Tab. 5.32 Explanation of the Register Card 2Mbps Port Usage . . . . . . . . . . . . 145
2Mbps Port Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Tab. 5.34 Explanation of the Register Card 64Kbps CC Overview . . . . . . . . . . 147
Tab. 5.35 Explanation of the button on the Register Card
64Kbps CC Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Tab. 6.1 Determining the TOS Address from the DCN Alarm Address . . . . . . . 152
Tab. 6.2 Alarm Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
12 A50010-A3-C800-5-7619
A50010-A3-C800-5-7619 13
User Manual
UMN CMXC
1 Introduction
In this Manual, an overview about the components and their interworking in the access
network of the Crossconnect Multiplexer CMXC is given. Function, commissioning,
operation and maintenance are described in detail. The operation is done via the graph-
ical interface of the Operating System (OS). This is the Domain Manager ACI. For the
ACI DM, there is a separate documentation available (see Section 1.3 "Additional Doc-
umentation"). The software version you can take from the Release Notes which were
delivered with the software.
1.1 Structure of the Manual
The manual consists of the following Sections:
Introduction
System overview
Components
Commissioning
Operation
Maintenance and trouble shouting.
Technical Description The Technical Description (system overview and components) contains special informa-
tion about the CMXCs modules and the shelf, i. e. interfaces, Technical Data and the
connector assignment.
Commissioning The Commissioning describes all the procedures and measurements for activating the
installed system, including step-by-step instructions to commissioning the System
Module CMXC.
Operation This section offers a guide line to use the operating procedures for configuring and for
creating the crossconnections.
Maintenance The procedures which expedite the re-establishment of normal operating state after a
malfunction has occurred in the CMXC can be find out via the operating system by
Branch to Maintenance. The section Maintenance gives an overview of the possible
malfunctions and contains a guideline for the using of Branch to Maintenance.
14 A50010-A3-C800-5-7619
1.2 Typographical Conventions
In all sections of this manual, the following conventions are applied:
1.3 Additional Documentation
In addition, following documentation are used:
User Manual AccessIntegrator ACI DM version V8.3,
Prod. No. A50010-T3-H130-*-76K5
User Manual Flexible Multiplexer FMX2R3.2,
Prod. No. A50010-A3-C702-*-76K5
Infrastructure FastLink V10: UMN Infrastructure
Prod. No. A50010-A3-K419-*-7619
Project (planning) documentation.
Style of Representation Meaning
Courier Inputs and outputs
Example: Enter LOCAL as the server name
Command not found
Italics Variables
Example: name can be up to eight letters long.
Italics Variables fin procedures and title bas
Example: General NE Parameter. <Network Element#...>:CUC#...
Boldface Special emphasis
Example: This name may not be deleted
Quotation marks Labels on the user interface (e.g. windows, menu items, buttons)
Example: Activate the OK button
Make a selection in the File menu.
<Courier> Key combinations
Example: <CTRL> <ALT>+<ESC>
Successive menu items
Example: File Close
i
Additional items of information
!
Warnings at critical points in the activity sequence
Tab. 1.1 Typographical Conventions
A50010-A3-C800-5-7619 15
User Manual
UMN CMXC
1.4 Protection Measures
This Section contains a summary of the most important requirements with regard to pro-
tection of people and equipment. It does not claim to be complete. The installation in-
structions listed are shown in detail in the relevant Installation Manuals.
All assembly, installation, operation and repair work may only be undertaken by properly
trained and qualified personnel.
In the event of any injury (e.g. burns and acid burns) being sustained, seek medical help
immediately.
1.4.1 Protection Against Excessive High Contact Voltages
When handling the power supply or working on it, observe the safety measures de-
scribed in the specifications of the European Norm EN 50110, part 1 and part 2 (Oper-
ation of electrical Systems) and the valid national country specific standards.
Special warning labels on the shelves point to the dangers which can result from high
contact voltages when they are not grounded.
1.4.2 Protection Against Escaping Laser Light
When working on optical modules, note the regulations covering radiation safety on la-
ser light units (EN 60825).
Modules equipped with laser light units carry the laser symbol.
The following points should be noted here:
For operation in closed systems the laser light units comply with Laser class 1, and such
units can be identified by a stick on label as well as by a warning label.
Laser symbol
Warning label
16 A50010-A3-C800-5-7619
To guard against any possible hazards, all optical transmitters are equipped with an au-
tomatic laser shutdown circuit. This trips if an input signal is missing at the relevant op-
tical receiver, e.g. if the connection is interrupted.
This preventive measure should also be followed to avoid any damage to health by mak-
ing sure that escaping laser light is not directed towards the eye.
When breaking laser connections, the following procedure should be followed, despite
the presence of the laser shutdown circuit:
Pull out the plug-in unit about 5 cm
Disconnect optical fiber
Pull out unit completely.
1.4.3 Protection Against Fire in Racks or Housings
If FMX2R3.2 shelves are used in housing, the shelves must be performed the conditions
for a fire protection housing according to Din EN 60950.
To comply with fire protection standards as defined in Din EN 60950, a protective plate
(C42165-A320-C285) must be fitted into the floor of ETS and 19-inch standard racks.
The rack must also meet the requirements of a fire-resistant housing as defined in
Din EN 60950.
1.4.4 Components Subject to Electrostatic Discharge
When packing or unpacking, touching pulling or plugging plug-in units bearing the ESD
symbol, it is essential to wear a grounding bracelet, which should be grounded to a shel-
ter or rack when working on it. This ensures that the units are not subject to electrostatic
discharge.
Under no circumstances should the printed conductors or components of modules be
touched. Take hold of modules by the edge only.
Once they have been removed, modules must be placed in the conductive plastic
sleeves intended for them, and kept or dispatched in the special boxes or transport cas-
es bearing the ESD symbol.
In order to avoid further damage to defective modules, they should be treated with the
same degree of care as new ones.
Modules which are accommodated in a closed and intact housing are protected anyway.
European standard EN50082-1 provides information on the proper handling of compo-
nents which are subject to electrostatic discharge.
!
Note, the laser safety shutdown must be always activated.
ESD
symbol
!
Slide-in units bearing this symbol are equipped with components subject to electrostatic
discharge, that is to say the relevant safety provisions must be adhered to.
A50010-A3-C800-5-7619 17
User Manual
UMN CMXC
1.4.5 Handling Modules (General)
When working with modules (slide-in units, power supply modules, subracks) the follow-
ing points should be noted:
Existing ventilation equipment must not be changed. The sufficient air circulation
must not be obstructed.
When changing power supply modules you must switch off the fuse at the ac power
connection. Damaged power connection cables for ac power operated systems are
to be replaced by special leads supplied by the manufacturer.
All slide-in units except for power supply modules can be removed or inserted with
the power still applied. To remove and insert the units you should use the two levers
fitted to the front of the unit. A type label is fixed to one of the two levers providing
information on the hardware and software version of the unit.
When inserting and removing subracks and when transporting them, take their
weight into consideration.
Cables may never be disconnected by pulling on the cable. Disconnection/connec-
tion may only be undertaken by pushing in/pulling out the connector involved.
1.4.6 Handling Optical Fiber Connectors and Cables
Optical connectors are precision-made components and must be handled accordingly.
To ensure faultless functioning, the following points must be observed:
The minimum bending radius for optical fibers is 30 mm!
Mechanical damage to the surfaces of optical connectors impairs transmission qual-
ity by higher attenuation.
For this reason, do not expose the connectors to impact and tensile load.
Always fit optical fiber connectors with protective caps to guard them against me-
chanical damage and contamination. The protective dust caps should only be re-
moved immediately prior to installation.
Once the protective dust caps have been removed, you must check the surfaces
of the optical fiber connectors to ensure that they are clean, and clean them if nec-
essary.
For cleaning, the C42334-A380-A926 optical fiber cleaning tool or a clean, lint-
free cellulose cloth or a chamois leather is suitable. Isopropyl alcohol can be used
as cleaning fluid.
1.4.7 Protection against Foreign Voltages in the System
Two-level foreign voltage protection for the outdoor user lines is provided within the en-
tire system (shelf or ONU and subscriber ports on the slide-in units).
For outdoor user lines, 420-V gas tube arresters are recommended. These can be in-
stalled in the MDF (Main Distribution Frame) or an external MDF on the LSAs.
!
Beware of rotating parts.
!
Sufficient protection against foreign voltages for outdoor subscriber lines are only given
when appropriate protection elements are used.
18 A50010-A3-C800-5-7619
1.4.8 Virus Protection
Even when exchanging data via network or external data carries (e.g. floppy disks) there
is a possibility of infecting your system with a virus. The occurrence of a virus in your
system may lead to a loss of data and breakdown of functionality.
You have to do the following task:
You have to check every data carrier (used data carriers as well as new ones) for
virus before reading data from it.
You must ensure that a current valid virus scanning program is always available. This
program has to be supplied with regular updates by a certified software.
It is recommended to make period checks against viruses in your OS.
At the LCT it is recommended to integrate the virus scanning program into the start-
up sequence.
1.5 CE Declaration of Conformity
The CE conformity of the product will be given if the construction and cabling is under-
taken in accordance with the manual and the documents listed there in, e.g. mounting
instructions, cable lists. Where necessary account should be taken of project-specific
documents.
Deviations from the specifications or unstipulated changes during construction, e.g. the
use of cable types with lower screening values can lead to violation of the CE require-
ments. In such case the conformity declaration is invalidated and the responsibility pass-
es to those who have caused the deviations.
1.6 Waste of Electrical and Electronic Equipment (WEEE)
All electrical and electronic products should be disposed of separately from the
municipal waste stream via designated collection facilities appointed by the government
or the local authorities.
The correct disposal and separate collection of your old appliance will help prevent
potential negative consequences for the environment and human health. It is a
precondition for reuse and recycling of used electrical and electronic equipment.
!
To prevent a virus infection you may not use any software other than that which is re-
leased for Operating System (TMN-OS based on Basis AccessIntegrator), Local Craft
Terminal (LCT) and transmission system.
!
The operator is responsible for protecting against viruses, and for carrying out repair
procedures when the system is infected.
A50010-A3-C800-5-7619 19
User Manual
UMN CMXC
For more detailed information about disposal of your old appliance, please contact your
Nokia Siemens Networks service partner.
The statements quoted above are only fully valid for equipment which is installed in the
countries of the European Union and is covered by the directive 2002/96/EC.
Countries outside the European Union may have other regulations regarding the dispos-
al of electrical and electronic equipment.
20 A50010-A3-C800-5-7619
2 System Overview
2.1 Application
The CMXC crossconnect multiplexer is a compact solution to establish small network
nodes at 8-kbit/s, 64-kbit/s and 2-Mbit/s level. It supports up to 32 2-Mbit/s ports and
makes it possible to switch 64-kbit/s channels between these ports without blocking.
The CMXC connects communication paths between the following signals:
Max. 240 each with 8 kbit/s in the structure n 8 kbit/s (n = 1, 2 and 4)
Max. 992 each with 64 kbit/s in the structure n 64 kbit/s (n = 1 to 31)
64-kbit/s channels can be cross connected with and without signaling identification
(CAS).
Max. 32 each with 2 Mbit/s
The 2-Mbit/s signals are available at 32 E1 ports.
Unframed 2-Mbit/s signals are switched through transparently.
A frame selected from framed 2-Mbit/s signals can also be used as a reference
frame for signal processing in the CMXC.
The connections are usually bidirectional, but 2-Mbit/s and 64-kbit/s connections can
also be created unidirectionally or as a loop (loopback).
Fig. 2.1 CMXC Application (Example)
The crossconnect multiplexer offers the following possibilities:
Switching a maximum of 32 framed (with and without CRC4) and unframed 2-Mbit/s
signals with up to 992 switchable 64-kbit/s time slots
Group switching of n 64-kbit/s time slots by complying with the frame integrity
Bidirectional switching of up to 30 time slots (64 kbit/s) via a subrate matrix to switch
n 8-kbit/s channels (n = 1, 2 and 4) by changing the signal delays without process-
ing the identification
Establishing scheduled jobs and path protection on 2-Mbit/s level
Switching for Sa bits 4 to 8 to be used as the clock control bit in ring structures
LE2 3
P7
P8
SMX1/4c STM-1/STM-4
CMXC
ZS1
ZS60
FMX2R3.2
LE2 1
.
.
.
.
.
.
.
.
.
.
.
.
P1 P17
P3
P32
P2
P4
P1
P16
P9
P16
.
.
.
.
.
.
E1, 2 Mbit/s
G.703
E1, 2 Mbit/s
G.703
A50010-A3-C800-5-7619 21
User Manual
UMN CMXC
Providing 4 ECC channels (two synchronous with 64 kbit/s and two asynchronous
with 9.6 kbit/s) for remote control in TMN (telecommunications Management Net-
works) systems
Creating conference calls for speech signals (30 subscribers in 10 conferences) with
digital conference of the identification
Digital conferences for 64-kbit/s time slots with data signals (max. 10 conferences
with up to 30 subscribers) with digital conference of the identification
Synchronization to one of 7 freely configurable clock sources (2-Mbit/s data line
clocks) or central clock pulse T3
Supervision of the connection quality according to G.821/G.826
Providing the alarm signaling contacts ZA(A), ZA(B)
Software upgrade via the QD2 interface
Restore and backup configuration data
Complying with the requirements ITU-T G.812 and G.796.
Fig. 2.2 CMXC Application in an FMX2R3.2 Ring Connection
For an FMX2R3.2 application it is advantageous if system module FMX2R3.2 is operat-
ed together with the CMXC in a ring structure. This includes:
Optimum capacity utilization of the 2-Mbit/s lines in an FMX2R3.2 ring
2-Mbit/s path protection is retained in a ring structure
Both 2-Mbit/s ports of the CUD unit are available in a ring structure for the transmis-
sion of basic channels
Possibility of optionally cross connecting 8-kbit/s and 64-kbit/s channels
Suitable structures for network management
Concentration in the CMXC such as four ECC interfaces to integrate the SNUS shelf
and other system components in TMN.
CMXC
CMXC
CMXC
CMXC
FMX2R3.2
FMX2R3.2
FMX2R3.2
FMX2R3.2
22 A50010-A3-C800-5-7619
2.2 Structure
2.2.1 Overview
The following units belong to Crossconnect Multiplexer CMXC:
One or two central CUCs (central unit cross connect)
The central unit contains the switching matrix via which the communication paths
are connected. A second central unit is connected in parallel for module redundancy.
Up to two interface PU16 units (port unit with 16 2-Mbit/s ports)
The interface unit provides the 2-Mbit/s interfaces. One or two PU16s are equipped
depending on the number of desired interfaces.
Fig. 2.3 CMXC Block Diagram
2.2.2 External Interfaces
2-Mbit/s Interfaces (E1)
16 2-Mbit/s interfaces (E1in, E1out) are established for each PU16 unit.
HDB3-coded PCM signals are received and sent at the E1 interfaces. They correspond
to the ITU-T recommendation G.703/6.
The line impedance 75 unsymmetrical or 120 symmetrical can be set individually
for each interface by means of jumpers (see Section 3.3.3).
PCIS5 to 8
CUC
PU16
CUCS
PCI5 to 8 PCI1 to 4
PCIS1 to 4
CCUR
CCURS
LSI (1 to 7)
SVB
S
T
S
B
C
C
QD2-S T3in T3out
ZA(A), ZA(B)
48 V
4 ECC (V.11)
ZA(A), ZA(B)
48 V
4 ECC (V.11)
2 Mbit/s, G.703 2 Mbit/s, G.703
1
16
17
32
.
.
.
.
.
.
PU16
48 V
48 V
redundant CUC
CCUR
CCURS
A50010-A3-C800-5-7619 23
User Manual
UMN CMXC
Each 2-Mbit/s interface can be deactivated separately via the graphical user interface.
There is the choice between the following two states:
passive
Resulting from this, AIS will be sent at E1out.
tristate
The output driver from E1out will be switched to the high-impedance state.
T3 Interface
For clock synchronization, a clock signal can be fed via interface T3in and sent via
T3out. The interface is on the CUC and corresponds to the ITU-T recommendation
G.703/10. The input impedance of T3in can either be connected with high-impedance
(1.6 k II < 120 pF) or with low-impedance (120 symmetrical/75 unsymmetrical).
A clock signal is sent at T3out if the cross connect is synchronized by T3in or E1in of an
2-Mbit/s port. The interface is designed with low-impedance and is disconnected when
switching over to the redundant CUC.
QD2 Slave Interface
The CUC has a QD2 slave interface according to EIA RS485 which forms the TMN ac-
cess to the network element CMXC. Because the number of subscribers is not fixed
from the start due to the bus structure and the possibility of different equipping, the in-
terface is closed with high-impedance on the unit. Depending on the QD2 structure, the
bus termination must be suitably fitted on the outside. Care must be taken that two bus
loads are active for redundant equipping of CUC (maximum possible number is 32).
One QD2 address applies to active and standby CUCs.
ECC Interfaces
The ECC interfaces transmit control information from higher-level and to remote system
components. The control information is integrated in an ECC channel (64-kbit/s time
slot) within a 2-Mbit/s signal. The central CUC provides four ECC interfaces. They con-
form to ITU-T V.11 and can be accessed via the connector panel.
Two ECC interfaces are provided as synchronous interfaces (with clock lines) and two
as asynchronous interfaces (without clock lines). The synchronous interfaces are oper-
ated with 64 kbit/s. Signal distortions of +5% to 10% are obtained for asynchronous op-
eration with 9.6 kbit/s (or lower bit rates).
Alarm Contacts
The alarm contacts are arranged on central units CUC and are used to signal alarm
modes of the CMXC system module. They are established as floating relay contacts.
Fig. 2.4 shows the allocation of alarm contacts for ZA(A). The alarm contacts ZA(B) are
designed in an equivalent manner.
Fig. 2.4 Allocation of Alarm Contacts, Example ZA(A)
ZA(A)_A
ZA(A)_R
ZA(A)_U
(PUP)
ZA(A)
To the
connector panel
24 A50010-A3-C800-5-7619
Alarm contact ZA(A) optionally signals prompt alarms (A alarm) or service alarms
(S alarms) and the selection is menu-controlled. Alarm contact ZA(B) signals deferred
alarms (B alarm). The software of both CUCs activates these alarms.
The criteria to release A, B and S alarms are given in the alarm table (see Section 3.3.2).
CCUR Interface
The symmetrical interface lines CCUR (according to RS485), signal redundancy opera-
tion. Each CUC signals its active or standby mode via a separate line of the external
equipment so that these can switch over their PCI bus drivers.
2.2.3 Internal Interfaces
PCI Interfaces
The PCI interfaces transmit useful data between the CUC and units PU16. They also
distribute the clocks of the master clock from the CUC to the peripheral equipment.
A PCI link establishes a point-to-point connection between the CUC and the two PU16s
via two symmetrical two-wire lines (separately in the upstream and downstream direc-
tion) on the rear panel.
The PCI frame contains 162 time slots with a width of 10 bits each. The CAS bit is not
used in the CMXC and is loaded on fixed potential.
The PCI time slots are designed according to Tab. 2.1.
A useful load of 4 2-Mbit/s links with 32 PCM time slots each is mapped into each PCI
frame as shown below:
Bit 1 2 3 4 5 6 7 8 9 10
TS 0 to 160 D1 D2 D3 D4 D5 D6 D7 D8 CAS P
TS 161 R 1 1 1 0 0 1 1 0 P
D1...D8: PCM data
CAS : Bit for CAS signaling (not used here)
P : Parity bit
R : Reserved bit (in PCI downstream direction: Activity mode of the CUC is displayed)
Tab. 2.1 Structure of a PCI Time Slot
PCI
time slot
PCM
link
PCM
time slot
0 1
0
1 2
2 3
3 4
4 1
1
5 2
6 3
7 4
....
Tab. 2.2 PCI Frame Structure
A50010-A3-C800-5-7619 25
User Manual
UMN CMXC
LSI Interface
The LSI interface is established on PU16 (transmitter) and CUC (receiver). It consists of
7 symmetrical line pairs and transfers the E1in guide clock from the PU16 to the CUCs.
An 8th line pair transfers the frame pulse belonging to the E1 guide clock.
Of the two PU16s, only one clock source may be activated per LSI line and the remain-
ing transmit drivers are connected with high-impedance. The LSI interfaces are activat-
ed via the software according to a clock priority list, see section 2.2.4.
Supervision Bus SVB
Internal communication between units CUC and PU16 takes place via the supervision
bus SVB. This bus is an HDLC interface which works according to the master-slave prin-
ciple. The master (primary station) is the active CUC and the slaves (secondary station)
the PU16 units.The standby CUC does not access the bus and the line drivers are con-
nected inactively.
Supervision bus SVB is used for the following functions:
Loading the software and configuration data of units PU16 during intitialization,
Distributing the SISA messages via the active CUC to the SISA functional units of
units PU16,
Module-internal communication between CUC and PU16
(e.g. control commands of the CUC to unit PU16 for clock source control).
CCUR Interface
There are two unsymmetrical connections between the units to signal the operating
mode of both CUCs and the PCI buses and their redundancy switchover. On PU16, only
receivers are connected to the record circuits whereas they are crossed between the
CUC receive and transmit lines. A high level on line CCUR indicates that the left CUC
is active and is connected via the primary PCI bus. In this mode, the CCURS line is at
the low level. When changing levels, a switchover to the redundant PCI bus and to the
redundant central CUC takes place.
CC Interface
The CC interface (cross coupling interface with CC_I and CC_O) connects both CUCs
and synchronizes the standby CUC via the clock master. The clock contains the fre-
quency reference and the position of the central multiframe synchronization pulse is im-
pressed via a pulse duration modulation.
124 1
31
125 2
126 3
127 4
128
free ...
160
161 FSW
PCI
time slot
PCM
link
PCM
time slot
Tab. 2.2 PCI Frame Structure
26 A50010-A3-C800-5-7619
CCR Interface
The CCR interface connects both CUCs and synchronizes the PCI frame of the standby
CUC via the active CUC.
STSB Interface
Data is transmitted between the active CUC and the standby CUC via the STSB inter-
face (status standby control). In this way the two CUCs run quasisynchronously and
switch over procedures can be released very quickly via the static command line
(CCUR). The STSB interface is a point-to-point connection between the two central
units inserted next to one another.
2.2.4 Clock Synchronization
For the CMXC function it is necessary that all the 2-Mbit/s signal streams E1in and
E1out are applied with the same clock signal. This requirement is met if the signals at
the output of preceding equipment is derived from the same synchronous clock; other-
wise is must be guaranteed by establishing clock loops in all the closed user terminals
(transmitting clock = recovered receive clock). On violation of this principle, frame slips
occur which lead to interferences in signal transmission.
The active CUC is the clock master for all the other CMXC units.
The 2-MHz guide clock can be derived from the following clock sources, see Fig. 2.5:
T3in interface to feed an external synchronous clock,
Regenerated clock signal which was retrieved from the E1in data of a 2-Mbit/s port
Internal oscillator on the CUC (emergency operation).
7 symmetrical wire pairs LSI1 to LSI7 (line synchronization input) have been provided
for the E1in guide clocks from the PU16 units to the CUC. The source for the guide clock
can be selected at random from the 32 E1 ports. The software selects the activated
clock source on the basis of a priority list. This decides which one of the possible receive
clocks of the E1in ports are loaded on which of the 7 guide clock lines.
If PU16, which provides a guide clock, identifies a malfunctioning of the E1in signal, it
disconnects the corresponding clock source. The CUC then identifies clock failure and
switches over to the clock source with the next lower priority (see the alarm table of the
CUC in Section 3.3.2). If all the external clock sources fail, the PLL of CUC is switched
to free-running and a prompt alarm is released.
If a clock source with a higher priority becomes available while operating with a lower
priority standby clock, the guide clock switches over automatically.
A50010-A3-C800-5-7619 27
User Manual
UMN CMXC
Fig. 2.5 CMXC Synchronization
Phase synchronicity requirements of G.703 interface signals can be found in the ITU-T-
recommendations G.823 and ETS TBR-12 and they are formed by buffer stores and jit-
ter reducers on units PU16. An elastic store sets up the frame synchronicity.
The synchronous clock on units PU16 is derived by means of PLL from the PCI down-
stream signal.
For subsequent equipment, the active CUC provides a 2.048-MHz synchronous clock
T3out which is synchronous to the current system clock.
Both CUCs manage the T3 interface. The software ensures that only the active CUC ac-
cesses the interface.
2.2.5 Conferences
A maximum of 30 digital and 30 analog conference channels can be switched in up to
20 mutually independent conferences at the same time. The requirements for analog
and digital conferences differ:
For the analog conference, each conference participant receives the total of all the other
signals. Its individual transmit signal is deactivated. The identifications are switched dig-
itally for the participants in analog conferences.
For the digital conference, the signals of all the participants are switched with bit-by-bit
OR operation. Its individual transmit signal is retained. For the participants in digital con-
ferences, the identifications are also switched digitally as for analog conferences.
.
.
.
.
.
.
.
LSI1 LSI7
...
E1in/17 to 32
...
T3in T3out
E1in/1 to 16
...
PCI
up
CUC standby CUC
PU16 PU16
Analog conferences Digital conferences
Maximum number of conference participants 30 30
Maximum number of participants per conference 10 30
Maximum number of parallel conferences 10 10
Tab. 2.3 Conference Requirements
28 A50010-A3-C800-5-7619
2.2.6 Subrate Multiplexer
To switch subrate connections, a subrate channel of 1, 2 or 4 bits is converted to 8 full
bits and then switched and compressed again. Conversion takes place by oversampling
or subsampling.
A maximum of 240 bidirectional subbit rate signals each with 8 kbit/s in CMXC can be
switched.
2.2.7 Voice Channel in Common Frequency Radio Networks
In this application a voice channel is transmitted from one source to a number of desti-
nations. The group delay time of the voice channel is constant here. There can only be
one such connection within the network. This connection is always unidirectional.
The source can only be a VF interface in multiplexer FMX2R3 (with units CUD and
UAC68). All subsequent multiplexers/crossconnect multiplexers must synchronize
themselves to the outgoing frames of the multiplexer with the synchronizing clock
source.
2.2.8 Redundancy Concept
2.2.8.1 Module Redundancy
To increase the operating reliability of CMXC, the central CUC is duplicated so that fur-
ther functioning of the entire system is guaranteed if the unit fails. Failure of the active
CUC leads to a redundancy switchover if there is another CUC in the CMXC system
module. The software releases redundancy switchover. To this end, the operability of all
the components is supervised on both CUCs (active and standby).
Units PU16 are not equipped redundantly, i.e. there is no protection switching if a PU16
unit fails. Therefore, the CMXC system module has a fault penetration range of 16 E1
interfaces.
Fig. 2.6 Redundancy Concept
The PCI buses are duplicated, see Fig. 2.6. A switchover to the redundant bus is pos-
sible in case of faults. The central CUCs are connected to separate signal groups (PCIS
at standby unit).
PCI1 to 8
PCIS1 to 8
STSB
CCUR
CCURS
C
C
U
R
C
C
U
R
S
PU16
CUC
CUCS
PU16
CCUR
To external equipment
Redundant CUC
A50010-A3-C800-5-7619 29
User Manual
UMN CMXC
However, the decentralized PU16 units are connected to both the bus systems. They
receive information about which one of the two PCI buses is active, the CCUR and
CCURS signals (see CCUR Interface).
Bus STSB is used as the communication interface for redundancy operation between
the two CUCs (see STSB Interface).
The clock sources for the synchronous clock of CMXC is switched over to standby ac-
cording to a priority list (see section 2.2.4).
Both CUCs manage the T3 interface and the QD2 interface. The software ensures that
only the active CUC accesses the specific interface.
2.2.8.2 Alternative Route Switching for a 2-Mbit/s Connection
One alternative route can be configured for each 2-Mbit/s connection which is switched
over to for the alarm criteria below:
LOS, AIS,
Local loop, remote loop always
SYN, BER-3, only for framed signals
SYNK, AISK, only for framed signals with CAS signaling
BER-5/-6 only for framed signals, if the alarm criterion
was switched on
D-Bit, D
k
-Bit, N-Bit, N
k
-Bit never
The alternative route must be entered into the user menu.
The alarm criterion BER-5/-6 has a lower priority than the LOS, AIS, SYN, BER-3, AISK,
SYNK, local loop and remote loop alarms. If a high priority alarm occurs at the one port
and a low priory alarm at the other port, the low priority alarm will be used as the trans-
mission route. Therefore, the alarm criterion should be switched on.
2.2.9 Power Supply
Units CUC and PU16 of CMXC are supplied with an input voltage of 48 V (36 V to
72 V). The input voltage is fed via a plug in the connector panel of the shelf. For redun-
dancy operation, a second plug (S) is provided to feed a further 48 V. The active and
standby CUCs are connected to either of the two voltages in each case. The PU16 units
are connected to both voltages. The input voltages are fed to the consumers via EMC
filters on the backplane of the shelf.
Fig. 2.7 Power Supply in Shelf SNUS
CUCS CUC
PU16 PU16
Connector panel
48 V/
60 V
48 V-S/
60 V-S
30 A50010-A3-C800-5-7619
2.3 Operation and Supervision
2.3.1 Access to CMXC
The CMXC forms an SISA Network Element. The central CUC accesses the Network
Element via the QD2 slave interface. Addressing the CMXC Network Element is allocat-
ed slot-coded via the rear panel of shelf SNUS.
The following types of access are possible, see Fig. 2.8:
CMXC connection to the OS via the QD2 slave interface
QD2 access is in stand-alone operation of unit SNUS via supervision unit SUE-E.
Switch positions connect the internal QD2 bus to the master port of the SUE-E.
LCT connection via the F interface of the supervision unit.
In stand-alone operation, the DCN channels are connected directly to the QD2 slave
port of SUE-E via the connector panel of the shelf.
Fig. 2.8 CMXC in Stand-alone Operation Mode (Example)
2.3.2 Operating Elements
The CUC has a jumper to set the impedance of the T3in interface to high-impedance
(1.6 k II < 120 pF) or low-impedance (120 symm./75 unsymm.) operation (see
Section 3.3.3).
Jumpers are located on units PU16 to set the impedances of the E1 interfaces. The line
impedance of each F1 interface can either be set separately to 75 unsymmetrical or
to 120 symmetrical (see Section 3.4.3).
A 5-step DIL switch is arranged on shelf SNUS to set the SISA address of the system
module (see Section 3.2.4).
Detailed information about the switch settings and plug connector allocations can be
found in Section 3.
i
SUE and SUE-E are combined in the name SUE-E. The SUE-E is a subsequent unit for
SUE and fulfils the same functions, but has in addition an Ethernet interface.
NE
ASA32
LCT
F
SISA-V
LMX/V2
SUE-E
QD2 slave 1
RS485/RS232
V.28
QD2 slave 2
Internal QD2 bus
RS485
primary or
CMXC
SISA-V
ECC (V.11)
FMX2R3
SISA-V
SMX1/4c
SISA-V
LTCOH/LT
SISA-V
LT12CM/LT
LT22CM/LT
LTO/LT
Internal QD2 bus
T port (QD2 slave 1) for other NEs
QD2-M
Ethernet
A50010-A3-C800-5-7619 31
User Manual
UMN CMXC
2.3.3 Supervision
SMD-LEDs signal the operating mode for each unit (see Section 3.3.2 to 3.4.2).
The E1, PCI and LSI interfaces are supervised according to alarm tables on the units
(see Section 3.3.2 to 3.4.2).
the CUC supervises PCI and LSI links between the PU16 and the CUC.
PU16 evaluates the E1 interfaces.
SISA0 alarms are reported to the OA&M computer. Two LEDs (red and green) on the
CUC indicate the system alarms.
2.3.4 Diagnostic Functions
When switching on the input voltages for CMXC, self-test routines of the software and
hardware components on the units are first of all performed.
In operation, PCM signals received at the E1 ports can be analyzed continuously ac-
cording to ITU-T G.821 and the values stored in quality data records. Both the current
quality counter and any stored record can be displayed.
The number of frame slips occurring at a 2-Mbit/s port can be requested via the LCT.
The following loop connections can be established on PU16, see Section 3.4.1:
Local loop for fault location within the CMXC system module,
Remote loop for fault location of the external 2-Mbit/s connections.
The procedures for alarm evaluation are contained in the Section 5.
2.4 Software
The required SW of network element CMXC is loaded with the craft terminal and SW
download via the V.24 or the QD2 interface. Special SW in the form of a file exists for
each CMXC unit.
2.4.1 Storage Structure
Each one of the units has a unit computer consisting of a micro controller and various
storage circuits (FEPROM, EEPROM, RAM) for administering the software and the da-
ta. The micro controller controls the internal functional flow on the individual units. The
storage circuits are used for software and data protection. In order to retain the config-
uration in case of a fault, backup versions are stored in the OS which can then be set up
again at a later stage.
Firmware containing the initial program loader, self-test programs and type label data
are found on each unit. The firmware is stored in the flash EEPROM on the unit. The
RAM contains the current SW which is loaded by the initial program loader.
2.4.2 Initializing
After power-up each unit starts the initial program loader software contained in the
FEPROM. The initial program loader comprises the self-test routines of the unit (dura-
tion a maximum of 30 s) and log-in into the supervision bus. After successful software
download and starting, the units read-in their configuration data.
For an SW update, the current SW version carries on working in the RAM. A reset must
always be performed after a new SW has been loaded, so that the unit can reboot.
32 A50010-A3-C800-5-7619
3 Components
3.1 General
The CMXC consists of a maximum of two CUC units and a maximum of two PU16 units
in double eurocard size. The units are installed in an SNUS shelf.
The SUE-E unit used for stand alone operation mode is equipped in SNUS shelf also.
The 19-inch SNUS shelf is used for indoor operation. It can be delivered as stand-alone
or with a complete infrastructure (with power supply, backup battery and signal distrib-
utor) as SNU60FTTB or in an SNU180FTTB.
The following system modules can be equipped in SNUS together with CMXC:
Multiplexer FMX2R3.2
Line equipment for 2-Mbit/s transmission
on copper cable
with U
K2
interface according to FTZ 1 TR221 or G.703/short-haul (LT2ME1),
HDSL-coded (1 2 Mbit/s with LTCOH/LT12CM or 2 2 Mbit/s with LT22CM),
on optical cable via single mode glass fibers
1 2 Mbit/s via 2 fibers according to FTZ 1 TR222 (LUOT-A), or
2 2 Mbit/s, transmit and receive direction via 1 fiber (LTO).
Synchronous multiplexer SMX1/4c or the optical line equipment OMX16
All external CMXC interfaces can be accessed via the connector panel of the shelf.
Should FMX2R3.2, 2-Mbit/s line equipment and OMX16/SMX1/4c be equipped, the
2-Mbit/s interfaces have already been prewired internally and only a section of the inter-
faces can be accessed from the outside. Detailed information about internal wiring can
be found in the User Manual FMX2R3.2, UMN:TED, see Section 1.3 Additional Docu-
mentation.
i
SUE and SUE-E are combined in the name SUE-E. The SUE-E is a subsequent unit for
SUE and fulfils the same functions, but has in addition an Ethernet interface.
A50010-A3-C800-5-7619 33
User Manual
UMN CMXC
3.2 SNUS Shelf
3.2.1 SNUS Layout
Fig. 3.1 SNUS with Front Panel
101
X1 V1 A1 B1 C1 D1 E1 F1 G1 H1 J1 K1 L1 M1 N1 P1 Q1 R1 S1
E2 F2 G2 H2 J2 K2 L2 M2 N2 P2 Q2 R2 S2 T2 D2 C2 B2
Y2
X2 U2 W2 V2
U3 V3 W3 X3
Y3
SMX DSMX Trib.
Unit
T
3
T
3
(
+
)
(
-
)
4
8
V
6A
(
+
)
(
-
)
4
8
V
6A
Q
D
2
-
S
l
a
v
e
Q
D
2
-
M
a
s
t
e
r
T
l
n
T
l
n
T
l
n
G
.
7
0
3
T
l
n
T
l
n
T
l
n
G
.
7
0
3
H
D
S
L
(
L
T
3
)
P
C
I
G
.
7
0
3
G
.
7
0
3
G
.
7
0
3
G
.
7
0
3
G
.
7
0
3
1

.

.

4
9

.

.

1
2
1

.

.

4
9

.

.

1
2
1
7
.

.

2
1
1

.

.

4
9

.

.

1
2
address
1 16
on
off
L
C
1
F
R
C
O
N
L
C
2
L
C
3
L
C
4
L
C
5
L
C
6
L
T
2
PB
A2
Port Unit 1 CMXC Port Unit 2 Trib Unit SMX
A3
T
l
n
T
l
n
T
l
n
T
l
n
T
l
n
T
l
n
G
.
7
0
3
G
.
7
0
3
5

.

.

8
1
3
.

.
1
6
E
C
C
P
C
I
S
G
.
7
0
3
G
.
7
0
3
5

.

.

8
1
3
.

.
1
6
G
.
7
0
3
G
.
7
0
3
5

.

.

8
1
3
.

.
1
6
G
.
7
0
3
1
7
.

.
2
1
V
.
1
1
x
t
.

c
o
n
t
a
c
t
s
Z
A
L
T
1
1
2
1
2
1
2
1
2
1
2
1
2
1
2
1
2
1
2
1
2
F-PC
SNUS
LASER KLASSE 1
LASER CLASS 1
Achtung!
Laser und Glasfaser
mechanisch
nicht belasten
ATTENTION!
LASER AND GLASS FIBER
MUST NOT BE
PHYSICALLY DAMAGED
OR STRAINED
B A D C F E H G K J M L P N R Q T S V U X W
34 A50010-A3-C800-5-7619
Fig. 3.2 SNUS Front View with the DIL Switches S101 to S116
Fig. 3.3 DIL Switches S105 to S116
B A D C F E H G K J M L P N R Q T S V U X W Y
X1 V1 A1 B1 C1 D1 E1 F1 G1 H1 J1 K1 L1 M1 N1 P1 Q1 R1 S1
address
1 16
on
off
Q
D
2
-
S
l
a
v
e
Q
D
2
-
M
a
s
t
e
r
T
l
n
T
l
n
T
l
n
G
.
7
0
3
T
l
n
T
l
n
T
l
n
G
.
7
0
3
H
D
S
L
(
L
T
3
)
P
C
I
G
.
7
0
3
G
.
7
0
3
G
.
7
0
3
G
.
7
0
3
G
.
7
0
3
(
+
)
(
-
)
4
8
V
6A
(
+
)
(
-
)
4
8
V
6A
Y2
X2 U2
E2 F2 G2 H2 J2 K2 L2 M2 N2 P2 Q2 R2 S2 T2
L
C
1
F
R
C
O
N
L
C
2
L
C
3
L
C
4
L
C
5
L
C
6
L
T
2
L
T
1
1

.

.

4
9

.

.

1
2
1

.

.

4
9

.

.

1
2
1
7
.

.

2
1
1

.

.

4
9

.

.

1
2
W2 V2
D2 C2 B2
PB
A2
Port Unit 1 CMXC Port Unit 2 Trib Unit SMX
A3
T
l
n
T
l
n
T
l
n
T
l
n
T
l
n
T
l
n
G
.
7
0
3
G
.
7
0
3
5

.

.

8
1
3
.

.
1
6
E
C
C
P
C
I
S
G
.
7
0
3
G
.
7
0
3
5

.

.

8
1
3
.

.
1
6
G
.
7
0
3
G
.
7
0
3
5

.

.

8
1
3
.

.
1
6
G
.
7
0
3
1
7
.

.
2
1
V
.
1
1
U3 V3 W3 X3
Y3
SMX DSMX Trib.
Unit
T
3
T
3
x
t
.

c
o
n
t
a
c
t
s
Z
A
201 202 204 205 206 207 208 209 210 211 212 213 214 215 216 217 SNUS
201
202
204 205 206 207 208 209 210 211 212 213
214
215
216
217
101
S103 S104
S102
S111 S112 S114 S115
S113 S116
S108
S109
S105
S106
S107
S101
As-delivered condition:
For S105 to S116 all sliders are set to the down
position.
These DIL switches are not used for System
Module CMXC.
ON
S114
1 2 3 4
O N
S108
ON
S109
ON
S111
1 2 3 4
ON
S112
1 2 3 4
O N
S105
ON
S113
1 2 3 4
O N
S106
ON
S107
ON
S115
1 2 3 4
ON
S116
1 2 3 4
A50010-A3-C800-5-7619 35
User Manual
UMN CMXC
3.2.2 Addressing
Almost all units in the SNUS are assigned addresses via the backplanes. The addresses
assigned to the slots are shown in Tab. 3.1.
The SISA addresses of the SUE-E are set using DIL switch 101 in the terminal panel
(possible addresses: 1 to 30), see Fig. 3.6 and Fig. 3.4.
Fig. 3.4 DIL Switch S101
The addresses implemented in the SNUS are shown in Tab. 3.1.
Unit In slot QD2 address Slot address (connected and fixed)
SUE-E 201 Is set using DIL switch
S101 in the terminal panel
of the SNUS, see Fig. 3.6
and Fig. 3.4.
5Bit = 1 to 30
5 bit = 3
(K0...K4 shelf model)
CUD 202 Is set using DIL switch
S102 on the backplane of
the SNUS, see Fig. 3.2.
5Bit; here only 1 to 8 usable
SEL_0 = GND
SEL_1 = GND
Line cards 1-6 203 to 208 4 bit = 1 to 6
LT1 as LU
1) 3)
207 Fixed (4 bit) = 7
LT1 as LT
2) 3)
207 Fixed (5 bit) = 7
LT2 as LU
1) 3)
208 Fixed (4 bit) = 8
LT2 as LT
2) 3)
208 Fixed (5 bit) = 8
LT3 as LU
1)
209 Fixed (4 bit) = 9
LT3 as LT
2)
209 Fixed (5 bit) = 9
PU16(1) 210 5 bit = 10
CUC(1) 211 Fixed (5 bit) = 13 5 bit = 11
CUC(2) 212 Fixed (5 bit) = 13 5 bit = 12
PU16(2) 213 5 bit = 13
ADM (SMX) 216 Fixed (5 bit) = 16
Trib.Unit 214
LU
1)
= LUOT, LUCP, LUC, LUCT
LT
2)
= LTO, LTCOH, LT12CM, LT22CM, LT2ME1
3) If an LT/LU unit instead of a line card is equipped in slots 207 or 208, the slot must be configured accord-
ingly (with DIL switches S106 and S107 for slot 207 or with DIL switch S109 for slot 208). Switches S105
and S108 must always be switched, see Fig. 3.2, Fig. 3.3
Tab. 3.1 SNUS Overview of Addressing and the Units
1
ON = LOW = log 0
Example:
Switch 1 on OFF corresponds to 2
4
= 16
Switch 5 on OFF corresponds to 2
0
= 1
Corresponds to address 17 for the SUE
ON (0)
OFF (1)
2
4
2
3
2
2
2
1
2
0
5
36 A50010-A3-C800-5-7619
3.2.3 QD2 Structure
If the stand alone operation mode the SUE-E must be used for supervision. Operating
or maintenance functions can be carried out locally via an F interface using a local craft
terminal. The SUE-E monitors all units in the SNUS. The internal QD2 bus of the SNUS
must be switched using switches S103 (all slider units on OFF) and S104 (all slider
units on ON) to the SUE-E master port, see Fig. 3.2 and Fig. 3.5.
Slave port 1 of the SUE-E is executed as a T interface, likewise the T connections are
accessible in the X101 slave connector, see Fig. 3.6.
Master port 1 of the SUE-E is stored in the QD2 X102 master connector and is the start-
ing point of the internal QD2 bus when used in standalone mode. Further slaves in the
internal QD2 bus can be connected to X102.
Slave port 2 of the SUE-E is also located in the QD2 X102 master connector. The over-
head interface of LT location 3 is also located here. Connection to slave 2 via an appro-
priately assigned connector is possible and thus a control channel via the overhead from
a remote device (unit in LT location 3 as a feeder for the SNUS).
Further control is possible via ECC channels. The ECC connections of both CUC loca-
tions are stored in parallel and in a 25-pin D-sub connector. Of the four ECC interfaces
of the CMXC, two are equipped with clock transmission. The ECC of the CUD is also
routed to this X131 D-sub.
Fig. 3.5 DIL Switches S103 and S104
PSD 218 5 bit = 18
optional with
OMX16
DSMX34 215 5 bit = 15
OTRU36 217 5 bit = 17
OTSU_2M 218 Fixed (5 bit) = 18
Unit In slot QD2 address Slot address (connected and fixed)
LU
1)
= LUOT, LUCP, LUC, LUCT
LT
2)
= LTO, LTCOH, LT12CM, LT22CM, LT2ME1
3) If an LT/LU unit instead of a line card is equipped in slots 207 or 208, the slot must be configured accord-
ingly (with DIL switches S106 and S107 for slot 207 or with DIL switch S109 for slot 208). Switches S105
and S108 must always be switched, see Fig. 3.2, Fig. 3.3
Tab. 3.1 SNUS Overview of Addressing and the Units (Cont.)
ON
S104
4 3 2 1
ON
S103
4 3 2 1
As-delivered condition:
For S103 all slider units are set to OFF (down position) and for
S104 all slider units are set to ON (up position), i.e. the SNUS is
monitored by a SUE (standalone, without COMPS and without OSU)
A50010-A3-C800-5-7619 37
User Manual
UMN CMXC
3.2.4 Position and Assignment of Connectors
Fig. 3.6 Location of Connectors and Equipping of Units
In the following topics, assignments of connectors in terminal panel used for the CMXC
units are only described.
4
8

V
4
8

V
Q
D
2
-
S
A
l
a
r
m
PB
-
+
-
+
A
X101 to X154 are the connectors in the terminal panel
X201 to X316 are the connectors for the units in the shelf
1) DIL switch S101 for setting the SISA address of the SUE
2) LT1/2/3 = LT/LU units (LT22CM may only be inserted into slot 209)
C
Q
D
2
-
M
B D E F G H
I
/
O

1
-
4
J
I
/
O

9
-
1
2
K
H
D
S
L
-
L
T
3
L
P
C
I
M
I
/
O

1
-
4
N
I
/
O

9
-
1
2
P
I
/
O

1
-
4
Q
I
/
O

9
-
1
2
R
I
/
O

1
7
-
2
1
S
I
/
O

5
-
8
I
/
O

1
3
-
1
6
E
C
C
-
C
U
C
P
C
I
S
I
/
O

5
-
8
I
/
O

1
3
-
1
6
I
/
O

5
-
8
I
/
O

1
3
-
1
6
I
/
O

1
7
-
2
1
Z
A
T
3
a
n
T
3
o
u
t
V
.
1
1
Add.
1)
E3IN
X153
X151
E3OUT
X154
X152
X
3
0
1
201
X
2
0
1
S
U
E
-
E
X
3
0
2
202
X
2
0
2
C
U
D

/

C
U
A
X
3
0
3
203
X
2
0
3
L
C
1

/

F
R
C
O
N
X
3
0
4
204
X
2
0
4
L
C
2
X
3
0
5
205
X
2
0
5
L
C
3
X
3
0
6
206
X
2
0
6
L
C
4
X
3
0
7
207
X
2
0
7
L
C
5

/

L
T
1
2
)
X
3
0
8
208
X
2
0
8
L
C
6

/

L
T
2
2
)
X
3
0
9
209
X
2
0
9
L
T
3
2
)
X
3
1
0
210
X
2
1
0
P
U
1
6
X
3
1
1
211
X
2
1
1
C
U
C
X
3
1
2
212
X
2
1
2
C
U
C
X
3
1
3
213
X
2
1
3
P
U
1
6
X
1
4
D

X
1
4
C
214
X
1
4
B

X
1
4
A
T
U
X
3
1
4
215
X
2
1
4
D
S
M
X
3
4
X
1
5
D

X
1
5
C
216
X
1
5
B

X
1
5
A
A
D
M
X
3
1
6
218
X
2
1
6
O
T
S
U
_
2
M

/

P
S
D
X
3
1
5
217
X
2
1
5
O
T
R
U
3
6
o
r
o
r
X121 X122
X123 X125 X127 X129 X131 X133 X135 X137
X124 X126 X128 X130 X132 X134 X136
X138
Exchange conn.
LC slots
2Mbit/s 2Mbit/s 2Mbit/s
X120
X104 X106 X108 X110 X112 X114 X116
X103 X105 X107 X109 X111 X113 X115 X117 X141 X142 X101
X102
X143
X144
Slot desig-
nations
S101
T
38 A50010-A3-C800-5-7619
Connectors of the Power Supply (X141 and X142)
QD2 (X101 and X102) and Alarm Inputs (X121)
Notes to Tab. 3.3:
GND = operation ground
GND_S = shielded ground
For X101:
Slave1 from SUE-E
QD2S1 In a/b
QD2S1 OUT a/b
T-connections to Slave1 of the SUE-E
QD2T IN a/b
QD2T OUT a/b
DAT, CLK, NRST = not used in CMXC
For X121:
AIN1 to AIn8 = alarm inputs of the SUE-E
AM = negative operating voltage for alarm contacts
X141 Pin X142 Pin
1 1
-48V (MUP1) 2 -48V (MUP2) 2
+48V (GND) 3 +48V (GND) 3
Tab. 3.2 Assignment of Connectors X141 (left and ) X142 (right)
Pin X101
QD2-Slave
X102
QD2-Master
X121
Alarm inputs
1 GND_S GND_S GND_S
2 QD2S1 OUT a QD2M IN a AIN1
3 QD2T1 OUT a AIN3
4 QD2S1 IN a QD2M OUT a AIN5
5 QD2T1 IN a AIN7
6
7 DAT
8 GND GND GND
9 QD2S1 OUT b QD2M IN b AIN2
10 QD2T1 OUT b AIN4
11 QD2S1 IN b QD2M OUT b AIN6
12 QD2T1 IN b AIN8
13
14 NRST
15 CLK
Tab. 3.3 Terminal Assignment of Jacks X101, X102 and X121
A50010-A3-C800-5-7619 39
User Manual
UMN CMXC
For X102:
Master from SUE-E:
QD2M IN a/b
QDM OUT a/b
T3 Interface (X143 and X144)
Notes to Tab. 3.11:
For X143:
T3 OUT1 a/b = T3-output from CUC plug-in places
T3 OUT2 a/b = T3-output from CUD plug-in place (202)
For X144:
T3 IN1 a/b = T3in1-input to CUD-, LT-/LU-, and CUC plug-in places
T3 OUT1 a/b = T3in1-output to the terminal panel
T3 IN2 a/b = T3in2-input to the ADM plug-in place
T3 OUT2 a/b = T3in2-output to the terminal panel
ZA Contacts (X122) and ECC of the CUC (X131)
Pin X143
Connector T3ab
X144
Connector
T3an
1 GND_S GND_S
2 T3 OUT1 a T3 IN1 a
3 T3 OUT1 a
4 T3 OUT2 a T3 IN2 a
5 T3 OUT2 a
6 T3 OUT1 b T3 IN1 b
7 T3 OUT1 b
8 T3 OUT2 b T3 IN2 b
9 T3 OUT2 b
Tab. 3.4 Terminal Assignment of 9-Contact Jacks X143 and X144
Pin X122
ZA-contacts
X131
ECC of the CUC
(in addition to CUD)
1 GND_S GND_S
2 EAN_A1
3 ZAA2 EAB_A1
4 ZAA3 ET_A1
5 ZAA4 EAN_A2
6 ZAA5 EAB_A2
Tab. 3.5 Terminal Assignment of Jacks X122 and X131
40 A50010-A3-C800-5-7619
Notes to Tab. 3.11:
For X122:
Index 1 = SUE-E
Index 2 = CU plug-in place (202), not used in CMXC
Index 3...5 = LT plug-in places (207 to 209), not used in CMXC
Index 6, 7 = CUC, plug-in places 211 and 212
Index 8 = PSD plug-in place 218, not used in CMXC
Index 9 = OTSU2M, plug-in place 218, not used in CMXC
(optional equipping)
For X131:
ECC1 to ECC4 of the CUC from both units (connect in parallel)
ECC1 and ECC2 with clock
ECC3 and ECC4 without clock
7 ZAA6 ET_A2
8 ZAA7 EAN_A3
9 ZAA8 EAB_A3
10 ZAA9 EAN_A4
11 EAB_A4
12 EANCUD_A
13 GND EABCUD_A
14 ZAB1 EAN_B1
15 ZAB2 EAB_B1
16 ZAB3 ET_B1
17 ZAB4 EAN_B2
18 ZAB5 EAB_B2
19 ZAB6 ET_B2
20 ZAB7 EAN_B3
21 ZAB8 EAB_B3
22 ZAB9 EAN_B4
23 EAB_B4
24 EANCUD_B
25 GND EABCUD_B
Pin X122
ZA-contacts
X131
ECC of the CUC
(in addition to CUD)
Tab. 3.5 Terminal Assignment of Jacks X122 and X131
A50010-A3-C800-5-7619 41
User Manual
UMN CMXC
Interfaces 2 Mbit/s G.703 (X109 to X110, X129 to X130, X113 to X117 and X133 to
X137)
Notes to Tab. 3.6:
For X109, X129, X110 and X130:
E1 OUTy a = a-wire,
E1 OUTy b = b-wire from output 2Mbit/s G.703 from Port y (PU16/1)
E1 INy a = a-wire,
E1 INy b = b-wire from input 2Mbit/s G.703 from Port y (PU16/1)
E1 = 2Mbit/s G.703
Example:
E1 OUT1 a = a-wire,
Interfaces 2 Mbit/s G.703
Pin X109/X113 X129/X133 X110/X114 X130/X134
1 GND_S GND_S GND_S GND_S
2 E1 OUT1 a E1 OUT5 a E1 OUT9 a E1 OUT13 a
3 E1 IN1 a E1 IN5 a E1 IN9 a E1 IN13 a
10
11
12
13
14 E1 OUT1 b E1 OUT5 b E1 OUT9 b E1 OUT13 b
15 E1 IN1 b E1 IN5 b E1 IN9 b E1 IN13 b
22
23
24
25
Tab. 3.6 Terminal Assignment of Jacks X109, X110, X 113, X114, X129, X130,
X133, X134 and X115
42 A50010-A3-C800-5-7619
E1 OUT1 b = b-wire from output 2Mbit/s G.703 from Port 1 (PU16/1)
E1 IN1 a = a-wire,
E1 IN1 b = b-wire from input 2Mbit/s G.703 from Port 1 (PU16/1)
E1 = 2Mbit/s G.703
The external names E1 IN.. E1 OUT.. are relate to the PU16.
The internal Interfaces from X109 are port 1 to 4 of the PU16/1 in Slot 210.
The Interfaces from X129 are port 5 to 8 of the PU16/1 in Slot 210 and are internal con-
nected to the first interface of the CUD place and of the 3 LT plug-in places.
The interfaces from X110 come from the ADM and are internal connected with port 9 to
12 of the PU16/1 in Slot 210.
The interfaces from X130 come from the ADM and are internal connected with port 13
to 16 of the PU16/1 in Slot 210.
For X113, X133, X114 and X134:
E1 OUTy a = a-wire,
E1 OUTy b = b-wire from output 2Mbit/s G.703 from Port y (PU16/2)
E1 INy a = a-wire,
E1 INy b = b-wire from input 2Mbit/s G.703 from Port y (PU16/2)
E1 = 2Mbit/s G.703
Example:
E1 OUT1 a = a-wire,
E1 OUT1 b = b-wire from output 2Mbit/s G.703 from Port 1 (PU16/2)
E1 IN1 a = a-wire,
E1 IN1 b = b-wire from input 2Mbit/s G.703 from Port 1 (PU16/2)
E1 = 2Mbit/s G.703
The external names E1 IN.. E1 OUT.. are relate to the PU16.
The interfaces from X113 are Port 1 to 4 of the PU16/2 in Slot 213.
The interfaces from X133 are Port 5 to 8 of the PU16/2 in Slot 213 and are internal con-
nected to the second interface of the CUD place and of the 3 LT plug-in places.
The interfaces from X114 come from the ADM and are internal connected with port 9 to
12 of the PU16/2 in Slot 213.
The interfaces from X134 come from the ADM and are internal connected with port 13
to 16 of the PU16/2 in Slot 213.
A50010-A3-C800-5-7619 43
User Manual
UMN CMXC
3.2.5 Technical Data
EMC
Climate
Power Supply
Compliance with the following standards ETS 300 386-1, 12/1994
EN 300 386-2, 12/1997
EMC Specif. 1TR9, 09/1999
In operation
SNUS, standalone . . . . . . . . . . . . . . . . . . . . . . . . . .
SNU, ONU indoor. . . . . . . . . . . . . . . . . . . . . . . . . . .
in acc. with ETS 300 019-1-3
environmental class 3.1
+5 C to +40 C
in acc. with ETS 300 019-1-3
environmental class 3.1E
5 C to +45 C
during transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . in acc. with ETS 300 019-1-2
storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . in acc. with ETS 300 019-1-1
Input voltage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 V to 72 V
Power consumption of the unit . . . . . . . . . . . . . . . . . . . . 8 W
44 A50010-A3-C800-5-7619
3.3 Central Unit CUC
3.3.1 Overview
The central unit CUC makes it possible to switch 1536 64-kbit/s time slots, i.e. 32 E1
signals, without blocking. Referred to the usable time slots, these are 1488 time slots
without CAS processing or 744 bidirectional 64-kbit/s connections and 1440 time slots
with CAS or 720 bidirectional 64-kbit/s connections.
Both the basic channels and the identifications are crossconnected.
The central unit works together with two interface units PU16 which combined supply
16 2-Mbit/s signals as 4 PCI links.
Fig. 3.7 CUC Block Diagram
The CUC allows conference calls for analog and digital signals as well as corresponding
identification processing (CAS conference). The total number of subscribers for confer-
ence operation is 30. These can be a maximum of 10 analog and/or 10 digital confer-
ences with 3 subscribers each and a maximum of 10 analog or 30 digital subscribers for
each conference.
The CUC performs the following functions:
Crossconnecting the 64-kbit/s signals in the switching matrix and administering the
database needed for this
Switching analog, digital and CAS conferences and administering associated data
Clock generation by selecting the guide clock
Exchanging configuration and program information between CUC and PU16 via su-
pervision bus SVB
LSI1 to LSI7
Frame clock
System clock
SVB
STSB
T3in
CC, CCR (unsym.)
PUP
MUP
SISA-ADR (0 to 4)
CCUR (unsym.)
5
14
+5 V
+3.3 V
T3out
GND
G.703/10
ON
EXTERNAL
SYSTEM
INTERNAL
SERVICE
PCI8 (RS422)
PCI1 (RS422)
4
4
Computer
EEPROM
RAM
HDLC
controller
QD2-S
HDLC
controller
(RS485)
ECC
Subbit rate
matrix
4 x ECC
2 x CLK64
CCUR
Conference
Clock
generation
Operating
mode
CMXC
mapping
call
(V.11)
(V.11)
(RS485)
Alarm
contacts
ADR
5
(0 to 4)
Switching
matrix
VCXO
25.92 MHz
A50010-A3-C800-5-7619 45
User Manual
UMN CMXC
Data exchange between the CUC and PU16 units via PCI links
Standby control
Alarm signaling via ZA(A) and ZA(B) contacts and LEDs
Providing the time.
The CUC has the following interfaces:
Data
8 x PCIs as system-internal interfaces to transmit PCM signals between the CUC
and the peripheral units PU16
Clock pulses
7 x LSI interfaces to receive the 2-MHz guide clock from PU16
LSI_FR interface to receive a selected frame clock from units PU16
T3in interface for synchronizing by an external clock pulse
T3out interface for synchronizing downstream equipment
CLK64: Sending 2 64-kHz clock pulses to synchronize ECC channels
Interfaces CC and CCR for phase-correct synchronizing of the standby unit by the
active CUC
Supervision
QD2 slave interface to transmit SISA information (HDLC protocol)
SVB interface to communicate between the CUC and PU16 units (HDLC protocol)
STSB interface between the active and standby unit for data alignment
4 ECC interfaces for the remote supervision of remote equipment (V.11)
2 synchronous each with 64 kbit/s, 2 asynchronous each with 9.6 kbit/s and
oversampling
Debug interface for commissioning and software development
Rear panel connections to read-in the QD2 unit address and slot address which
can be set
Internal CCUR interface to signal active/standby operation (unsymmetrical, TTL)
External CCUR interface to signal active/standby operation for external equip-
ment (symmetrical, RS485)
Outputs for the alarm contacts ZA(A) and ZA(B)
2 visible and 5 covered LEDs to indicate the operating mode.
Power supply with 48 V.
46 A50010-A3-C800-5-7619
3.3.2 Supervision and Alarm Signaling
5 SMD-LEDs are located on the front panel of the unit which can only be seen when the
front panel of the shelf is removed. They show the operating mode of the CUC.
Two LEDs (can be seen without removing the front panel of the shelf) indicate the oper-
ating mode of System Module CMXC. The causes for the alarm indication can be diag-
nosed with reference to the alarm table (see Tab. 3.10 or Tab. 3.11).
The following priorities exists when alarms are signaled:
A alarm (highest priority)
B alarm
S alarm.
In the case of faults, the standby unit does not indicate an A, B or S alarm, but only its
own unit errors.
The CUC unit has an alarm table for each of its operating statuses (active or standby).
LED Color Mode Meaning
ON green on Unit in order, active operating mode
flashes Unit in order, standby mode or QD2 bus active
off No power supply or failure of the unit
EXTERNAL red on Alarm mode of external interfaces,
e.g. failure of the guide clock, failure of the ECC channel
SYSTEM red on Alarm mode of system-internal interfaces, e.g. parity error or
loss signal on the PCI links
INTERNAL red on Unit error, e.g. self-test error
flashes Unit was not yet loaded with software after power-up
SERVICE yellow on QD2 bus active
Tab. 3.7 CUC Signaling the active Operating Mode
Operating mode CMXII LED red LED green
Interference-free operation off on
A alarm on off
B alarm flashes on
S alarm on on
Tab. 3.8 CMXC Indication of the Operating Mode
Operating mode of standby CUC LED red LED green
Interference-free operation off flashes
Unit faulty flashes flashes
Tab. 3.9 CUC Indication of the standby Operating Mode
A50010-A3-C800-5-7619 47
User Manual
UMN CMXC
Criterion Alarm AIS Free r. Change OS LED
A S B PCI
D (n)
PCM
U (n)
SUB
U (n)
CAS
U (n)
CAS
D (n)
Dout
(n)
Dk
(n)
PLL
9)
Sync
Src
Trunk Stand-
by
PCI LOPU (n)
4)

10)
Syst
passive
Sync
Src
LOESI
5)
6)
6)
7)

6)
14)

6)
Ext
LOLSI(n)
5)
6)
6)
7)

6)
14)

6)
Syst
LOCC
3)

LOCCR
3)

E1
(CAS)
AISk(n)
8)

13)
SYNk(n)
8)

13)
Dk-Bit(n)
13)
Nk-Bit(n)
13)
ECC
port
Dan
1)
Ext
passive
QD2
bus
LOQD2 Serv
11)
Supv
bus
LOSVB Syst
LOSTSB
2)
Syst
Unit A(n)
S(n)
B(n)
Tab. 3.10 CUC Alarm Table (Active)
48 A50010-A3-C800-5-7619
Internal LOFTSI_1 Int
LOFTSI_2 Z
15)
Int
FWE Int
Startup Z Z Int
12)
STE Z Z Int
12)
) The measure is being implemented (as soon as possible)
1) The alarm monitor can be configured at Din (ECC port). The basic setting is switched on.
2) The alarm criterion only applies if the partner unit is available. The partner unit is considered available if no LOCC and no LOCCR alarm
are being signaled. If the unit is in standby mode then the partner unit must be available (received CCUR signal is active)
3) The alarm criterion does not trigger an alarm on the active unit.
4) This criterion is only evaluated for active PCI links, PCI links are active, for which a PU16 is inserted.
5) Only clock sources are monitored which have been registered in the clock priority list.
6) Is executed if the clock source is active and no guide clocks of lower priority are available.
7) Is executed if the clock source is not active or there are more guide clocks of a lower priority available.
8) AIS is injected into the shared signaling channels.
9) If the PLL is idle, the T3out driver becomes passive.
10) Switching is only executed on an alternative route if an alternative route has been configured for the connection which is affected by the
failure of the PCI signal.
11) The service LED goes out if there is no connection to the master TMN system via the QD2 interface.
12) The On LED goes out at the same time.
13) The TMN alarm is signaled via the PU16 unit.
14) Is executed if the clock source is active and there are more guide clocks of lower priority are available.
15) This action is used to insert a 1 into the shared sub time slots.
Z) High-impedance output (tri state)
A S B PCI
D (n)
PCM
U (n)
SUB
U (n)
CAS
U (n)
CAS
D (n)
Dout
(n)
Dk
(n)
PLL
9)
Sync
Src
Trunk Stand-
by
Tab. 3.10 CUC Alarm Table (Active) (Cont.)
A50010-A3-C800-5-7619 49
User Manual
UMN CMXC
A S B PCI
D (n)
PCM
U (n)
SUB
U (n)
CAS
U (n)
CAS
D (n)
Dout
(n)
Dk
(n)
PLL
9)
Sync
Src
Trunk Stand-
by
PCI LOPU (n)
4)
Syst
passive
Sync
Src
LOESI
5)

7)
Ext
LOLSI(n)
5)

LOCC
LOCCR
E1
(CAS)
AISk (n)
8)

13)
SYNk (n)
8)

13)
Dk-Bit (n)
13)
Nk-Bit (n)
13)
ECC
port
Din
1)
Ext
passive
QD2
bus
LOQD2
Supv
bus
LOSVB
LOSTSB
2)
Syst
Unit A(n)
S(n)
B(n)
Tab. 3.11 CUC Alarm Table (Standby)
50 A50010-A3-C800-5-7619
Intern LOFTSI_1 Int
LOFTSI_2 Z
15)
Int
FWE Int
Startup Z Z Int
12)
STE Z Z Int
12)
) The measure is being implemented (as soon as possible)
1) The alarm monitor can be configured at Din (ECC port). The basic setting is switched on.
2) The alarm criterion only applies if the partner unit is available. The partner unit is considered available if no LOCC and no LOCCR alarm
are being signaled. If the unit is in standby mode then the partner unit must be available (received CCUR signal is active)
3) The alarm criterion does not trigger an alarm on the active unit.
4) This criterion is only evaluated for active PCI links. PCI links are active, for which a PU16 is inserted.
5) Only clock sources are monitored which have been registered in the clock priority list.
6) Is executed if the clock source is active and no guide clocks of lower priority are available.
7) Is executed if the clock source is not active or there are more guide clocks of a lower priority available.
8) AIS is injected into the shared signaling channels.
9) If the PLL is idle, the T3out driver becomes passive.
10) Switching is only executed on an alternative route if an alternative route has been configured for the connection which is affected by the
failure of the PCI signal.
11) The service LED goes out if there is no connection to the master TMN system via the QD2 interface.
12) The On LED goes out at the same time.
13) The TMN alarm is signaled via the PU16 unit.
14) Is executed if the clock source is active and there are more guide clocks of lower priority are available.
15) This action is used to insert a 1 into the shared sub time slots.
Z) High-impedance output (tri state)
A S B PCI
D (n)
PCM
U (n)
SUB
U (n)
CAS
U (n)
CAS
D (n)
Dout
(n)
Dk
(n)
PLL
9)
Sync
Src
Trunk Stand-
by
Tab. 3.11 CUC Alarm Table (Standby) (Cont.)
Alarm criteria
LOPU(n) Loss of PCI upstream, PCI link n
PCI signals fail at the PCI receiving port of the PCIC, detected by:
- Parity error rate
- Loss of frame synchronization
LOESI Loss of external synchronization input
Loss of T3in (background clock monitor in the PCIC).
LOLSI(n) Loss of line synchronization input
Loss of the guide clock from the E1 port (background clock monitor in the
PCIC).
LOCC Loss of cross coupling
Loss of the guide clock of the standby module (background clock monitor
in the PCIC),
Alarm criterion triggers an alarm on the standby module.
LOCCR Loss of Cross Coupling PCI frame
Loss of PCI frame guide clock in the standby module (background clock
monitor in the PCOC),
Alarm criterion triggers an alarm on the standby module.
A50010-A3-C800-5-7619 51
User Manual
UMN CMXC
AISK Received AIS signal in the multiframe
The incoming signals are controlled at the interfaces if they contain the AIS
signal. Evaluation is carried out according to G.796.
SYNk Detects a failure of the multiframe synchronization at E1.
Dk bit Bit 6 of time slot 16 (bits 1 to 8) in frame 0 of the received E1 signal
D bit = "L" normal status
D bit = "H" display of the distant end (the multiframe signal in the
preceding equipment fails)
Nk bit Bit 7 of time slot 16 (bits 1 to 8) in frame 0 of the received E1 signal
Nk bit = "H" bit is not being used
Nk bit = "L" display
Din Signal failure at ECC port (Din)
LOQD2 Signal failure on QD2
LOSVB Signal failure on SVB
LOSTSB Signal failure on STSB
A(n) Urgent alarm of module n
S(n) Service alarm of module n
B(n) Non-urgent alarm of module n
LOFTSI_1 Failure or faulty frame synchronization impulse at the IC TTSI2K32_1 cross
connect
LOFTSI_2 Failure or faulty frame synchronization impulse at the IC TTSI2K32_2 sub
rate cross connect
FWE Flash write error
STE Self test error
Start-up Startup phase of the module
Responses
A alarm Urgent unit alarm, service is not available. Initiate immediate ac-
tion to rectify the fault. If the A alarm is configured as a switch
criterion for the AZ contact, this is activated immediately until the
A alarm disappears.
B alarm Non-urgent unit alarm, service is impaired.
Initiate maintenance action.
Immediate activation of the BZ contact until the B alarm disap-
pears.
S alarm Service unit alarm, service is not available.
Initiate maintenance action. Fault must be rectified at another lo-
cation if possible. If the S alarm is configured as a switch criteri-
on for the AZ contact, this is activated immediately before the S
AIS Send continuous H signal.
Z Tri state switching of the interface transmitter
Dk bit Send bit 6 (Dk bit) of the multiframe in the E1 signal.
AIS PCID Use AIS in the relevant time slots of the PCI downstream links
AIS PCMU Use AIS in the relevant time slots of the PCI upstream links
AIS SUBU Use AIS in the subrate upstream links
AIS CASU Use AIS in the shared signals
AIS CASD Use AIS in the signals of the CAS downstream links
AIS Dout Send AIS at the ECC port affected
Idle PLL Switch PLL for 8.192 MHz system clock in idle circuit
52 A50010-A3-C800-5-7619
The positions of the connectors and the LEDs are shown in Fig. 3.8.
Fig. 3.8 CUC Operating Elements
Fig. 3.9 Position of the Jumpers on the Pin Strips X401
Change sync source Change active synchronization clock source
Change trunk Switch to the alternative route
TMN alarm Display alarm via the TMN system
PNA Protection not available (switch to standby CUC blocked)
LED The specified SMD LED of the unit switches on.
10
11
Amber1)
Red1)
Red1)
Red1)
Green1)
10 Internal connector
11 External connector
1) Only visible if front panel is removed
Red
Green
X401
2 1
Pin strips X401 to configure the terminating resistors of the T3 interfaces at 75 /120 or high
impedance
120 /75 high impedance
1 2
1 2
A50010-A3-C800-5-7619 53
User Manual
UMN CMXC
Assignment of the Connectors
Pin A row B row C row
1 GND GND GND (A0)...(A4) = 12 slot address of backplane
(ADR0)...(ADR4) = 13 is QD2 address.
of backplane (for both CUC = 13)
P5V (Pin C9) = 5V output with
low power for terminating resistor on the
backplane
CC_T / CC_R = Clock synchronization
CCR_T / CCR_R = Frame
and multiframe synchronization
SVB:
(I) = CUC input
(O) = CUC output
CCUR_T = H ----> PCI active
(unsymm. switching signal from CUC/1,
i.e. CUC/2 in standby)
2 (ADR0) GND (A0) PUP
3 GND (ADR1) GND (A1)
4 (ADR2) (A2) MUP2
5 (ADR3) (A3)
6 GND (ADR4) GND (A4) CCUR_ (O)
7 GND GND CCUR_ (I)
8 GND_S GND_S GND_S
9 LED_R LED_G P5V
10 GND GND GND
11 LSI1_P LSI1_N T3AN-A1
12 GND GND T3AN_B1
13 LSI2_P LSI2_N
14 GND GND T3AB_A1
15 LSI3_P LSI3_N T3AB_B1
16 GND GND GND
17 LSI4_P LSI4_N
18 GND GND STSB (O)
19 LSI5_P LSI5_N STSB (O)
20 GND GND GND
21 LSI6_P LSI6_N STSB (I)
22 GND GND STSB (I)
23 LSI7_P LSI7_N PM
24 GND GND GND
25 LSIFR_P LSIFR_N PE
26 GND GND GND
27 SVB_D_P (O) TXD RXD
28 SVB_D_N (O) CC (O)
29 GND GND CCR (O)
30 SVB_U_P (I) CCR (I)
31 SVB_U_N (I) REF_FR CC (I)
32 GND GND GND
Tab. 3.12 CUC Connector (bottom)
54 A50010-A3-C800-5-7619
1 GND GND ZAA6 (7) Table applies to X211
The following apply to X212:
PCIS_ instead of PCI_ and CCURS_
instead of CCUR_
and also ZAA7 and ZAB7
EAN_A/B1, EAB_A/B1, ET_A/B1 =
ECC interface 1with clock signal
(likewise interface 2)
EAN_A/B3, EAB_A/B3 =
ECC interface 3 without
carried clock signal
(likewise interface 4)
Explanations on the PCI signals:
(likewise signal PCIS_... for X212)
..._D_... = Downstream
..._U_... = Upstream
..._P... = Positive
..._N... = Negative
(I) = CUC input
(O) = CUC output
CCUR_A/B = symm. switching signal
for external interfaces
2 GND_S GND_S ZAB6 (7)
3 PCI_D_P9 (O) PCI_D_N9 (O) PCI_D_P11 (O)
4 PCI_U_P9 (I) GND PCI_D_N11 (O)
5 PCI_U_N9 (I) PCI_U_P11 (I) PCI_U_N11 (I)
7 PCI_U_P10 (I) GND PCI_D_N12 (O)
9 GND CCUR_B CCUR_A
10 EAN_A1 EAN_B1 EAN_A3
11 EAB_A1 EAB_B1 EAN_B3
12 ET_A1 ET_B1 EAB_A3
13 EAN_A2 EAN_B2 EAB_B3
14 EAB_A2 EAB_B2 EAN_A4
15 ET_A2 ET_B2 EAN_B4
16 QD2SAB_B (O) QD2SAB_A (O) EAB_A4
17 QD2SAN_B (I) QD2SAN_A (I) EAB_B4
18 GND GND GND
19 PCI_D_P1 (O) PCI_D_P5 (O) PCI_D_N5 (O)
20 PCI_D_N1 (O) GND PCI_U_P5 (I)
21 PCI_U_P1 (I) PCI_U_N1 (I) PCI_U_N5 (I)
22 GND GND GND
23 PCI_D_P2 (O) PCI_D_P6 (O) PCI_D_N6 (O)
24 PCI_D_N2 (O) PCI_U_P6 (I) PCI_U_N6 (I)
25 PCI_U_P2 (I) PCI_D_P7 (O) PCI_D_N7 (O)
27 GND GND GND
29 PCI_U_P3 (I) PCI_U_N3 (I) PCI_D_N8 (O)
30 PCI_D_P4 (O) PCI_D_N4 (O) PCI_U_P8 (I)
31 PCI_U_P4 (I) PCI_U_N4 (I) PCI_U_N8 (I)
32 GND GND GND
Tab. 3.13 CUC Connector (top)
A50010-A3-C800-5-7619 55
User Manual
UMN CMXC
T3 Interface
PCI Interface
QD2 Slave Interface
Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2048 kHz (1 50 ppm)
T3in
Impedance, high-impedance . . . . . . . . . . . . . . . . . . . . . 1.6 k II < 120 pF
Input voltage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0.5 V
0S
to 1.9 V
0S
Cable attenuation at 2048 kHz. . . . . . . . . . . . . . . . . . . . 6 dB
Reflection attenuation at 2048 kHz . . . . . . . . . . . . . . . . 15 dB
T3out
Impedance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 , symmetrical or
75 , unsymmetrical
Level
120 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
75 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.0 V
0S
to 1.9 V
0S
0.75 V
0S
to 1.5 V
0S
Inherent jitter (at 20 Hz to 100 kHz) . . . . . . . . . . . . . . . . 0.05 UIpp
Bit rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.96 Mbit/s
Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NRZ
Frame duration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 s
Frame length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1620 bit
Level for symmetrical digital interfaces . . . . . . . . . . . . . according to EIA RS422
Maximum difference voltage at input . . . . . . . . . . . . . . . 250 mV
Equal level at input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0.5 V to (Vcc - 0.5 V)
Difference voltage at output . . . . . . . . . . . . . . . . . . . . . . 2 V
Equal level at output. . . . . . . . . . . . . . . . . . . . . . . . . . . . 0.4 V to 2.5 V
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . serial bus system according
to EIA RS 485
Bus user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 master and
up to 30 slaves
Transmission lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . symmetrical, 4-wire
Impedance bus termination . . . . . . . . . . . . . . . . . . . . . . high-impedance
Bit rate (automatic identification) . . . . . . . . . . . . . . . . . . 1.2 kbit/s, 9.6 kbit/s
or 64 kbit/s
Transmission mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . plesiochronous
Line code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NRZI
permissible line length . . . . . . . . . . . . . . . . . . . . . . . . . . 500 m
Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Initiator of the data connection. . . . . . . . . . . . . . . . .
Addresses of secondaries . . . . . . . . . . . . . . . . . . . .
HDLC (NRM, polling)
primary
1 to 30
Address setting, via rear panel . . . . . . . . . . . . . . . . . . . . 5 bit
56 A50010-A3-C800-5-7619
ECC Interface
Alarm Contacts
CCUR Interface
Power Supply
Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . according to ITU-T V.11
Bit rate
asynchronous operation . . . . . . . . . . . . . . . . . . . . .
synchronous operation with clock CLK64 . . . . . . . .
9.6 kbit/s
64 kbit/s
Permissible external voltage, surge pulse 1.2/50 s . . . 500 V
Max. permissible load current . . . . . . . . . . . . . . . . . . . . 2 A
The driver connection is designed short-circuit proof.
Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . according to EIA RS485,
symmetrical
Signaling the active CUC unit . . . . . . . . . . . . . . . . . . . . H level
Input voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 V to 72 V
Power consumption of the unit . . . . . . . . . . . . . . . . . . . 8 W
A50010-A3-C800-5-7619 57
User Manual
UMN CMXC
3.4 Interface Unit PU16
3.4.1 Overview
Interface unit PU16 receives 16 plesiochronous, HDB3-coded, 2-Mbit/s signals (E1in),
synchronizes all the data streams, converts the data into PCI signals and sends four PCI
upstreams to the CUC.
Unit PU16 receives four PCI downstreams from the CUC in the reverse direction, gen-
erates the appropriate frames and converts them into 16 x 2 Mbit/s (E1out).
One central CUC can process the data streams of two PU16s.
Fig. 3.10 PU16 Block Diagram
PU16 performs the following functions:
Connecting 16 E1 interfaces (2-Mbit/s ports)
Frame and multiframe synchronization of the received signal
Establishing the supervision and alarm signaling function for 16 2-Mbit/s interfaces
Transmitting the guide clock to the CUC via the LSI interface
selecting 7 from 16 clock sources controlled by the CUC,
transmitting frame synchronous information for the selected clock source
Multiplexing 16 2-Mbit/s data streams in four PCI links and symmetrical transmis-
sion of the PCI signals to the CUC
Providing four PCIS interfaces for redundant signal transmission
Signaling PCI transmission via the CCUR/CCURS interface between the active CUC
and the standby CUC and PU16 (via an unsymmetrical line)
Communication between the CUC and the PU16 via SVB in the master slave mode
Providing the time
Synchron. 2-Mbit/s
interface
E1in(16)
E1out(16)
PCI
interface
LSI1
LSI7
ADR
5
(0 to 4)
SVB
G.703/6
CCUR
ON
EXTERNAL
SYSTEM
INTERNAL
SERVICE
4
4
HDLC
controller Computer
EEPROM
RAM
PCI1
PCIS4
E1in(1)
E1out(1)
Synchron. 2-Mbit/s
interface
4
PCI4
4
PCIS1
PUP
MUP
+5 V
+3.3 V
GND
CCURS
1
16
1
16
58 A50010-A3-C800-5-7619
Storing the initial program loader, the configuration, crash data, error manager data
and the type label data (writable part): Storage area of flash EEPROM 512 kBytes
Storing the fixed type label data in the serial EEPROM (size 256 bytes).
Unit PU16 has the following interfaces:
Data
16 E1 interfaces (according to G.703/6) to connect 16 x 2-Mbit/s ports
8 PCI interfaces (four active and four standby) as system-internal interfaces to
transmit the PCM payload to the active and standby CUC units
Clock pulses: 7 x LSI interfaces to transmit the guide clock to the CUC
Supervision
SVB interface to communicate between the CUC and PU16 units
Rear panel contacts for slot identification
Debug interface for commissioning and software development
Control signals CCUR and CCURS to select the PCI bus switched to active or
standby
Power supply with 48 V.
3.4.2 Supervision and Alarm Signaling
The PU16 mode can be diagnosed with reference to alarm messages, see alarm table.
5 SMD-LEDs are located on the front panel of the unit which can only be seen when the
front panel of the shelf is removed. They show the operating mode of the PU16.
Checking the transmission quality at E1in
PCM signals received at the E1 ports are analyzed continuously according to ITU-T
G.821 and the values determined are stored in quality data records. Both the current
quality counter and any stored record can be displayed.
In addition, the frame slips are counted in a counter. The counter can be requested via
the user interface.
LED Color Mode Meaning
ON green on Unit in order
flashes SW download
off No power supply or failure of the unit
EXTERNAL red on Alarm mode of E1 interfaces
SYSTEM red on Alarm mode of system-internal interfaces (PCI link, SVB)
INTERNAL red on Unit error, power supply error
flashes Unit was not yet loaded with software after power-up
SERVICE yel-
low
on Active service mode on the unit
(SW download, loop switched)
Tab. 3.14 PU16 Signaling the Operating Mode
A50010-A3-C800-5-7619 59
User Manual
UMN CMXC
Loop connections
Loop connections can be established for maintenance work which locate the fault in
case of malfunctioning. The loops can be controlled individually for each 2-Mbit/s port.
The following loops can be connected:
Local loop (LL)
The signal at the send port of the 2-Mbit/s interface is connected to the receive port.
The AIS signal is sent in the E1out direction. In this way, faults can be located within
the CMXC system module.
Remote loop (RL)
The signal at the receive port of the 2-Mbit/s interface is connected to the send port.
In the PCI upstream direction, AIS is put into the corresponding time slots instead of
the useful load. In this way, malfunctioning of the external connecting lines can be
located.
Fig. 3.11 Local Loop and Remote Loop Test Loops
The loop connection is released and split by SISA commands via the LCT or the OS.
The loop mode is not stored in the EEPROM. The current loop mode can be displayed
via SISA requests. Moreover, the SERVICE-LED indicates an activated loop connection
on the unit. The resulting reactions for activated test loops are specified in the alarm ta-
ble.
The follow-up actions for activated test loops are given in the alarm table.
LL RL
E1out
E1in
PCI
downstream
PCI
upstream
2-Mbit/s
interface
PCI
interface
60 A50010-A3-C800-5-7619
Criterion Action
Alarm E1out E1out
(CAS)
PCIup
A S B D
bit
AIS HighZ Dk-
bit
7)
AISk
7)
AIS HighZ Change
sync
source
Change
trunk
5)
TMN
alarm
LED
E1in
(unframed)
LOS
3)

4)
EXTERNAL
AIS
3)

4)
EXTERNAL
E1in/
(framed)
LOS
3)

4)
EXTERNAL
AIS
3)

4)
EXTERNAL
SYN
3)

4)
EXTERNAL
BER-3
3)

4)
EXTERNAL
BER-5/6
1)

9)

6)
EXTERNAL
D-Bit EXTERNAL
N-Bit
8)
EXTERNAL
AISk
2)
EXTERNAL
SYNk
2)
EXTERNAL
Dk-Bit
2)
EXTERNAL
Nk-Bit
2)8)
EXTERNAL
TSB
10)

4)11)

E1 passive
3)

tristate
3)

The action is to be implemented (as soon as possible).
1) The basic setting for the alarm criterion (if delivered) is BER-6.
2) The alarm evaluation is only executed for the E1 ports for which CAS signaling has been configured.
3) The AIS PCIup action only applies to time slots of the PCI links which are relevant to the corresponding E1 port.
4) The switching action is carried out on another clock source if the current clock synchronization is carried out by the clock source that
has just failed. If the internal oscillator clock source is activated, then the T3out signal is also blocked.
5) The alarm is triggered for connections in the cross connect for which an alternative route has been configured.
6) The alarm action is configurable.
7) The alarm is triggered by the CUC module.
8) The alarm criterion is configurable.
9) The alarm action is configurable. BER-5/6 leads to the B alarm.
10) The QD2 configures the clock control bit. An Sa bit (Sa bits 4 to 8) can be configured for each E1 port as a clock control bit. Regardless
of whether the Sa bit is low or high active, it is configured by QD2.
11) The clock source is only configured if the clock control bit is received for the E1 port and is used as an active clock source and
configuration of the clock control bit is carried out by QD2.
12) The alarm action only applies to the E1 ports which are assigned to the PCI receiver that signals the fault.
13) The alarm action only applies to the E1 or PCI ports which are assigned to the PCIPG that signals the fault.
14) Action AIS to E1out applies to all 16 E1 ports.
15) Alarm actions only apply to versions without V5.x signaling.
Tab. 3.15 PU16 Alarm Table
A50010-A3-C800-5-7619 61
User Manual
UMN CMXC
PCI down LOF(n)
12)
SYSTEM
PER(n)
12)
SYSTEM
BOVD(n)
13)
INTERNAL
Internal BOVU(n)
13)
INTERNAL
LOC25(n) INTERNAL
LOC8(n)
14)
INTERNAL
LOSVB SYSTEM
LOFTSI
15)
INTERNAL
STE INTERNAL
Start-Up - INTERNAL
Service LL
4)
SERVICE
RL
3)
SERVICE
Criterion Action
Alarm E1out E1out
(CAS)
PCIup
A S B D
bit
AIS HighZ Dk-
bit
7)
AISk
7)
AIS HighZ Change
sync
source
Change
trunk
5)
TMN
alarm
LED
The action is to be implemented (as soon as possible).
1) The basic setting for the alarm criterion (if delivered) is BER-6.
2) The alarm evaluation is only executed for the E1 ports for which CAS signaling has been configured.
3) The AIS PCIup action only applies to time slots of the PCI links which are relevant to the corresponding E1 port.
4) The switching action is carried out on another clock source if the current clock synchronization is carried out by the clock source that
has just failed. If the internal oscillator clock source is activated, then the T3out signal is also blocked.
5) The alarm is triggered for connections in the cross connect for which an alternative route has been configured.
6) The alarm action is configurable.
7) The alarm is triggered by the CUC module.
8) The alarm criterion is configurable.
9) The alarm action is configurable. BER-5/6 leads to the B alarm.
10) The QD2 configures the clock control bit. An Sa bit (Sa bits 4 to 8) can be configured for each E1 port as a clock control bit. Regardless
of whether the Sa bit is low or high active, it is configured by QD2.
11) The clock source is only configured if the clock control bit is received for the E1 port and is used as an active clock source and
configuration of the clock control bit is carried out by QD2.
12) The alarm action only applies to the E1 ports which are assigned to the PCI receiver that signals the fault.
13) The alarm action only applies to the E1 or PCI ports which are assigned to the PCIPG that signals the fault.
14) Action AIS to E1out applies to all 16 E1 ports.
15) Alarm actions only apply to versions without V5.x signaling.
Tab. 3.15 PU16 Alarm Table (Cont.)
Alarm criterion
LOS Signal failure to E1 or Din
AIS Receive the AIS signal
AIS Receive the AIS signal
The incoming signals are controlled at the interfaces if they contain
the AIS signal.
62 A50010-A3-C800-5-7619
SYN Detects a failure of the frame synchronization for E1 (failure of the
PCM frame; its failure is displayed for selected CRC4 frames of the 2
Mbit/s signal)
BER-3 The error rate at E1 is greater than or equal to 10-3.
BER-5/6 The error rate of the received PCM signal at E1 is greater than or
equal to:
for active CRC4 frames : 10-6
for switched-off CRC4 frames : 10-5
D bit Bit 3 of the received service word in the E1 signal
D bit = "H" display (the received signal in the
N bit Sa4, bit 4 of the received service word in the E1 signal
N bit = "H" bit is not being used
N bit = "L" display
AISk Receive the AIS signal in the multiframe
The incoming signals are controlled at the interfaces if they contain
the AIS signal. Analysis is carried out according to G.796.
SYNk Detect a failure of the multiframe synchronization at E1.
Dk bit Bit 6 of time slot 16 (bits 1 to 8) in frame 0 of the received E1 signal
D bit = "H" display (the multiframe signal in the
Nk bit Bit 7 of time slot 16 (bits 1 to 8) in frame 0 of the received E1 signal
Nk bit = "H" bit is not being used
Nk bit = "L" display
TSB Receive the clock control bit
LOF Loss of frame synchronization in the PCI downstream
PER Parity error rate in the PCI downstream
BOVD Buffer overflow in the PCI downstream
BOVU Buffer overflow in the PCI upstream
LOC25 Failure of the VCXO in the PCI receiver (25.92 MHz)
LOC8 Failure of the user PLL (8.192 MHz)
LOFTSI Failure of or fault with the frame synchronization impulses at the TTSI
STE Self test error
Start-up Startup phase of the module
LL Local loop (close to loop at an E1 port)
RL Remote loop (remote loop at an E1 port)
Responses
A alarm Urgent unit alarm, service is not available.
Initiate immediate action to rectify the fault. If the A alarm is config-
ured as a switching criterion for the AZ contact, this is activated im-
mediately until the A alarm disappears.
B alarm Non-urgent unit alarm, service is impaired. Initiate service action.
Immediate activation of the BZ contact until the B alarm disappears.
S alarm Service unit alarm, service is not available.
Fault must be rectified at another location if possible. If the S alarm is
configured as a switching criterion for the AZ contact, this is activated
immediately until the S alarm disappears.
A50010-A3-C800-5-7619 63
User Manual
UMN CMXC
The operating elements and the positions of the connectors and the LEDs are shown in
Fig. 3.12.
Fig. 3.12 PU16 Operating Elements
Position of the jumpers on the pin strips:
The jumpers are to be used to configure the terminating resistors of the sixteen E1 in-
terfaces of 75 or 120 for the 6-pin strips. The jumpers must be inserted according
to the required input Impedance, see Fig. 3.13.
Dk bit Send bit 3 (D bit) of the service word in the E1 signal.
AIS Send continuous H signal.
High Z High sender Z switching of the E1 interface.
D bit Send bit 6 (Dk bit) of the multiframe in the E1 signal.
AISk Send continuous H signal in the multiframe.
AIS PCI up Use AIS in the relevant time slots of the PCI upstream links.
High Z PCI up High sender Z switching of the PCI interface.
Change sync Change the active synchronization clock source.
Source change
trunk
Switch to the alternative route.
TMN alarm Alarm display via the TMN system.
LED The specified SMD LED of the unit switches on.
10
11
Amber1)
Red1)
Red1)
Red1)
Green1)
1) Only visible if the front panel is removed Front pan-
Pin strips X101 to X104, X201 to X204, X301 to X304 and X401 to X404 to configure the
terminating resistors of the sixteen E1 interfaces at 75 or 120
X101
X104
...
X201
X204
...
X301
X304
...
X401
X404
...
64 A50010-A3-C800-5-7619
Fig. 3.13 Position of the Jumpers on the Pin Strips
1 GND GND GND
2 (A0) GND
3 GND (A1) MUP1
4 (A2) GND MUP2
5 (A3) CCUR (I) GND_S
6 GND (A4) CCUR (I) GND_S
7 GND GND GND
8 PU_AN PCI_D_P (I)
9 TYP PCI_D_N (I)
10 GND GND PCI_U_P (O)
11 LSI1_P LSI1_N PCI_U_N (O)
12 GND GND GND
13 LSI2_P LSI2_N PCI_D_P (I)
14 GND GND PCI_D_N (I)
15 LSI3_P LSI3_N PCI_U_P (O)
16 GND GND PCI_U_N (O)
17 LSI4_P LSI4_N
18 GND GND GND
19 LSI5_P LSI5_N PCIS_D_P (I)
20 GND GND PCIS_D_N (I)
21 LSI6_P LSI6_N PCIS_U_P (O)
22 GND GND PCIS_U_N (O)
23 LSI7_P LSI7_N PM
24 GND GND GND
25 LSIFR_P LSIFR_N PCIS_D_P (I)
26 GND GND PCIS_D_N (I)
27 SVB_D_P (I) RXD PCIS_U_P (O)
28 SVB_D_N (I) TXD PCIS_U_N (O)
Tab. 3.16 PU16 Connector (bottom)
120 75 Jumper settings for the following
6-pin strips:
X101 to X104
X201 to X204
X301 to X304
X401 to X404
A50010-A3-C800-5-7619 65
User Manual
UMN CMXC
29 GND GND
30 SVB_U_P (O) PE
31 SVB_U_N (O) REF_FR
32 GND GND
1 GND GND F1out_A9 (O)
2 F1out_B9 (O)
3 F1out_A1 (O) F1out_B1 (O) F1in_A9 (I)
4 F1in_A1 (I) F1in_B1 (I) F1in_B9 (I)
5 F1in_A2 (I) F1in_B2 (I) F1in_A10 (I)
6 F1out_A2 (O) F1out_B2 (O) F1in_B10 (I)
7 F1out_A3 (O) F1out_B3 (O) F1out_A10 (O)
8 F1in_A3 (I) F1in_B3 (I) F1out_B10 (O)
9 F1in_A4 (I) F1in_B4 (I) F1out_A11 (O)
10 F1out_A4 (O) F1out_B4 (O) F1out_B11 (O)
11 F1out_A5 (O) F1out_B5 (O) F1in_A11 (I)
12 F1in_A5 (I) F1in_B5 (I) F1in_B11 (I)
13 F1in_A6 (I) F1in_B6 (I) F1in_A12 (I)
14 F1out_A6 (O) F1out_B6 (O) F1in_B12 (I)
15 F1out_A7 (O) F1out_B7 (O) F1out_A12 (O)
16 F1in_A7 (I) F1in_B7 (I) F1out_B12 (O)
17 F1in_A8 (I) F1in_B8 (I) F1out_A13 (O)
18 F1out_A8 (O) F1out_B8 (O) F1out_B13 (O)
19 F1in_A13 (I)
20 F1in_B13 (I)
21 F1in_A14 (I)
22 F1in_B14 (I)
23 F1out_A14 (O)
24 PCI_D_P1 (I) PCI_D_N1 (I) F1out_B14 (O)
25 PCI_U_P1 (O) PCI_U_N1 (O) F1out_A15 (O)
26 PCI_D_P2 (I) PCI_D_N2 (I) F1out_B15 (O)
27 PCI_U_P2 (O) PCI_U_N2 (O) F1in_A15 (I)
28 PCIS_D_P1 (I) PCIS_D_N1 (I) F1in_B15 (I)
29 PCIS_U_P1 (O) PCIS_U_N1 (O) F1in_A16 (I)
30 PCIS_D_P2 (I) PCIS_D_N2 (I) F1in_B16 (I)
Tab. 3.17 PU16 Connector (top)
Tab. 3.16 PU16 Connector (bottom) (Cont.)
66 A50010-A3-C800-5-7619
E1 Interface
According to ITU-T G.703/6
Power Supply
31 PCIS_U_P2 (O) PCIS_U_N2 (O) F1out_A16 (O)
32 GND GND F1out_B16 (O)
Tab. 3.17 PU16 Connector (top) (Cont.)
Impedance, switchable
symmetrical, ungrounded
and shielded connections . . . . . . . . . . . . . . . . . . . .
coaxial connections. . . . . . . . . . . . . . . . . . . . . . . . .
120
75
Bit rate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2048 kbit/s (1 50 ppm)
Coding. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HDB3
Nominal voltage
coaxial connections. . . . . . . . . . . . . . . . . . . . . . . . .
symmetrical connections. . . . . . . . . . . . . . . . . . . . .
2.37 V
3 V
Nominal value of the pulse width. . . . . . . . . . . . . . . . . . 244 ns
Pulse form from E1out. . . . . . . . . . . . . . . . . . . . . . . . . . according to ITU-T G.703,
Fig. 15
Frame structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . unframed or
according to ITU-T G.704/5
Jitter characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . according to ETS 300324,
TBR 12
Cable attenuation at E1in at 1024 kHz . . . . . . . . . . . . . 6 dB
Reflection attenuation
51 Hz to 102 kHz. . . . . . . . . . . . . . . . . . . . . . . . . . .
102 kHz to 2048 kHz. . . . . . . . . . . . . . . . . . . . . . . .
2048 kHz to 3072 kHz. . . . . . . . . . . . . . . . . . . . . . .
12 dB
18 dB
14 dB
Operating voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 V to 72 V
Power consumption. . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 W
Short-circuit protection for 3.3 V . . . . . . . . . . . . . . . . . . Safety fuse 1 A
A50010-A3-C800-5-7619 67
User Manual
UMN CMXC
3.5 Supervision Unit SUE and SUE-E
3.5.1 Overview
Fig. 3.14 Operation and Monitoring via SUE-E Interfaces
The SUE-E performs the following functions:
Creating a virtual concentrator (SISA-V/LMX V2)
The SUE-E establishes an SISA-V/LMX V2 which manages the ASA32 network el-
ement as being continuously present in its polling list.
Operating the NEs in the shelf via QD2 master interface
Duplicating the QD2 slave interface to provide additional system access
Establishing the T functionality of both QD2 slave interfaces to set up multipoint net-
work structures
Network management access to the T-port of QD2 slave port 1 via Ethernet interface
(only SUE-E)
Operation of a local F interface
Evaluating up to 8 external alarms.
If, among the network elements in a station, the SISA-V is the highest network element
in the OS hierarchy, then the SISA-V is designated as Top of Station (TOS). A data-
base is maintained with details of the network elements which comprise the station and
about the connections to other stations which are linked to the station addressed (in the
descending direction).
During its initialization phase, the SUE-Es operating program carries out self-tests on
the plug-in unit components and the interfaces. In the event of a fault, the SUE-E outputs
fault signals. In addition, card identification is carried out using static inputs.
There are two options for connection to the network management system (NWS). The
SUE-E can be connected either directly via RS485/RS232 (QD2 operation mode 1: with-
out Ethernet), or via Ethernet interface provided by the T-port of QD2-slave interface 1
(QD2 operation mode 2) to enable access to the WAN/LAN network.
i
The SUE-E is the subsequent unit to the SUE and fulfils management and supervision
functions in the SNUS, FMX2S and MXS19C shelves. In addition to the SUE, the SUE-E
provides an Ethernet interface. In this document, the SUE-E is mainly described, beside
some control and connector assignment information for the SUE.
QD2-M1 64 kbit/s QD2-S1
QD2-S2
F-SST
OS
LCT
SUE-E
QD2-M2
T
T
CMXC

SMX1/4c
QD2-S QD2-S QD2-S
LTx FMX2R3
QD2-S

QD2 or
Ethernet
QD2
68 A50010-A3-C800-5-7619
The SUE-E has the following interfaces:
2 QD2 slave interfaces,
QD2 slave 1 with control line (SE) and transparent operating mode (T)
The T-port can be switched to use it as QD2 or Ethernet 10Base-Tx/100Base-Tx.
QD2 slave 2 with transparent operating mode (T)
F interface,
QD2 master interface,
8 alarm inputs (A1+ to A8+ and negative reference potential A),
Shelf rear panel coding (K0 to K4) to define the SISA address (5 bits),
2 8-pin switches to switch over the configuration of the QD2 interfaces either ac-
cording to RS232 or RS485,
6-pin switch switch for bus termination with 120 per QD2 slave port and for the
T-ports,
6-pin switch to set the ECC time slot, and activate/deactivate 9.6 kbit/s signal gen-
eration per T-port of QD2 slave ports,
2 x 5 jumpers to set the QD2 operation mode either on QD2 slaves active, or on
Ethernet slave active and QD2 slaves are inactive,
Power supply.
F Interface
The F interface is used to access the virtual concentrator on the plug-in unit, and its sub-
ordinate network elements. The F interface can be access by a 9-pin plug connector on
the front of the unit. It conforms to ITU-T V.28.
QD2 Slave Interfaces
The QD2 slave interfaces are arranged as specified by EIA RS485. QD2 slave
interface 1 is always used for the primary network access, while QD2 slave interface 2
is used as a redundant network access. In addition, QD2 slave interface 1 has an SE
control line for connecting to a remote QD2 bus.
(virtual
concen-
trator)
SISA-V
Alarm
inputs
QD2
slave
port 2
QD2
slave
port 1
Ethernet
QD2
master
F port
ECC port
RS485
RS485
V.28
RS485
RS485
RS485
RS232
RS485
RS232
Alarm inputs
Redundant TMN access
Primary TMN access
T port (HDLC) or
Shelf connector and
Local operation
ECC channel
T port
primary TMN access
via Ethernet
internal QD2 bus
PCM
ASA32
SUE-E
PCM port PCM bus
A50010-A3-C800-5-7619 69
User Manual
UMN CMXC
The T-port of QD2 interface 1 (QD2Txx1) can be used dependent on jumper X11 setting:
either as T-port for QD2 slave interface 1 (default status)
or as Ethernet slave port (10Base-Tx/100Base-Tx interface).
Ethernet interface
The Ethernet interface provides a slave interface for 10Base-Tx and 100Base-Tx. The
electrical properties for 10Base-Tx comply with specification IEEE 802.3 clause 14, and
for 100Base-Tx with IEEE 802.3 clause 25.
The data are transmitted on a 4-wire line (two pair twisted wire).
When the interface is configured as Ethernet port, a primary network access via Ether-
net tunnel is possible. In that case, the QD2 interfaces 1 and 2 are deactivated. The re-
dundant network access is no longer possible.
The access via Ethernet interface is implemented via QD2Txx1 to ensure a point-to-
point connection without involvement of other units.
QD2 Master Interface
The QD2 master interface conforms to EIA RS485. The QD2 master interface provides
a serial bus system for connecting the network elements.
ZA Interface
The ZA interface signals urgent alarms (A alarms) or service alarms to the central
service observation equipment. The interface takes the form of a break contact, so that
if the operating power fails an alarm is output.
3.5.2 Control and Monitoring
Control and monitoring by the SUE-E is effected by the OS through the QD2 slave inter-
face or Ethernet interface, or by the LCT via the F interface. The QD2 master interfaces
are preinitialized at 64 kbit/s. For the F interface, a bit rate of 9.6 kbit/s is preset.
There are 4-pin switches on the unit, which can be used to terminate the bus for the QD2
slave interfaces. The SISA address for the shelf is read by rear panel contacts K0 to K4.
For local monitoring, one red and one green LED is fitted on the front of the SUE-E, and
a yellow LED further back on the unit- see the following table.
LED (green) LED (red) LED
(yellow)
1)
Status
Off Off Off No operating voltage
On Off Off Fault-free operation
On Off On Fault-free operation, connection established to the next
higher hierarchical level in the OS
Off On Off SUE-E in a fault state or self-test
Off On On Fault state, connection is maintained
1) Only visible when the cover plate for the unit is removed
Tab. 3.18 Visual Signals Output by the SUE-E
70 A50010-A3-C800-5-7619
Ethernet-Line Supervision
For the Ethernet interface (QD2 operation mode 2 of SUE-E), an Ethernet line monitor-
ing is necessary. Because TCP/IP does not offer a capable option for cyclic line moni-
toring, the ACI (version 6.1 or higher) simulates line monitoring by software. At the
SUE-E, the Ethernet slave interface (QD2 operating mode 2) provides this functionality.
For line monitoring, a second TCP connection between master and slave is established
to allow the transport of control commands not affected by data traffic. So, the initial con-
nection is used for control commands and the second for the QD2 data. If during line
monitoring a line cut off is detected, the master-slave connections will be closed. After
that, the two connections attempt to build-up again.
The necessary IP addresses and TCP port have to be configured. For line monitoring,
the TCP port number can be chosen freely between 50000 and 65534 (e.g. 54000). The
port for the associated data connection is then the next higher number (e.g. 54001).
For Ethernet line monitoring, the parameters "PollTime" and "Response-Time" are nec-
essary. The "PollTime" is the time intervall between the control telegrams to the SUE-E.
The Response-Time is the time-out value for responses to control telegrams. If there
is no response, the DCN server shuts down the connection to the SUE-E, and tries then
to reconnect the SUE-E. The parameters are configured at the Ethernet-Master (ACI)
and communicated to the slave.
3.5.3 Controls
Controls of the SUE
Fig. 3.15 Controls of the SUE
S3
View from
front:
S2
S1
10
11
green
red
yellow
ON
3
8
1
6
8
1
ON
1
ON
S4
6
1
ON
F2 F1
12
1
4
2
X4
3
1
4
2
X5
D3
12 Connector for LCT (F-Inter-
face)
X4 Test jack
X5 Test jack
F1 Solder-in fuse for 48 V/60 V
(2,5 A)
(2,5 A)
D3 Initial program loader
A50010-A3-C800-5-7619 71
User Manual
UMN CMXC
Switch S1 and S2:
Switch S3:
Switch S4: T-Interface
Connector 12 (F Interface)
Switch S1 Switch S2
Slides 1 to 4 Slides 5 to 8 Slides 1 to 4 Slides 5 to 8 Function Setting
OFF
1)
ON
1)
Interface settings at master- port 1 RS485 interface
ON OFF Interface settings at master- port 1 RS232
OFF
1)
ON
1)
Interface settings at slave-Port 1 RS485 interface
ON OFF Interface settings at slave-Port 1 RS232
1) As delivered state
Slide Function Position Meaning
1 Interface termination for QD2 slave port 1 (transmit direction) OFF
1)
ON
High-impedance
120
2 Interface termination for QD2 slave port 1 (receive direction) OFF
1)
ON
High-impedance
120
1)
ON
High-impedance
120
1)
ON
High-impedance
120
5 Interface termination for T-Port on slave 1 (transmit direction) OFF
1)
ON
High-impedance
120
1)
ON
High-impedance
120
Slide Port Position Function
4 Slave port 1 OFF
1)
ON
64 kbit/s or 9,6 kbit/s T port
9,6 kbit/s with T port signal regeneration
5 Slave port 2 OFF
1)
ON
64 kbit/s or 9,6 kbit/s T port
9,6 kbit/s with T port signal regeneration
1
5
6
9
12
No. Assignment No. Assignment
1 6
2 RXD 7
3 TXD 8
4 9
5 GND
72 A50010-A3-C800-5-7619
Controls of the SUE-E
Fig. 3.16 Controls of the SUE-E
Switch S1 and S2:
Switch S3:
View from
front:
X1
X2
green
red
yellow
3
S4 6
ON
F1
12
1
4
2
X4
3
1
4
2
X5
X1 Internal connector
X2 External connector
12 Connector for LCT (F-Inter-
face)
X4 Test jack
X5 Test jack
(2.5 A delayed acting)
(2.5 A delayed acting)
F3 Solder-in fuse for ZA-contact
(0.25 A fast acting)?
S1
8 1
8 1
6
1
S2
S3
ON
ON
ON
1
F2
F3
1
2
X11
1
9
2
0
Switch S1 Switch S2
Slides 1 to 4 Slides 5 to 8 Slides 1 to 4 Slides 5 to 8 Function Setting
OFF
1)
ON
1)
Interface settings at master- port 1 RS485 interface
ON OFF Interface settings at master- port 1 RS232
OFF
1)
ON
1)
Interface settings at slave-Port 1 RS485 interface
ON OFF Interface settings at slave-Port 1 RS232
1)
ON
High-impedance
120
1)
ON
High-impedance
120
1)
ON
High-impedance
120
1)
ON
High-impedance
120
A50010-A3-C800-5-7619 73
User Manual
UMN CMXC
Jumper X11
The jumper X11 is used to select QD2 operation mode 1 (RS485 interface) or 2 (Ether-
net interface) at T-port of QD2 slave port 1. Tx and Rx on the T-port are switched by four
jumpers. An additional jumper activates respectively deactivates the operation mode
QD2 via Ethernet tunnel, see Fig. 5.5. Simultaneously, the RS485-transceiver will be
deactivated in case of Ethernet tunnel is used.
The operator has to ensure, that ever all 5 jumpers of X11 are set according the opera-
tion mode, see Tab. 3.19.
Switch S4
ECC Initialization
Slave Port 1 T-Port Operation Mode
1)
ON
High-impedance
120
1)
ON
High-impedance
120
Jumper X11 Jumper setting
3 to 4
7 to 8
11 to 12
15 to 16
19 to 20
QD2 operation mode 1 (as-delivered state)
T-port function via RS485 (HDLC),
QD2 slaves are activated
1 to 2
5 to 6
9 to 10
13 to 14
17 to 18
QD2 operation mode 2
Ethernet function (QD2 via Ethernet tunnel) active,
QD2 slaves are deactivated
Tab. 3.19 Operating Modes QD2-Slave 1 T-port (QD2Txx1)
S4-1 S4-2 S4-3 Bus time slot (0 to 63) Time slot (1 to 32)
ON OFF OFF 29 15 odd
OFF ON OFF 41 21 odd
ON OFF ON 30 15 straight
OFF ON ON 42 21 straight
All other codings ECC switched off
S4-4 Setting
OFF 9.6 kbit/s signal generation switched off (delivery state)
ON 9.6 kbit/s signal generation switched on
74 A50010-A3-C800-5-7619
Slave Port 2 T-Port Operation Mode
Connector 12 (F Interface)
S4-5 Setting
OFF 9.6 kbit/s signal generation switched off (delivery state)
ON 9.6 kbit/s signal generation switched on
1
5
6
9
12
No. Assignment No. Assignment
1 6
2 RXD 7
3 TXD 8
4 9
5 GND
A50010-A3-C800-5-7619 75
User Manual
UMN CMXC
3.5.4 Connector Assignment
Connector assignment of the SUE
Fig. 3.17 Connector 11 of the SUE
Row
No
.
c b a
2 QD2Tin_a1 QD2Sin_a1 QD2Sin_b1
4 QD2Tin_b1 QD2Sout_a1 QD2Sout_b1
6 QD2Tout_a1 QD2Sin_a2 QD2Sin_b2
8 QD2Tout_b1 QD2Sout_a2 QD2Sout_b2
10 QD2Tin_a2 SESout_a SESout_b
12 QD2Tin_b2 QD2Min_a1 QD2Min_b1
QD2_MCLK_b QD2_MCLK_a
14 QD2Tout_a2 QD2Mout_a1 QD2Mout_b1
CTXD
1)
CRXD
1)
16 QD2Tout_b2 S0in_a S0in_b
T1
1)
18 A1P AM
L1
1)
RESET
1)
20 A2P A0out_a S0out_b
22 A3P QD2Min_a2 QD2Min_b2
24 A4P QD2Mout_a2 QD2Mout_b2
L3
1)
L2
1)
26 A5P Ein_a Ein_b
Ein_a Ein_b
28 A6P Eout_a Eout_b
30 A7P EDS_out EDS_in
32 A8P GND
1) Pins are used only for test purposes
76 A50010-A3-C800-5-7619
Fig. 3.18 Connector 10 of the SUE
Row
No
.
c b a
GND_S GND_S GND_S
2 GND/PUP GND
GND K4
4 MUP_2 MUP_1 ZA
6 O3 I7 O2
O4 PB4 PB7
8 PB0 PB3
GND PB6 PB5
10 PE
1)
PB2 PB1
P5V_EEP GND GND
12 GND GND
SCL GND GND
14 TXDSVB RXDSVB
SDA
16 RTSSVB CLKSVB
GND
18 K2 K1
20 K3 K0
22 GND I2 I1
24 GND
26 I3 GND
GND GND SYN_E
28 I0 I4
PCM_E CLK_4M
30 GND O1
SYN_S PCM_S
32 GND GND GND
A50010-A3-C800-5-7619 77
User Manual
UMN CMXC
Connector assignment of the SUE-E
Fig. 3.19 Connector X2 of the SUE-E
Row
No
.
c b a
2 QD2Tin_a1 QD2Sin_a1 QD2Sin_b1
4 QD2Tin_b1 QD2Sout_a1 QD2Sout_b1
6 QD2Tout_a1 QD2Sin_a2 QD2Sin_b2
8 QD2Tout_b1 QD2Sout_a2 QD2Sout_b2
10 QD2Tin_a2 SESout_a SESout_b
12 QD2Tin_b2 QD2Min_a1 QD2Min_b1
QD2_MCLK_b QD2_MCLK_a
14 QD2Tout_a2 QD2Mout_a1 QD2Mout_b1
CTXD
1)
CRXD
1)
16 QD2Tout_b2
T1
1)
18 A1P AM
L1
1)
RESET
1)
20 A2P
22 A3P
24 A4P
L3
1)
L2
1)
26 A5P Ein_a Ein_b
Ein_a Ein_b
28 A6P Eout_a Eout_b
30 A7P
32 A8P GND
1) Pins are used only for test purposes
78 A50010-A3-C800-5-7619
Fig. 3.20 Connector X1 of the SUE-E
Row
No
.
c b a
GND_S GND_S GND_S
2 GND/PUP GND
GND K4
4 MUP_2 MUP_1 ZA
6 O3 O2
O4 PB4 PB7
8 PB0 PB3
GND PB6 PB5
10 PE
1)
PB2 PB1
P5V_EEP GND GND
12 GND GND
SCL GND GND
14 TXDSVB RXDSVB
SDA
16 RTSSVB CLKSVB
GND
18 K2 K1
20 K3 K0
22 GND I2 I1
24 GND
26 I3 GND
GND GND SYN_E
28 I0 I4
PCM_E CLK_4M
30 GND O1
SYN_S PCM_S
32 GND GND GND
A50010-A3-C800-5-7619 79
User Manual
UMN CMXC
3.5.5.1 F Interface
3.5.5.2 QD2 Slave Interfaces
3.5.5.3 Ethernet Interface
Configuration point-to-point, as per V.28
Transmission lines screened, unbalanced
Bit rate, auto detect 9.6/19.2/38.4 kbit/s
Transmission mode asynchronous
Line code NRZ
Permissible length 20 m
Protocol
Frame structure
Address and control byte
Initiator of the data circuit
Secondary addresses
IEC TC57
HDLC (NRM, polling)
primary (LCT)
1
Data format 8 data bits, even parity
1 stop bit
Plug connector plug
(TXD:pin 2; RXD:pin 3)
Configuration serial bus as per EIA RS485
Format back-to-back structure
Additional SE option on QD2 slave 1 point-to-point per EIA RS422
Bus users 1 master and up to 30 slaves
Transmission lines,
separate transmit and receive lines
QD2 slave 1 including T and SE lines
QD2 slave 2 including T lines
balanced, 10-wire
balanced, 8-wire
Bit rate, auto detect 0.6/1.2/9.6/64 kbit/s
Transmission mode plesiochronous
Line code NRZI
Protocol
Secondary addresses,
which can be set using 5-pin switches
HDLC (NRM, polling)
primary (NCT, LCT)
1 to 30
TXD idle state logical 1 (high-impedance)
RXD expected idle state continuous flags
Termination, switchable 121
T-port of QD2-S1 is switchable to Ethernet Interface see Ethernet Interface
Access (only SUE-E) via T-port of QD2-S1
Transmission line 4-wire (two pair twisted wire)
Connector RJ45 connector and jack
Interfaces 10Base-Tx or 100Base-Tx
80 A50010-A3-C800-5-7619
3.5.5.4 QD2 Master Interface
3.5.5.5 Signal Output, ZA
3.5.5.6 Signal Inputs A1+ / A1- to A8+ / A8-
3.5.5.7 Backplane Detection
3.5.5.8 Power Supply
Configuration, serial bus switchable as per EIA RS485 or RS 232
Bus users 1 master and up to 30 slaves
Transmission lines, separate transmit and receive lines,
in addition, received synchronous clock usable for
transmit direction
balanced, 4-wire
Bit rate, configurable 0.6/1.2/9.6/64 kbit/s
Transmission mode plesiochronous
Line code NRZI
Protocol
Secondary addresses
HDLC (NRM, polling)
primary (SUE-E)
1 to 30
RXD expected idle state logical 1 (high-impedance)
TXD idle state continuous flags
Termination, switchable 121
Form switching contact to ground potential, 1-pin
Malfunction or fault situation (closed contact)
Current
Residual voltage
1 mA, 60 mA
2 V
Fault-free operation (open contact)
Applied DC voltage
Permissible operating range
Maximum residual current
30 V
8 V to 30 V
20 A
Configuration DC interfaces, isolated from
ground
Transmission lines per input balanced, 2-wire
Input voltage (floating)
In the active state 20 V to 60 V
Passive state 0 V
Configuration TTL input, internal pull-up
Number of contacts 5, unbalanced
Input voltage 36 V to 72 V
Power consumption (at 60 V) 3 W
A50010-A3-C800-5-7619 81
User Manual
UMN CMXC
4 Commissioning
4.1 Introduction
4.1.1 Scope of the ITMN
The ITMN presents the installation procedures for all network elements (NEs) including
the following information:
Hardware settings
Commissioning procedures for NEs or parts thereof
Electrical interface configuration settings.
Configuration of country or customer-specific Linecard parameters.
For path management operations, only standard configurations according to the engi-
neering rules are covered, since these cases are supported by LCTs. The subscriber
administration, which is only supported by the TMN, is not described.
4.1.2 Error Reports on the Installation Test Manual
Incorrect or unclear sections of this Section should be described in detail in a document
error report.
The error report should be sent to the Technical Assistance Center TAC3 in Munich.
4.1.3 Dealing with Defective Modules
If a module is really defective, it should be carefully repacked and returned to the repair
center along with the correct documentation.
For details, please see the Guidelines for the Repair and Replacement Service RUAD2
(Product No. A30100-R4050-A1-*-7635).
4.1.4 Procedure in the Event of Faults
Faults occurring during on-line operation should be identified and rectified in accordance
with the instructions in the Section 6 "Maintenance".
4.1.5 Procedure in the Event of Serious Faults
Serious faults are not dealt with in the MMN. First, the installation technician should try
to clear the fault. If the installation technician is not qualified to eliminate serious faults,
a fault report must be completed, providing the following information in detail (TAC2
Tool, FMERF):
Description of the test step attempted
Description of the system response
Description of any parallel system activities, e.g. work done by other testers during
modification of hardware or software.
The fault report must be sent to TAC2/TAC3.
82 A50010-A3-C800-5-7619
4.2 Prerequisites
4.2.1 Hardware
1. Local Craft Terminal (LCT):
A Local Craft Terminal (LCT) is required for the configuration, administration and
software download of the Network Elements. The LCT has to be configured at least
in such a way as described in the User manual AccessIntegrator, UMN:IMN
(see 1.3 "Additional Documentation").
2. Connecting Cable (for the F ports):
An LCT universal cable will be needed to connect the LCT to the F interface of a
SUE-E (product code number of the universal cable: S42023-A877-S100,
length = 3m).
This universal cable has a number of different connectors.
9-pin sub-D jack for the connection to the LCT:
(Labeling on the jack: LCT) Pin Connections:
The SUE-E needs a 1:1 connection:
9-pin Sub-D jack (Labeling on the jack: FMX, Flex MuxV2
3. Digital multimeter (e.g. for measuring the battery voltage).
4.2.2 Software
Installation of the ACI-Software:
The SW-prerequisites for the LCT are described in the UMN:IMN of the User Manual
AccessIntegrator ACI (see 1.3 "Additional Documentation").
Scope of supply: 1 CD-ROM
APS of the CMXC System Module:
The APS (application program software) includes all load files for the Network Elements
(NEs) of the CMXC.
The System APS (S-APS) includes:
1 stocklist
1 complete set of load files (P-APS)
The load files for the software download are listed in Tab. 5.5.
Number Assignment Number Assignment
1 6
2 RXD 7
3 TXD 8
4 9
5 GND
Tab. 4.1 Pin Connections
i
It is vital to install the ACI software according to the instructions given in the IMN of the
ACI!
A50010-A3-C800-5-7619 83
User Manual
UMN CMXC
4.3 Procedures
4.3.1 Sequences for Commissioning
For commissioning the CMXC the following sequence should be used:
4.3.2 Visually Inspection (Check List)
The following tasks must be performed for every system component before/during com-
missioning:
1. All Deliverables were supplied and the Installation Work is completed
The shelves SNUS are assembled.
Using the parts list, check that all deliverables were supplied.
The cabling and positioning of the modules should be checked with the installa-
tion instructions for the individual system components.
The modules are not plugged-in.
Both all internal and external cables were correctly routed and connected.
The shelves and cables are labeled correctly.
Visual check of the complete installation (particularly the protection devices, e.g.
overvoltage and lightning protection).
2. The Hardware Modules are in delivery Condition
The copper interfaces and the multiplexer section can remain in their delivery con-
dition.
The hardware settings of modules must be checked.
The modules are equipped with the current firmware and hardware (compare
for this the existing FW and HW with the Release Note of the current SW-APS
baggage)
The power supply is connected and constantly available
(the emergency power supply system is operational) but
The circuit breakers for the power supply must be switched off.
For installation in the ONU/ODT, the battery connector must be unplugged from
the power supply.
Cables to other SISA partners may not be connected (the QD2 connections
should be removed to prevent the SISA network from being affected.).
3. The CMXC documentation is available on Site.
Procedure see Section
1. Visually Inspection (general Requirements/Check
list)
4.3.2
2. Commissioning of the SNUS 4.3.4
3. Commissioning of the SUE-E 4.3.5
4. Commissioning of the CUC 4.3.6
5. Commissioning of the PU16 4.3.7
6. Creating Crossconnections 4.3.8
7. Backup of the Configuration data
Please use the Backup function of the ACI
User Manual AccessIntegrator,
UMN:OMN ACI DM V8.3 (see
1.3 "Additional Documentation")
Tab. 4.2 Sequence of the Commissioning
84 A50010-A3-C800-5-7619
4. The required Tooling/Test Equipment is available.
5. The LCT is installed and ready for Service.
4.3.3 Starting the LCT
So you can start the LCT:
1. Login in Windows NT (user name + keyword)
2. Start the ACI-proceedings via the start-menu
in the following order:
DCN server
ACI LCT server
ACI LCT client.
4.3.4 Commissioning of the SNUS
4.3.4.1 Hardware Settings
SISA Address
The SISA addresses of all units of the CMXC are assigned to the backplane. The QD2
address setting for the SUE-E occurs via the DIL switch S101 (see section 3.2.2).
Clock Supply
The SNUS has a number of symmetrical clock inputs and clock outputs. The following
connections are accessible at the external connectors:
T3in1, external guide clock for synchronizing the CMXC
T3out1, clock output from the CMXC for synchronizing downstream modules
If required, the clock inputs are terminated directly in the units (CUD, CUC, ADM) in the
shelf. It is not possible to synchronize the LT22CM (slot 209) on the T3 in the SNUS (no
level converter is available on the backplane).
Shelf Equipment
The possible equipment variants of the SNUS are shown in the Tab. 3.1. SUE-E and
units for CMXC must be plug-in in the following slots of the Shelf:
QD2 Structure
If the stand-alone operation mode of the SNUS, the SUE-E monitors all modules in the
shelf. The internal QD2 bus is switched using DIL switches S103 (all slider units on
OFF) and S104 (all slider units on ON) on the SUE-E master port (see Section 3.2.3).
Modules Slot
SUE-E 201
PU16 210
CUC(1) 211
CUC(2) 212
PU16 213
Tab. 4.3 Shelf Equipping with SUE-E and Units for CMXC
A50010-A3-C800-5-7619 85
User Manual
UMN CMXC
Testing the Power Supply in the SNUS and Installing the Units
1. Please switch on the power supply.
2. Measure the SNUS system voltage and test the correct polarity of the power supply.
If the voltage or the polarity is not correct, test the power supply and connections to
the SNUS and rectify the fault.
3. Please plug-in the modules in the slots of the SNUS.
4.3.5 Commissioning of the SUE-E
The following hardware settings must be provided, see Sections 4.3.4.1 (SNUS) and
4.3.5.1 (SUE and SUE-E):
Setting the SISA address
The SISA address is set with DIL switch S101/S100 on the backplane of the shelf.
Operation mode of QD2 ports
For the master port1 and the slave port1 you can select either RS232 or RS485.
Slave port 2 always permanently operates as RS485 IF. The settings can be made
with DIL switches S1 and S2 on the SUE-E.
QD2 operation mode: QD2 slave or Ethernet slave
The QD2 operation mode can be set by jumper X11 on the SUE-E board.
Bus terminations for slave ports and T ports
Operation mode of T ports as QD2 slave (QD2 operation mode 1)
Configure the operating mode of the T ports. The T port of the SUE-E operates with
oversampling at a usable bit rate of 9.6 kbit/s. A signal regeneration can be switched
on or switched of for the T port. This signal regeneration remedies the distortions of
the 9.6 kbit/s payload signal arising as a result of oversampling. This functionality is
useful to reduce the probability of signal corruptions in longer line structures.
4.3.5.2 Software Settings
Please connect the LCT to the F port of the SUE-E and start the LCT (see 4.3.3).
If the SUE-E is working with F-port protection please see the description in User Manual
AccessIntegrator, UMN ACI (Section 1.3 "Additional Documentation").
Software Download
1. Click on the SISA-V/LMX V2 of the SUE-E with the right mouse button.
Dialog Software Management APS Management...
86 A50010-A3-C800-5-7619
Fig. 4.1 SUE-E Dialog Software Download
2. Select the appropriate load for SW download and start it with the "Download" button
On the SUE (S42024-A1857-B1) or SUE-E (S42024-A1857-C1) the following load
must be loaded:
SEBL0R0.nnn without password protection on the F port or
SEBL0Rx.nnn with password protection on the F port.
3. Reset the SUE-E after successful downloading
4. Now the SISA-Vs of the units, equipped in the shelf, must appear under the
SISA-V/LMX V2 of the SUE-E.
For SUE-E, a software download over the WAN/LAN network is possible in the QD2 op-
erating mode 2, see UMN:TED Controls of the SUE-E. The Ethernet configuration
must be performed in the following way:
1. Switch to QD2 operating mode 2 via jumper X11 on SUE-E board.
2. Connect LCT via F-port to SUE-E, setup the Ethernet configuration.
3. Restart the SUE-E, and connect the OS via Ethernet port to the SUE-E.
4. SW download can be started.
A SW download via F-port with LCT is also possible, but takes much more time. An up-
date via FTP is not supported.
Setting the desired bit rate of the QD2 ports:
1. In the DCN View use the left mouse button to select network element SISA-V/
LMX V2 for the SUE-E, open the menu by clicking with the right mouse button and
select the item NE Configuration/General NE Parameters:
i
Before software download has not been closed, no further commands or requests must
be sent to the network element.
i
If software with F-port protection was loaded, all following operating procedures are
possible only after valid password input, see user manual ACI.
A50010-A3-C800-5-7619 87
User Manual
UMN CMXC
Fig. 4.2 SUE-E Register Card Configuration
Set the corresponding bit rate for the master port.
The slave port sets itself automatically to the bit rate of the higher-level SISA hierar-
chy (only relevant, if the higher-level network element exist).
In Ethernet slave mode, configure the TCP/IP parameters:
Fig. 4.3 SUE-E Register Card General
The necessary IP addresses and TCP port have to be configured. For line monitor-
ing, the TCP port number can be chosen freely between 50000 and 65534 (e.g.
54000). The port for the associated data connection is then the next higher number
(e.g. 54001).
Example for TCP/IP configuration is shown in Fig. 4.4.
88 A50010-A3-C800-5-7619
Fig. 4.4 Example of TCP/IP Configuration
2. The fact that the higher level station has access to the SUE-E is shown by the yellow
LED located on the side of the SUE-E, see UMN:TED Section 3.22.2 (only relevant
when an higher-level network element exists).
3. Check the loaded software.
MENU: Utilities/Inventory Data Retrieval.../Equipment Data...
Fig. 4.5 SUE-E Register Card Inventory Data
Check for Existing Alarms
1. MENU: Fault/Alarm list...
Check for existing alarms and, if necessary, correct these in accordance with the
Branch to Maintenance.
2. Close the alarm window with "Close.
IP address: x.x.x.x
IP-address: 208.0.0.1
Router
Ethernet port
(slave)
QD2 port
(master)
Configuration parameters:
IP address: 208.0.0.2
Subnet mask: 255.255.255.0
Gateway IP-address: 208.0.0.1
TCP port: 54000
SUE-E
Ethernet (TCP/IP)
A50010-A3-C800-5-7619 89
User Manual
UMN CMXC
4.3.6 Commissioning the CUC
4.3.6.1 Prerequisites
The following prerequisites are necessary for commissioning a CUC:
The CUC is commissioned after the SUE-E, i.e. after the associated SISA concen-
trator has been provided.
The associated PU16 must be inserted and initialized to configure the port.
No hardware settings are necessary on the CUC module.
The first operational CUC is the one that is active. The software configuration switches
it to standby mode.
SW Download
1. In the DCN View, select the icon for the NE SISA-V/LMX for the CMXC using the left
mouse button.
2. Choose in the main menu the menu item Configuration Software Management
APS Management.... The dialog Software-Download will be opened.
Select the file number 2 for the CUC in the field File Number.
Select the matching file in the field File used for SWDownload (selection with the
button Browse)
Confirm with Download.
3. After the SW download has ended with the message Download Completed Suc-
cessfully, this is confirmed by clicking on the Close button.
4. To activate the new software, the CUC has to be reset (only necessary if the reset
has not been performed automatically).
5. Reset the CUC
In the DCN View, select icon for the NE SISA-V/LMX for the CMXC using the left
mouse button.
Open the Equipment View via menu item View Equipment View.
Select the module CUC.
Choose in the main menu the menu item Configuration NE Configuration NE
Status...
Click on the Reset Equipment button.
i
No commands or requestions must be sent to he system before the process software
download is not ended.
i
For loading the software the first time (no SW is loaded on CUC) after successfully
download, no reset is necessary.
90 A50010-A3-C800-5-7619
6. Check the loaded Software
In the DCN View, select the icon for the NE SISA-V/LMX for the CMXC using the left
mouse button.
Choose in the main menu the menu item Utilities Inventory Data Retrieval
Equipment Data...
Compare the loaded software with the APS list.
Set Date and Time of the System
mouse button.
2. Choose in the main menu the menu item Configuration NE Configuration NE
Status .... The dialog Status - ... with register cards Time and date and Operating
mode is opened.
3. Set date and time.
Click on the Synchronise button to send time and date settings to the module.
Confirm your settings with Apply.
Close the dialog with Close
Configuration
1. In the DCN View, select the icon for the NE SISA-V/LMX for the CMXC and open the
dialog General NE-Parameters - CMXC#...:CUC#... (see Section 5.3.2 "CUC".
2. Clock Setting
Open the Clock Sync register card.
Select the corresponding clock source according to your planning documentation
and confirm with Apply (see "Configuring the Central Unit CUC", Register Card
Clock sync.).
3. Configuring the Frame Structure and the Initialization
Open the Frame register card.
Perform the corresponding project-specific port settings according to your planning
documentation and confirm with Apply (see "Configuring the Central Unit CUC",
Register Card Frame).
4. Configuring the ECC-Mode
Open the ECC-Mode register card.:
Perform the corresponding project-specific port settings according to your planning
documentation and confirm with Apply (see "Configuring the Central Unit CUC",
Register Card ECC Mode).
5. Port Initialization
Open the General register card.
Perform the corresponding project-specific port settings according your planning do-
cumentation and confirm with Apply (see "Configuring the Central Unit CUC",
Register Card General).
6. Configuration Backup
The set configuration data should be backed up via the backup function of the ACI
(see the User Manual AccessIntegrator ACI DM, UMN:ADMN).
A50010-A3-C800-5-7619 91
User Manual
UMN CMXC
4.3.7 Commissioning the PU16
The 6-pin jumpers are to be used to configure the 75 or 120 terminating resistors in
the 16 E1 interfaces. The correct jumper setting should be taken from the Section 3.4.3.
All other configurations are made using the AccessIntegrator operating system.
SW Download
mouse button.
2. Choose in the main menu the menu item Configuration Software management
APS Management.... The dialog Software-Download will be opened.
Select the file number 3 for the PU16 in the field File Number.
Select the matching file in the field File used for SWDownload (selection with the
button Browse)
Confirm with Download.
3. After the SW download has ended with the message Download Completed Suc-
cessfully, this is confirmed by clicking on the Close button.
4. To activate the new software, the PU16 has to be reset (only necessary if the reset
has not been performed automatically).
5. Reset the PU16
In the DCN View, select the icon for NE SISA-V/LMX for the CMXC using the left
mouse button.
Open the Equipment View via menu item View Equipment View.
Select the module PU16.
Choose in the main menu the menu item Configuration NE Configuration NE
Status....
Click on the Reset Equipment button.
6. Check the loaded Software
In the DCN View, select the icon for NE SISA-V/LMX for the CMXC using the left
mouse button.
Choose in the main menu the menu item Utilities Inventory Data Retrieval
Equipment Data...
Compare the loaded software with the APS list.
i
No commands or requestions must be sent to he system before the process software
download is not ended.
i
For loading the software the first time no SW is loaded on CUC) after successfully down-
load, no reset is necessary.
92 A50010-A3-C800-5-7619
Configuration
1. In the DCN View, select the icon for NE SISA-V/LMX for the CMXC and open the
dialog General NE-Parameters - CMXC#...:PU16#... (see Section 5.3.3 "PU16".
2. Control Functions and Maintenance Functions
Open the Loops register card.
Set No loop. Confirm your settings with Apply (see Section 5.3.3 "PU16",Register
Card Loops).
3. Frame Structure and Signaling
Open the Frame register card.
Configure the necessary ports according to the planning documentation and confirm
with Apply see Section 5.3.3 "PU16",Register Card Frame).
4. Alarm Criteria
Open the Alarm Criteria register card.
Make the settings according to the planning documentation and confirm with Apply
(see Section 5.3.3 "PU16",Register Card Alarm Criteria).
5. Synchronization and Sa-Bit Control
Open the Clock Control register card.
Make the settings according to the planning documentation and confirm with Apply
(see Section 5.3.3 "PU16",Register Card Clock Control).
6. Port Initialization
Open the General register card.
Set State to Active and confirm with Apply (see Section 5.3.3 "PU16",Register
Card General).
7. Configuration Backup
The set configuration data should be backed up via the backup function of the ACI
(see the User Manual AccessIntegrator ACI DM version V8.2, UMN:ADMN).
A50010-A3-C800-5-7619 93
User Manual
UMN CMXC
4.3.8 Creating the Connections
The creating of cross connection is described in detail on Section 5.4. In this section only
the sequence of the procedures and the associated settings are described in form of a
table.
You will find the procedures for opening any dialog in Section 5.4.
4.3.8.1 General
Through connection of an unframed 2Mbit/s connection is only possible between EPP2
or EPPM2/8 functional units which have been configured as unframed beforehand.
A framed 2Mbit/s connection is only possible between EPP2 or EPPM2/8 functional unit
which have been configured as framed beforehand.
Unidirectional connections can only be set up between TPs which have been configured
as such. The same applies to bidirectional connections. Here the associated TPs must
be configured as bidirectional TPs.
Connections at the 64kbit/s level can only be switched by the BPX64. Here it is neces-
sary that a connection between the EPP2 functional unit and the IPMB64/2 functional
unit of a 2Mbit/s port is set up via the BPX2 cross connect. This connection must always
be a bidirectional connection.
Path segment protection can be set up for connections at the 2Mbit/s level (unidirectional
or bidirectional) and connections for the transition to the BPX64 cross connect. If a con-
nection is set up between a EPP2 and a IPM64/2 with path segment protection, then the
TP(A) must always be the IPMB64/2 and the TP(B) the EPP2. The TP(B) can be an ar-
bitrary EPP2 functional unit. The selection of termination points TP(A), TP(B) and TP(B)
for connections at the 2Mbit/s level must be based on the application.
A time slot cannot be switched if the PU16 module associated with the TP is not
equipped. Conversely, deleting connections is not possible if the associated PU16 is not
inserted.
A summary of switchable connections on BPX2 you will find in Section 5.4.1.1.
4.3.8.2 Creating the Cross Connection
2 Mbit/s
Sequence Operating Task required Settings see Section
1. Configuring the required PU16 ports Frame: framed
State: active
5.3.3 and
5.4.1.1
2. Filter setting All and FG-FE or Module-Port-TS 5.4.1.1
3. Creating the 2-Mbit/s connection FG-FE or Module-Port-TS according to your
planning documentation
5.4.1.1
4. Activating the 2-Mbit/s connection Selecting the connection and activating via button
Connect or via a time schedule.
5.4.1.1
5. Creating a protection path (option) Path protection points, path protection mode and
switchover criteria according to your planning
documentation
5.4.1.1
Tab. 4.4 Sequence for Creating 2-Mbit/s Cross Connections
94 A50010-A3-C800-5-7619
64 kbit/s
8 kbit/s
6. Activating the protection path Selecting the connection and activating via button
Connect or via a time schedule
5.4.1.1
7. Backup of the configuration data according to the Backup function of the ACI UMN:ADMN ACI DM
(see Section 1.3)
Tab. 4.4 Sequence for Creating 2-Mbit/s Cross Connections (Cont.)
State: active
5.3.3 and
5.4.2.1
5.4.2.1
Connect
5.4.2.1
5. Creating the 64-kbit/s connection FG-FE or Module-Port-TS according to your
5.4.2.1
6. Activating the 64-kbit/s connection Selecting the connection and activating via button
5.4.2.1
(see Section 1.3)
Tab. 4.5 Sequence for Creating 64-kbit/s Cross Connections
State: active
5.3.3 and
5.4.3.1
5.4.3.1
Connect
5.4.3.1
5.4.3.1
Connect
5.4.3.1
5.4.3.1
Tab. 4.6 Sequence for Creating 8-kbit/s Cross Connections
A50010-A3-C800-5-7619 95
User Manual
UMN CMXC
Conferences
5.4.3.1
(see Section 1.3)
Tab. 4.6 Sequence for Creating 8-kbit/s Cross Connections (Cont.)
State: active
5.3.3 and
5.4.4.1
5.4.4.1
Connect
5.4.4.1
5. Creating the conferences Conference type, port, subscriber and time slot
according to your planning documentation
5.4.4.1
(see Section 1.3)
Tab. 4.7 Sequence for Creating Conferences
96 A50010-A3-C800-5-7619
5 Operation
5.1 Introduction
5.1.1 Notes for Working
Each operating task for the system module CMXC is described in a separate main sec-
tion or in the Operating Manual of the Access Integrator (ACI), see Tab. 5.1. The first
information given in the main sections is that required for a general understanding of the
operating task. The operating tasks are then described in subsections. These contain
the required operating procedure in the form of a numbered list to be worked through
step-by-step. For each operating task a dialog window is shown as an example. Tables
explain the setting options for the individual parameters and relate these to the network
elements.
The requirement for all operating procedures is that the AccessIntegrator or the Local
Craft Terminal (LCT) and the CMXC are already installed, connected and proceeds
without errors. Procedures for rectifying errors are described in Section Maintenance
(see Section 6).
Inside the operation procedure, starting the ACI functions or opening the dialog are de-
scribed via the main menu, because this task always can be used. The menu bar, con-
text sensitive menus or key combinations can be used alternatively. For example for
this, see User Manual AccessIntegrator, UMN:OMN (see Section 1.3 "Additional Docu-
mentation").
This manual describes the operation tasks for AccessIntegrator ACI DM software up
version 8.2.
5.1.2 Overview of Operating Functions
This chapter provides an overview of all functions that can be performed in AccessInte-
grator. The table below lists the individual functions available under the ACI main menu.
In the case of NE-specific functions you find a reference to the section in which they are
described in detail. For all other tasks you are referred to the ACI manual OMN.
The LCT column indicates whether the function can also be performed using an LCT.
i
A general knowledge of the structure and functioning of the CMXC, plus the use and
functions of the AccessIntegrators graphical user interface, are prerequisites for work-
ing with this manual.
A50010-A3-C800-5-7619 97
User Manual
UMN CMXC
AccessIntegrator Main Menu LCT Function Manual/ection
File Print Preview yes Print preview for active window
Print... yes Opening printer dialog (NT)
Network Editor
Creating a network map

Updating the network map
UMN:OMN
1)
Exit yes Exiting ACI client
View Toolbar
Status Bar
yes
yes
Showing/hiding
Network Map (TOP) Opening network map UMN:OMN
Parent Network Map Opening the parent map window
DCN Port View yes Opening DCN Port View
Opening DCN View (port 1... 64)
OS Tree Opening view with external OS
Equipment View
Functional View
yes
yes
Opening Equipment View
Opening Functional View
SNMP NT List not relevant
NE in DCN View
NE in Network Map
Opens the DCN View for an NE

Opens the map window for an NE
UMN:OMN
Service Network Map Opening the map window for service
networks
Zoom 200...10%
Zoom in/Zoom out
User defined...
yes Zooming the display
(all views)
Find NE... yes Searching for an NE in the access
network
Connections... Displaying connections
Setting up connections
(in network map - editor mode)
Time-scheduled Jobs... yes Displaying, modifying, deleting time-
scheduled jobs
Properties... yes Displaying name/description for
subnetwork/shelf/NE/module/note/label
Editing name/description for
subnetwork/shelf/NE/module/note/label
(in editor mode)
Configu-
ration
NE Configuration General NE Parameters...
User Data...
yes
yes
Configuring general NE parameters
Displaying/modifying customer data
5.3
4.3.5.2
SNMP Settings... yes Configuring SNMP parameters not relevant
NE Status... Displaying/modifying NE status 4.3.5.2
Cross Connect... yes Creating/deleting CCs 5.4
1) UMN:OMN and UMN:ADMN mean the User Manual Accessintegrator ACI DM, see Section 1.3
Numbers (e.g. 2) name the section in this manual
Tab. 5.1 Overview of Functions
98 A50010-A3-C800-5-7619
Configu-
ration
NE Configuration V5 Interface... yes Configuring, modifying, deleting a V5.x
interface (V5.1, V5.2, V5C)
not relevant
Frame Relay... Not relevant to ACI DM
Insert SNMP Network
Element...
yes Inserting a new SNMP NE
Software Management APS Management... Managing S-APS versions:
Inserting a new S-APS
Removing an S-APS
Checking the S-APS in network
UMN:OMN
Changing the addressing mode
yes
Starting a SW download:
For a complete AN
For NEs/modules in single mode
For NEs in broadcast mode
For a new NE
As a time-scheduled job
SW Download with LCT
UMN:OMN/4.3.5
Parameter Download... Not relevant to ACI DM not relevant
NE Backup...
NE Restore...
yes
yes
NE configuration data:
Backup (NE ACI)
Restore (ACI NE)
UMN:ADMN
Network Configuration Route Management...
Modifying route mgt. properties

Displaying network resources
Displaying state information
Displaying SNC data
Exporting the route list
Searching of routes
UMN:OMN
SNC Management...
Modifying SNC mgt. properties

Creating new SNC
Planning a SNC for later activation
Deleting a SNC
Searching for SNCs
Displaying appropriate SNC IDs
Extending a SNC
Reducing a SNC
Modifying variable SNC data
Displaying route data
Deleting a subscriber assignment
SCN Log Administration.
SCN Log Display...
Service Network Overview.
Administering log files

Displaying log files
Displaying service connections
Tab. 5.1 Overview of Functions (Cont.)
A50010-A3-C800-5-7619 99
User Manual
UMN CMXC
Fault Alarm List...
Alarm Status...
Alarm Counter...
Alarm Configuration...
Alarm Acknowledge
Alarm Color Setting...
yes
yes
yes
yes
Opening the alarm list

Opening the alarm status window
Displaying alarm counters
Configuring alarms
Acknowledging alarms
Defining alarm colors
Alarm Log Display...
Alarm Log Administration..
yes
yes
Administering log files:
Creating
Starting/stopping
Configuring parameters
Deleting
Displaying
Alarm Severity Configura-
tion
external Alarm configura-
tion
not relevant
Event Log Display...
Event Log Administration..

Creating
Starting/stopping
Deleting
Displaying
UMN:OMN
Mea-
sure-
ment
Battery Test... yes Check battery
Activate boost charge mode
Reset battery performance data
not relevant
Traffic... Not relevant to ACI DM
Performance Log Display...
Log Administration...
yes
yes
Creating
Starting/stopping
Deleting
Displaying
UMN:OMN
Performance Data...
Configuration...
Scheduled Services...
yes
yes
Displaying quality data

Configuring quality data
Time jobs for quality data
Management... Administer the performance data of ele-
ments present in the network
Data Displaying quality data
Configuration... Configuring quality data
Configure Threshold Pro-
file...

100 A50010-A3-C800-5-7619
Mea-
sure-
ment
Sheduled Services... Time jobs for quality data UMN:OMN
Subscriber Line Test Log Display...

Creating
Starting/stopping
Deleting
Displaying
not relevant
Subscriber Line Test Data.. yes Displaying test results of an automatic
line test
Configure Automatic Test.. yes Configuring/starting an
automatic line test
Configure Manual Test... yes Starting the manual line test
Line test via SNMP API interface
Measurement Points Log Display...

Creating
Starting/stopping
Deleting
Displaying
UMN:OMN
Measurement Data...
Configuration...
yes
yes
Displaying NE measurement data
Configuring the threshold values
Security Domain Administration... Administering user related domains:
Creating
Deleting
Modifying
Showing domains
UMN:ADMN
Add/Remove NEs...
View Domain Mappings...
Permission Administration Modifying the function range for an
ACI permission class
Exporting the settings
External Manager Display... Defining user rights for external
operating systems
F-Port Access
Management...
Administering passwords in SISA
nodes for F-Port access
A50010-A3-C800-5-7619 101
User Manual
UMN CMXC
Utilities Inventory Data Retrieval Equipment Data... yes Displaying data for individual NEs:
Inventory data
Label data
Modification information
Reference list
UMN:OMN
Store Inventory Data... Storing data into a file:
Starting data retrieval
Canceling data retrieval
NE Upload Configuration Parameter...
Log file Data..
for service
personal only!
Trace Error Log...
Diagnostic Information...
Mass Provisioning Mass Provisioning from File

Upload Configuration...
Download Configuration...
UMN:OMN
Migration Export
Import
Opening the dialog foe export

Opening the dialog for import
QD2 Telegram Trace... yes Logging QD2 telegrams
Consistency Check... yes Consistency check between ACI
database and NE
Media Interface Media Configuration...
Media Event List...
yes
yes
Configuring the media interface (MIF)
Displaying configured events
Alarm Media Configuration.
Disconn. NEs Media Conf..
yes
yes
Selecting alarms
Selecting NEs to be signaled
Maintenance Manual... Displaying/modifying the installation
path for the maintenance manual
Self Test Script*) For service personnel only!
not relevant
DDE*) For service personnel only!
Scripting Execute Script*)
Stop Scripting*)
*) only available after
installation of SNMP script
support
yes
yes
Starting/Executing/Ending the Script
Support Tool for Packet Hub configura-
tion
Options View Options... yes General settings for the graphical repre-
sentation of the network (all views)
UMN:OMN
Load/Save
Window Layout Set...
Network Options...
yes
yes
yes
Loading/saving user-defined
window settings
Modifying the interface parameters for
Startup phases and operation
Alarm supervision
Confugure Log FetchSize Defining the fatch size of alarm logs
102 A50010-A3-C800-5-7619
5.1.3 Overview of Function Group
Structure and function of the system module CMXC are described in Sections 2.2 and
3. For equipping the shelf, see Section 3.2.1.
5.1.3.1 Network Elements and subordinated Function Groups
The CMXC includes the following network elements, see Tab. 5.2.
Options Network Options... yes Modifying the interface parameters for
Startup phases and operation
Alarm supervision
UMN:OMN
Fault Notepad Options... Opens the alarm notepad dialog
Auditing Configuration... yes Testing the database occupancy UMN:ADMN
System Module/
Network Terminal
Network Element Function Group Subordinated Hardware
CMXC SISA-V/LMXV2 SISA0 SUE-E
CMXC SISA0
PET
BPX2
BPX64
IPMB64/2
IPMB8k/64
EPPM2/8
SPBX
ICBA
CUC
ICBD
IIF64
EPP2 PU16
ASA-K SISA0
MEL
SUE-E
Tab. 5.2 Network Element CMXC and its associated Function Groups
Function Group Function
BPX2 Bottom Path Connection 2 Mbit/s
BPX64 Bottom Path Connection 64 kbit/s
EPP2 Electrical Plesiochronous Port 2 Mbit/s
EPPM2/8 Electrical Plesiochronous Multiplex Port 2/8 Mbit/S
Tab. 5.3 Name of the Function Groups
A50010-A3-C800-5-7619 103
User Manual
UMN CMXC
ICBA Internal Conference Block Analog
ICBD Internal Conference Block Digital
IIF64 Internal Interface 64 kbit/s
IPMB64/2 Internal Plesiochronous Multiplex Block 64 bit/s/2 Mbit/s
IPMB8k/64 Internal Plesiochronous Multiplex Block 8 bit/s/64 bit/s
MEL Message Input (digital input group with 32 Bit)
PET Plesiochronous Equipment Timing
SISA0 SISA-0 (Management of the QD2 interface)
Function Group Function
Tab. 5.3 Name of the Function Groups (Cont.)
104 A50010-A3-C800-5-7619
5.1.4 Network Management
Fig. 5.1 illustrates the basic layout of the QD2 structure for the control and monitoring
of the ONU and OLTs.
Fig. 5.1 QD2 Structure (Example)
ONU
Central
alarm supervision
QD2 Interface
SISA-K
OS
SISA-K
SISA-K SISA-K
Domain
LCT
Domain
LCT
Domain
LCT
Domain
LCT
West
South
East
AMT-1
AMT-2
Leased Lines 64K
LCT
ONU
ONU
ONU
ONU
ONU
ONU
ONU
ONU
ONU
Domainmanager
ACI DM
SISA-
GK
SISA-
GK
SISA-
GK
SISA-
GK
A50010-A3-C800-5-7619 105
User Manual
UMN CMXC
5.1.5 SISA Communication Network
The SISA communication network (DCN) enables centralized operation and mainte-
nance of the system.
The SISA network has a uniform basic pattern and possesses a serial data bus, to which
a maximum of 30
1
) subscribers can be connected, see Fig. 5.2.
Here, one subscriber functions as a master, whilst the others are assigned to him as
slaves. By means of the cascading of this basic pattern, hierarchically-arranged net-
works with a number of levels can be created. Generally speaking, data traffic moves in
both transport directions, both up and down the hierarchy.
1) Up to 254 subscribers can be connected at the lowest hierarchical level.
Fig. 5.2 SISA Structure of FastLink System
For access to the individual network elements, virtual SISA concentrators (SISA-V) are
implemented. They simulate the logical tree structure within the Access Networks (AN),
(1) (254)
(30)
(1)
(1) (30)
ML-OS
SISA-GK
1 to n
SISA-V NE NE/SISA-V
SISA-V NE
NE
Plane n
Plane 2
(Addr. 1)
Plane 3
(Addr. 1-1)
Plane 4
(Addr. 1-1-2)
Planes 5 to (n-2)
Plane (n-1)
(1) Rack 1
(2)
SISA-V
(30) Rack 30
SISA-V
NE
NE/SISA-V
SISA-K
(1)
Plane 1
106 A50010-A3-C800-5-7619
thus enabling selective information exchange with the individual NEs, as well as with
their subordinate units.
To this end, the network elements have the following properties:
Each NE has a specific TMN address.
This address is set with the help of backplane coding (effected by plug-in place) and
via DIL address switches (see Section 3.2.2).
In the case of a faulty connection to the OS, the NEs can also be operated via the
F interface of the assigned monitoring group.
The NE default values are so set, that upon commissioning, a connection to the hi-
erarchically superordinate TMN component will always be established.
The NE automatically recognizes interface and bit rate, and adjusts itself in line with
these.
Since the individual NEs, whether related to the plug-in unit or the system as a whole,
can exist in multiple form, identification calls for the use of a structured SISA address,
see Fig. 5.3. Assignment of the addresses is via appropriate reference lists. In informa-
tion exchanges FG conforms to second to the last, and FE the last position of the SISA
address.
Fig. 5.3 Example of a SUE-E Address
5.1.6 Interfaces used for Operating Purposes
If the operation system is set up as a multiuser system, the client PC is linked to the
server PC via a LAN. The server PC is connected via the SISA-DCN (Data Connection
Network) to the QD2 interface on the highest SISA concentrator in the SISA hierarchy
(e.g. SISA-GK). In the case of a single user system, a single PC - which incorporates
both the server and client functions - is linked via the DCN to the QD2 interface on the
AN. The AccessIntegrator (ACI) is used to manage all the network elements which are
subordinate to this SISA concentrator in the SISA hierarchy.
In addition, for some of the operating tasks (primarily commissioning and maintenance)
it is possible to use an LCT. Using a connecting cable for F-interfaces, this is connected
to the F-interface of the highest SISA concentrator in the SISA hierarchy, or directly to
the appropriate F-interface on the system module, see Tab. 5.4.
The interfaces between CMXC and the operating equipment are as follows:
DCN-PORT
(Rack group)
SISA-GK SISA-V
(OLT, 1st rack)
SISA-V/LMX
(OLT rack)
SISA-V/LMX
(ONU)
SISA-0
(ASA-K)
SISA-V/LMX
(upper shelf)
SISA address
SUE-E: 1 1 2 1 7 8 1 - - - - - -
FG-No. FE
Sub address
: 244 - 01
A50010-A3-C800-5-7619 107
User Manual
UMN CMXC
5.1.7 Operation Modes of SUE-E
The SUE-E supports two modes of QD2 operation. The operation mode can be selected
via jumper X11 on the SUE-E board. In both modes, the SUE-E behaves in a strictly hi-
erarchical QD2 network as virtual SISA concentrator, i.e. it has its own SISA address,
and is approachable via this address by functions of the application protocol AWP01.
There are following QD2 operation modes:
QD2-operation mode 1: with QD2 interface as QD2 slave
QD2-operation mode 2: with Ethernet interface as Ethernet slave
In QD2-operation mode 1 as QD2 slave, the management connection is ensured via
QD2 also with redundant port. The integration of TMN-access can be done in FMX2R3.2
system by direct ACI connection to the SUE-E or via SISA-GK/E. Fig. 5.4 shows the use
case with a direct connection to the SUE-E.
Fig. 5.4 QD2-Operatiion Mode 1: Slave with QD2 Interface
In QD2-operation mode 2 as Ethernet slave, the QD2-management connection is pro-
vided by an Ethernet tunnel (QD2 via TCP/IP) on the FMX2R3.2 shelf backplane. The
QD2-slave port 1 is used as Ethernet interface. The redundant QD2 slave 2 is turned off
in this case to avoid that there are two QD2 masters in the network. Fig. 5.5 shows the
connections of SUE-E in QD2-operating mode 2.
Shelf System Module F/QD2 Interface on
plug-in unit
Plug-in Place
on the shelf
F Connecting Line
SNUS CMXC SUE-E 1 Recommendation:
LCT connecting cable
S42023-A877-S100
Tab. 5.4 F Interface of the System Modules
SUE-E
ACI
RS485
ACI
redundant
V.28
RS485
RS485
SUE-E
SISA-
Service
PC
RS485
NE
RS485
not used in this configuration
Ethernet
108 A50010-A3-C800-5-7619
Fig. 5.5 QD2 Operation Mode 2: Slave with Ethernet Interface
Since the original QD2 protocol of the OSI layers "physical layer" (RS485), "data link lay-
er" (HDLC/UNC), "network layer" (VMP01) and "application layer" (AWP01) is imple-
mented, the SUE-E terminates the RS485 and HDLC/UNC, and encapsulates network
and application layer via TCP/IP and Ethernet (IEEE 802.3). This allows the transport of
QD2 protocol over commercial IP equipment (see Fig. 5.6).
Fig. 5.6 QD2 Tunnel via TCP/IP
Now, the SISA-GK/E in front of a shelf is not required for TCP/IP based DCN connection
anymore, because a TCP/IP-based DCN server for the QD2 protocol is available with
ACI and SUE-Es operation mode 2 (Ethernet master).
5.2 Software Management
The software management of the AccessIntegrator supports following operation tasks:
APS Management
Backup and restore of network element data.
The functions of the software management are described in detail in User manual
AccessIntegrator, UMN:OMN (see Section 1.3 "Additional Documentation").
In this section, an overview of the required load files and the correlation between load
files and any units are given.
Load Files
Tab. 5.5 show the correlation between the load files and the modules inside a CMXC
System Module.
SUE-E
Ethernet
V.28
RS485
RS485
SUE-E
Ethernet
NE
RS485
not used in this configuration
RS485
ACI
> V6.1
SISA-
Service-
PC
Management
network
Ethernet
TCP
HDLC
VMP01
RS485
IP
Ethernet
AWP01
VMP01
AWP01
A50010-A3-C800-5-7619 109
User Manual
UMN CMXC
For SUE-E, a software download over the WAN/LAN network is possible in the QD2 op-
erating mode 2, see Controls of the SUE-E. The Ethernet configuration must be per-
formed in the following way:
1. Switch to QD2 operating mode 2 via jumper X11 on SUE-E board.
2. Connect LCT via F-port to SUE-E, setup the Ethernet configuration.
3. Restart the SUE-E, and connect the OS via Ethernet port to the SUE-E.
4. SW download can be started.
A SW download via F-port with LCT is also possible, but takes much more time. An up-
date via FTP is not supported.
5.3 Configuration Management
All the network elements are factory preset (default setting) to guarantee their function-
ing. However, the operator may modify the settings to meet the users requirements.
This section explains the setting options for the network elements. Tab. 5.6 provides an
overview of which network element parameters can be configured. A full description is
contained in the sections quoted.
Plug-in Unit Name of the Load File Remark
SUE-E SEBL0R0.nnn
1)
SUE-E SEBL0R0.nnn with F port protection
CUC CUCL0R0.nnn
PU16 PU6L0R0.nnn
1) nnn: Version (e.g. 102)
Tab. 5.5 Correlation between Unit and Load Files
i
Please backup the set configuration data via the backup function of the ACI (see User
Manual AccessIntegrator ACI DM, UMN:ADMN).
110 A50010-A3-C800-5-7619
5.3.1 SISA-V/LMXV2
Configuring SISA Concentrator
1. Select the icon for the SISA concentrator in the DCN Tree and open the Equipment
view.
2. Select the required module and choose in the main menu the menu item
Configuration NE Configuration General NE Parameters... to open the dia-
log General NE Parameters - SISA-V/LMXV2#...: SUE-E#....
3. On the register card Interface, change the bit rate, see Fig. 5.7.
4. Confirm the with Apply.
Register Card Interface
Fig. 5.7 SUE-E Register Card Interface
Network
Element
Plug-in Unit Register card
(Function Group)
Settings (Selection) Sect.
SISA-V/LMXV2 SUE-E Interface Bit rate on the master port 5.3.1
ASA-K SUE-E (MEL1 to MEL32) For configuration of the alarm inputs, see User manual ACI DM V8.2,
UMN:OMN, Section 6.5.4.
CMXC CUC Clock synchronization
ECC Alarm Criteria
Frame
ECC Mode
General
Clock source
Alarm Din
CAS,
Operation mode of the ECC channels
Forced activation of the CUC, port state
5.3.2
5.3.2
5.3.2
5.3.2
5.3.2
PU16 Loops
Alarm Criteria
Frame
Clock control
General
Loops
BER-5/5, N bit, Nk bit
CRC4 frame, B1sout, B1mout
Clock source control via Sa bits
Port state
5.3.3
5.3.3
5.3.3
5.3.3
5.3.3
Tab. 5.6 Configuration Parameters for the Network Elements
i
Use the Get button to update the display.
A50010-A3-C800-5-7619 111
User Manual
UMN CMXC
5.3.2 CUC
The following settings are possible:
Synchronous clock source (register card Clock Sync.)
Alarm criteria of the ECC (register card ECC Alarm Criteria)
frame structure (register card Frame)
Operation mode of the ECC (register card ECC Mode)
General settings (register card General).
In addition, the current states will be displayed for ECC and PCI ports register cards
ECC Status and PCI Status).
Configuring the Central Unit CUC
1. Select the icon for the NE CMXC and open Equipment View.
2. Select the central unit and choose in the main menu the menu item Configuration
NE Configuration General NE Parameters...to open the dialog General NE
Parameters: CMXC#...:CUC#....
3. Open the required register card and change the parameter.
4. Confirm then with Apply.
Parameter valid Values Default Explanation
Bitrate 0.6 kbit/s,
1.2 kbit/s,
19.2 kbit/s,
64 kbit/s,
128 kbit/s
x
Setting made on the master port, slave ports
automatically detect the bit rate set on the
master port.
i
112 A50010-A3-C800-5-7619
Register Card Clock sync.
Fig. 5.8 CUC Register Card for Setting the Clock Synchronization
Column valid Values Explanation
No. 1 to 8 Sequential numbers of the clock sources, arranged in order of
their priority. It is possible to specify one clock synchronization
source and up to seven reserve clock sources.
Clock Source
T3an,
Port 01 to Port 07,
Internal
Clock source freely selectable via Insert according to planning
document.:
central clock according to ITU-T G.703,
synchronization clock from 2Mbit/s port of the PU16 (LSI1 to
LSI7),
internal clock
Module According to planning
document
Displaying of the PU16, from which the clock source is derived,
as selected via Insert.
Channel According to planning
document
Displaying is equal with the port, from which the clock source is
derived, as selected via Insert
Tab. 5.7 List Entries in the Clock Priority List
A50010-A3-C800-5-7619 113
User Manual
UMN CMXC
Register Card ECC Alarm Criteria
Fig. 5.9 CUC Register Card for Configuring the Alarm Supervision
Button Meaning
Insert Opens the window Insert Clock Source, used to insert additional clock sources.
Change Opens the window Change Clock source, used to change the parameters for the
selected clock source.
Delete Deletes the selected clock source.
Tab. 5.8 Explanation of the Buttons in the CUC Register Card Clock sync.
Parameter valid Values Explanation
Alarm Dan 1
to
Alarm Dan 4
on,
off
Default setting, alarms are generated if the criterion is fulfilled,
alarms are not generated
Tab. 5.9 Explanation of the CUC Register Card ECC Alarm Criteria
114 A50010-A3-C800-5-7619
Register Card Frame
Fig. 5.10 CUC Register Card for Configuring the Ports
Port 01 CAS to
Port 48 CAS
on,
off
External PCI Port not used at the time
Tab. 5.10 Explanation of the CUC Register Card Frame
A50010-A3-C800-5-7619 115
User Manual
UMN CMXC
Register Card ECC Mode
Fig. 5.11 CUC Register Card for Setting the ECC Operation Mode
AMOD ECC1
AMOD ECC2
Synchron,
Asynchron
ECC channels for remote monitoring::
ECC1 and ECC2 can be used synronous (with clock line, 64
kbit/s) or asynchronous (without clock line, 9,6 kbit/s). ECC3
and ECC4 can be used. asynchronous only.
AMOD ECC3
AMOD ECC 4
Asynchron
Tab. 5.11 Explanation of the CUC Register Card ECC Mode
116 A50010-A3-C800-5-7619
Register Card General
Fig. 5.12 CUC Register Card for Activation/Deactivation of the ports
Activation Forced Activate Unit 1,
Forced Activate Unit 2
Unit CUC1 or CUC2 can be forced activated. The
other unit is in standby mode and will be active, if
a active unit failures.
Activation ZA(A) With A alarm,
With S alarm
A alarm is connected with break contact,
S alarm is connected with break contact.
External
PCI-Ports
Port 1 Active
to
Port 4 Active
not used at the time
ECC
Ports
Port 1 Active
to
Port 4 Active
on,
off
ECC ports can be activated or deactivated. gener-
ated alarms are suppressed.
Tab. 5.12 Explanation of the CUC Register Card General
A50010-A3-C800-5-7619 117
User Manual
UMN CMXC
Register Card ECC Status
Fig. 5.13 CUC Register Card for Displaying the State of the ECC Ports
These register card shows the current state of the ECC ports. The states can be
changed of the following register cards:
5.3.3 PU16
The following settings are possible:
Operator loops (register card Loops)
Alarm criteria (register card Alarm Criteria)
Frame structure (register card Frame)
Sa-Bit control (register card Clock control)
State (register card General).
In addition, the current state of all ports will be displayed (register card Status View).
Configuring the Unit PU16
1. Select the icon for the NE CMXC and open the Equipment View.
2. Select the PU16 and choose in the main menu the menu item Configuration NE
Configuration General NE Parameters...to open the dialog General NE Param-
eters: CMXC#...:PU16#....
3. Select the port must be configured from the Drop down list.
4. Open the required register card and change the parameter.
Parameter Changings are possible on
Status Register card General, in the field ECC-Ports
Alarm Register card ECC Alarm Criteria in the field Report Alarm Dan
Sync. Register card ECC Mode in the field AMOD ECC1 to AMOD ECC4
Tab. 5.13 Explanation of the CUC Register Card ECC Status
118 A50010-A3-C800-5-7619
5. Confirm then with Apply.
Register Card Loops
Fig. 5.14 PU16 Register Card for setting the Operator Loop
i
Loops at
F1-Port
No Loop,
Local Loop,
Remote Loop
x Normal mode,
local loop on selected F1 port (transmission port will
be connected to the receive port in CMXC),
remote loop on selected F1 port (receive port will be
connected to the transmission port inside the ex-
change cabling).
Loops can be switched for all E1 ports which are con-
figured as a bidirectionally Termination Point. If a loop
is activated, AIS is sent and the a accordingly LED is
lit (see Section 3.4.2.
Tab. 5.14 Explanation of the PU16 Register Card General
A50010-A3-C800-5-7619 119
User Manual
UMN CMXC
Register Card Alarm Criteria
Fig. 5.15 PU16 Register Card for Setting the Alarm Criteria
Register Card Frame
Fig. 5.16 PU16 Register Card for Setting the Frame structure
BER-5/6 leads
to B-Alarm
on,
off x
Bit rate 10
-5
(CRC4 off) or 10
-6
(CRC4 on) leads to B
alarm.
Show Nk-Bit
Alarm
on,
off x
Nk-Bit Alarm triggers B alarm (if CAS for 2Mbit/s port is
configured).
Show N-Bit
Alarm
on,
off
x N-Bit Alarm triggers B alarm (Sa4 bit in receive message
word of the 2Mbit(s signal).
Tab. 5.15 Explanation of the Pu16 Register Card Alarm Criteria
120 A50010-A3-C800-5-7619
Register Card Clock Control
Fig. 5.17 PU16 Register Card for Setting the Sa Bit Control
Parameter valid values Default Explanation
CRC4 CRC4 ON,
CRC4 OFF x
CRC4 frame according to ITU-T GF.704
Frame Framed,
Unframed
x 2-Mbit/s signaling frame is framed
B1sab B1sab ON,
B1sab OFF
x Bit 1 can be used as a frame synchronous word.
Setting is only possible, if CRC4 procedure is set to
inactive.
B1mab B1mab ON,
B1mab OFF
x Bit 1 can be used as a message word.
Setting is only possible, if CRC4 procedure is set to
inactive.
Tab. 5.16 Explanation of the PU16 Register Card Frame
Sa-Bit None,
Sa4,
Sa5,
Sa6,
sa7,
Sa8
x If the synchronous clock is one of the F1ports, then one of
its bits can be used to switch over the current synchroniza-
tion clock source to a reserve clock source.
Mode Sa-Bit Low,
Sa-Bit High
x Switch over on L level of the bit,
Switch over on H level of the bit,
only possible, if any Sa bit is set.
Tab. 5.17 Explanation of the PU16 Register Card Clock Control
A50010-A3-C800-5-7619 121
User Manual
UMN CMXC
Register Card General
Fig. 5.18 PU16 Register Card for Setting the Operation Mode
State Active, x
Passive Port is not used, alarm messages are suppressed.
AIS is sent from the deactivated port..
(no other setting are possible for this port).
Tristate Port is not used, alarm messages are suppressed.
The driver from the deactivated port is switched in the high-
impedance state.
(no other setting are possible for this port).
Tab. 5.18 Explanation of the PU16 Register Card General
122 A50010-A3-C800-5-7619
Register Card Status View
Fig. 5.19 PU16 Register Card for Displaying the State off all Ports
These register card shows the current state of the 16 ports. The states can be changed
of the following register cards:
Parameter Changings are possible on
State Register card General, in field State
Loop Register card Loops in field Loops at F1-Port
Frame Register card Frame in field Frame
CRC4 Register card Frame in field CRC4
B1sab Register card Frame in field B1sab
B1mab Register card Frame in field B1mab
CAS Standard setting can not be changed.
Tab. 5.19 Explanation of the PU16 Register Card Status View
A50010-A3-C800-5-7619 123
User Manual
UMN CMXC
5.4 Crossconnection
This section describes the setting up changing and deleting of cross connections and
conferences through the system module CMXC
5.4.1 Crossconnections 2 Mbit/s
5.4.1.1 Creating
Fig. 5.20 Register Card Connections 2Mbit/s
Column Values Explanation
! Red dot Displayed in addition when the state is not connected or created.
ID Display field Number, defined by the system
From Display field Source endpoint of the crossconnection, consisting of port name#port
number:1 (e.g. EPP2#6:1); can be selected in the dialog Create: Cross
Connection - CMXC#...:CUC#..., see Fig. 5.22.
Tab. 5.20 Explanation of the Register Card Connections 2Mbit/s
124 A50010-A3-C800-5-7619
To Display field Destination endpoint of the crossconnection, consisting of port
name#port number:1 (e.g. EPP2#17:1); can be selected in the dialog
Create: Cross Connection - CMXC#...:CUC#..., see Fig. 5.22.
State
connected,
not connected,
created
Shows the current state of the crossconnection:
can be selected using the Connect button,
can be selected using the Disconnect button,
state after creating the cross connection
Type bi,
uni,
loopback
Transmission type, can be selected in the dialog
Protect Display field Displaying of the alternative destination (for bidirectional operation)/the
alternative source (for unidirectional operation), can be selected in the
dialog Create: Cross Connection - CMXC#...:CUC#....
Displaying of the operating state:
Automatic: (default after switchover to connected) switchover to
Standby or Active is performed automatically by evaluating certain
alarms.
Standby: standby circuit is not active (connection is by the main route,
or this setting has been forced using the Forced to SR button).
Active: standby circuit is active (connection via the main route is
disrupted, or this setting has been forced using the Forced to AR but-
ton).
ARS worked,
protected
Main route is activated,
Alternative Route is activated.
Time according to the
planning
document
Displaying the selected time order for switching the crossconnections,
can be selected in the dialog Cross Connection: Time Order,
see Fig. 5.23.
Flag S,
G
Flag for single selection,
Flag for multiple selection, can be selected in the dialog
nCC according to the
planning docu-
ment
Displaying the number of member of the group selection, can be select-
ed in the dialog Create: Cross Connection - CMXC#...:CUC#..., see
Fig. 5.22. A window with all connected time slots can be opened by
double-checking on the selected connection.
Button Meaning
Create Opens a dialog for creating cross connections, see Fig. 5.22
Connect Changes the current status of the selected cross connection to connected.
If the attempt is unsuccessful, a message appears.
(Mode can be changed automatically via time order).
Disconnect Changes the current status of the selected crossconnection to not connected.
Connections 2Mbit/s
Tab. 5.20 Explanation of the Register Card Connections 2Mbit/s
A50010-A3-C800-5-7619 125
User Manual
UMN CMXC
Setting up 2 Mbit/s Crossconnections
1. Select the NE and open the Equipment View.
2. Select the required unit PU16, see Section 5.3.3. Choose the following parameters:
3. Choose in the menu Configuration NE Configuration Cross Connect... to
open the register card Filter.
Select the setting All for the Radio button and FG-FE or Module - Port - TS for
the representation of Recources field, see Fig. 5.21.
Delete Deletes the selected crossconnection. It is then removed from the table.
Configure... Opens a dialog for modifying a selected cross connection (only time order can be
changed).
Protection... Opens a pop-up window with the following buttons:
Automatic: Switching back into the state Automatic, after an another state was
forced manually.
Manual: Manually switching over to the alternative route
Forced to AR: alternative routing is forced activated
Forced to SR: main route is forced activated
Protection criteria...: opens Fig. 5.24 for selecting the switching criteria.
Get Updates the display for the selected cross connection.
Button Meaning
Connections 2Mbit/s (Cont.)
Parameter Value Register Card Remark
Port from Drop down list Port Frame of the
PU16 unit
Selection must be done for each re-
quired port according to the planning
document. see Tab. 5.22 also.
Frame framed,
unframed
State active General of the
PU16 unit
i
If the parameter Representation of Resources: Module- Port-TS is set, the connec-
tions can be displayed directly on unit PU16. The complicated way via the FG can be
slipped.
126 A50010-A3-C800-5-7619
Fig. 5.21 Register Card for Setting Filter Parameter
4. Open the register card Connections 2Mbit/s. This contains an overview of all the
crossconnections which have been created, see Fig. 5.20.
5. Use the Create button to open the dialog Create: Cross Connection 2Mbit -
CMXC#...:CUC#..., see Fig. 5.22.
6. Choose the parameter from the Drop down list. Use OK to confirm. The selection
then appears in the list in Fig. 5.20.
7. Select the created crossconnections and use the Connect button to activate the
crossconnections or select a time order for the activation (dialog
Create: Cross Connection 2Mbit - CMXC#...:CUC#..., Time button).
8. Create a protection path (TP(B) in Fig. 5.22, if necessary, choose the protection
mode and use the Protection... button to define switching criteria.
9. Select the created cross connections and use the Connect button to activate the
cross connections or select a time order for the activation. The protection path then
is in the state ...(automatic).
10. Repeat the steps 4 to 9 to create other new cross connection, if necessary.
A50010-A3-C800-5-7619 127
User Manual
UMN CMXC
Fig. 5.22 Dialog for Creating Crossconnection 2 Mbit/s
(Example with Filter setting Representation of Resources: FG-FE)
Parameter Entry
Type Transmission type according the planning document, see Tab. 5.22:
bidirectional (default setting),
unidirectional,
loopback
Port TP(A)
Timeslot
Selection of the function group is dependent on the using according to the planning
document, see Tab. 5.22 and Tab. 5.23.
Selection must be 1 (* means: this time slot is already busy).
Port TP(B)
Timeslot
document, see Tab. 5.22 and Tab. 5.23.
Port TP(B)
Timeslot
When the operating mode is bidirectional (unidirectional), the alternative destination
(alternative source) can be entered here. Selection of the function group is depen-
dent on the using according to the planning document, see Tab. 5.22 and
Tab. 5.23.
Bandwidth
n x (64kbit/s)
Not relevant for 2 Mbit/s interface.
Distribution of
Timeslots:
Not relevant for 2 Mbit/s interface.
Create Not relevant for 2 Mbit/s interface.
Protection
mode
revertive: autom. switch back to main route, if the error is cleaned,
non-revertive: no autom. switch back to main route, if the error is cleaned.
128 A50010-A3-C800-5-7619
Fig. 5.23 Dialog for Setting the Time Order
Fig. 5.24 Dialog for Setting the Switching Criteria
Button Meaning
Time... Opens a dialog for setting time order, see Fig. 5.23.
Protection... Opens a dialog for setting switch criteria, see Fig. 5.24.
A50010-A3-C800-5-7619 129
User Manual
UMN CMXC
5.4.1.2 Modifying
Parameter valid Values Entry
Switching criteria Excessive BER-5/6,
AIS,
Trail Signal degrede
Switching over, if the bit rate is exceeded,
Switching over, if AIS is received,
Switching over by signal degrede
Error Seconds According to the
planning document
Fields for entry are only activated after the activation of the
field Trail Signal degrede.
Connections TP(A)* TP(B)* ** TP(B) Frame Direction
2Mbit/s-IF <--> 2Mbit/s-IF EPP2#x:1
EPP2#x:1
EPPM2/8#v:1...4
EPP2#y:1
EPPM2/8#v:1...4
EPPM2/8#v:1...4
EPP2#z:1
-
-
framed,
unframed
bidirectional,
unidirectional,
loopback
2Mbit/s-IF <--> connection field BPX64
1)
IPMB64/2#x:1
IPMB64/2#u:1
EPP2#x:1
EPPM2/8#v:1...4
EPP2#y:1
-
framed bidirectional
* TP(A) and TP(B) can be changed according to the table information.
** TP(B) not used for loopback.
u = 33...48 ; x, y, z = 1... 32
1) On connections with transition to connection field BPX64, the number of the FG IPMB64/2 is dependent on the associate TP,
see Tab. 5.23.
Tab. 5.22 Switchable Function Groups for 2Mbit/s Cross Connections
FE Number of the IPMB64/2 Associate TP
IPMB64/2#1 EPP2#1
IPMB64/2#2 EPP2#2
... ...
IPMB64/2#32 EPP2#32
IPMB64/2#33 EPPM2/8#1:1
IPMB64/2#34 EPPM2/8#1:2
IPMB64/2#35 EPPM2/8#1:3
IPMB64/2#36 EPPM2/8#1:4
IPMB64/2#37 EPPM2/8#2:1
... ...
IPMB64/2#48 EPPM2/8#4:4
Tab. 5.23 Assignment of IPMB64/2 to Associate TP
i
The modifying an existing cross connection with or without path protection is not possi-
ble (exception: time order). The cross connection only can be deleted and then it must
be new created (see Fig. 5.28).
130 A50010-A3-C800-5-7619
Modifying existing 2 Mbit/s Crossconnections
1. Select the NE.
2. Choose in the menu Configuration NE Configuration Cross Connect to open
the register card Filter.
Select the setting All for the Radio buttons and FG-FE or Module - Port - TS for
the representation of Recources field, see Fig. 5.21 or choose a specified filter
parameter.
crossconnections which have been created, see Fig. 5.20. This display is updated
by selecting Get.
4. Select the cross connection.
5. Use the Configure button to open the dialog Configure Cross Connections-
CMXC#...:CUC#.... Then use the Time... button to openthe dialog Cross
Connection: Time Order. Change the parameter and confirm with OK.
5.4.1.3 Deleting
Deleting the 2 Mbit/s Crossconnections
1. Select the NE.
parameter.
by selecting Get
4. Select the crossconnection which must be deleted and use the Delete button to de-
lete the connection.
i
Unlike a broken connection (status not connected) a deleted connection is removed
permanently from the database and the associated network elements.
A50010-A3-C800-5-7619 131
User Manual
UMN CMXC
5.4.2 Cross Connections 64 kbit/s
5.4.2.1 Creating
Fig. 5.25 Register Card Connections 64kbit/s
! Red dot
Black dot
Displayed in addition when the state is Not connected and Created.
Displayed in addition when the state is Connected.
From Display field Source endpoint of the crossconnection, consisting of port name#time
slot:port number (e.g. IPMB64/2#1:3); can be selected in the dialog
name#time slot:port number (e.g. IPMB64/2#2:2); can be selected in
the dialog Create: Cross Connection - CMXC#...:CUC#...,
see Fig. 5.26.
Tab. 5.24 Explanation of the Register Card Connections 64kbit/s
132 A50010-A3-C800-5-7619
Setting up 64 kbit/s Cross Connections
2. Select the required unit PU16. Choose the following parameters, see Section 5.3.3:
State
connected,
not connected,
created
Shows the current state of the crossconnection:
state after creating the cross connection.
Type bi,
uni,
loopback
Transmission type, can be selected in the dialog
Create: Cross Connection - CMXC#...:CUC#....
Protect Display field Not relevant for crossconnections 64kbit/s
ARS working Not relevant for crossconnections 64kbit/s
Time According to
the planning
document
Displaying the selected time order for switching the cross connections,
can be selected in the dialog Cross Connection: Time Order,
see Fig. 5.23.
Flag S,
G
Flag for multiple selection, can be selected in the dialog Create: Cross
A window displayed all associated time slots to this group is opened by
double clicking on the connection, see Fig. 5.27.
planning docu-
ment
ed in the dialog Create: Cross Connection - CMXC#...:CUC#...,
see Fig. 5.26. A window with all connected time slots can be opened by
double clicking on the selected connection.
Button Meaning
Create Opens a dialog for creating crossconnections, see Fig. 5.26
Connect Changes the current status of the selected cross connection to connected.
Configure... Opens a dialog for modifying a selected cross connection (only time order can be
changed).
Protection... Not relevant for crossconnections 64kbit/s
Get Updates the display for the selected crossconnection.
Connections 64kbit/s
Tab. 5.24 Explanation of the Register Card Connections 64kbit/s (Cont.)
A50010-A3-C800-5-7619 133
User Manual
UMN CMXC
5. Use the Create button to open the dialog Create: Cross Connection 2Mbit -
6. Select the parameter from the Drop down list:
Connect a required EPP2#n:1 (n = port number) with its associated IPMB64/2#n in
accordance with the planning documents (e.g. EPP2#7:1 with IPMB64/2#7:1 and
EPP2#5:1 with IPMB64/2#5:1).
7. Confirm with OK. The selection will then appear in the list in Fig. 5.20 (e.g. ID 1
and ID 2) Select the crossconnection and use the Connect button to activate the
cross connection.
8. Open the register card Connections 64kbit/s. This contains an overview of all the
cross connections which have been created, see Fig. 5.25.
9. Use the Create button to open the dialog Create: Cross Connection
- CMXC#...:CUC#..., see Fig. 5.26.
connect the required IPMB64/2 (Source From) configured in 2-Mbit/s dialog with
any IPMB64/2 (Destination To) configured in the same window in accordance with
the planning documents (e.g. IPMB64/2#1:3 with IPMB64/2#2:2).
11. Confirm with OK. The changes will then appear in the overview in Fig. 5.25. Select
the crossconnection and use the Connect button to activate the cross connection.
PU16 unit
Frame framed,
unframed
PU16 unit
i
tions can be displayed directly on unit PU16. The complicated way via the FG) can be
slipped (see Fig. 5.28).
134 A50010-A3-C800-5-7619
(Example with Filter setting Representation of Resources; FG-FE)
Parameter Entry
Type Transmission type according to the planning documents, see Tab. 5.26:
unidirectional,
loopback
Port TP(A)
Timeslot
document, see Tab. 5.26. (* means: this time slot is already busy).
Port TP(B)
Timeslot
document, see Tab. 5.26. (* means: this time slot is already busy).
Port TP(B) Not relevant for crossconnection 64kbit/s.
Bandwidth
n x (64kbit/s)
Selection of the number selected 64-kbit/s time slots assigned to a group of any port
(max. 32). Time slots which are busy cannot be selected.
Distribution of
Timeslots:
Consecutive,
Equidistant
Create Group: Time slots of any port can be created in group, see Fig. 5.27.
Multiple: Crossconnection is created for each time slot.
Protection
mode
Not relevant for cross connection 64kbit/s.
Button Meaning
Time... Opens a dialog for setting time order, see Fig. 5.23.
Protection... Not relevant for cross connection 64kbit/s.
A50010-A3-C800-5-7619 135
User Manual
UMN CMXC
Fig. 5.27 Displaying of the Time Slots assigned to a Group (Example)
Fig. 5.28 Dialog for Creating the Crossconnection 64 kbit/s (Example)
Connection TP(A)* TP(B)* ** Frame Direction
64kbit/s connection IPMB64/2#x:1... 31 IPMB64/2#y:1... 31 framed bidirectional,
unidirectional,
loopback
EOMC64 connection IPMB64/2#x:1 IIF64#y:1 framed bidirectional
64kbit/s <--> sub rate connection field SPPX IPMB64/2#x:1 IPMB6k/64#z:1 framed bidirectional
** TP(B) not used for loopback x = 1... 32; y = 1... 4, z = 1..60
Tab. 5.26 Switchable Function Groups for 64kbit/s Crossconnections
136 A50010-A3-C800-5-7619
5.4.2.2 Modifying
Modifying existing 64 kbit/s Cross Connections
1. Select the NE.
parameter.
by selecting Get.
4. Select the cross connection.
5. Use the Configure button to open the dialog Configure Cross Connections:
UMXC#...:CUC#.... Then use the Time... button to open the dialog Cross Con-
nection: Time Order. Change the parameter and confirm with OK.
5.4.2.3 Deleting
Deleting the 64 kbit/s Crossconnections
1. Select the NE.
parameter.
by selecting Get.
i
The modifying an existing crossconnection is not possible (exception: time order). The
cross connection only can be deleted and then it must be new created.
i
A50010-A3-C800-5-7619 137
User Manual
UMN CMXC
5.4.3 Cross Connections 8 kbit/s
5.4.3.1 Creating
Fig. 5.29 Register Card Connections 8kbit/s
! Red dot
Black dot
Displayed in addition when the state is Not connected.
Displayed in addition when the state is Connected.
From Display field Source endpoint of the crossconnection, consisting of port name#time
slot:port number (e.g. IPMB8k/64#1:27); can be selected in the dialog
Create: Cross Connection - CMXC#:CUC#..., see Fig. 5.26.
name#time slot:port number (e.g. IPMB8k/64#1:28); can be selected
in the dialog Create: Cross Connection - CMXC#..:CUC#...,
see Fig. 5.26.
State
connected,
not connected,
created
Shows the current state of the cross connection:
state after creating the cross connection.
Type bi, Transmission type
Protect - Not relevant for crossconnections 8kbit/s
ARS working Not relevant for crossconnections 8kbit/s
Time - Not relevant for crossconnections 8kbit/s
Flag S,
G
Flag for multiple selection, can be selected in the dialog Create: Cross
A window displayed all associated time slots to this group is opened by
double clicking on the connection.
planning docu-
ment
ed in the dialog Create: Cross Connection - CMXC#...:CUC#...,
see Fig. 5.26. A window with all connected time slots can be opened by
double clicking on the selected connection.
Tab. 5.27 Explanation of the Register Card Connections 8kbit/s
138 A50010-A3-C800-5-7619
Setting up 8 kbit/s Crossconnections
5. Use the Create button to open the dialog Create: Cross Connection -
Connect a required EPP2#n:1 (n = port number) with its associated IPMB64/2#n in
accordance with the planning documents (e.g. EPP2#7:1 with IPMB64/2#7:1 and
EPP2#5:1 with IPMB64/2#5:1).
7. Confirm with OK. The selection will then appear in the list in Fig. 5.20 (e.g. ID 1
and ID 2). Select the crossconnection and use the Connect button to activate the
cross connection.
Button Meaning
Create Opens a dialog for creating cross connections, see Fig. 5.26
Connect Changes the current status of the selected crossconnection to connected.
Configure... Opens a dialog for modifying a selected crossconnection (only time order can be
changed).
Protection... Not relevant for crossconnections 8kbit/s
Get Updates the display for the selected crossconnection.
Connections 8kbit/s
PU16 unit
Frame framed,
unframed
PU16 unit
i
A50010-A3-C800-5-7619 139
User Manual
UMN CMXC
cross connections which have been created, see Fig. 5.25.
9. Use the Create button to open the dialog Create: Cross Connection
- CMXC#...:CUC#..., see Fig. 5.26.
connect the required IPMB64/2 (Source From) configured in 2-Mbit/s dialog with
any IPMB64/2 (Destination To) configured in the same window in accordance with
the planning documents (e.g. IPMB64/2#1:3 with IPMB64/2#2:2).
the crossconnection and use the Connect button to activate the cross connection.
crossconnections which have been created, see Fig. 5.29
CMXC#...:CUC#..., see Fig. 5.26
connect the required IPMB8k/64 (Source From) configured in 64-kbit/s dialog with
any IPMB8k/64 (Destination To) configured in the same window in accordance with
the planning documents (e.g. IPMB64/2#2:1 with IPMB64/2#5:1)
the crossconnection and use the Connect button to activate the crossconnection.
(Example with Filter setting Representation of Resources; FG-FE)
Parameter Entry
Type Transmission type
Port TP(A)
Timeslot
Selection of the FG IPM8k/64 according to the planning document, see Tab. 5.29.
Port TP(B)
Timeslot
Selection of the FG IPM8k/64 according to the planning document, see Tab. 5.29.
Selection must be 1(* means: this time slot is already busy).
140 A50010-A3-C800-5-7619
5.4.3.2 Modifying
5.4.3.3 Deleting
Deleting the 8 kbit/s Cross Connections
1. Select the NE.
parameter.
by selecting Get.
Port TP(B) Not relevant for cross connection 8kbit/s.
Bandwidth
n x (64kbit/s)
Selection of the number selected 8-kbit/s time slots assigned to a group of any port:
2: 16kbit/s connections
4: 32kbit/s connections.
(Time slots which are busy cannot be selected).
Distribution of
Timeslots:
Consecutive,
Equidistant
Create Group: Time slots of any port can be created in group (n = 2 or 4).
Multiple: Crossconnection is created for each time slot.
Protection
mode
Not relevant for crossconnection 8kbit/s.
Button Meaning
Time... Not relevant for cross connection 8kbit/s.
Protection... Not relevant for cross connection 8kbit/s.
Connection TP(A)* TP(B)* Frame Direction
8bit/s connection IPMB8k/64#x:1 IPMB8k/64#y:1 framed bidirectional
x, y = 1... 60, max number of available connection: 240
Tab. 5.29 Switchable Function Groups for 8kbit/s Cross Connections
i
The modifying an existing crossconnection is not possible. The cross connection only
can be deleted and then it must be new created.
i
A50010-A3-C800-5-7619 141
User Manual
UMN CMXC
5.4.4 Conference Mode (between 64 kbit/s Time Slots only)
In addition to its basic functions, the cross-connect multiplexer can work in the following
operating modes:
Conference (Full)
Every incoming time slot is distributed to all the outgoing time slots.
Point-to-multipoint mode (Point-to-Multipoint)
The incoming time slot of the point is distributed to all the outgoing time slots in the
multipoint. When this is set up, one of the subscribers must be defined as the point.
5.4.4.1 Creating
The creating a data conference is described in this Section. The operation task for cre-
ating a data conference is the same as the operation task for creating a voice confer-
ence.
Fig. 5.31 Dialog Configure Conferences - CMXII-CAS (Example)
Left field (only displaying):
Conf. ID Number for each conference, determined by the system.
#Subs according to the
planning document
Number of subscribers (at least 3 subscribers) in this conference, set
up in the Add data conference - <NE#...> window.
ConfType Full,
Point to Mul-
tipoint
Operating mode for the conference, set up in the
Add data conference - <NE#...> dialog
State Degraded,
Connected
Current state, while the conference is being set up,
Operating state, sets itself automatically.
Right field: will only display anything if a conference has been selected in the left-hand field
Tab. 5.30 Explanation of the Register Card Data Conferences
142 A50010-A3-C800-5-7619
Setting up a Conference
Connect a required EPP2#n:1 (n = port number) with its associated IPMB64/2#n:1
in accordance with the planning documents.
7. Confirm with OK. The selection will then appear in the list in Fig. 5.20. Select the
cross connection and use the Connect button to activate the cross connection.
Subs# according to the
planning document
All the subscribers who are participating in the selected conference;
in the case of point-to-point connections, the subscriber defined as
the point will be marked.
Port according to the
planning document
Displays the port assigned to the subscriber
Time slot according to the
planning document
Displays the time slot assigned to the subscriber
Button Meaning
Add... Opens the dialog for setting up conferences, see Fig. 5.32
Edit... Opens the window for editing the selected conference
Remove Deletes the selected conference. It is removed from the table.
Get Updates the display.
Tab. 5.31 Explanation of the Buttons
on the Register Card Data Conferences
Tab. 5.30 Explanation of the Register Card Data Conferences
PU16 unit
Frame framed,
unframed
PU16 unit
i
A50010-A3-C800-5-7619 143
User Manual
UMN CMXC
8. Open the register card Data Conference, see Fig. 5.31. This contains on the left-
hand an overview of all the data conferences which have been created.
9. Use Add... to open the window Add data conference - CMXC#...:CUC#... and
select the conference type, see Fig. 5.32.
Fig. 5.32 Dialog Add data Conference - CMXC#...:CUC#...
10. Use Add... to open the window Set port/timeslot for subscriber.
In the Drop down list, select the first subscribers port and time slot. Time slots which
are occupied are marked with Bi, Uni or +++ (not used at present, but reserved for
other subscribers in the same conference). Use OK to confirm. Close the window.
Subscriber #1 will be entered into the list in the window Add data conference -
CMXC#...:CUC#.... Proceed in the same way for the other subscribers (there must
be at least three subscribers).
11. The subscriber entries are now shown in the window Add data conference -
CMXC#...:CUC#.... Confirm with OK. The conference appears in the left-hand list
in the window Configure Conferences - CMXC#...:CUC#..., and its status changes
from Degraded to Connected when it has been successfully set up.
Parameter Entry
Full Operation modus conference, duplex modus between all subscrib-
ers.
Point to multipoint Operation modus Point to multipoint, duplex mode between sub-
scriber #1 (determined as point) and all other subscribers (#2 and
higher), which only can be communicated with subscriber #1.
i
The OK button can only be used when at least three subscribers have been entered.
144 A50010-A3-C800-5-7619
5.4.4.2 Modifying
Existing conferences can be modified.
Modifying existing Conferences
1. Select the NE.
the register card Data conference, see Fig. 5.31.
3. Select the conference and open the window Edit data conference -
CMXC#...:CUC#..., use the Edit... button. If necessary change the conference
type, see Fig. 5.32.
4. Select the conference. Open the dialog Set port/timeslot for subscriber, use the
Edit... button, and then use the Drop down list to change the port and time slot for
the individual subscribers as necessary. Confirm with OK. The changes will be en-
tered into the list in the window Edit data conference CMXC#...:CUC#.... Close the
window.
5. Use OK to confirm the entries.
5.4.4.3 Deleting
The operator can delete both subscriber and conferences.
Deleting existing Conferences
1. Select the NE.
2. Change in the menu Configuration NE Configuration Cross Connect to open
3. Select the conference and use the Remove... button. The conference is removed
from the list.
Deleting Subscribers from a Conference
1. Select the NE.
3. Select the conference and open the dialog Edit data conference -
CMXC#...:CUC#..., using the Edit... button.
4. Select the subscriber and use the Remove button. The conference is removed from
the list.
i
When a conference is edited, it is deleted and then a new one inserted. The new
conference can have a different identity from the one which has been deleted.
i
Note that for a conference there must be at least three subscribers involved.
A50010-A3-C800-5-7619 145
User Manual
UMN CMXC
5.4.5 Displaying the used 2-Mbit/s Ports
Fig. 5.33 Register Card 2Mbps Port Usage (Example)
Column Explanation
Window on the top
Sort The following selection is possible from the Drop down list:
Alphabetical Order Ascending: PU16 is sort in ascending sequence.
Alphabetical Order Descending: PU16 is sort in descending sequence.
Resources Free: unsorted design of free and used resources.
Resources Used: Resource with used ports are designed on top of the list.
PU16#... Displaying of all plugged-in units PU16 (# with plug-in place).
1 to 16 Is equal to the ports 1 to 16 of each PU16:
All ports can be used are designed as green squares. Ports with connections are designed
colorful (color is according to the generated alarm. The blue point shows the remote end of
the crossconnection of the selected port.
Window below
CCId to
Protect
The columns are equal with the columns of the register card Connections 2Mbit/s.
Tab. 5.32 Explanation of the Register Card 2Mbps Port Usage
146 A50010-A3-C800-5-7619
Displaying the used 2-Mbit/s Ports
1. Select the NE.
2. Choose in the Menu Configuration NE Configuration Cross Connect.
Open the register card 2Mbps Port Usage, see Fig. 5.33.
All ports of the PU16 which can be used (active state) are designed as green
squares. All ports with crossconnection are designed as colorful squares, see
marked crossconnection in Fig. 5.33. The color is according to the generated alarm
on the port.
3. Open the field Sort and choose the parameter, e.g: Resources Used. All connect-
ed time slots are displayed on the top of the list.
Displaying of the assigned opposite side:
4. Select any connected port and use the Opposite button. The connected opposite
side is marked with a blue point.
Button Meaning
Opposite Displaying of the opposite side of the crossconnection of the selected port (blue point).
Search... Opens a dialog for setting the number of free time slots are used.
(on 2-Mbit/s port not relevant)
2Mbps Port Usage
A50010-A3-C800-5-7619 147
User Manual
UMN CMXC
5.4.6 Overview of the used 64 kbit/s Crossconnections
Fig. 5.34 Register Card 64Kbps CC Overview (Example)
Column Meaning
Window on the top
Sort The following selection is possible from the Drop down list:
Alphabetical Order Ascending: PU16 is sort in ascending sequence.
Alphabetical Order Descending: PU16 is sort in descending sequence.
Resources Free: unsorted design of free and used resources.
Resources Used: Resource with used ports are designed on top of the list.
CUC#..:
<FG>
Displaying of all possible Function groups with assigned central unit.
0 to 31 Is equal to the time slots 1 to 16 of the Function Groups:
All time slots can be used are designed as grey squares. Time slots which are busy are
marked with X (state connected) or with N (state not connected). The blue point shows the
remote end of the crossconnection of the selected time slot. Time slots with CAS signalling
are white.
Possible Conferences on the Function Groups ICBA (analog) and ICBD (digital) are make as
red squares. Connected conferences are marked.
Window below
CCId to
Protect
The columns are equal with the columns of the register card Connections 64kbit/s. The en-
tries are made by selection an connected time slot in the window above.
Tab. 5.34 Explanation of the Register Card 64Kbps CC Overview
148 A50010-A3-C800-5-7619
Displaying the Overview of used 64 kbit/s Crossconnections
1. Select the NE.
2. Choose in the menu Configuration NE Configuration Cross Connect.
Open the register card 64Kbps CC Overview, see Fig. 5.34.
All possible time slots of the Function Groups are designed as grey squares. The
connected time slots are marked:
X (State connected)
N (State not connected)
3. Open the field Sort and choose the parameter, e.g: Resources Used. All connect-
ed time slots are displayed on the top of the list.
4. Select any connected time slot. The columns in the window below are filled. The en-
tries are equal with the columns in Fig. 5.34.
Displaying of the assigned opposite side:
5. Then use the Opposite button. The connected opposite side is marked with blue
point.
Displaying of the free time slots of a Function Group:
6. Select any connected time slot and use the Search... button. Entry the number of
free time slots which will be displayed and confirm the with OK. The free time slots
will be marked with blue points.
Button Meaning
Opposite Displaying of the opposite side of the crossconnection of the selected time slot (blue point).
Search... Opens a dialog for setting the number of free time slots are used.
Tab. 5.35 Explanation of the button on the Register Card
64Kbps CC Overview
A50010-A3-C800-5-7619 149
User Manual
UMN CMXC
6 Maintenance
This section describes all such measures as are necessary for the rectification of faults
which can be localized and rectified via the operator terminals and the appropriate alarm
signalling.The procedures can be opened from the Operating System via the feature
Branch to Maintenance.
6.1 Terminals for Maintenance and Fault Rectification
For central operation and maintenance of the CMXC the AccessIntegrator is used. In
the following Text it is named OS. The handling and the elementary functions are de-
scribed in User Manual, UMN AccessIntegrator (see Section 1.3 "Additional Documen-
tation"). The access to the OS takes place via the QD2 interface in the OLT.
For local operator guidance purposes, the LCT (Local Craft Terminal) is deployed on
site, e.g. connected via F interface to OLT, ODT or ONU. Their structure and assignment
to the communications equipment of the transmission network is illustrated in
Section 5.1.4. For the F interface with access protection, please see User Manual, UMN
ACI (Section 1.3 "Additional Documentation").
The LCT has a V.24/RS232 port for connection to the F interfaces of the system com-
ponents. The output of alarm messages to the operation terminal is carried out via QD2
interface.
6.2 Alarms
Alarms are triggered by faults which affect operation and those which do not.
The system distinguishes between three level of urgency of alarms:
A alarm
Urgent alarm. The message has the highest priority
B alarm
Non-urgent alarm. The message has a lower priority as A alarm
S alarm
Service alarm. The unit has been switched to the operating status Service
Every fault initiates an alarm message in the network element affected, and this is for-
warded via the QD2 interface. Faulty NEs and plug-in units are highlighted using color
in the appropriate graphical summary of the operator terminal. This enables the rapid
identification and pinpointing of faults. In addition, all alarm messages are available in
the form of a list at AccessIntegrator and LCT. The messages contain, for example, in-
formation on location, urgency of alarm, fault type, date and time. The messages are
stored until such time as the alarm is acknowledged by the operating personnel.
The operator can set up filters according to various criteria to handle the display of alarm
messages. By means of this, display of such messages can be limited according to their
urgency and/or the units involved. Setting of the filter can also be restricted to a specific
time period.
Alarms can be triggered either by hardware faults or software errors.
150 A50010-A3-C800-5-7619
6.2.1 Hardware Alarms
If during operation, a fault is detected in a functional hardware block, the unit is automat-
ically taken out of operation, and an appropriate message issued to the OS. The higher-
ranking NE periodically attempts to put the faulty functional block back into operation.
After rectification of the fault the configuration applying before occurrence of the fault is
automatically restored. An alarm reset message is issued to the OS.
6.2.2 Software Alarms
The software is periodically checked by the creation of checksum. If the checksum dif-
fers from the value expected, the functional block or the NE will be reset. All connections
set up via the faulty functional block are terminated.
In the case of a software error, the error messages from the network elements affected
are stored in a non-volatile memory.
The following criteria trigger an alarm:
The program's checksum is incorrect
The watchdog circuit is not operated
Software for the network element is missing
Configuration data is incorrect
In general, software errors can be eliminated by software download or reconfiguration
of the data records.
6.2.3 Adjustments for Service in System Module
Various type of test can be performed to limit the extent of faults.
These include:
Connection of test loops
Check on synchronization loss
Bit error measurement
The tests also can be controlled locally from the LCT.
Certain types of test, for example bit error measurement, are only possible with the as-
sistance of external measurement technology.
6.2.4 Fault Management
The following functionality is currently implemented:
In the event of the failure, the protection switching is automatically activated (e.g.
CUC in the case of 1+1-protection switching)
After failure and subsequent restoration of the operating voltage, the system mod-
ules are automatically restarted
In the event of permanent errors (hardware and/or software), the corresponding
functional block is switched off, and a message issued to the OS.
A50010-A3-C800-5-7619 151
User Manual
UMN CMXC
6.3 Representation of Alarms in OS and LCT
The representation of an definite alarm signal is the same in OS and LTC. But the length
of the shown SISA address differs because of different connection places in SISA net.
Following kinds of presentation are given in OS/LCT:
Global alarm list - for displaying current alarms
Alarms of log: name - alarm list for recording all alarms from starting the log file
Alarms of x-y-z: NE -alarm list of a selected NE
The LCT is designated for mobile use. If it will connected to a F interface, only that part
of the SISA net is displayed that is hierarchical lower to the NE the LCT is connected to.
The display of alarms is also only possible for this part of the net. Therefore the SISA
address for a specific NE at the LCT is shorter as at the AccessIntegrator.
Display Elements and Controls
Display elements and controls are located in the devices OLT and ONU. With the help
of display elements actual operational states are represented. Controls are necessary
for setting system parameters are required. The setting is executed one-time in factory.
Besides, with the help of controls required resets and tests can be started at mainte-
nance works.
As display elements exclusive LEDs with colors red, yellow and green are used, in which
the red LED shine at a fault and the green LED at regular function. With the help of the
yellow LED it will be pointed to an active laser transmitter or on a special adjustment on
a slide-in unit.
Controls are arranged in part at the front side of the slide-in unit and in part on the slide-
in unit. Controls are DIP FIX switches, jumper, non-locking keys or jacks for connection
measuring instruments.
The assignment of the display elements and controls of several slide-in units are repre-
sented and their function explained in Section 3.
6.4 Elimination of an Alarm
To eliminate alarms displayed in OS or LCT, it is necessary to pick out the absolute ad-
dress of affected components. To get more information about alarm course, the SISA
surroundings and possible sequence errors following steps must be executed:
With the help of the OS the incorrect behavior is analyzed. On the basis of the NE
address, the OS sets up a point-to-point connection to the NE affected, and under-
takes NE-specific error analysis.
If the malfunction cannot be rectified from the location of the OS (e.g. failure of a
plug-in unit), then the malfunction must be rectified on site with the aid of a LCT.
6.4.1 Localization of an Alarm
To find out the absolute address of a system component, often the SISA address of the
top NE of this system component is necessary. Following it is called TOS (Top of Sta-
tion). For finding TOS following steps are necessary:
Determining the SISA address of the alarm in the alarm list
Identification of the SISA address of the TOS, to which the SISA address of the
alarm can be assigned
Reading the TOS user file
(The geographical addresses was deposited here during installation)
152 A50010-A3-C800-5-7619
If no TOS userfiles available, use the AKU HW lists for finding absolute address
The following algorithm must be used to generate the address of the TOS from the alarm
address of a network element, see Tab. 6.1 (n = Domain No.).
6.4.2 Alarm Elimination by Procedure
For eliminating disturbances in system, procedures must be processed step by step,
see Section 6.6.
6.4.3 Branch to Maintenance Procedures from Alarm Lists of the ACI
A direct entry point into the suitable procedure from alarm list of the ACI is realized by
the feature Branch to Maintenance. The installation and operation of this feature is de-
scribed in User Manual, UMN ACI DM (see Section 1.3 "Additional Documentation").
6.5 Branch to Maintenance Procedure from Graphical User
Interface of the OS/LCT
To show the maintenance procedure for an alarm type of the alarm list, the HTML col-
lection of the maintenance manual must be installed according to UMN:OMN of the ACI
(see Section 1.3 "Additional Documentation").
6.6 Explanations of the Procedures
Starting point is the failure indication in the Global Alarm List of the OS/LCT. The fault
term in the task list corresponds to the terms at the OS/LCT.
The basic hints should be noted are described in PROC0000.
Notes on replacing plug-in units
ESD precautions
All plug-in units are equipped with electrostatic sensitive devices (ESD symbol). It is
therefore necessary to adhere to the ESD precautions when inserting and removing
plug-in units.
When changing plug-in units maintenance personnel should wear a conducting wrist
strap to discharge static electricity. Before plug-in units, cables or components are
moved the wrist strap must be connected to the ground potential of the rack via a
flexible conductor. Ensure that when units are being plugged in, the conducting parts
of the banana plug must not be touched (bridging the discharge resistor).
DCN alarm address FastLink system components DCN address of the TOS
n-1-3/4/5/6-...: OLT (COT) rack n-1
n-1-1/2-(22/23/24)-1-x-...: ONU/SNU n-1-1/2-(22/23/24)-1-x
n-1-1/2-(22/23/24)-y-.... (y > 1) OLT (OMX) rack n-1
n SISA-K in OS TOS not required
n only AccessIntegrator is used (n for domain)
Tab. 6.1 Determining the TOS Address from the DCN Alarm Address
A50010-A3-C800-5-7619 153
User Manual
UMN CMXC
Defective plug-in units
Once removed, defective plug-in units should be labeled as such and should be han-
dled just as carefully as new units.
For transport to a repair center the defective units should be marked and packed in
compliance with ESD requirements.
Replacement plug-in units
The replacement unit must be identical to the original unit which it is replacing (same
code number for both HW/FW and functional status). In exceptional circumstances
the Functional Level List can be used to determine whether the functional status of
the replacement unit (as regards. HW/FW) is compatible with that of the original unit.
If the plug-in unit includes switches or other elements used to make settings, these
elements should be set to match those of the original plug-in units.
The individual procedures are arranged internally in consecutively numbered blocks.
The procedure elements used in the blocks are explained in Fig. 6.1.
Fig. 6.1 Elements of the Maintenance Procedures
6.7 Alarm Messages
The clearance procedures are associated to the following alarm messages (see
Tab. 6.2).
12 Decision block
Must fault clearance be cancelled for this block (e.g. no replacement module
available)?
Comments are always written in italics
For evaluation of system reaction see 4.19
Continue in accordance with system reaction:
- xxxx........................................................................................................
- NOT xxxx................................................................................................
- else .........................................................................................................
i....PROC:1234
h.......18
h.......19
J h .....13
N h .....16
.....4.19
Block number
Comment
(italics)
Multiple-choice
jump
Jump symbol
Yes/no
jump
Jump destination
(block number)
Block
Reference from/
to
information in
other sections
Jump symbol
with return
13 Decision block
Alarm name Meaning Function group Module
FWE Flash write error SISA0 SUE-E
INT-A internal error
LCN Communication error
PNV Program not valid
FWE Flash write error SISA0 CUC
INT-A Internal communication error
INT-B Internal communication error
Tab. 6.2 Alarm Association
154 A50010-A3-C800-5-7619
PNA Program not available
SumALM-
MODx
Sum alarm of Module x
LOS Loss of signal EPPM2/8
Dan No signal at Dan IIF64
LOTx Loss of timing reference PET CUC
Major Internal error
Minor Internal error
AIS AIS received EPP2 PU16
AISk AIS received
BER-3 Bit error rate exceeds 10E-3
BER-5/6 Bit error rate exceeds 10E-5/E-6
D-Bit D-Bit received
INT-A Internal communication error
ISA Loss of Signaling multiframe Alignment
LOF Loss of frame
LOS Loss of signal
LoopActive Port in Maintenance state
N-Bit N-Bit received
NK Nk-Bit received
TSB Clock control bit received
rSA Remote Signaling multiframe Alarm indication
Major Internal error
Minor Internal error
INT Internal error SISA0 ASA-K (SUE-E)
USM Power failure
Contact x External contact x MEL
Alarm name Meaning Function group Module
Tab. 6.2 Alarm Association (Cont.)
A50010-A3-C800-5-7619 155
User Manual
UMN CMXC
7 Index
B
Branch to Maintenance
Installation 152
Showing the maintenance procedure 152
C
Central Unit CUC
Alarm table active 48
Assignment of the connectors 53
Function 44
Interfaces 45
Operating elements 52
Overview 44
Supervision and alarm 46
Technical data 55
Clock synchronization 26
CMXC
Application 20
Features 20
in FMX2R3 Application 21
Overview 13, 22, 32
SISA access 30
Commissioning 13
Creating crossconnections 93
CUC 89
General hints 81
Prerequisites 82
PU16 91
Sequence for commissioning 83
SNUS shelf 84
Starting the LCT 84
Visually inspection (checklist) 83
Conferences
General 27
Configuration
CUC 111
PU16 117
SUE 110
Crossconnection
2 Mbit/s 123
64 kbit/s 131
8 kbit/s 137
Conferences 141
E
External interface
Alarm contacts 23
CCUR 24
E1 22
ECC 23
QD2 slave 23
T3 23
I
Interface Unit PU16
Alarm table 60
Assignment of connectors 64
Function 57
Interfaces 58
Operating elements 63
Overview 57
Supervision and alarm 58
Technical data 66
Internal interface
CC 25
CCR 26
CCUR 25
LSI 25
PCI 24
STSB 26
SVB 25
M
Maintenance 13
Alarm messages 153
O
Operation 13
Backup function 109
Configuration management 109
Function groups 102
General hints 96
Load files 108
Overview operation tasks 96
QD2 structure for control and monitoring 104
SISA Network 105
P
Power supply 29
R
Redundancy
Alternative route for 2-Mbit/s connections 29
Creating the alternative route 123
Module redundancy 28
S
SNUS shelf
Assignment of the connectors 38
Equipping 37
Layout 33
QD2 addressing 35
QD2 structure 36
Technical data 43
156 A50010-A3-C800-5-7619
Subrate multiplex 28
T
Technical description 13

Crossconnect Multiplexer CMXC User Manual

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Crossconnect Multiplexer CMXC User Manual

Загружено:

Авторское право:

Доступные форматы

User Manual

Crossconnect Multiplexer CMXC

Creating a network map

Opens the DCN View for an NE

Modifying route mgt. properties

Modifying SNC mgt. properties

Administering log files

Opening the alarm list

Displaying log files

Displaying quality data

AccessIntegrator Main Menu LCT Function Manual/ection

Displaying log files

Displaying log files

Mass Provisioning Mass Provisioning from File

Opening the dialog foe export

Вам также может понравиться