Tn-1x System Description

323-1061-100 SDH TRANSMISSION

Nortel TN-1X System Description

Release 9 Standard July 2001

SDH TRANSMISSION

Nortel TN-1X System Description

Document Number: 323-1061-100 Document Status: Standard Product Release Number: 9 Date: July 2001

Copyright  1995 – 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 it only to its employees with a need to know, and shall protect it, 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 and Unified Networks are trademarks of Nortel Networks.

Netscape and Navigator are trademarks of Netscape Communications Corporation. Hewlett-Packard is a trademark of Hewlett-Packard Company.

Nortel TN-1X System Description

iii

Publication history July 2001 Release 9 Standard. November 1998 Release 8 Standard (Revision 2). October 1998 Release 8 Standard (Revised). September 1998 Release 8 Standard. November 1997 Release 7 Standard (Revision 1). October 1997 Release 7 Standard. November 1996 Release 6 Standard. December 1995 Release 5.1 Standard.

Nortel TN-1X System Description

v

Contents About this document

xiii

Related documents xiii

Technical support and information

xiv

System overview

1-1

TN-1X network element 1-1 Preside EC-1 Element Controller 1-4 1:N and remote central archive facility 1-4 Preside 1-5

System configurations

2-1

Terminal multiplexer 2-3 Drop and insert multiplexer 2-3 STM-4 aggregates 2-5 STM-1 tributaries 2-7 Single fibre working 2-9 Engineering Order Wire 2-10

Equipment description

3-1

TN-1X subrack 3-3 TN-1X/S subrack 3-3 Subrack layouts 3-4 Equipped subrack variants 3-5 Plug-in units 3-6 Equipping 3-9 Interface modules 3-9 TN-1X 3-9 TN-1X/S 3-10 TIM allocation - TN-1X 3-11 TIM allocation - TN-1X/S 3-11 Connector panels 3-12 Local Craft Access Panel 3-12 Equipment codes 3-12 TN-1X subrack codes 3-16 TN-1X/S subrack codes 3-16 Blank panel codes 3-16 Inventory 3-16 Automatic laser shutdown 3-17 Laser test facility 3-19

System parameters

4-1

Power requirements 4-1 Nortel TN-1X System Description

vi Construction 4-1 System interfaces 4-3 ElectroMagnetic compatibility 4-7 Environmental conditions 4-7 Thermal qualifications 4-8

Traffic processing

5-1

Internal traffic interfaces 5-1 Tributary Unit/Payload Manager interfaces 5-2 Payload Manager/Aggregate Unit interfaces 5-3 Overhead buses 5-3 Traffic processing 5-4 2 Mbit/s Tributary Unit 5-9 34/45 Mbit/s Tributary Unit (VC-3) 5-9 34 Mbit/s Tributary Unit (16x2) 5-10 STM-1 Tributary Unit 5-11 Payload Manager 5-12 STM-1 Aggregate Unit 5-13 STM-4 Optical Aggregate Unit 5-14

Equipment management

6-1

Backplane interfaces 6-1 Subrack Controller 6-3 Card controllers 6-3 Real time clock 6-4 Alarm monitoring 6-5 Alarm handling 6-5 External alarms 6-6 Software 6-8 Software upgrade overview 6-9 Software status 6-9 Configuration data 6-12 Configuration table status 6-12 Detached mode 6-13 Warm restart 6-14 Cold restart 6-14 Local terminal interface 6-15 Network management 6-15 Remote Layer Management 6-17 Third-party router interoperability 6-19 Punch-Through feature 6-19

Synchronisation Synchronisation sources 7-1 Synchronisation source hierarchy 7-2 Synchronisation settings 7-3 Synchronisation switching mechanisms 7-4 Synchronisation status messaging 7-4 Synchronisation status messaging network examples 7-6 Inter-operating with non-SSM networks 7-8 SSM recommendations 7-9 Non-SSM synchronisation sourcing 7-10 Failure of synchronisation source 7-11 Failure hold-off time 7-11 323-1061-100 Release 9 Standard

7-1

vii Wait to restore time 7-11 External synchronisation output 7-12 Synchronisation alarms 7-12

Power

8-1

Power supply to the TN-1X subracks 8-1 Power supply to the TN-1X/S subracks 8-2

Connectivity

9-1

Channel numbering schemes 9-1 Port/channel designations 9-3 Connection types 9-5 Through connections 9-5 Unprotected drop/insert connections 9-6 Protected drop/insert connections 9-6 Internal traffic connections 9-6 General rules for adding new connections 9-6 Defragmentation 9-9 Traffic connections 9-10 Testing connections 9-11 Standby connections 9-11 User labels 9-12 Path trace (J1 and J2 byte) 9-12 J1 byte 9-12 J2 byte 9-13 Consequent actions 9-13 Single fibre working 9-14 Signal label (C2 and V5 bytes) 9-15 Consequent actions 9-16

Protection

10-1

VC-12/VC-3 path protection switching 10-1 Modes of operation 10-1 Provisionable Hold-Off time 10-2 Persistence checks 10-2 STM-1 tributaries 10-2 1:N 2 Mbit/s tributary protection 10-3 Modes of operation 10-4 Switching prerequisites 10-5 1:N tributary switching alarms 10-5 Payload Manager switching 10-7 Switching prerequisites 10-8 Multiplexer section protection 10-9 MSP configurations 10-10 Bidirectional and unidirectional operation 10-11 Switching conditions 10-13 MSP protocol 10-13 MSP alarms 10-16 MSP LAPD settings 10-17 Converting protected connection to unprotected connections 10-17 1:1 manual tributary protection 10-18

Performance monitoring

11-1

Types of parity error counts 11-1 Nortel TN-1X System Description

viii Performance counts 11-1 Performance monitoring points 11-3 Performance anomalies and defects 11-4 Performance monitoring periods 11-5 Performance logs 11-6 Quality of service violation alarms 11-6

Diagnostics

12-1

Loopbacks 12-1 2 Mbit/s Tributary Unit 12-2 34/45 Mbit/s Tributary Unit (VC-3) 12-3 STM-1 Aggregate Unit/STM-1 Tributary Unit 12-4 34 Mbit/s Tributary Unit (16x2) 12-4 Loopback alarm 12-4 Engineering Order Wire operation 12-5

Construction

13-1

TN-1X subrack variants 13-1 TN-1X/S subrack variants 13-3 Subrack backplane 13-5 Backplane connectors 13-5 Backplane links 13-5 Plug-in units 13-9 Interface modules 13-9 EOW handset 13-11 Electro-Magnetic Compatibility protection 13-12 Electro Static Discharge protection 13-12 Earthing arrangements 13-13 Unused subrack positions 13-13

External interfaces Introduction 14-1 Local Craft Access Panel 75 Ω 14-2 Mating connectors/cabling 14-3 75 Ω Traffic Access Module (TN-1X) 14 4 Mating connectors/cabling 14-5 75 Ω Traffic Access Module (1:N Protection) (TN-1X) 14-6 Mating connectors/cabling 14-7 75 Ω Traffic Access Module (TN-1X/S) 14-8 Mating connectors/cabling 14-9 120 Ω Traffic Access Module (TN-1X) 14-10 Mating connectors/cabling 14-12 120 Ω Traffic Access Module (1:N Protection) (TN-1X) 14-13 Mating connectors/cabling 14-15 120 Ω Traffic Access Module (TN-1X/S) 14-16 Mating connectors/cabling 14-18 High Speed Traffic Access Module (16x2) 14-19 Mating connectors/cabling 14-20 High Speed Traffic Access Module (VC-3) 14-21 Mating connectors/cabling 14-22 1:1 Manual Tributary Protection TAM (VC-3) 14-23 Mating connectors/cabling 14-24 High Speed Aggregate Module 14-25 Mating connectors/cabling 14-26 323-1061-100 Release 9 Standard

14-1

ix High Speed Tributary Module 14-27 Mating connectors/cabling 14-28 Station Service Module 14-29 Mating connectors/cabling 14-31 75 Ω Star Card (25UJJ00750GWZ) 14-32 Mating connectors/cabling 14-33 75 Ω Star Card (NTKD25AA) 14-34 Mating connectors/cabling 14-35 Flexible Termination Module 14-36 Flexible Access Module 14-37 Mating connectors/cabling 14-38 Power & LCAP Module 14-39 Mating connectors/cabling 14-41 Flexible Access Module (External Alarms) 14-42 Mating connectors/cabling 14-43 External Alarm Module 14-44 Mating connectors/cabling 14-45 75 Ω Connector Panel 14-46 Mating connectors/cabling 14-46 120 Ω Connector Panel 14-47 Mating connectors/cabling 14-48 EOW/CATT Connector Panel 14-49 Mating connectors/cabling 14-50 Cabling and connector arrangements 14-51 TN-1X subrack 14-51 TN-1X/S subrack 14-51 Optical connections 14-55 LAN transceiver connections 14-56

Appendix A: Synchronous digital hierarchy (SDH)

15-1

SDH multiplexing structure 15-2 TN-1X 15-4 Mapping of a 2048 kbit/s signal into a VC-12 15-4 VC3/TU-3 mapping/demapping 15-5 Multiplexing of VC-12s into a TUG-2 15-7 Multiplexing of TUG-2s into a TUG-3 15-8 Multiplexing of a VC-3 into a TUG-3 15-8 Mapping of TUG-3s into a VC-4 15-9 Mapping of a VC-4 into a STM-1 via an AU-4/AUG 15-10 Path overheads 15-10 Section overhead 15-11 TN-1X/4 15-13

Appendix B: Important notes

16-1

Introduction 16-1 Operational qualifications for Release 7 TN-1X multiplexer 16-1

Appendix C: Release 9 units, feature lists and compatability 17-1 Introduction 17-1

Index

18-1

Figures Figure 1-1

TN-1X - external interfaces 1-2 Nortel TN-1X System Description

x Figure 2-1 Figure 2-2 Figure 2-3 Figure 2-4 Figure 2-5 Figure 2-6 Figure 2-7 Figure 2-8 Figure 3-1 Figure 3-2 Figure 3-3 Figure 3-4 Figure 3-5 Figure 5-1 Figure 5-2 Figure 5-3 Figure 5-4 Figure 5-5 Figure 5-6 Figure 5-7 Figure 6-1 Figure 6-2 Figure 6-3 Figure 7-1 Figure 7-2 Figure 7-3 Figure 7-4 Figure 7-5 Figure 8-1 Figure 9-1 Figure 10-1 Figure 10-2 Figure 10-3 Figure 10-4 Figure 12-1 Figure 13-1 Figure 13-2 Figure 13-3 Figure 13-4 Figure 13-5 Figure 13-6 Figure 13-7 Figure 13-8 Figure 13-9 Figure 13-10 Figure 14-1 Figure 14-2 323-1061-100 Release 9 Standard

Nortel Networks TN-1X - typical system 2-2 Terminal multiplexer 2-3 Drop and insert multiplexer chains 2-4 Drop and insert multiplexer ring 2-5 TN-1X/4 multiplexer - STM-1 routing 2-6 Typical deployment of the TN-1X/4 in an STM-4 access ring 2-7 STM-1 tributary configurations 2-8 TN-1X - single fibre operation 2-10 TN-1X - block diagram 3-1 TN-1X/S - block diagram 3-2 TN-1X - subrack layout 3-4 TN-1X/S - subrack layout 3-5 Automatic laser shutdown operation 3-18 Inter-unit traffic connections 5-2 Tributary Unit/Payload Manager packed TU (secondary) format 5-3 Payload Manager/Aggregate Unit floating AU (primary) format 5-3 TN-1X traffic processing (2 Mbit/s tributaries) 5-5 TN-1X traffic processing (34 Mbit/s tributaries, 16x2) 5-6 TN-1X/4 traffic processing (STM-1 tributaries) 5-7 TN-1X traffic processing (mixed payloads) 5-8 Equipment management bus architecture 6-2 Software upgrade overview 6-11 General network management architecture 6-16 Synchronisation source - block diagram 7-2 SSM within a simple STM-N ring with a single external source 7-6 SSM within a simple STM-N ring with two external sources 7-7 SSM within a simple STM-N ring with two external sources 7-8 SSM within a simple STM-N ring inter-connecting with non-SSM network 7-9 Typical TN-1X rack power cabling and fusing 8-3 TN-1X connection types 9-5 MSP configurations 10-10 MSP protection between rings 10-10 Unidirectional operation 10-11 Bidirectional operation 10-12 Position of loopbacks 12-2 TN-1X unequipped subrack (25GMU00750GWV PCS Level 5) 13-1 TN-1X unequipped subrack (25GMU00750GWV PCS Level 6) 13-2 TN-1X/S unequipped subrack (25G MU00 750 HHX PCS Level 6) 13-3 TN-1X/S unequipped subrack (25G MU00 750 HHX PCS Level 7) 13-4 TN-1X subrack backplane - plug-in unit area 13-6 TN-1X subrack backplane - station interface area 13-7 TN-1X/S subrack backplane 13-8 Station Interface Area cover for 25GMU00750GWV PCS Level 5 13-10 Station Interface Area cover for 25GMU00750GWV PCS Level 6 13-11 EOW handset - TN-1X mounting position 13-12 Local Craft Access Panel 75 Ω - front view 14-2 75 Ω Traffic Access Module (TN-1X) - front and side views 14-4

xi Figure 14-3 Figure 14-4 Figure 14-5 Figure 14-6 Figure 14-7 Figure 14-8 Figure 14-9 Figure 14-10 Figure 14-11 Figure 14-12 Figure 14-13 Figure 14-14 Figure 14-15 Figure 14-16 Figure 14-17 Figure 14-18 Figure 14-19 Figure 14-20 Figure 14-21 Figure 14-22 Figure 14-23 Figure 14-24 Figure 14-25 Figure 14-26 Figure 14-27 Figure 14-28 Figure 14-29 Figure 14-30 Figure 14-31 Figure 14-32 Figure 14-33 Figure 14-34 Figure 14-35 Figure 14-36 Figure 14-37 Figure 14-38 Figure 15-1 Figure 15-2 Figure 15-3 Figure 15-4 Figure 15-5 Figure 15-6 Figure 15-7 Figure 15-8

75 Ω Traffic Access Module (TN-1X) - 2 Mbit/s port allocation 14-5 75 Ω Traffic Access Module (1:N Protection) (TN-1X) - front and side views 14-6 75 Ω Traffic Access Module (1:N Protection) (TN-1X) - 2 Mbit/s port allocation 14-7 75 Ω Traffic Access Module (TN-1X/S) - front and side views 14-8 75 Ω Traffic Access Module (TN-1X/S) - 2 Mbit/s port allocation 14-9 120 Ω Traffic Access Module (TN-1X) - front and side views 14-10 120 Ω Traffic Access Module (TN-1X) - 2 Mbit/s port allocation 14-11 120 Ω Traffic Access Module (1:N Protection) (TN-1X) - front and side views 14-13 120 Ω Traffic Access Module (1:N Protection) (TN-1X) - 2 Mbit/s port allocation 14-14 120 Ω Traffic Access Module (TN-1X/S) - front and side views 14-16 120 Ω Traffic Access Module (TN-1X/S) - 2 Mbit/s port allocation 14-17 High Speed Traffic Access Module - front and side views 14-19 High Speed Traffic Access Module (VC-3) - front and side views 14-21 1:1 Manual Tributary Protection TAM (VC-3) - front and side views 14-23 High Speed Aggregate Module - front and side views 14-25 High Speed Tributary Module - front and side views 14-27 Station Service Module - front and side views 14-29 75 Ω Star Card (25UJ00750GWZ) - front and side views 14-32 75 Ω Star Card (NTKD25AA) - front and side views 14-34 Flexible Termination Module - front and side views 14-36 Flexible Access Module - front and side views 14-37 Power & LCAP Module - front and side views 14-39 Power & LCAP Module - earth strapping pins 14-40 Flexible Access Module (External Alarms) - front and side views 14-42 External Alarms Module - front and side views 14-44 75 Ω Connector Panel 14-46 75 Ω Connector Panel - suggested port connections 14-46 120 Ω Connector Panel 14-47 120 Ω Connector Panel - connector pin allocation 14-47 120 Ω Connector Panel - suggested port connections 14-48 EOW/CATT Connector Panel - front view 14-49 TN-1X 75 Ω traffic cable grooming 14-52 TN-1X 120 Ω traffic cable grooming 14-53 TN-1X/S 75 Ω traffic cable grooming 14-54 TN-1X/S 120 Ω traffic cable grooming 14-54 Connector panel forward and rearward positions 14-55 SDH generalised multiplexing structure 15-2 STM-1 frame structure 15-4 TN-1X - multiplexing structure 15-4 2048 kbit/s tributary/VC-12/TU-12 mapping 15-5 34/45 Mbit/s tributary/VC-3TUG-3/ mapping 15-6 Multiplexing of TU-12 via a TUG-2 15-7 TU-12/TUG-2/TUG-3 multiplexing 15-8 Multiplexing of a TU-3 via a TUG-3 15-9 Nortel TN-1X System Description

xii Figure 15-9 Figure 15-10 Figure 15-11 Figure 15-12 Figure 15-13 Figure 15-14

Multiplexing of three TUG-3s into a VC-4 15-9 Mapping of a VC-4 into a STM-1 via an AU-4/AUG 15-10 VC-12 Path Overhead 15-10 Section overhead 15-12 STM-4 frame structure 15-13 STM-4 section overhead 15-14

Tables Table 3-1 Table 3-2 Table 3-3 Table 3-4 Table 7-1 Table 9-1 Table 10-1 Table 10-2 Table 10-3 Table 11-1 Table 11-2 Table 13-1 Table 14-1 Table 14-2 Table 14-3 Table 14-4 Table 14-5 Table 14-6 Table 14-7 Table 14-8 Table 14-9 Table 14-10 Table 14-11 Table 17-1 Table 17-2 Table 17-3 Table 17-4

323-1061-100 Release 9 Standard

Plug-in unit codes 3-13 TN-1X Interface Module codes 3-15 TN-1X/S Interface Module codes 3-15 Connector Panel codes 3-15 QL settings for use with SSM 7-5 Channel numbering schemes 9-2 K1 byte (bits 1 to 4) usage 10-14 K1 byte (bits 5 to 8) usage 10-15 K2 byte usage 10-15 Performance monitoring points (PMPs) and error counts 11-3 PMP anomalies and defects 11-4 Blank front panels 13-13 Local Craft Access Panel 75 Ω - local terminal connector pin-out 14-2 Station Service Module - rack alarm connector pin-out 14-30 Station Service Module - LAN connector pin-out 14-30 Station Service Module - power connector pin-out 14-30 Station Service Module - earth strapping options 14-31 Power & LCAP Module - power connector pin-out 14-39 Power & LCAP Module- earth strapping options 14-40 Power & LCAP Module - EOW/CATT connector pin-out 14-41 Flexible Access Module (External Alarms) - external alarm connector pin-out 14-43 External Alarm Module - external alarm connector pin-out 14-44 EOW/CATT Connector Panel - local terminal connector pin-out 14-49 Release 9 plug-in unit codes 17-1 Features: 2 Mbit/s Tributary units 17-2 Features: 34/45 Mbit/s Tributary units 17-3 Compatibility of TN-1X Release 9 hardware and software 17-3

xiii

About this document This document provides a system level description of the Nortel Networks TN-1X multiplexer. The document acts as a concise introduction to the equipment and is recommended for anyone working with the TN-1X. 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. Related documents The following documents are referenced within this document: Module Replacement Procedures, Release 9 (NTP 323-1061-547) Unit Descriptions, Release 9 (NTP 323-1061-110) Alarm Clearing Procedures, Release 9 (NTP 323-1061-543) Command Line User Interface Guide, Release 9 (NTP 323-1061-401)

Nortel TN-1X

System Description

xiv

Technical support and information As far as Nortel Networks knows, the information in this document is correct. If, however, you discover any errors or have comments about the arrangement of the content, send details by email to: [email protected] Nortel Networks provides a full technical support service for its customers. The Nortel Networks Service Desk can be called at any time on the following numbers: Within Europe: Freephone

00800 8008 9009

Outside of Europe:

+44 20 8920 4618

Fax within the United Kingdom:

020 8945 3456

Fax outside of the United Kingdom: +44 20 8945 3456 As an option, you can contact technical support through the Nortel Networks web site: www.nortelnetworks.com and by selecting Customer Support.

EMC/Safety conformance This product/product family complies 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.

323-1061-100 Release 9 Standard

1 1-1

System overview

1-

This chapter provides a system overview of the Nortel Networks TN-1X multiplexer.

TN-1X network element There are two versions of the TN-1X, the full-height version (TN-1X) and a reduced-height version (TN-1X/S). Note: Unless there are specific differences, the designation TN-1X is used to refer to the TN-1X and the TN-1X/S. The equipment provides multiplexing between the following tributary and aggregate ports. Tributaries • 2048 kbit/s electrical ports — up to sixty-three 2048 kbit/s electrical ports (TN-1X) — up to sixteen 2048 kbit/s electrical ports (TN-1X/S) •

34368 kbit/s or 45736 kbit/s electrical ports — up to four 34368 kbit/s or 45736 kbit/s ports (TN-1X). Only three of these can carry traffic at any time.

•

34368 kbit/s electrical ports (16x2) — up to four 34368 kbit/s electrical ports (TN-1X), each port providing access to sixteen 2048 kbit/s signals

•

STM-1 tributary ports — up to four STM-1 optical or electrical tributary ports (TN-1X) — up to four STM-1 optical tributary ports (TN-1X/S)

Aggregates It is possible to mix the following aggregate ports up to a maximum of two: • STM-1 aggregate ports — one or two STM-1 optical or electrical aggregate ports (TN-1X) — one or two STM-1 optical aggregate ports (TN-1X/S) •

STM-4 aggregate ports

Nortel TN-1X System Description

1-2 System overview

— one or two STM-4 optical aggregate ports (TN-1X and TN-1X/S). A multiplexer fitted with two STM-4 ports is referred to as TN-1X/4. Note: STM-4 Optical Aggregate units are unavailable to order until further notice. Figure 1-1 shows the external interfaces associated with the TN-1X and the TN-1X/S multiplexers. Figure 1-1 TN-1X - external interfaces

STM-N Aggregate Ports Port A

Port B Rack Alarm Bus

Power

Local Terminal Interface

TN-1X

EOW

Network Management Interface

Synchronisation Input/Output

External Alarms

1 63 2048 kbit/s Electrical Ports

1 4 34368/44736 kbit/s Electrical Ports

1 4 STM-1 Opt/Elec Tributary Ports

TN-1X

STM-N Aggregate Ports Port B

Port A

Local Terminal Interface Power

TN-1X/S

Network Management Interface

EOW External Alarms

1 16 2048 kbit/s Electrical Ports

TN-1X/S

323-1061-100 Release 9 Standard

1 4 STM-1 Optical Tributary Ports

System overview 1-3

The equipment is designed to operate in a managed network environment, however, it is capable of being used in a stand alone mode where a network management infrastructure does not exist. The TN-1X is managed using application software embedded on the TN-1X which performs the internal control and monitoring functions. The configuration and status information is stored in each Network Element (NE) and not in the management tools used to control them. Refer to Chapter 6, “Equipment management” for more information. The TN-1X can be monitored and configured by accessing the User Interface (UI) of the application software. The UI can be accessed either: • locally by a Craft Access Terminal (CAT) connected directly to the TN-1X •

remotely via the Preside EC-1 Element Controller. Note: The TN-1X also provides an interface to the rack alarm system (not applicable to the TN-1X/S).

Two types of UI are available: • Browser User Interface (Browser). This is a point-and-click hypertext interface. The interface is viewed by Netscape Navigator*. For more information on the Browser, refer to the TN-1X Browser User Interface Guide, NTP 323-1061-403. •

Command Line User Interface. This is a text-based interface. For more information on the Command Line User Interface, refer to the TN-1X Command Line User Interface Guide, NTP 323-1061-401.

When used in a managed network environment, the TN-1X multiplexer operates as either: • a ‘gateway network element’ (TN-1X only) which provides an interface to the next layer of the network management hierarchy (for example, element controller) and an interface for remote multiplexers via the Embedded Control Channel (ECC). •

a ‘network element’ (TN-1X and TN-1X/S) which provides an interface to the next layer of the network management hierarchy, or interfaces via the ECC and a ‘gateway network element’.

The ECC is provided by the section overhead in the STM-1 or STM-4 frame structure.

Nortel TN-1X System Description

1

1-4 System overview

Preside EC-1 Element Controller The Preside EC-1 Element Controller is a complete network management application software package, operating at the Element Manager level of the network management hierarchy. The system can be run on a single Hewlett-Packard* UNIX workstation, and uses a Graphical User Interface (GUI) to provide flexible management of Nortel Networks TN-1X, TN-1X/S, TN-1C, TN-1P and Optera Metro 4100 multiplexers. Details of the Preside EC-1 Element Controller are provided in Preside EC-1 Element Controller User Procedures, NTP 323-1091-402. The Element Controller facilities are divided into five main areas: •

Configuration: This function provides the means of adding, copying, modifying, and removing network elements. The Element Controller provides GUI sessions for configuration and connection management, and also provides access to the UI on the NE for further configuration facilities.

•

Alarm/Event Monitoring: Events (changes in status of network entities) and alarms (indications of actual or potential failures) are received as unsolicited reports from the network elements. The Element Controller provides on-screen displays at three different levels of detail (including an Alarm Count only mode), and full event logging and reporting facilities. Performance Monitoring: The TN-1X, TN-1X/S, TN-1C, TN-1P and Optera Metro 4100 NEs have comprehensive performance monitoring facilities, allowing the monitoring of selected points within the multiplexer against a range of performance criteria. The Element Controller uses these facilities to provide powerful report generation features. Security Management: The Element Controller provides security safeguards against unauthorised users, and restricts authorised users to a subset of features appropriate to their role. Data security is provided by automatic daily back-ups of all network data and clear warnings are provided if the system disk becomes too full. Reporting: The reporting function of the Element Controller allows the generation of reports about event logs, performance logs, NE configuration, and faulty equipment.

•

•

•

1:N and remote central archive facility A Remote Central Archive (RCA) facility is provided which allows users to maintain a centralised backup of all configuration, logs, and performance monitoring for a number of Preside EC-1 Element Controllers. During installation, the Preside EC-1 Element Controller may be configured to operate in one of the following modes: • Stand-alone Preside EC-1 Element Controller. The Preside EC-1 Element Controller performs a nightly archive to a local tape. •

Primary Preside EC-1 Element Controller backing up to a warm standby or RCA. The Preside EC-1 Element Controller performs a nightly archive to a local tape and to a remote archive platform. If the primary Preside EC-1 Element Controller losses data, the backup data may be copied from the RCA.

323-1061-100 Release 9 Standard

System overview 1-5

If there is a catastrophic and unrecoverable failure of the primary Preside EC-1 Element Controller: — data may be copied to a cold standby Preside EC-1 Element Controller (allowing this machine to take over the role of the primary Preside EC-1 Element Controller). or — a warm standby Preside EC-1 Element Controller may be switched to the active mode. •

Remote central archive. The RCA platform is a simple repository of archived files from the primary Preside EC-1 Element Controllers (it does not have the Preside EC-1 Element Controller software installed). The RCA performs a daily archive to tape of all the archive data for each primary Preside EC-1 Element Controller.

•

Warm standby. A warm standby Preside EC-1 Element Controller provides two functions: — acts as a RCA for the primary Preside EC-1 Element Controllers in the network. — acts as a standby machine that can quickly take over from another Preside EC-1 Element Controller without having to reload configuration data. Switching to a warm standby machine is controlled by the user (there is no automatic switchover).

•

Cold standby. A cold standby is used if it is not possible to establish OSI communication to the standby EC-1. The cold standby does not need to be powered up until required.

Preside Note: The Preside was previously know as the Integrated Network Manager (INM) or Network Resource Manager (NRM). The Preside EC-1 Element Controller is capable of providing an interface to the Preside. The Preside is a software application which runs on a Hewlett-Packard UNIX workstation, complementing and adding value to the functions provided by Preside EC-1 Element Controllers. It provides a graphical representation of the network and of any alarms collected from the network elements in it. Communication with the system is provided on-screen, via dialogue boxes and menus. Preside provides a single point of access to the existing operations, administration, and maintenance, and provisioning (OAM&P) functions in a network. This includes: • •

Connection and end-to-end trail management. Consolidation of performance monitoring data from multiple Element Controllers and across different network element types.

•

Hierarchical displays, background maps, and partitioned user views.

end of chapter

Nortel TN-1X System Description

1

2-1

System configurations

2-

The TN-1X can be configured to operate as: • A conventional terminal multiplexer fitted with two aggregate units for use in protected point to point configurations. The two aggregate ports, A and B, are used in a main/standby mode to provide 1 for 1 protection for the aggregate ports. •

A drop and insert multiplexer fitted with two aggregate units whereby the two aggregate ports, A and B, provide ‘East’ and ‘West’ ports for connection in drop and insert rings or chains. When connected in a drop and insert ring, protection of the traffic can be provided by alternative routing around the ring, this is not possible when configured in a drop and insert chain.

•

A terminal multiplexer fitted with a single aggregate unit for use in unprotected point to point systems, or as end terminals in a drop and insert chain.

The different configurations for the TN-1X (that is, terminal multiplexer, drop and insert ring, and drop and insert chain) are shown in Figure 2-1.

Nortel TN-1X System Description

2

2-2 System configurations Figure 2-1 Nortel Networks TN-1X - typical system

STM-1

STM-1

(A) Point-to-point subsystem

LAN I/F

Main

Standby 2 Mbit/s

2 Mbit/s

Element Controller

∗

Management LAN STM-1

STM-1

2 Mbit/s

STM-1

2 Mbit/s

STM-1

STM-1 STM-1

(B) Ring subsystem

STM-1 Trib

STM-1

2 Mbit/s

*

STM-1 2 Mbit/s

STM-1

LAN I/F

STM-1 Link (Spur)

STM-1

STM-1

2 Mbit/s

Possible routing to provide flattened ring

* STM-1

STM-1

2 Mbit/s

STM-1

2 Mbit/s

STM-1

STM-1

2 Mbit/s

(C) Drop & insert chain subsystem * TN-1X multiplexers must be used in the positions marked *, as the TN-1X/S does not have a LAN port.

323-1061-100 Release 9 Standard

LAN I/F STM-1 2 Mbit/s

System configurations 2-3

Terminal multiplexer When configured as a conventional terminal multiplexer with two aggregate units, the Nortel Networks TN-1X provides a point-to-point link with inherent 1 for 1 protection (see Figure 2-2). Figure 2-2 Terminal multiplexer A Tributaries

Main

A TN-X

TN-1X

Tributaries

Standby B

B

The 1 for 1 protected terminal multiplexer configuration can be achieved by configuring the multiplexer as a drop and insert multiplexer and either configuring the aggregates for Multiplex Section Protection (MSP) or setting all tributaries as protected connections. An unprotected terminal multiplexer configuration can be achieved by configuring the multiplexer as a drop and insert multiplexer, setting all tributaries as unprotected connections to one aggregate port, and unequipping the unused aggregate port.

Drop and insert multiplexer When configured as a drop and insert multiplexer (also known as an Add/Drop Multiplexer), the Nortel Networks TN-1X can be used in two configurations: • drop and insert chain •

drop and insert ring

Figure 2-3 shows examples of drop and insert chains. When using a simple drop and insert chain as shown in Figure 2-3(a), no protection is provided against faults in the optical path and the multiplexers are configured as unprotected. In this configuration, the end terminals only require a single aggregate port (i.e. unprotected terminal multiplexers as described in the previous section). Flattened rings (see Figure 2-3(b)) make use of existing patterns of ducts and fibres to form a distorted ring. Protection against faults in the optical paths is provided by routing the traffic simultaneously both ways around the ring and configuring the multiplexers as drop and insert multiplexers. However, the flattened ring configuration is susceptible to the common mode faults (e.g. both optical fibres in a duct being broken at the same time).

Nortel TN-1X System Description

2

2-4 System configurations Figure 2-3 Drop and insert multiplexer chains

Tributaries

TN-1X

TN-1X West

Tributaries

East TN-1X Insert

Drop Tributaries

(a)

Drop and insert chain

Added to make flattened ring West Tributaries

East

TN-1X

TN-1X

East

West

East

Tributaries

West

TN-1X Insert

Drop

Tributaries

(b)

Drop and insert chain using flattened ring

Figure 2-4 shows an example of a drop and insert ring. The drop and insert ring provides diverse routing which overcomes common mode faults and thus provides protection against a fault in any optical path. Tributaries that require protection (for example, Private Circuit (PC) traffic) are routed both ways around the ring. At the receiving multiplexer, traffic from one aggregate port is used unless there is a fault when traffic from the other aggregate port is used.

323-1061-100 Release 9 Standard

System configurations 2-5 Figure 2-4 Drop and insert multiplexer ring Tributaries

2 TN-1X

East

Tributaries

West

West

East

East

West

TN-1X

TN-1X

West

Tributaries

East

TN-1X

Tributaries

STM-4 aggregates When STM-4 Aggregate Units are used, each TN-1X/4 multiplexer is used to provide drop and insert facilities for any one of the four AUGs which make up the STM-4 payload. The remaining three AUGs are routed from aggregate unit A to aggregate unit B, and vice-versa, for onward transmission. In this way, the payload in the ‘East’ and ‘West’ directions (see Figure 2-5) is maintained. The TN-1X/4 can also be used to provide the grooming function at the ring head. This requires access to one, two, three or four AUGs within the STM-4 aggregate signal and requires a separate TN-1X/4 multiplexer for each AUG to be accessed. The main application of the TN-1X/4 multiplexer is in optical rings where it is used to provide access to both private and switched traffic as follows: • •

Private Circuit (PC) traffic is routed to other access rings terminating at the same ring head site or alternatively to other remotely sited access rings. Switched traffic is routed to the Digital Local Exchange (DLE).

Whilst most of the traffic flow will be from ring node to ring head, some private circuit traffic will be routed between ring nodes and some switched traffic will be routed between remote switches attached to the ring nodes.

Nortel TN-1X System Description

2-6 System configurations Figure 2-5 TN-1X/4 multiplexer - STM-1 routing STM-4 Optical Aggregate Unit A

East optical traffic

STM-1 STM-4 RX TX

STM-4 STM-1

To/from Payload Manager

3 3

STM-4 Optical Aggregate Unit B STM-1 STM-4 RX TX

STM-4 STM-1

West optical traffic

Figure 2-6 shows a typical deployment of the TN-1X/4 and TN-1X multiplexers in an STM-4 access ring.

323-1061-100 Release 9 Standard

System configurations 2-7 Figure 2-6 Typical deployment of the TN-1X/4 in an STM-4 access ring Higher level network

2 Multiple 2 Mbit/s or STM-1

STM-4/16

STM-1 Multiple 2 Mbit/s

DLE

Private circuits to other STM-1/STM-16 access rings STM-1 Ring node TN-1X/4 STM-4

STM-4 Private circuits

Remote Concentrator Unit

Ring node TN-1X/4

STM-4

Note: All paths are bidirectional.

STM-4 access ring

Ring node TN-1X/4

Remote Concentrator Unit

Remote Concentrator Unit

Ring node TN-1X/4

Private circuits STM-1 spur STM-1 Multiplexer

STM-4 TN-1X

Private circuits

PABX

STM-1 tributaries The TN-1X provides STM-1 tributaries for the connection of partially filled STM-1 spurs and inter-ring connectivity. Figure 2-7 shows examples of the application of STM-1 tributaries.

Nortel TN-1X System Description

2-8 System configurations Figure 2-7 STM-1 tributary configurations

STM-1 Ring

Tributaries STM-1 Tributaries

TN-1X

TN-1X

(a) STM-1 Spur (Unprotected) W = Working P = Protection

STM-4 Ring

W Tributaries

TN-1X/4

TN-1X P STM-1

(b) STM-1 Spur (Protected)

STM-1 Ring

STM-4 Ring

Tributaries TN-1X

TN-1X/4

STM-1

(c) Inter-connection of STM Rings (Unprotected) W = Working P = Protection STM-1 Ring

STM-1 Ring

W TN-1X

TN-1X

P

STM-1

(d) Inter-connection of STM Rings (Protected)

STM-4 Ring TN-1X/4 (AU4-1)

TN-1X/4 (AU4-2)

Tributaries

Tributaries STM-1

(e) Inter-connection of TN-1X/4s using different AU4s in an STM-4 Ring 323-1061-100 Release 9 Standard

System configurations 2-9

Figure 2-7(a) shows the connection of a STM-1 spur from a TN-1X (typically a TN-1X/S situated at the customer premises or in street cabinets) to a TN-1X STM-1 ring. In this application, the TN-1X at the customer premises is configured as an unprotected terminal multiplexer and is connected to a STM-1 Tributary Unit at the TN-1X in the STM-1 ring. No protection is provided for traffic on the spur. Figure 2-7(b) shows the connection of partially filled STM-1 spur from a TN-1X to a TN-1X/4 STM-4 ring using duplicated STM-1 tributaries. In this configuration, Multiplex Section Protection (MSP) is used to provide protection for the spur traffic (see Chapter 10, “Protection” for more details of MSP). In this application, the spur TN-1X is configured as an protected terminal multiplexer with the aggregate ports configured for MSP. The STM-1 tributaries at the TN-1X/4 in the STM-4 ring must also be configured for MSP. In the event of failure of the working path, traffic is automatically switched to the protection path. Figure 2-7(c) shows the interconnection between a TN-1X STM-1 ring and a TN-1X STM-4 ring. In this application, both TN-1Xs are configured as drop and insert multiplexers. No protection is provided for traffic on the spur. Figure 2-7(d) shows the interconnection between two TN-1X STM-1 rings using duplicated STM-1 tributaries. In this application, both TN-1Xs are configured as drop and insert multiplexers with each pair of STM-1 tributaries configured for MSP to provide protection for the inter-connection traffic (see Chapter 10, “Protection” for more details of MSP). In the event of failure of the working path, traffic is automatically switched to the protection path. Figure 2-7(e) shows the interconnection between TN-1X/4s in an STM-4 ring which are dropping/inserting different AU4s, allowing for traffic grooming between AU4s in the ring.

Single fibre working The TN-1X is capable of operating in a single fibre mode whereby 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 converter box (see Figure 2-8). If a break occurs in the single fibre, there is a possibility of the transmitted traffic being echoed by the 2-1 optical converter box to the receive port on the same multiplexer. This signal must be recognised as faulty and Alarm Indication Signal (AIS) transmitted downstream. To recognise the echoed signal, the high-order path trace facility should be used with the transmit and receive path trace settings set to different values and the consequent actions enabled (see “Single fibre working” on page 9-14 for details).

Nortel TN-1X System Description

2

2-10 System configurations Figure 2-8 TN-1X - single fibre operation

Tx Rx

Single Optical Fibre

2-1 Converter

TN-1X

2-1 Converter

TN-1X

Rx Tx

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 Loss of Frame alarm will be raised whilst the multiplexer is achieving frame alignment to the echoed signal. The Loss of Signal alarm is used as a trigger for automatic laser shutdown (ALS), see “Automatic laser shutdown” on page 3-17 for details. In the event of a broken fibre, if the echo is sufficient to constitute a valid signal, the Loss of Signal will not be raised, therefore ALS is not supported when operating in a single fibre mode.

Engineering Order Wire The TN-1X contains provision for an Engineering Order Wire (EOW) facility which provides a dedicated telephone communication system for maintenance purposes between TN-1Xs in a ring or line configuration. The facility only operates over a single ring or chain and does not support branches or multiple rings/chains. A maximum of 99 nodes are allowed in the ring or chain. The EOW system uses the E1 or E2 bytes (hardware selectable) in the STM section overhead to provide a 64 kbit/s voice communication channel between TN-1Xs. If the path section is invalid (i.e. out of alignment), the communication path is disconnected. Note: It is the operators responsibility to ensure the both ends of a path segment are set to use the same EOW byte. The EOW system requires a single EOW Unit at each TN-1X in the network (even at sites where no EOW access is required). The EOW system uses a standard DTMF telephone which is connected to the Local Craft Access Panel on the TN-1X or the EOW/CATT Connector Panel on the TN-1X/S. end of chapter

323-1061-100 Release 9 Standard

3-1

Equipment description

3-

A block diagram of the TN-1X is given in Figure 3-1, a block diagram of the TN-1X/S is given in Figure 3-2. Figure 3-1 TN-1X - block diagram Traffic Processing (Standby)

34 Mbit/s Tributary Unit (16x2)

34368 kbit/s Interfaces (G.703) 34368 kbit/s or 44736 kbit/s Interfaces (G.703)

2048 kbit/s Interfaces (G.703)

Station Battery

Payload Manager (Main)

STM-N Ports Aggregate Unit (B)

STM-1 Tributary Unit

STM-1 Tributary Ports

EOW Handset

Aggregate Unit (A)

34/45 Mbit/s Tributary Unit (VC3)

2 Mbit/s Tributary Unit

EOW Unit

Power Unit

Power

Synchronisation Input/Output

E1/E2 OH Byte Access

Internal Derived Supplies

External Alarms

Monitoring /Control Subrack Controller

Network Management Rack Alarm Bus Local Terminal

Equipment Management

Nortel TN-1X System Description

3

3-2 Equipment description Figure 3-2 TN-1X/S - block diagram Traffic Processing (Standby) STM-1 Tributary Unit

STM-1 Tributary Ports

Payload Manager (Main)

STM-1 Tributary Unit

Aggregate Unit (A) STM-N Ports Aggregate Unit (B)

2048 kbit/s Interfaces (G.703)

EOW Handset

Station Battery

2 Mbit/s Tributary Unit

E1/E2 OH Byte Access

EOW Unit

Power Unit

Monitoring/ Control

Internal Derived Supplies

Power

External Alarms Subrack Controller Local Terminal

Equipment Management

The Nortel Networks TN-1X can be divided functionally into the following areas which are described in subsequent chapters: • •

Chapter 5, “Traffic processing” Chapter 6, “Equipment management”

• •

Chapter 7, “Synchronisation” Chapter 8, “Power”

• •

Chapter 9, “Connectivity” Chapter 10, “Protection”

• •

Chapter 11, “Performance monitoring” Chapter 12, “Diagnostics”

The Nortel Networks TN-1X also provides for optional external alarms and Engineering Order Wire (EOW) facilities.

323-1061-100 Release 9 Standard

Equipment description 3-3

TN-1X subrack The upper section of the subrack houses the plug-in units. The lower section of the subrack is the Station Interface Area (SIA) which houses the Interface Modules and associated cabling, minimising site installation time, and providing easy connector access during maintenance. A moulded cover protects the cables during normal operation. The middle section of the subrack contains a fibre routing tray and a Local Craft Access Panel (LCAP). The fibre routing tray routes the optical fibres from the optical units via adjustable moulded fibre guides to either the left-hand or right-hand side of the subrack. Fibre guides mounted on the side of the subrack allow the fibres to be routed up or down the rack. The Local Craft Access Panel provides easy access to frequently used facilities. There are two variants of the TN-1X unequipped subrack: • 25G MU00 750 GWV (Release 5). This is made from aluminium. •

25G MU00 750 GWV (Release 6). This is made from steel.

Details of the TN-1X subrack are given in Chapter 13, “Construction”.

TN-1X/S subrack The upper section of the subrack houses the plug-in units. The lower section of the subrack is the Station Interface Area which houses the Interface Modules and associated cabling. Additional space should be left below the subrack to enable access to the Service Interface Area for installation and maintenance. Mounted in front of the Interface Modules are a fibre routing tray and the tributary connector panels. The fibre routing tray routes the optical fibres from the optical units via adjustable moulded fibre guides to the left-hand side of the subrack. At the right hand side of the fibre tray, behind the hinged cover, the EOW/CATT Connector Panel provides easy access to frequently used facilities. The 75 Ω or 120 Ω connector panel enables access to all tributary cabling from the front of the subrack and has two positions. The forward position is used whilst the incoming and outgoing tributary cables are being wired to the subrack. The panel is then moved to the rearward position. The special extended screws are threaded at two points to allow the connector panel to be fixed in either position. There are two variants of the TN-1X/S unequipped subrack: • 25G MU00 750 HHX (Release 5). This is made from aluminium. •

25G MU00 750 HHX (Release 6). This is made from steel.

Details of the subrack are given in Chapter 13, “Construction”.

Nortel TN-1X System Description

3

3-4 Equipment description

Subrack layouts The layout of the subrack is shown in Figure 3-3 (TN-1X) and Figure 3-4 (TN-1X/S). The unit subrack position numbers are those used by the software and are indicated above the plug-in units, the subrack slot position is the backplane connector designation. The prefix ‘S’ is used to indicate a plug-in unit slot position, the prefix ‘T’ is used to indicate the Interface Module slot position. These prefixes do not appear on the software screens or the equipment.

21

26

34

42

47 52

Unit Subrack Position

S1

S2

S3

S4

S5

S6

S7

S8

S9 S10 S11

Tributary Unit

1:N Protection Tributary Unit/Spare*

Tributary Unit

Payload Manager A

Aggregate Unit A

62

71

80

S12

S13

S14

Power Unit

Tributary Unit

Tributary Unit

57

Subrack Controller

16

Power Unit

11

Spare**

6

Payload Manager B

1

Aggregate Unit B

Subrack Slot Position

EOW Unit

Figure 3-3 TN-1X - subrack layout

Fibre Storage Tray

25

30

35

40

45

55

65

70

Station Service Module

T9 T10 T11 T12 T13 T14 T15 T16

Not Used

T8

* not spare when a 2” STM-1 Tributary Unit fitted in position S2. ** not spare when a 2” STM-1 Tributary Unit fitted in position S9.

323-1061-100 Release 9 Standard

Low Speed Ports 9 to 16 (S11)

T7

Low Speed Ports 1 to 8 (S11)

T6

Not Used

T5

50

Low Speed Ports 9 to 16 (S9)

T4

Low Speed Ports 1 to 8 (S9)

15

High Speed Aggregate Ports

10

Star Card

1

High Speed Aggregate Ports

T3

Low Speed Ports 9 to 16 (S4)

T2

Low Speed Ports 1 to 8 (S4)

T1

Not Used

Subrack Slot Position

Low Speed Ports 9 to 16 (S2)

Interface Module Subrack Position

Low Speed Ports 1 to 8 (S2)

Station Interface Area

Flexible Access Module

Local Craft Access Panel

80

Equipment description 3-5 Figure 3-4 TN-1X/S - subrack layout Subrack Slot Position Unit Subrack Position

1

6

11

16

21

26

34

42

47

52

57

S1

S2

S3

S4

S5

S6

S7

S8

S9 S10 S11

62

71

80

S12

S13

S14

M1A

Low Speed Ports 1 to 8

Power & LCAP

M1B

Low Speed Ports 9 to 16

Flexible Termination/Ext Alm

Subrack Controller

Power Unit

Power Unit

STM-1 Tributary Unit

Spare*

STM-1 Tributary Unit

Payload Manager

Aggregate Unit

Aggregate Unit

Payload Manager

STM-1 Tributary Unit

Spare*

Tributary Unit

Interface Module Subrack Position

EOW

3

* not spare when a 2” STM-1 Tributary Unit fitted in position S2. ** not spare when a 2” STM-1 Tributary Unit fitted in position S9.

Equipped subrack variants Each equipped subrack variant of the TN-1X and TN-1X/S caters for a specific complement of units (for example, type of aggregate unit, number of tributary units, types of interface module). Each of the individual units also has an unique 8-digit or 13-digit code. Each type of unit may also have a number of variants in order to cater for customer requirements (e.g. front panel details). The codes of the available units are detailed in “Equipment codes” on page 3-12.

Nortel TN-1X System Description

3-6 Equipment description

Plug-in units The TN-1X and TN-X/S subracks provide dedicated plug-in unit positions for the following plug-in units: • Power Unit, (1 or 2 units) which fit into subrack positions S12 and S13.

•

The Power Units provide the regulated d.c. outputs for the other units in the subrack. When two Power Units are fitted, they operate as a load sharing pair. If one of the units fails, the other unit can supply the total power requirement. Subrack Controller, (1 unit) which fits into subrack position S14. The Subrack Controller performs general control and monitoring functions.

•

•

Payload Manager, (1 or 2 units) which fit into subrack positions S5 and S8. The Payload Manager provides a drop and insert facility, and a reordering facility at the TU level of the SDH. TU-3 operation is only possible when using a mixed payload Payload Manager (NTKD10AA). When two units are fitted they operate in a main/standby configuration to provide protection against a Payload Manager or backplane failure. In normal operation, both units are active but the outputs of the standby unit are disabled. EOW Unit, (1 unit) which fits into subrack position S1. Two versions of the EOW Unit are available as follows: — The EOW Unit (25U SV00 750 GVX), also known as ICC1, provides internal telephone communication between TN-1Xs in a network. The unit interfaces with a standard DTMF telephone and provides the analogue/PCM coding/decoding using A-law companding. The 64 kbit/s PCM data is transferred via the backplane overhead bus to the aggregate units for transmission via the E1 or E2 bytes in the section overhead. — The EOW Unit (NTKD13AA), also known as ICC2, provides all the EOW facilities provided by the 25U SV00 750 GVX variant. The unit also is used to control 1:N protection of 2 Mbit/s Tributary Units (see “1:N 2 Mbit/s tributary protection” on page 10-3).

The TN-1X and TN-X/S subracks provide six general purpose tributary unit positions (maximum of five used on TN-1X, maximum of four used on TN-1X/S). The following tributary plug-in units are available: •

2 Mbit/s Tributary Unit, 75 Ω or 120 Ω Each 2 Mbit/s Tributary Unit provides sixteen 2048 kbit/s interfaces, conforming to ITU-T recommendation G.703. For each tributary, the unit performs the mapping of the tributary into a VC-12 of the SDH and generates the TU pointer, thus producing a TU-12. The unit performs the corresponding pointer processing and demapping in the opposite direction.

323-1061-100 Release 9 Standard

Equipment description 3-7

•

STM-1 Tributary Unit, optical or electrical Each STM-1 Tributary Unit provides an STM-1 tributary port with access to a maximum of sixty-three VC-12 channels or three VC-3 channels (or a combination of the two). The unit performs the STM-1 section overhead processing, the TU reordering, and the electrical/optical conversions (STM-1 Optical Tributary Unit) or the CMI coding/decoding (STM-1 Electrical Tributary Unit). Note 1: The TN-1X/S does not support STM-1 Electrical Tributary Units. Note 2: VC-3 operation is only possible using the mixed payload STM-1 Tributary Units (NTKD11AA and NTKD12AA).

•

34 Mbit/s Tributary Unit (16x2), 75 Ω Each 34 Mbit/s Tributary Unit provides a 34368 kbit/s interface, conforming to ITU-T recommendation G.703. The unit performs demultiplexing of the 34368 kbit/s signal according to ITU-T recommendations G.742 and G.751 into sixteen 2048 kbit/s plesiochronous channels. For each channel, the unit performs the mapping of the channel into a VC-12 of the SDH and generates the TU pointer, thus producing a TU-12. The unit performs the corresponding pointer processing, demapping, and multiplexing in the opposite direction. Note: The TN-1X/S does not support 34 Mbit/s Tributary Units.

•

34/45 Mbit/s Tributary Unit (VC3), 75 Ω Each 34/45 Mbit/s Tributary Unit provides a 34368 kbit/s or 44736 kbit/s interface, conforming to ITU-T recommendation G.703. The unit performs the mapping of the tributary into a VC-3 of the SDH and generates the TU pointer, thus producing a TU-3. The unit performs the corresponding pointer processing and demapping in the opposite direction. Note: The TN-1X/S does not support 34/45 Mbit/s Tributary Units.

The TN-1X and TN-X/S subracks provide two general purpose aggregate unit positions for the following plug-in units: • STM-1 Aggregate Unit, optical or electrical — The STM-1 Aggregate Unit performs the STM-1 section overhead processing and the electrical/optical conversions (STM-1 Optical Aggregate Unit) or the CMI line coding/decoding (STM-1 Electrical Aggregate Unit). Note: The TN-1X/S does not support STM-1 Electrical Aggregate Units. •

STM-4 Optical Aggregate Unit — The STM-4 Optical Aggregate Unit performs the STM-4 electrical/ optical conversions, the STM-4 section overhead processing, and the dropping/insertion of one of the AUGs within the STM-4 signal.

The TN-1X and TN-1X/S subrack are designed so that the tributary and aggregate positions can be equipped in later versions of the multiplexer with other tributary and aggregate units to provide a wider range of features. Nortel TN-1X System Description

3

3-8 Equipment description

TN-1X subrack - tributary and aggregate options For present TN-1X subracks, the tributary and aggregate positions can be occupied by the following plug-in units. •

tributaries — 2 Mbit/s Tributary Unit, 75 Ω or 120 Ω (up to 4 units) or STM-1 Optical or Electrical Tributary Unit (up to 4 units) or 34/45 Mbit/s Tributary Unit (VC-3) (up to 4 units) or 34 Mbit/s Tributary Unit (16x2) (up to 4 units) The units fit into subrack positions S2, S4, S9, and S11. The 2” variant of the STM-1 Tributary Unit occupies two slots and can only be fitted in positions S2 and S9 (i.e. unit in position S2 occupies slots S2 and S3, unit in position S9 occupies slots S9 and S10).

•

If 1:N protection is required, a 2 Mbit/s Tributary Unit is fitted in subrack position S3 (see“1:N 2 Mbit/s tributary protection” on page 10-3 for more details of 1:N requirements). aggregates — STM-1 Optical or Electrical Aggregate Unit (up to 2 units) or STM-4 Optical Aggregate Unit, 1310 nm or 1550 nm (up to 2 units) or one STM-1 Aggregate Unit and one STM-4 Aggregate Unit These units fit into subrack positions S6 and S7.

TN-1X/S subrack - tributary and aggregate options For present TN-1X/S subracks, the tributary and aggregate positions can be occupied by the following plug-in units. •

•

tributaries — 2 Mbit/s Tributary Unit, 75 Ω or 120 Ω (1 unit) or STM-1 Optical Tributary Unit (up to 4 units). The 2 Mbit/s Tributary Units fit into subrack positions S2 only. The STM-1 Tributary Units fit into subrack positions S2, S4, S9, and S11. The 2” variant of the STM-1 Tributary Unit occupies two slots and can only be fitted in positions S2 and S9 (i.e. unit in position S2 occupies slots S2 and S3, unit in position S9 occupies slots S9 and S10). aggregates — STM-1 Optical Aggregate Unit (up to 2 units) or STM-4 Optical Aggregate Unit, 1310 nm only (up to 2 units) or one STM-1 Aggregate Unit and one STM-4 Aggregate Unit (1310 nm only)

323-1061-100 Release 9 Standard

Equipment description 3-9

These units fit into subrack positions S6 and S7. Equipping When a card (plug-in unit) is installed in the TN-1X, the user must specify which type of card is installed in each subrack slot. This procedure is known as equipping. If a card is absent when a slot is equipped, or if it is removed while the slot is equipped, an NE-Card_Out alarm is raised. Under certain circumstances, it is possible to re-equip a slot without losing connections. If the new card is in the same card family (e.g. a 2 Mbit/s Tributary Unit is being replaced by a different variant 2 Mbit/s Tributary Unit), the slot may be equipped without first unequipping it and removing all connections. Each card family includes all variants of a card type. Note 1: STM-4 aggregates and STM-1 optical aggregates are regarded as a single card family, referred to as STM-N optical aggregates. Note 2: Some new variants which are direct replacements for existing variants must be equipped as the variant they are replacing (see Table 3-1 for details). Note 3: Cards that are part of an MSP protection pair cannot be unequipped. However, these cards can replaced and re-equipped with cards from the same card family without disrupting MSP settings. If a card is to be permanently removed from a subrack, the subrack slot must be unequipped. Before being unequipped (removed), connections to the card must be deleted. If a card is still present when a slot is unequipped, or if a card is added while a slot is unequipped, an NE-Unexpected_Card alarm is raised.

Interface modules The Interface Modules provide the external electrical connections. There are two types of Interface Modules: • •

Traffic Interface Modules (TIMs) which provide the traffic connectors. Service Interface Modules (SIMs) which provide the general rack connectors.

TN-1X The following SIMs and TIMs are available: •

75 Ω Traffic Access Module. The 75 Ω Traffic Access Module provides connections for eight 2 Mbit/s 75 Ω tributary ports. Two modules are required for the full 16 channels of a 2 Mbit/s Tributary Unit.

•

75 Ω Traffic Access Module 1:N Protection. The 75 Ω Traffic Access Module 1:N Protection provides connections for eight 2 Mbit/s 75 Ω tributary ports. The module also contains the relays used to switch traffic when 1:N protection is employed. Two modules are required for the full 16 channels of a 2 Mbit/s Tributary Unit. Nortel TN-1X System Description

3

3-10 Equipment description

•

120 Ω Traffic Access Module. The 120 Ω Traffic Access Module provides connections for eight 2 Mbit/s 120 Ω tributary ports. Two modules are required for the full 16 channels of a 2 Mbit/s Tributary Unit.

•

120 Ω Traffic Access Module 1:N Protection. The 120 Ω Traffic Access Module 1:N Protection provides connections for eight 2 Mbit/s 120 Ω tributary ports. The module also contains the relays used to switch traffic when 1:N protection is employed. Two modules are required for the full 16 channels of a 2 Mbit/s Tributary Unit.

•

High Speed Traffic Access Module (16x2). The High Speed Traffic Access Module provides connections for a 34 Mbit/s 75 Ω tributary port. High Speed Traffic Access Module (VC-3). The High Speed Traffic Access Module provides connections for a 34 Mbit/s or 45 Mbit/s 75 Ω tributary port.

•

•

1:1 Manual Tributary Protection Traffic Access Module (VC-3). This unit provides no connections, but receives traffic from a High Speed Traffic Access Module (VC-3) via the Star Card.

•

High Speed Aggregate Module. The High Speed Aggregate Module provides connections for a STM-1 electrical aggregate port. High Speed Tributary Module. The High Speed Tributary Module provides connections for a STM-1 electrical tributary port.

• • • •

Station Service Module. The Station Service Module provides connections for the rack alarm bus, the management Q3 port (LAN), and power. 75 Ω Star Card. The 75 Ω Star Card provides connections for the external synchronisation timing ports. Flexible Access Module. The Flexible Access Module provides the connections to the LCAP. A variant is provided that also provides connections to the LCAP and connections for up to 5 external alarms.

TN-1X/S The following SIMs and TIMs are available: •

75 Ω Traffic Access Module. The 75 Ω Traffic Access Module provides connections for eight 2 Mbit/s 75 Ω tributary ports to the 75 Ω Connector Panel. Two modules are required for the full 16 channels of a 2 Mbit/s Tributary Unit.

•

120 Ω Traffic Access Module. The 120 Ω Traffic Access Module provides connections for eight 2 Mbit/s 120 Ω tributary ports to 120 Ω Connector Panel. Two modules are required for the full 16 channels of a 2 Mbit/s Tributary Unit. Flexible Termination Module. The Flexible Termination Module fills the empty position in the SIA below the Power & LCAP (Local Craft Access Panel) module and maintains EMC screening.

•

•

Power & LCAP Service Interface Module. The Power & LCAP Service Interface Module provides the connector for power and through connections to the EOW/CATT connector panel.

323-1061-100 Release 9 Standard

Equipment description 3-11

•

External Alarm Interface Module.The External Alarm Interface Module is fitted instead of Flexible Termination Module if external alarm facilities are required and provides the connections for up to 5 external alarms.

TIM allocation - TN-1X The allocation of the TIMs to the 2 Mbit/s Tributary Units in the TN-1X subrack is as follows: TIM in position T2 provides 2048 kbit/s ports 1 to 8 for position S2 TIM in position T3 provides 2048 kbit/s ports 9 to 16 for position S2 TIM in position T5 provides 2048 kbit/s ports 1 to 8 for position S4 TIM in position T6 provides 2048 kbit/s ports 9 to 16 for position S4 TIM in position T10 provides 2048 kbit/s ports 1 to 8 for position S9 TIM in position T11 provides 2048 kbit/s ports 9 to 16 for position S9 TIM in position T13 provides 2048 kbit/s ports 1 to 8 for position S11 TIM in position T14 provides 2048 kbit/s ports 9 to 16 for position S11 The allocation of the TIMs to the 34/45 Mbit/s Tributary Units (VC-3) in the TN-1X subrack is as follows: TIM in position T3 provides 34368 or 44736 kbit/s port for position S2 TIM in position T6 provides 34368 or 44736 kbit/s port for position S4 TIM in position T11 provides 34368 or 44736 kbit/s port for position S9 TIM in position T14 provides 34368 or 44736 kbit/s port for position S11 The allocation of the TIMs to the 34 Mbit/s Tributary Units (16x2) in the TN-1X subrack is as follows: TIM in position T3 provides 34368 kbit/s port for position S2 TIM in position T6 provides 34368 kbit/s port for position S4 TIM in position T11 provides 34368 kbit/s port for position S9 TIM in position T14 provides 34368 kbit/s port for position S11 The allocation of the TIMs to the STM-1 Electrical Tributary Units is as follows: TIM in position T3 provides STM-1 port for position S2 TIM in position T6 provides STM-1 port for position S4 TIM in position T11 provides STM-1 port for position S9 TIM in position T14 provides STM-1 port for position S11 The allocation of the TIMs to the STM-1 Electrical Aggregate Units is as follows: TIM in position T7 provides STM-1 port for position S6 TIM in position T9 provides STM-1 port for position S7 TIM allocation - TN-1X/S The allocation of the TIMs to the 2 Mbit/s Tributary Units in the TN-1X/S subrack is as follows: TIM in position M1A provides 2048 kbit/s ports 1 to 8 for position S2 TIM in position M1B provides 2048 kbit/s ports 9 to 16 for position S2

Nortel TN-1X System Description

3

3-12 Equipment description

Connector panels The connector panels are located at the front of the Station Interface Area of the TN-1X/S. • 75 Ω Connector Panel. The panel provides SMB connections for sixteen 2 Mbit/s 75 Ω tributary ports. • •

120 Ω Connector Panel. The panel provides four 25-way D-type connections for sixteen 2 Mbit/s 120 Ω tributary ports. EOW/CATT Connector Panel. The panel provides access to the subrack alarm facilities (alarm LEDs, receiving attention push-button switch) and the local terminal and EOW connectors.

Details of the Connector Panels are given in Chapter 14, “External interfaces”.

Local Craft Access Panel The Local Craft Access Panel (LCAP) is mounted centrally at the front of the TN-1X subrack and provides the interfaces commonly used by installation and maintenance engineers, together with the subrack alarm facilities. The right-hand side of the panel contains the subrack alarm facilities (alarm LEDs, receiving attention push-button switch), and an ESD bonding point. A hinged cover on the face plate provides access to the commonly used connectors. The LCAP interfaces with the Subrack Controller via the SIM in position T1. Details of the LCAP are given in a Chapter 14, “External interfaces”.

Equipment codes Each unit has a unique 8-digit or 13-digit code. Each type of unit may have more than one variant in order to cater for specific customer requirements (e.g. front panel language). •

Table 3-1 details the currently available plug-in units

• •

Table 3-2 details the currently available Interface Modules on the TN-1X Table 3-3 details the currently available Interface Modules on the TN-1X/S

•

Table 3-4 details the currently available Connector Panels on the TN-1X/S

323-1061-100 Release 9 Standard

Equipment description 3-13 Table 3-1 Plug-in unit codes Applicability Unit Type

Code TN-1X

TN-1X/S

Power Units NTKD24AA

√

√

NTKD19AB

√

√

Payload Manager (VC-12 Payload only)

NTKD10CA

√

√

Payload Manager (Mixed Payload)

NTKD10AA

√

√

STM-1 Optical Aggregate Unit (1310 nm Long Haul)

NTKD20AA

√

√

STM-1 Optical Aggregate Unit (1550 nm)

NTKD21AA

√

√

25U TM00 750 GWB

√

2 Mbit/s Tributary Unit 75 Ω

NTKD23AA (see Note 1)

√

√

2 Mbit/s Tributary Unit 120 Ω

NTKD23AB (see Note 1)

√

√

25U JU00 750 HJZ

√

NTKD16AC

√

NTKD11AA

√

Power Unit 120 W Subrack Controllers Subrack Controller (4M RAM) Payload Managers

STM-1 Optical Aggregate Units

STM-1 Electrical Aggregate Units STM-1 Electrical Aggregate Unit 2 Mbit/s Tributary Units

34 Mbit/s Tributary Units (16x2) 34 Mbit/s Tributary Unit (16x2) 34/45 Mbit/s Tributary Units (VC-3) 34/45 Mbit/s Tributary Unit (see Note 3) STM-1 Optical Tributary Units STM-1 Optical Tributary Unit 1”

√

continued

Nortel TN-1X System Description

3

3-14 Equipment description Table 3-1 Plug-in unit codes (continued) Applicability Unit Type

Code TN-1X

TN-1X/S

STM-1 Electrical Tributary Units NTKD12AA (see Note 2)

√

25U EP00 750 GXB

√

EOW Unit (ICC2)

NTKD13AA

√

EOW Handset Kit

25S KM00 750 HZM

√

STM-1 Electrical Tributary 1” (Mixed Payloads) LCAPs Local Craft Access Panel 75 Ω EOW Units

√

Note 1: The NTKD23AA must be equipped as a 25U JU00 750 HVT unit and the NTKD23AB must be equipped as a 25U JU00 750 HVQ unit. Note 2: The NTKD12AA can be used as a direct replacement for the STM-1 Electrical Tributary Unit 2" 25U JU00 750 JBK Note 3: The NTKD16AC reports AIS on the 45 Mbit/s side. NTKD16AC only works with release 9 software. Note 4: STM-4 Optical Aggregates 25U TM00 750 GSA, 25U TM00 750 GSC and 25U TM00 750 HVB are applicable to Release 9 but are not currently available to order until further notice. —end—

323-1061-100 Release 9 Standard

Equipment description 3-15 Table 3-2 TN-1X Interface Module codes Interface Module

Code

75 Ω Traffic Access Module

25U JJ00 750 GVZ

75 Ω Traffic Access Module (1:N Protection)

NTKD14AA

120 Ω Traffic Access Module

25U JJ00 750 HLV

120 Ω Traffic Access Module (1:N Protection)

NTKD15AA

High Speed Traffic Access Module (16x2)

25U JJ00 750 HTD

High Speed Traffic Access Module (VC-3)

NTKD17AA

1:1 Manual Tributary Protection Module (VC-3)

NTKD17AB

High Speed Aggregate Module

25U JJ00 750 GYZ

High Speed Tributary Module

25U JJ00 750 GWY

Station Service Module

25U JJ00 750 GXC

75 Ω Star Card

25U JJ00 750 GWZ

75 Ω Star Card (1:1 Manual Trib Protection)

NTKD25AA

Flexible Access Module

25U JJ00 750 GWX

Flexible Access Module - Ext Alarms

25U JJ00 750 HPD

Table 3-3 TN-1X/S Interface Module codes Interface Modules

Codes

75 Ω Traffic Access Module

25U JJ00 750 HHZ

120 Ω Traffic Access Module

25U JJ00 750 HJA

Flexible Termination Module

25U JJ00 750 HJD

Power & LCAP Module

25U JJ00 750 HJB

External Alarm Module

25U JJ00 750 HPF

Table 3-4 Connector Panel codes Connector Panel

Code

75 Ω Connector Panel

25R PN00 021 AAF

120 Ω Connector Panel

25R PN00 021 AAG

EOW/CATT Connector Panel

25U EP00 750 HJC

Nortel TN-1X System Description

3

3-16 Equipment description

TN-1X subrack codes Each TN-1X equipped subrack comprises an unequipped subrack (25G MU00 750 GWV) and the required complement of plug-in units (see Table 3-1) and Interface Modules (see Table 3-2). TN-1X/S subrack codes Each TN-1X/S equipped subrack comprises an unequipped subrack (25G MU00 750 HHX) and the required complement of plug-in units (see Table 3-1) and Interface Modules (see Table 3-3). Blank panel codes All unused plug-in unit and Interface Module positions must be fitted with blank front panels. Codes for the relevant blank front panels are as follows: 1" Plug-in Unit Dummy Panel: 25R BN00 021 AAB 1.6" Plug-in Unit Dummy Panel:

25R BN00 021 AAC

1.8" Plug-in Unit Dummy Panel:

25R BN00 021 AAD

1" Interface Module Dummy Panel:

25R BN00 021 AAA

Service Interface Module Flexible Termination:

25U JJ00 750 HJD

Inventory The TN-1X provides inventory information that allows the user to uniquely identify a network component. For the TN-1X, the following information is available for each plug-in unit and TAM: •

Card type - identifies the card type and variant. For example, the 25U JU00 750 HVT variant of the 75 Ω 2 Mbit/s tributary unit has a card type of ‘2M_Trib-75ohm_HVT’.

•

Nortel Networks order code. Typically, this is an eight character code. Where thirteen character codes are used, the first five characters are omitted. That is, ‘25UJU00750GVA’ becomes ‘00750GVA’. Newer cards have the highest PCS level on the card appended to this code as a two digit suffix. For example, the ‘NTKD17AB’ TAM with a PCS level of 1 has a code of ‘NTKD17AB01’.

•

Serial number - unique serial number that is identical to the bar-coded serial number of the assembled unit.

•

Date of manufacture - week and year of manufacture (e.g. ‘1098’ indicates that the unit was manufactured in Week 10 in 1998). Note: For warranty purposes, the date label attached to the unit is the definitive date not the manufacture date.

•

Checksum - checksum for the integrity of unit of the previous inventory information.

323-1061-100 Release 9 Standard

Equipment description 3-17

Note 1: For some older plug-in units and TAMs, the serial number, date of manufacture, checksum, and product control level information may not be available. Note 2: Where a card is a direct replacement for a previous variant of the card, the inventory report will give the code of the new variant but the description of the old variant.

Automatic laser shutdown Note: Automatic laser shutdown is not supported if the multiplexer is operating in a single fibre mode. The STM-1 Optical Aggregate Units, STM-1 Optical Tributary Units and the STM-4 Optical Aggregate Units contain an Automatic Laser Shutdown (ALS) circuit which shuts down the laser if an OS-Optical_Power_High or an RS-LOS alarm occurs. This prevents excessive optical power being radiated from a broken fibre or an unterminated optical connector. The laser is shut down if the RS-LOS alarm is present for greater than approximately 525 ms or immediately by an OS-Optical_Power_High alarm. If the RS-LOS alarm clears, the laser is switched back on immediately. If the shutdown is initiated by an OS-Optical_Power_High alarm, the laser can not be restarted until the unit is reset (e.g. removed and replaced in the subrack). On power-up of the unit, the laser is held on for 2 seconds irrespective of the alarm conditions. The automatic restart periodically forces the laser on for 2 seconds until the laser restart is successful. The period between laser restarts is dependent on the variant as follows: 64 seconds:

STM-1 Aggregate Unit (25U TM00 750 GWA) STM-4 Aggregate Units (25U TM00 750 GSA, GSC, HVB) STM-1 Tributary Unit (25U JU00 750 GVA)

72 seconds:

STM-1 Aggregate Unit (25U TM00 750 HWF, NTKD20AA) STM-1 Tributary Unit (25U TM00 750 HWE, HWG, NTKD11AA)

The initial delay before a laser restart pulse is dependent on the variant as follows: 72 seconds:

STM-1 Aggregate Unit (25U TM00 750 GWA)

90 seconds:

STM-1 Aggregate Unit (NTKD20AA, 25U TM00 750 HWF) STM-1 Tributary Unit (25U TM00 750 HWE, HWG, NTKD11AA)

94 seconds

STM-4 Aggregate Units (25U TM00 750 GSA, GSC, HVB) STM-1 Tributary Unit (25U JU00 750 GVA)

Nortel TN-1X System Description

3

3-18 Equipment description

The longer initial delay allows for interactions between section ends if a fibre break occurs in one direction only. The operation of the automatic laser shutdown for STM-1 Aggregate Unit 25U TM00 750 GWA, with reference to Figure 3-5, is described in the following paragraphs. Figure 3-5 Automatic laser shutdown operation STM-1 Aggregate Unit

STM-1 Aggregate Unit

TX

RX ‘X’ Fibre Break

RX

Terminal ‘A’

TX

Terminal ‘B’

If a fibre break at point ‘X’ occurs, Terminal A raises an RS-LOS alarm which causes the laser at Terminal A to shutdown approximately 525 ms after the fibre breaks. Terminal B raises an RS-LOS alarm approximately 525 ms after the fibre breaks, this causes the laser at Terminal B to be shutdown 525 ms after the alarm is detected (i.e. approximately 1.05 seconds after the fibre break). Thus the optical power at the point ‘X’ is removed approximately 1.05 seconds after the fibre breaks. Whilst the break is present, an automatic laser restart is attempted at Terminal A by removing the laser shutdown signal to the laser for 2 seconds every 62 seconds. The laser at Terminal A is switched on for 2 seconds which removes the RS-LOS alarm, and thus the laser shutdown signal, at Terminal B for 2 seconds. The laser at Terminal B is switched on for 2 seconds, however, the signal from the Terminal B does not reach Terminal A due to the fibre break. An RS-LOS is therefore still present at Terminal A after the 2 seconds restart signal and the laser shutdown signal is reapplied. This sequence is repeated every 64 seconds. Once the break has been repaired, an automatic laser restart is performed at Terminal A, removing the laser shutdown signal to the laser for 2 seconds. The laser is switched on for 2 seconds which removes the RS-LOS alarm, and thus the laser shutdown signal, at Terminal B for 2 seconds. The laser at Terminal B is switched on which, as the break is fixed, removes the RS-LOS alarm at Terminal A and disables the laser shutdown signal.

323-1061-100 Release 9 Standard

Equipment description 3-19

The STM-4 Optical Aggregate Unit, STM-1 Optical Tributary Unit and the latest versions of the STM-1 Optical Aggregate Unit (variant NTKD20AA, 25U TM00 750 HWF) contain an ALS circuit which differs in operation from that described in the previous paragraphs in that the laser is also shutdown immediately if: • STM-4 Optical Aggregate Unit: an OS-Optical_Power_Low and a OS-Laser_Bias_High condition (indicating failure of the laser back diode used by the feedback circuit on the optical transmitter module). If the shutdown is initiated by an OS_Optical_Power_Low/ OS-Laser_Bias_High alarm combination, the laser can not be restarted until the unit is reset. •

STM-1 Optical Tributary Unit and STM-1 Optical Aggregate Unit (variant NTKD20AA, 25U TM00 750 HWF): a Clock Fail condition (dedicated ALS clock). If the shutdown is initiated by a Clock Fail condition, the laser can not be restarted until the unit is reset.

Laser test facility The following units provide a test facility which overrides the laser shutdown mechanism: • NTKD20AA, 25U TM00 750 HWF (identifiable by a second yellow LED on the front panel) and latest versions of the STM-1 Optical Aggregate Units 25U TM00 750 GWA • •

STM-1 Optical Tributary Unit STM-4 Optical Aggregate Unit

The override enables the laser for 90 seconds in order for optical power measurements to be made. For safety reasons, the laser shutdown override will not operate if an Optical High Power alarm is present. For details of the link options, see the Module Replacement Procedures, NTP 323-1061-547, or the Unit Descriptions, NTP 323-1061-110. end of chapter

Nortel TN-1X System Description

3

4-1

System parameters

4-

This chapter provides the performance specifications for the TN-1X and TN-1X/S multiplexers.

Power requirements Input supply Two independent separately fused d.c. supplies (per subrack) in the range 40 V to 72 V, positive earth. A 7 A fuse should be fitted to each supply. Power consumption Typical power consumptions for each of the units are listed below: Subrack Controller: 11.0 W Payload Manager: 10.3 W 2 Mbit/s Tributary Unit: 8.2 W 34 Mbit/s Tributary Unit (16x2): 8.05 W 34/45 Mbit/s Tributary Unit (VC-3): 9 W STM-1 Optical Aggregate Unit: 7.9 W STM-1 Electrical Aggregate Unit: 10.1 W STM-4 Optical Aggregate Unit: 21.9 W STM-1 Optical Tributary Unit (2”): 10.9 W STM-1 Optical Tributary Unit (1”): 8.0 W STM-1 Electrical Tributary Unit: 12.9 W EOW Unit: 8.0 W The efficiency of the Power Units is greater than 75%.

Construction Equipment practice External dimensions conform to draft ETSI standard pr ETS 300-119 part 4. TN-1X subrack Height: Width: Depth:

525 mm, 21 Standard Unit (SU) where a SU is equivalent to 25 mm. 450 mm 535 mm including flanges 250 mm (without plug-in units)

Nortel TN-1X System Description

4

4-2 System parameters

TN-1X/S subrack Height: 325 mm, 13 SU Width: 450 mm 535 mm including flanges Depth: 250 mm (without plug-in units) Plug-in unit aperture dimensions Height: 266.7 mm Width: 426.72 mm, 84 pitches of 5.08 mm Cable interface area dimensions Height: 266.7 mm (TN-1X) 50 mm (TN-1X/S) Width: 426.72 mm Plug-in units Height: Depth: Widths:

233 mm (excluding ejectors levers) 220 mm (excluding connectors and front panel) n x 5.05 mm, where n = 5, 8, 9 or 10.

Interface modules TN-1X Height: 250 mm (excluding ejectors levers) Depth: 55 mm (excluding connectors and front panel) Widths: n x 5.05 mm, where n = 5 or 8. TN-1X/S • Traffic interface modules

•

Height: 25.5 mm Depth: 55 mm (excluding connectors and front panel) Width: 250 mm (excluding ejectors levers) Station interface modules Height: 25.5 mm Depth: 55 mm (excluding connectors and front panel) Width: 160 mm (excluding ejectors levers)

Weight TN-1X subrack Unequipped subrack: 8 kg Fully equipped TN-1X subrack: 20 kg (maximum). TN-1X/S subrack Unequipped subrack: 9.5 kg Fully equipped TN-1X/S subrack: 18 kg (maximum).

323-1061-100 Release 9 Standard

System parameters 4-3

System interfaces Most external system interfaces are made via Interface Modules in the Station Interface Area of the TN-1X subrack or via Connector Panels in the Station Interface Area of the TN-1X/S subrack. Different Interface Module and Connector Panel types are available to cater for specific customer connector requirements. Optical interfaces are made via optical connectors on the front of the optical units. The Local Craft Access Panel (LCAP) on the TN-1X and the EOW/CATT Connector Panel on the TN-1X/S provide interfaces for frequently used features (for example, local terminal). 2048 kbit/s traffic 2 Mbit/s tributary inputs and outputs interfaces conform to ITU-T recommendation G.703 as follows: Line rate: Line code: Access impedance: Output pulse height: Nominal pulse width: Cable loss to input:

Input return loss:

Output return loss:

2048 kbit/s ± 50 ppm High Density Bipolar 3 (HDB3) 75 Ω or 120 Ω ±2.37 V ± 10% (75 Ω) peak ±3 V ± 10% (120 Ω) peak 244 ns 0 dB to 6 dB at 1024 kHz, typically maximum of 330 m of 2002 cable typically maximum of 470 m of 2003 cable typically maximum of 280 m of 3002 cable not less than 12 dB in the range 50 kHz to 100 kHz not less than 18 dB in the range 100 kHz to 2048 kHz not less than 14 dB in the range 2048 kHz to 3072 kHz not less than 6 dB in the range 512 kHz to 1024 kHz not less than 8 dB in the range 1024 kHz to 3072 kHz.

34368 kbit/s traffic 34 Mbit/s tributary inputs and outputs interfaces conform to ITU-T recommendation G.703 as follows: Line rate: Line code: Access impedance: Output pulse height: Nominal pulse width: Cable loss to input:

34368 kbit/s ± 20 ppm High Density Bipolar 3 (HDB3) 75 Ω 1.0 V ± 0.1 V peak 244 ns 0 dB to 12 dB at 17184 kHz, typically maximum of 250 m of 2003 cable

Nortel TN-1X System Description

4

4-4 System parameters

Input return loss:

Output return loss:

not less than 12 dB in the range 860 kHz to 1720 kHz not less than 18 dB in the range 1720 kHz to 34368 kHz not less than 14 dB in the range 34368 kHz to 51550 kHz not less than 6 dB in the range 859.2 kHz to 1718.4 kHz not less than 8 dB in the range 1718.4 kHz to 51552 kHz.

44736 kbit/s traffic 45 Mbit/s tributary inputs and outputs interfaces conform to ITU-T recommendation G.703 and ANSI DS-3/TR-NW-000499 as follows: Line rate: 44736 kbit/s ± 20 ppm Line code: B3ZS Access impedance: 75 Ω Output 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 - long haul (1310 nm) The STM-1 long haul aggregate/tributary optical inputs and outputs exceed ITU-T recommendation G.957 (application code L-1.1) for 155,520 kbit/s STM-1 signals. The optical interface is as follows: Output power: maximum 0 dBm minimum –5 dBm nominal –2.5 dBm Receiver sensitivity: –35.5 dBm (error rate 1 in 1010) Receiver overload: 0 dBm Optical path penalty: 1 dB Section loss: 0 dB to 29.5 dB (TN-1X to TN-1X) Wavelength (nominal): 1310 nm Spectral range: 1285 nm to 1330 nm Fibre type: monomode. STM-1 optical - long haul (1550 nm) The STM-1 long haul aggregate optical inputs and outputs exceed ITU-T recommendation G.957 (application code L-1.2) for 155,520 kbit/s STM-1 signals. The optical interface is as follows: Output power: maximum +4 dBm minimum -1.0 dBm nominal 1.5 dBm Receiver sensitivity: –34.5 dBm (error rate 1 in 1010) Receiver overload: -6 dBm Optical path penalty: 1.0 dB Section loss: 10 dB to 33.5 dB (TN-1X to TN-1X) (error rate 1 in 1010) 323-1061-100 Release 9 Standard

System parameters 4-5

Wavelength (nominal): 1550 nm Spectral range: 1540 nm to 1560 nm Fibre type: monomode. STM-1 optical - short haul (1310 nm) The STM-1 short haul aggregate/tributary optical inputs and outputs exceed ITU-T recommendation G.957 (application code S-1.1) for 155,520 kbit/s STM-1 signals. The optical interface is as follows: Output power:

maximum –8 dBm minimum –13.5 dBm nominal –10 dBm Receiver sensitivity: –34.5 dBm (error rate 1 in 1010) Receiver overload: 0 dBm Optical path penalty: 1 dB Section loss: 0 dB to 20 dB (TN-1X to TN-1X) Wavelength (nominal): 1310 nm Spectral range: 1280 nm to 1335 nm Fibre type: monomode. STM-1 electrical The STM-1 aggregate/tributary electrical inputs and outputs conform to ITU-T recommendation G.703 for 155,520 kbit/s STM-1 signals. The electrical interface is as follows: Line code: Coded Mark Inversion (CMI) Access impedance: 75 Ω Input and Output Return Loss: not less than 15 dB in the range 8 MHz to 240 MHz Cable loss to input: 0 dB to 12.7 dB at 78 MHz (maximum of 120 m of 2003 cable) Output pulse height: 1.0 V ± 0.1 V peak. STM-4 optical aggregate - long haul 1310 nm The STM-4 long haul aggregate optical inputs and outputs exceed ITU-T recommendation G.957 (application code L-4.1) for 622,080 kbit/s STM-4 signals. The optical interface is as follows: Output power: maximum +2 dBm minimum –3 dBm nominal –0.5 dBm Receiver sensitivity: –32.5 dBm (error rate 1 in 1010) Receiver overload: –6 dBm Optical path penalty: 1 dB Section loss: 8 dB to 28.5 dB (TN-1X to TN-1X) Wavelength (nominal): 1310 nm Spectral range: 1298 nm to 1323 nm Fibre type: monomode.

Nortel TN-1X System Description

4

4-6 System parameters

STM-4 optical aggregate - intra-office 1310 nm The STM-4 intra-office aggregate optical inputs and outputs exceed ITU-T recommendation G.957 (application code I-4) for 622,080 kbit/s STM-4 signals. The optical interface is as follows: Output power:

maximum –8 dBm minimum –14 dBm nominal –11 dBm Receiver sensitivity: –27 dBm (error rate 1 in 1010) Receiver overload: –5 dBm Optical path penalty: 1 dB Section loss: 0 dB to 12.5 dB (TN-1X to TN-1X) Wavelength (nominal): 1310 nm Spectral range: 1200 nm to 1348 nm Fibre type: monomode. STM-4 optical aggregate - long haul 1550 nm The STM-4 long haul 1550 nm aggregate optical inputs and outputs exceed ITU-T recommendation G.957 (application code L-4.2) for 622,080 kbit/s STM-4 1550 nm signals. The optical interface is as follows: Output power:

maximum +2 dBm minimum –3 dBm nominal -0.5 dBm Receiver sensitivity: –34 dBm (error rate 1 in 1010) Receiver overload: –6 dBm Section loss: 8 dB to 30 dB (TN-1X to TN-1X) Optical path penalty: 1 dB Wavelength (nominal): 1550 nm Spectral range: 1540 nm to 1560 nm Fibre type: monomode. Rack alarm bus The rack alarm bus interface (not applicable to the TN-1X/S) provides a connection to the standard 10-way ribbon interface for connection, if applicable, to the Rack Alarm Unit (RAU) at the top of the rack. Local terminal The local terminal port is an RS232C asynchronous interface working at 19.2 kbit/s. Connection is via a 25-way D-type connector on the Local Craft Access Panel (TN-1X) or the EOW/CATT Connector Panel (TN-1X/S). Network management The network management port (not applicable to the TN-1X/S) is an Ethernet Local Area Network (LAN) Open Systems Interconnect (OSI) model conforming to ISO 8802.3 with Carrier Sense Multiple Access with Collision Detection (CSMA/CD). The physical interface is an Attachment Unit Interface (AUI) for connection with a LAN transceiver mounted in the same rack.

323-1061-100 Release 9 Standard

System parameters 4-7

Provision is made for communication with remote multiplexers via the Embedded Control Channel (ECC) within the STM-1 frame (bytes D1 to D3 or D4 to D12 in the section overhead). External synchronisation input and output The synchronisation inputs and outputs conform to ITU-T recommendation G.703 for 2048 kHz clock signals. No synchronisation inputs or outputs are provided on the TN-1X/S. External alarms Five closed contact inputs (i.e. floating inputs with no earth provided) with following characteristics: Open circuit condition: Greater than 1 MΩ (Normal active alarm state) Short circuit condition: Less than 200 Ω (Normal non-active alarm state) Electrical protection: Alarm inputs protected against accidental connection to a supply battery with a steady state voltage up to 72 V. Engineering Order Wire (EOW) The EOW system uses the E1 or E2 Orderwire bytes in the STM section overhead. All TN-1Xs on a ring or line system must be equipped with an EOW Unit. Maximum number of nodes: 99 Facilities: point-to-point calls broadcast ringing conference call (maximum of 4 parties on a conference call) Signalling: DTMF Telephone socket: Type 603A socket

ElectroMagnetic compatibility The subrack is designed to meet the Class B requirements of European Standard EN 55022.

Environmental conditions The subrack is designed to meet the requirements of ETSI standard ETS 300-019 as follows: Storage: Transport: Operation:

Class 1.2 Class 2.3 Class 3.1E.

Nortel TN-1X System Description

4

4-8 System parameters

Thermal qualifications •

•

•

• •

A maximum of three TN-1Xs fitted with STM-1 aggregates can be equipped per 2.2 m ETSI rack and will operate over the full ambient temperature range of –5°C to 45°C. No air gap is required between the subracks. Two TN-1Xs in a 2.2 m ETSI rack, both fitted with STM-4 aggregates, will operate over the full ambient temperature range of –5°C to 45°C if a 525 mm air gap is provided between the subracks. Two TN-1Xs in a 2.2 m ETSI rack, both fitted with STM-4 aggregates, will operate over the full ambient temperature range of –5°C to 35°C with no air gap between the subracks. Three TN-1Xs fitted with STM-4 aggregates per 2.2 m ETSI rack is not recommended. One TN-1X or one TN-1X/S, with any configuration of aggregates and tributaries, can be equipped in a Clifton or Quante street cabinet and will operate over the full ambient temperature range of –5°C to 45°C. The ambient temperature range of operation in other street cabinets will depend on the thermal performance of the cabinet.

end of chapter

323-1061-100 Release 9 Standard

5-1

Traffic processing

5-

This chapter provides information on traffic processing on the TN-1X and TN-1X/S.

Internal traffic interfaces The Nortel Networks TN-1X subrack (shelf) contains slot positions for the following units associated with traffic processing: •

six tributary units — a maximum of four tributary units are used in present applications Note: If the 1:N protection facility is required, an additional 2 Mbit/s Tributary Unit is fitted (not applicable to TN-1X/S subracks).

• •

two Payload Managers two aggregate units

Traffic connections between the traffic units are shown in Figure 5-1. Each Payload Manager has a separate serial interface with each of the tributary units and aggregate units. Each interface consists of three lines in each direction, i.e. 155,520 kbit/s data, 155,520 kHz clock, and a Multiframe Synchronisation (MFS) signal. The interface between the aggregate units consists of three lines for each of the three STM-1s in each direction, i.e. three 155,520 kbit/s data lines, three 155,520 kHz clock signals, and three MFS signals. These lines are only applicable for STM-4 aggregate units, when they allow AU-4 capacities to be transferred between the aggregate units. The Multiframe Synchronisation signal, occurring every 48 frames (i.e. every 6 ms), is produced by the active Payload Manager and is used to ensure that payload connections between the Payload Manager and the interface units are clock and multiframe synchronous. The traffic units take account of any backplane transmission delays and delays caused by the serial/parallel conversions by using co-directional clocks and MFS signals for each data signal.

Nortel TN-1X System Description

5

5-2 Traffic processing Figure 5-1 Inter-unit traffic connections

Payload Manager A (Standby) CLK MFS Tributary Unit 1

CLK

Data

MFS

CLK

Data

MFS

Aggregate Unit (A)

CLK

Data

STM-N Signals

MFS Data

Data

3 3 3 MFS

Data

MFS

CLK

3 3 3

CLK

Payload Manager B (Main)

CLK CLK MFS Data Tributary Unit 6

CLK MFS

MFS Data CLK

Aggregate Unit (B)

STM-N Signals

MFS Data

Data

Notes Payload Manager B has separate but identical links with the Tributary and Aggregate Units as Payload Manager A. Links between the two Aggregate Units are for STM-4 working.

CLK: Clock MFS: Multiframe Synchronisation

Data is transferred between the traffic units in variations of the STM-1 frame format as detailed in the following sections. Details of the Synchronous Digital Hierarchy (SDH) are given in Appendix A: Synchronous digital hierarchy (SDH). Tributary Unit/Payload Manager interfaces The logical interface between the Tributary Units and the Payload Manager is designed to allow the maximum flexibility for the allocation of tributary data into the transmission structure. Between the Tributary Units and the Payload Managers, data is transferred in a partially filled secondary format. In this format, the TU data is packed into the STM-1 frame columns, starting at column one and occupying the normal section and line overhead columns, and containing no gaps. When the data from all the Tributary Units is combined on the Payload Manager, it is in a packed TU format and occupies the first 252 columns of the STM-1 frame (see Figure 5-2, which shows the payload made up of 63 TU-12s, each

323-1061-100 Release 9 Standard

Traffic processing 5-3

occupying four columns). The last 18 columns of the STM-1 are unused and contain fixed bits. Figure 5-2 Tributary Unit/Payload Manager packed TU (secondary) format 1

64 TU1 COL 2

127

TU63 TU1 COL 2 COL3

TU63 COL3

TU1 COL4

190 TU63 COL4

TU1 COL1

253

270

TU63 COL1

Fixed Stuff

TU-12 Pointers

Payload Manager/Aggregate Unit interfaces Between the Payload Managers and the Aggregate Units, data is transferred in a floating AU (primary) format (see Figure 5-3). In this format, the data is in the form of an Administrative Unit Group (AUG), that is, STM-1 frames with the section overhead bytes containing null bytes. Figure 5-3 Payload Manager/Aggregate Unit floating AU (primary) format 9

3

1

261

Null

AU4 PTR

V C 4 Fixed P Stuff O H

5

Payload

Null

Overhead buses The TN-1X has a number of overhead buses, designated Overhead Bus (OHB) and Overhead Z Bus (OHZB). Access to these bytes is not available in present releases.

Nortel TN-1X System Description

5

5-4 Traffic processing

The buses are separated on unit type as follows: • •

Aggregate positions have two buses Payload Manager positions have two buses

•

Tributary positions have three buses

Each overhead bus operates at 4860 kbit/s and provides up to 75 timeslots, this gives a total bandwidth of 34,020 kbit/s of overhead or 75 x 7 timeslots. Note: The bus actually provides 75 8-bit timeslots and a 7.5 bit timeslot and is reset every frame.

Traffic processing Figure 5-4 details the traffic processing for the TN-1X with 2 Mbit/s tributaries. Figure 5-5 details the traffic processing for the TN-1X with 34 Mbit/s tributaries. Figure 5-6 details the traffic processing for the TN-1X/4 with STM-1 tributaries. Figure 5-7 details the traffic processing for the TN-1X with mixed payloads (TU-12s and TU-3s). Traffic processing for the TN-1X is performed by the following units: • •

• • • •

up to four 2 Mbit/s Tributary Units (TN-1X) or one 2 Mbit/s Tributary Unit (TN-1X/S). Each unit provides interfaces for sixteen 2048 kbit/s ports. up to four 34 Mbit/s Tributary Units (16x2) (TN-1X). Each unit provides interfaces for a 34368 kbit/s port, providing access to sixteen 2048 kbit/s channels. up to four 34/45 Mbit/s Tributary Units (VC-3) (TN-1X). Each unit provides interfaces for a 34368 kbit/s or 44736 kbit/s port. up to four STM-1 Optical and Electrical Tributary Units (TN-1X) or up to four STM-1 Optical Tributary Units (TN-1X/S). one/two Payload Managers one/two STM-1 Optical or Electrical Aggregate Units (TN-1X) or one/two STM-1 Optical Aggregate Units (TN-1X/S) or one/two STM-4 Optical Aggregate Units or one STM-1 Aggregate Unit and one STM-4 Aggregate Unit

323-1061-100 Release 9 Standard

STM-1 Opt I/F

Inputs

HDB3

2048 kbit/s

Sixteen

Elec

Opt

Elec

Opt

P

S

P

S

4

4

4

4

Sync

Term

P S

S

TU TU

TU TU

POH Term PO

POH

2 Mbit/s Tributary Unit

Quad 2 Mbit/s ASIC

Map Insert

PO

Interface

Receive

TU TU

TU TU

C-12

4 x 2 Mbit/s

PO

Term PO

POH

TU TU

POH

TU TU

P

Term PO

PO

Insert

POH

POH

Insert

Map

C-12

Map

Interface

Receive

4 x 2 Mbit/s

Interface

Receive

4 x 2 Mbit/s C-12

S

PO

P

TSI

PO

S

TSI

TSI

POH

P

Mux

TSI

TU TU

S

VC POH Insert

TU Sync

POH

P

TSI ASIC

Insert

PTR

AU

TSI ASIC

Term

VC POH Term

TU TU

S

AU PTR

Insert

P

P

S

P

S

Term

Map

C-12

S

P

S

P

Payload Manager (one of two, only one shown)

Interface

Receive

4 x 2 Mbit/s

STM-1 Processor ASIC

Insert

SOH

AU

SOH

STM-1 Aggregate Unit A

C-12

P S

VC POH Term

VC POH Insert

Demap

C-12

Demap

C-12

Demap

C-12

Demap

TU Sync

Mux

AU

S

Interface

Transmit

4 x 2 Mbit/s

Interface

Transmit

4 x 2 Mbit/s

Interface

Transmit

4 x 2 Mbit/s

Interface

Transmit

4 x 2 Mbit/s

P

Term

PTR

AU

PTR

S

P

4

4

4

4

S

P

P

S

P

S

AU Term

SOH

Sixteen

Opt

Elec

Opt

Elec

Note: Traffic processing is shown for Optical Aggregate Units. For Electrical Aggregate Units, the electro/optical conversions are replaced by CMI coding/decoding.

Outputs

HDB3

2048 kbit/s

S

P

S

P

Key: AU = Administrative Unit Elec = Electrical Mux = Multiplex Opt = Optical P = Parallel POH = Path Overhead PTR = Pointer S = Serial SOH = Section Overhead Term = Termination TSI = Timeslot Interchanger TU = Tributary Unit VC = Virtual Container

STM-1 Processor ASIC

Sync

Insert

SOH

STM-1 Aggregate Unit B

STM-1 Opt I/F

Traffic processing 5-5

Figure 5-4 TN-1X traffic processing (2 Mbit/s tributaries)

5

Nortel TN-1X System Description

STM-1 Opt I/F

323-1061-100 Release 9 Standard

Demux

4

4

4

P

TSI ASIC

Insert

PTR

AU

TSI ASIC

Term

P

Mux

TU Sync

S

TSI

TSI

S

P

TSI

TSI

S

POH Term PO

TU TU POH Term PO

POH

TU TU POH Insert

PO

PO

Insert

TU TU

TU TU

POH

POH

PO P

TU TU Term PO

TU TU Insert S

POH Term PO

Insert

PO

POH

P

S

VC POH Insert

VC POH Term

TU TU

S

AU PTR

TU TU

P

P

S

P

S

Quad 2 Mbit/s ASIC

Map

C-12

Map

C-12

Map

C-12

Map

C-12

S

P

S

P

Payload Manager (one of two, only one shown)

34 Mbit/s Tributary Unit

34 Mbit/s

to 2 Mbit/s

Input

STM-1 Processor ASIC

Insert

4

Sync

Term

SOH

AU

SOH

HDB3

P

S

P

S

34368 kbit/s

Elec

Opt

Elec

Opt

STM-1 Aggregate Unit A

C-12

P S

VC POH Term

C-12

Demap

C-12

Demap

C-12

Demap

4

4

4

4

VC POH Insert

Demap

TU Sync

Mux

AU

2 Mbit/s

S

S

P

Mux

S

P

to 34 Mbit/s

P

Term

PTR

AU

Insert

PTR

Term

SOH

Insert

SOH

HDB3

Opt

Elec

Opt

Elec

Note: Traffic processing is shown for Optical Aggregate Units. For Electrical Aggregate Units, the electro/optical conversions are replaced by CMI coding/decoding.

Output

S

P

S

P

Key: AU = Administrative Unit Demux = Demultiplexer Elec = Electrical Mux = Multiplex Opt = Optical P = Parallel POH = Path Overhead PTR = Pointer S = Serial SOH = Section Overhead Term = Termination TSI = Timeslot Interchanger TU = Tributary Unit VC = Virtual Container

STM-1 Processor ASIC

Sync

AU

34368 kbit/s

P

S

P

S

STM-1 Aggregate Unit B

STM-1 Opt I/F

5-6 Traffic processing

Figure 5-5 TN-1X traffic processing (34 Mbit/s tributaries, 16x2)

STM-4 Optical I/F

P

S

P

S

STM-1 Optical I/F

Elec

Opt

Elec

Opt

STM-4 Aggregate Unit A

Byte

P

S

P

S

Sync

Term

Insert

SOH

STM-1 Processor ASIC (x4)

AU

SOH

Sync

Term

Insert

AU

SOH

SOH

STM-1 Processor ASIC

STM-1 Tributary Unit

Elec

Opt

Elec

Opt

STM-4 Processor ASIC

Int

Byte

Disint

TSI

TX

TSI

RX

S

P

S

P

S

P

S

P

S

P

S

P

S

P

S

P

S

P

S

P

See Figure 5-4 for details of traffic processing

Payload Manager (one of two, only one shown) Insert

SOH

SOH Term

AU Sync

STM-1 Processor ASIC (x4)

Note: Traffic processing is shown for STM-1 Optical Tributary Unit. For STM-1 Electrical Tributary Unit, the electro/ optical conversions are replaced by CMI coding/decoding.

P

S

P

S

P

S

P

S

P

S

P

S

P

S

P

S

P

S

P

S

Opt

Elec

Opt

Elec

Key: AU = Administrative Unit Dis = Disinterleaver Elec = Electrical Int = Interleaver Opt = Optical P = Parallel POH = Path Overhead S = Serial SOH = Section Overhead Term = Termination TSI = Timeslot Interchanger

STM-4 Processor ASIC

Disint

Byte

Int

Byte

STM-4 Aggregate Unit B

STM-4 Optical I/F

Traffic processing 5-7

Figure 5-6 TN-1X/4 traffic processing (STM-1 tributaries)

5

Nortel TN-1X System Description

323-1061-100 Release 9 Standard

for details of traffic processing

See Figure 5-4

STM-1 Optical I/F

P

S

P

S

RX

P

ADD Mux

TUG-3

TU-12 TU-3

TSI

SOH

Mux

ADD

TUG-3

P

S

Insert

AU Sync

SOH

Term

STM-1 Tributary Unit*

Elec

Opt

Elec

Opt

P

S

STM-1 Processor ASIC

Note: Traffic processing is shown for STM-1 Optical Tributary Unit. For STM-1 Electrical Tributary Unit, the electro/ optical conversions are replaced by CMI coding/decoding.

* Processing for TU-3 TSI ASIC is the same as for TU-12 TSI ASIC but at the TU-3 level.

STM-1 Opt I/F

STM-1 Aggregate Unit

VC POH Term

TU-12 TU-3

TSI

TX

Mux

P

TU-3 TSI ASIC*

S

VC POH Insert

S

P

S

P

S

TU-12 TSI ASIC

Insert

PTR

AU

TU-3 TSI ASIC*

TU-12 TSI ASIC

Term

PTR

AU

P

Mux

TU Sync

S

P

TSI

TSI

S

Mux

TU Sync

Key: AU = Administrative Unit Elec = Electrical Mux = Multiplex Opt = Optical P = Parallel POH = Path Overhead PTR = Pointer S = Serial SOH = Section Overhead Term = Termination TSI = Timeslot Interchanger TU = Tributary Unit VC = Virtual Container

TSI

TSI

Payload Manager (one of two, only one shown)

P S

VC POH Term

VC POH Insert

AU PTR

S

S

P

Mux

ADD

TUG-3 S

P

S

S

P

P

PO

Insert

POH

TU TU

Term

POH

TU

Map

C-3

C-3De map

34/45 Mbit/s Tributary Unit

P

Term

PTR

AU

Insert

I/F

Line

TAM

for details of traffic processing

See Figure 5-4

STM-1 Aggregate Unit

or 44736 kbit/s Interface

34368 kbit/s

STM-1 Opt I/F

5-8 Traffic processing

Figure 5-7 TN-1X traffic processing (mixed payloads)

Traffic processing 5-9

2 Mbit/s Tributary Unit Each 2 Mbit/s Tributary Unit can process up to sixteen 2048 kbit/s High Density Bipolar 3 (HDB3) tributary signals as follows: Tributary to Payload Manager direction Each HDB3 tributary input is converted to binary format and asynchronously mapped into a VC-12 as defined in ITU-T recommendation G70X. The VC-12 is combined with the parts of the TU-12 having a fixed position in the synchronous frame (bytes V1 to V4 containing the pointer information which is used to locate the start of the VC-12). Each TU-12 is allocated four columns in the STM-1 frame. Data for each of the TU-12s is combined in a partially filled secondary frame format (see “Tributary Unit/Payload Manager interfaces” on page 5-2), containing no section overhead. The partially filled secondary frames are converted to serial form at 155,520 kbit/s and output via separate backplane interfaces to the main and standby Payload Managers (if appropriate). Payload Manager to tributary direction Serial data at 155,520 kbit/s in a partially filled secondary frame format is received from the main and standby Payload Managers (if appropriate). Selection of either the main or standby signal is controlled by the Subrack Controller. The selected signal is converted to parallel form and the data separated into the individual TUs. For each TU, the pointer value is extracted from the V1 and V2 bytes and used to locate the start of the VC-12. The control and overhead bits are removed from the VC-12 and processed. The data is then demapped and converted to HDB3 form for output to the backplane connectors. 34/45 Mbit/s Tributary Unit (VC-3) The 34/45 Mbit/s Tributary Unit can operate at either 34368 kbit/s or 44736 kbit/s. Selection of the line rate is via the Element Controller and CAT. Tributary to Payload Manager direction The 34368 kbit/s HDB3 or 44736 kbit/s B3ZS tributary input is converted to binary format and asynchronously mapped into a VC-3 as defined in ITU-T recommendation G70X. The VC-3 is combined with the parts of the TU-3 having a fixed position in the synchronous frame (bytes H1 to H3 containing the pointer information which is used to locate the start of the VC-3). Each TU-3 is allocated eighty-six columns in the STM-1 frame. Data for the TU-3 is combined in a partially filled secondary frame format (see “Tributary Unit/Payload Manager interfaces” on page 5-2), containing no section overhead. The partially filled secondary frames are converted to serial form at 155,520 kbit/s and output via backplane interfaces to the Payload Manager. Nortel TN-1X System Description

5

5-10 Traffic processing

Payload Manager to tributary direction Serial data at 155,520 kbit/s in a partially filled secondary frame format is received from the Payload Manager. The signal is converted to parallel form and the TU-3 data separated. The pointer value is extracted from the H1 to H3 bytes and used to locate the start of the VC-3. The control and overhead bits are removed from the VC-3 and processed. The data is then demapped and converted to HDB3 or B3ZS form for output to the backplane connectors. 34 Mbit/s Tributary Unit (16x2) Each 34 Mbit/s Tributary Unit can process a single plesiochronous 34368 kbit/s High Density Bipolar 3 (HDB3) tributary signal as follows: Tributary to Payload Manager direction Each HDB3 tributary input is converted to binary format and demultiplexed (according to ITU-T recommendation G.742 and G.751) into its constituent sixteen 2048 kbit/s signals. Each 2048 kbit/s signal is asynchronously mapped into a VC-12 as defined in ITU-T recommendation G70X. The VC-12 is combined with the parts of the TU-12 having a fixed position in the synchronous frame (bytes V1 to V4 containing the pointer information which is used to locate the start of the VC-12). Each TU-12 is allocated four columns in the STM-1 frame. Data for each of the TU-12s is combined in a partially filled secondary frame format (see “Tributary Unit/Payload Manager interfaces” on page 5-2), containing no section overhead. The partially filled secondary frames are converted to serial form at 155,520 kbit/s and output via separate backplane interfaces to the main and standby Payload Managers (if appropriate). Payload Manager to tributary direction Serial data at 155,520 kbit/s in a partially filled secondary frame format is received from the main and standby Payload Managers (if appropriate). Selection of either the main or standby signal is controlled by the Subrack Controller. The selected signal is converted to parallel form and the data separated into the individual TUs. For each TU, the pointer value is extracted from the V1 and V2 bytes and used to locate the start of the VC-12. The control and overhead bits are removed from the VC-12 and processed. The VC-12 signal is then demapped into a 2048 kbit/s signal. The sixteen 2048 kbit/s signals are then multiplexed and converted to HDB3 form for output to the backplane connectors.

323-1061-100 Release 9 Standard

Traffic processing 5-11

STM-1 Tributary Unit Each STM-1 Tributary Unit can process up to sixty-three VC-12 signals or, for mixed payload STM-1 Tributary Units, three VC-3 signals (or a combination of VC-12s and VC-3s) as follows: Note: Although the user interface allows the user to change the path trace settings for STM-1 Tributary Units 25U JU00 750 GVA/GVB and 25U TM00 750 HWE, the path trace is fixed to the default setting on the unit and cannot be changed. Tributary to Payload Manager direction On the STM-1 Optical Tributary Unit, the incoming 155,520 kbit/s optical signal is applied to the optical receiver on the optical transceiver. Opto-electrical conversion is performed by a germanium Avalanche Photodiode (APD). The signal is then amplified and regenerated. The circuit includes a limiting amplifier which ensures that the optimum ‘eye’ waveform is always present irrespective of the amplitude of the optical input signal (allowing for different route lengths). On the STM-1 Electrical Tributary Unit, the incoming 155,520 kbit/s CMI encoded signal is decoded into a binary signal by the electrical transceiver. The data from the optical transceiver (STM-1 Optical Tributary Unit) or the electrical transceiver (STM-1 Electrical Tributary Unit) is converted to parallel form and applied to the STM-1 Processor. The data is frame aligned, descrambled, and the SOH bytes extracted and processed. The AU-4 payload is realigned to the local frame synchronisation signal and new AU pointers generated. The AU-4 payload is applied to the TU-12 RX Timeslot Interchanger (TSI) where: • •

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. The TU-12s are synchronised by realigning the TU-12s to the local multiframe and generating new TU pointers.

•

TU-12 data is written into each TSI in sequential order but can be read in any order, thus providing a re-ordering opportunity.

•

The reordered TU-12s, in a partially filled secondary format (see “Tributary Unit/Payload Manager interfaces” on page 5-2).

For mixed payload STM-1 Tributary Units, the AU-4 payload is also applied to the TU-3 RX TSI (in parallel with the TU-12 RX TSI) where the above processing occurs at the TU-3 level. The outputs of the TU-3 RX TSI and the TU-12 RX TSI are combined to form the VC-4 payload. The output from the RX TSI(s) is converted to serial form at 155,520 kbit/s and output via separate backplane interfaces to the main and standby Payload Managers (if appropriate).

Nortel TN-1X System Description

5

5-12 Traffic processing

Payload Manager to tributary direction Serial data at 155,520 kbit/s in a partially filled secondary frame format is received from the main and standby Payload Managers (if appropriate). Selection of either the main or standby signal is controlled by the Subrack Controller. The selected signal is converted to parallel form and applied to the TU-12 TX TSI and the TU-3 TX TSI (mixed payloads STM-1 Tributary Units only). The selected signal is then processed as follows: • For TU-12 only STM-1 Tributary Units, the TU-12 TX TSI reorders the TU-12s as required, assembles the VC-4, and generates the VC-4 path overhead. The data is then applied to the STM-1 Processor Unit. •

For mixed payload STM-1 Tributary Units, the TU-12 TX TSI reorders the TU-12s as required, assembles the VC-4, and generates the VC-4 path overhead. The TU-3 TX TSI performs the same function at the TU-3 level. The outputs from the TU-12 TX TSI and the TU-3 TX TSI are then multiplexed together to form the VC-4 payload. The VC-4 path overhead and AU-4 pointer is regenerated as required. The data is then applied to the STM-1 Processor Unit.

The SOH bytes are generated and inserted into the appropriate positions within the STM-1 frame and the resulting data scrambled. The scrambled data is converted to serial form and applied to the optical transceiver (STM-1 Optical Tributary Unit) or the electrical transceiver (STM-1 Electrical Tributary Unit). On the STM-1 Optical Tributary Unit, the optical transceiver performs the electro-optic conversion on the scrambled serial data. This is achieved using a modulated semiconductor laser. The mean output of the laser is stabilised at a nominal –2.5 dBm (long haul) or –10 dBm (short haul) by a feedback circuit. The short haul option is only available on the latest units (variants NTKD11AA, 25U TM00 750 HWE/HWG) and is selected via an on-board link. On the STM-1 Electrical Tributary Unit, the electrical transceiver performs the CMI coding on the scrambled serial data. Payload Manager The TN-1X subrack contains slot positions for two Payload Managers. When two units are fitted, the units operate in a main/standby configuration. In normal operation both units are active but the outputs of the standby unit are disabled. Disabling/enabling of the required outputs is controlled by the Subrack Controller. The Payload Manager provides a drop and insert and a re-ordering facility at the TU level between the aggregate and tributary interface units. For mixed payload Payload Managers, this re-ordering is performed at both the TU-12 and TU-3 levels by separate TSI ASICs.

323-1061-100 Release 9 Standard

Traffic processing 5-13

In each direction: •

Data from the aggregate unit in a floating AU primary format (see Payload Manager/Aggregate Unit interfaces on page 5-3) is converted from serial to parallel form. 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.

•

The TUs are synchronised by realigning the TUs to the local multiframe and generating new TU pointers. The TUs are reordered, if required, using TSIs. Two TSIs are used, one provides the insert facility and one provides the drop facility. TU data is written into each TSI in sequential order but can be read in any order, thus providing a re-ordering opportunity.

•

• •

•

•

The order in which the TUs are read from the TSIs is controlled by a store under control of the Subrack Controller. In a drop and insert configuration, the traffic bytes of the required TUs from the insert TSI are combined with the through-path TUs from the TU synchroniser to provide the TU ordering. In a terminal configuration, the insert TSI provides all the TUs. TUs that are to be dropped (all TUs in the case of a terminal configuration) are output onto a common data bus. The TUs are output in serial form to each Tributary Unit, in a partially filled secondary format (see “Tributary Unit/Payload Manager interfaces” on page 5-2), as required. The VC-4 path overhead bytes are generated and combined with the combined data from the TSI and the TU synchroniser. An AU-4 pointer is then added (set to its nominal value of 522).

When using mixed payloads, the above processing is performed at both the TU-12 and TU-3 level. The outputs from the TU-12 TSI ASIC and the TU-3 TSI ASIC are multiplexed together to form the VC-4 payload. The VC-4 path overhead and AU-4 pointer is regenerated as required. The resulting data is converted to serial form for transmission to the aggregate units. STM-1 Aggregate Unit The TN-1X subrack contains slot positions for two aggregate units with optical or electrical STM-1 interfaces. When two units are fitted, the two aggregate ports, A and B, are used in either a main/standby mode for a 1 for 1 protected terminal multiplexer, or as separate east and west ports for a drop and insert multiplexer. A single unit can be used to provide an unprotected terminal multiplexer. The STM-1 Aggregate Unit provides the optical or electrical transmit and receive interfaces and also generates/terminates the Section Overhead (SOH) of the STM-1 frames.

Nortel TN-1X System Description

5

5-14 Traffic processing

Payload Manager to STM-1 direction Serial data at 155,520 kbit/s, in a floating AU primary format (see “Payload Manager/Aggregate Unit interfaces” on page 5-3), is received from the main and standby Payload Managers (if appropriate). Selection of either the main or standby signal is controlled by the Subrack Controller. The selected signal is converted to parallel form. The SOH bytes are generated and inserted into the appropriate positions within the STM-1 frame and the resulting data scrambled. The scrambled data is converted to serial form and applied to the optical transceiver (STM-1 Optical Aggregate Unit) or the electrical transceiver (STM-1 Electrical Aggregate Unit). On the STM-1 Optical Aggregate Unit, the optical transceiver performs the electro-optic conversion on the scrambled serial data. This is achieved using a modulated semiconductor laser. The mean output of the laser is stabilised at a nominal –2.5 dBm (long haul) or -10 dBm (short haul) by a feedback circuit. The short haul option is only available with variant NTKD20AA and is selected via an on-board link. On the STM-1 Electrical Aggregate Unit, the electrical transceiver performs the CMI coding on the scrambled serial data. STM-1 to Payload Manager direction On the STM-1 Optical Aggregate Unit, the incoming 155,520 kbit/s optical signal is applied to the optical receiver on the optical transceiver. Opto-electrical conversion is performed by a photo-detector. The signal is then amplified and regenerated. The circuit includes a limiting amplifier which ensures that the optimum ‘eye’ waveform is always present irrespective of the amplitude of the optical input signal (allowing for different route lengths). On the STM-1 Electrical Aggregate Unit, the incoming 155,520 kbit/s CMI encoded signal is decoded into a binary signal by the electrical transceiver. The data from the optical transceiver (STM-1 Optical Aggregate Unit) or the electrical transceiver (STM-1 Electrical Aggregate Unit) is converted to parallel form and applied to the STM-1 Processor. The data is frame aligned, descrambled, and the SOH bytes extracted and processed. The AU-4 payload is realigned to the local frame synchronisation signal and new AU pointers generated. The AU-4 payload, in a floating AU primary format, is converted to serial form and output to the Payload Managers. STM-4 Optical Aggregate Unit The TN-1X/4 multiplexer subrack contains slot positions for two Aggregate Units which operate as separate A and B ports in a drop and insert mode. Note: It is possible to operate with one STM-4 Aggregate Unit and one STM-1 Aggregate Unit.

323-1061-100 Release 9 Standard

Traffic processing 5-15

The STM-4 Optical Aggregate Unit provides the optical transmit interfaces, generates/terminates the Section Overhead (SOH) and drops/inserts one of the AUGs within the STM-4 signal. Tributary to STM-4 direction The STM-4 signal has the capacity for four AUG (STM-1) payloads. In the transmit direction, one of the AUGs (selectable via the local terminal or the network management system) is supplied from either the main or standby Payload Manager. Selection of either the main or standby signal is controlled by the Subrack Controller. The remaining three AUG payloads are received from the other STM-4 Optical Aggregate Unit in the subrack. Each AUG payload is received as serial data at 155,520 kbit/s in the primary format. The selected four AUG signals are converted to parallel form. The SOH bytes are generated and inserted into STM-1 #1 (the SOH is actually inserted into all four STM-1 signals but some of the SOH bytes in STM-1 #2, #3 and #4 are ignored in the receive direction). The four STM-1 payloads are scrambled and byte interleaved. The framing bytes in the resulting STM-4 signal are overwritten (to maintain alignment if one of the STM-1 processors fails). A BIP-8 calculation is then performed on the entire STM-4 frame, scrambled and placed in the SOH (Byte B1) of STM-1 #1 of the next frame. Note: Although the scrambling is performed at the STM-1 level, the required STM-4 scrambling according to ITU-T recommendations is achieved. The STM-4 data is converted to serial form at 622,080 kbit/s and applied to the optical transmitter module. The electro-optic conversion is performed by a modulated semiconductor laser. The mean output of the laser is stabilised at a nominal –0.5 dBm (long haul) or –11 dBm (intra-office) by a feedback circuit. The transmitter module contains a Peltier heater/cooler which keeps the module at the optimum operating temperature. STM-4 to tributary direction. The incoming 622,080 kbit/s optical signal is applied to the optical receiver module. Opto-electrical conversion is performed by a III-V APD. The receiver module includes the circuitry to provide the necessary amplification, clock extraction and data retiming. The module ensures that the optimum ‘eye’ waveform is always present irrespective of the amplitude of the optical input signal (allowing for different route lengths). The data from the optical receiver is converted to parallel form and applied to the STM-4 Processor. The data is frame aligned and disinterleaved. The resulting four STM-1 signals are applied to the STM-1 Processors where the data is descrambled and the SOH is extracted from the STM-1 payloads. Note: Some of the SOH bytes of STM-1 #2, #3 and #4 are ignored in the receive direction.

Nortel TN-1X System Description

5

5-16 Traffic processing

In each STM-1 Processor, the AU payload is realigned to the local frame synchronisation signal and new AU pointers generated. The four AU payloads from the STM-1 Processors are converted to serial form. The selected AUG to be dropped is output to the main and standby Payload Managers in a floating AU primary format. The remaining AUGs, in a floating AU primary format, are applied to the other STM-4 Optical Aggregate Unit. end of chapter

323-1061-100 Release 9 Standard

6-1

Equipment management

6-

The equipment management functions of the Nortel Networks TN-1X are performed by the Subrack Controller.

Backplane interfaces The TN-1X subrack contains two backplane buses used for equipment management purposes (see Figure 6-1). The control bus is used for transferring control and monitoring information between the Subrack Controller and the other plug-in units. The data communication bus is used for transferring the Embedded Control Channel (ECC) data between the aggregate units/STM-1 tributary units and the Subrack Controller. The ECC is provided by the Regenerator Data Communications Channel (DCCR), D1 to D3 bytes, or the Multiplexer Section Overhead (DCCM), D4 to D12 bytes, in the section overhead of the STM-1 frame. Both the control and data communication buses are High-level Data Link Control (HDLC) based and conform to the proprietary Multi-Master Serial Bus (MMSB) standard. Backplane interfaces are at ‘Futurebus’ levels. The control bus (MMSB1) operates at a nominal 2048 kbit/s, the clock being provided by the Subrack Controller which also derives the +2 V supply used for backplane termination of the data and clock buses. The data and clock buses of the control bus are terminated via resistors to the +2 V supply on the subrack backplane. The data communication bus (MMSB2) operates at a nominal 1944 kbit/s, the clock being provided by one of the aggregate units. The aggregate units also derive a +2 V supply used for terminating the data and clock buses. The Subrack Controller produces an update signal, synchronised to the Multiframe Synchronisation (MFS) signal from the Payload Managers, which is used for synchronising changes in configuration on the aggregate units. The update signal, which occurs 24.5 ± 0.25 frames after a MFS pulse, is activated once the new configuration data has been loaded onto the required aggregate units.

Nortel TN-1X System Description

6

323-1061-100 Release 9 Standard

Control/ Monitoring

Tributary Unit 4

Tributary Unit 3

Tributary Unit 2

Tributary Unit 1

Memory

Control/ Payload Manager A Monitoring Payload Manager B

Card Controller

Card Controller

HDLC Interfaces

Microcont

Memory

Control Bus 2 V

Control Bus Clock

Control Bus (MMSB1)

Data Comms Bus (MMSB2)

Data Comms Clock

Common 2 V

Update

Microcont

HDLC Interfaces

Line Terminations

Aggregate Unit B

Memory

+2 V

Timer

HDLC I/Fs

Subrack I/Fs

Control/ Monitoring/ECC

HDLC Interfaces

Card Controller

Microcont

Aggregate Unit A

+2 V

Line Terminations

Rack Alarm I/F

RS232C I/F

Ethernet I/F

Memory

Subrack Controller

Flexible Access Module (External Alarms) or External Alarm Module

Alarm Detection & Protection

µP

External Alarms

Rack Alarm Bus

Local Terminal

Network Management System

6-2 Equipment management

Figure 6-1 Equipment management bus architecture

Equipment management 6-3

Subrack Controller The Subrack Controller performs the general control and monitoring function for the TN-1X. The unit provides the following interfaces: • two MMSB channels used for inter-unit communication (i.e. the control and data communication buses). • • • •

Ethernet Attachment Unit Interface (AUI) for communication with the Element Controller via the Local Area Network (LAN). RS232C port for communication with a local terminal. standard alarm interface to a rack alarm bus (not supported on the TN-1X/ S subrack). general purpose subrack interface (e.g. unit removal alarms, power fail signals, external alarm inputs (see “External alarms” on page 6-6).

The Subrack Controller is based on a 32-bit 68020 microprocessor operating at 12.5 MHz and uses the pSOS+ operating system. The Subrack Controller is provided with the following memory: •

•

• • •

128 Kbytes of Flash EEPROM (Bank 0) which provides non-volatile non-erasable memory for the operating system and hardware/software initialisation code (i.e. the ‘foundation’ software). 4096 Kbytes of Flash EEPROM, arranged in two banks (Banks 1 and 2), for storing two versions of applications software, the default configuration data, and the download traffic unit software. Banks 1 and 2 can be downloaded via the user interface. The download traffic unit software is downloaded to the traffic units via the control bus (MMSB1). 2048 Kbytes of RAM used for basic microprocessor data and stack functions. 128 Kbytes of battery backed RAM used for storing the configuration data. Dual port RAM used for communication between the Ethernet interface and the microprocessor.

When the microprocessor ‘boots’ up, the microprocessor vectors to the foundation software, but performs a check to see if other downloaded modules exist in Banks 1 and 2 (see “Software” on page 6-8). The unit incorporates a function self-check facility to check for hardware and software failures and also includes a real time clock function.

Card controllers Each traffic unit contains a microprocessor based ‘card controller’ circuit based on a 80C188 microcontroller operating at 10 MHz. The circuit monitors and controls other circuits on the unit under general direction of the Subrack Controller.

Nortel TN-1X System Description

6

6-4 Equipment management

The circuit comprises the following basic components: • •

•

•

•

An 80C188 microcontroller, which provides the required memory and peripheral select lines. A self test circuit which provides a non-maskable interrupt to the microcontroller if a failure occurs (watchdog timer time out or attempted writes to protected memory locations). If this interrupt is not successfully actioned, a reset is applied to the microcontroller. 128 Kbytes of EEPROM used for storing embedded software (foundation software). This memory contains the pSOS operating system, the hardware/software initialisation code and the MMSB communication code. 256 Kbytes of Random Access Memory (RAM) used for storing various data items and as a store for applications software downloaded from the Subrack Controller. An 82525 High Level Serial Communications Controller (HSCC) which provides the two MMSB channels.

Real time clock The Subrack Controller contains a non-volatile real time clock with an accuracy of 1.25 seconds per day. The clock is used for time stamping alarm and performance messages. The clock is factory set but can be adjusted from the CAT or the Element Controller. When connected to a Element Controller, the clock is periodically adjusted to keep the local clock aligned with the Element Controller clock. The real time clock function has a battery back-up which maintains time and calendar functions for up to approximately six weeks in the absence of power to the Subrack Controller.

323-1061-100 Release 9 Standard

Equipment management 6-5

Alarm monitoring The Subrack Controller receives alarm information from the traffic units via the control bus. The received information is time-stamped, logged and processed as described in the following sections. Details of the alarm indications, alarm sequences and individual alarms are given in the Alarm Clearing Procedures, NTP 323-1061-543. Alarm handling Alarm monitoring Each alarm is processed to convert the raw state of the alarm into a monitored alarm state (active or clear). For some alarms (where specific equipment/ network applications need to be considered), the user can enable or disable the monitored alarm state. If alarm monitoring is disabled, the alarm will never be reported. All reported alarms are time stamped and logged. Alarms are logged when the alarm state changes. Alarm filtering Each alarm raised is subject to filtering which determines the alarm state. The alarm ‘present’ and alarm ‘not-present’ filtering periods are assigned pre-set values which cannot be changed. An alarm may therefore exist in one of three states: • Present - an alarm that is present for longer than the ‘present’ filtering period (i.e. alarm is constant). • •

Clear - an alarm that has cleared for longer than the ‘not-present’ filtering period. Masked - as the ‘Present’ state but is not reported due to the presence of a higher priority alarm.

Alarm masking This is performed by the Subrack Controller, so that all consequential alarms are suppressed and only the highest level alarm is included in the reporting schemes. Masking is subject to masking check and masking extension periods. The masking check period is the length of time during which the Subrack Controller checks to see if a higher level alarm is present before reporting an alarm. The masking extension period is the length of time during which the Subrack Controller waits to see if the clearing of a higher level alarm results in the clearance of a previously masked alarm. Any alarm that becomes masked is reported to the user interface as clear. Details of the masking hierarchy are given in the Alarm Clearing Procedures, NTP 323-1061-543. Rack alarm categories/alarm severities Each of the generic alarms is allocated one of four rack alarm categories: •

Prompt - an alarm that requires immediate attention at all times. It is normally extended to a maintenance/control point when the station is unattended. Nortel TN-1X System Description

6

6-6 Equipment management

•

Deferred - an alarm that does not require immediate attention outside normal hours. It is normally extended to a maintenance/control point when the station is unattended.

•

In Station - an alarm that does not require attention outside normal hours. It is not normally extended. Disconnected - an alarm that is indicated by the user interface but no unit, subrack, or rack alarm indications or extensions are provided.

•

The rack alarm categories are linked to the alarm severities used by the Element Controller which displays alarm counts according to their severity. The alarm severities are Critical, Major, Minor or Warning and are linked to the rack alarm categories as follows: Critical Major Minor Warning

Prompt Deferred In-station Disconnect

It is possible to change the rack alarm categories/severities of the alarms using the user interface. Note: Certain alarms (PS-Power_Fail and OS-Optical_Power_High) have fixed rack alarm categories. All reported alarms are time stamped and logged. Alarms are logged when the alarm state changes. External alarms The Flexible Access Module (variant 25U JJ00 750 HPD) and External Alarm Module support 5 external alarm input signals, provided as earth free relay contacts, which can be used for external alarm applications (e.g. door open, intruder alert, fire alert). Each alarm can be assigned a 15 character name via the UI to simplify identification. Each alarm input is a closed contact input, i.e. floating inputs with no earth provided. Each alarm input is protected against accidental connection to a steady state voltage up to 72 V. Sensing circuits for each alarm detect open circuit (>1 MΩ) and short circuit (<200 Ω) conditions. Provision is made via the user interface to set the operating mode of each alarm as follows: • •

Off - disables monitoring of the alarm Closed - enables the monitoring of the alarm with the short circuit (<200 Ω) state being the active alarm condition. This is the default mode.

•

Open - enables the monitoring of the alarm with the open circuit (>1 MΩ) state being the active alarm condition.

323-1061-100 Release 9 Standard

Equipment management 6-7

Filtering for the each alarm can be turned on and off (default) via the user interface. With filtering off, the alarm is raised immediately the active alarm condition is met. With filtering on, the alarm is not raised unless it is present for greater than a set filter period (that is, transient alarms are ignored). Note: Changes to external alarm names are not reflected in alarms that have already been raised. Subsequent instances of the affected alarm will use the new alarm name. CAUTION Removal/insertion of external alarms SIM

Spurious alarms may result if the Flexible Access Module (variant 25U JJ00 750 HPD) or the External Alarm Module is removed or inserted whilst monitoring of external alarms is enabled, but this action shall not cause loss of service or damage to equipment. The Flexible Access Module (variant 25U JJ00 750 HPD) or the External Alarm Module must not be inserted into an operating multiplexer with the external alarm connector already fitted. Electrical protection

The Flexible Access Module (variant 25U JJ00 750 HPD) and External Alarm Module inputs provide connection against connection to a battery supply in the range of 40 V to 72 V, no protection is provided for battery surge, lightening pulse or mains voltages. All external equipment connected to the alarm inputs should provide protection from mains voltages in accordance with the requirements of EN 41003 for connection to Telecommunication Network Voltage (TNV) circuits. In the event of high voltages (>TNV) appearing at the external alarm inputs, the Flexible Access Module (variant 25U JJ00 750 HPD) or the External Alarm Module may need to be replaced. External alarm integrity

It is not possible to guarantee the integrity of the end-to-end transmission link, therefore external alarms are only reported remotely if the transmission link is maintained. The external alarms should not be used for life dependent or hazardous activities.

Nortel TN-1X System Description

6

6-8 Equipment management

Software The TN-1X contains two types of software: • Foundation software which includes the operating system and the hardware/software initialisation code. The foundation software is installed on the Subrack Controller as firmware and cannot be updated. The foundation software is run automatically when the TN-1X is powered up. •

Application software which controls the operation of the TN-1X. The Subrack Controller contains non-volatile Flash memory for two versions (banks) of application software.The application software is started by the foundation software when the TN-1X is powered up. It is possible to download new applications software (for the entire equipment) via the user interface. Note: Current application software is supplied in compressed format for loading via the CAT and must be decompressed prior to loading.

The software bank containing the application software currently in use is referred to as the ‘active’ bank. The other software bank is referred to the ‘inactive bank’. The versions held in each bank should be the same at all times except during software upgrades. As only one bank is selected by the TN-1X foundation software, the software in the inactive bank can be upgraded while the active bank is running. The foundation software selects the bank as follows: • If a cold (traffic affecting) restart occurs, either at power-up or when the user requests a cold restart, the current bank is used (i.e. the bank in use prior to the restart). • If a warm (non-traffic) restart occurs, the bank is selected by the user (default is the current bank in use prior to the restart). A checksum is performed on the selected software, if the test is successful, that software is run. The Subrack Controller contains an automatic reversion facility. If the selected version of the application software fails to start-up successfully, an automatic reversion to the other software bank is carried out. In the unlikely event that both banks fail, the Subrack Controller should be replaced. The ‘card controller’ on each traffic unit contains non-volatile memory which contains the resident software (i.e. operating system, hardware/software initialisation code and the MMSB communications code) which allows the operating software to be downloaded from the Subrack Controller. Once the traffic unit has performed its power-up sequence, a ‘hard reset’ message is sent to the Subrack Controller (via the control bus), the Subrack Controller then downloads the operating software to the traffic unit. Once the download is complete, a ‘soft reset’ message is sent to the Subrack Controller, which then downloads the configuration data. The operating and configuration data on the traffic units is held in RAM which is checked during the power up sequence (failure of the RAM test results in a NE-Card_Fault alarm).

323-1061-100 Release 9 Standard

Equipment management 6-9

Validation of the operating software on the Subrack Controller and the ‘card controllers’ on the traffic units is periodically performed using checksums. A checksum failure on the Subrack Controller results in an INT-SW_Corrupt alarm. A checksum failure on a traffic unit results in a NE-Card_Fault alarm. Software upgrade overview The software upgrade procedure must start with both software banks containing the same functioning version of the application software. New application software is downloaded into the inactive bank from either the CAT or the Preside EC-1. The user is then able to switch to the loaded (new) software in order to test it while retaining the previous software version in the other bank; this permits the user to ‘back out’ to the previous version should the new version prove unsatisfactory. The TN-1X has two configuration tables, one an active table and the other an inactive table (see “Configuration data” on page 6-12). At the time of a software upgrade, each configuration table becomes associated with a software bank. In this situation, configuration changes made using the new software are not reflected in the configuration table associated with the original software. If the user then reverts to the original software, the changes are lost. To avoid losing configuration data, the software versions in each software bank should be the same whenever possible. After a short period of testing, if the new software proves satisfactory, the user should commit to the new software (this replaces the old software in the inactive bank with a copy of the new software). The TN-1X is then once more in a stable configuration. If the new software is unsatisfactory, the user should switch to the original old software and backout (this replaces the new software in the inactive bank with a copy of the old software). The upgrade process is shown in Figure 6-2. ATTENTION The internal bus of the TN-1X is mapped differently at R9 than at earlier releases. While this does not affect the operation of current connections, future connections are more likely to generate traffic hits. To minimize future traffic hits, it is imperative that a VC-12 defragmentation is performed on each TN-1X NE that is upgraded to R9. This should be performed at a time of low network activity. Software status The software status can be checked at all times via the user interface. The software status should be checked during the software upgrade process. If the status is not correct for the operation being attempted, the operation will fail. The software upgrade status can be one of the following: •

Stable Both software banks contain the same software version.

•

Ready_to_activate The user has downloaded new software. The latest loaded software version is in the inactive bank. Nortel TN-1X System Description

6

6-10 Equipment management

•

Ready_to_commit The user has downloaded new software. The latest loaded software version is in the active bank.

•

Download_in_progress Software is being downloaded to the inactive bank. Checksum_bank The download process was aborted, or a software bank has been corrupted. New software must be downloaded, or the active software must be copied to the inactive bank.

•

323-1061-100 Release 9 Standard

Equipment management 6-11 Figure 6-2 Software upgrade overview

Both software banks contain the original software.

Start New software available Download software to TN-1X Inactive Bank

Active Bank contains the original software and Inactive Bank now contains the new software.

Switch to loaded software While the new software is being tested, the original software can remain in Inactive Bank. The user may switch between the different software in each bank.

Test new software

Software OK

During normal operation, it is important that both banks contain the same software version. If the software in each bank is different, this can interfere with the operation of configuration functions.

Yes

No If the new software is satisfactory, the user may decide to commit to it. If the new software proves unsatisfactory, then the user must back out, reverting to the original software. In either case, after the software has been tested, the version in each bank should be the same.

Switch to original software

Backout

Commit to new software

Old software in both banks

New software in both banks

Finish

Nortel TN-1X System Description

6

6-12 Equipment management

Configuration data The TN-1X has a set of configurable parameters that are required to accommodate various user preferences. The Subrack Controller incorporates two configuration data tables (one active and one inactive), each associated with one software flash bank, and stored in non-volatile memory (battery-backed RAM). In normal operation, the two configuration tables should contain identical information, one is the operational bank and the other is the backup bank. However, when the application software is being upgraded, each configuration table becomes associated with an application software bank. If the user changes the configuration using the new software, and performs a backout, or commits to new software after changing the configuration using the old software, the recent configuration changes are lost. The user may backup the current configuration table settings into a file or disk on the CAT or Preside EC-1. The configuration data stored in the file may then be restored, which overwrites the data to the inactive table. The user can then make the new configuration data active by switching to the new loaded configuration data. The user is then able to either: • backout to the old configuration data if necessary (e.g. the new configuration data in incorrect). The old configuration data is then in both tables. • commit to the new configuration data if the restored data is satisfactory. The restored configuration data is then written to both tables. The checksum of the non-volatile RAM containing the configuration data is periodically checked, failure results in an Internal Configuration Corrupt (INT-NE-Config_Corrupt) alarm. Changes to the configuration data can be made via either the Element Controller or the CAT. Requests to change configuration data are validated by the Subrack Controller before the configuration data is changed, invalid requests are rejected (for example, connecting two tributary ports to the same logical channel). Configuration table status The configuration table status can be one of the following: •

•

•

Stable Both tables are identical, one table is currently active. The status must be stable in normal operating conditions. Other conditions should only be seen when the configuration is being upgraded or restored. Ready-to-activate A table has been restored to the inactive bank and has not been activated. The active table holds the current configuration. Ready-to-commit A table has been restored and a ‘Switch-to-Restored’ command has been issued, this makes the restored table active.

323-1061-100 Release 9 Standard

Equipment management 6-13

Detached mode If the Subrack Controller detects that there is a mismatch between the configuration table and the current traffic configuration, the Subrack Controller enters the Detached mode. In the Detached mode: • the Subrack Controller does not control the traffic and the traffic is left running.

•

Note 1: Manual Payload Manager, 1:N protection, 1:1 manual tributary protection, and VC12/VC3 path protection switches are inhibited while the NE is in the Detached mode. Note 2: While in the Detached mode, ‘NE-Unexpected_Card’ and ‘PPI-Unexp_Signal’ alarms may be raised when cards are present. These alarms will clear once the multiplexer is in the normal operating mode. monitoring of the multiplexer is minimal and unreliable.

• •

an INT-NE-Config_Corrupt alarm is raised. the Subrack Controller can still communicate with the Element Controller or CAT.

•

the configuration tables can be updated or restored but the changes are not imposed on the traffic cards (non-traffic affecting). When the configuration tables have been updated or restored and are correct, the Impose_Config command can be issued via the user interface which will impose the information in the active configuration table on the traffic cards (possibly traffic affecting).

The Subrack Controller enters the Detached mode in the following circumstances: • both configuration tables are corrupt or unreadable and there are traffic connections. • •

the multiplexer is cyclically rebooting and there are traffic connections. the Subrack Controller detects a difference between the configuration table and the current traffic configuration.

•

the user issues a ‘Default’ command via the user interface. The current configuration table is overwritten with the default settings. the NE address on the backplane does not match the NE address held in the configuration table on the Subrack Controller (i.e. the Subrack Controller is in the wrong subrack or a new or replacement Subrack Controller has been inserted). In this situation, an INT-NE-Config_Bp_Mismatch alarm is raised. the user issues a ‘Force detached’ command. All current configuration table settings are retained. This command should only be used under exceptional circumstances.

•

•

To exit from the Detached mode, one of the following user actions is required: • If the Subrack Controller has been inserted in the wrong subrack, fit the unit in the correct subrack. Nortel TN-1X System Description

6

6-14 Equipment management

•

if the Subrack Controller is a new or replacement unit, or is cyclically rebooting, then: — issue the Default command via the user interface Note: The user must ensure that the correct Payload Managers and Aggregate Units are configured on the NE before imposing defaults. Failure to do so will result in a loss of communications to the NE once the defaults have been imposed. A site visit will be required to correct this situation. — either Restore a previous configuration table or manually update the current configuration table via the user interface. — issue the ‘impose_config’ command from the user interface.

• •

if the multiplexer is not carrying live traffic, perform a cold restart (issue a cold restart command or power cycle off and on). if the user had issued a a ‘Force detached’ command, issue the ‘impose_config’ command to return to normal operation. Any changes that have been made to the active configuration while the TN-1X was in this mode are applied.

Warm restart If a warm restart is performed, the configuration data in the non-volatile RAM is retained unless a problem occurs. If a problem occurs, the non-volatile RAM configuration data is set to default. On the start-up of each unit, checks are performed on the performance monitoring, connections and synchronisation source data. If a problem occurs, the appropriate data is set to default. Note: When rebooting a TN-1X that is interworking with another multiplexer for MSP purposes, no MSP operations should be attempted until the TN-1X is fully operational. The other multiplexer should not be rebooted during this period. Cold restart A cold restart operates in the same manner as a warm restart except that the hardware is reset and that the Subrack Controller leaves the detached mode (if appropriate). Note 1: Cold restart should not be initiated while 2 Mbit/s 1:N or 34/ 45Mbit/s 1:1 protection is active Note 2: A cold restart of a fully equipped TN-1X takes 12 minutes. No changes should be made to the TN-1X until at least 12 minutes after a cold restart. Note 3: When rebooting a TN-1X that is interworking with another multiplexer for MSP purposes, no MSP operations should be attempted until the TN-1X is fully operational. The other multiplexer should not be rebooted during this period. 323-1061-100 Release 9 Standard

Equipment management 6-15

Local terminal interface The local terminal interface (the ‘F’ interface in the ITU-T SDH recommendations) provides a port capable of supporting a standard intelligent terminal offering full control and monitoring access to the multiplexer or a standard dumb terminal offering read only access to the alarm information (not available on present systems). ATTENTION When the TN-1X is powered up, ensure that the local terminal is not connected to the TN-1X. If the local terminal is connected, the active configuration of the TN-1X will be lost. For the present systems, the interface uses an IBM-PC compatible ‘Laptop’ computer. The computer must be equipped, as a minimum, with the following features: • •

Pentium 100 processor (or higher) Microsoft Windows 95*

• •

16 MByte RAM 0.5 Gbyte Hard Disk Drive

• •

3.5 inch 1.44 MByte floppy disk drive Fully compatible RS-232C serial port

6

— Data rate: 19200 bit/s — Word length: 8 — Stop bits: 1 — Parity checking: Not used — Flow control: none • •

A printer port An externally accessible earth terminal for ESD grounding

Network management The TN-1X is designed to operate in a managed network environment, however, provision is made for the multiplexer to operate in a stand alone mode (using a CAT) where a network management infrastructure does not exist. The Synchronous Digital Hierarchy includes provision within the section overhead structure for a network management channel, implemented using the International Standards Organisation (ISO) 7 layer Open Systems Interconnect (OSI) reference model.

Nortel TN-1X System Description

6-16 Equipment management

When operating within a managed network environment, the TN-1X operates as either: •

A Gateway Network Element (TN-1X only) which communicates with the element controller via a network management interface (Ethernet). The multiplexer also provides network management access to other remote multiplexers via the ‘Embedded Control Channel’ (ECC) within the STM-N frame structure.

•

A Network Element (TN-1X and TN-1X/S) which communicates with the element controller, either via a network management interface, or via the ECC and a Gateway Network Element.

The general network management architecture within which the TN-1X operates is shown in Figure 6-3. Figure 6-3 General network management architecture Potential Standby Gateway Network Element

Element Controller Q3 LAN

Central Node Q3 F

Q3

Gateway Network Element

F

Network Element

F

Network Element

ECC

Q3 F

Gateway Network Element

F

Network Element

ECC

Network Element

Q3 ECC

ECC

LAN Q3

F

Network Element

F

Network management interface via standard LAN (Ethernet)

ECC ‘Embedded Control Channel’ within STM-1 frame structure F

F

ECC

Remote Nodes

Q3

Q3

ECC F

Local terminal port

TN-1X/S multiplexers cannot be used in the positions marked

323-1061-100 Release 9 Standard

Network Element

Network Element

Network Element

Equipment management 6-17

The various interfaces shown in Figure 6-3 are detailed below: •

Q3 interface. This is the network management interface by which individual multiplexers or subsystems of multiplexers communicate with the next layer of the network management hierarchy (Element Controller). The interface supports an ISO 7 layer OSI interface based on ITU-T recommendations Q.811 (CLNSI) and Q.812. In the physical layer, an Attachment Unit Interface (AUI) is provided compliant with ISO 8802-3. Provision is made via the CAT and Element Controller for enabling/ disabling the interface. Note: The TN-1X/S does not support the Q3 interface.

•

ECC interface. This is the ‘Embedded Control Channel’ within the STM-N frame structure which is used for communication between remote multiplexers (i.e. network elements) and the central multiplexers (i.e. gateway network elements). The channel supports an ISO 7 layer OSI protocol based on ITU-T recommendation G.784. In the physical layer, the D1 - D3 Data Communication Channel (DCCR) bytes or the D4 - D12 Data Communication Channel (DCCM) bytes are supported, see “Remote Layer Management” on page 6-17.

•

F interface. This is a RS232C interface for the CAT. The terminal provides operational/maintenance access to the multiplexer.

Communication on the network management interface and ECC are controlled by the Subrack Controller. Messages received on the network management interface with the local network address are processed. Messages to other addresses are sent via the data communications bus to the appropriate aggregate unit for transmission via the ECC. Remote Layer Management The TN-1X provides Remote Layer Management which allows limited management of the data communication resources. The Remote Layer Management allows the TN-1X to interwork with other SDH network elements in emerging SDH networks. In particular, Remote Layer Management provides the following capabilities: • • •

connection of TN-1Xs to STM-1 ports which do not support ECC on higher rate SDH equipment (for example, TN-16X). connection to SDH systems requiring fixed DCC selection. stopping management data communications between different operators SDH networks and between incompatible SDH network elements in a SDH network.

The Remote Layer Management provides the following facilities: •

ECC port management. Control of the ECC port, also known as LAPD link, is made via the user interface. If the link is set to Auto, the TN-1X will attempt to establish a connection on the DCCR channel (RS) and then on the DCCM channel (MS) alternately until the link is established.

Nortel TN-1X System Description

6

6-18 Equipment management

Alternatively, it is possible to force a particular DCC channel to be used via the user interface. Setting RS on, forces the DCCR channel to be used. Setting MS on, forces the DCCM channel to be used. • •

LAN port management. Provision is made for enabling/disabling the interface via the user interface. Network Layer Address Management supporting Standard Network Layer Address Formats. CAUTION Manual Area Addresses

Take care when changing the Manual Area Addresses, ensure that you are aware of the consequences to communication within your network. TN-1X Network Element CAUTION Manual Area Addresses

Take care when changing the Manual Area Addresses, ensure that you are aware of the consequences to communication within your network. The TN-1X supports the configuration/monitoring of the following Network Layer Addresses: •

NE Network Layer Address — read/write access to the three Manual Area Addresses for IS-IS area definition. — read access to the six byte MAC portion (Ethernet). The Ethernet address of the TN-1X is contained in PROM on the subrack backplane. It can only be altered by changing the PROM.

•

Network Manager. The Network Manager address is the address which the TN-1X uses for communication with the Element Controller. — read/write access to the full Network Layer Addresses.

Management System CAUTION Manual Area Addresses

Take care when changing the Manual Area Addresses, ensure that you are aware of the consequences to communication within your network.

323-1061-100 Release 9 Standard

Equipment management 6-19

The Preside EC-1 Element Controller supports the configuration/monitoring of the following Network Layer Addresses: •

Preside EC-1 Element Controller Network Layer Address — read/write access to the three Manual Area Addresses for IS-IS area definition. — read access to the six byte MAC portion (Ethernet) MS Network Layer Address, stored on the MS.

•

NE Network Layer Addresses — read/write access to the full Network Layer Addresses (stored on the MS) of the NE within its span of control.

When the TN-1X is added to the Element Controller, the network address is entered on the management system. When the TN-1X is provisioned to bring it under control of the management system, the address is used to set up a communication path with the TN-1X.

Third-party router interoperability The TN-1X NEs and the Preside EC-1 Element Controller can operate in a network which has multiple routing areas. The Preside EC-1 Element Controller in a network of multiple routing areas can mange all TN-1X NEs in any or all the routing areas. The Nortel Networks TN-1X NEs and the Preside EC-1 Element Controller can reside in several different Level 1 routing areas and communicate via Level 2 routers. • Each routing area can include up to 512 End-Systems (ESs) and 150 Intermediate Systems (ISs). The TN-1X NEs are ISs, the Preside EC-1 Element Controller is an ES. • •

The network can have at most 20 routing areas. The Nortel Networks TN-1X NEs conform to OSI standard ISO 10589 requirements for Level 1 IS-IS routing.

•

All nodes (TN-1X NEs and the Preside EC-1 Element Controller) conform to ISO 9542 requirements for the ES-IS protocol.

Punch-Through feature The Punch-Through feature enables management of a co-located router through the CAT port of the TN-1X. Note: The Punch-Through feature is for future use and is not a supported feature at Release 9. end of chapter

Nortel TN-1X System Description

6

7-1

Synchronisation

7-

The synchronisation source protection functionality of the TN-1X enables the user to control the way in which synchronisation is sourced for the multiplexer. For integration into an SDH network, the TN-1X can synchronise to any external signal traceable to a Primary Reference Clock (PRC).

Synchronisation sources The local clock (155,520 kHz) used for synchronising the TN-1X is provided by the main (active) Payload Manager. For the TN-1X, the synchronising clock can be slaved from any of the following sources: • Tributary Synchronisation (TS) backplane signal. This signal may be derived from: — either of the incoming aggregate STM-1 or STM-4 signals, A or B — any STM-1 tributary signal — any 2048 kbit/s PDH tributary input on a 2M or 34M (16x2) trib unit

7

— any 34368 kbit/s PDH tributary input — any 44736 kbit/s PDH tributary input Note 1: If a STM-4 aggregate signal is selected, the signal is derived from the AUG (STM-1) signal being dropped, which is synchronised to the incoming STM-4 signal. Note 2: Either section of an MSP protection pair can be used for synchronisation purposes. These mechanisms operate independently. Note 3: It is recommended that synchronisation is taken from non-PDH sources in preference to PDH sources. Note 4: It is possible to add an unused or unconfigured tributary/aggregate port to the synchronisation source hierarchy. It is the user’s responsibility to ensure that the synchronisation sources in the hierarchy are configured and valid.

• •

Note 5: PDH ports should not be used as synchronisation sources if PPI-AIS consequent actions or port monitoring is disabled for the port. External 2.048 MHz interface (not available on the TN-1X/S). Connection is via the Star Card module. Internal 16.384 MHz master oscillator (with an accuracy of ±4.6 ppm) on the Payload Manager.

Nortel TN-1X System Description

7-2 Synchronisation

Figure 7-1 shows the functionality of the synchronisation source facility. Figure 7-1 Synchronisation source - block diagram

Payload Manager Internal Oscillator

Activity Detector

External Sync Line

Activity Detector

Trib Sync Line

2M Trib Unit

External Sync Output

Switch

Activity Detector

PLL

Local Timing

Activity Detector

STM-1 Trib Unit

34/45M Trib Unit

Aggr Unit

Note 1: Loss of the active synchronisation source can cause loss of all traffic for approximately 200 ms. Note 2: If a traffic unit provides the current synchronisation source, switch to an alternative synchronisation source before replacing the unit or re-provisioning the multiplexer. Note 3: Systems with subracks using STM-4 aggregates should not be run with the synchronisation independently set to ‘Internal’. They should be synchronised via the line back to a common source (for example, a Head Mux set to ‘External’ or ‘Internal’). Note 4: Do not apply a ‘Local’ loopback for a tributary selected as the active synchronisation source, otherwise the multiplexer will lose synchronisation.

Synchronisation source hierarchy The basis for synchronisation source protection is the synchronisation source hierarchy. This is formed from four sources identified by the user. The first source has the highest priority for the user, with the fourth having the lowest. A standby signal is also available, which is always the internal oscillator on the Payload Manager. 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 (see “Synchronisation switching mechanisms” on page 7-4 for details).

323-1061-100 Release 9 Standard

Synchronisation 7-3

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 (that is, 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 TN-1X 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 TN-1X begins a ‘holdover period’. During this period, the TN-1X 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. — If the holdover period ends (typically after five seconds) without the source becoming available, the standby source (the internal oscillator) is used.

•

Note 1: When a source is in forced use, reversion settings are ignored. Note 2: During holdover, a QL =15 is transmitted for Payload Manager variant 25U PJ00 750 GXF and QL = 11 is transmitted for Payload Manager variants NTKD10AA, NTKD10CA and 25U PJ00 750 HZQ. See “Synchronisation status messaging” on page 7-4 for details. 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.

Nortel TN-1X System Description

7

7-4 Synchronisation

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” on page 7-4. •

A non-SSM system. This is similar to the synchronisation mechanism used by the TN-1X up to (and including) Release 6. See “Non-SSM synchronisation sourcing” on page 7-10. Note: Both of these mechanisms make use of the software settings described in “Synchronisation settings” on page 7-3.

Synchronisation status messaging Synchronisation status messaging (SSM) is based on the transmission of synchronisation quality messages between potential synchronisation sources. Using this system, the TN-1X 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 7-3). 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 7-3). If no source is available, the standby source is selected. Note: The SSM mechanism can only select sources that are listed in the synchronisation source hierarchy.

The Quality Level (QL) of a source is transmitted in the section overhead of all STM-N signals as the S1 byte. QL has a possible range of 1 to 15, with 1 as the highest priority. In practice, a subset of these values is used by the TN-1X. This subset of QL values is defined in Table 7-1. The TN-1X transmits its QL on all STM-N ports, except for the STM-N 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-1X 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.

323-1061-100 Release 9 Standard

Synchronisation 7-5

By default, each TN-1X uses its internal clock, which has a QL of 11. Table 7-1 QL settings for use with SSM QL

Meaning

Description

0

Synchronisation quality unknown

Included for backwards compatibility reasons. Will always be interpreted by multiplexer as QL = 15.

2

Traceable to Primary Reference Clock (PRC)

The external timing source for the network.

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 Equipment Clock (SEC)

The internal oscillator of the multiplexer. Note: This is the default setting.

15

Do not use for synchronisation

This prevents the multiplexer’s synchronisation source from being used by multiplexers that receive this value.

The user can configure the QL settings for both RX and TX purposes. These manual settings override any QL values established by the TN-1X software. Note 1: Early Aggregate Units are unable to receive or transmit QL values. The QL for these aggregates will default to 15 (“do not use for sync”). Note 2: A failure holdoff time of one second must be set if the NTKD10CA or 25U PJ00 750 GXF Payload Manager is used when SSM is enabled.

Nortel TN-1X System Description

7

7-6 Synchronisation

Synchronisation status messaging network examples Simple ring with a single reference source An example simple ring network with a single reference source is shown in Figure 7-2. Figure 7-2 SSM within a simple STM-N ring with a single external source

PRC (An EXTernal source) QL = 2

2 15

TN-1X (A) QL = 2 A Hierarchy=EXT

2 B 2

B

A

TN-1X QL = 2 Hierarchy=B, A A

TN-1X QL = 2 Hierarchy=B, A

STM-N RING

B

2

B

15

TN-1X QL = 2 Hierarchy=B, A

15

A

2

In the example of Figure 7-2, synchronisation is derived from the Primary Reference Clock (PRC). The PRC is the external (EXT) source with a QL=2 at TN-1X(A). The other TN-1Xs in the ring have their hierarchy set to derive synchronisation from the counter-clockwise TN-1X in preference to the clockwise TN-1X (that is, on their B ports in preference to A). The QL = 2 clock is transmitted on all STM-N ports for the TN-1X, 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-1Xs 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-1Xs after the break will send a QL = 11 in the counter-clockwise direction. The last TN-1X in the ring will switch to the higher quality clock (QL = 2) being sent from the TN-1X 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-1X will switch to the PRC QL = 2 clock. The ring will then be synchronised to the highest available quality clock.

323-1061-100 Release 9 Standard

Synchronisation 7-7

Simple ring with two reference sources An example simple ring network with a two reference sources is shown in Figure 7-3. Figure 7-3 SSM within a simple STM-N ring with two external sources

PRC (An EXTernal source) QL = 2 2 15

TN-1X(A) QL = 2 A Hierarchy=EXT, B B

2

2 B

A

TN-1X QL = 2 Hierarchy=B, A A

TN-1X QL = 2 Hierarchy=B, A

STM-N RING

B

2

B 15

15

A TN-1X(B) QL = 2 Hierarchy=EXT, B 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-1X(A). There is also a Secondary Reference Source (SRC) which is also external and has a QL = 3 at TN-1X(B). The other TN-1Xs in the ring have their hierarchy set to derive synchronisation from the counter-clockwise TN-1X in preference to the clockwise TN-1X, that is, on their B ports in preference to A. The QL = 2 clock is transmitted on all STM-N ports for the TN-1X, 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-1X with the primary source switches to an internal clock with a QL = 11. This will propagate around the network until it reaches the TN-1X 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-1Xs synchronising to the secondary reference source. Note: The hierarchy on the TN-1Xs 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. Nortel TN-1X System Description

7

7-8 Synchronisation

Chain network with two reference sources An example simple chain network with a two reference sources is shown in Figure 7-4. Figure 7-4 SSM within a simple STM-N ring with two external sources

PRC QL = 2

SRC QL = 3

15

15 TN-1X QL = 2

TN-1X QL = 2 2

15 TN-1X QL = 2

2

TN-1X QL = 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. Inter-operating with non-SSM networks An example simple ring network inter-operating with a non-SSM network is shown in Figure 7-5. In this example, the TN-1X ring is subtended to a non-SSM TN-16X ring via an STM-1 tributary. In this situation, it is necessary to override the receive and transmit QL settings on the STM-1 tributary at the TN-1X inter-connecting with the TN-16X ring. In the example, the RX override on the STM-1 tributary at TN-1X(A) is set to a value of 4 (the value should correspond to the value of the synchronisation source in the TN-16X ring). This value is transmitted around the TN-1X and is used as the synchronisation source (assuming no higher level source is available). Note: The RX override can be configured to a value between 1 and 15. Setting the RX override to a value between 11 and 15 will cause the TN-1Xs to run from their internal source. It is recommended that the TX override of the STM-1 tributary is set to a value of 15 (do not use). This provides an additional safeguard if the non-SSM equipment becomes SSM compatible. 323-1061-100 Release 9 Standard

Synchronisation 7-9

Note: If the TN-16X ring is not the source of synchronisation for the TN-1X ring, the RX and TX overrides for the TN-1X STM-1 tributary should be set to 15 (do not use) or the STM-1 tributary removed from the synchronisation hierarchy. Figure 7-5 SSM within a simple STM-N ring inter-connecting with non-SSM network

TN-1X Ring (SSM) 4 15

TN-1X QL = 4 A Hierarchy=B, A

15 B 4

B

A

TN-1X QL = 4 Hierarchy=B, A A

TN-1X QL = 4 Hierarchy=B, A

STM-N RING

B

4

B

4

TN-1X(A) QL = 4 Hierarchy=C

4

C Rx override=4

B

15

A

Tx override=15

TN-16X

A

TN-16X Ring (non-SSM)

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-1X 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. Nortel TN-1X System Description

7

7-10 Synchronisation

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, that is, 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, that is, 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, that is, 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, for example, 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 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 7-3). With SSM off, the TN-1X can operate in one of three modes dependent on the reversion and force settings (these modes are similar to the synchronisation schemes used up to and including Release 6). •

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

323-1061-100 Release 9 Standard

Synchronisation 7-11

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). •

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 and STM-4 aggregate ports, STM-1 tributary ports — RS-LOS — RS-LOF — MS-AIS or AU-AIS

7

— 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

• •

Tributary Synchronisation Activity Detector External Sync Source Activity Detector

• •

Internal Oscillator Activity Detector SETG Fail alarm

Failure hold-off time If a synchronisation source fails, a check is performed to check that it has failed continually for a period of time. The period of time, known as the “failure hold-off time”, is configurable via the user interface. 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. Nortel TN-1X System Description

7-12 Synchronisation

External synchronisation output The TN-1X provides an external 2048 kHz synchronisation output signal (via the Star Card module) in accordance with ITU-T recommendation G.703, the output signal is present at all times.

Synchronisation alarms There are five alarms associated with the synchronisation facility, namely: • •

‘SYNC-SETG_Fail’ - indicates failure of the currently selected source. ‘SYNC-Src_Not_Primary’ - indicates that the primary synchronisation source is not currently selected.

•

‘INT-SYNC-Trib_Line_Fail’ - indicates that the status of the Trib Sync line is unreliable (that is, activity is detected when not expected or no activity when expected). The alarm is detected during a synchronisation source switch and indicates that either the unit that was providing the source has not switched it off, or the unit providing the new synchronisation source has not switched it on.

•

‘INT-SYNC-Oscillator_Fail’ - indicates that the internal oscillator has failed. ‘SYNC-Ext_ Sync_LOS’ - indicates that the external synchronisation source has failed.

• end of chapter

323-1061-100 Release 9 Standard

8-1

Power

8The Nortel Networks TN-1X and TN-1X/S subracks contain one or two Power Units which provide the +5 V, –5.2 V, +12 V, and –2 V supplies for the subrack units. The Power Units operate in a load sharing mode, however, each Power Unit is capable of supplying the total power requirement. It is possible when in the load sharing mode, to remove or fit one of the Power Units without affecting the performance of the Nortel Networks TN-1X. The Power Units operate from a battery supply in the range of 40 V to 72 V (nominal 48 V or 60 V). Each subrack requires two separately fused supplies. The supply to each subrack is normally separately fused. For power supplies of 48 V or 60 V, the fuse rating for each subrack is 7 A. One supply is used to provide the ‘power’ input to the first Power Unit and the ‘alarm’ input to the second Power Unit. The other supply is used to provide the ‘power’ input to the second Power Unit and the ‘alarm’ input to the first Power Unit. This ensures that power is still available to the subrack if one of the fused supplies fails. Backplane filtering ensures that plugging any unit into the subrack will not cause a disturbance on the voltage rails sufficient to cause malfunction on any other unit in the subrack. Each of the derived voltages is monitored and a power supply fail alarm raised if any of the voltages exceed their specified tolerance.

Power supply to the TN-1X subracks There are normally two independent d.c. station supplies which are connected to fuse holders at the top of the rack. The remaining information in this sub-section gives a typical power supply arrangement for a ETSI rack fitted with a Rack Alarm Unit. The incoming cables are either 10 mm2 or 16 mm2, terminated in a crimped wire pin and sleeved. They are each fixed to the upper of one of the fuse holders which are Klippon type P.O.136H (25S TP00 001 AAA).

Nortel TN-1X System Description

8

8-2 Power

For station power supplies of 48 V or 60 V, the fuse rating for each subrack is 7 A. The first fuse position (0) is reserved for the Rack Alarm Unit (if fitted). Its rating is 2 A type, coded 25C PR13 001 GBD. Up to 10 fuses can be used for the subrack power cables and these are arranged in two groups, each group being connected to one of the independent supplies using link bars to connect adjacent fuses, see Figure 8-1. The earth cables associated with each subrack supply are connected to the earth tags located at the top of the rack. They then form a twisted pair with the corresponding power cable and pass down the right hand side of the rack. The power cables to the subracks are 1/1.13 mm2 type. The power cable is coloured blue and the earth cable is black. The twisted pairs are distributed down the rack height so that two twisted pairs are available for use at regular intervals. They are arranged so that the two twisted pairs at regular intervals are from a different group. Since each subrack requires two separate power inputs, these supplies are thus independent. This means that the subracks are protected against a power supply failure. The power connector is mounted on the Station Service Module and is chosen to suit customer requirements. The backplane has separate earth layers for the 0 V battery input and the signal earths. If required these can be linked by strapping pins on the Station Service Module. Power supply to the TN-1X/S subracks The power connector is mounted on the Power & LCAP module. The backplane has separate earth layers for the 0 V battery input and the signal earths. If required these can be linked by strapping pins on the Power & LCAP module.

323-1061-100 Release 9 Standard

Power 8-3 Figure 8-1 Typical TN-1X rack power cabling and fusing Independent Power Supply Inputs

Network Management Bus

Rack Alarm Unit

Fuse Positions

0 1

2 3

1 2 3

Rack Alarm Bus Ribbon Cable

Subrack 3

Subrack 2

8 Subrack 1

Notes 1. The rack has 10 subrack power supply cables. For each of the 10 subrack power cables there is an associated earth cable. The earth cables are either connected to earth tags at the top of the rack or to a vertical bar. The live and earth wires form twisted pairs. Groups of 2 twisted pairs are spaced at regular intervals in the rack.

Cables in the right-hand cable space

2. In this application only six twisted pairs are used to power three subracks. 3.

Indicates that a fuse is fitted

Indicates that no fuse is fitted

end of chapter

Nortel TN-1X System Description

9-1

Connectivity

9-

Channel numbering schemes The Nortel Networks TN-1X uses the ITU-T ‘KLM’ channel numbering system which uses a 3-figure vector (K,L,M) representation to identify the TUG-3, TUG-2 and TU-12 within the VC-4 payload. The KLM scheme also 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’ (that is, a 2 Mbit/s VC-12 signal) •

‘2,0,0’ - indicates TUG-3 ‘2’ (that is, a 34/45 Mbit/s VC-3 signal)

Table 9-1 provides cross-references between the K, L, M numbering scheme and the ETSI channel and Nortel Networks numbering schemes used in previous releases. All user interfaces use the KLM numbering scheme when configuring and displaying connection information. In addition, when using the connection management facility on the Element Controller, the screens also indicate the equivalent ETSI channel numbers.

9

Nortel TN-1X System Description

9-2 Connectivity Table 9-1 Channel numbering schemes TUG-3 K

TUG-2 L

TU-12 M

ETSI (ITU-T)

Nortel Networks

TUG-3 K

TUG-2 L

TU-12 M

Nortel Networks

ETSI (ITU-T)

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3

1 1 1 2 2 2 3 3 3 4 4 4 5 5 5 6 6 6 7 7 7 1 1 1 2 2 2 3 3 3 4 4 4 5 5 5 6 6 6 7 7 7 1 1 1 2 2 2 3 3 3 4 4 4 5 5 5 6 6 6 7 7 7

1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63

1 22 43 4 25 46 7 28 49 10 31 52 13 34 55 16 37 58 19 40 61 2 23 44 5 26 47 8 29 50 11 32 53 14 35 56 17 38 59 20 41 62 3 24 45 6 27 48 9 30 51 12 33 54 15 36 57 18 39 60 21 42 63

1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3 1 2 3

1 1 1 2 2 2 3 3 3 4 4 4 5 5 5 6 6 6 7 7 7 1 1 1 2 2 2 3 3 3 4 4 4 5 5 5 6 6 6 7 7 7 1 1 1 2 2 2 3 3 3 4 4 4 5 5 5 6 6 6 7 7 7

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63

1 22 43 4 25 46 7 28 49 10 31 52 13 34 55 16 37 58 19 40 61 2 23 44 5 26 47 8 29 50 11 32 53 14 35 56 17 38 59 20 41 62 3 24 45 6 27 48 9 30 51 12 33 54 15 36 57 18 39 60 21 42 63

323-1061-100 Release 9 Standard

Connectivity 9-3

Port/channel designations Connections can be made to/from the following tributaries and aggregates. The total tributary capacity of the TN-1X is equivalent to one VC-4, irrespective of the number and capacity of the tributary units. Note: VC-3 operation is only possible if mixed payload Payload Managers and STM-1 Tributary Units (if applicable) are used. 2 Mbit/s tributaries 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 (‘2’, ‘4’, ‘9’ or ‘11’, i.e. S2, S4, S9 or S11). ‘n’ is the tributary port on the indicated unit (‘1’ to ‘16’).

For example: • ‘S2-2’ is port 2 on the 2 Mbit/s Tributary Unit in slot 2. •

‘S9-10’ is port 10 on the 2 Mbit/s Tributary Unit in slot 9. Note: For TN-1X/S, only slot S2 is available for 2 Mbit/s tributary ports.

34 Mbit/s tributaries (16x2) The 34 Mbit/s Tributary Unit (16x2) provides access to sixteen constituent 2 Mbit/s signals. For connection purposes, these signals are defined as if they are 2 Mbit/s tributary ports on a 2 Mbit/s Tributary Unit, that is in the form ‘Ss-n’ where: • ‘s’ is the slot number (‘2’, ‘4’, ‘9’ or ‘11’, i.e. S2, S4, S9 or S11). •

‘n’ is the tributary instance on the indicated unit (‘1’ to ‘16’). Note: The 34 Mbit/s Tributary Unit (16x2) is not available on the TN-1X/ S.

34/45 Mbit/s tributaries (VC-3) The 34/45 tributary ports are defined by the unit slot number and tributary instance in the form ‘Ss-n’ where: • •

‘s’ is the slot number (‘2’, ‘4’, ‘9’ or ‘11’, i.e. S2, S4, S9 or S11). ‘n’ is the tributary instance on the indicated unit (‘1’).

For example: • ‘S4-1’ is port 1 on the 34/45 Mbit/s Tributary Unit in slot 4. Note: The 34/45 Mbit/s Tributary Unit is not available on the TN-1X/S. STM-1 tributaries STM-1 tributary channels are defined by the unit slot number and the KLM channel number in the form ‘Ss-n-Jj-Kklm’ where: • •

‘s’ is the slot number (‘2’, ‘4’, ‘9’ or ‘11’, i.e. S2, S4, S9 or S11). ‘n’ is the port number (always ‘1’ for STM-1 tributaries).

•

‘j’ is the AU-4 selection (always ‘1’ for STM-1 tributaries). Nortel TN-1X System Description

9

9-4 Connectivity

•

‘klm’ is the KLM reference — 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: • ‘S4-1-J1-K213’ is TUG-3 ‘2’, TUG-2 ‘1’, TU-1 ‘3’ on STM-1 Tributary Unit in slot 4. • ‘S11-1-J1-K300’ is TUG-3 ‘3’ (i.e. a VC-3 signal) on STM-1 Tributary Unit in slot 11. STM-1 aggregates STM-1 aggregate channels are defined by the unit slot number and the KLM channel number in the form ‘Ss-n-Jj-Kklm’ where: • ‘s’ is the slot number (‘6’ or ‘7’, i.e. S6 (Aggregate A) or S7 (Aggregate B)). • •

‘n’ is the port number (always ‘1’ for STM-1 aggregates). ‘j’ is the AU-4 selection (always ‘1’ for STM-1 aggregates)

•

‘klm’ is the KLM reference — 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: • ‘S6-1-J1-K271’ is TUG-3 ‘2’, TUG-2 ‘7’, TU-1 ‘1’ on STM-1 Aggregate Unit in slot 6 (aggregate A). •

‘S7-1-J1-K100’ is TUG-3 ‘1’ (i.e. a VC-3 signal) on STM-1 Aggregate Unit in slot 7 (aggregate B).

STM-4 aggregates STM-4 aggregate channels are defined by the unit slot number and the KLM channel number of the selected dropped AU-4 in the form ‘Ss-n-Jj-Kklm’ where: • ‘s’ is the slot number (‘6’ or ‘7’, i.e. S6 (Aggregate A) or S7 (Aggregate B)). • •

‘n’ is the port number (always ‘1’ for STM-4 aggregates). ‘j’ is the AU-4 selection (‘1’ to ‘4’)

•

‘klm’ is the KLM reference — 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: •

‘S6-1-J2-K152’ is TUG-3 ‘1’, TUG-2 ‘5’, TU-1 ‘2’ on AU-4 ‘2’ on STM-4 Aggregate Unit in slot 6 (aggregate A).

323-1061-100 Release 9 Standard

Connectivity 9-5

Connection types There are three possible types of connections which are shown in Figure 9-1 and described in subsequent sections. Figure 9-1 TN-1X connection types

TN-1X

STM-1 Trib

...

34/45M Trib

STM-1 Aggr

2M Tribs

STM-1 Aggr

VC-12

VC-3

VC-12 Protect

VC-3 Protect

STM-1

Note: It is not possible to concurrently connect all the connections shown above, as the STM-1 bandwidth would be exceeded. Note: Trib-to-Trib connections are not supported at Release 9. Through connections A through connection connects a payload channel (VC-12 or VC-3) from one aggregate to the same payload channel on the other aggregate. For example, it is possible to make a through connection between the ‘S6-1-J1-K111’ (aggregate A) and ‘S7-1-J1-K111’ (aggregate B).

Nortel TN-1X System Description

9

9-6 Connectivity

Unprotected drop/insert connections An unprotected drop/insert connection connects a VC-12 or VC-3 tributary signal to a payload channel on one of the aggregates. In the event of failure, an alternative routing via the other aggregate is NOT available. For example, it is possible to make an unprotected connection between ‘S2-1’ (tributary 1 on 2 Mbit/s Tributary Unit in slot 2) and ‘S6-1-J1-K333’ (aggregate A). Protected drop/insert connections A protected drop/insert connection connects a VC-12 or VC-3 tributary signal to the same payload channel on both aggregates. In the transmit direction, the tributary signal is transmitted on both aggregates. In the receive direction, the signal is received from both aggregates but only one of the signals is dropped to the tributary. In the event of failure of the signal from the selected aggregate, the signal from the other aggregate is dropped to the tributary. For example, it is possible to make a protected connection between S9-1-J1-K300 (VC-3 signal on STM-1 Tributary Unit in slot 9) and S6-1-J1-K200 (aggregate A) and S7-1-J1-K200 (aggregate B).

Internal traffic connections For internal traffic connections between the traffic cards, the TN-1X uses an internal backplane traffic bus architecture that has a bandwidth of a single STM-1 signal (see Chapter 4, “System parameters” for details). In most circumstances, the TN-1X automatically allocates bandwidth (timeslots) on the internal traffic buses to new connections as required and the internal buses are invisible to the user. Under certain circumstances, however, the internal bus timeslots may have been used in a way that further connections cannot be made without reallocating existing connections on the internal buses (i.e. the internal buses are fragmented). When this occurs, the user can initiate a reallocation of timeslots on the internal buses, this is known as ‘defragmentation’. General rules for adding new connections Because of the way that the TN-1X Release 9 software allocates backplane timeslots, there is a preferred order in which to utilise the 2 Mbit/s tributary ports. The guidelines given below apply all TN-1Xs no matter whether the multiplexer is: a. a current Release 9 multiplexer (that is, it was shipped from the factory with Release 9 software inside) b. an existing multiplexer that has been upgraded from Release 7.n or Release 8.n software to Release 9. VC-12 defrag must have been issued. Adding a VC3 Connection When adding a VC3 connection to a Release 9 NE consider the number of VC12s used on the NE and the number of VC3 connections required: • If there are no VC12 connections on the NE then no action is required and the VC3 can be added normally.

323-1061-100 Release 9 Standard

Connectivity 9-7

•

If adding a single VC3 connection and there are less than 21 VC12 connections present then do a test connect and note the circuits that may be hit, then apply the connection. This will result in a hit risk to some or all VC12's present.

•

If adding a single VC3 and there are more than 21 VC12 connections present then apply a VC3 Test Defrag noting the circuits that will be hit, apply the VC3 Defrag then add the VC3 connection. The VC3 Defrag will result in a hit risk to some or all VC12's present.

•

If adding two VC3 connections to a Mux without VC12 connections present then the VC3 connections can be added without a traffic hit. If Adding Two VC3 connections to a Mux with VC12 connections present then a VC3 Defrag should be applied. The VC3's can now be applied without a further traffic hit.

•

•

If adding a VC3 to a mux with a VC3 and VC12's present, a VC3 Test defrag must be applied and the circuits affected noted. A VC3 defrag can then be applied and the second VC3 then added. The VC3 Defrag will only hit VC12 connections that need to be reallocated to facilitate the addition of the VC3.

Adding a combination of VC12 and VC3 connections If the user requires to add a series of VC12 and VC3 connections to the one Release9 NE, then the VC3 connection should be added (using above procedure) before any VC12 connections. By adding the VC3's first the back-plane will be organized so as minimize potential traffic hits for the new connections. The VC12 connections can then be added (following the methods detailed below). Adding VC12 connections only A test connect should be carried out, if the test connect reports significant traffic hits (greater than four VC12 connections) then consideration should be given to performing a VC12 defrag before making the connection. A VC12 defrag will reduce the potential hits for future VC12 traffic, but a traffic hit may be induced on a number of ports during the defrag operation. • Adding VC12 connections to 2Meg Trib cards after an Upgrade Where possible use a set of 4 ports that has no connections already on it. E.g. if slot 4, ports 5, 6, 7, 8 are all free use these up first. Relevant sets of 4 are: Ports 1, 2, 3, 4 Ports 5, 6, 7, 8 Ports 9, 10, 11, 12 Ports 13, 14, 15, 16 This is for any 2M card (or the 16x2 card) •

Method 1: 60 Connections without Hit Risk 60 VC12 connections can be added in any order, but it is recommended that the VC12 Connections on 2Meg tribs should be added in incrementing order, all the ports on slot 2 from 1 to 16 then all the ports on s4 1 to 16, all Nortel TN-1X System Description

9

9-8 Connectivity

the ports on slot 9 1 to 16 and then slot 11 1 to 12. The last three connections (slot 11 ports 13, 14 and 15) will generate a hit risk with this method. •

•

Method 2: 63 Connections without Hit Risk The second method requires adding the last 3 available ports first, e.g. add slot 11 port 13, 14 and 15, The rest of the connections can be added in any order but it is again recommended that they are added in incrementing order from slot 2 port 1 up to slot 11 port 12 finally. All 63 VC12 connections can be added without a Hit Risk using this method. Churning 2Meg Trib Connections On a VC12 Only Mux

•

When Churning the connections added using the above methods the last three connections e.g. Slot 11 port 13, 14 and 15 should not be deleted if possible, this will prevent significant Hit Risk when adding further connections. Deleting then adding new connections on 2Meg Trib Cards After VC12 connections have been deleted and new connections are to be added, these new connections can be added in any order to the ports that are available.

•

2Meg Trib and STM1 Cards The VC12 Connections on 2Meg tribs should be added first in incrementing order, all the ports on slot 2 from 1 to 16 then all the ports on s4 1 to 16 etc. The connections on the STM1 card can then be added. This method will prevent Hit Risk.

•

•

Deleting then adding connections on 2Meg and STM1 Trib Cards The connections on both cards can be deleted in any order, but the VC12 connections on the 2Meg trib cards should be re-added first using the methods detailed above. The connections on the STM1 card can then be added. This method will reduce a Hit Risk to existing traffic. Adding VC12 connections on STM1 Trib Cards only

•

These connections can be added in any order up to the total number of 63. A VC12 Defrag should never be used on a mux with only STM1 trib cards present. Adding VC12 Connections with a VC3 Present The VC12 connections can be added in incrementing order using the methods detailed above.

However, in making this decision the customer should consider the number of potential hits reported by the test connect, the number of potential hits reported by the test defrag and perform the defrag if deemed necessary. Adding VC12 connections on an STM1 tributary card When adding VC12 connections to an STM1 trib consideration should be given to the mix of cards used in the mux. If other 2m connections are to be made using 2M tributary cards (such as HVT's or GXG's), then these connections should be added first so that they can be placed on their preferred 323-1061-100 Release 9 Standard

Connectivity 9-9

positions on the internal backplane of the MUX. Placing the STM1 VC12 connections first may block preferred positions on the 2M trib, causing backplane fragmentation when adding the effected connections and increasing the risk of 2M traffic hits. Defragmentation If an attempt is made to add a new connection when the internal buses have become fragmented, the internal buses may need to be defragmented before the new connection can be made. The defragmentation action can also be user initiated at any time so as to minimise problems when adding additional connections. Note: During the defragmentation action, PPI-Unexp_Signal and PPI-CV_QOSV_15M alarms may be raised as connections are broken and remade. When the internal buses are defragmented, temporary traffic hits may occur (the user is given a list of possible traffic hits before the defragmentation action is performed). Note: The physical connections for aggregate and tributary payloads are unchanged by defragmentation, only the internal bus allocation is changed. Defragmentation of the internal buses can be performed in one of two ways: •

VC-3. A VC3 Defrag will rearrange the connections on a mux in order to facilitate the addition of one or more VC3 connections. (This rearranging of the existing traffic will cause these paths to experience traffic Hits). A VC3 test defrag gives a pessimistic list of the hit risk connections that will be effected. A VC3 Defrag will not cause a traffic hit to a VC3 connection that is already present. If there is less than 21 VC12 connections present then a VC3 Defrag will provision the mux to accept two VC3 connections. When adding these two connections directly after the defrag there will be no traffic disruption to existing traffic. If there is less than 42 VC12 connections present then a VC3 Defrag will provision the mux to accept one VC3 connection. When adding this connection directly after the defrag there will be no traffic disruption to existing traffic. A VC3 defrag will typically hit every VC12 connection on the mux. Each channel will be hit for up to 20 seconds. The more connections on the mux, the longer the mux is affected. For a full fill mux the total period is as follows: — Release 7 is 60 seconds — Release 8 is 30 seconds — Release 9 is 60 seconds.

Nortel TN-1X System Description

9

9-10 Connectivity

A VC3 Defrag should only be implement after, a VC3 test connect reports connections will be hit. •

VC-12. A VC12 Defrag will rearrange the connections on a mux in order to facilitate the addition of more VC12 connections with a reduced hit risk. This rearranging of the existing traffic will cause these paths to experience a traffic outage. A VC12 test defrag gives a pessimistic list of the hit risk connections that will be effected. A VC12 Defrag needs to be used after an upgrade from Release 8 and after removing a VC3 but before replacing that VC 3 with VC12 connections. It can also be used if a Mux has had its connections churned to an extent that adding any new VC12 connections results in a significant Hit Risk warning. A VC12 defrag will typically hit every connection on the mux. Each channel will be hit for up to 20 seconds. The more connections on the mux, the longer the mux is affected. For a full fill mux the total period is as follows: — Release 7 is 60 seconds — Release 8 is 30 seconds — Release 9 is 60 seconds. Before a VC12 Defrag is implemented a VC12 Test Defrag should be applied to check the connections that may get hit.

Traffic connections When the Subrack Controller is requested to connect a particular tributary port to a specific aggregate channel (drop/insert connection) or connect between aggregate channels (through connection), a validity check is first made to check if the ports and channels are already in use. The potential endpoints (tributary or aggregate port/channel) for the connection will be in one of the following states: • ‘Connected’ indicates that the payload is connected, and is not available for connection. • •

• •

‘Free’ indicates that the endpoint is not used and is free for a new connection without affecting existing traffic connections. ‘Hit_risk’ indicates that the payload is free, but using it will hit traffic under some circumstances. The user should use one of the test connect commands to establish the exact connections that will be hit. ‘Blocked’ indicates that the payload is not used, but is unavailable because the bandwidth is in use by an overlapping payload. ‘Blocked_internally’ indicates that the payload is blocked due to the internal architecture of the TN-1X.

•

‘Drop_Free’ indicates that the payload is available for drop connections only.

•

‘MSP_blocked’ means that the payload is blocked due to MSP usage.

323-1061-100 Release 9 Standard

Connectivity 9-11

The default configuration provides sixty-three VC-12 through connections (e.g. Aggregate A K111 to Aggregate B K111, Aggregate A K112 to Aggregate B K112). As the default setting provides sixty-three VC-12 through connections, to provide a protected terminal multiplexer configuration with two aggregate units it is necessary to make protected tributary connections for all the tributaries. All sixty-three through connections will have to be disconnected before making add/drop connections. To provide an unprotected terminal multiplexer with a single aggregate unit (i.e. for unprotected point-to-point systems, or end terminals in a drop and insert chain), all sixty-three through connections will have to be disconnected and the unused aggregate port unequipped before making the unprotected connections. Testing connections A test connection facility is provided on the user interface which allows the user to identify traffic hits that will occur as a result of changes to connectivity. This allows the implications of new connections to be assessed before they are made. The user can identify: • • •

traffic hits that will result from a new connection. If existing connections conflict with the proposed connection, these are identified as being at risk. traffic hits that will be affected by a defragmentation biased towards future VC-12 connections. traffic hits that will be affected by a defragmentation biased towards future VC-3 connections. Note: The physical connections between aggregates and tributaries are unchanged by defragmentation, but a traffic hit will occur if the bus slots that enable this connection are reconfigured.

Standby connections Each PDH port can be set to traffic auto mode (default) or traffic standby mode via the user interface. In the traffic auto mode: • •

if a connection exists and there is no signal, a PPI-LOS alarm is raised. if no connection exists and a signal is encountered, a PPI-Unexp_Signal alarm is raised.

In the traffic standby mode: • if a connection exists and a signal is detected, a PPI-Unexp_Signal alarm will be raised but the traffic on the tributary is still carried by the multiplexer. •

if no connection exists, no PPI-LOS or PPI-Unexp_Signal alarms are raised.

Nortel TN-1X System Description

9

9-12 Connectivity

The standby mode can be used to set up standby connections. The tributary connection is set up in the usual way and then the traffic mode is set to standby. No alarms will be generated until the physical traffic connection is made to the port. Once the physical traffic connection is made, a PPI-Unexp_Signal will be raised but the traffic signal will be carried by the multiplexer. The PPI-Unexp_Signal alarm can then be removed by setting the port to the traffic auto mode. User labels Each connection can be given a user label of up to 15 characters to allow users to assign customer names to connections. The allowable characters are the alpha-numeric characters (A-Z, a-z, 0-9), dash (‘-’) and underscore (‘_’). The user labels are displayed on all alarm and performance monitoring messages and reports associated with connections. The default labels associated with connections are as follows: • For drop connections to a PDH port, the port reference is used (for example, ‘S2-1’). • For drop connections to a STM-1 tributary payload, the payload reference is used (for example, ‘S4-1-J1-K111’). •

For through connections, the alternate aggregate payload reference is used (for example, ‘S7-1-J1-K123’).

Path trace (J1 and J2 byte) The Synchronous Digital Hierarchy provides a path trace capability. For the TN-1X, the path trace capability allows internal paths to be verified at the VC-3, VC-4 and VC-12 level.

J1 byte The VC-3/VC-4 path overhead bytes contain a path trace byte (J1 byte). The multiplexer cyclically transmits a 16 byte string. The string consists of a frame start marker byte (which contains a CRC-7 calculation over the previous frame) and 15 user configurable bytes. The incoming string is checked against the expected receive string, any discrepancy generates a HP-TIM (VC-4) or a LP-TIM (VC-3) alarm. The transmit 15 user bytes and the expected receive 15 user bytes are set up via the user interface. Note 1: If the VC-4 path trace facility is disabled, a constant zero pattern is transmitted in the HP path trace string. Note 2: When setting the transmit and receive values, strings of less than 15 characters are padded out with the underscore ‘_’ character. Note 3: Although the user interface allows the user to change the VC-4 path trace settings for STM-1 Tributary Units 25U JU00 750 GVA/GVB and 25U TM00 750 HWE, the path trace is fixed to the default setting on the unit and cannot be changed. If inter-connecting with an STM-1 Aggregate Unit, ensure the expected receive value for the STM-1 Aggregate Unit is set to the default setting to prevent a ‘HP-TIM’ alarm being raised.

323-1061-100 Release 9 Standard

Connectivity 9-13

Note 4: The default settings are ‘RX_UNALLOCATED_’ for the receive value and ‘TX_UNALLOCATED_’ for the transmit value. Note 5: The VC-4 high order path trace format used for this release is not compatible with releases 5 and before. As a consequence, a HP-TIM alarm will be raised if the Release 9 TN-1X is connected to an TN-1X Release 5 or earlier. Note 6: High order path trace settings for MSP protection pairs can only be made against the working section. Configuration of the protection section is not supported. This will automatically mirror the settings of the working section. J2 byte The J2 path trace byte is defined by ITU-T standard G.707 as part of the VC-12 signal path overhead (POH). Sixteen J2 bytes taken together from successive transmissions constitute one frame and this is used as a way of attaching a low order path access point identifier to a VC-12 path. The CLUI is used to modify a user-defined ASCII text string that is transmitted over the J2 byte for any given connection and also define the string that should be received. The user can only enter a fifteen-character string, the sixteenth byte being reserved as a checksum (however the user may also manually edit this if so desired). The default settings are: • Path Trace Transmit String:

TX_UNALLOCATED_

• •

RX_UNALLOCATED_ Misaligned

Path Trace Expected String: Path Trace Status:

This transmitted string is extracted at the remote mux and compared to the user-defined expected value. If the transmitted and expected strings do not match then the connection is incorrect, while a CRC check highlights transmission problems. Monitoring is supported at the Preside. An LP-TIM (low order path trail information mismatch) alarm is raised at the local mux if there is a mismatch in the expected and received strings. Note: The 2 Mbit/s Tributary unit 75 Ω NTKD23AA must be equipped as a 25U JU00 750 HVT unit and the 2 Mbit/s Tributary unit 120 Ω NTKD23AB must be equipped as a 25U JU00 750 HVQ unit. Note: 2 Mbit/s tributary cards 25U JU00 750 GXG and 25U JU00 750 GXR do not support the path trace due to hardware limitations. 25U JU00 750 HVT v3.5 ASIC does not support J2 path trace. Consequent actions The system can be configured to generate consequent actions as a result of a the path trace alarms: • TU-AIS and HP-RDI consequent actions as a result of a HP-TIM alarm. Nortel TN-1X System Description

9

9-14 Connectivity

•

Tx-Trib-AIS and LP-RDI consequent actions as a result of a LP-TIM alarm

The consequent actions are enabled/disabled individually via the user interface. Note: If consequent actions are enabled and the path trace is changed, a caution is given indicating that this action may cause traffic disruption. Single fibre working When operating in a single fibre mode (i.e. one optical fibre to carry bi-directional optical signals between adjacent multiplexers), if the fibre breaks the transmitted signal may be echoed to the receive optical port on the same multiplexer. This signal must be recognised as faulty and AIS transmitted downstream. The high order path trace facility should be used to ensure signal integrity by setting the transmit and receive high order path trace settings to different values and enabling consequent actions. By using the high order path trace facility with consequent actions enabled, a HP-TIM alarm will be raised and AIS transmitted downstream if a fibre break occurs and the echoed signal is sufficient to constitute a valid signal. Note 1: If HP-RDI is enabled as a consequent action of a HP-TIM alarm, the transmitted signal will have the HP-RDI set. This will be received in the echoed signal causing a HP-RDI alarm to be raised on the same multiplexer that generated it. Note 2: If consequent actions are enabled for the HP-TIM alarm, detection of a HP-TIM alarm on an STM-1 Aggregate Unit or an STM-1 Tributary Unit will assign that card as a failed synchronisation source if it was in the synchronisation hierarchy. The same also applies to the STM-4 Aggregate Unit but a Qecc-Comms_Fail alarm must also be detected against an Aggregate Unit before a synchronisation source switch will occur. Note 3: Multiplexer Section Protection (MSP) should NOT be used when single fibre working is in use.

323-1061-100 Release 9 Standard

Connectivity 9-15

Signal label (C2 and V5 bytes) The path overhead provided by the Synchronous Digital Hierarchy includes signal label information which indicates the composition of the signal. For the TN-1X, signal label information is provided in the VC-12, VC-3 and VC-4 path overheads. The transmit and receive values are set up via user interface. Any discrepancy between the receive value and the expected receive value generates a signal label (PLM) alarm at the appropriate level (i.e. LP-PLM for VC-12 or VC-3 and HP-PLM for VC-4). VC-12 signal label The VC-12 path overhead contains three signal label bits (bits 5 to 7 of V5 byte), allowing eight different values (‘0’ to ‘7’). The meaning of the eight values is as follows: • •

‘0’ indicates that the VC-12 path is unequipped ‘1’ indicates that the VC-12 path is equipped with a non-specific payload

• •

‘2’ indicates that the VC-12 path is equipped with asynchronous mapping ‘3’ indicates that the VC-12 path is equipped with bit synchronous mapping ‘4’ indicates that the VC-12 path is equipped with byte synchronous mapping

•

• ‘5’ to ‘7’ are reserved to be defined for future specific VC-1 mappings Any value received other than ‘0’ indicates an equipped VC-1 path. The value is set to ‘0’ automatically if the tributary (VC-12 path) is unequipped. On current equipment, the value should be set to ‘2’ for equipped paths (default). Note: If the Tx Signal Label is set to ‘0’, the PPI-LOS alarm is disabled. If a valid signal is applied to the appropriate input with the Tx Signal Label set to ‘0’, a PPI-Unexp_Signal alarm will be raised. VC-3 signal label The VC-3 path overhead contains a signal label byte (C2), allowing 256 different values (‘0’ to ‘255’). A value ‘0’ indicates that the VC-3 path is unequipped. A value ‘1’ indicates that the VC-3 path is equipped with a non-specific payload, a value ‘4’ indicates that the VC-3 path is equipped with a C3 asynchronous mapped tributary. The remaining values are reserved to be defined for specific VC-3 mappings. Any value received other than ‘0’ indicates an equipped VC-3 path condition. The value ‘0’ should be set if the section is complete but there is no VC-3 path originating equipment. On current equipment, the value should be set to ‘4’ (default) if a 34 Mbit/s or 45 Mbit/s tributary (VC-3) is equipped. Note: The Tx Signal Label can be set to any value between ‘0’ and ‘255’ and the Rx Signal Label can be set to any value between ‘0’ and ‘255’.

Nortel TN-1X System Description

9

9-16 Connectivity

VC-4 signal label The VC-4 path overhead contains a signal label byte (C2), allowing 256 different values (‘0’ to ‘255’). A value ‘0’ indicates that the VC-4 path is unequipped. A value ‘1’ indicates that the VC-4 path is equipped with a non-specific payload, a value ‘2’ indicates that the VC-4 path is equipped with a TUG structure. The remaining values (‘3’ to ‘255’) are reserved to be defined for specific VC-4 mappings. Any value received other than ‘0’ indicates an equipped VC-4 path condition. The value ‘0’ should be set if the section is complete but there is no VC-4 path originating equipment and is therefore not used in present applications. On current equipment, the value should be set to ‘2’ (default). Note 1: The Tx Signal Label can be set to any value between ‘0’ and ‘255’ and the Rx Signal Label can be set to any value between ‘0’ and ‘255’. Note 2: VC-4 payload label settings for MSP protection pairs can only be made against the working section. Configuration of the protection section is not supported. This will automatically mirror the settings of the working section. Consequent actions The system can be configured to generate consequent actions as a result of a the signal label alarms: • TU-AIS and HP-RDI consequent actions as a result of a HP-PLM alarm. •

Tx-Trib-AIS and LP-RDI consequent actions as a result of a LP-PLM alarm The consequent actions are enabled/disabled individually via the user interface. Note: If consequent actions are enabled and the signal label is changed, a caution is given indicating that this action may cause traffic disruption. end of chapter

323-1061-100 Release 9 Standard

10-1

Protection

10-

VC-12/VC-3 path protection switching For the Nortel Networks TN-1X, the Subrack Controller can provide autonomous Path Protection Switching (PPS) at the VC-12 and VC-3 levels. Protection of the VC-12s and VC-3s is performed by transmitting the VCs from both aggregate ports (thus transmitting the VCs both ways round a ring or on both paths of a duplicated point-to-point system) and performing autonomous protection switching between the received VCs at the terminating multiplexer. Protected VCs occupy the same logical channel at both aggregate ports. Unprotected VCs only occupy a logical channel at one aggregate port, allowing the same logical channel at the other aggregate unit to be used for another unprotected VC. If an optical fault (e.g. fibre break) occurs, a laser shutdown is initiated (refer to “Automatic laser shutdown” on page 3-17) which causes traffic in both directions of the ring section to be shut down. This results in a dual ended path switch that sustains traffic during an optical fault in one section of the ring. Modes of operation Path protection switching can be in one of two modes which are selectable via the user interface. •

Automatic In the automatic mode (PPS on), a path protection switch will occur if any of the following alarms exist on the Payload Manager, 2 Mbit/s Tributary Unit, 34 Mbit/s Tributary Unit (16x2) or 34/45 Mbit/s Tributary Unit (VC-3): PAYLOAD MANAGER High-order Path (HP)

INT- AU-AIS INT-AU-LOP HP-LOM

Low-order Path (LP)

TU-AIS TU-LOP

TRIBUTARY UNIT

10 LP-EXC

Note 1: The HP alarms cause a protection switch on all the protected VC-12 and VC-3 paths, the LP alarms cause a protection switch on the specific VC-12 or VC-3 path against which the specific alarm was raised. Nortel TN-1X System Description

10-2 Protection

Note 2: A protection switch will also occur on all protected VC-12 and VC-3 paths as an indirect consequence a RS-LOS, RS-LOF, MS-AIS, MS-EXC and HP-TIM alarms raised on an Aggregate Unit (due to AU-AIS being injected towards the Payload Manager). Path protection switching is controlled by the user interface and is enabled/ disabled for each path separately.

•

Automatic path protection switching is disabled for 2 minutes after changing the on-line configuration. If a condition which should trigger protection switching occurs during the two minutes, switching will be delayed until the end of the 2 minute period. Manual In the manual mode (PPS off), a path protection switch can be initiated on each path individually via the user interface. It is not possible to perform a manual switch while the mux is in detached mode.

Provisionable Hold-Off time Path protection provisionable hold off time is an un-supported feature in Release 9. Persistence checks Failure persistence check To allow for higher-level protection to occur on other high level systems (e.g. where a protected VC-12 path is through a higher level STM-16 ring) before initiating a path protection switch, a failure persistence check is performed prior to switching. This check period also protects against short glitches causing undesired protection switches. Restoration persistence check To prevent the a protection switch to a faulty path and to prevent excessive oscillations between paths due to LP-EXC alarms being raised on both paths, a restoration persistence check is performed. A protection switch to the standby path will not occur if the standby path has any of the path failure conditions in the restoration persistence check period (the preceding 30 seconds). The check on the standby path cannot detect LP-EXC alarm as the standby path is not dropped to the 2 Mbit/s Tributary, 34 Mbit/s Tributary Unit (16x2) or 34/45 Mbit/s Tributary Unit (where the LP-EXC alarm is detected). A protection switch will not occur until after the 30 seconds restoration persistence check period. However, a switch will occur if a LP-EXC alarm is present on both paths after the restoration check period. A switch will then occur every 30 seconds until LP-EXC alarm is cleared from at least one path. STM-1 tributaries As described in “Modes of operation” on page 10-1, TU-AIS is used as the main mechanism to trigger automatic path protection switching. When using STM-1 Tributary Unit variants (25U TM00 750 HWG, 25U TM00 750 JBK, NTKD11AA, NTKD12AA, NTKD11AB and NTKD11BA), TU-AIS is

323-1061-100 Release 9 Standard

Protection 10-3

propagated between aggregate and STM-1 tributary paths, allowing for full subnetwork connection protection. When using STM-1 Tributary Units 25U JU00 750 GVA/GVB and 25U TM00 750 HWE, TU-AIS is not propagated on the STM-1 tributary links. Path protection on a network containing these STM-1 Tributary Units is provided by using the LP-EXC alarm as the trigger mechanism. This is possible as the BIP-2 bits (part of the V5 path overhead byte) are always set to one during TU-AIS and thus always generate an LP-EXC alarm under TU-AIS conditions. Note 1: If a network failure leads to both the main and standby paths of a protected channel receiving LP-EXC alarms, protection switching between the main and standby paths will occur every 30 seconds (see “Restoration persistence check” on page 10-2). Note 2: For interoperation with other equipment that does not support LP-EXC triggered path protection, path protection switching is not supported for traffic that traverses a TN-1X STM-1 tributary using STM-1 Tributary Units 25U JU00 750 GVA/GVB and 25U TM00 750 HWE. Note 3: When using a ‘protected’ STM-1 link, if a ‘HP-TIM’ alarm is raised and AIS is generated as a consequent action, the switch to the other path takes up to 20 seconds. The standby path must be error free for 30 seconds before a switch occurs.

1:N 2 Mbit/s tributary protection 1:N tributary protection allows traffic on any of the 2 Mbit/s Tributary Units to be switched to a protection 2 Mbit/s Tributary Unit in the low-speed tributary protection slot (subrack slot S3). For 1:N protection to be used, the following units/modules must be fitted: • 2 Mbit/s Tributary Units in the normal (S2, S4, S9, and S11) and protection (S3) slots must be of the same impedance type (75 Ω or 120 Ω). • The protection 2 Mbit/s Tributary Unit in slot S3 must be equipped as either HVT or HVQ. •

•

1:N Protection 2 Mbit/s Traffic Access Modules (TAMs) must be fitted to the subrack. Each 2 Mbit/s Tributary Unit, except the protection 2 Mbit/s Unit, requires two 1:N Protection TAMs. The EOW Unit (ICC2) (NTKD13AA) must be equipped. Note 1: 1:N protection is not supported in the TN-1X/S. Note 2: Once 1:N tributary protection is enabled, the above units cannot be logically unequipped. Note 3: 1:N tributary protection can be enabled if the logical equipping is correct even if the physical equipment to support 1:N protection is not present. Ensure that no relevant NE-Card_Out alarms are present, in particular the EOW Unit (ICC2).

Nortel TN-1X System Description

10

10-4 Protection

Note 4: Early versions (PCS1 and 2) of Payload Manager 25U PJ00 750 GXF will allow 1:N protection to be enabled, but do not support it. In normal operation, the TAMs connect the tributary signals to its assigned 2 Mbit/s Tributary Unit. When a switching condition is raised, the TAMs connect the tributary signals associated with the faulty 2 Mbit/s Tributary Unit to the protection 2 Mbit/s Tributary Unit (all the tributary signals associated with faulty 2 Mbit/s Tributary Unit are switched together). CAUTION 1:N 2 Mbit/s tributary switching

If 1:N tributary protection is enabled, do not remove an active 2 Mbit/s Tributary Unit. Perform a manual 1:N protection switch to the protection 2 Mbit/s Tributary Unit before removing an active 2 Mbit/s Tributary Unit. CAUTION Rebooting a multiplexer

Performing a cold reboot of a multiplexer with 1:N protection enabled and actively protecting a slot, will cause loss of traffic for up to 12 minutes. Modes of operation 1:N protection switching can be in one of the following four modes which are selectable via the user interface. Disabled When 1:N tributary protection is disabled, no protection of the 2 Mbit/s Tributary Unit is provided, even though the necessary units may be equipped. Automatic In the automatic mode, 1:N protection switching is controlled by the multiplexer. An automatic 1:N protection switch will occur if any of the following alarm conditions exist on a 2 Mbit/s Tributary Unit in slot S2, S4, S9 or S11: NE-Card_Out NE-Card_Fail NE-Card_Fault On detection of a NE-Card_Out event, a 1:N protection switch occurs. Traffic is routed through the protection card and full traffic will be restored. (NE-Card_Fail and NE-Card_Fault can take seconds to detect). After an automatic switch has occurred, no more automatic switches are possible as the protection 2 Mbit/s Tributary Unit is being used to carry traffic.

323-1061-100 Release 9 Standard

Protection 10-5

If the working card recovers, traffic remains permanently on the protection card, unless the user performs a manual reversion. Auto-revertive The auto-revertive mode enables traffic being carried on the protection card to return automatically to the working card when the condition causing the protection switch clears. This normally occurs a specified time after the condition has cleared. This time interval is known as the Wait-To-Restore (WTR) period (300 seconds). The WTR period applies to the protection card. Note: The auto-reversion feature is not supported on the Preside. Manual In the manual mode, the protection switch is initiated by the user via the user interface. It is not possible to perform a manual switch while the mux is in detached mode. Switching prerequisites Before a manual or automatic 1:N protection switch can be performed, the following prerequisites must be met: •

• •

The EOW Unit (ICC2), the active Payload Manager and the protection 2 Mbit/s Tributary Unit (slot S3) do not have any NE_Card_Fail, NE_Card_Out, or NE-Card_Fault alarms present. The faulty 2 Mbit/s Tributary Unit must have traffic connections made. A 1:N protection switch has not already been made, i.e. the protection 2 Mbit/s Tributary Unit (slot S3) does not have traffic connections. Note: Once a 1:N protection switch has occurred, no further traffic connections can be made to the protection 2 Mbit/s Tributary Unit until the manual reversion is performed.

1:N tributary switching alarms There are a number of alarms associated with 1:N tributary protection switching as follows: •

NE-np1_switch_Alarm. This alarm indicates that a successful manual or automatic switch to the protection 2 Mbit/s Tributary Unit has occurred and the other 2 Mbit/s Tributary Units are no longer protected. The alarm will be cleared when a manual reversion to the original 2 Mbit/s Tributary Unit is performed.

•

NE-Card_Out (for TAM slot). This alarm indicates that an 1:N Protection 2 Mbit/s TAM has been removed from the subrack. NE-Wrong_Card (for TAM slot). Indicates that a wrong TAM has fitted or the 1:N Protection TAM has failed.

•

Note 1: The NE-Card_Out and NE-Wrong_Card alarms for TAM slots are only reported if the 1:N tributary protection is enabled.

Nortel TN-1X System Description

10

10-6 Protection

Note 2: Once the switching action is complete, monitoring of all alarms (except NE-Card_Out and NE-Card_Fail) on the protection 2 Mbit/s Tributary Unit are ignored for 30 seconds to allow spurious alarms to settle.

323-1061-100 Release 9 Standard

Protection 10-7

Payload Manager switching The TN-1X can be fitted with duplicated Payload Managers. CAUTION Payload Manager switching

Do not remove the active Payload Manager. A loss of traffic for up to 10 minutes can occur once a new Payload Manager is inserted. A Payload Manager switch can cause temporary loss of traffic, path protection switches, MSP switches, and temporary alarms. Payload Manager switching should not be performed unless absolutely necessary. Switching between Payload Managers should preferably only be performed during periods of low traffic density. Payload Manager switches should not be done more often than every 6 minutes on a single NE. The Payload Managers operate in a main/standby mode with only the traffic outputs of one Payload Manager active at any one time. If the Subrack Controller detects a fault on the main Payload Manager, it instructs the standby Payload Manager to become active (if no faults are present on the standby Payload Manager). The Subrack Controller also instructs the relevant tributary and aggregate units to receive/transmit via the standby Payload Manager. Payload Manager (B) is the default main unit. Modes of operation Payload Manager switching can be in one of two modes selectable via the user interface. •

Automatic In the automatic mode, Payload Manager switching is controlled by the Subrack Controller and will occur if any of the following alarm conditions exist on the active Payload Manager: NE-Card_Out NE-Card_Fail NE-Card_Fault INT-NE-Comms_Fail INT-SYNC-Oscillator_Fail HP-LOM Note: Automatic Payload Manager switching cannot be enabled unless both Payload Managers are of the same type. This prevents incorrect operation when VC3 traffic is being carried.

•

Manual In the manual mode, the protection switch is initiated by the user via the user interface. It is not possible to perform a manual switch while the mux is in detached mode.

Nortel TN-1X System Description

10

10-8 Protection

Switching prerequisites Before a manual or automatic Payload Manager switch can be performed, the following prerequisites must be met: • • •

the standby Payload Manager is equipped and does not have any of the Payload Manager switching conditions (see above). if the Payload Manager switching is automatic, the standby Payload Manager must be the same variant as the active Payload Manager. if the Payload Manager switching is manual, no VC-3 connections must be present if switching from a mixed payload Payload Manager to a non-mixed payload Payload Manager.

323-1061-100 Release 9 Standard

Protection 10-9

Multiplexer section protection Multiplexer section protection (MSP) is a mechanism that enables protection switching for all traffic on an STM-1 channel. A 1+1 protection architecture is supported, which uses a second STM-1 channel of the same type. This protection channel carries the same traffic as the original working channel. MSP controls which of these channels is used as the current channel. MSP monitors both STM-1 channels for failures. The protection status of the link is carried in the K1 and K2 bytes within the multiplexer section overhead of the protection channel. The MSP mechanisms on the local mux and the remote mux transmit protection status information using these bytes. This enables the mechanisms to determine which of the channels should be used, and to perform a protection switch as appropriate. MSP will switch to the protection channel under a number of alarm and non-alarm conditions. To revert to using the working channel, a manual switch must be used. Automatic reversion is not supported. The MSP mechanism can be locked to prevent the use of the protection section. It is also possible to force the mechanism to use either the working channel or the protection channel, and to test the working channel for errors. When MSP is established, the protection channel must have no connections present. There is a command that converts protected connections to unprotected connections on aggregates that are to be used for MSP. Also, MSP cannot be established on an STM-1 tributary unit that has trib-to-trib connections. Once MSP is established, the protection channel is inaccessible to the user, but its configuration mirrors that of the working channel at all times. All references in events, logs and reports to MSP channels refer to the working channel, even after a protection switch. Protected drop connections are supported when a pair of STM-1 tributary channels are used for MSP. Protected drop connections are not supported when both STM-1 aggregates are used for MSP. MSP supports both unidirectional and bidirectional modes of operation. Note: A synchronisation sync source switch does not necessarily occur as a result of a MSP switch. These mechanisms operate independently.

10

Nortel TN-1X System Description

10-10 Protection

MSP configurations On the TN-1X, MSP makes use of both aggregates or a pair of STM-1 tributaries. These are connected in a point-to-point configuration to a pair of aggregates or tributaries on another SDH multiplexer (such as TN-1X, TN-1C, TN-1P, TN-4X, TN-16X). Supported MSP configurations are shown in Figure 10-1. Figure 10-1 MSP configurations

Between aggregates

Between aggregates and tributaries

Between tributaries

TN-1X mux

Non-MSP aggr/trib channels

SDH mux

MSP aggr/trib channels

For example, a network that uses MSP protection between two rings is shown in Figure 10-2. The two rings are connected via an STM-1 tributary channel (Link X). A second tributary channel that carries identical traffic (Link Y) provides 1+1 MSP protection. If Link X fails, an MSP switch occurs. The protected and unprotected traffic that was received at either end of the protected channel from Link X is received instead from Link Y. Figure 10-2 MSP protection between rings

Link X

Ring 2

Ring 1 Link Y

323-1061-100 Release 9 Standard

Protection 10-11

Bidirectional and unidirectional operation The MSP mechanism supports both unidirectional and bidirectional operation. These are detailed in the sections that follow. Unidirectional operation In unidirectional mode, traffic moves in both directions, but the MSP mechanisms operate independently. That is, switching is evaluated at the receive end only. When a switch occurs, only the failed direction is switched from the working channel to the protection channel. Override values for the K1 and K2 bytes can be used for unidirectional operation. Unidirectional operation is illustrated in Figure 10-3. Note 1: Unidirectional operation is implemented in the same way for all MSP configurations. Note 2: Unidirectional operation when interworking with Nortel Networks TN-16X or SONET equipment may result in loss of communications. Figure 10-3 Unidirectional operation Before Switch

After Switch

Failed Channel

10 Transmitted Channel (In Use) Transmitted Channel (Not In Use)

Nortel TN-1X System Description

10-12 Protection

Bidirectional operation This is the default setting. In bidirectional mode, traffic moves in both directions, but the MSP mechanisms communicate and coordinate the switching of both channels as a pair. When a switch occurs, the use of both channels is switched from the working channel to the protection channel. Switching of a single direction is not supported in this mode. Override values for the K1 and K2 bytes are not used during bidirectional operation. Bidirectional operation is illustrated in Figure 10-3. Note 1: For bidirectional mode to be active, both local and remote NEs must be configured to use bidirectional mode. If only one is configured in this way, MSP will not function correctly. Note 2: Bidirectional operation is implemented in the same way for all MSP configurations. Note 3: Bidirectional operation is the preferred method when interworking with Nortel Networks TN-16X and SONET equipment. Figure 10-4 Bidirectional operation Before Switch

After Switch

Failed Channel

Transmitted Channel (In Use) Transmitted Channel (Not In Use)

323-1061-100 Release 9 Standard

Protection 10-13

Switching conditions TN-1X supports both manual and automatic MSP switching. It is not possible to perform a manual switch while the mux is in detached mode. An automatic MSP switch is initiated via the K bytes under the following conditions: • •

Equipment failure. This is characterised by a Signal Failure (SF) condition, specifically card fail, card fault or card out alarms. A ‘hard failure’ condition detected on the incoming STM-1 signal. This is characterised by a signal failure (SF), specifically LOS, LOF, MS-AIS or MS-EXC alarms. Note: Receipt of LOS causes a laser shutdown in addition to the switch. This causes an LOS on the remote mux, causing a switch. As a result, both channels switch. This occurs irrespective of whether bidirectional or unidirectional modes are active.

•

A ‘soft failure’. This is characterised by a Signal Degrade (SD) condition, specifically a signal degrade threshold being exceeded on the incoming STM-1 signal.

For unidirectional operation, a switch away from the failed channel is initiated and executed by the receiving MSP. For bidirectional operation, the local and remote MSP mechanisms communicate and co-ordinate the switching of both channels. MSP protocol MSP operates using a bit-oriented protocol that is transmitted in the K bytes (K1 and K2) of the multiplexer section overhead of the protection channel. The K bytes indicate the protection status of both working and protection channels, and are used by the MSP mechanisms on the local and remote multiplexer to determine any required switching actions. The K1 byte The K1 byte indicates a request from the multiplexer that generated it: •

Bits 1 to 4 indicate the request type. — A condition associated with a failure. For example, Signal Degradation (SD) or Signal Failure (SF). This condition can be high or low priority (high by default). — A state of the MSP function. For example, Wait To Restore (WTR), Do Not Revert (DNR), No Request (NR), Reverse Request (RR). — An external request. For example, Lockout of Protection, Forced, Manual or Exercise.

•

Bits 5 to 8 indicate the channel for which the request is issued. This indicates either the working or protection channel. Note: There are a number of binary settings that are not generated by the TN-1X. Other SDH equipment can generate these settings, however, and the TN-1X will recognise these.

Nortel TN-1X System Description

10

10-14 Protection

The operational values for bits 1 to 4 of the K1 byte are shown in Table 10-1. Table 10-1 K1 byte (bits 1 to 4) usage Bits

Value

Request

Type

Description

1111

15

Lockout of Protection

External

Highest priority.

1110

14

Forced Switch

External

Force switch unless locked out.

1101

13

Signal Fail - high priority (see note)

Condition

Switch due to a signal fail (high priority).

1100

12

Signal Fail - low priority

Condition

Switch due to a signal fail (low priority). TN-1X does not generate this.

1011

11

Signal Degrade - high priority

Condition

Switch due to BER conditions (high priority).

1010

10

Signal Degrade - low priority

Condition

Switch due to BER conditions (low priority). TN-1X does not generate this.

1001

9

Unused

N/A

N/A

1000

8

Manual Switch

External

Force switch unless alternative channel degraded.

0111

7

Unused

N/A

N/A

0110

6

Wait to Restore

State

Used in revertive schemes to delay reversion. Typically 5 to 12 minutes, configurable in 1 minute steps. TN-1X does not generate this.

0101

5

Unused

N/A

N/A

0100

4

Exercise

External

Used to check K byte operation.

0011

3

Unused

N/A

N/A

0010

2

Reverse Request

State

Consequence of Far-End request. Not used in Unidirectional mode.

0001

1

Do Not Revert

State

Used in Non-Revertive mode.

0000

0

No Request

State

Normal condition. Lowest priority.

Note - A signal fail on the protection section will take priority over any forced request which would cause an MSP switch from the working section to the protection section.

323-1061-100 Release 9 Standard

Protection 10-15

The operational values for bits 5 to 8 of the K1 byte are shown in Table 10-2. Table 10-2 K1 byte (bits 5 to 8) usage Bits

Value

Description

0000

0

Protection channel used (high priority).

0001

1

Working channel used.

0010 - 1111

2 - 15

Other traffic channels. TN-1X will not generate this.

The K2 byte The K2 byte carries status information: •

Bits 1 to 4 indicates the channel number being bridged. This is the number of the channel being carried simultaneously on the standby channel.

•

Bit 5 indicates whether 1+1 or 1:N architecture is in use. Note: 1:N architecture is not supported by TN-1X.

•

Bits 6-8 are mostly reserved for future use, though there are two values that are used currently. Note: There are a number of binary settings that are not generated by the TN-1X. Other SDH equipment can generate these settings, however, and the TN-1X will recognise these.

The operational values for the K2 byte are shown in Table 10-3. Table 10-3 K2 byte usage Bits

Bits

Value

Description

1 to 4

0000

0

Protection channel used (high priority).

0001

1

Working channel used.

1111 - 0010

2 - 15

Other traffic channels. TN-1X will not generate this.

0

0

1+1 protection architecture is in use.

1

1

1:N protection architecture is in use. TN-1X will not generate this.

000 - 101

0-5

Reserved for future use.

110

6

MS-RDI present.

111

7

MS-AIS present.

5

6 to 8

10

Nortel TN-1X System Description

10-16 Protection

Evaluation of requests Requests from the local and remote multiplexers are evaluated as follows: •

Bidirectional mode. The requests from the transmitted and received K1 bytes are compared to determine the highest priority request (see Table 10-1). If a higher priority request is received, a reverse request is transmitted to indicate this, and the request will be implemented. An equal priority with a lower channel number is handled in the same way.

•

Unidirectional mode. The local and remote K1 bytes are not compared. The local request is only affected by a change to the state of the local multiplexer. That is, a higher priority request occurs locally, or the current request becomes invalid.

Selection of the current channel Selection of the current channel is performed as follows: • Bidirectional mode. The remote channel number in the K2 byte is compared with the channel number in the local K1 byte. If the channel numbers are the same, this channel becomes/remains current. If the channel numbers are different for longer than 50 ms, an alarm is raised. •

Unidirectional mode. Selection of the current channel is determined by the highest priority local request.

MSP alarms The following new alarms are supported by the TN-1X in bidirectional operation. These alarms will be cleared once expected behaviour is restored: •

•

•

MSP_Prot_Scheme_Mismatch. This is raised after 50 ms if there is a difference between bit 5 in the sent and received K2 byte. This indicates that the remote and local MSP mechanisms are configured for different MSP architectures. MSP_Invalid_K_Bytes. This is raised if there is an invalid channel number or an invalid request indicated in either of the received K bytes for longer than 50 ms. In this instance, if the protection channel is in use, a signal fail condition on the protection section occurs. As a result, an MSP protection switch from the protection channel to the working channel occurs. MSP_Channel_Mismatch. This is raised if the K1 transmitted and K2 received channel numbers are different for longer than 50 ms. In this instance, if the protection channel is in use, a signal fail condition on the protection section occurs. As a result, an MSP protection switch from the protection channel to the working channel occurs. This alarm will not be raised if there is a signal fail on the protection section. Note: The ‘MSP_Invalid_K_Bytes’ and ‘MSP_Channel_Mismatch’ alarms can also be raised if there is a mismatch in MSP modes used by interworking equipment.

323-1061-100 Release 9 Standard

Protection 10-17

The MSP alarms listed above are always reported against the protection channel. MS and RS alarms that relate to multiplexer protection channels are always reported against the affected channel. All other alarms that relate to multiplexer protection channels are reported against the working channel. For details of the structure and usage of the K1 and K2 bytes, see “MSP protocol” on page 10-13. MSP LAPD settings The TN-1X supports the use of two LAPD channels for each MSP pair. When interacting with equipment that supports one LAPD channel, it is possible to disable the monitoring of the LAPD channel on the non-active section. When MSP LAPD monitoring is disabled, a QECC alarm cannot be raised against the non-active section. When an MSP switch occurs, monitoring of the LAPD channel also switches, and LAPD monitoring on the new non-active channel is disabled. Note: The MSP LAPD settings on are ignored if LAPD is disabled for the active port Converting protected connection to unprotected connections When MSP is established, the protection channel must have no connections present. To prepare a pair of aggregate channels for use with MSP, it is possible to convert all protected connections to unprotected connections. Note: This process should be performed on both the local and remote multiplexers. Before this is performed, all protected traffic passing between the multiplexers should be switched to one of the aggregate channels.

10

Nortel TN-1X System Description

10-18 Protection

1:1 manual tributary protection The TN-1X supports the protection of VC-3 traffic on up to two 34/45M tributary units. This enables VC-3 traffic to be protected during the replacement of a faulty 34/45M tributary unit, or during scheduled maintenance. The manual tributary protection mechanism uses a 1:1 architecture. That is, each protected tributary unit requires a dedicated protection tributary unit. When a manual tributary protection switch is performed, a VC-3 connection is made on the 34/45M protection unit, along with all configuration settings for the protected unit. The VC-3 traffic is then moved to the protection card, and the original connection is deleted. To revert to the protected card, the protection switch must be cleared manually. Note 1: For manual tributary protection to operate successfully, new 1:1 protection TAMs must be installed to support the protection units that are installed in slots 4 and 11. Also, a new variant of the Star Card is required. The use of these cards is detailed in the TN-1X Module Replacement Procedures handbook. Note 2: Once a manual protection switch is made, refresh the Preside EC-1 Element Controller connection interface, if it is in use. Note 3: Manual tributary protection switching is not possible when the mux is in detached mode. Note 4: Cold restarting a mux with manual tributary protection enabled and actively protecting a slot will cause a loss of traffic for up to 12 minutes. Note 5: When a manual VC-3 tributary protection switch is performed, any LP-TIM or LP-PLM alarms that exist will be lost. The monitoring needs to be re-enabled after switching. A manual tributary protection switch can be made at any time, either to restore traffic after the failure of a protected 34/45M tributary unit, or to enable maintenance on the protected unit. The following restrictions apply to manual tributary protection: • • • • •

Both slots in a protection pair must be equipped as 34/45M VC-3 tributary units before the feature can be enabled for the pair. The protection unit must be free of connections before the feature can be enabled for the pair. The ICC2 card must be present and equipped before the feature can be enabled. The ICC2, Star Card and supporting TAMS must all be present before a switch can be performed. Configuration of path trace, signal label, alarm monitoring and bit rate settings is not permitted on the protection unit once the feature is enabled.

323-1061-100 Release 9 Standard

Protection 10-19

•

It is not possible to unequip a card in a protection pair once the feature is enabled.

•

It is not possible to perform a manual switch while the mux is in detached mode. It is recommended that tributary units involved in protection pairs are not used for synchronisation source purposes.

• •

Performance monitoring for a protected unit is disabled by a manual switch. Performance monitoring settings must be configured manually for a protection card after a manual switch. Note: User interface commands that display connection and payload information will report that there are no connections on the protection tributary unit. However, these payloads are not available for connections. It is not possible to make a VC-3 connection manually on a protection unit once manual tributary protection for the pair is enabled.

To disable 1:1 tributary protection for a protection pair, the NE must not be using the tributary protection mechanism on the affected pair. If the protection mechanism is in use, a manual switch back to either slot 2 or 9 is required before the mechanism can be disabled. end of chapter

10

Nortel TN-1X System Description

11-1

Performance monitoring

11-

The Nortel Networks TN-1X generates performance monitoring information at various levels of the SDH (performance monitoring points - PMPs). This information is processed by the Subrack Controller and stored as performance logs. These logs are used as the basis for performance monitoring and are accessible from the user interface. Performance monitoring allows the user to measure transmission quality on an on-going basis. Note: By default, all collection of all performance monitoring data and the monitoring of performance monitoring alarms are disabled.

Types of parity error counts The TN-1X provides two types of parity error counts, bit counts and block counts: • Bit counts are the sum of all Bit Interleaved Parity (BIP) parity errors detected in the count period (nominally 1 second). •

Block counts are the sum of all BIP blocks in error detected in the count period (nominally 1 second).

The option to use either bit counts or block counts is configurable on a multiplexer wide basis via the user interface (default is Block counts). Note: Some PMPs do not support Block counts. If Block counts are selected, PMPs which do not support Block counts will use Bit counts. All performance logs/reports indicate the basis (bit or block) for the displayed counts.

Performance counts There are a number of performance counts that are accumulated within the TN-1X. These are: • 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 11-2 for 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

Nortel TN-1X System Description

11

11-2 Performance monitoring

also, by definition, an ES. The threshold number of errors which distinguish an ES from an SES can be configured by the user, for both bit and block counts. • •

•

•

•

Background Block Errors (BBE). A BBE is a block (not included in a SES) in which there is an anomaly. 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). Note: During periods of UAT, the ES, SES and BBE statistics are not recorded. The start of the UAT is indicated by ten consecutive SES. 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. Out Of Frame (OOF) seconds. A OOF second is recorded when one or more out-of-frame condition is detected within the regenerator section overhead of an STM-1 frame. Pointer Justification Events (PJE). A PJE is recorded when a positive or negative movement of a payload pointer within an STM-1 frame is detected. The bytes that point to the payload will vary depending on the payload. The total number of negative PJEs is also recorded. The difference between these two counts identifies the number of positive pointer movements. Assessed Seconds (AS). The AS is the number of seconds during which the performance monitoring statistics were accumulated. Typically, this is equivalent to the length of the performance monitoring period. However, if the TN-1X 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,

323-1061-100 Release 9 Standard

Performance monitoring 11-3

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-1X 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: HP, HP-FE and AU-PJE performance monitoring points for pairs of MSP channels will always be reported against the working section. Note 3: PPI-CV performance monitoring must not be enabled for ports that have either PPI-AIS consequent actions or monitoring disabled for the port. Note 4: PPI-CRC (CRC4) is only available on 2 Mbit/s tributary ports of specific 2 Mbit/s Tributary variants, refer to Table 17-2 ‘Features: 2 Mbit/s Tributary units’ on page 17-2 The PMPs and the performance counts they accumulate are listed in Table 11-1. Table 11-1 Performance monitoring points (PMPs) and error counts PMP

Description

RS

Regenerator Section

RS-OOF

Regenerator Section Out Of Frame

MS

ES

SES

BBE

UAS

OOF

PJE

Yes

Yes

Yes

Yes

-

-

-

-

-

-

Yes

-

Multiplexer Section

Yes

Yes

Yes

Yes

-

-

HP

High-order Path

Yes

Yes

Yes

Yes

-

-

HP-FE

High-order Path Far End

Yes

Yes

Yes

Yes

-

-

AU-PJE

Administrative Pointer Justification Events

-

-

-

-

-

Yes

LP

Low-order Path

Yes

Yes

Yes

Yes

-

-

LP-FE

Low-order Path Far End

Yes

Yes

Yes

Yes

-

-

TU-PJE

Tributary Unit Pointer Justification Events

-

-

-

-

-

Yes

PPI-CV

PDH Physical Interface Code Violations

Yes

Yes

Yes

Yes

-

-

PPI-CRC

PDH Physical Interface Cyclic Redundancy Check

Yes

Yes

Yes

Yes

-

-

11

Nortel TN-1X System Description

11-4 Performance monitoring

Performance anomalies and defects The basis for determining performance anomalies and defects are detailed in Table 11-2. Table 11-2 PMP anomalies and defects PMP

Definition

Anomalies

Defects

RS

B1, BIP-8

B1 Bit Errors

RS-LOS RS-LOF

RS-OOF

A1, A2

MS

B2, BIP-24

B2 Bit Errors

All RS defects MS-AIS MS-EXC

HP

B3, BIP-8

B3 Bit/Block Errors (see Note 1)

All RS defects All MS defects AU-AIS HP-LOM AU-LOP INT-AU-AIS INT-AU-LOP

HP-FE

G1, REI

G1 Block Errors

HP-RDI

AU-PJE (see Note 2)

H1, H2 AU Pointer

LP (VC-12)

V5 Bits 1, 2 BIP-2

V5 Bit/Block Errors (see Note 3)

All RS defects All MS defects All HP defects TU-AIS TU-LOP

LP (VC-3)

B3, BIP-8

B3 Bit/Block Errors

All RS defects All MS defects All HP defects TU-AIS TU-LOP

LP-FE (VC-12)

V5 Bit 3, REI

V5 Block Error

HP-RDI LP-RDI

LP-FE (VC-3)

G1, REI

G1 Block Error

HP-RDI LP-RDI

TU-PJE (see Note 3)

V1, V2 TU Pointer

RS-LOF

—continued—

323-1061-100 Release 9 Standard

Performance monitoring 11-5 Table 11-2 PMP anomalies and defects (continued) PMP

Definition

Anomalies

Defects

PPI-CV (see Note 4)

HDB3 Code Violations (2 Mbit/s and 34 Mbit/s) B3ZS Code Violations (45 Mbit/s)

HDB3 CV B3ZS CV

PPI-LOS PPI-AIS

PPI-CRC

HDB3 Code Violations (2 Mbit/s)

HDB3 CV

PPI-LOS PPI_EXC PPI-AIS PPI_LOF PPI_LOM

Note 1: Note 2: Note 3: Note 4:

Block error counts are not available on Payload Manager 25U PJ00 750 GXF. AU-PJE counts are not available on Payload Manager 25U PJ00 750 GXF or STM-1 Tributary Units 25U JU00 750 GVA/GVB or 25U TM00 750 HWE. Block error or TU-PJE counts are not available on 2 Mbit/s Tributary Units 25U JU00 750 GXG/GXR. 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: • Twenty-four hour (24H) monitoring period. Performance monitoring results can be calculated for any twenty four hour period. The starting hour for such a period can be configured by the user, though the default start time is midnight. •

Fifteen minute (15M) monitoring period. Performance monitoring results are automatically calculated for each fifteen minute period of the day. The start and end times for 15M 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 15M and 24H monitoring periods can be terminated prematurely. In this instance (like scheduled termination), performance results are stored as logs (see Performance logs, below), totals are reset, and a new monitoring period begins immediately. This new period, however, will end at the time when the terminated period was scheduled to end. 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 Nortel TN-1X System Description

11

11-6 Performance monitoring

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 over twenty two minutes.

Performance logs Performance logs store the results of individual monitoring periods in which monitoring is active. These logs are numbered from ‘1’, with the latest logs having the highest log numbers (entering ‘-1’ as the log number will display the latest log). The number of performance logs that the TN-1X can store is variable, as it depends upon the number of PMPs that are enabled. A minimum of sixteen 15 minute performance logs can be stored. This is equivalent to 4 hours, assuming no premature terminations are performed. A maximum of two 24 hour logs can be stored. 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. 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.

Quality of service violation alarms Quality Of Service Violation (QOSV) alarms are raised on a PMP basis 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. 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. end of chapter

323-1061-100 Release 9 Standard

12-1

Diagnostics

12-

Loopbacks Various loopback facilities are provided for maintenance and test purposes. For the Nortel Networks TN-1X, the following loopbacks (see Figure 12-1) are provided. CAUTION Traffic disruption

Loopback operation may disrupt traffic, and on occasions the comms/management network may be severely disrupted. The loopbacks can be set via the user interface. Note: An ‘NE-Loopback_Alarm’ is raised whenever one or more loopbacks are enabled. The alarm report will not indicate which port the loopback is on. Use the loopback view command to identify active loopbacks. This alarm clears once all loopbacks have been disabled.

12 Nortel TN-1X System Description

12-2 Diagnostics Figure 12-1 Position of loopbacks

STM-1 Signal

Aggr, Tx

Key: Remote

Aggr, Rx

STM-1 Aggregate Unit

Local

Payload Manager

Mux/Demux Rx

Tx

STM-1 Signal

STM-1 Tributary Unit

34 Mbit/s Port

34/45 Mbit/s Port

2 Mbit/s Ports

34368 kbit/s Signal

34368 kbit/s or 44736 kbit/s Signal

2048 kbit/s Signals

34 Mbit/s Tributary Unit (16x2)

34/45 Mbit/s Tributary Unit (VC-3)

2 Mbit/s Tributary Unit

2 Mbit/s Tributary Unit Remote loopbacks When enabled, tributary input data (after the line interface but prior to HDB3 decoding) is routed to the tributary output (after the HDB3 coding but prior to the line interface). The tributary input data is still processed by the rest of the unit unless the ‘Local’ loopback is enabled. Note: Selecting the ‘Remote’ loopback when the selected tributary has no input will cause a ‘PPI-TF’ alarm to be raised.

323-1061-100 Release 9 Standard

Diagnostics 12-3

Local loopbacks When enabled, tributary output data (after the HDB3 coding but prior to the line interface) is routed to the tributary input (after the line interface but prior to HDB3 decoding). The tributary output data is still applied to the line interface and output from the unit unless the ‘Remote’ loopback is enabled. Note 1: For each tributary, only the ‘Remote’ or the ‘Local’ loopbacks can operate at a given time. If both loopbacks are selected for a given tributary, the ‘Local’ loopback will not operate. Note 2: Do not apply a ‘Local’ loopback for a tributary selected as the active synchronisation source, otherwise the multiplexer will lose synchronisation. Note 3: When a local loopback is active on a 2 Mbit/s port, AIS is not detected on this port. 34/45 Mbit/s Tributary Unit (VC-3) Remote loopbacks When enabled, tributary input data (after the line interface but prior to line decoding) is routed to the tributary output (after the line coding but prior to the line interface). The tributary input data is still processed by the rest of the unit unless the ‘Local’ loopback is enabled. Local loopbacks When enabled, tributary output data (after the line coding but prior to the line interface) is routed to the tributary input (after the line interface but prior to line decoding). The tributary output data is still applied to the line interface and output from the unit unless the ‘Remote’ loopback is enabled. Note 1: For each tributary, only the ‘Remote’ or the ‘Local’ loopbacks can operate at a given time. If both loopbacks are selected for a given tributary, the ‘Local’ loopback will not operate. Note 2: Do not apply a ‘Local’ loopback for a tributary selected as the active synchronisation source, otherwise the multiplexer will lose synchronisation.

12 Nortel TN-1X System Description

12-4 Diagnostics

STM-1 Aggregate Unit/STM-1 Tributary Unit Remote loopbacks When enabled, the STM-1 input data (after the STM-1 interface and prior to the section overhead termination) is routed to the STM-1 output (after the section overhead insertion and prior to the STM-1 interface), the normal STM-1 output being disabled. This loopbacks the data from the receiver to the transmitter. The STM-1 input data from the receiver is still processed by the rest of the unit. Local loopbacks When enabled, the STM-1 output data (after the section overhead insertion and prior to the STM-1 interface) is routed to the STM-1 input (after the STM-1 interface and prior to the section overhead termination), the normal input from the receiver being disabled. This loopbacks the STM-1 data towards the Payload Manager. Note: For each STM-1 Aggregate Unit or STM-1 Tributary Unit, both the ‘Remote’ and ‘Local’ loopbacks should not be applied simultaneously. 34 Mbit/s Tributary Unit (16x2) Remote loopbacks When enabled, the 34 Mbit/s tributary input data (prior to demultiplexing) is routed to the 34 Mbit/s tributary output. The tributary input data is still processed by the rest of the unit unless the ‘Local’ loopback is enabled. Note 1: The 34 Mbit/s Remote loopback is enabled by selecting any of the 2 Mbit/s loop to line loopbacks for the 34 Mbit/s Tributary Unit from the user interface. Note 2: Selecting ‘Remote’ will affect all sixteen 2 Mbit/s channels. Local loopbacks When enabled, 2 Mbit/s channel data (prior to multiplexing) is routed back towards the Payload Manager. The 2 Mbit/s channel data is still applied to the multiplexer and output from the unit unless the ‘Remote’ loopback is enabled. Loopback alarm An ‘NE-Loopback_Alarm’ is raised whenever one or more loopbacks are enabled. The alarm report will not indicate which port the loopback is on. Use the loopback view command to identify active loopbacks. This alarm clears once all loopbacks have been disabled.

323-1061-100 Release 9 Standard

Diagnostics 12-5

Engineering Order Wire operation The EOW system uses a calling feature which uses the format ‘n n #’, where n is a digit between 0 and 9 and # is the dial termination character. The two ‘n’ digits provide a unique two-digit site-identification code which is set via a DIL switch on the EOW Unit. This code is used to match against the incoming DTMF digit sequence. Selective calling of an individual site is made by taking the handset off-hook, waiting for a dialling tone and dialling the site-identification code followed by the dial termination character (that is, ‘n n #’). A group dialling and broadcast call feature is also provided by the use of the wild card character ‘*’ as follows: • • •

entering the sequence ‘* n #’ rings all sites ending with the ‘n’ digit (group call) entering the sequence ‘n * #’ rings all sites starting with the ‘n’ digit (group call) entering the sequence ‘* * #’ which will make all nodes ring (broadcast call)

The EOW Unit contains a green LED and a buzzer which indicates the status of the EOW system at that node as follows: • LED and buzzer OFF - EOW channel not in use • •

LED ON, buzzer OFF - EOW channel in use LED flashing, buzzer sounding - incoming EOW call Note 1: There is no time-out for the LED and buzzer, they remain active until the call is answered (handset taken off-hook) or the caller’s handset is replaced. Note 2: The LED at the node initiating an EOW call is not illuminated, this indicates that it is the node which configured the system.

If a path section is invalid (out of alignment), the communication path is disconnected. If working in a protected configuration (protected terminal or ring) and the communication path is broken, EOW communication is still possible to all multiplexers but it may be necessary to re-initialise the call (that is, there is no automatic switching to protect to a call). Note: If the communication path is re-established after a call has been re-initiated, it is possible that a ‘howl’ will be heard in the handset earpiece. If this occurs, the call must be re-initiated. end of chapter

12 Nortel TN-1X System Description

13 13-1

Construction

13-

This section describes the mechanical construction of the Nortel Networks TN-1X and TN-1X/S subracks.

TN-1X subrack variants There are two variants of the TN-1X backplane: • •

25G MU00 750 GWV (PCS Level 5). This is made from aluminium, and is shown in Figure 13-1. 25G MU00 750 GWV (PCS Level 6). This is made from steel, and is shown in Figure 13-2.

Figure 13-1 TN-1X unequipped subrack (25GMU00750GWV PCS Level 5)

Honeycomb EMC Shielding

Plug-in Unit Guides

Fibre Routing Tray

Cable Access

Local Craft Access Panel

Station Interface Area

Cover Slide/Tilt Mechanism Backplane

Nortel TN-1X System Description

13-2 Construction Figure 13-2 TN-1X unequipped subrack (25GMU00750GWV PCS Level 6)

EMC Shielding

Plug-in Unit Guides

Fibre Routing Tray

Cable Access

Local Craft Access Panel

Station Interface Area Backplane

323-1061-100 Release 9 Standard

Construction 13-3

13

TN-1X/S subrack variants There are two variants of the TN-1X backplane: • 25G MU00 750 HHX (PCS Level 6). This is made from aluminium, and is shown in Figure 13-3). •

25G MU00 750 HHX (PCS Level 7). This is made from steel, and is shown in Figure 13-4).

Figure 13-3 TN-1X/S unequipped subrack (25G MU00 750 HHX PCS Level 6)

Honeycomb EMC Shielding

Backplane

Plug-in Unit Area

Station Interface Area

Nortel TN-1X System Description

13-4 Construction Figure 13-4 TN-1X/S unequipped subrack (25G MU00 750 HHX PCS Level 7)

EMC Shielding

Backplane

Plug-in Unit Area

Station Interface Area

Subrack Design In the TN-1X and TN-1X/S subrack designs, emphasis is placed upon compactness, accessibility, and ease of installation and maintenance. The basic plug-in unit is a printed circuit board assembly with three integral connectors at the rear edge which mate with those mounted on a subrack backplane. The traditional horizontal subrack assembly, with vertically mounted plug-in units, is used as it provides efficient ventilation by natural convection. The subrack is primarily intended for mounting in racks to draft ETSI standard pr ETS 300-119 part 3. Mounting kits are also available for mounting in BT Type 91, BT Type 92, and BT TEP 1E racks. The lower sections of the side plates are cut away to allow cable access. Flanges are fastened to the side plates which have captive screws for mounting the subrack to the rack. Front mounted flanges are standard for mounting to ETSI racks. Provision is made in the side plates for the attachment of a spigot to support the subrack during installation in certain rack types. The backplane is mounted on the rear rail and side plates.

323-1061-100 Release 9 Standard

Construction 13-5

13

Subrack backplane The subrack backplane is a one piece multilayer printed circuit board. The upper section has the plug-in unit connectors and the lower section the connectors for the Interface Modules. Figure 13-5 shows the position of the plug-in unit connectors in the upper plug-in unit area of the TN-1X subrack backplane. Figure 13-6 shows the position of the Interface Module connectors in the lower station interface area of the backplane. Figure 13-7 shows the position of the plug-in unit connectors and Interface Module connectors on the TN-1X/S subrack backplane. SK6 and SK7 are integrated circuit sockets which mount the integrated circuits (IC1 and IC2) that identify the Ethernet address. Backplane connectors The plug-in unit/backplane connections are made via DIN 41612 (IEC 603-2) type connectors. All positions have upper (A) and lower (C) connectors for traffic, alarm, and control signals. The middle (B) connector is the power supply connector. All upper and lower connectors, except the two Power Units, are plugs on the backplane and sockets on the plug-in units. The Power Unit connectors are sockets on the backplane and plugs on the plug-in units (for safety reasons). All middle connectors are plugs on the backplane and sockets on the plug-in units. The middle power supply connectors have early earth extended pins. The upper and lower connectors are fitted with key pegs which prevent a unit being inserted into the wrong backplane position. The Interface Module/backplane connections are made via DIN 41612 (IEC 603-2) type connectors. On the TN-1X subrack, all positions have upper (D) connector. Subrack slot positions 40 and 80 also have lower (E) connectors. On the TN-1X/S subrack, two backplane connectors are mounted horizontally for each Interface Module, each SIM having two connectors and each TIM having a single connector (the extra connector on the backplane is provided for possible future functionality). Backplane links The backplane contains four strapping pins, P1 to P4 (see Figure 13-6 and Figure 13-7). These pins should be left unstrapped.

Nortel TN-1X System Description

PLA6

PLB6

PLC6

PLA1

PLB1

323-1061-100 Release 9 Standard

PLC1

PLC11

PLB11

PLA11

PLC16

PLB16

PLA16

PLC21

PLB21

PLA21

PLC26

PLB26

PLA26

PLC34

PLB34

PLA34

PLC42

PLB42

PLA42

PLC47

PLB47

PLA47

PLC52

PLB52

PLA52

PLC57

PLB57

PLA57

SKC62

PLB62

SKA62

SK6

IC1

ADDRESS

ETHERNET

SK7

IC2

SKC71

PLB71

SKA71

PLC80

PLB80

PLA80

13-6 Construction

Figure 13-5 TN-1X subrack backplane - plug-in unit area

Construction 13-7

13

P4

P3

P2

P1

SKE80 SKE40

SKD1

SKD10

SKD15

SKD25

SKD30

SKD35

SKD40

SKD45

SKD50

SKD55

SKD65

SKD70

SKD80

Figure 13-6 TN-1X subrack backplane - station interface area

Nortel TN-1X System Description

323-1061-100 Release 9 Standard

PLB6

PLC6

PLB1

PLC1

SKG1

SKE1

PLA6

PLA1

PLC11

PLB11

PLA11

PLC16

PLB16

PLA16

PLC21

PLB21

PLA21

PLC26

PLB26

PLA26

SKF42

SKD42

PLC34

PLB34

PLA34

PLC42

PLB42

PLA42

PLC47

PLB47

PLA47

PLC52

PLB52

PLA52

SKF56

SKD56

PLC57

PLB57

PLA57

SKC62

PLB62

SKA62

SK6

IC1

ADDRESS

ETHERNET

SK7

IC2

SKF78

PLD78

SKC71

PLB71

SKA71

P4

P3

P2

P1

PLC80

PLB80

PLA80

13-8 Construction

Figure 13-7 TN-1X/S subrack backplane

Construction 13-9

13

Plug-in units All plug-in units, irrespective of size, have an injection moulded face plate metalised on the rear face, and locking upper and lower levers for insertion/ extraction from the subrack. To maintain Electro-Magnetic Compatibility (EMC) protection, the front panels are fitted with spring fingers so that they form a continuous earth plane. Spare positions must be fitted with blank panels. For identification purposes each plug-in unit front panel is marked with its abbreviated name, Nortel Networks code and bar code. All units make contact with the subrack backplane via three connectors; a power connector in between upper and lower signal connectors. All external connections are made via Interface Modules in the SIA of the subrack, except those carrying the optical signals which connect directly to the front of the appropriate optical unit.

Interface modules The Interface Modules are reduced size cards that provide the external connections. The Interface Modules fit into the lower Station Interface Area (SIA) of the subrack, different types of Interface Modules are available to cater for different customer connector requirements. The Interface Modules have an aluminium extrusion face plate, upper and lower levers for insertion/extraction from the subrack, and a single captive central locking screw. To maintain EMC protection, the front panels are fitted with spring fingers so that they form a continuous earth plane. Spare positions must be fitted with blank panels. For identification purposes each Interface Module front panel is marked with its name, Nortel Networks code and product change status level. All units make contact with the subrack backplane via one or two connectors. External connector interfaces are mounted on the front panels and are selected to meets customer applications. The TN-1X 25GMU00750GWV PCS Level 5 and PCS Level 6 subracks use different mechanisms for covering the Interface Modules: •

The PCS Level 5 subrack uses a moulded cover (see Figure 13-8) which is mounted on a slide and tilt mechanism. The cover contains two locking screws and two latches.

•

The PCS Level 6 subrack uses a moulded cover (see Figure 13-9) which is clip mounted.

Nortel TN-1X System Description

13-10 Construction Figure 13-8 Station Interface Area cover for 25GMU00750GWV PCS Level 5

Latch (closed position)

To Open

Lock Position

323-1061-100 Release 9 Standard

To Open

Locking screw (lock position)

Lock Position

Construction 13-11 Figure 13-9 Station Interface Area cover for 25GMU00750GWV PCS Level 6 Back view of Station Interface Area cover

Magnets

Clips

Front view of Station Interface Area cover mounted in rack

Handles

EOW handset If the EOW facility is used at a TN-1X, a mounting bracket is fitted to the underside of the LCAP (see Figure 13-10) for the EOW handset. This holds the EOW handset when not is use. When the EOW is required, the EOW handset is removed from the bracket and plugged into the appropriate connector in the LCAP. For the TN-1X/S, there is no convenient position for mounting an EOW handset. If the EOW facility is required, a DTMF handset can be plugged into the connector on the EOW/CATT connector panel.

Nortel TN-1X System Description

13

13-12 Construction Figure 13-10 EOW handset - TN-1X mounting position

Fibre Tray LCAP

EOW Handset

Service Interface Area

Electro-Magnetic Compatibility protection Electro-Magnetic Compatibility (EMC) protection is provided at subrack level. Nickel loaded solid silicone gaskets are used at critical openings, for example between the backplane and subrack rails at subrack level. The TN-1X PCS Level 5 and TN-1X/S PCS Level 6 subracks are made from aluminium, and use honeycomb EMC shielding which also provides ventilation. The TN-1X PCS Level 6 and TN-1X/S PCS Level 7 subracks are made from steel, and have a grid of punched ventilation holes which provides EMC shielding.

Electro Static Discharge protection Electro Static Discharge (ESD) protection is achieved by the provision of low resistance earth paths between the rack parts, subrack parts, and plug-in unit front panels to ensure any local discharge is conducted away to the installation earth. Discharge to the front face of plug-in units is prevented by use of non-conductive material on exposed faces. An ESD bonding point for operator use is provided on the Local Craft Access Panel at the front of the TN-1X subrack. The racks may also be fitted with an ESD bonding points for operator use.

323-1061-100 Release 9 Standard

Construction 13-13

13

Earthing arrangements The rack is normally fitted with a common earth point at the top in the form of a copper bus bar or single fixing. The earth connection is distributed to the subracks either by means of individual wires in the form of twisted pairs (earth and d.c. power supply) or by a vertical copper bus bar with a short link wire to each subrack position on the right hand side of the rack.

Unused subrack positions In order to maintain EMC protection, all unused plug-in unit and Interface Module positions must be fitted with blank front panels. Codes for the relevant blank front panels are shown in Table 13-1. Table 13-1 Blank front panels Card

Blank front panel

Payload Manager 2 Mbit/s Tributary

1" Dummy Panel, 25R BN00 021 AAB

STM-1 Tributary Unit STM-1 Aggregate Unit STM-4 Aggregate Unit

1.6" Dummy Panel, 25R BN00 021 AAC

Power Unit

1.8" Dummy Panel, 25R BN00 021 AAD

1" Interface Module

1" Dummy Panel, 25R BN00 021 AAA

end of chapter

Nortel TN-1X System Description

14-1

External interfaces

14-

Introduction External connections to the TN-1X subrack are made via the Local Craft Access Panel (frequently used connections) or Interface Modules in the Station Interface Area (SIA) of the subrack. External connections to the TN-1X/S subrack are made via the Connector Panels, which are in turn connected to the backplane via Interface Modules in the SIA of the subrack. The following sections provide details of the available LCAPs, Interface Modules, and Connector Panels. WARNING Take care when working with cables near the top of the Station Interface Area, so that your hands do not scrape on the honeycomb screen. Use of a suitable cable extraction/insertion tool is recommended.

Nortel TN-1X System Description

14

14-2 External interfaces

Local Craft Access Panel 75 Ω The Local Craft Access Panel 75 Ω provides a 25-way ‘D’ type connector for the local terminal, two 75 Ω monitoring points (for future use), and a EOW telephone socket for the TN-1X. The connectors are mounted behind a hinged cover on the left-hand side of the panel (see Figure 14-1). Figure 14-1 Local Craft Access Panel 75 Ω - front view For future use

1

2 TRAFFIC MONITOR

CATT

EOW

Behind hinged cover

RECEIVE ATT

RECEIVE ATT

ALARM

ALARM

ALM ACK

ESD

ESD

ALM ACK

The local terminal port is a female 25-way ‘D’ type connector. The pin-out of the connector is detailed in Table 14-1. Table 14-1 Local Craft Access Panel 75 Ω - local terminal connector pin-out Pin

Function

Pin

Function

1 2 3 4 5 6 7 8 9 10 11 12 13

Frame ground (0 V) Transmit data (TXD) Receive data (RXD) Ready to send (RTS) Clear to send (CTS) Data set ready (DSR) Signal ground (0 V) No connection +5 V (not used) Detect terminal No connection No connection No connection

14 15 16 17 18 19 20 21 22 23 24 25

No connection No connection No connection No connection No connection No connection Data transmit ready (DTR) No connection No connection No connection No connection No connection

323-1061-100 Release 9 Standard

1 14 15 16 17 18 19 20 21 22 23 24 25

2 3 4 5 6 7 8 9 10 11 12 13

External interfaces 14-3

The subrack alarm facilities are provided by a receive attention push-button switch (‘RECEIVE ATT’), and two LEDs (red ‘ALARM’, green ‘ALM ACK’). These facilities are controlled by the Subrack Controller. Mating connectors/cabling The local terminal port (CATT) is an RS232C interface using a 25-way ‘D’ Type socket. The cable must be terminated at the TN-1X end with plug type 32C CN36 100 AKU and 4.40 UNC screws. The cable and connector to the local terminal will depend on which type of local terminal device is used and is therefore customer specific. Cableform 25Y CN00 748 AAA provides suitable cabling and connectors when using a local terminal fitted with a 9-way ‘D’ type connector. A CW1311 type phone jack socket (EOW) is provided for connection of the DTMF handset for Engineering Order Wire operation. Two type 43 female coaxial connectors are provided for future traffic monitoring facilities. The Local Craft Access Panel 75 Ω interfaces to the Flexible Access Module using a cable with 25-way ‘D’ type connectors (cableform 25Y CN00 021 AAA, which is part of the LCAP assembly). The connector body and cable shield are d.c. coupled to the mechanical earth.

Nortel TN-1X System Description

14

14-4 External interfaces

75 Ω Traffic Access Module (TN-1X) The 75 Ω Traffic Access Module (TN-1X), see Figure 14-2, provides sixteen type 43 coaxial connectors for eight 2048 kbit/s tributary ports (a port being a transmit/receive pair) for the TN-1X. Figure 14-2 75 Ω Traffic Access Module (TN-1X) - front and side views

3 LK1

1

25UJJ00750GVZ

LK2

LK3

AC

2 DC

AC Coupled 3

AC

2 1 LK4

DC

DC Coupled

RX LK5

Link LK6

2 3 4 5 6 7 8 9 10

LK7

75 Ω TRAFFIC ACCESS MODULE

1

LK8

TX

323-1061-100 Release 9 Standard

External interfaces 14-5

The upper eight connectors (RX) provide the receive (input) connections. Links LK1 to LK8 on the module (see Figure 14-2) allow the coaxial cable shield of each input to be a.c. coupled (pins 2-3 linked) or d.c. coupled (pins 1-2 linked) to the electrical earth. Figure 14-3 shows the relationship between links and the 2048 kbit/s input ports. The lower eight connectors (TX) provide the transmit (output) connections. The coaxial cable shield of each output connector is d.c. coupled to the electrical earth. The 75 Ω Traffic Access Module (TN-1X) fits into Interface Module positions T2, T3, T5, T6, T10, T11, T13, and T14 (backplane slot positions 10, 15, 25, 30, 50, 55, 65, and 70) in the SIA of the subrack. Two modules are required to provide all the necessary connectors for a 2 Mbit/s Tributary Unit. The relationship between the 2048 kbit/s ports, the connectors on the 75 Ω Traffic Access Module (TN-1X), and the 2 Mbit/s Tributary Units is shown in Figure 14-3. Note 1: The input earth links are applicable to the upper receive connectors only. Note 2: A 75 Ω Tributary Unit must be fitted in the corresponding plug-in unit position if 75 Ω Traffic Access Modules are used (for example, a 75 Ω Tributary Unit must be fitted in plug-in unit position S2 if 75 Ω Traffic Access Modules (TN-1X) are fitted in position T2 and T3). Figure 14-3 75 Ω Traffic Access Module (TN-1X) - 2 Mbit/s port allocation S2 (6)

Plug-in unit position Interface Module position

T2 (10)

S4 (16) T3 (15)

T5 (25)

S9 (47) T6 (30)

T10 (50)

S11 (57) T11 (55)

T13 (65)

T14 (70)

Input earth link

Port 8

Port 16

Port 8

Port 16

Port 8

Port 16

Port 8

Port 16

LK1

Port 7

Port 15

Port 7

Port 15

Port 7

Port 15

Port 7

Port 15

LK2

Port 6

Port 14

Port 6

Port 14

Port 6

Port 14

Port 6

Port 14

LK3

Port 5

Port 13

Port 5

Port 13

Port 5

Port 13

Port 5

Port 13

LK4

Port 4

Port 12

Port 4

Port 12

Port 4

Port 12

Port 4

Port 12

LK5

Port 3

Port 11

Port 3

Port 11

Port 3

Port 11

Port 3

Port 11

LK6

Port 2

Port 10

Port 2

Port 10

Port 2

Port 10

Port 2

Port 10

LK7

Port 1

Port 9

Port 1

Port 9

Port 1

Port 9

Port 1

Port 9

LK8

(N) indicates subrack backplane slot position Ports are identified by the slot number and the instance, for example, S4-7 indicates port 7 for unit in slot S4

Mating connectors/cabling The 75 Ω 2048 kbit/s tributary interfaces use coaxial cables terminated with Type 43 coaxial sockets, the mating connector is coded 32C CN15 001 AAL. The preferred coaxial cable type is 3002, however, type 2002 can also be used. Nortel TN-1X System Description

14

14-6 External interfaces

75 Ω Traffic Access Module (1:N Protection) (TN-1X) The 75 Ω Traffic Access Module (1:N Protection) (TN-1X), see Figure 14-2, provides sixteen type 43 coaxial connectors for eight 2048 kbit/s tributary ports (a port being a transmit/receive pair) for the TN-1X and is used when 1:N protection of the 2 Mbit/s Tributary Units is required. Figure 14-4 75 Ω Traffic Access Module (1:N Protection) (TN-1X) - front and side views

LK1

NTKD14AA

LK2

1 2 3 AC Coupled

LK3

LK4

1 2 3 DC Coupled

RX LK5

2 3 4 5 6 7 8 9 10

LK6

LK7

2M 75 Ω TAM (1:N PROTECTION)

1

LK8

TX

323-1061-100 Release 9 Standard

Link

External interfaces 14-7

The upper eight connectors (RX) provide the receive (input) connections. Links LK1 to LK8 on the module (see Figure 14-2) allow the coaxial cable shield of each input to be a.c. coupled (pins 2-3 linked) or d.c. coupled (pins 1-2 linked) to the electrical earth. Figure 14-3 shows the relationship between links and the 2048 kbit/s input ports. The lower eight connectors (TX) provide the transmit (output) connections. The coaxial cable shield of each output connector is d.c. coupled to the electrical earth. The 75 Ω Traffic Access Module (TN-1X) fits into Interface Module positions T2, T3, T5, T6, T10, T11, T13, and T14 (backplane slot positions 10, 15, 25, 30, 50, 55, 65, and 70) in the SIA of the subrack. Two modules are required to provide all the necessary connectors for a 2 Mbit/s Tributary Unit. The relationship between the 2048 kbit/s ports, the connectors on the 75 Ω Traffic Access Module (TN-1X), and the 2 Mbit/s Tributary Units is shown in Figure 14-3. Note 1: The input earth links are applicable to the upper receive connectors only. Note 2: A 75 Ω Tributary Unit must be fitted in the corresponding plug-in unit position if 75 Ω Traffic Access Modules are used (for example, a 75 Ω Tributary Unit must be fitted in plug-in unit position S2 if 75 Ω Traffic Access Modules (TN-1X) are fitted in position T2 and T3). Figure 14-5 75 Ω Traffic Access Module (1:N Protection) (TN-1X) - 2 Mbit/s port allocation S2 (6)

Plug-in unit position Interface Module position

T2 (10)

S4 (16) T3 (15)

T5 (25)

S9 (47) T6 (30)

T10 (50)

S11 (57) T11 (55)

T13 (65)

T14 (70)

Input earth link

Port 8

Port 16

Port 8

Port 16

Port 8

Port 16

Port 8

Port 16

LK1

Port 7

Port 15

Port 7

Port 15

Port 7

Port 15

Port 7

Port 15

LK2

Port 6

Port 14

Port 6

Port 14

Port 6

Port 14

Port 6

Port 14

LK3

Port 5

Port 13

Port 5

Port 13

Port 5

Port 13

Port 5

Port 13

LK4

Port 4

Port 12

Port 4

Port 12

Port 4

Port 12

Port 4

Port 12

LK5

Port 3

Port 11

Port 3

Port 11

Port 3

Port 11

Port 3

Port 11

LK6

Port 2

Port 10

Port 2

Port 10

Port 2

Port 10

Port 2

Port 10

LK7

Port 1

Port 9

Port 1

Port 9

Port 1

Port 9

Port 1

Port 9

LK8

(N) indicates subrack backplane slot position Po Ports are identified by the slot number and the instance, for example, S4-7 indicates port 7 for unit in slot S4.

Mating connectors/cabling The 75 Ω 2048 kbit/s tributary interfaces use coaxial cables terminated with Type 43 coaxial sockets, the mating connector is coded 32C CN15 001 AAL. The preferred coaxial cable type is 3002, however, type 2002 can also be used. Nortel TN-1X System Description

14

14-8 External interfaces

75 Ω Traffic Access Module (TN-1X/S) The 75 Ω Traffic Access Module (TN-1X/S), see Figure 14-6, provides sixteen type 43 coaxial connectors for eight 2048 kbit/s tributary ports (a port being a transmit/receive pair) for the TN-1X/S. Figure 14-6 75 Ω Traffic Access Module (TN-1X/S) - front and side views

3 2

AC

1

DC

LK2

AC Coupled

LK3

3 2

AC

1

DC

LK4

RX

75 Ω TRAFFIC ACCESS MODULE

LK1

DC Coupled

LK5

Link LK6

LK7

1 2 3 4 5 6 7 8 9 10

LK8

TX

25UJJ00750HHZ

323-1061-100 Release 9 Standard

External interfaces 14-9

The left-hand eight connectors (RX) provide the receive (input) connections. Links LK1 to LK8 on the module (see Figure 14-6) allow the coaxial cable shield of each input to be a.c. coupled (pins 2-3 linked) or d.c. coupled (pins 1-2 linked) to the electrical earth. Figure 14-7 shows the relationship between links and the 2048 kbit/s input ports. The right-hand eight connectors (TX) provide the transmit (output) connections. The coaxial cable shield of each output connector is d.c. coupled to the electrical earth. The 75 Ω Traffic Access Module (TN-1X/S) fits into Interface Module positions M1A (upper) & M1B (lower) in the SIA of the subrack. Two modules are required to provide all the necessary connectors for a 2 Mbit/s Tributary Unit. The relationship between the 2048 kbit/s ports, the connectors on the 75 Ω Traffic Access Module (TN-1X/S), and the 2 Mbit/s Tributary Unit is shown in Figure 14-7. Note 1: The input earth links are applicable to the receive connectors only. Note 2: A 75 Ω Tributary Unit must be fitted in the corresponding plug-in unit position (S2) if 75 Ω Traffic Access Modules (TN-1X/S) are used. Figure 14-7 75 Ω Traffic Access Module (TN-1X/S) - 2 Mbit/s port allocation

TIM M1A (Upper) TIM M1B (Lower) Input earth link

Port 8

Port 7

Port 6

Port 5

Port 4

Port 3

Port 2

Port 1

Port 16

Port 15

Port 14

Port 13

Port 12

Port 11

Port 10

Port 9

LK1

LK2

LK3

LK4

LK5

LK6

LK7

LK8

Plug-in unit position S2 (subrack backplane slot position 6)

Mating connectors/cabling The module is connected to 75 Ω connector panel using thirty-two RG179 coaxial cables (25Y CN00 750 AAN). These cables are terminated with Type 43 connectors for connection to the traffic interface module and SMB connectors for connection to the connector panel.

Nortel TN-1X System Description

14

14-10 External interfaces

120 Ω Traffic Access Module (TN-1X) The 120 Ω Traffic Access Module (TN-1X), see Figure 14-8, provides two 25-way ‘D’ type connectors for eight 2048 kbit/s tributary ports (a port being a transmit/receive pair) for the TN-1X and is used when 1:N protection of the 2 Mbit/s Tributary Units is required. Figure 14-8 120 Ω Traffic Access Module (TN-1X) - front and side views

LK1

LK1

1

6

DC Coupled 25UJJ00750HLV

LK1

Pin 1 6

AC Coupled Link

1

2 3 4 5 6 7 8 9 10

INPUT

2M 120 Ω TAM (1:N PROTECTION)

1

Pin 1 OUTPUT

323-1061-100 Release 9 Standard

External interfaces 14-11

The upper male connector (INPUT) provides the receive (input) connections. Link LK1 (see Figure 14-8) allows the connector body and cable screen be d.c. coupled to the mechanical earth (pins 1-6 and 2-5 linked), a.c. coupled to the mechanical earth (pins 2-5 and 3-4 linked), or left isolated from the mechanical earth (no links fitted). The lower female connector (OUTPUT) provides the transmit (output) connections. The connector body and the cable shield are d.c. coupled to the mechanical earth. The 120 Ω Traffic Access Module (TN-1X) fits into Interface Module positions T2, T3, T5, T6, T10, T11, T13, and T14 (backplane slot positions 10, 15, 25, 30, 50, 55, 65, and 70) in the SIA of the subrack. Two modules are required to provide all the necessary connectors for a 2 Mbit/s Tributary Unit. The relationship between the 2048 kbit/s ports, the connectors on the 120 Ω Traffic Access Module (TN-1X), and the 2 Mbit/s Tributary Units is shown in Figure 14-9. Figure 14-9 120 Ω Traffic Access Module (TN-1X) - 2 Mbit/s port allocation

Sig 7b

14 15

Sig 8b

16

Sig 6b

17 19

Sig 4b

20 22

Sig 3b

23 25

5

Sig 6a

6

Sig 5a

8

Sig 4a

9

Sig 1a

11

Sig 3a

12

Signal Pair

Sig 2a

Pins 4, 7, 10, 13, 15, 18, 21, and 24 not used.

13 S2 (6)

Plug-in unit position Interface Module position

Sig 8a

10

24 Sig 2b

Sig 7a

3

7

21 Sig 1b

Cable Screen

2 4

18 Sig 5b

1

S4 (16)

T2 (10)

T3 (15)

Sig 1

Port 1

Port 9

Sig 2

Port 2

Port 10

Sig 3

Port 3

Sig 4

T5 (25)

S9 (47)

S11 (57)

T6 (30)

T10 (50)

T11 (55)

T13 (65)

T14 (70)

Port 1

Port 9

Port 1

Port 9

Port 1

Port 9

Port 2

Port 10

Port 2

Port 10

Port 2

Port 10

Port 11

Port 3

Port 11

Port 3

Port 11

Port 3

Port 11

Port 4

Port 12

Port 4

Port 12

Port 4

Port 12

Port 4

Port 12

Sig 5

Port 5

Port 13

Port 5

Port 13

Port 5

Port 13

Port 5

Port 13

Sig 6

Port 6

Port 14

Port 6

Port 14

Port 6

Port 14

Port 6

Port 14

Sig 7

Port 7

Port 15

Port 7

Port 15

Port 7

Port 15

Port 7

Port 15

Sig 8 Port 8 Port 16 Port 8 Port 16 Port 8 (N) indicates subrack backplane slot position Ports are identified by the slot number and the instance, for example, S4-7 indicates port 7 for unit in slot S4.

Port 16

Port 8

Port 16

Nortel TN-1X System Description

14

14-12 External interfaces

Note: A 120 Ω Tributary Unit must be fitted in the corresponding plug-in unit position if 120 Ω Traffic Access Modules (TN-1X) are used (for example, a 120 Ω Tributary Unit must be fitted in plug-in unit position S2 if 120 Ω Traffic Access Modules (TN-1X) are fitted in position T2 and T3). Mating connectors/cabling The module is connected to 120 Ω connector panel using cable 25Y CN00 750 AAV (2 of) and cable 25Y CN00 750 AAZ (2 of).

323-1061-100 Release 9 Standard

External interfaces 14-13

120 Ω Traffic Access Module (1:N Protection) (TN-1X) The 120 Ω Traffic Access Module (1:N Protection) (TN-1X), see Figure 14-8, provides two 25-way ‘D’ type connectors for eight 2048 kbit/s tributary ports (a port being a transmit/receive pair) for the TN-1X and is used when 1:N protection of the 2 Mbit/s Tributary Units is required. Figure 14-10 120 Ω Traffic Access Module (1:N Protection) (TN-1X) - front and side views

NTKD15AA

Pin 1

120 Ω TRAFFIC ACCESS MODULE

1

2 3 4 5 6 7 8 9 10

INPUT

Pin 1 OUTPUT

Nortel TN-1X System Description

14

14-14 External interfaces

The upper male connector (INPUT) provides the receive (input) connections. The connector body and cable screen be d.c. coupled to the mechanical earth. Note: Link LK1 is not used. The lower female connector (OUTPUT) provides the transmit (output) connections. The connector body and the cable shield are d.c. coupled to the mechanical earth. The 120 Ω Traffic Access Module (TN-1X) fits into Interface Module positions T2, T3, T5, T6, T10, T11, T13, and T14 (backplane slot positions 10, 15, 25, 30, 50, 55, 65, and 70) in the SIA of the subrack. Two modules are required to provide all the necessary connectors for a 2 Mbit/s Tributary Unit. The relationship between the 2048 kbit/s ports, the connectors on the 120 Ω Traffic Access Module (TN-1X), and the 2 Mbit/s Tributary Units is shown in Figure 14-9. Figure 14-11 120 Ω Traffic Access Module (1:N Protection) (TN-1X) - 2 Mbit/s port allocation

Sig 7b

14 15

Sig 8b

16

Sig 6b

17 19

Sig 4b

20 22

Sig 3b

23

Sig 8a

5

Sig 6a

6

Sig 5a

8

Sig 4a

9

Sig 1a

10

24 Sig 2b

Sig 7a

3

25

11

Sig 3a

12

Sig 2a

Interface Module position

Pins 4, 7, 10, 13, 15, 18, 21, and 24 not used.

13 S2 (6)

Plug-in unit position

Signal Pair

7

21 Sig 1b

Cable Screen

2 4

18 Sig 5b

1

S4 (16) T6 (30)

T10 (50)

S11 (57)

T2 (10)

T3 (15)

Sig 1

Port 1

Port 9

Port 1

Port 9

Port 1

Port 9

Port 1

Port 9

Sig 2

Port 2

Port 10

Port 2

Port 10

Port 2

Port 10

Port 2

Port 10

Sig 3

Port 3

Port 11

Port 3

Port 11

Port 3

Port 11

Port 3

Port 11

Sig 4

Port 4

Port 12

Port 4

Port 12

Port 4

Port 12

Port 4

Port 12

Sig 5

Port 5

Port 13

Port 5

Port 13

Port 5

Port 13

Port 5

Port 13

Sig 6

Port 6

Port 14

Port 6

Port 14

Port 6

Port 14

Port 6

Port 14

Sig 7

Port 7

Port 15

Port 7

Port 15

Port 7

Port 15

Port 7

Port 15

Sig 8 Port 8 Port 16 Port 8 Port 16 Port 8 (N) indicates subrack backplane slot position Ports are identified by the slot number and the instance, for example, S4-7 indicates port 7 for unit in slot S4.

Port 16

Port 8

Port 16

323-1061-100 Release 9 Standard

T5 (25)

S9 (47) T11 (55)

T13 (65)

T14 (70)

External interfaces 14-15

Note: A 120 Ω Tributary Unit must be fitted in the corresponding plug-in unit position if 120 Ω Traffic Access Modules (TN-1X) are used (for example, a 120 Ω Tributary Unit must be fitted in plug-in unit position S2 if 120 Ω Traffic Access Modules (TN-1X) are fitted in position T2 and T3). Mating connectors/cabling The module is connected to 120 Ω connector panel using cable 25Y CN00 750 AAV (2 of) and cable 25Y CN00 750 AAZ (2 of).

Nortel TN-1X System Description

14

14-16 External interfaces

120 Ω Traffic Access Module (TN-1X/S) The 120 Ω Traffic Access Module (TN-1X/S), see Figure 14-12, provides two 25-way ‘D’ type connectors for eight 2048 kbit/s tributary ports (a port being a transmit/receive pair) for the TN-1X/S. Figure 14-12 120 Ω Traffic Access Module (TN-1X/S) - front and side views

LK1

LK1

1

6

DC Coupled LK1

25UJJ00750HJA RX 1 2 3 4 5 6 7 8 9 10

120 Ω TRAFFIC ACCESS MODULE

TX

323-1061-100 Release 9 Standard

1

6

AC Coupled Link

External interfaces 14-17

The left-hand male connector (RX) provides the receive (input) connections. Link LK1 (see Figure 14-12) allows the connector body and cable screen be a.c. coupled to the mechanical earth (pins 1-6 and 2-5 linked), d.c. coupled to the mechanical earth (pins 2-5 and 3-4 linked), or left isolated from the mechanical earth (no links fitted). The right-hand female connector (TX) provides the transmit (output) connections. The connector body and the cable shield are d.c. coupled to the mechanical earth. The 120 Ω Traffic Access Module (TN-1X/S) fits into Interface Module positions M1A & M1B in the SIA of the subrack. Two modules are required to provide all the necessary connectors for a 2 Mbit/s Tributary Unit. The relationship between the 2048 kbit/s ports, the connectors on the 120 Ω Traffic Access Module (TN-1X/S), and the 2 Mbit/s Tributary Unit is shown in Figure 14-13. Figure 14-13 120 Ω Traffic Access Module (TN-1X/S) - 2 Mbit/s port allocation

Trib. 2 13

Interface Module position

25

12

11

Trib. 3

Plug-in unit position S2 (subrack backplane slot position 6)

24

Trib. 1

10

23

22

9

Trib. 4 8

21

Trib. 5

7

6

19

20

Trib. 6 5

18

Trib. 8

4

17

16

3

Trib. 7 2

15

14

1

Drain wire

Input tributaries (male panel connector)

Trib. 7

Drain wire 1

2

3

Trib. 8

Trib. 6 4

5

6

Trib. 4

Trib. 5 7

8

9

Trib. 1

Trib. 3 10

11

12

13

Trib. 2

Output tributaries (female panel connector)

M1A (Upper)

M1B (Lower)

Sig 1

Port 1

Port 9

Sig 2

Port 2

Port 10

Sig 3

Port 3

Port 11

Sig 4

Port 4

Port 12

Sig 5

Port 5

Port 13

Sig 6

Port 6

Port 14

Sig 7

Port 7

Port 15

Sig 8

Port 8

Port 16

Pins 4, 7, 10, 13, 15, 18, 21, and 24 not used.

14

15

16

17

18

19

20

21

22

23

24

25

Signal Pair

Note: A 120 Ω Tributary Unit must be fitted in the corresponding plug-in unit position (S2) if 120 Ω Traffic Access Modules (TN-1X/S) are used.

Nortel TN-1X System Description

14

14-18 External interfaces

Mating connectors/cabling Input The left-hand 25-way male ‘D’ type connector (RX) provides the receive connections, the mating connector is coded 32C CN16 100 AJH. Output The right-hand 25-way female ‘D’ type connector (TX) provides the transmit connections, the mating connector is coded 32C CN36 100 AKU.

323-1061-100 Release 9 Standard

External interfaces 14-19

High Speed Traffic Access Module (16x2) The High Speed Traffic Access Module, see Figure 14-14, provides two type 43 coaxial connectors for a 34,368 kbit/s 75 Ω electrical tributary port (a port being a transmit/receive pair) for the 34 Mbit/s Tributary Unit (16x2). The module also provides a coaxial connector for monitoring the output signal. The module is not applicable to the TN-1X/S.

MON

TX

HIGH SPEED TRAFFIC ACCESS MODULE

1

2 3 4 5 6 7 8 9 10

25UJJ00750HTD

Figure 14-14 High Speed Traffic Access Module - front and side views

RX

Nortel TN-1X System Description

14

14-20 External interfaces

The upper connector (MON) provides a coaxial connector for monitoring the output signal. The terminated output provides a signal 20 dB lower than the interface signal (nominal pulse height +0.1 V ± 0.01 V). The middle connector (TX) provides the transmit (output) connection. The coaxial cable shield of the output connector is d.c. coupled to the electrical earth. The lower connector (RX) provides the receive (input) connection.The coaxial cable shield of the output connector is d.c. coupled to the electrical earth. The High Speed Traffic Access Module fits into Interface Module positions T3, T6, T11, T11, and T14 (backplane slot positions 15, 30, 55, and 70) in the SIA of the subrack. The allocation of modules to 34 Mbit/s Tributary Units (16x2) is as follows: Position T3 34 Mbit/s Tributary Unit (16x2) fitted to plug-in unit position S2 (backplane slot position 6). Position T6 34 Mbit/s Tributary Unit (16x2) fitted to plug-in unit position S4 (backplane slot position 16). Position T11 34 Mbit/s Tributary Unit (16x2) fitted to plug-in unit position S9 (backplane slot position 47). Position T14 34 Mbit/s Tributary Unit (16x2) fitted to plug-in unit position S11 (backplane slot position 70). Mating connectors/cabling The 34,368 kbit/s electrical tributary ports use coaxial cables terminated with Type 43 coaxial sockets, the mating connector is coded 32C CN15 001 AAE. The preferred coaxial cable type is 2003.

323-1061-100 Release 9 Standard

External interfaces 14-21

High Speed Traffic Access Module (VC-3) The 75 Ω High Speed Traffic Access Module, see Figure 14-15, provides two type 43 coaxial connectors for a 34,368 kbit/s or 44736 kbit/s 75 Ω electrical tributary port (a port being a transmit/receive pair) for the 34/45 Mbit/s Tributary Unit. The module also provides a coaxial connector for monitoring the output signal. The module is not applicable to the TN-1X/S. Figure 14-15 High Speed Traffic Access Module (VC-3) - front and side views

TX

RX

HIGH SPEED TRAFFIC ACCESS MODULE

1

2 3 4 5 6 7 8 9 10

NTKD17AA

MON

Nortel TN-1X System Description

14

14-22 External interfaces

The middle connector (TX) provides the transmit (output) connection. The coaxial cable shield of the output connector is d.c. coupled to the electrical earth. The middle connector (MON) provides a coaxial connector for monitoring the output signal. The terminated output provides a signal 20 dB lower than the interface signal (nominal pulse height +0.1 V ± 0.01 V). The lower connector (RX) provides the receive (input) connection.The coaxial cable shield of the output connector is d.c. coupled to the electrical earth. The High Speed Traffic Access Module fits into Interface Module positions T3, T6, T11, T11, and T14 (backplane slot positions 15, 30, 55, and 70) in the SIA of the subrack. The allocation of modules to 34/45 Mbit/s Tributary Units is as follows: Position T3 34/45 Mbit/s Tributary Unit fitted to plug-in unit position S2 (backplane slot position 6). Position T6 34/45 Mbit/s Tributary Unit fitted to plug-in unit position S4 (backplane slot position 16). Position T11 34/45 Mbit/s Tributary Unit fitted to plug-in unit position S9 (backplane slot position 47). Position T14 34/45 Mbit/s Tributary Unit fitted to plug-in unit position S11 (backplane slot position 70). Mating connectors/cabling The 34,368 kbit/s or 44736 kbit/s electrical tributary ports use coaxial cables terminated with Type 43 coaxial sockets, the mating connector is coded 32C CN15 001 AAE. The preferred coaxial cable type is 2003.

323-1061-100 Release 9 Standard

External interfaces 14-23

1:1 Manual Tributary Protection TAM (VC-3) The 75 Ω 1:1 Manual Tributary Protection Traffic Access Module, see Figure 14-16, provides no connectors. The module is not applicable to the TN-1X/S.

1

2 3 4 5 6 7 8 9 10

NTKD17AB

Figure 14-16 1:1 Manual Tributary Protection TAM (VC-3) - front and side views

Nortel TN-1X System Description

14

14-24 External interfaces

The High Speed Traffic Access Module fits into Interface Module positions T6 and T14 (backplane slot positions 30 and 70) in the SIA of the subrack. The allocation of modules to 34/45 Mbit/s Tributary Units is as follows: Position T6 34/45 Mbit/s Tributary Unit fitted to plug-in unit position S4 (backplane slot position 16). The 34/45 Mbit/s Tributary Unit protects a 34/45 Mbit/s Tributary Unit in plug-in unit position S2. Position T14 34/45 Mbit/s Tributary Unit fitted to plug-in unit position S11 (backplane slot position 70). The 34/45 Mbit/s Tributary Unit protects a 34/45 Mbit/s Tributary Unit in plug-in unit position S9. Mating connectors/cabling Not applicable.

323-1061-100 Release 9 Standard

External interfaces 14-25

High Speed Aggregate Module The High Speed Aggregate Module, see Figure 14-17, provides two type 43 coaxial connectors for a 155,552 kbit/s (STM-1) electrical aggregate port (a port being a transmit/receive pair). The module is not applicable to the TN-1X/S.

TX

RX

HIGH SPEED AGG MODULE

1

2 3 4 5 6 7 8 9 10

25UJJ00750GYZ

Figure 14-17 High Speed Aggregate Module - front and side views

Nortel TN-1X System Description

14

14-26 External interfaces

The upper connector (TX) provides the transmit (output) connection. The coaxial cable shield of the output connector is d.c. coupled to the electrical earth. The lower connector (RX) provides the receive (input) connection.The coaxial cable shield of the output connector is d.c. coupled to the electrical earth. The High Speed Aggregate Unit fits into Interface Module positions T7 and T9 (backplane slot positions 35 and 45) in the SIA of the subrack. The module in Interface Module position T7 provides the high speed port for the STM-1 Electrical Aggregate Unit in plug-in unit position S6 (backplane slot position 26). The module in Interface Module position T9 provides the high speed port for the STM-1 Electrical Aggregate Unit in plug-in unit position S7 (backplane slot position 34). Mating connectors/cabling The 155,520 kbit/s (STM-1) electrical aggregate ports use coaxial cables terminated with Type 43 coaxial sockets, the mating connector is coded 32C CN15 001 AAE. The preferred coaxial cable type is 2003.

323-1061-100 Release 9 Standard

External interfaces 14-27

High Speed Tributary Module The High Speed Tributary Module, see Figure 14-18, provides two type 43 coaxial connectors for a 155,552 kbit/s (STM-1) electrical tributary port (a port being a transmit/receive pair). The module is not applicable to the TN-1X/S.

TX

RX

HIGH SPEED TRIB MODULE

1

2 3 4 5 6 7 8 9 10

25UJJ00750GWY

Figure 14-18 High Speed Tributary Module - front and side views

Nortel TN-1X System Description

14

14-28 External interfaces

The upper connector (TX) provides the transmit (output) connection. The coaxial cable shield of the output connector is d.c. coupled to the electrical earth. The lower connector (RX) provides the receive (input) connection.The coaxial cable shield of the output connector is d.c. coupled to the electrical earth. The High Speed Tributary Unit fits into Interface Module positions T3, T6, T11, and T14 (backplane slot positions 10, 30, 55, and 70) in the SIA of the subrack. The allocation of modules to STM-1 Electrical Tributary Units is as follows: Position T3 STM-1 Electrical Tributary Unit fitted to plug-in unit position S2 (backplane slot position 6). Position T6 STM-1 Electrical Tributary Unit fitted to plug-in unit position S4 (backplane slot position 16). Position T11 STM-1 Electrical Tributary Unit fitted to plug-in unit position S9 (backplane slot position 47). Position T14 STM-1 Electrical Tributary Unit fitted to plug-in unit position S11 (backplane slot position 70). Mating connectors/cabling The 155,520 kbit/s (STM-1) electrical tributary ports use coaxial cables terminated with Type 43 coaxial sockets, the mating connector is coded 32C CN15 001 AAE. The preferred coaxial cable type is 2003.

323-1061-100 Release 9 Standard

External interfaces 14-29

Station Service Module The Station Service Module, see Figure 14-19, provides connectors for the rack alarm bus, the management Q3 port (LAN), and power for the TN-1X.

RACK ALARM

LAN

1

2 3 4 5 6 7 8 9 10

25UJJ00750HLV

Figure 14-19 Station Service Module - front and side views

P5 P6 P2 P4 P7 1 2

P1 P3 P8

STN SERVICE MODULE

3 4

Earth strapping pins

POWER INPUT

Nortel TN-1X System Description

14

14-30 External interfaces

The upper connector (RACK ALARM) is a male 15-way ‘D’ type which provides the connections to the rack alarm bus. The connector body and cable shield are d.c coupled to the mechanical earth. The connector clamps onto a 10-way ribbon cable. The pin-out of the connector is detailed in Table 14-2. Table 14-2 Station Service Module - rack alarm connector pin-out Pin

Function

Pin

Function

1 2 3 4 5 6 7 8

-12 V Prompt alarm Deferred alarm In Station alarm Not used 0V 0V 0V

9 10 11 12 13 14 15

Not used Receive attention Not used Fault clear Not used 0V 0V

9 10 11 12 13 14 15

1 2 3 4 5 6 7 8

The middle connector (LAN) is a female 15-way ‘D’ type which provides the Attachment Unit Interface (AUI) Ethernet connection to the network management system. The connector body and cable shield are d.c. coupled to the mechanical earth. The inner signal shields are d.c. coupled to the electrical earth. The pin-out of the connector is detailed in Table 14-3. Table 14-3 Station Service Module - LAN connector pin-out Pin

Function

Pin

Function

1 2 3 4 5 6 7 8

Control In Circuit Shield (0V) Control In Circuit A (CI-A) Data Out Circuit A (DO-A) Data In Circuit Shield (0V) Data In Circuit A (DI-A) Voltage Common (VC) Control Out Circuit A (CO-A) Control Out Circuit Shield (0V)

9 10 11 12 13 14 15 Shell

Control In Circuit B (CI-A) Data Out Circuit B (DO-B) Data Out Circuit Shield (0V) Data In Circuit B (DI-B) Voltage Plus (VP) Voltage Shield (VS) Control Out Circuit B (CO-B) Protective Ground (PG)

15 14 13 12 11 10 9

8 7 6 5 4 3 2 1

The lower connector (POWER) is a 4-way BIC BT Type 237 connector which provides the connections for two input power supplies. The pin-out of the connector is detailed in Table 14-4. Table 14-4 Station Service Module - power connector pin-out Pin

Function

1 2 3 4

-48 V (fuse 1) 0 V (fuse 1) 0 V (fuse 2) -48 V (fuse 2)

323-1061-100 Release 9 Standard

External interfaces 14-31

The module contains eight strapping pins, P1 to P8 (see Figure 14-19), which allow the mechanical and two electrical signal earths to be linked. Table 14-5 details the earth strapping options. Table 14-5 Station Service Module - earth strapping options Earthing Option

Straps

For common 0 V (Fuse 1) and 0 V (Fuse 2) For common signal earth and 0 V (Fuse 1) For common signal earth and 0 V (Fuse 2) For common signal earth, 0 V (Fuse 1), and 0 V (Fuse 2) For isolated signal earth (signal earth is still referenced to 0 V (Fuse 1) by a 10 MΩ resistor)

Strap P1 to P3 Strap P2 to P4, and P5 to P6 Strap P3 to P4. and P5 to P6 Strap P1 to P3, P2 to P4, and P5 to P6 Leave P5 to P6 unstrapped; strap P7 to P8, and P2 to P4. 0 V (Fuse 1) and 0 V (Fuse 2) may still be commoned, if required, by strapping P1 to P3.

The Station Service Module fits into Interface Module position T16 (backplane slot position 80) in the SIA of the subrack. Mating connectors/cabling Rack alarm The rack alarm bus is a 10-way ribbon cable assembly which connects to the rack alarm unit via a 15-way ‘D’ type connector and runs down the right hand side rack cable space. Buckles are used to make loops in the cable at regular intervals. Connections for the subracks are made at the end of the loops using the 15-way ‘D’ type connector. LAN The cable between the LAN transceiver and the subrack, known as the drop cable, uses a 15-way cable. One end of this cable is terminated with a female ‘D’ type connector which engages with the LAN transceiver, the other end is terminated with a male ‘D’ type connector which engages with LAN connector on the Station Service Module. The ‘D’ type connector at the TN-1X end is terminated with plug which has a suitable slide retention compliant with IEC 807.2. The Ethernet port requires a +12 V supply. This is obtained from the subrack Power Unit. The power consumption of the LAN transceiver is less than 0.5 A at +12 V. Power The POWER connector mates with a rack power cables terminated with a flying socket. The socket comprises a moulding (25P SK00 001 AAF) and four power pins 2A (25P CN00 002 AAG).

Nortel TN-1X System Description

14

14-32 External interfaces

75 Ω Star Card (25UJJ00750GWZ) This variant, see Figure 14-21, provides two type 43 coaxial connectors for the external 2048 kHz timing signal ports for the TN-1X.

25UJJ00750GWZ

Figure 14-20 75 Ω Star Card (25UJ00750GWZ) - front and side views

LK1

RX CLK

3 2

AC

1

DC

AC Coupled 3 2

AC

1

DC

DC Coupled

1

2 3 4 5 6 7 8 9 10

Link

75 Ω STAR CARD

TX CLK

323-1061-100 Release 9 Standard

External interfaces 14-33

The upper connector (RX CLK) provides the receive (input) connection. Link LK1 on the module (see Figure 14-21) allows the cable shield of the input to be a.c. coupled to the electrical earth (pins 2 to 3 linked), or d.c. coupled to the electrical earth (pins 1 to 2 linked). The lower connector (TX CLK) provides the transmit (output) connections. The coaxial cable shield of the output connector is d.c. coupled to the electrical earth. The 75 Ω Star Card fits into Interface Module position T8 (backplane slot position 40) in the SIA of the subrack. Mating connectors/cabling The 75 Ω external timing signal ports use coaxial cables terminated with Type 43 coaxial sockets, the mating connector is coded 32C CN15 001 AAL. The preferred coaxial cable type is 3002, however, type 2002 can also be used.

Nortel TN-1X System Description

14

14-34 External interfaces

75 Ω Star Card (NTKD25AA) This variant, see Figure 14-21, provides two type 43 coaxial connectors for the external 2048 kHz timing signal ports for the TN-1X.

RX CLK

1

2 3 4 5 6 7 8 9 10

NTKD25AA

Figure 14-21 75 Ω Star Card (NTKD25AA) - front and side views

75 Ω STAR CARD

TX CLK

323-1061-100 Release 9 Standard

External interfaces 14-35

The upper connector (RX CLK) provides the receive (input) connection. The lower connector (TX CLK) provides the transmit (output) connections. The coaxial cable shield of the output connector is d.c. coupled to the electrical earth. The 75 Ω Star Card fits into Interface Module position T8 (backplane slot position 40) in the SIA of the subrack. Mating connectors/cabling The 75 Ω external timing signal ports use coaxial cables terminated with Type 43 coaxial sockets, the mating connector is coded 32C CN15 001 AAL. The preferred coaxial cable type is 3002, however, type 2002 can also be used.

Nortel TN-1X System Description

14

14-36 External interfaces

Flexible Termination Module The Flexible Termination Module fills the empty position in the SIA below the Power & LCAP module on the TN-1X/S and maintains EMC screening. Figure 14-22 Flexible Termination Module - front and side views

FLEX TERM. SIM

323-1061-100 Release 9 Standard

1 2 3 4 5 6 7 8 9 10

25UJJ00750HJD

External interfaces 14-37

Flexible Access Module The Flexible Access Module, see Figure 14-23, provides the connections for LCAP on the TN-1X.

25UJJ00750GWX

Figure 14-23 Flexible Access Module - front and side views

FLEXIBLE ACCESS MODULE

1 2 3 4 5 6 7 8 9 10

LCAP

Nortel TN-1X System Description

14

14-38 External interfaces

The connection to Local Craft Access Panel is provided by a 25-way ‘D’ type connector (LCAP), no external connections are provided by the unit. This connector provides connections for the following: • •

RS232 local terminal interface receive attention control

• •

Subrack Controller LEDs Engineering Order Wire phone

•

low speed traffic monitor points (future facility)

Mating connectors/cabling Cableform assembly 25Y CN00 021 AAA (part of the LCAP assembly) provides the connection between the module and the Local Craft Access Panel. The Flexible Access Module fits into Interface Module position T1 (backplane slot position 1) in the SIA of the subrack.

323-1061-100 Release 9 Standard

External interfaces 14-39

Power & LCAP Module The Power & LCAP Module provides the primary d.c. power feed into the TN-1X/S subrack and the connection to the EOW/CATT connector panel. Figure 14-24 Power & LCAP Module - front and side views

POWER & LCAP SIM

1 2 3 4 5 6 7 8 9 10

25UJJ00750HJB

LCAP

POWER

Power input The Power connector is a 4-way BIC BT Type 237 connector which provides the connections for two input power supplies. The pin-out of the connector is detailed in Table 14-6. Table 14-6 Power & LCAP Module - power connector pin-out Pin

Function

1 2 3 4

-48 V (fuse 1) 0 V (fuse 1) 0 V (fuse 2) -48 V (fuse 2)

The module contains eight strapping pins, P1 to P8 (see Figure 14-25), which allow the mechanical and two electrical signal earths to be linked. Table 14-7 details the earth strapping options. Nortel TN-1X System Description

14

14-40 External interfaces Figure 14-25 Power & LCAP Module - earth strapping pins P8

P7

P6

P3

P4

P5

P1

P2

C2

C11

Table 14-7 Power & LCAP Module- earth strapping options Earthing Option

Straps

For common 0 V (Fuse 1) and 0 V (Fuse 2) For common signal earth and 0 V (Fuse 1) For common signal earth and 0 V (Fuse 2) For common signal earth, 0 V (Fuse 1), and 0 V (Fuse 2) For isolated signal earth (signal earth is still referenced to 0 V (Fuse 1) by a 10 M¾ resistor)

Strap P1 to P3 Strap P2 to P4, and P5 to P6 Strap P3 to P4. and P5 to P6 Strap P1 to P3, P2 to P4, and P5 to P6 Leave P5 to P6 unstrapped; strap P7 to P8, and P2 to P4. 0 V (Fuse 1) and 0 V (Fuse 2) may still be commoned, if required, by strapping P1 to P3.

EOW/CATT connection A 25-way ‘D’ type socket provides the following through-connections to the EOW/CATT connector panel: • •

RS-232C local terminal (CATT) interface Receive attention control

• •

Subrack Controller LEDs Engineering Order Wire phone

•

Traffic monitor point (future facility; currently terminated on the EOW/ CATT connector panel).

The pin-out of the connector is detailed in Table 14-8.

323-1061-100 Release 9 Standard

External interfaces 14-41

Note: The local terminal may be connected directly to this socket provided only the pins shown in white in Table 14-8 are connected: the other signals might interfere with the operation of the RS-232C port.

14

Table 14-8 Power & LCAP Module - EOW/CATT connector pin-out Pin

Function

Pin

Function

1 2 3 4 5 6 7 8 9 10 11 12 13

Signal ground (0 V) Transmit data (TXD) Receive data (RXD) Ready to send (RTS) Clear to send (CTS) Data set ready (DSR) Signal ground (0 V) Signal ground (0 V) +5 V o/p Detect terminal Signal ground (0 V) EOW B +ve Monitor point +ve

14 15 16 17 18 19 20 21 22 23 24 25

EOW A +ve EOW A -ve Receive ATT switch Receive ATT switch (0 V) General Alarm LED anode General Alm LED cathode Data transmit ready (DTR) Receive ATT LED anode Receive ATT LED cathode Signal ground (0 V) EOW B -ve Monitor point -ve

1 2 3 4 5 6 7 8 9 10 11 12 13

14 15 16 17 18 19 20 21 22 23 24 25

Mating connectors/cabling EOW/CATT Cableform assembly 25Y CN00 750 AAQ is used to connect between the Power & LCAP module and the EOW/CATT connector panel. Power The POWER connector mates with a rack power cables terminated with a flying socket. The socket comprises a moulding (25P SK00 001 AAF) and four power pins 2A (25P CN00 002 AAG).

Nortel TN-1X System Description

14-42 External interfaces

Flexible Access Module (External Alarms) The Flexible Access Module (External Alarms), see Figure 14-26, provides the connections for LCAP on the TN-1X and up to 5 external alarms on the TN-1X.

25UJJ00750HPD

Figure 14-26 Flexible Access Module (External Alarms) - front and side views

FLEXIBLE ACCESS MODULE

1 2 3 4 5 6 7 8 9 10

LCAP

EXTERNAL ALARM

323-1061-100 Release 9 Standard

External interfaces 14-43

The upper connector (LCAP) is a female 25-way ‘D’ type connector which provides the connection to Local Craft Access Panel. This connector provides connections for the following: • •

RS232 local terminal interface receive attention control

• •

Subrack Controller LEDs Engineering Order Wire phone

•

low speed traffic monitor points (future facility)

14

The lower connector (EXTERNAL ALARM) is a male 25-way ‘D’ type which provides the connections for up to 5 external alarm inputs. The connector body and cable shield are d.c. coupled to the mechanical earth. The pin-out of the connector is detailed in Table 14-9. Table 14-9 Flexible Access Module (External Alarms) - external alarm connector pin-out Pin

Function

Pin

Function

1 2 3 4 5 6 7 8 9 10 11 12 13

} External alarm input 1 } External alarm input 2 } External alarm input 3 } External alarm input 4 } External alarm input 5

14 15 16 17 18 19 20 21 22 23 24 25

Not used Not used Not used Not used Not used Not used Not used Not used Not used Not used Not used Not used

Not used Not used Mechanical earth

14 15 16 17 18 19 20 21 22 23 24 25

1 2 3 4 5 6 7 8 9 10 11 12 13

The Flexible Access Module (External Alarms) fits into Interface Module position T1 (backplane slot position 1) in the SIA of the subrack. Mating connectors/cabling LCAP Cableform assembly 25Y CN00 021 AAA (part of the LCAP assembly) provides the connection between the module and the Local Craft Access Panel. EXTERNAL ALARM The lower 25-way male ‘D’ type connector (ALARMS) provides the external alarms connections, the mating connector is coded 32C CN16 100 AJH.

Nortel TN-1X System Description

14-44 External interfaces

External Alarm Module The External Alarm Module, see Figure 14-27, provides the connections for up to 5 external alarms on the TN-1X/S. Figure 14-27 External Alarms Module - front and side views

EXTERNAL ALARM

1 2 3 4 5 6 7 8 9 10

25UJJ00750HPF

EXTERNAL ALARM

The external alarm connector (EXTERNAL ALARM) is a male 25-way ‘D’ type which provides the connections for up to 5 external alarm inputs. The connector body and cable shield are d.c. coupled to the mechanical earth. The pin-out of the connector is detailed in Table 14-9. Table 14-10 External Alarm Module - external alarm connector pin-out Pin

Function

Pin

Function

1 2 3 4 5 6 7 8 9 10 11 12 13

} External alarm input 1 } External alarm input 2 } External alarm input 3 } External alarm input 4 } External alarm input 5

14 15 16 17 18 19 20 21 22 23 24 25

Not used Not used Not used Not used Not used Not used Not used Not used Not used Not used Not used Not used

Not used Not used Mechanical earth

323-1061-100 Release 9 Standard

14 15 16 17 18 19 20 21 22 23 24 25

1 2 3 4 5 6 7 8 9 10 11 12 13

External interfaces 14-45

The External Alarm Module fits into the Interface Module position below the Power & LCAP Module. CAUTION External Alarm Module removal/insertion

Spurious alarms may result if the External Alarm Module is removed or inserted whilst monitoring of external alarms is enabled, but this action shall not cause loss of service or damage to equipment. The External Alarm Module must not be inserted into a operating multiplexer with the external alarm connector already fitted. Electrical protection

The External Alarm Module external alarm inputs provide connection against connection to a battery supply in the range of 40 V to 72 V, no protection is provided for battery surge, lightening pulse or mains voltages. All external equipment connected to the alarm inputs should provide protection from mains voltages in accordance with the requirements of EN 41003 for connection to Telecommunication Network Voltage (TNV) circuits. In the event of high voltages (>TNV) appearing at the external alarm inputs, the External Alarm Module may need to be replaced. External alarm integrity

It is not possible to guarantee the integrity of the end-to-end transmission link, therefore external alarms are only reported remotely if the transmission link is maintained. The external alarms should not be used for life dependent or hazardous activities. Mating connectors/cabling The 25-way male ‘D’ type connector (EXTERNAL ALARM) provides the external alarms connections, the mating connector is coded 32C CN16 100 AJH.

Nortel TN-1X System Description

14

14-46 External interfaces

75 Ω Connector Panel The 75 Ω Connector Panel provides SMB connections for sixteen 2 Mbit/s 75 Ω tributary ports (both reception and transmission) on the TN-1X/S. Figure 14-28 75 Ω Connector Panel

R R

T T

Note: The order of the reception and transmission connectors depends upon the order the connections are made from the Traffic Access Modules to the connector panel. Figure 14-29 is a suggestion of the order to make the connections. Figure 14-29 75 Ω Connector Panel - suggested port connections 7 (M1A) 5 (M1A) 3 (M1A) 1 (M1A) 8 (M1A) 6 (M1A) 4 (M1A) 2 (M1A)

7 (M1A) 5 (M1A) 3 (M1A) 1 (M1A) 8 (M1A) 6 (M1A) 4 (M1A) 2 (M1A)

RX RX 15 (M1B) 13 (M1B) 11 (M1B) 9 (M1B) 16 (M1B) 14 (M1B) 12 (M1B) 10 (M1B)

TX TX 15 (M1B) 13 (M1B) 11 (M1B) 9 (M1B) 16 (M1B) 14 (M1B) 12 (M1B) 10 (M1B)

Mating connectors/cabling The connector panel is connected to the Traffic Access Module using 32 cables of type 25Y CN00 750 AAN. The 75 Ω 2048 kbit/s tributary interfaces use coaxial cables terminated with SMB coaxial sockets, the mating cable is coded 32Y CN00 693 AAA-AAK.

323-1061-100 Release 9 Standard

External interfaces 14-47

120 Ω Connector Panel The 120 Ω Connector Panel provides four 25-way ‘D’ type connections for sixteen 2 Mbit/s 120 Ω tributary ports (both reception and transmission) on the TN-1X/S). Figure 14-30 120 Ω Connector Panel

RX

TX

Note: The order of the reception and transmission connectors depends upon the order the connections are made from the Traffic Access Modules to the connector panel. Figure 14-29 is a suggestion of the order to make the connections. Figure 14-31 120 Ω Connector Panel - connector pin allocation

Trib. 2 13

12

Interface Module position

25

11

Trib. 3

Plug-in unit position S2 (subrack backplane slot position 6)

24

Trib. 1

10

22

23

Trib. 4

9

8

21

Trib. 5

7

20

19

6

Trib. 6 5

18

Trib. 8

4

3

16

17

Trib. 7 2

15

14

1

Drain wire

Input tributaries (male panel connector)

Trib. 7

Drain wire 1

2

3

Trib. 8

Trib. 6 4

5

6

Trib. 4

Trib. 5 7

8

Trib. 1 9

Trib. 3 10

11

12

13

Trib. 2

Output tributaries (female panel connector)

M1A (Upper)

M1B (Lower)

Sig 1

Port 1

Port 9

Sig 2

Port 2

Port 10

Sig 3

Port 3

Port 11

Sig 4

Port 4

Port 12

Sig 5

Port 5

Port 13

Sig 6

Port 6

Port 14

Sig 7

Port 7

Port 15

Sig 8

Port 8

Port 16

Pins 4, 7, 10, 13, 15, 18, 21, and 24 not used.

14

15

16

17

18

19

20

21

22

23

24

25

Signal Pair

Nortel TN-1X System Description

14

14-48 External interfaces Figure 14-32 120 Ω Connector Panel - suggested port connections

M1A

M1B

RX

M1A

M1B

TX

Mating connectors/cabling The connector panel is connected to the Traffic Access Module using 4 cables of type 25Y CN00 750 AAV. Input The left-hand 25-way male ‘D’ type connectors (RX) provide the receive connections, the mating connector is coded 32C CN16 100 AJH. Output The right-hand 25-way female ‘D’ type connectors (TX) provide the transmit connections, the mating connector is coded 32C CN36 100 AKU.

323-1061-100 Release 9 Standard

External interfaces 14-49

EOW/CATT Connector Panel The EOW/CATT connector panel is mounted on the right-hand side of the fibre tray, behind the hinged cover. It provides the following: • •

local terminal interface connection via a 25-way ‘D’ type connector. EOW interface connection via a BT Type 603A socket.

• •

Receive attention control. Subrack Controller LEDs.

Figure 14-33 EOW/CATT Connector Panel - front view

REC ATT

ALM

ACK EOW CATT

Behind hinged cover

The local terminal port is a female 25-way ‘D’ type connector. The pin-out of the connector is detailed in Table 14-8. Table 14-11 EOW/CATT Connector Panel - local terminal connector pin-out Pin

Function

Pin

Function

1 2 3 4 5 6 7 8 9 10 11 12 13

Frame ground (0 V) Transmit data (TXD) Receive data (RXD) Ready to send (RTS) Clear to send (CTS) Data set ready (DSR) Signal ground (0 V) No connection +5 V (not used) Detect terminal No connection No connection No connection

14 15 16 17 18 19 20 21 22 23 24 25

No connection No connection No connection No connection No connection No connection Data transmit ready (DTR) No connection No connection No connection No connection No connection

14 15 16 17 18 19 20 21 22 23 24 25

1 2 3 4 5 6 7 8 9 10 11 12 13

The subrack alarm facilities are provided by a receive attention push-button switch (‘REC ATT’), and two LEDs (red ‘ALM’, green ‘ACK’). These facilities are controlled by the Subrack Controller.

Nortel TN-1X System Description

14

14-50 External interfaces

Mating connectors/cabling The local terminal port (CATT) is an RS232C interface using a 25-way ‘D’ Type socket. The cable must be terminated at the TN-1X end with plug type 32C CN36 100 AKU and 4.40 UNC screws. The cable and connector to the local terminal will depend on which type of local terminal device is used and is therefore customer specific. Cableform 25Y CN00 748 AAA provides suitable cabling and connectors when using a local terminal fitted with a 9-way ‘D’ type connector. A CW1311 type phone jack socket (EOW) is provided for connection of the DTMF handset for Engineering Order Wire operation. The EOW/CATT connector panel is connected to the SIM Type 40S Power & LCAP module using a cable with 25-way ‘D’ type connectors (cableform 25Y CN00 750 AAQ). The connector body and cable shield are d.c. coupled to the mechanical earth.

323-1061-100 Release 9 Standard

External interfaces 14-51

Cabling and connector arrangements TN-1X subrack External cabling normally enters the rack at the top or bottom and runs in the cable space at the sides of the rack. Cable support features are provided. Common rack wiring, that is the power supply, rack alarm bus, and network management bus cables, are normally located in the right hand cable space. Traffic cabling can be located in the left hand space or the right hand space. The cables gain access to the SIA of the subrack via the cut away sections in the subrack sideplates. The connectors are mounted on the front of the Interface Modules. Figure 14-34 shows typical cable grooming for a subrack with 75 Ω 2048 kbit/s interfaces. Figure 14-35 shows typical cable grooming for a subrack with 120 Ω 2048 kbit/s interfaces. TN-1X/S subrack The cabling arrangement will depend upon the installation. Power is connected to the Power & LCAP SIM in the SIA. Incoming tributaries are connected to the connector panel at the lower front of the subrack. Figure 14-36 shows typical cable grooming for a subrack with 75 Ω 2048 kbit/s interfaces. Figure 14-37 shows typical cable grooming for a subrack with 120 Ω 2048 kbit/s interfaces. Tributary connections Tributaries are connected to the subrack via the lower connector panel. The connector panel brings the connection point to the front of the subrack to simplify connection of tributary cables. The connector panel has two positions (see Figure 14-38). The forward position is used whilst the incoming and outgoing tributary cables are being wired to the subrack. The panel is then moved to the rearward position. The special extended screws are threaded at two points to allow the connector panel to be fixed in either position. It is recommended that the tributary cables be dressed to the right-hand side of the rack because the optical fibres have to be dressed to the left-hand side. The connector panel is connected to the TIMs by individual cables.

Nortel TN-1X System Description

14

14-52 External interfaces Figure 14-34 TN-1X 75 Ω traffic cable grooming

STM1 OPT AGG

P/LOA D MNGR

2M TRIB (75 Ω)

1 0

FAIL

FAIL

FAIL

FAIL

11

BLANK MODUL E

FAIL

1 2

2M TRIB OWER (75 Ω)

FAIL

1 3

P UNIT

FAIL

14

POWE R UNIT

SBRK CONT

FAIL

FAIL

25UMN00750G XD

7

25UPW00750HAY

9

STM1 OPT AGG

25UJU00750GXG

6

25UPW00750HAY

8

P/LOA D MNGR

25RBN00021AAB

25RBN00021AAB

FAIL

25UJU00750GXG

25RBN00021AAB

FAIL

5

2M TRIB (75 Ω)

25UJU00750GXG

4

25UPJ00750GXF

BLANK MODUL E

25UTM00750GWA

3

2M TRIB (75 Ω)

25UTM00750GWA

2

25UPJ00750GXF

BLANK MODUL E

25UJU00750GXG

1

SHELF 2 POSITIO 1 N

RECEIVE ATT ALARM ALM ACK

Note: Shown with SIA cover removed

323-1061-100 Release 9 Standard

ESD

External interfaces 14-53 Figure 14-35 TN-1X 120 Ω traffic cable grooming

14 FAIL

FAIL

FAIL

FAIL

1 0

2M TRIB (120 Ω)

11

BLANK MODUL E

FAIL

1 2

2M TRIB (120 Ω)

FAIL

1 3

14

POWE R UNIT

POWE R UNIT

SBRK CONT

FAIL

FAIL

FAIL

25UMN00750G XD

9

P/LOA D MNGR

25UPW00750HAY

8 STM1 OPT AGG

25UPW00750HAY

7 STM1 OPT AGG

25UJU00750GXR

6

P/LOA D MNGR

25RBN00021AAB

25RBN00021AAB

FAIL

25UJU00750GXR

25RBN00021AAB

FAIL

5

2M TRIB (120 Ω)

25UJU00750GXR

4

25UPJ00750GXF

BLANK MODUL E

25UTM00750GWA

3

2M TRIB (120 Ω)

25UTM00750GWA

2

25UPJ00750GXF

BLANK MODUL E

25UJU00750GXR

1

SHELF 2 POSITIO 1 N

RECEIVE ATT ALARM ALM ACK

ESD

Note: Shown with SIA cover removed

Nortel TN-1X System Description

14-54 External interfaces Figure 14-36 TN-1X/S 75 Ω traffic cable grooming 9

FAIL

FAIL

FAIL

FAIL

25RBN00021AAB

P/LOA D MNGR

1 0

BLANK MODUL E

11

BLANK MODUL E

RX

1 2

BLANK MODUL E

1 3

14

POWE R UNIT

POWE R UNIT

SBRK CONT

FAIL

FAIL

FAIL

25UMN00750G XD

8

STM1 OPT AGG

25UPW00750HAY

7 STM1 OPT AGG

25UPJ00750GXF

25RBN00021AAB

25UJU00750GXG

25RBN00021AAB

FAIL

6

P/LOA D MNGR

25RBN00021AAB

5

BLANK MODUL E

25UPW00750HAY

4

25RBN00021AAB

BLANK MODUL E

25UPJ00750GXF

3

2M TRIB (75 Ω)

25RBN00021AAB

2

25UTM00750GWA

BLANK MODUL E

25UTM00750GWA

1

TX

RX

TX

Figure 14-37 TN-1X/S 120 Ω traffic cable grooming 9

P/LOA D MNGR

FAIL

FAIL

FAIL

FAIL

RX

323-1061-100 Release 9 Standard

TX

1 0

BLANK MODUL E

11

BLANK MODUL E

1 2

BLANK MODUL E

1 3

14

POWE R UNIT

POWE R UNIT

SBRK CONT

FAIL

FAIL

FAIL

25UMN00750G XD

8 STM1 OPT AGG

25UPW00750HAY

7 STM1 OPT AGG

25UPW00750HAY

25RBN00021AAB

25RBN00021AAB

25UJU00750GXR

25RBN00021AAB

FAIL

6

P/LOA D MNGR

25RBN00021AAB

5

BLANK MODUL E

25RBN00021AAB

4

25RBN00021AAB

BLANK MODUL E

25UPJ00750GXF

3

2M TRIB (120 Ω)

25UTM00750GWA

2

25UTM00750GWA

BLANK MODUL E

25UPJ00750GXF

1

External interfaces 14-55 Figure 14-38 Connector panel forward and rearward positions

14

Connector panel in forward position for connecting the tributary cables

Connector panel in rearward position

Optical connections The optical signal cables connect directly to FC-PC type optical connectors on the front panels of the optical units. The optical cables lay in a tray, which contains retaining clips, mounted at the bottom of the plug-in unit (see Figure 14-34 to Figure 14-37). The upper connector (RX) is the receive connector, the lower connector (TX) is the transmit connector. The optical connectors on the front of the optical unit are protected by a hinged cover. For safety reasons, this cover can only be opened when the unit is not fully inserted into the subrack (the front panel of the adjacent unit preventing the cover from opening). This prevents access to the optical connectors whilst the unit is powered-up and an optical output signal is present. CAUTION Damage to unit

Do not attempt to force open the cover whilst the unit is fully inserted into the subrack.

Nortel TN-1X System Description

14-56 External interfaces

LAN transceiver connections The Nortel Networks TN-1X and the Preside EC-1 Element Controller interconnect through 10 Mbit/s CSMA/CD (Ethernet-type) LANs. The Nortel Networks TN-1X and the Preside EC-1 Element Controller have standard LAN interfaces which conform to Ethernet, IEEE 802.3 and ISO 8802-3. There are a number of physical options for the LAN infrastructure itself (that is, external LAN equipment to which both the Nortel Networks TN-1X and the Preside EC-1 Element Controller can attach). For use in a telecommunications environment, a medium with good electromagnetic compatibility is necessary, the following are recommended: • 10Base-T - 10 Mbit/s twisted pair baseband cabling (using a central LAN ‘hub’). •

10Base5 - 10 Mbit/s thick coaxial baseband cabling

For most purposes, 10Base-T provides the more cost effective and easily implemented solution. Note: Nortel Networks Product Engineering Code (PEC) for the LAN Transceiver (10Base-T Attachment Unit Interface) is NTPA1532. [Common Product Code (CPC) is A0650261] 10Base5 was the original Ethernet medium but is generally more expensive and harder to install than 10Base-T. If the current installations use 10Base5, Nortel Networks recommends that you use 10Base-T when extending the LAN. You can do this extension through the use of a 10Base-T hub, connected directly or through a repeater to the thick coax segment. Extension of the LAN within a local site, but beyond the distance span of a single segment, can be completed by repeaters or local bridges/routers. Remote bridges/routers provide a means of extending the LAN across separated sites. For extension of a LAN between two sites up to a short distance and where there are spare fibres between the sites, Fibre Optic Inter Repeater Links (FOIRL) can be used to interconnect LAN segments on the two sites. The maximum length of a single FOIRL segment is 1 km. end of chapter

323-1061-100 Release 9 Standard

15-1

Appendix A: Synchronous digital hierarchy (SDH)

15- 15

The synchronous digital hierarchy, covered by ITU-T recommendation G.707, Network node interface for the synchronous digital hierarchy (SDH), details the international standards covering synchronous multiplexing and transmission. 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 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.

Nortel TN-1X System Description

15-2 Appendix A: Synchronous digital hierarchy (SDH)

SDH multiplexing structure The first level of the SDH is at 155,520 kbit/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,520 kbit/s STM-4: 622,080 kbit/s

•

STM-16: 2,488,320 kbit/s (2.4 Gbit/s)

The 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 generalised multiplexing structure of the SDH is shown in Figure 15-1. Figure 15-1 SDH generalised multiplexing structure xN STM-N

x1 AUG

AU-4

VC-4

C-4

140 Mbit/s

C-3

45 Mbit/s 34 Mbit/s

x3 x1

TUG-3

x3

TU-3

VC-3

x7 AU-3

VC-3 x7

Pointer Processing Multiplexing

x1 TUG-2

TU-2

VC-2

C-2

6 Mbit/s

x4 TU-12

VC-12

C-12

2 Mbit/s

TU-11

VC-11

C-11

1.5 Mbit/s

x3

Aligning Mapping

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. 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. 323-1061-100 Release 9 Standard

Appendix A: Synchronous digital hierarchy (SDH) 15-3

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 15-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.

Nortel TN-1X System Description

15

15-4 Appendix A: Synchronous digital hierarchy (SDH) Figure 15-2 STM-1 frame structure 270 Columns (Bytes) 1

9 10

270

1 SOH 3 4 AU PTRs 9 Rows 5

STM-1 Payload

SOH

9

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-1X The TN-1X uses a subset of the SDH multiplexing structure as shown in Figure 15-13. Figure 15-3 TN-1X - multiplexing structure xN STM-N

x1 AUG

VC-4

x3

x7

x3 AU-4

TUG-3

TUG-2

TU-12

VC-12

C-12

TU-3

VC-3

C-3

2 Mbit/s

x1 34 Mbit/s

The procedure for assembling the STM-1 frame for the TN-1X and brief descriptions of the overhead bytes are given in the following sections. 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 15-4). The additional fixed stuff bits and bytes maintain a defined size of 140 bytes for a 500 µs TU multiframe (that is, 4 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 “Path overheads” on page 15-10).

323-1061-100 Release 9 Standard

Appendix A: Synchronous digital hierarchy (SDH) 15-5 Figure 15-4 2048 kbit/s tributary/VC-12/TU-12 mapping VC-12

TU-12

V5

V1 (Ptr 1)

State of H4 byte XXXXXX00

R 32 Bytes

15

R J2 C1 C2 O O O O R R

Zero Ptr offset

XXXXXX01

V5

32 Bytes

Z6 C1 C2 O O O O R R 32 Bytes

V3 (Ptr 3, Action)

XXXXXX10

V4 (Reserved)

XXXXXX11

144 Bytes

R

500 µs

140 Bytes

V2 (Ptr 2)

R Z7 C 1 C 2 O O O O R S1 S2 I

I

I

I

I

I

I

31 Bytes R Asynchronous mapping for 2048 kbit/s tributary (Multiframe) I: Information Bit C: Justification Control R: Fixed Stuff J2: LO Path Trace

O: Overhead S: Justification Opportunity V5: VC1 Path Overhead Z6, Z7: Reserved

VC3/TU-3 mapping/demapping Mapping/demapping between 34368 kbit/s and 44736 kbit/s tributary signals and VC-3s/Tributary Unit-3s (TU-3s) of the Synchronous Digital Hierarchy (SDH) is shown in Figure 15-5. The 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).

Nortel TN-1X System Description

15-6 Appendix A: Synchronous digital hierarchy (SDH) Figure 15-5 34/45 Mbit/s tributary/VC-3TUG-3/ mapping 86 TUG-3 H1

VC-3

H2

J1

H3

B3 C2

T1

3 rows

T2

3 rows

T3

3 rows

G1 Fixed stuff

F2 H4 F3 K3 N1 1

VC-3 POH

125 µs

84

34 Mbit/s 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

45 Mbit/s 8R

8R

RRC 5I

R

Fixed stuff bit

C

Justification control bit

S

Justification opportunities bit

I

Information bit

O

Overhead bit

8R 200 I

323-1061-100 Release 9 Standard

CCRRRRRR

8R 8I

200 I

CCRROORS 8I

200 I

Appendix A: Synchronous digital hierarchy (SDH) 15-7

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 15-4). 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. Figure 15-6 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 15-7.

15

Figure 15-6 Multiplexing of TU-12 via a TUG-2 TUG-2 12 Columns

VC Ptr

VC Ptr

VC Ptr

TU-12 9 Rows

4 Columns

Nortel TN-1X System Description

15-8 Appendix A: Synchronous digital hierarchy (SDH) Figure 15-7 TU-12/TUG-2/TUG-3 multiplexing A

B

C

TU-12

TUG-2

AB AB AB AB C C C C

(1)

12

TUG-3

34

(2)

12 56

7

34

12 56

Stuffing 1 3 5 7 9 2 4 6 8

7

34

(3)

12 56

7

34

12 56

7

34

(7)

12 56

7

34

12 56

7

34

56

7

85 84 86

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 15-7. The inclusion of the TUG-3 is primarily to provide a structure for 34,368 kbit/s and 44,736 kbit/s transmission rates. 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 15-8.

323-1061-100 Release 9 Standard

Appendix A: Synchronous digital hierarchy (SDH) 15-9 Figure 15-8 Multiplexing of a TU-3 via a TUG-3

86 columns

TUG-3

H1 H2 85 columns

H3

Fixed stuff

J1

15

B3 C2 G1 F2

Container-3

H4 N1 K3 N1

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 15-9. 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 15-10). Columns two and three are fixed stuff. Figure 15-9 Multiplexing of three TUG-3s into a VC-4

TUG-3

TUG-3 (A) 1

TUG-3 (B) 86

1

TUG-3 (C) 86

1

86

POH

VC-4

AB AB A C C

1 3 5 7 9 2 4 6 8

B C A B CA B C

261

Nortel TN-1X System Description

15-10 Appendix A: Synchronous digital hierarchy (SDH)

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 15-10). The AU-4 is placed directly in the AUG, which together with the SOH, forms the STM-1. Figure 15-10 Mapping of a VC-4 into a STM-1 via an AU-4/AUG 9

3

261

AU-4

AUG SOH

1

J1 B3 AU-4 PTR

5

C2

SOH

G1

VC-4

F2 H4 N1 Z4 N1

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 15-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. The V5 byte in the VC-12 (see Figure 15-4) is the path overhead information pertaining to the VC-12 end-to-end path. The function of the V5 bits is shown in Figure 15-11 and is detailed in subsequent paragraphs: Figure 15-11 VC-12 Path Overhead RFI

REI BIP-2 1

323-1061-100 Release 9 Standard

2

RDI

Signal Label 3

4

5

6

7

8

Appendix A: Synchronous digital hierarchy (SDH) 15-11

•

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 (Bit 3). The Remote Error Indication (REI) bit is used to communicate detected BIP-2 errors back to the VC-12 path originator. RFI (Bit 4). Remote Fail Indicator (RFI). Not used in present applications.

• • •

Signal label (Bits 5 to 7). These bits are used to indicate the payload mapping and equipped status. RDI (Bit 8). The Remote Defect Indicator (RDI) bit is used to indicate certain detected TU path alarms to the VC-12 path originator.

The VC-3/VC-4 path overhead consists of nine bytes as shown in Figure 15-8 and Figure 15-10. The function of the nine bytes is as follows: •

• • • • •

Path trace (J1). 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). This byte provides an error monitoring function for the VC-3/VC-4 path. Signal label (C2). This byte is used to indicate the composition of the VC-3/VC-4 payloads. Path status (G1). This byte is used to convey path terminating status and performance information back to the VC-3/VC-4 path originator. Path user channel (F2). This byte is available for user communication purposes between path elements. Not used in present applications.

•

Multiframe indicator (H4). This byte provides a generalised multiframe indicator for VC-12 payloads. Automatic Protection Switching (APS) (K3). This byte is allocated for APS signalling for high order path protection. Not used in present applications.

•

Spare (F3, K3, N1). 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 15-12.

Nortel TN-1X System Description

15

15-12 Appendix A: Synchronous digital hierarchy (SDH) Figure 15-12 Section overhead A1 A1 A1 A2 A2 A2 J0 RSOH

B1

E1

F1

D1

D2

D3

AU-Pointer H1 H1 H1 H2 H2 H2 H3 H3 H3

MSOH

B2 B2 B2 K1

K2

D4

D6

D5

D7

D8

D9

D10

D11

D12

A1, A2: B1, B2: J0:

Framing Bit Error Monitoring Regenerator Section Trace - not currently used Data Channel D1 - D12: Order Wire E1, E2: User Channel F1: H1, H2, H3: AU-Pointer Bytes Automatic Protection Switching K1, K2: Timing Marker Byte S1 not currently used Section FEBE - not currently M1: used

S1 F3 F3 K3 K3 M1 E2 All unmarked bytes are reserved for future international standardisation.

Bytes reserved for national use.

The function of the RSOH bytes is as follows: • •

Framing (A1, A2). These bytes are used for frame alignment purposes. BIP-8 (B1). This byte is used to provide an error monitoring function for a regenerator section. The byte is also used in the frame alignment process.

•

Order wire (E1). This byte is used to provide an order wire channel which may be accessed at regenerators and multiplexers.

• •

User channel (F1). This byte is reserved for user purposes. Not used in present systems. DCCR (D1 to D3). The Data Communication Channel (DCC) bytes provide a 192 kbit/s regenerator data channel. These bytes can be used as a physical layer for the ECC.

•

Regenerator Section Trace (J0). Not used in present applications.

The function of the MSOH bytes is as follows: • •

•

• •

BIP-24 (B2). These bytes are used to provide an error monitoring function for the multiplex section. APS channel (K1, K2). The Automatic Protection Switching (APS) Channel bytes are used for APS signalling. In present systems, the bytes are only used to communicate multiplex section REI and Alarm Indication Signal (AIS) indications to the far multiplexer. DCCM (D4 to D12). The Data Communication Channel bytes provide a 576 kbit/s multiplex data channel. These bytes can be used as a physical layer for the ECC. Order wire (E2). This byte is used to provide an order wire channel which may be accessed only at multiplex section terminations. Synchronisation Status Messaging Byte (S1). This byte is used for transmitting synchronisation status.

323-1061-100 Release 9 Standard

Appendix A: Synchronous digital hierarchy (SDH) 15-13

•

Section REI (M1). Not used in present applications.

All other bytes in the RSOH and MSOH are either reserved for national use or for future international standardisation and are not used in present systems. TN-1X/4 Multiplexing structure The TN-1X/4 multiplexer provides interfaces at the STM-4 level of the Synchronous Digital Hierarchy. The STM-4 signal contains four AUGs together with Section Overhead (SOH) information (see Figure 15-13). The four AUGs are one-byte interleaved and have a fixed phase relationship with respect to the STM-4. Figure 15-13 STM-4 frame structure 1 1

261

9

1 1

1 1

#1

#2

AUG

SOH

261

9

AUG

261

9

1 1

261

9

#3

#4

AUG

AUG

12341234

12341234

SOH 4x9

4 x 261 STM-4

Each AUG has a structure of 9 rows by 261 columns plus 9 bytes in row 4 (for the AU pointers). In this document, the AUGs (and corresponding STM-1s) are denoted #1, #2, #3 and #4 corresponding to their order in the STM-4 payload. The section overhead bytes occupy columns 1 to 36, rows 1 to 3 and 5 to 9 of the frame as shown in Figure 15-14. It should be noted that the TN-1X/4 multiplexer assembles the STM-4 signal by interleaving four STM-1 signals, each of which has a SOH. Therefore the STM-4 frame contains STM-1 overhead in all four STM-1 channels and some of the bytes reserved for national and future international usage contain STM-1 overhead bytes. In the receive direction, only the appropriate SOH bytes are processed. The first row of the section overhead (i.e. 36 columns) is not scrambled.

Nortel TN-1X System Description

15

15-14 Appendix A: Synchronous digital hierarchy (SDH) Figure 15-14 STM-4 section overhead ITU-U defined overhead 36 columns

9 rows

A1 A1 A1 A1 A1 A1

A1 A1 A1 A1 A1 A1 A2 A2 A2 A2 A2 A2 A2 A2 A2 A2 A2 A2 J0 Z0 Z0

B1

E1

D1

D2

D3

AU Pointers B2 B2 B2 B2 B2 B2 B2 B2 B2 B2 B2 B2

K1

K2

D4

D5

D6

D7

D8

D9

D10

D11

D12

S

F3 F3 F3 F3 F3 F3 F3 F3 F3 F3 F3 K3 K3 M1 K3 K3 K3 K3 K3 K3 k3 K3 K3 E2

TN-1X/4 overhead A1 A1 A1 A1 A1 A1

9 rows

Z0

F1

36 columns A2 A2 A2 A2 A2 A2 A2 A2 A2 A2 A2 A2 C1 C1 C1 C1

A1 A1 A1 A1 A1 A1

B1 B1 B1 B1

E1 E1 E1 E1

F1 F1 F1 F1

D1 D1 D1 D1

D2 D2 D2 D2

D3 D3 D3 D3

B2 B2 B2 B2 B2 B2 B2 B2 B2 B2 B2 B2

K1 K1 K1 K1

K2 K2 K2 K2

D4 D4 D4 D4

D5 D5 D5 D5

D6 D6 D6 D6

AU Pointers

D7 D7 D7 D7

D8 D8 D8 D8

D9 D9 D9 D9

D10 D10 D10D10

D11 D11D11 D11

D12 D12D12 D12

F3 F3 F3 F3 F3 F3 F3 F3 F3 F3 F3 F3 K3 K3 K3 K3 K3 K3 K3 K3 K3 K3 K3 K3 E2 E2 E2

Bytes reserved for national use. All unmarked bytes are reserved for future use international standardisation (for media dependent, additional national use and other purposes).

end of chapter

323-1061-100 Release 9 Standard

E2

16-1

Appendix B: Important notes

16-

Introduction This appendix provides operational qualifications for the Nortel Networks TN-1X R9. A user who is uncertain of the operation of the system should refer to the relevant section of the NTPs, where explanatory notes are provided. If any assistance is required on the Nortel Networks TN-1X or its Preside EC-1 Element Controller, Nortel Networks provides a full technical support service for its customers. The Nortel Networks Service Desk can be called at any time on the following numbers: Within Europe: Freephone

00800 8008 9009

Outside of Europe:

+44 20 8920 4618

Fax within the United Kingdom:

020 8945 3456

Fax outside of the United Kingdom: +44 20 8945 3456 As an option, you can contact technical support through the Nortel Networks web site: http://www.nortelnetworks.com/help/contact/global

Operational qualifications for Release 7 TN-1X multiplexer 1 Payload Manager switching should not be performed unless absolutely operationally necessary. Switching between Payload Managers should be preferably only be performed during periods of low traffic density. 2 As a result of hot inserting an Aggregate Unit of a gateway multiplexer, communications loss to the NE may occur. To prevent the loss of comms being permanent, ensure that the relevant slot is equipped as the new aggregate before the aggregate is inserted. 3 Loopbacks on 2 Mbit/s Tributary Unit variants 25U JU00 750 HVQ/HVT work correctly except for the alarms that are reported when the loopbacks are applied. For example, if a 2 Mbit/s tributary connection is made and there is no traffic input, a ‘PPI-LOS’ alarm is reported as expected. When a ‘Local’ loopback is applied to that tributary port, the ‘PPI-LOS’ alarm should clear. However, when using these variants of the 2 Mbit/s Tributary Nortel TN-1X System Description

16

16-2 Appendix B: Important notes

4

Unit’ the alarm does not clear but traffic is restored. Conversely, whenever there is no connection associated with a tributary port and a ‘Local’ loopback is applied to that port, ‘PPI-Unexp_Signal’ and ‘PPI-AIS’ would be expected to be reported. However, when using these variants of the 2 Mbit/s Tributary Unit’, the alarms are not reported. The user must ensure that the correct Payload Manager and Aggregate Units are configured on the NE before imposing configuration. Failure to do so will result in loss of communications to the NE once the defaults have been imposed. A site visit will be required to correct this situation.

end of chapter

323-1061-100 Release 9 Standard

17-1

Appendix C: Release 9 units, feature lists and compatability 17Introduction The following tables lists the plug-in units available for Release 9, features and compatibilty differences to earlier TN-1X releases. Table 17-1 Release 9 plug-in unit codes

17

Applicability Unit Type

Code TN-1X

TN-1X/S

Power Units NTKD24AA

√

√

NTKD19AB

√

√

Payload Manager (VC-12 Payload only)

NTKD10CA

√

√

Payload Manager (Mixed Payload)

NTKD10AA

√

√

STM-1 Optical Aggregate Unit (1310 nm Long Haul)

NTKD20AA

√

√

STM-1 Optical Aggregate Unit (1550 nm)

NTKD21AA

√

√

25U TM00 750 GWB

√

2 Mbit/s Tributary Unit 75 Ω

NTKD23AA (see Note 1)

√

√

2 Mbit/s Tributary Unit 120 Ω

NTKD23AB (see Note 1)

√

√

25U JU00 750 HJZ

√

Power Unit 120 W Subrack Controllers Subrack Controller (4M RAM) Payload Managers

STM-1 Optical Aggregate Units

STM-1 Electrical Aggregate Units STM-1 Electrical Aggregate Unit 2 Mbit/s Tributary Units

34 Mbit/s Tributary Units (16x2) 34 Mbit/s Tributary Unit (16x2)

Nortel TN-1X System Description

17-2 Appendix C: Release 9 units, feature lists and compatability Table 17-1 Release 9 plug-in unit codes (continued) Applicability Unit Type

Code TN-1X

TN-1X/S

34/45 Mbit/s Tributary Units (VC-3) NTKD16AC

√

NTKD11AA

√

NTKD12AA (see Note 2)

√

25U EP00 750 GXB

√

EOW Unit (ICC2)

NTKD13AA

√

EOW Handset Kit

25S KM00 750 HZM

√

34/45 Mbit/s Tributary Unit (see Note 3) STM-1 Optical Tributary Units STM-1 Optical Tributary Unit 1”

√

STM-1 Electrical Tributary Units STM-1 Electrical Tributary 1” (Mixed Payloads) LCAPs Local Craft Access Panel 75 Ω EOW Units

√

Note 1: The NTKD23AA must be equipped as a 25U JU00 750 HVT unit and the NTKD23AB must be equipped as a 25U JU00 750 HVQ unit. Note 2: The NTKD12AA can be used as a direct replacement for the STM-1 Electrical Tributary Unit 2" 25U JU00 750 JBK Note 3: The NTKD16AC reports AIS on the 45 Mbit/s side. —end—

Table 17-2 Features: 2 Mbit/s Tributary units Code

ASIC version (Quad 2M Trib)

Feature J1 Path Trace

J2 Path Trace

CRC4 PM

Yes

No

No

25U JU00 750 HVT (PCS 01-03) Version 4

Yes

Yes

No

25U JU00 750 HVT (PCS 05)

Version 5

Yes

Yes

Yes

NTKD23AA (equip as HVT)

CR Version 5

Yes

Yes

Yes

Version 3.5

Yes

No

No

25U JU00 750 HVQ (PCS 01-03) Version 4

Yes

Yes

No

25U JU00 750 HVQ (PCS 04)

Version 5

Yes

Yes

Yes

NTKD23AB (equip as HVQ)

CR Version 5

Yes

Yes

Yes

2 Mbit/s Tributary Unit 75 Ω 25U JU00 750 GXG

Version 3.5

2 Mbit/s Tributary Unit 120 Ω 25U JU00 750 GXR

323-1061-100 Release 9 Standard

Appendix C: Release 9 units, feature lists and compatability 17-3 Table 17-3 Features: 34/45 Mbit/s Tributary units Code

Feature Full 45M ANSI AIS detection

34/45 Mbit/s Tributary Units (VC-3) NTKD16AA

No

NTKD16AC

Yes

Table 17-4 code

Subrack Controller

25UMN00750GXD

Subrack Controller

NTKD19AB

Payload Manager

Prefered for Release 9

Item

Obsolete at Release 9

Compatibility of TN-1X Release 9 hardware and software

•

TN-1X Software Release 2.5

3

4

4.1

5

6

7

8

9

Y

Y

Y

Y

Y

Y

Y

Y

Y

N

N

N

N

N

Y

Y

Y

Y

25UPJ00750GXF

Y

Y

Y

Y

Y

Y

Y

Y

Y

Payload Manager (TSI-2)

25UPJ00750HZQ

N

N

N

N

N

Y

Y

Y

Y

•

Payload Manager (Mixed Payload)

NTKD10AA

•

N

N

N

N

N

N

Y

Y

Y

Payload Manager (VC-12 Payload only)

NTKD10CA

•

N

N

N

N

N

Y

Y

Y

Y

STM-1 Opt. Aggregate (1310 nm L/H)

25UTM00750GWA

•

Y

Y

Y

Y

Y

Y

Y

Y

Y

STM-1 Opt. Aggregate (1310 nm L/H)

25UTM00750HWF

•

N

N

N

N

Y

Y

Y

Y

Y

STM-1 Opt. Aggregate (1310 nm L/H)

NTKD20AA

N

N

N

N

Y

Y

Y

Y

Y

STM-1 Opt. Aggregate (1550 nm)

NTKD21AA

•

N

N

N

N

N

N

N

Y

Y

STM-1 Elect. Aggregate

25UTM00750GWB

Y

Y

Y

Y

Y

Y

Y

Y

Y

STM-4 1310 nm Aggregate (L/H)

25UTM00750GSA

•

N

Y

Y

Y

Y

Y

Y

Y

Y

STM-4 1310 nm Aggregate (I/S)

25UTM00750GSC

•

N

N

Y

Y

Y

Y

Y

Y

Y

STM-4 1550 nm Aggregate (L/H)

25UTM00750HVB

•

N

N

N

N

Y

Y

Y

Y

Y

STM-1 2" Optical Trib

25UJU00750GVA

•

N

N

Y

Y

Y

Y

Y

Y

Y

STM-1 1" Optical Trib

25UTM00750HWE

•

N

N

N

N

Y

Y

Y

Y

Y

STM-1 1" Optical Trib (TSI-2)

25UTM00750HWG

•

N

N

N

N

N

Y

Y

Y

Y

STM-1 1" Optical Trib (Mixed Payloads)

NTKD11AA

N

N

N

N

N

N

Y

Y

Y

•

Nortel TN-1X System Description

17

17-4 Appendix C: Release 9 units, feature lists and compatability Table 17-4 code

Obsolete at Release 9

Item

Prefered for Release 9

Compatibility of TN-1X Release 9 hardware and software (continued)

•

TN-1X Software Release 2.5

3

4

4.1

5

6

7

8

9

N

N

Y

Y

Y

Y

Y

Y

Y

N

N

N

N

N

Y

Y

Y

Y

STM-1 2" Electrical Trib

25UJU00750GVB

STM-1 2" Electrical Trib (TSI-2)

25UJU00750JBK

STM-1 1" Elect Trib (Mixed Payloads)

NTKD12AA

N

N

N

N

N

N

Y

Y

Y

2M Trib 75 Ω

25UJU00750GXG

•

Y

Y

Y

Y

Y

Y

Y

Y

Y

2M Trib 75 Ω (Q2M-4B)

25UJU00750HVT

•

N

N

N

N

N

Y

Y

Y

Y

•

2M Trib 75 Ω

NTKD23AA

N

N

N

N

N

Y

Y

Y

Y

2M Trib 120 Ω

25UJU00750GXR

•

Y

Y

Y

Y

Y

Y

Y

Y

Y

2M Trib 120 Ω (Q2M-4B)

25UJU00750HVQ

•

N

N

N

N

N

Y

Y

Y

Y

2M Trib 120 Ω

NTKD23AB

N

N

N

N

N

Y

Y

Y

Y

N

N

N

N

N

Y

Y

Y

Y

N

N

N

N

N

N

N

Y

Y

N

N

N

N

N

N

N

N

Y

N

N

N

N

Y

Y

Y

Y

Y

•

•

34M Trib (16 x VC12)

25UJU00750HJZ

34/45M Trib (VC-3)

NTKD16AA

34/45M Trib (VC-3 with 45M AIS)

NTKD16AC

ICC (EOW)

25USV00750GVX

• • •

ICC (EOW/1:N)

NTKD13AA

N

N

N

N

N

N

Y

Y

Y

ATU

25UMU00750HVJ

N

N

N

N

Y

Y

Y

Y

Y

2M 75 Ω TAM (1:N Protection)

NTKD14AA

N

N

N

N

N

N

Y

Y

Y

2M 120 Ω TAM (1:N Protection)

NTKD15AA

N

N

N

N

N

N

Y

Y

Y

34/45M 75 Ω TAM

NTKD17AA

N

N

N

N

N

N

N

Y

Y

34/45M 75 Ω 1:1 protection TAM

NTKD17AB

N

N

N

N

N

N

N

Y

Y

STAR TAM

NTKD25AA

N

N

N

N

N

N

N

Y

Y

Power Unit

NTKD24AA

Y

Y

Y

Y

Y

Y

Y

Y

Y

—end— end of chapter

323-1061-100 Release 9 Standard

18-1

Index 1:N 2 Mbit/s tributary protection 10-3 120 Ω Connector Panel 14-47 120 Ω TAM (1:N Protection) (TN-1X) 14-13 120 Ω TAM (TN-1X) 14-10 120 Ω TAM (TN-1X/S) 14-16 2 Mbit/s Tributary Unit 5-9 1:N protection 10-3 34 Mbit/s Tributary Unit (16x2) 5-10 34/45 Mbit/s Tributary Unit (VC-3) 5-9 manual tributary protection 10-18 75 Ω Connector Panel 14-46 75 Ω Star Card 14-32, 14-34 75 Ω TAM (1:N Protection) (TN-1X) 14-6 75 Ω TAM (TN-1X) 14-4 75 Ω TAM (TN-1X/S) 14-8

A aggregates 1-1 alarms external 4-7, 6-6 filtering 6-5 handling 6-5 masking 6-5 monitoring 1-4, 6-5 rack 6-5 automatic laser shutdown 3-17 laser test facility 3-19

B backplane connectors 13-5 links 13-5 TN-1X 13-6 TN-1X/S 13-8 blank panel 13-13 codes 3-16

18C cabling TN-1X subrack 14-51 TN-1X/S subrack 14-51 card controllers 6-3 categories rack alarm 6-5 channel designations 9-3 channel numbering schemes 9-1 clock 6-4 configuration 1-4 configurations system 2-1 connections 9-1, 9-5 internal traffic 9-6 traffic 9-10 connector panels 3-12 120 Ω Connector Panel 14-47 75 Ω Connector Panel 14-46 EOW/CATT Connector Panel 14-49 TN-1X codes 3-15 consequent actions 9-13, 9-14, 9-16 path trace 9-13 signal label 9-16 construction 13-1 equipment practice 4-1 Interface Modules 13-9 plug-in units 13-9 cover 13-10, 13-11

D defragmentation 9-9 detached mode 6-13 diagnostics 12-1 dimensions 4-1 drop and insert multiplexer 2-3 chains 2-4 ring 2-5 Nortel TN-1X System Description

18

18-2 Index

E earthing 13-13 ECC port 6-17 electromagnetic compatibility 4-7, 13-12 electrostatic discharge 13-12 Element Controller 1-4 remote central archive 1-4 standby 1-4 Engineering Order Wire 2-10, 12-5, 13-11 environmental conditions 4-7 EOW, see Engineering Order Wire EOW/CATT Connector Panel 14-49 equipment codes 3-12 equipment management 6-1 bus architecture 6-2 equipment practice 4-1 equipping 3-9 events monitoring 1-4 external alarms 4-7, 6-6 external connections 14-1 external interfaces, see system interfaces

Flexible Access Module 14-37 Flexible Access Module (External Alarms) 14-42 Flexible Termination Module 14-36 High Speed Aggregate Module 14-25 High Speed TAM (16x2) 14-19 High Speed TAM (VC-3) 14-21 High Speed Tributary Module 14-27 Manual Tributary Protection TAM 14-23 Power & LCAP Module 14-39 Station Service Module 14-29 TN-1X codes 3-15 TN-1X/S codes 3-15 interfaces see also system interfaces see internal traffic interfaces see system interfaces internal traffic interfaces 5-1 overhead buses 5-3 Payload Manager/Aggregate Unit 5-3 Tributary Unit/Payload Manager 5-2 inventory 3-16

F

L

Flexible Access Module 14-37 Flexible Access Module (External Alarms) 14-42 Flexible Termination Module 14-36 frame structure STM-1 15-4 STM-4 15-13

H High Speed Aggregate Module 14-25 High Speed TAM (16x2) 14-19 High Speed TAM (VC-3) 14-21 High Speed Tributary Module 14-27

LAN transceivers 14-56 LCAP, see Local Craft Access Panel Local Craft Access Panel 3-12, 14-2 local terminal 6-15 loopback 2 Mbit/s Tributary Unit 12-2 34 Mbit/s Tributary Unit (16x2) 12-4 34/45 Mbit/s Tributary Unit (VC-3) 12-3 STM-1 Aggregate Unit 12-4 STM-1 Tributary Unit 12-4

M

manual area addresses 6-18 manual tributary protection 10-18 Manual Tributary Protection TAM 14-23 I mapping Interface Modules 3-9, 13-9 2 Mbit/s to VC-12 15-4 120 Ω TAM (1:N Protection) TUG-3s to VC-4 15-8 (TN-1X) 14-13 VC-4 to STM-1 15-10 120 Ω TAM (TN-1X) 14-10 masking 6-5 120 Ω TAM (TN-1X/S) 14-16 multiplexer section protection 10-9 75 Ω Star Card 14-32, 14-34 multiplexing 75 Ω TAM (1:N Protection) (TN-1X) 14-6 TUG-2s to TUG-3 15-8 75 Ω TAM (TN-1X) 14-4 TUG-3s to VC-4 15-8 75 Ω TAM (TN-1X/S) 14-8 VC-12s to TUG-2 15-7 dimensions 4-2 323-1061-100

Release 9

Standard

Index 18-3

N network management 6-15 Network Resource Manager 1-5 Nortel TN-1X 1-1, 5-4 block diagram 3-1 external interfaces 1-2 multiplexing structure 15-4 subrack layout 3-4 Nortel TN-1X/4 STM-1 routing 2-6 typical deployment 2-7 Nortel TN-1X/S block diagram 3-2 external interfaces 1-2 subrack layout 3-5

P path overhead 15-10 path protection switching 10-1 path trace 9-12 consequent actions 9-13 single fibre working 9-14 Payload Manager 5-12 switching 10-7 performance monitoring 1-4, 11-1 anomalies and defects 11-4 counts 11-1 logs 11-6 periods 11-5 quality of service violation alarms 11-6 plug-in units 3-6, 13-9 codes 3-13, 17-1 dimensions 4-2 equipping 3-9 TN-1X subrack 3-8 TN-1X/S subrack 3-8 port designations 9-3 power 8-1 input supply 4-1 power consumption 4-1 TN-1X subrack 8-1 TN-1X/S subrack 8-2 Power & LCAP Module 14-39 Power Unit 8-1 protection 10-1, 10-3 1:N 2 Mbit/s tributary 10-3 manual tributary protection 10-18 multiplexer section 10-9 path 10-1

Payload Manager 10-7

Q quality of service violation alarms 11-6

R rack alarm categories 6-5 real time clock 6-4 remote central archive 1-4 remote layer management 6-17 reporting 1-4 restart cold 6-14 warm 6-14 rings, see drop and insert multiplexer routers 6-19

S section overhead 15-11, 15-14 security management 1-4 Service Interface Module (SIM), see Interface Modules SIA cover 13-10, 13-11 signal label 9-15 consequent actions 9-16 single fibre working 2-9 path trace 9-14 software 6-8 status 6-9 upgrade 6-9 standby Element Controller 1-4 Station Service Module 14-29 status software 6-9 STM-1 frame structure 15-4 section overhead 15-11 tributaries 2-7 STM-1 Aggregate Unit 5-13 STM-1 Tributary Unit 5-11 STM-4 aggregates 2-5 frame structure 15-13 section overhead 15-14 STM-4 Optical Aggregate Unit 5-14 subrack backplane 13-5 TN-1X 3-3 TN-1X layout 3-4 Nortel TN-1X System Description

18

18-4 Index

TN-1X/S 3-3 TN-1X/S dimensions 4-2 TN-1X/S layout 3-5 weight 4-2 Subrack Controller 6-3 switching manual tributary protection 10-18 multiplexer section protection 10-9 path protection 10-1 Payload Manager 10-7 synchronisation 7-4 synchronisation 7-1 alarms 7-12 external output 7-12 source hierarchy 7-2 sources 7-1 failure 7-11 switching 7-4 synchronisation source messaging 7-4 synchronous digital hierarchy administrative unit 15-3 administrative unit group 15-3 container 15-2 multiplexing structure 15-2 STM-1 15-3 STM-N 15-4 tributary unit 15-3 tributary unit group 15-3 virtual container 15-2 system configurations 2-1 drop and insert multiplexer 2-3 STM-1 tributaries 2-7 STM-4 aggregates 2-5 terminal multiplexer 2-3 system interfaces 2 Mbit/s traffic 4-3 34 Mbit/s traffic 4-3 45 Mbit/s traffic 4-4 Engineering Order Wire 4-7 external alarms 4-7 external synchronisation 4-7 local terminal 4-6 network management 4-6 rack alarm bus 4-6 STM-1 electrical aggregate 4-5 STM-1 electrical tributary 4-5 STM-1 optical aggregate (long haul 1310 nm) 4-4 STM-1 optical aggregate (long haul 1550 nm) 4-4 323-1061-100

Release 9

Standard

STM-1 optical aggregate (short haul 1310 nm) 4-5 STM-1 optical aggregate (short haul) 4-4 STM-1 optical tributary (long haul 1310 nm) 4-4 STM-1 optical tributary (long haul 1550 nm) 4-4 STM-1 optical tributary (short haul 1310 nm) 4-5 STM-1 optical tributary (short haul) 4-4 STM-4 optical aggregate (intra-office 1310 nm) 4-6 STM-4 optical aggregate (long haul 1310 nm) 4-5 STM-4 optical aggregate (long haul 1550 nm) 4-6

T terminal multiplexer 2-3 thermal qualifications 4-8 third-party routers 6-19 traffic connections 9-5, 9-10 internal connections 9-6 user labels 9-12 Traffic Interface Module (TIM), see Interface Modules traffic processing 5-4 tributaries 1-1

U unit duplication Payload Managers 10-7 upgrade software 6-9 user interface 1-3 user labels 9-12

V variants 3-5 VC-12 path overhead 15-10 VC-12/VC-3 path protection switching 10-1 VC-3/VC-4 path overhead 15-11

W weight 4-2

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 and Unified Networks are trademarks of Nortel Networks.

Netscape and Navigator are trademarks of Netscape Communications Corporation. Hewlett-Packard is a trademark of Hewlett-Packard Company.

SDH TRANSMISSION

Nortel TN-1X System Description Copyright  1995 – 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 it only to its employees with a need to know, and shall protect it, 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-1061-100 Product Release Number: 9 Document Status: Standard Date: July 2001 Printed in England