HL 6100

NTY316AL
Nortel
Optical Long Haul 1600

Repeater NE Network Application Guide
Rel 11 Standard Issue 1 December 2005
Whats inside...
Introduction
Dense regenerator application
Wavelength Translator application
Wavelength Combiner application
Optical dedicated protection ring (ODPR) application
MOR Plus amplifier application
Operations, administration, maintenance, and provisioning (OAM&P)
Engineering rules
Mechanical specifications
Circuit pack technical specifications
Appendix A: Overhead processing
Appendix B: TriFEC applications
Appendix C: Merged XR/WT circuit packs
Appendix D: Short-reach optics
Technical assistance information
*A0507000*
Copyright 20002005 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.
This information is provided as is, and Nortel Networks does not make or provide any warranty of any kind, expressed or implied,
including any implied warranties of merchantability, non-infringement of third party intellectual property rights, and fitness for a
particular purpose. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the
information contained herein.
Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks.
ACE/Server, RSA, and SecurID are trademarks of RSA Security Inc.
HP-UX is a trademark of Hewlett-Packard Company
Sun and Solaris are trademarks of Sun Microsystems, Inc.
CLFI, Common Language, and Telcordia are trademarks of Telcordia Technologies, Inc.
UNIX is a trademark of X/Open Company Ltd.
Windows and Windows NT are trademarks of Microsoft Corporation.
Printed in Canada
iii
Contents
About this document
Introduction
0
ix
1-1
Optical Long Haul 1600 Release 11 1-2

Optical Long Haul 1600 platform 1-2
Applications supported on the Repeater network element 1-2
Product upgrade paths 1-6
Interoperability 1-7
Network management 1-7
Optical Long Haul 1600 application interworking 1-7
2-1
Description of the Dense regenerator application 2-1

Supported circuit packs for the Dense regenerator application 2-2
Overhead processing 2-7
Dense regenerator application in a network 2-8
3-1
Description of the Wavelength Translator application 3-1

Supported circuit packs for the Wavelength Translator application 3-2
Transparent FEC bytes 3-7
B1 and C1 (J0) bytes provisioning 3-8
Wavelength leasing application 3-9
Legacy interoperability 3-9
Fault sectionalization 3-9
Wavelength Translator application with TriFEC 3-12
Transparency of Wavelength Translator applications with TriFEC 3-12
Error correction provisioning 3-13
Determining whether the line/MS is severely degraded (for WT applications with
TriFEC) 3-15
WAN PHY support in Optical Long Haul 1600 3-16
Description of LAN PHY and WAN PHY 3-17
10 GE WAN PHY Wavelength translator interworking 3-18
Wavelength Translator application in a network 3-19
4-1
Description of the Wavelength Combiner application 4-2
Repeater NE Network Application Guide NTY316AL Rel 11 Issue 1 Standard Dec 2005
iv Contents
Supported circuit packs for the Wavelength Combiner application 4-7
Dual Gigabit Ethernet circuit pack (NTCA90xA) 4-8
B1 and B2 bytes 4-12
Enhanced DCC transparency of the Wavelength Combiner 4-13
K1 and K2 transparency 4-13
Orderwire and user bytes transparency (E1, E2, F1, and F2) 4-14
Fault sectionalization 4-14
Wavelength Combiner application with TriFEC 4-18
Transparency of Wavelength Combiner applications with TriFEC 4-18
Error correction provisioning 4-18
Determining whether the line/MS is severely degraded
(for Wavelength Combiner applications with TriFEC) 4-20
Wavelength Combiner operation with Dual Gigabit Ethernet 4-23
Traffic management 4-26
Synchronization 4-29
Network element synchronization modes 4-29
Optical Long Haul 1600 Wavelength Combiner interoperability with Transport Node
OC-48 BLSR using k-byte compliancy 4-32
Wavelength Combiner application in a network 4-33
Optical dedicated protection ring (ODPR) application
5-1
Description of the optical dedicated protection ring (ODPR) application 5-2

Supported circuit packs for the ODPR application 5-4
ODPR application and network protection 5-9
Considerations 5-14
Protection switching 5-15
Protection switch behaviors and hierarchy 5-16
Signal flow and module interconnection 5-17
Normal traffic flow 5-18
Traffic flow after a unidirectional 1+1 protection switch 5-19
Optical fiber connections for the ODPR circuit pack group 5-20
ODPR application with TriFEC 5-22
Determining whether the line/MS is severely degraded (for ODPR applications with
TriFEC) 5-22
Network element user interface (NE UI) support 5-24
Optical Protection Menu 5-24
Protection Performance Menu 5-25
Signal degrade (SD) threshold provisioning 5-25
Alarms affected by the ODPR application 5-26
OPC support for the ODPR application 5-27
ODPR application in a network 5-27

Description of the MOR Plus amplifier 6-2
Mid-stage access 6-2
Integrated optical service channel 6-3
Complete suite of optical layer management tools 6-3
Scalability for DWDM backbones 6-4
MOR Plus amplifier application guides 6-4
Optical Long Haul 1600 NTY316AL Rel 11 Issue 1 Standard Dec 2005
6-1
Contents v
Operations, administration, maintenance, and provisioning

(OAM&P)
7-1
Commissioning and span of control upgrades 7-2

New deployments and multiple catalog software (MCS) support 7-2
Restore commissioning MI command 7-3
Product upgrade paths 7-4
Interoperability 7-4
Performance monitoring 7-7
Performance monitoring for the Wavelength Combiner application 7-7
Performance monitoring for the Wavelength Translator and Dense regenerator
applications 7-11
SONET and SDH (ETSI) PM counts 7-14
Untimed bins 7-16
Concatenated PM counts 7-17
Network element user interface (NE UI) support for the Repeater 7-18
External communications (DCC and OSC) 7-23
DCC for the Wavelength Combiner application 7-23
DCC and OSC for Dense regenerator applications 7-24
OAM&P for Dual Gigabit Ethernet circuit packs 7-25
Optical link interoperability 7-37
MOR Plus amplifier 7-37
ODPR and third-party routers 7-37
Traffic protection for Wavelength Combiner applications 7-37
Wavelength Combiner Dual GE services interoperability with third-party
routers 7-38
Synchronization status messaging (SSM) 7-39
Timing generation 7-40
Timing distribution 7-41
ESI modes of operation 7-41
Target filter mode provisioning 7-43
Synchronization status messaging provisioning 7-44
Alarms and events for synchronization status messaging 7-48
20-character network element name 7-48
64K NE ID 7-48
Routing fundamentals 7-49
Level 1 routing 7-51
Level 2 routing 7-53
Centralized manual area address provisioning 7-57
Manual area addresses 7-58
Adding a manual area address 7-59
Partition repair 7-61
OPC support 7-62
Fault management 7-62
Performance monitoring capability 7-62
Extension shelf 2 7-62
OPC software features 7-63
Span of control and deployment engineering guidelines 7-64
TL1 facility and equipment provisioning 7-65
Facility provisioning 7-65
Equipment provisioning 7-65
vi Contents
Surveillance 7-66
Restrictions 7-66
Strong authentication 7-67
Network management 7-74
Ethernet Wayside 7-74
Feature description 7-77
Open access orderwire 7-82
Connection Query and Addition 7-83
Manual seams 7-84
Engineering rules
8-1
Circuit pack maximum and optical jitter 8-2

Mechanical bay assembly shelf G-naming 8-2
Circuit pack positioning for the control shelf 8-4
Mandatory circuit packs for the control shelf 8-4
Optional circuit packs 8-7
Circuit pack positioning for transport circuit packs 8-9
MOR Plus amplifier circuit packs 8-10
Wavelength Translator circuit packs 8-11
Dense regenerator circuit packs 8-12
Wavelength Combiner circuit pack groups 8-13
Optical dedicated protection ring (ODPR) circuit pack groups 8-16
Circuit pack sparing and replacement 8-18
Circuit pack sparing and replacement rules for dual 2.5 Gbit/s WT circuit
packs 8-24
OPC definition and span of control 8-25
Maximum number of network elements in a span of control 8-26
Communication between the partitioned OPC (POPC) and other network elements
through optical fiber 8-26
Communication between the partitioned OPC (POPC) and independent networks
over the Ethernet DCC bridge 8-26
Location of the partitioned OPC (POPC) in a networks 8-27
Rules for Optical Long Haul 1600 applications with one span of control 8-27
Rules for Optical Long Haul 1600 applications with multiple spans of control 8-28
Repeater network element limitations 8-29
Network reconfiguration 8-29
External communications 8-29
Globalization 8-29
Network synchronization requirements 8-30
Stratum clocks 8-31
External synchronization interface internal clock specifications 8-31
DS1 timing interface specifications 8-31
2 MHz timing interface specifications 8-32
Building-integrated timing supply 8-32
Synchronization status messaging (SSM) 8-33
Ethernet Wayside engineering rules 8-40
Strong authentication 8-42
OPC provisioning requirements 8-43
Open access orderwire 8-45
Contents vii
9-1
Safety specifications 9-2

Site engineering 9-3
Maximum Ethernet cable length 9-3
Mechanical bay assembly specifications 9-4
Frame equipment 9-5
Operational environment 9-6
Storage and transportation environment 9-7
Altitude 9-8
Atmospheric dust 9-8
Mechanical shock and vibration 9-9
Electromagnetic compatibility 9-9
Emissions 9-10
Susceptibility/Immunity 9-11
Electrostatic discharge and electrical fast transient 9-11
Parallel telemetry output relay rated capacity 9-12
Floor loading 9-12
Thermal loading 9-13
Power requirements 9-13
Power distribution 9-14
Power installation requirements 9-15
Circuit pack power estimates 9-23
Thermal tool 9-24
List of procedures
9-1
Determining thermal requirements for circuit pack configurations 9-26
Thermal tool worksheet 9-28
Custom applications 9-31
Power management tool 9-31
Circuit pack technical specifications
10-1
Optical interface specifications 10-1

Technical specifications for Repeater circuit packs 10-1
2.5G WT circuit pack (NTCA70xx) 10-3
OC-48/STM-16 T/R SR circuit pack (NTCA30CK) 10-6
OC-48/STM-16 DWDM T/R circuit pack (NTCA30xK) 10-9
OC-48/STM-16 T/R (1310 nm) circuit pack (NTCA30AL) 10-12
10G WT SR (TriFEC) circuit pack (NTWR07AA) 10-15
10G WT circuit pack (NTCA07xx) 10-18
10G WT (TriFEC) circuit pack (NTCF07xx) 10-21
Dual 2.5G WT on/off ramp circuit pack (NTCA72xx) 10-24
OC-192/STM-64 T/R circuit pack (NTCA06xx) 10-27
OC-192/STM-64 T/R (TriFEC) circuit pack (NTCF06xx) 10-31
OC-192/STM-64 XR circuit pack (NTCA04xx) 10-35
OC-192/STM-64 XR/WT circuit pack (NTCF04xx) 10-38
Dual GE circuit pack (NTCA90CA, NTCA90EA, or NTCA90GA) 10-41
Optical switch module (OSM) circuit pack (NTCA39AA) 10-44
11-1
Description of overhead bytes 11-2
viii Contents
Service transparency values for overhead bytes 11-3
12-1
TriFEC-capable circuit packs 12-2

Description of TriFEC 12-2
Improved link budgets 12-4
Forward error correction provisioning 12-8
Editing the forward error correction mode 12-10
Querying the forward error correction mode 12-10
Performance monitoring counts for TriFEC-capable circuit packs 12-10
Alarms and alerts affected by TriFEC 12-11
Network applications using TriFEC 12-12
Wavelength Translator and ODPR applications with TriFEC 12-12
Wavelength Combiner application with TriFEC 12-13
Selecting TriFEC-capable or non-TriFEC circuit packs 12-13
Appendix C: Merged XR/WT circuit packs
13-1
Merged XR/WT circuit packs 13-1

Description of merged XR/WT circuit packs 13-1
Merged XR/WT circuit packs in a network 13-2
Traffic mode provisioning for merged XR/WT circuit packs 13-3
Alarms for merged XR/WT circuit packs 13-3
14-1
Short-reach circuit packs 14-1

Description of short-reach optics 14-2
Short-reach circuit packs in a network 14-2
Output power 14-3
15-1
Technical assistance service telephone numbers 15-1
Index
16-1
ix
About this document
The Repeater NE Network Application Guide describes the Repeater network

element and its supported applications. This document contains network
planning information for the Nortel Optical Long Haul 1600 Optical Line
System Repeater applications.
Optical Long Haul 1600 supports the following system applications.
Optical Long Haul 1600 supported applications
Network element
Supported applications
Repeater
Wavelength Translator
Dense regenerator
Wavelength Combiner
Optical dedicated protection ring (ODPR)
MOR Plus amplifier
Amplifier
1600G Amplifier
Optical amplifier shelf
MOR and MOR Plus amplifier
Note: For information on the 1600G Amplifier, refer to the 1600G

Amplifier Unidirectional Network Application Guide (NTY314AL).
Read this document in conjunction with the latest Optical Long Haul 1600
NTP library. Where necessary, this document refers to specific application
guides and Nortel technical publications (NTP).
Unless otherwise indicated, the NTPs and guides in the Optical Long Haul
1600 library cover both SONET and SDH protocols.
x About this document
Audience
The following members of your company are the intended audience of this
application guide:
planners
provisioners
network administrators
transmission standards engineers
References
This document includes the following references:
Optical Long Haul 1600 documents
1600G Amplifier Unidirectional Network Application Guide
(NTY314AL).
1600G Amplifier Unidirectional Optical Layer Applications Guide
(NTY315DX)
100 GHz, MOR Plus, 2 to 32- Optical Layer Applications Guide
(NTY312DX)
200 GHz, MOR/MOR Plus, 2 to 16- Optical Layer Applications Guide
(NTY311DX)
MOR Plus Optical Add/Drop Applications Guide (NTY313DX)
MOR Plus Optical Layer OAM&P Guide (NTY314DX)
Ordering Guide (NTY311KL)
Ethernet Wayside User Guide (NTY317GF)
SONET Orderwire User Guide (NTCA66CA)
SDH Orderwire User Guide (NTCA66DA)
Data Communications Network Planning Guide (NTR710AM)
TL1 Interface Description, 323-1801-190
Installation Procedures, 323-1801-201
System Commissioning and Testing Procedures, 323-1801-222
Security Management Procedures, 323-1801-305
Provisioning and Operations Procedures, 323-1801-310
Protection Switching Procedures, 323-1801-311
Performance Monitoring Procedures, 323-1801-520
Alarm Reference Guide, 323-1801-542
Trouble Clearing and Module Replacement, 323-1801-543
About this document xi
Optical Connect DX documents

Gigabit Ethernet Data User Guide, NTCA65YA
Optical Network Management (formely known as Preside) documents
Preside Applications Platform 9.2.1 Service Pack 1 (SP-1) or 10,
450-3101-XXX
Preside Applications Platform 10.1 Introduction, 450-3101-100
Preside Applications Platform 10.1 Planning Guide, 450-3101-601
Preside Applications Platform 9.2.1 SP1 Introduction, 450-3101-100
Preside Applications Platform 9.2.1 SP1 Planning Guide, 450-3101-601
Standards
The following list contains references to common industry standards that are
referred to in this document:
IEC 60950Safety of Information Technology Equipment, Third Edition,
Corrigendum: 1/2000, 1 April 1999, 540 pages
Telcordia (formerly known as Bellcore) GR-63-CORE Issue 1, October
1995
Telcordia GR-1377
Telcordia GR-78
IEC 60825-2:1993 A1:1997, International Electrotechnical Commission,
Safety of Laser Products: Part 2 Safety of Optical Fibre Communication
Systems, 1993, Amendment 1, 1997.
Nortel document ITI-5004
ECSA committee T1X1.4, T1X1.5 in document T1.105, Optical Interface
Rates and Format Specifications, March 1988
TA-NPL-000436Digital Network Plan, Section 3.3, Issue 1, November
1986
TR-NWT-000063, Issue 5, September 1993, Section 4.6, Airborne
Contaminants
FCC Part 15B, Class A
EN55022, Class A
Telcordia GR-1089-CORE, Class A
Bell Canada TAD 8465, Class A
ICES-003, Class A
ETSI 300 386-2, Class A
Telcordia GR-499, Issue 1
Bell Canada DS 8171
xii About this document
ETSI 300 132-2

EN300 386-2
ETSI 300 132-2
EN 50082-1
The Telecommunications Industry Association (TIA) and the Electronics

Industries Alliance (EIA) accepted RS-232 as a standard in 1997 and
renumbered this standard as TIA/EIA-232. In this document, RS-232 is used
to reflect current labels on the hardware and in the software for Optical Long
Haul 1600.
1-1
Introduction
1-
The Nortel Optical Long Haul 1600 Optical Line System product portfolio
offers multi-service backbone solutions with open optical interfaces, scalable
capacity on dense wavelength division multiplexing (DWDM) Repeater and
Amplifier platforms. Figure 1-1 represents the Optical Long Haul 1600
product architecture.
Figure 1-1
Optical Long Haul 1600 product architecture
OTP2536p
Preside
Open
optical
interfaces
Multi-service,
multi-vendor
environment
Legend
- OPTera Long Haul 1600
- Optical amplifier
- Service-terminating network elements
Optical
add/drop
multiplexer
(OADM)
DWDM backbone
traffic on Optical
dedicated protection
ring (ODPR)
1-2 Introduction
Optical Long Haul 1600 Release 11

Optical Long Haul 1600 Release 11 builds on the functionality of previous
Optical Long Haul 1600 releases (1.53, 2.0, 3.02, 4.02, 5.13, 6.01, 7.01, 9.01
and 10.02). Release 11 supports features supported in previous Optical Long
Haul 1600 releases. Release 11 does not introduce enhancements to the 1600G
Amplifier NE; only to the Repeater NE.
Optical Long Haul 1600 platform

Optical Long Haul 1600 backbones protect previous investments in legacy
systems by maintaining the capability to aggregate existing 2.5 Gbit/s and
10 Gbit/s backbones into a unified DWDM platform.
Optical Long Haul 1600 products conform to the following industry standards:
Telcordia (formerly Bellcore)
Network Equipment Building System (NEBS)

European Telecommunications Standards Institute (ETSI)
American National Standards Institute (ANSI)
International Telecommunications Union-Telecommunications (ITU-T)
(formerly CCITT)
Underwriters Laboratories (UL)
Canadian Standards Association (CSA)
International Organization for Standardization (ISO)
Note: Nortel is actively involved in forums and standards bodies to ensure
that current and new products conform with the directions and evolution of
the telecommunications industry.
Applications supported on the Repeater network element

The following applications are supported on the Repeater network element.
Dense regenerator
Wavelength Combiner
MOR Plus amplifier
Table 1-1 lists the circuit packs supported for each application on the Repeater
network element. Certain circuit packs can be used in several applications.
The Repeater network element interworks with the 1600G Amplifier network
element. For information, refer to 1600G Amplifier Unidirectional Network
Application Guide (NTY314AL).
Introduction 1-3
Table 1-1
Supported circuit packs for Repeater network element applications
Application
Circuit pack
PEC
2.5G WT
NTCA70xx
Dual 2.5G WT on/off ramp
NTCA72xx
10G WT SR (TriFEC)
NTWR07AA
10G WT
NTCA07xx
10G WT (TriFEC)
NTCF07xx
OC-192/STM-64 XR/WT
NTCF04xx
OC-192/STM-64 XR
NTCA04xx
OC-192/STM-64 XR/WT
NTCF04xx
OC-48/STM-16 T/R SR
NTCA30CK
OC-48/STM-16 DWDM T/R
NTCA30xK
OC-48/STM-16 T/R (1310 nm)
NTCA30AL
OC-192/STM-64 T/R
NTCA06xx
OC-192/STM-64 T/R (TriFEC)
NTCF06xx
External synchronization interface (ESI)
NTCx44xx
Timing distribution (TD)
NTCA21AA
Dual Gigabit Ethernet (GE)
NTCA90xA
Dense regenerator
Wavelength Combiner (see Note)
1-4 Introduction
Table 1-1 (continued)
Supported circuit packs for Repeater network element applications
Application
Circuit pack
PEC
Optical dedicated protection ring

(ODPR)
10G WT SR (TriFEC)
NTWR07AA
10G WT
NTCA07xx
10G WT (TriFEC)
NTCF07xx
OC-192/STM-64 XR/WT
NTCF04xx
OC-192/STM-64 XR
NTCA04xx
Optical switch module
NTCA39AA
MOR Plus amplifier (with and without OSC)
NTCA11xK
MOR Plus amplifier
Note: A Repeater network element equipped with at least one Wavelength Combiner circuit pack group
requires two ESI and two half-height TD circuit packs. If slot 5 (G4A and G4B) of the main shelf
(required for the TD circuit packs) is already in use, then you cannot add Wavelength Combiners until
the existing service is removed.
For circuit pack engineering rules, refer to Mechanical specifications on

page 9-1.
For a complete list of supported circuit packs, refer to Ordering Guide
(NTY311KL).
Full-fill Repeater network element
The Repeater network element can support different applications within one
bay for maximum use of the bay footprint.
Figure 1-2 shows an example of a Repeater network element that supports
multiple system applications.
All supported applications must respect existing power and thermal
engineering rules. For circuit pack engineering rules, refer to Mechanical
specifications on page 9-1.
Introduction 1-5
Figure 1-2
Flexible full-fill Repeater network element (supporting multiple applications)
OTP3001p
Ethernet Wayside
Ethernet Wayside
PT
OW
POPI
PT
ESI
ESI
128M MI
MX
MX
POPC
32M SC
POPS
Breaker filter
Breaker Interface Panel (BIP)
Breaker filter
Attention
When you equip TriFEC-capable
circuit packs, you must follow all
TriFEC thermal, power and
engineering rules.
Control
shelf
(Shelf ID: 1)
Air Intake
Local Craft Access Panel
Fiber Management Tray (FMT)
G9
2.5G WT
OC-48/STM-16
DWDM T/R
OC-48/STM-16
DWDM T/R
G8
OC-192/STM-64
XR/WT
TD
10G WT
OC-192/STM-64 T/R
OSM
OC-192/STM-64 XR/WT
Note 2: Do not mix circuit pack traffic

mode (REGEN for XR or 3R for WT)
within the same ODPR circuit pack group.
G7
10G WT
OSC
G3 G4B G5 G6
2.5G WT
MOR Plus
G2
10G WT
Note 1: A network element equipped

with at least one Wavelength Combiner
circuit pack group requires two ESI and
two half-height TD circuit packs.
OC-48/STM-16
DWDM T/R
OC-48/STM-16
DWDM T/R
OSC
G1
G4A
2.5G WT
MOR Plus
G0
10G WT
TD

Air Exhaust
G10 G11 G12 G13 G14 G15 G16 G17 G18 G19
10G WT
10G WT
2.5G WT
10G WT
2.5G WT
OC-192/STM-64
XR/WT
OC-192/STM-64 XR
OC-192/STM-64 XR/WT
Note 5: Be sure to follow the

appropriate equipping rules when you
equip MOR Plus amplifier circuit packs
in the first four slots of the main shelf.
OC-192/STM-64 XR/WT
Note 4: Equip one or two Ethernet

Wayside circuit packs in slot 16 (G5)
and slot 17 (G6) of the control shelf for
point-to-point and continuity of Ethernet
communication. The network element
must also be equipped with MOR Plus
amplifier circuit packs.
OC-192/STM-64 XR
Note 3: ODPR does not support

2.5 Gbit/s circuit packs.
Main
shelf
(Shelf ID: 2)
Environmental
control panel
(ECP) houses
three fans
Extension
shelf 1
(Shelf ID: 3)
Environmental
control panel
(ECP) houses
three fans
Extension
shelf 2
(Shelf ID: 4)
G20 G21 G22 G23 G24 G25 G26 G27 G28 G29
1-6 Introduction
Product upgrade paths

The supported upgrade paths to the Optical Long Haul 1600 Release 11 load
are:
Optical Long Haul 1600 Release 9.01
Optical Long Haul 1600 Release 10.01 and 10.02
In-service upgrades from previous releases are performed as in previous
in-service upgrades. An upgrade is not traffic affecting.
ATTENTION
You cannot commission an Optical Long Haul 1600 bay as a Combiner
network element in Release 6 and subsequent releases. The Combiner
network element is no longer a supported network element type. In-service
Combiner network elements are transparently converted to Repeater network
elements as part of the upgrade process beginning with Release 6.
An upgrade to Release 6 or later converts a Combiner network element to a
Repeater network element transparently. Existing Combiner network elements
do not require decommissioning and then recommissioning to Repeater
network elements. The upgrade does not change G-naming positions in the
bay. Configuration engineering rules for all applications remain valid for the
new Repeater network element.
For more information on G-naming, refer to Mechanical specifications on
page 9-1.
Network element commissioning
Figure 1-3 shows the commissioning command for a Repeater network

element.
Figure 1-3
Commissioning a Repeater network element (example)
OTP2261t
uncommissioned>
Enter the NE number:
[ 1-65534 ]
? 1621
Enter the standard:
[ SONET, SDH ]
? sonet
Enter the NE type:
REPEATER
- Repeater for SONET
[ REPEATER ]
? repeater
Introduction 1-7
Note: The network element user interface (NE UI) screen for an
uncommissioned network element does not allow you to perform an LED
(light-emitting diode) test for the Repeater bay. When the network element
is commissioned, you can perform an LED test from the network element
submenu.
For more information on product upgrade paths, refer to Product upgrade
paths on page 7-4.
Interoperability
A minimum baseline is required for Optical Network Management and other
products to operate with Optical Long Haul 1600 Release 11.
For more information on interoperability, refer to Optical link
interoperability on page 7-37.
Network management
Optical Network Management Applications Platform is a software application
that provides a single point of access to the existing operations, administration,
maintenance, and provisioning functions for managing your network.
For more information on network management, refer to Network
management on page 7-74.
Optical Long Haul 1600 application interworking

Optical Long Haul 1600, Optical Connect DX, Optical Connect HDX, Optical
Long Haul DT, Optical Multiservice Edge 6500 Broadband, and Optical
Network Management platforms interwork to provide an end-to-end, open
network solution that is flexible, scalable and fault-tolerant.
The Optical Long Haul 1600, Optical Long Haul DT, and Optical Multiservice
Edge 6500 Broadband platforms enable the optical layer framework for
long-haul applications. The Optical Connect DX and Optical Connect HDX
platforms act as bandwidth management hubs and provide the multiplexing
layer. Optical Network Management is an integrated network management
software package that optimizes the capabilities of the Optical Long Haul
1600, Optical Long Haul DT, Optical Multiservice Edge 6500 Broadband,
Optical Connect DX, and Optical Connect HDX platforms. Optical Network
Management lets network managers perform preventive maintenance and fault
isolation from a central location, simplifying and reducing the costs associated
with network management.
See Figure 1-4 for a network view of application interworking with 1600G
Amplifiers. Optical Long Haul 1600 Release 11 interworks with Optical
Network Management (formely known as Preside) Applications Platform
9.2.1 SP1 or 10, Optical Connect DX Release 4, Optical Connect HDX
1-8 Introduction
Release 2, Optical Long Haul DT Release 1, and Optical Multiservice Edge

1.5. For details on these products, refer to their respective Nortel technical
publication (NTP) libraries.
Figure 1-4
Application interworking with 1600G Amplifiers
OTP3489p
Preside
Optical
OPTera Long
Haul 1600 ODPR
OPTera Long
Haul 1600
Combiner,
Wavelength
Translator, and
Dense Regenerator
1600G Amplifier
OPTera
Connect DX
OPTera Long
Haul DT
OPTera
Connect HDX
2-1
2-
Chapter overview
This chapter provides a detailed description of the Dense regenerator
application supported by the Repeater network element.
The following topics are covered in this chapter.
Section
Page
Description of the Dense regenerator application
2-1
Supported circuit packs for the Dense regenerator application
2-2
Overhead processing
2-7
Dense regenerator application in a network
2-8
Description of the Dense regenerator application

Introduced in Optical Long Haul 1600 Release 1.2, the OC-192/STM-64 XR
single circuit pack supports full 10 Gbit/s SONET/SDH regeneration. The
OC-192/STM-64 XR circuit pack reshapes, retimes, and reamplifies (3R
regeneration) the incoming signal. Unlike the 10G WT, the OC-192/STM-64
XR circuit pack regenerates the entire SONET/SDH overhead. The
OC-192/STM-64 XR circuit pack therefore does not provide transparency of
services but maintains SONET data communication over the network.
Note: Forward error correction (FEC) is not available on Dense
regenerator circuit packs because FEC is expected to be performed at
terminal sites by the on-ramp and off-ramp circuit packs. FEC is not
required at regenerator sites.
See Circuit pack maximum and optical jitter on page 8-2 for details on jitter
specifications and the maximum number of circuit packs an optical signal can
pass through.
2-2 Dense regenerator application
Supported circuit packs for the Dense regenerator application

The Dense regenerator application allows provisioning for the Dense
regenerator circuit packs listed in Table 2-1.
Two Dense regenerator circuit packs are required for each 10 Gbit/s channel to
achieve full SONET/SDH data communication integrity: one circuit pack for
eastbound traffic and one circuit pack for westbound traffic.
Table 2-1
Supported Dense regenerator circuit packs
Circuit pack (see Note 1 and Note 2) PEC
Introduced in release
Notes
OC-192/STM-64 XR
NTCA04xx
1.2
OC-192/STM-64 XR/WT
NTCF04xx
See Note 3.
NTCA72xx
See Note 4.
Note 1: For a complete list of network element applications and supported circuit packs, refer to Table
1-1 on page 1-3.
Note 2: For circuit pack positioning and sparing rules, refer to Mechanical specifications on page 9-1.
Note 3: For information on merged XR/WT circuit packs, refer to Appendix C: Merged XR/WT circuit
packs on page 13-1.
Note 4: Although the Dual 2.5G WT on/off ramp is intended for applications at terminal sites, it can also
be deployed in a pair at a Regenerator site to provide 2.5Gbit/s signal regeneration. See Dual 2.5G WT
on/off ramp circuit pack (NTCA72xx) on page 2-3. For more information on the Dual 2.5G WT on/off
ramp circuit pack, see Chapter 3, Wavelength Translator application.
Note 5: This circuit pack is also supported on a Repeater NE running Release 9.01.
OC-192/STM-64 XR circuit packlegacy (NTCA04xx)

The OC-192/STM-64 XR circuit pack is a single regenerator circuit pack that
receives, regenerates, and transmits 10 Gbit/s signals that have been sent over
long distances on an optical link. The OC-192/STM-64 XR circuit pack
operates as a full 10 Gbit/s SONET/SDH regenerator. The OC-192/STM-64
XR circuit pack has a transmitter output port and a receiver input port. The
transmitters use distributed feedback (DFB) semiconductor laser technology.
These transmitters also provide provisionable output power, chirp, and analog
maintenance (AM) setting. Analog maintenance 2 (AM2) is required for
1600G Amplifier optical links. AM1 is required for MOR Plus amplifier
systems.
The OC-192/STM-64 XR circuit packs are available for all wavelength grids.
Dense regenerator application 2-3
OC-192/STM-64 XR/WT circuit pack (NTCF04xx)

The OC-192/STM-64 XR/WT circuit pack transmits at a fixed wavelength and
is specifically designed for regenerator sites. As with other merged XR/WT
circuit packs, you can provision the traffic mode to either 3R for WT or
REGEN for XR. The default traffic mode is REGEN.
When the traffic mode on the OC-192/STM-64 XR/WT circuit pack is set to
REGEN, this circuit pack provides the same functionality as the
OC-192/STM-64 XR circuit pack (NTCA04xx). When the traffic mode on the
OC-192/STM-64 XR/WT circuit pack is set to 3R, this circuit pack provides
the same level of transparency as the 10G WT circuit pack (NTCA07xx).
The OC-192/STM-64 XR/WT circuit pack is available for Red and Blue
wavelengths for MOR Plus amplifier applications, and for Grid 1 to Grid 4
wavelengths for 1600G Amplifier applications.
For more information on merged XR/WT circuit packs, refer to Appendix C:
Merged XR/WT circuit packs on page 13-1.
Dual 2.5G WT on/off ramp circuit pack (NTCA72xx)
The Dual 2.5G WT on/off ramp circuit pack is a single, full-height circuit pack
that houses two 2.5 Gbit/s facilities. Each facility consists of a 2.5 Gbit/s
transmitter and receiver.
The transmitter of one facility is a DWDM laser for transmission of signals on
the optically amplified line. The transmitter of the second facility is equipped
with short-reach optics. The on-ramp 2.5 Gbit/s DWDM service is transmitted
on the optically amplified line and the co-located 2.5 Gbit/s service in the
opposite direction provides short-reach off-ramp transmission (see Figure
2-1). Both facilities support C-band wavelengths only.
The DWDM laser of the dual 2.5G WT on/off ramp circuit pack supports both
AM1 and AM2. Provision the AM setting according to your application:
AM2 for interworking with 1600G Amplifier applications
AM1 for interworking with MOR Plus applications
The default AM setting is AM2. The short-reach optics of the dual 2.5G WT
on/off ramp circuit pack do not support either version of AM.
The Repeater network element can support up to sixty 2.5 Gbit/s facilities
within a bay equipped with Extension shelf 2, increasing the 2.5 Gbit/s
capability of a full-filled Repeater network element from 75 Gbit/s to
150 Gbit/s.
For details on Dual 2.5G WT on/off ramp circuit packs, refer to Chapter 10,
Circuit pack technical specifications. For details on the Wavelength
Translator application, see Chapter 3, Wavelength Translator application.
Note: The Dual 2.5G WT on/off ramp circuit pack does not support
provisionable forward error correction (FEC).
Regenerator site application
A pair of Dual 2.5G WT on/off ramp circuit packs can provide a regeneration
function. To perform regeneration using dual 2.5G WT on/off ramp circuit
packs, it is recommended that you configure the dual 2.5G WT on/off ramp
circuit packs as shown in the top portion of Figure 2-1.
For each direction, the DWDM signal is received at Port 2 (Rx) of one Dual
2.5G WT on/off ramp circuit pack. The short-reach transmit port (Port 2 Tx)
of this circuit pack is connected to Port 1 (Rx) on the other Dual 2.5G WT
on/off ramp circuit pack. The DWDM transmit port (Port 1 Tx) of the second
circuit pack provides the DWDM output signal. For the location of the ports
on the Dual 2.5G WT on/off ramp circuit pack, see Dual 2.5G WT on/off
ramp circuit pack (NTCA72xx) on page 10-24.
CAUTION
Risk of damage to circuit packs
The Optical Long Haul 1600 Dual 2.5G WT circuit pack

(NTCA72xx) can be damaged if too much optical power
reaches the Long Reach Receiver (port 2). The recommended
power level for that Receiver is 17 dBm, and the maximum
power supported for an amplified link is 12 dBm. Always
check the power before connecting the receiver. The power
should never exceed 8 dBm, even during testing. Note that
these power levels are significantly lower than those for
equivalent 10 Gbit/s applications.
The configuration in the lower half of Figure 2-1 is not recommended as it is
not supported by current Optical Network Management releases.

Figure 2-1
Signal flow in Dual 2.5G WT on/off ramp circuit packs in a regenerator
application
OTP3409p
Port 1
Port 2
DWDM
Rx
Tx
Rx
Tx
Tx
Rx
Tx
Rx
DWDM
Port 2
Port 1
Supported configuration
(Connection between ports on different circuit packs)
Port 1
Port 2
Rx
Tx Rx
Tx
DWDM
Port 2
Port 1
DWDM
Tx
Rx Tx
Rx
Non-supported configuration
(Loopback between ports on same circuit pack)
Legend
= fiber-optic patch cord
Figure 2-2 shows an application using the Dual 2.5G WT on/off ramp circuit
packs at a regenerator site.

Figure 2-2
Dual 2.5G WT on/off ramp circuit packs in a regenerator application
OTP3383p
Terminal site 1
Regenerator site
Terminal site 2
DWDM optics
Port1
Rx
Tx
On ramp
Port2
Tx
Rx
Off ramp
n+1
n+1
Port 2
Port 1
Rx Tx
Rx Tx
Tx Rx
Tx Rx
Port 1
Port 2
n
n+1
Port2
Rx
Tx
Off ramp
n+1 Port1
Tx
Rx
On ramp
n
DWDM optics
Legend
= fiber-optic patch cord
Note: For 1600G Amplfier configurations,

ln and ln+1 can be the same wavelength.
Engineering rules for regenerator configurations
The following lists the engineering rules and restrictions for the Dual 2.5G WT
on/off ramp circuit packs in a regenerator configuration:
The Dual 2.5G WT on/off ramp circuit packs can be equipped in any slot
or bay. Therefore, the adjacent slot is not reserved or alarmed.
The optical fiber patch cords used to connect the signal between the Port 2
Tx on one Dual 2.5G WT on/off ramp circuit pack and the Port 1 Rx on the
other Dual 2.5G WT on/off ramp circuit pack should be routed via the
optical fiber guides at the side of the bay (store the optical fiber slack on
the optical fiber guides).
Note: If the two Dual 2.5G WT on/off ramp circuit packs forming the
regenerator are in different sides of the bay (for example, G5 and G6), the
optical fibers connecting the circuit packs will have to be routed to the side
of the bay, off the bay (above or below depending on configuration), and
then back on the other side of the bay.
You can deploy a maximum of seven regenerator sites (14 Dual 2.5G WT
on/off ramp circuit packs in cascade) between line terminating equipment
(LTE).
Overhead processing
Table 2-2 shows a summary of the service transparency features of a Dense
regenerator circuit pack.
Note 1: For descriptions of overhead byte functions and service
transparency values, refer to Appendix A: Overhead processing on page
11-1.
Note 2: For specific instructions on changing the value of a provisionable
byte, refer to Provisioning and Operations Procedures, 323-1801-310.
Note 3: Overhead processing described in this table does not apply to the
Dual 2.5G on/off ramp WT. For overhead processing for the Dual 2.5G
on/off ramp WT, see Table 3-3 on page 3-7.
Table 2-2
Dense regenerator service transparency
Transport overhead
bytes
Service transparency
A1, A2
Regenerated
B1
Recalculated
B2
Passthrough
C1 (J0)
Provisionable: interleave or section trace
D1, D2, D3
Recalculated
E2
Transparent
E1, F1
Terminated
K1, K2
Transparent: insertion of AIS-L upon signal degradation
D4-D12
Transparent
S1
Transparent
Z1-Z2
Transparent
Other bytes
Application dependent
Dense regenerator application in a network

Dense regenerator circuit packs extend system reach by reconstituting the
optical signal in each direction at an intermediate point between two
service-terminating locations. If required, multiple-cascaded Dense
regenerator circuit packs are deployed along with optical amplifiers to extend
system reach by hundreds of kilometers. Unlike traditional SONET/SDH
regenerator network elements, Optical Long Haul 1600 supports as many as
30 Dense regenerator circuit packs in a single seven-foot bay. This efficient
use of space yields substantial savings in capital equipment costs, operational
costs, and footprint requirements when compared to traditional solutions.
Example of Dense regenerator application in a network
Figure 2-3 shows an example of the Dense regenerator application in an

optical network.
Figure 2-3
Example of a Dense regenerator application in a network
OTP2955p
OPTera
Connect DX
OPTera
Connect DX
Repeater
Dense
regenerator
T/R 10
G
10G WT
10G WT
XRs
2.5G WT
2.5G WT
Mux/
Demux
Note:
T/R
10
Mux/
Demux
Mux/
Demux
Mux/
Demux
The client-facing equipment's TFEC setting must be turned off for

correct interoperability with other vendors.
Example of a Dense regenerator application in a Repeater bay
Figure 2-4 shows an example of a full-fill Repeater network element

supporting the Dense regenerator application.

Figure 2-4
Repeater network element (Dense regenerator application)
OTP3003p
Breaker interface panel (BIP)

Ethernet Wayside
Ethernet Wayside
9 10 11 12 13 14 15 16 17
PT
OW
POPI
PT
Filler
Filler
128M MI
MX
MX
POPC
32M SC
3 4 5
POPS
Breaker filter
Breaker filter
Control shelf
(Shelf ID: 1)
Air Intake
Local Craft Access Panel (LCAP)
Air Exhaust

appropriate equipping rules when
you equip MOR Plus amplifier circuit
packs in the first four slots of the
main shelf.
10
XR
XR
G9
XR
G8
XR
G7
XR
G6
XR
G5
XR
G4
XR
G3
XR
G2
XR
XR
10
XR
XR
XR
XR
XR
G1
G10 G11 G12 G13 G14 G15 G16 G17 G18 G19
10
XR
XR
XR
XR
XR
XR
XR
XR
XR

or slot 17 (G6) of the control shelf
for point-to-point and continuity of
Ethernet communication. Be sure
to equip the network element with
MOR Plus amplifier circuit packs.
G0
XR
Note 1: All slots in the main

shelf, extension shelf 1, and
extension shelf 2 can contain the
following circuit packs:
OC-192/STM-64 XR or
OC-192/STM-64 XR/WT.
MOR Plus (RedPost/

BluePre) MSA Post
MOR Plus (RedPost/
BluePre) MSA Post
MOR Plus (RedPre/
BluePost) MSA Pre
MOR Plus (RedPre/

BluePost) MSA Pre
Main
shelf
(Shelf ID: 2)
Environmental
control panel
(ECP) houses
three fans
Extension
shelf 1
(Shelf ID: 3)
Environmental
control panel
(ECP) houses
three fans
Extension
shelf 2
(Shelf ID: 4)
G20 G21 G22 G23 G24 G25 G26 G27 G28 G29
3-1
3-
Chapter overview
This chapter provides a detailed description of the Wavelength Translator
Section
Page
Description of the Wavelength Translator application
3-1
Supported circuit packs for the Wavelength Translator

application
3-2
Overhead processing
3-6
Wavelength Translator application with TriFEC
3-12
WAN PHY support in Optical Long Haul 1600
3-16
Wavelength Translator application in a network
3-19
Description of the Wavelength Translator application

A Wavelength Translator (also known as a transponder) is a circuit pack that
translates one wavelength into another. This capability is useful for mapping
legacy wavelengths onto the ITU-T compliant dense-wavelength division
multiplexing (DWDM) wavelength grid. Wavelength Translators reshape,
reamplify, and retime (3R regeneration) a signal without regenerating the
entire SONET/SDH overhead. Because of its minimal overhead (OH)
processing and monitoring capability, a Wavelength Translator is also known
as a thin SONET/SDH regenerator. Wavelength Translators provide an
enhanced level of transparency for wavelength leasing alternatives.
The Wavelength Translator does not terminate section/RS or line/MS data
communications channel (DCC) (D1 to D3 and D4 to D12, respectively). You
must use the optical service channel (OSC) to support full DCC-like
operations, administration, maintenance, and provisioning (OAM&P) access
to all network elements on the optical line/MS.
3-2 Wavelength Translator application
See Circuit pack maximum and optical jitter on page 8-2 for details on jitter
specifications and the maximum number of circuit packs an optical signal can
pass through.
Supported circuit packs for the Wavelength Translator application

The Wavelength Translator application allows provisioning for the
Wavelength Translator circuit packs listed in Table 3-1.
Table 3-1
Supported Wavelength Translator circuit packs
Circuit pack (see Note 1 and Note 2) PEC
Introduced in release Notes
2.5G WT
NTCA70xx
1.5
10G WT
NTCA07xx
1.5
10G WT (TriFEC)
NTCF07xx
See Note 3.
10G WT SR (TriFEC)
NTWR07AA
See Note 3, and

Note 4.
OC-192/STM-64 XR/WT
NTCF04xx
See Note 5.
NTCA72xx
See Note 6.
1-1 on page 1-3.
Note 3: For information on TriFEC circuit packs, refer to Wavelength Translator application with
TriFEC on page 3-12 and Appendix B: TriFEC applications on page 12-1.
Note 4: For information on short-reach optics, refer to Appendix D: Short-reach optics on page 14-1.
packs on page 13-1.
Note 6: For information on Dual 2.5G WT on/off circuit packs, refer to Chapter 10, Circuit pack
technical specifications.
2.5G WT and 10G WT circuit packslegacy (NTCA70xx and NTCA07xx)

Wavelength Translators condition 2.5 Gbit/s or 10 Gbit/s services for DWDM
long-haul transport in a multivendor environment. Translated optical signals
are regenerated, reshaped, and retimed (3R regeneration) for optimum
performance over a DWDM backbone. Open optical interfaces allow
transparent interworking with virtually any SONET, SDH, IP, or ATM
2.5 Gbit/s or 10 Gbit/s network elements not equipped with
DWDM-compatible optics. The 2.5G WT circuit pack (NTCA70xx) and
10G WT circuit pack (NTCA07xx) have a transmitter output port and a
receiver input port. The transmitters use distributed feedback (DFB)
semiconductor laser technology. These transmitters also provide provisionable
output power and chirp setting.
Wavelength Translator application 3-3
Chirp setting is provisionable only on the 10G WT circuit packs. Analog

maintenance 2 (AM2), which is required for interoperability with the 1600G
Amplifier, is only available on the 10G WT circuit pack. As such, the 10G WT
circuit pack is available for all wavelength grids, whereas the 2.5G WT circuit
pack is only available for the MOR/MOR Plus amplifier wavelength grids.
The legacy 2.5G WT and 10G WT circuit packs do not support forward error
correction (FEC).
10G WT (TriFEC) circuit pack (NTCF07xx)
The 10G WT (TriFEC) circuit pack (NTCF07xx) is similar to the 10G WT
circuit pack (NTCA07xx) but supports triple forward error correction
(TriFEC) for improved link budgets.
For details on TriFEC, refer to Wavelength Translator application with
10G WT SR (TriFEC) circuit pack (NTWR07AA)
Designed for short-reach applications, the 10G WT SR (TriFEC) circuit pack
transmits at up to distances of approximately 20 km. This distance is ideal for
inter-office applications. The 10G WT SR (TriFEC) circuit pack retains all the
transparency benefits of the 10G WT circuit pack (NTCA07xx), with a
specific application for off-ramp short-distance transmissions.
Note: The 10G WT SR (TriFEC) circuit pack has forward error correction
detection capability on the receiver only. The transmitter does not provide
forward error correction capability.
For details on TriFEC, refer to Wavelength Translator application with
For details on short-reach optics, refer to Appendix D: Short-reach optics on
page 14-1.
The OC-192/STM-64 XR/WT circuit pack transmits at a fixed wavelength and
is specifically designed for regenerator sites. As with other merged XR/WT
circuit packs, you can provision the traffic mode to either 3R for WT or
REGEN for XR. The default traffic mode is REGEN.
When the traffic mode on the OC-192/STM-64 XR/WT circuit pack is set to
REGEN, this circuit pack provides the same functionality as the
OC-192/STM-64 XR circuit pack (NTCA04xx). When the traffic mode on the
OC-192/STM-64 XR/WT circuit pack is set to 3R, this circuit pack provides
the same level of transparency as the 10G WT circuit pack (NTCA07xx).
The OC-192/STM-64 XR/WT circuit pack is available for Red and Blue
For details on merged XR/WT circuit packs, refer to Appendix C: Merged
XR/WT circuit packs on page 13-1.
The Dual 2.5G WT on/off ramp circuit pack is a single, full-height circuit pack
that houses two 2.5 Gbit/s facilities. Each facility consists of a 2.5 Gbit/s
transmitter and receiver.
The transmitter of one facility is a DWDM laser for transmission of signals on
the optically amplified line. The transmitter of the second facility is equipped
with short-reach optics. The on-ramp 2.5 Gbit/s DWDM service is transmitted
on the optically amplified line and the co-located 2.5 Gbit/s service in the
opposite direction provides short-reach off-ramp transmission (see Figure
3-1). Both facilities support C-band wavelengths only.
The DWDM laser of the dual 2.5G WT on/off ramp circuit pack supports both
AM1 and AM2. Provision the AM setting according to your application:
AM2 for interworking with 1600G Amplifier applications
AM1 for interworking with MOR Plus applications
The default AM setting is AM2. The short-reach optics of the dual 2.5G WT
on/off ramp circuit pack do not support either version of AM.
The Repeater network element can support up to sixty 2.5 Gbit/s facilities
within a bay equipped with Extension shelf 2, increasing the 2.5 Gbit/s
capability of a full-filled Repeater network element from 75 Gbit/s to
150 Gbit/s.
CAUTION
Risk of damage to circuit packs
The Optical Long Haul 1600 Dual 2.5G WT circuit pack

(NTCA72xx) can be damaged if too much optical power
reaches the Long Reach Receiver (port 2). The recommended
power level for that Receiver is 17 dBm, and the maximum
power supported for an amplified link is 12 dBm. Always
check the power before connecting the receiver. The power
should never exceed -8 dBm, even during testing. Note that
these power levels are significantly lower than those for
equivalent 10 Gbit/s applications.

Figure 3-1
Dual 2.5G WT on/off ramp circuit packs at terminal sites
OTP3366p
Terminal site 1
Terminal site 2
SR optics
DWDM optics
Port1
Rx
Tx
On ramp
Port2
Tx
Rx
Off ramp
n
n+1
SR optics
Port1
Rx
Tx
Off ramp
n+1 Port2
Tx
Rx
On ramp
n
DWDM optics
For details on Dual 2.5G WT on/off ramp circuit packs, refer to Chapter 10,
Circuit pack technical specifications.
Note: The Dual 2.5G WT on/off ramp circuit pack does not support
provisionable forward error correction (FEC).
Interworking
The Repeater network element supports both single and dual 2.5 Gbit/s circuit
packs in the same network element. Single 2.5 Gbit/s WT and dual 2.5 Gbit/s
circuit packs interwork with other circuit packs, as summarized in Table 3-2.
On-ramp applications
A single 2.5 Gbit/s WT circuit pack can feed a MOR Plus circuit pack
amplifying a mixed set of wavelengths that are transmitted from other
dual 2.5 Gbit/s circuit packs and single 2.5 Gbit/s circuit packs.
A single 2.5G WT circuit pack functions correctly (alarm-free) when it
receives a wavelength from a Dual 2.5G WT on/off ramp circuit pack.
Off-ramp applications
A single 2.5 Gbit/s WT circuit pack can receive a wavelength from a
MOR Plus amplifier circuit pack amplifying a mixed set wavelengths
that are transmitted from other dual 2.5 Gbit/s circuit packs and single
A Dual 2.5G WT on/off ramp circuit pack functions correctly
(alarm-free) when it receives a wavelength from a single 2.5G WT
circuit pack.

Table 3-2
Single and dual 2.5 Gbit/s circuit pack interworking
Receive
Transmit
2.5G WT
Dual 2.5G WT
(on or off
ramp)
Amplifier
interoperability
MOR Plus
1600G
Amplifier
2.5G WT
Yes
Yes
Yes
No (see
Note)
Dual 2.5G WT
(on ramp)
Yes
Yes
Yes
Yes
Dual 2.5G WT
(off ramp)
Yes
(equipped with
short-reach
optics)
Yes
(equipped with
short-reach
optics)
No
No
(equipped (equipped
with
with
short-reach short-reach
optics)
optics)
Note: AM2, which is required for interoperability with the 1600G Amplifier, is not
available on single 2.5G WT circuit packs.
Overhead processing
All overhead bytes, except for the following bytes, are transparent to the
Wavelength Translator:
A1 and A2 framing bytes: Framing is used to identify the byte and frame
limits of the incoming serial bit stream. The A1 and A2 bytes received at
the WT are processed to detect the frame pattern and align to it. This
processing allows detection of the short-term status of alignment (SEF)
and the long-term status of alignment (LOF).
B1 byte: B1 is a BIP-8 parity check used to determine if the transmitted
data has any errors. This byte is used to calculate several PM statistics and
applies to the regenerator section only.
C1 (J0) bytes: The section trace (J0) is a 64 Kbit/s channel and is the
C1 byte in STS-1 #1 of the SONET signal or the C1 byte in STM-1 #1 of
the SDH signal. To effectively manage optical interconnections between
carriers, section trace is used to detect potential errors in optical fiber
connections.
Table 3-3 shows a summary of the service transparency features of a
Wavelength Translator circuit pack.
Note 1: For details on overhead byte functions and service transparency
values, see Appendix A: Overhead processing on page 11-1.
Note 2: For instructions on changing the value of a provisionable byte,

refer to Provisioning and Operations Procedures, 323-1801-310.
Table 3-3
Wavelength Translator service transparency
Transport
Overhead bytes
Service transparency
A1, A2
Regenerate
B1
Provisionable: recalculated or passthrough (see Note 1 and 2)
B2
Passthrough
C1 (J0)
Provisionable: insert, passthrough, or user-defined
D1, D2, D3
Transparent
E1, E2
Transparent
F1
Transparent
K1, K2
Transparent: insertion of AIS-L upon signal degradation
D4-D12
Transparent
S1
Transparent
Z1-Z2
Transparent
Others
Application dependent
Note 1: To enable FEC or TriFEC functionality, you must set B1 to recalculate.

Note 2: Editing the B1 mode may cause a short traffic hit, which generates
performance monitoring counts.
Note: The DCC is transparent to the WT and cannot be accessed. Use an

external DCC channel (for example, OSC) to guarantee data
communication between each Repeater network element that houses
Wavelength Translators in a network.
Transparent FEC bytes
When error correction is provisioned to FEC or TriFEC, parity is inserted into
the FEC or TriFEC bytes of the SONET/SDH overhead. When error correction
is provisioned to NONE, the overhead bytes are transparent. This feature
allows subtending equipment carriers to offer transport services using the
undefined overhead bytes in the SONET or SDH overhead.
For details on error correction, see Wavelength Translator application with
B1 and C1 (J0) bytes provisioning

Transparency provisioning allows you to determine how to process the B1 and
C1 (J0) bytes in the SDH/SONET signal.
You can set the B1 byte to recalculate or passthrough (see Table 3-4 for
supported values by circuit pack). When you provision the B1 byte setting to
recalculate, the B1 byte content is processed to generate performance
monitoring (PM) statistics, and is then regenerated. When you provision the
B1 byte setting to passthrough, the B1 byte content is passed through but
monitored for error detection.
Table 3-4
B1 provisioning
Circuit pack
PEC
B1 provisioning
PASSTHRU
RECALCULATE
10G WT
NTCA07xx
Supported
Supported
2.5G WT
NTCA70xx
Supported
Supported
Dual 2.5G WT on/off ramp NTCA72xx
Supported
Supported
OC-192/STM-64 XR/WT
(in 3R mode)
NTCF04xx
Supported
Supported
10G WT (TriFEC)
NTCF07xx
Supported only if Tx FEC and Rx FEC

are set to None.
Supported
10G WT SR (TriFEC)
NTWR07AA
Supported only if Tx FEC and Rx FEC

are set to None.
Supported
Note: To set the section parity (B1) to PASSTHRU, you must first set the section trace mode (J0/C1)
to PASSTHRU.
You can set the C1 (J0) byte to C1 insert, J0 user-defined, or C1 passthrough.

C1 insert is used in 2.5 Gbit/s links to simplify interoperability with legacy
OC-48/STM-16 regenerators that use the C1 byte for framing (see Legacy
interoperability on page 3-9). J0 user-defined allows the section trace to be
provisioned at the transmitter site with a number or a text string, as well as at
the receiving site for matching purposes. The transmitted section trace and
expected received section trace are set from the NE UI facility menu of each
WT facility. In C1 passthrough mode, the circuit pack does not change
incoming C1 bytes and passes them to the next downstream network element.
If you set B1 to passthrough, then you must set C1 (J0) to passthrough.
Alternatively, if you set B1 to recalculate, you can set C1 (J0) to C1 insert,
user-defined, or passthrough. Refer to Table 3-5 for details.

Table 3-5
B1 and C1 (J0) provisioning for the 10G WT and 2.5G WT circuit packs
B1
C1 (J0)
Comments
Recalculate
C1 insert
C1 bytes interleaving used for framing

(see Note 1)
J0 user-defined
J0 transmit and expected receive can be

provisioned
C1 passthrough
C1 bytes are not altered
C1 passthrough
and J0 disabled
C1 and B1 bytes are not altered

(see Note 2)
Passthrough
Note 1: In a SONET signal, C1 insertion refers to the STS-1 number assignment

in the C1 byte of each STS-1 of an STS-n signal. In an SDH signal, C1 insertion
refers to STM-1 number assignment in the C1 byte of each STM-1 of an STM-n
signal. Available C1 bytes are set to AA. Signals that use the A1 and A2 bytes for
framing are not affected by the C1 interleave insertion mode.
Note 2: J0 disabled and C1 passthrough indicate that the circuit pack does not
change incoming C1 bytes and passes them to the next downstream network
element. You cannot provision section trace when C1 is in passthrough mode (for
example, J0 disabled).
Wavelength leasing application

In wavelength leasing applications, traffic from the end-user must be carried
transparently across a carrier network. In such applications, the B1 and J0
bytes can be set to passthrough. The passthrough setting prevents any
processing, recalculation, and rewriting of the incoming signal but complicates
the sectionalization of faults. To avoid this complication, provision the B1 byte
to recalculate during system lineup and testing (SLAT). When the system is
tested and error free, set the B1 byte to passthrough to ensure transparency.
The same recommendation applies to C1 (J0). Ensure that no optical fiber
connection errors using the J0 (section trace) user-defined setting exist and
later switch to J0 passthrough. In passthrough mode, the input signal reaches
the far-end equipment without modifications to the signals overhead.
Legacy interoperability
Some older SONET/SDH systems (for example, legacy OC-48/STM-16
regenerator) use C1 interleaving for framing. If the source (for example, an IP
router) does not provide C1 interleaving, a WT can be used as a converter to
provide the C1 interleaving for any downstream OC-48/STM-16 regenerators.
In this case, you must set B1 to recalculated and set C1 to C1 insert mode.
Fault sectionalization
Fault sectionalization refers to the process of detecting errors and their
location. The fastest method of sectionalizing faults in a Wavelength
Translator application or ODPR application is by disabling transparency
across the optical line/MS.

B1 byte provisioning functionality for Wavelength Translator applications
If the B1 byte is provisioned as passthrough for Wavelength Translator

applications, the error count increases every time a fault occurs and the total
number of error counts reaches the subtending equipment (see Figure 3-2 on
page 3-11).
The B1 byte is set to recalculated for Dense regenerator applications. As a
result, the Dense regenerator application cannot provide passthrough
capability. You cannot provision the Dense regenerator application to provide
B1 transparency.
To sectionalize faults when B1 is set to passthrough, you must log in to each
Repeater network element in the link and analyze the PM screens. This method
allows you to determine where the counts have started to increase.
Provisioning the B1 byte to passthrough meets the need of some customers for
total service transparency, while still signaling faults to the subtending
equipment. The subtending equipment can then handle the protection
switching. However, in this scenario, sectionalization of faults is a laborious
process.
For a faster and more effective sectionalization of faults solution than logging
into each network element, provision the B1 byte to recalculated for
Wavelength Translator applications. In this scenario, the B1 byte is reset to 00
at every Repeater network element site when no faults are detected within a
span. If an error occurs between two Repeater network elements, the error
counts are displayed on the PM screens of the receiving Repeater network
element. The fault is then localized and acknowledged much faster without
extra calculations. For carriers who require rapid fault detection, B1
recalculated is a valuable solution.
Subtending equipment is still provided with switching capabilities in the event
of a B2 error as the passed through B2 byte is detected at the far-end terminal.

Figure 3-2
Sectionalization of faults for the Repeater network element (example)
OTP0125
Subtending
TBM
Subtending
TBM
B1 = pass-through
B1 = pass-through
B1 = pass-through
B1 = pass-through
B1
ATM
B1
B1
B1
B1
B1 errors
RPT
RPT
RPT
RPT
ATM
B1 errors
Routers
Off ramp
On ramp
Routers
X B2 errors
IP
B1
B1
B1 = recalculated
B2
B1
B1 = recalculated
B1
IP
B1 = recalculated
B1
B1 = recalculated
B2
For information on performance monitoring for the Wavelength Translator

application, refer to Performance monitoring for the Wavelength Translator
and Dense regenerator applications on page 7-11.

Optical Long Haul 1600 Release 5 introduced forward error correction (FEC)
for the Wavelength Translator application. This section provides information
on triple forward error correction (TriFEC) functionality for the Wavelength
Translator application.
For a general description of TriFEC, refer to Appendix B: TriFEC
applications on page 12-1.
Transparency of Wavelength Translator applications with TriFEC
When error correction is disabled on the TriFEC-capable WT circuit packs, the
error correction bytes (single FEC or TriFEC) are transparent. This
transparency allows subtending equipment carriers to offer transport services
using the undefined overhead bytes in the SONET or SDH overhead. (These
undefined bytes are normally used by the single FEC or TriFEC bytes.)
Figure 3-3 shows a network that sectionalizes faults by having the section
parity (B1) set to recalculated, rather than passthrough, at regenerator sites. By
setting B1 to recalculated, transparency is disabled in the network shown in
Figure 3-3.
The configuration shown in Figure 3-3 is also an ideal network setup for initial
turn up since this setup prevents the propagation of errors.
Figure 3-3
Fault sectionalization in a Wavelength Translator application
OTP2514T
SONET
or SDH
Equipment
B1 = recalculated
B1 = recalculated
B1 = recalculated
10G WT
(TriFEC)
10G WT
10G WT
(TriFEC)
10G WT
(TriFEC)
10G WT
10G WT
(TriFEC)
Terminal
Site
Regenerator
Site
Terminal
Site
SONET
or SDH
Equipment
Error correction provisioning

You provision Tx FEC and Rx FEC separately for the TriFEC-capable WT
circuit packs.
ATTENTION
In-service provisioning of FEC modes (either Tx FEC or Rx FEC) is not
supported. Provision the FEC mode during a service interruption (scheduled
maintenance) or before the network is placed in-service.
Table 3-6 lists the supported and default NE UI values for Tx FEC and
Rx FEC.
Table 3-6
Tx FEC and Rx FEC parameter values for TriFEC-capable WT circuit packs
Facility parameter
Supported NE UI values
Default NE UI value
Tx FEC
NONE (no error correction) NONE (no error correction)
(error correction in the FEC (single FEC)

transmit direction)
TFEC (TriFEC)
Rx FEC
NONE (no error correction) NONE (no error correction)
(error correction in the FEC (single FEC)

receive direction)
TFEC (TriFEC)
Note: TFEC refers to the NE UI command for enabling TriFEC. FEC

refers to the NE UI command for enabling single FEC.
When you change the error correction mode on a TriFEC-capable 10G WT
circuit pack, the signal degrade threshold is automatically reprovisioned as
shown in Table 3-7.
Table 3-7
Automatically provisioned signal degrade threshold values
(TriFEC-capable 10G WT circuit packs)
FEC mode
Automatically provisioned signal degrade threshold
TriFEC
1 x 10-6
FEC or None
1 x 10-8
For 10G WT circuit packs, the signal degrade threshold is relevant only if the
circuit packs are part of an ODPR circuit pack group. For details on TriFEC
and signal degrade for ODPR applications, see Signal degrade threshold and
protection switching in ODPR applications on page 5-23.
ATTENTION
For Repeater applications using TriFEC-capable WT circuit packs, you must
set Tx FEC and Rx FEC on the optical-facing link to the same value. If you
do not set Tx FEC and Rx FEC on the optical-facing link to the same value,
the FEC Provisioning Mismatch alarm is raised and FEC will not be
implemented on the optical line/MS. As such, line/MS FEC will not
accumulate on the receiving circuit pack and errors on the link will not be
corrected.
Figure 3-4 on page 3-14 shows an example of a network deployment. The
on-ramp and off-ramp 10G WT (TriFEC) circuit packs at the terminal sites are
provisioned to transmit and receive TriFEC, respectively. The 10G WT circuit
packs (without TriFEC functionality) at the regenerator sites are transparent to
the TriFEC bytes. By provisioning Tx FEC at the on-ramp site to the same
value as Rx FEC at the off-ramp site, TriFEC is enabled on the optical line/MS
and the FEC provisioning mismatch alarm is not raised.
Figure 3-4
Network deployment showing transmit and receive error correction provisioning at terminal sites
(10G WT (TriFEC) circuit packs)
OTP2673t
Rx FEC = NONE
Tx FEC = TFEC
10G WT
(TriFEC)
SONET
or SDH
Equipment
10G WT
(TriFEC)
Rx FEC = TFEC
Tx FEC = NONE
10G WT
10G WT
Rx FEC = TFEC
Tx FEC = NONE
Terminal
Site
10G WT
(TriFEC)
10G WT
(TriFEC)
SONET
or SDH
Equipment
Rx FEC = NONE
Tx FEC = TFEC
Regenerator
Site
Terminal
Site
Note 1: TFEC refers to the NE UI command for enabling TriFEC.

Note 2: The client-facing equipment's TFEC setting must be turned
off for correct interoperability with other vendors.
Figure 3-4 shows that the carriers subtending SONET or SDH equipment
does not transmit FEC to the terminal site. Therefore, Rx FEC at the on-ramp
circuit pack is provisioned to NONE (no error correction). Similarly, Tx FEC
at the off-ramp circuit pack is provisioned to NONE (no error correction).
Figure 3-4 also shows that error correction provisioning is not possible from
the carriers subtending SONET or SDH equipment.
If error correction is not required on the optical link, you can provision the
on-ramp Tx FEC mode and the off-ramp Rx FEC mode to NONE,
respectively. Alternatively, you can install the 10G WT circuit packs (without
TriFEC functionality) at the terminal sites.
If error correction is required on the optical link, you must set on-ramp
Tx FEC and off-ramp Rx FEC to TFEC or FEC on the 10G WT (TriFEC)
circuit packs. Also, you must set on-ramp Rx FEC and off-ramp Tx FEC to
NONE on the 10G WT (TriFEC) circuit packs.
Some regenerator sites are deployed with thin 3R functionality (without
TriFEC functionality). Therefore, when you use circuit packs in Wavelength
Translator mode, overhead bytes are passed through transparently.
Determining whether the line/MS is severely degraded (for WT
applications with TriFEC)
Determining the BER of the corrected payload
Use Table 3-8 to determine the bit-error ratio (BER) of the corrected payload
from the line/MS FEC counts (15 minute and 1 day). Use the Display facility
PM Counts command in the Facility Performance Menu to view the line/MS
FEC counts. For details on displaying facility PM counts, refer to Performance
Monitoring Procedures, 323-1801-520.
Table 3-8
Determining the BER of the corrected payload from the line/MS FEC counts
BER of the corrected payload
Line/MS FEC
(15 minute)
Line/MS FEC
(1 day)
3.00 x 10-38
831
1.00 x 10-35
43
4156
2.00 x 10-34
87
8313
2.00 x 10-31
433
41 565
3.00 x 10-30
866
83 130
1.00 x 10-27
4330
415 649
2.00 x 10-26
8659
831 298
1.00 x 10-23
43 297
4 156 490
2.00 x 10-22
86 594
8 312 979
1.00 x 10-19
432 968
41 564 897

Line/MS FEC
(15 minute)
Line/MS FEC
(1 day)
2.00 x 10-18
865 935
83 129 795
1.00 x 10-15
4 329 677
415 648 972
6.00 x 10-15
6 927 483
665 038 351
Note 1: If the BER of the corrected payload exceeds 1.00 x 10-14, the
severely errored seconds (SES) count appears. Line/MS CV (for SONET
PM mode), line/MS BBE or EB (for SDH PM mode), and line/MS FEC
counts are inhibited. Unavailable seconds (UAS) will inhibit the SES
counts after ten consecutive SES. Under these circumstances, the BER of
the corrected payload approaches the signal degrade threshold.
Note 2: The TriFEC-capable WT circuit packs propagate approximately
two percent of the incoming line/MS CV (for SONET PM mode), line/MS
BBE or EB (for SDH PM mode) counts to the subtending client equipment
(errors before TriFEC is applied). These errors are propagated through the
SONET/SDH overhead because TriFEC is only applied to the payload.
Advance warning of a severely degraded line/MS
To receive warning of a severely degraded line/MS, use the PM 15min

line/section threshold / PM 15 minute MS/RS threshold alarm and the PM 1
minute line/section threshold / PM 1 minute MS/RS threshold alarm. For
more information, refer to System Commissioning and Testing Procedures,
323-1801-222.
WAN PHY support in Optical Long Haul 1600

Note: Optical Long Haul 1600 supports wide area network (WAN)
physical interface (PHY) only. Optical Long Haul 1600 does not support
local area network (LAN) PHY.
The most widely used networking technologies in wide area networks (WAN)
are SONET and SDH. Because of the growth of Ethernet in metropolitan area
networks (MAN), an increasing need exists for interconnecting Ethernet
LANs and MANs to the SONET networks. With the introduction of 10 Gigabit
Ethernet (GE), the common line rates between OC-192 SONET and 10 GE
resulted in the opportunity to simplify the interface. This section describes
how 10 GE nodes can easily interconnect with OC-192 SONET networks,
without abandoning the Ethernet cost model.
Description of LAN PHY and WAN PHY

The Institute of Electrical and Electronics Engineers (IEEE) P802.3ae
standard specifies two 10 GE PHY types: the LAN PHY and the WAN PHY.
The LAN PHY encodes the 10.0 Gbit/s data stream from the medium access
control protocol (MAC) to a 10.3125 Gbit/s signal using the 64B/66B physical
coding sublayer (PCS).
The WAN PHY uses the same PCS operating in rate adaptation mode to ensure
that the output data stream matches the payload-carrying capacity of a SONET
OC-192 signal (or equivalently an SDH STM-64 signal). The WAN PHY also
incorporates the WAN interface sublayer (WIS) to provide a simplified
SONET framer function as well as the complement of SONET/SDH
compatible management information bases (MIB). The output of the WIS is an
OC-192 frame compatible signal.
The WIS sublayer is the only difference between the LAN PHY and the WAN
PHY. Both physical interfaces share the same PCS, serial physical medium
attachment (PMA), and physical medium dependent (PMD) sublayers. As a
result, the cost benefit applies to both PHY types.
Table 3-9 provides a comparison of LAN PHY and WAN PHY.
Table 3-9
Comparison of LAN PHY with WAN PHY
LAN PHY (see Note 1)
WAN PHY (see Note 1 and Note 2)
10 Gbit/s data rate
Compatible with SONET OC-192/STM-64 payload

rate
64B/66B line encoding
64B/66B line encoding and simplified inexpensive

SONET/SDH framer (see Note 3)
Asynchronous Ethernet interface
Asynchronous Ethernet interface
LAN, MAN, WAN Ethernet pt-pt applications;

incompatible with SONET TDM/DWDM OC-192
optical networks
LAN, MAN, WAN Ethernet pt-pt applications and

simple, low-cost access to SONET TDM/DWDM
OC-192 optical networks
Note 1: Both LAN and WAN PHY support 802.3 Ethernet frame format, MAC, and layer 2 functionality.
Note 2: Optical Long Haul 1600 supports WAN PHY only.
Note 3: Only a small subset of SONET overhead bytes are specified. The 802.3ae standard does not
include conformance to SONET/SDH jitter, stratum clocking, and support of complex features such as
protection switching.
10 GE WAN PHY Wavelength translator interworking

A 10 GE WAN PHY signal can be connected directly to a Wavelength
Translator. Because the Wavelength Translator is based on a regenerator,
section overhead is added. The section overhead is used in the SONET
backbone for management (for example, data communications channel [DCC]
and orderwire).
At the edge of the WAN, the Wavelength Translator (or transponder) is used.
The Wavelength Translator converts the relatively short reach (that is, less than
40 km) metro signals from loose wavelength tolerance 1310 nm optics to
longer reach, tight wavelength tolerance 1550 nm optics on the ITU-T grid.
Since the incoming or on-ramp signals are in SONET format, the chipset from
a SONET regenerator can be used. The key difference between a SONET
regenerator and a Wavelength Translator is that the regenerator has ITU-T grid
optics on both sides.
A seamless end-to-end Ethernet connection can be established without
additional equipment for performing data rate or protocol conversion. 10 GE
provides the potential for an Ethernet solution aligned with the
9.953 280 Gbit/s rate of the OC-192 backbone. For the first time, no additional
speed-matching equipment is required to link with the WAN. A seamless,
end-to-end Ethernet network can be built at a lower network cost.
Wavelength Translator application in a network

Some regenerator sites are deployed with thin 3R functionality (without
TriFEC functionality). Therefore, when you use circuit packs in Wavelength
Translator mode, overhead bytes are passed through transparently.
Example of a Wavelength Translator application in a network
Figure 3-5 shows an example of the Wavelength Translator application in an

optical network.
Figure 3-5
Example of a Wavelength Translator application in a network
OTP2681p
Repeater
Wavelength
Translator
application
10Gbit/s
Vendor
equipment
On-ramp
WT
1600G or
MOR Plus amplifier
10Gbit/s
Off-ramp
WT
MUX/
DEMUX
Note: The client-facing equipment's forward error correction setting

must be turned off for correct interoperability with other vendors.
Example of a Wavelength Translator application in a Repeater bay
Figure 3-6 on page 3-20 shows an example of a full-fill Repeater network

element supporting the Wavelength Translator application.

Figure 3-6
Repeater network element (Wavelength Translator application)
OTP3007p
Breaker interface panel (BIP)

Ethernet Wayside
Ethernet Wayside
PT
OW
Filler
Filler
128M MI
MX
MX
POPI
PT
POPC
32M SC
POPS
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
Breaker filter
Breaker filter
Attention
engineering rules.
Control shelf
(Shelf ID: 1)
Air Intake
10
WT (2.5 or 10 Gbit/s)
G9
G8
G5 G6 G7
G4
G3
G2
10
10
G10 G11 G12 G13 G14 G15 G16 G17 G18 G19


or slot 17 (G6) of the control shelf for
point-to-point Ethernet communication.
Be sure to equip the network element
with MOR Plus amplifier circuit packs.
Note 2: You can also equip the first four

slots with 2.5 Gbit/s and 10 Gbit/s WT
circuit packs (see Note 1).
Note 1: Slots 5 to 10 of the main shelf

can contain the following WT circuit
packs: 2.5G WT, Dual 2.5G WT,
10G WT SR (TriFEC), 10G WT (TriFEC),
10G WT, or OC-192/STM-64 XR/WT.
G0 G1
MOR Plus (RedPre/

BluePost) MSA Pre
MOR Plus (RedPost/
BluePre) MSA Post
MOR Plus (RedPost/
BluePre) MSA Post
MOR Plus (RedPre/
BluePost) MSA Pre
Air Exhaust
1
G20 G21 G22 G23 G24 G25 G26 G27 G28 G29
Main
shelf
(Shelf ID: 2)
Environmental
control panel
(ECP) houses
three fans
Extension
shelf 1
(Shelf ID: 3)
Environmental
control panel
(ECP) houses
three fans
Extension
shelf 2
(Shelf ID: 4)
4-1
4-
Chapter overview
This chapter provides a detailed description of the Wavelength Combiner
Section
Page
Description of the Wavelength Combiner application
4-2
Supported circuit packs for the Wavelength Combiner

application
4-7
Overhead processing
4-11
Wavelength Combiner application with TriFEC
4-18
Wavelength Combiner operation with Dual Gigabit Ethernet
4-23
Synchronization
4-29
Optical Long Haul 1600 Wavelength Combiner interoperability

with Transport Node OC-48 BLSR using k-byte compliancy
4-32
Wavelength Combiner application in a network
4-33
Repeater network element (Wavelength Combiner application)
4-34
4-2 Wavelength Combiner application
ATTENTION
The Wavelength Combiner circuit pack groups at both terminals must be
originally equipped with the same type of 10 Gbit/s transmitters (both
TriFEC-capable or both non-TriFEC). Failure in following this rule will
probably cause a Protection scheme mismatch or Channel ID mismatch
alarm to be raised on the subtending OC-48 or TN-16X equipment and cause
subsequent protection path failures.
You can replace a non-TriFEC OC-192/STM-64 T/R circuit pack with a
TriFEC-capable OC-192/STM-64 (TriFEC) T/R circuit pack. However, if
you perform this replacement, the enhanced transparency of the
TriFEC-capable circuit pack will not be available: you will also only be able
to provision single FEC or no FEC only on the replacement OC-192/STM-64
(TriFEC) T/R circuit pack.
If you require TriFEC functionality or enhanced transparency of the optical
signal, then you must first delete the non-TriFEC OC-192/STM-64 T/R
circuit pack, and then autoprovision the slot with a TriFEC-capable
OC-192/STM-64 (TriFEC) circuit pack. This process is known as a circuit
pack upgrade.
Description of the Wavelength Combiner application

The Wavelength Combiner application, introduced in Release 2, aggregates up
to four 2.5 Gbit/s services into one 10 Gbit/s line signal while maintaining
service transparency. The 2.5 Gbit/s services can originate from any
combination to OC-48/STM-16 DWDM T/R, OC-48/STM-16 T/R SR, and
Dual Gigabit Ethernet circuit packs.
A Repeater network element can house up to five Wavelength Combiner
circuit pack groups, for a total of 50 Gbit/s of aggregated services. Since the
optical line signal is managed by its overhead, the tributary services are
transparent to the 10 Gbit/s SONET/SDH line/MS. This arrangement allows
the use of forward error correction (FEC) and communication channels on the
line side. The Wavelength Combiner application supports ITU-T standard
wavelengths.
Compared to a transponder-based solution, the Wavelength Combiner offers
service granularity on the access space, while maximizing wavelength traffic
capacity on the transport medium. The Wavelength Translator acts as a
transparent interface. The Wavelength Combiner acts as an open optical
interface and provides at least four times the effective channel count on the
fiber plant.
Figure 4-1 shows the Wavelength Combiner circuit packs.
Wavelength Combiner application 4-3

Figure 4-1
Wavelength Combiner
OTP2783t
Fixed backplane
connections
Trib 2.5 Gbit/s T/R
or Dual GE
From/to
subtending
system
Trib 2.5 Gbit/s T/R

or Dual GE
Trib 2.5 Gbit/s T/R
or Dual GE
Line
10 Gbit/s
T/R
10 Gbit/s
line
Trib 2.5 Gbit/s T/R

or Dual GE
TDA/TDB
ESI A/B
Similar to the transparent Mux (TMux) application on the 10 Gbit/s S/DMS

TransportNode platform, the Wavelength Combiner distributes its tributary
service signals onto the 10 Gbit/s line/MS signal through a fixed mapping
scheme. This mapping is executed through the Optical Long Haul 1600
platform backplane bus signals, therefore eliminating the need for switch
module circuit packs or bandwidth management core.
Each tributary interface circuit pack is assigned to a reserved block in the

OC-192/STM-64 frame. Timeslot alignment on the Wavelength Combiner is
as listed below.
tributary circuit pack A is mapped to STS timeslots 97 to 144
tributary circuit pack B is mapped to STS timeslots 49 to 96
tributary circuit pack C is mapped to STS timeslots 1 to 48 (see Note)
Note: For Wavelength Combiners equipped with a non-TriFEC
OC-192/STM-64 T/R circuit pack, the STS timeslot 1 overhead of the
C channel tributary is mapped to the STS timeslot 1 of the 10 Gbit/s
Combiner line/MS.
For Wavelength Combiners equipped with a TriFEC-capable

OC-192/STM-64 T/R circuit pack, the STS timeslot 1 overhead of the
C channel tributary is mapped to the STS timeslot 13 of the 10 Gbit/s
Combiner line/MS. All C channel transparency issues that exist on the
non-TriFEC T/R circuit pack do not exist on the TriFEC-capable T/R
circuit pack.
tributary circuit pack D is mapped to STS timeslots 145 to 192
Figure 4-2 shows the tributary mapping of the Wavelength Combiner for the
main shelf of the Repeater bay. The same mapping scheme is used for all
Wavelength Combiner circuit pack groups in the Repeater bay. The
Wavelength Combiner application supports concatenated payloads on all
tributaries.

Figure 4-2
Wavelength Combiner tributary mapping
TD
G4B
TD
STS
timeslots
#97 to 144
STS
timeslots
#49 to 96
7
G6
8
G7
9
G8
10
G9

or Dual GE
5
6
G4A G5

or Dual GE
4
G3
OC-192/STM-64 T/R
3
G2

or Dual GE
Main shelf
1
2
G0 G1

or Dual GE
OTP0162
STS
timeslots
#1 to 48
STS
timeslots
#145 to 192
ATTENTION
A Repeater network element equipped with at least one Wavelength
Combiner circuit pack group requires two ESI and two half-height TD circuit
packs. No alarm is raised if the two ESI and two half-height TD circuit packs
are missing when a Repeater network element is equipped with a Wavelength
Combiner.
ATTENTION
You cannot use 10 Gbit/s T/R circuit packs in extension shelf 2 (G22 and
G27) to line time your network element.
The Repeater network element supports up to five Wavelength Combiner
circuit pack groups within one bay. One Wavelength Combiner circuit pack
group can be placed on the main shelf (slots 6 to 10). Each of the extension
shelves can contain up to two Wavelength Combiners each (slots 1 to 5 and
slots 6 to 10 on each extension shelf). When equipping a Repeater network
element with a Wavelength Combiner circuit pack group, you must equip two
half-height timing distribution (TD) and two ESI circuit packs in the Repeater
network element.
Although the Repeater network element does not require two ESI and two
half-height TD circuit packs when only Wavelength Translator, ODPR, and
Dense regenerator applications are provisioned, careful planning is required if
you install Wavelength Combiners in a Repeater network element during
commissioning or in the future. You must reserve slot 5 (G4) on the main shelf
for two half-height TD circuit packs to avoid disrupting service in the future.
You can mix OC-48/STM-16 DWDM T/R, OC-48/STM-16 T/R SR, and Dual
Gigabit Ethernet circuit packs in the same Wavelength Combiner circuit pack
group.
ATTENTION
originally equipped with the same type of 10 Gbit/s transmitters (both
TriFEC-capable or both non-TriFEC). Failure in following this rule will
probably cause a Protection scheme mismatch or Channel ID mismatch
alarm to be raised on the subtending OC-48 or TN-16x equipment and cause
subsequent protection path failures. For more information, refer to the
attention box on page 4-2.
Each Wavelength Combiner circuit pack group contains a group of five circuit
packs, described as follows:
one OC-192/STM-64 T/R circuit pack (NTCA06xx) and up to four of the
same or a mix of the following circuit packs
OC-48/STM-16 DWDM T/R circuit pack (NTCA30xK)
OC-48/STM-16 T/R SR circuit pack (NTCA30CK)
OC-48/STM-16 T/R (1310 nm) circuit pack (NTCA30AL)
Dual Gigabit Ethernet circuit pack (NTCA90xA)
one OC-192/STM-64 T/R (TriFEC) circuit pack (NTCF06xx) and up to
four of the same or a mix of the following circuit packs
The OC-192/STM-64 T/R (TriFEC) circuit pack provides you with the ability
to perform forward error correction for optimizing link budget performance.
The OC-192/STM-64 T/R (TriFEC) circuit pack provides enhanced
transparency of the C Channel tributary over the non-TriFEC
OC-192/STM-64 T/R circuit pack.
Supported circuit packs for the Wavelength Combiner application

The Wavelength Combiner application allows provisioning of the circuit packs
listed in Table 4-1.
Table 4-1
Supported Wavelength Combiner circuit packs
Circuit packs (see Note 1 and Note 2)
PEC
Notes
OC-48/STM-16 T/R SR
NTCA30CK 2
NTCA30xK 4
OC-48/STM-16 T/R (1310 nm)
NTCA30AL 2
Dual Gigabit Ethernet (GE)
NTCA90xA 9
See Note 3
OC-192/STM-64 T/R
NTCA06xx
NTCF06xx
See Note 4
NTCx44xx
NTCA21AA 2
1-1 on page 1-3.
Note 3: For information on Dual Gigabit Ethernet circuit packs, refer to Wavelength Combiner
operation with Dual Gigabit Ethernet on page 4-23 and Chapter 10, Circuit pack technical
specifications.
Note 4: For information on TriFEC, refer to Wavelength Combiner application with TriFEC on page
4-18 and Appendix B: TriFEC applications on page 12-1.

The OC-48/STM-16 T/R SR tributary circuit pack is a 2.5 Gbit/s tributary to
the Wavelength Combiner. It converts optical signals from OC-48/STM-16
subtending equipment into electrical signals, then transmits them to the
backplane. This circuit pack is also equipped with short-reach optics on the
transmit port for transmission at 1310 nm to subtending equipment. This
circuit pack can occupy the following slots:
slots 6, 7, 9, and 10 (G5, G6, G8, and G9, respectively) of the main shelf
slots 1, 2, 4 to 7, 9, and 10 of extension shelf 1 (G10, G11, G13 to G16,
G18, and G19, respectively)

The OC-48/STM-16 DWDM T/R tributary circuit pack functions as a
2.5 Gbit/s tributary to the Wavelength Combiner. This circuit pack receives its
signal from the OC-48/STM-16 subtending equipment, converts the signal
into an electrical signal, and transmits the signal to the backplane. The circuit
pack is equipped with DWDM optics on the transmit port, for transmission
after receipt from the 10 Gbit/s optical link.
This circuit pack can occupy the following slots:
slots 1, 2, 4 to 7, 9, and 10 (G10, G11, G13 to G16, G18, and G19,
respectively) of extension shelf 1
slots 1, 2, 4 to 7, 9, and 10 (G20, G21, G23 to G26, G28, and G29,
respectively) of extension shelf 2
The OC-48/STM-16 T/R (1310 nm) tributary circuit pack functions as a
2.5 Gbit/s tributary to the Wavelength Combiner. This circuit pack receives its
signal from the OC-48/STM-16 subtending equipment, converts the signal
into an electrical signal, and transmits the signal to the backplane. The circuit
pack is equipped with 1310 nm optics on the transmit port for transmission to
subtending equipment.
The Dual Gigabit Ethernet (GE) long reach (LX), short reach (SX), and
extended reach circuit packs (NTCA90CA, NTCA90EA, and NTCA90GA)
function as tributary circuit packs to the Wavelength Combiner. The Dual GE
circuit pack extends the services available on the Repeater network element
(NE) allowing the carrier to transport subtending Gigabit Ethernet traffic on
the SONET/SDH 10 Gbit/s line.
The Dual GE circuit pack is a full-height circuit pack that maps two
independent GE data traffic streams into two separate SONET/SDH payloads
carried on the Optical Long Haul 1600 network, providing the capability for
GE traffic to interconnect in a point-to-point fashion. Dual GE data packets are
populated in the payload of SONET/SDH STS-24c/VC-4-8c frames. Up to
eight GE signals can be combined in one OC-192/STM-64 signal in a fully
equipped Wavelength Combiner CPG.

This circuit pack provides the carrier with the
ability to carry low-cost data services on the Optical Long Haul 1600
optical network
ability to lease Gigabit Ethernet services
ability to provide Ethernet transport applications: router to router
interconnection across a wide area network (WAN)
In addition to the preceding network applications, the Dual GE provides a
direct Ethernet interface that provides significant savings compared to packet
over SONET/SDH (PoS) router ports.
For more information on Dual Gigabit Ethernet circuit packs, refer to Chapter
10, Circuit pack technical specifications.
OC-192/STM-64 T/R circuit pack (NTCA06xx)
The OC-192/STM-64 T/R circuit pack integrates the functionality of a
DWDM receiver, demultiplexer, and transmitter in one circuit pack. This
circuit pack provides transmit and receive facility terminations. This circuit
pack is used to convert backplane electrical signals into optical output signals.
The OC-192/STM-64 T/R line circuit pack is a key element for Wavelength
Combiner applications.
slot 8 (G7) of the main shelf
slots 3 and 8 (G12, G17, G22, and G27) of extension shelf 1 and extension
shelf 2
OC-192/STM-64 T/R (TriFEC) circuit pack (NTCF06xx)
The OC-192/STM-64 T/R (TriFEC) circuit pack integrates the functionality of
a DWDM receiver, demultiplexer, and transmitter in one circuit pack. Because
this circuit pack supports TriFEC, this circuit pack provides improved optical
link performance over non-TriFEC OC-192/STM-64 T/R circuit packs. This
circuit pack also provides enhanced transparency for tributary C (refer to
Transparency of Wavelength Combiner applications with TriFEC on page
4-18 for details).

slots 8 (G7) of the main shelf
slots 3 and 8 (G12, G17, G22, and G27) of extension shelf 1 and extension
shelf 2
The OC-192/STM-64 T/R (TriFEC) circuit pack is available for Red and Blue
For more information on TriFEC circuit packs, refer to Wavelength Combiner
application with TriFEC on page 4-18 and Appendix B: TriFEC
External synchronization interface (ESI) circuit pack
(NTCA44AA and NTCE44BA, NTCE44CA)
The external synchronization interface (ESI) circuit pack provides the
interface between an external timing source and the shelf timing equipment.
The ESI circuit pack selects the external reference signal and provides an
accurate timing source to the shelf.
The ESI circuit pack receives timing input from an external stratum clock with
a building-integrated timing supply (BITS) or from a framing embedded in the
incoming OC-192/STM-64 optical signal.
If an interruption occurs that has an effect on all the reference signals, the ESI
circuit pack enters an operation mode known as holdover. The ESI circuit
pack continues to provide an accurate timing source based on the last known
correct reference. The ESI enters holdover mode as a result of a manual request
or as the result of a loss of the reference signal. In holdover mode, the ESI
maintains its synchronization for 24 hours based on the last valid Stratum 3 or
better reference signal. After the 24-hour period, the reference returns to
Stratum 3 quality (if the reference quality was better than Stratum 3). If the
reference was Stratum 3, the quality remains Stratum 3.
The ESI circuit pack can also provide timing distribution to other network
elements in the network. The output from the network element uniSATT panel
can deliver a synchronization signal. ESI G1 generates a DS1 or 2 MHz timing
reference called G1OUT. ESI G2 generates another DS1 or 2 MHz timing
reference called G2OUT. The ESI circuit pack generates the timing
distribution signals based on the timing generation signals.
The ESI equipment protection is 1+1 revertive. Each ESI output facility has
two redundant references to provide protection in case of a line reference
failure on ESI G1 or ESI G2.
The following ESI facilities are provisioned by default for ESI G1 and ESI G2:
one timing generation group, including two BITS input facilities (BITSA
and BITSB)
two timing distribution output facilities (G1OUT and G2OUT)
There is one timing distribution reference protection group for each ESI circuit
pack. Each timing distribution protection group has three reference sources:
OC-192/STM-64 G7, OC-192/STM-64 G12, and OC-192/STM-64 G17.
If a Repeater network element includes the Combiner application, then the ESI
circuit packs are mandatory in slots 7 and 8 of the control shelf.
Three types of ESI circuit packs are available:
NTCE44BA provides external inputs and outputs at 2.048 MHz (2 MHz)
for SDH systems. The NTCE44BA cannot operate with a 60 V power
supply. You cannot spare a defective NTCE44CA with an NTCE44BA
circuit pack. This circuit pack does not provide SSM to external outputs.
For more information on SSM, refer to Synchronization status messaging
(SSM) on page 7-39.
NTCE44CA provides external inputs and output at 2.048 MHz (2 MHz)
for SDH systems. This new ESI circuit pack can operate at 35 V to 75 V
and is dedicated for deployment in captive offices that use a 60 V power
supply. An NTCE44BA can be spared with an NTCE44CA circuit pack.
The NTCE44CA can also operate with 48 V power supply. This circuit
pack does not provide SSM to external outputs. For more information on
SSM, refer to Synchronization status messaging (SSM) on page 7-39.
NTCA44AA provides external inputs and outputs at the DS1 line rate
(1.5 Mbit/s) for SONET systems.
Timing distribution (TD) circuit pack (NTCA21AA)
The half-height timing distribution (TD) circuit pack provides a 1+1
non-revertive timing protection scheme. The TD circuit pack provides
differential clock references to each OC-192/STM-64 T/R line circuit pack.
If a Repeater network element includes a Wavelength Combiner circuit pack
group, the half-height TD circuit pack must be equipped in slots G4A and G4B
of the Repeater network element.
Overhead processing
Table 4-2 shows a summary of the service transparency features for the
OC-48/STM-16 tributary services of a Wavelength Combiner.
Note: For descriptions of overhead byte functions and service
transparency values, refer to Appendix A: Overhead processing on page
11-1.

Table 4-2
Wavelength Combiner OC-48/STM-16 service transparency
Transport overhead bytes
Tributary service transparency
A1, A2
Regenerated
B1, B2
Recalculated and propagated to tail-end combiner tributaries
Section/RS DCC (D1-D3)
Transparent
Line/MS DCC (D4-D12)
Transparent (see Note 1)
K1, K2
Transparent
E1, E2
C1 (J0)
Terminated
Synch Status S1 (Z1)
Terminated
Payload pointers (H1-H3)
Regenerated
User byte F1
Z2/M1 (Line FEBE)
Transparent
Note 1: If the OC-192/STM-64 T/R (NTCA06xx) is deployed in the circuit pack group, line/MS DCC
(D4-D12) for tributary C is not available.
Note 2: If the OC-192/STM-64 T/R (NTCA06xx) is deployed in the circuit pack group, Wavelength
Translators (WT) are required at regenerator sites if E1 and F1 transparency is required for tributary C.
B1 and B2 bytes
The overhead bytes of each tributary signal are mapped to the first STS/STM
timeslot of the reserved portion of the frame. Framing bytes A1 and A2 are
regenerated on each tributary for correct framing alignment.
The Wavelength Combiner recalculates and propagates tributary section parity
(B1) and line parity (B2) bytes to ensure tributary B1/B2 service transparency.
Tail-end tributary B1/B2 counts reflect the head-end tributary counts, although
PM count alarms are raised at the head-end Wavelength Combiner tributary for
management of faults. The similar propagated counts raise the correct
alarming scheme on the subtending equipment.
The B1 counts on the 10 Gbit/s line are used to raise PM count alarms on the
10 Gbit/s regenerator or tail-end Combiner equipment. Since the 10 Gbit/s
section/RS is independent from the tributary service, no B1 counts are visible
to the tributary service.
The B2 counts on the Wavelength Combiner 10 Gbit/s line raise the B2 line
counts on all tail-end tributary services and raise the PM count alarms on the
10 Gbit/s regenerator or tail-end Combiner equipment.
Enhanced DCC transparency of the Wavelength Combiner

Section/RS DCC (bytes D1 to D3) of the tributaries are transparent to the
Wavelength Combiner. The Wavelength Combiner uses its 10 Gbit/s
section/RS DCC for network communication.
When the Combiner circuit pack group contains TriFEC-capable
OC-192/STM-64 T/R circuit packs, the Wavelength Combiner supports full
line/MS data communication channel (DCC) (bytes D4 to D12) for channels
A, B, C, and D.
Table 4-3 lists the channel transparency of deployed 10 Gbit/s line circuit
packs.
Table 4-3
Tributary line/MS DCC channel transparency available for 10 Gbit/s line circuit packs
Channel A
line/MS DCC
transparency
Channel B
line/MS DCC
transparency
Channel C
line/MS DCC
transparency
Channel D
line/MS DCC
transparency
OC-192/STM-64 T/R
(NTCA06xx)
Yes
Yes
No
Yes

(NTCF06xx)
Yes
Yes
Yes
Yes
TriFEC-capable OC-192/STM-64 T/R circuit packs provide enhanced

transparency of the C channel tributary over the OC-192/STM-64 T/R circuit
pack (without TriFEC functionality). The C channel tributaries slots G8, G13,
G18, G23, and G28 are equipped with OC-48/STM-16 T/R circuit packs.
For more information, refer to Transparency of Wavelength Combiner
applications with TriFEC on page 4-18.
Note: Line/MS DCC for the C channel tributary is not available if
OC-192/STM-64 T/R circuit packs (NTCA06xx) are deployed along the
link.
The DCC overhead of the 10 Gbit/s T/R is separate from that of its tributary
services. The 10 Gbit/s T/R offers full SONET/SDH network management on
the 10 Gbit/s optical line/MS, independent of the service network management
schemes.
K1 and K2 transparency
Tributary SONET/SDH APS bytes K1 and K2 are also transparent. To trigger
protection switching on the subtending services, the Wavelength Combiner
forces alarm indication signal (AIS) on K1 and K2 bytes when a signal degrade
(SD) condition occurs on the 10 Gbit/s line/MS. A fault condition affecting the
10 Gbit/s line/MS is distributed to all tributaries. A fault condition affecting

one head-end tributary only raises protection mechanisms at the tail-end
equipment, without affecting the other tributaries.
Orderwire and user bytes transparency (E1, E2, F1, and F2)
E2 and F2 are transparent for all tributaries within the Wavelength Combiner
circuit pack group.
If the link deploys the OC-192/STM-64 T/R (NTCA06xx) circuit pack, the
orderwire bytes (E1) and user byte (F1) are transparent for tributaries A, B and
D. However, end-to-end transparency of the tributary C orderwire byte (E1)
and user byte (F1) is only achieved if regenerator sites include Wavelength
Translators. Orderwire and user byte (E1 and F1) transparency are not
achieved if OC-192/STM-64 XR circuit packs are deployed at regenerator
sites because, in this case, the E1 and F1 bytes are terminated.
If the Wavelength Combiner deploys the TriFEC-capable
OC-192/STM-64 T/R circuit packs within the circuit pack group, orderwire
bytes (E1) and user byte (F1) are transparent on the Wavelength Combiner for
all tributaries (A, B, C, and D).
ATTENTION
When the link deploys the OC-192/STM-64 T/R circuit pack (NTCA06xx)
and end-to-end orderwire byte E1 and user byte F1 passthrough are required
on tributary C, you must deploy the 10 Gbit/s Wavelength Translator circuit
pack at the regenerator site. You cannot use an OC-192/STM-64 XR circuit
pack at the regenerator site (full SONET/SDH regenerator) because this
circuit pack terminates the E1 and F1 bytes in STS timeslot 1.
Section trace byte J0 (C1 #1) is terminated for the Wavelength Combiner
tributaries. Fiber management and trace-back is executed through the
distinctive Combiner line and tributary interfaces at both ends of the Optical
Long Haul 1600 network.
The synchronization status bytes S1 (Z1) are terminated. The payload pointers
H1, H2, and H3 are regenerated. All other overhead bytes (for example, user
bytes and line far-end block errors [FEBE]) are transparent to the Wavelength
Combiner.
Fault sectionalization
Fault sectionalization refers to the process of detecting errors and their
location.
In Figure 4-3, a B1 error (section parity byte for error counts and performance
monitoring counts) occurs between the subtending OC-48/STM-16 equipment
and the first Wavelength Combiner application that acts as a terminal site. The
B1 error is seen by the Wavelength Combiner application on one of its

OC-48/STM-16 tributaries and is propagated down the optical line until the B1
error reaches the far-end subtending equipment. The far-end equipment then
detects the B1 error on the far-end received tributary and switches the far-end
protection circuit as a result of signal degrade (or signal fail) levels.
PM threshold crossing alarms are raised at the head-end Wavelength Combiner
tributary facility to facilitate the carrier section management.
Figure 4-3
Sectionalization of faults for a Wavelength Combiner application (example of a B1 error)
OTP2791p
Subtending
TBM
B2
B1
B2
B1=
Recalculated
OC-48/
STM-16
Regenerator
B1
B2
Subtending
TBM
OC-48/
STM-16
Regenerator
0
0
B1
B2
B1
error
0
0
B1
B2
1
0
Propagate B1 and B2
B1
B2
1
0
1
0
Repeater
Network
Element
Repeater
Network
Element
Repeater
Network
Element
Wavelength
Combiner
10 Gbit/s
Dense
regenerator
Wavelength
Combiner
Figure 4-4 shows the same fault management process shown in Figure 4-3. In
this scenario, a B2 error (line parity byte for error counts and PM counts)
occurs between the subtending OC-48/STM-16 equipment and the first
Wavelength Combiner that acts as a terminal site. The error is correctly seen
by the far-end receiving equipment and tributary protection switching takes
place at the determined level.
The head-end Wavelength Combiner tributary facility raises the appropriate
line alarms on the affected 2.5 Gbit/s subtending service.

Figure 4-4
Sectionalization of faults for a Wavelength Combiner application (example of a B2 error)
OTP2790p
Subtending
TBM
B2
B1
B2
B1=
Recalculated
OC-48/
STM-16
Regenerator
B1
B2
Subtending
TBM
OC-48/
STM-16
Regenerator
0
0
B1
B2
B2
error
0
1
B1
B2
1
1
Propagate B1 and B2
B1
B2
1
1
1
1
Repeater
Network
Element
Repeater
Network
Element
Repeater
Network
Element
Wavelength
Combiner
10 Gbit/s
Dense
regenerator
Wavelength
Combiner
Figure 4-5 shows that a B2 fault on the 10 Gbit/s line affects all four 2.5 Gbit/s
channels on the Wavelength Combiner and triggers the generation of a
service-affecting alarm to notify the subtending equipment. However, in the
event of a B1 fault on the Optical Long Haul 1600 10 Gbit/s line, the B1 error
is only raised within the Optical Long Haul 1600 span of control (SOC) to
isolate the troubled area. According to the B1 recalculated scheme, each
intermediate Optical Long Haul 1600 network element (in this scenario, the
Optical Long Haul 1600 intermediate network element is a Repeater) resets the
B1 byte to 00 to find the source of the fault much faster and to avoid long
backtracking calculations.
PM threshold alarms are raised on the affected 10 Gbit/s section/RS, without
propagation to the 2.5 Gbit/s subtending services.

Figure 4-5
Signal degrade handling on the Wavelength Combiner application
OTP2792p
Subtending
TBM
B2
B2
OC-48/
STM-16
Regenerator
B1
B2
Subtending
TBM
OC-48/
STM-16
Regenerator
0
0
B1
B2
Signal B1
Degradation B2
0
0
Propagate B1 and B2
B1
B2
0
1
0
1
Repeater
Network
Element
Repeater
Network
Element
Repeater
Network
Element
Wavelength
Combiner
10 Gbit/s
Dense
regenerator
Wavelength
Combiner
10 Gbit/s line
B1
B2
0
0
B1
B2
1
1
B1
B2
B1
Recalculated
0
1
For more information on performance monitoring for the Wavelength

Combiner, refer to Operations, administration, maintenance, and
provisioning (OAM&P) on page 7-1.

Optical Long Haul 1600 Release 5 introduced triple forward error correction
(TriFEC) for the Wavelength Combiner application. This section provides
information on TriFEC functionality for the Wavelength Combiner
application.
Transparency of Wavelength Combiner applications with TriFEC
The TriFEC-capable OC-192/STM-64 T/R circuit packs provide enhanced
transparency of the C channel tributary service over the OC-192/STM-64 T/R
circuit pack (without TriFEC functionality). This enhancement is achieved by
transparently passing the line/MS data communications channel (DCC) bytes
D4 to D12. The C channel tributaries are equipped with OC-48/STM-16 T/R
circuit packs in G8, G13, G18, G23, and G28 of the Repeater network element.
Before the introduction of the TriFEC-capable OC-192/STM-64 T/R circuit
packs, the line/MS DCC of the C channel tributary service was overwritten by
the line/MS DCC of the OC-192/STM-64 Combiner line.
Moreover, with TriFEC-capable OC-192/STM-64 T/R circuit packs, the local
orderwire byte (E1) and the user byte (F1) of the C channel tributary service
are transparent even when OC-192/STM-64 XR circuit packs are equipped at
regenerator sites. Before the introduction of the TriFEC-capable
OC-192/STM-64 circuit packs, the E1 and F1 bytes were not transparent when
OC-192/STM-64 XR circuit packs were equipped at regenerator sites.
Error correction provisioning
When you set the error correction mode (FEC) on the TriFEC-capable
OC-192/STM-64 T/R circuit packs, Tx FEC and Rx FEC are set
simultaneously to the same value.
ATTENTION
Starting with Optical Long Haul 1600 Release 6, you provision the transmit
and receive error correction modes for OC-192/STM-64 T/R circuit packs
concurrently to the same value. You cannot provision Rx FEC and Tx FEC
separately.
ATTENTION
In-service provisioning of the FEC mode is not supported. Provision the FEC
mode during a service interruption (scheduled maintenance) or before the
network is placed in-service.
Table 4-4 lists the supported and default NE UI values for FEC.
Table 4-4
FEC parameter values for the TriFEC-capable OC-192/STM-64 T/R circuit packs
Facility parameter
Supported NE UI values
Default NE UI value
FEC
NONE (no error correction) FEC (single FEC)
(error correction in both FEC (single FEC)

the Tx and Rx
TFEC (TriFEC)
directions)
Note: TFEC refers to the NE UI command for enabling TriFEC. FEC

refers to the NE UI command for enabling single FEC.
When you change the error correction mode on an OC-192/STM-64 T/R
circuit pack, the signal degrade threshold is automatically reprovisioned
according to your FEC setting, as listed in Table 4-5.
Table 4-5
Automatically provisioned signal degrade threshold values
(OC-192/STM-64 T/R circuit packs)
FEC mode
Automatically provisioned signal degrade threshold
TriFEC
1 x 10-5 (maximum value)
FEC or None
1 x 10-8
For more information on TriFEC and signal degrade, see Signal degrade
threshold on page 4-21.
You provision the FEC setting for each FEC-capable circuit pack through the
Facility Menu. You can provision, edit, and query the FEC level for the
required link. You must ensure that the FEC level is the same at both ends of
the optical link. Otherwise, a FEC provisioning mismatch alarm is raised.
When the FEC provisioning mismatch alarm is active, errors on the link are
not corrected by FEC or TriFEC. (The receiver will not decode the single FEC
or TriFEC encoded bytes.) The alarm clears when FEC is provisioned
correctly.
Figure 4-6 shows an example of a network deployment. The OC-192/STM-64
T/R (TriFEC) circuit packs in the Combiner circuit pack groups are
provisioned to transmit and receive TriFEC, respectively. The
OC-192/STM-64 XR circuit packs (without error correction functionality) at
the regenerator sites are transparent to the TriFEC bytes. By provisioning the
FEC mode for both Combiner circuit pack groups to the same value, TriFEC
is enabled on the aggregate optical line/MS and the FEC provisioning
mismatch alarm is not raised.

Figure 4-6
Network deployment showing error correction provisioning at terminal sites (OC-192/STM-64 T/R
(TriFEC) circuit packs)
OTP2856t
OC-48/STM-16
T/R
OC-192/
STM-64
T/R
(TriFEC)
OC-192/
STM-64
XR
OC-192/
STM-64
XR
OC-48/STM-16
T/R
FEC = TFEC
FEC = TFEC
Terminal
Site
OC-192/
STM-64
T/R
(TriFEC)
Regenerator
Site
Terminal
Site

Note 2: Tx FEC and Rx FEC are set concurrently when setting the FEC mode.
Note 3: The FEC setting must be identical at both ends of the optical
link. In this example, the FEC setting at each terminal site is set
to TFEC to enhance the link budget.
Figure 4-6 shows that the carriers subtending 2.5 Gbit/s SONET or SDH
equipment does not transmit forward error correction to the terminal site and
error correction provisioning is not possible from the carriers subtending
SONET or SDH equipment. The OC-48/STM-16 T/R tributary circuit packs
do not have error correction functionality.
If error correction is not required on the optical link, you can provision the
FEC mode to NONE (no error correction) on the OC-192/STM-64 T/R
(TriFEC) circuit packs in the Combiner circuit pack groups. If error correction
is required on the optical link, you must set the error correction mode to FEC
(single FEC) or TFEC (TriFEC) on both TriFEC-capable OC-192/STM-64
T/R circuit packs.
Determining whether the line/MS is severely degraded
(for Wavelength Combiner applications with TriFEC)
FEC counts. For more information on displaying facility PM counts, refer to
Performance Monitoring Procedures, 323-1801-520.

Table 4-6
Line/MS FEC
(15 minute)
Line/MS FEC
(1 day)
3.00 x 10-38
831
1.00 x 10-35
43
4156
2.00 x 10-34
87
8313
2.00 x 10-31
433
41 565
3.00 x 10-30
866
83 130
1.00 x 10-27
4330
415 649
2.00 x 10-26
8659
831 298
1.00 x 10-23
43 297
4 156 490
2.00 x 10-22
86 594
8 312 979
1.00 x 10-19
432 968
41 564 897
2.00 x 10-18
865 935
83 129 795
1.00 x 10-15
4 329 677
415 648 972
6.00 x 10-15
6 927 483
665 038 351
Note: If the BER of the corrected payload exceeds 1.00 x 10-14, the
PM mode), line/MS BBE or EB (for SDH PM mode) counts, and line/MS
FEC counts are inhibited. Unavailable seconds (UAS) will inhibit the SES
counts after 10 consecutive SES. Under these circumstances, the BER of
the corrected payload approaches the signal degrade threshold.
Signal degrade threshold
When the provisioned signal degrade threshold is exceeded in a non-TriFEC

application, the Signal degrade / MS signal degrade alarm is raised. The
Signal degrade / MS signal degrade alarm is triggered based on the
uncorrected (raw) BER of the line/MS CV (B2) errors (for SONET PM mode)
or line/MS BBE or EB errors (for SDH PM mode). However, for TriFEC
applications, the BER of the corrected payload can be much lower than the
uncorrected (raw) BER.
When TriFEC is enabled on the line/MS, line/MS CV (for SONET PM mode)
or line/MS BBE or EB errors (for SDH PM mode) errors are corrected.
However, the counts reported by the Display facility PM Counts command is
not adjusted for the errors corrected by TriFEC. As such, the line/MS CV (for
SONET PM mode) or line/MS BBE or EB (for SDH PM mode) count
corresponds to the uncorrected (raw) errors.
Because the Signal degrade/MS signal degrade alarm is triggered based on
the uncorrected (raw) BER, and not based on the BER of the corrected
payload, misleading error counts may be propagated to subtending equipment.
To avoid the Signal degrade/MS signal degrade alarm from being triggered,
the signal degrade threshold is automatically set to 1.0 x 10-5 (maximum
value) when you provision TriFEC on the TriFEC-capable OC-192/STM-64
T/R circuit packs. When the signal degrade threshold is (automatically) set to
1.0 x 10-5, the Signal degrade / MS signal degrade alarm is not raised
because an LOS is raised at an (uncorrected) BER of 3.2 x 10-6.
Note: For details on the automatically provisioned signal degrade
threshold value, see Table 4-5 on page 4-19.
If you change the signal degrade threshold to a value less than 1.0 x 10-5, a
Signal degrade/MS signal degrade alarm can occur on the 10 Gbit/s
Combiner line. In this case, each 2.5 Gbit/s tributary adopts the greater of the
following line/MS CV (for SONET PM mode) or line/MS BBE or EB (for
SDH PM mode) counts: the count for the 10 Gbit/s Combiner line, or the count
for the individual 2.5 Gbit/s tributary (see Figure 4-7). Because the Signal
degrade/MS signal degrade alarm is raised based on the uncorrected (raw)
BER and not based on the corrected BER, misleading counts can propagate to
subtending equipment.
Note: The 2.5 Gbit/s tributaries report the greater line/MS CV (for
SONET PM mode) or line/MS BBE or EB (for SDH PM mode) count only
if the signal degrade threshold is exceeded. When the signal degrade
threshold is not exceeded, the 2.5 Gbit/s tributaries retain their original
counts.

Figure 4-7
Tributaries receive greater B2 upon signal degrade of 10 Gbit/s line
OTP2782t
B2
10 Gbit/s
line
OC-192/
STM-64
T/R
OC-48/STM-16
DWDM T/R
Channel A
B2trib A = max (B210G' B2trib A)
OC-48/STM-16
DWDM T/R
Channel B
B2trib B = max (B210G' B2trib B)
OC-48/STM-16
DWDM T/R
Channel C
B2trib C = max (B210G' B2trib C)
OC-48/STM-16
DWDM T/R
Channel D
B2trib D = max (B210G' B2trib D)
To receive warning of a severely degraded line/MS, Nortel recommends that

you use the PM 15min line/section threshold / PM 15 minute MS/RS
threshold alarm and the PM 1 minute line/section threshold / PM 1 minute
MS/RS threshold alarm. For more information, refer to System
Commissioning and Testing Procedures, 323-1801-222.
Wavelength Combiner operation with Dual Gigabit Ethernet

The Dual GE circuit packs are compliant to the 1000 BASE-LX (NTCA90CA)
and 1000 BASE-SX (NTCA90EA) physical layers specified in the IEEE
802.3z standard for 1000 Mbit/s Ethernet (Gigabit Ethernet) transmission. The
1000 BASE-LX optical interface operates at 1310 nm on single-mode fiber
(SMF) with a 10 km reach. The 1000 BASE-SX optical interface operates at
850 nm on multi-mode fiber (MMF) with a reach of 275 m (62.5 m MMF) or
550 m (50 m MMF).
The Dual GE ZX circuit pack supports 1000Base-ZX (1550 nm) single-mode
optical fiber (70 km reach) for each port.
Figure 4-8 displays Dual GE circuit packs in a sample network.

Figure 4-8
Dual GE tributary circuit pack in an Optical Long Haul 1600 network
OTP3367p
Incoming/outgoing
data traffic
Incoming/outgoing
data traffic
OPTera Long
Haul 1600
OPTera Long
Haul 1600
STS-24c/
VC-4-8c
Gigabit
Ethernet
Router/
Switch
10G
T/R
STS-24c/
VC-4-8c
Long Haul
Transport
Network
Wavelength
Combiner
10G
T/R
Gigabit
Ethernet
Router/
Switch
Wavelength
Combiner
Legend
= Dual GE circuit pack in a OPTera Long Haul 1600
Repeater network element
Applications
The Dual GE circuit pack provides a low-cost Gigabit Ethernet interface that
maps native Internet protocol (IP) traffic directly onto the 10G SONET/SDH
payload, and transports this traffic from one metro area to another. Because the
Dual GE circuit pack can carry native IP traffic, there is no need for an external
gearbox to convert the native IP traffic (coming from the data switch/router)
into the SONET/SDH stream. Having Gigabit Ethernet tributary interfaces in
addition to SONET/SDH interfaces on the same network element offers new
revenue-generating opportunities for customers.
Point-of-presence interconnect
In a point-of-presence (POP) interconnect application, national service

providers (NSP) provide connections to the Internet backbone through their
POP sites. The NSPs require high-speed connections between the sites and the
flexibility to adjust bandwidth to adequately service their customer base.
The Dual GE circuit pack as part of the Optical Packet Edge System can make
use of existing optical transport infrastructure to enable this application. It is
also possible to mix different types of services such as data Gigabit Ethernet,
video (concatenated payload) and voice to efficiently utilize 10 Gbit/s
bandwidth.
Dual GE circuit packs enable POP interconnect applications by providing:

point-to-point links between the POP sites across a high-speed optical
network
the ability to quickly add new sites because of its plug-and-play
capabilities and the connectionless nature of packet transport
end-to-end management of the network
Figure 4-9 shows an example of the POP interconnect application.
Figure 4-9
Point-of-presence interconnect
DX4526
NSP POP
Network Element
with Dual GE
circuit pack
Network Element
with Dual GE
circuit pack
NSP POP
Legend
NSP = National Service Provider
POP = Point-of-Presence
Network Access Storage
Optical Long Haul 1600 supports Network Access Storage (NAS) over
Ethernet across the WAN. This application enables the following:
secure off-site data storage
fast (1 Gbit/s) access to data
extended distance between network element sites
disaster recovery
Figure 4-10 shows the network access storage application.

Figure 4-10
Network Access Storage application
DX4525
PoP site
Storage Farm
Office LAN
Transport
Network
File server
LH 1600/
OPTera
Connect DX
LH 1600/
OPTera
Connect DX
Gigabit
Ethernet
Connection
Traffic management
Management of the GE services on the Dual GE circuit pack is performed at
two different levels:
the SONET/SDH level with the standard bay network element user
interface (NE UI) and operations controller user interface (OPCUI)
the GE data level with a Bay Command Console command line interface
(BCC CLI) resident on the Dual GE circuit pack itself, or with a generally
available simple network management protocol (SNMP) manager such as
HP Openview, Nortel Optivity, or Castlerock SNMPc
SONET/SDH level
Operations, administration, maintenance and provisioning (OAM&P) services

are available at the SONET/SDH level with standard NE UI, OPC, and
transaction language 1 (TL1) interfaces.
Note: TL1 is only supported for SONET systems.
For the Dual GE circuit pack, the following are supported:
fault, logs and alarm monitoring at the SONET/SDH level at each port
SONET/SDH path performance monitoring for each STS-24c/VC-4-8c
payload and threshold provisioning

Data level
The Dual GE circuit pack is managed at the data level through SNMP and a
BCC CLI. The following features are supported at the data level:
SNMP v.1 access using the maintenance interface (MI) Ethernet port (data
managers, such as Nortel Optivity, HP Overview, or Castlerock SNMPc
can be used to view SNMP information)
a BCC CLI accessible from the NE UI
full-duplex support only
Ethernet extended frames of up to 9600 bytes
Note: Frame sizes between 1519 and 1536 bytes that are received with
CRC errors are dropped. Frame sizes between 1537 and 9600 bytes are
passed transparently
IEEE 802.3 (1998) user-provisionable auto-negotiation

CAUTION
Auto-negotiation interoperability with switches and routers
Auto-negotiation on the Dual GE circuit pack port and the

switch/router port to which it is connected must be configured
to be both enabled or both disabled. If the ports do not come up
on both Dual GE and the switch/router, or link operation is
unreliable, it is recommended that both are configured to be
auto-negotiation disabled. Contact Nortel for information on
specific switches and routers that are known to be compatible
or incompatible with the Dual GE circuit pack
auto-negotiation.
flow control is not used over the GE interface

Note: The Dual GE circuit pack does not generate pause frames.
all control frames are dropped (received pause frames from link partner are
not honoured)
Layer 3 transparency: Internet protocol (IP), user datagram protocol
(UDP), transmission control protocol (TCP), and all other routing
protocols are transparent to the Dual GE circuit pack
transparent passthrough of VLAN tags (IEEE 802.1Q) and priority fields
(IEEE 802.1P)
Internet control message protocol (ICMP) echo in accordance with
RFC792 (ping)
Head error check (HEC) encoding of Ethernet packets (see Figure 4-11)
Note: You cannot establish a physical loopback on the same port of one
Dual GE circuit pack. For example, it is not supposed to connect the output
port of Port 1 to the input of Port 1 with a fiber-optic patchcord. A fully
operational Gigabit Ethernet link cannot be established if such a
connection is created.
For more information on traffic management at the data level, refer to the
Gigabit Ethernet Data User Guide (NTCA65YA).
Figure 4-11
HEC encoding of Ethernet packets
OTP3381p
Standard Ethernet packet

size is 64 to 1518 bytes.
STS-24c packaged
over OC-192 line
Dual GE supports packet

size of up 9600 bytes for
OPTera Long Haul 1600.
Data
SONET
SDH
GE
Dual GE CP
Port 1
VC-4-8c packaged
over STM-64 line
46-1500
DATA
FCS
1 IEEE 802.3
Preamble SFD Dest Address Source Address Length
Frame Encapsulation
2
Length Variable Type HEC Dest Address Source Address Length
46-1500
DATA
FCS
1 Gbit/s of Ethernet traffic
Path OH
Path OH
Path OH
Path OH
Path OH
Path OH
LOH
Path OH
SOH
Path OH
OC-192/STM-64 line
STS-24c/VC-4-8c
Synchronization
Because the Wavelength Combiner is a SONET/SDH-based multiplexing
application, it requires synchronization to correctly align its incoming
tributary services to the line signal time slots. On the S/DMS TransportNode
TMux, time slot alignment and timing reference to the line interfaces was
provided by the OC-192/STM-64 switch module circuit packs.
The external synchronization (ESI) circuit pack receives timing input from an
external stratum clock with a building-integrated timing supply (BITS) or
from a framing embedded in the incoming OC-192/STM-64 optical signal.
The timing distribution (TD) circuit pack distributes the incoming reference
signal from the selected synchronization source (BITS external signal or one
of the 10 Gbit/s line signals in G7, G12, or G17) to the 10 Gbit/s line interface
circuit packs. Tributary circuit packs are synchronized from their respective
line circuit pack.
Note: A tributary signal cannot be used as a timing source for the
Wavelength Combiner application.
ATTENTION
You cannot use OC-192/STM-64 T/R circuit packs in extension shelf 2 (G22
and G27) to line time your network element.
Network element synchronization modes
Depending on the timing source, different modes of synchronization are
supported on the network element.
The Repeater network element uses the following synchronization modes (see
Figure 4-12).
External timing
External timing mode uses a timing source that is independent of any internal
clock or received optical or tributary signal. An external timing source is
typically a highly accurate stratum clock.
On the Repeater network element, external timing is provided by a BITS. The
external source is 1.544 Mbit/s (DS1) or 2 MHz. The BITS reference input
connections are located at the top of the bay on the synchronization alarm
telemetry terminations (SATT). The SATT terminations are wire wrap pins
(DS1) or coaxial connectors (2 MHz).
Each BITS input (BITSA and BITSB) can accept a 2 MHz signal (2 MHz ESI,
NTCE44BA or NTCE44CA) or a DS1 signal with extended superframe or
superframe format, with a line code of B8ZS or alternate mark inversion
(AMI) (1.5 Mbit/s ESI, NTCA44AA).

Line timing
Line timing is a method of deriving timing from a received transport

OC-192/STM-64 optical signal. The derived signal is used to synchronize
outgoing optical signals in both directions, and all tributary signals. 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 for Dense regenerator, Wavelength Translator and
ODPR applications, 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.
For additional information on synchronization and timing, refer to
Synchronization status messaging (SSM) on page 7-39 and Network
synchronization requirements on page 8-30.

Figure 4-12
Flow of synchronization timing signals for different reference sources
OTP3195p
BITS
Stratum 3
or better
Network
element
(a) External timing
Network element
Network element
(b) Line timing
Network element
Clock
(c) Through timing
(d) Freerun timing
Legend:
= Transport traffic flow
= Tributary traffic flow
= Synchronization timing
= External synchronization reference
Optical Long Haul 1600 Wavelength Combiner interoperability with

Transport Node OC-48 BLSR using k-byte compliancy
An OC-48 2-fiber BLSR going through a Wavelength Combiner must be
running OC-48 Release 16 or later. Nortel encodes the k-bytes in STS-1 #1, as
prescribed by Telcordia (formerly known as Bellcore). In addition, Nortel
transmits an inverted version of these k-bytes in STS-1 #26 as added
robustness. Because of this added robustness, the k-bytes of OC-48 Release 16
are not compliant with Telcordia standards.
The Wavelength Combiner does not process the inverted k-bytes transmitted
in STS-1 #26 by the OC-48 2-fiber BLSR. To prevent the Wavelength
Combiner from receiving invalid k-bytes, the extra robustness must be
disabled in the OC-48 optics connected to the Wavelength Combiner. When
the robustness is disabled, the k-bytes are Telcordia compliant.
Therefore, for all OC-48 network elements in a 2-fiber BLSR that uses a
Wavelength Combiner link, you must use the password-protected BCPROV
tool to make the k-bytes Telcordia compliant.
For the procedure on k-byte compliance, refer to System Commissioning and
Testing Procedures, 323-1801-222.
For more details on the 2.5 Gbit/s optical interfaces supported by the
Wavelength Combiner, refer to Supported circuit packs for the Wavelength
Combiner application on page 4-7.
Wavelength Combiner application in a network

Example of a Wavelength Combiner application in a network
Figure 4-13 shows an example of the Wavelength Combiner application with

OC-48/STM-16 tributaries in an optical network.
Figure 4-13
Example of a Wavelength Combiner application in a network
OTP2902p
Wavelength Combiner
Network
element
Network
element
2.5G
1600G or
MOR Plus
amplifier
Network
element
2.5G
B
2.5G
Network
element
C
D
2.5G
Router
10G
T/R
10G
T/R
MUX /
DEMUX
MUX /
DEMUX
B
C
2.5G
2.5G
Network
element
Router
Note: The Wavelength Combiner circuit pack groups at both terminals

must be originally equipped with the same type of T/R circuit packs,
either TriFEC-capable or non-TriFEC. Failure in following this rule
will probably cause a "Protection scheme mismatch" or "Channel ID
mismatch" alarm to be raised on the subtending OC-48 or TN-16X
equipment and cause subsequent protection path failures.
Example of a Wavelength Combiner application in a Repeater bay

supporting the Wavelength Combiner application.

Figure 4-14
Repeater network element (Wavelength Combiner application)
OTP2997p

Ethernet Wayside
Ethernet Wayside
9 10 11 12 13 14 15 16 17
PT
OW
POPI
PT
ESI (G1)
ESI (G2)
128M MI
MX (G1)
MX (G2)
POPC
32M SC
3 4 5
POPS
Breaker filters
Breaker filters
Control shelf
(Shelf ID: 1)
Attention
engineering rules.
Air Intake
see Note 1
see Note 1
see Note 1
G0
G1
G2
TD
G4A
G3 G4B G5 G6
G7
G8
Main
shelf
(Shelf ID: 2)
Note 1: Equip slots 1 to 4 of the main

shelf with any of the following circuit packs:
MOR Plus amplifier, 2.5G WT,
Dual 2.5G WT on/off ramp, 10G WT,
10G WT (TriFEC), 10G WT SR (TriFEC),
OC-192/STM-64 , or OC-192/STM-64 XR/WT.
Note 2: A Wavelength Combiner circuit
pack group contains one of the following
tributary circuit packs in this
slot: OC-48/STM-16 DWDM T/R,
OC-48/STM-16 T/R SR or Dual GE.
G9
6
7
8
9
10
Wavelength Combiner C
T/R (2.5 Gbit/s) or
Dual GE (see Note 2)
T/R (2.5 Gbit/s) or
T/R (10 Gbit/s)

(see Note 3)
T/R (2.5 Gbit/s) or
T/R (2.5 Gbit/s) or
1
2
3
4
5
Wavelength Combiner B
T/R (2.5 Gbit/s) or
T/R (2.5 Gbit/s) or
6
7
8
9
10
Wavelength Combiner A
T/R (10 Gbit/s)
(see Note 3)
T/R (2.5 Gbit/s) or
T/R (2.5 Gbit/s) or
T/R (10 Gbit/s)

(see Note 3)
T/R (2.5 Gbit/s) or
T/R (2.5 Gbit/s) or
T/R (2.5 Gbit/s) or

T/R (2.5 Gbit/s) or
TD
see Note 1

Air Exhaust
Environmental
control panel
(houses
Note 3: A Wavelength Combiner circuit
three fans)
pack group contains one of the following
Extension
shelf 1
(Shelf ID: 3)
T/R (10 Gbit/s) circuit packs in this

slot: OC-192/STM-64 T/R or
OC-192/STM-64 T/R (TriFEC).
Note 4: A network element equipped

with at least one Wavelength Combiner
circuit pack group requires two ESI and
two half-height TD circuit packs.
G10 G11 G12 G13 G14 G15 G16 G17 G18 G19
T/R (10 Gbit/s)

(see Note 3)
T/R (2.5 Gbit/s)
(see Note 2)
T/R (2.5 Gbit/s)
(see Note 2)
6
7
8
9
10
Wavelength Combiner E
T/R (2.5 Gbit/s)
(see Note 2)
T/R (2.5 Gbit/s)
(see Note 2)
T/R (10 Gbit/s)

(see Note 3)
T/R (2.5 Gbit/s)
(see Note 2)
T/R (2.5 Gbit/s)
(see Note 2)
T/R (2.5 Gbit/s)

(see Note 2)
T/R (2.5 Gbit/s)
(see Note 2)
1
2
3
4
5
Wavelength Combiner D
G20 G21 G22 G23 G24 G25 G26 G27 G28 G29
Environmental
control panel
(houses
three fans)
Extension
shelf 2
(Shelf ID: 4)

and slot 17 (G6) of the control shelf
for point-to-point and pass-through
connectivity of Ethernet communication.
You must also equip the network element
with MOR Plus amplifier circuit packs.
Note 6: Equip G1 and G3 of the main
shelf with 1625 nm OSC circuit packs to
obtain bidirectional OSC functionality on
a single optical fiber. Be sure to follow
the appropriate equipping rules when you
equip MOR Plus amplifier circuit packs in
the first four slots of the main shelf.
5-1
Optical dedicated protection ring

(ODPR) application
5-
Chapter overview
This chapter provides a detailed description of the optical dedicated protection
ring (ODPR) application supported by the Repeater network element.
Section
Page
Description of the optical dedicated protection ring (ODPR)

application
5-2
Supported circuit packs for the ODPR application
5-4
ODPR application and network protection
5-9
Protection switching
5-15
Signal flow and module interconnection
5-17
ODPR application with TriFEC
5-22
Network element user interface (NE UI) support
5-24
Signal degrade (SD) threshold provisioning
5-25
Alarms affected by the ODPR application
5-26
OPC support for the ODPR application
5-27
ODPR application in a network
5-27
5-2 Optical dedicated protection ring (ODPR) application
Description of the optical dedicated protection ring (ODPR)

application
Introduced in Release 4, the ODPR application extends existing self-healing
ring protection switching to unprotected 10 Gbit/s router-based services. The
ODPR application functionality features 1+1 unidirectional, nonrevertive
protection switching of SONET/SDH 10 Gbit/s signals at the optical layer.
Normally, the ODPR application provides protection for Internet backbone
routers at OC-192c or STM-64c.
An ODPR circuit pack group allows a mix of circuit packs with the following
functionality:
provisionable FEC and non-FEC
provisionable traffic mode or fixed traffic mode
short-reach receiver
The Repeater network element supports up to six ODPR circuit pack groups.
An ODPR circuit pack group consists of five circuit packs: one optical switch
module (OSM) and four optical interfaces with the same traffic mode. An
ODPR circuit pack group contains the following circuit packs:
one OSM circuit pack (NTCA39AA) and a mix of the following circuit
packs
10G WT circuit packs (NTCA07xx)
10G WT (TriFEC) circuit packs (NTCF07xx)
10G WT SR (TriFEC) circuit packs (NTWR07AA)
OC-192/STM-64 XR/WT circuit packs (NTCF04xx)
one OSM circuit pack (NTCA39AA) and a mix of the following circuit
packs
OC-192/STM-64 XR circuit pack (NTCA04xx)
Note 1: The ODPR application does not support 2.5 Gbit/s WT circuit
packs.
Note 2: The 10G WT SR (TriFEC) circuit pack is a cost-effective solution
for off-ramp optical interfaces of an ODPR circuit pack group. Make sure
you equip the 10G WT SR (TriFEC) circuit pack in the off-ramp position.
Note that the ODPR software provisioning rules do not prevent you from
equipping the 10G WT SR (TriFEC) circuit pack in an on-ramp position.
Note 3: You must provision all optical interfaces in an ODPR circuit pack
group to the same traffic mode (3R for WT or REGEN for XR).
Optical dedicated protection ring (ODPR) application 5-3
Note 4: The message exchange (MX) circuit pack is equipped in slot 10

of the control shelf. It is highly recommended but not mandatory to equip
a second MX circuit pack in slot 11. However, two MX circuit packs are
mandatory for a Repeater that includes at least one ODPR circuit pack
group.
The ODPR circuit pack group autoprovisions when the circuit packs that form
the group are inserted into a Repeater bay. When all circuit packs of an ODPR
circuit pack group are seated in the correct slots, each circuit pack
autoprovisions. After autoprovisioning, the ODPR circuit pack group is
created and the circuit packs become active and ready to carry traffic.
Figure 5-1 shows an ODPR circuit pack group in a Repeater bay. This figure
identifies the connections that link each of the ODPR application building
blocks. The ODPR application is compatible with all DWDM equipment
including DWDM couplers, OADM couplers, and 1600G Amplifier modules.
Figure 5-1
ODPR circuit pack group (building blocks connections)
OTP2903p
Working Working
Repeater
WT
or
XR
WT
or
XR
on ramp
off ramp
Protection Protection
O
S
M
WT
or
XR
WT
or
XR
on ramp
off ramp
ODPR
Repeater
Protection
B
On ramp
Off ramp
Rx
Working
A
On ramp
Off ramp
Rx
OSM
Splitter
In
Selector
Out
Wavelength Translator (WT)

or
Dense Regenerator (XR)
Supported circuit packs for the ODPR application

The ODPR application allows provisioning for the circuit packs listed in Table
5-1.
Table 5-1
Supported ODPR circuit packs
Circuit packs (see Note 1 and Note 2) PEC
Introduced in release Notes
Optical switch module (OSM)
NTCA39AA
10G WT
NTCA07xx
1.5
10G WT (TriFEC)
NTCF07xx
See Note 3.
10G WT SR (TriFEC)
NTWR07AA
See Note 3, Note 4.
OC-192/STM-64 XR
NTCA04xx
1.2
OC-192/STM-64 XR/WT
NTCF04xx
See Note 5.
1-1 on page 1-3.
Note 3: For information on TriFEC circuit packs, refer to ODPR application with TriFEC on page 5-22
and Appendix B: TriFEC applications on page 12-1.
Note 4: For more information on short-reach optics, refer to Appendix D: Short-reach optics on page
14-1.
packs on page 13-1.
Optical switch module (OSM) circuit pack (NTCA39AA)

The OSM circuit pack is the core of the ODPR circuit pack group. The OSM
circuit pack contains an optical splitter that divides the signal coming from the
10 Gbit/s client interface into a working signal and a protection signal. The
OSM circuit pack also contains a 2 x 2 optical switch that selects the best
signal between the working and protection signals at the receiving end. The
OSM circuit pack is a single-width circuit pack with six front-access optical
connectors. The connectors are contained within two extendable panels.
Figure 5-2 shows the OSM circuit pack.

Figure 5-2
Optical switch module (OSM) circuit pack
OTP1197
Extendable
line panel
(two connectors)
Fiber carrier
Extendable
client panel
(four connectors)
Extendable
panel
Latch
Carrier
handle
Optical
connectors
O UT C
IN
OU T D
IN
Carrier
handle
OUT
IN
OUT
IN
LOS
S
LO
W
P
W
P
Latch
Side view
Front view
Note: The OSM circuit pack has six front-access optical

connectors: four in the extendable client panel and
two in the extendable line panel.
The OSM circuit pack has six optical interfaces:

one input connection to the customer equipment on the client side (in the
extendable panel on the right)
one output connection to the customer equipment on the client side (in the
extendable panel on the right)
two input (working and protection) connections to the network interface
equipment on the carrier side (in the extendable panel on the left)
two output (working and protection) connections to the network interface
equipment on the carrier side (in the extendable panel on the left)
The OSM circuit pack has four light-emitting diodes (LED) on its faceplate:
one circuit pack active green LED
one circuit pack fail red LED
one LOS LED for the input of the working signal
one LOS LED for the input of the protection signal
Note: A red LED that is ON normally indicates a partial or complete
failure of the circuit pack (for example, a Circuit pack fail alarm). A red
LED that is ON can also indicate a mismatch condition on the circuit pack
(for example, a Circuit pack mismatch alarm).
Figure 5-3 shows the functionality of the OSM circuit pack. If an optical fiber
cut or any failure at an intermediate Repeater network element site occurs, all
downstream Repeater network elements send a failed SONET/SDH signal that
reach the far-end off-ramp 10 Gbit/s optical interface. The off-ramp circuit
pack detects the failure and sends information to the OSM circuit pack through
GraceLAN messages by way of the Repeater network element backplane.
These GraceLAN transmissions contain protection status messages that are
processed and decoded by the OSM circuit pack. The OSM circuit pack always
evaluates the signal quality of both working and protection signals before
performing switching operations. An optical protection switch occurs when a
signal failure or a signal degrade alarm is raised. These conditions are
monitored using the B2 byte of the OC-192/STM-64 line/MS overhead. The
signal degrade threshold is user-provisionable. If any or both of these
conditions are detected by the OSM circuit pack, tail-end switching occurs.
These two conditions are monitored by the off-ramp 10 Gbit/s optical
interfaces.

Figure 5-3
OSM circuit pack (optical switching functionality)
OTP1338p
Signal broadcasted
on both directions
Valid optical signal

Failed SONET/SDH signal
Fiber
cut
Repeater NE1
ODPR CPG
1w
1p
OSM
On-ramp
WT or XR
Signal received from both directions.

WT or XR detects signal quality at
the optical and SONET/SDH level.
Information provided to the OSM.
OSM performs tail-end switching
Repeater
Rx
Working = Protection
Rx
Repeater NE2
ODPR CPG
Tx
Tx
Repeater
Off-ramp
WT or XR
OSM
Note 1: Only one direction is shown for simplicity.

Note 2: Signal is broadcasted in both directions.
10 Gbit/s Wavelength Translator circuit packs

The ODPR application supports 10G WT, 10G WT SR, 10G WT (TriFEC),
and OC-192/STM-64 XR/WT (traffic mode set to 3R for WT) circuit packs as
part of an ODPR circuit pack group. The ODPR application supports 10 Gbit/s
optical interfaces only. The WT is an open optical interface that translates non
Nortel Networks wavelengths and integrates them into a DWDM network. The
WT circuit pack accepts any OC-192/STM-64 or OC-192c/STM-64c signal.
The WT circuit pack shares on-ramp and off-ramp capabilities with overhead
(OH) transparency to enable wavelength leasing applications for subtending
multivendors. The WT circuit packs function as a gateway between the optical
transport layer of the network and the service interface of the subtending
equipment.
An ODPR circuit pack group can consist of any mix of optical interfaces if
they are all of the same traffic mode type and all engineering, thermal, and
power rules are followed. You can mix TriFEC-capable and non-TriFEC,
merged XR/WT and non-merged, and short-reach circuit packs within the
same ODPR circuit pack group. All 10G WT SR circuit packs must be placed
in off-ramp optical interface positions since the transmit port is equipped with
short-reach optics.
When WT circuit packs are used within an ODPR circuit pack group, they are
configured in two pairs: a working pair and a protection pair. Each pair has
on-ramp and off-ramp facilities. By monitoring the B2 byte in the
SONET/SDH line/MS overhead, the line/MS receiving 10G WT (off-ramp)
circuit packs can measure the signal quality of the received waveform to detect
signal degrade and signal failure conditions. Another function of the WT
circuit pack is to buffer the received signals to a correct power level for the end
user.
The line/MS transmitting WT circuit packs regenerate the client wavelength.
Both line/MS transmitting WT circuit packs and line/MS receiving WT circuit
packs are DWDM transmitters with provisionable output power and received
signal quality monitoring capabilities. When the 10 Gbit/s signal is
regenerated after it is split, the signal allows for different wavelength
availability requirements on the working and protection paths. The
regeneration also allows the provisioning of different input power levels for
working and protection line amplifiers.
For information on overhead processing for the WT circuit pack, refer to
Overhead processing on page 3-6.
10 Gbit/s Dense regenerator circuit packs
The ODPR application supports full 10 Gbit/s SONET/SDH regenerator
functionality using the OC-192/STM-64 XR and OC-192/STM-64 XR/WT
(traffic mode set to REGEN for XR) circuit packs. The 10 Gbit/s Dense
regenerator reconstructs an OC-192 SONET or STM-64 SDH signal to extend
reach in a DWDM network. The OC-192/STM-64 XR and
OC-192/STM-64 XR/WT (traffic mode set to REGEN for XR) circuit packs
operate in a manner similar to the WT circuit pack.
The OC-192/STM-64 XR and OC-192/STM-64 XR/WT (traffic mode set to
REGEN for XR) circuit packs reshape, retime, and reamplify (3R
regeneration) the incoming signal of both on-ramp and off-ramp facilities.
The OC-192/STM-64 XR and OC-192/STM-64 XR/WT (traffic mode set to
REGEN for XR) circuit packs are equipped with an electro-optic modulator,
photo detector, and the required RF circuitry to convert the 10 Gbit/s
modulated optical signal to the electrical domain for 3R regeneration and
overhead processing. The signal is then converted back to an optical signal.
Because the OC-192/STM-64 XR and OC-192/STM-64 XR/WT (traffic mode
set to REGEN for XR) circuit packs completely regenerate the signal
overhead, transparency of services is not available.
When the OC-192/STM-64 XR and OC-192/STM-64 XR/WT (traffic mode

set to REGEN for XR) circuit packs are used within an ODPR circuit pack
group, they are configured in two pairs: a working pair and a protection pair.
Each pair contains an on-ramp and an off-ramp facility. The line/MS receiving
(off-ramp) circuit packs have the same roles as the line/MS receiving
10G WTs. The line/MS transmitting (on-ramp) circuit packs restore the client
wavelength and have the same function as the line/MS transmitting 10G WT
circuit packs. Both line/MS transmitting (on-ramp) 10 Gbit/s circuit packs and
line/MS receiving (off-ramp) 10 Gbit/s circuit packs are DWDM transmitters
with provisionable output power and received signal quality monitoring
capabilities.
For information on overhead processing for the XR circuit pack, refer to
ODPR application and network protection

The ODPR application provides 1+1 unidirectional, nonrevertive protection
through optical switching. The ODPR application is similar in functionality to
a SONET/SDH UPSR/SNCP system.
The ODPR application provides the following:
a 1+1 protection scheme at the optical level over a separate optical fiber (a
second wavelength protects a working wavelength)
a unidirectional switching scheme that provides optical switching between
traffic in the receive (off ramp) direction, but not in the transmit (on ramp)
direction
a nonrevertive switching mode: traffic does not automatically return to its
working channel when the condition fault that caused the switch is
corrected
Figure 5-4 shows the concept of an ODPR application in a network that
contains three terminal sites. Each terminal site includes an ODPR circuit pack
group. The connection between each terminal site that includes an ODPR
circuit pack group is a point-to-point line connection. An ODPR application is
therefore a collapsed ring that consists of multiple point-to-point line
connections. The channel type (working or protection) that passes through a
node depends on the node position in the network. For the network shown, the
pass-through path at the node in City B is a protection channel, and the
pass-through path at the nodes in City A and City C are working channels.
Pass-through connectivity is achieved using a regenerating device such as a
Wavelength Translator or a Dense regenerator.

Figure 5-4
ODPR application (collapsed ring)
OTP0872
City A
City B
Legend
W
P
Working
Protection
W P W P
City C
The optical switching in an ODPR application is performed on a wavelength

by wavelength basis at a specific line rate, therefore providing protected
carrier grade wavelength services. The ODPR application is beneficial mainly
for the Internet backbone router market and allows protection for unprotected
OC-192c/STM-64c router interfaces (see Figure 5-5). The ODPR application
supports only SONET or SDH traffic at 10 Gbit/s.
Figure 5-5 also shows the connectivity between two unprotected client routers
and the ODPR application terminals. The ODPR application is deployed at
terminal sites, preferably co-located with router interfaces. Route the working
line and the protection line separately to prevent double-failure scenarios. The
line systems are Repeater network elements with Wavelength Translator or
Dense regenerator circuit packs and line amplifiers that can carry the working
and protection channels across a carrier network.

Figure 5-5
ODPR application (network supporting unprotected routers)
OTP1358p
Working off ramp
Line
system
Working on ramp
Working off ramp
OSM
OSM
- unprotected
router
- short-reach
interfaces
- inter-office
- OC-192c/
STM-64c
payload
Protection on ramp
Protection off ramp
ODPR circuit
pack group
Working on ramp
Line
system
Protection off ramp
Protection on ramp
ODPR circuit
pack group
The main advantage of the ODPR application is the ability to decouple the
service layer from the transport layer by allowing transparent protection
switching on the line system. Protection is therefore non-intrusive and does not
affect traffic performance or wavelength availability at the end-user level.
Note: Optical switching is performed within 50 ms after fault detection.
Failures are detected within 10 ms.
The ODPR application also addresses a problem where a ring carries
unbalanced traffic. In such a scenario, providing protection bandwidth all the
way around the ring is inefficient. If traffic between cities is distributed
unevenly and shared protection is the available protection scheme, reserving
ring protection wastes bandwidth.
In Figure 5-6,
site A to B has five working OC-192/STM-64c wavelengths
site B to C has two working OC-192/STM-64c wavelengths
site C to D has one working OC-192/STM-64c wavelength
site D to A has three working OC-192/STM-64c wavelengths
In this example a carrier must allocate bandwidth to protect five wavelengths
all around the ring.
Figure 5-6
ODPR application (shared protection for unbalanced ring)
OTP1359p
Working 5
Working 2
Protection 5
Protection 5
Site B
Site A
Site C
Client
Router
Protection 5
Working 3
Site D
Protection 5
Working 1
With this set of conditions, an ODPR application opens up each

terminal-to-terminal connection in the ring to allow the exact amount of
working channels and protection channels to be carried on different paths, and
on separate optical fibers (see Figure 5-7).

Figure 5-7
ODPR application
OTP1360p
Working 5
Protection 5
Working 2
Site B
ODPR
Protection 2
Site C
ODPR
Site A
ODPR
Client
router
Protection 3
Site D
ODPR
Protection 1
Working 1
Working 3
Legend
Regenerator
The ODPR application is deployed on the Repeater network element. In an

ODPR application, one protected bidirectional channel is achieved with five
circuit packs that make up the ODPR circuit pack group. At the core of the
ODPR circuit pack group is a 2 x 2 optical switch module (OSM) circuit pack.
The OSM circuit pack splits the signal coming from the unprotected 10 Gbit/s
source into two identical signals. The OSM circuit pack can select either the
working or protected input.
All incoming and outgoing line signals are buffered by any of the following
circuit packs if their traffic modes (WT or XR) are identical throughout the
ODPR circuit pack group:
10G WT
10G WT (TriFEC)
10G WT SR (TriFEC) (off-ramp optical interfaces only)
OC-192/STM-64 XR
OC-192/STM-64 XR/WT
Note 1: You can equip the short-reach circuit packs in off-ramp positions
only because the Tx port on this circuit pack has short-reach optics.
Note 2: You must follow thermal and power engineering positioning rules
when you equip a bay with 10G WT (TriFEC), and 10G SR (TriFEC)
circuit packs.
Note 3: An ODPR circuit pack group supports a mix of the following
functionality within the same ODPR circuit pack group: short-reach,
TriFEC-capable or non-TriFEC, provisionable traffic mode or fixed traffic
mode. The traffic mode (REGEN for XR or 3R for WT) for all circuit
packs within an ODPR circuit pack group must be same. You cannot mix
XR circuit packs and WT circuit packs within the same ODPR circuit pack
group.
The OC-192/STM-64 XR circuit packs are also used as signal quality
discriminators.
Considerations
You must deploy an ODPR application network according to fixed rules and
limitations. Before deploying an ODPR application network, you must review
the following limitations:
The ODPR application is nonrevertive and provides unidirectional
switching only.
The Amplifier network elements do not support the ODPR application.
You cannot mix a traffic mode REGEN (XR) circuit pack and traffic mode
3R (WT) circuit pack within the same ODPR circuit pack group.
The ODPR circuit pack group does not support 2.5 Gbit/s circuit packs.
You cannot add an ODPR circuit pack group to a live traffic system.To add
protection to an existing link, you must be able to use the subtending
equipment for protection switching. You must reconnect optical fiber and
perform system line-up and testing (SLAT) procedures to configure a new
ODPR circuit pack group. You must reconfigure ODPR circuit pack
groups out-of-service, when the tributary traffic has switched to protection.
The K1 and K2 line/MS overhead bytes do not trigger switching.
The OSM circuit pack switches when an alarm indication signal (AIS-L or
MS-AIS), loss of light (LOL), loss of signal (LOS), signal degrade (SD), or
signal fail (SF) condition occurs. This switch causes the traffic source to move
from the working off-ramp circuit packs to the protection off-ramp circuit
packs. The switch is nonrevertive. In other words, the traffic remains on the
protection path even after the condition clears. You can manually switch the
OSM from protection to working.
An SD condition occurs if the BER reaches the SD threshold (normally set to
1 x 10-8).
Note 1: The SD condition is detected by monitoring the B2 byte.
Note 2: The SD threshold is provisionable from 1 x 10-5 to 1 x 10-9 on all
OC-192/STM-64 optical facilities that are part of the ODPR circuit pack
group.
An SF occurs if the following conditions exist:
a BER higher than the SF threshold (normally set to 1 x 10-3)
Note: The SF condition is also detected by monitoring the B2 byte.
an LOS
an LOF
an AIS-L or MS-AIS
An LOL occurs under the following conditions:

an optical fiber break between an off-ramp circuit pack and the OSM
circuit pack
a disconnected optical fiber between an off-ramp circuit pack and the OSM
circuit pack
a faulty off-ramp circuit pack
a faulty OSM circuit pack
Protection switch behaviors and hierarchy

If a switch request is initiated when another switch request is already active,
the higher priority request overrides the lower priority request. If the lower
priority request is user-initiated and is the earlier request, the lower priority
request is cleared.
priority request is user-initiated and is the new request, the lower priority
request is denied.
priority request is an automatic switch request, the lower priority request
is set to pending.
Note: Pending means that the automatic switch starts again when all
higher priority requests are cleared.
A switch request clears under the following circumstances:
when the condition that started the request is removed (for example, an
automatic switch)
when a user releases the request (for example, a lockout, or forced switch
in nonrevertive mode)
when a higher priority switch request overrides it (for example, a forced
switch or manual switch)
Beginning with the highest priority, the hierarchy of user switch requests is as
follows:
1 lockout
2 SF on protection
3 forced switch
4 SF on working
5 SD
6 manual switch
Note 1: SD for working and protection have the same priority.
Note 2: LOL on protection is the same as SF on protection. LOL on
working is the same as SF on working.
Signal flow and module interconnection

To understand ODPR functionality, you must examine the interworkings of the
ODPR circuit pack group. Figure 5-8 displays the signal flow within an
ODPR circuit pack group from the output port of the router to the optical link
and back from the link to the input port of the router.
Figure 5-8
ODPR circuit pack group (interconnection)
OTP2999p
1600G Amplifier/
MOR Plus amplifier
1600G Amplifier/
MOR Plus amplifier
Optical Mux/Demux
DWDM optics
West
Working
Rx
Tx
Rx
East
Protection
Tx
Off ramp
On ramp
G5
(Tx)
G6
(Rx)
G8
(Tx)
G9
(Rx)
Rx
Tx
Rx
Tx
Tx
Tx
Rx
Rx
OSM
G7
2x2
optical
switch
Passive
optical
splitter
Rx
Tx
Unprotected client interface
Figure 5-8 shows that the output of the 10 Gbit/s source is connected to the
input port of the OSM circuit pack. The router transmits its output to the OSM
circuit pack located in G7 of the Repeater network element. The OSM circuit
pack splits the signal into two identical signals that are sent to the on-ramp
circuit packs through fiber-optic cable connections. Select the on-ramp circuit
packs based on your transparency requirements. The on-ramp circuit packs are
located in G5 and G8 of the Repeater network element. The off-ramp circuit
packs are located in G6 and G9. The off-ramp circuit packs can use the same
circuit pack types as the on-ramp circuit packs with the addition of the 10G
WT SR designed specifically for off-ramp applications. All circuit packs
within an ODPR circuit pack group must be provisioned to the same traffic
mode: REGEN for XR or 3R for WT. An ODPR circuit pack group does not
support a mix of XR and WT circuit packs within an ODPR circuit pack group.
This signal flow example applies for all ODPR circuit pack groups in the
Repeater network element. The on-ramp circuit packs receive signals from the
splitter; the signals are then translated into Nortel DWDM wavelengths, and
finally retransmitted to the DWDM couplers. The DWDM couplers are the
same Mux/Demux devices that were supported in previous releases of Optical
Long Haul 1600.
Note: A Nortel wavelength forms part of a wavelength plan, determined
by the ITU-T standards, that support analog maintenance (AM). Nortel
proprietary AM dither provides a means of signal identification and helps
manage signals at the optical level.
From the optical link, the DWDM signals are demultiplexed and sent to the
off-ramp circuit packs. The off-ramp circuit packs detect any signal failure
(SF) or signal degrade (SD) conditions by monitoring the B2 line/MS
overhead byte. Optical switching occurs if any of the following SF alarms are
detected at the input port of the off-ramp circuit pack:
loss of signal (LOS)
loss of frame (LOF)
line/MS alarm indication signal (AIS-L)
The OSM circuit pack also switches when a loss of light (LOL) condition
occurs. This alarm indicates a problem between an off-ramp circuit pack and
the working input/protection input port of the OSM circuit pack.
If the SONET/SDH signal received by the off-ramp circuit pack is not failed
but degraded such that the BER reaches the SD threshold (normally 1 x 10-8),
then the off-ramp circuit pack sends a signal to the OSM circuit pack
indicating the failure condition. This signal causes the OSM circuit pack to
switch. If both the working and protection signals are degraded, the OSM
circuit pack switches to the best path.
Normal traffic flow
Figure 5-9 shows normal traffic flow when no SD, SF, LOL, or AIS-L (or
MS-AIS) conditions exist. The traffic from the client input port (on-ramp) is
split and transmitted on separate optical fibers through working and protection
on-ramp circuit packs. The traffic to the client output port (off-ramp) is
received from the working off-ramp circuit pack.

Figure 5-9
Normal traffic flow under 1+1 protection scheme
OTP1369p
On ramp, working circuit pack (G5)
OSM (G7)
Off ramp, working circuit pack (G6)
On ramp
(client IN)
Off ramp
(client OUT)
On ramp, protection circuit pack (G8)
Off ramp, protection circuit pack (G9)

Legend
Traffic flow
Traffic flow after a unidirectional 1+1 protection switch

Figure 5-10 shows traffic flow using a unidirectional 1+1 protection scheme
when an SD, SF, LOL, or AIS-L condition exists. The traffic from the client
input port (on ramp) is split and transmitted on separate optical fibers using
working and protection on-ramp circuit packs. The traffic to the client output
port (off ramp) is received from the protection off-ramp circuit pack.

Figure 5-10
Traffic flow after 1+1 protection switch
OTP1370p
On ramp, working circuit pack (G5)
OSM (G7)
Off ramp, working circuit pack (G6)
On ramp
(client IN)
SD, SF, LOL or AIS-L condition

Off ramp
(client OUT)
On ramp, protection circuit pack (G8)
Off ramp, protection circuit pack (G9)

Legend
Traffic flow
Optical fiber connections for the ODPR circuit pack group

Figure 5-11 shows the circuit pack arrangement for the ODPR circuit pack
group and the optical fiber connections between the OSM circuit pack and the
10 Gbit/s on-ramp and off-ramp circuit packs. This figure shows only the
optical fiber routing for the first ODPR circuit pack group located in slots 1 to
5 (G0 to G4) in the main shelf of the Repeater network element. The same
optical fiber connections are valid for the other five ODPR circuit pack groups.

Figure 5-11
ODPR circuit pack group interconnection
OTP1362p
Fiber from/to client router
To/from DWDM
equipment
or line
From/to DWDM
equipment
or line
Protection
In
In
In
In
Input Output
Client ports
In(W) In(P)
Out
Out
Out(W) Out(P)
Out
Out
WT or XR
(on ramp)
slot 1
WT or XR
(off ramp)
slot 2
OSM
slot 3
WT or XR
(on ramp)
slot 4
WT or XR
(off ramp)
slot 5
Note: Optical connections to the OSM circuit pack are made through
extendable panels on the right-hand side of the circuit pack (see Figure 5-2
on page 5-5).

Optical Long Haul 1600 Release 5 introduced forward error correction (FEC)
for the ODPR application. This section provides information on triple forward
error correction (TriFEC) functionality for the ODPR application.
Note: Forward error correction (FEC) is not available on Dense
regenerator circuit packs because FEC is expected to be performed at
terminal sites by the on-ramp and off-ramp circuit packs.
Determining whether the line/MS is severely degraded (for ODPR
applications with TriFEC)
FEC counts. For more information on displaying facility PM counts, refer to
Performance Monitoring Procedures, 323-1801-520.
Table 5-2
Line/MS FEC
(15 minute)
Line/MS FEC
(1 day)
3.00 x 10-38
831
1.00 x 10-35
43
4156
2.00 x 10-34
87
8313
2.00 x 10-31
433
41 565
3.00 x 10-30
866
83 130
1.00 x 10-27
4330
415 649
2.00 x 10-26
8659
831 298
1.00 x 10-23
43 297
4 156 490
2.00 x 10-22
86 594
8 312 979
1.00 x 10-19
432 968
41 564 897
2.00 x 10-18
865 935
83 129 795
1.00 x 10-15
4 329 677
415 648 972
6.00 x 10-15
6 927 483
665 038 351
Note 1: If the BER of the corrected payload exceeds 1.00 x 10-14, the
PM mode), line/MS BBE or EB (for SDH PM mode), and line/MS FEC
counts are inhibited. Unavailable seconds (UAS) will inhibit the SES
counts after ten consecutive SES. If this occurs, the BER of the corrected
payload approaches the signal degrade threshold.
Note 2: The TriFEC-capable 10G WT circuit pack propagates
approximately two percent of the incoming line/MS CV (for SONET PM
mode), line/MS BBE or EB (for SDH PM mode) counts to the subtending
client equipment (errors before TriFEC is applied). These errors are
propagated through the SONET/SDH overhead because TriFEC is only
applied to the payload.
Signal degrade threshold and protection switching in ODPR applications
When the provisioned signal degrade threshold is exceeded in an ODPR

application without TriFEC, the Signal degrade/MS signal degrade alarm is
raised. The Signal degrade/MS signal degrade alarm is triggered based on
the uncorrected (raw) BER of the line/MS CV (B2) errors (for SONET PM
mode) or line/MS BBE or EB errors (for SDH PM mode). However, for
TriFEC applications, the BER of the corrected payload can be much lower than
the uncorrected (raw) BER.
When TriFEC is enabled on the line/MS, line/MS CV (for SONET PM mode),
line/MS BBE or EB (for SDH PM mode) errors are corrected. However, the
counts reported by the Display facility PM Counts command is not adjusted
for the errors corrected by TriFEC. As such, the line/MS CV (for SONET PM
mode), line/MS BBE or EB (for SDH PM mode) counts correspond to the
uncorrected (raw) errors.
Because the Signal degrade/MS signal degrade alarm is triggered based on
the uncorrected (raw) BER, and not based on the BER of the corrected
payload, misleading error counts may be propagated to subtending equipment.
To avoid the Signal degrade/MS signal degrade alarm from being triggered,
the signal degrade threshold is automatically set to 1.0 x 10-6 when you
provision TriFEC on the TriFEC-capable OC-192/STM-64 T/R circuit packs.
When the signal degrade threshold is (automatically) set to 1.0 x 10-6, the
Signal degrade / MS signal degrade alarm is not raised because an LOS is
raised at an (uncorrected) BER of 3.2 x 10-6. Therefore, an automatic
protection switch occurs upon an LOS condition.
Note 1: For details on error correction provisioning and on the
automatically provisioned signal degrade threshold value, see Table 3-6 on
page 3-13 and Table 3-7 on page 3-13, respectively.
Note 2: For a 10G WT (TriFEC) circuit pack that is not part of an ODPR
group, the Signal degrade / MS signal degrade alarm does not apply.

To receive warning of a severely degraded line/MS, Nortel recommends that

you use the PM 15min line/section threshold / PM 15 minute MS/RS
threshold alarm and the PM 1 minute line/section threshold / PM 1 minute
MS/RS threshold alarm. For more information, refer to System
Commissioning and Testing Procedures, 323-1801-222.
When the PM thresholds are provisioned correctly, a PM 15min line/section
threshold / PM 15 minute MS/RS threshold alarm or a PM 1 minute
line/section threshold / PM 1 minute MS/RS threshold alarm is raised to
indicate a severely degraded line in an ODPR application. In this case, it is
recommended that you perform a manual protection switch from the working
to protection path or vice versa, as required. For more information on
performing a manual protection switch, refer to Protection Switching
Procedures, 323-1801-311.
Network element user interface (NE UI) support

To support the ODPR application, the Optical Long Haul 1600 Repeater
software includes the following menus:
the Optical Protection Menu (sub-menu of the Protection Menu)
the Protection Performance Menu (sub-menu of the PM Menu)
Optical Protection Menu
Use the Optical Protection Menu to list, query, and edit protection settings on
the protected 10 Gbit/s optical interfaces. Figure 5-12 shows the commands
available from the Optical Protection Menu.
Figure 5-12
OTP1364p

----------------------0. Quit
1. LIST protection summary
2. QueRy all Protection Members
3. QueRy Protection Group
4. EDit Protection Group
5. Operate Lockout
6. Release Lockout
7. Operate Forced
8. Release Forced
9. Operate Manual
10. Release Manual
For more information on the commands in the Optical Protection Menu, refer
to Protection Switching Procedures, 323-1801-311.
Protection Performance Menu

Use the Protection Performance Menu to display and clear the protection
switching statistics. The protection switch counts are compiled and displayed
as protection switching statistics. Figure 5-13 shows the commands available
from the Protection Performance Menu.
Figure 5-13
Protection Performance Menu
OTP1365p
Protection Performance Menu[ ]

--------------------------0. Quit
1. SELect
2. Display protection pm Counts
3. Display History Counts
4. Clear Counts
For more information on the commands in the Protection Performance Menu,

refer to Performance Monitoring Procedures, 323-1801-520.
Signal degrade (SD) threshold provisioning

SD threshold provisioning allows you to set the switching decision threshold
according to your specific requirements. The SD threshold is provisionable for
all 10 Gbit/s facilities that are part of an ODPR circuit pack group. Access the
provisioning command from the Facility Menu of the NE UI.
For specific instructions on changing the SD threshold, refer to Provisioning
and Operations Procedures, 323-1801-310.
Alarms affected by the ODPR application

The following alarms support the OSM circuit pack and the ODPR application
facilities:
Circuit pack missing
Circuit pack fail
Circuit pack mismatch
Protection switch complete
Force switch request
Manual switch request
Protection switch fail
Lockout request
Loss of light
Switch oscillation control active
Line AIS/MS AIS
Note: The Line AIS or MS AIS alarm cannot be raised on 10G WT,
10G WT (TriFEC), 10G WT SR, 10G WT SR (TriFEC), OC-192/STM-64
XR, or OC-192/STM-64 XR/WT circuit packs if the circuit packs are not
part of an ODPR circuit pack group.
Signal degrade/MS signal degrade

Note: The Signal degrade or MS signal degrade alarm is only raised
on 10G WT, 10G WT (TriFEC), 10G WT SR, 10G WT SR (TriFEC),
OC-192/STM-64 XR, or OC-192/STM-64 XR/WT circuit packs if the
circuit packs are part of an ODPR circuit pack group.
Signal fail/MS excessive BER

Note: The Signal fail or MS excessive BER alarm is only raised on
10G WT, 10G WT (TriFEC), 10G WT SR, 10G WT SR (TriFEC),
OC-192/STM-64 XR, or OC-192/STM-64 XR/WT circuit packs if the
circuit packs are part of an ODPR circuit pack group.
Except for the Loss of light alarm, these alarms already exist for the
OC-192/TN-64X product.
Note: For information on clearing these alarms, refer to Trouble Clearing
and Module Replacement, 323-1801-543.
OPC support for the ODPR application

The OPC user interface (UI) fully supports the ODPR application. To provide
this support, the following enhancements were added:
Fault management: All OSM circuit pack related alarms were moved to the
network banner line and to the Transaction language 1 (TL1) fault
management interface.
Note: TL1 is available only for SONET configurations.
Full performance monitoring capability: The OPC PM Collection Filter

tool and internal collection process can be used to monitor the quality of
the traffic carried across the network every 15 minutes.
Protection attributes: All switch protection information is passed to
Optical Network Management through the OPC.
ODPR application in a network

Figure 5-14 shows an example of a network that includes the ODPR
application.
Figure 5-14
Example of an ODPR application in a network
OTP1343p
On-ramp site
Repeater
MOR Plus
Post
ODPR with
WT or XR
Amplifier sites
Repeater
MOR Plus
MSA
Pre/Post
10 Gbit/s DWDM
MOR Plus
MSA
Pre/Post
Regenerator
site
Repeater
MOR Plus
Pre/Post
10G WT
or
OC-192/
STM-64 XR
Amplifier sites
Repeater
MOR Plus
MSA
Pre/Post
MOR Plus
MSA
Pre/Post
Off-ramp site
Repeater
MOR Plus
Pre
ODPR with
WT or XR
10 Gbit/s DWDM
Note 1: Only one optical path is represented.

Note 2: For end-to-end transparency, use 10 Gbit/s WT circuit packs at all on-ramp
and off-ramp sites.
Example of an ODPR application in a Repeater bay

supporting the ODPR application.

Figure 5-15
Repeater network element (ODPR application)
OTP2998p

Filler circuit pack
Filler circuit pack
9 10 11 12 13 14 15 16 17
PT
OW
POPI
PT
Filler
Filler
128M MI
MX
MX
POPC
32M SC
3 4 5
POPS
Breaker filter
Breaker filter
Attention
engineering rules.
Control
shelf
(Shelf ID: 1)
Air Intake
10G WT or XR (see note 1)
G9
8
9
ODPR
10
OSM
G8
OSM
OSM
3
4
ODPR
10
8
9
ODPR
G4
G3
G2
OSM
G7
G5 G6
G1
8
9
ODPR
10
OSM
3
4
ODPR
G10 G11 G12 G13 G14 G15 G16 G17 G18 G19

OSM
Note 3: ODPR does not support

3
4
ODPR
G0
Note 2: Do not mix circuit pack traffic

mode (REGEN for XR or 3R for WT)
within the same ODPR circuit
pack group.
Note 1: This slot can contain the

following XR (10 Gbit/s) circuit packs:
OC-192/STM-64 XR or OC-192/STM-64
XR/WT. This slot can also contain the
following WT (10 Gbit/s) circuit packs:
10G WT, OC-192/STM-64 XR/WT,
or 10G WT (TriFEC). The 10G WT SR
(TriFEC) circuit pack is supported in offramp positions.
1

Air Exhaust
G20 G21 G22 G23 G24 G25 G26 G27 G28 G29
Main
shelf
(Shelf ID: 2)
Environmental
control panel
(ECP) houses
three fans
Extension
shelf 1
(Shelf ID: 3)
Environmental
control panel
(ECP) houses
three fans
Extension
shelf 2
(Shelf ID: 4)
6-1
6-
Chapter overview
This chapter provides a description of the MOR Plus amplifier application
supported by the Repeater network element.
Section
Page
Description of the MOR Plus amplifier
6-2
Mid-stage access
6-2
Integrated optical service channel
6-3
Complete suite of optical layer management tools
6-3
Scalability for DWDM backbones
6-4
MOR Plus amplifier application guides
6-4
6-2 MOR Plus amplifier application
Description of the MOR Plus amplifier

The Nortel Multiwavelength Optical Repeater (MOR) Plus amplifier provides
extended reach dense wavelength division multiplexing (DWDM) solutions
on 2.5 Gbit/s and 10 Gbit/s backbone routes transporting up to 32 wavelengths
(320 Gbit/s aggregate span capacity). Using erbium-doped fiber amplifier
(EDFA) technology, the MOR Plus amplifier boosts the level of the optical
signal in each direction without costly electrical/optical conversions. Proven
in real-world applications, MOR Plus bidirectional optically amplified
systems were the first to achieve 32-wavelength operation.
The MOR Plus amplifier technology provides bidirectional optical
amplification for 32 counter-propagating wavelengths on one optical fiber.
The MOR Plus amplifier can be configured as a bidirectional optical pre/post
amplifier when co-located with service-terminating or regenerator network
elements. The MOR Plus amplifier can also be configured as a bidirectional
optical line amplifier at intermediate sites along a backbone route. Multiple
optical amplifier building blocks can be cascaded on a route to achieve the
required reach. MOR Plus amplifier DWDM solutions are engineered for
robust operation over the wide variety of optical fiber types currently deployed
in today's networks. MOR Plus amplifier solutions are also engineered to
enable cost-effective expansion to 1.12 Tbit/s backbones in conjunction with
1600G Amplifier systems. MOR Plus amplifier circuit packs can be installed
in available slots in Optical Long Haul 1600 bays and in S/DMS
TransportNode OC-192/TN-64X systems. Stand-alone MOR Plus amplifier
bay configurations are also available.
Mid-stage access
The MOR Plus amplifier permits per-band access at mid-stage for in-line
optical components. Per-band access allows dispersion compensation to be
performed on only a portion of the wavelengths on a DWDM link.
Compensation can be performed on the Blue and Red bands independently.
This type of compensation is required when some wavelengths experience a
dispersion amount which is significantly different than other wavelengths in
the system. The in-line optical components enable advanced optical
networking applications (for example, distributed dispersion compensation,
wavelength add/drop, and optical cross connection). DWDM backbones based
on the MOR Plus amplifier are always ready to handle tomorrow's optical
networking needs. Mid-stage access applications do not materially affect
either optical link budgets or the number of optical fiber spans supported.
MOR Plus amplifier application 6-3
Integrated optical service channel

The MOR Plus amplifier offers a 1510 nm optical service channel (OSC) to
permit full operations access at remote line amplifier sites. The OSC supports
all network management functions including alarm reporting, provisioning,
optical layer fault management, optical layer maintenance tools, and software
downloads. With the OSC, seamless management is maintained from end to
end across the network. In a typical application that uses separate optical fibers
for working traffic and protection, MOR Plus amplifier plug-ins are paired at
each site to create a complete bidirectional 1510 nm OSC for management
access. In this arrangement, Red and Blue wavelength propagation occurs in
opposite directions on the working and protection fibers. The 16 wavelengths
in the Red spectrum range between 1547.5 nm and 1561.00 nm, and the 16
wavelengths in the Blue spectrum range between 1528.40 nm and
1542.50 nm. The 1510 nm OSC signal always travels in the same direction as
the Red wavelengths.
In applications where a separate protection optical fiber is not available, you
can pair the MOR Plus amplifier with a 1625 nm OSC-only plug-in to achieve
a complete bidirectional optical service channel that uses 1510 nm and
1625 nm wavelengths traveling in opposite directions on a single optical fiber.
Complete suite of optical layer management tools

The MOR Plus amplifier also offers an extensive portfolio of optical layer
management features that promote robust operation, high-quality service,
rapid fault diagnosis, and simplified service turn-up. These features include
the following:
optical layer parameter provisioning including inventory information for
each wavelength
proactive performance monitoring of the optical layer
peak power control for DWDM optics
analog maintenance power measurement tools for each wavelength in each
direction
optical reflectometer tool that measures unwanted signal reflections
power optimizer that reduces the time and effort required to determine and
provision optimum optical transmitter power levels when turning up or
modifying a DWDM route
graphical fault management tools for the optical layer
6-4 MOR Plus amplifier application
Scalability for DWDM backbones

DWDM backbones based on MOR Plus amplifiers easily scale from 2 to 32
wavelengths. If required, you can cost-effectively add an additional 80
wavelengths from the L-band using 1600G Amplifier applications. This
alternative provides up to 1.12 Tbit/s aggregate capacity on a single optical
fiber and protects against stranded investment in a 320 Gbit/s DWDM
infrastructure. The 1600G Amplifier application features a highly modular
architecture that easily scales to keep today's costs in line with current capacity
requirements.
MOR Plus amplifier application guides

For detailed information about the MOR Plus amplifier application for the
Repeater network element, refer to the following documents:
(NTY312DX)
This guide describes DWDM system applications from 2 to 32- with
100 GHz optical channel spacing designed with MOR Plus amplifiers.
This guide also provides planning, engineering, and ordering information
for deploying these applications.
(NTY311DX)
This guide describes DWDM system applications from 2 to 16- with
200 GHz optical channel spacing designed with MOR, MOR Plus, or a
mix of MOR and MOR Plus amplifiers. This guide also provides planning,
engineering, and ordering information for deploying these applications.
MOR Plus Optical Add/Drop Applications Guide (NTY313DX)
This guide describes the various optical channel add/drop topologies in
both 100 GHz and 200 GHz optical channel spacing types of DWDM
systems. This guide also provides planning, engineering, and ordering
information for deploying these applications.
MOR Plus Optical Layer OAM&P Guide (NTY314DX)
This guide contains technical information related to the operation,
administration, maintenance, and provisioning of Optical Long Haul 1600
network elements equipped with MOR Plus amplifier circuit packs.
7-1
Operations, administration,
maintenance, and provisioning
(OAM&P)
7-
Chapter overview
This chapter describes operations, administration, maintenance, and
provisioning (OAM&P) features for Optical Long Haul 1600. The following
topics are covered in this chapter.
Section
Page
Commissioning and span of control upgrades
7-2
Performance monitoring
7-7
Network element user interface (NE UI) support for the Repeater
7-18
External communications (DCC and OSC)
7-23
OAM&P for Dual Gigabit Ethernet circuit packs
7-25
Optical link interoperability
7-37
Synchronization status messaging (SSM)
7-39
20-character network element name
7-48
Routing fundamentals
7-49
OPC support
7-62
TL1 facility and equipment provisioning
7-65
Strong authentication
7-67
Network management
7-74
Ethernet Wayside
7-74
Open access orderwire
7-82
7-2 Operations, administration, maintenance, and provisioning (OAM&P)
Commissioning and span of control upgrades

New deployments and multiple catalog software (MCS) support
The MCS feature provides support for different software network element
loads for multiple network element types on a single operations controller
(OPC). The MCS feature allows a network planner to perform span of control
(SOC) upgrades and new build deployments of Repeater, Amplifier, and
Optical Amplifier Shelf (OAS) network elements using a single software load.
Each network element type requires its own catalog file. The selection of one
catalog file over another catalog file depends on the network element type. The
catalog file is fixed when the bay is commissioned. MCS functionality does
not change the current upgrade procedure. MCS facilitates the software
upgrade process by allowing a selective type of upgrade where only specific
network elements undergo a true software upload. All software upgrades are
performed in-service.
When a new network is built, each Optical Long Haul 1600 network element
is commissioned with a commissioning maintenance interface (Golden MI).
After a network element is commissioned to a specific network element type
(Repeater, Amplifier, or OAS), the unused catalog files on the commissioning
MI are stored and recovered when the restorecmi command is used. The
restorecmi command is only available for new build systems. The restorecmi
command is not available for upgrades to the current release from a previous
release. The OPC, with its MCS, is then able to control, manage, and store data
from each network element in the network according to each network element
type.
New build deployment
You can deploy all applications listed in Table 7-1. You can include all
applications in the same OPC SOC. Each SOC can manage either SDH or
SONET types, but not both simultaneously.
Table 7-1
Network element
Repeater
Dense regenerator
Wavelength Combiner
MOR Plus amplifier
Amplifier
1600G Amplifier
Optical amplifier shelf
MOR and MOR Plus amplifier
Operations, administration, maintenance, and provisioning (OAM&P) 7-3
In a new network build, you require a commissioning maintenance interface

(MI) circuit pack to apply the network element load to each bay. When
installed, the MI contains the required software library. You can select the
required application from the software library.
Network overlay
If required, you can include applications introduced in previous releases in the

same SOC as the current release. In this case, you must perform a
span of control upgrade to the current release.
When you implement Optical Connect DX with Optical Long Haul 1600, your
network requires a separate span of control for the Optical Connect DX system
(see Figure 7-1).
Figure 7-1
Optical Long Haul 1600 interworking
OTP2540p
Second
span of
control
Second
span of
control
First span of control

Repeater
Wavelength
Combiner
OPTera
Connect DX
OC-192/
STM-64
10 Gbit/s
feeds
2.5 Gbit/s
feeds
Repeater
Terminal
site 1
1600G
Amplifier
Repeater
2.5 Gbit/s/10 Gbit/s
DWDM
2.5G WT
10 Gbit/s
feeds
Repeater
ODPR with
XR or WT
Line amplifier
site
1600G
Amplifier
Regenerator
site
2.5G WT,
10G WT,
OC-192/
STM-64 XR,
or OC-192/
STM-64
XR/WT
Terminal
site 1
1600G
Amplifier
Wavelength
Combiner
10 Gbit/s
feeds
2.5 Gbit/s
feeds
OPTera
Connect DX
OC-192/
STM-64
Repeater
2.5G WT
10 Gbit/s
feeds
Repeater
ODPR with
XR or WT
Restore commissioning MI command

If you make a provisioning error during a commissioning procedure (for
example, you select the incorrect catalog to commission a network element),
you can use the restorecmi command to restore a Golden MI (commissioning
MI). The restorecmi command is available for Release 4 or later software
loads. You can change the network element type using the restorecmi
command by first decommissioning the network element and then
recommissioning it as a different network element type using the same MI.

This change can only be performed if the network element has not been
upgraded. All provisioning information is lost when the system is
decommissioned.
The restorecmi command is only available for new build systems. The
restorecmi command is not available for upgrades to the current release from
a previous release.
Product upgrade paths
Table 7-2 lists information on the different options available when you deploy
or upgrade Optical Long Haul 1600 network elements. You must use the
commissioning MI (Golden MI) for all first deployments (green field
deployments).
The supported upgrade paths to the Optical Long Haul 1600 Release 10 load
are:
Hardware Baseline checking
The Hardware Baseline tool tracks the product engineering code (PEC) and
hardware release number of circuit packs compatible with the current Optical
Long Haul 1600 software release. These circuit packs form the hardware
baseline for the release.
The Healthcheck tool uses the Hardware Baseline tool during release
upgrades. The OPC compares the active baseline with circuit packs installed
in the system when preparing for a release upgrade.
Interoperability
For other products to operate with the current release of Optical Long
Haul 1600, a minimum baseline is required.
Subtending tributaries
Equipment subtending from the Optical Long Haul 1600 network elements
must be managed by its own separate span of control.
MOR Plus amplifier interoperability
Tributaries operating with the Optical Long Haul 1600 MOR Plus amplifier
must be running a minimum software baseline, as follows:
OC-48 Release 16.1
OC-192 Release 7.02
TN-64X Release 2

1600G Amplifier interoperability
To achieve optimal performance with 1600G Amplifiers that are running

Release 10, refer to 1600G Amplifier Unidirectional Network Application
Guide (NTY314AL).
Table 7-2
Optical Long Haul 1600 deployment and software upgrade paths
Optical Long Haul
1600 release
Commissioning MI (Golden MI)

supported deployment
Possible software upgrade path
1.0
OAS network elements
None (introduction)
1.2
Repeater network elements
None (introduction)
1.53 (see Note 1)
Release 1.0 to 1.53
Release 1.2 to 1.53
Combiner network elements
Introduction
Release 1.53 to 2.03
2.03 (see Note 2)

3.02
Amplifier network elements
None (introduction of Amplifier)
2.03 to 3.02
1.53 to 3.02

4.02

5.13

6 (see Note 3)

7.01

Optical Long Haul 1600 deployment and software upgrade paths
Optical Long Haul
1600 release
Commissioning MI (Golden MI)

supported deployment
Possible software upgrade path
9.01
Release 7.01 to 10
Release 9.01 to 10
10
Note 1: Optical Long Haul 1600 Release 1.53 to Release 2.03 is a span of control (SOC) only upgrade
because this upgrades the OPC software to include management of Combiner network elements into
an existing Release 1.5 network. Network element software catalog files are upgraded with the new
release information.
Note 2: Optical Long Haul 1600 Release 2.03 supports the new deployment of OAS, Repeater, and
Combiner network elements through the Multiple catalog support (MCS) functionality. MCS also allows
the SOC upgrade of an Optical Long Haul 1600 OAS or Repeater from Release 1.53 to Release 2.03.
This SOC upgrade allows the use of a single SOC for all network element types. A Combiner network
element can only be created upon commissioning MI deployment, not upon upgrade or
decommissioning of an existing Repeater or OAS network element.
Note 3: Optical Long Haul 1600 Release 6 supports upgrades from Release 4.02 and Release 5.13 to
Release 6 only. You cannot commission an Optical Long Haul 1600 bay as a Combiner network element
for Release 6 and subsequent releases. The Combiner network element is no longer a supported
network element type. In-service Combiner network elements are transparently converted to Repeater
network elements as part of the upgrade process beginning with Release 6.
For more information on MCS, refer to New deployments and multiple

catalog software (MCS) support on page 7-2.
Performance Monitoring (PM) is the process that monitors the performance of
a facility through performance data collection and analysis, without
interruptions to service. The functions of performance monitoring include:
collection of PM counts
reporting of PM counts
storage of PM counts
threshold crossing alerts when PM counts exceed the corresponding
threshold settings
For detailed information on performance monitoring, refer to Performance
Monitoring Procedures, 323-1801-520.
Note: Amplifier and Optical Amplifier Shelf (OAS) network elements do
not support PM counts.
Performance monitoring for the Wavelength Combiner application
Optical Long Haul 1600 supports the same performance monitoring (PM) set
as in OC-192 Release 7 and TN-64X Release 2. However, not all PM counts
are used by the Wavelength Combiner application. Physical PM counts (Rx
power monitoring), and line/MS FEC (forward error correction) counts are not
supported on the OC-48/STM-16 T/R circuit pack. However, Rx power
monitoring and FEC monitoring are supported on all the OC-192/STM-64 T/R
circuit packs (TriFEC-capable and non-TriFEC).
Note: Counts for path performance monitoring are only available at the
intermediate path level for Wavelength Combiner circuit pack groups
(CPG). When you monitor the performance at the path level, you are
actually monitoring the performance at the intermediate path level.
For information on threshold default values, refer to Performance Monitoring
Table 7-3 and Table 7-4 list the SONET and SDH PM counts, respectively, that
the Wavelength Combiner application supports.
Note: For information on performance monitoring for Dual Gigabit
Ethernet tributaries, see Performance monitoring on page 7-25.

Table 7-3
SONET PM parameters supported by the Wavelength Combiner application
PM
(see Note)
OC-48/STM-16 T/R
circuit packs
(NTCA30CK) (NTCA30xK)
(NTCA30AL)
OC-192/STM-64 T/R
circuit packs
(NTCA06xx) (NTCF06xx)
(NTCF16xx)
Dual Gigabit Ethernet

circuit packs
(NTCA90CA) (NTCA90EA)
Optical facilities
OPR
No
Yes
No
IQ
No
Yes
No
Section/RS
CV
Yes
Yes
No
ES
Yes
Yes
No
SES
Yes
Yes
No
SEFS
Yes
Yes
No
Line/MS
CV
Yes
Yes
No
ES
Yes
Yes
No
SES
Yes
Yes
No
UAS
Yes
Yes
No
FC
Yes
Yes
No
FEC
No
Yes
No
Path
CV
Yes
Yes
Yes
ES
Yes
Yes
Yes
SES
Yes
Yes
Yes
UAS
Yes
Yes
Yes
FC
Yes
Yes
Yes
Note: For a description of PM parameters, see Performance Monitoring Procedures, 323-1801-520.

Table 7-4
SDH PM parameters supported by the Wavelength Combiner application
PM
(see Note)
OC-48/STM-16 T/R
circuit packs
(NTCA30AL)
OC-192/STM-64 T/R
circuit packs
(NTCF16xx)

circuit packs
Optical facilities
OPR
No
Yes
No
IQ
No
Yes
No
Section/RS
EB
Yes
Yes
No
BBE
Yes
Yes
No
ES
Yes
Yes
No
SES
Yes
Yes
No
OFS
Yes
Yes
No
BBER
Yes
Yes
No
ESR
Yes
Yes
No
SESR
Yes
Yes
No
Line/MS
EB
Yes
Yes
No
BBE
Yes
Yes
No
ES
Yes
Yes
No
SES
Yes
Yes
No
UAS
Yes
Yes
No
SEP
Yes
Yes
No
BBER
Yes
Yes
No
ESR
Yes
Yes
No
SESR
Yes
Yes
No
SEPI
Yes
Yes
No
UAT
Yes
Yes
No
FEC
No
Yes
No

SDH PM parameters supported by the Wavelength Combiner application
PM
(see Note)
OC-48/STM-16 T/R
circuit packs
(NTCA30AL)
OC-192/STM-64 T/R
circuit packs
(NTCF16xx)

circuit packs
Path
EB
Yes
Yes
Yes
BBE
Yes
Yes
Yes
ES
Yes
Yes
Yes
SES
Yes
Yes
Yes
UAS
Yes
Yes
Yes
SEP
Yes
Yes
Yes
BBER
Yes
Yes
Yes
ESR
Yes
Yes
Yes
SESR
Yes
Yes
Yes
SEPI
Yes
Yes
Yes
UAT
Yes
Yes
Yes
Note: For a description of the PM parameters, refer to Performance Monitoring Procedures,

323-1801-520.
The Optical Long Haul 1600 software PM system automatically configures the
operation mode of the supported circuit packs and sends the required
provisioning data. The PM system operates automatically and does not require
user intervention.
The PM system can support a maximum of 20 of the following tributary
services:
OC-48/STM-16 DWDM T/R (NTCA30xK)
OC-48/STM-16 T/R SR (NTCA30CK)
OC-48/STM-16 T/R (1310 nm) (NTCA30AL)
The PM system can support a maximum of 40 of the following tributary
services:
Dual Gigabit Ethernet LX (NTCA90CA)
Dual Gigabit Ethernet SX (NTCA90EA)
Dual Gigabit Ethernet ZX (NTCA90GA)
The PM system can support a maximum of five of the following 10 Gbit/s

line/MS circuit packs:
OC-192/STM-64 T/R (NTCA06xx)
OC-192/STM-64 T/R (TriFEC) (NTCF06xx)
Performance monitoring for the Wavelength Translator and Dense
regenerator applications
Optical Long Haul 1600 supports the same performance monitoring (PM) set
as in OC-192 Release 7.0 and TN-64X Release 2.0. However, not all PM
counts are used by the Dense regenerator and Wavelength Translator
applications. Because the WT and XR circuit packs operate in 3R regeneration
mode, PM supports section/RS counts, but not line/MS PM counts or Path PM
counts. However, the TriFEC-capable 10G WT circuit packs support both
section/RS and line/MS PM counts (including line/MS FEC).
The single 2.5Gbit/s WT (NTCA70xx) does not support physical PM counts
(Rx power monitoring). The Dual 2.5G on/off ramp supports Rx power
monitoring on Port 2 only.
For information on threshold default values, refer to Performance Monitoring
Table 7-5 and Table 7-6 list the SONET and SDH PM counts, respectively, that
the Wavelength Translator and Dense regenerator applications support.
Table 7-5
SONET PM parameters supported by the Wavelength Translator and Dense regenerator
applications
PM
2.5 Gbit/s WT 10 Gbit/s WT
(see Note 1) (NTCA70xx) (NTCA07xx)
(NTCF04xx: 3R
for WT mode)
TriFEC-capable
10 Gbit/s WT
(NTCF07xx)
(NTWR07AA)
(NTWR17AA)
10 Gbit/s XR
(NTCA04xx)
(NTCF04xx:
REGEN for XR
mode)
(NTCF14xx:
REGEN for XR
mode)
Dual 2.5G WT
on/off ramp
(NTCA72xx)
Optical facilities
OPR
No
Yes
Yes
Yes
Yes (Port 2
only)
IQ
No
Yes
Yes
Yes
No
Section/RS
CV
Yes
Yes
Yes
Yes
Yes
ES
Yes
Yes
Yes
Yes
Yes

SONET PM parameters supported by the Wavelength Translator and Dense regenerator
applications
PM
2.5 Gbit/s WT 10 Gbit/s WT
(see Note 1) (NTCA70xx) (NTCA07xx)
(NTCF04xx: 3R
for WT mode)
TriFEC-capable
10 Gbit/s WT
(NTCF07xx)
(NTWR07AA)
(NTWR17AA)
10 Gbit/s XR
(NTCA04xx)
(NTCF04xx:
REGEN for XR
mode)
(NTCF14xx:
REGEN for XR
mode)
Dual 2.5G WT
on/off ramp
(NTCA72xx)
SES
Yes
Yes
Yes
Yes
Yes
SEFS
Yes
Yes
Yes
Yes
Yes
Line/MS
CV
No
No
Yes
No
No
ES
No
No
Yes
No
No
SES
No
No
Yes
No
No
UAS
No
No
Yes
No
No
FC
No
No
Yes
No
No
FEC
No
No
Yes
No
No
Yes
No
Protection
PSC
(see Note 2)
No
Yes
Yes
Note 1: For a description of the PM parameters, refer to Performance Monitoring Procedures,

323-1801-520.
Note 2: The PSC parameter only applies to off-ramp (receive) facilities in an ODPR group.

Table 7-6
SDH PM parameters supported by the Wavelength Translator and Dense regenerator applications
PM
2.5 Gbit/s WT
(see Note 1) (NTCA70xx)
10 Gbit/s WT
(NTCA07xx)
(NTCF04xx: 3R
for WT mode)
TriFEC-capable
10 Gbit/s WT
(NTCF07xx)
(NTWR07AA)
(NTWR17AA)
Dual 2.5G WT
10 Gbit/s XR
on/off ramp
(NTCA04xx)
(NTCA72xx)
(NTCF04xx:
REGEN for XR
mode)
(NTCF14xx:
REGEN for XR
mode)
Optical facilities
OPR
No
Yes
Yes
Yes
Yes (Port 2 only)
IQ
No
Yes
Yes
Yes
No
Section/RS
EB
Yes
Yes
Yes
Yes
Yes
BBE
Yes
Yes
Yes
Yes
Yes
ES
Yes
Yes
Yes
Yes
Yes
SES
Yes
Yes
Yes
Yes
Yes
OFS
Yes
Yes
Yes
Yes
Yes
BBER
Yes
Yes
Yes
Yes
Yes
ESR
Yes
Yes
Yes
Yes
Yes
SESR
Yes
Yes
Yes
Yes
Yes
Line/MS
EB
No
No
Yes
No
No
BBE
No
No
Yes
No
No
ES
No
No
Yes
No
No
SES
No
No
Yes
No
No
UAS
No
No
Yes
No
No
SEP
No
No
Yes
No
No
BBER
No
No
Yes
No
No
ESR
No
No
Yes
No
No
SESR
No
No
Yes
No
No
SEPI
No
No
Yes
No
No

SDH PM parameters supported by the Wavelength Translator and Dense regenerator applications
PM
2.5 Gbit/s WT
(see Note 1) (NTCA70xx)
10 Gbit/s WT
(NTCA07xx)
(NTCF04xx: 3R
for WT mode)
TriFEC-capable
10 Gbit/s WT
(NTCF07xx)
(NTWR07AA)
(NTWR17AA)
Dual 2.5G WT
10 Gbit/s XR
on/off ramp
(NTCA04xx)
(NTCA72xx)
(NTCF04xx:
REGEN for XR
mode)
(NTCF14xx:
REGEN for XR
mode)
UAT
No
No
Yes
No
No
FEC
No
No
Yes
No
No
Yes
No
Protection
PSC
(see Note 2)
No
Yes
Yes
Note 1: For a description of the PM parameters, refer to Performance Monitoring Procedures,

323-1801-520.
Note 2: The PSC parameter only applies to off-ramp (receive) facilities in an ODPR group.
The Optical Long Haul 1600 software PM system automatically configures the
operation mode of the supported circuit packs and sends the required
provisioning data. The PM system operates automatically and does not require
user intervention.
The PM system can support a maximum of 30 Wavelength Translator circuit
packs or 30 Dense regenerator circuit packs for each network element.
SONET and SDH (ETSI) PM counts
The collection mode for SONET and SDH performance monitoring data is
based on Telcordia (formerly Bellcore) GR-253. Optical Long Haul 1600
addresses the requirements as described in ITU-T standards G.828 and G.829.
SONET PM is based on bit-error measurement and SDH PM is based on
block-error measurement.
Bit-error measurement: When the BIP-8 byte is checked, any of the eight
parity bits that indicate a parity error give rise to one bit error. The
maximum number of bit errors per block or frame is eight.
Block-error measurement: When the BIP-8 byte is checked, if one or more
of the eight parity bits indicate a parity error, only one block error is
counted. The maximum number of bit errors per block or frame is one.
You can collect PM counts in either SONET or SDH mode. If the network
element is commissioned as SDH or if the facility is provisioned to collect
SDH PM counts, SDH parameters appear in the facility and path PM displays.
Similarly, if the network element is commissioned as SONET or if the facility
is provisioned to collect SONET PM counts, SONET parameters appear in the
facility and path PM displays.
The shelf controller (SC) circuit packs support a mix of both SONET and SDH
PM counts. Depending on the application, you can provision some facilities
under SONET mode and others under SDH mode. This arrangement provides
flexibility for global applications where end-to-end connections move across
mixed protocol networks.
Engineering rules for PM counts are as follows:
SDH or SONET facility provisioning is performed on an individual facility
basis for all facilities of a given OC-n/STM-n rate (FAC Collection mode),
or on a network element basis (NE Collection mode).
Optical Long Haul 1600 and Optical Connect DX optical switch bays
support SDH and SONET PM counts. New commissioned network
elements default to the collection mode based on the selected protocol for
the network element. For example, if you commission a network element
as SONET, then the PM collection mode defaults to SONET.
The differences between SONET and SDH PM collection are as follows.
In SONET mode, all counts (zero or nonzero) are stored in the history.
In SDH, only non-zero counts are stored in the history bins.
In SONET mode, 32 15-minute history bins are recorded in PM
collection. In SDH mode, 16 nonzero 15-minute history bins are
recorded in PM collection.
Commands specific to the collection mode
You can switch the PM collection mode between SONET and SDH on a
facility basis or on a network element basis using the following commands
(see Figure 7-2):
Fac Collection Mode
NE Collection Mode

Figure 7-2
Performance Monitoring Menu
OTP2277t
Performance Monitoring Menu

--------------------------0. Quit
1. Facility Performance
2. Path Performance
3. PRotection Performance
4. Fac Collection Mode
5. NE Collection Mode
The default PM collection mode of the network element is set to SONET or

SDH during the network element commissioning process. You can change the
default PM collection mode of the network element using the NE Collection
Mode command in the NE UI. All circuit packs provisioned after you change
the PM collection mode will automatically collect PM counts in the
provisioned mode (SDH or SONET).
Untimed bins
The untimed PM bin contains the total PM counts starting from a specified
date and time. You can reset the untimed bin. The untimed bin is available for
the path performance and facility performance monitoring counts.
Untimed PM counts allow you to monitor an optical fiber or path link from a
start time that you set. If you are concerned with the long-term degradation of
signals, you can now evaluate facility performance or path performance over
a given length of time.
Note: You cannot retrieve or clear untimed bins through Transaction
Language 1 (TL1) commands.
Engineering rules for untimed PM counts are as follows:
Availability of untimed PM counts is provided by default: you cannot
remove this column from the user interface.
Unlike 15-minute and 1-day PM counts, untimed PM counts do not clear
automatically. You must clear untimed PM counts manually.
Untimed PM counts do not affect alarms or alerts. Alarms and alerts for
15-minute and 1-day PM counts are not affected.
No threshold crossing alert (TCA) is available for the untimed PM bin.
You can clear untimed PM counts for a specific facility or path, or for an
entire facility or path.
The NE UI indicates the date and time you started the untimed bin (see Figure
7-3 and Figure 7-4). Use the Start Untimed Counts command in the facility
and path performance monitoring menus to reset the bin to zero.
Figure 7-3
Untimed PM counts (STM-64)
OTP2147t
Payload: STM1 1
Unit : STM64
G7
NE Id: 5312
Mode : SDH
Direction: RX
Location : NEND
Untimed Start: 1995/01/01 00:01:54
15-minute
current
last
Path
Path
Path
Path
Path
Path
EB
BBE
ES
SES
UAS
SEP
0
0
0
0
0
0
0
0
0
0
0
0
1-day
Untimed
current
last
31
31
5
1
44
0
0
0
0
0
0
0
31
31
5
1
44
0
Figure 7-4
Untimed PM counts (OC-192)
OTP2146t
Payload: STS1 1
Unit : OC192
G7
NE Id: 2625
Mode : SONET
Direction: RX
Location : NEND
Untimed Start: 2004/12/25 17:25:55
15-minute
current
last
Path
Path
Path
Path
Path
CV
ES
SES
UAS
FC
0
0
0
0
0
0
0
0
0
0
1-day
Untimed
current
last
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Concatenated PM counts
Concatenated PM support is applicable only when you query concatenated
path PM counts in a Wavelength Combiner application. You can select only the
first channel of a concatenated payload when querying information for that
payload. The PM counts for a concatenated payload are displayed for the first
channel of the concatenation only. Before Release 6, when you queried a
channel other than the first channel, the counts displayed zeros.
Note: Wavelength Translator and Dense regenerator applications do not

support path PM counts.
Network element user interface (NE UI) support for the Repeater
The NE UI can perform Wavelength Combiner, ODPR, Dense regenerator, and
MOR Plus application commands from the same NE UI. Although you may
choose to equip a Repeater network element with only several of the supported
applications, all commands and menus for all applications are displayed.
However, you can execute only the commands that are supported by the circuit
packs installed in your Repeater network element.
The NE UI for the Repeater network element
supports access to all Wavelength Combiner, Dense regenerator,
Wavelength Translator, and ODPR facilities on the network element
through one NE UI
includes an OCn facility menu for the SONET OC-48 T/R (DWDM and
short-reach), OC-192 T/R (TriFEC-capable), Wavelength Translator, and
Dense regenerator circuit packs
includes an STMn facility menu for the SDH STM-16 T/R (DWDM and
short-reach), STM-64 T/R (TriFEC-capable), Wavelength Translator, and
The NE UI offers the following advantages:
allows you to locate commands related to optical hardware easily
allows you to easily query and change configuration information for the
optical hardware
The NE UI supports the following attributes:
Repeater network element added capability with respective shelf IDs
(main shelf ID is 2, first extension shelf ID is 3, and second extension shelf
ID is 4)
MOR Plus end-to-end power control for 32- (automatic channel
discovery, channel provisioning information propagation and local locking
capabilities, output power propagation and local locking capabilities)
merged Wavelength Translator, Dense regenerator, ODPR, and
Wavelength Combiner circuit pack inventory
64K NE ID
transmitter Analog Maintenance provisioning support (AM1 or AM2)
restructured Optical Facility Menu that groups all optical-related
submenus and includes transmitter output provisioning, received physical
parameters, MOR Plus facility, and measurements, and MOR Plus DCC
control
Tx Optical Facility that includes wavelength-specific information

(previously found in the Equipment Menu).
software provisionable transmitted power, wavelength, and chirp
Note: Chirp is not provisionable on the OC-48/STM-16 T/R circuit packs
and single and Dual 2.5G WT circuit packs.
additional Tx provisioning: AM1 or AM2 dither provisioning and NLS

dither provisioning
restorecmi command to restore the MI to the golden state following errors
made during commissioning of a new network element
delete extension shelf command
secondary state support for circuit packs and circuit pack groups
support for timing distribution (TD) and synchronization changes
support equipment protection for external synchronization interface (ESI),
message exchange (MX) and TD (when equipped)
provisionable forward error correction for FEC-capable circuit packs
Refer to Figure 7-5 to Figure 7-7 for overviews of the NE UI menu. Refer to
Figure 7-8 for an example of an NE UI screen.

Figure 7-5
NE UI overview for the Repeater network element
OTP2788p
Main
0. Quit
1. SELect
2. Display facility pm Counts
3. Display facility pm Ratio
4. Display facility pm
additional Events
6. Clear counts
7. THresholds
0. Quit
1. SELect
2. Display path pm Counts
3. Display path pm Ratio
4. Display path pm
additional Events
6. Clear counts
7. THresholds
0. Quit
1. SELect
2. Display protection pm
Counts
3. Display History counts
4. Clear Counts
0. Quit
1. list all active ALarms
2. list all active ALarms by
Severity
3. list all active ALarms by
Class
4. ALarm Details
5. List all Historical alarms
ALarms
Facility
Performance
Performance
Monitoring
OPTical
Protection
Path
Performance
PRotection
Timing
Generation
0. Quit
2. QueRy all Protection
Members
Member
6. ADD member to
protection group
7. DELete member from
protection group
8. Operate Forced
9. Release Forced
10. Operate Manual
11. Release Manual
Timing
Distribution
0. Quit
Members
Member
6. ADD member to
protection group
7. DELete member from
protection group
8. Operate Forced
9. Release Forced
10. Operate Manual
11. Release Manual
Protection
Performance
0. Quit
1. SELect
2. QueRy facility Collection
Mode
3. EDit facility Collection
Mode
Facility
Collection
Mode
0. Quit
1. SELect
2. QueRy ne Collection
Mode
3. EDit ne Collection Mode
NE
Collection
Mode
0. Quit
Members
4. Operate Lockout
5. Release Lockout
6. Operate Forced
7. Release Forced
8. Operate Manual
9. Release Manual
Circuit
Pack Group
Protection
0. Quit
Members
4. Operate Lockout
5. Release Lockout
6. Operate Forced
7. Release Forced
8. Operate Manual
9. Release Manual

Figure 7-6
OTP2789p
Main
Network
Element
Equipment
0. Quit
1. QueRy NE
2. QueRy cp inventory
3. EDit NE
4. EDit SHelf Position
5. DELete NE
6. DELete extension SHelf
7. NE Timing Provisioning
8. NE Alarm Provisioning
9. SHelf Alarm Provisioning
10.Manual Area Address
management
11.NE Routing Level
12.RELeases
13.Led Test
Circuit
Pack Group
Equipment
0. Quit
1. SELect
2. QueRy cpg
3. EDit cpg
4. Change State
5. DELete cpg
6. Alarm Provisioning
7. QueRy cpg Members
Query
Circuit
Pack
Enter the shelf number:

1 - Control Shelf
2 - Main Shelf
3 - EXT 1 Shelf
4 - EXT 2 Shelf
[ 1-4 ]
?
Query
Common
Equipment
Orderwire
0. Quit
1. QueRy General
parameters
2. EDit General parameters
3. QueRy connections
4. ADD connections
5. DELete connections
6. Enable Manual Seam
7. Disable Manual Seam
Ethernet
Wayside
0. Quit
1. SELect
3. ADD connections
4. DELete connectins

Figure 7-7
OTP3000p
Main
0. Quit
1. SELect
2. QueRy facility
3. EDit facility
4. Change facility Mode
5. Change State
6. facility Alarm provisioning
7. List all facilities
0. Quit
1. SELect
2. QueRy facility
3. EDit facility
4. Change State
6. timing output Alarm
provisioning
0. Quit
1. SELect
2. QueRy facility
3. EDit facility
4. Change State
6. timing output Alarm
provisioning
0. Quit
1. QueRy all Line dcc
2. QueRy all Section dcc
3. EDit Line dcc
4. Change Section dcc
5. Change State of Line dcc
6. Change State of Section
dcc
OCn
facility
FAcility
Timing
Input
Optical
FAcility
Timing
Output
Dcc
control
MOR
facility
0. Quit
1. optical SIGnal facility
2. OSC facility
3. PoWeR Measurement
4. MOR Dcc control
Tx
Optical
Facility
0. Quit
1. SELect
2. QueRy
3. EDit
Rx
Optical
Facility
0. Quit
1. SELect
2. QueRy
3. Determine current base
value
Payload
0. Quit
1. SELect
2. QueRy payload
3. EDit payload
ADministration
0. Quit
1. List Log Report summary
2. QueRy Log records
3. Date and Time
4. User Administration
5. Interface ports
LOGOUT
HELP

Figure 7-8
NE UI screen (example)
OTP2797p
C 000
M 000
m 000
w 000
LckOut 000
ActPt 000
00:47
Shelf: OTP-LH MAIN

Sh Slot Type
Equip ID
ExpPEC
PEC
Vintage Serial
SState
-----------------------------------------------------------------------------------2
1
OC-192 WT
WMR3HX0AAB NT**07** NTCA07YQ
05
01Y1BRWFA
NIL
2
2
OC-192 WT
WMR4C5NAAA NT**07** NTCA07UV
04
01B1BQ5XD
NIL
2
3
OC-192 XR/W WMR3BZ0AAA NT**04** NTCF04YR
01
01I1BRNA4
NIL
2
4
OC-192 XR
WMR4FA0AAE NT**04** NTCA04JP
09
01240260W
NIL
2
5 U
TD
SN98AAAAAA NTCA21** NTCA21AA
03
01W1BH9GG
NIL
2
5 L
TD
SN98AAAAAA NTCA21** NTCA21AA
03
01Q1BH9DP
NIL
2
6
OC-48 TR
WMT3A0FAAA NTCA30** NTCA30VK
01
01K1BDICZ
NIL
2
7
OC-48 TR
WMT3A0MAAA NTCA30** NTCA30XK
01
507X0IXX4
NIL
2
8
OC-192 TR
SN2TDY0BAA NT**06** NTCF06UP
02
0154023XH
NIL
2
9
OC-48 TR
WMT3A0FAAA NTCA30** NTCA30VK
01
01B1BAL1X
NIL
2
10
OC-48 TR
WMT3AF0AAA NTCA30** NTCA30FK
01
01X1BKW5M
NIL
External communications (DCC and OSC)

The following circuit packs provide external communications functionality on
the Repeater network element:
32M shelf controller (SC) circuit pack
128M MI circuit pack
optical circuit packs
Optical Long Haul 1600 external communications and remote layer
management (RLM) support both section/RS data communications channel
(DCC) and optical service channel (OSC).
DCC for the Wavelength Combiner application
Section/RS DCC and line/MS DCC are passed through unchanged on the
Wavelength Combiner tributaries A, B, and D. When the OC-192/STM-64
T/R (NTCA06xx) circuit pack is deployed in the Wavelength Combiner circuit
pack group, tributary C cannot use line/MS DCC. Section/RS DCC is passed
through unchanged. No limitations exist for tributary C if the Wavelength
Combiner circuit pack group contains a TriFEC-capable OC-192/STM-64 T/R
circuit pack. OC-48/STM-16 section/RS DCC and line/MS DCC are
processed transparently on the OC-192/STM-64 T/R and OC-192/STM-64
T/R (TriFEC) line/MS signal.
For more information on Wavelength Combiner transparency, refer to
DCC and OSC for Dense regenerator applications

The Dense regenerator application processes section/RS DCC. MOR Plus
amplifiers provide OSC for communication.
Wavelength Translator circuit packs offer an enhanced level of transparency
for the SONET/SDH bytes used for section/RS DCC communication and
therefore do not provide access to section/RS DCC.
Section/RS DCC access is not available with Wavelength Translator circuit
packs.
For more information on Wavelength Translator transparency, refer to
OAM&P for Dual Gigabit Ethernet circuit packs

This section describes the operations, administration, maintenance, and
provisioning (OAM&P) services available to manage the Dual GE circuit pack
in Optical Long Haul 1600 Repeater network elements.
Network element user interface enhancements
Two facilities exist on the Dual GE circuit packs. As a result, when defining a
facility, you must specify the G-name and the port number of the facility. For
details on G-names and port numbering on Dual GE circuit packs, see
Provisioning and Operations Procedures, 323-1801-310.
Provision the GE facilities from the new Gigabit Ethernet Facility menu in the
Facility menu (see Figure 7-9). For provisioning and operation procedures
using the Gigabit Ethernet Facility menu, refer to Provisioning and Operations
Procedures, 323-1801-310. You can also access the BCC CLI from the Gigabit
Ethernet Facility menu in the NE UI. For more information and procedures on
using the BCC CLI to query, configure and troubleshoot the Dual GE circuit
pack, refer to the Gigabit Ethernet Data User Guide (NTCA65YA).
Figure 7-9
Gigabit Ethernet Facility Menu
Gigabit Ethernet Facility Menu[ ]
-----------------------------0. Quit
1. SELect
2. QueRy facility
3. EDit facility
4. facility Alarm Provisioning
5. LIST all facilities
6. Bay Command Console
Since the Dual GE circuit pack terminates the path overhead of a concatenated
SONET/SDH payload, the circuit pack supports the collection of path
termination PM counts.
Note 1: The Dual GE circuit pack does not support far-end path PM
counts, physical PM counts, or protection PM counts.
Note 2: Path PM counts are monitored by the receiving Dual GE circuit
pack on the SONET/SDH side.
The Dual GE circuit pack supports the following path PM parameters:

SONET PMs: code violation (CV), errored second (ES), severely errored
second (SES), unavailable second (UAS), and failure count (FC)
SDH PMs: errored block (EB), background block error (BBE), errored
second (ES), severely errored second (SES), unavailable second (UAS),
severely errored period (SEP), background block error ratio (BBER),
errored second ratio (ESR), severely errored second ratio (SESR), severely
errored period intensity (SEPI), and unavailable time (UAT).
Note: The SES threshold for STS-24c/VC-4-8c payloads is 15000 CVs
(SONET PMs) or 30% EBs (SDH PMs).
For definitions of the path PM parameters and more information on
performance monitoring, refer to Performance Monitoring Procedures,
323-1801-520.
Failure signaling
The Dual GE circuit pack functions as a part of the transport network. As such,
failures on the 10G optical transport link will be propagated to the Dual GE
circuit pack and its link partner. The Dual GE circuit pack indicates link
failures to its remote link partners using the auto-negotiation remote fault bits
signaling.
In the event of a failure at the near-end of a Dual GE circuit pack link, the Dual
GE circuit pack at the near-end uses Layer 1 (SONET/SDH layer) signaling
for Layer 2 conditioning of the far-end Dual GE circuit pack. As a result,
unused SONET/SDH path overhead bytes are set and propagated across the
Wavelength Combiner link to indicate the link status (Link Fail) to the far-end
Dual GE circuit pack. Once the failure is repaired, the unused SONET/SDH
path overhead bytes are cleared to indicate the link recovery status to the
far-end Dual GE circuit pack. Figure 7-10 to Figure 7-22 illustrate several
failure handling scenarios.
ATTENTION
In the following scenarios, send link failure indication to GE client
equipment means that the Dual GE circuit pack restarts auto-negotiation
with Remote Fault bits set (if auto-negotiation is enabled) and then sends
continuous invalid codes (all ones). Send link offline indication to the GE
client equipment means that the Dual GE circuit pack restarts
auto-negotiation with the Remote Fault bits set to offline (if
auto-negotiation is enabled) and then sends continuous invalid codes.

Ethernet frame forwarding during failure conditions
The following rules apply to the forwarding of Ethernet frames during fault
conditions:
When a link failure is detected at the near-end Dual GE circuit pack (see
Scenario 1, Figure 7-10), Ethernet frames are not forwarded towards the
link partner in either direction.
Note: The far-end Dual GE circuit pack can continue to receive frames
from the far-end client if the far-end client does not support signaling of
link failures by use of the Remote Fault bits in the auto-negotiation
procedure or if auto-negotiation is disabled. When higher layer routing
protocols are established on the Ethernet network, traffic is immediately
transferred to another link.
When a WAN path failure is detected (failure on the 10G path between two
Wavelength Combiner circuit pack groups, see Scenario 2, Figure 7-12),
the Dual GE circuit pack receiving path AIS does not forward Ethernet
frames in either direction.
Note: The far-end Dual GE circuit pack can continue to receive frames
from the far-end client if the far-end client does not support signaling of
link failures by use of the Remote Fault bits in the auto-negotiation
procedure or if auto-negotiation is disabled. When higher layer routing
protocols are established on the Ethernet network, traffic is immediately
transferred to another link.
When a Link_Failure or Offline indication is signaled from a client using

the auto-negotiation Remote Fault bits, the Dual GE circuit pack continues
to forward Ethernet frames in both directions. It is the clients responsibility
to take the necessary action.

Figure 7-10
Scenario 1: Failure at the input of the Dual GE circuit pack (or client signals Link_Failure)
OTP3368p
NE UI and OPC:
'Ethernet link down'
alarm raised
SNMP: Dual GE A
sends 'LinkDown'
SNMP trap
NE UI and OPC:
'Ethernet link remote
fail' alarm raised
Dual GE A inserts
'Link fail' indicator in
STS-24c/VC-4-8c
path OH
Dual GE B detects
STS-24c/VC-4-8c
path OH
SNMP: Dual GE B
sends 'LinkDownRemote
Failure' SNMP trap due
to remote failure
GE
GE
Dual GE B
Dual GE A
2.5G T/R
2.5G T/R
10G
T/R
2.5G T/R
10G
T/R
2.5G T/R
2.5G T/R
2.5G T/R
COMBINER A
COMBINER B
Dual GE A sends link

failure indication to the
GE client equipment
Dual GE B sends link

GE client equipment
Note: This scenario does not cause Path PMs
Figure 7-11
Scenario 1: Recovery of the input to the Dual GE circuit pack
OTP3369p
NE UI and OPC:
fail' alarm clears
NE UI and OPC:
'Ethernet link down'
alarm clears
SNMP: Dual GE A
sends 'LinkUp'
SNMP trap
Dual GE A clears
STS-24c/VC-4-8c
path OH
Dual GE B detects
clearing of 'Link fail'
in STS-24c/VC-4-8c
path OH
SNMP: Dual GE B
sends 'LinkUp'
SNMP trap
GE
GE
Dual GE B
Dual GE A
2.5G T/R
2.5G T/R
10G
T/R
2.5G T/R
COMBINER A
Dual GE A clears the
link failure indication to
the GE client equipment
10G
T/R
2.5G T/R
2.5G T/R
2.5G T/R
COMBINER B
Dual GE B clears the

Figure 7-12
Scenario 2: Unidirectional 10G line signal failure
OTP3370p
NE UI and OPC:
'Drop Path RFI'
alarm raised
Path UAS PMs
Dual GE A detects
'Link Fail' indicator in
the STS-24c/VC-4-8c
path OH
SNMP: Dual GE A
Failure' SNMP trap
due to remote failure
Dual GE B inserts
the STS-24c/VC-4-8c
path OH
GE
2.5G T/R
10G
T/R
10G
T/R
2.5G T/R
2.5G T/R
2.5G T/R
2.5G T/R
COMBINER A
GE client equipment
SNMP: Dual GE B
sends 'LinkDown
SNMP trap
GE
Dual GE B
Dual GE A
2.5G T/R
NE UI and OPC:
'Drop Path AIS'
alarm raised
NE UI and OPC:
'Line RFI' alarm
raised on 10G T/R
COMBINER B
NE UI and OPC:
10G 'Signal Fail' alarm
(e.g. LOS, LOF)
raised on 10G T/R

GE client equipment
Note: Path UAS PMs increment but do not alarm by default.
Figure 7-13
Scenario 2: Signal recovery on the unidirectional 10G line
OTP3371p
NE UI and OPC:
'Drop Path RFI'
alarm clears
SNMP: Dual GE A
sends 'LinkUp'
SNMP trap
GE
Path UAS
PMs stop NE UI and OPC:
'Drop Path AIS'
Dual GE A detects
Dual GE B clears
alarm clears
clearing of 'Link Fail' 'Link Fail' indicator in
indicator in STS-24c/ STS-24c/VC-4-8c
SNMP: Dual GE B
VC-4-8c path OH
path OH
sends 'LinkUp'
SNMP trap
GE
Dual GE B
Dual GE A
2.5G T/R
2.5G T/R
10G
T/R
2.5G T/R
COMBINER A

NE UI and OPC:
'Line RFI' alarm
clears on 10G T/R
10G
T/R
2.5G T/R
2.5G T/R
2.5G T/R
COMBINER B
NE UI and OPC:
clears on 10G T/R


Figure 7-14
Scenario 3: Bidirectional 10G line signal failure
OTP3372p
NE UI and OPC:
'Drop Path AIS'
alarm raised
Dual GE A inserts
SNMP: Dual GE A
sends 'LinkDown'
STS-24c/VC-4-8c
SNMP trap
path OH
NE UI and OPC:
'Drop Path AIS'
alarm raised
Dual GE B inserts
SNMP: Dual GE B
sends 'LinkDown'
STS-24c/VC-4-8c
SNMP trap
path OH
Path UAS PMs
GE
GE
Dual GE B
Dual GE A
2.5G T/R
2.5G T/R
10G
T/R
X
X
10G
T/R
2.5G T/R
2.5G T/R
2.5G T/R
COMBINER A
GE client equipment
2.5G T/R
COMBINER B
NE UI and OPC:
(e.g. LOS, LOF)
raised on 10G T/R

GE client equipment
Figure 7-15
Scenario 3: Signal recovery on the bidirectional 10G line
OTP3373p
NE UI and OPC:
NE UI and OPC:
'Drop Path AIS'
'Drop Path AIS'
alarm clears
alarm clears
Dual GE B clears
Dual GE A clears
SNMP: Dual GE B
'Link Fail' indicator
SNMP: Dual GE A
sends 'LinkUp'
in STS-24c/VC-4-8c
in STS-24c/VC-4-8c
sends 'LinkUp'
SNMP trap
path OH
path OH
SNMP trap
Path UAS
PMs stop
GE
GE
Dual GE B
Dual GE A
2.5G T/R
2.5G T/R
10G
T/R
10G
T/R
2.5G T/R
2.5G T/R
2.5G T/R
COMBINER A
2.5G T/R
COMBINER B
NE UI and OPC:
clears on 10G T/R


Figure 7-16
Scenario 4: Failure or removal of the Dual GE circuit pack
OTP3374p
NE UI and OPC:
'Circuit pack missing'
or Circuit pack fail'
10G T/R inserts
alarm raised
'Path AIS' in both
against Dual GE A
STS-24c/VC-4-8c
corresponding to
SNMP: No response
Dual GE circuit pack
from node
NE UI and OPC:
'Drop Path AIS'
alarm raised
Dual GE B detects
the 'Path AIS' in the
STS-24c/VC-4-8c
and sends back
'Path RFI'
Path
UAS PMs
SNMP: Dual GE B
sends 'LinkDown
SNMP trap due to
remote failure
GE
GE
Dual GE B
Dual GE A
2.5G T/R
10G
T/R
2.5G T/R
2.5G T/R
10G
T/R
2.5G T/R
2.5G T/R
2.5G T/R
COMBINER B
Client detects loss
of Rx synchronization
and takes link down

client GE equipment
NE UI and OPC:
'Payload Fail' alarm
raised on 10G T/R
Figure 7-17
Scenario 4: Replacement or re-insertion of the Dual GE circuit pack
OTP3375p
10G T/R clears

'Path AIS' in both
STS-24c/VC-4-8c
corresponding to
SNMP: Dual GE A
sends 'Link Up'
SNMP trap
NE UI and OPC:
'Drop Path AIS'
alarm clears
SNMP: Dual GE B
sends 'Link Up'
SNMP trap
Dual GE B detects
the 'Path AIS' clearing
and clears 'Path RFI'
GE
GE
Dual GE B
Dual GE A
2.5G T/R
2.5G T/R
10G
T/R
2.5G T/R
COMBINER A
Client detects signal
recovery and takes
link up
10G
T/R
2.5G T/R
2.5G T/R
2.5G T/R
COMBINER B
NE UI and OPC:
'Payload Fail' clears
on 10G T/R


Figure 7-18
Scenario 5: Failure or removal of the 10G T/R circuit pack
OTP3376p
NE UI and OPC:
'Drop Path LOP'
alarm raised
NE UI and OPC:
'Drop Path AIS'
alarm raised
Dual GE B inserts
STS-24c/VC-4-8c
path OH
SNMP: Dual GE A
sends 'LinkDown'
SNMP trap
SNMP: Dual GE B
sends 'LinkDown'
SNMP trap
Path UAS PMs

GE
GE
Dual GE B
Dual GE A
2.5G T/R
2.5G T/R
2.5G T/R
10G
T/R
10G
T/R
2.5G T/R
2.5G T/R
2.5G T/R
COMBINER A
GE client equipment
COMBINER B
GE client equipment
NE UI and OPC:
NE UI and OPC:
'Circuit pack missing' 10G 'LOS' alarm
raised on 10G T/R
or 'Circuit pack fail'
alarm raised on
10G T/R
Figure 7-19
Scenario 5: Replacement or re-insertion of the 10G T/R circuit pack
OTP3377p
NE UI and OPC:
'Drop Path LOP'
alarm clears
Dual GE B clears
in STS-24c/VC-4-8c
path OH
SNMP: Dual GE A
sends 'LinkUp'
SNMP trap
NE UI and OPC:
'Drop Path AIS'
alarm clears
SNMP: Dual GE B
sends 'LinkUp'
SNMP trap
Path UAS
PMs stop
GE
GE
Dual GE B
Dual GE A
2.5G T/R
2.5G T/R
10G
T/R
2.5G T/R
COMBINER A
NE UI and OPC:
'Circuit pack missing'
or 'Circuit pack fail'
alarm clears on
10G T/R
10G
T/R
2.5G T/R
2.5G T/R
2.5G T/R
COMBINER B
NE UI and OPC:
10G 'LOS' alarm
clears on 10G T/R


Figure 7-20
Scenario 6: Failure or removal of timing distribution circuit pack in the Repeater network element
OTP3378p
NE UI and OPC:
'Drop Path RFI'
alarm raised
NE UI and OPC:
'Drop Path AIS'
alarm raised
Dual GE A detects
STS-24c/VC-4-8c
path OH
SNMP: Dual GE A
sends 'LinkDown
RemoteFailure '
SNMP trap due
to remote failure
GE
Dual GE B inserts
STS-24c/VC-4-8c
path OH
SNMP: Dual GE B
sends 'LinkDown'
SNMP trap
Path UAS PMs
GE
Dual GE B
Dual GE A
2.5G T/R
2.5G T/R
10G
T/R
10G
T/R
2.5G T/R
2.5G T/R
2.5G T/R
COMBINER B
COMBINER A
GE client equipment
2.5G T/R
NE UI and OPC:
NE UI and OPC:
'Line RFI' alarm
'Line AIS' alarm
raised on 10G T/R raised on 10G T/R

GE client equipment
NE UI and OPC:
TDC 'Circuit pack
missing' alarm raised
Figure 7-21
Scenario 6: Timing distribution circuit pack re-inserted in the Repeater network element
OTP3379p
NE UI and OPC:
'Drop Path RFI'
alarm clears
SNMP: Dual GE A
sends 'LinkUp'
SNMP trap
GE
NE UI and OPC:
'Drop Path AIS'
alarm clears
Dual GE A detects
Dual GE B clears
SNMP: Dual GE B
clearing of 'Link Fail'
sends 'LinkUp'
indicator in STS-24c/
in STS-24c/VC-4-8c
SNMP trap
VC-4-8c path OH
path OH
Path UAS
PMs stop
GE
Dual GE B
Dual GE A
2.5G T/R
2.5G T/R
10G
T/R
2.5G T/R
COMBINER A
NE UI and OPC:
'Line RFI' alarm
clears on 10G T/R
10G
T/R
2.5G T/R
2.5G T/R
2.5G T/R
COMBINER B
NE UI and OPC:
'Line AIS' alarm
clears on 10G T/R

NE UI and OPC:
TDC 'Circuit pack fail'
alarm clears

Figure 7-22
Scenario 7: Dual GE port taken DOWN at Combiner A (or client indicates Link Offline)
OTP3380p
NE UI and OPC:
offline' alarm raised
SNMP: Dual GE A
sends 'LinkDown'
SNMP trap
Dual GE A inserts
'Link offline' indicator
in STS-24c/VC-4-8c
path OH
Dual GE B detects
'Link offline' indicator
in STS-24c/VC-4-8c
path OH
SNMP: Dual GE B
Offline' SNMP trap
GE
GE
Dual GE B
Dual GE A
2.5G T/R
2.5G T/R
10G
T/R
2.5G T/R
COMBINER A
Dual GE sends
'Link offline'
indication to
the client
10G
T/R
2.5G T/R
2.5G T/R
2.5G T/R
COMBINER B
Dual GE sends
'Link offline'
indication to
the client
Note: This scenario does not cause Path PMs

Alarms
Table 7-7 lists equipment alarms, facility alarms, and facility alerts generated
by the Dual GE circuit packs on Optical Long Haul 1600. All alarms are
visible at the network element. For procedures to clear the Dual GE alarms on
the Optical Long Haul 1600 Repeater network element, refer to Trouble
Clearing and Module Replacement Procedures, 323-1801-543. You can
provision the alarming and the reporting of the Dual GE circuit pack group
equipment alarms and facility alarms on or off, refer to Provisioning and
Operations Procedures, 323-1801-310. Alarms are on by default. When the
primary state of the Dual GE circuit pack is out of service, equipment alarms
do not appear. When the Admin status of the Gigabit Ethernet port is down,
facility alarms do not appear.
Table 7-7
Alarms associated with the Dual GE circuit pack
Alarm
Alarm type
Severity
Reason
Circuit pack fail
Equipment
Critical, Service
Affecting
A damaged Dual GE circuit pack is in a

provisioned slot or a filler card is inserted in a
slot provisioned with a Dual GE circuit pack
Circuit pack
mismatch
Equipment
Critical, Service
Affecting
A circuit pack other than a Dual GE circuit pack

is inserted into a slot provisioned for a Dual GE
circuit pack
Circuit pack
missing
Equipment
Critical, Service
Affecting
The Dual GE circuit pack is removed from its

slot
Circuit pack
unlatched
Equipment
minor, non-service The latches of the Dual GE circuit pack are in a

affecting
released state
Circuit pack
vintage mismatch
Equipment
Critical, Service
Affecting
Intercard fail
Equipment
Major, non-service Any intercard fault

affecting
This alarm becomes active against the circuit
pack that has most likely failed
The vintage of the Dual GE circuit pack is

outside the range of the vintage baseline
This alarm lists the other circuit pack

associated with the failed link
Autoprovisioning
mismatch
Equipment
(common)
minor, non-service A Dual GE circuit pack is inserted into an

affecting
unsupported slot or a slot reserved for another
circuit pack
Drop signal label

mismatch
Facility
Major, Service
Affecting
The received signal label does not match the

expected signal type
Drop path
unequipped
Facility
Major, Service
Affecting
The path detects an unequipped signal
Drop path loss of

pointer
Facility
Major, Service
Affecting
The path detects a loss of pointer

Alarms associated with the Dual GE circuit pack
Alarm
Alarm type
Severity
Reason
Drop path AIS
Facility
Major, Service
Affecting
The path detects an AIS condition
Drop path RFI
Facility
minor, non-service The path detects an RFI condition (the far end
affecting
has a path failure condition)
Ethernet link down Facility
Major, Service
Affecting
Gigabit Ethernet port detects local ethernet link

down
Ethernet link
remote fail
Facility
Major, Service
Affecting
Gigabit Ethernet port is notified of a remote

ethernet link down
Ethernet line
remote offline
Facility
Major, Service
Affecting
Gigabit Ethernet port is notified of a remote

ethernet link is offline
PM day path
threshold
Facility
minor, non-service The day path threshold setting is crossed within

affecting
the day time period
PM 15min path
threshold
Facility
minor, non-service The 15 minute path threshold setting is crossed

affecting
within the 15 minute period
LEDs
The faceplate of the Dual GE circuit pack has the following LEDs:
two yellow LEDs (one for each Gigabit Ethernet port) to monitor the link
status. The yellow LED on the Dual GE circuit pack is lit if a failure occurs
anywhere on the Ethernet link between the local and the remote Dual GE
circuit packs. Ethernet link failures causing the yellow LED to be lit
include failures between the remote client and the local Dual GE circuit
pack, failures on the 10 Gbit/s optical line, and failures between the remote
client and the remote Dual GE circuit pack. The craftsperson is required to
locate the fault using the NE UI alarms or by querying the ports status in
the BCC CLI.
one green LED to indicate that the circuit pack is in service
one red LED to indicate a circuit pack failure
Optical link interoperability

MOR Plus amplifier
The baseline for MOR Plus Power Optimizer (PO) interoperability is OC-192
Release 7.0 or TN-64X Release 2.0. Interworking between MOR and
MOR Plus amplifiers is only supported at the physical layer.
ODPR and third-party routers
The main function of ODPR is to protect 10 Gbit/s unprotected router
interfaces. ODPR applications interoperate with SONET/SDH 10 Gbit/s client
signals from third-party routers. To interwork with Nortel equipment, client
signals must conform to the SONET or SDH standard since some vendors use
selected bytes for proprietary purposes. Concatenated OC-192c and STM-64c
signals can interoperate with the ODPR application.
Traffic protection for Wavelength Combiner applications
The Wavelength Combiner application does not support tributary or line traffic
protection. However, because the Wavelength Combiner acts as an open and
transparent gateway onto the optical line/MS, it transparently carries the
incoming signals across the network and flags failure conditions encountered
during propagation. This functionality allows the 2.5 Gbit/s subtending nodes
to handle traffic protection. If a failure occurs on the 10 Gbit/s line/MS, traffic
is diverted as if the failure had occurred on the four 2.5 Gbit/s lines. For traffic
protection switching to work correctly at the tributary level, each 10 Gbit/s
wavelength must be duplicated and propagated along a different optical path.
Figure 7-23 shows Wavelength Combiner point-to-point systems connected to
a subtending 2.5 Gbit/s system.

Figure 7-23
Traffic protection at the 2.5 Gbit/s nodes
OTP0163
Failure on
10 Gbit/s line
Working
Wavelength
Combiner
Wavelength
Combiner
2.5 Gbit/s
2.5 Gbit/s
Wavelength
Combiner
Wavelength
Combiner
Protection
Legend:
: Normal path
: Failure path
Wavelength Combiner Dual GE services interoperability with third-party

routers
The Wavelength Combiner equipped with Dual GE circuit packs can interwork
with any product that is compliant to the IEEE 802.3 (1998) with
1000Base-LX, 1000Base-SX interfaces, or 1000Base-ZX (1550 nm)
single-mode optical fiber (70 km reach) interfaces.
CAUTION
Auto-negotiation interoperability with switches and routers
Auto-negotiation on the Dual GE circuit pack port and the

switch/router port to which it is connected must be configured
to be both enabled or both disabled. If the ports do not come up
on both Dual GE and the switch/router, or link operation is
unreliable, it is recommended that both are configured to be
auto-negotiation disabled. Contact Nortel for information on
specific switches and routers that are known to be compatible
or incompatible with the Dual GE circuit pack
auto-negotiation.

Synchronization status messaging (SSM) allows network elements to
reconfigure their synchronization references to avoid timing loops. SSM
contains clock-quality information and provides automatic switching to the
most appropriate timing reference based on reference quality and priority.
SSM provides timing intelligence and reliability to network timing
synchronization.
Only the Wavelength Combiner application requires timing. All other
applications supported by the Repeater network element (for example,
Wavelength Translator, Dense regenerator, and ODPR) perform
through-timing. A Repeater network element with at least one Wavelength
Combiner circuit pack group requires synchronization. Synchronization is
performed by two external synchronization interface (ESI) and two half-height
timing distribution (TD) circuit packs.
SSM ensures that the best timing source is selected by using the quality code
(QC) and priority code. Bits 5 to 8 of the S1 byte are used to communicate the
quality code and priority code to other network elements. The network
elements then determine which source (BITS or line optics) becomes the
active timing source (see Table 7-8 on page 7-40).
The SSM feature can do the following:
receive, process, and respond to SSM in OC-192/STM-64 signals or from
an external extended superframe format DS1 building-integrated timing
supply (BITS) source
generate and transmit timing clock quality through OC-192/STM-64
signals
switch to the most appropriate timing reference from up to five timing
reference sources when the active reference fails or the network element
synchronization status changes
allow a user-initiated switch to a timing reference from up to a maximum
of five reference sources
set the transmitted quality level of DS1 output signals to that of the
OC-192/STM-64 source that drives it and send an alarm indication signal
(AIS) to that output if the quality level drops to or is below a provisionable
threshold
provide default provisioning and user provisioning of SSM attributes
Note: Although SSM decreases the chances of timing loops, it is
recommended not to use mixed provisioning in a ring system if one
network element is externally timed. Mixed provisioning refers to a mix of
external (ESI) and internal (OC-n/STM-n) timing sources. For more
information on SSM, refer to Synchronization status messaging (SSM)
on page 8-33.

Table 7-8
SSM quality descriptions
SONET quality
SDH quality
Quality
value
S1 byte
Quality
(bits 5 to 8) level
(see Note)
Stratum 1
ST1
0001
Stratum Unknown
STU
0000
Traceable to primary clock
PRC
0010
Traceable to transit clock
SSUT
0100
Stratum 2
ST2
0111
Traceable to a local SSU
SSUL
1000
Stratum 3
ST3
1010
10
Traceable to an SDH
equipment clock
SEC
1011
11
SONET minimum clock

(+20 ppm)
SMC
1100
12
Reserved for network

synchronization
Reserved for network

synchronization
RES
1110
user defined
Do not use for synchronization Do not use for synchronization DUS
1111
15
Note: The quality level defines the priority assigned to each quality value. The quality levels not listed
in this table are not currently used.
Note: For information on changing the SSM quality code value for an ESI
input or output facility, refer to Provisioning and Operations Procedures,
323-1801-310.
Timing generation
The timing generation references for a Repeater network element equipped
with at least one Wavelength Combiner circuit pack group is N:1 protected (N
sources for one selection), where N is less than or equal to 5. The best timing
reference is automatically or manually selected from a pool of up to five
sources.
The five available sources for timing generation references in a network
element are as follows:
BITSA
BITSB
OC-192/STM-64 T/R G7
OC-192/STM-64 T/R G12

OC-192/STM-64 T/R G17
BITSA and BITSB provide external timing for the network element. The
OC-192/STM-64 T/R circuit pack references provide line timing functionality
through G7, G12, and G17. Optical Long Haul 1600 does not support
OC-48/STM-16 T/R tributary timing.
Note: For descriptions of external timing, line timing, and through timing,
refer to Synchronization on page 4-29.
ATTENTION
You cannot use OC-192/STM-64 T/R circuit packs in extension shelf 2
(G22 and G27) to line time your network element.
Timing distribution
Timing distribution synchronizes 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 get a timing
distribution reference output. Optical Long Haul 1600 does not support SSM
on timing distribution outputs over 2 MHz format.
The facilities on which the clock quality can be transmitted are as follows:
G1OUT
G2OUT
OC-192/STM-64 T/Rs (G7, G12, G17)
OC-48/STM-16 tributaries
ATTENTION
SSM requires an extended superframe DS1 input. SSM cannot be carried by
a 2 MHz or superframe format DS1 signal. Instead, a quality code (QC) of
STU is sent.
ESI modes of operation
The modes of operation for an ESI circuit pack are as follows:
freerun
holdover
acquire (not user-provisionable)
fast-acquire (not user-provisionable)
normal

Freerun mode
In freerun mode, the ESI provides a Stratum 3 free-running clock timing signal
(at an accuracy of +4.6 ppm). Because the clock on the shelf is a Stratum 3.5
clock, with an accuracy of 20 ppm, the ESI clock improves performance even
in freerun mode. This setting indicates that the network element provides the
timing reference to other network elements.
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
(for 24 hours) based on the last known frequency reference. After the 24-hour
period, the reference returns to Stratum 3 quality (if the reference quality was
better than Stratum 3). If the reference was Stratum 3, the quality remains
Stratum 3.
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. The reference signal can be a BITS source or a OC-192/STM-64 signal.
Frequency alignment is checked continuously and the ESI enters fast mode to
realign (if necessary).
Target filter mode provisioning

Table 7-9 lists information on the timings modes of operation.
Table 7-9
Timing modes of operation
Shelf clock ESI target
source
filter mode
(see Note 1)
Timing reference
Timing mode Accuracy

(see Note 2)
Application
ESI
BITSA or BITSB
External
timing
As precise as
the local BITS
Wavelength
Combiner
OC-192/STM-64 T/R G7
Line timing
As precise as
the received
signal
All timing references are

failed
Holdover
+0.37 ppm
relative to the
last reference
for first 24 hrs.,
drifting no
worse than
+4.6 ppm
(stratum-3)
after the 24
hour period
Holdover
Internal ESI oscillator
Holdover
+0.37 ppm
relative to the
last reference
for first 24 hrs
(stratum-3
holdover
stability)
Freerun
Internal ESI oscillator
Freerun
+4.6 ppm
(stratum-3
accuracy)
Normal
OC-192/STM-64 T/R G12

OC-192/STM-64 T/R G17
(see Note 3)

Timing modes of operation
Shelf clock ESI target
source
filter mode
(see Note 1)
Timing reference
Timing mode Accuracy

(see Note 2)
Application
Through
timed
Received signal to be
regenerated
Through timed As precise as

the received
signal
Dense
regenerator
Not
applicable
(no ESI
required)
Wavelength
Translator
ODPR
Note 1: For detailed instructions on changing the target filter mode, refer to Provisioning and
Operations Procedures, 323-1801-310.
Note 2: For descriptions of the timing modes, refer to Network element synchronization modes on
page 4-29.
Note 3: You cannot use OC-192/STM-64 T/R circuit packs in extension shelf 2 (G22 and G27) to line
time your network element.
Synchronization status messaging provisioning

From the NE UI, you can provision the following parameters for SSM:
Rx SSM quality code (QC) override

Rx SSM global mode
Tx SSM QC override
Tx SSM global mode
TG threshold
TD threshold
RES
Rx SSM QC override
The Rx SSM QC override applies to an optical facility or to a BITS facility.

You can provision the Rx SSM QC override to the value of any SSM QC value
(refer to Table 7-8) or AUTO. If you set the Rx SSM QC override to a value
different from AUTO, then the provisioned QC value replaces the incoming
SSM QC value. The incoming value is ignored by reference protection, which
uses the Rx SSM QC override when selecting a timing reference. If you change
the Rx SSM QC override, the timing references are re-evaluated and a new
reference may be selected.
Note: The AUTO setting implies that no override is active.
For a BITS facility, only SONET values are supported. The 2 MHz ESI circuit
pack (NTCE44BA and NTCE44CA) does not process SSM information from
SDH BITS signals. Setting an SDH value for a BITS override causes the BITS
to be ignored by reference protection.
An invalid incoming QC raises an alarm, even if an override is active.

However, reference protection can still use the source.
Rx SSM QC override can be used to control the selection of the timing
reference. For example, if you set the received QC to a high value, other
sources with lower QCs are not selected as a reference. If you set the Rx
override to a higher priority than the incoming QC, a Tx AIS alarm is raised.
The Tx AIS alarm is not raised if the override is set equal to the incoming
QC.
Note: For instructions on changing the Rx SSM QC override value, refer
to the procedure on changing the SSM quality code for an ESI input facility
in Provisioning and Operations Procedures, 323-1801-310.
Rx SSM global mode
Rx SSM global mode applies to optical facilities only. Starting with Release 6,
only OC-192/STM-64 facilities use this parameter. Rx SSM global mode
controls the acceptance of incoming SDH or SONET codes for a facility.
When you enable Rx SSM global mode, the network element does not
discriminate between the SDH and SONET timing quality codes: the facility
accepts both SONET and SDH QCs. The Invalid sync status message
alarms, for SDH/SONET codes on a facility whose facility mode is the
opposite (SONET/SDH), are masked. Also, the provisioned RES value is
accepted and used for an SDH system.
When you disable Rx SSM global mode, the facility mode (SDH or SONET)
of the facility determines if the QC must be a SONET or an SDH code: the
facility only accepts codes corresponding to the facility type. For example, a
SONET facility only accepts SONET codes and an SDH facility only accepts
SDH codes.
By default, the Rx SSM global mode is disabled.
Tx SSM QC override
Tx SSM QC override applies to an optical facility or to a DS1 output facility

in ESF format. You can provision the Tx SSM QC override to the value of any
SSM QC (refer to Table 7-8) or AUTO. If you set the Tx SSM QC override to
a value different from AUTO, then the provisioned QC value replaces the
outgoing SSM QC.
Note: The AUTO setting implies that no override is active.
On a network element that uses the 2 MHz ESI circuit pack (NTCE44BA or
NTCE44CA), the outgoing 2 MHz signal does not carry any SSM QCs.
Tx SSM QC override can be used to control reference selection behavior on

other connected network elements by overriding the outgoing QC on each
facility that causes connected network elements to re-evaluate the best timing
reference.
Note: For instructions on changing the Tx SSM QC override value, refer
to the procedure on changing the SSM quality code for an ESI output
facility in Provisioning and Operations Procedures, 323-1801-310.
Tx SSM global mode
Tx SSM global mode applies to optical facilities only. Tx SSM global mode
controls the transmission of SDH or SONET codes on a facility in the outgoing
direction.
If you enable Tx SSM global mode on the Tx facility, the SSM code of the
active timing reference source (with any appropriate overrides) is sent out on
the Tx facility, even if this code does not match the SONET/SDH mode of the
Tx facility.
If you disable Tx SSM global mode, the facility mode of the Tx facility
determines if the outgoing QC is a SONET or an SDH code. For a SONET
facility, the nearest SONET version of the timing source QC is sent (identical
if the timing source was in SONET mode). The same process occurs for SDH.
In other words, the SSM code of the active source is translated, if necessary, to
match the SDH/SONET mode of the transmit facility. For example, STU
would be translated to SSUT if the transmit facility is an SDH facility.
Note: Only tributary facilities can have a different facility mode from that
of the network element. That is, for a SONET network element, the
high-speed lines will always have facility mode SONET.
By default, the Tx SSM global mode is disabled.
TG threshold
The timing generation (TG) group threshold determines the point below which
a timing reference in the TG group is considered failed. The incoming QC on
the timing reference (or override, if one exists) is compared to the TG
threshold. If the TG threshold is set to a priority greater than or equal to the
incoming timing reference a Tx AIS alarm is raised. If the QC is less than or
equal to the TG threshold, then the reference has failed and is not used as an
active timing source for the network element.
TD threshold
The timing distribution (TD) group threshold determines when a timing

reference in the TD group has failed to provide a source to the outgoing timing
signal. The incoming QC on the timing reference (or override, if one exists) is
compared to the TD threshold. If the QC is less than or equal to the TD
threshold, then the reference fails and is not used as an active timing source for
the outgoing signal. If the reference is the only one available, the outgoing
timing signal transmits an alarm indication signal (AIS). If the TD threshold is
set to a priority greater than or equal to the incoming timing reference, a Tx
AIS alarm is raised.
RES
The RES parameter applies to the entire network element. RES indicates a
replacement value to use if an incoming QC is set to RES. This value is user
provisionable. RES is a code defined for interoperability with vendors using
standard or non-standard timing.
To query or edit the RES value, refer to the procedure on querying or changing
the network element timing provisioning in Provisioning and Operations
RES for SONET
If RES is received as a QC on a traffic or DS1 input, then the provisioned RES

value replaces the RES code for reference selection for that timing source.
RES is then sent out on outgoing traffic if the source becomes the active timing
source.
RES for SDH
If RES is received as a QC on a traffic or DS1 input, then the reference

protection considers it as DUS. However, the RES value is never sent out
because it is never the active timing source. If the Rx SSM global mode of the
input facility is enabled, the RES code is considered identical to that on a
SONET system, where the RES source can be used as a reference and RES is
then sent out as the outgoing QC.
Alarms and events for synchronization status messaging

Table 7-10 describes alarms and events specific to SSM.
Table 7-10
Alarms and events for SSM
Description
Type
Severity
Applies to Service
code
Details
Invalid sync
Alarm
status message
Minor
FAC
non-service A synchronization message was

affecting
received with an undefined value in
the provisioned message set.
(nsa)
Unstable sync Alarm

status message
Minor
FAC
nsa
The value of the received

synchronization status message was
not constant during the validation
period (10 seconds).
Loss of sync
Alarm
status message
Minor
BITS FAC
nsa
No synchronization message was

received at a BITS DS1 input for a
period greater than 10 seconds.
Sync status
message
changed
LOG
Minor
FAC401
FAC
nsa
A change occurred in the value of the

incoming synchronization status
message.
Protection
activity
LOG
Minor
ALT402
FAC
nsa
Indicates a successful protection

switch (reasons: quality change, loss
of SSM, and unstable SSM).
For more information on clearing alarms, refer to Trouble Clearing and

Module Replacement, 323-1801-543.
20-character network element name

The network element name is a 20-character alpha-numeric string. The
extended network element name is displayed on all the NE UIs that display
13-character network element names, and on the OPC UI.
If a system that supports a 13-character network element name and a system
that supports a 20-character network element name co-exist and carry traffic
in the same managed network, you cannot perform a remote login using the
network element name with a length greater than 13 characters. In this case,
NE ID is used and remote login is possible for a system that supports a
20-character network element name to a system that supports a 13-character
network element name.
64K NE ID
Optical Long Haul 1600 supports extended network element ID numbers up to
65534 characters.
Routing fundamentals
For Level 2 routing commissioning procedures, refer to Provisioning and
Operations Procedures, 323-1801-310.
For details on data communications, refer to the Data Communications
Network Planning Guide (NTR710AM).
Level 2 routing increases the size of the network beyond the current 150 node
Level 1 limitation, and simplifies network maintenance and monitoring.
Level 2 routing creates a bridge between existing Level 1 network areas (see
Figure 7-24). The division of Level 1 areas is completed by assigning manual
area addresses (MAA) to each network element that is part of the network.
Each Level 2 router builds a set of network element addresses of the Level 1
area in which it exists. The Level 2 routers exchange these sets of addresses to
build a map of Level 1 areas that each Level 2 router supports. With this map,
each Level 2 router determines how to route messages destined for other
Level 1 areas.
All addressable network elements in a network must be identified by a unique
network service access point (NSAP). A protocol data unit (PDU) is a packet
that is used by a source network element to send data to a destination network
element: a source and destination NSAP information and service data unit
(SDU) that carries the actual data in the message.
All network elements operating within the same routing parameter form a
domain. A domain can be further divided into sub-domains or areas, also
known as Level 1 areas. The protocol used for routing PDUs within an area is
known as Level 1 routing (intra-area). Network elements within an area take
on one of the following roles:
an end system (ES) is a node that can originate and terminate PDUs but
does not route PDUs within an area. An example of an ES is an OPC.
a Level 1 intermediate system (Level 1 IS) performs the same role as an
ES. Level 1 IS is also responsible for routing and relaying PDUs from one
network element to another within the Level 1 area. A Level 1 IS maintains
a detailed topological view of routes to every connected network element
within its Level 1 area. Examples of Level 1 IS are network elements and
the network processor (NP).
a Level 2 intermediate system (Level 2 IS) performs all the functions of a
Level 1 IS. A Level 2 IS is also responsible for routing PDUs from one
Level 1 area to another Level 1 area within the domain.
Figure 7-24
Data communication fundamentals
OTP0137
Level 2
Area A
Level 1
Area B
Level 1
Domain X
Level 1 routing
A Level 1 routing area is created or defined by a unique set of area addresses.
Because of standards history, the maximum number of unique area addresses
that can be supported for interoperability purposes in a Level 1 area is three.
For routing messages between nodes, routing adjacency must be established
between the nodes. A SONET DCC example is used to explain routing
adjacency on network elements. The concepts are similar for LAN-based
connections (Control NET [CNET] and Ethernet).
A link is established over the channel. The frame size used at each end of the
link must be identical. Nothing in the protocol specification verifies that the
frame size at each end is the same. You must ensure that the frame sizes at each
end are equal. In a SONET example, the point-to-point connection uses the
Link Access Protocol for D-channels (LAPD) over the section/RS data
communications channel (DCC). This arrangement establishes whether the
network elements can communicate with each other. After communication is
established, the network elements must determine their routing compatibility
(their ability to route messages to or from the other network element). At this
time, routing adjacency status is determined.
After the LAPD connection is established, the network elements exchange
routing information. This routing information contains the following network
element details:
NSAP address
the number of area addresses the network element supports
a list of the area addresses that this network element supports (maximum
of three)
The network elements compare lists of supported area addresses. One area
address must be common on the two network elements. If at least one area
address is in common, a routing adjacency is established and messages can be
routed between the two network elements. If the two network elements do not
have at least one area address in common, then the network elements view the
link as unusable for the purpose of routing messages between one another.
When a routing adjacency is established, the network elements exchange
additional information. This additional information includes details as to
which adjacent network elements are accessible through which port. All
network elements within the Level 1 network exchange their information with
another network element in the network. It is this information that allows each
network element to build the same view of the network and the network
connectivity. This information is then used by the network elements that
function as Level 1 routers to route messages throughout the Level 1 network.
When two Level 1 areas are joined into a single Level 1 area, only the network
elements from the two areas that are physically connected require a common
area address. The key factors required to join two separate Level 1 areas into
one Level 1 area are as follows:
The frame size on the connecting link must be identical.
The number of supported area addresses at each network element must be
the same.
The connected network elements must have at least one supported area
address in common.
In some cases, network elements from different vendors must interwork in a
network and route each others messages. It is likely that two different
vendors equipment have different default area addresses. The ability to
support more than one area address is beneficial because this scenario allows
the provisioning of one vendors area address on the other vendors network
element to which it is connected; this ensures that one area address is in
common.
The manual area address (MAA) set on any given network element is the area
addresses the network element has provisioned on it. The network element
uses this NSAP as the source address of all messages it originates. To establish
routing adjacency, network elements exchange information about which area
addresses they each support. This information is passed from network element
to network element around the entire Level 1 area. All network elements in the
entire Level 1 area have information about all area addresses provisioned
within the Level 1 area. The union of all these manual area address sets then
becomes the computed area address (CAA) set. The CAA set is found on each
network element within the Level 1 area. No more than three MAAs can be
provisioned in a Level 1 area.
Since all nodes can support a maximum of three area addresses in their
computed area address set, the remaining area addresses are dropped, which
can have a negative impact on the network. The nodes decide which area
addresses to keep and which to drop according to the following rule, from
ISO 10589: Compare all area addresses digit by digit starting from the left.
When a lower digit is found, that area address is deemed to be the lower
address. After all area addresses in the computed area address set are
compared, only the three lowest remain.

Example of ISO 10589 rule
Assume the following five manual area addresses are provisioned on nodes
within a Level 1 area:
123456
23456789
34567890
4
5
As stated by the ISO 10589 rule, area addresses 123456, 23456789, and
34567890 are kept, and 4 and 5 are dropped. No leading zeroes are added to
pad the addresses. All addresses are left justified. In this example, the
comparison ends after the first digits are compared.
Because area addresses 4 and 5 are dropped, any nodes that use either of these
area addresses in their NSAP addresses have a problem. For example, assume
node X has area address 5 in its manual area address set and uses this area
address in its NSAP. When X originates a message, it places its NSAP as the
source address of the message. The destination node, for example Y, receives
the message (assuming Y was not using either 4 or 5 as part of its NSAP
address).
If Y responds to the message, it uses the source address NSAP from the
message it has now received from X as the destination NSAP for its response.
Since Y dropped area address 5 from its computed area address set, Y cannot
route the message within this Level 1 area to the correct destination node, X.
If Level 1 routing is supported in this network, Y discards the message and
node X does not get a response to its message.
Level 2 routing
Level 2 routing is used to interconnect previously created Level 1 areas.
Level 2 routers follow the Level 1 algorithms as described in the previous
section. Level 2 routers are network elements within a Level 1 area. Level 2
routers can also route messages to nodes that are not within their own Level 1
area. To achieve this arrangement, a Level 2 router must have at least one of
its communications ports directly connected to that of another Level 2 router.
To maintain connectivity in a domain comprised of numerous Level 1 areas,
all Level 2 routers must be connected. This connection forms the Level 2
routing backbone.
When connected and provisioned as Level 2 routers, the Level 2 routers
exchange information with other Level 2 routers. The information exchanged
is the set of area addresses each supported in its Level 1 area (computed as a
set of area addresses). Each Level 2 router can then build a map of which
Level 2 routers support which Level 1 area addresses. In addition, each
Level 2 router can determine the link over which it must send a message
destined for another Level 1 area to allow the message to reach its destination
(see Figure 7-25).
Figure 7-25
Level 2 routing across Level 1 areas
OTP0138
Preside
L21S
Area Y
The 3 areas are
connected with L21S.
L21S
L21S
Area X
Area Z
Note 1: Only one routing domain exists.

This routing domain is comprised of 3
unique areas identified with unique
area addresses (X, Y, Z).
Note 3: Peer-to-peer communication between

network elements of different areas is now possible.
Note 4: Redundant communication path from Preside
to the network elements upon broken links.
Note 2: Each one of the areas is

connected to Level 2 routers.

Level 2 connectivity
Some common misconceptions exist regarding connectivity among Level 2

routing. Most assume boundary network elements can be configured as Level
2 routers and Level 2 routing occurs. This scenario holds true in a simple case
where only two areas are involved. The situation becomes more complex when
more than two areas are involved.
A Level 1 router can only operate in the Level 1 area.
A Level 1 router cannot operate in the Level 2 sub-domain.
A Level 2 router can operate in both Level 1 and Level 2 sub-domains,
bridging both levels.
A Level 2 router can also act as a Level 1 router. It can route packets within
its area and can also route packets between different areas in the Level 2
sub-domain.
When a packet is routed through the Level 2 sub-domain, the Level 2
router cannot use Level 1 links or paths to forward the packet.
A packet routed through the Level 2 sub-domain must use Level 2 paths
formed by Level 2 links. Level 1 and Level 2 paths operate separately.
Level 2 with linear systems
An Optical Long Haul 1600 system can support a number of on-ramp and
off-ramp tributaries, where a cluster of network elements operate from each
tributary. Each of these tributary clusters will form a tributary network. In this
case, the total number of network elements in the entire tributary network can
exceed the Level 1 routing limit. If this situation occurs, part or all of the
tributary networks must be partitioned into smaller Level 1 areas. Each
tributary network is configured as an individual area. In each area, the network
element connection to the Optical Long Haul 1600 linear backbone is
configured as a Level 2 router for the area itself. This network element can
then tap into the Optical Long Haul 1600 backbone using the tributary circuit
(see Figure 7-26).

Figure 7-26
Level 2 with linear systems
OTP0139
Subtending
Subtending
L2
L2
The OPTera Long Haul 1600

level 2 routers are connected
to each other using DCC or
OSC to form the backbone
for the level 2 path.
Tributary
Tributary
L2
L2
OSC
or
DCC
L2
L2
Legend
- Level 2 path
- Level 2 router
Note 1: Each tributary network is configured as

an individual area. In each tributary area, the network
element connection to the OPTera Long Haul 1600
backbone is configured as a level 2 router for the area itself.
This network element can then tap into the OPTera Long Haul
1600 backbone using the tributary circuit.
Note 2: OPTera Long Haul 1600 can support a
number of tributaries where a cluster of network elements can
hang off each tributary.
Note 3: Each of these tributary clusters is a

tributary network.
Note 4: The total number of network elements
in the entire tributary network can exceed a level 1
routing limit in this scenario. Therefore, part or all of
the tributary networks must be partitioned into
smaller level 1 areas.
Amplifier site or Dense regenerator site as a Level 2 hub
A Repeater network element configured as a line amplifier site (using MOR

Plus amplifiers) is the ideal choice for a Level 2 router because the MOR Plus
amplifier functions as an optical hub where multiple spans of network
elements meet at a single point. Each node in the different areas can
communicate with one another, as well as the common regenerator or line
amplifier, through the Level 2 routers (see Figure 7-27).

Figure 7-27
Amplifier site or dense regenerator as a Level 2 Hub
OTP0140
Network
element
L2
Area 2
L2
Area 5
MOR
Area 3
Area 4
L2
L2
L2
L2
Area 6
Area 7
Network
element
Area 1
Legend
- Level 2 path
- Level 2 router
Note 1: MOR network element is the natural choice for a

level 2 router, since the MOR circuit packs act as an optical
hub where multiple spans of network elements meet at a single point.
Note 2: Nodes in the different areas can communicate with one
another and the common regenerator/optical line amplifier through
the level 2 routers.
Centralized manual area address provisioning

For more information on Level 2 routing, Level 1 areas, and manual area
addresses, refer to the Data Communications Network Planning Guide
(NTR710AM).
You can provision manual area addresses on network elements in an OPC span
of control from a centralized location. The centralized OPC manual address
tool is included in the OPC Commissioning Manager tool.
Manual area addresses

In Optical Long Haul 1600, the OPC Commissioning Manager tool adds or
deletes the manual area address for the primary OPC, the backup OPC, and all
the network elements in the OPC span of control (SOC). The OPC
Commissioning Manager tool then prompts the user to datasync the
information at the end of each operation performed. Each task can be
performed centrally from one provisioning dialog box to reduce the number of
steps, and minimize potential errors when entering a manual area address.
The Area Addresses display dialog box contains three lists (see Figure 7-28):
Provisioned MAA list
Manual Area Addresses list
Computed Area Addresses list
Figure 7-28
Area address display dialog box
OTP1373p
Area Addresses (SOC)

_____________________________________________________________________
WARNING: A maximum of three Manual Area Addresses can be provisioned.
* denotes the current communicating address.
OPC/NE Provisioned MAA set

MAA1
MAA2
MAA3
_______________________________________________
OPC OPC7677P
A
B*
8576 Ottawa
A*
B
8577 Toronto
?
Manual Area Addressess

MAA#
_________________________________
39840+80000000000000000000
A
49+0000
B
[ Done
Return ]
Computed Area Addressess

___________________________
39840+80000000000000000000
49+0000
[ Add Manual Area Address
+ ]

Provisioned MAA list
Use the Provisioned MAA list to display the primary OPC and all the network
elements in the OPC SOC with their unique manual area address sets. The
second, third, and fourth columns of the list display these sets of addresses
with the index of each manual area address. The index character (A and B in
Figure 7-28) saves screen space and also makes the comparison easier. In
previous releases, only a few characters differentiated the addresses. The star
next to the index represents the address used by the network element and OPC
(the default manual area address used for the NSAP) to communicate with the
rest of the SOC.
Manual Area Addresses list
Use the Manual Area Addresses list to display the hexadecimal value of each
of the manual area addresses that are provisioned on the OPC and on each
network element in the SOC. To the right of each manual area address is the
unique index character assigned to the provisioned manual area address.
Computed Area Addresses list
Use the Computed Area Addresses list to display the hexadecimal value of
each computed area address used in the network for the Level 1 area where the
SOC resides.
Adding a manual area address
Select the Add Manual Area Address button to display the area address
provisioning dialog box (see Figure 7-29).

Figure 7-29
Adding a manual area address
OTP1374p
Area Address Provisioning (SOC)

_____________________________________________________________________
Entering an incorrect area address could cause a loss of OAM for
this system. Check the detailed procedures in the NTPs prior to
adding a manual area address.
AFI: > 39 IDI 840
Select
______
39
39
49
Organization abcdef
Routing_Domain 1234
Area
:
Select
:
______
:
840
124
Manual Area Address: > 39840+
[ OK
Return ]
1 39840+80000000000000000000
2 39124+80000000000000000000
3 39840+80123456000012344321
4 49+0000
5 [Clear
Field Area Address
Add Manual
Del ]
After this dialog box is displayed, you can select a default manual area address
from the Manual Area Address field chooser, or enter the manual area address
in the separate fields. The chooser contains the most common manual area
address defaults (for example, 39840+00000000000000000000) with the last
five previously provisioned values.
When the first address is provisioned, the dialog box remembers the last
Authority and Format Identifier (AFI) used and pre-fills the AFI the next time
the dialog box is opened. This arrangement allows you to select a previously
used address quickly, and then provision a new one by editing only a few
characters. When you select OK and the confirmation dialog box is accepted,
the OPC sends a message to each network element to add the new entered
address. A new manual area address is added to the whole SOC with one
provisioning operation.
In summary, Level 2 routing enables the data communication network to
develop beyond the current network size limit. This new functionality allows
the communication to any network element and OPC within networks. It is no
longer necessary to segment the data communication domain to respect the
conventional 150 nodes Level 1 area limit by selectively turning on or off
physical DATACOMM ports. Instead, the entire network can be split into
Level 1 routing areas with simple manual area address provisioning at each
network element. A small number of network elements at the boundary area

can be provisioned as Level 2 routers and used to interconnect the previously
created Level 1 areas. The addition of one or more large network segments to
the existing DATACOMM network can be accomplished easily by creating
one or more new areas without requiring re-provisioning of any existing
DATACOMM ports.
Partition repair
Before Release 6, a Level 2 router was unable to detect if one of its adjacent
Level 1 areas was partitioned. In such a case, the router sends a message
through one path and if the network element to which the message is destined
is not reachable, the message is dropped. Partition repair, introduced in
Release 6, allows the Level 2 routers to encapsulate the message and re-route
it to the destined network element through a valid route.
To understand partition repair, consider a network scenario where partition
repair is useful. Figure 7-30 on page 7-62 shows that the link between network
element 1 and network element 2 is broken, which causes area X to be
partitioned into two isolated areas with the same area address.
Without partition repair, if the Level 2 network element 152 has a message
destined for network element 1, then network element 152 first sends the
message to either network element 3 or network element 4. Network element
152 does not detect that network element 3 cannot reach network element 1
and network element 4. Similarly, network element 4 cannot reach network
element 2 and network element 3. Network element 152 only detects that to
reach the area address specified, network element 152 can route to either
Level 2 routers network element 3 or network element 4. If network element
152 sends the message to network element 3, then the message is discarded
because network element 1 cannot be reached.
When partition repair is supported by network element 3 and network
element 4, network element 3 and network element 4 can detect the
partitioning of area X. If network element 152 sends the message to network
element 3 destined for network element 1, network element 3 encapsulates the
message and sends it through network element 152 to network element 4,
which then routes the message to network element 1.

Figure 7-30
Partition repair
OTP2652
Area X
Partition 1
L2 IS
Network
element
2
Network
element
3
L2 IS
Network
element
1
Area X
Partition 2
Network
element
4
L2 IS
Network
element
153
Network
element
152
Network
element
154
Network
element
300
Network
element
151
Area Y
Partition repair functionality was introduced in Optical Connect DX optical

switch Release 2 and Optical Long Haul 1600 Release 6.
For more information on Level 2 routing, refer to the Data Communications
Network Planning Guide (NTR710AM).
OPC support
The partitioned OPC is the baseline OPC for Optical Long Haul 1600. The
OPC software delivery is executed by tape, 122 MB flash cartridge, or
POPC-C storage.
Fault management
ODPR-related alarms are available through the network banner line and the
TL1 fault management interface.
Performance monitoring capability
OPC PM Collection Filter tool and internal collection process are used to
monitor the switch protection counts. This information is also passed on to
Optical Network Management Applications Platform.
Extension shelf 2
The OPC supports extension shelf 2. Optical Long Haul 1600 provides OPC
software support for both SONET and SDH through a partitioned OPC
(POPC) circuit pack. Legacy OPCs located in the OC-48, OC-12, and TN-16X
shelves cannot be used to control Optical Long Haul 1600 network elements.
OPC software features

OPC software features for Optical Long Haul 1600 include:
software delivery by tape, 122 MB flash cartridge, or POPC storage circuit
pack
SOC commissioning
SOC upgrade from a previous to the current release through MCS. For
more information on MCS, refer to Commissioning and span of control
upgrades on page 7-2.
fault management and event status through the OPC tools, and Optical
Network Management upload
user ID and password management, time-of-day sync, OPC data Save and
Restore, OPC activity switch, OPC port configuration
Optical Network Management upload for remote inventory, shelf-level

graphics, facility provisioning, performance monitoring (PM) display
remote login across DATACOMM network in addition to Optical Network
Management remote pass-through capability
flow-through operations, administration and maintenance (OAM)
messaging through the Transport Bridge configuration
software download and managed software upgrades for a product release
PM collectors for transmitting to Optical Network Management and TL1
support for enhanced level of security access to network elements using
strong authentication
Level 2 routing (see Level 2 routing on page 7-53)
Span of control and deployment engineering guidelines

The span of control (SOC) engineering guidelines for Optical Long Haul 1600
are as follows:
A backup OPC is highly recommended in each SOC; primary and backup
OPCs should be in different locations.
Optical Long Haul 1600 software must be in a distinct and separate SOC
with its own OPC.
A mix of SONET and SDH network elements is not possible within the
same SOC.
Interworking between Repeater, OAS, and Amplifier is supported within
the same SOC.
Although an OPC can be in a network element that is outside of its SOC,
it is not recommended that the system be configured this way.
Level 2 routing enables network size to increase beyond the 150 nodes
DCC limit.
A maximum of 34 managed Optical Long Haul 1600 network elements is
allowed in each SOC.
The OSC link is limited to 13 hops if only MOR Plus amplifier OSC is
available for software upgrades.
Note: This limitation only applies when no other communication channel,
such as SONET/SDH section/RS DCC or Ethernet links, are accessible to
remote sites.
The OSC link is limited to 30 hops if only 1600G Amplifier OSCs are
available for software upgrades. For more information on this limitation,
refer to the 1600G Amplifier Unidirectional Network Application Guide
(NTY314AL).
A maximum of 30 DATACOMM hops (data communication sections) is
allowed from the primary OPC to managed network elements.
A maximum of 150 visible DATACOMM Level 1 nodes, including OPCs,
are allowed within the same SOC.
A maximum of four concurrent Optical Network Management
workstations are allowed.
TL1 facility and equipment provisioning

Transaction Language 1 (TL1) is an industry-recognized common language
protocol for messages exchanged between network elements and an operations
system (OS). TL1 allows an OS to communicate with different vendors
equipment through the common language protocol. TL1 eliminates the need to
support vendor-specific interfaces. Since Release 6, the Optical Long Haul
1600 platform supports facility and equipment provisioning through TL1.
Facility provisioning
Optical Long Haul 1600 provides facility provisioning support for retrieving
facility instances for the following circuit packs:
10 Gbit/s interfaces
2.5 Gbit/s interfaces
Dual Gigabit Ethernet interfaces
Optical Long Haul 1600 also supports editing the primary state from the TL1
provisioning interface for the facilities in the preceding list.
Facility provisioning support is provided for the MOR/MOR Plus amplifier
facilities from the TL1 provisioning interface on the Repeater network
elements and the OAS network elements.
You can change the following facility information through TL1, regardless of
the state of the DCC:
G-block
Primary state of the facility (IS or OOS)
F-Block
Common Language facility identifier (CLFI)
Signal degrade threshold
Equipment provisioning
Equipment provisioning includes the retrieval of states for the following
circuit packs:
10 Gbit/s interfaces
2.5 Gbit/s interfaces
Dual Gigabit Ethernet interfaces
MOR/MOR Plus circuit packs
Timing distribution (TD) circuit pack
all circuit packs in the control shelf of the Repeater network element
The enhanced TL1 support also includes the retrieval of MOR equipment and
all the circuit packs in the control shelf of the OAS network element.
TL1 provisioning support for editing the primary state on a Repeater network
element is also provided for in the preceding list.
Surveillance
The surveillance interface supports all Repeater circuit packs. Surveillance
support includes the following:
autonomous alarms, alerts, and logs reporting on the TL1 interface
support for nonautonomous commands to retrieve alarms
standing conditions
PM counts
both 15-min and 1-day bins, and history bins

setting the state of PM collection from the OPC
setting and retrieving PM count thresholds for both 15-min and 1-day, and
support for clearing the 15-min and 1-day bins
Optical Long Haul 1600 allows SDH or SONET standard PM counts to be

collected from a selected facility type on a given network element. Support for
SONET and SDH PM counts is also included in the TL1 surveillance.
Restrictions
The following restrictions and exclusions apply to TL1 provisioning:
Facility/Equipment provisioning on the Amplifier network element is not
supported.
Deleting equipment through TL1 is not supported.
TL1 facility provisioning for transmitter parameters (for example, Traffic
Mode and FEC attributes) is not supported.
To change the primary state of a circuit pack from IS to OOS through TL1,
you must do the following:
through TL1, place the facility of the circuit pack OOS
through the NE UI, place the DCC of the circuit pack OOS
You cannot change the state of the DCC through TL1. Through the NE UI,
you must change the state of the DCC by placing it out-of-service to place
the circuit pack OOS.
through TL1, place the circuit pack OOS
For a complete list of TL1 provisioning commands, refer to TL1 Interface
Description, 323-1801-190.
Optical Long Haul 1600 supports an optional centralized authentication
mechanism that provides additional security for accessing Optical Long Haul
1600 network elements and operations controllers (OPC).
An optional access based on a two-factor authentication is made available to
customers with requirements for strict control authentication to network
elements.
The two-factor authentication is characterized as follows:
user name and personal identification number (PIN) (constant
information)
RSA SecurID card with a pseudo-random number or dynamic token code
(dynamic information)
RSA Securitys SecurID card generates a token code every 60 seconds. If you
want to log in to a system, you must provide your user name and PIN, with the
token code displayed by the SecurID card. These three pieces of identification
form your passcode, which is authenticated by the RSA Security Access
Control and Encryption authentication server (ACE/Server). An intruder who
accesses your user name and PIN cannot access the system without a valid
token code from the SecurID card (<pin><token> <password>).
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 accepts token codes in a three-minute window, which allows you to
use either the last, current, or next valid token code. This feature is provided to
allow for clock drift between the SecurID card and the RSA Security server.
Nortel use of this feature is based on the Remote Authentication Dial-In User
Service (RADIUS) protocol. RADIUS is an industry standard protocol for
centralized authentication. The RSA Security authentication server, which
uses the SecurID token card for secure two-factor authentication, includes
support for RADIUS clients. This arrangement allows RADIUS clients to use
SecurID authentication without deploying proprietary SecurID authentication
software.
RADIUS clients are implemented on the OPC, according to RFC 2138. The
RADIUS client on the OPC is used as a proxy to a SecurID authentication
server. The OPC acts as a server (proxy) for network element authentication.
OPC-based authentication is simple to implement and administer. OPC-based
authentication is also scalable.
The authentication server (RADIUS or RSA Security) is a third-party product

that the customer must purchase and install.
Information about RADIUS/SecurID authentication servers can be obtained
from the following vendors:
RSA Security Inc. RSA Security Inc. is the manufacturer of the SecurID
token card and the ACE/Server authentication server. Optical Long Haul
1600 supports only the ACE/Server authentication server from RSA
Security Inc.
Nortel. Nortel provides the BaySecure Access Control RADIUS server
software.
Funk Software. Funk Software manufactures the Steel Belted RADIUS
authentication server software.
Figure 7-31 shows an example of a network configuration with authentication
servers.
Figure 7-31
Sample network configuration with authentication servers
OTP2263p
Firewall
Corporate
LAN
Preside
Integrated
Management
Authentication
Servers
NOC LAN
Router
High-speed
network
Router
Router
OPC Element
Network
Network
Element
Network
Element
Network
Element
OPC
RADIUS authentication protocol

The RADIUS protocol is an IETF Draft Standard (RFC 2138 and RFC 2139)
widely used to support remote access protocols (for example, telnet and
rlogin). This protocol can be used as single-factor authentication or as a proxy
to a SecurID authentication server for two-factor authentication.
The RADIUS protocol is a UDP-based client-server protocol that consists of
the following three messages:
Access-Request: message sent from the client to the authentication server
that provides user information (for example, user ID and password)
Access-Accept: message sent from the authentication server to the client
that grants access to you
Access-Reject: message sent from the authentication server to the client
that refuses access to you
OPC RADIUS authentication
The OPC implements full RADIUS clients (according to RFC 2138) and acts
as a proxy for network element authentication. With TCP/IP connection
already in place for Optical Network Management, the OPC can locate a
RADIUS/SecurID authentication server on the same network.
The OPC software architecture provides support for high availability of
RADIUS proxy process for network element authentication. A backup OPC
can provide warm standby switch-over if the primary OPC fails. Alarms also
become active at the network element level when an OPC fails. For more
information on new OPC equipment alarms for strong authentication, refer to
Table 7-11 on page 7-73.
The Centralized User Administration (CUA) tool on the OPC UI manages user
names, passwords, and security parameters for the OPC and network elements
in the OPC span of control. Support for RADIUS authentication is available in
the User Profile and Global Security Parameter screens.
The system administrator defines the system default authentication type for all
users as follows:
local (default). Only user ID and password are required.
RADIUS-local. User ID, password, and SecurID code are required.
system default authentication. Allows the system administrator to change
all users to either local or RADIUS-local authentication without having to
edit each user profile
Note: If the authentication requests from the network element and the
OPC are not delivered in a timely manner to the RADIUS server, users
with RADIUS-local authentication can access the system with local
authentication.
Network element RADIUS authentication

The network element supports the strong authentication feature through the
network element user interface (NE UI). The network element cannot
implement full RADIUS clients. Instead, the network element communicates
with the OPC as an authentication proxy (see Figure 7-32).
The use of the OPC as a RADIUS proxy for network element authentication
simplifies the following tasks:
deployment of centralized authentication
A TCP/IP overlay network to each network element is not required if the
network element implements its own RADIUS clients.
network administration
The authentication server does not require each network element to be
configured as an authentication client.
The data communications channel (DCC) datacomm path between the
network element and the OPC is a low-security risk because an intruder cannot
easily physically access the DCC.

Figure 7-32
Example of strong authentication in a span of control
OTP2264p
User access
through Preside
with SecurID card
ACE/Server
(Access Control
& Encryption Server)
Radius
Server
TCP/IP
Network
Element
Network
Element
Network
Element
Network
Element
Network
Element
Network
Element
Network
Element
Network
Element
Network
Element
Network
Element
User access
directly through
the OPC with
SecurID card
Legend
User access
remotely through
the OPC with
SecurID card
= DCC datacom path

= Strong authentication validation from
NE and OPC to SecurID ACE/Server
= Primary OPC
= Backup OPC
OPC user interface

The Edit User Profile of the CUA includes the Authentication type field. This
parameter is configured for each user. Only the system administrator can
change this parameter. If the system administrator changes this value, the new
value is communicated to the network elements in the OPC span of control and
to the inactive OPC.
Figure 7-33 displays the Edit User Profile dialog box, which includes the
Authentication type field.
Figure 7-33
Edit User Profile dialog box
OTP2267t
Edit User Profile

User Id:
Group:
User Name:
Detail:
Authentication type:
Network Element
[ OK
Return ]
<
Accessibility
Select group
Access Class
Change password
[ Cancel
Del]
The Configure System Parameters dialog box in the CUA tool includes the
Authentication type for special user field. This field allows the system
administrator to set the authentication type (local or RADIUS-local) for root,
root1, and standby users.
Figure 7-34 displays an example of the Configure System Parameters dialog
box with, which includes the Authentication type for special user field.
Figure 7-34
Configure System Parameters dialog box
OTP2268t
Configure System Parameters

Accreditation period (days):
Password expiration period (days):
Password obsolescence interval (days):
Authentication type for special user:
<
Passwords
Unacceptable Passwords:
Enter new unacceptable password:

[ OK
Return]
[ Cancel
Del]
You can provision the default authentication type (local or RADIUS-local)

from the Provision default parameters for the authentication type dialog box.
You can access this dialog from the Utilities menu.
Figure 7-35 shows an example of the authentication type dialog box.
Figure 7-35
Provision default parameters for the authentication type dialog box
OTP2269t
Prevision default parameters for the authentication type
Default authentication type:
[ OK
<
Return ]
[ Cancel
Del]
Alarms for the Strong Authentication feature

OPC equipment alarms for Strong Authentication
An alarm and a security log are raised if the system cannot access the RADIUS
server. A security log is also raised when you are allowed or denied access
when logging in to the OPC.
Table 7-11
OPC equipment alarms
Alarm and alert
Severity
Description
Primary: RADIUS
servers
unreachable
Major,
The RADIUS server is unreachable for the following possible
non-service reasons:
affecting
The provisioning data in the RADIUS server file (rsa_server) on the
(nsa)
OPC is invalid.
The RADIUS servers are not running.
A router/connection problem exists between the OPC and the
RADIUS server workstation.
Backup: RADIUS
servers
unreachable
Major, nsa
The RADIUS server is unreachable for the following possible

reasons:
The provisioning data in the RADIUS server file (rsa_server) on the
OPC is invalid.
The RADIUS servers are not running.
A router/connection problem exists between the OPC and the
RADIUS server workstation.
For more information on clearing alarms, refer to Trouble Clearing and

Module Replacement, 323-1801-543.
Network management
Optical Network Management Applications Platform is a software application
that runs on a Hewlett Packard workstation. The platform provides a single
point of access to the existing operations, administration, maintenance, and
provisioning functions in the network.
Optical Long Haul 1600 Release 10 requires Optical Network Management
Applications Platform 9.2.1 SP1 or 10 or later which supports the following:
Optical Section View (OSV) 5.2.4
Optical Power Management (OPM) 3.2.1
Wavelength Path Management (WPM) 3.2.4
DWDM View 1.2.4
Preside Software Upgrade Manager 2.1.0
For more information on these releases, refer to Optical Network Management
Applications Platform 9.2 SP1 Planning Guide, 450-3101-601.
Ethernet Wayside
ATTENTION
You cannot provision the Ethernet Wayside circuit pack in an Optical
Amplifier Shelf (OAS) or an Amplifier (AMP) network element.
The Ethernet Wayside circuit pack (NTCA56AA), introduced in Release 6,
provides end-to-end connectivity of two Ethernet 10Base-T ports through the
optical service channels (OSC) of the Optical Long Haul 1600 MOR Plus
amplifier circuit pack as the transmission medium. The communication
medium is the transmission fiber. The Ethernet Wayside data is transmitted
over the OSC channel of the MOR/MOR Plus and 1625 nm OSC circuit packs.
This transmission provides a maximum of 2 Mbits/s full-duplex bandwidth
capacity within the Ethernet Wayside network. The Ethernet Wayside circuit
pack can occupy slot 16 or 17 (G5 or G6) in the control shelf of the Repeater
network element.
The faceplate of the Ethernet Wayside circuit pack contains four 9-pin
10Base-T ports for connecting of up to four Ethernet devices (routers or
bridges) to a LAN. Each Ethernet Wayside circuit pack supports connection to
one WAN port, which is not visible to you. The wide area network (WAN) port
is connected to one bidirectional OSC facility. Two Ethernet Wayside circuit
packs are required to handle eastbound and westbound directions.
Note: All MOR Plus amplifier sites must be equipped with Ethernet
Wayside circuit packs using Ethernet Wayside functionality.
The Ethernet Wayside circuit pack is implemented as a layer 2 Repeater that

supports Ethernet II and IEEE 802.3 traffic. The Ethernet Wayside circuit pack
bridges frames between the Ethernet port and the OSC. The Ethernet Wayside
circuit pack provides a convenient way of connecting remote Ethernet
equipment without requiring the allocation of additional payload bandwidth.
The Ethernet Wayside circuit pack also provides learning bridge functionality.
However, the Ethernet Wayside circuit pack does not detect network loops.
The learning bridge functionality improves network performance by reducing
unnecessary traffic flow on the Ethernet Wayside WAN. Irrelevant traffic is
not forwarded through the Ethernet Wayside WAN from external networks that
connect to the Ethernet Wayside.
Although direct hub connections to the Ethernet Wayside circuit pack are
accepted, it is recommended that a front-end bridge or router be installed to
optimize throughput and the handling of complex networks.
Applications for the Ethernet Wayside circuit pack include the following:
access to remote power monitoring equipment from a centralized
monitoring station
The Ethernet Wayside circuit pack removes the need for separate telephone
line and modem equipment for the remote site, which have significant cost
implications (see Figure 7-36).
access to remote LAN
With routers connected to the Ethernet Wayside circuit packs, assign a
2 Mbit/s bandwidth WAN to interconnect the LANs.
native Ethernet connectivity by a craftsperson to the corporate intranet
from a remote site
This feature allows you to download documentation (for example,
provisioning and test procedures) from the corporate intranet.
Figure 7-36
Ethernet Wayside network configuration
OTP2270p
Ethernet Wayside
equipped
network element
Ethernet Wayside
equipped
network element
LAN
LAN
Router
Router
OSC
10Base-T
Ethernet
10Base-T
Ethernet
User station
Remote equipment
The advantages of deploying the Ethernet Wayside circuit pack compared to

other solutions are as follows:
native Ethernet connectivity between Optical Long Haul 1600 network
elements for data networking
This connectivity prevents the need for a separate data network between
network elements using payload bandwidth.
long-distance Ethernet (WAN) for connecting corporate networks
(intraWAN) using existing equipment
convenient, standardized, and inexpensive interface for connecting

different customer equipment
compatibility with other Optical Long Haul 1600 equipment
The Ethernet Wayside circuit pack generates alarms and logs consistent
with other Optical Long Haul 1600 equipment. The Ethernet Wayside
circuit pack can be provisioned through the NE UI interfaces. You avoid
the need to learn new interfaces and commands to manage a piece of data
equipment.
better performance than traditional dial-up connectivity using modems
Feature description
The Ethernet Wayside circuit pack communicates with MOR/MOR Plus
amplifier circuit packs through the backplane to transmit and receive Ethernet
traffic. The MOR/MOR Plus amplifier circuit packs are supported in slots 1,
2, 3, 4 (G0, G1, G2, G3 respectively) of the main shelf in a Repeater network
element. You must follow MOR/MOR Plus amplifier circuit pack provisioning
rules.
Figure 8-8 on page 8-36 shows the positioning of the Ethernet Wayside circuit
pack in the control shelf.
For a complete description of Ethernet Wayside, refer to the Ethernet Wayside
User Guide (NTY317GF).
Ethernet Wayside powering up and autoprovisioning
Full Ethernet Wayside capability is not available until you provision the
Ethernet Wayside circuit pack (auto-provision or change primary state to IS).
After the Ethernet Wayside circuit pack autoprovisions, the Ethernet Wayside
default mode is set to in-service (IS). However, no Ethernet Wayside
connections to MOR/MOR Plus amplifier circuit packs are established.
If the shelf controller (SC) circuit pack is not active when the Ethernet
Wayside circuit pack is powered up, Ethernet Wayside communication is not
supported. With the SC inactive, the Ethernet Wayside circuit pack initializes
but does not receive, process, or generate Ethernet Wayside bytes for the OSC.
If the SC circuit pack is active when the Ethernet Wayside circuit pack is
powered up, or if the SC becomes active while Ethernet Wayside is in the IS
default mode, the Ethernet Wayside circuit pack automatically configures with
no connections established (default mode).
When you have completed provisioning the Ethernet Wayside circuit pack
group and Ethernet Wayside connection, the Ethernet Wayside circuit pack
status is reported as in-service (IS), and the connections are established as
provisioned.
Note: The Ethernet Wayside circuit pack is only supported within a

commissioned Repeater network element. You can only provision Ethernet
Wayside connections to establish wayside network connectivity after the
Repeater network element is commissioned.
Ethernet Wayside communication
The Ethernet Wayside circuit pack supports one fixed Ethernet Wayside WAN
port. The WAN port is connected to one bidirectional OSC facility and
provides bidirectional communications with another Repeater network
element equipped with Ethernet Wayside.
For a Repeater network element to provide Ethernet Wayside communication
in eastbound/westbound directions, two Ethernet Wayside circuit packs are
required (maximum allowed). One Ethernet Wayside circuit pack provides
bidirectional communication in the eastbound direction. The second Ethernet
Wayside circuit pack provides communication in the westbound direction.
Figure 7-37 shows the Ethernet Wayside circuit pack with four Ethernet
connectors on the faceplate.
Each Ethernet Wayside faceplate supports up to four 9-pin 10Base-T ports.
The Ethernet Wayside equipment provides circuit pack group creation logs and
menus for selection of in-service (IS) or out-of-service (OOS) and deletion of
the circuit pack group.
Any excess traffic above the stated limit requires retransmission from upper
layers. The information packets received from the Ethernet Wayside faceplate
connections are forwarded to the Ethernet Wayside WAN port for transmission
over the OSC. The reverse is also true. Information packets received from the
Ethernet Wayside WAN port are forwarded to the Ethernet Wayside faceplate
connections on the same Ethernet Wayside circuit pack.
Pass-through
No OSC pass-through mode is available for forwarding Ethernet traffic

through one Repeater network element to another Repeater network element.
All line Repeater network elements require two Ethernet Wayside circuit packs
to bridge the Ethernet connection for forwarding Ethernet transmissions down
the line. Pass-through of the Ethernet Wayside traffic can be achieved by using
faceplate connectors from two Ethernet Wayside circuit packs through a
cross-over Ethernet cable (Ethernet to Ethernet). This connection procedure is
also used to interconnect Ethernet Wayside networks.
Add/drop of Ethernet Wayside traffic
Nortel recommends that you use routers or bridges at network elements where
you need to add and drop Ethernet traffic. However, no restriction exists on the
type of Ethernet equipment that can be connected to the Ethernet Wayside
circuit pack. You can connect hosts, bridges, or routers to the Ethernet Wayside
network. You are responsible for ensuring that the data network is configured
correctly. By connecting bridges or routers to the Ethernet Wayside circuit
pack, you add the advantage of limiting traffic to the amount that is required
to move across the network. If you connect a host station to the Ethernet
Wayside network, more traffic is sent on the network and this unnecessary
traffic degrades the overall network performance.
Ethernet Wayside loops
You are responsible for ensuring that no Ethernet loop is created when you
install and commission Ethernet Wayside on a ring configuration. Have at least
one router or bridge in each Ethernet Wayside loop in the network or leave one
of the OSC connections unprovisioned. You are thereby opening any potential
loop.
Note: No alarms report the existence of a loop. Ethernet Wayside network
loops degrade network performance because of traffic accumulation (for
example, broadcast traffic and destination not found).
OSC pair status validation and Ethernet Wayside circuit pack validation are
performed when Ethernet Wayside WAN connections are provisioned. No
other attempt is made to protect the Ethernet Wayside channel in the event of
any equipment or provisioning failure.
Connection provisioning
You provision an Ethernet Wayside connection manually through the NE UI

menus.
The query command shows the provisioned Ethernet Wayside WAN
connections and their current status (up/down, with a potential reason).
Ethernet Wayside circuit pack restart
During an Ethernet Wayside circuit pack restart, Ethernet Wayside traffic is

lost for approximately 10 seconds. Upper layers initiate retransmission. Traffic
continuity is automatically restored after the Ethernet Wayside circuit pack
restart completes.
Front faceplate LEDs
LEDs on the faceplate show circuit pack status information (see Table 7-12).
Red and green LEDs are located on the faceplate. LEDs are activated or
deactivated according to the same rules that apply for all circuit packs in a bay.
The yellow LED is always turned off except during lamp tests and Ethernet
Wayside circuit pack restarts.

Table 7-12
Ethernet Wayside circuit pack faceplate LEDs
Faceplate LEDs
Status
Conditions
Status LED 1
Red
When active, an Ethernet Wayside circuit pack
(see Note) equipment failure has been detected.
Status LED 2
Green
When active, the Ethernet Wayside equipment is

in-service and running.
Link LED
Yellow
This LED is always inactive, except during

lamptest and Ethernet Wayside circuit pack
restarts.
Note: A red LED that is ON usually indicates a partial or complete failure of the
circuit pack (for example, a Circuit pack fail alarm). A red LED that is ON can also
indicate a mismatch condition on the circuit pack (for example, a Circuit pack
mismatch alarm).
Provisioning connections using the NE UI
The Circuit Pack Group Equipment (CPGE) command in the NE UI menu

(command cpge) allows you to make changes to the Ethernet Wayside circuit
pack group (for example, change of state and deletion). The standard NE UI
CPGE menu also allows you to query the Ethernet Wayside circuit pack and
circuit pack group. The Ethernet Wayside circuit pack group is deleted only
when its primary state is OOS.
Note 1: The Ethernet Wayside circuit pack group is created through
auto-provisioning when the circuit pack is inserted into the slot.
Note 2: You cannot create the Ethernet Wayside circuit pack group using
NE UI commands.
You are responsible for manually provisioning Ethernet Wayside connections
to the MOR Plus/MOR amplifier OSC pairs that carry the OSC signal
(bidirectional).
OSC LOS on line circuit pack group (for example, fiber breaks)
When an MOR Plus/MOR OSC circuit pack group experiences a loss of signal
(LOS) condition on the incoming signal and the circuit pack group has been
configured to receive Ethernet Wayside traffic, no Ethernet Wayside traffic is
possible on the connection. Ethernet Wayside traffic is automatically restored
when the LOS condition clears.
For information on circuit pack positioning and sparing, refer to Mechanical
specifications on page 9-1.
For a detailed description of Ethernet Wayside, refer to the Ethernet Wayside

Figure 7-37
Ethernet Wayside circuit pack
OTP2320p
Based on
F3756_R21
Port 1
Port 2
9-pin 10Base-T
Ethernet ports
Port 3
Port 4
Circuit pack
restart (Yellow)
Fail or
mismatch
(Red)
Active (Green)

The orderwire (OW) circuit pack, along with its associated software
functionality, provides voice-frequency communication between Optical Long
Haul 1600 network elements using the following:
orderwire interfaces present on the local craft access panel (LCAP)
the orderwire circuit pack faceplate
Orderwire is typically used during maintenance activities, when craftspeople
at two sites must communicate to coordinate their actions and confirm
diagnostic results. The orderwire circuit pack is an optional component that
(when equipped) resides in slot 15 of the control shelf of the Optical Long Haul
1600 network element. The presence or absence of the orderwire circuit pack
does not impact any aspect of the Repeater network element operation except
for orderwire functionality.
Local and express orderwire is accessed over the optical service channel
(OSC) supported on multiwavelength optical repeater (MOR) Plus amplifiers
in slots 1 to 4 (G0 to G3) of the Optical Long Haul 1600 network element to
obtain OW functionalities on the DWDM link. OW is provided through a
pairing of two MOR Plus amplifier (or 1625 nm OSC, if required) circuit
packs in the Repeater main shelf.
Before Release 6, orderwire (OW) was not fully user-configurable. Fixed
access was implemented instead of open access. Connections were
automatically created and no changes were allowed (for example, each OW
connection was fixed to a transmit (Tx) and a receive (Rx) optical service
channel (OSC) supplied by the MOR Plus amplifier circuit pack pairs). Also,
one manual seam was provisioned (applied to one of the two fixed connections
as determined by the software). One automatic seam appeared (applied to one
of the two fixed connections as determined by the software).
Open access technology benefits the end user by providing more control over
OW connectivity and maintenance over the MOR Plus optical line. You can
decide specifically which transport circuit packs bridge an OW connection.
You can provision a manual seam for individual connections. When automatic
seams appear in the Repeater network element, you can query the connections
to discover which specific connections are affected.
Some limitations exist for open access technology. The supported transport for
OW on a Repeater network element continues to be through the bidirectional
OSC of the MOR Plus amplifier circuit pack. However, a Repeater network
element allows provisioning for a maximum of four MOR Plus amplifier
circuit packs (two pairs). Because OSC requires a pair of MOR Plus amplifier
circuit packs to operate correctly, OW connects the OSC to the conference
bridge through the MOR Plus amplifier circuit pack pair. The system supports
no more than two OW connections, although the OW software is capable of
establishing up to six connections.
Connection Query and Addition
You can add, delete, and query connections and enable and disable manual
seams based on a connection. The Orderwire menu allows all of these options.
Use the ADD connections command to create a connection (see Figure 7-38).
Figure 7-38
Orderwire Menucreating a connection (example)
OTP2272t
Orderwire Menu
-------------0. Quit
1. QueRy General parameters
4. ADD connections
NE 234> 4
Enter the receiving circuit pack(RX) circuit pack type:
[ MOR, ]
? mor
Enter the receiving circuit pack(RX) circuit pack name:
[ G0, G1, G2, G3, G5, G6, G7, G8 ]
? g0
Are you sure?
Do you wish to continue:
[Y,N]
? y
Command successful.
NE 234>
Use the Query connections command to query a connection (see Figure

7-39).

Figure 7-39
Orderwire Menuquerying a connection (example)
OTP2273t
Orderwire Menu
-------------0. Quit
4. ADD connections
NE 234> 3
RX
TX
OSC
Manual
Auto
Bridge
Connection
Port#
CPG
CPG
Facility seam
seam
Status
details
-------------------------------------------------------------------------------1
MOR G0 MOR G1
NULL
BRIDGED
Connection bridged
2
NULL
UNBRIDGED No
Connection
3
NULL
UNBRIDGED No
Connection
4
NULL
UNBRIDGED No
Connection
5
NULL
UNBRIDGED No
Connection
6
NULL
UNBRIDGED No
Connection
NE 234>
Manual seams
Manual seams are no longer enabled and disabled through the Network
Parameters NE UI menu and no longer take effect across all connections on the
OW circuit pack (for example, one seam for all six possible connections).
Manual seams are now enabled and disabled based on a connection through
menu items on the Orderwire menu in the NE UI. After the seam operation is
selected, you are prompted for the Rx circuit pack group of the connection in
question. This information is sent to the Orderwire Connection software,
which finds the appropriate connection record and sets the manual seam flag
accordingly.
Use the Enable Manual Seam command to enable a manual seam (see Figure
7-40).

Figure 7-40
Orderwire Menuenabling a manual seam (example)
OTP2275t
Orderwire Menu
-------------0. Quit
4. ADD connections
NE 234> 6
Enter the receiving card(RX) circuit pack type:
[ MOR, ]
? mor
Enter the receiving card(RX) circuit pack name:
[ G0, G1, G2, G3, G5, G6, G7, G8 ]
? g0
Are you sure?
[Y,N]
? y
Command successful.
NE 234>
For a detailed description of orderwire and orderwire provisioning, refer to the

SONET Orderwire User Guide (NTCA66CA) or the SDH Orderwire User
Guide (NTCA66DA).
The orderwire public switched telephone network (PSTN) functionality is not
supported when a Wavelength Combiner is created in SDH mode. All other
OW attributes are similar to those provided with the OC-192 Release 7 and
TN-64X Release 2.
8-1
Engineering rules
8-
Chapter overview
This chapter provides engineering rules for circuit pack positioning, sparing,
and replacement.
Section
Page
Circuit pack maximum and optical jitter
8-2
Mechanical bay assembly shelf G-naming
8-2
Circuit pack positioning for the control shelf
8-4
Circuit pack positioning for transport circuit packs
8-9
Circuit pack sparing and replacement
8-18
OPC definition and span of control
8-25
Repeater network element limitations
8-29
Network synchronization requirements
8-30
8-33
Ethernet Wayside
8-36
8-42
8-45
8-2 Engineering rules
Circuit pack maximum and optical jitter

An optical signal can pass through a maximum of 30 WT, XR, or combination
of WT and XR circuit packs on an optical link. This maximum complies with
the Telcordia (formerly Bellcore) specifications for jitter outlined in the
following documents:
For jitter generation: GR-1377 Section 5.6.5 requirement, R5-20, R5-23
For jitter tolerance: GR-1377 requirement, R5-22
For jitter transfer: GR-1377 requirement, R5-21
The 30 circuit pack maximum applies to any combination of 2.5G WT,
10G WT, or OC-192/STM-64 XR circuit packs.
Mechanical bay assembly shelf G-naming

The mechanical bay assembly (NTCA89GC) includes the control shelf, the
main shelf, extension shelf 1, and extension shelf 2. A total of 30 slots (G0 to
G29) are available for placing circuit packs. The mechanical bay assembly
(NTCA89GB) that includes the control shelf, the main shelf, and extension
shelf 1 is also supported.
Table 8-1 describes the conventions used for G-naming and slot numbering.
Table 8-1
G-naming and slot numbering
Shelf
G-name
Slot numbering
Control shelf
G1 to G6
1 to 17
Main shelf
G0 to G9
1 to 10
Extension shelf 1
G10 to G19
1 to 10
Extension shelf 2
G20 to G29
1 to 10
Figure 8-1 shows shelf locations for Repeater network element circuit packs.
Engineering rules 8-3

Figure 8-1
Supported circuit pack positions for Repeater applications
PEC
NTCA70xx
NTCA72xx
NTCA07xx
NTCF07xx
NTWR07AA
NTCA04xx
NTCF04xx
NTCA06xx
NTCF06xx
NTCA30xK
NTCA30CK
NTCA90xA
NTCA39AA
NTCA21AA
NTCA11xx
NTCA56AA
Control Shelf
POPS
Circuit pack
2.5G WT
Dual 2.5G WT
10G WT
10G WT (TriFEC)
10G WT SR (TriFEC)
OC-192/STM-64 XR
OC-192/STM-64 XR/WT
OC-192/STM-64 T/R
OC-48/STM-16 T/R SR
Dual GE
Timing Distribution (TD)
MOR Plus
Ethernet Wayside
POPC
32 MB SC
ESI
ESI
128 MB MI
MX
MX
POPI
PT
PT
OW
Ethernet Wayside
Ethernet Wayside
Attention
engineering rules.
Breaker filters
Breaker filters
Applications
MOR Plus
WT
XR
ODPR
WC
OTP3512p

Air Intake
FMT
FMT
Air Exhaust
G0 G1 G2 G3 G4 G5 G6 G7 G8 G9
MOR Plus
Main shelf
WT
XR
WC
TD
OPDR CPG
Extension shelf 1
OSM
G10 G11 G12 G13 G14 G15 G16 G17 G18 G19
G20 G21 G22 G23 G24 G25 G26 G27 G28 G29
WT
XR
Extension shelf 2
WC
OPDR CPG
OSM
Legend
MOR Plus
WT
XR
ODPR CPG
=
=
=
=
MOR Plus amplifier circuit packs

Wavelength Translator circuit packs
Optical dedicated protection ring circuit pack group
WC
TD
OSM
FMT
=
=
=
=
Wavelength Combiner circuit pack group

Timing Distribution circuit pack
Fiber management tray
Circuit pack positioning for the control shelf

Table 8-2 lists the supported circuit pack positions for control shelf circuit
packs.
Table 8-2
Circuit pack positions for control shelf circuit packs
Circuit pack type
G-name(s)
Slot number(s)
Shelf description
Ethernet Wayside
G5 and G6
16, 17
Control shelf
Breaker filters
1, 2
Control shelf
3, 4
Control shelf
Control shelf
12
Control shelf
POPC-S
POPC-C
G1
POPC-I
32M SC
G1
Control shelf
Filler
7, 8, 16, 17
Control shelf
128M MI
G1
Control shelf
MX (see Note)
G1, G2
10, 11
Control shelf
PT
G2, G3
13, 14
Control shelf
OW
G4
15
Control shelf
ESI
G1, G2
7, 8
Control shelf
Note: Two MX circuit packs are required for the ODPR circuit pack group to function correctly.
Mandatory circuit packs for the control shelf

The following circuit packs are mandatory for the Repeater network element:
breaker/filter module
shelf controller (SC) circuit pack
maintenance interface (MI) circuit pack
message exchange (MX) circuit pack
filler circuit pack
Breaker/filter module
Two breaker/filter modules (A and B) units must be equipped in slots 1 and 2

of the control shelf for redundant 48 V supply to the shelves. Each
breaker/filter module contains seven 15-ampere breakers and the associated
filters. The modules distribute power to the control shelf, main shelf, extension
shelf 1, and extension shelf 2, including the environmental control panels
(ECP).
The circuit breakers are logically assigned for the power distribution to the
control shelf, to each half of the main shelf, and to each half of extension shelf
1 and extension shelf 2 (see Figure 8-2). In addition, the breaker/filter modules
attenuate the noise on the 48 V power lines. The filters also limit current
surges and clamp overvoltages.
Figure 8-2
Optical Long Haul 1600 power distribution and circuit breaker assignment (one battery feed)
OTP0241
(-)
A3
(-)
A2
(-)
A1
-48V connections on external power

termination, at top of the bay
1
3 - 17
Control shelf
2
1-5
Main shelf
2
6 - 10
3
1-5
Extension shelf 1
3
6 - 10
4
1-5
Extension shelf 2
4
6 - 10
Note: Fan power is provided by internal fuses located in the breaker/filter module.
Shelf controller (SC) circuit pack
One SC processor is required in the control shelf. The SC circuit pack is

equipped in slot 6. The SC circuit pack interfaces to all software-based circuit
packs and serves as a message gateway for DCC, external RS-232, and
Ethernet. The functions of the SC circuit pack include alarm reporting, PM
collection, system fault detection, isolation and protection, software download

and upgrade, and restart capability from the local nonvolatile flash on the
maintenance interface (MI) circuit pack.
The SC autoprovisions the circuit packs that are inserted in the Optical Long
Haul 1600 main and two extension shelves. The SC performs the following
functions:
automatically recognizes the circuit pack
places the circuit pack in-service
creates facilities (where applicable)
initializes the default provisioning values (for example, minimum Tx
power)
Note: The system generates a Circuit pack missing alarm if a
provisioned circuit pack is removed from its slot.
Maintenance interface (MI) circuit pack
The maintenance interface (MI) circuit pack is required for each Optical Long
Haul 1600 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 with the SC circuit pack and contains 128 Mbytes
of flash memory, which is used for configuration and code storage. The main
functions of the MI circuit pack include alarm reporting, processor sanity,
circuit pack inventory and status, and Ethernet/RS-232 port drivers. The 32
Mbyte or 64 Mbyte MI circuit packs found on the Optical Connect DX optical
switch platform are not supported on the Optical Long Haul 1600 platform.
Message exchange (MX) circuit pack
The message exchange (MX) circuit pack is equipped in slot 10 (mandatory)

and 11 (optional) of the control shelf. This circuit pack handles internal
communications between the control circuit packs and the optical circuit
packs, as well as DCC routing. The MX circuit pack connects the SC circuit
pack to all software-based circuit packs in the Optical Long Haul 1600 bay
through the internal star-based LAN.
Note: The MX circuit pack is mandatory in slot 10 of the control shelf. It
is highly recommended to equip a second protection MX circuit pack
circuit pack in slot 11. You must equip a second protection MX circuit pack
in a Repeater network element if the network element includes an optical
dedicated protection ring (ODPR) circuit pack group.
Filler circuit packs
To prevent electromagnetic interference (EMI) emissions, filler circuit packs

(NTCA59AA) are required for all empty slots in the control shelf of the
Optical Long Haul 1600 bay. Insert additional filler circuit packs in slots 3, 4,
5, and 12 of the control shelf if the partitioned OPC (POPC) is not used. Filler
circuit packs are also required in slots 11, 13, 14, 15, 16, and 17 of the control
shelf if the redundant MX, the parallel telemetry (PT), the orderwire (OW),
and the Ethernet Wayside (EW) circuit packs are not used.
Optional circuit packs
The following circuit packs are optional for the Repeater network element:
Timing distribution (TD) circuit pack
OPC controller (POPC-C)
OPC storage (POPC-S)
OPC interface (POPC-I)
Message exchange (protection) circuit pack
Parallel telemetry (PT) circuit pack
Orderwire (OW)
Ethernet Wayside (EW) circuit pack
Note: An optional circuit pack can be equipped in the input/output slots of
the control shelf.
Equip two half-height timing distribution (TD) circuit packs in slots G4A and
G4B of the Repeater network element to achieve a 1+1 non-revertive timing
protection scheme. The TD circuit pack provides differential clock references
to each OC-192/STM-64 T/R line/MS circuit pack.
For protection operation, you must equip two external synchronization

interface (ESI) circuit packs in slots 7 and 8 of the control shelf for the
Wavelength Combiner application. The ESI circuit pack is required to
synchronize the Optical Long Haul 1600 bay to an external BITS or the
Optical Long Haul 1600 line/MS source. The DS1 or the 2 MHz timing
reference signal is connected to the wire wrap field on the uniSATT card.
OPC controller (POPC-C)
The OPC controller circuit pack is the basic hardware component of the OPC
computing engine for the Optical Long Haul 1600 control shelf. The OPC
controller provides operations, administration, maintenance, and provisioning
(OAM&P) functionality. The OPC controller circuit pack communicates with
the OPC interface circuit pack, the OPC storage circuit pack, the shelf
controller circuit pack, and the maintenance interface circuit pack.

OPC storage (POPC-S)
The OPC controller storage circuit pack consists of a hard-disk drive,

electrically erasable programmable read-only memory (EEPROM) and a
removable media interface (NTCA53BA). The OPC storage circuit pack
functions as an extension to the OPC controller.
OPC interface (POPC-I)
The OPC interface circuit pack is designed to be a reactive circuit pack. The
OPC interface circuit pack provides the external customer interfaces for the
Optical Long Haul 1600 control shelf. It also communicates with the
maintenance interface circuit pack and the OPC controller circuit pack.
Note: The legacy OPC (NT7E24xx) is not supported on Optical Long
Haul 1600.
Message exchange (protection) circuit pack
The MX circuit pack connects the shelf controller to all software-based circuit
packs through an internal bus. The MX circuit pack detects circuit pack
presence and supports intercard messaging. The MXA circuit pack, equipped
in slot 10, is a mandatory circuit pack. A second protection MX circuit pack,
MXB in slot 11, is an optional circuit pack (see Note). The main function of
the second MX circuit pack support is to provide protection for intercard
messaging.
Note: The MX circuit pack is mandatory in slot 10 of the control shelf. It
is highly recommended to equip a second protection MX circuit pack
Parallel Telemetry (PT) circuit pack
Two optional parallel telemetry circuit packs can be equipped in slots 13 and
14 of the control shelf. The PT circuit pack offers 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 monitors and controls external equipment.
Orderwire (OW) circuit pack
The orderwire (OW) circuit pack provides two voice frequency

communication channels between Optical Long Haul 1600 network elements.
The channels operate at a rate of 64 Kbit/s, using reserved bytes within the
optical service channel (OSC). OSC can be transmitted on the 1510 nm or/and
the 1625 nm wavelength. Orderwire over the SONET overhead is not
available.

Ethernet Wayside (EW) circuit pack
Ethernet Wayside provides end-to-end connectivity of two Ethernet 10base-T

ports through the optical service channel (OSC). The Ethernet data is
transmitted within reserved bytes of the OSC. A maximum of 2 Mbit/s full
duplex bandwidth capacity is provided within the Ethernet Wayside network.
Two Ethernet Wayside circuit packs can be equipped in slots 16 and 17 of the
control shelf.
Circuit pack positioning for transport circuit packs

You must follow positioning rules for circuit packs equipped in an Optical
Long Haul 1600 bay. A circuit pack autoprovisions correctly when it is placed
in a supported slot within the bay for the application. Each circuit pack has
predefined supported slots within a bay that support the circuit packs
functionality. When you insert the circuit pack into a supported unprovisioned
slot, the circuit pack will autoprovision correctly.
For sparing and replacing provisioned circuit packs, refer to Circuit pack
sparing and replacement on page 8-18.
The first four slots of the main shelf support a mix of the following circuit
packs:
MOR Plus amplifier (NTCA11xK)
10G WT (NTCA07xx)
10G WT (TriFEC) (NTCF07xx)
10G WT SR (TriFEC) (NTWR07AA)

OC-192/STM-64 XR (NTCA04xx)
OC-192/STM-64 XR/WT (NTCF04xx)
2.5G WT (NTCA70xx)
Dual 2.5G WT on/off ram (NTCA72xx)
G4 to G9 and G10 to G29 support all of the above circuit packs, except for the
MOR Plus amplifier circuit pack.
For an overview of the possible circuit pack and circuit pack group positions
within the Optical Long Haul 1600 bay, see Figure 8-1 on page 8-3.
Be sure to comply with the following rules when you equip the network
element:
MOR Plus amplifier equipping rules (supported only in the first four slots,
G0 to G3, of the main shelf)
OC-192/STM-64 XR pairing rules
TriFEC thermal, power, and engineering rules
Note: The existing equipping rules for mid-stage access (MSA) amplifier
configurations continue to apply.
You must follow MOR Plus amplifier equipping rules. For more information,
refer to the 100 GHz, MOR/MOR Plus, 2 to 32- Optical Layer Applications
Guide (NTY312DX).
For more information on XR pairing rules, refer to Dense regenerator circuit
packs on page 8-12.
For more information on TriFEC thermal, power, and engineering rules, refer
to Thermal tool on page 9-24.
MOR Plus amplifier circuit packs
Table 8-3 lists the supported G-name and slot positions for MOR Plus
amplifier circuit packs.
Table 8-3
G-names and slot positions for MOR Plus amplifier circuit packs
Circuit pack
MOR Plus amplifier or

1625 nm OSC (see Note)
Supported locations in the Repeater network element

G-name(s)
Slot number(s)
Shelf description
G0, G1, G2, G3
1, 2, 3, 4
Main shelf
Note: You must follow MOR Plus amplifier equipping rules. For more information, refer to the
100 GHz, MOR/MOR Plus, 2 to 32- Optical Layer Applications Guide (NTY312DX).
Wavelength Translator circuit packs

You can equip the following WT circuit packs in slots 1 through 10 of the main
shelf, extension shelf 1, and extension shelf 2:
10G WT circuit pack (NTCA07xx)
2.5G WT circuit pack (NTCA70xx)
Dual 2.5G WT on/off ramp (NTCA72xx)
Note 1: No pairing rules exist for WT circuit packs. When you equip a WT
circuit pack in an empty unprovisioned slot, the circuit pack autoprovisions
but its paired slot does not autoprovision. You can equip a 10G WT circuit
pack and a single 2.5G WT circuit pack side by side: an alarm is not raised.
Note 2: The 10G WT SR (TriFEC) (NTWR07AA or NTWR17AA) circuit
pack is used in off-ramp positions only. The transmitter of this circuit pack
is equipped with short-reach optics.
Table 8-4 lists the supported G-name and slot positions for Wavelength
Translator circuit packs.
Table 8-4
G-names and slot positions for Wavelength Translator circuit packs
Circuit pack type

G-name(s)
Slot
number(s)
Shelf description
10G WT (NTCA07xx)
G0 through G9
1 through 10
Main shelf

(see Note 1 and Note 2)
G10 through G19
1 through 10
Extension shelf 1
G20 through G29
1 through 10
Extension shelf 2
10G WT (TriFEC) (NTCF07xx) (see Note 1)

2.5G WT (NTCA70xx)
Dual 2.5G WT on/off ramp (NTCA72xx)
Note 1: You must follow TriFEC thermal, power, and engineering rules. Refer to Thermal tool on page
9-24.
Note 2: FEC-capability is available on the receiver only. The transmitter is equipped with short-reach
optics.
For information on equipping rules for the Wavelength Translator application

using TriFEC-capable circuit packs, refer to Thermal tool on page 9-24.

The following XR circuit packs can be equipped in slots 1 through 10 of the
main shelf, extension shelf 1, and extension shelf 2:
XR circuit pack pairing rules
The XR circuit pack pairing rules apply for the following circuit packs:
The pair must have one pack face eastbound and one pack face westbound to
maintain DCC connectivity.
A Repeater network element supports pairs of OC-192/STM-64 XR circuit
packs as follows:
five pairs in the main shelf (G0 to G9)
five pairs in extension shelf 1 (G10 to G19)
five pairs in extension shelf 2 (G20 to G29)
For the OC-192/STM-64 XR circuit packs, the adjacent slot is reserved for
another OC-192/STM-64 XR circuit pack. For example, if an
OC-192/STM-64 XR circuit pack is inserted in position G0, then G1 is
reserved for another 10 Gbit/s XR circuit pack. If a circuit pack other than the
expected circuit pack is inserted in position G1, an Autoprovisioning
mismatch alarm is raised (in this case, G1).
The merged XR/WT circuit packs do not reserve the adjacent slot as is done
with the OC-192/STM-64 XR circuit packs. For example, an OC-192/STM-64
XR/WT circuit pack (traffic mode set to REGEN for XR) is inserted in
position G0. An incorrect pairing circuit pack is seated in the adjacent slot (G1)
and it autoprovisions to 3R for WT. A Traffic mode mismatch alarm is raised
against G0. The alarm clears when the pair of circuit packs are provisioned
with the same traffic mode (both set to 3R or both set to REGEN).
Note 1: For more information on the Traffic mode mismatch alarm,
refer to Alarms for merged XR/WT circuit packs on page 13-3.
Table 8-5 lists the supported G-name and slot positions for Dense regenerator
circuit packs.

Table 8-5
G-names and slot positions for Dense regenerator circuit packs
Circuit pack type

G-name(s)
Slot number(s)
Shelf description
G0 to G9
1 to 10
Main shelf
G10 to G19
1 to 10
Extension shelf 1
G20 to G29
1 to 10
Extension shelf 2
Wavelength Combiner circuit pack groups

ATTENTION
A Repeater network element equipped with at least one Wavelength
Combiner circuit pack group requires two ESI and two half-height TD circuit
packs. When a Repeater network element is equipped with a Wavelength
Combiner and the two ESI and two half-height TD circuit packs are missing,
Optical Long Haul 1600 does not raise an alarm.
Wavelength Combiner circuit pack groups can be equipped as follows:
slots 6 to 10 of the main shelf
slots 1 to 5 and slots 6 to 10 of extension shelf 1
Each Wavelength Combiner circuit pack group consists of five circuit packs
described as follows:
one OC-192/STM-64 T/R circuit pack (NTCA06xx) and up to four of the
same or a mix of the following circuit packs
Dual Gigabit Ethernet (NTCA90XA)
one OC-192/STM-64 T/R (TriFEC) (NTCF06xx) circuit pack and up to
four of the same or a mix of the following
Dual Gigabit Ethernet (NTCA90xA)
You can equip a Wavelength Combiner circuit pack group with less than four
tributaries. You can equip tributaries with no sequence restrictions when the
deployed 10 Gbit/s line circuit packs are OC-192/STM-64 T/R (NTCA06xx),
OC-192/STM-64 T/R (TriFEC) (NTCF06xx). You must equip the remaining
slots with filler circuit packs. Filler circuit packs cannot be replaced with other
transport circuit packs (for example, XRs or WTs). Both ends of an optical link
where the 10 Gbit/s transmitters are T/R circuit packs must be either
TriFEC-capable or non-TriFEC circuit packs.
You can equip tributaries with no sequence restrictions when the deployed
10 Gbit/s line/MS circuit packs are TriFEC-capable. The Wavelength
Combiner circuit pack groups at both terminals must be originally equipped
with the same type of 10 Gbit/s transmitters (both TriFEC-capable or both
non-TriFEC). Failure in following this rule will probably cause a Protection
scheme mismatch or Channel ID mismatch alarm to be raised on the
subtending OC-48 or TN-16X equipment and cause subsequent protection
path failures.
For guidelines on sparing T/R circuit packs, refer to TriFEC hardware
capability for 10 Gbit/s T/R circuit packs on page 8-20.
For more information on possible combinations of supported tributary services
in a Wavelength Combiner circuit pack group, refer to Optical dedicated
protection ring (ODPR) application on page 5-1.
ATTENTION
You cannot use OC-192/STM-64 T/R circuit packs in extension shelf 2
(G22 and G27) to line time your network element.
Table 8-6 lists the supported G-name and slot positions for Wavelength
Combiner circuit pack groups.

Table 8-6
G-names and slot positions for Wavelength Combiner circuit pack groups
Circuit pack type

G-name(s)
Slot
number(s)
Shelf description
TD
G4
Main shelf
OC-48/STM-16 DWDM T/R (NTCA30xK)
G5, G6, G8,

G9
6, 7, 9, 10
Main shelf
OC-48/STM-16 T/R SR (NTCA30CK)
OC-48/STM-16 T/R (1310 nm) (NTCA30AL) G10,

G13,
Dual Gigabit Ethernet (NTCA90xA)
G15,
G18,
G11,
G14,
G16,
G19
1, 2, 4, 5, 6, 7, Extension shelf 1
9, 10
G20,
G23,
G25,
G28,
G21,
G24,
G26,
G29
1, 2, 4, 5, 6, 7, Extension shelf 2
9, 10
OC-192/STM-64 T/R (NTCA06xx)
G7
Main shelf
OC-192/STM-64 T/R TriFEC (NTCF06xx)
G12, G17
3, 8
Extension shelf 1
G22, G27
3, 8
Extension shelf 2
Note: Because of extension shelf 2 backplane limitations, the 10 Gbit/s T/R line/MS circuit packs in
extension shelf 2 (slots 3 and 8) cannot line time the network element.
Optical dedicated protection ring (ODPR) circuit pack groups

ODPR circuit pack groups can be equipped as follows:
slots 1 to 5 and slots 6 to 10 of the main shelf
Each ODPR circuit pack group contains five circuit packs as follows:
one optical switch module (OSM) circuit pack (NTCA39AA) and any four
of the same or a mix of the following circuit packs
OC-192/STM-64 XR/WT (NTCF04xx) circuit pack (traffic mode set
to REGEN for XR)
one OSM circuit pack (NTCA39AA) and any four of the same or a mix of
the following circuit packs
10G WT circuit packs (NTCA07xx)
10G WT SR (TriFEC) (NTWR07AA) circuit pack (off-ramp position
only)
OC-192/STM-64 XR/WT (NTCF04xx) circuit pack (traffic mode set
to 3R for WT)
Note 1: You cannot mix XR and WT circuit packs within an ODPR circuit
pack group. The traffic mode, XR or WT, for all circuit packs within an
ODPR circuit pack group must be the same.
Note 2: You can mix fixed wavelength, short-reach, provisionable traffic
mode, and TriFEC circuit packs. However, you must follow all thermal,
power, and engineering rules.
Note 3: The MX circuit pack is mandatory in slot 10 of the control shelf.
It is highly recommended to equip a second protection MX circuit pack
Table 8-7 lists ODPR circuit pack group G-naming positions.

Table 8-7
G-names and slot positions for ODPR circuit pack groups
Circuit pack type
G-name(s) Slot number(s) Shelf description
10G WT (NTCA07xx)
G0, G1,
G3, G4,
G5, G6,
G8, G9
1, 2, 4, 5, 6, 7, 9, Main shelf
10
G10, G11,
G13, G14,
G15, G16,
G18, G19
1, 2, 4, 5, 6, 7, 9, Extension shelf 1
10
G20, G21,
G23, G24,
G25, G26,
G28, G29
1, 2, 4, 5, 6, 7, 9, Extension shelf 2
10
G1, G4,
G6, G9
2, 5, 7, 10
Main shelf
G11, G14,
G16, G19
2, 5, 7, 10
Extension shelf 1
G21, G24,
G26, G29
2, 5, 7, 10
Extension shelf 2
G2, G7
3, 8
Main shelf
G12, G17
3, 8
Extension shelf 1
G22, G27
3, 8
Extension shelf 2
10G WT (TriFEC) (NTCF07xx) (see Note 1)

(see Note 3)

(see Note 1 Note 2, and Note 3)
Optical switch module (OSM) (NTCA39AA)
Note 1: You must follow thermal, power, and engineering rules. Refer to Thermal tool on page 9-24.
Note 2: FEC-capability is available on the receiver only. The transmitter is equipped with short-reach
optics.
Note 3: You cannot mix XR and WT circuit packs within an ODPR circuit pack group. The traffic mode,
3R or REGEN, for all circuit packs within an ODPR circuit pack group must be the same.
Circuit pack sparing and replacement

Definition of sparing
Sparing refers to replacing a circuit pack with another circuit pack (a spare)
without deprovisioning or deleting the original circuit pack or taking the
original circuit pack out-of-service.
In certain scenarios, for sparing to proceed, you must edit certain Optical
Facility parameters to clear provisioning mismatch alarms. After you clear the
alarms, you can use the new circuit pack.
Note: Sparing or replacement procedures are service-affecting if the
affected services are unprotected.
Optical Long Haul 1600 offers a flexible and dynamic sparing and circuit pack
replacement strategy.
Note: In case of uncertainty, spare circuit packs only with circuit packs
that have the same PEC.
As a general guideline, when you replace a circuit pack with a less capable
circuit pack, you are not restricted to the original circuit pack's capabilities,
except with legacy T/R circuit packs. However, when you replace a circuit
pack with a less capable circuit pack, two mismatch alarms are raised:
Circuit pack provision mismatch alarm
Facility provisioning mismatch alarm
These alarms are raised only if the new circuit pack does not support the
provisioned values. These mismatch alarms clear when you edit the new
circuit packs provisionable parameters (for example, Tx Wavelength or Tx
Output power). You must edit the new circuit packs provisionable parameters
to match its capable values. To view a circuit packs supported values, use the
query command in the Tx Optical Facility Menu.
ATTENTION
Editing the Tx Optical Facility settings can be traffic affecting.
A Mismatch field is included in the Tx Optical Facility and the OCn/STM-n
Facility screens. This field indicates mismatch values and identifies which
provisionable parameters require editing (with the exception of TMUX).
When no mismatches exist, the Mismatch field displays NONE.
Note: The Tx Optical Facility and the OCn/STM-n Facility screens only
include facility and related capabilities items that prevent a circuit pack
from running. Because FEC mismatches and section trace mismatches do
not prevent a circuit pack from running, these mismatches are not indicated
in the Mismatch field.
Table 8-8 lists mismatch values that can be displayed in the Mismatch field.
Table 8-8
Mismatch field values
Mismatch field
Description
NONE
No mismatch
Chirp
Tx Chirp provisioning
AM
Analog Maintenance provisioning
NLSDither
NLS Dither provisioning
Wavelength
Tx Output Wavelength provisioning
Power
Tx Output Power provisioning
TrafficMode
Traffic Mode provisioning
B1
B1 Mode provisioning
TMUX
TriFEC hardware incompatibility
The following sparing and replacement rules apply to 10 Gbit/s line/MS

capacity circuit packs and indicate the cause of the mismatch alarms (Circuit
pack provision mismatch and Facility provisioning mismatch).
Tx Wavelength
You can replace a fixed wavelength circuit pack with another fixed wavelength
circuit pack of the same wavelength. In this case, the new circuit pack
autoprovisions.
If the replacement circuit pack has a capable Tx Wavelength that is different
from the original circuit packs Tx Wavelength, then the Mismatch field
indicates Wavelength. In this case, you must edit the Tx Wavelength to
match the new circuit packs capable wavelength.
Tx Chirp, AM, and NLS Dither provisioning
When the replacement circuit pack does not have the same capabilities as the
original circuit packs provisioned settings, you must edit these transmitter
parameters: Tx Chirp, Analog Maintenance (AM), and NLS Dither.
For example, if you insert a replacement 10G WT SR (TriFEC) circuit pack
(NTWR07AA) in a slot originally equipped with a 10G WT (TriFEC) circuit
pack (NTCF07xx), then you must set the Tx Chirp, AM, and NLS Dither
parameters to NONE. You must also set the Tx Wavelength to Fixed.
Use Table 8-9 on page 8-21, Table 8-10 on page 8-22, and Table 8-11 on page
8-23 for all 10Gbit/s circuit pack replacement scenarios.

Tx Output Power
You can replace a 10G WT SR (TriFEC) circuit pack (NTWR07AA) with

another 10G WT SR (TriFEC) circuit pack. The 10G WT SR (TriFEC) circuit
pack autoprovisions. You do not need to reprovision the circuit pack manually.
The 10G WT SR (TriFEC) circuit pack (NTWR07AA) and the 10G WT
(TriFEC) circuit pack (NTCF07xx) are interchangeable. However, mismatch
alarms are raised. To clear the alarms, you must edit the mismatched
parameters to the new circuit packs capable range.
Note: You must set the Tx Output Power to Fixed on the 10G WT SR
(TriFEC) circuit pack to clear the Power mismatch.
Use Table 8-11 on page 8-23 for all Wavelength Translator circuit pack (10
Gbit/s line/MS capacity) replacement scenarios.
Traffic Mode
You can replace an OC-192/STM-64 XR circuit pack (NTCA04xx), 10G WT

circuit pack (NTCA07xx), or merged XR/WT circuit pack (NTCF04xx) with
a merged XR/WT circuit pack (NTCF04xx). You can spare a merged XR/WT
circuit pack with an OC-192/STM-64 XR circuit pack (NTCA04xx) or a 10G
WT circuit pack (NTCA07xx). If the traffic mode differs from the provisioned
traffic mode, mismatch alarms are raised. The Mismatch field indicates
TrafficMode. The alarms clear when you edit the Traffic Mode.
Use Table 8-9 on page 8-21, Table 8-10 on page 8-22, and Table 8-11 on page
8-23 for all circuit pack replacement scenarios.
B1 Mode
When you use a circuit pack that does not support the provisioned B1 setting
as a replacement circuit pack, the Mismatch field indicates B1. To clear the B1
mismatch, you must edit the mismatched parameter to the new circuit packs
capable setting.
TriFEC hardware capability
TMUX overhead shuffling capabilities are hardware-related and are not

provisionable.
Enhanced TMUX2 capable hardware is limited to the following circuit packs:
10G WT (TriFEC) (NTCF07xx)
TriFEC hardware capability for 10 Gbit/s T/R circuit packs
You can replace an OC-192/STM-64 T/R circuit pack (NTCA06xx) with

another OC-192/STM-64 T/R circuit pack (NTCA06xx). If necessary, you can
spare the OC-192/STM-64 T/R circuit pack with a TriFEC-capable
OC-192/STM-64 T/R circuit pack. However, the enhanced overhead
transparency available on the TriFEC-capable hardware is not implemented. If

you require the enhanced overhead transparency, you must delete and
reprovision the circuit pack.
You cannot replace a TriFEC-capable OC-192/STM-64 T/R circuit pack with
an OC-192/STM-64 T/R circuit pack (NTCA06xx). The Mismatch field
indicates TMUX. When the Mismatch field indicates TMUX, a TriFEC
hardware incompatibility exists. To clear the TMUX mismatch, you must
remove the unsupported replacement circuit pack.
Note: The Wavelength Combiner circuit pack groups at both terminal sites
must be originally equipped with the same type of 10 Gbit/s T/R circuit
packs (TriFEC-capable or non-TriFEC). Failure in following this rule will
probably cause a Protection scheme mismatch or Channel ID
mismatch alarm to be raised on the subtending OC-48 or TN-16X
equipment and cause subsequent protection path failures.
TriFEC hardware capability for 10 Gbit/s WT circuit packs
You cannot spare a 10G WT circuit pack (NTCA07xx) with a

10G WT SR (TriFEC) circuit pack (NTWR07AA), or a 10G WT (TriFEC)
circuit pack (NTCF07xx). A Circuit Pack Mismatch alarm is raised.
Use Table 8-10 on page 8-22 and Table 8-11 on page 8-23 for all
TriFEC-capable circuit pack replacement scenarios.
Table 8-9
Dense regenerator circuit pack replacement
Originally provisioned
circuit pack
Replacement circuit pack
OC-192/STM-64 XR
(NTCA04xx))
OC-192/STM-64 XR
(NTCA04xx)
Same :
Autoprovision
Same : Autoprovision
Different : Must edit

Tx Wavelength
OC-192/STM-64 XR/WT Same :
Autoprovision
(NTCF04xx)
(see Note 1 and
Note 2)
Different : Must edit

Tx Wavelength
Different : Must edit Tx Wavelength
Note 1: The Traffic Mode for the original OC-192/STM-64 XR/WT circuit pack is set to REGEN.
Note 2: If necessary, replace the original OC-192/STM-64 XR/WT circuit pack (traffic mode set to
REGEN for XR) with a 10G WT circuit pack. However, you must set the traffic mode to 3R for WT. See
Table 8-11 on page 8-23 for possible WT replacement circuit packs.

Table 8-10
Wavelength Combiner (line optics) circuit pack replacement
Originally provisioned
circuit pack
Replacement circuit pack (see Note 1)
OC-192/STM-64 T/R
(NTCA06xx)
OC-192/STM-64 T/R
(NTCA06xx)
Different : Must edit Tx Different : Must edit Tx Wavelength

Wavelength
(see Note 2)
OC-192/STM-64 T/R N/A

(TriFEC) (NTCF06xx) (see Note 3 and
Note 4)
Note 1: The Wavelength Combiner circuit pack groups at both terminals must be originally equipped
with the same type of 10 Gbit/s transmitters (TriFEC-capable or non-TriFEC). Failure in following this
rule will probably cause a Protection scheme mismatch or Channel ID mismatch alarm to be raised
on the subtending OC-48 or TN-16X equipment and cause subsequent protection path failures.
Note 2: The replacement circuit pack is only capable of single FEC or no forward error correction
(NONE). You can provision TriFEC on the replacement circuit pack only if you delete and then
reprovision the circuit pack. Before you delete a circuit pack, make sure you take note of all required
provisioning information (such as the transmit optical power, transmit wavelength, chirp setting, and
FEC setting). For instructions on deleting a circuit pack, refer to Provisioning and Operations
Note 3: A slot originally provisioned with NTCF06xx cannot be replaced by an NTCA06xx: a TMUX
mismatch alarm is raised.
Note 4: This replacement is accepted only if the TriFEC-capable circuit pack previously replaced the
NTCA06xx.

Table 8-11
Wavelength Translator circuit pack replacement
Replacement circuit pack
Originally provisioned circuit pack
10G WT
(NTCA07xx)
(no FEC)
10G WT (NTCA07xx)
(no FEC)
OC-192/STM-64
XR/WT
(NTCF04xx)
(no FEC)
10G WT
(TriFEC)
(NTCF07xx)
10G WT SR
(TriFEC)
(NTWR07AA)
(only Rx
FEC/TFEC)
Same :
Autoprovision
Same :
Autoprovision
N/A
N/A
(see Note 3)
(see Note 3)
N/A
N/A
(see Note 3)
(see Note 3)
Different : Must edit Different : Must

Tx Wavelength
edit Tx
Wavelength
OC-192/STM-64 XR/WT Same :

(NTCF04xx)
Autoprovision
(no FEC)
Same :
Autoprovision
10G WT (TriFEC)
(NTCF07xx)
N/A
N/A
(see Note 3)
(see Note 3)
Different : Must edit Different : Must

(see Note 1 and Note 2)
Tx Wavelength
edit Tx
Wavelength
Same :
Must edit all
Autoprovision mismatched
parameters
Different :
Must edit Tx
Wavelength
10G WT SR (TriFEC)
(NTWR07AA)
(only Rx FEC/TFEC)
N/A
N/A
(see Note 3)
(see Note 3)
Must edit all

mismatched
parameters
Autoprovision
Note 1: The traffic mode for the original OC-192/STM-64 XR/WT circuit pack is set to 3R for WT.
Note 2: If necessary, replace the original OC-192/STM-64 XR/WT circuit pack with an OC-192/STM-64
XR circuit pack. However, you must set the traffic mode to REGEN for XR. See Table 8-9 on page 8-21
for possible XR replacement circuit packs.
Note 3: TriFEC-capable circuit packs are not interchangeable with non-TriFEC circuit packs.
Circuit pack sparing and replacement rules for dual 2.5 Gbit/s WT circuit
packs
You can spare a dual 2.5 Gbit/s WT circuit pack only with the same type of
circuit pack. Specifically:
you can replace two single 2.5 Gbit/s WT circuit packs with one dual
2.5 Gbit/s WT circuit pack:
you must delete the single circuit pack first and then insert and
reprovision the new dual 2.5 Gbit/s circuit pack
you do not have to change the circuit packs at both ends of the link
(single and dual 2.5 Gbit/s WT interworking is supported, see
Interworking on page 3-5)
OPC definition and span of control

The operations controller (OPC) provides operations, administration,
maintenance, and provisioning (OAM&P) functionality in an Optical Long
Haul 1600 network. OPC capabilities include system administration, network
surveillance, and software management.
An OPC has a span of control. A span of control consists of the Optical Long
Haul 1600 network elements that can be directly controlled or monitored by a
single OPC (primary OPC only) or a pair of OPCs (primary and backup
OPCs). Normally, a span of control is monitored by a pair of OPCs.
The partitioned OPC (POPC) consists of three separate OPC circuit packs that
are installed together in the control shelf of an Optical Long Haul 1600
network element. The POPC is loaded with software that allows the POPC to
monitor Optical Long Haul 1600 network elements.
The OPC controller circuit pack installed in the control shelf communicates
with the maintenance interface (MI) circuit pack, the OPC storage circuit pack
and the OPC interface circuit pack (see Figure 8-3).
Figure 8-3
Communication between the partitioned OPC (POPC) and other circuit packs in the network
element
OTP0239
MI
SC
OPC-C
OPC-S
OPC-I
Circuit
Pack
MX G1
MX G2
Circuit
Pack
Circuit
Pack
Circuit pack equipped with a processor (TCS)
Maximum number of network elements in a span of control

The maximum number of network elements in a single span of control (SOC)
is 34. The maximum number of network elements in a DCC network is 150.
The network elements can be interconnected through the data communication
channel (DCC) or Ethernet. All of the nodes in a DCC network are visible to
the OPCs because of the Network Name Service. The Network Name Service
is a database on the OPC that stores network routing information and is
updated whenever a network element is removed or added to the system.
The OC-12, OC-48, OC-192, and Optical Long Haul 1600 network elements
require their own OPCs. The Optical Long Haul 1600 network elements must
be in a different OPC span of control from OC-12, OC-48, or OC-192 network
elements. The primary and backup OPCs in the Optical Long Haul 1600 span
of control must be located at opposite ends of the optical line/MS in network
elements that are configured in their span of control. This arrangement ensures
that all network elements are still visible in the event of a communication
failure.
Communication between the partitioned OPC (POPC) and other network
elements through optical fiber
The OPC controller circuit pack exchanges OAM&P messages with network
elements through the OSC. The OSC reproduces the SONET/SDH section/RS
and line/MS DCC information embedded in the SONET /SDH overhead of the
optical traffic.
At the receiving network element, the OSC optical signal is received by the
OSC circuit pack and DCC information is processed. The DCC then travels
over GraceLAN to the message exchange (MX) circuit pack, then over the
multi-master serial bus (MMSB) to the shelf controller (SC). The SC receives
the information, or retransmits the information downstream using the OSC
DCC to the adjacent network element.
Communication between the partitioned OPC (POPC) and independent
networks over the Ethernet DCC bridge
An Ethernet DCC bridge permits OAM&P messages to be exchanged between
Optical Long Haul 1600 networks that are not connected by optical fiber but
have network elements at the same site.
For example, two independent Optical Long Haul 1600 networks (see Figure
8-4), each with one network element at a common site, can be connected with
an Ethernet DCC bridge. The two independent networks are controlled by the
same OPC and are in the same span of control because OAM&P messages can
travel through the Ethernet DCC bridge.
The maintenance interface circuit pack is equipped with three 10Base-T

Ethernet ports on its faceplate. The maintenance interface Ethernet ports allow
DCC bridging between adjacent Optical Long Haul 1600 network elements.
Figure 8-4
Ethernet DCC bridge
NT22K08AA08 1600ASDF
NTCA42AA08 1600ASDF
NTCA42AA08 1600ASDF
OTP0240
Ethernet
DCC bridge
Network element 1
SC
MI
1234567890
SC
MI
MI
SC
Ethernet
backplane
connection
Ethernet
faceplate
connection
MI
1234567890
Ethernet
backplane
connection
SC
Network element 2
Location of the partitioned OPC (POPC) in a networks

The purpose of the OPC is to provide a centralized view and control point for
the network elements that are contained within its span of control. Therefore,
it is best for OPCs to be located near VT100-compatible terminals or
workstations. Because the OPC storage circuit pack uses a removable media
for data backups and software upgrades, the primary OPC should be located in
an accessible site.
Although a configuration can function with a primary OPC only, it is
recommended that a configuration has a primary and backup OPC for
maximum protection against system failures.
Rules for Optical Long Haul 1600 applications with one span of control
In an Optical Long Haul 1600 system with one span of control, the OPCs are
normally mounted in network elements at opposite ends of the network. This
configuration is the most reliable for all system failures. In the worst case, a
fiber cut or equipment failure can partition the span into two subsystems, each
under the control of one OPC (primary or backup). The backup OPC
automatically becomes active to control all network elements up to the failure
partition from its end. In this case, no network elements are isolated from an
OPC.
Rules for Optical Long Haul 1600 applications with multiple spans of
control
Because the maximum number of network elements in a single Optical Long
Haul 1600 span of control is 34, multiple spans of control are often necessary.
To optimize the placement of the OPCs in networks with multiple spans of
control, a planner must consider the following system characteristics.
Locate the OPCs on network elements within the span of control
The OPC can be located in a network element that is not in the span of control.
To optimize performance, this scenario must be avoided if possible because
this setup increases the length of the communications channel.
Equalize the size of spans of control
To optimize performance, it is recommended that you split network elements

in an Optical Long Haul 1600 network with multiple spans of control into
equally sized spans of control (see Figure 8-5). It is also recommended to avoid
having one span of control operating near capacity and the other containing
few network elements. Rearrange the spans of control so that both have an
equal number of network elements.
Figure 8-5
OC-192/TN-64X SOC overlay onto Optical Long Haul 1600 SOC
OTP0043
OPTera Long Haul 1600 1.x SOC

- Overlay onto OPTera Long Haul 1600 1.x Network
Maximum of 7 OSC spans*
On-ramp site
On-ramp site
Amplifier sites
Regeneration site
Amplifier sites
OPTera Long
OPTera Long
OPTera
Long
Haul
1600
OPTera
Long
Haul
1600
OPTera
Long
Haul
1600
Haul 1600
Haul 1600
REPEATERS
REPEATERS
REPEATERS
REPEATER
REPEATER
MOR Plus
Post
2.5G WT
MOR Plus
MSA
Pre/Post
MOR Plus
MSA
Pre/Post
2.5G/10G DWDM
MOR Plus
Pre/Post
XR
MOR Plus
MSA
Pre/Post
MOR Plus
MSA
Pre/Post
2.5G/10G DWDM
2.5G 10G
WT WT
MOR Plus
Pre
2.5G WT
10G feed
OC-192/TN-64X SOC
*Note: This EXTERNAL COMM limitation is required to support software download

for upgrades when section/RS DCC and line/MS DCC is not available. The
MOR Plus chain must be at the same MOR Plus software baseline link budget
engineering as specified in the MOR Plus SLAT and Upgrade Procedures,
OC-192/TN-64X
OC-192/TN-64X
323-1801-225.
ADM/LTE
ADM/LTE
Repeater network element limitations

This section describes limitations for the Optical Long Haul 1600 Repeater
network element.
Network reconfiguration
Limitations on network reconfiguration are as follows:
In-service add for extension shelf 1 (shelf ID: 3) is not supported. Although
all extension shelves are optional, it is recommended to have at least
extension shelf 1 installed from the start.
Optical layer interworking between OAS and Repeater is supported.
However, it is recommended that OAS network elements and other Optical
Long Haul 1600 network elements have separate SOCs.
External communications
Limitations on external communications are as follows:
A limit of seven nodes in link mode is recommended if only MOR Plus
amplifier OSC is available for upgrading (that is, full-fill Wavelength
Translator on a Repeater bay).
A maximum of 34 network elements within the same SOC is
recommended by the OPC.
Globalization
Limitations on globalization are as follows:
The OPC does not support mixed network element types (SONET/SDH)
in the same SOC.
Note: TL1 is not available for SDH network elements. TL1 is available
only for SONET network elements. The TL1 interface facility is not
required for the SDH market.
SDH block-based performance monitoring (PM) collection is supported

only as of Release 6.
The legacy OPCs located in OC-48, OC-12 and TN-16X shelves cannot be
used to control the Optical Long Haul 1600 network elements.
OW Public Switched Telephone Network (PSTN) functionality is not
supported when the network element is commissioned as SDH.
Network synchronization requirements

Nortel optical networks products comply with the network synchronization
requirements described in TA-NPL-000436, Digital Network Plan, Issue 1,
November 1986, Section 3.3.
Network element synchronization is required for Repeater network elements
equipped with Combiner circuit pack groups The external synchronization
interface (ESI) provides the most accurate timing source to timing distribution,
the OC-192/STM-64 high-speed optics, and tributaries.
The ESI supports external timing and line timing modes with Stratum 3
(+4.6 ppm) holdover capabilities. You can provision the timing mode. For
more information, refer to Chapter 7, Operations, administration,
maintenance, and provisioning (OAM&P).
The ESI circuit pack receives timing input from an external
building-integrated timing supply (BITS) source or OC-192/STM-64
high-speed optics. Dense Regenerator applications and Wavelength Translator
are through-timed and do not require ESI circuit packs. At least one
Wavelength Combiner circuit pack group in a system (or one ADM in a ring)
requires a BITS timing source. The other ADMs in the system can receiving
timing input from a BITS source or from another network element (line timed).
The ESI can also provide timing distribution to other equipment in the SONET
network.
Three types of ESI circuit packs are available:
NTCE44BA provides external inputs and outputs at 2.048 MHz (2 MHz)

for SDH systems. The NTCE44BA cannot operate with a 60 V power
supply. You cannot spare a defective NTCE44CA with an NTCE44BA
circuit pack. This circuit pack does not provide SSM to external outputs.
For more information on SSM, refer to Synchronization status messaging
(SSM) on page 7-39.
NTCE44CA provides external inputs and output at 2.048 MHz (2 MHz)
for SDH systems. This new ESI circuit pack can operate at 35 V to 75 V
and is dedicated for deployment in captive offices that use a 60 V power
supply. An NTCE44BA can be spared with an NTCE44CA circuit pack.
The NTCE44CA can also operate with 48 V power supply. This circuit
pack does not provide SSM to external outputs. For more information on
SSM, refer to Synchronization status messaging (SSM) on page 7-39.
NTCA44AA provides external inputs and outputs at the DS1 line rate
(1.5 Mbit/s) for SONET systems.
The two ends of a Combiner line can be provisioned with different ESI circuit
packs (such as in the case of cross-continental applications).
Stratum clocks
Stratum clocks are stable timing reference signals that are graded according to
their accuracy. American National Standards Institute (ANSI) standards define
four levels of stratum clocks. Table 8-12 shows the accuracy requirements of
the stratum clock levels.
Table 8-12
Required standard clock stratum
Stratum
Minimum accuracy
Minimum holdover stability
+1.0 x 10-11
Not applicable
+1.6 x 10-8
1 x 10-10 per day
+4.6 parts per million

(ppm)
+0.37 ppm during first 24 hours
+32 ppm
Not required
External synchronization interface internal clock specifications

The external synchronization interface (ESI) meets stratum 3 requirements and
is completely compatible with building-integrated timing supply (BITS) clock
applications. Table 8-13 provides the ESI specifications.
Table 8-13
ESI specifications
Condition
Specification
long-term stability
4.6 ppm
holdover stability
0.37 ppm (constant temperature for the range

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

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

Table 8-14
ESI interconnect characteristics
Parameter
Value
line code
Bipolar with 8 zero substitution (B8Zs) or

Alternate Mark Inversion (AMI)
frame format
Superframe (SF) or
Extended Superframe (ESF)
test load
100 ohms 5%, resistive
DS1 output AIS line rate
1.544 Mbit/s 32 ppm
Table 8-15
DS1 cable lengths for different LBO settings
LBO value
DS1 ABAM (608) cable
AT&T 1249C DS1 cable
Short
0 to 46 m (0 to 150 ft)
0 m to 30 m (0 ft to 100 ft)
Medium
46 to 137 m (150 to 450 ft)
30 m to 76 m (100 ft to 250 ft)
Long
137 to 200 m (450 to 655 ft)
76 m to 137 m (250 ft to 450 ft)
2 MHz timing interface specifications

The ESI timing reference input accepts 2 MHz signals and the timing
reference output provides a 2 MHz signal according to ITU-T
recommendations G.703 and G.813. Table 8-16 lists the 2 MHz ESI
interconnect characteristics.
Table 8-16
2 MHz ESI interconnect characteristics
Parameter
Value
impedance
75
rate
2.048 MHz 4.6 ppm
input return loss
15 dB
cable loss to input
0 dB to 6 dB at 2048 kHz
output voltage
0.75 V (minimum), 1.5 V (maximum)
Building-integrated timing supply

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

Performance: The indication of a master timing supply for each building
enhances the reliability of the timing distribution. The BITS minimizes the
number of synchronization links that enter a central office because the
BITS receives timing reference from outside the office.
Use of resources: Use of a BITS increases the quantity of acceptable
2 MHz or DS1-level interconnection. Use of a BITS allows services within
the office to share resources.
Operations: The BITS is location-dependent, not service-dependent.
Records for provisioning and maintenance purposes are easier to maintain
in the event of the introduction of new digital services.

As customer networks grow, synchronization status messaging (SSM)
increases in complexity. With the introduction of mesh and unprotected hub
networks, timing has become more complicated than in the past.
Figure 8-6 and Figure 8-7 show how timing loops can still occur despite the
use of SSM.
Although SSM decreases the chances of timing loops, it is recommended not
to use mixed provisioning in a ring system if the system includes one
externally timed network element. Mixed provisioning refers to external (ESI)
and internal (OC-n/STM-n).

Figure 8-6
Synchronization status messaging (QC=PRC-P)
OTP2678p
Active
timing
source
BITS source
QC = PRC-P
QC = PRC
QC = DUS
G7
Active
timing
source
G7
G12
G17
QC = PRC
QC = PRC
Network element B
Network element A
BITS is active timing reference in
timing generation group. Therefore,
the network element sends out PRC
as its current timing source QC on
all STM-64 lines.
OC-192/STM-64 (G7) line source is

active timing reference (with QC PRC).
This network element sends back
DUS to the network element that
it is line timing from G7.
Timing generation protection group

(Network element A)
G17 does not immediately detect

that it is also connected to the timing
source network element and therefore
does not send back DUS. Instead
G17 sends the current timing quality
of the network element, which is PRC.
Reference
BITS
OC-192/STM-64 (G7)
OC-192/STM-64 (G12)
QC
PRC
DUS
PRC
Timing generation protection group

(Network element B)
Reference
OC-192/STM-64 (G7)
OC-192/STM-64 (G17)
QC
PRC
PRC
Note: A change in QC takes approximately 6 seconds to be realised at both ends of a line.

Therefore, network element A already selects G12 as its new timing reference before
the new QC from the BITS source filters through the system.

Figure 8-7
Synchronization status messaging (QC=STU)
OTP2677p
BITS source
Timing loop
QC = STU
QC = PRC
QC = DUS
G7
Active
timing
source
G7
G12
Active
timing
source
G17
QC = DUS
QC = PRC
Network element A
When the QC of the BITS source
changes to STU (which is of lower
value than PRC), network element A
synchronizes to its best timing source.
The timing source comes from G12
(which is still receiving PRC). G12 then
sends back DUS to network element B
as this is its source of timing.
Network element B
This network element still receives
a timing source of quality PRC to G7
and therefore makes no changes in
its timing reference solution.
Note: A change in QC takes approximately 6 seconds to be realised at both ends of a line.

Therefore, network element A already selects G12 as its new timing reference before
the new QC from the BITS source filters through the system.
Ethernet Wayside
ATTENTION
You cannot provision the Ethernet Wayside circuit pack in an Optical
Amplifier Shelf (OAS) or an Amplifier (AMP) network element.
Ethernet Wayside provides a full duplex point-to-point, up to 2 Mbit/s Ethernet
link between Repeater network elements. The new Ethernet Wayside circuit
pack is supported on Repeater network elements. You can provision a
maximum of two Ethernet Wayside circuit packs in each bay. The Ethernet
Wayside circuit packs are supported in slots 16 and 17 of the control shelf in a
Repeater bay.
Figure 8-8 shows the positioning of the Ethernet Wayside circuit pack in the
control shelf of the Repeater network element.
Figure 8-8
Ethernet Wayside circuit pack positioning
OTP2572p

4
9 10 11 12 13 14 15 16 17
EW
EW
OW
PT
PT
POPI
MX
MX
128M MI
ESI
ESI
32M SC
Control
shelf
POPC
POPS
2
Breaker filters
1
Breaker filters
Slot
number
G4
The Ethernet Wayside circuit pack communicates with MOR/MOR Plus

amplifier circuit packs or the 1625 nm optical service channel (OSC) through
the backplane for transmitting and receiving Ethernet traffic over the OSC.
These circuit packs are supported in slots 1, 2, 3, and 4 (G0, G1, G2, and G3,
respectively) on the main shelf of the bay.
For more information on MOR/MOR Plus amplifier equipping rules, refer to
the 100 GHz, MOR/MOR Plus, 2 to 32- Optical Layer Applications Guide
(NTY312DX).
Figure 8-9 shows Ethernet Wayside circuit pack configurations within the
control shelf.

Figure 8-9
Ethernet Wayside configurations
G0 G1 G2 G3
MOR Plus
MOR Plus
MOR Plus
G6
MOR Plus
MOR Plus
MOR Plus
MOR Plus
G5 G6
MOR Plus
MOR Plus
MOR Plus
G5
G0 G1
Filler circuit pack

EW
EW
EW
EW
Filler circuit pack
OTP2573p
G0 G1 G2 G3
OSC
OSC
OSC
OSC
Considerations for Ethernet Wayside network configuration
The following figures show several network configurations available for

interconnecting Ethernet Wayside circuit packs. If more than two network
elements are connected to create the Ethernet Wayside network, two Ethernet
Wayside circuit packs are required in each intermediate network element.
For end-to-end connectivity, the two Ethernet Wayside circuit packs are
interconnected through the external 10Base-T ports using one of the following
options.
Connect the circuit packs using the Ethernet hub available on the faceplate
of the Ethernet Wayside circuit pack. The hub on each circuit pack has four
ports, which makes three ports available for connecting other host station
equipment (see Figure 8-10). This option is the simplest and most
cost-effective method for a small network with low levels of traffic
volume. Any section of the Ethernet Wayside network connected using
hubs must be linear (no loops for Ethernet Wayside traffic) to avoid
broadcast storms. For larger networks or networks with higher traffic
volumes, routers or bridges are recommended.
The use of an external bridge requires at least a three-port bridge, two ports
for the Ethernet Wayside circuit packs and one for the LAN segment (see
Figure 8-11). For this option, all host devices connected to the bridges are
on the same IP network. All host devices are on the same broadcast
domain. No routers are required to send traffic from one host to the other.
The use of an external router requires at least a three-port router, two ports
to interconnect the Ethernet Wayside circuit packs and one port to connect
to the LAN (see Figure 8-12). Each router interconnects different IP
networks to the Ethernet Wayside WAN.
Combinations using the options described in this section are also possible.
Figure 8-10
Network element interconnection through hubs
OTP2574p
Network element
Ethernet
Wayside
Network element
Ethernet
Wayside
Ethernet
Wayside
Network A
Network element
Ethernet
Wayside

Figure 8-11
Network element interconnecting through bridges
OTP2575p
Network element
Network element
Ethernet
Wayside
Ethernet
Wayside
Ethernet
Wayside
Bridge
Network element
Ethernet
Wayside
Bridge
Bridge
Network A
Figure 8-12
Network element interconnection through routers
OTP2576p
Network element
Ethernet
Wayside
Router
Network A
Network element
Ethernet
Wayside
Ethernet
Wayside
Router
Network B
Network element
Ethernet
Wayside
Router
Network C
Ethernet Wayside does not dictate the use of a particular network

configuration. Ethernet Wayside circuit packs are configured as a linear
system or as a loop. In an Ethernet Wayside network linear configuration, two
Ethernet Wayside circuit packs are used in each intermediate node to ensure
end-to-end Ethernet Wayside traffic continuity. The end network elements
require one Ethernet Wayside circuit pack each. The loop network provides
route diversity. In a ring network, at least one router or bridge must exist to
break the loop so traffic does not indefinitely move across the ring. When
different routes exist (for example, a ring), the router/bridge determines the
best path to the final destination.
Ethernet Wayside engineering rules
The Ethernet Wayside circuit packs are provisioned in the optional slots 16 and
17 (G5 and G6) of the control shelf (see Figure 8-8 on page 8-36) in the
Repeater network element.
You must manually configure the circuit packs to transmit/receive data
through MOR Plus/MOR OSC or MOR Plus/MOR Plus OSC transmit/receive
pairs (see Figure 8-13). You cannot connect Ethernet Wayside circuit packs to
any other circuit pack in the network element.

Figure 8-13
Ethernet Wayside circuit packs in a Repeater network element
OTP2578t
Ethernet 10Base-T west port
Control
shelf
Main
transport
shelf
Ethernet 10Base-T east port
Ethernet
Wayside
circuit pack
Ethernet
Wayside
circuit pack
G5
G6
MOR Plus
circuit pack
MOR Plus
circuit pack
pair
pair
OSC west
OSC east
Note: Figure 8-13 is for reference only and does not represent the physical
location of the Ethernet Wayside circuit packs and MOR Plus amplifier
circuit packs in a Repeater network element.
Figure 8-13 shows that a single Ethernet Wayside circuit pack is dedicated to
a single optical link (for example, eastbound or westbound). A second Ethernet
Wayside circuit pack must be used to access a second link if two links are
required to connect an external router or bridge.
Ethernet Wayside circuit pack sparing
You can spare an Ethernet Wayside (NTCA56AA) circuit pack only with
another Ethernet Wayside circuit pack.
For a detailed set of rules on Ethernet Wayside, refer to the Ethernet Wayside
The following engineering rules apply to the strong authentication feature:
This feature is optional and requires a special license to be deployed with
Optical Long Haul 1600 software. You must install and configure
third-party software (for example, RSA Security ACE/Server or
BaySecure Access Control) according to the manufacturers instructions.
You must then provision the client database with the IP address or
hostname of the OPCs.
You must install the ACE/Server authentication server software on a Sun
Solaris, HP-UX, or Windows NT workstation with TCP/IP connectivity to
the OPCs acting as RADIUS authentication clients.
The usability of RADIUS/SecurID authentication on the OPC and network
elements depends on low network latency between the server and clients.
As a result, you must follow these guidelines when configuring the
authentication server.
The Solaris, HP-UX, or Windows NT workstation running the
ACE/Server software must not be used for any other resource-intensive
application such as Optical Network Management (formely known as
Preside).
The ACE/Server and the RADIUS server software must be able to
coexist on the same workstation because the RADIUS server forwards
authentication requests to the ACE/Server.
The workstations running the authentication server software must
have a high-speed and low-latency connection directly to its client
OPCs.
The TCP/IP traffic between the OPCs and local area network (LAN)
where the authentication servers are located must not be tunnelled over
SONET/SDH DCC or transmitted over low-speed links such as
TCP/IP over X.25.
The authentication servers must be on a network protected by a firewall
from unauthorized external access.
To increase security robustness, a primary OPC and a backup OPC (in
warm stand-by) act as primary and backup RADIUS proxies.
Auto login functionality is not available for users configured with
RADIUS-local authentication. The system cannot store the users
passcode for later use.
OPC provisioning requirements

The following OPC tools allow the system administrator to provision the
strong authentication feature:
OPC Servers Configuration File (rsa_server)
OPC Users Configuration File
Note: At the network element level, no provisioning requirements are
necessary to support the strong authentication feature. The authentication
method (local or RADIUS-local) and the local password are automatically
sent from the OPC to the network elements in the OPC span of control. The
primary and backup OPCs act as primary and backup RADIUS proxies for
the network elements.
OPC Servers Configuration file
For the RADIUS-local authentication to work, the system administrator must

correctly commission the OPC Servers Configuration file.
The OPC Servers Configuration file is a plain text file that contains the
following information:
addresses of the primary and backup authentication servers
The addresses can be either a host name (as defined in the /etc/hosts file)
or an IP address. The backup authentication server is optional but strongly
recommended. Only one backup authentication server is supported.
RADIUS password (shared Secret) of the RADIUS client
The password is encrypted with a reversible encryption algorithm and
encoded in base-64 format 2.
Figure 8-14 shows an example of the OPC Servers Configuration file.
Figure 8-14
OPC Servers Configuration file
OTP2265t
# sample servers file - this is a comment line

# primary
radserv1
backup
password
radserv2
Rt5e9xoPqh2U3tv5RPxf2o3
This file is created with a command-line tool on the OPC. The system
administrator must create this file when the strong authentication feature is
first enabled.
The OPC Servers Configuration file can survive restarts and reboots, and work
for the OPC restoration. This file does not affect network upgrades and
software downloads. The active OPC transfers this file to the inactive OPC
during the datasync operation.
OPC users configuration file
The OPC users configuration file is a plain text file that contains the following
information:
user IDs for both Centralized User Administration (CUA) users and
special users (special users defined in the etc/passwd file but not in CUA
database)
authentication method for each user (local or RADIUS-local)
Figure 8-15 shows an example of the OPC Users Configuration file.
Figure 8-15
OPC users configuration file
OTP2266t
# sample servers file - this is a comment

# userID
authentication method
admin
RADIUS-Local
root
Local
The system updates the OPC Users Configuration file automatically when user
data is updated in the CUA tool. Information about special users not included
in the CUA database (for example, root user) is retrieved from the UNIX
/etc/passwd file when the RADIUS software is first installed. The system
administrator can change the authentication type for special users by editing
this file. Optical Long Haul 1600 software includes a command-line tool for
use during the initial software installation.
The RADIUS server file can survive restarts and reboots, and work for the
OPC restoration. This file does not affect network upgrades and software
downloads. The active OPC transfers this file to the inactive OPC during the
datasync operation.
For more information on the OPC tools and procedures to provision the strong
authentication feature, refer to Security Management Procedures,
323-1801-305.

Open access orderwire uses the MOR Plus bidirectional OSC circuit pack as
the transport medium for providing a conference bridge connection between
two Repeater network elements.
Up to two orderwire connections are currently available and the software is
ready to provide up to six orderwire connections.
The orderwire circuit pack, with its associated software functionality, provides
voice frequency communication between Optical Long Haul 1600 network
elements using the following:
orderwire interfaces present on the local craft access panel (LCAP)
orderwire circuit pack faceplate
Orderwire is normally used during maintenance activities, when craftspeople
at two sites must communicate to plan their actions and confirm diagnostic
results.
The orderwire circuit pack is optional and is equipped in slot 15 (G4) of the
control shelf in a Repeater network element (see Figure 8-16). The presence or
absence of the orderwire circuit pack does not affect any aspect of the Repeater
network element operation except for the orderwire functionality.
Figure 8-16
Orderwire circuit pack positioning
OTP2577t

4
9 10 11 12 13 14 15 16 17
EW
EW
OW
PT
PT
POPI
MX
MX
128M MI
ESI
ESI
32M SC
Control
shelf
POPC
POPS
2
Breaker filters
1
Breaker filters
Slot
number
G4
Local and express orderwire is accessed over the optical service channel
(OSC) supported on MOR Plus amplifiers in slots 1 through 4. Orderwire is
provided through a fixed pairing of two pairs of circuit packs: 1 pair for
eastbound and 1 pair for westbound, configured as Pre/Post amplifiers located
in the Repeater bay main shelf.
To configure orderwire on a Repeater network element, equip two to four
MOR Plus amplifier circuit packs in the main shelf for each node.
The MOR Plus amplifier circuit packs are configured as follows:
G0 and G3 (slots 1 and 4) provisioned as Red Pre/Blue Post or Red MSA
Pre/Blue MSA Post
G1 and G2 (slots 2 and 3) provisioned as Red Post/Blue Pre or Red MSA
Post/Blue MSA Pre
The OSC pairing of the MOR Plus amplifier circuit packs is as follows:
West OSC: slot 1 and 2 (MOR Plus G0 and G1)
East OSC: slot 3 and 4 (MOR Plus G2 and G3)
The two MOR Plus amplifier circuit packs that contain OSC capabilities to
achieve bidirectional OSC functionality are as follows:
one MOR Plus amplifier circuit pack to achieve 1510 nm OSC in one
direction
one OSC plug-in module to achieve the 1625 nm OSC in the other
direction
Figure 8-17 shows MOR Plus amplifier circuit packs with OSC functionality.

Figure 8-17
MOR Plus amplifier circuit packs with OSC functionality
OTP0037
Control shelf
OW
RB Main shelf
OSC
West facing
Rx
Tx
Tx
Rx
Slot 1
Slot 2
Slot 3
Slot 4
G0
MOR
Plus
G1
MOR
Plus
G2
MOR
Plus
G3
MOR
Plus
Overhead
buses
OSC
East facing
Manual seam
Open access orderwire circuit pack sparing
You can spare an open access orderwire (NTCA47AA) circuit pack with
another open access orderwire circuit pack (NTCA47AA). Refer to the
Ordering Guide (NTY311KL) for detailed engineering rules.
Note: The NTCA47BA Orderwire circuit pack provides access to two 64
Kbit/s channels for voice communications between network elements.
This OW circuit pack extracts the voice data from the optical service
channel (OSC) and provides both local (LOW) and express (EOW)
communications on 1600G Amplifier systems. This circuit pack only
operates with Optical Long Haul 1600 Release 7 or later releases.
Interworking between the NTCA47AA Orderwire circuit pack and
NTCA47BA Orderwire circuit pack is supported but only LOW access is
supported.For more information about the orderwire functionality
provided by the NTCA47BA circuit pack, refer to the Optical Long Haul
1600/Optical Connect DX/TN-64X Orderwire User Guide, (NTY313HX).
For a detailed description of orderwire and its implementation in the network,
refer to the SONET Orderwire User Guide (NTCA66CA) or the SDH
Orderwire User Guide (NTCA66DA).
9-1
9-
Chapter overview
This chapter provides the environmental, physical, and safety issues that you
must consider to install and operate an Optical Long Haul 1600 Repeater
network element at your site.
Note: For more information on specifications for the Amplifier network
element, refer to 1600G Amplifier Unidirectional Network Application
Guide (NTY314AL).
Section
Page
Safety specifications
9-2
Site engineering
9-3
Mechanical bay assembly specifications
9-4
Operational environment
9-6
Electromagnetic compatibility
9-9
Parallel telemetry output relay rated capacity
9-12
Floor loading
9-12
Thermal loading
9-13
Power requirements
9-13
Power distribution
9-14
Power installation requirements
9-15
Circuit pack power estimates
9-23
Thermal tool
9-24
Custom applications
9-31
9-2 Mechanical specifications
Table 9-1 indicates the safety regulations applicable to the Optical Long
Haul 1600 system.
Table 9-1
Discipline
Applicable country or region
Regulatory and
industry
specification
Key customer
requirement
Regulatory safety
USA
UL1950
Regulatory safety
Canada
CSA, C22.2 No. 950
Regulatory safety
Europe
EN 60950
Regulatory safety
International
IEC 60950
Laser safety
USA and Canada (Laser), Regulatory
FDA 21 CFR
Laser safety
International/Europe (Laser), Regulatory
IEC/EN 60825-1,
IEC/EN 60825-2
Product safety
RBOC serving locations within USA
Telcordia
GR-1089
GR-63-Core
GR-78
Mechanical specifications 9-3
Site engineering
The Optical Long Haul 1600 system meets the network equipment building
system (NEBS) standard six-bay line-up floor plan for 305 mm (12 in.) deep
equipment. This layout provides a maintenance aisle and a wiring aisle (see
Figure 9-1).
Figure 9-1
Optical Long Haul 1600 standard floor plan
OTP0278
Bay
lineup
12 in.
(305 mm)
15 in.
(381 mm)
Maintenance aisle
12 in.
(305 mm)
Universal
frame
12 in.
(305 mm)
26 in.
(660 mm)
Bay
lineup
Wiring aisle
15 in.
(381 mm)
DWDM
passive bay
35.4 in.
(900 mm)
Bay
lineup
VFO
Universal
frame
VFO
Maintenance aisle
35.4 in.
(900 mm)
Note 1: The DWDM passive bay footprint is 1.5 times the width of the
OPTera Long Haul 1600 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
26 in. (660 mm) for ANSI installations and 600 mm (23.6 in.) for ETSI installations.
Bear in mind the dimensions of the DWDM passive bay (35.4 in. or 900 mm), if
applicable.
Maximum Ethernet cable length

The maximum cable length allowed for Ethernet connections is 100 m
(330 ft).

Table 9-2 describes the mechanical dimensions of an Optical Long Haul 1600
network element.
Table 9-2
Bay frame
Width
598 mm
(23.62 in.)
Height
2125 mm
(83.66 in.)
Depth
298 mm
(11.73 in.)
Weight
49.89 kg
(110 lb)
Clearance between uprights
502 mm
(19.76 in.)
Vertical mounting centers
25 mm
(0.98 in.)
Horizontal mounting centers
515 mm
(20.27 in.)
Maximum base height
118 mm
(4.645 in.)
Optical Long Haul 1600 control shelf (including LCAP)

Width
495 mm
(19.5 in.)
Height
500 mm
(19.7 in.)
Depth
280 mm
(11.0 in.)
Width (without mounting flanges)
495 mm
(19.5 in.)
Height
88.14 mm
(3.47 in.)
Depth
240.5 mm
(9.47 in.)
Width
495 mm
(19.5 in.)
Height
367 mm
(14.462 in.)
Depth
280 mm
(11.0 in.)
Width
500 mm
(19.68 in.)
Height
74.98 mm
(2.95 in.)
Depth
215 mm
(8.47 in.)
Fiber management trays
Optical Long Haul 1600 main shelf
Environmental control panel (ECP)

Optical Long Haul 1600 extension shelf 1 and 2
Width
495 mm
(19.5 in.)
Height
367 mm
(14.462 in.)
Depth
280 mm
(11.0 in.)
Frame equipment
The Optical Long Haul 1600 bay is built using a 2.125 m (6 ft 11.64 in.)
front-access universal frame. Frame extenders are optional and 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
necessary attachment screws
A standard equipped Optical Long Haul 1600 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.
Table 9-3 outlines the operating environment envelope.
Table 9-3
Attribute
Normal operating
temperature (see Note
1)
Short term operating
temperature (see Note
1 and Note 2)
Normal operating
humidity (see Note 1)
Condition
Test method and specifications
5 C to 40 C,
USA: Telcordia (formerly known as Bellcore)

NEBS GR-63-CORE
5% to 85% relative humidity
Bell Canada: DS 8161

5 C to 50 C
Brazil: 240-600-702, 240-600-703

Europe: ETSI 300 019-1-3:1992
but not greater than
Taiwan: Specification for Toll Switching System
0.024 kg water/kg of dry air
British Telecom: BT RC 5000P
Short term operating

humidity (see Note 1
and Note 2)

but not greater than
0.024 kg water/kg dry air
Temperature cycling
5 C to 50 C
at 30 C per hour
Brazil: 240-600-702, 240-600-703

NEBS GR-63-CORE
Europe: ETSI 300 019-1-3:1992 Class 3.1
Operational altitude
4000 m above sea level
Brazil: 240-600-702, 240-600-703

NEBS GR-63-CORE
Acoustic noise
60 dBA

NEBS GR-63-CORE
Acoustic noise
contour of constant
loudness, index 1.99
UK: British Telecom RC 5000P; BS 4198 1967
Airborne contaminants
Thermal loading
(per office floorspace)
Earthquake/seismic

NEBS GR-63-CORE
1.94 kW/m2 or
180 W/ft2

NEBS GR-63-CORE
Zone 4

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

NEBS GR-63-CORE

Attribute
Operational vibration
Condition
Europe: ETSI 300 019-1-3: 1992 Class 3.1;

IEC 68-2-6 test Fc
NEBS GR-63-CORE
Microphonic shock
100 g point impulse as

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

Optical Connect DX meets the storage and transportation requirements of
Brazil, Europe and USA.
Table 9-4 outlines the storage and transportation environment envelope.
Table 9-4
Attribute
Temperature
Condition
50C to 70C, 72 hour

duration at each temperature
extreme.
Brazil: 240-600-702, 240-600-703

NEBS GR-63-CORE
Humidity
up to 98% R.H.
(non-condensing) or 4.0 kPa
water vapor pressure
(whichever is less)
Europe: ETSI 300 019:1992 Class 1.2/2.3
High temperature
thermal shock
25C to 70C in less than 5

minutes

NEBS GR-63-CORE
Low temperature
thermal shock
25C to 40C in less than 5

minutes
High humidity cyclic

test
1C to 28C at 95% relative

humidity

NEBS GR-63-CORE
Europe: ETSI 300 019-1-2:1992 Class 1.2/2.3,

IEC 68-2-6 test Fc
Shipping vibration

NEBS GR-63-CORE

Attribute
Condition
Installation drop
(systems)
Handling drop
(palletized)
Europe: ISO 2244
Handling drop
(packaged)
Servicing drop (topple)
Europe: IEC 68-2-31 test Ec
Servicing drop
(free fall)
Shock fragility
Europe: IEC 68-2-27 test Ea
Bounce-transportation
Europe: IEC 68-2-55
horizontal
Air shipment

NEBS GR-63-CORE

NEBS GR-63-CORE

NEBS GR-63-CORE Issue 1 Oct. 1995
Altitude
The Optical Long Haul 1600 network element is designed to operate up to
4000 m (13 000 ft) above sea level. Restrictions apply for altitudes above
1830 m (6000 ft), in which case the specified operating temperature range
must be derated by a factor of 2C (3.6F) for every 305 m (1000 ft) up to
4000 m (13 000 ft).
Atmospheric dust
The Optical Long Haul 1600 shelves do not require air filters. The enclosed
construction of circuit packs equipped in the main shelf permits forced air
cooling operation without air filters and associated maintenance. This method
of construction eliminates the risk of airborne contaminants reaching the
electronic components of the circuit packs. The dust contaminants, if allowed
in quantity on the electronic components, would otherwise reduce cooling and
potentially induce hardware/intermittent faults.
The equipment remains operational and is subject to the requirements of
Telcordia (formerly Bellcore) TR-NWT-000063, Issue 5, September 1993,
Section 4.6, Airborne Contaminants.
Mechanical shock and vibration

The Optical Long Haul 1600 network element meets mechanical robustness
requirements for normal transportation, service handling, shock robustness,
operational vibrations and earthquakes. The tests shown in the following tables
are deemed suitable to verify these requirements.
Shock
The product is fully compliant with Telcordia (formerly Bellcore)

GR-63-CORE, Issue 1, October 1995 specifications in sections 4.3.1.2 and
4.3.2 and test methods in sections 5.3.1 and 5.3.2 (see Table 9-5).
Table 9-5
Shock specifications
Condition
Specification
Packed for shipment
Drop height 609 mm (24 in.) or 762 mm (30 in.) dependent on weight
Unpacked (at installation)
Drop height 76 mm (3 in.) or 102 mm (4 in.) dependent on weight
Vibration
The product is fully compliant with Telcordia (formerly Bellcore)

TR-NWT-000063, Issue 5, September 1993, specification in sections 4.4 and
5.6.4 (refer to Table 9-6).
Table 9-6
Vibrational specifications
Condition
Specification
Operating environment
0.1 g from 5 to 100 Hz at 0.1 oct/min
Non-operating environment (shipping) 5 to 50 Hz at 0,5 g and 0.1 oct/min and

50 to 500 Hz at 3 g and 0.25 oct/min
Transportation bounce
The product is tested on a truck bed simulator, according to test method IEC
Draft 68-2-55.
Earthquake
The equipment remains operational when subjected to floor response spectra

simulating Zone 4 earthquake loading and mounted in a Nortel frame. The
product is compliant with Telcordia (formerly 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 Optical
Long Haul 1600 network element.
Emissions
Electromagnetic interference (EMI) emission requirements are intended to
minimize the interference of spurious EMI from the Optical Long Haul 1600
system to other electronic devices.
Radiated
When installed in its maximum worst-case reasonable configuration, the

Optical Long Haul 1600 product meets the radiated emission requirements of
the following specifications:
FCC Part 15B, Class A
EN55022, Class A
Telcordia (formerly Bellcore) GR-1089-CORE, Class A
ICES-003, Class A

Conducted
When installed in its maximum worst-case reasonable configuration, the

Optical Long Haul 1600 product meets the conducted emission requirements
(power and signal cables) of the following specifications:
Telcordia (formerly Bellcore) GR-1089-CORE, Class A
Telcordia (formerly Bellcore) GR-499, Issue 1
Bell Canada DS 8171
ETSI 300 132-2
Susceptibility/Immunity
Radio frequency immunity (RFI) requirements are intended to ensure a high
degree of robustness to electromagnetic disturbances from other electronic
devices and radio-wave transmissions.
Radiated
The Optical Long Haul 1600 product meets the radiated immunity
requirements of the following specifications:
Telcordia (formerly Bellcore) GR-1089-CORE
Bell Canada TAD 8465
EN300 386-2
EN 50082-1
Conducted
The Optical Long Haul 1600 product meets the conducted immunity
requirements of the following specifications:
Telcordia (formerly Bellcore) GR-499
EN300 386-2
ETSI 300 132-2
EN 50082-1
Electrostatic discharge and electrical fast transient
Electrostatic discharge (ESD) requirements are intended to ensure a high
degree of robustness to broadband electromagnetic disturbances from ESD
events on the Optical Long Haul 1600 system or within close proximity.
Electrical fast transient (EFT) requirements ensure a high degree of robustness
to conducted transients on cables.

Electrostatic discharge
The Optical Long Haul 1600 product meets the following specifications up to
15 Kv (air discharge, direct) and 8 Kv (contact discharge, direct and indirect)
with no errors or malfunction:
EN 300 386-2
EN 50082-1
EN 61000-4-2 (formerly IEC 801-2)
Electrical fast transient
The Optical Long Haul 1600 product meets the following specifications up to
Level 3 (2 Kv power, 1 Kv signal) with no errors or malfunction and
automatically recover, without damage, up to Level 4 (4 Kv power, 2 Kv
signal):
ETSI 300 386-2
EN 61000-4-4 (formerly IEC 801-4)
EN 50082-1
Parallel telemetry output relay rated capacity

Each form-C output relay contact is rated at 120 V ac (110 V dc) at 1 A. Each
output is a three-signal set supplied by a relay with a common connection
(COM) grouped with a normally open contact (NO) and a normally closed
contact (NC).
Floor loading
Table 9-7 shows the maximum total weights of fully filled mechanical bay
assemblies for the supported Optical Long Haul 1600 applications. Given a
300 mm (11.81 in.) deep frame, the recommended Telcordia (formerly
Bellcore) occupied floor area is 0.65 m2 (7.04 ft2).
The Telcordia (formerly Bellcore) standard GR-63-CORE Issue 1, October
1995 requirement states that the total floor load for the specified area including
overhead cables, light fixtures and transient loads supported by the equipment
frame must not exceed 735 kg/m2 (150.6 lb/ft2).
Table 9-7
Maximum total weights for filled network elements
Configuration
Maximum weight
Floor loading
Amplifier
331.80 kg (731.5 lb)
510.5 kg/m2 (103.9 lb/ft2)
Repeater
369.5 kg (814.5 lb)
568.4 kg/m2 (115.7 lb/ft2)
Thermal loading
The Optical Long Haul 1600 bay is a forced-air cooled, free-standing frame.
The bay is 300 mm (11.81 in.) deep. The Telcordia standard (formerly
Bellcore) GR-63-CORE Issue 1, October 1995 heat release objective is
1950 W/m2 (181.2 W/ft2).
The Optical Long Haul 1600 bay heat dissipation depends on the
configuration. Table 9-8 shows the maximum thermal loading for a fully
equipped Optical Long Haul 1600 bay, given a Telcordia specified occupied
floor area of 0.65 m2 (7.04 ft2).
For the thermal loading specifications of an Optical Long Haul 1600G
Amplifier network element, refer to the 1600G Amplifier Unidirectional
Network Application Guide (NTY314AL).
Table 9-8
Maximum power dissipation and thermal density for Optical Long Haul 1600 mechanical bay
assemblies
Configuration
Maximum power dissipation

(fully equipped configurations)
Thermal density
Repeater
3541 W
5448 W/m2 (503 W/ft2)
Note: The sum of all Optical Long Haul 1600 circuit pack typical power values is increased by 10
percent to obtain the maximum power dissipation.
Power requirements
Table 9-9 lists all the requirements related to the powering of an Optical Long
Haul 1600 network element.
Table 9-9
Power requirements
Battery voltage requirements
Range
40 V dc to 60 V dc
Battery step change during end wall switching
5 V step @ 5 V/ms
Note: The Optical Long Haul 1600 system meets safety and regulatory
requirements within an operating voltage range from 40 V dc to 60 V dc. The
system is capable of functioning up to 75 V dc, but is not safety compliant above
60 V dc.
Power distribution
Redundant feeds power the Optical Long Haul 1600 system. Failure of one
power feed because of an open or short circuit does not affect the system. Two
breaker/filter modules provide power for the Optical Long Haul 1600 shelves.
Refer to Figure 9-2 on page 9-15 for breaker assignment.
The A side and the B side can have separate power supplies. See Table 9-10
for the acceptable voltage difference between the two power supplies.
Table 9-10
Power distribution
Measured voltage across
Acceptable range
A (48) and A (RET)
40 V to 60 V
B (48) and B (RET)
40 V to 60 V
A (48) and B (48)
05V
A (RET) and B (RET)
0 0.1 V
Each breaker/filter module is connected to the three parallel battery feeds

located in the power termination area, as shown in Figure 9-2 on page 9-15.
Breaker/filter modules distribute power to the three parallel battery feeds
located in the power termination area. The control shelf houses the circuit
packs in slots 1 and 2: one circuit pack for battery A power feeds and one
circuit pack for battery B power feeds. You must have both circuit packs to
achieve power redundancy.

Figure 9-2
Optical Long Haul 1600 power distribution and circuit breaker assignment (one battery feed)
OTP0241
(-)
A3
(-)
A2
(-)
A1
-48V connections on external power

termination, at top of the bay
1
3 - 17
Control shelf
2
1-5
Main shelf
2
6 - 10
3
1-5
Extension shelf 1
3
6 - 10
4
1-5
Extension shelf 2
4
6 - 10
Note: Fan power is provided by internal fuses located in the breaker/filter module.
Power installation requirements

Office power terminations are fastened to the control shelf with lugs. All
power distribution is contained within the bay, shelves, and frames. Power
wires are not externally accessible to protect power distribution from
accidental cuts or shorts.
For detailed information on the installation of the universal power supply, refer
to Installation Procedures, 323-1801-201.
The configurations presented in this section are based on the following

assumptions:
Ambient temperature for short-term operation does not exceed 40C at
1800 m altitude or 45C at sea level.
The conditions for bay powering were calculated for the dual power fault
scenario. For the dual power fault scenario, the low battery voltage of the
point-of-use power supply (PUPS) on the circuit packs is used (32 V dc),
and one power feed, either feed A or feed B, is not in operation. With this
short-term condition (less than three hours), the breakers can be loaded at
full capacity.
Office power terminations are fastened to the control shelf with lugs. All
power distribution is contained within the bay, shelves, and frames. Power
wires are not externally accessible to protect power distribution from
accidental cuts or shorts.
You can use three configurations to connect power feeds to the power supply:
ATTENTION
Before choosing one of the following three configurations to connect power
feeds to the power supply for a Repeater network element, review Thermal
tool on page 9-24 to determine whether thermal limitations restrict the
circuit pack configuration of your application.
Six power feeds for 50-ampere service for ANSI and ETSI installations
Two power feeds for 100-ampere service for ANSI and ETSI installations
Note: If full flexibility for future use is not required and breaker size is
critical, you can use another power-feed configuration other than those
mentioned above. To determine the specific breaker size for your custom
application, refer to Custom applications on page 9-31.
This power configuration provides the maximum amount of power to the

universal bay and provides the maximum flexibility for future circuit pack
deployment in the network element.
You can connect the six power feeds to the front power termination block (see
Figure 9-3 on page 9-20). Figure 9-5 on page 9-22 demonstrates how to
connect the power cables to the front termination block. The recommended
amperage for fuses or breakers for each power lead from the battery
distribution fuse panel (BDFP) is 50 amperes.
50-ampere service requires that you tap customer-supplied feed wires into
cables for bay connections. The customer-supplied feed wire size depends on
the distance to the BDFP.
For 50-ampere service, use No. 6 AWG or 16-mm2 power cable to terminate
power at the universal bay. You can tap these cables into thicker cable
depending on the distance from the bay to the BDFP.
As shown in Figure 9-5 on page 9-22, three power feeds from each battery (A
and B) and the required three-battery return cables for each battery (A and B)
provide power to the bay. A ground connection is also provided at the top of
the bay for frame ground connection to the central office (CO) ground.
Note: To upgrade from 40-ampere service to 50-ampere service, contact
Nortel.
This power configuration provides sufficient power to the universal bay and
provides the flexibility for future circuit pack deployment in the network
element.
You can connect the six power feeds to the front power termination block (see
Figure 9-3 on page 9-20). Figure 9-5 on page 9-22 demonstrates how to
connect the power cables to the front termination block. The recommended
amperage for fuses or breakers for each power lead from the battery
distribution fuse panel (BDFP) is 40 amperes.
40-ampere service requires that you tap customer-supplied feed wires into
cables for bay connections. The customer-supplied feed wire size depends on
the distance to the BDFP.
For 40-ampere service, use No. 6 AWG or 16-mm2 power cable to terminate
power at the universal bay. You can tap these cables into thicker cable
depending on the distance of the bay to the BDFP.
As shown in Figure 9-5 on page 9-22, three power feeds from each battery (A
and B), and the required three battery return cables for each battery (A and B)
provide power to the bay. A ground connection is also provided at the top of
the bay for frame ground connection to the central office (CO) ground.
Two power feeds for 100-ampere service for ANSI and ETSI installations
The following general considerations apply for the power connections from
the power supply point to the amplifier bay.
To connect the two power feeds, you must have the power feed jumper kit
(NTCA89GE). This kit contains two three-position bus bars (P0885924),
one six-position bus bar (P0882764).
The power terminations on the universal bay accommodate a maximum

cable size of 25 mm2.
The power cables must have a temperature rating of 90o Celsius.
The two power cables can enter the bay from above, or through the floor.
The size of the power cable depends on the distance between the battery
distribution fuse panel (BDFP) and the 1600G Amplifier bay and the
voltage drop you can tolerate in the feed cables.
ANSI installations
The following considerations apply to ANSI installations:

If feed wires larger than 2 AWG are used, they must be tapped into 2 AWG
cable for termination on the bus bar.
Refer to Table 9-11 for ANSI cable selection guidelines, based on a 1.0V
voltage drop and 100 Amp power feed. These guidelines are for planning
purposes and are not intended to replace application specific power feed
calculations.
Table 9-11
Cable selection guidelines for ANSI installations
Cable size
One-way circuit length range,

overhead feeds
One-way circuit length

range, through-floor feeds
2 AWG
up to 8.5 m (27.5 ft)
up to 8.5 m (27.5 ft)
1 AWG
8.5 m to 10.5 m (27.5 ft to 34 ft)
8.5 m to 10 m (27.5 ft to 32.5 ft)
2/0 AWG
10.5 m to 16.5 m (34 ft to 54 ft)
10 m to 15 m (32 ft to 49 ft)
4/0 AWG
16.5 m to 26 m (54 ft to 85 ft)
15 m to 22 m (49 ft to 72 ft)
Note: The cable lengths refer to the distance between the secondary power
distribution panel and the Optical Long Haul 1600 bay.
Distance = 1/2 cable loop length, where the loop length is the total length of feeder
cables (L+ and L-). Loop length = 2 Distance.

ETSI installations
The following considerations apply to ETSI installations:

If feed wires larger than 35 mm2 are used to connect the two power feeds
at the top of the bay, you require the Optical Overhead Power Connection
kit (A0820533). This kit includes a power termination box, terminals,
power cables, lugs, and fixings.
If feed wires larger than 35 mm2 are used to connect the two power feeds
at the bottom of the bay, you require the Optical Bottom Fitting Power kit
(A0820532). This kit includes a DIN rail, brackets, DIN terminals, power
cables, lugs, and fixings.
Power cables are routed from the BDFP to the power termination box at
the top of the Repeater bay (either using an overhead or an under floor
cable run).
For an under floor cable run, the maximum voltage drop allowed in the
cable run between the BDFP and the terminals in the bottom of the
universal bay should be less than 0.64V to meet a total voltage drop
requirement of less than 1.0 V from the BDFP to the termination box on
the bay.
For detailed information about Optical ETSI power connections, refer to
Nortel Installation Technology Procedure (ITP) document ITP-04004
(formerly ITI-5004), Power Cable Installation for Optical Long Haul and
Optical Connect DX.
Refer to Table 9-12 for ETSI cable selection guidelines, based on a 1.0V
voltage drop and 100 Amp power feed. These guidelines are for planning
purposes and are not intended to replace application specific power feed
calculations.
Table 9-12
Cable selection guidelines for ETSI installations
Cable size
One-way circuit length range,

overhead feeds
One-way circuit length

range, through-floor feeds
35 mm2
up to 9 m (29.5 ft)
up to 9 m (29.5 ft)
50 mm2
9 m to 12.5 m (29.5 ft to 41 ft)
9 m to 11.5 m (29.5 ft to 37.5 ft)
70 mm2
12.5 m to 17 m (41 ft to 55.5 ft)
11.5 m to 15 m (37.5 ft to 49 ft)
120 mm2
17 m to 29 m (55.5 ft to 95 ft)
15 m to 23.5 m (49 ft to 77 ft)
Note: The cable lengths refer to the distance between the secondary power
distribution panel and the Optical Long Haul 1600 bay.
Distance = 1/2 cable loop length, where the loop length is the total length of feeder
cables (L+ and L-). Loop length = 2 Distance.
See Figure 9-4 on page 9-21 for a detailed schematic of the two power feeds
installation procedure.
Figure 9-5 on page 9-22 demonstrates how to connect the power cables to the
front termination block.
Figure 9-3
Installing six power feeds to a front power termination block
OTP3033p
Feed
Place the six feed

power cables
(two-hole crimp lug)
over each two
feed busbars
Return
A1
A1
B1
B1
A2
A2
B2
B2
A3
A3
B3
B3
All -48 V
Tighten to
torque
specification
Place the six

return power
cables (twohole crimp lug)
over the return
busbars
0V
Note: Measure power at the busbar and at the fastening nuts over the power cables.

Figure 9-4
Installing two power feeds to a front power termination block
OTP2964p
Step 1
Return
A1
Feed
Place the three-position
busbar B down first
(insulator up so that
it is visible)
B1
B1
A2
B2
B2
A3
Tighten to
torque
specification
B3
B3
0V
Six-position busbar
Three-position busbar
Step 2
Feed
Place the three-position
busbar A with
insulator down so
that it is in contact
with insulator on
busbar B
Tighten to
torque
specification
Return
A1
A1
B1
B1
A2
A2
B2
B2
A3
A3
B3
B3
0V
Step 3
Feed
Place the two feed
power cables
(two-hole crimp lug)
over the two feed
busbars A2 / B3
Tighten to
torque
specification
Return
A1
A1
B1
B1
A2
A2
B2
B2
A3
A3
B3
B3
Place the two

return power
cables (two-hole
crimp lug) over
the top two
return busbars
0V
Note: Measure power at the busbar and at the fastening nuts over the power cables.

Figure 9-5
Power cables connected to the Optical Long Haul 1600 control shelf power termination block
OTP1305
Power cables from

the power termination
block to the power
supply
Power termination
block
Breaker filter
Module A
Breaker filter
Module B

Table 9-13 shows the typical power estimates of the Optical Long Haul 1600
Repeater circuit packs operating at the nominal battery voltage.
Note: For information on circuit packs for an Amplifier network element,
refer to the 1600G Amplifier Unidirectional Network Application Guide
(NTY314AL).
Table 9-13
Circuit pack
PEC
Typical power
dissipation (W)
(see Note 1)
2.5G WT
NTCA70xx
56
10G WT
NTCA07xx
85
10G WT (TriFEC)
NTCF07xx
96
10G WT SR (TriFEC)
NTWR07AA
97
OC-192/STM-64 XR
NTCA04xx
85
OC-192/STM-64 XR/WT
NTCF04xx
78
OC-192/STM-64 T/R
NTCA06xx
125
NTCF06xx
115
NTCA30xK
50
OC-48/STM-16 T/R SR
NTCA30CK
46
OC-48/STM-16 T/R (1310 nm)
NTCA30AL
65
NTCA72xx
105
Ethernet Wayside
NTCA56AA
NTCA39AA
10
MOR Plus amplifier (with and without OSC)
NTCA11xK
45
Unidirectional OSC 1510/1615 nm
NTCA15Ax
36
NTCA21AA
NTCA90xA
31
Orderwire
NTCA47xx
OPC storage
NTCA51xx
13
OPC controller
NTCA50xx
11

Circuit pack
PEC
OPC interface
NTCA52xx
OPC removable media
NTCA53xx
Shelf controller, 32 M
NTCA41xx
10
Maintenance interface
NTCA42xx
External synchronization interface
NTCx44xx
10
Message exchange
NTCA48xx
Parallel telemetry
NTCA45xx
NTCA40xx
Fan module (see Note 2)
NTCA85EA
50
Note 1: Power dissipation values vary by

June 1, 2001.
Typical power
dissipation (W)
(see Note 1)
10 percent. These values are estimates starting from
Note 2: You must equip NTCA85EA fans under both the main shelf and extension shelf 1. You must
replace NTCA85DA fans previously supported on the Optical Long Haul 1600 bay by the NTCA85EA
fans for fully equipped configurations. Three fan modules are required for each environmental control
panel (ECP) unit. Two ECP units are required for each NTCA89GC bay.
Thermal tool
ATTENTION
The slot location of TriFEC-capable circuit packs in an Optical Long Haul
1600 bay can reduce the maximum number of circuit packs that you can
install. You are limited to the number and type of circuit packs in a bay,
depending on the circuit pack configuration and the circuit pack typical
power dissipation (see Table 9-13 on page 9-23). You must ensure that your
configuration meets the thermal rules described in this section.
You must follow specific thermal rules when equipping the Optical Long Haul
1600 bay with TriFEC-capable circuit packs. The following six-step tool
confirms whether a proposed circuit pack configuration complies with the
maximum permissible temperature of the bay. Use Table 9-14 to obtain
thermal rating and maximum power values required for the thermal tool.

Table 9-14
Thermal rating and maximum power dissipation
Thermal rating (TR)
Circuit pack
PEC
Maximum
power
Main shelf
Main shelf
Main shelf
dissipation
(slots 1 to 3) (slots 4 to 6) (slots 7 to 10) (P
MAX) (W)
OC-192/STM-64 T/R
NTCA06xx
60
85
100
138
OC-192/STM-64 T/R
(TriFEC)
NTCF06xx
60
85
100
127
OC-48/STM-16 T/R SR
NTCA30CK
100
100
100
51
OC-48/STM-16 DWDM
T/R
NTCA30xK
100
100
100
55
OC-48/STM-16 T/R
(1310 nm)
NTCA30AL
100
100
100
72
OC-192/STM-64 XR
NTCA04xx
100
100
100
94
OC-192/STM-64 XR/WT
NTCF04xx
85
100
100
86
2.5G WT
NTCA70xx
60
71
82
62
Dual 2.5G WT on/off ramp NTCA72xx
100
100
100
105
10G WT
NTCA07xx
100
100
100
94
10G WT (TriFEC)
NTCF07xx
85
100
100
106
10G SR WT (TriFEC)
NTWR07AA
92
100
100
107
MOR Plus amplifier
NTCA11xK
96
100
100
50
Timing distribution
NTCA21AA
100
100
100
NTCA90xA
100
100
100
31

(OSM)
NTCA39AA
100
100
100
11
Procedure 9-1
Determining thermal requirements for circuit pack
configurations
Use this procedure to determine whether your proposed circuit pack
configuration complies with the maximum permissible temperature of the bay.
Procedure purpose
You must follow specific thermal rules when equipping the Optical Long Haul 1600 bay with
TriFEC-capable circuit packs. The following six-step tool confirms whether a proposed circuit pack
configuration complies with the maximum permissible temperature of the bay. Use Table 9-14 on page
9-25 to obtain thermal rating and maximum power values required for the thermal tool.
Before you start

Determine the proposed circuit pack fill of the Optical Long Haul 1600 bay, including the exact slot
location of each circuit pack.
Photocopy the worksheet on page 9-28. Use this worksheet to enter your data for each step of this
procedure.
Procedure tasks
Determine which circuit pack has the lowest thermal rating (TR) in slots 1 to 3, 4 to 6, and 7 to 10 of the
main shelf (step 1).
Compute the mid-shelf thermal index (MSTI) in slots 1 to 3, 4 to 6, and 7 to 10 for extension shelf 1
(step 2).
Compute the maximum permissible bottom shelf thermal index (BSTI) in slots 1 to 3, 4 to 6, and 7 to 10
for extension shelf 2 (step 3).
Determine BSTIMIN (step 4).
Compute the maximum permissible total power for extension shelf 2 (step 5).
Compute the maximum number of circuit packs allowed in extension shelf 2 (step 6).
Expected results
The proposed circuit pack configuration meets maximum permissible temperature values for the bay.
If the expected results do not occur, you must find another suitable configuration and perform the
procedure again to determine if the new configuration meets the maximum permissible temperature
values for the bay.
continued

Procedure 9-1 (continued)
Determining thermal requirements for circuit pack configurations
Action
Step
Action
Determine which circuit pack has the lowest thermal rating (TR) in slots 1 to 3,
4 to 6, and 7 to 10 of the main shelf (refer to Table 9-14 on page 9-25 for the
thermal rating values of circuit packs). Record these thermal rating values as
TRMIN, 1-3, TRMIN, 4-6, and TRMIN, 7-10 respectively, in the worksheet on page
9-28.
Compute the mid-shelf thermal index (MSTI) in slots 1 to 3,

4 to 6, and 7 to 10 for extension shelf 1, using the following formulas:
MSTI 1-3 = 0.07 x ( P1-6 +90)
MSTI 4-6 = 0.07 x (P3-8 +90)
MSTI 7-10 = 0.07 x (P5-10 +90)
The power summation (PMAX) is the sum of all maximum power dissipations
for circuit packs in extension shelf 1 from slots 1 to 6, 3 to 8, or 5 to 10, as
indicated in the above formulas.
Compute the maximum permissible bottom shelf thermal index (BSTI) in slots
1 to 3, 4 to 6, and 7 to 10 for extension shelf 2, using the following formulas:
BSTI1-3 = TRMIN, 1-3 MSTI1-3
Determine the lowest BSTI value from BSTI1-3, BSTI4-6, and BSTI7-10.
Record this value as BSTIMIN in the worksheet on page 9-28. BSTIMIN
corresponds to maximum permissible bottom shelf thermal index.
Compute the maximum permissible total power for extension shelf 2 using
the following formula:
P1-10, EXTSHELF 2= (BSTIMIN/0.042) 150.
Compute the maximum number of circuit packs allowed in extension shelf 2

using the following formula:
Number of circuit packs = (P1-10, EXTSHELF 2) / PMAX
where PMAX is the maximum power dissipation for a circuit pack (see Table
9-14 on page 9-25). You can also determine Pmax for each slot using the
following formula:
PMAX for each slot = (P1-10, EXTSHELF 2) / 10.
Round the computed number of circuit packs to the nearest integer value.
Note: Although not mandatory, it is recommended to place filler circuit packs

and low power circuit packs to the left side of extension shelf 2.
end
Thermal tool worksheet

Use Table 9-15 as a worksheet for Procedure 9-1, Determining thermal
requirements for circuit pack configurations.
Table 9-15
Thermal tool summary
Thermal tool
Step
Shelf
Formula
Step 1
Main shelf
TR MIN, 1-3 = MIN (TR1, TR2, TR3) =

(see Note 1)
TR MIN, 4-6 = MIN (TR4, TR5, TR6) =
(see Note 1)
TR MIN, 7-10 = MIN (TR7, TR 8, TR9. TR10) =
(see Note 1)
Step 2
Extension shelf 1 MSTI1-3 = 0.07 x (P1-6 +90) =

MSTI4-6 = 0.07 x (P3-8 +90) =
MSTI7-10 = 0.07 x (P5-10 +90) =
Step 3
Extension shelf 2 BSTI1-3 = TR MIN, 1-3 MSTI1-3 =

BSTI4-6 = TR MIN, 4-6 MSTI4-6 =
BSTI7-10 = TRMIN, 7-10 MSTI7-10 =
Step 4
BSTIMIN= MIN (BSTI1-3, BSTI4-6, BSTI7-10) =
Step 5
P1-10, EXTSHELF 2 = (BSTIMIN / 0.042) 150 =
Step 6
Number of circuit packs allowed = (P1-10, EXTSHELF 2) / PMAX =

(see Note 2)
Note 1: The thermal rating (TR) is obtained from Table 9-14 on page 9-25.
Note 2: PMAX is the maximum power dissipation for a circuit pack (see Table 9-14 on page 9-25).

Example of a Repeater network element with OC-192/STM-64 XR/WT circuit
packs (NTCF04) and 10G WT (TriFEC) circuit packs (NTCF07)
Table 9-16 lists thermal ratings (TR) and power dissipation values for the
following Optical Long Haul 1600 bay configuration:
OC-192/STM-64 XR/WT circuit packs (NTCF04) in the main shelf and
extension shelf 1
10G WT (TriFEC) circuit packs (NTCF07) in extension shelf 2
The values in Table 9-16 are obtained from Table 9-14 on page 9-25. Table
9-17 on page 9-30 provides a summary of steps used for this example.
Table 9-16
Thermal ratings and power dissipation values for a Repeater network element equipped with
OC-192/STM-64 XR/WT circuit packs (NTCF04) and 10G WT (TriFEC) circuit packs (NTCF07)
Repeater network element
Control shelf
Main shelf
G0
G1
G2
G3
G4
G5
G6
G7
G8
G9
TR1=85 TR 2=85 TR3=85 TR4=100 TR5=100 TR6=100 TR7=100 TR8=100 TR 9=100 TR =100
10
P1=86 P2=86 P3=86 P4=86
P5=86
P6=86
P7=86
P8=86
P9=86
P10=86
Extension shelf 1
G10
G11
G12
G13
G14
G15
G16
G17
G18
G19
P1=86
P2=86
P3=86
P4=86
P5=86
P6=86
P7=86
P8=86
P9=86
P10=86
G28
G29
Extension shelf 2
(to be equipped with 10G WT (TriFEC) circuit packs)
G20
G21
G22
G23
G24
G25
G26
G27

Table 9-17
Summary of steps for a Repeater network element with OC-192/STM-64 XR/WT circuit packs
(NTCF04) and 10G WT (TriFEC) circuit packs (NTCF07)
Thermal tool
Step
Shelf
Formula
Step 1
Main shelf
TR MIN, 1-3 = MIN (TR1, TR2, TR3) (see Note 1) = 85

TR MIN, 4-6 = MIN (TR4, TR5, TR6) (see Note 1) = 100
TR MIN, 7-10 = MIN (TR7, TR 8, TR9. TR10) (see Note 1) = 100
Step 2
Extension shelf 1 MSTI1-3 = 0.07 x (P1-6 +90) = 0.07 x (86 x 6 + 90) = 42.42
MSTI4-6 = 0.07 x (P3-8 +90) = 0.07 x (86 x 6 + 90) = 42.42
MSTI7-10 = 0.07 x (P5-10 +90) = 0.07 x (86 x 6 + 90) = 42.42
Step 3
Extension shelf 2 BSTI1-3 = TR MIN, 1-3 MSTI1-3 = 85 42.42 = 42.58

BSTI4-6 = TR MIN, 4-6 MSTI4-6 = 100 42.42 = 57.58
BSTI7-10 = TRMIN, 7-10 MSTI7-10 = 100 42.42 = 57.58
Step 4
BSTIMIN= MIN (BSTI1-3, BSTI4-6, BSTI7-10) = 42.58
Step 5
P1-10, EXTSHELF 2 = (BSTIMIN / 0.042) 150 = (42.58 / 0.042) 150 =

863.8
Step 6
Number of circuit packs allowed in extension shelf 2 =

(P1-10, EXTSHELF 2) / PMAX (see Note 2) = 863.8 / 106 = 8.14 =
eight 10G WT (TriFEC) circuit packs
As an alternative, you can equip extension shelf 2 with ten
OC-192/STM-64 XR/WT circuit packs (863.8 / 86 = 10).
Note 1: The thermal rating (TR) is obtained from Table 9-14 on page 9-25.
Note 2: PMAX is the maximum power dissipation for a circuit pack (see Table 9-14 on page 9-25).
Custom applications
For custom applications where breaker amperes are restricted and a fully-filled
configuration is not a requirement, you can use the following power tool to
determine the breaker size for a specific configuration on an Optical Long
Haul 1600 bay. Use the typical circuit pack power estimates in Table 9-13 on
page 9-23 for the breaker calculations.
Power management tool
You must use the power management tool to determine the required breaker
size on the Optical Long Haul 1600 bay (see Table 9-18). Breaker size is
calculated by using the following conditions:
low battery conditions (where circuit packs can continue to draw current
down to 32 V dc)
100% breaker loading for low battery (for short term condition at less than
three hours)
a redundant feed to the bay has failed (only A or B feed supplies all the
current)
total [sum of typical powers for circuit packs in the main shelf, extension
shelf 1, and extension shelf 2 + sum of typical powers for circuit packs in
the control shelf + environmental control panel(s)] + 10% variation

Table 9-18
Power management tool
Total (W)
Breakers
required
Bay assembly
Environmental control panel (ECP)
(NTCA89CA) (see Note 1 and Note 2)
Bay assembly (sub-total1)
Control shelf (sub-total2)
(sum of typical powers for each circuit pack in control shelf)
Main shelf (sub-total3)
(sum of typical powers for each circuit pack in main shelf)
Extension shelf 1 (sub-total4)
(sum of typical powers for each circuit pack in extension shelf 1)
Extension shelf 2 (sub-total5)
(sum of typical power for each circuit pack in extension shelf 2)
Single feed (minimum breakers required)
TotalMAX
(sum of all sub-totals) X 1.1
Current Load (@ 32V) in Amperes
(totalMAX / 32)
Minimum Breakers required using 100% load
(current load) / 1.0
Triple feed (minimum breakers required)
Feed A1: (sub-total3 + ECP1) X 1.1 / 32
Feed A2: (sub-total4 + ECP2) X 1.1 / 32
Feed A3: (sub-total2 + sub-total5) X 1.1 / 32
Note 1: The thermal load for NTCA89CA is 150 W.

Note 2: The NTCA89GB bay (with extension shelf 1) requires one ECP. The NTCA89GC bay (with
extension shelf 1 and extension shelf 2) requires two ECPs.
10-1
Circuit pack technical specifications 10This chapter provides advanced specifications and requirements for Repeater
network element circuit packs.
For details on power and thermal requirements for the Repeater network
element, refer to Mechanical specifications on page 9-1.
Optical interface specifications

The Optical Long Haul 1600 network element equipment meets the
requirements of the SONET rates and format specifications defined by ECSA
committee T1X1.4, T1X1.5 in document T1.105, Optical Interface Rates and
Format Specifications, March 1988.
All Optical Long Haul 1600 equipment complies with the SONET/SDH
optical interface specifications. All SONET/SDH transmit interface circuit
packs can transmit to non SONET/SDH receivers. Similarly, all SONET/SDH
receive interface circuit packs can accept signals from non SONET/SDH
transmitters.
The specifications provided in this section apply to the worst-case production
units, operating at environmental extremes and end-of-life (EOL) limits.
Technical specifications for Repeater circuit packs

Table 10-1 lists all circuit packs supported by the Repeater network element.
Refer to the appropriate table for the technical specifications of a specific
circuit pack.
10-2 Circuit pack technical specifications

Table 10-1
Circuit pack technical specification tables
Circuit pack
PEC
Reference
2.5G WT
NTCA70xx
Table 10-2
OC-48/STM-16 T/R SR
NTCA30CK
Table 10-3
NTCA30xK
Table 10-4
OC-48/STM-16 T/R (1310 nm)
NTCA30AL
Table 10-5
10G WT SR (TriFEC)
NTWR07AA
Table 10-6
10G WT
NTCA07xx
Table 10-7
10G WT (TriFEC)
NTCF07xx
Table 10-8
NTCA72xx
Table 10-9
OC-192/STM-64 T/R
NTCA06xx
Table 10-10
NTCF06xx
Table 10-11
OC-192/STM-64 XR
NTCA04xx
Table 10-12
OC-192/STM-64 XR/WT
NTCF04xx
Table 10-13
NTCA90xA
Table 10-14
NTCA39AA
Table 10-15
Ethernet Wayside
NTCA56AA
Note 1
MOR and MOR Plus amplifier (with and without OSC)
NTCA11xK
Note 2
Note 1: For details on the Ethernet Wayside technical specifications, refer to the Ethernet Wayside
Note 2: For details on MOR Plus amplifier technical specifications, refer to the 200 GHz, MOR/MOR
Plus, 2 to 16- Optical Layer Applications Guide (NTY311DX).
For technical specifications of circuit packs supported in the Amplifier

network element, refer to the 1600G Amplifier Unidirectional Network
Application Guide (NTY314AL).
Circuit pack technical specifications 10-3
2.5G WT circuit pack (NTCA70xx)

Table 10-2
2.5G WT circuit pack
F4724-MOR_R80
LOS (yellow)
Fail or mismatch (red)
Active (green)
Output optical connector

Input optical connector

Functional description
The 2.5 Gbit/s Wavelength Translator (WT) acts as a gateway that converts non-Nortel DWDM
wavelengths to Nortel optical frequencies aligned with the ITU-T grid. The frequency, accuracy, and
stability of the optical signal emitted allow these WTs to be used in DWDM systems with spacings of
100 GHz or more between adjacent wavelengths. The 2.5G WT circuit pack supports AM1 only.
Wavelength Translators are capable of processing thin SONET/SDH signals. Therefore, these
translators provide access to the optical backbone. This arrangement allows for open architectures.
Hardware description
The 2.5 Gbit/s Wavelength Translator (WT) is designed to be installed in the Optical Long Haul 1600
mechanical bay assembly. The 2.5 Gbit/s WT is equipped with an electro-optic modulator,
photodetector and the required RF circuitry to convert the 2.5 Gbit/s modulated optical signal to the
electrical domain for 3R regeneration and overhead processing. The signal is then converted back to
the optical domain with a specific carrier wavelength.
Three LEDs are located on the faceplate to identify an LOS (yellow LED), an active circuit pack (green
LED), or a failed circuit pack (red LED). A red LED that is ON usually indicates a partial or complete
failure of the circuit pack (for example, a Circuit pack fail alarm). A red LED that is ON can also indicate
a mismatch condition on the circuit pack (for example, a Circuit pack mismatch alarm).
OAM&P features
The 2.5 Gbit/s WT has the following features:
thin SONET/SDH overhead processing
remote provisioning of output power and chirp polarity
optical power monitoring
analog maintenance support
alarm reporting
Specifications
Product Engineering Code
NTCA70xx (see Note 1)
Connector type
Adapterless (see Note 2)
Limitations
The 2.5 Gbit/s WT is not supported with 1600G Amplifier applications.
Transmitter specifications
Tx module laser type
Distributed Feedback (DFB) semiconductor laser
Maximum laser spectral width

(Continuous wave linewidth)
0.115 nm (see Note 3)
Minimum laser Side Mode Suppression

Ratio (SSR)
40 dB
Pigtail fiber type
Single-mode fiber
Wavelength range
1527.99 to1562.23 nm

Central wavelength accuracy
Provisionable output power
Configurable from 11 to 3 dBm subject to the accuracy

below.
Output power adjustment accuracy
0.25 dBm
This worst-case end-of-life (EOL) number includes
connector loss, aging and temperature degradation.
Reflection tolerance
14 dB
Maximum tolerated optical power into

output connector of the transmitter
10 dBm
Transmitter line coding
Non-return to zero (NRZ)
Receiver specifications
Photodetector type
APD
Pigtail fiber type
Single-mode fiber
Wavelength range input
1290 nm to 1570 nm
Guaranteed sensitivity
28.3 dBm
Overload level (input power to the Rx must 15 dBm

be equal or below this value so that
guaranteed link BER and jitter tolerance are
met)
Damage level (maximum power allowed at 5 dBm
the input of the Rx above which the
components can be permanently damaged)
Line coding
Note 1: For the specific product engineering codes (PECs) and wavelengths for NTCA70xx, see
Ordering Guide (NTY311KL).
Note 2: SC connectors are recommended for Optical Long Haul 1600 applications. FC connectors are
also available. The maximum connector insertion loss is 0.7 dB. The minimum connector return loss is
30 dB.
Note 3: The laser spectral width specification measurement is taken at 3 dB.
Note 4: This value does not include information bandwidth and dispersion compensating chirp.

Table 10-3
OC-48/STM-16 T/R SR circuit pack
F4724-MOR_R80
LOS (yellow)
Active (green)


The OC-48/STM-16 T/R short reach circuit pack is a low speed tributary interface that combines a
1310 nm short reach transmitter and a receiver into one circuit pack. This single circuit pack provides
both transmit and receive interface ports.
The circuit pack receives a 2.5 Gbit/s optical signal from the subtending equipment. The optical signal
is converted into an electrical signal and transmitted to the backplane where it is multiplexed into an
STS-192 signal. The STS-192 signal is then directed towards the OC-192/STM-64 T/R circuit pack. You
can provision the OC-48/STM-16 T/R circuit pack in both SONET and SDH configurations.
The OC-48/STM-16 T/R SR circuit pack is designed to be installed in the Optical Long Haul 1600 or
Connect DX mechanical bay assembly. Three circuits support the OC-48/STM-16 T/R SR interface:
point-of-use power supply (PUPS), the receive (Rx) controller, and the transport control subsystem
(TCS).
The PUPS generates all voltage required by the OC-48/STM-16 T/R SR interface. The Rx controller
samples the quality of the data streams, and controls the phase adjustment of the data and the bias of
the avalanche photo-diode (APD). The Rx controller also provides the TCS with status information. The
TCS controls the operation of the OC-48/STM-16 T/R SR interface. The TCS provides communication
with the SC, generates alarms, and activates the LEDs on the circuit pack faceplate.
The three LEDs identify an LOS (yellow LED), an active circuit pack (green LED), or a failed circuit pack
(red LED). A red LED that is ON usually indicates a partial or complete failure of the circuit pack (for
example, a Circuit pack fail alarm). A red LED that is ON can also indicate a mismatch condition on
the circuit pack (for example, a Circuit pack mismatch alarm).
OAM&P features
The OC-48/STM-16 T/R supports the alarm reporting feature.
Specifications
Product engineering code (PEC)
NTCA30CK (short reach) (see Note 1 and Note 2)
Connector type
Fabry-Perot laser
Pigtail fiber type
Single-mode fiber
Central wavelength
1310 nm
Wavelength tolerance
1260 to 1360 nm
Spectral width
4 nm
Maximum tolerated optical reflection
27 dB
Guaranteed launch power
10 dBm (min), 3 dBm (max) (see Note 4 and Note 5)

Photodetector type
PIN photo diode
Pigtail fiber type
Single-mode fiber
1260 to 1570 nm
18 dBm
Line rate
OC-48/STM-16 (2.488 Gbit/s)
Overload level
3 dBm (see Note 6)
Damage level
3 dBm (see Note 7)
Line coding
Note 1: For the specific product engineering codes (PECs) and wavelengths for NTCA30CK, see
Note 2: 1557 nm or DWDM-capable OC-48/STM-16 T/R can be supported for long-reach applications.
30 dB.
Note 4: This parameter is a worst-case launch power and includes connector losses, aging, equipment
impairment caused by implementation, and temperature degradation. This value represents the power
level measured at the station fiber on the link side of connectors.
Note 5: The transmit output power is not user provisionable.
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 and all jitter tolerance specifications.
Note 7: Damage level is the maximum optical power for which no damage to the components occurs.

Table 10-4
OC-48/STM-16 DWDM T/R circuit pack
F4724-MOR_R80
LOS (yellow)
Active (green)


The OC-48/STM-16 DWDM T/R circuit pack is a low-speed tributary interface. The circuit pack
combines an OC-48/STM-16 DWDM transmitter and a receiver into one circuit pack. This single circuit
pack provides both transmit and receive interface ports.
STS-192 signal. The STS-192 signal is then directed towards the OC-192/STM-64 T/R circuit pack.
You can provision the OC-48/STM-16 DWDM T/R circuit pack in both SONET and SDH configurations.
The OC-48/STM-16 DWDM T/R circuit pack is designed to be installed in the Optical Long Haul 1600
or Connect DX mechanical bay assembly. Three circuits support the OC-48/STM-16 DWDM T/R
interface: point-of-use power supply (PUPS), the receive (Rx) controller, and the transport control
subsystem (TCS).
The PUPS generates all voltage required by the OC-48/STM-16 DWDM T/R interface. The Rx
controller samples the quality of the data streams, and controls the phase adjustment of the data and
the bias of the APD (avalanche photo-diode). The Rx controller also provides the TCS with status
information. The TCS controls the operation of the OC-48/STM-16 DWDM T/R interface. The TCS
provides communication with the SC, generates alarms, and activates the LEDs on the circuit pack
faceplate.
The transmitter of the OC-48/STM-16 DWDM T/R circuit pack uses the AM1 dither feature. The AM1
dither feature is not provisionable on the OC-48/STM-16 DWDM T/R transmitter.
OAM&P features
The OC-48/STM-16 DWDM T/R supports the alarm reporting feature.
Limitations
The OC-48/STM-16 DWDM T/R interface operates as a normal short-reach circuit pack. DWDM
features such as optical power output and wavelength provisioning are not supported by the
Wavelength Combiner software.
Specifications
NTCA30xK (see Note 1)
Connector type
Maximum laser spectral width (Continuous wave 0.115 nm (Note 3)
linewidth)
Minimum laser Side Mode Suppression Ratio
(SSR)
40 dB
Pigtail fiber type
Single-mode fiber

Wavelength range
1528.77 nm to 1558.98 nm
Launch power range
3 dBm (see Note 4)
0.12 nm
Spectral width
(data + chirp + SBS suppression) 0.035 nm
Dispersion tolerance
+17000 2000 ps/nm
SBS threshold
14 dB
Transmitter optical return loss
27 dB
14 dB
Minimum extinction ratio
10 dB
Transmitter type
DFB laser
Modulator Type
IIIV Mach-Zehnder
Chirp factor provisionable
positive or negative
Input power
28.3 dBm to 15 dBm (see Note 5)
Receiver overload
15 dBm
Optical Return Loss
10 dBm
Detector type
APD
Input wavelength range
1290 nm to 1570 nm
Note 1: For the specific product engineering codes (PECs) and wavelengths for NTCA30xK, see
30 dB.
Note 4: The transmitter output power is a set value and cannot be changed.
Note 5: The receiver input power range is set to the particular values to maintain a bit error ratio (BER)
of 10 12 at the end of the line.

Table 10-5
OC-48/STM-16 T/R (1310 nm) circuit pack
F4724-MOR_R80
LOS (yellow)
Active (green)


The OC-48/STM-16 T/R (1310 nm) tributary circuit pack is a low speed tributary interface that combines
a 1310 nm transmitter and a receiver into one circuit pack. This single circuit pack provides both
transmit and receive interface ports.
STS-192 signal. The STS-192 signal is then directed towards the OC-192/STM-64 T/R circuit pack.
You can provision the OC-48/STM-16 T/R (1310 nm) tributary circuit pack in both SONET and SDH
configurations.
The OC-48/STM-16 T/R (1310 nm) tributary circuit pack is designed to be installed in the Optical Long
Haul 1600 or Connect DX mechanical bay assembly. Three circuits support the OC-48/STM-16 T/R
(1310 nm) interface: point-of-use power supply (PUPS), the receive (Rx) controller, and the transport
control subsystem (TCS).
The PUPS generates all voltage required by the OC-48/STM-16 T/R (1310 nm) interface. The Rx
controller samples the quality of the data streams, and controls the phase adjustment of the data and
the bias of the avalanche photo-diode (APD). The Rx controller also provides the TCS with status
information. The TCS controls the operation of the OC-48/STM-16 T/R (1310 nm) interface. The TCS
provides communication with the SC, generates alarms, and activates the LEDs on the circuit pack
faceplate.
OAM&P features
The OC-48/STM-16 T/R (1310 nm) circuit pack supports the alarm reporting feature.
Specifications
NTCA30AL (see Note 1)
Connector type
Laser
DFB laser
Minimum laser Side Mode Suppression Ratio

(SSR)
33 dB
Pigtail fiber type
Single-mode fiber
Central wavelength
1310 nm
Line rate
2.488 Gbit/s
10 nm
Spectral width
0.65 nm

Line code
NRZ
Maximum tolerated optical reflection
20 dB
Guaranteed launch power (see Note 3)
2.0 dBm (min.)

3.0 dBm (max.)
Detector
APD
Pigtail
single-mode fiber
Line rate
2.488 Gbit/s
Line code
NRZ
Receiver overload (see Note 5 and Note 6)
15 dBm
Damage level (see Note 4)
5.0 dBm
Guaranteed receiver sensitivity
25.5 dBm
Wavelength of operation
1290 nm to 1570 nm
Note 1: For the specific product engineering codes (PECs) and wavelengths for NTCA30AL, see
30 dB.
Note 3: These parameters are worst-case and include connector losses, aging, equipment impairment
caused by implementation and temperature degradation. This value represents the power level
measured at the station fiber on the link side of connectors.
Note 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 OC-48/STM-16 T/R SR (NTCA30CK)
interface and the intermediate reach OC-48/STM-16 T/R (1310 nm) (NTCA30AL) interface. The short
reach OC-48/STM-16 T/R SR (NTCA30CK) interface has a PIN detector whereas the intermediate
reach OC-48/STM-16 T/R (1310 nm) (NTCA30AL) interface has an APD detector. The APD is also
more sensitive to the power levels and potential risk of damage to hardware.
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
10G WT SR (TriFEC) circuit pack (NTWR07AA)

Table 10-6
10G WT SR (TriFEC) circuit pack
F4724-MOR_R80
LOS (yellow)
Active (green)


The 10G WT SR (TriFEC) circuit pack acts as a gateway that converts the Nortel optical frequencies
aligned with the ITU-T grid to 1550 nm. Designed for off-ramp applications, the 10G WT SR (TriFEC)
circuit pack is equipped with short-reach optics on the transmitter. The 10G WT SR (TriFEC) circuit
pack provides provisionable error correction only on the receiver: no error correction, single FEC, and
TriFEC.
Wavelength Translators are capable of processing SONET or SDH signals using thin regeneration. The
Wavelength Translators provide access to the optical backbone. This arrangement allows for open
architectures.
The 10G WT SR (TriFEC) circuit pack is designed to be installed in the Optical Long Haul 1600 bay at
a terminal site for off-ramp applications. The 10G WT SR (TriFEC) circuit pack is equipped with an
electro-optic modulator, photodetector and the required RF circuitry to convert the 10 Gbit/s modulated
optical signal to the electrical domain for 3R regeneration and overhead processing. The signal is then
converted back to the optical domain with a specific carrier wavelength.
Three light-emitting diodes (LED) are located on the faceplate to identify a loss of signal (LOS) (yellow
LED), an active circuit pack (green LED), or a failed circuit pack (red LED). A red LED that is ON usually
indicates a partial or complete failure of the circuit pack (for example, a Circuit pack fail alarm). A red
LED that is ON can also indicate a mismatch condition on the circuit pack (for example, a Circuit pack
mismatch alarm).
OAM&P features
The 10G WT SR (TriFEC) circuit pack has the following features.
thin SONET or SDH overhead processing
alarm reporting
provisionable error correction (no error correction, single FEC, and TriFEC) only on the receiver
Specifications
NTWR07AA
Connector type
Distributed feedback (DFB) semiconductor laser

(see Note 2)
Maximum laser spectral width (Continuous

wave linewidth)
Minimum laser side mode suppression ratio

(SSR)
30 dB
Pigtail fiber type
Single-mode fiber
Wavelength range
1530 nm to 1562 nm

0.125 nm
Guaranteed launch power
2.5 dBm (minimum), 1 dBm (maximum)

(see Note 4)
0.5 dBm (see Note 5)
Chirp polarity
zero
14 dB
Maximum tolerated optical power into output

connector of the transmitter
10 dBm
Photodetector type
PIN photodetector
Pigtail fiber type
Single-mode fiber
1290 nm to 1603.13 nm
12 dBm for amplified links

14 dBm for non-amplified links
Overload level (input power to the Rx must be 0 dBm

equal or below this value so that guaranteed
link BER and jitter tolerance are met)
Damage level (maximum power allowed at the 5 dBm
input of the Rx above which the components
can be permanently damaged)
Receiver line decoding
30 dB.
Note 2: Short-reach standard Telcordia (formerly known as Bellcore: GR-1377SR-2, Nearest ITU-T:
G691 s64.2b)
Note 4: The transmit output power is not user provisionable.
Note 5: This parameter is a worst case parameter and includes connector losses, aging equipment,
impairment caused by implementation, and temperature degradation.
10G WT circuit pack (NTCA07xx)

Table 10-7
10G WT circuit pack
F4724-MOR_R80
LOS (yellow)
Active (green)


10G WT circuit pack
The 10 Gbit/s Wavelength Translator (WT) acts as a gateway that converts non-Nortel wavelengths to
Nortel optical frequencies aligned with the ITU-T grid. The frequency, accuracy, and stability of the
optical signal emitted allow these WTs to be used in DWDM systems with spacings of 50 GHz or more
between adjacent wavelengths. The 10G WT circuit pack supports AM1 and AM2.
Wavelength translators are capable of processing thin SONET/SDH signals. The Wavelength
Translators provide access to the optical backbone. This arrangement allows for open architectures.
Note: The 10G WT circuit pack is manufacture discontinued and no longer orderable. This circuit pack
is still supported by Nortel, and it is still supported in the Repeater network element.
The 10 Gbit/s Wavelength Translator (WT) is designed to be installed in the Optical Long Haul 1600
mechanical bay assembly. The 10 Gbit/s WT is equipped with an electro-optic modulator, photodetector
and the required RF circuitry to convert the 10 Gbit/s modulated optical signal to the electrical domain
for 3R regeneration and overhead processing. The signal is then converted back to the optical domain
with a specific carrier wavelength.
Three LEDs are located on the faceplate to identify an LOS (yellow LED), an active circuit pack (green
LED), or a failed circuit pack (red LED). A red LED that is ON usually indicates a partial or complete
failure of the circuit pack (for example, a Circuit pack fail alarm). A red LED that is ON can also indicate
a mismatch condition on the circuit pack (for example, a Circuit pack mismatch alarm).
OAM&P features
The 10 Gbit/s WT has the following features:
alarm reporting
Specifications
Product Engineering Code (PEC)
Connector type

wave linewidth)

Ration (SSR)
40 dB
Pigtail fiber type
Single-mode fiber
Wavelength range
1528.77 to 1603.13 nm

10G WT circuit pack
Configurable from 10 to 1.5 dBm subject to the

accuracy listed in this table.
0.25 dBm
This number is a worst-case end-of-life number that
includes connector loss, aging and temperature
degradation.
Chirp polarity
Configurable to positive or negative
14 dB

10 dBm
Photodetector type
PIN photodetector
Pigtail fiber type
Single-mode fiber
1290 nm to 1603.13 nm


Line coding
30 dB.

Table 10-8
10G WT (TriFEC) circuit pack
F4724-MOR_R80
LOS (yellow)
Active (green)


The 10G WT (TriFEC) circuit pack acts as a gateway that converts non-Nortel wavelengths to Nortel
optical frequencies aligned with the ITU-T grid. The frequency, accuracy, and stability of the optical
signal emitted allows these Wavelength Translators to be used in DWDM systems with spacings of 50
GHz or more between adjacent wavelengths. The 10G WT (TriFEC) circuit pack supports analog
maintenance (AM1 and AM2). The 10G WT (TriFEC) circuit pack provides provisionable error
correction: no error correction, single FEC, and TriFEC.
Wavelength Translators are capable of processing SONET or SDH signals using thin regeneration. The
Wavelength Translators provide access to the optical backbone. This arrangement allows for open
architectures.
The 10G WT (TriFEC) circuit pack is designed to be installed in the Optical Long Haul 1600 mechanical
bay assembly. The 10G WT (TriFEC) circuit pack is equipped with an electro-optic modulator,
photodetector and the required RF circuitry to convert the 10 Gbit/s modulated optical signal to the
Three light-emitting diodes (LED) are located on the faceplate to identify a loss of signal (LOS) (yellow
LED), an active circuit pack (green LED), or a failed circuit pack (red LED). A red LED that is ON usually
indicates a partial or complete failure of the circuit pack (for example, a Circuit pack fail alarm). A red
LED that is ON can also indicate a mismatch condition on the circuit pack (for example, a Circuit pack
mismatch alarm).
OAM&P features
The 10G WT (TriFEC) circuit pack has the following features:
thin SONET or SDH overhead processing
analog maintenance (AM) support
alarm reporting
provisionable error correction (no error correction, single FEC, and TriFEC)
Specifications
NTCF07xx (see Note 1)
Connector type

wave linewidth)

Ration (SSR)
40 dB

Pigtail fiber type
Single-mode fiber
Wavelength range
1528.77 to 1603.13 nm

accuracy listed in this table.
0.25 dBm
This number is a worst-case end-of-life number that
includes connector loss, aging, and temperature
degradation.
Chirp polarity
14 dB

10 dBm
Photodetector type
PIN photodetector
Pigtail fiber type
Single-mode fiber
1290 nm to 1603.13 nm

14 dBm for nonamplified links

Note 1: For the specific product engineering codes (PECs) and wavelengths for NTCF07xx, see
30 dB.

Table 10-9
Dual 2.5G WT on/off ramp circuit pack
OTP2486p
LOS (Port 1) (yellow)

LOS (Port 2) (yellow)
Active (green)
Port 1 IN (SR Rx)
Port 1 Out (DWDM Tx)
Port 2 IN (DWDM Rx)
Port 2 OUT (SR Tx)
Front view
Note: The dual 2.5 Gbit/s circuit packs include two LOS (yellow) LEDs,
one for each facility.
The Dual 2.5G WT on/off ramp circuit pack acts as a gateway converting non-Nortel DWDM
wavelengths to Nortel optical frequencies aligned with the ITU-T grid. The frequency accuracy and
stability of the optical signal emitted allow these WTs to be used in DWDM systems with spacings of
100 GHz between adjacent propagating wavelengths. The Dual 2.5G WT on/off ramp circuit pack
supports AM1 and AM2 (for C-Band only). Wavelength Translators are capable of processing thin
SONET/SDH signals. Therefore, these translators provide access to the optical backbone. This
arrangement allows for open architectures.
The Dual 2.5G WT on/off ramp circuit pack (thin SONET/SDH regenerator) acts as an open optical
interface that allows access to the optical transport layer for one 2.5 Gbit/s SONET/SDH signal while
the second signal is equipped with short-reach optics for transmission to subtending equipment. The
Dual 2.5G WT on/off ramp circuit pack offers on-ramp and off-ramp capabilities with overhead
transparency.

The Dual 2.5G WT on/off ramp circuit pack is designed to be installed in the Optical Long Haul 1600
Repeater bay. The 2.5 Gbit/s WT on-ramp facility is equipped with an electro-optic modulator,
photodetector and the required RF circuitry to convert the 2.5 Gbit/s modulated optical signal to the
the optical domain with a specific carrier wavelength. The 2.5 Gbit/s WT off-ramp facility is equipped
with short-reach optics for transmission to subtending equipment. Four LEDs are located on the
faceplate: a yellow LED1 for port 1 (on-ramp) LOS, a yellow LED2 for port 2 (off-ramp) LOS, a green
LED to indicate circuit pack active, and a red LED to indicated a failed circuit pack. A red LED that is
ON usually indicates a partial or complete failure of the circuit pack (for example, a Circuit pack fail
alarm). A red LED that is ON can also indicate a mismatch condition on the circuit pack (for example, a
Circuit pack mismatch alarm).
OAM&P features
The Dual 2.5G WT on/off ramp has the following features:
two 2.5 Gbit/s services within one circuit pack
remote provisioning of output power and chirp polarity (on-ramp)
receive optical power monitoring (off-ramp only)
analog maintenance support on port 1(on-ramp)
alarm reporting
Specifications
Port 1
Port 2
Product Engineering Code (see Note 1)
NTCA72xx
Weight
3.54 kg (7.8 lbs)
Maximum power dissipation
105 W
Connector type
Port 1
Port 2
Distributed Feedback (DFB) Multi-longitudinal mode

semiconductor laser
(MLM) laser
Maximum laser spectral width

(Continuous wave linewidth)
2.5 nm

Ratio (SSR)
40 dB
Pigtail fiber type
Single-mode fiber
Single-mode fiber
Wavelength range
1527.99 to1562.23 nm
Central wavelength accuracy (see Note 5)

Central wavelength
0.12 nm
1310 nm
1280 nm to 1357 nm

Transmitter specifications (cont)
Port 1
Port 2
Transmitter output power
Configurable from 11 dBm Guaranteed

to 3.0 dBm subject to the 7.0 dBm (minimum)
following accuracy.
3.0 dBm (maximum)
0.25 dBm
This worst-case end-of-life

number includes connector
loss, aging and temperature
degradation.
14 dB
27 dB
Maximum tolerated optical power into

output connector of the transmitter
10 dBm
NRZ
NRZ
Port 1
Port 2
Photodetector type
PIN photodiode
APD
Pigtail fiber type
Single-mode fiber
Single-mode fiber
1260 nm to 1570 nm
1290 nm to 1570 nm
18.0 dBm
23.0 dBm for amplified

links
25 dBm for nonamplified
links
Overload level (see Note 5)
3.0 dBm
12.0 dBm
Damage level (maximum power allowed at 3.0 dBm

the input of the Rx above which the
components can be permanently damaged)
3.0 dBm
Line coding
NRZ
NRZ
Note 1: For the specific product engineering code (PEC) and wavelength for NTCA72xx, see
30 dB.
Note 4: This value does not include information about bandwidth and dispersion compensating chirp.
Note 5: The APD detector at the receiver is more sensitive to power levels than the PIN photodiode
receiver and has higher potential risk of damage to hardware.
Note 6: The Dual 2.5G WT on/off ramp circuit pack (NTCA72xx) can be damaged if too much optical
power reaches the Long Reach Receiver (Port 2). The recommended power level for that Receiver is
17 dBm, and the maximum power supported for an amplified link in 12 dBm. The power must always
be checked before connecting the receiver and must not exceed 8 dBm, even during testing. Note that
these power levels are significantly lower than for equivalent 10Gbit/s applications.
OC-192/STM-64 T/R circuit pack (NTCA06xx)

Table 10-10
OC-192/STM-64 T/R circuit pack
F4724-MOR_R80
LOS (yellow)
Active (green)


The OC-192/STM-64 T/R combines the functionality of a DWDM transmitter, receiver and demultiplexer
in one circuit pack. This single circuit pack provides both transmit and receive interface ports. The circuit
pack converts the 10 Gbit/s backplane electrical signals to an optical signal. You can provision the
OC-192/STM-64 T/R circuit pack in both SONET and SDH configurations.The frequency, accuracy and
stability of the optical signal emitted allows you to use the transmitters in a DWDM system with spacing
of 50 GHz or more between adjacent wavelengths. The OC-192/STM-64 T/R circuit pack supports AM1
and AM2.
Note: The OC-192/STM-64 T/R circuit pack is manufacture discontinued and no longer orderable. This
circuit pack is still supported by Nortel, and it is still supported in the Repeater network element.
The OC-192/STM-64 T/R is designed to be installed in the Optical Long Haul 1600 or Connect DX
mechanical bay assembly. This circuit pack is equipped with both digital and analog boards. The digital
board contains a set of application-specific integrated circuits (ASIC) and associated circuitry. The
analog board accommodates the circuitry that converts electrical signals into optical signals. It uses the
Transport Control Subsystem (TCS) platform, which includes GraceLAN and P-bus interfaces.
Both output and input connectors are located on the module faceplate. Because the OC-192/STM-64
T/R is an adapterless circuit pack, you can order the FC, ST, or SC type adapters to match the fiber
plant connector types.
Three LEDs are located on the faceplate. The LEDs identify an LOS (yellow LED), an active circuit pack
(green LED), or a failed circuit pack (red LED). A red LED that is ON usually indicates a partial or
complete failure of the circuit pack (for example, a Circuit pack fail alarm). A red LED that is ON can
also indicate a mismatch condition on the circuit pack (for example, a Circuit pack mismatch alarm).
OAM&P features
The OC-192/STM-64 T/R has the following features:
alarm reporting
Specifications
Connector type

wave linewidth)
Minimum laser Side Mode Suppression Ratio 40 dB

(SSR)

Pigtail fiber type
Single-mode fiber
Wavelength range
1528.77 to 1603.58 nm

following accuracy.
0.25 dBm
This worst-case end-of-life number includes connector
loss, aging and temperature degradation.
Chirp polarity
14 dB
Optical return loss
27 dB

10 dBm
Photodetector type
PIN photodetector
Pigtail fiber type
Single-mode fiber
1290 nm to 1603 nm
12 dBm for amplified links (see Note 5)

Overload level (input power to the Rx must be 0 dBm (see Note 6)

Damage level (maximum power allowed at the 5 dBm (see Note 7)
Line coding

30 dB.
Note 5: The sensitivity level is the minimum optical power for which the interface meets an uncorrected
bit-error ratio of 1x10-10 with forward error correction (FEC) disabled. The guaranteed end-of-life
performance is 14 dBm at a bit-error ratio of 1x10-13.
Note 6: The overload level is the maximum optical power for which the interface meets an uncorrected
bit-error ratio of 1x10 -12 with FEC disabled or 1x10-15 with FEC enabled.
Note 7: The damage level is the maximum optical power for which no damage to the components
occurs.
OC-192/STM-64 T/R (TriFEC) circuit pack (NTCF06xx)

Table 10-11
OC-192/STM-64 T/R (TriFEC) circuit pack
F4724-MOR_R80
LOS (yellow)
Active (green)


The OC-192/STM-64 T/R (TriFEC) circuit pack combines the functionality of a DWDM transmitter,
receiver, and demultiplexer in one circuit pack. This single circuit pack provides both transmit and
receive interface ports. The circuit pack converts the 10 Gbit/s backplane electrical signal to an optical
signal. You can provision the OC-192/STM-64 T/R (TriFEC) circuit pack in both SONET and SDH
configurations.The frequency, accuracy, and stability of the optical signal emitted allows you to use the
transmitters in a DWDM system with spacing of 50 GHz or more between adjacent wavelengths. The
OC-192/STM-64 T/R (TriFEC) circuit pack supports analog maintenance (AM1 and AM2). The
OC-192/STM-64 T/R (TriFEC) circuit pack provides provisionable error correction: no error correction,
single FEC, and TriFEC.
The OC-192/STM-64 T/R (TriFEC) circuit pack is designed to be installed in the Optical Long Haul 1600
or Optical Connect DX mechanical bay assembly. This circuit pack is equipped with both digital and
analog boards. The digital board contains a set of application-specific integrated circuits (ASIC) and
associated circuitry. The analog board accommodates the circuitry that converts electrical signals into
optical signals. It uses the Transport Control Subsystem (TCS) platform, which includes GraceLAN and
P-bus interfaces.
Both output and input connectors are located on the module faceplate. Because the
OC-192/STM-64 T/R (TriFEC) circuit pack is an adapterless circuit pack, you can order the FC or SC
type adapters to match the fiber plant connector types.
OAM&P features
The OC-192/STM-64 T/R (TriFEC) circuit pack has the following features:
alarm reporting
analog maintenance (AM) support
provisionable error correction (no error correction, single FEC, and TriFEC)
Specifications
Connector type

wave linewidth)

Minimum laser Side Mode Suppression Ratio 40 dB
(SSR)
Pigtail fiber type
Single-mode fiber
Wavelength range
1528.77 to 1603.13 nm

following accuracy.
0.25 dBm
This worst-case end-of-life number includes connector
loss, aging and temperature degradation.
Chirp polarity
14 dB

10 dBm
Photodetector type
PIN photodetector
Pigtail fiber type
Single-mode fiber
1290 nm to 1603 nm
12 dBm for amplified links (see Note 5)

14 dBm for nonamplified links
Overload level (input power to the Rx must be 0 dBm (see Note 6)

Damage level (maximum power allowed at the 5 dBm (see Note 7)

Note 1: For the specific product engineering codes (PECs) and wavelengths for NTCF06xx, see
30 dB.
Note 5: The sensitivity level is the minimum optical power for which the interface meets an uncorrected
bit-error ratio of 1x10-10 with forward error correction (FEC) disabled. The guaranteed end-of-life
performance is 14 dBm at a bit-error ratio of 1x10-13.
Note 6: The overload level is the maximum optical power for which the interface meets an uncorrected
bit-error ratio of 1x10 -12 with FEC disabled or 1x10-15 with FEC enabled.
Note 7: The damage level is the maximum optical power for which no damage to the components
occurs.

Table 10-12
OC-192/STM-64 XR circuit pack
F4723-MOR_R80
LOS (yellow)
Active (green)


The OC-192/STM-64 XR combines the functionality of a receiver and a DWDM regenerator transmitter
in one circuit pack. Used in a regenerator, this single circuit pack replaces the regenerator transmitter
and receiver circuit packs. The frequency, accuracy, and stability of the optical signal emitted allows
these transmitters to be used in a DWDM system with spacing of 50 GHz or more between adjacent
wavelengths. The OC-192/STM-64 XR circuit pack supports both AM1 and AM2.
Note: The OC-192/STM-64 XR circuit pack is manufacture discontinued and no longer orderable. This
circuit pack is still supported by Nortel, and it is still supported in the Repeater network element.
The OC-192/STM-64 XR is designed to be installed in the Optical Long Haul 1600 mechanical bay
assembly. The OC-192/STM-64 XR is equipped with an electro-optic modulator, photo detector, and
the required RF circuitry to convert the 10 Gbit/s modulated optical signal to the electrical domain for
3R regeneration and overhead processing. The signal is then converted back to the optical domain with
a specific carrier wavelength.
One output connector is located on the module faceplate. You can order the FC, or SC type adapters
to match the fiber plant connector types.
OAM&P features
The OC-192/STM-64 XR has the following features:
alarm reporting
Specifications
Connector type

wave linewidth)
Minimum laser Side Mode Suppression Ration 40 dB

(SSR)
Pigtail fiber type
Single mode fiber
Wavelength range
1528.77 to 1603.13 nm


accuracy below.
0.25 dBm
This number is a worst-case end-of-life (EOL) number
that includes connector loss, aging and temperature
degradation.
Chirp polarity
14 dB

10 dBm
Photodetector type
PIN photodetector
Pigtail fiber type
Single-mode fiber
1290 nm to 1603 nm


Line coding
Note 1: For specific product engineering codes (PECs) and wavelengths for NTCA04xx, see Ordering
Guide (NTY311KL).
30 dB.

Table 10-13
OC-192/STM-64 XR/WT circuit pack
F4723-MOR_R80
LOS (yellow)
Active (green)


Overview
The OC-192/STM-64 XR/WT circuit pack receives, regenerates, and transmits signals. The circuit pack
operates as a full 10 Gbit/s SONET/SDH regenerator (traffic mode set to REGEN for XR) or as a thin
10 Gbit/s SONET/SDH regenerator (traffic mode set to 3R for WT). The OC-192/STM-64 XR/WT circuit
pack offers 160-wavelength DWDM functionality for either XR or WT regeneration.
The OC-192/STM-64 XR/WT circuit pack combines the functionality of a Wavelength Translator, Dense
regenerator, and DWDM regenerator transmitter in one circuit pack. The frequency, accuracy, and
stability of the optical signal emitted allow these transmitters to be used in a DWDM system with spacing
of 50 GHz or more between adjacent wavelengths. The OC-192/STM-64 XR/WT circuit pack supports
both AM1 and AM2.
The OC-192/STM-64 XR/WT circuit pack is designed to be installed in the Optical Long Haul 1600
Repeater bay. The OC-192/STM-64 XR/WT circuit pack is equipped with an electro-optic modulator,
photo detector, and the required RF circuitry to convert the 10 Gbit/s modulated optical signal to the
One output connector is located on the module faceplate. You can order the FC, or SC type adapters
to match the fiber plant connector types.
OAM&P features
The OC-192/STM-64 XR/WT circuit pack has the following features.
alarm reporting
traffic mode provisioning (3R or REGEN)
Specifications
Connector type

wave linewidth)
Minimum laser Side Mode Suppression Ration 40 dB

(SSR)

Pigtail fiber type
Single-mode fiber
Wavelength range
1528.77 to 1603.13 nm
Configured from 10 to 1.5 dBm subject to the following

accuracy.
0.25 dBm
This number is a worst-case end-of-life (EOL) number
that includes connector loss, aging and temperature
degradation.
Chirp polarity
14 dB

10 dBm
Photodetector type
PIN photodetector
Pigtail fiber type
Single mode fiber
1290 nm to 1603 nm


Line coding
Note 1: For specific product engineering codes (PECs) and wavelengths for NTCF04xx, see Ordering
Guide (NTY311KL).
30 dB.
Note 4: This value does not include information about bandwidth and dispersion compensating chirp.
Dual GE circuit pack (NTCA90CA, NTCA90EA, or NTCA90GA)

Table 10-14
DX3650p
Optical connectors
(4 places)
Fiber carrier
1-2
Upper
latch
Dual GE
1-2
lG
iDua
Carrier
handle
OUT
OUT 1
IN OUT
IN
IN
OUT 2
1
2
IN
Fiber clip
1
2
Lower
latch
Side view
Front view
The Dual GE circuit pack maps two independent Gigabit Ethernet traffic streams onto two separate
SONET/SDH STS-24c/VC-4-8c payloads carried on the OC-192/STM-64 SONET/SDH network. The
circuit pack therefore allows Ethernet traffic to interconnect over an Optical Long Haul 1600 network in
a point-to-point fashion.
The Dual GE circuit pack is designed to be installed in a Wavelength Combiner application in an Optical
Long Haul 1600 Repeater bay. The Dual GE circuit pack is equipped with an electro-optic modulator,
photodetector and the required circuitry to map the GE traffic onto the SONET/SDH STS-24c/VC-4-8c
payload which is applied to the 10G T/R of the Wavelength Combiner. Four LEDs are located on the
faceplate: two yellow LEDs to indicate the link status of each port, one green LED to indicate the circuit
pack is active, and one red LED to indicate a circuit pack failure.

OAM&P features
The Dual GE circuit pack has the following features:
Two GE services within one circuit pack
SONET/SDH level management through standard NE UI and OPC interfaces
Data management through SNMP and a Bay Command Console command line interface resident on
the GE circuit pack
alarm reporting
SONET/SDH path PM for each STS-24c/VC-4-8c payload
Specifications
1000 BASE-LX
1000 BASE-SX
1000 BASE-ZX
Product Engineering Code
NTCA90CA
NTCA90EA
NTCA90CA
Weight
3.2 kg (7 lbs)
3.2 kg (7 lbs)
3.2 kg (7 lbs)
Maximum power dissipation 31 W
31 W
31 W
Connector type
SC (see Note )
SC (see Note )
SC (see Note )
Reach
10 km for 9 m or 10 m 275 m for 62.5 m MMF 70 km

SMF (only achievable if 550 m for 50 m MMF
far-end uses laser of
equivalent quality)
Fabry-Perot (FP) laser
Vertical cavity surface Distributed Feedback

emitting laser (VCSEL) (DFB) laser
Spectral width - rms
1.4 nm (typical)
2.8 nm (maximum)
0.85 nm
1.0 nm
Pigtail fiber type
Single-mode fiber
Multi-mode fiber
(1550 nm)
single-mode optical
fiber (70 km reach)
Wavelength range
1272 nm to 1355 nm
830 nm to 860 nm
1480 to 1580 nm
Output power
3 dBm to 9.5 dBm

(when using 9 m or
10 m SMF)
Not provisionable
1.5 dBm to 9.5 dBm

(when using 50 m or
62.5 m SMF)
Not provisionable
2.0 dBm to 3.0 dBm

(for SMF)
NRZ
NRZ
NRZ
< 0.5 dBm (when using

50 m or 62.5 m
MMF)
Not provisionable

1000 BASE-LX
1000 BASE-SX
1000 BASE-ZX
Photodetector type
GaAs PIN Photodiode
InP PIN Photodiode
GaAs PIN Photodiode
Pigtail fiber type
Single-mode fiber
Multi-mode fiber
(1550 nm)
single-mode optical
fiber (70 km reach)
1270 nm to 1570 nm
770 nm to 860 nm
1100 nm to 1600 nm
Receiver range
20.0 dBm to 3.0 dBm 17.0 dBm to 0.0 dBm
Stressed sensitivity
14.4 dBm at BER

10-12
23.0 dBm to 3.0

dBm
18 dBm at BER 10-12

12.5 dBm at BER
-12
10 for 62.5 m MMF
13.5 dBm at BER
10-12 for 50 m MMF
Overload level (input power 3.0 dBm

to the Rx must be equal or
below this value so that
guaranteed link BER and
jitter tolerance are met)
0.0 dBm
3.0 dBm
Damage level (maximum

power allowed at the input
of the Rx above which the
components can be
permanently damaged)
6 dBm
N/A
6 dBm
Optical return loss
12 dB
12 dB
12 dB
Note: SC connectors are recommended for Optical Long Haul 1600 applications.
Optical switch module (OSM) circuit pack (NTCA39AA)

Table 10-15
OTP1405p
Latch
(2 places)
Fiber
carrier
Carrier
handle
OUT C
IN
OUT D
IN
Optical
connector
(typical)

The optical switch module (OSM) switches optical traffic at the photonic level using the latest optical
switching technology. The OSM is wavelength independent and enables flexibility and reliability in
designing optical protection rings. The OSM accepts any OC-192/STM-64 or OC-192c/STM-64c signal
from a client router, splits it into two identical signals and selects the best signal at the receiving end.
Install the OSM circuit pack in the Optical Long Haul 1600 mechanical bay assembly configured as a
Repeater network element. The circuit pack contains two printed circuit boards. The motherboard
consists of the common TCS circuitry, FPGA, PUPs, and LEDs. The four LEDs indicate the state of the
OSM: LOS (two yellow LEDs), an active circuit pack (green LED), or a failed circuit pack (red LED). A
red LED that is ON usually indicates a partial or complete failure of the circuit pack (for example, a
Circuit pack fail alarm). A red LED that is ON can also indicate a mismatch condition on the circuit
pack (for example, a Circuit pack mismatch alarm). The daughter board consists of the optical
components (50/50 optical splitter and 2 x 2 optical switch) as well as the associated drive circuitry.
OAM&P features
The OSM has the following features:
alarm reporting
failure detection and signal monitoring
protection switching signalling
Specification
Product engineering code (PEC) NTCA39AA (see Note 1)
Connector type
Optical switch
2 x 2 solid state polymer waveguide
Pigtail fiber type
Single-mode fiber
Wavelength range
1290 nm to 1330 nm
Operating window No. 1
Crosstalk: >24 dB
Wavelength range
1530 nm to 1565 nm
Operating window No. 2
Crosstalk: >27 dB
Insertion loss
< 4 dB
PDL
< 0.3 dB
Return loss
> 40 dB
Switching time
< 2 ms
Max optical input
2 dB

Other
Detector
PIN photodiode, single mode
Splitter
50/50%
Tap coupler
95/5%
Note 1: For specific product engineering codes (PEC) and wavelengths for NTCA39AA, see Ordering
Guide (NTY311KL).
Note 2: SC connectors are recommended for Optical Long Haul 1600 applications.
11-1
11-
Chapter overview
This chapter provides an overview of the terminology used in the descriptions
of overhead processing.
Section
Page
Description of overhead bytes
11-2
Service transparency values for overhead bytes
11-3
11-2 Appendix A: Overhead processing
Description of overhead bytes

Table 11-1 describes the overhead bytes.
Table 11-1
Overhead byte descriptions
Overhead bytes
Function
Description
A1, A2
Framing
Aligns frames to distinguish the overhead from the

payload
B1
Section parity
Determines if a transmission error has occurred over

a section/RS
B2
Line parity
Determines if a transmission error has occurred over

a line/MS
C1 (J0)
Section trace
Identifies STS-n/STM-n using nth byte. C1 refers to all

N bytes of an STS-N/STM-N signal. J0 refers to first
STS-1/STM-1 byte of C1.
K1/K2
Used to signal automatic protection switching (APS)
D1 - D3
Section/RS DCC
Provides a 192 Kbit/s datacomm channel between

STEs
E1
Local Orderwire
64 Kbit/s voice channel for craftspeople on STEs and

LTEs
F1
User byte
Defined only for STS-1/STM-1 # 1. For use by

network provider
D4 - D12
Line/MS DCC
Provide a 576 Kbit/s datacomm channel between

LTEs
E2
Express Orderwire
64 Kbit/s voice channel for craftspeople on LTEs
H1 - H3
Payload pointers
Points to the start of the signal payload envelope

(SPE)
S1/Z1
Sync status
Used for synchronization status messages from the

network element
Z2
FEBE
The total errors as detected by B2 mismatches
Appendix A: Overhead processing 11-3

Some service applications (such as wavelength leasing and IP/ATM transport
over SONET/SDH) require transparency from unnecessary SONET/SDH
multiplexing or processing. This section defines the terminology used to
characterize the level of transparency.
Not all overhead bytes are provisionable. Provisionable bytes can be set to
specific service transparency values based on the application. See Table 11-2
for descriptions of transparency values for overhead bytes. For a list of
non-provisionable and provisionable bytes, as well as the allowable service
transparency values for a specific application, refer to the Overhead
processing section in the appropriate chapter for the application.
Note: For specific instructions on changing the value of a provisionable
byte, refer to Provisioning and Operations Procedures, 323-1801-310.
Table 11-2
Service transparency Description
value
Regenerated
Complete electrical regeneration of the payload and overhead data. The

overhead data is processed according to defined standards (for example, all
section/RS overhead is processed at section/RS terminating elements).
Inserted
Preset data is inserted into the output stream (for example, all 1 pattern is
inserted into the payload upon an alarm indication signal [AIS] condition).
Pass-through
Pass-through of data with monitoring (for example, section trace byte J0 is

pass-through since the system can mismatch on the Rx value).
Recalculated
Received data is terminated; output of data is either recalculated or

compensated based on the received data (for example, section parity B1 is
recalculated at STE).
Terminated
Received data is terminated and output is either not generated or the output
content has no relation to the received data (for example, LOH bytes are
terminated at LTE or J0 is terminated when section trace is disabled; that is,
J0 = 1 regardless of the Rx value).
Transparent
Pass-through of data untouched and without monitoring (for example, payload

is transparent).
Interleave
Inserts STS-1/STM-1 numbering in the C1 byte.
Section trace
Enables full section trace feature.
11-4 Appendix A: Overhead processing
12-1
12-
Chapter overview
This chapter provides a general description of TriFEC functionality. For
specific information on TriFEC functionality in Wavelength Translator or
Wavelength Combiner applications, refer to Chapter 3, Wavelength
Translator application or Chapter 4, Wavelength Combiner application.
TriFEC improves the link-budget performance over applications with no error
correction or single FEC. Therefore, TriFEC-enabled optical links can cover
longer distances in each span. (For information on link budgets, refer to 1600G
Amplifier Optical Layer Applications Guide [NTY315DX].) TriFEC also
enhances the transparency of Wavelength Combiner and Wavelength
Translator applications.
Section
Page
TriFEC-capable circuit packs
12-2
Description of TriFEC
12-2
Forward error correction provisioning
12-8
Performance monitoring counts for TriFEC-capable circuit packs
12-10
Alarms and alerts affected by TriFEC
12-11
Network applications using TriFEC
12-12
12-2 Appendix B: TriFEC applications

Optical Long Haul 1600 supports the TriFEC-capable circuit packs listed in
Table 12-1.
Table 12-1
Supported TriFEC-capable circuit packs
Circuit packs
PEC
Notes
10G WT (TriFEC)
NTCF07xx
NTCF06xx
10G WT SR (TriFEC)
NTWR07AA
See Note .
Note: For information on short-reach optics, refer to Appendix D: Short-reach optics on page 14-1.
Description of TriFEC
Error-control coding provides a method for protecting data from errors. The
error-control algorithm detects and corrects errors, which improves the
integrity of the optical link. Before Optical Long Haul 1600 Release 5, the only
available error-control algorithm was single forward error correction (single
FEC), which was available only on the OC-192/STM-64 T/R circuit pack.
Optical Long Haul 1600 Release 5 introduced a more powerful detection and
correction algorithm than single forward error correction: triple forward error
correction (TriFEC).
TriFEC is implemented in unused bytes of the SONET or SDH overhead.
TriFEC is independent of the Open Systems Interconnection (OSI)
architecture that is used for operations, administration, maintenance, and
provisioning (OAM&P) data communications. TriFEC provides a method of
error control whereby the receiving circuit pack can detect and correct data
transmission errors. To detect and correct transmission errors in the SONET or
SDH payload, the transmitter embeds additional parity bits in an unused
portion of the SONET or SDH overhead. These additional parity bits enable
automatic detection and correction of errors at the receiving end of an optical
link.
You can provision forward error correction on the TriFEC-capable circuit
packs to the following values:
no error correction (NONE)
single FEC (FEC)
TriFEC (TFEC)
Appendix B: TriFEC applications 12-3
Table 12-2 lists the supported forward error correction modes for all transport
circuit packs.
Table 12-2
Error correction for transport circuit packs
Circuit pack
(see Note 1)
PEC
Supported NE UI forward error

correction values
OC-192/STM-64 XR/WT
NTCF04xx
NONE
10G WT SR (TriFEC)
NTWR07AA
NONE, FEC, TFEC (see Note 2)

(see Note 3)
NTCF06xx
NONE, FEC, TFEC
10G WT (TriFEC)
NTCF07xx
NONE, FEC, TFEC
NTCA30xK
NONE
OC-48/STM-16 T/R SR
NTCA30CK
NONE
OC-48/STM-16 T/R (1310 nm)
NTCA30AL
NONE
NTCA90xA
NONE
OC-192/STM-64 T/R (see Note 3)
NTCA06xx
NONE, FEC
OC-192/STM-64 XR
NTCA04xx
NONE
10G WT
NTCA07xx
NONE
2.5G WT
NTCA70xx
NONE
NTCA72xx
NONE
Note 1: The latest release supports all circuit packs listed in this table.
Note 2: FEC capability is available on the receiver only. The transmitter is equipped with short-reach
optics.
Note 3: The Wavelength Combiner circuit pack groups at both terminals must be originally equipped
with the same type of 10 Gbit/s transmitters (TriFEC-capable or non-TriFEC). Failure in following this rule
will probably cause a Protection scheme mismatch or Channel ID mismatch alarm to be raised on the
subtending OC-48 or TN-16X equipment and cause subsequent protection path failures.
Improved link budgets

TriFEC improves the link-budget performance over applications with no
forward error correction or single FEC. Therefore, TriFEC-enabled optical
links can cover longer distances in each span than single FEC-enabled optical
links.
Note 1: In general, deploy TriFEC-capable circuit packs at terminal sites,
and deploy non-TriFEC circuit packs at regenerator sites. Follow this
guideline if the number of regenerators in the network is within the link
budget specifications and derating is not required. If the number of
regenerators surpasses the limit and derating is required, then you can
deploy TriFEC-capable circuit packs at regenerator sites to avoid derating.
For more information, contact Nortel.
Note 2: For more information on link budgets for 1600G Amplifier
applications, refer to 1600G Amplifier Optical Layer Applications Guide
(NTY315DX). For special configurations involving MOR Plus amplifier
circuit packs, contact Nortel for assistance.
Since you can also provision the error correction mode on the TriFEC-capable
circuit packs to no error correction (NONE) or single FEC (FEC), the
TriFEC-capable circuit packs are compatible with the link budgets for
applications with no error correction or single FEC on the optical link.
Link budgets for new network deployments
Figure 12-1 on page 12-5 represents a new Optical Long Haul 1600 network
deployment that includes 10G WT (TriFEC) circuit packs at the terminal sites
(on-ramp and off-ramp sites). As shown in Figure 12-1, TriFEC is enabled in
the transmit direction of the on-ramp circuit pack and in the receive direction
of the off-ramp circuit pack. Figure 12-2 on page 12-6 represents a new Optical
Long Haul 1600 network deployment that includes OC-192/STM-64 T/R
(TriFEC) circuit packs at the terminal sites. As shown in Figure 12-2, TriFEC
is enabled in the transmit and receive directions of both circuit packs at each
end of the optical link. The two new networks benefit from extended reach in
each span over networks with no forward error correction.
You can introduce TriFEC-capable circuit packs in initial deployments. If you
enable TriFEC, the improved link budgets apply.

Figure 12-1
New network deploying 10G WT (TriFEC) circuit packs for extended reach
Tx
10G WT
(TriFEC)
Mux
40
C-Band
+
40
L-Band
Tx
Rx
Demux
OTP2214p
Channel propagation
(Eastbound)
FEC = TFEC
FEC = NONE
40
C-Band
+
40
L-Band
Tx FEC = NONE
Rx FEC = TFEC
Rx
10G WT
(TriFEC)
Rx
10G WT
(TriFEC)
Mux
40
C-Band
+
40
L-Band
Tx
Rx
Demux
80 unidirectional
(Direction 1)
Channel propagation
(Westbound)
FEC = NONE
FEC = TFEC
Tx
10G WT
(TriFEC)
40
C-Band
+
40
L-Band
Tx FEC = TFEC
Rx FEC = NONE
80 unidirectional
(Direction 2)
Terminal site
Line site
Terminal site
Legend
1600G Amplifier - unidirectional
Note 1: Each on-ramp and off-ramp circuit pack must have the same error correction provisioning.
Note 2: TFEC refers to the network element user interface (NE UI) command for enabling TriFEC.

Figure 12-2
New network deploying OC-192/STM-64 T/R (TriFEC) circuit packs for extended reach
OTP2940t
OC-48/STM-16
T/R
OC-192/
STM-64
T/R
(TriFEC)
OC-192/
STM-64
XR
OC-192/
STM-64
XR
OC-48/STM-16
T/R
FEC = TFEC
FEC = TFEC
Terminal
Site
OC-192/
STM-64
T/R
(TriFEC)
Regenerator
Site
Terminal
Site

Note 2: For the OC-192/STM-64 T/R (TriFEC) circuit pack Tx FEC and Rx FEC are set
concurrently when you set the FEC mode.
Note 3: The error correction setting must be identical at both ends of the optical
link. In this example, the error correction setting at each terminal site is set
to TFEC to enhance the link budget.
Improved link budgets may not be required for new network deployments. For
example, if network expansion to introduce new services is not expected or if
the required reach of the optical link can be achieved using existing link
budgets, you can continue to deploy the non-TriFEC circuit packs, rather than
the TriFEC-capable circuit packs. In this case, the improved link budgets for
TriFEC-enabled applications do not apply.

Link budgets for existing networks
To anticipate requirements for future applications that take advantage of

unused wavelengths, you can improve the link-budget margin by upgrading
existing optical links to TriFEC-capable circuit packs.
If network expansion to introduce new services is not expected and
transparency across the optical link is required, then the TriFEC-capable WT
circuit packs are not required. Maintain the non-TriFEC WT circuit packs.
Figure 12-3 represents an existing Optical Long Haul 1600 network that
provides full transparency using the 10G WT circuit packs (without TriFEC
functionality) at the terminal sites (on-ramp and off-ramp sites). In this case,
the improved link budgets for TriFEC-enabled applications do not apply.
Figure 12-3
Existing network with 10G WT circuit packs for transparency
40
C-Band
+
40
L-Band
Mux
Tx
10G WT
Demux
OTP2213p
Channel propagation
(Eastbound)
B1= pass-through
Rx
10G WT
40
C-Band
+
40
L-Band
B1= pass-through
Rx
10G WT
B1= pass-through
Mux
40
C-Band
+
40
L-Band
Demux
80 unidirectional
(Direction 1)
Channel propagation
(Westbound)
Tx
10G WT
40
C-Band
+
40
L-Band
B1= pass-through
80 unidirectional
(Direction 2)
Terminal site
Line site
Terminal site
Legend
1600G Amplifier - unidirectional
Forward error correction provisioning

From the NE UI, you can provision forward error correction for
TriFEC-capable circuit packs to the following values:
NONE (no forward error correction)
FEC (single FEC)
TFEC (TriFEC)
You can set single FEC or TriFEC on the transmit and receive directions of the
optical line/MS using TriFEC-capable circuit packs.
ATTENTION
In-service provisioning of forward error correction modes (either Tx FEC or
Rx FEC) is not supported. Provision the forward error correction mode
during a service interruption (scheduled maintenance) or before the network
is placed in-service.
When you provision the forward error correction mode for TriFEC-capable
OC-192/STM-64 T/R circuit packs, the forward error correction in the
transmit and receive directions are set simultaneously to the same value.
You must provision the transmit and receive forward error correction modes
on the TriFEC-capable WT circuit packs independently. This flexibility is
available because the required error correction mode is different at the
transmitter and receiver of the circuit pack that is equipped at a terminal site.
You must, however, provision Tx FEC at the on-ramp site and Rx FEC at the
off-ramp site of an optical link to the same value. You must set the error
correction mode to NONE on the customer facing optical path.
ATTENTION
For applications using TriFEC-capable WT circuit packs, you must set Tx
FEC and Rx FEC on the optical-facing link to the same value. If you do not
set Tx FEC and Rx FEC on the optical-facing link to the same value, the
FEC provisioning mismatch alarm is raised and FEC will not be
implemented on the optical line/MS. As such, Line/MS FEC will not
accumulate on the receiving circuit pack and errors on the link will not be
corrected.
When you change the error correction mode on FEC-capable or

TriFEC-capable circuit packs, the signal degrade threshold is automatically
reprovisioned. For details on the automatically provisioned signal degrade
threshold value, refer to the following tables.
For TriFEC-capable 10G WT circuit packs, see Table 3-7 on page 3-13.
Note: For 10G WT circuit packs, the signal degrade threshold is relevant
only if the circuit packs are part of an ODPR circuit pack group.
For OC-192/STM-64 T/R circuit packs, see Table 4-5 on page 4-19.
For more information on TriFEC and signal degrade in Wavelength Combiner

applications, see Signal degrade threshold on page 4-21.
For more information on TriFEC and signal degrade in ODPR applications,
see Signal degrade threshold and protection switching in ODPR applications
on page 5-23.
For specific instructions on provisioning the error correction and the signal
degrade threshold, refer to Provisioning and Operations Procedures,
323-1801-310.
Editing the forward error correction mode

The Edit facility command in the OCn/STM-n Facility Menu allows you to
provision error correction. Figure 12-4 displays the Edit command in the
OCn/STM-n Facility Menu.
Figure 12-4
Edit command in OCn/STM-n Facility Menu
OTP2786t
NE 1621>2
Enter the facility type:
[ OC192, OC48 ]
? oc192 g7
Please select on of the following:
CLFI - Common Language Facility Identifier
SD - Signal Degrade Threshold
FEC - Forward Error Correction
STF - Section Trace Format
STM - Section Trace (J0/C1) Mode
RXST - 16 Byte Expected Rx Section Trace
TXST - 16 Byte Tx Section Trace
BRXST - 1 Byte Expected Rx Section Trace
BTXST - 1 Byte Tx Section Trace
TXSSM - Tx SSM Global Mode
RXSSM - Rx SSM Global Mode
TXQC - Tx SSM Quality Code Override
RXQC - Rx SSM Quality Code Override
?fec
You are about to execute a service affecting command!
Enter the Forward Error Correction:
[ FEC, NONE, TFEC ]
?fec
Are you sure?
[ Y, N ]
?y
Command successful
Querying the forward error correction mode

The Query facility command in the OCn/STM-n Facility Menu displays the
applied error correction value(s).
Performance monitoring counts for TriFEC-capable circuit packs

The Display facility PM Counts command in the Facility Performance Menu
displays the uncorrected line/MS parity errors (line/MS CV or B2 errors) and
the number of errors corrected on the FEC bytes (line/MS FEC counts) (see
Figure 12-5). You can monitor line/MS counts for Wavelength Combiner
applications and Wavelength Translator applications with TriFEC.

Figure 12-5
Output of Display facility PM Counts command in the Facility Performance
Menu
OTP2134T
Unit : OC192
NE Id: 2625
Mode : SONET
G7
Direction: RX
Location : NEND
Untimed Start: 2004/12/24 19:11:04
15-minute
current
last
Sect
Sect
Sect
Sect
Line
Line
Line
Line
Line
Line
CV
ES
SES
SEFS
CV
ES
SES
UAS
FC
FEC
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1-day
Untimed
current
last
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
For more information on the performance monitoring procedures for facilities,

refer to Performance Monitoring Procedures, 323-1801-520.
Alarms and alerts affected by TriFEC

TriFEC functionality affects the FEC provisioning mismatch alarm and the
Line Rx FEC threshold 1/2 / MS Rx threshold 1/2 alert.
Note: For more information on clearing these alarms and alerts, refer to
Trouble Clearing and Module Replacement, 323-1801-543.
FEC provisioning mismatch alarm
The FEC provisioning mismatch alarm is raised when error correction (FEC
or TriFEC) is enabled on the network element at one end of the section/RS or
line/MS and does not match at the other end. This alarm is also raised when
error correction (FEC or TriFEC) is enabled, but the supporting hardware does
not have the corresponding error correction capability.
Line Rx FEC threshold 1/2 / MS Rx threshold 1/2 alert
The Line Rx FEC threshold 1/2 / MS Rx threshold 1/2 alert is raised if the
number of FEC or TriFEC errors surpasses the limit set by the provisioned
threshold 1 or threshold 2.
Network applications using TriFEC

The Wavelength Translator, ODPR, and Wavelength Combiner applications
can include TriFEC-capable circuit packs. TriFEC-capable circuit packs must
be deployed at specific sites along the optical link, as described in this section.
Wavelength Translator and ODPR applications with TriFEC
Figure 12-6 and Figure 12-7 represent a Wavelength Translator application
and an ODPR application, respectively, with TriFEC-capable WT circuit
packs deployed at the terminal sites.
Figure 12-6
OTP2215T
10G WT
(TriFEC)
SONET
or SDH
Equipment
10G WT
10G WT
(TriFEC)
10G WT
(TriFEC)
10G WT
10G WT
(TriFEC)
Terminal
Site
Regenerator
Site
Terminal
Site
SONET
or SDH
Equipment
Figure 12-7
OTP2529T
SONET
or SDH
Equipment
10G WT
(TriFEC)
10G WT
10G WT
(TriFEC)
10G WT
(TriFEC)
10G WT
10G WT
(TriFEC)
OSM
OSM
10G WT
(TriFEC)
10G WT
10G WT
(TriFEC)
10G WT
(TriFEC)
10G WT
10G WT
(TriFEC)
Terminal
Site
Regenerator
Site
Terminal
Site
SONET
or SDH
Equipment
Deploy TriFEC-capable WT circuit packs at terminal sites (on-ramp and

off-ramp sites). Deploy non-TriFEC WT circuit packs (without TriFEC
functionality) or XR circuit packs at regenerator sites.
Note: In general, deploy TriFEC-capable circuit packs at terminal sites,
Figure 12-8 represents a Wavelength Combiner application with
TriFEC-capable T/R circuit packs deployed at the terminal sites.
Figure 12-8
OTP2216T
OC-192/
STM-64
T/R
(TriFEC)
Terminal
Site
OC-192/
STM-64 XR
OC-192/
STM-64 XR
Regenerator
Site
OC-192/
STM-64
T/R
(TriFEC)
Terminal
Site

originally equipped with the same type of 10 Gbit/s transmitters
(TriFEC-capable or non-TriFEC). Failure in following this rule will probably
cause a Protection scheme mismatch or Channel ID mismatch alarm to be
raised on the subtending OC-48 or TN-16X equipment and cause subsequent
protection path failures.
The regenerator site is a Repeater network element that can contain either
non-TriFEC WT circuit packs or XR circuit packs. The WT circuit packs
provide thin SONET or SDH regeneration, whereas the XR circuit packs
provide full SONET or SDH regeneration.
Selecting TriFEC-capable or non-TriFEC circuit packs
To determine whether to deploy TriFEC-capable circuit packs or non-TriFEC
circuit packs at terminal sites, refer to Improved link budgets on page 12-4,
and Table 12-3 on page 12-14.
Table 12-3 lists recommended deployment scenarios for terminal sites, based
on network requirements.
Table 12-3
Deployment scenarios at terminal sites based on network requirements
Description
Requirements
Recommended deployment scenario

at terminal sites only
New network
deployment
Thin SONET or SDH

regeneration across the
link (Repeater)
For Wavelength Translator and ODPR applications:

deploy non-TriFEC WT circuit packs at terminal sites
No extra link-budget
margin required
New network
deployment
For Wavelength Combiner applications: deploy

non-TriFEC T/R circuit packs at terminal sites
Extra link-budget margin For Wavelength Translator and ODPR applications:

deploy TriFEC-capable circuit packs at terminal
required for future
sites
applications
Extended span reach
For Wavelength Combiner applications: deploy

TriFEC-capable circuit packs at terminal sites
Note: To take advantage of improved link budgets,

configure the optical links with TriFEC on both the
transmit and receive directions.
Existing networks
with non-TriFEC
circuit packs
Thin SONET or SDH

regeneration across the
link (Repeater)
Maintain non-TriFEC circuit packs at terminal sites.

(No network upgrade is required.)
Maintain existing network

services
Existing networks
with non-TriFEC
circuit packs
Extra link-budget margin An upgrade is required. An in-service upgrade is

required for future
possible only if a protection path is available.
applications
For Wavelength Translator and ODPR applications:
upgrade to TriFEC-capable circuit packs at terminal
sites
For Wavelength Combiner applications: upgrade to
TriFEC-capable circuit packs at terminal sites
Note: To take advantage of improved link budgets,

configure the optical links with TriFEC on both the
transmit and receive directions.

Enabling TriFEC on an optical link
In summary, to enable TriFEC on an optical link, follow these guidelines:

Deploy TriFEC-capable circuit packs at terminal sites. Provision TriFEC
in the transmit and receive directions at terminal sites only.
Deploy non-TriFEC circuit packs at regenerator sites. Since 10G WT
circuit packs or OC-192/STM-64 XR circuit packs are deployed at
regenerator sites, error correction is not supported (therefore eliminating
the possibility of errors in provisioning).
Note: In general, deploy TriFEC-capable circuit packs at terminal sites,
To enable error correction (single FEC or TriFEC) on the optical link, use the
NE UI to provision single FEC or TriFEC only at the terminal sites (using the
commands FEC or TFEC, respectively). If the FEC or TriFEC bytes are
terminated prior to the off-ramp circuit pack, the overall gain of the optical link
is limited. Therefore, error correction should not be provisioned at mid-span
sites.
13-1
Appendix C: Merged XR/WT circuit

packs
13-
Chapter overview
This chapter provides a description of merged XR/WT circuit packs. For
information on a specific merged XR/WT circuit pack in Dense regenerator or
Wavelength Translator applications refer to Chapter 3, Wavelength Translator
application or Chapter 4, Wavelength Combiner application.
Section
Page
Merged XR/WT circuit packs
13-1
Description of merged XR/WT circuit packs
13-1
Merged XR/WT circuit packs in a network
13-2
Traffic mode provisioning for merged XR/WT circuit packs
13-3
Alarms for merged XR/WT circuit packs
13-3
Merged XR/WT circuit packs

Optical Long Haul 1600 supports the merged XR/WT circuit packs listed in
Table 13-1.
Table 13-1
Supported merged XR/WT circuit packs
Circuit packs
PEC
Notes
OC-192/STM-64 XR/WT
NTCF04xx
Description of merged XR/WT circuit packs

Before merged XR/WT circuit packs were introduced, Wavelength Translator
and Dense regenerator applications were made available through separate
circuit packs with different line rates (10 Gbit/s or 2.5 Gbit/s). The merged
XR/WT circuit packs, introduced in Release 6, allow you to provision the
traffic mode to either full SONET/SDH regeneration (REGEN for XR) or
13-2 Appendix C: Merged XR/WT circuit packs
transparent (3R for WT) mode on the same circuit pack. Setting the traffic
mode to 3R provides an enhanced level of transparency. Setting the traffic
mode to REGEN provides full SONET/SDH regeneration.
Merged XR/WT circuit pack technology provides the following advantages:
faster, more efficient wavelength turn-up time than separate XR and WT
circuit packs
flexibility for changing network requirements
ease of sparing
Note: Merged XR/WT circuit packs do not support forward error
correction.
Merged XR/WT circuit packs in a network

Figure 13-1 shows the use of merged XR/WT circuit packs in a network
application. The regenerator site is equipped with merged XR/WT circuit
packs.
Figure 13-1
Example of merged XR/WT circuit packs in a network
OTP3006p
Terminal site
Regenerator site
Terminal site
Eastbound
2.5
Tx
Gbit/s
2.5
Gbit/s 10
2.5 Gbit/s
Gbit/s TR
2.5
Rx
Gbit/s
2.5
Gbit/s
2.5
10
Gbit/s Gbit/s
2.5
TR
Gbit/s
2.5
Tx
Gbit/s
Merged
Rx 10 Gbit/s Tx
XR/WT
Rx
Merged
Tx 10 Gbit/s Rx
XR/WT
Westbound
Off ramp
On ramp
Eastbound
Merged
Rx 10 Gbit/s Tx
XR/WT
Merged
Rx 10 Gbit/s Tx
XR/WT
Rx
SR 10G Rx
Tx SR WT
Merged
Tx 10 Gbit/s Rx
XR/WT
Merged
Tx 10 Gbit/s Rx
XR/WT
Off ramp
Westbound
10G SR
SR WT Tx
On ramp
Provisionable
to 3R for WT or
REGEN for XR
Appendix C: Merged XR/WT circuit packs 13-3
Traffic mode provisioning for merged XR/WT circuit packs

You can provision the regeneration mode of the circuit pack from the
OCn/STM-n Facility Menu menu (see Figure 13-2).
Figure 13-2
Traffic mode provisioning (3R or REGEN) OCn/STM-n Facility Menu (example)
OTP2579t
NE 1621> al
Please select one of the following:
CLFI - Common Language Facility Identifier
STF
- Section Trace Format
TM
- Traffic Mode
B1
- Section Parity (B1) Mode
STM
- Section Trace (J0/C1) Mode
RXST - 16 Byte Expected RX Section Trace
TXST - 16 Byte TX Section Trace
BRXST - 1 Byte Expected RX Section Trace
BRXST - 1 Byte TX Section Trace
? tm
Enter the traffic mode:
[ 3R, REGEN ]
? REGEN
Are you sure?
[Y,N]
?y
Command successful.
For specific instructions on changing the traffic mode for a merged XR/WT
circuit pack, refer to Provisioning and Operations Procedures, 323-1801-310.
Alarms for merged XR/WT circuit packs

The merged XR/WT circuit packs are affected by the Traffic mode
mismatch alarm. The severity of this alarm is minor, non service-affecting.
The Traffic mode mismatch alarm is raised when the provisioned traffic
mode is different between facilities that are in the same protection or (XR)
pairing group. This alarm is raised only on the merged XR/WT circuit packs.
To clear the alarm, set the expected traffic mode or take the facility
out-of-service.
Note 1: If a provisioned WT circuit pack is replaced by a merged XR/WT
circuit pack, the merged XR/WT circuit pack will default to WT mode. In
this case, a Traffic mode mismatch alarm is not raised.
Note 2: For more information on clearing alarms, refer to Trouble
Clearing and Module Replacement, 323-1801-543.
13-4 Appendix C: Merged XR/WT circuit packs
14-1
14-
Chapter overview
This chapter provides a description of circuit packs that include short-reach
(SR) optics. The following topics are covered in this chapter.
Section
Page
Short-reach circuit packs
14-1
Description of short-reach optics
14-2
Short-reach circuit packs in a network
14-2
Output power
14-3
Short-reach circuit packs

Optical Long Haul 1600 supports the short-reach circuit packs listed in Table
14-1.
Table 14-1
Supported short-reach circuit packs
Circuit packs
PEC
Notes
OC-48/STM-16 T/R SR
NTCA30CK
10G WT SR (TriFEC)
NTWR07AA
See Note 1, Note 2,

and Note 3.
Note 1: For information on TriFEC-capable circuit packs, refer to Appendix B: TriFEC applications on
page 12-1.
Note 2: The 10G WT SR (TriFEC) circuit pack has forward error correction detection capability on the
receiver only. The transmitter does not provide forward error correction capability.
Note 3: The 10G WT SR (TriFEC) circuit pack is designed for short-reach off-ramp optical interfaces at
the terminal sites for 1600G Amplifier applications that do not exceed six spans.
14-2 Appendix D: Short-reach optics
Description of short-reach optics

Circuit packs that include short-reach optics provide a cost-effective
alternative for off-ramp applications over existing circuit packs with DWDM
optics.
Optical links deployed today use DWDM technology to multiplex different
wavelengths on a single optical fiber. However, off-ramp transmitters do not
require costly DWDM lasers. Designed for short-reach applications, these
circuit packs transmit at up to distances of approximately 20 km. This distance
is ideal for inter-office applications.
Short-reach circuit packs in a network

Figure 14-1 shows an example of a 10G WT SR (TriFEC) circuit pack at a
terminal site.
Figure 14-1
10G WT SR (TriFEC) circuit pack at a terminal site
OTP2241p
Terminal site
10G WT SR (off ramp)
DWDM optics
10 Gbit/s WT
Client site
Rx
20 km
maximum
on ramp Tx
10G WT SR (TriFEC)
n+1
Tx
Short-reach
optics
off ramp Rx
Provisionable FEC
Appendix D: Short-reach optics 14-3
Output power
Circuit packs with short-reach optics are manufactured and configured for
short-distance transmissions. Therefore, these circuit packs have limited
provisioning capabilities on their transmit optical facility. These circuit packs
provide fixed Tx optical power.
Note: You cannot edit the transmit optical parameters of an
OC-48/STM-16 T/R circuit pack.
Figure 14-2 shows an example of the output of the query command in the Tx
Optical Facility Menu.
Figure 14-2
Querying the transmit optical parameters
(example of a 10G WT SR (TriFEC) circuit pack)
OTP2242t
> gr
Enter the circuit pack type:
[ OC192 ]
? OC192
Enter the circuit pack name:
[ G1 ]
? G1
Equipment Type: OC192
Primary State:
IS
Tx
Tx
Tx
Tx
Tx
Optical Power (dBm):

Chirp:
Wavelength (nm):
NLS Dither:
Analog Maintenance:
Provisioned
Fixed
Zero
1550
None
None
CPG Name:
G1
Secondary State:
FF
Capable
Fixed
Zero
1550
None
None
For specific instructions on querying the transmit optical parameters, refer to

Provisioning and Operations Procedures, 323-1801-310.
14-4 Appendix D: Short-reach optics
15-1
15-
Technical assistance service telephone numbers

This section provides technical assistance telephone numbers based on the
location of your installation.
Technical Assistance Service
For service-affecting problems:
For 24-hour emergency recovery or software upgrade
support, that is, for:
North America:
1-800-4NORTEL (1-800-466-7835)
restoration of service for equipment that has been carrying

traffic and is out of service
International:
001-919-992-8300
issues that prevent traffic protection switching

issues that prevent completion of software upgrades
For non-service-affecting problems:
For 24-hour support on issues requiring immediate support
or for 14-hour support (8 a.m. to 10 p.m. EST) on upgrade
notification and non-urgent issues.
North America:
1-800-4NORTEL (1-800-466-7835)
Note: You require an express routing

code (ERC). To determine the ERC, see
our corporate Web site at
www.nortel.com. Click on the Express
Routing Codes link.
International:
Varies according to country. For a list of
telephone numbers, see our corporate
Web site at www.nortel.com. Click on the
Contact Us link.
Global software upgrade support:
North America:
1-800-4NORTEL (1-800-466-7835)
International:
Varies according to country. For a list of
telephone numbers, see our corporate
Web site at www.nortel.com. Click on the
Contact Us link.
15-2 Technical assistance information
16-1
Index
10 Gbit/s Dense regenerator circuit packs 5-8
10 Gbit/s line capacity circuit packs
B1 mode 8-20
mismatch field values 8-19
traffic mode 8-20
TriFEC 8-20
Tx chirp, AM, NLS dither
provisioning 8-19
Tx output power 8-20
Tx wavelength 8-19
10 Gbit/s T/R circuit packs, TriFEC 8-20
10 Gbit/s Wavelength Translator circuit
packs 5-7
10 Gbit/s WT circuit packs, TriFEC hardware
capability 8-21
10 GE WAN PHY 3-18
100-ampere service
ANSI installations 9-17
ETSI installations 9-17
10G SR TriFEC (NTWR07AA) circuit
pack 3-3
10G WT (NTCA07xx) circuit pack 3-2
10G WT (TriFEC) circuit pack (NTCF07xx),
technical specifications 10-21
10G WT circuit pack (NTCA07xx), technical
specifications 10-18
(NTWR07AA), technical
10G WT TriFEC (NTCF07xx) circuit
pack 3-3
1600G Amplifier interoperability 7-5
2 MHz ESI interconnect characteristics 8-32
2 MHz timing interface 8-32
2.5G WT (NTCA70xx) circuit pack 3-2
162.5G WT circuit pack (NTCA70xx), technical

specifications 10-3
40-ampere service
50-ampere service
A
A1 and A2 framing bytes 3-6
access, mid-stage 6-2
acquire mode, SSM 7-42
address, manual area
alarms
affected by TriFEC 12-11
affected by TriFEC, FEC provisioning
mismatch 12-11
merged XR/WT circuit packs 13-3
ODPR 7-62
ODPR application 5-26
security, strong authentication 7-73
SSM 7-48
strong authentication 7-73
alerts
affected by TriFEC 12-11
affected by TriFEC, Line Rx REC threshold
1/2 / MS Rx 12-11
altitude, environmental specifications 9-8
AM, 10 Gbit/s line capacity circuit
packs 8-19
analog maintenance. See AM
ANSI installations
100-ampere service 9-17
16-2 Index
application guides, MOR Plus amplifier 6-4

applications 1-2
custom 9-31
Dense regenerator 1-2, 2-1, 2-8
MOR Plus amplifier 1-2, 6-1
application guides 6-4
description 6-2
mid-stage access 6-2
optical layer management tools 6-3
optical service channel (integrated) 6-3
scalability 6-4
ODPR with TriFEC 5-22
Optical dedicated protection ring 1-2
supported 7-2
supported circuit packs 1-3
TriFEC 12-1, 12-12
Wavelength Combiner 12-13
Wavelength Translator 12-12
using TriFEC
ODPR 12-12
Wavelength Combiner 1-2, 4-1
Wavelength Combiner with TriFEC 4-18
wavelength leasing 3-9
Wavelength Translator 1-2, 3-1
Wavelength Translator with TriFEC 3-12
architecture, OPTera Long Haul 1600 1-1
authentication, strong 8-42
B
B1 framing byte 3-6, 4-12
B1 framing byte, provisioning 3-8, 3-10
B1 mode, 10 Gbit/s line capacity circuit
packs 8-20
B2 framing byte 4-12
bay assembly, specifications 9-4
BER
ODPR applications with TriFEC 5-22
bins, untimed 7-16
bit error ratio. See BER
BITS
advantages 8-33
description 8-32
timing generation 7-40
breaker, circuit 9-15
breaker, circuit, assignment 8-5

breaker/filter module 8-4
bridges, network element interconnection,
building integrated timing supply
advantages 8-33
description 8-32
bytes, framing
A1 and A2 3-6
B1 3-6
C1 3-6
C
C1 framing byte 3-6
C1 framing byte, provisioning 3-8
cable length
DS1 8-32
Ethernet 9-3
circuit breaker assignment 8-5, 9-15
circuit pack group, ODPR application 5-3
circuit pack replacing
Wavelength Combiner circuit packs 8-22
circuit pack sparing and replacement
10 Gbit/s line capacity circuit packs
B1 mode 8-20
traffic mode 8-20
Tx chirp, AM, NLS dither
provisioning 8-19
Tx output power 8-20
Tx wavelength 8-19
10 Gbit/s line capacity circuit packs,
TriFEC 8-20
10 Gbit/s T/R circuit packs, TriFEC 8-20
10 Gbit/s WT circuit packs, TriFEC 8-21
circuit packs
10G SR TriFEC (NTWR07AA) 3-3
10G WT (NTCA07xx) 3-2
10G WT B1 and C1 provisioning 3-9
10G WT TriFEC (NTCF07xx) 3-3
2.5G WT (NTCA70xx) 3-2
2.5G WT B1 and C1 provisioning 3-9
alarms 13-3
configurations, determining thermal
requirements 9-26
Index 16-3
control shelf 8-4

circuit pack positioning 8-4
filler circuit packs 8-6
maintenance interface 8-6
message exchange 8-6
shelf controller 8-5
Dense regenerator circuit packs, pairing
rules 8-12
Dual 2.5G WT (NTCA72xx) 2-3, 3-4
error correction, summary 12-3
ESI (NTCA44AA and NTCE44BA) 4-10
Ethernet Wayside, positioning 8-36
merged XR/WT 13-1
description 13-1
in a network 13-2
traffic mode provisioning 13-3
non-TriFEC, selecting 12-13
OC-192/STM-64 T/R (NTCA06xx) 4-9
(NTCF06xx) 4-9
OC-192/STM-64 XR (NTCA04xx) 2-2
OC-192/STM-64 XR/WT
(NTCF04xx) 2-3, 3-3
(NTCA30xK) 4-8
OC-48/STM-16 T/R (1310 nm)
(NTCA30AL) 4-8
OC-48/STM-16 T/R SR
(NTCA30CK) 4-7
10 Gbit/s Dense regenerator circuit
packs 5-8
packs 5-7
OSM circuit pack (NTCA39AA) 5-4
orderwire 8-45
orderwire, positioning 8-45
parallel telemetry 8-8
PECs
NTCA04xx 2-2, 10-35
NTCA06xx 4-9, 10-27
NTCA07xx 3-2, 10-18
NTCA21AA 4-11
NTCA30AL 4-8, 10-12

NTCA30CK 4-7, 10-6
NTCA30xK 4-8, 10-9
NTCA39AA 5-4, 10-44
NTCA44AA 4-10, 8-7
NTCA44BA 4-10
NTCA70xx 3-2, 10-3
NTCA72xx 2-3, 3-4
NTCE44BA 8-7
NTCF04xx 2-3, 3-3, 10-38
NTCF06xx 4-9, 10-31
NTCF07xx 3-3, 10-21
NTWR07AA 3-3, 10-15
power estimates 9-23
replacing
Wavelength Combiner circuit
packs 8-22
Wavelength Translator circuit
packs 8-23
sparing and replacing 8-18
SR 14-1
description 14-2
in a network 14-2
output power 14-3
supported by application 1-3
technical specifications
optical interface 10-1
Timing distribution (NTCA21AA) 4-11
transport, circuit pack positioning 8-9
TriFEC network deployment 3-14, 4-20
TriFEC-capable 12-2, 12-12
alarms 12-11
alerts 12-11
improved link budgets 12-4
performance monitoring 12-10
selecting 12-13
WT 3-13
XR circuit packs, pairing rules 8-12
circuit packs technical specifications 10-1
(NTCF07xx) 10-21
16-4 Index

(NTWR07AA) 10-15
2.5G WT circuit pack (NTCA70xx) 10-3
(NTCF06xx) 10-31
(NTCA06xx) 10-27
(NTCA04xx) 10-35
(NTCF04xx) 10-38
(NTCA30xK) 10-9
(NTCA30AL) 10-12
(NTCA30CK) 10-6
CNET, level 1 routing 7-51
commissioning 1-6, 7-2
communications
between POPC and independent networks
over Ethernet DCC bridge 8-26
between POPC and network elements
data 7-50
external 8-29
DCC 7-23
OSC 7-23
concatenated PM counts 7-17
conducted, susceptibility/immunity,
electromagnetic compatibility 9-11
configurations
circuit packs, determining thermal
requirements 9-26
network 7-68
connections, ODPR circuit pack group 5-20
connectivity, level 2 7-55
control shelf
engineering rules 8-4
mandatory circuit packs 8-4
maintenance interface 8-6
message exchange 8-6
custom applications 9-31
D
data communications
fundamentals 7-50
hops, maximum 7-64
level 1 nodes, maximum 7-64
DCC
external communications 7-23
for Dense regenerator application 7-24
for Wavelength Combiner application 7-23
routing 7-51
DCC bridge, communication between POPC
and independent networks 8-26
degradation
advance warning of severely degraded
line/MS 4-23
advance warning of severely degraded
line/MS, ODPR with TriFEC 5-24
line/MS, ODPR with TriFEC 5-22
line/MS, Wavelength Combiner with
TriFEC 4-20
line/MS, Wavelength Translator with
TriFEC 3-15
signal, Wavelength Combiner
application 4-16, 4-17
Dense regenerator
application
DCC 7-24
description 2-1
OSC 7-24
PM 7-11
circuit packs 2-2
in network 2-8
description 2-1
pairing rules 8-12
replacing 8-21
deployment and span of control engineering
guidelines 7-64
deployments
at terminal sites 12-14
network overlay 7-3
network, error correction provisioning at
terminal sites 3-14, 4-20
new and multiple catalog software 7-2
Index 16-5
new and multiple catalog software,

supported applications 7-2
distribution, power 9-15
documentation, MOR Plus amplifier
applications guides 6-4
DS1
cable lengths 8-32
timing interface specifications 8-31
dual 2.5G WT
interworking 3-5
regenerator 2-4
sparing and replacement rules 8-24
Dual 2.5G WT (NTCA72xx) circuit
pack 2-3, 3-4
Dual GE 4-8
applications 4-24
OAM&P 7-25
traffic management 4-26
dual GE
E
E1 user byte 4-14
E2 user byte 4-14
earthquake, environmental specifications 9-9
editing
FEC 12-10
forward error correction mode 12-10
electrical fast transient, electromagnetic
compatibility 9-11
electrostatic discharge, electromagnetic
compatibility 9-11
emissions
conducted 9-11
radiated 9-10
engineering guidelines, span of control and
deployment 7-64
circuit pack positioning
control shelf 8-4
transport circuit packs 8-9
circuit pack sparing and replacing 8-18
mandatory circuit packs, control shelf 8-4

mechanical bay assembly shelf
G-naming 8-2
optional circuit packs 8-7
PM counts 7-15
PM untimed counts 7-16
slot numbering 8-2
engineering, site 9-3
environmental specifications
altitude 9-8
mechanical shock and vibration 9-9
earthquake 9-9
shock 9-9
transportation bounce 9-9
vibration 9-9
equalizing, spans of control 8-28
equipment provisioning, TL1 7-65
error control, TriFEC, description 12-2
error correction provisioning
error correction provisioning at terminal sites
error correction summary 12-3
ESI
interconnect characteristics 8-32
internal clock specifications 8-31
modes of operation 7-41
acquire 7-42
fast-acquire 7-42
freerun 7-42
holdover 7-42
normal 7-42
ESI circuit pack (NTCA44AA and
NTCE44BA) 4-10, 8-7
Ethernet cable length 9-3
Ethernet DCC bridge, communication
between POPC and independent
networks 8-26
Ethernet Wayside
adding/dropping traffic 7-78
circuit pack restart 7-79
communication 7-78
configurations 8-37
connection provisioning 7-79
16-6 Index
connection provisioning, using NE

UI 7-80
functionality 8-36
network element interconnection through
bridges 8-39
hubs 8-38
routers 8-39
loops 7-79
MOR Plus/MOR OSC LOS 7-80
network configuration 7-76
OAM&P 7-74
passthrough 7-78
powering up and autoprovisioning 7-77
Ethernet Wayside circuit pack
description 8-36
LEDs 7-79, 7-80
sparing 8-41
ETSI installations
ETSI PM counts 7-14
EW circuit pack. See Ethernet Wayside circuit
pack
extension shelf 2, OPC support 7-62
external synchronization interface circuit
pack 8-7
External Synchronization Interface circuit
pack. See ESI circuit pack
external timing 4-29
F
F1 user byte 4-14
F2 user byte 4-14
facility provisioning
F-block 7-65
G-block 7-65
facility provisioning, TL1 7-65
fast-acquire mode, SSM 7-42
fault management 7-62
faults, sectionalizing 3-9, 3-11
Wavelength Combiner (B1) 4-15

Wavelength Combiner (B2) 4-16
F-block 7-65
FEC
description 12-2
provisioning 12-8
transparent FEC bytes 3-7
FEC bytes, transparent 3-7
FEC provisioning 12-8
FEC provisioning mismatch alarm 12-11
filter mode provisioning, target 7-43
floor loading, mechanical specifications 9-12
floor plan 9-3
flow
signal 5-17
traffic 5-18
traffic, after unidirectional 1 + 1 protection
switch 5-19
forced switch 5-16
forward error correction. See FEC
frame equipment, specifications 9-5
freerun mode, SSM 7-42
Funk Software, Inc. 7-68
G
G-block 7-65
globalization 8-29
G-naming 8-2
ODPR circuit pack groups 8-17
Golden MI circuit pack
restore commissioning command 7-3
supported deployments 7-5
H
hardware baseline checking tool 7-4
holdover mode, SSM 7-42
hubs
level 2, Amplifier site or Dense regenerator
site 7-56
Index 16-7
network element interconnection, Ethernet

Wayside 8-38
I
interconnection
characteristics, 2 MHz ESI 8-32
module 5-17
network elements with Ethernet Wayside
through bridges 8-39
through hubs 8-38
through routers 8-39
ODPR circuit pack group 5-21
interoperability 1-7, 3-9, 4-32, 7-4
1600G Amplifier 7-5
optical link 7-37
ODPR 7-37
Wavelength Combiner application traffic
protection 7-37
software upgrade paths 7-5
subtending tributaries 7-4
interoperability with TransportNode 4-32
interworking 1-7, 7-3, 7-64
dual 2.5G WT 3-5
OPTera Connect DX optical switch 1-7
Preside 1-7
intraWAN 7-76
introduction 1-1
inventory, remote, Preside 7-63
ISO 10589 rule, level 1 routing 7-53
J
JO framing bytes 3-6
L
LAN PHY 3-17
LAN PHY, description 3-17
LAPD 7-51
leasing, wavelength 3-9
legacy interoperability 3-9
level 1 routing, description 7-49, 7-51
level 2 routers 7-53
level 2 routing
connectivity 7-55
DCC maximum 7-64
description 7-49, 7-53

hub, Amplifier site or Dense regenerator
site 7-56
with linear systems 7-55
limitations
globalization 8-29
network reconfiguration 8-29
Repeater network element 8-29
Line Rx FEC threshold 1/2 / MS Rx threshold
1/2 12-11
line timing 4-30
link access protocol for D-channels 7-51
link budgets
new network deployments 12-4
link budgets, TriFEC-capable circuit
packs 12-4
existing networks 12-7
loading
floor 9-12
thermal 9-13
local area network physical interface. See
LAN PHY
lockout 5-16
M
MAA. See manual area address
maintenance interface circuit pack 8-6
management, network 1-7
mandatory circuit packs 8-4
manual area address
adding 7-59
provisioning 7-57
manual switch 5-16
mechanical shock, environmental
specifications 9-9
mechanical specifications 9-1, 9-9, 9-31
circuit pack power estimates 9-23
emissions 9-10
susceptibility/immunity 9-11
electromagnetic compatibility, electrostatic
discharge and electrical fast
transient 9-11
floor loading 9-12
16-8 Index
mechanical bay assembly 9-4

parallel telemetry output relay rated
capacity 9-12
power distribution 9-14
power installation requirements 9-15
power requirements 9-13
safety 9-2
site engineering 9-3
thermal
loading 9-13
requirements for circuit pack
configurations 9-26
tool 9-24
menus
Optical Protection 5-24
Orderwire 7-83
Performance Monitoring 7-16
merged XR/WT circuit packs 13-1
description 13-1
in a network 13-2
traffic mode provisioning 13-3
message exchange (protection) circuit
pack 8-8
message exchange circuit pack 8-6
messaging, provisioning
RES 7-47
RES for SDH 7-47
RES for SONET 7-47
Rx SSM global mode 7-45
TD threshold 7-46
TG threshold 7-46
Tx SSM global mode 7-46
Tx SSM QC override 7-45
MI circuit pack 8-6
MI circuit pack, restore commissioning
command 7-3
mismatch field values, 10 Gbit/s line capacity
circuit packs 8-19
modes
acquire 7-42
fast-acquire 7-42
forward error correction
editing 12-10
querying 12-10
freerun 7-42
holdover 7-42
normal 7-42
target filter mode provisioning 7-43
timing modes of operation 7-43
modes, network element
synchronization 4-29
module interconnection 5-17
monitoring, OPC 7-62
MOR Plus amplifier
application
optical layer management tools 6-3
scalability 6-4
application guides 6-4
description 6-2
optical service channel (integrated) 6-3
MOR Plus amplifier application 6-1
MOR Plus amplifier circuit packs with
OSC 8-47
MOR Plus amplifier interoperability 7-4
MX (protection) circuit pack 8-8
MX circuit pack 8-6
N
NE ID 7-48
NE UI
overview 7-20
provisioning Ethernet Wayside
connections 7-80
NE UI support 7-18
network applications
TriFEC
ODPR 12-12
using TriFEC 12-12
network configuration description 7-68
network configuration, Ethernet
Wayside 7-76
network deployments
at terminal sites 12-14
new, link budgets for TriFEC-capable
circuit packs 12-4
network element commissioning 1-6
Index 16-9
network element name 7-48

network element RADIUS
authentication 7-70
network element user interface
overview 7-20
support 7-18
network elements, maximum number in span
of control 7-64, 8-26
network interworking 7-3
network management 1-7, 7-74
network management tools 1-7
network protection, ODPR application 5-9
network service access point 7-49
network synchronization requirements 8-30
2 MHz timing interface specifications 8-32
BITS 8-32
DS1 timing specifications 8-31
ESI internal clock specifications 8-31
stratum clocks 8-31
networks, existing, link budgets for
NLS dither, 10 Gbit/s line capacity circuit
packs 8-19
non-TriFEC circuit packs, selecting 12-13
normal mode, SSM 7-42
Nortel Networks web site 7-68
NSAP 7-49, 7-51, 7-52
NTCA04xx 2-2, 10-35
NTCA06xx 4-9, 10-27
NTCA07xx 3-2, 10-18
NTCA21AA 4-11
NTCA30AL 4-8, 10-12
NTCA30CK 4-7, 10-6
NTCA30xK 4-8, 10-9
NTCA39AA 5-4, 10-44
NTCA44AA 4-10, 8-7
NTCA44BA 4-10
NTCA70xx 3-2, 10-3
NTCA72xx 2-3, 3-4
NTCE44BA 8-7
NTCF04xx 2-3, 3-3, 10-38
NTCF06xx 4-9, 10-31
NTCF07xx 3-3, 10-21
NTWR07AA 3-3, 10-15
O
OAM&P 7-1
commissioning and span of control
upgrades 7-2
hardware baseline checking tool 7-4
new deployments and multiple catalog
software support 7-2
restore commissioning MI
command 7-3
upgrade paths 7-4
DCC for Dense regenerator 7-24
DCC for Wavelength Combiner 7-23
OSC for Dense regenerator 7-24
interoperability 7-4
1600G Amplifier 7-5
software upgrade paths 7-5
subtending tributaries 7-4
NE UI support 7-18
network management 7-74
OPC support 7-62
extension shelf 2 7-62
PM capability 7-62
software features 7-63
optical link interoperability 7-37
ODPR 7-37
protection 7-37
orderwire 7-82, 7-83
PM 7-7
concatenated PM counts 7-17
SDH PM counts 7-14
SONET PM counts 7-14
untimed bins 7-16
PM counts, engineering rules 7-15
PM untimed counts, engineering
rules 7-16
routing fundamentals 7-49
16-10 Index
span of control upgrades 7-2

SSM
acquire mode 7-42
alarms and events 7-48
description 7-39
fast-acquire mode 7-42
holdover mode 7-42
normal mode 7-42
provisioning 7-44
target filter mode provisioning
mode 7-43
timing distribution 7-41
synchronization status messaging
freerun mode 7-42
TL1 equipment provisioning 7-65
TL1 facility and equipment
provisioning 7-65
restrictions 7-66
surveillance 7-66
TL1 facility provisioning 7-65
upgrades, span of control 7-2
(NTCF06xx), technical
(NTCA06xx) 4-9
(NTCA06xx), technical
OC-192/STM-64 T/R TriFEC circuit pack
(NTCA06xx) 4-9
(NTCA04xx) 2-2
(NTCF04xx) 2-3, 3-3
(NTCA30xK) 4-8

(NTCA30xK), technical
specifications 10-9
(NTCA30AL) 4-8
(NTCA30AL), technical
(NTCA30CK) 4-7
(NTCA30CK), technical
specifications 10-6
ODPR 1-2
applications
1 + 1 protection scheme 5-19
alarms 5-26
circuit pack group 5-3
circuit packs 5-4
collapsed ring 5-10
description 5-1
fault sectionalizing 3-9
FEC counts 5-22
in network 5-27
module interconnection 5-17
NE UI 5-24
network protection 5-9
network supporting unprotected
routers 5-11
OPC 5-27
rules 5-14
shared protection for unbalanced
ring 5-12
signal degrade threshold 5-23
signal flow 5-17
with TriFEC 5-22
circuit pack group, optical fiber
connections 5-20
circuit pack groups, engineering rules
circuit packs
10 Gbit/s Dense regenerator circuit
packs 5-8
packs 5-7
NE UI
Optical Protection Menu 5-24
Index 16-11

ODPR circuit pack group,
interconnection 5-21
OPC
communications
between POPC and independent
networks over Ethernet DCC
bridge 8-26
between POPC and network elements
definition and span of control, maximum
number of network elements 8-26
locating OPCs on network elements within
span of control 8-28
location of POPC 8-27
provisioning requirements, strong
authentication (security) 8-43
remote login 7-63
span of control, locating OPCs on network
elements 8-28
OPC controller circuit pack 8-7
OPC definition and span of control 8-25
OPC interface circuit pack 8-8
OPC RADIUS authentication 7-69
OPC servers configuration file, strong
OPC storage circuit pack 8-8
OPC support 7-62
extension shelf 2 7-62
software features 7-63
OPC user interface 7-71
OPC users configuration file, strong
open access orderwire 7-82, 8-45
operations, administration, maintenance, and
provisioning 7-1
optical dedicated protection ring. See ODPR
optical fiber connections, ODPR circuit pack
group 5-20
optical link interoperability 7-37
ODPR 7-37
protection 7-37
optical link, enabling TriFEC 12-15
optical switch module circuit pack

(NTCA39AA) 5-4
optical switching, functionality 5-7
optional circuit packs 8-7
external synchronization interface 8-7
message exchange (protection) 8-8
OPC controller 8-7
OPC interface 8-8
OPC storage 8-8
orderwire 8-8
parallel telemetry 8-8
orderwire 7-82, 8-45
adding connections 7-83
querying connections 7-83
orderwire circuit pack 8-8, 8-45
orderwire circuit pack, sparing 8-47
Orderwire Menu 7-83
OSC
functionality 8-47
OSC circuit pack, orderwire 8-45
OSC for Dense regenerator application 7-24
OSC link hop limit 7-64
OSC, integrated 6-3
OSM circuit pack (NTCA39AA), technical
output power, SR circuit packs 14-3
overhead bytes
description 11-2
service transparency values 11-3
overhead processing 2-7, 3-6, 4-11, 11-1
A1 and A2 framing bytes 3-6
B1 framing byte 3-6, 4-12
B2 framing byte 4-12
C1 framing byte 3-6
enhanced DCC transparency 4-13
orderwire and user bytes
transparency 4-14
overhead bytes, description 11-2
service transparency values for overhead
bytes 11-3
overlay
network 7-3
16-12 Index
OC-192/TN-64X span of control overlay

onto OPTera Long Haul 1600 span of
control 8-28
overview 1-1, 1-2
P
parallel telemetry circuit pack 8-8
parallel telemetry output relay rated capacity,
mechanical specifications 9-12
parameter values for TriFEC-capable WC
circuit packs 4-19
parameter values for TriFEC-capable WT
circuit packs
Rx FEC 3-13
Tx FEC 3-13
partition repair 7-61
partitioned OPC. See also OPC
partitioned OPC. See POPC
PECs, circuit packs
NTCA04xx 2-2, 10-35
NTCA06xx 4-9, 10-27
NTCA07xx 3-2, 10-18
NTCA21AA 4-11
NTCA30AL 4-8, 10-12
NTCA30CK 4-7, 10-6
NTCA30xK 4-8, 10-9
NTCA39AA 5-4, 10-44
NTCA44AA 4-10, 8-7
NTCA44BA 4-10
NTCA70xx 3-2, 10-3
NTCA72xx 2-3, 3-4
NTCE44BA 8-7
NTCF04xx 2-3, 3-3, 10-38
NTCF06xx 4-9, 10-31
NTCF07xx 3-3, 10-21
NTWR07AA 3-3, 10-15
Performance Monitoring Menu 7-16
performance monitoring. See PM
platform, OPTera Long Haul 1600 1-2
PM
counts
concatenated 7-17
SDH 7-14
SONET 7-14
surveillance 7-66
monitoring capability 7-62

surveillance 7-66
untimed bins 7-16
untimed counts, engineering rules 7-16
POPC circuit pack 8-7
POPC, location of 8-27
POPC-I circuit pack 8-8
POPC-S circuit pack 8-8
power dissipation 9-25, 9-29
power distribution and circuit breaker
assignment 9-15
power distribution, mechanical
specifications 9-14
power estimates, circuit packs, mechanical
specifications 9-23
power installation requirements
100-ampere service for ANSI and ETSI
installations 9-17
installations 9-17
installations 9-16
mechanical specifications 9-15
power management tool 9-31
power requirements, mechanical
specifications 9-13
power, output, SR circuit packs 14-3
Preside 1-7
application 7-74
upload for remote inventory 7-63
workstations, maximum 7-64
product architecture 1-1
product engineering codes. See PECs
product interworking 1-7
OPTera Connect DX optical switch 1-7
Preside 1-7
product upgrade paths 1-6
protection
1 + 1, ODPR application 5-19
shared protection for unbalanced ring,
switching 5-15
forced switch 5-16
hierarchy 5-16
lockout 5-16
Index 16-13
manual switch 5-16

signal degrade 5-16
signal fail on protection 5-16
signal fail on working 5-16
traffic flow after unidirectional 1 + 1
protection switch 5-19
traffic, Wavelength Combiner
application 7-37
unprotected routers, ODPR
application 5-11
protection, ODPR application 5-9
provisioning
B1 3-8, 3-9, 3-10
B1 and C1 bytes 3-8
C1 3-9
equipment 7-65
error correction
error correction at terminal sites 4-20
error correction at terminal sites,
Ethernet Wayside connection 7-79
Ethernet Wayside connection, using NE
UI 7-80
facility 7-65
FEC 12-8
signal degrade threshold, ODPR
application 5-25
SSM 7-44, 7-45, 7-46
traffic mode, merged XR/WT circuit
packs 13-3
PT circuit pack 8-8
Q
querying
FEC 12-10
forward error correction mode 12-10
R
radiated, susceptibility/immunity,
RADIUS authentication protocol 7-67, 7-69
reconfiguration, network 8-29
regeneration, 10 Gbit/s Dense regenerator
circuit packs 5-8
regenerator, dual 2.5G WT 2-4

remote authentication dial-in user
service 7-67
remote inventory, Preside 7-63
remote login 7-63
Repeater circuit packs
(NTWR07AA), technical
2.5G WT circuit pack (NTCA70xx),
(NTCA30xK), technical
specifications 10-9
(NTCA30AL), technical
(NTCA30CK), technical
specifications 10-6
OSM circuit pack (NTCA39AA), technical
Repeater circuit packs, technical
specifications 10-1
Repeater network element limitations 8-29
globalization 8-29
Repeater network element, fault
sectionalizing 3-11
RES 7-47
16-14 Index
RES for SDH 7-47

RES for SONET 7-47
restore commissioning MI command 7-3
restrictions, TL1 facility and equipment
provisioning 7-66
rlogin 7-63
routers
level 1 7-51
level 2 7-53
network element interconnection, Ethernet
Wayside 8-39
unprotected, ODPR application 5-11
routing
level 1 7-51, 7-53
level 2 7-53
partition repair 7-61
routing adjacency 7-51
routing fundamentals 7-49
routing, NSAP 7-49
RSA Security Inc. 7-68
rules
applications
with multiple spans of control 8-28
with one span of control 8-27
engineering 8-1
ISO 10589 7-53
Rx SSM QC override 7-44
S
safety specifications 9-2
SC circuit pack 8-5
scalability, MOR Plus amplifier
application 6-4
SD. See signal degrade
SDH PM counts 7-14
sectionalizing faults 3-11
SecurID card 7-67
security
Funk Software, Inc. 7-68
RADIUS 7-67
RSA Security Inc. 7-68

SecurID card 7-67
strong authentication 7-67, 8-42
service transparency 2-7, 3-6, 4-11, 11-1
B1 and C1 (J0) bytes 3-8
enhanced DCC transparency 4-13
transparency 4-14
overhead bytes 11-2
values, overhead bytes 11-3
SF. See signal fail
shelf G-naming 8-2
shock, environmental specifications 9-9
short-reach circuit packs. See SR circuit packs
signal degradation
Wavelength Combiner 4-16, 4-17
signal degrade threshold 4-21
signal degrade threshold provisioning, ODPR
application 5-25
signal degrade threshold, ODPR
application 5-23
signal degrade, ODPR application 5-16
signal fail on protection, ODPR
application 5-16
signal fail on working, ODPR
application 5-16
signal flow 5-17
floor plan 9-3
frame equipment 9-5
maximum Ethernet cable length 9-3
mechanical bay assembly
specifications 9-4
slot numbering 8-2
Index 16-15
software delivery 7-63

software features, OPC 7-63
SONET PM counts 7-14
span of control and deployment engineering
guidelines 7-64
spans of control 8-25
commissioning 7-63
equalizing 8-28
locating OPCs on network elements 8-28
maximum number of network
elements 8-26
OC-192/TN-64X span of control overlay
onto OPTera Long Haul 1600 span of
control 8-28
rules for multiple spans of control 8-28
rules for one span of control 8-27
upgrade 7-63
upgrades 7-2
sparing
definition 8-18
Ethernet Wayside circuit pack 8-41
orderwire circuit pack 8-47
sparing and replacing 8-18
specifications
2 MHz timing interface 8-32
DS1
timing interface 8-31
environmental
altitude 9-8
earthquake 9-9
mechanical shock and vibration 9-9
shock 9-9
transportation bounce 9-9
vibration 9-9
frame equipment 9-5
mechanical 9-1
circuit pack power estimates 9-23
custom applications 9-31
floor loading 9-12
parallel telemetry output relay rated
capacity 9-12
power dissipation 9-25, 9-29
power installation requirements 9-15
power management tool (custom

applications) 9-31
power requirements 9-13
thermal loading 9-13
thermal ratings 9-29
thermal requirements for circuit pack
configurations 9-26
thermal tool 9-24
thermal tool worksheet 9-28
mechanical bay assembly 9-4
safety 9-2
technical
circuit packs 10-1
optical interfaces 10-1
SR circuit packs
description 14-2
in a network 14-2
output power 14-3
SSM
acquire mode 7-42
alarms and events 7-48
description 7-39
fast-acquire mode 7-42
freerun mode 7-42
holdover mode
normal mode 7-42
provisioning 7-44
RES 7-47
RES for SDH 7-47
RES for SONET 7-47
Rx SSM QC override 7-44
TD threshold 7-46
TG threshold 7-46
target filter mode provisioning mode 7-43
stratum clocks 8-31
strong authentication 7-63, 7-67, 8-42
alarms 7-73
OPC provisioning requirements 8-43
OPC servers configuration file 8-43
16-16 Index
OPC users configuration file 8-44

STS timeslots 4-4
subtending tributaries, interoperability 7-4
surveillance 7-66
alerts (TL1) 7-66
autonomous alarms (TL1) 7-66
logs (TL1) 7-66
PM counts 7-66
PMs 7-66
susceptibility/immunity
conducted 9-11
radiated 9-11
susceptibility/immunity, electromagnetic
compatibility 9-11
switch
forced 5-16
manual 5-16
switching, protection 5-15
switching, protection, hierarchy 5-16
external timing 4-29
network element synchronization
modes 4-29
requirements 8-30, 8-31
timing
flow of timing signals 4-31
line 4-30
through 4-30
synchronization status messaging. See SSM
T
TD circuit pack 8-7
TD circuit pack (NTCA21AA) 4-11
TD threshold 7-46
dual 2.5G WT 10-24
dual GE 10-41
technical specifications, circuit pack 10-1
TG threshold 7-46
thermal loading, mechanical
specifications 9-13
thermal ratings, mechanical
specifications 9-29
thermal requirements for circuit packs 9-26
thermal tool worksheet, mechanical

specifications 9-28
thermal tool, mechanical specifications 9-24
threshold, signal degrade 4-21
through timing 4-30
timeslots, STS 4-4
timing
DS1 timing interface specifications 8-31
ESI internal clock specifications 8-31
external 4-29
flow of synchronization timing
signals 4-31
interface specifications
2 MHz 8-32
DS1 8-31
line 4-30
stratum clocks 8-31
through 4-30
Timing distribution circuit pack. See TD
circuit pack
timing modes of operation 7-43
TL1 equipment provisioning 7-65
TL1 facility provisioning 7-65
tools
hardware baseline checking 7-4
optical layer management, MOR Plus
amplifier application 6-3
traffic flow 5-18
traffic flow, after unidirectional 1 + 1
protection switch 5-19
traffic mode provisioning, merged XR/WT
circuit packs 13-3
traffic mode, 10 Gbit/s line capacity circuit
packs 8-20
traffic protection, Wavelength Combiner
application 7-37
transparency 2-7, 3-6
B1 and C1 (J0) bytes 3-8
enhanced DCC transparency of Wavelength
Combiner 4-13
transparency 4-14
service
Index 16-17
overhead bytes 11-2

values for overhead bytes 11-3
Wavelength Translator applications with
TriFEC 3-12
transparency, service 4-11, 11-1
transport circuit packs, engineering rules 8-9
Wavelength Combiner circuit pack
groups 8-13
transportation bounce, environmental
specifications 9-9
tributaries, subtending, interoperability 7-4
TriFEC
applications 12-1
circuit packs 3-3
circuit packs, network deployment 3-14,
4-20
description 12-2
enabling 12-15
line/MS degradation 3-15
provisioning 12-8
transparency of Wavelength Translator
applications 3-12
TriFEC circuit packs 3-3
TriFEC hardware capability
10 Gbit/s line capacity circuit packs 8-20
10 Gbit/s T/R circuit packs 8-20
10 Gbit/s WT circuit packs 8-21
TriFEC-capable circuit packs 12-2, 12-12
alarms 12-11
alarms, FEC provisioning mismatch 12-11
alerts 12-11
alerts, Line Rx FEC threshold 1/2 / MS Rx
threshold 1/2 12-11
improved link budgets 12-4
link budgets for existing networks 12-7
link budgets for new network
deployments 12-4

selecting 12-13
TriFEC-capable WT circuit packs 3-13
triple FEC. See TriFEC
triple forward error correction. See TriFEC
Tx chirp, 10 Gbit/s line capacity circuit
packs 8-19
Tx output power, 10 Gbit/s line capacity
circuit packs 8-20
Tx wavelength, 10 Gbit/s line capacity circuit
packs 8-19
U
untimed bins 7-16
upgrade paths 1-6, 7-4, 7-5
upgrades, span of control 7-2
URL, Nortel Networks 7-68
user interfaces
NE UI 7-18
NE UI, ODPR application 5-24
OPC 7-71
OPC, ODPR application 5-27
V
vibration, environmental specifications 9-9
W
WAN PHY 3-16
WAN PHY, description 3-17
warning, severely degraded line/MS 4-23
Wavelength Combiner
application 4-1
BER 4-20
DCC 7-23
description 4-2
error correction provisioning 4-18
fault sectionalizing (B1) 4-15
fault sectionalizing (B2) 4-16
in network 4-33
interoperability with
TransportNode 4-32
PM 7-7
traffic protection 7-37
TriFEC (line/MS degradation) 4-20
16-18 Index
with TriFEC 4-18

circuit pack group 4-6
circuit packs 4-7
Wavelength Combiner circuit pack
groups 8-13
Wavelength Combiner circuit packs,
replacing 8-22
wavelength leasing application 3-9
application 3-1
B1 byte provisioning 3-10
error correction provisioning 3-13
in network 3-19
PM 7-11
sectionalizing faults 3-12
TriFEC (line/MS degradation) 3-15
with TriFEC 3-12
circuit packs 3-2
Wavelength Translator circuit packs,
replacing 8-23
WC. See Wavelength Combiner
web site, Nortel Networks 7-68
wide area network physical interface. See
WAN PHY
wide area network, intraWAN 7-76
WT. See Wavelength Translator
X
XR circuit packs 8-12
XR/WT circuit packs, merged 13-1
Index 16-19
16-20 Index
Index 16-21
16-22 Index
Index 16-23
16-24 Index
Index 16-25
16-26 Index
Index 16-27
16-28 Index
Index 16-29
16-30 Index
Nortel
Optical Long Haul 1600

Repeater NE Network Application Guide
Copyright 20002005 Nortel, 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.
This information is provided as is, and Nortel Networks does not
make or provide any warranty of any kind, expressed or implied,
including any implied warranties of merchantability,
non-infringement of third party intellectual property rights, and
fitness for a particular purpose. Except as expressly authorized in
writing by Nortel Networks, the holder is granted no rights to use
the information contained herein.
Nortel, the Nortel logo, and the Globemark are trademarks of
Nortel Networks.
ACE/Server, RSA, and SecurID are trademarks of RSA Security,
Inc.
HP-UX is a trademark of Hewlett-Packard Company
Sun and Solaris are trademarks of Sun Microsystems, Inc.
CLFI, Common Language, and Telcordia are trademarks of
Telcordia Technologies, Inc.
UNIX is a trademark of X/Open Company Ltd.
Windows and Windows NT are trademarks of Microsoft
Corporation.
NTY316AL
Rel 11 Standard Issue 1
December 2005
Printed in Canada

HL 6100

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

HL 6100

Transféré par

Droits d'auteur :

Formats disponibles

NTY316AL

Optical Long Haul 1600

Copyright 20002005 Nortel Networks, All Rights Reserved

Optical Long Haul 1600 Release 11 1-2

Dense regenerator application

Description of the Dense regenerator application 2-1

Wavelength Translator application

Description of the Wavelength Translator application 3-1

Wavelength Combiner application

Description of the Wavelength Combiner application 4-2

Optical dedicated protection ring (ODPR) application

Description of the optical dedicated protection ring (ODPR) application 5-2

MOR Plus amplifier application

Operations, administration, maintenance, and provisioning

Commissioning and span of control upgrades 7-2

Circuit pack maximum and optical jitter 8-2

Safety specifications 9-2

Circuit pack technical specifications

Optical interface specifications 10-1

Appendix A: Overhead processing

Description of overhead bytes 11-2

Appendix B: TriFEC applications

TriFEC-capable circuit packs 12-2

Appendix C: Merged XR/WT circuit packs

Merged XR/WT circuit packs 13-1

Appendix D: Short-reach optics

Short-reach circuit packs 14-1

Technical assistance information

Technical assistance service telephone numbers 15-1

About this document

The Repeater NE Network Application Guide describes the Repeater network

Optical amplifier shelf

MOR and MOR Plus amplifier

Note: For information on the 1600G Amplifier, refer to the 1600G

x About this document

About this document xi

Optical Connect DX documents

xii About this document

ETSI 300 132-2

The Telecommunications Industry Association (TIA) and the Electronics

Optical Long Haul 1600 Release 11

Optical Long Haul 1600 platform

Network Equipment Building System (NEBS)

Applications supported on the Repeater network element

Dual 2.5G WT on/off ramp

OC-48/STM-16 DWDM T/R

OC-48/STM-16 T/R (1310 nm)

OC-192/STM-64 T/R (TriFEC)

External synchronization interface (ESI)

Timing distribution (TD)

Dual Gigabit Ethernet (GE)

Wavelength Combiner (see Note)

Optical dedicated protection ring

Optical switch module

MOR Plus amplifier (with and without OSC)

MOR Plus amplifier

For circuit pack engineering rules, refer to Mechanical specifications on

Breaker Interface Panel (BIP)

Note 2: Do not mix circuit pack traffic

Note 1: A network element equipped

Fiber Management Tray (FMT)

Note 5: Be sure to follow the

Note 4: Equip one or two Ethernet

Note 3: ODPR does not support