TN1Ue Reference Manual Issue 9.0

TN1Ue
SDH Multiplexer
Technical Overview
& Reference Manual
Copyright  GE Multilin Inc. 2002-2017
TN1-86400-400PS
Issue 9.0
May 2017
TN1-86400-400PS
Issue 9.0
May 2017
Page 2
TN1Ue
SDH Multiplexer
Technical Overview and Reference Manual
Copyright  GE Multilin Inc. 2002-2017, All Rights Reserved
The copyright of this document is the property of GE Multilin Inc. This document must not be copied,
reprinted or reproduced in any material form, either wholly or in part, without the written consent of GE
Multilin Inc.
GE Multilin reserves the right to make changes and modifications to any part of this document without
notice.
GE Multilin Inc. is not responsible for any damages or losses incurred as a result of out-of-date or
incorrect information contained in this document.

TN1-86400-400PS
Issue 9.0
May 2017
Page 3
TABLE OF CONTENTS
SECTION PAGE
1 INTRODUCTION ....................................................... 7
1.1 Overview ................................................................................................... 7
1.2 Summary of Features .............................................................................. 9
1.3 Applications ............................................................................................ 10
2 PRODUCT STRUCTURE ......................................... 11

2.1 Optical Aggregate Unit ........................................................................... 11
2.2 TU-1 Level Units ...................................................................................... 12
2.3 TUG-3 Level Units ................................................................................... 14
2.4 64 kb/s Level Units .................................................................................. 15
2.5 Supporting Units ..................................................................................... 15
2.6 Paddleboards .......................................................................................... 17
3 FEATURES............................................................... 19
3.1 Introduction ............................................................................................. 19
3.2 SDH Conformance .................................................................................. 19
3.2.1 Background and History.................................................................. 19
3.2.2 TN1Ue System .................................................................................. 20
3.3 Main Design Specifications .................................................................... 20
3.4 Local and Remote Monitoring and Configuration ................................ 21
3.5 System Redundancy and Availability ................................................... 21
3.6 Security and Dependability Features .................................................... 22
3.7 Alternate Traffic Routing ........................................................................ 23
3.8 Modular Design and Expansion ............................................................. 24
4 COMMON EQUIPMENT UNITS ............................... 25

4.1 Introduction ............................................................................................. 25
4.2 Equipment Shelf ...................................................................................... 26
4.3 Power Unit ............................................................................................... 29
4.4 STM-16 Aggregate Unit ........................................................................... 30
4.5 STM-4 Aggregate Unit ............................................................................. 35
4.6 STM-1 Aggregate Unit ............................................................................. 39

TN1-86400-400PS
Issue 9.0
May 2017
Page 4
4.7 External Sync Unit .................................................................................. 44

4.8 Cyber-Secured Service Unit (CSSU) ..................................................... 46
4.9 Orderwire Unit ......................................................................................... 51
4.10 CMUX Unit................................................................................................ 52
4.11 CDAX Unit ................................................................................................ 54
4.12 Tie Unit ..................................................................................................... 57
4.13 TUG-3 Unit ............................................................................................... 58
5 INTERFACE UNITS .................................................. 59

5.1 Introduction ............................................................................................. 59
5.2 Ethernet Applications ............................................................................. 59
5.2.1 ETHER-1000 Unit .............................................................................. 59
5.2.2 ETHER-100 Unit ................................................................................ 70
5.2.3 ETHER-10 Unit .................................................................................. 74
5.3 VF Applications ....................................................................................... 76
5.3.1 4W VF Unit ........................................................................................ 76
5.3.2 2W FXO and 2W FXS Units .............................................................. 77
5.3.3 2W TO/E&M Unit ............................................................................... 78
5.3.4 4W VF Partyline Unit ........................................................................ 79
5.4 Digital Telemetry Applications ............................................................... 80
5.4.1 Contact I/O Unit ................................................................................ 80
5.5 Data Applications .................................................................................... 81
5.5.1 DATA-LS Unit ................................................................................... 81
5.5.2 DATA-PTM Unit ................................................................................ 82
5.5.3 DATA-G703 Unit ............................................................................... 83
5.5.4 DATA-NX64 Unit ............................................................................... 84
5.5.5 T1/E1 Unit ......................................................................................... 85
5.6 Teleprotection Applications ................................................................... 87
5.6.1 DATA-NX64F Unit ............................................................................. 87
5.6.2 DTT Unit ............................................................................................ 88
5.6.3 DTT Test Panel ................................................................................. 90
6 NETWORK MANAGEMENT..................................... 91
6.1 Introduction ............................................................................................. 91
6.2 What is VistaNET..................................................................................... 91
6.3 Peer-to-Peer VistaNET Architecture ...................................................... 91
6.4 Features ................................................................................................... 92
6.5 Node Communications ........................................................................... 93
6.5.1 STM-N Aggregate to TU-1 Level Unit Communications ................ 93
6.5.2 CMUX/CDAX Unit to Channel Unit Communications..................... 93
6.6 Intra-Ring Communications ................................................................... 93
6.7 Ring-to-Ring Communications .............................................................. 94
6.8 VistaNET Workstation Communications ............................................... 94
6.9 VistaNET Unit Discovery ........................................................................ 94

TN1-86400-400PS
Issue 9.0
May 2017
Page 5
6.10 VistaNET System Tree ............................................................................ 95

6.11 VistaNET Application Tabs .................................................................... 95
6.11.1 View Tab – Ring Map View .............................................................. 95
6.11.2 View Tab – SDH Network Map View ................................................ 97
6.11.3 View Tab – Unit View ....................................................................... 98
6.11.4 Alarms Tab (Alarm Engine) ............................................................. 99
6.11.5 Inventory Tab .................................................................................. 100
6.11.6 Activity Log Tab .............................................................................. 101
6.12 VistaNET Security .................................................................................. 102
6.12.1 VistaNET Security Management..................................................... 103
7 CONFIGURATIONS ................................................ 105

7.1 Introduction ............................................................................................ 105
7.2 Standalone TN1Ue System .................................................................... 105
7.2.1 Ring Network ................................................................................... 105
7.2.2 Linear Add & Drop Network ........................................................... 106
7.2.3 Multiple Network System ................................................................ 108
7.3 TN1Ue and Foreign SDH Networks....................................................... 109
7.3.1 TN1Ue with Foreign STM-N Nodes in Same Network ................... 109
7.3.2 TN1Ue STM-N Ring Established Through a Higher Order SDH
Network Capable of Switching at VC-4 Level Only .................................. 109
7.3.3 TN1Ue STM-4 Ring Established Through a Higher Order SDH
Network Capable of Switching at VC-12 Level ......................................... 111
7.3.4 Applications with SDH Radio ......................................................... 111
7.3.5 Two Parts of TN1Ue System Interconnected via VC-12 Cross-
Connect ....................................................................................................... 112
7.4 Applications with Backup Control Centre ........................................... 112
7.4.1 Main and Backup Control Centres in Same Ring ......................... 112
7.4.2 Main and Backup Control Centres in Different Rings .................. 113
7.5 Mixed TN1Ue and E1MXe Networks ..................................................... 114
7.6 Standalone E1MXe Networks ................................................................ 115
8 SYNCHRONIZATION, PROPAGATION DELAYS AND

SYSTEM ENGINEERING ........................................ 117
8.1 Synchronization and Clocking .............................................................. 117
8.1.1 Synchronization Status Messaging (SSM) Algorithm .................. 120
8.1.2 External Sync Unit Application Examples..................................... 123
8.1.3 Clock Distribution in Mixed TN1Ue and E1MXe Networks ........... 129
8.1.4 Clock Distribution in Standalone E1MXe Networks ..................... 129
8.2 Propagation Delays................................................................................ 130
8.3 System Engineering............................................................................... 132
APPENDIX A................................................................ 135

TN1-86400-400PS
Issue 9.0
May 2017
Page 6
List of Figures ................................................................................................. 135

List of Tables .................................................................................................. 139
APPENDIX B................................................................ 141

List of Acronyms ............................................................................................ 141

TN1-86400-400PS
Issue 9.0
May 2017
Page 7
1 INTRODUCTION
1.1 Overview
TN1Ue is an integrated SDH drop-and-insert (add/drop) multiplexer operating at the STM-16 (2,488.32
Mb/s), STM-4 (622.08 Mb/s) or STM-1 rate (155.52 Mb/s), designed specifically for utility (power,
transportation, pipelines, oil & gas, etc.) industry communications. It can be configured for operation in
various network topologies including point-to-point, linear add/drop, self-healing path-protected rings,
multiple self-healing rings, rings-plus-spurs etc.
An STM-1/STM-4 TN1Ue system can be upgraded to higher capacity (STM-4/STM-16) by upgrading the
optical aggregate modules. For a protected TN1Ue system, this upgrade can be done while maintaining
services (in-service upgrade).
TN1Ue can accommodate a variety of broadband, wideband and narrowband services thus providing a
compact transport solution for a wide range of applications. Each service uses a dedicated portion of the
STM-N bandwidth which is not shared with other ones and is available to the given service in its entirety all
the time. The entire TN1Ue system has been designed and built around the concept of providing an
extremely reliable and dependable transmission network for transporting a variety of services, including
mission critical applications such as teleprotection, signalling and SCADA.
Compact unit design and flexible shelf architecture allow housing of all the units, from the optical ones
down to various user interfaces, on the same shelf. Additional shelf slots can be provided by adding
virtually unlimited number of expansion shelves.
As shown in Figure 1, the STM-4 optical signal can be visualized as a group of four VC-4s where each
VC-4 consists of three TUG-3s. These are represented as smaller virtual pipes inside a large STM-4
pipe. Each TUG-3 can be dedicated to a single service (single interface module) or be broken down into
21 smaller pipes of 2.2 Mb/s called VC-12s.1 If required, each VC-12 can be further divided in smaller
pipes of 64 kb/s. Note that each virtual pipe uses dedicated bandwidth with guaranteed quality of service
and is completely isolated and secured from other pipes. Furthermore, each pipe can be optionally
protected if TN1Ue ring topology is deployed.
The above model is also applicable to STM-16 and STM-1 signals. Note that STM-16 carries 16 VC-4s
while STM-1 carries only one VC-4 i.e. three TUG-3s.
The interface modules offered with TN1Ue are classified in 3 categories: broadband, wideband and
narrowband.
Broadband interface modules are mapping broadband services into the SDH payload at the VC-3/TU-3
level (TUG-3 accommodates one VC-3)2. Examples of broadband services are Gigabit Ethernet and Fast
Ethernet.
Wideband interface modules are mapping wideband services into the SDH payload at the VC-12/TU-12
level. Examples of wideband services are 10Mb/s Ethernet and E1 signals3.
1 TUG-3 actually accommodates 21 TU-12s, where each TU-12 consists of one VC-12 and a TU-1 pointer.
Therefore, the terms VC-1 and TU-1 are often used interchangeably.
2 TUG-3 actually accommodates one TU-3 which consists of one VC-3 and a TU-3 pointer. Therefore, terms VC-3
and TU-3 are often used interchangeably.
3 With the exception of E1 interface unit, the wideband interface units map the tributary signals into VC-11s,
however, these are converted into VC-12s before multiplexing.

TN1-86400-400PS
Issue 9.0
May 2017
Page 8
VC-4 TUG-3 # 2,1 VC-3

Ethernet
#2
TUG-3 # 2,3
TUG-3 # 1,1 VC-3

VC-4 Ethernet
#1 TUG-3
TUG-3 # 1,2# 3,1
VC-3
STM-4 TUG-3 # 1,3

TUG-3 # 3,2
TUG-3
TUG-3 # 4,1 # 3,3
VC-12 # 4,2,1 E1
VC-4 Ethernet
VC-12 # 4,2,2 VC-11
#4 TUG-3 # 4,2 64k # 1 RS-232
VC-12 # 4,2,21 VC-11 64k # 2 VF
64k # 24
56/64k DATA
TUG-3 # 4,3 Teleprotection
Optical Level VC-4 Level TUG-3 Level VC-1/TU-1 Level 64kb/s Level
Figure 1: STM-4 signal virtual pipes showing various levels of services
Narrowband interface modules are mapping narrowband services into the SDH payload at the 64 kb/s
channel level. Examples of narrowband interfaces are voice frequency (VF) signals, low and high-speed
data, digital telemetry and teleprotection signals.
Certain interface modules require use of multiple pipes (N  pipe capacity) to offer more bandwidth for
the respective services. For example, the ETHER-1000 module can map Ethernet signals onto SDH
using 1 to 24 VC-3s thus providing up to 1.2 Gb/s (24 x 50 Mb/s) for Ethernet transport. Similarly, the
ETHER-10 module can be configured to use 1 to 7 VC-12s to provide 1.6 to 11.2 Mb/s for Ethernet
transport. The Data-Nx64 data module can use 1 to 12 64kb/s channels to provide bandwidth for
mapping a data signal at a rate ranging from 64 to 768 kb/s.
The TN1Ue Network Management System (NMS) called VistaNET offers an easy, intuitive, yet powerful
Operation, Administration, Maintenance and Provisioning tool, which provides remote management of
every node in the TN1Ue system, from the optical aggregate units all the way down to interface modules.
VistaNET is a Microsoft Windows based software and connects to the TN1Ue network through a serial
RS-232 link (directly or through a modem connection) and/or via Ethernet connection. Multiple
simultaneous NMS users can be accommodated.
The NMS communication between TN1Ue nodes is normally carried out using SDH overhead channels
reserved for NMS. In addition, TN1Ue can be configured to map NMS information inside the payload
which ensures NMS visibility in applications where TN1Ue nodes are combined with foreign SDH nodes
within the same ring or linear network.

TN1-86400-400PS
Issue 9.0
May 2017
Page 9
Utility organizations have very distinct and unique environmental requirements. Equipment is often
located in a power utility substation, roadside, trackside or next to a pipeline block valve where EMI
(Electromagnetic Interference) and RFI (Radio Frequency Interference) levels are greatly increased and
where the occurrence of an electrical surge is not an unusual event. The equipment is required to operate
over wide temperature range and to provide secure, dependable and robust transmission channels
capable of backup either by redundancy or alternate fibre path routing. All these specific utility
requirements and corresponding performance parameters are built in the design of every TN1Ue module.
Safe testing of teleprotection circuits, alarming and NMS support for all modules down to individual
interface cards are some of those additional characteristics of the system designed specifically for the
utility market.
This reference document is meant to assist planners and engineers of telecommunication networks in
understanding and implementing the TN1Ue system for immediate and future communication
requirements.
1.2 Summary of Features
 An SDH-based add & drop multiplexer that integrates transport and access functionality
 Diverse collection of interfaces for broadband, wideband and narrowband applications (Ethernet,
Voice, Data, Digital Telemetry, Teleprotection)
 Scalable bandwidth allocation to services
 Direct access to individual services including those mapped into 64 kb/s channels
 Low power consumption
 Guaranteed performance over the ambient temperature range of -10 to +60 ºC
 No built-in fans
 No air-conditioning required
 Implements path protection switching for all supported services. Protection switching is faster than
3 ms for mission critical applications.
 Minimal end-to-end delays
 Fast traffic rerouting to backup control centre(s)
 Smooth integration with legacy E1 networks
 Integrated Windows-based Network Management System with powerful Alarm Engine and remote
access to individual units from optical aggregate units down do 64 kb/s level units
 Operates on 48 VDC power supply
 System reference clock can be generated internally or obtained from an external source
 Orderwire communication for maintenance personnel
 Modular design for ease of maintenance, configuration and expansion
 Redundancy for critical modules
 Supports multiple topologies (point-to-point, linear, ring, multiple rings etc.)
 Capable of passing NMS information through foreign SDH equipment
 Cyber-secured NMS (data privacy, authentication, authorization & administration)
 Optional SNMP agent for building customized NMS solutions
 Meets ANSI/IEEE C37.90.1 specification for surge withstand and fast transients
 Meets ETSI EN 300386-2 and CENELEC EN 50082-2 specifications for EMC
 Meets IEC 60950 specification for Safety of Information Technology Equipment

TN1-86400-400PS
Issue 9.0
May 2017
Page 10
1.3 Applications
The applications for the TN1Ue integrated communications system are those that require:
 Economic, reliable multiplexing of Ethernet, voice, data, digital telemetry, SCADA and/or
teleprotection traffic
 Flexible networking using linear, ring, and/or multiple ring topologies
 Multiplexing of traffic for transport over higher-order SDH STM-N multiplexers or SDH radio
equipment
 Fast protection switching and minimal delays
 Operation in harsh environment (extreme temperatures, humidity, high EMI and RFI etc.).
All the above makes the TN1Ue a perfect choice for a variety of organizations including Power Utilities, Oil
and Gas Utilities, Pipelines, Transportation Systems (Highways, Ground, Rail, Metro) etc.

TN1-86400-400PS
Issue 9.0
May 2017
Page 11
2 PRODUCT STRUCTURE
The TN1Ue system is extremely modular in design which makes it very flexible and adaptable to various
application needs and allows for simple additions of new features to existing systems. Consequently, the
TN1Ue product portfolio has grown to include a large number of modules (units). This section is meant to
provide the reader with the basic concepts of the TN1Ue product structure. Understanding these
concepts will establish a good basis for getting deeper into individual unit functionalities.
2.1 Optical Aggregate Unit

Figure 2 shows the hierarchy of units available for carrying customer traffic. Optical aggregate units
including STM-16, STM-4 and STM-1 Aggregate units are at the top of this hierarchy. On the line side,
these units are equipped with single-mode fibre-optic interfaces running at 2488.32 Mb/s, 622.08 Mb/s
and 155.52 Mb/s respectively. Each add/drop node in a ring or linear network is equipped with two optical
aggregate units of the same type while a terminal node in a linear network configuration is equipped with
one optical aggregate unit only. At an add/drop node, all the traffic that is not dropped locally is passed
through between the two aggregate units.
Optical Aggregate Units TUG-3 Level Units

STM-1 STM-4 STM-16 10/100/1000 Mbps
155.52 Mb/s 622.08 Mb/s 2488.32 Mb/s ETHER-1000 Ethernet LAN
(up to 24xTU-3)
10/100 Mbps
CBW-A CBW-A ETHER-100 Ethernet LAN
CBW-A (up to 6xTU-3)
CBW-B CBW-B
STM-1 STM-4 STM-16
CBW-C CBW-C
Agg. Agg. Agg.
CBW-D CBW-D
CBW-B CBW-E CBW-E
TUG-3
TIFports TIFports TIFports TIFports
TU-1 (TIF)
CMUX CDAX T1/E1 Tie ETHER-10 Level Units
(Up to 4 TU-11s) (up to 7 TU-11s) (Up to 7 TU-12s) (Up to 7 TU-12s) (Up to 7 TU-11s)
CBUS
ports
To 64 kbps channel Same as E1 Interfaces To other TN1U 10/100 Mbps
units (see below) CMUX plus (T1 mode is n/a nodes (TU-12 Tie Ethernet LAN
channelized E1 for TN1U) connections)
64 kbps
4W 2W 2W 2W Level
Data Data Data Data Data Cont
VF VF VF VF DTT Units
LS PTM G.703 Nx64 Nx64F I/O
E&M FXO FXS E&M
Figure 2: Hierarchy of TN1Ue units available for carrying customer traffic

TN1-86400-400PS
Issue 9.0
May 2017
Page 12
As defined in Section 1, all tributary signals can be grouped in broadband, wideband and narrowband
signals. A broadband signal occupies one or more TUG-3s, a wideband signal occupies one or more TU-
12s/VC-12s, while a narrowband signal occupies one or more 64 kb/s channels. Narrowband and
wideband signals are mapped into VC-12s that are subsequently multiplexed into TUG-3s, while the
broadband signals are mapped into VC-3s where each VC-3 will be subsequently placed into an individual
TUG-3. Table 1 depicts capacities of aggregate units and their capabilities when it comes to dropping 1
narrowband, wideband and broadband applications.
Add/drop capabilities
Unit Capacity Supported cross-connect levels
Narrowband Wideband Broadband
STM-16 Agg. 48 x TUG-3* Yes Yes Yes TU-12, TUG-3, VC-4, VC-4-4c
STM-4 Agg. 12 x TUG-3* Yes Yes Yes TU-12, TUG-3. Also capable of
bypassing individual VC-4s.
STM-1 Agg. 3 x TUG-3* Yes Yes Yes TU-12, TUG-3
* Each TUG-3 can either be VC-12-structured (carries 21 VC-12s) or be used for one broadband application. Each
VC-12 can either be 64kb/s-structured (carries 64kb/s channels for narrowband applications) or be used for a
wideband application.
Table 1: Optical Aggregate Unit Capacities and Drop Capabilities
All three optical aggregate (units are capable of dropping narrowband, wideband and broadband
applications. A broadband application is dropped through a CBW port. CBW stands for Configurable
Bandwidth and indicates that the port can be configured to drop one or multiple TUG-3s.
The STM-N Aggregate units drop TU-12s/VC-12s through TIFports (TIF is a TN1Ue Intermediate Format
multiplex level). Each TIFport is capable of dropping a maximum of seven TU-12s/VC-12s. Each STM-N
Aggregate unit has three TIFports so a maximum of 21 TU-12s/VC-12s can be dropped through them.
Each TIFport can be configured for either the TU-12 mode of operation or the TU-11 mode of operation.
The TU-12s selected for dropping through a TIFport in the TU-11 mode are converted to TU-11s. The
TU-12s selected for dropping through a TIFport in the TU-12 mode are dropped unchanged. If more than
three TIFports are required at a node, a TUG-3 unit can be connected to a CBW/TUG-3 port (provides
additional three TIFports). Thus, in the extreme case where one TUG-3 unit is connected to each CBW
port, the STM-1 Aggregate unit can drop a maximum of 21+(21x2)=63 TU-12s while the STM-4 and STM-
16 Aggregate units are capable of dropping a maximum of 21+(5x21)=126 TU-12s.
Regardless of its capacity, a TN1Ue ring network operates as an SDH ring with SNC protection (so called
SNC-DPRing). This means that protection switching for tributary signals is carried out at the respective
(VC-12/VC-11 or VC-3) path level. Protection switching for wideband and narrowband applications takes
place in the TU-1 level units. For broadband applications, protection switching takes place in respective
TUG-3 level interface units (ETHER-1000, ETHER-100).
2.2 TU-1 Level Units

Traffic dropped through the TIFports is processed by TU-1 level units (also called TIF-level units). The
type of the TU-1 level unit connected to a TIFport depends on the type of traffic carried in the TU-1s being
dropped on the port. The TU-1 level units are listed in Table 2.
1 In this manual, the term "dropping" assumes both adding and dropping unless specified otherwise.

TN1-86400-400PS
Issue 9.0
May 2017
Page 13
Unit Required Number of TU-12s/TU-11s Use

TIFport mode
T1/E11 TU-12 Up to 7 (one per provisioned Adding and dropping E1 (2,048 kb/s) signals
E1 interface)
CMUX TU-11 Up to 4 (one per Interfacing 64 kb/s channel units (adding and
provisioned CBUS port) dropping narrowband applications)
CDAX TU-11 Up to 7 Same as CMUX plus originating/terminating
channelized E1 signals. 64 kb/s channels can be
cross-connected between TIFport TU-11s, E1
signals and 84 kb/s level interface units.
ETHER-10 TU-11 Up to 7 Adding and dropping Ethernet signals
Tie TU-12 Up to 7 Passing TU-12 traffic from one ring/linear network
to another
Table 2: TU-1 Level Units
At a node in a ring network, the TU-1 level units are equipped in pairs (Figure 3) and are installed in
adjacent shelf slots. One unit is sending/receiving traffic through the left STM-N Aggregate unit and one
through the right STM-N Aggregate unit. In the outgoing direction, traffic is bridged and sent both ways
around the ring, while in the incoming direction one or the other signal is selected based on its health and
user-programmable priority. If the online (priority) path is lost, the protection switching occurs within less
than 3 ms. Since ETHER-10 units handle traffic that can be of point-to-multipoint nature, their protection
switching algorithm is more complex and does not require priority selection.
STM-N L R STM-N
Pass-Through
STM-N Aggregate Traffic STM-N Aggregate
TIFports
#1 #2 #3 #1 #2 #3
7 TU-11s
CASCADING
L R L R L R
ETHER ETHER T1/E1 T1/E1
CMUX CMUX (max (max
10 10
(max (max 7xTU-1) 7xTU-1)
(max (max
4xTU-1) 4xTU-1)
7xTU-1) 7xTU-1)
CBUS-P E1-7 ...

CBUS-Q
E1-2
CBUS-R
CBUS-S E1-1
10/100Base-TX
1 TU-11 CBUS-S
Ch 1 Ch 7 Ch 24
4W LS
E&M Data DTT
Protection switching = 3 ms
Figure 3: TU-1 level units at a ring node
1 T1 refers to the 1.544 Mb/s primary multiplex signal used in North America. The T1/E1 unit does not support T1
mode when used in a TN1Ue system.

TN1-86400-400PS
Issue 9.0
May 2017
Page 14
In order to optimize/maximize utilization of TIFport capacity, two (pairs of) TU-1 level units may be
cascaded on the same TIFport (Figure 3) as long as their required TIFport modes of operation are the
same (either TU-11 or TU-12). Thus, a T1/E1 unit can only be cascaded with a Tie unit or another T1/E1
unit whereas a CMUX unit can only be cascaded with a ETHER-10, CDAX or another CMUX unit. Each
cascaded unit (pair) uses different TU-11s/TU-12s on the TIFport to which they are both connected.
2.3 TUG-3 Level Units

The TUG-3 level units are the ones whose line side connects to STM-1/STM-4/STM-16 Aggregate units’
CBW ports. The TUG-3 level units are listed in Table 3.
Unit Number of TUG-3s Use

ETHER-1000 Up to 24 (TU-3 Adding and dropping Ethernet signals via an integrated Ethernet Layer-2
structured) switch
ETHER-100 Up to 6 (TU-3 Adding and dropping Ethernet signals (may be equipped with multiport
structured) Ethernet Layer 2 switch)
TUG-3 1 (TU-12-structured) Providing three additional TIFports at the node
Table 3: TUG-3 Level Units
At a node in a ring network, the TUG-3 units are equipped in pairs. Since ETHER-1000 and ETHER-100
units handle traffic that may be of point-to-multipoint nature, their protection switching algorithm does not
require any priority selection.
STM-16 Pass-Through Traffic STM-16

L R
CBW-F CBW-F
ETHER-1000
CBW-E (up to 24 TU-3s) CBW-E
CBW-D LAYER 2 SWITCH CBW-D

…
STM-16 CBW-C CBW-C STM-16
10/100/1000 Mbps Ethernet
Aggregate Aggregate
CBW-B CBW-B
CBW-A CBW-A
ETHER-100
(up to 6 TU-3s)
LAYER 2 SWITCH
…
TIFports 10/100 Mbps Ethernet TIFports
#1 #2 #3 #1 #2 #3
L R
TUG-3 TUG-3
TIFports TIFports
#1 #2 #3 #1 #2 #3
Figure 4: TUG-3 level units at a ring node

TN1-86400-400PS
Issue 9.0
May 2017
Page 15
2.4 64 kb/s Level Units

The 64 kb/s level units provide interfaces for narrowband applications i.e. the applications requiring one or
more 64 kb/s channels. These interface cards address a variety of voice, data, digital telemetry and
teleprotection applications and are listed in Table 4.
Group Unit No of Interface

channels
4W VF E&M 1 or 4 4-wire, with or without E&M signalling
2W VF FXO 4 2-wire; FXO loop-start or FXO ground-start signalling
Voice Frequency 2W VF FXS 2 2-wire; FXS loop-start, FXS ground-start or PLAR signalling
(VF) Units 2W VF E&M 1 2-wire with or without E&M signalling
4W VF 1 orderwire 4-wire, point-to-multipoint
Partyline channel
Data-LS 1 Asynchronous RS-232 (V.24); up to four 9.6 kb/s, or two 19.2
kb/s, or one 38.4 kb/s data signal plus four 300 b/s control lines
Data-PTM 2 Asynchronous RS-232 (V.24); point-to-multipoint data up to
19.2 kb/s
Data Units
Data-G703 1 G.703; 64 kb/s
Data-Nx64 1 to 12 V.35; one N x 64 kb/s signal (N=1 to 12)
Optionally equipped with Ethernet bridge for point-to-point
Ethernet communication up to 768 kb/s.
Contact I/O 1 Allows up to 16 external (foreign) contacts (open/closed) to be
Digital Telemetry replicated from one node to another; each set of four contact
circuits is configurable for inputs or outputs
Data-Nx64F 1 to 12 Multimode optical interface per IEEE C37.94
Teleprotection
DTT 1 Direct Transfer Trip; up to two transmit and two receive trip
Units
circuits
Table 4: 64 kb/s Level Units
As indicated in Figure 2 and Figure 3, the line side of each 64 kb/s level unit, with exception of 4W VF
Partyline unit, connects to a 64 kb/s channel bus (CBUS) extended from either a CMUX or CDAX unit
drop port. Multiple 64 kb/s level units can be connected to the same CBUS port as long as they are
configured for different 64 kb/s channels.
In the case of CMUX unit, the 64 kb/s level units connected to the same CBUS port are mapping/
demapping data to/from their respective channels on the same VC-11/TU-11. A CMUX unit CBUS port
can be programmed to drop all 64 kb/s channels at the same node or to have each 64 kb/s channel
individually dropped. In the latter case each channel may be dropped at a different node, which typically
ensures better bandwidth utilization; however, this is paid by slower protection switching time and
extended propagation delays.
If a CDAX unit is used, the user has more flexibility in a sense that the 64 kb/s level units on the same
drop port can be connected to different channels on different VC-11/TU-11s or hairpinned to different
channels on drop ports in E1 mode.
2.5 Supporting Units

The units shown in Figure 5, with exception of the STM-N Aggregate units, are not directly involved in
handling customer traffic.
Power units provide voltage conversion between the station battery (48 VDC) and a TN1Ue node. Each
shelf is normally equipped with two power units for redundancy purposes. Additional Power units may be
accommodated if required.

TN1-86400-400PS
Issue 9.0
May 2017
Page 16
CS Service unit (CSSU) provides summary alarm status of the node, access for Orderwire and/or 4W VF
Partyline units as well as connections for the NMS. The unit supports enhanced network management
functions including advanced cyber security. It can also monitor as many as four external contact inputs
and report their status to the NMS. The CSSU is capable of accessing up to 7 overhead channels that
may be used by Orderwire and/or 4W VF Partyline units so up to 7 independent Orderwire and/or 4W
Partyline systems can be accessed at a node.
Sync References
(2048 kHz or E1)
STM-N External STM-N

(N x 155.52 Mb/s) Sync (N x 155.52 Mb/s)
Unit
(optional)
Left/West Sync Right/East

48 VDC
Through-Traffic
STM-N STM-N
Power
Aggregate Aggregate
Unit
Unit Unit
CS Service Unit
(CSSU)
Add/Drop Add/Drop
Traffic ALM OW NMS Traffic
(to other units) (to other units)
Office Network
Alarms Management
Interface
Orderwire Unit
(optional)
Figure 5: TN1Ue units carrying no traffic (with exception of STM-N Aggregate units)
Orderwire unit provides a multipoint voice communication channel between any two or more sites in the
TN1Ue system intended for maintenance personnel use.
The External Sync unit is typically used in the following applications:

 To synchronize the TN1Ue network from an external reference clock signal (a 2048 kHz signal or a
framed E1 that may carry traffic). Applications with backup external sync nodes in the same or different
rings are also supported.
 To synchronize external (non-TN1Ue) equipment to the TN1Ue network timing reference. This could
be a 2048 kHz signal or a framed or unframed E1 signal carrying no traffic.
 To flexibly pass timing and Synchronization Status Message (SSM) from one TN1Ue ring/linear
network to another in either direction.
 To filter the accumulated jitter using an external SASE (Stand-Alone Synchronization Equipment) in
TN1Ue networks with large number of nodes.
When used, a pair of External Sync units is recommended for redundancy.

TN1-86400-400PS
Issue 9.0
May 2017
Page 17
2.6 Paddleboards
Most of the TN1Ue units are used with the corresponding unit-specific paddleboard installed in the rear of
same shelf slot position. Paddleboards provide customer connections and/or connections to other TN1Ue
units. The units installed in pairs share a common paddleboard.

TN1-86400-400PS
Issue 9.0
May 2017
Page 18
THIS PAGE INTENTIONALLY LEFT BLANK

TN1-86400-400PS
Issue 9.0
May 2017
Page 19
3 FEATURES
3.1 Introduction
The TN1Ue system is an integrated SDH add & drop multiplexer capable of interfacing a variety of drop
equipment signals. The system supports a number of configurations as described in Section 7. Sections
4 and 5 provide a brief overview of the common and interface units supported by the system.
The system is modular in design to allow for simple capacity upgrades and adding new modules to the
existing in-service systems. All units are housed in the equipment shelves that mount in a standard 19”
rack. The shelves are either 5 rack units in height (Common Equipment Shelf) or 4 rack units in height
(Expansion Shelf).
All units are powered from the +5 VDC shelf bus. Power units convert station battery input to +5 VDC.
Station battery is also required on all DTT keying loops and DTT test panels.
3.2 SDH Conformance
3.2.1 Background and History
In 1988 ITU-T (former CCITT) approved a standard to address multi-vendor environments, synchronous
networking, enhanced OAM&P and future transport requirements for LAN, HDTV etc. The synchronous
multiplexing technique was coined SDH for Synchronous Digital Hierarchy.
The Phase 1 standard defined:
 A base rate and format

 A hierarchy of rates and formats based on synchronous multiplexing of the base
 Overhead layering, definitions, and locations
 Frequency justification and loading of payloads
Phase 2, released in 1996, provided further definition in OAM&P, Automatic Protection Switching (APS)
and additional Payload Mapping.
SDH is based on STM-1 (Synchronous Transfer Module) signal which is a basic building block for higher
STM-N rates. Higher rate SDH signals are produced by byte-interleaving N STM-1 signals to form an
STM-N signal.
Line Rate
STM Level
(Mb/s)
STM-1 155.52
STM-4 622.08
STM-16 2488.32
STM-64 9953.28
STM-256 39813.12
Table 5: SDH Hierarchy and Rates

TN1-86400-400PS
Issue 9.0
May 2017
Page 20
The figure below details the SDH multiplexing structure. It includes both SONET (Synchronous Optical
Network) multiplexing route (used in North America and Japan) and ETSI multiplexing route (used in the
rest or the world).
xN x1
STM-N AUG AU-4 VC-4 C-4 140 Mbit/s
x3
x3 x1
TUG-3 TU-3 VC-3
x7
45 Mbit/s
AU-3 VC-3 C-3
34 Mbit/s
x7 x1
TUG-2 TU-2 VC-2 C-2 6 Mbit/s
Pointer processing
x3
Multiplexing
TU-12 VC-12 C-12 2 Mbit/s

Aligning x4
Mapping
SONET specific options VC-11 C-11 1.5 Mbit/s

TU-11
ETSI specific options
Figure 6: SDH multiplexing structure
3.2.2 TN1Ue System
The TN1Ue System is an integrated SDH drop and insert multiplexer operating at 155.52 Mb/s (STM-1),
622.08 Mb/s (STM-4) or 2488.32 Mb/s (STM-16) rate. The system provides an STM-N optical interface
on the line side per ITU-T Recommendation G.707. For mapping and multiplexing tributary signals, the
TN1Ue uses VC-11s, VC-12s, VC-3s and ETSI multiplexing route (Figure 6).
In ring configurations, the system supports unidirectional and bidirectional path protection switching
schemes per ITU-T Recommendation G.841.
A node in a TN1Ue system can be synchronized from an internal clock, from a line signal, or externally,
from a collocated TN1Ue node belonging to another ring or linear system. Synchronization is covered in
more detail in Section 8.
The TN1Ue provides access to both E1 and E2 orderwire channels (ITU-T G.707).
OAM&P functions are carried in the overhead bytes of the STM-1 frame and utilized by the TN1Ue
Network Management System.
3.3 Main Design Specifications

The TN1Ue system has been designed to operate in harsh environments. This includes temperature
extremes as well as SWC (Surge Withstand Capability), RFI (Radio Frequency Interference) and EMI
(Electromagnetic Interference).

TN1-86400-400PS
Issue 9.0
May 2017
Page 21
Operation is guaranteed over the extended ambient temperature range of -10 to +60 ºC.
All external metallic interfaces to the system, be they signal (voice, data), power or alarm & control are
capable of withstanding fast surge voltage transients of 4000 volts.
The system meets ETSI EN 300386-2 and CENELEC EN 50082-2 specifications for EMC and ANSI/IEEE
C37.90.1 spec for SWC. The system also meets the IEC 60950 specification for Safety on Information
Technology Equipment as well as EN 60825-1 and EN 60825-2 for Safety of Laser Products.
3.4 Local and Remote Monitoring and Configuration

All units with software configurable settings, except for the CSSU in Secure mode, can be individually
monitored and configured locally through the unit's RJ-11 Craft Interface (CI) using VistaNET software.
VistaNET operates on a Microsoft Windows-based PC . VistaNET link to the CI port operates at 9600 b/s
using asynchronous RS-232 interface i.e. one of the serial (COM) ports on the PC. VistaNET
communicates to the unit’s microprocessor to display unit’s status and various read-only parameters and
to set unit’s configurable parameters, The user must authenticate to VistaNET in order to make any
configuration changes on the unit.
The user can also access all unit information through the VistaNET network management connection
running through a serial or Ethernet connection to the CSSU. The TN1Ue network management features
are covered in Section 6. A VistaNET PC connected to a CSSU allows the user to monitor and configure
all the nodes in the same NMS domain from any node. Configuration changes are permitted only if the
user has successfully authenticated himself to VistaNET and, in the case the CSSU in Secure mode, to
the CSSU itself. Visibility of nodes is down to the 64 kb/s level which includes monitoring, configuration
and alarm reporting. Manual path switching is also available.
Testing of VC-1/VC-3 paths and BER monitoring are some of the maintenance functions supported by
VistaNET.
3.5 System Redundancy and Availability

Circuit availability and reliability are key elements in the TN1Ue design. Power units can be paralleled on
the same shelf and across multiple shelves. Route diversity is achieved in a ring configuration by
assigning both priority and backup paths. This ensures that if a common unit such as an STM-16
Aggregate or CMUX fails, or a fibre is broken, traffic is still maintained between the drop sites. Due to the
importance of propagation delay between sites for teleprotection traffic, the design offers extremely fast
switching time (<3 ms) between route diversity fibre paths.
In a TN1Ue ring, either unidirectional or bidirectional switching algorithm can be selected for each
protected VC-1 path. By default, the protection switching is unidirectional, i.e. in case of a unidirectional
failure (e.g single fibre cut), the unaffected direction of transmission is not switched. However, if there is a
requirement to ensure protection switching of both transmission directions (even in the event of
unidirectional failure), a bidirectional switching algorithm can be enabled. This is an important feature for
applications where both directions of transmission must experience the same (or nearly the same) delay
even in the case of a ring failure (e.g. some teleprotection applications).
Note that in either case the protection switching is revertive, i.e. the traffic is switched back to the priority
path when the priority path is restored.

TN1-86400-400PS
Issue 9.0
May 2017
Page 22
FIBRE OPTIC PAIR (STM-N)
FIBRE OPTIC PAIR (STM-N)
P S S P P S S P
C C S C C S
O T T O O T T O
INTERFACE M M E INTERFACE M M E
W M M W W M M W
UNITS U U R UNITS U U R
E - - E E - - E
X X V X X V
R N N R R N N R
COMMON EQUIPMENT SHELF COMMON EQUIPMENT SHELF
Figure 7: Two-node ring
The above figure shows a two-node system operating in a ring configuration. If an equipment failure
occurs in a Power, CMUX or STM-N Aggregate unit, traffic is still maintained. If a fibre pair is damaged,
traffic is also maintained. A more detailed description of configurations is provided in Section 7.
3.6 Security and Dependability Features

Interface units unique to utilities (power, industrial, transit, etc.) include Direct Transfer Trip (DTT) units,
Data-Nx64F units and Contact I/O units. All of the above plus some data and VF units often used for
teleprotection utilize an addressing technique to ensure the correct transmit/receive pair are
communicating. In essence, no transmitter can talk to an incorrect receiver. All units can be configured
with a binary address of 1 to 4095. This addressing scheme is done through software, which, on the
receive units, will also display the configured transmitter address. A sample VistaNET view for a DTT unit
is shown in Figure 8. Note the BC96 addressing fields.
If for any reason the address is corrupted or not

received at all, an alarm is initiated and the circuit
functions are disabled (e.g. no false trip signals for
DTT units are processed).
The above mentioned units also have numerous

self-check features. Input keying loops on DTT units
are continuously self-tested.
Figure 8: Security features

TN1-86400-400PS
Issue 9.0
May 2017
Page 23
3.7 Alternate Traffic Routing

Faced with new security requirements and regulations, a growing number of network operators are
implementing backup control centres to boost their immunity to various potential threats. The
telecommunications network must be able to quickly reroute critical voice and data traffic to the backup
control centre in the event of a main control centre outage.
The Alternate Traffic Routing (ATR) feature allows the network administrator using VistaNET to activate
the appropriate pre-configured traffic routing alternative in a fast and reliable fashion when a catastrophic
facility outage occurs. The inactive (offline) traffic routing images are stored in the Flash memory of
STM-N Aggregate units and can be modified either locally or remotely with no effect on current traffic.
This allows for fast swapping of traffic routing images with simple VistaNET intervention thus eliminating
human errors in stressful situations.
Figure 9: Swapping normal and alternate configuration images

TN1-86400-400PS
Issue 9.0
May 2017
Page 24
3.8 Modular Design and Expansion

The TN1Ue system was designed such that interface units could be easily added as system requirements
grow. All interface units can be installed in any of the Expansion Shelf slots 2 to 14 or Common
Equipment Shelf slots 2 to 11. CBUS extensions are easily performed through modular plugs and
connectors. A variety of extension cables allow the user to add more shelves and equipment to any
existing node.
Each interface unit has a corresponding interconnect paddleboard which provides the necessary
connections for the customer interface.
Figure 10: Common Equipment Shelf (rear view)
The same shelf is used whether the system operates at the STM-1, STM-4 or STM-16 line rate. External
cooling (i.e. fans) is not required.
All TN1Ue units can be installed or removed from the shelf with shelf power applied.

TN1-86400-400PS
Issue 9.0
May 2017
Page 25
4 COMMON EQUIPMENT UNITS
4.1 Introduction
The components that make up a TN1Ue system can be divided into three categories: equipment shelves,
common equipment, and interface units. All systems and nodes will have a combination of the above
three.
This section contains information on the shelves and common equipment. Section 5 provides a brief
overview of the interface units supported by the system.
Common equipment units include Power units, STM-N Aggregate unit(s), CSSU, External Sync unit(s),
TUG-3 unit(s), CMUX unit(s), CDAX unit(s), Tie unit(s) and Orderwire unit(s). The common equipment
requirement at a node depends on the system configuration details and amount of traffic being dropped at
the node.
The TN1Ue equipment shelves (Common Equipment Shelf and Expansion Shelf) provide housing for
TN1Ue common and interface units and their respective paddleboards. They mount in a standard 19”
rack. The Common Equipment Shelf can accommodate all types of units offered with the TN1Ue
product. The Expansion Shelves are needed only to expand the capacity of the Common Equipment
Shelf when a lot of interface units for the customer drop equipment are to be installed at the node.
All common equipment and interface units are powered from the +5 VDC shelf bus. Power units convert
station battery input to +5 VDC. Station battery voltage is also required for the operation of Direct Transfer
Trip (DTT) keying loops and DTT Test Panels.
Redundant Power units are recommended in each shelf so in the case of single unit failure, one unit can
supply the +5 VDC required for the entire shelf. The power buses of up to three shelves (six Power units)
may be paralleled. In that manner all paralleled Power units share the power load on the respective
shelves. In addition to providing additional redundancy, this feature must be used in cases when the
power consumption of all units at a single shelf exceeds the power that can be provided by a single Power
unit.
A typical rack layout is provided in Figure 11. It shows some of the above mentioned units along with
some interface units.
The open architecture of the TN1Ue provides maximum flexibility for network modifications and growth.
New features and interfaces are easily integrated with existing systems.
The following descriptions are intended to provide the reader with the basic functionality of equipment
shelves and each common equipment unit. All units are covered in detail in their associated Technical
Practice and Installation Manuals. These manuals can be obtained through GE Multilin.

TN1-86400-400PS
Issue 9.0
May 2017
Page 26
FIBRE TO: SITE B FIBRE TO: SITE D
MODE TDM TOPOLGY L RING: 1 R

slot 1 TO 7 CH 1
CBW-4 “BB" NODE: 1 “AA"
1 RING
TU 15x TO 21x 2 RING SYNC MODE
3 LINE-R NORMAL, LEFT
PAIR 1 CBW
4 -
PORT
L R
48 V D CBW PORT E 48 V
TIFPORT 1
PWR BLANK BLANK ETHER-10 ETHER-10 E-100 BLANK ETHER-1000 BLANK OW STM-16 CSSU STM-16 PWR
CBUSL/R slot TU MODE Port

L/R slot TU E1 L/R slot TU
CBUS-S (PAIR 4) TU-1
S - 1 1
- -
1x SHR
- 1 L 1 7x
CH 5 CH 4 CH 3 CH 2 CH 1 R R 2 10x STD 2 - - - 2 R 2 8x
R R L L R 3 - - - 3 R 3 9x
Q L 3 14x STD 4 - - - 4 L 4 12x
SITE H SITE D SITE B SITE B SITE H - - -
- - - - - 5 L 5 3x 5
TX: 0158 CH 4 6 R 6 5x 6 - - -
RX: 0815 L PAIR 4 7 - - - 7 - - -
48 V CONTACT SITE B L R L PAIR 3 R L PAIR 2 R 48 V
TIFPORT 3 TIFPORT 2 TIFPORT 2
PWR BLANK BLANK I/O 2W TO 2W FXS 4W 4W CMUX CMUX TIE TIE T1/E1 T1/E1 PWR
CBUS-R (PAIR 4) TU-10: SITE G CBUS-Q (PAIR 4) TU-14: SITE B
CH 1 CH 2 CH 3-6 CH 7 CH 1 CH 1
TX: 0201 TX: 0301 TX: 0401

RX: 0102 RX: 0103 RX: 0104 BC96 TX: 0023 BC96 RX: 0032
48 V LS Nx64F NX64 G703 48 V

PWR DATA DATA DATA DATA BLANK BLANK BLANK BLANK BLANK DTT TX DTT RX PWR
TRANSMIT RECEIVE
CCT1 CCT2 CCT3 CCT4 CCT1 CCT2 CCT3 CCT4
86429-M2 DTT TEST PANEL
J1 J2 J3 J4 J5 J6 J7 J8 J9 J10 J11 J12 J13 J14 J15
Figure 11: Typical rack layout
4.2 Equipment Shelf

Both the Common Equipment Shelf (B86430-28) and Expansion Shelf (B86430-421) provide 15 shelf slot
spaces, power bus, and CBUS for 64 kb/s channel units. The Common Equipment Shelf occupies 5 rack
units while the Expansion Shelf occupies 4 rack units. Both shelves mount in a standard 19" rack.
Flexible architecture of the Common Equipment Shelf allows housing of various units, from STM-N
Aggregate units down to 64kb/s interface units, on the same shelf. Expansion Shelves are used only to
provide additional shelf space when needed.
Most of the TN1Ue units are installed with the corresponding unit-specific paddleboard installed at the rear
of the shelf, in the same slot position. The units installed in pairs share a common paddleboard.
Various cables provide quick, efficient connections for all common equipment units.
1 This shelf superseded legacy B86430-22 Expansion Shelf.

TN1-86400-400PS
Issue 9.0
May 2017
Page 27
LENTRONICS LENTRONICS LENTRONICS LENTRONICS LENTRONICS

MULTIPLEXERS MULTIPLEXERS MULTIPLEXERS MULTIPLEXERS MULTIPLEXERS
LOCAL LOCAL
NMS
RCV RCV
RCV YEL ALM RCV YEL ALM

VC-4 VC-4
MINOR MAJOR
STM-4 STM-4
ALARM ALARM ALARM
ACK ACK ACK
STATUS C.I. C.I. C.I. STATUS
B86431-42 (48V) B86417-21 B86434-11 B86417-21 B86431-42 (48V)

POWER UNIT STM-4 UNIT CS SERVICE UNIT STM-4 UNIT POWER UNIT
Figure 12: Common Equipment Shelf (front view with front cover removed and
Power Units, STM-4 Aggregate Units and CSSU installed)
OPENINGS FOR LEFT AGG. UNIT CBW /

SYNC SYNC TUG-3 PORT EXTENSIONS TO TUG-3,
STM-N UNIT STM-N UNIT SIGNAL SIGNAL VMAPPER-40 AND ETHER-100 UNITS RIGHT TU-1 LEVEL LEFT TU-1 LEVEL
TIFPORT#1 (RIGHT) TIFPORT#1 (LEFT) POWER BUS EXTENSION UNIT TIFPORT UNIT TIFPORT
FROM TO IN ADDITIONAL COMMON SHELF. (TO UPPER ADJACENT
AND AND OTHER OTHER (OPENINGS FOR RIGHT PORTS ARE (FROM RIGHT STM-1 (FROM LEFT STM-1
TIFPORT#2 (RIGHT) TIFPORT#2 (LEFT) SHELF) UNIT UNIT
RINGS RINGS SHOWN WITH BLANKING PLATES.)
TIFPORT#1/#2/#3) TIFPORT#1/#2/#3)
LEFT TU-1 LEVEL RIGHT TU-1 LEVEL

STM-N UNIT 087-86430-90 JUMPER UNIT TIFPORT UNIT TIFPORT
O/W BUS EXTENSION
TIFPORT#3 SUBASSEMBLY (TO/FROM LEFT (TO/FROM RIGHT
TO EXPANSION SHELF
(RIGHT + LEFT) (CBUS EXTENDER) CASCADED CASCADED
TU-1 LEVEL UNIT) TU-1 LEVEL UNIT)
SHELF GROUND
(TO LOWER ADJACENT POWER BUS EXTENSION POWER BUS EXTENSION CBUS EXTENSION TO
SHELF GROUND (TO LOWER ADJACENT (TO LOWER ADJACENT EXPANSION SHELF
CONNECTION) SHELF) SHELF)
Figure 13: Common Equipment Shelf (rear view)

TN1-86400-400PS
Issue 9.0
May 2017
Page 28
CBUS FROM CMUX UNIT OR RIGHT TU-1 LEVEL LEFT TU-1 LEVEL CBUS FROM CMUX UNIT OR
EXTENSION FROM COMMON UNIT TIFPORT UNIT TIFPORT EXTENSION FROM COMMON POWER BUS EXTENSION
OR ANOTHER EXPANSION (FROM RIGHT STM-N (FROM LEFT STM-N OR ANOTHER EXPANSION (TO UPPER ADJACENT
SHELF (TRACED TO SLOT 14) UNIT TIFPORT#1/#2/#3) UNIT TIFPORT#1/#2/#3) SHELF (TRACED TO SLOT 8) SHELF)
CBUS TIF IN TIF IN TIF IN TIF IN TIF IN TIF IN TIF IN

[14] [14] R [12] R [10] R [7] R [10] R [5] R [3] R
CBUS
[7]
TIF IN TIF IN TIF IN TIF IN TIF IN TIF IN

+5V [R] +5V [L]
[13] L [11] L [9] L [8] L [4] L [2] L
TIF EXT TIF EXT TIF EXT TIF EXT TIF EXT TIF EXT
[14] R [12] R [10] R [7] R [5] R [3] R
CBUS CBUS
[8] [1]
TIF EXT TIF EXT TIF EXT TIF EXT TIF EXT TIF EXT
+5V [R] +5V [L]
[13] L [11] L [9] L [6] L [4] L [2] L
SHELF GROUND RIGHT TU-1 LEVEL LEFT TU-1 LEVEL CBUS FROM CMUX UNIT OR
(TO LOWER UNIT TIFPORT UNIT TIFPORT CBUS FROM CMUX UNIT OR EXTENSION FROM COMMON
POWER BUS EXTENSION POWER BUS EXTENSION
ADJACENT SHELF (TO/FROM LEFT (TO/FROM RIGHT EXTENSION FROM COMMON OR ANOTHER EXPANSION SHELF
(TO LOWER ADJACENT (TO LOWER ADJACENT
GROUND CASCADED CASCADED OR ANOTHER EXPANSION (TRACED TO SLOT 2 VIA CBUS
SHELF) SHELF)
CONNECTION) TU-1 LEVEL UNIT) TU-1 LEVEL UNIT) SHELF (TRACED TO SLOT 7) JUMPER BETWEEN SLOTS 1 AND 2)
Figure 14: Expansion Shelf (rear view)
Only a few unit types have their mandatory shelf slot positions. The Common Equipment Shelf slot
positions 1 and 15 are reserved for the Power units, positions 12 and 14 for the STM-N Aggregate or
TUG-3 units1, while the position 13 is reserved for the CSSU2. The rest of the Common Equipment Shelf
can flexibly accommodate all other unit types including Orderwire unit, External Sync units, TU-1 level
units and all types of interface units. When TUG-3 units are required, each pair of TUG-3 units is installed
in a separate Common Equipment Shelf.
The Expansion Shelf slot positions 1 and 15 are reserved for Power units while positions 2 to 14 can be
equipped with TU-1 level units, 64 kb/s channel units and External Sync units.
Pairs of TU-1 level units may be inserted in Common Equipment Shelf slot positions 2/3, 4/5, 6/7, 8/9, and
10/11, or in Expansion Shelf slots 2/3, 4/5, 6/7, 9/10, 11/12, and 13/14.
A CBUS (Channel Bus) brings the traffic from a CMUX or CDAX unit drop port (S, R, Q or P)3 to 64 kb/s
level units. Each of these drop ports can add & drop a maximum of 24 64kb/s channels. In the case of
CMUX unit the channels that appear on the given drop port are from the same TU-11, while in the case of
CDAX unit they can be from different TU-11s or even from the drop ports in E1 mode. The drop port S is
automatically connected to the shelf upon insertion of (a pair of) CMUX/CDAX unit(s) so the first 64 kb/s
level unit connected to this port can be inserted into the shelf slot immediately to the left of the
CMUX/CDAX unit (pair). A CBUS may be extended along the shelf by using CBUS jumper
subassemblies (CBUS jumpers) and to another shelf by using an appropriate cable. Each Expansion
Shelf can support up to two extendable CBUSes. If future extensions of the CBUSes are not required, the
Expansion Shelf can support up to four CBUSes.
Figure 15 shows a typical backplane cabling example for a ring node with a pair of T1/E1 units and a pair
of Tie units cascaded and connected to the TIFport #1.
1 The first Common Equipment Shelf at the node accommodates STM-N Aggregate units. If TUG-3 units are
needed, an additional Common Equipment Shelf is installed. Each pair of TUG-3 units requires a separate Common
Equipment Shelf.
2 The slot position 13 is equipped with a blank unit if the positions 12 and 14 are equipped with TUG-3 units.
3 The CMUX unit's drop ports are actually labelled CBUS-S, CBUS-R, CBUS-Q and CBUS-P.

TN1-86400-400PS
Issue 9.0
May 2017
Page 29
Each shelf also has connections to extend the power bus between shelves. This allows Power units in
different shelves to be connected in parallel to ensure maximum redundancy and load sharing.
Figure 15: Backplane cabling example
4.3 Power Unit
LENTRONICS The B86431 Power unit provides the interface

MULTIPLEXERS between a customer-supplied 48 VDC station battery
and a TN1Ue node. The unit provides a regulated
+5 VDC supply to the other units in the shelf by
converting the station battery voltage to +5 VDC.
Each B86431-42 Power unit can be loaded with a
maximum of 18 W on permanent basis.1
The Power unit can be paralleled with another Power

unit in the same shelf and with the Power units of up
to two other shelves to provide redundancy in the
case of a single unit failure. A maximum of six Power
units can be paralleled.
All connections to the unit are made on the

STATUS paddleboard (Figure 17).
B86431-42 (48V) The Power unit can be installed in the 1st or 15th slot
POWER UNIT of either the Common Equipment Shelf or Expansion
Shelf. Typically, both slots are equipped so in the
Figure 16: Power Figure 17: Power Unit event of a single Power unit failure, the shelf power is
Unit Front Panel Paddleboard maintained. If necessary, an additional (third) Power
unit can be installed in the shelf.
The Power unit does not have a craft interface since there are no configurable options on the unit.
1 The maximum allowed permanent load for the old-generation Power unit (B86431-02) was 18 W.

TN1-86400-400PS
Issue 9.0
May 2017
Page 30
An alarm relay and front panel red LED provide indication of abnormal Power unit operation. The alarm
relay terminals NO ("normally open") and C ("common") of all Power units at the node are normally wired
to the respective port on the CSSU paddleboard so that the CSSU can monitor and report their status.
4.4 STM-16 Aggregate Unit

LENTRONICS The B86419 STM-16 Aggregate unit provides the STM-16 (2488.32 Mb/s)
MULTIPLEXERS transmit and receive optical interface between a TN1Ue node and adjacent node
TIMING in the same ring or linear network. The unit provides hardware and software
LOCAL interfaces to the CSSU, External Sync units, TUG-3, ETHER-1000, ETHER-100
and all TU-1 level units.
RCV
The STM-16 Aggregate unit occupies one shelf slot position in a Common
RCV YEL ALM
Equipment Shelf and must be installed in either the 12th or 14th position in the shelf
VC-4
(both locations are equipped at a ring node or at an add/drop node in a linear
STM
-16
network).
ALARM
The unit is equipped with an SFP (Small Form-factor Pluggable) optical
ACK transceiver module available in many different options depending on the desired
reach (IR, LR, ELR), wavelength (1310nm, 1550nm), fibre type (SMF, MMF),
number of fibres (dual-fibre or single-fibre interface ) etc. Typically, dual-fibre
C.I.
transceivers are equipped with LC connectors while the single-fibre ones are
equipped with an SC connector. The unit accepts only transceivers equipped with
B86419-21 DMI (Diagnostic Monitoring Interface) to allow for in-depth transceiver monitoring.
STM-16 UNIT
The SFP transceivers installed have guaranteed minimal system gain of
Figure 18: STM- 13dB@1310nm for the B86419-21/AA unit option, 26dB@1310nm for the B86419-
16 Aggregate Unit 21/BB option, 26dB@1550nm for the B86419-21/CC option and 31dB@1550nm
Front Panel for the B86419-21/EE option over the whole TN1Ue operating temperature range.
STS-48 Bypass The STM-16 Aggregate unit’s

VC-4
POH
port payload comprises sixteen
Optical VC-4s or an equivalent
STM-16 16 NxTUG-3
XCVR CBW-F
(2.488 Gb/s) LC
Connectors
14 combination of VC-4-4cs and
RSOH
.
NxTUG-3
CBW-E VC-4s. Each VC-4 can be
.
. TU-12*/ NxTUG-3 configured to carry bulk VC-4
MSOH TUG-3/ CBW-D
VC-4/
payload or three TUG-3s.
6 VC-4-4c
NxTUG-3
CBW-C Each of the TUG-3s belonging
Cross to the first four VC-4s can be
5 NxTUG-3
Connect CBW-B
4* configured to carry either one
3* NxTUG-3
CBW-A TU-3 (VC-3) or 21 TU-12s
2*
TUG-3 (VC-12s) so a maximum of
1*
3 TIF 252 TU-12s can be carried in
ports an STM-16 signal. On the
* Use of TU-12 cross-connect is
limited to first 4 VC-4s only TUG-3 Through drop side, the unit has three
port
(shelf)
TIFports and five CBW
(Configurable Bandwidth)
Figure 19: STM-16 Aggregate Unit Signal Flow Diagram
ports (Figure 19). Each CBW
port can be configured to drop various combinations of cross-connected VC-4-4cs, VC-4s, TUG-3s and/or
as many as 21 individually cross-connected TU-12s. CBW ports are available on the top of the unit, while
the TIFports are available on the shelf backplane from where they are cabled to the TU-1 level units.
Each TIFport can drop a maximum of seven TU-12s/VC-12s and it provides an interface to either one or
two cascaded TU-1 level units (of the same or different type). Each TIFport can be configured for either
TU-11 or TU-12 mode of operation. In the TU-12 mode, a TIF signal consists of seven TU-12s while in

TN1-86400-400PS
Issue 9.0
May 2017
Page 31
the TU-11 mode it consists of seven TU-11s. The conversion of TU-12s selected for dropping on a port in
TU-11 mode is in accordance with the ITU-T Recommendation G.707 (03/96, Section 10.1.6). The TU-12
mode is used for T1/E1 and Tie units while the TU-11 mode is used for CMUX, CDAX and ETHER-10
units.
When configured for 1 x TUG-3 mode of operation (21 x TU-12 capacity), a CBW port can be used for
interfacing a TUG-3 unit (to add more TIFports). A CBW port configured for 1 x TU-3 capacity can
interface ETHER-100 units (configured for 1 x TU-3 mode).
A CBW port configured for an N x TUG-3 mode of operation (N= 4, 6, 12, 241) can be used for providing a
large bandwidth channel access for broadband applications such as 100/1000 Mb/s Ethernet wire-speed
bridging or for efficient tying of multiple TUG-3/VC-4/VC-4-4c signals and/or locally cross-connected TU-
12s between TN1Ue rings.
Normally, all through-traffic is passed to the companion STM-16 Aggregate units via the Bypass link (a 7-
wire SATA cable). The shelf through-port is used only while upgrading in-service STM-1 rings to STM-16
capacity.
The unit’s cross-connect capabilities are summarized in Figure 20.
STM-16 STM-16
TU-12s only: 2 5
LEFT RIGHT
TU-12s and/or
TUG-3/VC-4/ 1
VC-4-4cs: 1 3 4
2 3
Bypass link
(STM-16)
Port X
5 4
…

1x 2x … 21x
A B C D E Drop ports E D C B A
1 2 3 3 2 1
7 TU-12s
1 2 3
TIFports TIFports
CBW ports CBW ports
Figure 20: Types of cross-connections supported by STM-16 Aggregate unit
Figure 21 shows how these cross-connect capabilities may be utilized for efficient traffic routing between
multiple rings. The unit’s “hairpinning” feature allows the TU-12s, TUG-3s, VC-4s and VC-4-4cs from one
subtended ring to be passed to another subtended ring through the local STM-16 node.
Unit configuration and monitoring is performed through the VistaNET software. The unit's VistaNET view
consists of multiple tabs.
1 The “24 x TUG-3” mode is available for CBW ports E & F only.

TN1-86400-400PS
Issue 9.0
May 2017
Page 32
STM-4
TN1Ue
STM-4 CBW-TIE
TN1Ue TU-12 TRAFFIC
TUG-3 TRAFFIC
STM-4
VC-4 / VC-4-4c TRAFFIC
TN1Ue
STM-4
TU-12 Drop
TN1Ue 5
TU-3 Drop STM-16
TN1Ue
4
STM-16 3 STM-16
TN1Ue Foreign
3 STM-16
STM-16 3 STM-16 TN1Ue
3
TN1Ue TN1Ue
4
STM-16
TN1Ue STM-16
STM-1 TN1Ue STM-16
TN1Ue STM-16 Foreign
STM-1 TN1Ue
TN1Ue
STM-1
TN1Ue STM-16
STM-16 Foreign
STM-1 TN1Ue STM-16
STM-1 TN1Ue Foreign
TN1Ue
Figure 21: Tying traffic between STM-N rings using CBW tie links
The Main tab (Figure 22) allows the user to configure most of the unit parameters including
synchronization parameters, section trace parameters, optical alarm levels and BER thresholds and to
perform some maintenance functions. Optical receive level, laser current, PLL voltage, status of the STM-
16 signal and unit temperature are some of the parameters monitored and displayed in the Main tab.
Figure 22: STM-16 Aggregate Unit View – Main Figure 23: STM-16 Aggregate Unit View – VC-4
Tab Tab

TN1-86400-400PS
Issue 9.0
May 2017
Page 33
The VC-4 tab (Figure 23) allows the user to configure the STM-16 payload format and perform
maintenance functions on individual TUG-3/VC-4/VC-4-4c signals.
The Cross-Connect tab (Figure 24) allows the user to configure the modes of operation for CBW ports
and configure TU-12, TUG-3, VC-4 and VC-4-4c cross-connects on the unit. By default, all TU-12s, TUG-
3s, VC-4s and VC-4-4cs from the STM-16 port are connected to the Bypass link (passed through). Right
mouse click on a specific TU-12, TUG-3, VC-4 or VC-4-4c slot on a drop port opens up a menu, which
allows the user to select a TU-12/TUG-3/VC-4/VC-4-4c that will be cross-connected to the given slot.
Note that for the ports configured for N x TUG-3 mode (N=4, 6, 12, 24), the first TUG-3 slot may be
configured as TU-12-structured (see CBW-E port configuration in Figure 24).
Figure 24: STM-16 Aggregate Unit View – Figure 25: STM-16 Aggregate Unit View –
Cross-Connect Tab TIFports Tab
The TIFports tab (Figure 25) allows the user to assign TU-12s to the unit's TIFports. Only the TU-12s
cross-connected from the optical STM-16 port or CBW ports to the unit's internal Port X may be assigned
("dropped") to the unit's TIFports. The TU-12s cross-connected to the Port X but not assigned to any
TIFports are passed through the node via the shelf backplane.
Figure 26: STM-16 Aggregate Unit View – TU-12 Figure 27: STM-16 Aggregate Unit View – Errors
Status Tab Tab

TN1-86400-400PS
Issue 9.0
May 2017
Page 34
The TU-1 Status tab (Figure 26) provides status information for the TU-12s/TU-11s assigned to the unit's
TIFports.
The Errors tab (Figure 27) provides status and performance information on all SDH layers terminated by
this unit plus the status of the received Bypass signal.
The History tab (looks similar to the STM-4 Aggregate unit's History tab shown in Figure 40) allows the
user to retrieve the information on code violations registered in the Section layer of the received STM-16
signal over an adjustable time period. This period is divided in 60 time cells of equal (and configurable)
duration.
The STM-16 Aggregate unit allows for up to two firmware packages to be loaded on the unit, where only
one of them can be active (operational). The Firmware tab (Figure 28) allows the user to reboot the unit
using currently active package or switch to the alternate (currently inactive) firmware package.
Figure 28: STM-16 Aggregate Unit View – Figure 29: STM-16 Aggregate Unit View – Config
Firmware Tab Image 2 Tab
The Config Image 2 tab (Figure 29) allows the user to create and store into the unit's flash memory the
alternate image for traffic routing. The traffic routing information includes the STM-16 payload format,
cross-connections and TU-12 assignments for the TIFports. The user can swap the two images using
NMS when required.
The transmit STM-16 signal may be timed from the unit’s internal clock, from the incoming fibre, from the
shelf, or from a CBW port tied to a collocated TN1Ue node belonging to a different ring or linear system.
The shelf timing signal may be supplied by the companion STM-16 unit or introduced externally either
from a collocated STM-16 node (belonging to a different ring or linear system) or from an external
reference clock through a (pair of) External Sync unit(s) installed at the node. Refer to Section 8 for more
information on the synchronization options and synchronization distribution algorithm.
The STM-16 Aggregate unit may be used as a plug-in replacement for STM-1 and STM-4 Aggregate units
to upgrade existing TN1Ue networks with STM-1/STM-4 capacity to STM-16 capacity1. Ring networks
can be upgraded while the system is in service.
1 If fibre-optic lines permit (i.e. optical budget, fibre type etc.).

TN1-86400-400PS
Issue 9.0
May 2017
Page 35

LENTRONICS The B86417 STM-4 Aggregate unit provides the STM-4 (622.08 Mb/s) transmit
MULTIPLEXERS and receive optical interface between a TN1Ue node and adjacent node in the
TIMING same ring or linear network. The unit provides hardware and software interfaces
LOCAL to the CSSU, External Sync units, TUG-3, ETHER-1000, ETHER-100 and all TU-1
level units.
RCV
The STM-4 Aggregate unit occupies one shelf slot position in a Common
RCV YEL ALM Equipment Shelf and must be installed in either the 12th or 14th position in the shelf
VC-4
(both locations are equipped at a ring node or at an add/drop node in a linear
STM-4 network).
ALARM
The unit is equipped with an SFP (Small Form-factor Pluggable) optical
ACK transceiver module available in many different options depending on the desired
reach (IR, LR, ELR), wavelength (1310nm, 1550nm), fibre type (SMF, MMF),
number of fibres (dual-fibre or single-fibre interface ) etc. Typically, dual-fibre
C.I.
transceivers are equipped with LC connectors while the single-fibre ones are
equipped with an SC connector. The unit accepts only transceivers equipped with
B86417-21
STM-4 UNIT
DMI (Diagnostic Monitoring Interface) to allow for in-depth transceiver monitoring.
The SFP transceivers installed have guaranteed minimal system gain of
Figure 30: STM-4 14dB@1310nm for the B86417-21/AA unit option, 25dB@1310nm for the B86417-
Aggregate Unit 21/BB option, 34dB@1550nm for the B86417-21/CC option and 38dB@1550nm
Front Panel for the B86417-21/EE option over the whole TN1Ue operating temperature range.
12 x TUG-3 Bypass The STM-4 payload comprises

port four VC-4s, where each VC-4
SFP TUG-3 consists of three TUG-3s.
STM-4 NxTUG-3
(622 Mb/s) LC
XCVR
VC-4 POH
CBW-E Each TUG-3 can carry either
Connectors
RSOH NxTUG-3 one TU-3 (VC-3) or 21 TU-12s
CBW-D
(VC-12s) so a maximum of
MSOH VC-4 POH TU-12 NxTUG-3
CBW-C 252 TU-12s may be carried in
and an STM-4 signal. On the drop
TU-3 NxTUG-3
CBW-B side, the unit has three
Cross
VC-4 POH
Connect NxTUG-3 TIFports and five CBW
CBW-A
(Configurable Bandwidth)
ports (Figure 31). Each CBW
VC-4 POH 3 TIF
TUG-3
ports
port can be configured to drop
multiple TUG-3s and/or as
TUG-3 Through many as 21 individually cross-
port
(shelf) connected TU-12s.
CBW ports are available on the top of the unit, while the TIFports are available on the shelf backplane
from where they are cabled to the TU-1 level units.
units.

TN1-86400-400PS
Issue 9.0
May 2017
Page 36
interface ETHER-100 unit (configured for 1 x TU-3 mode).
A CBW port configured for N x TUG-3 mode of operation (N= 4, 6, 12) allows a CBW port to be used for
providing a large bandwidth channel access for broadband applications such as 100/1000 Mb/s Ethernet
wire-speed bridging or for efficient tying of multiple TUG-3s and/or locally cross-connected TU-12s
between TN1Ue rings.
Normally, all through-traffic is passed to the companion STM-4 Aggregate units via the Bypass link (a 40-
wire ribbon cable). The shelf through-port is used only while upgrading in-service STM-1 rings to STM-4
capacity.
STM-4 STM-4
TU-12s only: 2 5 LEFT RIGHT

1
TU-12s
and/or TUG-3s: 1 3 4
2 3
Bypass link
(STM-4)
Port X
5 4
…

1x 2x … 21x
A B C D E Drop ports E D C B A
1 2 3 3 2 1
7 TU-12s
1 2 3
TIFports TIFports
CBW ports CBW ports
multiple rings. The unit’s “hairpinning” feature allows the TU-12s and TUG-3s from one subtended ring to
be passed to another subtended ring through the local STM-4 node.
maintenance functions on individual TUG-3 signals.

TN1-86400-400PS
Issue 9.0
May 2017
Page 37
STM-1
TN1Ue
STM-1
TN1Ue
STM-1
TN1Ue
STM-1
TU-12 Drop
TN1Ue 5 STM-4
TU-3 Drop
TN1Ue
4 STM-4
STM-4 3
TN1Ue TN1Ue
3 STM-4
STM-4 STM-4 TN1Ue
3 3
CBW TIE TN1Ue TN1Ue
4
TU-12 TRAFFIC
STM-4
TUG-3 TRAFFIC
TN1Ue STM-1
STM-1 TN1Ue STM-1
TN1Ue STM-1 TN1Ue
STM-1 TN1Ue
TN1Ue
STM-1
TN1Ue STM-1
STM-1 TN1Ue
STM-1 TN1Ue STM-1
STM-1 TN1Ue TN1Ue
TN1Ue
Figure 33: Tying traffic between STM-4 and STM-1 rings using CBW tie links
Figure 34: STM-4 Aggregate Unit View – Main Tab Figure 35: STM-4 Aggregate Unit View – VC-4 Tab
and configure TUG-3 and TU-12 cross-connects on the unit. By default, all TUG-3s and TU-12s from the
STM-4 port are connected to the Bypass link (passed through). Right mouse click on a specific TU-12 or
TUG-3 slot on a drop port opens up a menu that allows the user to select a TU-12/TU-3 that will be cross-
connected to the given TU-12/TUG-3 slot. Note that for the ports configured for N x TUG-3 mode (N=3, 4,
6, 12), the first TUG-3 slot may be configured as TU-12-structured (see CBW-E port configuration in
Figure 36).

TN1-86400-400PS
Issue 9.0
May 2017
Page 38
Figure 36: STM-4 Aggregate Unit View – Figure 37: STM-4 Aggregate Unit View –
Cross-Connect Tab TIFports Tab
The TIFports tab (Figure 37) allows the user to assign TU-12s to the unit's TIFports. Only the TU-12s
cross-connected from the optical STM-4 port or CBW ports to the unit's internal Port X may be assigned
("dropped") to the unit's TIFports. The TU-12s that are cross-connected to the Port X but not assigned to
any TIFports are passed through the node via the shelf backplane.
The TU-1 Status tab (Figure 38) provides status information for the TU-12s/TU11s assigned to the unit's
TIFports.
Figure 38: STM-4 Unit View – TU-12 Status Tab Figure 39: STM-4 Aggregate Unit View – Errors Tab

TN1-86400-400PS
Issue 9.0
May 2017
Page 39
The History tab (Figure 40) allows the user to retrieve the information on code violations registered in the
Section layer of the received STM-4 signal over an adjustable time period. This period is divided in 60
time cells of equal (and configurable) duration.
Figure 40: STM-4 Aggregate Unit View – History Figure 41: STM-4 Aggregate Unit View – Config
Tab Image 2 Tab
The Config Image 2 tab (Figure 41) allows the user to create and store into the unit's flash memory the
alternate image for traffic routing. The traffic routing information includes the STM-4 payload format,
cross-connections and TU-12 assignments for the TIFports. The user can swap the two images using
NMS when required.
The transmit STM-4 signal may be timed from the unit’s internal clock, from the incoming fibre, from the
shelf, or from a CBW port tied to a collocated TN1Ue node belonging to a different ring or linear system.
The shelf timing signal may be supplied by the companion STM-4 unit or introduced externally either from
a collocated STM-4 node (belonging to a different ring or linear system) or from an external reference
clock through a (pair of) External Sync unit(s) installed at the node. Refer to Section 8 for more
information on the synchronization options and synchronization distribution algorithm.
The STM-4 Aggregate unit may be used as a plug-in replacement for STM-1 Aggregate units to upgrade
existing TN1Ue networks with STM-1 capacity to STM-4 capacity1. Ring networks can be upgraded while
the system is in service.

The B86432 STM-1 Aggregate unit provides the STM-1 (155.52 Mb/s) transmit and receive optical
interface between a TN1Ue node and adjacent node in the same ring or linear network. The unit provides
hardware and software interfaces to the CSSU, External Sync units, TUG-3, ETHER-1000, ETHER-100
and all TU-1 level units.
The unit occupies one shelf slot position in a Common Equipment Shelf and must be installed in either the
12th or 14th position in the shelf (both locations are equipped at a ring node or at an add/drop node in a
linear network).
1 If fibre-optic lines permit (i.e. optical budget, fibre type etc.).

TN1-86400-400PS
Issue 9.0
May 2017
Page 40
LENTRONICS The unit is equipped with an SFP (Small Form-factor Pluggable) optical
MULTIPLEXERS transceiver module available in many different options depending on the
desired reach (IR, LR, ELR), wavelength (1310nm, 1550nm), fibre type
LOCAL (SMF, MMF), number of fibres (dual-fibre or single-fibre interface ) etc.
Typically, dual-fibre transceivers are equipped with LC connectors while the
RCV single-fibre ones are equipped with an SC connector. The unit accepts only
transceivers equipped with DMI (Diagnostic Monitoring Interface) to allow for
RCV YEL ALM
VC-4
in-depth transceiver monitoring. The SFP transceivers installed have
guaranteed minimal system gain of 20dB@1310nm for the B86432-51/AA
STM-1
unit option, 29dB@1310nm for the B86432-51/BB option, 34dB@1550nm for
ALARM the 86432-51/CC option, 37dB@ 1550nm for the B86432-51/EE option and
46dB@1550nm for the B86432-51/FF option over the whole TN1Ue
ACK
operating temperature range.
The STM-1 payload (VC-4) comprises three TUG-3s (Tributary Unit Group-
C.I.
3). Each TUG-3 may be used to carry 21 TU-12s so there is a maximum of
63 TU-12s that may be carried in an STM-1 signal. On the drop side, the unit
B86432-51
STM-1 UNIT has three TIFports and two CBW (Configurable Bandwidth) ports (Figure
43). Each CBW port can be configured to drop multiple TUG-3s and/or as
Figure 42: STM-1 many as 21 individually cross-connected TU-12s.
Aggregate Unit Front
Panel CBW ports are available on the top of the unit, while the TIFports are
available on the shelf backplane from where they are cabled to the TU-1
level units.
units.
interface and ETHER-100 unit (configured for 1 x TU-3 mode).
A CBW port configured for 4 x TUG-3 mode of operation allows a CBW port to be used for providing a
large bandwidth channel access for broadband applications such as 100 Mb/s Ethernet wire-speed
bridging or for efficient tying of multiple TUG-3s and/or locally cross-connected TU-12s between TN1Ue
rings.
All through-traffic is passed to the companion STM-1 Aggregate unit via the shelf backplane.
N x TUG-3
CBW-B
TU-12
TUG-3
and N x TUG-3
CBW-A
STM-1 OPTICS
STM-1e
RSOH MSOH VC-4 POH TUG-3
(155 Mb/s) LC Cross
Connectors Connect TUG-3 3 TIF
ports
Through-port
(shelf backplane)

TN1-86400-400PS
Issue 9.0
May 2017
Page 41
STM-1 STM-1
TU-12s only: 2 5
LEFT RIGHT
TU-12s and/or 1
TUG-3s: 1 3 4
2 3
Bypass link
(STM-1)
Port X
5 4
…

1x 2x … 21x
A B Drop ports B A
1 2 3 3 2 1
7 TU-12s
1 2 3
TIFports CBW ports CBW ports TIFports
multiple rings. The unit’s “hairpinning” feature allows the TU-12s and TUG-3s from one subtended ring to
be passed to another subtended ring through the local node.
STM-1
TN1Ue
STM-1
TN1Ue
STM-1
TN1Ue
STM-1
VC-12 Drop
TN1Ue 5 STM-4
VC-3 Drop
4
TN1Ue
STM-1 3 STM-4
TN1Ue TN1Ue
3 STM-4
STM-1 STM-1 TN1Ue
3 3
CBW-TIE TN1Ue TN1Ue
VC-12 TRAFFIC
VC-3 TRAFFIC
STM-1
TN1Ue
4
STM-1 STM-1
TN1Ue STM-1
TN1Ue STM-1
Foreign
TN1Ue
STM-1
STM-1
TN1Ue STM-1
Foreign
Foreign
STM-1
STM-1 TN1Ue
TN1Ue STM-1
Foreign STM-1
Foreign
Figure 45: Tying traffic between STM-1 and STM-4 rings using CBW tie links

TN1-86400-400PS
Issue 9.0
May 2017
Page 42
Figure 46: STM-1 Aggregate Unit View – Main Tab Figure 47: STM-1 Aggregate Unit View – VC-4 Tab
Figure 48: STM-1 Aggregate Unit View – Cross- Figure 49: STM-1 Aggregate Unit View – TIF Ports
Connect Tab Tab
maintenance functions on individual TUG-3 signals.
and configure TUG-3 and TU-12 cross-connects on the unit. By default, all TUG-3s and TU-12s from the
STM-1 port are connected to the Bypass link (passed through). Right mouse click on a specific TU-12 or
TUG-3 slot on a drop port opens up a menu that allows the user to select a TU-12/TU-3 that will be cross-
connected to the given TU-12/TUG-3 slot. Note that for the ports configured for 4 x TUG-3 mode, the first
TUG-3 slot may be configured as TU-12-structured (see CBW-B port configuration in Figure 48).

TN1-86400-400PS
Issue 9.0
May 2017
Page 43
The TIFports tab (Figure 49) allows the user to assign TU-12s to the unit's TIFports, to select the mode of
operation for the TIFports and to select the TU-12 that may alternatively be used for carrying NMS
information (refer to Section 6 for more information).
Figure 50: STM-1 Aggregate Unit View – Errors Figure 51: STM-1 Aggregate Unit View – Config
Tab Image 2 Tab
The TU-1 Status tab (Figure 49) provides status information for the TU-12s/TU-11s assigned to the unit's
TIFports.
The History tab (Figure 52) allows the user to
retrieve the information on code violations registered
in the Section layer of the received STM-1 signal
over an adjustable time period. This period is
divided in 60 time cells of equal (and configurable)
duration.
The Config Image 2 tab (Figure 51) allows the user
to create and store into the unit's flash memory the
alternate image for traffic routing. The traffic routing
information includes the STM-1 payload format,
cross-connections and TU-12 assignments for the
TIFports. The user can swap the two images using
NMS when required.
The transmit STM-1 signal may be timed from the
unit’s internal clock, from the incoming fibre, or from
the shelf. The shelf timing signal may be supplied by
the companion STM-1 Aggregate unit or introduced
Figure 52: STM-1 Aggregate Unit View – History externally either from a collocated TN1Ue node
Tab (belonging to a different ring or linear system) or
from an external reference clock through a (pair of) External Sync unit(s) installed at the node. Refer to
Section 8 for more information on the synchronization options and synchronization distribution algorithm.

TN1-86400-400PS
Issue 9.0
May 2017
Page 44
4.7 External Sync Unit
LENTRONICS The B86480 External Sync unit is typically used in the following applications:
MULTIPLEXERS
 To synchronize the TN1Ue network from an external reference clock signal
INT/STBY (a 2048 kHz signal or a framed E1 that may carry traffic). Applications with
HOLDOVER backup external sync nodes in the same or different rings are also
supported.
A
 To synchronize external (non-TN1Ue) equipment to the TN1Ue network
B/C timing reference. This could be a 2048 kHz signal or a framed or unframed
LINE-L E1 signal carrying no traffic.
LINE-R
 To flexibly pass timing and Synchronization Status Message (SSM) from one
TN1Ue ring/linear network to another in either direction.
ALARM  To filter the accumulated jitter using an external SASE (Stand-Alone
ACK
Synchronization Equipment) in TN1Ue networks with large number of nodes.
The unit supports the following sync reference inputs (Figure 54):
 Line-L/R: Clock signals derived from the incoming (Left and Right) optical
C.I.
aggregate signals.
 A-IN and B-IN: Each of these ports may be configured for an external 2048
B86480-31 kHz (G.703/13) sync signal or a framed 2048 Mb/s (G.703/9) signal. Note
EXT-SYNC UNIT
that the latter one may carry live traffic and can be the local node’s tributary.
Figure 53: External  C-IN: Sync signal from another TN1Ue node belonging to a collocated ring or
Sync Unit Front Panel linear network (an “intelligent sync tie” interface).
Each input on the Selector B can be individually provisioned; however, it is not possible to have both B-IN
and C-IN provisioned.
The intelligent sync tie input, the inputs from the optical aggregates, and the inputs configured for Framed
E1 mode (PCM30+CRC4 or PCM31+CRC4 format) can process the incoming SSM. The SSM can be
read from any of the E1 multiframe bits Sa4 to Sa8 (as per G.704). Any input can have a user-assigned
SSM that overwrites the incoming SSM.
The External Sync Unit provides two external sync outputs (A-OUT and B-OUT) that may be used to
synchronize foreign, non-TN1Ue equipment. For this application, each output can be configured to
provide a 2048 MHz signal, a framed E1 or an unframed E1 signal. These signals are by default timed
from the shelf clock (Selector C set for the “Shelf” position) but for some applications they may be line
timed (Selector C set for “Line” position) in which case the timing source (Line-L or Line-R) is selected by
the Selector A based on their availability and associated SSM.
The outgoing framed E1 signal in PCM30+CRC4 or PCM31+CRC4 format can be configured to carry
SSM in its multiframe bit Sa#4 (as per G.704).
Each of the two outputs may also be configured for a pass-through mode. In this mode, the output is a
copy of the signal from the respective input which includes its timing and traffic (if any). This is used for
applications where an E1 sync reference carries live traffic (typically as a local node’s tributary signal) 1.
The inputs and outputs configured for framed E1 signal can support PCM30, PCM30+CRC4, or
PCM31+CRC4 framing formats (as per G.704). The line code for the input and output E1 signals may be
either HDB3 or AMI.
1 The same can be achieved by using a 75-ohm BNC T-connector on the port’s input in which case the respective
output does not have to be configured for Pass-Through mode (may be disabled, set for 2048 kHz, etc.).

TN1-86400-400PS
Issue 9.0
May 2017
Page 45
Left Aggregate Right Aggregate
8 kHz timing 8 kHz timing

(with SSM) (with SSM)
LINE-L LINE-R
SSM
T1(R)
Selector LINE A-OUT2
Selector T4
T1(L) A
C B-OUT3
SSM
T1(R)
SSM T1(L) T0 (2 kHz)

SETG
T2/T3 Selector Shelf Clock (T0)
A-IN1
B with embedded
T2/T3 SSM-to-L and
B-IN1
SSM-to-R
SSM SSM
C-IN C-OUT
(with SSM) From / To (with SSM)
companion unit
1 May carry SSM if framed E1 (PCM30+CRC4 or PCM31+CRC4 format)

2 Configurable for 2048 kHz, Framed E1 (with SSM), Unframed E1, or “Pass-Through” (connect to A-IN).
3 Configurable for 2048 kHz, Framed E1 (with SSM), Unframed E1, or “Pass-Through” (connect to B-IN).
SETG: Synchronous Equipment Timing Generator T2: Reference frequency from 2048 kb/s tributary
T0: Node internal timing (TN1Ue’s 2kHz shelf clock) T3: 2048 kHz reference frequency (G.703/13) – input
T1: Reference frequency from STM-N (TN1Ue’s 8kHz clock) T4: 2048 kHz reference frequency (G.703/13) – output
Figure 54: External Sync Unit Inputs and Outputs
Each provisioned sync reference input is constantly checked for availability and validity. The selector B
will select the clock source with the lowest incoming (or user-assigned) SSM and the SETG will lock to it.
If two or more sources have the same (incoming or user-assigned) SSM value, then the source with the
highest priority setting will be selected. If the selected sync source fails, the unit performs a switch to
another input. In the case when all provisioned sync references fail, the unit (i.e. its SETG module) will
enter holdover mode.
The selected input is used for driving the shelf clock, the intelligent sync tie output and, optionally, the two
external sync outputs. The SSM associated with the selected sync input will be sent to all applicable
output ports; however, this may be overwritten (forced by the user) for individual output ports.
The External Sync unit can provide internal timing reference with stability of 4.6 ppm, but typically the unit
is not used in such applications since the aggregate unit can be configured to provide the same
functionality.
It is recommended that two External Sync units be installed at a node. When two units are equipped, one
unit is Master (online) while the other one is on standby. The online unit provides the TN1Ue shelf with 2-
kHz timing signal synchronous to the selected synchronization reference.
A pair of External Sync units share the same paddleboard. The paddleboard provides external sync
connections to the units (75-ohm BNC), intelligent sync tie connections, as well as connections to the
Service Unit Paddleboard (for timing and SSM signals between External Sync units and Aggregate units).

TN1-86400-400PS
Issue 9.0
May 2017
Page 46
Figure 55: External Sync Unit View – Main Tab Figure 56: External Sync Unit View – Sync Outputs
4.8 Cyber-Secured Service Unit (CSSU)

The B86434-11 CS Service unit (CSSU) provides alarm collection and reporting, orderwire channel
access for Orderwire and 4W VF units, and a multitude of NMS functions for the local TN1Ue node. In
conjunction with remote CSSUs, it allows monitoring, configuration and diagnostics of the entire TN1Ue
network. The unit can also monitor as many as four external contact inputs and report their status to the
NMS.
NMS-Tie – Master NMS-Tie – Slave
LENTRONICS
MULTIPLEXERS
Office Alarms
(Minor and Major)
NMS
External contact inputs
Rear Ethernet
and alternative rear CI
Interface (for
MINOR MAJOR access
permanent NMS
connections)
ALARM
Connection to
Power Unit
Ext. Sync Unit
ACK Monitor (wired
Paddleboard
to Power Unit
(if equipped)
paddleboards)
C.I.
Wiring for
Shelf Alarms Rear Craft Interface
(Minor and Major (requires use of
B86434-11
CS SERVICE UNIT Shelf LEDs) DB9-to-RJ11 adapter)
Figure 57: CS
Service Unit Front Figure 58: 86434-81 Service Unit Paddleboard
Panel
The CSSU is installed in the 13th slot of the Common Equipment Shelf (between the left and right OC-N
Aggregate units). The 86434-81 paddleboard (Figure 58) provides connections for office alarms, power

TN1-86400-400PS
Issue 9.0
May 2017
Page 47
monitor, Orderwire CBUS, external contact inputs and NMS ties. Also available on the paddleboard are
the rear Craft Interface and Ethernet ports.
The unit is equipped with alarm indicators which summarize the node alarms. Alarms are reported by two
front panel LEDs for Major and Minor alarm condition. The amber LED is latched if any alarm (minor or
major) occurs at this node. This LED will remain lit after the alarms have cleared and can be extinguished
by pressing the Acknowledge (ACK) button provided on the front of the unit.
The Form-C office alarm contacts can be configured to reflect the alarm status of the local node (default
setting), the status of the local network (ring or linear network that the local node belongs to), or the status
of the entire TN1Ue system (made of all rings and linear networks in the same NMS domain).
All TN1Ue nodes capable of exchanging NMS data belong to the same NMS domain. The nodes
belonging to the same ring or linear network are normally configured to belong to the same NMS domain.
The CSSU acts as a gateway to the NMS domain to which the node belongs. Visibility of the entire NMS
domain can be achieved through any CSSU within the domain.
NMS domains can be expanded across multiple ring/linear networks by means of NMS tie links. NMS ties
are established using dedicated cables between Service Unit Paddleboards at sites where TN1Ue nodes
belonging to multiple ring/linear networks are collocated (see NMS Domain #4 in Figure 59).
The unit supports two modes of operation, Legacy and Secure.
A CSSU in Legacy mode (CSSU-L) can exchange NMS data with legacy (B)86434-02 Service Units (SU)
or other CSSU-L units installed at other TN1Ue nodes in the same ring/linear network through SDH
overhead channels.
A CSSU in Secure mode (CSSU-S) has its enhanced network management features including cyber
security enabled. This mode requires that all the nodes in the local TN1Ue ring/linear network are
equipped with CSSU-S units. The CSSU-S protects against malicious and unintentional network
access/control through defence-in-depth strategies allowing TN1Ue users to meet the latest network
security standards. Note that the network management data cannot be exchanged between CSSU-S-
based and SU/CSSU-L-based TN1Ue rings.
A CSSU operating in Secure mode acts as a secure gateway between the local TN1Ue node and the
VistaNET NMS software by ensuring:
 NMS data privacy by employing strong AES 256-bit encryption of NMS data.
 Authentication of users accessing NMS ports by implementing TLS/SSL protocol and X.509 digital
certificate.
 Authorization of users’ access and their read/write privileges using an integrated Access Control
List that is replicated and synchronized among all CSSUs within the same network management
domain.
 Accountability by logging and securely storing alarms and activity logs.
The CSSU in Secure mode also supports RADIUS (Remote Access Dial-In User Service) for centralized
user authentication as well as date and time synchronization to an NTP server. It will also be able to
utilize the built-in micro-SD memory card for supplemental alarm and event storage.
The unit provides two Ethernet ports. The front one is available on unit’s faceplate (RJ-45 connector
labeled ‘NMS’) while the rear one is available on the 86434-81 paddleboard.
Both front and rear Ethernet ports provide access to TN1Ue NMS from a PC running VistaNET software.
Additionally, using the unit’s Web UI, the CSSU administrator (cssuadmin) can perform a firmware

TN1-86400-400PS
Issue 9.0
May 2017
Page 48
upgrade, configure security and timing (NTP) parameters, modify Access Control List (ACL), update
certificates, and synchronize (copy) the security settings to all other CSSUs in the NMS domain.1
The front Ethernet port is used for a direct (local) connection to a PC running VistaNET, while the rear one
is normally connected to the user’s IP network. Both front and rear Ethernet ports can get their IP
addresses assigned either statically or dynamically (from a DHCP server). The front Ethernet port also
supports DHCP server functionality (enabled by default) to allow the locally connected PC to acquire an IP
address from the CSSU and establish a quick point-to-point Ethernet link to the port.
The CSSU can support up to four simultaneous TCP/IP connections. These can be split between front
and rear Ethernet ports.2
In addition to Ethernet ports, the unit has two Craft Interfaces (CI). These are serial 9600-baud
asynchronous RS-232 interfaces that are operational only in Legacy mode. The Craft Interface can be
connected to a VistaNET PC through a direct (hardwire) connection, a dial-up (modem) connection or a
DATA-LS circuit. The front CI (RJ-11 connector on the unit’s faceplate) is typically used for temporary
serial connections to a local VistaNET PC. The rear CI (RJ-11 connector on the 86434-81 paddleboard)
is typically used for permanent serial connections.
24/7 VistaNET PC
VistaNET
SNMP User
Manager
RS-232 Modem
Ethernet
VistaNET
User Hardwire PSTN
(RJ-11)
CI
DATA-LS
LAN / WAN Modem
TN1Ue
CI
NMS Domain #1 TN1Ue

Ethernet
TN1Ue
NMS Domain # 4
TN1Ue DATA-LS NMS Domain #3
TN1Ue
TN1Ue TN1Ue
TN1Ue TN1Ue CI
TN1Ue
TN1Ue
E1
NMS Tie
NMS Domain #2
E1MXe
TN1Ue TN1Ue TN1Ue
TN1Ue
E1
Sync Tie
E1MXe
TN1Ue
Figure 59: Various types of VistaNET connections to CSSUs in different NMS domains
Various types of VistaNET PC connections to CSSUs are illustrated in Figure 59. A VistaNET PC
initialized with VNI license and connected to a CSSU is capable of monitoring and configuring all visible
TN1Ue nodes (refer to Section 6 for TN1Ue NMS features). If this PC is running VistaNET Server
Application (VSA) and is also connected to an Ethernet LAN/WAN, it will act as a server for other
VistaNET PCs connected to the same LAN/WAN thus providing them with the same monitoring and
configuring capabilities.
1 Most of these actions are applicable to Secure mode only.

2 The front Ethernet port, due to its intended use, is never connected to more than one VistaNET user at a time so it
will practically never “consume” more than one TCP/IP link (out of the four supported by the unit).

TN1-86400-400PS
Issue 9.0
May 2017
Page 49
A VistaNET PC can be configured to act as an SNMP proxy (v1, v2c or v3) agent for all managed TN1Ue
units. With this function enabled, VistaNET PC will produce SNMP traps for alarms received from the
TN1Ue network.
The usage of CSSU’s Craft Interface (CI) and Ethernet ports is summarized in Table 6.
Port Usage Legacy Mode Secure Mode

CI Local CSSU configuring Yes No
(front/ & rear) and monitoring
NMS Access Yes
Firmware Upgrades No
Ethernet Local CSSU configuring Yes Yes (security settings can be
(front & rear) and monitoring modified via Web UI by
cssuadmin only)
NMS Access Yes Yes (any configuration change
requests require user
authentication and authorization
against ACL stored in the unit)
Firmware Upgrades Yes (via Web UI, available to Yes (cssuadmin only)
cssuadmin only)
Table 6: Comparing CSSU’s CI and Ethernet Port Functions
CSSU provides four external contact inputs whose status can be monitored locally or remotely. Each
contact can be programmed for either normally open or normally closed operation. When the NMS alert
feature for a contact is enabled, a Minor Alarm (Minor red LED and Minor Form C relay) is reported for the
duration of the contact’s active condition. The alarm cut-off (ACO) function allows the user to remotely
terminate the Minor alarm caused by an active external contact while the external contact is still active.
Each ‘idle-to-active’ event on any contact input with alert feature enabled produces a ‘set alarm’ entry in
the VistaNET alarm engine. Similarly, each ‘active-to-idle’ or ACO event produces a ‘clear alarm’ in the
alarm engine. Each set/clear alarm entry includes date & time and the source CSSU.
Figure 60: CSSU VistaNET View – Status Tab Figure 61: CSSU VistaNET View – Basic Setup Tab
The CSSU-S units exchange security maintenance data over a set of Overhead bytes separate from the
bytes used for NMS communications. This channel is referred to as Security Maintenance channel. An
internal private LAN is established over this channel where the unit IP addresses are based on the unique
combination of Ring# and Node# assigned to each CSSU (see Figure 62).

TN1-86400-400PS
Issue 9.0
May 2017
Page 50
Secondary
RADIUS
Primary Server
RADIUS NTP
192.168.0.2 Primary Server
Server
192.168.0.1 Master
VistaNET PC Rear Port
Front 3.94.212.247 24/7 VistaNET PC
Port
Corporate
CSSU-S subnet over LAN / WAN
SDH overhead
Rear Port VistaNET PC

3.94.212.199
Secondary
Master
Figure 62: CSSU-S Communications

One CSSU-S in the domain operates as a master CSSU-S. The CSSU administrator designates the
primary and, optionally, the secondary master CSSU-S unit. If the primary master unit fails, the secondary
one becomes the master CSSU-S unit. Once the primary master unit is operational, it will become the
master CSSU again.
The master CSSU-S does the following:

 Operates as a watchdog that constantly checks if all CSSU-S in the domain have the same
security settings, ACL and certificates.
 Distributes the current date and time across the domain. Its real time clock (RTC) can be
optionally configured to synchronize from an NTP server on regular basis.
 Operates as a gateway for RADIUS server communications (if applicable).
The unit’s ACL consists of the Local and RADIUS users. The Local Users list will take effect only if either
RADIUS authentication is not used or no RADIUS servers are presently available.
Each RADIUS user account consists of a username
(must match the username in the external directory
used by the RADIUS server), account expiry date &
time, and membership to a user group (all members
of the given user group share the same
authorizations). The Local user accounts also
include a password. The CSSU administrator adds,
modifies or deletes individual user accounts through
the Web UI.
A user that successfully authenticated to a CSSU-S
will be able to perform configuration changes within
the unit’s NMS domain based on his/her
authorizations. Any authenticated user disconnected
from the unit for an extended period of time (default
is 60 sec but configurable by the CSSU
administrator) will have to re-authenticate himself in
Figure 63: CSSU Web UI – Authorization Tab order to perform any configuration changes within the
unit’s NMS domain.
Using Web UI, the CSSU administrator can define User Groups whose members will share the same
access privileges to certain rings and nodes.

TN1-86400-400PS
Issue 9.0
May 2017
Page 51
4.9 Orderwire Unit

The B86471 Orderwire unit provides the multipoint voice communications between any two or more sites
in the TN1Ue system using one of the Orderwire bytes in the STM-N Section Overhead. The unit
connects to the CSSU, which provides the interface to the overhead bytes from both the right and left
directions. A maximum of seven overhead bytes can be selected to carry Orderwire and/or VF Partyline
channels in a TN1Ue system, i.e. up to seven independent Orderwire/Partyline systems can be
established within the same TN1Ue system.
The first Orderwire unit at a node is typically installed in the Common Equipment Shelf slot 2. Additional
Orderwire and/or Partyline units are installed in adjacent shelf slots (3, 4…). Alternatively, the Orderwire
bus can be established on an Expansion Shelf.
LENTRONICS Connection for the

MULTIPLEXERS TELSET can be made on
the rear RJ-12 jack on the
BUSY / RING
unit paddleboard. The
unit is equipped with a
sub-assembly board
HEADSET providing the talk battery
(+5 VDC to -28/56 VDC
CALL
conversion) and ringing
generator functions.
ACK ALM A HEADSET can be

plugged into the
C.I. corresponding jack on the
front of the unit. The
B86471- HEADSET in conjunction
ORDERWIRE UNIT with the CALL button and
audible buzzer can be
Figure 64: Orderwire Figure 65: Orderwire Unit View used for both partyline
Unit Front Panel (all-call) and address
(selective) calling.
Also available on the paddleboard are four unbalanced, high impedance inputs (100 k) labelled as
VF(IN) and four unbalanced, low impedance (150 ) outputs VF(OUT). This allows the VF orderwire
signal to be passed between multiple networks in a TN1Ue system.
The user can configure both the local unit address as well as the far-end unit address (00-99) for DTMF
tones. The far-end address setting determines what far-end Orderwire unit will ring when local CALL
button is pressed. If "" is selected as the far-end address then the CALL button will alert (ring) all sites
in the orderwire system (all remote units using the same orderwire channel). If a telset is used, the far-
end address can be directly selected on the telset keypad.
One Orderwire unit in a ring is configured as "Headend" and all other Orderwire units using the same
Orderwire channel are configured as "Normal". This ensures that the orderwire signal is broken at one
node thus preventing indefinite circulation of orderwire tones in the ring.
A proprietary orderwire channel switching algorithm ensures that the orderwire service remains
operational in the event of a ring break.

TN1-86400-400PS
Issue 9.0
May 2017
Page 52
4.10 CMUX Unit

The B86485 CMUX unit provides the interface between an STM-N Aggregate or TUG-3 unit TIFport and
four CBUS ports. The TIFport must be configured for TU-11 mode of operation.
LENTRONICS
MULTIPLEXERS
CBUS
S
R
CBUS-P CBUS-Q
Q
P
ALARM
ACK
CBUS-R CBUS-S
C.I.
B86485-22
CMUX UNIT
Figure 66: CMUX Figure 67: CMUX Unit Paddleboard

Unit Front Panel
The CMUX unit may be directly connected to an STM-N Aggregate or TUG-3 unit TIFport, or it may be
paralleled (cascaded) with another TU-1 level unit of TU-11 type (CMUX, CDAX or ETHER-10 unit) so that
a maximum of seven TU-11s can be dropped or inserted at the TIFport. At ring nodes, CMUX units are
equipped in pairs to provide automatic path switching in case of fibre or unit failure. A path priority is set
through software configuration so that the other path is only used when a failure is detected on the priority
path. Protection switching is revertive, i.e. when the problem is corrected, the traffic is switched back to
the priority path.
The four CBUS ports are identified as CBUS-S, CBUS-R, CBUS-Q, and CBUS-P. Each CBUS consists of
up to 24 64kb/s channels. Normally, CBUS-S is assigned first as it directly feeds the shelf bus
immediately to the left of the CMUX unit. For channel access to CBUS-R, CBUS-Q, and CBUS-P ports,
they must be cabled to the desired destination shelves. The CBUS-S port can also be optionally cabled to
a desired destination shelf.
Each CBUS port can be independently configured for either Standard or Share mode of operation.1
In Standard mode, the unit drops all 24 64kb/s channels on the bus and the protection switching takes
place at TU-11 level. The path switching time is specified as 3 ms.
In Share mode, the unit drops only the selected 64 kb/s channels. Other 64 kb/s channels (the ones not
selected for dropping) are passed through. This mode allows a TU-11 to be shared between several
TN1Ue nodes. Each shared TU-11 provides 24 64kb/s node-to-node links with no restrictions on the
number of links terminated at a node. In Shared mode, each 64 kb/s channel is switched independently.
Share mode of operation allows better utilization of the TU-11 bandwidth, however, this mode is not
recommended for teleprotection circuits because the protection switching time and node through-delay
are generally longer in Share than in Standard mode of operation.
1 The CBUS-P port of the legacy (B)86485-21 unit supports only Standard mode of operation.

TN1-86400-400PS
Issue 9.0
May 2017
Page 53
The unit has a built-in test capability which allows for the insertion of a test pattern into any or all of the
outgoing TU-11s. By monitoring the incoming TU-11 at the far end, a validity of the VC-11 path can be
confirmed. This end-to-end VC-11 path testing checks the entire VC-11 path integrity.
consists of multiple tabs. The Main Tab (Figure 68) is used for TU-11 setup, status monitoring and test
functions as well as monitoring the unit status and temperature.
Figure 69: CMUX Unit View –

Figure 68: CMUX Unit View – Main Tab
64 kb/s Channels Tab
For a selected online / NMS Master CBUS port in

Standard or Share mode of operation, 64 kb/s
Channels tab (Figure 69) provides unit type and
status information for the channels used by 64
kb/s level units. For CMUX ports in Share mode
of operation, this tab allows for selection of
channels that are to be dropped, for configuring
their priorities, and forcing online channels to
standby mode (on per channel basis) for
maintenance.
For the selected CBUS, the Show TU-11 tab

(Figure 70) displays the content of a TU-11
superframe received from the far-end unit, which
may be useful for maintenance. A new TU-11
superframe is captured and displayed every few
Figure 70: CMUX Unit – Show TU-11 Tab seconds.

TN1-86400-400PS
Issue 9.0
May 2017
Page 54
4.11 CDAX Unit

LENTRONICS The CDAX unit provides 64kb/s cross-connect function between an STM-N
MULTIPLEXERS Aggregate or TUG-3 unit's TIFport and four "drop ports". Each drop port can be
TIF
configured to:
- drop as many as 24 64kb/s channels to various 64kb/s-level interface units
S
offered in TN1Ue product portfolio;
R
- interface a channelized E1 signal in order to pass as many as 30 64kb/s
Q
channels to/from a remote TN1Ue network, GE Lentronics E1 Multiplexer
P
(E1MXe) or any other equipment interfacing a channelized E1 signal (foreign E1
multiplexer, DACS, PABX, etc.) through a direct E1 link or E-carrier system.
ALARM
- Interface a proprietary 30-channel “optic E1” signal in order to pass 64kb/s
ACK
channels to/from a remote TN1Ue network or E1MXe node optically.
The four drop ports are denoted Port S, Port R, Port Q, and Port P (Figure 72).
C.I.
The unit can process as many as 7 TU-11s on the TIFport and is capable of cross-
B86486-21 connecting individual 64kb/s channels between the TIFport's TU-11s on one side and
CDAX UNIT four drop ports on the other. This allows any 64kb/s channel from any of the
TIFport's 7 TU-11s to be connected to any 64kb/s channel on any of the four drop
Figure 71: ports. The unit also allows for connecting whole TU-11 payloads to specific drop
CDAX Unit Front ports as well as cross-connecting 64kb/s channels between the drop ports
Panel themselves (64kb/s hairpinning).
to STM-N Optionally cascaded

unit’s TIFport signal (7 TU-11 time-slots) to another TIF-level
TIFport unit using TU-11s
TU-11 Slot#1
TU-11 Slot#2
TU-11 Slot#3
TU-11 Slot#4
TU-11 Slot#5
TU-11 Slot#6
TU-11 Slot#7
TIFport
Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Slot 6 Slot 7

… … … … … … … Slot 7
64kb/s
Cross 1 24
Connect Hairpinning 24 x 64 kb/s
Module
… … … …
30 x 64 kb/s
Port S Port R Port Q Port P 1 30*
Port Q
Port R
Port S
Port P
Drop Ports Port P
CBUS E1 CBUS Optical * When in E1/Optic mode

E1
Figure 72: CDAX Unit Ports and Cross-Connect Functions
If the CDAX unit is provisioned to process less than 7 TU-11s, it can be paralleled (cascaded) with another
TIF-level unit (i.e. T1/E1, ETHER-10, CMUX or another CDAX unit) so that the utilization of the TIFport
can be maximized.
The CDAX unit is backwards compatible with the CMUX unit in a sense that it can drop or tie 64kb/s and
TU-11 circuits originated/tied by these units at the far end and provide the same functionality.

TN1-86400-400PS
Issue 9.0
May 2017
Page 55
Slot 1 Slot 2 Slot 3 Slot 4 Slot 5 Slot 6 Slot 7

The unit can be used as part of a GE Lentronics E1
… … … … … … … Multiplexer node (E1MXe) in which case the TIFport
is unprovisioned (Figure 73). An E1MXe can be
64kb/s configured to operate as a 4-port DACS, add/drop E1
Cross multiplexer, or terminal E1 multiplexer.
Connect
Module An E1MXe can be interconnected electrically or
optically with other E1MXe nodes to create a cluster
… … … …
of E1MXe nodes, which may operate either as a
Port S Port R Port Q Port P standalone entity or an entity integrated with a TN1Ue
network. Point-to-point, linear, star, ring1 and mixed
E1MXe cluster topologies are supported. NMS
Port Q
Port R
Port S
Port P
visibility of an E1MXe cluster can be obtained from
any of its nodes through VistaNET. When connected
to a TN1Ue network, an E1MXe cluster is also visible
CBUS E1 Optical Optical
E1 E1 from any of the TN1Ue nodes in the NMS domain to
which the TN1Ue node interfacing the cluster
Figure 73: CDAX in E1MXe application belongs.
Each of the drop ports (S, R, Q and P) can operate in one of the modes of operation listed in Table 7.
Mode of
Description
Operation
Bulk Drop The port is configured to drop 24 64kb/s channels from a single TU-11. A TU-11 from the TIFport
must be assigned to this port.
Share Drop The port is configured to drop a maximum of 24 64kb/s channels. Each provisioned 64kb/s
channel can be connected to a 64kb/s channel of any of the 7 TU-11s on the TIFport or hairpinned
to a 64kb/s channel of any other drop port configured for E1 or Optic mode.
E1 The port provides the interface to a standard channelized E1 signal. Each provisioned 64kb/s
channel on the port can be connected to a 64kb/s channel of any of the 7 TU-11s on the TIFport or
hairpinned to a 64kb/s channel of any other drop port configured for E1, Optic or Share Drop mode.
Optic The port provides an optical E1 interface to a remote CDAX unit port configured for the same mode
of operation. An SFP optical transceiver must be equipped in the respective paddleboard port slot.
Table 7: CDAX Unit Drop Port Modes of Operation
Three types of paddleboards are available for use with CDAX units. The simplest of the three is normally
used when CDAX units are deployed at TN1Ue nodes and no optical connections to remote E1MXe
nodes are required. The other two paddleboards are equipped with power unit monitor input, an auxiliary
contact input and major and minor office alarm relays, which are the features used at E1MXe nodes. The
most complex paddleboard can be equipped with optical SFP transceivers and can be used at either
E1MXe or TN1Ue nodes.
Two CDAX units can be installed on the same paddleboard to provide:

- ability to share the same TU-11 bandwidth between three or more nodes in TN1Ue applications;
- TU-11/64kb/s path and hardware redundancy in TN1Ue ring applications;
- hardware redundancy in E1MXe applications.
When deployed at a TN1Ue node, the CDAX unit allows for:

a) Expanding TN1Ue network over E1 radio or copper links. At the far end of an E1 link, an E1MXe
node/network or another TN1Ue network may be deployed. All types of TN1Ue 64kb/s circuits
can be extended to a remote TN1Ue or E1MXe node/network.
b) Reaching into legacy E1 equipment/network at the 64kb/s level. A foreign E1 multiplexer, PABX
or DACS residing at the edge of an E1-based network may be connected at the far end of the E1
1 Ports in Optic mode presently do not support E1MX rings.

TN1-86400-400PS
Issue 9.0
May 2017
Page 56
link. NOTE: Only VF interface units and interface units for 64 kb/s and Nx64 kb/s data can
communicate with respective 64kb/s-level units at foreign (non-E1MXe) E1 multiplexers.
c) Adding DACS capability at the TN1Ue network edge. Allows for consolidation of 64kb/s traffic
from multiple E1 links into a single TU-11 and/or from multiple TU-11s into a single E1 link.
Examples of the above applications are provided in Section 7.
Figure 74: CDAX Unit View – Main Tab Figure 75: CDAX Unit View – Cross-Connect Tab
Figure 76: CDAX Unit View – 64kb/s Channels Tab Figure 77: CDAX Unit View – E1 Tab

TN1-86400-400PS
Issue 9.0
May 2017
Page 57
4.12 Tie Unit
LENTRONICS The B86435 Tie unit provides the interface between an STM-N Aggregate or TUG-
MULTIPLEXERS 3 unit's TIFport and seven TU-12 ports. The TIFport must be configured for TU-
TU-12 12 mode of operation. The Tie unit interfaces the TIFport and selects up to seven
PORT individual TU-12s for interface between multiple TN1Ue networks. The TU-12
1
ports are grouped on four RJ-45 connectors available on the unit paddleboard.
2 The TU-12 ports #1 and #2 are grouped on the first RJ-45 connector, TU-12 ports
3 #3 and #4 are grouped on the second, TU-12 ports #5 and #6 on the third, and
4 TU-12 port #7 on the fourth RJ-45 connector. Therefore, a Tie unit can pass a
maximum of seven TU-12s from one TN1Ue network to a maximum of four other
5
TN1Ue networks.
6
7 If the unit does not use all seven slots on the TIFport, it may be paralleled
ON YEL ALM
(cascaded) with a T1/E1 unit.
ACK At a ring node, two Tie units interface separate (left and right) STM-N Aggregate
units to the same seven TU-12s for automatic path switching in case of fibre or
common unit failure in the local ring. A path priority is set through software
C.I.
configuration so that the other path is only used when a failure is detected on the
priority path. Path switching times are specified as 3 ms.
B86435-22
TIE UNIT
A built in test capability allows for the insertion of a test pattern into any or all of the
outgoing TU-12s. By monitoring the incoming TU-12 at the remote site, a validity
Figure 78: Tie Unit of the VC-12 path can be confirmed. This end-to-end VC-12 path testing checks
Front Panel the entire VC-12 path integrity and is performed through the software.
The unit also supports line loopback feature allowing a TU-12 coming from the TIFport to be looped back
(sent back towards the STM-N Aggregate unit). The loopback can be enabled independently for each
TU-12 port through the software.
Figure 79: Tie Unit View – Main Tab Figure 80: Tie Unit View – Tie Info Tab
Note that either a 2kHz sync tie connection (see section 8) or an intelligent sync tie connection (see
section 4.7) must be present at the tie site in order for a TU-12 tie connections to be operational.

TN1-86400-400PS
Issue 9.0
May 2017
Page 58
4.13 TUG-3 Unit

The B86490 TUG-3 unit provides the interface between an STM-N Aggregate unit’s CBW port (configured
for 1 x TUG-3 mode of operation) and three TIFports.
LENTRONICS This unit is used at TN1Ue nodes where more than three TIFports are required
MULTIPLEXERS at a node. Each TUG-3 unit provides three additional TIFports. Thus, an
STM-N Aggregate unit with one TUG-3 unit provides six TIFports, an STM-N
Aggregate unit with two TUG-3 units provides nine TIFports etc.
TEST At a ring node, a pair of TUG-3 units is required to drop TU-1 traffic from a
TUG-3 port. The left TUG-3 unit is connected to a left CBW or TUG-3 port on
the left STM-t Aggregate unit through a cable. A similar connection is
TUG-3 PORT established between the right TUG-3 unit and the corresponding CBW or TUG-
3 Port on the right STM-N Aggregate unit.
ALARM
Each TUG-3 unit TIFport may be configured for either TU-11 or TU-12 mode of
ACK operation. The TU-12 mode of operation is used for E1 and Tie units while the
TU-11 mode is used for CMUX, CDAX or ETHER-10 units.
C.I. The Main tab of the unit's VistaNET view (Figure 82) displays status and
information about the unit and its TUG-3 port connections and allows the user
B86490-51 to make TU-1 assignments to the unit's TIFports.
TUG-3 UNIT
Figure 81: TUG-3 Unit TU-1 Status tab (Figure 83) provides status information for the TU-12s
Front Panel assigned to the unit's TIFports.
The TUG-3 units are installed in the slots 12 and 14 of a Common Equipment Shelf. An additional
Common Equipment Shelf is required for each pair of TUG-3 units. The space between the two TUG-3
units (slot 13) is unused.
Figure 82: TUG-3 Unit View – Main Tab Figure 83: TUG-3 Unit View – TU-1 Status Tab

TN1-86400-400PS
Issue 9.0
May 2017
Page 59
5 INTERFACE UNITS
5.1 Introduction
TN1Ue interface units are the modules designed to interface various customer equipment that is sending
and/or receiving traffic through the TN1Ue system. Based on the application type it is designed to
address, each interface unit belongs to one of the following categories:
 Ethernet applications
 VF (voice) applications
 Data applications
 Digital Telemetry applications
 Teleprotection applications
The following descriptions are intended to provide the reader with the basic functionality of each interface
unit currently available in the TN1Ue product line. More details on these units can be found in respective
Technical Practice and Installation Manuals. These manuals can be obtained from GE Multilin on request.
5.2 Ethernet Applications
5.2.1 ETHER-1000 Unit
The B86498 ETHER-1000 unit provides a bridging function between two or more Ethernet/IEEE 802.3
LANs that are physically separate. The ETHER-1000 unit addresses the applications where it is required
to provide more than 300 Mb/s of capacity between bridges, or the applications where its extended set of
features (compared with B86418 ETHER-100 and B86438 ETHER-10 unit) is the imperative.
LAN Segment C1 LAN Segment C2 LAN Segment D
LAN
Segment
E1
12345678 12345678
SWITCH P/B SWITCH P/B
Nx50 Mb/s
ETHER-1000 ETHER-1000
Nx50 Mb/s TN1Ue TN1Ue Nx50 Mb/s
NODE C NODE D
ETHER-1000
12345678
ETHER-1000
12345678
SWITCH P/B
SWITCH P/B
TN1Ue
TN1Ue
NODE B NODE E
LAN
Segment
B NODE A NODE F
Nx50 Mb/s
SWITCH P/B SWITCH P/B LAN Segment E2
12345678 12345678
LAN LAN LAN

Segment Segment Segment
A F1 F2
Figure 84: ETHER-1000

Figure 85: ETHER-1000 Ring System
Unit Front Panel
The unit acts as an intelligent bridge between the LAN segments, exchanging only those frames that are
not locally addressed. The MAC addresses of devices sourcing Ethernet frames are learned from the

TN1-86400-400PS
Issue 9.0
May 2017
Page 60
normal Ethernet traffic. The ETHER-1000 unit allows for bridging of Ethernet frames with up to 1632
bytes in length i.e. the unit is transparent for maximum size Ethernet frames that are either untagged or
tagged with single or multiple 802.1Q VLAN tags (up to 28 levels of QinQ nesting).
An ETHER-1000 unit is connected with one or more other ETHER-1000 units within a TN1Ue network to
form a point-to-point, linear or ring ETHER-1000 network topology. Ethernet ports of all ETHER-1000
units that make up such a topology create an Ethernet switch with geographically spread access ports (a
“distributed Ethernet switch”). An example of ETHER-1000 ring network topology is shown in Figure 85.
All devices connected to ETHER-1000 units at all six sites can exchange traffic through common
bandwidth (N x TU-3).
The unit is used with a multi-port paddleboard (86498-74) with built-in switch (“LAN” switch), which passes
traffic destined for remote ETHER-1000 sites to the local ETHER-1000 unit (“WAN” switch) via GMII port
(see Figure 86). The paddleboard can be equipped with one ETHER-1000 quad-port module and/or one
ETHER-100 quad-port module. These modules have dedicated locations (Banks A and B) on the
paddleboard. The ETHER-1000 quad-port module (86498-75) equipped with two 1000 Mb/s optical (SFP)
and two 100 Mb/s optical (SFP) Ethernet ports is presently the only module type that can be installed into
Bank B. Three types of ETHER-100 interface modules are available: 86498-81 module with four 10/100
Mb/s (built-in RJ-45) Ethernet ports, 86498-83 module with four optical 100 Mb/s (SFP) Ethernet ports.
The RJ-45 interfaces support auto-negotiation for data transfer speed (10 or 100 Mb/s) and mode (half or
full duplex). Alternatively, the user can disable auto-negotiation (on per-port basis) and configure the
mode and speed as desired. Optical ports can be flexibly equipped with SFP transceivers, as required.
Up to
24 x TU-3
Left Right
STM-16ETHER-100 STM-16
AGG AGG
A B C D E E D C B A
CBW
Up to 1.2 Gb/s FDX Ports
(24 x TU-3)
L R
ETHER-1000 Unit
("WAN" switch)
1 Gb/s FDX GMII

"LAN" SWITCH P/B
E1000 module E100 module
1000 Mb/s ports (FDX)

10/100 Mb/s ports (HDX/FDX)
100 Mb/s ports (FDX)
Customer Connections
Figure 87: ETHER-1000 paddleboard

Figure 86: Typical ETHER-1000 drop
with modules installed in both banks
The “WAN” switch performs a bridging function between the GMII port (interface to the paddleboard) and
its two (left and right) line ports. The line ports connect to STM-N Aggregate units’ CBW ports. At a ring
node or an add/drop node in a linear network, the left and right line ports are connected to both left and
right STM-N Aggregate units to allow bridging to/from both left and right fibre pairs. The SDH bandwidth
available for bridging through the line ports is user-configurable and can range from 50 Mb/s (1 x VC-3) to
1.2 Gb/s (N x VC-3, N=1…24). The unit can partition this bandwidth into as many as four TDM pipes.
Each provisioned TDM pipe can use from 50 Mb/s to 1.2 Gb/s of bandwidth, to a maximum total of 1.2
Gb/s for all provisioned TDM pipes (Figure 88). The ETHER-1000 unit has independent traffic forwarding
queues for each TDM pipe, which ensures that traffic carried in different TDM pipes will be independently

TN1-86400-400PS
Issue 9.0
May 2017
Page 61
queued within the unit. This feature allows for establishing “guaranteed SDH bandwidth” for selected
critical VLANs when multiple VLANs are handled by the same ETHER-1000 system.
Up to 24 TU-3s
grouped in up to
TDM Pipe #1 4 TDM pipes TDM Pipe #1
TDM Pipe #2 TDM Pipe #2

STM-16 STM-16
TDM Pipe #4 TDM Pipe #4
CBW Port CBW port
ETHER-1000
Figure 88: TDM pipes
The TDM pipes connected in ring topologies offer the capability for traffic/route diversity. Normally,
unicast traffic is routed to the destination port through the path with fewer ETHER-1000 hops and the
broadcast/multicast traffic is routed half way around the ring simultaneously in both clockwise and
counterclockwise directions in a “drop-and-continue” manner. If a failure occurs in a STM-N Aggregate
unit, or a fibre is damaged, affected traffic will be automatically rerouted to the other way around the ring
typically within 5 ms.
The ETHER-1000 unit can exchange traffic with remote ETHER-100 units (some restrictions apply).
Along each TDM pipe, an independent ETHER network topology, which may include a mixture of ETHER-
1000 and ETHER-100 units, can be created.
The “WAN” switch has a 32,768-entry MAC address table while the “LAN” switch has an 8192-entry MAC
address table. The aging time for learned MAC addresses is user-configurable and is ranging from 30
seconds to 1 hour or never. If an Ethernet device is moved from one site to another, the WAN MAC
address tables across the system are instantly updated.
A network of ETHER-1000 units supports up to 60 distributed port-based VLANs (“D-PVLANs”). D-

PVLANs #1-15 are carried in TDM Pipe #1, D-PVLANs #16-30 are carried in TDM pipe #2, D-PVLANs
#31-45 are carried in TDM pipe #3, while D-PVLANs #46-60 are carried in TDM pipe #4. Using VistaNET,
the user can assign membership in any one D-PVLAN to each of the 8 ports on the paddleboard. Ports
provisioned as PT trunks can have multiple D-PVLAN memberships (explained later). This feature
provides guaranteed isolation of traffic between ports with different D-PVLAN memberships i.e. broadcast
frames are contained within the same D-PVLAN. In the example shown in Figure 89, the ports connected
to LAN segments A, C1, D, E2 and F1 are configured for D-PVLAN=1 while the ports connected to LAN
segments B, C2, E1 and F2 are configured for D-PVLAN=2. This ensures that no traffic from stations in
D-PVLAN#1 can reach any stations in D-PVLAN#2 and vice versa.

TN1-86400-400PS
Issue 9.0
May 2017
Page 62
LAN Segment C1 LAN Segment C2 LAN Segment D

LAN
Segment
D-PVLAN=1 E1
D-PVLAN=1 D-PVLAN=2
12345678 12345678
SWITCH P/B SWITCH P/B
Nx50 Mb/s
D-PVLAN=2
NODE C NODE D
ETHER-1000
12345678
ETHER-1000
12345678
SWITCH P/B
SWITCH P/B
TN1Ue
TN1Ue
NODE B NODE E D-PVLAN=2

LAN
Segment
B
NODE A NODE F D-PVLAN=1
Nx50 Mb/s
SWITCH P/B SWITCH P/B LAN Segment E2
12345678 12345678
D-PVLAN=1 D-PVLAN=1 D-PVLAN=2

LAN LAN
LAN Segment
Segment Segment
F1 F2
A
Figure 89: D-PVLANs in ETHER-1000 system
The port-based VLAN feature is implemented without corrupting any ingressing frames’ 802.1p or 802.1Q
tags, thereby providing transparent transport of Ethernet traffic. The D-PVLAN information is encoded in a
proprietary tag called “envelope header” attached to each frame at its source ETHER-1000 unit and
removed at the destination one, so the frames can leave the ETHER-1000 system unchanged. Optionally,
the 802.1Q/p tags can be added or removed at the destination port if the port is set to do so.
The unit is capable of monitoring the (outer) 802.1Q VLAN IDs (“QVLAN IDs”) of the frames ingressing
and egressing each of its drop ports and, if the port's QVLAN-filtering feature is enabled, only the frames
whose (outer) QVLAN IDs are in the list of static QVLAN entries for the port will be processed (not
discarded). As a result, any ingressing broadcast and multicast traffic will be delivered only to those ports
that are members of the same D-PVLAN and QVLAN. A maximum of 50 QVLAN memberships in the
range from 1 to 4000 per can be assigned to a port.
QVLAN filtering for the port is enabled or disabled by means of selecting the proper Port Type option.
Ports provisioned as P-Access (PA) or P-Trunk (PT) ports do not support QVLAN filtering, while the ports
provisioned as Q-Access (QA) or Q-Trunk (QT) ports do. For ports with QVLAN filtering enabled (QA and
QT ports), any ingressing untagged (native) frames and 802.1p frames may be either discarded or
assigned the port’s Default QVLAN ID value, depending on the setting.
PA ports can exchange traffic only with remote PA and PT ports with matching D-PVLAN memberships,
while the QA and QT ports can exchange traffic only with remote QA and QT ports with matching D-
PVLAN and QVLAN memberships.
Only PT ports can have multiple D-PVLAN memberships. Each frame egressing a PT port has an added
802.1Q tag with the VID corresponding to its originating D-PVLAN. This is preset to 4000+(D-PVLAN ID#)
but can be modified to any VID in 1-4000 range (per D-PVLAN). The ingressing tagged frames are placed
into respective D-PVLANs based on the VID carried in their (outer) tag. The (outer) tag is removed on
ingress. Any untagged frames are blocked. Also, any tagged frames whose (outer) VID does not match
any of the VIDs associated with selected D-PVLANs are blocked.
Typical application examples for PT and PA ports are shown in Figure 90, Figure 91 and Figure 92.

TN1-86400-400PS
Issue 9.0
May 2017
Page 63
PA PA
PA PA PA PA
1
2 2 2
1 1
1 PT PT 1
JMUX Ring
TN1Ue Ring 11 JMUX Ring
TN1Ue Ring 12
2 2
2 1 2 1 2 1
Frames are Q-tagged with

PA PA VIDs corresponding to PA PA
PA D-PVLAN memberships PA
Figure 90: Tying multiple D-PVLANs through a P-Trunk
PA
PA PA
2 Trunk port
1 2
1 PT External 1 Access ports

JMUX
TN1UeRing
Ring1
2 Switch 2
2 1 2
Frames are Q-tagged with D-PVLAN membership
VIDs corresponding to
PA PA D-PVLAN memberships VLAN membership
PA
Figure 91: Distributing VLANs from external switch’s trunk port to D-PVLANs
PA
PA PA
Trunk port for
2 VLANs 1 & 2
1 2
1 PT
JMUX
TN1UeRing
Ring1 Router
2
2 1 2 Frames are Q-tagged with VIDs

corresponding to D-PVLAN
memberships.
PA PA All frames egressing the router port
D-PVLAN membership
PA typically have the same source MAC.
Figure 92: Distributing traffic from a router’s trunk port to D-PVLANs
The output tagging feature, is available in its generic form only to ports with QVLAN filtering enabled (QA
and QT ports). It allows for optional adding or removing the (outer) 802.1Q tags of the frames egressing
the port. Tagged frames can be outputted either unchanged or with the (outer) tag removed. Untagged
frames can be outputted either unchanged or with an added tag carrying the source port’s Default QVLAN
ID and Default Priority. Output Tagging mode is configured on per-QVLAN basis.
The main difference between Q-Access (QA) and Q-Trunk (QT) ports is that QA ports support only one
QVLAN membership per port (Default QVLAN ID) while the QT ports support up to 50 QVLAN
memberships (including the Default QVLAN ID) per port. Another notable difference is that the QA ports
can be set to allow ingress of non-tagged and/or tagged frames, while the QT ports always allow ingress
of tagged frames with optional ingress of untagged frames. Typical application examples for QA and QT
ports are shown in Figure 93, Figure 94 and Figure 95.

TN1-86400-400PS
Issue 9.0
May 2017
Page 64
QA QA
QA QA QA QA
102 101
101 102 102 101
1 1 1 1 1 1
101 QT 101
JMUX Ring
TN1Ue Ring 11 1 1 JMUX Ring
TN1Ue Ring 12
102 QT 102
1 1 1 1 1 1
102 102 101 101
101 102
QA QA QA QA
QA QA
QVLAN Memberships = 101,102
INGRESS
Output Tagging: Tag
Default QVLAN ID=102
(‘No Change’ is an alternative only if D-PVLAN membership
EGRESS
tagged frames appear on all ports.)
Output Tagging: QVLAN membership
- Untag (pop) if drop device is "native".
- Tag (push) if drop device is “Dot1Q”.
- ‘No Change’ can be used as an alternative to 'Tag' if only
tagged frames appear on all ports.
Figure 93: Multiple VLANs within a single D-PVLAN over multiple rings
QA
QA QA
102
101 102
1 1 1
101
101 QT External 101
JMUX Ring
TN1Ue Ring 1 1
102 Switch 102
102
1 1 1
102 102 All frames are tagged
101
QA QA
INGRESS QA
Default QVLAN ID=102
EGRESS QVLAN Memberships = 101,102
Output Tagging: Output Tagging: Tag
- Untag (pop) if drop device is "native". (‘No Change’ is an alternative only if
- Tag (push) if drop device is “Dot1Q”. tagged frames appear on all ports.)
- ‘No Change’ can be used as alternative to 'Tag' if only tagged
frames appear on all ports.
Figure 94: Connecting remote end devices to various VLANs on external switch trunk port
QA
QA QA
102
101 102
1 1 1
101 QT
JMUX Ring
TN1Ue Ring 1 1 Router
102
1 1 1
102 102 All frames are tagged.
101
Frames egressing router
QA QA typically have the same
QA
source MAC address.
Figure 95: Connecting remote end devices to various VLANs on a router port

TN1-86400-400PS
Issue 9.0
May 2017
Page 65
The ETHER-1000 unit allows for traffic prioritization which ensures guaranteed delivery of mission critical
traffic (high priority traffic is delivered with minimal latency regardless of the amount of competing lower-
priority traffic). To ensure this, the unit has a number of priority queues (Figure 96).
Egress "WAN"
Queuing 7+
Frames are outputted with SWITCH IN 7-
At destination site, frames are 6+

their original size and priority ETHER-1000 6-
information preserved or with "LAN" UNIT

queued into 8 priority queues
based on Mapping Priority
5+
5-
16
optionally added/removed SWITCH 4+ OUTPUT
designated at source site. 4-
PRIORITY
Q-tag (see Output Tagging ON P/B 3+ Egress
features). See NOTE below. 7 2+
3-
QUEUES
GMII port 2- (PER TDM
6 1+
PIPE) to/from
6-7 1- Left
Egress 4-5 8 5
4
0+
0-
Line Port
ETHERNET FRAME OUTPUT
2-3 PRIORITY 3
FRAME BUFFER Ingress
QUEUES 2
0-1
to/from 1
Paddleboard ET 0
Access Ports
6-7 7+
7-
4-5 6+
ETHERNET FRAME FRAME BUFFER 5+

6-
16
2-3 5-
OUTPUT
Ingress 4+
0-1
4- PRIORITY Egress
3+
3- QUEUES
2+
(PER TDM
2- to/from
PIPE) Right
Source Priority Mapping Priority Routing 1+
1-
• Value in 802.1p/Q priority field. (assigned for use within TN1Ue) Selection of TDM 0+ Line Port
0-
• Value in ‘TOS’ field of IP frame. =7 for selct'd EtherType frames. pipe is based on
• No priority (‘native’ frame), in For other frames, may be set source port's
FRAME BUFFER Ingress
which case the user-configurable (per port) for: D-PVLAN setting.
port's Default Priority is assumed. • Source Priority (with 76) Selection of Line Queuing
• Forced to N (N=1…6) • Forced to N (N=1…6). port (L or R) is Higher priority and NOTE: Any tagged "EtherType" frames are
NOTE: Selected EtherType frames based on minimum “Pass-thru” frames outputted
NOTE: with 802.1p/Q
The "LAN" priority
switch has set to 7.
with same priority Any tagged frames whose Mapping Priority
are using top-priority queue. [Forcing Mapping Priority forces number of hops to common ingress and egress
was forced to N are outputted
EtherType is set per port. Source Priority to same value.] destination. are mapped first. queues (total 4).
with 802.1p/Q priority set to N.
Figure 96: ETHER-1000 Unit Priority Queues
Each added frame is assigned a mapping priority (0 to 7, where 7 is the highest and 0 is the lowest
priority). The mapping priority is carried in the secure tag attached to each frame for transmission
between ETHER-1000 units. This tag is removed at the far-end unit's destination port. The mapping
priority may be set based on the frame's source priority (802.1p/Q tag or IP TOS field or, if neither is
present, user-defined default priority). Optionally, the user can force the mapping priority of all frames
ingressing the given access port to a specific priority.
Each paddleboard port is capable of detecting ingressing “mission critical” frames based on the frame’s
embedded EtherType code (e.g. 88b8 for GOOSE messages). All frames whose EtherType code is
matching the port’s EtherType setting will be treated as “super-priority frames” and they will be switched
through the highest priority queues in both “LAN” and “WAN” switches. Use of this feature guarantees
that the selected mission critical traffic is transported with the highest priority possible.
The “LAN” switch (residing on the paddleboard) has 4 priority queues. The ingressing frames with source
priorities 0/1, 2/3 and 4/5 are mapped into the three lower priority queues, respectively, while the top-
priority queue is used for the segregated EtherType traffic and frames with source priorities 6 and 7.
The ETHER-1000 unit (the “WAN” switch) has 16 priority queues (8 for “add” traffic and 8 for “pass-
through” traffic, denoted as “-“ and “+” queues, respectively, in Figure 96) for each TDM pipe on either
Line port. The unit also has 8 priority queues for the “drop” traffic passed to the GMII port (the port facing
paddleboard). The highest priority queue (within each set of 8) is reserved for “EtherType traffic”, while
the 7 lower priority queues are used for all other traffic.
Each “add” frame is directed for mapping into either the left or right line port signal based on the minimum
number of ETHER-1000 hops to its destination (broadcast/multicast frames are sent to both) and placed
into one of the eight "add" queues (belonging to the TDM pipe associated with its D-PVLAN membership)

TN1-86400-400PS
Issue 9.0
May 2017
Page 66
depending on its mapping priority. For "Pass-thru" frames, separate priority queues are used. Add and
pass-thru frames are then mapped into the line port signal using the following two principles:
 Higher priority frames are mapped first
 “Pass-thru” frames with same priority designation as “add” frames are mapped first
At the destination site, frames are queued into 8 priority queues and dropped accordingly (i.e. the frames
with highest mapping priority are dropped first).
For each queue shown in Figure 96, counts of outputted and discarded frames can be monitored through
the VistaNET software (see Figure 107).
GE recommends that the following priority assignments be used for various traffic types:
 Protection (relaying): Priority 6 (Note: 'GOOSE' frames shall be assigned
priority 7 using EtherType filtering feature)
 SCADA: Priority 5
 Metering: Priority 4
 Voice over IP: Priority 3
 Corporate LAN: Priority 2
 Misc. (e.g. deo): Priority 1
The unit provides around-the-ring latency monitoring for highest priority frames which allows the user to
estimate current end-to-end delay time for mission critical traffic (see Figure 97).
Figure 97: ETHER-1000 Unit View – Main Tab Figure 98: ETHER-1000 Unit View – Line Setup
The unit security mode can be set to High (default) or Low (see Figure 98). The unit in High Security
mode will allow non-administrators to configure/modify only the SDH-path related settings. Only VistaNET
administrators can change the unit security from High to Low.
For port security, the following features are available (see Figure 100):
 Remote port enable/disable
 Automatic port disabling on cable disconnect
 Blocking of unknown MAC addresses
 Intrusion detection
 Security status monitor

TN1-86400-400PS
Issue 9.0
May 2017
Page 67
The Off On Disconnect feature, ensures that the port will be disabled automatically as soon as cable
disconnect (loss of input signal) is detected. An alarm will be reported to the NMS (if the Alert feature for
the port is enabled). The alarm will remain latched until either the cable is re-connected and the port is re-
enabled or the Off On Disconnect feature for the port is disabled.
Figure 99: ETHER-1000 Unit View – Line Monitor Figure 100: ETHER-1000 Unit View – Port Setup
Tab Tab
Each of the eight ports on the paddleboard has a configurable learning mode. A port in No Blocking mode
will learn the MACs of all connected devices (up to an optional user-configurable limit). A port in Secured
mode has the MAC learning disabled. It will let communicate only those local devices whose MACs either
appear in the user-defined list of the port’s static MACs or had been learned before the port got secured
(pseudo-static MACs). Both static and pseudo-static MACs are stored in flash to allow for restoring
normal operation after unit reboot. The user can have as many as 20 static MAC entries defined per port
(see Figure 105).
If an unknown ingressing MAC address is detected on a secured port with intrusion detection feature
enabled, the MAC address will be treated as an intruder MAC and an alarm will be reported to the NMS (if
the Alert feature for the port is on). The alarm will remain latched until acknowledged by the user.
Rate limiting can be applied to traffic being inputted and/or outputted through the paddleboard ports. It is
individually configurable for each access port, and for each direction (input and output). The selectable
rate limit values range from 128kb/s to 800Mb/s (see Figure 102).
For input rate limiting, the user can define up to three rate limit values and respective sets of criteria
(rules) that will specify the frames to which the respective rate limit will be applied. Each set of criteria
includes the specific frame type(s) (unicast, multicast, broadcast) and source priorities. The frames that
do not meet any of the configured (up to three) sets of criteria are not rate limited.
Output rate limiting, if enabled, applies to all frames being outputted through the given port regardless of
their type (broadcast, multicast or unicast) and priority.
The user can determine the list of local MAC entries associated with any given D-PVLAN (to a maximum
of 138 entries) along with the information on which local port each or these MAC addresses is associated
with (see Figure 106).

TN1-86400-400PS
Issue 9.0
May 2017
Page 68
Figure 101: ETHER-1000 Unit View – Port Details Figure 102: ETHER-1000 Unit View – Port Details
Tab (example for RJ-45 port with default settings) Tab (example for optical port)
Figure 103: ETHER-1000 Unit View – VLANs Tab Figure 104: ETHER-1000 Unit View – VLANs Tab
(P-Trunk port example) (Q-Trunk port example)
The user can determine the list of MAC entries associated with any given D-PVLAN (to a maximum of 138
entries) along with the information on which port (“remote” or a specific local one) each or these MAC
addresses is associated with.
Port mirroring feature allows the traffic coming in or out of a local port to be mirrored on another local port
set as a monitor port. Multiple local ports can be mirrored on the same monitor port.

TN1-86400-400PS
Issue 9.0
May 2017
Page 69
Figure 105: ETHER-1000 Unit View – MAC Tab Figure 106: ETHER-1000 Unit View – MAC Tab
(entering static MAC entries) (monitoring MAC Table Entries)
Figure 107: ETHER-1000 Unit View – Passed Tab Figure 108: ETHER-1000 View – Advanced Tab

TN1-86400-400PS
Issue 9.0
May 2017
Page 70
5.2.2 ETHER-100 Unit
The B86418 ETHER-100 unit provides a bridging function between two or more Ethernet/IEEE 802.3
LANs that are physically separate. The ETHER-100 unit’s operation is similar to that of ETHER-1000 but
it cannot bridge more than 300 Mb/s of traffic and it does not provide as advanced set of features (limited
security, no GigE ports, no TDM pipes, no PVLAN trunking, no output tagging/untagging, no segregation
of mission-critical frames based on EtherType value etc).
LAN Segment C1 LAN Segment C2

LAN Segment D
LAN
Segment
LENTRONICS E1
MULTIPLEXERS 12345678
SWITCH P/B
L Nx50 Mb/s
ETHER-100 ETHER-100
R TN1Ue TN1Ue
Nx50 Mb/s Nx50 Mb/s
NODE C NODE D
12345678
ETHER-100
SWITCH P/B
ETHER-100
TN1Ue
TN1Ue
NODE B NODE E
LAN
ALARM
Segment
B NODE A NODE F
ACK Nx50 Mb/s TN1Ue TN1Ue Nx50 Mb/s
ETHER-100 ETHER-100
Nx50 Mb/s
SWITCH P/B LAN Segment E2
12345678
C.I.
LAN LAN LAN
B86418-01
A F1 F2
ETHER-100 UNIT

Unit Front Panel
The unit acts as an intelligent bridge between the LAN segments, exchanging only those frames that are
not locally addressed. The MAC addresses of devices sourcing Ethernet frames are learned from the
normal Ethernet traffic. The ETHER-100 unit allows for bridging of Ethernet frames with up to 1536 bytes
in length i.e. it is transparent for maximum size Ethernet frames with 802.1Q VLAN tag as well as nested
VLAN frames (up to four levels of QinQ nesting).
Regardless of the TN1Ue network topology used, at a node where Ethernet access is required (and the
choice is to use ETHER-100 rather than ETHER-10), one ETHER-100 unit and one paddleboard
assembly are required.
The unit performs bridging function between the MII port (interface to the paddleboard) and its two (left
and right) line ports. The line ports connect to STM-N Aggregate units’ CBW ports. At a ring node or
add/drop node in a linear network, the left and right line ports are connected to both left and right
Aggregate units to allow bridging to/from both left and right fibre pairs. The bandwidth available for
bridging through each line port can range from 50 Mb/s (1 x VC-3) to 300 Mb/s (N x VC-3, N=1…6).
An ETHER-100 unit is connected with one or more other ETHER-100 units in a TN1Ue network to form a
point-to-point, linear or ring ETHER-100 network topology. Ethernet ports of all ETHER-100 units that
make up such a topology create an Ethernet switch with geographically spread access ports (a
“distributed Ethernet switch”). An example of ETHER-100 ring network topology is shown in Figure 110.
All devices connected to ETHER-100 units at all six sites can exchange traffic through common bandwidth
(N x 50 Mb/s).

TN1-86400-400PS
Issue 9.0
May 2017
Page 71
The unit can be used with a single-shelf-slot-wide single-port paddleboard (equipped with one
10/100Base-TX interface) or with a two-shelf-slot-wide multi-port paddleboard with built-in 8-port switch.
The latter paddleboard can be equipped with one or two 4-port interface modules. Two types of interface
modules are available; one provides four 10/100Base-TX ports, while the other one can be equipped with
up to four 100Base-FX/LX ports with LC connectors (pluggable SFP transceivers). All copper interfaces,
including the one on the single-port paddleboard and those on the multi-port switch, support auto-
negotiation for data transfer speed (10 or 100 Mb/s) and mode (half or full duplex). Alternatively, the user
can disable auto-negotiation (on per-port basis) and configure the mode and speed as desired.
ETHER-100 units connected in ring topologies offer the capability for traffic/route diversity. Normally, the
unicast traffic is routed to the destination port through the path with fewer ETHER-100 hops, while the
broadcast/multicast traffic is routed half way around the ring simultaneously in both clockwise and counter-
clockwise directions in a “drop-and-continue” manner. If a failure occurs in an aggregate unit, or a fibre is
damaged, affected traffic will automatically be rerouted to the other way around the ring within 5 ms.
The ETHER-100 has a 4094-entry MAC address table that records MAC addresses of field devices
connected to the LAN. The MAC addresses of devices sourcing Ethernet frames are learned from the
normal Ethernet traffic. The aging time for learned MAC addresses is user-configurable and is ranging
from 4 seconds to 30 days or never. If an Ethernet device is moved from one site to another, the MAC
address table is instantly updated (as opposed to ETHER-10 unit where the respective MAC address entry
needs to be aged out before any Ethernet communication to/from the moved device can be established).
A network of ETHER-100 units supports up to 63 port-based VLANs (“PVLANs”)1. Through VistaNET, the
user can assign membership in any one (and only one) PVLAN to each drop port. This feature provides
guaranteed isolation of traffic between ports with different PVLAN membership assignments i.e. broadcast
frames are contained within the same PVLAN. In the example shown in Figure 111, the ports connected
to LAN segments A, C1, D, E2 and F1 are configured for PVLAN=1 while the ports connected to LAN
segments B, C2 , E1 and F2 are configured for PVLAN=2. This ensures that no traffic from stations in
PVLAN#1 can reach any stations in PVLAN#2 and vice versa.
LAN Segment C1 LAN Segment C2

LAN Segment D
LAN
Segment
E1
PVLAN=1 PVLAN=2 PVLAN=1
12345678
SWITCH
Nx50 Mb/s
ETHER-100 ETHER-100
PVLAN=2 NODE C NODE D

12345678
ETHER-100
ETHER-100
SWITCH
TN1Ue
TN1Ue
NODE B NODE E PVLAN=2
LAN
Segment
B NODE A NODE F PVLAN=1
ETHER-100 ETHER-100
Nx50 Mb/s
SWITCH LAN Segment E2
12345678
PVLAN=1 PVLAN=1 PVLAN=2
LAN LAN LAN
A F1 F2
Figure 111: PVLANs in ETHER-100 system
1 These are equivalent to ETHER-1000 unit’s D-PVLANs.

TN1-86400-400PS
Issue 9.0
May 2017
Page 72
The port-based VLAN feature is implemented without corrupting any ingressing frames’ 802.1p or 802.1Q
tags, thereby providing the transparent transport of Ethernet traffic. The PVLAN information is encoded in
the “envelope header” attached to each frame for transmission between the ETHER-100 units.
The unit allows for traffic prioritization which ensures guaranteed delivery of mission critical traffic (high
priority traffic is delivered with minimal latency regardless of amount of competing lower-priority traffic). To
ensure this, the unit has a number of priority queues (Figure 112).
7+
7-
6+
6-
5+
5- 16
4+
4- OUTPUT EGRESS
3+
3-
PRIORITY
7+ 2+ QUEUES
7- 2-
6+ 1+ To/From
6- 1-
Left Line Port
16 5-
5+ 0+
0-
EGRESS OUTPUT 4-
4+
PRIORITY 3-
3+
FRAME BUFFER
QUEUES 2+ INGRESS
2-
To/From 1-
1+
Paddleboard 0+
0- 7+
7-
6+
6-
FRAME BUFFER 5+
5-
16 EGRESS
INGRESS 4+ OUTPUT
4-
3+ PRIORITY
2+
3-
QUEUES
1+
2-
To/From
1- Right Line Port
0+
0-
FRAME BUFFER
INGRESS
Figure 112: ETHER-100 Unit Priority Queues
Each added frame is assigned a priority (0 to 7) so that it can be placed in a proper queue. The priorities
are assigned based on the value detected in 802.1p priority field, ‘TOS’ field in the IP (layer 3) frame, or
based on a user-configurable default priority (independently configurable for each port and applied only to
frames carrying no priority information). For all frames coming from the same port, the assigned priority
can be optionally:
 compressed up to elevate the priority
 compressed down to reduce the priority
 forced (to any of the 8 priorities).
Note that the frame prioritization is implemented without corrupting any 802.1p priority information on the
"add" frames nor the 802.1p tags are added to "native" (non-tagged) frames. The assigned priority
information is encoded in the “envelope header” attached to each frame for transmission between the
ETHER-100 units.
Each “add” frame (with priority assigned) is directed for mapping into left or right line port signal based on
the minimum number of hops to destination (broadcast/multicast frames are sent to both) and is placed in
one of eight "add" queues (denoted with suffix '-' in Figure 112) depending on the priority assigned to it in
the process described above. For "Pass-thru" frames separate priority queues are used (denoted with
suffix '+'). Add and pass-thru frames are then mapped into the line port signal using the following two
principles:
 Higher priority frames are mapped first
 “Pass-thru” frames with same priority designation as “add” frames are mapped first
At the destination site, frames are queued into 8 priority queues and dropped accordingly (higher priority
frames are dropped first).

TN1-86400-400PS
Issue 9.0
May 2017
Page 73
For each of the 40 queues shown in Figure 112, a count of the bytes outputted and a count of the packets
discarded can be monitored through the VistaNET software.
The unit provides around-the-ring latency monitoring for highest priority frames which allows the user to
estimate current end-to-end delay time for mission critical traffic.
Figure 113: ETHER-100 Unit View – Main Tab Figure 114: ETHER-100 Unit View – Line Tab
Figure 115: ETHER-100 Unit View – Port Figure 116: ETHER-100 Unit View – Port Details
Summary Tab Tab
To provide guaranteed security and dependability, the following has to be taken into account when the
ETHER-100 system is engineered:
 For complete isolation of traffic streams (security), port-based VLANs must be used.
 If the peak traffic can overload a link, traffic prioritization must be used. The peak of all the "no-lost-
packet" traffic must be lower than the SDH bandwidth assigned to the given ETHER-100 system.

TN1-86400-400PS
Issue 9.0
May 2017
Page 74
5.2.3 ETHER-10 Unit
The B86438 ETHER-10 unit provides a bridging function between two or more Ethernet/IEEE 802.3 LANs
that are physically separate. The unit acts as an intelligent bridge between the LAN segments,
exchanging only those frames that are not locally addressed. The MAC addresses of devices sourcing
Ethernet frames are learned from the normal Ethernet traffic. The aging time for learned MAC addresses
is user-configurable and is ranging from 6 seconds to 45 minutes. The ETHER-10 unit allows for bridging
of Ethernet frames with up to 1522 bytes in length i.e. it is transparent for maximum size Ethernet frames
with 802.1Q VLAN tag.
LAN Segment C LAN Segment D
LENTRONICS
MULTIPLEXERS
ON YEL ALM
ETHER ETHER 11 Mb/s ETHER ETHER
10 10 10 10
L TN1Ue R L TN1Ue R
11 Mb/s 11 Mb/s
NODE C NODE D
R L
ETHER ETHER
ETHER
ETHER-100
10
10
TN1Ue
TN1Ue
ALARM NODE B NODE E
ETHER
10
10
LAN
ACK Segment
L R LAN
B
NODE A NODE F Segment
E
11 Mb/s R L R L
TN1Ue TN1Ue
ETHER ETHER
C.I. 10 10 11 Mb/s
LAN
B86438-22 Segment
ETHER-10 UNIT A

Unit Front Panel
STM-N FIBER PAIR The ETHER-10 unit is software programmable to allocate

(N x 155.52 Mb/s)
between 1 and 7 TU-11s (1.6 Mb/s to 11.2 Mb/s) for inter-
TX RX TX RX
bridge data transport. This provides the user with the
LEFT RIGHT
STM-N STM-N capability to allocate bandwidth on demand. The unit
UNIT UNIT
interfaces a TIFport of an STM-N Aggregate or TUG-3 unit.
TU-12/TU-3
THROUGH-TRAFFIC The TIFport must be configured for TU-11 mode of operation.
P1 P2 P3 P1 P2 P3
If the unit is not using all seven TU-11s on the TIFport, it may
TIFport TIFport
(in TU-11 (in TU-11 be cascaded with another TU-1 level unit of TU-11 type
mode) mode)
(CMUX, CDAX or ETHER-10 unit) in order to maximize the
STATUS
TIFport utilization.
LEFT RIGHT
86438 ETHERNET 86438
ETHER-10 THROUGH-TRAFFIC In a ring network, two ETHER-10 units are equipped at each
ETHER-10
UNIT node where Ethernet access is required. Both units interface
UNIT
the local LAN segment and are "online" at the same time. The
LOCAL ETHERNET ETHER-10 units communicate with each other and determine
which unit is responsible for bridging to the remote site. An
Figure 119: ETHER-10 Drop ETHER-10 unit is designated for bridging with a remote site if
the path to the destination site requires fewer hops through
intermediate ETHER-10 units than its companion unit or if the companion unit is unable to reach the
remote site. Protection switching time is faster than 1 second.
The ETHER-10 unit dynamically determines the location of all sites on the ring. No user intervention is
required to establish connectivity between the sites. The user only has to ensure that each Ethernet site
in the ring/linear network is assigned a unique Site ID.

TN1-86400-400PS
Issue 9.0
May 2017
Page 75
The ETHER-10 unit provides the means of establishing logic sets of bridged LAN segments. This allows
LAN segments within the same set on the same ring/linear network to be bridged while preventing
bridging between LAN segments that are not in the same set. All units interfacing the LAN segments that
are bridged together must be configured with the same LAN identification.
Customer connections to the

local LAN can be established
through either a non-hubbing
or a hubbing paddleboard. If
a non-hubbing paddleboard is
used, both ETHER-10 units
sharing the same
paddleboard must be
independently connected to
the LAN using RJ-45
(10/100Base-TX) connectors
(Figure 120). There are two
hubbing paddleboard options;
Figure 120: ETHER-10 Unit Figure 121: ETHER-10 Unit one provides a single RJ-45
Non-Hubbing Paddleboard Hubbing Paddleboard connector while the other
provides two RJ45 and one
AUI interface (the latter one is shown in Figure 121). The AUI can be used to provide a variety of standard
10 Mb/s Ethernet interfaces through third-party transceivers.
The ETHER-10 can auto-negotiate with the Ethernet device connected to the local non-hubbing
paddleboard the maximum data transfer speed (10 or 100 Mb/s) and mode (half or full duplex). The
maximum allowed rate and duplex mode is user-configurable. When the connected device does not
support auto-negotiation, the unit uses the highest speed in half-duplex mode. Note that the bandwidth
available for inter-bridge transport is determined by the number of TU-1s assigned to the unit (max 11.2
Mb/s in each direction if 7 TU-1s are assigned) regardless of the interface mode selected. When a
hubbing paddleboard is used, only 10 Mb/s half duplex connections can be established.
Figure 122: ETHER-10 Unit View – Main Tab Figure 123: ETHER-10 Unit View – Ethernet Tab

TN1-86400-400PS
Issue 9.0
May 2017
Page 76
5.3 VF Applications
5.3.1 4W VF Unit
The B86444 4W VF unit provides the VF and E&M signalling interface between a 4W VF trunk and a
TN1Ue node. Unit options determine features and capabilities of the unit. The unit can be equipped with
either one or four DS0 channels. It provides E&M Types I…Type V signalling and supports programmable
on-hook and off-hook patterns for the signalling bits. Transmit and receive levels are software adjustable
between -17.5 and +6.5 dBm for transmit and -11.0 dBm and +10.0 dBm for receive. The adjustments
can be made in 0.1 dB steps.
Front panel LEDs provide indication of the state of E&M signals.
The unit has built-in signalling test capabilities and loopback features. When configured for E&M
signalling Type II, III, IV or V, it requires external -48VDC battery for proper operation. The unit is
equipped with two yellow LEDs per channel to indicate the state of E&M leads. Signalling setup and
loopback commands are available through the software.
The unit can be set to synthesize a 1 kHz test tone and send it to either the far-end or near-end VF output.
LENTRONICS LENTRONICS
MULTIPLEXERS MULTIPLEXERS
1
E M
2
3
4
E M
ALARM ALARM
ACK ACK
C.I. C.I.
B86444-08 B86444-28
4W VF E&M UNIT 4W VF E&M UNIT
Figure 124: 4W VF E&M

Figure 125: 4W VF Unit View
Unit Front Panel
The unit implements a circuit addressing scheme which prevents the unit from communicating with an
improper far-end unit. This feature is primarily used in tone teleprotection applications (Frequency Shift
Keying) where situations like signal loopback or signal receipt from an incorrect far-end device may
produce a false trip.
Customer connections are made on the unit paddleboard through its DB9 connector(s). Two paddleboard
options available for use with the 4W VF unit. The 86444-75 paddleboard provides four modular 8P8C
(RJ-45) connectors and it is normally used with the quad-channel unit option. It may also be used with the
single-channel unit option in which case only Port 1 is used. The 86444-71 paddleboard supports only
one channel (Port 1) and provides a DB9 connector for customer connections. It is normally used with the
single-channel unit option but it may also be used with the quad-channel option if only one channel is
needed.

TN1-86400-400PS
Issue 9.0
May 2017
Page 77
5.3.2 2W FXO and 2W FXS Units
The B86445-42 2W FXO (Foreign Exchange Office) unit provides the interface between four independent
2-wire VF lines with FXO (Foreign Exchange Office) signalling and a TN1Ue node. This unit requires use
of 2W FXS interface unit at the far end.
The B86445-32 2W FXS/PLAR unit provides the interface between two independent 2-wire VF lines with
FXS (Foreign Exchange Station) or PLAR (Private Line Automatic Ringdown) signalling and a TN1Ue
node. The unit is equipped with on-board ringing generator and talk battery for each VF line.
Both units can be configured for 2W line impedance of 600 or 900 ohms, with or without series
capacitance. They can also be configured for additional Network Build Out Capacitance (NBOC).
Front panel amber LED provides the unit's signalling status, while the bantam jack allows test-set access
to the VF channel on a bridging or splitting1 basis.
The units have built-in signalling test capabilities and loopback features. Signalling setup and loopback
commands are available through the software.
LENTRONICS LENTRONICS
MULTIPLEXERS MULTIPLEXERS
T/R BUSY1
BUSY2
1 2 T1/R1
BUSY
3 4 T2/R2
ALARM ALARM
ACK ACK
C.I. C.I.
B86445-42 86445-32
2W VF FXO UNIT 2W VF FXS UNIT
Figure 126: 2W Figure 127: 2W

FXO Unit Front FXS Unit Front Figure 128: 2W FXO Unit View
Panel Panel
Transmit and receive VF levels are software adjustable in 0.1 dB steps in the following ranges:
 B86445-42 2W FXO unit: -10 dBm to +3.0 dBm (transmit) and -12 dBm to +2.0 dBm (receive)
 B86445-32 2W FXS unit: -9.5 dBm to +5.0 dBm (transmit) and -15 dBm to +5.0 dBm (receive)
The loop current, talk battery voltage, and ringing voltage for the 2W FXS unit are 23 mA, -48 VDC, and
70 VAC (20 Hz), respectively. When the 2W FXS unit is configured for the PLAR mode, the ringing
duration is programmable and can be set to 10 sec, 20 sec, 60 sec or "indefinite".
Customer connections are made on the respective paddleboard through its DB9 connector. The 2W FXO
and 2W FXS units use different paddleboards.
1 Splitting is not applicable to B86445-42 unit.

TN1-86400-400PS
Issue 9.0
May 2017
Page 78
5.3.3 2W TO/E&M Unit
The B86449 2W TO (Transmission Only)/E&M unit provides the VF and E&M signalling interface between
a 2W VF trunk and a TN1Ue node. Unit options determine features and capabilities of each unit.
The E&M unit option can provide E&M Type I…Type V signalling. Transmit and receive levels are
software adjustable in -16.5 dBm to +6.5 dBm (transmit) and -21.5 dBm to +2.5 dBm (receive) ranges.
Front panel LEDs provide indication of the state of E&M signals, while a bantam jack allows test-set
access to the signalling channel. The second front panel bantam jack allows access to the VF signals on
a bridging or splitting basis.
The E&M unit option has built-in signalling test capabilities. Signalling setup and loopback commands are
available through the software.
LENTRONICS
MULTIPLEXERS
E M
ACK ALM
C.I.
B86449-
2W VF E&M UNIT
Figure 129: 2W E&M Unit Front Figure 130: 2W TO/E&M Unit View
Panel
The unit can be configured for 2W line impedance of 600 or 900 ohms, with or without series capacitance.
The unit can also be configured for additional Network Build Out Capacitance (NBOC).
Customer connections are made on the unit paddleboard through its DB9 connector.

TN1-86400-400PS
Issue 9.0
May 2017
Page 79
5.3.4 4W VF Partyline Unit
The B86474 4W VF Partyline unit provides a multipoint voice communications channel between any two
or more sites in the TN1Ue system via a 4-wire 600 balanced interface. The unit has a similar circuitry
to the Orderwire unit but it does not provide headset/telset connections and talk battery. A typical
application of the 4W VF Partyline unit is to provide a common communication channel for Remote
Terminal Units (RTUs) equipped with modems (in a SCADA network). The unit connects to the CSSU,
which provides the interface to the overhead bytes from both the right and left directions.
The 64 kb/s channel is carried by one of the Overhead bytes. A total of seven bytes can be selected to
carry VF Partyline channels and Orderwire channels in a TN1Ue system, i.e. up to seven independent
Orderwire/Partyline systems can be established within the same TN1Ue system.
A front panel test button can be used to test the visibility of the channel by sending a test signal.
The 4W VF Partyline unit can support the applications that require traffic to be tied across multiple
ring/linear networks.
LENTRONICS
MULTIPLEXERS
TEST
ACK ALM
C.I.
B86474-
4W VF Partyline Unit
Figure 131: 4W VF Figure 132: 4W Partyline Unit View

Partyline Unit Front
Panel

TN1-86400-400PS
Issue 9.0
May 2017
Page 80
5.4 Digital Telemetry Applications
5.4.1 Contact I/O Unit
The B86463 Contact I/O unit allows up to 16 external ("foreign") contacts to be replicated at a remote
location. A typical application is to transport rectifier alarms, door alarms, fire alarms etc. The unit
occupies one shelf slot and uses one 64 kb/s channel.
Each unit can be configured to operate in one of five modes:

● 16 inputs ● 4 inputs and 12 outputs
● 12 inputs and 4 outputs ● 16 outputs
● 8 inputs and 8 outputs
LENTRONICS Two Contact I/O units at two separate TN1Ue sites comprise a link and must be
MULTIPLEXERS set to complementary modes of operation.
Each unit has four I/O interface boards, each I/O interface board has 4 circuits.
The orientation of the I/O interface board determines whether the four associated
WARNING
CHECK
circuits are inputs or outputs. The mode of operation of the I/O interface board
INTERNAL must be implemented before insertion of the Contact I/O unit into a TN1Ue
SETTINGS equipment shelf and the function is automatically displayed in VistaNET software.
BEFORE
INSERTION
Input to the unit is an external contact closure. An external contact closure
ALARM causes about 5mA to flow through the solid-state opto-isolated switch. An
input can be configured through software as follows:
ACK
 Normally-open or normally-closed external contacts.
C.I.  “Alert” enabled or disabled. When an abnormal input condition on a
contact with alert enabled is detected, an alert will be raised (flashing red
B86463-01 LED on the unit and “channel alert” in the VistaNET software).
CONTACT I/O UNIT
Figure 133:  Idle-to-active delay time. All abnormal input conditions are “deglitched”,
Contact I/O Unit i.e. the abnormal input condition must be steady for a certain time before it
Front Panel is transmitted. Each input may be independently programmed over a
range of 0 ms to 65 sec.
Outputs are floating (opto-isolated) solid-state contacts capable of switching up to 100mA/350V AC/DC.
Each output follows the received signal and it can be configured through the software as follows:
 Normally-open or normally closed operation.
 Active-to-idle delay time, with a range of 0 ms to 65 sec.
 Under path failure condition to either hold the last received state or open the contact.
The unit uses a BC96 (4095 choices) address scheme between the two Contact I/O units in the link to
ensure that each unit is receiving the desired information.
Front panel LEDs provide indication of the status of the received DS0 signal at the near end, the status of
the far-end received DS0 signal, the status of the I/O interface boards, and the presence of any input
“alerts”.
Maintenance features which may be enabled through software include the following:
 Any input circuit can be "forced" to emulate a closed or open external contact.
 Any output circuit can be "forced" open or closed.

TN1-86400-400PS
Issue 9.0
May 2017
Page 81
5.5 Data Applications
5.5.1 DATA-LS Unit
The B86448 DATA-LS unit provides up to four 9.6 kb/s full-duplex asynchronous data ports along with four
end-to-end RS-232 control signals over a single 64kb/s channel. Data transmission is transparent,
regardless of baud rate, start, stop, or data bits.
The DATA-LS unit can be configured with one, two or four active data ports with maximum baud rates of
38.4 kb/s, 19.2 kb/s and 9.6 kb/s respectively. All ports will accept sub-multiple rates of the programmed
maximum baud rate. All four control lines are available regardless of the number of data ports configured.
The unit supports Local, Line, and Local+Line loopbacks that can be independently enabled for each of
the data ports. The B86448-03 unit has a built-in PRBS generator and PRBS analyser that can be used to
test the bit-error performance of the data channel or to measure round-trip delay of the data signal with no
need for external test equipment.
Front panel LEDs provide indication of data port activity and unit status.
LENTRONICS
MULTIPLEXERS
4
XMT RCV
ALARM
ACK
C.I.
B86448-03
DATA-LS UNIT
Figure 134: Data-LS

Figure 135: DATA-LS Unit View
Unit Front Panel
Total end-to-end delay (excluding

propagation delay in fibres and
through-nodes) is:
  0.5 ms @ 38.4 kb/s
  0.8 ms @ 19.2 kb/s
  1.5 ms @ 9.6 kb/s
Figure 136: RS-232 Connections

TN1-86400-400PS
Issue 9.0
May 2017
Page 82
5.5.2 DATA-PTM Unit
The B86465 DATA-PTM (Point-to-Multipoint) unit provides asynchronous RS-232 interface for transport of
data between multiple sites in a TN1Ue fibre-optic transmission system.
A typical application of the DATA-PTM unit is to provide a common communication channel for Remote
Terminal Units (RTUs) in a SCADA network. The master site is equipped with DATA-PTM unit configured
as a Master Terminal Unit (MTU) and remote sites are equipped with DATA-PTM units configured as
Remote Terminal Units (RTUs).
LENTRONICS
MULTIPLEXERS
XMT RCV
RTS RLSD
ALARM
ACK
C.I.
B86465-02
DATA-PTM UNIT
Figure 137: Data-PTM

Figure 138: DATA-PTM Unit View
Unit Front Panel
The units supports one point-to-multipoint data channel at maximum baud rate of 19.2kb/s. It also
accepts data at sub-multiple rates of its maximum baud rate.
Control lines supported are RTS, CTS, RLSD and DSR.
The unit occupies one shelf slot and uses two 64 kb/s channels on a CBUS in Share mode of operation.
All corresponding DATA-PTM units must be set to use the same 64 kb/s channels.
A DATA-PTM communication channel established in a ring or multi-ring TN1Ue system is protected

against single failure events in the system.
Front panel green LEDs allow monitoring of send and receive data activity as well as the control lines'
status. Alarm LED reports the unit alarm condition. The unit setup, status and port activity are also
reported via the VistaNET software.
Connections to external drop equipment can be either made via DB9 connectors or RJ-45 connectors
(different paddleboard options).
End-to-end delay is 0.8ms+(N-2)*350µs+L*5µs. N is the total number of DATA-PTM units in the loop
(using the same pair of 64 kb/s channels), and L is the total length of fibre in km.

TN1-86400-400PS
Issue 9.0
May 2017
Page 83
5.5.3 DATA-G703 Unit
The B86466 DATA-G703 unit provides the G.703 interface for transport of synchronous or plesiochronous
64 kb/s data signal with co-directional timing over a single 64 kb/s channel.
Front panel green LEDs allow monitoring of send and receive data activity at the data port. The red and
yellow LEDs report the alarm status of the local and far-end units respectively. The unit setup, status and
port activity are also reported via the VistaNET software.
The unit can be programmed for local loopback, line loopback, or local plus line loopback modes.
The unit's built-in PRBS generator and PRBS analyser can be used to test the bit-error performance of the
data channel or to measure round-trip delay of the data signal with no need for external test equipment.
The unit implements a circuit addressing scheme which prevents the unit from communicating with an
improper far-end unit.
LENTRONICS
MULTIPLEXERS
XMT RCV
YEL
ALARM
ACK
C.I.
B86466-01
DATA-G703 UNIT
Figure 139: Figure 140: DATA-G703 Unit View

Data-G703 Unit Front
Panel
Customer connections are made on the unit paddleboard through its DB9 connector. This includes Form-
C relay alarm connections that may be used to externally monitor the alarm status of the unit.
Total end-to-end delay for the DATA-G703 unit is 675s (excluding propagation delay in fibres and
through-nodes).

TN1-86400-400PS
Issue 9.0
May 2017
Page 84
5.5.4 DATA-NX64 Unit
The B86464-01 DATA-NX64 unit provides the V.35 interface for transport of a synchronous data signal
from 64 kb/s to 768 kb/s between two nodes in a TN1Ue fibre-optic transmission system.
The unit occupies one shelf slot and depending on the data rate selected may be configured to use from
one to twelve 64 kb/s channels. Both near-end and far-end units must be set to the same data rate and
use the same 64 kb/s channels.
LENTRONICS The unit may be configured either as DCE interface or DTE interface.
MULTIPLEXERS When configured as DTE the direction of data is opposite to when
configured as a DCE.
XMT RCV DATA-NX64 unit supports flexible clocking of data. Transmit timing may
YEL
be configured as INT (internal) or EXT (external). Receive Timing is
automatically set based on the mode of operation (DCE/DTE). Thus the
DATA-NX64 unit may operate as a co-directional interface or as a contra-
directional interface.
ALARM
The unit supports V.35 interface control lines. The control lines are local
ACK
and are not propagated through the TN1Ue system.
Front panel green LEDs allow monitoring of send and receive data activity
C.I. at the data port. The red and yellow LEDs report the alarm status of the
local and far-end units respectively. The unit setup, status and port activity
B86464-01 are also reported via VistaNET software.
DATA-NX64 UNIT
Figure 141: The unit implements a circuit addressing scheme which prevents the unit
Data-NX64 Front Panel from communicating with an improper far-end unit.
The unit can be programmed for local

loopback, line loopback, or local plus line
loopback modes.
The unit's built-in PRBS generator and PRBS

analyser can be used to test the bit-error
performance of the data channel or to
measure round-trip delay of the data signal
with no need for external test equipment.
Customer connections are made on the

paddleboard with DB25 connector or on the
paddleboard equipped with an Ethernet bridge
and RJ-45 connector. The paddleboard with
Ethernet bridge is used to support point-to-
point Ethernet circuits over up to twelve 64kb/s
channels (768 kb/s). .
Total end-to-end delay for the DATA-NX64

unit varies between 400s and 1200s,
depending on the selected data rate. These
values exclude propagation delay in fibres and
Figure 142: DATA-Nx64 Unit View
through nodes.

TN1-86400-400PS
Issue 9.0
May 2017
Page 85
5.5.5 T1/E1 Unit
The B86437-21 T1/E1 unit, when used in a TN1Ue system, provides the interface for seven separate
short-haul 2.048 Mb/s (E1) circuits to a TIFport on the STM-N Aggregate unit or TUG-3 unit. The TIFport
has to be configured for TU-12 mode of operation. If fewer than 7 E1 ports are used, the unit can be
cascaded with another TU-1 level unit of TU-12 type (T1/E1 or Tie unit) on the same TIFport to maximize
the TIFport utilization.
LENTRONICS At ring nodes, the T1/E1 units are equipped in

MULTIPLEXERS pairs to provide automatic path switching in case
T1/E1 of fibre or unit failure. A path priority is set up for
1 each E1 circuit during configuration so that the
2 other path is only used when a failure is detected
3 on the priority path. Protection switching is
revertive.
4
5 The E1 interfaces are labelled E1-1 to E1-7.
6 Each E1 signal is mapped into one TU-12. Each
7 E1 interface can be independently programmed
ON YEL ALM to support either HDB3 or AMI line code.
ACK
For each provisioned E1 port, the unit monitors
the locally received E1 signal for its presence,
for the presence of E1-AIS and for bipolar
C.I.
violations. The E1 signal status is reported
through the VistaNET software.
B86437-21
T1/E1 UNIT Front panel LEDs provide indication of the
received TU-12 signal, far-end received TU-12
Figure 143: T1/E1 Figure 144: T1/E1 Unit signal status, incoming E1 signal status and
Unit Front Panel Paddleboard whether the unit is on-line or off-line (for ring
configurations).
Figure 145: T1/E1 Unit View – Main Tab Figure 146: T1/E1 Unit View – E1 Tab

TN1-86400-400PS
Issue 9.0
May 2017
Page 86
The unit supports E1 loopbacks on the line and drop sides of the unit. These are configurable for each E1
port independently.
A built in VC-12 path test allows the integrity of an end-to-end VC-12 path to be confirmed. An E1-AIS can
be forced in either outgoing or incoming signal direction.
The unit has a built-in PRBS generator and PRBS analyser for each E1 port. When enabled, the PRBS
generator is producing a repetitive pseudo-random bit pattern that is replacing the port’s outgoing E1
traffic. The PRBS analyser can check if the incoming E1 signal carries the same PRBS pattern and, if so,
any mismatches will be detected and counted.
The user can define an up-to-20-characters-long alias for each T1/E1 unit’s drop port.
Customer connections to the T1/E1 unit are balanced 120 and they are made on the 86437-78
paddleboard’s DB37 connector (Figure 144).

TN1-86400-400PS
Issue 9.0
May 2017
Page 87
5.6 Teleprotection Applications
5.6.1 DATA-NX64F Unit
The B86464-02 DATA-NX64F unit provides the interface between a protective relay equipped with fibre-
optic interface designed per IEEE C37.94 standard and a TN1Ue node. The teleprotection data at bit
rates from 64 kb/s to 768 kb/s (in increments of 64 kb/s) is transported between two nodes in a TN1Ue
fibre-optic transmission system. The unit is end-to-end compatible with the DATA-NX64 unit.
The unit supports connection to the compliant teleprotection equipment via up to 2km long 50mm or
62.5mm multi-mode optical fibre. For longer spans, a single-mode fibre interface can be used.
LENTRONICS The unit occupies one shelf slot and, depending on the data rate selected,
MULTIPLEXERS uses one to twelve 64 kb/s channels of the 24 64kb/s channels available on a
CBUS. Both near-end and far-end units must be set to the same data rate
and use the same 64 kb/s channels.
XMT RCV
YEL
Front panel green LEDs allow monitoring of send and receive data activity at
the data port. The red and yellow LEDs report the alarm status of the local
and far-end units and the status of the signal being received from the local
drop equipment. The unit setup, status and port activity are also reported via
ALARM VistaNET software.
ACK
The optical fibre drop connections are made using the two “ST” connectors
on the unit paddleboard.
C.I. The unit implements a circuit addressing scheme which prevents the unit
from communicating with an improper far-end unit.
B86464-02
DATA-NX64F UNIT The unit can be programmed for local loopback, line loopback, or local plus
line loopback modes.
Figure 147:
Data-NX64F Front Panel The unit's built-in PRBS generator and PRBS analyser can be used to test
the bit-error performance of the data channel or to measure round-trip delay
of the data signal with no need for external test equipment.
Figure 148:
Data-NX64F
Unit Paddleboard
Figure 149: Data-Nx64F Unit View

TN1-86400-400PS
Issue 9.0
May 2017
Page 88
5.6.2 DTT Unit
The B86441-42 DTT unit provides two transmit and two receive trip circuits to an associated remote DTT
unit. The unit occupies two shelf slots and uses one DS0 channel.
Redundant opto-isolated keying loops provide enhanced dependability for the two input trip circuits. Two
"Active Tripping" outputs associated with respective input trip circuits are available for external trip
monitoring.
The unit may be configured for a variety of trip immunity times, trip extension times or minimum trip times
to suit the application.
Two opto-isolated solid state outputs (Main and Aux) are provided for each of the two output circuits. The
Main output is equipped with two series connected drivers for enhanced security.
A user-selectable address, matching the remote DTT unit, allows protection from network data crosses
and loopbacks. A 32-bit CRC checksum provides security against data corruption and false tripping logic.
Secure end-to-end testing is provided using optional Test Panels.
Form-C alarm contacts are provided for external monitoring in addition to status reporting via the
VistaNET software. When a DTT Test Panel is used, the unit paddleboard is wired to the Test Panel
where the customer connections are made. Otherwise, the customer connections are made on the
paddleboard.
The unit is immune to RFI and SWC on output circuits and alarm leads.
Figure 150: DTT Unit Front Figure 151: DTT Figure 152: False Trip Probability
Panel Paddleboard
The receiver will issue a desired trip if and only if a completely correct 96-bit frame is received. The
probabilities for various Bit Error Rates (BER) are shown in graphical form. For normal transmissions, the
probability of a false-trip is better than 10-72 which is zero for all practical purposes; and, even with a
continuous BER of 0.1 (worst-case), the probability is still only 10-16 which is once in 300,000 years.

TN1-86400-400PS
Issue 9.0
May 2017
Page 89
96-bit FRAME The incoming signal from the

far-end DTT unit is a continuous
8-bit TEST
synchronous bit stream. The bit
16-bit HEADER 24-bit ADDRESS 12-bit TRIP DATA 4-bit ALM 32-bit CRC-16 stream comprises contiguous
96-bit frames (Figure 153), with
the exception that an idle frame
OOOO11111111OOOO ACACACACACACACACACACACAC 111222333444 TCTCTCTC BCBC KCKCKC. . . .KCKCKCKCKCKCKC will be terminated early to speed
the transmission of a high
C = Complement of preceding bit priority (new trip) frame.
FRAME DURATION: 1.5 ms at 64 kb/s
Figure 153: BC96 Code
PARAMETER SPECIFICATION
Number of Input Circuits Two; each input circuit has redundant (main and aux) opto-isolated keying loops
Input Circuit Ratings 10 mA, 48/130/250 VDC (paddleboard options)
Spurious Trip Immunity 0.8 ms, 1.7 ms, 2 ms to 20 ms in 1 ms increments (software adjustable)
Transmit Trip Extension Times 6 ms to 180 ms in 6 ms increments (software adjustable)
Transmit Trip Minimum Duration 6 ms to 180 ms in 6 ms increments (software adjustable)
Alarm Relay Form-C Relay
Transmit Local Alarm Contacts Two Form-C Relays (one for each input circuit)
“Active Tripping” Contacts Four solid state relays, 5 A @ 150 VDC
Number of Output Circuits Two; each output circuit has two (Main and Aux) solid state contacts
Output Contact Ratings Main: 1A continuous (5A peak) @ 250VDC
Aux: 1A continuous (5A peak) @ 150VDC
Receive Trip Extension Times 0, 25, 50, 75...200, 300, 400...800 ms, 1.2, 1.6, 2.0, 2.4 sec (software adjustable)
Receive Trip Minimum Duration 0, 25, 50, 75...200, 300, 400...800 ms, 1.2, 1.6, 2.0, 2.4 sec (software adjustable)
Receive Local Alarm Contacts Two Form-C Relays (one for each output circuit)
Unit Alarm Contacts Form-C Relay
Max load: 350 V, 120 mA (350 mA for <10 ms); On-Resistance: 23 Ω (typ), 35 Ω (max)
End-to-End Delay 3 ms, excluding transmission delay
Table 8: DTT Unit Specifications

TN1-86400-400PS
Issue 9.0
May 2017
Page 90
5.6.3 DTT Test Panel
The B86429 DTT Test Panel is a tool that provides the user with the ability to test and maintain DTT links.
The Test Panel is wired directly to the DTT unit and all customer connections are made directly on the
Test Panel. The Test Panel requires external station battery and is capable of operating at various
voltages depending on the option chosen.
The Test Panel supports four DTT transmit and four DTT receive circuits. Each DTT circuit can be tested
individually so that it does not interrupt the remaining in-service circuits. The Main and Auxiliary Keying
Loops on the DTT unit are tested individually.
Receive output trip drivers can be energized locally to verify driver state. When any receive circuit is put in
test, the external DC trip circuit is removed and replaced with LEDs on the DTT Test Panel.
A transmit or receive switch that is not in the NORMAL position produces a contact closure on the test
panel ALARM terminal. This may be utilized for external monitoring of status of the test panel switches.
TRANSMIT RECEIVE
TRIP TRIP TRIP TRIP
MAIN AUX MAIN AUX MAIN AUX MAIN AUX
1 2 3 4
TEST TEST TEST TEST

TRIP TRIP TRIP TRIP
86429- AUX AUX AUX AUX LOCAL TRIP LOCAL TRIP LOCAL TRIP LOCAL TRIP
DTT TEST PANEL MAIN MAIN MAIN MAIN
ISSUE M2 TEST TEST TEST TEST
NO NO NO NORMAL NO NO NO NORMAL
CCT 1 CCT 2 CCT 3 CCT 4 CCT 1 CCT 2 CCT 3 CCT 4
Figure 154: DTT Test Panel (Front View)
RECEIVE TRANSMIT
MAIN TRIP AUX TRIP TEST MONITOR TEST MODE AUX LOOP MAIN LOOP
TO DTT-RCV (864X2-9X TB1) TO DTT-RCV (864X2-9X TB2) TO DTT-RCV (864X2-9X TB4) TO DTT-XMT (864X1-9X TB4) TO DTT-XMT (864X1-9X TB2) TO DTT-XMT (864X1-9X TB1)
8 P6 1 8 P11 1 9 P7 1 5 P5 1 8 P2 1 8 P1 1
MAIN TRIP OUTPUT RELAYS AUX TRIP ALARM BATT MAIN LOOP INPUT AUX LOOP
- 1 + - 2 + - 3 + - 4 + - 1 + - 2 + - 3 + - 4 + - + - 1 + - 2 + - 3 + - 4 + - 1 + - 2 + - 3 + - 4 +
1 16 1 5 1 16
TB1 TB2 TB4
Figure 155: DTT Test Panel (Rear View)
The test panel is two rack units in height (3.5", 89 mm) and mounts in a standard 19" rack.

TN1-86400-400PS
Issue 9.0
May 2017
Page 91
6 NETWORK MANAGEMENT
6.1 Introduction
This section contains Operations, Administration, Maintenance and Provisioning (OAM&P) functions
supported by the TN1Ue Network Management System (NMS). The NMS allows for remote monitoring,
testing and configuring of various common and interface units. Communication to different NEs in the
system is performed by sending encoded operation messages using dedicated bit-oriented channels
within the SDH network. For NMS transport, the user has three options. The first one is to select DCC
bytes in the STM-N signal's Section Overhead (SOH) i.e. the bytes recommended by ITU-T
Recommendation G.707 for this purpose. The second option is to select unused bytes of any TU-12
carrying no E1 traffic (i.e. a TU-12 that is either unused or carrying traffic originated at a TU-1 level unit of
TU-11 type). The third option is to select the unused VC-4 bytes (the second column of the VC-4 frame)
of one of the VC-4s carried in the STM-N signal. The last two options allow the NMS information to be
passed through any non-TN1Ue SDH transport nodes that may be used along with TN1Ue nodes in the
same ring or linear network to provide NMS visibility of all TN1Ue nodes. Note that the third option
requires the whole NMS-carrying VC-4 to be passed through all non-TN1Ue nodes, while the second one
requires only the NMS-carrying TU-12 to be passed through the non-TN1Ue nodes.
All NMS functions within a TN1Ue node are handled by its CSSU. The CSSU monitors alarms from
individual units and provides Major and Minor office alarm relays.1 An "Alarm Engine" in the NMS
software is tasked with handling all incoming alarms while displaying helpful information to the user for
assistance in maintenance and troubleshooting procedures.
The Network Management Software allows the user access to a series of powerful, menu driven, industry
standard (MS Windows) screens, which provide the user complete monitoring information and
configuration control of a TN1Ue system.
6.2 What is VistaNET

VistaNET is a complete peer-to-peer NMS solution for TN1Ue networks. It provides centralized
management capability of both contiguous and non-contiguous networks with the total number of nodes
ranging from a few to hundreds. The connection from a PC running VistaNET to a TN1Ue network can be
established through a direct cable connection, through a high-speed corporate LAN/WAN, or through a
traditional dialup link.
The VistaNET program can run on a PC running Windows 7, Windows 2008 server or Windows Vista.
6.3 Peer-to-Peer VistaNET Architecture

The term "peer-to-peer architecture" describes the concept of distributed computing by linking multiple
PCs together. VistaNET uses this approach to distribute processing resources across PCs so that
complete NMS solutions can be realized especially when connectivity to non-contiguous TN1Ue networks
is unavoidable.
Generally, VistaNET users have the choice of using VistaNET either as standalone users or in a peer-to-
peer architecture (multiple VistaNET PCs exchanging data through an Ethernet LAN).
1 At an E1MXe node, this function is provided by the CDAX unit.

TN1-86400-400PS
Issue 9.0
May 2017
Page 92
Standalone VistaNET PCs interact with TN1Ue multiplexers via logical point-to-point links to CSSUs.
When connected to a CSSU in Legacy mode, this link can be a serial (hardwire, modem) or a TCP/IP link.
For a CSSU in Secured mode, only a TCP/IP link can be used.
When implementing peer-to-peer distributed services, VistaNET must be installed on more than one PC,
with each of these PCs connected (or periodically connected) to a common Ethernet LAN. This approach
is primarily intended for users that are using VistaNET servers 1 to stream NMS data to remote VistaNET
sessions that reside on the enterprise network.
Each session of VistaNET contains two elements; the GUI (Graphical User Interface) and the local
VistaNET service. The GUI provides a windows-based user interface to VistaNET. The VistaNET service
is a background agent that performs multiple functions that include supporting serial connections to
TN1Ue units, identifying remote VistaNET services (other VistaNET sessions) and synchronizing data
between all available VistaNET services.
In both standalone and distributed services, VistaNET permits local provisioning of individual units through
a serial port on the local PC.
Ring 3
VistaNET
COM Port RS-232* VistaNET

RS-232* CSSU’s or IP link VistaNET
or IP link CI or
Ethernet VistaNET
port Ring 1 Ethernet
RS-232* LAN
or IP link
Ring
NMS VistaNET
RS-232*
Tie or IP link
VistaNET
Ring 2 Ring 4
Standalone Peer-To-Peer
VistaNET Operation VistaNET Operation
* Hardwire or Modem connection
Figure 156: VistaNET Deployment Options
6.4 Features
The NMS allows for remote monitoring, testing and reconfiguring of any node from any other node in the
system, which may include multiple rings and/or linear networks with spurs. A "check-back" before any
actual reconfiguration is used to ensure against incorrect configuration commands.
1 VistaNET server is a PC running VistaNET with a VistaNET Server Application (VSA) license(s) applied to one or
more of its logical point-to-point CSSU links (serial or TCP/IP).

TN1-86400-400PS
Issue 9.0
May 2017
Page 93
The NMS provides for simultaneous monitoring and configuration from more than one node. By allowing
multiple user access, maintenance personnel have real time information of the network for testing and
troubleshooting, as well as the potential of back-up control centres.
An industry standard graphical user interface (Microsoft Windows) for displaying the desired level of detail
is used. The software allows displays of information all the way from the STM-N optical receive levels, to
the state of DTT relaying channels, the current/voltage levels on the pilot wire interfaces, and activity on
data channel interface units.
Note: Some of the above features are optional and the system must be ordered as such.
6.5 Node Communications

The CSSU at each node constantly polls the local STM-N Aggregate and External Sync units for their
presence and summary status bits, generating a "node-view" packet for the node. This polling of the
STM-N Aggregate and External Sync units is done over a half-duplex 1 Mb/s Serial Peripheral Interface
(SPI) microprocessor bus.
In addition to this constant polling, the SPI bus is used for requests to STM-N Aggregate units for more
detailed status information on each unit at the node. The response from the units back to the CSSU can
be anywhere from 6 to 400 bytes. This information can be for any of the operating parameters of the unit
(i.e. received optical level), for any of the configuration bytes (i.e. priority direction) or status of a re-
configuration command.
6.5.1 STM-N Aggregate to TU-1 Level Unit Communications
This communication uses the overhead channel in the TIFport data link.
For each assigned TU-1, each STM-N Aggregate unit polls the appropriate TIFport to check that a TU-1
level unit is properly configured and healthy. The STM-N Aggregate unit keeps a 21-entry table for these
responses plus a summary TU-1 level status byte for the NMS system view icons.
When the NMS workstation operator desires more local TU-1 level unit information, the request/response
paths also use this channel.
6.5.2 CMUX/CDAX Unit to Channel Unit Communications
These communications use the overhead channel on the CBUS which connects these units.
An online CMUX/CDAX unit polls each of the 24 channel slots on each provisioned CBUS to maintain a
database of the equipped 64 kb/s level units and their status.
Further specific information is obtained, as required by NMS commands.
6.6 Intra-Ring Communications

The CSSU at each node communicates with the CSSUs at other nodes in the same ring/linear network
using one or more of the overhead bytes in the STM-N signal (each byte provides 64 kb/s). The NMS
packets are sent out on both left and right STM-N Aggregate unit optical outputs. It is the responsibility of
the destination node to resolve the arrival of duplicate packets. The receipt of every command packet

TN1-86400-400PS
Issue 9.0
May 2017
Page 94
"destined-for-here" has a sequence number and CRC. Prior to acting upon a command, the history
memory is searched for a matching unique ID and, if found, the command is discarded.
6.7 Ring-to-Ring Communications

For multi-ring NMS communications, each CSSU has two bidirectional NMS tie ports which connect to a
CSSU on another ring/linear network. At the collocated TN1Ue nodes (belonging to different ring/linear
networks) the NMS tie ports are connected through special NMS tie cables.
6.8 VistaNET Workstation Communications

The CSSU’s front Ethernet port is normally used for NMS communications to a local VistaNET PC via a
dedicated RJ-45 cable link. The unit’s rear Ethernet port (available on the paddleboard) supports one or
more NMS communication links to remote VistaNET PCs via an IP network.
For CSSUs operating in Legacy mode, NMS communications can be alternatively established through its
front and/or rear Craft Interface (RJ-11) ports. Each of these 9600 b/s serial ports can be used for an
independent hardwire or modem connection to a VistaNET PC.
6.9 VistaNET Unit Discovery

After the VistaNET software has been loaded and activated, and a valid NMS communication link to a
CSSU has been established, a discovery of the network inventory may be required.
An inventory discovery can be acquired through one of two mechanisms:

1. VistaNET administrators can click on the “Discover Network” button. Each unit is independently
discovered.
2. VistaNET services will “Synchronize” with remote services in a peer-to-peer distributed network to
update discovered data.
In both cases, the discovered data is stored locally to a local encrypted database file (H7engine.db3).
This file is updated with the results of any subsequent network rediscoveries. Obviously, the rediscovery
time is considerably different when comparing the two methods. Most VistaNET users will enjoy quick
rediscovery times automated by the interaction between VistaNET services across the organization’s
Intranet, while those that initiate a complete rediscovery must wait for each unit to be successfully
discovered. The latter discovery time is dependent on the number of rings, nodes and units within each
node.
The administrator can opt to discover/rediscover all visible nodes, a selected node or ring, or a range of
nodes across the same or multiple rings. Selective discovery/rediscovery is useful after node additions or
minor system modifications.
VistaNET will store the discovery results in a local database file, and display the results as a tree or map
(shown later) each time the program is started.
The VistaNET discovery process will detect each unit according to its unique provisioned traffic path. The
traffic path follows a specific syntax shown below:
Path = Ring / Node / Side / TUG-3 or CBW port / TIFport / TU-1 / Channel
(e.g. Ring 1 / Node 4 / Left / X / TP2 / TU5 / Ch13)

TN1-86400-400PS
Issue 9.0
May 2017
Page 95
6.10 VistaNET System Tree

With discovery complete, VistaNET builds a system tree of all units and their relationship with the rings
and nodes they reside within. The inventory tree can be expanded or collapsed to navigate through the
unit inventory.
As shown in Figure 157, the system tree is arranged into three distinct areas; the Local Connections, SDH
and E1MXe. When serial and/or Ethernet connections between the VistaNET PC and TN1Ue equipment
are established, the users will be able to interact with TN1Ue units through the tree. In addition to network
navigation, the tree provides the following functionality through its right-click menu:
 Assigning name aliases to units, nodes and rings
 Opening an additional unit display window (for reviewing near and far-end units concurrently)
 Acknowledging CSSU latched alarms
 Resetting the CSSU
 Setting the new maximum number of NMS packet hops in all CSSUs within the selected ring
 Refreshing the system tree and local serial connections
 Rediscovering the selected network entity (SDH node/ring/network or E1MXe group/network)
 Erasing the inventory for the selected network entity
 Logging into the gateway CSSUs operating in Secure mode
6.11 VistaNET Application Tabs

VistaNET is equipped with a series of application tabs that allow users to toggle between VistaNET tasks.
The task list includes:
 Alarms – displays current and historic alarm events with corresponding time stamps
 View – Depending on the selection in the system tree, displays one of the following:
o a unit form that allows unit monitoring, configuration and administration. Alternatively,
the user can display textual view of unit data-points and their values as well as the unit’s
serial number, firmware version and MAC address if applicable.
o summary status of the node along with some critical performance parameters and fibre
connectivity information
o visual representation of the ring status, fibre orientation and optical losses
o visual representation of the network status and tie locations between individual rings
 Inventory – allows the user to create system inventory reports
 Activity Log – shows a list of actions made by VistaNET users.
6.11.1 View Tab – Ring Map View
If a Ring label in the System Tree is selected, the View tab will display a graphical representation
of the nodes that belong to that ring.
The Ring Map View provides the user with the following capabilities:
 Facilities to sketch and design the ring layout
 Online monitoring of STM-N Aggregate, TUG-3 level, TU-1 level and 64kb/s level unit alarms
 Ability to select a node and "drill" down to the optical unit level
 Acknowledge CSSU latched alarms

TN1-86400-400PS
Issue 9.0
May 2017
Page 96
In the Ring Map View (Figure 157), the nodes belonging to the same ring or linear network are
represented with icons interconnected with lines illustrating respective fibre interconnects. Each node icon
is divided in two halves, one for the left and one for the right half of the common equipment. The upper
part of every node icon is coloured according to whether the left and right STM-N Aggregate units are
installed, whether the left and right External Sync units are installed, and how each STM-N Aggregate unit
at the node is synchronized. The lower part of the icon consists of three rows of fields. The top row is for
the STM-N Aggregate units, the middle row is for the TUG-3 level and TU-1 level units and the bottom row
is for the 64kb/s level units. Each "line level" field will display green for normal operation, red for fail
condition, amber for alert condition, blue for test condition and yellow for "far-end alarm" condition.
The timer interrupt for this window will initially ask the CSSU for the NODE-ICON-BYTES for all the nodes
and update the coloured areas of the icons accordingly; thereafter, the TIMER will ask for only any
changes. These bytes are also monitored by the VistaNET Alarm Engine.
The CSSU responds to these VistaNET requests from a database which the unit updates from the nodes'
broadcast NODE-ICON packets.
Program
System Icon Title Bar
Toolbar
Application
Tabs
System
Tree
Main
Display
Window
Utility
Toolbar
Figure 157: Ring Map View
VistaNET administrator can use the Ring Map View configuration tools to arrange the nodes in a ring or
linear topology (as they are positioned in the customer’s network), and then draw fibre paths between
nodes to represent the optical connectivity. The auto-connect right-to-left clockwise/counterclockwise
feature can be used in situations where the nodes are optically connected following the ascending Node #
(set in respective CSSUs). Also, the node icons can be auto-arranged in a symmetrical ring within the
main display window to make optimal use of the available space.
The descriptions of the Node Icon fields are available in Figure 158.

TN1-86400-400PS
Issue 9.0
May 2017
Page 97
1) LEFT AGGREGATE UNIT LOOPBACK (BLUE)

2) LEFT AGGREGATE UNIT RDI ALARM (YELLOW)
3) LEFT AGGREGATE UNIT STATUS (GREEN-HEALTHY,
AMBER-ALERT, RED-FAIL)
4) MAJOR ALARM (RED)
5) RIGHT AGGREGATE UNIT STATUS (GREEN-HEALTHY,
6) RIGHT AGGREGATE UNIT RDI ALARM (YELLOW)
7) RIGHT AGGREGATE UNIT LOOPBACK (BLUE)
8) LEFT TUG-3 / TU-1 LEVEL UNIT TEST (BLUE)
9) LEFT TUG-3 / TU-1 LEVEL UNIT RDI ALARM (YELLOW)
10) LEFT TUG-3 / TU-1 LEVEL UNITS’ STATUS (GREEN-HEALTHY,
22 23
11) MINOR ALARM (RED)
1 2 3 4 5 6 7 12) RIGHT TUG-3 / TU-1 LEVEL UNITS’ STATUS (GREEN-HEALTHY,
8 9 10 11 12 13 14 AMBER-ALERT, RED-FAIL)
15 16 17 18 19 20 21 13) RIGHT TUG-3 / TU-1 LEVEL UNIT RDI ALARM (YELLOW)
14) RIGHT TUG-3 / TU-1 LEVEL UNIT TEST (BLUE)
15) 64KB/S CHANNEL UNIT TEST (BLUE)
16) 64KB/S CHANNEL UNIT YELLOW ALARM (YELLOW)
17) 64KB/S CHANNEL UNITS’ STATUS (GREEN-HEALTHY,
ORANGE-ALERT, RED-FAIL)
18) NOT USED
19) 64KB/S CHANNEL UNITS’ STATUS (GREEN-HEALTHY,
ORANGE-ALERT, RED-FAIL)
20) 64KB/S CHANNEL UNIT YELLOW ALARM (YELLOW)
21) 64KB/S CHANNEL UNIT TEST (BLUE)
22) LEFT AGGREGATE OR EXTERNAL SYNC UNIT
TIMING STATUS (SEE BOTTOM OF RING
MAP VIEW FOR COLOUR CODE LEGEND).
23) RIGHT AGGREGATE OR EXTERNAL SYNC UNIT
TIMING STATUS (SEE BOTTOM OF RING
MAP VIEW FOR COLOUR CODE LEGEND).
Figure 158: Node Icon Description
6.11.2 View Tab – SDH Network Map View
If the SDH label in the System Tree is selected, the View tab will display a graphical
representation of the whole TN1Ue SDH system where each ring or linear network is represented
with a Ring icon showing the summary status of its nodes. These may be interconnected with
lines indicating traffic ties (Figure 159).
The SDH Network Map View provides the user with the following capabilities:
 Facilities to sketch and design the system layout and indicate the tie locations
 On-line summary status indication of STM-N Aggregate, TUG-3 level, TU-1 level and 64 kb/s level
units in each ring
 Ability to select a ring and "drill" down to the Ring Map View
 Acknowledge CSSU latched alarms
VistaNET administrator can use the configuration tools available in this view to arrange the ring icons and
draw the lines representing tie connections between ring icons to indicate tying locations.

TN1-86400-400PS
Issue 9.0
May 2017
Page 98
Figure 159: SDH Network Map View
6.11.3 View Tab – Unit View
When more details on a unit are required, the user can select the View tab and then select the
desired unit from the system tree, thereby opening up the Unit View (Figure 160). Any unit listed
in the system tree can be selected. Use the expand/collapse feature of the tree to locate desired
units. The unit view can be alternatively selected from the Inventory tab (if the unit is displayed in the
inventory list) or from the Alarms tab (if the unit produced an alarm entry).
Each unit form provides both configurable data-point fields and monitoring data-point fields.
Configurable fields are necessary to facilitate circuit provisioning, unit setup and maintenance tests. For
instance, through the VistaNET, the user can perform maintenance activities such as end-to-end TU-1
continuity tests or forcing TU-1s to switch to the back-up path (to verify that in the case of main path failure
the service would still be maintained). Any changes made in the configurable fields will not take effect
until after the Configure button is pressed. Multiple fields may be configured simultaneously. VistaNET
will allow users to provision changes on both left and right Aggregate / TU-1 level units simultaneously.
Furthermore, a copy/paste feature allows users to copy data-point values from a unit and paste them into
another unit of the same type thus reducing the provisioning time and increasing the accuracy of unit
configuration.
Monitoring fields typically provide an indication of unit status, counters and test/maintenance results.

TN1-86400-400PS
Issue 9.0
May 2017
Page 99
Figure 160: VistaNET Unit View for Data-Nx64F Unit
6.11.4 Alarms Tab (Alarm Engine)
The main function of the Alarm Engine is to record all alarms from the network so that they may
be reviewed and the problem correctly diagnosed. Alarms that are detected are time stamped
using the internal clock of the computer running VistaNET.
The alarm engine is arranged into two sub-tabs: the Current Alarms and Alarm History. Each new alarm
event detected is added to the Current Alarms tab which shows only presently active alarms. The Alarm
History stores all historical (cleared) alarms and synchronizes them with remote VistaNET services. A
complete alarm history will be created through this synchronization model.
The VistaNET Alarm Engine provides the user with the following capabilities:
 Online alarm and status information display
 Alarm logging and date and time stamping (automatically saved)
 Alarm acknowledgment
 Maintenance of an alarm history file
 Alarm filtering based on unit, node or ring
 Alarm history filtering based on a specific date or range of days
 Sorting of alarm entries based on date, severity, source etc.
 Alarm Set and Clear can be viewed in a sequence of events or consolidated together

TN1-86400-400PS
Issue 9.0
May 2017
Page 100
Figure 161: VistaNET Alarm Engine: Current Alarms
The user has the option to print off the alarms to a local or network printer.
The system tree and individual node/ring icons displayed in the Ring / SDH Network Map View also
interact with the alarm engine by changing icon colours to reflect the alarm state at the ring, node or unit
level. The combined status of all units at a node determines the status of the node and the combined
status of all nodes in a ring determines the status of the ring. RED depicts an alarm condition, while
GREEN is displayed for a healthy unit, node or ring.
Users can also sort the system tree by selecting the “Expand to Alarms” icon from the system icon toolbar.
The system tree will be expanded to show all tree paths that are declaring alarms.
6.11.5 Inventory Tab
The Inventory tab provides users with a quick and convenient method of checking and then
printing or saving the network inventory if so desired.
In the system tree, the user first selects the network entity (SDH network/ring/node or E1MXe
network/group/node) for which the inventory report will be created. The Inventory Summary window
displays all unit types found in the selected network entity at the time it was discovered along with the
respective counts of units. The user now has a choice to include all displayed unit types in the inventory
report or just a selection of them.
Additional information such as traffic allocations, serial number and firmware version can be included for
each individual unit included in the inventory report.

TN1-86400-400PS
Issue 9.0
May 2017
Page 101
In addition to having the inventory report viewed in the main display window, the user may choose to save
it as an xml file, print it on a local or network printer, or print it to a pdf file (if Adobe Writer is installed).
Figure 162: VistaNET Inventory
6.11.6 Activity Log Tab
The Activity log displays user activities performed with VistaNET (e.g. configuration changes
made to TN1Ue and E1MXe nodes, network discovery actions, user login/logout actions, etc.).
As shown in Figure 163 an activity log includes the following information:
Time: Time when the action was initiated

User: The user who initiated the action (if applicable)
Description: Brief description of the action
Path: The NMS path to the unit where the change was performed (if applicable)
Unit: The type of unit where the change occurred (if applicable)
Loc/NMS: The information on whether the action was performed locally or through NMS
Result: Result of action (success or fail)
IP: The IP address of the PC from which the action was initiated
Category: Type of action performed (Startup, Log In/Out, Unit Configuration, Discovery, etc.)
Duration: Time required by VistaNET to complete the action
The activity log for the last 60 days is synchronized between VistaNET services so any users running
VistaNET with synchronization enabled will contribute to building a complete log file. Entries older than 60
days are purged on VistaNET restart (locally only).

TN1-86400-400PS
Issue 9.0
May 2017
Page 102
Figure 163: Activity Log
The user can select a day or range of days for which the activity log will be displayed. Additionally, the
user can set various additional filtering options (Figure 164). The Tree Filter allows the user to focus only
on the selected network entity (SDH network/ring/node or E1MXe network/group/node). The Action
Category Filter filters out all entries that do not belong to the selected action categories. The Text Search
filter ensures that only the entries with specific text matches will be displayed.
Figure 164: Setting Activity Log Filtering Options
6.12 VistaNET Security

Generic security features like user password control and preventing database tampering have been
included in VistaNET.

TN1-86400-400PS
Issue 9.0
May 2017
Page 103
For security reasons, only one person or a small group of

people (VistaNET administrators) should be responsible for
managing user accounts and user group privileges/restrictions.
All VistaNET users must first login before unit configuration

changes or system software parameters may be altered.
VistaNET will prompt the user to start a configuration session
when he attempts to configure a unit data point or change a
system parameter (Figure 165). The appropriate security
restrictions, as employed by the administrator are then applied
to the configuration session. Figure 165: Login Dialog Window
6.12.1 VistaNET Security Management

VistaNET administrator is responsible for creating and maintaining VistaNET user accounts and
configuring user group restrictions. Furthermore, the administrator is responsible for customizing the look
and feel of VistaNET for his organization, coordinating the distribution of new VistaNET releases/updates
and integrating purchased VistaNET components. Finally, in networks equipped with CSSUs operating in
Secure mode, the administrator is responsible for configuring their security policies and managing access
control lists stored in the CSSUs.
The configuration security is applied in five ways:

1. VistaNET Authentication: A user must successfully authenticate himself to VistaNET before making
any configuration changes to TN1Ue/E1MXe nodes.
2. VistaNET Authorization: Configuration privileges are applied at the ring, node or unit type level for
each user group defined in VistaNET.
3. Hardware Authentication: To make a remote configuration change in a TN1Ue network equipped
with CSSUs operating in Secure mode, the user must authenticate itself to the CSSU hosting his
VistaNET connection.
4. Hardware Authorization: Any remote configuration change attempts in a TN1Ue network equipped
with CSSUs operating in Secure mode, are subjected to ring/node configuration privileges specified
for each user group defined within the given CSSU-S domain.
5. Encrypted VistaNET Communication: VistaNET link to a CSSU in Secure mode is encrypted.
VistaNET Authentication
VistaNET administrator must actively manage VistaNET

user accounts. Each user will need to log in with a correct
username and password before any configurable changes
to any TN1Ue/E1MXe unit are allowed. Managing the
VistaNET user account includes adding new users,
deleting existing users who do not require VistaNET
access, and changing user profiles when required. A new
user can be selected either from the Microsoft Active
Directory or from the list of local Windows accounts on the
local or remote VistaNET PC.
VistaNET Authorization
VistaNET administrator can restrict configuration of all

units or certain unit types at the network, ring or node
level. Also, different restrictions may be applied for Local
(unit craft interface) and NMS (remote) configuration
Figure 166: Managing user accounts
changes (Figure 167 and Figure 168).

TN1-86400-400PS
Issue 9.0
May 2017
Page 104
In the example in Figure 169,

there are two configuration
restrictions defined for a group
called SCADA. One is a local
configuration restriction for
CDAX units. Another one is an
NMS configuration restriction
for all unit types residing at
nodes in rings 1 and 2. Note
that each configuration
restriction needs to be added
separately.
Note: Configuration restrictions

cannot be applied to members
of the ‘Administrators’ group.
Administrators can grant

discovery privileges to any user Figure 167: Adding a local Figure 168: Adding an NMS
group. configuration restriction configuration restriction
Note: All users have visibility of all units at all

nodes regardless of their configuration
restrictions.
Hardware Authentication
Using the CSSU’s Web UI, the CSSI

administrator defines the Access Control List
that consists of Local and, optionally, RADIUS
users. The Local Users list will take effect only
if either RADIUS authentication is not used or
no RADIUS servers are presently available. Figure 169: List of defined restrictions
Each RADIUS user account consists of a username (must match the username in the external directory
used by the RADIUS server), account expiry date & time, and membership to a user group (all members
of the given user group share the same authorizations). The Local user accounts also include a password.
The CSSU administrator adds, modifies or deletes individual user accounts through the Web UI.
A user that successfully authenticated to a CSSU-S will be able to perform configuration changes within
the unit’s NMS domain based on his/her authorizations. Any authenticated user disconnected from the
unit for an extended period of time (default is 60 sec but configurable by the CSSU administrator) will have
to re-authenticate himself in order to perform any configuration changes within the unit’s NMS domain.
Hardware Authorization
Using the CSSU’s Web UI, the administrator can define User Groups whose members will share the
same access privileges to certain rings and nodes. There are also two predefined user groups; Global
RW (global read/write) and Global RO (global read only).
Upon CSSU login, the user’s authorizations (restrictions) defined in VistaNET are matched against the
authorizations defined in the CSSU. Any conflicts at individual ring/node level will be treated as denial of
configuration permission for the given ring/node.

TN1-86400-400PS
Issue 9.0
May 2017
Page 105
7 CONFIGURATIONS
7.1 Introduction
The TN1Ue system can be arranged to operate in many different configurations, all using the same
modular units. This permits easy and cost effective growth and migration between configurations.
For the STM-1 system, the optical gain ranges from 20dB@1310nm (Intermediate Reach) to
46dB@1550nm (Extra Long Reach-2) depending on the SFP transceiver option used (see section 4.6).
These operating margins correlate to typical maximum single-mode fibre distances of 30 and 200 km (19
and 125 miles), respectively. A transceiver for multimode fibre spans of up to 2 km is also available.
38dB@1550nm (Extra Long Reach-2) depending on the SFP transceiver option used (see section 4.5).
These operating margins correlate to typical maximum single-mode fibre distances of 15 and 160 km (9
and 100 miles), respectively. A transceiver for multimode fibre spans of up to 1 km is also available.
31dB@1550nm (Extra Long Reach) depending on the SFP transceiver option used (see section 4.4).
These operating margins correlate to typical maximum single-mode fibre distances of 15, 40, 80 and 120
km, respectively.
When a 1310nm unit Intermediate Reach SFP transceiver option is used, the optical receiver can be
connected directly to the laser source with no additional optical attenuators required. This may be useful
when the distances between adjacent nodes are extremely short as well as for system testing and
troubleshooting.
7.2 Standalone TN1Ue System

7.2.1 Ring Network
Ring topologies offer route diversity for all circuits. If a common unit such as an STM-N Aggregate unit or
CMUX unit fails, traffic is automatically rerouted to the alternate (backup, standby) path. Typical switching
time is < 3 ms.
Figure 170 and Figure 171 illustrate how traffic is rerouted and passed through a node when a fibre failure
occurs.
Traffic is transmitted along both paths but is only received from one of them. The path with lower end-to-
end delay is usually assigned as priority path. If the priority TU-1 path fails, TU-1 path switching takes
place within a pair of CMUX units and the traffic is received from the backup path. Although there are in
effect two CMUX units (one connected to the Left and one to the Right STM-N Aggregate unit), each
CMUX unit pair is shown as one unit. Traffic is passed through all nodes that may exist between the two
nodes originating/terminating the given TU-1 path. This node-through-delay for the TU-1 depends on the
type of STM-N Aggregate unit and it equals to 17 s for STM-1, 18 s for STM-4 and 23 s for STM-16
Aggregate units. The system reverts back to the priority path when the abnormal condition has been
corrected.
A detailed description of clock synchronization upon various failure scenarios is included in Section 8.

TN1-86400-400PS
Issue 9.0
May 2017
Page 106
TU-1 From/To Node B

CMUX
Channel
Units
STM-N STM-N
NODE A
TU-1 From/To Node A
CMUX
Channel
Units
STM-N STM-N STM-N STM-N
NODE B NODE C
Figure 170: Normal Configuration
TU-1 From/To Node B

CMUX
Channel
Cable Failure Units
STM-N STM-N
NODE A
TU-1 From/To Node A
CMUX
Channel
Units
STM-N STM-N STM-N STM-N
NODE B NODE C
Figure 171: Fibre Failure
7.2.2 Linear Add & Drop Network
TN1Ue nodes can also be configured in a linear network topology. This topology does not offer route
diversity in the event of an equipment failure or damaged fibre (Figure 172).
After a failure, traffic will still be maintained within the "islands" and one node for each island will source
the synchronization reference for that leg of the network.

TN1-86400-400PS
Issue 9.0
May 2017
Page 107
TN1Ue TN1Ue TN1Ue TN1Ue
NODE A NODE B NODE C NODE D
Example TU-1 Assignment:

(a) Normal Condition
NODE A - NODE B
NODE A - NODE C
NODE B - NODE D
NODE C - NODE D
NODE A NODE B NODE C NODE D

Example TU-1 Assignment: Traffic Maintained:
NODE A - NODE B (b) Failure Condition NODE A - NODE B
NODE A - NODE C NODE C - NODE D
NODE B - NODE D
NODE C - NODE D Traffic Terminated:
NODE A - NODE C
NODE B - NODE D
Figure 172: Linear Network
The following figure shows two nodes in a linear network. The left node is a terminal site where all the
circuits are dropped. The right node is an add/drop site where some of the traffic may be dropped and
other traffic added. Traffic from the terminal site that is not being dropped at the add/drop node is passed
through this node to be dropped and terminated at a different node in the network.
Terminal Node Add/Drop Node
Ether-1000
Voice
2W, 4W
Ether-1000 Ether-100 Ether-100
RS-232
64 kb/s STM-N AGG. STM-N AGG. STM-N AGG.

UNIT UNIT UNIT
N x 64 kb/s
STM-N STM-N
DTT T1/E1 T1/E1
CMUX UNIT Voice
(TU-11 MUX) 2W, 4W
CDR
DTT Ether-10
RS-232
Multipoint
CDR
Contact
I/O RS-232
Multipoint
T1/E1 CMUX UNIT
64 kb/s (TU-11 MUX)
Ether-10
N x 64 kb/s
CS Service Power Contact CS Service Power
Unit Supply I/O Unit Supply
Figure 173: Add and Drop Application in Linear Network

TN1-86400-400PS
Issue 9.0
May 2017
Page 108
7.2.3 Multiple Network System
A TN1Ue system can be made of multiple networks (rings, linear networks, and spurs). Traffic may be
passed between networks without leaving SDH either through TU-12 tie connections (using Tie units) or
through CBW tie connections (by interconnecting CBW ports of collocated nodes). Ethernet traffic may be
passed via Ethernet ties (by interconnecting ETHER-10/100/1000 unit paddleboard ports).
TN1Ue
TN1Ue TN1Ue
TIE TIE
TRAFFIC Ring # 1 TRAFFIC Ring # 2
TN1Ue TN1Ue TN1Ue TN1Ue TN1Ue
TN1Ue TN1Ue
TIE TRAFFIC
Note:
TIE TRAFFIC may include TU-12 tie, CBW tie, Vport tie and Ethernet tie connections.
Each ring/linear network may operate at different STM-N rate.
Figure 174: TN1Ue system comprising multiple rings, linear network and spur
Traffic between two adjacent rings may be optionally tied using dual homing configurations. Dual homing
refers to tying traffic between two rings at two tie points (Figure 175). Dual homing is implemented in
order to eliminate single point of failure created by a single tie site and to allow for establishing:
- Protected point-to-point circuits whose main and backup paths use different tie connections, and/or
- Virtual TUG-3 rings over two physical rings via two tie points.
Virtual TUG-3 ring
Site A
CBW-N Protected
point-to-point
circuit
Ring 1 Ring 2
CBW-N
Site B
Figure 175: Dual homing configuration

TN1-86400-400PS
Issue 9.0
May 2017
Page 109
64 kb/s traffic can be passed between remote TN1Ue networks using E1 links (Figure 176).
Foreign E-carrier/SDH CH 9
system or network (e.g.
E1 microwave radio link,
TN1Ue TN1Ue
leased E1 line etc.)
TN1Ue
TN1Ue
TN1Ue
TN1Ue
TN1Ue CH 6 CH 6 TN1Ue
CH 9 CH 6
Ring 1 CH 9 CH 9 Ring 2
CDAX unit’s CDAX unit’s

port in E1 mode port in E1 mode
TN1Ue E1 Link TN1Ue
CBUS
CH 6
Figure 176: Using E1 link to pass 64 kb/s traffic between remote TN1Ue SDH rings
7.3 TN1Ue and Foreign SDH Networks

TN1Ue can interoperate with foreign (non-TN1Ue) SDH equipment. Below are some typical network
configurations.
7.3.1 TN1Ue with Foreign STM-N Nodes in Same Network
DTT
Since the entire network needs to be
synchronized, use of the same
TN1Ue
synchronisation algorithm must be
ensured. Foreign STM-N multiplexers
Foreign Foreign are transparent for TN1Ue NMS
STM-N STM-N Ring STM-N E1 information (see Section 6.1).
MUX MUX
TN1Ue
DTT E1
Figure 177: TN1Ue and foreign STM-N multiplexers

operating in same ring
7.3.2 TN1Ue STM-N Ring Established Through a Higher Order SDH Network Capable of
Switching at VC-4 Level Only
When a TN1Ue network is used in conjunction with a non-TN1Ue higher-order SDH network it is normally
line-timed from the higher-order network. As all nodes in the TN1Ue system must be synchronous to
each other, the higher-order SDH network must also be synchronized.

TN1-86400-400PS
Issue 9.0
May 2017
Page 110
N x STM-1 (N≤16)
VIRTUAL RING STM-64 STM-64
ADM ADM
STM-64 Ring
STM-64 STM-64 STM-64
ADM ADM ADM
TN1Ue TN1Ue
TIE TRAFFIC TIE TRAFFIC
TN1Ue TN1Ue
TN1Ue TN1Ue
Figure 178: N x STM-1 virtual ring established through STM-64 backbone ring
The higher order SDH network is transparent for TN1Ue NMS information (see Section 6.1).
TN1Ue TN1Ue TN1Ue
N x STM-1 (N≤16) STM-64 STM-64 N x STM-1 (N≤16)

ADM ADM
STM-64 Ring
STM-64 STM-64
ADM STM-64 ADM
ADM
TN1Ue TN1Ue
TN1Ue Ring
TN1Ue TN1Ue TN1Ue
Figure 179: TN1Ue STM-N ring closed through STM-64 backbone ring

TN1-86400-400PS
Issue 9.0
May 2017
Page 111
7.3.3 TN1Ue STM-4 Ring Established Through a Higher Order SDH Network Capable of
Switching at VC-12 Level
The higher-order SDH network must be maintained synchronous to ensure the proper operation of the
TN1Ue in all single-point-of-failure scenarios.
E1
STM-16
STM-16 ADM STM-16
ADM ADM
STM-16 Ring
STM-16 STM-16
ADM STM-16 ADM
ADM
TN1Ue TN1Ue
STM-1 / STM-4 Ring
TN1Ue TN1Ue
E1
Figure 180: E1 circuit established between TN1Ue and non-TN1Ue SDH nodes
The higher order network is transparent for TN1Ue NMS information (see Section 6.1).
7.3.4 Applications with SDH Radio
One or more optical hops in an STM-1 TN1Ue network can be replaced with an STM-1 microwave radio
system (Figure 181).
TN1Ue TN1Ue
TN1Ue STM-1 Ring TN1Ue
TN1Ue TN1Ue
Figure 181: TN1Ue ring with microwave radio hops

TN1-86400-400PS
Issue 9.0
May 2017
Page 112
7.3.5 Two Parts of TN1Ue System Interconnected via VC-12 Cross-Connect
TN1Ue
STM-4 STM-1
...
TN1Ue
STM-1 STM-1
TN1Ue TN1Ue TN1Ue TN1Ue TN1Ue
TN1Ue
VC-12
Cross-Connect
TN1Ue
Figure 182: Two parts of TN1Ue system interconnected via VC-12 cross-connect
The Cross Connect must be synchronous to the TN1Ue system. The Cross-Connect is transparent for
TN1Ue NMS information, as long as at least one of the TN1Ue VC-12s being cross-connected is unused
or not carrying an E1 signal.
7.4 Applications with Backup Control Centre

As described in section 3.7, the Alternate Traffic Routing (ATR) feature allows the network administrator
using VistaNET to activate a pre-configured traffic routing alternative to redirect traffic normally routed to
the main control centre to the backup one.
7.4.1 Main and Backup Control Centres in Same Ring
Figure 183 shows the situation when the Main Control Centre is active. The optical aggregate units at the
Backup Control Centre are using configuration image #1. Note that only optical units at the Backup
Control Centre require two configuration images.
TN1Ue TN1Ue Main Control Centre
TN1Ue TN1Ue
SDH Ring
TN1Ue TN1Ue
TN1Ue TN1Ue
(Config Image 1)
Backup
Control
Centre
Active Control Centre
Figure 183: Main and backup control centres in same ring – normal operation

TN1-86400-400PS
Issue 9.0
May 2017
Page 113
If the Main Control Centre becomes unavailable, the optical aggregate units at the Backup Control Centre
are forced to use configuration image #2. Traffic normally routed to the Main Control Centre is now routed
to the Backup Control Centre.
TN1Ue TN1Ue Main Control Centre
TN1Ue TN1Ue
SDH Ring
TN1Ue TN1Ue
TN1Ue TN1Ue
(Config Image 2)
Backup
Control
Centre
Active Control Centre
Figure 184: Main and backup control centres in same ring – main control centre outage
7.4.2 Main and Backup Control Centres in Different Rings
To achieve full system redundancy, in the example shown in Figure 185 dual homing has been
implemented between the rings (not mandatory). The optical aggregate units at the Backup Control
Centre and all tie nodes require two configuration images. As long as the Main Control Centre is active,
the traffic is routed as per their configuration image #1.
TN1Ue
Main
Control
TN1Ue
Centre
(Config Image 1) (Config Image 1)
SDH SDH
Ring Ring

TN1Ue
TN1Ue Active Control Centre

(Config Image 1)
Backup
Control
Centre
Figure 185: Main and backup control centres in different rings – normal operation
If the Main Control Centre becomes unavailable, the optical aggregate units at the Backup Control Centre
and all tie nodes are forced to use configuration image #2. Traffic normally routed to the Main Control
Centre is now routed to the Backup Control Centre.

TN1-86400-400PS
Issue 9.0
May 2017
Page 114
TN1Ue
Main
Control
TN1Ue
Centre
SDH
SDH
Ring
Ring

TN1Ue
TN1Ue Active Control Centre

(Config Image 2)
Backup
Control
Centre
Figure 186: Main and backup control centres in different rings – main control centre outage
7.5 Mixed TN1Ue and E1MXe Networks

Two examples showing various applications with mixed TN1Ue and E1MXe networks are shown below.
Note that all TN1Ue and E1MXe nodes in such a mixed system can be managed through common NMS.
CH 20 Foreign
E1 Multiplexer
CH 7
E1
E1MXe
CH 14
E1
CH 20 CH 18
CDAX unit’s E1
CH 7 CH 9 CH 12
port in E1 mode
TN1Ue E1 E1
E1MXe E1MXe
CDAX
unit’s
port in
CH 6 CH 6 E1 mode
CH 2
TN1Ue
TN1Ue
TN1Ue CH 7 CH 7 CH 7
CH 9
Ring CH 9 CH 9
CH 20 E1
E1MXe E1MXe
CDAX unit’s
port in E1 mode Foreign E1
TN1Ue E-carrier/SDH
system or network
CH 6 CH 6 CH 12 CH 14
CH 11 E1MXe
CH 11 CH 2
CH 18
Foreign E1 Link
E1 Multiplexer CBUS
Figure 187: Mixed TN1Ue and E1MXe network – example with E1MXe spur and tree topologies

TN1-86400-400PS
Issue 9.0
May 2017
Page 115
CH 20 CH 7
CH 9
TN1Ue E1MXe
E1 E1
CH 14
CH 6
CH 2 TN1Ue CH 7
TN1Ue
TN1Ue
CH 7 E1 E1MXe
E1MXe
E1MXe
CH 9 SDH CH 12
Ring CH 9 Ring E1MXe
CH 20 E1
CH 14
CH 12
E1 E1
TN1Ue
E1MXe
E1 Link
CH 6 CH 2 CH 6 CBUS
Figure 188: Mixed TN1Ue and E1MXe network – example with E1MXe ring and spur topologies
7.6 Standalone E1MXe Networks

A network of E1MXe multiplexers with no links to CDAX units at TN1Ue nodes is referred to as a
standalone E1MXe network. As shown in Figure 189, such network may include one or more foreign E1
multiplexers.
CH 20 Foreign
E1 Multiplexer
CH 7
E1
E1MXe
CH 14
E1
CH 20 CH 18
E1 CH 9 CH 12
CH 7
CH 21
E1
E1
E1 E1MXe E1MXe
E1MXe
E1
E1
CH 6 CH 6
CH 2 CH 7
E1MXe
E1MXe
E1MXe E1 CH 7 CH 7 E1
CH 9
Ring CH 9 CH 9 E1
CH 20 E1MXe E1MXe
E1 Foreign
E1 E1
E-carrier/SDH
E1MXe
system or network
E1
CH 6
E1MXe CH 6 CH 12 CH 14
CH 11
CH 11 CH 2
CH 18
CH 21 Foreign E1 Link
E1 Multiplexer
CBUS
Figure 189: Standalone E1MXe network example

TN1-86400-400PS
Issue 9.0
May 2017
Page 116

TN1-86400-400PS
Issue 9.0
May 2017
Page 117
8 SYNCHRONIZATION, PROPAGATION DELAYS AND

SYSTEM ENGINEERING
8.1 Synchronization and Clocking

The internal clocks of all nodes in a TN1Ue system, which may include multiple contiguous ring and linear
networks, must be referenced back to a single clock source. In ring networks, proper sync distribution
must be maintained even in the case of a ring failure.
The reference clock is distributed from a node that is referred to as a "headend node" where it is either
generated by the node itself (i.e. by one of its aggregate units), or introduced externally (from a SASE,
digital exchange, or foreign PDH/SDH network element) as a 2.048 MHz timing signal or a traffic-carrying
E1 signal. When the reference clock is introduced to the headend node externally, the node must be
equipped with a (pair of) External Sync unit(s) (described in section 4.7). Configurations with primary and
secondary headend nodes are used when the system needs to remain referenced to a highly accurate
external clock even if the primary headend node becomes unavailable. These configurations are detailed
later in this section.
An STM-N Aggregate unit has two user-configurable parameters that determine its synchronization mode,
"Node Type" and "Sync Priority". The "Node Type" can be set to "Normal", "Slave", "Headend" or "CBW
Port p" (p=A, B, C, D, E)1 while the "Sync Priority" can be set to "Left" or "Right". These parameters are
configured identically at both left and right STM-N Aggregate units in most cases. The only exception are
tie nodes in dual homing applications where the Node Type on the left and right STM-N Aggregate units
may be configured differently (explained later).
The "Sync Priority" setting takes effect only if both STM-N Aggregate units are equipped at the node. This
parameter is included to provide compatibility with a similar option typically included in foreign SDH
multiplexers thus ensuring proper synchronization in networks comprising TN1Ue and foreign SDH
multiplexers. The "Sync Priority" is set the same on both STM-N Aggregate units and it is normally kept
defaulted (Left) at every node in the network. Note that left-to-right optical connectivity between adjacent
nodes within a ring or linear network needs to be maintained in order to ensure proper network
synchronization and traffic flow between certain interface units types.2
A TN1Ue node configured as "Headend" generates its own clock. The "Sync Priority" setting determines
which of the two STM-N Aggregate units (Left or Right) generates the reference clock. If the sync priority
unit fails (or is being replaced for maintenance), the non-priority unit takes over the clock generation task.
This clock is used to time the unit's outgoing optical signal as well as the local node through the 2kHz
shelf clock. The other STM-N Aggregate unit is "shelf timed", i.e. it is timed from the 2kHz shelf clock.
A "Normal" node derives the reference clock from the received STM-N line signal. Normally, one of the
STM-N Aggregate units is "line timed" while the other one is "shelf timed". Which of the two STM-N
Aggregate units (left or right) will be "line timed" is determined by comparing the SSM values in the
respective received optical signals. In the case when both signals carry the same SSM value, the "Sync
Priority" setting determines the optical signal used for timing.
1 For STM-1 Aggregate units, only CBW ports A and B are available.
2 If the system consists of multiple contiguous TN1Ue rings and CBW tie connections are used, the same optical
connectivity (e.g. clockwise left-to-right, as viewed from above) should be maintained in all rings.

TN1-86400-400PS
Issue 9.0
May 2017
Page 118
The reference clock is passed between two adjacent TN1Ue ring/linear networks at a site where the two
networks have collocated nodes. Generally, the clock can be passed using a 2kHz sync tie, intelligent
sync tie or CBW tie connection.
The 2kHz sync tie connection is established directly between the collocated nodes’ Common Equipment
Shelves and it is capable of passing the shelf clock without SSM in one direction only. Up to four
collocated nodes can be timed from a single node.
L R L R
H H N N
R L R L
N N S N
Ring 1 2kHz
Ring 2
N N S N
sync tie
L R L R
H = Headend
S = Slave
N = Normal
N N R N N L E = External Sync Unit
R L
Figure 190: 2kHz sync tie connection between two rings
An intelligent sync tie connection allows for passing the clock with embedded SSM in either direction
and it requires use of External Sync units at both ends of the tie link. The connections are made on
External Sync unit paddleboards. Only one intelligent sync tie connection can be established at a node.
A CBW tie connection is established directly between the collocated nodes’ STM-N Aggregate units and it
allows for passing TU-12s and/or TUG-3s from one ring or linear network to the other along with the
reference clock and SSM. Note that a CBW tie connection can be used for tying traffic only.
The type of sync tie connection used depends on the customer network design. 2kHz sync tie
connections are widely used in applications with single tie sites (no dual homing). Intelligent sync
tie connections are used in applications where the primary and backup headend nodes are
residing in different rings (Figure 201) and in some dual homing applications (Figure 192: Dual
homing application with intelligent sync tie at primary tie site
). CBW tie connections are widely used for tying network reference clock in dual homing
applications (Figure 191: Dual homing application with both tie sites configured for CBW port timing
and Figure 192: Dual homing application with intelligent sync tie at primary tie site
). Also note the following:
- TU-12 tie connections between Tie units (see section 0) can be established only at sites with either
2kHz sync tie or intelligent sync tie connections.1
- CBW tie connections and NMS tie connections established between CSSUs do not require sync tie
connections at the tie site as long as the two networks are timed from the same clock source.
1 Same applies to NMS tie connections established between legacy (B)86434-02 Service Units.

TN1-86400-400PS
Issue 9.0
May 2017
Page 119
A TN1Ue node is configured as "Slave" when it is timed through a 2kHz sync tie link or when External
Sync unit(s) are equipped at the node. At a "Slave" node, both STM-N Aggregate units are "externally
timed".
L R L R
H H N N
CBW
Port p
L R
N CBW
CBW-N
R L
N N N N
R L
Ring 1 Ring 2
N L R N
L N N R
CBW-N
N CBW
R L H = Headend
S = Slave
CBW N = Normal
Port p CBW = CBW Port p timing (p=A, B…)
N N R N N L E = External Sync Unit
R L
Figure 191: Dual homing application with both tie sites configured for CBW port timing
L N N R N N
CBW
Port p
L R
CBW-N
N CBW
R
S N N N
E R L
E Ring 2
S Ring 1 L R N
L S S
E Intelligent E
E Sync Tie E
S S
CBW-N
R L
S = Slave
N = Normal
CBW = CBW Port p timing (p=A, B…)
N N N N E = External Sync Unit
R L
Figure 192: Dual homing application with intelligent sync tie at primary tie site
In applications with single tie site using "CBW Port p" timing mode, both STM-N Aggregate units at the
node receiving the reference clock from the tie link are configured for “CBW Port p” mode. Both units
have their CBW port p independently tied to the collocated TN1Ue node’s STM-N Aggregate units. Under
normal conditions, the sync priority aggregate unit is timed from its CBW port p while its companion is
“shelf timed”.
In dual homing applications where “CBW Port p” mode is used at one or both tie sites, the STM-N
Aggregate unit facing the other tie site is set for “Normal” while the other aggregate unit is set for “CBW
Port p” mode. If the sync priority STM-N Aggregate unit is the one configured for “CBW Port p” mode, it is
normally timed from its CBW port p while its companion is “shelf timed”. On the other hand, if the sync
priority unit is the one configured for “Normal” mode, it is normally “line timed” while its companion is “shelf
timed”.

TN1-86400-400PS
Issue 9.0
May 2017
Page 120
8.1.1 Synchronization Status Messaging (SSM) Algorithm
TN1Ue nodes communicate clock integrity information to each other using a slightly modified ETSI SSM
(Synchronization Status Messaging) scheme which is described below.
Both left and right STM-N Aggregate units receive and transmit SSM messages. The SSM message is a
four-bit message contained in bits 5-8 of the S1 byte, as defined in ITU-T Recommendation G.707. This
message provides an indication of the quality level of the synchronization source of the SDH signal.
SSM S1 bits
G.707 meaning
Value (b5-b8)
0 0000 Quality unknown
1 0001
2 0010 Traceable to G.811
3 0011
4 0100 G.812 Transit Clock
5 0101
6 0110
7 0111
8 1000 G.812 Local Clock
9 1001
10 1010
11 1011 Traceable to G.813 Clock (SEC)
12 1100
13 1101
14 1110
15 1111 Do not use for synchronization
Table 9: SSM Values as per ITU-T Recommendation G.707
If a value of SSM=0 is received, it is processed as if it is SSM=15. The STM-16 Aggregate unit can be
alternatively set to process the received SSM=0 as the top quality SSM.
If an optical port receives any of alarms LOS, LOF, MS-AIS or OOF, it will present SSM=15 as its received
value to the processor.
When the Node Type is set to "Normal" on both aggregate units (if equipped) the node will synchronize
from the optical port which receives the lowest SSM value (highest quality level). If they have the same
SSM value, then the node synchronizes from the optical port that has been selected in the "Sync Priority"
field. If both received SSM values are 15 then the node synchronizes internally and sends SSM=11 out of
both ports. If the node is synchronized from the left optical port, the SSM value received from the left will
be transmitted out of the right optical port, and SSM=15 will be transmitted out of the left optical port.
Similarly, if the node is synchronized from the right optical port, the SSM value received from the right will
be transmitted out of the left optical port, and SSM=15 will be transmitted out of the right optical port. If
the node is synchronized internally (a ring failure scenario), SSM=11 will be transmitted out of both optical
ports.
Note that the above-described logic for “Normal” nodes applies only if both aggregate units at the node
are set for "Normal" mode. Actually, a sync-priority unit in "Normal" mode that has detected a companion
unit set for "CBW Port p" mode (which is the configuration used in some dual homing applications)
implements a more complex sync selection logic, which, in addition to the SSM values received from the
local optical input and from the companion unit, also checks where the companion unit is presently timing
from (see Normal – SP unit column in Table 10).

TN1-86400-400PS
Issue 9.0
May 2017
Page 121
When the Node Type is set to "Slave" (on both aggregate units, if equipped), and no External Sync units
are equipped, the node synchronizes from a 2kHz sync tie signal (from a collocated TN1Ue node) and
transmits SSM=8 (default) or the SSM value selected by the user (Force Xmt SSM) out of both optical
aggregate ports. If the External Sync units are equipped, the node synchronizes from the 2kHz sync
signal provided by the master External Sync unit. The master External Sync unit also controls the SSM
values transmitted from the left and right optical aggregate ports. If the 2kHz sync signal is lost, the node
will synchronize from its internal clock and will transmit SSM=11 out of both optical ports. After
approximately one second and once per second thereafter the node will check the SSM values received at
its optical ports. If a value of less than 11 is received then the node will act as if it is in "Normal" mode, but
will continue to sample its received SSM values and will return to its internal source if the received SSM
rises to 11 or higher again.
When the Node Type is set to "Headend" (on both aggregate units, if equipped) then the node
synchronizes internally and transmits a user-selectable SSM value (default is SSM=8) out of both optical
ports. The STM-N Aggregate unit internal clock accuracy is ±4.6ppm over the full operating temperature
range of the TN1Ue. The "Sync Priority" setting (Left or Right) at the Headend node determines which of
the two STM-N Aggregate units is timed internally (the other one is shelf timed).
When the unit's Node Type is set to "CBW Port p" (p=A, B, C, D, E), the logic for sync reference selection
between the CBW Port p input, Line (optical input), Shelf (companion unit), and Internal depends on
whether the unit is a sync-priority unit or not, whether the companion unit is present or not, and the
actual SSM values received from the CBW Port p input, from the local optical input and from the
companion unit. Generally, the unit synchronizes from the input on which it receives the lowest SSM. If
two or more inputs are providing the same SSM, the unit locks to the input with the highest designated
priority. The input's priority designation depends on whether the unit is a sync-priority (SP) or a non-sync-
priority (NSP) unit. Table 10 shows the input prioritizations used by SP and NSP units when configured
for "CBW Port p" mode. For comparison, the input prioritizations used by the units configured for
"Normal” mode are also provided.
CBW Port p (p=A, B, C, D, E) Normal

SP unit NSP unit SP unit NSP unit
CBW Port p 1 2
Shelf 2 1 2 1
Line 3 3 11 2
Internal 4 4 3 3
Table 10: Input prioritization on units in CBW Port p and Normal modes
When both aggregate units (if equipped) are set for "CBW Port p" mode, the sync-priority unit is normally
timed from the CBW Port p while the non-sync-priority unit is shelf timed. If the CBW Port p input on the
sync-priority unit fails, the node will attempt to time from the CBW Port p input on the non-sync-priority
unit. Failing that, the node will synchronize from its internal clock and will transmit SSM=12 out of both
optical ports.
When the Node Type is set to "CBW Port p" on one aggregate unit while the other one is set for "Normal",
it is assumed that this is a tie node in a dual homing application i.e. there is another tie site that can
provide timing for this ring. The sync-priority unit in "CBW Port p" mode is normally CBW Port p timed
(and its companion "Normal" unit is shelf timed), while the non-sync-priority "CBW Port p" unit is normally
shelf timed (and its companion "Normal" unit is line timed).
Figure 193 shows the sync distribution in a four-node TN1Ue ring with no failures. The Sync Priority
parameter at all nodes including the Headend is set for Left (default).
1 It will not line time if the companion unit is CBW Port p timed or line timed.

TN1-86400-400PS
Issue 9.0
May 2017
Page 122
Sync Priority: Left

HEADEND
STM-1 STM-1
R L
SSM=8 A-FIBRE SSM=8 A-FIBRE
REF
4.6ppm
SSM=8
SSM=15 B-FIBRE 2 kHz B-FIBRE
SSM=8 SSM=8
NODE 1
STM-1 6.48 STM-1
MHz
L DENOTES THE FIBRE R
Sync Priority: USED FOR SYNC 2 Sync Priority:
NODE 2 2 NODE 4
Left kHz kHz Left
STM-1 STM-1
6.48
R Sync Priority: Left MHz L
NODE 3
STM-1 STM-1
B-FIBRE L R B-FIBRE
SSM=15 6.48 SSM=15
A-FIBRE MHz 2 kHz
A-FIBRE
SSM=8 SSM=8
Figure 193: Reference clock distribution in a ring with no failures
Figure 194 shows the sync distribution in the same ring experiencing a cable failure.
Figure 195 shows the sync distribution in a ring where the Headend node is out of service (i.e. isolated
from the rest of the system).
Sync Priority: Left

HEADEND
STM-1 STM-1
R L
SSM=8 A-FIBRE SSM=8 A-FIBRE
REF
4.6ppm
SSM=15
SSM=15 B-FIBRE 2 kHz B-FIBRE
SSM=8 SSM=8
NODE 1
STM-1 6.48 6.48
MHz MHz STM-1
L DENOTES THE FIBRE R
Sync Priority: USED FOR SYNC 2 Sync Priority:
NODE 2 2 kHz NODE 4 Left
Left kHz
STM-1 STM-1
R Sync Priority: Left L
LOS
NODE 3
STM-1 STM-1
B-FIBRE L R B-FIBRE
SSM=8 SSM=8 2 kHz SSM=8
A-FIBRE LOS 6.48 A-FIBRE
MHz
SSM=15
Figure 194: Reference clock distribution in a ring with fibre failure

TN1-86400-400PS
Issue 9.0
May 2017
Page 123
Sync Priority: Left

HEADEND
STM-1 STM-1
R L
A-FIBRE SSM=8 REF LOS A-FIBRE
4.6ppm
SSM=11
B-FIBRE 2 kHz B-FIBRE
LOS LOS SSM=8
SSM=11 NODE 1 LOS
STM-1 STM-1
L R
DENOTES THE FIBRE
Sync Priority: 2 USED FOR REFERENCE 2 Sync Priority:
NODE 2 kHz CLOCK DISTRIBUTION kHz NODE 4 Left
Left
STM-1 NEW STM-1
R 6.48 REF L
MHz Sync Priority: Left
NODE 3
STM-1 STM-1
B-FIBRE L B-FIBRE
R
SSM=15 SSM=11 2 kHz SSM=11
A-FIBRE 6.48 A-FIBRE
MHz
SSM=15
Note: This figure shows the situation when the signal from Headend node is first lost at Node 2.
If the signal from Headend node is first lost at Node 4, the Node 2 provides new reference clock.
Figure 195: Reference clock distribution in a ring with headend node failure
8.1.2 External Sync Unit Application Examples
Below are some common application examples with the External Sync Units.
Note that the aggregate units at a node equipped with External Sync Unit(s) have the Node Type
parameter always set to Slave. This is because the master External Sync Unit provides the node with the
2kHz shelf clock regardless of the actual application. In the unlikely event when both External Sync Units
fail, the node clock will be provided by one of the aggregate units which will be either internally timed or
line-timed, depending on the SSM received on the aggregate inputs.
a) Applications with Single Headend Node Timed from External Sync Reference
Figure 196 shows a standalone TN1Ue system comprising two contiguous rings timed from an external
sync source. Only Node A is equipped with a (pair of) External Sync Unit(s). The master External Sync
Unit is presented with a maximum of two external sync signals (A-IN and/or B-IN). Each of the two inputs
can be fed by either a 2048 kHz sync signal (G.703/13) or a framed E1 (G.703/9) signal. The unit selects
one of the two inputs based on their health, incoming or assigned SSM, and priority setting. The selected
reference is used to supply the node with the clock. The SSM (2, 4, 8 or 11) associated with the selected
external input will be forwarded to both left and right aggregate units and asserted to the outgoing
aggregate signals.
Node A distributes the clock to other nodes in Ring 1, typically one way around the ring (default setting).
The aggregate units at all other nodes in Ring 1 have the Node Type parameter set to Normal. At each
Normal node, one of the two aggregate units is normally line timed. The sync signal is passed from Ring
1 to Ring 2 by means of a 2kHz sync tie link. The aggregate units at Node E have the Node Type
parameter set to Slave. The node is not equipped with External Sync Units. The aggregate units at other
nodes in Ring 2 are configured for Normal mode.

TN1-86400-400PS
Issue 9.0
May 2017
Page 124
D H
TIE SITE
Prim
A C E G
Sec 2 kHz
Sync Tie
(no SSM)
B F
Prim Primary External Sync Reference TN1Ue node equipped with External Sync Unit(s)
Sec Secondary External Sync Reference
TN1Ue node not equipped with External Sync Unit(s)
Figure 196: Application with single headend node (Normal State)
If the primary clock source at Node A becomes unavailable, the unit will switch to the secondary source
(Figure 197).
D H
TIE SITE
Prim
A C E G
Sec 2 kHz
Sync Tie
(no SSM)
B F
Figure 197: Application with single headend node (loss of primary sync input)
If both external sources at Node A become unavailable (Figure 198), the Master unit will go into Holdover
mode and will continue to supply the node with the clock. In this mode, the SSM=11 will be provided to
both aggregate units. If the Master unit fails or is forced to Sleep mode, the Standby unit will become a
new master.
Note that in this application, with reference to Figure 54, there is no need to provision the Line-L and Line-
R inputs as they should never be used for synchronization.

TN1-86400-400PS
Issue 9.0
May 2017
Page 125
D H
TIE SITE
Prim
HOLD
C E G
OVER 2 kHz
Sec
Sync Tie
(no SSM)
B F
Figure 198: Application with single headend node (holdover)
b) Applications with Main and Backup Headend Nodes Timed from External Sync Reference
Some applications require an alternate (backup) headend node i.e. presence of another site with access
to external sync references. The backup headend node may be located in the same or different ring with
respect to the main sync node. In either case, although equipped with External Sync Units, this node
would normally be line timed. To ensure this, the SSMs associated with the backup headend node’s
external sync references must be greater (lower sync quality designation) than those at the main headend
node during normal operation, but not greater than 8. This can be achieved by utilizing the Force SSM
feature. For example, if the main headend node’s external sync references have their SSM set to 2
(PRC), the backup headend node must have its external sync references’ SSMs set to 4 or 8.
Figure 199 shows the normal condition for the application with both main and backup sync nodes residing
in the same ring.
Main
Headend
Node
Prim Prim
A C TN1Ue node equipped
Sec Sec with External Sync Unit(s)
Backup
Headend
TN1Ue node not equipped
Node
with External Sync Unit(s)
B
Figure 199: Main and backup headend nodes in same ring (normal operation)
In the case when both external sync references at the main headend node are lost, its master External
Sync Unit goes into Holdover mode and asserts SSM=11 in both outgoing aggregate signals. Since this
SSM is now greater than the SSM associated with external references available at the backup headend
node, the primary reference at the backup headend node will be selected for local timing and its SSM will
be asserted in the outgoing aggregate signals. The master External Sync Unit at the main headend node
will observe that the new (lower than 11) SSM is received on one of the local aggregate inputs and will
perform a sync switch from holdover to line timing (Figure 200).

TN1-86400-400PS
Issue 9.0
May 2017
Page 126
Once at least one of the two external sync references at the main sync node is valid again, the master
External Sync Unit will switch back to it. Shortly, the backup sync node will become line timed again.
Note that, in addition to the external sync inputs, both main and backup headend nodes must have both
Line-L and Line-R provisioned.
Main
Headend
Node
Prim Prim
A C TN1Ue node equipped
Sec Sec with External Sync Unit(s)
Backup
Headend
Node TN1Ue node not equipped
B
Figure 200: Main and backup headend nodes in same ring

(loss of sync inputs at main headend node)
If there is a requirement to provide a backup headend node in an adjacent TN1Ue ring, both nodes at the
tie site must be equipped with External Sync Units with their Ports C interconnected. This establishes an
intelligent sync tie connection between the two rings which is capable of passing both timing and SSM
signals in either direction (Figure 201a and Figure 201b).
D H
TIE SITE
Prim Prim
A C E G
Sec Intell. Sec
Sync Tie
(with SSM)
B F
(a)
D H
TIE SITE
Prim Prim
A C E G
Sec Intell.
Sec
Sync Tie
(with SSM)
B F
(b)
Figure 201: Main and backup headend nodes in different rings: (a) normal operation;
(b) loss of sync inputs at main headend node

TN1-86400-400PS
Issue 9.0
May 2017
Page 127
NOTE: If the rings with main and backup headend nodes are not adjacent, all sync tie connections on the
sync path between the main and standby nodes must be “intelligent”.
NOTE: If there are multiple collocated nodes at a site (all belonging to different ring or linear networks), all
sync tie connections that are not on the “main-to-standby sync node path” should be the standard ones
(non-intelligent).
NOTE: A tie node supporting an intelligent sync tie connection may be used as a main or backup headend
node; however, in that case it cannot support more than one external sync reference. This is because it is
not possible to have both B-IN and C-IN provisioned (see Figure 54).
c) Timing External Equipment with TN1Ue System Clock
A (pair of) External Sync Unit(s) can be used to provide TN1Ue clock to external (non-TN1Ue) network
element (e.g. digital exchange, foreign PDH/SDH node etc.) using the A-OUT and/or B-OUT sync outputs.
For this application, the output(s) should be configured to generate a 2048 kHz (G.703/13) signal,
unframed E1 signal, or framed E1 signal. Which of these output interface options will be chosen depends
on the type of interface used by the external non-TN1Ue equipment. Also, the Selector C (Figure 54)
should be set for Shelf (T0) to ensure that the clock used for shelf timing also drives the external sync
output(s) regardless of whether a line signal or a local external sync reference is currently used for timing.
Prim Foreign
A C SDH Network
Sec
TN1Ue node equipped with External Sync Unit(s)
Figure 202: Timing external network element with TN1Ue clock
In the example shown in Figure 202, Node C provides a collocated foreign SDH network element with a
clock synchronous to the external reference clock selected for the TN1Ue system timing at Node A. Both
A-OUT and B-OUT can be simultaneously connected to the foreign network element if redundancy of
external sync inputs is required.
d) Timing TN1Ue Network From a Traffic-Carrying E1 Signal
In some applications with CDAX units, a TN1Ue network needs to be timed from a traffic-carrying E1
signal. A typical example is the application shown in Figure 176 where the two rings need to be in sync in
order for the E1 circuits inside the E1 link to operate. The easiest way to ensure this is to time one of the
two rings from the other one through the E1 link itself. For example, if Ring 2 is timed from Ring 1, the E1
signal fed to the CDAX unit pair in Ring 2 is also fed to a (pair of) External Sync units (see Figure 203).
Note that it must be ensured that the timing quality of the E1 signal carrying the sync reference for an SDH
network does not drop below SEC accuracy in any failure scenario.

TN1-86400-400PS
Issue 9.0
May 2017
Page 128
E1-out
C
E1-in C TN1Ue
E ring
C CDAX Unit
E
E External Sync Unit
Sync Reference Path
Figure 203: Timing TN1Ue ring from traffic-carrying E1
d) Filtering Accumulated Jitter Using External SASE Equipment
A (pair of) External Sync Units, in conjunction with SASE, can be used to filter the excessive jitter
accumulated along the sync paths with very large number of nodes in order to allow for more nodes to be
synchronized downstream. The node clock built in SASE (normally a G.812 clock) has better jitter filtering
capabilities than the clock built in External Sync Units (a G.813 Option 1 clock). Note that using the
External Sync Unit’s SETG (see Figure 54) for the jitter filtering function does not make sense since the
aggregate units use the clock with same jitter filtering capabilities.
SASE
D
A B C E F
TN1Ue node equipped with H J

External Sync Unit(s)
TN1Ue node not equipped

Figure 204: Filtering accumulated jitter using external SASE equipment
In the example shown in Figure 204, the sync signal derived at Node D from the aggregate signal received
from Node C is supplied to the SASE and returned to the External Sync Unit with significantly reduced
amount of jitter. This clock is then selected for the shelf clock (T0). As a result, the sync reference
forwarded downstream (to Nodes E and G) will have better jitter performance than the one received from
Node C.
For this application, with reference to Figure 54, the Selector C must be set for Line while the Line-R and
Line-L must be unprovisioned as it must never be selected for shelf timing by the selector B (note that
Line-L and Line-R provisioning applies to the Selector B only).

TN1-86400-400PS
Issue 9.0
May 2017
Page 129
8.1.3 Clock Distribution in Mixed TN1Ue and E1MXe Networks
All network elements involved in originating, cross-connecting and terminating individual 64 kb/s and N x
64 kb/s circuits must be synchronized. Consequently, the E1MXe nodes/networks “attached” to a TN1Ue
network through CDAX units must be timed from the TN1Ue network.
E1MXe
Headend
TN1Ue TN1Ue
JungleMUX SONET Ring

SDH Ring
TN1Ue TN1Ue TN1Ue
CDAX at TN1Ue node

E1 link
64 kb/s circuit
E1MXe E1MXe
Sync reference
E1MXe E1MXe E1MXe
Figure 205: Synchronizing mixed TN1Ue and E1MXe networks
8.1.4 Clock Distribution in Standalone E1MXe Networks
One node in a standalone E1MXe network (E1MXe Master) is designated to originate and distribute the
reference clock to all other E1MXe nodes in the network. The E1MXe Master is typically configured to
time internally but it can also time from a SASE or traffic-carrying E1 signal originated from a foreign E1
multiplexer.
Master
E1MXe
E1MXe
E1MXe
E1MXe E1MXe
E1MXe Ring E1MXe
E1MXe E1MXe
E1MXe
E1MXe
E1MXe
E1MXe
E1 link
E1MXe
Sync reference
Figure 206: Clock distribution in standalone E1MXe network

TN1-86400-400PS
Issue 9.0
May 2017
Page 130
As shown in Figure 207, a standalone E1MXe network whose one or more E1 links are tunnelled through
an SDH or E-carrier network is timed independently from the network through which its E1 links are
tunnelled.1
SDH Master
Standby E1
Path SDH ADM SDH ADM
SONET Ring
SDH Ring
SDH ADM SDH ADM SDH ADM

Online E1
Path
E1 tributary interface
E1MXe E1MXe E1MXe Ring E1MXe E1 link

SDH sync reference
E1MXe sync reference
E1MXe
E1MXe E1MXe E1MXe E1MXe
Master
Figure 207: Clock distribution in standalone E1MXe network with an E1 link “tunneled” through SDH
8.2 Propagation Delays

Since certain types of utility traffic require minimal delays between path ends, the TN1Ue node-through
delay has been kept to a minimum. When a TU-12 signal is passed through an STM-1 node, it
experiences a delay of 17.2 s (Figure 208). At STM-4 and STM-16 nodes, the TU-12 pass-through delay
is 18 and 23 s, respectively (Figure 209 and Figure 210). A TU-1 signal added/dropped on a TIFport
configured for TU-11 mode experiences a delay of 10.2s/19s. If a TU-1 signal is added/dropped on a
TIFport configured for TU-12 mode, these delays are 7.2s/16s. The CMUX unit causes another
10.2s/19s of delay to add/drop a standard TU-11. Each 64kb/s level interface unit will have its own
delays associated with it. The light propagating in the fibre experiences a delay of about 5 s/km.
When a 64kb/s channel from a shared TU-11 is dropped or passed through, the corresponding delay in
the CMUX unit varies between 5 and 125 s and cannot be controlled. Therefore, use of SHARED TU-11
mode shall be carefully considered for delay sensitive applications.
A TU-1 added/dropped through a TUG-3 unit’s TIFport experiences approximately the same delay as a
TU-1 added/dropped through an STM-N Aggregate unit’s TIFport.
If a CDAX unit is used instead of CMUX unit, refer to Table 11 for the relevant delay information.
1 “E1 tunneling” assumes no 64kb/s channel access or 64kb/s-level cross-connections along the tunneling path.

TN1-86400-400PS
Issue 9.0
May 2017
Page 131
Voice Voice
2W, 4W 2W, 4W
DTT DTT
CDR CDR
RS-232 STM-1
STM-1 AGG.
AGG. STM-1 AGG. STM-1 AGG. RS-232
STM-1 STM-1
64 kb/s 64 kb/s
CMUX CMUX
N x 64 kb/s CMUX CMUX N x 64 kb/s
CONTACT Pass-through 64kb/s channel path CONTACT

I/O I/O
(when carried in Shared TU-1)
DS1 JIF-DS1
DS1
ETHER-100 ETHER-100
CMUX STM-1 AGG. STM-1 AGGREGATE UNITS STM-1 AGG. CMUX

UNIT UNIT (THROUGH-DELAY) UNIT UNIT
ADD: 7 s ADD TU (TIFport,TU-11): 10.2s STANDARD TU-1: 17.2 s ADD TU (TIFport,TU-11): 10.2s ADD: 7 s
DROP (STD TU): 7 s DROP TU (TIFport,TU-11): 19s SHARED TU-1: 94 60s DROP TU (TIFport,TU-11): 19s DROP (STD TU): 7 s
DROP (SHR TU): 65 60s ADD TU (TIFport,TU-12): 7.2s ADD TU (TIFport,TU-12): 7.2s DROP (SHR TU): 65 60s
DROP TU (TIFport,TU-12): 16s DROP TU (TIFport,TU-12): 16s
ADD TU (CBW PORT*,TU-12): 4.2s ADD TU (CBW PORT*,TU-12): 4.2s
ADD TU (CBW PORT**,TU-12): 12s ADD TU (CBW PORT**,TU-12): 12s
DROP TU (CBW PORT,TU-12): 13s DROP TU (CBW PORT,TU-12): 13s
ADD TU-3: 2.4 s ADD TU-3: 2.4 s
TU-3: 6.4 s
* In TU-12 TIE or DROP TU-3: 4.0 s DROP TU-3: 4.0 s
TU-12 DROP mode
** In CBW-N mode FIBRE PROPAGATION DELAY: 5 s / km
Figure 208: Propagation delay through an STM-1 TN1Ue system

Voice Voice
2W, 4W 2W, 4W
DTT DTT
CDR CDR
RS-232 STM-4 AGG. STM-4 AGG. STM-4 AGG. RS-232
STM-4 STM-4
64 kb/s 64 kb/s
CMUX CMUX

I/O I/O
DS1 JIF-DS1
DS1
ETHER-100 ETHER-100

ADD: 7 s ADD TU (TIFport,TU-11): 10.2s STANDARD TU-1: 18s ADD TU (TIFport,TU-11): 10.2s ADD: 7 s
ADD TU-3: 2.4 s ADD TU-3: 2.4 s
TU-3: 8 s
* In TU-12 TIE or DROP TU-3: 4.0 s DROP TU-3: 4.0 s
TU-12 DROP mode
** In CBW-N mode FIBRE PROPAGATION DELAY: 5 s / km

TN1-86400-400PS
Issue 9.0
May 2017
Page 132
Voice Voice
2W, 4W 2W, 4W
DTT DTT
CDR CDR
RS-232 STM-16 AGG. STM-16 AGG. STM-16 AGG. RS-232
STM-16 STM-16
64 kb/s 64 kb/s
CMUX CMUX

I/O I/O
DS1 JIF-DS1
DS1

ADD: 7 s ADD TU (TIFport,TU-11): 10.2s STANDARD TU-1: 23s ADD TU (TIFport,TU-11): 10.2s ADD: 7 s
* In TU-12 TIE or
ADD TU-3: 5.5 s**/2.4 s*** ADD TU-3: 5.5 s**/2.4 s***
TU-12 DROP mode TU-3: 8 s
** In CBW-N mode DROP TU-3: 4.0 s DROP TU-3: 4.0 s
*** In TU-3 TIE or
TU-3 DROP mode FIBRE PROPAGATION DELAY: 5 s / km
Data Delay (s)

Delay type From (port) To (port)
Typ Max
64 kb/s Drop TIF Drop (Bulk Drop mode) 10 10
TIF Drop (Share Drop mode) 200 260
TIF Drop (E1/Optic mode) 305 375
64 kb/s Add Drop (Bulk Drop mode) TIF 5 5
Drop (Share Drop mode) TIF 5 5
Drop (E1/Optic mode) TIF 120 120
64 kb/s Through TIF TIF 75 150
(both units)
DS0 Hairpin Drop (Share Drop mode) Drop (E1/Optic mode) 310 375
Drop (E1/Optic mode) Drop (Share Drop mode) 185 250
Drop (E1/Optic mode) Drop (E1/Optic mode) 310 375
Table 11: CDAX unit delays
8.3 System Engineering

All customer purchased systems are completely engineered down to the 64 kb/s level. Shelf layout,
channel assignments, TU-12 assignments and synchronization are all engineered and documented for
future customer reference. This allows for either GE Multilin or the user, to add to or modify the existing
system.
A key component in the engineering process is the Node Assignment Drawing (NAD). Each node in a
system has a NAD which shows all required information for that node. A sample drawing is shown in the
figure below.

TN1-86400-400PS
Issue 9.0
May 2017
Page 133
SITE: B
FIBRE TO: SITE A FIBRE TO: SITE C RING:

4 3
RACK #:
6
HEADEND: SITE C
C RING: 1
1
Bus L/R slot TU Mode L R
CBUS-S (PAIR 1) TU#4x: SITE A CH 1
S L 1 4x STD 1300nm NODE:1 1300nm
CH 3 CH 2 CH 1 CH 1 R R 2 13x STD
SYNC MODE
Q - - - -
BC96 TX: 0023 BC96 RX: 0032 P - - - - NORMAL, LEFT 2 7

PAIR 1
48 V LS L R 48 V
TIFPORT 1
PWR DATA 4W DTT TX DTT RX CMUX CMUX BLANK O/W STM-1 CSSU STM-1 PWR
CBUS-R (PAIR 1) TU#13x: SITE D Port L/R slot TU E1 L/R slot TU

1 - - - 1 L 1 7x slot 1 TO 7
2 - - - 2 R 2 8x
CH 1 CH 2 CH 14 CH 9-13 CH 6 3 - - - 3 R 3 9x
CH 8 CH 20 4 - - - 4 L 4 12x TU 15x TO 21x
BC96 BC96 BC96
5 L 5 3x 5 - - -
TX: 0158 TX: 0103 TX: 0204 6 R 6 5x 6 - - -
RX: 0815 BC96 TX: 0041 RX: 0301 RX: 0402 PAIR 2
BC96 RX: 0014 7 - - - 7 - - -
48 V CONTACT NX64 G703 L PAIR 4 R L PAIR 3 R L R 48 V
TIFPORT 3 TIFPORT 3 TIFPORT 2
PWR I/O CDR HCB DATA DATA BLANK TIE TIE T1/E1 T1/E1 ETHR-10 ETHR-10 PWR 8
TRANSMIT RECEIVE
CCT1 CCT2 CCT3 CCT4 CCT1 CCT2 CCT3 CCT4
86429-M2 DTT TEST PANEL
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 5
0 See Description Below
Figure 211: Typical Node Assignment Drawing
The following information is shown on the drawing:

1. Indicates both the downstream and upstream node on the ring. If the far-end STM-N Aggregate unit
Left/Right designation is not stated, it is assumed that the Left unit at the local node connects to the
Right unit at the far-end and vice versa.
2. Indicates how the node is configured for synchronization. The first parameter indicates the Node Type
(HEADEND, NORMAL, SLAVE or CBW PORT p), while the second one indicates the Sync Priority
(Left or Right).
3. Indicates the port to which this CBUS is connected (CBUS-S) and on what TU-1 level unit pair (PAIR
1). Also shows TU-1 assignment (TU-1#4x) and where the TU-1 is being dropped at the far end
(SITE H).
4. Indicates channel assignment for the given channel interface unit. Other information shown is BC96
address for DTT, Contact I/O and some data and VF units as well as priority path and far-end drop
site for channels dropped off a shared TU-11.
5. Provides slot reference bar for unit shelf slot location.
6. Shows TU-1 level unit pair configuration. Indicates priority path for CBUS ports, the TIFport slot and
TU-1# assigned to the CBUS, the CBUS mode of operation, and the STM-N Aggregate Unit TIFport
being used.
7. Provides Site location, Ring # and Rack #, and what node on the system is the HEADEND.
8. Provides each unit name.
9. Indicates intra-node CBW port connections, if applicable.
10. Provides TUG-3, TU-12 and 64 kb/s channel cross-connect information in tables associated with the
drawing as applicable to the given node (not shown in Figure 211).

TN1-86400-400PS
Issue 9.0
May 2017
Page 134

TN1-86400-400PS
Issue 9.0
May 2017
Page 135
APPENDIX A
LIST OF ILLUSTRATIONS
List of Figures
Section 1 Figures
Figure 1: STM-4 signal virtual pipes showing various levels of services....................................................... 8
Section 2 Figures
Figure 2: Hierarchy of TN1Ue units available for carrying customer traffic ................................................. 11
Figure 3: TU-1 level units at a ring node ..................................................................................................... 13
Figure 4: TUG-3 level units at a ring node .................................................................................................. 14
Figure 5: TN1Ue units carrying no traffic (with exception of STM-N Aggregate units)................................ 16
Section 3 Figures
Figure 6: SDH multiplexing structure .......................................................................................................... 20
Figure 7: Two-node ring .............................................................................................................................. 22
Figure 8: Security features .......................................................................................................................... 22
Figure 9: Swapping normal and alternate configuration images ................................................................. 23
Figure 10: Common Equipment Shelf (rear view) ....................................................................................... 24
Section 4 Figures
Figure 11: Typical rack layout ..................................................................................................................... 26
Figure 12: Common Equipment Shelf (front view with front cover removed) .............................................. 27
Figure 13: Common Equipment Shelf (rear view) ....................................................................................... 27
Figure 14: Expansion Shelf (rear view) ....................................................................................................... 28
Figure 15: Backplane cabling example ....................................................................................................... 29
Figure 16: Power Unit Front Panel .............................................................................................................. 29
Figure 17: Power Unit Paddleboard ............................................................................................................ 29
Figure 18: STM-16 Aggregate Unit Front Panel .......................................................................................... 30
Figure 19: STM-16 Aggregate Unit Signal Flow Diagram ........................................................................... 30
Figure 20: Types of cross-connections supported by STM-16 Aggregate unit ........................................... 31
Figure 21: Tying traffic between STM-N rings using CBW tie links ............................................................ 32
Figure 22: STM-16 Aggregate Unit View – Main Tab.................................................................................. 32
Figure 23: STM-16 Aggregate Unit View – VC-4 Tab ................................................................................. 32
Figure 24: STM-16 Aggregate Unit View – Cross-Connect Tab ................................................................ 33
Figure 25: STM-16 Aggregate Unit View – TIFports Tab ........................................................................... 33
Figure 26: STM-16 Aggregate Unit View – TU-12 Status Tab .................................................................... 33
Figure 27: STM-16 Aggregate Unit View – Errors Tab ............................................................................... 33
Figure 28: STM-16 Aggregate Unit View – Firmware Tab .......................................................................... 34
Figure 29: STM-16 Aggregate Unit View – Config Image 2 Tab ................................................................. 34

TN1-86400-400PS
Issue 9.0
May 2017
Page 136
Figure 30: STM-4 Aggregate Unit Front Panel ............................................................................................ 35

Figure 31: STM-4 Aggregate Unit Signal Flow Diagram ............................................................................. 35
Figure 32: Types of cross-connections supported by STM-4 Aggregate unit ............................................. 36
Figure 33: Tying traffic between STM-4 and STM-1 rings using CBW tie links .......................................... 37
Figure 34: STM-4 Aggregate Unit View – Main Tab.................................................................................... 37
Figure 35: STM-4 Aggregate Unit View – VC-4 Tab ................................................................................... 37
Figure 36: STM-4 Aggregate Unit View – Cross-Connect Tab .................................................................. 38
Figure 37: STM-4 Aggregate Unit View – TIFports Tab ............................................................................. 38
Figure 38: STM-4 Unit View – TU-12 Status Tab ........................................................................................ 38
Figure 39: STM-4 Aggregate Unit View – Errors Tab ................................................................................. 38
Figure 40: STM-4 Aggregate Unit View – History Tab ................................................................................ 39
Figure 41: STM-4 Aggregate Unit View – Config Image 2 Tab ................................................................... 39
Figure 42: STM-1 Aggregate Unit Front Panel ............................................................................................ 40
Figure 43: STM-1 Aggregate Unit Signal Flow Diagram ............................................................................. 40
Figure 44: Types of cross-connections supported by STM-1 Aggregate unit ............................................. 41
Figure 46: STM-1 Aggregate Unit View – Main Tab.................................................................................... 42
Figure 47: STM-1 Aggregate Unit View – VC-4 Tab ................................................................................... 42
Figure 48: STM-1 Aggregate Unit View – Cross-Connect Tab ................................................................... 42
Figure 49: STM-1 Aggregate Unit View – TIF Ports Tab ............................................................................ 42
Figure 50: STM-1 Aggregate Unit View – Errors Tab ................................................................................. 43
Figure 51: STM-1 Aggregate Unit View – Config Image 2 Tab ................................................................... 43
Figure 52: STM-1 Aggregate Unit View – History Tab ................................................................................ 43
Figure 53: External Sync Unit Front Panel .................................................................................................. 44
Figure 54: External Sync Unit Inputs and Outputs ...................................................................................... 45
Figure 55: External Sync Unit View – Main Tab .......................................................................................... 46
Figure 56: External Sync Unit View – Sync Outputs ................................................................................... 46
Figure 57: CS Service Unit Front Panel ...................................................................................................... 46
Figure 58: 86434-81 Service Unit Paddleboard .......................................................................................... 46
Figure 59: Various types of VistaNET connections to CSSUs in different NMS domains........................... 48
Figure 60: CSSU VistaNET View – Status Tab ........................................................................................... 49
Figure 61: CSSU VistaNET View – Basic Setup Tab .................................................................................. 49
Figure 62: CSSU-S Communications .......................................................................................................... 50
Figure 63: CSSU Web UI – Authorization Tab ........................................................................................... 50
Figure 64: Orderwire Unit Front Panel ........................................................................................................ 51
Figure 65: Orderwire Unit View ................................................................................................................... 51
Figure 66: CMUX Unit Front Panel.............................................................................................................. 52
Figure 67: CMUX Unit Paddleboard ............................................................................................................ 52
Figure 68: CMUX Unit View – Main Tab ..................................................................................................... 53
Figure 69: CMUX Unit View – 64 kb/s Channels Tab ................................................................................ 53
Figure 70: CMUX Unit – Show TU-11 Tab .................................................................................................. 53
Figure 71: CDAX Unit Front Panel .............................................................................................................. 54
Figure 72: CDAX Unit Ports and Cross-Connect Functions........................................................................ 54
Figure 73: CDAX in E1MXe application ...................................................................................................... 55
Figure 74: CDAX Unit View – Main Tab ...................................................................................................... 56
Figure 75: CDAX Unit View – Cross-Connect Tab ...................................................................................... 56
Figure 76: CDAX Unit View – 64kb/s Channels Tab ................................................................................... 56
Figure 77: CDAX Unit View – E1 Tab ......................................................................................................... 56
Figure 78: Tie Unit Front Panel ................................................................................................................... 57
Figure 79: Tie Unit View – Main Tab ........................................................................................................... 57
Figure 80: Tie Unit View – Tie Info Tab ....................................................................................................... 57
Figure 81: TUG-3 Unit Front Panel ............................................................................................................. 58
Figure 82: TUG-3 Unit View – Main Tab ..................................................................................................... 58
Figure 83: TUG-3 Unit View – TU-1 Status Tab.......................................................................................... 58

TN1-86400-400PS
Issue 9.0
May 2017
Page 137
Section 5 Figures
Figure 84: ETHER-1000 Unit Front Panel ................................................................................................... 59
Figure 85: ETHER-1000 Ring System ........................................................................................................ 59
Figure 86: Typical ETHER-1000 drop ......................................................................................................... 60
Figure 87: ETHER-1000 paddleboard with modules installed in both banks .............................................. 60
Figure 88: TDM pipes .................................................................................................................................. 61
Figure 89: D-PVLANs in ETHER-1000 system ........................................................................................... 62
Figure 90: Tying multiple D-PVLANs through a P-Trunk ............................................................................ 63
Figure 91: Distributing VLANs from external switch’s trunk port to D-PVLANs .......................................... 63
Figure 92: Distributing traffic from a router’s trunk port to D-PVLANs ........................................................ 63
Figure 93: Multiple VLANs within a single D-PVLAN over multiple rings .................................................... 64
Figure 94: Connecting remote end devices to various VLANs on external switch trunk port...................... 64
Figure 95: Connecting remote end devices to various VLANs on a router port .......................................... 64
Figure 96: ETHER-1000 Unit Priority Queues ............................................................................................. 65
Figure 97: ETHER-1000 Unit View – Main Tab........................................................................................... 66
Figure 98: ETHER-1000 Unit View – Line Setup ........................................................................................ 66
Figure 99: ETHER-1000 Unit View – Line Monitor Tab............................................................................... 67
Figure 100: ETHER-1000 Unit View – Port Setup Tab ............................................................................... 67
Figure 101: ETHER-1000 Unit View – Port Details Tab (example for RJ-45 port with default settings) ..... 68
Figure 102: ETHER-1000 Unit View – Port Details Tab (example for optical port) ..................................... 68
Figure 103: ETHER-1000 Unit View – VLANs Tab (P-Trunk port example) ............................................... 68
Figure 104: ETHER-1000 Unit View – VLANs Tab (Q-Trunk port example) .............................................. 68
Figure 105: ETHER-1000 Unit View – MAC Tab (entering static MAC entries) .......................................... 69
Figure 106: ETHER-1000 Unit View – MAC Tab (monitoring MAC Table Entries) ..................................... 69
Figure 107: ETHER-1000 Unit View – Passed Tab .................................................................................... 69
Figure 108: ETHER-1000 View – Advanced Tab ........................................................................................ 69
Figure 109: ETHER-100 Unit Front Panel ................................................................................................... 70
Figure 110: ETHER-100 Ring System ........................................................................................................ 70
Figure 111: PVLANs in ETHER-100 system ............................................................................................... 71
Figure 112: ETHER-100 Unit Priority Queues ............................................................................................. 72
Figure 113: ETHER-100 Unit View – Main Tab........................................................................................... 73
Figure 114: ETHER-100 Unit View – Line Tab............................................................................................ 73
Figure 115: ETHER-100 Unit View – Port Summary Tab ........................................................................... 73
Figure 116: ETHER-100 Unit View – Port Details Tab ................................................................................ 73
Figure 117: ETHER-10 Unit Front Panel ..................................................................................................... 74
Figure 118: ETHER-10 Ring System .......................................................................................................... 74
Figure 119: ETHER-10 Drop ....................................................................................................................... 74
Figure 120: ETHER-10 Unit Non-Hubbing Paddleboard ............................................................................ 75
Figure 121: ETHER-10 Unit Hubbing Paddleboard.................................................................................... 75
Figure 122: ETHER-10 Unit View – Main Tab............................................................................................. 75
Figure 123: ETHER-10 Unit View – Ethernet Tab ....................................................................................... 75
Figure 124: 4W VF E&M Unit Front Panel .................................................................................................. 76
Figure 125: 4W VF Unit View ...................................................................................................................... 76
Figure 126: 2W FXO Unit Front Panel ........................................................................................................ 77
Figure 127: 2W FXS Unit Front Panel......................................................................................................... 77
Figure 128: 2W FXO Unit View ................................................................................................................... 77
Figure 129: 2W E&M Unit Front Panel ........................................................................................................ 78
Figure 130: 2W TO/E&M Unit View............................................................................................................. 78
Figure 131: 4W VF Partyline Unit Front Panel ............................................................................................ 79
Figure 132: 4W Partyline Unit View............................................................................................................. 79
Figure 133: Contact I/O Unit Front Panel .................................................................................................... 80
Figure 134: Data-LS Unit Front Panel ......................................................................................................... 81
Figure 135: DATA-LS Unit View .................................................................................................................. 81
Figure 136: RS-232 Connections ................................................................................................................ 81

TN1-86400-400PS
Issue 9.0
May 2017
Page 138
Figure 137: Data-PTM Unit Front Panel ...................................................................................................... 82

Figure 138: DATA-PTM Unit View............................................................................................................... 82
Figure 139: Data-G703 Unit Front Panel..................................................................................................... 83
Figure 140: DATA-G703 Unit View ............................................................................................................. 83
Figure 141: Data-NX64 Front Panel ............................................................................................................ 84
Figure 142: DATA-Nx64 Unit View .............................................................................................................. 84
Figure 143: T1/E1 Unit Front Panel............................................................................................................. 85
Figure 144: T1/E1 Unit Paddleboard .......................................................................................................... 85
Figure 145: T1/E1 Unit View – Main Tab .................................................................................................... 85
Figure 146: T1/E1 Unit View – E1 Tab ........................................................................................................ 85
Figure 147: Data-NX64F Front Panel.......................................................................................................... 87
Figure 148: Data-NX64F Unit Paddleboard ............................................................................................... 87
Figure 149: Data-Nx64F Unit View.............................................................................................................. 87
Figure 150: DTT Unit Front Panel ............................................................................................................... 88
Figure 151: DTT Paddleboard ..................................................................................................................... 88
Figure 152: False Trip Probability ............................................................................................................... 88
Figure 153: BC96 Code............................................................................................................................... 89
Figure 154: DTT Test Panel (Front View) ................................................................................................... 90
Figure 155: DTT Test Panel (Rear View) .................................................................................................... 90
Section 6 Figures
Figure 158: VistaNET Deployment Options ................................................................................................ 92
Figure 159: Ring Map View ......................................................................................................................... 96
Figure 160: Node Icon Description .............................................................................................................. 97
Figure 161: SDH Network Map View........................................................................................................... 98
Figure 162: VistaNET Unit View for Data-Nx64F Unit ................................................................................. 99
Figure 163: VistaNET Alarm Engine: Current Alarms ............................................................................... 100
Figure 164: VistaNET Inventory ................................................................................................................ 101
Figure 165: Activity Log ............................................................................................................................. 102
Figure 167: Login Dialog Window ............................................................................................................. 103
Figure 168: Managing user accounts ........................................................................................................ 103
Figure 169: Adding a local configuration restriction .................................................................................. 104
Figure 170: Adding an NMS configuration restriction ................................................................................ 104
Figure 171: List of defined restrictions ...................................................................................................... 104
Section 7 Figures
Figure 172: Normal Configuration ............................................................................................................. 106
Figure 173: Fibre Failure ........................................................................................................................... 106
Figure 174: Linear Network ....................................................................................................................... 107
Figure 175: Add and Drop Application in Linear Network ......................................................................... 107
Figure 176: TN1Ue system comprising multiple rings, linear network and spur ....................................... 108
Figure 177: Dual homing configuration ..................................................................................................... 108
Figure 178: Using E1 link to pass 64 kb/s traffic between remote TN1Ue SDH rings .............................. 109
Figure 179: TN1Ue and foreign STM-N multiplexers operating in same ring ........................................... 109
Figure 180: N x STM-1 virtual ring established through STM-64 backbone ring ...................................... 110
Figure 181: TN1Ue STM-N ring closed through STM-64 backbone ring .................................................. 110
Figure 182: E1 circuit established between TN1Ue and non-TN1Ue SDH nodes .................................... 111
Figure 183: TN1Ue ring with microwave radio hops ................................................................................. 111
Figure 184: Two parts of TN1Ue system interconnected via VC-12 cross-connect ................................. 112
Figure 185: Main and backup control centres in same ring – normal operation ....................................... 112
Figure 186: Main and backup control centres in same ring – main control centre outage ........................ 113

TN1-86400-400PS
Issue 9.0
May 2017
Page 139
Figure 187: Main and backup control centres in different rings – normal operation ................................. 113
Figure 188: Main and backup control centres in different rings – main control centre outage .................. 114
Figure 189: Mixed TN1Ue and E1MXe network – example with E1MXe spur and tree topologies .......... 114
Figure 190: Mixed TN1Ue and E1MXe network – example with E1MXe ring and spur topologies .......... 115
Figure 191: Standalone E1MXe network example .................................................................................... 115
Section 8 Figures
Figure 192: 2kHz sync tie connection between two rings ......................................................................... 118
Figure 193: Dual homing application with both tie sites configured for CBW port timing .......................... 119
Figure 194: Dual homing application with intelligent sync tie at primary tie site ........................................ 119
Figure 195: Reference clock distribution in a ring with no failures ............................................................ 122
Figure 196: Reference clock distribution in a ring with fibre failure ........................................................... 122
Figure 197: Reference clock distribution in a ring with headend node failure ........................................... 123
Figure 198: Application with single headend node (Normal State) ........................................................... 124
Figure 199: Application with single headend node (loss of primary sync input) ........................................ 124
Figure 200: Application with single headend node (holdover) ................................................................... 125
Figure 201: Main and backup headend nodes in same ring (normal operation) ....................................... 125
Figure 202: Main and backup headend nodes in same ring (loss of sync inputs at main headend node) 126
Figure 203: Main and backup headend nodes in different rings ............................................................... 126
Figure 204: Timing external network element with TN1Ue clock .............................................................. 127
Figure 206: Filtering accumulated jitter using external SASE equipment ................................................. 128
Figure 210: Propagation delay through an STM-1 TN1Ue system ........................................................... 131
Figure 211: Propagation delay through an STM-4 TN1Ue system ........................................................... 131
Figure 212: Propagation delay through an STM-16 TN1Ue system ......................................................... 132
Figure 213: Typical Node Assignment Drawing ........................................................................................ 133
List of Tables
Table 1: Optical Aggregate Unit Capacities and Drop Capabilities ............................................................. 12
Table 2: TU-1 Level Units............................................................................................................................ 13
Table 3: TUG-3 Level Units ......................................................................................................................... 14
Table 4: 64 kb/s Level Units ........................................................................................................................ 15
Table 5: SDH Hierarchy and Rates ............................................................................................................. 19
Table 6: Comparing CSSU’s CI and Ethernet Port Functions ..................................................................... 49
Table 7: CDAX Unit Drop Port Modes of Operation .................................................................................... 55
Table 8: DTT Unit Specifications ................................................................................................................. 89
Table 9: SSM Values as per ITU-T Recommendation G.707 ................................................................... 120
Table 10: Input prioritization on units in CBW Port p and Normal modes ................................................. 121
Table 11: CDAX unit delays ...................................................................................................................... 132

TN1-86400-400PS
Issue 9.0
May 2017
Page 140

TN1-86400-400PS
Issue 9.0
May 2017
Page 141
APPENDIX B
LIST OF ACRONYMS
2W 2-wire
4W 4-wire
AC Alternating Current
ACL Access Control List
ACK Acknowledge
ACO Alarm Cut-Off
ADM Add/Drop Multiplexer
AES Advanced Encryption Standard
AIS Alarm Indication Signal
ALM Alarm
AMI Alternate Mark Inversion
ANSI American National Standards Institute
APS Automatic Protection Switching
AU Administrative Unit
AUG Administrative Unit Group
AUI Attachment Unit Interface
BC96 Balanced Code 96
BER Bit Error Rate
BPV Bipolar Violations
B3ZS Bipolar with 3 Zero Substitution
C Container; Common
CBUS Channel Bus
CBW Configurable Bandwidth
CCT Circuit
CDAX Compact Digital Access cross-connect
CENELEC Comité Européen de Normalisation Électrotechnique
(European Committee For Electrotechnical Standardization)
CI Craft Interface
CMUX Channel Multiplexer
COM Communication
CRC Cyclic Redundancy Check
CSA Canadian Standards Association
CSSU Cyber-Secured Service Unit
CSSU-L CSSU operating in Legacy mode
CSSU-S CSSU operating in Secure mode
CTS Clear To Send
CV Code Violations
DACS Digital Access and Cross-connect System
DC Direct Current
DCC Data Communication Channel (DCCR + DCCM)
DCCR Regenerator Section Data Communications Channel (SOH bytes D1 to D3, 196 kb/s)
DCCM Multiplex Section Data Communications Channel (SOH bytes D4-D12, 576 kb/s)
DDS Digital Data Service
DMI Diagnostics Monitoring Interface
DHCP Dynamic Host Configuration Protocol
DPRing Dedicated Protection Ring

TN1-86400-400PS
Issue 9.0
May 2017
Page 142
D-PVLAN Distributed Port-Based VLAN

DSR Data Set Ready
DTT Direct Transfer Trip
E1 Primary Multiplex Signal 2048 kb/s
E1, E2 Orderwire bytes in STM-N SOH signals (E1 is Regenerator Section Orderwire Channel &
E2 is Multiplex Section Orderwire Channel)
E1MXe GE Lentronics E1 Multiplexer
EEPROM Electronically Erasable Programmable Read Only Memory
EMC Electromagnetic Compliance
EMI Electro Magnetic Induction
ETSI European Telecommunications Standards Institute
FET Field Effect Transistor
FDX Full Duplex
FXO Foreign Exchange Office
FXS Foreign Exchange Station
GMII Gigabit Media Independent Interface
GOOSE Generic Object-Oriented Substation Events
GUI Graphical User Interface
HDB3 High Density Bipolar 3
HDX Half Duplex
I/F Interface
I/O Input/Output
IEEE Institute of Electrical and Electronics Engineers
IP Internet Protocol
ITU-T International Telecommunication Union – Telecommunications Sector
LAN Local Area Network
LED Light Emitting Diode
LOF Loss Of Frame
LOP Loss Of Pointer
LOS Loss of Signal
LS Low Speed
MII Media Independent Interface
MMF Multimode Fibre
MS Multiplex Section
MSOH Multiplex Section Overhead
MTU Master Terminal Unit
NAD Node Assignment Drawing
NBOC Network Build-Out Capacitance
NC Normally Closed
NE Network Element
NMS Network Management System
NO Normally Open
NTP Network Timing Protocol
OAM&P Operations, Administration, Maintenance & Provisioning
OOF Out Of Frame
PABX Private Automatic Branch Exchange
PBOC Packet Buffer Overflow Counter
PBX Private Branch Exchange
PC Personal Computer
PDH Plesiochronous Digital Hierarchy
PIN Positive-Intrinsic-Negative
PLAR Private Line Automatic Ringdown
PLL Phase Locked Loop
POH Path Overhead
PPB Parts per Billion

TN1-86400-400PS
Issue 9.0
May 2017
Page 143
PPM Parts per Million

PRBS Pseudo Random Bit Stream
PRC Primary Reference Clock
PSTN Public Switched Telephone Network
PTM Point To Multipoint
PVLAN Port-Based VLAN
QVLAN 802.1Q VID-based VLAN
RADIUS Remote Access Dial-In User Service
RCV Receive
RDI Remote Defect Indication
RFI Radio Frequency Interference
RLSD Remote Line Signal Detect
RS Regenerator Section
RSOH Regenerator Section Overhead
RTS Request To Send
RTU Remote Terminal Unit
RU Rack Unit
RX Receive
SASE Stand Alone Synchronization Equipment
SCADA Supervisory Control and Data Acquisition
SD Secure Digital (memory card)
SDH Synchronous Digital Hierarchy
SEC Synchronous Equipment Clock, SDH Equipment Clock
SFP Small Form-factor Pluggable
SMF Single Mode Fibre
SNC Sub-Network Connection
SNMP Simple Network Management Protocol
SOH Section Overhead
SONET Synchronous Optical NETwork
SOY Switch on Yellow
SPI Serial Peripheral Interface
SSL Secure Socket Layer
SSM Synchronization Status Message
STM Synchronous Transport Module
SWC Surge Withstand Capability
T1 North American Primary Multiplex Signal (1544 kb/s, DS1)
TCP Transmission Control Protocol
TLS Transport Layer Security
TDM Time Division Multiplexing
TIF TN1Ue Intermediate Format
TO Transmission Only
TOS Type of Service
TP TIFport
TU Tributary Unit
TUG Tributary Unit Group
TX Transmit
UI User Interface
VC Virtual Container
VCXO Voltage Controlled Crystal Oscillator
VF Voice Frequency
VLAN Virtual LAN
VNI VistaNET Network Interface
VSA VistaNET Server Application
WAN Wide Area Network
XCVR Transceiver

TN1-86400-400PS
Issue 9.0
May 2017
Page 144
XMT Transmit
YEL Yellow

TN1Ue Reference Manual Issue 9.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TN1Ue Reference Manual Issue 9.0

Uploaded by

Copyright:

Available Formats

TN1Ue

Copyright  GE Multilin Inc. 2002-2017, All Rights Reserved

Copyright  GE Multilin Inc. 2002-2017

2 PRODUCT STRUCTURE ......................................... 11

4 COMMON EQUIPMENT UNITS ............................... 25

Copyright  GE Multilin Inc. 2002-2017

4.7 External Sync Unit .................................................................................. 44

5 INTERFACE UNITS .................................................. 59

Copyright  GE Multilin Inc. 2002-2017

6.10 VistaNET System Tree ............................................................................ 95

7 CONFIGURATIONS ................................................ 105

8 SYNCHRONIZATION, PROPAGATION DELAYS AND

APPENDIX A................................................................ 135

Copyright  GE Multilin Inc. 2002-2017

List of Figures ................................................................................................. 135

APPENDIX B................................................................ 141

Copyright  GE Multilin Inc. 2002-2017

Copyright  GE Multilin Inc. 2002-2017

VC-4 TUG-3 # 2,1 VC-3

TUG-3 # 1,1 VC-3

STM-4 TUG-3 # 1,3

Figure 1: STM-4 signal virtual pipes showing various levels of services

Copyright  GE Multilin Inc. 2002-2017

1.2 Summary of Features

Copyright  GE Multilin Inc. 2002-2017

Copyright  GE Multilin Inc. 2002-2017

2.1 Optical Aggregate Unit

Optical Aggregate Units TUG-3 Level Units

TIFports TIFports TIFports TIFports

Figure 2: Hierarchy of TN1Ue units available for carrying customer traffic

Copyright  GE Multilin Inc. 2002-2017

2.2 TU-1 Level Units

Copyright  GE Multilin Inc. 2002-2017

Unit Required Number of TU-12s/TU-11s Use

CBUS-P E1-7 ...

Figure 3: TU-1 level units at a ring node

Copyright  GE Multilin Inc. 2002-2017

2.3 TUG-3 Level Units

Unit Number of TUG-3s Use

Table 3: TUG-3 Level Units

STM-16 Pass-Through Traffic STM-16

CBW-D LAYER 2 SWITCH CBW-D

Figure 4: TUG-3 level units at a ring node

Copyright  GE Multilin Inc. 2002-2017

2.4 64 kb/s Level Units

Group Unit No of Interface

Table 4: 64 kb/s Level Units

2.5 Supporting Units

Copyright  GE Multilin Inc. 2002-2017

STM-N External STM-N

Left/West Sync Right/East

The External Sync unit is typically used in the following applications:

Copyright  GE Multilin Inc. 2002-2017

Copyright  GE Multilin Inc. 2002-2017

THIS PAGE INTENTIONALLY LEFT BLANK

Copyright  GE Multilin Inc. 2002-2017

3.2 SDH Conformance

3.2.1 Background and History

The Phase 1 standard defined:

 A base rate and format

Table 5: SDH Hierarchy and Rates

Copyright  GE Multilin Inc. 2002-2017

TU-12 VC-12 C-12 2 Mbit/s