SDH Planning and Ordering Guide R6.0
SDH Planning and Ordering Guide R6.0
SDH Planning and Ordering Guide R6.0
Nortel Networks
OPTera Connect DX
optical switch
SDH Planning and Ordering Guide
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.
Publication history 0
November 2005
Standard issue. Updates to Ordering Information.
April 2004
Standard issue.
Contents 0
About this document xi
Introduction 1-1
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
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
Change Application
Procedures
(CAPs)
OC-48 DWDM
Tributary Application
Note
(NTRR12AC)
Circuit
Pack Descriptions
(323-1531-102)
TL1 Interface
Description
(323-1531-190)
NE User Interface
Description
(323-1531-195)
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
• Provisioning and Operations Procedures Part 2, 323-1531-310
• Provisioning and Operations Procedures Part 3, 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
• Trouble Clearing and Module Replacement Part 2, 323-1531-543
• Trouble Clearing and Module Replacement Part 3, 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
Introduction 1-
This chapter provides an introduction to the OPTera Connect DX Release 6.0
product.
Figure 1-1 on page 1-5 shows a front-view diagram of the OPTera Connect DX
bay with extension shelf.
Figure 1-1
Front view of the OPTera Connect DX bay with extension shelf
DX3203p
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
Security
Bay configuration
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
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
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)
2-Fiber Ring extra traffic DX bay only DX bay only DX bay only DX bay only
Subtending SNCP ring DX bay only, DX bay only, DX bay only DX bay only
except except
unprotected hub unprotected hub
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
Synchronization
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, 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-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)
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
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 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 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 long reach DX bay only DX bay only DX bay only DX bay only
T/R
HH STM-4 TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
Dual STM-16 short reach No DX bay only, DX bay only, DX bay only,
(SR) equipped with equipped with equipped with
DX100 or DX140 DX100 or DX140 DX100 or DX140
switch modules switch modules switch modules
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 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
DX100 switch module DX bay only DX bay only DX bay only DX bay only
DX140 switch module DX bay only DX bay only DX bay only DX bay only
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 maintenance TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
interface (supported for
upgrades)
MOR and MOR Plus TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
Protection switching
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)
Sub-network connection DX bay only DX bay only DX bay only DX bay only
protection (SNCP) ring
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)
Nodal interface
Alarming
MOR power optimization TN-64X bay only TN-64X bay only TN-64X bay only TN-64X bay only
alarms
OPC tools
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 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
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
TL1 support No No No No
TL1 connections No No No No
provisioning
Troubleshooting tools
From/to TN-64X No No No No
Release 1
From/to TN-64X No No No No
Release 2
Adding/deleting an ADM DX bay only DX bay only DX bay only DX bay only
node to/from 2-Fiber Ring
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-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
Adding/deleting DX NE No No No Yes
to/from a 2-Fiber TN-16X
and DX MS-SPRing Ring
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
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
Unprotected hub (0:1) No Yes (see Note) Yes (see Note) Yes (see Note)
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).
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
STM-64 8 4 4
STM-16 56 40 16
STM-4 64 64 64
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
DX65 STM-64
11
Filler card
G0
G10
slot (see note) slot (see note)
2-24 New feature content
2
2
12
G1
G11
G21
pack slot slot pack slot
3
3
G12
G2
13
G22
pack slot slot pack slot
4
4
G23
pack slot DX100/DX140 pack slot
14
Switch module A
Non-10 Gbit/s circuit Non-10 Gbit/s circuit
5
5
G4
G24
pack slot pack slot
Non-10 Gbit/s circuit Non-10 Gbit/s circuit
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
8
8
16
G27
G17
9
9
G8
G28
pack slot slot pack slot
Filler card
18
10
G19
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:
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.
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.
• 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.
BMER B05
2FR 4FR
Legend
— 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)
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.
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])
Table 2-7
Example of supported 10 Gbit/s configurations with DX100 or DX65 switch module
4FR - 1x4FR - - -
MS-SPRing
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
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 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.
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.
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 single STM-16 LR T/R circuit pack has the same functionality as the
existing STM-16 LR T/R interfaces (NTCA30AK/AL).
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.
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 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.
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:
• 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 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:
• 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)
• 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
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)
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
Used to cancel a TL1 user tid Any valid Target Identified (TID)
administration session. in the OPC
dlt-user-secu:<tid>:<uid>:<ctag>;
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)
0 4
1 4
2 3
3 3
4 2
5 1
6 1
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.
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
[ 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
From the Hardware Baseline tool main menu screen, the user is provided with
the following options:
— 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
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
• 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
Connection Rate: > VC-4 < Direction: > Bi < No of Conns: > 1
Source Sink
Endpoint: > STM64 G19 1 Endpoint: > STM64 G11, G12 1
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
Connection Name:
A End NE Z End NE
NE: > < NE: > <
Next Config NE: > < Next Config NE: > <
Route: > Short < Channel: > Traffic type: > Protected <
[ Route List ] [ Secondary Gateway G]
[ Apply Return] [ Close Del]
• 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.
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.
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
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
The existing PLD401 log will be generated when the test access SplitE is
initiated or removed.
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.
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.
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.
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:
• 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.
• 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.
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.
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)
• an in-service upgrade from OPTera Connect DX Release 4.1 (GA) to
OPTera Connect DX Release 6.0 (GA)
• an in-service upgrade from OPTera Connect DX Release 5.0 (GA) to
OPTera Connect DX Release 6.0 (CA)
• an in-service upgrade from OPTera Connect DX Release 5.0 (GA) to
OPTera Connect DX Release 6.0 (GA)
• an in-service upgrade from OPTera Connect DX Release 6.0 (CA) to
OPTera Connect DX Release 6.0 (GA)
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.
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).
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
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
TN-16X 9.0
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
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 .
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)
[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)
• 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)]
• mixed Px4-Fiber Ring, Nx2-Fiber Ring, Linear Mx(1+1) and Kx(0:1)
[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).
• mixed Nx2-Fiber Ring and Mx(0:1) [where N is 0 to 2 and M = 4 - (2xN)]
• mixed Nx2-Fiber Ring and Linear Mx(1+1) [where N is 0 to 2 and
M = (4 - (2xN))/2].
• mixed Nx2-Fiber Ring, Linear Mx(1+1) and Kx(0:1) [where N is 0 to 2,
M is 0 to 2 and K = 4 - 2x(N+M)]
• Linear Nx(1+1) (where N is 1 to 2)
• mixed Linear Nx(1+1) and Mx(0:1) [where N is 0 to 2 and M = 4 - (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 4
10GBit/s optical interfaces.
Note 2: 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.
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.
Note:
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.
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.
When the network element is equipped with DX65 or DX100 switch modules,
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).
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
F F PP W
G17 G18 G12 G11
P P G18
G12 P P
W W
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:
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.
When the network is equipped with DX140 switch modules, the network
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: 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).
Figure 4-3
Single 4-Fiber Ring
DX0497_SDH
W PP PP W
G17 G18 G12 G11
P P G18
G12 P P
W W
Legend
= STM-64 traffic path
Figure 4-4
Dual 4-Fiber Rings with a network element configured as a 2x4-Fiber ADM
DX5383p
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.
This illustration also applies to protection group G0/G10 and G9/G19.
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
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
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
= 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.
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 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.
Note 2: The OPTera Connect DX network element must be either SONET
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.
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-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
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
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
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.
DX Unprotected DX Unprotected
2.5G Interface Interface
traffic
10G
DX NE
Legend
= OPC SOC
= ATM switch
= IP Router
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.
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
Legend
LTE = Line-terminating equipment
DX_HUB = DX_HUB network element
NE = Network element
= Span of control boundaries
Figure 4-12
Subtending SNCP ring support
DX5379t
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.
Figure 4-14
Subtending STM-16 2-Fiber MS-SPRing support
DX5381t
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
• 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:
Figure 4-15
Example of subtending STM-16 2-Fiber MS-SPRing using regular hairpinning connections
DX4555p
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
Location A Location B
Legend
Figure 4-16
Example of subtending 2-Fiber MS-SPRing using OPTera Connect DX STM-16 interfaces
OPTera
Connect DX
network element
Legend
= STM-64 rate
= STM-16 rate
= STM-16 interface
= TN-16X network element
Figure 4-17
Example of a standalone 2-Fiber Ring consisting of TN-16X and OPTera Connect DX network
elements
DX4626p
TN-16X
NE
Legend
DX NE = OPTera Connect DX network element
= STM-16 rate
= STM-16 interface
DX65 4 4 4
DX100 20 8 20
DX140 28 N/A 28
Table 4-2
TN-16X transmit interface circuit pack with Ring TSI1 ASIC
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
Cross-connect
STM-16 functionality
Back-to-Back tribs
No longer needed STM-1
STM connections
STM-16
STM-4
DX Ring
STM-1
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
Note: Since OPTera Connect DX Release 5.0 STM-64 T/R circuit pack are
no longer required for system lineup and testing (SLAT).
Table 4-3
Tributary interfaces and supported protection schemes
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.
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.
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
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.
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.
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.
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.
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.
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.
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.
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
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.
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
• Quad 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
• Quad STM-4 circuit packs
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.
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.
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.
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.
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.
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
Procedures, 323-1531-520 for the OPTera Connect DX platform.
Table 5-1
Performance monitoring parameters
MS UAS
MS FEC
RS ES RS ES
RS SES RS SES
RS ESR
RS SESR
RS BBER
path ES path ES
path SESR
path BBER
path UAT
path SEP
path SEPI
path UAS
Note: Physical PMs are only supported on the 10 Gbit/s line interfaces.
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)
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 long reach APD −6.0, −25.0 −7.0, −24.0 −7.0, −24.0
T/R
TN-64X 10G STM-64 single −4.0, −12.5 −6.0, −11.5 −6.0, −11.5
regenerator (XR)
• 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
Procedures, 323-1531-311 for the OPTera Connect DX platform.
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.
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
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.
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.
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 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.
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.
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
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).
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.
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.
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.
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
Network Element
(OPTera Connect DX)
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.
Input Output
Input Output
Input Output
TAP In
Legend
TAP = Test access port
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
• 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.
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.
Figure 5-6
Example of connection loopback
DX4570t
Rx Rx
Tx Tx
Figure 5-7
Example of terminal loopback
DX4569t
Tx
Rx
Tx
Rx
Port or line Switcher Port or line
circuit pack module circuit pack
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:
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
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
Figure 5-10 on page 5-32 shows the scenario where the AINS status is enabled,
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
Figure 5-11 on page 5-33 shows the scenario where the AINS status is enabled,
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
AINS = Auto in-service
AIP = Alarm inhibit period
SUP = Start-up period
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
Legend
AINS = Auto in-service
AIP = Alarm inhibit period
SUP = Start-up period
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
SUP
Legend
AINS = Auto in-service
AIP = Alarm inhibit period
SUP = Start-up period
Figure 5-14
Example of Orderwire usage
DX4567p
Handset Handset
Orderwire Orderwire
circuit pack circuit pack
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.
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
• 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.
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.
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.
• 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.
• 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.
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).
Figure 6-1
OPTera Connect DX bay with extension shelf
DX2710p
Cable Cover
(both sides)
Control shelf
Fan
(3 places)
Fan
(3 places)
Extension shelf
Figure 6-2
OPTera Metro Connect bay
DX4119p
Cable Cover
(both sides)
Control shelf
Fan
(3 places)
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
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.
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
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.
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
• 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)
Note 1: You can mix any configuration as long as the you don’t exceed 8
10 Gbit/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.
For OPTera Connect DX bays equipped with DX100 switch modules
(NTCA26BA) or DX65 switch 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 - (2xP))/2].
• mixed Px4-Fiber Ring and Mx(0:1) [where P is 0 to 1 and M = 4 - (4xP)]
Table 6-1
Supported tributary circuit pack group types
STM-16 G1 - G8 2-9
Quad STM-16 (see Note 2 and G0, G9 - G12, or G17 - G19 1, 10 -13 or 16 - 19
Note 4)
STM-64 See Table 6-2 for the STM-64 CPG for different
configurations
Extension shelf
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.
Unprotected 10 Gbit/s terminal G11, G12, G17, G18 12, 13, 16, 17,
G0, G10, G9 or G19 1, 11, 10, 18
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).
Figure 6-11 on page 6-22 shows the main shelf of the OPTera Connect DX
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.
Figure 6-12 on page 6-23 shows the main shelf of the OPTera Connect DX
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.
1
Filler G0
11
Filler
G10
2
Tributary circuit pack
12
G1
G11
STM-64 T/R circuit pack slot slot
13
G2
G12
STM-64 T/R circuit pack slot slot
4
Tributary circuit pack
G3
slot
DX65 Switch module A
14
5
Tributary circuit pack
G4
slot
6
Tributary circuit pack
G5
slot
DX65 Switch module B
15
Tributary circuit pack
7
G6
slot
16
8
G7
G17
STM-64 T/R circuit pack slot slot
9 Tributary circuit pack
17
G8
G18
STM-64 T/R circuit pack slot slot
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
Tributary circuit pack
12
G1
G11
Universal slot slot
G12
Universal slot slot
4
Tributary circuit pack
G3
slot
DX100 Switch module A
14
5
Tributary circuit pack
G4
slot
6
Tributary circuit pack
G5
slot
DX100 Switch module B
15
Tributary circuit pack
7
G6
slot
16
8
G7
G17
Universal slot slot
9
Tributary circuit pack
17
G8
18
G9
Filler Filler
G19
OPTera Connect DX main shelf showing supported circuit pack slots for DX100 switch modules
DX5353p
Figure 6-12
11
G0
G10
Universal slot Universal slot
2
Tributary circuit pack
12
G1
G11
Universal slot slot
3
Tributary circuit pack
13
G2
G12
Universal slot slot
4
Tributary circuit pack
G3
slot
DX140 Switch module A
14
5
Tributary circuit pack
G4
slot
6
Tributary circuit pack
G5
slot
DX140 Switch module B
15
7
Tributary circuit pack
G6
slot
16
8
Tributary circuit pack
G7
G17
17
G18
G8
18
G9
G19
DX5354p
6-24 Hardware feature description
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.
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).
G20 G21 G22 G23 G24 G25 G26 G27 G28 G29
Tributary circuit pack
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.
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 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.
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 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
— single slot control shelf filler cards (NTCA59AA) are required for slots
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
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
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.
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
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.
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.
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.
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.
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.
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.
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.
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.
Technical specifications 8-
This chapter provides the technical specifications and requirements for the
OPTera Connect DX network element.
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.
Table 8-1
IEC laser emission classes
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.
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
(12.00 IN.) Wiring aisle
381mm
(15.00 in.) Maintenance aisle
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.
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
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
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).
Table 8-4
Circuit pack power estimates
Normal Maximum
Normal Maximum
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)).
Table 8-5
Maximum thermal loading
Power requirements
The following specifications cover all the requirements related to power for an
OPTera Connect DX network element.
Table 8-7
Battery voltage requirements measured at the bay
Requirement Specification
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
75 V 10 ms ANSI T1.315-199x
100 V 2 ms BTR2511
Table 8-10
Power converter safety specifications
EN EN60950 ITE
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
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
— 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
–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
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 2: Fitting the 3-position bus bars on the power feed terminals
AusTel TPH01115(U) –
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
Acoustic noise contour of constant UK: British Telecom RC 5000P; BS 4198 1967
loudness, index 1.99
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.
Table 8-16 on page 8-17 outlines the storage and transportation environment
envelope.
Table 8-16
Storage and transportation environment
High temperature 25°C to 70°C in less than 5 USA: Telcordia (formerly known as Bellcore)
thermal shock minutes NEBS GR-63-CORE
High humidity cyclic –1°C to 28°C at 95% relative USA: Telcordia (formerly known as Bellcore)
test humidity NEBS GR-63-CORE
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.
Condition Specification
In a shipment package Drop height 609 mm (24 in.) or 762 mm (30 in.)
(depends on weight)
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
Condition Specification
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
Connect DX network element.
Emissions
Electromagnetic interference (EMI) emission requirements minimize the
interference of EMI from the OPTera Connect DX system to other electronic
devices.
The OPTera Connect DX bay meets the following specifications at these levels
with no errors or malfunction:
• Telcordia (formerly known as Bellcore) GR-1089-CORE
• Bell Canada TAD 8465
• 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).
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.
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
Table 8-20
ESI specifications
Condition Specification
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
Table 8-22
DS1 cable lengths for different LBO settings
LBO value DS1 ABAM (608) cable AT&T 1249C DS1 cable
Long 137 to 200 m (450 to 655 ft) 76 m to 137 m (250 ft to 450 ft)
Parameter Value
Impedance 75 Ω
Parameter Value
Impedance 75 Ω or 120 Ω
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:
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 element NE
Clock
Legend:
= Transport traffic flow
Table 8-25
Timing modes of operation
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.
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.
— 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).
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
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
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
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
Ethernet
point-to-point
link
SC MI MI SC
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
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
NTCA35AB (MPO) HD STM-1o (16 RS DCC channels) Compliant to ITU-T G.957 S1.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
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)
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.
Specifications
Transmitter
Pigtail single-mode
Specifications
Receiver
Specifications
Transmitter
Pigtail single-mode
Side-mode suppression NA 30 dB
ratio (SMSR)
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.
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.
Receiver
Specifications
Pigtail single-mode
Note 3: Damage level is the maximum optical power for which no damage to the components occurs.
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
Connector | adapterless
(see Note 1)
Transmitter
Specifications
Pigtail single-mode
Wavelength range -
Side-mode 33 dB n/a 30 dB
suppression
ratio (SMSR)
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.
Note 3: 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.
Receiver
Pigtail single-mode
Specifications
Note 4: Damage level is the maximum optical power for which no damage to the components occurs.
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.
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
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
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
Note: See Chapter 9, “Ordering information”, for the complete information on Dual GE tributary circuit
packs.
Transmitter
Laser DFB laser DFB laser EML laser MZ LiNb03 DFB laser
laser
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
Side-mode 40 dB 40 dB 30 dB 30 dB 40 dB
suppression ratio
(SMSR)
(unmodulated)
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)
Maximum 27 dB 27 dB 20 dB 27 dB 27 dB
tolerated optical
reflection (return
loss)
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.
Receiver
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)
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 11: Damage level is the maximum optical power for which no damage to the components occurs.
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.
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).
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)
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.
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:
• 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)]
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—
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)".
• Table 9-1 on page 9-22 lists these items.
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)".
• Table 9-1 on page 9-22 lists these items.
5 If this OPTera Connect DX bay is at the end of a row:
• order "End panel kit for a 660 mm line up".
• Table 9-1 on page 9-22 lists these items.
—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)”
• Table 9-1 on page 9-22 lists these items.
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
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
Figure 9-1
OPTera Connect DX Release 6.0 product structure
OPTera Connect DX
Release 6.0
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.
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)
Fan
(3 places)
Extension shelf
Figure 9-3
OPTera Metro Connect bay
DX4119p
Cable Cover
(both sides)
Control shelf
Fan
(3 places)
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.
1
Filler G0
11
Filler
G10
9-18 Ordering information
2
Tributary circuit pack
12
G1
G11
STM-64 T/R circuit pack slot slot
G12
STM-64 T/R circuit pack slot slot
4
Tributary circuit pack
G3
slot
DX65 Switch module A
14
5
Tributary circuit pack
G4
slot
6
Tributary circuit pack
G5
slot
DX65 Switch module B
15
Tributary circuit pack
7
G6
slot
16
8
G7
G17
STM-64 T/R circuit pack slot slot
9 Tributary circuit pack
17
G8
G18
STM-64 T/R circuit pack slot slot
10
18
G9
Filler Filler
G19
OPTera Connect DX main shelf showing supported circuit pack slots for DX65 switch modules
DX5356p
Figure 9-6
1
Filler
G0
11
Filler
G10
2
Tributary circuit pack
12
G1
G11
Universal slot slot
13
G2
G12
Universal slot slot
4
Tributary circuit pack
G3
slot
DX100 Switch module A
14
5
Tributary circuit pack
G4
slot
6
Tributary circuit pack
G5
slot
DX100 Switch module B
15
Tributary circuit pack
7
G6
slot
16
8
G7
G17
Universal slot slot
9
Tributary circuit pack
17
G8
G18
Universal slot slot
10
18
G9
Filler Filler
G19
OPTera Connect DX main shelf showing supported circuit pack slots for DX100 switch modules
DX5353p
Figure 9-7
11
G0
G10
Universal slot Universal slot
2
Tributary circuit pack
12
G1
G11
9-20 Ordering information
3
Tributary circuit pack
13
G2
G12
Universal slot
4
Tributary circuit pack
G3
slot
DX140 Switch module A
14
5
Tributary circuit pack
G4
slot
6
Tributary circuit pack
G5
slot
DX140 Switch module B
15
7
Tributary circuit pack
G6
slot
G17
Universal slot slot
9 Tributary circuit pack
17
G18
G8
18
G9
G19
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
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
OPTera Connect DX bay with rear exhaust air flow NTCA91AC A0896276 3, 5, 6, 7
OPTera Connect Top infill panel kit (2200 mm) NTCA91ML A0993402 20
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).
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
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
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).
• 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.
Table 9-3
STM-64 10G T/R circuit packs
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
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 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
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 TriFEC 1528.77 nm +/- CHIRP NTCF06MP A0827034 1,2,8,9,10,13
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
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
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
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 1579.52 nm +/-CHIRP NTCF06RU A0826704 1,2,6,8,9,10,13
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 1602.31 nm +/-CHIRP NTCF06CT A0826625 1,2,6,8,9,10,13
STM-64 AM2 10G T/R TriFEC 1601.88 nm +/-CHIRP NTCF06YV A0826627 1,2,6,8,9,10,13
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
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.
4 This circuit pack uses a transmitter with provisionable AM1 or AM2 dither
patterns. Use this circuit pack in conjunction with DWDM couplers and
MOR Plus amplifiers, or OPTera Long Haul 1600G amplifiers.
5 This circuit pack uses a transmitter with provisionable AM1 or AM2 dither
patterns. Use this circuit pack in conjunction with DWDM couplers and
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.
11 This circuit pack uses a transmitter with provisionable AM1 or AM2 dither
patterns. Use this circuit pack in conjunction with DWDM couplers and
MOR, or MOR Plus amplifiers. You cannot use this circuit pack with
OPTera Long Haul 1600G amplifiers.
12 This circuit pack uses a transmitter with provisionable AM1 or AM2 dither
patterns. Use this circuit pack in conjunction with DWDM couplers and
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
Legend:
PEC = Product Engineering Code (Nortel Network customer order code)
CPC = Common Product Code (Nortel Network internal order code)
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.
— 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)
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 10Gbit/s
configuration examples supported by the OPTera Connect DX when
equipped with DX140 switch modules.
For OPTera Connect DX bays equipped with DX100 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)]
Table 9-5
Switch module circuit pack
Table 9-6
Tributary interface 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-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-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
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 T/R with 16 RS DCC channels NTCE35AB A0877946 1, 3, 4, 19, 24,
25, 28
Dual Gigabit Ethernet tributary T/R short reach NTCA90EA A0893722 1, 3, 26, 27
Legend:
PEC = Product Engineering Code (Nortel Network customer order code)
CPC = Common Product Code (Nortel Network internal order code)
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
better performance than FC or ST connectors.
16 This circuit pack has ST connectors. 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.
17 This circuit pack has SC connectors. 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.
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.
Table 9-8
Optical connector adapter kits
Optical connector adapter kits for circuit packs with up to three optical ports
Optical connector adapter kits for circuit packs with four optical ports
Table 9-9
Common equipment circuit packs
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
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
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
Table 9-12
Optical fiber cables equipped with mVOAs
Legend:
SM = Single mode
PEC = Product Engineering Code (Nortel Network customer order code)
CPC = Common Product Code (Nortel Network internal order code)
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.
Table 9-13
HD STM-1o optical fiber cable assemblies
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
Legend:
PEC = Product Engineering Code (Nortel Networks’ customer order code)
CPC = Common Product Code (Nortel Networks’ internal order code)
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
Legend:
PEC = Product Engineering Code (Nortel Networks’ customer order code)
CPC = Common Product Code (Nortel Networks’ internal order code)
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
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
Legend:
PEC = Product Engineering Code (Nortel Network customer order code)
CPC = Common Product Code (Nortel Network internal order code)
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
Table 9-19
OPTera Connect DX Release 6.0 software load - supply options
Applications
Extended applications
Upgrade licence
Software certificates
Legend:
PEC = Product Engineering Code (Nortel Network customer order code)
CPC = Common Product Code (Nortel Network internal order code)
MS-SPRing = multiplexer section shared protection ring
ADM = add/drop multiplexer
RS = regenerator section
MS = multiplexer section
SNCP = sub-network connection protection
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).
OPTera Connect DX5 SDH (universal bay and TN-64X bay NTCA65KF
combined) NTP suite
OPTera Connect DX4.1 SDH (universal bay and TN-64X bay NTCA65KE
combined) NTP suite
OPTera Connect DX4.0 SDH (universal bay and TN-64X bay NTCA65KD
combined) NTP suite
Interactive CD-ROMs
Helmsman CD-ROMs
Legend:
PEC = Product Engineering Code (Nortel Network customer order code)
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
Volume 4 - Maintenance
Supporting documentation
Table 9-23 shows the ordering information for supporting documentation that
is available to customers.
Table 9-23
Supporting documentation
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
Legend:
PEC = Product Engineering Code (Nortel Network customer order code)
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.
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 - Convert a 4F ADM chain to a 4F Ring see Note 1 see Note 2 see Note 2
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
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
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 - 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 - 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
Preside SUM - TN-64X - Upgrade backout from TN-64X see Note 1 NTRR35KH A0999940
Rel. 7.00
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 - 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 - 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
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 - 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 - System software upgrade to DX Rel. 4.00 OC 01- 173 NTRR21JD A0878704
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:
PEC = Product Engineering Code (Nortel Network customer order code)
CPC = Common Product Code (Nortel Network internal order code)
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
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
optical switch
SDH Planning and Ordering Guide
Copyright © 2000–2005 Nortel Networks, All Rights Reserved
NTRR11DG
Standard Release 6 Issue 2
November 2005
Printed in Canada and in the United Kingdom