planning guide, part 1 of 2

ATTENTIONClicking on a PDF hyperlink takes you to the appropriate page. If necessary, scroll up or down the page to see the beginning of the referenced section.

www.nortel.com

NTT840FF

What’s inside...New in this releaseOverviewShelf configurations, wavelengths, and network managementHardware description

See Part 2 for the following:System descriptionData communicationsTechnical specificationsOrdering informationTechnical assistanceList of abbreviationsIndex

Nortel Common Photonic Layer

Planning Guide, Part 1 of 2Standard Release 4.0 Issue 1 September 2009

Nortel Common Photonic LayerRelease 4.0Publication: Planning Guide, Part 1 of 2Document Status: StandardDocument Release Date: September 2009

Copyright © 2004-2009, Nortel Networks, All Rights ReservedThis document is protected by copyright laws and international treaties. All information, copyrights and any other intellectual property rights contained in this document are the property of Nortel Networks. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein and this document shall not be published, copied, produced or reproduced, modified, translated, compiled, distributed, displayed or transmitted, in whole or part, in any form or media.

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.

Nortel Networks, the Nortel logo, and the Globemark are trademarks of Nortel Networks.

Printed in Canada

iii

Contents 0

Introduction vii

New in this release 1-1Features 1-1

Overview 2-1Key feature and benefits overview 2-1

Link engineering and capacity 2-2Hardware-modular architecture 2-4Software feature benefits 2-5

Common Photonic Layer site descriptions and building blocks 2-6Terminal site 2-7Line Amplifier site 2-12GMD based OADM site 2-14TOADM site 2-15All TOADM rings 2-17ROADM 2-18Direction Independent Access (DIA) 2-21Coarse DGFF site 2-33Fine DGFF site 2-33Linear spur site 2-34Branch site using WSSs 2-36Distributed branch nodes 2-41Single span CMD44 point-to-point terminal 2-43Cascaded LIM configurations 2-47Metro, regional, and long haul applications 2-48Advanced optical control 2-50

DIA restoration 2-52Raman applications 2-54

DRA supported deployments 2-56Operational considerations 2-57

Common Photonic Layer Line Amplifiers in an OME6500 photonics network 2-59Operational considerations 2-61OSC link budgets 2-61

Engineering tools 2-62Optical Modeler 2-62Optical Planner 2-63

Wavelength plan 2-63

Nortel Common Photonic LayerPlanning Guide, Part 1 of 2

NTT840FF Issue 1 StandardRelease 4.0 September 2009

Copyright © 2004-2009, Nortel Networks

iv Contents

CMD44 deployment rules 2-65Supported CMD44 to WSS configurations 2-68Supported network configurations 2-71Channel capacity increase options 2-76

Interworking with Nortel portfolio and with other vendor’s equipment 2-77Mixing different types of transmitters and receivers 2-80

Transmitter and CMD compatibility 2-82

Shelf configurations, wavelengths, and network management 3-1Supported network element configurations 3-2Rack level shelf configurations 3-3Compatible wavelength plan 3-27Network management requirements 3-33Network management software 3-35SNMP support 3-35

Craft Interface 3-35Simple Network Management Protocol 3-35SNMP access and SNMP agent 3-37SNMP security 3-38SNMP agent configuration 3-39SNMP traps 3-40Trap receivers 3-40Active and cleared alarms 3-40SNMP trap enabling and filtering 3-41Provisioned equipment and circuit pack inventory retrieval 3-42Shelf wide index schemes 3-42MIB compliancy 3-44SNMP—supported features in this release 3-52

Hardware description 4-1Common Photonic Layer frame 4-2

Adapter brackets and 1U and 2U carriers 4-4Enclosing the Common Photonic Layer frame 4-5Multi-slot carriers 4-5Group Mux/Demux (GMD) module (NTT801AA-BA) 4-9

Functional description 4-9OAM&P features 4-12Customer interface office alarm and PTT connections 4-14

Dual Optical Service Channel (DOSC) module (NTT839AA) 4-16Functional description 4-16OAM&P features 4-17Customer interface office alarm and PTT connections 4-19

Uni Optical Service Channel (UOSC) module (NTT839BA) 4-21Functional description 4-21OAM&P features 4-22Customer interface office alarm and PTT connections 4-24

4 Channel Mux/Demux (CMD4) module (NTT810BA-BH, BJ) 4-25Functional description 4-25OAM&P features 4-27




Contents v

44 Channel Mux/Demux C-Band (CMD44) module (NTT862AA/BA/BB/FAE5) 4-29Functional description 4-29OAM&P features 4-33

Serial 4 Channel Mux/Demux (SCMD4) module (NTT810CA-CH, CJ) 4-39Functional description 4-39OAM&P features 4-41

Serial 8 Channel Mux/Demux (SCMD8) module - Filtered SCMD8 (NTT861AA-AH, AJ) and Open SCMD8 (NTT861BA-BH, BJ) 4-44

Functional description 4-44OAM&P features 4-46

Broadband Mux/Demux 1x2 (NTT862DAE5) 4-49Functional description 4-49OAM&P features 4-50

Wavelength Selective Switch (WSS) module (NTT837CA, NTT837DA) 4-52Functional description 4-52OAM&P features 4-54

Common Photonic Layer Amplifier (NTT830xA) 4-56Functional description 4-56OAM&P features 4-57

Distributed Raman Amplifier (NTT831AA) 4-66Functional description 4-66OAM&P features 4-67

Channel Mux/Demux Amplifier (NTT832AA) 4-70Functional description 4-70OAM&P features 4-71

Optical Power Monitor (NTT838AA) 4-73Functional description 4-73OAM&P features 4-74

Breaker interface panels (BIP) 4-761U BIP - NTK599DA (for global deployments) 4-76BIP - NTN458RA (for deployments in North America) 4-78EMEA BIP - NTT899GC (for deployments in Europe, Middle East and Africa)

4-79Fuse panels 4-80

1U Fuse Interface Panel - NTK599EA 4-80Fuse Panel, 10 circuits - NTT899GB 4-82

2U AC Rectifier (NTN458SB, NTN458SC) 4-83Fiber Manager (FM) with/without Dispersion Slope Compensation Module

(DSCM) 4-84DSCM drop-in plate assembly (NTT899FB) 4-85Dispersion Slope Compensation Module 4-85Slack-storage drop-in plate assembly (NTT899FD) 4-87

Fiber and cable management strategy 4-88Fiber management 4-88Cable management strategy 4-91

Connector strategy 4-91Slider connector mechanism 4-91

Data communication connections 4-93




vi Contents

Visual indicator strategy 4-93Shelf - network element level visual indicators (GMD, UOSC and DOSC) 4-93Module visual indicators (all modules) 4-93

Hardware required for interface functionality 4-93Optical Manager Element Adapter (OMEA) hardware 4-93Site Manager hardware requirements 4-93Site Manager supported operating platforms 4-95




vii

Introduction 0

The Planning Guide, NTT840FF, provides an overview of the features and hardware provided by the Common Photonic Layer Release 4.0.

Attention: This document is presented in two parts: Part 1 and Part 2. Each part has its own table of contents. The table of contents in Part 1 contains topics found in Part 1 only. The table of contents in Part 2 contains topics found in Part 2 only. Part 2 continues sequential chapter numbering from Part 1.

NavigationPlanning Guide Part 1, NTT840FF, contains the following:

• New in this release

• Overview

• Shelf configurations, wavelengths, and network management

• Hardware description

Planning Guide Part 2, NTT840FF, contains the following:

• System description

• Data communications

• Technical specifications

• Ordering information

• Technical assistance

• List of abbreviations

• Index




viii Introduction




1-1

New in this release 1-

The following sections detail what is new in Nortel Common Photonic Layer for Release 4.0.

FeaturesSee the following sections for information about feature changes:

• Direction Independent Access (DIA) on page 1-1

• OME6500 Photonic using Common Photonic Layer line amplifiers on page 1-2

• Broadband Mux/Demux 1x2 (BMD2) on page 1-2

• eCMD44 100 GHz on page 1-2

• Optical Transport Section (OTS) on page 1-2

• DOSC at TOADM and ROADM on page 1-2

• DOC Enhanced automation mode on page 1-3

• Security enhancements on page 1-3

• Database Replication Service (DBRS) on page 1-3

Direction Independent Access (DIA)Direction Independent Access (DIA) allows the user to determine the optical direction of a channel from a site using software and not a physical connection. A DIA terminal uses standard WSS, amplifier, and OPM components to create a directionally independent access point. A DIA simplifies the planning of ROADM sites and networks by allowing wavelengths to be remotely redirected to another direction as the bandwidth requirements change. For further information, see the following sections:


• DIA restoration on page 2-52




1-2 New in this release

OME6500 Photonic using Common Photonic Layer line amplifiers Common Photonic Layer line amplifiers are supported in a network comprising OME6500 equipment. For further information, see Common Photonic Layer Line Amplifiers in an OME6500 photonics network on page 2-59.

Broadband Mux/Demux 1x2 (BMD2)The Broadband Mux/Demux 1x2 (BMD2) module is used in direction independent access (DIA) configurations to allow full 88 channel support in 50 GHz systems. For further information, see the following sections:


• Broadband Mux/Demux 1x2 (NTT862DAE5) on page 4-49

eCMD44 100 GHzThe eCMD44 C-Band 100 GHz module must be used in 100 GHz DIA configurations.The eCMD44 C-Band 100 GHz has all the same features as the CMD44 C-Band 100 GHz except that it includes an isolator on the Common In port (Demux side). For further information, see the following sections:


• 44 Channel Mux/Demux C-Band (CMD44) module (NTT862AA/BA/BB/FAE5) on page 4-29

Optical Transport Section (OTS)Release 4.0 introduces the concept of a Optical Transport Section (OTS) object that contains many of attributes that were accessed at the shelf level in previous releases.

An OTS is defined as a group of equipment all serving the same fiber pair and is built around a Line Interface Module (LIM, usually an amplifier module) and an optical service channel (OSC) unit (GMD, UOSC, or DOSC). For more information, see “System description” chapter in Part 2 of this document.

DOSC at TOADM and ROADMRelease 4.0 introduces the support for Dual OSC (DOSC) at ROADM and TOADM sites to replace two Uni-OSCs (UOSCs). For further information, see the following sections:

• Common Photonic Layer site descriptions and building blocks on page 2-6

• “Ordering information” chapter in Part 2 of this document




New in this release 1-3

DOC Enhanced automation modeThe DOC Enhanced automation mode provides improved DOC speed and increases availability of system functions. In this mode, channel actions (add/delete) are performed in a single step separate from the optimization steps. Re-optimization is performed after a channel add/delete. For more information, see “System description” chapter in Part 2 of this document.

Security enhancementsSecure shellRelease 4.0 supports secure shell (SSH) that is a protocol which provides encrypted communication between the Common Photonic Layer network element and Site Manager or OMEA.

Secure HTTPRelease 4.0 supports a secure HTTP feature that provides users with a new means to securely access the Common Photonic Layer network elements via HTTPS protocol using Site Manager or Internet Browsers to perform different configuration and management related functions.

For more information, see the following:

• “System description” chapter in Part 2 of this document

• “Data communications” chapter in Part 2 of this document

Database Replication Service (DBRS)Release 4.0 introduces support for Database Replication Service (DBRS) applications which provides a mechanism for segregating large OSPF networks and for connecting existing networks together.

For more information, see “Data communications” chapter in Part 2 of this document.




1-4 New in this release




2-1

Overview 2-

This planning guide describes the applications, configurations, and functionality provided by the software and hardware of Common Photonic Layer.

Table 2-1 lists the topics in this chapter.

Key feature and benefits overviewCommon Photonic Layer optical line product leverages years of proven expertise in developing and building metro, regional, and long haul optical network solutions. This platform provides customers a single photonic line solution that can bridge edge and core applications while pushing the technology envelope to bring the most cost effective, scalable, and above all, flexible solution that the market requires to meet ongoing competitive pressures.

Table 2-1Topics in this chapter

Topic Page

Key feature and benefits overview 2-1

Common Photonic Layer site descriptions and building blocks 2-6

DIA restoration 2-52

Raman applications 2-54

Common Photonic Layer Line Amplifiers in an OME6500 photonics network

2-59

Engineering tools 2-62

Wavelength plan 2-63

CMD44 deployment rules 2-65

Interworking with Nortel portfolio and with other vendor’s equipment 2-77

Transmitter and CMD compatibility 2-82




2-2 Overview

The guiding principles for the Common Photonic Layer optical architecture are:

• a cost-optimized, scalable, modular design that provides the lowest possible first in cost, with a clear path to a lower full-fill cost and minimized operational expenditures

• an optical add-drop multiplexer (OADM)-centric platform that is either:

— Wavelength Selective Switch (WSS) based for per wavelength access and branching

— Thin OADM based for low initial cost and well understood traffic

— Group Mux/Demux (GMD) based for large or small channel access

• a platform capable of supporting both edge and core dense wavelength division multiplexing (DWDM) applications

• a platform that provides one of the richest optical layer performance monitoring tools on the market

Common Photonic Layer is a next-generation DWDM optical line solution that aims to greatly simplify installation, deployment and capacity addition/deletion and operations throughout the platform lifetime. It provides the foundation to turn-up end-to-end wavelength services rapidly through automated control and a rich suite of optical layer performance monitoring capabilities.

Link engineering and capacityThe Common Photonic Layer architecture supports DWDM wavelengths in the C-band with:

• 100 GHz spacing with a 36-wavelength capacity with 8 additional skip channels supported on CMD44 for a total of 44 wavelengths

• 50 GHz spacing with a 72-wavelength capacity with 16 additional skip channels supported on CMD44s for a total of 88 wavelengths

Both 100 GHz and 50 GHz sources can be connected to CMD44s, SCMD4s, or the Open SCMD8s. Wavelengths must adhere to the ITU G.698.1 narrow 100 GHz specification. In the Nortel portfolio, these include 50 GHz and 100 GHz wavelengths designated to operate on the Common Photonic Layer spectral grid. These wavelengths can be routed through both the GMD and WSS modules.

The Filtered SCMD8s can only support the 50 GHz OME6500 Broadband 10G NGM eDCO wavelengths, but a mixture of eDCO and non-eDCO wavelengths can be routed through the GMD and WSS modules.

For 50 GHz OME6500 40G eDCO wavelengths, it is recommended to use Open SCMD8s (contact Nortel if the use of Filtered SCMD8s with 50 GHz OME6500 40G eDCO wavelengths is required).




Overview 2-3

Attention: Connecting any mixture of optical systems to the same CMD may require specialized link budget and equipping rules. Mixed-wavelength CMD applications should be validated with Nortel prior to deployment.

The Common Photonic Layer architecture is capable of supporting a variety of different line rates at 50 GHz or 100 GHz spacing, including but not limited to:

• 2.5 Gbit/s (OC48/STM16)

• 10 Gbit/s (OC192/STM64)

• 10.3 (11.1) Gbit/s 10 GE LAN PHY

• 10.7 Gbit/s (OTU2) 10 GE LAN PHY

• 40 Gbit/s (OC768/STM256/OTU3)

• 100 Gbit/s (OTU4)

A mix of 100 GHz Common Photonic Layer-compliant Optical Metro 5100/5200 2.5G and 10G sources are supported on a Common Photonic Layer Open sCMD8. Optical Metro 5100/5200 2.5G tunable circuit packs can be tuned to 50 GHz CPL-compliant channels supported by the Open sCMD8 (NTT861BA-BJ).

Typical system reach is up to 2000 km without dispersion compensation and using erbium-doped fiber amplifier (EDFA) technology covering core, regional, and edge applications.

The Distributed Raman Amplification (DRA) module provides a counter-propagating Raman amplifier solution that can minimize the impact of long, lossy spans in multi-span applications. DRA extends span reach, which is dependent on the fiber type (see “DRA supported deployments” on page 2-56). The DRA reduces network regeneration when it is deployed on spans that are affecting the overall system reach and forcing regeneration points.

The Common Photonic Layer architecture supports multiple fiber types including:

• Non-Dispersion Shifted Fiber (NDSF)

• TrueWave Classic (TWc)

• Lambda Shifted Single Mode Fiber (LS)

• Dispersion Shifted Single Mode Fiber (DSF)

• TrueWave Reduced Slope (TWRS)

• TrueWave Plus (TWP)

• Large Effective Area Fiber (LEAF)




2-4 Overview

• Enhanced Effective Area Fiber (ELEAF)

• Freelight (FL)

• Allwave (AW)

Attention: TWRS and LEAF fiber types are not supported with the DRA in the managed mode (see “System description” chapter in Part 2 of this document).

Attention: Nortel Optical Modeler can be used to create Common Photonic Layer link designs. For applications that fall outside the scope of Optical Modeler or if you do not currently have Optical Modeler, contact your Nortel account representative to obtain a detailed custom link design.

Hardware-modular architectureThe Common Photonic Layer directly addresses lower initial first cost by using a modular building block approach to tailor each application with the most cost effective solution. Nortel has also introduced new service flexibility by making the Common Photonic Layer a service-independent platform that interworks with Nortel and foreign (non-Nortel) DWDM wavelengths from other vendors’ multiservice provisioning platform (MSPP), optical-electrical-optical (OEO), or optical cross-connect (OXC) devices.

The Common Photonic Layer’s modular architecture provides optimized network configurations based on the following types of optical modules:

• Channel Mux/Demux (CMD) modules

— 4 Channel Mux/Demux (CMD4)

— 44 Channel Mux/Demux 100 GHz C-Band (CMD44)

— Enhanced 44 Channel Mux/Demux 100 GHz C-Band (eCMD44)

— 44 Channel Mux/Demux 50 GHz C-Band (CMD44)

— Serial 4 Channel Mux/Demux (SCMD4)

— Serial 8 Channel Mux/Demux (SCMD8)

— Channel Mux/Demux Amplifier (CMDA)

• Broadband Mux/Demux 1x2 (BMD2)

• Group Mux/Demux (GMD) module

• Amplifier modules

— Single Line Amplifier (SLA): single (pre-amplifier) EDFA

— Mid-stage Line Amplifier (MLA): dual (pre-amplifier/booster) EDFA

— Mid-stage Line Amplifier 2 (MLA2): dual (pre-amplifier/booster) EDFA




Overview 2-5

— Line Interface Module (LIM)

— Distributed Raman Amplifier (DRA)

• Dual Optical Service Channel (DOSC) module

• Uni Optical Service Channel (UOSC) module

• Wavelength Selective Switch 5 x 1 - 50 GHz (WSS)

• Wavelength Selective Switch 5 x 1 - 100 GHz (WSS)

• Optical Power Monitor (OPM)

• Dispersion Slope Compensation Modules (DSCM)

— DSCM Type 1 (NDSF)

— DSCM Type 2 (TWRS)

— DSCM Type 3 (TWCL)

— DSCM Type 5 (ELEAF)

The Common Photonic Layer product is based on a backplane-less architecture, therefore, required modules are simply interconnected to provide optimized low-cost solutions. Since there is no backplane to provide power to the various modules or to provide inter-module communications, these connections are handled through a power cable harness from a breaker interface panel (BIP) and ethernet cable connections, respectively. The backplane-less architecture allows for deployments with impressive reductions in space and footprint, and power consumption.

The Common Photonic Layer is a global platform with a single Network Equipment Building System/European Telecommunications Standards Institute (NEBS/ETSI) footprint.

Software feature benefitsResponding to market demand, the Common Photonic Layer platform meets stringent customer requirements by incorporating features such as:

• optical planning using the Optical Modeler tool

• simplified system lineup and testing (SLAT) using the nodal SLAT assistant tool (SAT)

• optical layer PM statistics including:

— per-channel reporting

— per-group reporting

— OSC signal degrade reporting

• topology discovery




2-6 Overview

• domain optical control consisting of:

— improved reach capability (using fine DGFF and adaptive optical control)

— in-service wavelength activation

— seamless scalability up to 72 50 GHz wavelengths using SCMD8

— seamless scalability up to 88 50 GHz wavelengths using CMD44

— per-channel control for per-channel add/drop

— per-channel control for per-channel attenuation

— per-channel control for per-channel in-service remote wavelength reconfigurability

— support for cascaded LIM between the pre-amp and the WSS or GMD

• branching support including automatic channel add/delete across DOC domains

• per-wavelength and per-group power monitoring

• Site Manager based craft GUI interface

• datacomms configurations support for a variety of options including:

— single and dual GNE configurations

— DCN drops

Common Photonic Layer site descriptions and building blocksA high-level view of the various building blocks used to perform the distinct functions at the different site types is described in this section. The site types include:

• Terminal site on page 2-7

• Line Amplifier site on page 2-12

• Line Amplifier site with Distributed Raman Amplifiers (DRA) on page 2-12

• eDCO line amplifier site on page 2-13

• GMD based OADM site on page 2-14

• TOADM site on page 2-15

• All TOADM rings on page 2-17

• ROADM on page 2-18


• Coarse DGFF site on page 2-33

• Fine DGFF site on page 2-33

• Linear spur site on page 2-34

• Branch site using WSSs on page 2-36

• Single span CMD44 point-to-point terminal on page 2-43




Overview 2-7

Terminal siteA terminal site is a site where all channels that form the photonic layer are terminated at the service layer. Three kinds of terminal sites are available: GMD based, WSS based, and Thin based. Table 2-2 shows the building blocks for each type of terminal site.

Table 2-2Terminal sites

Type of terminal site

Building blocks Number Figure showing photonic connections

GMD terminal GMD 1 Figure 2-1 on page 2-8

CMD4, SCMD4, SCMD8 1 to 9

SLA, MLA, MLA2, or LIM 1

DRA (optional) 0 or 1

WSS terminal UOSC or DOSC 1 Figure 2-2 on page 2-9, Figure 2-3 on page 2-10, and Figure 2-4 on page 2-11

SCMD4, SCMD8, CMD44(see Note 1, Note 2, Note 3, and Note 4)

1 to 9

CMDA (optional) 1

WSS 1

OPM (see Note 5) 1

MLA or MLA2 1

SLA (for loss-less DSCM function if compensation is required)

1


Thin terminal UOSC 1 Figure 2-31 on page 2-44 and Figure 2-32 on page 2-45

SCMD (see Note 1) 1 to 9

CMD44 (see Note 6) 1

MLA, MLA2, SLA, LIM (see Note 7) 1





2-8 Overview

Figure 2-1 shows the photonic connections between the different modules at a GMD based terminal site.

Figure 2-1Common Photonic Layer - GMD based terminal building blocks

Note 1: The software allows up to 9 SCMDs to be provisioned. Optical Modeler may limit this number for link engineering reasons.

Note 2: CMD4s can only be used at a WSS terminal when used at the end of a cascade.

Note 3: CMD44s cannot be cascaded from an SCMD4. CMD44s must be connected to its own WSS port either directly or using a CMDA.

Note 4: SCMD4, SCMD8, or CMD44 modules cannot be cascaded from switch port 1 of a WSS at a terminal site.

Note 5: An OPM can be shared between OTSs with the same or different OSID.

Note 6: The CMD44 point-to-point terminal is a low cost, low functionality point-to-point configuration application (see “Single span CMD44 point-to-point terminal” on page 2-43).

Note 7: LIM, SLA or MLA2 amplifiers are not supported for the CMD44 point-to-point terminal.

Table 2-2 (continued)Terminal sites

Type of terminal site

Building blocks Number Figure showing photonic connections

CMD4 GMD

9

Group Mux

OS

C

9

Group Demux

MLA

4

Ch Mux

4

Ch Demux

Tx

Rx




Overview 2-9

Figure 2-2 shows the photonic connections between the different modules at a WSS based terminal site using SCMD4 and SCMD8.

Figure 2-2Common Photonic Layer - WSS based terminal building blocks (SCMD4 and SCMD8)

UOSC or DOSC OPM

WSS

Mux

Mux

OSC

MLA/MLA2

SCMD4

SCMD8

Demux

Demux




2-10 Overview

Figure 2-3 shows the photonic connections between the different modules at a WSS based terminal site using CMD44 100 GHz.

Figure 2-3Common Photonic Layer - WSS based terminal building blocks (CMD44 100 GHz)

UOSC or DOSC

WSS

OutSwitch 1

Switch 2

Switch 3

CommonOut

CommonIn

Switch 4

Switch 5

In

OutIn

OutIn

OutIn

OutIn

OSC

MLA/MLA22

11

12

1

43

65

87

109

Common Out

Common In

44 C

hann

el M

UX

/DE

MU

X

1 Ch1 In CMD44

Ch1 Out2

90

89

3 Ch2 In

Ch2 Out4

85 Ch43 In

Ch43 Out86

87 Ch44 In

Ch44 Out88

OPM




Overview 2-11

Figure 2-4 shows the photonic connections between the different modules at a WSS based terminal site using two CMD44 50 GHz (Red and Blue) and a CMDA.

Figure 2-4Common Photonic Layer - WSS based terminal building blocks (CMD44 50 GHz and CMDA)

UOSC or DOSC

WSS

OutSwitch 1

Switch 2

Switch 3

CommonOut

CommonIn

Switch 4

Switch 5

In

OutIn

OutIn

OutIn

OutIn

OSC

2

11

12

1

43

65

87

109

Common Out

Common In

44 C

hann

el M

UX

/DE

MU

X

1 Ch1 In CMD44 50 GHz Blue

Ch1 Out2

90

90

89

89

3 Ch2 In

Ch2 Out4

85

85

Ch43 In

Ch43 Out86

86

87

87

Ch44 In

Ch44 Out88

88

Common Out

Common In

44 C

hann

el M

UX

/DE

MU

X

1 Ch45 In CMD4450 GHz Red

Ch45 Out2

3 Ch46 In

Ch46 Out4

Ch87 In

Ch87 Out

Ch88 In

Ch88 Out

OPM

MLA/MLA2

CMDA

∑

∑1

36

2

4

5




2-12 Overview

Line Amplifier siteFigure 2-5 shows a Line Amplifier site. The building blocks of a Line Amplifier site are:

• one DOSC

• two SLAs or MLAs or MLA2s (Figure 2-5 shows MLAs)

• DSCMs (optional)

Figure 2-5Common Photonic Layer - Line Amplifier building blocks

Line Amplifier site with Distributed Raman Amplifiers (DRA)Figure 2-6 shows a Line Amplifier site with DRA. DRAs are optional at any site. The building blocks of a Line Amplifier site with DRAs are:

• one DOSC

• two MLAs or MLA2s

SLAs are not supported as the LIM with a DRA module in any configuration, unless the SLA is used in combination with a MLA/MLA2 in the loss-less DSCM function.

• DSCMs (optional)

• one DRA per line direction (optional)

DOSC

OS

C

OS

C

MLA MLA

DSCM

DSCM




Overview 2-13

Figure 2-6Common Photonic Layer - Line Amplifier building blocks with DRA

eDCO line amplifier siteFigure 2-7 and Figure 2-8 show Electronic Dynamically Compensating Optics (eDCO) line amplifier sites. eDCO provides improved dispersion management and longer reach.

Inter operability of Common Photonic Layer and Optical Multiservice Edge 6500 eDCO circuit packs provides the benefits of the eDCO in the Core and Long Haul market segments. The use of eDCO reduces the requirements of dispersion compensation in the Common Photonic Layer network and allows channel agility.

The eDCO Line Amplifier site is an amplifier site without DSCMs and is for use with eDCO wavelengths. The building blocks of an eDCO Line Amplifier site are:

• one DOSC

• two EDFAs the following combinations are supported

— one MLA/ MLA2 and one LIM

— SLA-SLA pair

DOSC

OS

C

OS

C

MLA MLA

DSCM

DSCM

DRA

Line B In Line B Out

Line A Out Line A In

(Pump Out)

2

3

B

A

1

4

DRA

Line B InLine B Out

Line A OutLine A In

(Pump Out)

1

4

2

3

B

A




2-14 Overview

Figure 2-7Common Photonic Layer - eDCO MLA and LIM site building blocks

Figure 2-8Common Photonic Layer -eDCO SLA and SLA site building blocks

GMD based OADM siteThe optical add-drop multiplexer (OADM) GMD based site provides the ability to add/drop any channel available in the photonic system. As shown in Figure 2-9, this OADM site can contain the following elements:

• two GMDs

• two to 18 CMDs (CMD4, SCMD4, SCMD8) (Figure 2-9 shows CMD4s)

• two SLAs/MLAs/MLA2/LIMs (Figure 2-9 shows MLAs)

• two DRAs (optional)

The GMD provides group-level granularity while the SCMDs and the CMD4s provide the per channel add/drop capabilities.

DOSC

OS

C

OS

C

MLA/MLA2 LIM

DOSCO

SC

OS

CSLA SLA




Overview 2-15

Figure 2-9Common Photonic Layer - GMD based OADM building blocks

TOADM siteThe TOADM site provides the ability to add/drop channels, without the requirement of having GMD at the site. As shown in Figure 2-10, the TOADM site can be comprised of the following elements:

• two UOSCs (one per facing direction/logical network element) or one DOSC

• up to 9 SCMDs per facing direction/logical network element or a total of 18 SCMDs at a site. The software allows a maximum number of 9 SCMDs to be provisioned per facing direction/logical network element. Optical Modeler may limit this number for link engineering reasons.

• two EDFA (SLA, MLA, MLA2, LIM), 1 per facing direction/logical network element (Figure 2-10 shows MLAs). See TOADM to TOADM configurations on page 2-17 for limitations.

• two DRAs (optional), 1 per facing direction/logical network element

4

CMD4

ChMux

ChDemux

4

MLA

OS

C

OS

C

MLA

4

CMD4

ChMux

ChDemux

4

GMD

9

Group Mux

9

9

9

Group DemuxGroup Mux

Group Demux

GMD

Tx Rx Tx Rx




2-16 Overview

The UOSC or DOSC provides the shelf controller and OSC functionality for access sites at which a GMD is not deployed. A DOSC can be used to replace two UOSCs (East and West facing). The SCMD have group filtering functionality, this allows the SCMD to be serially cascaded as shown in Figure 2-10. When a TOADM site is placed between GMD (OADM) sites, the link budget for the express groups is unaffected.

Figure 2-10Common Photonic Layer - TOADM building blocks

UOSC*

DSCM(optional)

Mux

OSC

MLA

SCMD

Group x

Group y

Demux

Mux

Demux

Group z

Mux

Demux

UOSC*

DSCM(optional)

Mux

OSC

MLA

SCMD

Group z

Where groupnumbers x<y<z

West facing logicalnetwork element #2

East facing logicalnetwork element #1

Group y

Demux

Mux

Demux

Mux

Demux

Group x

Note: * A DOSC can be used instead of two UOSCs.




Overview 2-17

Figure 2-10 shows three groups of add and drop; however there could be more or less depending on the requirements and the link budget implications. Similarly, the amplification requirements would be determined on a link-by-link basis. This figure also shows two facing directions with the SCMDs interconnected in such a way that there is east-west separability with no single point of failure for both add/drop and express traffic. Symmetry between the dropped and added channels, is not required. There may be different groups added and dropped from the two directions or even a different number of groups. The order of the cascade must be known.

TOADM to TOADM configurationsIn configurations where two TOADM shelves at different sites are connected, DOC will not operate correctly (for example, channels cannot be added) if a LIM is equipped at both the facing TOADM shelves. For DOC to operate correctly, one of the following supported configurations for the facing TOADM shelves must be deployed:

All TOADM ringsAn all-TOADM ring with optical pass through at all sites is not supported since the ring is subject to lasing effects as the amplified spontaneous emission (ASE) is re-circulated around the ring. To avoid this condition, two possible solutions are possible:

1 At least one TOADM site in the ring must be provisioned as two Thin Terminals with no optical pass through connection. This forms an optical seam and prevents the ASE lasing condition.

If the two Thin Terminals have the same SiteID, DOC assumes that the two Thin Terminals configuration is a true TOADM and assumes a passthrough optical path (no optical seam). This creates an artificially high noise channel power in DOC calculations. As a result, channel add operations may not be possible. To avoid this condition, provision different SiteIDs for the two Thin Terminals. This creates a linear topology as opposed to a ring topology. In order to assign different SiteIDs to each Thin Terminal, each Thin Terminal must reside in a different CPL shelf.

2 At least one TOADM site in the ring must instead be a ROADM site. The ROADM site filters out the ASE and prevents the ASE lasing condition.

Site x Site y

SLA < - > SLA

LIM < - > MLA

MLA < - > LIM

LIM (sCMD) < - > LIM

LIM < - > LIM (sCMD)




2-18 Overview

ROADMThe remotely reconfigurable optical add-drop multiplexer (ROADM) site provides the ability to remotely and automatically reconfigure optical networks. As shown in Figure 2-11, the ROADM site can be comprised of the following elements:


• two to 18 SCMDs, CMD44s (one CMD44 100 GHz or two CMD44 50 GHz). You can have any mix of SCMD4s, SCMD8s, and CMD44s. CMD4s can be used at a WSS node if used at the end of a cascade of SCMDs.

• two MLA/MLA2 (Figure 2-11 shows MLAs)

• two DRAs (optional)

• one OPM shared between two WSSs

• two WSS

• one SLA per facing direction

If compensation is used, a cascaded LIM per facing direction is required to provide a loss-less DSCM function for control purposes (see Figure 2-12 on page 2-20).

The WSS is fully flexible. Any of the WSS switch ports on the WSS can be used for branched passthrough. For passthrough channels in the same domain, switch port 1 must be used. Any port except port 1 can be used for local add/drop.

The UOSC or DOSC provides the shelf controller and OSC functionality for access sites at which a GMD is not deployed. A DOSC can be used to replace two UOSCs.




Overview 2-19

Figure 2-11Common Photonic Layer - ROADM building blocks

UOSC*

West facing NE East facing NE

WSS

OutSwitch 1

Switch 2

Switch 3

CommonOut

CommonIn

Switch 4

Switch 5

Mux

In

OutIn

OutIn

OutIn

OutIn

OSC

MLA/MLA2

SCMD4

SCMD8

SCMD4

SCMD8

FTMux

FTMux

16GHzDemux

16GHzDemux

UOSC*

OSCOPM

Demux

Mux

Demux

MLA/MLA22

11

12

1

43

65

87

109

WSS

In Switch 1

Switch 2

Switch 3

CommonOut

CommonIn

Switch 4

Switch 5

Out

InOut

InOut

InOut

InOut

12

11

1

3

5

7

9

4

6

8

10

2

LC

Common Out

Common In

LC

44 C

hann

el M

UX

/DE

MU

X

1 Ch1 In

Ch1 Out2

3 Ch2 In

Ch2 Out4

LC

LC

85 Ch43 In

Ch43 Out86

87 Ch44 In

Ch44 Out88

CMD44





2-20 Overview

Figure 2-12ROADM site with MLAs and cascaded LIMs

A

BLi

ne B

In67

58

MLA

Shel

f1, S

lot2

Mon

itor 1

Mon

itor 2

21

OSC

B In

OSC

A O

ut

3 4

Line

A In

A

Line

B In

67

58

SLA

Shel

f1, S

lot1M

onito

r 1

Mon

itor 2

21

OSC

B In

3 4

DSC

M

Shelf

1, FM

T1In

Out

WSS 1X5

Sw

itch1

Out

Sw

itch1

In

2 1

Sw

itch2

Out

Sw

itch2

In

4 3

Sw

itch3

Out

Sw

itch3

In

6 5

Sw

itch4

Out

Sw

itch4

In

8 7

WS

S

Shel

f1, S

lot3

Sw

itch5

Out

Sw

itch5

In

10 9

Com

mon

In

Com

mon

Out

11 12

WSS 1X5

Sw

itch1

In

Sw

itch1

Out

1 2

Sw

itch2

In

Sw

itch2

Out

3 4

Sw

itch3

In

Sw

itch3

Out

5 6

Sw

itch4

In

Sw

itch4

Out

7 8

WS

S

Shel

f2, S

lot3

Sw

itch5

In

Sw

itch5

Out

9 10

Com

mon

Out

Com

mon

In

12 11

Line

B In

B

Line

A O

utA

Line

A In

85

76

MLA

Shel

f2, S

lot2

Mon

itor 1

Mon

itor 2

21

OSC

B In

OSC

A O

ut3 4

DSC

MIn

Out

Line

B In

Line

A O

utA

Line

A In

85

76

SLA

Shel

f2, S

lot1

Mon

itor 1

Mon

itor 2

21

OSC

B In

OSC

A O

ut

3 4

UO

SC

*O

SC 1O

SC1

In

1 1

OSC

1 O

ut

Shel

f2, S

lot4

OP

MO

PMM

onito

r 2

1 2

Mon

itor 1

Mon

itor 4

3 4

Mon

itor 3

Shel

f1, S

lot1

3

UO

SC

*O

SC 1O

SC1

In

1 1

OSC

1 O

ut

Shel

f1, S

lot4

Shelf

2, FM

T1

Loca

tion

1Lo

catio

n 2

SC

MD

SC

MD

SC

MD

SC

MD

Loca

tion

1Lo

catio

n 2

Line

A In

Line

B O

ut

Line

A O

utLi

ne A

Out

Line

B O

ut

Line

B O

utLi

ne B

Out

OS

CA

Out

Not

e: *

A D

OS

C c

an b

e us

ed

inst

ead

of tw

o U

OS

Cs.




Overview 2-21

Global engineering rules for SCMD and CMD44 group deployment order and WSS port allocationTo minimize gain tilt/gain ripple effect, it is recommended that, when possible, the group capacity be allocated according to the following guidelines to grow network capacity.

• For non eDC40G wavelengths, start with 1564.68 nm and expand towards 1530.33 nm, unless specified otherwise in the OPNET custom link design report or Optical Modeler.

• For eDC40G wavelengths, refer to OPNET custom link design report or Optical Modeler.

Optical Modeler WSS port allocation guidelines • Never place SCMDs or a CMD44 on switch port 1 (SW1). SW1 is

designated as the express path only.

• SW1 must be used when interconnecting the two WSS modules belonging to the same OSID.

• Always append SCMDs to cascades at ROADM nodes. Never insert them (so as not to impact existing wavelengths).

• Minimize cascade lengths by spreading the SCMDs across all the user-defined available switch ports. The shorter the cascade, the better the performance.

• Place SCMDs and CMD44s on the highest (as in SW5 first, then SW4, etc.) available switch ports. This placement allows you to defer the decision on how many switch ports should be reserved for branching. With switch ports 3, 4, and 5 enabled on WSS modules on a ROADM-ROADM link, when you auto-assign 72 demands between the ROADMs, you should have the following SCMD order:

— Switch port 3 = groups 7, 4 and 1



Direction Independent Access (DIA)Previous to Release 4.0, ROADM configurations were directionally dependent where a Tx/Rx pair connected to a CMD could only be sent in the direction of the line ports of the WSS connected to the CMD.

Direction Independent Access (DIA) allows the user to determine the optical direction of a channel from a site using software and not a physical connection. A DIA terminal uses standard WSS, amplifier, and OPM components to create a directionally independent access point. A DIA simplifies the planning of ROADM sites and networks by allowing wavelengths to be remotely redirected to another direction as the bandwidth requirements change.




2-22 Overview

Figure 2-13 shows a 5-way ROADM site with one DIA terminal using the 1x5 100 GHz WSS (only the transmit direction is shown).

Figure 2-135-way ROADM with single DIA




Overview 2-23

A DIA supports directional control of 44 (100 GHz eCMD44) or 88 (50 GHz CMD44s) wavelengths. Each optical direction has capacity up to 88 wavelengths via combination of passthrough, DIA add/drop, and local add/drop. All outgoing lines must be in different domains.

Figure 2-14 show the building blocks for a DIA terminal configuration.

Figure 2-14DIA terminal building blocks

As shown in Figure 2-14, the DIA terminal can be comprised of the following elements:

• CMD44:

— For 50 GHz systems: CMD44 50 GHz Blue and CMD 50 GHz Red

— 100 GHz systems: eCMD44 100 GHz

• BMD2: Only required when using the CMD44 50 GHz.

• LIM (MLA, SLA, or MLA2): MLA is used in most scenarios, some situations may require MLA2, SLA, or LIM (determined by link budget).

• OPM: Used for per channel measurement for WSS control.

MLA/SLA/MLA2BMD2CMD44xGHz WSS xGHz

OPM

To/From 1st DirectionMux

Demux

∑

∑

∑

WSS

To/From 2nd Direction

To/From 3rd Direction

To/From nth Direction

A

B




2-24 Overview

• WSS: WSS 1x5 100 GHz or WSS 1x5 50 GHz

— In the transmit direction (Tx Broadcast), the wavelengths from the CMD44 are optically broadcast from each enabled switch to each exiting direction.

— In the transmit direction (Rx Select), each wavelength is selected from a direction by each switch.

• UOSC or DOSC: DIA terminal can be controlled either by it’s own UOSC or DOSC or by a DOSC which controls another WSS direction. However, OSC is not used on the DIA terminal.

DIA terminal configurationsThe following DIA terminal configurations are supported:

• 1x5 WSS 50 GHz -- LIM -- BMD2 -- 50 GHz CMD44 Red and Blue (see Figure 2-15 on page 2-25)

• 1x5 WSS 50 GHz -- LIM -- BMD2 -- 50 GHz CMD44 Red only (extra ports on BMD2 for future upgrade) (see Figure 2-16 on page 2-26)

• 1x5 WSS 50 GHz -- LIM -- BMD2 -- 50 GHz CMD44 Blue only (extra ports on BMD2 for future upgrade) (see Figure 2-17 on page 2-27)

• 1x5 WSS 50 GHz -- LIM-- 100 GHz eCMD44 (see Figure 2-18 on page 2-28)

• 1x5 WSS 100 GHz -- LIM -- 100 GHz eCMD44 (see Figure 2-18 on page 2-28)

Attention: The shelf controller (UOSC or DOSC) is not shown in the configuration figures. A DIA terminal can be controlled either by it’s own UOSC or DOSC or by a DOSC which controls another WSS direction.




Overview 2-25

Figure 2-15DIA terminal configuration: 1x5 WSS 50 GHz -- LIM -- BMD2 -- 50 GHz CMD44 Red and Blue




2-26 Overview

Figure 2-16DIA terminal configuration: 1x5 WSS 50 GHz -- LIM -- BMD2 -- 50 GHz CMD44 Red only




Overview 2-27

Figure 2-17DIA terminal configuration: 1x5 WSS 50 GHz -- LIM -- BMD2 -- 50 GHz CMD44 Blue only




2-28 Overview

Figure 2-18DIA terminal configuration: 1x5 WSS 50 GHz (or 1x5 WSS 100 GHz)-- LIM-- 100 GHz eCMD44




Overview 2-29

DIA terminal engineering guidelinesThe following are the engineering guidelines for the DIA terminal:

• DIA is only supported at ROADM sites.

• The DIA NE must be TID-Consolidated with the line facing ROADM NEs.

• DIA is only supported when using the DOC Enhanced automation mode. DOC considers the DIA to be a single configuration. The DIA amplifier gain is set during the OTS creation and is not controlled by DOC.

• A wavelength can only be dropped once per direction at a site.

— A wavelength can either be dropped to a CMD on a backbone WSS or the DIA CMD44 at the same site.

— Once the channel is dropped at a CMD on a backbone WSS, it is blocked by software from dropping at a DIA CMD44 at the same site.

• A wavelength can only be added once per direction at a site.

— A wavelength can either be added at a CMD on a backbone WSS or the DIA CMD44 at the same site.

— Once the channel is added at a CMD on a backbone WSS, it is blocked by software from being added in the same optical direction at the DIA CMD44 at the same site

• A DIA does not contain a DOC facility, no OSID is configured for the DIA.

• All the line side WSS modules connected to the DIA must be in different optical domains.

• A DIA can be controlled either by it’s own UOSC or DOSC or by a DOSC which controls another WSS direction. However, OSC is not used on the DIA terminal.

• DRA amplifiers are not supported within the DIA.

• Maximum number of DIAs per site is 2.

• The following components are not supported in DIA terminal configurations and are blocked by software:

— CMD4, sCMD4, sCMD8, and CMDA

— DSCMs.

— CMD44 100 GHz (must be eCMD44 100 GHz).

— BMD2 with CMD44 100 GHz or eCMD44 100 GHz

— GMD (unless GMD is only used as a virtual shelf processor)

— DRA

• The maximum number of OPMs per shelf is one. In a site where all shelves have one OTS, the DIA OPM can be shared with any shelf.

• DIA configurations are set to Channel Access.




2-30 Overview

• A DIA is provisioned by setting the DIA subtype to ‘DIA’ in the OTS configuration dialogs.

• The DIA amplifier has ALSO disabled.

• The amplifier in the DIA does not support OSC and is not in a paired amp configuration.

• If there is a fiber break, the DIA amplifier either shuts down or goes into APR.

DIA site configurationsThis section provides examples of typical DIA site configurations:

• Single DIA with 5-way branch, no local add/drop on line-facing WSS modules (see Figure 2-19 on page 2-31)

The DIA in this type of configuration allows the user to:

— increase the route diversity (send the same source wavelength on multiple domains)

— increase the high available links (allows the wavelength to always have two valid paths)

• Dual DIA with 4-way branch, no local add/drop on line-facing WSS modules (see Figure 2-20 on page 2-32)

The Dual DIA in this type of configuration allows the user to:



— increase the channel count (can use the same wavelength as active in two directions)

— provide redundancy on the functionality of the DIA terminal

• Dual DIA with 3-way branch, local add/drop on line-facing WSS modules (see Figure 2-21 on page 2-32)

The Dual DIA in this type of configuration allows the user to:



— increase the channel count (can use the same wavelength as active in two directions)

— provide redundancy on the functionality of the DIA terminal

— have add/drop specific traffic per domain




Overview 2-31

The WSS used for the DIA terminal must be on the same grid (50 GHz or 100 GHz) as the WSS used on the backbone (line-facing WSSs) except for a configuration using a WSS 50 GHz for the DIA terminal and WSS 100 GHz for the line-facing WSSs. In this configuration, an eCMD44 100 GHz must be used at the DIA terminal and the line-facing WSSs can only add/drop 100 GHz channels to the DIA terminal.

Figure 2-19Single DIA with 5-way branch (no local add/drop on line-facing WSS modules)




2-32 Overview

Figure 2-20Dual DIA with 4-way branch (no local add/drop on line-facing WSS modules)

Figure 2-21Dual DIA with 3-way branch (local add/drop on line-facing WSS modules)




Overview 2-33

Coarse DGFF siteThe coarse dynamic gain flattening filter (DGFF) site, shown in Figure 2-22, is a variant of an OADM site with all group connections glassed-through. The coarse DGFF provides a per-group attenuation profile for control purposes to overcome the accumulation of gain tilt and ripple in an optical link. As shown in Figure 2-22, the course DGFF site is comprised of the following elements:

• two GMDs


Figure 2-22Common Photonic Layer - Coarse DGFF building blocks

Fine DGFF siteThe fine dynamic gain flattening filter (DGFF) site, shown in Figure 2-23, is a variant of an ROADM site with select channel glass-through. The fine DGFF provides a per-wavelength attenuation profile for control purposes to overcome the accumulation of gain tilt and ripple in an optical link. As shown in Figure 2-23, the fine DGFF site is comprised of the following elements:


• two WSSs


— the type of EDFA; MLA or MLA2, depends upon the span losses into the fine DGFF site.

— if the link is a compensated, a cascaded LIM is required per facing direction with DSCM, to provide loss-less DSCM function for control purposes. eDCO links do not require a cascaded LIM since DSCMs are not used.

• one OPM

MLA2

OS

C

OS

C

MLA2

GMD

9

Group Mux

9

9

9


Group Demux

GMD




2-34 Overview

Figure 2-23Common Photonic Layer - Fine DGFF building blocks

Linear spur siteThe linear spur site, shown in Figure 2-24, is a backbone and remote site where traffic can be dropped off of the main backbone because the remote site is a short distance from the backbone. As shown in Figure 2-24, the linear spur site is comprised of the following elements:

• Backbone elements: (GOADM)

— two GMDs (network elements #1 and #2)

— one UOSC (network element #3)

— CMDs connected to and managed by the GMDs at backbone

— SCMDs connected to and managed by the UOSC (element #3)

— three EDFAs (MLAs, MLA2s, or SLAs)

• Remote site, end of spur elements:

— one EDFAs (MLAs, MLA2, SLA)

— one UOSCs at end of spur

— one (S)CMDs

Attention: Figure 2-24 shows CMD4s and SCMD4s. However, this site can be comprised of any type of (S)CMDs.

UOSC*

WSS

Out1

2

3

CommonOut

CommonIn

4

5

In

OutIn

OutIn

OutIn

OutIn

OSC

MLA2

UOSC*

OSCOPM

MLA2WSS

In 1

2

3

CommonOut

CommonIn

4

5

Out

InOut

InOut

InOut

InOut





Overview 2-35

Figure 2-24Common Photonic Layer - Linear Spur building blocks

CMD4

MLA

OS

C

OS

C

MLA

SCMD4

UOSC

Demux

MuxDemux

Mux

SCMD4

DemuxMux

MLA

MLA

GMD

9

Group Mux

9

9

9


Group Demux

GMDBackbone site

Remote site at end of spur

Networkelement # 2

Networkelement # 3

UOSC

Networkelement # 4

Networkelement # 1




2-36 Overview

Branch site using WSSsOptical branching allows for more flexible networks and allows for the removal of channel-terminating regenerators at branching sites. Release 4.0 supports 3-way, 4-way, and 5-way branch sites.

Attention: The supported branch count includes both WSS branches and spurs at a site (a 3-way ROADM with two spurs is considered a 5-way branch).

Each branch can at the site requires either it’s own shelf controller (UOSC or DOSC) or a DOSC can be shared between two branches.

3-way Y-branch siteThe Y-branch site is a 3-way branch site involving 3 different domains. The Y-Branch site consists of 3 WSS modules from 3 different domains. Each WSS can be connected to SCMDs (see Figure 2-25) or a CMD44 (see Figure 2-26) for local add/drop.

Figure 2-25ROADM 3-way Y-branch using SCMD (or spurs)

Domain B

Domain A Domain C

SCMD SCMD

SCMD

SCMD

AMP

Tx/Rx

Tx/Rx




Overview 2-37

Figure 2-26ROADM 3-way Y-branch (WSS-WSS-WSS) with local add drop

3-way T-branch siteThe T-branch site is also a 3-way branch site involving 2 different domains. The T-Branch site contains 3 WSS modules, 2 WSS modules in one domain and the other WSS module in a different domain. Each WSS can be connected to SCMDs or a CMD44 for local add/drop (see Figure 2-27).

When only a few channels are in a branch, branching with SCMD modules (or spurs) can be used.

Domain B

Domain A Domain C

Tx/

Rx

Tx/

Rx

Tx/Rx

SC

MD

SC

MD

CMD44........




2-38 Overview

Figure 2-27ROADM 3-way T-branch (WSS-WSS-WSS) with local add drop

4-way branch siteAt 4-way branching sites, four WSS modules are required (see Figure 2-28). For each WSS module, three of the WSS switch ports are used for branching (interconnecting the four WSS modules). The remaining two WSS switch ports per direction can be used for 100% add/drop capability as follows:

• full-fill 88 wavelengths using Red and Blue CMD44 50 GHz, with or without a CMDA

• full-fill 88 wavelengths using Red and Blue CMD44 50 GHz with CMDA on one of the ports and a cascade of SCMDs on the other port (for example, for spurs)

• partial fill (less than 88 wavelengths) using one CMD44 (50 GHz or 100 GHz) on one of the ports and a cascade of SCMDs on the other port

5-way branch siteAt 5-way branching sites, five WSS modules are required (see Figure 2-29 on page 2-40). For each WSS module, four of the WSS switch ports are used for branching (interconnecting the five WSS modules). The remaining WSS switch port per direction can be used for 100% add/drop capability as follows:

• full-fill 88 wavelengths using Red and Blue CMD44 50 GHz with a CMDA (CMDA is required as only one free WSS port)

• partial fill (less than 88 wavelengths) using either one CMD44 (50 GHz or 100 GHz) or a cascade of SCMDs

Domain B

Domain A

Tx/

Rx

Tx/

Rx

Tx/Rx

SC

MD

SC

MD

CMD44.........




Overview 2-39

Figure 2-284-way branching - site interconnections

uni OSC

OSC

MLA/MLA2 WSS

OutSwitch 1

Switch 2

Switch 3

CommonOut

CommonIn

Switch 4

Switch 5

In

OutIn

OutIn

OutIn

OutIn

2

11

12

1

43

65

87

109

uni OSC

OSC

MLA/MLA2WSS

Out Switch 1

Switch 2

Switch 3

CommonOut

CommonIn

Switch 4

Switch 5

In

OutIn

OutIn

OutIn

OutIn

11

12

uni O

SC

OS

C

WS

S

Out

Sw

itch

1

Sw

itch

2

Sw

itch

3

Com

mon Out

Com

mon In

Sw

itch

4

Sw

itch

5

InOut

InOut

InOut

InOut

In

2

1112

1436587109

MLA

/MLA

2

uni O

SC

OS

C

WS

S

Out

Sw

itch

1

Sw

itch

2

Sw

itch

3

Com

mon Out

Com

mon In

Sw

itch

4

Sw

itch

5

InOut

InOut

InOut

InOut

In

2

1112

1436587109

MLA

/MLA

2

1

3

5

7

9

2

4

6

8

10

11

DIR

EC

TIO

N 1

DIRECTION 2 DIRECTION 3

DIR

EC

TIO

N 4

CommonOut

CommonIn

44 C

hann

el M

UX

/DE

MU

X

1 Ch1 In CMD44 50 GHz

BlueCh1 Out2

90

89

90

89

3

1

2

3

Ch2 In

Ch2 Out4

85 Ch43 In

Ch43 Out86

87 Ch44 In

Ch44 Out88

4

85

86

87

88

CommonOut

CommonIn

44 C

hann

el M

UX

/DE

MU

X

Ch45 In CMD4450 GHz

RedCh45 Out

Ch46 In

Ch46 Out

Ch87In

Ch87 Out

Ch88 In

Ch88 Out

CMDA

∑

∑




2-40 Overview

Figure 2-295-way branching - site interconnections

uni OSC

OSC

MLA/MLA2 WSS

OutSwitch 1

Switch 2

Switch 3

CommonOut

CommonIn

Switch 4

Switch 5

In

OutIn

OutIn

OutIn

OutIn

2

11

12

1

43

65

87

109

uni OSC

OSC

MLA/MLA2WSS

Out Switch 1

Switch 2

Switch 3

CommonOut

CommonIn

Switch 4

Switch 5

In

OutIn

OutIn

OutIn

OutIn

11

12

uni O

SC

OS

C

WS

S

Out

Sw

itch

1

Sw

itch

2

Sw

itch

3

Com

mon Out

Com

mon In

Sw

itch

4

Sw

itch

5

InOut

InOut

InOut

InOut

In

2

1112

1436587109

MLA

/MLA

2

uni O

SC

OS

C

WS

S

Out

Sw

itch

1

Sw

itch

2

Sw

itch

3

Com

mon Out

Com

mon In

Sw

itch

4

Sw

itch

5

InOut

InOut

InOut

InOut

In

2

1112

1436587109

MLA

/MLA

2

1

3

5

7

9

2

4

6

8

10

11

DIR

EC

TIO

N 1

DIRECTION 2 DIRECTION 3

DIR

EC

TIO

N 4

uni OSC

OSC

MLA/MLA2WSS

Out Switch 1

Switch 2

Switch 3

CommonOut

CommonIn

Switch 4

Switch 5

In

OutIn

OutIn

OutIn

OutIn

11

12

10

11

DIR

EC

TIO

N 5

CommonOut

CommonIn

44 C

hann

el M

UX

/DE

MU

X

1 Ch1 In CMD44 50 GHz

BlueCh1 Out2

90

89

3 Ch2 In

Ch2 Out4

85 Ch43 In

Ch43 Out86

87 Ch44 In

Ch44 Out88

1

2

90

89

3

4

85

86

87

88

CommonOut

CommonIn

44 C

hann

el M

UX

/DE

MU

X

Ch45 In CMD4450 GHz

RedCh45 Out

Ch46 In

Ch46 Out

Ch87 In

Ch87 Out

Ch88 In

Ch88 Out

CMDA

∑

∑

1

3

5

7

9

2

4

6

8




Overview 2-41

Distributed branch nodesNormally at branching nodes, all the WSS shelves are located at the same site. In some applications, it may be useful if the WSS shelves are not in the same site but still consolidated to form a branching node, which is called a distributed branch node.

To achieve a distributed branch node, an alternative method is required to connect the ILAN ports of the consolidated WSS shelves (see Figure 2-30). Two fiber pairs are required between each WSS shelf:

• one fiber pair carries the passthrough DWDM traffic

• one fiber pair carries the ILAN 100Base-T DCN OSC traffic

A media converter (for example, the Nortel OME1000) is used to convert the electrical ILAN 100Base-T DCN traffic to an optical signal and transmit the signal between the WSS shelves.

Engineering guidelinesThe following are engineering guidelines for distributed branch nodes:

• The loss between the WSS modules must be less than 3 dB (approximately 10 km).

• The media converter must be fully transparent to CPL DCN traffic.

• The 100Base-T ports on the media converters should be configured as follows:

— Speed: 100 Mbit/s full-duplex

— Auto-negotiation: Off

— Link Integrity Notification (LIN): Off

— Flow control: Off

• There is no need to interconnect all the ILAN ports of the consolidated shelves. For example, in Figure 2-30 no ILAN connections exist between the shelves at Site 1 and Site 3 (provisioned but not interconnected).




2-42 Overview

Figure 2-30Distributed branch node

uni O

SC

uni O

SC

ILA

N1

ILA

N2

OS

C

MLA

/MLA

2

MLA

/MLA

2

100B

-T

100B

-T

100B

-T

100B

-T

WS

S

Out

Sw

itch

1

Sw

itch

2

Sw

itch

3

Com

mon

Out

Com

mon

In

Sw

itch

4

Sw

itch

5

In

Out In

Out In

Out In

Out In

2

11 12

1 4 3 6 5 8 7 10 9

uni O

SC

OS

C

MLA

/MLA

2W

SS

Out

Sw

itch

1

Sw

itch

2

Sw

itch

3

Com

mon Out

Com

mon In

Sw

itch

4

Sw

itch

5

In Out

In Out

In Out

In Out

In1112

OSC

WSS

OutSwitch 1

Switch 2

Switch 3

CommonOut

CommonIn

Switch 4

Switch 5

In

OutIn

OutIn

OutIn

OutIn

2

11

12

1

43

65

87

109

1 3 5 7 92 4 6 8 10

11

SIT

E 1

SIT

E 2

SIT

E 3

Med

ia

Con

vert

er

ILA

N1

ILA

N2

ILA

N1

ILA

N2

Med

ia

Con

vert

erM

edia

C

onve

rter

Med

ia

Con

vert

er

Opt

ical

fibe

r pa

irs fo

r pa

ssth

roug

h D

WD

M tr

affic

,m

axim

um lo

ss 3

dB

(~

10 k

m)

Opt

ical

fibe

r pa

irs fo

r O

SC

DC

N tr

affic

,m

axim

um lo

ss 3

dB

(~

10 k

m)

NO

TE

:S

helf

at S

ite 1

is th

e pr

imar

y sh

elf

and

the

gate

way

net

wor

k el

emen

t (G

NE

).




Overview 2-43

Single span CMD44 point-to-point terminalThe single span CMD44 point-to-point terminal application is a low-cost, low functionality application, with the following features and considerations:

• Set-and-forget provisioning:

— Therefore there is no DOC support to optimize the system.

— Channel adds and deletes are performed by direct connection and disconnection to the CMD44.

• There is no topology support, so wavelength routing is not available to higher level applications.

• This system is a strict point-to-point system with no line amplifier sites.

• The single span CMD44 Thin terminal application is not supported by Optical Modeler.

• The application provisioning rules are designed for NDSF fiber with NGM eDCO and Optical Metro 5100/5200 sources. For other sources, fiber types, stretched applications, or provisioning optimized for a particular channel fill, contact Nortel for custom link engineering.

• The single span CMD44 point-to-point terminal application can be unamplified (see Figure 2-31) or amplified (see Figure 2-32 and Figure 2-33).

• The unamplified version:

— consists of one CMD44 100 GHz at each end of the span. There is no advantage to using the CMD44 50 GHz in this application as this module has a higher loss and you are still limited to 44 channels.

— does not require a shelf controller (UOSC), therefore monitoring, alarm, visualization, and other types of information are not available

— is completely passive

— for NGM eDCO sources, set the Tx to +1.5 dBm. Fiber spans of 0 km to 37.5 km of NDSF are supported. This reach is assumed with 0.2 dB/km fiber loss.

— for Optical Metro 5100/5200 sources, set the Tx to +4.2 dBm (use attenuation as necessary as Tx power cannot be set). Fiber spans of 15 km to 76 km of NDSF are supported. For spans less than 15 km, pad the span to at least 3 dB. This reach is assumed with 0.2 dB/km fiber loss.




2-44 Overview

• The amplified version:

— consists of either:

– one CMD44 100 GHz, one UOSCs, and one MLA at each end of the span (see Figure 2-32 on page 2-45). There is no advantage to using the CMD44 50 GHz in this application as this module has a higher loss and you are still limited to 44 channels.

– two 50 GHz CMD44s (one Red and one Blue), one CMDA, one UOSCs, and one MLA at each end of the span. See Figure 2-33 on page 2-46.

— uses amplifiers in the set-and-forget mode:

– For single CMD44 systems (1 wavelength to 44 wavelengths), MLA Pre-amp is set to 20 dB gain and the MLA Booster is set to 8 dB gain.

– For 50 GHz CMD44 systems (4 wavelengths to 88 wavelengths), MLA Pre-amp is set to 18 dB gain, MLA Booster is set to 10 dB gain, and CMDA Demux amplifier is set to 12.7 dB gain.

— the span loss should be equal to 32 dB for either configuration for both the NDSF fiber plus optional DSCMs. Padding should be used to ensure a total loss of 32 dB ± 1 dB.

— the CMD44 is completely passive, therefore all sources should be set or padded to 0 dBm ± 1dB to approximately equalize the system.

Figure 2-31Single span CMD44 point-to-point terminal - unamplified

Common Out

Common In

Common Out

Common In

44 C

hann

el M

UX

/DE

MU

X

44 C

hann

el M

UX

/DE

MU

X

Ch1 In

Ch1 Out

Ch2 In

Ch2 Out

Ch1 In

Ch1 Out

Ch2 In

Ch2 Out

Ch43 In

Ch43 Out

Ch43 In

Ch43 Out

Ch44 In

Ch44 Out

Ch44 In

Ch44 Out

CMD44 CMD44

LC

LC LC

LC

85

86

87

88

90

89

90

89

LC

1

2

3

4

LC

LC

LC

LC

LC1

2

3

4

85

86

87

88




Overview 2-45

Figure 2-32Single span CMD44 100 GHz point-to-point terminal - amplified

UO

SCP

EC

: NTT

839B

AO

SC

1O

SC

1 In

1 1

OS

C1

Out

OSC

2

Loc:

She

lf: S

lot:4

LC

UO

SC

PEC

: NTT

839B

A

OSC

1

OS

C1

In

11

OS

C1

Out

OSC

2

Loc:

She

lf: S

lot:4

LC

Line

A In

Line

A O

utA

Line

B O

utB

Line

B In

SC

SC

67

58

MLA

PE

C: N

TT83

0BA

Loc:

RR

100.

11 S

helf:

1 S

lot:2

Mon

itor 1

Mon

itor 2

LC 21

OS

C B

In

OS

C A

Out

3 4LC

Line

B In

Line

B O

utB

Line

A O

utA

Line

A In

SC

SC

85

76

MLA

PE

C: N

TT83

0BA

Loc:

100.

01 S

helf:

2 S

lot:2

Mon

itor 1

Mon

itor 2

LC

21

OS

C B

In

OS

C A

Out

3 4

LC

DS

CM

PE

C:

Loc:

Shelf

: FM

T:In

Out

SC

SC

2 dB

2 dB

DS

CM

PE

C:

Loc:

Shelf

: FMT

:In

Out

SC

SC

Com

mon

Out

Com

mon

In

44 Channel MUX/DEMUX

Ch1

In

Ch1

Out

Ch2

In

Ch2

Out

Ch4

3 In

Ch4

3 O

ut

Ch4

4 In

Ch4

4 O

ut

CM

D44

Gai

n =

8 d

B

Gai

n =

20

dB

Gai

n =

8 d

BG

ain

= 2

0 dB

LC

LC

LC85 86 87 88

90 89

LC

1 2 3 4

85 86 87 881 2 3 4

LC

Com

mon

Out

Com

mon

In


Ch1

In

Ch1

Out

Ch2

In

Ch2

Out

Ch4

3 In

Ch4

3 O

ut

Ch4

4 In

Ch4

4 O

ut

CM

D44

Spa

n lo

ss =

32

dB(a

ny c

ombi

natio

n of

ND

SF

fibe

r, D

SC

M &

pad

s)

LC

LC LCLCLC

90 89




2-46 Overview

Figure 2-33Single span CMD44 50 GHz point-to-point terminal - amplified

UO

SCP

EC

: NTT

839B

AO

SC

1O

SC

1 In

1 1

OS

C1

Out

OSC

2

Loc:

She

lf: S

lot:4

LC

UO

SC

OSC

1

OS

C1

In

11

OS

C1

Out

OSC

2

Loc:

She

lf: S

lot:4

LC

Line

A In

Line

A O

utA

Line

B O

utB

Line

B In

SC

SC

67

58

MLA

PE

C: N

TT83

0BA

Loc:

RR

100.

11 S

helf:

1 S

lot:2

Mon

itor 1

Mon

itor 2

LC 21

OS

C B

In

OS

C A

Out

3 4LC

Line

B In

Line

B O

utB

Line

A O

utA

Line

A In

SC

SC

85

76

MLA

She

lf:2

Slo

t:2

Mon

itor 1

Mon

itor 2

LC

21

OS

C B

In

OS

C A

Out

3 4

LC

DS

CM

PE

C:

Loc:

Shelf

: FM

T:In

Out

SC

SC

2 dB

2 dB

DS

CM

PE

C:

Loc:

Shelf

: FMT

:In

Out

SC

SC

Gai

n =

10

dB

Gai

n =

12.

7 dB

Gai

n =

18

dB

Gai

n =

10

dBG

ain

= 1

8 dB

Spa

n lo

ss =

32

dB

(any

com

bina

tion

of N

DS

F fi

ber,

DS

CM

& p

ads)G

ain

= 1

2.7

dB

Com

mon

Out

Com

mon

In


1C

h1 In

CM

D44

50

GH

z B

lue

Ch1

Out

2

90 89 90 89

3C

h2 In

Ch2

Out

4 85C

h43

In

Ch4

3 O

ut86 87

Ch4

4 In

Ch4

4 O

ut88 1 2 3 4 85 86 87 88

Com

mon

Out

Com

mon

In


Ch4

5In

CM

D44

50 G

Hz

Red

Ch4

5 O

ut

Ch4

6 In

Ch4

6 O

ut

Ch8

7 In

Ch8

7 O

ut

Ch8

8 In

Ch8

8 O

ut

CM

DA

∑∑

CM

D44

50

GH

z B

lue

Com

mon

Out

Com

mon

In


1C

h1 In

CM

D44

50 G

Hz

Red

Ch1

Out

2

9089

3C

h2 In

Ch2

Out

4 85C

h43

In

Ch4

3 O

ut86 87

Ch4

4 In

Ch4

4 O

ut88 1 2

9089

3 4 85 86 87 88

Com

mon

Out

Com

mon

In


Ch1

In

Ch1

Out

Ch2

In

Ch2

Out

Ch4

3 In

Ch4

3 O

ut

Ch4

4 In

Ch4

4 O

ut

CM

DA

∑ ∑




Overview 2-47

Cascaded LIM configurationsPrior to Release 3.2, cascaded LIMs were supported between the preamp and the WSS demux to provide a loss-less DSCM function. These SLAs were used in a set and forgot mode (no DOC control).

Attention: Cascaded LIMs were known as Interior SLAs prior to Release 4.0.

Since Release 3.2, Common Photonic Layer allows a cascaded LIM to be controlled by DOC allowing DOC to optimize the gain and achieve the optimum OSNR. Cascaded LIMs are supported at ROADM and GOADM sites only, see Figure 2-34 and Figure 2-35. Cascaded LIMs are not supported at TOADMs or line amplifiers.

Figure 2-34Cascaded LIM - ROADM site

WSS

1X

5

Switch1 In

Switch1 Out

1

2

Switch2 In

Switch2 Out

3

4

Switch3 In

Switch3 Out

5

6

Switch4 In

Switch4 Out

7

8

WSS

Shelf2, Slot3

Switch5 In

Switch5 Out

9

10

Common Out

Common In

12

11

Line B In B

Line A Out A Line A In 8

5

7

6

MLA

Shelf2, Slot2

Monitor 1

Monitor 22

1

OSCB In

OSCA Out

34

DSCMIn Out

Line B In


5

7

6

SLA

Cascaded LIM MLA or MLA2 only

Shelf2, Slot1

Monitor 1

Monitor 22

1

OSCB In

OSCA Out

34

UOSCOSC

1 OSC1 In

1

1

OSC1 Out

Shelf2, Slot4

OPMOPM

Monitor 2

12

Monitor 1

Monitor 4

34

Monitor 3

Shelf1, Slot13

Shelf2, FMT1

Line B Out Line B Out




2-48 Overview

Figure 2-35Cascaded LIM - GOADM site

For cascaded LIMs controlled by DOC, DOC adjusts the gain of the SLA to meet provisioned peak power targets.

Engineering guidelinesThe following are engineering guidelines associated with the cascaded LIM feature:

• For Release 4.0, the cascaded LIM parameter for the OTS identifies which slot the SLA is installed. The SLA is only controlled by DOC if this parameter is provisioned. This provides the option of leaving an SLA in the set and forget mode in existing networks.

• When upgrading to Release 4.0 from pre-Release 3.2, any cascaded LIMs remain in the set and forget mode until the Cascaded LIM parameter is provisioned. Refer to SLAT and Channel Procedures, 323-1661-221, for a procedure to change from the set and forget mode to a managed mode.

• After provisioning the Cascaded LIM parameter, adjacencies for the SLA are derived automatically. ADJ-<shelf>-<slot>-7 points to the WSS or GMD port the SLA is connected to. ADJ-<shelf>-<slot>-5 points to itself because this port is bypassed in the set up (see Figure 2-34 and Figure 2-35), but requires an adjacency for validation purposes.

Metro, regional, and long haul applicationsFigure 2-36 and Figure 2-37 outline the high-level architecture of the Common Photonic Layer for two typical application spaces although the flexibility of the architecture does not preclude other configurations from being deployed in various environments (edge, regional, and core) or even a mix of applications (combining both 100 GHz and 50 GHz signals in the same photonic domain–constrained by the use of different CMD groups).

Line B In B


5

7

6

MLA

Shelf2, Slot2

Monitor 1

Monitor 221

OSCB In

OSCA Out34

Line B In


5

7

6

SLA

Shelf2, Slot1

Shelf 2, Slot4

Monitor 1

Monitor 221

OSCB In

OSCA Out

34

Line B Out Line B Out

Cascaded LIM MLA or MLA2 only

Com Out

Com In

GR

OU

P M

UX

/ D

EM

UX

Group1 In

Group1 Out

1

2

Group2 In

Group2 Out

3

4

Group3 In

Group3 Out

5

6

Group4 In

Group4 Out

7

8

Group5 In

Group5 Out

9

10

Group6 In

Group6 Out

11

12

Group7 In

Group7 Out

13

14

Group8 In

Group8 Out

15

16

Group9 In

Group9 Out

17

18

23

22

OSC Out

OSC In

21

21

GMD Type 2

DSCMIn OutShelf2, FMT1




Overview 2-49

The hubbed ring topology shown in Figure 2-36 is a variation of a meshed ring architecture where the hub site has no glass-through connection (that is, all traffic is added or dropped from/to the service layer network element at that site). In a meshed ring, every site can be an OADM site.

Figure 2-36Edge hubbed ring application example

Lineinterface

Lineinterface

DWDMMux/Demux

DWDMTx/Rx

Lineinterface

Lineinterface

DWDMMux/Demux

DWDMMux/Demux

DWDMTx/Rx

DWDMTx/Rx

WSSWSS

Lineinterface

Lineinterface

DWDMTx/Rx

DWDMTx/Rx

DWDMTx/Rx

Lineinterface

Lineinterface

Hubnode site

OADM

ROADMOADM

LineAMPsite

LineAMPSite

DWDMMux/Demux

Terminal

Terminal

DWDMMux/Demux

DWDMMux/Demux

Note 1: In this application, the OADM can be a GMD based (GOADM), a WSS based OADM (ROADM) or it can be a thin OADM (TOADM).Note 2: The DWDM Mux/Demux can be one of the following:

• GMD + CMD4 or SCMD (GOADM)• SCMD4 (TOADM)

OADMOADM GOADM

or TOADM




2-50 Overview

Different application spaces require different sets of building blocks, with the maximum reach for any point-to-point traffic as a key factor in determining the complexity and number of building blocks required. Figure 2-37 illustrates the building blocks for a typical core application.

All sites including the Line Amplifier sites, require line interface functions, which always include OSC functions and OSC filters and often include optical amplifiers to overcome optical path losses.

Figure 2-37Core application example

Advanced optical controlThe Common Photonic Layer domain optical control (DOC) incorporates advanced optical control features to optimize traffic and maximize system performance and reach.

Lineinterface

Terminalsite

Terminalsite

LinearSpur

ROADMsite

Lineinterface

CDcomp

Lineinterface

Lineinterface

Lineinterface

CDcomp

CDcomp

CDcomp

DWDMTx/Rx

WSS WSS

DWDMMux/Demux

DWDMMux/Demux

DWDMTx/Rx

DWDMTx/Rx

DWDMMux/Demux

Lineinterface

CDcomp

DWDMTx/Rx

DWDMMux/Demux

LineAMPsite

LineAMPsite

LineAMPsite

LineAMPsite

LineAMPsite

LineAMPsite

Lineinterface

Lineinterface

Lineinterface

Lineinterface

CDcomp

CDcomp

DWDMMux/Demux

DWDMMux/Demux

DWDMMux/Demux

DWDMMux/Demux

WSS

Note 1: In this example, the OADM can be a GMD based OADM (GOADM), a WSS based OADM (ROADM) or it can be a thin OADM (TOADM).Note 2: The channel degrade compensation (CD comp) is not required at a eDCO site.




Overview 2-51

DOC prevents re-optimization when a DRA is not in normal operating mode (is in the APR or Shutoff mode)

Link budget analysis dictates the placement of back-to-back GMDs or WSSs and OPMs, for the purposes of a coarse or fine DGFF function used to optimize system performance.

DOC intelligence provides:

1 Peak power control

— EDFA gain set such that no wavelength exceeds a prescribed target

— limits non-linearities

2 Tilt control loop

— tilt is set on each amp

— minimizes accumulation of gain tilt and ripple across the link

— ensures the gain spectrum through cascaded EDFAs, DSCMs and the fiber plant is as flat as possible

3 WSS control loop

— maintains a per wavelength attenuation profile using data collected from amps upstream and downstream from it

There is no DOC or OPTMON support for point-to-point thin terminals with CMD44s. Wavelengths need to be manually optimized for this configuration.

Optical Power Monitoring (OPM) provides optimization algorithms with a more accurate view of the channel power profiles in the network, and allows data to be used efficiently, for data to be passed across sections, and for end of link OSNR to be estimated.

From a system perspective, the Common Photonic Layer peak power, tilt, and WSS control loops combine to

• limit non-linearities (that is, minimize the penalty attributable to non-linearities that result from self-phase modulation [SPM], cross-phase modulation [XPM], and four-wave mixing [FWM])

• control the gain tilt of the system (that is, preserve a wavelength’s optical signal-to-noise ratio [OSNR] by ensuring it is not overly attenuated through its propagation)

• equalize (that is, distribute finite available power such that all wavelengths are treated equitably [the equitability currency is either power or estimated OSNR])

Refer to “System description” chapter in Part 2 of this document for more information on the Common Photonic Layer advanced optical control.




2-52 Overview

DIA restorationThe introduction of Direction Independent Access (DIA) provides the ability to provide protection for individual wavelengths if an alternative protection path is available.

For Common Photonic Layer Release 4.0, the protection is provided at Layer 0 and is controlled by the Optical Manager Element Adapter (OMEA), see “System description” chapter in Part 2 of this document.

In Release 4.0, each wavelength to be protected is initially provisioned on the Common Photonic Layer and is routed in one direction from the DIA terminal. In OMEA, each protected wavelength is defined as photonically protected with a defined protection path.

If a failure occurs in the original path, OMEA identifies the wavelength as being failed with a potential restoration path. OMEA deletes the original wavelength path and adds the wavelength in the pre-defined protection path. Restoration is performed by the OMEA user by selecting Restore which changes the DIA routing to the pre-defined restoration path. Restoration requires that a valid communication path between the end points exists during the failure scenario.

Figure 2-38 shows the stages in the DIA restoration process.

For more information on the DIA restoration, refer to the Optical Manager Element Adapter documentation.




Overview 2-53

Figure 2-38DIA restoration




2-54 Overview

Raman applicationsThe Distributed Raman Amplifier (DRA) module provides a counter-propagating Raman amplifier solution that

• can minimize the impact of long, lossy spans in multi-span applications and reduces network regeneration when it is deployed on spans which are affecting the overall system reach and forcing regeneration points.

• can be used to ultra long reach applications for stretched spans.

The maximum span loss for Raman applications depends on the shutoff mode and the fiber type (see “DRA supported deployments” on page 2-56 for details).

Optical amplification based on stimulated fiber Raman gain was one of the earliest methods of optical amplification that was investigated. Raman amplification is made possible by a fiber nonlinear effect known as Stimulated Raman Scattering (SRS), which occurs when light waves interact with the vibrating molecules of an optical fiber. The molecules of the fiber absorb the pump light, then re-emit photons at roughly 13.2 THz downshifted frequency with energy equal to the original photon minus the molecular vibration of the fiber.

Distributed Raman amplification occurs when the transmission fiber is used as the gain medium. The power generated by the interaction of the pump light with the fiber medium amplifies the traffic-carrying signals. Therefore, the transmission fiber itself acts as the gain medium amplifying the traffic-carrying optical signals.

Since the transmission fiber itself is the gain medium, distributed Raman amplification does not require the insertion of a special gain medium, as is the case with the erbium-doped fiber of an EDFA. Unlike EDFAs, which provide discrete amplification, Raman amplification is distributed along the path of the optical signal since amplification occurs over a certain length of the entire transmission fiber, which is determined by the pump attenuation in the fiber and other fiber characteristics. See Figure 2-39 on page 2-55.

Raman amplifiers have several features that augment EDFAs and improve overall system performance. The preferred amplifier architecture is a hybrid EDFA-Raman amplifier platform that can exploit the benefits of both amplifier types. For instance:

• Greater signal reach-reducing costs associated with regenerator sites

Hybrid EDFA-Raman amplifier systems realize optical gain in the transmission fiber itself, so optical signals are amplified as they travel along the fiber. Raman amplification actually improves the optical signal-to-noise-ratio (OSNR) because the signal does not weaken between spans in a hybrid system to the extent it does in an EDFA-only




Overview 2-55

amplifier link. This reduced noise penalty is the reason why the optical signal can travel greater distances before requiring regeneration. Fewer regenerator sites means reduced costs associated with the purchase and maintenance of the hardware and software.

• Increased capacity, optimizing your equipment investment

Hybrid EDFA-Raman amplifier systems allow lower signal power at the EDFA transmitter side than EDFA-only systems to achieve the same reach as EDFA-only systems. The reduced signal power requirement at the EDFA transmitter side can be used to increase channel bit rate, or to combine more DWDM wavelengths into one fiber depending on the intended application. This potential to increase capacity enables optimization of hardware investment.

Figure 2-39Signal-to-noise ratio and nonlinear effects

DRA provides gain across the entire C-band spectrum and has the ability to flatten and/or adjust the gain profile across the entire spectrum. The DRA module is capable of 8 to 12 dB Raman gain depending on the application.

Amplifier

Raman pump

Transmission signalwithout Raman

Nonlinear effects

High noise

Distance

1 span

1 span

Sig

nal p

ower

(dB

)

Raman pump Raman pump

Amplifier Amplifier

Transmission signal withdistributed Raman amplification

SNR = Signal-to-noise ratio

Legend




2-56 Overview

DRA supported deploymentsDRA modules must be deployed in both directions of an optical link. DRA modules are always used in pairs, see Figure 2-40.

Figure 2-40Link with DRA pair

The DRA can be placed at any line amplifier or OADM site (ROADM, TOADM, GOADM). Use the DRA with any SLA, MLA, MLA2, or LIM amplifier module.

The DRA has line A and B input and output SC type connector interfaces. Therefore, line system splicing is not required for DRA deployment.

The DRA can be placed in any slot designated to support any equipment type and variant. Recommended shelf configurations are shown in Rack level shelf configurations on page 3-3. The DRA is a separate amplifier module so it can be replaced without changing the EDFA (LIM, SLA, MLA, or MLA2).

The DRA can be operated in two shutofff modes, local and managed, which determine the DRA shutoff mechanism (see “System description” chapter in Part 2 of this document).

The shutoff mode determines the possible span losses as follows:

• local mode (pre Release 3.2) - multi-span applications with span losses as detailed in “System description” chapter in Part 2 of this document (fiber type dependent)

• managed mode with internal OSC - multi-span applications with span losses is fiber dependent, see Table 2-3 on page 2-57

Line A In Line A OutA

Line B OutB

Line B In

SCSC6

7

5

8

MLAPEC: NTT830BA

Loc:RR100.11 Shelf:1 Slot:2

Monitor 1

Monitor 2

LC

2

1

OSC B In

OSC A Out

3

4

LC

Line B In Line B OutB

Line A OutA

Line A In

SCSC8

5

7

6

MLAPEC: NTT830BA

Loc:100.01 Shelf:2 Slot:2

Monitor 1

Monitor 2

LC

2

1

OSC B In

OSC A Out

3

4

LC

UOSC PEC: NTT839BA

OSC 1

OSC1 In

1

1

OSC 1 Out

Loc:100.01 Shelf:1 Slot:4

LCUOSC PEC: NTT839BA

OSC 1

OSC 1 In

1

1

OSC 1 Out

Loc:100.01 Shelf:2 Slot :4

LC

2 1B

DRAPEC: NTT831AAE5

43Line A InLine A Out

Line B In Line B Out

( Pump Out )A

1 2 3 4

DRA PEC: NTT831AAE5

21 B

4 3ALine A In Line A Out

Line B InLine B Out

(Pump Out )

1 2 3 4

Line A provides the amplification

Line B filters out any residual pump power from the upstream DRA




Overview 2-57

• managed mode with externally routed OSC - multi-span applications with span losses as detailed in is fiber dependent, see Table 2-3 on page 2-57

In this application, the OSC traffic must be routed externally, for example using the NGM GCC overhead channels or CPL ILAN routed using an OM5100/5200 channel. Due to the use of externally routed OSC, the ultra long reach application requires special procedures for initial channel turn-up and manual recovery, which are detailed in SLAT and Channel Procedures, 323-1661-221, and Fault Management - Alarm Clearing, 323-1661-543. In addition, it is recommended (but not essential) that the ultra long reach application is bookended by terminals to avoid issues with comms isolation.

Accurate fiber characterization is required for all ultra long reach links. Ultra long reach links must be analyzed by the Nortel OPNET team. If accurate fiber characterization is not available, the system design is based on worst case models.

Operational considerationsThe following should be considered when deploying DRA modules:

• Unless DRA pump provisioning is provided by Nortel Link Engineering (LE), users should leave the Raman Target Power at the maximum of +27 dBm (default) for all applications during SLAT. During SLAT the OSC Shutoff Threshold and Turn-On parameters must be provisioned based on information in the “System description” chapter in Part 2 of this document if the DRA is being used in the local shutoff mode.

• The DRA does not support adjacency and topology features.

• The managed mode is the default setting.

• The managed mode is the required mode when using the DOC Enhanced automation mode.

• The DRA does not provide a Shelf Wavelength Topology (SWT) port map.

Table 2-3DRA supported deployments - maximum span loss

Application Fiber type

PSC NDSF ELEAF

Multi-span applications with full OSC functionality and automatic recovery - DRA (see Note 1)

37.3 dB 37.0 dB 37.3 dB

Multi-span ultra long reach (stretched span) applications requiring alternative OSC routing and manual channel turn-up/recovery procedures (see Note 2)

44.2 dB 42.3 dB 45.0 dB

Note 1: The assumed fiber length for these estimates was 160 km for PSC and 140 km for NDSF and ELEAF.

Note 2: The assumed fiber length for these estimates was 210 km for all fiber types.




2-58 Overview

• The DRA does not support Auto-in-service (AINS) by Raman facility for safety reasons.

• Shelf Level Correlation (SLC) will not apply to DRA alarms.

• The CRS AID continues to have the LIM as the edge port of a channel, even when a DRA provisioned on the node.

• The DRA is not supported in the Channel Access Large with WSS fixed configuration because no free slots are available.

• An alarm is not raised when DRA pumps cannot achieve provisioned power ratio.

• Automated facility provisioning based on fiber type provisioning is not available.

• In the local mode (see “System description” chapter in Part 2 of this document), an OSC Input LOS Threshold triggers the LOS LED. However, no alarm is raised. Set the OSC Input LOS Threshold to the same value as OSC Shutoff Threshold.

• In the managed mode, the LOS LED is redundant and does not operate.

• Raman gain appears as a reduced span loss. A change in OSC span loss occurs when the DRA is on.

• The difference in OSC span loss calculation is an estimation of the Raman gain at 1510 nm. The signal gain will be slightly more.

• DOC prevents re-optimization when a DRA is not in normal operating mode (APR, Shutoff). You must provision the slot for the DRA using the DRA parameter for the appropriate OTS (which defines the direction) as DOC uses this information to determine which direction a DRA is associated with and only stop DOC optimization in one direction when a DRA fault occurs.

• A Common Photonic Layer system is engineered for a single wavelength (with growth to 88 wavelengths). DRA provisioning is not expected to change with channel capacity growth.

• Systems with externally routed data communications must be engineered such that management requests from the user are not transmitted over the externally routed OSC in normal operation. For more information, see “Data communications” chapter in Part 2 of this document.

• Systems with externally routed data communications must be engineered such that the externally routed data communications only go through one ultra long reach span

• Nortel recommends systems with externally routed data communications are set up such that the OME6500 or OM5100/5200 link closest to the extended span provides the external comms link.




Overview 2-59

• The Wayside Channel cannot be used on high loss spans where data communications are routed externally.

• Under certain conditions it is possible for a DOC path failure to go undetected for up to an hour. OAM comms can be operating normally, but if the ultra long reach span has a failure, the DOC path can be down and may not alarm for an hour. Note that alarms will still be raised against the ultra long reach span that has failed.

Common Photonic Layer Line Amplifiers in an OME6500 photonics network

Common Photonic Layer Line Amplifiers are supported in a network comprising OME6500 equipment. The Common Photonic Layer Line Amplifiers are supported in the following configurations:

• Common Photonic Layer Line Amplifiers only (see Figure 2-41)

• Mix of Common Photonic Layer Line Amplifiers and OME6500 Line Amplifiers (see Figure 2-42)

• Mix of Common Photonic Layer Line Amplifiers and OME6500 Line Amplifiers with Raman amplification between Common Photonic Layer Line Amplifiers site only (see Figure 2-43 on page 2-60). To deploy Raman at an OME6500 ROADM/TOADM site (see Figure 2-44 on page 2-60), you must deploy an additional Common Photonic Layer line-amp site with pads for an additional span (normally at SLA would be deployed for the OME6500 ROADM/TOADM and a LIM/MLA2 would be deployed for the Common Photonic Layer Line Amplifier).

Figure 2-41OME6500 ROADM/TOADM with Common Photonic Layer Line Amplifiers

Figure 2-42OME6500 ROADM/TOADM with mix of Common Photonic Layer and OME6500 Line Amplifiers

OME6500ROADM or

TOADM

OME6500ROADM or

TOADM

CommonPhotonic

LayerLine Amplifier

CommonPhotonic

LayerLine Amplifier

OME6500ROADM or

TOADM

OME6500ROADM or

TOADM

CommonPhotonic

LayerLine Amplifier

OME6500Line Amplifier




2-60 Overview

Figure 2-43OME6500 ROADM/TOADM with Common Photonic Layer Line Amplifiers with Raman

Figure 2-44OME6500 ROADM/TOADM with Common Photonic Layer Line Amplifiers with Raman

OME6500ROADM or

TOADM

OME6500ROADM or

TOADM

Raman Amplified

Span

CommonPhotonic

LayerLine Amplifierwith Raman

CommonPhotonic


OME6500ROADM or

TOADM

OME6500ROADM or

TOADM

Raman Amplified

Span

Colocated

Pad

CommonPhotonic


CommonPhotonic


OME6500Line Amplifier

Pad




Overview 2-61

Operational considerationsThe following should be considered when deploying Common Photonic Layer Line Amplifiers in OME6500 networks:

• Common Photonic Layer nodes must be at Release 4.0 or above, OME6500 nodes must be at Release 6.0 or above.

• Common Photonic Layer LIM, SLA, MLA, MLA2, and Raman amplifiers are supported on the OME6500 Line Amplifier Sites are:

Attention: If Raman amplifiers are required on a span, the span must start and finish with Common Photonic Layer amplifiers.

• Common Photonic Layer Line Amplifiers are not allowed at OME6500 ROADM sites.

• When using the Low Tx Power OSC SFP (NTK592NGE5) on the OME6500, span losses of 24.5 dB (measured at 1550 nm) are supported with a Common Photonic Layer at one end and an OME6500 at the other end.

• Data communication is supported between OME6500 sites if Common Photonic Layer Line Amplifier sites are located between the OME6500 sites.

— OME6500 Private IP GNE configurations are not supported but other OME6500 GNE configurations can be used to manage the Common Photonic Layer remote network elements.

— OME6500 TL1 Gateway does not support Common Photonic Layer remote network elements’

• If using Site Manager, a consolidated craft installation comprising both Common Photonic Layer and OME6500 components is required.

OSC link budgetsTable 2-4 details the OSC link budgets for OME6500 networks with Common Photonic Layer Line Amplifiers.




2-62 Overview

Engineering toolsOptical Modeler

Nortel Optical Modeler is a Windows-based design tool that automatically places Common Photonic Layer components in the network. This placement is based on site locations, fiber type and characteristics, inter-site distances, etc., to guarantee integrity of the signal transmission through to the end of life of the product.

Attention: Nortel Optical Modeler can be used to create Common Photonic Layer link designs. For applications that fall outside the scope of Optical Modeler or if you do not currently have Optical Modeler, contact your Nortel account representative to obtain a detailed custom link design.

Table 2-4Common Photonic Layer line-amplifiers in an OME6500 photonics network - OSC link budgets

Platform OSC Tx Type OSC Rx TypeCalculated Budget Max Span Compared to

Min Span Max Span CPL-CPL OME-OME

CPL GMD/DOSC/UOSC GMD/DOSC/UOSC 0.6 dB 34.8 dB

Not Applicable

OME6500 Short Short 0.0 dB 26.7 dB

Standard Standard 7.0 dB 31.2 dB

Premium Premium 7.0 dB 34.7 dB

Low Tx Power Low Tx Power 0.0 dB 31.5 dB

Inter-working(see

GMD/DOSC/UOSC

Short 0.0 dB 32.2 dB Worse Better

Standard 3.7 dB 31.7 dB Worse Better

Premium 3.7 dB 34.7 dB Better Same

Low Tx Power 0.0 dB 32.0 dB Worse Better

Short GMD/DOSC/UOSC

0.0 dB 29.1 dB Worse Better

Standard 0.0 dB 34.1 dB Worse Better

Premium 0.2 dB 34.8 dB Better Better

Low Tx Power 0.0 dB 24.5 dB Worse Worse

Note: 9 dB Common Photonic Layer OSC Tx padding is used in inter-working scenario with OME6500 low tx power OSC SFP. No padding is needed on the Common Photonic Layer OSC Tx interwork with other OME (short/standard/premium) OSC SFPs.




Overview 2-63

Optical PlannerNortel Optical Planner is a Windows-based capacity planning software tool that assists with wavelength generation, through service grooming, and leverages powerful automated algorithms to determine the cost-optimized routing and assignment of wavelengths within the flexible photonic layer. With its multi-period design capabilities, Optical Planner enables strategic “what-if” analysis for growth and optimization activities over a base infrastructure that can be imported from the EMS.

Optical Planner and Optical Modeler have a common look and feel to ease the learning curve for users of both tools.

Wavelength planThe Common Photonic Layer multiplexer/demultiplexer capability is intended to interoperate with a wide range of different DWDM transmitter/receiver options for both the edge and core application spaces. The C-band wavelength plans for the Common Photonic Layer can support up to 880 Gbit/s of 10G capacity or 3.5 Tbit/s of 40G capacity.

For edge or regional applications, the 100 GHz wavelength plan is shown in Figure 2-45 on page 2-63 and Figure 2-46 on page 2-64. Figure 2-47 on page 2-64 and Figure 2-48 on page 2-64 show the 50 GHz wavelength plans.

Attention: The Common Photonic Layer out-of-band OSC wavelength is 1510 nm, which is at the blue edge of the Common Photonic Layer Amplifier bandwidth.

For further wavelength plan details, see “Compatible wavelength plan” on page 3-27.

Figure 2-45100 GHz 36 wavelength plan (9 CMD4s or SCMD4s)

Group 1

OSC1510 nm

1530.334 nm(195.900 THz)

1564.678 nm(191.600 THz)

36-λ capacity with the CMD4/SCMD4 (100 GHz)

Group 2 Group 3 Group 4 Group 5 Group 6 Group 7 Group 8 Group 9




2-64 Overview

Figure 2-46100 GHz 44 wavelength plan (1 CMD44 100 GHz)

Figure 2-4750 GHz wavelength plan (SCMD8)

Figure 2-4850 GHz 88 wavelength plan (2 CMD44 50 GHz)

Group 1

OSC1510 nm

1530.334 nm(195.900 THz)

1564.678 nm(191.600 THz)

44-λ capacity with the CMD44 (100 GHz)


Group 1

OSC1510 nm

1530.334(195.90 THz)

1565.087 nm(191.550 THz)

72-λ capacity with the SCMD8 (50 GHz)


Group 1

OSC1510 nm

1530.334(195.90 THz)

1565.087 nm(191.550 THz)

88-λ capacity with the CMD44 (50 GHz)





Overview 2-65

CMD44 deployment rulesAs indicated in the previous section (Wavelength plan on page 2-63), the Common Photonic Layer can support up to 44 wavelengths when using CMD44 100 GHz modules and up to 88 wavelengths when using CMD44 50 GHz modules. The following deployment rules must be considered when deploying CMD44 50 GHz and 100 GHz modules:

• CMD44 50 GHz and CMD44 100 GHz in the same network

The 50 GHz spaced channels either side of the 100 GHz channels cannot be used. Provisioning of these 50 GHz spaced channels is not blocked and optimization will cause interference on the neighboring 100 GHz channel.

• TOADMs in the same network as CMD44 50 GHz and/or CMD44 100 GHz modules

The one (CMD44 100 GHz) or two (CMD44 50 GHz) skip wavelengths associated with groups dropped at the TOADM cannot be used. In addition, for CMD 50 GHz modules the last channel in the previous group also cannot be used.

• GMDs (including GOADMs) in the same network as CMD44 50 GHz and/or CMD44 100 GHz modules

All 8 (CMD44 100 GHz) or 16 (CMD44 50 GHz) skip wavelengths cannot be used.

• SCMD4/SCMD8 modules cannot be cascaded with CMD44s (they are supported on a different WSS port). SCMD8s are not supported with CMD44 100 GHz modules.

• CMD44s are supported on single span CMD44 Thin terminal (see Single span CMD44 point-to-point terminal on page 2-43).

• The channels must originate and terminate on a CMD of the same channel spacing (for example, CMD44 100 GHz to CMD4 is allowed, CMD44 100 GHz to CMD8 is not allowed).

Provisioning of skip channels on CMD44s in a TOADM, GOADM, or group-based DGFF node is not prevented by the software. The use of skip channels in networks with GOADM or group-based DGFF is not permitted, and may cause instability and/or DOC to cease to function. If provisioned in TOADM networks, these skip channels pass through a TOADM in some limited configurations. Otherwise, the channel is lost at the node. SCMDs have a band-pass filter that filters and drops the channels for the corresponding CMD group. The rest of the channels are passed to the upgrade port. The band-pass filter partially filters out the skip channels that are just below or just above the optical spectrum of the group being dropped. In this case, the skip channels partially pass through a TOADM and any attempt to add the channels with DOC causes a traffic impact on existing




2-66 Overview

in-service channels. In the case where the skip channels that are not adjacent to the groups being dropped at the TOADM, the channels pass through without any filtering.

If a duplicate channel exists on a SCMD4/SCMD8 and CMD44, the SCMD4/SCMD8 channel has precedence over the CMD44 channel. Manual and auto-provisioning of a SCMD4/SCMD8 is not permitted if shared (overlapping) wavelengths are already provisioned and in-service on a CMD44. Similarly, provisioning a channel on a CMD44 is blocked if any of the channels in the associated group is provisioned on an existing SCMD4/SCMD8 on the shelf. An Auto-provisioning Mismatch alarm is raised if auto-provisioning of a (s)CMD4/8 is blocked due to in-service wavelengths on a CMD44.

For 50 GHz networks, use Table 2-5 on page 2-66, Table 2-6 on page 2-67, Table 2-7 on page 2-67, and Table 2-8 on page 2-67 to determine which 50 GHz channels are not allowed by:

• listing the channels which you believe you should have based on the CMDs used in the network

• using the tables to determine if any of those channels are not allowed.

Table 2-5Unavailable 50 GHz channels - CMD44 combinations

CMD44 combination Unavailable channels

CMD44 100 GHz only 2, 4, 6, .... 88(total of 44)

Plus any additional channels that are blocked due to the inclusion of (S)CMD4, sCMD8, GMDs (see Table 2-6, Table 2-7, and Table 2-8).

Channel numbering refers to the 50 GHz grid, see Table 3-5 on page 3-30.

CMD44 100 GHz and CMD44 50 GHz Blue

44 and 46, 48, 50, .... 88 (total of 23)

CMD44 100 GHz and CMD44 50 GHz Red

2, 4, 6, .... 44(total of 22)

CMD44 50 GHz Blue and CMD44 50 GHz Red

none




Overview 2-67

Table 2-6Unavailable 50 GHz channels - sCMD4s

(s)CMD4 group Unavailable channels

1 2, 4, 6, 8

2 10, 12, 14, 16, 18

3 20, 22, 24, 26, 28

4 30, 32, 34, 36, 38

5 40, 42, 44, 46, 48

6 50, 52, 54, 56, 58

7 60, 62, 64, 66, 68

8 70, 72, 74, 76, 78

9 80, 82, 84, 86, 88

Table 2-7Unavailable 50 GHz channels - TOADMs

TOADM group Unavailable channels

1 9, 10

2 10, 19, 20

3 20, 29, 30

4 30, 39, 40

5 40, 49, 50

6 50, 59, 60

7 60, 69, 70

8 70, 79, 80

9 80

Note: GMDs/GOADMs block the skip channels of all groups.

Table 2-8Unavailable 50 GHz channels - GMDs/GOADMs

GMDs Unavailable channels

GMDs/GOADMs block the skip channels of all groups which are 9, 10, 19, 20, 29, 30, 39, 40, 49, 50, 59, 60, 69, 70, 79, and 80




2-68 Overview

Supported CMD44 to WSS configurationsThe following are the supported CMD44 OADM configurations:

• CMD44 100 GHz connected directly to WSS (see Figure 2-49 for CMD44 100 GHz). If CMD44 100 GHz is deployed, the whole C-band is designated 100 GHz.

• CMD44 100 GHz connected to WSS using a CMDA (see Figure 2-50 for CMD44 100 GHz with CMDA). If CMD44 100 GHz is deployed, the whole C-band is designated 100 GHz.

• CMD44 50 GHz Blue and Red connected directly to WSS (see Figure 2-51). Either both the CMD44 50 GHz Red and Blue, only the CMD44 50 GHz Red, or only the CMD44 50 GHz Blue can be deployed (although deploying only the CMD44 50 GHz Blue does not follow normal deployment rules).

• CMD44 50 GHz Blue and Red connected to WSS using a CMDA or BMD2 (see Figure 2-52 for example connected using a CMDA and Figure 2-53 for example connected using a BMD2). Either both the CMD44 50 GHz Red and Blue, only the CMD44 50 GHz Red, or only the CMD44 50 GHz Blue can be deployed (although deploying only the CMD44 50 GHz Blue does not follow normal deployment rules).

For supported CMD44 to LIM configurations in DIA terminals, see Direction Independent Access (DIA) on page 2-21.

Figure 2-49CMD44 100 GHz without a CMDA

WSS

OutSwitch 1

Switch 2

Switch 3

CommonOut

CommonIn

Switch 4

Switch 5

In

OutIn

OutIn

OutIn

OutIn

11

12

1

3

5

7

9Common Out

Common In

44 C

hann

el M

UX

/DE

MU

X

1 Ch1 In CMD44100 GHz

Ch1 Out2

90

89

3 Ch2 In

Ch2 Out4

85 Ch43 In

Ch43 Out86

87 Ch44 In

Ch44 Out88

2

4

6

8

10




Overview 2-69

Figure 2-50CMD44 100 GHz with a CMDA

Figure 2-51CMD44 50 GHz without a CMDA

WSS

OutSwitch 1

Switch 2

Switch 3

CommonOut

CommonIn

Switch 4

Switch 5

In

OutIn

OutIn

OutIn

OutIn

11

12

1

3

3

5

7

9

Common Out

Common In

44 C

hann

el M

UX

/DE

MU

X1 Ch1 In CMD44

100 GHzCh1 Out

2

90

89

3 Ch2 In

Ch2 Out4

85 Ch43 In

Ch43 Out86

87 Ch44 In

Ch44 Out88

2

1

4

6

8

10

CMDA

∑

∑

2

4

6

5

WSS

OutSwitch 1

Switch 2

Switch 3

CommonOut

CommonIn

Switch 4

Switch 5

In

OutIn

OutIn

OutIn

OutIn

11

12

1

3

5

7

9

Common Out

Common In

44 C

hann

el M

UX

/DE

MU

X

1 Ch1 In CMD4450 GHz Blue

Ch1 Out2

90

89

3 Ch2 In

Ch2 Out4

85 Ch43 In

Ch43 Out86

87 Ch44 In

Ch44 Out88

1

2

90

89

3

4

85

86

87

88

Common Out

Common In

44 C

hann

el M

UX

/DE

MU

X

Ch45 In CMD4450 GHz Red

Ch45 Out

Ch46 In

Ch46 Out

Ch87 In

Ch87 Out

Ch88 In

Ch88 Out

2

4

6

8

10




2-70 Overview

Figure 2-52CMD44 50 GHz with a CMDA

Figure 2-53CMD44 50 GHz with a BMD2

WSS

OutSwitch 1

Switch 2

Switch 3

CommonOut

CommonIn

Switch 4

Switch 5

In

OutIn

OutIn

OutIn

OutIn

11

12

1

3

5

7

9

Common Out

Common In

44 C

hann

el M

UX

/DE

MU

X


Ch1 Out2

90

89

3 Ch2 In

Ch2 Out4

85 Ch43 In

Ch43 Out86

87 Ch44 In

Ch44 Out88

1

2

90

89

3

4

85

86

87

88

Common Out

Common In

44 C

hann

el M

UX

/DE

MU

X


Ch45 Out

Ch46 In

Ch46 Out

Ch87 In

Ch87 Out

Ch88 In

Ch88 Out

2

4

6

8

10

3

1

CMDA

∑

∑

2

4

6

5

WSS

OutSwitch 1

Switch 2

Switch 3

CommonOut

CommonIn

Switch 4

Switch 5

In

OutIn

OutIn

OutIn

OutIn

11

12

1

3

5

7

9

Common Out

Common In

44 C

hann

el M

UX

/DE

MU

X


Ch1 Out2

90

89

3 Ch2 In

Ch2 Out4

85 Ch43 In

Ch43 Out86

87 Ch44 In

Ch44 Out88

1

2

90

89

3

4

85

86

87

88

Common Out

Common In

44 C

hann

el M

UX

/DE

MU

X


Ch45 Out

Ch46 In

Ch46 Out

Ch87 In

Ch87 Out

Ch88 In

Ch88 Out

2

4

6

8

10

Input 1

Output 1

Output 2

CommonOut

CommonIn

Input 2

BMD2

∑2

1




Overview 2-71

Supported network configurations100 GHz CMD44 networksThe following 100 GHz example networks using CMD44 100 GHz modules are supported:

• all ROADM 100 GHz (Figure 2-54 on page 2-71) - supports the full 44 100 GHz wavelengths.

• ROADM 100 GHz with SCMD4 spurs (Figure 2-55 on page 2-71) - supports the full 44 100 GHz wavelengths.

• ROADM 100 GHz with SCMD4 TOADM (Figure 2-56 on page 2-72) - network capacity is reduced by one wavelength (skip channel) for each SCMD4 group deployed at the TOADM.

Figure 2-54100 GHz ROADM network

Figure 2-55100 GHz ROADM with SCMD4 network

100100

CMD44

CMD44

100100

CM

D44 C

MD

44

CM

D44

100100

CM

D44

CM

D44

100

CM

D44CMD44

CMD44

100

100

100

100100

CMD44

CMD44

100

100

CM

D44 C

MD

44

100100

CM

D44

CM

D44

CMD44sCMD

sCMD100

100




2-72 Overview

Figure 2-56100 GHz ROADM with SCMD4 TOADM network

50 GHz CMD44 networksThe following 50 GHz example networks using CMD44 50 GHz modules are supported:

• all ROADM 50 GHz (Figure 2-57 on page 2-73) - supports the full 88 50 GHz wavelengths.

• ROADM 50 GHz with SCMD8 spurs (Figure 2-58 on page 2-73) - supports the full 88 50 GHz wavelengths.

• ROADM 50 GHz with SCMD4 spurs (Figure 2-59 on page 2-74) - network capacity is reduced by five wavelengths (five 50 GHz channels due to 100 GHz limitation) for each SCMD4 group deployed at the ROADM.

• ROADM 50 GHz with SCMD8 TOADM (Figure 2-60 on page 2-74) - network capacity is reduced by three wavelengths (skip channels) for each SCMD8 group deployed at the TOADM (see Table 2-7 on page 2-67).

• ROADM 50 GHz with SCMD4 TOADM (Figure 2-61 on page 2-75) - network capacity is reduced by seven wavelengths (five 50 GHz channels due to 100 GHz limitation and two skip channels) for each SCMD4 group deployed at the TOADM.

• ROADM 50 GHz with GOADM (Figure 2-62 on page 2-75) - network capacity is reduced by 16 wavelengths (skip channels).

100100

CMD44

CMD44

100

100

CM

D44 C

MD

44

100100

CM

D44

CM

D44

sCM

DsC

MD




Overview 2-73

Figure 2-5750 GHz ROADM network

Figure 2-5850 GHz ROADM with SCMD8 spurs network

Each side of the ROADM could beany of the allowed configurationssubject to the overall deploymentrules.

505050

CM

D44

CM

D44

CM

D44

50 5050

CM

D44

CM

D44

CM

D44

50

5050

CMD44 CMD44

CMD44 CMD44

CM

D44

CM

D44

50

5050

CMD44CMD44

CMD44CMD44


505050

CM

D44

CM

D44

CM

D44

50 5050

CM

D44

CM

D44

CM

D44

50

5050

CMD44 CMD44

CMD44 CMD44

CM

D44

CM

D44

50

5050

CMD44CMD44

CMD44CMD44

sCM

D8sC

MD

8sCM

D8




2-74 Overview

Figure 2-5950 GHz ROADM with SCMD4 spurs network



505050

CM

D44

CM

D44

CM

D44

50 5050

CM

D44

CM

D44

CM

D44

50

5050

CMD44 CMD44

CMD44 CMD44

CM

D44

CM

D44

50

5050

CMD44CMD44

CMD44CMD44

sCM

D4sC

MD

4sCM

D4


505050

CM

D44

CM

D44

CM

D44

50 5050

CM

D44

CM

D44

CM

D44

50

5050

CMD44 CMD44

CMD44 CMD44

CM

D44

CM

D44

sCM

D8

sCM

D8




Overview 2-75


Figure 2-6250 GHz ROADM with ROADM network


505050

CM

D44

CM

D44

CM

D44

50 5050

CM

D44

CM

D44

CM

D44

50

5050

CMD44 CMD44

CMD44 CMD44

CM

D44

CM

D44

sCM

D4

sCM

D4


505050

CM

D44

CM

D44

CM

D44

50 5050

CM

D44

CM

D44

CM

D44

50

5050

CMD44 CMD44

CMD44 CMD44

CM

D44

sCM

D8

GMD

GMD

CM

D44

sCM

D8




2-76 Overview

Channel capacity increase optionsFor networks where CMD44 100 GHz modules are already deployed, a number of options available for increasing the channel capacity to greater then 44 wavelengths when deploying CMD44 50 GHz modules. The possible options are summarized in Figure 2-63.

The following should be considered:

• For the initial configuration, only the red half (channels 23 to 44) of the CMD44 100 GHz wavelengths should be deployed. If any of the blue half (channels 1 to 22) of the CMD44 100 GHz wavelengths are deployed, it prevents the CMD44 50 GHz Blue from being added in the future.

• When adding the CMD44 50 GHz Blue to increase capacity, depending on the required end capacity, either just the CMD44 50 GHz channels can be used (maximum channel capacity of 65) or the CMD44 100 GHz channels can be rolled over (maximum channel capacity of 88). Roll-over of channels is an out-of-service traffic-affecting operation.

Figure 2-63CMD44 channel capacity increase options

100G

Hz

Capacity = 22 lambda

AddCMD4450GHzBlue(halffilled)

ReplaceCMD44100GHz

withCMD4450GHz

Red

FillCMD4450GHzBlueStart with 100GHz in Release 3.1

Fill 22 red channels 45 to 87 only

50

100G

Hz

50G

Hz

50

100G

Hz

Capacity = 44 lambda Capacity = 44 lambda Capacity = 88 lambda

Capacity = 44 lambda Capacity = 65 lambda

Fill remaining channels Roll over 100GHz channels toBlue CMD 44 50GHz

No further upgrade possible


The CMDA is optional


5010

0GH

z50

GH

z

50

50G

Hz

50G

Hz

50

100G

Hz

50G

Hz

50




Overview 2-77

Interworking with Nortel portfolio and with other vendor’s equipmentCommon Photonic Layer carries DWDM wavelengths from either Nortel or third party suppliers. Common Photonic Layer interworks with:

• Optical Multiservice Edge 6500 BB (OME NGM)

• Optical Multiservice Edge 6500 (OME6500)

• Optical Cross Connect HDXc

• Optical DWDM Terminal (DT)

• Optical Long Haul 1600 (LH)

• Optical Cross Connect DX (DX)

• Optical Metro 5100/5200 (OM5K)

• Common Photonic Layer

• Other vendors

For transmitters and receivers supported by Common Photonic Layer, see Table 2-9. Refer to the Optical Modeler User Guide to determine which of these transmitter types is supported by the Optical Modeler link engineering tool.

Attention: Nortel recommends that all Common Photonic Layer network designs are validated with Optical Modeler or custom engineered by Nortel. For more information, see Engineering tools on page 2-62.

Table 2-9Supported transmitters and receivers for Common Photonic Layer

Product Transmitter/receiver type (PEC) Default modulation class

Optical Multiservice Edge 6500 BB(OME NGM)

OME NGM (eDCO) WT 1xOC192/STM64 1x10.7G (NTK530AA)

OME NGM (eDCO) WT 1xOC-192/STM-64 1x10.7G EXT PWR (NTK530AA)

OME NGM (eDCO) WT 1xOC-192/STM-64 1x10.7G Regional (NTK530BA)

OME NGM (eDCO) WT 1xOC-192/STM-64 1x10.7G Regional EXT PWR (NTK530BA)

OME NGM (eDCO) WT 1x10GE LAN 1x11.1G (NTK530AB)

OME NGM (eDCO) WT 1x10GE LAN 1x11.1G EXT PWR (NTK530AB)

OME NGM (eDCO) WT 1x10GE LAN 1x11.1G Regional (NTK530BB)

OME NGM (eDCO) WT 1x10GE LAN 1x11.1G Regional EXT PWR (NTK530BB)

OME NGM (eDCO) WT 1xOTU2 1x10.7G (NTK530AC)

OME NGM (eDCO) WT 1xOTU2 1x10.7G EXT PWR (NTK530AC)

10G NGM

10G NGM

10G NGM

10G NGM

10G NGM

10G NGM

10G NGM

10G NGM

10G NGM

10G NGM




2-78 Overview

Optical Multiservice Edge 6500 BB(OME NGM)(continued)

OME NGM (eDCO) WT 1xOTU2 1x10.7G Regional (NTK530BC)

OME NGM (eDCO) WT 1xOTU2 1x10.7G Regional EXT PWR (NTK530BC)

OME eDC40G OCLD 1xOTU3+ DWDM Enhanced PMD Comp (NTK539PA)

OME eDC40G OCLD 1xOTU3+ DWDM (NTK539PB)

OME eDC40G OCLD 1xOTU3+ DWDM Regional (NTK539PC)

OME eDC40G OCLD 1xOTU3+ DWDM Metro (NTK539PD)

eDC40G OCLD 1xOTU3+ DWDM Submarine

100 Gbs Transmitter

OME OTSC Tunable 1xOTU2 1x10.7G RS8 FEC (NTK528AA)

OME OTSC Tunable 1xOTU2 1x10.7G SCFEC (NTK528AA)

OME OTSC Tunable FC1200 11.3G RS8 FEC (NTK528AA)

OME OTSC Tunable FC1200 11.3G SCFEC (NTK528AA)

OMENGMWT10GbE11G1EXT

NGM WT 1x10GE LAN 1x11.1G Submarine

NGM WT 1xOC192/STM64 and OTU 1x10.7G Submarine

10G NGM

10G NGM

40G

40G

40G

40G

40G

100G

10G

10G

10G

10G

10G

10G

10G

Optical Multiservice Edge 6500(OME6500)

OME DWDM 2xOC-48/STM-16 STS/HO VT/LO DPO (DPO Modules: NTK580xx; Carriers: 2xSTS1/HO Carrier: NTK519BA; 2xVT1.5/LO Carrier: NTK520BA)

OME DWDM 2xOC-48/STM-16 STS/HO VT/LO SFP (SFP Modules: NTK585xx; Carriers: 2xSTS1/HO Carrier: NTK516BA; 2xVT1.5/LO Carrier NTK517BA)

OME DWDM 1xOC-192/STM64 G.709 STS/HO VT/LO(STS1/HO: NTK526[K-N]x; VT1.5/LO: NTK527[K-N]x)

OME DWDM 1xOC-192/STM64 G.709 HO/LO TUNABLE AM1 AM2 RS8 FEC (HO: NTK526JA; LO: NTK527JA)

OME DWDM 1xOC-192/STM64 G.709 HO/LO TUNABLE AM1 AM2 SCFEC (HO: NTK526JA; LO: NTK527JA)

OME SuperMux 10G DWDM Tunable 10.7G RS8 FEC (NTK535EA)

OME SuperMux 10G DWDM Tunable 10.7G SCFEC (NTK535EA)

OME DWDM Tunable OTR 1xOC192/STM64 1x10G RS8 FEC (NTK530MA)

OME DWDM Tunable OTR 1xOC192/STM64 1x10.7G SCFEC (NTK530MA)

OME DWDM Tunable OTR 1x10GE LAN 11.1G RS8 FEC (NTK530MA)

OME DWDM Tunable OTR 1x10GE LAN 11.1G SCFEC (NTK530MA)

OME DWDM Tunable OTSC 1xOC192/STM64 1x10.7G RS8 FEC (NTK528AA)

OME DWDM Tunable OTSC 1xOC192/STM64 1x10.7G SCFEC (NTK528AA)

OME DWDM Tunable OTSC 1x10GE LAN 11.1G RS8 FEC (NTK528AA)

OME DWDM Tunable OTSC 1x10GE LAN 11.1G SCFEC (NTK528AA)

2.5G

2.5G

10G

10G

10G

10G

10G

10G

10G

10G

10G

10G

10G

10G

10G

Optical Metro 3500(OM3500)

OM3500 10G (NTN445xx)

OM3500 2.5G (NTN442xx)

10G

2.5G

Optical Cross Connect HDXc

HDX (_C) 4 X 10G DWDM TR Pluggable Tunable

HDX (_C) 4 X 10G DWDM TR (Optical Modules: NTUC32[B-Z][P-Q; Quad Carrier: NTUC32AA)

10G

10G

Optical DWDM Terminal(DT)

DT Single combiner (10G)

DT Dual 10G WT (Line Side)

DT Dual Regen

10G

10G

10G

Table 2-9 (continued)Supported transmitters and receivers for Common Photonic Layer





Overview 2-79

Optical Long Haul 1600(LH)

LH 1600T 10G WT with TriFEC (NTCF07xx)

LH 1600T DWDM OC-48 trib (NTCA30xx)

LH 1600T 10 G WT (w/SFEC) (NTCF07xx)

10G

2.5G

10G

Optical Cross Connect DX(DX)

DX 10G (w/SFEC) (NTCF06[B-Z][P-Q])

DX 10G w/TriFEC (NTCF06[B-Z][P-Q])

10G

10G

Optical Metro 5100/5200(OM5K)

OM5K OCLD 2.5G Flex (NT0H80xx)

OM5K OTR 2.5G Flex 850nm/1310nm (850nm Client: NT0H82x; 1310nm Client: NT0H81xx)

OM5K OTR 10G Enhanced (CPL) (NT0H83[A-J][A-D])

OM5K OTR 10G Enhanced (CPL) 10GbE 11.1G (NT0H83[A-J][A-D])

OM5K OTR 10G Ultra 10.7G RS8 (NT0H85xx)

OM5K OTR 10G Ultra 10.7G SCFEC (NT0H85xx)

OM5K OTR 10G Ultra 10GbE 11.1G (NT0H85xx)

OM5K OTR 10G Ultra FC1200 11.3G (NT0H85xx)

OM5K OTR 10G Enhanced Tunable 10.7G (NT0H83AZ)

OM5K OTR 10GBE Tunable 10.7G (NT0H83AZ)

OM5K OTR 4G FC400(SFPs: NTK586xx; Card: NT0H08AA)

OM5K MOTR 10G GbE/FC (NT0H84[A-J][A-D]; w/VCAT: NT0H84[A-J][E-H])

OM5K MOTR 10G GbE Extended Reach 10.7G RS8 (NT0H86xx)

OM5K MOTR 10G Tunable GbE 10.7G RS8 (NT0H84AZ)

OM5K MOTR OTN 4xOC48/OTU1 Tunable 10.7G RS8 (NT0H87AZ)

OM5K MOTR OTN 4xOC48/OTU1 Tunable 10.7G SCFEC (NT0H87AZ)

OM5K MOTR 2.5G FC/GbE EFM (SFPs: NTK586xx; Card: NT0H08AA)

2.5G

2.5G

10G

10G

10G

10G

10G

10G

10G

10G

2.5G

10G

10G

10G

10G

10G

2.5G

Common Photonic Layer

Note: These entries are used to define spur connections.

SCMD4-connection to/from a CMD4 or SCMD4

SCMD8-connection to/from a SCMD8

Undefined

Other vendors

Foreign (other vendor supplied Tx/Rx) Custom

Note: The min/max/nominal power levels that are auto-populated when selecting any Tx type (except foreign) are based on link engineering requirements for Common Photonic Layer DWDM photonic layer applications. No manual editing of parameters is required unless explicitly specified by the Nortel Link Engineering Team or EDP. A known exception to this guideline is that the nominal power values for (s)CMD4 and SCMD8 must be provisioned manually based on EDP MOPs.

Table 2-9 (continued)Supported transmitters and receivers for Common Photonic Layer





2-80 Overview

Mixing different types of transmitters and receiversDOC control points optimize the optical bandwidth on a per wavelength and per channel basis. Control or system optimization is independent of any proprietary modulation scheme.

A combination of different types of Tx and Rx including foreign wavelengths are possible, where the limitation is imposed by the system budget.

To make such an open system possible, each type of transmitter and receiver are characterized by a series of parameters. A key parameter is the Rx nominal power which defines the optimal operating point of the receiver.

During system optimization, the power level presented to the different receivers is adjusted by the VOA on the common input port of the CMD4s or the EDFA on the common input port of the SCMD8s. On each (S)CMD4 or SCMD8, the VOA or EDFA on the common input port is adjusted so that the power present at the different channel output ports is as close as possible to the nominal power of the different receivers.

The CMD44 has no VOAs, optimization is carried out through the WSS and CMDA (if applicable).

Connecting different types of receivers to the same CMDConnecting any mixture of optical systems to the same CMD may require specialized link budget and equipping rules. Mixed-wavelength CMD applications should be validated with Nortel prior to deployment.

When different types of receivers are connected to the same CMD, the VOA or EDFA on the common input port will be adjusted to achieve an acceptable compromise among the different receivers. Some receivers will see a power level above their nominal value but lower than the saturation level while some other receivers will see a power level below the nominal power but above their sensitivity.

In some cases, such a compromise is impossible to achieve. As an example, if receivers of type A with a nominal power of -9 dBm and a sensitivity of -12 dBm are mixed on the same CMD with type B of receivers with a nominal power of -20 dBm and an overload level of -15 dBm, there is no acceptable compromise. When faced with this situation, the solution involves increasing the nominal, overload and sensitivity power on the type B receivers by 10 dB while adding a 10 dB pad in front of these receivers. In most if not all metropolitan or long-haul only applications, these considerations become relevant only when mixing wavelengths modulated at different line rate and using different receiver technologies.




Overview 2-81

To avoid padding the receivers and changing their characteristics and to achieve a better compromise on the Rx power level, one can choose to put receivers with similar nominal power on the same CMD (same group). In general, this is equivalent to organizing the optical bandwidth in groups dedicated to different application space (that is groups used for edge and regional applications and other groups covering the long-haul space).

Filtered SCMD8 modules only support the 50 GHz OME6500 Broadband eDCO 10G wavelengths only, but a mixture of eDCO and non-eDCO wavelengths can be routed through the GMD and WSS modules.

A mix of 100 GHz Common Photonic Layer-compliant Optical Metro 5100/5200 2.5G and 10G sources are supported on a Common Photonic Layer Open SCMD8. Optical Metro 5100/5200 2.5G tunable circuit packs can be tuned to 50 GHz CPL-compliant channels supported by the Open SCMD8 (NTT861BA-BJ).

To assist customers in using foreign wavelengths with the Common Photonic Layer, Nortel offers foreign source characterization services, path validation services for characterized sources, and turn-up services (provisioning and test) for foreign wavelengths. Nortel highly recommends the use of these services before adding foreign wavelengths to guarantee the performance of the network.

The minimum transmitter and receiver specifications that must be provided for foreign wavelength characterization are identified in Table 2-10.

Table 2-10Minimum transmitter / receiver specifications required for foreign wavelength characterization

Transmitter Parameter Receiver Parameter

OSNR bias Sensitivity threshold

Line rate Overload threshold

FEC gain Damage threshold

Minimum launch power Maximum positive transient

Maximum launch power Minimum negative transient

Tx wavelength




2-82 Overview

Transmitter and CMD compatibilityTable 2-11 provides the compatibility of CPL CMDs (CMD4, CMD44, SCMD4, SCMD8-Filtered, and SCMD8-Open) and the transmitters supported on other Nortel product lines.

Table 2-11Nortel Tx and CMD compatibility

Nortel Product Line

Nortel Circuit Pack Description CMD compatibility

CMD4 CMD44 SCMD4 SCMD- Open(Note 1)

SCMD8-Filtered

Optical Metro 5100/5200

OM5K OCLD 2.5G Flex yes yes yes yes no

OM5K OTR 2.5G Flex 850nm/1310nm yes yes yes yes no

OM5K OTR 10G Enhanced (CPL) yes yes yes yes no

OM5K OTR 10G Enhanced (CPL) 10GbE 11.1G yes yes yes yes no

OM5K OTR 10G Ultra 10.7G RS8 yes yes yes yes no

OM5K OTR 10G Ultra 10.7G SCFEC yes yes yes yes no

OM5K OTR 10G Ultra 10GbE 11.1G yes yes yes yes no

OM5K OTR 10G Ultra FC1200 11.3G yes yes yes yes no

OM5K OTR 10G Enhanced Tunable 10.7G yes yes yes yes no

OM5K OTR 10GBE Tunable 10.7G yes yes yes yes no

OM5K OTR 4G FC400 yes yes yes yes no

OM5K MOTR 10G GbE/FC yes yes yes yes no

OM5K MOTR 10G GbE Extended Reach 10.7G RS8 yes yes yes yes no

OM5K MOTR 10G Tunable GbE 10.7G RS8 yes yes yes yes no

OM5K MOTR OTN 4xOC48/OTU1 Tunable 10.7G RS8 yes yes yes yes no

OM5K MOTR OTN 4xOC48/OTU1 Tunable 10.7G SCFEC yes yes yes yes no

OM5K MOTR 2.5G FC/GbE EFM yes yes yes yes no




Overview 2-83

OME6500

OME NGM (eDCO) WT 1xOC192/STM64 1x10.7G yes yes yes yes yes

OME NGM (eDCO) WT 1xOC-192/STM-64 1x10.7G EXT PWR yes yes yes yes yes

OME NGM (eDCO) WT 1xOC-192/STM-64 1x10.7G RR yes yes yes yes yes

OME NGM (eDCO) WT 1xOC-192/STM-64 1x10.7G RR EXT PWR yes yes yes yes yes

OME NGM (eDCO) WT 1x10GE LAN 1x11.1G yes yes yes yes yes

OME NGM (eDCO) WT 1x10GE LAN 1x11.1G EXT PWR yes yes yes yes yes

OME NGM (eDCO) WT 1x10GE LAN 1x11.1G RR yes yes yes yes yes

OME NGM (eDCO) WT 1x10GE LAN 1x11.1G RR EXT PWR yes yes yes yes yes

OME NGM (eDCO) WT 1xOTU2 1x10.7G yes yes yes yes yes

OME NGM (eDCO) WT 1xOTU2 1x10.7G EXT PWR yes yes yes yes yes

OME NGM (eDCO) WT 1xOTU2 1x10.7G RR yes yes yes yes yes

OME NGM (eDCO) WT 1xOTU2 1x10.7G RR EXT PWR yes yes yes yes yes

OME eDC40G OCLD 1xOTU3+ DWDM Enhanced PMD Comp yes yes yes yes yes (see Note 2)

OME eDC40G OCLD 1xOTU3+ DWDM yes yes yes yes yes (see Note 2)

OME eDC40G OCLD 1xOTU3+ DWDM Regional yes yes yes yes yes (see Note 2)

OME eDC40G OCLD 1xOTU3+ DWDM Metro yes yes yes yes yes (see Note 2)

OME DWDM Tunable OTR 1xOC192/STM64 1X10G RS8 FEC yes yes yes yes no

OME DWDM Tunable OTR 1xOC192/STM64 1X10.7 SCFEC yes yes yes yes no

OME DWDM Tunable OTR 1x10GE LAN 11.1G RS8 FEC yes yes yes yes no

OME DWDM Tunable OTR 1x10GE LAN 11.1G SCFEC yes yes yes yes no

OME DWDM 2xOC-48/STM-16 STS/HO VT/LO DPO yes yes yes yes no

OME DWDM 2xOC-48/STM-16 STS/HO VT/LO SFP yes yes yes yes no

OME DWDM 1xOC-192/STM64 G.709 STS/HO VT/LO yes yes yes yes no

OME DWDM 1xOC-192/STM64 G.709 HO/LO TUNE AM1 AM2 RS8 FEC

yes yes yes yes no

OME DWDM 1xOC-192/STM64 G.709 HO/LO TUNE AM1 AM2 SCFEC

yes yes yes yes no

Table 2-11 (continued)Nortel Tx and CMD compatibility

Nortel Product Line



SCMD8-Filtered




2-84 Overview

OME6500

OME SuperMux 10G DWDM Tunable 10.7G RS8 FEC yes yes yes yes no

OME SuperMux 10G DWDM Tunable 10.7G SCFEC yes yes yes yes no

OME DWDM Tunable OTSC 1xOC192/STM64 1x10.7G RS8 FEC yes yes yes yes no

OME DWDM Tunable OTSC 1xOC192/STM64 1x10.7G SCFEC yes yes yes yes no

OME DWDM Tunable OTSC 1x10GE LAN 11.1G RS8 FEC yes yes yes yes no

OME DWDM Tunable OTSC 1x10GE LAN 11.1G SCFEC yes yes yes yes no

OME OTSC Tunable 1xOTU2 1x10.7G RS8 FEC yes yes yes yes no

OME OTSC Tunable 1xOTU2 1x10.7G SCFEC yes yes yes yes no

OME OTSC Tunable FC1200 11.3G RS8 FEC yes yes yes yes no

OME OTSC Tunable FC1200 11.3G SCFEC yes yes yes yes no

Optical Metro 3500

OM3500 10G yes yes yes yes no

OM3500 2.5G yes yes yes yes no

Optical Cross Connect HDXc

HDX (_C) 4 X 10G DWDM TR Pluggable Tunable yes yes yes yes no

HDX (_C) 4 X 10G DWDM TR yes yes yes yes no

OPTera Long Haul DWDM Terminal

DT Single combiner (10G) yes yes yes yes no

DT Dual 10G WT (Line Side) yes yes yes yes no

DT Dual Regen yes yes yes yes no

Optical Long Haul 1600

LH 1600T 10G WT with TriFEC yes yes yes yes no

LH 1600T DWDM OC-48 trib yes yes yes yes no

LH 1600T 10 G WT (w/SFEC) yes yes yes yes no

OPTera Connect DX optical switch

DX 10G (w/SFEC) yes yes yes yes no

DX 10G w/TriFEC yes yes yes yes no

Note 1: Since the SCMD8-Open has an embedded EDFA with a minimum operating gain of 6 dB, DOC channel additions can fail when certain Nortel receivers that have low overload levels (for example, 0 dBm) are connected to a SCMD8-Open. To avoid this condition, it may be required to pad the receiver and to modify the Rx adjacency values. Padding and Rx adjacency provisioning information is provided by Optical Modeler or custom link engineering.Note 2: The use of OME eDC40G circuit packs with the SCMD8-Filtered must be validated by the Nortel OPNET group.

Table 2-11 (continued)Nortel Tx and CMD compatibility

Nortel Product Line



SCMD8-Filtered




3-1

Shelf configurations, wavelengths, and network management 3-

This chapter provides an overview of the configurations, wavelength plan, and network management requirements for Common Photonic Layer. Table 3-1 lists the topics in this chapter.


Topic Page

Supported network element configurations 3-2

Rack level shelf configurations 3-3

Compatible wavelength plan 3-27

Network management requirements 3-33

Network management software 3-35

SNMP support 3-35




3-2 Shelf configurations, wavelengths, and network management

Supported network element configurationsThe Nortel Common Photonic Layer supports three basic configurations:

1 Channel Access

The channel access configuration represents configurations where channels are accessible to service layer equipment. The following configurations are considered channel access configuration:

— Terminal (GMD based, WSS based, Thin based)

— GMD based optical add-drop multiplexer (OADM)

— Thin optical add-drop multiplexer (TOADM)

— Reconfigurable optical add-drop multiplexer (ROADM)

— Dependent independent access (DIA)

These configurations provide a wide variety of dense wavelength division multiplexing (DWDM) solutions.

2 Line Amplifier

3 Dynamic gain flattening filter (DGFF)

Attention: The network element configuration type is provisioned during SLAT using the nodal SLAT assistant tool (NSAT). A Provisioning Incompatible alarm is raised when the physical configuration of the shelf does not match the provisioned fixed configuration type. If “No Fixed Configuration Type” is left as the “Fixed Configuration Type” then the Provisioning Incompatible alarm is not raised regardless of what equipment is provisioned in a slot with the exception that the GMD, UOSC, or DOSC must be in slot 4. If one of the other configuration types is selected during SLAT, the modules allowed in certain slots are pre-defined. Using a module in a slot other than the pre-defined module type raises the Provisioning Incompatible alarm. Figure 3-1 to Figure 3-26 shows the equipment type that can be provisioned in a slot. If the network element contains DRAs, the “No Fixed Configuration Type” default must be used. If the network element contains a cascaded LIM, the “No Fixed Configuration Type” default must be used. For DIA terminals, the “No Fixed Configuration Type” default must be used.




Shelf configurations, wavelengths, and network management 3-3

Rack level shelf configurationsThe following rack level shelf configurations are shown:

• “WSS-based terminal - rack level configuration” on page 3-5

• “WSS-based terminal with DSCM and cascaded LIM - rack level configuration” on page 3-6

• “ROADM (without DRA) - rack level configuration” on page 3-7

• “ROADM (with DRA) - rack level configuration” on page 3-8

• “ROADM (with DRA, CMD44 50 GHz, CMDA, and 4 SCMDs) - rack level configuration” on page 3-9

• “ROADM (with DRA, CMD44 50 GHz, CMDA, and 2 SCMDs) - rack level configuration” on page 3-10

• “ROADM (with DRA, CMD44 50 GHz, CMDA, 2 SCMDs, and cascaded LIM) - rack level configuration” on page 3-11

• “ROADM (large channel access with DRA) - rack level configuration” on page 3-12

• “ROADM (large channel access with DRA and cascaded LIM) - rack level configuration” on page 3-13

• “ROADM (with DRA and CMD44 100 GHz) - rack level configuration” on page 3-14

• “DIA 50 GHz (with shelf level controller) - rack level configuration” on page 3-15

• “DIA 100 GHz (with shelf level controller) - rack level configuration” on page 3-15

• “DIA 50 GHz (without shelf level controller) - rack level configuration” on page 3-16

• “DIA 100 GHz (without shelf level controller) - rack level configuration” on page 3-16

• “Thin terminal- rack level configuration” on page 3-17

• “Thin terminal, with CMD44 100 GHz (with DRA) - rack level configuration” on page 3-18

• “Thin terminal, with CMD44 100 GHz (without DRA) - rack level configuration” on page 3-19

• “Thin OADM - rack level configuration” on page 3-20

• “Thin OADM (small channel access with DRA) - rack level configuration” on page 3-21

• “GMD-based terminal - rack level configuration” on page 3-22

• “GMD-based terminal (with planning considerations for a future ROADM) - rack level configuration” on page 3-23





• “GMD-based OADM (small channel access with DRA) - rack level configuration” on page 3-24

• “GMD-based OADM - rack level configuration” on page 3-25

• “Line amplifier- rack level configuration” on page 3-26

• “Line amplifier- rack level configuration with DRA” on page 3-26

• “eDCO line amplifier (no DSCMs) - rack level configuration” on page 3-27

Refer to Chapter 2, “Overview” for block diagrams of each supported configuration.





Figure 3-1WSS-based terminal - rack level configuration

123456789

1011121314151617181920212223.....

4344

0102

03

050607080910111213

04

BIP / FIPFuture BIP/FIPFuture BIP/FIP

FM (Slack Storage)

UOSC

OPMMLA or MLA2

WSSDSCM or FMDSCM or FM

SCMDxSCMDxSCMDxSCMDxSCMDxSCMDxSCMDxSCMDxSCMDx

RU No. Module Description Slot

Note 1: The specific SCMD groups are assigned to WSS ports and the cascade order is provisioned. Note 2: You cannot have SCMD modules with the same group number in a shelf.Note 3: Use MLA or MLA2 depending on link budgets. Note 4: If compensated, an interior SLA is required.Note 5: Scalable to 9 SCMD groups.Note 6: The 1U BIP or 1U FIP saves space.Note 7: Multi-Slot Carrier allows shipment of modules in place.Note 8: SCMD4 or SCMD8 modules and CMD44 modules can be connected on the same WSS moduleonly if they are connected on different switch ports. �Cascading CMD44 and SCMD4/SCMD8 modules from each other is not supported.�Note 9: A mix of SCMD4 and SCMD8 (Open and Filtered) are supported. CMD44 100 GHz cannot interwork with SCMD8s.Note 10: Three SCMDs can be cascaded from a WSS port. To cascade four or five SCMDs, contact Nortel for custom link engineering.

Mul

ti-sl

ot-c

arrie

r Typ

e 1

RO

AD

M (

NT

T89

9AQ

)





Figure 3-2WSS-based terminal with DSCM and cascaded LIM - rack level configuration

1234567891011121314151617181920212223.....

4344

0506070809101112

04

BIP / FIPFuture BIP/FIP

OPM

FM (Slack Storage)

UOSC

Cascaded LIMMLA or MLA2

WSSDSCM or FMDSCM or FM

SCMDxSCMDxSCMDxSCMDxSCMDxSCMDxSCMDxSCMDx


Note 1: The specific SCMD groups are assignedto WSS ports and the cascade order is provisioned. Note 2: You cannot have SCMD modules with the same group number in a shelf.Note 3: Use MLA or MLA2 depending on link budgets.Note 4: If compensated, an cascaded LIM is required.Note 5: Scalable to 8 SCMD groups.Note 6: The 1U BIP or 1U FIP saves space.Note 7: Multi-Slot Carrier allows shipment of modules in place.Note 8: SCMD4 or SCMD8 modules and CMD44 modules can be connected on the same WSS moduleonly if they are connected on different switch ports. �Cascading CMD44 and SCMD4/SCMD8 modules from each other is not supported.�Note 9: A mix of SCMD4 and SCMD8 (Open and Filtered) are supported. CMD44 100GHz cannot interwork with SCMD8s.Note 10: Three SCMDs can be cascaded from a WSS port. To cascade 4 or 5 SCMDs, contact Nortel.Note 11: OPM is mandatory. OPM can be shared between two WSS terminal based NEs.

Mul

ti-sl

ot-c

arrie

r Typ

e 1

RO

AD

M (

NT

T89

9AQ

)

13 01

03

02





Figure 3-3ROADM (without DRA) - rack level configuration

0102

050607080910111213

04

BIP / FIP -east-facing NEBIP / FIP -west-facing NE

Future BIP / FIP

OPM MLA or MLA2

Cascaded LIM (Optional)

DSCM or FMDSCM or FM


FM (Slack Storage)SCMDxSCMDxSCMDxSCMDxSCMDxSCMDxSCMDxSCMDxSCMDx

OPM MLA or MLA2

Cascaded LIM (Optional)

Note 1: WSS provisioned with UOSC. Note 2: SCMD4s or SCMD8 and CMD44s can be connected on the same WSS module only if they are �connected on different switch ports. Cascading CMD44s and SCMD4s/SCMD8s from each other is not supported. �A mix of SCMD4 and SCMD8 (Open and Filtered) are supported. CMD44 100 GHz cannot interwork with SCMD8s.Note 3: OPM is mandatory. OPM can be shared between two ROADM NEs.Note 4: Use MLA or MLA2 depending on link budgets. If compensated, an interior SLA also required.Note 5: Additional BIP/FIP required if network element exceeds 13 modules. Note 7: Multi-Slot Carrier allows shipment of modules in place.Note 8: Max. footprint shown when MSCs are not used. Min. footprint shown when MSC Type 1 are used.Note 9: Three SCMDxs can be cascaded from a WSS port. To cascade 4 or 5 SCMDxs, contact Nortel.

UOSC

123456789

10111213141516171819202122232425262728293031323334..

41.

44

0102

0506..

13

FM (Slack Storage)SCMDxSCMDxSCMDxSCMDxSCMDx

03WSS

03WSS


04UOSC

Multi

-slo

t-ca

rrie

r Ty

pe 1

RO

AD

M (

NT

T899A

Q)

Multi

-slo

t-ca

rrie

r Ty

pe 1

RO

AD

M (

NT

T899A

Q)





Figure 3-4ROADM (with DRA) - rack level configuration

13

05060708

04


Future BIP / FIP


FM (Slack Storage)SCMDxSCMDxSCMDxSCMDx

Note 1: WSS provisioned with UOSC. Note 2: SCMD4s or SCMD8s and CMD44s can be connected on the same WSS module only if they �are connected on different switch ports. Cascading CMD44s and SCMD4s/SCMD8s from each other is �not supported. A mix of SCMD4 and SCMD8 (Open and Filtered) are supported. CMD44 100 GHz cannot interwork with SCMD8s.Note 3: OPM is mandatory. OPM can be shared between two ROADM NEs.Note 4: Use MLA or MLA2 depending on link budgets. If compensated, an interior SLA also required.Note 5: Additional BIP/FIP required if network element exceeds 13 modules. Note 6: Multi-Slot Carrier allows shipment of modules in place.Note 7: Max. footprint shown when MSCs are not used. Min. footprint shown when MSC Type 1 are used.Note 8: Three SCMDxs can be cascaded from a WSS port. To cascade 4 SCMDxs, contact Nortel.

UOSC

123456789

10111213141516171819202122232425262728293031323334..

41.

44

02

WSS

Mul

ti-sl

ot-c

arrie

r Typ

e 1

RO

AD

M (N

TT89

9AQ

)

DRA

OPM or Cascaded LIM 01

MLA/MLA2/SLA/LIM

03

FM (Slack Storage)FM (Slack Storage)





Figure 3-5ROADM (with DRA, CMD44 50 GHz, CMDA, and 4 SCMDs) - rack level configuration

13

05060708

04

BIPFuture BIP


FM (Slack Storage)SCMDxSCMDxSCMDxSCMDx

Note 1: WSS provisioned with UOSC. Note 2: SCMD4s or SCMD8s and CMD44s can be connected on the same WSS module only if they are �connected on different switch ports. Cascading CMD44s and SCMD4s/SCMD8s from each other is not supported. �A mix of SCMD4 and SCMD8 (Open and Filtered) are supported. CMD44 100 GHz cannot interwork with SCMD8s.Note 3: OPM is mandatory. OPM can be shared between two ROADM NEs.Note 4: Use MLA or MLA2 depending on link budgets. If compensated, an interior SLA also required.Note 5: Additional BIP/FIP required if network element exceeds 13 modules (CMD44 do not require BIP/FIP). Note 6: Multi-Slot Carrier allows shipment of modules in place.Note 7: Max. footprint shown when MSCs are not used. Min. footprint shown when MSC Type 1 are used.Note 8: Three SCMDxs can be cascaded from a WSS port. To cascade 4 SCMDxs, contact Nortel.Note 9: CMDA, WSS, and CMD44s use FM in rack unit 13.

UOSC

CMDA

CMD44 50GHz Blue

CMD44 50GHz Red

123456789

10111213141516171819202122232425262728293031323334..

41.

44

02

WSS

Mu

lti-s

lot-

carr

ier

Typ

e 1

RO

AD

M (

NT

T8

99

AQ

)

DRA

OPM or Cascaded LIM 01

MLA/MLA2/SLA/LIM

03

09

14

15






Figure 3-6ROADM (with DRA, CMD44 50 GHz, CMDA, and 2 SCMDs) - rack level configuration

0506

04

BIP Future BIP / FIP


FM (Slack Storage)SCMDx

Note 1: WSS provisioned with UOSC. Note 2: SCMD4s or SCMD8s and CMD44s can be connected on the same WSS module only if they are �connected on different switch ports. Cascading CMD44s and SCMD4s/SCMD8s from each other is not supported. �A mix of SCMD4 and SCMD8 (Open and Filtered) are supported. CMD44 100 GHz cannot interwork with SCMD8s.Note 3: OPM is mandatory. OPM can be shared between two ROADM NEs.Note 4: Use MLA or MLA2 depending on link budgets. Note 5: Additional BIP/FIP required if network element exceeds 13 modules (CMD44 do not need BIP/FIP). Note 6: Multi-Slot Carrier allows shipment of modules in place.Note 7: Max. footprint shown when MSCs are not used. Min. footprint shown when MSC Type 1 are used.Note 8: Three SCMDxs can be cascaded from a WSS port. To cascade 4 or 5 SCMDxs, contact Nortel.Note 9: CMDA, WSS, and CMD44s use FM in rack unit 11.

UOSC

123456789

10111213141516171819202122232425262728293031323334..

41.

44

02

WSS

SCMDx

CMDA

CMD44 50GHz Blue

CMD44 50GHz RedM

ulti

-slo

t-ca

rrie

r Ty

pe

1R

OA

DM

(N

TT

89

9A

Q)

OPM 01MLA/MLA2

03

07

08

14

15

FM (Slack Storage)

FM (Slack Storage)

DRA





Figure 3-7ROADM (with DRA, CMD44 50 GHz, CMDA, 2 SCMDs, and cascaded LIM) - rack level configuration

0506

04

BIP Future BIP / FIP


FM (Slack Storage)SCMDx

Note 1: WSS provisioned with UOSC. Note 2: SCMD4s or SCMD8s and CMD44s can be connected on the same WSS module only if they are �connected on different switch ports. Cascading CMD44s and SCMD4s/SCMD8s from each other is not supported. �A mix of SCMD4 and SCMD8 (Open and Filtered) are supported. CMD44 100 GHz cannot interwork with SCMD8s.Note 3: OPM is mandatory. OPM can be shared between two ROADM NEs.Note 4: Use MLA or MLA2 depending on link budgets. Note 5: Additional BIP/FIP required if network element exceeds 13 modules (CMD44 do not need BIP/FIP). Note 6: Multi-Slot Carrier allows shipment of modules in place.Note 7: Max. footprint shown when MSCs are not used. Min. footprint shown when MSC Type 1 are used.Note 8: Three SCMDxs can be cascaded from a WSS port. To cascade 4 or 5 SCMDxs, contact Nortel.Note 9: CMDA, WSS, and CMD44s use FM in rack unit 11.

UOSC

12345678910111213141516171819202122232425262728293031323334..

41.

44

02

WSS

SCMDxCMDA

CMD44 50GHz Blue

CMD44 50GHz Red

Multi

-slo

t-ca

rrie

r Ty

pe 1

RO

AD

M (

NT

T899A

Q)

OPM

Cascaded LIM 01MLA/MLA2

03

07

08

13

14

15

FM (Slack Storage)

FM (Slack Storage)

DRA





Figure 3-8ROADM (large channel access with DRA) - rack level configuration

0506070809101112

04


Future BIP / FIP


FM (Slack Storage)SCMDxSCMDxSCMDxSCMDxSCMDxSCMDxSCMDxSCMDx

Note 1: WSS provisioned with UOSC. Note 2: SCMD4s or SCMD8s and CMD44s can be connected on the same WSS module only if they are �connected on different switch ports. Cascading CMD44s and SCMD4s/SCMD8s from each other is not supported. �A mix of SCMD4 and SCMD8 (Open and Filtered) are supported. CMD44 100 GHz cannot interwork with SCMD8s.Note 3: OPM is mandatory. OPM can be shared between two ROADM NEs.Note 4: Use MLA or MLA2 depending on link budgets. If compensated, an interior SLA is also required.Note 5: Additional BIP/FIP required if network element exceeds 13 modules. Note 6: Multi-Slot Carrier allows shipment of modules in place.Note 7: Max. footprint shown when MSCs are not used. Min. footprint shown when MSC Type 1 are used.Note 8: Three SCMDxs can be cascaded from a WSS port. To cascade 4 or 5 SCMDxs, contact Nortel.

UOSC

123456789

10111213141516171819202122232425262728293031323334..

41.

44

02

WSS

Mu

lti-s

lot-

carr

ier

Typ

e 1

RO

AD

M (

NT

T899A

Q)

OPM 01

MLA/MLA2/SLA/LIM

03


DRA 13





Figure 3-9ROADM (large channel access with DRA and cascaded LIM) - rack level configuration

05060708091011

04


Future BIP / FIP


FM (Slack Storage)SCMDxSCMDxSCMDxSCMDxSCMDxSCMDxSCMDx

OPM

Note 1: WSS provisioned with UOSC. Note 2:SCMD4s or SCMD8s and CMD44s can be connected on the same WSS module only if they are �connected on different switch ports. Cascading CMD44s and SCMD4s/SCMD8s from each other is not supported. �A mix of SCMD4 and SCMD8 (Open and Filtered) are supported. CMD44 100 GHz cannot interwork with SCMD8s.Note 3: OPM is mandatory. OPM can be shared between two ROADM NEs.Note 4: Use MLA or MLA2 depending on link budgets. If compensated, an interior SLA is also required.Note 5: Additional BIP/FIP required if network element exceeds 13 modules. Note 6: Multi-Slot Carrier allows shipment of modules in place.Note 7: Max. footprint shown when MSCs are not used. Min. footprint shown when MSC Type 1 are used.Note 8: Three SCMDxs can be cascaded from a WSS port. To cascade 4 or 5 SCMDxs, contact Nortel.

UOSC

12345678910111213141516171819202122232425262728293031323334..

41.

44

02

WSS

Multi

-slo

t-ca

rrie

r Ty

pe 1

RO

AD

M (

NT

T899A

Q)

Cascaded LIM 01

MLA/MLA2/SLA/LIM

03


DRA

13

12





Figure 3-10ROADM (with DRA and CMD44 100 GHz) - rack level configuration

05060708091011

04



FM (Slack Storage)SCMD4SCMD4

SCMD4 (future)SCMD4 (future)SCMD4 (future)SCMD4 (future)SCMD4 (future)

Note 1: WSS provisioned with UOSC. Note 2:SCMD4s or SCMD8s and CMD44s can be connected on the same WSS module only if they are �connected on different switch ports. Cascading CMD44s and SCMD4s/SCMD8s from each other is not supported. �A mix of SCMD4 and SCMD8 (Open and Filtered) are supported. CMD44 100 GHz cannot interwork with SCMD8s.Note 3: OPM is mandatory. OPM can be shared between two ROADM NEs.Note 4: Use MLA or MLA2 depending on link budgets. If compensated, an interior SLA is also required.Note 5: Additional BIP/FIP required if network element exceeds 13 modules. Note 6: Multi-Slot Carrier allows shipment of modules in place.Note 7: Max. footprint shown when MSCs are not used. Min. footprint shown when MSC Type 1 are used.Note 8: Three SCMDxs can be cascaded from a WSS port. To cascade 4 or 5 SCMDxs, contact Nortel.

UOSC

123456789

101112131415161718192021222324252627282930313233343536..

44

02

WSS

WSS

UOSC

Multi

-slo

t-ca

rrie

r Ty

pe 1

RO

AD

M (

NT

T899A

Q)

Cascaded LIM 01MLA/MLA2

03

FM (Slack Storage)

DRA

13

12

FM (Slack Storage)

OPM

14

CMD44

FillerMLA


FM (Slack Storage)SCMD4SCMD4

01

03

04

0506

CMD44 14

Multi

-slo

t-ca

rrie

r Ty

pe 1

RO

AD

M (

NT

T899A

Q)





Figure 3-11DIA 50 GHz (with shelf level controller) - rack level configuration

Figure 3-12DIA 100 GHz (with shelf level controller) - rack level configuration

123456789

10111213...

4344

14-3014-30

14-30


OPM (if not shared)

BMD2CMD44 50 GHz Blue

CMD44 50 GHz Red

MLA, MLA2, SLA, or LIMWSS

UOSC or DOSC


Note 1: Use MLA, MLA2, SLA, or LIM depending on link budgets.Note 2: The 1U BIP or 1U FIP saves space.Note 3: OPM is mandatory. OPM can be shared between two WSS terminal based NEs.

01 02

04

03

123456789

10111213...

4344

14-30


OPM (if not shared)

eCMD44 100 GHz

MLA, MLA2, SLA, or LIMWSS

UOSC or DOSC



01 02

04

03





Figure 3-13DIA 50 GHz (without shelf level controller) - rack level configuration

Figure 3-14DIA 100 GHz (without shelf level controller) - rack level configuration

123456789

10111213...

4344

14-3014-30

14-30


OPM (if not shared)MLA, MLA2, SLA, or LIM

FMTFMTWSS

BMD2CMD44 50 GHz Blue

CMD44 50 GHz Red



01 02

03

MS

C T

ype

2(N

TT

899A

R)

123456789

10111213...

4344

14-30


OPM (if not shared)MLA, MLA2, SLA, or LIM

FMTFMTWSS

eCMD44 100 GHz



01 02

03

MS

C T

ype

2(N

TT

899A

R)





Figure 3-15Thin terminal- rack level configuration

0102

05060708

04

BIP / FIPFutureFuture

OPM (optional)MLA/MLA2


SCMDSCMDSCMDSCMD

Note 1: A typical thin terminal configuration does not allocate space for WSS. Note 2: Use MLA or MLA2 depending on link budgets.Note 3: If compensated, an interior SLA is also required.Note 4: Additional BIP/FIP required if network element exceeds 13 modules. The 1U-BIP/FIP saves space.Note 5: Multi-Slot Carrier allows shipment of modules in place. Note 6: You cannot have SCMD modules with the same group number in a shelf. Note 7: CMD44 100 GHz modules cannot interwork with SCMD8 modules.

FM (Slack Storage)

UOSC

FM (Slack Storage)

123456789

101112131415161718...

4344

MS

C T

ype

3TO

AD

M(N

TT

899A

S)DSCM or FM





Figure 3-16Thin terminal, with CMD44 100 GHz (with DRA) - rack level configuration

0102

05060708

04

BIP / FIPFuture

OPM (optional)MLA/SLA/LIM


SCMD4SCMD4

SCMD4 (Future)SCMD4 (Future)

Note 1: A typical thin terminal configuration does not allocate space for WSS. Note 2: Use MLA or MLA2 depending on link budgets.Note 3: If compensated, an interior SLA is also required.Note 4: Additional BIP/FIP required if network element exceeds 13 modules.The 1U-BIP/FIP saves space.Note 5: Multi-Slot Carrier allows shipment of modules in place. Note 6: You cannot have SCMD4 modules with the same group number in a shelf.Note 7: CMD44 100 GHz modules cannot interwork with SCMD8 modules.�

FM/DSCM

UOSC

FM (Slack Storage)

123456789

101112131415161718...

4344

DRA 03

FM (Slack Storage)

CMD44 14

Mul

ti-sl

ot-c

arrie

r Typ

e 1

(N

TT

899A

Q)





Figure 3-17Thin terminal, with CMD44 100 GHz (without DRA) - rack level configuration

0102

05060708

04

BIP / FIPFuture

OPM (optional)MLA/SLA/LIM


SCMD4SCMD4 (Future)SCMD4 (Future)SCMD4 (Future)

Note 1: A typical thin terminal configuration does not allocate space for WSS. Note 2: Use MLA or MLA2 depending on link budgets.Note 3: If compensated, an interior SLA is also required.Note 4: Additional BIP/FIP required if network element exceeds 13 modules.The 1U-BIP/FIP saves space.Note 5: Multi-Slot Carrier allows shipment of modules in place. Note 6: You cannot have SCMD4 modules with the same group number in a shelf. Note 7: CMD44 100 GHz modules cannot interwork with SCMD8 modules.

FM/DSCM

UOSC

FM (Slack Storage)

123456789

101112131415161718...

4344

FM (Slack Storage)

CMD44 14

MS

C T

ype

3TO

AD

M(N

TT

899A

S)





Figure 3-18Thin OADM - rack level configuration

02

05060708

04


Future BIP / FIPLIM/SLA/MLA/MLA2

DSCM or FM


SCMD4SCMD4SCMD4SCMD4

Note 1: A typical TOADM configuration does not allocate space for WSS. This space can be allocated for future expansion to a ROADM.Note 2: Use MLA or MLA2 depending on link budgets.Note 3: If compensated, SLA also required.Note 4: Additional Universal BIP/FIP required ifnetwork element exceeds 13 modules. The 1U- BIP / FIP saves space.Note 5: Multi-Slot Carrier allows shipment of modules in place. Note 6: If a type 3 multi-slot carrier is used, the WSS is not supported.

DSCM or FM

UOSC

FM (Slack Storage)

123456789

1011121314151617181920212223242526272829303132333435.

44

02

05060708

04

LIM/SLA/MLA/MLA2DSCM or FM

SCMD4SCMD4SCMD4SCMD4

DSCM or FM

UOSC

FM (Slack Storage)

MS

C T

ype

3TO

AD

M(N

TT

899A

S)

MS

C T

ype

3TO

AD

M(N

TT

899A

S)





Figure 3-19Thin OADM (small channel access with DRA) - rack level configuration

0102

05060708

04

BIP / FIPFuture

Optional OPM or Extra SLAMLA/SLA/LIM


SCMD/CMD4SCMD/CMD4SCMD/CMD4SCMD/CMD4

Note 1: Use MLA or MLA2 depending on link budgets.Note 2: If compensated, SLA also required.Note 3: Additional BIP/FIP required if network element exceeds 13 modules.The 1U-BIP/FIP saves space.Note 5: Multi-Slot Carrier allows shipment of modules in place. Note 6: You cannot have SCMD4 modules with the same group number in a shelf.

GMD

FM (Slack Storage)

123456789

101112131415161718...

4344

FM (Slack Storage)

DRA 03

Mul

ti-sl

ot-c

arrie

r Typ

e 1

(N

TT

899A

Q)





Figure 3-20GMD-based terminal - rack level configuration

123456789

1011121314151617181920212223.....

4344

050607080910111213

04

BIP / FlP

FM (Slack Storage)

GMD type 2

OPM (optional)LIM/SLA/MLA/MLA2


CMD4/SCMDxCMD4/SCMDxCMD4/SCMDxCMD4/SCMDxCMD4/SCMDxCMD4/SCMDxCMD4/SCMDxCMD4/SCMDxCMD4/SCMDx

FutureFutureFutureFutureFutureFutureFutureFutureFutureFutureFuture


Note 1: A mix of CMD4s, SCMD4s and SCMD8s can be connectedto the GMD type 2 only if they are not connected serially (cascaded)and none of the modules have the same group number. CMD44 modules: cannot be used in at GMD based terminal sites.Note 2: Scalable to 9 SCMD groups.Note 3: The 1U BIP or 1U FIB saves space.Note 4: Up to 72 wavelengths supported.Note 5: Multi-Slot Carrier allows shipment of modules in place.

Future BIP / FIPFuture BIP / FIP

Mul

ti-sl

ot-c

arrie

r T

ype

3 (

NT

T89

9AS

)

0102





Figure 3-21GMD-based terminal (with planning considerations for a future ROADM) - rack level configuration

For a GMD OADM to ROADM reconfiguration, the existing GMD can be used as the shelf controller instead of a UOSC. Contact your Nortel representative for more information.

123456789

1011121314151617181920212223.....

4344

0102

03

050607080910111213

04

BIP / FIP

FM (Slack Storage)

GMD type 2

OPM (optional)LIM/SLA/MLA/MLA2

Future WSSDSCM or FMDSCM or FM

SCMDx (Grp 1)SCMDx (Grp 2)SCMDx (Grp 3)SCMDx (Grp 4)SCMDx (Grp 5)SCMDx (Grp 6)SCMDx (Grp 7)SCMDx (Grp 8)SCMDx (Grp 9)

FutureFutureFutureFutureFutureFutureFutureFutureFuture


Note 1: A mix of CMD4s, SCMD4s and SCMD8s can be connected to the GMD type 2 only if they are not connected serially (cascaded). However,CMD4s cannot be used at a WSS node. CMD44 modules cannot be used atGMD based terminal sites.Note 2: Scalable to 9 SCMD groups.Note 3: The 1U BIP or 1U FIB saves space.Note 4: Up to 72 wavelengths supported.Note 5: Multi-Slot Carrier allows shipment of modules in place.Note 6: If compensated, a future ROADM site would require an additional interior SLA.Note 7: A future ROADM site would use a UOSC in logical slot 04.

Future BIP/ FIPFuture BIP / FIP

Mul

ti-sl

ot-c

arrie

r Typ

e 1

GM

D T

erm

(N

TT

899A

Q)





Figure 3-22GMD-based OADM (small channel access with DRA) - rack level configuration

0102

05060708

04

BIP / FIPFuture

Optional OPM or Interior SLAMLA/SLA/LIM


SCMD/CMD4SCMD/CMD4SCMD/CMD4SCMD/CMD4

Note 1: Use MLA or MLA2 depending on link budgets.Note 2: If compensated, an interior SLA is also required.Note 3: Additional BIP/FIP required if network element exceeds 13 modules.The 1U-BIP/FIP saves space.Note 5: Multi-Slot Carrier allows shipment of modules in place. Note 6: You cannot have SCMD4 modules with the same group number in a shelf.

GMD

FM (Slack Storage)

123456789

101112131415161718...

4344

FM (Slack Storage)

DRA 03

Mul

ti-sl

ot-c

arrie

r Typ

e 1

(N

TT

899A

Q)





Figure 3-23GMD-based OADM - rack level configuration

1,2,3456789

10111213141516171819202122232425262728293031323334353637..

4344

0102

050607080910111213

04

BIP / FIP

FM (Slack Storage)

GMD

FutureSLA / MLA / LIM

DSCMDSCM

SCMDx or CMD4SCMDx or CMD4SCMDx or CMD4

(s)CMDx(s)CMDx(s)CMDx(s)CMDx


0102

050607080910111213

04

FM (Slack Storage)

GMD

FutureSLA / MLA / LIM

DSCMDSCM

(s)CMDx(s)CMDx(s)CMDx(s)CMDx(s)CMDx(s)CMDx(s)CMDx(s)CMDx(s)CMDx

Note 1: A mix of CMD4s, SCMD4s and SCMD8s can be connected to the GMD type 2 only ifthey are not connected serially (cascaded) and none of the modules have the same group number.CMD44 modules cannot be used at GMD based OADM sitesNote 2: Scalable to 9 SCMD groups.Note 3: The 1U BIP or FIB saves space.Note 4: Up to 72 wavelengths supported.Note 5: Use an OPM in Slot 1 for extended reach systems.

MS

C T

ype

3TO

AD

M(N

TT

899A

S)

MS

C T

ype

3TO

AD

M(N

TT

899A

S)





Figure 3-24Line amplifier- rack level configuration

Figure 3-25Line amplifier- rack level configuration with DRA

1,23456789

0102

SLA/MLA/MLA2 - direction 1SLA/MLA/MLA2 - direction 2DSCM (Mux Out to Amp In)

DSCM (Amp B Out to Demux In)

DOSC 04

BIP (common)


Note 1: Multi-Slot Carrier allows shipment of modules in place.Note 2: Use multi-slot carrier type 2 (NTT899AR) for line amplifiers.Note 3: At line amplifier sites it is occasionally deemed necessary todeploy an Optical Power Monitor (OPM) to improve VOSA performance. At line amplifier sites, the OPM must be deployed in slot 3. Place the OPM below the DOSC. If a multi-slot carrier is used the Ethernet harness may not accommodate the OPM. Therefore a separate Ethernet cable is required.

MS

C T

ype

2(N

TT

899A

R)

1,23456789

101112

0102

MLA/MLA2 - direction 1MLA/MLA2 - direction 2

DSCM (Mux Out to Amp In)DSCM (Amp B Out to Demux In)

DOSC

DRA - direction 1

DRA - direction 2

04

BIP (common)


Note 1: Multi-Slot Carrier allows shipment of modules in place.Note 2: Use multi-slot carrier type 2 (NTT899AR) for line amplifiers.Note 3: At line amplifier sites it is occasionally deemed necessary todeploy an Optical Power Monitor (OPM) to improve VOSA performance. At line amplifier sites, the OPM must be deployed in slot 3. Place the OPM below the DOSC. If a multi-slot carrier is used the Ethernet harness may not accommodate the OPM. Therefore a separate Ethernet cable is required.Note 4: DRA requirement is application dependent.

MS

C T

ype

2(N

TT

899A

R)

06

05





Figure 3-26eDCO line amplifier (no DSCMs) - rack level configuration

Compatible wavelength planBoth 100 GHz and 50 GHz sources can be connected to the CMD44s, SCMD4s, or the Open SCMD8s. Wavelengths must adhere to ITU G.698.1 narrow 100 GHz specification. In the Nortel portfolio, these include 50 GHz and 100 GHz wavelengths designated to operate on the Common Photonic spectral grid. Wavelengths on the 50 GHz wavelength grid can be routed through the GMD and the 50 GHz WSS. The 100 GHz WSS can only route wavelengths on the 100 GHz wavelength grid.

Connecting any mixture of optical systems to the same CMD may require specialized link budget and equipping rules. Mixed-wavelength CMD applications should be validated with Nortel prior to deployment.

The Common Photonic Layer wavelength plan, shown in Table 3-2 on page 3-28, provides a view of the wavelength plan for 100 GHz ITU grid. The CMD44 100 GHz uses the existing Common Photonic Layer 100 GHz ITU grid 36 wavelength plan, plus an additional eight skip channels between the nine Nortel Common Photonic Layer wavelength groups for a total of 44 wavelengths. See Table 3-3 on page 3-28 for all CMD44 wavelengths.

Table 3-4 on page 3-29 provides the 50 GHz ITU grid wavelength plan. The CMD44 50 GHz use the existing Common Photonic Layer 50 GHz ITU grid 72 wavelength plan, plus an additional 16 skip channels between the nine Common Photonic Layer wavelength groups for a total of 88 wavelengths. See Table 3-5 on page 3-30 for all CMD44 wavelengths.

OM5100/5200 supports all 36 (44 with the OM5100/5200 tunable circuit packs) channels on the Common Photonic Layer 100 GHz grid and all 72 (88 with the OM5100/5200 tunable circuit packs) channels on the Common Photonic Layer 50 GHz grid. See Table 3-6 on page 3-31 for the OM5100/5200 and CMD44 wavelength plan.

1,23456789

0102

SLA/MLA/MLA2 - direction 1SLA/MLA/MLA2 - direction 2

Fiber Manager (Bulk Slack Storage)Fiber Manager (Bulk Slack Storage)

DOSC 04

BIP (common)


Note 1: Multi-Slot Carrier allows shipment of modulesin place.Note 2: Use multi-slot carrier type 2 (NTT899AR) for line amplifiers.

MS

C T

ype

2(N

TT

899A

R)





Table 3-2Common Photonic Layer 100 GHz ITU grid 36 wavelength plan

Group #

Channel Wavelength100 GHz(nm)

Group #


Group #


1 1

2

3

4

1530.33

1531.12

1531.90

1532.68

4 1

2

3

4

1542.14

1542.94

1543.73

1544.53

7 1

2

3

4

1554.13

1554.94

1555.75

1556.55

2 1

2

3

4

1534.25

1535.04

1535.82

1536.61

5 1

2

3

4

1546.12

1546.92

1547.72

1548.51

8 1

2

3

4

1558.17

1558.98

1559.79

1560.61

3 1

2

3

4

1538.19

1538.98

1539.77

1540.56

6 1

2

3

4

1550.12

1550.92

1551.72

1552.52

9 1

2

3

4

1562.23

1563.05

1563.86

1564.68

Table 3-3Common Photonic Layer 100 GHz ITU grid 44 wavelength plan (for the CMD44 100 GHz)

Channel Wavelength 100 GHz(nm)




1 1530.33 12 1538.98 23 1547.72 34 1556.55

2 1531.12 13 1539.77 24 1548.51 35 1557.36

3 1531.90 14 1540.56 25 1549.32 36 1558.17

4 1532.68 15 1541.35 26 1550.12 37 1558.98

5 1533.47 16 1542.14 27 1550.92 38 1559.79

6 1534.25 17 1542.94 28 1551.72 39 1560.61

7 1535.04 18 1543.73 29 1552.52 40 1561.42

8 1535.82 19 1544.53 30 1553.33 41 1562.23

9 1536.61 20 1545.32 31 1554.13 42 1563.05

10 1537.40 21 1546.12 32 1554.94 43 1563.86

11 1538.19 22 1546.92 33 1555.75 44 1564.68





OME6500 supports all 88 channels on the Common Photonic Layer 50 GHz grid.

The two-level multiplexing strategy for the nine group filters with a 100 GHz four-skip-one cadence results in up to 36 x 100 GHz wavelengths in the C-band. In the case of the 50 GHz ITU grid, each of the nine groups can have up to eight wavelengths, resulting in up to 72 x 50 GHz wavelengths in the C-band.

Table 3-4Common Photonic Layer 50 GHz ITU grid 72 wavelength plan

Group #


Group #


Group #


1 1

2

3

4

5

6

7

8

1530.33

1530.72

1531.12

1531.51

1531.90

1532.29

1532.68

1533.07

4 1

2

3

4

5

6

7

8

1542.14

1542.54

1542.94

1543.33

1543.73

1544.13

1544.53

1544.92

7 1

2

3

4

5

6

7

8

1554.13

1554.54

1554.94

1555.34

1555.75

1556.15

1556.55

1556.96

2 1

2

3

4

5

6

7

8

1534.25

1534.64

1535.04

1535.43

1535.82

1536.22

1536.61

1537.00

5 1

2

3

4

5

6

7

8

1546.12

1546.52

1546.92

1547.32

1547.72

1548.11

1548.51

1548.91

8 1

2

3

4

5

6

7

8

1558.17

1558.58

1558.98

1559.39

1559.79

1560.20

1560.61

1561.01

3 1

2

3

4

5

6

7

8

1538.19

1538.58

1538.98

1539.37

1539.77

1540.16

1540.56

1540.95

6 1

2

3

4

5

6

7

8

1550.12

1550.52

1550.92

1551.32

1551.72

1552.12

1552.52

1552.93

9 1

2

3

4

5

6

7

8

1562.23

1562.64

1563.05

1563.45

1563.86

1564.27

1564.68

1565.09





Table 3-5Common Photonic Layer 50 GHz ITU grid 88 wavelength plan (for the CMD44 50 GHz)





1 1530.33 23 1538.98 45 1547.72 67 1556.55

2 1530.72 24 1539.37 46 1548.11 68 1556.96

3 1531.12 25 1539.77 47 1548.51 69 1557.36

4 1531.51 26 1540.16 48 1548.91 70 1557.77

5 1531.90 27 1540.56 49 1549.32 71 1558.17

6 1532.29 28 1540.95 50 1549.72 72 1558.58

7 1532.68 29 1541.35 51 1550.12 73 1558.98

8 1533.07 30 1541.75 52 1550.52 74 1559.39

9 1533.47 31 1542.14 53 1550.92 75 1559.79

10 1533.86 32 1542.54 54 1551.32 76 1560.20

11 1534.25 33 1542.94 55 1551.72 77 1560.61

12 1534.64 34 1543.33 56 1552.12 78 1561.01

13 1535.04 35 1543.73 57 1552.52 79 1561.42

14 1535.43 36 1544.13 58 1552.93 80 1561.83

15 1535.82 37 1544.53 59 1553.33 81 1562.23

16 1536.22 38 1544.92 60 1553.73 82 1562.64

17 1536.61 39 1545.32 61 1554.13 83 1563.05

18 1537.00 40 1545.72 62 1554.54 84 1563.45

19 1537.40 41 1546.12 63 1554.94 85 1563.86

20 1537.79 42 1546.52 64 1555.34 86 1564.27

21 1538.19 43 1546.92 65 1555.75 87 1564.68

22 1538.58 44 1547.32 66 1556.15 88 1565.09





Table 3-6OM5100/5200 and CPL 100 GHz and 50 GHz wavelength plans

Center wavelength (channels)

OM5100/5200 DWDM-CPL

Band # Channel #

CPL 100 GHz Group #

Channel #

CPL 50 GHz Group #

Channel #

CPL 100 GHz CMD44

Channel #

CPL 50 GHz CMD44

Channel #

Band # Ch # Group # Ch # Group # Ch # Ch # Ch #

1530.33 nm1530.72 nm1531.12 nm1531.51 nm1531.90 nm1532.29 nm1532.68 nm1533.07 nm1533.47 nm1533.86 nm

1 15263748910

1 1-2-3-4---

1 12345678--

1-2-3-4-5-

12345678910


2 15263748910

2 1-2-3-4---

2 12345678--

6-7-8-9-10-

11121314151617181920


3 15263748910

3 1-2-3-4---

3 12345678--

11-12-13-14-15-

21222324252627282930






4 15263748910

4 1-2-3-4---

4 12345678--

16-

17-

18-

19-

20-

31323334353637383940


5 15263748910

5 1-2-3-4---

5 12345678--

21-

22-

23-

24-

25-

41424344454647484950


6 15263748910

6 1-2-3-4---

6 12345678--

26-

27-

28-

29-

30-

51525354555657585960

Table 3-6 (continued)OM5100/5200 and CPL 100 GHz and 50 GHz wavelength plans



Band # Channel #

CPL 100 GHz Group #

Channel #

CPL 50 GHz Group #

Channel #

CPL 100 GHz CMD44

Channel #

CPL 50 GHz CMD44

Channel #






Network management requirementsThe Common Photonic Layer uses Internet protocol (IP) communications across the OSC physical layer for internal site-to-site communications and open shortest path first (OSPF) routing protocol standard within that network. Single or Dual Gateway Network Elements may be used for communications between the Common Photonic Layer network and the OS and/or Element Management System.


7 15263748910

7 1-2-3-4---

7 12345678--

31-

32-

33-

34-

35-

61626364656667686970


8 15263748910

8 1-2-3-4---

8 12345678--

36-

37-

38-

39-

40-

71727374757677787980

1562.23 nm1562.64 nm1563.05 nm1563.45 nm1563.86 nm1564.27 nm1564.68 nm1565.09 nm

9 15263748

9 1-2-3-4-

9 12345678

41-

42-

43-

44-

8182838485868788

Table 3-6 (continued)OM5100/5200 and CPL 100 GHz and 50 GHz wavelength plans



Band # Channel #

CPL 100 GHz Group #

Channel #

CPL 50 GHz Group #

Channel #

CPL 100 GHz CMD44

Channel #

CPL 50 GHz CMD44

Channel #






For network element to OS communications, TL1 over IP is the primary application layer protocol supported with SNMP support (see SNMP support on page 3-35).

At higher levels, the Nortel Optical Manager Element Adapter (OMEA) is recommended as the element manager for the Common Photonic Layer network elements when the Nortel management system, Optical Network Manager (ONM), is used. With ONM and OMEA, the user has complete reach-through access to the Common Photonic Layer Craft interface through the OMEA server.

Figure 3-27 shows the network management systems for a typical Common Photonic Layer Craft network.

Figure 3-27Network management systems for a typical Common Photonic Layer network

NorthboundInterface (XDR)

SouthboundInterface

(TL1 and RADIUS)

NetworkElements

Ele

men

t Man

agem

ent L

ayer

OpticalNetworkManager

OpticalManagerElementAdapter





Network management softwareThe Common Photonic Layer operates with the network management software releases shown in Table 3-7.

SNMP supportThis section provides the operations, administration, maintenance and provisioning (OAM&P) description for SNMP.

To provision and manage the different applications on Common Photonic Layer, the following applications can be used:

• Craft Interface on page 3-35

• Simple Network Management Protocol on page 3-35

Craft InterfaceThe Common Photonic Layer Site Manager SNMP application is used to enable/disable the SNMP agent running on the shelf processor and to provision and manage registered trap receivers. Starting in Common Photonic Layer Release 4.0, the SNMP application can also be used to edit/reset the default SNMP community names.

SNMP operations (GET, GETNEXT, GETBULK, SET) can also be performed through any MIB Browser. For more information on the supported MIBs, see “Simple Network Management Protocol” on page 3-35.

Simple Network Management ProtocolThe Simple Network Management Protocol (SNMP) is an application-layer protocol that provides a way to monitor and manage networking devices. In an SNMP network, a management station, the Network Management Station (NMS) (also known as the SNMP Manager) sends SET or GET messages to a networking device (known as the SNMP agent). The messages allow the NMS to change or retrieve fields in the agent’s database of networking information, known as a Management Information Base (MIB).

Table 3-7Network management software releases compatible with Common Photonic Layer Release 4.0

Network management software Release

Optical Solution Release (OSR) 15.0

Optical Manager Element Adapter (OMEA) 8.0

Network and Service Viewer (NSV) 5.0

TeleManagement Forum (TMF) 814 8.0

Optical Service Provisioner (OSP) 8.0





The NMS can be any PC or workstation running SNMP management software. An SNMP agent can be any networking device containing SNMP client software. Figure 3-28 illustrates the basic architecture of an SNMP Management System (NMS) and an SNMP Managed System (SNMP Agent).

Figure 3-28SNMP management and managed systems

The simple network management protocol (SNMP) interface of Common Photonic Layer supports SNMP Version 1 (SNMP v1) and SNMP Version 2c (SNMP v2c) functionality including:

• user datagram protocol (UDP)-based communication with an NMS

• access based on read-only and read-write communities

• the processing of SNMP v1 and v2c message formats and protocol data units (PDU)

• enabling/disabling of the SNMP agent

• northbound SNMP functionality that can be enabled/disabled through trap receiver provisioning

• GET, GETNEXT, GETBULK and limited SET SNMP operations

• the generation of generic SNMP v1 or v2c traps (by default, v2c traps are generated)

Comms network

SNMP messages

SNMP managementsystem

Managementapplication

NMS (aka SNMP Manager)

UDP

Get

IP

Link

Applicationmanages objects

Set

Eve

nt

Get

-Nex

t

Get

-R

espo

nse

SNMP managementsystem

SNMO managedobjects

SNMP agent

UDP

Get

IP

Link

Set

Eve

nt

Get

-Nex

t

Get

-R

espo

nse





• SNMP traps (v1 or v2c; defaults to v2c) for all Common Photonic Layer network element critical, major, minor, warning, message alarms (including non data related alarms)

• alarm retrieval capabilities and filtering capabilities, through the use of the alarmActive, alarmClear and alarmModel tables of the Alarm MIB

— includes the retrieval of the Gauge TCA Summary alarm generated on a Common Photonic Layer NE. This summary alarm is generated in response to individual PM TCA events

• optical layer performance monitoring data retrieval through Nortel Optical PM MIB (five supported tables described in Table 3-10 on page 3-46)

• provisioned equipment and circuit pack inventory retrieval and equipment insertion and removal notification through the Entity MIB

• standard set of SNMP MIBs for configuring the Common Photonic Layer SNMP agent

• Site Manager SNMP application.

By default (that is, when a node has undergone system lineup and testing [SLAT]) there are several communities created (such as ‘public’ with read-only access and ‘sysadmin’ with read/write access). The ‘sysadmin’ read/write community can be used as the admin community through which the system administrator configures the SNMP agent by specifying the following:

• trap generation version (v1 or v2c, defaults to v2c)

• trap generation community name (defaults to sysadmin)

• system description information (for example, system description and system location)

To support SNMP, Site Manager includes the SNMP application which can be used to enable/disable the SNMP agent running on the network element and to manage the trap receiver list. Starting in Common Photonic Layer Release 4.0, the SNMP application can also be used to edit/reset the default SNMP community names.

SNMP access and SNMP agentFrom an SNMP point of view, the Common Photonic Layer GMD, UOSC or DOSC module is the SNMP agent. SNMP access is performed through the GMD, DOSC and UOSC and the externally visible IP address assigned at commissioning time (for example, Shelf IP, COLAN IP) is the IP address to be used for SNMP requests. Port 161 is used on the shelf processor to access the SNMP Agent.





The Common Photonic Layer SNMP agent supports both SNMP version 1 and version 2c. The Agent supports the following SNMP operations:

• GET

• GETNEXT

• GETBULK

• SET (see MIB compliancy on page 3-44 for more details on supported SET operations)

By default, the SNMP agent is disabled and can be enabled using the Site Manager Configuration -> SNMP application menu option. For more details on how to enable the SNMP agent, refer to Configuration, 323-1661-310.

SNMP securityAccess to Management Information Base (MIB) objects is performed using community strings. Community strings are available for all SNMP versions and are essentially a user ID without a password. The community strings are included in the SNMP messages the agent receives. The agent only replies to SNMP messages having valid community strings and rejects invalid ones.

Table 3-8 on page 3-39 provides a list of the supported default community strings.

On Common Photonic Layer network elements that are upgraded from an earlier release (2.01 or earlier), only the sysadmin and public communities are present on the network elements. New SNMP communities are not added over a network element upgrade as that would be a security risk. Contact Nortel support if the new communities available in the release are required to be added to an network element that was upgraded from an older release.

Attention: Nortel recommends that the administrator change all community strings to non-default values to secure the network element.

Do not change the SNMP Community Security names (you must only change the SNMP community name values).

It is recommended that the sysadmin SNMP community name never be deleted to prevent being locked out of the network element. Starting with Common Photonic Layer Release 4.0, the default communities can be manually reset on the node should the lockout happen.

See MIB compliancy on page 3-44 to get a complete of list of supported MIBs.





SNMP agent configurationThe sysadmin community is the SNMP community used by a system administrator to configure the Common Photonic Layer SNMP agent by specifying the following:

• trap generation version (v1 or v2c; defaults to v2c)

• trap generation community name (defaults to sysadmin)

• system description information (for example, system description and system location)

It is highly recommended to perform an NE database backup before changing the SNMP agent configuration.

Table 3-8Default community strings

Default SNMP communityname value

Read access to MIB groups

Write access to MIB groups

Community security name

sysadmin All (Note 1) All (Note 1) sysadmin

operator Exclude security Exclude security operator

observer Exclude security None observer

customer1 Exclude security and trap destinations

None customer1

customer2 Exclude security, PMs and trap destinations Include only

None customer2

public Include only RFC1213 system group

None public

Note 1: All includes: Everything below “internet” (OID .1.3.6.1)

Note 2: Security excludes:SNMP-USER-BASED-SM-MIB -> snmpUsmMIB (OID .1.3.6.1.6.3.15)SNMP-VIEW-BASED-ACM-MIB -> snmpVacmMIB (OID .1.3.6.1.6.3.16)SNMP-COMMUNITY-MIB -> snmpCommunityMIB (OID .1.3.6.1.6.3.18)

Note 3: Security includes:SNMP-COMMUNITY-MIB -> snmpCommunityMIB -> snmpTargetAddrExtTable (OID .1.3.6.1.6.3.18.1.2)

Note 4: Trap destinations additionally excludes:SNMP-TARGET-MIB -> snmpTargetMIB (OID .1.3.6.1.6.3.12)SNMP-NOTIFICATION-MIB -> snmpNotificationMIB (OID .1.3.6.1.6.3.13)SNMP-COMMUNITY-MIB -> snmpCommunityMIB -> snmpTargetAddrExtTable (OID .1.3.6.1.6.3.18.1.2)

Note 5: PM groups additionally excludes:NORTEL-OPTICAL-PM-MIB -> nnOpticalPmMIB (OID .1.3.6.1.4.1.562.68.10.1)





SNMP trapsSNMP trap generation is supported on Common Photonic Layer. An SNMP trap is a message that the SNMP agent automatically transmits to the NMS. The message notifies the NMS of an event on the managed device. The NMS can be configured to trigger an operation when it receives an SNMP trap.

Each eight trap destinations can be sent a particular SNMP trap version and community name. Default is SNMPv2c and sysadmin for all.

There are two groups of traps:

• SNMP standard MIB traps:

— SNMP generic traps: coldStart, and authenticationFailure are supported in the current release

— SNMP entConfigChange trap

• Nortel proprietary MIB traps (NORTEL-ALARM-EXT-MIB):

— Nortel alarm traps: every Critical, Major, Minor, and Warming alarm raised on the Common Photonic Layer platform triggers the generation of an SNMP trap. Clear traps are also sent when these Nortel alarm traps clear.

— Nortel Threshold Crossing Alerts (TCA) traps: PM TCAs are sent as traps and displayed as messages on the NMS.

— Nortel database change traps: Database changes on the Common Photonic Layer trigger the generation of an SNMP trap and are displayed as messages on the NMS.

Trap receiversOn Common Photonic Layer, traps are sent to all registered trap receivers. Registered trap receivers can be defined through the Site Manager SNMP -> Trap Destinations application, which is the preferred method.

Common Photonic Layer supports up to eight different registered SNMP trap receivers. Registered trap receivers must use a community that has trap notification access. Default is sysadmin. For more details on how to add, edit, or delete registered trap receivers using Common Photonic Layer, refer to Configuration, 323-1661-310.

Active and cleared alarmsThe Alarm MIB (alarmActive and alarmClear tables) can be used by the NMS to retrieve active and recently cleared Nortel alarm traps. A maximum of 1000 active alarms and 300 cleared alarms are supported.

The SNMP alarmActiveEngineAddress field in the SNMP alarmActiveTable gives the IP address of the NE against which an alarms is active. SNMP alarms for remote network elements in a GNE (redundant NAT) configuration





are represented by their private IP address instead of the expected public IP address. Therefore, it is good practice to keep all private IP addresses unique within an enterprise, so that they can be readily cross-referenced to determine their corresponding public IP address.

When you retrieve the SNMP alarmActiveTable, the alarmActiveEngineAddress field contains a private IP when it is associated with an NE which is configured behind a GNE (redundant NAT). This IP cannot be used to directly connect to the NE in question. Also, private IPs do not have to be unique within an enterprise, so care must be taken if using the private IP to identify the NE in question (keep IP addresses unique).

SNMP trap enabling and filteringThe current release provides the following trap enabling and filtering functionality:

• SNMP standard trap enabling:

The authenticationFailure standard trap can be enabled/disabled through the use of the snmpEnableAuthenTrap MIB object defined in RFC1213. All other SNMP standard traps (coldStart and entConfigChange) are always enabled and cannot be disabled.

The above standard traps (authenticationFailure, coldStart, and entConfigChange) can also be filtered using the snmpNotification MIB (snmpNotifyFilterProfileTable and snmpNotifyFilterTable tables), as per RFC2573.

• Nortel proprietary alarm trap filtering:

Traps generated from TL1/Site Manager based alarms can be filtered out (no traps are generated) using the alarmModel table of the Alarm MIB. The SNMP alarm trap filtering is distinct and independent from TL1/Site Manager based alarm filtering: SNMP filters are not reflected in TL1/Site Manager and vice versa.

Filtering can also be done based on alarm severity (Critical, Major, Minor) using the snmpNotification MIB (snmpNotifyFilterProfileTable and snmpNotifyFilterTable tables), as per RFC2573.

• SNMP source IP filtering

SNMP source IP filtering cannot be used on remote network elements (RNE) in the redundant NAT configuration. SNMP source IP filtering is used to prevent all but a specified set of NMS's from communicating with the SNMP agent on an NE. Since NMS source IPs do not reach RNEs (they are changed by the GNE en route), the source IP filtering feature is unavailable to RNEs.





Provisioned equipment and circuit pack inventory retrievalProvisioned equipment and circuit pack inventory in the shelf can be retrieved through the use of the Entity MIB.

The Entity MIB allows inventory retrieval for the GMD/UOSC/DOSC shelf processor (logical slot 4), and subtending modules (slots 1-3, 5-15, and 20-23) inserted in the shelf.

Provisioned equipment is also populated in the Entity MIB, even if the module is not present/inserted in the shelf.

Shelf wide index schemesIn Common Photonic Layer, shelf wide numbering schemes are used to uniquely identify a piece of equipment in the shelf. Two shelf wide instance numbering schemes are used in the Nortel Optical PmifIndex set (nnOpticalPmRecentIfIndex, nnOpticalPmUntIfIndex, nnOpticalPmBaslnIfIndex, nnOpticalPm15MinIfIndex, and nnOpticalPmDayIfIndex) and the Entity MIB (entPhysicalIndex).

Figure 3-29 shows a graphical representation of the generic PmifIndex and entPhysicalIndex numbering schemes.

Figure 3-29Generic PmifIndex and entPhysicalIndex formats

In Common Photonic Layer, the SNMP Index parameter of the Equipment and Facility applications represent the entPhysicalIndex values.

PmifIndex

0 0 0 1

sign (1 bit)ifIndex version (3 bits)

X X X X X

Interface Type (5 bits)

X X X X X X X

Port (7 bits)

X X X X X X X

Slot (7 bits)

X X X X X X X XX X X

Wavelength (7 bits)WavelengthPlan

(2 bits)

entPhysicalIndex

0

sign (1 bit)Version (3 bits)

Reserved (3 bits)

X

Container (1 bit)

X X X X X X

Shelf (6 bits)

X X X X X X XX X X X X X

Slot (7 bits)

X X X X X X X X X X X

Port (11 bits)





PmifIndex formatThis generic PmifIndex format is based on a signed 32-bit integer, which is divided in the following fields:

• Sign bit: Always set to 0 in the current release.

• ifIndex version bits: Always set to 100 in the current release.

• Slot #: Identifies the slot number. Can take any value from 1 to 127.

• Port #: Identifies the port number within the module. Can take any value from 1 to 127.

• Wavelength Plan - 02 for the C-Band

• Wavelength - Identifies the C-Band wavelength supported on the 50 GHz grid. Can take on any value from 1 to 88.

• Interface type bits: Identifies which type of Common Photonic Layer facility is being referenced

— IF_OPTMON 01101 (decimal 13)

— IF_VOA 01110 (decimal 14)

— IF_AMP 01111 (decimal 15)

— IF_CHMON 10000 (decimal 16)

— IF_OSC 10001 (decimal 17)

— IF_CHC 10010 (decimal 18)

— IF_RAMAN 10110 (decimal 22)

entPhysicalIndex formatThis entPhysicalIndex format is based on a signed 32-bit integer, which is divided in the following fields:

• Sign bit: Always set to 0 in the current release.

• Version bits: Set to 001 for Common Photonic Layer Release 3.2.

• Reserved bits: Always set to 000 in the current release.

• Container bit: Used to distinguish between a slot (applicable to Common Photonic Layer) or a physical piece of equipment, such as a circuit pack or pluggable optical module, for example, SFP (not applicable to Common Photonic Layer):

— Slot identification: container=1

• Shelf #: Indicates the shelf number. Can take any value from 1 to 20.

• Slot #: Indicates the slot number. Can take any value from 1 to 15, 20-23.

• Facility #: Identifies the port number within the module. Can take any value from 1 to 128.





MIB compliancyThe Management Information Bases consist of both standard MIBs as well as proprietary enterprise MIBs.

Supported standard MIBs are defined in a series of Request For Comments (RFC), see Table 3-9 on page 3-44. The list of supported SET operation capabilities is also available in Table 3-9 on page 3-44. Standard MIBs can be retrieved directly from the NMS or from the following web sites:

• IETF Standards location: http://www.simpleweb.org

• MIB depot location: http://www.mibdepot.com

Proprietary MIBs are covered by the Enterprise MIB. The enterprise object identifier (OID) designation for Nortel is 562 and as such the proprietary MIBs appear under the subtree iso(1).org(3).dod(6).internet(1).private(4).enterprise(1).nortel(562).

Table 3-10 on page 3-46 provides a list of the supported Nortel proprietary MIBs. Figure 3-30 on page 3-47 shows a screen capture of a MIB Browser, with highlights on the supported MIBs applicable to Common Photonic Layer.

Table 3-9Standard MIBs supported on Common Photonic Layer

MIB name RFC number Description

RFC1213-MIB RFC1213 Provides generic system information like system name, description and location. The sysContact, sysName, and sysLocation objects can be modified by the use of the SET operation.

Only the system and snmp groups (snmp group provides SNMP statistics from the SNMP agent) are supported.

ENTITY-MIB RFC2737 Used to get inventory information from the shelf (circuit packs, pluggable optical modules). The entityPhysical, entityGeneral and entityMIBTraps groups are supported.

The entPhysicalSerialNum, entPhysicalAlias, and entPhysicalAssetID objects, although defined as writable, do not support SET operations in the current release.

ALARM-MIB RFC3877 Used when generating traps to the registered trap receivers. The alarmNotifications, alarmActive, alarmClear groups are supported. AlarmModelEntry items can be added/deleted by the use of the SET operation.

The alarmClearMaximum object from the AlarmClearTable, although defined as writable, does not support SET operations in the current release.





SNMPv2-MIB RFC1213 Provides SNMP generic traps.

SNMP-FRAMEWORK-MIB RFC2571 Provides basic information on the snmp engine status running on the shelf processor. For example, the maximum length of the received snmp packet and the number of re-initializations the snmp engine went through. The snmpEngine group is supported.

SNMP-TARGET-MIB RFC2573 Provides registered trap receiver information.

SNMP-NOTIFICATION-MIB RFC2573 Provides registered trap receiver information.

SNMP-COMMUNITY-MIB RFC2576 Provides snmp security provisioning functionality. The SnmpCommunity MIB is used to query, create and delete community strings on the SNMP agent.

On Common Photonic Layer network elements that are upgraded from an earlier release (2.01 or earlier), only the sysadmin and public communities are present on the network elements. New SNMP communities (customer1, customer2, observer, operator) are not added over a network element upgrade as that would be a security risk. Contact Nortel support if the new communities available in the release are required to be added to an network element that was upgraded from an older release.

SNMP-MPD-MIB RFC2572 Provides information on message processing and dispatching.

SNMP-USER-BASED-SM-MIB

RFC2574 Provides SNMP security information, for example, description errors, unsupported security levels.

As per RFC2574, this MIB is used solely for the purpose of setting up SNMP v3 user-based security elements. As SNMP v3 is not yet supported, this MIB is accessible but not used in the current release.

SNMP-VIEW-BASED-ACM-MIB

RFC2575 Allows configuration of access control policy for the different communities. Individual MIBs and/or MIB subtrees can be included or excluded from the different access list so that access is restricted on a per community basis.

Table 3-9 (continued)Standard MIBs supported on Common Photonic Layer

MIB name RFC number Description





In Figure 3-30, the SnmpFramework MIB, SnmpCommunity MIB, SnmpTarget MIB, SnmpNotification MIB, SnmpUsm MIB, SnmpMDnPstats MIB, and SnmpVacm MIB are all found under:

.iso.org.dod.internet.snmpV2 (.1.3.6.1.6).

Table 3-10Proprietary MIBs supported on Common Photonic Layer

MIB name Description

NORTEL-MIB (1.3.6.1.4.1.562)

Represents the Nortel top-level MIB definition.

NORTEL-GENERIC-MIB(1.3.6.1.4.1.562.29)

Represents the top-level MIB branch for some of the generic MIBs that are common to Nortel products.

NORTEL-ENTITY-VENDORTYPE-MIB (1.3.6.1.4.1.562.29.5)

Describes Nortel vendor type identifiers for use with the Entity MIB's entPhysicalVendorType.

NORTEL-ALARM-EXT-MIB (1.3.6.1.4.1.562.29.6)

Provides detailed Nortel specific notifications as well as additional alarm information that complements the standard Alarm MIB.

NORTEL-OPTICAL-GENERIC-MIB

(1.3.6.1.4.1.562.68.10)

Represents the top-level MIB branch for some of the generic optical MIBs that are common to Nortel optical products.

NORTEL-OPTICAL-PM-MIB(1.3.6.1.4.1.562.68.10.1)

Represents the Nortel proprietary MIB for Nortel optical SNMP PM retrieval.

Five tables on which SNMP PM data retrieval requests can be performed are supported:

• nnOpticalPmRecentTable (Nortel Optical Recent PM table)

• nnOpticalPmUntTable (Nortel Optical Untimed PM table)

• nnOpticalPmBaslnTable (Nortel Optical Baseline PM table)

• nnOpticalPm15MinTable (Nortel Optical 15 Minute PM table)

• nnOpticalPmDayTable (Nortel Optical Day PM table)

The 15 Min PM table is large and can be very large on full fill systems.

CHMON facilities support current 15-min, and current day PM information. Retrieve 15-min date for the CHMON facility from nnOpticalPm15MinTable and current day data from nnOpticalPmDayTable. CHMON data is not available from nnOpticalPmRecentTable.

Note: With the exception of NORTEL-OPTICAL-PM-MIB, there are no retrieval data fields in the Nortel proprietary MIBs. These MIBs are only used by the Site Manager MIB Browser or any trap viewer for MIB information decoding.





Figure 3-30MIB browser example—supported MIBs (entityMIB and alarmMIB expanded)





Figure 3-31 shows the supported MIBs with the nnOpticalPm MIB expanded.

Figure 3-31MIB browser example—supported MIBs (nnOpticalPmMIB expanded)

Access to Nortel proprietary MIBsNortel proprietary MIBs can be downloaded directly from the Common Photonic Layer network element:

1 In an Internet Browser, enter the following address and hit return:

http://<ipAddress>where the ipAddress is the COLAN or Shelf IP of the Common Photonic Layer NE

2 In the Common Photonic Layer homepage, click on the download SNMP MIBs Definitions link to download the MIB structures.





3 The mibfiles.tar.gz file contains the following files:

— NORTEL-MIB

— NORTEL-GENERIC-MIB

— NORTEL-ENTITY-VENDORTYPE-MIB

— NORTEL-ALARM-EXT-MIB

— NORTEL-OPTICAL-GENERIC-MIB

— NORTEL-OPTICAL-PM-MIB

— NORTEL-RPR-MIB (does not apply to CPL)

— NORTEL-TM-MIB (does not apply to CPL)

— NortelOpticalMibBundle

— NORTEL-OPTICAL-CPL-MIB

— NORTEL-OPTICAL-OME6500-MIB (does not apply to CPL)

— S5-ETH-MULTISEG-TOPOLOGY-MIB (does not apply to CPL)

— S5-ROOT-MIB (does not apply to CPL)

— SYNOPTICS-ROOT-MIB (does not apply to CPL)

— NORTEL-OME40G-MIB (does not apply to CPL)

— NORTEL-OME40G-CNXN-MIB (does not apply to CPL)

— NORTEL-OME40G-FAC-MIB (does not apply to CPL)

— NORTEL-OME40G-PM-PROV-MIB (does not apply to CPL)

— NORTEL-OME40G-OM-COUNTS-MIB (does not apply to CPL)

— NORTEL-OME40G-PRTN-MIB (does not apply to CPL)

— NORTEL-OME6500-ALARMS-MIB (does not apply to CPL)

— NORTEL-OME6500-EQPT-MIB (does not apply to CPL)

— NORTEL-OME6500-SHELF-PARAMS-MIB (does not apply to CPL)

— NortelSMIMibBundle (does not apply to CPL)

— version.txt

The Nortel MIB files are to be loaded in the NMS to get access to the Nortel specific alarms/entities. The NortelOpticalMIBBundle contains all Nortel MIBs and provides easy loading access to all MIBs at once. It is important to only load one or the other (the bundle file or all individual MIB files).

The Nortel MIBs alone are not sufficient to get the SNMP functionality. Other (standard) MIBs are also required to be loaded to the NMS. See Table 3-11 on page 3-50 for the complete list and loading order.





MIB loading orderDepending on which NMS is used, different standard MIBs can be present/loaded by default. In order to fully support all of the SNMP features available in the current release, the standard MIBs must be loaded on the NMS (includes standard and Nortel proprietary MIBs).

Table 3-11 on page 3-50 gives the suggested loading order for all required MIBs.

Table 3-11Suggested MIBs loading order

Standard MIBs (Note 1, Note 2) - to be loaded before the Nortel MIBs:

— SNMPv2-SMI (RFC 1442/1902/2578) (Note 3)

— SNMPv2-TC (RFC 2579) (Note 3)

— SNMPv2-MIB (RFC 1907) (Note 3)

— SNMPv2-TM (RFC 1906) (Note 3)

— IANAifType-MIB (RFC 1573) (Note 3)

— RFC1213-MIB (RFC 1158/1213) (Note 3)

— IF-MIB (RFC 2863)

— SNMP-FRAMEWORK-MIB (RFC 2571)

— SNMP-TARGET-MIB (RFC 2573)

— SNMP-NOTIFICATION-MIB (RFC 2573)

— SNMP-COMMUNITY-MIB (RFC2576)

— SNMP-MPD-MIB (RFC 2572)

— SNMP-USER-BASED-SM-MIB (RFC 2574) (Note 4)

— SNMP-VIEW-BASED-ACM-MIB (RFC 2575)

— INET-ADDRESS-MIB (RFC 2851) (Note 3)

— ENTITY-MIB (RFC 2737)

— IANA-ITU-ALARM-TC-MIB (RFC 3877) (Note 3)

— ITU-ALARM-TC-MIB (RFC 3877) (Note 3)

— RFC1271-MIB (RFC 1271) (Note 3)

— RMON-MIB (RFC 1271) (Note 3)

— TOKEN-RING-RMON-MIB (RFC 1271) (Note 3)

— RMON2-MIB (RFC 2021) (Note 3)

— ALARM-MIB (RFC 3877)

— ITU-ALARM-MIB (RFC 3877) (Note 3)

— NOTIFICATION-LOG-MIB (RFC 3014) (Note 3)

— HC-PerfHist-TC-MIB (RFC3705) (Note 3 and Note 5)

— IEEE-802DOT17-RPR-MIB (Note 5)





Nortel MIBs—to be loaded after the standard MIBs:

— NORTEL-MIB

— NORTEL-GENERIC-MIB

— NORTEL-ENTITY-VENDORTYPE-MIB

— NORTEL-ALARM-EXT-MIB

— NORTEL-OPTICAL-GENERIC-MIB

— NORTEL-OPTICAL-OME6500-MIB (Note 5)

— NORTEL-OPTICAL-CPL-MIB

— NORTEL-OPTICAL-PM-MIB

— NORTEL-RPR-MIB (Note 5)

— NORTEL-TM-MIB (Note 5)

— NORTEL-OME6500-SHELF-PARAMS-MIB (Note 5)

— NORTEL-OME6500-EQPT-MIB (Note 5)

— NORTEL-OME40G-MIB (Note 5)

— NORTEL-OME40G-FAC-MIB (Note 5)

— NORTEL-OME40G-CNXN-MIB (Note 5)

— NORTEL-OME40G-PRTN-MIB (Note 5)

— NORTEL-OME40G-PM-PROV-MIB (Note 5)

— NORTEL-OME40G-OM-COUNTS-MIB (Note 5)

— NORTEL-OME6500-ALARM-MIB (Note 5)

— SYNOPTICS-ROOT-MIB (Note 5)

— S5-ROOT-MIB (Note 5)

— S5-ETH-MULTISEG-TOPOLOGY-MIB (Note 5)

Note 1: Please note that MIB browsers differ in their MIB loading behaviors. After using the above load order, validation of the intended MIB set is recommended.

Note 2: If MIBs are pre-loaded by default in a MIB Browser, the pre-loaded MIBs can be left loaded and the suggested MIB loading order should only be followed for the missing MIBs.

Note 3: The list of MIBs above are required as import dependencies only. Presence in this load order does not imply full support for the MIB. Please refer to Table 3-9 on page 3-44 and Table 3-10 on page 3-46 for the list of supported MIBs

Note 4: As per RFC2574, this MIB is used solely for the purpose of setting up SNMP v3 user-based security elements. As SNMP v3 is not yet supported, this MIB is accessible but not used in the current release.

Note 5: Not supported or required in Common Photonic Layer.

Table 3-11 (continued)Suggested MIBs loading order





SNMP—supported features in this release The SNMP functionality supported by this release of Common Photonic Layer consists of:

• retrieval active and cleared alarms on a shelf

• alarm filtering

• retrieval of shelf inventory and notification of inventory addition/removal (autonomous reporting)

• generation of traps for NE alarms and PM TCAs

• retrieval of PMs for circuit pack interfaces

Alarm retrieval This release of Common Photonic Layer supports:

• the retrieval of alarms through the SNMP GET operation on tables defined in the standard Alarm Management Information Base (MIB) (RFC 3877)

— retrieval through GET and GETNEXT operations on entire rows (all column objects) or partial rows (subset of all column objects) of the alarm tables.

— alarm tables are indexed by active/cleared alarm timestamp and active/cleared instance number

• the retrieval of active Common Photonic Layer alarms through SNMP GET operations on the rows of the active alarm table (alarmActiveTable) in the Alarm MIB

— each row contains information from a trap generated for an Common Photonic Layer alarm

— a row added when a trap for an Common Photonic Layer alarm is raised

— a row removed when the clear trap for the active alarm is generated

• retrieval of cleared Common Photonic Layer alarms through SNMP GET operations on the rows cleared alarm table (alarmClearTable) in the Alarm MIB

— each row contains information from a trap generated for an Common Photonic Layer alarm clearing

— a row is added when a trap for an alarm clearing is generated

— the alarm clear table will contain the last 300 alarms that were cleared

The alarmActiveStatsTable is also used to display the current number of active alarms, the cumulative number of alarms that have been active since the last agent restart, the sysUpTime when the last alarm was raised, and the sysUpTime when the last alarm was cleared.





Alarm filtering This release of Common Photonic Layer supports:

• filtering of Common Photonic Layer alarm traps via the alarm model table(alarmModelTable) in the Alarm MIB (RFC 3877)

— each row contains the reference (non-instance) data for an Common Photonic Layer alarm type (for example circuit pack missing, Loss of Signal)

— at system installation there is a row for each supported Common Photonic Layer alarm type

— a trap for an Common Photonic Layer alarm type is filtered based on the existence of its row in the model table

• end-user provisioning of filters for Common Photonic Layer alarm traps through the alarm model table (alarmModelTable) in the Alarm MIB

— end-user removal of an alarm model table row through SNMP SET operation with deletion row status

— end-user addition of an alarm model table row through SNMP SET operation with creation row status

Inventory retrieval This release of Common Photonic Layer supports:

• retrieval of Common Photonic Layer inventory through the physical entity table (entityPhysicalTable) in the Entity MIB (2737)

— retrieval through GET and GETNEXT operations on entire rows (all column objects) or partial rows (subset of all column objects) of the entity table

— each row contains information describing a distinct piece of inventory (Common Photonic Layer circuit pack in the slot of an Common Photonic Layer shelf)

— table indexed by inventory instance number which is an encoding of the shelf, slot and port where the inventory is located in the Common Photonic Layer shelf

— row added when a piece of inventory is added to an Common Photonic Layer shelf

— row removed when a piece of inventory is removed from an Common Photonic Layer shelf

• notification of Common Photonic Layer inventory addition and removal using the entity configuration change trap(entConfigChange) of the Entity MIB

— a trap is generated when a piece of inventory is either added to or removed from an Common Photonic Layer shelf and when it provisioned or deleted





PM retrieval through the Nortel Optical PM MIBThis release of Common Photonic Layer supports:

• recent PMs (current and previous 15 minute, current and previous day) from nnOpticalPmRecent table with 2 indexes; If index and PM montype

• untimed PMs from nnOpticalPmUnt table with 2 indexes; If index and PM montype

• baseline PMs from nnOpticalPmBasln table with 2 indexes; If index and PM montype

• historical 15 Minute PMs from nnOpticalPm15Min table with 3 indexes; If index, 15 minute interval index, and PM montype (0 being the current 15 minute interval and 1-32 being the previous 15 minute intervals)

• historical Day PMs from nnOpticalPmDay table with 3 indexes; If index, day interval index, and PM montype (0 being the current day interval and 1 being the previous day interval)




4-1

Hardware description 4-

This chapter provides an overview of the Common Photonic Layer hardware. Table 4-1 lists the topics in this chapter.


Topic Page

Common Photonic Layer frame 4-2

Enclosing the Common Photonic Layer frame 4-5

Multi-slot carriers 4-5

Group Mux/Demux (GMD) module (NTT801AA-BA) 4-9

Dual Optical Service Channel (DOSC) module (NTT839AA) 4-16

Uni Optical Service Channel (UOSC) module (NTT839BA) 4-21

4 Channel Mux/Demux (CMD4) module (NTT810BA-BH, BJ) 4-25

44 Channel Mux/Demux C-Band (CMD44) module (NTT862AA/BA/BB/FAE5)

4-29

Serial 4 Channel Mux/Demux (SCMD4) module (NTT810CA-CH, CJ) 4-39

Serial 8 Channel Mux/Demux (SCMD8) module - Filtered SCMD8 (NTT861AA-AH, AJ) and Open SCMD8 (NTT861BA-BH, BJ)

4-44

Broadband Mux/Demux 1x2 (NTT862DAE5) 4-49

Wavelength Selective Switch (WSS) module (NTT837CA, NTT837DA) 4-52

Common Photonic Layer Amplifier (NTT830xA) 4-56

Distributed Raman Amplifier (NTT831AA) 4-66

Channel Mux/Demux Amplifier (NTT832AA) 4-70

Optical Power Monitor (NTT838AA) 4-73

Breaker interface panels (BIP) 4-76




4-2 Hardware description

Common Photonic Layer frameThe standard offering for Common Photonic Layer network element installation is within the PTE2000 frame with EIA mounting. The PTE2000 frame is an ETSI frame. Adapter brackets convert the PTE2000 ETSI to EIA mounting. See Installation, 323-1661-201 for details.

The PTE2000 frames meet global footprint requirements (American National Standards Institute [ANSI], Telcordia Network Equipment Building System [NEBS], European Telecommunications Standards Institute [ETSI]) and meet NEBS Zone 4 seismic requirements. Furthermore, the PTE2000 frames support overhead and raised-floor cabling environments. Figure 4-1 shows the PTE2000 frame.

The Common Photonic Layer supports several frame sizes including:

• 19 in. and 23 in. standard Electronic Industries Alliance (EIA) frames

• extended PTE2000 equipment frames, along with adapter bracket, for standard deployments involving Nortel supplied systems

• other non-standard 19 in. frames with a minimum upright spacing of 17.5 in.

Contact Nortel if you want to install modules in 19 in. or 23 in. frames.

Fuse panels 4-80

2U AC Rectifier (NTN458SB, NTN458SC) 4-83

Fiber Manager (FM) with/without Dispersion Slope Compensation Module (DSCM)

4-84

Fiber and cable management strategy 4-88

Connector strategy 4-91

Data communication connections 4-93

Visual indicator strategy 4-93

Hardware required for interface functionality 4-93

Table 4-1 (continued)Topics in this chapter

Topic Page




Hardware description 4-3

Figure 4-1PTE2000 frame

598 mm(23.54 in.)

502 mm(19.76 in.)

1969.5 mm(77.54 in.)

2119.6 mm(83.45 in.)

300 mm(11.81 in.)

Note:598 mm (23.54 in.): This dimension is the overall width of the frame.502 mm (19.76 in.): This dimension is the usable aperture betweenequipment mounting uprights.2119.6 mm (83.45 in.): This dimension does not include the levelling feet.1969.5 mm (77.54 in.): This dimension is the equipment aperture in the vertical direction.300 mm (11.81 in.): This dimension is the overall depth of the frame.44 rack units high (44U), 1U=1.75 in





Adapter brackets and 1U and 2U carriersThe Common Photonic Layer standard configuration is 19" EIA. To achieve a 5 in. setback and EIA hole spacing in a PTE2000 frame, adapter brackets are used. Carriers (1U and 2U) are attached to the adapter brackets on the frame. Carriers are used to hold the individual modules in a frame. See Figure 4-2 for an example of a carrier. Adapter brackets also provide cable and fiber management features.

Carrier upgrade kits are also available which include configurable mounting brackets to adapt mounting chassis kits to 19 in. EIA (5 in. and 6 in. setback), 23 in. EIA (5 in. and 6 in. setback), and ETSI (50 mm setback) frames.

Attention: Direct mounting in ETS 300-119-3 equipment frames (50 mm setback) is supported, but frame density is not optimal. 1U is centered on 50 mm (a loss of 5.6 mm) and 2U on 100 mm (a loss of 11.1 mm).

Figure 4-2Mounting chassis kit (2U carrier shown)





Enclosing the Common Photonic Layer frame The PTE2000 frame can be partially enclosed using the cable cover kit or fully enclosed using the cabinet skins kit.

Cable cover kitThe cable cover kit (NTT899BD) can be used to partially enclose the PTE2000 frame protecting fibers and improving aesthetics. See Installation, 323-1661-201, for the parts of this kit and how these parts are assembled.

Side panels can be ordered separately if required. Order side panel kit (NTRU0125).

Cabinet skin kit The cabinet skin kit (NTT899BE) fully encloses the PTE2000 frame. See Installation, 323-1661-201, for the parts of this kit and how these parts are assembled. The cabinet skin kit has a lockable door. The door design allows for easy installation and removal for maintenance procedures.

Multi-slot carriersThe Multi-slot carriers (MSC) are chassis that can house modules for fixed configurations.

Three types of multi-slot carriers are supported:

• Multi-slot carrier Type 1 (NTT899AQ) provides base slots for Reconfigurable OADM (ROADM) configurations. Carrier Type 1 is also used for thin terminal rack configurations using a DRA. See Figure 4-3 on page 4-6.

• Multi-slot carrier Type 2 (NTT899AR) provides base slots for line amplifier and DIA configurations (see Figure 4-4 on page 4-7).

• Multi-slot carrier Type 3 (NTT899AS) provides base slots for thin OADM (TOADM) and OADM configurations (see Figure 4-5 on page 4-7).

Multi-slot carriers provide a cost saving by integrating into a single chassis, a core module sub-set of standard supported configurations.

Labour cost savings are realized in field installation operations since installing a larger unit into an equipment rack takes less time than multiple smaller units. Additionally, for systems shipped without an equipment rack, the multi-slot carrier allows partial systems to be shipped modules-in-place and fiber-in-place.

The Multi-slot carrier is supported in all of the frames listed in Common Photonic Layer frame on page 4-2. They can be configurable for front exhaust, rear exhaust or front/rear exhaust (neutral position). All of the Multi-slot carriers have a ground bus bar to terminate a ground cable with a two holed





lug (5/8” spacing). The ground bus bar provides a single point frame ground connection that grounds all of the modules in the Multi-slot carriers simultaneously.

Figure 4-3Type 1 multi-slot carrier, 11U (NTT899AQ) for ROADM or thin terminal with DRA applications





Figure 4-4Type 2 multi-slot carrier, 6U (NTT899AR) for line amplifier and DIA configurations

Figure 4-5Type 3 multi-slot carrier, 7U (NTT899AS) for TOADM and GMD-based OADM configurations





Figure 4-6 shows the module positions for each type of multi-slot carrier.

Figure 4-6Module positions for multi-slot carriers, Type 1, Type 2 and Type 3

Type 1ROADM site or

Thin Terminal with DRA

(11U)

OPMMLA/SLA/LIM

WSS or DRA

FM/DSCMFM/DSCM

UOSC/GMD

FM(S)CMD(S)CMD

Type 2 Line Amp site

(6U)

MLA/SLA/LIM (Dir 1)MLA/SLA/LIM (Dir 2)

FM/DSCMFM/DSCM

DOSC

Type 2 DIA site

(6U)

OPMMLA/MLA2/SLA/LIM

FMFM

WSS

MLA/SLA/LIM FM/DSCM

FM

UOSC/GMD2

FM(S)CMD

Type 3 TOADM site without DRA

(7U)

Legend

(S)CMDDOSCFMFM/DSCMMLA/SLA/LIMOPMUOSC/GMDUOSC/GMD2WSSDRA

= Channel Mux/Demux or Serial Channel Mux/Demux= Dual Optical Service Channel Module= Fiber Manager= Fiber Manager/Dispersion Slope Compensation Module= Mid-Stage Line Amplifier/Single Line Amplifier/Line Interface Module= Optical Power Monitor= Uni Optical Service Channel or Group Mux/Demux= Uni Optical Service Channel or Group Mux/Demux type 2= Wavelength Selectable Switch= Distributed Raman Amplifier





Group Mux/Demux (GMD) module (NTT801AA-BA)Functional description

The Group Mux/Demux (GMD) module is a self-contained unit that provides the final wavelength multiplexing stage and interface to the amplified line system. The GMD supports all the wavelength groups (1 to 9) for the entire C-band grid. Each group is comprised of eight individual wavelengths multiplexed through the Channel Mux/Demux (CMD4, SCMD4, or SCMD8) module. The system capacity is up to 36 (100 GHz ITU grid) wavelengths or up to 72 (50 GHz ITU grid) wavelengths. Figure 4-7 provides a front view of the GMD module.

Figure 4-7GMD module front view (GMD Type 1 shown with door both open and closed)

The GMD supports optical monitoring taps and electronically-controlled variable optical attenuators (eVOA) on the input multiplexer ports. If the GMD loses power, the eVOAs settings on the mux ports are frozen and add/drop and/or pass through traffic is maintained.

Two types of GMDs are available (Type 1 and Type 2). Functionally, the two GMD types are identical, except that Type 1 has an upgrade port for future applications whereas Type 2 does not have an optical upgrade port. Figure 4-8 on page 4-10 and Figure 4-9 on page 4-11 provide functional block diagrams of the two types of GMD modules.





Figure 4-8GMD module (Type 1-NTT801AA) functionality

GMD Type 1

Group 1 In (Port 1)Group 2 In (Port 3)Group 3 In (Port 5)Group 4 In (Port 7)Group 5 In (Port 9)Group 6 In (Port 11)Group 7 In (Port 13)Group 8 In (Port 15)Group 9 In (Port 17)

Upgrade In (Port 19)

OSC In (Port 21)

Group 1 Out (Port 2)Group 2 Out (Port 4)Group 3 Out (Port 6)Group 4 Out (Port 8)Group 5 Out (Port 10)Group 6 Out (Port 12)Group 7 Out (Port 14)Group 8 Out (Port 16)Group 9 Out (Port 18)

Upgrade Out (Port 20)

OSC

Common Out (Port 23)

Common In (Port 22)

OSC Out (Port 21)

Group Muxwith Upgrade Port

Σ

Group Demuxwith Upgrade Port

Σ

= Performance monitoring portLegend





Figure 4-9GMD module (Type 2-NTT801BA) functionality

The GMD also serves as the shelf controller and provides the communications infrastructure that enables the Common Photonic Layer node to interface with other nodes, elements within the node, and the outside world. The GMD is an intelligent component of the network that stores information pertaining to network management, configuration, communication, optimization, and control. The GMD also provides standard alarms and telemetry support. The GMD can control up to nine (S)CMDs and two amplifiers.

GMD Type 2

Group 1 In (Port 1)Group 2 In (Port 3)Group 3 In (Port 5)Group 4 In (Port 7)Group 5 In (Port 9)Group 6 In (Port 11)Group 7 In (Port 13)Group 8 In (Port 15)Group 9 In (Port 17)

OSC In (Port 21)

Group 1 Out (Port 2)Group 2 Out (Port 4)Group 3 Out (Port 6)Group 4 Out (Port 8)Group 5 Out (Port 10)Group 6 Out (Port 12)Group 7 Out (Port 14)Group 8 Out (Port 16)Group 9 Out (Port 18)

Group Demux

OSC

Common Out (Port 23)

Common In (Port 22)

OSC Out (Port 21)

Group Mux






The GMD provides support for an out-of-band optical service channel (OSC), providing an Ethernet-over-SONET (EOS) communications infrastructure available for use by both the customer and the applications software of the GMD itself.

Along with all other modules of the Common Photonic Layer, the GMD fits into a PTE2000, 19 in. or 23 in. wide frame with the use of a 2U or multi-slot carrier. The module measures 2U in height. The GMD supports in-service fiber cleaning of internal facing fibers and in-service replacement of fans and air filters.

OAM&P featuresThe operations, administration, maintenance, and provisioning (OAM&P) features of the GMD are:

• network element management and communications subnet

• performance monitoring (PM) including per-band power monitoring at the ingress ports and total optical power monitoring at all common ports

• optical power control

• Transaction Language 1 (TL1) craft interface

• TL1 based remote network management interface

• TL1 gateway / northbound simple network management protocol (SNMP)

• wayside access for customer usage

• node consolidation/subnet

• alarm display, provisioning, and history

• software load management

• browser graphical user interface (GUI) craft support

• network and local optimization control

• private dynamic host configuration protocol (DHCP) address pool for subtending circuit pack presence detection

• DCN and RS-232 modem (debug) access

• network element configuration

• communications configuration

• facility access and configuration

• security control





Table 4-2GMD electrical interfaces

Interface name Number of ports Function Connector type

Modem (RS-232) 1 Serial port craft interface supporting data terminal equipment (DTE) functionality

DB9

Craft 1 Internet protocol (IP) over 10Base-T Ethernet craft interface

RJ-45 (MDI)

COLAN 1 IP over 10/100Base-T Ethernet data communications interface to the customer data network

RJ-45 (MDI-X)

WSC-1(Wayside)

1 IP over 10/100Base-T Ethernet data communications interface for unspecified use by the customer

RJ-45 (MDI-X)

Slot-n 12 IP over 10/100Base-T Ethernet data communications interface for subtending modules

RJ-45 (MDI-X)

ILAN-n 2 IP over 10/100Base-T Ethernet data communications interface for service shelves

RJ-45 (MDI-X)

DC Power 2 Dual (A/B) feed power connections per module

Molex MiniFit BMI Header 2x2

Alarm/Telemetry 1 Contact closures for interfacing with bay-level consolidated alarms (Critical, Major, and Minor)

DB25

Table 4-3GMD push buttons

Push button Function

ACO/Lamp Test Alarm Cut-Off/Lamp Test

Reset Reset module





Customer interface office alarm and PTT connectionsThe GMD provides parallel telemetry alarm connections through a DB25 connector as identified in Table 4-5.

Table 4-4GMD optical interfaces

Interface name Physical port # Function Connector type

Grp 1 In / Out

Grp 2 In / Out

Grp 3 In / Out

Grp 4 In / Out

Grp 5 In / Out

Grp 6 In / Out

Grp 7 In / Out

Grp 8 In / Out

Grp 9 In / Out

1 / 2

3 / 4

5 / 6

7 / 8

9 / 10

11 / 12

13 / 14

15 / 16

17 / 18

Dense wavelength division multiplexing (DWDM) optical input from the (S)CMD multiplexed output / DWDM optical output to the (S)CMD demultiplexed input

LC

Upgd In / Out 19 / 20 DWDM optical input / output (for future in-service upgrade)

LC

Common In / Out

22 / 23 DWDM optical input / output to the line system

LC

OSC In / Out 21 / 21 OSC channel input / output LC

Table 4-5GMD alarm interface and PTT connector pinout

Function Normally open

Common Normally closed

Other Comments

Pin number on DB25 connector

Visible alarm

Critical 2 14 1 a set of relay contacts

Major 16 3 15 a set of relay contacts

Minor 5 17 4 a set of relay contacts

Audible alarm




Parallel Telemetry Input 2

20 Shorting pins 19 and 20 causes the Parallel Telemetry Input 2 alarm to be raised.Parallel

Telemetry Input 219





Parallel Telemetry Output

6 7 8 a set of relay contacts



Telemetry Input 121

Table 4-6GMD technical specifications and engineering rules

Product Engineering Code (PEC)

• NTT801AA: GMD Type 1 with upgrade port

• NTT801BA: GMD Type 2 without upgrade port

Engineering rules • Required at all GMD Terminal or GMD based OADM sites

• Terminal: 1 per site

• OADM: 2 per site (1 per direction)

• Always located in logical slot 4

Optical specifications • Group DEMUX (in to drop) insertion loss: 7 dB (Type 1), 4 dB (Type 2)

• Group MUX (add to out) insertion loss: 7 dB (Type 1), 4 dB (Type 2)

• Group MUX/DEMUX (in to out) insertion loss: 14 dB (Type 1), 7.2 dB (Type 2)

• Each group multiplexer input has an eVOA with a 15 db range

• Optical taps on multiplexer output/demultiplexer input

Built-in OSC specifications

• 1510 nm optical interface

• Tx: 1 dBm (end-of-life [EOL])

• Rx: -36 dBm (EOL sensitivity), 0 dBm (overload)

• Maximum link budget: 34 dB

Dimensions • Depth: 10.90 in. (276.9 mm)

• Height: 3.38 in. (85.5 mm)

• Width: 15.88 in. (405.8 mm)

Weight 20 lbs (9.08 kg)

Power 45 Watts, typical

Table 4-5 (continued)GMD alarm interface and PTT connector pinout



Other Comments






Dual Optical Service Channel (DOSC) module (NTT839AA)Functional description

The Dual Optical Service Channel (DOSC) module provides the shelf controller and OSC functionality for:

• Line Amplifier sites in regional and core applications.

• ROADM and TOADM sites where the DOSC is shared between optical transmission sections (OTS). The DOSC can be shared between:

— two ROADMs

— two TOADMs

— one TOADM and one ROADM

— one ROADM and one DIA

The OSC provides a 155 Mbit/s Ethernet-over-SONET (EOS) communications infrastructure available for use by both the customer and the applications software of the DOSC itself. Figure 4-10 provides a front view of the DOSC module whereas Figure 4-11 on page 4-17 provides a functional block diagram of the DOSC module.

Figure 4-10DOSC module front view (shown with door both open and closed)





Figure 4-11DOSC module functionality

The DOSC houses the master processor, controls, and communications for all photonic layer equipment at a Line Amplifier site, ROADM/ROADM site, TOADM/TOADM site, ROADM/TOADM, or ROADM/DIA site. As a shelf controller, the DOSC (like the GMD and UOSC) is an intelligent component of the network that stores information pertaining to network management, configuration, communication, optimization and control. The DOSC also provides standard alarms and telemetry support.

The DOSC provides the following functional elements of the Common Photonic Layer architecture:

• two OSC facilities

• optical generation and termination of each OSC facility

• TL1 craft interface



• private Ethernet communications interfaces in support of subtended Amplifier modules

The DOSC module fits into a PTE2000, 19 in. or 23 in. wide frame with the use of a 2U or multi-slot carrier. The module measures 2U in height. The DOSC supports in-service fiber cleaning of internal facing fibers and in-service replacement of fans and air filters (later releases of the DOSC do not have fans).

OAM&P featuresThe OAM&P features of the DOSC are:


• total optical power monitoring at all common ports

• optical power control

• TL1 craft interface

DOSC

OSCOSC 1 In (Port 1)

OSC 1 Out (Port 1)

OSC 2 In (Port 2)

OSC 2 Out (Port 2)

OSC






• TL1 gateway / northbound SNMP



• alarm and fault correlation


• browser GUI craft support

• network and local optimization control

• private DHCP address pool for subtending circuit pack presence detection

• 10Base-T, RS-232, modem access

• visual alarm indicators




• facility access and configuration


Table 4-7DOSC electrical interfaces


Modem 1 Serial port craft interface supporting DTE functionality

DB9

Craft 1 IP over 10Base-T Ethernet craft interface RJ-45 (MDI)


RJ-45 (MDI-X)

WSC-1WSC-2Wayside)


RJ-45 (MDI-X)


RJ-45 (MDI-X)


RJ-45 (MDI-X)

DC Power 2 Dual (A/B) feed power connections per module Molex MiniFit BMI Header 2x2


DB25





Customer interface office alarm and PTT connectionsThe DOSC provides parallel telemetry alarm connections through a DB25 connector as identified in Table 4-10.

Table 4-8DOSC push buttons



Reset Reset module

Table 4-9DOSC optical interfaces


OSC 1 In / Out 1 Out-of-band (1510 nm) OSC input / output from the Amplifier, direction 1

Dual LC

OSC 2 In / Out 2 Out-of-band (1510 nm) OSC input / output to the Amplifier, direction 2

Dual LC

Table 4-10DOSC alarm interface and PTT connector pinout



Other Comments


Visible alarm




Audible alarm





20 Shorting pins 19 and 20 causes the Parallel Telemetry Input 2 alarm to be raised.


19




18 Shorting pins 18 and 21 causes the Parallel Telemetry Input 1 alarm to be raised.


21





Table 4-11DOSC technical specifications and engineering rules


NTT839AA

Engineering rules • 1 module required at Line Amplifier sites


Optical specifications

• 1510 nm optical interface

• Tx: 1 dBm (EOL)


• Maximum link budget: 34 dB


• Height: 3.38 in. (85.5 mm)

• Width: 15.88 in. (405.8 mm)







Uni Optical Service Channel (UOSC) module (NTT839BA)Functional description

The Uni Optical Service Channel (UOSC) module provides the virtual shelf controller and OSC functionality for access sites at which a GMD is not deployed (ROADM and TOADM sites). Figure 4-12 provides a front view of the UOSC module whereas Figure 4-13 provides a functional block diagram of the UOSC module.

Figure 4-12UOSC module front view (shown with door both open and closed)

Figure 4-13UOSC module functionality

UOSC

1OSC1 Out

1OSC1 InOSC1





The UOSC serves as the shelf controller and provides the communications infrastructure that enables the Common Photonic Layer node to interface with other nodes, elements within the node, and the outside world. The UOSC is an intelligent component of the network that stores information pertaining to network management, configuration, communication, optimization, and control. The UOSC also provides standard alarms and telemetry support.

The UOSC provides support for an out-of-band optical service channel (OSC), providing an Ethernet-over-SONET/SDH (EOS) communications infrastructure available for use by both the customer and the applications software of the UOSC itself.

Along with all other modules of the Common Photonic Layer, the UOSC fits into a PTE2000, 19 in. or 23 in. wide frame with the use of a 2U or multi-slot carrier. The module measures 2U in height. The UOSC supports in-service replacement of fans and air filters. The UOSC supports in-service fiber cleaning of internal facing fibers and in-service replacement of fans and air filters (later releases of the UOSC do not have fans).

OAM&P featuresThe operations, administration, maintenance and provisioning (OAM&P) features of the UOSC are:


• performance monitoring including OSC power monitoring at the input port and support for an OSC Signal Degrade Alarm

• optical domain control


• northbound simple network management protocol (SNMP)



• alarm display, provisioning, and history


• browser (java based) graphical user interface (GUI) craft support

• private dynamic host configuration protocol (DHCP) address pool for subtending circuit pack presence detection









Table 4-12UOSC electrical interfaces


Modem (RS-232) 1 Serial port craft interface supporting data terminal equipment (DTE) functionality

DB9

Craft 1 Internet protocol (IP) over 10Base-T Ethernet craft interface

RJ-45 (MDI)


RJ-45 (MDI-X)

WSC-1

(Wayside)


RJ-45 (MDI-X)


RJ-45 (MDI-X)


RJ-45 (MDI-X)




DB25

Table 4-13UOSC push buttons



Reset Reset module

Table 4-14UOSC optical interfaces


OSC In / Out 1 / 1 OSC channel input from the amplifier / OSC channel output from the amplifier

LC





Customer interface office alarm and PTT connectionsThe UOSC provides parallel telemetry alarm connections through a DB25 connector as identified in Table 4-15.

Table 4-15UOSC alarm interface and PTT connector pinout



Other Comments


Visible alarm




Audible alarm






Telemetry Input 219





Telemetry Input 121





4 Channel Mux/Demux (CMD4) module (NTT810BA-BH, BJ)Functional description

The 4 Channel Mux/Demux (CMD4) module provides the initial wavelength channel multiplexing stage in the two-stage Common Photonic Layer multiplexing scheme and interfaces to the terminal equipment. The CMD4 supports four DWDM channels in the 100 GHz-spaced ITU grid. Nine different CMD4 modules are required to cover the entire C-band for a total of 36 wavelengths. The nine CMD4 modules connect directly to the GMD module and support any bit rate from 1.25 Gbit/s to 10.7 Gbit/s. Figure 4-14 provides a front view of the CMD4 module whereas Figure 4-15 provides a functional block diagram of the CMD4 module.

Table 4-16UOSC technical specifications and engineering rules


• NTT839BA

Engineering rules • 1 module required for each facing direction at TOADM, ROADM sites (Two UOSCs per two-way site)

• Each side will operate as a separate logical network element in the network


Built-in OSC specifications • 1510 nm optical interface

• Tx: 1 dBm (end-of-life [EOL])


• 155 Mb/s (OC-3/STM-1) rate


• Height: 3.38 in. (85.5 mm)

• Width: 15.88 in. (405.8 mm)







Figure 4-14CMD4 module front view (shown with door both open and closed)

Figure 4-15CMD4 module functionality

CMD4 with eVOA

Channel 1 In (Port 3)Channel 2 In (Port 5)Channel 3 In (Port 7)Channel 4 In (Port 9)

Channel 1 Out (Port 4)Channel 2 Out (Port 6)Channel 3 Out (Port 8)Channel 4 Out (Port 10)

Channel Demux

Common Out (Port 2)

Common In (Port 1)

Channel Mux






The CMD4 works only with the communications infrastructure provided by the GMD (10Base-T), the CMD4 is not intended for use as a standalone module.

The CMD4 modules include ingress eVOAs for wavelength optimization support. If the CMD4 loses power, the eVOAs on the multiplexer ports and demultiplexer port revert to 40 dB of attenuation.

Along with the other Common Photonic Layer modules, the CMD4 module fits into a PTE2000, 19 in. or 23 in. wide frame with the use of a 1U or multi-slot carrier. The module measures 1U in height. The CMD4 module supports in-service rear-side fiber cleaning.

OAM&P featuresThe OAM&P features of the CMD4 are:

• channel level optical mux and demux on the 100 GHz ITU grid

• card processor

• local optical control (LOC) support

• total optical power monitoring at the common port on the multiplexer side

• total optical power monitoring at the common port on the demultiplexer side

• total optical power adjustment through an eVOA on the demultiplexer side

• serial port (RS-232) debug interface

• private Ethernet communications interface that connects to the GMD module


Table 4-17CMD4 electrical interfaces


RS-232 1 Serial port interface (RS-232) for module debug purposes

RJ-45

Ethernet 1 IP over 100Base-T Ethernet data communications interface to GMD, UOSC or DOSC

RJ-45 (MDI)







Table 4-18CMD4 optical interfaces


Ch 1 In / Out

Ch 2 In / Out

Ch 3 In / Out

Ch 4 In / Out

3 / 4

5 / 6

7 / 8

9 / 10

Optical input / output from the client-side interface(s)

LC

Common In / Out 1 / 2 DWDM optical input / output to the GMD demultiplexer output / multiplexer input

LC

Table 4-19CMD4 technical specifications and engineering rules


NTT810BA-BH, BJ: CMD4 (100 GHz) with ingress eVOA

(A different PEC is available for each of the available wavelength groups. For more information, see “Ordering information” chapter in Part 2 of this document.)

Engineering rules • Required per 4 wavelength add/drop or express group at each Terminal or OADM site:

– 1 per group at Terminal site

– 2 per group at OADM site

• Express/OADM groups require different CMD4s at Terminal sites

• Located in slots 5 to 13 of the Common Photonic Layer network element.

• For compatibility with Nortel transmitters, see Nortel Tx and CMD compatibility on page 2-82.

• CMD4s cannot carry traffic at WSS sites, and should not be connected to a WSS or cascaded from an SCMD connected to a WSS port.


• The multiplexer has a channel-level tap and an ingress eVOA with a 15 dB range to allow for launch power levelling with transponder interfaces

• Channel Mux CMD4 insertion loss: 4.2 dB (with ingress eVOA)

• Channel Demux CMD4 insertion loss: 4 dB

• The demultiplexer has a band-level VOA to ensure receivers are not overloaded (15 dB range)

• Optical taps on multiplexer output/demultiplexer input


• Height: 1.65 in. (41.9 mm)

• Width: 15.88 in. (405.8 mm)


Power 7.5 Watts, typical





44 Channel Mux/Demux C-Band (CMD44) module (NTT862AA/BA/BB/FAE5)

Functional descriptionThe 44 Channel Mux/Demux (CMD44) module provides low cost 50 GHz or 100 GHz Mux/Demux for ROADMs, WSS-based terminals, and point-to-point Thin terminals.

Three variants of the CMD44 are available:

• CMD44 C-Band 100 GHz - NTT862AA

• eCMD44 C-Band 100 GHz - NTT862FAE5

• CMD44 C-Band 50 GHz Blue (1530.33 nm to 1547.32 nm) - NTT862BA

• CMD44 C-Band 50 GHz Red (1547.72 nm to 1565.09 nm) - NTT862BB

The CMD44 C-Band 100 GHz uses the existing Common Photonic Layer 100 GHz ITU grid 36 wavelength plan, plus an additional eight skip channels between the nine Common Photonic Layer wavelength groups for a total of 44 wavelengths. See Table 3-3 on page 3-28 for all CMD44 100 GHz wavelengths.

The eCMD44 C-Band 100 GHz module must be used in 100 GHz DIA configurations.The eCMD44 C-Band 100 GHz has all the same features as the CMD44 C-Band 100 GHz except that it includes an isolator on the Common In port (Demux side). The isolator prevents existing traffic being affected if the Tx/Rx fibers are incorrectly connected for new wavelengths (prevents MLA from going into APR).

The CMD44 C-Band 50 GHz modules use the existing Common Photonic Layer 50 GHz ITU grid 72 wavelength plan, plus an additional 16 skip channels between the nine Common Photonic Layer wavelength groups for a total of 88 wavelengths (44 per module). When both CMD44 C-Band 50 GHz Blue and CMD44 C-Band 50 GHz Red are deployed, a total of 88 wavelengths are available. See Table 3-5 on page 3-30 for all CMD44 50 GHz wavelengths.

The channels on the CMD44 module have 100% add/drop capability, allowing one to 44 channels to be added, dropped, or passed through for each module.

The CMD44 has no VOAs. Optimization is carried out through the WSS and CMDA (if deployed). On the CMD44, PMs are only supported for the OPTMON facility type. Optical monitoring occurs with an OPM and although OPTMON facilities are associated with each of the channel input ports, its value is scaled appropriately. The CMD44 module does not supply OPTMON facility related information to the GMD or UOSC. In Common Photonic Layer, the OPM module provides the optical monitoring. OPTMON is not supported in a point-to-point TOADM terminal with a CMD44.





Figure 4-16 on page 4-30 provides a front view of the CMD44 module (CMD44 C-Band 100 GHz variant shown, others are similar).

Figure 4-16 CMD44 front view shown with door both open and close





Figure 4-17 provides a functional block diagram of the CMD44 100 GHz module. Figure 4-18 on page 4-32 provides a functional block diagram of the CMD44 50 GHz modules.

Figure 4-17CMD44 100 GHz ports

LC

Common Out

Common In

LC

44 C

hann

el M

UX

/DE

MU

X

1 Ch1 In CMD44100 GHz

Ch1 Out2

LC90

89

3 Ch2 In

Ch2 Out4

LC

LC

85 Ch43 In

Ch43 Out86

87 Ch44 In

Ch44 Out88

Channel Mux 1-44 In = 1, 3, 5, 7, ..., 87Channel Demux 1-44 Out = 2, 4, 6, 8, ..., 88Demux Common In = 89Mux Common Out = 90





Figure 4-18CMD44 50 GHz ports

The CMD44 module is comprised of two Wideband Athermal AWG optical mux/demux modules, one for multiplexing and one for demultiplexing. This tray is intended to be mounted in a shelf with a 2U height.

The CMD44 is slightly wider than other Common Photonic Layer modules therefore CMD44s are not housed in the multi-slot carriers (Types 1, 2 or 3). The CMD44 module fits into a PTE2000, 19 in., or 23 in. wide frame with the use of adapter brackets and/or configurable mounting ears. Each CMD44 is shipped with 19” EIA brackets installed. Order one NTT862HA Upgrade Kit for each CMD44 ordered that is to be installed in a 23” EIA or ETSI style frame.

The CMD44 faceplate does not accommodate attenuator fix pads. Attenuator fix pads should be applied directly on the transmitter or receiver or at the patch panel as shown in Figure 4-19. Unlike the CMD4, SCMD4, and SCDM8, the CMD44 does not have sliders.

LC

Common Out

Common In

LC44

Cha

nnel

MU

X/D

EM

UX

1Ch1 In CMD44

50 GHz Blue

Ch1 Out2

LC90

89

3Ch2 In

Ch2 Out4

LC

LC

85Ch43 In

Ch43 Out86

87Ch44 In

Ch44 Out88

1

2

90

89

3

4

85

86

87

88


LC

Common Out

Common In

LC

44 C

hann

el M

UX

/DE

MU

X


Ch45 Out

LC

Ch46 In

Ch46 Out

LC

LC

Ch87 In

Ch87 Out

Ch88 In

Ch88 Out






Figure 4-19Installing Attenuator fix pads at the patch panel

Fibers are routed directly into fiber risers, and intra-shelf bend limiters are not used. Existing 22U Common Photonic Layer fiber riser have a fiber capacity of approximately 200 fibers. For more information on routing CMD44 fibers, see the Routing and labeling fiber section in Installation, 323-1661-201.

OAM&P featuresThe CMD44 is a passive module and therefore does not require DC power. Since the CMD44 is passive, it is not detected or auto-provisioned by the Common Photonic Layer shelf. To add this equipment to the shelf inventory, it must be manually provisioned. Provisioning of the CMD44 module is supported in slots 14 and 15 only. As with the CMD4, SCMD4, and SCMD8 modules, the CMD44 facilities are auto-provisioned upon the creation of the CMD44 equipment. CMD44 facilities include:

• Tx and Rx adjacencies against the Channel In/Out ports

• WSS adjacencies against the Common Out port

• OPTMON facilities associated with the channel In ports

See Figure 4-17 on page 4-31 for port numbering.





Equipment alarms (Circuit Pack Missing, Circuit Pack Mismatch) and functionality that is associated with card presence detection is not supported since the CMD44 is a passive module. Auto-in-service (AINS) is also not supported and unnecessary for the OPTMON facility since no LOS alarms are raised upon facility creation until the channel becomes managed by DOC and channel power data is considered valid.

The Pre-Check feature is supported on the CMD44 module.

Provisioning of skip channels on CMD44s in a TOADM, GOADM, or group based DGFF node is not prevented by the software. The use of skip channels in networks with GOADM or group based DGFF is not permitted, and may cause instability and/or DOC to cease to function. If provisioned in TOADM networks, these skip channels pass through a TOADM in some limited configurations otherwise, the channel is lost at the node. SCMDs have a band-pass filter that filters and drops the channels for the corresponding SCMD group. The rest of the channels are passed to the upgrade port. The band-pass filter partially filters out the skip channels which are just below or just above the optical spectrum of the group being dropped. In this case, the skip channels partially pass through a TOADM and any attempt to add the channels with DOC causes a traffic impact on existing in-service channels. In the case where the skip channels that are not adjacent to the groups being dropped at the TOADM, the channels pass through without any filtering. Contact Nortel if you need more information on provisioning of skip channels on CMD44s in a TOADM.

There is no cascade ordering, users must provision the far end address of the CMD44 Adjacency at the WSS for Common Out and the CMD adjacency on the WSS to point to the CMD44 Common In.

If a duplicate channel exists on a SCMD4/SCMD8 and CMD44, the SCMD4/SCMD8 channel has precedence over the CMD44 channel. Manual and auto-provisioning of a SCMD4/SCMD8 is not permitted if shared (over-lapping) wavelengths are already provisioned and in-service on a CMD44. Similarly, provisioning a channel on a CMD44 is blocked if any of the channels in the associated group is provisioned on an existing SCMD4/SCM8 on the shelf. An Auto-provisioning Mismatch alarm is raised if auto-provisioning of a SCMD4/SCMD8 is blocked due to in-service wavelengths on a CMD44.

Table 4-20CMD44 electrical interfaces



RJ-45





Table 4-21CMD44 optical interfaces - CMD44 100 GHz and CMD44 50 GHz Blue


Ch 1 In / OutCh 2 In / OutCh 3 In / OutCh 4 In / OutCh 5 In / OutCh 6 In / OutCh 7 In / OutCh 8 In / OutCh 9 In / OutCh 10 In / OutCh 11 In / OutCh 12 In / OutCh 13 In / OutCh 14 In / OutCh 15 In / OutCh 16 In / OutCh 17 In / OutCh 18 In / OutCh 19 In / OutCh 20 In / OutCh 21 In / OutCh 22 In / OutCh 23 In / OutCh 24 In / OutCh 25 In / OutCh 26 In / OutCh 27 In / OutCh 28 In / OutCh 29 In / OutCh 30 In / OutCh 31 In / OutCh 32 In / OutCh 33 In / OutCh 34 In / OutCh 35 In / OutCh 36 In / OutCh 37 In / OutCh 38 In / OutCh 39 In / OutCh 40 In / OutCh 41 In / OutCh 42 In / OutCh 43 In / OutCh 44 In / Out

1 / 23 / 45 / 67 / 8

9 / 1011 / 1213 / 1415 / 1617 / 1819 / 2021 / 2223 / 2425 / 2627 / 2829 / 3031 / 3233 / 3435 / 3637 / 3839 / 4041 / 4243 / 4445 / 4647 / 4849 / 5051 / 5253 / 5455 / 5657 / 5859 / 6061 / 6263 / 6465 / 6667 / 6869 / 7071 / 7273 / 7475 / 7677 / 7879 / 8081 / 8283 / 84 85 / 8687 / 88


LC

Common In / Out 89 / 90 AMP Line A Out /Line B In or

WSS Switch port Out / Switch port In

LC





Table 4-22CMD44 optical interfaces - CMD44 50 GHz Red


Ch 45 In / OutCh 46 In / OutCh 47 In / OutCh 48 In / OutCh 49 In / OutCh 50 In / OutCh 51 In / OutCh 52 In / OutCh 53 In / OutCh 54 In / OutCh 55 In / OutCh 56 2 In / OutCh 57 In / OutCh 58 In / OutCh 59 In / OutCh 60 In / OutCh 61 In / OutCh 62 In / OutCh 63 In / OutCh 64 In / OutCh 65 In / OutCh 66 In / OutCh 67 In / OutCh 68 In / OutCh 69 In / OutCh 70 In / OutCh 71 In / OutCh 72 In / OutCh 73 In / OutCh 74 In / OutCh 75 In / OutCh 76 In / OutCh 77 In / OutCh 78 In / OutCh 79 In / OutCh 80 In / OutCh 81 In / OutCh 82 In / OutCh 83 In / OutCh 84 In / OutCh 85 In / OutCh 86 In / OutCh 87 In / OutCh 88 In / Out

1 / 23 / 45 / 67 / 8

9 / 1011 / 1213 / 1415 / 1617 / 1819 / 2021 / 2223 / 2425 / 2627 / 2829 / 3031 / 3233 / 3435 / 3637 / 3839 / 4041 / 4243 / 4445 / 4647 / 4849 / 5051 / 5253 / 5455 / 5657 / 5859 / 6061 / 6263 / 6465 / 6667 / 6869 / 7071 / 7273 / 7475 / 7677 / 7879 / 8081 / 8283 / 84 85 / 8687 / 88


LC

Common In / Out 89 / 90 AMP Line A Out /Line B In or


LC





Table 4-23CMD44 technical specifications and engineering rules


NTT862AA - CMD44 C-Band 100 GHzNTT862FAE5 - eCMD44 C-Band 100 GHzNTT862BA - CMD44 C-Band 50 GHz BlueNTT862BB - CMD44 C-Band 50 GHz Red(For more information, see “Ordering information” chapter in Part 2 of this document.)

Engineering rules • The CMD44 is deployed at WSS-based ROADMs (wavelength branching) or WSS-based terminals where the CMD44 connected to one of the five switch ports on either the WSS 50 GHz or WSS 100 GHz module.

• For 100 GHz DIA configurations, the eCMD44 100 GHz module must be used as it contains an isolator that prevents existing traffic being affected if the Tx/Rx fibers for new channels are incorrectly connected.

• The CMD44 can be connected directly to the WSS switch ports or indirectly using a CMDA. The CMDA can provide demux amplification for the following CMD44 configurations:

– single CMD44 100 GHz

– single CMD44 50 GHz (Blue or Red)

– both Blue and Red CMD44 50 GHz

• SCMD4/SCMD8 modules and CMD44 modules can be connected on the same WSS module only if they are connected on different switch ports. Cascading CMD44 and SCMD4/SCMD8 modules from each other is not supported. See Figure 4-20 for a supported deployment. SCMD8 modules are not supported with CMD44 100 GHz modules.

• (S)CMD4 based TOADMs can co-exist in the same network as CMD44s (100 GHz and 50 GHz). However, the skip channels are not supported to pass through a (S)CMD4 TOADM.

• (S)CMD8 based TOADMs can co-exist in the same network as CMD44 50 GHz. However, the skip channels are not supported to pass through a (S)CMD8 TOADM. (S)CMD8 based TOADMs cannot co-exist in the same network as CMD44 100 GHz.

• Provisioning of skip channels on CMD44s in a TOADM, GOADM, or group based DGFF node is not prevented by the software. The use of skip channels in networks with GOADM or group based DGFF is not permitted and may cause instability and/or DOC to cease to function. If provisioned in TOADM networks, these skip channels pass through a TOADM in some limited configurations. Otherwise the channel is lost at the node. Contact Nortel if you need more information on provisioning of skip channels on CMD44s in a TOADM.

• CMD44 modules can be used at a point-to-point TOADM terminal site (single amplified span). However, there is no OPTMON, DOC, or topology support.





Engineering rules (cont)

• CMD44 modules:

– can be used at a ROADM 3/4/5-way branch for local add/drop. You could also use a CMD44 at a 2-way WSS ROADM with a co-located SCMD spur hanging off it (making it a 3-way branch).

– can be used at a point-to-point Thin terminal site (single amplified span). However, there is no OPTMON, DOC, or topology support.

– cannot be used at GMD based sites

– channels that originate on a 100 GHz CMD (SCMD4/CMD44 100 GHz) must terminate on a 100 GHz CMD. Similarly a channel that originates n a 50 GHz CMD (SCMD8/CMD44 50 GHz) must terminate on a 50 GHz CMD

– can co-exist with channels in a different group that go from sCMD to sCMD.

– channels can only drop on a CMD44 that are added on a (s)CMD of the same channel spacing (50GHz or 100GHz) (or vice versa)

– cannot be cascaded off of a SCMD4/SCMD8. The CMD44 and SCMD4/SCMD8 must be provisioned on separate WSS ports. SCMD8 not supported with CMD 100 GHz modules.

• The channels on the CMD44 module have 100% add/drop capability, allowing one to 44 channels to be added, dropped, or passed through.

• Located in slots 14 to 30 of the Common Photonic Layer network element.



• 44 channel Mux/Demux

• C-Band 100 GHz grid (NTT862AA)

• C-Band 100 GHz grid (NTT862FAE5) - for DIA

• C-Band 50 GHz grid (NTT862BA/BB)

• 100% Add/Drop capability

• No VOAs (optimization via WSS)

• Virtual OPTMON provided by WSS/OPM

• CMD44 100 GHz/eCMD44 100 GHz insertion loss: 6 dB

• CMD44 50 GHz insertion loss: 7 dB


• Height: 3.46 in. (87.8 mm)

• Width: 17.25 in. (438.1 mm)

Weight 16 lbs (7 kg)

Power Completely passive module (no power required)

Table 4-23 (continued)CMD44 technical specifications and engineering rules





Figure 4-20ROADM branch site with SCMD4 and CMD44

Serial 4 Channel Mux/Demux (SCMD4) module (NTT810CA-CH, CJ)Functional description

The Serial 4 Channel Mux/Demux (SCMD4) module is based on the same hardware platform as the CMD4. The difference between the CMD4 and SCMD4 is that the SCMD4 has passive group filters and passthrough/upgrade ports for cascading.

The SCMD4 is 100 GHz spaced and serially cascadable. This module provides the initial mux stage and interface to the terminal equipment on the 100 GHz spaced ITU grid in terminal, OADM, Thin OADM (TOADM), and Reconfigurable OADM (ROADM) configurations. The SCMD4 can also be connected to two GMD group input ports in the same manner that you would connect a CMD4. Figure 4-21 on page 4-40 provides a front view of the SCMD4 module whereas Figure 4-22 on page 4-40 provides a functional block diagram of the SCMD4 module.

SCMD4

CM

D44

Branch

OPM

SCMD4

WSSWSS





Figure 4-21SCMD4 module front view (shown with door both open and closed)

Figure 4-22SCMD4 module functionality

The SCMD4 works only with the communications infrastructure provided by the GMD or UOSC (10Base-T), the SCMD4 is not intended for use as a standalone module.

The SCMD4 modules include ingress eVOAs for wavelength optimization support.

SCMD4 with eVOA

Channel 1 In (Port 3)Channel 2 In (Port 5)Channel 3 In (Port 7)Channel 4 In (Port 9)

Channel 1 Out (Port 4)Channel 2 Out (Port 6)Channel 3 Out (Port 8)Channel 4 Out (Port 10)

Channel Demux

Common Out (Port 2)


Common In (Port 1)Upgrade Out (Port 12)

Channel Mux






Attention: If the SCMD4 loses power, upon power up, the eVOAs reset to 40 dB of attenuation before they recover their settings from the database.

Along with the other Common Photonic Layer modules, the SCMD4 module fits into a PTE2000, 19 in., or 23 in. wide frame with the use of a 1U or multi-slot carrier. The module measures 1U in height. The SCMD4 module supports in-service rear-side fiber cleaning.

OAM&P featuresThe OAM&P features of the SCMD4 are:


• group level cascade for use in TOADM applications

• group level cascade for use with WSS in ROADM applications

• channel level optical power monitor and adjustment via a voltage controlled optical attenuator (VOA) on the MUX side


• card processor

• local optical control (LOC) support

• total optical power monitoring at the common port on the multiplexer side

• total optical power monitoring at the common port on the demultiplexer side

• total optical power adjustment through a voltage controlled optical attenuator (eVOA) on the demultiplexer side

• private Ethernet communications interface that connects to the GMD or UOSC module


Table 4-24SCMD4 electrical interfaces



RJ-45

Ethernet 1 IP over 100 Base-T Ethernet data communications interface to GMD, UOSC or DOSC

RJ-45 (MDI)







Figure 4-23SCMDx optical interface connections

Table 4-25SCMD4 optical interfaces


Ch 1 In / Out

Ch 2 In / Out

Ch 3 In / Out

Ch 4 In / Out

3 / 4

5 / 6

7 / 8

9 / 10


LC

Common In / Out 1 / 2 DWDM optical input / output to SCMD4 or SCMD8 Updg In / Updg Out, AMP Line A Out /Line B In, GMD demultiplexer output / multiplexer input or


LC

Upgrade In / Out 11 / 12 Group level bypass input / output LC

Line B IN

Line B INLine A OUT

Line A OUT

C INC IN

UPG IN

UPG IN

UPG IN

UPG IN

UPG OUT

C OUTC OUT

UPG OUT

UPG OUT

UPG OUT

SCMD

C IN C INC OUT C OUT

SCMD SCMD

SCMD





Table 4-26SCMD4 technical specifications and engineering rules


NTT810CA-CH, CJ: SCMD4 (100 GHz) with ingress eVOA

(A different PEC is available for each of the available wavelength groups. For more information, see “Ordering information” chapter in Part 2 of this document.)

Engineering rules • Required per 4 wavelength add/drop or express group at each site:



• SCMD4 cascade order must be user provisioned

• Maximum number of cascaded SCMD4s per facing network element at a TOADM or ROADM site is dictated by link engineering (Optical Modeler).

• Located in slots 5 to 13 of the Common Photonic Layer network element


Internal variable optical attenuators (VOAs) and taps

• The multiplexer has a channel-level tap and an ingress eVOA with a 15 dB range to allow for launch power leveling with transponder interfaces

• Demultiplexer has a group-level VOA to ensure that gain spectrum is as flat as possible, and power is within appropriate range for Rxs, based on the Tx/Rx profiles known by DOC

• The demultiplexer has a band-level VOA to ensure receivers are not overloaded (15 dB range)

• Internal optical taps on multiplexer output / demultiplexer input


• Add path maximum insertion losses (VOAs = 0 dB)

— Ch-In to Common Out: 5.0 dB

— Upgrade In to Common Out: 1.1 dB

• Drop Path maximum insertion losses (VOA = 0 dB)

— Common In to Ch-Out: 4.8 dB

— Common In to Upgrade Out: 0.7 dB


• Height: 1.65 in. (41.9 mm)

• Width: 15.88 in. (405.8 mm)


Power 7.5 Watts, typical





Serial 8 Channel Mux/Demux (SCMD8) module - Filtered SCMD8 (NTT861AA-AH, AJ) and Open SCMD8 (NTT861BA-BH, BJ)

Functional descriptionThe Serial 8 Channel Mux/Demux (SCMD8) has passive group-filters for cascading. This module provides the initial mux stage and interface to the terminal equipment in Reconfigurable OADM (ROADM), GMD based OADM, and terminal configurations.

Two types of SCMD8 modules are supported, the Filtered SCMD8 (NTT861AA-AH, AJ) and the Open SCMD8 (NTT861BA-BH, BJ).

Attention: You can have a mix of Filtered and Open SCMD8s in a cascade.

Filtered SCMD8 (NTT861AA-AH, AJ)The Filtered SCMD8 module support up to 8 wavelengths of only 10G eDCO-enabled optical interfaces. The module contains a filter that is optimized for maximum performance when used with eDCO optics. When this unit is used for eDCO optics on a given Common Photonic Layer system, it is possible to support multi-system wavelengths on a 100 GHz grid by selecting the SCMD4 for groups that require multi-system support.

Open SCMD8 (NTT861BA-BH, BJ)The Open SCMD8 module supports up to 8 wavelengths of both eDCO-enabled and multi-system optical interfaces. Select this module when a variety of optical interfaces are required on a 50 GHz spectral grid. All multi-system engineering rules for the SCMD4 also apply to the Open SCMD8.

Figure 4-24 provides a front view of the SCMD8 module whereas Figure 4-25 provides a functional block diagram of the SCMD8 module.





Figure 4-24SCMD8 module front view (shown with door both open and closed)

Figure 4-25SCMD8 module functionality

SCMD8

Channel 1 In (Port 3)Channel 2 In (Port 5)Channel 3 In (Port 7)Channel 4 In (Port 9)Channel 5 In (Port 11)Channel 6 In (Port 13)Channel 7 In (Port 15)Channel 8 In (Port 17)

Channel 1 Out (Port 4)Channel 2 Out (Port 6)Channel 3 Out (Port 8)Channel 4 Out (Port 10)Channel 5 Out (Port 12)Channel 6 Out (Port 14)Channel 7 Out (Port 16)Channel 8 Out (Port 18)

Channel Demux

Common Out (Port 2)


Common In (Port 1)Upgrade Out (Port 20)

Channel Mux






The SCMD8 works only with the communications infrastructure provided by the GMD or UOSC (10Base-T), the SCMD8 is not intended for use as a standalone module.

The SCMD8 modules include ingress eVOAs for wavelength optimization support.

Attention: If the SCMD8 loses power, upon power up, the eVOAs reset to 40 dB of attenuation before they recover their settings from the database.

Along with the other Common Photonic Layer modules, the SCMD8 module fits into a PTE2000, 19 in., or 23 in. wide frame with the use of a 1U or multi-slot carrier. The module measures 1U in height. The SCMD8 module supports in-service rear-side fiber cleaning.

OAM&P featuresThe OAM&P features of the SCMD8 are:


• narrow demultiplexer optical filter which improves link-budgets (eDCO DWDM Txs optimized for use with SCMD8)

• can be connected to two GMD group ports in the same manner that you would connect a CMD4

• can be connected in cascade with SCMD4s or SCMD8s of different groups off of a WSS add/ drop port (serial configuration)

• channel level optical power monitor and adjustment via a voltage controlled optical attenuator (VOA) on the MUX side

• demultiplexer path EDFA provides high input power to 50 GHz spaced channels


• private Ethernet communications interface that connects to the GMD or UOSC module






Table 4-27SCMD8 electrical interfaces



DB9

Ethernet 1 IP over 100Base-T Ethernet data communications interface to GMD, UOSC, or DOSC

RJ-45 (MDI)



Table 4-28SCMD8 optical interfaces


Ch 1 In / Out

Ch 2 In / Out

Ch 3 In / Out

Ch 4 In / Out

Ch 5 In / Out

Ch 6 In / Out

Ch 7 In / Out

Ch 8 In / Out

3 / 4

5 / 6

7 / 8

9 / 10

11 / 12

13 / 14

15 / 16

17 / 18


LC

Common In / Out 1 / 2 DWDM optical input / output to SCMD4 or SCMD8 Updg In / Updg Out, AMP Line A Out /Line B In, GMD demultiplexer output / multiplexer input or


LC

Upgrade In / Out 19 / 20 Group level bypass input / output LC





Table 4-29SCMD8 technical specifications and engineering rules


Filtered SCMD8 (NTT861AA-AH, AJ)

Open SCMD8 (NTT861BA-BH, BJ)

(There is a different PEC for each one of the 8 available wavelength groups. For more information, see “Ordering information” chapter in Part 2 of this document.)

Engineering rules • Required per 8 wavelength add/drop or express group at each site:



• SCMD8 cascade order must be user provisioned, can be cascaded in any order to allow multiple groups to be added or dropped at a site.

• Maximum number of cascaded SCMD8s per facing network element at a TOADM or ROADM site is dictated by link engineering (Optical Modeler).

• Located in slots 5 to 13 of the Common Photonic Layer network element


Internal variable optical attenuators (VOAs) and taps

• The multiplexer has a channel-level tap and an ingress eVOA with a 15 dB range to allow for launch power levelling with transponder interfaces

• demultiplexer path has taps at common input, before and after the EDFA

• Internal optical taps on upgrade input and common input ports


• Add path maximum insertion losses (VOAs = 0 dB)

— Ch-In to Common Out: 8.4 dB

— Upgrade In to Common Out: 1.0 dB

• Drop path maximum insertion losses

— Common In to Upgrade Out: 1.2 dB

— Common In to EDFA In: 1.7 dB

— EDFA Out to Ch-Out:

– 3 dB for filtered SCMD8

– 6 dB for opened SCMD8

• Drop path EDFA

— Max TOP: 10 dBm

— Max Gain: 17 dB


• Height: 1.65 in. (41.9 mm)

• Width: 15.88 in. (405.8 mm)







Broadband Mux/Demux 1x2 (NTT862DAE5)Functional description

The Broadband Mux/Demux 1x2 (BMD2) module is used in direction independent access (DIA) configurations to allow full 88 channel support. The BMD2 can also be used in ROADM configurations instead of a CMDA to allow full 88 channel support but do not need the gain of the drop amplifier.

The BMD2 contains two 50/50 wide-band optical couplers that perform the function of coupler on the Mux side and splitter on the Demux side. The BMD2 contains an isolator on the Common In port (Demux side) to protect all wavelengths if fibers are incorrectly connected.

Figure 4-37 provides a front view of a BMD2.

Figure 4-26BMD2 front view shown with door both open and close

Figure 4-38 provides functional block diagrams of the BMD2 module.

Figure 4-27BMD2 module functionality





The BMD2 is slightly wider than other Common Photonic Layer modules therefore BMD2s are not housed in the multi-slot carriers (Types 1, 2 or 3). The BMD2 module fits into a PTE2000, 19 in., or 23 in. wide frame with the use of adapter brackets and/or configurable mounting ears. Each BMD2 is shipped with 19” EIA brackets installed. Order one NTT862HA Upgrade Kit for each BMD2 ordered that is to be installed in a 23” EIA or ETSI style frame.

OAM&P featuresThe BMD2 is a passive module and therefore does not require DC power. Since the BMD2 is passive, it is not detected or auto-provisioned by the Common Photonic Layer shelf. To add this equipment to the shelf inventory, it must be manually provisioned. Provisioning of the BMD2 module is supported in any slot between 14 and 30 which is not already in use. As with the CMD4, SCMD4, SCMD8, and CMD44 modules, the BMD2 facilities are auto-provisioned upon the creation of the BMD2 equipment.

For a DIA configuration, the facility adjacencies for the BMD2 are derived once the BMD2 has been associated to an OTS and all equipment for a DIA is present in the OTS. The adjacencies between the BMD2 and the WSS are auto derived, the BMD2 to CMD44 adjacencies have to be manually on the BMD2 to point to the appropriate CMD44.

See Figure 4-17 on page 4-31 for port numbering.

Equipment alarms (Circuit Pack Missing, Circuit Pack Mismatch) and functionality that is associated with card presence detection is not supported since the BMD2 is a passive module. Auto-in-service (AINS) is also not supported and unnecessary for the OPTMON facility since no LOS alarms are raised upon facility creation until the channel becomes managed by DOC and channel power data is considered valid.

Table 4-30BMD2 electrical interfaces



RJ-45

Table 4-31BMD2 optical interfaces


Common In / Out

1 / 2 Common In / Out LC

Input 1/Output 1 3 / 4 Input/output to coupler (Mux side) LC

Input 2/Output 2 5 / 6 Input/output to splitter (Demux side) LC





Table 4-32BMD2 technical specifications and engineering rules


• NTT862DAE5

Engineering rules • Equip at direction independent access (DIA) configurations in 50 GHz system to allow full 88 channel support.

• Equip at WSS-based sites to provide full 88 channel support where amplification is not required between the WSS and the CMD44 modules in the demux path.

• The BMD2 can use any slot between 14 to 30 of the Common Photonic Layer shelf.


• Maximum total input power: 24 dBm

• Minimum return loss: 45 dB

• Working bandwidth: 1528 nm to 1570 nm

• Max insertion loss per channel (Add or Drop): 3.8 dB


• Height (1U): 1.71 in. (43.4 mm)

• Width: 17.25 in. (438.1 mm)






Wavelength Selective Switch (WSS) module (NTT837CA, NTT837DA)Functional description

The 1 x 5/ 5 x 1 (50 GHz or 100 GHz) Wavelength Selective Switch (WSS) provides the following functions:

• a per wavelength attenuation profile for up to 88 channels at 50 GHz (NTT837CA) or up to 44 channels at 100 GHz (NTT837DA) spacing

• a multiplexer block with 5 switch ports that can be used for traffic passthrough or local add/drop. The mux block is a 1D MEMS mirror array per input port.

• a demultiplexer block which is essentially a 1:5 passive power splitter

• support for up to five degree branching

• flexible per-wavelength add/drop and passthrough

• per-wavelength switching. For example, a passthrough wavelength can be converted to an add/drop wavelength.

Figure 4-28 provides a front view of the WSS module whereas Figure 4-29 provides a functional block diagram of the WSS module.

The WSS works only with the communications infrastructure provided by the GMD or UOSC (10Base-T), the WSS is not intended for use as a standalone module.

Along with the other Common Photonic Layer modules, the WSS module fits into a PTE2000, 19 in., or 23 in. wide frame with the use of a 2U or multi-slot carrier. The module measures 2U in height. Dual LC fiber sliders allow cleaning of fibers during maintenance periods.





Figure 4-28WSS module front view (shown with door both open and closed)

Figure 4-29WSS module functionality

WSS Optical Monitoring Points

Channel 1 In (Port 1)Channel 2 In (Port 3)Channel 3 In (Port 5)Channel 4 In (Port 7)Channel 5 In (Port 9)

Common Out(Port 12)

Mux block50 GHz WSS 5x1

Channel 1 Out (Port 2)Channel 2 Out (Port 4)Channel 3 Out (Port 6)Channel 4 Out (Port 8)Channel 5 Out (Port 10)

Common In(Port 11)

Demux blockpassive power

splitter





OAM&P featuresThe OAM&P features of the WSS are:

• provides 50 GHz (NTT837CA) or 100 GHz (NTT837DA) grid channel add/drop and passthrough capability. The 50 GHz grid wavelengths are defined in Table 3-4 on page 3-29 and the 100 GHz grid wavelengths are defined in Table 3-2 on page 3-28.

• total optical power monitoring at the common in port on the demux side

• total optical power monitoring at the mux input for all paths


• private Ethernet communications interface that connects to the UOSC module


• the control loop on WSS (Middle optical control) maintains per-channel loss profile

• one channel control facility per wavelength

• variable attenuation per channel used by DOC for system optimization

Table 4-33WSS electrical interfaces



DB9

Ethernet 1 IP over 100Base-T Ethernet data communications interface to GMD, UOSC, or DOSC

RJ-45 (MDI)


Table 4-34WSS optical interfaces


Switch 1 In / Out

Switch 2 In / Out

Switch 3 In / Out

Switch 4 In / Out

Switch 5 In / Out

1 / 2

3 / 4

5 / 6

7 / 8

9 / 10

Optical input / output from other WSS or CMD44, SCMD4 and SCMD8

LC

Common In / Out 11 / 12 DWDM optical input / output to /from the line amplifier

LC





Table 4-35WSS technical specifications and engineering rules


NTT837CA: 5 x 1 - 50 GHz, C-Band

NTT837DA: 5 x 1 - 100 GHz, C-Band

Engineering rules • One WSS module required per node direction

— ROADM: 2 WSS modules (facing configuration)

• Network element shelf equipping rules

— Logical slot 3 for ROADM node and DGFF node

• Add/Drop of SCMD groups possible on any port.

• Recommend planning guidelines for deployments are

— SCMD cascade order can be pre-provisioned

— Mixed SCMD4/SCMD8/CMD44 topology supported

— Maximum number of cascaded SCMDxs off a WSS switch port is dictated by link engineering (Optical Modeler).

— See Global engineering rules for SCMD and CMD44 group deployment order and WSS port allocation on page 2-21 for more information.


• Maximum total input power: 24 dBm for common input, switch 1-5 input

• Demux Insertion Loss:

— From Common in to Switch 1, 2, 3, 4, 5 out: 8.7dB maximum

• Mux Insertion Loss:

— From Switch 1,2,3,4,5 in to Common out: 7dB maximum

• Available attenuation per channel: 0-15 dB


• Height: 3.38 in. (85.5 mm)

• Width: 15.88 in. (405.8 mm)

Weight 17.5 lbs (7.9 kg)






Common Photonic Layer Amplifier (NTT830xA)Functional description

The Common Photonic Layer Amplifier (Amplifier) modules are low-noise, high input power modules with fast transient control and remote software-provisionable gain control that delivers enhanced reach capabilities to ensure each wavelength is amplified equally. Figure 4-30 provides a front view of an Amplifier module.

Figure 4-30Amplifier module front view (MLA2 shown with door both open and closed)

The Common Photonic Layer architecture includes three different amplifier modules, a line interface module, and a Distributed Raman Amplifier:

• The Single Line Amplifier (SLA), which is a single (pre-amplifier) erbium-doped fiber amplifier (EDFA), is primarily used for edge applications.

• The Mid-stage Line Amplifier (MLA), which is a dual (pre-amplifier/booster) EDFA, is used for both edge and core applications.

• The Mid-stage Line Amplifier 2 (MLA2), which is a dual (pre-amplifier/booster) EDFA, is used for both edge and core applications. The MLA2 provides gain in uncompensated WSS nodes.

• The Line Interface Module (LIM) is used for point-to-point and unamplified edge applications and core applications when used with an MLA2.

• The Distributed Raman Amplification (DRA) module, provides a counter-propagating Raman amplifier solution that can minimize the impact of long, highly lossy spans in multi-span applications. DRA modules must be deployed in both directions of an optical link. For more information on the DRA module, see Distributed Raman Amplifier (NTT831AA) on page 4-66.

Figure 4-31 provides functional block diagrams of the amplifier modules and the line interface module.





Figure 4-31Amplifier module functionality

The Amplifier modules fit into a PTE2000, 19 in. or 23 in. wide frame with the use of a 1U or multi-slot carrier. The modules measure 1U in height. Each Amplifier module supports in-service rear-side fiber cleaning and includes field-replaceable fans.

OAM&P featuresThe OAM&P features of the Amplifier are:

• local optical control (LOC)

• optical power monitoring

• power control modes (peak/total/gain/tilt)

• automatic line shutoff (ALSO)/automatic power reduction (APR) software mechanisms


Line InterfaceModule

(LIM) - NTT830DA

Line Interfacew/OSC Filter

Single LineAmplifier

(SLA) - NTT830AA

Pre Ampw/OSC Filter

Mid-stage LineAmplifier

(MLA) - NTT830BA

Pre-Boosterw/OSC Filter

Legend

1. Monitoring Port (Port 1)2. Monitoring Port (Port 2)3. OSC B In (Port 3)4. OSC A Out (Port 4)

5. Line B Out (Port 5)6. Line B In (Port 6)7. Line A Out (Port 7)8. Line A In (Port 8)

EDFA

EDFA EDFA

B

A

B

A A

B

1

6

3

4

7

2

5

8

1

6

3

4

7

2

1

6

3

4

7

2

5

8

5

8

Mid-stage LineAmplifier 2

(MLA2) - NTT830FA

Pre-Boosterw/OSC Filter

EDFA

EDFA

A

B

1

6

3

4

7

2

5

8





Attention: If duplex LC-LC patchcords are used for connections between the OPM and amplifier module monitor ports, ensure the fibers are traced properly for no crossed connections. If simplex LC-LC patchcords are available, connecting them one at a time can reduce the risk of misfibering. The connections for OPM and LIM (SLA, MLA, MLA2) are:

LIM LineB_MON (port 1) -> OPM Port 1 (local)LIM LineA_MON (port 2) -> OPM Port 2 (local)LIM LineB_MON (port 1) -> OPM Port 3 (remote)LIM LineA_MON (port 2) -> OPM Port 4 (remote)

Table 4-36Amplifier electrical interfaces (SLA, MLA, MLA2, LIM)


RS-232 1 Serial port craft interface supporting DTE functionality

DB9

Ethernet 1 IP over 100Base-T Ethernet interface to GMD, UOSC, or DOSC

RJ-45 (MDI)


Table 4-37MLA and MLA2 optical interfaces


Line A In / Out 8 / 7 Input / output port of Amplifier A SC

Line B In / Out 6 / 5 Input / output port of Amplifier B SC

Mon 2 Monitor port for Line A Out LC

Mon 1 Monitor port for Line B Out LC

OSC A Out 4 Optical Service Channel output LC

OSC B In 3 Optical Service Channel input LC





Table 4-38SLA optical interfaces



Line B In / Out 6 / 5 Input / output port of passthrough channel B SC





Table 4-39LIM optical interfaces


Line A In / Out 8 / 7 Input / output port of passthrough channel A SC

Line B In / Out 6 / 5 Input / output port of passthrough channel B SC









Table 4-40Amplifier technical specifications and engineering rules


• NTT830AA: Single Line Amplifier

• NTT830BA: Mid-stage Line Amplifier

• NTT830FA: Midstage Line Amp 2

• NTT830DA: Line Interface Module

Engineering rules • SLA: Equip at a Common Photonic Layer site where pre-amplification is required based on link engineering rules

• MLA: Equip at a Common Photonic Layer site where pre- and post-amplification (booster amplification) is required per link engineering rules

• LIM: Equip at a Common Photonic Layer site where no amplification is required per link engineering rules

— 1 module at Terminal sites

— 2 modules at Line Amplifier or OADM sites

• ROADM Applications (uncompensated):

— Use MLA2 for spans with higher losses, threshold as per link engineering rules

— Use MLA for lower span losses, threshold as per link engineering rules

• ROADM Applications (compensated):

— Use MLA-DSCM-SLA for each facing side at ROADM that requires a DSCM, providing a loss-less DSCM function from DOC perspective

• Uncompensated Line Amp

— MLA2-LIM combination can be used as an alternative to SLA-SLA pair, as dictated by link-engineering

• At terminal and OADM sites, amplifier is located in slot 2.

• At line amplifier sites amplifiers are located in slot 1 and 2.

• Do not add attenuators on Amplifiers (MLA2, MLA, SLA, LIM) on Line A Port 7 and Port 8.






SLA:• Pre-amplifier

– 20 dB design flat gain (DFG)

– 17 dBm maximum total output power (TOP)

• APR/ALSO functionality

• Hazard Level 1 (IEC60825-2:2000) classification

• Presence of OSC filter

• Optical connectorized taps on Amplifier input/output ports

• See Figure 4-32 on page 4-63 for the SLA line A gain mask

• See Table 4-41 on page 4-62 for the SLA LOS thresholds

MLA:• Pre-amplifier

– 20 dB DFG

– 17 dBm maximum TOP

• Post-amplifier (Booster)

– 17 dB DFG

– 19 dBm maximum TOP

• APR/ALSO/ORL functionality



• Optical connectorized taps on Amplifier input/output ports

• See Figure 4-32 on page 4-63 for the MLA line A & Figure 4-33 on page 4-64 for the MLA line B gain mask

• See Table 4-41 on page 4-62 for the MLA LOS thresholds

MLA2:• Pre-amplifier

– 23.5 dB DFG

– 19.5 dBm maximum TOP

• Post-amplifier (Booster)

– 23 dB DFG

– 19 dBm max TOP


• Hazard Level 1


• Optical taps on amplifier input/output ports

• See Figure 4-34 on page 4-65 for the MLA2 line A & line B gain mask

• See Table 4-41 on page 4-62 for the MLA2 LOS thresholds

Table 4-40 (continued)Amplifier technical specifications and engineering rules





Optical specifications (continued)

LIM:

• 0.9 dB loss

• OSC filters in/out

• Optical connectorized taps


• Height: 1.65 in. (41.9 mm)

• Width: 15.88 in. (405.8 mm)

Weight SLA, MLA, LIM: 10.5 lbs (4.76 kg)

MLA2: 12 lbs (5.44 kg)

Power SLA: 35 Watts, typical

MLA, MLA2: 40 Watts, typical

LIM: 20 Watts, typical

Note: The ratio between the main signal and the monitoring port is 2%.

Table 4-41Amplifier input and output LOS thresholds

Amplifier Input LOS threshold (dBm) Output LOS threshold (dBm)

Min Default Max Min Default Max

SLA lineA -40 -32 10 -15 -10 15

MLA lineA

MLA lineB

-40

-30

-32

-22

10

13

-15

-11

-10

-6

15

24

MLA2 lineA

MLA2 lineB

-40

-40

-36

-36

10

10

-11

-11

-9

-9

24

24

Table 4-40 (continued)Amplifier technical specifications and engineering rules





Figure 4-32SLA line A and MLA line A gain mask

1. The dashed lines area ( ), identifies the minimum guaranteed outputpower when the module is over gained. It is not required to maintain flatgain in those regions.

2. In the Extended Range, it is not required to meet a maximum outputpower of 17 dBM. The Gain Tilt is between 0 and -5dB.

Extendedrange

Over Gainrange

Typical range

20

18

16

14

12

10

8

6

4

2

0

-2

-4

-6

-8

-10

-11-30 -28 -26 -24 -22 -20 -18 -16 -14 -12 -10 -8 -6 -4 -2 0 2 4 6 8 10 12

Minimum guaranteed outputpower under single channel

Out

put P

ower

(dB

m)

Input Power (dBm)





Figure 4-33MLA Line B gain mask



22

20

18

16

14

12

10

8

6

4

2

0

-2

-4

-20 -18 -16 -14 -12 -10 -8 -6 -4 -2 0 2 4 6 8 10 12 14 16��

yyyyyyyyyyyyyyyyyyyyyyyy

Minimum guaranteed outputpower under single channel

Extendedrange

Over Gainrange

Out

put P

ower

(dB

m)

Input Power (dBm)

Typical range





Figure 4-34MLA2 Line A and Line B gain mask



22

20

18

16

14

12

10

8

6

4

2

0

-2

-4

-6

-8

-10

-36 -34 -32 -30 -28 -26 -24 -22 -20 -18 -16 -14 -12 -10 -8 -6 -4 -2 0 2 4 6 8 10 12

��

yyyyyyyyyyyyyyyyyyyy

Extendedrange

Over Gainrange

Out

put P

ower

(dB

m)

Input Power (dBm)

Typical range





Distributed Raman Amplifier (NTT831AA)Functional description

The Distributed Raman Amplifier (DRA) module provides a counter-propagating Raman amplifier solution that can minimize the impact of long, lossy spans in multi-span applications. DRA extends span reach and reduces network regeneration when it is deployed on spans which are affecting the overall system reach and forcing regeneration points. Figure 4-35 provides a front view of a DRA module.

The DRA has 4 pumps as follows, each capable of up to 50 mW (500 mW [27 dBm] total).

• Pump 1 wavelength 1424.5 nm




The DRA module fits into a PTE2000, 19 in. or 23 in. wide frame with the use of a 2U or multi-slot carrier. The module measures 2U in height. Each DRA module includes field-replaceable fans.

Figure 4-35DRA front view shown with door both open and close

Figure 4-36 provides a functional block diagram of the DRA module.





Figure 4-36DRA module functionality

OAM&P featuresThe OAM&P features of the DRA are:

• automatic shutoff and automatic power reduction (APR); embedded optical laser safety software mechanisms


• pump ratio provisioning for gain flattening

• provisionable target power

• provides gain across the entire C-band spectrum and has the ability to flatten and or adjust the gain profile across the entire spectrum

• capable of 8 to 12 dB Raman gain depending on the application

• monitoring points for signal power, OSC power, Raman pump power, and Raman reflected pump power.

Raman Pump Dump

Raman FilterLine B Out

1

4

2

3

Line B In

Raman Filter

C Band Signal Monand OSC Signal Mon

Pump Mon

Pump Reflect Mon

Line A In Line A Out

Pump Wavelength 1 1424.5 nmPump Wavelength 2 1434.5 nmPump Wavelength 3 1455.0 nmPump Wavelength 4 1465.0 nm4 pumps (no polarization)

Raman Pumps





Table 4-42DRA electrical interfaces



DB9


RJ-45 (MDI)



Table 4-43DRA optical interfaces



Line B In / Out 2 / 1 Input / output port of Amplifier B SC

Table 4-44DRA technical specifications and engineering rules


• NTT831AA

Engineering rules • Equip at a Common Photonic Layer site where distributed Raman amplification is required for long lossy spans.

Note: When deployed at a length in excess of 10 m (such as an application where the DRA resides in a frame other than the GMD/DOSC/UOSC), the Ethernet interface of the DRA does not meet the intra-building surge criteria (R4-12) of Telcordia GR-1089-CORE, Issue 4. The interface is, however, fully compliant with the surge criteria of (ETSI) EN 300 386 for equipment operating in locations other than telecommunication centers.

• Use with MLA or MLA2 amplifiers.

• DRA module is always used in pairs, one at each opposite end of the span.

• At GOADM (Figure 3-22 on page 3-24) and TOADM terminal (Figure 3-19 on page 3-21) sites, the DRA is located in slot 3.

• At small channel access ROADM terminal sites, the DRA is located in slot 13. See (Figure 3-4 on page 3-8)

• At channel access ROADM terminal sites, the DRA is located in slot 13. See (Figure 3-8 on page 3-12)

• At channel access ROADM terminal sites with an extra SLA, the DRA is located in slot 12. See (Figure 3-9 on page 3-13)

• At line amplifier sites, DRAs are located in slot 5 and 6. See (Figure 3-25 on page 3-26)






• Counter-propagating distributed Raman amplifier.

• Provides gain across the entire C-band spectrum and has the ability to flatten and or adjust the gain profile across the entire spectrum.

• Capable of up to 12 dB Raman gain depending on application variables such as fiber type.

• Provides limited gain on the OSC channel.

• Optical power at any port is 27 dBm (typical)

• Distributed Raman amplification is compatible with all fiber types (except for TWRS and LEAF fiber types when operating in the managed shutoff mode) and gain can be achieved at any wavelength depending on the availability of the pump.

• DRA pump wavelengths (range is 1420 to 1467 nm)

– Pump Wavelength 1 1424.5 nm




• Input/Output Return Loss (correspond to the minimal connector return loss at any ports) 40 dB.

• Insertion Loss

– Line A In to Line A Out is 1.3 dB maximum

– Line B Out to Line B In is 1.0 dB maximum

– C/L coupler is 1.3 dB maximum

– Patch panel is 0.5 dB maximum

Note 1: In the managed mode, the total supported span loss is defined as the total loss from DRA Line B IN to DRA Line A IN. In the local mode, the total supported span loss is defined as the total loss from Booster output to DRA Line A IN.Note 2: Span loss depends on losses from the patch panel, DRA Line B filter, and C/L couplers.Note 3: If the patch panel and/or C/L coupler losses exceed the maximum values, the DRA may not turn on.• APR/ALSO functionality

• 1M (IEC60825-2:2000) classification

• Although DRA specific Performance Monitoring capabilities are not supported, Common Photonic Layer have sufficient PMs to operate, maintain, and troubleshoot systems with DRAs.

• Optical connectorized ports on DRA input/output ports


• Height: 1.65 in. (41.9 mm)

• Width: 15.88 in. (405.8 mm)


Power consumption 54 W typical, 100 W, maximum

Table 4-44 (continued)DRA technical specifications and engineering rules





Channel Mux/Demux Amplifier (NTT832AA)Functional description

The Channel Mux/Demux Amplifier (CMDA) module contains:

• a single erbium-doped fiber amplifier (EDFA) that provides high input power to 50 GHz spaced channels in the demultiplexer path

• splitter/couplers for demux and mux of the 50 GHz Blue and Red channels

Figure 4-37 provides a front view of a CMDA.

Figure 4-37CMDA front view shown with door both open and close

Figure 4-38 provides functional block diagrams of the CMDA module.

Figure 4-38CMDA module functionality

CMDA

Common Out6

2

4

3

1

5

Mux 1 In

Mux 2 In

Demux 1 Out

Demux 2 OutCommon In∑

∑





The CMDA module fits into a PTE2000, 19 in. or 23 in. wide frame with the use of a 1U or multi-slot carrier. The modules measure 1U in height. Each CMDA module supports in-service rear-side fiber cleaning and includes field-replaceable fans.

OAM&P featuresThe OAM&P features of the amplifier are:

• local optical control (LOC)

• optical power monitoring

• power control mode (gain)

Attention: The gain can be set by a user but is normally controlled by DOC.


Table 4-45CMDA electrical interfaces



DB9


RJ-45 (MDI)


Table 4-46CMDA optical interfaces


Common In / Out

5 / 6 Common In / Out LC

Mux 1/2 In

1 / 3 Inputs to mux filter LC

Demux 1/2Out

3 / 4 Outputs from demux amplifier/filter LC





Table 4-47CMDA technical specifications and engineering rules


• NTT832AA

Engineering rules • Equip at WSS-based sites where amplification is required between the WSS and the CMD44 modules in the demux path.

• The CMDA is controlled by DOC (except in single span CMD44 Thin terminal applications).

• The CMDA can use any slot of the Common Photonic Layer shelf. However, it is recommended to provision in slot 5 or the first next available slot.


• Amplifier

– 0 dB to 17 dB gain

– 20.5 dBm maximum total output power (TOP) prior to demux filter

• Insertion Loss

– Mux path: 3.5 dB maximum

– Demux path: 3.5 dB maximum



• See Figure 4-39 for the CMDA gain mask

• See Table 4-48 for the CMDA LOS thresholds


• Height: 1.65 in. (41.9 mm)

• Width: 15.88 in. (405.8 mm)


Power 30 W, typical

Table 4-48CMDA AMP facility input and output LOS thresholds (Common In port)

Min Default Max

Input LOS threshold -45 dBm -22 dBm 20 dBm

Output LOS threshold -10 dBm -10 dBm 30 dBm

Shutoff -45 dBm -35 dBm 20 dBm





Figure 4-39CMDA gain mask

Optical Power Monitor (NTT838AA)Functional description

The Optical Power Monitor (OPM) provides the ability to monitor and report the per-wavelength optical powers on the 50 GHz ITU grid across the entire C-band using the interconnection of up to two Common Photonic Layer amplifiers within a site. Figure 4-40 provides a front view of an OPM module. Figure 4-41 provides functional block diagrams of the OPM module.

Table 4-49CMDA OPTMON facility LOS thresholds (Common Out port)

Min Default Max

LOS threshold -45 dBm -20 dBm 20 dBm

The dashed lines area ( ), identifies the minimum guaranteed outputpower when the module is over gained. It is not required to maintain flatgain in those regions.

22

20

18

16

14

12

10

8

6

4

2

0

-2

-4

-6

-20 -18 -16 -14 -12 -10 -8 -6 -4 -2 0 2 4 6 8 10 12 14 16��

yyyyyyyyyyyyyyyyyyyyyyyy

Minimum guaranteed outputpower under single channelExtended range minimum outputpower under single channel

Extendedrange

Over Gainrange

Out

put P

ower

(dB

m)

Input Power (dBm)

Typical range





Figure 4-40OPM front view (shown with door both open and closed)

Figure 4-41OPM module functionality

The OPM module fits into a PTE2000, 19 in. or 23 in. wide frame with the use of a 1U or multi-slot carrier. The OPM module measure 1U in height.

OAM&P featuresThe OAM&P features of the OPM are:

• optical power monitoring taps on OPM ports (1-4) for fiber connection validation with amplifier monitor-out ports


• 50 GHz spaced per-wavelength optical power monitoring and reporting functionality across the C-band


Port 1

OPM

Per Ch Power

Port 2Monitor In

Per Ch Power

Port 3 Per Ch Power

Port 4 Per Ch Power





• Ethernet interface for private communication with the GMD, UOSC or DOSC module

ATTENTIONIf duplex LC-LC patchcords are used for connections between the OPM and amplifier module monitor ports, ensure the fibers are traced properly for no crossed connections. If simplex LC-LC patchcords are available, connecting them one at a time can reduce the risk of misfibering. The connections for OPM and LIM (SLA, MLA, MLA2) are:

LIM LineB_MON (port 1) -> OPM Port 1 (local)LIM LineA_MON (port 2) -> OPM Port 2 (local)LIM LineB_MON (port 1) -> OPM Port 3 (remote)LIM LineA_MON (port 2) -> OPM Port 4 (remote)

Table 4-50OPM electrical interfaces



DB9

Ethernet 1 IP over 100Base-T Ethernet interface to GMD, UOSC or DOSC

RJ-45 (MDI)



Table 4-51OPM optical interfaces


Mon 1 / 2 Optical input LC

Mon 3 / 4 Optical input LC

Table 4-52OPM technical specifications and engineering rules


• NTT838AA: Optical Power Monitor

Engineering rules • Mandatory at WSS (ROADM) sites, may be required at other sites as dictated by link engineering (Optical Modeler).

• An OPM can be shared between network elements with the same or different OSID.

• Connected to amplifier module Line A / B out monitoring ports

• Located in slot 1 of the Common Photonic Layer network element





Breaker interface panels (BIP)The following breaker interface panels are supported:

• 1U BIP - NTK599DA (for global deployments) on page 4-76

• BIP - NTN458RA (for deployments in North America) on page 4-78

• EMEA BIP - NTT899GC (for deployments in Europe, Middle East and Africa) on page 4-79

1U BIP - NTK599DA (for global deployments)This BIP is a 1U high assembly that mounts at the top of the Common Photonic Layer equipment frame. Deployment of the 1U BIP is supported in the following rack types:

• ETSI racks compliant to ETS 300 119-3

• standard 19” and 23” EIA racks compliant with EIA 310-D

• 19” EIA racks with non-compliant minimum 17.5” upright spacing

The 1U BIP has 13 x 5 A redundant breakers, one for each module, with an additional 20 A or 4 0A circuit breaker which is available for terminal equipment in the same rack unit. Breakers are field replaceable and order provisionable based on your system requirements. This BIP comes configured with all 5 A breakers (13 for -48 V A and 13 for -48 V B). Order the 20 A and 40 A breakers separately.


• for use with C-band only

• 4 LC optical ports with taps

• Channel Power Measurements at 50 GHz

• Total Input Power Range Per Port (dBm): -25 to +7

— Accuracy of total power measurement is guaranteed within above range

— Max total optical input power at any port: 23 dBm

• Per Channel Input Power Dynamic range Per port (dBm): -43 to +9

— Channel power is detectable within above range

— Max channel power at any port: 10 dBm


• Height: 1.65 in. (41.9 mm)

• Width: 15.88 in. (405.8 mm)



Table 4-52 (continued)OPM technical specifications and engineering rules





The 1U BIP also has the following features:

• full front access and a pull out drawer for servicing activities

• alternatively, front and rear access and a pull out drawer for servicing activities

• power routing diversity

• field or custom termination of power feeds, without the need for special tools

• input power and grounding lugs are located on the 1U BIP front surface, permitting unobstructed access for assembly and maintenance

• power cables are routed towards the rear of the 1U BIP, then out the top of the frame

• optional return or ground bridge accessible from front

• A and B are isolated loads, have separate alarm capabilities and can be separately configured

The 1U BIP is rated for operation in the temperature range of -10°C to +60°C. The 1U BIP provides A and B inputs with a voltage of -48 V dc nominal (-40 V dc to -60 V dc). Figure 4-42 shows the front views of the 1U BIP.

Figure 4-421U BIP front view

Power input alarm indicatorsThe 1U BIP has two alarm light-emitting diodes (LEDs). The alarm LEDs on the A side are identical to the LEDs on the B side. See Table 4-53 for the 1U BIP LED summary.

Attention: When a breaker trips, it pops out.

Table 4-531U BIP LED summary

Operation state PWR ON (green LED) Filter Fail (red LED)

normal operation on off

failed operation (see Note) on on

Note: LED is lit when the voltage is less than or equal to -34 V.





BIP - NTN458RA (for deployments in North America)The BIP is a 1U high assembly that mounts at the top of the Common Photonic Layer equipment frame. The BIP supports four breakers at 20 A, three breakers at 5 A, and one breaker at 15 A and can support up to eight Common Photonic Layer modules. The BIP is rated for operation in the temperature range of -10°C to +60°C. The BIP provides A and B inputs with a voltage of -48 V dc nominal (-40 V dc to -60 V dc). Figure 4-43 shows rear, top and front views of the BIP.

Figure 4-43BIP rear, top and front views

Power input alarm indicatorsThe BIP power input alarm circuit detects an input power failure. A green “PWR ON” light-emitting diode (LED) that is lit indicates normal operation. When this LED is turned off, it indicates that the input power is lost. In normal operation, the power input alarm external relays are in an energized or powered state. The relays de-energize or power off when input power is lost, providing common to normally closed (C to NC) contact closure for the alarm state.

B A

Output connectors

Rear view(rotated)

TOP OF PANEL

PWRALM

FUSEALARM BAY ALARMS

VIS AUD

CRRACNONO NCNC

CONTACTS ACTIVATE

MJRACNONC NCNO

MNRACNOC NCC

BA

23" bracket

19" bracket

Output breakerspower A

Output breakerspower B

Front view





Breaker alarm indicatorBreaker alarms have two methods of operation. In both cases, the red “BREAKER ALARM” LED is turned off for normal operation and lit when the alarm circuit is activated. The first method uses indicating type breakers that provide a mechanical connection to activate the alarm card. The second method uses open-circuit electronic sensing across the fuse holder. Open-circuit detection usually requires that the “RESET” push button be activated to clear the breaker alarm. For both methods, the breaker alarm external relays de-energize or power off for normal operation and energize or power on when a breaker alarm is detected, providing common to normally open (C to NO) contact closure for the alarm state.

Bay alarmsBay alarms provide visual alarm status indications for the frame (system level). These alarms can be a combination of three different levels: critical, major, and minor. Critical alarms are red; major alarms are either red or yellow; and minor alarms are always yellow. The external alarm relays are de-energized (or in a powered-off state) for normal operation and energize (or go into a powered-on state) when an external alarm is detected. Activation of these types of alarms comes from external equipment alarm contacts that are either in the frame or system and provide an alarm ground to the input ports of the alarm system.

Alarm circuitsMost monitoring alarm systems require an alarm ground signal to activate the individual alarms.

The most common, is a single-point contact or paralleled contact configuration. An alarm ground wire connects to the common of the external relay contact, and the associated NC or NO contact connects to the alarm monitoring system. When the alarm activates, the relay closure between the C and either the NC or NO sends an alarm ground to the alarm monitoring system, activating the appropriate alarm. Multiple relay contacts can be paralleled in this configuration to activate a single or multiple input to the alarm monitoring system.

EMEA BIP - NTT899GC (for deployments in Europe, Middle East and Africa)

The EMEA BIP is a 3U high assembly that mounts at the top of the Common Photonic Layer equipment frame and is suitable for front and rear access installations. The EMEA BIP supports 22 breakers (11 breakers on each side [A and B]) at 6 A each and can support up to 11 Common Photonic Layer modules. The EMEA BIP is rated for operation in the temperature range of -25°C to +55°C. The EMEA BIP provides A and B inputs with an input voltage range of -40 V dc to -75 V dc that is suitable for -48 V dc nominal or -60 V dc nominal sites. Figure 4-44 shows front and rear views of the EMEA BIP.





Figure 4-44EMEA BIP front and rear views

Fuse panelsThe following breaker interface panels are supported:

• 1U Fuse Interface Panel - NTK599EA on page 4-80

• Fuse Panel, 10 circuits - NTT899GB on page 4-82

1U Fuse Interface Panel - NTK599EAThis Fuse Interface Panel (FIP) is a 1U high assembly that mounts at the top of the Common Photonic Layer equipment frame. Deployment of the 1U FIP is supported in the following rack types:

• ETSI racks compliant to ETS 300 119-3

• standard 19” and 23” EIA racks compliant with EIA 310-D

• 19” EIA racks with non-compliant minimum 17.5” upright spacing

The 1U FIP has 13 x 5 A redundant fuses, one for each module with an additional 20 A or 40 A circuit breakers which is available for terminal equipment in the same rack unit. Fuses are field replaceable and order provisionable based on your system requirements. This FIP comes configured with all 5 A fuses (13 for -48 V A and 13 for -48 V B). Order the 20 A and 40 A breakers separately.





The 1U FIP also has the following features:

• full front access and a pull out drawer for servicing activities

• alternatively, front and rear access and a pull out drawer for servicing activities

• power routing diversity

• field or custom termination of power feeds, without the need for special tools

• input power and grounding lugs are located on the 1U FIP front surface, permitting unobstructed access for assembly and maintenance

• power cables are routed towards the rear of the 1U FIP, then out the top of the frame

• optional return or ground bridge accessible from front

• A and B are isolated loads, have separate alarm capabilities and can be separately configured

• the Filter Fail red LED, indicates that the voltage is less than or equal to -34 V

The 1U FIP is rated for operation in the temperature range of -10°C to +60°C. The 1U FIP provides A and B inputs with a voltage of -48 V dc nominal (-40 V dc to -60 V dc). Figure 4-45 shows the front views of the 1U FIP.

Figure 4-451U FIP front view

Power input alarm indicatorsThe 1U FIP has three alarm light-emitting diodes (LEDs). The alarm LEDs on the A side are identical to the LEDs on the B side. See Table 4-54 for the 1U FIP LED summary.

Attention: When a fuse is blown, the Fuse Fail LED is lit on the side of the blown fuse. To identify the blown fuse, look at the top of the fuses to identify the fuse with the broken filament.





Fuse Panel, 10 circuits - NTT899GB

Attention: The CPL Fuse Panel 10 circuits, NTT899GB, is now Manufactured Discontinued (MD) and is replaced by the BIP 13x5A,20A or 40A 1U Front Access, NTK599DA. Customers who prefer to replace the NTT899GB with a power breaker instead of fuse panel can use the NTK599EA FIP 13x5A, 20A or 40A, 1U Front Access.

The fuse panel is a 1U high assembly that mounts at the top of the Common Photonic Layer equipment frame. The fuse panel provides 20 GMT fuses (10 fuses on each side [A and B]) at 5 A each and can support up to 10 Common Photonic Layer modules. The fuse panel is rated for operation in the temperature range of -5°C to +55°C. The fuse panel has an input voltage range of -20 V dc to -60 V dc and screw-type output terminals. Figure 4-46 shows front and rear views of the fuse panel.

Figure 4-46Fuse panel front and rear views

Power input alarm indicatorsThe fuse panel power input alarm circuit detects an input power failure. A green “PWR ON” LED that is lit indicates normal operation. When this LED is turned off, it indicates that the input power is lost.

Fuse alarm indicatorThe red “FUSE ALARM” LED is turned off for normal operation and lit when the fuse panel’s alarm circuit is activated.

Table 4-541U FIP LED summary (A or B side)

Operation state PWR ON (green LED)

Filter Fail (red LED)

Fuse Fail (red LED)

normal operation on off off

failed operation (see Note) on on on

one or more fuses are blown on on or off on

Note: LED is lit when the voltage is less than or equal to -34 V.





2U AC Rectifier (NTN458SB, NTN458SC)Common Photonic Layer requires DC power for operation. The 2U high rectifier converts AC power to DC power. The rectifier kit can be ordered with batteries when battery backup is required (NTN458SC) or without batteries (NTN458SB).

The 2U AC Rectifier kits (NTN458SB/SC) include the following components:

• Rectifier chassis (N0016409) pre-installed with two (1400 W) rectifiers (NTGS24LD)

• Rectifier Monitoring and Control Unit (NTGS27LD)

• Rectifier chassis ground cable assembly, 6 AWG (NTN458SE)

• Battery ground cable assembly, 6 AWG (NTN458SF)

• Alarm cable, 22 AWG (R0117360)

• 5 hex screws (P097F813). Four are required for installation, one is spare.

The NTN458SC kit also includes the necessary components for battery backup:

• Battery tray (N0013524)

• 4 batteries, VRLA 12V 46Amp-Hr (A0672263)

• Cable kit for rectifier and batteries (NTN458SG)

• 9 hex screws (P097F813). Eight are required for installation, one is spare.

The 2U AC Rectifier can be installed in a 19, 21 or 23 -inch rack. To mount the rectifier in a 21 or 23-inch rack, you must install the extender brackets supplied with the rectifier chassis. Use the 1U power cable support bracket (N0070324) for ETSI applications and use the N0070325 for non-ETSI applications.

The 2U AC Rectifier with battery backup must be installed in a 21 or 23-inch rack.

The 2U AC rectifier can power a maximum of three breaker interface panels (BIP) or fuse panels and supports 120 V, 208 V, 230 V, or 240 V AC dual feed inputs. See Table 4-55 for the corresponding wire sizes and fuse/breaker ratings.

The 2U AC rectifier must be connected on a branch circuit with a rating of 20 A or less.

Attention: For redundant power supply, Nortel recommends that both AC circuits be derived from the same ac phase. Consult your local and national safety codes if you are considering powering each rectifier from different AC phases.





Fiber Manager (FM) with/without Dispersion Slope Compensation Module (DSCM)

The FM (with/without DSCM) is a frame-mountable, 1U high, chassis and drawer assembly that serves to contain either a slack-storage drop-in plate assembly or a DSCM drop-in plate assembly and DSCM which are installed in the FM during field deployment. A complete slack storage solution requires one FM (NTT899FA or NTT899FE) and one slack-storage drop-in plate assembly (NTT899FD). A DSCM application requires one FM (NTT899FA or NTT899FE), one DSCM drop-in plate assembly (NTT899FB), and a specific DSCM (Type 1, Type 2, Type 3, Type 5) depending on the application. Each component must be ordered separately.

Attention: The NTT899FE is included with the multi-slot carriers.

Figure 4-47 shows the interior view of the FM drawer (NTT899FA).

Figure 4-47Interior view of the Fiber Manager (FM)

Table 4-552U AC Rectifier supported inputs

Input feed Nominal AC mains input

Max. current

Wire size Protective element min. rating

Protective element min. rating, poles/positions per feed

One per rectifier

Single phase 120V AC 10 A #16 AWG 15 A 1

Single phase 208V AC 10 A #16 AWG 15 A 2

Single phase 230/240V AC

8 A #16 AWG 10 A 2





DSCM drop-in plate assembly (NTT899FB)The DSCM drop-in plate assembly provides some slack fiber storage for the fiber connections to the DSCM and ensures that all fibers within the FM drawer are properly routed to prevent damage or performance degradation. The fiber management hardware guides the fiber to allow full extension of the FM drawer, and protects the fiber as the FM drawer is opened and closed.

Figure 4-48 shows the DSCM drop-in plate assembly and DSCM (NTT899FB).

Figure 4-48DSCM drop-in plate

Dispersion Slope Compensation ModuleProduct Engineering Codes (PECs) include:

• NTT870AA-AH, AJ-AN, AP-AQ

• NTT870CA-CH, CJ

• NTT870EA-ED

• NTT870GA-GG

The Dispersion Slope Compensation Module (DSCM) is a passive device used to provide chromatic dispersion compensation and slope compensation introduced by the inherent characteristics of the transmission fiber as a light pulse travels through the fiber over long distances. DSCMs are therefore used to maximize the performance of the Common Photonic Layer system.





DSCMs are available for various fiber types and they come in different fiber lengths for varying amounts of accumulated dispersion. DSCM types and lengths available include:

• DSCM Type 1 is used for the compensation of NDSF fiber spans. DSCM Type 1 units are available in a 5 km length and in lengths ranging from 10 km to 140 km (in 10 km increments).

• DSCM Type 2 is used for the compensation of TWRS fiber spans. DSCM Type 2 units are available in a 20 km length and in lengths ranging from 40 km to 320 km (in 40 km increments).

• DSCM Type 3 is used for the compensation of TWCL fiber spans. DSCM Type 3 units are available in a 20 km length and in lengths ranging from 40 km to 120 km (in 40 km increments).

• DSCM Type 5 is used for the compensation of ELEAF fiber spans. DSCM Type 5 units are available in a 12.5 km length and in lengths ranging from 25 km to 150 km (in 25 km increments).

See “Ordering information” chapter in Part 2 of this document for a complete list of available DSCMs along with their maximum insertion loss values.

The DSCM consists of a DSCM variant, a bulkhead equipped with two SC-SC adaptors and a plate to secure the DSCM to the DSCM drop-in plate assembly in the FM drawer. The DSCM is a field-replaceable unit.

Figure 4-49 shows a DSCM and an interior view of the FM with DSCM.

Figure 4-49Interior view of the Fiber Manager (FM) with DSCM (shown with DSCM drop-in plate assembly and DSCM)





Engineering rules1 Module loss is the worst case insertion loss of any wavelength within the

specified C-band (see “Ordering information” chapter in Part 2 of this document).

2 All C-band DSCMs have a minimum optical return loss of 45 dB.

Attention: When the DSCM is added to the network, the total optical return loss decreases.

3 To avoid module damage, the maximum optical input power must not exceed 24 dBm.

4 The insertion loss includes 0.3 dB connector loss for two mated connections.

Slack-storage drop-in plate assembly (NTT899FD)The slack-storage drop-in plate assembly provides 12 flip trays (spools) for up to 6 ft 8 in. (2 m) of discrete slack storage for 12 Tx/Rx fiber pairs, or 24 discrete fibers. The slack-storage drop-in plate assembly secures to the FM drawer and is a field-replaceable unit.

Figure 4-50 shows the slack-storage drop-in plate assembly.

Table 4-56DSCM optical interfaces

Interface name Function Connector type

DCSM In Input to DSCM SC

DSCM Out Compensated output SC

Table 4-57DSCM physical specifications


NTT870AA - AH, AJ-AN, AP, AQ (Type 1)

NTT870CA - CH, CJ (Type 2)

NTT870EA-ED (Type 3)

NTT870GA - GF (Type 5)


• Height: 1.2 in. (30.5 mm)

• Width: 9.6 in. (243.8 mm)






Figure 4-50Slack-storage drop-in plate

Fiber and cable management strategyFiber management

The fiber management strategy for the Common Photonic Layer is designed to maximize fiber routing efficiency and manageability based on the following parameters:

• High-speed multi-wavelength fibers are isolated from single-wavelength fibers.

• A minimum bend radius of 30 mm is maintained for all 2 mm jacketed fibers.

• Fibers can be routed to overhead troughs or through floor.

• Client-side fibers are segregated on a module basis to aid in tracing.

• Installation/removal of a single fiber is possible without impacting traffic on other connections (especially high-speed fibers).

• Copper and fiber connections are completely isolated from each other.

A two-tiered bend limiter design allows the multi-wavelength fibers to remain protected while providing easy access to the client-side fibers.

For examples of bend limiters, see the Routing and labeling fiber section in Installation, 323-1661-201.

Fiber layout guidelinesOn a typical Common Photonic Layer system, the fiber layouts are in accordance with the following guidelines:

• The fiber exits to the right-hand side of the sub-rack.

• The fiber riser is segregated on a module basis to aid in fiber tracing.





• The installation/removal of a module does not disturb fibers or require disassembly of fiber management components.

• The fiber management system enables the user to trace, remove, and install a single fiber without impacting traffic on adjacent fibers.

• The client fibers from the three bottom most SCMD or CMD4 modules are routed to the outermost fiber riser channel. The fibers from the next three modules are routed in the next fiber riser channel and so on.

• The line fibers are protected in the innermost channel.

• The channel for the group and intrasystem fibers is formed by routing them behind the bend limiters attached to the CMD4 and GMD module or SCMD and UOSC module carriers. Here, they are protected from disturbance when the client fibers are being handled

• The line fiber is isolated and well protected from the more frequently manipulated client fibers.

• The vertical fiber channels are formed using fiber clips fastened to the riser.

• Each vertical channel of client fibers feeds into its own Fiber Manager (FM).

• Use fiber cross-channel assembly (NTT899AC) to route fibers from the left side to the right side of the bay and down to the Common Photonic Layer shelf. This is needed only if a terminal shelf is mounted in the same bay with a Common Photonic Layer shelf and the terminal shelf is above the CPL shelf.

Attention: It is assumed the fiber cross channels are assembled below the terminal shelf.

• Use fiber cross-channel assembly (NTT899AD) to route fibers from the left side to the right side of the bay and up to the Common Photonic Layer shelf. This is needed only if a terminal shelf is mounted in the same bay with a Common Photonic Layer shelf and the terminal shelf is below the CPL shelf.

Attention: It is assumed the fiber cross channels are assembled below the terminal shelf.

• Use the left fiber riser (NTT899BD) in conjunction with the fiber cross-channel assembly (NTT899AC/AD) to manage and segregate copper and fiber cables. The left fiber riser allow systems, with left side





fiber and copper ingress/egress cables, to be properly managed and routed to and out of the Common Photonic Layer bay. The left fiber riser is an add-on to the current 22U adaptor bracket.

Figure 4-51 shows a typical fiber layout for the Common Photonic Layer.

See Installation, 323-1661-201, for more details on fiber layouts and related procedures.

Figure 4-51Common Photonic Layer fiber layout example

Each vertical fiber riserchannel of client fibersfeeds into its own optionalFiber Manager (FM).

Vertical fiber riser channelsare formed using fiber clipsfastened to the riser. Verticalfiber riser channels minimizefiber crossing.

Group and intra-systemfibers are routed behindbend limiters and areprotected from disturbanceduring client fiber operations.

Client fibers are routed intofiber riser channels based ona modularity of three (S)CMDs.

Filler

Filler





Cable management strategyThe modular design of the Common Photonic Layer architecture requires that all copper cabling follows the guidelines below:

• Copper power and signal cables must exit the left-hand side of the sub-rack.

• Power and Ethernet cables are harnessed for various configurations and typically pre-installed at the factory.

• Power cables are routed at the rear of the upright.

• Ethernet cables are routed near the front to allow easy access and manipulation in order to remove air filters from the appropriate modules as needed.

• Grounding is typically accomplished with a solid metal ground bar or with an option for a 6 AWG ground cable with a two-hole ground lug.

Connector strategyThe Common Photonic Layer is a backplane-less architecture; therefore, all module interconnections are through optical fiber and/or copper data connections. The optical fiber interconnect design features ensure minimized fibering complexity, improved installation and deployment times, and simplified fiber management.

The system uses LC or SC optical connectors in single-slider connection assemblies.

• Mechanism: double-deep slider that houses two duplex LC adapters or two SC adapters

• Type of connection: patch cord

• Connector type: duplex LC or single SC

Slider connector mechanismThe slider mechanism (see Figure 4-52) has the following attributes:

• It extends out of the horizontal plane of the faceplate to allow in-service access to individual fibers without disturbing other fibers within the faceplate for fiber handling activities such as cleaning.

• It maintains a physical level of laser hazard safety as optical connections and exposed optical apertures are constrained within the vertical plane of the faceplate.

• It provides troubleshooting access by providing optical port number identification.

• It provides expanded text information for detailed port identification with the faceplate door open and in the extended position out of the faceplate.





Figure 4-52Slider connectors (SCMD4 example)

Table 4-58 lists the Common Photonic Layer modules and their associated mechanical connection assemblies.

Table 4-58Common Photonic Layer modules and mechanical connection assemblies

Module Assembly Connector type

GMD 6 double-deep sliders LC

CMD4, SCMD4 3 double-deep sliders LC

SCMD8 4 triple-deep sliders LC

CMD44 45 duplex LC bulkhead adaptors (see Note) LC

DOSC, UOSC 1 double-deep slider LC

SLA, MLA, MLA2, LIM 4 double-deep sliders SC/LC

DRA 2 double-deep sliders SC

OPM 2 double-deep sliders LC

WSS 4 double-deep sliders LC

CMDA 3 double-deep sliders LC

Note: CMD44s do not use sliders.





Data communication connectionsAll intermodule communication connections and external communication links are through a Ethernet straight cable with RJ-45 connectors. The GMD/DOSC/UOSC supports 16 data communication ports to interconnect up to 9 CMD4s or 9 SCMDs with additional ports available for craft, interconnect local area network (ILAN), central office local area network (COLAN), and Wayside connections. Ethernet cable harnesses are available for communication between GMD/DOSC/UOSC and subtending modules.

Visual indicator strategyShelf - network element level visual indicators (GMD, UOSC and DOSC)

The GMD, UOSC and DOSC include a number of LEDs to provide alarm indications for the entire network element. See Fault Management - Alarm Clearing, 323-1661-543, for LED behaviors.

Module visual indicators (all modules)Each module includes LEDs to identify its status and operating condition including loss of signal state. See Fault Management - Alarm Clearing, 323-1661-543, for LED behaviors.

Hardware required for interface functionalitySupplementary hardware is required for the Optical Manager and Common Photonic Layer Craft interfaces.

Optical Manager Element Adapter (OMEA) hardwareFor details on OMEA hardware, see the Optical Manager Element Adapter 8.0 Planning Guide, 450-3121-601.

Site Manager hardware requirementsTable 4-59 on page 4-94 identifies the recommended hardware requirements for Site Manager for Common Photonic Layer Rel 4.0 standalone installation.

Table 4-60 on page 4-94 identifies the recommended hardware requirements for Site Manager Consolidated Craft installation.





For more information on Site Manager Consolidated Craft, see Site Manager Planning and Installation Guide, 323-1661-195.

Table 4-59Site Manager hardware requirements for Common Photonic Layer standalone installation

PC HP workstation (see Note)

Sun workstation(see Note)

Recommended hardware requirements

CD-ROM drive or network access

Required Same as the supported platform in Optical Network Manager AP requirements

(See hardware requirements for recommended hardware platforms in Optical Network Manager Applications Platform Planning Guide, Release 11 or higher)

Same as the supported platforms in OMEA platform requirements

(See the Optical Solution Release Engineering Guide, NN10740-073, for recommended hardware platforms)

Hard disk space 400 Mbyte

Monitor 256-color display or better

Processor Pentium III processor at 400 MHz or higher

RAM 256 Mbyte or higher

Note: Use the default software parameters with respect to the guided installation option of the operating system software.

Table 4-60Site Manager hardware requirements for Consolidated Craft installation

PC HP workstation (see Note)

Sun workstation(see Note)

Recommended hardware requirements

CD-ROM drive or network access

Required Same as the supported platform in Optical Network Manager AP requirements

(See hardware requirements for recommended hardware platforms in Optical Network Manager Applications Platform Planning Guide, Release 11 or higher)

Same as the supported platforms in OMEA platform requirements

(See the Optical Solution Release Engineering Guide, NN10740-073, for recommended hardware platforms)

Hard disk space 800 Mbyte

Monitor 256-color display or better

Processor Pentium III class CPU at 750 MHz or higher

RAM 512 Mbyte or higher

Note: Use the default software parameters with respect to the guided installation option of the operating system software.





Site Manager supported operating platformsTable 4-61 lists each supported operating platform and the corresponding supported operating systems.

For more information on Site Manager Consolidated Craft, see Site Manager Planning and Installation Guide, 323-1661-195.

Table 4-61Operating platforms

Operating platform Supported operating systems

Personal computer (PC)

• Windows XP

• Windows Vista Business Edition updated to Service Pack 1

Hewlett Packard (HP) workstation

• HP-UX 11i

Sun workstation • Solaris 10




Nortel Common Photonic Layer

Planning Guide, Part 1 of 2Copyright © 2004-2009, Nortel Networks, All Rights ReservedThis document is protected by copyright laws and international treaties. All information, copyrights and any other intellectual property rights contained in this document are the property of Nortel Networks. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein and this document shall not be published, copied, produced or reproduced, modified, translated, compiled, distributed, displayed or transmitted, in whole or part, in any form or media.

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.

Nortel Networks, the Nortel logo, and the Globemark are trademarks of Nortel Networks.

Printed in CanadaRelease 4.0Publication: Planning Guide, Part 1 of 2Document Status: StandardDocument Issue: Issue 1Document Release Date: September 2009

To provide feedback or to report a problem in this document, go to www.nortel.com/documentfeedback.

www.nortel.com

planning guide, part 1 of 2

Documents