SDH Planning and Ordering Guide R6.0

NTRR11DG
Nortel Networks
OPTera Connect DX
optical switch
SDH Planning and Ordering Guide
Standard Rel 6 Issue 2 November 2005
What’s inside...
Introduction
New feature content
Upgrade considerations and planning
Network configuration architecture
Software feature description
Hardware feature description
Optical layer OAM&P
Technical specifications
Ordering information
Technical assistance information
A0546240
Copyright © 2000–2005 Nortel Networks, All Rights Reserved
The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in
writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose the information only to
its employees with a need to know, and shall protect the information, in whole or in part, from disclosure and dissemination to third
parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except
as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein.
Nortel Networks, the Nortel Networks logo, the Globemark, OPTera and Preside are trademarks of Nortel Networks.
SMF-LS is a trademark of Corning. Truewave is a trademark of Lucent Technologies Inc. UNIX is a trademark of X/Open Company
Ltd. Microsoft and Windows are registered trademarks of Microsoft Corporation in the United States and/or other countries.
ACE/Server, RSA, and SecurID are registered trademarks of RSA Security Inc.
Printed in Canada and in the United Kingdom

iii
Publication history 0
November 2005
Standard issue. Updates to Ordering Information.
April 2004
Standard issue.
SDH Planning and Ordering Guide Rel 6 Standard Nov 2005

iv Publication history
OPTera Connect DX optical switch Rel 6 Standard Nov 2005

v
Contents 0
About this document xi
Introduction 1-1
New feature content 2-1

Universal slots 2-22
Mixed configuration enhancements 2-29
Quad STM-16 T/R circuit pack 2-33
STM-16 LR T/R circuit pack 2-38
Dual Gigabit Ethernet ZX circuit pack 2-39
VC-4-64c support on STM-64 linear 1+1 and 4-Fiber MS-SPRing and Chain 2-40
DCC route diversity enhancement 2-43
Security administration through the TL1 interface 2-44
Hardware Baseline tool 2-50
OPC connection service enhancements 2-54
OPC Protection Manager enhancements 2-56
Test access enhancement 2-58
Miscellaneous features 2-61
Flexible default protection scheme enhancement 2-61
Synchronization Status Messaging enhancements 2-62
Strong authentication enhancements 2-64
Network and hardware reconfigurations 2-64
In-service hardware reconfigurations 2-64
In-service network reconfigurations 2-65
Upgrade considerations and planning 3-1

Software 3-1
Hardware 3-2
New hardware introduced in OPTera Connect DX Release 6.0 3-3
Interworking 3-3
Preside 3-3
OPTera Connect DX Release 6.0 interworking 3-5
OPC span of control rules 3-9
Network configuration architecture 4-1

Network configurations 4-1
4-Fiber network configurations and protection switching 4-3
2-Fiber Ring configurations and protection switching 4-14

vi Contents
10 Gbit/s unprotected configuration 4-18

10 Gbit/s Linear 1+1 configuration 4-20
Subtending sub-network connection protection ring 4-21
Subtending STM-16 2-Fiber multiplexer section shared protection rings 4-23
Tributary hairpinning application 4-32
Low-speed cross-connect application 4-35
Tributary circuit packs and protection schemes 4-35
Level 2 routing 4-36
Optical amplifier support 4-37
OPTera Connect DX interoperability 4-38
Interoperability versus interworking 4-38
Levels of interoperability 4-38
Automatic protection switching 4-39
SONET and SDH interoperability 4-40
Data communications channel (DCC) interoperability 4-40
Compliance to Industry Standards 4-40
OSI addresses and area addresses 4-41
Provisioning OSI stack parameters 4-41
Enabling the DCC links 4-42
Secure DCC Feature 4-42
Software feature description 5-1

Shelf configuration 5-2
Traffic configuration 5-3
Section trace 5-4
Path trace 5-4
Signal label 5-4
Forward error correction 5-4
Triple forward error correction 5-4
Tributary facility mode 5-5
Dense wavelength division multiplexing 5-5
Multiwavelength optical repeater 5-6
Performance monitoring 5-6
Receive signal level threshold alarming 5-9
Facility protection switching 5-11
SNCP (path) protection switching 5-11
STM-16 2-Fiber MS-SPRing 5-11
Single 4-Fiber MS-SPRing protection switching 5-11
Single 2-Fiber MS-SPRing protection switching 5-12
Protection oscillation control 5-12
Head-end ring switching 5-13
Ring extra traffic 5-13
MS-switched matched nodes 5-13
Equipment protection switching 5-13
Equipment protection switch types and priorities 5-14
Synchronization 5-14
Timing generation 5-15
Timing distribution 5-16
Data communications 5-16
Head-end datacomm gateway 5-16
Ring extra traffic 5-17

Contents vii
Tributary hairpinning 5-17

Software management by release 5-17
Parameter provisioning 5-18
Parallel telemetry 5-19
System security 5-19
Alarms 5-20
Logs 5-21
DX_HUB network element 5-21
Flexible default protection scheme 5-21
Test access 5-22
Loopback (facility and connections) 5-26
Auto in-service 5-29
SDH overhead Orderwire 5-35
Low-speed cross-connection provisioning enhancements 5-40
TL1 interface 5-40
Preside 5-40
Hardware feature description 6-1

OPTera Connect DX network element bay 6-1
TN-64X network element bay 6-3
Control shelf 6-6
Termination panel 6-6
Power section 6-6
Control section 6-6
I/O section 6-6
Local craft access panel 6-8
RS-232 interface 6-8
Orderwire features 6-9
Other features 6-9
Optical fiber cable management 6-10
Fiber management hardware kit 6-11
Main transport shelf 6-16
Tributary circuit packs for any configuration 6-18
STM-16 circuit pack network configurations 6-20
Environmental control panels 6-24
Extension shelf 6-25
Transport interfaces 6-26
OPTera Connect DX 6-26
TN-64X 6-26
OPTera Connect DX switch modules 6-26
Quad STM-1o/e T/R tributary circuit pack 6-27
HD STM-1o/e T/R tributary circuit pack 6-28
Half-height STM-4 or Quad STM-4 T/R tributary circuit packs 6-29
STM-16, Dual STM-16 or Quad STM-16 tributary circuit packs 6-30
Dual Gigabit Ethernet tributary circuit packs 6-31
Filler cards 6-32
Mandatory control shelf circuit packs 6-34
Breaker/filter module 6-34
Shelf controller 6-37
External synchronization interface 6-37
Maintenance interface 6-38

viii Contents
Message exchange 6-38

Optional control shelf circuit packs 6-38
OPC controller circuit pack 6-38
OPC storage circuit pack 6-39
Removable media 6-39
OPC interface 6-39
Message exchange (protection) 6-39
Parallel telemetry 6-39
Orderwire 6-39
Optical layer OAM&P 7-1

Software and provisioning enhancements 7-1
Channel autodiscovery 7-1
Channel provisioning propagation 7-2
Output power propagation 7-2
Operational enhancements 7-3
Technical specifications 8-1

Safety specifications 8-1
Laser emission 8-1
Site engineering 8-2
Maximum unshielded twisted pair cable length for Ethernet connection 8-3
Maximum cable length for Quad STM-1e cables 8-3
Maximum cable length for HD STM-1e cables 8-3
Mechanical specifications 8-3
Frame equipment 8-5
Floor loading 8-5
Circuit pack characteristics 8-5
Thermal loading 8-7
Power requirements 8-8
Input power specifications 8-8
Voltage transients 8-9
Conducted noise on DC power leads 8-9
Safety requirements for power converters 8-10
Power distribution 8-10
Power installation requirements 8-11
Grounding and isolation 8-15
Environmental specifications 8-15
Operational environment 8-15
Storage and transportation environment 8-17
Altitude 8-18
Atmospheric Dust 8-19
Mechanical shock and vibration 8-19
Electromagnetic compatibility 8-20
Emissions 8-20
Susceptibility 8-21
Electrostatic discharge 8-21
Network synchronization 8-22
External synchronization interface internal clock specifications 8-23
DS1 timing interface specifications 8-23

Contents ix
2 MHz timing interface specifications 8-25

2 Mbit/s timing interface specifications 8-25
Building-integrated timing supply 8-26
Network element synchronization modes 8-26
ESI modes of operation 8-30
Timing generation 8-31
Timing distribution 8-32
Parallel telemetry output relay 8-33
OPC definition 8-33
Partitioned OPC 8-33
Communication between the OPC and other network elements through optical
fiber 8-34
Communication between the OPC and independent networks through an Ethernet
DCC bridge 8-36
Location of the partitioned OPC in a network 8-37
Optical interface specifications 8-37
Rates and format specifications 8-38
Interface specifications 8-39
HD STM-1o T/R, Quad STM-1o T/R and Quad STM-4 interface
specifications 8-39
Quad STM-16, Dual STM-16 and STM-16 tributary T/R interface
specifications 8-41
Dual Gigabit Ethernet tributary T/R interface specifications 8-44
STM-64 10G T/R interface specifications 8-46
Optical link budgets 8-48
Dispersion sign 8-48
Optical link budgets 8-49
Single span link budgets 8-50
Ordering information 9-1

Introduction 9-1
Network element 9-1
List of procedures
9-1 Selecting a set of OPTera Connect DX equipment 9-3
OPTera Connect DX bay 9-13
Control shelf 9-13
Main transport shelf 9-13
Extension shelf 9-14
Bay equipment 9-22
STM-64 T/R interface circuit packs 9-28
STM-64 T/R short, intermediate and long reach interface circuit packs 9-40
Switch modules 9-40
Tributary circuit packs 9-43
Filler cards 9-48
Optical connector adapter kits 9-49
Common equipment circuit packs 9-49
Cables 9-52
HD STM-1o optical fiber cable assemblies 9-58
Quad STM-1e coaxial cables 9-62
HD STM-1e coaxial cable assembly 9-63

x Contents
Optical fiber cables for the Dual GE short reach circuit packs 9-65
Peripheral cables 9-67
Software 9-69
Software loads 9-69
Software licenses and certificates 9-71
Documentation 9-72
NTP libraries 9-73
Supporting documentation 9-77
Models 9-82
Technical assistance information 10-1

Nortel web site 10-1

xi
About this document 0

This planning guide describes the applications and functionality provided by
the software and hardware of Nortel OPTera Connect DX optical switch
Release 6.0 (referred to as OPTera Connect DX in this document) network
element.
This planning guide covers the following topics:

• Introduction to OPTera Connect DX Release 6.0
• New feature content
• Upgrade considerations and planning
• Network configuration architecture
• Software feature description
• Hardware feature description
• Optical layer OAM&P
• Technical specifications
• Ordering information
• Technical assistance information
Audience
This document is for the following members of the operating company:
• strategic and current network planners
• provisioners
• transmission and standards engineers
• network administrators
• system lineup and testing (SLAT) personnel

xii About this document
OPTera Connect DX SDH NTP Library

Installing, Managing and Maintaining and Supporting
Planning a Commissioning and documentation for
Provisioning Troubleshooting
Network Testing a Network the OPTera
a Network a Network
Connect DX SDH
Library
Change Application
Procedures
(CAPs)
OC-48 DWDM
Tributary Application
Note
(NTRR12AC)
OPTera Long Haul

User Interface Performance 1600 NTP Library
About the OPTera SDH Network
Connect DX Element Deployment Connection Procedures Monitoring Procedures
SDH NTP Guide (323-1531-301) (323-1531-520)
OPTera Metro 4100
Library (NTCA67DG) NTP Library
(323-1531-090) External Interface Trouble Clearing and
Installation Configuration Module Replacement
Procedures Procedures (323-1531-543) OPTera Metro 4200
OPTera Connect DX (323-1531-302) NTP Library
SDH Planning and (323-1531-201)
Ordering Guide Software Log Reference
(NTRR11DG) Powering up and (323-1531-840) OPTera Metro
Administration Connect SDH
Commissioning Procedures
Procedures User Guide
SDH Orderwire (323-1531-303) (NTCA69YA)
User Guide (323-1531-220)
(NTCA66DA) Data Administration
System Procedures Optical Networks
Network Commissioning and (323-1531-304) Applications Library
Interworking Guide Testing Procedures
(NTCA68CA) (323-1531-222) Security Management
Procedures Preside
Network (323-1531-305) documentation
Interoperability Guide
(NTCA68CB) Provisioning and
Operations Procedures TN-1X NTP Library
Data Communications (323-1531-310)
Network Planning
Protection
Guide
Switching Description TN-4X NTP Library
(NTR710AM)
and Procedures
(323-1531-311)
Gigabit Ethernet
Data User Guide
TN-16X NTP Library
(NTCA65YA)
Circuit
Pack Descriptions
(323-1531-102)
TL1 Interface
Description
(323-1531-190)
NE User Interface
Description
(323-1531-195)
OPC User Interface

Description
(323-1531-196)

About this document xiii
References
This document refers to the following Nortel technical publications (NTP) that
are specific to the OPTera Connect DX NTP Library:
• SDH Orderwire User Guide, NTCA66DA
• Circuit Pack Descriptions, 323-1531-102
• TL1 Interface Description, 323-1531-190
• System Commissioning and Testing Procedures,323-1531-222
• External Interface Configuration Procedures, 323-1531-302
• Software Administration Procedures,323-1531-303
• Security Management Procedures, 323-1531-305
• Provisioning and Operations Procedures Part 1, 323-1531-310
• Protection Switching Description and Procedures Part 1, 323-1531-311
• Protection Switching Description and Procedures Part 2, 323-1531-311
• Performance Monitoring Procedures, 323-1531-520
• Trouble Clearing and Module Replacement Part 1, 323-1531-543
• Log Reference, 323-1531-840
This document refers to the following supporting documentation:
• OPTera Metro Connect SDH User Guide, NTCA69YA
• Optical Networks Data Communications Planning Guide, NTR710AM
• OC-48 DWDM Tributary Application Note, NTRR12AC (OC 99-176)
• OPTera Long Haul 1600G Amplifier Network Application Guide,
NTY314AF
• OPTera Long Haul 1600G Amplifier Optical Layer Application Guide,
NTY315DX
• MOR Optical Layer OAM&P, 323-1251-100
• Optical Networks Applications Library, NTCA66BA
• Preside NTP Library, 450-3101-XXX
• Preside Applications Platform 10.1 Planning Guide, 450-3101-601
• Preside Trail Management 5.0 Planning Guide, 450-3101-608
• Preside Backup and Restore 2.1 Planning Guide, 450-3101-637

xiv About this document
• Preside Optical Power Management 4.0 Planning Guide, 450-3101-633

• Preside Optical Sections View 6.0 Planning Guide, 450-3101-632
• Preside DWDM View 2.0 Planning Guide, 450-3101-646
• Preside Software Upgrade Manager 3.0 Planning Guide, 450-3101-635
• Preside Optical Connection Manager 2.0 Planning Guide, 450-3101-628

1-1
Introduction 1-
This chapter provides an introduction to the OPTera Connect DX Release 6.0
product.
OPTera Connect DX Release 6.0 has superior feature content compared to

previous OPTera Connect DX Releases. The OPTera Connect DX Release 6.0
software supports the SDH DX platform and continues to support TN-64X .
Note: Starting in Release 6, the TN-64X platform is no longer supported

in the NTP Library. As a result, all OPTera Connect DX NTPs now use the
NTP number 323-1531-xxx for one single (DX) platform. For
documentation on the TN-64X platform, refer to the OPTera Connect DX
Release 5 (or earlier) NTP library.
OPTera Connect DX Release 6.0 has many advantages, including:

• Universal slots: The universal slots feature allows the flexibility of
equipping the universal slots with STM-64 circuit packs or certain
tributary circuit packs. The supported tributary circuit packs in the
universal slots are the HD STM-1, Dual STM-16, Quad STM-16 or Dual
Gigabit Ethernet circuit packs. Therefore, the universal slots can increase
add/drop tributary capacity of the OPTera Connect DX network element.
• Capacity: OPTera Connect DX network elements terminate up to
60 Gbit/s of unprotected tributary bandwidth in the tributary circuit pack
slots, which can be fed as input to the high-speed (10 Gbit/s) transport
sides or hair-pinned into other tributaries. The OPTera Connect DX
network elements also terminate up to 80 Gbit/s of unprotected high-speed
traffic or tributary traffic in the universal slots , for an aggregate total
bandwidth of 140 Gbit/s.
• Grade of Service: OPTera Connect DX allows the network provider to
distinguish and provide services of distinctly different grades, ranging
from protected services, triple forward error correction for superior bit
error rate performance to economical unprotected tributaries and ring extra
traffic services. OPTera Connect DX robust architecture enables
unparalleled network reliability and availability.

1-2 Introduction
• Networking: OPTera Connect DX Release 6.0 provides unmatched

functionality by combining add/drop multiplexer (ADM), linear,
unprotected and cross-connect functionalities on the same platform. The
OPTera Connect DX Release 6.0 supports numerous mixed 10 Gbit/s
configurations on the same network element. Inter-ring traffic can also be
protected via integrated matched nodes gateways.
• OPTera Connect DX Release 6.0 supports a mix of 10 Gbit/s
configurations on the same OPTera Connect DX network element. You can
provision up to eight 10 Gbit/s high-speed interfaces in the universal slots
to support the following mixed configurations:
— Nx4-Fiber Ring (N is 1 or 2)
— mixed Px4-Fiber Ring and Nx2-Fiber Ring [where P is 0 to 2 and
N = (8 - (4xP))/2]
— mixed Px4-Fiber Ring and Linear Mx(1+1) [where P is 0 to 2 and
M = (8 - (4xP))/2]
— mixed Px4-Fiber Ring and Mx(0:1) [where P is 0 to 2 and
M = 8 - (4xP)]
— mixed Px4-Fiber Ring, Nx2-Fiber Ring, Linear Mx(1+1) and Kx(0:1)
[where P is 0 to 2, N is 0 to 4, M is 0 to 4 and K = 8 - [(Px4)+2x(N+M)]]
— Nx2-Fiber Ring (N is 1 to 4)
— mixed Nx2-Fiber Ring and Mx(0:1) [where N is 0 to 4 and
M = 8 - (2xN)]
— mixed Nx2-Fiber Ring and Linear Mx(1+1) [where N is 0 to 4 and
M = (8 - (2xN))/2]
— mixed Nx2-Fiber Ring, Linear Mx(1+1) and Kx(0:1) [where N is 0 to
4, M is 0 to 4 and K = 8 - 2x(N+M)]
— Linear Nx(1+1) (where N is 1 to 4)
— mixed Linear Nx(1+1) and Mx(0:1) [where N is 0 to 4 and
M = 8-(2xN)]
— Nx(0:1) (where N is 1 to 8)
— On the tributary side, the OPTera Connect DX bay supports:
– subtending linear (1+1) configurations
– unprotected (0:1) configurations
– matched nodes (1*1) configurations
– subtending sub-network connection protection (SNCP) ring
configurations
– subtending STM-16 2-Fiber MS-SPRing configurations

Introduction 1-3
• Operations: OPTera Connect DX supports end-to-end provisioning,

maintenance and administration of services, using industry standard
operations and protocols.
• Service Flexibility: OPTera Connect DX supports concatenated and
non-concatenated services on:
— STM-16 tributaries
— Gigabit Ethernet tributaries
• OPTera Connect DX provides full bandwidth management at the VC-4
granularity. Concatenated connections are at VC-4, VC-4-2c, VC-4-4c,
VC-4-8c , VC-4-16c and VC-4-64c rates.
• When the OPTera Metro Connect bay is equipped with OPTera Metro
(OM) 4100/4200 network element, the network element provides E1 and
E3 services.
• Nodal efficiencies and network savings: OPTera Connect DX supports
subtending STM-16 2-Fiber MS-SPRing and SNCP Ring nodes on its
tributaries. Therefore, back-to-back tributary connections to subtending
head-end ring nodes are no longer required. These features allow
optimization and simplification of the Central Office which translates into
lower capital expenditure (CAPEX) by decreasing footprint and
equipment requirements and into lower operating expenditure (OPEX) by
reducing the number of nodes, real estate and power requirements.
• Seamless non-blocking scalability: OPTera Connect DX modular
architecture allows you to scale your requirements, starting small and
growing as required. This provides optimization of initial deployment cost.
The OPTera Connect DX product conforms with the following industry
standards:
• Telcordia (formerly known as Bellcore)
• Network Equipment Building System (NEBS)
• European Telecommunications Standards Institute (ETSI)
• American National Standards Institute (ANSI)
• International Telecommunications Union-Telecommunications
Standardization Bureau (ITU-T)
• Underwriters’ Laboratories (UL)
• Canadian Standards Association (CSA)
• International Organization for Standardization (ISO)

1-4 Introduction
Nortel is actively involved in various forums and standard bodies to ensure

that current and new products conform with the directions and evolution of the
telecommunications industry.
Figure 1-1 on page 1-5 shows a front-view diagram of the OPTera Connect DX
bay with extension shelf.

Introduction 1-5
Figure 1-1
Front view of the OPTera Connect DX bay with extension shelf
DX3203p

1-6 Introduction

2-1
New feature content 2-

This chapter provides an overview of the applications and functionality
provided by OPTera Connect DX Release 6.0 software and hardware. The
functionality includes all features offered from previous SDH releases and the
following new features:
• Universal slots
• Mixed configuration enhancements
• Quad STM-16 T/R circuit pack
• STM-16 LR T/R circuit pack
• Dual Gigabit Ethernet ZX circuit pack
• VC-4-64c support on STM-64 linear 1+1 and 4-Fiber MS-SPRing and
Chain
• DCC route diversity enhancement
• Security administration through the TL1 interface
• Hardware Baseline tool
• OPC connection service enhancements
• OPC Protection Manager enhancements
• Test access enhancement
• Miscellaneous features
• Network and hardware reconfigurations

2-2 New feature content
Table 2-1 on page 2-2 lists the features available in OPTera Connect DX
Releases 4, 4.1, 5 and 6.
Table 2-1
Summary of features for previous and current OPTera Connect DX releases
OPTera Connect OPTera Connect OPTera Connect OPTera Connect

DX Release 4.0 DX Release 4.1 DX Release 5.0 DX Release 6.0
Security
System security Yes Yes Yes Yes
Secure DCC and TCP/IP Yes Yes Yes Yes

access control
Strong User Yes Yes Yes Yes

Authentication
Bay configuration
Control Shelf Yes Yes Yes Yes
Line extension shelf TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
Low-speed port extension DX bay only DX bay only DX bay only DX bay only
shelf
Total number of shelves • TN-64X bay: 3 • TN-64X bay: 3 • TN-64X bay: 3 • TN-64X bay: 3
per bay • DX bay: up to 3 • DX bay: up to 3 • DX bay: up to 3 • DX bay: up to 3
Total number of tributary • TN-64X bay: up • TN-64X bay: up • TN-64X bay: up • TN-64X bay: up
circuit pack slots to 8 to 8 to 8 to 8
• DX bay: up to 16 • DX bay: up to 16 • DX bay: up to 16 • DX bay: up to 8
with DX100 or with DX65
DX140 • DX bay: up to 20
with DX100
• DX bay: up to 24
with DX140
Total number of STM-64 • TN-64X bay: up • TN-64X bay: up • TN-64X bay: up • TN-64X bay: up
line circuit pack slots to 4 to 4 to 4 to 4
• DX bay: up to 8 • DX bay: up to 8 • DX bay: up to 8 • DX bay: up to 8
Network element types
Single 2-Fiber ADM DX bay only DX bay only DX bay only DX bay only
Single 4-Fiber ADM Yes Yes TN-64X bay only TN-64X bay only
Nx2-Fiber ADM DX bay only DX bay only DX bay only DX bay only
2x4-Fiber ADM DX bay only DX bay only DX bay only DX bay only
Regenerator (Regen) TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
Dense Regen TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only

Table 2-1 (continued)


Unprotected hub DX bay only DX bay only - -

(See Note 1) (See Note 1)
DX_HUB No No DX bay only DX bay only
Network configuration and architecture
Single 10 Gbit/s Linear No No Yes Yes

1+1 terminal
Single 4-Fiber ADM chain Yes Yes Yes Yes
Single 4-Fiber Yes Yes Yes Yes

MS-SPRing
Single 4-Fiber HERS DX bay only DX bay only DX bay only DX bay only
2x4-Fiber single or mixed DX bay only DX bay only DX bay only DX bay only
network configuration of
MS-SPRing, HERS, and
ADM chain
Single 2-Fiber DX bay only DX bay only DX bay only DX bay only
MS-SPRing
Nx2-Fiber mixed network DX bay only DX bay only DX bay only DX bay only
configuration of
MS-SPRing and HERS
(where N is 1, 2, 3 or 4)
Unprotected hub DX bay only DX bay only - -

(See Note 1) (See Note 1)
10 Gbit/s Linear Nx(1+1) No No DX bay only DX bay only

terminals (where N is 1, 2,
3 or 4)
10 Gbit/s unprotected No No DX bay only DX bay only

terminals (where N is 1 to
8)
Mix 10 Gbit/s No No DX bay only DX bay only

configurations on the
same network element
MS-switched matched Yes Yes Yes Yes

nodes
4-Fiber Ring extra traffic Yes Yes Yes Yes



2-Fiber Ring extra traffic DX bay only DX bay only DX bay only DX bay only
Hairpinning Yes Yes Yes Yes
Universal slots No No No DX bay only
Subtending SNCP ring DX bay only, DX bay only, DX bay only DX bay only
except except
unprotected hub unprotected hub
Subtending STM-16 No No DX bay only DX bay only

2-Fiber MS-SPRing
Low-speed cross-connect DX bay only DX bay only DX bay only DX bay only
OPTera Metro Connect DX bay only DX bay only DX bay only DX bay only
Data communications
Telnet access to the NE Yes Yes Yes Yes

by way of TCP/IP
Level 2 routing Yes Yes Yes Yes
Synchronization
Synchronization status Yes Yes Yes Yes

messaging (SSM)
Bandwidth management and traffic configuration
Switching capacity • TN-64X bay: • TN-64X bay: • TN-64X bay: • TN-64X bay:
60 Gbit/s 60 Gbit/s 60 Gbit/s 60 Gbit/s
• DX bay: 60 Gbit/s • DX bay: 60 Gbit/s • DX bay: 60 Gbit/s • DX bay: 60 Gbit/s
(384 VC-4s) with (384 VC-4s) with (384 VC-4s) with (384 VC-4s) with
DX65 switch DX65 switch DX65 switch DX65 switch
module module module module
• DX bay: 80 Gbit/s • DX bay: • DX bay: • DX bay:
(512 VC-4s) with 100 Gbit/s (640 100 Gbit/s (640 100 Gbit/s (640
DX100 switch VC-4s) with VC-4s) with VC-4s) with
module DX100 switch DX100 switch DX100 switch
• DX bay: module module module
120 Gbit/s (768 • DX bay: • DX bay: • DX bay:
VC-4s) with 140 Gbit/s (896 140 Gbit/s (896 140 Gbit/s (896
DX140 switch VC-4s) with VC-4s) with VC-4s) with
module DX140 switch DX140 switch DX140 switch
module module module
VC-4 TSA bandwidth Yes Yes Yes Yes

management



Payload supported at the Yes Yes Yes Yes

tributary level (VC-4,
VC-4-4, and VC-4-16)
VC-4, VC-4-4c, and Yes (Automatic Yes (Automatic Yes (Automatic Yes (Automatic
VC-4-16c concatenated connection connection connection connection
payload support provisioning provisioning provisioning provisioning
through software) through software) through software) through software)
VC-4-2c and VC-4-8c No Yes Yes Yes

concatenated payload
support
VC-4-64c concatenated DX bay only DX bay only DX bay only DX bay only
payload support (configured only (configured only (supported on (supported on
as an as an STM-64 STM-64 linear
unprotected hub unprotected hub unprotected 1+1, 4-Fiber
network element) network element) interfaces) Ring/Chain or
unprotected
interfaces)
Gigabit Ethernet support Yes Yes Yes Yes

(VC-4, VC-4-2c, VC-4-4c
and VC-4-8c)
Protected tributary port • TN-64X bay: • TN-64X bay: • TN-64X bay: • TN-64X bay:
capability (speeds of 10 Gbit/s 10 Gbit/s 10 Gbit/s 10 Gbit/s
STM-16 or less) • DX bay: 20 Gbit/s • DX bay: 30 Gbit/s • DX bay: 30 Gbit/s • DX bay: 70 Gbit/s
Unprotected tributary port • TN-64X bay: • TN-64X bay: • TN-64X bay: • TN-64X bay:
capability (speeds of 20 Gbit/s 20 Gbit/s 20 Gbit/s 20 Gbit/s
STM-16 or less) • DX bay: 40 Gbit/s • DX bay: 60 Gbit/s • DX bay: 60 Gbit/s • DX bay:
140 Gbit/s
STM-64 line capability • TN-64X bay: • TN-64X bay: • TN-64X bay: • TN-64X bay:
20 Gbit/s T/R 20 Gbit/s T/R 20 Gbit/s T/R 20 Gbit/s T/R
protected or protected or protected or protected or
40 Gbit/s 40 Gbit/s 40 Gbit/s 40 Gbit/s
protected with protected with protected with protected with
extra traffic extra traffic extra traffic extra traffic
• DX bay: 40 Gbit/s • DX bay: 40 Gbit/s • DX bay: 40 Gbit/s • DX bay: 40 Gbit/s
protected or protected or protected or protected or
80 Gbit/s on 80 Gbit/s on 80 Gbit/s on 80 Gbit/s on
unprotected hub unprotected hub unprotected unprotected
configuration or configuration or 10 Gbit/s 10 Gbit/s
extra traffic extra traffic terminals or extra terminals or extra
traffic traffic



STM-64 line transmitter, receiver and optical features
DWDM transmitter (Tx) TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
AM1 dithering (for MOR
and MOR Plus)
DWDM AM1 T/R dithering Yes Yes Yes Yes

(for MOR and MOR Plus)
DWDM AM2 T/R dithering DX bay only DX bay only DX bay only DX bay only
(for MOR, MOR Plus, and
OPTera Long Haul
1600G amplifier)
DWDM forward error Yes Yes Yes Yes

correction (FEC)
DWDM triple forward DX bay only DX bay only DX bay only DX bay only
error correction (TriFEC)
Non-DWDM short reach DX bay only DX bay only DX bay only DX bay only
T/R
Non-DWDM intermediate No DX bay only DX bay only DX bay only

reach T/R
Non-DWDM long reach DX bay only DX bay only DX bay only DX bay only
T/R
Chromatic dispersion Yes Yes Yes Yes

compensator with
dispersion compensation
module (DCM)
Mixed tributary configurations (circuit packs)
Quad STM-1o/e Yes Yes Yes Yes

1 RS DCC and 1 MS DCC
channels
Quad STM-1o/e No No Yes Yes

channels
HD STM-1o DX bay only, DX bay only, DX bay only, DX bay only,

0 DCC channel equipped with equipped with equipped with equipped with
DX100 or DX140 DX100 or DX140 DX100 or DX140 DX100 or DX140
switch modules switch modules switch modules switch modules



HD STM-1o/e No DX bay only, DX bay only, DX bay only,

16 RS DCC channels equipped with equipped with equipped with
DX100 or DX140 DX100 or DX140 DX100 or DX140
switch modules switch modules switch modules
HH STM-4 TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
Quad STM-4 Yes Yes Yes Yes

channels
Quad STM-4 No Yes Yes Yes

channels
STM-16 short reach (SR) Yes Yes Yes Yes
STM-16 long reach (LR) Yes Yes Yes Yes
STM-16 DWDM Yes Yes Yes Yes
Dual STM-16 short reach No DX bay only, DX bay only, DX bay only,
(SR) equipped with equipped with equipped with
Dual STM-16 No DX bay only, DX bay only, DX bay only,

intermediate reach (IR) equipped with equipped with equipped with
Dual STM-16 long reach No No DX bay only, DX bay only,

(LR) equipped with equipped with
DX100 or DX140 DX100 or DX140
switch modules switch modules
Quad STM-16 SR No No No DX bay only,

equipped with
DX100 or DX140
switch modules
Quad STM-16 IR No No No DX bay only,

equipped with
DX100 or DX140
switch modules
Dual Gigabit Ethernet No Yes Yes Yes

(GE) long reach (LX)



Dual Gigabit Ethernet No No Yes Yes

(GE) short reach (SX)
Dual Gigabit Ethernet No No Yes Yes

(GE) extended reach (ZX)
Transmitter and Receiver circuit packs
STM-64 DWDM TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
TxDemux/Rx (AM1)
STM-64 XR on Regens TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
STM-64 merged XR/WT TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
on Regens
STM-64 DWDM T/R (AM1 DX bay only DX bay only DX bay only DX bay only
and AM2)
STM-64 Short Reach T/R DX bay only DX bay only DX bay only DX bay only
STM-64 Intermediate No DX bay only DX bay only DX bay only

Reach T/R
STM-64 long reach T/R DX bay only DX bay only DX bay only DX bay only
with APD and TriFEC
Switch modules
DOS switch module TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
DX65 switch module DX bay only DX bay only DX bay only DX bay only
Control shelf circuit packs
16 Mbyte Shelf Controller TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
(supported on Regens
only)
32 Mbyte Shelf Controller Yes Yes Yes Yes
32 Mbyte maintenance TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
interface (supported for
upgrades)



128 Mbyte maintenance Yes Yes Yes Yes

interface (required on
TN-64X if commissioning
the bay)
68 Mbyte removable Yes Yes Yes Yes

media for the OPC
(supported for OPC
backup operations only)
122 Mbyte removable Yes Yes Yes Yes

media for the OPC
OPC/SSD OPC Yes Yes Yes Yes
1.5 Mbit/s ESI circuit pack Yes Yes Yes Yes
2.0 MHz ESI circuit pack Yes Yes Yes Yes
2 Mbit/s / 2.0 MHz ESI No No Yes Yes

circuit pack
Orderwire TN-64X bay only TN-64X bay only Yes Yes
MOR and MOR Plus TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
Parallel Telemetry Yes Yes Yes Yes
Protection switching
1+1 tributary protection Yes Yes Yes Yes
Revertive and Yes Yes Yes Yes

nonrevertive protection
selection for tributaries
Unidirectional and Yes Yes Yes Yes

bidirectional protection
selection for tributaries
MS-switched matched Yes Yes Yes Yes

nodes (1*1 for primary
gateway tributaries and, if
required, 1+1 for
secondary gateway)
Provisionable span Yes Yes Yes Yes

wait-to-restore (WTR)
period and ring WTR
period



Default protection No No DX bay only DX bay only

scheme provisioning for
tributary and line
interfaces
Extended WTR switch Yes Yes Yes Yes

oscillation control for
tributaries only
(provisionable on or off)
Automatic updating of Yes Yes Yes Yes

ring protection squelch
tables
Ring protection exerciser Yes Yes Yes Yes
Enable/disable tributary Yes Yes Yes Yes

exerciser on a facility
group basis
4-Fiber Multiplexer Yes Yes Yes Yes

section shared protection
ring (MS-SPRing)
2-Fiber MS-SPRing DX bay only DX bay only DX bay only DX bay only
2-fiber and 4-Fiber DX bay only DX bay only DX bay only DX bay only
Head-end ring switching
(HERS)
STM-64 Linear 1+1 No No DX bay only DX bay only
Sub-network connection DX bay only DX bay only DX bay only DX bay only
protection (SNCP) ring
STM-16 2-Fiber No No DX bay only DX bay only

MS-SPRing
Performance monitoring (PM)
PM support for Yes Yes Yes Yes

concatenated payloads
PM support for tributaries Yes Yes except for Yes except for Yes except for
GE tributaries GE tributaries GE tributaries
PM support for STM-64 TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
Rx



PM support for 10 Gbit/s DX bay only DX bay only DX bay only DX bay only
STM-64 T/Rs
PM support for STM-64 TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
XRs circuit pack
(supported on Regens
only)
SDH PMs Yes Yes Yes Yes
Untimed PMs Yes Yes Yes Yes
Nodal interface
NE numbering to 65534 Yes Yes Yes Yes
Menu based UI (OPC and Yes Yes Yes Yes

NE UI)
NE UI dynamic protection Yes Yes Yes Yes

screens with scrolling
capability
NE UI ALL ports selector Yes Yes Yes Yes

commands
NE UI Add command Yes Yes Yes Yes
Alarming
OAM Security/Audit Trail Yes Yes Yes Yes

alarms
OPC Disk Robustness Yes Yes Yes Yes

alarms
OPC pointer alarms Yes Yes Yes Yes
MOR power optimization TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
alarms
SSM related alarms Yes Yes Yes Yes
Optical power receiver Yes Yes Yes Yes

signal level threshold
crossing alarms
OPC datacomm access Yes Yes Yes Yes

violation alarm



OPC TCP/IP access Yes Yes Yes Yes

violation alarm
OPC tools
Connection Manager Yes Yes Yes Yes
Commissioning Manager Yes Yes Yes Yes
Configuration Manager Yes Yes Yes Yes
Protection Manager Yes Yes Yes Yes
OAM Security/Audit Trail Yes Yes Yes Yes
Secondary State support Yes Yes Yes Yes

for circuit packs, circuit
pack groups, and facilities
9-character OPC name Yes Yes Yes Yes
24 ADM/DX_HUB nodes Yes Yes Yes Yes

per OPC span of control
(SOC) configured with
single 2-Fiber or 4-Fiber
ADM

per OPC SOC when one
or more ADM/DX_HUB is
configured with 2x4-Fiber
or Nx2-Fiber ADM (N > 1)

per OPC SOC for
unprotected hub
configuration (0:1)
24 nodes per OPC SOC No No Yes Yes

of DX_HUB NEs
configured with single
10 Gbit/s Linear 1+1
terminals only

of DX_HUB NEs
configured with single
Linear 1+1 and Nx(1+1)
terminals only (N is 1 to 4)




of DX_HUB NEs
configured with Nx2-Fiber
Rings and Mx(1+1)
terminals only
(M + N is 1 to 4)
8 nodes per OPC SOC of No No Yes Yes

DX_HUB NEs configured
with unprotected STM-64
ports (0:1) and Nx2-Fiber
Ring NE only (N = 1 to 3)

ports (0:1) and 1x4-Fiber
Rings only

ports (0:1) and Mx(1+1)
terminals only (M is 1 to 3)

ports (0:1), Nx2-Fiber
Ring ADM and Mx(1+1)
terminals only
(N+M is 1 to 3)
Autodiscovery and Yes Yes Yes Yes

connection adviser
support
In-service channel Yes Yes Yes Yes

rollover and in-service
route rollover
In-service tributary Yes Yes Yes Yes

rollover
OPC Connection DX bay, DX bay, DX bay, 10G DX bay,

Manager nodal unprotected hub unprotected hub unprotected 10G 4FR & chain,
connection support for only only terminal only 1+1 and 0:1
VC-4-64c



OPC Connection Yes Yes Yes Yes

Manager nodal
connection name
provisioning
OPC Connection No No No Yes

Manager connection edit
enhancements
OPC secure DCC Yes Yes Yes Yes

provisioning tool
OPC secure TCP/IP Yes Yes Yes Yes

provisioning tool
Consolidated OPC Yes Yes Yes Yes

banner line tool
Enhanced protection Yes Yes Yes Yes

exerciser (EPE) tool
SLAT and upgrades
65534 NE ID Yes Yes Yes Yes
20-character NE name Yes Yes Yes Yes
Strong authentication Yes Yes Yes Yes
Hardware baseline check Yes Yes Yes Yes

(during upgrade)
Hardware baseline tool No No No Yes
MOR support
MOR and MOR Plus TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
circuit packs
Optical service channel
Optical service channel TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
(OSC)
Orderwire
Orderwire over OSC TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
Open Access Orderwire TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
via OSC



SDH overhead Orderwire No No DX bay only DX bay only
Amplifier provisioning
MOR output power TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
propagation
MOR channel TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
provisioning propagation
Channel autodiscovery TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
System management
Operations controller Yes Yes Yes Yes

(OPC)
Consolidated OPC Yes Yes Yes Yes

banner line
TL1 support No No No No
OAM TL1 Gateway No No No No
TL1 connections No No No No
provisioning
Preside AP Release 10.1 Yes Yes Yes Yes
Preside Trail Yes Yes Yes Yes

Management Release 5.0
Preside Backup and Yes Yes Yes Yes

Restore Release 2.1
DWDM Management Yes Yes Yes Yes
Preside Optical Power Yes Yes Yes Yes

Management (OPM)
Release 4.0
Preside Optical Section Yes Yes Yes Yes

View (OSV) Release 6.0
DWDM View Release 2.0 Yes Yes Yes Yes
Optical Power Yes Yes Yes Yes

Management Release 4.0



Wavelength Path Yes Yes Yes Yes

Management (WPM) (See Note 2)
Release 4.0
Optical Manager No No No Yes

Release 2.1
Optical Connection Yes Yes Yes Yes

Manager (OCM) Release
2.0
Preside Software Yes Yes Yes Yes

Upgrade manager
(PSUM) Release 3.0
Auto in-service (AINS) No No Yes Yes
Troubleshooting tools
Test access - Monitor and No No DX bay only DX bay only

split (A/B)
Test access - Split (E/F) No No No DX bay only
Loopback (facility and No No DX bay only DX bay only

connections)
Supported upgrade and backout paths
From/to TN-64X No No No No
Release 1
From/to TN-64X No No No No
Release 2
From/to OPTera Connect No No No No

DX Release 1
From/to OPTera Connect No No No No

DX Release 2
From/to OPTera Connect Yes Yes Yes No

DX Release 3
From/to OPTera Connect N/A Yes Yes No

DX Release 4.0
From/to OPTera Connect N/A N/A Yes Yes

DX Release 4.1



From/to OPTera Connect N/A N/A N/A Yes

DX Release 5.0
Supported standard reconfiguration
Adding/deleting an ADM Yes Yes Yes Yes

node to/from a 4-Fiber
Ring
Adding/deleting an ADM DX bay only DX bay only DX bay only DX bay only
node to/from 2-Fiber Ring
Adding/deleting an ADM Yes Yes Yes Yes

node to/from 4-Fiber ADM
chain
4-Fiber ADM chain to/ Yes Yes Yes Yes

4-Fiber Ring conversion
Low-speed cross-connect No No DX bay only DX bay only

(LSXC) to 4-Fiber ADM
chain conversion
LSXC to 2-Fiber No No DX bay only DX bay only

MS-SPRing conversion
LSXC to 4-Fiber No No DX bay only DX bay only

MS-SPRing conversion
HH STM-4 tributary to TN-64X bay only TN-64X bay only No No

Quad STM-4 in-service
reconfiguration
STM-16 tributary to Quad Yes Yes No No

STM-4 in-service
reconfiguration
In-service switch module DX bay only DX bay only DX bay only DX bay only
upgrade (DX65 to DX100
or DX140, and DX100 to
DX140)
Quad STM-4 to STM-16 Yes Yes Yes No

card conversion
STM-16 to HD STM-1o DX bay only DX bay only DX bay only No

card conversion
Quad STM-4 to HD DX bay only DX bay only DX bay only No

STM-1o card conversion



Quad STM-1o to DX bay only DX bay only DX bay only DX bay only
HD STM-1o card
conversion
Quad STM-1e to DX bay only DX bay only DX bay only DX bay only
HD STM-1e card
conversion
STM-16 to Dual STM-16 No DX bay only DX bay only DX bay only

card conversion (See Note 3) (See Note 3) (See Note 3)
Adding/deleting DX NE No No No Yes
to/from a 2-Fiber TN-16X
and DX MS-SPRing Ring
Move an ADM to a new Yes Yes Yes Yes

OPC span of control
2 MHz to 2Mbit/s ESI No No Yes Yes

reconfiguration
1.5 Mbit/s to 2Mbit/s ESI No No Yes Yes

reconfiguration
Supported non-standard reconfiguration
In-service bay Yes Yes No Yes

replacement/Traffic
migration to a DX ADM
Collapsing of subtending Yes Yes Yes Yes

head-end SNCP ring
node into an OPTera
Connect DX ADM
In-service 2x4-Fiber bay Yes Yes Yes Yes

(hub) replacement



Collapsing of subtending No No Yes Yes

head-end 2-Fiber STM-16
MS-SPRing node into an
OPTera Connect DX
ADM
In-service rollover of a No No DX bay only DX bay only

2-Fiber STM-16
MS-SPRing to a 2-Fiber
STM-64 MS-SPRing
Note 1: The DX_HUB network element type replaces 4FR, 2FR and unprotected hub network element
types.
Note 2: This functionality has been merged with Preside Trail Management Release 5.0.
Note 3: OPTera Connect DX Release 4.1 supported conversions to Dual STM-16 (IR and SR)
interfaces. OPTera Connect DX Release 5.0 and 6.0 supports conversions to Dual STM-16 (IR, SR and
LR) interfaces.
Note 4: OPTera Connect HDX and OPTera Connect HDXc have been rebranded to Optical Cross
Connect HDX and Optical Cross Connect HDX respectively.
Table 2-2 on page 2-19 lists the features supported by each switch module.
Table 2-2
Switch modules and supported interfaces and features
TN-64X DX65 DX100 DX140

SW DOS
Switching capacity 60 Gbit/s 60 Gbit/s 100 Gbit/s 140 Gbit/s
Tributary port shelf 10 Gbit/s 10 Gbit/s • 30 Gbit/s without • 30 Gbit/s without

capability universal slots universal slots
(protected add/drop) • 50 Gbit/s with • 70 Gbit/s with
universal slots universal slots
Tributary port shelf 20 Gbit/s 20 Gbit/s • 60 Gbit/s without • 60 Gbit/s without

capability universal slots universal slots
(unprotected • 100 Gbit/s with • 140 Gbit/s with
add/drop) universal slots universal slots
STM-64 line 20 Gbit/s T/R • 20 Gbit/s T/R • 20 Gbit/s T/R • 40 Gbit/s T/R
capability protected protected protected protected
• 40 Gbit/s T/R • 40 Gbit/s T/R
• 80 Gbit/s T/R
unprotected unprotected
unprotected


TN-64X DX65 DX100 DX140

SW DOS
Single 4-Fiber ADM Yes Yes Yes Yes

chain
Single 4-Fiber Yes Yes Yes Yes

MS-SPRing
Single 4-Fiber HERS No Yes Yes Yes
2x4-Fiber mixed No No No Yes

network configuration
of MS-SPRing,
HERS, ADM Chain
Single 2-Fiber Ring No Yes Yes Yes
Nx2-Fiber mixed No Yes Yes Yes

of MS-SPRing, HERS
(where N is 1 or 2)
Nx2-Fiber mixed No No No Yes

of MS-SPRing, HERS
(where N is 3 or 4)
Unprotected hub (0:1) No Yes (see Note) Yes (see Note) Yes (see Note)
Dual GE Yes Yes Yes Yes
HD STM-1o/e No No Yes Yes
Dual STM-16 No No Yes Yes
Quad STM-16 No No Yes Yes
VC-4-64c No Yes Yes Yes

(See Note) (See Note) (See Note)
Universal slots No No Yes Yes


TN-64X DX65 DX100 DX140

SW DOS
Subtending SNCP No Yes Yes Yes

ring
Subtending STM-16 No Yes Yes Yes

2-Fiber MS-SPRing
Note: For OPTera Connect DX Release 6.0, the DX65, DX100 or DX140 switch modules support
VC-4-64c payload on STM-64 linear 1+1, 4-Fiber Ring or unprotected interfaces. OPTera Connect DX
Release 5.0 support VC-4-64c payload on STM-64 unprotected interfaces with the DX65, DX100 or
DX140 switch modules. OPTera Connect DX Release 4.0 and Release 4.1 supported VC-4-64c payload
on STM-64 unprotected interfaces which is supported on unprotected hub network element only. The
unprotected hub network element supports the DX140 switch modules only.

The following sections provide descriptions of the new and enhanced features
in OPTera Connect DX Release 6.0.
Universal slots
OPTera Connect DX Release 6.0 introduces the universal slots feature for the
OPTera Connect DX. This augments the flexibility of the OPTera Connect DX
network element by allowing non-10 Gbit/s interfaces to be placed in the 10
Gbit/s slots, maximizing the non-10 Gbit/s capacity of the network element.
The universal slots feature increases the overall bandwidth that can be
added/dropped on the OPTera Connect DX bay from 60 Gbit/s to 140 Gbit/s
(with DX140 switch card).
In previous OPTera Connect DX releases, only 10 Gbit/s (STM-64) circuit

packs were supported in the 10 Gbit/s circuit pack slots of the OPTera Connect
DX network element. The universal slots feature supports certain type of
non-10 Gbits circuit packs or 10 Gbit/s circuit packs in the 10 Gbit/s slots. The
10 Gbit/s slots (universal slots) are slots 1, 10, 11, 12, 13, 16, 17, and 18 of the
main transport shelf (see Figure 2-1 on page 2-24).
Note: The universal slots feature is not supported on OPTera Connect DX

network element equipped with DX65 switch modules. For this
configuration, the network element continues to support 10 Gbit/s circuit
packs only, in slots 12, 13, 16 or 17 of the main transport shelf.
When the 10 Gbit/s slots are not required for 10 Gbit/s circuit packs, you can
increase the add/drop traffic capacity of non-10 Gbit/s on the network element
by equipping the supported non-10 Gbit/s circuit packs in the 10 Gbit/s slots.
Table 2-3 on page 2-23 shows the number of service ports available on OPTera
Connect DX network element when equipped with various switch modules.

Table 2-3
Number of service ports available on the OPTera Connect DX
Service Ports Type Switch modules
DX140 DX100 DX65

(see Note)
STM-64 8 4 4
STM-16 56 40 16
STM-4 64 64 64
STM-1 256 256 256
Gigabit Ethernet (GE) 48 40 32
Note: The universal slots feature is not supported on OPTera Connect DX network
element equipped with DX65 switch modules.
You can populate the 10 Gbit/s slots with the STM-64 T/R, HD STM-1o/e,
Dual STM-16, Quad STM-16, or Dual Gigabit Ethernet (GE) circuit packs. As
in previous OPTera Connect DX releases, the equipping rules depend on the
type of switch modules:
• For DX100 switch modules, you can equip the 10 Gbit/s or non-10 Gbit/s
circuit pack in 10 Gbit/s slots 12 (G11), 13 (G12), 16 (G17), or 17 (G18).
• For DX140 switch modules, you can equip 10 Gbit/s or non-10 Gbit/s
circuit pack in 10 Gbit/s slots 1 (G0), 10 (G9), 11 (G10), 12 (G11), 13
(G12), 16 (G17), 17 (G18), or 18 (G19).
Note: An OPTera Connect DX network element supports a maximum of
16 HD STM-1o/e circuit packs. If this number is exceeded, a ‘CPG
provisioning limit exceeded’ alarm is raised against the last provisioned
HD STM-1 circuit pack(s).
The circuit packs supported in the 10 Gbit/s slots are shown in Table 2-4 on
page 2-23 for the various OPTera Connect DX switch modules.
Table 2-4
Supported 10 Gbit/s and non-10 Gbit/s circuit packs in 10 Gbit/s slots
Switch 10 Gbit/s Slot G-Numbers

Module
G0 G9 G10 G11 G12 G17 G18 G19
DX140 STM-64, HD STM-1o/e, Dual STM-16, Quad STM-16, Dual GE
DX100 STM-64, HD STM-1o/e, Dual STM-16, Quad

STM-16, Dual GE
DX65 STM-64

Figure 2-1
10 Gbit/s circuit pack 10 Gbit/s circuit pack

1
11
Filler card
G0
G10
slot (see note) slot (see note)
2
2
Non-10 Gbit/s circuit 10 Gbit/s circuit pack Non-10 Gbit/s circuit
12
G1
G11
G21
pack slot slot pack slot
OPTera Connect DX optical switch

Non-10 Gbit/s circuit Non-10 Gbit/s circuit
3
3
10 Gbit/s circuit pack
G12
G2
13
G22
circuit pack in this slot.

Non-10 Gbit/s circuit
4
4

G3
G23
pack slot DX100/DX140 pack slot
14
Switch module A
5
5
G4
G24
pack slot pack slot
Main shelf
6
6
G5
G25
pack slot DX100/DX140 pack slot
15
Extension shelf
Switch module B
7
7
G6
G26
pack slot pack slot
Rel 6 Standard Nov 2005

8
8

G7
16
G27
G17

9
9
G8

17
G18
G28
Note: The DX140 switch modules are required to support the

10 Gbit/s circuit pack 10 Gbit/s circuit pack
G9
Filler card
18
10
G19
slot (see note) slot (see note)

OPTera Connect DX network element showing the 10 Gbits/non-10 Gbits circuit pack slots
DX5358p
Protection switching mode

When compared to previous OPTera Connect DX releases, there is no change
to the protection switching modes for the 10 Gbit/s or non-10 Gbit/s interfaces
that are supported in the 10 Gbit/s slots. Table 2-5 on page 2-25 shows the
circuit packs and their protection switching modes.
Table 2-5
10 Gbit/s and non-10 Gbit/s circuit packs and their protection switching modes
Protection Mode STM-64 STM-16 STM-1 GE
Unprotected Yes Yes Yes Yes
1+1 Yes Yes Yes No
1*1 No Yes Yes No
2FR Yes Yes No No
4FR Yes No No No
SNCP No Yes No No
Note: For SNCP the interfaces are in unprotected mode.
As in previous releases, all service carrying circuit packs (except Dual GE) can
have protected or unprotected ports on a per-port basis. The following
protection pairing are supported on 10 GBit/s slots for all protection modes
except 4-Fiber MS-SPRing:
• G0 & G10 (with DX140 switch module)

• G9 & G19 (with DX140 switch module)
• G11 & G12 (with DX 100 and DX140 switch module)
• G17 & G18 (with DX 100 and DX140 switch module)
The protection pairing for 10GBit/s 4-Fiber MS-SPRing remains unchanged.
Traffic routing
Trafffic connections are supported between any traffic carrying circuit packs
in the OPTera Connect DX network element, including 10 Gbit/s or non-10
Gbit/s circuit packs in the 10 Gbit/s slots. The user can provision connections
from any circuit pack port to any circuit pack port from the OPC, TL1, OPTera
Connection Manager or Preside Trail Manager.
Network element user interface

The network element user interface was enhanced to support the non-10 Gbit/s
circuit packs in the 10 Gbit/s slots. The following network element user
interface menus were enhanced:
• Performance Monitoring Menu

— Facility Performance Menu (Facility Clear Counts Menu and Facility

Threshold Menu)
— Path Performance Menu (Path Clear Counts Menu and Path Threshold
Menu)
— Protection Performance Menu (Protection Clear Counts Menu)
— Facility Collection Menu
• Protection Menu
— Traffic Protection - Linear Menu
– LIST protection summary (all sub-menus)
— Traffic Protection - Four fiber ring Menu (all sub-menus)
— Traffic Protection - Two fiber ring Menu (all sub-menus)
— Traffic Protection - Path Menu (all sub-menus)
• Equipment Menu
— Circuit Pack Group Equipment Menu (CPG Alarm Provisioning
Menu)
• Facility Menu
— STMn Facility Menu ( Facility Alarm Provisioning Menu and Facility
Loopback Menu)
— DCC Control Menu
— Gigabit Ethernet Facility Menu
• Payload Menu
— Connection Loopback Menu
— Test Access Menu
OPC user interface
The OPC user interface was modified to support the non-10 Gibt/s circuit
packs in the 10 Gbit/s slots. The OPC Performance Monitoring sub-systems
was enhanced to support performance monitoring collection, threshold setting
and threshold retrieval for the non-10 Gbit/s circuit packs in the 10 Gbit/s slots.
In previous OPTera Connect DX releases, the OPC Protection Manager

supported the STM-64 circuit pack only. In OPTera Connect DX Release 6.0,
the OPC Protection Manager supports STM-16 2-Fiber MS-SPRing and the
STM-64 Linear 1+1, 2F and 4F MS-SPRing. Hence, if an OPTera Connect DX
network element does not have an STM-64 circuit pack but has an STM-16
2-Fiber MS-SPRing, the exerciser can be scheduled.

Note 1: If the OPTera Connect DX network element does not have either
an STM-64 Linear 1+1, 2F and 4F MS-SPRing or an STM-16 2-Fiber
MS-SPRing configurations, the OPC Protection Manager tool will not
open.
Note 2: If the OPTera Connect DX network element does not have either
an STM-64 Linear 1+1, 2F and 4F MS-SPRing or an STM-16 2-Fiber
MS-SPRing configurations, the exerciser cannot be scheduled. This is
because the Protection Manager does not know what configuration the
network element belongs to.
Network and hardware reconfigurations
OPTera Connect Release 6.0 supports hardware and network reconfigurations
for non-10 Gbit/s circuit packs in non-10 Gbit/s or 10 Gbit/s slots. For more
information, refer to Network and hardware reconfigurations on page 2-64 of
this chapter.
Alarms and Logs

A new “CPG provisioning limit exceeded” (mn, nsa) alarm is raised when
OPTera Connect DX bay is populated with more than 16 HD STM-1o circuit
packs.
This alarm is raised under the following scenarios:
• 15 STM-1o cards already provisioned and the protection default for

STM-1 facilities is set to 1+1.
– If one more HD STM-1o is inserted, the ‘CPG provisioning limit
exceeded’ alarm is raised against the slot and the card will have a
red led active.
– If two more HD STM-1o are inserted, the ‘CPG provisioning limit
exceeded’ alarm is raised twice, once against each slot, and both
cards will have a red leds active.
• 16 STM-1o cards already provisioned and the protection default for
STM-1 facilities is set to 1+1.
– If one more HD STM-1o is inserted, the ‘CPG provisioning limit
exceeded’ alarm is raised against the slot and the card will have a
red led active.
– If two more HD STM-1o are inserted, the ‘CPG provisioning limit
exceeded’ alarm is raised twice, once against each slot, and both
cards will have a red leds active.
• If the OPTera Connect DX bay was populated with more than 16 STM-1o
circuit packs prior to commissioning the network element.
A “Autoprovisioning Mismatch” (mn, nsa) alarm is raised if an unsupported
non-10 Gbit/s circuit packs is inserted in 10 Gbit/s slots.

Engineering rules and restrictions

The following engineering rules and restrictions apply to the Universal slots
feature:
• Universal slots feature is supported on the OPTera Connect DX network
elements equipped with DX100 or DX140 switch modules only.
• The universal slots feature allows the support of the following circuit packs
in the 10 Gbit/s slots: STM-64 T/R, HD STM-1o Dual STM-16,
Quad STM-16, or Dual GE circuit pack.
• The DX65 switch modules do not support the Universal slots feature. The
DX65 switch modules continue to support STM-64 circuit packs only, in
10 Gbit/s slots 12 (G11), 13 (G12), 16 (G17), or 17 (G18) only.
• The DX100 switch modules support 10 Gbit/s or certain types of non-10
Gbit/s circuit packs in universal slots 12 (G11), 13 (G12), 16 (G17), or
17 (G18) only.
• The DX140 switch modules support 10 Gbit/s or certain types of non-10
Gbit/s circuit packs in universal slots 1 (G0), 10 (G9), 11 (G10), 12 (G11),
13 (G12), 16 (G17), 17 (G18), or 18 (G19).
• Universal slots feature is not supported on TN-64X network elements.
• The OPTera Connect DX network element supports a maximum of 16
HD STM-1 circuit packs. A new alarm ‘CPG provisioning limit exceeded’
is raised against the last provisioned HD STM-1 circuit pack(s) when the
number exceeds 16 or if the number is 15 and the sixteenth circuit pack
provisions a protected CPG (that is, the sixteenth circuit pack is working
and the seventeen is protection).
• Card reconfiguration from Quad STM-1 to HD STM-1 will be prevented
when user issues the card reconfiguration command on a bay with 15 or 16
HD STM-1 already provisioned.
• Data communications channels are supported for non-10 Gbit/s circuit
packs in the 10 Gbit/s slots. However, the maximum number of DCC
allowed on a network element is 80 for level 1 router and 50 for level 2
router.
• The Test Access and Loopback feature is supported for non-10 Gbit/s
circuit packs in the universal slots.
• The Auto Discovery feature is supported for non-10 Gbit/s circuit packs in
the 10 Gbit/s slots.
• The auto in service (AINS) feature is supported for non-10 Gbit/s circuit
packs in the 10 Gbit/s slots.
• Query and provisioning of non-10 Gbit/s circuit packs in the 10 Gbit/s slots
is supported by OPC, TL1, OPTera Connection Manager or Preside Trail
Manager.

• Line timing from facilities of non-10 Gbit/s circuit packs in the 10 Gbit/s
slots is not supported.
• All existing logs are supported for non-10 Gbit/s circuit packs in the
10 Gbit/s slots.
• All existing performance monitoring functionality are supported for
non-10 Gbit/s circuit packs in the 10 Gbit/s slots.
• All existing equipment, facility, PM and datacom alarms are supported for
non-10 Gbit/s circuit packs in the 10 Gbit/s slots.
• Orderwire functionality requires 10 Gbit/s interface cards to be
provisioned in the bay.
Mixed configuration enhancements

Mixed configuration provides the flexibility and simplicity for users to
configure their network element to meet their service requirements, by
allowing various 10 Gbit/s configurations to be configured on the same
OPTera Connect DX network element (see Figure 2-2).
Figure 2-2
Example of a mixed configuration
DX5458
Subtending SNCP Ring/STM-16

2-Fiber MS-SPRing 0:1
Other
vendor
BMER B05 1+1
1+1 1+1
BMER B05
2FR 4FR
1+1 or unprotected low-speed interfaces
Legend
MS-SPRing = multiplexer section shared protection ring

SNCP = sub-network connection protection

OPTera Connect DX Release 5.0 introduced the support of 10 Gbit/s mixed

configuration on the same network element. OPTera Connect DX Release 5.0
supported all mixed configuration with the exception of the following 10G
mixed configurations:
• 2-Fiber Ring and 4-Fiber Ring

• Linear 1+1 and 4-Fiber Ring
• Linear 1+1, 4-Fiber Ring and 2-Fiber Ring
In OPTera Connect DX Release 6.0, the mixed configuration feature is
enhanced to support the above 10 Gbit/s mixed configurations and all of the 10
Gbit/s mixed configurations that were already supported in OPTera Connect
DX Release 5.0. You can provision the eight 10 Gbit/s high-speed interfaces
in the universal slots to support the following mixed configurations:
N = (8 - (4xP))/2]
M = (8 - (4xP))/2]
M = 8 - (4xP)]
M = 8 - (2xN)]
M = (8 - (2xN))/2]
4, M is 0 to 4 and K = 8 - 2x(N+M)]
M = 8 - (2xN)]
Note: The protection switching on one ring is independent of the other
ring and each ring can operate independently under MS-SPRing or HERS
protocol.
Table 2-6 on page 2-31, summarizes the various 10 Gbit/s configuration

examples supported by the OPTera Connect DX when equipped with DX140
switch modules.

Table 2-7 on page 2-32, summarizes the various 10 Gbit/s configuration

examples supported by the OPTera Connect DX when equipped with DX100
or DX65 switch modules.
Table 2-6
Example of supported 10 Gbit/s configurations with DX140 switch module
Configurations 4F 4FR 2FR Linear 1+1 0:1

Chain MS-SPRing MS-SPRing
4F Chain up to 2x4F 1x4FR + 1x4F up to 2x2F + up to 2x[1+1] up to 4x[0:1] +

Chain Chain 1x4F Chain + 1x4F Chain 1x4F Chain
4FR 1x4FR + 1x4F up to 2x4FR up to 2x2F + up to 2x[1+1] + up to 4x[0:1] +

MS-SPRing Chain 1x4FR 1x4FR 1x4FR
2FR up to 2x2FR + up to 2x2FR + up to 4x2FR from (1x[1+1] from (2x[0:1] +

MS-SPRing 1x4F Chain 1x4FR + 3x2FR) to 3x2FR) to
(3x[1+1] + (6x[0:1] + 1 x
1x2FR) 2FR)
Linear 1+1 up to 2x[1+1] + up to 2x[1+1] + from (1 x [1+1] up to 4x[1+1] from (1x[1+1] +

1x4F Chain 1x4FR + 3x2FR) to 6x[0:1]) to
(3x[1+1] + (3x[1+1]
1x2FR) +2x[0:1])
0:1 up to 4x[0:1] + up to 4x[0:1] + from (1x2FR + from (1x[1+1] up to 8x[0:1]

1x4F Chain 1x4FR 6x[0:1]) to + 6x[0:1]) to
(3x2FR + (3x[1+1]
2x[0:1]) +2x[0:1])
4FR + 2FR - - from 1x4FR + 1x4FR + 1x4FR + 1x2FR

1x2FR to 4FR 1x2FR + + 2x[0:1]
+ 2x2FR 1x[1+1])
4F Chain + 2FR - - from 1x4F 1x4F Chain+ 1x4F Chain+

Chain+ 1x2FR 1x2FR + 1x2FR + 2x[0:1]
to 4F Chain+ 1x[1+1])
2x2FR


Example of supported 10 Gbit/s configurations with DX140 switch module

2FR + [1+1] 1x2FR + 1x 1x4FR + 1x2FR from (1x[1+1] + from (1x[1+1] from (1x2FR +
[1+1] + 1x4F + 1x[1+1] 3x2FR) to (3x + 3x2FR) to 1x[1+1] + 4x[0:1])
Chain [1+1] + 1x2FR) (3x[1+1] + to (2x2FR +
1x2FR) 1x[1+1] + 2x[0:1])
to (1x2FR +
2x[1+1] + 2x[0:1])
4FR + [1+1] - - 4FR + 1x[1+1] from (4FR + 4FR + 1x[1+1] +

+ 1x2FR 1x[1+1]) to 2x[0:1]
(4FR
+2x[1+1])
4FR Chain + - - 4F Chain+ from (4F 4F Chain+

[1+1] 1x[1+1] + Chain+ 1x[1+1] + 2x[0:1]
1x2FR 1x[1+1]) to (4F
Chain+2x[1+1]
)
Table 2-7
Example of supported 10 Gbit/s configurations with DX100 or DX65 switch module

4F Chain 1x4F Chain - - - -
4FR - 1x4FR - - -
MS-SPRing
2FR - - up to 2x2FR 1x2FR + 1x2FR + 2x[0:1]

MS-SPRing 1x[1+1]
Linear 1+1 - - 1x[1+1] + up to 2x[1+1] 1x[1+1] + 2x[0:1]

1x2FR
0:1 - - 2x[0:1] + 1x[1+1] + up to 4x[0:1]

1x2FR 2x[0:1]

The following engineering rules and restrictions apply to the mixed STM-64
configurations:
• Only two nodes are supported in a 10 Gbit/s Linear 1+1 terminal.
• Extra traffic is not supported in 10 Gbit/s Linear 1+1 configurations.
• Route diversity for 10 Gbit/s Linear 1+1 configurations is supported.

• 10 Gbit/s 1:1 or N:1 configurations is not supported.

• The DX140 switch modules are required to support STM-64 circuit packs
in slots G0, G9, G10 and G19.
• Existing protection groups can be deleted only if there is no node map
against it (for rings) or if there is no network element map (for linear).
• Protection group pairing is the same as in OPTera Connect DX Release 5.0.
– For 10 Gbit/s 4FR: (G0&G10, G9&G19), (G11&G12, G17&G18)
– For 10 Gbit/s 4F Chain: (G0&G10, G9&G19), (G11&G12,
G17&G18)
– For 10 Gbit/s 2FR: (G0&G10), (G9&G19), (G11&G12),
(G17&G18)
– For 10 Gbit/s 1+1: (G0&G10), (G9&G19), (G11&G12),
(G17&G18)
• You cannot mix SONET and SDH configurations on the same OPTera
Connect DX network element.
— SONET and SDH network elements cannot be provisioned in the same
linear or ring configuration.
— All configurations on a DX Hub network element must be SONET or
SDH, not a mix of both.
• The protection switching on one ring is independent of the other ring and
each ring can operate independently under MS-SPRing or HERS protocol.
Quad STM-16 T/R circuit pack
OPTera Connect DX Release 6.0 introduces two new non-DWDM Quad
STM-16 T/R circuit packs: Quad STM-16 Short Reach (SR) T/R circuit pack
(NTWR31AB) and Quad STM-16 Intermediate Reach (IR) T/R circuit pack
(NTWR31BA). The Quad STM-16 T/R circuit pack is a full height circuit
pack with four transmit and four receive optical ports, that provides a total of
10 Gbit/s capacity. The Quad STM-16 T/R circuit pack has SC connectors and
operates at 1310 nm.
The Quad STM-16 tributary circuit pack is only supported in the universal
slots of the OPTera Connect DX network element. Therefore, the Quad
STM-16 circuit pack can provide an addition of up to 40 Gbit/s of protected or
80 Gbit/s of unprotected add/drop tributary traffic in the universal slots.
The Quad STM-16 SR T/R circuit pack has the same transmit and receive
specifications as the single STM-16 SR T/R circuit pack (NTCA30CK) or the
Dual STM-16 T/R circuit pack (NTWR30AA). The Quad STM-16 SR T/R
circuit pack complies with the SR STM-16 optical parameters of ITU-T
Specifications (G.957 I-16.1).

The Quad STM-16 IR T/R circuit pack has the same transmit and receive
specifications as the Dual STM-16 T/R circuit pack (NTWR30BA). The Quad
STM-16 IR T/R circuit pack complies with the IR STM-16 optical parameters
of ITU-T Specifications (G.957 S-16.1).
The Quad STM-16 circuit pack has a wide band receiver (1250 nm - 1600 nm).
For more information, refer Chapter 8 “Technical specifications” in this
document.
The Quad STM-16 circuit pack provides four independent T/R interfaces. The
Quad STM-16 circuit pack has one red RED to indicate a circuit pack failure,
one green LED to indicate that any one of transmit or receive optical fibers is
carrying traffic, and four yellow LEDs (one for each receive optical fiber) to
indicate a loss of signal (LOS) condition on a receive optical fiber (see Figure
2-3 on page 2-34).
Figure 2-3
Quad STM-16 T/R functional diagram
DX5367t
Port #1
Tx
2.5G
Rx
Yellow LED
Port #2
Tx
2.5G
Rx
Yellow LED
To switch
Port #3 cards via
Tx backplane
2.5G
Rx
Yellow LED
Port #4
Tx
2.5G
Rx
Yellow LED
Red LED
Green LED

Shelf configuration
The Quad STM-16 circuit pack is supported in the universal slots of the main
transport shelf and requires the shelf be equipped with DX100 or DX140
switch modules. The DX100 switch modules support the Quad STM-16 circuit
packs in universal slots 12 (G11), 13 (G12), 16 (G17), and 17 (G18) only (see
Figure 2-1 on page 2-24). The DX140 switch modules support the Quad
STM-16 circuit packs in universal slots 1 (G0), 10 (G9), 11 (G10), 12 (G11),
13 (G12), 16 (G17), 17 (G18) and 18 (G19) (see Figure 2-1 on page 2-24).
The Quad STM-16 circuit pack can be mixed with other circuit pack types in
the same group, provided the circuit pack group is configured as unprotected.
Otherwise, protected groups must include the same circuit pack type. For this
rule, the Quad STM-16 SR T/R circuit pack and Quad STM-16 IR T/R circuit
pack are considered as the same circuit pack type. A protection group is
G11/G12, G17/G18, G0/G10, or G9/G19.
Traffic configuration
Four STM-16 facilities are created when a Quad STM-16 circuit pack group is
provisioned. The facilities are in-service by default. You can change the
primary state of any of the facility. You can also query the secondary state of
the facilities.
When the Quad STM-16 circuit pack is auto-provisioned, the protection mode
of the STM-16 facilities are set to its default protection scheme. The Quad
STM-16 circuit pack supports mixed 2FR, linear 1+1 protected and
unprotected facilities on the same circuit pack. After the Quad STM-16 circuit
pack is auto-provisioned, you can change the protection scheme of each port
independently.
The Quad STM-16 circuit pack also supports mixed SONET and SDH
facilities on the same circuit pack. For example, ports 1 and 3 can be SONET
and ports 2 and 4 can be SDH.

Performance monitoring
The performance monitoring functionality of the Quad STM-16 circuit pack is
similar to the single or Dual STM-16 circuit pack. The Quad STM-16 circuit
pack supports SONET or SDH facility performance monitoring for each
OC-48 or STM-16 facility, as shown in Table 2-8 on page 2-36 and Table 2-9
on page 2-36.
Table 2-8
SONET parameters collected
Level Parameters
Section CV, ES, SES, SEFS
Line CV, ES, SES, UAS, FC
Intermediate path CV, ES, SES, UAS, FC
Table 2-9
SDH parameters collected
Level Parameters
Regenerator section (RS) EB, BBE, ES, SES, OFS, BBER, ESR, SESR
Multiplexer section (MS) EB, BBE, ES, SES, UAS, SEP, BBER, ESR, SESR,
SEPI, UAT
Intermediate path EB, BBE, ES, SES, UAS, SEP, BBER, ESR, SESR,
SEPI, UAT
Protection PM monitoring covers protection switch count (PSC) and

protection switch duration (PSD). The PSD is reported for revertive switch
modes only.
Protection switching
The Quad STM-16 T/R circuit pack supports the following protection
switching schemes (similar to the single or Dual STM-16 T/R circuit pack) on
a per-port basis:
• 1+1 unidirectional and bidirectional (non-revertive and revertive)
• 1*1 unidirectional and revertive (for multiplexer section-switched
matched nodes)
• unprotected (0:1)
• SNCP
• 2FR
The Quad STM-16 T/R circuit pack supports following protection switch
hierarchy (from highest to lowest priority): lockout, forced switch, automatic
switch, manual switch, wait-to-restore, and exerciser.

Bandwidth management and connection provisioning

Connections for each facilities of the Quad STM-16 SR T/R circuit pack are
supported at the following rates: VC-4, VC-4-2c, VC-4-4c, VC-4-8c or
VC-4-16c.
The Quad STM-16 SR T/R circuit pack provides support for path trace
functionality and signal label extraction on all supported payload types.
Section trace functionality is provided for all STM-16 facilities.
Alarms and fault management

The Quad STM-16 T/R circuit pack supports the detection of both module and
facility failures. All equipment and facility alarms that are currently supported
by other SDH low-speed port circuit packs are supported by the Quad STM-16
T/R circuit pack.
External communications
The Quad STM-16 circuit pack supports for four RS DCC and four MS DCC
ports. All DCC ports are disabled by default and can be enabled or disabled
from the network element user interface. An OPTera Connect DX network
element supports a maximum of 80 level 1 and 50 level 2 DCC ports. For more
information, refer to the Optical Networks Data Communications Planning
Guide, NTR710AM.
The Quad STM-16 circuit pack supports independent DCC route diversity on
each port. Route diversity can be either enabled or disabled independently for
each facility.

The network element user interface was modified to support the Quad STM-16
OPC user interface

The OPC user interface was modified to support the Quad STM-16 circuit
packs in the universal slots.

The following engineering rules and restrictions apply to the Quad STM-16
circuit pack:
• the Quad STM-16 circuit pack is only supported in the universal slots of
the OPTera Connect DX network element.
• the Quad STM-16 circuit pack is not supported in Classic TN-64X network
element.

• in protected configurations, the working Quad STM-16 circuit packs are

equipped in slots 1 (G0), 10 (G9), 12 (G11), 16 (G17) and the protection
Quad STM-16 circuit packs are equipped in slots 11 (G10), 13 (G12), 17
(G18), 18 (G19).
• the Quad STM-16 circuit pack is only supported with the DX100 or
DX140 switch modules.
• the Quad STM-16 circuit pack is supported with OPTera Connect DX
Release 6.0 only.
• the Quad STM-16 circuit pack does not support Physical PM monitoring.
• the Quad STM-16 circuit pack supports mixed DCC route diversity. The
route diversity of each port of the Quad STM-16 circuit pack can be
independently enabled or disabled.
• Quad STM-16 circuit pack in the universal slots of the OPTera Connect
DX network element can not be used to line time the OPTera Connect DX
shelf, however can be used to provide timing to connected equipment.
STM-16 LR T/R circuit pack
OPTera Connect DX Release 6.0 introduces a new 1550 nm single STM-16
long reach (LR) T/R circuit pack. The single STM-16 LR T/R circuit pack
addresses the need for a two optical port circuit pack (one transmit and one
receive) that provides reach of subtending STM-16 systems beyond the metro
area of up to 75 km. The 75 km fiber span is a target distance, the actual reach
depends on the installed fiber plant.
The single STM-16 LR T/R circuit pack has the same functionality as the
existing STM-16 LR T/R interfaces (NTCA30AK/AL).

The following engineering rules and restrictions apply to the STM-16 LR T/R
circuit pack:
• the STM-16 LR T/R is only supported on the OPTera Connect DX network
element.
• the STM-16 LR T/R is supported with the DX65, DX100 or DX140 switch
module.
• the STM-16 LR T/R is supported in the main transport shelf (G1 to G8) or
in the tributary extension shelf (G21 to G28).
• mixed DCC route diversity provisioning is supported.
• support on Legacy TN-64X and DX platforms.
• supports both SONET and SDH modes.
For more information, refer to Chapter 8 “Technical specifications” in this
document.

Dual Gigabit Ethernet ZX circuit pack

OPTera Connect DX introduced a new Dual Gigabit Ethernet (GE) extended
reach (ZX) circuit pack (NTCA90GA). The Dual GE circuit pack is part of
Nortel OPTera Packet Edge 1000 portfolio and provides a reach of up to 70 km.
The Dual GE circuit pack allows native Ethernet traffic to be mapped and
carried in the SDH synchronous payload envelope. This allows for Ethernet
traffic to be carried over an STM-64 SDH backbone in a point-to-point
configuration.
Circuit pack description

The Dual GE circuit pack is a full-height circuit pack with two independent
Ethernet ports.
The faceplate of the Dual GE circuit pack has the following LEDs:
• two yellow LEDs (one for each Ethernet port) to monitor the link status. If
either the Tx or Rx optical fiber is disconnected from the port, the link
status is down and the yellow LED for that port is on.
• one green LED to indicate that the circuit pack is in-service and that at least
one of the two Gigabit Ethernet ports is carrying traffic.
• one red LED to indicate a circuit pack failure.
The Dual GE circuit pack has the following characteristics:
• two optical interfaces with SC connectors that support 1000Base-ZX
(1550 nm) single-mode optical fiber (70 km reach) for each port.
• support for IEEE 802.3 (1998) provisionable Auto-Negotiation and flow
control (pause frame capability in the TX direction only).
• support for IEEE 802.1Q VLAN tags transparent pass .
• support for IEEE 802.1p priority fields.
• ability to handle packet frames up to 9600 bytes.
• path automatic in-service propagation to the Ethernet link level.
• support for signal label for terminated Dual Gigabit Ethernet (GE)
payloads.
• layer 3 transparency.
The Dual GE ZX T/R circuit pack has the same functionality as the existing
Dual GE SX and LX T/R interfaces (NTCA90EA/CA).

The following lists the engineering rules and restrictions for the Dual GE ZX
T/R circuit pack:
• the Dual GE ZX T/R is supported on Legacy TN-64X and DX platforms.

• the Dual GE ZX T/R is supported with the DX65, DX100 or DX140 switch
module.
• the Dual GE ZX T/R is supported in the main transport shelf (G0 to G12
& G17 to G18) or tributary extension shelf (G21 to G28).
• the Dual GE ZX T/R is backwards compatible with OPTera Connect DX
Release 5.0 software.
For more information, refer to Chapter 8 “Technical specifications” in this
document.
VC-4-64c support on STM-64 linear 1+1 and 4-Fiber MS-SPRing and

Chain
OPTera Connect DX Release 4.0 introduced support for VC-4-64c
concatenated payloads on unprotected hub network elements. This capability
allowed customers to connect their 10 Gbit/s routers through a network of
OPTera Connect DXs over unprotected 10 Gbit/s links. OPTera Connect DX
Release 6.0 extends the VC-4-64c capability to support protected STM-64
1+1, 4-Fiber MS-SPRing and 4-Fiber Chain protection schemes.
Note: VC-4-64c connection is not supported on 2-Fiber MS-SPRing

configurations.
VC-4-64c concatenated payloads are supported on the following

10 Gbit/s T/R circuit packs.:
• DWDM STM-64 10G T/R circuit packs (NTCF06xx)

• Non-DWDM STM-64 10G short reach T/R circuit pack (NTWR06AB)
• Non-DWDM STM-64 10G intermediate reach T/R circuit packs
(NTWR06CA)
• Non-DWDM STM-64 10G long reach T/R circuit packs
(NTWR06BA/BB)
Note: VC-4-64c concatenated signal will pass through TN-64X regenerators
without being altered.
Connection provisioning
Provisioning VC-4-64c connections is performed from the OPC connection
Manager user interface, Translation Language 1 (TL1), Preside Trail Manager
application or from Optical Connection Manager (OCM).
4-Fiber Ring connection provisioning
VC-4-64c connection provisioning is supported for both the working and
protection channels (extra traffic) on a 4-Fiber MS-SPRing. A VC-4-64c
connection request will be denied by the OPC Connection Manager tool if:

• any facility in the entire path of the connection is not VC-4-64c capable
(i.e. unavailable bandwidth or not one of the following supported 10G T/R
circuit packs: NTCF06xx, NTWR06AB, NTWR06CA, NTWR06BA/BB)
• any ADM in the ring is not a DX bay.
• the connection is protected and any protection facility in the ring (span and
ring) is not VC-4-64c capable (i.e. unavailable bandwidth or not one of the
following supported 10G T/R circuit packs: NTCF06xx, NTWR06AB,
NTWR06CA, NTWR06BA/BB).
4-Fiber Chain connection provisioning
VC-4-64c connection provisioning is supported for both the working and
protection channels (extra traffic) on a 4-Fiber Chain. A VC-4-64c connection
request will be denied by the OPC Connection Manager tool if:
circuit packs: NTCF06xx, NTWR06AB, NTWR06CA,
NTWR06BA/BB).
• any ADM in the chain is not a DX bay.
• the connection is protected and any protection facility in the span is not
VC-4-64c capable (i.e. unavailable bandwidth or not one of the following
supported 10G T/R circuit packs: NTCF06xx, NTWR06AB,
NTWR06CA, NTWR06BA/BB)
1+1 connection provisioning
VC-4-64c connection provisioning is supported for the working channels on a
1+1. A VC-4-64c connection request will be denied by the OPC Connection
Manager tool if:
circuit packs: NTCF06xx, NTWR06AB, NTWR06CA, NTWR06BA/BB)
• attempting to provision a VC-4-64c connection on the protection facility.
Application
The protected VC-4-64c feature fulfills the growing need to carry and support
the super rate payloads required for the next generation 10 Gbit/s routers (see
Figure 2-4 on page 2-42).

Figure 2-4
VC-4-64c application
DX5463p
VC-4-64c
STM-64 Connection
1+1
VC-4-64c
Connection 4-Fiber MS-SPRing
STM-64
1+1 STM-64
STM-64 1+1
1+1
STM-64
STM-64
1+1
OPTera Connect DX
network element
OPTera Connect DX
network element
Legend
= STM-64c router
Alarms and logs

A “Connection Facility Mismatch” (Major, Service Affecting) alarm is raised
if:
• a VC-4-64c connection was provisioned on VC-4-64c capable STM-64
T/R circuit packs in the entire path and one or more of the STM-64 T/R
circuit packs are replaced by STM-64 T/R other than NTCF06xx,
NTWR06AB, NTWR06CA, or NTWR06BA/BB.
The following lists the engineering rules and restrictions for the
VC-4-64csupport on STM-64 linear 1+1 and 4-Fiber Ring feature:
• In-Service Route Rollover (ISRR) will be prevented if the STM-64 T/R

circuit packs in the new path do not support the rate.

• OnlyNTCF06xx, NTWR06AB, NTWR06CA, or NTWR06BA/BB

STM-64 T/R circuit packs support VC-4-64c concatenated payloads.
• VC-4-64c connection is not supported on 2-Fiber MS-SPRing
configurations (each 10 Gbit/s facility contains 24 working channels only).
• VC-4-64c connection provisioning is support on OPTera Connect DX bays
only.
• VC-4-64c connection are passed through TN-64X regenerators and
OPTera Long Haul (LH) repeaters.
• In-service edits of lower-rate connections to an VC-4-64c connection is not
supported.
• VC-4-64c matched line connections are not supported.
• Chain to Ring conversion will be prevented if the chain has working
VC-4-64c connection provisioned and the protection circuit pack group
(CPG) in the chain, including the broken span protection (CPG), are not
capable of VC-4-64c traffic.
• Add node procedure will be prevented, if the OPC detects that an
VC-4-64c connection is present in the ring and that the network element
being added is not capable of carrying VC-4-64c traffic.
DCC route diversity enhancement
Prior to OPTera Connect DX Release 6.0, data communications channel
(DCC) route diversity was enabled or disabled on a circuit pack basis. This
meant that the DCC route diversity of all the ports on a multi-port circuit pack
could be set to either enabled or disabled only. OPTera Connect DX Release
6.0 allows you to enable or disable the DCC route diversity feature on each
port separately. For each port the same route diversity value (enable or disable)
applies to both Regenerator Section DCC (RS DCC) and Multiplexor Section
DCC (MS DCC).
Note: For STM-64 interfaces, route diversity is always enabled.
Alarms and Logs

The following logs are modified to support route diversity on a per port bases:
• COML508 Comms Diverse Routing Change

— This logs provides the details of which port number the route diversity
was changed.
• PROV420 Local Provisioning Request
— This logs provides summary of actions performed by the user.

Security administration through the TL1 interface

Transaction Language 1 (TL1) is an industry-recognized common language
protocol for exchanging information between network elements and an
operations system (OS) for SONET optical products. OPTera Connect DX
Release 6.0 introduces TL1 commands and messages for the network
administrative functions. TL1 allows an OS to communicate with different
vendor’s equipment through the common language protocol. TL1 eliminates
the need to support vendor-specific interfaces.
OPTera Connect DX Release 6.0 provides support for the following network
administrative (security) TL1commands for SDH OPTera Connect DX:.
• ACT-USER
— The act-user command activates the TL1 user administration session.
It allows access to other user administration commands. Admin and
root users can activate the act-user command.
• CANC-USER
— The canc-user command cancels the TL1 user administration session.
• ED-USER-SECU
— This command is used to edit user security information from the OPC
user list. You can edit the user identifier (ID), group, password,
authentication type, and access privileges. Only admin users can
activate the ed-user-secu command.
• DLT-USER-SECU
— The dlt-user-secu command is used to delete a user from the OPC user
list. Only admin users can activate the dlt-user-secu command.
• ENT-USER-SECU
— The ent-user-secu command is used to add a user to the OPC user list.
You must specify the user ID, group, authentication type, and access
privileges. Only admin users can activate the ent-user-secu command.
• RTRV-USER-SECU
— Use the rtrv-user-secu command to retrieve user security information
from the OPC user list. This information includes the user ID, group,
authentication type, and access privileges. Only admin users can
activate the rtrv-user-secu command.
Note: In previous OPTera Connect DX releases, TL1 was supported on the
SONET platform only. In OPTera Connect DX Release 6.0, only the above
security commands are supported for the SDH platform. For more
information, refer to Administrative interface in TL1 Interface
Description, 323-1531-190.

Table 2-10 on page 2-45, provides a summary of new and modified TL1
commands for OPTera Connect DX Release 6.0.
Table 2-10
TL1 commands (See Note 1)
Command and Parameters Description Possible Value

Description
act-user:[tid]:<uid>:<ctag>::<pid>;
Used by admin and root tid Any valid Target Identified (TID)
users to activate a TL1 in the OPC
user administration
session. uid User ID of a user in either the • minimum length is 1 character
admin or root user groups. • maximum length is 8 characters
• alphabetical characters
supported include a through z
(lowercase only)
• numeric characters supported
include 0 to 9
• the first character must be
alphabetical
ctag Any valid Correlation TAG
pid Password: • must be exactly 8 characters in

local length
= <local password> • alphabetical characters
radius_local user
(lowercase only)
= <PIN><SecurID token>,<local
password> include 0 to 9
• special characters supported
include $ (dollar sign) and _
(underscore)
alphabetical
• passwords must contain at least 1
numeric or 1 special character
• passwords must not contain the
associated UserID
• do not reuse an old password
unless it is older than the obsolete
password



Description
canc-user:<tid>:[uid]:<ctag>;
Used to cancel a TL1 user tid Any valid Target Identified (TID)
administration session. in the OPC
uid User ID of a user in either the • minimum length is 1 character

(lowercase only)
include 0 to 9
alphabetical
dlt-user-secu:<tid>:<uid>:<ctag>;
Used, during a user tid Any valid Target Identified (TID)

administration session, to in the OPC
delete a user from the
OPC user list. uid User ID of a user in either the • minimum length is 1 character
(lowercase only)
include 0 to 9
alphabetical



Description
ed-user-secu:<tid>:<uid>:<ctag>:[ngrp]:,[npid],,[nuap]:[auth_type];
Used, during a user tid Any valid Target Identified (TID)

administration session, to in the OPC
change the security
parameters associated uid User ID of a user in either the • minimum length is 1 character
with a tl1usr user. admin or root user groups. • maximum length is 8 characters
(lowercase only)
alphabetical
ngrp New group to contain the user
npid Optional new password for the • must be exactly 8 characters in

user account length
(lowercase only)
(underscore)
alphabetical
associated UserID
• don’t reuse an old password
unless it is older than the obsolete
password
nuap Optional new user access The possible values are:

privilege for the user account. R (read access only)
RW (read/write access only)
RWA (read/write/admin access)
NULL (no access)
auth_type Authentication type LOCAL (user local authentication)

RADIUS_LOCAL (both local and
RADIUS authentications)
DEFAULT (default authentication
type specified in the CUA)



Description
ent-user-secu:<tid>:<uid>:<ctag>:<grp>:<pid>,,<uap>:<auth_type>;
tid Any valid Target Identified (TID)

in the OPC
uid User ID of a user in either the • minimum length is 1 character

(lowercase only)
include 0 to 9
alphabetical
grp Group where you want to include

the new user
pid Password for the user account • must be exactly 8 characters in

length
(lowercase only)
include 0 to 9
(underscore)
alphabetical
associated UserID
uap User access privilege for the The possible values are:
user account. R (read access only)
RW (read/write access only)
RWA (read/write/admin access)
NULL (no access)
auth_type Authentication type LOCAL (user local authentication)

RADIUS_LOCAL (both local and
RADIUS authentications)
DEFAULT (default authentication
type specified in the CUA)



Description
rtrv-user-secu:<tid>:[uid]:<ctag>;
Used, during a user tid Any valid Target Identified

administration session, to (TID) in the OPC
retrieve the security
parameters for a tl1usr uid User ID of a user in either the • minimum length is 1 character
user. admin or root user groups. • maximum length is 8 characters
(lowercase only)
include 0 to 9
alphabetical
Note 1: For more information refer to TL1 Interface Description, 323-1531-190.
Simultaneous TL1 sessions

OPTera Connect DX Release 6.0 a maximum of six simultaneous
TL1surveillance sessions If six TL1 sessions are active, then a maximum of
one OPC user interface sessions can occur, see Table 2-11.
Table 2-11
TL1 operations system sessions
OPTera Connect DX Release 6.0
Simultaneous TL1 Simultaneous

sessions OPCUI sessions
0 4
1 4
2 3
3 3
4 2
5 1
6 1
The TL1 enhancement are implemented according to the following Telcordia

standards: GR-199 and GR-835.

Hardware Baseline tool

OPTera Connect DX Release 6.0 introduces the Hardware Baseline tool, this
feature provides tool to perform hardware baseline audits automatically
(schedulable) and manually in order to ensure the baseline of the cards inside
an OPC span of control meet the baseline requirements. Prior to OPTera
Connect DX Release 6.0, the hardware baseline check was only available
when doing a Healthcheck during a software upgrade. DX Release 6.0 makes
this tool available outside of the software upgrade utility.
The Hardware Baseline tool identifies the product engineering code and
hardware release number of circuit packs, and schedules a hardware baseline
audit. The default baseline can be modified to suit user-specified needs.
There are two baselines which Hardware Baseline tool supports:
• the Nortel baseline (the default provided by Nortel)

• a customer-modified baseline (optional)
Only one baseline, per span of control and per release, can be active at a time.
By default, the Nortel baseline is active (that is, it overrides the
customer-modified baseline if one has been created). After you create the
customer-modified baseline, you must then specifically activate it before it can
override the default Nortel baseline.
After a release upgrade, the new release uses the Nortel baseline. Any changes
in the customer-modified baseline are not copied to the new Nortel baseline.
The customer-modified baseline must be activated again after each release
upgrade if you wish to use the modified settings.
The Hardware Baseline tool is part of the OPC Admin toolset listed as
“Hardware Baseline” and is available for “ROOT” users and users in the
“ADMIN” group. Figure 2-5 on page 2-51, shows the layout of the OPCUI
screen with the Hardware Baseline tool listed.

Figure 2-5
OPCUI Screen - Hardware Baseline tool
DX5459
>. User Session Manager : root

Available tools Open tools
Toolset/Tools ID State Tool

OPC Shutdown 2 >. OK OPC Status: Primar y/Active
OPC Date 3 - Unix Shell
Por t Configuration 4 - Unix Shell
IP Routing Admin 6 >. OK Alar m Monitor
Unix Shell
OPC PM Coll. Filter
TL1 Configuration
OPC Alarm Prov
Event Browser (SEC)
Security Log Dump
Protection Mngr (A)
Hardware Baseline
Network Admin
Configuration Mngr
Connection Mngr (AC)
[ Logout ]
C0 M0 m2 w0 FailProt 0 Lckt 0 ActProt 15 PrfAlrt 0 21:47
Figure 2-6 on page 2-51, shows the functions available to a user from the
Hardware Baseline tool main menu screen.
Figure 2-6
Hardware Baseline tool - Main menu
DX5460
Hardware Baseline Tool
Please choose one of the following:
1) view the hardware baseline

2) perform hardware baseline check
3) view the results of baseline check
4) modify the hardware baseline
5) activate a hardware baseline
6) delete the modified hardware baseline
7) disable/re-enable baseline check
8) modify the scheduled audit
9) display additional help text and infor mation
10) quit this tool
Enter your numeric choice [1-10]:
C0 M0 m0 w0 FailProt 0 Lckt 0 ActProt 15 PrfAlrt 0 21:36
From the Hardware Baseline tool main menu screen, the user is provided with
the following options:
• View the hardware baseline file

— This option lists the Hardware baseline files available for viewing.
• Perform hardware baseline check
— This option allows the user to manually run the hardware baseline tool
on one, more than one or all the NEs in the OPC Span of Control
(SOC). Manual audits may be run any number of times.
• View the results of the hardware baseline check
— This option allows the users to view the results from up to five previous
checks. The key words “(most recent)” are placed beside the latest
result file.
• Modify the hardware baseline file
— The user can modify the baseline file by selecting:
– modify the release of a card in the baseline
For each circuit pack, you can specify the baseline number as a specific
card release or higher, as a range of releases, by excluding specific
releases, or a combination of these. See Table 2-12 on page 2-52 for
baseline number examples.
Table 2-12
Baseline number examples
Baseline number Meaning
1 Any card with this PEC
3-5 Any card with this PEC and version number greater than
2
3-5, 10 Any card with this PEC and a version greater than or
equal to 10, plus versions 3 through 5 (inclusive)
3-5, 10, 15 Any card with this PEC and a version greater than or
equal to 15, plus versions 3 through 5 (inclusive) and
version 10
– add a new card to the baseline file

– delete a card that was added to the baseline
Note: You cannot delete a default circuit pack type from the baseline. You
can only add new ones or delete your own customer-added entries.
• Activate a hardware baseline file

— Selects which baseline is active (either the Nortel default baseline or
the modified baseline.) The baseline check always uses the active
baseline.
• Delete the modified hardware baseline file

— Removes a modified baseline, this option discards ALL changes made

to the default Nortel baseline.
• Enable/disable baseline check
— This option turns off (disables) the baseline audit (or turns it back on
[enables] if it is already disabled). The result of disabling the baseline
audit is that if the user tries to perform a baseline check, a message will
appear stating that the baseline test is disabled and nothing is done.
• Modify the scheduled audit
— Allows the user to schedule the Hardware Baseline tool to
automatically check the baseline at a given time. The frequency can be
set to a minimum of once per day, once per week, or up to a maximum
of once every 6 weeks. The scheduled audit can also be disabled
completely.
The baseline file specifies the circuit packs supported in a release by product
engineering code (PEC) and baseline number (hardware release number).
There is a default Nortel baseline file (baseline.dx) that cannot be edited or
deleted. There can also be a user editable baseline file (baseline.mod) that
allows users to add and delete a circuit pack, change the release number of the
circuit pack and delete the delete the modified baseline file. This file is created
when a modify baseline operation is performed.
Alarms and Logs

If the audit finds one or more circuit packs below the OPTera Connect DX
Release 6.0 active baseline, the following OPC equipment alarm is generated:
• Below-baseline CP exists in the system

The severity of this alarm is minor, non service affecting (mn, nsa).
A Software and Data Administration (SDA) log is generated when:
• OPC hardware baseline audit completes (SDA622)

• OPC fails to raise the alarm “Below-baseline CP exists in the system”
(SDA348)
• The audit fails for a reason OPC can determine (SDA344)
• The audit fails for a reason OPC cannot determine (SDA345)
The following engineering rules and restrictions apply to Hardware Baseline
tool:
• Only one instance of the Hardware Baseline audit can be running at any
given time, whether scheduled, manual, or as part of an upgrade.
• The Hardware Baseline audit can only be run on an active OPC.

• The Hardware Baseline tool does not run on the NE; it only runs on the
OPC.
• Scheduled audits run at a maximum frequency of once per day. The
Hardware Baseline tool can be run manually as well.
• The OPC will store the results of the five most recent baseline checks.
• Association must exist to all NEs for the baseline check to complete
successfully.
OPC connection service enhancements
The OPC user interface was updated to support the Quad STM-16 T/R circuit
packs (SR and IR) and tributary circuit packs in the universal slots. In addition,
the OPC Connection Manager was enhanced to support:
• editing of nodal connections
• editing of end-to-end connections
• provisioning of VC-4-2cand VC-4-8c connection rates across 2 Fiber
STM-16 MS-SPRing configurations
Editing of nodal connections
A new Edit Nodal Connection dialog (see Figure 2-7 on page 2-55) was added
to the OPC Connection Manager user interface that allows the user to edit all
the fields except the NE field of a nodal connection. The Edit Nodal
Connection dialog is the same as the Add Nodal Connection dialog except that
the Increment button is disabled.
If you change the connection name only, traffic is not affect. If you change any
other parameter, a traffic hit occurs. You can change one or more parameters
before applying the changes. When you complete the parameter changes,
select the Apply button to implement the changes. If you do an invalid change,
the system give an appropriate informative warning message.

Figure 2-7
Edit Nodal Connection dialog box
DX5474p
Edit Nodal Connection
NE: > 20004 <
Connection Rate: > VC-4 < Direction: > Bi < No of Conns: > 1
Connection Name: MIXED CONFIG
Source Sink
Endpoint: > STM64 G19 1 Endpoint: > STM64 G11, G12 1
Shelf: 2 Slot: 18 SNCP [ ] Shelf: 2 Slot: 12,13 SNCP [ ]
End NE A: > 20005 < End NE Z: > 19206 <

Sec NE A: > < Sec NE Z: > <
[ Apply Return] [ Close Del]
Editing of end-to-end connections

A new Edit End to End Connection dialog (see Figure 2-8 on page 2-56) was
added to the OPC Connection Manager user interface that allows the user to
edit all the fields except the Configuration field of an end-to-end connection.
The Edit End to End Connection dialog is similar to the Add End to End
Connection dialog except that the Configuration field is disabled.
If you change the connection name only, traffic is not affect. If you change any
other parameter, a traffic hit occurs. You can change one or more parameters
before applying the changes. For matched node connection, select the
Secondary Gateway button to display the Add Secondary Gateway(s) dialog
box, make the changes to this dialog box and select the OK button to return to
the Edit Connection dialog box. When you complete the parameter changes,
select the Apply button to implement the changes. If you perform an invalid
change, the system give an appropriate informative warning message.

Figure 2-8
Edit connection dialog box
DX5475p
Edit End to End Connection
Configuration: > < Rate: > < Direction: > Bi <
Connection Name:
A End NE Z End NE
NE: > < NE: > <
Endpoint: > Endpoint: >

Shelf: Slot: SNCP [ ] Shelf: Slot: SNCP [ ]
Next Config NE: > < Next Config NE: > <
Route: > Short < Channel: > Traffic type: > Protected <
[ Route List ] [ Secondary Gateway G]
[ Apply Return] [ Close Del]
Note: Only the connection ID can be modified on a Gigabit Ethernet (GE)

provisioned connection.
Provisioning of VC-4-2c and VC-4-8c connection rates across 2 Fiber

STM-16 MS-SPRing configurations
OPTera Connect DX release 6.0 supports the provisioning of VC-4-2c and
VC-4-8c connection rates across 2 Fiber STM-16 MS-SPRing configurations.
Both unidirectional and bidirectional connection types are supported.
OPC Protection Manager enhancements

The Protection Manager tool provides a subnetwork view of the protection
status and control of all network elements. The Protection Manager tool allows
the user to monitor the protection status, perform protection switching
commands, and schedule the exercisers.
The OPTera Connect DX OPC Protection Manager tool in Release 6.0 is

enhanced to support protection switching utilities for STM-16 subtending
MS-SPRing configurations.
Default Filtering scheme

The default filtering scheme between linear and MS-SPRing schemes will be
same as in previous releases. That is, if an OPC contains both linear and
MS-SPRing (both 2FR and 4FR) configurations, then invoking the protection
manager will display MS-SPRing configuration first. Within MS-SPRing,
4FR precedes 2FR.
In DX Release 6.0, if the OPC contains both STM-64 2F/4F MS-SPRing

configuration and STM-16 Subtending 2F MS-SPRing configurations then
the default filtering will be STM-64 2F/4F configuration included and

STM-16 subtending 2F MS-SPRing configuration (s) excluded. Both STM-64

and STM-16 configurations can not be included at the same time. To include
STM-16 subtending 2F MS-SPRing configuration, user will have to exclude
all the STM-64 configurations and then include the STM-16 subtending 2F
MS-SPRing configurations.
Displaying Out-Of-SOC network elements

OPTera Connect DX NEs not in of the OPC’s Span Of Control (SOC), along
with STM-16 Classic NEs and OPTera Metro 3500 NEs which can be part of
the STM-16 subtending 2F MS-SPRing, will be displayed in the protection
manager anchor window as “not in SOC”. However, the protection status for
all those network elements will be filled with “-” and the network elements
greyed out.
Protection Manager command set

All STM-64 2F MS-SPRing protection commands are now supported for
STM-16 subtending 2F MS-SPRing configurations. These commands include:
• Lockout working
• Lockout protection
• Global lockout working
• Global lockout of protection
• Forced switch
• Manual switch
• Exercise this NE
• Exercise this configuration
The Global lockout of working and Global lockout of protection commands
are new for STM-16 subtending 2F MS-SPRing configurations. These
commands will apply a lockout of working and lockout of protection
respectively on all OPTera Connect DX network elements which are part of the
selected 2F MS-SPRing configuration and belong to the OPC’s SOC.
Scheduling Exercisers
The protection exerciser allows you to verify the protection functionality
without affecting the traffic. By running the protection exerciser, you can
detect silent protection-related failures before the failures become
service-affecting.
The protection exerciser uses specific APS channel (K-byte) signaling to

initiate protection switching behavior. This protection switching behavior is
initiated in the network element and within other network elements in the
network. The protection exerciser simulates protection switching, without
completing the actual protection bridge and switch.

For OPTera Connect DX Release 6.0, you will be able to schedule the exerciser
time for a particular network element or a particular configuration using the
commands Schedule this NE and Schedule this configuration for all the
OPTera Connect DX network elements in the OPC’s SOC which are part of the
STM-16 subtending 2F MS-SPRing configuration.
Note: For 2F MS-SPRing configuration consisting of OPTera Connect

DX, and TN-16X network elements, the exerciser should be run on all the
network elements in order to verify the integrity of the protection
switching bytes (K-bytes) communication between an optical interface
pair
Test access enhancement

OPTera Connect DX Release 5.0 introduced the test access feature which
supported the monitoring test access (non-intrusive in-service testing) and the
split (A/B) test access (for an out-of service connection) modes of operation.
OPTera Connect Release 6.0 continues to support these two test access modes
and introduces the split (E/F) test access mode of operation.
The split (A/B) test access mode allows you to monitor signals on a test set via
a test access port (TAP) in one direction and transmits a signal from the
transmitter of the same test set in the same direction of the monitored channels
(see Figure 2-9 on page 2-58).
Figure 2-9
Example of a split (A/B) test access mode of operation
DX4544t
Input Output
Input Output
TAP In
Test
unit
TAP Out
Legend
TAP - Test access port

Note: SplitB is achieved by entering a splitA command with the FromAID

of the facility side.
The split (E/F) test access mode allows you to monitor signals on a test set via
a TAP in one direction and loopback a signal from the transmitter of the same
test set. In this mode of operation, the network element inserts AIS signal on
the outgoing channels that are under test (see Figure 2-10 on page 2-59).
Figure 2-10
Example of a split(E/F) test access mode of operation
DX5370t
AIS
Input Output
AIS
Input Output
TAP In
Test
unit
TAP Out
Legend:
AIS = Alarm indication signal
TAP = Test access port
Note: SplitF is achieved by entering a splitE command with the FromAID

of the facility side.

The network element user interface was modified to support the split (E/F)
mode of operation. The modification was made to the Test Access Menu which
is a sub-menu of the Payload Menu. The following tools of the Test Access
Menu were changed:
• QueRy Test Access Port (QRTAP)
• Set Test Access Connection (STAC)
• Change Test Access Mode (CTAM)

QueRy Test Access Port (QRTAP)

In OPTera Connect DX Release 5.0, this command displayed Split or Monitor
status for the Test Mode of the test access connections on the Test Access port.
The Split status was by default split (A/B) mode because this was the only
mode that was supported in OPTera Connect DX Release 5.0. To differentiate
the split (E/F) mode from the split (A/B) mode, the Split Test Mode status was
modified to SplitA and SplitE. SplitA mode is for split (A/B) mode and SplitE
is for the new split (E/F) mode.
Set Test Access Connection (STAC)
Set Test Access connection command creates a new connection between an
input port specified by the user and the test access port. For this command in
OPTera Connect DX Release 6.0, you have a choice of three test modes
(MONITOR, SPLITA or SPLITE) instead of two test modes (MONITOR or
SPLIT) for the test connections.
Change Test Access Mode (CTAM)
Change Test Access Mode command allows the user to change the test state of
the test access connection. In OPTera Connect DX Release 6.0, this command
will provide a choice of three test modes (MONITOR, SPLITA or SPLITE)
instead of two test modes (MONITOR or SPLIT) for the test connections.
The following test mode changes are supported:
• MONITOR −−> SPLITA

– if there is no SPLITE on the other end of the connection.
• SPLITA −−> MONITOR
• MONITOR −−> SPLITE
– if there is no SPLITA on the other end of the connection.
• SPLITE −−> MONITOR
The following test mode changes are NOT supported:
• SPLITA −−> SPLITE

• SPLITE −−> SPLITA
If user attempts to change to one of the not supported test mode change, the
following error message is displayed : “Test Access mode cannot be changed
between SPLITA and SPLITE.”
Alarms and Logs

The existing “Test Access Connection active” (w, nsa) alarm will be
raised/lowered when Test Access SplitE connection is initiated/removed.
The existing PLD401 log will be generated when the test access SplitE is
initiated or removed.


The engineering rules and restrictions for the split (E/F) test access mode is the
same as that for the split (A/B) test access mode, except:
• Test access splitE connections can be applied to bidirectional connections
only.
• Test access SplitE connection cannot be applied to a connection on which
a SplitA connection has been applied.
• Test access SplitE connection cannot be applied to a connection on which
a loopback has been applied.
• Test access splitE can only be applied once per connection in each
direction.
Miscellaneous features
Flexible default protection scheme enhancement
OPTera Connect DX Release 5.0 introduced the default protection scheme
(DPS) feature. The DPS feature allows you to provision the default protection
scheme for tributary and line interfaces (except for Gigabit Ethernet interfaces
which are always unprotected). You can set the DPS for each optical interface
during the commissioning of the network element and you can change the DPS
of the interfaces later.
In OPTera Connect DX Release 6.0, this feature is enhanced to allow users to

define the switch mode (Uni-directional or Bi-directional) for 1+1 protection
scheme.
During commissioning, you must set the DPS for the 10 Gbit/s interfaces to
one of the following:
• 4FR
• 2FR
• 1+1 uni
• 1+1 bi
• unprotected
During commissioning, the setting of the DPS for the STM-1, STM-4 and
STM-16 interfaces is optional. You can set the DPS of the tributary interfaces
as follows:
• STM-1 interfaces can be set to 1+1 bi, 1+1 uni or unprotected.
• STM-4 interfaces can be set to 1+1 bi, 1+1 uni or unprotected.
• STM-16 interfaces can be set to 2FR, 1+1 bi, 1+1 uni or unprotected.
Gigabit Ethernet interfaces always defaults to unprotected.

Note: If you do not provision the DPS for any STM-1, STM-4 and
STM-16 interfaces, the DPS of the interfaces automatically defaults to 1+1
unidirectional.
Synchronization Status Messaging enhancements

The OPTera Connect DX supports two modes for translating synchronization
status messages from the terminating STM-N to the derived DS1 outputs
(G1OUT, G2OUT):
1 “Threshold AIS generation” mode is used when the receiving BITS clock
do not have synchronization status messaging capabilities
2 “Message Pass-through” mode is used receiving BITS clock have
synchronization status messaging capabilities.
Threshold AIS generation
OPTera Connect DX Release 6.0 continues to support “Threshold AIS
generation” mode as in previous releases. In this mode, if the best available
synchronization status message contained within the S1 byte of any STM-N
reference is of equal or poorer quality than the user provisioned Threshold AIS
value (possible options for this value are: STU, SSUT, ST2, SSUL, ST3, SEC,
SMC, or DUS), then the DS1 output (G1OUT, G2OUT) sends AIS and the TX
AIS alarm will be raised for both SF and ESF signal formats.
If the synchronization status message contained within the selected STM-N's

S1 byte is of better quality than the user provisioned Threshold AIS value, the
message on the selected STM-N is translated to the derived DS1 ESF signal
and passed to the ESI DS1 outputs (G1OUT, G2OUT). This mode of operation
is similar to the functionality currently provided by network elements that do
not support synchronization status messaging. Such network elements
generate an AIS on the derived DS1 when the STM-N becomes unacceptable
as a reference (e.g., during an LOS or AIS on the STM-N). Since BITS clocks
recognize AIS as an unacceptable reference, the generation of AIS ensures that
the BITS do not take synchronization from an STM-N that has been
disqualified. With the “Threshold AIS generation” mode, STM-N signals that
degrade in terms of synchronization traceability also cause AIS ensuring that
the reference is rejected by the BITS. This mode allows the derived DS1 signal
to be used as a synchronization reference in the cases where synchronization
status messaging in the DS1 ESF format is not supported by the BITS clock.
Message Pass-through
Prior to Release 6.0, the OPTera Connect DX supported “Message
Pass-through” mode for all signals levels except for “DUS”. In this mode of
operation, both the network element and the BITS must support DS1 ESF
synchronization status messages. The message on the selected STM-N is
translated to the derived DS1 ESF signal and passed to the ESI DS1 outputs
(G1OUT, G2OUT), in the case of “DUS” (Don’t Use for Synchronization) the

NE transmitted “AIS” instead. The BITS decides which reference is

appropriate based upon the synchronization status message provided by the
derived DS1 outputs.
For Release 6.0, the OPTera Connect DX will enhance the “Message
Pass-through” capability to pass all (including “DUS”) synchronization status
messages (SSM) processed by the “Active” STM-N reference deriving the ESI
DS1 outputs (G1OUT, G2OUT). “Message Pass-through” is enabled by
setting the Quality Code Threshold (QCT) to “Null” for a Timing Distribution
(TD) protection group.
If the DS1 output facility is set to ESF format and QCT = “Null” , then:
• If one or more STM-N reference is available (i.e. free of any automatic or

user initialed switches), after the selection based on quality level and
priority the outgoing SSM code will be the SSM code received on the
active reference used for deriving the DS1.
• In the event that multiple references or a single reference being used to
derive the DS1 have DUS code and no better reference is available, the
outgoing GxOUT synchronization status message (SSM) code will be
DUS.
• In the event that no references are available for selection (due to multiple
LOS/LOF conditions), the outgoing GxOUT signal(s) will carry AIS
(unframed all 1's) and the TX AIS alarm will be raised.
• A DUS code will no longer preclude a reference from being selected
(Active source).
If the DS1 output facility is set to SF format and QCT = “Null”, then:
• The output signal will not carry AIS, regardless of the quality code of the
active reference (even DUS), unless there are no references available for
selection (e.g. due to LOS/LOF/etc conditions).
Note: This provisioning combination is not recommended, as this may
interfere with the proper synchronization operation of the network.
If the Quality Code Threshold (QCT) is provisioned to any non-NULL value

(“Threshold AIS generation mode”), the timing distribution group will
function as in previous releases. If the Quality Code (QC) of the active
reference (STM-N) is above the threshold, the message will be passed through
onto the ESF output signal. If the best available reference is at or below the
provisioned QCT, then the derived DS1 (GxOUT) output signal will send AIS,
and the TX AIS alarm will be raised for both SF and ESF signal formats.

Strong authentication enhancements

OPTera Connect DX Release 3.0 introduced a new centralized authentication
mechanism that provided additional security when accessing OPTera Connect
DX and OC-192 network elements and operations controllers (OPCs).
In previous releases, access was based on single-factor authentication (user

name and password). As of OPTera Connect DX Release 3.0, you can assign
user access based on a two-factor authentication. A two-factor authentication
is based on:
• what you know: user name and personal identification number, or PIN
(constant information)
• what you have: SecurID card from RSA Security Inc. with a dynamic
token code (dynamic information)
The SecurID card from RSA Security Inc. generates a pseudo-random number
(called the token code) every 60 seconds. If you want to log in to a system, you
must provide your user name and PIN, together with the token code currently
displayed by the SecurID card. These three pieces of identification combine to
form your passcode. The ACE/Server authentication server from RSA
Security Inc. authenticates your passcode. If an intruder obtained your user
name and PIN, they cannot access the system without a valid token code from
the SecurID card.
Note: Note: If a user has the RADIUS-local authentication type, they

require their user name, PIN, token code and local password to log in to a
system.
You must send your authentication request to the RSA Security server while
the current token code is valid. SecurID token codes change every 60 seconds.
The server will accept token codes in a 3 minute window, allowing you to use
either the last, current, or next valid token code.
Prior to OPTera Connect DX Release 6.0, when a user logged into a OPTera
Connect DX network element or OPC they had to enter a 4- digit alphanumeric
PIN and a 6- digit token code as the password identifier (PID) and the local
password. In OPTera Connect Release 6.0, this functionality is enhanced to
support an alphanumeric PIN of up to 8-digits along with 6 or 8 digit token
codes.
Network and hardware reconfigurations

In-service hardware reconfigurations
OPTera Connect DX Release 6.0 supports all the in-service hardware
reconfigurations that are supported in OPTera Connect DX Release 5.0 except:
• In-service reconfiguration of Quad STM-4 to HD STM-1o
• In-service reconfiguration of Quad STM-4 to HD STM-1e

• In-service reconfiguration of STM-16 to HD STM-1o

• In-service reconfiguration of STM-16 to HD STM-1e
• In-service reconfiguration of Quad STM-4 to STM-16
No new in-service hardware reconfiguration are introduced in OPTera Connect
DX Release 6.0, however ISTR procedures are updated to support new Quad
STM-16 circuit pack and the universal slot feature.
In-service network reconfigurations

OPTera Connect DX Release 6.0 supports all the standard and non-standard
network reconfigurations that were supported in OPTera Connect DX Release
5.0. In addition, OPTera Connect DX Release 6.0 support the new standard and
non-standard reconfigurations listed below.
OPTera Connect DX Release 6.0 introduced the following new standard

network reconfigurations:
• In-service Add/Delete node of an OPTera Connect DX node to/from a
subtending mixed TN-16X/OPTera Connect DX 2-Fiber MS-SPRing.


3-1
Upgrade considerations and planning 3-

This chapter provides information when planning upgrades to OPTera Connect
DX Release 6.0.
Software
OPTera Connect DX Release 6.0 supports in-service software upgrades from
OPTera Connect DX Release 4.1/TN-64X Release 6.1 and OPTera Connect
DX Release 5.0/TN-64X Release 7.0. The following upgrades are supported:
• an in-service upgrade from OPTera Connect DX Release 4.1 (GA) to
OPTera Connect DX Release 6.0 (CA)
OPTera Connect DX Release 6.0 (GA)
OPTera Connect DX Release 6.0 (CA)
• an in-service upgrade from OPTera Connect DX Release 6.0 (CA) to
Note 1: You must upgrade network elements running OPTera Connect DX

Release 4.0 or earlier to OPTera Connect Release 4.1 or Release 5.0, before
you can upgrade the network elements to OPTera Connect DX Release 6.0.
Note 2: You must upgrade TN-64X network elements running TN-64X
Release 6 or earlier to TN-64X Release 6.1, or 7.0, before you can upgrade
the network elements to OPTera Connect DX Release 6.0.
Refer to Figure 3-1 on page 3-2 for the supported upgrade paths in OPTera
Connect DX Release 6.0.

3-2 Upgrade considerations and planning
Figure 3-1
Supported upgrade paths to OPTera Connect DX Release 6.0.
DX5368t
DX DX
DX Release 6.0
Release 6.0
Release 4.1 GA
CA
GA
DX
Release 5.0
GA
Hardware
Network planners require information regarding hardware impact in planning
of a software upgrade. For OPTera Connect DX Release 6.0, there is no change
from previous OPTera Connect DX releases with regards to a minimum
hardware baseline. Users currently operating their networks using these
software releases do not require a hardware upgrade in order to perform a
software upgrade to OPTera Connect DX Release 6.0.
You may have to upgrade the switch modules in order to support certain new
features in OPTera Connect DX Release 6.0. The DX100 or DX140 switch
modules are required to support the HD STM-1o/e or Dual STM-16 tributary
circuit packs. The DX100 or DX140 switch modules are also required to
support the following tributary circuit packs in the universal slots;
HD STM-1o/e, Dual STM-16, Quad STM-16, or Dual Gigabit Ethernet (GE)
circuit packs.
For additional information on OPTera Connect DX Release 6.0 features that

require upgraded switch modules, refer to Chapter 2, “New feature content” in
this document.
32 Mbyte shelf controller

For the OPTera Connect DX bay and the TN-64X add/drop multiplexer
(ADM) bay, you must have the 32 Mbyte shelf controller (NTCA41CA) to run
the OPTera Connect DX Release 6.0 software. For the TN-64X regenerator
(Regen) bay, both the 16 Mbyte (NTCA41BA) and 32 Mbyte shelf controller
support the OPTera Connect DX Release 6.0 software. This remains
unchanged from previous OPTera Connect DX releases.

128 Mbyte maintenance interface

For the OPTera Connect DX bay the 128 Mbyte maintenance interface
(NTCA42BA) is required to run the OPTera Connect DX Release 6.0 software.
For the TN-64X ADM and Regen bays, you can use the 32 Mbyte maintenance
interface (NTCA42AA) for in-service upgrades or sparing purposes only.
When you commission the TN-64X bay with a commissioning maintenance
interface, a 128 Mbyte maintenance interface is required. This remains
unchanged from previous OPTera Connect DX releases.
122 Mbyte removable media

The operations controller (OPC) supports data backups on both the 68 Mbyte
and 122 Mbyte removable media. You must use the 122 Mbyte removable
media when you perform a local upgrade to an OPTera Connect DX or
TN-64X bay. This remains unchanged from previous OPTera Connect DX
releases.
Note: You perform a local upgrade when you insert a removable media
directly in the OPC to upgrade your span of control. You can also upgrade
your span of control from a remote workstation with the Preside network
management software.
OPC
OPTera Connect DX Release 6.0 supports both the OPC-S hard disk
(NTCA51AA) and the OPC-S solid state storage module (NTCA51AB).
New hardware introduced in OPTera Connect DX Release 6.0

The following new hardware is introduced in OPTera Connect DX Release 6.0:
• Quad STM-16 SR T/R tributary circuit pack (PEC NTWR31AB)
• Quad STM-16 IR T/R tributary circuit pack (PEC NTWR31BA)
• STM-16 LR T/R tributary circuit pack (PEC NTCA30AN)
• Dual Gigabit Ethernet ZX T/R tributary circuit pack (PEC NTCA90GA)
For more details on the new circuit pack and supporting hardware, refer to
Chapter 2, “New feature content”, in this document.
Interworking
The following sections describe the minimum software baseline for other
Nortel products to interwork with OPTera Connect DX Release 6.
Preside
OPTera Connect DX Release 6.0 is aligned with Preside OSR 10, which
includes:
• Preside Applications Platform (AP) Release 10.1
• Preside Trail Management Release 5.0

• Preside Backup and Restore Release 2.1

• Preside Optical Power Management Release 4.0
• Preside Optical Sections View Release 6.0
• Preside DWDM View Release 2.0
• Preside Software Upgrade Manager Release 3.0
• Preside Optical Connection Management Release 2.0
For more information on functionality provided by these products of the
Preside network management software, refer to the section on Preside in
Chapter 5 “Software feature description” of this document.
Previous versions of the Preside network management software can also

provide limited support to OPTera Connect DX Release 6.0. To find out what
additional functionality is provided by these versions, contact your Nortel
representative.

OPTera Connect DX Release 6.0 interworking

Subtending (SDH) linear tributaries interworking
Table 3-1 on page 3-5 lists the minimum software baseline releases for SDH
linear tributaries interworking with OPTera Connect DX Release 6.0. Each
network element in a span of control must be running the minimum software
baseline release, and is managed from its own span of control.
Table 3-1
Subtending (SDH) linear tributary interworking
Subtending Linear Equipment Supported rates Supported S/W Releases
TN-1X STM-1o/e 6.0, 7.0, 8.0
TN-16x STM-16, STM-4, 7.1, 8.0, 9.0

STM-1o/e
OPTera Metro 4100 STM-4, STM-1o/e 4.5, 4.6, 4.7, 4.8
OPTera Metro 4200 STM-16, STM-4, 3.1, 3.51, 4.0, 4.1

STM-1o/e
STM-64 ADM STM-16, STM-4, 6.0, 6.1, 7.0

STM-1o/e
OPTera Connect DX 2 FR, STM-16, STM-4, 4.0, 4.1, 5.0

4 FR/Chain, Linear 1+1ADM STM-1o/e
OPTera Connect DX STM-16, STM-4, 4.0, 4.1,

unprotected 10G facilities STM-1o/e
Optical Cross Connect HDX STM-16, STM-4, 2.0, 2.1, 3.0

(formally known as OPTera STM-1o
Connect HDX)
Optical Cross Connect HDXc STM-16, STM-4, 2.11, 3.0

(formally known as OPTera STM-1o
Connect HDXc)
OPTera LH STM-16 7.0, 9.0, 10.0

Subtending (SDH) SNCP tributaries interworking

Table 3-2 on page 3-6 lists the minimum software baseline releases for SDH
SNCP tributaries interworking with OPTera Connect DX Release 6.0. Each
network element in a span of control must be running the minimum software
baseline release, and is managed from its own span of control.
Table 3-2
Subtending (SDH) SNCP tributaries interworking
Subtending (SDH) SNCP Supported rates Supported S/W Releases

Equipment
OPTera Metro 4200 STM-16, STM-4, 3.1, 3.51, 4.0, 4.1

STM-1o/e
Subtending STM-16 2-Fiber MS-SPRing tributaries interworking

Table 3-3 on page 3-6 lists the minimum software baseline releases for 2-Fiber
STM-16 MS-SPRing tributaries interworking with OPTera Connect DX
Release 6.0. Each network element in a span of control must be running the
minimum software baseline release, and is managed from its own span of
control.
Table 3-3
Subtending STM-16 2-Fiber MS-SPRing tributaries interworking
Subtending (SDH) Supported rates Supported S/W Releases

MS-SPRing Equipment
TN-16x STM-16 9.0
OPTera Connect DX STM-16 5.0
Optical Cross Connect HDX STM-16 2.0, 2.1, 3.0

(formally known as OPTera
Connect HDX)
Optical Cross Connect HDXc STM-16 2.11, 3.0

(formally known as OPTera
Connect HDXc)
Note 1: The maximum and default MS and RS DCC frame sizes of the
OPTera Metro 4100 and 4200 is 512. When the Metro 4100 or 4200 is
connected to a tributary interface of the OPTera Connect DX network
element, you must provision the MS or RS DCC frame sizes on the
tributary interface to 512. For more information, refer to Part 1 of
Provisioning and Operations Procedures, 323-1531-310 for the OPTera
Connect DX platform.

Note 2: When you are connecting other Nortel Networks equipment to the
OPTera Connect DX or TN-64X network elements, refer to the Network
Interworking Guide, NTCA68CA for more details.
Optical Ethernet Interworking
Table 3-4 on page 3-7 lists the minimum software baseline releases for optical
Ethernet interworking with OPTera Connect DX Release 6.0. Each network
element in a span of control must be running the minimum software baseline
release, and is managed from its own span of control.
Table 3-4
Optical Ethernet Interworking
Optical Ethernet equipment Supported S/W Releases
TN-16X 9.0
OPTera Long Haul 1600

Table 3-5 on page 3-7 lists the minimum OPTera Long Haul 1600 Releases
operating with OPTera Connect DX Release 6.0.
Table 3-5
OPTera Long Haul interoperability with OPTera Connect DX Release 6.0
OPTera Long Haul 1600 equipment Supported S/W Releases
Repeater/OAS 7.0, 9.0, 10.0
Combiner 7.0, 9.0, 10.0
1600G 7.0, 9.0, 10.0
Interworking span of control with 10 Gbit/s network elements

The following section outlines the minimum software baseline for 10 Gbit/s
network elements (ADMs, Regens) to interwork with OPTera Connect DX
Release 6.0 network elements.
Interworking with TN-64X regenerators
For a unified span of control, OPTera Connect DX bays and TN-64X bays
must be running the same OPTera Connect DX Release 6.0 software.
TN-64X regenerator bays running TN-64X Release 2.02 and above can
operate with OPTera Connect DX Release 6.0 network elements, provided the
TN-64X regenerator bays are under a different span of control.
Interworking with 10 Gbit/s network elements via back-to-back tributaries
Table 3-6 on page 3-8 shows the minimum software baseline for 10 Gbit/s
network elements to interwork with OPTera Connect DX Release 6.0 network
elements.

Table 3-6
Interworking with 10 Gbit/s network elements
NE Type 10 Gbit/s Configuration Supported S/W Releases
Repeater/OAS 7.0, 9.0, 10.0
Combiner 7.0, 9.0, 10.0
1600G 7.0, 9.0, 10.0
OPTera Metro 3500 1+1, 0:1 12.0
Optical Cross Connect 1+1, 0:1 2.0, 2.1, 3.0

HDX (formally known as 2F MS-SPRing,
OPTera Connect HDX) 4F MS-SPRing
Optical Cross Connect 1+1, 0:1 2.11, 3.0

HDXc (formally known as 2F MS-SPRing,
OPTera Connect HDXc) 4F MS-SPRing
TN-64X Regen 6.0, 6.1, 7.0
All ADMs in a single 2-Fiber or 4-Fiber Ring must be running the same
OPTera Connect DX Release 6.0 software. The exception can happen during a
software upgrade when customers want to upgrade the ADMs of a ring from
OPTera Connect DX Releases 4.1 or 5.0 to OPTera Connect DX Release 6.0
and these ADMs happen to be under a different OPC span of control. In this
case, the ADMs within the same ring might be running a mix of OPTera
Connect DX Release 4.1 or 5.0, and OPTera Connect DX Release 6.0 loads
for the duration of the upgrade. As such, support of mixed OPTera Connect DX
Release 4.1 or 5.0, and OPTera Connect DX Release 6.0 ADMs on the same
ring is supported for the duration of the upgrade.
Note: Customers are requested to upgrade all ADMs within the same ring
to the same OPTera Connect DX Release 6.0 .

OPC span of control rules

The OPC span of control (SOC) rules for the OPTera Connect DX Release 6.0
are:
• You cannot mix SONET and SDH network elements in the same OPC span
of control.
• An OPC span of control can comprise of:
— a maximum of 24 DX_HUB network elements configured with single
4-Fiber ADM network elements plus additional regenerator network
elements, up to a total of 34 network elements
2-Fiber ADM network elements, with no other network elements
10 Gbit/s Linear 1+1 terminal, with no other network elements
2-Fiber ADM and Nx2 Fiber Hub network element (where N is 1 to 4),
with no other network elements
4-Fiber ADM network elements and 2x4-Fiber Hub network elements,
plus additional regenerator network elements, up to a total of 34
network elements
— a maximum of 12 DX_HUB network elements configured with mixed
single Linear 1+1 and Nx(1+1) 10 Gbit/s terminals, with no other
network elements
Nx2-Fiber ADM and Linear 10 Gbit/s Mx(1+1) terminal where N+M
is 1 to 4, with no other network elements
Mx2-Fiber ADM and 1x4-Fiber ADM 10 Gbit/s terminals, where M is
1 to 2, with no other network elements
1x4-Fiber ADM and Linear 10 Gbit/s Mx(1+1) terminals where M is 1
to 2, with no other network elements
unprotected 10G facilities (0:1) and Nx2-Fiber Ring ADM where N is
1 to 3, with no other network elements
unprotected 10G facilities (0:1) and 1x4-Fiber ADM, with no other
network elements
unprotected 10G facilities (0:1) and Linear Mx(1+1) terminal s where
M is 1 to 3, with no other network elements


unprotected 10G facilities (0:1), Nx2-Fiber ADM and Linear Mx(1+1)
terminal where M+N is 1 to 3, with no other network elements
unprotected 10G facilities (0:1), 2-Fiber ADM, Linear Mx(1+1)
terminal and 4-Fiber ADM, where mixing any 2 out of 3 configurations
with no other network element
— a maximum of 8 DX_HUB network elements configured with
unprotected 10G facilities Nx(0:1) terminals, with no other network
elements

4-1
Network configuration architecture 4-

This chapter provides a system-level description of the OPTera Connect DX
network element within the optical networks synchronous optical fiber
transmission system. Topics covered include the following:
• Network configurations
• Level 2 routing
• Optical amplifier support
• OPTera Connect DX interoperability
Network configurations
OPTera Connect DX Release 6.0 supports mixed 10 Gbit/s configurations on
the same OPTera Connect DX network element. The mix of 10 Gbit/s
configurations support on the OPTera Connect DX is dependent on the switch
matrix deployed.
For OPTera Connect DX bays equipped with DX140 switch modules
(NTCA26CA) the following configurations are supported:
• Nx4-Fiber Ring (N is 1 or 2)
• mixed Px4-Fiber Ring and Nx2-Fiber Ring [where P is 0 to 2 and
N = (8 - (4xP))/2]
• mixed Px4-Fiber Ring and Linear Mx(1+1) [where P is 0 to 2 and
M = (8 - (4xP))/2]
• mixed Px4-Fiber Ring and Mx(0:1) [where P is 0 to 2 and M = 8 - (4xP)]
• mixed Px4-Fiber Ring, Nx2-Fiber Ring, Linear Mx(1+1) and Kx(0:1)
• Nx2-Fiber Ring (N is 1 to 4)
• mixed Nx2-Fiber Ring and Mx(0:1) [where N is 0 to 4 and M = 8 - (2xN)]
• mixed Nx2-Fiber Ring and Linear Mx(1+1) [where N is 0 to 4 and
M = (8 - (2xN))/2].
• mixed Nx2-Fiber Ring, Linear Mx(1+1) and Kx(0:1) [where N is 0 to 4,
M is 0 to 4 and K = 8 - 2x(N+M)]
• Linear Nx(1+1) (where N is 1 to 4)

4-2 Network configuration architecture
• mixed Linear Nx(1+1) and Mx(0:1) [where N is 0 to 4 and M = 8 - (2xN)]

• Nx(0:1) (where N is 1 to 8)
Note 1: You can mix any configuration as long as the you don’t exceed 8
10GBit/s optical interfaces.
Note 2: Table 2-6 on page 2-31, summarizes the various 10 Gbit/s
configuration examples supported by the OPTera Connect DX when
equipped with DX140 switch modules.
(NTCA26BA) or DX65switch modules (NTCA26AA) the following
configurations are supported:
• Nx4-Fiber Ring (N is 1)
• mixed Px4-Fiber Ring and Nx2-Fiber Ring [where P is 0 or 1 and
N = (4 - (4xP))/2]
• mixed Px4-Fiber Ring and Linear Mx(1+1) [where P is 0 or 1 and
M = (4 - (4xP))/2].
• mixed Px4-Fiber Ring and Mx(0:1) [where P is 0 to 1 and M = 4- (4xP)]
[where P is 0 to 1, N is 0 to 2, M is 0 to 2 and K = 4 - 2x(N+M)]
• Nx2-Fiber Ring (N is 1 to 2).
M = (4 - (2xN))/2].
M is 0 to 2 and K = 4 - 2x(N+M)]
equipped with DX100 or DX65 switch modules.
The mixed configurations feature increases network configuration flexibility
by allowing various 10 Gbit/s configurations on the same OPTera Connect DX
network element. The 10 Gbit/s Linear 1+1 and 10 Gbit/s unprotected
configurations allow interconnection between the OPTera Connect DX
network element and other vendors 10 Gbit/s Linear 1+1 and 10 Gbit/s
unprotected terminals.

This section describes the following network configurations:

• 4-Fiber network configurations and protection switching
• 2-Fiber Ring configurations and protection switching
• 10 Gbit/s unprotected configuration
• 10 Gbit/s Linear 1+1 configuration
• Subtending sub-network connection protection ring
• Subtending STM-16 2-Fiber multiplexer section shared protection rings
• Tributary hairpinning application
• Low-speed cross-connect application
• Tributary circuit packs and protection schemes
The 4-Fiber Rings and 2-Fiber Rings can also support multiplex section
(MS)-switched matched nodes configuration to protect the inter-ring traffic.
Note:
4-Fiber network configurations and protection switching

The OPTera Connect DX Release 6.0 network element supports mixed
10 Gbit/s configurations including on the same network element. The
following 4-Fiber network configurations are supported on the same
DX_HUB network element:
• Single (1x4-Fiber) and Dual (2x4-Fiber) Linear ADM chain configuration
• Single 1x4-Fiber and 2x4-Fiber Ring configurations
• Single (1x4-Fiber) ADM chain and Single (1x4-Fiber) Ring configuration
• Single (1x4-Fiber) with linear 1+1 configuration
• Single (1x4-Fiber) with unprotected 10G facilities
• Single (1x4-Fiber) with linear 1+1 configuration and unprotected 10G
facilities
When the network element is equipped with DX65 or DX100 switch modules,
the network element supports a single 4-Fiber ring on the 10 Gbit/s protection
group G11/G17 working and G12/G18 protection. When the network element
is equipped with DX140 switch modules, the network element can support up
to two 4-Fiber rings. One 4-Fiber ring can be supported on protection group
G11/G17 working and G12/G18 protection. The other 4-Fiber ADM can be
supported on protection group G0/G9 working and G10/G19 protection. Each
of the 4-Fiber configurations can be configured as a 4-Fiber Ring or a 4-Fiber
ADM chain configuration.

The protection switching for the single 4-Fiber Ring can be based on either
MS-SPRing protocol or head-end ring switching (HERS) protocol. The HERS
protocol is targeted for large rings with a ring circumference greater than 1200
km. When there is a ring switch (due to a node failure or total span failure), the
HERS protocol uses the shortest direct path to reroute the traffic so that signal
transmission delay is minimized. Typical application of the HERS feature
would be on transoceanic and transcontinental on single 4-Fiber Rings.
The default protection switching protocol is MS-SPRing and can be changed

to HERS from the OPC user interface.
On single 4-Fiber configurations, you can map tributary traffic to either the
working 10 Gbit/s lines or to the protection 10 Gbit/s lines (as ring extra
traffic). When a protection switch occurs, the affected extra traffic drops from
the protection 10 Gbit/s line and the working traffic is switched to the
protection 10 Gbit/s line. This results in the loss of any affected extra traffic.
This applies to both MS-SPRing and HERS protocols. The MS-SPRing
protocol uses all of the network elements to switch protected traffic.
Single (1x4-Fiber) and Dual (2x4-Fiber) Linear ADM chain configuration

A single 4-Fiber ADM chain configuration can contain up to 24 ADMs and
optional regenerators (Regens)/Line amplifiers in between ADM spans.
the network element can support a single 4-Fiber ADM chain. The network
element must be equipped with four STM-64 optical interfaces in 10 Gbit/s
protection group G11/G17 working and G12/G18 protection (see Figure 4-1
on page 4-6).
When the network is equipped with DX140 switch modules, the network
element can support up to two 4-Fiber ADM chains. To support two 4-Fiber
ADM chains, the network element must be equipped with eight STM-64
optical interfaces. One 4-Fiber ADM chain is supported with four STM-64
optical interfaces in protection groups G11/G17 working and G12/G18
protection. The other 4-Fiber ADM chain is supported with four STM-64
optical interfaces in protection groups G0/G9 working and G10/G19
protection (see Figure 4-2 on page 4-7).
Note 1: The network element must be equipped with DX140 switch

modules to support STM-64 optical interfaces in 10 Gbit/s protection
group G0/G10 and G9/G19.
Note 2: When the network element is equipped with DX140 switch
modules, there is no restriction on which ADM chain you can equip first.
The 4-Fiber ADM chain uses MS-SPRing protocol with one span left open at
the end nodes. The traffic protection of the 4-Fiber ADM chain is similar to
that of a single 4-Fiber Ring, except that the ring switching of the system is

disabled. The application of a global lockout using the OPC command (Global
Lockout Working) prevents ring switching. This command performs a
lockout of working traffic (ring) at all the ADMs in the single 4-Fiber ADM
chain. As a result, only span switching is available for traffic protection in
4-Fiber ADM chain.
Note 1: The network element supports intra-chain (within the same ADM
chain) and inter-system (across two systems) connections.
Note 2: The OPTera Connect DX network element must be either SONET
only or SDH only.
Interworking with 4-Fiber ADM chain
A 4-Fiber ADM chain can comprise of:
• OPTera Connect DX Release 6.0 network element configured to support a
4-Fiber ADM chain
• Optical Cross Connect HDX or HDXc network element configured with a
4-Fiber ADM chain
• TN-64X Regen network element running OPTera Connect DX Release 6
software
• if required, OPTera Long Haul 1600 and MOR amplifier networks between
the ADMs to provide optical signal amplification and regeneration
The supported tributary interfaces and their protection schemes of the OPTera
Connect DX network element are the same and independent of the 10 Gbit/s
configurations (see Tributary circuit packs and protection schemes on page
4-35).

Figure 4-1
Single 4-Fiber ADM chain configuration
DX0499_SDH
OPC Node A W W G11 Node B

G17
P PP G12
G18 P
G11 G12 G18 G17
F F PP W
F F PP W
G17 G18 G12 G11
P P G18
G12 P P
W W
Node D G11 G17 Node C
Legend
= STM-64 traffic path
F = Filler

Figure 4-2
Two 4-Fiber ADM chains, using the DX_HUB network element as a 2x4-Fiber ADM
DX5382p
Node
G11 F F G17 A
Node
C OPC
F
G12 F G18
G17 G18 G12 G11
W P P W
Chain 1
2X4-Fiber ADM
G12 G18
P P
Node B
OPC
W G11 G17 W
W G9 G0 W
P P
G19 G10
Chain 2
W P P W
G11 G12 G18 G17
G18 F F G12
Node Node
D G17 G11
F F E
OPC
Legend:
= 10 Gbit/s traffic path

F = Filler
Note : The illustration shows protection group G11/G12 and G17/18 in nodes A, C, D and E.
This illustration also applies to protection group G0/G10 and G9/G19.

Single 1x4-Fiber and 2x4-Fiber Ring configurations

The single 4-Fiber Ring configuration contains a maximum of 24 ADMs and
optional Regens/Line amplifiers in between ADM spans.
the network element can support a single 4-Fiber Ring. The network element
must be equipped with four STM-64 optical interfaces in 10 Gbit/s protection
group G11/G17 working and G12/G18 protection (see Figure 4-3 on page
4-10).
element can support up to two 4-Fiber Rings. To support two 4-Fiber Rings,
the network element must be equipped with eight STM-64 optical interfaces.
One 4-Fiber Ring is supported with four STM-64 optical interfaces in
protection groups G11/G17 working and G12/G18 protection. The other
4-Fiber Ring is supported with four STM-64 optical interfaces in protection
group G0/G9 working and G10/G19 protection (see Figure 4-4 on page 4-11).
Note 1: The network element must be equipped with DX140 switch

modules to support STM-64 optical interfaces in 10 Gbit/s protection
group G0/G10 and G9/G19.
Note 2: When the network element is equipped with DX140 switch
modules, there is no restriction on which ring you can equip first.
Note 3: The network element supports intra-ring (within the same ring)
and inter-system (across two systems) connections.
only or SDH only.
The protection switching protocol on one ring is independent of the other ring
and each ring can operate independently under the MS-SPRing or HERS
protocol.
Note: Time slot inter-change (TSI) for inter-ring extra traffic is not
supported on OPTera Connect DX network elements (same 10 Gbit/s
channels must be used for end-to-end extra traffic connections traversing
multiple 4-Fiber configurations).
To protect the inter-ring traffic from node failures, OPTera Connect DX

Release 6.0 supports MS-switched matched nodes (see Figure 4-5 on page
4-12). In this example, the MS-switched matched node is shown with two
2x4-Fiber ADMs. At the secondary gateway, you do not need back-to-back
tributaries (STM-1, STM-4, or STM-16) because connections can be made on
the switch modules. At the primary gateway, you need tributary loopbacks on
the protected tributaries and back-to-back tributaries on the working
tributaries.

Note: MS-switched configurations are not supported on rings configured

with HERS protocol.
Interworking with 4-Fiber Ring
A 4-Fiber Ring can comprise of:
4-Fiber ADM and the same switching protocol (MS-SPRing or HERS)
• Optical Cross Connect HDX and HDXc network element configured with
a 4-Fiber ADM (ring with MS-SPRing protocol only)
software
4-35).

Figure 4-3
Single 4-Fiber Ring
DX0497_SDH
OPC Node A W W G11 Node B

G17
P PP G12
G18 P
G11 G12 G18 G17
WWw PP PP W
W PP PP W
G17 G18 G12 G11
P P G18
G12 P P
W W
Node D G11 G17 Node C
Legend
= STM-64 traffic path

Figure 4-4
Dual 4-Fiber Rings with a network element configured as a 2x4-Fiber ADM
DX5383p
Node G11 W W G17

Node
C A
OPC
G12 P P G18
G17 G18 G12 G11
W P P W
2X4-Fiber ADM
G12 G18
P P
W G11 G17 W
Node B
OPC
W G9 G0 W
G19 G10
P P
Ring B
W P P W
G11 G12 G18 G17
G18 P P G12
Node
D
Node
OPC G17 G11 E
W W
Legend
Note : The illustration shows protection group G11/G12 and G17/18 in nodes A, C, D and E.

Figure 4-5
Interconnected rings with matched nodes connections using 2x4-Fiber ADM
configurations
DX4183t
Tributary
Connection
G1 G3
G2 G4
2x4-Fiber ADM
Primary
End A Gateway End B
2x4-Fiber ADM
Secondary
Gateway
Single (1x4-Fiber) ADM chain and Single (1x4-Fiber) Ring configuration

The OPTera Connect DX Release 6.0 network element can be configured to
support mixed configuration of single (1x4-Fiber) ADM chain and single
(1x4-Fiber) Ring on the same network element (see Figure 4-6 on page 4-13).
The 4-Fiber Ring and 4-Fiber ADM chain operates independently and
intra-system (within the same system) and inter-system (across two systems)
connections are supported. The 4-Fiber Ring configuration can be MS-SPRing
or HERS protocol. For more information on 4-Fiber Ring, refer to Single
1x4-Fiber and 2x4-Fiber Ring configurations on page 4-8. The 4-Fiber ADM
chain can be MS-SPRing only. For more information on 4-Fiber ADM chain,
refer to Single (1x4-Fiber) and Dual (2x4-Fiber) Linear ADM chain
configuration.

Figure 4-6
Mixed 4-Fiber ADM chain and 4-Fiber MS-SPRing with a network element configured as a
2x4-Fiber ADM
DX5384p
Node
G11 F F G17 A
Node
C OPC
G12 F ADM Chain F G18

G17 G18 G12 G11
W P P W
2X4-Fiber ADM
G12 G18
P P
Node B
OPC
W G11 G17 W
W G9 G0 W
P P
G19 G10
Ring
W P P W
G11 G12 G18 G17
G18 P P G12
Node
D
OPC G17 G11 Node
W W E
Legend
F = Filler
Note: The illustration shows protection group G11/G12 and G17/18 in nodes A, C, D and E.

2-Fiber Ring configurations and protection switching

10 Gbit/s configurations on the same network element. The following 2-Fiber
Ring configurations and protection switching are supported:
• Single 2-Fiber Ring
• Multiple Nx2-Fiber Rings (where N is 1, 2, 3 or 4)
• Multiple Nx2-Fiber Ring with single 4F ring or Chain (where N = 1 or 2)
• Multiple Nx2-Fiber Ring with 10G Mx1+1 (where N is 0 to 4 and M = (8
- (2xN))/2])
• Multiple Nx2-Fiber Ring with unprotected 10G Mx0:1 (where N is 0 to 2
and M = 4 - (2xN))
• Multiple Nx2-Fiber Ring, 10G Mx1+1 and unprotected 10G Mx0:1 (where
N is 0 to 4, M is 0 to 4 and K = 8 - 2x(N+M))
The protection switching for the single 2-Fiber Ring can be based on either
MS-SPRing protocol or HERS protocol. The HERS protocol is targeted for
large rings with a ring circumference greater than 1200 km. When there is a
ring switch (due to a node failure or total span failure), the HERS protocol uses
the shortest direct path to reroute the traffic so that signal transmission delay
is minimized. Typical application of the HERS feature would be on
transoceanic and transcontinental on single 2-Fiber Rings.
The default protection switching protocol is MS-SPRing and can be changed

to HERS from the OPC user interface.
On single 2-Fiber configurations, you can map tributary traffic to either the
working or protection (as ring extra traffic) bandwidth of the 10 Gbit/s lines.
When a protection switch occurs, the affected extra traffic drops from the
protection bandwidth and the working traffic is switched to the protection
bandwidth. This results in the loss of any affected extra traffic. This applies to
both MS-SPRing and HERS protocols. The MS-SPRing protocol uses all of
the network elements to switch protected traffic.
Note: Time slot inter-change (TSI) for inter-ring extra traffic on the
OPTera Connect DX network element is not supported (same 10 Gbit/s
channels must be used for end-to-end extra traffic connections traversing
multiple 2-Fiber configurations).
Single 2-Fiber Ring
The single 2-Fiber Ring configuration can consists of up to a maximum of 24
2-Fiber ADMs.
Note: The TN-64X network element does not support 2-Fiber ADM
network element types.

When you configure a protection group of the OPTera Connect DX network

element to support a single 2-Fiber Ring ADM node, the protection group is
equipped with two STM-64 optical interfaces, each carrying both working and
protection traffic (see Figure 4-7 on page 4-16).
Multiple Nx2-Fiber Rings (where N is 1, 2, 3 or 4)
the network element can support up to two 2-Fiber Rings. To support two
2-Fiber Rings, the network element must be equipped with four STM-64
optical interfaces in 10 Gbit/s protection groups G11/G12 and G17/G18.
When the network element is equipped with DX140 switch modules, the
network element can support up to four 2-Fiber Rings. To support four 2-Fiber
Rings, the network element must be equipped with eight STM-64 optical
interfaces in 10 Gbit/s protection groups G11/G12, G17/G18, G0/G10 and
G9/G19. (see Figure 4-8 on page 4-17).
Note 1: The network element supports intra-ring (within the same ring)
and inter-system (across two systems) connections.
only or SDH only.
The protection switching on one ring is independent of the other ring and each
ring can operate independently under the MS-SPRing or HERS protocol.
To protect the inter-ring traffic from node failures, OPTera Connect DX

Release 6.0 supports MS-switched matched nodes (see Figure 4-9 on page
4-18). In this example, the MS-switched matched node is shown with two
2x2-Fiber ADMs. At the secondary gateway, you do not need back-to-back
tributaries (STM-1, STM-4, or STM-16) because connections can be made on
the switch modules. At the primary gateway, you need tributary loopbacks on
the protected tributaries and back-to-back tributaries on the working
tributaries.
Note: MS-switched configurations are not supported on rings configured

with HERS protocol.
Interworking with 2-Fiber Rings
A 2-Fiber Ring can comprise of
2-Fiber ADM and the same switching protocol (MS-SPRing or HERS)
software

4-35).
Figure 4-7
Single 2-Fiber MS-SPRing
DX3338
W/P
W/P
2-Fiber ADM 2-Fiber ADM
W/P W/P
W/P W/P

W/P
W/P
Legend:
ADM = add/drop multiplexer
W/P = working/protection

Figure 4-8
Interconnecting four 2-Fiber ADMs through an OPTera Connect DX network element
DX3234p
Node B
Working/protection Working/protection
2-fiber
ADM
Node A Node C
2-fiber 2-fiber
Node K ADM ADM Node E
2-fiber 2-fiber
ADM Working/protection Working/protection ADM
Working/protection Node D Working/protection
Node M Working/protection Working/protection Node F
2-fiber 2-fiber
ADM ADM
Working/protection Working/protection
Working/protection 4x2-fiber Working/protection
Working/protection ADM Working/protection
2-fiber 2-fiber
ADM ADM
Node J Node H
2-fiber 2-fiber
Node L ADM ADM Node G
Working/protection Node I Working/protection
2-fiber
ADM

Figure 4-9
Example of MS-switched matched nodes with a 2x2-Fiber Ring configuration
DX3233t
Tributary
Connection
G1 G3
G2 G4
2x2-Fiber ADM
Primary
End A Gateway End B
2x2-Fiber ADM
Secondary
Gateway
10 Gbit/s unprotected configuration

10 Gbit/s configurations on the same network element. When the network is
equipped with DX65 or DX100 switch modules, the network element can
support up to 4 unprotected 10 Gbit/s terminals in G11, G12, G17 and G18.
element can support up to eight unprotected 10 Gbit/s terminals in G0, G9,
G10, G11, G12, G17, G18 and G19.
The STM-64 T/R interfaces can be arranged into four groups; G11/G12,
G17/G18, G0/G10 and G9/G19. You can provision any or all of the groups as
unprotected 10 Gbit/s terminals. When you provision a group to operate in the
unprotected mode, the two STM-64 T/R interfaces of the group operate
independently.
You can connect the unprotected STM-64 T/R interfaces to any 10 Gbit/s
interfaces.This fulfills the growing need to carry super rate payloads of next
generation 10 Gbit/s routers.

Interworking with unprotected 10 Gbit/s interfaces

The unprotected 10 Gbit/s interfaces can interwork with:
• other 10 Gbit/s interfaces
• 10 Gbit/s router.
The supported tributary interfaces and the tributary protection schemes of the
OPTera Connect DX network element are the same and independent of the
10 Gbit/s configurations (see Tributary circuit packs and protection schemes
on page 4-35).
Figure 4-10
Example of a network using unprotected line and tributaries
DX5385p
DX Unprotected DX Unprotected
2.5G Interface Interface
traffic
10G
DX Unprotected DX Unprotected DX Unprotected

Interface Interface Interface Ring ADM
2.5G 10G 2x4-Fiber

Ring
DX NE
Legend
= OPC SOC
= ATM switch
= IP Router

10 Gbit/s Linear 1+1 configuration

OPTera Connect DX Release 6.0 supports mixed 10 Gbit/s configurations
including 10 Gbit/s Linear 1+1 terminals on the same OPTera Connect DX
network element. When the network is equipped with DX65 or DX100 switch
modules, the network element supports up to two Linear 1+1 terminals on
protection groups G11/G12 and G17/G18. When the network is equipped with
DX140 switch modules, the network element supports up to four Linear 1+1
terminals on the protection groups G11/G12, G17/G18, G0/G10 and G9/G19.
You can provision any or all of the groups (G11/G12, G17/G18, G0/G10 and
G9/G19) to operate in a Linear 1+1 mode (see Figure 4-11 on page 4-21).
When you provision a group to operate in the Linear 1+1 mode, one of
STM-64 interfaces (G0, G9, G11 or G17) is the working channel and the other
STM-64 interface (G10, G19, G12 or G18) is the protection channel.
Note: The 10 Gbit/s Linear 1+1 terminal can be configured as

point-to-point route diversity enabled systems only.
Interworking with 10 Gbit/s terminal
The 10 Gbit/s Linear 1+1 terminal can interwork with:
• other OPTera Connect DX 10 Gbit/s Linear 1+1 terminals
• Optical Cross Connect HDX and HDXc configured with 10 Gbit/s Linear
1+1 terminals
• other vendors 10 Gbit/s Linear 1+1 terminals
• 10 Gbit/s routers
4-35).

Figure 4-11
Example of an OPTera Connect DX network element showing Linear Nx(1+1)
configurations where N is 4.
DX4638p
Other vendor
10 Gbit/s NE LTE NE
4 1
G0/G10 G11/G12
5
G9/G19 G17/G18
3 2
DX_HUB HDX NE
10 Gbit/s 4x (1+1) DX_HUB
Legend
LTE = Line-terminating equipment
DX_HUB = DX_HUB network element
NE = Network element
= Span of control boundaries
Subtending sub-network connection protection ring

The subtending sub-network connection protection (SNCP) ring feature
supports STM-4, and STM-16 subtending SNCP rings on the OPTera Connect
DX network element. The other nodes of the subtending SNCP rings can be
from Nortel and other ITU-T G.841 compliant vendors. The OPTera Connect
DX network element supports multi-SNCP ring protection groups on the
unprotected tributaries. The SNCP ring feature eliminates the need to connect
the head-end network element to the OPTera Connect DX bay through
back-to-back tributaries. You can connect the SNCP ring directly on the
tributaries of the OPTera Connect DX bay (Figure 4-12 on page 4-22). This
results in reduced space, cost and power utilization.

Figure 4-12
Subtending SNCP ring support
DX5379t
Pre-DX release 4.0 DX release 4.0 or higher

DX
network
element
Head-end DX
network network
element element
STM-1/
STM-4
STM-16 Subtending STM-16 Subtending
SNCP ring SNCP ring
The SNCP ring involves bridging the signal at the entry node. Then, the signal
is routed in both directions around the ring to the exit node. At the exit node,
the better signal quality of the two paths is selected (Figure 4-13 on page 4-22).
Figure 4-13
Example of a SNCP ring
DX3966t
STM-16 NE
Node B
STM-16 NE STM-16 NE
Node A Node C
Sub-network connection
protection (SNCP) ring
STM-16 NE
Node D

The SNCP ring enables various applications for subtending SNCP rings. A
single OPTera Connect DX network element can terminate several SNCP ring
systems, as well as provide unrestricted hairpinning across all SNCP rings in
a non-blocking fashion.
Subtending STM-16 2-Fiber multiplexer section shared protection rings

The subtending STM-16 2-Fiber multiplexer section shared protection ring
(MS-SPRing) feature supports STM-16 subtending 2-Fiber MS-SPRings of
Nortel network elements only. The subtending STM-16 2-Fiber MS-SPRing is
compliant to ITU-T G.783 section 6.4, ITU-T G.841 section 7.4 and ETSI EN
300417-4-1 V1.1.3 (1999-05).
The OPTera Connect DX network element supports multiple 2-Fiber

MS-SPRing protection groups on its unprotected STM-16 tributaries. The
subtending 2-Fiber Ring feature eliminates the need to connect the STM-16
2-Fiber Ring head-end network element to the OPTera Connect DX network
element through back-to-back tributaries. You can connect the STM-16
2-Fiber Ring directly on the STM-16 tributaries of the OPTera Connect DX
network element (see Figure 4-14 on page 4-24). This results in reduced space,
cost and power utilization.
The subtending STM-16 2-Fiber MS-SPRing feature allows the network

element to be a node of a STM-16 2-Fiber Ring. The 2-Fiber Ring can be a
subtending tributary ring of a 10 Gbit/s network or a standalone ring. The
2-Fiber Ring can include subtending 2-Fiber nodes of OPTera Connect DX
network elements and TN-64X or Optical Cross Connect HDX and HDXc
network elements.

Figure 4-14
Subtending STM-16 2-Fiber MS-SPRing support
DX5381t
Pre-OPTera Connect DX OPTera Connect DX

Release 5.0 Release 5.0 or higher
OPTera
Connect DX
network
element
OPTera
Connect DX
Head-end network
network element
element
STM-1/
STM-4
STM-16 2-Fiber STM-16 Subtending
MS-SPRing 2-Fiber MS-SPRing
Legend
MS-SPRing - Multiplexer section shared protection ring
Supported subtending STM-16 2-Fiber MS-SPRing configurations

STM-16 2-Fiber MS-SPRing can include the following network elements:
• OPTera Connect DX Release 5.0 and above network elements only
• a mix of TN-16X (Release 9 and above) and OPTera Connect DX Release
5.0 or above network elements
• Optical Cross Connect HDX Release 2.0 and above
• Optical Cross Connect HDXc Release 2.11 and above
When TN-16X network elements are used with an OPTera Connect DX

network element in a subtending 2-Fiber Ring, the following conditions must
be satisfied for proper operations:
• The TN-16X network elements adjacent to OPTera Connect DX network
elements must contain NT8E06AB or NT8E06AD demux circuit packs in
both G1 and G2.

• The transmit interface circuit pack on the group of the TN-16X network
element that is connected to the STM-16 interface of the OPTera Connect
DX network element, must be equipped with TSI2 or EMTSI ASIC.
• The Kbyte compliance on all the TN-16X network elements in the 2-Fiber
Ring must be set to ON to ensure proper protection switching operation.
Figure 4-15 on page 4-26 shows examples of subtending STM-16 2-Fiber
MS-SPRing using regular and hairpin connections. The examples shown are:
• An application using normal ring connections. The traffic from subtending

Ring A in location A is connected to subtending Ring F in location B, via
the OPTera Connect DX backbone network.
• An application using two adjacent OPTera Connect DX STM-16 tributary
ports as a virtual ring node in passthrough mode. This application bypasses
the 10 Gbit/s facilities (see Ring C at location A).
• An application using the DX_HUB network element as a cross-connect.
This application enables traffic from one subtending ring to be connected
to another subtending ring on the same OPTera Connect DX network
element, via tributary-to-tributary hairpin connections. The hairpin
connections do not use the 10 Gbit/s line bandwidth (see Ring E and Ring
G at location B).
Figure 4-16 on page 4-27 shows an example of subtending 2-Fiber
MS-SPRing using STM-16 interfaces of the OPTera Connect DX network
element.
Figure 4-17 on page 4-28 shows an example of a STM-16 2-Fiber MS-SPRing

using OPTera Connect DX network elements only.

Figure 4-15
Example of subtending STM-16 2-Fiber MS-SPRing using regular hairpinning connections
DX4555p
OPTera Connect DX OPTera Connect DX

ADM ADM
STM-16 2-Fiber STM-16 2-Fiber

MS-SPRing A MS-SPRing D
STM-16 2-Fiber
Backbone MS-SPRing E
Networks
STM-16 2-Fiber (see note)
MS-SPRing B
STM-16 2-Fiber
MS-SPRing F
STM-16 2-Fiber STM-16 2-Fiber

MS-SPRing C MS-SPRing G
Location A Location B
Legend

= hairpin connections
Note: The backbone network can be a 2FR, 4FR, 1+1 or 0:1 10G networks,
2.5G 2FR MS-SPRing, STM-4/STM-16 SNCP Ring or STM-1/STM-4/STM-16
(1+1 or 0:1)networks

Figure 4-16
Example of subtending 2-Fiber MS-SPRing using OPTera Connect DX STM-16 interfaces
STM-16 2FR STM-16 2FR

MS-SPring MS-SPring
OPTera
Connect DX
network element
STM-16 2FR STM-16 2FR

MS-SPring MS-SPring
Legend
= STM-64 rate
= STM-16 rate
= STM-16 interface
= TN-16X network element
A single OPTera Connect DX network element can terminate several STM-16

2-Fiber MS-SPRing systems, as well as provide unrestricted hairpinning
across all STM-16 2-Fiber MS-SPRing in a non-blocking fashion.

Figure 4-17
Example of a standalone 2-Fiber Ring consisting of TN-16X and OPTera Connect DX network
elements
DX4626p
2-Fiber MS-SPRing can have a mix

of Classic TN-16X network element
and interface pairs of OPTera
Connect DX network element DX
NE
TN-16X STM 2-Fiber Ring connected to DX

NE OPTera Connect DX tributaries NE
TN-16X
NE
Legend
DX NE = OPTera Connect DX network element
= STM-16 rate
= STM-16 interface

Shelf configuration rules

Table 4-1 on page 4-29 shows the maximum number of subtending STM-16
2-Fiber MS-SPRing that can be supported on different OPTera Connect DX
network element configurations.
Table 4-1
Maximum number of subtending STM-16 2-Fiber MS-SPRing on OPTera
Connect DX network element and different switch modules
Switch OPTera Connect network element configuration

modules
Low-speed OPTera Connect DX Bay
cross-connect Metro
DX65 4 4 4
DX100 20 8 20
DX140 28 N/A 28
When the network element is equipped with DX100 or DX140 switch

modules, the network element supports Quad STM-16 in the universal slots
and Dual STM-16 circuit packs in the main transport shelf only.

STM-16 2-Fiber MS-SPRing reconfiguration

OPTera Connect DX Release 6.0 supports the following STM-16 2-Fiber
MS-SPRing network reconfigurations:
• Collapsing head-end STM-16 2-Fiber MS-SPRing node into OPTera
Connect DX network element. The steps for the collapsing the head-end
network element into the OPTera Connect DX network element are
outlined in a Nortel Change Application Procedure (CAP). This CAP must
be performed by Nortel trained personnel only.
• Adding a tributary pair to a subtending STM-16 2-Fiber MS-SPRing. The
steps for adding a tributary pair to a subtending STM-16 2-Fiber
MS-SPRing are outlined in a CAP. This CAP will be made available upon
customer request.
• Adding/Deleting a Classic TN-16X 2-Fiber Ring ADM to/from ring
comprised of a mix of Classic TN-16X 2-Fiber Ring ADMs and OPTera
Connect DX tributary STM-16 2-Fiber Ring pair(s) is supported. The
associated CAP will be made available upon customer request.
• In-service traffic rollover of STM-16 2-Fiber MS-SPRing to STM-64
2-Fiber MS-SPRing. The steps for the rollover are outlined in a CAP. This
CAP must be performed by Nortel trained personnel only.
The following engineering rules and restrictions apply to the subtending
STM-16 2-Fiber Ring:
• Subtending STM-16 2-Fiber MS-SPRing are supported on OPTera
Connect DX network elements only.
• Subtending STM-16 2-Fiber MS-SPRing are not supported on TN-64X
network elements.
• The 2-Fiber MS-SPRing is supported on optical STM-16 interfaces only.
• A maximum of 16 Ring ADM nodes is supported on a subtending STM-16
2-Fiber MS-SPRing.
• The 2-Fiber Ring ADM node on the OPTera Connect DX network element
must use two adjacent STM-16 interfaces of the same port numbers of the
same type of circuit packs. For Dual STM-16 circuit packs, short reach,
intermediate reach and long reach are considered as the same type of
circuit pack.
• Intra-ring timeslot interchange is not allowed.
• Extra traffic is not supported on interfaces participating in a subtending
STM-16 2-Fiber MS-SPRing
• SNCP Ring connections cannot be provisioned on interfaces participating
in a subtending STM-16 2-Fiber MS-SPRing
• STM-16 interfaces, which are part of a STM-16 2-Fiber MS-SPRing,
cannot be the primary or secondary gateway for a matched line connection.

• Preprovisioning is not supported. If an interface pair was provisioned as

the MS-SPRing protection scheme, connections to this tributary are
blocked until the interfaces are added to a configuration.
• An STM-16 2-Fiber MS-SPRing can be connected to an OPTera Connect
DX network element by only one STM-16 MS-SPRing interface pair (for
example, each interface pair of the same OPTera Connect DX network
element must be in a different subtending ring).
• Renumbering of the network elements configured in subtending STM-16
2-Fiber Rings is not supported.
• Audit correction for configuration audit between spans of control is not
supported. Mismatches must be corrected manually on the appropriate
OPC.
• Connection audit is not supported for 2-Fiber Ring with TN-16X and
OPTera Connect DX network elements.
• In-service tributary rollover is not supported for STM-16 MS-SPRing
tributary pairs.
• In-service channel rollover (ISCR) and in-service route rollover (ISRR)
are not supported for connections which include STM-16 MS-SPRing
interface pairs.
• When you configure a subtending STM-16 2-Fiber MS-SPRing with
OPTera Connect DX and TN-16X network elements, you must do the
following:
— equip both G1 and G2 of the TN-16X network element that is
connected to the OPTera Connect DX network element with either
NT8E06AB or NT8E06AD demultiplexer circuit packs.
— equip the group of the TN-16X network element that is connected to
the OPTera Connect DX network element with transmit interface
circuit pack that contains Ring TSI2 or EMTSI ASIC. If the transmit
interface circuit pack contains Ring TSI1 ASIC, the subtending ring
will not function correctly. Refer to Table 4-2 on page 4-32 for a list of
the transmit interface circuit packs and vintages with Ring TSI1 ASIC
which are not suitable for subtending STM-16 MS-SPRing
application.
— set the KByte compliance on all TN-16X network elements in the
subtending ring to ON. The default setting of the KByte compliance is
OFF.
Note: If the conditions of this bullet are not met, the subtending ring will
not function correctly.

Table 4-2
TN-16X transmit interface circuit pack with Ring TSI1 ASIC
PEC Vintages that contain Ring TSI1 ASIC
NT8E01BA 1, 3, 4, 5, 6, 10, 11, 12, 13, 14
NT8E01BB/BC 1, 2, 3, 4, 5, 6, 10, 11, 12, 13, 14
NT8E01KB/KC/KD 1, 2, 3, 4, 8, 9, 10, 11, 12
NT8E01BD 4, 6, 10, 12, 14
NT8E01PA 11, 12, 13, 14, 15, 16, 17
NT8E01PB 11, 12, 13, 14, 15, 16, 18, 19, 20, 21, 22, 23
NT8E01PC 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23
NT8E01PD 12, 13, 15, 16, 18, 19, 20, 21, 22, 23
NT8E01QB/QC/QD 9, 10, 11, 12, 13, 14, 16, 18, 19, 20, 21, 22
NT8E01LB/LC/LD 1, 2, 3, 4, 5, 6, 7, 8
NTFW01AB 1, 2, 3, 4, 5, 6, 7, 8, 9, 11
NTFW01AD 6, 7, 8, 9, 11
NTFW01DB 1, 2, 3, 4, 5, 6, 7, 8
NTFW01DD 5, 6, 7, 8, 10
NT8E11DQ 2, 3, 4
NT8E11FQ/HR/KQ/MQ/MR/TR/VQ 1, 2, 3, 4, D02
NT8E11KR/RR 2, 3
Tributary hairpinning application

The hairpinning configuration consists of tributary-to-tributary STM
connections on the same network element without using any high-speed
bandwidth.
The hairpinning configuration allows you to utilize the OPTera Connect DX

and TN-64X bays as a full cross-connect bandwidth manager, offering total
flexibility in provisioning channelized services. Back-to-back tributaries on
subtending equipment are no longer necessary (Figure 4-18 on page 4-33).
The hairpinning configuration does not compromise any high-speed

bandwidth. You can provision full hairpinning on a network element while
allowing full passthrough connections on the same network element, thereby
taking full advantage of the bandwidth available on OPTera Connect DX and
TN-64X bays.

Hairpinning is supported on STM-1, STM-4, STM-16, and Dual GE

tributaries. Hairpinning is supported on the OPTera Connect DX and TN-64X
bays regardless of the switch module that is present. You can provision
individual VC-4 connections or concatenated connections.
Figure 4-18
Example of OPTera Connect DX as a fully protected cross-connect
DX2577p
Cross-connect
STM-16 functionality
Back-to-Back tribs
No longer needed STM-1
STM connections
STM-16
STM-4
DX Ring
STM-1
Tributary-to-tributary hairpinning applications are also supported on SNCP

Ring and subtending 2-Fiber Ring configurations. Figure 4-19 on page 4-34
displays an example of hairpin connections for SNCP rings that allows traffic
from one SNCP ring to be dropped at another SNCP ring on the same OPTera

Figure 4-19
Example of hairpin connections for SNCP rings at a OPTera Connect DX node
DX4042p
To other node
of the ring or
ADM chain
STM-16 NE
STM-16 NE DX NE
Node A Node Z
STM-16 DX switch
trib module
STM-1/ Subtending
STM-4 Sub-network connection
protection (SNCP) ring 10G T/R
line
STM-16 NE
STM-16 NE
STM-16 NE
Node A
STM-16
trib
STM-1/ Subtending
STM-4 Sub-network connection
protection (SNCP) ring 10G T/R
line
STM-16 NE
To other node
of the ring or
ADM chain

Low-speed cross-connect application

The low-speed cross-connect application is only supported on the OPTera
Connect DX network element running Release 3 or higher. In this application,
the OPTera Connect DX network element uses the hairpinning feature to make
the tributary cross-connections. The hairpinning feature allows:
• interconnection of any VC-4 connections to any other VC-4 connections
on the same network element
• interconnection of any VC-4 concatenated connections to any other VC-4
concatenated connections of the same rate on the same network element
Low-speed cross-connection is supported with STM-1o/e, STM-4, STM-16
and GE tributaries. In the low-speed cross-connection application, the network
element is not equipped with STM-64 T/R circuit packs.
Note: Since OPTera Connect DX Release 5.0 STM-64 T/R circuit pack are
no longer required for system lineup and testing (SLAT).
Tributary circuit packs and protection schemes

OPTera Connect Release 6 supports the same tributary interfaces and
protection schemes for all 10 Gbit/s configurations and low-speed
cross-connect applications.
Tributary interfaces
The supported tributary interfaces and equipping shelf rules are:
• STM-16 interfaces (main and extension shelves)
• Dual STM-16 interfaces (main shelf only)
• Quad STM-16 interfaces (main shelf only)
• Quad STM-4 interfaces (main and extension shelves)
• Quad STM-1 interfaces (main and extension shelves)
• HD STM-1 interfaces (main and extension shelves)
• Dual Gigabit Ethernet interfaces (main and extension shelves)
Note 1: The network element must be equipped with DX100 or DX140
switch modules to support traffic on the extension shelf.
switch modules to support the Quad STM-16, Dual STM-16 and HD
STM-1 circuit packs.
switch modules to support tributary traffic in the universal slots.
Protected tributaries
Table 4-3 list the OPTera Connect DX Release 6.0 low-speed interfaces and
their supported protection switching scheme.

Table 4-3
Tributary interfaces and supported protection schemes
Supported protection switching schemes
Tributary interfaces 1*1 1+1 0:1 SNCP Ring 2F

(revertive) (revertive or (unprotected) MS-
non-revertive SPRing
STM-16 Yes Yes Yes Yes Yes
Dual STM-16 Yes Yes Yes Yes Yes
Quad STM-16 Yes Yes Yes Yes Yes
Quad STM-4 Yes Yes Yes Yes No
HD STM-1o Yes Yes Yes No No
HD STM-1e Yes Yes Yes No No
Quad STM-1o Yes Yes Yes No No
Quad STM-1e Yes Yes Yes No No
Dual Gigabit Ethernet No No Yes No No
Note 1: The 1*1 protection scheme is used for the primary gateway MS-switched node configuration
only.
Note 2: The HD STM-1o circuit pack, NTCA35AA, does not support DCC, MS-switched nodes and
IPPM.
Mixed protected and unprotected tributaries

In OPTera Connect DX Release 6.0, the same network element can support
unprotected and protected tributaries on a port-basis. If the default protection
scheme of an interface is unprotected, the tributary interface provisions
automatically in unprotected CPG pairs. If the protection mode of a GPG of a
multiport circuit pack is unprotected, the circuit pack can support mixed
protected and unprotected facilities on the same circuit pack. If the default
protection scheme of an interface is protected, the tributary interfaces
provisions automatically in protection pairs according to its default protection
scheme when an interface circuit pack is inserted in a valid unprovisioned
tributary slot.
Tributary interfaces interworking with other Nortel network elements
Refer to OPTera Connect DX Release 6.0 interworking in Chapter 3.
Level 2 routing
Network elements that operate within the same routing parameters are within
the same routing domain. A routing domain can be divided into level 1 routing
areas. Nortel supports up to 150 nodes in any given level 1 routing area.

Level 2 routing allows network elements in separate level 1 routing areas to

communicate through level 2 routers. This feature allows the size of the
Datacomm network to increase beyond 150 nodes.
Level 2 routing, as described in ISO 10589, allows level 2 routers to route

operations, administration and maintenance (OAM) messages between
different level 1 areas within a routing domain. Refer to Figure 4-20 on page
4-37 for an example of level 2 routing.
For detailed information about level 2 routing, refer to Optical Networks Data
Communications Planning Guide, NTR710AM. For more information on
Level 2 routing area unification, refer to Part 2 of Provisioning and Operations
Procedures, 323-1531-310 for the OPTera Connect DX platform.
Figure 4-20
Level 2 routing
DX0648
Level 2
router
Level 2
NE 3X router NE 3Y
NE 2X
NE 2Y
NE 4X ... NE
150X NE 4Y ... NE
150Y
NE 1X
Routing Area X NE 1Y Routing Area Y
Level 1 Level 1
Domain Z
Optical amplifier support

The distance between network elements in a transmission network increases
with the use of MOR (16 wavelengths), MOR Plus (32 wavelengths), and
OPTera Long Haul 1600G optical amplifiers (160 wavelengths). The MOR
Plus or OPTera Long Haul 1600G optical amplifiers are inserted in an OPTera

Long Haul 1600 network element bay. The OPTera Connect DX Release 5.0
software supports MOR and MOR Plus circuit packs inserted in existing
TN-64X network element bays.
For more details on optical amplifiers in a TN-64X system, refer to Crcuit
Pack Descriptions, 323-1511-102. For DWDM system applications from 2 to
32 wavelengths, refer to the Optical Networks Applications Library,
NTCA66BA. For 1600G applications, refer to the OPTera Long Haul 1600G
Amplifier Unidirectional Network Application Guide, NTY314AG.
OPTera Connect DX interoperability

Nortel has carefully designed the OPTera Connect DX network elements with
considerable emphasis on compliance to industry standards. Such standards
compliance is the basis for multi-vendor interoperability and, as a result,
mid-span meets between the OPTera Connect DX network elements and other
industry standard-compliant non-Nortel products are facilitated.
The following OPTera Connect DX interfaces can be connected to non-Nortel

equipment:
• tributary interface (STM-1, STM-4, STM-16, or Gigabit Ethernet) except
for STM-16 interfaces configured for subtending 2-Fiber Ring operation
• STM-64 interface (only for Linear 1+1 and unprotected)
Interoperability versus interworking
Nortel differentiates between interoperability and interworking as follows:
• interoperability is a mid-span meet application between a Nortel product
and another vendor product
• interworking is the mid-span meet application between one Nortel product
and another Nortel product
Levels of interoperability
There are three different levels of interoperability in a multi-vendor mid span
meet configuration: traffic and protection interoperability, operations,
administration, and maintenance (OAM) messaging and management
channels interoperability, and operation support system (OSS) interoperability.
Traffic and protection interoperability is the basic level that is required in

every multi-vendor mid span meet application. It is also a prerequisite to
successfully attain the other levels. Traffic continuity and integrity, as well as
payload protection, are achieved at this level.
OAM messaging and management channels interoperability, also referred to

as data communications channel (DCC) interoperability, is the ability of
network elements from different vendors to route each other’s OAM
messages. Examples of applications which use this level of interoperability are
remote login, TL1 messaging and software download.

OSS interoperability refers to the management of a multi-vendor network from

a single location. This level of interoperability is not addressed in this
document.
Automatic protection switching

Successful interoperability at this basic level depends on the automatic
protection switching (APS) mode of interest.
Linear interoperability
All linear APS modes are interoperable. It is important to ensure that both
vendors at each end of the mid-span meet are provisioned to operate in the
same APS mode. You must always change the tributary protection applicable
standard from TR253 to GR253 and disable the working channel K-byte
signaling when interoperating with another vendor at the tributary level.
Care must also be taken with respect to understanding the level of exerciser
support on non-Nortel equipment. Specifically, determine if the subtending
non-Nortel network element is capable of the following:
• providing a valid response to an exerciser request received via the K-bytes
• initiating an exerciser request through the K-bytes, and in which protection
mode it is supported (unidirectional or bidirectional)
Sub-network connection protection (SNCP) ring interoperability
The SNCP ring feature supports STM-4 and STM-16 subtending SNCP rings
from Nortel and other GR-1400/ITU-T G.841 compliant vendors. The SNCP
feature offers nonrevertive path protection switching at the VC-4 granularity
level. The following SNCP connection rates are supported: VC-4, VC-4-2c,
VC-4-4c, VC-4-8c, and VC-4-16c.
Multiplexer section shared protection ring (MS-SPRing) interoperability
On OPTera Connect DX Release 6.0 systems, MS-SPRing is supported only
on the STM-16 tributary interfaces and STM-64 line interfaces. Although the
K-byte protection protocols are well defined by standards, many crucial
aspects of MS-SPRing operations remain undefined. These undefined aspects
include Node ID and Squelch Table Management. Without a standardized
solution for these issues, no product from any vendor is ever MS-SPRing
interoperable with other products from another vendor. Therefore, the OPTera
Connect DX network element should never be provisioned in a MS-SPRing
ring consisting of non-Nortel equipment.
Head-end ring switching (HERS) interoperability
On the OPTera Connect DX systems, HERS is supported only on the 10 Gbit/s
facilities. Similar to MS-SPRing protocol, no product from any vendor is ever
HERS interoperable with other products from another vendor. Therefore, the
OPTera Connect DX network element should never be provisioned in a HERS
ring consisting of non-Nortel equipment.

SONET and SDH interoperability

This type of mid-span meet is when SONET equipment interoperates with
SDH equipment in a multi-vendor environment. This is typical of networks
that cross international borders. Due to the differences between SONET and
SDH standards interoperability is achievable if certain considerations are
taken. Furthermore, note that although there are several standards that consider
SONET or SDH applications, there is no standard that is dedicated to
interconnecting SONET and SDH network elements.
During any SONET and SDH mid-span meet applications, you must
• change the switch mode to unidirectional for tributary protection group
• change the switch mode to unidirectional for 10 Gbits Linear 1+1
protection group
• provision the tributary SS bits accordingly
Data communications channel (DCC) interoperability
Interoperation at the DCC level encompasses the ability of network elements
from different vendors to route each other’s operations, administration, and
maintenance (OAM) messages, and to discover each other for routing
purposes. Refer to the Data Communications Network Planning Guide,
NTR710AM, for additional information regarding DCC interoperability
considerations.
If the products to be interoperated are compliant to industry standards, then

DCC interoperability is usually achievable. However, because there are no
default standard values for certain open systems interconnect (OSI) stack
parameters and address fields, more often than not, these parameters must be
defined and provisioned across a mid-span meet in order to achieve
interoperability.
It is important to understand that the management communications network

comprised of the OSI stack and physical DCC links, actually functions
independently from the SONET, SDH, or optical network in which it exists.
Compliance to Industry Standards

Most SONET vendors, including Nortel, are compliant to Telcordia
GR-253-CORE Section 8 and Appendices C and D for their DCC OSI stacks.
Note that some vendors implement an IP based stack for their management
communications function. An IP based DCC stack will not interoperate with
an OSI DCC stack.
Any proprietary features, such as DCC tunneling, merit close customer

scrutiny. For example, there are different types of tunneling, and each has its
advantages and disadvantages to consider. Often, these type of proprietary
DCC features make use of the overhead byes already defined by standards,
such as the section DCC (D1-D3) or line DCC (D4-D12) bytes. This

proprietary overhead byte usage may cause interoperability issues in the event
that the bytes being used are required for the purpose that they were defined in
the standard.
OSI addresses and area addresses

Nortel OPTera Connect DX has an OSI DCC stack. Therefore it can
interoperate with any other non-Nortel equipment that is also OSI based.
Product vendors may supply default OSI area addresses but quite often these
addresses are different and do not have the common field values required to
successfully achieve management communications. Each network element
within a routing area must have at least one (out of a maximum of three) area
addresses in common.
Maximum number of network elements in a routing area
Each vendor specifies a maximum number of network elements per routing
area (also referred to as a Level 1 area) that their product supports. Nortel
OPTera Connect DX supports a maximum of 150 network elements in a
routing area. Standards do not specify a value for this important engineering
rule. As such, in a multi-vendor mid-span meet application, the lowest of each
of the different product’s maximums becomes the effective limit to adhere to.
Therefore, it is essential to ensure that the number of network elements in a
mixed vendor routing area does not exceed the lowest maximum number of
network elements per area limit as specified by each vendor.
For example, the maximum number of network elements in a routing area for
the OPTera Connect DX is 150 nodes. Consider a routing area that comprises
of some Nortel network elements and some non-Nortel network elements
whose maximum network elements per routing area is limited to 50.
Therefore, the maximum number of nodes allowed in this routing area is the
lowest of the two limits, which is 50 nodes.
Provisioning OSI stack parameters

As previously mentioned, there are several OSI stack parameters whose values
are not specifically defined in standards, and therefore need to be manually
provisioned at each end of the multi-vendor mid-span meet for successful
interoperability.
The link service data unit (LSDU) size must be the same value at each end of
the link. Usually, vendors have different values for this parameter and a
mismatch can prevent communications if not corrected by proper
provisioning.
Note: To ensure the best performance of the DCC link, the LSDU frame
size must be set to the largest common value supported by both vendor’s
network elements.

Enabling the DCC links

Vendors usually provide a means to enable or disable DCC communications
across a multi-vendor mid-span meet. Often this parameter may be defaulted
to disabled. The DCC link must be enabled at both ends of the mid-span meet
to achieve successful interoperability.
Within a SONET mid-span meet, DCC communications interoperability can

be achieved through either section or line DCC. The section DCC refers to
bytes D1-D3 of the section overhead, while line DCC refers to bytes D4-D12
of the line overhead. It is important to identify which of these is supported on
a specific vendors’ interface, as well as which of these is needed for the
networks management communications. Refer to the Data Communications
Network Planning Guide, NTR710AM, for a detailed description of the types
of DCC supported on the OPTera Connect DX network element.
Secure DCC Feature

The secure data communication channel (DCC) and Transmission Control
Protocol/Internet Protocol (TCP/IP) access control features allow for better
security control of user access to the DCC and TCP/IP networks.
The secure DCC feature prevents unauthorized access to and from the DCC
network by operations controllers (OPCs) and network elements connected to
the DCC network. The TCP/IP access control feature prevents unauthorized
access to the TCP/IP network from the operations controller (OPC). Both
features are optional and can be enabled/disabled from the OPC. No additional
hardware is required to support these features.
There are situations where equipment from two different customers are present
on the same TCP/IP or DCC network (for example, nodes belonging to a 3rd
party or mid-span stage meets). The secure DCC feature can be used to limit
access to the DCC network without disabling the DCC to block access. The
feature limits access to the DCC network to authorized network element
(NE)/OPC names and NE IDs.

5-1
Software feature description 5-

This chapter provides a description of the different software features on the
OPTera Connect DX network element.
Many of the software features come with the basic network element software
and some are optional. For details on the feature packaging for orders, refer to
Chapter 9, “Ordering information” in this document.
The following is a list of topics covered. For more detailed information, refer
to the section indicated within this chapter.
• Shelf configuration
• Traffic configuration
• Dense wavelength division multiplexing (DWDM)
• Multiwavelength optical repeater (MOR)
• Performance monitoring (PM)
• Facility protection switching
• Equipment protection switching
• Synchronization
• Data communications
• Ring extra traffic
• Tributary hairpinning
• Software management by release
• Parameter provisioning
• Parallel telemetry
• System security
• Alarms
• Logs
• DX_HUB network element
• Flexible default protection scheme
• Test access

5-2 Software feature description
• Loopback (facility and connections)

• Auto in-service
• SDH overhead Orderwire
• Low-speed cross-connection provisioning enhancements
• Preside
Shelf configuration
When you commission a OPTera Connect DX network element, you must
provision the default protection scheme of the STM-64 interfaces. You also
have the option to provision the default protection scheme of the tributary
interfaces (STM-1, STM-4 and STM-16). If you do not provision the default
protection scheme of the tributary interfaces, the tributary protection scheme
defaults to 1+1 unidirectional. The Gigabit interface is always unprotected.
When a circuit pack is inserted into a valid unprovisioned slot of the shelf, the
circuit pack groups automatically autoprovisions according to its default
protection scheme. You can change the protection scheme on a circuit pack
group (CPG) basis or CPG port basis for multi-port circuit packs. If the CPG
has a node map against it or has a connection provisioned, you must delete the
node map and all connections from the OPC. Then, you can delete the
protection scheme of the CPG. After you delete the CPG, the circuit packs of
the CPG are configured as unprotected.
The following circuit packs are optional:

• OPC (three components)
• parallel telemetry
• Quad STM-1o/e, HD STM-1o/e, half-height STM-4, Quad STM-4,
STM-16 , Dual STM-16, Quad STM-16, Dual GE and STM-64 circuit
packs
• multi wavelength optical repeater (MOR), MOR Plus, optical service
channel (OSC)
• Orderwire
• second (protection) message exchange (MX)
Note 1: The half-height STM-4, MOR, and MOR Plus circuit packs are
supported on the TN-64X network element only.
Note 2: The HD STM-1o/e, and Dual STM-16, Quad STM-16 circuit
packs are supported on the OPTera Connect DX network element only.
Note 3: The STM-64 circuit packs are optional on OPTera Connect DX
bays only.
Note 4: It is highly recommended, but not mandatory, that you install a
second MX circuit pack in the control shelf.

To query, set, or change equipment parameter values, refer to Part 1 of

Provisioning and Operations Procedure, 323-1531-310 for the OPTera
Connect DX platform.
Refer to Circuit Pack Descriptions, 323-1531-102, for a full description of the

circuit packs. Refer to Chapter 6, “Hardware feature description”, for a
description of the shelf configurations.
Traffic configuration
OPTera Connect DX Release 6.0 supports up the following add/drop
bandwidths:
• up to 64 protected VC-4s or 128 unprotected VC-4s with DX65 switch
modules
• up to 192 protected VC-4s or 384 unprotected VC-4s with DX100 and
DX140 switch modules and equipping the tributary circuit pack slots only.
• up to 320 protected VC-4s or 640 unprotected VC-4s with the DX100
switch modules and tributary circuit packs in the tributary circuit pack and
universal slots (G11, G12, G17 and G18).
• up to 448 protected VC-4s or 896 unprotected VC-4s with the DX140
switch modules and tributary circuit packs in the tributary circuit pack and
universal slots (G0, G9, G10, G11, G12, G17, G18 and G19).
OPTera Connect DX Release 6.0 supports concatenated VC-4-2c, VC-4-4c,
VC-4-8c, and VC-4-16c bidirectional connections. Concatenated payloads at
VC-4-64c rates are also supported on the 10 Gbit/s unprotected T/R interfaces,
1+1, 4-Fiber MS-SPRing, and 4-Fiber Chain, provided that the 10 Gbit/s
circuit packs are VC-4-64c capable.
The DX_HUB network element supports the following tributary circuit packs:
• Quad STM-1o/e circuit packs
• HD STM-1o/e circuit packs
• Quad STM-4 circuit packs
• STM-16 circuit packs
• Dual STM-16 circuit packs
• Dual Gigabit Ethernet circuit packs
The TN-64X ADM supports the following tributary circuit packs:
• Quad STM-1o/e circuit packs
• Half-height STM-4 circuit packs

• STM-16 circuit packs

• Dual Gigabit Ethernet circuit packs
Refer to Part 2 of Provisioning and Operations Procedures, 323-1531-310 for
traffic configuration procedures for the OPTera Connect DX platform.
The following sections describe software features which are associated with
the facility provisioning on tributaries and high-speed optics: section trace,
path trace, signal label, forward error correction (FEC), triple forward error
correction (TriFEC), and SS bit provisioning.
Section trace
Section trace monitors STM-4, STM-16, and STM-64 sections of traffic.
Section trace helps protect system integrity at installation against improperly
connected optical fibers. For a section trace, you enter the transmit value at the
head-end. If the receive value at the tail-end does not match the transmit value
previously entered at the head-end, a Section Trace Mismatch alarm becomes
active.
Path trace
Path trace checks the integrity of an end-to-end path. The network element
extracts path trace bytes from the SDH path overhead. You can then compare
the received path trace value with the provisioned expected path trace value.
The system reports both of these values on the network element user interface
(NE UI) and no alarm becomes active in case of path trace mismatch.
Signal label
The path overhead carries the signal label, which indicates the type of data
carried in a payload. The signal label is transmitted at the transmit end of a path
and extracted at the receive end, where it is checked against an expected signal
label value. You can query and provision the expected label value for the
receive signal through the NE UI.
Forward error correction

The forward error correct (FEC) feature detects and corrects small burst error
of 8 bits on an STM-16 basis. The FEC feature adds some redundancy parity
bits on the transmit side and removes the bits on the receive side. With FEC,
the guaranteed end-of-life BER is enhanced from 10 E-12 (without FEC) to
10E-15 with FEC. FEC is only available on STM-64 facilities and is enabled
by default. You can disable the FEC through the NE UI.
Triple forward error correction

The Triple forward error correction (TriFEC) feature uses undefined overhead
bytes to perform multiple parity error checks (BCH-3) and improves the
performance of OPTera Connect DX 10 Gbit/s receivers. TriFEC corrects a
burst error of 24 bits on an STM-16 basis, compared to a burst error of 8 bits

on an STM-16 basis, for single FEC. You can provision the FEC status (with
the NE UI) as None, FEC (default) and TriFEC. TriFEC is only available on
STM-64 facilities.
Tributary facility mode

The usage of the SS bits in the H1 and H2 AU pointer bytes differs between
SDH systems and SONET systems. To allow the OPTera Connect DX and
TN-64X network elements to interwork with SONET tributaries as well as
SDH tributaries, you can provision the facility mode on the tributaries to either
SDH mode or SONET mode. The SDH mode is enabled by default.
Note: The facility mode can be provisioned on a per port basis, as opposed
to tributary basis. A Quad/HD tributary circuit pack can support the
SONET facility mode on some ports and the SDH facility mode on the
other ports.
In the SDH mode:

• the SS bits are set to 10 on all outgoing tributary signals
• the SS bits in all incoming tributary signals are ignored
• pointer processing for pointer increment/decrement checks for 4 out of 5
valid I bits and 4 out of 5 valid D bits
In the SONET mode:
• the SS bits are set to 00 on all outgoing tributary signals
• the SS bits in all incoming tributary signals are ignored
• pointer processing for pointer increment/decrement checks for 8 out of 10
valid I and D bits
Note: On the STM-64 line signals, the SS bits are always set to the SDH
mode and cannot be changed.
Dense wavelength division multiplexing

On a 10 Gbit/s dense wavelength division multiplexing (DWDM) transmit
circuit pack, you can provision the following:
• optical power output (-10.0 dBm to +1.5 dBm)
• the transmit chirp (positive, negative or zero)
• the Tx NLS dithering (ON or OFF) and the Tx Analog Maintenance (AM1,
AM2)
Note: The current DWDM transmitter cannot support a zero value for the
Tx Chirp.

The system saves all parameters over software restart, reboot, upgrade, and
power up. For more information, refer to Part 1 of Provisioning and
Operations Procedures, 323-1531-310 for DWDM provisioning procedures
for the OPTera Connect DX platform.
Multiwavelength optical repeater

The MOR and MOR Plus circuit packs are supported in TN-64X Regen and
ADM bays, but are not supported on the OPTera Connect DX bay. You can
perform the following functions from the NE UI:
• provision the MOR facilities
• provision the optical signal facility
• provision the optical service channel (OSC) facility
• query the input and output power levels of OSCs
• optimize the MOR power:
— autodiscover channel inventory
— propagate channel inventory
— lock optical channel provisioning
— propagate output power recommendations and lock output power
The system saves all parameters over software restart, reboot, upgrade,
power up, and circuit pack replacement. For DWDM system applications from
2 to 32 wavelengths, refer to the Optical Networks Applications Library,
NTCA66BA.
Performance monitoring
Performance monitoring (PM) provides early detection of degradation and the
ability to detect section network degradations. The PM feature gathers
performance indicators from the various traffic-carrying circuit packs and
reports PM parameter counts from these indicators. The PM feature also
provides for the storage of performance statistics and PM threshold crossing
alerts.
The collection mode for PMs can be set to either SONET or SDH on a network
element and a facility basis. In the SONET mode, measurements are made on
a basis of bit errors, as per Telcordia GR-253. In the SDH mode, measurements
are made on a basis of block errors based on ITU-U standards G.828 and G.829.
The OPTera Connect DX software also supports untimed PM counts. Untimed

PM counts increment until the user resets the count or until the upper limit is
reached. Untimed PM counts allow for monitoring of a given optical fiber or
path link over a longer period of time. Users concerned with degradation of
signals are capable of evaluating facility or path performance over a given
length of time.

OPTera Connect DX Release 6.0 provides full support for Path PMs of
concatenated signals up to VC-4-64c rates. OPTera Connect DX Release 6.0
also supports Receive Signal Level (RSL) Threshold alarming to notify the
user that the Optical Power Receive (OPR) value has gone outside the desired
range.
Table 5-1 lists the PM parameters for the network element. For default
parameter values, refer to Part 1 of Provisioning and Operations Procedures,
323-1531-310 for the OPTera Connect DX platform.
You can access PM data from the NE UI and from the OPC user interface. For
performance monitoring procedures, refer to Performance Monitoring
Table 5-1
Performance monitoring parameters
Level Parameter: Telcordia GR 253 Parameter: ITU-T G.828 and G.829
Multiplex section MS coding violation (CV) MS errored blocks (EB)

(MS)
MS errored second (ES) MS ES
MS severely errored second MS SES

(SES)
MS unavailable second (UAS) MS background block errors (BBE)
MS failure count (FC) MS ratio of ES to the total seconds (ESR)
MS forward error correction (FEC) MS ratio of SES to the total seconds

(SESR)
MS ratio of BBE to total blocks not

including those during a SES (BBER)
MS unavailable time span (UAT)
MS when 3 or more consecutive SES is

detected (SEP)
MS severely errored period intensity

(SEPI)
MS UAS
MS FEC


Performance monitoring parameters
Level Parameter: Telcordia GR 253 Parameter: ITU-T G.828 and G.829
Regen section (RS) RS CV RS EB
RS ES RS ES
RS SES RS SES
RS severely errored frame second RS BBE

(SEFS)
RS out of frame second (OFS)
RS ESR
RS SESR
RS BBER
Path path CV path EB
path ES path ES
path SES path SES
path FC path BBE
path UAS path ESR
path SESR
path BBER
path UAT
path SEP
path SEPI
path UAS
Physical performance indication of quality (IQ) IQ

optical power received (OPR) OPR
Protection protection switch duration (PSD) PSD

performance protection switch count (PSC) PSC
Note: Physical PMs are only supported on the 10 Gbit/s line interfaces.

Receive signal level threshold alarming

Optical power received (OPR) is a measure of the optical signal (dBm)
received at a receiver circuit pack. The OPR measured includes all internal and
faceplate connectors losses. The user can query the OPR levels, calculated
every second, using the network element user interface (NE UI).
During the setting up of the power levels in an optical network, power levels
received at the receiver circuit packs can fluctuate in the network. OPTera
Connect DX Release 4.0 provides user notification when an OPR goes outside
the predefined range. This feature allows the user to quickly identify the
problem facility without having to query the OPR for all the facilities from the
NE UI.
When the OPR level falls outside the threshold trigger range, the system raises
a ‘PM OPR out of range’ alarm. The alarm clears when the OPR level is within
the threshold trigger by a preset hysteresis value. The hysteresis prevents the
alarm toggling if the OPR level fluctuates around the threshold levels as shown
in Figure 5-1 on page 5-9. The threshold and hysteresis levels are set
depending on the circuit pack type and cannot be changed. The receive signal
level threshold alarms meet the requirements of Telcordia standards GR-253
(Issue 2 Dec 1995 Section 6.22) and GR-820 CORE (Issue 1 Nov 1994
Sections 2.6.7 and 3.3).
Figure 5-1
Receive signal level alarm hysteresis
DX3916t
High
Hysterisis zone
threshold
OPR level (dBm)
Low Hysterisis zone

threshold
Time

Table 5-2 shows the threshold and hysteresis values for the supported circuit
packs.
Table 5-2
Receive signal level threshold alarm threshold and hysteresis values
Circuit Pack Type Threshold Range Hysteresis Range Normal Operating
(dBm) (dBm) Range (dBm)
DX 10G STM-64 T/R −4.0, −12.5 −6.0, −11.5 −6.0, −11.5
DX 10G STM-64 long reach APD −6.0, −25.0 −7.0, −24.0 −7.0, −24.0
T/R
TN-64X 10G STM-64 Rx −4.0, −12.5 −6.0, −11.5 −6.0, −11.5
TN-64X 10G STM-64 single −4.0, −12.5 −6.0, −11.5 −6.0, −11.5
regenerator (XR)
Supported circuit packs

The 10 Gbit/s STM-64 circuit packs that support OPR physical performance
monitoring (PM) support the receive signal level threshold alarm feature. The
supported circuit packs are:
• STM-64 10G T/R circuit packs in the OPTera Connect DX bay
• STM-64 10G long reach APD T/R circuit packs in the OPTera Connect DX
bay
• STM-64 10G short reach receiver circuit packs in the OPTera Connect DX
bay
Note: Tributaries do not support receive signal level threshold alarms.

Facility protection switching

Facility protection switching protects traffic against various fault scenarios.
An automatic switch occurs at the following signs of trouble:
• equipment failure (circuit packs carrying traffic)
• release of the bottom latch on a traffic-carrying circuit pack
• loss of signal, loss of frame, or an alarm indication signal
• signal degradation below a user defined threshold
The time an automatic protection switch takes is less than 60 ms (including
10 ms detection time). For a user-initiated protection switch, the total time is
less than 50 ms. Some exceptions apply for the following:
• large transcontinental or transoceanic rings with a circumference greater
than 1200 kilometers. With the head-end ring switching (HERS) protocol,
switch times typically less than 300 ms are achievable (no matter if the ring
is carrying extra traffic).
• rings with more than 16 nodes
• rings carrying extra traffic connections. In this case, the protection switch
completes in less than 110 ms.
SNCP (path) protection switching
OPTera Connect DX Release 6.0 supports path protection switching for
subtending SNCP (STM-4/STM-16) Rings.
STM-16 2-Fiber MS-SPRing

OPTera Connect DX Release supports subtending STM-16 2-Fiber
MS-SPRing. The protection switch types and priorities are similar to that of
the STM-64 2-Fiber Ring.
Single 4-Fiber MS-SPRing protection switching

Protection switch types and priorities
You can command a lockout, a forced switch, or a manual switch from the
NE UI. The priority of switch types from highest to lowest is as follows:
• lockout of protection or signal failure on protection or lockout of working
(span/ring)
• forced switch
— forced span switch
— forced ring switch

• automatic switch
— signal failure on working
— signal degradation on protection
— signal degradation on working
• manual switch
— manual span switch
— manual ring switch
A higher priority requests have precedence over active lower priority requests
and
• a lower priority user request is cleared implicitly and does not go pending
• a lower priority automatic switch goes pending
For more information, refer to Part 1 of Protection Switching Description and
Single 2-Fiber MS-SPRing protection switching

Protection switch types and priorities
You can perform a lockout, a forced switch, or a manual switch from the
NE UI. The priority of switch types from highest to lowest is as follows:
• lockout of protection span or lockout of working
• forced ring switch
— signal failure on working
— signal degradation on working
• manual ring switch
For more information, refer to Part 1 of rotection Switching Description and
Protection oscillation control

Protection oscillation control is enabled by default in revertive tributary
protection configurations. Protection oscillation control prevents switching to
and from the protection channel caused by intermittent faults on the working
channel.
For more information, refer to Part 1 of Protection Switching Description and

Procedures, 323-1531-311 for the OPTera Connect DX platform,

Head-end ring switching

Head-end ring switching (HERS) is used on very large ring systems with ring
circumferences beyond 1200 km. When there is a node failure or complete
span failure, the traffic is rerouted by way of the shortest direct path. You can
use the OPC user interface (OPCUI) to provision the protection protocol
(either MS-SPRing or HERS) for each ring.
Note: HERS is supported on STM-64 MS-SPRing rings.
Ring extra traffic

Ring extra traffic allows you to provision connections on the protection
STM-64 bandwidth. That is, connections can be provisioned from any
working/protection tributary to any working/protection 10G bandwidth. When
the system carry extra traffic, the total protection switch will complete in less
than 110 ms.
MS-switched matched nodes

MS-switched matched nodes are available for 4-Fiber and 2-Fiber Rings. As
the number of rings in a network increases, the originating and terminating
nodes (network elements) for a traffic path are not always in the same ring.
Rings require interconnection, and each connection must have protection. In
matched nodes configurations, two nodes (primary gateway and secondary
gateway) protect the inter-ring traffic.
The protection scheme is 1*1 for the primary gateway, and 1+1or unprotected
1+0 for the secondary gateway. The 1*1 protection scheme is similar to 1+1,
unidirectional revertive line protection and requires physical optical fiber
loopback at the protection circuit pack. The service selector module on the
primary path detects failures and selects the proper primary or secondary feed
for the traffic. If there is a P-AIS failure, the switch holds off for a hold-off time
of 100 ms to allow any ring or span switches to clear. The default hold-off time
is 100 ms, and the hold-off time is provisionable from 100 ms to 250 ms. The
hold-off feature prevents unnecessary matched node switches.
For more information about matched node protection switching, refer to Part
1 of Protection Switching Description and Procedures, 323-1531-311 for the
OPTera Connect DX platform.
Equipment protection switching

Equipment protection switching (1+1 revertive) protects against circuit pack
failures for the following circuit packs:
• switch modules
• external synchronization interface (ESI)
• message exchange (MX)

Both user-initiated and automatic protection switching are available on the

ESI, switch module, and MX equipment. When a backup OPC is present, a 1:1
protection in revertive mode is available for the OPCs.
For a description of equipment protection switching, refer to Part 1 of

Protection Switching Description and Procedures, 323-1531-311 for the
OPTera Connect DX platform. For protection provisioning procedures, refer to
Part 1 of Provisioning and Operations Procedures, 323-1531-310 for the
OPTera Connect DX platform.
Equipment protection switch types and priorities

You can issue a lockout, a forced switch, or a manual switch command from
the NE UI. The priority of these equipment switch types from highest to lowest
is as follows:
• lockout
• forced switch
• manual switch
You can provision protection switching priorities. For more information, refer
to Part 1 of Protection Switching Description and Procedures, 323-1531-311,
for the OPTera Connect DX platform.
Synchronization
The external synchronization interface (ESI) receives timing input from an
external building-integrated timing supply (BITS) source or high-speed optics.
The ESI provides the best timing source to timing distribution, the high-speed
optics and tributaries. Synchronization status messaging (SSM) ensures that
the best timing source is selected by using quality codes and priority codes.
Bits 5 to 8 of the S1 byte are read to determine which source (BITS or line
optics) will become the active timing source. The ESI can provide timing
distribution to other equipment in the SDH network.
The ESI supports external timing and line timing modes with stratum
3 (+ 4.6 ppm) holdover capabilities.
All network elements must have ESI circuit packs. Regenerators are
through-timed and do not require ESI circuit packs. At least one ADM in a ring
requires a BITS timing source. The other ADMs can be BITS-timed or line
timed.
Three variants of the ESI circuit pack are available. The first unit
(NTCE44BA) provides external inputs and outputs at the E-1 line rate
(2.048 MHz) (SDH). The second unit (NTCA44AA) provides external inputs
and outputs at the DS1 line rate (1.5 Mbit/s) (SONET). The third unit

(NTCE44AA) can be provisioned to provide external inputs and outputs at the

2.048 MHz or 2.048 Mbit/s line rates (SDH). The default setting is
2.048 Mbit/s. A conversion box can be mounted at the top of the TN-64X
ADM network element that converts the DS1 external ESI signals into
2.048 MHz signals for use in an ETSI environment.
Refer to the section on network synchronization in Chapter 8, “Technical

specifications”, for a full description of synchronization in a system. For
synchronization provisioning procedures, refer to Part 1 of Provisioning and
Operations Procedures, 323-1531-310 for the OPTera Connect DX platform.
Timing generation
The timing generation references for a network element is N:1 protected
(where N is less than or equal to 6). The best timing reference can be
automatically or manually selected from a pool of six sources.
For an OPTera Connect DX network element, the six timing generation

references sources are taken from the following pool of references:
• BITSA
• BITSB
• any four of:
— STM-64 G0
— STM-64 G9
— STM-64 G10
— STM-64 G11
— STM-64 G12
— STM-64 G17
— STM-64 G18
— STM-64 G19
For an TN-64X network element, the six sources are:
• BITSA
• BITSB
• STM-64 G1
• STM-64 G2
• STM-64 G3
• STM-64 G4
BITSA and BITSB provide external timing. The STM-64 references provide
line timing functionality.

Timing distribution
Timing distribution synchronizes a large number of systems within a single
location to a single timing reference signal. The ESI circuit packs provide
timing distribution. Each ESI circuit pack uses the recovered optical signal to
derive a timing distribution reference output.
Each ESI circuit pack provides two timing reference outputs (2 Mbit/s, 2 MHz
or 1.5 Mbit/s, depending on the ESI circuit pack used). The timing distribution
outputs from ESI G1 is G1OUT. The timing distribution outputs from ESI G2
is G2OUT. G1OUT and G2OUT are redundant but do not protect each other.
For the 1.5 Mbit/s ESI, the timing distribution output is a framed all-1s DS1
with superframe format (SF) or extended superframe format (ESF). The
default frame format is ESF. The timing distribution output can have short
(default), medium, or long line build-out (LBO). The ESI then uses the DS1
signal to synchronize the local BITS. The local BITS in turn synchronizes all
the other network elements at that location.
Note: For the 1.5 Mbit/s ESI, each TD output is buffered to provide four
connections on the SATT (i.e. four G1OUT signals and four G2OUT
signals). For the 2 MHz ESI, each TD output is buffered to provide a single
connection on the SATT (i.e. one G1OUT signal and one G2OUT signal).
Data communications
A data communications channel (DCC) provides the ability to interconnect
between network elements and subtending systems in a network. Information
travels in the SDH overhead or by Ethernet. The network element supports
routing of data over the Open Systems Interconnection (OSI) 7 layer stack.
Both the OPTera Connect DX and TN-64X bays support Level 2 routing. This
feature allows network elements in separate Level 1 areas to communicate
with one another. As a result, the number of nodes within the entire routing
domain can increases beyond 150 network elements.
The secure DCC feature allows customers to limit access to the DCC network
to authorized NE/OPC names and NE IDs, without the need to disable DCC.
Refer to Chapter 4, “Network configuration architecture” for interface port

descriptions. For port configuration procedures, refer to External Interface
Configuration Procedures, 323-1531-302.
Head-end datacomm gateway

The introduction of the SNCP Ring feature in OPTera Connect DX Release 4.0
creates a stronger demand to use the OPTera Connect DX bay as a head-end
datacomm gateway. In this section, usage of the OPTera Connect DX bay as a
head-end datacomm gateway refers to the case where the bay is acting as an
interface between the customer TCP/IP network and the OSI DCC network.

This increased demand for head-ending on the OPTera Connect DX bay adds
to the processing requirements of various components of the OPTera Connect
DX bay. These include the Shelf Controller (SC), the Message Exchange
(MX), the Maintenance Interface (MI), and the port cards that are connected
to the subtending equipment.
For the engineering rules and planning guidelines for the case where the
OPTera Connect DX bay is used for OAM head-ending of subtending metro
networks elements, refer to the Optical Networks Data Communications
Planning Guide, NTR710AM.
Ring extra traffic

Ring extra traffic allows you to provision STM connections on the 10 Gbit/s
protection bandwidth for single 2-Fiber Rings (OPTera Connect DX bay only),
single 4-Fiber Rings, and single 4-Fiber ADM chain configurations. Ring
extra traffic is also supported on 2x4-Fiber Rings, 2x4-Fiber ADM chains and
Nx2-Fiber Rings, and can originate from either protected or unprotected
tributaries.
Ring extra traffic connections have lower priority than those connections
provisioned on the working bandwidth. In addition time slot interchange (TSI)
across the Nx2-Fiber Rings, 2x4-Fiber Rings and 2x4-Fiber ADM chains is
not supported for extra traffic (you must use the same high-speed protection
channels when extra traffic crosses multiple rings via DX HUBs).
Note: Restorable ring extra traffic for HERS-based 2-Fiber and 4-Fiber
rings is not supported in OPTera Connect DX Release 6.0.
Tributary hairpinning
You can provision individual VC-4 connections or concatenated hairpinned
connections. Hairpinning connections are provisioned as nodal connections,
found on the OPC UI Connection Manager, TL1, Trail Management
connections, or as Optical Connection Manager connections.
For more information on tributary hairpinning, refer to “Tributary hairpinning

application” in Chapter 4, “Network configuration architecture”.
Software management by release

The management-by-release feature:
• automatically defines a set of software loads (called the software lineup)
for all downloadable circuit packs in a span of control
• controls the software configuration among these loads
• eliminates the need to keep track of software load names and compatibility
between software loads

Note: The different software loads in the software lineup are compatible
with the circuit packs and with each other.
Parameter provisioning
You can customize the network element and the related OPC pair after the
system lineup and testing (SLAT) commissioning procedures. To perform
SLAT procedures, key parameters must have default settings for testing
purposes. You can provision the following parameters through the NE UI:
• alarm inhibition
• common language facility identifier
• Orderwire
• FEC and TriFEC
• Ethernet control
• parallel telemetry
• payload
• performance monitoring thresholds
• facility protection
• network element protection mode (protected or unprotected)
• section trace
• expected receive VC-4 path trace
• expected receive VC-4 signal label
• signal degrade threshold
• synchronization
• user identifiers (user IDs) and passwords
• wait-to-restore (WTR) period
• link service data unit size
• DCC provisioning
• level 2 routing
• facility mode provisioning (SONET or SDH)
For default parameter values and the procedures for parameter provisioning,
refer to Part 1 ofProvisioning and Operations Procedures, 323-1531-310 for
the OPTera Connect DX platform.

Parallel telemetry
Two parallel telemetry circuit packs in the control shelf support the parallel
telemetry feature. Each parallel telemetry circuit pack provides 32 external
customer inputs, which are active low only, and 8 form-C relay outputs for
system alarms, status, and external equipment controls.
Refer to Chapter 4, “Network configuration architecture” for more

information on parallel telemetry.
System security
You can control the security features on the network element through the
NE UI, the Centralized User Administration on the OPC user interface, and the
Preside network management software. You can perform the following
functions:
• create, edit, or delete user groups and toolsets
• query and audit user profiles
• query and force out current users
• perform routine system security maintenance
• enable or disable SecurID authentication as local or Remote
Authentication Dial-In User Service-local (RADIUS-local)
Note: For SecurID authentication, enter the commissioning parameters in
the OPC servers file.
The secure DCC and TCP/IP access control allows you to perform the
following functions:
• enable and disable the secure DCC and the secure TCP/IP features
• modify the allow and deny access control lists by invoking the
config_dcc_ac and the config_ac commands from the OPC UNIX shell
command line
• clear the Datacomm Access Violation alarm from the OPC alarm
provisioning tool
• clear the TCP/IP Access Violation alarm from the OPC alarm provisioning
tool
Refer to Security Management Procedures, 323-1531-305, for procedures on
system security management.

Alarms
The OPTera Connect DX and the TN-64X systems report equipment, facility,
and environmental alarms. The remote monitoring of alarms is possible with
the following surveillance interfaces:
• the NE UI through a modem or Telnet session
• the OPC user interface through a modem or Telnet session
• Preside network management software for network management
The consolidated OPC banner line tool (COBLT) enables you to monitor up to
16 OPC Span of controls and their banner line changes, all inside a single
display window. Within the Remote viewing area, a user can highlight a
selected monitored OPC banner line and display a drop down menu to:
• remote login to the monitored OPC
• suspend / resume monitoring of the remote OPC without removing it from
the viewing list
• manually switch monitoring from Primary OPC to Backup (Peer) OPC
• delete the monitored OPC from the viewing list
• display detailed information about the selected OPC (OPC name, OPC IP
address, OPC Type, Initial Start, Total Counts changes, Peer OPC name
and Peer OPC IP address)
• save OPC IP address to the user’s save file (can be loaded later)
The following are local alarm indicators:
• the network view banner line in the Alarm Monitor and Network Summary
tools on the OPC user interface
• the consolidated OPC Banner Line tool, accessed either from the Network
Surv toolset or the Surveillance (View) toolset of the OPCUI
• the circuit pack light-emitting diodes (LEDs)
• the bay LEDs
• the central office alarm contacts (visible and audible alarms)
• the parallel telemetry
• the alarms and logs from the NE UI
• the alarms and logs from the OPC user interface
• the alarms and logs from the Preside network management software
An alarm cutoff (ACO) push button is available on the local craft access panel
(LCAP) to silence audible alarms. A LED test button allows you to check the
shelf LEDs. The NE UI has a test for the ACO and LED functions. You can

use ACO remotely through the synchronization, alarms, and telemetry

terminations (SATT) interfaces. You can terminate audible alarms through the
co command on the NE UI.
The alarm history contains the last 50 alarms. The alarm history is available
from the NE UI or the OPC user interface (which you can access from the
Preside network management software).
For a description of OPTera Connect DX alarms, refer to Part 2 of Trouble

Clearing and Module Replacement, 323-1531-543 for OPTera Connect DX
equipment and environmental alarms and to Part 3 of Trouble Clearing and
Module Replacement, 323-1531-543 for OPTera Connect DX facility alarms.
Logs
Significant events on the network element generate a log report. Examples of
these events are user logins and logouts, command failures, system initiated
actions, or service-affecting changes performed by a user, the OPC, or the
network element software. The logs are in a circular buffer, which has a
capacity of 2000 logs. New logs replace older logs when the buffer is full.
For more information on logs, refer to Log Reference, 323-1531-840.
DX_HUB network element

The DX_HUB network element type is supported on the OPTera Connect DX
platform only, replacing the OPTera connect DX network element types (4FR,
2FR and unprotected hub) introduced prior to OPTera Connect DX Release
5.0. The DX_HUB network element type applies to new commissioned
OPTera Connect DX Release 6.0 network elements. In addition, after an
upgrade of previous OPTera Connect DX Releases to OPTera Connect DX
Release 5.0 and above, the OPTera Connect DX network element types (4FR,
2FR and unprotected hub) are automatically upgraded to DX_HUB network
element type. When the Classic TN-64X network element is upgraded to
OPTera Connect DX Release 5.0 and above, the network element type stays
the same.
Flexible default protection scheme

OPTera Connect DX Release 5.0 introduced the default protection scheme
(DPS) feature. The DPS feature allows you to provision the default protection
scheme for tributary and line interfaces (except for Gigabit Ethernet interfaces
which is always unprotected). You can set the DPS for the tributary and line
interfaces during the commissioning of the network element and you can
change the DPS of the interfaces later.

During commissioning, you must set the DPS for the 10 Gbit/s interfaces to
one of the following:
• 4FR
• 2FR
• 1+1 bi
• 1+1 uni
• unprotected
During commissioning, the setting of the DPS for the tributary interfaces is
optional. If you do not provision the DPS for any tributary interface, the DPS
of the interfaces automatically defaults to 1+1 unidirectional. You can set the
DPS of the tributary interfaces as follows:
• STM-1 interfaces can be set to 1+1 bi, 1+1 uni, or unprotected.
• STM-4 interfaces can be set to 1+1 bi, 1+1 uni, or unprotected.
• STM-16 interfaces can be set to 2FR, 1+1 bi, 1+1 uni, or unprotected.
Note: Gigabit Ethernet interfaces always defaults to unprotected.
When a circuit pack is inserted into a slot that was not provisioned, the
protection scheme of the interfaces autoprovisions to the DPS setting for that
type of interface. For example, if the DPS of the STM-64 interfaces is set to
2FR, and a STM-64 circuit pack was inserted into slot G0 or G10, the DPS of
G0/G10 autoprovisions to support the 2-Fiber Ring.
During an upgrade to OPTera Connect DX Release 6.0, the existing protection

scheme of the network element are maintained. For example, if the protection
scheme of a network element is a 2FR before the upgrade, the DPS of the
network element maintains the 2FR protection scheme after the upgrade.
Test access
The test access feature monitors and tests signal quality of cross-connects
through a test access port (TAP). This feature provides quick and reliable
confirmation of service performance, as well as isolation of trouble when
failure occurs in the network.
OPTera Connect DX Release 5.0 introduced the support for test access on
OPTera Connect DX Release 5 network elements. The test access feature
allows you to route any cross-connected signal to a single dedicated test access
port (TAP) for local monitoring and testing. The TAP can be provisioned on a
port of any tributary interface.

Two types of test access functions are supported:

• monitoring test access (non-intrusive in-service testing)
• split test access (for an out-of-service connection)
The test access feature provides a quick and reliable way to check traffic
performance, as well as isolate trouble when failure occurs in the network.
Figure 5-2 on page 5-23 illustrates the organization of the main components of
the test access feature. The testing operations systems (TOS) sends testing
requests in the form of TL1 commands to the test access equipment through an
internal data network. The test access equipment is in the supported mode of
test controller system (TCS). In the TCS mode, the test access equipment
manages the test access session and sends TL1 commands to the network
element. Communication between the test access equipment and network
element occurs through a TCP/IP control link.
Figure 5-2
Test access components
DX5468p
Testing Operations
System (TOS)
DCN
Test access equipment

- test head
Control Link Test Access Interface cable

- TCP/IP socket (STM1, STM4, STM16 or GBE)
Network Element
(OPTera Connect DX)
Monitoring test access

Monitoring test access is a non-intrusive in-service testing of path connections
(see Figure 5-3 on page 5-24). The path connections are tapped and routed (via
the test access port) to monitoring test equipment. The monitored connections
are unaffected by the TAP, and therefore the monitoring is non-intrusive.

You can designate any active unprotected tributary interface which does not
have any connections as the TAP. However, there can be only one TAP per
network element, but you can establish multiple monitoring test access
connections up to the maximum bandwidth of the TAP. In addition, you can
establish test access monitor connections to a protected connection allowing
you to monitor the working and protection channels.
Note: The deletion and provisioning of monitoring test access

connections do not affect traffic or protection switching on the connection
that is monitored.
Figure 5-3
Example of a monitored test access configuration
DX4568t
Input Output
Input Output
Input Output
TAP In
TAP Out Test

unit
Legend
TAP = Test access port
Split test access

Split test access is an intrusive, service-affecting operation (see Figure 5-4 on
page 5-25). The cross-connection is split and the incoming signal is connected
(via the TAP output) to the receiver of a monitoring test equipment. The
outgoing signal is fed from the transmitter of the monitoring test equipment.
You can designate any active unprotected tributary interface which does not
have any connections as the TAP. However, there can be only one TAP per
network element. In addition, you can establish only one test access split
connection on the inputs (in either direction) of a protected connection.
Deleting the split test access connection automatically restores original
connection.

Figure 5-4
Example of splitA/B test access configuration
DX4544t
Input Output
Input Output
TAP In
Test
unit
TAP Out
Legend
TAP - Test access port

The network element user interface was modified to support the test access
feature. The support includes the provisioning, deprovisioning and retrieval of
monitor and split test access connections. The changes to the network element
user interface include a new submenu for test access under the payload menu.
The new sub menu allows you to query, set and clear test access port, as well
as to set and delete test access connections.
Test access engineering rules and restrictions

The following engineering rules and restrictions apply to the test access
feature:
• Test access is provisioned on a unidirectional basis.
• The SDH signal routed to TAP is down to VC-4 granularity and can
include concatenated paths or whole line up to the 2.5 Gbit/s rate.
• A TAP can simultaneously accommodate connections from more than one
interface (until the TAP capacity is reached).
• A tributary interface can be selected as TAP, provided that:
— it is in-service and does not carry connections
— the interface is provisioned as unprotected
• The TAP supports performance monitoring and alarm monitoring.

• A ‘Fac Test Access Connection’ active alarm (w,nsa) is raised only if there
is a test access connection provisioned against the facility. The facility
secondary state is set to TEST when you provision the TAP.
• The test access supports all types of connections (MS-SPRing, SNCP,
protected, unprotected and hairpin).
• The test access feature is not supported on the TN-64X platform.
• Only one tributary interface per network element can be designated as
TAP.
• Protection switching is not available on connections provisioned as split
test access.
• Only test access connections (split and monitoring) can use the test access
port.
• You cannot apply a test access connection to a loopback connection.
• You cannot use a STM-64 T/R interface as a TAP.
• A connection must exist in order to be monitored or split at the test access
port.
• Test access connections on the protection channel of a 2-Fiber or 4-Fiber
MS-SPRing are not supported.
• Test access connections on the protection channel of a 10 Gbit/s Linear
1+1 system are supported.
• A SDH connection can only be dropped to a TAP provisioned to the same
standard (SDH).
• You cannot change the protection scheme of a facility which has a test
access connection.
• OPC and Preside do not provide direct interfaces for the provisioning,
deprovisioning, and retrieval of test access connections.
Loopback (facility and connections)

OPTera Connect DX Release 5.0 introduced the support for loopback test
mode on the OPTera Connect DX platform only. The loopback test modes are
supported on all interfaces of the network elements. The feature allows you to
loopback connections at the VC-4 granularity and any valid concatenation
rates.
The two types of loopback functions which are supported include:

• facility loopback on all optical interfaces except older version of STM-16
T/R circuit packs (NTCA30AL version 1 and NTCA30CK version 1 to 4)
• connection loopback at a connection (path) level
The loopback feature provides a quick and reliable way to sectionalize
connections during testing and troubleshooting.

Facility loopback
Facility loopback is supported on all SDH optical interfaces except GE
interfaces. The facility loopback can be applied against an out-of-service
(OOS) facility only. Figure 5-5 on page 5-27 shows a STM-64 facility
loopback. Although no connection provisioning is required, the facility
loopback command induces P-AIS on normal onward connections. A warning
alarm is raised against all facilities in facility loopback test mode (the
secondary facility state displays LPBK).
Figure 5-5
Example of facility loopback
DX4813t
Rx
Rx
Tx
Tx
Port or line Switcher Port or line
circuit pack module circuit pack
Connection loopback
Connection loopback is supported on all tributary interfaces (including GE
interface) and STM-64 interfaces (see Figure 5-6 on page 5-28). Unlike
facility loopback, the connection loopback can be applied against an in-service
facility only. The connection loopback command induces P-AIS on the normal
forward connection. Before you can perform a connection loopback test, you
need to provision a connection at any supported connection rate. A warning
message is displayed when connection loopback is operated against an
in-service facility.
Connection loopback is implemented on a channel basis (working or

protection). This means that a connection loopback on the working channel of
a linear 1+1 interface will only loopback working channel traffic. In the event
of a switch to protection with a working channel connection loopback in effect,
the traffic takes the path based on the status of the protection channel. If the
protection channel is not in a connection loopback mode, the traffic pass
through the protection channel. The connection loopback behavior of the
protection channel is as that of the working channel.

Figure 5-6
Example of connection loopback
DX4570t
Rx Rx
Tx Tx

Network Element user interface

The network element was modified to support loopback provisioning which
includes query, operate and release operations.

The following engineering rules and restrictions apply to the loopback
functionality:
• Loopback test modes are not available on TN-64X platforms.
• Loopback connection on the protection channel of a 2-Fiber or 4-Fiber
MS-SPRing is not supported.
• Loopback connection on the protection channel of a 10 Gbit/s Linear 1+1
system is supported.
• Connection loopback is implemented on a per channel basis (working or
protection). For example, if a connection loopback is activated against the
working channel of a linear 1+1 notifies, the loopback is not active on the
protection channel.
• Facility loopback is not supported on Gigabit Ethernet interfaces.
• When performing a facility loopback connection test using a test set, the
test set must be synchronized to the same timing source as the OPTera
Connect DX network element. You can use the external timing source from
the OPTera Connect DX network element or use the same timing source as
the OPTera Connect DX network element to synchronize the test set. If the
test set is not synchronized with the same timing reference as the OPTera
Connect DX network element, loss-of-frame (LOS) and out-of-frame
(OOF) errors will appear on the test set.
• Loopback is not supported on electrical interfaces.
• Facility loopback is not supported on the older version of the STM-16 T/R
circuit packs (NTCA30AL version 1 and NTCA30CK version 1 to 4). For
these circuit packs, validation of loopback request fails resulting in
“Command Failed” message when the command is issued against these
circuit packs.
• Terminal loopbacks are not supported (see Figure 5-7 on page 5-29).

Figure 5-7
Example of terminal loopback
DX4569t
Tx
Rx
Tx
Rx
Auto in-service
OPTera Connect DX Release 5.0 introduced the Auto in-service (AINS)
feature to give you the capability to mask specific traffic related alarms from
being displayed at the network element user interface and any OAM-P layer.
The AINS feature is supported on OPTera Connect DX and TN-64X Legacy
platforms except for TN-64X Regenerators. The AINS functionality is
supported on all interfaces (STM-64, STM-16, STM-64, STM-1 and Gigabit
Ethernet).
Operating companies sell port services (for example, STM-1) which are not
used by the customer immediately. In this scenario, the operating company has
several traffic related alarms appearing at their user interface for these ports.
The alarms are not significant because the ports are not in use. The AINS
feature allows the operating companies to mask the alarms indefinitely or for
a specific period of time (known as the alarm inhibit period).
If the customer sends a valid signal through a port with the alarms masked, a
timer is started for a period of time known as the start-up period. The AINS
remains masked enabled during the start-up period. When the start-up period
expires and the signal is still valid, all the alarms are unmasked and the AINS
functionality is disabled for that port. The activation of the start-up period
occurs when all of the following conditions are met:
• the AINS feature is enabled for the port

• the port primary port state is in-service
• the secondary port state is NIL or TEST
• the port has a valid signal
• the circuit pack which is home to the port is physically present
The operating company has the ability to set the alarm inhibit functionality of
the AINS feature to “Configured” or “Not Configured”. When the alarm
inhibit period is configured, AINS will continue to mask the alarms until the
alarm inhibit period expires or if AINS is disabled via the user interface.

Note 1: The AINS feature is disabled by default. The AINS status and
alarm inhibit period status are preserved during future upgrades. However,
in-progress start-up period and alarm inhibit period recovery timing are not
maintained during upgrades.
Note 2: The default for the alarm inhibit period is not configured. An
active alarm inhibit period timer does not start until the circuit pack is
present and physically exists.
There are two status parameters, the auto in service status (AINS) and the
alarm inhibit status (ALIS). If the AINS is enabled, AINS is turned on and the
specific alarms are masked. If the ALIS is not configured and the AINS status
is enabled, the alarms are masked until a valid signal is received for the
required start-up period or if the user disables the AINS feature. If the ALIS is
configured and the AINS status is enabled, the alarms are masked only for the
alarm inhibit period, until a valid signal is received for the required start-up
period or if the user disables the AINS feature.
For normal operations, customers mask the alarms indefinitely. To mask the
alarm indefinitely, you must set the AINS to “Enabled” and ALIS to “Not
Configured”. Under this condition, the AINS feature continues to mask the
alarms indefinitely until you disabled the AINS feature (by setting AINS to
“Disabled” via the user interface) or until a good signal is received for the
amount of time specified in the start-up period (SUP). When a good signal is
received, the start-up period timer starts running. When the start-up period
timer expires, the AINS is set to “Disabled” and all the alarms are unmasked.
As an option during testing, the customer may like to mask alarms for a fixed
period of time. To mask the alarm for a fixed period, you must set the AINS to
“Enabled” and ALIS to “Configured”. Under this condition, the alarm inhibit
period (AIP) timer begins to count down from the amount of time specified in
the AIP (AIP default value is 31 days). If a good signal is not received for the
time specified in the AIP, the AIP timer times out, the AINS is set to
“Disabled” and all the alarms are unmasked. If a good signal is received within
the time specified in the AIP, the start-up period timer starts running. When the
start-up period timer expires, the AINS is set to “Disabled” and all the alarms
are unmasked. If the AIP timer expires before the start-up timer expires, the
alarms remain masked until the start-up timer expires. The start-up period
timer takes precedence over the AIP timer expiration.
From the network element user interface, you can view the status of all ports
that have AINS enabled. From the network element main menu, select the
equipment menu, then the network element menu, followed by the auto in
service menu and finally the query AINS parameters menu. Figure 5-8
displays an example of the screen that is displayed with the query AINS
parameter request. The asterisk “*” under AINS Status column indicates that
the facility port is “Enabled”. The asterisk “*” under Alarm Inhibit Status
column indicates that the ALIS is “Configured”.

Figure 5-8
Query AINS parameters dialog box
DX5126p_sdh
NE 884> QueRy AINS Parameters
Alarm Start-Up Alarm Alarm

AINS Inhibit Period Start-Up Inhibit Inhibit
Unit Status Status (DD/HH/MM) Time Left Period Time Left
STM64 G1 * * 00/04/00 00/00/00 31/00/00 00/00/00
STM64 G2 . . 00/04/00 00/00/00 31/00/00 00/00/00
STM64 G3 . . 00/04/00 00/00/00 31/00/00 00/00/00
STM64 G4 . . 00/04/00 00/00/00 31/00/00 00/00/00
STM16 G1 . . 00/04/00 00/00/00 31/00/00 00/00/00
STM16 G2 . . 00/04/00 00/00/00 31/00/00 00/00/00
STM4 G5 * . 00/04/00 00/00/00 31/00/00 00/00/00

STM4 G6 . . 00/04/00 00/00/00 31/00/00 00/00/00
Figure 5-9 on page 5-31 shows the scenario where the AINS status is enabled,
the ALIS status is configured and no valid signal is received for the duration
of the alarm inhibit period. The alarm inhibit period expires and the AINS is
disabled, allowing all traffic related alarms for this unused facility to be
displayed at the user interface.
Figure 5-9
Alarm inhibit period expires - No start-up period
DX4883p
AIP
AIP started AIP expires

AINS disabled
Legend
AINS = Auto in-service
AIP = Alarm inhibit period

the ALIS status is configured, a valid signal is received, the start-up period
begins and the start-up period expires before the alarm inhibit period expires.
When the start-up period expires, the alarm inhibit period is cancelled and the
AINS functionality is disabled.
Figure 5-10
Start-up period expires before the alarm inhibit period expires
DX4884p
AIP
SUP
AIP started SUP started SUP expires

AIP cancelled
AINS disabled
Legend
SUP = Start-up period
the ALIS status is configured, a valid signal is received, the start-up period
begins and the signal goes bad before the start-up time expires. At that time,
the start-up period is cancelled and the alarm inhibit period is restarted.

Figure 5-11
Start-up period cancelled - Bad signal received before start-up time expires
DX4885p
AIP
SUP
AIP started SUP started SUP cancelled (for example, LOS) AIP expires
AIP restarted AINS disabled
Legend
LOS = Loss of signal
Figure 5-12 on page 5-33 shows the scenario where the AIP starts, a good
signal is received, and the SUP timer starts. The AIP timer expires before the
SUP timer expires but is ignored. Then, the SUP timer expires and the AINS
is disabled.
Figure 5-12
Alarm inhibit period expires before start-up expires
DX4886p
AIP
SUP
AIP started SUP started AIP expires SUP expires

but is ignored AINS disabled
Legend

Figure 5-13 on page 5-34 shows the scenario where the AIP starts, a good
signal is received, and the SUP timer starts. The AIP timer expires before the
SUP timer expires but is ignored. Then, the SUP timer is cancelled and at the
same time, the AIP timer is restarted from the initial value.
Figure 5-13
Alarm inhibit period expires and start-up period cancelled
DX4887p
AIP AIP Reset
SUP
AIP SUP started AIP expires SUP cancelled

started but is ignored AIP reset
Legend
Alarms that can be masked by AINS

The following alarms can be masked by AINS:
• PM 15min path threshold
• PM day path threshold
• PM Physical TCA
• PM OPR out of range
• MS RDI
• MS AIS
• Loss of frame
• Loss of signal
• MS Signal degrade
• MS Excessive BER
• PM day MS/RS threshold
• PM 15min MS/RS threshold
• PM 1min MS/RS threshold
• Drop path AIS
• Drop path loss of pointer

• Drop path unequipped

• Drop signal label mismatch
• Drop path RFI
• Ethernet link down
• Ethernet link remote fail
• Ethernet link remote offline
The following lists the engineering rules and restrictions of the AINS feature:
• The global default apply command applies to all the facilities in the
network element.
• The AINS feature is not supported on TN-64X Regenerators.
• In-progress start-up period and alarm inhibit period recovery is not
maintained over restarts (hard and soft) and upgrades.
SDH overhead Orderwire

The SDH Orderwire feature provides access to two voice frequency (VF)
communication channels via the E1 and E2 overhead bytes of the OPTera
Connect DX network. The connectors on the Orderwire circuit pack and the
local craft access panel (LCAP) allow headset, handset or modem access to the
VF channels, enabling voice or data communication between sites. The VF
data is encoded and transmitted within E1 and E2 bytes of the SDH overhead.
A typical example of Orderwire usage is during maintenance activities, when

crafts people at two adjacent sites would use headset devices to talk to each
other to co-ordinate their actions and confirm diagnostic results (see Figure
5-14 on page 5-36).

Figure 5-14
Example of Orderwire usage
DX4567p
Handset Handset
Orderwire Orderwire
circuit pack circuit pack
Voice PCM data transported

through SDH overhead
STM-64 T/R STM-64 T/R

circuit pack circuit pack
SDH traffic + overhead

network element network element
Legend
PCM = pulse coded modulation
The Orderwire circuit pack (NTCA47AA) is an optional circuit pack that you
install in slot 15 of the control shelf of the OPTera Connect DX network
element. The Orderwire circuit pack provides access to two 64 Kbit/s channels
for VF communications with other OPTera Connect DX network elements that
are also equipped with Orderwire circuit packs. Conceptually, the Orderwire
circuit pack provides you with the capability of accessing two separate
conference bridges known as local Orderwire (LOW) and express Orderwire
(EOW). You can access the two communication channels through a handset, a
headset, VF-300 ports or public switched telephone network (PSTN) ports.
The following interfaces are located on the orderwire circuit pack faceplate:
• public switched telephone network (PSTN) connector

• VF-300 connector
The following interfaces for the following orderwire functions are located on
the LCAP:
• four-wire handset jack
• four-wire headset jack
• broadcast call button
• LOW select button with integrated light-emitting diode (LED)
• EOW select button with integrated LED
• Orderwire buzzer
A single OPTera Connect DX network element has the capability to bridge up
to six pulse coded modulation (PCM) VF channels into the SDH Orderwire
communication channels. The Open Access Orderwire feature allows you to
create Orderwire connections on any valid STM-64 T/R circuit pack pair (up
to a maximum of six Orderwire connections per Orderwire circuit pack
equipped on an OPTera Connect DX network element). Orderwire connection
record, addition, deletion and query functionality is provided through the
network element user interface. The bridging rules are as follows:
• A PCM channel selected for bridging will be bridged to both the LOW and
EOW.
• The local handset/headset may be bridged to either the LOW or EOW by
pressing the appropriate channel selector button (located on the LCAP).
• Incoming PSTN calls will always be bridged to the LOW. Outgoing PSTN
calls will be bridged to either the LOW or the EOW and is dependant upon
what the current local selection is.
• The VF-300 is bridged to either the LOW or EOW.
When the local Orderwire circuit pack is accessed from another network
element, a buzzer sounds and the LED flashes on the LCAP of the local
network element. You can call all sites without the use of a handset by
activating the broadcast call push-button switch on the LCAP. Each PCM
channel can bridge to a conference call in a network via the STM-64 T/R
interfaces of the network elements. The bridging connection is user
provisionable.
The SDH Orderwire feature enables:
• the provisioning of a manual seam per Orderwire connection

• the choice of selective or broadcast notification when originating an
Orderwire call
• the provisioning of mu-Law or A-Law compounding schemes
• Orderwire provisioning via software

• automatic provisioning of automatic seam at network element in the

direction where the fault occurs
• dynamic unbridging or bridging upon failure detection or removal
• the ability to bridge Orderwire channels to the PSTN. The PSTN
connection provides access for incoming or outgoing PSTN calls you can
bridge into an Orderwire conference call.
• access to a VF-300 port, which provides analogue access that you can use
to bridge voice frequency devices (example, a modem) to the LOW and
EOW channels
• interconnection of TN-64X and LH 1600 systems via VF-300 interface
For more details on the Orderwire functionality, provisioning, and
administration, refer to SDH Orderwire User Guide, NTCA66DA.
SDH Orderwire interworking with TN-64X network elements

You cannot access or passthrough SDH Orderwire traffic at a TN-64X ADM.
You cannot access but you can passthrough SDH Orderwire traffic at a
TN-64X Regenerator. For an TN-64X Regenerator to passthrough Orderwire
traffic over SDH overhead E1 and E2 bytes, would depend on amplification
mechanism used (as a regen can be equipped with MOR/MOR Plus, XR or
Rx/Tx pair for amplification purpose):
• MOR/MOR Plus amplifiers passes through both SDH LOW and EOW
• transponder/regenerator (XR) STM-64 interfaces passes through SDH
EOW only
• Rx and Rg/Tx STM-64 pair only passes through SDH EOW only
Note: Pre-OPTera Connect DX Release 5.0 Orderwire over optical service
channel (OSC) functionality remains unchanged.
Orderwire interworking with OPTera Long Haul 1600 network elements

You cannot access SDH Orderwire traffic on OPTera Long Haul 1600 network
elements. All the supported optical circuit packs would passthrough the SDH
Orderwire traffic over the E1 and E2 bytes except the XR circuit pack, which
would passthrough only EOW.
Note: Pre-OPTera Connect DX Release 5.0 Orderwire over OSC

functionality remains unchanged.
Orderwire circuit packs must be equipped on each OPTera Connect DX

network element in its path for Orderwire connectivity (see Figure 5-15 on
page 5-39). In this example, you must equip the middle (as well as the ends)
OPTera Connect DX network element with an Orderwire circuit pack to allow
Orderwire traffic between the end OPTera Connect DX network elements.

Figure 5-15
OPTera Connect DX SDH Orderwire interworking with OPTera Long Haul 1600 and TN-64X
Regenerators
DX4558p
DX LH 1600 DX TN-64X DX
Legend
DX = OPTera Connect DX network element

OW = orderwire
TN-64X = TN-64X regenerator equipped with Rx and Rg/Tx circuit pack pairs
LH 1600 = OPTera Long Haul 1600 repeater equipped with XR circuit packs
= Express OW
= Local OW

The following engineering rules and restrictions apply to the SDH Orderwire
feature:
• The SDH Orderwire is not supported on TN-64X or Long Haul 1600
platforms.
• The SDH Orderwire feature is only supported on the STM-64 interfaces,
and therefore is not supported on low-speed cross-connect OPTera
Connect DX network elements.
• The SDH Orderwire feature is not supported on tributaries.
• You cannot passthrough Orderwire traffic at an OPTera Connect DX
network element if the network element is not equipped with an Orderwire
circuit pack.
• Orderwire circuit packs must be equipped on a OPTera Connect DX
network elements in its path for SDH Orderwire connectivity.
• SDH Orderwire provisioning is not available via the OPC .

• You can only provision SDH Orderwire via the network element user
interface.
• Orderwire circuit pack does not support “quiet” PCM code generation.
Low-speed cross-connection provisioning enhancements
The low-speed cross-connection (LSXC) is a low cost application of the
OPTera Connect DX optical switch. OPTera Connect DX Release 5.0 and
above allows you to perform the SLAT operation of the LSXC without the
STM-64 circuit pack.
TL1 interface
The TL1 protocol allows an operations system to monitor a group of network
elements under the span of control of an OPC. The operations system can send
and receive TL1 commands and messages on the same X.25 link or
Transmission Control Protocol/Internet Protocol (TCP/IP) session from the
network elements which are in other span of control. You can use the same
TL1 interface for network surveillance, user administration functions,
equipment provisioning, and facility provisioning.
The TL1 user administration interface supports the management of users who
access the OPC and the network elements through TL1. A system
administrator can create, edit, and delete users and user accounts.
Preside
OPTera Connect DX Release 6.0 is aligned with Preside Optical Service
Release (OSR) 10.0 provides full support and is aligned with. The following
features are supported in Preside OSR 10 network management software:
• Applications Platform
• Trail Management
• Backup and Restore
• DWDM Management
• Optical Section View/DWDM View
• Optical Power Management
• Optical Connection Manager
Applications Platform
The Preside Applications Platform (AP) provides a view of protection
switching status and traffic routing. When monitoring the network, you can
quickly determine the state of the network by the information displayed in the
alarm banner. The alarm banner displays a summary of all the alarm counts in
the set of network elements that you can access. When an alarm condition
occurs, you can quickly identify the location of the alarm and then view the
active alarm details.

Preside AP Release 10.1 provides support to OPTera Connect DX Release 6

and includes the following:
• support for TN-64X on the Legacy platform and DX_ HUB network
element only on the OPTera Connect DX platform
• traffic display GUI support for specific configuration
• protection status and control GUI support
• shelf level view and remote inventory support
• centralized performance monitoring
• OPTera Connect DX GUI and contract interfaces support for fault
management, remote inventory and performance monitoring
• alarm monitoring and history
• service provisioning
For more information, refer to the Preside Applications Platform 10.1
Planning Guide, 450-3101-601 or the latest Preside Application Platform 10.1
Operational Considerations.
Trail Management
Trail Management provides an end-to-end circuit viewing, querying,
connection and bandwidth management capability for optical networks. Trail
Management Release 5.0 provides support to OPTera Connect DX Release
6.0.
For more information, refer to the Preside Trail Management 5.0 Planning
Guide, 450-3101-608 or the latest Preside Trail Management 5.0 Operational
Considerations.
Backup and Restore

The Backup and Restore optional application enables you to easily backup
data from network elements or OPCs. The backup feature allows you to
centralize and automate the backup of network element database and OPC
configuration data to a Preside AP server. The restore feature allows you to
restore the backed up data when required.
With the Backup and Restore application, you can create network wide
backups, which are placed on centralized storage (such as a hard drive). You
can use the backup to restore the OPC in the event of a network element
controller hardware failure or to recover from a provisioning error.
Backup and Restore Release 2.1 provides full support to OPTera Connect DX
Release 6.0. For more information, refer to the Preside Backup & Restore
Planning Guide, 450-3101-637.

DWDM Management
Preside's complete DWDM Management solution answers essential optical
networks management requirements in the following key areas:
• power monitoring: guarantees accuracy of transmitted information by
ensuring quality of signal through Preside OPM
• representation: allows you to view both active and passive optical
components with Preside OSV
• topology: allows you to understand and manage the behavior of
wavelengths and payloads (with connectivity and layering provided by
Preside)
Optical Section View/DWDM View
The Optical Section View (OSV) is an add-on application for Preside that
enables the Graphical Network Browser (GNB) users to display the physical
connectivity of the optical components that comprise an optical section. The
Preside Optical topology database provides the GNB data about the optical
network elements. This data includes information about passive optical
devices provided by the Node Modeler and physical connectivity between
optical components provided by NetBuilder.
The DWDM View is an add-on application for Preside that enables the
DWDM layer to be managed separately from the SDH layer. The DWDM
View displays the optical link for multiple wavelengths. The DWDM View
can display all the wavelengths that go through an amplifier. The display of the
optical link is from one DWDM coupler to another DWDM coupler.
The DWDM View and OSV complement each other to combine the
management of multiple wavelengths in conjunction with the SDH layer. The
DWDM View (like the OSV) shares the same common database with the Trail
Manager application, which means that both applications can be deployed
co-resident on the same workstation.
OSV Release 6.0/DWDM View 2.0 provides support to OPTera Connect DX

Release 6.0. For more information, refer to the Optical Sections
View 6.0/DWDM View 2.0 Planning Guide, 450-3101-632 or the Optical
Sections View 6.0/DWDM View 2.0 Operational Considerations.
Optical Power Management

The Preside Optical Power Management (OPM) application eases the
management of DWDM systems by providing the capabilities to:
• view all wavelengths that go through a given optical amplifier
• view details on the optical components of each wavelength: transmit (Tx),
receive (Rx), and amplifier information
• monitor the power on each of the components (for example, Tx power, Rx
power, channel input/output power)

• provide graphs for quick access and interpretation of values (for example,
Rx input power vs wavelengths or Signal Quality vs wavelengths)
• adjust the Tx power from the application without having to remote login
into the network elements
OPM Release 4.0 provides support to OPTera Connect DX Release 6.0. For
more information, refer to the Preside Optical Power Management 4.0
Planning Guide, 450-3101-633 or the latest Preside Optical Power
Management 4.0 Operational Considerations.
Optical Connection Manager

Optical Connection Manager (OCM) is an application that provides the ability
to provision, delete, and query connections on a nodal and sub-network basis
via the following connection management functions:
• Subnetwork nodal - allows the user to manage nodal cross connections on

a single node and allows the user to step through the network and provision
connections node by node if sub-network configuration or topology data is
available to the Optical Connection Manager.
• Sub-network Multi-nodal - allows the users to manage multi-nodal
connections (one node NE A to another node NE Z) based on available
configuration (i.e. MS-SPRing configuration) or topology data.
Additionally, it allows the user to continue a multi-nodal or nodal
connection into another configuration.
• OCM Release 2.0 provides support to OPTera Connect DX Release 6.0.
For more information, refer to the Preside Optical Connection Manager
2.0 Planning Guide, 450-3101-628.
Preside Software Upgrade Management support
The purpose of Preside Software Upgrade Management (PSUM) is to deliver
new software to the processors of one or more network elements (NE), and to
upgrade the circuit pack cards on these network elements.
Preside SUM is a network-level application installed on the Preside

Applications Platform. Preside SUM provides fast, simple, and reliable
software upgrade deployment across a network, from a single location.
Preside SUM Release 3.0 provides upgrade support of OPTera Connect DX

network elements controlled by a operational controller (OPC).
For more information on Preside Software Upgrade Management capability,

refer Preside Software Upgrade Management Release 3.0 documentation
(NTNM26DA).


6-1
Hardware feature description 6-

This chapter provides a description of hardware features that are part of an
The following is a list of the new hardware introduced OPTera Connect DX

Release 6.0:
• Quad STM-16 short reach (SR) T/R circuit pack, (PEC NTWR31AB)
• Quad STM-16 intermediate reach (IR) T/R tributary circuit pack,
(PEC NTWR31BA)
• STM-16 long reach (LR) T/R tributary circuit pack, (PEC NTCA30AN)
• Dual Gigabit Ethernet extended reach (ZX) T/R tributary circuit pack
(PEC NTCA90GA)
For more detailed information on these new hardware features, refer to
Chapter 2, “New feature content” of this document.
OPTera Connect DX network element bay

The OPTera Connect DX network element bay is a front-access frame that is
compatible with overhead and underfloor cabling.
The OPTera Connect DX bay frame is available in one height, 2.125 m

(83.7 in). For OPTera Connect DX Release 5.0 or higher, the DX_HUB is the
only network element that is supported on the OPTera Connect DX platform.
You can provision the eight 10 Gbit/s high-speed interfaces in the universal
slots to support the following mixed configurations:
N = (8 - (4xP))/2]
M = (8 - (4xP))/2]
• mixed Px4-Fiber Ring and Mx(0:1) [where P is 0 to 2 and
M = 8 - (4xP)]
[where P is 0 to 2, N is 0 to 4, M is 0 to 4 and K = 8 - [(Px4) + 2x(N+M)]]

6-2 Hardware feature description

M = (8 - (2xN))/2].
M is 0 to 4 and K = 8 - 2x(N+M)]
An OPTera Connect DX bay contains the following elements:
• Control shelf
• Main transport shelf
• Extension shelf (see Note 1)
• Local craft access panel (LCAP)
• Two Optical fiber cable management (see Note 2)
• Two Environmental control panels (see Note 3)
Note 1: You can order an OPTera Connect DX bay with an extension shelf
(NTCA91AB/AC) or without an extension shelf (NTCA91AA/BA). The
NTCA91BA is the OPTera Metro Connect bay. The NTCA91AC is the
OPTera Connect DX bay with rear exhaust.
Note 2: Fiber management hardware is not included on the OPTera Metro
Connect bay and the OPTera Connect DX bay with rear exhaust.
Note 3: One environmental control panel is included with the OPTera
Metro Connect bay.
When no coaxial cabling is present, the OPTera Connect DX bay can
accommodate up to 240 single optical fibers, up to 64 external breakout optical
fiber cable assemblies or 64 optical fiber cable assemblies. The optical fiber
cable assemblies are required for the HD STM-1o tributary circuit packs. Each
optical fiber cable assembly includes 8 single mode optical fibers. The OPTera
Connect DX bay can also accommodate a maximum of 8 STM-1e coaxial
cables. You perform peripheral cabling (parallel telemetry [PT], maintenance
interface [MI], and operations controller [OPC]) at the control shelf level, in
the input/output (I/O) section, using connectorized cables.
Power connections, office alarm and external synchronization interface (ESI)

terminations reside at the top of the bay. Figure 6-1 on page 6-4 shows an
OPTera Connect DX bay. Figure 6-2 on page 6-5 shows an OPTera Metro
Connect bay.

TN-64X network element bay

The TN-64X network element bay is a front-access frame that is compatible
with overhead and underfloor cabling.
The TN-64X bay frame is available in one height, 2125 mm (84 inches). You
can configure each bay as a single 4-Fiber ADM or as a regenerator (Regen).
A TN-64X bay contains the following elements:

• Control shelf
• Main transport shelf
• Line extension shelf
Note: The TN-64X bay configured as a single 4-Fiber ADM requires a
line extension shelf.
• Local craft access panel (LCAP)

• Five fiber management trays
• Environmental control panel (ECP)
The following elements are optional:
• Dense Regen extension shelf
Note: Only a TN-64X bay configured as a Regen, supports the dense
Regen shelf.
• Dense wavelength division multiplexing shelf assembly (DWDM)

• DWDM couplers
• Dispersion compensation module assembly (DCM)
When no coaxial cabling is present, the TN-64X bay can hold a maximum of
84 optical fibers. The TN-64X bay can hold a maximum of 16 STM-1 coaxial
cables. You perform peripheral cabling (PT, MI, OPC and Orderwire) at the
control shelf level, in the input/output (I/O) section, using connectorized
cables.
Power connections, office alarm and external synchronization interface (ESI)

terminations reside at the top of the bay.

Figure 6-1
OPTera Connect DX bay with extension shelf
DX2710p
Cable Cover
(both sides)
Control shelf
Fan
(3 places)
Upper main transport

shelf
Lower main transport

shelf
Fan
(3 places)
Extension shelf

Figure 6-2
OPTera Metro Connect bay
DX4119p
Cable Cover
(both sides)
Control shelf
Fan
(3 places)

shelf

shelf

Control shelf
The control shelf is divided into four different sections:
• the termination panel
• the power section
• the control section
• the I/O section
Termination panel
The termination panel includes two separate areas (see Figure 6-3 on page
6-7):
• the synchronization, alarms, and telemetry terminations (SATT)
wire-wrap/connector field, where ESI and office alarms connect
• the external power terminations, used to terminate the power feeds
Power section
The power section (slots 1 and 2) contains redundant breaker/filter modules,
one for Battery A power feed, the second for Battery B power feed. Both
breaker/filter modules must be present in the control shelf for all
configurations (see Figure 6-4 on page 6-8).
Control section
In an TN-64X 4-Fiber ADM or OPTera Connect network element, the control
section (slots 3 through 8) contains the shelf controller (SC) and two ESI
circuit packs (one working, one protection). The control shelf also contains the
partitioned OPC module. The partitioned OPC module contains the partitioned
operations controller (POPC), the partitioned OPC storage circuit pack
(POPS), and the OPC interface circuit pack (POPI).
Note 1: For TN-64X, the Regen and the MOR stand-alone configurations
do not support ESI circuit packs.
Note 2: Install the POPC and POPS circuit packs only if the TN-64X
network element contains a partitioned OPC module. If this network
element does not contain a partitioned OPC module, install filler cards in
these positions.
I/O section
Recessed circuit pack positions allow peripheral cabling of different circuit
packs in the I/O section (slots 9 through 17) of the control shelf. You require
the MI circuit pack and two message exchange (MX) circuit packs for all bay
configurations except the OPTera Metro Connect bay. One MX circuit pack
(two recommended) is supported on the OPTera Metro Connect bay. In
addition, if you equip the OPC interface circuit pack it must be in the I/O
section.

The I/O section of the control shelf can also contain the following optional
circuit packs:
• two parallel telemetry (PT) circuit packs (in slots 13, 14)
• an Orderwire circuit pack
Note 1: OPTera Connect DX Release 5.0 or higher supports the Orderwire
circuit pack. For information concerning the Orderwire functionality, refer
to the SDH Orderwire User Guide, NTCA66DA.
Note 2: Unequipped circuit pack slots in both control and I/O sections
must be equipped with proper filler cards. For details about the listed
circuit packs, refer to Circuit Pack Descriptions, 323-1531-102.
Figure 6-3
Control shelf (typical configuration)
F3153-4_R21
Power
terminations
SATT wire wrap

connector field
Power
section
Control
section
I/O section

Figure 6-4
Circuit pack location in the control shelf
DX4967p
Breaker/filter module A
Breaker/filter module B
OPC controller
OPC storage
OPC I/F
ESI G1
ESI G2
MX G1
MX G2
PT G2
PT G3
Filler
Filler
OW
SC
MI
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Note 1: The parallel telemetry (PT) circuit packs and the Orderwire (OW) circuit pack
are optional circuit packs.
Note 2: The second MX circuit pack (MX G2) is highly recommended
but it is not mandatory.
Note 3: OPC circuit packs in slots 3, 4, 5, and 12 are not required in every network element.
All three circuit packs are only required in a network element that houses the primary
OPC or backup OPC.
Local craft access panel

Located at the bottom of the control shelf, the local craft access panel (LCAP)
is a field replaceable unit that provides the technician with different
functionality (see Figure 6-5 on page 6-10).
RS-232 interface
An RS-232 interface connector provides interconnection with a
VT100-compatible terminal used to access the network element user interface
(NE UI).

Orderwire features
The LCAP provides the following orderwire features:
• headset jacks allow for the connection of a headset, for local and express
voice channels
• call push button initiates a call on a selected voice channel to all applicable
sites in the system
• local channel light emitting diode (LED) lights up when the channel is in
use, and flashes when there is an incoming call on the channel
• local channel push button to select the local voice channel
• express channel LED lights when the channel is in use, and flashes when
there is an incoming call on the channel
• express channel push button to select the express voice channel
• handset jacks allow for the connection of a handset, for local and express
voice channels
• call buzzer (internal, not shown in Figure 6-5 on page 6-10) provides
audible indication that an orderwire call is incoming
Note: The Orderwire circuit pack must be inserted in the Control Shelf in
order for these features to work.
Other features
The LCAP provides other features such as:
• lamp test button, when pressed, activates all the circuit packs, LCAP, and
bay light emitting diodes (LED) for a fixed period of 30 seconds
• alarm cutoff (ACO) switch allows the technician to mute the audible alarm
condition
• ACO LED indicates that the ACO switch has disabled one audible alarm
and at least one visible alarm is present. The ACO LED turns off when the
system raises a new alarm or when you clear all alarms.
• power lamp (hardware controlled), a green LED which indicates the power
status of the bay
• alarm lamps (critical, major, and minor) indicate that the system has raised
an alarm on the NE, and indicate the severity of the alarm
• circuit-breaker trip indicator indicates the system has tripped one or more
circuit breakers
• electrostatic discharge (ESD) jack allows for the connection of a
grounding device, such as a wrist type ground strap
• alarm buzzer provides audible indication when the system raises an alarm

Figure 6-5
Local craft access panel
F3181
RS232
Headset
Call
Local
Express
Handset
Lamp test
Alarm cutoff
Power
Critical
Major
Minor
Breaker trip
ESD jack
Optical fiber cable management

OPTera Connect DX Release 6.0 supports fiber cable management for the
HD STM-1o T/R tributary circuit packs:
• optical fiber cable assemblies
• breakout optical fiber cable assemblies
You cannot use the existing fiber management trays on the OPTera Connect
DX bay to manage optical fibers for the HD STM-1o tributary circuit packs.
The existing fiber management trays on the OPTera Connect DX bay continues
to manage the optical fibers from other tributary circuit packs as well as the
STM-64 T/R circuit packs. For more information on the fiber cable
management for the HD STM-1o tributary circuit packs, refer to Chapter 9
“Ordering information” of this document.

Fiber management trays

Fiber management trays manage optical fiber cable slack going in and out of
the bay. The fiber management unit on the standard OPTera Connect DX bay
(NTCA91AB) contains two separate pull-out trays. The fiber management
unit on the TN-64X bay contains five separate pull-out trays, available in two
formats: standard and dense. The OPTera Metro Connect bay (NTCA91BA
and the OPTera Connect DX rear exhaust bay do not contain fiber management
trays.
The fiber management unit (located below the LCAP) contains two separate
pull-out trays that are available in standard format (NTCA84GA). The basic
configuration (NTCA91AB available with the OPTera Connect DX network
element) has 20 fiber reels in each tray for discrete fiber storage. Each reel can
store up 2 m of optical fiber patch cord slack with or without miniature variable
optical attenuators (mVOAs) without affecting the allowed bend radius.
Figure 6-6 on page 6-12 shows a standard OPTera Connect DX fiber
management tray unit equipped with 20 optical fiber reels.
For the TN-64X bay, each optional dense fiber management tray can manage
up to 12 dual-fiber optical cables (24 lines) and related optical devices for
Quad tributaries on a main transport shelf. The optical patch cords do not
require space for extra slack. Figure 6-7 on page 6-13 shows the left-entry
dense fiber management shelf with one fiber interface panel (FIP) tray open.
Figure 6-8 on page 6-14 shows the standard equipment that is equipped in the
OPTera Connect DX fiber management trays to manage optical fiber cables
more easily.
Fiber management hardware kit

Figure 6-9 on page 6-15 shows the optional equipment that you can add to the
TN-64X fiber management trays to manage optical fiber cables more easily.
The optional fiber management hardware kit (NTCC8414) includes:
• five mVOA clips to hold mVOAs, and five plastic rivets to attach the clips
• two connector plates to hold optical fiber adapters
• 20 optical fiber reels to store excess optical fiber cables
• four reel posts and two WDM plates

Figure 6-6
OPTera Connect DX fiber management tray with 20 optical fiber reels (one is shown with optical
fiber)
DX0423

Figure 6-7
Dense fiber management shelf (left entry) with one fiber interface panel (FIP) tray open
F5518-192_R60.EPS
FIP drawer
(closed)
Fiber
snakes
FIP drawer
(open)

Figure 6-8
OPTera Connect DX optical fiber management tray equipped with the hardware kit (20 optical fiber
reels)
DX0424

Figure 6-9
TN-64X fiber management tray equipped with optional fiber management hardware kit
(NTCC8414)
F3179-2-192_R30
Fiber
snake
DCM clip
WDM plate
MVOA clip
Fiber reel
(5 per stack)
Connector
plate
Fiber
snake

Main transport shelf

The main transport shelf can contain different circuit packs depending on the
configurations on the network element. The DX_HUB network element
supports following 10 Gbit/s configurations:
• mixed Px4-Fiber Ring and Nx2-Fiber Ring [where P is 0 to 2 and N = (8 -
(4xP)/2)]
M = (8 - (4xP))/2].
[where P is 0 to 2, N is 0 to 4, M is 0 to 4 and K = 8 - [(Px4) + 2x(N+M)]]
M = (8 - (2xN))/2].
• mixed Nx2-Fiber Ring, Linear Mx(1+1) and Kx(0:1) [where N is 0 to 4, M
is 0 to 4 and K = 8 - 2x(N+M)]
10 Gbit/s optical interfaces.
(NTCA26BA) or DX65 switch modules (NTCA26AA) the following
• Nx4-Fiber Ring (N is 1)
• mixed Px4-Fiber Ring and Nx2-Fiber Ring [where P is 0 or 1 and N = (4 -
(4xP)/2)]
• mixed Px4-Fiber Ring and Linear Mx(1+1) [where P is 0 or 1 and
M = (4 - (2xP))/2].


• Nx2-Fiber Ring (N is 1 or 2).
M = (4 - (2xN))/2].
M is 0 to 2 and K = 4 - 2x(N+M)]
• Linear Nx(1+1) (where N is 1 or 2) mixed Linear Nx(1+1) and Mx(0:1)
[where N is 0 to 2 and M = 4 - (2xN)]
10 Gbit/s optical interfaces.
equipped with DX100 or DX65 switch modules.
Note 3: Empty slots on the network element must be equipped with
appropriate filler cards. Filler cards make sure there is adequate airflow
within the bay.

Tributary circuit packs for any configuration

Table 6-1 on page 6-18 shows the circuit pack group (CPG) name mapping and
slot assignment for each supported tributary circuit pack in the main transport
shelf and extension shelf.
Table 6-1
Supported tributary circuit pack group types
Circuit pack group type CPG name Slot
Quad STM-1o/e G1 - G8 2-9
HD STM-1o/e (see Note 2, Note 3 G0 - G12 or G17 - G19 1 - 13 or 16 - 18

and Note 4)
Quad STM-4 G1 - G8 2-9
STM-16 G1 - G8 2-9
Dual STM-16 (see Note 2 and G0 - G12 or G17 - G19 1 - 13 or 16 - 18

Note 4)
Quad STM-16 (see Note 2 and G0, G9 - G12, or G17 - G19 1, 10 -13 or 16 - 19
Note 4)
Dual Gigabit Ethernet G0 - G12 or G17 - G19 1 - 13 or 16 - 18

(see Note 4)
STM-64 See Table 6-2 for the STM-64 CPG for different
configurations
Switch A, B (see Note 1) 14, 15
Extension shelf
Quad STM-1o/e G21 - G28 2-9
HD STM-1o/e (see Note 2 and G21 - G28 2-9

Note 3)
Quad STM-4 G21 - G28 2-9


Supported tributary circuit pack group types
Circuit pack group type CPG name Slot
STM-16 G21 - G28 2-9
Dual Gigabit Ethernet G21 - G28 2-9
Note 1: If you equip the extension shelf with tributary circuit packs, you must also
equip the DX_HUB network element with either DX100 or DX140 switch modules.
Note 2: If you equip the DX_HUB network element with this circuit pack, you must
also equip the DX_HUB network element with either DX100 or DX140 switch
modules.
Note 3: You can equip up to 16 HD STM-1o, or up to 8 STM-1e.
Note 4: If you equip this circuit pack in the universal slots, you must also equip the
network element with either DX100 or DX140 switch modules.

STM-16 circuit pack network configurations

Table 6-2 on page 6-20 shows the STM-16 CPG names mapping and slot
assignment for each supported network configuration.
Table 6-2
STM-64 circuit pack group types in different configurations
STM-64 Configurations CPG names Slots
4-Fiber Ring G11/G12 and G17/G18 12/13, 16/17

or or
4-Fiber ADM chain G0/G10 and G9/G19 1/11, 10/18
2-Fiber Ring G11/G12, G17/G18, 12/13, 16/17
Linear 1+1 terminal G0/G10 or G9/G19 1/11 or 10/18
Unprotected 10 Gbit/s terminal G11, G12, G17, G18 12, 13, 16, 17,
G0, G10, G9 or G19 1, 11, 10, 18
Note: STM-64 interfaces are not supported on low-speed cross-connect

configuration
Figure 6-10 on page 6-21 shows the main shelf of the OPTera Connect DX
network element with DX65 switch modules. The DX65 switch modules
support STM-64 circuit packs only in slots 12 (G11), 13 (G12),
16 (G17) or 17 (G18).
network element with DX100 switch modules. The universal slots 12 (G11),
13 (G12), 16 (G17) or 17 (G18) supports STM-64 circuit packs or tributary
circuit packs as described in Table 6-1 on page 6-18.
network element with DX140 switch modules. The universal slots 1 (G0), 10
(G9), 11 (G10), 12 (G11), 13 (G12), 16 (G17), 17 (G18) or 18 (G19) supports
STM-64 circuit packs or tributary circuit packs as described in Table 6-1 on
page 6-18.
Note: An OPTera Connect DX low-speed cross-connect network element

is a network element without STM-64 circuit packs. Depending on the type
of switch modes, the network element supports different type of tributary
circuit packs in the universal and tributary circuit pack slots. Figure 6-10
to Figure 6-12 shows the circuit packs slots that are supported with
different type of switch modules. Table 6-1 on page 6-18 shows the
tributary circuit packs and their supported circuit pack slots.

Figure 6-10
1
Filler G0
11
Filler
G10
2
Tributary circuit pack
12
G1
G11
STM-64 T/R circuit pack slot slot
13
G2
G12
4
G3
slot
DX65 Switch module A
14
5
G4
slot
6
G5
slot
DX65 Switch module B
15
7
G6
slot

16
8
G7
G17
9 Tributary circuit pack
17
G8
G18
10
18
G9
Filler Filler
G19
OPTera Connect DX main shelf showing supported circuit pack slots for DX65 switch modules

DX5356p
Figure 6-11
1
Filler
G0
11
Filler
G10
2
12
G1
G11
Universal slot slot

13
G2
G12
Universal slot slot
4
G3
slot
14
5
G4
slot
6
G5
slot
15
7
G6
slot

16
8
G7
G17
Universal slot slot
9
17
G8
Universal slot G18 slot

10
18
G9
Filler Filler
G19
DX5353p
Figure 6-12
11
G0
G10
Universal slot Universal slot
2
12
G1
G11
Universal slot slot
3
13
G2
G12
Universal slot slot
4
G3
slot
14
5
G4
slot
6
G5
slot
15
7
G6
slot
16
8
G7
G17

Universal slot slot
17
G18
G8
Universal slot slot

10
18
G9
G19


DX5354p
Environmental control panels

The OPTera Connect DX bay uses environmental control panels (ECPs) to
cool the bay circuit packs during operation by providing an airflow through the
shelves. The ECP raises alarms in case of failure, or when the temperature
exceeds the indicated limits. The environmental control panel requires no air
filter maintenance. Figure 6-13 on page 6-24 shows the ECP and the fan
modules.
Note: The fan modules do not have breaker/filter modules and they cannot
trip the main breaker/filter modules. The fan modules have an internal fuse
that prevents catastrophic failure.
For a functional description of the fan modules, refer to Circuit Pack

Descriptions, 323-1531-102.
Figure 6-13
Environmental control panel
DX2647
Fans
Environmental
control panel

Extension shelf
OPTera Connect DX Release 3 and higher software support the use of the
extension shelf. OPTera Connect DX Release 1 and 2 software do not support
the use of the extension shelf.
The extension shelf in OPTera Connect DX Release 3 and higher supports all
tributary circuit packs except the Dual STM-16 or Quad STM-16 T/R circuit
packs. You require either the DX100 or DX140 switch module to support
tributary circuit packs in the extension shelf (see Figure 6-14 on page 6-25).
The OPTera Metro Connect bay (NTCA91BA) is not equipped with an

extension shelf. The OPTera Metro Connect bay allows the installation of
Nortel Metro products with electrical interfaces (DS3, E1/T1) at the bottom of
the bay, or for the bottom of the bay to remain empty if you do not require the
tributary capacity of the extension shelf. For more information, refer to the
OPTera Metro Connect SDH User Guide, NTCA69YA.
Figure 6-14
OPTera Connect DX extension shelf showing supported circuit pack slots
DX5357p
G20 G21 G22 G23 G24 G25 G26 G27 G28 G29

slot
slot
slot
slot
slot
slot
slot
slot
Filler Filler
1 2 3 4 5 6 7 8 9 10

Transport interfaces
OPTera Connect DX
STM-64 T/R circuit pack
You can use the STM-64 transmitter/receiver (T/R) circuit pack as either an
OC-192 T/R or an STM-64 T/R circuit pack. The STM-64 T/R circuit packs
are required for the following 10 Gbit/s configurations: 2-Fiber Ring, 4-Fiber
Ring, 4-Fiber ADM chain, Linear 1+1 and unprotected configurations. The
STM-64 T/R circuit pack is capable of receiving and transmitting 10 Gbit/s of
traffic at the same time.
TN-64X
TN-64X Transmit interface
Application-specific transmitters are required for the TN-64X network
element configured either as 4-Fiber ADM or Regen. Transmitters are usually
placed in slots 13 and 16 of the main transport shelf for 4-Fiber ADM and in
slots 3 and 8 of the line extension shelf of a 4-Fiber ADM configuration. The
Regen transmitters are allocated to slots 2, 4, 8, and 10 of the main transport
shelf.
You must know the dispersion ranges expected from the fiber plant before you
can order the proper transmitter type. For an installed section of fiber plant
with +250 to –1000 ps/nm dispersion (typically on NDSF), you must use a
negative chirp transmitter type. You must use the positive chirp transmitter
selection for a dispersion of –250 to +1500 ps/nm. You can use either
transmitter type for the –250 to +250 ps/nm range. You can provision the chirp
on the network element user interface (NE UI).
TN-64X Receive interface
The receivers are also applicable to TN-64X 4-Fiber ADM or Regen
applications. The locations for the receivers vary with each application. The
receivers are found in slots 11 and 18 of the main transport shelf for 4-Fiber
ADM and in slots 1 and 10 of the line extension shelf for 4-Fiber ADM
applications. For Regen applications, the receivers are placed in slots 1, 3, 7
and 9 of the Regen main transport shelf.
TN-64X demultiplexer
TN-64X demultiplexers (Demux) are required in TN-64X 4-Fiber ADM
applications only. Install the Demux in slots 12 and 17 of the main transport
shelf and slots 2 and 9 of the line extension shelf.
OPTera Connect DX switch modules

The OPTera Connect DX Release 6.0 network element supports three different
types switch modules:
• DX65 switch module


The DX65 switch modules support up to 10 Gbit/s protected or 20 Gbit/s
unprotected of add/drop tributary traffic on the OPTera Connect DX network
element. The DX65 switch modules support tributary traffic in the tributary
section (slots 2 to 9) of the main shelf only. The extension shelf must be
equipped with filler cards. Two DX65 switch modules are required for 1+1
redundancy. The DX65 switch modules support STM-64 circuit packs only in
the slots 12 (G11), 13 (G12), 16 (G16) and 17 (G18). The DX65 switch module
does not support tributary circuit packs in the slots and HD STM-1o/e, Dual
STM-16, or Quad STM-16 tributary circuit packs.

unprotected add/drop tributary traffic on the OPTera Connect DX network
element. The 50 Gbit/s protected or 100 Gbit/s tributary traffic includes
30 Gbit/s protected or 60 Gbit/s unprotected tributary traffic in slots 2 to 9 of
the main shelf and extension shelf and an additional 20 Gbit/s protected or
40 Gbit/s unprotected tributary traffic in the universal slots 12 (G11), 13
(G12), 16 (G16) and 17 (G18). The DX100 switch modules support tributary
traffic in the main and extension shelves. Two DX100 switch modules are
required for 1+1 redundancy. The DX100 switch modules support STM-64
circuit packs, or HD STM-1o/e, Dual STM-16, Quad STM-16, or Dual GE
tributary circuit packs in universal slots 12 (G11), 13 (G12), 16 (G16) and 17
(G18) only.

unprotected add/drop tributary traffic on the OPTera Connect DX network
element. The 70 Gbit/s protected or 140 Gbit/s tributary traffic includes
30 Gbit/s protected or 60 Gbit/s unprotected tributary traffic in slots 2 to 9 of
the main shelf and extension shelf and an additional 40 Gbit/s protected or
80 Gbit/s unprotected tributary traffic in the universal slots 1 (G0), 10 (G9) 11
(G10), 12 (G11), 13 (G12), 16 (G16), 17 (G18) and 18 (G19). The DX140
switch module supports tributary traffic in the main and extension shelves.
Two DX140 switch modules are required for 1+1 redundancy. The DX140
switch modules support STM-64 circuit packs, or HD STM-1o/e, Dual
STM-16, Quad STM-16, or Dual GE tributary circuit packs in universal slots
1 (G0), 10 (G9) 11 (G10), 12 (G11), 13 (G12), 16 (G16), 17 (G18) and 18
(G19).
The switch modules supports all of the mix configurations up to its capacity.
Quad STM-1o/e T/R tributary circuit pack
The TN-64X and OPTera Connect DX network elements support the
Quad STM-1o T/R tributary circuit pack. The Quad STM-1o/e T/R tributary
circuit pack is a full-height circuit pack and has four STM-1o/e T/R facilities.

The Quad STM-1o/e tributaries supports 1+1 (revertive or nonrevertive and

bidirectional or unidirectional) and unprotected (bidirectional or
unidirectional) protection scheme. For a MS-switched matched node,
protection switching is 1*1 unidirectional revertive at the primary gateway
node.
An TN-64X network element can support up to 8 Quad STM-1o circuit packs

in slots 2 through 9 in the tributary section of the main transport shelf.
An OPTera Connect DX network element equipped with DX65 switch

modules can support up to 8 Quad circuit packs in slots 2 through 9 in the
tributary section of the main transport shelf only. The network element can
also support up to 4 Quad STM-1e circuit packs in slot 2 to 9 in the tributary
section of the main transport shelf. Because of cable management limitations,
a maximum of two Quad STM-1e circuit packs can be installed in slots 2 to 5
and a maximum of two Quad STM-1e circuit packs can be installed in slots 6
to 9.
An OPTera Connect DX network element equipped with DX100 or DX140

switch modules can support up to 8 Quad STM-1o circuit packs in slots 2
through 9 in the tributary section of the main transport shelf and up to 8 Quad
STM-1o circuit packs in slots 2 through 9 in the extension shelf. The network
element can also support up to 4 Quad STM-1e circuit packs, up to 4 in the
main transport shelf and up to 4 in the extension shelf. Because of cable
management limitations, a maximum of two of the Quad STM-1e circuit packs
each can be installed in slots 2 to 5 of the main shelf, slots 6 to 9 of the main
shelf, slot 2 to 5 of the extension shelf or slot 6 to 9 of the extension shelf.
You must install filler cards in all unused slots.
HD STM-1o/e T/R tributary circuit pack

The HD STM-1o/e T/R tributary circuit packs are supported on the OPTera
Connect DX network element only. The HD STM-1o/e T/R tributary circuit
pack is not supported on the TN-64X network element. The HD STM-1o/e T/R
tributary circuit pack is a full-height circuit pack and has 16 STM-1o T/R
facilities.
The HD STM-1o/e tributaries support is 1+1 (revertive or nonrevertive and

node.

modules do not support the HD STM-1o/e tributary circuit packs.


modules can support:
• up to 8 HD STM-1o/e circuit packs, in slots 2 through 9 in the tributary
circuit pack slots of the main transport shelf
• up to 4 HD STM-1o/e circuit packs in universal slots 12, 13, 16 or 17 of
the main transport shelf
• up to 8 HD STM-1o/e circuit packs in slots 2 through 9 in the extension
shelf
• up to 8 HD STM-1o/e circuit packs, in slots 2 through 9 in the tributary
• up to 8 HD STM-1o/e circuit packs in universal slots 1, 10, 11, 12, 13, 16,
17 or 18 of the main transport shelf
• up to 8 HD STM-1o/e circuit packs in slots 2 through 9 in the extension
shelf
Note: The maximum number of HD STM-1o/e circuit packs that is
supported on an OPTera Connect DX network element is 16. When the
maximum number of HD STM-1o/e circuit pack is exceeded, an alarm
“CPG provisioning limit exceeded’ is raised against any HD STM-1o/e
circuit pack that is provisioned after the 16th. The alarm can be cleared
when the 17th and higher HD STM-1o/e circuit packs are removed or
when the HD STM-1o/e circuit packs are deleted to reduce the number to
16. If the network element is provisioned with 15 HD STM-1o/e circuit
packs and the default protection scheme of the STM-1 interface is 1+1
protected, the alarm is also raised when the 16th HD STM-1o/e
autoprovisions.
Note: The maximum number of HD STM-1e circuit packs that is

supported on an OPTera Connect DX network element is 8.
Half-height STM-4 or Quad STM-4 T/R tributary circuit packs

The half-height STM-4 T/R tributary circuit packs are supported on the
TN-64X network element only. The Quad STM-4 T/R tributary circuit packs
are supported on the TN-64X and OPTera Connect DX network elements.
The half-height STM-4 T/R tributary circuit pack has one STM-4 T/R tributary
interface. The Quad STM-4 T/R tributary circuit pack is a full-height circuit
pack and has four STM-4 T/R tributary interfaces.

One STM-4 circuit pack carrier assembly kit is required for every slot
equipped with half-height STM-4 T/R circuit packs. Each kit provides the
material to assemble one circuit pack carrier. A circuit pack carrier provides
the mechanical support for two half-height STM-4 circuit packs.
The STM-4 tributaries support 1+1 (revertive or nonrevertive and

node. For SNCP Rings, the protection switching scheme is SNCP
(unidirectional and nonrevertive).
An TN-64X network element can support up to 16 half-height STM-4 circuit

packs or up to eight Quad STM-4 circuit packs in slots 2 through 9 in the
tributary section of the main transport shelf.

modules can support up to 8 Quad STM-16 circuit packs in slots 2 through 9
in the tributary section of the main transport shelf only.

• up to 8 Quad STM-4 circuit packs, in slots 2 through 9 in the tributary
• up to 8 Quad STM-16 circuit packs in slots 2 through 9 in the extension
shelf
• up to 8 Quad STM-4 circuit packs in slots 2 through 9 in the tributary
• up to 8 Quad STM-4 circuit packs in slots 2 through 9 in the extension shelf
Note: The Quad STM-4 circuit pack is not supported in universal slots 1,
10, 11, 12, 13, 16, 17 or 18 of the main transport shelf.
STM-16, Dual STM-16 or Quad STM-16 tributary circuit packs

The TN-64X and OPTera Connect DX network elements support the STM-16
T/R tributary circuit pack. The OPTera Connect DX network element also
supports the Dual STM-16 and the Quad STM-16 circuit packs. Each circuit
pack is a full-height circuit pack. The STM-16 T/R circuit pack has one T/R
facility. The Dual STM-16 T/R circuit pack has two T/R facilities and the
Quad STM-16 T/R circuit pack has four T/R facilities.

The STM-16 tributaries support 1+1 (revertive or nonrevertive and

bidirectional or unidirectional), unprotected (bidirectional or unidirectional)
protection scheme, 2-Fiber MS-SPRing. For a MS-switched matched node
configuration, the protection switching is 1*1 unidirectional revertive at the
primary gateway node. For SNCP Rings, the protection switching scheme is
SNCP (unidirectional and nonrevertive).

modules can support up to 8 STM-16 circuit packs in slots 2 through 9 in the
tributary section of the main transport shelf only.

• up to 8 STM-16 or Dual STM-16 circuit packs, in slots 2 through 9 in the
tributary circuit pack slots of the main transport shelf
• up to 4 Dual STM-16 or Quad STM-16 circuit packs in universal slots 12,
13, 16 or 17 of the main transport shelf
• up to 8 STM-16 circuit packs in slots 2 through 9 in the extension shelf
• up to 8 STM-16 or Dual STM-16 circuit packs in slots 2 through 9 in the
tributary circuit pack slots of the main transport shelf
• up to 8 Dual STM-16 or Quad STM-16 circuit packs in universal slots 1,
10, 11, 12, 13, 16, 17 or 18 the main transport shelf
• up to 8 STM-16 circuit packs in slots 2 through 9 in the extension shelf
Note: The STM-16 circuit packis not supported in universal slots 1, 10,
11, 12, 13, 16, 17 or 18 of the main transport shelf.
Dual Gigabit Ethernet tributary circuit packs

The TN-64X and OPTera Connect DX network elements support the Dual
Gigabit Ethernet (GE) Extended Reach (ZX) tributary circuit packs, Dual
Gigabit Ethernet Long Reach (LX) T/R tributary circuit packs and the Dual
Gigabit Ethernet Short Reach (SX) T/R circuit packs. A Dual GE T/R circuit
pack has two GE T/R facilities. The Dual GE circuit packs operate in the
unprotected mode only.

modules can support up to 8 Dual GE circuit packs in slots 2 through 9 in the
tributary section of the main transport shelf only.


• up to 8 Dual GE circuit packs in slots 2 through 9 in the tributary circuit
pack slots of the main transport shelf
• up to 4 Dual GE circuit packs in universal slots 12, 13, 16 or 17 of the main
transport shelf
• up to 8 Dual GE circuit packs in slots 2 through 9 in the extension shelf
• up to 8 Dual GE circuit packs in slots 2 through 9 in the tributary circuit
pack slots of the main transport shelf
• up to 8 Dual GE circuit packs in universal slots 1, 10, 11, 12, 13, 16, 17 or
18 of the main transport shelf
• up to 8 Dual GE circuit packs in slots 2 through 9 in the extension shelf
Filler cards
Use the filler cards to fill empty slots on the main transport shelf and the
optional extension shelf in order to ensure proper cooling. Control shelf filler
cards are also required for empty slots in the control shelf to protect against
EMI emissions.
The single-slot filler cards (NTCA49AA) are used in all unequipped

full-height single slots of the OPTera Connect DX and the TN-64X network
elements. The half-height filler cards (NTCA49AC) are used in all unequipped
half-height slots of the TN-64X main transport shelf. Half-height filler cards
are not required on Regens. Also, since switch modules are not required on
Regens, the double-slot filler card (NTCA49AB) is used in slots 14 and 15 to
fill the empty slots in order to prevent forced air within the shelf from
escaping.
The control shelf filler cards are used according to the following rules:
• OPTera Connect DX network element
— single slot control shelf filler cards (NTCA59AA) are required for slots
15, 16, and 17
11, and 13, 14 if the redundant MX and the PT circuit packs are not
used
— two single slot control shelf filler cards (NTCA59AA) are required for
slots 3 and 4, and single slot control shelf filler cards (NTCA59AA) are
required for slots 5 and 12 if the partitioned OPC is not used

• TN-64X network element

— single slot control shelf filler cards (NTCA59AA) are required in slots
16 and 17
11, 13 and 14, and 15 if the redundant MX, the PT and the orderwire
circuit packs are not used
— two single slot control shelf filler cards (NTCA59AA) are required for
slots 3 and 4, and single slot control shelf filler cards (NTCA59AA) are
required for slots 5 and 12 if the partitioned OPC is not used
Note: In a TN-64X Regen configuration where ESI circuit packs are not
used, additional single slot control shelf filler cards (NTCA59AA) are also
required in slots 7 and 8.

Mandatory control shelf circuit packs

The following circuit packs are mandatory for the OPTera Connect DX,
TN-64X ADM and regenerators network elements.
Breaker/filter module
The breaker/filter modules (NTCA40BA) for the OPTera Connect DX bay are
composed of one 10 ampere and six 20 ampere circuit breakers, low-frequency
filtering and soft start circuits. The circuit breakers control power distribution
to the control shelf. Each of the circuit breakers are assigned a quadrant of the
main transport shelf and to each half of the extension shelf (Figure 6-15). Each
breaker/filter module is connected to the three parallel battery feeds located in
the power termination area. The circuit packs are located in slots 1 and 2 of the
control shelf, one circuit pack for battery A power feeds and one circuit pack
for battery B power feeds. Both circuit packs are required to offer power
redundancy.
Note: The breaker/filter modules (NTCA40AA) for the TN-64X bay are
composed of one 10 ampere and six 15 ampere circuit breakers, low
frequency filtering and soft start circuits.

Figure 6-15
OPTera Connect DX power distribution and circuit breaker assignment (one battery feed)
DX0657
-48 v connections on
external power termination,
at the top of the bay
(-) (-) (-)
A3 A2 A1
Breaker/filter
module Control shelf
1
1-17

2
1-5
2
6-10
2
11-14
2
15-18
Extension shelf
3
1-5
3
6-10
Note: Internal fuses located in the breaker/filter module, provide power to the fans.

Two breaker/filter modules (A and B) units must be equipped in slots 1 and 2

of the control shelf for redundant –48 v supply to the shelves (refer to Figure
6-16 on page 6-36). Each breaker/ filter module contains one 10 ampere and
six 20 ampere circuit breakers and the associated filters. The modules
distribute power to the control, main transport and extension shelves,
including the environmental control panel (ECP). In addition, the breaker/filter
modules attenuate the noise on the –48 v power lines. The filters also limit
current surges and clamp overvoltages.
Figure 6-16
Breaker/filter module and shelf assignment
DX3705
Control shelf
Slots 1-5 on
upper DX main transport shelf
Slots 6-10 on
Faceplate upper DX main transport shelf
Slots 11-14 on
lower DX main transport shelf
Slots 15-18 on
lower DX main transport shelf
Slots 1-5 on extension

shelf
Slots 6-10 on extension

shelf
Filter Module Label

Shelf controller
The Control shelf requires one shelf controller circuit pack, equipped in slot 6.
The shelf controller interfaces to all software-based circuit packs and serves as
a message gateway for data communications channel (DCC), external RS-232
and Ethernet. The shelf controller provides the following functions:
• alarm reporting
• PM collection
• system fault detection
• isolation and protection
• software download and upgrades and restart capability from local
nonvolatile flash on the MI circuit pack
The OPTera Connect DX bay supports the 32 Mbyte shelf controller. The
TN-64X Regen bay requires either the 16 or 32 Mbyte shelf controller. The
TN-64X ADM bay requires the 32 Mbyte shelf controller.
Note: The 16 Mbyte shelf controller is manufacture discontinued (MD).
External synchronization interface

The OPTera Connect DX or TN-64X ADM requires the external
synchronization interface circuit pack to synchronize to an external BITS or to
the TN-64X line source. The DS1 timing reference signals are connected to the
wire-wrap field on the SATT circuit pack. The 2 MHz timing reference signals
are connected to the coaxial connector field on the SATT circuit pack. The 2
Mbit/s timing reference signals are connected either to the coaxial connector
fields (75 ohms) or the wire-wrap fields (120 ohms) on the SATT circuit pack.
For protected operation, two ESI circuit packs must be equipped in slots 7 and
8 of the Control shelf. These circuit packs are required at each ADM network
element. They are not required on Regen sites since Regens are always
operating in through-timing mode.

Maintenance interface
The maintenance interface (MI) circuit pack is required for each bay and is
equipped in slot 9 of the Control shelf. The MI circuit pack houses one serial
RS-232 port and three Ethernet ports on its faceplate. The MI circuit pack
operates in conjunction with the shelf controller and contains 128 Mbyte of
flash memory which is used for configuration and code storage. The MI circuit
pack provides the following functions:
• alarm reporting
• processor sanity
• circuit pack inventory and status
• Ethernet/RS-232 port status
Note: The 128 Mbyte MI is required on the OPTera Connect DX bay. The
128 Mbyte MI is required on the TN-64X bay for commissioning. You can
perform upgrades and sparing on the TN-64X bay with a 32 Mbyte or 128
Mbyte MI.
Message exchange
The message exchange (MX) circuit pack is required in slot 10 and 11 of the
Control shelf. It handles internal communications between the control circuit
packs and the optical circuit packs, as well as DCC routing. The MX circuit
pack connects the shelf controller to all software based circuit packs in the bay
through the internal star-based LAN.
Note: It is highly recommended, but not mandatory, that you install a

second MX circuit pack in the control shelf.
Optional control shelf circuit packs

An optional circuit pack can be equipped in the input/output slots of the
Control shelf.
OPC controller circuit pack

The OPC controller circuit pack is the basic hardware component of the OPC
computing engine for the control shelf. The OPC controller provides
operations, administration, maintenance and provisioning (OAM&P)
functionality. It communicates with the OPC interface circuit pack, the OPC
storage circuit pack, the shelf controller circuit pack and the maintenance
interface circuit pack.

OPC storage circuit pack

The OPC storage circuit pack consists of a hard disk drive, electrically erasable
programmable read only memory (EEPROM) and a removable media
interface. OPTera Connect DX Release 1 introduced a 122 Mbyte removable
media interface.
The OPC storage circuit pack acts as an extension to the OPC controller.
Removable media
The removable media provides software download, save, and restore
capabilities for the network element. The 122 Mbyte removable media is
required for software upgrades to this release. However, you can use the
68 Mbyte removable media for OPC data backups.
OPC interface
The OPC interface circuit pack is intended to be a reactive circuit pack. The
OPC interface circuit pack provides the external customer interfaces for the
control shelf. It also communicates with the maintenance interface circuit pack
and the OPC controller circuit pack.
Message exchange (protection)

The message exchange (MX) circuit pack connects the shelf controller to all
software based circuit packs through an internal bus. It detects circuit pack
presence and supports inter-circuit pack messaging. The MXA circuit pack,
found in hardware slot 10 is considered a mandatory circuit pack. A second
protection MX circuit pack, MXB found in slot 11 is an optional circuit pack.
Parallel telemetry
Two optional parallel telemetry circuit packs can be equipped in slots 13 and
14 of the Control shelf. These circuit packs offer 64 telemetry inputs (activated
when connected to ground) and 16 form-C relay outputs. The interface is
achieved through one 44-pin D-sub connector for inputs and one 25-pin D-sub
connector for outputs, located on the faceplate of the unit. This unit is used to
monitor and control external equipment.
Orderwire
OPTera Connect DX network elements and TN-64X network elements equip
with MOR Plus circuit packs support Orderwire. For information concerning
the network elements that allow OW functionality, refer to the SDH Orderwire
User Guide, NTCA66DA.


7-1
Optical layer OAM&P 7-

This chapter provides an overview of the optical layer operations
administration, maintenance and provisioning (OAM&P) that are supported
on the Multiwavelength Optical Repeater (MOR) and MOR Plus. The TN-64X
bay supports the MOR and MOR Plus.
Software and provisioning enhancements

The following sections describe the software and provisioning features.
Channel autodiscovery
You can execute this feature on a post amplifier to determine which channels
(wavelength and payload) are detected at the post amplifier input. Channel
autodiscovery reports the recommended provisioning parameters based on the
discovered wavelengths and payloads.
Channel autodiscovery also reports the channels that are locked. For example,
this feature reports channels:
• you tagged to remain provisioned even if they are not discovered
• that are undetected (provisioned wavelengths that the post amplifier cannot
detect)
Channel autodiscovery prompts you to accept or refuse the recommended
provisioning. If you accept the recommended provisioning, this feature
reprovisions the channels. If you refuse, this feature does not modify the
current provisioning parameters.
The system can only execute the channel autodiscovery command at the
post amplifier site of the red or blue band to be discovered. The system does
not execute this command if you issue it from any site other than the
post amplifier site.

7-2 Optical layer OAM&P
Channel provisioning propagation

You can execute this command on a post amplifier to propagate its channel
provisioning parameters to all the amplifiers down the line from the post
amplifier. These parameters include:
• wavelength
• payload
• description
You can apply channel locks to a selected channel destination. These locks
prevent the software from reprovisioning channels that have already been
provisioned but are not part of the channel settings propagated from the
post amplifier. If there are channel locks at a local site you are provisioning, a
collision resolution algorithm can provision the new wavelengths around the
locked wavelengths.
The system can only execute this command at the post amplifier site of the red
or blue band to be provisioned. The system does not execute this command if
you issue it from any site other than the post amplifier site. The system issues
a confirmation of success or failure. An alarm at the local site becomes active
if the provisioning is not completed successfully. This alarm indicates that the
channel provisioning propagation was only partially successful (for example
due to locks or a rare system problem). The alarm clears when the operation is
successful at the local site.
Output power propagation

You can execute this command on a post amplifier to propagate Peak and Total
power control targets derived from the power optimizer tool to each amplifier
down the line. The post amplifier sets a timer and waits for a message to return.
If the timer expires, the message is resent for a maximum of four attempts. If
all attempts are unsuccessful, an alarm becomes active.
You can provision locks at local sites to prevent provisioning of the

recommended power targets at that site. The provisioning values appear, and
the system prompts you to accept or refuse the command. If there is a power
propagation lock on a band at a local site you are provisioning, the system does
not modify the provisioned values at that site.
The system can only execute this command at the post amplifier site of the red
or blue band to be provisioned. The system does not execute this command if
you issue it from any site other than the post amplifier site. The system issues
a confirmation of success or failure.

Optical layer OAM&P 7-3
The following features are available on specific post amplifiers:

• red channel provisioning, optical signal peak, and total powers on the red
post amplifier
• blue channel provisioning, optical signal peak, and total powers on the blue
post amplifier
The commands associated with these features appear at each site, but you can
only execute these commands from the post amplifier site. A single red or blue
band is affected by a propagation or autodiscovery.
Locks prevent automatic provisioning for these features from the

post-amplifier, but locks do not prevent local provisioning. Use locks to
customize wavelength and payload provisioning in the channel autodiscovery
feature. For the channel provisioning and output power propagation features,
the locks allow customized provisioning and some security in a shared system.
For example, if two different network providers administer two neighboring
multiple optical repeaters (MORs), the locks provide each network provider a
mean to prevent remote provisioning on their system.
These features provide the following benefits:

• less susceptibility to errors caused by manual provisioning
• reduced provisioning steps - for example, provisioning eight wavelengths
in a band across five amplifiers now takes two instructions (autodiscover
and propagate) instead of forty channel provisioning operations
• no need to travel to each site for local provisioning
• the system provides you with recommended provisioning parameters
Operational enhancements
The following operational enhancements enable TN-64X to support additional
applications:
• maximum output power control
• increased power optimizer coverage
• 32 lambda power optimization support
For more information on these optical enhancements, refer to MOR Optical
Layer OAM&P, 323-1251-100, of the Optical Networks Applications Library,
NTCA66BA.

7-4 Optical layer OAM&P

8-1
Technical specifications 8-
This chapter provides the technical specifications and requirements for the
Safety specifications
OPTera Connect DX meets the safety requirements of Europe, USA and
Canada.
Laser emission
The laser emissions of OPTera Connect DX meet the safety requirements of
Europe, USA and Canada.
The lasers in OPTera Connect DX are rated in IEC up to Class 3A during

normal operation and during servicing. OPTera Connect DX circuit packs that
contain lasers have the following labels and wordings:
• Identification label: manufacturing data
• Certification label: FDA compliance
• Safety label: FDA Class I wording and IEC Class 3A wording
Table 8-1 on page 8-1 shows the laser output power levels (at the optical
connector on the faceplate of the circuit pack) which determine the regulatory
class of the laser.
Table 8-1
IEC laser emission classes
Laser class 1310 nm lasers 1550 nm lasers
Class 1 6.8 dBm 10 dBm
Class 3A 16.6 dBm 17.0 dBm
Class 3B 27.0 dBm 27.0 dBm
A circuit pack that contains class 1 lasers does not require a laser warning
label. A circuit pack that contains lasers above class 1 requires a laser warning
label on the circuit pack.

8-2 Technical specifications
Class 1 products represent least hazard (none at all), class 3B products present
the greatest hazard.
The IEC class is determined by the maximum output power of the laser in
‘single fault’ conditions. A single fault condition is defined as the failure of
electro-optical circuitry or a break in the optical fiber.
IEC 825 is part of the European self-declaration system for the CE mark.
Site engineering
The OPTera Connect DX bay is a universal bay that meets Telcordia (formerly
known as Bellcore), Network Equipment Building System (NEBS) and ETSI
standards. Where required, the OPTera Connect DX bay is fitted with
extenders to conform to these standards.
Figure 8-1
OPTera Connect DX standard floor plan
DX3944p
Bay
lineup
305mm
(12.00 IN.)
381mm
(15.00 in.) Maintenance aisle
305mm Universal Bay

TYPICAL frame
(12.00 IN.) lineup
305mm
(12.00 IN.) Wiring aisle
381mm
(15.00 in.) Maintenance aisle
Universal V DWDM V Bay

F F
frame O passive bay O lineup
660mm 900mm
TYPICAL TYPICAL
(26.00 in.) (35.43 in.)
Note 1: The DWDM passive bay footprint is 1.5 times the width of the OPTera Connect DX
universal bay footprint.
Note 2: This bay lineup is for NEBS ANSI installations according to GR-63-CORE.
Note 3: Space the anchor bolt holes for adjacent universal bay frames to allow 660mm (26.0 in.)
for ANSI installations and 600mm (23.6 in.) for ETSI installations.

Maximum unshielded twisted pair cable length for Ethernet connection

The maximum unshielded twisted pair (UTP) cable length allowed for
Ethernet connections is 100 m (330 ft).
Maximum cable length for Quad STM-1e cables

The connections on the Quad STM-1e T/R tributary interface circuit pack are
on one connector on the faceplate of the circuit pack. The customer
connections to STM-1e tributaries are made on Type 43 connectors on a
10 meter (33 ft) long cable (NTCC90KA) that connects the STM-1e T/R
tributary interface circuit pack to the digital distribution frame.
There is a 9 dB budget between the Type 43 connectors on NTCC90KA and

the customer’s equipment.
Maximum cable length for HD STM-1e cables

The connections on the HD STM-1e T/R tributary interface circuit pack are on
one connector on the faceplate of the circuit pack. The customer connections
to STM-1e tributaries are made on Type 43 connectors on a coaxial cables of
a coaxial cable assembly that connects to the STM-1e T/R tributary interface
circuit pack to the digital distribution frame. You can order a 10 meter (33 ft)
cable with or without Type 43 connectors or a 3.25 meter (10.7 ft) cable
without Type 43 connectors.
There is a 9 dB budget between the Type 43 connectors on NTCC90 cable and

the customer’s equipment.
Mechanical specifications
Table 8-2 on page 8-3 shows the dimensions of the OPTera Connect DX bay.
Table 8-3 on page 8-4 shows the dimensions of OPTera Connect DX shelves
and other network element hardware components.
Table 8-2
OPTera Connect DX bay specifications
Dimension OPTera Connect DX bay ETSI standard
width 600 mm 600 mm

(23.6 in.) (23.6 in.)
height 2125 mm 2200 mm

(83.7 in.) (84.0 in.)


OPTera Connect DX bay specifications
Dimension OPTera Connect DX bay ETSI standard
depth 300 mm 300 mm

(11.8 in.) (11.8 in.)
weight 300 kg –
(660 lb)
(see Note)
Note: Fully equipped, but not including optical fiber cables or STM-1e cables.
Table 8-3
Shelf and hardware specifications
OPTera Connect DX control shelf (including LCAP)
Width 495 mm (19.5 in.)
Height 500 mm (19.7 in.)
Depth 280 mm (11.0 in.)
Fiber management trays
Width (w/o mounting 495 mm (19.5 in.)

flanges)
Height 88.14 mm (3.47 in.)
Depth 240.5 mm (9.47 in.)
OPTera Connect DX main transport shelf
Width 495 mm (19.5 in.)
Height 367 mm (14.462 in.)
Depth 280 mm (11.0 in.)
Environmental control panel
Width 500 mm (19.68 in.)
Height 74.98 mm (2.95 in.)
Depth 215 mm (8.47 in.)
OPTera Connect DX extension shelf
Width 495 mm (19.5 in.)
Height 367 mm (14.462 in.)
Depth 280 mm (11.0 in.)

Frame equipment
OPTera Connect DX bay
The OPTera Connect DX bay is built using a 2.125 m (6 ft. 11.64 in.)
front-access universal frame. Optionally, frame extenders can be used to
extend the 2.125 m frames to the following heights:
• 2.13 m (7 ft.)
• 2.20 m (7.21 ft.)
• 2.29 m (7.5 ft.)
• 2.44 m (8 ft.)
• 2.60 m (8.53 ft.)
• 2.74 m (9 ft.)
• 3.50 m (11.5 ft.)
A bay frame includes the following:
• anchor bolts
• shear plate
• a grounding strip and
• all the necessary attachment screws
A standard equipped OPTera Connect DX bay is available on a frame with
dimensions of 0.60 m (23.62 in.) wide x 0.298 m (11.73 in.) deep x 2.125 m
(83.66 in.) high.
Floor loading
The OPTera Connect DX network element has a total weight of 300 kg
(652 lb) completely configured. With a 300 mm (11.8 in.) deep frame, the
required floor area is 0.65 m2 (7.04 ft2). The total floor load is 462 kg/m2
(93 lb/ft2).
Telcordia (formerly known as Bellcore) standard GR-63-CORE Issue 1,

October 1995 indicates a maximum total floor load for the area of 748.1 kg/m2
(150.6 lb/ft2). This specification includes overhead cables, light fixtures and
transient loads supported by the equipment frame.
Circuit pack characteristics

Table 8-4 on page 8-6 lists the weights, and estimates of the normal power
dissipation and maximum power dissipation for each OPTera Connect DX
circuit pack. The power dissipation values are taken at the nominal battery
voltage of –48 V.

Table 8-4
Circuit pack power estimates
Weight Power dissipation

Circuit pack kg (lbs) (Watts)
Normal Maximum
DX65 switch module (NTCA26AA) 8.1 (17.9) 145 205
DX100 switch module (NTCA26BA) 8.1 (17.9) 160 206
DX140 switch module (NTCA26CA) 8.1 (17.9) 160 206
STM-64 10G T/R (NTCA06) 4.54 (10.0) 125
STM-64 10G T/R Regular TriFEC (NTCF06) 4.54 (10.0) 115
STM-64 short reach 10G T/R (NTWR06AB) 4.54 (10.0) 123
STM-64 long reach 10G T/R (NTWR06BA) 4.54 (10.0) 117
STM-64 long reach 10G T/R (NTWR06BB) 4.54 (10.0) 117
STM-64 intermediate reach 10G T/R 4.54 (10.0) 117

(NTWR06CA)
STM-16 T/R tributary (NTCA30) 3.6 (7.9) 65
STM-16 T/R tributary (NTCA30AN) 3.6 (7.9) 65
STM-16 DWDM T/R tributary (NTCA30) 3.6 (7.9) 50
Dual STM-16 T/R tributary (NTWR30) 3.6 (7.9) 65 90
Quad STM-16 T/R tributary (NTWR31) 3.3 (7.3) 42 60
Quad STM-1e T/R tributary (NTCE37) 3.2 (7.0) 42 54
Quad STM-1 T/R tributary (NTCA33) 3.2 (7.0) 42 52
HD STM-1o T/R tributary (NTCA35) 3.1 (6.8) 37
HD STM-1e T/R tributary (NTCE35) 3.85 (8.5) 28 31
Quad STM-4 T/R tributary (NTCA36) 3.2 (7.0) 42 48
Dual Gigabit Ethernet (GE) interface (SX) 3.2 (7.0) 27

tributary (NTCA90EA)
Dual Gigabit Ethernet (GE) interface (LX) 3.2 (7.0) 27

tributary (NTCA90CA)
Dual Gigabit Ethernet (GE) interface (ZX) 3.2 (7.0) 27

tributary (NTCA90GA)
OPC storage (NTCA51) 2.5 (5.6) 13
OPC controller (NTCA50) 0.8 (1.8) 11


Circuit pack power estimates
Weight Power dissipation

Circuit pack kg (lbs) (Watts)
Normal Maximum
OPC interface (NTCA52) 0.7 (1.5) 3
OPC removable media (NTCA53) n/a 1 2
Shelf controller, 32 Mbyte (NTCA41) 0.7 (1.5) 10
Maintenance interface (NTCA42) 0.6 (1.4) 7
Message exchange (NTCA48) 0.7 (1.5) 8
Parallel telemetry (NTCA45) 0.6 (1.3) 2
Orderwire (NTCA47) 0.7 (1.5) 7 10
External synchronization interface (NTCE44) 1.5 (3.3) 10
Breaker/filter (NTCA40BA) 1.7 (3.8) 5
Fan module (NTCA85EA) 0.5 (1.1) 50
Control shelf filler card 1.1 (2.5) n/a
Main shelf filler card 1.1(2.5) n/a
Thermal loading
The OPTera Connect DX bay uses forced air cooling and is free standing. The
Telcordia (formerly known as Bellcore) standard GR-63-CORE Issue 1,
October 1995 heat release objective is 1.950 kW/m2 (181.2 W/ft2).
Calculation of the bay heat dissipation is based on a floor area defined by
Telcordia (0.59 m2 (6.39 ft2)).
The real OPTera Connect DX bay heat dissipation depends on the

configuration. Table 8-5 on page 8-7 shows the maximum thermal loading for
a completely equipped OPTera Connect DX network element. These figures
are based on a floor area of 0.65 m2 (7.04 ft2), as defined by Telcordia.
Table 8-5
Maximum thermal loading
Maximum power dissipation Thermal density

(fully equipped)
3000 W 4615 W/m2 (413 W/ft2)

Power requirements
The following specifications cover all the requirements related to power for an
Input power specifications

OPTera Connect DX meets the input power requirements specified in the
relevant sections of the documents listed in Table 8-6 on page 8-8.
Table 8-6
Input power specifications
Authority Document Issue
ANSI/T1E1 ANSI T1.315-199x draft
British Telecom BTR2511 3 June 1985
Bell Canada DS8171 2
ETSI prETS 300 132 December 1990
DBP Telekom FTZ19 Pfl 1 March 1985
AusTel TP00344B, Spec 1550 1
Telcordia (formerly known TR-TSY-001003 1 May 1990

as Bellcore)
Telcordia (formerly known TR-NWT-000499 Iss4, Rev1, April 1992

as Bellcore) GR-499-CORE
Table 8-7 on page 8-8 shows the input voltage specifications.
Table 8-7
Battery voltage requirements measured at the bay
Requirement Specification
Range −40 V dc to −60 V dc
Battery step change during end wall switching 5 V step at ≥ 5 V/ms

Voltage transients
OPTera Connect DX operates properly when the input voltage transients
shown in Table 8-8 on page 8-9 are applied.
Table 8-8
Input voltage transients
Voltage Duration Specification
75 V 10 ms ANSI T1.315-199x
75 V 1 second FTZ 19 Pfl 1
100 V 2 ms BTR2511
100 V 22 µF capacitance TP00344B
150 V 0.1/0.3 ms FTZ 19 Pfl 1
200 V 100 µs ETS 300 132
300 V 700 µs BTR2511
1 kV 0.22 µF capacitance TP00344B
2.5 kV 10/700 µs ETS 300 132
5 V2/ms not applicable DS 8171 (Bell Canada)
Conducted noise on DC power leads

OPTera Connect DX meets the conducted noise emission and immunity levels
given in the documents listed in Table 8-9 on page 8-9.
Table 8-9
Conducted noise on DC power leads
ANSI/T1E1 ANSI T1.315-199x draft
British Telecom BTR2511 3
Bell Canada DS8171 2
ETSI prETS 300 132 Draft
Telcordia (formerly known GR-1089-CORE 1 October 1991

as Bellcore)
AusTel TP00344B,Spec 1550 1
Telcordia (formerly known TR-NWT-000499 Iss4, Rev1, April 1992

as Bellcore) GR-499-CORE

Safety requirements for power converters

OPTera Connect DX power converters meet the safety requirements given in
the documents listed in Table 8-10 on page 8-10.
Table 8-10
Power converter safety specifications
Authority Document Applicable products
AusTel TS001 customer premises equipment

(CPE)
BSI BS6301/1989 telecom products
CSA CSA234 power supplies
EN EN41003 telecom equipment
EN EN60950 ITE
IEC IEC950 ITE
UL UL1459-iss.2 telecom equipment
UL UL1950 data processing
Power distribution
The OPTera Connect DX network element is powered by redundant power
feeds, namely A and B feeds. A failure of one of the power feeds has no effect
on the system. Two breaker/filter modules (A and B) provide power for the
OPTera Connect DX shelves.
The A side and the B side can have separate power supplies. See Table 8-11 on
page 8-10 for the operating voltage range.
Table 8-11
Acceptable operating voltage range
Measured voltage across Acceptable operating voltage range
A (–48) and A (RET) –40 V dc to –60 V dc
B (–48) and B (RET) –40 V dc to –60 V dc
A (–48) and B (–48) 0 ± 5 V dc
A (RET) and B (RET) 0 ± 0.1 V dc

The bay operating voltage range is specified at –40 V dc to –60 V dc, the
nominal voltage is –48 V dc.
If the input voltage falls to –38 V dc, the network element reports a fault
condition and it raises a low shelf voltage alarm. The low shelf voltage alarm
clears when the shelf voltage increases to above approximately –41.5 V dc.
If the input voltage falls above –41.5 V dc and stays on or below –40 V dc, the
network element operates normally but you cannot perform provisioning
operations, otherwise you will lose all the provisioned data entered. As the
voltage rises and crosses the threshold of –41.5 V dc an automatic restart of the
shelf controller (SC) occurs. The restart of the SC causes a temporary loss of
association with the affected network element during the time of recovery.
This loss of association remains for one minute to one and a half minute.
Power installation requirements
You can use either six cables or two cables to connect the power from the
battery distribution fuse bay (BDFB) to the OPTera Connect DX network
element:
• Six power feeds (see Figure 8-2 on page 8-13)
— you can connect six power cables to the front power termination block
— the power cables can enter the bay from above, or through the floor
— for each power cable of the OPTera Connect DX network element,
Nortel recommends a 50 amperes circuit breaker to meet all types of
configurations and future evolution
Note 1: You can lower the rating of the circuit breakers according to the
system configurations and capacity described in Table 8-12 on page 8-11.
Note 2: Nortel recommends that you size the cables according to the
maximum power capabilities of the bay (i.e. 6X50).
Note 3: You must upgrade the circuit breakers of the system if the switch
module circuit packs are upgraded.
.
Table 8-12
Six power feed cables circuit breakers
Switch modules Circuit breakers required for guaranteed minimum

voltage level of –40 V dc measured at the bay
DX65 40 A circuit breaker
• Two power feeds (see Figure 8-3 on page 8-14)

— you can connect two power cables to the front power termination block

— the two power cables can enter the bay from above. You cannot use the
through-floor option with two power cables
— for each power cable of the OPTera Connect DX network element,
Nortel recommends a 100 amperes circuit breaker to meet all types of
configurations and future evolution
Note 1: You can lower the rating of the circuit breakers according to the
system configurations and capacity described in Table 8-13 on page 8-12.
Note 2: Nortel recommends that you size the cables according to the
maximum power capabilities of the bay (i.e. 2X100).
Note 3: You must upgrade the circuit breakers of the system if the switch
module circuit packs are upgraded.
Table 8-13
Two power feed cables circuit breakers
Switch modules Circuit breakers required for a guaranteed minimum

voltage level measured at the bay
–40 V –42 V
DX65 60 A circuit breaker 60 A circuit breaker

Figure 8-2
Power feed assignments for six power feeds with front power block (front view shown)
DX0394
A1 feed (-48 V) A1 return (0 V)

B1 feed (-48 V) B1 return (0 V)
2-position bus bars
Power termination block (front view) showing terminal designations for six feeds
Power termination block (front view) showing feed cable routing for six feeds

Figure 8-3
Jumper busbars on the two power feed front power termination block (front view shown)
DX3173
Step 1: Removing the 2-position bus bars
Power termination block

(front view)
2-position bus bars
Step 2: Fitting the 3-position bus bars on the power feed terminals

3-position bus bars (front view)
3-position bus bar B

(insulator up so that it
is visible)
Step 3: Fitting the 6-position bus bar on the return terminals
3-position bus bar A

(insulator down facing
insulator on bus bar B)
3-position bus bars (front view)
6-position bus bar

Grounding and isolation

OPTera Connect DX is suitable for installation in the system-level and
building-level grounding configurations specified in the documents listed in
Table 8-14.
Table 8-14
Grounding specifications
AusTel TPH01115(U) –
ITU-TS Rec.K.27 1991
ETSI prETS 300 253 October 1992
Telcordia (formerly known TR-NWT-000295 2 July 1992

as Bellcore)
REA TEC Section 810 6 September 1983
NFPA NFPA 70 1993
CSA CSA22.1 1990
OPTera Connect DX uses an integrated frame and logic grounding system. An

example of this is the point-of-use power supply (PUPS) of each circuit pack.
The −4.5 V dc and −12 V dc logic ground from each PUPS connects to the
frame of the shelf through the backplane. The battery return is separate from
the frame ground as described in Telcordia (formerly known as Bellcore)
TR-NWT-000063, Issue 5, September 1993.
The shields of the Quad and HD STM-1e coaxial cables terminate on the shelf
ground. The ground pins of RS-232, parallel telemetry, and Ethernet cables
connect to the shelf ground.
Environmental specifications
The following sections describe the environmental specifications that OPTera
Connect DX Release 6.0 equipment meets.
Operational environment
OPTera Connect DX meets the environmental requirements for the United
Kingdom, Europe, Mexico, Brazil, Canada, USA, and Taiwan:
• normal operating temperature
• short-term operating temperature
• operating humidity

• short-term operating humidity

• operational altitude
OPTera Connect DX meets the earthquake, resonance search, and operational
vibration requirements of USA and Europe.
Table 8-15 on page 8-16 outlines the operating environment envelope.

Table 8-15
Attribute Condition Test method and specifications
Normal operating 5 °C to 40 °C, USA: Telcordia (formerly known as Bellcore)

temperature (see Note 5% to 85% relative humidity NEBS GR-63-CORE
1) Bell Canada: DS 8161
Short term operating –5 °C to 50 °C Brazil: 240-600-702, 240-600-703
temperature (see Note 5% to 90% relative humidity Europe: ETSI 300 019-1-3:1992
1 and Note 2) but not greater than Mexico: E220
0.024 kg water/kg of dry air
Taiwan: Specification for Toll Switching System
Normal operating 5% to 85% relative humidity British Telecom: BT RC 5000P
humidity (see Note 1)
Short term operating 5% to 90% relative humidity

humidity (see Note 1 but not greater than
and Note 2) 0.024 kg water/kg dry air
Temperature cycling –5 °C to 50 °C Brazil: 240-600-702, 240-600-703

at 30 °C per hour USA: Telcordia (formerly known as Bellcore)
NEBS GR-63-CORE
Europe: ETSI 300 019-1-3:1992 Class 3.1
Mexico: E220
Operational altitude 4000 m above sea level Brazil: 240-600-702, 240-600-703

USA: Telcordia (formerly known as Bellcore)
NEBS GR-63-CORE
Acoustic noise 60 dBA USA: Telcordia (formerly known as Bellcore)

NEBS GR-63-CORE
Acoustic noise contour of constant UK: British Telecom RC 5000P; BS 4198 1967
loudness, index 1.99
Airborne contaminants USA: Telcordia (formerly known as Bellcore)

NEBS GR-63-CORE
Thermal loading 1.94 kW/m2 or USA: Telcordia (formerly known as Bellcore)

(per office floorspace) 180 W/ft2 NEBS GR-63-CORE


Earthquake/seismic Zone 4 USA: Telcordia (formerly known as Bellcore)

NEBS GR-63-CORE
Taiwan: Specification for Toll Switching System
Resonance search > 6.5 Hz Europe: IEC 68-2-6 test Fc

NEBS GR-63-CORE
Operational vibration - Europe: ETSI 300 019-1-3: 1992 Class 3.1;

IEC 68-2-6 test Fc
NEBS GR-63-CORE
Microphonic shock 100 g point impulse as 011-0.2-1R46 Microphonic Tool

calibrated using the BNR
transmission shock tool
Note 1: This specification is fully compliant with Telecordia (formerly Bellcore) GR-63-CORE, Issue 1,
October 1995.
Note 2: The short term is no more than 96 consecutive hours and a total of no more than 15 days in a
year.
Storage and transportation environment

OPTera Connect DX meets the storage and transportation requirements of
Brazil, Europe and USA.
Table 8-16 on page 8-17 outlines the storage and transportation environment
envelope.
Table 8-16
Temperature –50°C to 70°C, 72 hour Brazil: 240-600-702, 240-600-703

duration at each temperature USA: Telcordia (formerly known as Bellcore)
extreme. NEBS GR-63-CORE
Humidity up to 98% R.H. Europe: ETSI 300 019:1992 Class 1.2/2.3
(non-condensing) or 4.0 kPa
water vapor pressure
(whichever is less)


High temperature 25°C to 70°C in less than 5 USA: Telcordia (formerly known as Bellcore)
thermal shock minutes NEBS GR-63-CORE
Low temperature 25°C to –40°C in less than 5

thermal shock minutes
High humidity cyclic –1°C to 28°C at 95% relative USA: Telcordia (formerly known as Bellcore)
test humidity NEBS GR-63-CORE
Shipping vibration - Europe: ETSI 300 019-1-2:1992 Class 1.2/2.3,

IEC 68-2-6 test Fc
NEBS GR-63-CORE
Installation drop - Europe: IEC 68-2-6 test Fc

(systems) USA: Telcordia (formerly known as Bellcore)
NEBS GR-63-CORE
Handling drop - Europe: ISO 2244

(palletized)
Handling drop - Europe: IEC 68-2-6 test Fc

(packaged) USA: Telcordia (formerly known as Bellcore)
NEBS GR-63-CORE
Servicing drop (topple) - Europe: IEC 68-2-31 test Ec
Servicing drop - Europe: IEC 68-2-6 test Fc

(free fall) USA: Telcordia (formerly known as Bellcore)
NEBS GR-63-CORE Issue 1 Oct. 1995
Shock fragility - Europe: IEC 68-2-27 test Ea
Bounce-transportation - Europe: IEC 68-2-55
Air shipment horizontal -
Altitude
The OPTera Connect DX network element operates up to 4000 m (13,000 ft)
above sea level.
For altitudes above 1800 m (5905 ft), you must reduce the operating
temperature range. Reduce the operating temperature range by 2°C (3.6 °F) for
every 305 m (1000 ft) up to 4000 m (13,000 ft).

Atmospheric Dust
The OPTera Connect DX shelves do not require any air filters. The enclosed
construction of circuit packs in the main transport shelf permits forced air to
cool the system. Air filters and their related maintenance are not necessary.
Particles in the air do not collect on the electronic components of the circuit
packs.
The equipment remains in operation and subject to the requirements of

Telcordia (formerly known as Bellcore) TR-NWT-000063, Issue 5, September
1993, Section 4.6, ‘Airborne Contaminants’.
Mechanical shock and vibration

The OPTera Connect DX network element meets mechanical strength
requirements for normal transportation, service, shock strength, working
vibrations and earthquakes. The tests in the following tables are acceptable to
check these requirements.
Shock
The equipment meets the following standards (see Table 8-17 on page 8-19).
• Telcordia (formerly known as Bellcore) GR-63-CORE, Issue 1, October
1995 in sections 4.3.1.2 and 4.3.2. The test methods are specified in
sections 5.3.1 and 5.3.2
• International Electrotechnical Commission (IEC) Draft 68-2-55 Transport
Bounce and IEC 68-2-27 Shock Fragility
Table 8-17
Shock specifications
Condition Specification
In a shipment package Drop height 609 mm (24 in.) or 762 mm (30 in.)
(depends on weight)
Out of package Drop height 76 mm (3 in.) or 102 mm (4 in.)

(at installation) (depends on weight)
In a shipment package Drop heights:

(each circuit pack) 609 mm, less than 10 kg
762 mm, 10 kg to 25 kg
In a shipment package Drop height 150 mm

(system level)
Out of package Drop height:

(each circuit pack) 100 mm, less than 10 kg
75 mm, 10 kg to 25 kg
Out of package shock fragility 30 g, 18 ms, ½ sine

Vibration
The equipment meets Telcordia (formerly known as Bellcore)
TR-NWT-000063, Issue 5, September 1993, specification in sections 4.4 and
5.6.4 (see Table 8-18 on page 8-20).
Table 8-18
Vibration specifications
Working environment 0.1 g from 5 Hz to 100 Hz at 0.1 oct/min
Not working environment (shipping) 5 Hz to 50 Hz at 0,5 g and 0.1 oct/min and

50 Hz to 500 Hz at 3 g and 0.25 oct/min
Transportation bounce
Transportation bounce is measured by tests on a truck bed simulator. The
OPTera Connect DX meets test method IEC Draft 68-2-55.
Earthquake
An OPTera Connect DX network element remains in operation for floor
response spectra that simulate Zone 4 earthquake loading. The OPTera
Connect DX bay meets Telcordia (formerly known as Bellcore)
GR-63-CORE, Issue 1, October 1995 section 4.4, Zone 4 waveform.
Electromagnetic compatibility
This section covers the electromagnetic compatibility (EMC) of the OPTera
Emissions
Electromagnetic interference (EMI) emission requirements minimize the
interference of EMI from the OPTera Connect DX system to other electronic
devices.
In its maximum worst-case acceptable configuration, the OPTera Connect DX

system meets class A limits for the following radiated emission requirements:
• FCC Part 15 Subpart B
• EN55022
• Telcordia (formerly known as Bellcore) GR-1089-CORE
• Bell Canada TAD 8465
• ICES-003
• EN 300 386-2

Conducted emission requirements refer to power and signal cables. In its

maximum worst-case acceptable configuration, the OPTera Connect DX meets
class A limits for the following conducted emission requirements:
(formerly TR-NWT-000499, Issue 4)
• Bell Canada DS 8171
• EN 300 386-2
• ETSI 300 132-2
Susceptibility
Radio frequency immunity (RFI) requirements ensure a high degree of
robustness to electromagnetic disturbances. These disturbances can come
from other electronic devices and radio-wave transmissions.
The OPTera Connect DX bay meets the following radiated immunity

requirements:
• EN 300 386-2
• EN 50082-1
The OPTera Connect DX bay meets the following conducted immunity
requirements:
• Telcordia (formerly known as Bellcore) GR-499-CORE (formerly
TR-NWT-000499, Issue 4)
• EN 300 386-2
• EN 50082-1
• ETSI 300 132-2
Electrostatic discharge
The electrostatic discharge (ESD) requirements in this section apply up to the
following levels:
• 15 kV (air discharge, direct)
• 8 kV (contact discharge, direct and indirect)

The OPTera Connect DX bay meets the following specifications at these levels
with no errors or malfunction:
• EN 300 386-2
• EN 1000-4-2 (formerly IEC 801-2)
Electrical fast transient
The OPTera Connect DX bay meets the specifications in this section up to
Level 3 (2 kV power, 1 kV signal). No errors or malfunctions occur at this
level. The system automatically recovers, without damage, up to Level 4 (4 kV
power, 2 kV signal).
The OPTera Connect DX bay meets the following specifications:

• EN 300 386-2
• EN 1000-4-4 (formerly IEC 801-4)
The above specifications summarize most of the global electromagnetic
compatibility (EMC) requirements. With compliance to the above
specifications, robustness of OPTera Connect DX to RF noise and ESD is
maximized and risk of OPTera Connect DX causing RF interference to other
sensitive receivers is minimized.
Network synchronization
OPTera Connect DX complies with the network synchronization requirements
in TA-NPL-000436, Digital Network Plan, Issue 1, November 1986,
Section 3.3.
SDH equipment derives many of its basic attributes from synchronous

operation. When a network element is synchronized, the shelf is timed from a
stable clock and all subtending tributaries and transport signals generated by
the network element are synchronized to its timing source.

Stratum clocks are stable timing reference signals that are graded according to
their accuracy. Table 8-19 on page 8-23 shows the accuracy requirements of
the stratum clock levels.
Table 8-19
Required standard clock stratum
Stratum Minimum accuracy Minimum holdover stability
1 +1.0 x 10-11 Not applicable

2 +1.6 x 10-8 1 x 10-10 per day
3 +4.6 parts per million +0.37 ppm during first 24 hours
(ppm)
4 +32 ppm Not required
External synchronization interface internal clock specifications

The external synchronization interface (ESI) meets stratum 3 requirements and
is completely compatible with building-integrated timing supply (BITS) clock
applications. Table 8-20 on page 8-23 provides the ESI specifications.
Table 8-20
ESI specifications
Long-term stability ±4.6 ppm
Holdover stability ±0.37 ppm (constant temperature for the range

of 0 °C to +50 °C).
Minimum pull-in range ±4.6 ppm
DS1 timing interface specifications

The ESI DS1 timing interfaces are compliant with the DSX-1 specification
defined in ANSI TI.102-1987 and GR-253-CORE.
The ESI timing reference input accepts framed DS1 signals. The timing
reference output provides a framed all 1s or unframed all 1s DS1 alarm
indication signal (AIS). Table 8-21 on page 8-24 provides the ESI interconnect
characteristics. Table 8-22 on page 8-24 provides the range of DS1 cable
length for different line build-out (LBO) values.

Table 8-21
ESI interconnect characteristics
Parameter Value
Line code B8ZS or Alternate Mark Inversion (AMI)
Frame format Superframe (SF) or

Extended Superframe (ESF)
Test load 100 ohms ± 5%, resistive
DS1 output AIS line rate 1.544 Mbit/s ± 32 ppm
Table 8-22
DS1 cable lengths for different LBO settings
LBO value DS1 ABAM (608) cable AT&T 1249C DS1 cable
Short 0 to 46 m (0 to 150 ft) 0 m to 30 m (0 ft to 100 ft)
Medium 46 to 137 m (150 to 450 ft) 30 m to 76 m (100 ft to 250 ft)
Long 137 to 200 m (450 to 655 ft) 76 m to 137 m (250 ft to 450 ft)

2 MHz timing interface specifications

The ESI timing reference input accepts 2 MHz signals and the timing
reference output provides a 2 MHz signal according to ITU-T
recommendations G.703 and G.813. Table 8-23 on page 8-25 gives the 2 MHz
ESI interconnect characteristics.
Table 8-23
2 MHz ESI interconnect characteristics
Parameter Value
Impedance 75 Ω
Termination types coaxial connector
Rate 2.048 MHz ± 4.6 ppm
Input return loss ≥15 dB at 2048 kHz
Cable loss to input 0 dB to 6 dB at 2048 kHz
Output voltage (peak) 75 Ω: 0.75 V (minimum), 1.5 V (maximum)

120 Ω: 1.0 V (minimum), 1.9 V (maximum)
2 Mbit/s timing interface specifications

The ESI timing reference input accepts 2 Mbit/s signals and the timing
reference output provides a 2 Mbit/s signal according to ITU-T
recommendations G.701, G.703, G.704, G.706, G.732, G.775, G.783, G.784,
G.810, G.813, G.823 and G.825. Table 8-24 on page 8-25 gives the 2 Mbit/s ESI
interconnect characteristics.
Table 8-24
2 Mbit/s ESI interconnect characteristics
Parameter Value
Line code HDB3 or Alternate Mark Inversion (AMI)
Impedance 75 Ω or 120 Ω
Termination types coaxial connector (75 Ω) or wire wrap (120 Ω)
Rate 2.048 Mbit/s ± 4.6 ppm
Input return loss ≥18 dB
Cable loss to input 0 dB to 6 dB at 1024 kHz
Output voltage (nominal) 75 Ω: 3.0 V (mark), 0 V± 0.3 V (space)

120 Ω: 2.37 V (mark), 0 V± 0.237 V (space)

Building-integrated timing supply

The building-integrated timing supply (BITS) concept stipulates that all digital
equipment in a structure must synchronize to the same master clock. This
master clock (the BITS) is the most accurate and stable clock in the building.
The BITS provides 2 Mbit/s, 2 MHz or DS1-level synchronization for the
building.
A reference to stratum-1 drives the BITS. This reference can come from the
following sources:
• a signal derived from a SONET or SDH signal, for example, the output of
an external synchronization interface (ESI)
• an external stratum clock
Advantages of the BITS concept
The advantages of implementing the BITS concept are the following:
Performance: The indication of a master timing supply for each building

enhances the reliability of the timing distribution. The BITS minimizes the
number of synchronization links that enter a central office because the BITS
receives timing reference from outside the office.
Utilization of resources: Use of a BITS increases the quantity of acceptable

2 Mbit/s, 2 MHz or DS1-level interconnection. Use of a BITS allows services
within the office to share resources.
Operations: The BITS is location-dependent, not service-dependent. Records

for provisioning and maintenance purposes are easier to maintain in the event
of the introduction of new digital services.
Network element synchronization modes

Depending on the timing source, different modes of synchronization are
supported on the network element (see Table 8-25 on page 8-29).
OPTera Connect DX network elements use the following synchronization

modes (see Figure 8-4 on page 8-28).
External timing
External timing mode uses a timing source that is independent of any internal
clock or received optical or tributary signal. An external timing source is
typically a highly accurate stratum clock.
On the OPTera Connect DX and TN-64X network elements, external timing is

provided by a BITS. The external source is 1.544 Mbit/s (DS1), 2 MHz or
2 Mbit/s. The BITS reference input connections are located at the top of the
bay on the synchronization alarm telemetry terminations (SATT). The SATT
terminations are wire wrap pins (DS1 or 2 Mbit/s) or coaxial connectors
(2 MHz or 2 Mbit/s).

Each BITS input (BITSA and BITSB) can accept a 2 MHz signal
(NTCE44BA or NTCE44AA), 2 Mbit/s (NTCE44AA) or DS1 signal with
extended superframe or superframe format, with a line code of B8ZS or
alternate mark inversion (AMI) (NTCA44AA).
Line timing
Line timing is a method of deriving timing from a received transport optical
signal. The derived signal is used to synchronize outgoing optical signals in
both directions, and all synchronous tributary signals terminated by the ADM.
The quality of synchronization depends on the stability of the optical signal
received from the remote end. The timing reference must be traceable to an
external source, such as a BITS.
Through timing
Through timing is used only on regenerators, where the input optical signal is
used to synchronize the output optical signal in the same direction. The
synchronization of signals travelling in opposite directions through a
regenerator is independent, therefore a timing source is required for each
direction. Since external synchronization is not required in regenerators, ESI
circuit packs are not present.

Figure 8-4
Flow of synchronization timing signals for different reference sources
DX1184
BITS
Stratum 3
or better
Network Network element

element
(a) External timing (b) Line timing
Network element NE
Clock
(c) Through timing (d) Freerun timing
Legend:
= Transport traffic flow
= Tributary traffic flow

= Synchronization timing
= External synchronization reference

Table 8-25
Timing modes of operation
Shelf clock ESI target Timing Timing mode Accuracy Application

source filter mode reference
ESI Normal BITSA or External timing As precise as DX_HUB

BITSB the local BITS network
element
STM-64 G0, Line timing As precise as
STM-64 G9, the received
STM-64 G10, signal
STM-64 G11,
STM-64 G12,
STM-64 G17,
STM-64 G18,
STM-64 G19
All timing Holdover +0.37 ppm

references are relative to the
failed last reference
for first 24 hrs.,
drifting no
worse than
+4.6 ppm
(stratum-3)
after the 24
hour period
Holdover Internal ESI Holdover +0.37 ppm

oscillator relative to the
last reference
for first 24 hrs
(stratum-3
holdover
stability)
Freerun Internal ESI Freerun +4.6 ppm

oscillator (stratum-3
accuracy)
Through timed Not applicable Received Through timed As precise as Regenerator

(no ESI signal to be the received
required) regenerated signal
Synchronization status messaging

Synchronization status messages are defined as bits 5 to 8 of the SDH section
overhead S1 byte. Synchronization status messaging (SSM) provides
automatic switching to the most appropriate timing reference based on
reference quality and priority. SSM provides timing intelligence and reliability
to network synchronization.

Table 8-26 on page 8-30 defines the synchronization messages in accordance

with the Technical Report 33, Telcordia (formerly known as Bellcore)
GR-253-CORE, ETSI G.781ETSI ETS 300-417.
Table 8-26
Synchronization status message definition
Quality level description Acronym Quality code Quality level
(Note 1) (Note 2)
STRATUM 1 Traceable ST1 1 0
G.811 Traceable to a primary PRC 2 1

reference clock
Synchronized - Traceability STU 0 2

Unknown
G.812T Traceable to a transit SSUT 4 5

synchronization supply unit (SSU)
G.812L Traceable to a local SSU SSUL 8 8
G.813 Traceable to an SDH SEC 11 11

equipment clock
SONET Minimum Clock - (± 20 ppm SMC 12 12

clock)
Reserved for network RES 14 user defined

synchronization use
Do not use for synchronization DUS 15 15
Note 1: Quality codes (QCs) 3, 6, 9, and 13 are not used and are invalid.
Note 2: The quality level defines the priority assigned to each quality code. The
quality levels not listed in this table are not currently used.
ESI modes of operation

The following ESI modes of operation are defined:
• freerun
• holdover
• acquire (not user-provisionable)
• fast-acquire (not user-provisionable)
• normal

Freerun mode
In freerun mode, the ESI provides a stratum 3 free-running clock timing signal
(at an accuracy of + 4.6 ppm). Because the clock on the shelf is a stratum 3.5
clock, with an accuracy of ± 20 ppm, the ESI clock improves performance
even in freerun mode.
Holdover mode
If no valid timing reference input is available, the ESI enters holdover mode.
In holdover mode, the ESI output timing signal is operated at a fixed frequency
based on the last known frequency reference.
Acquire mode
Acquire mode is used to bring the output timing signal of the ESI into
frequency alignment with the selected timing reference input. Large changes
in frequency are made until the frequency alignment is within a certain range,
then fast-acquire mode is entered. Acquire mode is not user-provisionable.
Fast-acquire mode
In fast-acquire mode, the ESI makes small modifications in frequency to bring
its clock into close alignment with the selected timing reference input. Acquire
mode is not user-provisionable.
Normal mode
In normal mode, the internal clock of the ESI is aligned with the reference
signal. Frequency alignment is checked continuously and the ESI enters fast
mode to realign (if necessary).
Timing generation
The timing generation references for the network element is N:1 protected
(where N is 6). The best timing reference can be automatically or manually
selected from a pool of six sources.
For an OPTera Connect DX network element, the six timing generation

references sources are:
• BITSA
• BITSB
• any four of the following eight sources:
— STM-64 G0
— STM-64 G9
— STM-64 G10
— STM-64 G11
— STM-64 G12
— STM-64 G17
— STM-64 G18

— STM-64 G19
For an TN-64X network element, the six sources are:
• BITSA
• BITSB
• STM-64 G1
• STM-64 G2
• STM-64 G3
• STM-64 G4
BITSA and BITSB provide external timing. The STM-64 references provide
line timing functionality.
Timing distribution
Timing distribution (TD) synchronizes a large number of systems within a
single location to a single timing reference signal. Each ESI circuit pack uses
the recovered optical signal to derive a timing distribution (TD) reference
output.
The TD output generated by the 2 MHz ESI is a 2 MHz signal. The TD output
generated by the 2 Mbit/s ESI is a 2 Mbit/s signal. The TD output generated
by the 1.5 Mbit/s ESI is a framed all-1s DS1 with:
• superframe (SF) or extended superframe (ESF) frame format (default)
• short (default), medium, or long line buildout (LBO)
The DS1, 2 MHz or 2 Mbit/s signal is then used by the ESI to synchronize the
local BITS, which in turn synchronizes all the other network elements in the
building. The two TD outputs generated (one from each ESI circuit pack) are
named G1OUT and G2OUT. If the system cannot select a reference source for
the 2 MHz or 2 Mbit/s ESI, the timing reference output for that TD group is
disabled. If the system cannot select a reference source for the 1.5 Mbit/s ESI,
the timing reference output for that TD group returns to an unframed all-1s
DS1. The all-1s DS1 signal is the alarm indication signal (AIS).
Note: For the 1.5 Mbit/s ESI, each TD output is buffered to provide four
connections on the SATT (i.e. four G1OUT signals and four G2OUT
signals). For the 2 MHz or 2 Mbit/s ESI, each TD output is buffered to
provide a single connection on the SATT (i.e. one G1OUT signal and one
G2OUT signal).

Parallel telemetry output relay

The output relays of the PT circuit pack are form-C. The relay contacts are
rated at 120 V ac (110 V dc) at 1 A. Each output is a three-signal set. The
parallel telemetry circuit pack accesses the eight telemetry outputs through a
25-pin D-subminiature connector located on the circuit pack faceplate. The
relay that supplies the output has:
• a common (COM) connection
• a normally open (NO) contact
• a normally closed (NC) contact
OPC definition
The operations controller (OPC) provides operations, administration,
maintenance and provisioning (OAM&P) functionality in a network. The
functions of the OPC include system administration, network surveillance and
software management.
The span of control (SOC) of an OPC is the set of network elements that are
directly controlled or monitored by a single OPC (primary OPC only) or a pair
of OPCs (primary OPC and backup OPC). Normally, a span of control is
monitored by a pair of OPCs.
Partitioned OPC
The partitioned OPC consists of three separate OPC circuit packs (OPC
storage, OPC controller, and OPC interface) and an OPC removable media.
The OPC controller circuit pack installed in the control shelf communicates
with the maintenance interface circuit pack, the OPC storage circuit pack and
the OPC interface circuit pack, as seen in Figure 8-5 on page 8-34.

Figure 8-5
Communication between the partitioned OPC and other circuit packs in the network element
F3239-192_R40
MI
OPC-C SC MX G1 MX G2
Circuit Circuit Circuit

OPC-S OPC-I pack 1 pack x pack y
Circuit packs equipped with a processor (TCS)
Legend:
MI = Maintenance Interface module
MX = Message eXchange module
OPC-C = Operations Controller Control module
OPC-I = Operations Controller Input/Output module
OPC-S = Operations Controller Storage module
SC = Shelf Controller module
Communication between the OPC and other network elements through

optical fiber
The OPC controller circuit pack exchanges OAM&P messages with network
elements through the SDH regenerator section DCC (RS DCC) and multiplex
section DCC (MS DCC) embedded in the SDH overhead of STM-64 optical
traffic (Figure 8-6).
At the receiving network element, the STM-64 optical signal is received by the
STM-64 T/R or the STM-64 receive circuit pack and SDH RS DCC and MS
DCC is terminated. The SDH RS DCC and MS DCC then travels over
GraceLAN to the message exchange circuit pack, then through the
multi-master serial bus (MMSB) to the shelf controller. The shelf controller
receives the information, or retransmits the information downstream by way
of the SDH RS DCC and MS DCC to the adjacent network element.

Figure 8-6
Communication between the partitioned-OPC and network elements through optical fiber
DX1770p

receiver or receiver or
transmitter transmitter
Overhead Overhead Overhead
GraceLAN GraceLAN
MX MX
MMSB MMSB
SPEZ bus
SPEZ bus
SC SC
Ether- Ether-
net net
RS-232 RS-232
MI MI
Ethernet Ethernet
Active OPC Standby OPC

(primary) (backup)
LAN (to Preside) LAN (to Preside)
VT100
Legend
LAN = Local area network RX = Receiver
MI = Maintenance interface SC = Shelf controller
MMSB = Multi master serial bus SPEZ = Serial processor extension bus
MX = Message exchange TX = Transmitter
OPC = Operations controller

Communication between the OPC and independent networks through an

Ethernet DCC bridge
An Ethernet DCC bridge permits OAM&P messages to be exchanged between
networks elements that are not connected by fiber but are located at the same
site.
For example, two independent OPTera Connect DX networks (Figure 8-7 on

page 8-36), each with one network element at a common site, can be connected
with an Ethernet DCC bridge. The two independent networks are controlled by
the same OPC and could be in the same span of control since OAM&P
messages can travel through the Ethernet DCC bridge.
The maintenance interface circuit pack is equipped with three 10Base-T

Ethernet ports on its faceplate. The maintenance interface Ethernet ports allow
SDH RS and MS DCC bridging between adjacent OPTera Connect DX
network elements.
Figure 8-7
Ethernet DCC bridge
F3753
Ethernet
point-to-point
link
Ethernet Ethernet Ethernet

backplane faceplate backplane
connection connection connection
SC MI MI SC
Network element 1 Network element 2

Location of the partitioned OPC in a network

The purpose of the OPC is to provide a centralized view and control point for
the network elements that are contained within its span of control. Therefore,
the best place for the OPCs to be located is near VT100-compatible terminals
or workstations. Since the OPC storage circuit pack uses a removable media
for data backups and software upgrades, the primary OPC should be located in
an accessible site.
Although a configuration can function with a primary OPC only, it is

recommended that a configuration have a primary and backup OPC for
maximum protection against system failures.
Optical interface specifications

This chapter provides specifications for the optical interfaces in the OPTera
Table 8-27 on page 8-37 list the ITU-T G.957 classification of Nortel Networks
optical interfaces.
Table 8-27
ITU-T G.957 classification of optical circuit packs
PEC Circuit pack description ITU-T G.957 classification
NTCA33BA (FC) Quad STM-1o Compliant to ITU-T G.957 S1.1
NTCA33BB (ST) Quad STM-1o Compliant to ITU-T G.957 S1.1
NTCA33BC (SC) Quad STM-1o Compliant to ITU-T G.957 S1.1
NTCA33CA (FC) Quad STM-1o (4 RS DCC channels) Compliant to ITU-T G.957 S1.1
NTCA33CC (SC) Quad STM-1o (4 RS DCC channels) Compliant to ITU-T G.957 S1.1
NTCA35AA (MPO) HD STM-1o (0 RS DCC channel) Compliant to ITU-T G.957 S1.1
NTCA35AB (MPO) HD STM-1o (16 RS DCC channels) Compliant to ITU-T G.957 S1.1
NTCA36BA (FC) Quad STM-4o Compliant to ITU-T G.957 S4.1
NTCA36BB (ST) Quad STM-4o Compliant to ITU-T G.957 S4.1
NTCA36BC (SC) Quad STM-4o Compliant to ITU-T G.957 S4.1
NTCA36CA (FC) Quad STM-4o (4 RS DCC channels) Compliant to ITU-T G.957 S4.1
NTCA36CC (SC) Quad STM-4o (4 RS DCC channels) Compliant to ITU-T G.957 S4.1
NTCA30AL STM-16o (1310 nm) Compliant to ITU-T G.957 L16.1 except for
(see Note 1) the minimum overload sensitivity
(see Note 2).

Table 8-27
ITU-T G.957 classification of optical circuit packs
PEC Circuit pack description ITU-T G.957 classification
NTCA30AK STM-16o (1557 nm) Compliant to ITU-T G.957 L16.2 except for
(see Note 1) the minimum overload sensitivity
(see Note 2)
NTCA30CK STM-16o SR Compliant to ITU-T G.957 I-16
NTCA30xK STM-16o DWDM Compliant to ITU-T G.957 L16.2 except for

the minimum overload sensitivity
(see Note 2)
NTCA30AN STM-16o LR Compliant to ITU-T G.957 L16.2 except for

the minimum overload sensitivity
(see Note 2)
NTWR30AA Dual STM-16o SR Compliant to ITU-T G.957 I-16
NTWR30BA Dual STM-16o IR Compliant to ITU-T G.957 S-16.1
NTWR30CA Dual STM-16o LR Compliant to ITU-T G.957 L-16.1
NTWR31AB Quad STM-16o SR Compliant to ITU-T G.957 I-16
NTWR31BA Quad STM-16o IR Compliant to ITU-T G.957 S-16.1
NTWR06AB STM-64o SR Compliant to ITU-T G.691 S-64.2b
NTWR06CA STM-64o IR Compliant to ITU-T G.691 I-64.2b
NTWR06BA STM-64o LR Compliant to ITU-T G.691 L-64.2c
NTWR06BB STM-64o LR Compliant to ITU-T G.691 L-64.2c
NTCA06xx STM-64o DWDM Compliant to ITU-T G.691 L-64.2b
NTCF06xx STM-64o DWDM Compliant to ITU-T G.691 L-64.2b
NTCF16xx STM-64o DWDM Compliant to ITU-T G.691 L-64.2c

(see Note 1)
NTCA90CA Dual Gigabit Ethernet LX Compliant to IEEE 802.3z (Gigabit

Ethernet)
NTCA90EA Dual Gigabit Ethernet SX
NTCA90GA Dual Gigabit Ethernet ZX
Note 1: The NTCA30AL, NTCA30AK and NTCF16xx are manufacture-discontinued.

Note 2: The actual overload level of this circuit pack is -15 dB. ITU-T G.957 L16.1 and L16.2 specifies
a minimum overload sensitivity of -9 dB.
Rates and format specifications

The OPTera Connect DX meets the rate and format specifications defined in
ITU-T recommendation G.707.

Interface specifications
All OPTera Connect DX equipment complies with the SDH optical interface
specifications:
• all OPTera Connect DX transmit interfaces can transmit into receivers that
are not part of the OPTera Connect DX product
• all OPTera Connect DX receive interface circuit packs can accept signals
from transmitters that are not part of the OPTera Connect DX product
• OPTera Connect DX equipment can interwork with equipment that is not
part of the OPTera Connect DX product over the same link. The system
does not necessarily meet full OPTera Connect DX link specifications in
this case.
The specifications in this chapter apply to worst case production units, in
operation at environmental extremes and end-of-life limits.
HD STM-1o T/R, Quad STM-1o T/R and Quad STM-4 interface

specifications
Table 8-28 on page 8-39 provides the specifications for the HD STM-1o,
Quad STM-1o and Quad STM-4 transmit/receive (T/R) tributary interfaces for
OPTera Connect DX.
Table 8-28
HD STM-1o, Quad STM-1o and Quad STM-4 T/R specifications
Specifications
Quad STM-4 Quad STM-1o HD STM-1o

(see Note 4) (see Note 5)
(see Note 6)
Product engineering code NTCA36BA (FC) NTCA33BA (FC) NTCA35AB (MPO)

(PEC) (see Note 1) NTCA36BB (ST) NTCA33BB (ST)
NTCA36BC (SC) NTCA33BC (SC)
NTCA36CA (FC) NTCA33CA (FC)
NTCA36CC (SC) NTCA33CC (SC)
Transmitter
Laser Fabry-Perot laser
Pigtail single-mode
Central wavelength 1310 nm
Wavelength tolerance 1274 nm to 1356 nm 1261 nm to 1360 nm
Spectral width 2.5 nm 4.0 nm
Line rate 622.08 Mbit/s 155.52 Mbit/s
Line code NRZ


HD STM-1o, Quad STM-1o and Quad STM-4 T/R specifications
Specifications
Quad STM-4 Quad STM-1o HD STM-1o

(see Note 4) (see Note 5)
(see Note 6)
Maximum tolerated optical 20.0 dB

reflection (return loss)
(see Note 2)
Guaranteed launch power –15.0 dBm (min.)

(see Note 2) –8.0 dBm (max.)
Receiver
Detector PIN photodiode
Pigtail multi-mode single-mode
Wavelength of operation 1260 nm to 1360 nm 1261 nm to 1580 nm
Line rate 622.08 Mbit/s 155.52 Mbit/s
Line code NRZ
Overload level –8 dBm
Damage level (see Note 3) +3 dBm
Guaranteed receiver –28 dBm

sensitivity
Note 1: It is recommend to use SC connectors for OPTera Connect DX applications. FC and ST

connectors are also available.
Note 2: These parameters are worst-case parameters and include connector losses, aging, equipment
impairment caused by implementation, and temperature degradation. This value represents the power
level measured at the station fiber on the link side of connectors.
Note 3: Damage level is the maximum optical power for which no damage to the components occurs.
Note 4: The Quad STM-4 circuit packs NTCA36BA/BB/BC, support one RS DCC in port 1 only. The
Quad STM-4 circuit packs, NTCA36CA/CC, support four RS DCCs (one in each port).
Note 5: The Quad STM-1o circuit packs, NTCA33BA/BB/BC, support one RS DCC in port 1 only. The
Quad STM-1o circuit packs, NTCA33CA/CC, support four RS DCCs (one in each port).
Note 6: The HD STM-1o circuit pack NTCA35AA, does not support any RS DCC channels, SNCP and
intermediate path performance monitoring (IP PM ). The HD STM-1o circuit packs, NTCA35AB supports
sixteen RS DCCs (one per port), SNCP and intermediate path performance monitoring (IPPM).

Quad STM-16, Dual STM-16 and STM-16 tributary T/R interface

specifications
Table 8-29 on page 8-41 gives the specifications for the Dual STM-16
(NTWR30AA/BA/CA) and Quad STM-16 (NTWR31AB/BA) T/R tributary
interfaces. Table 8-29 on page 8-41 gives the specifications for the STM-16
(NTCA30xx) T/R tributary interfaces. Table 8-30 on page 8-42 gives the
specifications for the STM-16 (NTCA30xK) DWDM T/R tributary interfaces.
Table 8-29
Quad STM-16 and Dual STM-16 tributary T/R specifications
Specifications
Product engineering code NTWR30AA NTWR30BA NTWR30CA

(PEC) NTWR31AB NTWR31BA (LR)
(SR) (IR)
Connector (see Note 1) adapterless
Transmitter
Laser Fabry-Perot laser DFB laser
Pigtail single-mode
Central wavelength 1310 nm
Wavelength tolerance 1266 nm to 1260 nm to 1280 nm to

1360 nm 1360 nm 1335 nm
Spectral width 4.0 nm 1.0 nm
Side-mode suppression NA 30 dB
ratio (SMSR)
Line rate 2.488 Gbit/s
Line code NRZ
Maximum tolerated optical 27 dB

reflection (return loss)
Guaranteed launch power –10.0 dBm (min.) –5.0 dBm (min.) –2.0 dBm (min.)
(see Note 2) –3.0 dBm (max.) 0 dBm (max.) +3.0 dBm (max.)
Note 1: It is recommended that SC connectors are used for OPTera Connect DX applications. FC and
ST connectors are also available.
Receiver
Detector PIN photodiode APD


Quad STM-16 and Dual STM-16 tributary T/R specifications
Specifications
Product engineering code NTWR30AA NTWR30BA NTWR30CA

(PEC) NTWR31AB NTWR31BA (LR)
(SR) (IR)
Pigtail single-mode
Wavelength of operation 1250 nm to 1600 nm
Line code NRZ
Overload level −3.0 dBm 0 dBm -9.0 dBm

(see Note 4 and Note 5)
Damage level 3.0 dBm -5.0 dBm

(see Note 3)
Guaranteed receiver −18.0 dBm -27.0 dBm

sensitivity
(see Note 6)
Note 4: The overload level is different between the short reach, intermediate reach and long reach
STM-16 TR interface. The short and intermediate reach STM-16 TR interface has a PIN detector
whereas the long reach STM-16 TR interface has an APD detector. The APD is also more sensitive to
the power levels and potential risk of damage to hardware. The failure mode could range from dribbling
errors to hard failure.
Note 5: The overload level is the maximum optical power for which the interface meets:
— a bit-error rate (BER) of 10 -12 with forward error correction (FEC) off
— all jitter tolerance specifications
Note 6: The guaranteed receiver sensitivity values refer to a BER of 10 -12.
Table 8-30
STM-16 tributary T/R specifications
Specifications
Product NTCA30AL NTCA30AK NTCA30CK NTCA30AN

engineering code (1310 nm) (1557 nm) (SR) (LR)
(PEC) (see Note 2) (see Note 2)
Connector | adapterless
(see Note 1)
Transmitter
Laser DFB laser Fabry-Perot laser DFB laser


Specifications

Pigtail single-mode
Central wavelength 1310 nm 1557 nm 1310 nm 1550 nm
Wavelength range -
Wavelength + 10 nm + 3 nm 1266 nm to 1500 nm to

tolerance 1360 nm 1580 nm
Spectral width 0.65 nm 4.0 nm 0.65 nm
Side-mode 33 dB n/a 30 dB
suppression
ratio (SMSR)
Line code NRZ
Maximum tolerated 20 dB 27 dB 20 dB
optical reflection
(return loss)
Guaranteed launch –2.0 dBm (min.) –10.0 dBm (min.) –3.5 dBm (min.)
power 3.0 dBm (max.) –3.0 dBm (max.) –2.5 dBm (max.)
(see Note 3)
Note 1: It is recommended that SC connectors are used for OPTera Connect DX applications. FC and
ST connectors are also available.
Note 2: The NTCA30 AL and NTCA30AK circuit packs are manufactured discontinued.
Receiver
Detector avalanche photodiode PIN photodiode APD

(APD)
Pigtail single-mode
Wavelength of 1290 nm to 1570 nm

operation
Line code NRZ


Specifications

Overload level −15.0 dBm −3.0 dBm -15.0 dBm

(see Note 4, Note 5
and Note 6)
Damage level −5.0 dBm 3.0 dBm 0 dBm

(see Note 4)
Guaranteed −25.5 dBm −18.0 dBm -25.5 dBm

receiver sensitivity
(see Note 7)
Note 5: The overload level is different between the short reach, intermediate reach and long reach
STM-16 TR interface. The short and intermediate reach STM-16 TR interface has a PIN detector
whereas the long reach STM-16 TR interface has an APD detector. The APD is also more sensitive to
the power levels and potential risk of damage to hardware. The failure mode could range from dribbling
errors to hard failure.
Note 6: The overload level is the maximum optical power for which the interface meets:
— a bit-error rate (BER) of 10 -12 with forward error correction (FEC) off
— all jitter tolerance specifications
Note 7: The guaranteed receiver sensitivity values refer to a BER of 10 -12.
Dual Gigabit Ethernet tributary T/R interface specifications

Table 8-31 on page 8-44 gives the specifications for the Dual Gigabit Ethernet
(GE) short reach (SX), long reach (LX) and extended reach (ZX) T/R tributary
interfaces.
Table 8-31
Dual GE tributary specifications
Specifications Dual GE ZX Dual GE LX Dual GE SX
Product engineering code (PEC) NTCA90GA NTCA90CA NTCA90EA

(see Note)
Line rate 1.25 ± 100 ppm Gbit/s 1.25 ± 100 ppm Gbit/s 1.25 ± 100 ppm Gbit/s
Connector type SC SC SC
Operating temperature range -5°C to 70°C 0°C to 70°C 0°C to 70°C


Transmitter
Launch power range Max: 2.0 dBm Max: -3 dBm Max: -1.5 dBm
Min: -3.0 dBm Min: -9.5 dBm Min: -9.5 dBm
(For SMF) (when using 9 µm or (when using 50 µm or
<0.5 dBm 10 µm SMF) 62.5 µm MMF)
(when using 50 µm or Not provisionable Not provisionable
62.5 µm MMF)
Not provisionable
Wavelength range 1480 to 1580 nm 1272 to 1355 nm 830 to 860 nm
Central wavelength 1550 nm 1278 nm (minimum) 850 nm

1343 nm (maximum)
Spectral width 1.0 nm 1.4 nm (typical) 0.85 nm

2.8 nm (maximum)
Extinction ratio 9.0 db min 9.0 dB min 9.0 dB min
Transmitter type DFB Laser Fabry-Perot laser Vertical cavity

surface emitting laser
Modulator Direct Direct Direct
Reach 70 Km 10 km for 9 µm or 275 m for 62.5 µm

10 µm SMF (only MMF
achievable if far-end 550 m for 50 µm MMF
uses laser of
equivalent quality)
Receiver
Receiver level -23 dBm to -3dBm –20 dBm to –3 dBm –17 dBm to 0 dBm
Stressed sensitivity -18.0 dBm at 10E-12 -14.4 dBm at 10E-12 -12.5 dBm at 10E-12
for 62.5 µm MMF
-13.5 dBm at 10E-12
for 50 µm MMF
Wavelength range 1100 nm to 1600 nm 1270 nm to 1570 nm 770 nm to 860 nm
Overload level –3.0 dBm –3.0 dBm 0 dBm


Optical return loss 12.0 dBm 12.0 dBm 12.0 dBm
Detector type GaAs PIN GaAs PIN InP PIN Photodiode

Photodiode Photodiode
Note: See Chapter 9, “Ordering information”, for the complete information on Dual GE tributary circuit
packs.
STM-64 10G T/R interface specifications

Table 8-32 on page 8-46 gives the specifications for the OPTera Connect DX
STM-64 10G T/R circuit pack interfaces.
Table 8-32
Specifications DWDM TriFEC Short Reach Intermediate Long Reach

Reach
Product NTCA06xx NTCF06xx NTWR06AB NTWR06CA NTWR06BA

engineering code (see Note 3) (see Note 3) NTWR06BB
(PEC) (see Note 3)
(see Note 1)
Connector adapterless adapterless adapterless adapterless adapterless

(see Note 4)
Dispersion window 0 to 1500 0 to 1500 0 to 500 ps/nm 0 to 800 ps/nm 0 to 1500

ps/nm ps/nm ps/nm
Transmitter
Laser DFB laser DFB laser EML laser MZ LiNb03 DFB laser
laser
Pigtail single-mode single-mode single-mode single-mode single-mode
Central Refer to Table Refer to Table 1550 nm 1550 nm 1533 nm

wavelength 9-3 on page 9-3 on page 1557 nm
9-30 9-30
Wavelength range 1528.77 to 1528.77 to 1530 to 1565 1530 to 1565 1533 and 1557
1603.13 nm 1603.13 nm nm nm nm
Laser wavelength ±0.04 nm ±0.05 nm ±0.125 nm ±0.125 nm ±2.5 nm

tolerance
Spectral width 0.115 nm 0.115 nm 0.115 nm 0.115 nm 0.115 nm

(see Note 9)



Reach
Side-mode 40 dB 40 dB 30 dB 30 dB 40 dB
suppression ratio
(SMSR)
(unmodulated)
Chirp polarity positive or positive or Fixed Fixed Fixed

negative negative (see Note 7) (see Note 7) (see Note 7
(configurable, (configurable, and Note 8)
see Note 6) see Note 6)
Line rate STM-64 (9.953 STM-64 (9.953 STM-64 (9.953 STM-64 (9.953 STM-64 (9.953
Gbit/s) Gbit/s) Gbit/s) Gbit/s) Gbit/s)
Line code NRZ NRZ NRZ NRZ NRZ
Maximum 27 dB 27 dB 20 dB 27 dB 27 dB
tolerated optical
reflection (return
loss)
Reflection –14 dB –14 dB –14 dB –14 dB –14 dB

tolerance
Guaranteed –10 dBm (min.) –10 dBm (min.) – 5.0 dBm 1.5 ± 0.5 dBm 1.5 dBm
launch power (see 1.5 dBm 1.5 dBm (min.) (see Note 7) (see Note 7
Note 5) (max.) (max.) –1 dBm (max.) and Note 8)
(see Note 6) (see Note 6) (see Note 7)
Note 1: See Chapter 9, “Ordering information”, for the complete list of STM-64 interface PEC codes.
Note 2: The NTCA06xR/S/V/W, and NTCF06xR/S/V/W and all NTCF16xx circuit packs are
manufactured discontinued.
Note 3: The NTWR06BA is STM-64 1533 nm T/R and the NTWR06BB is STM-64 1557 nm T/R.
Note 4: SC connectors are recommended for OPTera Connect DX applications. FC and ST connectors
are also available.
Note 5: This parameter is a worst-case parameter and includes connector losses, aging, equipment
impairment caused by implementation, and temperature degradation.
Note 6: You can configure the chirp polarity and output power parameters. You can configure the chirp
polarity as positive or negative. You can configure the output power between –10 dBm and 1.5 dBm.
Guaranteed accuracy of power is ±0.5 dBm.
Note 7: You can not configure the chirp polarity.
Note 8: The chirp polarity is set to negative and you must provision the output power to +1.5 dBm to
satisfy a link with 21 dB loss and 1500ps/nm dispersion (NDSF fiber).
Note 9: The spectral width specification measurement is based on -3 dB.



Reach
Receiver
Detector PIN PIN PIN PIN Avalanche

photodiode photodiode photodiode photodiode photodiode
(APD)
Pigtail single-mode single-mode single-mode single-mode single-mode
Wavelength of 1290 to 1603 1290 to 1603 1290 to 1603 1290 to 1603 1290 to 1603
operation nm nm nm nm nm
Line rate STM-64 (9.953 STM-64 (9.953 STM-64 (9.953 STM-64 (9.953 STM-64 (9.953
Gbit/s) Gbit/s) Gbit/s) Gbit/s) Gbit/s)
Line code NRZ NRZ NRZ NRZ NRZ
Overload level 0 dBm 0 dBm 0 dBm 0 dBm −5 dBm

(see Note 10)
Damage level +5.0 dBm +5 dBm +5.0 dBm +5.0 dBm +5.0 dBm
(see Note 11)
Guaranteed −15.95 dBm −15.95 dBm −15.95 dBm −15.95 dBm −24 dBm
receiver sensitivity (see Note 13) (see Note 13) (see Note 13) (see Note 13) (see Note 14)
(see Note 12)
Note 10: The overload level is the maximum optical power for which the interface meets an
uncorrected bit-error rate (BER) of 10 −12 with FEC off or 10 −15 with FEC on.
Note 12: The sensitivity level is the minimum optical power for which the interface meets an
uncorrected bit-error rate of 10 −10 with FEC off.
Note 13: The guaranteed end-of-life performance is −14 dBm at a bit-error rate of 10 −13.
Note 14: The guaranteed end-of-life performance is −20.5 dBm at a bit-error rate of 10 −13.
Optical link budgets

This section provides information on optical link budgets.
Dispersion sign
Dispersion on an OPTera Connect DX fiber link can be positive or negative.
To determine the net dispersion for an optical fiber link, consider the position
of the fiber zero dispersion wavelength λ0 with respect to the transmitter
wavelength. The zero dispersion wavelength of an optical fiber is the
wavelength at which dispersion is zero. Transmitters with a center wavelength
greater than λ0 have positive dispersion. Transmitters with a center
wavelength less than λ0 have negative dispersion (see Figure 8-8).

A positive dispersion sign always occurs on standard single-mode fiber

(non-dispersion-shifted fiber or NDSF). Either sign can occur on standard
dispersion-shifted fiber (DSF). Dispersion ranges calculated for standard DSF
are the worst case for:
• a signal wavelength of 1557 ± 2.5 nm
• a zero dispersion wavelength of 1557.5 ± 12.5 nm
Precompensation designed into the transmitter and additional dispersion
compensating modules (DCMs) in NDSF links provide compensation for
dispersion. For DWDM system applications from 2 to 32 wavelengths, refer to
the Optical Networks Applications Library, NTCA66BA. For 1600G system
applications, refer to the OPTera Long Haul 1600G Amplifier Optical Layer
Application Guide, NTY315DX.
The maximum link dispersion values in link budget tables in this chapter
assume the appropriate sign (positive or negative) of precompensation.
Minimum sensitivity values include worst-case link dispersion impairment.
Figure 8-8
Zero dispersion wavelength
F3693
Dispersion D (ps/nm.km)
Transmitter λ2<λ0 Positive

λ2 dispersion
Negative λ0 λ1 λ
dispersion Transmitter λ1>λ0
Optical link budgets

The OPTera Connect DX system uses undefined bytes in the SDH overhead to
provide single forward error correction (FEC) and triple forward error
correction (TriFEC) on the optical links. The FEC or TriFEC improves the
performance of the OPTera Connect DX receivers. For optical link

performance and optical link achievable with FEC and TriFEC, refer to the
OPTera Long Haul 1600G Amplifier Optical Layer Application Guide,
NTY315DX.
The OPTera Connect DX link budgets in this section are for a corrected BER
level of 10 −15 EOL. This number is equivalent to an uncorrected BER level of
10 −12 EOL.
Low reflection and tuned optical connectors are necessary at the transmit and
receive interfaces. A tuned optical connector is a connector with a better
alignment of cores, which provides a lower insertion loss. The maximum
connector insertion loss for SC-PC square connectors is 0.3 dBm. The transmit
interfaces output power and receiver sensitivity values in this chapter include
the connector insertion loss. It is recommend that you use SC connectors and
tuned optical patch cords with OPTera Connect DX systems. SC connectors
offer better performance than FC/PC or ST connectors.
The following link budgets take into consideration penalties caused by

non-linearities. Values are based on those of normally installed optical fiber
plant and for the optical power levels in the optical fiber. Transmit interfaces
minimum and maximum output power values in the link budget calculations
are EOL values.
Single span link budgets

For DWDM system applications from 2 to 32 wavelengths, refer to the Optical
Networks Applications Library, NTCA66BA. For OPTera Long Haul 1600G
system applications, refer to the OPTera Long Haul 1600G Amplifier Optical
Layer Application Guide, NTY315DX.

9-1
Ordering information 9-
Introduction
This chapter provides a description of the engineering rules and ordering
information for the OPTera Connect DX network element. This chapter
includes information about:
• the process you use to select a set of OPTera Connect DX equipment to
meet your requirements (Procedure 9-1, “Selecting a set of OPTera
Connect DX equipment”)
• order codes and engineering rules for hardware
• order codes and engineering rules for software
• order codes for documentation
• engineering and installation services
Network element
OPTera Connect DX Release 6.0 supports the DX_HUB network element type
only on the OPTera Connect DX platform. The DX_HUB network element
supports the following 10 Gbit/s configurations:
N = (8 - (4xP))/2]
M = (8 - (4xP))/2]
• Nx2-Fiber Ring (N is 1 to 4)
M = (8 - (2xN))/2]
M is 0 to 4 and K = 8 - 2x(N+M)]

9-2 Ordering information

You can configure an OPTera Connect DX Release 6.0 network element with
Quad STM-1o/e, Quad STM-4, HD STM-1o/e, STM-16, Dual STM-16,
Quad STM-16 and Dual Gigabit Ethernet (GE) tributary circuit packs. OPTera
Connect DX Release 6.0 supports:
• 1+1 (1*1 for matched nodes) protected STM-1o/e, STM-4 and STM-16
tributaries
• unprotected STM-1o/e, STM-4, STM-16 and GE tributaries
• SNCP Ring for STM-4 and STM-16 tributaries
• 2-Fiber MS-SPRing for STM-16 tributaries only
Note 1: The Quad STM-16 circuit pack is supported in the universal slots
only.
Note 2: The HD STM-1o/e, Dual STM-16 and Quad GE circuit packs are
supported in both the universal slots and the tributary circuit pack slots.

Procedure 9-1
Selecting a set of OPTera Connect DX equipment
Follow this procedure to select a set of OPTera Connect DX equipment to
provide the features you need.
Procedure tasks
• Select the required bay and the bay junction kits (step 2).
• Select earthquake zone 4 fixings, if you require these items (step 3).
• Select height extenders, if you require these items (step 4).
• Select end guards and label holders, if you require these items (step 5 and step 6).
• Select IBN grounding, if you require this item (step 7).
• Select special power feed kits, if you require these items (step 8 and step 9).
• Select the circuit packs and the interface cables for the control shelf (step 10 and step 11).
• Select the switch modules for the main transport shelf (step 12).
• Select the STM-64 10G T/R circuit packs, optical adapters and the optical fiber cables for the main
transport shelf (step 13 to step 15).
• Select the tributary circuit packs for the main transport shelf and extension shelf (step 16).
• Select the optical adapters and the optical fiber cables for the optical tributary circuit packs (step 17 to
step 18).
• Select the external breakout optical fiber cable or optical fiber cable assemblies for the optical HD
STM-1o tributary circuit packs (step 19).
• Select the coaxial cables for the Quad STM-1e tributary circuit packs (step 20).
• Select the coaxial cables for the HD STM-1e tributary circuit packs (step 21).
• Select the filler cards for all empty slots (step 22).
• Select the software and software licenses and certificates you require for this configuration (step 24).
• Select the documentation you require (step 27).
• Check that you can make the configuration you have defined. (step 28).
Expected results
• You have specified a set of equipment, units and cables which make up an OPTera Connect DX network
element that meets your requirements.
• If the expected results do not occur:
— Go through the selection process a second time.
— Contact Nortel Networks for support.
—continued—

Procedure 9-1 (continued)

Action
Step Action
1 Review the product structure for the OPTera Connect DX Release 6.0
network element:
• Figure 9-1 on page 9-12 gives an overview of the structure of the
equipment which makes up the OPTera Connect DX network element.
2 Select the OPTera Connect DX bay you require:
• If you do not require more than eight tributary circuit packs, select
"OPTera Connect DX bay, no extension shelf" (NTCA91AA).
• If you require more than eight tributary circuit packs, select "OPTera
Connect DX bay with extension shelf" (NTCA91AB).
• If you require a bay with rear exhaust air flow, select "OPTera Connect
DX bay with rear exhaust air flow" (NTCA91AC). This bay contains a
tributary extension shelf.
• If you do not require more than eight tributary circuit packs and you want
the option to install the supported OPTera Metro network element in the
bottom of this bay, select "OPTera Metro Connect bay" (NTCA91BA). For
more information, refer to the OPTera Metro Connect SDH User Guide,
NTCA69YA.
• Table 9-1 on page 9-22 lists these items.
3 If you want to fix this bay to meet zone 4 earthquake standards, select
"Earthquake anchor bolts kit (zone 4)".
4 If you want to extend the height of the bay, select the appropriate height
extender kit:
• To extend the height of the bay to meet the ETSI requirements, order
"Frame extender to 2200 mm (75 mm)".
5 If this OPTera Connect DX bay is at the end of a row:
• order "End panel kit for a 660 mm line up".
—continued—


Step Action
6 If you require a label at the top of this bay, select "Top label holder kit".
• Table 9-1 on page 9-22 lists this item.
7 If you require IBN grounding for this bay, order "Frame insulator kit".
• Table 9-1 on page 9-22 lists this item.
8 If you want two power feeds (instead of the six power feeds that are
standard):
• Order "Power feed jumper kit (# 2 AWG kit)"
• If you want to connect the dc power (with two power cables) at the top of
the bay, order "OPTera top power kit (in an ETSI installation)".
• If you want to connect the dc power (with two power cables) at the bottom
of the bay, order “OPTera bottom power kit (in an ETSI installation)”
9 If you require access through the floor for the power and control cables, order
"ETSI through-floor kit".
• Refer to Table 9-1 on page 9-22.
10 Select the circuit packs you require for the control shelf:
• Refer to Figure 9-4 on page 9-17 for a layout of the circuit packs in the
control shelf.
• Refer to Table 9-9 on page 9-50 for the slot allocations and the
engineering rules for the control shelf.
• You can order bay assemblies and sets of circuit packs to meet specific
requirements as part of a model. Refer to “Models” in this chapter.
11 Order the cables to provide the user interfaces and network communications:
• Refer to "Peripheral cables" in this chapter for the order codes and
engineering rules of the cables that connect to the control shelf.
12 Select two of the switch module circuit packs:
• Refer to Figure 9-6 on page 9-19 that shows the positions of the switch
module circuit packs in the main transport shelf.
• Table 9-5 on page 9-42 lists the switch module circuit packs.
13 Select the STM-64 transport circuit packs (STM-64 10G T/R circuit packs)
you require:
• For an unprotected 10 Gbit/s T/R terminal, select one STM-64 10G T/R
circuit pack.
• For a 10 Gbit/s Linear 1+1 terminal, select two STM-64 10G T/R circuit
packs.
• For a 2-Fiber Ring, select two STM-64 10G T/R circuit packs.
• For a 4-Fiber ADM, select four STM-64 10G T/R circuit packs.
—continued—


Step Action
• Refer to Figure 9-6 on page 9-19 that shows the positions of eight
STM-64 10G T/R circuit packs in the main transport shelf of an OPTera
Connect DX bay.
Note: The network element supports mixed configurations and a maximum
of eight STM-64 T/R circuit packs with DX140 switch modules. Refer to
“Switch modules” in this chapter for the supported configurations. You can
equip the network element to its maximum STM-64 T/R circuit packs capacity,
provided the configurations are supported.
• Some STM-64 10G T/R circuit packs are available in AM1/AM2
provisionable. Refer to Table 9-3 on page 9-30.
• STM-64 short-reach 10G T/R circuit pack are available for short reach
applications
• STM-64 intermediate reach 10G T/R circuit pack are available for
intermediate reach applications
• STM-64 long-reach 10G T/R circuit pack are available for long-reach
applications
• Select the STM-64 10G T/R circuit packs to match the DWDM
wavelength plan you use. If you are using MOR or MOR Plus amplifiers
as your optical link, for information about the order of introduction of
wavelengths for DWDM system applications from 2 to 32 wavelengths,
refer to the Optical Networks Applications Library, NTCA66BA. If you are
using OPTera Long Haul amplifiers as your optical link, for information
about the order of introduction of wavelengths, refer to the OPTera Long
Haul 1600G Amplifier Network Application Guide, NTY314AF.
• STM-64 10G T/R circuit packs are adapterless. You determine the type
of optical connector when you select the optical connector adapter in
step 14.
• Table 9-3 on page 9-30 and Table 9-4 on page 9-40 list the STM-64 10G
T/R circuit packs.
14 Order two optical connector adapter kits for each STM-64 10G T/R circuit
pack you ordered in step 13.
• Optical connector adapter kits are available with FC, ST, or SC
connectors.
• It is recommended that you use SC connectors for OPTera Connect DX
applications. FC and ST connectors are also available.
• Table 9-8 on page 9-49 lists the optical connector adapter kits.
—continued—


Step Action
15 Order the optical fiber cables you require for the STM-64 10G T/R circuit
packs:
• Order two optical fiber cables for each STM-64 10G T/R circuit pack.
• Refer to "Optical fiber cables" in this chapter for the order codes and
engineering rules for the optical fiber cables.
16 Select the T/R tributary circuit packs you require:
• Refer to Figure 9-6 on page 9-19 for a sample configuration of the
tributary circuit packs in the main transport shelf of an OPTera Connect
DX network element.
• Refer to Figure 9-8 on page 9-21 for a sample configuration of the
tributary circuit packs in the extension shelf of an OPTera Connect DX
network element.
• Order tributary circuit pack in pairs (except Dual GE circuit packs) for
protection, SNCP Ring, and 2 Fiber Ring (STM-16, Dual STM-16 and
Quad STM-16 T/R circuit packs only).
• Order single tributary circuit packs for an unprotected tributaries.
• You can install any combination of tributary circuit packs up to a
maximum payload equivalent to 64 STM-1 protected or 128 STM-1
unprotected using the DX65 switch module.
• You can install any combination of tributary circuit packs up to a
maximum payload equivalent to:
— 192 STM-1 protected or 384 STM-1 unprotected using the DX100 or
DX140 switch modules and equipping the tributary circuit pack slots
only.
— 320 STM-1 protected or 640 STM-1 unprotected using the DX100
switch modules and equipping the tributary circuit pack slots and
tributary circuit packs in universal slots G11, G12, G17 and G18.
— 448 STM-1 protected or 896 STM-1 unprotected using the DX140
switch modules and equipping the tributary circuit pack slots and
tributary circuit packs in universal slots G0, G9, G10, G11, G12, G17,
G18 and G19.
—continued—


Step Action
• Quad STM-1e and HD STM-1e tributary circuit packs are available.

• Quad STM-1o tributary circuit packs with one RS DCC are available for
1310 nm with FC, ST or SC connectors. Quad STM-1o tributary circuit
packs with four RS DCCs are available for 1310 nm with FC or SC
connectors.
• HD STM-1o tributary circuit packs are available for 1310 nm with MPO
connectors.
• Quad STM-4 tributary circuit packs with one RS DCC are available for
1310 nm with FC, ST or SC connectors. Quad STM-4 tributary circuit
packs with four RS DCCs are available for 1310 nm with FC or SC
connectors.
• STM-16, Dual STM-16 and Quad STM-16 tributary circuit packs are
available for 1310 nm wavelengths. STM-16 tributary circuit packs are
also available for DWDM wavelengths. Refer to OC-48 DWDM Tributary
Application Note, NTRR12AC (OC 99-176) for information about STM-16
DWDM tributary applications.
• Although this guide refers to OC-48 DWDM tributaries, the same circuit
packs are used for STM-16 DWDM tributaries and the same guidelines
can be followed.
• STM-16 and Dual STM-16 tributary circuit packs are adapterless. You
determine the type of optical connector when you select the optical
connector adapter in step 17.
• Quad STM-16 tributary circuit packs are available for 1310 nm with SC
connectors
• Table 9-6 on page 9-43 lists the T/R tributary circuit packs.
17 Order two optical connector adapter kits for each single STM-16 tributary
circuit pack, four optical connector adapter kits for each Dual STM-16
tributary circuit pack that you ordered in step 16.
• Optical connector adapter kits are available with FC, ST, or SC
connectors.
• It is recommended that you use SC connectors for OPTera Connect DX
applications. FC and ST connectors are also available.
• Table 9-8 on page 9-49 lists the optical connector adapter kits.
—continued—

18 Order the optical fiber cables you require for the optical tributary circuit packs:
• Order two optical fiber cables for each STM-16 circuit pack.
• Order four optical fiber cables for each Dual STM-16 circuit pack.
• Order eight optical fiber cables for each Quad STM-16 circuit pack.
• Order four optical fiber cables for each Dual GE LX and GE ZX circuit
pack.
• Order four multimode optical fiber cables (see Table 9-16 on page 9-65)
for each Dual GE SX circuit pack.
• Order eight optical fiber cables for each Quad STM-4 circuit pack.
• Order eight optical fiber cables for each Quad STM-1o circuit pack.
• Refer to "Cables" in this chapter for the order codes and engineering
rules of the optical fiber cables.
19 If the network element includes HD STM-1o T/R tributary circuit packs and
you are terminating the tributaries on a fiber distribution frame or an external
fiber patch panel:
• Order four external breakout fiber cable or optical fiber cable assemblies
for each HD STM-1o circuit pack.
• Refer to "HD STM-1o optical fiber cable assemblies" in this chapter for
the order codes and engineering rules of the optical fiber cable
assemblies.
20 Order the cables you require for the Quad STM-1e tributary circuit packs:
• Order one ‘STM-1e Quad cable 10 m’ (NTCC90KA) for each Quad
STM-1e tributary circuit pack.
• If you need a connection panel, order ‘STM-1e customer connection
panel’, (NTCE38AA).
Note: The connection panel does not fit in the OPTera Connect DX bay.
• Refer to "Quad STM-1e coaxial cables" in this chapter for the order codes
and engineering rules of the coaxial cable and connection panel.
21 Order the cables you require for the HD STM-1e tributary circuit packs:
• Order one HD STM-1e coaxial cable assembly for each HD STM-1e
tributary circuit pack.
• Refer to "HD STM-1e coaxial cable assembly" in this chapter for the order
codes and engineering rules of the coaxial cables.
—continued—


Step Action
22 Check the configuration you have to order filler cards for all slots that remain
empty.
• Table 9-7 on page 9-48 lists the filler cards.
23 Order spare circuit packs to suit your requirements. Base the number of
spares you order on the practices of your company. It is recommended that
you order the following:
• traffic carrying circuit packs, as required
• at least one external synchronization interface (ESI) circuit pack
• at least one shelf controller (SC) circuit pack
• at least one maintenance interface (MI) circuit pack
24 Select the software load you require. You must have one "OPTera Connect
DX Release 6.0 software load" for each network element. You can order the
software load on:
• an OPC storage module
• a maintenance interface circuit pack
• a magnetic tape cartridge
• an OPC flash cartridge
25 Select the software licenses you require.
• You must order licenses and certificates for each network element.
• Use the table below to select mandatory software licenses and upgrade
certificate as well as any additional software licenses.
NE Type Software Licenses
Mandatory As required
New • Application licence • Extended application licence

• Software certificate • Utility and features licence
Existing • Upgrade license • Applications license

• Software certificate • Extended applications license
• Utility and features license
• Refer to "Software licenses and certificates" in this chapter for more

details.
26 Order the Preside licenses you require.
• Refer to the Preside NTP Library, 450-3101-XXX, for details of the
software licenses for network management.

27 Select the customer documentation you require.

• Select from CD-ROM or paper versions.
• Refer to "Documentation" in this chapter.
28 Check that the equipment selection that makes up the configuration you
require is possible:
• Refer to the ordering information engineering rules about the equipment
you selected.
• If you cannot define an OPTera Connect DX configuration to meet your
requirements, contact your Nortel Networks representative.
—end—

Figure 9-1
OPTera Connect DX Release 6.0 product structure
OPTera Connect DX
Release 6.0
OPTera Connect DX bay with OPTera Connect DX bay no extension shelf

extension shelf (Table 9-1) or OPTera Metro Connect (Table 9-1)
Bay installation items

fixings, extenders,
power feed kits,
(Table 9-1)
Common equipment Peripheral cables

Software loads and circuit packs (Table 9-9) (Table 9-17)
licenses (Table 9-18 and
Table 9-20)
Switch modules Optical fiber cables
(Table 9-5) (Table 9-11 and Table 9-12)
Documentation
• NTPs (Table 9-21 and STM-64 T/R circuit Optical adapter kits
Table 9-22) packs (Table 9-3) SC-SC, SC-FC, SC-ST
• Planning Guides and (Table 9-8)
additional documentation
(Table 9-23)
STM-16 T/R tributary Optical adapter kits
• CAPs (Table 9-24) circuit packs (Table 9-6) SC-SC, SC-FC, SC-ST
(Table 9-8)
Models
(Table 9-25) Dual GE tributary circuit Optical fiber cables
packs (Table 9-6) (Table 9-11, Table 9-12
and Table 9-16)
Filler cards Quad STM-1 and Quad

STM-4 T/R circuit packs Optical fiber cables
(Table 9-7)
(Table 9-6) (Table 9-11 and Table 9-12)
Fiber cable assemblies

HD STM-1o T/R circuit
MPO-MPO/SC/FC conn
packs (Table 9-6)
(Table 9-13)
Note: The engineering rules STM-1e electrical
Quad STM-1e T/R circuit
and quantities for the items in cables and connection
packs (Table 9-6)
this diagram are given in the panel (Table 9-14)
‘Rules’ section after the HD STM-1e coaxial
HD STM-1e T/R circuit
appropriate table. cables (Table 9-15)
packs (Table 9-6)

OPTera Connect DX bay

An OPTera Connect DX bay includes the following:
• a bay frame
• a number of interconnected shelves that provide the OPTera Connect DX
functionality, specific to the requirement
• two environmental control panels (only one panel is included with the
OPTera Metro Connect bay)
• a fiber manager with two fiber management trays (not included with the
OPTera Metro Connect bay)
Note: You can order the bay with the circuit packs fitted, or with the circuit
packs not fitted. The order code for the bay does not include any circuit
packs. Order the circuit packs under their separate codes.
Figure 9-2 on page 9-15 shows an example of an OPTera Connect DX bay with
extension shelf. Figure 9-3 on page 9-16 shows an example of an OPTera
Connect DX OPTera Metro Connect bay. Table 9-1 on page 9-22 lists the
OPTera Connect DX bays, shelves and auxiliary equipment.
Control shelf
The control shelf contains the common equipment circuit packs that are listed
in “Common equipment circuit packs” in this chapter.
Figure 9-4 on page 9-17 shows the layout of the circuit packs in the control
shelf.

The main transport shelf of an OPTera Connect DX network element contains
the switch module circuit packs, STM-64 10G T/R transport interface circuit
packs and tributary circuit packs:
• “STM-64 T/R interface circuit packs” in this chapter lists the STM-64 10G
T/R transport interface circuit packs in the main transport shelf
• “STM-64 T/R short, intermediate and long reach interface circuit packs”
in this chapter lists the STM-64 10G T/R short, intermediate and long
reach interface circuit pack in the main transport shelf
• “Switch modules” in this chapter lists the switch module circuit packs in
the main transport shelf
• “Tributary circuit packs” in this chapter lists the tributary interface circuit
packs in the main transport shelf and the extension shelf
• “Filler cards” in this chapter lists the filler cards
• “Optical connector adapter kits” in this chapter lists the optical connector
adaptor kits

Figure 9-5 on page 9-18 shows the layout of the main transport shelf showing
supported circuit pack slots for DX65 switch modules. Figure 9-6 on page 9-19
shows the layout of the main transport shelf showing supported circuit pack
slots for DX100 switch modules. Figure 9-7 on page 9-20 shows the layout of
the main transport shelf showing supported circuit pack slots for DX140
switch modules.
Extension shelf
The extension shelf contains tributary circuit packs and filler cards. A
maximum of eight tributary circuit packs can be installed in the extension
shelf. See “Tributary circuit packs” in this chapter for a list of tributary circuit
packs supported in the extension shelf. Figure 9-8 on page 9-21 shows the
layout of the circuit packs in the extension shelf.
Note 1: Slots 1 and 10 cannot support tributary circuit packs and must be
filled with filler cards.
Note 2: If you want to use tributaries in the extension shelf, you must
equip the system with DX100 (NTCA26BA) or DX140 (NTCA26CA)
switch modules in the main transport shelf. Refer to “Switch modules” in
this chapter for more details.

Figure 9-2
OPTera Connect DX bay with extension shelf
DX2710p
Cable Cover
(both sides)
Control shelf
Fan
(3 places)

shelf

shelf
Fan
(3 places)
Extension shelf

Figure 9-3
OPTera Metro Connect bay
DX4119p
Cable Cover
(both sides)
Control shelf
Fan
(3 places)

shelf

shelf

Figure 9-4
OPTera Connect DX control shelf
DX4967p
Breaker/filter module A
Breaker/filter module B
OPC controller
OPC storage
OPC I/F
ESI G1
ESI G2
MX G1
MX G2
PT G2
PT G3
Filler
Filler
OW
SC
MI
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Note 1: The parallel telemetry (PT) circuit packs and the Orderwire (OW) circuit pack
are optional circuit packs.
Note 2: The second MX circuit pack (MX G2) is highly recommended
but it is not mandatory.
Note 3: OPC circuit packs in slots 3, 4, 5, and 12 are not required in every network element.
All three circuit packs are only required in a network element that houses the primary
OPC or backup OPC.

Figure 9-5
1
Filler G0
11
Filler
G10
2
12
G1
G11

13
G2
G12
4
G3
slot
14
5
G4
slot
6
G5
slot
15
7
G6
slot

16
8
G7
G17
17
G8
G18
10
18
G9
Filler Filler
G19
DX5356p
Figure 9-6
1
Filler
G0
11
Filler
G10
2
12
G1
G11
Universal slot slot
13
G2
G12
Universal slot slot
4
G3
slot
14
5
G4
slot
6
G5
slot
15
7
G6
slot

16
8
G7
G17
Universal slot slot
9
17
G8
G18
Universal slot slot
10
18
G9
Filler Filler
G19

DX5353p
Figure 9-7
11
G0
G10
2
12
G1
G11
Universal slot slot
3
13
G2
G12
Universal slot

slot
4
G3
slot
14
5
G4
slot
6
G5
slot
15
7
G6
slot

16
8
G7
G17
Universal slot slot
17
G18
G8
Universal slot slot

10
18
G9
G19

DX5354p
Figure 9-8
OPTera Connect DX extension shelf showing supported circuit pack slots
DX5357p
G20 G21 G22 G23 G24 G25 G26 G27 G28 G29

slot
slot
slot
slot
slot
slot
slot
slot
Filler Filler
1 2 3 4 5 6 7 8 9 10

Bay equipment
Table 9-1 on page 9-22 provides information about OPTera Connect DX bay
equipment.
Table 9-1
OPTera Connect DX bays and shelves
Description Order code CPC Rules

(PEC)
Bays and shelves
OPTera Connect DX bay, no extension shelf NTCA91AA A0781274 1, 5, 6, 7
OPTera Connect DX bay with extension shelf NTCA91AB A0781276 2, 5, 6, 7
OPTera Connect DX bay with rear exhaust air flow NTCA91AC A0896276 3, 5, 6, 7
OPTera Metro Connect bay NTCA91BA A0875501 4, 5, 6, 7
Earthquake anchor bolts kit (zone 4) NT7E74AA A0370984 8
OPTera bay top fixing kit A0820535 9
OPTera bay frame junction kit A0820534 10
ANSI frame accessory kit NTCA89GL A0803267 11
ETSI frame accessory kit NTCA89GK A0803268 12
End panel kit for a 600 mm line up NTRU0403 A0790388 14
End panel kit for a 660 mm line up NTRU0404 A0790389 13
Frame extender to 7.5 ft NTRU0405 A0790390 15
Frame extender to 8 ft NTRU0406 A0790391
Frame extender to 9 ft NTRU0407 A0790392
Frame extender to 11.5 ft NTRU0408 A0790393
Frame extender to 7 ft (9 mm) NTRU0409 A0790394
Frame extender to 2200 mm (75 mm) NTRU0414 A0799164
Frame extender to 2600 mm NTCA89GM A0810340
Top label holder kit A0785009 16
Frame insulator kit NTRU0410 A0790395 17
Frame levelling kit NT7E6040 A0797043 18
OPTera Metro Connect bay environmental control NTCA85FB A0875401 19

panel (ECP)
OPTera Connect Top infill panel kit (2200 mm) NTCA91ML A0993402 20



(PEC)
Power feed kits
Power feed jumper kit (# 4 AWG kit) NTCA89GE A0797615 21
Power feed jumper kit (# 2 AWG kit) NTCA89GJ A0887153 22
ANSI through-floor kit NTCA89GF A0797615 23
ETSI through-floor kit NTCA89GG A0797617 24
OPTera top power kit (in an ETSI installation) A0820533 25
OPTera bottom power kit (in an ETSI installation) A0820532 26
Coaxial cable management kits
OPTera Connect DX Quad STM-1e coax cable NTCA91MB A0821175 27

dressing kit (in an ETSI installation)
OPTera Connect DX coax feeder lane kit, 16 NTCA91MC A0872303 28, 29

HD STM-1e (in an ETSI installation)
Quad STM-1e OPTera Connect DX Coax NTCA91ME A0881775 30

trough/kickplate
HD STM-1e OPTera Connect DX Coax NTCA91MK A0993401 31

trough/kickplate
Equipment supplied as part of the bay
Front access frame 2.13 m (7 ft.) NTRU0411 A0790396 32
ANSI washer kit NTRU0412 A0790397
Top cover assembly NTCC8154 A0789630
Environmental control panel (ECP) NTCA85CA A0768688
OPTera Metro Connect bay environmental control NTCA85FA A0875399 33

panel (ECP)
Fan module NTCA85EA A0816914 32, 34
Universal synchronization alarms and telemetry NTCE8134 A0622195

terminations (UniSATT)
Fiber manager shelf - 2 tray NTCA84GA A0793199 32
Baffle assembly (top) NTCC9101 A0781286 32, 34
Baffle assembly (bottom) NTCC9102 A0781287



(PEC)
Control shelf NTCA81GA A0776337 32, 35
Main transport shelf NTCC80BA A0781277 32
Extension shelf NTCC83BA A0781283 36
Ordering rules for bays and shelves

1 Order this item if you do not require the extension shelf. This item includes
a bay frame, unequipped control shelf, unequipped main transport shelf,
two environmental control panels, fiber manager with two trays, zone 2
bay fixings, all required fixings and cables for a completely equipped bay.
For this configuration, OPTera Connect DX Release 6.0 supports a
maximum of eight tributary circuit packs in the tributary section of main
transport shelf and optionally a maximum eight tributary circuit packs in
universal slots.
2 This item includes the items listed in rule 1 and an unequipped extension
shelf. Order this item if you want to have the option for an addition of eight
tributary circuit packs. For this configuration, OPTera Connect DX
Release 6.0 supports a maximum of eight tributary circuit packs in the
tributary section of main transport shelf, a maximum of eight tributary
circuit packs in the extension shelf and optionally a maximum eight
tributary circuit packs in universal slots.
3 This item includes the items listed in rule 1, an unequipped extension shelf
and air flow exhaust that exits from the rear of the bay. Order this item if
you want to have the option for more than eight tributary circuit packs.
OPTera Connect DX Release 6.0 supports a maximum of eight tributary
circuit packs in the main transport shelf and a maximum of eight tributary
circuit packs on the extension shelf.
4 Order this item if you do not require the extension shelf and you want the
option to install a Metro network element on the bay. This item includes a
bay frame, unequipped control shelf, unequipped main transport shelf, one
environmental control panel, zone 2 bay fixings, all required fixings and
cables for a completely equipped bay. For this configuration, OPTera
Connect DX Release 6.0 supports a maximum of eight tributary circuit
packs in the tributary section of main transport shelf and optionally a
maximum eight tributary circuit packs in universal slots. Some OPTera
Metro network elements can be supported in the bottom of this bay. For
more information, refer to OPTera Metro Connect SDH User Guide,
NTCA69YA.

5 Use a floor loading of 462 kg/m2 (93 lb/ft2) to determine the maximum
permitted weight of a completely loaded bay. A completely loaded OPTera
Connect DX bay weighs approximately 300 kg (652 lb).
6 Use a thermal loading of 4.615 kW/m2 (0.413 kW/ft2) to determine the
maximum thermal dissipation allowed for a completely loaded bay with
forced convection.
7 For any deployment, do not exceed a thermal density of 2.484 kW/m2
(0.222 kW/ft2) in any 0.65 m2 (7.04 ft2) area. The real thermal dissipation
of the bay depends on the type and quantities of units fitted.
8 The bay frame assembly includes standard attachment bolts. Order this
item if you require earthquake zone 4 fixings. One set of earthquake
attachment bolts (Zone 4) contains four bolts.
9 Order this kit to fix the top of the OPTera Connect DX bay to overhead
metalwork. This kit contains two brackets, two washers, and two bolts.
10 You require one bay frame junction kit to connect two adjacent OPTera
Connect DX bay frames together, back to back. This kit contains two
brackets, four washers and four bolts.
11 This ANSI frame accessory kit includes the cable cover kit (NTRU0401)
for 660 mm (26.0 in) wide installations.
12 This ETSI frame accessory kit includes the cable cover kit (NTRU0402)
for 600 mm (23.6 in) wide installations and the ETSI washer kit
(NTRU0413).
13 Order one or two end guards and end panel kits for each bay lineup for
ANSI installation.
14 Order one or two end guards and end panel kits for each bay lineup for
ETSI installation.
15 This kit includes ground bridge loops. Order frame extenders to increase
the height of the bay. Use the NTRU0409 to conform to Telcordia
standards.
16 Order one of this item when you require a label on the top of the bay.
17 Order this item if integrated bonding network (IBN) grounding is required.
18 Order a leveling kit to provide shims to level the OPTera Connect DX bay.
Each kit includes 50 shims of each of the following sizes: 0.79 mm
(0.031 in), 1.58 mm (0.062 in), 3.16 mm (0.125 in) and 6.32 mm
(0.250 in).
19 This item includes one ECP (NTCA85FA), one Plenum, three fans
(NTCA85EA) and all required fixings. Order this item if you:
— installed DX140 switch modules in the main transport shelf and you
are not installing a supplementary network element on the bay
— installed tributary circuit packs with a power dissipation of greater than
65 watts in slots 2, 3, 8, or 9 of the main transport shelf

This item mounts directly below the main transport shelf. For more
information, refer to the OPTera Metro Connect SDH User Guide,
NTCA69YA.
20 Order this kit with an OPTera Connect DX bay for ETSI installations that
are 2200 mm in height. This kit includes one top infill panel.
21 This kit has been replaced with the NTCA89GJ.
22 Order this kit when you require two power feeds (and #2 AWG lugs) to the
bay. This kit includes nine power feed jumpers (NTCA8946) and four #2
AWG lugs (A0868459).
23 Order this kit when you require access to power and control cables through
the floor in an ANSI installation. This kit includes two left power troughs
and two right power troughs.
24 Order this kit when you require access to power and control cables through
the floor in an ETSI installation. This kit includes two left power troughs,
two right power troughs, two left fiber troughs (fiber highways), two right
fiber troughs, and eight plastic push pins.
25 Order this kit when you want to feed the OPTera Connect DX bay with two
power cables from the top of the bay in an ETSI installation. This kit
includes:
— a power termination box containing four terminal blocks and covers
— two double insulated 25 mm2 blue power cables (one meter long)
— two 25 mm2 double insulated black power cables (one meter long)
— 12 No. 4 AWG lugs
— a selection of 35 mm to 120 mm lugs (to terminate power cables larger
than No. 4 AWG on to the terminal blocks)
— four M8 nuts, four M8 bolts
26 Order this kit when you want to feed the OPTera Connect DX bay with two
power cables from the bottom of the bay in an ETSI installation. This kit
includes:
— four terminal blocks and covers
— two power terminal end stops
— a DIN rail
— two brackets to mount the DIN rail to the bay
— two double insulated 25 mm2 blue power cable (three meters long)
— two double insulated 25 mm2 black power cable (three meters long)
— 12 No. 4 AWG lugs
— a selection of 35 mm to 95 mm lugs (to terminate power cables larger
than No. 4 AWG on to the terminal blocks).

— four M6 bolts (to fix the DIN rail to the bay)

— two M6 nuts and two M6 washers (to fix the DIN rail to the bay)
27 Order this kit to dress coaxial and fiber cables on the OPTera Connect DX
bay in an ETSI installation if you are installing Quad STM-1e circuit
packs. You can also use this kit with a maximum of two HD STM-1e
circuit packs per quadrant, provided that there are no Quad STM-1e circuit
packs in the same quadrant. This kit includes:
— left and right coaxial feeder lanes
— Quad coaxial troughs
— coaxial cable covers
— one kickplate
bay in an ETSI installation if you are installing (or planning to install) more
than two HD STM-1e circuit packs in a quadrant, or a combination of HD
STM-1e and Quad STM-1e circuit packs in the same quadrant. This kit
includes:
— left and right coaxial feeder lanes
— coaxial through
29 Cable covers are not included with this item.
30 Order this kit if you are installing Quad STM-1e circuit packs in the main
transport shelf of OPTera Connect DX bay NTCA91AA/BA, or the main
transport shelf and the tributary extension shelf of OPTera Connect DX bay
NTCA91AB/AC. This kit includes:
— one upper cable trough
— one lower cable trough
— one kickplate
bay in an ETSI installation if you are installing HD STM-1e circuit packs.
This kit includes:
— one upper cable trough (HEX)
— one lower cable through (HEX)
— one kickplate
32 The NTCA91AA/AB/AC/BA mechanical bay assembly includes this
item.
33 The NTCA91BA mechanical bay assembly includes this item. Order this
item as replacement for the NTCA91BA bay only. This item does not
include the fan modules.
34 Order this item as a spare or replacement only.

35 The control shelf includes the following:

— 48 V dc input power connectors
— UniSATT (Connection panel for external synchronization, alarms and
telemetry)
— LCAP (RS-232 terminal connection, alarm lamps and buttons)
— backplane and mechanical housing for the power, control and interface
circuit packs
36 The NTCA91AB/AC mechanical bay assembly includes this item.
STM-64 T/R interface circuit packs
You must install STM-64 T/R transport interface circuit packs according to the
required network configuration and type of switch modules equipped on the
See Table 9-2 on page 9-28 for the G-numbering and shelf slots of the STM-64
T/R interfaces for supported configurations on the OPTera Connect DX
network element.
See Table 9-3 for the ordering codes and ordering rules for the STM-64 T/R
interface circuit packs.
Table 9-2
STM-64 T/R G-numbering and universal slots for supported 10G configurations
Supported Number of STM64 G-numbering and slots

configurations T/R circuit packs (STM-64 T/R circuit packs are installed in the universal slots
required of the main transport shelf only)
Unprotected up to 8 G11/G12 (universal slots 12 and 13) is a group

10 Gbit/s T/R (unprotected G17/G18 (universal slots 16 and 17) is a group
terminal terminals are G0/G10 (universal slots 1 and 11) is a group
provisioned on a G9/G19 (universal slots 10 and 18) is a group
group basis)
10 Gbit/s Linear up to 8 G11/G12 (universal slots 12 and 13) is a Linear 1+1 group
Nx(1+1) terminals (two circuit packs are G17/G18 (universal slots 16 and 17) is a Linear 1+1 group
(where N = 1, 2, 3 required for each G0/G10 (universal slots 1 and 11) is a Linear 1+1 group
or 4) Linear 1+1 terminal) G9/G19 (universal slots 10 and 18) is a Linear 1+1 group


STM-64 T/R G-numbering and universal slots for supported 10G configurations
Supported Number of STM64 G-numbering and slots

configurations T/R circuit packs (STM-64 T/R circuit packs are installed in the universal slots
required of the main transport shelf only)
Nx4-Fiber ADM 8 G11/G12 (universal slots 12 and 13) and G17/G18 (universal
(where N is 1 or 2) (four circuit packs are slots 16 and 17) is a 4-Fiber ADM group
required for each G0/G10 (universal slots 1 and 11) and G9/G19 (universal
4-Fiber ADM) slots 10 and 18) is a 4-Fiber ADM group
Nx2-Fiber ADM up to 8 G11/G12 (universal slots 12 and 13) is a 2-Fiber ADM group
(where N is 1, 2, 3 (two circuit packs are G17/G18 (universal slots 16 and 17) is a 2-Fiber ADM group
or 4) required for each G0/G10 (universal slots 1 and 11) is a 2-Fiber ADM group
2-Fiber ADM) G9/G19 (universal slots 10 and 18) is a 2-Fiber ADM group
Note 1: The DX_HUB network element supports mixed 10 Gbit/s configurations. You cannot mix the
following 10 Gbit/s configurations on the same network element: 2-Fiber Ring and 4-Fiber Ring, Linear
1+1 and 4-Fiber Ring, and Linear 1+1, 4-Fiber Ring and 2-Fiber Ring.
Note 2: When the network element is equipped with DX65 or DX100 switch modules, the network
element supports STM-64 circuit packs in universal slots 12 (G11), 13 (G12), 16 (G17) and 17 (G18)
only.
Note 3: When the network element is equipped with DX140 switch modules, the network element
supports STM-64 circuit packs in universal slots 12 (G11), 13 (G12), 16 (G17), 17 (G18), 1 (G0), 11
(G10), 10 (G9), 18 (G19).
The OPTera Connect DX supports different types of STM-64 T/R transport

interfaces:
• Circuit packs with AM1/AM2 lasers (C-band Grid 1). You can use these
circuit packs in an OPTera Connect DX bay when using multiwavelength
optical repeater (MOR), MOR Plus, or OPTera Long Haul 1600G
amplifiers as your optical link. When operating with MOR or MOR Plus
amplifiers, the AM must be provisioned to AM1. When operating with
OPTera Long Haul 1600G amplifiers, the AM must be provisioned to
AM2.
Note 1: NTCA06MP and NTCA06MQ are both AM1/AM2 provisionable
but they are not part of the C-band wavelength plan. When using these
circuit packs, you cannot use OPTera Long Haul 1600G amplifiers as your
optical link (therefore you must provision these circuit packs as AM1).
Note 2: Some of the wavelengths are not supported by MOR or MOR Plus
amplifiers. See Table 9-3 on page 9-30 for details.
• Circuit packs with only AM2 lasers (L-band Grid 3). You can only use
these circuit packs in an OPTera Connect DX bay when using OPTera Long
Haul 1600G amplifiers as your optical link.
Note: It is recommended that you select circuit packs only from one of
C-band Grid 1, or L-band Grid 3 lasers and not mix the selection. Also it
is recommended to deploy C-band Grid 1 first and then deploy more

wavelengths in the L-band Grid 3. For more information, refer to the

OPTera Long Haul 1600G Amplifier Unidirectional Network Application
Guide, NTY314AG.
• Circuit packs with triple forward error correction (TriFEC). You can use
these circuit packs in an OPTera Connect DX bay running Release 6.0
software. The OPTera Connect DX bay supports mixed TriFEC and
non-TriFEC circuit packs. You can use the TriFEC circuit packs with the
OPTera Long Haul 1600G amplifiers as your optical link. See Table 9-3 on
page 9-30 for details.
Note: When you select a STM-64 T/R circuit pack you must follow the
correct order for the introduction of wavelengths. Select the wavelengths
according to the type of optical fiber and DWDM allocation plan you use.
For information about the wavelengths and about the order of introduction
of wavelengths, refer to the Optical Networks Applications Library,
NTCA66BA or the OPTera Long Haul 1600G Unidirectional Amplifier
Network Application Guide, NTY314AG.
If you require more information on STM-64 10G T/R transport interfaces,

refer to , 323-1511-102.
Table 9-3
STM-64 10G T/R circuit packs

(PEC)
Circuit packs with AM1/AM2 lasers
STM-64 10G T/R 1528.77 nm +/-CHIRP, adapterless NTCA06MP A0805005 1,2,8,10,11,13
STM-64 10G T/R 1529.55 nm +/-CHIRP, adapterless NTCA06MQ A0805028 1,2,8,10,12,13
Circuit packs with AM1/AM2 lasers, C-band Grid 1
STM-64 AM2 10G T/R 1530.33 nm +/- CHIRP NTCA06EP A0805006 1,2,3,8,9,10,13
STM-64 AM2 10G T/R 1531.12 nm +/- CHIRP NTCA06EQ A0805029 1,2,4,8,9,10,13
STM-64 AM2 10G T/R 1531.90 nm +/- CHIRP NTCA06NP A0805007 1,2,3,8,9,10,13
STM-64 AM2 10G T/R 1532.68 nm +/- CHIRP NTCA06NQ A0805030 1,2,4,8,9,10,13
STM-64 AM2 10G T/R 1533.47 nm +/- CHIRP NTCA06FP A0805008 1,2,3,8,9,10,13
STM-64 AM2 10G T/R 1534.25 nm +/- CHIRP NTCA06FQ A0805031 1,2,4,8,9,10,13
STM-64 AM2 10G T/R 1535.04 nm +/- CHIRP NTCA06GP A0805009 1,2,3,8,9,10,13
STM-64 AM2 10G T/R 1535.82 nm +/- CHIRP NTCA06GQ A0805032 1,2,4,8,9,10,13
STM-64 AM2 10G T/R 1536.61 nm +/- CHIRP NTCA06PP A0805010 1,2,3,8,9,10,13



(PEC)
STM-64 AM2 10G T/R 1537.40 nm +/- CHIRP NTCA06PQ A0805033 1,2,4,8,9,10,13
STM-64 AM2 10G T/R 1538.19 nm +/- CHIRP NTCA06QP A0805012 1,2,3,8,9,10,13
STM-64 AM2 10G T/R 1538.98 nm +/- CHIRP NTCA06QQ A0805034 1,2,4,8,9,10,13
STM-64 AM2 10G T/R 1539.77 nm +/- CHIRP NTCA06RP A0805013 1,2,3,8,9,10,13
STM-64 AM2 10G T/R 1540.56 nm +/- CHIRP NTCA06RQ A0805035 1,2,4,8,9,10,13
STM-64 AM2 10G T/R 1541.35 nm +/- CHIRP NTCA06HP A0805014 1,2,3,8,9,10,13
STM-64 AM2 10G T/R 1542.14 nm +/- CHIRP NTCA06HQ A0805036 1,2,5,8,9,10,13
STM-64 AM2 10G T/R 1542.94 nm +/- CHIRP NTCA06SP A0805015
STM-64 AM2 10G T/R 1543.73 nm +/- CHIRP NTCA06SQ A0805038
STM-64 AM2 10G T/R 1544.53 nm +/- CHIRP NTCA06BP A0805016
STM-64 AM2 10G T/R 1545.32 nm +/- CHIRP NTCA06BQ A0805039
STM-64 AM2 10G T/R 1546.12 nm +/- CHIRP NTCA06TP A0805017 1,2,5,7,8,9,10,13
STM-64 AM2 10G T/R 1546.92 nm +/- CHIRP NTCA06TQ A0805040 1,2,5,8,9,10,13
STM-64 AM2 10G T/R 1547.72 nm +/- CHIRP NTCA06UP A0805018 1,2,3,8,9,10,13
STM-64 AM2 10G T/R 1548.52 nm +/- CHIRP NTCA06UQ A0805041 1,2,4,8,9,10,13
STM-64 AM2 10G T/R 1549.32 nm +/- CHIRP NTCA06JP A0805019 1,2,3,8,9,10,13
STM-64 AM2 10G T/R 1550.12 nm +/- CHIRP NTCA06JQ A0805042 1,2,4,8,9,10,13
STM-64 AM2 10G T/R 1550.92 nm +/- CHIRP NTCA06VP A0805020 1,2,3,8,9,10,13
STM-64 AM2 10G T/R 1551.72 nm +/- CHIRP NTCA06VQ A0805043 1,2,4,8,9,10,13
STM-64 AM2 10G T/R 1552.52 nm +/- CHIRP NTCA06KP A0805021 1,2,3,8,9,10,13
STM-64 AM2 10G T/R 1553.33 nm +/- CHIRP NTCA06KQ A0805044 1,2,4,8,9,10,13
STM-64 AM2 10G T/R 1554.13 nm +/- CHIRP NTCA06WP A0805022 1,2,3,8,9,10,13
STM-64 AM2 10G T/R 1554.94 nm +/- CHIRP NTCA06WQ A0805045 1,2,4,8,9,10,13
STM-64 AM2 10G T/R 1555.75 nm +/- CHIRP NTCA06XP A0805023 1,2,3,8,9,10,13
STM-64 AM2 10G T/R 1556.56 nm +/- CHIRP NTCA06XQ A0805046 1,2,4,8,9,10,13
STM-64 AM2 10G T/R 1557.36 nm +/- CHIRP NTCA06LP A0805024 1,2,3,8,9,10,13
STM-64 AM2 10G T/R 1558.17 nm +/- CHIRP NTCA06LQ A0805047 1,2,4,8,9,10,13



(PEC)
STM-64 AM2 10G T/R 1558.98 nm +/- CHIRP NTCA06YP A0805025 1,2,3,8,9,10,13
STM-64 AM2 10G T/R 1559.79 nm +/- CHIRP NTCA06YQ A0805048 1,2,4,8,9,10,13
STM-64 AM2 10G T/R 1560.61 nm +/- CHIRP NTCA06ZP A0805026 1,2,3,8,9,10,13
STM-64 AM2 10G T/R 1561.42 nm +/- CHIRP NTCA06ZQ A0805049 1,2,5,8,9,10,13
STM-64 AM2 10G T/R 1562.23 nm +/- CHIRP NTCA06CP A0805027
Circuit packs with AM2 lasers, L-band Grid 3
STM-64 AM2 10G T/R 1570.42 nm +/-CHIRP NTCA06NT A0815525 1,2,6,8,9,10,13
STM-64 AM2 10G T/R 1571.24 nm +/-CHIRP NTCA06NU A0815523
STM-64 AM2 10G T/R 1572.06 nm +/-CHIRP NTCA06FT A0815521
STM-64 AM2 10G T/R 1572.89 nm +/-CHIRP NTCA06FU A0815519
STM-64 AM2 10G T/R 1573.71 nm +/-CHIRP NTCA06GT A0815517 1,2,6,8,9,10,13
STM-64 AM2 10G T/R 1574.54 nm +/-CHIRP NTCA06GU A0815458
STM-64 AM2 10G T/R 1575.37 nm +/-CHIRP NTCA06PT A0815456
STM-64 AM2 10G T/R 1576.20 nm +/-CHIRP NTCA06PU A0815454
STM-64 AM2 10G T/R 1577.03 nm +/-CHIRP NTCA06QT A0815452
STM-64 AM2 10G T/R 1577.86 nm +/-CHIRP NTCA06QU A0815450
STM-64 AM2 10G T/R 1578.69 nm +/-CHIRP NTCA06RT A0815448
STM-64 AM2 10G T/R 1579.52 nm +/-CHIRP NTCA06RU A0815446
STM-64 AM2 10G T/R 1580.35 nm +/-CHIRP NTCA06HT A0815443
STM-64 AM2 10G T/R 1581.18 nm +/-CHIRP NTCA06HU A0815441
STM-64 AM2 10G T/R 1582.02 nm +/-CHIRP NTCA06ST A0815439
STM-64 AM2 10G T/R 1582.85 nm +/-CHIRP NTCA06SU A0815437
STM-64 AM2 10G T/R 1583.69 nm +/-CHIRP NTCA06BT A0815434
STM-64 AM2 10G T/R 1584.53 nm +/-CHIRP NTCA06BU A0815432
STM-64 AM2 10G T/R 1585.37 nm +/-CHIRP NTCA06TT A0815430
STM-64 AM2 10G T/R 1586.20 nm +/-CHIRP NTCA06TU A0815428
STM-64 AM2 10G T/R 1587.04 nm +/-CHIRP NTCA06UT A0815426 1,2,6,,9,10,13



(PEC)
STM-64 AM2 10G T/R 1587.88 nm +/-CHIRP NTCA06UU A0815424 1,2,6,8,9,10,13
STM-64 AM2 10G T/R 1588.73 nm +/-CHIRP NTCA06JT A0815421
STM-64 AM2 10G T/R 1589.57 nm +/-CHIRP NTCA06JU A0815419
STM-64 AM2 10G T/R 1590.41 nm +/-CHIRP NTCA06VT A0815417
STM-64 AM2 10G T/R 1591.26 nm +/-CHIRP NTCA06VU A0815415
STM-64 AM2 10G T/R 1592.10 nm +/-CHIRP NTCA06KT A0815413
STM-64 AM2 10G T/R 1592.95 nm +/-CHIRP NTCA06KU A0815410
STM-64 AM2 10G T/R 1593.79 nm +/-CHIRP NTCA06WT A0815381
STM-64 AM2 10G T/R 1594.64 nm +/-CHIRP NTCA06WU A0815379
STM-64 AM2 10G T/R 1595.49 nm +/-CHIRP NTCA06XT A0815350
STM-64 AM2 10G T/R 1596.34 nm +/-CHIRP NTCA06XU A0815348 1,2,6,8,9,10,13
STM-64 AM2 10G T/R 1597.19 nm +/-CHIRP NTCA06LT A0815346
STM-64 AM2 10G T/R 1598.04 nm +/-CHIRP NTCA06LU A0815344
STM-64 AM2 10G T/R 1598.89 nm +/-CHIRP NTCA06YT A0815342
STM-64 AM2 10G T/R 1599.75 nm +/-CHIRP NTCA06YU A0815340
STM-64 AM2 10G T/R 1600.60 nm +/-CHIRP NTCA06ZT A0815338
STM-64 AM2 10G T/R 1601.46 nm +/-CHIRP NTCA06ZU A0815336
STM-64 AM2 10G T/R 1602.31 nm +/-CHIRP NTCA06CT A0815334
STM-64 AM2 10G T/R 1603.17 nm +/-CHIRP NTCA06CU A0815332
Circuit packs with AM1/AM2 lasers regular TriFEC, C-band Grid 1
STM-64 AM2 10G T/R TriFEC 1528.77 nm +/- CHIRP NTCF06MP A0827034 1,2,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1529.55 nm +/-CHIRP NTCF06MQ A0827033
STM-64 AM2 10G T/R TriFEC 1530.33 nm +/- CHIRP NTCF06EP A0827032 1,2,3,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1531.12 nm +/- CHIRP NTCF06EQ A0827030 1,2,4,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1531.90 nm +/- CHIRP NTCF06NP A0827026 1,2,3,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1532.68 nm +/- CHIRP NTCF06NQ A0827024 1,2,4,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1533.47 nm +/- CHIRP NTCF06FP A0827020 1,2,3,8,9,10,13



(PEC)
STM-64 AM2 10G T/R TriFEC 1534.25 nm +/- CHIRP NTCF06FQ A0827016 1,2,4,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1535.04 nm +/- CHIRP NTCF06GP A0826996 1,2,3,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1535.82 nm +/- CHIRP NTCF06GQ A0826993 1,2,4,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1536.61 nm +/- CHIRP NTCF06PP A0826990 1,2,3,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1537.40 nm +/- CHIRP NTCF06PQ A0826987 1,2,4,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1538.19 nm +/- CHIRP NTCF06QP A0826985 1,2,3,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1538.98 nm +/- CHIRP NTCF06QQ A0826981 1,2,4,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1539.77 nm +/- CHIRP NTCF06RP A0826979 1,2,3,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1540.56 nm +/- CHIRP NTCF06RQ A0826977 1,2,4,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1541.35 nm +/- CHIRP NTCF06HP A0826975 1,2,3,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1542.14 nm +/- CHIRP NTCF06HQ A0826973 1,2,5,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1542.94 nm +/- CHIRP NTCF06SP A0826970
STM-64 AM2 10G T/R TriFEC 1543.73 nm +/- CHIRP NTCF06SQ A0826968
STM-64 AM2 10G T/R TriFEC 1544.53 nm +/- CHIRP NTCF06BP A0826966
STM-64 AM2 10G T/R TriFEC 1545.32 nm +/- CHIRP NTCF06BQ A0826964
STM-64 AM2 10G T/R TriFEC 1546.12 nm +/- CHIRP NTCF06TP A0826962 1,2,5,7,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1546.92 nm +/- CHIRP NTCF06TQ A0826956 1,2,5,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1547.72 nm +/- CHIRP NTCF06UP A0826954
STM-64 AM2 10G T/R TriFEC 1548.52 nm +/- CHIRP NTCF06UQ A0826952
STM-64 AM2 10G T/R TriFEC 1549.32 nm +/- CHIRP NTCF06JP A0826950
STM-64 AM2 10G T/R TriFEC 1550.12 nm +/- CHIRP NTCF06JQ A0826790
STM-64 AM2 10G T/R TriFEC 1550.92 nm +/- CHIRP NTCF06VP A0826788
STM-64 AM2 10G T/R TriFEC 1551.72 nm +/- CHIRP NTCF06VQ A0826786



(PEC)
STM-64 AM2 10G T/R TriFEC 1552.52 nm +/- CHIRP NTCF06KP A0826784 1,2,5,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1553.33 nm +/- CHIRP NTCF06KQ A0826782
STM-64 AM2 10G T/R TriFEC 1554.13 nm +/- CHIRP NTCF06WP A0826780
STM-64 AM2 10G T/R TriFEC 1554.94 nm +/- CHIRP NTCF06WQ A0826778
STM-64 AM2 10G T/R TriFEC 1555.75 nm +/- CHIRP NTCF06XP A0826773
STM-64 AM2 10G T/R TriFEC 1556.56 nm +/- CHIRP NTCF06XQ A0826771
STM-64 AM2 10G T/R TriFEC 1557.36 nm +/- CHIRP NTCF06LP A0826768
STM-64 AM2 10G T/R TriFEC 1558.17 nm +/- CHIRP NTCF06LQ A0826765
STM-64 AM2 10G T/R TriFEC 1558.98 nm +/- CHIRP NTCF06YP A0826763
STM-64 AM2 10G T/R TriFEC 1559.79 nm +/- CHIRP NTCF06YQ A0826760
STM-64 AM2 10G T/R TriFEC 1560.61 nm +/- CHIRP NTCF06ZP A0826758
STM-64 AM2 10G T/R TriFEC 1561.42 nm +/- CHIRP NTCF06ZQ A0826756
STM-64 AM2 10G T/R TriFEC 1562.23 nm +/- CHIRP NTCF06CP A0826751
Circuit packs with AM2 regular TriFEC, L-band Grid 3
STM-64 AM2 10G T/R TriFEC 1570.42 nm +/-CHIRP NTCF06NT A0826729 1,2,6,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1571.24 nm +/-CHIRP NTCF06NU A0826727
STM-64 AM2 10G T/R TriFEC 1572.06 nm +/-CHIRP NTCF06FT A0826725
STM-64 AM2 10G T/R TriFEC 1572.89 nm +/-CHIRP NTCF06FU A0826723
STM-64 AM2 10G T/R TriFEC 1573.71 nm +/-CHIRP NTCF06GT A0826721
STM-64 AM2 10G T/R TriFEC 1574.54 nm +/-CHIRP NTCF06GU A0826719
STM-64 AM2 10G T/R TriFEC 1575.37 nm +/-CHIRP NTCF06PT A0826717
STM-64 AM2 10G T/R TriFEC 1576.20 nm +/-CHIRP NTCF06PU A0826714
STM-64 AM2 10G T/R TriFEC 1577.03 nm +/-CHIRP NTCF06QT A0826710
STM-64 AM2 10G T/R TriFEC 1577.86 nm +/-CHIRP NTCF06QU A0826708
STM-64 AM2 10G T/R TriFEC 1578.69 nm +/-CHIRP NTCF06RT A0826706



(PEC)
STM-64 AM2 10G T/R TriFEC 1579.52 nm +/-CHIRP NTCF06RU A0826704 1,2,6,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1580.35 nm +/-CHIRP NTCF06HT A0826702
STM-64 AM2 10G T/R TriFEC 1581.18 nm +/-CHIRP NTCF06HU A0826700
STM-64 AM2 10G T/R TriFEC 1582.02 nm +/-CHIRP NTCF06ST A0826697
STM-64 AM2 10G T/R TriFEC 1582.85 nm +/-CHIRP NTCF06SU A0826695
STM-64 AM2 10G T/R TriFEC 1583.69 nm +/-CHIRP NTCF06BT A0826693
STM-64 AM2 10G T/R TriFEC 1584.53 nm +/-CHIRP NTCF06BU A0826691
STM-64 AM2 10G T/R TriFEC 1585.37 nm +/-CHIRP NTCF06TT A0826687
STM-64 AM2 10G T/R TriFEC 1586.20 nm +/-CHIRP NTCF06TU A0826685
STM-64 AM2 10G T/R TriFEC 1587.04 nm +/-CHIRP NTCF06UT A0826670
STM-64 AM2 10G T/R TriFEC 1587.88 nm +/-CHIRP NTCF06UU A0826668
STM-64 AM2 10G T/R TriFEC 1588.73 nm +/-CHIRP NTCF06JT A0826666
STM-64 AM2 10G T/R TriFEC 1589.57 nm +/-CHIRP NTCF06JU A0826664
STM-64 AM2 10G T/R TriFEC 1590.41 nm +/-CHIRP NTCF06VT A0826662
STM-64 AM2 10G T/R TriFEC 1591.26 nm +/-CHIRP NTCF06VU A0826660 1,2,6,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1592.10 nm +/-CHIRP NTCF06KT A0826658
STM-64 AM2 10G T/R TriFEC 1592.95 nm +/-CHIRP NTCF06KU A0826656
STM-64 AM2 10G T/R TriFEC 1593.79 nm +/-CHIRP NTCF06WT A0826652
STM-64 AM2 10G T/R TriFEC 1594.64 nm +/-CHIRP NTCF06WU A0826650
STM-64 AM2 10G T/R TriFEC 1595.49 nm +/-CHIRP NTCF06XT A0826647
STM-64 AM2 10G T/R TriFEC 1596.34 nm +/-CHIRP NTCF06XU A0826645
STM-64 AM2 10G T/R TriFEC 1597.19 nm +/-CHIRP NTCF06LT A0826642
STM-64 AM2 10G T/R TriFEC 1598.04 nm +/-CHIRP NTCF06LU A0826639
STM-64 AM2 10G T/R TriFEC 1598.89 nm +/-CHIRP NTCF06YT A0826635
STM-64 AM2 10G T/R TriFEC 1599.75 nm +/-CHIRP NTCF06YU A0826632
STM-64 AM2 10G T/R TriFEC 1600.60 nm +/-CHIRP NTCF06ZT A0826630
STM-64 AM2 10G T/R TriFEC 1601.46 nm +/-CHIRP NTCF06ZU A0826628



(PEC)
STM-64 AM2 10G T/R TriFEC 1602.31 nm +/-CHIRP NTCF06CT A0826625 1,2,6,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1603.17 nm +/-CHIRP NTCF06CU A0826621
STM-64 AM2 10G T/R TriFEC 1601.88 nm +/-CHIRP NTCF06YV A0826627 1,2,6,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1602.74 nm +/-CHIRP NTCF06YW A0826624
Legend:
PEC = Product Engineering Code (Nortel Network customer order code)
CPC = Common Product Code (Nortel Network internal order code)
AM = Analog maintenance
T/R = Transmit/Receive
TriFEC = Triple Forward Error Correction
Ordering rules for STM-64 10G T/R circuit packs

1 Install STM-64 10G T/R circuit packs according to the network
configurations. Refer to Table 9-2 on page 9-28 for supported network
configurations and slot numbers.
2 This circuit pack supports both positive chirp and negative chirp. You can
select the chirp. Use these rules to select the chirp polarity:
Fiber type Net link dispersion Required transmitter
(see Note 1) chirp
NDSF (see Note 2) positive negative
DSF positive or negative (see Note 3)

(see Note 3 and Note
4)
SMF-LS negative positive

(λ0 > 1560 nm) (see Note 5)

Fiber type Net link dispersion Required transmitter

(see Note 1) chirp
TrueWave positive negative

(λ0 < 1530 nm) (see Note 6)
Note 1: λ0 is the zero dispersion wavelength (wavelength at which the fiber’s

dispersion is zero).
Note 2: For NDSF fiber, the dispersion in the window is normally 17 ps/nm x km
(varies as a function of signal wavelength, fiber slope and λ0).
Note 3: Standard DSF fiber has a λ0 of 1557.5 ± 12.5 nm. For a transmitter at
1533 ± 2.5 nm, the dispersion in the optical fiber is always negative. For a
transmitter at 1557 ± 2.5 nm the dispersion can be positive or negative. The
dispersion slope of DSF fiber is normally about 0.08 ps/nm x km2. The dispersion
slope varies as a function of signal wavelength, fiber slope and λ0.
Note 4: Use the fiber manufacturer’s data to determine the sign of dispersion
for the system at the signal wavelength (λσ) used.
Note 5: SMF-LS fiber has a λ0 > 1560 nm. Dispersion for a transmitter at
1557 nm or 1533 nm is negative.
Note 6: TrueWave fiber has a λ0 < 1530 nm. Dispersion for a transmitter at
1557 nm or 1533 nm is positive.
Legend:
NDSF = Non-dispersion-shifted fiber
DSF = Dispersion-shifted fiber
3 This circuit pack uses a transmitter with provisionable AM1 or AM2 dither
patterns. Use this circuit pack in conjunction with DWDM couplers and
MOR amplifiers, MOR Plus amplifiers, or OPTera Long Haul 1600G
amplifiers.
MOR Plus amplifiers, or OPTera Long Haul 1600G amplifiers.
OPTera Long Haul 1600G amplifiers only.
6 This circuit pack uses a transmitter with AM2 dither patterns. Use this
circuit pack in conjunction with DWDM couplers and OPTera Long Haul
1600G amplifiers only.
7 Nortel has selected this transmitter to be the spare wavelength for the
C-Band Grid 1 wavelengths. For more information about the DWDM
wavelength allocation plan, refer to the OPTera Long Haul 1600G
Amplifier Unidirectional Network Application Guide, NTY314AG.

8 Order two optical connector adapters of the required type for this circuit
pack. See Table 9-8 on page 9-49 to choose the kits that suit the connectors
you require. For high-speed optical fiber links, it is recommended that you
use SC-tuned or FC-tuned connectors. SC and FC connectors provide
better performance than ST connectors.
9 When you select a STM-64 10G T/R circuit pack you must follow the
correct order for the introduction of wavelengths. Select the wavelengths
according to the type of optical fiber and DWDM allocation plan you use.
For information about the wavelengths and about the order of introduction
of wavelengths, refer to the Optical Networks Applications Library,
NTCA66BA, or the OPTera Long Haul 1600G Amplifier Unidirectional
Network Application Guide, NTY314AG.
10 Within the restrictions given in the other rules in this list, you can mix
STM-64 10G T/R circuit packs of any wavelength without restriction in an
OPTera Connect DX network element. However, it is recommended that
you select circuit packs from one grid until you finish all the wavelengths
in that grid. Then, you can select wavelengths from the other grids.
MOR, or MOR Plus amplifiers. You cannot use this circuit pack with
OPTera Long Haul 1600G amplifiers.
MOR Plus amplifiers. You cannot use this circuit pack with MOR, or
OPTera Long Haul 1600G amplifiers.
13 A 10G T/R with TriFEC-capable circuit pack can spare any other 10G T/R
circuit pack. A 10G T/R with non-TriFEC-capable circuit packs can only
spare a 10G T/R with TriFEC-capable if the slot was originally
provisioned with a non-TriFEC-capable circuit pack.

STM-64 T/R short, intermediate and long reach interface circuit packs
Use Table 9-4 on page 9-40 to order STM-64 10G T/R short, intermediate and
long reach interface circuit packs.
Table 9-4
STM-64 T/R short, intermediate and long reach interface circuit packs

(PEC)
STM-64 10G T/R short reach 1530-1565 nm NTWR06AB A0847793 1, 4
STM-64 10G T/R long reach 1533 nm NTWR06BA A0825802 2, 4
STM-64 10G T/R long reach 1557 nm NTWR06BB A0825804
STM-64 10G T/R intermediate reach 1550 nm NTWR06CA A0898997 3, 4
Legend:
Ordering rules for STM-64 10G T/R short, intermediate and long reach interface
circuit packs
1 This circuit pack is a non-DWDM transmitter/receiver (T/R). The receiver
is a wide-band receiver that can receive wavelengths from 1290 nm to
1603 nm. The transmitter can transmit wavelengths from 1530 nm to
1565 nm but the central wavelength has been set to 1550 nm. Use this
circuit pack in non-amplified short reach applications.
2 This circuit pack is a non-DWDM transmitter/receiver (T/R). Use this
circuit pack in non-amplified long reach applications.
3 This circuit pack is a non-DWDM transmitter/receiver (T/R). Use this
circuit pack in non-amplified intermediate reach applications.
4 Order two optical connector adapter kits for this circuit packs. See Table
9-8 on page 9-49 to choose the kits that suit the connectors you require. For
high-speed optical fiber links, it is recommended that you use SC-tuned or
FC-tuned connectors. SC and FC connectors provide better performance
than ST connectors.
Switch modules
Two switch modules are required for each OPTera Connect DX network
element to ensure STM-1 connection mappings, and to provide protection of
the STM-64 line, STM-16, STM-4, and STM-1 tributaries. The supported
switch modules are DX65, DX100 and DX140.
Note: The DX65 switch modules do not support the HD STM-1o/e, Dual
STM-16 and Quad STM-16 tributary circuit packs, tributary circuit packs
in the universal shelf or tributary circuit packs in the extension shelf.


N = (8 - (4xP))/2]
M = (8 - (4xP))/2]
— mixed Px4-Fiber Ring and Mx(0:1) [where P is 0 to 2 and M = 8 -
(4xP)]
— mixed Nx2-Fiber Ring and Mx(0:1) [where N is 0 to 4 and M = 8 -
(2xN)]
M = (8 - (2xN))/2].
4,
M is 0 to 4 and K = 8 - 2x(N+M)]
— mixed Linear Nx(1+1) and Mx(0:1) [where N is 0 to 4 and M =
8-(2xN)]
Note 2: Table 2-6 on page 2-31, summarizes the various 10Gbit/s
(NTCA26BA) or DX65switch modules (NTCA26AA) the following
— Nx4-Fiber Ring (N is 1)
— mixed Px4-Fiber Ring and Nx2-Fiber Ring [where P is 0 or 1 and
N = (4 - (4xP))/2]
— mixed Px4-Fiber Ring and Linear Mx(1+1) [where P is 0 or 1 and
M = (4 - (4xP))/2].
M = 4 - (4xP)]


— Nx2-Fiber Ring (N is 1 to 2).
M = 4 - (2xN)]
M = (4 - (2xN))/2].
2, M is 0 to 2 and K = 4 - 2x(N+M)]
— Linear Nx(1+1) (where N is 1 or 2)
M = 4-(2xN)]
10G optical interfaces. Table 2-6 on page 2-31, summarizes the various
10Gbit/s configuration examples supported by the OPTera Connect DX
when equipped with DX140 switch modules.
Note 2: The DX100 or DX140 switch modules also support the

HD STM-1o/e, Dual STM-16, Quad STM-16 or Dual GE tributary circuit
packs in the universal slots.
Install switch modules in a redundant configuration so that the first switch
module is protected by the second one. Table 9-5 on page 9-42 provides the
ordering information and ordering rules for switch modules.
Table 9-5
Switch module circuit pack
Description Order code Rules

(PEC)
DX65 switch module NTCA26AA 1
DX100 switch module NTCA26BA 1, 2, 3, 4
DX140 switch module NTCA26CA 1, 2, 3, 4
Rules for switch module circuit packs

1 You must install two switch modules. Install one switch module in slot 14
of the main transport shelf. Install one switch module in slot 15 of the main
transport shelf. You cannot mix different switch module types within the
same main transport shelf.
2 The DX100 or DX140 switch modules are required to support tributary
circuit packs in the extension shelf.

3 The DX100 or DX140 switch modules are required to support the

HD STM-1o/e, Dual STM-16 or Quad STM-16 tributary circuit packs
4 The DX100 or DX140 switch modules are required to support tributary
Tributary circuit packs

The transmit/receive (T/R) tributary circuit packs must be installed in the
upper section of the main transport shelf. If the network element is equipped
with an extension shelf and DX100 or DX140 switch modules, you can also
install tributary circuit packs in the extension shelf. An OPTera Connect DX
network element can be equipped with the following tributary circuit packs:
• STM-16 T/R
• Dual STM-16 T/R
• Quad STM-16 T/R
• Quad STM-1o/e T/R
• Quad STM-4 T/R
• HD STM-1o/e T/R
• Dual Gigabit Ethernet (GE)
Table 9-6 on page 9-43 shows the ordering information for the tributary circuit
packs.
Table 9-6
Tributary interface circuit packs

(PEC)
STM-16 tributary circuit packs
STM-16 adapterless tributary short reach (1310, univ) NTCA30CK A0760927 1, 2, 3, 4, 5, 6,

7, 8
STM-16 adapterless tributary long reach (1550, univ) NTCA30AN A0537970 1, 2, 3, 4, 5, 6,

8
DWDM STM-16 tributary circuit packs
STM-16 adapterless DWDM tributary (1530.33 nm) NTCA30EK A0760867 1, 2, 3, 4, 6, 10



(PEC)
STM-16 adapterless DWDM tributary (1533.47 nm) NTCA30FK A0760874 1, 2, 3, 4, 9, 10
STM-16 adapterless DWDM tributary (1535.04 nm) NTCA30GK A0760876
STM-16 adapterless DWDM tributary (1541.35 nm) NTCA30HK A0760886
STM-16 adapterless DWDM tributary (1549.32 nm) NTCA30JK A0760903
STM-16 adapterless DWDM tributary (1552.52 nm) NTCA30KK A0760908
STM-16 adapterless DWDM tributary (1557.36 nm) NTCA30LK A0760919
STM-16 adapterless DWDM tributary (1528.77 nm) NTCA30MK A0760864
STM-16 adapterless DWDM tributary (1531.90 nm) NTCA30NK A0760869
STM-16 adapterless DWDM tributary (1536.61 nm) NTCA30PK A0760878
STM-16 adapterless DWDM tributary (1538.19 nm) NTCA30QK A0760881
STM-16 adapterless DWDM tributary (1539.77 nm) NTCA30RK A0760884
STM-16 adapterless DWDM tributary (1547.72 nm) NTCA30UK A0760902
STM-16 adapterless DWDM tributary (1550.92 nm) NTCA30VK A0760906
STM-16 adapterless DWDM tributary (1554.13 nm) NTCA30WK A0760911
STM-16 adapterless DWDM tributary (1555.75 nm) NTCA30XK A0760913
STM-16 adapterless DWDM tributary (1558.98 nm) NTCA30YK A0760921
STM-16 adapterless DWDM tributary (1550.61 nm) NTCA30ZK A0760924
Dual STM-16 tributary circuit packs
Dual STM-16 adapterless tributary short reach (SR) (1310, NTWR30AA A0859720 1, 2, 4, 5, 8, 11,
univ) 22
Dual STM-16 adapterless tributary intermediate reach (IR) NTWR30BA A0892627 1, 2, 4, 8, 11,
(1310, univ) 12, 22
Dual STM-16 adapterless tributary long reach (LR) (1310, NTWR30CA A0888047 1, 2, 4, 11, 13,
univ) 14, 22
Quad STM-16 tributary circuit packs
Quad STM-16 tributary T/R SR (1310, SC) NTWR31AB A0998622 1, 2, 4, 5, 8, 22,

29
Quad STM-16 tributary T/R IR (1310, SC) NTWR31BA A0505125 1, 2, 4, 8, 12,

22, 29



(PEC)
Quad STM-4 tributary circuit packs
Quad STM-4 Quad tributary T/R w/1 RS DCC (1310, FC) NTCA36BA A0802096 1, 3, 4, 8, 15
Quad STM-4 Quad tributary T/R w/1 RS DCC (1310, ST) NTCA36BB A0802097 1, 3, 4, 8, 16
Quad STM-4 Quad tributary T/R w/1 RS DCC (1310, SC) NTCA36BC A0733133 1, 3, 4, 8, 17
Quad STM-4 Quad tributary T/R w/4 RS DCC (1310, FC) NTCA36CA A0848730 1, 3, 4, 8, 15,
18
Quad STM-4 Quad tributary T/R w/4 RS DCC (1310, SC) NTCA36CC A0848733 1, 3, 4, 8, 17,
18
Quad STM-1o tributary circuit packs
Quad STM-1 Quad tributary T/R w/1 RS DCC (1310, FC) NTCA33BA A0802094 1, 3, 4, 8, 15
Quad STM-1 Quad tributary T/R w/1 RS DCC (1310, ST) NTCA33BB A0802095 1, 3, 4, 8, 16
Quad STM-1 Quad tributary T/R w/1 RS DCC (1310, SC) NTCA33BC A0737002 1, 3, 4, 8, 17
Quad STM-1 Quad tributary T/R w/4 RS DCC (1310, FC) NTCA33CA A0848734 1, 3, 4, 8, 15,
18
Quad STM-1 Quad tributary T/R w/4 RS DCC (1310, SC) NTCA33CC A0848736 1, 3, 4, 8, 17,
18
Quad STM-1e tributary circuit pack
Quad STM-1e tributary T/R NTCE37AA A0762740 1, 3, 4, 19, 20,

21
HD STM-1o tributary circuit packs
HD STM-1o tributary T/R (1310, MPO), with 16 RS DCC NTCA35AB A0877945 1, 3, 4, 22, 23,
channels 28
HD STM-1e tributary circuit pack
HD STM-1e tributary T/R with 16 RS DCC channels NTCE35AB A0877946 1, 3, 4, 19, 24,
25, 28
Gigabit Ethernet tributary circuit pack
Dual Gigabit Ethernet tributary T/R extended reach NTCA90GA A0520861 1, 3, 26



(PEC)
Dual Gigabit Ethernet tributary T/R long reach NTCA90CA A0821217 1, 3, 26
Dual Gigabit Ethernet tributary T/R short reach NTCA90EA A0893722 1, 3, 26, 27
Legend:
Ordering rules for T/R tributary circuit packs

1 You must install a filler card (NTCA49AA) in any slot where you do not
install an active circuit pack.
2 This circuit pack is adapterless. You require one adapter kit for each optical
port on an adapterless optical circuit pack (i.e. one for the Transmit and on
for the Receive port). See Table 9-8 on page 9-49 to choose the kits that
suit the connectors you require. For high-speed optical fiber links, it is
recommended that you use SC-tuned connectors. SC connectors provide
better performance than FC or ST connectors.
3 You can install this circuit pack in slots 2 to 9 only of the main transport
shelf and the extension shelf. However, the network element must be
equipped with DX100 or DX140 switch module when the circuit packs are
installed in the extension shelf.
4 You can install tributary circuit packs separately (unprotected) or as pairs
(protected). You can install this circuit pack in 1+1 (1*1 for matched
nodes) for a protection pairs. You can also install Quad STM-4, STM-16,
or Dual STM-16 tributary circuit packs for SNCP Ring application and
STM-16, Dual STM-16, or Quad STM-16 tributary circuit packs for
2-Fiber MS-SPRing application.
You can install any combination of tributary circuit packs up to a
maximum payload.
5 This circuit pack is for short-reach use only. Do not use this circuit pack in
amplified spans.
6 Use these circuit packs for OPTera Connect DX Release 6.0. The
manufacture of NTCA30KA/KC is discontinued and is replaced with
NTCA30EK. The manufacture of NTCA30LA/LC is discontinued and
replaced with NTCA30CK.
7 Versions 1 and 2 of this circuit pack do not support sub-network
connection protection (SNCP) ring path signal fail.
8 This circuit pack operates as a Class 1 laser device (IEC hazard level 1).

9 Use these circuit packs for OPTera Connect DX Release 6.0. The
manufacture of NTCA30AK is discontinued and replaced with these
circuit packs.
10 This circuit pack is for DWDM applications. This circuit pack can be used
in single-span, non-amplified configurations only. Refer to OC-48 DWDM
Tributary Application Note, NTRR12AC (OC 99-176) for information
about STM-16 DWDM tributary applications.
Note: Although this guide refers to OC-48 DWDM tributaries, the same
circuit packs are used for STM-16 DWDM tributaries and the same
guidelines can be followed.
11 This circuit pack is supported in the universal slots or tributary circuit pack
slots of main transport shelf only. This circuit pack is not supported in the
extension shelf.
12 This circuit pack is for use with intermediate reach applications. Do not use
this circuit pack in amplified spans.
13 This circuit pack is for use with long reach applications. Do not use this
circuit pack in amplified spans.
14 This circuit pack operates as a Class IIIb laser device (IEC hazard level 1).
15 This circuit pack has FC connectors. For high-speed optical fiber links, it
is recommended that you use SC-tuned connectors. SC connectors provide
16 This circuit pack has ST connectors. For high-speed optical fiber links, it
17 This circuit pack has SC connectors. For high-speed optical fiber links, it
18 This circuit pack supports four RS DCC in ports 1 through 4 and one MS
DCC in port 1.
19 Order one coax management accessories kit per bay if this circuit pack is
used.
20 Order a coax cable management kit listed in Table 9-1 “ OPTera Connect
DX bays and shelves” in this chapter according to your coax circuit pack
requirements.
21 Because of cable management limitations, you can only equip up to four
Quad STM-1e circuit packs in slots 2 through 9 of the main transport shelf
and up to four Quad STM-1e circuit packs in slots 2 through 9 of the
extension shelf. You can only equip two Quad STM-1e circuit packs in
slots 2 through 5 and two Quad STM-1e circuit packs in slots 6 through 9
on each shelf.

22 You need DX100 or DX140 switch modules to support the HD STM-1o/e,

Dual STM-16 or the Quad STM-16 tributary circuit pack.
23 To support the HD STM-1o T/R tributary circuit packs, you can use:
— external breakout fiber cable assemblies (refer to Table 9-13 on page
9-59) with fiber distribution frame or external fiber patch panels, or
— optical fiber cable assemblies (refer to Table 9-13 on page 9-59) to
connect to an optical breakout panel
24 Because of EMC requirements, you can only equip up to eight
HD STM-1e circuit packs in the OPTera Connect DX bay.
25 You require coax feeder lane kits NTCA91MC and NTCA91MK if you
have:
— more than two HD STM-1e circuit packs equipped in the same
quadrant, or
— two HD STM-1e and two Quad STM-1e circuit packs equipped in the
same quadrant
26 This circuit pack operates in the unprotected mode only.
27 You must order 50/125 micron multimode patchcord optical cables
equipped with a 2.0 mm jacket for this circuit pack. For more information,
refer to “Optical fiber cables for the Dual GE short reach circuit packs” in
this chapter.
28 The HD STM-1o T/R circuit pack (NTCA35AB) and the HD STM-1e T/R
circuit pack (NTCE35AB) support 16 RS DCC channels and intermediate
path performance monitoring (IPPM).
29 This circuit pack is supported in the universal slots of main transport shelf
only.
Filler cards
The filler cards have two distinct purposes in an OPTera Connect DX network
element. In the main transport shelf and the extension shelf, you require filler
cards to ensure proper cooling. In the control shelf, you require filler cards to
protect against electromagnetic interference (EMI) emissions. Table 9-7 on
page 9-48 provides the ordering information for filler cards in an OPTera
Connect DX bay.
Table 9-7
Filler cards
Description Order code (PEC) Rules
Full height filler card NTCA49AA 1
Control shelf filler card (single slot, 1”) NTCA59AA 2

Ordering rules for filler cards

1 This item is mandatory in all unequipped slots of the main transport shelf
and the extension shelf.
2 This item is mandatory in all single-width unequipped slots of the control
shelf.
Optical connector adapter kits
Table 9-8 on page 9-49 lists all the optical connector adapter kits. You must
order the appropriate kit based on the number of optical ports on the
adapterless circuit pack.
Table 9-8
Optical connector adapter kits
Description Order code (PEC) Rules
Optical connector adapter kits for circuit packs with up to three optical ports
Single SC-FC adapter kit NTCC99AA 1, 2, 3, 4, 5
Single SC-ST adapter kit NTCC99AB 1, 2, 3, 4, 5
Single SC-SC adapter kit NTCC99AC 1, 2, 3, 4, 5
Optical connector adapter kits for circuit packs with four optical ports
Single SC-FC adapter kit NTCA99BA 1, 2, 6, 7
Single SC-ST adapter kit NTCA99BB 1, 2, 6, 7
Single SC-SC adapter kit NTCA99BC 1, 2, 6, 7
Ordering rules for optical connector adapter kits

1 This item includes one optical connector adapter. Order one optical
connector adapter kit of the required type for one optical port on an
adapterless circuit pack.
2 Order at least one optical connector adapter kit as a spare for each OPTera
Connect DX network element. Order according to your requirements.
3 This adapter kit is for circuit packs with up to three optical ports.
4 For each pack with 2 optical ports order a quantity of 2 adapter kits
5 For each pack with 3 optical ports order a quantity of 3 adapter kits.
6 This adapter kit is for circuit packs with four optical ports.
7 For each pack with 4 optical ports order a quantity of 4 adapter kits.
Common equipment circuit packs

Table 9-9 on page 9-50 lists the common equipment circuit packs.

Note: For OPTera Connect DX Release 5.0 or higher, the Orderwire

circuit pack is supported on the OPTera Connect DX bay. For Orderwire
information, refer to the SDH Orderwire User Guide, NTCA66DA.
Table 9-9
Common equipment circuit packs
Description Order code (PEC) CPC Rules
Breaker/filter module NTCA40BA A0762739 1
32 Mbyte SC circuit pack NTCA41CA A0681810 2
128 Mbyte MI circuit pack NTCA42BA A0741120 3
1.5 Mbit/s ESI circuit pack NTCA44AA A0628339 4
2 MHz/2 Mbit/s ESI circuit pack NTCE44AA A0622235 4, 5
2 MHz ESI circuit pack NTCE44BA A0758092 4
PT circuit pack NTCA45AA A0628466 6
MX circuit pack NTCA48AA A0628463 7
POPC circuit pack NTCA50BA A0785203 8, 9
POPS circuit pack NTCA51AA A0647458 8, 10
POPS-SSD circuit pack NTCA51AB A0785100
POPI circuit pack NTCA52AA A0647459 8, 11
68 Mbyte OPC flash cartridge NTCA53AA A0653643 12
122 Mbyte OPC flash cartridge NTCA53BA A0741121 13
Orderwire circuit pack NTCA47AA A0657037 14
Legend:
OPC = operations controller
POPS = partitioned OPC storage
POPS-SSD = partitioned OPC storage solid state drive
POPC = partitioned OPC controller
SC = shelf controller
ESI = external synchronisation interface
MI = Maintenance interface
MX = Message transfer
POPI = partitioned OPC interface
PT = Parallel telemetry
Ordering rules for common equipment circuit packs

1 You must install two breaker/filter modules. Install one breaker/filter
module in slot 1 of the control shelf. Install one breaker/filter module in
slot 2 of the control shelf.

2 Order one SC circuit pack for each OPTera Connect DX network element.
Install the SC in slot 6 of the control shelf.
3 You must install one MI circuit pack in slot 9 of the control shelf. The 128
Mbyte MI circuit pack is mandatory on the OPTera Connect DX bay. The
software load must be installed in the MI prior to shipment. This can be
accomplished by ordering a MI unit loaded with an OPTera Connect
Release 6.0 software load (refer to Table 9-19 on page 9-70).
4 You must install two ESI circuit packs. You must install one ESI circuit
pack in slot 7 of the control shelf. You must install one ESI circuit pack in
slot 8 of the control shelf.
5 The ESI circuit pack, NTCE44AA, must be fitted into the control shelf of
a network element with a universal synchronization, alarms, and telemetry
terminations (uniSATT) connector block so that both E1 (2 Mbit/s) and 2
MHz rates are supported. This circuit pack can operate at 2 MHz rate in a
network element with a 2 MHz SATT. This circuit pack cannot operate in
a network element with a 1.5 Mbit/s SATT, unless the network element is
using line timing.
6 The PT circuit packs are optional. You can install zero, 1, or 2 PT circuit
packs. You must install the first PT circuit pack in slot 13. You must install
the second PT circuit pack (if required) in slot 14. If you do not install
circuit packs in these slots, you must install single-width control shelf filler
cards (NTCA59AA).
7 Install two MX circuit packs in the control shelf. Install one MX circuit
pack in slot 10 and one MX circuit pack in slot 11 of the control shelf. The
second MX circuit pack is highly recommended but not mandatory.
8 The OPC is optional. If you install an OPC, then you must install all three
OPC circuit packs. You must install a set of OPC circuit packs in at least
one network element in a span of control. It is recommended that you
install one main and one backup set of OPC circuit packs in each span of
control.
9 The POPC circuit pack fits in slot 5 of the control shelf. If you do not install
a circuit pack in this slot, you must install a single-width control shelf filler
card (NTCA59AA).
10 The POPS circuit pack fits in slots 3 and 4 of the control shelf. Choose
either NTCA51AA or NTCA51AB, depending on your requirements (see
note). If you do not install the POPS circuit pack, you must install two
control shelf filler card (NTCA59AA).
Note 1: The NTCA51AB (POPS-SSD) is based on solid state technology
and is more robust than the NTCA51AA.
Note 2: You can order the OPC storage circuit pack loaded with an OPTera
Connect Release 6.0 software load (refer to Table 9-19 on page 9-70).

11 The POPI circuit pack fits in slot 12 of the control shelf. If you do not
install a circuit pack in this slot, you must install a single-width control
shelf filler card (NTCA59AA).
12 Use this circuit pack ONLY for OPC data backups.
13 Order as required for the OPC. You can order the OPC flash cartridge
loaded with an OPTera Connect Release 6.0 software load (refer to Table
9-19 on page 9-70).
14 The Orderwire circuit pack is optional. If required, order one Orderwire
circuit pack (revision 5 or higher) for each OPTera Connect DX network
element. Install the Orderwire circuit pack in slot 15 of the control shelf.
Miscellaneous items
Table 9-10 on page 9-52 provides a list of all miscellaneous items. Order
according to your requirements.
Table 9-10
Miscellaneous items

(PEC)
Orderwire handset NTCA36AA A0771143 1
Legend:
PEC = Product Engineering Code (Nortel’ customer order code)
CPC = Common Product Code (Nortel’ internal order code)
Ordering rule for miscellaneous items

1 Order this item to allow voice communications between network elements.
Order this item with the Orderwire circuit pack according to your
configuration. Refer to Table 9-9 on page 9-50 for the Orderwire ordering
rules. For Orderwire information, refer to the SDH Orderwire User Guide,
NTCA66DA.
Cables
Optical fiber cables
Optical fiber cables are available in a variety of lengths, and are fitted with FC,
ST or SC connectors. A patch cord has connectors at both ends. A pigtail has
a connector at one end only.
You can order both patch cords and pigtails equipped with miniature variable
optical attenuators (mVOAs). Remember to use:
• optical patch cords and pigtails without mVOAs with transmit interfaces
• patch cords and pigtails with mVOAs only:
— with receive interfaces

— only when the optical link budget is within the maximum receive
optical level allowed for the receive interface
Order optical fiber cables according to your requirements. Table 9-11 on page
9-53 provides ordering information for optical fiber cables without mVOAs.
Table 9-12 on page 9-57 provides ordering information for optical fiber cables
with mVOAs.
Table 9-11
Optical fiber cables without mVOAs

(PEC)
SM optical patchcord 1 ft (FC) A0785133 1, 3
SM optical patchcord 1 m (3.3 ft) (FC) A0704489
SM optical patchcord 3 m (9.9 ft) (FC) A0385575 2, 3
SM optical patchcord 5 m (16.5 ft) (FC) NT7E46GA A0665771



(PEC)
SM optical patchcord 9 m (29.7 ft) (FC) A0704480 2, 3
SM optical patchcord 10 m (33 ft) (FC) NT7E46GB A0665772
SM optical patchcord 15 m (49.5 ft) (FC) NT7E46GC A0665773
SM optical patchcord 20 m (66 ft) (FC) NT7E46GD A0665774
SM optical patchcord 30 m (99 ft) (FC) NT7E46GE A0665775
SM optical patchcord 40m (132 ft) (FC) A0810650



(PEC)
SM optical patchcord 1 ft (SC) A0773231 1, 3
SM optical patchcord 1 m (3.3 ft) (SC) A0704477
SM optical patchcord 3 m (9.9 ft) (SC) A0773873 2, 3
SM optical patchcord 5 m (16.5 ft) (SC) NT7E46HA A0665776
SM optical patchcord 10 m (33 ft) (SC) NT7E46HB A0665777
SM optical patchcord 15 m (49.5 ft) (SC) NT7E46HC A0665778
SM optical patchcord 20 m (66 ft) (SC) NT7E46HD A0665778
SM optical patchcord 30 m (99 ft) (SC) NT7E46HE A0665780
SM optical patchcord 35m (115.5 ft) (SC) A0812913
SM optical patchcord 40m (132 ft) (SC) A0812914



(PEC)
SM optical patchcord 5 m (16.5 ft) (ST) NT7E46CA A0351090 2, 4
SM optical patchcord 10 m (33 ft) (ST) NT7E46CB A0351100
SM optical patchcord 15 m (49.5 ft) (ST) NT7E46CC A0351101
SM optical patchcord 20 m (66 ft) (ST) NT7E46CD A0351102
SM optical patchcord 30 m (99 ft) (ST) NT7E46CE A0388573
SM optical pigtail 20 m (66 ft) (ST) NT7E48CA A0371187 2, 5
SM optical pigtail 20 m (66 ft) (FC) NT7E48BA A0365308
SM optical pigtail 20 m (66 ft) (SC) NT7E48FA A0408384
Ordering rules for optical fiber cables without mVOAs

1 Use these patch cords for connections between circuit packs and shelves
on the same bay to minimize patchcord slack storage.
2 Use optical patchcords and pigtails without mVOAs with transmit
interfaces. Use optical patchcords without mVOAs with transmit interface
circuit packs and with multiwavelength components that restrict the use of
mVOAs.
3 This optical fiber cable has tuned connectors at both ends. It is
recommended that you use optical fiber cables with tuned connectors on
all OPTera Connect DX high-speed links.
4 The connectors fitted to this optical fiber cable are not tuned. It is
recommended that you do not use this cable on OPTera Connect DX
high-speed links.
5 This optical fiber cable has a connector at one end only. The connector
fitted to this optical fiber cable is not tuned. It is recommended that you do
not use this cable on OPTera Connect DX high-speed links.

Table 9-12
Optical fiber cables equipped with mVOAs

(PEC)
SM optical patchcord with mVOA 5 m (16 ft) (ST) NT7E47EA A0379304 1, 3
SM optical patchcord with mVOA 10 m (33 ft) (ST) NT7E47CB A0351096
SM optical patchcord with mVOA 15 m (49 ft) (ST) NT7E47CC A0351097
SM optical patchcord with mVOA 20 m (66 ft) (ST) NT7E47CD A0351098
SM optical patchcord with mVOA 30 m (98 ft) (ST) NT7E47CE A0388576
SM optical patchcord with mVOA 5 m (16 ft) (FC) NT7E47GA A0665781 1, 2
SM optical patchcord with mVOA 10 m (33 ft) (FC) NT7E47GB A0665782
SM optical patchcord with mVOA 15 m (49 ft) (FC) NT7E47GC A0665784
SM optical patchcord with mVOA 20 m (66 ft) (FC) NT7E47GD A0665785
SM optical patchcord with mVOA 30 m (98 ft) (FC) NT7E47GE A0665786
SM optical patchcord with mVOA 5 m (16 ft) (SC) NT7E47HA A0665787
SM optical patchcord with mVOA 10 m (33 ft) (SC) NT7E47HB A0665788
SM optical patchcord with mVOA 15 m (49 ft) (SC) NT7E47HC A0665789
SM optical patchcord with mVOA 20 m (66 ft) (SC) NT7E47HD A0665790
SM optical patchcord with mVOA 30 m (98 ft) (SC) NT7E47HE A0665791
SM optical pigtail with mVOA 20 m (66 ft) (ST) NT7E49CA A0371188 1, 4
SM optical pigtail with mVOA 20 m (66 ft) (FC) NT7E49BA A0365416
SM optical pigtail with mVOA 20 m (66 ft) (SC) NT7E49FA A0408395
Legend:
SM = Single mode
Ordering rules for optical fiber cables with mVOAs

1 Use patchcords and pigtails with mVOAs only with receive interfaces.
Only use patch cords or pigtails with mVOAs when the optical link budget
is within the maximum optical level allowed for the receive interface. Use
optical patchcords without mVOAs with transmit interface circuit packs
and with multiwavelength components that restrict the use of mVOAs.
2 This optical fiber cable has tuned connectors at both ends. It is
recommended that you use optical fiber cables with tuned connectors on
all OPTera Connect DX high-speed links.

3 The connectors fitted to this optical fiber cable are not tuned. It is
recommended that you do not use this cable on OPTera Connect DX
high-speed links.
4 This optical fiber cable has a connector at one end only. The connector
fitted to this optical fiber cable is not tuned. It is recommended that you do
not use this cable on OPTera Connect DX high-speed links.
HD STM-1o optical fiber cable assemblies
Three versions of optical fiber cable assemblies are available for use with the
HD STM-1o circuit packs:
• single mode external optical fiber cable assemblies with a pin-less
Multifiber Push-on (MPO) connector at one end and 8 breakout SC
connectors at the other end
• single mode external optical fiber cable assemblies with a pin-less MPO
connector at one end and 8 breakout FC connectors at the other end
• single mode external optical fiber cable assemblies with a pinned MPO
connector at one end and a pin-less MPO connector at the other end
The optical fiber cable assemblies are available in a variety of lengths. The
optical fiber cable assemblies are designed for applications that require
termination on a fiber distribution frame, an external fiber patch panel, or an
external optical breakout panel.
Note 1: The optical fiber cable assemblies do not include mVOAs.

Note 2: An optical network element access bay (or breakout bay) can be
used to manage optical fibers for the HD STM-1o tributary circuit pack.
The first release of the ADC optical network element access bay has a
width of 26 inches, a height of 7 feet and a depth of 12 inches. This access
bay includes the fiber cable assemblies required to connect to the
HD STM-1o tributary circuit packs. For more information, contact ADC
to obtain ADC specification sheet 1233016 and ADC document Fiber
Breakout Bay Cable Routing Guide, ADCP-90-329.
Order external optical fiber cable assemblies according to your requirements.
Table 9-13 on page 9-59 provides ordering information for these optical fiber
cable assemblies.

Table 9-13

(PEC)
External breakout optical fiber cable assembly NTCA35ZA A0864652 1, 2, 5

(SM, MPO to 8 SC), 2.5 m (8.2 ft)
External breakout optical fiber cable assembly NTCA35YA A0892613

(SM, MPO to 8 SC), 5 m (16.4 ft)
External breakout optical fiber cable assembly NTCA35YB A0892614

(SM, MPO to 8 SC), 7.5 m (24.6 ft)
External breakout optical fiber cable assembly NTCA35ZE A0864667

(SM, MPO to 8 SC), 10 m (33 ft)
External breakout optical fiber cable assembly NTCA35YC A0892615 1, 2, 5

(SM, MPO to 8 SC), 12.5 m (41 ft)
External breakout optical fiber cable assembly NTCA35YD A0892617

(SM, MPO to 8 SC), 15 m (49.2 ft)
External breakout optical fiber cable assembly NTCA35YE A0892618

(SM, MPO to 8 SC), 17.5 m (57.4 ft)
External breakout optical fiber cable assembly NTCA35ZB A0864653

(SM, MPO to 8 SC), 20 m (66 ft)
External breakout optical fiber cable assembly NTCA35YF A0892619

(SM, MPO to 8 SC), 25 m (82 ft)
External breakout optical fiber cable assembly NTCA35YG A0892621

(SM, MPO to 8 SC), 30 m (98.4 ft)
External breakout optical fiber cable assembly NTCA35YH A0892623

(SM, MPO to 8 SC), 40 m (131.4 ft)
External breakout optical fiber cable assembly NTCA35ZC A0864657

(SM, MPO to 8 SC), 50 m (165 ft)
External breakout optical fiber cable assembly NTCA35ZD A0864655

(SM, MPO to 8 SC), 100 m (330 ft)



(PEC)
External breakout optical fiber cable assembly NTCA35ZS A0881286 1, 3, 5

(SM, MPO to 8 FC), 2.5 m (8.2 ft)
External breakout optical fiber cable assembly NTCA35YN A0892624

(SM, MPO to 8 FC), 5 m (16.4 ft)
External breakout optical fiber cable assembly NTCA35YP A0892625

(SM, MPO to 8 FC), 7.5 m (24.6 ft)
External breakout optical fiber cable assembly NTCA35ZT A0881285

(SM, MPO to 8 FC), 10 m (33 ft)
External breakout optical fiber cable assembly NTCA35YQ A0892629

(SM, MPO to 8 FC), 12.5 m (41 ft)
External breakout optical fiber cable assembly NTCA35YR A0892631

(SM, MPO to 8 FC), 15 m (49.2 ft)
External breakout optical fiber cable assembly NTCA35YS A0892690

(SM, MPO to 8 FC), 17.5 m (57.4 ft)
External breakout optical fiber cable assembly NTCA35ZU A0881288

(SM, MPO to 8 FC), 20 m (66 ft)
External breakout optical fiber cable assembly NTCA35YT A0892693 1, 3, 5

(SM, MPO to 8 FC), 25 m (82 ft)
External breakout optical fiber cable assembly NTCA35YU A0892694

(SM, MPO to 8 FC), 30 m (98.4 ft)
External breakout optical fiber cable assembly NTCA35YV A0892698

(SM, MPO to 8 FC), 40 m (131.4 ft)
External breakout optical fiber cable assembly NTCA35ZV A0881289

(SM, MPO to 8 FC), 50 m (165 ft)
External breakout optical fiber cable assembly NTCA35ZW A0881291

(SM, MPO to 8 FC), 100 m (330 ft)



(PEC)
Optical fiber cable assembly (SM, MPO to MPO), NTCA35ZF A0881273 4, 5, 6

1.0 m (3.28 ft)
Optical fiber cable assembly (SM, MPO to MPO), NTCA35ZG A0881274

2.5 m (8.2 ft)
Optical fiber cable assembly (SM, MPO to MPO), NTCA35ZH A0881275

3.0 m (9.84 ft)
Optical fiber cable assembly (SM, MPO to MPO), NTCA35ZJ A0881278

3.5 m (11.48 ft)
Optical fiber cable assembly (SM, MPO to MPO), NTCA35ZK A0881277

4.0 m (13.12 ft)
Optical fiber cable assembly (SM, MPO to MPO), NTCA35ZL A0881280

4.5 m (14.76 ft)
Optical fiber cable assembly (SM, MPO to MPO), NTCA35ZM A0881281

5.0 m (16.4 ft)
Optical fiber cable assembly (SM, MPO to MPO), NTCA35ZN A0892703

7.5 m (24.6 ft)
Optical fiber cable assembly (SM, MPO to MPO), NTCA35ZP A0892701 4, 5, 6

10 m (33 ft)
Optical fiber cable assembly (SM, MPO to MPO), NTCA35ZQ A0892705

12.5 m (41 ft)
Optical fiber cable assembly (SM, MPO to MPO), NTCA35ZR A0892706

15 m (49.2 ft)
Optical fiber cable assembly (SM, MPO to MPO), NTCA35ZX A0892707

17.5 m (57.4 ft)
Optical fiber cable assembly (SM, MPO to MPO), NTCA35ZY A0892708 4, 5, 6

20 m (66 ft)
Optical fiber cable assembly (SM, MPO to MPO), NTCA35YW A0892709

25 m (82 ft)
Optical fiber cable assembly (SM, MPO to MPO), NTCA35YX A0892710

30 m (98.4 ft)
Optical fiber cable assembly (SM, MPO to MPO), NTCA35YY A0892711

40 m (131.4 ft)
Optical fiber cable assembly (SM, MPO to MPO), NTCA35YZ A0892712

50 m (165 ft)

Ordering rules for optical fiber cable assemblies

1 Use this external breakout optical fiber cable assembly for connection
between the HD STM-1o circuit pack and an external fiber distribution
frame or fiber patch panel.
2 The external breakout optical fiber cable assembly has 8 breakout optical
SC connectors at one end and a pin-less MPO connector at the other end.
3 The external breakout optical fiber cable assembly has 8 breakout optical
FC connectors at one end and a pin-less MPO connector at the other end.
4 Use this optical fiber cable assembly for connection between the HD
STM-1o circuit pack and an external optical breakout panel with a pin-less
MPO connector.
5 Order 4 optical fiber cable assembly per HD STM-1o circuit pack.
6 This optical fiber assembly has a pin-less MPO connector at one end and a
pinned MPO connector at the other end. The pin-less MPO connector is the
interface with the HD STM-1o circuit pack. The pinned MPO connector is
to interface with the external optical breakout panel.
Quad STM-1e coaxial cables
The connectors on the Quad STM-1e T/R tributary circuit pack are on one
connector on the faceplate of the circuit pack. A ten meter cable connects the
STM-1e T/R tributary circuit pack to external cables.
The connectors to the customer’s coaxial cables are eight Type 43 coaxial
connectors. A customer connection panel, which mounts externally to the
OPTera Connect DX bay is available.
Table 9-14 on page 9-62 gives the ordering information for the STM-1e
coaxial cable and the customer interface panel. Refer to Table 9-1 “ OPTera
Connect DX bays and shelves” in this chapter to order the appropriate coaxial
cable management kits.
Table 9-14
Quad STM-1e coaxial cable and customer interface panel

(PEC)
STM-1e Quad cable 10 m terminated NTCC90KA A0802855 1, 3, 4
STM-1e BT43 connectors for Quad cable A0860000 2
STM-1e customer connection panel NTCE38AA A0817361 3, 4, 5
Legend:
PEC = Product Engineering Code (Nortel Networks’ customer order code)
CPC = Common Product Code (Nortel Networks’ internal order code)

Ordering rules for the Quad STM-1e coaxial cables

1 You must order this cable to connect a Quad STM-1e T/R tributary
interface (NTCE37AA) to the external coaxial connections. This cable
includes eight BT type 43 connectors.
2 You must order the BT43 connectors and terminate the coaxial cable with
32 bulkhead mounting Type 43 connectors (A0860000). You mount the
Type 43 connectors on your own termination panel, or on the customer
connection panel (NTCE38AA).
3 You must mount the customer connection panel externally to the OPTera
Connect DX bay. You can use the customer connection panel to terminate
the STM-1e Quad cable (NTCC90KA).
4 The NTCC90KA coaxial cables have a loss of 0.27 dBm at 77.76 MHz.
This translates into a 2.7 dB loss for each 10 m length of coaxial cable in
the NTCC90KA cable assembly. To meet the CMI equipment interface
requirements, a maximum budget of 9 dB remains between the Type 43
connectors on the NTCC90KA cable assembly and the customer’s
equipment.
5 You can terminate up to 64 coaxial connectors (connections for up to 8
Quad STM-1e T/R interface circuit packs).
HD STM-1e coaxial cable assembly
The connections on the HD STM-1e T/R tributary interface circuit pack are on
one connector on the faceplate of the circuit pack. There are two types of
HD STM-1e cables: unterminated and terminated.
The unterminated cable assembly includes a 64 position connector (DIN

41651) at one end and 32 unterminated coaxial cables at the other end. You
need 32 BT43 type connectors to terminate the unterminated coaxial cables.
The terminated cable assembly includes a 64 position connector (DIN 41651)
at one end and 32 BT43 type connectors at the other end.
You can terminate the BT43 type connectors on a customer termination panel.
The customer connection panel mounts externally to the OPTera Connect DX
bay.
Table 9-14 gives the ordering information for the HD STM-1e coaxial cables.
Refer to Table 9-1 “ OPTera Connect DX bays and shelves” in this chapter to
order the appropriate coaxial cable management kits.

Table 9-15
HD STM-1e coaxial cable assembly

(PEC)
HD STM-1e coaxial cable assembly 10 m (33 ft) NTCC90KB A0802854 1, 2, 4, 5

unterminated
HD STM-1e coaxial cable assembly 10 m (33 ft) NTCC90KD A0896344 1, 3, 5

terminated
STM-1e BT43 connectors for Quad cable A0860000 4
Legend:
PEC = Product Engineering Code (Nortel Networks’ customer order code)
CPC = Common Product Code (Nortel Networks’ internal order code)
Rules for the HD STM-1e coaxial cables

1 You must order one of either NTCC90KB or NTCC90KD to connect an
HD STM-1e tributary interface (NTCE35AB) to external coaxial
connections on a customer connection panel.
2 This cable assembly is equipped with a 64 position connector (DIN 41651)
at one end and 32 unterminated coaxial cables at the other end.
3 This cable assembly is equipped with a 64 position connector (DIN 41651)
at one end and 32 BT type 43 connectors at the other end.
4 You must order the BT43 connectors and terminate the coaxial cable with
32 bulkhead mounting Type 43 connectors (A0860000). You mount the
Type 43 connectors on your own termination panel, or on the customer
connection panel (NTCE38AA).
5 The NTCC90KB/KD coaxial cables have a loss of 0.27 dBm at 77.76
MHz. This translates into a 2.7 dB loss for each 10 m length of coaxial
cable in the NTCC90KB/KD cable assembly. To meet the CMI equipment
interface requirements, a maximum budget of 10 dB remains between the
Type 43 connectors on the NTCC90KB/KD cable assembly and the
customer’s equipment.

Optical fiber cables for the Dual GE short reach circuit packs
Order these optical fiber cables when you install Dual GE short reach (SX)
circuit packs in the OPTera Connect DX network element. These optical cables
are 50/125 micron multimode patchcords, equipped with a 2.0 mm jacket.
Table 9-16 provides ordering information for these optical fiber cables.
Table 9-16
Optical fiber cables for the Dual GE SX circuit pack
Description CPC Rules
50/125 micron MMF riser cable patchcord 1 m (SC to SC) A0501086 1, 2
50/125 micron MMF riser cable patchcord 2 m (SC to SC) A0501089


50/125 micron MMF riser cable patchcord 1 m (SC to LC) A0501144
50/125 micron MMF riser cable patchcord 13 m (SC to LC) A0501132 1, 2


50/125 micron MMF riser cable patchcord 30 m (SC to LC) A0501103 1, 2
Ordering rules for Dual GE SX optical fiber cables

1 Use this optical cable for connection between the Dual GE SX circuit pack
and the customer termination point.
2 Order four cables for each Dual GE SX circuit pack.
Peripheral cables
Peripheral cables connect external equipment to the local craft access panel
(LCAP), maintenance interface (MI), OPC interface, and parallel telemetry
(PT) circuit packs. Table 9-17 on page 9-67 provides the ordering information
for the peripheral cables.
Note: Starting with OPTera Connect DX Release5, the Orderwire circuit

pack is supported on the OPTera Connect DX bay.
Table 9-17
Peripheral cables

(PEC)
9/25-pin user interface modem access cable 20 m (66 ft) NTCC8930 A0647273 1
25/25-pin user interface modem access cable 0.3 m (1 ft) NTCC90DA A0674756 2
25/25-pin user interface cable 5 m (16 ft) NT7E44FA A0365240 3
25/25-pin user interface cable 20 m (66 ft) NT7E44FB A0465386
9/25-pin user interface cable 5 m (16 ft) NT7E44EA A0365239 5
9/25-pin user interface cable 20 m (66 ft) NT7E44EB A0365485
Null-modem cable adapter 25/25-pin NT7E44MA A0375304 4
Multiple shelf LAN cable 20 m (65 ft) – MI to MI NTCC8927 A0647270 6
Ethernet cable 20m (65 ft) - MI to Ethernet LAN NTCC90BA A0674754 7
Ethernet cable 40m (130 ft) - MI to Ethernet LAN NTCC90BB A0685908
Ethernet cable 20m (65 ft) - MI to X-terminal NTCC90CA A0674755 8
9/25-pin OPC interface to an external modem 20 m (66 ft) NTCC90HA A0681317 9
25/25-pin OPC interface to an external modem 20 m (66 ft) NTCC90EB A0674758 10


Peripheral cables

(PEC)
25/25-pin OPC terminal adapter cable 0.3 m (1 ft) NTCC90GA A0681316 11
9-pin OPC interface to Ethernet LAN 20 m (66 ft) NTCC90BA A0674754 12
44-pin parallel telemetry input cable assembly, stranded NTCC8928 A0647271 13

20 m (66 ft)
44-pin parallel telemetry input cable assembly, solid 20 m NTCC8933 A0666923

(66 ft)
25-pin parallel telemetry output cable assembly, stranded NTCC8934 A0666924 13

20 m (66 ft)
25-pin parallel telemetry output cable assembly, solid 20 m NTCC8929 A0647272

(66 ft)
Legend:
Ordering rules for peripheral cables

1 Order this cable to connect an external modem to the RS-232 user interface
on the maintenance interface.
Order this cable and a null-modem cable adapter (NT7E44MA) to connect
a VT100-compatible terminal or a printer to the RS-232 user interface on
the maintenance interface.
2 Order this cable as an adapter with NTCC90EB to connect the RS-232 user
interface on the LCAP to an external modem.
3 Order this cable to connect a VT100-compatible terminal or a printer to the
RS-232 user interface on the LCAP.
Order this cable and a null-modem cable adapter (NT7E44MA) to connect
a modem to the RS-232 user interface on the LCAP.
4 Order this adapter with NTCC8930, NT7E44FA, and NT7E44FB, if
required.
5 Order this cable to connect a VT100-compatible terminal to the RS-232
interface on the maintenance interface.
6 Order this cable to connect two maintenance interfaces (MI) together for
data communications channel (DCC) bridging applications.
7 Order this cable to connect the MI to the Ethernet LAN.
8 Order this cable to connect an MI to an X-terminal. You can also use this
cable to connect the OPC interface to an X-terminal.

9 Order this cable to connect an external modem to a synchronous RS-232

OPC interface.
10 Order this cable to connect an external modem to an asynchronous RS-232
OPC interface.
11 Order this cable as an adapter with NTCC90EB to connect the OPC
interface to a terminal.
Order this cable as an adapter with NTCC8930 to connect the MI to a
terminal.
12 Order this cable to connect the OPC interface to the Ethernet LAN.
13 Order this cable to connect the telemetry inputs or outputs, when you have
PT circuit packs installed in the bay. It is recommended that you use the
solid wire cables for wire wrap and punchdown applications.
Software
This section provides the information you require to order OPTera Connect
DX network element software.
Software loads
A software load contains all applications, features, and utilities for a specific
OPTera Connect DX software release. In addition to the software load, you
require software licenses (see Table 9-18 on page 9-69 for ordering
information for software loads for OPTera Connect DX Release 4.0 or higher).
Note 1: You cannot order these software loads individually. You must
select the appropriate supply option (which includes the media with the
software load) for your application.
Table 9-18
Software loads for OPTera Connect DX Release 4.0 or higher
Description Order code (PEC) Rule
OPTera Connect DX Release 4.0 software load NTCE60KA 1, 2
OPTera Connect DX Release 4.1 software load NTCE60LA
OPTera Connect DX Release 5.02 software load NTCE60MA 1, 3
OPTera Connect DX Release 5.03 software load NTCE60MB
OPTera Connect DX Release 6.0 software load NTCE60NC
Rules for software load

1 The software load is part of a ten digit software-specific building block
code. Each building block code includes the media that contains the
software load. The software load is available on the following media: 128
Mbyte MI circuit pack (NTCA42BA), 4 mm magnetic tape cartridge

(NT7E24TA), partitioned OPC solid state drive (SSD) storage module

(NTCA51AB), partitioned OPC storage module (NTCA51AA), or 122
Mbyte OPC flash cartridge (NTCA53BA).
2 You can order this item as part of a ten-digit building block ordering code.
For more information, refer to the “Software and documentation” in
chapter 9 in the appropriate version the SDH Planning Guide, NTRR11Dx
for OPTera Connect DX Release 4 and Release 4.1.
3 Refer to Table 9-19 on page 9-70 to select the appropriate supply option
for OPTera Connect DX Release 5 or higher.
.
Table 9-19
OPTera Connect DX Release 6.0 software load - supply options
Description Order code (PEC) Rule
Magnetic tape cartridge (4 mm) loaded with an SCE60NCA6A 1

OPTera Connect DX Release 6.0 software load
Partitioned OPC SSD storage module loaded SCE60NCB1A 2

with an OPTera Connect DX Release 6.0
software load
Partitioned OPC storage module loaded with an SCE60NCA9A 3

MI circuit pack (128 Mbyte) loaded with an SCE60NCA8A 4

OPC flash cartridge (122 Mbyte) loaded with an SCE60NCB3A 5

Ordering rules for supply options

1 This item includes a 4 mm magnetic tape cartridge (NT7E24TA) loaded
with one copy of OPTera Connect DX Release 6.0 software load
(NTCE60NC).
2 This item includes a partitioned OPC solid state drive storage module
(NTCA51AB) loaded with one copy of OPTera Connect DX Release 6.0
software load (NTCE60NC).
3 This item includes a partitioned OPC storage module (NTCA51AA)
loaded with one copy of OPTera Connect DX Release 6.0 software load
(NTCE60NC).
4 This item includes a 128 Mbyte maintenance interface circuit pack
(NTCA42BA) loaded with one copy of OPTera Connect DX Release 6.0
software load (NTCE60NC).
5 This item includes a 122 Mbyte OPC flash cartridge (NTCA53BA) loaded
with one copy of OPTera Connect DX Release 6.0 software load
(NTCE60NC).

Software licenses and certificates

Each application, feature, or utility in a software load has an associated
software license. A software license allows the customer to use the
applications, features, and utilities for one network element. Table 9-20 on
page 9-71 provides the ordering information for software licenses.
Table 9-20

(PEC)
Applications
Application – 10G Linear 1+1 terminal NTCA62AA A0648881 1
Application – 2F MS-SPRing NTCA62AC A0720041
Application – 4F MS-SPRing/Line ADM NTCA62AD A0720042
Application – Metro (non-DWDM) NTCA62AG A0813343
Application – Head-end ring switching NTCA62AH A0825432
Application – 10G unprotected terminal NTCA62FP A0813344
Extended applications
Application – 2nd 4F MS-SPRing/Line ADM NTCA62FN A0813346 2
Application – 2nd 2F MS-SPRing/ NTCA62FO A0813345

10G Linear 1+1/10G unprotected
Utility and features
Utility - MS/RS Performance Monitoring NTCA62EA A0648883 2, 3
Feature - Intermediate Path Performance Monitoring NTCA62FA A0648884
Feature - Forward Error Correction NTCA62FB A0648885
Feature - TL-1 Interface NTCA62BA A0648886
Feature - Optical Trib data communications channel NTCA62FC A0648887

(DCC)
Feature - Extra Traffic NTCA62FD A0720044
Feature - Matched Nodes NTCA62FF A0720046
Feature - Sync Messaging NTCA62FH A0720048
Feature - Local User Interface NTCA62FL A0720051



(PEC)
Feature - Subtending SNCP Ring NTCA62FE A0720045 2, 3
Feature - OPTera Connect DX Feature - Subtending NTCA62FR A0894192

Rings (SNCP / MS-SPRing)
Feature - Strong authentication NTCA62AF A0804186
Upgrade licence
Upgrades to OPTera Connect DX Rel. 6.0 from NTCA60ZZ 2, 4

supported releases
Upgrades to OPTera Connect DX Rel. 6.0 from non NTCA60YY

supported releases
Software certificates
OPTera Connect DX Rel 6.0 Software Certificate NTCA61NC 2, 4
Legend:
ADM = add/drop multiplexer
RS = regenerator section
MS = multiplexer section
Rules for software licenses

1 Order one of this item for the first type of configuration on each OPTera
2 You must order ‘1’ copy of this software license for each OPTera Connect
DX network element.
3 The OPTera Metro Connect (OMC) includes some software licenses as
part of its models (refer to Models on page 9-82). Order “1” copy of any
additional software license for each OPTera Metro Connect network
element.
4 Refer to Upgrade considerations and planning on page 3-1 for list of
supported upgrade paths.
Documentation
This section provides documentation ordering information and a brief
overview of the Nortel Networks technical publication (NTP) libraries and
individual documents that can be ordered for OPTera Connect DX network
element.

NTP libraries
NTP libraries and their supporting documents are available on paper and on
CD-ROM (Interactive version and Helmsman version).
The Interactive CD-ROM is an HTML Java-based application that requires

a web browser (Netscape or Microsoft Internet Explorer) and Sun
Microsystems’ Java plug-in (included on the CD-ROM) on the user’s
machine. The Interactive CD-ROM operates on systems running Microsoft
Windows 95, Windows 98, Windows 2000, Windows NT 4.0 or later with
Service Pack 4 or later, and Windows XP.
The Interactive CD-ROM application licenses a single user to run the

CD-ROM. Currently, the Interactive CD-ROM is not supported on Servers or
UNIX platforms.

The Interactive CD-ROM includes the following key features:

• self-executing
• an interactive graphical interface to the NTP library with the following
navigational aids: menus showing the product platforms and/or release
notes, roadmaps, search and master index buttons
• hypertext links between a master topical index and the entire NTP library
• hypertext-linked references within books, and between books
• A full library search through Adobe Acrobat Search tool from within
books or from a Search button. The search options are: word stemming,
thesaurus, match case, sounds like and proximity.
The Helmsman CD-ROM includes the Helmsman Client application. The
Helmsman Client application is available for the following computers:
• Macintosh (Power Macintosh with Apple System Software 7.6.1 or later)
• PC-compatible (with Microsoft Windows 95, Windows 98, Windows 2000
or Windows NT 4.0 or later with Service Pack 3 or later)
• UNIX (with Solaris 2.5.1 or 2.6; HP-UX 10.20 or later)
The Helmsman Client application licenses a single user to access the
CD-ROM. If the CD-ROM is on a server that allows access to many users, you
must order additional software licenses. The Helmsman Client application
includes the following key features:
• Boolean search logic using terms “AND” and “OR”
• wildcard searching using the asterisk (*) to denote wildcard characters
• thesaurus and synonym support so that a search for an abbreviation will
also locate occurrences of the expanded version of the abbreviation
• word list function provides a list of all words and abbreviations indexed
within a specific library
Table 9-21 on page 9-74 lists the ordering information for NTP libraries on
paper and on CD-ROM.
Table 9-21
NTPs for OPTera Connect DX
Description Order code (PEC)
OPTera Connect DX NTP libraries on paper
OPTera Connect DX Release 6.0 NTPs
OPTera Connect DX6 SDH (universal bay) NTP suite NTCA65JG


OPTera Connect DX5 SDH (universal bay) NTP suite NTCA65JF
TN-64X Release 7.0 NTP suite NTCE65AH
OPTera Connect DX5 SDH (universal bay and TN-64X bay NTCA65KF
combined) NTP suite
OPTera Connect DX4.1 SDH (universal bay) NTP suite NTCA65JE
TN-64X Release 6.1 NTP suite NTCE65AG
OPTera Connect DX4.1 SDH (universal bay and TN-64X bay NTCA65KE
combined) NTP suite
OPTera Connect DX4.0 SDH (universal bay) NTP suite NTCA65JD
TN-64X Release 6.0 NTP suite NTCE65AF
OPTera Connect DX4.0 SDH (universal bay and TN-64X bay NTCA65KD
combined) NTP suite
OPTera Connect DX NTP libraries on CD-ROM
Interactive CD-ROMs
OPTera Connect DX Release 6.0 (SONET and SDH) NTPs NTCA64FG
OPTera Connect DX Release 5.0 (SONET and SDH) NTPs NTCA64FF
OPTera Connect DX Release 4.1 (SONET and SDH) NTPs NTCA64FE
OPTera Connect DX Release 4.0 (SONET and SDH) NTPs NTCA64FD
Helmsman CD-ROMs
OPTera Connect DX Release 6.0 (SONET and SDH) NTPs NTCA64DG
OPTera Connect DX Release 5.0 (SONET and SDH) NTPs NTCA64DF
OPTera Connect DX Release 4.1 (SONET and SDH) NTPs NTCA64DE
OPTera Connect DX Release 4.0 (SONET and SDH) NTPs NTCA64DD
TN-64X Release 7.0 NTPs NTCE64AH
TN-64X Release 6.1 NTPs NTCE64AG
TN-64X Release 6.0 NTPs NTCE64AF
Helmsman viewer application (DOS) additional user license NT7E64MA


Helmsman viewer application (MAC) additional user license NT7E64MB
Helmsman viewer application (UNIX) additional user license NT7E64MC
Legend:
Table 9-22 on page 9-76 lists the documents within the OPTera Connect DX
(universal bay) NTP library (NTCA65JG) .
Note: Guides with their own PECs can also be ordered separately.
Table 9-22
Documents within the OPTera Connect DX NTP library
Description Document code
Volume 1 - Description and Planning
About the OPTera Connect DX SDH NTP library 323-1531-090
SDH Planning Guide NTRR11DG
SDH Orderwire User Guide NTCA66DA
Optical Networks Network Interworking Guide NTCA68CA
Network Interoperability Guide NTCA68CB
Optical Networks Data Communications Planning Guide NTR710AM
Gigabit Ethernet Data User Guide NTCA65YA
Circuit Pack Descriptions 323-1531-102
Ordering Information (OPTera Connect DX only) 323-1531-151

(see Note)
TL1 Interface Description (OPTera Connect DX only) 323-1531-190
Network Element User Interface Description 323-1531-195
OPC User Interface Description 323-1531-196
Volume 2 - Installation, Commissioning and Testing
SDH Network Element Deployment Guide NTCA67DG
Installation Procedures (OPTera Connect DX only) 323-1531-201
Powering-up and Commissioning procedures (OPTera Connect DX only) 323-1531-220


Documents within the OPTera Connect DX NTP library
Description Document code
System Commissioning and Testing Procedures (OPTera Connect DX 323-1531-222

only)
Volume 3 - Operations, Administration and Provisioning
User Interfaces Connection Procedures 323-1531-301
External Interface Configuration Procedures 323-1531-302
Software Administration Procedures 323-1531-302
Data Administration Procedures 323-1531-302
Security Management Procedures 323-1531-302
Provisioning and Operations Procedures (OPTera Connect DX only) 323-1531-310
Protection Switching Description and Procedures (OPTera Connect DX 323-1531-311

only)
Volume 4 - Maintenance
Performance Monitoring Procedures (OPTera Connect DX only) 323-1531-520
Trouble Clearing and Module Replacement (OPTera Connect DX only) 323-1531-543
Log Reference 323-1531-840

Note: Starting with OPTera Connect DX Release 6.0, the ordering information is documented in the OPTera
Connect SDH DX Planning and Ordering Guide (NTRR11DG).
Supporting documentation
Table 9-23 shows the ordering information for supporting documentation that
is available to customers.
Table 9-23
Description Order code CPC

(PEC)
Application Guide for OPTera Connect DX using OPTera Metro NTCA69ZB A0892140
5200 OFA
OC-48 DWDM Tributary Application Note, OC 99-176 (see Note 1) NTRR12AC A0810392
OPTera Connect DX/OPTera Metro 3000 Series Interworking NTRN15AA A0997091

Application Guide
OPTera Long Haul 1600 NTP Library NTCA65EF A0836416
OPTera Metro Connect SDH User Guide NTCA69YA A0876954


Description Order code CPC

(PEC)
Optical Networks Application Library NTCA66BA A0798571
Preside documentation 450-3101-xxx
Network Interworking Application Guide (see Note 2) NTCA68CA A0863652
SDH Low-Speed Cross-Connect Application Guide (see Note 2) NTCA69DC A0876754
Legend:
Note 1: Although this guide refers to OC-48 DWDM tributaries, the same circuit packs are used for
STM-16 DWDM tributaries and the same guidelines can be followed.
Note 2: Starting with OPTera Connect DX Release 4. these guides are integrated into the NTPs.
Change application procedures

Change Application Procedures (CAPs) provide detailed procedures for
software upgrades, software upgrade backouts, hardware upgrades and
network reconfigurations. Table 9-24 on page 9-78 list the ordering
information for software upgrade, software upgrade backouts, hardware
upgrade and network reconfiguration for OPTera Connect DX and TN-64X.
Table 9-24
OPTera Connect DX and TN-64X CAPs
Description CAP code Order code CPC

(PEC)
OPTera Connect DX Release 6.0 CAPs
SDH - Add an ADM to a 4F ring or a 4F ADM chain see Note 1 NTRR61JG A0516588
SDH - Delete an ADM from a 4F ring or a 4F ADM chain see Note 1 NTRR62JG A0516596
SDH - Add an end node to a 4F ADM chain see Note 1 NTRR63JG A0516590
SDH - Delete an end node to a 4F ADM chain see Note 1 see Note 2 see Note 2
SDH - Add an ADM to a 2F Ring see Note 1 NTRR69JG A0516592
SDH - Delete an ADM from a 2F Ring see Note 1 NTRR71JG A0516598
SDH - Convert a 4F ADM chain to a 4F Ring see Note 1 see Note 2 see Note 2
SDH - Move an in-service NE to a new SOC see Note 1 NTRR68JG A0516594
SDH - Add an ADM to a 2F STM-16 Ring see Note 1 see Note 2 see Note 2
SDH - Delete an ADM from a 2F STM-16 Ring see Note 1 see Note 2 see Note 2



(PEC)
SDH - In service tributary rollover see Note 1 NTRR76JG A0516584
SDH - Quad STM-1o/e to HD STM1o/e card conversion see Note 1 NTRR77JG A0516579
SDH - STM-16 to Dual STM-16 card conversion see Note 1 NTRR78JG A0516581
SDH - System software upgrade to DX Rel. 6.00 see Note 1 NTRR21JG A0516570
SDH - Upgrade backout from DX Rel. 6.00 see Note 1 NTRR25JG A0516573
SDH Preside SUM Upgrade backout from Rel. 6.0 see Note 1 NTRR35JG A0516576
OPTera Connect DX Release 5 and TN-64X Release 7.0 CAPs
SDH - Add an ADM to a 4F ring or a 4F ADM chain see Note 1 NTRR61JF A0999942
SDH - Delete an ADM from a 4F ring or a 4F ADM chain see Note 1 see Note 2 see Note 2
SDH - Add an end node to a 4F ADM chain see Note 1 NTRR63JF A0999944
SDH - Delete an end node from a 4F ADM chain see Note 1 see Note 2 see Note 2
SDH - Quad STM4 to STM16 card conversion see Note 1 see Note 2 see Note 2
SDH - Convert a 4F ADM chain to a 4F Ring see Note 1 see Note 2 see Note 2
SDH - Move an in-service NE to a new SOC see Note 1 NTRR68JF A0999946
SDH - Add an ADM to a 2F ring see Note 1 NTRR69JF A0999948
SDH - Delete an ADM from a 2F ring see Note 1 see Note 2 see Note 2
SDH - HH STM-4/STM-16 to Quad STM-4, and Quad STM-4 see Note 1 see Note 2 see Note 2
to STM-16 card conversion
SDH - STM-16 to HD STM-1o card conversion see Note 1 see Note 2 see Note 2
SDH - Quad STM-4 to HD STM-1o card conversion see Note 1 see Note 2 see Note 2
SDH - In service tributary rollover see Note 1 NTRR76JF A0999950
SDH - Quad STM-1o/e to HD STM1o/e card conversion see Note 1 NTRR77JF A0899003
SDH - STM-16 to Dual STM-16 card conversion see Note 1 NTRR78JF A0999954
SDH - System software upgrade to DX Rel. 5.00 see Note 1 NTRR21JF A0999933
SDH - Upgrade backout from DX Rel. 5.00 see Note 1 NTRR25JF A0999936
SDH Preside SUM Upgrade backout from Rel. 5.0 see Note 1 NTRR35JF A0999939
TN-64X - System software upgrade to TN-64X Rel. 7.00 see Note 1 NTRR21KH A0999934
TN-64X - Upgrade backout from TN-64X Rel. 7.00 see Note 1 NTRR25KH A0999937



(PEC)
Preside SUM - TN-64X - Upgrade backout from TN-64X see Note 1 NTRR35KH A0999940
Rel. 7.00
OPTera Connect DX Release 4.1 and TN-64X Release 6.1 CAPs
SDH - Add an ADM to a 4F ring or a 4F ADM chain see Note 1 NTRR61JE A0894563
SDH - Delete an ADM from a 4F ring or a 4F ADM chain see Note 1 NTRR62JE A0894647
SDH - Add an end node to a 4F ADM chain see Note 1 NTRR63JE A0894649
SDH - Delete an end node from a 4F ADM chain see Note 1 NTRR64JE A0894651
SDH - HH STM-4/STM-16 to Quad STM-4, and Quad STM-4 see Note 1 see Note 2 see Note 2
to STM-16 card conversion
SDH - Convert a 4F ADM chain to a 4F Ring see Note 1 NTRR66JE A0894657
SDH - Move an in-service NE to a new SOC see Note 1 NTRR68JE A0894659
SDH - Add an ADM to a 2F ring see Note 1 NTRR69JE A0894661
SDH - Delete an ADM from a 2F ring see Note 1 NTRR71JE A0894663
SDH - STM-16 to HD STM-1o card conversion see Note 1 see Note 2 see Note 2
SDH - Quad STM-4 to HD STM-1o card conversion see Note 1 see Note 2 see Note 2
SDH - QSTM-1o to HD STM1o card conversion see Note 1 see Note 2 see Note 2
SDH - In-service tributary rollover see Note 1 NTRR76JE A0899002
SDH - Quad STM-1o to HD STM-1o card conversion see Note 1 NTRR77JE A0899003
SDH - STM-16 to Dual STM-16 card conversion see Note 1 NTRR78JE A0899007
SDH - Add a backup OPC to a span of control see Note 1 NTRR79JE A0992284
SDH - System software upgrade to DX Rel. 4.12 see Note 1 NTRR21JE A0894577
SDH - Upgrade backout from DX Rel. 4.12 see Note 1 NTRR25JE A0894578
SDH Preside SUM Upgrade backout from Rel. 4.12 see Note 1 NTRR35JE A0894576
TN-64X - System software upgrade to TN-64X Rel. 6.12 see Note 1 NTRR21KG A0894575
TN-64X - Upgrade backout from TN-64X Rel. 6.12 see Note 1 NTRR25KG A0894574
Preside SUM - TN-64X - Upgrade backout from TN-64X see Note 1 NTRR35KG A0894574
Rel. 6.12



(PEC)
OPTera Connect DX Release 4.0 and TN-64X Release 6.0 CAPs
SDH - Add an ADM to a 4FR ring or a ADM chain (midnode) OC 01-125 NTRR61JD A0878876
SDH - Delete a midnode ADM from a 4FRring or ADM chain OC 01-127 NTRR62JD A0878879
SDH - Add an end node to a 4FR ADM chain OC 01-129 NTRR63JD A0878882
SDH - Delete an end node from a 4FR ADM chain OC 01-131 NTRR64JD A0878884
(Available at GA)
SDH - HH STM4/STM-16 to Quad STM4, and Quad STM4 to OC 01-133 NTRR65JD A0878887
STM16 card conversion
SDH - Convert a 4FR ADM chain to a 4FR Ring OC 01-137 NTRR66JD A0878889
(Available at GA)
SDH - Move an in-service NE to a new SOC OC 01-141 NTRR68JD A0878893
SDH - Add an ADM to a 2FR ring OC 01-143 NTRR69JD A0878895
SDH - Delete an ADM from a 2FR ring (Available at GA) OC 01-145 NTRR71JD A0878897
SDH - STM16 to HDSTM1o card conversion OC 01-147 see Note 2 see Note 2
SDH - QSTM4 to HDSTM1o card conversion OC 01-149 see Note 2 see Note 2
SDH - QSTM1o to HDSTM1o card conversion OC 01-153 see Note 2 see Note 2
SDH - In-service Tributary Rollover OC 01-189 NTRR76JD A0878700
SDH - System software upgrade to DX Rel. 4.00 OC 01- 173 NTRR21JD A0878704
SDH - Upgrade backout from DX Rel. 4.00 OC 01-174 NTRR25JD A0878705
TN64X - System software upgrade to TN64X Release 6.00 OC 01-175 NTRR21KF A0878707
(GA)
TN64X - Upgrade backout from TN-64X Rel. 6.00 (GA) OC 01-176 NTRR25KF A0878708
Preside SUM - SDH - Upgrade backout from Rel. 4.00 (GA) OC 01 -186 NTRR35JD A0878706
Preside SUM - TN64X - Upgrade backout from TN64X OC 01 -187 NTRR35KF A0878709
Rel. 6.00 (GA)
Legend:
Note 1: Starting with OPTera Connect DX Release 4.1, CAP numbers are discontinued.
Note 2: This CAP is only available upon request. To obtain a copy of this CAP, contact your Nortel
representative (refer to Chapter 10 “Technical assistance information” for the telephone numbers).

Models
Models provide customized sets of bay assemblies and circuit packs for
customers who have specific installation plans. Table 9-25 on page 9-82
provides ordering information for models.
Table 9-25
Models

(PEC)
ANSI model ordering codes with 1.5 Mbit/s ESI modules
OPTera Connect DX bay with tributary shelf and NTZV03AA A0842306 1

common equipment
OPTera Connect DX bay with tributary extension NTZV03AB A0876713 2

shelf, common equipment and DX100 switch
modules
OPTera Connect DX bay with tributary extension NTZV03AC A0876714 3

shelf, common equipment and DX140 switch
modules
OPTera Connect DX bay with tributary extension NTZV03AD A0889615 4

shelf, common equipment and DX65 switch modules
OPTera Connect DX bay (no tributary extension NTZV03BH A0893584 5

shelf) with common equipment and DX65 switch
modules
OPTera Connect DX bay (no tributary extension NTZV03BJ A0893585 6

modules
OPTera Connect DX bay (no tributary extension NTZV03BK A0893586 7

modules
ETSI model ordering codes with 2.0 MHz ESI modules
OPTera Connect DX bay with common equipment, NTJD93JE A0858923 8

filler cards and DX65 switch modules
OPTera Connect DX bay with common equipment, NTJD93JJ A0873351 9

OPTera Connect DX bay with common equipment, NTJD93JM A0898665 10

OPTera Connect DX single-shelf bay with common NTJD93KA A0895028 11

equipment, filler cards and DX65 switch modules


Models

(PEC)
OPTera Connect DX single-shelf bay with common NTJD93KB A0895026 12

equipment, filler cards and DX100 switch modules
ETSI model ordering codes with 2.0 Mbit/s / 2 MHz ESI modules
(only supported on OPTera Connect DX Release 5 or higher)
OPTera Connect DX bay with common equipment NTJD93JN A0507442 13
OPTera Connect DX single-shelf bay with common NTJD93KC A0507443 14

equipment
OPTera Metro Connect models
OPTera Metro Connect with OM4100 Supplemental NTJD93KD A0516421 15

Shelf and DX65 switch modules
OPTera Metro Connect with OM4100 Supplemental NTJD93KE A0516422 16

Shelf and DX100 switch modules
OPTera Metro Connect with OM4200 Supplemental NTJD93KF A0516424 17

Shelf and DX65 switch module
OPTera Metro Connect with OM4200 Supplemental NTJD93KG A0516425 18

OPTera Metro Connect with OM4150 Supplemental NTJD93KH A0519189 19

OPTera Metro Connect with OM4150 Supplemental NTJD93KJ A0519190 20

Installation ordering codes
Installer consumable kit NTJE01AC A0786359 21

Ordering rules for models

1 This model includes the following equipment:
— one OPTera Connect DX mechanical bay assembly with tributary
extension shelf (NTCA91AB)
— two breaker/filter modules (NTCA40BA)
— one 32 Mbyte SC circuit pack (NTCA41CA)
— two 1.5 Mbit/s ESI circuit packs (NTCA44AA)
— one MX circuit pack (NTCA48AA)
— one power feed jumper kit (# 2 AWG kit) (NTCA89GJ)
— one ANSI frame accessory kit (NTCA89GL)
— one frame insulator kit (NTRU0410)
— one ANSI washer kit (NTRU0412)
— one NPS50332-01L3 5ft wrist strap (A0336175)
— one model pre-assembly (NTCC9990)
— two DX100 switch modules (NTCA26BA)

— two DX140 switch modules (NTCA26CA)

— two DX65 switch modules (NTCA26AA)
— one OPTera Connect DX mechanical bay assembly without tributary
extension shelf (NTCA91AA)



— two 2 MHz ESI circuit packs (NTCE44BA)

— two MX circuit packs (NTCA48AA)
— 14 full height filler cards (NTCA49AA)
— three control shelf filler cards (NTCA59AA)
— OPTera bay frame junction kit (A0820534)
— one ETSI frame accessory kit (NTCA89GK)
— one frame extender kit to 2200 mm (NTRU0414)
— one installer consumable kit (NTJE01AC)
— two full height filler cards (NTCA49AA)

— six full height filler cards (NTCA49AA)

— one OPTera Connect DX single-shelf mechanical bay assembly
(NTCA91BA)
— four full height filler cards (NTCA49AA)
(NTCA91BA)
— four full height filler cards (NTCA49AA)


— two 2 Mbit/s / 2 MHz ESI circuit packs (NTCE44AA)
— one OPTera Rack Fix Kit (A0820534)
(NTCA91BA)
— two 2 Mbit/s / 2 MHz ESI circuit packs (NTCE44AA)
— one OPTera Rack Fix Kit (A0820534)
(NTCA91BA)


— two Quad STM-4 (FC) (NTCA36CA)
— two STM-4o aggregate (NTEU20AA)
— one Saturn EOS upper card assembly (NTEU40AA)
— one Saturn EOS lower card assembly (NTEU41AA)
— one Saturn subrack assembly (NTEU60AA)
— one RTU OC-192 DX Application Metro (non-DWDM)
(NTCA62AG)
— one RTU OC-192 Utility Section/Line PM (NTCA62EA)
— one RTU OC-192 Feature Optical Trib DCC (NTCA62FC)
— one OPTera Metro 4100/4200 installation kit used on NTCA91BA
(NTCA91KB)
— one ECP (II) with Plenum kit used on NTCA91BA (NTCA85FB)
— one configuration of combined products (NTYY99AQ)
— four 3 dB fixed pad attenuator (FC-FC) (A0783041)
— four optical patch cord FC-FC 3m (A0385575)
— one #2 AWG Lugs and Jumper Kit (NTCA89GJ)
(NTCA91BA)


(NTCA62AG)
— one RTU DX subtending SNCP rings (NTCA62FE)
(NTCA91KB)
(NTCA91BA)
— two STM-16 Short Reach circuit packs (NTCA30CK)
(NTCA62AG)
(NTCA91KB)
— two STM-16o aggregate (FC/PC) (NTEU25AA)


— four SC-FC adapter kit (NTCC99AA)
(NTCA91BA)
— two STM-16 Short Reach circuit packs (NTCA30CK)
(NTCA62AG)
(NTCA91KB)
— four SC-FC adapter kit (NTCC99AA)


(NTCA91BA)
(NTCA62AG)
(NTCA91KB)
(NTCA91BA)


(NTCA62AG)
(NTCA91KB)
— 20 NE-145C Tags (A0024293)
— one black permanent waterproof fine point marker (A0610072)
— one Brady SCNC-10 (numbers 0-9 x 30) wire marker (A0784416)
— one wire marker booklet (A0787459)
— one 1-ounce container of No-ox (A0802603)
— 20 0.063 in. shims for bay levelling (P0266174)
— 100 7.38 in. white cable ties (P0567232)
— 100 14 in. white self-locking cable ties (P0590550)
— 50 4.38 in. “Flag tag” self-locking cable ties (P0590555)
— 100 4 in. white self-locking cable ties (P0633700)
— three card labels with fiber optic warning (6 labels per card)
(P0645992)

— four brass tags with text “Do not disconnect” (P098A603)

— one roll of grey electrical tape, 3/4 in. x 66 ft (R0050333)
— one roll of black electrical tape, 3/4 in. x 66 ft (R0054458)
— four wire marker cards, #1-33 (R0105028)
— 4 ft. black heat shrink tubing, 3/4 in. diameter (R0105561)
— 10 ft. flame retardant white spiral wrap tubing, 1/2 in. diameter
(R0112569)
— 2 rolls of twine, waxed polyester, no. 9 size, tensile strength 105 lbs.
(R0112611)
— 4 ft. black heat shrink tubing, 1 in. diameter (R0112621)
— 10 ft. Nomax Aramid paper, 5 in. width (R0113635)
— 1 Grommet strip, catepillar 12.75 in., white, UL94V-0 (R0114693)
— 1 bottle of paint, Telephone Equipment Grey, brush on bottle,
0.6 ounces (R0116081)
— 4 ft. clear heat shrink tubing, 1/2 in. diameter (R0116510)
— 4 ft. clear heat shrink tubing, 3/8 in. diameter (R0116511)
— 4 ft. clear heat shrink tubing, 1 in. diameter (R0116512)
— 1 red pencil, for marking drawings


10-1
Technical assistance information 10-

For technical support and information from Nortel, refer to the following table.
Technical Assistance Service

For service-affecting problems: North America:
For 24-hour emergency recovery or software upgrade 1-800-4NORTEL (1-800-466-7835)
support, that is, for:
• restoration of service for equipment that has been carrying International:
traffic and is out of service 001-919-992-8300
• issues that prevent traffic protection switching
• issues that prevent completion of software upgrades
For non-service-affecting problems: North America:
For 24-hour support on issues requiring immediate support 1-800-4NORTEL (1-800-466-7835)
or for 14-hour support (8 a.m. to 10 p.m. EST) on upgrade Note: You require an express routing
notification and non-urgent issues.
code (ERC). To determine the ERC, see
our corporate Web site at
www.nortel.com. Click on the Express
Routing Codes link.
International:
Varies according to country. For a list of
telephone numbers, see our corporate
Web site at www.nortel.com. Click on the
Contact Us link.
Global software upgrade support: North America:
1-800-4NORTEL (1-800-466-7835)
International:
Varies according to country. For a list of
telephone numbers, see our corporate
Web site at www.nortel.com. Click on the
Contact Us link.
Nortel web site

You can also contact us through the Nortel web site at: www.nortel.com.
Select the link Support.

10-2 Technical assistance information

Nortel Networks
OPTera Connect DX
optical switch
Copyright © 2000–2005 Nortel Networks, All Rights Reserved
The information contained herein is the property of Nortel

Networks and is strictly confidential. Except as expressly
authorized in writing by Nortel Networks, the holder shall keep all
information contained herein confidential, shall disclose the
information only to its employees with a need to know, and shall
protect the information, in whole or in part, from disclosure and
dissemination to third parties with the same degree of care it uses
to protect its own confidential information, but with no less than
reasonable care. Except as expressly authorized in writing by
Nortel Networks, the holder is granted no rights to use the
information contained herein.
Nortel Networks, the Nortel Networks logo, the Globemark,

OPTera and Preside are trademarks of Nortel Networks.
SMF-LS is a trademark of Corning. Truewave is a trademark of

Lucent Technologies Inc. UNIX is a trademark of X/Open
Company Ltd. Microsoft and Windows are registered trademarks
of Microsoft Corporation in the United States and/or other
countries. ACE/Server, RSA, and SecurID are registered
trademarks of RSA Security Inc.
NTRR11DG
Standard Release 6 Issue 2
November 2005
Printed in Canada and in the United Kingdom

SDH Planning and Ordering Guide R6.0

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

SDH Planning and Ordering Guide R6.0

Hochgeladen von

Copyright:

Verfügbare Formate

NTRR11DG

Standard Rel 6 Issue 2 November 2005

Printed in Canada and in the United Kingdom

SDH Planning and Ordering Guide Rel 6 Standard Nov 2005

OPTera Connect DX optical switch Rel 6 Standard Nov 2005

New feature content 2-1

Upgrade considerations and planning 3-1

Network configuration architecture 4-1

SDH Planning and Ordering Guide Rel 6 Standard Nov 2005

10 Gbit/s unprotected configuration 4-18

Software feature description 5-1

OPTera Connect DX optical switch Rel 6 Standard Nov 2005

Tributary hairpinning 5-17

Hardware feature description 6-1

SDH Planning and Ordering Guide Rel 6 Standard Nov 2005

Message exchange 6-38

Optical layer OAM&P 7-1

Technical specifications 8-1

OPTera Connect DX optical switch Rel 6 Standard Nov 2005

2 MHz timing interface specifications 8-25

Ordering information 9-1

SDH Planning and Ordering Guide Rel 6 Standard Nov 2005

Technical assistance information 10-1

OPTera Connect DX optical switch Rel 6 Standard Nov 2005

About this document 0

This planning guide covers the following topics:

SDH Planning and Ordering Guide Rel 6 Standard Nov 2005

OPTera Connect DX SDH NTP Library

OPTera Long Haul

OPC User Interface

OPTera Connect DX optical switch Rel 6 Standard Nov 2005

SDH Planning and Ordering Guide Rel 6 Standard Nov 2005

• Preside Optical Power Management 4.0 Planning Guide, 450-3101-633

OPTera Connect DX optical switch Rel 6 Standard Nov 2005

OPTera Connect DX Release 6.0 has superior feature content compared to

Note: Starting in Release 6, the TN-64X platform is no longer supported

OPTera Connect DX Release 6.0 has many advantages, including:

SDH Planning and Ordering Guide Rel 6 Standard Nov 2005

• Networking: OPTera Connect DX Release 6.0 provides unmatched

OPTera Connect DX optical switch Rel 6 Standard Nov 2005

• Operations: OPTera Connect DX supports end-to-end provisioning,

SDH Planning and Ordering Guide Rel 6 Standard Nov 2005

Nortel is actively involved in various forums and standard bodies to ensure

OPTera Connect DX optical switch Rel 6 Standard Nov 2005

SDH Planning and Ordering Guide Rel 6 Standard Nov 2005

OPTera Connect DX optical switch Rel 6 Standard Nov 2005

New feature content 2-

SDH Planning and Ordering Guide Rel 6 Standard Nov 2005

OPTera Connect OPTera Connect OPTera Connect OPTera Connect

System security Yes Yes Yes Yes

Secure DCC and TCP/IP Yes Yes Yes Yes

Strong User Yes Yes Yes Yes

Control Shelf Yes Yes Yes Yes

Network element types

OPTera Connect DX optical switch Rel 6 Standard Nov 2005

Table 2-1 (continued)

OPTera Connect OPTera Connect OPTera Connect OPTera Connect

Unprotected hub DX bay only DX bay only - -

DX_HUB No No DX bay only DX bay only

Network configuration and architecture

Single 10 Gbit/s Linear No No Yes Yes

Single 4-Fiber ADM chain Yes Yes Yes Yes

Single 4-Fiber Yes Yes Yes Yes

Unprotected hub DX bay only DX bay only - -