Crossconnect Multiplexer CMXC User Manual

User ManualCrossconnect Multiplexer CMXC

UMN CMXC

A50010-A3-C800-5-7619

2UMN CMXC User ManualCrossconnect Multiplexer CMXCThe 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 SafetyElevated 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 ProduktsicherheitIn 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


UMN CMXCReason for Update

Details:

Chapter/Section Reason for Update

All SUE replaced by SUE-E with Ethernet interface

Issue HistoryIssue Date of issue Reason for Update

4 2/2009 Rebranding

5 02/2012 SUE replaced by SUE-E with Ethernet interfaceA50010-A3-C800-5-7619 3

UMN CMXC User ManualCrossconnect Multiplexer CMXC4 A50010-A3-C800-5-7619


UMN CMXCThis document consists of a total of 156 pages. All pages are issue 5.

Contents1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.1 Structure of the Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.2 Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.3 Additional Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.4 Protection Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.4.1 Protection Against Excessive High Contact Voltages. . . . . . . . . . . . . . . . . 151.4.2 Protection Against Escaping Laser Light . . . . . . . . . . . . . . . . . . . . . . . . . . 151.4.3 Protection Against Fire in Racks or Housings. . . . . . . . . . . . . . . . . . . . . . . 161.4.4 Components Subject to Electrostatic Discharge. . . . . . . . . . . . . . . . . . . . . 161.4.5 Handling Modules (General) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171.4.6 Handling Optical Fiber Connectors and Cables . . . . . . . . . . . . . . . . . . . . . 171.4.7 Protection against Foreign Voltages in the System . . . . . . . . . . . . . . . . . . 171.4.8 Virus Protection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.5 CE Declaration of Conformity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.6 Waste of Electrical and Electronic Equipment (WEEE) . . . . . . . . . . . . . . . 182 System Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.1 Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.2 Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.2.2 External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222.2.3 Internal Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242.2.4 Clock Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262.2.5 Conferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272.2.6 Subrate Multiplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.2.7 Voice Channel in Common Frequency Radio Networks. . . . . . . . . . . . . . . 282.2.8 Redundancy Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282.2.9 Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292.3 Operation and Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302.3.1 Access to CMXC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302.3.2 Operating Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302.3.3 Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.3.4 Diagnostic Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.4 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.4.1 Storage Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312.4.2 Initializing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3 Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323.2 SNUS Shelf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.2.1 SNUS Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333.2.2 Addressing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353.2.3 QD2 Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.2.4 Position and Assignment of Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . 373.2.5 Technical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43A50010-A3-C800-5-7619 5

UMN CMXC User ManualCrossconnect Multiplexer CMXC3.3 Central Unit CUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443.3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443.3.2 Supervision and Alarm Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463.3.3 Operating Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523.3.4 Technical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553.4 Interface Unit PU16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573.4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573.4.2 Supervision and Alarm Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583.4.3 Operating Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633.4.4 Technical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663.5 Supervision Unit SUE and SUE-E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673.5.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673.5.2 Control and Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693.5.3 Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703.5.4 Connector Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753.5.5 Technical Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

4 Commissioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814.1.1 Scope of the ITMN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814.1.2 Error Reports on the Installation Test Manual . . . . . . . . . . . . . . . . . . . . . . . 814.1.3 Dealing with Defective Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814.1.4 Procedure in the Event of Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814.1.5 Procedure in the Event of Serious Faults. . . . . . . . . . . . . . . . . . . . . . . . . . . 814.2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824.2.1 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824.2.2 Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824.3 Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834.3.1 Sequences for Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834.3.2 Visually Inspection (Check List) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834.3.3 Starting the LCT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844.3.4 Commissioning of the SNUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844.3.5 Commissioning of the SUE-E. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854.3.6 Commissioning the CUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894.3.7 Commissioning the PU16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914.3.8 Creating the Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

5 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 965.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 965.1.1 Notes for Working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 965.1.2 Overview of Operating Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 965.1.3 Overview of Function Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025.1.4 Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045.1.5 SISA Communication Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1055.1.6 Interfaces used for Operating Purposes . . . . . . . . . . . . . . . . . . . . . . . . . . 1065.1.7 Operation Modes of SUE-E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075.2 Software Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1085.3 Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1096 A50010-A3-C800-5-7619


UMN CMXC5.3.1 SISA-V/LMXV2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1105.3.2 CUC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1115.3.3 PU16 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1175.4 Crossconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1235.4.1 Crossconnections 2 Mbit/s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1235.4.2 Cross Connections 64 kbit/s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1315.4.3 Cross Connections 8 kbit/s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1375.4.4 Conference Mode (between 64 kbit/s Time Slots only) . . . . . . . . . . . . . . 1415.4.5 Displaying the used 2-Mbit/s Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1455.4.6 Overview of the used 64 kbit/s Crossconnections . . . . . . . . . . . . . . . . . . 147

6 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1496.1 Terminals for Maintenance and Fault Rectification. . . . . . . . . . . . . . . . . . 1496.2 Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1496.2.1 Hardware Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1506.2.2 Software Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1506.2.3 Adjustments for Service in System Module . . . . . . . . . . . . . . . . . . . . . . . 1506.2.4 Fault Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1506.3 Representation of Alarms in OS and LCT. . . . . . . . . . . . . . . . . . . . . . . . . 1516.4 Elimination of an Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1516.4.1 Localization of an Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1516.4.2 Alarm Elimination by Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1526.4.3 Branch to Maintenance Procedures from Alarm Lists of the ACI . . . . . . . 1526.5 Branch to Maintenance Procedure from Graphical User Interface of the

OS/LCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1526.6 Explanations of the Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1526.7 Alarm Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

7 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155A50010-A3-C800-5-7619 7

UMN CMXC User ManualCrossconnect Multiplexer CMXCIllustrationsFig. 2.1 CMXC Application (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Fig. 2.2 CMXC Application in an FMX2R3.2 Ring Connection . . . . . . . . . . . . . . 21Fig. 2.3 CMXC Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Fig. 2.4 Allocation of Alarm Contacts, Example ZA(A) . . . . . . . . . . . . . . . . . . . . 23Fig. 2.5 CMXC Synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Fig. 2.6 Redundancy Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Fig. 2.7 Power Supply in Shelf SNUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Fig. 2.8 CMXC in Stand-alone Operation Mode (Example) . . . . . . . . . . . . . . . . . 30Fig. 3.1 SNUS with Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Fig. 3.2 SNUS Front View with the DIL Switches S101 to S116 . . . . . . . . . . . . . 34Fig. 3.3 DIL Switches S105 to S116 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Fig. 3.4 DIL Switch S101 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Fig. 3.5 DIL Switches S103 and S104 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Fig. 3.6 Location of Connectors and Equipping of Units . . . . . . . . . . . . . . . . . . . 37Fig. 3.7 CUC Block Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Fig. 3.8 CUC Operating Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Fig. 3.9 Position of the Jumpers on the Pin Strips X401 . . . . . . . . . . . . . . . . . . . 52Fig. 3.10 PU16 Block Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Fig. 3.11 Local Loop and Remote Loop Test Loops . . . . . . . . . . . . . . . . . . . . . . . 59Fig. 3.12 PU16 Operating Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Fig. 3.13 Position of the Jumpers on the Pin Strips . . . . . . . . . . . . . . . . . . . . . . . . 64Fig. 3.14 Operation and Monitoring via SUE-E Interfaces . . . . . . . . . . . . . . . . . . . 67Fig. 3.15 Controls of the SUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Fig. 3.16 Controls of the SUE-E. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Fig. 3.17 Connector 11 of the SUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Fig. 3.18 Connector 10 of the SUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Fig. 3.19 Connector X2 of the SUE-E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Fig. 3.20 Connector X1 of the SUE-E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Fig. 4.1 SUE-E Dialog Software Download . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Fig. 4.2 SUE-E Register Card Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 87Fig. 4.3 SUE-E Register Card General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Fig. 4.4 Example of TCP/IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Fig. 4.5 SUE-E Register Card Inventory Data . . . . . . . . . . . . . . . . . . . . . . . . . 88Fig. 5.1 QD2 Structure (Example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Fig. 5.2 SISA Structure of FastLink System. . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Fig. 5.3 Example of a SUE-E Address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Fig. 5.4 QD2-Operatiion Mode 1: Slave with QD2 Interface . . . . . . . . . . . . . . . 107Fig. 5.5 QD2 Operation Mode 2: Slave with Ethernet Interface. . . . . . . . . . . . . 108Fig. 5.6 QD2 Tunnel via TCP/IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Fig. 5.7 SUE-E Register Card Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Fig. 5.8 CUC Register Card for Setting the Clock Synchronization . . . . . . . . . . 112Fig. 5.9 CUC Register Card for Configuring the Alarm Supervision . . . . . . . . . 1138 A50010-A3-C800-5-7619

Fig. 5.10 CUC Register Card for Configuring the Ports . . . . . . . . . . . . . . . . . . . . 114


UMN CMXCFig. 5.11 CUC Register Card for Setting the ECC Operation Mode . . . . . . . . . . 115Fig. 5.12 CUC Register Card for Activation/Deactivation of the ports . . . . . . . . 116Fig. 5.13 CUC Register Card for Displaying the State of the ECC Ports . . . . . . 117Fig. 5.14 PU16 Register Card for setting the Operator Loop . . . . . . . . . . . . . . . 118Fig. 5.15 PU16 Register Card for Setting the Alarm Criteria . . . . . . . . . . . . . . . 119Fig. 5.16 PU16 Register Card for Setting the Frame structure. . . . . . . . . . . . . . 119Fig. 5.17 PU16 Register Card for Setting the Sa Bit Control . . . . . . . . . . . . . . . 120Fig. 5.18 PU16 Register Card for Setting the Operation Mode. . . . . . . . . . . . . . 121Fig. 5.19 PU16 Register Card for Displaying the State off all Ports . . . . . . . . . . 122Fig. 5.20 Register Card Connections 2Mbit/s. . . . . . . . . . . . . . . . . . . . . . . . . . 123Fig. 5.21 Register Card for Setting Filter Parameter. . . . . . . . . . . . . . . . . . . . . . 126Fig. 5.22 Dialog for Creating Crossconnection 2 Mbit/s

(Example with Filter setting Representation of Resources: FG-FE) . 127Fig. 5.23 Dialog for Setting the Time Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Fig. 5.24 Dialog for Setting the Switching Criteria . . . . . . . . . . . . . . . . . . . . . . . 128Fig. 5.25 Register Card Connections 64kbit/s . . . . . . . . . . . . . . . . . . . . . . . . . 131Fig. 5.26 Dialog for Creating the Crossconnection 64 kbit/s

(Example with Filter setting Representation of Resources; FG-FE) . 134Fig. 5.27 Displaying of the Time Slots assigned to a Group (Example) . . . . . . . 135Fig. 5.28 Dialog for Creating the Crossconnection 64 kbit/s (Example) . . . . . . . 135Fig. 5.29 Register Card Connections 8kbit/s . . . . . . . . . . . . . . . . . . . . . . . . . . 137Fig. 5.30 Dialog for Creating the Crossconnection 8 kbit/s

(Example with Filter setting Representation of Resources; FG-FE) . 139Fig. 5.31 Dialog Configure Conferences - CMXII-CAS (Example) . . . . . . . . . . 141Fig. 5.32 Dialog Add data Conference - CMXC#...:CUC#... . . . . . . . . . . . . . . 143Fig. 5.33 Register Card 2Mbps Port Usage (Example) . . . . . . . . . . . . . . . . . . 145Fig. 5.34 Register Card 64Kbps CC Overview (Example) . . . . . . . . . . . . . . . . 147Fig. 6.1 Elements of the Maintenance Procedures. . . . . . . . . . . . . . . . . . . . . . 153A50010-A3-C800-5-7619 9

UMN CMXC User ManualCrossconnect Multiplexer CMXCTablesTab. 1.1 Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Tab. 2.1 Structure of a PCI Time Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Tab. 2.2 PCI Frame Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Tab. 2.3 Conference Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Tab. 3.1 SNUS Overview of Addressing and the Units. . . . . . . . . . . . . . . . . . . . . 35Tab. 3.2 Assignment of Connectors X141 (left and ) X142 (right) . . . . . . . . . . . . 38Tab. 3.3 Terminal Assignment of Jacks X101, X102 and X121 . . . . . . . . . . . . . . 38Tab. 3.4 Terminal Assignment of 9-Contact Jacks X143 and X144 . . . . . . . . . . . 39Tab. 3.5 Terminal Assignment of Jacks X122 and X131 . . . . . . . . . . . . . . . . . . . 39Tab. 3.6 Terminal Assignment of Jacks X109, X110, X 113, X114, X129, X130,

X133, X134 and X115. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Tab. 3.7 CUC Signaling the active Operating Mode . . . . . . . . . . . . . . . . . . . . . . . 46Tab. 3.8 CMXC Indication of the Operating Mode . . . . . . . . . . . . . . . . . . . . . . . . 46Tab. 3.9 CUC Indication of the standby Operating Mode . . . . . . . . . . . . . . . . . . . 46Tab. 3.10 CUC Alarm Table (Active). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Tab. 3.11 CUC Alarm Table (Standby) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Tab. 3.12 CUC Connector (bottom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Tab. 3.13 CUC Connector (top) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Tab. 3.14 PU16 Signaling the Operating Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Tab. 3.15 PU16 Alarm Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Tab. 3.16 PU16 Connector (bottom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Tab. 3.17 PU16 Connector (top) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Tab. 3.18 Visual Signals Output by the SUE-E. . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Tab. 3.19 Operating Modes QD2-Slave 1 T-port (QD2Txx1) . . . . . . . . . . . . . . . . . 73Tab. 4.1 Pin Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Tab. 4.2 Sequence of the Commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Tab. 4.3 Shelf Equipping with SUE-E and Units for CMXC . . . . . . . . . . . . . . . . . 84Tab. 4.4 Sequence for Creating 2-Mbit/s Cross Connections. . . . . . . . . . . . . . . . 93Tab. 4.5 Sequence for Creating 64-kbit/s Cross Connections . . . . . . . . . . . . . . . 94Tab. 4.6 Sequence for Creating 8-kbit/s Cross Connections . . . . . . . . . . . . . . . . 94Tab. 4.7 Sequence for Creating Conferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Tab. 5.1 Overview of Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Tab. 5.2 Network Element CMXC and its associated Function Groups . . . . . . . 102Tab. 5.3 Name of the Function Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Tab. 5.4 F Interface of the System Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Tab. 5.5 Correlation between Unit and Load Files . . . . . . . . . . . . . . . . . . . . . . . 109Tab. 5.6 Configuration Parameters for the Network Elements . . . . . . . . . . . . . . 110Tab. 5.7 List Entries in the Clock Priority List . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Tab. 5.8 Explanation of the Buttons in the CUC Register Card Clock sync. . . 113Tab. 5.9 Explanation of the CUC Register Card ECC Alarm Criteria . . . . . . . . 113Tab. 5.10 Explanation of the CUC Register Card Frame . . . . . . . . . . . . . . . . . . 114Tab. 5.11 Explanation of the CUC Register Card ECC Mode . . . . . . . . . . . . . . 11510 A50010-A3-C800-5-7619

Tab. 5.12 Explanation of the CUC Register Card General . . . . . . . . . . . . . . . . . 116


UMN CMXCTab. 5.13 Explanation of the CUC Register Card ECC Status . . . . . . . . . . . . . 117Tab. 5.14 Explanation of the PU16 Register Card General. . . . . . . . . . . . . . . . 118Tab. 5.15 Explanation of the Pu16 Register Card Alarm Criteria . . . . . . . . . . . 119Tab. 5.16 Explanation of the PU16 Register Card Frame . . . . . . . . . . . . . . . . . 120Tab. 5.17 Explanation of the PU16 Register Card Clock Control . . . . . . . . . . . 120Tab. 5.18 Explanation of the PU16 Register Card General. . . . . . . . . . . . . . . . 121Tab. 5.19 Explanation of the PU16 Register Card Status View. . . . . . . . . . . . . 122Tab. 5.20 Explanation of the Register Card Connections 2Mbit/s . . . . . . . . . . . 123Tab. 5.21 Explanation of the Buttons on the Register Card

Connections 2Mbit/s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Tab. 5.22 Switchable Function Groups for 2Mbit/s Cross Connections. . . . . . . . 129Tab. 5.23 Assignment of IPMB64/2 to Associate TP . . . . . . . . . . . . . . . . . . . . . . 129Tab. 5.24 Explanation of the Register Card Connections 64kbit/s . . . . . . . . . . 131Tab. 5.25 Explanation of the Buttons on the Register Card

Connections 64kbit/s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Tab. 5.26 Switchable Function Groups for 64kbit/s Crossconnections . . . . . . . . 135Tab. 5.27 Explanation of the Register Card Connections 8kbit/s . . . . . . . . . . . 137Tab. 5.28 Explanation of the Buttons on the Register Card

Connections 8kbit/s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Tab. 5.29 Switchable Function Groups for 8kbit/s Cross Connections . . . . . . . . 140Tab. 5.30 Explanation of the Register Card Data Conferences. . . . . . . . . . . . . 141Tab. 5.31 Explanation of the Buttons

on the Register Card Data Conferences . . . . . . . . . . . . . . . . . . . . . . 142Tab. 5.32 Explanation of the Register Card 2Mbps Port Usage . . . . . . . . . . . . 145Tab. 5.33 Explanation of the Buttons on the Register Card

2Mbps Port Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Tab. 5.34 Explanation of the Register Card 64Kbps CC Overview . . . . . . . . . . 147Tab. 5.35 Explanation of the button on the Register Card

64Kbps CC Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Tab. 6.1 Determining the TOS Address from the DCN Alarm Address . . . . . . . 152Tab. 6.2 Alarm Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153A50010-A3-C800-5-7619 11

UMN CMXC User ManualCrossconnect Multiplexer CMXC12 A50010-A3-C800-5-7619


UMN CMXC1 IntroductionIn this Manual, an overview about the components and their interworking in the accessnetwork 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 theACI 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 weredelivered with the software.

1.1 Structure of the ManualThe 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 theconnector assignment.

Commissioning The Commissioning describes all the procedures and measurements for activating theinstalled system, including step-by-step instructions to commissioning the SystemModule CMXC.

Operation This section offers a guide line to use the operating procedures for configuring and forcreating the crossconnections.

Maintenance The procedures which expedite the re-establishment of normal operating state after amalfunction has occurred in the CMXC can be find out via the operating system byBranch to Maintenance. The section Maintenance gives an overview of the possiblemalfunctions and contains a guideline for the using of Branch to Maintenance.A50010-A3-C800-5-7619 13

UMN CMXC User ManualCrossconnect Multiplexer CMXC1.2 Typographical ConventionsIn all sections of this manual, the following conventions are applied:

1.3 Additional DocumentationIn 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 outputsExample: Enter LOCAL as the server name

Command not found

Italics VariablesExample: name can be up to eight letters long.

Italics Variables fin procedures and title basExample: General NE Parameter. :CUC#...

Boldface Special emphasisExample: 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.

Key combinationsExample: +

Successive menu itemsExample: File Close

i Additional items of information

!Warnings at critical points in the activity sequence

Tab. 1.1 Typographical Conventions14 A50010-A3-C800-5-7619


UMN CMXC1.4 Protection MeasuresThis 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 properlytrained and qualified personnel.In the event of any injury (e.g. burns and acid burns) being sustained, seek medical helpimmediately.

1.4.1 Protection Against Excessive High Contact VoltagesWhen 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 highcontact voltages when they are not grounded.

1.4.2 Protection Against Escaping Laser LightWhen 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 suchunits can be identified by a stick on label as well as by a warning label.

Laser symbol

Warning labelA50010-A3-C800-5-7619 15

UMN CMXC User ManualCrossconnect Multiplexer CMXCTo 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, despitethe 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 HousingsIf FMX2R3.2 shelves are used in housing, the shelves must be performed the conditionsfor 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 inDin EN 60950.

1.4.4 Components Subject to Electrostatic Discharge

When packing or unpacking, touching pulling or plugging plug-in units bearing the ESDsymbol, 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 electrostaticdischarge.Under no circumstances should the printed conductors or components of modules betouched. Take hold of modules by the edge only.Once they have been removed, modules must be placed in the conductive plasticsleeves 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 thesame 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.16 A50010-A3-C800-5-7619


UMN CMXC1.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 CablesOptical 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 SystemTwo-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. A50010-A3-C800-5-7619 17

UMN CMXC User ManualCrossconnect Multiplexer CMXC1.4.8 Virus Protection

Even when exchanging data via network or external data carries (e.g. floppy disks) thereis a possibility of infecting your system with a virus. The occurrence of a virus in yoursystem 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 ConformityThe 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. mountinginstructions, cable lists. Where necessary account should be taken of project-specificdocuments.Deviations from the specifications or unstipulated changes during construction, e.g. theuse 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 themunicipal waste stream via designated collection facilities appointed by the governmentor the local authorities.The correct disposal and separate collection of your old appliance will help preventpotential negative consequences for the environment and human health. It is a

!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.18 A50010-A3-C800-5-7619

precondition for reuse and recycling of used electrical and electronic equipment.


UMN CMXCFor more detailed information about disposal of your old appliance, please contact yourNokia Siemens Networks service partner.The statements quoted above are only fully valid for equipment which is installed in thecountries 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.A50010-A3-C800-5-7619 19

UMN CMXC User ManualCrossconnect Multiplexer CMXC2 System Overview

2.1 ApplicationThe CMXC crossconnect multiplexer is a compact solution to establish small networknodes at 8-kbit/s, 64-kbit/s and 2-Mbit/s level. It supports up to 32 2-Mbit/s ports andmakes 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 canalso 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 3P7

P8

SMX1/4c STM-1/STM-4

CMXC

ZS1

ZS60FMX2R3.2

LE2 1

...

...

...

...

P1 P17

P3

P32

P2

P4

P1

P16

P9

P16

...

...

E1, 2 Mbit/sG.703

E1, 2 Mbit/sG.70320 A50010-A3-C800-5-7619


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.2A50010-A3-C800-5-7619 21

UMN CMXC User ManualCrossconnect Multiplexer CMXC2.2 Structure

2.2.1 OverviewThe 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 correspondto the ITU-T recommendation G.703/6. The line impedance 75 unsymmetrical or 120 symmetrical can be set individuallyfor each interface by means of jumpers (see Section 3.3.3).

PCIS5 to 8

CUC

PU16

CUCS

PCI5 to 8PCI1 to 4

PCIS1 to 4

CCURCCURS

LSI (1 to 7)SVB

STSB CC

QD2-ST3in 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 V48 V

redundant CUC

CCUR

CCURS22 A50010-A3-C800-5-7619


UMN CMXCEach 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 InterfaceFor clock synchronization, a clock signal can be fed via interface T3in and sent viaT3out. The interface is on the CUC and corresponds to the ITU-T recommendationG.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 an2-Mbit/s port. The interface is designed with low-impedance and is disconnected whenswitching over to the redundant CUC.

QD2 Slave InterfaceThe 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 fixedfrom 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, thebus termination must be suitably fitted on the outside. Care must be taken that two busloads are active for redundant equipping of CUC (maximum possible number is 32). One QD2 address applies to active and standby CUCs.

ECC InterfacesThe ECC interfaces transmit control information from higher-level and to remote systemcomponents. The control information is integrated in an ECC channel (64-kbit/s timeslot) 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 twoas 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 ContactsThe alarm contacts are arranged on central units CUC and are used to signal alarmmodes 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) aredesigned in an equivalent manner.

Fig. 2.4 Allocation of Alarm Contacts, Example ZA(A)

ZA(A)_AZA(A)_R

ZA(A)_U(PUP)

ZA(A)

To the connector panelA50010-A3-C800-5-7619 23

UMN CMXC User ManualCrossconnect Multiplexer CMXCAlarm 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 deferredalarms (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 InterfaceThe 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 externalequipment so that these can switch over their PCI bus drivers.

2.2.3 Internal Interfaces

PCI InterfacesThe PCI interfaces transmit useful data between the CUC and units PU16. They alsodistribute 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 PU16svia 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 notused 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 PCIframe 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 dataCAS : Bit for CAS signaling (not used here)P : Parity bitR : Reserved bit (in PCI downstream direction: Activity mode of the CUC is displayed)

Tab. 2.1 Structure of a PCI Time Slot

PCItime slot

PCMlink

PCMtime slot

0 1

01 22 33 44 1

15 26 37 4....

Tab. 2.2 PCI Frame Structure24 A50010-A3-C800-5-7619


UMN CMXCLSI InterfaceThe LSI interface is established on PU16 (transmitter) and CUC (receiver). It consists of7 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 SVBInternal communication between units CUC and PU16 takes place via the supervisionbus 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 InterfaceThere are two unsymmetrical connections between the units to signal the operatingmode of both CUCs and the PCI buses and their redundancy switchover. On PU16, onlyreceivers are connected to the record circuits whereas they are crossed between theCUC receive and transmit lines. A high level on line CCUR indicates that the left CUCis active and is connected via the primary PCI bus. In this mode, the CCURS line is atthe low level. When changing levels, a switchover to the redundant PCI bus and to theredundant central CUC takes place.

CC InterfaceThe CC interface (cross coupling interface with CC_I and CC_O) connects both CUCsand 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

31125 2126 3127 4128

free...160161 FSW

PCItime slot

PCMlink

PCMtime slot

Tab. 2.2 PCI Frame StructureA50010-A3-C800-5-7619 25

UMN CMXC User ManualCrossconnect Multiplexer CMXCCCR InterfaceThe CCR interface connects both CUCs and synchronizes the PCI frame of the standbyCUC via the active CUC.

STSB InterfaceData 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 andswitch 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 centralunits inserted next to one another.

2.2.4 Clock SynchronizationFor the CMXC function it is necessary that all the 2-Mbit/s signal streams E1in andE1out are applied with the same clock signal. This requirement is met if the signals atthe 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 slipsoccur 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 providedfor the E1in guide clocks from the PU16 units to the CUC. The source for the guide clockcan be selected at random from the 32 E1 ports. The software selects the activatedclock source on the basis of a priority list. This decides which one of the possible receiveclocks 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, itdisconnects the corresponding clock source. The CUC then identifies clock failure andswitches over to the clock source with the next lower priority (see the alarm table of theCUC in Section 3.3.2). If all the external clock sources fail, the PLL of CUC is switchedto free-running and a prompt alarm is released.If a clock source with a higher priority becomes available while operating with a lowerpriority standby clock, the guide clock switches over automatically.26 A50010-A3-C800-5-7619


UMN CMXCFig. 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 clockT3out 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 ConferencesA maximum of 30 digital and 30 analog conference channels can be switched in up to20 mutually independent conferences at the same time. The requirements for analogand digital conferences differ:

For the analog conference, each conference participant receives the total of all the othersignals. 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-bitOR 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...

PCIup CUC standbyCUC

PU16PU16

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 RequirementsA50010-A3-C800-5-7619 27

UMN CMXC User ManualCrossconnect Multiplexer CMXC2.2.6 Subrate MultiplexerTo switch subrate connections, a subrate channel of 1, 2 or 4 bits is converted to 8 fullbits and then switched and compressed again. Conversion takes place by oversamplingor subsampling.A maximum of 240 bidirectional subbit rate signals each with 8 kbit/s in CMXC can beswitched.

2.2.7 Voice Channel in Common Frequency Radio NetworksIn 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 beone such connection within the network. This connection is always unidirectional.The source can only be a VF interface in multiplexer FMX2R3 (with units CUD andUAC68). All subsequent multiplexers/crossconnect multiplexers must synchronizethemselves to the outgoing frames of the multiplexer with the synchronizing clocksource.

2.2.8 Redundancy Concept

2.2.8.1 Module RedundancyTo 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 activeCUC leads to a redundancy switchover if there is another CUC in the CMXC systemmodule. The software releases redundancy switchover. To this end, the operability of allthe components is supervised on both CUCs (active and standby). Units PU16 are not equipped redundantly, i.e. there is no protection switching if a PU16unit fails. Therefore, the CMXC system module has a fault penetration range of 16 E1interfaces.

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 (PCISat standby unit).

PCI1 to 8

PCIS1 to 8

STSBCCUR

CCURS

CCUR

CCUR

S

PU16

CUC

CUCSPU16

CCURTo external equipment

Redundant CUC28 A50010-A3-C800-5-7619


UMN CMXCHowever, the decentralized PU16 units are connected to both the bus systems. Theyreceive information about which one of the two PCI buses is active, the CCUR andCCURS signals (see CCUR Interface). Bus STSB is used as the communication interface for redundancy operation betweenthe 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 thatonly the active CUC accesses the specific interface.

2.2.8.2 Alternative Route Switching for a 2-Mbit/s ConnectionOne alternative route can be configured for each 2-Mbit/s connection which is switchedover 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, Dk-Bit, N-Bit, Nk-Bit neverThe 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 portand 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 SupplyUnits 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 andstandby CUCs are connected to either of the two voltages in each case. The PU16 unitsare connected to both voltages. The input voltages are fed to the consumers via EMCfilters on the backplane of the shelf.

Fig. 2.7 Power Supply in Shelf SNUS

CUCSCUC

PU16 PU16

Connector panel48 V/60 V

48 V-S/60 V-SA50010-A3-C800-5-7619 29

UMN CMXC User ManualCrossconnect Multiplexer CMXC2.3 Operation and Supervision

2.3.1 Access to CMXCThe CMXC forms an SISA Network Element. The central CUC accesses the NetworkElement 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 slaveport of SUE-E via the connector panel of the shelf.

Fig. 2.8 CMXC in Stand-alone Operation Mode (Example)

2.3.2 Operating ElementsThe 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 (seeSection 3.3.3).Jumpers are located on units PU16 to set the impedances of the E1 interfaces. The lineimpedance of each F1 interface can either be set separately to 75 unsymmetrical orto 120 symmetrical (see Section 3.4.3). A 5-step DIL switch is arranged on shelf SNUS to set the SISA address of the systemmodule (see Section 3.2.4).Detailed information about the switch settings and plug connector allocations can befound 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

LCTFSISA-V

LMX/V2

SUE-E

QD2 slave 1RS485/RS232

V.28

QD2 slave 2

Internal QD2 bus

RS485primary or

CMXC

SISA-V

ECC (V.11)FMX2R3

SISA-V

SMX1/4c

SISA-VLTCOH/LT

SISA-V

LT12CM/LTLT22CM/LTLTO/LT

Internal QD2 bus

T port (QD2 slave 1) for other NEs

QD2-M

Ethernet30 A50010-A3-C800-5-7619


UMN CMXC2.3.3 SupervisionSMD-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 theCUC indicate the system alarms.

2.3.4 Diagnostic FunctionsWhen switching on the input voltages for CMXC, self-test routines of the software andhardware 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 currentquality 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 SoftwareThe required SW of network element CMXC is loaded with the craft terminal and SWdownload via the V.24 or the QD2 interface. Special SW in the form of a file exists foreach CMXC unit.

2.4.1 Storage StructureEach one of the units has a unit computer consisting of a micro controller and variousstorage circuits (FEPROM, EEPROM, RAM) for administering the software and the da-ta. The micro controller controls the internal functional flow on the individual units. Thestorage 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 upagain at a later stage.Firmware containing the initial program loader, self-test programs and type label dataare found on each unit. The firmware is stored in the flash EEPROM on the unit. TheRAM contains the current SW which is loaded by the initial program loader.

2.4.2 InitializingAfter power-up each unit starts the initial program loader software contained in theFEPROM. 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 softwaredownload 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 mustA50010-A3-C800-5-7619 31

always be performed after a new SW has been loaded, so that the unit can reboot.

UMN CMXC User ManualCrossconnect Multiplexer CMXC3 Components

3.1 GeneralThe CMXC consists of a maximum of two CUC units and a maximum of two PU16 unitsin 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-aloneor 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 UK2 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 fibers1 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 OMX16All 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, the2-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 canbe 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.32 A50010-A3-C800-5-7619


UMN CMXC3.2 SNUS Shelf

3.2.1 SNUS Layout

Fig. 3.1 SNUS with Front Panel

101X1V1A1 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 T2D2C2B2

Y2X2U2 W2V2

U3 V3 W3 X3Y3

SMX DSMXTrib.Unit T3

T3

(+)(-)

48V

6A

(+)(-)

48V

6A

QD2-

Slave

QD2-

Ma

ste

r

Tln

Tln

Tln

G.70

3

Tln

Tln

Tln

G.70

3 HD

SL(LT

3)

PCI

G.7

03

G.70

3

G.70

3

G.7

03

G.70

3

1 . .

4

9 . .

12

1 . .

4

9 . .

12

17. .

21

1 . .

4

9 . .

12

address116

onoff

LC1

FRCO

N

LC2

LC3

LC4

LC5

LC6

LT2

PBA2

Port Unit 1 CMXC Port Unit 2 Trib Unit SMX

A3

Tln

Tln

Tln

Tln

Tln

Tln

G.70

3

G.70

3

5 . .

8

13. .

16

ECC

PCIS

G.70

3

G.70

3

5 . .

8

13. .

16

G.70

3

G.70

3

5 . .

8

13. .

16

G.70

317

. .21

V.11

xt. c

on

tact

s

ZA

LT1

12

12

12

12

12

12

12

12

12

12

F-PC

SNUS

LASER KLASSE 1LASER CLASS 1

Achtung!Laser und Glasfaser

mechanischnicht belasten

ATTENTION!LASER AND GLASS FIBER

MUST NOT BEPHYSICALLY DAMAGED

OR STRAINED

BA DC FE HG KJ ML PN RQ TS VU XWA50010-A3-C800-5-7619 33

UMN CMXC User ManualCrossconnect Multiplexer CMXCFig. 3.2 SNUS Front View with the DIL Switches S101 to S116

BA DC FE HG KJ ML PN RQ TS VU XW YX1V1A1 B1 C1 D1 E1 F1 G1 H1 J1 K1 L1 M1 N1 P1 Q1 R1 S1

address116

onoff

QD2-

Sla

ve

QD2-

Mast

er

Tln

Tln

Tln

G.7

03

Tln

Tln

Tln

G.7

03 HD

SL(LT

3)

PCI

G.70

3

G.7

03

G.70

3

G.70

3

G.7

03

(+)(-)

48V

6A

(+)(-)

48V

6AY2X2U2

E2 F2 G2 H2 J2 K2 L2 M2 N2 P2 Q2 R2 S2 T2LC1

FRCO

N

LC2

LC3

LC4

LC5

LC6

LT2

LT1

1 . . 4

9 . . 12

1 . . 4

9 . . 12

17. . 21

1 . . 4

9 . . 12

W2V2

D2C2B2

PBA2

Port Unit 1 CMXC Port Unit 2 Trib Unit SMX

A3

Tln

Tln

Tln

Tln

Tln

Tln

G.70

3

G.70

3

5 . .

8

13. .

16

ECC

PCIS

G.7

03

G.7

03

5 . .

8

13. .16

G.7

03

G.7

03

5 . .

8

13. .16

G.7

0317

. .21

V.11

U3 V3 W3 X3Y3

SMX DSMXTrib.Unit T3

T3

xt. c

onta

cts

ZA

201 202 204 205 206 207 208 209 210 211 212 213 214 215 216 217 SNUS

201202

204 205 206 207 208 209 210 211 212 213214

215216

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

S1141 2 3 4

ON

S108

ONS109

ON

S1111 2 3 4

ON

S1121 2 3 4

ON

S105

ON

S1131 2 3 4

ON

S106

ONS107

ON

S1151 2 3 4

ON

S1161 2 3 434 A50010-A3-C800-5-7619

Fig. 3.3 DIL Switches S105 to S116


UMN CMXC3.2.2 AddressingAlmost all units in the SNUS are assigned addresses via the backplanes. The addressesassigned 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 S101The 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 = GNDSEL_1 = GND

Line cards 1-6 203 to 208 4 bit = 1 to 6

LT1 as LU1) 3) 207 Fixed (4 bit) = 7LT1 as LT2) 3) 207 Fixed (5 bit) = 7LT2 as LU1) 3) 208 Fixed (4 bit) = 8LT2 as LT2) 3) 208 Fixed (5 bit) = 8LT3 as LU1) 209 Fixed (4 bit) = 9LT3 as LT2) 209 Fixed (5 bit) = 9PU16(1) 210 5 bit = 10CUC(1) 211 Fixed (5 bit) = 13 5 bit = 11CUC(2) 212 Fixed (5 bit) = 13 5 bit = 12PU16(2) 213 5 bit = 13ADM (SMX) 216 Fixed (5 bit) = 16Trib.Unit 214

LU1) = LUOT, LUCP, LUC, LUCTLT2) = LTO, LTCOH, LT12CM, LT22CM, LT2ME13) 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 0Example: Switch 1 on OFF corresponds to 24 = 16Switch 5 on OFF corresponds to 20 = 1Corresponds to address 17 for the SUE

ON (0)

OFF (1)

24 23 22 21 20

5A50010-A3-C800-5-7619 35

UMN CMXC User ManualCrossconnect Multiplexer CMXC3.2.3 QD2 StructureIf the stand alone operation mode the SUE-E must be used for supervision. Operatingor maintenance functions can be carried out locally via an F interface using a local craftterminal. The SUE-E monitors all units in the SNUS. The internal QD2 bus of the SNUSmust be switched using switches S103 (all slider units on OFF) and S104 (all sliderunits 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 areaccessible 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 theinternal 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 froma 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 interfacesof the CMXC, two are equipped with clock transmission. The ECC of the CUD is alsorouted 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)

LU1) = LUOT, LUCP, LUC, LUCTLT2) = LTO, LTCOH, LT12CM, LT22CM, LT2ME13) 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

S1044321

ON

S1034321

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)36 A50010-A3-C800-5-7619


UMN CMXC3.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 CMXCunits are only described.

48 V

48 V

QD2-

SAl

arm

PB

-

+-

+

A

X101 to X154 are the connectors in the terminal panelX201 to X316 are the connectors for the units in the shelf

1) DIL switch S101 for setting the SISA address of the SUE2) LT1/2/3 = LT/LU units (LT22CM may only be inserted into slot 209)

CQD

2-M

B D E F G H

I/O 1

-4

J

I/O 9

-12

K

HD

SL-L

T3

L

PCI

M

I/O 1

-4

N

I/O 9

-12

P

I/O 1

-4

Q

I/O 9

-12

R

I/O 1

7-21

S

I/O 5

-8I/O

13-

16EC

C-CU

CPC

ISI/O

5-8

I/O 1

3-16

I/O 5

-8I/O

13-

16I/O

17-

21

ZA

T3an

T3ou

t

V.11

Add.1)

E3IN

X153

X151

E3OUT

X154

X152

X301

201

X201

SUE-

E

X302

202

X202

CUD

/ CUA

X303

203

X203

LC1

/ FR

CON

X304

204

X204

LC2

X305

205

X205

LC3

X306

206

X206

LC4

X307

207

X207

LC5

/ LT1

2)

X308

208

X208

LC6

/ LT2

2)

X309

209

X209

LT32

)

X310

210

X210

PU16

X311

211

X211

CUC

X312

212X2

12CU

C

X313

213X2

13PU

16

X14D

X14

C

214

X14B

X14

ATU

X314

215

X214

DSM

X34

X15D

X15

C

216

X15B

X15

AAD

M

X316

218

X216

OTS

U_2M

/ PS

D

X315

217

X215

OTR

U36

or

or

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

X120X104 X106 X108 X110 X112 X114 X116

X103 X105 X107 X109 X111 X113 X115 X117 X141 X142X101

X102

X143

X144

Slot desig-nations

S101

TA50010-A3-C800-5-7619 37

UMN CMXC User ManualCrossconnect Multiplexer CMXCConnectors of the Power Supply (X141 and X142)

QD2 (X101 and X102) and Alarm Inputs (X121)

Notes to Tab. 3.3:GND = operation groundGND_S = shielded groundFor X101:Slave1 from SUE-EQD2S1 In a/bQD2S1 OUT a/bT-connections to Slave1 of the SUE-EQD2T IN a/bQD2T OUT a/bDAT, CLK, NRST = not used in CMXCFor X121:AIN1 to AIn8 = alarm inputs of the SUE-EAM = 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 X101QD2-Slave

X102QD2-Master

X121Alarm 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 X12138 A50010-A3-C800-5-7619


UMN CMXCFor X102:Master from SUE-E:QD2M IN a/bQDM OUT a/b

T3 Interface (X143 and X144)

Notes to Tab. 3.11:GND = operation groundGND_S = shielded groundFor 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 placesT3 OUT1 a/b = T3in1-output to the terminal panelT3 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 X143Connector T3ab

X144Connector

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 X122ZA-contacts

X131ECC 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_A2A50010-A3-C800-5-7619 39

Tab. 3.5 Terminal Assignment of Jacks X122 and X131

UMN CMXC User ManualCrossconnect Multiplexer CMXCNotes to Tab. 3.11:GND = operation groundGND_S = shielded ground

For X122:Index 1 = SUE-EIndex 2 = CU plug-in place (202), not used in CMXCIndex 3...5 = LT plug-in places (207 to 209), not used in CMXCIndex 6, 7 = CUC, plug-in places 211 and 212Index 8 = PSD plug-in place 218, not used in CMXCIndex 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 clockECC3 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 X122ZA-contacts

X131ECC of the CUC

(in addition to CUD)

Tab. 3.5 Terminal Assignment of Jacks X122 and X13140 A50010-A3-C800-5-7619


UMN CMXCInterfaces 2 Mbit/s G.703 (X109 to X110, X129 to X130, X113 to X117 and X133 to X137)

Notes to Tab. 3.6:GND_S = shielded groundFor 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.703Example: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 A50010-A3-C800-5-7619 41

UMN CMXC User ManualCrossconnect Multiplexer CMXCE1 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 to12 of the PU16/1 in Slot 210.The interfaces from X130 come from the ADM and are internal connected with port 13to 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.703Example: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 to12 of the PU16/2 in Slot 213.The interfaces from X134 come from the ADM and are internal connected with port 13to 16 of the PU16/2 in Slot 213.42 A50010-A3-C800-5-7619


UMN CMXC3.2.5 Technical Data

EMC

Climate

Power Supply

Compliance with the following standards ETS 300 386-1, 12/1994EN 300 386-2, 12/1997EMC Specif. 1TR9, 09/1999

In operationSNUS, standalone . . . . . . . . . . . . . . . . . . . . . . . . . .

SNU, ONU indoor. . . . . . . . . . . . . . . . . . . . . . . . . . .

in acc. with ETS 300 019-1-3environmental class 3.1+5 C to +40 Cin acc. with ETS 300 019-1-3environmental class 3.1E5 C to +45 C

during transport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . in acc. with ETS 300 019-1-2environmental class 2.3

storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . in acc. with ETS 300 019-1-1environmental class 1.2

Input voltage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 V to 72 VPower consumption of the unit . . . . . . . . . . . . . . . . . . . . 8 WA50010-A3-C800-5-7619 43

UMN CMXC User ManualCrossconnect Multiplexer CMXC3.3 Central Unit CUC

3.3.1 OverviewThe central unit CUC makes it possible to switch 1536 64-kbit/s time slots, i.e. 32 E1signals, without blocking. Referred to the usable time slots, these are 1488 time slotswithout CAS processing or 744 bidirectional 64-kbit/s connections and 1440 time slotswith CAS or 720 bidirectional

Documents

Crossconnect Multiplexer CMXC User Manual