8120 M Tellabs Node Operating Manual

Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual22030_12 07.01.2013 Document Information Revision History Document No. 22030_12 22030_11 22030_10 22030_09 Date 07.01.2013 09.03.2009 29.08.2008 02.11.2007 Description of Changes The Tellabs 8120 mini node has been discontinued. A discontinuation note has been added in ch. 1. Erroneous V35-M discontinuation note removed throughout the document. Layout and cross reference changes due to format conversion throughout the document. Safety notes related to grounding updated in chapters 4.5 and 6.11. Outdated data removed from the foreword. Figures 2, 24, 25 and 40 updated. The list of numbered items referring to the mechanical construction updated in chapter 4.8. Disassembling instructions updated in chapter 4.8.1. EMC standard updated in chapter 6.12. © 2013 Tellabs. All rights reserved. This Tellabs manual is owned by Tellabs or its licensors and protected by U.S. and international copyright laws, conventions and treaties. Your right to use this manual is subject to limitations and restrictions imposed by applicable licenses and copyright laws. Unauthorized reproduction, modification, distribution, display or other use of this manual may result in criminal and civil penalties. The following trademarks and service marks are owned by Tellabs Operations, Inc. or its affiliates in the United States and/or other countries: TELLABS ®, TELLABS ® logo, TELLABS and T symbol ®, and T symbol ®. Any other company or product names may be trademarks of their respective companies. The specifications and information regarding the products in this manual are subject to change without notice. All statements, information, and recommendations in this manual are believed to be accurate but are presented without warranty of any kind, express or implied. Users must take full responsibility for their application of any products. Adobe ® Reader ® are registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 2 22030_12 © 2013 Tellabs. Document Information Terms and Abbreviations Term Explanation ADPCM AIS CAS CRC DMA FAS FrFEA HDLC IF MEI MFrFEA PMA RAI TS VF Adaptive Differential Pulse Code Modulation Alarm Indication Signal Channel Associated Signalling Cyclic Redundancy Check Deferred Maintenance Alarm Frame Alignment Signal Frame Far-end Alarm High Level Data Link Control Interface Maintenance Event Information Multiframe Far-end Alarm Prompt Maintenance Alarm Remote Alarm Indication Time Slot Voice Frequency Compliance Statement Hereby, Tellabs Oy declares that this product is in compliance with the essential requirements and other relevant provisions of Directive 1999/5/EC. 22030_12 © 2013 Tellabs. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 3 Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 4 22030_12 © 2013 Tellabs. . .......... 28 3............................... 16 2..................................................................................................................................................................................................................................................1 Framed Interfaces ..........................................2 General.........................................................2 Unframed Interfaces ................................................Table of Contents Table of Contents About This Manual .................................................................... Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 5 .............................. 9 Audience.......5 3 Operation ...............11 2 Tellabs 8120 Mini Node M as Tellabs 8100 Network Element................................... 20 Network Synchronization ................................ 14 User Access Ports .............................................................................................................................1 2.............. 27 3....................................4..................................................................................................................................................................2...................................3................................................................................................................................................................... 17 Applications. 25 3.................................................................................. 11 1.............................2............. 9 Discontinued Products.............................................................................................................................................................5.2 Master Clock Synchronization ..........................................................................................................................3............................................................................................. 34 Cross-Connect Block......................................................... 35 3.................. 13 Framed Interfaces IF1 and IF2 ........................................ 17 2..................................................................................................... 35 3..........................................................3... 9 Objectives...............704 Framed Interfaces IF1 and IF2 ................3 Rules for Mixing Different Interface Types .................................................................................................................................. 25 G.................................. 30 3................................. 9 Documentation Feedback.............1 Frame and Multiframe Structure ....................................................... 37 Operation of Unframed Channel Interfaces IF3-IF6 .........................2 Framed Interface as User Access Port......................................................... 38 3...................................................1 3...........................................................3 Split Trunk Lines ....................................................................................................................................1 Construction.....................4.... 16 2......................... 13 2.....................................5 3..............1 Unframed Interfaces . 26 3.............2...1 Cross-Connection ........................................ 30 Operation of Framed Interfaces ..................................................................................................................6 22030_12 © 2013 Tellabs..............................................................................................................................................................................................4 1+1 Protection .............3 3....................................... 17 2...............................................................................................................................4 2.................................. 17 2............................................................3 General. 23 2............................................................................................................................................2.......................... 10 1 Introduction ..........................................2 Buffers .......................................................................................................... 31 Unit Controller.............................................................................5......................................................................................................................................................................................................................................................4 3................................................................................... 9 Document Conventions ............................................................................................................................................2 2. ............ 93 4.......4 OTE-LED-M.............2 Data Interfaces.................................................................................2 LTE-M Line Terminal 1 or 2 Mbit/s.............................. 98 4..........5 Cross-Connection Menu ............... 87 4........................................7................... 87 4.................................................................................................................................................................................. 89 4...........7.........................................................................................................................................................................................................7 Recommended Settings of Framed Interfaces ..................7................................................... 93 4..7 Entering Security Menu of Tellabs 8120 Mini Node M ........................................................ 49 3..................6......................10..10......................................................................................3 V Series Interface Modules ................9..................... BTE-2048-M........ 60 4...................................... 63 4......................................................4...............................................6....... 53 4 Installation ....................... 80 4.....3 Tests of Unframed Interfaces.........9 Unit List of Tellabs 8120 Mini Node M .......1 4................................................. 87 4................................................................................................................................................................................................. 39 3...............................................................................Table of Contents 3.....4 Interface Parameters Menu...................1 Common Units....... 62 4..............................................5 Configuration of Tellabs 8120 Mini Node M ........................... 56 Back Panel Connections ......................6.............................................................. 106 4................6 Menus of Tellabs 8120 Mini Node M ..... BTE-1088-M...................................1 G703-75-M and G703-120-M............................................. 8 Mbit/s .........6...........................5.......................... 72 4...........703 2 Mbit/s............2 4............................... 68 4..... 97 4................................... 60 4.... 103 4................................1 Framed Interface Used as 2048 kbit/s Trunk............................................................................................................. 102 4..........1 DC Power Supply Cabling ........................ 2 or 8 Mbit/s ..................................... 71 4...............2 Local Control...................... 88 4...7.................................................................3 Parameters Menu .....................................1 NMS Control ....................................6......7................................................................................................................................................................. 46 3................................................... 104 4..................... 56 Front Panel Indicators and Controls .....................10..10............... 56 Mains Connection.................................................................................... 100 4.........................5 Cross-Connection of Unframed Interfaces ................................ BTE-576-M..........................................................................................................8.............. BTE-576-M..................... 91 4..............6.......................................................4.....3 Timing Modes.... 60 4......................................................6 BTE-320-M.....................8 Service Operations and Modifications............................ BTE-1088-2W-M and BTE-2304-M Settings ........................................................... 96 4.....................................10............................................................................................ 90 4........... BTE-2048-2W-M and BTE-4096-M................................................................................................ 43 3... 86 4...................................................4 Rate Adaptation and Mapping.................2 Main Interface Modules...............................................................................................................................................................................10...........7.........5......................................................................................9.......1 Data Formatting Functions ........... 43 3..............................................................6............................................................................ 50 3..4 BTE-384-M Settings............................ Local Service Computer Connector..................................................2 Framed Interface Used as 2048 kbit/s User Access Point .......................................... BTE-1088-2W-M and BTE-2304-M.6...........7...............1 Security Menu....................... 58 4.......................6..............................2 Test of Framed Interfaces .................................................9.........................2 Faults Menu ...4............................... ........................................................................................................................7....................................................3 4...........................................6............... 97 4.....................................1 Equipment Test ............ 48 Test Resources ................................3 SYNC Connector...................................6 Cross-Connection Example .............7 3.....6 Copy Settings Menu ..................................................................... G............10 Connectors and Strappings of Framed Interfaces................................................................. 100 4...................... 59 4....6......................5 BTE-384-M.................................................................4 Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 6 22030_12 © 2013 Tellabs...........................................................................................................5 BTE-320-M..7 Binary-to-Hexadecimal Conversion Table ................ 103 4....................................................... 320…2304 kbit/s ................................................................ 384 kbit/s…4224 kbit/s ......................................................... 99 4........................................................................................3 Framed Interface Used as 8448 kbit/s Trunk.......... 49 3........................... 58 Operating Environment ................................................. Optical LED...............................6.....3 G703-8M-M.......7..................................1 Instructions on Disassembling Tellabs 8120 Mini Node M ........................... 75 4..........................................................2 SC......................... 62 4.......7............................. 94 4............................. ..........................................2........9 Mini LAN Module............................. V.....113 4.................. 141 Unframed Data Interfaces..................................................... Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 7 ....... 131 Faults and Actions of Unframed Interfaces............... 0............. V.. 130 5....................704/706)........................2 Master Clock Faults (Block 0)............V.......................6…64 kbit/s..................................................................... 132 5..... 2 pcs .......12......2........................ 2 pcs ..............1 Frame and Multiframe Buffer.................................. 133 5..................................... 126 5..................6…8448 kbit/s .......................... n x 64 kbit/s…2Mbit/s................Table of Contents 4....................................................................................28 if/DCE........................................................3 2048 kbit/s Interface (CCITT G...........3 6.............8 HSSI-M....................................704 Type Frame ............3............. 1...1 Common Logic Faults (Block 0) ..................... 56................. 107 4....................................35... DMA........................................................................................................................................ 10Base-T.........................11........................................... 64…2048 kbit/s...........35-IEC if....... MEI..................................... 2 pcs ....... 130 5................ 142 6... 2) ......4.........3....... 121 5 Faults and Actions ...........................2............. 137 Timing......1 Downloading Tellabs 8120 Mini Node M Software ...............10.. 135 5.......................2 6.......................... 125 5.......................6…64 kbit/s.....V........2 kbit/s.............................................................................................3......3....10.............1 General IF Faults of Unframed Interfaces .............................3................119 4... 120 4..... 2).............. 127 5...................................................... 2 pcs ............................2..................114 4...................112 4..................................................2..... 0...............................................................................5 X21-M...... 123 5.... n x 64 kbit/s.3 Cross-Connect Block Faults (Block 0)...............................................24/V.12 Software Update ............................................4 V24-DTE-M.......703 64 kbit/s Co/Contradirectional Interface.....................................1 5.........................................................11... 109 4........ V.............4 N x 64 kbit/s Interface with G......... 0................................................................ 142 6...........................................2 Terminology.....3..........11.................................... 138 6................3 V24-DCE-M....................4 Faults of Framed IF Tx Signal (Block 1........... n x 64 kbit/s Interfaces....8 Fault and Service Status (PMA...........704) ....2........... 0...............11.........4............................5 Performance Conditions of Unframed Interfaces.............................................................1 6..................................................110 4...................... 124 5...........................11................................5................. 133 5............... 108 4.....116 4....36 48................................ 48....................................................................................28.................. 138 G....... 125 5................2 8448 kbit/s Interface (CCITT G........ 2) ........7 Reference Points of Unframed Interfaces.....2 Replacing EPROMs.11..... 130 5..................4.. V...................2 IF Signal Faults of Unframed Interfaces .5 Faults of Framed IF Rx Signal (Block 1.............................. 2 pcs ......3 6 Technical Specifications of Tellabs 8120 Mini Node M ..36/V................ 56.............................6 G703-64-M......................... 136 6..................................................................................................704 Framed Interface....... 138 6..11...............................6…64 kbit/s.7 V35-G704-SM............. n x 64 kbit/s ......................24/V.................................................3..........6 Common Faults of Unframed Interfaces ......................... 56................................................21 1..........................6 1+1 Protection Switch Fault Messages (Block 0) ...............................28 if/DCE................... 140 6...........................117 4.............3 Net Side Signal Faults of Unframed Interfaces ...................2..................................................................115 4...2................................................................................11.. 134 5..................................... n x 64 kbit/s Interfaces................12.......11..................................... 139 6........... 2 pcs . V................................2…n x 64 kbit/s Interface..........11 Connectors and Strappings of Unframed Interfaces..............................2.4...................................................................................... 123 Common Faults and Actions ....................................5 22030_12 © 2013 Tellabs.......................24/V.... 135 5........................... X... 136 Cross-Connect ........................................1 V..... TIA/EIA 612......... 134 5..........7 Miscellaneous Faults of Framed Interfaces (Block 1.................. G........................................2…19...........4 Relevant Recommendations ..............1 V35-M.......... 124 5............................................... 120 4.........................................................8 X21-G704-SM.. S) in 1+1 Mode of Framed Interfaces ................9 Fault Conditions of Framed Interfaces .................2 V36-M.... 109 4.............................................................35 48.............................. V.......................................24/V................ 132 5.................4 Test Loop Activation of Unframed Interfaces ...............7 V35/V24-M....35 n x 64 kbit/s…2 Mbit/s ..........................................................11........28 if/DTE.. V.............................................. .......... 164 Multiframe Structure in Signalling Time Slot........................................................................................6 Baseband Line Interface 64…384 kbit/s (BTE-384-M Module) .............2 X...................1 8448 kbit/s..........3 2048 kbit/s.............10 Environmental Conditions....................703 Interface (G703-75-M) ...........3 Transparent 2 Mbit/s..........12 Electromagnetic Compatibility............................................................... G.................... 162 8448 kbit/s Frame Structure ............. 56......................................................................................6.................. BTE-4096-M...................................................................... 146 6...................10......... 143 6....................................................................................................................................................................... ....................5 Optical Line Interface 2048 kbit/s / 8448 kbit/s (OTE-LED-M Module) ..... 145 6......................................................... G................................2 kbit/s.................. 149 Appendix 1: Frame Structures ...4224 kbit/s (BTE-1088-M..............11 Safety Compatibility................ 48....5.........9 Mechanics............ 166 CRC Multiframe Structure in TS0 for 2 Mbit/s and n x 64 kbit/s Frames...................................................1 Power Consumptions of Tellabs 8120 Mini Node M Units and Modules...........................................................................6............................7 Baseband Line Interfaces 320............. 146 6........................5............................................... 163 N x 64 kbit/s Frame Structure ................8..................................................................................................................................................................................................................................................... 147 6............................. 144 6...............703 Interface (G703-8M-M Module) .....2 2048 kbit/s.......6............6............................................21 1.................................................. 144 6.. 149 6............ 150 Frame Structures at Bit Rates below 48 Kbit/s .......................................................................7 Service Computer (SC) Interface ............................................. 147 6........704 Frame Structures...................................................................................................6....................................................6.....................4 2048 kbit/s and 1088 kbit/s Line Terminal Interface (LTE-M Module)............................... 148 6........ 148 6............ BTE-576-M.... n x 64 kbit/s...................2…19......1 Climatic/Mechanical Compatibility ....................... 157 Appendix 2: G....................... BTE-2048-2W-M.. 143 6.............................. 143 6........................................................................................................................................................................................................................................................................ n x 64 kbit/s............ 143 6............703 Interface (G703-120-M) ............. G................6 Data Interface Modules .8 Power Supply....................... 148 6.................. BTE-1088-2W-M and BTE-2304-M Modules) .............. BTE-320-M......................................................................................... 150 Frame Structures at Bit Rates 48…2048 Kbit/s .... 167 Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 8 22030_12 © 2013 Tellabs...................................................... 144 6.... 162 2048 kbit/s Frame Structure ... 145 6...Table of Contents 6................6...................................................................................... BTE-2048-M....................................................................... It emphasizes or supplements information in the document.com by navigating to Product Documentation > Managed Access > Tellabs 8100 Managed Access System (Includes all 81XX products) > Technical Documentation > Network Element Manuals > 8100 List of Discontinued Products.About This Manual About This Manual This section discusses the objectives and intended audience of this manual.tellabs. 22030_12 © 2013 Tellabs.portal. This is a caution symbol. It indicates that damage to equipment is possible if the instructions are not followed. Audience This manual is intended for system specialists and personnel involved in network planning. Discontinued Products Tellabs ® 8100 Managed Access System Discontinued Products list can be found in Tellabs Portal. This is a warning symbol. It indicates that bodily injury is possible if the instructions are not followed. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual and consists of the following sections: • Objectives • Audience • Discontinued Products • Document Conventions • Documentation Feedback Objectives The goal is to describe the network element features of Tellabs 8120 mini node M and its installation. www. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 9 . Document Conventions This is a note symbol. 4131.About This Manual Documentation Feedback Please contact us to suggest improvements or to report errors in our documentation: Email: fi[email protected] Fax: +358. .9.2430 Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 10 22030_12 © 2013 Tellabs. 21 depending on the used interface module. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 11 .36. This operating manual describes the version 6. Under the metallic cover there are the following parts: • main unit • switching power supply unit (AC or DC) • channel board • two user access interface modules • two framed interface modules On the front panel there are an LCD display with 2 x 24 characters. On the front panel there is a connector for the service computer. The interfaces can. 1. 8448 kbit/s and n x 64 kbit/s.1 or later of Tellabs ® 8120 mini node M (SBM 2048M). The transmission rates of unframed interfaces can be 0.24 or X.1 Introduction 1 Introduction The Tellabs 8120 mini node M has been discontinued. The configuration and control of Tellabs 8120 mini node M can be applied in different ways. The transmission rates and physical features of the interfaces depend on the used interface modules. Tellabs 8120 mini node M can make connections between interfaces of any type. The front panel of Tellabs 8120 mini node M is provided with an LCD display and keyboard (four buttons) which can handle the menu controlled user interface control functions needed when using Tellabs 8120 mini node M. Different interface modules are available for different applications.704 frame is used at n x 64 kbit/s.35. four pushbuttons. V. which can manage the configuration and control with a user interface with windows. As part of the Tellabs 8100 network. The transmission rates of framed interfaces are 2048 kbit/s. 22030_12 © 2013 Tellabs.704. This piece of equipment can be furnished with up to two framed interfaces and up to two unframed interface modules (usually two interfaces per module). Tellabs ® 8120 mini node M (SBM 2048M) is a small cross-connect device. be V. where the control channel is connected to the device through a framed interface. where n = 2…33. for example.6…2048 kbit/s. V. The frame structure of a framed interface is according to CCITT G. alarm LEDs for each channel and a connector for the service computer. which can operate either as part of the Tellabs ® 8100 managed access system network connected to Tellabs ® 8000 network manager.1 Construction Tellabs 8120 mini node M is built into a compact metallic case. or as a separate cross-connect device controlled and supervised locally. The modified G. the control can be realised through Tellabs 8000 manager. It is suitable for tabletop use. and the interfaces IF5 and IF6 are of type V. the connectors for the framed interfaces IF1 and IF2 are on the bottom row of the back panel and the connectors for the user access ports at the upper part of it. For example in Fig. . a power cord. 1 Tellabs 8120 Mini Node M Front Panel On the back panel of Tellabs 8120 mini node M there are the interface connectors. In this example the interface IF1 is G703-75-M. 2. The desired combination of modules can be selected for one piece of equipment according to the unit list. The type for interfaces IF1 and IF2 can be selected irrespective of each other.1 Introduction Fig.9 Unit List of Tellabs 8120 Mini Node M.36. An unframed interface module has typically two interfaces which are of the same type. the synchronization connectors and a measurement point connector. For further details and possible exceptions refer to 4. The connectors for framed interfaces IF1 and IF2 are on the lower part of the back panel and the connectors for user access ports on the upper part. Fig. The interfaces IF3 and IF4 are of type V. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 12 22030_12 © 2013 Tellabs. The connector type depends on the module in use.35. and the interface IF2 is OTE-LED-M. 2 Example of Tellabs 8120 Mini Node M Back Panel Connectors A framed interface module has one interface. Fig.703/G.704 frame this information is typically in time slot TS0. The cross-connect function of the equipment is independent of the channel interfaces. For example.2 Tellabs 8120 Mini Node M as Tellabs 8100 Network Element 2 Tellabs 8120 Mini Node M as Tellabs 8100 Network Element 2. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 13 . The system uses a synchronous time slot interleaved framing. the public transmission network or another transmission device with a G. 3 Architecture of Tellabs 8120 Mini Node M The trunk interfaces are provided with the CCITT G. A part of the frame is reserved for the internal information transfer of the system (frame alignment.704 framed user data A framed interface can also be a user access interface.1 General Tellabs 8120 mini node M is connected through the framed interfaces to another Tellabs 8120 mini node or a corresponding piece of equipment. Cross-connections can be made in accordance with the following: 22030_12 © 2013 Tellabs. These time slots of the trunk lines are never used for transporting cross-connect channels (XB/XD channels). a Tellabs 8100 node. it can support channel interfaces. CRC check.704 interface. The user access interfaces can be divided into two main categories: • unframed user data • G. This facilitates the flexible implementation of different channel interfaces. Like an ordinary multiplexer. Tellabs 8120 mini node M can also be described as a digital multiplexer equipped with two trunk interfaces.704/706 compliant frame structure. in the 2 Mbit/s G. The interfaces with which Tellabs 8120 mini node M is connected to the Tellabs 8100 network or to another similar piece of equipment are called trunk interfaces in this manual. network management channel). 2 Tellabs 8120 Mini Node M as Tellabs 8100 Network Element • framed/framed • framed/unframed • unframed/unframed When an interface is used for cross-connection, it is called a port. The mapping of the user access ports to the trunks by the cross-connect are based on the following signals: • time slots: n x 64 kbit/s • time slot bits: n x 8 kbit/s The n x 8 kbit/s and n x 64 kbit/s groups mapped by the channel interfaces are called XB channels. The XB channel can also be a combination of 64 kbit/s and 8 kbit/s signals. Fig. 4 XB and XD Channels If the interfaces are equipped with signalling or control signals, they are either mapped to the XB channel or to the corresponding signalling bits (n x 500 bit/s) of the XB channel. In the latter case the signals are mapped into the G.704-compliant multiframe of the 2 or 8 Mbit/s trunk. The n x 500 bit/s signalling bits are called the XD channel of the interface. Unframed interfaces do not normally use the XD channel. 2.2 Framed Interfaces IF1 and IF2 In most cases the framed interfaces of Tellabs 8120 mini node M are used as trunk interfaces. The framed interfaces (IF1, IF2) provided by Tellabs 8120 mini node M are shown in the table below. (The modules are electrically, but not mechanically, identical with the modules in the GMH unit of the Tellabs 8100 system.) Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 14 22030_12 © 2013 Tellabs. 2 Tellabs 8120 Mini Node M as Tellabs 8100 Network Element Framed Interface Modules Module Type BTE-384-M2 Electrical Interface 2W/4W Biphase code 2W 2B1Q code 2W 2B1Q code 2W/4W 2B1Q code 4W 2B1Q code 2W 2B1Q code 4W 2B1Q code 2W/4W 2B1Q code 4W 2B1Q code LTE Bit Rate n= 2…6 XB/XD Capacity1 n-2 TS for XB channels 1 TS for XD channels4 n-1 TS for XB channels n-1 TS for XB channels n-1 TS for XB channels n-2 TS for XB channels 1 TS for XD channels4 n-1 TS for XB channels n-2 TS for XB channels 1 TS for XD channels4 n-1 TS for XB channels n-2 TS for XB channels 1 TS for XD channels4 n-2 TS for XB channels 1 TS for XD channels4 30 TS for XB channels 1 TS for XD channels4 n-2 TS for XB channels 1 TS for XD channels4 n-2 TS for XB channels 1 TS for XD channels4 30 TS for XB channels 1 TS for XD channels4 120 TS for XB channels 4 TS for XD channels4 5 spare TS5 30 TS for XB channels 1 TS for XD channels4 30 TS for XB channels 1 TS for XD channels4 120 TS for XB channels 4 TS for XD channels4 5 spare TS5 BTE-320-M2 BTE-576-M2 BTE-10882W-M2 BTE-2048-M2 BTE-20482W-M2 BTE-1088-M2 BTE-2304-M2 BTE-4096-M2 LTE-M2, 3 n=5 n=5, 9 n=5, 9, 16, 17 n=16, 17, 32, 33 n=16, 17, 32, 33 n=5, 9, 17 n= 16, 17, 32, 33, 34, 36 n= 16, 17, 82, 33, 64, 66 1088 kbit/s 2048 kbit/s V35-G704-SM2 X21-G704-SM2 OTE-LED-M V.36/V.11 V.11 Optical LED n x 64 kbit/s n = 2…33 n x 64 kbit/s n = 2…33 2048 kbit/s 8448 kbit/s G703-75-M G703-120-M G703-8M-M2 G.703 G.703 G.703 2048 kbit/s 2048 kbit/s 8448 kbit/s 1TS = 64 kbit/s time slot. interface module has been discontinued. 3LTE = integrated line terminal. 4XD time slots can be turned off and used as XB time slots. 5One is used for HDLC. These five XB time slots do not have XD channels associated with them. 2The 22030_12 © 2013 Tellabs. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 15 2 Tellabs 8120 Mini Node M as Tellabs 8100 Network Element 2.3 2.3.1 User Access Ports Unframed Interfaces Tellabs 8120 mini node M supports two channel interface modules. Unframed Channel Interface Modules Module Type V35-M, V36-M6 V24-DCE-M6 V24-DTE-M6 V35/V24-M6 X21-M G703-64-M6 HSSI-M6 Mini LAN Module9 Electrical Interface V.35 or V.36/V.11 V.24/V.28 V.24/V.28 V.35-IEC X.21/X.27 G.703 co/contradir TIA/EIA 612 10Base-T Ethernet Bit Rate 0.6…4224 kbit/s7 0.6…64 kbit/s 0.6…64 kbit/s / 0.6…8192 kbit/s8 0.6…4224 kbit/s7 64 kbit/s 0.6…8448 kbit/s 64…2048 kbit/s The modules are electrically, but not mechanically, identical with the modules in the channel unit of the Tellabs 8100 system. The functions of these data interfaces are • V.110 rate adaptation for bit rates ≤ 56 kbit/s • CRC end-to-end monitoring possible with all bit rates • control signal transmission through the network (V.13 simulated carrier or in the V.110 frame) • interface, local and V.54 remote loops One end of the circuit can be any other data interface or a G.704 user access point in another Tellabs 8120 mini node or in a Tellabs 8100 node. The circuit types can be • point-to-point (pp) • broadcast (bc) Tellabs 8120 mini node M does not support the point-to-multipoint server functions as the channel unit in the Tellabs 8100 node. The user interfaces, however, can be connected as end points to a point-to-multipoint circuit when the Point-to-Multipoint (pmp) Servers (branch points) are in the Tellabs 8100 nodes. interface module has been discontinued. maximum bit rate per module is 8448 kbit/s. This capacity can be divided between two channels in the modules V35-M, V36-M and X21-M. Tellabs recommends the HSSI-M module for usage above 2 Mbit/s bit rates as it offers the possibility to have more cable length. 8Tellabs recommends the HSSI-M module for usage above 2 Mbit/s bit rates as it offers the possibility to have more cable length. 9The technical name SMU-BRIDGE can be seen in Tellabs 8000 manager. 7The 6The Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 16 22030_12 © 2013 Tellabs. It is.110 framing (≤56 kbit/s) • V. c. 22030_12 © 2013 Tellabs.21 ≤48 kbit/s) 2. Fig.2 Framed Interface as User Access Port Framed n x 64 kbit/s.3.21 C/I mapping (X. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 17 . In this case the standard procedures should be used: • V. d a/b/c/d - A typical G.110.2 Tellabs 8120 Mini Node M as Tellabs 8100 Network Element 2.4 2.110 frame • same XB/XD capacity • same XB framing of data circuits (V.3 Rules for Mixing Different Interface Types Usually. modified V. both ends of the connection use the same interface type. 2 Mbit/s or 8 Mbit/s interfaces can be used as user access interfaces in which case the interfaces are called G. Different electrical interfaces are not usually of major concern. A framed channel interface can offer several user access ports. b/c. Cross-Connectable Time Slot Fractions n x 64 kbit/s 32 kbit/s 16 kbit/s 8 kbit/s XB n x 64 kbit/s 32 kbit/s 16 kbit/s 8 kbit/s XD n x (a.704 user access port can comprise the following time slots and time slot fractions. The same alternatives are available when connecting Tellabs 8120 mini node M to a Tellabs 8100 node.704 framed user access port.110.1 Applications Framed Interfaces There are different applications for the transmission rate and the features of the framed interfaces in Tellabs 8120 mini node M. very easy to do by using the G. At least the following points must be checked between both ends: • same use of control bits in V.704 user access port is a 2 Mbit/s interface for a digital PABX. In some cases it is possible to mix different interface types. the framed interfaces provide the same features as the corresponding trunk interfaces.3.30-specified X. d) a. In principle. no framing) The structure of the XB/XD channel is not normally transported outside the network. A 2 Mbit/s G. however.13 simulated carrier (V type interfaces ≥64 kbit/s) • X.704 user access ports which means that there is no HDLC channel. b. 5 presents the different ways to interconnect two Tellabs 8120 mini node M devices.4. 2. 5 Tellabs 8120 Mini Node M Trunk Lines Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 18 22030_12 © 2013 Tellabs.2 Tellabs 8120 Mini Node M as Tellabs 8100 Network Element Fig. . STU-1088 (with BTE-1088-M). The interface complies with the corresponding Recommendations G.5-6 km depending on the cable type and the transmission rate. BTE-2304-M. The frame structure is a modified G.703/G. BTE-4096-M offer HDSL-like performance at rates 320-4224 kbit/s using 4-wire transmission. BTE-576-M.704 Recommendations.2 Tellabs 8120 Mini Node M as Tellabs 8100 Network Element BTE Modules The BTE modules10 serve baseband transmission at rates 128-4224 kbit/s. BTE-384-M uses biphase transmission for 2. module and cable characteristics. The rate can freely be allocated between all user access points by the cross-connection of the equipment. STU-2048 and STU-2304 has been discontinued. The cable length can be 4-10 km depending on the rate. The impedance of the transmission line is 120 Ω and the maximum attenuation of the transmission line can be -36 dB. BTE-4096-M and baseband modems SBM 384. BTE-1088-2W-M and BTE-2304-M offer also additional 4-wire modes at rates 320-2304 kbit/s. STU-320. BTE-1088-2W-M and BTE-2304-M offer HDSL-like performance at rates 320-2304 kbit/s using 2-wire full duplex transmission over a single wire pair. respectively). cable lengths of over two kilometers can be reached. The maximum attenuation of the transmission line is 6 dB. 11The production of the interface module LTE-M has been discontinued. The transmission rates of the LTE module are 2048 kbit/s and 1088 kbit/s. STU-1088-2W (with BTE-1088-2W-M) or STU-2304 (with BTE-2304-M). 22030_12 © 2013 Tellabs.704 frame. The impedance of the transmission line is fixed (75 or 120 Ω. BTE-384-M. G703-75-M and G703-120-M The G703-75-M and G703-120-M modules offer an interface with a transmission rate of 2048 kbit/s. BTE-2048-2W-M.703/G. BTE-320-M.704. At the 1088 kbit/s rate a modified G. 2B1Q line code. STU-1088-2W. BTE-320-M. BTE-2048-2W-M offers 2-wire full duplex operation over a single wire pair using echo cancellation. 10The production of the interface modules BTE-64-M.or 4-wire lines at rates 128-384 kbit/s. Using a BTE module. BTE-2048-M. The cable length can be up to 3. STU-2048 (with BTE-2048-M). Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 19 . STU-576 (with BTE-576-M). The line code is 2B1Q. STU-1088. Tellabs 8120 mini node M can be connected to a Tellabs 8100 node with a corresponding interface. The cable length can be 3-10 km depending on the rate. The 2048 kbit/s interface complies with G. BTE-1088-M. where the overhead of 64 kbit/s is used for the frame structure. STU-320 (with BTE-320-M). The available transmission rate for the terminal equipment is the line rate subtracted by 64 kbit/s. module and cable characteristics. BTE-1088-M. BTE-1088-2W-M. another Tellabs 8120 mini node or to table top baseband modems SBM 384A (with BTE-384-M). STU-576. BTE-576-M. BTE-2048-M. Depending on the cable type and transmission rate. The interface is designed for the interconnection of equipment in the same physical location. LTE-M11 The LTE-M module provides a line interface for a symmetrical pair cable.704 frame is used. the better one of the two received signals is selected for the terminal equipment interfaces. .11 Recommendations. V35-G704-SM and X21-G704-SM13 Tellabs 8120 mini node M can be equipped with a V35-G704-SM module.704. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 20 22030_12 © 2013 Tellabs. however. Transmission distances of several dozens of kilometers can be achieved with an OTE module. Normally. the interface timing is codirectional and the connectors are of type D with 9 pins. Tellabs 8120 mini node M should be installed near the equipment in order to be accessed. OTE-LED-M The OTE-LED-M module is an optical fiber interface. Almost all fiber types which are suitable for data transmission (not plastic-coated fibers) can be used with this module. This facilitates a transmission where the transmission rate of the signal from the terminal equipment interface is higher than the rate of a separate framed interface. production of the interface modules V35-G704-SM and X21-G704-SM has been discontinued. where the connection signal levels are according to the V. The modules V35-G704-SM and X21-G704-SM have 2 23-1 type scramblers in both transmission directions. The rate of the interface is n x 64 kbit/s (n = 2…33) and the frame structure is modified G. The impedance of the transmission line is fixed 75 Ω and the maximum allowable attenuation of the transmission line is 6 dB. The connector is of type FC. In the receive direction. Restrictions for the maximum propagation time difference between the transmission lines of the framed interfaces are set. Special Modes The interfaces IF1 and IF2 of Tellabs 8120 mini node M can be connected to 1+1 protecting mode when both interfaces transmit the same data in the transmission direction.35 or V. It is advisable to use the scramblers whenever it is possible. It is recommended that both interfaces use the symmetrical pairs located in the same cable.2 Tellabs 8120 Mini Node M as Tellabs 8100 Network Element G703-8M-M12 The G703-8M-M module is similar to G703-75-M but with a transmission rate of 8448 kbit/s. where the signal from the terminal equipment interface is distributed to the two framed connections and returned at the receiving end in its original form. The transmission rates are 2048 kbit/s and 8448 kbit/s.2 Unframed Interfaces The unframed interfaces of Tellabs 8120 mini node M support user bit rates 600 bit/s…8448 kbit/s. The interface is designed for the connection of Tellabs 8120 mini node M to the V series interface provided by the public data transmission network. 2. The scramblers can be used when the transmission rate is 31 x 64 kbit/s or lower except by the unframed mode.704. using the bit rate of n x 64 kbit/s. The protection can be realised with any two modules with the same transmission rate. and the frame structure is according to G. 12The 13The production of the interface module G703-8M-M has been discontinued. This duplication is used in order to protect the transmission. where the scramblers cannot be used. The interfaces IF1 and IF2 can use the split trunk transmission method as well.4. 36. however. X21 G. X21 V35.8 7. 17A separate 8.21 interface is done for bit rates ≤48 kbit/s according to the Recommendation X. V. X21 V24. modified V. X21 V35. possible to map the data with an additional n x 8 kbit/s frame which includes end-to-end monitoring (CRC) and network-independent clocking for channels.110 V.4 48 56 72 80 144 160 n x 64 n x 64 64 Interface Type V24. X21 V24.2 Tellabs 8120 Mini Node M as Tellabs 8100 Network Element Unframed Channel Interface Types Interface Bit Rate kbit/s 0. It is.703 (co or contradir) XB Bit Rate kbit/s 8 16 32 64 64 64 72 (+8 or 16) 80 (+8 or 16) 152 (+8) 160 (+8 or 16) n x 64 (+8. The XB structure in the table above refers to the framing or coding of user data when it is mapped into the trunk. 36. X21 V35. X21 V35.24/V. X21 V35.110 frame in the data interface types <64 kbit/s.110 is a typical frame used for data connections and it is used in an ISDN network for the rate adaptation of V and X series interfaces. X21 V24. 16 or 24 kbit/s frame can be used (CRC.110). 36.2 38. 35.2…9.110 V. 36.16 or 24) n x 64 (+8 or 24) 64 +(8) Structure V.110 framing can be used (CRC error monitoring and network independent clocking). The framing is used between the user access ports of the connection and it is not visible outside the trunks of the network.13 Notes 1415 1415 1415 1415 1615 1615 17 17 17 17 17 18 17 V. 105/109 and network independent clocking). With bit rates n x 64 kbit/s it is only possible to map the user data into the XB/XD channel. 36. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 21 .110 frame frame frame frame frame V. At bit rates 56 kbit/s and n x 64 kbit/s the C/I can be mapped through the network but it is proprietary. X21 V24. 36. synchronous bit rates of up to 64 kbit/s are supported.14 synchronous/asynchronous conversion is used. 36. 35. 36.13 (can be turned off).30 (compatible with V.110 framing can be used (CRC error monitoring is included).28 can be synchronous or asynchronous. 15Also 14A 22030_12 © 2013 Tellabs.110 V. The ITU-T-specified V. X21 V24. The bit rate of the additional frame is presented below.110 V.6 14. 18Simulated carrier function according to Recommendation V. The C/I control signal mapping of the X.110 V. X21 V35. 16A modified V. A separate 8 or 24 kbit/s frame can be used (CRC and network independent clocking).4…19.6…4. The end-to-end connection is monitored and supervised by the V. Bit Rate of Additional Frame 105/109 Transfer CRC Network Independent Clocking User Rate ≤512 kbit/s Frame Rate kbit/s 8 ON ON ON ON 8 8 16 User Rate >512 kbit/s Frame Rate kbit/s 8 8 24 16 ON special. LAN bridges and routers • data links between two computers • trunks of low or medium capacity data networks The typical applications for the high speed interfaces V35.2 Tellabs 8120 Mini Node M as Tellabs 8100 Network Element 105/109 Transfer CRC Network Independent Clocking ON User Rate ≤512 kbit/s Frame Rate kbit/s 16 16 8 User Rate >512 kbit/s Frame Rate kbit/s 24 24 24 ON ON ON ON ON ON The end-to-end monitoring supervises the XB/XD signal path through the network.21 or X.28 (≤0. The standard V.4 kbit/s and n x 3. The CRC monitored ports count errored CRC blocks which include every bit of the user signal.2 kbit/s may be used for access links to data networks using 6+2 (n x 3.6…38.2.0 and n x 3. n x 1.24/V.0 kbit/s) signalling formats.2. V.6 kbit/s) are • termination of point-to-point circuits in a data processing centre • end point of point-to-multipoint circuits in the Tellabs 8100 network • termination of V.110 framing for low speed interfaces also supports the network independent clocking.6…19. V.21 bis mode the X. HSSI (64…8448 kbit/s) are • links for data multiplexers. 48.28 at rates n x 3.24/V.2 kbit/s) or 8+2 (n x 3. 38. and n x 64 kbit/s) are • termination of point-to-point circuits in a data processing centre • end point of point-to-multipoint circuits in the Tellabs 8100 network • links for data multiplexers. 48. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 22 22030_12 © 2013 Tellabs.36 (≤9.21 at rates 0.110 formatted circuits The typical applications for the medium speed interfaces V. . Interfaces X. routers • data links between two computers • trunks of low or medium capacity data networks The typical applications for the LAN module (64…2048 kbit/s) are • LAN interconnection Low speed interfaces V.25 data networks.36. In X.110 framed port does this by counting errored frames. PADs.4.35. 56.6. PADs • links for LAN bridges. The typical applications for the low-speed interfaces V. Network independent clocking means that the user’s DTE equipment can provide timing for transmission data which is not frequency-synchronized to the network clock. 64 and (n x 64) kbit/s may be used for X.21 access links to X. A V.21 interface may be applicable for a variety of applications with data multiplexers etc. 703 interface is mainly used for transfer between the Tellabs 8100 network and another transport network or switching system based on the G. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 23 .700 Series ITU-T Recommendations. 22030_12 © 2013 Tellabs. 2. the buffer memories of the framed interfaces require that the average bit rate in the incoming signals is the same in all trunks (mesochronous clocks).703 interface. This practise can be used if an accurate station clock is available. The following clock faults are recognized: • loss of clock or signal • loss of frame alignment at a clock interface • far-end alarm concerning the loss of the reference clock of the node Two examples on the synchronization of Tellabs 8120 mini node M are given below. In this practise the equipment uses exclusively the external clock input (EXT CLK). which gives timing to the cross-connect switch. The same requirement usually applies to the synchronous n x 64 kbit/s data interfaces (user access ports). Some computers and data multiplexers may also be equipped with a 64 kbit/s G. Tellabs 8120 mini node M is provided with an internal master clock.5 Network Synchronization Trunks use the synchronous octet interleaving. Some data interface types allow the use of a plesiochronous clock in the user access ports. The master clock can be locked to • an external n x 64 kHz clock input • an incoming n x 64 kHz clock of a trunk or channel interface If the master clock is not locked to any external reference timing.2 Tellabs 8120 Mini Node M as Tellabs 8100 Network Element The G. The clock reference source is defined by a clock fallback list which can have up to five clock entries. 6 Independent Timing of Network Nodes Nodes can be timed independently of one another. Fig. the clock operates in an internal mode with an accuracy of ±30 ppm. One piece is the master and the clock is distributed via the network to the other pieces.2 Tellabs 8120 Mini Node M as Tellabs 8100 Network Element Fig. The clock distribution network can make use of reserve routes. Both pieces should not be synchronized at the same time to the trunk coming from the other end because it causes a closed timing loop and corruption of data transfer. The selection of the reserve clock route must be done so that the change-over to a reserve route does not cause a closed timing loop. The network is normally locked to an external clock source via the network master equipment or to the internal clock of the master. . 7 Synchronization through Trunk The usual practise with two pieces of equipment is to synchronize one to the external clock or to use its internal clock. The same practise can also be used if there are many pieces of equipment in the same network. The other piece is synchronized to the trunk coming from the master equipment. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 24 22030_12 © 2013 Tellabs. A change-over is based on the clock faults criteria. 8 Tellabs 8120 Mini Node M Functional Block Diagram The common functional blocks of Tellabs 8120 mini node M are • G.704 framed interfaces IF1 and IF2 • cross-connect block • microprocessor block for control functions • keyboard and display • AC/DC power supply or DC/DC power supply 22030_12 © 2013 Tellabs. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 25 .1 General The functional block diagram is presented in Fig. Fig.3 Operation 3 Operation 3. 8. 704 framing block. In the transmitting direction the Tx frame block creates a signal by mapping data from the X-bus into the correct time slots. the Rx frame block can extract the data transmission time slots. For instance. The length of the receiving buffers can be changed in accordance with the application requirements. When the synchronization is found. A modified G. . The frame structure and the use of the certain bits in the frame depend on the transmission speed. These buffers also form a flexible buffer in order to compensate for minor momentary speed differences between the X-bus and the received signal. The transmit buffers also synchronise the phase of the transmitted frame with the phase of the X-bus and stuff idle data in the unused time slots of the frame. At 2048 kbit/s and 8448 kbit/s the frame structure is in accordance with G.704.704 Framed Interfaces IF1 and IF2 The G.704 frame structure is used for other speeds.704 framing block processes framed signals at 8448 kbit/s.704 framing block are located on the main board. 3. 2048 kbit/s and n x 64 kbit/s. be G. for example. and. adding frame alignment signal bits and the CRC check sum. the cross-connect block and the G. at certain speeds. and recover and supply the HDLC channel to the processor. The block includes two independent transmission channels to carry data and also to provide an internal communication link of the Tellabs 8100 system. optical interfaces.703 interfaces. In the G. The channel board and two changeable user access interface modules are located over the main board and the framed interface modules. it is also possible to remove the framing and have the channel to operate in transparent mode. check the CRC check sum.3 Operation The microprocessor block. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 26 22030_12 © 2013 Tellabs. The receiving buffers of the channels store incoming data so that required time slots are always available for the cross-connect block.704 framing block there are data buffers for the data transmission. The transmission channel interfaces are independent of each other and they may. The keyboard and the display are on the front panel. The transmit buffers of the channels are used to store data so that there is always a time slot available to be transmitted by the Tx frame block.2 G. in some cases a minimum connection delay is required whereas in plesiochronous operation slips should occur as seldom as possible. If required. Two changeable interface modules for framed interfaces are located on the main board and connected through connectors to the framing block. also baseband interfaces. The framed signal which is carried on the transmission line is assembled and disassembled in the G. The cross-connect and microprocessor busses connect the channel board and the main board together. In the receiving direction the Rx frame block searches the received signal for the frame synchronization word. The power supply is a separate board connected through cables to the main board and covered with a metallic shield to prevent the main current causing a hazard when the case is opened. and by generating the HDLC channel at a required position within the frame with the aid of the processor. 80 of Appendix 2 and the 2 Mbit/s frame structure in Fig.704 compliant CRC check in order to detect errors in the received signal and to prevent alignment to an imitative frame alignment word. The 8 Mbit/s frame structure is shown in Fig. 68. 81 of Appendix 2. The framed interface lines primarily use the following time slots for XB channels.704 multiframe structure of the signalling time slot. 34…65. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 27 . 17…n-1 Total 120 TSs Total 30 TSs Total n-2 TSs if n ≤17 Total n-2 TSs if n ≥18 The table of Multiframe Structure in Signalling Time Slot in Appendix 2 shows the G. 71…98.1 Frame and Multiframe Structure The unit has two independent G. 100…131 TS 1…15. The frame length is n time slots.3 Operation 3. Frame 8 Mbit/s 2 Mbit/s n x 64 kbit/s Time Slot TS99 TS0/B1 TS0/B1 CRC Check CRC-6 CRC-4 CRC-4 22030_12 © 2013 Tellabs.704 Specification. For the transmission of the XD channels the following time slots are used: 8 Mbit/s 2 Mbit/s n x 64 kbit/s TS 67. The frame has the following three modes. The CRC check is inserted into the different frame structures in the following way. On the user access lines the CRC check can be turned off if the user equipment does not support the CRC frame structure. and in the 8 Mbit/s frame each group has its own signalling time slot (TS67…70). • 8448 kbit/s = 132 TS • 2048 kbit/s = 32 TS • n x 64 kbit/s = n TS The 2 Mbit/s and 8 Mbit/s frame structures conform with ITU-T G. The 2 Mbit/s frame has one signalling time slot (TS16). For further details see Appendix 2. if n ≥18. or in TS16. 69. Possible signalling bits are in the last time slot of the frame.704 framed interfaces. 17…31 TS 1…n-2 TS 1…15.2. The main features of the n x 64 kbit/s frame are the same as those of the 2 Mbit/s frame. The 8 Mbit/s signal has four 2 Mbit/s groups (thirty time slots). 70 TS 16 TS n-1 if n ≤17 TS16 if n ≥18 The trunk lines always use the G. 8 Mbit/s 2 Mbit/s n x 64 kbit/s TS 5…32. the receiver writes the time slot data into the Rx buffer clocked by the received frame. Frame Buffers The buffers have four operating modes. the buffer must control that the write and read operations do not simultaneously address the same time slot. centred. The transmit buffer length is two frames.2. Therefore. This transmit buffer arrangement causes a delay of one frame (125 µs). or when the transmission is plesiochronous.2 Buffers In the transmit direction the buffer supplies time slot data from the X-bus to the frame to be transmitted. The frame multiplexing circuits will fetch the data when they are transmitting the corresponding time slot. one of them has to be moved. The length of the interval depends on the frequency difference and on the buffer mode. Buffer Mode 4 Fr19 8 Fr 8 Fr/Split 64 Fr Rx Delay (Frames) 1…3 1…7 2…6 1…63 Tx Delay (Frames) 1 1 1 1 Usage Framed user access interfaces. The frame multiplexing block reads the first frame area and the bus writes into the second frame area. e. The unit stores the data in its transmit buffer in a position corresponding to the position of the time slot in the frame. it also specifies the time slot concerned. Usually. in other words. n x 64 kbit/s trunks Special use Split trunk line components Special use. the buffer has to be centred at regular intervals. and the change is always one frame or a multiple of a frame.g. The centring is made by changing the read address. When the cross-connect block via the X-bus requests data from the interface block. If a plesiochronous system constantly exhibits a frequency difference in the same direction. small slip rate in plesiochronous use In a plesiochronous system the interval between the centring situations is: 19Fr = frame = 125 µs Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 28 22030_12 © 2013 Tellabs. on the other hand. the phase of the received frame does not coincide with the frame phase of the X-bus. . The centring causes a certain number of frames to be lost or retransmitted. When the cross-connect block supplies data to the X-bus. Centring is required when equipment is powered up. the Rx buffer has to control that the read and write operations do not collide. As it is possible to write the data from the bus to any time slot position in the buffer.3 Operation 3. when a received signal contains disturbances. If the read and write addresses come too close. it also adds information about the location in the transmitted frame where the data is to be placed. In the receiving direction the buffer supplies received time slot data from the demultiplexed frame to the X-bus. in spite of speed fluctuations and jitter. The long buffer leads to a delay of up to 63 frames.3 Operation Buffer Mode 4 Fr20 8 Fr 8 Fr/Split 64 Fr n x 64 kbit/s n x 8/df21 4 x n x 8/df 2 x n x 8/df 32 x n x 8/df 2048 kbit/s 256/df 1024/df 512/df 8192/df 8448 kbit/s 1056/df 4224/df The 4 Fr buffer is the normal mode of the buffer. thus. the received signalling data has to be buffered until the cross-connect block performs the cross-connect function for the data concerned. 22030_12 © 2013 Tellabs. Multiframe Buffers In the transmitting direction the signalling data is directed through the same buffer as the time slot data. The multiframe buffer length depends on the selected length of the frame buffer. Thus. It may also be used for other applications. this buffer mode is recommended for special purposes only. unusually large fluctuations have to be handled correctly or if the frame alternation has to be intact after the centring as well. This buffer mode can be used at 2048 kbit/s and n x 64 kbit/s. Thus. 23The multiframe length is 2 ms. Frame Buffer Mode22 4…8 frames 64 frames Multiframe Buffer Mode23 2 MFr 4 MFr MFr-Rx Delay 0…2 MFr 1…3 MFr MFr-Tx Delay 1 Fr 1 Fr The time slot data and signalling data have separate buffers. the signalling data and the time slot data have equal delays in the transmitting direction. A buffer with a length of eight frames is used for split trunk operation. The framing block generates a synchronization time slot in the first frame of the signalling multiframe. The cross-connect block supplies the frame signalling data. In the receiving direction the phase of the received signal multiframe usually differs from the phase of the X-bus multiframe. for example. This means that the signalling data and the time slot data which are placed in a transmitted frame do not necessarily originate from the same frame. Therefore. There are two alternatives for the multiframe buffer length: two and four multiframes. along with the other time slot data of the frame. 22The length of a frame is 125 µs. there are different delays in the processing of signalling data and time slot data. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 29 . The slip distance is very large in a plesiochronous system and the buffer is well suited for large frequency fluctuations. it should be used if. The signalling multiframe of the frame to be transmitted is synchronized to the multiframe clock of the X-bus. 20Fr 21df = frame = 125 µs = frequency difference between the signal received from the line and the receiving frequency generated by the master clock oscillator. The port numbers for data ports of interfaces correspond to the interface numbers. The receiving direction includes a change-over switch that selects the active receiver. This operation causes data time slots sent from a transmitting node in the same frame to be read together within one frame into the cross-connect block of the receiving equipment.5 frames. In the transmitting direction the interface transmit buffers and the Tx frame multiplexers are synchronized with the X-bus MSYN signal to transmit in the same multiframe phase. or TS16. if it is possible. a unidirectional channel from the control port of the master channel to the control port of the slave channel must be created. One of the interfaces will function as a master and the others as slaves. Those lines which carry one or more data channels with signalling data will use the last time slot. The interfaces are synchronized to each other by their CRC4 multiframe structure. however. Rx signal faults are classified into several categories. The split trunk mode can be used for line speeds n x 64 kbit/s and 2048 kbit/s when a frame with CRC4 is used. the worst or most serious fault. the maximum delay allowed between lines in a split trunk line is 0. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 30 22030_12 © 2013 Tellabs.2. The fault categories are indicated in the fault table. Theoretically. It is not necessary to use a CAS time slot for lines that do not include data channels with signalling. In the protected mode both channels must have the same rate and framing mode settings. In Tellabs 8120 mini node M the control port numbers are 20 for IF1 and 21 for IF2. The time integrity of the time slots in the split trunk line is preserved even if the n x 64 kbit/s is connected through physically separated cables. Split components must have the same bit rate. In the protected mode both channels transmit the same data signal coming from a buffer. Due to technical reasons. 1.x means first category. as a signalling channel with a multiframe structure. Framed interfaces working in the protected mode will look like one cross-connect port towards the X-bus. For example. Each line of a split trunk line will handle its own signalling data.3 Split Trunk Lines A split trunk line can be used to combine two parallel n x 64 kbit/s or 2048 kbit/s interfaces in order to increase the maximum number of time slots of a n x 64 kbit/s trunk interface.4 1+1 Protection The interface can be 1+1 protected by another framed interface. which will centre their own receiving buffers to the same phase. The switch uses fault categories to select the interface to be used. The split trunk mode always requires long buffers (8 frames). the maximum delay is 50 µs.3 Operation 3. 3. Both channels use their own frame mux to create the frame structure.2. . In the receiving direction the master interface sends information about its receiving buffer read phase to the slaves. When making cross-connection for a split trunk. No switch-over operation is activated when the categories are the same for both interfaces.703 type or optical modules are used. 2. Line codes are coded/decoded in the framing block when modules of G. where n = 0…6000. 3. The interface modules contain the analog components required for the interface and also the analog components needed for generating the input and the output clocks. In prefer operating mode a switch-over is triggered if there is a difference between the interface fault categories. in baseband modules the line coding is performed in the module. The delay is defined as n x 10 ms. In a situation with equal fault categories for both interfaces the switch selects the preferred interface. 5. Each module type supports defined transmission rates which can be selected with the user interface. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 31 .3 Operation Fig. The delay defines the allowed fault duration before the switch is triggered to switch-over. In this situation the Protection Switch Forced fault message with status MEI (maintenance event information) appears. OK) of the active interface is continuously worse than the fault category of the other interface for a longer period than the given time delay. 22030_12 © 2013 Tellabs. In forced operating mode the switch is forced to switch over without delay.3 Operation of Framed Interfaces Tellabs 8120 mini node M is connected to a transmission line through interface modules. 3. 9 Protection Mode of Framed Interfaces The operating modes of the change-over switch are • normal operation • prefer operation • forced operation In normal operating mode the switch will automatically switch to the other interface if the Rx signal fault category (1. The signals between the framing block and the interface module are digital signals which are converted to the transmission line level in the module. the delay is 0…1 minutes. A switch operating time delay is defined for the prefer and normal operating modes. 4. in other words. The better interface is switched into being active. Received data from the active interface is immediately connected to the X-bus. The codes and the available transmission rates are described in Technical Specifications. and the red LED is turned on. the module sets an AIS signal to the framing block and at the same time activates a missing signal alarm via the processor bus.g. if it is too low or missing completely. can be selected through the bus. NRZ data for baseband interfaces is connected to the interface module where it is coded and transformed into a line level signal. In the receive direction the interface module regenerates the coded signal received from the transmission line and transforms the signal to the digital level.g. which uses it to decode the line code and to demultiplex the frame. e. a missing incoming signal. The coded digital data is connected to the interface module where it is converted to a line level signal.3 Operation The processor bus is connected to both interface module connectors. The framing block generates the frame structure for the data in the transmit direction. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 32 22030_12 © 2013 Tellabs. 10 Data and Clock Processing in the Receive Direction The receive direction clock is recovered from the data in the interface module.703 interfaces and for optical interfaces. Parameters which define the module functions. the interface module replaces the received clock with the transmitted clock. The line code of the data is generated in the framing block for G. The clock is supplied to the framing block. If there is no received signal. . the transmission rate and possible looping commands. The missing signal alarm with V series modules is based on detecting the incoming clock signal. Through this bus it is possible to detect the module type and to read data regarding the module status. Fig. e. The clock to the synchronization bus is disconnected if there is a received signal failure. The received clock from both framed interfaces is connected to the synchronization bus where the processor can select a desired clock to be used as a synchronization signal for the master clock of the equipment. The receive clock in the V series modules is taken from the circuit 113 from line. The module monitors the level of the received signal. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 33 . If the C16M clock is missing. 22030_12 © 2013 Tellabs. but the time slot data and possible multiframe signalling are set to AIS. If the C16M clock is missing. the output clock is generated by using the oscillator of the interface module. Fig. the output signal is generated with the aid of the clock signal from the interface module crystal oscillator. which then is used to create the frame and to generate the output pulses in the coder. Even if the C16M clock is missing. This divided clock is used to create the frame and to generate the output pulses in the coder. 12 Transmit Direction Clock and Data Generation at 2048 kbit/s The transmit direction clock for 2048 kbit/s and 1088 kbit/s is generated by the phase-locked crystal oscillator of the interface module. In all cases the transmit direction clock is phase-locked to the C16M frame clock received from the X-bus. a frame is transmitted.3 Operation Fig. The phase-locked oscillator will then be adjusted to its nominal frequency and the time slot data in the frame is set to AIS. 11 Transmit Direction Clock and Data Generation at 8448 kbit/s The transmit direction clock generation depends on the interface module and the transmission rate. The oscillator is locked to the C16M clock of the bus which is used to create the frame and to generate the output pulses in the coder. The transmit direction clock for 8448 kbit/s is usually generated by dividing the bus clock C16M by two. a voltage received from a baseband module controlling the baseband line power-off situation. it is thus possible to update these programs without opening the case of the device. The control voltage is. The dividing process may cause some jitter to the clock in this case. the clock generated by the module is connected to the framing circuit. In case of power interruption the unit is automatically reset to the conditions prevailing before the interruption. The line coded data is then generated with the aid of the phase-locked oscillator clock signal. 13 Transmitting Direction Clock and Data Generation in Baseband Modules The clock which is used to create the frames for baseband modules is generated in the framing block by dividing the C16M bus clock by a programmable divider to the nominal transmission rate. where the phase-locked oscillator is locked to the clock. This clock signal and the data to be transmitted are supplied to the module. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 34 22030_12 © 2013 Tellabs. If the C16M clock is missing. again. is generated by the framing block. The transmit direction clock for V35-G704-SM and X21-G704-SM modules is generated by dividing the C16M clock by a suitable divider. The clock. without specific parametrisation. no signal or clock is sent from the module.g. The RAM memory of the processor operates as a working storage containing e. This clock is used as the transmit clock of the module in circuit 115.4 Unit Controller The unit is controlled with an 80C186 microprocessor. . The non-volatile memory is also used to store the operating parameters and the serial number of the unit. and the frame and a possible control channel are transmitted. The application programs are stored in non-volatile FLASH memories. but all other data is set to AIS. error counters and data buffers for the HDLC links and the frame control bus. If the C16M clock is missing. for instance. The output signal rate is adjusted to its nominal value. The unit includes a multichannel analog-to-digital converter (A/D) which monitors the operating voltages and also the control voltage from the interface module connectors.3 Operation Fig. The system program is stored on the board in two interchangeable EPROM memories. 3. 22030_12 © 2013 Tellabs. The G. The cross-connection bus contains approximately 1050 cross-connectable time slots (8-bit bytes). The cross-connect switch combines the needed new bytes for the interfaces by using 8 kbit/s granularity. The C16M clock is also the central clock of the equipment. is placed in the unused time slots. The bus supplies frame alignment and multiframe alignment signals to the frame buffers. These port numbers are used to specify the port used by the payload data of the interface.5 Cross-Connect Block The cross-connect block has the following main functions: • cross-connection of XB and XD channels • control of the cross-connect bus • master clock oscillator of the unit • interface for external clock input and output • selection of a reference signal for the master clock oscillator • selection of a clock signal for the external clock output The cross-connection is done in the switching matrix of the cross-connect block. which can be defined in the user interface. The port numbers for framed interfaces are 1 and 2.3 Operation 3. Other port numbers are reserved for control channels.1 Cross-Connection The cross-connect block executes the cross-connection commands from the NMS or from the front panel user interface. Bus functions are also monitored by the interface blocks. the unit will activate the IA Activity Missing alarm if it cannot receive its channel address from the bus. The interface blocks monitor the combined information formed by the bus clock and multiframe synchronization signal.704 framing block receives from the cross-connect block the time slot address which directs the bus data transmission to one selected time slot at a time. and some time slots can be unused. 3. Every interface has one or more cross-connect ports. By means of cross-connection the data of the user access interface is placed in the selected time slots of the framed interface or in an another user access interface. Received and transmitted data is carried on separate 8-bit-wide busses. Thus. In this case the free TS data. The port is a description of interface properties for the cross-connection block. The delay caused by the cross-connection is one 8-kHz frame (125 µs). The cross-connect commands are stored in a non-volatile memory. Time slots from a framed interface can also be connected to freely selectable time slots of another framed interface. it is used to create clock frequencies for the transmitted signals. whole time slots or bytes are cross-connected. if this information is missing. The cross-connect block supplies the C16M bus clock through the X-bus.5. The bits from the interface blocks are collected by using this bus. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 35 . corresponding to the interface numbers IF1 and IF2. When the interface is synchronized and the corresponding cross-connection is made. Usually. the data from the framed interface can consist of data from several interfaces. the unit will activate the Bus Sync Missing alarm. The port numbers for user access interfaces are dependent on the used channel board and user access interface modules. The cross-connect block exchanges data with the interface units by placing a channel address on the X-bus which activates the data buffers of the corresponding channel. . The cross-connect cannot be made before the port is locked.704 compliant multiframe of the 2 or 8 Mbit/s trunk. Four signalling bits are reserved for each time slot.3 Operation The cross-connection ports are defined by using interface definition. Even if only some of the bits are needed. The cross-connect types supported by the unit are 1. A cross-connect command made to one port causes a cross-connection to both interfaces. c. 2. b. d) The a. If need be. they are either mapped to the XB channel or to the corresponding signalling bits (n x 500 bit/s) of the XD channel. Protection Connection The framed interfaces in protected mode will look like one cross-connect port towards the X-bus. and its direction is from master to slave. This means that the properties of the port are transferred to the cross-connect block which needs the information for capacity allocation. all four bits are cross-connected and transferred to the far-end channel interface. b. The n x 500 bit/s signalling bits are called the XD channel of the interface. The parameters of the interface can be changed if the port is in unlocked state. XB Capacity TSn/B1…B8 64 kbit/s TSn/B1…B4 32 kbit/s TSn/B5…B8 32 kbit/s XD Capacity 4 bits (a. d bits in G. Port Locking After the operator has changed the parameters of the interface to the desired state. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 36 22030_12 © 2013 Tellabs. TS definition and a possible bit mask (n x 8 kbit/s connections). the cross-connection commands can include the signalling bits. In the latter case the signals are mapped to the G. Bidirectional connection: interface/(TS/bits) ⇔ interface/(TS/bits) Unidirectional connection: interface/(TS/bits) → interface/(TS/bits) The n x 8 kbit/s and n x 64 kbit/s groups mapped by the interfaces are called the XB channel. Signalling bits are reserved for the XB channel in the following way. The bit mask means a combination of eight bits. b) 2 bits (c.704 multiframe correspond to the XB channel time slots in the G. The port number for the protected ports is 1. and d bits of the XD channel in the G. The capacity reserved by XB and XD channels is determined by the interface type and the user requirements. the parameters of the interface must be locked. The control channel is made by unidirectional connection command. Split Trunk Connection In split trunk mode there is always a master and a slave. where state 1 indicates an 8 kbit/s channel of a time slot which is connected. c.704 structure) 2 bits (a. and the port cannot be unlocked if there are any cross-connections made to the port. If the interfaces are equipped with signalling or control signals. The mask can also be presented in hexadecimal format. The number of the signalling bits depends on the capacity of the XB channel. state 0 means capacity left free. The XB channel can be a combination of 64 kbit/s and 8 kbit/s signals. In Tellabs 8120 mini node M the control port number is 20 for IF1and 21 for IF2.704 frame. The data buffer of the slave follows the action of the master interface through a control channel created by the cross-connection. IF_ • 3. Clock Fallback List The clock fallback list defines the interfaces which can be used for synchronization. there is no activated alarm related to the master clock even if the last entry of the fallback list would be used. The master clock is usually synchronized to an incoming data signal (generally a 2 Mbit/s trunk. IF_ (Internal) The last entry is automatically followed by the internal state. If for some reason the neighbour node changes its clock signal used for synchronization. 22030_12 © 2013 Tellabs. The clock of the desired interface is derived by using a separate sync clock bus. the QL of this new reference clock is transmitted via the HDLC channel. The list can have up to five entries. This information is called Quality Level (QL) and it has been defined as numerical values from 1 to 7 where 1 is the highest and 6 the lowest one (7 means do not use this clock. Quality Level (QL) of Clock Signal When a HDLC channel is used at interface (IF1…IF3) and the Message Sending option is activated. The cross-connect block controls the status of the synchronization clock and tells the required interface to connect the received clock of the interface to this bus. If clock signals have the same QL. The clock signal which has the highest QL and whose status is OK is the one to which the master clock is synchronized.5 Network Synchronization on network synchronization). It also describes the priority order for situations where two or more clock signals have the same QL. Whenever all the clock signals are available for synchronization (the status of the clocks is OK). the clock to which it is synchronized is the one with the highest priority according to the fallback list. IF_ • 2. The QL of the internal clock is normally fixed to 6. The QL of the clock signal from an interface which does not use the HDLC channel is fixed to value 1. The form of the list is • 1. the figure is used to prevent timing loops).5. Tellabs 8120 mini node M polls these QL values from all the interfaces and thus can select the best available clock signal. Tellabs 8120 mini node M may receive messages from its neighbour node. see 2.2 Master Clock Synchronization The 16 MHz master clock of the equipment is used for generating the timing of the cross-connect bus. The timing consists of • 16 MHz • 8 kHz frame synchronization • 500 Hz multiframe synchronization The 16 MHz clock is also used to generate the Tx clock of each data interface. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 37 . Some of these messages include information about the clock signal to which this neighbour node is synchronized.3 Operation 3. 24. The master clock of the equipment can be synchronized to the clock received from the unframed interfaces through the sync bus. the equipment supports end-to-end CRC supervision of the user signals and plesiochronous data timing. Whenever required. Note that the HSSI-M interface module and Mini LAN Module support only one channel per module. It supports four independent data transmission interfaces. At higher rates an extra transmission capacity of 8. This buffer can be used if the buffer length in the base unit is not sufficient. The available interface types support V. At rates below 64 kbit/s the CRC and plesiochronous timing features are supported in the V.30.110 frame. The receiver circuits convert the incoming signal levels to CMOS level data.6 kbit/s…8448 kbit/s. V.g. or G. both supporting two channel interfaces. There is an additional 16-bit input buffer on the V24-DTE-M module. timing and control signals to balanced or unbalanced V. The interface modules convert the CMOS level data.703 co. 16. 32 or 64 kbit/s across the network.6. The interface module monitors the existence of the received signal level. according to the requirements for each interface type.703. V. Interface Modules Tellabs 8120 mini node M accesses the physical interfaces through the interface modules. The V.110 signals are transported as 8. or sync/async converter) is performed in the channel board. The n x 64 kbit/s signals are transported at the user rate across the network. X. There are also data and address busses for the microprocessor controls.36. V.and contradirectional operation. The board can take two interface modules. The data formatting circuitry is described in more detail in 3.1 Data Formatting Functions. G. Asynchronous start-stop signals are supported at bit rates below 256 kbit/s.10. V. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 38 22030_12 © 2013 Tellabs.21.6 Operation of Unframed Channel Interfaces IF3-IF6 The channel interface board accesses unframed user signals at rates 0.703 (64 kbit/s). a power off signal indication is given to the unit controller. Bus Interfaces The bus interfaces perform the adaptation between the data formatting circuitry and the data bus and the address bus of the main board of the equipment. User signals at bit rates below 64 kbit/s are rate-adapted in accordance with the frame structure V. G.110/X. 16 or 24 kbit/s is required across the network.28. HSSI or 10Base-T interfaces. The basic functional blocks of the channel board are • data formatting circuitry • bus interfaces • interface modules Data Formatting Circuitry The data formatting circuitry determines the majority of the characteristics of the data interfaces provided by the channel board.35. The interface signal coding (e.3 Operation 3. .11. clock and control signals. if the signal is missing. 32 or 64 kbit/s which can be handled by the cross-connect block and the routing tools. The V.21 test loops • test pattern generation and error counting Fig.3 Operation 3. rate-adapted to 8. 22030_12 © 2013 Tellabs. G.6.54 and X. 16.110 frame is transparently transported through the network and can be used for the end-to-end monitoring of the channel quality.703) • sync/async conversion • V.1 Data Formatting Functions The data formatting circuitry provides the main data processing functions: • rate adaptation and framing • CRC monitoring • V. 14 Functional Block Diagram of Channel Board Rate Adaptation and Framing Bit Rates <64 kbit/s Data bit rates ≤64 kbit/s are.13 simulated carrier • bit rate generation • user interface signal coding (e. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 39 . using the ITU-T Method V.g.110. The V. 32 kbit/s the user data is transferred in one. Rates 144 and 160 kbit/s need two full time slots and three or four bits of a third one (144 kbit/s uses one extra bit due to an ASIC restriction).110S and X. or at minimum one byte of jitter and wander.110 and V. The channel X carries both the signal 106 and the far-end alarm.6.110S. User data rates < 600 bit/s are transferred by sampling at rate 4800 bit/s. and X. When the 107/108 transfer is not required. both SA and SB (SA+SB = S) may carry the 105/109 or C/I signal.110 table 7b and 7c) framing is supported.2. and the basic V.2 kbit/s (data network formats 6+2 bits) and n x 3.110 or V. c refer to V. The rates 48 kbit/s and 56 kbit/s are selected as 6 x 8 and 7 x 8 kbit/s in the management menu.110b and V.110. Bit Rates n x 64+8 kbit/s The n x 64+8 kbit/s rate is basically intended for the T1 rate 1544 kbit/s. enabling the minimum control signal delay. .8 kbit/s) are supported in modes V. and 48 kbit/s are supported in V. The S signal is sampled once for each byte of user data. They are called SA.30 modes.0 kbit/s (data network formats 8+2 bits). The byte oriented buffering and minimum control signal delay is called X.3 Operation The V. The signal 106 is either derived locally from the signal 105 or from the channel X received from the far-end. n x 3.110S or X.6 kbit/s (including rates 3.30 as the mode conforms to the CCITT Recommendation X.110 mode simply V. The data buffer length may vary from three to sixty-four bytes.110 frame offers three channels for the transfer of the control signals.110c (b.4 and 28. V.110S configurations use bit oriented data buffering with a 2 bit jitter/wander margin. the locally generated 106 signal is delayed until 105 is sampled by the framer. In the management menus this mode is called V. This generates the minimum 106 delay which guarantees that 109 is turned on before the first data bit is received at the far end. Bit Rates n x 64 kbit/s At n x 64 kbit/s (rates 64…2048 kbit/s) the unframed user data is transferred in 1…32 time slots. 16.30.6 kbit/s. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 40 22030_12 © 2013 Tellabs. User rates n x 3.30. SB. Certain other n x 64+8 kbit/s rates are also supported. 7.110.4 kbit/s). Rates 0. n x 1. No data framing is needed for the data transfer. two or four bits of a time slot. When 105 is turned on. The byte oriented data buffering is used in X. At 56 kbit/s both ITU-T V. 14.21 applications or when octet timing is desired. Bit Rates n x 8 kbit/s At rates 8. The channel SA carries the signals 108/107 and the channel SB the signals 105/109. At rates 72 and 80 kbit/s the data is transferred using one full time slot and one or two bits of another one. This mode uses n full time slots and one extra bit.2 kbit/s (up to 38. The nominal buffer length selection allows for 18 µs. required for X. n x 3. When 105 is turned off. for example. The SA. it will automatically return to on state when more than 31 errors have been detected in the pseudo random pattern during a certain time period. X30M frames. 109 is turned off and the user data (104) is blocked to off state.6.110 based frames (X. V. The delay is expressed in time units at the management interface.6 kbit/s. Whenever required. depending on the user bit rate. the frames are called V. The end-to-end performance monitoring is based on the end-to-end CRC monitoring. the receiving end misses the turn on sequence. and n x 3. Control Signals The unframed interfaces support control signals for the following user channels: • 105/109 transfer at all bit rates (X.21 applications. when activated. If.13 Simulated Carrier The V. n x 3.110 only. At rates < 1.110.110 or X. due to transmission errors. and the channel is ready for the transfer of the user data. After that 106 turns on.0. Performance data is expressed in terms of G. X.2. At n x 64 kbit/s and n x 64+8 kbit/s the CRC check sum is transferred end-to-end in a proprietary Martis frame.821 parameters. the minimum 106 delay required to guarantee proper operation is used. because the corresponding ITU-T frames do not support CRC monitoring.21bis) • 108/107 transfer at V. the CRC check sum is transferred on the last five bits of frame alignment signal of the V. The CRC-4 procedure used is similar to the one for the G.2. using 8 kbit/s extra XB capacity.13 simulated carrier or an 8 kbit/s channel are used at n x 8 and n x 64 kbit/s rates. an additional delay may be selected in the range of 8…8000 bits. The 8 kbit/s channel requires additional transmission capacity but it offers a continuous channel which is. X.110. The V. When 105 turns on.30M. 48 and n x 64 kbit/s The control channels can be transferred in several ways. 22030_12 © 2013 Tellabs. V. A modified V.21bis) • C/I at X. Channel associated end-to-end CRC monitoring is the only way to get accurate performance characteristics for a channel.2.13 simulated carrier is an inband transfer method which does not require extra capacity. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 41 .30. When 48 bits of that pattern have been received.704 2-Mbit/s frames.21bis) • 106 locally generated • 106 transfer from the far-end (V. the user data is substituted by a pseudo random pattern. n x 1.3 Operation CRC Monitoring The channel board can support end-to-end CRC monitoring of the user data.110M. SB and X bits are normally used (selection V. X. the pattern generator input is changed from 1 to 0 for 8 bits.30 frame.110M or X. When transferring the CRC check sum.21 interfaces and bit rates 0.30) with V. 106 Delay Normally.2.110 frame is used at rates 48 and 56 kbit/s. n x 1. and n x 3. n x 3. 7. Timing Sources Depending on the configuration. The phase adjustments take place in small steps in order to minimize the phase jitter amplitude and frequency spectrum width. Plesiochronous transfer is supported in the standard ITU-T V. At the receiving end the synthesiser adjusts its phase according to the value received from the far-end. The V.6.2. 16 and 32 kbit/s. Each detected erroneous pattern start-stop is considered as an input signal code error. At n x 64 kbit/s rates the data buffer operates in a so-called frame synchronous mode where the data transferred during one X-bus frame form a block. The data timing signals are derived from the 16896 kHz system clock by built-in programmable frequency synthesisers.2. The clock for the outgoing data (Rx direction) can come from the channel board or it can be taken from the Tx clock received from the user. The converter recognizes the start-stop pattern which may have start-stop bits and 6. An extra 8 kbit/s channel with the Martis frame is required at rates n x 8 kbit/s and n x 64 kbit/s. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 42 22030_12 © 2013 Tellabs. There is a synthesiser for each channel and each transmission direction. Bit Rate Generation A variety of bit rates is required for the unframed interfaces. 8 or 9 data bits.110 method of transferring the data phase and stuffing is used at all bit rates. The synthesisers operate in a digital PLL mode with slight jitter filtering of the input clock before phase comparison with the system reference clock. the channel board can monitor the 105 state and generate an alarm if 105 goes off.110 (V. 48 and 56 kbit/s. If desired.0. With rates above 512 kbit/s plesiochronous clocking requires a 24 kbit/s channel. Async/Sync Conversion The asynchronous/synchronous converter samples the incoming signal at 16 times the user rate. the plesiochronous operation (the same nominal bit rate) is required.110 frame at rates n x 1.3 Operation 105 Supervision In some applications 105 should continuously stay in on condition. A Martis modification of V. Plesiochronous Clocking When the user data clock cannot be synchronized to the master clock of Tellabs 8120 mini node M. . With plesiochronous clocking the V. The stuffing bits are deleted and inserted at the border between two blocks.110M) also supports plesiochronous clocking at n x 3. The equipment supports the transfer of plesiochronous clocking at all bit rates except for at 8.110 data buffer operates in bit mode. the timing signal for the incoming data (Tx direction) can come from the user equipment or from the clock source of the channel board. The 8 kbit/s channel supports both CRC monitoring and plesiochronous timing at bit rates of up to 512 kbit/s. 128 kbit/s and 256 kbit/s. The receiving side adds the deleted stop bits and compensates for the overspeed by shortening the stop bits of the eight consecutive characters.11 V.28 V.11 V.28 V. on the type of the interfaced equipment and on the operation mode.11 V. In extended operation mode.35 V.11 V.28 V.11 V.36 V.28 V.28 V.28 V. By the aid of drivers and transformers the control signals are converted to G.28 V.24/V.35 V.35 V.11 V.2 Data Interfaces The interface signals of V.28 V.28 V.28 X.703 outputs come as positive and negative CMOS level pulses from the base unit.21 V.11 V.703 input signals are converted to CMOS signals using comparators.11 V. The G. The async converter can be used at bit rates 600 bit/s…64 kbit/s. The method allows for 1. 3. 3.11 V. Data and control signals can change their states at the edge of a clock period. the stop bits are deleted at certain intervals.28 V.11 V.28 V.28.6.11 V.28 V.28 V. The interface modules convert the CMOS level signals to appropriate interface signals.36 and X.28 V.5% overspeed.11 V.11 V.28 103 104 105 106 107 108 109 113 114 115 140 141 142 V.28 V.3 Timing Modes The clocking mode of data interfaces depends on the type of interface. the stop bits can be deleted from every fourth character enabling 2.28 V.11 V.28 V.11 V.25% overspeed.28 V.35. At bit rates below 600 bit/s the async converter is by-passed and the user data is sampled at the rate of 4800 bit/s.11 V.11 V.35 V. At underspeed additional stop characters are inserted.28 V. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 43 . The user clock may be considered to be locked to the network timing source if 22030_12 © 2013 Tellabs. Interface Module Signal Levels Signal Name Interface Type V.28 V.3 Operation In case of overspeed.21 interfaces are NRZ coded.703 signals. V.11 V.11 V.6.35 V. V.28 V. The clock signal has a falling edge at the beginning of a period and a rising one in the middle of the period.28 V.24/V.35 V.11 HSSI TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 The data and clock signals for G.28 V. At longer DTE-DCE distances and in applications where the DTE terminates a data circuit with clock looping at the far-end. the clock 113 is used in the direction DTE-DCE instead of 114.811 and G. or it is clocked by a timing source locked to the same source as Tellabs 8120 mini node M.3 Operation 1. The data interface is clocked from the network. • Data in the direction DTE to DCE (103) is clocked by the timing signal 114 from the DCE (IF module). • Data in the direction DCE to DTE (104) is clocked by the timing signal 115. 16 Contradirectional Synchronous and Codirectional Mesochronous Timing of an Unframed Data Interface in DTE Mode Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 44 22030_12 © 2013 Tellabs. 15 Contradirectional Synchronous and Codirectional Mesochronous Timing of an Unframed Data Interface in DCE Mode Fig.36) is connected to a DTE as if it were a data modem (DCE). V. 2. The clocking method can be used when the transfer delay between the DCE and DTE is below 0. • Data in the direction DTE to DCE (103) is clocked by the timing signal 113. bit rate in Mbit/s.g. V.24/V. 3. The timing mode is called synchronous 114/115. a national timing distribution network both the user system and the network are locked to the timing source according to the CCITT Recommendations G. e.35.28. the user equipment uses the clock supplied by the network interface the user system and the network use the same timing source. The signals in the direction DTE-DCE may contain jitter and wander when compared to the DCE-DTE timing. Fig. .823 V Series Interfaces In most cases the unframed V series interface (V. The timing mode is called 113/115 mesochronous.15 bit (L < 30/(bit rate) m). • Data in the direction DCE to DTE (104) is clocked by the timing signal 115. 17 Codirectional Plesiochronous Timing of an Unframed Data Interface A data source (DTE or DCE) which cannot be synchronized to the Tellabs 8100 network is accessed using plesiochronous timing.3 Operation When interfacing a DCE. in codirectional mode.24 DTE interface is available. the interface module may operate either as a DCE (signals cross-connected in the interface cable) or as a DTE (without signal cross-connection in the interface cable). The timing signals may. X. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 45 . The timing signals are switched off in the asynchronous mode. Currently. from both the DTE and DCE (115/113).21 Interface Fig. Fig. come from the DCE to the interface module (cases 115/114 EXT or 115 EXT). In plesiochronous mode only codirectional timing is supported. or. in contradirectional mode.21 Unframed Data Interface 22030_12 © 2013 Tellabs. Asynchronous V Series Interface The asynchronous operation is supported at bit rates of up to 256 kbit/s. 18 Timing of an X. only the V. Rate Adaptation and Mapping at Bit Rates ≤48 kbit/s User Rate kbit/s < 0. SB. SB.2 38. X SA.6. The signals and control signals in the channel board are rate-adapted and mapped as follows.6 19.and contradirectional operation.4 0. The clock comes from the interface module or towards it.30 V. X S SA.703 interface at 64 kbit/s supports co. SB. SB. X S SA.4 3 6 12 24 3. 2.110 V.703 Unframed Data Interface The G. .2. 1. X S SA.30 V.110 V.6. 3. X SA.110 V. SB.8 4. X Plesiochronous Clocking No No No Yes No Yes No Yes No Yes No Yes Yes Yes Yes Yes Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 46 22030_12 © 2013 Tellabs.2 19.110 XB Mapping kbit/s 1x8 1x8 1x8 1x8 1x8 2x8 2x8 4x8 4x8 8x8 8x8 1x8 2x8 4x8 8x8 1x8 Control Signals SA. SB. octet timing may also be used.6 0.110 X.4 38. X S SA.110 X.30 V.110 X. SB.703 Interface Fig. When required.110 X.30 V.110 V. SB.2 Rate Adaptation Method V.4 Rate Adaptation and Mapping The frame structures used are described in Appendix 1. X SA. SB. SB.8 9.30 V. Octet timing is also supported. X SA.110 V. 1. SB. G. 2.21 mode. X SA. X S SA.4 4.6 9.3 Operation Only one clock signal is used in X. The clock is always locked to the same source as the clock of Tellabs 8120 mini node M.2. 19 Timing of a 64 kbit/s G.6.110 X. 8 25.4 28.110 V.3 Operation User Rate kbit/s 6. SB. SB.110M/7c is a slightly modified V.110 Frame Table 7b. or X.110 (56 kbit/s) like Martis specific frame. MartisDXX is a V.110M. The CCITT/ITU-T Rec. X SA. SA.110/7c V.110 XB Mapping kbit/s 2x8 4x8 8x8 1x8 2x8 4x8 8x8 Control Signals SA.110 V.110 V. X SA.110/7b V.110/7b refers to CCITT Rec. X Plesiochronous Clocking Yes Yes Yes Yes Yes Yes Yes End-to-end CRC monitoring can be supported at all bit rates mentioned above. 8.110M V.8 Rate Adaptation Method V. SB and X refer to SA.110 V. SB.2 14. X SA. 22030_12 © 2013 Tellabs. SB. SB.6 3. SB. SB. X SB SB SB SB SB SB SB SB CRC Support No Yes No No Yes No Yes No Yes No Yes No Yes No Yes No Yes Yes Yes Plesiochronous Clocking No Yes No No Yes No Yes No Yes No Yes No Yes No Yes No Yes N ≤ 8 No N > 8 Yes N > 8 24V. X SA. X SA. SB. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 47 . V.110 V.6 7. V. X bits in the frame.110 V. 16 denotes extra capacity carrying CRC with plesiochronous timing control. X SA. and V. X SA.110M MartisDXX MartisDXX MartisDXX MartisDXX MartisDXX MartisDXX MartisDXX MartisDXX XB Mapping kbit/s 1 x 64 1 x 64 1 x 64 1 x 64 1 x 64 1 x 64 1 x 64+ 8 + 8 1 x 64+1 x 8 1 x 64+1 x 8+ 8 + 8 1 x 64+2 x 8 1 x 64+2 x 8+ 8 + 8 2 x 64+3 x 8 2 x 64+3 x 8+ 8 2 x 64+4 x 8 2 x 64+4 x 8+ 8 + 8 N x 64 N x 64+ 8 + 8 N x 64+ 8 + 8 N x 64+ 24 Control Signals SA.110 and X. SB. X SA. SB.110 frame. SB.4 12.30 do not support CRC monitoring.30M when CRC is activated. The frame type is renamed V. Rate Adaptation and Mapping at Bit Rates ≥48 kbit/ User Rate kbit/s 48 48 56 56 56 64 64 72 72 80 80 144 144 160 160 N x 64 N x 64 N x 64 N x 64 Adaptation Method24 V. X SA. SB.110 V. for example. The first time slot of a port definition of an unframed interface is always TS0. 3. the control bits are the lowest bits of the next time slot.5 Cross-Connection of Unframed Interfaces The cross-connection ports are defined by using interface definition. Many interface types can produce n x 8 kbit/s capacity even when the data speed in the user interface is n x 64 kbit/s. The entire capacity of the unframed interface must be connected in order to ensure the proper function of the interface. If the data uses the whole n x 64 kbit/s capacity (whole time slots). The bit mask means a combination of 8 bits where state 1 indicates an 8 kbit/s channel of a time slot which is connected.6. a bit mask must be used for the connection of the n x 8 kbit/s portion. state 0 means capacity left free. Then the control channel must be connected as well. The control bits can be connected to any usable time slot and bit in the framed interface. the control bits are the last bits of the port. and a possible bit mask (n x 8 kbit/s connections).2 kbit/s) need n x 8 kbit/s cross-connection. TS definition. When the XB capacity of the unframed interface is exactly n x 64 kbit/s. The mask can also be presented in hexadecimal format.13 for transfer of the 105/109 signal. need 64 kbit/s XB capacity. . V.110 rate adaptation. an unframed n x 64 kbit/s connection with end-to-end CRC checking needs 8 kbit/s additional capacity in the XB channel. 48…56 kbit/s data interfaces after V.13 is mostly used at rates n x 64 kbit/s. the n x 8 kbit/s cross-connection is not needed. All low rate data interfaces (≤19. For example. When the unframed interface is connected to the framed interface and a part of the full capacity consists of n x 8 kbit/s portions.3 Operation User Rate kbit/s 1544 1544 1544 Adaptation Method24 MartisDXX MartisDXX XB Mapping kbit/s N x 64+8 N x 64+8+ 8 + 8 N x 64+8+ 24 Control Signals SB SB CRC Support No Yes Yes Plesiochronous Clocking No No Yes At all data rates the channels can support simulated carrier in accordance with V. In some cases an unframed interface can be defined only by using the interface definition (in Tellabs 8000 manager only). The unframed interface can be provided with a control channel in some cases. When making connection to the unframed interface which has such control bits as CRC checking. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 48 22030_12 © 2013 Tellabs. The control bits are automatically connected when the Connect whole port command in Tellabs 8000 manager is used. and the cross-connection is created between these time slots. the correct starting of the main oscillator and the condition of the cross-connect RAM memory is checked. In the TS bits command the time slot and the bit mask for both the interfaces are defined. In the TS pair command one time slot from both interfaces is defined. The last four bits of the unframed interface (two payload bits and two control bits) in TS2 are connected to the TS4 of the framed interface with the TS bits command. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 49 . The type of the user-activated tests depends on the user interface. it is possible to activate the test resources for the specified circuits in the desired place in the network. The first time slot of the unframed interface is TS0. The unframed port is specified as capacity 2 x 64 kbit/s and 4 x 8 kbit/s. 3. and to interface tests. and the cross-connection is made between these areas. In the following chapters the tests are grouped to equipment tests. some of them are running as background processes. This can be made with the TS pair or TS area commands. For instance. In the TS area command the first and the last time slot of an area with equal amount of time slots in both interfaces are defined. 22030_12 © 2013 Tellabs. some tests can be activated through the front panel user interface. 3.7 Test Resources Tellabs 8120 mini node M has many functions to indicate a defect in the operation of the equipment or in the data transmission. and some of them are activated by the user. 20 Example of Cross-Connection The figure above shows an unframed interface IF3 with a bit rate of 144 kbit/s and control channel with 2 x 8 kbit/s (in all 160 kbit/s) connected to a framed interface IF1 which has the G. In Tellabs 8120 mini node M. Some tests are performed when the power is switched on. TS0 and TS1 of interface IF3 are connected to TS2 and TS3 of IF1. some start-up tests are executed. however. which means two time slots and four bits. like the control of the voltages of the power supply. The equipment is not allowed to start other processes if these things are not in order.704 frame structure. by which the quality of data transmission can be controlled and the failure localisation in fault conditions can be performed.1 Equipment Test When the equipment is restarted after a reset. Usually.7.3 Operation Fig. If the equipment is connected to Tellabs 8000 manager. tests can only be activated through the service computer or the Tellabs 8000 manager network management system. and the cross-connection is made between the unmasked bits. The measurement process runs continuously and the results can be read using the service computer. . the signal statistic values according to the ITU-T G. Values that are too low will cause an alarm.35 interface does not use coding in the transmission. In some cases all the values are not available. the V.821 Statistics To control the quality of the data transmission of the framed interfaces. if available. for example. The results can be read with the service computer. and for this reason the code errors are not counted. many tests are executed as background processes. or to search the fault of the transmission line: • code errors • number of G. The equipment has capability to measure the voltages generated by the main power unit. A failure of the test causes the IA Missing alarm for the failed interface.7. This test checks the cross-connect data busses and some parts of the ASIC circuits. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 50 22030_12 © 2013 Tellabs. 3. A detected fault situation causes an alarm. The reason for the alarm can be traced using the user interface. RAM and flash memories. The cross-connect bus test is also running as a background process for locked interfaces.704 frame losses • number of frame synchronization word errors • number of CRC block errors • buffer slips The count time of the counters is from the last reset of the counters or from the last reset of the equipment.2 Test of Framed Interfaces G. The tests run continuously. Near-end and far-end statistics: • total time (seconds) • unavailable time (seconds) • errored seconds • severely errored seconds (10 -3) • degraded minutes (10 -6) Error Counters The number of the following events can be read and cleared by the user interface in both framed interfaces separately in order to check the reason for poor quality.821 Specification are supported in both framed interfaces separately. or a service computer. and the data buffer test checks the Tx-ram and the Rx-ram memories of the framed interfaces. The uP memory test checks the EPROM. The uP memory test and the data buffer test are checking the condition of certain components of the equipment.3 Operation When the equipment is running. are also tested in the loop. The loop will. There should be no other faults in the unit fault list when the loop is created. 21 Loops of a Framed Interface Interface Loop The following signals are activated during the interface loop. The type of the module determines the point where the loop is created in the module. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 51 . Equipment Loop The following signals are activated during the equipment loop. When the framed interface is looped. all data circuits going through the interface are looped. • AIS is transmitted to the line. due to technical reasons. and a part of the module logic. always test the control bus of the interface module. • Looped data is connected back to the demultiplexer. In most cases. • Tx data of the interface module is looped back to the receiver of the interface. as well as the frame multiplexer and demultiplexer. however. 22030_12 © 2013 Tellabs. • Tx clock is looped to the Rx clock. The line coder and decoder. The equipment includes a loop time-out control which will turn off a loop when the time defined by the user has come to an end. Fig. the connectors. the loop is not made by using a signal with line level.3 Operation Test Loop Functions The loops and measurement points are used to find a faulty section of the line and to detect the faulty transmit or receive direction. All other bits are looped back to the interface. as well as the corresponding clocks. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 52 22030_12 © 2013 Tellabs. the HDLC controller works with the line loop. • The received clock signal is used as the transmitter clock. • Looped data is connected back to the frame demultiplexer. • Rx data. it is suggested that the user perform a test with the interface loop to ensure that the module is in order. • AIS is transmitted to the line. . Neither the line coder. If no problems are detected with the equipment loop. is looped back to the interface output. The choices are • Rx data after the interface module but before the frame demultiplexer • Rx clock • Tx data after the frame multiplexer but before the interface module • Tx clock The signal to be measured is selected with the service computer in the General Unit Parameters window. The selection can also be made with the front panel user interface in Tellabs 8120 mini node M. Remote Line Loop The remote line loop operates in the looped unit in the same way as the local line loop. and the yellow LED of the looped interface is also lit. It is also possible to detect faults in the transmitting and receiving buffers. The measuring point is isolated with a transformer. When the loop is made. the yellow LED of the unit controlling the loop is switched on. This loop tests the frame multiplexer and demultiplexer. The status of the looped unit can be checked with the user interface. and the control channel will continue to operate even when the remote line loop is active. as well as the frame demultiplexer and the multiplexer. Measuring Point A 75 Ω G. can be tested from the line connector of the module with the line loop test. • AIS signal is connected to the X-bus instead of the received signal. Through the measuring point it is possible to measure the input and output signals of both framed interfaces IF1 and IF2. This selection is stored in the non-volatile memory of the unit so that the selection is also retained after a possible power interruption. received by the interface module. When it is used. the decoder nor the interface module are included in the loop. The loop is made via the HDLC channel. and the decoder. The equipment loop is made in the unit.704 multiplexer (before the interface module) is looped back to the demultiplexer. Line Loop The following signals are activated during the line loop.3 Operation • Tx data from the G. The remote line loop is activated from the unit at the other end of the line. The interface module. The whole line can be tested with the remote line loop. the line coder. but the connector body is connected to the unit ground.703 type coaxial cable measuring point is provided on the back panel of the unit. Error Counters The channel board can count the following event numbers by using the software and the hardware counters.110 frame losses (the frame from the net) (the frame of XB channel) • number of multiframe losses (the frame from the net) • number of frame word errors (the frame from the net) • number of CRC block errors • code errors in the user interface (G.3 Tests of Unframed Interfaces G. adjustable to seconds.54 loops supported by the equipment can be limited or even disabled with the user interface. The counter deactivates the loop when the set time has expired.3 Operation The data signal of the measurement point is HDB3 coded and independent of the type of the interface module and the coding of the data interface signal.821 Statistics Every unframed interface has its own group of counters when the V.54 loops also have special configurable values. start-stop format) • buffer slips and adjustments Test Loop Functions To find the places where problems might occur in the unframed interfaces.110. The signal levels and formats are in accordance with G. which will turn off a loop when the defined time has come to an end. The V. X. The values can be read and cleared with the user interface separately. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 53 .821. The loops and the measurement point can be used to detect a faulty Tx and Rx direction and to pinpoint a faulty line. there are test loop functions which can be activated separately for each interface with the service computer or with the front panel user interface.7. A loop activated to an unframed interface only affects the data circuit which goes through the involved circuit. The available circuit performance values are • total time (seconds) • unavailable time (seconds) • errored seconds • severely errored seconds • degraded minutes With these values the quality of the data transmission can be controlled in accordance with the CCITT G. These event numbers can be read and cleared by user interface. All loops have a separate time-out counter which is adjustable by the user.30 or the Martis framing is activated with the CRC transfer.703.703. The V. 22030_12 © 2013 Tellabs. 3. each interface separately: • number of V. or by connecting the data measuring equipment to the remote end of the circuit. are included in the loop. By activating the line loop it is possible to test the whole interface from the line connector of the module. is looped back to the interface output. as well as the CRC circuit. received by the interface module.3 Operation Fig. 22 Loops of Unframed Interface Interface Loop The following signals are activated during the interface loop: • The Tx data of the interface module is looped back to the receiver of the interface. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 54 22030_12 © 2013 Tellabs. . • The looped signal is connected back to the cross-connection. • The Tx clock is looped to the Rx clock. If some of the framing formats are used. A line loop can be activated close to the X-bus interface towards the user interface. The operator can activate an interface loop which is close to the physical user interface back towards the network. instead of the received signal. When this loop is activated. • AIS signal is connected to the X-bus. the frame multiplexer and demultiplexer. it is possible to test the correct function and cross-connection of the unframed interface by connecting measuring equipment to the framed interface to where the looped interface is cross-connected. Line Loop The following signals are activated during the line loop: • Rx data. The test pattern is according to the ITU-T Recommendation O. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 55 . loop 2 activated at the far-end sets the received data to off or to pattern 1010…. the loop tests can be started. Test Pattern Generator The channel module has built-in per channel test pattern generators and pattern error detectors. or only allow the operator to control the loops. 22030_12 © 2013 Tellabs. the test loop indication signal 142 goes on.3 Operation Local Loop and Remote Loop The unframed interfaces are equipped with the V. When some of the V. In case of X. The remote loop makes it possible to check the whole data circuit through the network.21 interface module. The remote loop is activated when the V. All the loops have an adjustable enable timer. The loops can be controlled with the user interface. For these loops the user interface has configurable parameters to disable. RLB) are supported by the X.54 loop circuit receiver recognizes the activation pattern coming from the far-end through the X-bus.54 loops are on. enable. The user interface facilitates the activation of the test resources and presentation of the test results. RL. LL) and the remote loop (loop 2.21. a test is performed with the remote loop activated at the far-end. The X.54 test loop functions supporting the local loop (loop 3. Activating the local loop makes it possible to check the operation of the interface and the user line from the user device. Typically. the loops should be enabled in the equipment which are as close as possible to the user interfaces. enable with timer. In general. The sending of the pattern from the far-end is activated by the user interface or by the input signal 141. The local loop can be activated with the user interface or by activating the input signal 141.151. or the loops can also be controlled with the user device through the signals 140 and 141. and disabled in all intermediate equipment. A loop 2 (RLB) activated from the far-end turns the signal 142 on and sets the received data to off. RL). There is one test pattern generator per interface.21 loop functions (LL. Thereafter. One way to perform this is to use the built-in test pattern generator and pattern error detector of the unframed interface. 24 shows a typical back panel arrangement of Tellabs 8120 mini node M. The back panel is furnished with four different changeable interface modules. 23. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 56 22030_12 © 2013 Tellabs.4 Installation 4 Installation 4.2 Back Panel Connections Fig. 4. IF1…IF6 and SYS. and the synchronization connectors. The numbering of the interfaces is also shown in the figure below. The type of the connector depends on the type of the module.24 interface with a 9-pin D connector.1 Front Panel Indicators and Controls The front panel of Tellabs 8120 mini node M is presented in Fig. The fixed items of the back panel are a power connector. There are two alarm LEDs (red and yellow) for each block.6 kbit/s asynchronous V. For the service computer (SC) there is a 9. The front panel of Tellabs 8120 mini node M is equipped with LEDs to display the alarms of the system and the interface circuits. 23 Front Panel of Tellabs 8120 Mini Node M The four buttons and the LCD display are for local control operations. Fig. Each block reports its own alarms with these LEDs. . a measurement connector. Also the framed interfaces can be of a different type in the same piece of equipment. and there are no restrictions to usage of different types of unframed modules in the same piece of equipment. 25 Example of Back Panel with G703-75-M. Through these connectors the equipment can be synchronized to an external clock source. The synchronization connectors provide a 75 Ω input and output for the clock signal of the master clock oscillator of the equipment. 25. Each module can be of a different type. Fig. The impedance of the interface is 75 Ω. OTE-LED-M. V36-M and V35-M Modules 22030_12 © 2013 Tellabs. The control of the clock signal is handled with the Master Clock menu of the user interface. In one unframed module there are two channels with the same type of an interface.4 Installation Fig. 24 Tellabs 8120 Mini Node M with BTE-384M. The interface signals and the Rx and Tx clocks of the framed interfaces can be measured with measurement equipment through the measurement connector. or the equipment can give a clock to another data transmission equipment connected to the same transmission network. On the framed interface modules there is one interface in each module. On the lower part of the back panel there are two places for framed interface modules. G703-75-M. The back panel arrangement for Tellabs 8120 mini node M with a different module configuration is shown in Fig. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 57 . V35-M and V36-M Modules There are two places for unframed interface modules on the upper part of the panel. Tellabs 8120 mini node M must be disconnected from the mains supply before removing the cover as high voltages are present inside the case. 4. negative pole earthed 40…60 V DC. 25The power supply module PDU422 has been discontinued. The fuse is of a standard 5 x 20 mm size and it must be replaced with the ratings indicated below.4 Installation If an unframed interface module (user access interface module) is removed permanently by the user. Only qualified personnel is allowed to change the fuse.3 Mains Connection Tellabs 8120 mini node M is connected to a 100…240 V AC mains supply with a three-pin grounded plug. The fuse of the AC model is located inside the metallic case. Tellabs 8120 mini node M is equipped with one primary fuse. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 58 22030_12 © 2013 Tellabs. Other power supply problems can be checked with the user interface which has a voltage measurement facility. If the green power indicator is switched off. do not put it in a warm place. part code 880070158A. The AC model mains supply primary fuse can be changed after the metallic top cover and power supply shield have been removed. The primary fuse of the DC models is accessible on the back panel of the device.4 Operating Environment When installing Tellabs 8120 mini node M. The consumption varies depending on the installed module configuration and the bit rates in use. it must be replaced with a blank lower interface. Power Unit 8990NFS40 PDU422 24 V DC25 Fuse T1A T4A T4A Input Voltage 100…240 V AC ±10% 47…63 Hz 19…36 V DC. The maximum power consumption is approximately 40 V A. to close the back panel opening. to close the back panel opening. Other power supply alternatives are a 48 V DC or a 24 V DC power supply. positive pole earthed PDU423 48 V DC Power consumption: 40 V A max. 4. If a framed interface module is removed permanently by the user. it indicates a failure of the fuse. part code 880070157A. it must be replaced with a blank upper interface. . Operating temperature: +5…+35 °C Operating humidity: < 85% RH. Enough free space should be left around Tellabs 8120 mini node M to guarantee proper functioning and ventilation. 4.1 DC Power Supply Cabling Tellabs 8120 mini node M with DC power supply is connected to the main battery system with a two-wire cable which has the following color codes: 24 V DC Power Supply +24 V 0V Wire Color Red Black 48 V DC Power Supply -48 V 0V Wire Color Blue Black 22030_12 © 2013 Tellabs. even danger for the user.4. in some cases. 26 Route of Ventilation Air Do not cover the ventilation holes on the case of Tellabs 8120 mini node. Fig. non-condensing The figure below shows how the ventilation air goes through the device. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 59 . A very dusty or humid installing place can also cause incorrect working of Tellabs 8120 mini node M and.4 Installation Never put Tellabs 8120 mini node M on top of another piece of equipment of the same kind because it can cause overheating and malfunctioning of the equipment. Local Service Computer Connector The SC.5 Configuration of Tellabs 8120 Mini Node M Step 1 Check that Tellabs 8120 mini node M is ready for operation: • Interface modules are properly installed and fastened. See the exact location of the wire in Fig.28 V.28 V.28 V. • No loose parts are inside the case. • Check that nothing covers the ventilation holes of Tellabs 8120 mini node M. local service computer connector is provided with a 9-pin female D-connector according to ISO 2110 Standard.4.28 V.3 SYNC Connector The SYNC connectors are SMB type connectors. 40.4. electrically of G. • Note that there are ventilation holes also on the sides of the metallic case.4 Installation 4. . • The cover is installed. • Screw the grounding earth wire with washers tightly to the M5 nut at the back of the node. The connector is furnished with two UNC 4-40 locking screws. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 60 22030_12 © 2013 Tellabs.28 V. Pin # 1 2 3 4 5 6 7 8 9 ITU-T Circuit # 109 104 103 108 102 107 105 106 Signal Level V.2 SC.28 Function Received line signal indicator Received data Transmitted data Data terminal ready Signal ground Data set ready Request to send Clear to send Not connected 4. 4. Step 2 Put Tellabs 8120 mini node M to correct operation environment as described in 4. • The metallic case is in its place and fastened with all screws. Connect the power cord to the main power supply and the protective earth wire to the grounding terminal. Step 3 Step 4 Connect interface connectors to the back panel of Tellabs 8120 mini node M.703/75 Ω impedance.4 Operating Environment.28 V. the yellow LED will be switched off and Tellabs 8120 mini node M is ready for operation. 22030_12 © 2013 Tellabs. which is from 30 to 60 seconds and depends on the configuration of the equipment. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 61 . There are two HDLC control channels (one in both framed interfaces IF1 and IF2). which is in the SCU unit of the other nodes.6 kbit/s asynchronous V. All other fault situations. Test state (loops etc. When the power cord is connected. These are normally used when Tellabs 8120 mini node M is connected to Tellabs 8000 manager. 27 Grounding Earth Wire Assembly Step 5 Step 6 Tellabs 8120 mini node M is now ready for use. The configuration of Tellabs 8120 mini node M can be monitored and altered through Tellabs 8000 manager or by a local service computer connected to the front panel connector.) • Set the node ID.24 interface. Fig. Green Yellow Red Lit when Tellabs 8120 mini node M is connected to the mains supply and the power is switched on. The meaning of the color of LEDs is explained below.). The Tellabs 8120 mini node M blocks have the same Tellabs 8000 manager functions as in the corresponding units in the Tellabs 8100 node. After a start-up time.4 Installation When DC power supply is used. • Check that no unusual alarms are on. does not. exist in Tellabs 8120 mini node M.7 Recommended Settings of Framed Interfaces for recommended settings. The configuration can also be done locally through the front panel keys and the LCD display. the green and yellow LEDs are lit. a 9. Lit when Tellabs 8120 mini node M is receiving alarm indication from the network (far-end alarm. AIS). The control functions operate as in a Tellabs 8100 cross-connect node. Configure Tellabs 8120 mini node M with planned parameters. however. The common test resource. • Check that the parameters for the framed interfaces and master clock are correct. (See 4. Tellabs 8120 mini node M must be permanently connected to earth using the supplied grounding earth wire. It can be monitored on the LCD display during operation without interfering with data transmission. There are two HDLC control channels (one in both framed interfaces IF1 and IF2). however. . The parameter settings are stored in a non-volatile memory. serial number) • read/set master clock parameters • creating and deleting cross-connections (not possible with SC) • alarm information from each interface and block • read the active faults or the fault history • clear the fault history • set interface tests and loops • read the error counters and G. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 62 22030_12 © 2013 Tellabs.4 Installation 4.1 NMS Control Tellabs 8120 mini node M is designed to be controlled by Tellabs 8000 manager.5. does not. There is a 9. With the local keyboard and the LCD display the user can perform the following operations: • read the node parameters • node ID • unit ID (hardware and software versions. The Configuration menu recognizes the interface units and transmission modules and displays the correct menu items accordingly. which is in the SCU unit of the other nodes.6 kbit/s asynchronous V. Through this interface Tellabs 8120 mini node M can be controlled also with the service computer of the Tellabs 8100 system. exist in Tellabs 8120 mini node M. These control channels are used when Tellabs 8120 mini node M is connected to Tellabs 8000 manager.821 error statistics from each interface • read the status of V interface control signals • read/set interface parameters In the following description the abbreviation NTUM refers to Tellabs 8120 mini node M. The Tellabs 8120 mini node M blocks have the same NMS functions as the corresponding units in the Tellabs 8100 node.24 interface on the front panel.5.2 Local Control Tellabs 8120 mini node M has a local keyboard (four buttons) and an LCD display for local control operations. With these tools the local user can make the same operations that are possible with the service computer connected to the SC interface on the front panel. 4. The control functions operate as in a Tellabs 8100 cross-connect node. The common test resource. The NTUM parameter settings can be monitored during operation through the display without interfering the normal data transmission. The other items can be scrolled to the display with the keys.4 Installation The LCD display has two lines with 24 characters each. When the cursor is on the lower line. which is the first field of the branch. 22030_12 © 2013 Tellabs. The upper line is used to show the heading of an item. there may be many other items at the same level of the menu. the use of the ENTER key confirms that the present value of the field is used as a new value of the item and the cursor moves to the heading of the item. which means that there is a sub-menu for the item. Use the SCROLL keys to move the cursor to the Update field of the present menu branch. The text Updating appears on the display. On the lower line the EXIT key moves the cursor from the value field to the heading of the item. By using the EXIT and ENTER keys the user can move up or down in the menu structure. sub-menu or item) is unknown to the user. the EXIT key causes a move upwards to the next menu level. If the phase of the present menu level (menu. the new value of the menu branch must be confirmed by the Update field. Press the ENTER key to confirm the new value. In most cases three item fields are shown at a time. Although there are three items on the display. Press the ENTER key to move the cursor to the value field. the SCROLL keys (< or >) are used to move from one item to another at the same menu level. When the cursor is on the upper line. Do not push the keys before the text disappears and the menu text is visible. The ENTER key moves the cursor from the heading to the value field of the item or to the sub-menu if the value is DIR.6 Menus of Tellabs 8120 Mini Node M The following figures present the menu structure of Tellabs 8120 mini node M. the SCROLL keys are used to change the value of the parameter of the item. Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Move the cursor with the SCROLL and ENTER keys to the heading of the item you want to change. When the cursor is on the value field. All the needed changes of a menu branch can be made before using the Update field. When the cursor is on the upper line. The blinking cursor indicates the current item field. on the lower line there is the value of the item or the text DIR. Press the ENTER key to confirm the update. the main level is reached by pressing the EXIT key several times. 4. Use the SCROLL keys to select the new value for the item. If the value of an item is changed. Press the ENTER key to move the cursor to the value field of the Update field. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 63 . The ENTER key is also used to confirm a selection from a menu. The value of an item is changed in the following way. 28 Main Menu of Tellabs 8120 Mini Node M Fig. 29 Menu of Main Parameters Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 64 22030_12 © 2013 Tellabs. .4 Installation Fig. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 65 .4 Installation Fig. 30 Main Interface Parameters Menu of IF1 and IF2 22030_12 © 2013 Tellabs. 4 Installation Fig. 31 Menu for IF1 and IF2 Parameters Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 66 22030_12 © 2013 Tellabs. . 32 Menu for Neighbour Node Message Parameters 22030_12 © 2013 Tellabs.4 Installation Fig. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 67 . 6.4 Installation Fig. . The MartisDXX device is usually a part of the Tellabs 8100 network and it is managed by Tellabs 8000 manager. Device Mode Menu The Device Mode menu specifies the device mode of the NTUM.6. Neither are remote configuration and monitoring allowed when the NTUM is in the MartisDXX device mode. you are not allowed to configure the cross-connections of the MartisDXX device by using the front panel keys and the LCD display. This menu is entered in a specific way explained in 4.7 Entering Security Menu of Tellabs 8120 Mini Node M. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 68 22030_12 © 2013 Tellabs. 33 Cross-Connect Menu 4. Therefore. The NTUM can be either a MartisDXX device or a stand-alone device. The text DXXNTUM indicates that the NTUM is in MartisDXX device mode.1 Security Menu The security menu contains two items (device mode and panel locking) which can be set. 4 Installation The text NTUM indicates that the NTUM is in the stand-alone mode. In this mode all the configuration and monitoring operations are allowed by the use of the front panel keys and the LCD display if the panel is unlocked. To change the device mode, use the SCROLL keys to select the new mode and press ENTER. When ENTER is pressed, the new mode is saved into the non-volatile memory to make sure that the NTUM will go to the correct mode after reset. Panel Menu The item for key panel locking has three settings (panel unlocked, panel locked, panel configuration locked) to prevent the user from accidentally selecting the wrong settings to the configuration items and thus making the NTUM non-functional. To make any changes to the NTUM configuration, the item for the key panel locking has to be unlocked. The items for panel locking and their features are • Panel locked, Locked • NTUM configuration cannot be seen nor altered • Some statistics are available to the user • Panel configuration locked, Cfg. Lock • NTUM configuration can be seen but not altered • Panel unlocked, Unlocked • NTUM configuration can be seen and altered • Menus are available to the user according to the device mode To change the panel mode, use the SCROLL keys to select the new mode and press ENTER. When the ENTER is pressed, the new mode is saved into the non-volatile memory to make sure that the NTUM will go to the correct mode after reset. 22030_12 © 2013 Tellabs. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 69 4 Installation Fig. 34 Device Modes of Tellabs 8120 Mini Node M Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 70 22030_12 © 2013 Tellabs. 4 Installation NTUM Menu The NTUM user interface can be used to configure a local or a remote NTUM. The local NTUM is the target by default. The remote NTUM that is connected to the local NTUM via a trunk interface (IF1 or IF2) can be configured by using the local user interface if the HDLC communication channel is established over the trunk. To set the target NTUM, use the SCROLL keys to select it and press ENTER. Choices for the target NTUM are Local, Remote1 and Remote2. The number after the text Remote specifies the trunk interface that is used. The yellow LED of the corresponding interface blinks on the front panel of the local NTUM when it is in remote mode. The remote configuration is not allowed if the NTUM is part of the Tellabs 8100 network. 4.6.2 Faults Menu Three menu branches are available from the field of Faults by pressing the ENTER key: ActFlts, FltHist and ClrHist. From these fields the user can see the fault(s) which are active at the moment or receive the information of the latest fault state transitions (the fault history report) and clear the history report. ActFlts The ActFlts menu is used to ask active faults from the target NTUM by pressing the ENTER key. The active faults can be seen in the following list format (fault/interface or common level fault). 1 2 3 4 Rx signal mis. Master clock flt Fr fe alarm AIS from X-bus IF 1 Com IF 2 IF 5 If there are several faults, two of them will be displayed and the rest of the faults can be viewed by using the SCROLL keys. Pressing the ENTER key activates a new fault query from the NTUM. FltHist From the FltHist menu the user can see the fault history report by pressing the ENTER key. The fault history is useful when a fault has been on (the red LED flashes) but when asking for active faults the response is No faults. The display format is: 1 2 3 4 5 6 Reset Master clock Rx signal mi Fr f-e alarm Fr f-e alarm Rx signal mi Com Com IF 1 IF 2 IF 2 IF 1 DLT ON ON ON OFF OFF 22030_12 © 2013 Tellabs. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 71 Hw-ver Sw-ver Year Week Serial The hardware version of the unit. Node Identification Menu The NTUM has its own node identification number 0…65535 which can be changed by the user. The year when the unit was manufactured. the cross-connection clock selection (MastClk). the module defining. Each node in the network must have a different Node ID. are not changeable). The readable and changeable parameters are the node and unit level identification data. . The master clock is usually synchronized to one of the incoming data signals (generally a 2 Mbit/s trunk). the 1+1 protection and the measurement point selection. The week when the unit was manufactured. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 72 22030_12 © 2013 Tellabs. The 16-MHz clock is also used to generate the Tx clock of each data interface. The serial number is set at the production phase of the unit.4 Installation If there are several faults on the history report.3 Parameters Menu The general node and unit level parameters can be read and changed in the branch Param. The serial number which is an absolute identification of the unit. The timing consists of • 16 MHz • 8 kHz frame sync • 500 Hz multiframe sync The interfaces use these signals in the bus interface.6.g. The software version of the unit is used to identify the downloaded software version etc. (all parameters. 4. The latest fault transition has the biggest number (in the case above 6 Rx signal mi IF1 OFF is the latest fault transition). Master Clock Menu The NTUM has a 16-MHz master clock which is used for generating the timing of the cross-connect bus. The clock of the desired interface is collected by using a separate synchronization clock bus (SYB). Unit Identification Menu Only the unit level information of the NTUM can be read in this branch. The master clock object tells the required interface to connect its Rx clock to this bus. After clearing the faults the unit starts the fault history collection automatically. two of them will be displayed and the rest of the faults can be viewed by using the SCROLL keys. Pressing the ENTER key activates a new fault query from the NTUM. e. the serial number. ClrHist The fault history can be cleared in the ClrHist menu by pressing the ENTER key. The master clock menu is entered by pressing the ENTER key when the cursor blinks on the MastClk text. To change the frequency. This field displays the source interfaces of the sync clock busses. The text Remove IFn from FB List is shown. This field specifies the frequency of the clock output. Use the SCROLL keys to change the slot number. The list of the available interfaces can be scanned by using the SCROLL keys. SYB2 or Extern. Update Choices This field updates the new master clock parameters to the target NTUM (local or remote). This field indicates the current source of the master clock: Intern. The fallback list can be scanned by using the SCROLL keys. 5. otherwise press EXIT. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 73 . To remove an interface from the fallback list. It can be selected to the clock fallback list. This field indicates the current state of the master clock: OK. use the SCROLL keys to select a new frequency and press ENTER. The elements of the list are in the priority:source format. The form of the clock fallback list is 1. The Master Clock menu contains the following fields (upper line). The text Ext refers to the external clock. press ENTER to add the interface in the fallback list. The NTUM also has a clock output. Press ENTER to start the state monitoring. The master clock of an NTUM can be configured and monitored by using the master clock menu. press ENTER when the cursor blinks on that interface. Press ENTER again to remove the interface. The list can have up to five entries. where n = 1…132 (64 kHz…8448 kHz). To change the frequency. This field specifies the frequency of the external clock. To add an interface in the fallback list. All the available interfaces that can be used as the master clock are displayed here. The text None indicates that the list is empty. Alarm. The frequency of the external clock can be defined as n x 64 kHz. the text None is shown. The State Monitoring sub-menu contains the following fields which are automatically updated every fifth second. 4. Source State SYB1/2 Ext Clk Clk Out 22030_12 © 2013 Tellabs. If there are no available interfaces. The clock output frequency is derived from the master clock and its frequency can be selected (n x 64 kHz). press ENTER when the cursor blinks on that interface. When the slot number of the fallback list is selected. FB List State This is the sub-menu for the state monitoring of the master clock. SYB1. On the back panel of the NTUM there is a connector for the external clock input. 2. IF_ IF_ IF_ IF_ Ext. 3. It is electrically similar to the clock input. The text Add IFn in 1st FBL slot is shown. use the SCROLL keys to select a new frequency and press ENTER. The last entry is followed automatically by the internal state.4 Installation The clock fallback list is used to define the synchronization priority order. The fallback list of the master clock is displayed in this field. clock (Internal) The list can also be made shorter. Usually 2048 kHz is used. . If the output clock controlling is ON and the output clock is enabled (an output clock frequency is specified). Mode CurSele Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 74 22030_12 © 2013 Tellabs. The 1+1 parameters (Mode. To change the acceptance time. FltMsk and Configured Module). use the SCROLL keys to select a new time and press ENTER. the output clock will be disabled if the source of the master clock is either an internal or an external clock. for example.4 Installation OutCtrl This field specifies the control mode of the clock output. This field specifies the acceptance time for the clock sources. The module configuration field defines what kind of a module the unit program currently services. ScrmMo. When the IF1 or IF2 parameters are updated in the protected mode. The acceptance time value is 0-120 s. AcpTime Module Configuration Menu The NTUM device has six interfaces and four independent interface modules. The No prot selection means normal unprotected mode. 6). both interface parameters will be updated (except for the baseband parameters Line. The field is auto-refreshed. but modules 3 and 4 have both two interfaces (3. Thus. ScrmTyp. A clock source is a valid source for the master clock if the status of the clock source has been OK for at least as long as the acceptance time specifies. and ProtIf2 protected mode by settings of interface 2. use the SCROLL keys to select a new mode and press ENTER. 10E-3 Consequences. a module is not installed. 1+1 Protection Menu The interfaces 1 and 2 can be configured into the 1+1 protected mode. HomeSta. If the output clock controlling is OFF. The switch uses fault categories to select the interface to be used. To change the control mode. The modules are numbered so that the modules 1 and 2 have corresponding interfaces (1 and 2). also the module configuration must be changed from the Config branch. Update This field is used to update the 1+1 protection parameters in the NTUM. This field appears only if the installed module contains strappings. there should be the same module in the Install field as in the Config field. 4 and 5. The field shows the information on module strapping (75 Ω/120 Ω/ contradirectional/codirectional). When the user has decided to install a new interface module. ChaDel and Force) can be changed on other fields but after the changes the parameters must be updated by pressing the ENTER key in the Update field. If. the module should be configured as Not def. it shows which Rx signal is connected to the cross-connection. The Rx signal faults are classified into several categories. The field is displayed only in the 1+1 protected mode. There is also a Not def selection which means that the interface has not been defined (module not in use) and no faults which belong to this module will be reported. Level. ProtIf1 means protected mode by settings of interface 1. the state of the output clock does not depend on the source of the master clock. In this field the 1+1 mode can be defined on/off. IF1 Install Type Config This field shows the currently installed module (read-only information). The output clock controlling is either ON or OFF. In the protected mode both interface modules must support the selected bit rate. ChaDely Force Measurement Point Menu The NTUM device has one measurement point. Parameters of Interface 1 and 2 The following menus are available when the selected interface is IF1 or IF2. Buffer. The selection IF1/IF2 means that the IF1 or IF2 interface is defined as the home state. and when both interfaces are classified to the same category. All selections are available when the interface is in unlocked state. Rate. The field handles the protection switch change delay (0 ms…10 min). in the state IF1 or IF2 the protection switch is forced to select IF1 or IF2. The signal can be selected to this point from interfaces 1 or 2 and the signal can be either Rx clock or data or Tx clock or data. MeasPnt The measurement point selections can be scanned by using the SCROLL keys. The state None is normal. FtsData. 4. Press the ENTER key to confirm the selection. Off RxM. The selection No H-S means that the switch chooses the better Rx signal and the selection changes will be made only when the unused Rx signal quality is better than the used Rx signal. both interfaces must support the selected bit rate. The home state can be changed in the field to the switch which selects the Rx signal. If the interface is locked. the minimum bit rate is 128 kbit/s (2 x 64k). FltMsk. The interface parameters (Framing. The reading/change possibility depends on the panel state (see 4. FltAct) can be changed in other fields and sub-menus but after changes the parameters must be updated by pressing the ENTER key in the Update field. whereas the sub-menus of interfaces 3…6 are similar. If the state is locked. The selectable bit rate depends on the configured module (the module must support the selected bit rate). CAS. BitUse. The change delay is a filter parameter of the protection switch so that the fault transition which can affect the switch turning must be active for the duration of the change delay before the switch turns.6. When the framing is on. This field is displayed only in the 1+1 protected mode.4 Interface Parameters Menu The interface parameters (interface 1…6) can be read and changed in this branch. CntrlTyp. changed and updated in this branch.1 Security Menu). no bit rate changes can be made. If the device is in 1+1 protected mode. Interfaces can be divided into two groups according to their sub-menus: interfaces 1…2 have the same type of sub-menus.6. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 75 . This field is used to update the interface parameters. Off. the switch selection returns always back to the home state interface. the changes can be made only between Off RxMon/ Off. Param Update The general interface parameters can be read. The time-out for this control is the same as the time-out for IF1 controls. The field handles the force control of the protection switch. Basband. The possible selections are On. This field is displayed only in the 1+1 protected mode. Framing Rate 22030_12 © 2013 Tellabs.4 Installation HomeSta This field is displayed only in the 1+1 protected mode. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 76 22030_12 © 2013 Tellabs.g. NDPN and NPDNV29. e. ON/OFF.g. with other BTEs None and V29. FSW/RAI. one of the following: CRC use: CRC4 will be generated into this bit HDLC use: HDLC channel in this bit X-Con: the bit comes from the cross-connection CBSC: the bit is controlled by a separate command. in master clock remote alarm use0: the bit will be transmitted at permanent 0 state1: the bit will be transmitted at permanent 1 state CRCE FSW/RAI TS0B4…8 The following fields (TS99B1-7. The field is displayed only when the configured module is BTE384 and the possible scrambler modes are call and answer. The field is displayed if TS0B1 is in the CRC state and the CRCE bit can be configured as:ReEnd: CRCE bit is used to indicate remote end CRC errors0: the bit will be transmitted at the permanent 0 state1: the bit will be transmitted at the permanent 1 state The frame synchronization word and the far-end alarm (TS0B3) usage:Regen: Transmitted sync. CRCE. TS0B1 The field for selecting the use of TS0B1. In the state ON. in master clock remote alarm use 0: the bit will be transmitted at the permanent 0 state 1: the bit will be transmitted at the permanent 1 state. This field is displayed when the configured interface module is V35-G704 or X21-G704. CRCE.HDLC use: the bit is selected for HDLC useX-Con: the bit comes from the cross-connectionCBSC: the bit is controlled by a separate command e. The scrambler has two states. V32.4 Installation Basband *Line *Level *ScrmTyp *ScrmMo *WetCur This field is displayed when the configured interface module is a baseband module. . VdhScrm BitUse The following fields (TS0B1. V29. word and remote-end alarm are regeneratedX-Con: Transmitted sync. Note! When the control type is master or slave. this bit must be in CRC use. The type of the line can be 2-wire or 4-wire when the biphase coding is used (BTE384). the BTE module detects when the NTU is in the POWER OFF state. There are three sub-menus under the Basband menu. The possible output levels depend on the type of the BTE. TS99B8 and TS66B8) are displayed when the bit rate is 8M. TS0B4…TS0B8) are displayed when the bit rate is not 8M. With BTE384 the possible scrambler types are None. This field is displayed when the framing is ON and the sub-menus depend on the selected bit rate (in the 8M mode the sub-menus are different). word and remote-end alarm comes from the cross-connectionX-Sync: Sent frame is synchronized to the frame coming from the cross-connectionRAIXcon: Remote-end alarm comes from the cross-connection Fields for selecting the use of TS0B4…TS0B8 are similar (but independent). The field is displayed only when the configured module is BTE384 and the wetting current has the states ON/OFF. g.CRC use: CRC will be generated in these bitsHDLC use: bits are selected for HDLC useX-Con: bits come from the cross-connectionCBSC: bits are controlled by a separate command e.: When MCLRAI is in use. The master clock remote alarm usage can be controlled in this branch.ReEnd: CRCE bit is used to indicate remote-end CRC errors0: the bit will be transmitted at the permanent 0 state1: the bit will be transmitted at the permanent 1 state The field for selecting the use of TS99B8. *HDLC *TS *Bit1…8 *MCLRAI CAS The following fields (CAS.7.-----: MCLRAI is not in use. the time slot for MCLRAI use can be selected in this field.MCLRAIIn use: MCLRAI will be in use. this time slot must not be cross-connected (MCLRAI usage reserves the whole time slot).Bit1…8: When MCLRAI is in use.Pol. Bit5. When the HDLC channel is in use. in master clock remote alarm use0: the bit will be transmitted at the permanent 0 state1: the bit will be transmitted at the permanent 1 state *CRCE *TS99B8 *TS66B8 The HDLC and MCLRAI fields are both present whatever the bit rate is.-----: the HDLC channel is not in use.4 Installation *TS99B1-7 The field for selecting the use of TS99B1-7. the bit(s) for HDLC use can be selected in these fields. in master clock remote alarm use0: bits will be transmitted at the permanent 0 state1: bits will be transmitted at the permanent 1 state The field is displayed if TS99B1-7 are configured for CRC use. When the HDLC channel is in use. This field is displayed when the framing is ON and sub-menus depend on the selected bit rate (in the 8M mode there are four CAS groups A. *HDLC The HDLC control channel usage is selected in this branch. When the HDLC channel is used in the time slots TS0. the HDLC usage must be defined in the special time slot/bit field(s).g. The following can be selected in this field:In use: the HDLC channel will be in use.TS: When MCLRAI is in use. and in the other bit rate modes for signalling only one time slot is reserved).8) are displayed when the bit rate is not 8M.HDLC use: the bit is selected for HDLC useX-Con: the bit comes from the cross-connectionCBSC: the bit is controlled by a separate command e. 22030_12 © 2013 Tellabs. Special bits must be configured as CBSC for the clock remote-end alarm usage. the user can define the polarity of alarm in this field.HDLC use: the bit is selected for HDLC useX-Con: the bit comes from the cross-connectionCBSC: the bit is controlled by a separate command e. The clock remote-end alarm can be configured into frame special bits or in data bits. in master clock remote alarm use0: the bit will be transmitted at the permanent 0 state1: the bit will be transmitted at permanent 1 state The field for selecting the use of TS66B8. If the clock remote-end alarm is in the data bit. the time slot for HDLC use can be selected in this field. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 77 . TS66 and TS99 or it is desired to be used there.g. C and D. B. the user can define in this field which bit of the time slot is in MCLRAI usage. AIS detection in unframed mode ON/OFF: *Bit1…8 FltMsk FltAct *AisInh *RaiInh *RaiCsq *E3Csq AisDet Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 78 22030_12 © 2013 Tellabs. The remote alarm consequences affect to the AIS inserting into the received signalling time slot when the frame or the multiframe far-end alarm has been received. 8 is as above. The idle data of unconnected time slots can be defined in this branch.1: the bit will be transmitted at the permanent 1 state.OFF: the remote-end alarm(s) will be generatedON: when the received frame or multiframe far end alarm. The time slots for the signalling groups are CAS A in TS67.ON: AIS will be inserted when the far-end alarm has been received.8) are displayed when the bit rate is 8M. When the fault mask is ON. For this reason only the group CAS A is mentioned here. The fields for the signalling groups are similar. CAS B in TS68. The BER10E3 alarm will have the service alarm status (S). The far-end alarm fault is provided with service alarm status (S). The BER10E3 alarm is generated without service alarm status.8 The following fields (CAS A.8 Buffer FtsData Use of channel associated signalling of group A (TS67). In other cases the last time slot is used for signalling. Bit5. in master clock remote alarm use0: the bit will be transmitted at the permanent 0 state1: the bit will be transmitted at the permanent 1 state *Bit 5. RaiCsq and E3Csq).OFF: The error rate 10E3 does not cause the AIS insertion into the received signal. The field is for handling the Rx buffer. The selected bit rate and the split trunk usage affect the possible buffer length. This field affects the AIS inserting into the received signal when the received signal error rate is worse than 10E-3.X-Con: the bit comes from the cross-connectionCBSC: the bit is controlled by a separate command e.7. Some fault actions and consequences can be defined in this branch. This means that the time slots which are not cross-connected are transmitted with idle data. It is recommended that all bits are set at the state 1. There are three similar fields for selecting the usage of the special bits B5. . the signalling will be in TS5:On: one time slot is reserved for signallingOff: signalling is not used and the signalling time slot can be in data use The fields are displayed if CAS is turned ON. e. The AIS inhibit ON affects the AIS alarm generating. There are four sub-menus (AisInh. 64 frame buffer. In this field the fault mask state (ON/OFF) can be handled.0: the bit will be transmitted at the permanent 0 state.7. if the rate is 384 kbit/s (6 x 64 kbit/s).OFF: The far end alarm does not cause AIS inserting into the signalling time slot(s).g. There are eight similar fields (one field for each bit). no alarms will be generated due to this fault.g.7. each with two states ON/OFF.On: TS67 time slot is reserved for signallingOff: signalling is not used and the signalling time slot can be used for data use Use of the bits 5. TS16 is used for signalling. The far-end alarm fault is generated without service alarm status.7. no alarms will be generated due to this fault. When the bit rate is 1088 kbit/s (17 x 64 kbit/s) or higher. 8. CAS C in TS69 and CAS D inTS 70. 7. B7. no interface faults will be generated (only the fault of the mask itself). *CAS A *Bit 5.8…CAS D. RAI inhibit ON affects the far-end remote alarm generating (from frame and multiframe level). The possible selections: 4.OFF: the AIS alarm will be generatedON: when the received signal is AIS or in the received signalling TS is AIS. RaiInh. B8 of the signalling time slot.4 Installation *CAS Use of channel associated signalling.ON: AIS will be inserted into the received signal when the error rate is worse than 10E-3. Bit5. The loops can be activated/deactivated in this field. The field is displayed only if there is a connection between the neighbors. This is a read-only field where the neighbor node alarms of the neighbor of the target NTUM can be read. This branch has two sub-menu fields Own and the Neighbour alarms (Loop. This is a read-only field where the neighbor node alarms of the target NTUM can be read. The loop can be activated/deactivated and the state of the loops can be seen in this branch.g. the interface is in the unlocked state and the next change is made to lock the interface). Interface Loop. This branch has three sub-menus to activate or deactivate the sending. link number. The interface controls time-out in minutes. interface number and port number).g. Equipment Loop. NnmPara/MesSend and Module). Please note that the text on the LCD display describes the next movement in the locking state if ENTER is pressed (e. The count of errored bits during the test. and HDLC is not used). This is a read-only field where the loop state can be seen (e. it will be deactivated automatically after the time defined in Time-out). these parameters affect the sending and the monitoring of neighbor node parameters. TraBits ErrBits InjErr Time-out Time-out The count of transmitted bits during a test (test generator connected when RL). Remote Loop). unit number. The Alarm fields are auto-refreshed. Copies the existing data structure to the expected field (you have to remember to update). The field is auto-refreshed. the following menus are displayed. This field is used to update the neighbor node parameters into the NTUM. ON: the neighbor node data sending activatedOFF: the neighbor node data sending deactivated ON: the neighbor node state monitoring activatedOFF: the neighbor node state monitoring deactivated ON: the neighbor node supervision activatedOFF: the neighbor node supervision deactivated This field is used to lock or unlock the interface. The expected neighbor data has the same kind of data fields as in the Exist branch. OK). The interface controls time-out parameter can be handled in this branch. The Remote loop availability depends on the interface parameters (Framing. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 79 . the supervision and the monitoring. subrack address. The neighbor node parameters (Expected neighbour and Options) can be changed in other fields but after the changes the parameters must be updated by pressing the ENTER key in the Update field.4 Installation NnmPara This branch handles the neighbor node parameters of the interface. Unexpected neighbour. This branch has six sub-menu fields each of which has data of the existing neighbor (neighbor: node ID. Inject one error into the transmitted data. This is useful when updating the correct neighbor info. When the interface framing is ON and the HDLC channel is in use. (When the loop has been activated. 22030_12 © 2013 Tellabs. Line Loop. if there is the text Lock. No connection. The fields are auto-refreshed. Locking means that the interface allocates the needed capacity from the cross-connection and unlocking that the interface deallocates the reserved cross-connection capacity. HDLC. Update Alarms *Own *Far-end Exist Expec CpyExi Options *MesSend *StaMon *NeigSup Locking Loops State Set When the remote loop is a V54 loop (BTE384. 6. The value describes the time which the incoming data is in the buffer before it is clocked into the cross-connection.The fields are auto-refreshed. The fields are auto-refreshed. The cross-connection bus contains about 1050 cross-connectable time slots (8-bit bytes). This field is auto-refreshed. the display will show the available time.5 Cross-Connection Menu The cross-connection is done in the switching matrix of the NTUM. Read-only information from the received signal level. The commands are stored in a non-volatile memory. Count of buffer slips (read-only). . Clears the G. The time value should remain the same. Count of CRC errors (read-only). By pressing the ENTER key in this field the total time of the statistics can be seen on the display:Total Time9 dd 13 h 24 min 5 sWhen pressing the SCROLL keys. Count of faulty CRC E-bits (read-only). This sub-menu is divided into sub-menus to support the configuration of the various cross-connection formats (TS pair. Clear all error counters. Count of frame alignment losses (read-only). Cross-Connection Configuration Menu Cross-connections can be created and deleted by using the Configuration menu. To simplify the use of this menu it is divided into four sub-menus.821 counters. Read-only information from the received signal quality with A (best quality) through F (poorest quality).4 Installation ErCntrs ResCtrs FraLos FSW CRC CRCE BufSlip Code RxDelay The error counters can be read and cleared in this branch. the incoming clock of the interface differs from the clock used by the cross-connection system.821 statistics. Count of code errors (read-only). The cross-connections of the target NTUM (local or remote) can be configured and seen by using the Cross-Connection menu. The bits from the interfaces are collected by using this bus. The following fields are common to all of these sub-menus: Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 80 22030_12 © 2013 Tellabs. This field is auto-refreshed. TS area and TS bits) and the powerful delete operation (Del All). Count of faulty frame alignment words (read-only). The cross-connect switch combines (in other words. Branch to the standard G. G. This sub-menu can be accessed only when the NTUM is in the stand-alone mode and the panel is unlocked.821 *Display *ResG821 BbInfo *RxLevel *RxOual 4. This branch is displayed if the interface module is BTE-384 or BTE-768. makes the cross-connection) the needed new bytes for the interfaces in accordance with the cross-connection commands by using 8 kbit/s granularity. severely errors seconds. errored seconds and degraded minutes. If the time increases or decreases. the unavailable time. they are mapped either to the XB channel or to the corresponding signalling bits (n x 500 bit/s) of the XD channel. The number of the signalling bits depends on the capacity of the XB channel. When it has been selected by using the SCROLL keys. Before executing the cross-connection operation all parameters should be set.b) 2 bits (c. b. 22030_12 © 2013 Tellabs. If the interfaces are equipped with signalling or control signals. the operation can be executed by pressing the ENTER key. c and d bits of the XD channel in the G. TS area and TS bits sub-menus and it is used to execute the desired cross-connection operation that is either CreCons (create) or DelCons (delete). Four signalling bits are reserved for each time slot.d) 1 bit (a ) 1 bit (b ) 1 bit (c ) 1 bit (d ) The a. Data interfaces do not normally use the XD channel.c.b. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 81 . Even if only some of the bits are needed. all four bits are cross-connected and transferred to the far-end channel interface.704 structure) 2 bits (a. The XB channel can be a combination of 64 kbit/s and 8 kbit/s signals. The n x 500 bit/s signalling bits are called the XD channel of the interface. This field is used to specify the channel of the cross-connection. The n x 8 kbit/s and n x 64 kbit/s groups mapped by the channel interfaces are called the XB channel.704 frame.704 multiframe correspond to the XB channel time slots in the G.d bits in G. Signalling bits are reserved for the XB channel in the following way. This field is used to specify the directionality of the cross-connection: either unidirectional (A→B) or bidirectional (A⇔ B). Dir XB+XD XB Capacity TSn/B1…B8 TSn/B1…B4 TSn/B5…B8 TSn/B1…B2 TSn/B3…B4 TSn/B5…B6 TSn/B7…B8 64 kbit/s 32 kbit/s 32 kbit/s 16 kbit/s 16 kbit/s 16 kbit/s 16 kbit/s XD Capacity 4 bits (a.704 compliant multiframe of the 2 or 8 Mbit/s trunk. The capacity reserved by XB and XD channels is determined by the interface type and the user requirements.4 Installation Oper This is the leftmost field of the TS pair. In the later case the signals are mapped to the G. This is the source time slot of the unidirectional connection. 35 XB and XD Channels in Network X-Group If the cross-connection is a part of the cross-connection group (X-Group). This is the source interface of the unidirectional connection. TS A. TS B where • IF A: Interface number (only locked interfaces are valid). Both interfaces of the connection should reside in the same NTUM (local or remote). • TS B: Number of the time slot in the IF B. TS A = 2. . • TS A: Number of the time slot in the IF A. The X-Group IDs 1…16382 are valid. TS B = 5 Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 82 22030_12 © 2013 Tellabs. The TS pair cross-connection format describes the connection between the time slot of an interface and another time slot of the same or another interface. IF B = 2. • IF B: Interface number (only locked interfaces are valid). Dir. This is the destination time slot of the unidirectional connection. the ID of the group can be set by using this field. IF B.4 Installation Fig. XB. Time Slot Pair The TS Pair sub-menu contains the following fields: Oper X-Group. Example: DIR = A<->B. This is the destination interface of the unidirectional connection. A zero X-Group ID indicates that the cross-connection is not a member of any of the X-Groups and it is always in the active state. XB+XD. IF A. IF A = 1. IF A = 1. • IF B: Interface number (only the locked interfaces are valid). Dir . 36 Cross-Connection of One Time Slot between Two Framed Interfaces Time Slot Area The TS area cross-connection format describes the connection between the continuous area of time slots of an interface and another continuous area of time slots of the same or another interface. Both interfaces of a connection should reside in the same NTUM (local or remote). XB. • lstTS B: Number of the last time slot of the area in the IF B. • fstTS B: Number of the first time slot of the area in the IF B. lstTS B = 5 Fig. This specifies the destination of the unidirectional connection. IF B = 2. lstTs B where • IF A: Interface number (only the locked interfaces are valid). XB+XD. Example: DIR = A->B. This specifies the source of the unidirectional connection. IF A. This specifies the source of the unidirectional connection. The TS Area sub-menu contains the following fields: Oper X-Group. This is the source interface of the unidirectional connection. lstTS A = 2. fstTS A.4 Installation Fig. lstTS A. fstTs B. This specifies the destination of the unidirectional connection. fstTS A = 0. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 83 . fstTS B = 3. 37 Cross-Connection of Three Time Slots between Two Framed Interfaces 22030_12 © 2013 Tellabs. • fstTS A: Number of the first time slot of the area in the IF A. This is the destination interface of the unidirectional connection. • lstTS A: Number of the last time slot of the area in the IF A. IF B. • IF B: Interface number (only the locked interfaces are valid). Example: DIR = A<->B. The X-Group identifier of the cross-connections to be deleted can be specified. XB. The interfaces that are to be connected should reside in the same NTUM (local or remote). The bit mask consists of eight bits (one byte) where a 1 state of a bit indicates the connection.4 Installation Time Slot Bits The TS Bits cross-connection format describes the connection between the bits in a time slot of an interface and other bits in a time slot of the same or another interface. In the user interface of the NTUM the bit mask is presented in the hexadecimal format. 4. This is the source interface of the unidirectional connection. IF B. . • TS A: Number of the time slot in the IF A. Dir. • bMask B: Bit mask of the TS B. 38 Cross-Connection of Time Slot Bits Delete All This menu is used to delete all cross-connections of the target NTUM (local or remote). which will delete all cross-connections of the target NTUM. • bMask A: Bit mask of the TS A. TS B. TS A. bMask B where • IF A: Interface number (only the locked interfaces are valid). bMask A = 85H. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 84 22030_12 © 2013 Tellabs. bMask A. bMask = 62H Fig. TS A = 2. XB+XD. The TS area sub-menu contains the following fields: Oper X-Group. IF B = 2. The default value of the X-Group identifier is Any. This is the destination interface of the unidirectional connection.7 Binary-to-Hexadecimal Conversion Table contains the table for the binary to hexadecimal conversion. IF A = 1. TS B = 5. This is the source time slot of the unidirectional connection. • TS B: Number of the time slot in the IF B.7. IF A. This is the destination time slot of the unidirectional connection. To see the state of the x-groups of the existing cross-connections. x-group) connections. the text No connections is shown. It is much more simple to passivate the current configuration and activate the new one by passivating and activating the x-groups than deleting the current commands and creating new ones by using the Cross-Connection Configuration menu. • Display: By using this menu the current state of the x-groups can be seen and their states can be changed. in other words it does not contain any cross-connections. press the ENTER key when the existing cross-connection is on the display. The x-group IDs 1…16382 are valid and the state of the x-groups are stored in a non-volatile memory. If the target NTUM does not contain the specified (interface. The letter E in the status line of an x-group indicates that the x-group is empty. Several x-groups can be in active state at the same time if the cross-connections of these x-groups do not overlap each other. Also the existing cross-connections can be deleted more efficiently than by using the Configuration menu. otherwise press EXIT. the operation can be executed by pressing the ENTER key. Display). each on its own line. After that the states of the first two x-groups are shown on the LCD display. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 85 . To see the existing cross-connections. • Oper: This field specifies an operation which is used either to activate (ActGrp) or to passivate (PassGrp). The rest of the connections can be viewed by using the SCROLL keys. The cross-connection is shown so that it occupies both lines of the LCD display and the source end of the unidirectional connection is on the upper line. 22030_12 © 2013 Tellabs. a question Delete connection? is shown. The X-Group identifier and one interface of the cross-connections to be displayed can be specified. all cross-connections of that x-group are active. Otherwise. The text Getting is shown on the display during the message send/receive operation. • X-Group: This field is used to specify the x-group to be activated or passivated. The existing cross-connection can be deleted by using this menu only when the NTUM is in stand-alone mode and the panel is unlocked. It can be accessed only when the NTUM is in stand-alone mode and the panel is unlocked. press ENTER when the cursor blinks over the Display field. The text Getting is shown on the display during the message send/receive operation.4 Installation Cross-Connection Display Menu By using this menu the current state of the cross-connections can be seen. • Configuration: This menu is used to activate and passivate the x-groups. To simplify the use of this menu it is divided into two sub-menus (Config. After that. Press ENTER again if you want to delete the connection. When the operation has been selected by using the SCROLL keys. The x-group is either active or passive. X-Group Menu An x-group is a group of the cross-connections that have a common x-group identifier. If the x-group is active. the first connection is shown. The x-group concept is very useful when the user wishes to use one NTUM in the different cross-connection configurations. Before executing the operation the x-group should be specified. The rest of the x-groups can be viewed by using the SCROLL keys. The x-group configuration menu consists of the following fields. press the ENTER key twice when the cursor blinks over the GetCons field on the upper line of the LCD display. The state of the x-groups of the NTUM can be configured and seen by using the X-Group menu. To delete it. Each time slot contains eight bits. When the interface has been selected. Note that x-group 0 is always active and it is not possible to change its state.6. Now the ENTER key must be pressed and the cursor moves on the LocIf1 text. The interface where parameters will be copied to is selected with the SCROLL keys and the parameters are copied by pressing the ENTER key. Press ENTER again if you want to change the state. the text Peer interface is IF1 appears on the LCD display where the user can select the other interface of the cross-connection(s). press ENTER when the cursor is on the upper line of the display. the reading of the parameters is activated by pressing the ENTER key and the text CpyTo is displayed. Now the ENTER key must be pressed and the cursor moves to the interface/device selection. Now the ENTER key must be pressed and the cursor moves to the interface selection. Now the ENTER key must be pressed and the cursor moves on the LocIf1 text. the reading of the cross-connections is activated by pressing the ENTER key and the text CpyTo is displayed. otherwise press EXIT. After that the question Activate/Passivate X-Group n? is shown. or the whole cross-connection of the device can be copied. 4. Also the cross-connection of one interface can be copied to another. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 86 22030_12 © 2013 Tellabs. The capacities of the two first interfaces are displayed and the rest of the interfaces can be viewed by using the SCROLL keys. The cross-connection(s) that are to be copied are selected using the SCROLL keys. After that the text CpyFrom is shown on the display. When the interface/device has been selected. the XD symbol is added at the end of the line.4 Installation The state of the x-groups can be changed by using this menu only when the NTUM is in stand-alone mode and the panel is unlocked. To change the state of the x-group.6 Copy Settings Menu The interface parameters can be copied from one interface to another (the locking state and the configured module type are not copied). press ENTER when the cursor blinks on the IF Cap? text. Then the interface where parameters will be copied from is selected by using the SCROLL keys. Interface Capacity Menu This menu displays the cross-connection capacity of the locked interfaces of the target NTUM (local or remote). The copy of the cross-connections is confirmed by pressing the ENTER key. Copy Cross-Connections Menu The copying of the cross-connections is started by pressing the ENTER key in the X-Con field. . To see the capacity of the interfaces. After that the CpyFrom text is shown on the display. If the interface has signalling capacity. Copy Interface Parameters Menu The copying of the interface parameters is started by pressing the ENTER key in the IfParam field. The target to which the cross-connections are to be copied is selected with the SCROLL keys. The copying possibility depends on the mode of the device and the panel state. If the selected interface where the copy has been performed from has connections only to one interface. The capacity of an interface is displayed in the time slots + bits format. 4. This must be performed as the first operation after a reset and within 30 seconds from the activation of the display. 4.6.1 Framed Interface Used as 2048 kbit/s Trunk Main Parameters Bit rate Framing Control type Buffer length 2048 kbit/s ON Normal 4 Frames Bit Usage FSW usage TS0 B1 usage CRC E-bits usage TS0 B4 B5 B6 B7 B8 FSW Regenerate CRC Rem end error ind Permanent 1 HDLC HDLC HDLC HDLC ON OFF TS0 HDLC link Master clock RAI Free TS Data 1 1 2 1 3 1 4 1 5 1 6 1 7 1 8 1 CAS Free bits B5 B7 B8 ON Permanent 1 Permanent 1 Permanent 1 22030_12 © 2013 Tellabs.4 Installation The copying of the cross-connections is confirmed by pressing the ENTER key. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 87 . press all the four keys simultaneously for about five seconds until the display shows the items of the Security menu.7 Entering Security Menu of Tellabs 8120 Mini Node M To enter the Security menu.7 Recommended Settings of Framed Interfaces In the next chapter there are some examples of setting parameters for framed interfaces. 4.7. 7.2 Framed Interface Used as 2048 kbit/s User Access Point Main Parameters Bit rate Framing Control type Buffer length 2048 kbit/s ON Normal 4 Frames Bit Usage FSW usage TS0 B1 usage CRC E-bits usage TS0 B4 B5 B6 B7 B8 FSW Regenerate CRC Rem end error ind Permanent 1 Permanent 1 Permanent 1 Permanent 1 Permanent 1 OFF OFF -- HDLC link Master clock RAI Free TS Data 1 1 2 1 3 1 4 1 5 1 6 1 7 1 8 1 CAS Free bits B5 B7 B8 ON Permanent 1 Permanent 1 Permanent 1 Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 88 22030_12 © 2013 Tellabs. .4 Installation NNM Parameters NNM options Neighbour supervision State monitoring Message sending Expected neighbour Node Subrack Unit Link Interface Port Any Any Any Any Any Any Off Off On 4. CRC shall be used if the user access device can use G. If the CRC is not used. the recommended usage for TS0 B1 is Permanent 1.704 framing with CRC-4. 4.3 Framed Interface Used as 8448 kbit/s Trunk Main Parameters Bit rate Framing Control type Buffer lenght 8448 kbit/s ON Normal 4 Frames Bit Usage TS99 B1…B7 usage TS99 B8 usage TS66 B8 usage CRC E-bits usage HDLC link Bit mask 1 1 2 1 3 1 4 1 5 1 6 1 7 1 8 1 CRC Permanent 1 Permanent 1 Rem end error ind ON TS33 Master clock RAI OFF 22030_12 © 2013 Tellabs.7. Because the HDLC channel is not used. CAS will be used if the user access device needs the channel associated signalling.4 Installation NNM Parameters NNM options Neighbour supervision State monitoring Message sending Expected neighbour Node Subrack Unit Link Interface Port Any Any Any Any Any Any Off Off Off The HDLC channel is not used in a user access point. all NNM options are set to the off state. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 89 . 4 Installation Free TS Data 1 1 2 1 3 1 4 1 5 1 6 1 7 1 8 1 CAS.7. . All Groups Free bits B5 B7 B8 ON Permanent 1 Permanent 1 Permanent 1 NNM Parameters NNM options Neighbour supervision State monitoring Message sending Expected neighbour Node Subrack Unit Link Interface Port Any Any Any Any Any Any Off Off On 4.4 BTE-384-M Settings Main Parameters Bit rate Framing Control type Buffer lenght 6 x 64 kbit/s (384 kbit/s) ON Normal 4 Frames Bit Usage FSW usage TS0 B1 usage CRC E-bits usage TS0 B4 B5 B6 B7 B8 FSW Regenerate CRC Rem end error ind Permanent 1 HDLC HDLC HDLC HDLC ON TS0 HDLC link Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 90 22030_12 © 2013 Tellabs. the Scrambler mode setting will be Answer and the Wetting current setting will be in the On state.7. BTE-576-M.4 Installation Master clock RAI OFF Free TS Data 1 1 2 1 3 1 4 1 5 1 6 1 7 1 8 1 Baseband Line connection Scrambler type Scrambler mode Output level Wetting current 2-wire full duplex V. 4.5 BTE-320-M. These settings are for connection to a Tellabs 8100 node.32 Call +0 dBm Off CAS OFF NNM Parameters NNM options Neighbour supervision State monitoring Message sending Expected neighbour Node Subrack Unit Link Interface Port Any Any Any Any Any Any Off Off On The Baseband settings depend on which equipment Tellabs 8120 mini node M is connected to. BTE-1088-2W-M and BTE-2304-M Settings Main Parameters Bit rate (depends on the module) 5 x 64 kbit/s (BTE-320-M) 9 x 64 kbit/s (BTE-576-M) 17 x 64 kbit/s (BTE-1088-2W-M) 36 x 64 kbit/s (BTE-2304-M) ON Framing 22030_12 © 2013 Tellabs. If the piece of equipment connected to Tellabs 8120 mini node M is SBM 384A. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 91 . . Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 92 22030_12 © 2013 Tellabs.4 Installation Main Parameters Control type Buffer length Normal 4 frames Bit Usage FSW usage TS0 B1 usage CRC E-bits usage TS0 B4 B5 B6 B7 B8 FSW Regenerate CRC Rem end error ind Permanent 1 HDLC HDLC HDLC HDLC ON TS0 HDLC link Master clock RAI OFF Free TS Data 1 1 2 1 3 1 4 1 5 1 6 1 7 1 8 1 Baseband Line connection Scrambler type Scrambler mode Output level Timing 2-wire full duplex V.5 dBm Master/Slave26 CAS OFF NNM Parameters NNM options Neighbour supervision State monitoring Message sending Expected neighbour Node Subrack Any Any Off Off On 26It depends on the other end settings.32 Call/Answer26 +13. TS A = 4. bMask A = c0H. trunk <-> IF3. V.7. bMask B = 03H Fig.35 64kbit/s + CRC + Control Channel (8 kbit/s) IF Cap = 1TS+2bits (Use the menu to get this information) DIR = A<->B.7.6 Cross-Connection Example IF 1. 39 Cross-Connecting Example 4. IF A = 1. IF B = 3. IF A = 1. TS B = 1.4 Installation NNM Parameters Unit Link Interface Port Any Any Any Any 4. TS A = 6. IF B = 3. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 93 . XB.7 Binary-to-Hexadecimal Conversion Table CCITT BITS B1 B5 0 0 0 0 B2 B6 0 0 0 0 B3 B7 0 0 1 1 B4 B8 0 1 0 1 BIT MASK IN HEXADECIMAL FORMAT 0 1 2 3 22030_12 © 2013 Tellabs. XB. TS B = 0 DIR = A<->B. 40 presents the mechanical construction of Tellabs 8120 mini node M. The Fig.4 Installation CCITT BITS B1 B5 0 0 0 0 1 1 1 1 1 1 1 1 B2 B6 1 1 1 1 0 0 0 0 1 1 1 1 B3 B7 0 0 1 1 0 0 1 1 0 0 1 1 B4 B8 0 1 0 1 0 1 0 1 0 1 0 1 BIT MASK IN HEXADECIMAL FORMAT 4 5 6 7 8 9 A B C D E F Examples on Binary-to-Hexadecimal Conversion CCITT BITS B1 0 0 0 0 0 0 0 1 0 1 B2 0 0 0 0 0 0 1 1 1 0 B3 0 0 0 0 0 1 1 1 0 1 B4 0 0 0 0 1 1 1 1 1 0 B5 0 0 0 1 1 1 1 1 1 0 B6 0 0 1 1 1 1 1 1 0 1 B7 0 1 1 1 1 1 1 1 1 0 B8 1 1 1 1 1 1 1 1 0 1 BIT MASK IN HEXADECIMAL FORMAT 01 03 07 0F 1F 3F 7F FF 5A A5 4. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 94 22030_12 © 2013 Tellabs. most of the settings needed in installation can be done without opening the case.8 Service Operations and Modifications Tellabs 8120 mini node M is housed in a metallic case suitable for tabletop use. . The numbers in brackets in the following description refer to the numbers in that figure. Because the configuration of Tellabs 8120 mini node M is performed with various user interfaces. the power supply (#9) under the protection cover (#7) and up to four changeable interface modules (#1 and #4). The straps of the interface modules depend on the module type. The operation must be performed by qualified personnel only. 11. In order to make any physical changes in Tellabs 8120 mini node M hardware. Upper modules (unframed interfaces) Metal top cover Interface unit VCM 402 Lower modules (framed interfaces) Main unit SMU 701 Mains supply unit protection cover Distance bolts Power supply Screws Metallic lower casing Front panel Grounding earth wire Spacers 22030_12 © 2013 Tellabs. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 95 .11 Connectors and Strappings of Unframed Interfaces. as it involves electrical safety. 40 are the following: 1. 2. The numbered items in Fig. • Changing the setting of the straps on the interface modules. 8. • Changing the interface modules.4 Installation Inside the metallic case there are the main unit (#6). the interface unit (#3). such as changing the interface modules. 10. Tellabs 8120 mini node M must be disconnected from the mains supply before removing the cover as high voltages are present inside Tellabs 8120 mini node M case. • Updating the controller software by changing the EPROMs. 13. 4.10 Connectors and Strappings of Framed Interfaces and 4. 5. 12. 7. 3. The following service operations or modifications require the opening of the casing. 9. 6. Strapping instructions can be found in 4. the casing must be opened. slide the cover backwards and lift it off. .4 Installation Fig. To remove the VCM402 PCB you have to remove both upper modules first and loosen and remove the distance bolts. • The upper modules can now be lifted off. loosen and remove the screws on the modules. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 96 22030_12 © 2013 Tellabs.1 Instructions on Disassembling Tellabs 8120 Mini Node M The following steps are required when disassembling Tellabs 8120 mini node M. To remove the upper modules (#1). 40 Mechanical Construction of Tellabs 8120 Mini Node M 4. Loosen and remove all the screws at the back panel of Tellabs 8120 mini node M.8. • VCM402 can now be lifted off. Step 1 Step 2 Step 3 Step 4 Check that Tellabs 8120 mini node M is disconnected from the mains supply. negative pole earthed Unit power supply module. 22030_12 © 2013 Tellabs. • Check with the service computer or with the user interface of the NTU that the voltages are in normal range. Step 8 Step 9 Do not use unnecessary force when tightening the screws and nuts. If the lower interface modules are not assembled. • Check very carefully that the pins are set into the connectors in the correct position and that the pins are not bent. 4. When adding a new interface module. make sure that no loose parts are left inside the box. it is compulsory to use spacers under the distance bolts. check that Tellabs 8120 mini node M starts running in the normal way and that no unusual alarms are visible.9. 40…60 V DC.9 4.4 Installation Step 5 To remove the lower interface modules loosen and remove the distance bolts. positive pole earthed 1 1 1 0…1/SMU 0…1/SMU 0…1/SMU Equipping PDU 423 27The product has been discontinued.704 interfaces and four V type interfaces Main unit V interface base unit Tellabs 8120 mini node M program AC/DC power supply Unit power supply module. • If Tellabs 8120 mini node M malfunctions. Step 10 When the power is connected. remove the metal plate covering the interface slot in the back panel. • The lower modules can now be lifted off. When connecting the transmission modules or the interface board to the pin connectors. Step 6 Step 7 The Tellabs 8120 mini node M device is assembled in the opposite order. Before connecting the power. take care not to bend the pins of the connectors. The cover is removed by bending the plate until the points of support brake. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 97 .1 Unit List of Tellabs 8120 Mini Node M Common Units Name SMU-M SMU 701 VCM 402 SMZ 414 a b c 8990NFS40 PDU 42227 Description Multiplexer for two G. disconnect the power and check that the assembly was made correctly and that the pin connectors are positioned in the correct way. 19…36 V DC. 1 interface/module) Name a LTE-M28 LTE 404 OTE-LED-M OTE 405 BTE-384-M28 BTE 406 DPZ 380 G703-75-M GDH 477 G703-120-M GDH 487 G703-8M-M28 GDH 508 BTE-2048-M28 BTE 424 BAI 482 DPZ 498 BTE-20482W-M28 BTE 496 BAI 497 DPZ 578 BTE-1088-M28 BTE 479 BAI 483 DPZ 498 BTE-4096-M28 BTE 481 BAI 484 DPZ 498 Description Line terminal 2 or 1 Mbit/s LTE-M base module Optical LED 2 or 8 Mbit/s OTE-LED-M base module Baseband module 384 kbit/s Baseband base module 128…384 kbit/s Parameter PROM G703 2 Mbit/s. 120 Ω symmetrical G703-120-M base module G703 8 Mbit/s.9. 75 Ω coaxial G703-75-M base module G703 2 Mbit/s. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 98 22030_12 © 2013 Tellabs. 75 Ω coaxial G703-8M-M base module Baseband module 2048 kbit/s Baseband base module Baseband analog submodule Signal processor PROM T-SDSL module 2048 kbit/s 2w T-SDSL base module T-SDSL analog submodule Signal processor PROM Equipping 0…2/SMU 1/LTE-M 0…2/SMU 1/OTE-LED-M 0…2/SMU 1/BTE-384-M 1/BTE 406 0…2/SMU 1/G703-75-M 0…2/SMU 1/G703-120-M 0…2/SMU 1/G703-8M-M 0…2/SMU 1/BTE 1/BTE 1/BTE 0…2/SMU 1/BTE 1/BTE 1/BTE b c d e f g h i Baseband module 1088 kbit/s Baseband base module Baseband analog submodule Signal processor PROM Baseband module 4096 kbit/s Baseband base module Baseband analog submodule Signal processor PROM 0…2/SMU 1/BTE 1/BTE 1/BTE 0…2/SMU 1/BTE 1/BTE 1/BTE j 28The product has been discontinued. .2 Main Interface Modules (G.704 framed interfaces IF1 and IF2.4 Installation 4. 2-wire T-SDSL base module Signal processor PROM T-SDSL module 1088 kbit/s. 2/4-wire T-SDSL base module Signal processor PROM 0…2/SMU 1/BTE 1/BTE 4.24/V. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 99 .35 n x 64 kbit/s…2 Mbit/s scrambler V35-G704-SM base module X.21 0.28 IF/DTE. 2 ch V24-DCE-M base module V.24/V.6…n x 64 kbit/s interface module. 2/4-wire T-SDSL base module Signal processor PROM Equipping 0…2/SMU 1/V35-G704-SM 0…2/SMU 1/X21-G704-SM 0…2/SMU 1/BTE 1/BTE 0…2/SMU 1/BTE 1/BTE 0…2/SMU 1/BTE 1/BTE l m n o p T-SDSL module 2304 kbit/s. 2 ch V36-M base module V. 56. n x 64 kbit/s interface module.6…64 kbit/s IF module. 0. 2 ch V35-M base module V.28 IF/DCE.4 Installation Name k V35-G704-SM28 VDH 474 X21-G704-SM28 XDH 473 BTE-320-M28 BTE 592 DPZ 650 BTE-576-M28 BTE 596 DPZ 650 BTE-10882W-M28 BTE 559 DPZ 650 BTE-2304-M28 BTE 562 DPZ 650 Description V. n x 64 kbit/s interface module. 0. 2 ch X21-M base module Equipping 0…2/SMU 1/V35-M 0…2/SMU 1/V36-M 0…2/SMU 1/V24-DCE-M 0…2/SMU 1/V24-DTE-M 0…2/SMU 1/X21-M b c d e 22030_12 © 2013 Tellabs. 2 ch V24-DTE-M base module X.3 V Series Interface Modules (Interfaces IF3-IF6) Name a V35-M VDM 409 V36-M28 VDM 410 V24-DCE-M28 VDS 411 V24-DTE-M28 VDS 416 X21-M XDM 412 Description V.21 n x 64 kbit/s…2 Mbit/s scrambler X21-G704-SM base module T-SDSL module 320 kbit/s. 56.9. 2-wire T-SDSL base module Signal processor PROM T-SDSL module 576 kbit/s.6…64 kbit/s IF module.36 48.35 48. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 100 22030_12 © 2013 Tellabs. G.6…n x 64 kbit/s interface module. .10. 2 ch V35-IEC/V24-DCE-M base module HSSI. 0.6…n x 64 kbit/s. 1 ch HSSI-M base module Mini LAN Module. 1 ch Mini LAN Module base module Equipping 0…2/SMU 1/G703-64-M 0…2/SMU 1/V35-IEC/V24 0…2/SMU 1/HSSI-M 0…2/SMU 1/Mini LAN Module g h i 4. The connector is coaxial SMB. 41 Front Panel of G703-75-M The G703-75-M module is used when 75 Ω coaxial cable interface is needed.4 Installation Name f G703-64-M29 GCL 413 V35/V24-M29 VDM 434 HSSI-M28 HDH 708 Mini LAN Module EBH719 Description G. The Tx and Rx coaxial cable shields are fixed to ground.1 G703-75-M and G703-120-M. 29The product has been discontinued.703 2 Mbit/s Front Panel of G703-75-M Fig. 0.24/DCE. interface module. 2 ch G703-64-M base module V.35-IEC+V.10 Connectors and Strappings of Framed Interfaces 4. interface module.703 64 kbit/s co/contradir. 0 are as follows.0 or higher) Pin 1 2 4 5 6 9 Signal TxB TxA RxB RxA Ground Ground Settings for Use with 120 Ω Symmetrical Cable Strapping instructions for v1. Fig. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 101 .0) Pin 1 2 4 5 6 9 Signal Transmit signal B Transmit signal A Receive signal B Receive signal A Tx cable shield Rx cable shield J1 Connector Pins (v2. 43 D-Type 9-Pin Female Connector J1 Connector Pins (v1. 22030_12 © 2013 Tellabs. 42 Front Panel of G703-120-M The G703-120-M module is used when 120 Ω symmetrical cable interface is needed.4 Installation Front Panel of G703-120-M Fig. 10.2 LTE-M Line Terminal 1 or 2 Mbit/s Front Panel Fig. .4 Installation Strap CN5 CN8 Main Position ON ON Alternative Position OFF OFF Function of Main Position Tx cable shield grounded Rx cable shield grounded Note that there are no strappings with v2. 45 D-Type 9-Pin Female Connector P2 Connector Pins Pin 1 2 4 5 6 9 Signal Transmit signal B Transmit signal A Receive signal B Receive signal A Tx cable shield Rx cable shield Settings for Use with 120 Ω Symmetrical Cable Strap S1 S2 Main Position 2 1 Alternative Position 1 2 Function of Main Position Tx cable shield grounded Rx cable shield not grounded Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 102 22030_12 © 2013 Tellabs. 4. 44 Front Panel of LTE-M Fig.0 or higher. 4 OTE-LED-M. 2 or 8 Mbit/s Front Panel Fig. Strappings There are no strappings on the G703-8M-M module. 46 Front Panel of G703-8M-M The connector is coaxial SMB.4 Installation 4. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 103 . 8 Mbit/s Front Panel Fig. 22030_12 © 2013 Tellabs.3 G703-8M-M.10.10. 4. Optical LED. The Rx and Tx coaxial cable shields are fixed to ground. Strappings There are no strappings on the OTE-M module. 47 Front Panel of OTE-M The connector is a standard optical connector of FC type. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 104 22030_12 © 2013 Tellabs. BTE-2048-2W-M and BTE-4096-M. 49 D-Type 9-Pin Female Connector Pin Assignment at CN1 4-WIRE USE Pin 1 2 3 4 5 6 7 8 9 Transmit signal B Transmit signal A Not connected Receive signal B Receive signal A TX cable shield Not connected Not connected RX cable shield 2-WIRE USE BTE-384-M Not connected Not connected Not connected Tx/Rx signal B Tx/Rx signal A Not connected Not connected Not connected Cable shield BTE-2048-2W-M Tx/Rx signal B Tx/Rx signal A Not connected Not connected Not connected Not connected Not connected Not connected Cable shield Strappings in BTE-384-M There are two strappings available on the BTE-384-M baseband module. BTE-2048-2W-M and BTE-4096-M Fig. 384 kbit/s…4224 kbit/s Front Panel Fig. BTE-2048-M. BTE-1088-M.5 BTE-384-M.4 Installation 4. .10. 48 Front Panel of BTE-384-M. BTE-1088-M. BTE-2048-M. this function is disabled in Tellabs 8000 manager. The default position of the strappings is off. • If the customer wants to enable switching of wetting current. it can be turned ON or OFF in Tellabs 8000 manager. shields not grounded. If wetting current is disabled. This mode is not recommended due to EMC requirements.4 Installation • S1: TX direction cable shield grounded/not grounded • S2: RX direction cable shield grounded/not grounded (RX/TX direction in BTE-384 in 2-wire mode) • S3/S4: wetting current enabled/disabled • If wetting current is enabled. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 105 . Fig. 51 S3 and S4 Located between Line Transformers M1 and M2 Strappings in Other BTE Modules There are two strappings available on the module. 50 BTE-384-M Strappings The strappings are located near the line connector. • J1: TX direction cable shield grounded/not grounded • J4: RX direction cable shield grounded/not grounded 22030_12 © 2013 Tellabs. both S3 and S4 must be in position ON. Fig. These modules do not have any strappings. 320…2304 kbit/s Front Panel Fig. BTE-1088-2W-M and BTE-2304-M. The default position of the strappings is off.4 Installation Fig. BTE-576-M. BTE-1088-2W-M. . BTE-2304-M) Tx/Rx signal B Tx/Rx signal A Not connected Not connected Not connected 1 2 3 4 5 Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 106 22030_12 © 2013 Tellabs. BTE-2304-M) Transmit signal B Transmit signal A Not connected Receive signal B Receive signal A 2-WIRE USE (BTE-320-M.10. 4.6 BTE-320-M. BTE-576-M. 52 BTE Strappings The strappings are located near the line connector. shields not grounded. BTE-576-M. BTE-1088-2W-M and BTE-2304-M. BTE-576-M. BTE-1088-2W-M and BTE-2304-M Modules Fig. BTE-320-M. 53 Front Panel of BTE-320-M. This strapping information does not concern the following BTE modules. 54 D-Type 9-Pin Female Connector Pin Assignment at CN1 Pin 4-WIRE USE (BTE-1088-2W-M. BTE-1088-2W-M.35 n x 64 kbit/s…2 Mbit/s Front Panel Fig. V. BTE-576-M.4 Installation Pin 4-WIRE USE (BTE-1088-2W-M. 56 D-Type 9-Pin Female Connector D-Type 9-Pin Female Connector Pin 1 2 3 4 5 6 7 8 9 Signal Transmit Signal B Transmit Signal A Ground Receive Signal B Receive Signal A Transmit Clock B Transmit Clock A Receive Clock B Receive Clock A 103B 103A 115B 115A 113B 113A In In Out Out In In Name (DTE) 104B 104A Direction Out Out 22030_12 © 2013 Tellabs. BTE-576-M.7 V35-G704-SM. BTE-2304-M) Not connected Not connected Not connected Not connected 2-WIRE USE (BTE-320-M.10. BTE-576-M. 4. BTE-2304-M) Not connected Not connected Not connected Not connected 6 7 8 9 Strappings in BTE-320-M. BTE-1088-2W-M and BTE-2304-M modules do not have any strappings. 55 Front Panel of V35-G704-SM Module Fig. BTE-1088-2W-M and BTE-2304-M Modules The BTE-320-M. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 107 . Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 108 22030_12 © 2013 Tellabs.10.4 Installation Strappings All strappings of the module must be in position 1. out Direction Out Out Notice Strappings All strappings of the module must be in position 1 when used in DTE mode. 4. n x 64 kbit/s…2Mbit/s Front Panel Fig. The factory settings are in position 1. All strappings of the module must be in position 2 when used in DCE mode. out DCE. 57 Front Panel of X21-G704-SM Fig.8 X21-G704-SM. 58 D-Type 9-Pin Female Connector D-Type 9-Pin Female Connector Pin 1 2 3 4 5 6 7 8 9 Signal Transmit Signal B Transmit Signal A Ground Receive Signal B Receive Signal A Transmit Clock B Transmit Clock A Receive Clock B Receive Clock A Name (DTE) T/b T/a G R/b R/a X/b X/a S/b S/a In In Out Out In In DCE. . 59 Front Panel of V35-M Module Fig.35 interface is equipped with a rectangular 34-pin female connector according to ISO 2593 Standard. V. Data and timing signals are symmetrical with a level of 0.6 mm.1 V35-M. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 109 . n x 64 kbit/s Interfaces. 2 pcs Fig. The electrical characteristics of the control circuits are in accordance with V.11 Connectors and Strappings of Unframed Interfaces 4.35 48.28 output Received data V. V35 Connector Pin Assignment Pin Number A B P S R T C D E CCITT V.28 V.35 Circuit Number --102 103A 103B 104A 104B 105 106 107 input output output Request to send Ready for sending Data set ready V.35 Input/Output Cable shield Signal ground input Transmitted data V.28 V.55 V (+ 20%) to 100 Ω load. 56.35 Signal Level Signal 22030_12 © 2013 Tellabs. 60 34-Pin Female Connector The V. The nominal connector pin diameter is 1.4 Installation 4.28.11. The connector is provided with two UNC 6-32 locking screws. 36 48.35 output Transmitted data timing from VCM V. V.28 V. The connector is furnished with two either UNC 4-40 or M3 locking screws.4 Installation Pin Number F H U W Y AA V X N L NN CCITT V.35 input input output Remote loop-back Local loop-back Test indicator V.36 interface is provided with a 37-pin female D-connector according to ISO 4902 Standard.28 4. 56. 61 Front Panel of V36-M Module Fig.28 V. 2 pcs Fig. .28 V. n x 64 kbit/s Interfaces.28 V. 62 D-Type 37-Pin Female Connector The V.35 output Received data timing from VCM V.2 V36-M.11. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 110 22030_12 © 2013 Tellabs.35 Circuit Number 109 108 113A 113B 114A 114B 115A 115B 140 141 142 Input/Output output input input Signal Level Signal Signal detector Data terminal ready Transmitted data timing from DTE V. 11 input Transmitted data timing from DTE V.28 V.28 V.11 output Signal detector V.11 input Request to send V.11 input Input/ Output Signal Level Signal Cable shield Signal ground Transmitted data V.11 22030_12 © 2013 Tellabs.11 output Data set ready V.36 Circuit Number --102 103A 103B 104A 104B 105A 105B 106A 106B 107A 107B 109A 109B 108A 108B 113A 113B 114A 114B 115A 115B 140 141 142 input input output Remote loop-back Local loop-back Test indicator V. 20 4 22 6 24 7 25 9 27 11 29 13 31 12 30 17 35 5 23 8 26 14 10 18 CCITT V.4 Installation V36 Connector Pin Assignment Pin Number 1 19.11 output Received data V.28 output Received data timing from VCM V.11 input Data terminal ready V.11 output Transmitted data timing from VCM V.11 output Ready for sending V. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 111 . The electrical characteristics of all circuits are according to V.28 if/DCE.11. The connector is furnished with two either UNC 4-40 or M3 locking screws. V.24/V. .4 Installation 4.24 Circuit Number --102 103 104 105 106 107 109 108 113 114 115 140 input output input output output output input input output output input Input/Output Signal Cable shield Signal ground Transmitted data Received data Request to send Ready for sending Data set ready Signal detector Data terminal ready Transmitted data timing from DTE Transmitted data timing from VCM Received data timing from VCM Remote loop-back Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 112 22030_12 © 2013 Tellabs.28 interface is provided with a 25-pin female D-connector according to ISO 2110 Standard.28. V24/V.6…64 kbit/s.24/V. 64 D-Type 25-Pin Female Connector The V.3 V24-DCE-M. 63 Front Panel of V24-DCE-M Module Fig. 0.28 Connector Pin Assignment Pin Number 1 7 2 3 4 5 6 8 20 24 15 17 21 CCITT V. 2 pcs Fig. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 113 . 2 pcs Fig. 66 D-Type 25-Pin Female Connector V24/V.24 Circuit Number 141 142 ----------- Input/Output input output output output Signal Local loop-back Test indicator +10 V output via 321R -10 V output via 321R Not connected Not connected Not connected 4. 0.28 if/DTE.11.28 Connector Pin Assignment Pin Number 1 7 2 3 4 5 6 8 CCITT V.4 V24-DTE-M. 19 22.24/V. V.24 Circuit Number --102 103 104 105 106 107 109 output input output input input input Input/ Output Signal Cable shield Signal ground Transmitted data Received data Request to send Ready for sending Data set ready Signal detector 22030_12 © 2013 Tellabs.4 Installation Pin Number 18 25 9 10 11-14 16. 23 CCITT V.6…64 kbit/s. 65 Front Panel of V24-DTE-M Module Fig. 5 X21-M. .11. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 114 22030_12 © 2013 Tellabs. X.21 interface is electrically and mechanically compatible with CCITT Recommendation X.4 Installation Pin Number 20 24 15 17 21 18 25 9 10 11-14 16.21 interface is provided with a 15-pin female D-connector according to ISO 4903 Standard.11).27 (V.24 Circuit Number 108 113 114 115 140 141 142 ----------- Input/ Output output output input input output output input output output Signal Data terminal ready Transmitted data timing from VCM Transmitted data timing from DCE Received data timing from DCE Remote loop-back Local loop-back Test indicator +10 V output via 321R -10 V output via 321R Not connected Not connected Not connected 4.11. 23 CCITT V. The electrical characteristics of all circuits are according to V. 19 22.21 1. circuits C and I correspond to V. The X.24 circuits 105 and 109.21 for point-to-point applications. 2 pcs Fig. 68 D-Type 15-Pin Female Connector The X. Functionally. The connector is furnished with two either UNC 4-40 or M3 locking screws. The signal levels for all circuits are X.2…n x 64 kbit/s Interface. 67 Front Panel of X21-M Module Fig. 6 G703-64-M. 70 D-Type 15-Pin Female Connector 22030_12 © 2013 Tellabs.21 Circuit Number --T(A) T(B) C(A) C(B) R(A) R(B) I(A) I(B) S(A) S(B) X/B(A) X/B(B) G ---output/input DTE transmit signal element timing/ Byte timing Signal ground or common return Not connected output/input Signal element timing output/output Indication output/output Receive input/input Control input/input Mode DCE/DTE Signal Cable shield Transmit 4. 2 pcs Fig. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 115 . G.4 Installation X.11. 69 Front Panel of G703-64-M Module Fig.703 64 kbit/s Co/Contradirectional Interface.21 Connector Pin Assignment Pin Number 1 2 9 3 10 4 11 5 12 6 13 7 14 8 15 CCITT X. The connector is furnished with two either UNC 4-40 or M3 locking screws. 0.24/V.6…64 kbit/s. V. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 116 22030_12 © 2013 Tellabs. n x 64 kbit/s Fig.11. 72 D-Type 25-Pin Female Connector The V. 0. 71 Front Panel of V35/V24-M Module Fig.3 V24-DCE-M. The V.35-IEC if.4 Installation G.28 if/DCE. 2 pcs).7 V35/V24-M.28 interface is provided with a 25-pin female D-connector according to ISO 2110 Standard.55 V (+20%) to 100 Ω load.35-IEC interface is equipped with a 25-pin female D-connector according to ISO 2110 Standard. The data and timing signals are symmetrical with a level of 0.24/V. The electrical characteristics of the control circuits are according to V. V. The connector is furnished with two either UNC 4-40 or M3 locking screws. V. The electrical characteristics of all circuits are according to V.28 if/DCE.703 Connector Pin Assignment Pin Number 1 2 3 4 5 6 7 8 9-15 Input/ Output Signal output output input input output output output output Receive data (A) Receive data (B) Transmit data (A) Transmit data (B) Receive data timing (A) Receive data timing (B) Transmit data timing (A) Transmit data timing (B) Ground 4. The pin assignment is the same as with the V24-DCE-M module (See 4.28. .11.28.6…64 kbit/s.24/V. 4 Installation V.11.28 V. 0.35 input output output output input input Request to send Ready for sending Data set ready Signal detector Data terminal ready Transmitted data timing from DTE V.28 V. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 117 .35 output Transmitted data timing from VCM V.28 V.35 input Input/ Output Signal Signal Level Cable shield Signal ground Transmitted data V.28 V. TIA/EIA 612.35 IEC Connector Pin Assignment Pin Number 1 7 2 14 3 16 4 5 6 8 20 24 11 15 12 17 9 21 18 25 CCITT V.28 output Received data timing from VCM V.6…8448 kbit/s Fig.35 Circuit Number --102 103A 103B 104A 104B 105 106 107 109 108 113A 113B 114A 114B 115A 115B 140 141 142 input input output Remote loop-back Local loop-back Test indicator V.35 4.28 V.28 V.35 output Received data V.28 V.8 HSSI-M. 73 Front Panel of HSSI-M Module 22030_12 © 2013 Tellabs. 74 II-Type 50-Position SCSI Connector HSSI-M Pin Assignment Pin Number 1 26 2 27 3 28 4 29 5 30 6 31 7 32 8 33 TIA/EIA-613 Circuit Number 102 102 115A 115B 107A 107B 104A 104B LCA30 LCB 30 114A 114B 102 102 108/2A 108/2B Input/ Output Output Output Output Output Output Output Output Output Output Output Input Input Signal Signal Level Common Common Receiver signal element timing Receiver signal element timing DCE ready DCE ready Received data Received data Loopback request from DCE Loopback request from DCE Transmitter signal element timing Transmitter signal element timing Common Common DTE ready DTE ready TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 30LC is not specified in TIA/EIA-613. the pair is reserved for future use interchange circuits from DCE. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 118 22030_12 © 2013 Tellabs. .4 Installation Fig. 4 Installation Pin Number 9 34 10 35 11 36 12 37 13 38 19 44 24 49 25 50 TIA/EIA-613 Circuit Number 113A 113B 143A 143B 103A 103B 144A 144B 102 102 102 102 142A 142B 102 102 Input/ Output Input Input Input Input Input Input Input Input Output Output - Signal Signal Level Transmitter signal element timing Transmitter signal element timing Loopback A Loopback A Transmitted data Transmitted data Loopback B Loopback B Common Common Common Common Test mode Test mode Common Common TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 TIA/EIA-612 - 4. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 119 .11. 10Base-T. 76 RJ-45 Connector 22030_12 © 2013 Tellabs. 75 Front Panel of Mini LAN Module Fig. 64…2048 kbit/s Fig.9 Mini LAN Module. Y is the version of the software (SMZ4NN can be either SMZ 414 or SMZ 430.4 Installation The 10Base-T interface is implemented with an RJ-45 connector (twisted pair). If only the EPROMs are changed without performing a download. The following instructions describe how to update the software of Tellabs 8120 mini node M by downloading a compatible binary file through the management interface and how to replace the EPROMs on Tellabs 8120 mini node M. Flash memories are of an electrically programmable and erasable memory type.1 Downloading Tellabs 8120 Mini Node M Software The downloadable software for Tellabs 8120 mini node M is normally delivered as a binary SMZ4NN_X.Y are compatible if U = X. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 120 .5. The compatibility between the target unit software and the downloadable file is defined by the following two rules: • The product codes must be the same (SMZ4NN).7. Updating software means in most cases only the downloading of the application software. 76 and the pin assignment in the table below. The connector contact identification for RJ-45 is presented in Fig. The application software which is always needed for Tellabs 8120 mini node M to function is downloaded to the flash memories soldered on the main board of the equipment. The software can be downloaded on a running device. The EPROMs inside Tellabs 8120 mini node M only include the operating system of the controller. After the download process the piece of equipment makes a reset which causes a short (30…60 seconds) interruption to the data transmission going through the equipment. Step 1 Check that you have the correct downloadable software available. Pin 1 2 3 6 4. 22030_12 © 2013 Tellabs. the equipment will not operate. depending on the type of Tellabs 8120 mini node).V and X. The downloading process does not change any settings or the cross-connection of the equipment. U. 4. The downloadable software must be compatible with the EPROM set of the target unit.12 Software Update If the controller software needs to be updated.Y file on a micro floppy disk. a service computer or Tellabs 8000 manager is needed.8 Signal Tx+ (TD+) Tx.(TD-) Rx+ (RD+) Rx. The following instructions should be followed when downloading the Tellabs 8120 mini node M software. where X. 4.12.(RD-) Not connected The cabling of the LAN interface must remain inside the building. • Two versions. 4 Installation Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Select the correct target if you are using Tellabs 8000 manager. Check the compatibility of the software versions. Open the Downloading window. Select the correct binary file SMZ4NN_X.Y from your directory. • For example: SMZ414_4.6 Activate downloading. Wait for the operation to end. The downloading takes some minutes, including erasing time, data transfer and programming time, and checking and restarting time. After downloading, check the software version. 4.12.2 Replacing EPROMs There are two EPROMs for the software. The EPROMs are labeled with the identification stickers which contain the following information: product code (SMZ4NN), version number and EVEN/ODD to indicate the positions of EPROMs. The download must be disabled before installing the EPROMs with new versions. Tellabs 8120 mini node M must be disconnected from the mains supply before removing the cover as high voltages are present inside the Tellabs 8120 mini node M case. The following instructions should be followed when installing or replacing the EPROMs. Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Check that the unit is executing the PROM application. Remove the metallic cover of Tellabs 8120 mini node M. Remove the old EPROMs from their sockets. Put the new EPROMs (SMZ4NN rx.y ODD and EVEN) into the sockets. Check the correct places of the EPROMs (see the figure below). Check the direction of the EPROMs. The Pin #1 end is identified by a slot at the end of the component package. Replace the metallic cover of Tellabs 8120 mini node M. Download the new software version. 22030_12 © 2013 Tellabs. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 121 4 Installation Fig. 77 Location for EPROMs Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 122 22030_12 © 2013 Tellabs. 5 Faults and Actions 5 Faults and Actions 5.1 Terminology The following acronyms will be used in the tables below: Maintenance Status PMA DMA MEI Prompt maintenance alarm Deferred maintenance alarm Maintenance event information Service Status S Service alarm LED Indications R Y RB Red alarm LED Yellow alarm LED Red alarm LED blink Consequent Actions TxAIS RxAIS TxTS-AIS AIS FrFEA MFrFEA AIS insertion to Tx signal AIS insertion to Rx signal AIS insertion in time slots of Tx signal AIS insertion to whole signal Frame level far-end alarm (TS0/B3 in 2 Mbit/s frame, TS66/B7 in 8 Mbit/s frame) Multiframe level far end alarm (FR0/TS sig/B6) Also MFrFEA is transmitted if FrFEA is transmitted. 22030_12 © 2013 Tellabs. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 123 FLASH faults A problem has been found when saving parameters or programs to the non-volatile memory. S R - R - Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 124 22030_12 © 2013 Tellabs.2.2 5. Rx RAM error There is a difference between the written and read data in the Rx data buffer RAM of the framed interface. Missing application program There is no application program on the flash memory.-12 V) The voltage generated by the main supply unit is below the threshold limit. S PMA. S LED R Note Fault message (with delta event) appears when the unit starts to operate. Checksum err in downloaded SW The downloaded software has been corrupted.Download the latest version of the SMZ program.+12 V. Missing settings One of the setting structures has been corrupted on the non-volatile memory. EPROM fault The calculated check sum does not match with the stored one. Tx RAM error There is a difference between the written and read data in the Tx data buffer RAM of the framed interface. CPU memory faults RAM fault A background process has found a RAM location where the read value does not match with the written test pattern. Status PMA. S R PMA R - PMA PMA R R - PMA. S R - R - PMA.5 Faults and Actions 5. Rx signal action depends on the frame level alarm of the corresponding interface. S PMA. - PMA R PMA.1 Common Faults and Actions Common Logic Faults (Block 0) Fault Condition Reset There has been a unit reset (detected always after the power-up of the unit) Power supply (5 V. SW unpredicted This fault condition should never occur (or not yet supported). . Incompatible EPROM/FLASH SW The downloaded software (on the flash) is not compatible with the system software on the EPROMs. The record has been deleted. X-connect flash lst conflict A corrupted cross-connect record has been found in the non-volatile memory after the unit reset. X-connect RAM fault Problem found when configuring the cross-connect matrix.2 Master Clock Faults (Block 0) Fault Condition Loss of master clock locking The internal clock is used with non-empty fallback list. ASIC latch warning An ASIC setting is corrected by a checking background process. a port descriptor list) has been corrupted.3 Cross-Connect Block Faults (Block 0) Fault Condition Block IA fault Data transfer between the cross-connection and a specified block (interface/port) does not work.5 Faults and Actions 5. Status MEI MEI LED Note PMA R MEI PMA R MEI Y 5.g. PortDescr flash lst conflict A corrupted port descriptor record has been found in the non-volatile memory after the unit reset. Phase locked loop alarm The phase locked loop of the master clock cannot be locked to any clock. S PMA. S PMA. Fallback list warning The lowest choice is used (there is more than one choice in the fallback list). is not acceptable. Loss of external clock The external clock input is enabled but the clock.2. ASIC latch error An ASIC setting cannot be corrected by a checking background process. S MEI LED Y Note R R PMA.S R MEI MEI 22030_12 © 2013 Tellabs. connected to input. Status PMA. External clock warning The external clock is included in the fallback list but the external clock input is not enabled. The record has been deleted.2. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 125 . Clock far end alarm choice N The state of the fallback list choice N indicates the clock far end alarm. Flash list check sum error One of the flash lists (e. The record has been deleted. The cross-connect block should activate the IA on the bus if the interface is locked. X-conn warning A delta fault indicating a problem when switching the time controlled cross-connection on/off.5 Faults and Actions Fault Condition Swp trk flash lst conflict A corrupted swap trunk record has been found in the non-volatile memory after the unit reset. S MEI. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 126 22030_12 © 2013 Tellabs.2. S R Y TxTS-AIS TxAIS31 MEI. The record has been deleted. Additional information can be read in the error log of the time control process. .4 Faults of Framed IF Tx Signal (Block 1. S R TxTS-AIS Status PMA. word and RAI from the X-bus and TS0B2 changes between 0 and 1 are missing. BTE Tx line test The fault will be activated if a BTE module Tx test pattern generator is activated (used in V. fault (block 0) No cross-connection bus sync detected. 2) Fault Condition Tx Clock fault (PLL) The fault will be activated if the interface module transmitting clock phase locking to X-bus clock fails. Bus faults IA activity missing The fault will be activated if the unit cannot find its locked interface address on the cross-connection bus. S LED R Tx signal TxAIS PMA. Pass trk flash lst conflict A corrupted passivate trunk record has been found in the non-volatile memory after the unit reset. PMA.54 remote loop). Bus sync. S Y Test pattern 31Only when FAS is transferred through the network. Time contr. AIS from X-bus The fault will be activated if the frame sync. Status MEI LED Note MEI PMA 5. 3 No response to NNM message The control channel of the interface is used and the neighbour node supervision option of the interface is ON and no NNM (Neighbour Node Monitoring) message has been received from the interface in eight seconds.1 Own NNM messages received The control channel of the interface is used and the neighbour supervision option of the interface is ON and the received NNM message contains the same identification data as the NNM message sent to the interface.4 Rx signal is AIS The Rx signal is detected to be AIS.5 Loss of frame alignment 1.7 Wrong input signal 1. 1.5. S PMA.5 Faults of Framed IF Rx Signal (Block 1.2 CRC missing This fault indicates that the remote end does not use the CRC. The 10E-3 alarm status depends on fault consequences (AIS insertion). 1. 1.7. 1.3 Frame alignment lost by CRC See CCITT G.2. 1. S PMA. S R RxAIS FrFEA PMA. S Y RxAIS FrFEA R RxAIS FrFEA PMA. S R RxAIS PMA.706 Loss of frame alignment.7. S DMA R R RxAIS RxAIS FrFEA FrFEA Status PMA.1 Interface module missing No interface module is present but one is defined in the settings.5.5.3 Rx signal missing The signal level is below a specific level (the level depends on the used interface module and the selected bit rate). 1. 1. 1.8 NTU problems PMA.1 Frame alignment lost See CCITT G. 1. S R RxAIS - PMA. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 127 . S PMA. 1.5 Faults and Actions 5.2 Wrong IDs in NNM messages The control channel of the interface is used and the neighbour supervision option of the interface is ON and the received NNM message contains unexpected neighbour identification data. S LED R Rx signal RxAIS Tx signal - R RxAIS Cut off R RxAIS FrFEA MEI. 2) Signal and Frame Faults 1.2 Wrong interface module There is a conflict between the installed module and the settings. S R RxAIS - 22030_12 © 2013 Tellabs.7.706 Frame alignment recovery (2048 mode ≥915 CRC block errors detected). 1.6 BER 10 -3 The bit error rate is calculated from faulty frame alignment words or from code errors. 1. or the BTE module is used and the V.1.1. S Y - - 3 Multiframe level faults 3.5 Faults and Actions Signal and Frame Faults 1.5…4. S R RxAIS/SigTS MFrFEA Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 128 22030_12 © 2013 Tellabs. All other bits are looped back to the interface.1 Remote controlled line loop (2. S Y RxAIS MEI. 2.1.5 Hz and the current value difference is more than 1.1 Interface back to equipment An interface loop is created in the interface module. 1. 1. It loops the transmitted data and the clock signal back to the interface receiver. 2. When it is used.2.1 NTU power off / local loop The fault will be activated if the used module is BTE384 and the wetting current is ON and the received current value differs in frequency of 1.3 NTU short circuit The fault will be activated if the used module is BTE384 and the wetting current is ON and the received current value is higher than 6. S R - - MEI. but the loop is made before the interface module on the framing block in the base card.4) This alarm will be activated if the HDLC channel is in use and MUX/DEMUX back to line loop has been made to the neighbour unit. or the BTE module is used and the remote end has made loop by using the V. 1. . 2 Loops 2.2 MUX/DEMUX back to eq.5 mA. S Y - TxAIS MEI.54 loop sequence. 2. 2.1.2 mA.2 NTU line break The fault will be activated if the used module is BTE384 and the wetting current is ON and the received current value is lower than 1.9 ASIC register error The fault will be activated if difference of the write/read data of ASIC has been found. S Y RxAIS - MEI. the HDLC channel works with this line loop.5 mA.8.8.8. S Y - TxAIS MEI.1 Multiframe alignment lost (group N) The multiframe alignment in signalling time slot is lost.2 Remote loops 2.4 Line loop made by neighbour This alarm will be activated if the HDLC channel is in use and MUX/DEMUX back to line loop has been made from the remote end.3 MUX/DEMUX back to line Rx data is looped back to the interface transmitter. PMA.54 loop has been made to the remote end.1 Local loops 2. Status MEI LED Y Rx signal RxAIS Tx signal - MEI Y - - MEI Y - - PMA. As in the Interface back to equipment loop above. 1 Frame far-end alarm (FrFEA) The alarm state of the frame far end bit is received. The alarm status depends on fault consequences (AIS insertion into the signalling time slot). The fault will be activated if the phase drifting limit has been exceeded in three measurements out of four. S Y RxAIS/SigTS 5 Degraded Signal 5.1 Error rate 10 -3 See CCITT G. 5.4 Buffer slips/1 hour The fault will be activated if one or more buffer slip(s) has been observed during the last hour. MEI.736. The bit error rate is calculated from faulty frame alignment words or from code errors. Multiframe faults of the 8 Mbit/s signal are detected separately in each of the four signalling time slots (groups). MEI.2 Error rate 10 -6 The BER10E-6 error rate is calculated from CRC block errors when the bit rate is ≥1024 kbit/s.2 AIS in signalling (group N) The signal in the signalling time slot is detected to be AIS. S Y RxAIS/SigTS MFrFEA 4 Far-End Alarms 4. 5.3 Frequency difference The measurement period is 15 s and the phase drifting limit is 5 µs.2 Multiframe far-end alarm (MFrFEA) The alarm state of the multiframe far end bit is received. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 129 . The counting time is 10 s and the limit for the fault condition depends on the used bit rate (2048 limit is 10). S Y RxAIS/SigTS RxAIS operation can be turned off RxAIS operation can be turned off MEI. DMA R - DMA R - - DMA R - - MEI RB - - 22030_12 © 2013 Tellabs. 4. 5.5 Faults and Actions 3. The alarm status depends on fault consequences (AIS insertion into the signalling time slot). The 10E-3 alarm status depends on fault consequences (AIS insertion). 2. or if the cross-connection system has no port descriptor although the interface is locked. The fault will be deactivated when 10 consecutive non-SES seconds have been found. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 130 22030_12 © 2013 Tellabs. .821 supervision is used and at least one performance limit has been exceeded in a 15-minute period. Master clock RAI overlap with X-bus The fault will be activated if the MCLK/RAI bit is also used by the cross-connection bus. Loss of protected signal In 1+1 protection mode both interfaces IF1 and IF2 have faults which in unprotected mode have S status.2. Status DMA LED R Rx signal Tx signal - DMA R - - DMA R - - PMA.6 1+1 Protection Switch Fault Messages (Block 0) Fault Condition Protection switch forced When the unit is in 1+1 protected mode and the protection switch has been forced to select a signal from IF1 or IF2. 32Signal actions depend on actions of the protected interfaces. 2) Fault Condition Port locking conflict The fault will be activated if the cross-connection system has the port descriptor but the interface is unlocked. S R -32 -32 5.821 supervision is used and the state of the signal becomes unavailable (10 consecutive SES seconds). G821 limit event This fault will be activated as a delta fault if G. S - - - DMA - - - MEI Y - - 5. S) in 1+1 Mode of Framed Interfaces In principle.5 Faults and Actions 5. Status MEI LED R Rx signal Tx signal - PMA. MEI.7 Miscellaneous Faults of Framed Interfaces (Block 1. HDLC overlap with X-bus The fault will be activated if the HDLC control channel bit(s) are also used by the cross-connection bus. G821 unavailable state The fault will be activated if the G.2. Faults masked/Test The fault will be activated when the interface fault mask setting is ON (all interface faults will be cleared). both interfaces generate their own alarms (alarm messages with fault status). DMA.8 Fault and Service Status (PMA. PMA and S statuses are processed in this mode. Use lock/unlock. and with the PMA status there is an additional fault condition. RxAIS and RxAIS to SigTS are always generated when FrFEA or MFrFEA are sent. In normal or prefer operating modes this special condition is created when both interfaces have a fault of category 3 or worse. State 1 for alarm. State 1 for alarm. A signal in the signalling time slots containing one or no zeros in a multiframe period is recognized as an AIS signal. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 131 . In forced operating mode this condition occurs if the forced interface has a fault of categories 3 through 1. The state of signalling time slot frame 0 B6 alarm bit will be switched if the opposite state is received in three consecutive frames. A far-end alarm indicates that the Rx signal is out of service (S status). The fault will be deactivated when the frame alignment is found and the first four bits of the signalling time slot are found to be zeros (0) and when the prior signalling time slot has had at least one bit in state 1. a signal containing 12 or more zeros in a 2-frame period is recognized not to be an AIS signal. During a short period.9 Fault Conditions of Framed Interfaces Multiframe Alignment Lost The fault will be activated if two consecutive faulty multiframe alignment words have been received or if all signalling time slots in one multiframe contain only zeros (0). FrFEA: Rx frame out of service MFrFEA: Rx multiframe out of service Tx far-end alarms (FrFEA. AIS generating depends on the fault status of the selected interface. 2048 kbit/s and n x 64 kbit/s count time is 4 seconds: Count to activate alarm: 94 Count to inactivate alarm: 17 8448 kbit/s count time is 2 seconds: Count to activate alarm: 199 Count to inactivate alarm: 48 Count time is one second: Frame Far-End Alarm (FrFEA) Multiframe Far-End Alarm (MFrFEA) AIS in Frame 2048 kbit/s and n x 64 kbit/s AIS in Frame 8448 kbit/s AIS in Multiframe Error Rate 10E-3 Limits from Frame Alignment Word Error Rate 10E-3 Limits from Code Errors 22030_12 © 2013 Tellabs. After AIS is detected. S Status Processing Far-End Alarms in 1+1 Mode RxAIS Processing 5. a signal containing three or more zeros in a 2-frame period is recognized not to be an AIS signal. After AIS is detected. A signal containing less than eight zeros in a 2-frame period is recognized as an AIS signal. when the change-over switch is in a transition phase. In protection mode an S status is generated only in the Loss of protected signal fault condition. MFrFEA) of both interfaces are generated assuming a fault status of the active interface. Loss of protected signal. The inactive interface is not able to generate a fault with the PMA status. The state of TS0B3 frame far-end alarm bit will be switched if the opposite state is received in three consecutive frames.5 Faults and Actions PMA Status Processing In protection mode the normal PMA status is changed to the DMA status. In forced operating mode only the active forced interface can cause far-end alarms to be sent. the far-end may generate an alarm even if there is no fault in the better interface. A signal containing two or less zeros in a 2-frame period is recognized as an AIS signal.2. In 2M mode the fault will be deactivated if a CRC multiframe alignment has been found.3. . Power off in input Incoming data signal (103) out of the CCITT specs. Wrong interface module There is a conflict between the installed module and the settings. or if in 8M mode more than six CRC alignment losses due to excessive block errors have been found in a period of 3 seconds.PMA. S LED R UI2 C1 OFF/- R - OFF/- Y R OFF AIS OFF Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 132 22030_12 © 2013 Tellabs. 5. S MEI. Status PMA.5 Faults and Actions Speed kbit/s 8448 2048 1088 CRC Spurious Frame Alignment Limits Rate kbit/s 256 320 384 448 512 576 640 704 768 1088 2048 8448 CRC Missing Activate 8296 1973 1033 Inactivate 893 229 126 Values from 1000 counted to start a new frame search 613 637 660 681 700 719 736 753 768 832 915 826 The fault will be activated if in 2M mode a framing has been found and the CRC multiframe alignment has been lost 100…200 ms.3 5.1 Faults and Actions of Unframed Interfaces General IF Faults of Unframed Interfaces Fault Condition IF module missing No interface module is present but there is one defined in the settings. in 8M mode if no more than one frame alignment lost due to excessive CRC block errors in a three-second period has been found. ASIC register err HW error found in the ASIC. S PMA. output signal (UI2) buffer slip (n x 64kbit/s).30 buffer slip. Rx buffer alignment V. X30 or MartisDXX framing in use V.S R - AIS DMA R AIS - DMA R - AIS V.110. DMA R AIS PMA.110 or X. X. Loss of frame sync Loss of frame sync state in the case of a V. AMI or G. S R AIS Status LED UI2 C1 Note MEI. - Y - AIS Used when 105 should be continuously on.703 module. S PMA. Tx buffer alignment V.110 or X.2 IF Signal Faults of Unframed Interfaces Fault Condition Input signal faults (UI1) Interface signal missing No carrier state of the baseband module.110. X30 or MartisDXX framing in use Used at bit rates ≤2.110 or X.30 buffer slip. Loss of multiframe sync Loss of multiframe sync state in the case of a V.4 kbit/s.703 codir/contra). Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 133 .110 or X. V.110. X30 or MartisDXX framing in use Status LED UI2 C1 Note R AIS RAI R AIS RAI Y - - 22030_12 © 2013 Tellabs. Code errors from input Code erros (HDB3.5 Faults and Actions 5. S MEI.30. 105 off in input 105 signal off in input and 105 supervision selected in parameters.30.110.30 or MartisDXX framing in use.3. DMA R AIS - 5. No input clock (NRZ). Timing errors Rx buffer slips Buffer slip in Tellabs 8100 bus interface.110 or X.3. Alarm from far end Alarm bit set in V. MEI. Faulty input signal in the case of a G. S PMA. S Y AIS V.3 Net Side Signal Faults of Unframed Interfaces Fault Condition Input signal from net side (C2) AIS detected from network AIS from the cross-connection bus. PMA. Tx buffer slips Buffer slip in Tellabs 8100 bus interface. input signal (UI1) buffer slip (n x 64kbit/s).30 frame. 30 or MartisDXX framing in use. Status LED UI2 C1 Note DMA - - - Available when end-to-end CRC monitoring is activated. V. DMA R - - FAS-errors Frame sync word errors detected in case of V. S MEI. Status MEI. Available when end-to-end CRC monitoring is activated.54 loop activated (by the interface signal or from the far-end).3. V. Available when end-to-end CRC monitoring is activated.821 supervision is used and at least one performance limit has been exceeded in a 15-minute period. .110. DMA R - - CRC errors from near end CRC errors detected at the near-end.5 Performance Conditions of Unframed Interfaces Fault Condition Performance conditions G821 unavailable state The fault will be activated if the G. S MEI. G821 limit event This fault will be activated as a delta fault if the G.821 supervision is used and the state of the signal becomes unavailable (10 consecutive SES seconds). S LED Y Y Y UI2 AIS C1 AIS - 5.54 loop active V. Local loop or test active Local loop or test activated (by the manager). PMA Y - - Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 134 22030_12 © 2013 Tellabs.30.110 or X.S Available when end-to-end CRC monitoring is activated. CRC errors from far end CRC errors detected at the far-end. PMA.5 Faults and Actions 5.4 Test Loop Activation of Unframed Interfaces Fault Condition Interface loop active Interface loop activated (by the manager). The fault will be deactivated when 10 consecutive non-SES seconds have been found.3. X. 5 Faults and Actions 5.3.6 Common Faults of Unframed Interfaces Fault Condition RL state program error Remote loop state program not stored (HW error). Bus sync. fault (block 0) No cross-connection bus sync detected. IA activity missing The fault will be activated if the unit cannot find its locked interface address on the cross-connection bus. The cross-connect block should activate the IA on the bus if the interface is locked. Faults masked/Test The fault will be activated when interface fault mask setting is ON (all interface faults will be cleared). Status PMA, S PMA, S PMA, S LED R UI2 C1 Note R R AIS AIS AIS AIS MEI, - Y - - 5.3.7 Reference Points of Unframed Interfaces The channel board in Tellabs 8120 mini M holds four identical interface blocks numbered 3 and 6. The common parts are named block 0. The signals and directions are identified as follows. Signals and Directions of Fault Conditions Reference point UI1 UI2 C1 C2 Signal description Input signal at the receive part of the user interface Output signal at the transmit part of the user interface XB output signal towards the X-bus interface XB input signal from the X-bus interface, net side signal Fig. 78 Naming of Signal Reference Points 22030_12 © 2013 Tellabs. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 135 6 Technical Specifications of Tellabs 8120 Mini Node M 6 Technical Specifications of Tellabs 8120 Mini Node M All CCITT references concern the Blue Book, 1988. When applicable, the references to former CCITT Recommendations have been amended to ITU-T references. These references include the date of the valid ITU-T Recommendation in case these are revised in the future. If a CCITT Recommendation has not been updated as ITU-T by the International Telecommunication Union, CCITT is used in this document. 6.1 Relevant Recommendations The ITU-T/CCITT Recommendations concerning Tellabs 8100 trunk interfaces and user access ports are shown below. Rec. ITU-T Date(CCITT 1988) April 1991 CCITT CCITT CCITT March 1993 CCITT CCITT March 1993 Main Characteristics of Equipment and Trunk Interfaces G.703 G.704 G.706 G.732 G.736 G.744 G.821 G.823 Physical/electrical characteristics of hierachical digital interfaces Synchronous frame structure used at primary and secondary hierachical levels Frame alignment and CRC procedures for G.704 frames Characteristics of primary PCM multiplexing equipment operating at 2048 kbit/s Characteristics of a synchronous digital multiplex equipment operating at 2048 kbit/s Second order PCM multiplex equipment operating at 8448 kbit/s Error performance of an international digital connection The control of jitter and wander on the 2048 kbit/s hierarchy Standard Transmission Network Interfaces (2 Mbit/s and 8 Mbit/s) 2048 kbit/s framed interface 8448 kbit/s framed interface G.704, G.706, G.732, G.736, G.821, G.823 G.704, G.744, G.821, G.823 User Access Points For Unframed Data Interfaces33 V.11 (ITU-T 03/93) V.13 (ITU-T 03/93) V.14 Electrical characteristics for balanced double-current interface circuits Simulated carrier control Transmission of start-stop characters over synchronous bearer channels 33 All references to CCITT Recommendations, except those listed as ITU-T. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 136 22030_12 © 2013 Tellabs. 6 Technical Specifications of Tellabs 8120 Mini Node M User Access Points For Unframed Data Interfaces33 V.24 V.28 V.29 V.35 (CCITT Red Book) V.36 V.54 V.110 (ITU-T 09/92) X.21 (ITU-T 09/92) X.27 X.30 X.54 Interface circuits between DCE and DTE Electrical characteristics for unbalanced double-current interchange circuits 9600 bits per second modem standardised for use on point-to-point 4-wire leased telephone-type circuits Data transmission at 48 kbit/s using group band modem Modems for synchronous data transmission using group band modems Loop test devices for modems ISDN rate adaption for V-series interfaces Synchronous data network interface between DCE and DTE Same as V.11 ISDN rate adaption for X.21 interfaces Allocation of channels on international multiplex links at 64 kbit/s. User Access Points for Voice Frequency Interfaces G.711 (CCITT) G.712 (CCITT) G.713 (CCITT) G.714 G.715 G.721 (CCITT 1986/88) G.961 (ITU-T 03/93) 64 kbit/s PCM encoding 4-wire voice frequency interface 2-wire voice frequency interface Separate performance characteristics for the encoding and decoding sides of PCM channels applicable to 4-wire interfaces Separate performance characteristics for the encoding and decoding sides of PCM channels applicable to 4-wire interfaces 32 kbit/s ADPCM Access digital section for ISDN primary rate at 2048 kbit/s 6.2 Cross-Connect Cross-connection method Frame frequency Capacity: The sum of cross-connected signals Smallest cross-connect unit Signalling cross-connection Delay of cross-connect core Synchronous time slot interleaving 8 kHz 64 Mbit/s 8 kbit/s n x 500 bit/s (channel associated signalling = CAS) n x 64 kbit/s 1 frame = 125 µs CAS bits (500 bit/s) 2 ms Time integrity between time slots in cross-connected signals is maintained. 22030_12 © 2013 Tellabs. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 137 703 /75 Ω 75 Ω. 2 Mbit/s n x 64k.4 6. n=1…32 Electrically G.703/75 Ω Frequency 2048 kHz Locked to node master clock Electrically G.1 G. SMB connector G.3 Timing Master clock frequency Master clock functional modes 16 896 kHz ±30 ppm Locking to the interface rx clock (n x 64 kbit/s) Locking to external clock input (n x 64 kHz) Internal mode Clock fallback list (5 levels + internal mode) n x 64 kHz ±50 ppm Frequency n x 64 kHz.704 Framed Interface Frame and Multiframe Buffer Frame Buffer Mode 4 Fr34 8 Fr 8 Fr 64 Fr Bit Rates Rx Delay Frames 1…3 2…6 1…7 1…63 Tx Delay Frames 1 1 1 1 Plesiochronous buffer Main Usage n x 64k.nodes x Mbit/s frequency) 35df=frequency Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 138 22030_12 © 2013 Tellabs. 8 Mbit/s n x 64k.6 Technical Specifications of Tellabs 8120 Mini Node M 6. 2 Mbit/s.736 Locking frequency External clock input External clock output Connector type Jitter transfer function and jitter in the output clock 6. .4. 2 Mbit/s. 2 Mbit/s Non-trunk lines and n x 64 kbit/s trunks Split trunk lines Slip rate when the incoming signal is plesiochronous Buffer Length 4 Fr 8 Fr (split trunk line) 8 Fr 64 Fr Slip Rate n x 64 kbit/s n x 8/df35 2 x n x 8/df 4 x n x 8/df 32 x n x 8/df Slip Rate 2 Mbit/s 256/df 512/df 1024/df 8192/df Slip Rate 8 Mbit/s 1056/df 4224/df - Split trunk line operation (two physical lines combined to one logical trunk): 341 Fr = 125 µs difference (input x Mbit/s signal frequency . 8 Mbit/s n x 64k. c.6.69.1 8448 kbit/s.4.704) F0/TS sig (0000 xyxx) F0/TS sig/B6 G.b. G. 2 Mbit/s • All split components must have the same bit rate • Tolerated delay difference between lines < 50 µs Multiframe buffer modes When Frame Buffer Is 4…8 frames long 64 frames long Jitter and wander tolerance MFr Buffer36 2 MFr 4MFr G.68.6.70 (G.5 Optical Line Interface 2048 kbit/s / 8448 kbit/s (OTE-LED-M Module).821 TS67. Optical line See 6.703 See 6.b / c. Multiplexing method Bits in time slot Time slots in frame Frame alignment time slot Frame alignment procedure Far end alarm CRC error check CRC error indication to the remote end Error performance monitoring Signalling multiframe time slots Multiframe time slot content Multiframe far end alarm Multiframe alignment procedure Frames in multiframe Signalling bits Synchronous time slot interleaving (G.704) 8 132 numbered 0…131 TS0/B1…8 + TS66/B1…6 G.703 Interface (G703-8M-M Module). Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 139 .6 Technical Specifications of Tellabs 8120 Mini Node M • Line bit rates n x 64 kbit/s (3 ≤ n ≤ 32).823 Rx Delay 0…2 MFr 1…3 MFr Tx Delay 1 Fr 1 Fr 6.2 8448 kbit/s Interface (CCITT G.d / 64 kbit/s time slot 2 pcs a.704) Electrical interface G.732 (same as in 2 Mbit/s interface) Separate multiframe alignment for each signalling time slot 16 4 pcs a.d / 32 kbit/s 1 pc a / b / c /d / 16 kbit/s Control channel datalink n x 8 kbit/s (n=1…8) Any time slot except TS0 and TS66 Tellabs 8100 trunk lines preferable TS01/B1…B8 (64 kbit/s) or TS33/B1…B8 361 MFr = 2 ms 22030_12 © 2013 Tellabs.744 TS66/B7 CRC-6 in bits TS99/B1…6 (can be disconnected) TS99/B7 G. TS33 TS66/B8. TS100…TS131 5 time slots TS1…TS4.35.5 Optical Line Interface 2048 kbit/s / 8448 kbit/s (OTE-LED-M Module). 56.1 V.24/V.V.6. TS34…TS65.706 TS0/B3 CRC-4 in CRC multiframe of TS0/B1 (G.1 V.3 2048 kbit/s.36/V.6.2…19. G.36/V. 48.704/706) Electrical interface G.11 See 6.732 16 Signalling bits 4 pcs a.2…19.28.2 kbit/s.6 Technical Specifications of Tellabs 8120 Mini Node M Time Slot Usage in Trunks Cross-connectable time slots with signalling bits (CAS) Cross-connectable time slots without signalling bits Free bits 120 time slots TS5…TS32. TS71…TS98. Multiplexing method Bits in time slot Time slots in frame Frame alignment time slot Frame alignment method Far end alarm CRC error check CRC block error indication to the remote end Error performance monitoring Signalling multiframe time slot Multiframe alignment time slot content Multiframe far end alarm Multiframe alignment method Frames in multiframe Synchronous time slot interleaving 8 32 numbered 0…31 TS0 G.b.35 See 6.c. TS99/B8 6.5. Optical line See 6.36/V.11.V.2 2048 kbit/s. 1. 56.CRC can be disconnected) CRC multiframe E-bit G.5.b / c.2 kbit/s.6.24/V.d / 32 kbit/s 1 pc a / b / c /d / 16 kbit/s Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 140 22030_12 © 2013 Tellabs.4. Line terminal See 6.3 2048 kbit/s Interface (CCITT G.d / 64 kbit/s time slots 2 pcs a.821 TS16 (G.703 Interface (G703-75-M) and 6. 1.4 2048 kbit/s and 1088 kbit/s Line Terminal Interface (LTE-M Module). n x 64 kbit/s.703 See 6.703 Interface (G703-120-M). 48. .35. V.V.28.704/706. V.V.704) F0/TS16 (0000 xyxx) F0/TS16/B6 G. G. n x 64 kbit/s.6.11. d / 64 kbit/s 2 pcs a. Multiplexing method Bits in time slot Time slots in frame Frame alignment time slot Frame alignment method Far end alarm CRC error check CRC block error indication to the remote end Error performance monitoring Signalling multiframe time slot (TS sig. BTE-2048-M. V. TS1…TS15.6.704/706.113.) for V.35 and V. 1088 kbit/s line terminal See 6.) Multiframe alignment time slot content Multiframe far end alarm Multiframe alignment method Frames in multiframe Signalling bits Synchronous time slot interleaving 8 N numbered 0…n-1 TS0 G.4.7 Baseband Line Interfaces 320. BTE-1088-2W-M and BTE-2304-M Modules).704 Type Frame Electrical interface N x 64 kbit/s baseband interface See 6.. BTE-576-M.113.104..6 Baseband Line Interface 64…384 kbit/s (BTE-384-M Module) and 6. BTE-2048-2W-M.4 N x 64 kbit/s Interface with G.35 n x 64 kbit/s (signals 103. BTE-320-M.6.36 n x 64 kbit/s (signals 103.) V.35 electrical specs.36 n=2…32.CRC can be disconnected) CRC multiframe E-bit G. b / c.115. 81 in Appendix 2 in Tellabs ® 8120 Mini Node M Operating Manual (document number 22030_XX).6. TS17…TS31 TS0/B4…8 (see Control Channel Data Link below) n x 8 kbit/s (n=1…8) Any time slot except TS0 frame alignment bits Tellabs 8100 trunk lines preferable TS0/B5…8 (16 kbit/s) 6.732 16 4 pcs a.115.821 Last time slot in frame (TSn-1) except with n≥17 TS signalling=16 F0/TS signalling (0000 xyxx) F0/TS signalling/B6 G. b. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 141 . with n=32 the frame parameters are the same as in Fig.6 Technical Specifications of Tellabs 8120 Mini Node M Time slot usage in trunks: cross-connectable time slots with signalling bits (CAS) free bits Control channel datalink 30 time slots . V. 81 in Appendix 2Fig. BTE-4096-M. c.706 TS0/B3 CRC-4 in CRC multiframe of TS0/B1 (G. V. d / 32 kbit/s 1 pc a / b / c / d / 16 kbit/s 22030_12 © 2013 Tellabs.4224 kbit/s (BTE-1088-M.11 electrical specs.4 2048 kbit/s and 1088 kbit/s Line Terminal Interface (LTE-M Module).104. 11. 19.105/109 .24 . SB. 107. 48. 7. 113.V.36.6. 141 and 142.V.28 for signals 140.24/V.11 for other signals 102.24 Electrical Interface .6 Technical Specifications of Tellabs 8120 Mini Node M Time slot usage in trunk lines: cross-connectable time slots with signalling bits (CAS) free bits Control channel data link n-2 pcs TS0/B4…8 (see Control Channel Data Link below) n x 8 kbit/s (n=1…8) Any time slot except TS0 frame alignment bits Tellabs 8100 trunk lines preferable TS0/B5…8 (16 kbit/s) 6. 103. 105.35 .28 1. V. D-type 25-pin female connector ISO 4902. (loop 3) ISO 2110.24/ V.36/V. 114. D-type 37-pin female connector V.V. 9. n x 64 kbit/s Interface type Data bit rate Framing inside Tellabs 8100 network Interface functions Handshake signal transmission37 .24 V.35.RL.11.24/V.1 Unframed Data Interfaces V.V.4 kbit/s V.36 Interface signals Connector type . V.2.5 6.35 for signals 103.V.V.28 for other signals V. 104.5.106 .110 V.32 V.35 .28 for all signals V.110 frame Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 142 22030_12 © 2013 Tellabs.4.35-IEC . 4.28 48. 106.140/142 SB X SA V.V. 56 kbit/s V.V. D-type 25-pin female connector ISO 2593.….54 V. 109. 115.54 V.54 local loop.13 V. 141.35.2 kbit/s.V.V.110 V.LL. 140.36/V.2…19. 114. .V.2.24 (n=1) V. 113.4.54 remote loop. D-type 34-pin female connector ISO 2110. V. 2. 142 37SA. 38.54 SB X SA V.24 n x 64 kbit/s n=1. X are bits in V.8.35. 56. V. 108. 104.108/107 .24 . (loop 2) . 1.V.28.2. 115.V.2.36 Test loops via data interface . 14. 4.C/I V.6.1 Data Interface Modules 8448 kbit/s. 32 Baseband Line n x 64 kbit/s n=1…66 The G703-64-M interface is designed for indoor use only.5.24 56 kbit/s n x 64 kbit/s n=1.2.2 kbit/s. 38. 56.3 Transparent 2 Mbit/s.24 S1+S3+S4S1. R.110 V. T. 9.30 (V. S4 are bits in V.2. 6.2…48 kbit/s . 32 - Framing inside Tellabs 8100 network Interface functions Control signal transmission .21 1. 48 kbit/s X.6.4.bit rates 56…n x 64 kbit/s Electrical interface Connector type G.5.27(V.37 V/75 Ω unbalanced 59 ns ±10 ns 0…6 dB/4 MHz G. T.…. It is not meant for external connections.6 6. R. D-type 15-pin female connector 6. S3. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 143 .6 Technical Specifications of Tellabs 8120 Mini Node M 6.823 50 Ω. S X.2 X. 2. 19.8.110) V.703 Interface (G703-8M-M Module) Bit rate Coding Nominal impedance Nominal peak voltage Pulse width Attenuation margin Jitter tolerance Connector type 8448 kbit/s ±30 ppm HDB3 75 Ω 2.bit rates 1. G. S.110 frame S3+S4 - Interface signals . C. n x 64 kbit/s Data bit rate 1.703 2 Mbit/s n=32 G. SMB-type connector 22030_12 © 2013 Tellabs. n x 64 kbit/s Interface type Data bit rate. n x 64 kbit/s G. 48.4.11) ISO 4903.703 64 kbit/s n=1 Optical Line n=32 Line Terminal n=17. I G.2…19. 2. G.703 Interface (G703-75-M) Bit rate Coding Nominal impedance Nominal peak voltage Pulse width Attenuation margin Jitter tolerance Connector type 2048 kbit/s ±50 ppm HDB3 75 Ω 2.0 V/120 Ω balanced 244 ns ±25 ns 0…6 dB/1 MHz G.823 D-type 9-pin female connector 6. SMB-type connector 6.75 A2: 0.0 V / 120 Ω symmetrical 244 ns ±25 ns 0…36 dB at 1024 kHz G.6 (18 µs) A1: 0.6 Technical Specifications of Tellabs 8120 Mini Node M 6.2 2048 kbit/s.703 Interface (G703-120-M) Bit rate Coding Nominal impedance Nominal peak voltage Pulse width Attenuation margin Jitter tolerance Connector type 2048 kbit/s ±50 ppm HDB3 120 Ω 3.3 2048 kbit/s.6.823 50 Ω.823 for 2048 kbit/s with the following exceptions: A0: 19.703 D-type 9-pin female connector Gas discharge tubes.6. G.6.823 460 ns ±40 ns 0…36 dB at 544 kHz Mask like G. . diodes Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 144 22030_12 © 2013 Tellabs.4 2048 kbit/s and 1088 kbit/s Line Terminal Interface (LTE-M Module) Bit rate Coding Nominal peak voltage Pulse width Attenuation margin Jitter tolerance 2048 kbit/s ±50 ppm HDB3 3.37 V/75 Ω unbalanced 244 ns ±25 ns 0…6 dB/1 MHz G.10 f4: 50 kHz 1088 kbit/s ±50 ppm HDB3 Input impedance Return loss Connector type Overvoltage protection 120 Ω symmetrical G. 2. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 145 .651) Standard single mode fiber (G.6. 1.5 Optical Line Interface 2048 kbit/s / 8448 kbit/s (OTE-LED-M Module) Bit rate Transmission path Optical transmitter Nominal wave length Optical line code Symbol rate Optical receiver Min. 2001-08) Functional mode multimode single mode multimode single mode LED 2 M LED 2 M LED 8 M LED 8 M Minimum output power -20 dBm -30 dBm -20 dBm -30 dBm Attenuation margin 30 dB 20 dB 22 dB 12 dB Fig.652) Semiconductor LED 1300 nm CMI 4096 kBd (2 Mbit/s) 16896 kBd (8 Mbit/s) PIN diode -50 dBm (2M) -42 dBm (8M) FC type with a receptacle EN 60825-1/A2: 2001 (IEC 60825-1 Ed.6. 79 Class 1 LED Product 6.6 Baseband Line Interface 64…384 kbit/s (BTE-384-M Module) Bit rate Line interface Line code Interface impedance N x 64 kbit/s (n=1…6) 2/4W full-duplex Biphase space 150 Ω symmetrical 22030_12 © 2013 Tellabs.6 Technical Specifications of Tellabs 8120 Mini Node M 6. sensitivity (BER Optical connector LED safety 10 -9) 2048 kbit/s ±50 ppm 8448 kbit/s ±30 ppm Standard multimode fiber (G. . BTE-4096-M) 2 W full-duplex (BTE-320-M. 1 stop bit ISO 2110. 16. 109 Layers 2…7 proprietary Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 146 22030_12 © 2013 Tellabs. 66 (BTE-4096) 4 W full-duplex (BTE-1088-M. n=5 (BTE-320-M) n=5. BTE-576-M. 32. varies according to bit rate and transmit level Adaptive D type 9-pin female connector Line interface Line code Interface impedance Output level/135 Ω Return loss Maximum input level/135 Ω Minimum input level/135 Ω Equalizer Connector type 6. BTE-4096-M. BTE-1088-2W-M.7 Baseband Line Interfaces 320. 17. 34. 107. BTE-2048-2W-M) n=16. BTE-2304-M) 2B1Q 135 Ω symmetrical +13. 64. BTE-1088-2W-M and BTE-2304-M Modules) Bit rate n x 64 kbit/s.7 Service Computer (SC) Interface Interface type Electrical interface Data bit rate Character format Connector type Interface signals Protocol V. BTE-2048-2W-M. BTE-2048-M. 32. BTE-2048-M. 17.5 /+6 dBm/0 dBm > 12 dB + 15 dBm -15…-30 dBm. 9 (BTE-576-M) n=5. 9. no parity. 17 (BTE-1088-2W-M) n=5. 108.24 V. . 36 (BTE-2304-M) n=16. 17 (BTE-1088) n=16. 33. 105.6. 103. 17.28 9.6 Technical Specifications of Tellabs 8120 Mini Node M Output level/150 Ω Return loss Maximum input level/150 Ω Minimum input level/150 Ω Equalizer Connector type 0/-6 dBm >12 dB 0 dBm -33 . BTE-576-M) 2 W/4W full-duplex (BTE-2048-2W-M. 33 (BTE-2048.4224 kbit/s (BTE-1088-M. 104.-38 dBm (varies according to bit rate) Adaptive D-type 9-pin female connector 6.. 106. 32.6 kbit/s asynchronous 8 bit. D-type 9-pin female connector 102. BTE-320-M. 9. 33. 0 W 2.240 V AC ±10% 47…63 Hz 8990NFS40 DC Power Supply 24 V Input voltage Type number 19…36 V DC.8.2 W 3.5 W 1.8 Power Supply AC Power Supply Input voltage Type number 100. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 147 .3 W 2.0 W 1..2 W 3. positive pole earthed PDU 423 Power Consumption Dependent on furnishing.6 Technical Specifications of Tellabs 8120 Mini Node M 6.703 8 Mbit/s 75-ohm interface module Power Consumption (max) 2.1 Power Consumptions of Tellabs 8120 Mini Node M Units and Modules Unit or Module BTE-64-M39 BTE-320-M39 BTE-384-M39 BTE-576-M39 BTE-1088-M39 BTE-1088-2W-M39 BTE-2048-M39 BTE-2048-2W-M39 BTE-2304-M39 BTE-4096-M39 G703-64-M39 G703-75-M G703-120-M G703-8M-M39 Description Baseband interface module T-SDSL interface module Baseband interface module T-SDSL interface module Baseband interface module T-SDSL interface module Baseband interface module T-SDSL interface module T-SDSL interface module Baseband interface module G. max < 40 W 6.2 W 2.5 W 2.3 W 2. interface module has been discontinued.2 W 3.5 W 1. 22030_12 © 2013 Tellabs.5 W 4.703 2 Mbit/s 75-ohm interface module G. negative pole earthed PDU 42238 DC Power Supply 48 V Input voltage Type number 40…60 V DC.0 W 38The 39The power supply module has been discontinued.703 64 kbit/s interface module G.0 W 1..703 2 Mbit/s 120-ohm interface module G. 1 Climatic/Mechanical Compatibility Tellabs 8120 mini Node (SBM 2048) HW version 6.24 DCE interface module V.5 W 1.5 W 6.10.5 W 1.+45°C ETS 300 019-1-2:1992-02 Class2.1 Weather protected.0 W 3..5 W 1.. partly temperature controlled storage locations -5°C. depends on furnishing 6. max.28 DTE interface module V. 1W 2. .0 W 1.24/V.5 kg.+70°C Rain is not allowed .1 Temperature-controlled locations +5°C.35 interface module V.9 Mechanics Width Depth Height Weight.35/V.1 or later Storage ETS 300 019-1-1:1992-02 Class1.5 W 1. 352 mm 278 mm 75 mm 4..+40°C (-5°C…+45°C) Transport In use Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 148 22030_12 © 2013 Tellabs.7 W 5.10 Environmental Conditions 6.5 W 1...3 Public transportation -25°C.5 W 1..9 W 1.5 W 1.0 W 1.24 interface module V.36 interface module X. -25°C maximum ETS 300 019-1-3:1992-02 Class 3.6 Technical Specifications of Tellabs 8120 Mini Node M Unit or Module HSSI-M39 LTE-M39 Mini LAN Module OTE-LED-M SMU-M VCM-M-M VCM-V-M VCM-VM-M V24-DCE-M39 V24-DTE-M39 V35-M V35/V24-M39 V36-M39 X21-M Description High-Speed Serial interface module Line terminal 1/2 Mbit/s 10Base-T Ethernet interface module Optical line interface module 2/8 Mbit/s Tellabs 8120 mini M base unit V-series interface base unit VF-series interface base unit V/VF-series interface base unit V.21 interface module Power Consumption (max) 3. Tellabs 8120 mini M must be connected to a wall socket-outlet with protective earth contact.12 Electromagnetic Compatibility Tellabs 8120 mini Node (SBM 2048) HW version 6.11 Safety Compatibility Tellabs 8120 mini node (SBM 2048) HW version 6. 6. When DC power supply is used. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 149 .6 Technical Specifications of Tellabs 8120 Mini Node M 6.1 or later Safety EN 60950-1:2001 When AC power supply is used.1 or later EMC EN 300 386:2005 22030_12 © 2013 Tellabs. Tellabs 8120 mini node M must be permanently connected to earth using the supplied grounding earth wire. 30: SA+SB = C/I (105/109) signal • Frame length: 500 µs 56 kbit/s CCITT V. Bit no.30 V. .110 Rate Adaptation 56 kbit/s → 64 kbit/s Octet no Bit no. 1 1 2 3 4 D1 D8 D15 D22 2 D2 D9 D16 D23 3 D3 D10 D17 D24 4 D4 D11 D18 D25 5 D5 D12 D19 D26 6 D6 D13 D20 D27 7 D7 D14 D21 D28 8C 0 X S3 S4 8B 1 1 1 1 Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 150 22030_12 © 2013 Tellabs.110 Rate Adaptation 48 kbit/s → 64 kbit/s Octet no. S3: SA =108/107 signal • S4: SB = 105/109 signal • X: X = 106 signal • X.110 Tables b and c V.Appendix 1: Frame Structures Appendix 1: Frame Structures Frame Structures at Bit Rates 48…2048 Kbit/s Frames Not Supporting CRC Checking and Plesiochronous Clocking The rate adaptation and multiplexing schemes used in the basic operation mode (no CRC check or independent clocking) are as follows. 1 1 2 3 4 1 0 1 1 2 D1 D7 D13 D19 3 D2 D8 D14 D20 4 D3 D9 D15 D21 5 D4 D10 D16 D22 6 D5 D11 D17 D23 7 D6 D12 D18 D24 8 S1 X S3 S4 • FSW: 1011 • Dn: data bits • S1. 48 kbit/s CCITT V.110/X. 1 72 80 144 160 D1 D1 D1 D10 D1 D11 2 D2 D2 D2 D11 D2 D12 3 D3 D3 D3 D12 D3 D13 4 D4 D4 D4 D13 D4 D14 5 D5 D5 D5 D14 D5 D15 6 D6 D6 D6 D15 D6 D16 7 D7 D7 D7 D16 D7 D17 8 D8 D8 D8 D17 D8 D18 8 kbit/s chan no40 A D9 D9 D9 D9 B D10 D18 D10 C D19 D D20 • Di: User data bits. Bit 8 is used as 8B in frame mode 1 (CCITT V.704.110 table 7b) and as 8C in mode 2 (CCITT V. 160 kbit/s Data rate 64 kbit/s bit no. The index shows sequence order. C. The transfer of clock phase and stuffing bits is based on the method in V.110.110 table 7c). The CRC checking procedure is based on the CRC-4 method used in G. Frames Supporting CRC Checking and Plesiochronous Clocking The rate adaptation and multiplexing schemes supporting CRC checking or/and plesiochronous data clocking are shown below. D29 D36 D43 D50 D30 D37 D44 D51 D31 D38 D45 D52 D32 D39 D46 D53 D33 D40 D47 D54 D34 D41 D48 D55 D35 D42 D49 D56 1 1 1 1 1 1 1 1 V. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 151 . 144 and 160 kbit/s Mapping of 72. 40A.1111 • Dn: data bits • S3: SA =108/107 signal • S4: SB = 105/109 signal • X: X = 106 signal • Frame length: 1 ms 72.Appendix 1: Frame Structures Octet no 5 6 7 8 Bit no. D: 8 kbit/s channels used to transport the n x 8 kbit/s capacity 22030_12 © 2013 Tellabs.. 80. 80. 144.. B. • The frame length is 125 µs. • FSW0 .110 defines two types of frames at 56 kbit/s. 30 Rate Adaptation of 48 kbit/s → 64 kbit/s when Supporting CRC Check and Independent Clocking Octet no Bit no.110 Rate Adaptation of 56 kbit/s → 64 kbit/s when Supporting CRC Check and Independent Clocking Octet no Bit no. . 1 1 2 3 4 5 6 7 8 9 10 D1 D8 D15 D22 D29 D36 D43 D50 D57 D64 2 D2 D9 D16 D23 D30 D37 D44 D51 D58 D65 3 D3 D10 D17 D24 D31 D38 D45 D52 D59 D66 4 D4 D11 D18 D25 D32 D39 D46 D53 D60 D67 5 D5 D12 D19 D26 D33 D40 D47 D54 D61 D68 6 D6 D13 D20 D27 D34 D41 D48 D55 D62 D69 7 D7 D14 D21 D28 D35 D42 D49 D56 D63 D70 8A 0 X CFE S4 0 1 1 1 1 E4 8B 0 X CFE S4 0 1 1 1 1 X 8C 0 X S3 S4 0 1 1 1 1 E4 8D 0 X S3 S4 0 1 1 1 1 X Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 152 22030_12 © 2013 Tellabs.Appendix 1: Frame Structures 48 kbit/s Modified CCITT V.110/X. 1A 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 0 X CFE 1 0 1 1 1 1 E4 E5 E6 C1 C2 C3 C4 1B 0 X CFE 1 0 1 1 1 1 1 1 1 C1 C2 C3 C4 1C 0 X 1 1 0 1 1 1 1 E4 E5 E6 1 1 1 1 2 D1 D7 D13 D19 D25 D31 D37 D43 D49 D55 D61 D67 D73 D79 D85 D91 3 D2 D8 D14 D20 D26 D32 D38 D44 D50 D56 D62 D68 D74 D80 D86 D92 4 D3 D9 D15 D21 D27 D33 D39 D45 D51 D57 D63 D69 D75 D91 D87 D93 5 D4 D10 D16 D22 D28 D34 D40 D46 D52 D58 D64 D70 D76 D82 D88 D94 6 D5 D11 D17 D23 D29 D35 D41 D47 D53 D59 D65 D71 D77 D83 D89 D95 7 D6 D12 D18 D24 D30 D36 D42 D48 D54 D60 D66 D72 D78 D84 D90 D96 8 S1 X S3 S4 S1 X S3 S4 S1 X S3 S4 S1 X S3 S4 56 kbit/s Modified CCITT V. -01111 • Dn: data bits • S3: SA = 108/107 signal • S4: SB = 105/109 signal • X: X = 106 signal • CFE: CRC bit from remote end • Ci: bits for transfer of the CRC word • Ei: bits for transfer of clock phase and stuffing bits • E6: transfers an extra D bit at positive justification inserted between D72 .. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 153 . D71 D78 D85 D92 D99 D106 D72 D79 D86 D93 D100 D107 D73 D80 D87 D94 D101 D108 D74 D91 D88 D95 D102 D109 D75 D82 D89 D96 D103 D110 D76 D83 D90 D97 D104 D111 D77 D84 D91 D98 D105 D112 E5 E6 C1 C2 C3 C3 S3 S4 C1 C2 C3 C4 E5 E6 1 1 1 1 S3 S4 1 1 1 1 • 8A: both CRC checking and plesiochronous clocking are used • 8B: only CRC checking in use • 8C: only plesiochronous clocking in use • 8D: neither CRC check nor plesiochronous clocking in use • FSW: 0 .D73 or D84 . 22030_12 © 2013 Tellabs. 80 kbit/s Adaptation of 72 and 80 kbit/s when Supporting CRC Check and Plesiochronous Clocking Set no 64 kbit/s bit no 1 1 2 3 4 5 6 D1 D1 D1 D1 D1 D1 2 D2 D2 D2 D2 D2 D2 3 D3 D3 D3 D3 D3 D3 4 D4 D4 D4 D4 D4 D4 5 D5 D5 D5 D5 D5 D5 6 D6 D6 D6 D6 D6 D6 7 D7 D7 D7 D7 D7 D7 8 D8 D8 D8 D8 D8 D8 8 kbit/s chan41 A D9 D9 D9 D9 D9 D9 B D10 D10 D10 D10 D10 D10 C 0 X CFE S4 0 1 418 kbit/s channel no B is not used at 72 kbit/s.Appendix 1: Frame Structures Octet no 11 12 13 14 15 16 Bit no. Channel C uses a 16-bit long frame carrying the CRC check sum and phasing and stuffing data for plesiochronous clocking.D85 • D73: is set to 1 when performing negative justification • Frame length: 2 ms 72. -01111 • Dn: data bits • S3: SA = 108/107 signal • S4: SB = 105/109 signal • X: X = 106 signal • CFE: CRC bit from far-end • Ci: bits for transfer of the CRC word • Ei: bits for transfer of clock phase and stuffing bits • E6: transfers an extra D bit at positive justification inserted before bit D1 of set 14 • D8 of set 13: is set to 1 when performing negative justification • Frame length: 2 ms 144.. kbit/s channels B and D are not used at 160 kbit/s. 160 kbit/s Adaptation of 144 and 160 kbit/s when Supporting CRC Check and Plesiochronous Clocking Set no42 64 kbit/s bit no 1 1a 1b 2a 2b D1 D11 D1 D11 2 D2 D12 D2 D12 3 D3 D13 D3 D13 4 D4 D14 D4 D14 5 D5 D15 D5 D15 6 D6 D16 D6 D16 7 D7 D17 D7 D17 8 D8 D18 D8 D18 8 kbit/s no43 A D9 D9 B D10 D10 D19 D20 X D19 D20 0 C D E sets a and b are transmitted during the same G. Channel E uses a 16-bit long frame carrying the CRC check sum and phasing and stuffing data for plesiochronous clocking.704 frame (125 µs). .Appendix 1: Frame Structures Set no 7 8 9 10 11 12 13 14 15 16 64 kbit/s bit no D1 D1 D1 D1 D1 D1 D1 D1 D1 D1 D2 D2 D2 D2 D2 D2 D2 D2 D2 D2 D3 D3 D3 D3 D3 D3 D3 D3 D3 D3 D4 D4 D4 D4 D4 D4 D4 D4 D4 D4 D5 D5 D5 D5 D5 D5 D5 D5 D5 D5 D6 D6 D6 D6 D6 D6 D6 D6 D6 D6 D7 D7 D7 D7 D7 D7 D7 D7 D7 D7 D8 D8 D8 D8 D8 D8 D8 D8 D8 D8 8 kbit/s chan41 D9 D9 D9 D9 D9 D9 D9 D9 D9 D9 D10 D10 D10 D10 D10 D10 D10 D10 D10 D10 1 1 1 E4 E5 E6 C1 C2 C3 C4 • Set: group of data bits transmitted each 125 µs • FSW: 0 . 438 42The Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 154 22030_12 © 2013 Tellabs. Appendix 1: Frame Structures Set no42 3a 3b 4a 4b 5a 5b 6a 6b 7a 7b 8a 8b 9a 9b 10a 10b 11a 11b 12a 12b 13a 13b 14a 14b 15a 15b 16a 16b 64 kbit/s bit no D1 D11 D1 D11 D1 D11 D1 D11 D1 D11 D1 D11 D1 D11 D1 D11 D1 D11 D1 D11 D1 D11 D1 D11 D1 D11 D1 D11 D2 D12 D2 D12 D2 D12 D2 D12 D2 D12 D2 D12 D2 D12 D2 D12 D2 D12 D2 D12 D2 D12 D2 D12 D2 D12 D2 D12 D3 D13 D3 D13 D3 D13 D3 D13 D3 D13 D3 D13 D3 D13 D3 D13 D3 D13 D3 D13 D3 D13 D3 D13 D3 D13 D3 D13 D4 D14 D4 D14 D4 D14 D4 D14 D4 D14 D4 D14 D4 D14 D4 D14 D4 D14 D4 D14 D4 D14 D4 D14 D4 D14 D4 D14 D5 D15 D5 D15 D5 D15 D5 D15 D5 D15 D5 D15 D5 D15 D5 D15 D5 D15 D5 D15 D5 D15 D5 D15 D5 D15 D5 D15 D6 D16 D6 D16 D6 D16 D6 D16 D6 D16 D6 D16 D6 D16 D6 D16 D6 D16 D6 D16 D6 D16 D6 D16 D6 D16 D6 D16 D7 D17 D7 D17 D7 D17 D7 D17 D7 D17 D7 D17 D7 D17 D7 D17 D7 D17 D7 D17 D7 D17 D7 D17 D7 D17 D7 D17 D8 D18 D8 D18 D8 D18 D8 D18 D8 D18 D8 D18 D8 D18 D8 D18 D8 D18 D8 D18 D8 D18 D8 D18 D8 D18 D8 D18 8 kbit/s no43 D9 D9 D9 D9 D9 D9 D9 D9 D9 D9 D9 D9 D9 D9 D10 D10 D10 D10 D10 D10 D10 D10 D10 D10 D10 D10 D10 D10 D19 D20 C4 D19 D20 C3 D19 D20 C2 D19 D20 C1 D19 D20 E6 D19 D20 E5 D19 D20 E4 D19 D20 1 D19 D20 1 D19 D20 1 D19 D20 1 D19 D20 1 D19 D20 S4 D19 D20 CFE • FSW: 0 ..-01111 • Dn: data bits • S3: SA = 108/107 signal • S4: SB = 105/109 signal • X: X = 106 signal • CFE: CRC bit from far-end • Ci: bits for transfer of the CRC word • Ei: bits for transfer of clock phase and stuffing bits 22030_12 © 2013 Tellabs. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 155 . . . channel B is sufficient. If required. the 8 kbit/s channel C is used to carry signal SB transferring signal 105/109 or C/I • FSW: 0 . When no independent clocking is needed or when bit rates are below 512 kbit/s.-01111 • S4: SB = 105/109 signal • X: X = 106 signal • CFE: CRC bit from far-end • Ci: bits for transfer of the CRC word • Ei: bits for transfer of clock phase and stuffing bits • E6: transfers an extra D bit at positive justification The n x 64 kbit/s data is chopped into bytes.Appendix 1: Frame Structures • E6: transfers an extra D bit before D1 of set 13a at positive justification • D8 of set 13a: is set to 1 when performing negative justification • Frame length: 2 ms Adaptation of n x 64 kbit/s when Supporting CRC Check and Plesiochronous Clocking Frame No 8 kbit/s no A 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 E4 E5 E6 1 E4 E5 E6 1 E4 E5 E6 1 E4 E5 E6 B 0 X CFE S4 0 1 1 1 1 E4 E5 E6 C1 C2 C3 C4 C SB SB SB SB SB SB SB SB SB SB SB SB SB SB SB SB The 8 kbit/s channel A carries the clock phasing and justification data at bit rates exceeding 512 kbit/s. At positive justification the bit E6 is inserted after the last bit of the first byte received in frame 13. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 156 22030_12 © 2013 Tellabs. A negative justification takes place by deleting the last bit of the first byte received in frame 13. 6 kbit/s 19. Relation between Data Rates and Adapted XB Rates Data rate 1. S9: SB = 105/109 signal • X: X = 106 signal • E1-E3: user data rate information code • E4-E6: bits for transfer of clock phase information and stuffing bits at plesiochronous operation.4 kbit/s XB rate 8 kbit/s 8 kbit/s 16 kbit/s 32 kbit/s 64 kbit/s The octet structured V.Appendix 1: Frame Structures Frame Structures at Bit Rates below 48 Kbit/s Bit rates below 48 kbit/s are rate adapted to n x 8 kbit/s (XB rate) according to CCITT Recommendation V.2 kbit/s 2. S3. User Rates n x 4. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 157 . They are set to 1 when not used 22030_12 © 2013 Tellabs. S8: SA = 108/107 signal • S4.110/X.8 kbit/s V.2 kbit/s 38.30.4 kbit/s 9.110 frame is 80 bits long. S6.110 Frame for Adaptation of n x 4800 b/s to n x 8 kbit/s Octet no Bit no 1 1 2 3 3 5 6 7 8 9 10 0 1 1 1 1 1 1 1 1 1 2 0 D1 D7 D13 D19 E1 D25 D31 D37 D43 3 0 D2 D8 D14 D20 E2 D26 D32 D38 D44 4 0 D3 D9 D15 D21 E3 D27 D33 D39 D45 5 0 D4 D10 D16 D22 E4 D28 D34 D40 D46 6 0 D5 D11 D17 D23 E5 D29 D35 D41 D47 7 0 D6 D12 D18 D24 E6 D30 D36 D42 D48 8 0 S1 X S3 S4 E7 S1 X S3 S4 • FSW: 000000001…1…1…1…1…1…1…1…1 • Dn: data bits • S1. bit 1 = D1+D2. Bit no 1 1 2 3 3 5 6 7 8 9 10 0 1 1 1 1 1 1 1 1 1 2 0 D1 D7 D11 F E1 D19 D25 D29 F 3 0 D2 D8 D12 F E2 D20 D26 D30 F 4 0 D3 D9 F D15 E3 D21 D27 F D33 5 0 D4 D10 F D16 E4 D22 D28 F D34 6 0 D5 F44 D13 D17 E5 D23 F D31 D35 7 0 D6 F D14 D18 E6 D24 F D32 D36 8 0 S1 X S3 S4 E7 S1 X S3 S4 Otherwise see the table User Rates n x 4.g. E7 is set to 1 when not used • E6: transfers an extra D bit at positive justification.g. 44F = filling bit Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 158 22030_12 © 2013 Tellabs.g bit 1 = D1+D2+D3+D4. The bit is inserted between D24 and D25 • D25 : is set to 1 when performing negative justification • Frame length: 2.110 Frame for Adaptation of n x 3600 bit/s to n x 8 kbit/s Octet no.Appendix 1: Frame Structures • E7: alignment bit for the four frame multiframe (MFSW=1110). bit2 = D3+D4. D19 corresponds to D25. 12 bits at 1200 bit/s and 24 bits at 2400 bit/s.5. 1200 and 2400 are mapped to the frame of the previously presented table Adaptation of n x 64 kbit/s when Supporting CRC Check and Plesiochronous Clocking as follows: • Each 600 b/s bit occupies eight consecutive Dn bit positions starting from D1 (e.110 frame transfers 6 bits at 600 bit/s. depending on bit rate The rates 600. One V. . bit 1 = D1+D2+D3+D4+D5+D6+D7+D8) • Each 1200 b/s bit occupies four consecutive Dn bit positions starting from D1 (e. 5 or10 ms. bit3 = D5+D6).6 kbit/s V.8 kbit/s. User Rates n x 3. bit2 = D5+D6+D7+D8) • Each 2400 b/s bit occupies two consecutive Dn bit positions (e. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 159 .110 Frame for Adaptation of n x 3200 b/s to n x 8 kbit/s Octet no Bit no 1 1 2 3 3 5 6 7 8 9 10 0 1 1 1 1 1 1 1 1 1 2 0 D1 D7 D11 F E1 D17 D23 D27 F 3 0 D2 D8 D12 F E2 D18 D24 D28 F 4 0 D3 D9 F D15 E3 D19 D25 F D31 5 0 D4 D10 F D16 E4 D20 D26 F D32 6 0 D5 F D13 F E5 D21 F D29 F 7 0 D6 F D14 F E6 D22 F D30 F 8 0 S1 X S3 S4 E7 S1 X S3 S4 User Rates n x 3.Appendix 1: Frame Structures User Rates n x 3. Bit Information Code E1-E3 Bit rate bit/s 600 1200 E1 E2 E3 100 010 22030_12 © 2013 Tellabs.110 Frame for Adaptation of n x 3000 b/s to n x 8 kbit/s Octet no Bit no 1 1 2 3 3 5 6 7 8 9 10 0 1 1 1 1 1 1 1 1 1 2 0 D1 D7 D11 F E1 D16 D22 D26 F 3 0 D2 D8 D12 F E2 D17 D23 D27 F 4 0 D3 D9 F D15 E3 D18 D24 F D30 5 0 D4 D10 F F E4 D19 D25 F F 6 0 D5 F D13 F E5 D20 F D28 F 7 0 D6 F D14 F E6 D21 F D29 F 8 0 S1 X S3 S4 E7 S1 X S3 S4 Bit Rate Information Code E1-E3 The bit rate information is coded as follows.0 kbit/s V.2 kbit/s V. . Clock Phase and Stuffing Information Clock displacement. The E4-E6 bits are used as follows. % 0 +20 +40 -40 -20 E4 E5 E6 111 000 001 010 011 Stuffing control Positive justification of a 1 Positive justification of a 0 Negative justification 101 100 110 Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 160 22030_12 © 2013 Tellabs.Appendix 1: Frame Structures Bit rate bit/s 2400 4800 9600 19200 38400 3600 7200 14400 28800 3000 6000 12000 24000 3200 6400 12800 25600 E1 E2 E3 110 011 011 011 011 101 101 101 101 011 011 011 011 001 001 001 001 Use of Clock Phase and Stuffing Information Bits E4-E6 Network independent timing (plesiochronous) is supported at user data rates 3000 b/s and above. 22030_12 © 2013 Tellabs. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 161 . n x 3000 and n x 3200 b/s to n x 8 kbit/s as in the tables of the Frame Structures at Bit Rates below 48 Kbit/s presented earlier in Appendix 1.110 Frame for Transfer of CRC Check Sum Octet no Bit no 1 1 2 3 3 5 6 7 8 9 10 0 1 1 1 1 CFE C1 C2 C3 C4 2 0 D1 D7 D13 D19 E1 D25 D31 D37 D43 3 0 D2 D8 D14 D20 E2 D26 D32 D38 D44 4 0 D3 D9 D15 D21 E3 D27 D33 D39 D45 5 0 D4 D10 D16 D22 E4 D28 D34 D40 D46 6 0 D5 D11 D17 D23 E5 D29 D35 D41 D47 7 0 D6 D12 X D18 D24 E6 D30 D36 D42 D48 S3 S4 E7 S1 X S3 S4 8 0 S1 • FSW: 000000001…1…1…1 • Dn: data bits • S1. S3: SA = 108/107 signal • S4: SB = 105/109 signal • X: X = 106 signal • E1-E3: user data rate information code • E4-E6: bits for transfer of clock phase information and stuffing bits at plesiochronous • CFE: CRC check sum indication to the far-end • Ci: CRC check sum • F: filling bits (not shown) are used for adaptation of n x 3600.Appendix 1: Frame Structures Modified V. 704 Frame Structures 8448 kbit/s Frame Structure Fig.Appendix 2: G.704 Frame Structures Appendix 2: G.704 8448 kbit/s Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 162 22030_12 © 2013 Tellabs. . 80 Frame Structure of G. 704 Frame Structures 2048 kbit/s Frame Structure Fig.Appendix 2: G.704 2048 kbit/s 22030_12 © 2013 Tellabs. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 163 . 81 Frame Structure of G. .704 Frame Structures N x 64 kbit/s Frame Structure Fig.Appendix 2: G. 82 Frame Structure of G.704 n x 64 kbit/s. n ≤ 17 Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 164 22030_12 © 2013 Tellabs. n > 17 22030_12 © 2013 Tellabs. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 165 .704 n x 64 kbit/s.704 Frame Structures Fig.Appendix 2: G. 83 Frame Structure of G. 68. 69.Appendix 2: G. . A=FEA (1-active).) 45Frame # SigTSbits1234abcd 0000 TS1 TS2 TS3 TS4 TS5 TS6 TS7 TS8 TS9 TS10 TS11 TS12 TS13 TS14 TS15 SigTSbits5678abcd SASS TS17 TS18 TS19 TS20 TS21 TS22 TS23 TS24 TS25 TS26 TS27 TS28 TS29 TS30 TS31 Use 0000=M-FSW. . . N x 64 kbit/s frame with n≤17 TSn-1. . S=spare abcd bits for TS1 and TS17 of the group . . . . . 2 Mbit/s frame and n x 64 kbit/s frame with n >17 TS16. abcd bits for TS15 and TS31 of the group 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 45Multiframe length is 16 frames/125 µs = 2 ms (500 Hz) Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 166 22030_12 © 2013 Tellabs. . . . . 70. .704 Frame Structures Multiframe Structure in Signalling Time Slot (8 Mbit/s frame TS67. S = spare 0011011 = FSW.704 Frame Structures CRC Multiframe Structure in TS0 for 2 Mbit/s and n x 64 kbit/s Frames Frame # Block #1 0 1 2 3 4 5 6 7 Block #2 8 9 10 11 12 13 14 15 C1 1 C2 1 C3 E1 C4 E2 0011011 1ASHHHH 0011011 1ASHHHH 0011011 1ASHHHH 0011011 1ASHHHH E2 = BlockII FEA (0-active) E1 = BlockI FEA (0-active) C1 0 C2 0 C3 1 C4 0 0011011 1ASHHHH 0011011 1ASHHHH 0011011 1ASHHHH 0011011 1ASHHHH 46C1…C4 TS0 bits1 2345678 Use = CRC-4 bits A = FEA (1-active). H = reserved for the HDLC link 001011 = CRC M-FSW 46The CRC multiframe length is 16 frames/125 µs = 2 ms (500Hz) 22030_12 © 2013 Tellabs. Tellabs ® 8100 Managed Access System Tellabs ® 8120 Mini Node M Operating Manual 167 .Appendix 2: G.