TN-1C System Description

323-1081-100
NORTEL NETWORKS
TN-1C/TN-1P
System Description
Release 5.2 Standard (Revision 1) October 2001

NORTEL NETWORKS
TN-1C/TN-1P
System Description
Document Number: 323-1081-100

Document Status: Standard (Revision 1)
Product Release Number: 5.2
Date: October 2001
Copyright  1996 – 2001 Nortel Networks, All Rights Reserved.
Printed in England
The copyright of this document is the property of Nortel Networks. Without the written consent of Nortel Networks, given by contract
or otherwise, this document must not be copied, reprinted or reproduced in any material form, either wholly or in part, and the
contents of this document, or any methods or techniques available therefrom, must not be disclosed to any other person
whatsoever.
NORTEL NETWORKS CONFIDENTIAL: The information contained herein is the property of Nortel Networks and is strictly
confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein
confidential, shall disclose the information only to its employees with a need to know, and shall protect the information, in whole or
in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential
information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is
granted no rights to use the information contained herein.
So far as Nortel Networks is aware the contents of this document are correct. However, such contents have been obtained from a
variety of sources and Nortel Networks can give no warranty or undertaking and make no representation as to their accuracy. In
particular, Nortel Networks hereby expressly excludes liability for any form of consequential, indirect or special loss, and for loss of
data, loss of profits or loss of business opportunity, howsoever arising and whether sustained by the user of the information herein
or any third party arising out of the contents of this document.
*NORTEL NETWORKS, the Nortel Networks logo, the Globemark, How the World Shares Ideas and Unified Networks are
trademarks of Nortel Networks.
TN-1C/TN-1P System Description

iii
Publication history
October 2001
Release 5.1 Standard (Revision 1). Minor updates.
March 2001
Release 5.2 Standard. 24 x 2 Mbit/s tributary extension card and single-slot
TN-1C information added. PE10 router card references added.
September 2000
Release 5.1 Standard. Release 5.1 features added.
November 1999
Release 5 Standard. TN-1C and TN-1P documents combined, Release 5
features added.
January 1999
Release 3 Standard (Revision 1). Minor amendments.
March 1998
Release 3 Standard.
June 1997
Release 2 Standard.
December 1996
Release 1 Standard.

v
Contents
About this document xiii
Technical support and information xiv
System overview 1-1

TN-1C multiplexer 1-1
TN-1P and TN-1PH headend multiplexers 1-2
TN-1P Basestation multiplexer 1-2
System configuration - TN-1C 1-7
Point-to-point terminal multiplexer 1-7
Path protected 2-fibre ring 1-7
ADM loop feeder 1-8
ATU application 1-9
System configuration - TN-1P, TN-1PH 1-10
Point-to-point terminal multiplexer 1-10
Terminal multiplexer spur from an SDH ring 1-11
Hub configuration 1-12
ATU application 1-13
Mechanical description 1-15
Enclosure types 1-15
Mounting 1-15
Connectivity 1-18
Channel numbering schemes 1-18
Port/channel designations 1-20
Types of connections 1-21
User labels 1-23
Traffic mode 1-23
Path trace 1-24
Signal label 1-25
Path protection switching 1-26
Management and communications 1-26
Rack alarm adaptor 1-27
Software 1-27
Foundation software 1-27
Application software 1-27
Software download 1-28
Interfaces 1-28
Fan 1-28
Variants 1-29
TN-1C 1-29
TN-1P 1-31

vi
Equipment description 2-1

Power supplies 2-5
External 2-5
Internal power supply 2-5
Timing source 2-6
Clock generator 2-6
System clock 2-6
Controller platform 2-6
Processor 2-6
Restart 2-6
Memory 2-6
Serial communications 2-7
STM-1 interface 2-7
Timeslot interchanger 2-7
Multi-channel tributary block 2-8
Extension card interface (TN-1C only) 2-8
Traffic processing 2-8
Path protection 2-13
Holdoff period 2-13
Oscillation guard time 2-13
Reversion 2-13
Priority control 2-13
PPS criteria 2-14
Automatic laser shutdown 2-14
Loopbacks 2-15
STM-1 local loopback 2-15
STM-1 remote loopback 2-16
Tributary local loopback 2-17
Tributary remote loopback 2-17
Simultaneous loopbacks 2-18
Single fibre working 2-18
Built-in test facility 2-19
Non-service affecting tests 2-19
Service affecting tests 2-20
Subrack end processor and craft access panel (TN-1PH only) 2-22
LAN Interface 2-24
Alarm handler 2-24
RS-232 selector 2-24
Equipment management 3-1

Alarms 3-1
Alarm monitoring 3-1
Alarm handling 3-1
Alarm masking 3-1
External alarms 3-2
Rack alarms 3-2
Management 3-3
ATU channel 3-3
LAN channel 3-4
Real time clock 3-4
RSOH/MSOH DCC 3-4
Network addresses 3-5
Communication limitations 3-5
Inventory information 3-5
323-1081-100 Release 5.2 Standard (Revision 1)

vii
Software 3-6
Application software 3-6
Configuration data 3-6
Power supply unit 4-1

Functional description 4-1
Battery back-up 4-2
Alarms and indications 4-2
Connectors 4-3
Construction 4-4
Synchronisation 5-1
Sources 5-1
Synchronisation loss 5-1
Synchronisation schemes 5-2
TN-1C 5-2
TN-1P 5-3
Synchronisation source switch event 5-6
Synchronisation source hierarchy 5-6
Synchronisation settings 5-6
Synchronisation switching mechanisms 5-7
Synchronisation status messaging (SSM) 5-7
Synchronisation status messaging network examples 5-9
SSM recommendations 5-11
Non-SSM synchronisation sourcing (TN-1C/TN-1P) 5-12
Failure of synchronisation source 5-13
Wait to restore time 5-13
Synchronisation alarms 5-13
Performance monitoring 6-1

Parity error counts 6-1
Performance monitoring counts 6-1
Performance monitoring points 6-2
Disabling performance monitoring 6-3
Performance anomalies and defects 6-3
Performance monitoring periods 6-4
Performance logs 6-5
15 minute logs 6-5
24 hour logs 6-6
Early termination 6-7
Warm restart 6-7
Quality of service violation alarms 6-7
Traffic type 6-8
User actions 6-9
System parameters 7-1

Common 7-1
Electromagnetic compatibility 7-1
Environmental conditions 7-1
Construction 7-2
External dimensions 7-2
Weight 7-2
Supply voltage 7-2
Fuses 7-2

viii
Maximum power consumption 7-3

External interfaces 7-4
2 Mbit/s tributary interfaces 7-4
34 Mbit/s tributary interfaces (TN-1C only) 7-4
45 Mbit/s tributary interfaces (TN-1C only) 7-5
STM-1 optical interfaces 7-5
2 Mbit/s external synchronisation input 7-7
Craft Access Terminal interface 7-7
LAN interface 7-7
ATU interface 7-8
External alarms 7-8
Power Supply Unit (TN-1C and standard TN-1P only) 7-9
A.C. supply 7-9
D.C. output 7-9
Fuses 7-9
Power consumption 7-9
Power dissipation 7-9
Recommended battery replacement period 7-9
Alarm outputs 7-9

D-type connectors 8-13
2 Mbit/s 75 Ω tributary interfaces 8-13
2 Mbit/s 120 Ω tributary interfaces 8-13
34/45 Mbit/s tributary interfaces (TN-1C only) 8-14
Optical interfaces 8-15
Craft access terminal interface 8-15
ATU interface (TN-1C Release 1 and 2 and TN-1C single-slot hardware and
TN-1P) 8-16
ATU interface TN-1C (Release 3/5/5.1 hardware) 8-16
Fan interface (TN-1C and TN-1P Release 5.1 hardware) 8-18
2 Mbit/s external synchronisation input 8-18
External alarm interface 8-19
Power and power alarm interface 8-21
LAN interface 8-22
Rack alarm adaptor 8-23
Rack alarm bus connector 8-24
Fuses 8-24
Ordering codes 9-1

TN-1C only 9-1
TN-1P only 9-3
Common items 9-5
Obsolete codes 9-6
Appendix A: Synchronous digital hierarchy 10-1

Synchronous Digital Hierarchy 10-1
SDH multiplexing structure 10-2
TN-1C multiplexing structure 10-4
TN-1P multiplexing structure 10-4
Mapping of a 2048 kbit/s signal into a VC-12 10-5
Mapping of a 34.368 Mbit/s signal into a VC-3 10-6
Mapping of a 44.736 Mbit/s signal into a VC-3 10-6
Multiplexing of VC-12s into a TUG-2 10-7

ix
Multiplexing of TUG-2s into a TUG-3 10-7

Multiplexing of a VC-3 into a TUG-3 10-9
Mapping of TUG-3s into a VC-4 10-9
Mapping of a VC-4 into a STM-1 via an AU-4/AUG 10-10
Path overheads 10-10
Section overhead 10-11
Index 11-1
List of figures
Figure 1-1 TN-1C general view 1-3
Figure 1-2 TN-1P and single-slot TN-1C general view 1-4
Figure 1-3 TN-1P Headend subrack general view 1-5
Figure 1-4 TN-1P Basestation general view 1-6
Figure 1-5 TN-1C point-to-point terminal 1-7
Figure 1-6 TN-1C in a 2-fibre path protection ring 1-8
Figure 1-7 TN-1C connected to an ADM STM-1 tributary 1-9
Figure 1-8 Typical TN-1C ATU application 1-10
Figure 1-9 TN-1P protected point-to-point STM-1 line system 1-11
Figure 1-10 Terminal multiplexer spur 1-11
Figure 1-11 Hub configuration 1-12
Figure 1-12 Typical TN-1P ATU application 1-14
Figure 1-13 Typical TN-1C/TN-1P installations 1-16
Figure 1-14 Typical TN-1P Basestation installation 1-16
Figure 2-1 TN-1C block diagram 2-3
Figure 2-2 TN-1P block diagram 2-4
Figure 2-3 TN-1C traffic processing 2-10
Figure 2-4 TN-1P traffic processing 2-11
Figure 2-5 STM-1 local loopback 2-16
Figure 2-6 STM-1 remote loopback 2-17
Figure 2-7 Tributary local loopback 2-17
Figure 2-8 Tributary remote loopback 2-18
Figure 2-9 Single fibre operation 2-18
Figure 2-10 PRBS location 2-21
Figure 2-11 SEP and CAP block diagram 2-23
Figure 3-1 Software upgrade overview 3-7
Figure 4-1 TN-1C PSU block diagram 4-2
Figure 4-2 TN-1C and TN-1P multiplexer PSU layout 4-5
Figure 5-1 TN-1C recommended synchronisation scheme 5-4
Figure 5-2 TN-1P recommended synchronisation schemes 5-5
Figure 5-3 SSM within a simple STM-1 ring with a single external source 5-9
Figure 5-4 SSM within a simple STM-1 ring with two external sources 5-10
Figure 5-5 SSM within a simple STM-1 chain with two external sources 5-11
Figure 8-1 TN-1C connection panel (8 x 2 Mbit/s + 34/45 Mbit/s version)
Release 1 hardware 8-3
Figure 8-2 TN-1C connection panel (8 x 2 Mbit/s + 2 x 34/45 Mbit/s version)
Release 3/5 hardware 8-4
Figure 8-3 TN-1C connection panel (16 x 2 Mbit/s version) Release 1
hardware 8-5
Figure 8-4 TN-1C connection panel (16 x 2 Mbit/s version) Release 3/5
hardware 8-6
Figure 8-5 TN-1C connection panel (32 x 2 Mbit/s version) Release 5.1
hardware 8-7
Figure 8-6 TN-1C optional 75 Ω interface cards for Release 5.1 hardware 8-8

x
Figure 8-7 TN-1P connection panel (4 x 2 Mbit/s) Release 5 hardware 8-9

Figure 8-8 TN-1P (Release 5.1 hardware), TN-1P Basestation, and TN-1C
single-slot connection panel (8 x 2 Mbit/s) 8-10
Figure 8-9 TN-1P Basestation (integral front panel connectors) 8-11
Figure 8-10 TN-1PH connector panel 8-12
Figure 8-11 Standard pin numbering for D-type connectors 8-13
Figure 10-1 SDH generalized multiplexing structure 10-2
Figure 10-2 STM-1 frame structure 10-4
Figure 10-3 TN-1C multiplexing structure 10-4
Figure 10-4 TN-1P multiplexing structure 10-4
Figure 10-5 2.048 Mbit/s tributary/VC-12/TU-12 mapping 10-5
Figure 10-6 34.368 Mbit/s tributary/VC-3 mapping 10-6
Figure 10-8 Multplexing of TU-12 via a TUG-2 10-8
Figure 10-9 TU-12/TUG-2/TUG-3 multiplexing 10-8
Figure 10-10 Multiplexing of a TU-3 via a TUG-3 10-9
Figure 10-11 Multiplexing of three TUG-3s into a VC-4 10-9
Figure 10-12 Mapping of a VC-4 into an STM-1 via an AU-4/AUG 10-10
Figure 10-13 VC-12 Path Overhead (V5 byte) 10-10
Figure 10-14 Section overhead 10-12
List of tables
Figure 1-1 TN-1C general view 1-3
Figure 1-2 TN-1P and single-slot TN-1C general view 1-4
Figure 1-3 TN-1P Headend subrack general view 1-5
Figure 1-4 TN-1P Basestation general view 1-6
Figure 1-5 TN-1C point-to-point terminal 1-7
Figure 1-6 TN-1C in a 2-fibre path protection ring 1-8
Figure 1-7 TN-1C connected to an ADM STM-1 tributary 1-9
Figure 1-8 Typical TN-1C ATU application 1-10
Figure 1-9 TN-1P protected point-to-point STM-1 line system 1-11
Figure 1-10 Terminal multiplexer spur 1-11
Figure 1-11 Hub configuration 1-12
Figure 1-12 Typical TN-1P ATU application 1-14
Figure 1-13 Typical TN-1C/TN-1P installations 1-16
Figure 1-14 Typical TN-1P Basestation installation 1-16
Figure 2-1 TN-1C block diagram 2-3
Figure 2-2 TN-1P block diagram 2-4
Figure 2-3 TN-1C traffic processing 2-10
Figure 2-4 TN-1P traffic processing 2-11
Figure 2-5 STM-1 local loopback 2-16
Figure 2-6 STM-1 remote loopback 2-17
Figure 2-7 Tributary local loopback 2-17
Figure 2-8 Tributary remote loopback 2-18
Figure 2-9 Single fibre operation 2-18
Figure 2-10 PRBS location 2-21
Figure 2-11 SEP and CAP block diagram 2-23
Figure 3-1 Software upgrade overview 3-7
Figure 4-1 TN-1C PSU block diagram 4-2
Figure 4-2 TN-1C and TN-1P multiplexer PSU layout 4-5
Figure 5-1 TN-1C recommended synchronisation scheme 5-4
Figure 5-2 TN-1P recommended synchronisation schemes 5-5
Figure 5-3 SSM within a simple STM-1 ring with a single external source 5-9
Figure 5-4 SSM within a simple STM-1 ring with two external sources 5-10
Figure 5-5 SSM within a simple STM-1 chain with two external sources 5-11

xi
Figure 8-1 TN-1C connection panel (8 x 2 Mbit/s + 34/45 Mbit/s version)

Release 1 hardware 8-3
Figure 8-2 TN-1C connection panel (8 x 2 Mbit/s + 2 x 34/45 Mbit/s version)
Release 3/5 hardware 8-4
Figure 8-3 TN-1C connection panel (16 x 2 Mbit/s version) Release 1
hardware 8-5
Figure 8-4 TN-1C connection panel (16 x 2 Mbit/s version) Release 3/5
hardware 8-6
Figure 8-5 TN-1C connection panel (32 x 2 Mbit/s version) Release 5.1
hardware 8-7
Figure 8-6 TN-1C optional 75 Ω interface cards for Release 5.1 hardware 8-8
Figure 8-7 TN-1P connection panel (4 x 2 Mbit/s) Release 5 hardware 8-9
Figure 8-8 TN-1P (Release 5.1 hardware), TN-1P Basestation, and TN-1C
single-slot connection panel (8 x 2 Mbit/s) 8-10
Figure 8-9 TN-1P Basestation (integral front panel connectors) 8-11
Figure 8-10 TN-1PH connector panel 8-12
Figure 8-11 Standard pin numbering for D-type connectors 8-13
Figure 10-1 SDH generalized multiplexing structure 10-2
Figure 10-2 STM-1 frame structure 10-4
Figure 10-3 TN-1C multiplexing structure 10-4
Figure 10-4 TN-1P multiplexing structure 10-4
Figure 10-5 2.048 Mbit/s tributary/VC-12/TU-12 mapping 10-5
Figure 10-8 Multplexing of TU-12 via a TUG-2 10-8
Figure 10-9 TU-12/TUG-2/TUG-3 multiplexing 10-8
Figure 10-10 Multiplexing of a TU-3 via a TUG-3 10-9
Figure 10-11 Multiplexing of three TUG-3s into a VC-4 10-9
Figure 10-12 Mapping of a VC-4 into an STM-1 via an AU-4/AUG 10-10
Figure 10-13 VC-12 Path Overhead (V5 byte) 10-10
Figure 10-14 Section overhead 10-12

xiii
About this document

This document provides a system level description of the TN-1C, TN-1P,
TN-1PH Headend and TN-1P Basestation multiplexers. This document
provides a concise introduction to the equipment and is recommended reading
for anyone working with the TN-1C, TN-1P, TN-1PH Headend or the TN-1P
Basestation.
For details on the deployment of the optional Nortel Networks OPTera Packet
Edge 10 (OPE-10) in a TN-1C multiplexer, refer to the OPTera Packet
Edge 10 User Guide 323-1043-401.
Note: Unless otherwise specified, the term TN-1P is used to refer to the
standard TN-1P, TN-1PH multiplexers and the TN-1P Basestation.
Indication of trademarks in this document

The asterisk after a name denotes a trademarked item. The title page and back
cover acknowledge all trademarked items.

xiv
Technical support and information

So far as Nortel Networks is aware the information in this document is correct.
If, however, you discover any errors or have comments regarding the
presentation of the content, please send details by email to:
IONNTPS@nortelnetworks.com
Nortel Networks provides a comprehensive technical support service for its

customers. The Nortel Networks Service Desk may be contacted at any time
on the following numbers:
United Kingdom
Freephone: 00800 8008 9009
Fax within the United Kingdom: 020 8945 3456
International
Within Europe: Freephone 00800 8008 9009
Outside of Europe: +44 20 8920 4618
Fax outside of the United Kingdom: +44 20 8945 3456
You can contact us via the Nortel Networks web site:

www.nortelnetworks.com
Select the link Customer Support.
EMC/Safety conformance
This product/product family complies with the provisions of
the Low Voltage Directive 73/23/EEC, and with the essential
protection requirements of the EMC Directive 89/336/EEC as
amended by 92/31/EEC, when it is properly installed and
maintained and when it is used for the purposes for which it is
intended.

1
1-1
System overview 1-
TN-1C multiplexer
The TN-1C is a stand-alone synchronous digital hierarchy (SDH) add/drop
multiplexer (ADM). See Figure 1-1.
The TN-1C comprises a multiplexer assembly containing:

• 8 x 2 Mbit/s ADM multiplexer main card mounted in a frame, which
provides electro-magnetic compatibility (EMC) screening
• a dummy or tributary extension card
• a connection panel
A single-slot TN-1C is available which comprises a multiplexer assembly

containing:
• 8 x 2 Mbit/s ADM multiplexer main card mounted in a frame, which
provides electro-magnetic compatibility (EMC) screening
• a connection panel
In the transmit direction, the TN-1C multiplexes plesiochronous electrical

tributary input signals (2 Mbit/s, 34/45 Mbit/s) into an aggregate STM-1
signal. The TN-1C transmits the STM-1 signal over an optical fibre link. In
the receive direction, the TN-1C demultiplexes incoming STM-1 signals from
the fibre link to provide tributary outputs (2 Mbit/s, 34/45 Mbit/s).
The main TN-1C ADM card provides up to eight 2 Mbit/s tributaries. There
are four variants of the tributary extension card, which provide the following
additional interfaces:
• 8 x 2 Mbit/s interfaces
• 24 x 2 Mbit/s interfaces
• 1 x 34/45 Mbit/s interface
• 2 x 34/45 Mbit/s interfaces
Note: If a tributary extension card is not fitted, a dummy card must be

fitted in its place to comply with electro-magnetic compatibility (EMC)
requirements.
In addition to the tributary extension card, there is an optional high

performance router card, which supports 10/100 BaseT LAN and a variety of

1-2 System overview
WAN interfaces. For a description of the TN-1C multiplexer Packet Edge 10

router card, refer to the OPTera Packet Edge 10 User Guide 323-1043-401.
TN-1P and TN-1PH headend multiplexers

The TN-1P is a stand-alone SDH point-to-point (terminal) multiplexer. The
TN-1P comprises a multiplexer assembly containing a single 4 x 2 Mbit/s
multiplexer card mounted in a frame, which provides EMC screening, and a
connection panel (see Figure 1-2). You can upgrade the 4 x 2 Mbit/s
Release 5.1 hardware version of the TN-1P to support 8 x 2 Mbit/s tributaries
by replacing the 4 x 2 Mbit/s multiplexer card with an 8 x 2 Mbit/s ADM
card. A TN-1P which contains an 8 x 2 Mbit/s ADM card operates as a
single-slot TN-1C with limited functionality, and identifies itself to the
element controller (EC-1) as a TN-1C.
The TN-1PH headend contains up to twelve multiplexers (each functionally

equivalent to a TN-1P) mounted in a single headend subrack (see Figure 1-3).
In the transmit direction, the TN-1P multiplexes up to four plesiochronous

2 Mbit/s electrical tributary input signals into an aggregate STM-1 signal. The
TN-1P transmits the STM-1 signal over an optical fibre link. In the receive
direction, the TN-1P demultiplexes incoming STM-1 signals from the fibre
link to provide up to four 2 Mbit/s tributary outputs.
TN-1P Basestation multiplexer

The TN-1P Basestation is a rack mounted, point-to-point SDH multiplexer,
based on the TN-1P. The TN-1P Basestation has the following configurations:
• unprotected optics with 4 x 2 Mbit/s tributaries
• protected optics with 4 x 2 Mbit/s tributaries
• ADM with 8 x 2 Mbit/s tributaries (see note below)
You can upgrade the 4 x 2 Mbit/s versions of the TN-1P Basestation to

support 8 x 2 Mbit/s tributaries by replacing the 4 x 2 Mbit/s multiplexer card
with an 8 x 2 Mbit/s ADM card. A TN-1P Basestation which contains an
8 x 2 Mbit/s ADM card operates as a TN-1C with limited functionality, and
identifies itself to the EC-1 as a TN-1C.
Note: Refer to the TN-1C/TN-1P Installation Procedures 323-1081-200

for information on how to upgrade the TN-1P and TN-1P Basestation.
The TN-1P Basestation is suitable for installations where equipment height is

restricted and only front access is available.
The TN-1P Basestation comprises a rack-mounting shelf assembly containing

a single multiplexer card mounted in a frame, which provides EMC
screening, a rear connection panel and a front connection panel. See
Figure 1-4.

System overview 1-3
Figure 1-1
TN-1C general view
1
Backplane
connector
Connector
Fan panel
EMC
enclosure
Secondary
fan optional)
Secondary fan controller

card (optional)
Main 8x2 Mbit/s Tributary extension card or

ADM card PE10 router card
Note: The TN-1C illustrated is the 16 x 2 Mbit/s version.

The secondary fan is an optional item for harsh environments.

1-4 System overview
Figure 1-2
TN-1P and single-slot TN-1C general view
Fan
EMC screen
Connection
panel
Multiplexer unit
Note 1: At Release 5, the TN-1P connection panel supports 4 x 2 Mbit/s tributaries.

At Release 5.1, the TN-1P connection panel supports 8 x 2 Mbit/s tributaries.
Note 2: The fan is not fitted to Release 5 hardware.

System overview 1-5
Figure 1-3
TN-1P Headend subrack general view
1
100_02a
Connection panel
Mounting flanges
Plug-in Unit area
Fibre tray position

1-6 System overview
Figure 1-4
TN-1P Basestation general view
Rear connector panel

Cable tie
holders (as
Craft Access Terminal
required)
(CAT)
Front connector
Power panel
connector
Fan
Integral
Right-hand
mounting
bracket
Integral fibre
spool
2 Mbit/s tributaries (75 Ω BNC).
Four pairs are used on the 4 x
2 Mbit/s versions.
Eight pairs are used on the 8 x
2 Mbit/s ADM version. Shown with multiplexer
Integral
card extended
Left-hand
mounting
bracket
Note: The fan is not fitted to Release 5 hardware.

System overview 1-7
System configuration - TN-1C 1

The TN-1C multiplexer can operate in any of the following configurations:
• point-to-point terminal multiplexer
• path protected 2-fibre ring
• ADM loop feeder
Point-to-point terminal multiplexer

The TN-1C multiplexer can be used as a conventional terminal multiplexer in
a point-to-point arrangement for delivery of a number of 2 Mbit/s or
34/45 Mbit/s tributary links over an STM-1 fibre link. Figure 1-5 shows a
protected point-to-point system. The tributary input signals are multiplexed
into an STM-1 signal, and transmitted over the fibre link to the other end
where the 2 Mbit/s or 34/45 Mbit/s signals are reconstructed.
Figure 1-5
TN-1C point-to-point terminal
Craft Access
Terminal
Tributary interfaces Tributary interfaces
Local Partner
RS232C TN-1C TN-1C
connection
LAN EC-1
Path protected 2-fibre ring

The path protected 2-fibre ring configuration provides diverse routing which
overcomes common mode faults and thus provides protection against a fault
in any optical path. Tributaries that require protection (e.g. Private Circuit
[PC] traffic) are routed both ways around the ring. At the receiving
multiplexer, traffic from the one of the aggregate ports is used unless there is a
fault when traffic from the other aggregate port is used (see ‘Path protection
switching’ on page 1-26 and ‘Path protection’ on page 2-13).
A possible application of this configuration is for feeding 2 Mbit/s and/or

34/45 Mbit/s signals in a local loop (‘loop feeder’) where one of the TN-1Cs
is located in a central office site. Signals may be sourced from a switch (for
example, DMS 100), connected to the multiple 2 Mbit/s interfaces in the
TN-1C, and distributed to remote locations where switch remotes or primary
multiplexers are located.

1-8 System overview
Another possible application is to carry high-rate data services, such as

34 Mbit/s LAN interconnection. A ring can be used between several locations
and provides high-speed data flow.
The ring may consist of TN-1Cs and (possibly) TN-1Xs or TN-1X/Ss.

Figure 1-6 shows a path protected 2-fibre ring application.
Figure 1-6
TN-1C in a 2-fibre path protection ring
EC-1
LAN
2 Mbit/s and 34/45 Mbit/s
tributary interfaces 2 Mbit/s and 34/45 Mbit/s
tributary interfaces
TN-1C
TN-1C
TN-1C
TN-1C
TN-1C
2 Mbit/s and
34/45 Mbit/s
tributary interfaces RS232C
connection
Craft Access Terminal
ADM loop feeder

The TN-1C can be used in an ADM loop feeder configuration to provide a
spur from a SDH ring. In this configuration, the TN-1C operates as it would
in the case of a point-to-point terminal multiplexer. This configuration can
also be used to drop traffic from an ADM in a larger transport network to the
TN-1C. Figure 1-7 shows a ADM loop feeder configuration.

System overview 1-9
Figure 1-7
TN-1C connected to an ADM STM-1 tributary
1
ADM
ADM
STM-1o tributary
STM-1o tributary
STM-1o tributary
LAN
EC-1
TN-1C TN-1C
2 Mbit/s and 34/45 Mbit/s

tributary interfaces
ATU application
In the TN-1C asynchronous telemetry unit (ATU) application, the TN-1C is
used in an SDH ring with TN-1X ADMs (Figure 1-8). The ATU allows the
transport of asynchronous management (telemetry) information over the SDH
network.
The TN-1C is located in a street cabinet site with an external plesiochronous

digital hierarchy (PDH) access multiplexer (for example a Nortel Networks
PDMX-E or UE3000). The external equipment management system
communications are passed through a headend ATU that maps the external
equipment address to the respective TN-1C open systems interconnect (OSI)
address. The messages are sent via the SDH system LAN and the SDH
overhead to the TN-1C and are then passed to the equipment concerned
through the TN-1C point-to-multipoint RS-485 port (RS-232 port on early
hardware). This application provides a simple method of using a PDH access
multiplexer as a feed to an SDH system.
The TN-1C supports two ATU protocols:

• High-level data link control (HDLC) for PDMX-E

1-10 System overview
• Point-to-point protocol (PPP) for UE3000.
For information about the head-end ATU functionality and use, see TN-1X
Asynchronous Telemetry Unit System Description, 323-1063-100.
Figure 1-8
Typical TN-1C ATU application
External
EC-1 equipment
manager
LAN Headend ATU
TN-1X LAN
TN-1X
External
TN-1C equipment
RS-485
connector cable
System configuration - TN-1P, TN-1PH

The TN-1P multiplexer can operate in any of the following configurations:
• point-to-point terminal multiplexer
• terminal multiplexer spurred from an SDH ring
• terminal multiplexer or one of a number of terminal multiplexers in a hub
type arrangement
In all configurations one multiplexer unit of a TN-1P Headend subrack is

equivalent to a TN-1P although only one end of a point-to-point system can
be a Headend TN-1P.
Point-to-point terminal multiplexer

The TN-1P multiplexer can be used as a conventional terminal multiplexer in
a point-to-point arrangement for delivery of up to four (or eight with upgrade)
2 Mbit/s tributary links over an STM-1 fibre link. Figure 1-9 shows a
protected point-to-point system. The tributary input signals are multiplexed
into an STM-1 signal, and transmitted over the fibre link to the other end
where the 2 Mbit/s signals are reconstructed.

System overview 1-11
For TN-1P, the path can be either protected or unprotected, depending on the 1
TN-1P variant used (see page 1-31).
Figure 1-9
TN-1P protected point-to-point STM-1 line system
Headend
up to four up to four
(eight with A Working A
(eight with
upgrade) upgrade)
2 Mbit/s TN-1P TN-1P 2 Mbit/s
tributaries tributaries
B Standby B
Terminal multiplexer spur from an SDH ring

The TN-1P can be used as a terminal multiplexer spur from an SDH ring
providing an unprotected or protected STM-1 spur. Figure 1-10 shows both
applications.
Figure 1-10
Terminal multiplexer spur
tributaries
ADM
tributaries ADM ADM tributaries
ADM ADM
STM-1 optical STM-1 optical

1+1 Protected spur Unprotected spur
TN-1P TN-1P
up to four (eight up to four (eight

with upgrade) with upgrade)
2 Mbit/s tributaries 2 Mbit/s tributaries

Hub configuration
The TN-1P can be used in a hub configuration where a number of remote s
from different locations are connected to a central network element.
Figure 1-11 shows both protected and an unprotected TN-1P links feeding a
central office TN-1X hub which connects via an ADM into an STM-16 ring.
Figure 1-11
Hub configuration
STM-16
STM-16
ADM
2 Mbit/s
tributaries
STM-4
STM-1
TN-1P
Central
Office STM-4 TN-1P* STM-1
Location aggregate
TN-1X STM-1
Hub
STM-1 optical TN-1P
tributaries
TN-1P*
2 Mbit/s
tributaries
STM-1
STM-1 STM-1
TN-1P
TN-1P
2 Mbit/s 2 Mbit/s
* TN-1P or TN-1P Headend or TN-1P Basestation variant

within Central Office Location

ATU application 1
In the TN-1P ATU application, the TN-1P is used as a spur from a TN-1X
ADM as part of an SDH network (Figure 1-12). The ATU allows the transport
of asynchronous management (telemetry) information over the SDH network.
The TN-1P uses an RS-232 port for the ATU application.
The TN-1P is located in a street cabinet site with an external PDH access
multiplexer (for example a Nortel Networks PDMX-E or UE3000). The
external equipment management system communications are passed through
a headend ATU that maps the external equipment address to the respective
TN-1P OSI address.
The messages are sent via the SDH system LAN and the SDH overhead to the
TN-1P and are then passed to the equipment concerned through the TN-1P
RS-232 ATU port. In addition to the external system messages, the TN-1P to
TN-1X optical link has the capacity to carry up to eight 2 Mbit/s outputs from
the external equipment to the SDH network. This provides a simple method of
using a PDH access multiplexer as a feed to an SDH system.
The TN-1P supports two ATU protocols:

• High-level data link control (HDLC) for PDMX-E
• Point-to-point protocol (PPP) for UE3000.
For information on the Headend ATU functionality and use, see ‘TN-1X
Asynchronous Telemetry Unit System Description, 323-1063-100’.
Clear channel telemetry

The clear channel telemetry function allows equipment outside the
transmission network to pass asynchronous ASCII messages at 19200 bit/s
across the transmission network. This function is supported by TN-1C and
TN-1P. The throughput is limited to four messages per second. See “Clear
channel telemetry” on page 3-3 for more details.

Figure 1-12
Typical TN-1P ATU application
External
EC-1 equipment
manager
Headend ATU
LAN card
TN-1X LAN
TN-1X
TN-1X
RS232 connector
cable
TN-1P
RS232/RS485 External
converter equipment
up to four (eight with upgrade)
2 Mbit/s tributaries

Mechanical description 1
The TN-1C (see Figure 1-1) and standard TN-1P (see Figure 1-2) have the
same mechanical construction, except that the TN-1C can contain an optional
tributary extension card. If the tributary extension card is not fitted to a TN-1C,
a dummy card is fitted in its place to provide EMC compliance. The TN-1P
does not have the extension card. The single-slot TN-1C does not contain the
optional tributary extension card and has the same mechanical construction as
the TN-1P.
The TN-1P Headend (see Figure 1-3) is a subrack suitable for 19 inch or
ETSI rack mounting. The TN-1P Headend contains up to 12 TN-1P Main
Point-to-Point (MPP) units and a Subrack End Processor (SEP) unit. The
backplane extends upwards above the MPP unit mounting area to provide a
connection panel for all of the copper cabling, including the craft access
terminal (CAT) and LAN connections. A craft access panel (CAP) is fitted on
the right hand side of the subrack. The CAP provides local status indications,
an alarm acknowledge push-button, and a display and push-button to select
which of the MPP units is connected to the CAT socket. A fibre tray is
provided immediately below the subrack for the management of optical
aggregate fibres.
The TN-1P Basestation (see Figure 1-4) is based on the TN-1C/TN-1P

platform. The main changes from the standard TN-1P are as follows:
• Horizontal mounting into a 19-inch or European Telecommunications
Standards Institute (ETSI) rack or cabinet
• A backplane that supports 8 x 2 Mbit/s tributaries.
• Front access for 75 Ω tributaries, craft access terminal (CAT), power and
optical connections.
• Fibre management is carried out externally.
Enclosure types
The TN-1C or standard TN-1P is packaged in a single, lockable enclosure
that can be mounted on a wall in customer premises, in a street cabinet, or in a
rack. For Release 5.1 hardware, the enclosure is plastic (earlier releases can
have either a plastic or metal enclosure). The enclosure contains an EMC
frame with a connector panel fitted with the multiplexer card. The TN-1C can
be fitted with an optional tributary extension card or router card.
The TN-1PH Headend has no enclosure and is mounted in a rack.
The TN-1P Basestation has no enclosure and is mounted in a street cabinet or

in a rack. The TN-1P Basestation comprises a shelf which contains a
front-access connection panel and an EMC frame fitted with the main
multiplexer card and a connector panel.
Mounting
The TN-1C or standard TN-1P enclosure can be rack mounted or wall
mounted, depending on the environment in which it is deployed, see
Figure 1-13. The TN-1C can be installed in a street cabinet.

A hardware pin located on the TN-1P/TN-1PH main card indicates whether

the card is in a TN-1PH unit.
The TN-1P Basestation can be installed in a rack or street cabinet. See

Figure 1-14 for typical deployment of a TN-1P Basestation.
Figure 1-13
Typical TN-1C/TN-1P installations
Tributary Optical
cables fibres
Tributary Multi-
cables plexer
d.c. power
cable
PSU
a.c. power
cable Rack mounted multiplexer.
Optical fibres The power supply is taken from
the rack
Wall mounted multiplexer with
power supply
Figure 1-14
Typical TN-1P Basestation installation
Tributary d.c. power

cables cable
Optical
fibres
Rack mounted multiplexer.

The power supply is taken from the rack

Wall mounting 1
The TN-1C and the standard TN-1P multiplexer can be used with a dedicated
power supply unit (PSU) mounted in a matching enclosure, or can be powered
from a suitable customer power supply. The units are neutrally coloured and
designed to be unobtrusive in customer premises.
Rack mounting
• When rack-mounted, the TN-1C and the standard TN-1P multiplexer are
held in the same enclosure as used for wall mounting and the entire
enclosure is mounted on runners, in a standard ETSI or a 19 inch rack. In
this situation, the multiplexer uses the rack PSU.
• TN-1P Basestation is mounted directly onto the framework structure in a
standard ETSI or a 19 inch rack.
Street cabinet
• TN-1C street cabinet installations (not illustrated) are wholly dependent
upon the street cabinet type. The TN-1C is mounted without the cover and
can use the dual fan option (see page 1-28).
• TN-1P Basestation street cabinet installations (not illustrated) are wholly
dependent upon the street cabinet type. TN-1P Basestation does not have a
cover and can therefore be directly mounted without a fan.
TN-1PH rack mounting

Sufficient ventilation for a TN-1PH is provided through the fibre tray and
upper (connection panel) part of the subrack, so that two TN-1PH subracks
can be mounted in a 2.2 m rack (Figure 1-3). If two TN-1PH subracks are
mounted in one 2.2 m ETSI rack, they must be mounted with a fibre tray
between them, to maintain adequate ventilation. The two TN-1PH subracks
must be fitted as near the top of the 2.2 m ETSI rack as possible so that future
equipment can be installed.

Connectivity
Channel numbering schemes
The TN-1C and TN-1P use either the ITU-T ‘KLM’ or the ‘ETSI’ channel
numbering schemes to identify aggregate payload instances. The user can
enter aggregate payload instances using either the ‘KLM’ or ‘ETSI’ channel
numbering scheme. All outputs from the TN-1C and TN-1P use the ‘KLM’
channel numbering scheme. When using the connection management facility
on the Element Controller, the screens indicate the ‘KLM’ channel number
and the equivalent ‘ETSI’ channel numbers.
KLM channel numbering

The ‘KLM’ channel numbering scheme uses a 3-figure vector (K, L, M) to
represent channels within the virtual container (VC) payload structure:
• K = TUG-3 (1 to 3)
• L = TUG-2 (1 to 7)
• M = TU-12 (1 to 3)
The ‘KLM’ channel numbering scheme indicates the level of multiplexing,

allowing a TUG-3 containing a single TU-3 to be distinguished from a TUG-3
containing seven TUG-2s. This allows, for example, differentiation of a VC-3
(34/45 Mbit/s) signal from a VC-12 (2 Mbit/s) signal:
• ‘1,2,3’ - indicates TUG-3 ‘1’, TUG-2 ‘2’, TU-1 ‘3’ (i.e. a 2 Mbit/s VC-12
signal)
• ‘2,0,0’ - indicates TUG-3 ‘2’ (i.e. a 34/45 Mbit/s VC-3 signal)
Table 1-1 provides cross-references between the ‘KLM’ numbering scheme

and the ‘ETSI’ numbering scheme. The table also indicates the Nortel
Networks numbering scheme which was used on previous releases.
Refer to ‘Appendix A: Synchronous digital hierarchy’ for further information

about the SDH structure.

Table 1-1
Channel numbering schemes
1
TUG-3 TUG-2 TU-12 ETSI Nortel TUG-3 TUG-2 TU-12 Nortel ETSI
K L M (ITU-T) K L M (ITU-T)
1 1 1 1 1 1 1 1 1 1
1 1 2 2 22 2 1 1 2 22
1 1 3 3 43 3 1 1 3 43
1 2 1 4 4 1 2 1 4 4
1 2 2 5 25 2 2 1 5 25
1 2 3 6 46 3 2 1 6 46
1 3 1 7 7 1 3 1 7 7
1 3 2 8 28 2 3 1 8 28
1 3 3 9 49 3 3 1 9 49
1 4 1 10 10 1 4 1 10 10
1 4 2 11 31 2 4 1 11 31
1 4 3 12 52 3 4 1 12 52
1 5 1 13 13 1 5 1 13 13
1 5 2 14 34 2 5 1 14 34
1 5 3 15 55 3 5 1 15 55
1 6 1 16 16 1 6 1 16 16
1 6 2 17 37 2 6 1 17 37
1 6 3 18 58 3 6 1 18 58
1 7 1 19 19 1 7 1 19 19
1 7 2 20 40 2 7 1 20 40
1 7 3 21 61 3 7 1 21 61
2 1 1 22 2 1 1 2 22 2
2 1 2 23 23 2 1 2 23 23
2 1 3 24 44 3 1 2 24 44
2 2 1 25 5 1 2 2 25 5
2 2 2 26 26 2 2 2 26 26
2 2 3 27 47 3 2 2 27 47
2 3 1 28 8 1 3 2 28 8
2 3 2 29 29 2 3 2 29 29
2 3 3 30 50 3 3 2 30 50
2 4 1 31 11 1 4 2 31 11
2 4 2 32 32 2 4 2 32 32
2 4 3 33 53 3 4 2 33 53
2 5 1 34 14 1 5 2 34 14
2 5 2 35 35 2 5 2 35 35
2 5 3 36 56 3 5 2 36 56
2 6 1 37 17 1 6 2 37 17
2 6 2 38 38 2 6 2 38 38
2 6 3 39 59 3 6 2 39 59
2 7 1 40 20 1 7 2 40 20
2 7 2 41 41 2 7 2 41 41
2 7 3 42 62 3 7 2 42 62
3 1 1 43 3 1 1 3 43 3
3 1 2 44 24 2 1 3 44 24
3 1 3 45 45 3 1 3 45 45
3 2 1 46 6 1 2 3 46 6
3 2 2 47 27 2 2 3 47 27
3 2 3 48 48 3 2 3 48 48
3 3 1 49 9 1 3 3 49 9
3 3 2 50 30 2 3 3 50 30
3 3 3 51 51 3 3 3 51 51
3 4 1 52 12 1 4 3 52 12
3 4 2 53 33 2 4 3 53 33
3 4 3 54 54 3 4 3 54 54
3 5 1 55 15 1 5 3 55 15
3 5 2 56 36 2 5 3 56 36
3 5 3 57 57 3 5 3 57 57
3 6 1 58 18 1 6 3 58 18
3 6 2 59 39 2 6 3 59 39
3 6 3 60 60 3 6 3 60 60
3 7 1 61 21 1 7 3 61 21
3 7 2 62 42 2 7 3 62 42
3 7 3 63 63 3 7 3 63 63

Port/channel designations
Connections can be made to/from the following tributaries and aggregates.
Note: VC-3 operation is only possible for the TN-1C.
Tributary ports
2 Mbit/s tributary ports are defined by the unit slot number and tributary
instance in the form ‘Ss-n’ where:
• ‘s’ is the slot number within the multiplexer.
— for TN-1C, the slot numbers are ‘1’ for the main 8x2 Mbit/s ADM card
and ‘2’ for the tributary extension card.
— for TN-1P, the slot number is always ‘1’.
• ‘n’ is the port number within the denoted slot. The available ports are as
follows:
— ‘1’ to ‘8’ for 2 Mbit/s tributaries on the main TN-1C ADM card.
— ‘1’ to ‘8’ for 2 Mbit/s tributaries on the TN-1C 8 x 2 Mbit/s extension
card.
— ‘1’ to ‘24’ for 2 Mbit/s tributaries on the TN-1C 24 x 2 Mbit/s
extension card.
— ‘1’ or ‘2’ for 34/45 Mbit/s tributaries on the TN-1C 34/45 Mbit/s
extension card
— ‘1’ to ‘4’ for 2 Mbit/s tributaries on the TN-1P 4 x 2 Mbit/s card.
— ‘1’ to ‘8’ for 2 Mbit/s tributaries on the TN-1P 8 x 2 Mbit/s card.
For example:
• ‘S1-2’ is port 2 on the main TN-1C ADM card or the TN-1P.
• ‘S2-1’ is port 1 on the TN-1C extension card.
STM-1 aggregates
The STM-1 aggregate channels can be defined using either the ‘KLM’ or the
‘ETSI’ numbering scheme.
• KLM numbering scheme
STM-1 aggregate channels are defined by the aggregate port and the KLM
channel number in the form ‘sdh_port-J1-Kklm’.
Where:
— ‘sdh_port’ is either aggregate ‘A’ or ‘B’.
— ‘J1’ indicates the AU4 selection (always ‘J1’)
— ‘klm’ identifies a specific payload.
– for VC-12s, ‘k’= ‘1’ to ‘3’, ‘l’ = ‘1’ to ‘7’, ‘m’ = ‘1’ to ‘3’
– for VC-3s, ‘k’ = ‘1’ to ‘3’, ‘l’ = ‘0’, ‘m’ = ‘0’.

For example, 1
— ‘A-J1-K261’ is TUG-3 ‘2’, TUG-2 ‘6’, TU-12 ‘1’ on aggregate A.
— ‘B-J1-K300’ is TUG-3 ‘3’ (i.e. a VC-3 signal) on aggregate B.
• ETSI numbering scheme

STM-1 aggregate channels are defined by the aggregate port and the ETSI
channel number in the form ‘sdh_port-TUsize-payload_instance’.
Where:
— ‘sdh_port’ is either aggregate ‘A’ or ‘B’.
— ‘TU_size’ identifies the TU size and can be either ‘TU12’ or ‘TU3’.
Note: TU3 is not applicable to the TN-1P.
— ‘payload_instance’ is:
– ‘1’ to ‘63’ for TU-12s
– ‘1’ to ‘3’ for TU-3s
For example,
— ‘A-TU12-37’ is TU-12 ‘37’ on aggregate A.
— ‘B-TU3-3’ is TUG-3 ‘3’ (i.e. a VC-3 signal) on aggregate B.
High order payload

Aggregate high order payloads identify the AU4 on an SDH aggregate (for
VC-4 passthrough connections only). High order payloads are defined by the
aggregate port in the form ‘sdh_port-J1’, where ‘sdh_port’ is either aggregate
‘A’ or ‘B’ (‘A-J1’ or ‘B-J1’).
Types of connections
The TN-1C and TN-1P support the following bidirectional connections:
• No connection:
If there is no connection, the channel is not in use. Therefore no low order
path (LP) alarms and no TU alarms (TU-LOP and TU-AIS) are reported
for this channel. No consequent actions will be initiated, and no
performance monitoring (PM) logs relating to the channel are generated.
• Add/Drop connection:
A tributary signal is connected to a specific channel (TU) in the STM-1
signal. The 34/45 Mbit/s tributaries (TN-1C only) are associated with a
TU-3, while the 2 Mbit/s tributaries are associated with TU-12s. For
unprotected connections, the tributary is connected to one of the aggregate
ports. For protected connections, an alternative payload instance in the
other aggregate ports for path protection is specified.
Note: In the case of the protected connections, the same channel number
must be used on the two aggregates.

• TU-12/TU-3 Through connection (TN-1C only):

A through connection connects matching channels between aggregates A
and B.
• VC-4 passthrough connection:
A VC-4 passthrough connection connects the VC- 4 contained in the
STM-1 signal between aggregates A and B. The VC-4 passthrough
connection supports any traffic type carried by an STM-1 signal and when
provisioned, all other path connections must be free. When a VC-4
passthrough connection is provisioned, only the RS, MS and AU-AIS
alarms are enabled, all other traffic alarms are disabled and reported
cleared. The VC-4s have no KLM numbers and are designated as A-J1 and
B-J1.
Connection parameters
The connections are defined using the parameters ‘s_pl[&p_pl] d_pl [BI]’
where:
• ‘s_pl’ is the source payload instance.
• ‘&p_pl’ is the alternative source payload for protected connections.
• ‘d_pl’ is the destination.
— For add/drop tributary connections, the destination will be a tributary
instance.
— For through connections (TN-1C only), the destination will be the
same payload instance in the aggregate not selected for ‘s_pl’. For
example, if A-J1-K261 is selected for the ‘s_pl’, B-J1-K261 should be
selected for ‘d_pl’ to provide a through connection.
• ‘[BI]’ indicates bidirectional. As all connections on the TN-1C and TN-1P
are bidirectional, this indicator can be omitted.
For example:
• ‘A-J1-K111 S1-1’ defines an unprotected add/drop connection between
2 Mbit/s tributary 1 on the TN-1C ADM or the TN-1P card and K111 in
aggregate A.
• ‘A-J1-K200&B-J1-K200 S2-1’ defines a protected add/drop connection
between tributary 1 on the TN-1C 34/45 Mbit/s extension card and TUG3
‘2’ in aggregate A, with an alternative connection to TUG3 ‘2’ in aggregate
B for path protection.
• ‘A-J1-K311 B-J1-K311’ defines a through connection between TUG-3 ‘3’,
TUG-2 ‘1’, TU-12 ‘1’ in aggregate A and TUG-3 ‘3’, TUG-2 ‘1’, TU-12
‘1’ in aggregate B.
• ‘A-J1 B-J1’ defines a bidirectional VC-4 passthrough connection between
the VC-4 in aggregate A and the VC-4 in aggregate B.

Default connections 1
The TN-1C (and TN-1P Basestation fitted with an 8 x 2 Mbit/s ADM card)
defaults to having no connections. The TN-1P (4 x 2 Mbit/s tributaries)
defaults to the following connections:
• Protected TN-1P
A-J1-K111&B-J1-K111 S1-1
A-J1-K112&B-J1-K112 S1-2
A-J1-K113&B-J1-K113 S1-3
A-J1-K121&B-J1-K121 S1-4
• Unprotected TN-1P
A-J1-K111 S1-1
A-J1-K112 S1-2
A-J1-K113 S1-3
A-J1-K121 S1-4
Note: The All Connect command can be used to make these default
connections on a TN-1P. The command only works if there are no existing
connections.
User labels
The TN-1C and TN-1P provide a user label feature. This feature allows the
user to give each connection a label consisting of up to 15 characters to assign
customer names payloads or ports that are part of a connection. The allowable
characters are the alpha-numeric characters (A to Z, a to z, 0 to 9), dash (-), and
underscore (_). The user labels appear on all alarm and performance
monitoring messages and reports associated with the connections. The display
of user labels can be enabled or disabled by the user. The default labels
associated with connections are as follows:
• For drop connections, the PDH port reference is used (for example,
‘S2-1’).
• For through connections (TN-1C only), the alternate aggregate payload
reference is used (for example, ‘B-J1-K123’).
• For VC-4 through connections, the default user label is ‘J1’.
Traffic mode
The user can configure each TN-1C or TN-1P tributary input for one of four
traffic modes:
• Traffic on
• Traffic off
• Traffic auto
• Traffic standby
The ‘traffic on’ state enables the tributary to carry traffic. The ‘traffic off’
state disables the traffic carrying capability and, with the exception of
PPI-Unexp_Signal alarm, disables alarms associated with that particular
tributary. In the ‘traffic off’ state, an AIS is sent towards the tributary line, and

a VC-UNEQ (i.e. the signal label ‘000’ for VC-12s or ‘0H’ for VC-3s) is sent
towards the channel to which it is connected.
The ‘traffic auto’ state enables the tributary to carry traffic when it is part of a
connection or is in the synchronization source hierarchy. When the tributary is
not part of a connection and is not in the synchronization source hierarchy,
PPI-AIS is sent and PPI performance monitoring (PM) counts are counted if
traffic is present. Alarm behaviour is the same as the ‘traffic off’ mode. This
is the default setting.
The ‘traffic standby’ mode allows a tributary that is part of a generally unused
connection to carry traffic when the remote equipment is present. When a
signal is detected, a PPI-Unexp_Signal alarm is raised. This alarm notifies the
user to select ‘traffic auto’ mode for that tributary and the alarm is cancelled.
When the signal is removed, a PPI-LOS alarm is raised, this notifies the user
to reselect ‘traffic standby’ mode for the tributary. In the ‘traffic standby’
mode, PM counts are not counted for tributaries.
Path trace
The SDH path overhead provides a path trace capability which allows internal
paths to be verified at the VC-4 level. The multiplexer allows the user to
determine and display the contents of the path trace string. This is useful as a
means of checking the optical fibre connections whenever changes are made.
The path trace identifier can be provisioned by the user for each STM-1 link
and for each direction (receive/transmit) separately. The user can also display
the actual received pattern for maintenance purposes. When a VC-4
passthrough connection is in operation, the path trace identifier for both
aggregates can be viewed at the network element, although it can not be
provisioned.
The VC-4 path overhead bytes contain a path trace byte (J1). This byte is used
to cyclically transmit a 16 byte string. The string comprises a frame starter
marker byte (which contains a CRC-7 calculation over the previous frame)
and 15 user configurable bytes. The checksum can be either automatically
generated by the system, or entered by the user. The incoming string is
checked against the expected receive string, any discrepancy generates a
HP-Path_Trace alarm.
Note: The default settings are ‘RX_UNALLOCATED_’ for the receive

value and ‘TX_UNALLOCATED_’ for the transmit value.
For example, if two multiplexers (A and B) are connected together, the user
may set the transmit value of multiplexer ‘A’ to ‘route_1_AtoB’ and the
receive value of multiplexer ‘B’ to ‘route_1_AtoB’. Likewise, the transmit
value of multiplexer ‘B’ may be set to ‘route _1_BtoA’ and the receive value
of multiplexer ‘A’ to ‘route_1_BtoA’.
Refer to Browser User Guide, 323-1081-403 and Network Administration

Procedures, 323-1081-310 for further details of the operation of the path trace
facility.

Note: The TN-1C and TN-1P do not process the RS path trace byte (J0) 1
and the low order path trace byte (J2). Minor problems can occur when
interconnecting with equipment that support these bytes (for example, the
OPTera Metro 4100 supports the J0 byte on STM-1 tributary cards). The
problems are related to service assurance and are not traffic or service
affecting.
Signal label
The path overhead of the SDH includes signal label information which
indicates the composition of the signal. The signal labels (except VC-4) are
automatically set according to the traffic status (on/off/auto/standby) as
defined in Table 1-2.
If the received signal label is not as expected, a HP-PLM (VC-4) or LP-PLM

(VC-12 and VC-3) alarm is raised.
Table 1-2
Signal label data
VC level Traffic on Traffic off Traffic auto Traffic standby

Connection Connection Connection
present or in present, traffic present, no
sync hierarchy, present traffic
traffic present
VC-12 Transmit ‘010’ - ‘000’ - ‘010’ - ‘010’ - ‘000’ unequipped
(bits 5 to 7 of value Asynchronous Unequipped Asynchronous Asynchronous
V5 byte) floating floating floating
Expected ‘010’ - ‘000’ - ‘010’ - ‘010’ - ‘010’ -
receive Asynchronous Unequipped Asynchronous Asynchronous Asynchronous
value floating floating floating floating
or or or or
‘001’ - ‘001’ - Equipped ‘001’ - Equipped ‘001’ - Equipped
Equipped non-specific non-specific non-specific
non-specific
VC-3 Transmit ‘04H’ - ‘00H’ - ‘04H’ - ‘04H’ - ‘00H’ unequipped
(C2 byte) value Asynchronous Unequipped Asynchronous Asynchronous
(TN-1C only) Mapping of Mapping of Mapping of
34/45 Mbit/s 34/45 Mbit/s 34/45 Mbit/s
Expected ‘04H’ - ‘00H’ - ‘04H’ - ‘04H’ - ‘04H’ -
receive Asynchronous Unequipped Asynchronous Asynchronous Asynchronous
value Mapping of Mapping of Mapping of Mapping of
34/45 Mbit/s 34/45 Mbit/s 34/45 Mbit/s 34/45 Mbit/s
or or or or
‘01H’ - ‘01H’ - Equipped ‘01H’ - Equipped ‘01H’ - Equipped
Equipped non-specific non-specific non-specific
non-specific
VC-4 Transmit ‘02H’ - TUG structure
(C2 byte) value
Expected ‘02H’ - TUG structure
receive ‘01H’ - Equipped non-specific
value or
‘13H’ - ATM mapping

Path protection switching

Path protection switching (PPS) is provided by the multiplexer. Switching
occurs at the following levels to provide protection over the entire path:
• for 2 Mbit/s signals: TU-12 level,
• for 34/45 Mbit/s signals: TU-3 level
Note: The TU-3 level is applicable to the TN-1C multiplexer only.
The transmitting multiplexer sends the same data on both optical paths and
the receiving multiplexer, demultiplexes the signals from both aggregates and
monitors the validity of all incoming TU-12s and TU-3s.
On receipt of invalid TU-12s or TU-3s, the receiving network element

switches to the equivalent TU-12 or TU-3 from the standby optical link,
providing protection against a fault in the working path. Path protection
switching is non-revertive, that is, when the failed link is restored, it becomes
the standby; the receiving multiplexer only switches paths in the event of a
path failure. The user may select (with the User Interface) which aggregate to
use as the working path and, if required, may enable or disable PPS.
Further details of path protection switching are given in ‘Path protection’ on

page 2-13.
Management and communications

The TN-1C and TN-1P network elements are managed using application
software embedded within each network element. The configuration and
status information is stored in each network element and not in the
management tools used to control them.
The network element can be monitored and configured using the Browser
User Interface or the Command Line User Interface. The Browser is an
HTML interface to the network element application software and presents the
results as an intuitive point-and-click interface inside the Netscape Navigator
hypertext browser. The Command Line User Interface is accessed using
terminal application software.
The Browser and the Command line User Interface can be accessed as follows:
• locally from a craft access terminal (CAT) connected directly or remotely
to the network element,
• from the Element Controller EC-1
• via reach through from Nortel Networks Preside manager.
Communication with the EC-1 is via the embedded control channel (ECC) in
the section overhead of the STM-1 signals and/or LANs. The EC-1 can
manage TN-1C, TN-1P, TN-1X, and TN-4XE network elements and provides
additional alarm and monitoring facilities. The EC-1 also interfaces to the
higher level of network management such as Nortel Networks Preside.

The CAT can be connected directly to each network element to manage its 1
operation locally, or may be used to manage a remote ‘partner’ network
element.
Rack alarm adaptor

When the TN-1C or standard TN-1P are rack mounted, they can use an
optional external rack alarm adaptor (RAA) that allows the TN-1C or TN-1P,
via its external alarm facility, to drive a rack alarm system. The RAA provides
two alarm status LEDs and an alarm receiving attention button. The RAA
derives its power supply (–48 V d.c. at up to 120 mA) from the rack. The
TN-1PH multiplexer has a built-in rack alarm adaptor.
A rack alarm adaptor is not used with TN-1P Basestation.
Software
Each TN-1P and TN-1C multiplexer card has two flash memory banks to hold
software, banks ‘A’ and ‘B’. These flash memory banks hold individual
copies of the application software. The boot sector of bank ‘A’ holds the
foundation software.
There are two types of software associated with the multiplexer:

• foundation software
• application software
For more information, refer to “Software” on page 3-6.
Foundation software
The foundation software is executed at system start-up or reset. It is a short
program that selects one of the two application software banks. The foundation
software selects the bank as follows:
• after a cold (traffic affecting) restart, occurring at system switch-on or
when the user requests a cold restart, the current bank is used.
• after a warm (non-traffic affecting) restart, the bank is selected by the user
(default is current bank).
A checksum is performed on the selected software, if the test is successful,

that software is run. If the first software bank fails the checksum, the second
bank is tested; if this passes the test then it will be run. Failure of both
software banks causes an error and the system is rendered inoperative.
Application software
The application software resides in two flash memory banks and can be
functionally subdivided into two main areas:
• Operations software
• User interface software

The operations software controls the operation and equipment management

functions of the multiplexer (e.g. multiplexing, communication, alarm
monitoring and synchronisation).
The equipment management functions of the multiplexer are performed by

the synchronous equipment management function (SEMF) of the multiplexer
application software.
The user interface software is a hierarchical, text-based user interface which

allows an operator to configure and control the method of operation of the
network element. This is accessed using a CAT running VT-100 emulation
software, or via the EC-1.
Software download
During the operational life of the multiplexer, new versions of the application
software can be downloaded using the user interface from the CAT or the
EC-1.
Interfaces
A connector panel provides the external connections to each multiplexer. For
further information on connector panel configurations, refer to ‘External
interfaces’ on page 8-1.
Fan
A fan is fitted to the EMC enclosure of the TN-1C, TN-1P (not at Release 5),
TN-1P Basestation (not at Release 5). A fan is not fitted to the TN-PH.
The fan can be controlled automatically or manually:

• With automatic control: The fan switches on when the temperature exceeds
55° C and switches off when the temperature falls below 40° C.
• With manual control: The fan is switched on and off from the user interface
(UI). With manual control, a short delay exists between the fan on/off
command and the fan operation.
Where the TN-1C is operated in particularly harsh environments an optional

second fan can be installed. The second fan only operates if the first fan fails,
but does not clear the NE-Fan_Failed alarm. The second fan maintains the
correct working temperature until an engineer replaces the first fan.
WARNING
Rotating fan blades
Take care when the working on a TN-1C /TN-1P without a
cover as the fan blades are accessible.

Variants 1
TN-1C
Each TN-1C variant currently available can be either wall, rack or street
cabinet mounted. The variants are summarized in Table 1-3.
Table 1-3
TN-1C variants
Variant ADM card Tributary extension card Enclosure

(see Note 3) (see Note 3)
8 x 2 Mbit/s 8 x 2 Mbit/s Dummy card Plastic
8 x 2 Mbit/s + 8 x 2 Mbit/s 1 x 34/45 Mbit/s Plastic

1 x 34/45 Mbit/s
8 x 2 Mbit/s + 8 x 2 Mbit/s 2 x 34/45 Mbit/s Plastic

2 x 34/45 Mbit/s
16 x 2 Mbit/s 8 x 2 Mbit/s 8 x 2 Mbit/s Plastic
32 x 2 Mbit/s 8 x 2 Mbit/s 24 x 2 Mbit/s Plastic (see note 1)
8 x 2 Mbit/s 8 x 2 Mbit/s Dummy card Metal (see note 2)
16 x 2 Mbit/s 8 x 2 Mbit/s 8 x 2 Mbit/s Metal (see note 2)
8 x 2 Mbit/s + 8 x 2 Mbit/s 1 x 34/45 Mbit/s Metal (see note 2)

1 x 34/45 Mbit/s
8 x 2 Mbit/s + 8 x 2 Mbit/s 2 x 34/45 Mbit/s Metal (see note 2)

2 x 34/45 Mbit/s
Note 1: Thirty-two 2 Mbit/s connections are only available when using 120 Ω connection
interfaces. When using mixed 75 Ω/120 Ω connection interfaces, a maximum of twenty-four
2 Mbit/s connections are possible.
Note 2: This configuration is available as part of TN-1C Release 3/5 and cannot be ordered at
Release 5.1.
Note 3: The impedances for the 2 Mbit/s tributaries on the 8 x 2 Mbit/s ADM card and the 8 x
2 Mbit/s tributary extension card are configurable to either 75 Ω or 120 Ω. The impedances for
the first eight 2 Mbit/s tributaries of the 24 x 2 Mbit/s tributary extension card are configurable
to either 75 Ω or 120 Ω, the remaining sixteen 2 Mbit/s tributaires are 120 Ω only.
Each variant can be supplied with the following optical interfaces:

• short reach (1310 nm) S1.1 optics.
• long reach (1310 nm) L1.1 optics.
• long reach (1550 nm) L1.2 optics.

ADM card
Four variants of ADM card are available:
• Release 1 hardware 8 x 2 Mbit/s
• Release 3/5/5.1 hardware 8 x 2 Mbit/s (short reach 1310 nm optics)
• Release 3/5/5.1 hardware 8 x 2 Mbit/s (long reach 1310 nm optics)
• Release 3/5/5.1 hardware 8 x 2 Mbit/s (long reach 1550 nm optics)
Note: The impedances for the 2 Mbit/s tributaries on the 8 x 2 Mbit/s
ADM card are configurable to either 75 Ω or 120 Ω.
Tributary extension card

The TN-1C tributary extension card can be one of the following:
• 8 x 2 Mbit/s tributaries (Release 1 hardware)
• 8 x 2 Mbit/s tributaries with enhanced performance monitoring (framed
and CRC-4 functionality) (Release 3/5 hardware)
• 8 x 2 Mbit/s tributaries (Release 5.1 hardware)
• 24 x 2 Mbit/s tributaries (Release 5.1 hardware)
• 1 x 34/45 Mbit/s tributary (Release 3/5 hardware)
• 1 x 34/45 Mbit/s tributary with 45M AIS support (Release 5.1 hardware)
• 2 x 34/45 Mbit/s tributaries (Release 3/5 hardware)
• 2 x 34/45 Mbit/s tributaries with 45M AIS support (Release 5.1 hardware)
Note 1: If a tributary extension card is not fitted, a dummy card must be

fitted in its place to comply with electro-magnetic compatibility (EMC)
requirements.
Note 2: For details of the optional Packet Edge 10 router card, refer to the
OPTera Packet Edge 10 User Guide 323-1043-401.
Note 3: The impedances for the 2 Mbit/s tributaries on the 8 x 2 Mbit/s
tributary extension card are configurable to either 75 Ω or 120 Ω. The
impedances for the first eight 2 Mbit/s tributaries of the 24 x 2 Mbit/s
tributary extension card are configurable to either 75 Ω or 120 Ω, the
remaining sixteen 2 Mbit/s tributaires are 120 Ω only.
Connector panel
For Release 5.1 hardware, there are two types of connector panel (one for
TN-1C with extension slot and one for the single-slot TN-1C). For earlier
releases, there are a number of different connector panels. For further
information on connector panels, refer to ‘External interfaces’ on page 8-1.

TN-1P 1
The following TN-1P variants are available at Release 5.1:
• TN-1P with 4 x 2 Mbit/s tributaries and an unprotected optical link (the
multiplexer card has one electro-optical module).
• TN-1P with 4 x 2 Mbit/s tributaries and a protected optical link (the
multiplexer card has two electro-optical modules to provide 1+1
protection).
• TN-1PH Headend with 4 x 2 Mbit/s tributaries and an unprotected optical
link (the multiplexer card has one electro-optical module).
• TN-1PH headend with 4 x 2 Mbit/s tributaries and a protected optical link
(the multiplexer card has two electro-optical modules to provide 1+1
protection).
• TN-1P Basestation with 4 x 2 Mbit/s tributaries and an unprotected optical
link (the multiplexer card has one electro-optical module).
• TN-1P Basestation with 4 x 2 Mbit/s tributaries and a protected optical
link (the multiplexer card has two electro-optical modules to provide 1+1
protection).
• TN-1P Basestation with 8 x 2 Mbit/s tributaries and a protected optical
link (the multiplexer card has two electro-optical modules to provide 1+1
protection or ADM functionality).
All the TN-1P variants use short reach (1310 nm) S1.1 optics.
Connector panel
For Release 5.1 hardware, there is only one type of connector panel. Earlier
releases, have different connector panels. For further information on
connector panel variants, refer to ‘External interfaces’ on page 8-1
end of chapter

2-1
2
Equipment description 2-
The TN-1C/TN-1P network element multiplexes tributary inputs into an
STM-1 signal for transmission over an optical link to a remote network
element or into an SDH network. In the receive direction, the TN-1C/TN-1P
network element demultiplexes an incoming STM-1 signal from the optical
link to provide tributary outputs.
Figure 2-1 and Figure 2-2 show simplified block diagrams of the TN-1C and
TN-1P.
The TN-1C can provide any one of the following bi-directional electrical
tributary options:
• eight 2 Mbit/s tributaries
• sixteen 2 Mbit/s tributaries
• thirty-two 2 Mbit/s tributaries
• eight 2 Mbit/s tributaries and one 34/45 Mbit/s tributary
• eight 2 Mbit/s tributaries and two 34/45 Mbit/s tributary
The TN-1C has two STM-1 optical inputs and outputs, to provide
bidirectional protected operation.
Note: For details of the optional router card, refer to the OPTera Packet
The standard TN-1P has four 2 Mbit/s bidirectional tributaries in each

direction. The standard TN-1P can have either one STM-1 input and output
(unprotected) or two STM-1 inputs and outputs (protected).
The following versions of the TN-1P Basestation are available at Release 5.1:
• TN-1P Basestation with 4 x 2 Mbit/s unprotected multiplexer card and
S1.1 optics
• TN-1P Basestation with 4 x 2 Mbit/s protected multiplexer card and
S1.1 optics
• TN-1P Basestation with 8 x 2 Mbit/s ADM card and
S1.1 optics
Note: The 4 x 2 Mbit/s versions can be upgraded to the 8 x 2 Mbit/s ADM
version by replacing the multiplexer card.

2-2 Equipment description
The TN-1C and standard TN-1P are provided in a stand-alone enclosure. The
enclosure may be wall-mounted with an a.c. mains driven d.c. power supply
(or it may be powered from a suitable customer power supply), or mounted in
a rack (in which case it is powered from the rack power supply). The nominal
a.c. mains supply is 115/230 V.
The TN-1P Basestation has no enclosure. The TN-1P Basestation is mounted

in a rack and powered from the rack power supply, nominally –48 V d.c. The
multiplexers require an operating supply voltage in the range –20 V to
–72 V d.c.
Note: This equates to nominal earthed battery station voltages between

–24 V and –60 V.
The TN-1PH Headend subrack is also available, which contains the following:
• up to 12 TN-1P main point-to-point packs (MPP), each of which has the
functionality of one TN-1P.
• a subrack end processor (SEP), which provides a LAN connection for an
element controller EC-1 and consolidates the CAT access and alarms for
the multiple TN-1P MPPs.
• a craft access panel (CAP), which provides:
— status indications,
— an alarm acknowledge push-button,
— a means of selecting the CAT to each individual TN-1P MPP.
• A connection panel which provides connections for all of the electrical
tributaries, power, and support functions (CAT and LAN)

Figure 2-1
TN-1C block diagram
STM-1 interface
External sync
interface
Controller platform (CPU, FLASH & DRAM memories & other peripherals)
STM-1 STM-1
interface interface
LAN Interface CAT Interface ATU Interface External alarms

Power
Inputs & Outputs

supply
Aggregate B Aggregate A
Main ADM card
VC-3
VC-3
VC-12
VC-12
Timeslot
Timeslot
interchanger
interchanger
RS-485
Timing
source Extension card
interface PDH
(RS-232)
Mapper
Tributary block
PDH
PDH Line
Extension card*
Mapper Interface
Tributary
PDH Line
Interface
G.703 interfaces
G.703 interfaces
* Not applicable to single-slot TN-1C variants.

Figure 2-2
TN-1P block diagram
STM-1 interface
External sync
interface
(Note 1)
Controller platform (CPU, FLASH & DRAM memories & other peripherals)
STM-1 STM-1
interface interface
LAN Interface CAT Interface ATU Interface External alarms

Power
Inputs & Outputs

supply
Aggregate B Aggregate A
VC-12
VC-12
Timeslot
Timeslot
interchanger
RS-485
interchanger
Timing
source
Extension
(RS-232)
PDH
Tributary block
Mapper
PDH
Line
Interface
(Note 2)
G.703 interfaces
Note 1: External Synchronisation input available only for a TN-1P upgraded to an

8 x 2 Mbit/s ADM.
Note 2: LAN interface available only for a TN-1P Headend and a TN-1P upgraded
to an 8 x 2 Mbit/s ADM.

Power supplies
External
The external power supply is wall mounted and is in a similar enclosure to the
multiplexer unit. Its output voltage is –24 V d.c. A rack mounted multiplexer
uses the rack power supply and does not require the external power supply
unit. For more information see ‘Power supply unit’ on page 4-1.
2
Internal power supply
Each multiplexer unit, has its own point-of-use power supply (PUPS) which
can operate with an input voltage in the range –20 V to –72 V d.c. The SEP in
the TN-1PH also has a PUPS that can operate with an input voltage in the range
–36 V to –72 V d.c. as follows:
• TN-1C and TN-1P (wall mount): a nominal –24 V d.c. from the external
power supply (although it can accept voltages in the range –20 V to
–72 V d.c.)
• TN-1C and TN-1P (rack mounted): a nominal –48 V d.c. from the rack
–72 V d.c.).
• TN-1P Basestation (rack mounted): a nominal –48 V d.c. from the rack
–72 V d.c.).
• TN-1P Headend: a nominal –48 V d.c. from the rack power supply
(although it can accept voltages in the range –36 V to –72 V d.c.).
CAUTION
Incorrect d.c. polarity on TN-1P Headend
Ensure that the correct polarity rack power supply is connected.
The PUPS is divided into two functional blocks. The two functional blocks are
electrically isolated, power is supplied through a transformer and feedback
through an opto-isolator:
• Primary power train — provides a.c. output to the secondary power train
and protection against electromagnetic interference (EMI) and excessive
start-up current. It also provides an indication of low input voltage from the
external power supply.
• Secondary power train — provides a clean d.c. output which is compared
to a reference, the error is fed back to the primary power train. It also
provides output overvoltage protection.

Timing source
Clock generator
The clock generator produces a timing source for the multiplexer from an
incoming STM-1 signal, a selected 2 Mbit/s tributary or an external source
(TN-1C and TN-1P ADM card upgrades only). The clock generator produces
the system clock for system operation and data transmission.
System clock
A voltage controlled crystal oscillator (VCXO) generates a 19.44 MHz
system clock. This internal clock provides PDH compliant tributary signals,
but when connected to an SDH network, external synchronization from the
aggregate or an external source is the preferred option. The system clock also
provides synchronization timing for the TN-1C tributary extension card.
Controller platform
The controller platform controls the operation of the whole multiplexer,
including all configuration, provisioning, real-time and communication
functions.
Processor
The processor is equipped with a watchdog function which ensures program
integrity.
Restart
Two types of restart are provided on the multiplexer:
• cold restart - a hardware reset is performed on system power-up and held
for 600 ms until power is stabilized. You can request a cold restart from the
user interface. A cold restart is traffic affecting.
• warm restart - if a software fault or processor overload occurs, the software
is reset. This does not affect the traffic. Warm restart can be initiated from
the user interface. A warm restart is also started during the software
upgrade process and the configuration upgrade process. For detailed
descriptions of these processes, see System and System Administration
Procedures, 323-1081-302.
0
Memory
The multiplexer has four different areas of memory:
• volatile memory for microprocessor data stack functions (dynamic RAM).
• application memory - non-volatile memory that holds the multiplexer
application software (two banks) of Flash - electrically erasable
programmable read only memory (EEPROM).
• foundation memory - non-volatile memory that holds the multiplexer
foundation software (stored in the same flash as the application memory).
• configuration memory - non-volatile memory (EEPROM) that holds the
programmable configuration data.

The multiplexer allows two versions of application software to be stored in

banks A and B of the non-volatile flash memory. Only one version of
multiplexer application software is selected at any given time. The user can
switch between the two versions of application software, until committing to
the most recently loaded version. The new data is then written into both
banks. Refer to ‘Equipment management’ on page 3-1 for further details. 2
Serial communications
The multiplexer has the following communication links:
• Software programmable serial channel on the embedded control channel
(ECC) regenerator section and multiplex section overhead, which operates
at either:
— 192 kbit/s and uses bytes D1 to D3 (regenerator section overhead)
— 576 kbit/s and uses bytes D4 to D12 (multiplex section overhead)
(see ‘Section overhead’ on page 10-11).
• RS-232 channel for CAT operation.
• one RS-232C interface (used by TN-1C Release 1 hardware and TN-1P to
support the asynchronous telemetry unit (ATU) feature)
• one point-to-multipoint RS-485 interface (used by TN-1C Release 3
hardware to support the ATU feature)
• One 10BaseT LAN channel for remote network element management
using a Element Controller (TN-1C, TN-PH and TN-1P ADM card
upgrades only).
STM-1 interface
The STM-1 interface can be divided into three functional blocks:
• electro-optical interface - provides the conversion between electrical and
optical signals.
• dual serial-to-parallel Interface (DSPI) - provides high speed conversion
from 155.52 MHz serial to 19.44 MHz, 8 bit parallel data and vice-versa.
The DSPI also provides a divide-by-eight clock, derived from the high
frequency serial input. The parallel to serial conversion is buffered to
compensate for differences between input clock and the derived clock.
• STM-1 processor - is an application specific integrated circuit (ASIC)
which can receive and transmit STM-1 frames conforming to the SDH
protocol. The receiver performs frame alignment and overhead
termination. The transmitter performs overhead generation only.
Timeslot interchanger
The timeslot interchanger (TSI) is an ASIC which performs the following
functions:
• Extracts the AU pointer which is used to locate the start of the VC-4
container.
• Extracts and processes the VC-4 path overhead bytes.
• Synchronizes the pointer of each TU to the local multiframe.

• Performs the TU reordering, if required. Dropped TUs are output to the

PDH Mapper circuits. Insert TUs are combined with the through path TUs.
• Generates the VC-4 path overhead bytes and sets the AU pointer value.
Multi-channel tributary block

The multi-channel tributary block carries out the interfacing and mapping of
tributary PDH signals. It contains the following two blocks:
• PDH mapper - incorporates the functions of low-order path (VC-3/VC-12)
path termination, generation, rate adaption, 34/45 Mbit/s and 2 Mbit/s
mapping. VC-3 (34/45 Mbit/s) applicable to TN-1C only.
• PDH line interface - comprises a G.703 transmitter/receiver, line interface,
and a pseudo random binary sequence (PRBS) generator/detector.
Extension card interface (TN-1C only)

Note: The tributary extension card is not applicable to single-slot TN-1C
variants.
The interface to the tributary extension card allows the drop/insert TU data to
be processed by the appropriate tributary extension card. The user must equip
the extension card by specifying the full card type. The card type consists of
two parts:
• Major
This specifies the basic service provided by the card, for example an
8x2 Mbit/s tributary extension.
• Minor
This specifies the specialist characteristics of the card, for example a card
that supports frame structured 2 Mbit/s signals.
If the actual card and the user specified card type are different, functionality is
lost and alarms are raised. If the Major part is incorrect, an NE-Wrong_Card
alarm is raised and no functionality is provided. If the minor part is incorrect,
an NE-Minor_Card_Mismatch alarm is raised. Configuration changes are
available only for the card type that is equipped. Functionality is limited to a
subset of the actual card type and the equipped card type.
Traffic processing
TN-1C options
The following options are available for the TN-1C (see Figure 2-3):
• up to eight 2 Mbit/s inputs/outputs using the ADM card
• up to eight 2 Mbit/s inputs/outputs using the ADM card and one
34/45 Mbit/s inputs/output using a 34/45 Mbit/s tributary extension card
• up to eight 2 Mbit/s inputs/outputs using the ADM card and up to two
34/45 Mbit/s inputs/outputs using a 2 x 34/45 Mbit/s tributary extension
card
• up to eight 2 Mbit/s inputs/outputs using the ADM card and eight 2 Mbit/s
inputs/outputs using a 8 x 2 Mbit/s tributary extension card

• up to eight 2 Mbit/s inputs/outputs using the ADM card and 24 x 2 Mbit/s

inputs/outputs using a 24 x 2 Mbit/s tributary extension card
• 1+1 protected STM-1 interfaces
Note: For details of the optional router card, refer to the OPTera Packet
2
TN-1P options
The following options are available for the TN-1P (see Figure 2-4):
• up to four 2 Mbit/s inputs and outputs using the multiplexer card
• unprotected or 1+1 protected STM-1 interfaces.
TN-1P Basestation options

The following options are available for the TN-1P Basestation (see
Figure 2-4):
• up to four 2 Mbit/s inputs and outputs using the multiplexer card, with
unprotected or 1+1 protected STM-1 interfaces
• up to eight 2 Mbit/s inputs and outputs using the multiplexer card, with 1+1
protected STM-1 interfaces

Figure 2-3
TN-1C traffic processing
STM-1o STM-1o
Electro- Dual Serial Dual Serial Electro-
Timeslot Timeslot
optical to parallel STM-1 STM-1 to parallel optical
Inter- Inter-
interface interface Processor Processor interface interface
changer changer
STM-1 interface STM-1 interface

Electro Optical Module Electro Optical Module
Option 1 Option 2
Option 3
PDH mapper PDH mapper PDH mapper
Tributary block
Tributary block
Tributary block
2 Mbit/s tributaries 2 Mbit/s tributaries 2 Mbit/s tributaries

and line interface and line interface and line interface
2 Mbit/s electrical ports 2 Mbit/s electrical ports 2 Mbit/s electrical ports

1 x 34/45 Mbit/s or 2 x 34/45 Mbit/s
PDH mapper PDH mapper

8 x 2 Mbit/s or 24 x 2 Mbit/s
Tributary Extension card
Tributary extension card
34/45 Mbit/s 2 Mbit/s tributaries

tributary and line interface
and line interface
34/45 Mbit/s electrical ports 2 Mbit/s electrical ports

Figure 2-4
TN-1P traffic processing
STM-1o STM-1o
Electro-
optical
interface
Dual Serial
to parallel STM-1
Processor
Timeslot
Inter-
Timeslot
Inter-
STM-1
Processor
Dual Serial
to parallel
Electro-
optical
2
interface changer changer interface interface
STM-1 interface STM-1 interface

Electro Optical Module Electro Optical Module
PDH mapper
Tributary block
2 Mbit/s tributaries
and line interface
Up to four 2 Mbit/s electrical ports

(or up to eight in the TN-1P
Basestation with the ADM card
fitted)
Note: This figure shows a protected variant. The unprotected

variant is similar but has only one electro-optical module.
Transmit traffic path (2 Mbit/s to STM-1)

The tributary interface receives incoming signals in HDB3 format and
converts these signals to four 2 Mbit/s binary data streams, which are passed
to the PDH mapper. The PDH mapper then extracts a clock signal and
synchronizes the signals and maps the signals asynchronously to VC-12
tributary format. The TU-12 overhead and pointers are generated and the
signal is passed to the TSI.
Data arrives at the TSI ASIC in 8 kHz partially filled frames. The 19.44 MHz
system clock is used to clock incoming data onto the gate array and the
outgoing data to the output. Multiframe synchronization is used to indicate
the first byte of the frame. The AU pointer is added and the data, in 8 kHz
STM-1 frames with only the AU pointer in the overhead, is passed to the
STM-1 processor ASIC.
The STM-1 processor ASIC multiplexes section overhead bytes onto the
payload data and scrambles the data byte-by-byte. The data is then passed to
the DSPI where it is re-organized into a 155.52 Mbit/s serial stream aligned to
an internal high frequency clock (19.94 MHz). It is then passed to the
electro-optical interface where it is converted to a 155.52 Mbit/s optical signal
for transmission.

The processor supports loopback of the receive signal to the transmit signal
and vice versa.
0
Receive traffic path (STM-1 to 2 Mbit/s)
The electro-optical module receives the STM-1 (155.52 Mbit/s) optical signal
and converts it to a serial electrical signal. The DSPI ASIC then converts the
electrical signal into an 8-bit 19.44 MHz parallel signal. The 19.44 MHz
clock signal is extracted and the incoming STM-1 frames are aligned and
descrambled. The overhead bytes are then terminated leaving the data as
STM-1 frames with only AU pointers in the overhead. Differences in received
line timing and local equipment timing are accommodated by the pointer
processing unit. Output from the STM-1 processor is then passed to the TSI
ASIC, aligned to the system clock and in multiframe synchronization.
The STM-1 processor provides a free running 8 kHz clock from the received
optical byte clock, which is used to synchronize the system clock to the
incoming signal.
The data is received from the STM-1 ASIC in 8 kHz STM-1 frames with only
AU pointer bytes in the overhead. The AU-4 pointer information is extracted
and used to locate the start of the VC-4. The VC-4 path overhead data is
terminated and processed and the TUs are realigned to the local start of the
VC-4 payload and new TU pointers are generated.
The TUs are reordered and sent to the PDH mapper in 8 kHz frames at
19.44 Mbyte/s. Here, overhead termination of the four TU-12s takes place,
the pointers are extracted to locate the VC-12s which are then mapped
asynchronously to 2 Mbit/s channels and converted from binary to HDB3
format in the 2 Mbit/s line interface.
Transmit traffic path (Tributary extension card, 34/45 Mbit/s to STM-1,

TN-1C only)
Apart from the traffic being received in HDB3/B3ZS format respectively at
the tributaries and the PDH mapping of the signals asynchronously to VC-3
tributary format, data is processed in exactly the same way as in the 2 Mbit/s
transmit traffic path.
Receive traffic path (Tributary extension card, STM-1 to 34/45 Mbit/s,

TN-1C only)
The operation of this receive traffic path of the tributary extension card is
identical to that of the receive traffic path (STM-1 to 2 Mbit/s). However, in
this particular case when the pointers are being extracted, it is the VC-3s
which are mapped asynchronously to 34/45 Mbit/s channels and converted
from binary to HDB3/B3ZS format respectively in the 34/45 Mbit/s line
interface.
Transmit/Receive traffic path (Tributary extension card, 2 Mbit/s, TN-1C

only)
The operation of the transmit/receive traffic path circuitry, on the tributary
extension card, is identical to the 2 Mbit/s circuitry within the tributary block.

Path protection
Path protection switching (PPS) is not available on the TN-1P, TN-1PH or
TH-1P Basestation unprotected variants.
The TN-1C and the protected variants of the TN-1P, which have two STM-1
interfaces, support PPS. PPS provides protection over the whole VC-12 path
2
regardless of the SDH network in use. For the 34/45 Mbit/s variant of the
TN-1C, PPS is provided also over the whole VC-3 path.
The multiplexer monitors the validity of the incoming TUs from the two
STM-1 links, and uses a valid TU.
In the case of a failure in a TU-12 path, it is considered unavailable for use. If

the selected path fails and the other path is available, then the data is switched
to be received from the available path (i.e. it is now the selected path).
Holdoff period
Switching is performed immediately by default although the user may set a
holdoff period, which is a delay between detection of a fault and subsequent
switching. No holdoff period is implemented if the detected defect is of
RS/MS/AU/HP level. The holdoff time is selectable in the multiplexer
between 0.1 and 20 seconds, and the holdoff operation can be
enabled/disabled for each tributary.
Oscillation guard time

Oscillation guard time is the length of time that PPS is disabled after an
automatic protection switch. It prevents reversion to the original failed path
before the system has stabilised and subsequent oscillation between the two
paths. The oscillation guard time is between 1 and 30 seconds and is specified
in seconds.
Reversion
Path protection switching is non-revertive; after a switch and subsequent fault
clearance, the operation is not switched back to the original user selected
path. Switching only occurs when the selected path fails.
Priority control
For path protected connections, a user interface command implicitly
determines the source path and the alternative source path. Subsequent PPS
changes the source path, but the following conditions apply:
• the configuration report shows the configured order and does not change
as a result of a PPS.
• Software upgrades, warm restarts and configuration switch do not cause a
PPS if the current source path is not the originally configured source path.

PPS criteria
Table 2-1 shows the criteria that will cause a path protection switch.
Table 2-1
PPS switching criteria
Alarm Explanation
PPS criteria causing a path protection switch on all TUs
RS-LOS STM-1 Loss of Incoming Signal
RS-LOF STM-1 Loss of Frame alignment
MS-AIS Multiplexer Section Alarm Indication Signal
MS-EXC Multiplexer Section Excessive Bit Error Signal
AU-AIS Administrative Unit Alarm Indication Signal
INT-AU-AIS Internal Administrative Unit Alarm Indication Signal
INT-AU-LOP Internal Administrative Unit Loss Of Pointer
HP-PLM High order Path Signal Label Mismatch (see Note 1)
HP-LOM High order Path Loss Of Multiframe
HP-TIM High order Path Trace Identifier Mismatch (see Note 1)
PPS criteria causing a path protection switch on individual TUs
TU-AIS Tributary Unit Alarm Indication Signal
TU-LOP Tributary Unit Loss Of Pointer
LP-EXC Low order Path Excessive BER (see Note 2)
Note 1: The Consequent Action configuration facility allows the user to disable
switching on receipt of HP-PLM and HP-TIM alarms.
Note 2: The Consequent Action configuration facility allows the user to disable
switching (on a per tributary port basis) on receipt of an LP-EXC alarm.
Automatic laser shutdown
WARNING
Laser radiation
Do not stare into a laser beam. Do not view fibres directly with
optical instruments unless you are certain that the fibres are not
active.
The TN-1C and TN-1P optical aggregate units contain an automatic laser
shutdown (ALS) circuit which shuts down the laser if an Optical Power High
(OS-Optical_Power_High) alarm or an STM Loss of Signal (RS-LOS) alarm

occurs. This prevents excessive optical power being radiated from a broken
fibre or an unterminated optical connector.
The ALS operation is automatically disabled during the first 90s from a cold
start. Using a UI command during the first 90s from a cold start, maintenance
personnel may suspend the ALS operation permanently. This enables 2
maintenance tasks to be carried out. After the maintenance tasks are carried
out, the ALS operation may be returned to normal by a further command from
the UI.
During fault-free operation, both multiplexers on both sides of the link have
their optical unit lasers ‘on’. The laser shutdown mechanism operates
independently for each STM-1 link and may activate for the following reasons:
• If either or both multiplexers detect an RS-LOS indication present for at
least 550 ± 50 ms, its laser is shutdown. If the RS-LOS alarm clears (for at
least 100 ± 20 ms), the laser is switched back on immediately.
• If either or both multiplexers detect an OS-Optical_Power_High alarm its
laser is shutdown immediately. The laser can not be restarted until the unit
is reset (e.g. removed and replaced in the subrack).
In certain networks it can be necessary for an engineer to be able to force the

laser on at any time, to provide more convenient testing.
Only a system engineer has authority to force the laser on at any time. The
following safety features are associated with the force laser on feature:
• The laser force on feature can only be used from a local login, by a
craftsperson working at the TN-1C. The feature is not available from the
element controller.
• An OS-Optical_Power_High alarm does not affect the use of the
allow/disallow force feature, but the alarm does shut down the laser.
Loopbacks
A loopback facility on the multiplexer enables the user to perform test
procedures for fault finding. The following loopbacks may be initiated by the
user:
STM-1 local loopback

A local (‘near-end’ or ‘loop to mux’) loopback can be performed on a
selected STM-1 link, i.e. the outgoing (towards the optics) STM-1 data is
routed back to the STM-1 receiver on the same link, as well as being
transmitted towards the line. While an STM-1 local loopback is in operation,
an RS-Loopback_On alarm is raised. This loopback should be activated with
caution as it causes traffic loss.

An STM-1 local loopback is not permitted in an unprotected system. It is also

not permitted on both aggregates in a protected system. Refer to Figure 2-5.
CAUTION
ECC communication loss
An STM-1 local loopback must not be activated remotely as it
leads to ECC communication loss and a site visit is required to
remove the loopback condition.
CAUTION
Loss of traffic
An STM-1 local loopback causes traffic loss. Ensure that the
aggregate to be looped back is not carrying traffic.
Note: When a local STM loopback is raised, the multiplexer detects a

temporary loss of signal during the switch and raises an RS-LOS alarm
(which clears after the switch). This causes PPS on all tributaries fed from
this aggregate.
Figure 2-5
STM-1 local loopback
STM-1
Electro-
Section STM-1
Optical
Termination
Module x
STM-1 remote loopback

A remote (‘far-end’ or ‘loop to line’) loopback can be performed on a selected
STM-1 link, i.e. the incoming (from the optics) STM-1 data is routed back to
the optical connections on the same link, as well as being transmitted towards
the line. While an STM-1 remote loopback is in operation, an
RS-Loopback_On alarm is raised. Refer to Figure 2-6.
CAUTION
ECC communication loss
An STM-1 remote loopback must not be activated remotely as
it leads to ECC communication loss and a site visit will be
required to remove the loopback condition.
CAUTION
Loss of traffic
An STM-1 remote loopback causes traffic loss, the user should
ensure that the aggregate to be looped back is not carrying
traffic.

Note: When a remote STM loopback is raised, the remote multiplexer may
detect a temporary loss of signal (at the time of the switch) and raise an
RS-LOS alarm (which will be cleared after the switch) causing a PPS on
tributaries fed from that link.
Figure 2-6 2
STM-1 remote loopback
STM-1 x Electro-
Optical
Section Module STM-1
Termination
Tributary local loopback

A local (‘near-end’ or ‘loop to mux’) loopback can be performed on the
tributary level on the selected link, i.e. the outgoing (towards the metallic
wires) PDH data is routed back to the PDH receiver on the same link, as well
as being transmitted towards the line (refer to Figure 2-7). This loopback is
implemented in the tributary line driver in TN-1C Release 3/5/5.1 and TN-1P
hardware and in the tributary mapper in TN-1C Release 1 hardware. While a
tributary local loopback is in operation, a PPI-Loopback_On alarm is raised.
Figure 2-7
Tributary local loopback
Tributary Tributary Tributary

Interface Electrical Mapper
Line
x Driver
Note: The loopback can only be applied when the tributary port is in the
‘traffic on’, ‘traffic auto’ or ‘traffic standby’ mode.
Tributary remote loopback

A remote (‘far-end’ or ‘loop to line’) loopback can be performed on the
tributary level on the selected link, i.e. incoming tributary data (from the
metallic wires) is routed back to the tributary lines on the same link, as well as
being transmitted towards the PDH receiver in the mapper. This loopback is
implemented in the tributary electrical line driver in TN-1C hardware from
Release 3, in TN-1P hardware, and in the tributary mapper in TN-1C
hardware from Release 1. While a tributary remote loopback is in operation, a
PPI-Loopback_On alarm is raised.

Figure 2-8
Tributary remote loopback
x
Tributary Tributary Tributary
Interface Electrical Mapper
Line Driver
Note: The loopback can only be applied when the tributary port is in the
‘traffic on’, ‘traffic auto’ or ‘traffic standby’ mode.
Simultaneous loopbacks
STM-1 loopbacks and tributary loopbacks can be performed independently.
Although STM-1 loopbacks may be performed on both aggregates
simultaneously, this must not be done remotely as all ECC communications
are disabled and a site visit will be required to remove the loopback condition.
On a specific tributary or STM-1 aggregate, local and remote loopbacks
cannot be performed simultaneously.
Single fibre working

The TN-1C or TN-1P multiplexer is capable of operating in a single fibre
mode where a single optical fibre is used to carry bi-directional optical signals
between adjacent multiplexers. The conversion between two fibre working
and single fibre working is performed externally to the multiplexer by a 2-1
optical coupler (see Figure 2-9).
Figure 2-9
Single fibre operation
TN-1C TN-1C
Single
Tx Optical Rx
Converter
Converter
Fibre
2-1
2-1
Rx Tx
In the event of a break in the single fibre, there is a possibility of the

transmitted traffic being echoed by the 2-1 optical converter to the receive
port on the same multiplexer. This signal must be recognized as faulty and
AIS transmitted downstream. To recognize the echoed signal, the HO path
trace facility should be used with the transmit and receive path trace settings
set to different values and the consequent actions enabled.

By using the path trace facility with the consequent actions enabled, an
HP-TIM alarm will be raised and AIS transmitted downstream if a fibre break
occurs.
Note: If the consequent action of HP-TIM alarm is enabled, the

transmitted signal will have the HP-RDI set. This will be received in the 2
echoed signal causing a HP-RDI alarm to be raised on the same
multiplexer that generated it.
In the event of a broken fibre where the echo is sufficient to constitute a valid
signal, the multiplexer does not behave in the normal manner to a Loss of
Signal event. Instead a transient STM-LOF alarm will be raised while the
multiplexer is achieving frame alignment to the echoed signal.
If the single fibre is used as a synchronization reference, a timing loop may

develop. To avoid this, the HP-TIM alarm can be configured to invalidate the
aggregate as a synchronization source. This is recommended in any
multiplexer application except for a point-to-point application where, under
certain circumstances, a timing loop may be deemed acceptable.
The RS-LOS alarm is used as a trigger for ALS. In the event of a broken fibre,
if the echo is sufficient to constitute a valid signal, the RS-LOS will not be
raised, therefore ALS is not supported when operating in a single fibre mode.
Built-in test facility

The TN-1C or TN-1P multiplexer provides three types of tests: two automatic
non-service affecting tests, and a manual test which is initiated by the user,
via the user interface.
Note: A manual test affects traffic for a short period of time.
Non-service affecting tests

Power-up test
When the multiplexer is powered up, or after a ‘cold start’, the multiplexer
performs a hardware test before any traffic flow is established. This examines
the processor, memories, application software and other hardware
components that are not available for test when the multiplexer is operating. If
the test fails, the red ‘FAIL’ LED on the multiplexer connector panel remains
lit.
After the tests are completed, the following message is sent to the UI, if no user
is logged in at that time, the message is lost.
NORTEL TN1C, SW RELEASE = C515, BOOT = C515
*********************************************
RAM test passed
Clock 1 test passed
Clock 2 test passed
Clock 3 test passed
SCC1 test passed

SCC2 test passed

SCC3 test passed
Only the heading is sent after a warm restart.
Normal operating tests

During normal operation, the multiplexer performs periodic tests to provide
validation of the hardware operation. Tests are carried out on RAM, ASICs,
software FLASH memories, and configuration non-volatile storage. Upon
detection of a fault, a consequent action may be activated and an alarm raised.
Service affecting tests

The multiplexer includes a built-in test pattern generator and detector, operated
through a user interface session. The test pattern is:
• PRBS15 for the 2 Mbit/s tributaries (TN-1C and TN-1P) as defined in
ITU-T Recommendations 0.151 sec, 2.1
• PRBS23 for 34/45 Mbit/s tributary signals (TN-1C only) as defined in
ITU-T Recommendations 0.151 sec, 2.2.
The test pattern may be injected towards the optical line on a specific path or
towards the tributary line (one at a time per multiplexer). The tributaries must
be in the ‘traffic on’, ‘traffic auto’ or ‘traffic standby’ state to perform this
test. The test pattern overrides all the bits of the original signals (e.g. for
2 Mbit/s signal, all 256 bits per frame carry the PRBS15 bits).
A test pattern generator may be connected to the signal from the VC data or
from the tributary line. The detector synchronizes to the PRBS test data, and
once synchronized it starts counting the errors between the incoming
bit-stream and the expected bit-stream. Errors are periodically read, and
accumulated to derive the test results. The detector will detect bit error ratio
up to 10-3, with an overflow indication in case of a higher BER.
Once synchronization is lost, a flag is raised and the receiver will attempt to
re-synchronize.
The PRBS generator/detector is located between the PDH mapper and the
PDH line drivers as shown in Figure 2-10. The PRBS generator/detector is
shown for a single tributary, the PRBS generator/detector is common for all
tributaries and can be switched to any tributary. Throughout a PRBS test, a
PPI-Continuity_Test alarm is raised.

Figure 2-10
PRBS location
PRBS
Generator 2
towards
Trib optical
PDH line
electrical PDH
line driver mapper
PRBS
Detector
Note 1: PRBS should not be injected towards the optical side when the
same tributary is in ‘remote’ loopback. The test will fail due to a lack of
clock source in that scenario and the test does not provide any value.
Note 2: For 34/45 Mbit/s tributaries (TN-1C only), PRBS to an optical line
does not operate if a PPI-LOS alarm is detected on the tributary.
Note 3: PRBS can not be applied when the tributary port is in the
‘traffic off’ mode.
Note 4: PRBS cannot be applied when the tributary is in the
synchronisation source hierarchy.
0
The test results are reported to the UI as follows:
• Test time - length of the test in the format hh:mm:ss
(hours:minutes:seconds)
• Synchronization status - a sync/no sync attribute which specifies whether
the detector was continuously synchronized to the incoming test pattern
since the last report
• Error count - number of errors counted
• BER - The bit-error ratio is derived by the error count divided by the
product of Test Time (in seconds) and N. N equals 2048000 for 2 Mbit/s
tributary testing, 34368000 for 34 Mbit/s tributary testing and 44736000
for 45 Mbit/s tributary testing.
0
If the error count is inaccurate due to synchronization loss or error counter
overflow in one or more intervals, then the error count for those intervals will
be set to the hardware counter maximum count. Also the error count and BER
parameters will be marked as ‘invalid’ for the whole test period. This is
denoted by an asterisk ‘*’ after the report.
The user activates the PRBS by specifying a tributary to be tested and the
report frequency. The report frequency has a default of 30 seconds if the user
does not supply an alternative. Reports are displayed by the user interface.

Subrack end processor and craft access panel (TN-1PH only)

One subrack end processor (SEP) is fitted to each TN-1P Headend subrack in
slot 13, to the right of the MPP units. It is not required in the TN-1C or TN-1P
(wall/rack-mount unit). Its purpose is to consolidate the support functions of
the individual TN-1P MPPs into one common facility. 2
The SEP provides the following four functions:
• IEE802.3 CSMA/CD hub for 12 ports
• Alarm interface circuits
• CAT interface circuit
• on-card PUPS
The craft access panel (CAP) is a small panel fixed to the right hand side of the
TN-1PH subrack. It provides the front panel indications and controls required
by the SEP, as follows:
• ‘Fail’ alarm LED (indicates the subrack alarm status)
• Active ‘RCU-ACK’ LED (indicates the subrack alarm status)
• Alarm Acknowledge (REC ATT) push-button
• MPP/CAT selection display
• CAT selector push-button
0
Figure 2-11 shows a simplified block diagram of the SEP and CAP.

Figure 2-11
SEP and CAP block diagram
2
10BaseT 1 managed port
MAU AIU
(to MPP #1)
10BaseT
Selector Encoder/decoder
& regenerator
10BaseT Control
(to MPP #12) MAU
LAN Interface
4 rack alarms
To/from TN-1P MPPs
4 EXT alarm
outputs
Control REC ATT
Debounce
button
1 EXT alarm
input
LED
(REC ATT)
displays
Alarm handler
display
SELECT
Selector
CARD
Debounce Select button
12
Craft Access Panel

RS-232
to MPPs RS-232
repeater To CAT
RS-232 selector
+5 V
PUPS –48 V
SEP

LAN Interface
The medium attachment units (MAU) receives/transmits data to the individual
MPPs and performs collision detection.
The attachment unit interface (AUI) receives/transmits data to the LAN

manager workstation and sends/receives control signals to/from the hub.
The selector switches the active port to the encoder/decoder and regenerator
and then routes it to the remaining ports. It also performs port partitioning
when excessive numbers of collisions occur.
The encoder/decoder and regenerator implements the Manchester signalling

format required by IEEE802.3. It also performs signal retiming and amplitude
restoration. When a collision has been detected the regenerator notifies all
ports by sending a jam sequence.
Alarm handler
This consolidates the alarms from each MPP into a single standard rack alarm
interface.
The alarm outputs from the MPPs are tied together on the TN-1PH Headend
backplane, and then passed on to the alarm handler on the SEP. The rack alarm
outputs from the SEP are:
• ‘Prompt/Deferred’ alarm to rack
• ‘In-Station’ alarm to rack
• ‘Receive Attention’ input
• ‘Fault Clear’ input
The Alarm handler also has the following connections to the CAP:
• Fail alarm LED
• Active ‘REC-ACK’ LED
• Alarm Acknowledge (REC ATT) push-button
RS-232 selector
This block permits the selection of a local craft access terminal (CAT) to any
one of the MPPs. The CAT is plugged into the CAT port on the TN-1PH
connection panel. Selection is achieved by a single push-button on the CAP,
pressing the button connects the next MPP slot in the subrack to the CAT. The
MPP that is currently selected is identified on the two digit display on the
CAP.
end of chapter

3-1
Equipment management 3-
3
The equipment management functions of the TN-1C, TN-1P, TN-1PH and
TN-1P Basestation multiplexer are performed by the synchronous equipment
management function (SEMF) of the multiplexer embedded software.
Alarms
Alarm monitoring
Alarm monitoring is carried out in order to indicate the multiplexer status at
any given time. Alarm reports are made to:
• all open sessions
• external alarm outputs (according to alarm association with the alarm
outputs)
• the Element Controller EC-1 station (a brief report)
0
In addition, the user can always request a list of the current active alarms.
Details of the alarm indications, alarm sequences, and individual alarms are
given in Alarm Clearing Procedures, 323-1081-543.
Alarm handling
Each alarm raised is monitored for a specific period after they are set/cleared
in order to correlate any low level defect with the higher level defect that
might have caused them. The time periods for which these defects are set
vary, this is to avoid ‘alarm flooding’ before making a report. For reporting
purposes, the alarms are further processed for correlation, detection and
masking. All reported alarms are time stamped and logged.
Alarm masking
The multiplexer software performs alarm masking, so that only the highest
level alarm on any one traffic path is reported as set, while all other alarms are
considered cleared. However, when the higher priority alarm is cleared, then
the alarm with the next highest priority of the remaining alarms is reported.

3-2 Equipment management
External alarms
TN-1C and TN-1P
The multiplexer has twelve external alarms: eight input and four output.
The external alarms provide a means of collecting various indications from

external devices (via input alarms; fire detector, door open etc.) and reports
them to the management station. The output alarms can be set to activate
external devices (i.e. fire extinguisher, traffic alarm etc.).
Each alarm name associated with the external alarm input(s) and output(s)
can be set, by the user, to give a meaningful name i.e. ‘Fire’, etc.
An input alarm is set if it persists for longer than its predetermined time
period of one second. Output alarms may be associated with any (one or
more) alarm types. In this case, when at least one of the associated alarms is
set, the appropriate external alarm will be set. An external alarm is cleared if
none of its associated alarms is set.
The user may configure an external alarm into a certain state (Forced
set/cleared). If forced into a state, the external alarm output will remain in this
state regardless of any change in the associated alarms. Only after the user
disables the forced state, will the associated alarms be able to affect the
external alarm output state.
TN-1P Headend
In the TN-1P Headend the external alarms are configured as follows:
• Each main point-to-point (MPP) uses four external alarm outputs and one
external alarm input.
— The outputs are consolidated by the subrack end processor (SEP) into
a standard rack alarm interface.
— The input is used to accept a pressing of the receive attention
(REC-ACK) button.
• The remaining alarms are reserved for system use and are not available to
the user.
0
Each MPP also maintains its own state machine for the rack alarm signals
relating to its own status. The rack alarms indicate the alarm status of the
local MPPs and do not indicate the status of alarms in any remote TN-1P.
The alarms are graded with three levels of severity: Prompt, Deferred, and
In-Station. When passed on to the rack alarm bus, the Prompt and Deferred
alarms from each MPP are combined into a single alarm with the Prompt
level of severity.
Rack alarms
When used in a rack, the TN-1C or standard TN-1P can be used in
conjunction with a rack alarms adaptor, this allows the four output alarms to
be consolidated into the rack alarm system.

One input alarm (EAIn_8) is used to read the alarm receive attention button.
In this situation, the external alarms feature can not be used.
The rack alarms adapter has two LEDs, a red LED labelled ‘Alarm’ and a
green LED labelled ‘Receive Att’. When an unacknowledged alarm (of any
severity) is present, the red LED is illuminated. If the alarm receive attention
button is pressed, the alarm is acknowledged, the red LED is extinguished and
the green LED is illuminated. If an acknowledged alarm is cleared, the red
LED is illuminated again; at this stage both LEDs are illuminated. This means
that an acknowledged alarm has been cleared but the clear has not yet been
acknowledged. Once a cleared alarm has been acknowledged, both LEDs are
3
extinguished.
Similar LEDs are situated on the rack alarm unit, although there are usually
four, one confirming the power supply, a receive attention LED, one that is
illuminated to show the presence of a Prompt or Deferred alarm and another
that is illuminated to show the presence of an In station alarm or an
acknowledged alarm clearing.
TN-1P Basestation variant has no rack alarm adaptor.
Management
ATU channel
The TN-1C and TN-1P multiplexers provide an ATU channel. This is for the
use of external equipment that communicates with its management system via
the TN-1C and TN-1P. Asynchronous data is packaged and transmitted over
the ECC.
The auxiliary channel interface are as follows:

• TN-1C Release 1 hardware: RS-232 interface.
• TN-1C Release 3 onwards hardware: RS-485 point-to-multipoint
interface.
• TN-1P auxiliary channel: RS-232 interface
The multiplexer is defined as a data termination equipment (DTE) for the

TN-1C (Release 3 onwards) hardware and a data communications equipment
(DCE) for TN-1C Release 1 hardware and the TN-1P.
Clear channel telemetry

The clear channel telemetry feature allows equipment outside of the network
to pass asynchronous ASCII messages across the network.
The clear channel telemetry functionality collects the incoming characters,

packetizes these characters and stores them in a buffer having a capacity of up
to 440 bytes.
The clear channel telemetry functions in a similar manner to the ATU message
handling, but with the following differences:
• in clear channel telemetry, the user programs the destination,

• all ASCII characters are accepted (a start and stop sequence is not
expected)
• as there are no pre-defined control characters, the transfer of a frame in an
upstream direction (port to network) has only the following criteria:
— buffer full
— more than 0.25 seconds between characters
As the clear channel telemetry data is sent over the network in the same way
as the ATU data, the transferred message is identified using a transport
service access point ID (TSAP_ID) header.
LAN channel
The TN-1C, TN-1P (ADM upgrade only) and TN-1PH have a standard
10BaseT LAN interface which allows communication with the EC-1 or for
connection to other appropriate equipment. When a TN-1C, TN-1P (ADM
upgrade only) or TN-1PH network element is selected from the EC-1, the
resident application software within that network element is accessed via a
user interface window in the EC-1 screen.
Real time clock

The multiplexer contains a real time clock with an accuracy of ±5 seconds per
day, this is primarily used for time stamping alarm and performance statistics.
The user can view and update the date/time at any time during a Browser
session. When the multiplexer is powered up or after a warm or cold restart,
the clock aligns to a default date and time (January 1st 1995, 00:00).
The EC-1 updates the real time clock on the TN-1C and TN-1P upon EC-1
session setup, and daily thereafter.
RSOH/MSOH DCC
The data communications channel (DCC) provides a communications path to
manage remote NEs. The multiplexer software supports the following:
• regenerator section overhead (RSOH) DCC (bits D1 to D3) at a rate of
192 kbit/s
• multiplexer section overhead (MSOH) DCC (bits D4 to D12) at a rate of
576 kbit/s.
The following limitations are applicable:

• Each STM-1 aggregate can operate on either RS DCC or MS DCC, but not
both.
• There is no automatic selection of either RSOH or MSOH. The channel
must be explicitly configured.
• A change of state requires a warm restart.
• For TN-1C, the add/drop multiplexer (ADM) hardware does not support
DCC passthrough for other vendors’ management protocols.

More information about RSOH and MSOH is provided in ‘Section overhead’

in Appendix A: Synchronous digital hierarchy.
Network addresses
Each multiplexer is identified by a unique address to allow communications
between network elements using the ECC, and for network element
identification by the EC-1.
The network address of the TN-1P and TN-1C is held on board. For the
TN-1P the network address is held on the multiplexer card. For the TN-1C the
network address is held on the ADM card.
3
The multiplexer supports the configuration of up to three manual area
addresses in order to implement IS-IS (intermediate system to intermediate
system) routing. One manual area address must be configured in the
multiplexer at all times. The multiplexer also holds a ‘partner NE’ address,
this allows users of the Command Line User Interface to rapidly access a user
selected partner NE.
CAUTION
Changing area addresses
Before changing the area addresses, ensure that you are aware
of the consequences to the communications within your
network. Changing an area address can cause other NEs to lose
communications with the EC-1. Any changes must be carefully
planned on a network wide basis.
Communication limitations
The Release 5/5.1 TN-1C, TN-1P, and TN-1PH NEs act as IS-IS Level-1
routers. In a data communications network (DCN), a Level-1 address area
may contain a total of up to 250 elements, but no more than 150 IS-IS
network elements. In their maximum configuration (12 TN-1PH cards and 24
TN-1P remote units), the TN-1P/TN-1PH units appear as 36 individual IS-IS
routers. This must be considered when provisioning a network with
Release 5/5.1 TN-1P/TN-1PH NEs.
Note: Release 2 TN-1P NEs behaved as end systems.
Inventory information
Inventory information is held in on-board IDPROMs. The following data can
be accessed with User Interface commands:
• network address
• PEC
• serial number
• card type
• extension card information (TN-1C): PEC, card type, serial number
• date of manufacture

• checksums for main and connector cards
Software
Application software
One copy of the multiplexer application software is held in two ‘flash’
memory banks. The versions held in each bank should be the same at all times
except during software upgrades. As only one flash memory copy can be
selected by the multiplexer boot software at any given time, the software of
the flash bank not selected can be upgraded while the other copy is running.
The multiplexer contains an automatic reversion facility, i.e. if the selected

application software fails to start up successfully, an automatic reversion to
the older software version is carried out. Alternatively, the user may request a
return to the older software version after the first switch is made (refer to
configuration data below). In the unlikely event that both flash banks fail, the
multiplexer unit should be replaced and returned to Nortel Networks for
reprogramming. Figure 3-1 shows the overview of the software upgrade
procedure.
Configuration data
The multiplexer has a set of configurable parameters that are required to
accommodate various user preferences. The multiplexer incorporates two
configuration databases, each associated with one software flash bank, and
stored in non-volatile storage (NVS).
In normal operation, the two configuration data bases contain the same
information, one is the operational bank and the other is the backup bank.
However, when the application software is being upgraded, each
configuration data base becomes associated with a flash application software
bank. If the user changes the configuration using new software, and performs
a backout, or commits to the new software after changing the configuration
using the old software version, the recent configuration changes are lost.
The user may backup the current configuration data base settings into a file in
the CAT or in the EC-1, and restore the settings if they are required (if they
have been overwritten or if the multiplexer fails and is replaced by a new one).
If the user restores old configuration data from the CAT or EC-1, a copy of the
data is stored in the unused configuration bank in the multiplexer. If the
restored data is satisfactory, the user may commit to it and the multiplexer
puts it into service. The user may also backout to the old configuration until
the decision to commit is made to the new configuration, which means that it
is copied to the two banks.
Note: A software upgrade can only start when the configuration status is
stable, i.e. both banks contain the same data.

Figure 3-1
Software upgrade overview
Start Both software banks contain the

original software.
New software
available 3
Download to Active Bank contains the original
TN-1C/TN-1P software and Inactive Bank now
Inactive Bank contains the new software.
Switch to new
software While the new software is being
tested, the original software can
remain in Active Bank. The user may
Test new switch between the different software
software in each bank.
Yes
Software
OK
No During normal operation, it is
important that both banks contain the
same software version. If the
Switch to original
software in each bank is different,
software
this can interfere with the operation
of configuration functions.
Commit to new If the new software is satisfactory,

Backout the user may decide to commit to it.
software
If the new software proves
unsatisfactory, then the user must
backout, reverting to the original
Old software in New software software. In either case, after the
both banks in both banks software has been tested, the
version in each bank should be the
same.
Finish
end of chapter

4-1
Power supply unit 4-

Note: The power supply unit is not used with the TN-1P Basestation or
TN-1PH Headend.
The power supply unit (PSU) for the TN-1C and TN-1P multiplexer is a
dedicated external power supply unit, which is used in wall-mounted
4
applications, to supply a nominal –24 V d.c. to the multiplexer. Matching
enclosures are used to house the PSU and the multiplexer in this
wall-mounted application. The rack mounted multiplexer is powered from the
rack power supply.
The multiplexer PSU is powered from a nominal 115 V a.c. or 230 V a.c.
supply and has a nominal power consumption of 33 W. Power is normally
derived from the a.c. mains, but if a supply failure occurs, the multiplexer
PSU will supply operating power to the multiplexer for approximately three
hours from internal back-up batteries.
If the multiplexer PSU is assembled but is disconnected from the a.c. supply
for a period in excess of three days, it is recommended that the batteries are
removed from the unit.
Functional description
Figure 4-1 shows the block diagram of the multiplexer PSU.
The a.c. input is connected, via an IEC mains connector fitted with an in-line
2.5 A fuse, to the power supply unit. The fuse protects the power supply unit.
An a.c. input filter reduces conducted and radiated electromagnetic

interference to within the limits specified by EN55022 (radiated and
conducted emission) and EN50082 (EMC).
The output of the a.c. filter is fed to an a.c./d.c. converter and charger unit
where the a.c. is stepped down and rectified to provide regulated power to
charge the two PSU back-up batteries and to deliver power to the multiplexer.
Over-voltage and over-current protection are provided for the output.

4-2 Power supply unit
The output from the converter and charger is also connected to a comparator
which monitors the d.c. output and battery voltages and carries out the
following actions:
• disconnects the batteries from the output, via a relay, if the battery voltage
falls below a predetermined level. They are disconnected if the battery
voltage falls below 19 V ± 0.5 V, and re-connected at 23.5 V ± 0.5 V.
• extinguishes the d.c. LED if the output voltage falls outside predetermined
limits.
• sets alarm signals (PS-Power_Fail, PS-Battery_Low, PS-Door_Open) on
the d.c./alarm connector.
0
Figure 4-1
TN-1C PSU block diagram
Fuse
+ 0V
1
a.c. a.c./d.c.
a.c. input converter d.c. Batteries failed
input filter & LED LED (red)
charger d.c.
Fuse 7.5 A
output
– +
Comparators Protection
and relay Batteries
Diode
–
5 –24 V
3 PS-Power_Fail
2 PS-Battery Low
9 PS-Door_Alarm
4 Alarm earth
common
6
Shield
The batteries are charged from the d.c. output supply and are protected
against reverse connection and over-current at the output, by a protection
diode and a 7.5 A fuse respectively.
Battery back-up
The two batteries contained in the multiplexer PSU are 12 V, nominally 6 AH,
maintenance-free, sealed, rechargeable, lead-acid batteries connected in
series. The batteries are charged, and capable of powering a multiplexer for
approximately three hours should a mains supply failure occur.
Alarms and indications

The multiplexer PSU has two indicator LEDs and three alarm outputs.

The indicator LEDs are fitted to the alarm/interface unit. They are not visible
from the outside of the case, and are provided for maintenance purposes only:
• A red LED indicates that the battery voltage has dropped below
19 V ± 0.5 V, after the a.c. input voltage has been disconnected. If the
voltage continues to drop below a predetermined level, the LED is
extinguished.
• The green LED indicates that the nominal –28 V d.c. charger output
supply is present and within tolerance. It is extinguished if the charger
output voltage falls outside the limits of –24.9 V to –30 V d.c.
0
The alarm/interface panel contains a PSU ‘door open’ alarm microswitch.
The alarms are routed, via the d.c./alarm connector, to the multiplexer where
they may be accessed via a local UI session. Alternatively, they are included
in ECC overhead bytes and reported back to the CAT, via a remote UI session,
4
or to the element controller EC-1.
The alarms are as follows:
Alarm Description Type Parameters
PS-Battery_Low Battery low Active low Set if d.c. battery voltage

voltage (absolute value) falls below
21 V ± 0.5 V
PS-Power_Fail Line Power Fail Active low Set if charger output d.c. voltage
falls below 26.2 V ± 0.5 V
PS-Door_Open Door Alarm Active low Set if door is open
Connectors
The 115 V a.c. or 230 V a.c. mains input is connected via an IEC connector
assembly. This connector assembly also contains the mains fuse, filter, and a
spare fuse.
The d.c. output and alarms are routed to a nine pin ‘Mate-n-lock’ connector.
The pin-out of the connector is shown in Table 4-1.
Table 4-1
D.C./alarm connector pin-out
Pin Function Pin Function

1 d.c. feed return 0 V 6 Shielding
2 PS-Battery_Low Voltage 7 Not used
3 PS-Power_Fail 8 Not used

4 Alarm earth/common 9 PS-Door_Open
5 d.c. feed power –24 V

4-4 Power supply unit
Construction
The multiplexer PSU, which is designed for wall mounting, is housed in a case
identical to the multiplexer unit case. The enclosure cover is locked and there
are no customer field replaceable items. The unit comprises the following
major components:
• multiplexer type case
• IEC a.c. input connector/fuse/filter unit
• a.c./d.c. converter/charger unit
• alarm/interface panel
• two 12 V back-up batteries
0
All of the multiplexer PSU components are mounted on the backplate of the
multiplexer PSU case, the layout of which is shown in Figure 4-2. The two
12 V batteries slot into shelves on the backplate and are connected to the
charger unit by spade connectors.
The a.c. power lead plugs into an IEC connector at the bottom of the unit. The
d.c. supply/alarm output cable connects to the d.c./alarm connector located on
the alarm/interface panel below the converter/charger unit. The leads exit the
case via cutouts in the bottom or top of the case.

Figure 4-2
TN-1C and TN-1P multiplexer PSU layout
Battery
Battery
support
a.c./d.c.
converter and 4
charger unit
a.c voltage
selector
Battery
Battery
support
Alarm/interface
panel
d.c. fuse
Tyrap
(8 positions) d.c./alarm
connector
spare
d.c. fuse
door open
microswitch
d.c. supply/
alarm output
IEC a.c. mains input cable
connector assembly
PSU backplate Case backplate
end of chapter

5-1
Synchronisation 5-
For integration into an SDH network, the TN-1C, TN-1P, TN-1PH and TN-1P
Basestation multiplexers can synchronize to any external signal traceable to a
Primary Reference Clock (PRC):
Sources
The multiplexer synchronisation can be derived from any one of the following
sources:
• STM-1 optical aggregate input (aggregate A or B) 5
• 2 Mbit/s G.703 tributary input on the main multiplexer card
• 2 Mbit/s G.703 tributary input on a tributary extension card (TN-1C only)
• 34/45 Mbit/s tributary input on a tributary extension card (TN-1C only)
• 2 Mbit/s external synchronisation input (TN-1C and TN-1P ADM card
upgrades only)
• remain in the last known frequency (‘Holdover’)
• internal ‘free-running’ clock
Note 1: If synchronisation is derived from a tributary input, the signal can
be framed or unframed as the multiplexer derives an 8 kHz clock from the
signal and does not reframe it.
Note 2: A tributary in the ‘traffic off’ or ‘traffic stand-by’ state cannot be
used for synchronisation purposes.
Note 3: Use of the internal oscillator is not recommended when the
multiplexer is connected to an SDH system. An external source is
preferred.
Note 4: The use of synchronisation derived from the External
Synchronisation Input (TN-1C and TN-1P ADM card upgrades only) is
preferred to the use of the PDH port for synchronisation.
Synchronisation loss
The multiplexer interprets the following as loss of synchronisation signal:
• Loss of signal (RS-LOS or PPI-LOS)
• Receipt of an AIS (MS-AIS or PPI-AIS)
• Synchronisation source ‘out of limits’ (SYNC-Source_Fail)
• Loss of external synchronisation signal (SYNC_Ext_Sync_LOS)

5-2 Synchronisation
Note 1: For all the above synchronisation signal losses (except ‘out of
limits’), the synchronisation signal becomes valid again if the defect is
cleared for 10 seconds.
Note 2: A synchronisation source is considered ‘out of limits’ by the
multiplexer when the multiplexer cannot synchronize to the source whilst
it is in use. Synchronisation source ‘out of limits’ requires manual clearing
by the operator.
Note 3: The internal oscillator is a standard SDH clock but synchronizing
to an external clock is recommended. Therefore if a faulty synchronisation
source becomes valid again, the multiplexer will re-synchronize to it even
when reversion is off.
Note 4: Detection of an invalid external synchronisation source (TN-1C
and TN-1P ADM card upgrades only) is only performed when the source
becomes the reference. Ensure that a valid 2 Mbit/s signal is present on the
external synchronisation input (do not connect a 34/45 Mbit/s signal).
It is also possible to specify the following optional criteria as loss of

synchronisation signal in addition to the above.
• Excessive Bit Error Rate (MS-EXC or PPI-EXC)
• Loss of frame alignment (RS-LOF or PPI-LOF)
• Path Trace Mismatch (HP-TIM)
Synchronisation schemes
TN-1C
The following synchronisation schemes are recommended for TN-1C
applications and are designed to avoid possible synchronisation loops:
• Figure 5-1(a) shows a point-to-point application whose requirement is to
deliver the signals, while providing a G.703 compliant signal at the
tributaries (± 50 ppm for 2 Mbit/s). The multiplexer internal clock is
sufficient for this requirement (if no timing is required to be carried
between the two stations) although an external source is preferred.
However, using loop timing in the other multiplexer reduces the need for
pointer processing.
• Figure 5-1(b) shows a point-to-point application where one site (e.g. a
‘central office’) provides synchronisation to the other station, an external
source should be used. The external source can be a tributary signal, which
may or may not carry traffic, or the external synchronisation input. The
remote multiplexer derives synchronisation from the incoming optical
signal (± 20 ppm for STM-1) and uses it for aggregate and tributary
transmission.
• Figure 5-1(c) shows a ring application which has one node synchronized
to an external synchronisation source traceable to a PRS, that uses this
clock for transmission. All other nodes derive timing from the feeding
STM-1 link to use it for aggregate and tributary transmission.

Synchronisation 5-3
• Figure 5-1(d) shows a special case where an accurate reference signal

exists on every node (traceable to a PRS). It may be beneficial to derive
timing at the multiplexer from this accurate source in all nodes, rather than
use the line timing (which may be traceable to a primary source, but with
accumulated jitter and noise). The line timing may be used as a backup in
case the external signal fails.
TN-1P
The following synchronisation schemes are recommended for TN-1P
applications and are designed to avoid synchronisation loops:
• Figure 5-2 (a) shows a point-to-point application which merely requires
the transport of 2048 kbit/s PDH signals between two sites, while
providing a G.703 compliant 2048 kbit/s signal (± 50 ppm) at the
tributaries. The TN-1P’s internal oscillator at one TN-1P is sufficient for
this requirement. The second TN-1P derives its synchronisation from the
aggregate input, hence synchronizing both TN-1Ps to a single clock,
reducing the need for pointer processing.
• Figure 5-2 (b) shows a point-to-point application where one site (e.g. a
‘central office’) provides synchronisation via a 2 Mbit/s PDH port (ESI 5
port is not available on the standard TN-1P, but is available for TN-1P
ADM upgrades) to the other site. The tributary signal that is used may or
may not carry traffic. The remote TN-1P derives synchronisation from its
optical aggregates and uses it for aggregate and tributary transmission.
• Figure 5-2 (c) shows a TN-1P connected to an SDH add/drop multiplexer
(ADM) (for example, a Nortel Networks TN-1X). In this case, the TN-1P
should derive synchronisation from the STM-1 link(s) received from the
SDH ADM (which is likely to have a more accurate clock signal). This
signal is used for aggregate and tributary transmission.
CAUTION
Synchronisation timing loops
Take care when setting the synchronisation sources in a
network in order to avoid timing loops. For example, if a single
NE with a primary reference clock (see Figure 5-1) provides
snchronisation for a ring application, none of the aggregates
should be put in the synchronisation hierarchy in addition to the
external port for that NE.

5-4 Synchronisation
Figure 5-1
TN-1C recommended synchronisation scheme
Site #1 Site #2
INT
TN-1C TN-1C
Customer Premises Customer Premises

(a) Point-to-point application - simple station
EXT
(2 Mbit/s)
TN-1C TN-1C
Central Office Customer Premises

(b) Point-to-point application - with Central Office station
TN-1C
TN-1C TN-1C
TN-1C
(c) Ring application with Single Timing Reference
TN-1C
TN-1C TN-1C
TN-1C
(d) Ring application - with 2 Mbit/s Reference at every node
Synchronisation source or reference signal

Synchronisation path and direction

Synchronisation 5-5
Figure 5-2
TN-1P recommended synchronisation schemes
Site #1 Site #2
INT
TN-1P TN-1P
Customer Premises Customer Premises
(a) Point-to-point application - simple sites
EXT
(PDH port) (Note 1)
5
TN-1P TN-1P
Central Office Customer Premises
(b) Point-to-point/Head-end application - with Central Office
SDH TN-1P
ADM
e.g. a Nortel Networks TN-1X Customer Premises

multiplexer
(c) ADM tributary application
Note: If the Central Office TN-1P is upgraded to an 8 x 2 Mbit/s ADM, it can derive
its synchronisation via its external synchronisation input port.
Synchronisation source or reference signal.

Synchronisation path and direction.

5-6 Synchronisation
Synchronisation source switch event

After a synchronisation source switch has occurred, the craft access terminal
(CAT) or the EC-1 element controller displays a synchronisation source
switch event when you access the network element. This is not an alarm but
an indication that a changeover from one synchronisation source to another
has occurred. If a sync source switch occurs, an alarm is raised if the new
sync source is not the primary source. This alarm does not cause the red LED
to light as it does not affect traffic.
Synchronisation source hierarchy

The basis for synchronisation source protection is the synchronisation source
hierarchy. This is formed from three sources identified by the user. The first
source has the highest priority for the user, with the third having the lowest. A
stand-by signal is also available, which is always the internal oscillator. Only
sources listed within this hierarchy are considered for use.
The selected synchronisation source is used until the source fails, or a decision
to change sources is taken.
Synchronisation settings
The use of the synchronisation source hierarchy is controlled by reversion and
force settings as described in the following sections:
Reversion on/off
Reversion controls the selection of a source if a source fails:
• Reversion on. If a source fails, or a decision to change sources is made,
both higher and lower priority sources can be selected for use. The higher
priority source is only considered if that source has recovered.
• Reversion off. When a source fails, or a decision to change sources is
made, only sources of a lower priority can be selected for use.
If a source fails, a non-reversion flag is set on this source to prevent its

re-selection at a later stage. This flag must be cleared manually by the user
before that source is available for selection again.
Note: Reversion settings are not used when a source is in forced use (i.e.
force on).
Force on/off
Force on/off allows the user to manually select the source to be used.
• Force on. Using this setting, one of the sources in the hierarchy, including
one that is currently invalid, is selected for use. The multiplexer is not able
to change to a different source while in this mode.
If a source becomes invalid while in this mode, or if an invalid source is
selected for use, the multiplexer begins a ‘holdover period’. During this
period, the multiplexer reproduces the absent synchronisation signal
internally. This situation is resolved in either of the following ways:
— If the source becomes stable again during this time, the source is used
as if had not been interrupted.

Synchronisation 5-7
— If the holdover period ends (typically after five seconds) without the
source becoming available, the standby source (the internal oscillator)
is used.
Note: When a source is in forced use, reversion settings are ignored.
• Force off. Using this setting cancels any existing forced source usage, and
source selection comes under the control of reversion setting. Existing
non-reversion flags are unaffected when this mode is selected.
Note: The circumstances under which a switch in synchronisation occurs
depends on the implementation mechanism used.
Synchronisation switching mechanisms

The circumstances under which a switch in synchronisation occurs depends on
the implementation mechanism used. There are two mechanisms:
• A Synchronisation Status Messaging (SSM) mechanism. This uses
transmitted quality levels to determine the best source. See
“Synchronisation status messaging (SSM)” on page 5-7.
• A non-SSM system.With this mechanism, changes to the selected 5
synchronisation source only occur when a source fails, or if a manual
change is performed. See “Non-SSM synchronisation sourcing (TN-1C/
TN-1P)” on page 5-12.
Both of these mechanisms make use of the software settings described in
“Synchronisation settings” on page 5-6
Synchronisation status messaging (SSM)

Synchronisation status messaging (SSM) is based on the transmission of
synchronisation quality messages between potential synchronisation sources.
Using this system, the TN-1C/TN-1P is able to evaluate which synchronisation

source is the best for use. This evaluation is used under two circumstances:
• The best source will always be selected for use, subject to software settings
restrictions (see “Synchronisation settings” on page 5-6). That is, if a better
quality source is identified (and no source is in forced use), the current
reversion settings will dictate whether this source can be selected for use.
• If a source fails, the best of the remaining sources will be selected for use,
subject to software settings restrictions (see “Synchronisation settings” on
page 5-6). If no source is available, the stand-by source is selected.
Note: The SSM mechanism can only select sources that are listed in the
synchronisation source hierarchy.
The TN-1C and TN-1P support the transmission and reception of the Quality
Level (QL) and use SSM for determining the synchronisation source.
The QL of a source is transmitted in the section overhead of all STM-1
signals as the S1 byte. QL has a possible range of 1 to 15, with 1 as the

5-8 Synchronisation
highest priority. In practice, a subset of these values is used by the

multiplexer. This subset of QL values is defined in Table 5-1 .
Table 5-1
SSM quality levels
QL Meaning Description
0 Synchronisation quality Included for backwards compatibility

unknown. reasons. The multiplexer interprets QL = 0 as
QL = 15.
2 Traceable to Primary The external timing source for the network.

Reference Clock (PRC).
4 Traceable to Transit Clock. A clock provided for equipment which does

not connect with customer equipment. That
is, it only connects to other nodes.
8 Traceable to Local Clock. A clock provided for equipment which

connects directly with customer equipment.
11 Traceable to SDH The internal oscillator of the multiplexer.

Equipment Clock (SEC). Note: This is the default setting.
15 Do not use for Prevents the multiplexer’s synchronisation

synchronisation. source from being used by multiplexers that
receive this value.
You can configure the QL settings for both RX and TX purposes. These
manual settings override any QL values established by the TN-1C/TN-1P
software.
Note: By default, the TN-1C and TN-1P transmits using its internal clock
which has a QL of ‘11’ on the STM-1 ports.
The TN-1C/TN-1P transmits its QL on all STM-1 ports, except for the
STM-1 port from which it receives its synchronisation source. The QL
transmitted on this port is 15, which indicates to the source of the
synchronisation that the TN-1C or TN-1P should not be used for
synchronisation. This action prevents closed synchronisation loops, where
two multiplexers each attempt to synchronise from the synchronisation signal
of the other.

Synchronisation 5-9
Synchronisation status messaging network examples

Simple ring with a single reference source
Note: Applicable only to TN-1C and TN-1P fitted with the 8 x 2 Mbit/s
ADM card.
An example simple ring network with a single reference source is shown in

Figure 5-3.
Figure 5-3
SSM within a simple STM-1 ring with a single external source
PRC (An EXTernal source)

QL = 2
2 2
TN-1C (A)
QL = 2
A Hierarchy=EXT
15
B
B
A
2 5
TN-1C TN-1C
QL = 2 STM-N RING QL = 2
Hierarchy=B, A Hierarchy=B, A
A B
2
B A 15
TN-1C
QL = 2
Hierarchy=B, A
15 2
In the example in Figure 5-3, synchronisation is derived from the Primary

Reference Clock (PRC). The PRC is the external (EXT) source with a QL=2
at TN-1C(A). The other TN-1Cs in the ring have their hierarchy set to derive
synchronisation from the counter-clockwise TN-1C in preference to the
clockwise TN-1C (i.e. on their B ports in preference to A). The QL = 2 clock
is transmitted on all STM-1 ports for the TN-1C, with the exception of the
return port of the synchronisation source, on which QL = 15 (‘do not use for
synchronisation’) is transmitted. This prevents closed synchronisation loops.
Note: Before the PRC signal was introduced, all four TN-1Cs would have
used the default QL setting of 11, which indicates the use of an internal
oscillator (INT).
If a fibre break occurs, the TN-1Cs after the break will send a QL = 11 in the
counter-clockwise direction. The last TN-1C in the ring will switch to the
higher quality clock (QL = 2) being sent from the TN-1C with the PRC in the
clockwise direction. The QL = 2 clock is then available from its clockwise
port, so moving in a clockwise direction around the ring each TN-1C will
switch to the PRC QL = 2 clock. The ring will then be synchronised to the
highest available quality clock.

5-10 Synchronisation
Simple ring with two reference sources

Note: Applicable only to TN-1C and TN-1P Basestation fitted with the
8 x 2 Mbit/s ADM card.
An example simple ring network with a two reference sources is shown in

Figure 5-4.
Figure 5-4
SSM within a simple STM-1 ring with two external sources
PRC (An EXTernal source)

QL = 2
2 2
TN-1C(A)
QL = 2
15 A Hierarchy=EXT, B B
2
B A
TN-1C TN-1C
QL = 2 STM-N RING QL = 2
Hierarchy=B, A Hierarchy=B, A
A B
2
B A 15
TN-1C(B)
QL = 2
Hierarchy=B, EXT
15
2
QL = 3
SRC (An EXTernal source)
Synchronisation is derived from the Primary Reference Clock (PRC). The

PRC is the external (EXT) source with a QL=2 at TN-1C(A). There is also a
Secondary Reference Clock (SRC) which is also external and has a QL = 3 at
TN-1C(B). The other TN-1Cs in the ring have their hierarchy set to derive
synchronisation from the counter-clockwise TN-1C in preference to the
clockwise TN-1C, i.e. on their B ports in preference to A. The QL = 2 clock is
transmitted on all STM-1 ports for the TN-1C, with the exception of the
return port of the synchronisation source, on which QL = 15 (‘do not use for
synchronisation’) is transmitted. This prevents closed synchronisation loops.
In the event of a failure of the primary reference source the TN-1C with the
primary source switches to an internal clock with a QL = 11. This will
propagate around the network until it reaches the TN-1C with the secondary
reference source which will switch to the SRC and transmit a QL = 3. This
will then propagate around the network in a clockwise direction with the other
TN-1Cs synchronising to the secondary reference source.

Synchronisation 5-11
Note: The hierarchy on the TN-1Cs with the external sources are set so that
one synchronises in a clockwise direction around the ring and the other in
a counter-clockwise direction. This is to prevent synchronisation timing
loops.
Chain network with two reference sources

An example simple chain network with a two reference sources is shown in
Figure 5-5.
Figure 5-5
SSM within a simple STM-1 chain with two external sources
PRC SRC
QL = 2 QL = 3
TN-1C
QL = 2
15
TN-1C
QL = 2
15
TN-1C
QL = 2
15
TN-1C
QL = 2
5
2 2 2
For a chain network, there must be two reference sources, one at each end of
the network. In normal operation, the chain will derive its synchronisation
from the primary source. In the event of failure of the primary reference
source, the chain will derive its synchronisation from the secondary reference
source. In the event of a loss of a link, the chain will divide into two
synchronisation islands, one using the primary reference source and the other
the secondary reference source.
SSM recommendations
SSM can be used to increase the resilience of the synchronisation network to
network faults such as fibre breaks. It can also be used where the network is
carrying synchronisation sensitive services such as video.
SSM simplifies some operational aspects of synchronisation design, however,

care must be taken to avoid timing loops during the transition to SSM. The
following are recommendations regarding SSM:
1 If upgrading from an earlier TN-1C release where the synchronisation is
operating correctly, do not use SSM.
2 If SSM is to be deployed:
a. Have a clear understanding of how you wish to configure SSM to
operate in your network.
b. Develop a detailed plan for the configuration.
c. Set up the quality levels and priorities on each NE in the network first.

d. Initiate SSM on the NE from which the synchronisation source is

derived.
e. Initiate SSM on the next NE in the network.
f. Continue working around the network initiating SSM on each NE in
turn.
3 Avoid timing loops:
— During SSM configuration, ensure that there are no NEs without SSM
initiated between NEs that have SSM initiated.
— If some NEs do not support SSM, SSM should not be used in that ring
or chain.
— Do not mix SSM on a port, i.e. a port should have both or neither RX
override and TX override set to SSM.
— If RX override and TX override are not set to SSM, at least one must
be set to a QL = 15, i.e. a fixed configured port may use a received
synchronisation or transmit a usable synchronisation, but not both.
— Normally a STM tributary port should only be set to a fixed QL, i.e.
non-SSM, because either the other end of the link does not support
SSM or it is required not to use SSM over that link. This is the case at
a network boundary, e.g. span of control limit, operator boundary,
inter-link between rings.
4 When an NE uses its Internal synchronisation source as the reference
source, it is recommended that the RX and TX override values for the
aggregates of that NE are configured to a value of less than 11. This is
because the non-configurable Internal source has an QL = 11, which is the
same as the holdover QL value (for a digital PLL).
5 If a single NE brings the synchronisation into the network, do not have the
aggregates in the synchronisation hierarchy at that NE. This avoids the
situation where the aggregates receive a QL which is higher than all others
and is consequently selected as the NE QL. In this situation, all NEs would
be synchronised off aggregates, resulting in ‘timing loops’ and loss of the
external reference source. To resolve this, the synchronisation hierarchy
would need to be re-applied.
Non-SSM synchronisation sourcing (TN-1C/TN-1P)
When the SSM system is not in use, changes to the selected synchronisation
source only occur when a source fails, or if a manual change is performed.
Changes due to source failure as subject to software settings restrictions (see
“Synchronisation settings” on page 5-6). With SSM off, the TN-1C/TN-1P can
operate in one of three modes dependent on the reversion and force settings.
• Manual-only selection mode (MANUAL). In this mode automatic
selection of the synchronisation source is disabled. The synchronisation
source is selected manually by the user. The user can select any available
synchronisation source, no validity check is provided on the selected
source. This mode is selected by setting force on and SSM off (the
reversion setting has no effect).

Synchronisation 5-13
• Automatic switching with manual reversion mode (FALLBACK). In this

mode the multiplexer switches to the next highest priority valid source if
the selected synchronisation source fails. If a higher priority
synchronisation source recovers, it is not automatically selected as the
synchronisation source. To switch back to the higher priority source, the
user must perform a manual reversion. This mode is selected by setting
reversion off, force off and SSM off.
• Automatic switching with automatic reversion mode (REVERSION). In
this mode the multiplexer switches to the highest priority valid source
available. If a higher priority synchronisation source recovers, the source
is automatically selected as the synchronisation source. This mode is
selected by setting reversion on, force off and SSM off.
Failure of synchronisation source
When automatic switching is selected (either with manual reversion or
automatic reversion), the validity of the source is checked prior to switching.
The following alarms and activity detectors are used to determine the validity
of the source:
• STM-1 aggregate ports 5
— RS-LOS
— RS-LOF
— MS-AIS or AU-AIS
— MS-EXC
• 2048 kbit/s, 34368 kbit/s or 44736 kbit/s tributary ports
— PPI-LOS
— PPI-AIS (not applicable to 44376 kbit/s tributary ports)
— PPI-EXC
• External Sync Source Activity Detector
Wait to restore time

When a synchronisation source recovers, a check is performed to check that it
has recovered for a period of time. The period of time, known as the “wait to
restore time” is configurable via the user interface.
Synchronisation alarms
There are six alarms associated with the synchronisation facility. These are:
• ‘SYNC-Holdover’ - indicates that the multiplexer has entered holdover
(using the last known frequency) or free-run (using the internal clock). The
alarm is not raised if the internal clock is selected as the primary source.
• ‘SYNC-Source_Fail’ - indicates failure of the currently selected source.
• ‘SYNC-Src_Not_Primary’ - indicates that the primary synchronisation
source is not currently selected.
• ‘SYNC-Ext_ Sync_LOS’ - indicates that the external synchronisation
source has failed.

• ‘SYNC-Source-Out-of-Limits’ - this alarm is raised against the port in the

Signal Status Hierarchy that the Phase Lock Loop (PLL) fails to lock on to
it.
• ‘SYNC-SSMB_Unstable’ - this alarm is raised when the QL of the
aggregate is not stable (S1 defect is active). Applies only if the SSM_mode
is ‘on’ and the aggregate is in the SS Hierarchy.
end of chapter

6-1
Performance monitoring 6-
The TN-1C or TN-1P multiplexer generates performance monitoring (PM)
information from various points in the network element, known as
performance monitoring points (PMPs). PM data is not collected for
tributaries that are in the ‘traffic off’ or ‘traffic stand-by’ modes.
The synchronous equipment management function (SEMF) of the multiplexer

software collects and analyses PM data. The performance information is
available to the user via all open sessions of the craft access terminal (CAT) or
by the Element Controller EC-1 accessing the embedded user interface
software.
PM reporting (to the EC-1) can be configured by the user to suppress zero
reports and zero PMPs. This avoids loading network comms with unnecessary
messages. 6
Parity error counts
The multiplexer uses block counts as the basis for PM parity error counts.
Block counts are the sum of all bit-interleaved parity (BIP) blocks in error
detected in the count period (nominally 1 second).
Performance monitoring counts
There are a number of performance counts that are accumulated within the
multiplexer. The following categories of performance monitoring information
are generated for each of the PMPs:
• errored seconds (ES). An ES is a second in which at least one anomaly
(parity error/code violation) or performance defect (alarm) occurs. The
total number of errors is not recorded. See Table 6-1 for a list of anomalies
and defects.
• severely errored seconds (SES). An SES is a second in which either a
threshold level of anomalies is exceeded or a performance defect occurs.
The actual number of errors within this second is not recorded. An SES is
also, by definition, an ES. The threshold number of errors which
distinguish an ES from an SES can be configured by the user.
• background block error (BBE). A BBE is a block, not included in an SES,
in which there is an anomaly.

6-2 Performance monitoring
• unavailable seconds (UAS). A UAS is any second which forms part of a

period of unavailable time (UAT). A period of UAT starts with the onset of
ten consecutive SESs (included in UAT). The period of UAT ends when
there are ten consecutive non-SES seconds (not included in the UAT). UAS
is only counted during an AS (assessed second).
Note: During periods of UAT, the ES, SES and BBE statistics are not
recorded. The start of the UAT is indicated by ten consecutive SESs. Until
this ten seconds is complete, however, it is unclear whether the ES, SES
and BBE figures accumulated will be recorded. As a result, there is a ten
second delay in all performance monitoring timestamps.
• assessed seconds (AS). The AS is the number of seconds during which the
performance monitoring statistics were accumulated. This can be 0 for a
particular monitoring point. Typically, this is equivalent to the length of the
performance monitoring period. However, if the multiplexer is rebooted, or
the performance monitoring period is terminated early, or the clock
changes, the AS total may be shorter or longer than the performance
period.
Performance monitoring points

Performance monitoring points (PMPs) are points at which performance data
is collected. This data relates to the quality of the transmission path passing
through that point.
Note 1: TN-1C and TN-1P hardware only provides monitoring at a traffic

termination path. As a result, no performance data that relates to through
traffic can be collected.
Note 2: PDH physical interface code violation (PPI-CV) performance
monitoring must not be enabled for ports that have either PPI-AIS
consequent actions or monitoring disabled for the port.
The PMPs supported by the TN-1C and TN-1P are:
• MS - multiplexer section
• HP - high-order path
• HP-TIM - high-order path trace identifier mismatch
• HP-FE - high-order path far end
• LP - low-order path
• LP-FE - Low-order path far end
• PPI-AIS - PDH physical interface (PPI) alarm indication signal
• PPI-CV - (PPI) code violations
• PPI-CRC4 - PPI cyclic redundancy check (2 Mbit/s tributaries only)
• PPI-Tx - PPI transmit
• PPI-FRAMED (2 Mbit/s tributaries only)

Disabling performance monitoring

The user can configure the multiplexer to enable or disable a PMP. The
default value for all PMP instances is OFF. The user can disable the 15 minute
and 24 hour PMPs separately on a per monitored point instance basis. If a
PMP is disabled, it is not displayed on the current performance count.
Performance anomalies and defects

The basis for determining performance anomalies and defects are detailed in
Table 6-1.
Table 6-1
PMP anomalies and defects
PMP Definition Anomalies Defects
MS B2, BIP-24 B2 Errors RS-LOS
RS-LCF
MS-AIS
MS-EXC
HP B3, BIP-8 B3 Errors All MS defects
All RS defects
AU-AIS
HP-LOM (VC-12 only)
INT-AU-AIS
HP-FE G1, REI, BIP-8 G1 Errors

INT-AU-LOP
HP-RDI
6
LP (VC-12) V5 Bits 1, 2 BIP-2 V5 Errors All RS defects
All MS defects
All HP defects
TU-AIS
TU-LOP
INT-TU-AIS
INT-TU-LOP
LP-EXE (see Note 1)
LP (VC-3) B3, BIP-8 B3 Errors All RS defects
(34/45 Mbit/s All MS defects
only) All HP defects
TU-AIS
TU-LOP
INT-TU-AIS
INT-TU-LOP
LP-EXE (see Note 1)
LP-FE V5 Bit 3, REI, BIP-1 V5 Error HP-RDI
(VC-12) LP-RDI
LP-FE (VC-3) G1, REI, BIP-8 G1 Error HP-RDI
(34/45 Mbit/s LP-RDI
only)
PPI-CV HDB3 Code Violations HDB3 CV PPI-LOS
(see Note 2) (2 Mbit/s and 34 Mbit/s) B3ZS CV PPI-EXE
B3ZS Code Violations
(45 Mbit/s)
—continued—

Table 6-1
PMP anomalies and defects (continued)
PMP Definition Anomalies Defects
PPI-TX PPI-TF
PPI-FRAMED G704 frame alignment PPI-LOS
(2 Mbit/s) PPI-EXC
G751 frame alignment PPI-LOF
(34/Mbit/s) PPI-AIS
PPI-CRC G706 errored blocks PPI-LOS

PPI-EXC
PPI-LOF
PPI-AIS
PPI-LOM
Note 1: If configured for PPI AIS.
Note 2: PPI-CV performance monitoring must not be enabled for ports that have
either PPI-AIS consequent actions or monitoring disabled for the port.
Performance monitoring periods

Performance monitoring data is accumulated over a performance monitoring
period. There are two types of monitoring periods. These are:
• 24 hour monitoring period. Performance monitoring results can be
calculated for any 24 hour period. The starting hour for such a period can
be configured by the user, though the default start time is midnight.
• 15 minute monitoring period. Performance monitoring results are
automatically calculated for each fifteen minute period of the day. The start
and end times for 15 minute monitoring periods are fixed on quarter-hour
boundaries.
CAUTION
15 minute performance monitoring
The wider range of performance monitoring options provides
greater flexibility when monitoring service quality. 24 hour
performance monitoring is used for normal performance
monitoring measurements. 15 minute performance monitoring
produces large quantities of data, and should only be used on a
manual basis for specific maintenance measurements. Do NOT
use it to collect performance monitoring data automatically.
Both 15 minute and 24 hour monitoring periods can be terminated

prematurely. In this instance (like scheduled termination), performance
results are stored as logs (see “Performance logs” on page 6-5), totals are
reset, and a new monitoring period begins immediately.
Note: The exception to the above rule is when a terminated 15 minute

period has less than half of its scheduled fifteen minutes remaining. In this
instance, the new period will not end at the scheduled end of the current
period, but will continue to the end of the next 15 minute period. As a
result, the duration of the new period can be 22.5 minutes.

Performance logs
Performance logs store the results of individual monitoring periods in which
monitoring is active. The following performance logs are available:
• 15 minute performance log.
• 24 hour performance log.
• intermediate performance log.
• UAT performance log. This log displays unavailable time information.
If it is not possible to store a new performance log, the oldest will be deleted.
To avoid loss of data, the EC-1 must upload performance monitoring results
frequently.
Performance logs are numbered from 1 to 2147483647, with the latest logs
having the highest log numbers. Upon reaching the highest log number, the
next number returns to ‘1’. The user can also use log numbers between -1 and
-16 (for 15 minute logs) and -1 or -2 (for 24 hour logs) to access the latest
logs (-1 being the most current log).
15 minute logs
The TN-1C or TN-1P can store up to sixteen 15 minute performance logs.
This is equivalent to four hours, assuming that no premature terminations are
performed. For the 15 minute report, if a PMP is disabled or no errors are
detected during the interval, no data is displayed for that PMP.
6
Changing the current time
If the current time is changed during a 15 minute log, the duration of the log
is never less than 7.5 minutes and never greater than 22.5 minutes. Table 6-2
summarizes the behaviour of the multiplexer if the start time or current time
of the multiplexer are changed. Time changes are recorded in the performance
monitoring report and no alarms are raised relating to time changes.
Table 6-2
15 minute log behaviour after current time change
Log duration Time remaining Expected Duration of Duration of next

until time until next start behaviour current log log (mins)
change (mins.) time (mins)
0 to 7.5 Not applicable Continue log 7.5 to 22.5 15
7.5 to 22.5 0 Early termination 7.5 to 22.5 15
15 to 22.5 Not applicable Early termination 15 to 22.5 7.5 to 22.5
7.5 to 15 0 to 7.5 Continue log 7.5 to 22.5 15
7.5 to 15 7.5 to 15 Early termination 7.5 to 15 7.5 to 15
Note: If the log is terminated and the time remaining until the next
standard time (quarter-hour boundary) is less than 7.5 minutes, the
duration of the next log is also more than 7.5 minutes.

Assessed seconds (AS) count

PMPs that are only monitored for part of the duration show this in the AS
column.
Log contents after restarts

The contents of the current log are not lost after a warm restart or a
configuration switch. The system behaves the same way as for an early
termination, except that no report is issued to the user. The log duration could
be less than 7.5 minutes.
The contents of the current log are not saved after a cold restart, software
release switch, software release upgrade/downgrade, or power up.
24 hour logs
A maximum of two 24 hour logs can be stored: the current 24 hour log and
the previous 24 hour log. The user can view the two previous logs if they
exist. There is no similar zero suppression for the 24 hour logs. Zero counts
are displayed if no errors are detected.
Changing start and stop times

If the current time or start time is changed during a 24 hour log, the duration
of the log can change. All time changes are recorded in the performance
monitoring report and no alarms are raised relating to time changes. The
duration of the 24 hour performance monitoring period can vary if either of the
following is changed during that 24 hour period:
• start time of the 24 hour log period
• the time of the multiplexer
The duration of the 24 hour period cannot be less than 12 hours and cannot be
greater than 36 hours ±15 minutes. When the start time next occurs, the log
then reverts to a 24 hour period again. Table 6-3 summarizes the behaviour of
the multiplexer if the start time or current time of the multiplexer are changed.
Table 6-3
24 hour log behaviour after start time or current time change
Log duration Time remaining Expected Duration of Duration of next

until time until next start behaviour current log log (hours)
change (hours) time (hours)
0 to 12 Not applicable Continue log 12 to 36 24
12 to 36 0 Early termination 12 to 36 24
24 to 36 Not applicable Early termination 24 to 36 12 to 36
12 to 24 0 to 12 Continue log 12 to 36 24
12 to 24 12 to 24 Early termination 12 to 24 12 to 24

Early termination
If the user initiates an early termination, both the 15 minute and 24 hour logs
are terminated. This causes additional reports for both monitoring periods to
be generated at the time the early termination is initiated. Early termination
does not affect the configured borders. Time changes that cause premature or
non termination of a period, ignore early terminations that may have occurred
during the current period in deciding when to terminate next.
The duration of the 24-hour period can be less that 12 hours as a result of an
early termination.
Warm restart
After a warm restart is performed, the system behaves the same as for an early
termination, except that an early termination event is not reported.
The duration of the 24-hour period can be less than 12 hours as a result of a
warm restart.
Quality of service violation alarms

Quality of service violation (QOSV) alarms are raised on a PMP if any of the
ES, SES, BBE and UAS parameters exceed user configurable thresholds.
These alarms, which can be enabled and disabled on a PMP basis, can only be
raised if both monitoring and alarm raising are enabled for the affected PMP.
QOSV thresholds can be defined by the user, on both a BIP and block basis. 6
Note 1: If alarm raising is disabled for a PMP, monitoring is unaffected.
Error counts will still be collated, and results will be stored. These results,
however, will not be used to trigger alarm events.
Note 2: If monitoring and alarm raising are enabled for a connection and
the physical connector is not present, QOSV alarms will be raised for the
PMP and will persist until the end of the current monitoring period.
The QOSV alarms are listed in the following table. For details of these
alarms, refer to Alarm Clearing Procedures, 323-1081-543
QOSV alarms
HP-FE_QOSV_15M LP-QOSV_15M PPI-CV_QOSV_15M
HP-FE_QOSV_24H LP-QOSV_24H PPI-CV_QOSV_24H
HP-QOSV_15M MS-QOSV_15M PPI-Frm_QOSV_15M
HP-QOSV_24H MS-QOSV_24H PPI-Frm_QOSV_24H
LP-FE_QOSV_15M PPI-CRC_QOSV_15M PPI-Tx_QOSV_15M
LP-FE_QOSV_24H PPI-CRC_QOSV_24H PPI-Tx_QOSV_24H

The alarm reports the identity of the PMP instance but does not report the
parameter type or the threshold value that is crossed. A QOSV alarm is
provided for each PMP instance and for each 15-minute and 24-hour
measurement period.
Under the following conditions, a delay of up to one minute can occur before
the QOSV alarm is reported:
• if the alarm was previously clear and accumulated data exceeds the QOSV
threshold for a PMP
• if instance monitoring for a PMP is changed to the ‘enable’ state
• if alarm monitoring is changed to ‘enable’
An alarm is automatically raised when an SES count exceeds the threshold

and a PMP moves from AT (available time) to UAT (unavailable time).
However, an alarm is not automatically raised when the PMP moves from
UAT to AT, as the UAS period is decreased by ten seconds when moving to
AT (i.e. when there are ten consecutive non-SES seconds, which are not
included in the UAT period).
Enable/disable of QOSV alarms

The user can enable or disable the reporting of QOSV alarms separately for
the 15-minute and 24-hour measurement periods for each PMP. If an alarm is
disabled for a PMP, the alarm is in the ‘clear’ state.
Clearing QOSV alarms

For the 15-minute logs, a QOSV alarm is cleared if no QOSV thresholds are
exceeded during the log. In the event of early termination, QOSV alarms for
the 15-minute measurement period are cleared for PMP instances which have
thresholds less than the QOSV threshold. As a result, 15 minute QOSV
alarms can be cleared before the end of the 15 minute period.
Traffic type
The performance monitoring log contains a traffic type field which can contain
the following:
• 2M - 2 Mbit/s non-specific
• 34_45M - 34/45 dual tributary
• STM1o - STM-optical

User actions
The following user actions are available through a user interface session.
• Change the starting time of the accumulation intervals with respect to
midnight.
• Display any specific log in the buffer.
• Query for intermediate counts (i.e. before the interval ends) - this
intermediate data is not logged.
• Perform early termination of counts - will cause the intermediate counts
data to be stored in the logs. The current registers are cleared and the
accumulation will continue from zero. This ‘new’ accumulation will
terminate at the end of the interval.
• Enable or disable reporting of zero errored PM reports to the EC-1.
When a VC-4 passthrough connection is provisioned at the TN-1C or TN-1P,

the high-order path (HP) and the low-order path (LP) related PMPs are
disabled.
end of chapter

7-1
System parameters 7-
This chapter provides system parameters for:
• the TN-1C and TN-1P multiplexers
• Power Supply Unit (PSU) (for TN-1C and standard TN-1P only)
• the TN-1PH headend subrack.
• TN-1P Basestation
Common
Electromagnetic compatibility
The TN-1C, TN-1P, TN-1PH and TN-1P Basestation power supply units
(PSUs) comply with the Class B Electromagnetic Compatibility (EMC)
requirements and with the Electrostatic Discharge (ESD) requirements defined
in:
• EN 55022 - for radiated and conducted emissions
• EN 50082-1 - EMC for residential, commercial, and light industry
Note: To comply with Class B EMC, ferrite attenuators must be fitted to
the cables as detailed in Installation Procedures, 323-1081-200.
7
Environmental conditions
The TN-1C, TN-1P, TN-1PH and TN-1P Basestation PSU are designed to
meet the requirement of ETSI standard ETS 300 019 in the following classes:
Storage (Class 1.2): –25ºC to +55ºC
10% to 100% RH
Transport (Class 2.3): –40ºC to +70ºC
(including fast change of temperature)
Operation (Class 3.1): 0ºC to 45ºC
5% to 85% RH, non-condensing

7-2 System parameters
Construction
External dimensions
Plastic cased variants and PSU
Height: 430 mm
Depth: 155 mm
Width 280 mm
Metal cased variants

Height: 430 mm
Depth: 190 mm
Width 295 mm
TN-1PH
Height: 650 mm
200 mm (fibre tray)
Depth: 300 mm
Width 450 mm
TN-1P Basestation
Height: 89 mm (2U)
Depth: 300 mm
Width 450 mm
Weight
TN-1C, TN-1C single-slot, TN-1P
Less than 10 kg
7.5 kg (PSU with batteries)
2.5 kg (PSU without batteries)
TN-1PH
8.5 kg (unequipped)
20 kg (fully equipped)
TN-1P Basestation
Less than 10 kg
Supply voltage
–20 V d.c. to –72 V d.c.
Note: This equates to nominal earthed battery station voltages between

-24 V and -60 V d.c.
Fuses
TN-1C Release 1 and 2 hardware
3.5 A
0.125 A

TN-1C (Release 3/5/5.1), TN-1P (Release 5.1) and TN-1P

Basestation (Release 5/5.1) hardware
0.125 A
Circuit breaker
TN-1P
3 A (Release 3/5)
TN-1PH
12 A slow-blow
Maximum power consumption

TN-1C
Main ADM card 8 x 2 Mbit/s (Release 1 hardware) 24 W
Main ADM card 8 x 2 Mbit/s (Release 3/5/5.1 hardware) 20 W
34/45 Mbit/s tributary extension card 3.4 W
Dual 34/45 Mbit/s tributary extension card 4.5 W
8 x 2 Mbit/s tributary extension card (Release 1 hardware) 5W
8 x 2 Mbit/s tributary extension card (Release 3/5 hardware) 6.4 W
8 x 2 Mbit/s tributary extension card (Release 5.1 hardware) 6.4 W
24 x 2 Mbit/s tributary extension card (Release 5.1 hardware) 6.4 W
Fan module 1.5 W
7
Note: For details of the optional Packet Edge 10 router card, refer to the
OPTera Packet Edge 10 User Guide 323-1043-401.
TN-1P
Unprotected TN-1P: 10 W maximum
Protected TN-1P: 13 W maximum
TN-1PH
Unprotected TN-1PH 135 W (fully equipped with 12 mux and 1 SEP)
Protected TN-1PH 171 W (fully equipped with 12 mux and 1 SEP)
SEP: 15 W maximum
TN-1P Basestation
Unprotected TN-1P 10 W maximum
Basestation
Protected TN-1P 13 W maximum
Basestation

External interfaces
2 Mbit/s tributary interfaces
Up to 32 x 2 Mbit/s tributary interfaces are supported, which conform to
ITU-T recommendation G.703 and to ETS 300 166 as follows:
Line rate: 2048 kbit/s ± 50 ppm
Line rate: HDB3
Output pulse height: ±2.37 V ± 10% (75 Ω) peak
±3.0 V ± 10% (120 Ω) peak
Nominal pulse 244 ns
width:
Cable loss to input: 0 dB to 6 dB at 1024 kHz,
typically: 280 m using 3002 cable
330 m using 2002 cable
Input return loss: not less than 12 dB (50 kHz to 100 kHz)
not less than 18 dB (100 kHz to 2048 kHz)
Output return loss: not less than 6 dB (51.2 kHz to 102.4 kHz)
not less than 8 dB (102.4 kHz to 3072 kHz)
34 Mbit/s tributary interfaces (TN-1C only)

Up to two 34 Mbit/s tributary interfaces are supported, which conform to
ITU-T recommendation G.703 and to ETS 300 166 as follows:
Line code: HDB3
Output pulse height: 1.0 V ± 0.1 V peak
Nominal pulse width: 14.55 ns
(typically maximum of 250m of 2003 cable)
Input return loss not less than 12 dB (860 kHz to 1720 kHz)
Output return loss not less than 6 dB (859.2 kHz to 1718.4 kHz)

45 Mbit/s tributary interfaces (TN-1C only)

Up to two 45 Mbit/s tributary interface are supported, which conform to
ANSI DS-3/TR-NW-000499 definitions as follows:
Line rate: 44736 kbit/s ±20ppm
Line code: B3ZS
Pulse height: 0.36 V - 0.85 V (isolated pulse)
Power Level: –4.7 dBm to +3.6 dBm (AIS signal)
Maximum reach in
typical installation: 450 ft
STM-1 optical interfaces

The STM-1 optical inputs and outputs exceed ITU-T recommendation G.957
for 155.52 Mbit/s STM-1 signals. Three STM-1 optical interface variants are
available, these are as follows:
• short reach 1310 nm (application code S-1.1)
• long reach 1310 nm (application code L-1.1) (TN-1C only)
• long reach 1550 nm (application code L-1.2) (TN-1C only)
The short reach 1310 nm (application code S-1.1) optical interface is as

follows:
Output power: –8 dBm (maximum)
–11.5 dB (nominal)
–15 dBm (minimum) 7
Receiver sensitivity: –28 dBm
Receiver overload: 0 dBm
Optical path penalty: 1 dB
Section loss: 0 dB to 12 dB (TN-1C/TN-1P to TN-1C/TN-1P)
Wavelength (nominal): 1310 nm
Operating wavelength 1270 nm to 1350 nm
range:
Fibre type: monomode

The long reach 1310 nm (application code L-1.1) optical interface is as

follows:
Output power: 0 dBm maximum
–2 dBm nominal
–5 dBm minimum
Receiver sensitivity: –34 dBm (at BER of 10-10)
Receiver overload: -3dBm
Section loss: 3 dB to 28 dB (TN-1C to TN-1C)
Operating wavelength 1280 nm to 1335 nm
range:
Fibre type: monomode
The long reach 1550 nm (application code L-1.2) optical interface is as

follows:
Output power: 0 dBm maximum
–2 dBm nominal
–5 dBm minimum
Receiver sensitivity: –34 dBm (at BER of 10 -10)
Receiver overload: -3dBm
Section loss: 3 dB to 28 dB (TN-1C to TN-1C)
Operating wavelength range: 1530 nm to 1570 nm
Fibre type: monomode shifted

2 Mbit/s external synchronisation input

The 2 Mbit/s external synchronisation input (TN-1C and TN-1P ADM card
upgrades only) conforms to ITU-T recommendation G.703 and to ETS 300
166 as follows:
Line rate: HDB3
Output pulse height: ±2.37 V ± 10% (75 Ω) peak
Nominal pulse 244 ns
width:
typically: 280 m using 3002 cable
Input return loss: not less than 12 dB (50 kHz to 100 kHz)
Output return loss: not less than 6 dB (51.2 kHz to 102.4 kHz)
Craft Access Terminal interface

A simple asynchronous start-stop protocol, using RS-232C compliant signals,
are presented on a 9-pin D-type connector. On the TN-1PH the Craft Access
Terminal (CAT) can be switched to any one of the 12 multiplexer units.
7
The CAT is defined as a data termination equipment (DTE) and the
multiplexer is defined as a data communication equipment (DCE):
Baud rate: 19200 bit/s

Protocol: asynchronous start/stop
Word structure: 8 data bits, no parity, 1 stop bit (8N1)
Flow control: none
LAN interface
A standard 10BaseT LAN interface conforming to IEEE802.3 is used in the
TN-1C and TN-1PH and TN-1P ADM card upgrades.

ATU interface
TN-1C Release 1 and 2, TN-1C single-slot, and TN-1P hardware is equipped
with an RS232C interface presented on a 9-pin D-type connector, that
provides standard connection to telemetry equipment. The TN-1C and TN-1P
are defined as data communications equipment (DCE). The RS-232 interface
on the TN-1PH is a 25-way D-type connector.
TN-1C Release 3 (onwards) hardware is equipped with a point-to-multipoint

RS-485 interface presented on a 5-way terminal block that provides standard
connection to telemetry equipment. The TN-1C is a data terminal equipment
(DTE).
Baud rate: 1200, 2400, 4800, 9600, 19200 bit/s

Protocol: asynchronous start/stop
Word structure: 8 data bits, no parity, 1 stop bit (8N1)
Flow control: none
External alarms
TN-1C and TN-1P
Eight earth-free inputs and four dry-contact outputs (presented on a 25-way
D-type female connector), with the following characteristics:
Inputs: LS TTL with internal pull-up resistor, activated by
connecting the alarm lead to the alarm common via a
low resistance.
Alarm set: Contact closed, leakage current less than 10 mA at
5 V.
Alarm cleared: Contact open, residual voltage less than 0.5 V at
1 mA.
Outputs Dry-contact relays
Alarm set: Resistance between the leads less than 500 W.
Alarm cleared: Resistance between the leads greater than 100 kW.
Maximum permissible voltage: –60 V (open circuit).
Maximum permissible current: 35 mA (closed circuit).
TN-1PH:
Alarm set: Short circuit to rack power supply feed earth.
Alarm cleared: Open circuit
Resistance to earth: 25 MΩ (open circuit).
Voltage limits: -12 V to +20 V.

Power Supply Unit (TN-1C and standard TN-1P only)

A.C. supply
Voltage: 230 V +10% –18% at 50 Hz (189 V to 253 V)

115 V +14% –15% at 60 Hz (97.75 V to 131.1 V)
D.C. output
–24 V d.c. nominal, 4.5 A maximum
Fuses
a.c. 2.5 A
d.c. 7.5 A
Power consumption
42 W nominal (battery charged)
125 W maximum (for less than 5 minutes, battery discharged).
Power dissipation
25 W maximum (battery charging from fully discharged state)
Recommended battery replacement period

Replace at intervals recommended by the battery supplier, if no information is
available, Nortel Networks recommend that batteries are replaced every four
years.
Alarm outputs
BLV
(Battery Low Voltage):
Set if battery voltage falls below 21 V ± 0.5 V 7
LPF Set if the charger output d.c. voltage falls
(Line Power Fail): below 26.2 V ± 0.5 V
Door Open Alarm: Set if the PSU door is open.
end of chapter

8-1
External interfaces 8-
The external electrical connections to the TN-1C, TN-1P and TN-1PH are
made via their internal connector panels, see Figure 8-1 to Figure 8-7.
The external electrical connections to the TN-1P Basestation are made via the
integral front panel connection panel see Figure 8-9. The front panel
connectors are extended from their equivalent rear panel connectors via
extension cables. Additional external electrical connections to the TN-1P
Basestation are accessible (if used) via its internal connector panel, see
Figure 8-8.
Note 1: For details of the optional router card external electrical

connections, refer to the OPTera Packet Edge 10 User Guide
323-1043-401.
STM-1 optical connectors are mounted directly on the TN-1C and TN-1P
main multiplexer card.
• Standard connectors are used for all external connectors. The TN-1C,
TN-1P, TN-1PH and TN-1P Basestation have the following interfaces:
• 2 Mbit/s 75 Ω tributaries
— Coaxial connectors, type 43
• 2 Mbit/s 120 Ω tributaries
— 25-way, D-type
8
• 34/45 Mbit/s 75 Ω tributaries (TN-1C only)
— Coaxial connectors, type 43
• STM-1 aggregates
— FC/PC connectors
• Craft access terminal (CAT) interface
— 9-way, D-type
• External alarm input/output interface
— 25-way, D-type (TN-1C and TN-1P only)
— 15-way, D-type (TN-1PH only)
• Power and power alarm interface
— 9-pin ‘Mate-n-lock’ connector (TN-1C and TN-1P only)

8-2 External interfaces
— 6-pin ‘Mate-n-lock’ connector (TN-1PH only)

• Local area network (LAN) interface
— RJ45 socket (10BaseT) (TN-1C, TN-1PH and TN-1P ADM card
upgrades only)
• Asynchronous telemetry unit (ATU) interface
— 9-way, D-type (TN-1C Release 1 and TN-1P)
— RJ485 5-way, WAGO-type connector (TN-1C Release 3 onwards)
— 25-way D-type (TN-1PH only)
• External synchronisation input
— Coaxial connector, type 43 (TN-1C and TN-1P ADM card upgrades
only)
For detailed information on connector types, part numbers, and connections,

refer to ‘Installation Procedures’, 323-1081-200.

Figure 8-1
TN-1C connection panel (8 x 2 Mbit/s + 34/45 Mbit/s version) Release 1 hardware
The earth connection of the

tributary is set using a physical
d.c.
link. Here the link is set to the a.c.
option. a.c.
Tx1 Rx1 Lk 1
Fan
connector Tx2 Rx2
Tx3 Rx3
Alarms
Tx4 Rx4
2 Mbit/s 75 Ω
Tx5 Rx5
tributary connectors
8x2 Mbit/s ADM card
2 Mbit/s120 Ω Tx6 Rx6
(Tx) 8x2 Mbit/s Tx7 Rx7
ADM card
Tx8 Rx8
75 Ω a.c./d.c.
2 Mbit/s 120 Ω tributary Tx1 Rx1 selector links
connectors (Rx)
34/45 Mbit/s tributary
8x2 Mbit/s ADM card Tx2 Rx2 connectors, requires
extension card
8
Telemetry B (not
supported at this
release)
CAT Telemetry A
(ATU)
LAN On/off
switch
d.c./alarms Microswitch
input (door alarm)
Fuse

Figure 8-2
TN-1C connection panel (8 x 2 Mbit/s + 2 x 34/45 Mbit/s version) Release 3/5 hardware
The earth connection of the tributary is set using a

physical link. Here the link is set to the a.c. option. DC
Tx1 Rx1
Fan
AC
connector
Tx2 Rx2 LK1
Fuse
Tx3 Rx3 75 Ω a.c./d.c.

selector links
Tx4 Rx4
Alarms
Tx5 Rx5
2 Mbit/s 75 Ω
Tx6 Rx6 8x2 Mbit/s ADM card
2 Mbit/s 120 Ω Tx7 Rx7

(Tx)
Tx8 Rx8
8x2 Mbit/s ADM card
External
OUTPUT INPUT synchronization
connectors (only input
2 Mbit/s 120 Ω currently supported)
tributary connectors Tx1 Rx1
(Rx) 34/45 Mbit/s tributary
8x2 Mbit/s ADM Tx2 Rx2 connectors, requires
card extension card
CAT Auxiliary telemetry

(not currently
supported)
LAN ATU
Microswitch
d.c./alarms (door alarm)
PWR DOOR
SYS DOOR
input
d.c. filter Circuit breaker

SYS DOOR
PWR DOOR
The TN-1C and PSU door alarms are enabled

or disabled using physical links. Here the SYS
NORMAL
NORMAL
SHORT
SHORT
DOOR link (TN-1C) is set to the NORMAL

option enabling the NE-Door_Open alarm. The
PWR DOOR link (PSU) is set to the SHORT
option disabling the PS-Door_Open alarm.

Figure 8-3
TN-1C connection panel (16 x 2 Mbit/s version) Release 1 hardware

d.c.
link. Here the link is set to the
a.c. option. a.c.
Lk 1
Fan connector Tx1 Rx1
LAN Tx2 Rx2

Fuse A
B
Tx3 Rx3
Telemetry A: ATU
Telemetry B,C,D: Tx4 Rx4
not supported in 2 Mbit/s tributary
this release connectors (75Ω)
Tx5 Rx5
8x2 Mbit/s ADM
D
Tx6 Rx6
card
2 Mbit/s tributary
connectors (120Ω) Tx7 Rx7
8x2 Mbit/s ADM
card Tx8 Rx8
Rx
Tx
Tx1 Rx1
2 Mbit/s tributary
connectors (120Ω) Tx2 Rx2
requires extension
card Tx3 Rx3
8
34/45 Mbit/s tributary Tx1 Rx1 Tx4 Rx4
connectors (120Ω)
2 Mbit/s tributary
requires extension
Tx2 Rx2 Tx5 Rx5 connectors (75Ω)
card
requires
External alarms Tx6 Rx6 extension card
CAT
Tx7 Rx7
Fuse
Tx8 Rx8
d.c. alarms input
On/off switch

Figure 8-4
TN-1C connection panel (16 x 2 Mbit/s version) Release 3/5 hardware
The earth connection of the tributary is set using a

d.c.
physical link. Here the link is set to the a.c. option.
Fan connector Tx1 Rx1
LAN a.c.
Tx2 Rx2
Fuse
Auxiliary telemetry
(not currently Tx3 Rx3
supported)
Tx4 Rx4
Alarms
2 Mbit/s tributary
connectors
Tx5 Rx5
(75 Ω)
CAT
8x2 Mbit/s ADM
Tx6 Rx6 card
2 Mbit/s tributary
connectors (120 Ω) Tx7 Rx7
8x2 Mbit/s ADM
card
Tx8 Rx8
Tx
Rx
Tx9 Rx9
2 Mbit/s tributary
connectors (120 Ω)
requires extension Tx10 Rx10
card
34/45 Mbit/s Tx11 Rx11
tributary 2 Mbit/s tributary
connectors connectors
requires Tx1 Rx1 INPUT Tx12 Rx12 (75 Ω)
extension card requires
Tx2 Rx2 OUTPUT Tx13 Rx13 extension card
External
synchronization
connectors (only Tx14 Rx14
input currently
supported) ATU
Tx15 Rx15
POWER
DOOR
d.c./alarms input
d.c. filter Circuit breaker
Tx16 Rx16
POWER DOOR
NORMAL
SHORT
The PSU door alarm is enabled or disabled using a

physical link. Here the POWER DOOR link is set to the
NORMAL option enabling the PS-Door_Open alarm.
Note: Although sufficient physical connectors are available for sixteen (75 or
120 Ω) 2 Mbit/s and two 34/45 (75 Ω only) Mbit/s tributaries, these cannot be
operated. Allowable configurations are sixteen 2 Mbit/s tributaries or eight 2 Mbit/s
and one or two 34/45 Mbit/s tributaries.

Figure 8-5
TN-1C connection panel (32 x 2 Mbit/s version) Release 5.1 hardware
Fan A LAN
connector
Alarms
Auxiliary telemetry
(not currently supported) External synchronisation
SYNC in SYNC out
connectors (output not
Interna calibration- supported)
manufacturing aid only.
(Not used) CAL DC
CAT
ATU
AC
Mounting position of Connector for upper (second)
optional 8 x 75 Ω Optional 75 Ω Interface Card
Interface Card
TX 120 Ω (17-24)
2 Mbit/s tributary
RX 120 Ω (17-24)
(requires extension card)
TX 120 Ω (9-16)
The earth
RX 120 Ω (9-16) connection of the
34/45 Mbit/s tributary tributary is set
DC
connectors requires using a physical
TX RX link. Here the link
extension card (two
pairs) is set to the a.c.
AC option.
TX RX
Connector for lower (first)
Fuse Optional 75 Ω Interface Card
F1
TX 120 Ω (25-32)
2 Mbit/s tributary
8
RX 120 Ω (25-32) (requires extension card for
more than 8 x 2 Mbit/s)
TX 120 Ω (1-8)
POWER DOOR
RX 120 Ω (1-8)
Norm
(See SHORT
Note)
d.c filter
Microswitch
Short
NORMAL
(door alarm)
Circuit breaker
Fan B
(not used) d.c./alarms input
Note: The PSU door alarm is enabled or disabled using a physical link. Here the
POWER DOOR link is set to the NORMAL option enabling the PS-Door_Open alarm.

Figure 8-6
TN-1C optional 75 Ω interface cards for Release 5.1 hardware
Mounting 75 Ω a.c./d.c. selector links.

position of The earth connection of the
optional tributary is set using a
8 x 75 Ω physical link. Here the link is
Mounting connector
Interface Cards set to the a.c. option.
(right-hand half only)
d.c.
PORT LAYOUT DIFFERS
FROM PREVIOUS RELEASES
a.c.
TX8 RX8
TX 120 Ω (17-24)
TX7 RX7
TX6 RX6 Second (optional) card

RX 120 Ω (17-24) fits over remaining four
TX5 RX5 120 Ω connectors
(covers 34/45 Mbit/s
TX 120 Ω (9-16) TX4 RX4 connectors)
Note: The numbering
TX3 RX3 convention (at Release
RX 120 Ω (9-16) 5.1) for additional
TX2 RX2
tributary port
TX RX connections is right
TX1 RX1
(bottom) to left (top).
TX RX
F1
TX8 RX8
TX7 RX7
TX 120 Ω (25-32)
TX6 RX6 First (optional) card fits
over four 120 Ω
RX 120 Ω (25-32) TX5 RX5 connectors (leaving 34/45
Mbit/s connectors
TX4 RX4 revealed)
TX 120 Ω (1-8) Note: The numbering
TX3 RX3 convention (at Release
TX2 RX2 5.1) for additional tributary
RX 120 Ω (1-8) port connections is right
TX1 RX1 (bottom) to left (top).
16 Type 43 75 Ω tributary
connectors (8 Pairs)
Note:
With no optional 75 Ω Interface Cards fitted:
– up to 16 or 32 120 Ω 2 Mbit/s interfaces are available, or
– up to 16 or 32 120 Ω 2 Mbit/s interfaces and one or two 34/45 Mbit/s interfaces are available.
With one optional 75 Ω Interface Card fitted:
– up to 8 75 Ω 2 Mbit/s interfaces and up to 16 120 Ω 2 Mbit/s interfaces are available, or
– up to 8 75 Ω or 120 Ω 2 Mbit/s interfaces and one or two 34/45 Mbit/s interfaces are available.
With two optional 75 Ω Interface Cards fitted up to 16 75 Ω 2 Mbit/s interfaces are available.

Figure 8-7
TN-1P connection panel (4 x 2 Mbit/s) Release 5 hardware
Tx1 Rx1
Not used
Tx2 Rx2
2 Mbit/s tributary
connectors
Tx3 Rx3 (75 Ω)
External alarms
connector
Tx4 Rx4
75 Ω a.c./d.c.
selector links
120 Ω tributary
connnectors (Tx)
120 Ω a.c./d.c.
selector link
120 Ω tributary
connnectors (Rx)
Not used
8
Craft Access
ATU connector Terminal
On/off switch
Microswitch
d.c./alarms input (door alarm)
Fuse

Figure 8-8
TN-1P (Release 5.1 hardware), TN-1P Basestation, and TN-1C single-slot connection panel
(8 x 2 Mbit/s)
Fan connector LAN

(see Note 1)
TX
TX1
Alarms link. Here the link is set to the
a.c. option.
d.c.
External
EXT SYNC
IN OUT
synchronisation
connectors (see a.c.
Note 1) TX8
Fuse 75 Ω
tributary
RX
120 Ω connectors
RX1
Tributaries
(Tx)
CAL
Internal calibration
(manufacturing aid only)
120 Ω
Tributaries Physical link, for equipment
RX8
(Rx)) identification purposes.

Note: Default, factory setting is
CAT/P
CAT/P SHORT
CAT/C
Craft access Telemetry

terminal (CAT), see Note 2. (ATU)
NORM
The PSU door alarm is enabled SHORT PWR DOOR

PWR DOOR
or disabled using a physical link.

Here the POWER DOOR link is DC/alarms input
set to the NORMAL option
enabling the PS-Door_Open ‘Lump Plug’ for low voltage
alarm. NORMAL –24 V d.c. connection.
Note: Normally set to ’short’. Provides connection to an
a.c./d.c. rectifier
DC filter (currently not used).
Circuit breaker
Note 1: TN-1P and TN-1P Basestation fitted with an 8 x 2 Mbit/s ADM card support LAN and External synchronisation input.
Note 2: The TN-1P Basestation has front access for eight 75 Ω BNC pairs, CAT and Power connectors only (linked to
the front connector panel via terminated extension cables).

Figure 8-9
TN-1P Basestation (integral front panel connectors)
Front View
Craft Access
Terminal (CAT)
Only used if Power Connector
2 Mbit/s Multiplexer is Wrist strap
75 Ω Tributary upgraded earthing point
Interfaces (to 8 x 2 Mbit/s)
TX1 TX2 TX3 TX4 TX1 TX2 TX3 TX4 CAT POWER
RX1 RX2 RX3 RX4 RX1 RX2 RX3 RX4
TxA RxA TxB RxB

Multiplexer
Used for 1 +1
Optical Interface Connectors protected variant

Figure 8-10
TN-1PH connector panel
POWER
2Mbit 75 Ω TRANSMIT
RAU
2 ALARMS
RS-232
4
TELEMETRY
1-6 7-12
1
2Mbit 75 Ω RECEIVE
3
LAN
SHELF SYSTEM
4
Tx 1 Rx Tx 2 Rx Tx 3 Rx Tx 4 Rx Tx 5 Rx Tx 6 Rx Tx 7 Rx Tx 8 Rx Tx 9 Rx Tx10Rx Tx11Rx Tx12Rx

2Mbit 120 Ω
DC AC

D-type connectors
The TN-1C and TN-1P external interface D-type connectors follow standard
pin numbering as shown in Figure 8-11.
Figure 8-11
Standard pin numbering for D-type connectors
1 13 13 1
14 25 25 14
25-way D-type male 25-way D-type female

Connectors are shown looking from the outside into the shell
2 Mbit/s 75 Ω tributary interfaces

The 2 Mbit/s 75 Ω tributary interfaces use type 43 connectors to connect
coaxial cables. Two connectors are used for each interface (receive and
transmit).
Links
Transmit connectors - the shield is short circuited to the earth (d.c. coupled)
Receive connectors - the shield connection to the earth is selectable by a link

giving the following options:
• d.c. coupled (short circuit)
• a.c. coupled (connected via an isolating capacitor)
CAUTION
Risk if operational problems.
Do not remove or reposition links without referring to Nortel
Networks engineers.
8
2 Mbit/s 120 Ω tributary interfaces
Two (or four in a 16 x 2 Mbit/s system) (or eight in a 32 x 2 Mbit/s system)
25-pin D-type connectors are used to carry the output and input 8 x 2 Mbit/s
(or 16 x 2 Mbit/s) (or 32 x 2 Mbit/s) tributaries. The input connectors are
male, while the output connectors are female.

Table 8-1
2 Mbit/s 120 Ω connector tributary allocation
Tributary number Pin number
main with 8 x 2 Mbit/s with with

ADM card or 24 x2 Mbit/s 24 x 2 Mbit/s 24 x 2 Mbit/s
extension card extension card extension card
1 9 17 25 9 & 22
2 10 18 26 12 & 25
3 11 19 27 11 & 23
4 12 20 28 8 & 20
5 13 21 29 6 & 19
6 14 22 30 5 & 17
7 15 23 31 2 & 14
8 16 24 32 3 & 16
See note 1,4,7,10,13,15

,18,21,24
Note: Some of these pins are routed to the extension slot for future support.
34/45 Mbit/s tributary interfaces (TN-1C only)

The two 34/45 Mbit/s 75 Ω tributary interfaces use Type 43 connectors to
connect to coaxial cables. Two connectors are used for each (receive and
transmit).
Links
Transmit connectors - the shield is short circuited to the earth (d.c. coupled)

CAUTION
Risk of operational problems
Do not remove or reposition links without consulting Nortel
Networks engineers.

Optical interfaces
The STM-1 optical interface is via standard FC-PC connectors mounted
directly on the TN-1C or TN-1P multiplexer circuit board. The TN-1C or
TN-1P (if 1+1 protected) is equipped with two electro-optical modules and
four FC-PC connectors, i.e. two transmit connections and two receive
connections.
The optical connectors are arranged vertically as follows:

TxA
RxA
TxB
RxB
Craft access terminal interface

The TN-1C Craft Access Terminal (CAT) port is an RS-232C interface using
a 9-way D-type connector and provides for a standard connection to a CAT.
The CAT is defined as a data termination equipment (DTE), while the TN-1C
is defined as a data communication equipment (DCE). The pin assignments of
the CAT are shown in Table 8-2.
Table 8-2
Craft access terminal connector pin assignments
CAT (9 way female D-type)
Pin Signal Function Signal

No. name direction
1 not used
5
9 2 RxD Received data output from To CAT
TN-1C
6
1
3 TxD Transmit data from terminal to
TN-1C
From CAT
8
4 not used
5 Common Signal Common Bidirectional
6 not used
7 RTS Request to send From CAT
8 CTS Clear to send To CAT
9 not used

ATU interface (TN-1C Release 1 and 2 and TN-1C single-slot hardware and
TN-1P)
The ATU interface is an RS232C interface using a 9-way female D-type with
‘screw on’ locking capability that provides standard connection to telemetry
equipment. The pin-out is shown in Table 8-3.
Table 8-3
TN-1C ATU interface connector pin-out
Telemetry (9 way female D-type)
Pin Signal Description Direction

name
1 not used
5
9 2 RxD Receive data output from TN-1C from TN-1C/TN-1P
6
1
3 TxD Transmit data to TN-1C to TN-1C/TN-1P
4 not used
5 Common Signal Common bi-directional
6 not used
7 RTS Request to send to TN-1C/TN-1P
8 CTS Clear to send from TN-1C/TN-1P
9 not used
ATU interface TN-1C (Release 3/5/5.1 hardware)

The ATU interface is an RS-485 interface using a 5-way terminal block. The
pin-out is shown in Table 8-4.
Table 8-4
TN-1C ATU interface connector pin-out
ATU interface (5-way terminal block)
Pin Signal Description Direction

Wire name
receptacles
5 GND Ground
5
4 4 TxA Transmit data A to TN-1C to TN-1C
3
2
1 3 TxB Transmit data B to TN-1C to TN-1C
2 RxA Receive data A from TN-1C from TN-1C

Release
levers
1 RxB Receive data B from TN-1C from TN-1C

TN-1P Headend
The ATU interface is an RS232C interface using two 25-way female D-type
connectors (female) with ‘screw on’ locking capability that provides standard
connection to telemetry equipment. The pin-out is shown in Table 8-5.
Table 8-5
TN-1PH ATU interface connector pin-out
Telemetry (25 way female D-types)

Pin Function Direction Connector Connector
1 2
1 TxD To TN-1P MPP #1 MPP #7
1 2 RxD From TN-1P
14
3 RTS To TN-1P
4 CTS From TN-1P
6 RxD From TN-1P
25
13
7 RTS To TN-1P
8 CTS From TN-1P
10 RxD From TN-1P
11 RTS To TN-1P
12 CTS From TN-1P
13 Common
15 RxD From TN-1P 8
16 RTS To TN-1P
17 CTS From TN-1P
19 RxD From TN-1P
20 RTS To TN-1P
21 CTS From TN-1P
23 RxD From TN-1P
24 RTS To TN-1P
25 CTS From TN-1P

Fan interface (TN-1C and TN-1P Release 5.1 hardware)

The fan interface is a 6-pin male ‘Mate-n-Lock’ mounted on the connection
panel. As stated in Table 8-6, pins 3 and 6 must be linked on the fan
connector.
Table 8-6
Fan connector pin assignment
Fan (6 way male ‘Mate-n-Lock’)
Pin Signal name Description

No.
1 FAN_V+ +V to the fan
2 not connected not connected

3 2 1
3 GND Link to pin 6
6 5 4 4 FAN_V- -V to the fan
5 FAN_CON_IN FAN control
6 FAN_IN (Link to pin 3) FAN connected
2 Mbit/s external synchronisation input

The 2 Mbit/s 75 Ω external synchronisation input (TN-1C and TN-1P ADM
card upgrades only) uses a type 43 connector to connect to the coaxial cable.
Note: The external synchronisation output is not used in current systems.
Links
CAUTION
Risk if operational problems.
Do not remove or reposition links without referring to Nortel
Networks engineers.

External alarm interface

The external alarm interface uses a 25-way D-type connector with ‘screw-on’
locking capability. The pin assignments for TN-1C and TN-1P are shown in
Table 8-7. The pin assignments for TN-1PH are shown in Table 8-8.
Table 8-7
Pin assignments of the external alarm interface (TN-1C and TN-1P)
External alarms (25 way female D-type)
Pin Function
1 Alarm I/P 1
13 2 Alarm I/P 2
25
3 Alarm I/P 3
4 Alarm I/P 4
5 Alarm common
6 not connected
7 Alarm O/P 1+ (see note)
14
1 8 not connected
9 Alarm O/P 2+ (see note)
10 not connected
(-48 V Release 3 hardware only)
11 Alarm O/P 3 + (see note)
12 not connected
13 Alarm O/P 4 + (see note)
14 Alarm I/P 5
15 Alarm I/P 6
16 Alarm I/P 7
17 Alarm I/P 8
18 not connected
(0 V Release 3 hardware only)
8
19 Alarm O/P 1 – (see note)
20 not connected
22 not connected
24 not connected
Note: When the rack alarms mode is selected, the following alarms are designated:
Alarm O/P 1 — Prompt/Deferred
Alarm O/P 2 — In Station
Alarm O/P 3 — REC ATT
Alarm O/P 4 — Fault Clear

Table 8-8
Rack alarms connector pin-out (TN-1PH)
Pin Function
1 –12 V
8 15 2 Prompt alarm
3 not used
1 9
4 In Station alarm
5 reserved
6 –48RTN
7 –48RTN
8 –48RTN
9 reserved
10 Receive Attention
11 not used
12 Fault Clear
13 reserved
14 –48RTN
15 –48RTN

Power and power alarm interface

Power is supplied to the TN-1C and TN-1P via a 9-way male ‘Mate-n-Lock’
power connector. The pin assignments are shown in Table 8-9. The d.c. power
feed to the TN-1C or TN-1P system (Release 1 and 2 hardware only) is
enabled by a on/off switch on the connector panel. The switch is accessible
after removal of the TN-1C or TN-1P cover. The pin assignments for the
TN-1PH are shown in Table 8-10.
D.C. power feed to Release 3 hardware is enabled through a circuit breaker.

The circuit breaker is also accessible after removal of the TN-1C cover.
Table 8-9
D.C./alarm connector pin assignment (TN-1C and TN-1P)
TN-1C and PSU (9 way male ‘Mate-n-Lock’)
Pin No. Name Function
1 VS RTN d.c. return
2 BLV PS-Battery_Low_Volta
9 6 3 ge
3 LPF PS-Power_Fail
8 5 2
4 ALGND Alarm earth/common
7 4 1
5 VS Minus d.c. feed power –20 V
to -72 V
6 Shield Shielding
7 — not used
8 — not used
9 DR_ALRM_PWR PS-Door_Open 8
Table 8-10
D.C. connector assignment (TN-1PH)
6 way male ‘Mate-n-Lock’ Pin Function

(positronix PLB06M900A1)
1 –48RTN
2 –48V
3 6
2 5 3 Shield (not connected)
1 4 4 not connected
5 not connected
6 Shield (not connected)

LAN interface
For the TN-1C, TN-1PH and TN-1P ADM card upgrades, an external
10BaseT LAN interface (as defined in IEEE802.3) is provided for connection
of the element controller EC-1. For the TN-1PH, two RJ45 LAN connectors
are provided (see Figure 8-10). Use the connector labelled ‘SYSTEM’.
Note: The connector labelled ‘SHELF’ is reserved for future use.
The LAN connector pinout is shown in Table 8-11.
Table 8-11
LAN connector pin assignments (TN-1C, TN-1PH and TN-1P ADM card
upgrades)
RJ45 Plug (10BaseT)
Pin No. Function
1 LAN output +
2 LAN output –
3 LAN input +
1 2 3 4 5 6 7 8
4 not connected
5 not connected
6 LAN input –
7 not connected
8 not connected

Rack alarm adaptor

The rack alarm adaptor (rack alarm adaptor to TN-1C and standard TN-1P)
uses a 25-way male D-type connector with ‘screw-on’ locking capability. The
pin assignments are shown in Table 8-12.
Table 8-12
Pin assignments of the rack alarm adaptor
External Alarms Interface (25 way male D-type)
Pin Function
1 not used
13 2 not used
25
3 not used
4 not used
5 Alarm common
6 not used
14 7 EAOut_1+
1
8 not used
9 EAOut_2+
10 –48 V RAA supply (from rack)
11 EAOut_3+
12 not used
13 EAOut_4+
14 not used
15 not used
16 not used
17 EAIn_8
18 Ground (return to rack) 8
19 EAOut_1–
20 not used
21 EAOut_2–
22 not used
23 EAOut_3–
24 not used
25 EAOut_4–
Note: When the rack alarms mode is selected, the following alarms are designated:
Alarm O/P 1 — Prompt/Deferred
Alarm O/P 2 — In Station
Alarm O/P 3 — REC ATT
Alarm O/P 4 — Fault Clear

Rack alarm bus connector

The rack alarm bus connector (rack alarm adapter to rack alarm bus) uses a
15-way male D-type connector. The pin assignments are shown in Table 8-13.
Table 8-13
Pin assignments of the rack alarm bus connector
Pin No. Description
1 –12 V
2 Prompt alarm
3 not used
4 In station alarm
5 not used
6 0V
7 0V
8 0V
9 not used
10 Receive attention
11 not used
12 Fault clear
13 –48 V (optional)
14 0V
15 0V
Fuses
TN-1C Release 1 and 2 and TN-1P Release 5 hardware have the following
fuses mounted on the connection panel:
3.5 A
0.125 A
TN-1C (Release 3/5/5.1 hardware), TN-1P (Release 5.1 hardware), TN-1P

Basestation (Release 5/5.1 hardware), and the single-slot TN-1C has the
following mounted on the connection panel:
0.125 A fuse
Circuit breaker
end of chapter

9-1
Ordering codes 9-
TN-1C only
Each item has a unique eight character alphanumeric code.
Table 9-1 lists the main equipment versions for wall and rack mounted TN-1C
applications. Table 9-2 to Table 9-5 lists the main units required for TN-1C
applications. Table 9-14 details the Power Supply Unit and cables.
The software required to run the TN-1C, TN-1P and CAT is detailed in
Table 9-15. The rack mounting kit is detailed in Table 9-16.
Table 9-19 lists obsolete codes (cannot be ordered) that are supported by the
Release 5.2 software.
Note 1: A dummy card must be ordered with each unequipped unit, to

comply with electro-magnetic compatibility (EMC) requirements.
Note 2: For 75 Ω operation with TN-1C Release 5.1 hardware, you must
order the relevant number of 75 Ω I/O adaptors (see Table 9-5).
Note 3: For information on ordering the optional Packet Edge 10 router
card, refer to the OPTera Packet Edge 10 User Guide
323-1043-401.
Table 9-1
TN-1C versions (Release 5.1 hardware)
Version Ordering code

All the units in this table are supplied in a plastic case and are upgradeable with an extension card to
provide 32x2 Mbit/s tributaries, up to two 34/45 Mbit/s tributaries, or a Packet Edge 10 router.
9
TN-1C 8x2 ADM & Dummy card (S-1.1 optics) NTFT52CA+NTFT32AA
TN-1C 8x2 ADM & Dummy card (L-1.1 optics) NTFT52CD+NTFT32AA
TN-1C 8x2 ADM & Dummy card (L-1.2 optics) NTFT52CG+NTFT32AA
TN-1C 8x2 ADM & 1x34/45 extension card (S-1.1 optics) NTFT52CA+NTFT31AC
TN-1C 8x2 ADM & 1x34/45 extension card (L-1.1 optics) NTFT52CD+NTFT31AC
TN-1C 8x2 ADM & 1x34/45 extension card (L-1.2 optics) NTFT52CG+NTFT31AC
TN-1C 8x2 ADM & 2x34/45 extension card (S-1.1 optics) NTFT52CA+NTFT31AD
TN-1C 8x2 ADM & 2x34/45 extension card (L-1.1 optics) NTFT52CD+NTFT31AD
TN-1C 8x2 ADM & 2x34/45 extension card (L-1.2 optics) NTFT52CG+NTFT31AD
—continued—

9-2 Ordering codes
Table 9-1
TN-1C versions (Release 5.1 hardware) (continued)
TN-1C 16x2 (8x2 ADM & 8 x 2 Mbit/s extension card) (S-1.1 optics) NTFT52CA+NTFT08AC
TN-1C 16x2 (8x2 ADM & 8 x 2 Mbit/s extension card) (L-1.1 optics) NTFT52CD+NTFT08AC
TN-1C 16x2 (8x2 ADM 8 x 2 Mbit/s extension card) (L-1.2 optics) NTFT52CG+NTFT08AC
TN-1C 32x2 (8x2 ADM & 24x2 extension card) (S-1.1 optics) NTFT52CA+NTFT24BA
TN-1C 32x2 (8x2 ADM & 24x2 extension card) (L-1.1 optics) NTFT52CD+NTFT24BA
TN-1C 32x2 (8x2 ADM & 24x2 extension card) (L-1.2 optics) NTFT52CG+NTFT24BA
Note 1: A TN-1C PSU (Table 9-14) or a customer supplied d.c. supply is required unless the TN-1C is
rack mounted and using the rack power supply.
Note 2: If the units are to be rack mounted, then a rack mounting kit (Table 9-16) is required.
Note 3: For 75 Ω operation on TN-1C Release 5.1 hardware, you must also order the relevant number
of 75 Ω I/O adaptors. Order 1 adaptor (NTFT09AA) for 8x2 Mbit/s 75 Ω configurations or 2 adaptors
(NTFT09AA) for 16x2 Mbit/s 75 Ω configurations. See Table 9-5 for details.
Table 9-2
TN-1C multiplexers (Release 5.1 hardware)

8 x 2 Mbit/s ADM card with short range 1310 nm optics NTFT02BA
8 x 2 Mbit/s ADM card with long range 1310 nm optics NTFT02BB

8 x 2 Mbit/s ADM card with long range 1550 nm optics NTFT02BC
Table 9-3
TN-1C extension cards (Release 5.1 hardware)
Dummy card NTFT32AA
1x34/45 extension card NTFT31AC

2x34/45 extension card NTFT31AD
8 x 2 Mbit/s extension card NTFT08AC

24 x 2 Mbit/s extension card NTFT24BA
Table 9-4
TN-1C single-slot (Release 5.1 hardware)
TN-1C single slot with 1310 nm ADM pack NTFT51CD
TN-1C single slot with 1310 nm LH ADM pack NTFT51CE
TN-1C single slot with 1550 nm LH ADM pack NTFT51CF

Ordering codes 9-3
Table 9-5
TN-1C additional items (Release 5.1 hardware)
Item Ordering code
Dual fan kit NTFT06GA

75 Ω I/O adapter (8 x 2) (see Note) NTFT09AA
Note: For 75 Ω operation on TN-1C Release 5.1 hardware, order 1 adaptor for 8x2 Mbit/s
configurations or 2 adaptors for 16x2 Mbit/s configurations.
TN-1P only
Table 9-6 and Table 9-7 list the main units required for protected and
unprotected wall and rack-mounted TN-1P applications.
Table 9-8 lists the main units required for TN-1P protected and unprotected
headend applications.
Table 9-9 to Table 9-11 list the main units required for TN-1P protected and
unprotected Basestation applications.
The software required to run the TN-1P and CAT is detailed in Table 9-15.
The rack mounting kit is detailed in Table 9-16.
Table 9-6
Unprotected TN-1P
Item Code
TN-1P Release 5.1 NTFT51CA
Note 1: Requires TN-1P PSU (Table 9-14) or a customer supplied d.c. supply.
Note 2: Requires Rack mounting kit (Table 9-15) if rack mounted.
Table 9-7
1+1 protected TN-1P
Item Code
TN-1P (1+1) Release 5.1 NTFT51CB 9
Note 1: Requires TN-1P PSU (Table 9-14) or a customer supplied d.c. supply.
Note 2: Requires Rack mounting kit (Table 9-15) if rack mounted.

9-4 Ordering codes
Table 9-8
TN-1P headend equipment
Item Code
TN-1P Subrack Release 5.1 NTFT07AA

Comprising:Subrack End Processor NTFT10AA
CAP NTFT1302
Backplane NTFT07AD
Cable (CAP to Backplane) TLFT0711
Subrack chassis
TN-1P MPP (1 to 12 as required) NTFT01JC
TN-1P (1+1) MPP (1 to 12 as required) NTFT01JF
Fibre tray NTFT07AC
Interface area cover NTFT07AB
Table 9-9
TN-1P Basestation (unprotected 4 x 2 Mbit/s)
Item Code
TN-1P Basestation (Release 5.1) NTFT51CC +NTFT01BC
Table 9-10
1+1 protected 4 x 2 Mbit/s TN-1P Basestation (1+1 protected 4 x 2 Mbit/s)
Item Code
TN-1P Basestation (Release 5.1) NTFT51CC +NTFT01BF
Table 9-11
TN-1P Basestation (8 x 2 Mbit/s ADM)
Item Code
TN-1P Basestation (Release 5.1) NTFT51CC +NTFT02BA
Table 9-12
TN-1P multiplexers
Version Code
unprotected 4 x 2 Mbit/s NTFT01BC
1+1 protected 4 x 2 Mbit/s NTFT01BF

Ordering codes 9-5
Upgrade items
Table 9-11 lists the main units required to upgrade a 4 x 2 Mbit/s TN-1P
Basestation to an 8 x 2 Mbit/s ADM with limited functionality.
Table 9-13
TN-1P Basestation (upgrade to 8 x 2 Mbit/s ADM)
Item Code
TN-1C 8x2 ADM card short range 1310 nm optics NTFT02BA
Tributary extension cable –
(8 required, for Release 5 upgrade only)
Common items
Table 9-14 to Table 9-18 list items common to the TN-1C and the
TN-1P.
Table 9-14
Power supply unit
Equipment description Ordering code
AC/DC power unit NTFT21AA
SLA battery (optional) NTFT24AA

AC cable (optional) NTFT15AB
Table 9-15
Software
Software description Ordering code
Release 5.2 software
TN-1C and TN-1P Release 5.2 S/W kit (disk and tape) NTFT81EC
TN-1C and TN-1P Release 5.2 S/W (DAT tape) NTFT92EC

TN-1C and TN-1P Release 5.2 S/W (disk) NTFT93EC
TN-1C and TN-1P Release 5.2 S/W (download from Preside, NTQJ32HE
9
DAT tape)
Table 9-16
Rack mounting kit
Rack mounting installation kit NTFT06AA
TEP-1e rack mount brackets NTFT06AD

Note: This rack mounting installation kit is to be used in conjunction with the
equipment detailed in Table 9-2.

9-6 Ordering codes
Table 9-17
Rack alarm adaptor
Rack alarm adaptor NTFT06BA
Table 9-18
Single fibre working coupler
Single fibre working coupler with tails NTKD0101

Note: The coupler is only required if single fibre working is required.
Obsolete codes
Table 9-19 lists codes that are obsolete and cannot be ordered, but are
supported by the Release 5.2 software.
Table 9-19
Obsolete codes

TN-1C (Release1/3/5 hardware)
TN-1C 8 x 2 Mbit/s ADM (Release 1) with S1.1 optics NTFT02AA

TN-1C 8 x 2 Mbit/s extension card NTFT08AB
TN-1C 1 x 34/45 Mbit/s extension card NTFT31AA
TN-1C 2 x 34/45 Mbit/s extension card NTFT31AB
TN-1C 8x2 ADM (S-1.1 optics) NTFT52BA

TN-1C 8x2 ADM (L-1.1 optics) NTFT52BK
TN-1C 8x2 ADM (L-1.2 optics) NTFT52BF
These units are supplied in a plastic case and are
upgradeable to provide up to two 34/45 Mbit/s tributaries
TN-1C 8x2 & 1x34/45M ADM (S-1.1 optics) NTFT52BC

TN-1C 8x2 & 1x34/45M ADM (L-1.1 optics) NTFT52BM
TN-1C 8x2 & 1x34/45M ADM (L-1.2 optics) NTFT52BH
These units are supplied in a plastic case and are
upgradeable to provide two 34/45 Mbit/s tributaries
TN-1C 8x2 & 2x34/45 ADM (S-1.1 optics) NTFT52BE

TN-1C 8x2 & 2x34/45 ADM (L-1.1 optics) NTFT52BO
TN-1C 8x2 & 2x34/45 ADM (L-1.2 optics) NTFT52BJ
These units are supplied in a plastic case
TN-1C 16x2 ADM (S-1.1 optics) NTFT52BB

TN-1C 16x2 ADM (L-1.1 optics) NTFT52BL
TN-1C 16x2 ADM (L-1.2 optics) NTFT52BG
These units are supplied in a plastic case

Ordering codes 9-7
Table 9-19
Obsolete codes (continued)
TN-1C 8x2 ADM (S-1.1 optics) NTFT52BD

TN-1C 8x2 ADM (L-1.1 optics) NTFT52BN
TN-1C 8x2 ADM (L-1.2 optics) NTFT52BI
These units are supplied in a metal case and are
upgradeable to provide 16x2 Mbit/s tributaries or up to
two 34/45 Mbit/s tributaries
TN-1C 8x2 & 1 x 34/45 ADM (S-1.1 optics) NTFT52BP
TN-1C 8x2 & 1 x 34/45 ADM (L-1.1 optics) NTFT52BQ
TN-1C 8x2 & 1 x 34/45 ADM (L-1.2 optics) NTFT52BR
These units are supplied in a metal case and are
upgradeable to provide 16x2 Mbit/s tributaries or two
34/45 Mbit/s tributaries
TN-1C 8x2 & 2 x 34/45 ADM (S-1.1 optics) NTFT52BS
TN-1C 8x2 & 2 x 34/45 ADM (L-1.1 optics) NTFT52BT
TN-1C 8x2 & 2 x 34/45 ADM (L-1.2 optics) NTFT52BU
TN-1P
TN-1P Release 5 NTFT51BA
TN-1P (1+1) Release 5 NTFT51BB
TN-1P multiplexer PIU NTFT01AC
TN-1P multiplexer PIU (1+1) NTFT01AF
TN-1P Basestation (Release 5.0) NTFT51BC
TN-1P headend
TN-1P MPP NTFT01HC
TN-1P (1+1) MPP NTFT01HF

10-1
Appendix A: Synchronous digital

hierarchy 10-
Synchronous Digital Hierarchy
The Synchronous Digital Hierarchy (SDH), covered by ITU-T
recommendations G.707, G.708, and G.709 (formally CCITT), details the
international standards covering synchronous multiplexing and transmission.
• G.707 - Synchronous Digital Hierarchy Bit Rates
• G.708 - Network Node Interface for the Synchronous Digital Hierarchy
• G.709 - Synchronous Multiplexing Structure
0
The standards propose a number of recommendations, including the
transmission of Plesiochronous Digital Hierarchy (PDH) rates (except
8 Mbit/s). The tributary signals can be packaged into a standard sized
container and located in an easily identifiable position within the multiplexed
structure. The multiplexing structure includes provision for embedded
network management channels.
The main advantages of the SDH are:

• Simplified multiplexing/demultiplexing techniques compared to PDH.
• Access to lower speed tributaries without the need to multiplex/
demultiplex the entire high speed signal. This allows efficient drop and
insert of channels and cross connect applications.
• Embedded network management channels which provide enhanced
Operations, Administration, and Maintenance (OAM) capabilities,
allowing efficiently controlled networks.
• Easy growth to higher multiplexing levels.
• Allows the transport of digital signals at the hierarchy bit rates specified in
ITU-T recommendation G.702 (except 8 Mbit/s) and at broadband channel
bit rates. This will allow SDH equipment to be introduced directly into 10
existing networks and also allows the introduction of a wide range of
services.
• The standard defines an optical interface which allows mid span fibre
meets between equipment from different suppliers.
0

10-2 Appendix A: Synchronous digital hierarchy
SDH multiplexing structure

The first level of the SDH is at 155.52 Mbit/s and is known as a Synchronous
Transport Module 1 (STM-1) signal. Higher rates are integer multiples of the
first level bit rate and are denoted by the corresponding multiplication factor
of the first level rate. At present, the following rates constitute the Synchronous
Digital Hierarchy:
• STM-1: 155.52 Mbit/s
• STM-4: 622.08 Mbit/s
• STM-16: 2488.32 Mbit/s (2.5 Gbit/s)
• STM-64 9953.28 Mbit/s (10 Gbit/s)
0
SDH allows for any of the current transmission rates (except 8 Mbit/s) to be
mapped into containers, called Virtual Containers (VCs). The containers can
be combined into standard formats in order to form the payload of the STM-1
signal. Different containers can be mixed, allowing for different rates to be
carried simultaneously within the same structure.
The generalized multiplexing structure of the SDH is shown in Figure 10-1.

Figure 10-1
SDH generalized multiplexing structure
xN x1
STM-N AUG AU-4 VC-4 C-4 140 Mbit/s
x3
x1
x3 TUG-3 TU-3 VC-3
x7
45 Mbit/s
AU-3 VC-3 C-3
34 Mbit/s
x7
x1
Pointer TUG-2 TU-2 VC-2 C-2 6 Mbit/s
Processing
x3
Multiplexing x4 TU-12 VC-12 C-12 2 Mbit/s
Aligning
Mapping
TU-11 VC-11 C-11 1.5 Mbit/s
The elements of the SDH are as follows:
Container (C-n), n=1 to 4

This is the basic element of the STM signal consisting of a group of bytes
allocated to carry the transmission rates defined in ITU-T recommendation
G.702 (i.e. 1544 kbit/s and 2048 kbit/s transmission hierarchies).
Virtual Container (VC-n), n=1 to 4

The lower order VC-ns (n=1 or 2) are built up of the basic container (C-n, n=1
or 2) plus additional capacity to carry Path Overhead (POH) information.
Note: VC-11 and VC-2 are not applicable to this equipment.

The higher order VC-ns (n=3 or 4) are built up of either a single basic
container (C-n, n=3 or 4), or an assembly of Tributary Unit Groups (TUGs),
together with the appropriate POH information.
The POH information includes VC path performance monitoring, signals for

maintenance purposes, and alarm status indications. The POH information for
the higher order VC-ns also includes multiplex structure indications which
detail the VC composition.
Tributary Unit (TU-n), n=1 to 3

This element consists of a VC plus a Tributary Unit pointer and provides
adaptation between the lower order path layer and the higher order path layer.
The pointer value indicates the phase alignment of the VC with respect to the
TU POH added to it. The pointer location is fixed with respect to this higher
level VC.
Tributary Unit Group (TUG-n), n=2 or 3

This element is formed by a group of identical TUs or TUGs, allowing mixed
capacity payloads to be constructed.
Administrative Unit (AU-n), n=3 or 4

This element consists of a VC-n (n=3 or 4) plus an AU pointer and provides
adaptation between the higher order paths and the multiplex section layer.
The pointer value indicates the phase alignment of the VC-n with respect to
the STM-1 frame. The location of the pointer is fixed within the STM-1 frame
structure.
Administrative Unit Group (AUG)

This element is formed by a group of byte interleaved AUs. The AUG has a
fixed position in the STM payload.
Synchronous Transport Module Level 1 (STM-1)

This is the basic element of the SDH and comprises a single AUG and the
Section Overhead (SOH) information. The STM-1 frame structure comprises
an array of 270 columns by 9 rows of 8-bit bytes as shown in Figure 10-2.
The frame length is 125 µs. The order of transmission is from left to right,
then from top to bottom. Within each byte, the most significant bit (bit 1) is
transmitted first. The SOH information includes STM-1 framing, section
performance monitoring, and other maintenance and operational information.
10

Figure 10-2
STM-1 frame structure
270 Columns (Bytes)

1 9 10 270
1
SOH
3
4 AU PTRs STM-1
9 Rows 5 Payload
SOH
Synchronous Transport Module Level N (STM-N)

This element defines the Nth level of the SDH. An STM-N contains N AUGs
together with SOH information. The N AUGs are one-byte interleaved and
have a fixed phase relationship with respect to the STM-N.
TN-1C multiplexing structure

The TN-1C uses a subset of the SDH multiplexing structure as shown in
Figure 10-3.
Figure 10-3
TN-1C multiplexing structure
xN x1 x3 x7 x3
STM-N AUG AU-4 VC-4 TUG-3 TUG-2 TU-12 VC-12 C-12 2 Mbit/s
x1 34 Mbit/s
TU-3 VC-3 C-3 45 Mbit/s
The procedure for assembling the STM-1 frame for the TN-1C and brief
descriptions of the overhead bytes are given in the following sections.
TN-1P multiplexing structure

The TN-1P uses a subset of the SDH multiplexing structure as shown in
Figure 10-4.
Figure 10-4
TN-1P multiplexing structure
xN x1 x3 x7 x3
STM-N AUG AU-4 VC-4 TUG-3 TUG-2 TU-12 VC-12 C-12 2 Mbit/s

Mapping of a 2048 kbit/s signal into a VC-12

The 2048 kbit/s tributary signal (C-12) is asynchronously mapped into a
VC-12 signal (see Figure 10-5).
The additional fixed stuff bits and bytes maintain a defined size of 140 bytes
for a 500 µs TU multiframe (i.e. four STM-1 frames). Asynchronous
mapping allows for justification of the tributary, allowing for variations
between the tributary clock rates and the clock providing the timing for the
synchronous network. The VC-12 signal contains a POH byte, which
provides error checking, signal label, and path status information for the
VC-12 path (see “VC-12 path overhead” on page 10-10).
Figure 10-5
2.048 Mbit/s tributary/VC-12/TU-12 mapping
State of
VC-12 TU-12 H4 byte
V5 V1 (Ptr 1) XXXXXX00
R
32 Bytes
R
J2
Zero Ptr
C1 C2 O O O O R R offset V2 (Ptr 2) XXXXXX01
V5
32 Bytes
140 Bytes
R
500 µs
Z6
144 Bytes
C1 C2 O O O O R R
V3 (Ptr 3, Action) XXXXXX10
32 Bytes
R
Z7
C 1 C 2 O O O O R S1
S2 I I I I I I I
V4 (Reserved) XXXXXX11
31 Bytes
R
Asynchronous mapping
for 2048 kbit/s tributary
(Multiframe) 10
I: Information Bit O: Overhead
C: Justification Control S: Justification Opportunity
R: Fixed Stuff V5: VC1 Path Overhead
J2: LO Path Trace Z6, Z7: Reserved

Mapping of a 34.368 Mbit/s signal into a VC-3

The 34368 kbit/s tributary signal (C-3) is asynchronously mapped into a
VC-3 signal.
In addition to the VC-3 POH, the VC-3 consists of a payload of 9 x 84 bytes

every 125 µs. This payload is divided into three subframes, each subframe
comprising information bits (I), two sets of justification control bits (C1, C2),
two justification opportunity bits (S1, S2), and fixed stuff bits (R).
Figure 10-6
34.368 Mbit/s tributary/VC-3 mapping
J1
B3 T1 3 rows
C2
G1
VC-3 POH F2 T2 3 rows
H4
Z3
K3 T3 3 rows
Z5
1 125 µs
84
3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 C 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 C 3x81
3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 C 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 C 3x81
3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 C 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 3x81 A B 81
= RRRRRRRR
RRRRRRC1C2 RRRRRRRS1 S2I I I I I I I
R Fixed stuff bit
C1,C2 Stuff control bit
S1,S2 Justification opportunities bit
I Information bit
Mapping of a 44.736 Mbit/s signal into a VC-3

The 44.736 Mbit/s tributary signal (C3) is asynchronously mapped into a
VC-3 signal.
This payload is divided into nine subframes. Each subframe comprises one
byte of VC-3 POH, data bits, a set of justification control bits, one
justification opportunity bit, and two overhead communication channel bits.
The remaining bits are fixed stuff (R) bits. The O bits are reserved for future
overhead communication purposes.

Figure 10-7
44.736 Mbit/s tributary/VC-3 mapping
POH 8R 8R RRC 8R CCRRRRRR 8R CCRROORS
J1 5I 200 I 8I 200 I 8I 200 I
B3
C2
G1
F2
H4
Z3
K3
Z5
85
R Fixed stuff bit
C Justification bit
S Justification opportunity bit
I Information bit
O Overhead bit
Multiplexing of VC-12s into a TUG-2

A pointer is added to the VC-12 signal to form a TU-12, the pointer indicates
the phase alignment of the VC-12 with respect to the TU-12 (see
Figure 10-8). If the timing of a VC causes it to slip with respect to the timing
of the TUG, the pointer is adjusted to indicate the new alignment. Each
TU-12 occupies four columns. shows a conceptual view of the mapping of
three TU-12s into a TUG-2. In practice, the columns of each TU-12 are
interleaved as shown in Figure 10-9.
Multiplexing of TUG-2s into a TUG-3

The mapping of TUG-2s into a TUG-3 is a fixed mapping as shown in
Figure 10-9. The inclusion of the TUG-3 is primarily to provide a structure
for 34,368 kbit/s and 44,736 kbit/s transmission rates.
10

Figure 10-8
Multplexing of TU-12 via a TUG-2
TUG-2
12 Columns
VC VC VC
Ptr Ptr Ptr
TU-12
9 Rows
4 Columns
Figure 10-9
TU-12/TUG-2/TUG-3 multiplexing
A B C
TU-12
AB AB AB AB
C C C C
TUG-2
(1) (2) (3) (7)
12 12 12 12 12 12 12
34 34 34 34 34 34 34
TUG-3 56
7
56
7
56
7
56
7
56
7 56 56
7
7
Stuffing
1 3 5 7 9 85
2 4 6 8 84 86

Multiplexing of a VC-3 into a TUG-3

A pointer is added to the VC-3 signal to form a TU-3, the pointer indicates the
phase alignment with respect to the TU-3 frame. The individual TU-3
pointers are contained within the H1, H2, and H3 bytes within the TUG-3, see
Figure 10-10.
Figure 10-10
Multiplexing of a TU-3 via a TUG-3
86 columns
H1 TUG-3
H2
85 columns
H3
J1
Fixed stuff
B3
C2
G1
F2
Container-3
H4
Z3
K3
Z5
VC-3
VC-3 POH
Mapping of TUG-3s into a VC-4

The mapping of three TUG-3s into a VC-4 is fixed as shown in Figure 10-11.
Column one of the VC-4 contains the nine POH bytes, which provide error
checking, signal label, path status, and multiplexing structure information for
the VC-4 path (see “Path overheads” on page 10-10). Columns two and three
are fixed stuff.
Figure 10-11
Multiplexing of three TUG-3s into a VC-4
TUG-3 TUG-3 TUG-3 TUG-3

(A) (B) (C)
1 86 1 86 1 86
10
POH
AB AB A B C A B CA B C
C C
VC-4
1 3 5 7 9 261
2 4 6 8

Mapping of a VC-4 into a STM-1 via an AU-4/AUG

An AU pointer is added to the VC-4 to form an AU-4, the pointer indicates
the phase alignment of the VC-4 with respect to the STM-1 frame. The AU-4
pointers are in a fixed location in the STM-1 frame (see Figure 10-12). The
AU-4 is placed directly in the AUG, which together with the SOH, forms the
STM-1.
Figure 10-12
Mapping of a VC-4 into an STM-1 via an AU-4/AUG
9 261
AUG AU-4
3 SOH
1 J1
B3
AU-4 PTR
C2
5 SOH
G1
F2 VC-4
H4
Z3
K3
Z5
VC-4 POH
The Section Overhead (SOH) provides STM-1 framing, section performance

monitoring and other maintenance functions pertaining to the section path
(see “Section overhead” on page 10-11).
Path overheads
The Path Overhead (POH) forms part of the relevant Virtual Container and
provides information for use in the end-to-end management of a synchronous
path.
VC-12 path overhead

The V5 byte in the VC-12 (see Figure 10-13) is the path overhead information
pertaining to the VC-12 end-to-end path. The function of the V5 bits is shown
in Figure 10-13 and is detailed in subsequent paragraphs:
Figure 10-13
VC-12 Path Overhead (V5 byte)
)
REI (FEBE) RFI RDI (FERF)

BIP-2 Signal Label
1 2 3 4 5 6 7 8
• BIP-2 (Bits 1 and 2). The Bit Interleaved Parity (BIP) bits are used to
provide an error monitoring function for the VC-12 path.

• REI (remote error indication) (Bit 3). The REI bit is used to
communicate detected BIP-2 errors back to the VC-12 path originator.
Also known as FEBE (far end block error)
• RFI (remote fail Indicator) (Bit 4). Not used in present applications.
• Signal label (Bits 5 to 7). These bits are used to indicate the payload
mapping and equipped status.
• RDI (remote defect indication) (Bit 8). The RDI bit is used to indicate
certain detected TU path alarms to the VC-12 path originator. Also known
as FERF (far end receive failure).
VC-3/VC-4 path overhead

The VC-3/VC-4 path overhead consists of nine bytes as shown in
Figure 10-14. The function of the nine bytes is as follows:
• Path trace (J1 byte). This byte is used to provide a fixed length string
which is transmitted repetitively so that the receiving terminal can verify
connection to the intended transmitter.
• Path BIP-8 (B3 byte). This byte provides an error monitoring function for
the VC-3/VC-4 path.
• Signal label (C2 byte). This byte is used to indicate the composition of the
VC-3/VC-4 payloads.
• Path status (G1 byte). This byte conveys path terminating status and
performance information back to the VC-3/VC-4 path originator:
• Path user channel (F2 byte). This byte is for user communication
purposes between path elements. Not used in present applications.
• Multiframe indicator (H4 byte). This byte provides a generalized
multiframe indicator for payloads.
• APS (automatic protection switching) (K3 byte). This byte is for APS
signalling for high order path protection. Not used in present applications.
• Spare (Z3 and Z5 bytes). Not used in present applications.
Section overhead
The Section Overhead (SOH) forms part of the STM-1 frame. The SOH is
divided into two parts, the Multiplexer Section Overhead (MSOH) and the
Regenerator Section Overhead (RSOH). The MSOH is only generated/
terminated at each end of a multiplex section (i.e. where an STM is
assembled/disassembled) and passes transparently through regenerators. The
RSOH is assembled/terminated at each regenerator and at the end of a
multiplex section. The section overhead bytes are detailed in Figure 10-14. 10

Figure 10-14
Section overhead
A1 A1 A1 A2 A2 A2 J0 A1, A2: Framing

B1, B2: Bit Error Monitoring
RSOH B1 E1 F1 J0: Regenerator Section Trace - not
D1 D2 D3 currently used
D1 - D12: Data Channel
AU-Pointer H1 H1 H1 H2 H2 H2 H3 H3 H3 E1, E2: Order Wire
F1: User Channel
B2 B2 B2 K1 K2
H1, H2, H3: AU-Pointer Bytes
D4 D5 D6 K1, K2: Automatic Protection Switching
S1 Timing Marker Byte -
MSOH D7 D8 D9 not currently used
D10 D11 D12 Z1, Z2: Spare
M1: Section FEBE - not currently
S1 Z1 Z1 Z2 Z2 M1 E2 used
All unmarked bytes are reserved for Bytes reserved for national use.
future international standardisation.
The function of the RSOH bytes is as follows:

• Framing (A1 and A2 bytes). These bytes carry the frame alignment
pattern.
• BIP-8 (B1 byte). This byte is used to provide an error monitoring function
for a regenerator section. The byte is also used in the frame alignment
process.
• Orderwire (E1 byte). This byte is used to provide an orderwire channel
which can be accessed at regenerators and multiplexers. Not used in
present applications.
• User channel (F1 byte). This byte is reserved for user purposes. Not used
in present systems.
• DCCR (Data Communications Channel) (D1 to D3 bytes). The DCC
bytes provide a 192 kbit/s regenerator data channel. These bytes can be
used as a physical layer for the embedded communications channel (ECC).
• Regenerator Section Trace (J0 byte). Not used in present applications.
0
The function of the MSOH bytes is as follows:
• BIP-24 (Byte B2). These bytes are used to provide an error monitoring
function for the multiplex section.
• APS channel (K1, K2 bytes). The Automatic Protection Switching (APS)
channel bytes are used for APS signalling. In present systems, the bytes are
only used to communicate multiplex section AIS and RDI indications to
the far multiplexer.
• DCCM (D4 to D12 bytes). The DCC bytes provide a 576 kbit/s multiplex
data channel. These bytes can be used as a physical layer for the ECC.
• Orderwire (E2 byte). This byte is used to provide an orderwire channel
which can be accessed only at multiplex section terminations. Not used in
present applications.

• Timing Marker Byte (S1 byte). Not used in present applications (set to
0Bh).
• Spare (Z1, Z2 bytes). Function not allocated. Not used in present
applications.
• Section REI (FEBE) (M1 byte). Not used in present applications.
All other bytes in the RSOH and MSOH are either reserved for national use or
for future international standardization and are not used in present systems.
end of chapter
10

11-1
Index 11-
2 Mbit/s tributary interface 7-4 B
120 Ω 8-13 background block error (BBE) 6-1
75 Ω 8-13 banks
34 Mbit/s tributary interface 7-4, 8-14 flash memory 2-7, 3-6
45 Mbit/s tributary interface 7-5, 8-14 batteries
back-up 4-2
A replacement period 7-9
a.c. mains block diagram
parameters 7-9 TN-1C network element 2-3
address TN-1P network element 2-4
manual area 3-5 broken fibre
network 3-5 single fibre working 2-19
ADM loop feeder browser 1-26
TN-1C 1-8 built-in test 2-19
administrative unit (AU) 10-3
administrative unit group (AUG) 10-3 C
alarm handling 2-24 channel numbering schemes 1-18
alarms 3-1 clear channel telemetry 1-13
external 3-2 clock 3-4
interface 7-8 internal 2-6
handling 3-1 clock generator 2-6
masking 3-1 codes 9-1
monitoring 3-1 ordering 9-1
power supply unit 4-2, 7-9 cold restart 2-6
QOSV 6-7 Command Line User Interface (CLUI) 1-26
rack 3-2 communication
application memory 2-6 serial links 2-7
application software 1-27, 3-6 configuration data 3-6
assessed seconds (AS) 6-2 configuration table
ATU 3-3 memory 2-6
clear channel telemetry 1-13 configurations
interface 7-8, 8-16 TN-1C
TN-1C 1-9 ADM loop feeder 1-8
TN-1P 1-13 ATU 1-9
automatic laser shutdown 2-14 path protected 2-fibre ring 1-7
point-to-point terminal 1-7
11

11-2 Index
TN-1P F
ATU 1-13 fan
hub 1-12 interface 8-18
point-to-point terminal 1-10 TN-1C 1-28
spur 1-11 flash memory
connections banks A and B 2-7, 3-6
path trace 1-24 foundation memory 2-6
signal label 1-25 foundation software 1-27
traffic mode 1-23 fuses 7-2, 8-24
user labels 1-23 power supply unit 7-9
connectivity 1-18
connector panel 8-3
connectors 8-3 H
construction 7-2 hierarchy
mechanical 1-15 synchronisation source 5-6
power supply unit 4-4 holdoff period 2-13
continuity tests 2-20 hub
craft access panel (CAP) 2-22 TN-1P 1-12
craft access terminal
interface 7-7, 8-15 I
serial communications 2-7 installation
criteria examples 1-16
path protection switching 2-14 Integrated Network Manager (INM) 1-26
interfaces 7-4
D 2 Mbit/s tributary 7-4, 8-13
data communications channel (DCC) 3-4 34 Mbit/s tributary 7-4, 8-14
dimensions 45 Mbit/s tributary 7-5, 8-14
TN-1C 7-2 ATU 7-8, 8-16
TN-1P 7-2 craft access terminal 7-7, 8-15
TN-1P Basestation 7-2 external alarms 7-8, 8-19
TN-1PH 7-2 external synchronisation input 7-7, 8-18
download 1-28 fan 8-18
LAN 7-7, 8-22
power 7-2, 8-21
E rack alarm adaptor 8-23
electromagnetic compatibility 7-1 rack alarm bus 8-24
electrostatic discharge 7-1 STM-1 optical 7-5, 8-15
embedded control channel (ECC) 1-26, 2-7 internal clock 2-6
enclosure types 1-15 inventory 3-5
environmental conditions 7-1
equipment codes 9-1
errored second (ES) 6-1 K
ETSI channel numbering scheme 1-18 KLM channel numbering scheme 1-18
external alarms 3-2
interface 7-8, 8-19
external interfaces 7-4, 8-1
external synchronisation interface 7-7, 8-18

Index 11-3
L path
LAN overheads 10-10
interface 2-24, 3-4, 7-7, 8-22 protection switching 1-26, 2-13
laser criteria 2-14
automatic shutdown 2-14 reversion 2-13
local loopback path protected 2-fibre ring
STM-1 2-15 TN-1C 1-7
tributary 2-17 path trace 1-24
loopbacks 2-15 PDH ports
ECC comms loss 2-18 designations 1-20
performance monitoring 6-1, 6-9
anomalies and defects 6-3
M counts 6-1
management 3-3 parity error 6-1
manual area address 3-5 disabling 6-3
mapping early termination 6-7
2 Mbit/s to VC-12 10-5 logs 6-5
34 Mbit/s to VC-3 10-6 15 minute 6-5
45 Mbit/s to VC-3 10-6 24 hour 6-6
TUG-3 to VC-4 10-9 periods 6-4
masking 3-1 points (PMP) 6-2, 6-9
memory 2-6 QOSV alarms 6-7
banks 2-7, 3-6 VC-4 passthrough 6-9
monitoring warm restart 6-7
alarms 3-1 zero suppression 6-1
mounting point-to-point terminal
rack 1-17 TN-1C 1-7
street cabinet 1-17 TN-1P 1-10
TN-1P headend subrack 1-17 port designations 1-20
wall 1-17 power consumption
multiplexing power supply unit 7-9
TUG-2 into TUG-3 10-7 TN-1C 7-3
VC-12 into TUG-2 10-7 TN-1P 7-3
multiplexing structure 10-4 TN-1P Basestation 7-3
TN-1PH 7-3
N power supply
network address 3-5 interface 8-21
internal 2-5
O power supply unit 4-1
optical interfaces 8-15 a.c. supply 7-9
ordering codes 9-1 alarms 7-9
oscillation guard time 2-13 connectors 4-3
construction 4-4
external 2-5
P output voltage 2-5
parameters 7-1 parameters 7-9
partner NE 1-27
passthrough 6-9
power consumption 7-9 11
power-up test 2-19
protection switching
path 1-26, 2-13

11-4 Index
Q synchronisation 5-1
quality levels 5-7 loss 5-1
quality of service violation (QOSV) quality levels 5-7
alarms 6-7 schemes 5-2
TN-1C 5-2
TN-1P 5-3
R settings 5-6
rack alarm adaptor 1-27, 3-2, 9-6 single fibre working 2-19
interface 8-23 source hierarchy 5-6
rack alarm bus 8-24 source switch 5-6
rack alarms 3-2 sources 5-1
rack mounting 1-17 failure 5-13
remote loopback synchronisation status messaging 5-7
STM-1 2-16 synchronous digital hierarchy (SDH) 10-1
tributary 2-17 multiplexing structure 10-2
restart synchronous equipment management function
cold 2-6 (SEMF) 3-1
warm 2-6 system clock 2-6
reversion system parameters 7-1
path protection switching 2-13
RS-232
CAT channel 2-7
T
selector 2-24 telemetry (ATU)
clear channel 1-13
test
S continuity 2-20
SDH multiplexing structure 10-2 facilities 2-19
section overhead 10-11 power-up 2-19
severely errored second (SES) 6-1 results 2-21
signal label 1-25 timeslot interchanger 2-7
VC-12 10-11 timing source
VC-3 10-11 clock generator 2-6
single fibre working 2-18 internal clock 2-6
software 1-27, 3-6 TN-1C network element
application 1-27, 3-6 block diagram 2-3
download 1-28 configurations 1-7
foundation 1-27 construction 1-15
reversion 3-6 dimensions 7-2
upgrade 3-7 general view 1-3
spur multiplexing structure 10-4
TN-1P 1-11 power consumption 7-3
STM-1 aggregate channels traffic processing 2-8
designations 1-20 weight 7-2
STM-1 signal TN-1P Basestation network element
structure 10-3 construction 1-15
STM-1 dimensions 7-2
interface 2-7, 7-5 general view 1-6
supply voltage 7-2 power consumption 7-3
a.c. (PSU) 7-9 weight 7-2

Index 11-5
TN-1P network element U

block diagram 2-4 unavailable second (UAS) 6-2
configurations 1-10 unavailable time (UAT) 6-2
construction 1-15 user labels 1-23
dimensions 7-2
general view 1-4
multiplexing structure 10-4 V
power consumption 7-3 variants
traffic processing 2-11 TN-1P 1-31
variants 1-31 virtual container (VC) 10-2
weight 7-2 volatile memory 2-6
TN-1PH network element voltage
construction 1-15 a.c. 7-9
dimensions 7-2 d.c. 7-2
mounting 1-17
power consumption 7-3 W
weight 7-2 wall mounting 1-17
traffic 2-7 warm restart 2-6
processing weight
TN-1C network element 2-8 TN-1C 7-2
TN-1P network element 2-11 TN-1P 7-2
user labels 1-23 TN-1P Basestation 7-2
traffic mode 1-23 TN-1PH 7-2
tributary unit group (TUG) 10-3
11

International Optical Networks
Technical Documentation Group
Nortel Networks
Oakleigh Road South
London, N11 1HB
So far as Nortel Networks is aware the contents of this document
are correct. However, such contents have been obtained from a
variety of sources and Nortel Networks can give no warranty or
undertaking and make no representation as to their accuracy. In
particular, Nortel Networks hereby expressly excludes liability for
any form of consequential, indirect or special loss, and loss of
data, loss of profits or loss of business opportunity, howsoever
arising and whether sustained by the user of the information
herein or any third party arising out of the contents of this
document.
*
NORTEL NETWORKS, the Nortel Networks logo, the
Globemark, How the World Shares Ideas and Unified Networks
are trademarks of Nortel Networks.
NORTEL NETWORKS
TN-1C/TN-1P
System Description
Copyright  1996 – 2001 Nortel Networks, All Rights Reserved.
The copyright of this document is the property of Nortel Networks.
Without the written consent of Nortel Networks, given by contract
or otherwise, this document must not be copied, reprinted or
reproduced in any material form, either wholly or in part, and the
contents of this document, or any methods or techniques
available therefrom, must not be disclosed to any other person
whatsoever.
NORTEL NETWORKS CONFIDENTIAL: The information
contained herein is the property of Nortel Networks and is strictly
confidential. Except as expressly authorized in writing by Nortel
Networks, the holder shall keep all information contained herein
confidential, shall disclose the information only to its employees
with a need to know, and shall protect the information, in whole or
in part, from disclosure and dissemination to third parties with the
same degree of care it uses to protect its own confidential
information, but with no less than reasonable care. Except as
expressly authorized in writing by Nortel Networks, the holder is
granted no rights to use the information contained herein.
Document Number: 323-1081-100
Product Release Number: 5.2
Document Status: Standard (Revision 1)
Date: October 2001
Printed in England

TN-1C System Description

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

TN-1C System Description

Diunggah oleh

Hak Cipta:

Format Tersedia

323-1081-100

Release 5.2 Standard (Revision 1) October 2001

Document Number: 323-1081-100

Copyright  1996 – 2001 Nortel Networks, All Rights Reserved.

TN-1C/TN-1P System Description

TN-1C/TN-1P System Description

System overview 1-1

TN-1C/TN-1P System Description

Equipment description 2-1

Equipment management 3-1

323-1081-100 Release 5.2 Standard (Revision 1)

Power supply unit 4-1

Performance monitoring 6-1

System parameters 7-1

TN-1C/TN-1P System Description

Maximum power consumption 7-3

External interfaces 8-1

Ordering codes 9-1

Appendix A: Synchronous digital hierarchy 10-1

323-1081-100 Release 5.2 Standard (Revision 1)

Multiplexing of TUG-2s into a TUG-3 10-7

TN-1C/TN-1P System Description

Figure 8-7 TN-1P connection panel (4 x 2 Mbit/s) Release 5 hardware 8-9

323-1081-100 Release 5.2 Standard (Revision 1)

Figure 8-1 TN-1C connection panel (8 x 2 Mbit/s + 34/45 Mbit/s version)

TN-1C/TN-1P System Description

About this document

Indication of trademarks in this document

TN-1C/TN-1P System Description

Technical support and information

Nortel Networks provides a comprehensive technical support service for its

You can contact us via the Nortel Networks web site:

Select the link Customer Support.

323-1081-100 Release 5.2 Standard (Revision 1)

The TN-1C comprises a multiplexer assembly containing:

A single-slot TN-1C is available which comprises a multiplexer assembly

In the transmit direction, the TN-1C multiplexes plesiochronous electrical

Note: If a tributary extension card is not fitted, a dummy card must be

In addition to the tributary extension card, there is an optional high

TN-1C/TN-1P System Description

WAN interfaces. For a description of the TN-1C multiplexer Packet Edge 10

TN-1P and TN-1PH headend multiplexers

The TN-1PH headend contains up to twelve multiplexers (each functionally

In the transmit direction, the TN-1P multiplexes up to four plesiochronous

TN-1P Basestation multiplexer

You can upgrade the 4 x 2 Mbit/s versions of the TN-1P Basestation to

Note: Refer to the TN-1C/TN-1P Installation Procedures 323-1081-200

The TN-1P Basestation is suitable for installations where equipment height is

The TN-1P Basestation comprises a rack-mounting shelf assembly containing

323-1081-100 Release 5.2 Standard (Revision 1)

Secondary fan controller

Main 8x2 Mbit/s Tributary extension card or

Note: The TN-1C illustrated is the 16 x 2 Mbit/s version.

TN-1C/TN-1P System Description

Note 1: At Release 5, the TN-1P connection panel supports 4 x 2 Mbit/s tributaries.

Note 2: The fan is not fitted to Release 5 hardware.

323-1081-100 Release 5.2 Standard (Revision 1)

Plug-in Unit area

Fibre tray position

TN-1C/TN-1P System Description

Rear connector panel

Note: The fan is not fitted to Release 5 hardware.

323-1081-100 Release 5.2 Standard (Revision 1)

System configuration - TN-1C 1