NTRN15DA.1 (6500 R12.6 PhotonicLayerGuide) Issue1

6500 Packet-Optical Platform
Photonic Layer Guide, Part 1 of 3

Release 12.6
What’s inside...
The following topics for DOC-controlled fixed grid systems:
Topology Fundamentals
Photonic Optical Control
Photonic Applications
Photonic Engineering Rules
Photonic Set-Up Guidelines
Provisioning Examples
See Part 2 for the following...

The same topics as above but for non-DOC-controlled systems
See Part 3 for the following...

The same topics as above but for DOC-controlled flexible grid systems
NTRN15DA - Standard Issue 1

October 2019
Copyright© 2010-2019 Ciena® Corporation. All rights reserved.
LEGAL NOTICES
THIS DOCUMENT CONTAINS CONFIDENTIAL AND TRADE SECRET INFORMATION OF CIENA
CORPORATION AND ITS RECEIPT OR POSSESSION DOES NOT CONVEY ANY RIGHTS TO REPRODUCE
OR DISCLOSE ITS CONTENTS, OR TO MANUFACTURE, USE, OR SELL ANYTHING THAT IT MAY DESCRIBE.
REPRODUCTION, DISCLOSURE, OR USE IN WHOLE OR IN PART WITHOUT THE SPECIFIC WRITTEN
AUTHORIZATION OF CIENA CORPORATION IS STRICTLY FORBIDDEN.
EVERY EFFORT HAS BEEN MADE TO ENSURE THAT THE INFORMATION IN THIS DOCUMENT IS
COMPLETE AND ACCURATE AT THE TIME OF PUBLISHING; HOWEVER, THE INFORMATION CONTAINED IN
THIS DOCUMENT IS SUBJECT TO CHANGE.
While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed
to in writing CIENA PROVIDES THIS DOCUMENT “AS IS” WITHOUT WARRANTY OR CONDITION OF ANY
KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to
change without notice. For the most up-to-date technical publications, visit www.ciena.com.
Copyright© 2010-2019 Ciena® Corporation. All Rights Reserved
The material contained in this document is also protected by copyright laws of the United States of America and
other countries. It may not be reproduced or distributed in any form by any means, altered in any fashion, or stored
in a data base or retrieval system, without express written permission of the Ciena Corporation.
Security
Ciena® cannot be responsible for unauthorized use of equipment and will not make allowance or credit for
unauthorized use or access.
Contacting Ciena
Corporate Headquarters 410-694-5700 or 800-921-1144 www.ciena.com
Customer Technical Support/Warranty
In North America 1-800-CIENA-24 (243-6224)
410-865-4961
In Europe, Middle East, 800-CIENA-24-7 (800-2436-2247)
and Africa +44-207-012-5508
00 0800 77 454 (Slovenia)
In Asia-Pacific 800-CIENA-24-7 (800-2436-2247)
+81-3-6367-3989
+91-124-4340-600
120 11104 (Vietnam)
000 8004401369 (India)
In Caribbean and Latin 800-CIENA-24-7 (800-2436-2247)
America 1230-020-0845 (Chile)
009 800-2436-2247 (Colombia)
0800-77-454 (Mexico and Peru)
00 008000442510 (Panama)
Sales and General Information North America: 1-800-207-3714 E-mail: sales@ciena.com
International: +44 20 7012 5555
In North America 410-694-5700 or 800-207-3714 E-mail: sales@ciena.com
In Europe +44-207-012-5500 (UK) E-mail: sales@ciena.com
In Asia +81-3-3248-4680 (Japan) E-mail: sales@ciena.com
6500 Packet-Optical Platform Photonic Layer Guide, Part 1 of 3

Release 12.6 NTRN15DA Standard Issue 1
Copyright© 2010-2019 Ciena® Corporation October 2019
In India +91-22-42419600 E-mail: sales@ciena.com
In Latin America 011-5255-1719-0220 (Mexico City) E-mail: sales@ciena.com
Training E-mail: learning@ciena.com
For additional office locations and phone numbers, please visit the Ciena web site at www.ciena.com.
READ THIS LICENSE AGREEMENT (“LICENSE”) CAREFULLY BEFORE INSTALLING OR USING CIENA
SOFTWARE OR DOCUMENTATION. THIS LICENSE IS AN AGREEMENT BETWEEN YOU AND CIENA
COMMUNICATIONS, INC. (OR, AS APPLICABLE, SUCH OTHER CIENA CORPORATION AFFILIATE
LICENSOR) (“CIENA”) GOVERNING YOUR RIGHTS TO USE THE SOFTWARE. BY INSTALLING OR USING
THE SOFTWARE, YOU ACKNOWLEDGE THAT YOU HAVE READ THIS LICENSE AND AGREE TO BE BOUND
BY IT.
1. License Grant. Ciena may provide “Software” to you either (1) embedded within or running on a hardware
product or (2) as a standalone application, and Software includes upgrades acquired by you from Ciena or a Ciena
authorized reseller. Subject to these terms, and payment of all applicable License fees including any usage-based
fees, Ciena grants you, as end user, a non-exclusive, non-transferable, personal License to use the Software only in
object code form and only for its intended use as evidenced by the applicable product documentation. Unless the
context does not permit, Software also includes associated documentation.
2. Open Source and Third Party Licenses. Software excludes any open source or third-party programs supplied
by Ciena under a separate license, and you agree to be bound by the terms of any such license. If a separate
license is not provided, any open source and third party programs are considered “Software” and their use
governed by the terms of this License.
3. Title. You are granted no title or ownership rights in or to the Software. Unless specifically authorized by Ciena in
writing, you are not authorized to create any derivative works based upon the Software. Title to the Software,
including any copies or derivative works based thereon, and to all copyrights, patents, trade secrets and other
intellectual property rights in or to the Software, are and shall remain the property of Ciena and/or its licensors.
Ciena's licensors are third party beneficiaries of this License. Ciena reserves to itself and its licensors all rights in
the Software not expressly granted to you.
4. Confidentiality. The Software contains trade secrets of Ciena. Such trade secrets include, without limitation, the
design, structure and logic of individual Software programs, their interactions with other portions of the Software,
internal and external interfaces, and the programming techniques employed. The Software and related technical
and commercial information, and other information received in connection with the purchase and use of the
Software that a reasonable person would recognize as being confidential, are all confidential information of Ciena
(“Confidential Information”).
5. Obligations. You shall:
i) Hold the Software and Confidential Information in strict confidence for the benefit of Ciena using your best efforts
to protect the Software and Confidential Information from unauthorized disclosure or use, and treat the Software
and Confidential Information with the same degree of care as you do your own similar information, but no less than
reasonable care;
ii) Keep a current record of the location of each copy of the Software you make;
iii) Use the Software only in accordance with the authorized usage level;
iv) Preserve intact any copyright, trademark, logo, legend or other notice of ownership on any original or copies of
the Software, and affix to each copy of the Software you make, in the same form and location, a reproduction of the
copyright notices, trademarks, and all other proprietary legends and/or logos appearing on the original copy of the
Software delivered to you; and
v) Issue instructions to your authorized personnel to whom Software is disclosed, advising them of the confidential
nature of the Software and provide them with a summary of the requirements of this License.
6. Restrictions. You shall not:
i) Use the Software or Confidential Information a) for any purpose other than your own internal business purposes;
and b) other than as expressly permitted by this License;
ii) Allow anyone other than your authorized personnel who need to use the Software in connection with your rights
or obligations under this License to have access to the Software;
iii) Make any copies of the Software except such limited number of copies, in machine readable form only, as may
be reasonably necessary for execution in accordance with the authorized usage level or for archival purposes only;
iv) Make any modifications, enhancements, adaptations, derivative works, or translations to or of the Software;

v) Reverse engineer, disassemble, reverse translate, decompile, or in any other manner decode the Software;
vi) Make full or partial copies of the associated documentation or other printed or machine-readable matter provided
with the Software unless it was supplied by Ciena in a form intended for reproduction;
vii) Export or re-export the Software from the country in which it was received from Ciena or its authorized reseller
unless authorized by Ciena in writing; or
viii) Publish the results of any benchmark tests run on the Software.
7. Audit: Upon Ciena's reasonable request you shall permit Ciena to audit the use of the Software to ensure
compliance with this License.
8. U.S. Government Use. The Software is provided to the Government only with restricted rights and limited rights.
Use, duplication, or disclosure by the Government is subject to restrictions set forth in FAR Sections 52-227-14 and
52-227-19 or DFARS Section 52.227-7013(C)(1)(ii), as applicable. The Software and any accompanying technical
data (collectively “Materials”) are commercial within the meaning of applicable Federal acquisition regulations. The
Materials were developed fully at private expense. U.S. Government use of the Materials is restricted by this
License, and all other U.S. Government use is prohibited. In accordance with FAR 12.212 and DFAR Supplement
227.7202, the Software is commercial computer software and the use of the Software is further restricted by this
License.
9. Term of License. This License is effective until the applicable subscription period expires or the License is
terminated. You may terminate this License by giving written notice to Ciena. This License will terminate
immediately if (i) you breach any term or condition of this License or (ii) you become insolvent, cease to carry on
business in the ordinary course, have a receiver appointed, enter into liquidation or bankruptcy, or any analogous
process in your home country. Termination shall be without prejudice to any other rights or remedies Ciena may
have. Upon any termination of this License you shall destroy and erase all copies of the Software in your
possession or control, and forward written certification to Ciena that all such copies of Software have been
destroyed or erased. Your obligations to hold the Confidential Information in confidence, as provided in this License,
shall survive the termination of this License.
10. Compliance with laws. You agree to comply with all laws related to your installation and use of the Software.
Software is subject to U.S. export control laws, and may be subject to export or import regulations in other
countries. If Ciena authorizes you to import or export the Software in writing, you shall obtain all necessary licenses
or permits and comply with all applicable laws.
11. Limitation of Liability. ANY LIABILITY OF CIENA SHALL BE LIMITED IN THE AGGREGATE TO THE
AMOUNTS PAID BY YOU TO CIENA OR ITS AUTHORIZED RESELLER FOR THE SOFTWARE. THIS
LIMITATION APPLIES TO ALL CAUSES OF ACTION, INCLUDING WITHOUT LIMITATION BREACH OF
CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER
TORTS. THE LIMITATIONS OF LIABILITY DESCRIBED IN THIS SECTION ALSO APPLY TO ANY LICENSOR OF
CIENA. NEITHER CIENA NOR ANY OF ITS LICENSORS SHALL BE LIABLE FOR ANY INJURY, LOSS OR
DAMAGE, WHETHER INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL INCLUDING WITHOUT
LIMITATION ANY LOST PROFITS, CONTRACTS, DATA OR PROGRAMS, AND THE COST OF RECOVERING
SUCH DATA OR PROGRAMS, EVEN IF INFORMED OF THE POSSIBILITY OF SUCH DAMAGES IN ADVANCE.
12. General. Ciena may assign this License to an affiliate or to a purchaser of the intellectual property rights in the
Software. You shall not assign or transfer this License or any rights hereunder, and any attempt to do so will be void.
This License shall be governed by the laws of the State of New York without regard to conflict of laws provisions.
The U.N. Convention on Contracts for the International Sale of Goods shall not apply hereto. This License
constitutes the complete and exclusive agreement between the parties relating to the license for the Software and
supersedes all proposals, communications, purchase orders, and prior agreements, verbal or written, between the
parties. If any portion hereof is found to be void or unenforceable, the remaining provisions shall remain in full force
and effect.

Contents i
Contents 0
About this document ix
Topology Fundamentals 1-1

Introduction 1-3
Network topology segmentation levels 1-4
OTS configurations and subtypes 1-6
The OTS in DOC-controlled Photonic line systems 1-7
Complementing site topology information 1-20
Photonic layer directionality 1-20
Tx Path IDentifier 1-20
Photonic Domain 1-24
Optical Section 1-25
Photonic layer adjacency 1-29
Definition 1-29
Intra-OTS adjacencies 1-30
Inter-OTS adjacencies 1-30
Intra/inter-OTS adjacencies at Line Amp nodes 1-40
Standalone C-Band 50 GHz 2-port OPM adjacency provisioning 1-42
Tx/Rx adjacencies 1-46
Site Manager Photonic Profiles application 1-47
Service and Photonic Layer Interoperability (SPLI) 1-48
Photonic connections 1-61
Photonic connection attributes 1-61
Provisioning 1-64
Photonic layer topology applications 1-66
Topology collection 1-66
Optical System Topology 1-67
Optical Section Topology 1-67
Network Channel Topology 1-68
Shelf Wavelength Topology 1-69
Optical Protection Switch (OPS) circuit pack topology 1-70
Topology data communications requirements 1-74
Within a node 1-74
Between nodes 1-74
Photonic Optical Control 2-1

Benefits 2-3
Hierarchical optical control concepts 2-4
Overview of optical control within a Photonic domain 2-4
Optical control across multiple Photonic domains 2-8
DOC Sequencer and ingress Active flag 2-9
Domain Optical Controller (DOC) description 2-10
Types of control algorithms 2-10
DOC control of NTK553FB MLA2v VOA Target Loss 2-11
DOC control of NTK722AA RLA VOA Target Loss 2-18
OPS in a DOC-controlled system 2-20

ii Contents
Site Manager DOC application 2-21

DOC actions 2-30
Fault detection, auto-monitoring and fast-poller auto-monitoring cycles 2-30
Channel add/delete processes and related DOC functions 2-35
DOC actions blocking behaviour summary 2-47
Topology application affects on DOC actions 2-50
Monitoring DOC action status and progress 2-51
DOC-specific alarms 2-51
DOC faults and troubleshooting 2-53
Middle Optical Controller (MOC) description 2-57
NMCC facility 2-57
MOCs in add/drop branches 2-58
Local Optical Controller (LOC) description 2-59
Variable optical attenuators (VOAs) 2-59
CMD Local Optical Control 2-60
Other optical control mechanisms 2-64
Transponder Power Spectral Density 2-64
Automatic power reduction (APR) 2-65
Automatic Line Shutoff (ALSO) 2-66
Control of SRA-based Raman link 2-72
Raman safety mechanisms (Pump shutoff, ALSO, APR) 2-81
Transient suppression and detection 2-84
Connection Validation 2-86
Connection Validation Cable Trace or Connection Discovery Test 2-86
Connection Validation Fiber Loss Measurements Test 2-89
Connection Validation Optical Loopback Test 2-94
Connection Validation Cable Trace/Connection Discovery Test associated
alarms 2-96
Connection Validation Fiber Loss Measurements associated alarms 2-97
OTDR4 to NTK722AA RLA Connection Validation 2-97
Dark Section Conditioning 2-98
Photonic layer alarms 2-103
High Received Span Loss and Low Received Span Loss 2-104
High Fiber Loss 2-106
Connection Validation Fiber Loss Measurements Test 2-107
Channel power PMs and alarms for Colorless transponders 2-108
Channel Degrade alarm for WSS/RLA NMCC facilities 2-109
Crossed Fibers Suspected alarm 2-110
Automatic Shutoff Compromised alarm 2-112
Channel Opacity Error 2-114
Minimum Gain 2-114
Low Optical Return Loss 2-114
Gauge Threshold Crossing Alert Summary 2-115
AMPMON facility alarming on amplifier output 2-115
Incomplete Channel Topology 2-115
Adjacency Mismatch 2-116
OSPF Max Capability Reached 2-117
Alarm correlation 2-117
Alarm correlation support at CDC nodes 2-118
Alarm Correlation support on the OPS Module 2-118

Contents iii
Bias Provisioning 2-118

Photonic Differential Provisioning 2-119
Photonic Interworking 2-120
Interworking of 6500 configurations using DOC with those not using DOC 2-120
Considerations regarding nodes running different software releases 2-121
6500 T-Series interworking with 6500 S-Series/D-Series 2-121
6500 T-Series interworking with CPL 2-122
6500 S-Series and D-Series interworking with CPL 2-122
6500/CPL node level interworking 2-126
Photonic Applications 3-1

Colored Directional 3-4
Overview 3-4
Architecture 3-5
Metro ROADM 3-8
Colored Directionless 3-15
Overview 3-15
Architecture 3-17
Unsupported DIA configurations 3-34
Colorless Directionless 3-34
Overview 3-34
Architecture 3-36
Unsupported COADM OTS configurations 3-37
Colorless Directional or Colorless Direct Attach (CDA) 3-42
Overview 3-42
Architecture 3-43
Unsupported CDA with COADM direct attach configurations 3-44
Colorless Directionless, Colored Directionless and Colored Directional using 9x1
WSS 3-51
Overview 3-51
Architecture 3-53
Engineering rules and guidelines 3-53
Unsupported Colorless Directionless, Colored Directionless and Colored
Directional configurations 3-54
Low channel count Colorless Directionless 3-56
Overview 3-56
Architecture 3-57
Unsupported low channel count CD configurations 3-58
Low channel count Colorless Directionless and Colored Directional using 9x1
WSS 3-61
Overview 3-61
Architecture 3-62
Unsupported low channel count CD configurations 3-63
Colorless Directional or Colorless Direct Attach (CDA) using 20x1 WSS, FIM Type 4,
FIM Type 5 and FIM Type 6 3-64
Overview 3-64
Architecture using TID Sequence Provisioning 3-65
Architecture using Manual Adjacency Provisioning 3-71
Unsupported CDA with CCMD12 direct attach configurations 3-74
Colorless and Colored Direct Attach (CDA) using 20x1 WSS,

iv Contents
FIM Type 4, FIM Type 5 and FIM Type 6 3-74

Overview 3-74
Architecture using TID Sequence Provisioning 3-75
Colorless Directionless Contentionless (CDC) using 20x1 WSS 3-77
Overview 3-77
Architecture - greenfield deployment 3-78
Architecture - brownfield deployment 3-82
Unsupported CDC configurations 3-83
Colorless Directionless Contentionless (CDC) and Colored using 20x1 WSS 3-83
Overview CMD44 50 GHz 3-83
Architecture CMD44 50 GHz 3-84
Overview CMD44 100 GHz 3-84
Architecture CMD44 100 GHz 3-84
T-Series Colorless, Directionless, Contentionless (CDC) 3-85
Overview 3-85
Architecture 3-87
Unsupported CDC configurations 3-97
SCMD4 based Thin Terminal and Thin OADM (TOADM) 3-97
Overview 3-97
Architecture 3-98
96-channel support 3-104
96 channel operational considerations 3-105
Supported transponders for colorless and CDC line systems 3-107
OSC 3-108
OSC SFP hardware 3-109
OSC SFP carrier hardware 3-110
OSC filters embedded in circuit packs 3-110
Extra OSC drop filter module used in Raman applications 3-111
OSC Span Loss and OSC Span Loss PMs 3-113
Wayside Channel (WSC) 3-113
OSC Delay Measurement on S/D-Series and T-Series 3-115
EDFA amplified applications 3-116
Shared amplifier node 3-116
SLA-based Drop LIM 3-119
MLA2v - EDFA with embedded VOA 3-119
Compact footprint Line Amp node using SPAP-2 w/ 2xOSC 2xSFP 3-123
SLA/MLA Mux Amp 3-124
Dual XLA Line Amplifier 3-125
Raman amplified applications 3-126
Raman amplification overview 3-126
Single Line Raman amplifier (SRA) 3-128
Enhanced Service Access Module (ESAM) 3-131
Service Access Module (SAM) 3-133
Optical Time Domain Reflectometer (OTDR) 3-134
Overview 3-134
OTDR traces 3-135
OTDRCFG PMs 3-141
OTDR alarming 3-142
T-Series automatic OTDR examples 3-145
Understanding T-Series short traces 3-147

Contents v
Operational considerations for OTDR feature 3-148

Distributed ROADM 3-149
Remote CMD44 3-151
Standalone OPM C-Band 2-Port circuit pack (NTK553PA) 3-154
C-Band 2-port OPM with Enhanced CMD44 50 GHz modules 3-154
C-Band 2-port OPM at Line Amp nodes 3-155
C-Band 2-port OPM connections to LIMs at ROADM and TOADM nodes 3-157
2-port OPM as generic spectrum monitoring device 3-157
Optical protection switching using the OPS circuit pack 3-158
Overview 3-158
OPS protection architecture 3-158
OPS provisioning 3-161
OPS optical path protection options 3-162
Transceiver-Triggered OPS protection 3-163
Photonic Engineering Rules 4-1

Link engineering and capacity 4-3
C-Band wavelength plans 4-5
100 GHz SCMD4 deployment rules 4-14
Deployment guidelines for mixing 2150/4200 and 6500 100 GHz filters 4-20
Per-wavelength validation feature 4-24
Supported Transmitter/Receiver types for 6500 Photonic layer 4-28
Foreign (alien) wavelength use over 6500 Photonic Layer 4-33
OTS engineering rules 4-34
Channel access nodes of ROADM subtype 4-35
Line Amp nodes of AMP OTS subtype 4-36
Channel access node of TOADM OTS subtype 4-37
Channel access node with DIA OTS subtype 4-38
Channel access node with Colorless OADM OTS subtype 4-38
General slot sequence engineering rules 4-40
Slot sequence rules for OTSs using SRA/XLA and ESAM/SAM/XLA/MLAx 4-40
DOC engineering rules 4-42
DOC deployment rules 4-42
Photonic domain segmentation 4-43
DOC Power Audit (Calibration) engineering rules specific to Raman
applications 4-48
Photonic node engineering and shelf configuration rules 4-48
General considerations 4-48
Wavelength provisioning considerations 4-49
Line Adjacency Fiber Type provisioning with mixed fiber types 4-50
Extended depth brackets/doors when using attenuator pads 4-50
Colored Directional 1-way ROADM Terminal 4-51
Colored Directional higher degree (e.g. 2-way, 3-way, up to 8-way) ROADM/Metro
ROADM 4-78
ROADM/Metro ROADM with Mux Amp 4-103
Dynamic Gain Flattening Filter (DGFF) using 2-way ROADM 4-111
Colored Directionless 4-111
Colorless Directionless 4-113
Colorless Directional or Colorless Direct Attach (CDA) 4-114
Low channel count Colorless Directionless 4-115

vi Contents
Low channel count Colorless Directionless and Colored Directional using 9x1
WSS 4-116
Colorless Directional or Colorless Direct Attach (CDA) using 20x1 WSS, FIM Type
4, FIM Type 5 and FIM Type 6 4-116
Colorless, Directionless and Contentionless (CDC) 4-117
T-Series Colorless, Directionless and Contentionless (CDC) 4-119
OPM engineering rules 4-125
Photonic Line Amplifier node 4-127
SCMD4 based Thin Terminal or TOADM 4-140
6500 TID Consolidation 4-141
Shelf ID and Site ID Numbering 4-143
Branching engineering rules 4-144
Engineering rules related to Mode 1 capacity change mode 4-149
Photonic Set-Up Guidelines 5-1

Greenfield deployment 5-2
Commissioning a 6500 shelf equipped with photonic hardware 5-2
OTS provisioning model 5-4
Provisioning a Photonic node 5-9
Provisioning EDFA parameters, Differential Provisioning and Enabling of
alarms 5-19
Provisioning a T-Series Photonic node 5-21
Photonic Site SLAT 5-22
Photonic Network SLAT 5-23
Wavelength provisioning 5-36
Wavelength provisioning not using L0 Control Plane 5-38
Wavelength provisioning using L0 Provisioning Control Plane type 5-39
Wavelength deprovisioning using L0 Provisioning Control Plane type 5-40
Modifying an existing Photonic network 5-40
Reprovisioning amplifier parameters on an in-service system 5-41
Adding wavelengths to an in-service Photonic system 5-42
Deleting wavelengths from an in-service Photonic system 5-42
Re-routing wavelengths on an in-service Photonic system 5-43
Adding a photonic domain to an existing Photonic system 5-43
Adding a photonic domain to an existing T-Series Photonic system 5-47
Adding a CCMD16x12 or an AMP4 to an existing node 5-48
Reconfiguring a ROADM node to include a LIM in the mux/demux path 5-49
Provisioning Examples 6-1

OTS provisioning examples 6-2
Channel access OTS (ROADM subtype) - Metro ROADM configuration 6-2
Channel access OTS (ROADM subtype) - using SRA with XLA 6-5
Amplifier OTS (AMP subtype) - using LIMs 6-8
Amplifier OTS (AMP subtype) - using SRA and XLA or ESAM/SAMs and XLA/
MLAx 6-10
Channel Access OTS (COADM subtype) - CDA with COADM direct attach 6-19
Channel access OTS (ROADM subtype) - CDA with CCMD12 direct attach 6-21
Channel access OTS (ROADM subtype) - CDC 6-27
Channel access OTS (ROADM subtype) - T-Series CDC 6-30

Contents vii
Inter-OTS and intra-OTS adjacency provisioning examples 6-35

Wavelength provisioning and deprovisioning examples 6-42
Wavelength provisioning example not using L0 Control Plane (linear system, single
domain) 6-42
Wavelength deprovisioning example not using L0 Control Plane (linear system,
single domain) 6-43
Provisioning a wavelength example using SPLI (not using L0 Control Plane)
(multi-domain system) 6-45
Provisioning/deprovisioning wavelengths when a specific wavelength is used
multiple times 6-48
Wavelength provisioning example using L0 Provisioning Control Plane type and
implicit routing 6-49
Wavelength provisioning example using L0 Provisioning Control Plane type and
explicit routing 6-51
Wavelength deprovisioning example using L0 Provisioning Control Plane
type 6-52

viii Contents

About this document ix
About this document 0
DOC-controlled versus non-DOC-controlled Photonic line systems

In the context of the 6500 photonic layer deployments, configurations either
use Domain Optical Control (DOC) or do not. DOC algorithms perform
automatic per-channel power control and optimization. If DOC is not used,
per-channel power is equalized manually using pads. From this perspective:
• Single or multi-span line systems that use DOC can be further subdivided
into three subcategories:
— Colored Directional and Directionless based: using Reconfigurable
OADM (ROADM) branching and/or Thin OADM (TOADM) hardware.
This addresses the classical problem of channel performance
equalization in newer, more complex networks, and necessitates
adequate segmentation of the optical network. Addition of Direction
Independent Access (DIA) hardware further improves color-based
networks flexibility.
— Colorless, Directional and Directionless based: using
wavelength-selective colorless OADM hardware. Such hardware can
be appended to DIA hardware and then attached to ROADM backbone
OTSs (Directionless) or directly attached to ROADM backbone OTSs
(directional) and takes advantage of the ability of transponders relying
on coherent detection to select one of many different received
wavelengths impinging on a single receiver.
— Colorless, Directionless, Contentionless (CDC) based: using CDC
hardware and coherent transponders. The CDC architecture extends
the CD offering by removing potential wavelength contention issues at
ROADM branching nodes.
• The above two Colorless DOC-controlled subcategories are designed to
support flexible grid operation when using colorless channel mux demux
and flexible grid capable hardware.
• Applications which don’t use DOC consist of four sub-categories:
— Passive C-band Photonic layer:
– These provide a lower-cost deployment alternative for specific
customer applications, primarily metro DWDM systems deployed
in point-to-point, unamplified low span count or amplified single
span and multi-span configurations.
– They are based primarily on passive components imported from
the 2150/4200 platforms, although the 6500 CMD44 100 GHz filter
can also be used. A C-Band Fixed Gain Amplifier (FGA) is
available for amplified deployments.

x About this document
– Manual equalization using pads at various locations in the system

is necessary.
— Low cost single span:
– Single-span unamplified or amplified applications using the
CMD44 and OMD4 filter modules and the SLA amplifier circuit
pack. These applications offer a Layer 0 protection option based
on the Enhanced Trunk Switch (ETS) or the Optical Protection
Switch (OPS).
– Single-span unamplified or amplified applications using the
OMD4F, OMDF8 and BS5 filter modules and the FGA amplifier
circuit pack.
— Passive C-band Thin Terminal:
– These configurations are similar to the low cost single span
applications but support MLAx type amplifiers and also support
multiple spans using Line Amp nodes.
– They also support the “passive-bridge” application to
DOC-controlled systems.
— Passive L-band Photonic layer:
– These use the 5000 200 GHz 4-Channel or 16-Channel OMX filter
modules with L-Band Fixed Gain Amplifier (MLA) or L-Band LIM
(OSC filter).
With the exception of the Passive Bridge, configurations using DOC and those
that do not use DOC are by their nature not deployed together in interworking
scenarios, and no official support is provided by Ciena in such interworking
configurations.
The Photonic Layer Guide covers:

• DOC-controlled fixed grid systems in Part 1.
• Non-DOC-controlled fixed grid systems in Part 2.
• DOC-controlled flexible grid systems in Part 3.
New in this release

The following section lists new 6500 photonic features that are described in
the 6500 Packet-Optical Platform Photonic Layer Guide.
This issue of the guide covers Photonic layer features supported up to and
including 6500 Release 12.6.
Key changes in this version of the document pertain to the following:

About this document xi
New 6500 S-Series/D-Series Photonic Hardware

There is no new terrestrial hardware in this release.
New Photonic Layer applications and software features

New Photonic layer applications and software features introduced in Rel. 12.6:
• Additional arrangements of existing mux/demux structures involving
line-facing S/D-Series RLA, CMD64, plus others
• Enhancements in SRA behavior when provisioned with 0 dB gain
Concepts covered in this document

The following concepts are covered in this document:
• Topology fundamentals
• Photonic optical control
• Photonic applications
• Photonic engineering rules
• Photonic set-up guidelines
• Provisioning examples
Refer to Technical Publication 323-1851-090, Documentation Roadmap,

which identifies the series type of each 6500 shelf (for example, D-Series,
S-Series and T-Series).
References
You must use this document in conjunction with other 6500 Release 12.6
documents:
• Release 12.6 Planning Guide (NTRN10EY)

xii About this document
6500 Packet-Optical Platform technical publications

The following roadmaps identify the technical publications that support the
6500 T-Series platform and the technical publications that support the 6500
D-Series and S-Series for Release 12.6.
6500 D-Series and S-Series roadmap:
Planning a Network Installing, Managing and Maintaining and Circuit Pack-Based
Commissioning and Provisioning Troubleshooting Documentation
Testing a Network a Network a Network
Documentation Installation - Administration Fault Management - Common Equipment

Roadmap General Information and Security Performance (323-1851-102.1)
(323-1851-090) (323-1851-201.0) (323-1851-301) Monitoring
(323-1851-520) Electrical
Planning - Installation - Configuration -
(323-1851-102.2)
Parts 1, 2, and 3 2-slot Shelves Provisioning &
(NTRN10ER) Operating Parts 1 & 2 Fault Management -
(323-1851-201.1) OC-n/STM-n
Data Comms (323-1851-310) Alarm Clearing
(323-1851-102.3)
Planning & User Guide Installation - 7-slot & Parts 1 and 2
(323-1851-101) 6500-7 packet-optical Configuration - (323-1851-543) WaveLogic Ai, Flex,
Shelves Protection Switching 100G+, 40G,
Ordering Information
(323-1851-201.2) (323-1851-315) Fault Management - OSIC ISS, & SLIC10
(323-1851-151)
Module (323-1851-102.4)
Manufacturing Installation - Configuration - Replacement
Discontinued Parts 14-slot Shelves Bandwidth & Data (323-1851-545)
(323-1851-155) (323-1851-201.3) Services Parts 1,2,3 Broadband/SMUX
(323-1851-320) OTN FLEX MOTR
CLI, REST API, gRPC Installation - Fault Management - (323-1851-102.5)
(323-1851-165) 32-slot Shelves Configuration - SNMP
(323-1851-201.4) Control Plane (323-1851-740) Photonics
Latency
(323-1851-330) Equipment
Specifications Passive Chassis
(323-1851-170) Encryption and FIPS Fault Management - (323-1851-102.6)
(2150 & Photonics), Customer Visible
Pluggable Security Policy
Filters, and Modules Logs Data and Layer 2
Datasheets Overview and
(323-1851-201.5) (323-1851-840) (323-1851-102.7)
and Reference Procedures
(323-1851-180) (323-1851-340)
Licensing OTN I/F, PKT I/F, &
TL-1 Description (323-1851-210) MyCryptoTool PKT/OTN I/F
(323-1851-190) Certificate (323-1851-102.8)
Commissioning Management and
CLI Reference and Testing Quick Start
(323-1851-193) (323-1851-221) (323-1851-341)
Site Manager
Fundamentals
(323-1851-195)
SAOS-based Command Fault and MIB

Configuration Reference
Packet Services Reference Performance
(323-1851-630) (323-1851-690)
Documentation (323-1851-610) (323-1851-650)
Supporting WaveLogic Photonics 6500 Data 6500 Control Plane Submarine Networking
Documentation Coherent Select Application Guide Application Guide Application Guide
(323-1851-980) (NTRN15BA) (NTRN71AA) (NTRN72AA)
6500 Photonic Common 6500 - 5400 / 8700 Fiber Node Return 6500 AC Rectifier
Layer Guide Photonic Layer Interworking Solution Configuration (323-1851-900)
(NTRN15DA) Technical Publications (323-1851-160) (323-1851-985)

About this document xiii
6500 T-Series roadmap:
Planning a Network Installing, Managing and Maintaining and

Commissioning and Provisioning Troubleshooting
Testing a Network a Network a Network
T-Series Administration Fault Management -

Installation - Performance
Shelf Guide and Security
T-Series Shelves Monitoring
(323-1851-103) (323-1851-301)
(323-1851-201.6) (323-1851-520)
Data Communications Configuration -
Planning and Licensing Provisioning and Fault Management -
User Guide (323-1851-210) Operating Parts 1 & 2 Alarm Clearing
(323-1851-101) for T-Series Parts 1 and 2
T-Series Shelf (323-1851-311) for T-Series
Manufacturing Guide
(323-1851-544)
Discontinued Parts (323-1851-103) Configuration -
(323-1851-155) Protection Switching Fault Management -
(323-1851-315) Module
CLI, REST API, gRPC
Replacement
(323-1851-165) Configuration - for T-Series
Bandwidth (323-1851-546)
TL-1 Description for T-Series
for T-Series (323-1851-321) Fault Management -
(323-1851-191) SNMP
CLI Reference Configuration - (323-1851-740)
for T-Series Control Plane
(323-1851-194) (323-1851-330) Fault Management -
Customer Visible
Site Manager Logs
Fundamentals (323-1851-840)
(323-1851-195)
SAOS-based Command Fault and MIB

Packet Services Configuration Reference
Reference Performance
Documentation (323-1851-630) (323-1851-690)
(323-1851-610) (323-1851-650)

xiv About this document
Publication History
Document Changes
Document Date Engineer Writer Reason for Change

Release dd/mm/yyyy
Issue 1 10/17/2019 JPL JPL First official document release.

Topology Fundamentals 1-
This chapter provides a brief overview of the 6500 Packet-Optical Platform

(6500) topology fundamentals.
The following table lists the topics in this chapter.
Table 1-1
Topics in this chapter
Topic
“Introduction” on page 1-3
“Network topology segmentation levels” on page 1-4
“OTS configurations and subtypes” on page 1-6
— “The OTS in DOC-controlled Photonic line systems” on page 1-7
— “Complementing site topology information” on page 1-20
“Photonic layer directionality” on page 1-20
— “Tx Path IDentifier” on page 1-20
— “Photonic Domain” on page 1-24
— “Optical Section” on page 1-25
“Photonic layer adjacency” on page 1-29
— “Definition” on page 1-29
— “Intra-OTS adjacencies” on page 1-30
— “Inter-OTS adjacencies” on page 1-30
— “Intra/inter-OTS adjacencies at Line Amp nodes” on page 1-40
— “Standalone C-Band 50 GHz 2-port OPM adjacency provisioning” on page 1-42
— “Tx/Rx adjacencies” on page 1-46
— “Site Manager Photonic Profiles application” on page 1-47
— “Service and Photonic Layer Interoperability (SPLI)” on page 1-48
“Photonic connections” on page 1-61
— “Photonic connection attributes” on page 1-61
— “Provisioning” on page 1-64
“Photonic layer topology applications” on page 1-66
— “Topology collection” on page 1-66
— “Optical System Topology” on page 1-67

1-2 Topology Fundamentals
Table 1-1
Topic
— “Optical Section Topology” on page 1-67
— “Network Channel Topology” on page 1-68
— “Shelf Wavelength Topology” on page 1-69
“Optical Protection Switch (OPS) circuit pack topology” on page 1-70
“Topology data communications requirements” on page 1-74
— “Within a node” on page 1-74
— “Between nodes” on page 1-74

Introduction
In the last decade, terrestrial optical transport networks have been
transformed drastically. Optical reach, or the distance between electrical
regen nodes, has been increased from about 600 km to greater than 5000 km.
The advent of branching nodes (ROADM nodes) have tremendously eased
interconnections between regional networks, to a point where network
topologies no longer appear as simple ring or linear topologies but rather have
evolved to a complex mix of both, forming mesh-like topologies.
These changes to the optical transport networks have in turn granted a higher
degree of flexibility to the optical channels that ride over them. Not so long ago
limited to static point-to-point connections within a single optical transport
network, channels now potentially span multiple networks, as part of
point-to-multipoint connections that evolve more and more on a dynamic
basis.
Higher-layer control and OAM&P applications in photonic layer systems are

founded on the establishment and sharing of reliable system-level topology
information. This information can be categorized as follows:
• Network topology information, encompassing all optical connections
between equipment at a given node, and connections between nodes,
which are all defined via the optical adjacency concept;
• Channel topology information, which includes optical connections
between Tx/Rx interfaces and multiplexers/demultiplexers (also defined in
terms of optical adjacencies), as well as the photonic cross-connections
defining a channel’s path across the network.
Topology information enables, among others:

• Graphical network view representations in Site Manager and higher-layer
EMS applications
• Graphical channels paths view in Site Manager and higher-layer EMS
applications
• Channel capacity additions/deletion and other actions using DOC
• Photonic layer restoration at the OSRP or EMS layer
• Site- and network-level alarm correlation
This chapter covers the 6500 network and channel topology basics, and the
data communications requirements related to topology.

Network topology segmentation levels

In a DOC-controlled network, two levels of segmentation are defined (see
Figure 1-1 on page 1-5 and Figure 1-2 on page 1-6):
• Optical System: optical networks are first broken down in Optical Systems,
identified by a unique Optical System IDentifer (OSID).
— In Figure 1-1 on page 1-5, multiple channel access OTSs are part of
the same Optical System.
— In Figure 1-2 on page 1-6, the same optical network as Figure 1-1 on
page 1-5 is shown but using different optical system segmentation. In
this example, only two channel access OTSs are part of the same
Optical System.
— The optical system segmentation shown in Figure 1-2 on page 1-6 is
preferred. For more details, refer to “Photonic domain segmentation”
on page 4-43. Some configurations support only this type of optical
system segmentation.
• Optical Transport Section (OTS): a second level of segmentation involves
a logical association of photonic layer circuit packs, defined as the Optical
Transport Section or OTS. OTSs are either made of:
— photonic layer circuit packs servicing a given fiber plant direction. Such
OTSs are part of the Optical System backbone and thus constitute the
main Optical System building blocks;
or
— photonic layer circuit packs fulfilling a function shared amongst
multiple directions. Such OTSs connect to multiple Optical Systems
In a non-DOC-controlled network, topology information, though useful, is not

as stringent as a requirement. The Optical System concept is not used, but
the concept of the OTS applies to most applications. Rather than enabling
actual per-channel control, it is mainly used to display which channels are
deployed.

Figure 1-1
Optical network segmentation example #1

Figure 1-2
Optical network segmentation example #2
OTS configurations and subtypes

As the OTS concept is common to DOC-controlled and non-DOC-controlled
line systems, the following sections outline the various OTS types. OTS
provisioning details are provided in “OTS engineering rules” on page 4-34.
The OTSs are categorized by their configuration and subtype (Figure 1-3 on
page 1-7). The Template Family identified by the red boxes refers to the way
the OTSs are provisioned (see “OTS provisioning model” on page 5-4).

Figure 1-3
OTS configurations and subtypes
The OTS in DOC-controlled Photonic line systems

In DOC-controlled systems, there are two possible OTS configurations:
• Channel access: grouping the photonic layer circuit packs servicing a
given fiber plant direction, a Channel access OTS is equipped with
channel mux/demux filters of some sort.
• Amplifier: like the Channel access OTS, the Amplifier OTS groups
photonic layer circuit packs servicing a given fiber plant direction, but does
not have channel add/drop capabilities.
All the OTS types listed above can be mixed in a single network, as required.
6500 T-Series supports only the Channel access OTS configuration. No

mixing of OTS types is supported in this release.
Channel access OTS configuration

The Channel access OTS configuration is defined with the following subtypes:
ROADM, TOADM, DIA or COADM.
• The ROADM (Reconfigurable Optical Add-Drop Multiplexer) OTS subtype
is usually built around a WSS, an amplifier, an Optical Service Channel
(OSC) facility and some channel mux/demux filters. Many
implementations are possible, some examples of which are given below:
— Figure 1-4 on page 1-8 and Figure 1-5 on page 1-8 show a ROADM
OTS based on 50 GHz hardware. It uses the following equipment:

– one OSC SFP (either embedded in the 2xOSC circuit pack or the
SPAP-2 for the 2-slot or 7-slot shelf)
– one LIM (MLA, MLA2, MLA3, SLA or LIM)
– one cascaded LIM, if needed (SLA)
– one WSS (50 GHz 9x1 or 50 GHz 2x1)
– one BMD2, if needed
– up to two CMD44
– up to four DSCMs, if needed (not shown in the figure)
– Optional: one SAM or ESAM (as the line-facing module in front of
the MLAx)
Figure 1-4
50GHz ROADM OTS example 1
Figure 1-5
50GHz ROADM OTS example 2

— The figure below shows a ROADM OTS based on 100 GHz hardware.
It uses the following equipment:
– one Drop LIM, if needed (SLA)
– one WSS (100 GHz 5x1, 100 GHz 4x1 or 100 GHz 2x1)
– one CMD44
– up to four DSCMs, if needed (not shown in the figure)
– Optional: SAM or ESAM (as the line-facing module in front of the
MLAx)
Figure 1-6
100GHz ROADM OTS example

— The figure below shows a 50 GHz ROADM OTS based on the XLA
amplifier and SAM/ESAM/SRA.
– one XLA
– one SRA, ESAM or SAM
– one OSC SFP (contained in the SRA, ESAM or SAM)
– one WSS (50 GHz 9x1 illustrated, but any type does)
– up to two CMD44
– up to four DSCMs, if needed
Figure 1-7
50GHz ROADM OTS example with SRA/ESAM/SAM/XLA

— The figure below shows a Metro ROADM configuration. It uses the

following equipment:
– 2150 100 GHz filters (OMDF4, OMDF8, BS5)
– 6500 filters (CMD44 100 GHz, OMD4)
– Multiple Drop LIMs as needed (SLAs)
– one WSS (100 GHz 4x1, 100 GHz 2x1 or 50 GHz 9x1 if more than
4 degrees is required for branching)
– Multiple DSCMs as needed
– Optional: SAM or ESAM (as the line-facing module in front of the
MLAx)
Figure 1-8
Metro ROADM OTS example

— The figure below shows two possible implementations of the

Colorless, Directionless, Contentionless (CDC) or Colorless Direct
Attach (CDA) or Colorless Directionless (CD) ROADM OTS. It uses the
following equipment:
– one MLA3 and one OSC SFP (either embedded in the 2xOSC
circuit pack or the SPAP-2 for the 7-slot shelf)
– one XLA, plus one SRA, ESAM or SAM, plus one OSC SFP
(contained in the SRA, ESAM or SAM)
– one WSS (Flex 20x1)
Figure 1-9
CDC ROADM OTS examples
• For 6500 T-Series, the ROADM OTS subtype is supported. Channel

access OTS configuration of the ROADM subtype consists of a single
circuit pack which is the RLA 20x1 module.
• The TOADM (Thin Optical Add-Drop Multiplexer) OTS subtype is usually
built around an amplifier, an Optical Service Channel (OSC) facility and
SCMD4 channel mux/demux filters in cascade (see figure below). It
includes:
— one OSC SFP (either embedded in the 2xOSC circuit pack or the
— one LIM (MLA, MLA2, MLA3, SLA or LIM) or ESAM/MLAx (MLA3,
MLA2 or MLA)
— one cascaded LIM, if needed (SLA)
— up to nine cascaded 100 GHz serial CMD4s (C-band groups 1 through
9)
— up to four DSCMs, if needed

Attention: The TOADM OTS subtype is also used in the Coherent Select
(CS) architecture. For an overview of CS refer to Part 2. For detailed
information on the TOADM OTS in the context of CS, refer to 323-1851-980
WaveLogic Photonics Coherent Select.
Figure 1-10
TOADM OTS example

• The Direction-Independent Access (DIA) OADM OTS provides a channel

access function to multiple (backbone) fiber plant directions. These OTSs
are connected to backbone OTSs of the ROADM subtype. They are made
up of the following equipment (see figures below):
— one LIM (MLA, MLA2 or MLA3)
— one WSS (100 GHz 5x1, 100 GHz 4x1, 100 GHz 2x1, 50 GHz 9x1 or
50 GHz 2x1 [NTK553KC])
— one BMD2, if needed
— up to two CMD44
Attention: If using only one CMD44 Blue or Red then you must also use the
BMD2 since it has the embedded isolator.
The DIOADM OTS always connect to ROADM OTSs. Also, when present,
a COADM OTS can connect to a DIOADM or ROADM OTS.
Figure 1-11
100GHz DIOADM OTS
LIM WSS
Figure 1-12
50GHz DIOADM OTS
CMD44
LIM WSS
Red
A
BMD2
CMD44
B
Blue

• The Colorless OADM (COADM) OTS provides a colorless channel access

function to multiple (backbone) fiber plant directions when used in
directionless applications or provides a colorless channel access function
to single (backbone) fiber plant direction when used in directional
applications.
— At a directionless node, the COADM OTS is connected to a DIA OTS.
It is made up of the following equipment (refer to Figure 1-13 and
Figure 1-14 on page 1-16):
– One Selective Mux/Demux (SMD) 50 GHz C-Band 8x1 circuit
pack, or one SMD Flex C-Band 8x1 circuit pack, either of which
has an 8-way switch in the mux and demux directions
– Up to eight 12-Channel Colorless Mux/Demux (CCMD12 C-Band)
circuit packs
— At a directional node, the COADM OTS is directly attached to a
ROADM OTS subtype without the DIOADM present for directional
colorless traffic flow. This is known as CDA (Colorless Direct Attach).
The COADM OTS uses the SMD/FlexSMD and CCMD12, and an
optional LIM (MLA2/MLA3) as warranted by the link design (refer to
Figure 1-15 on page 1-16).
Figure 1-13
COADM OTS shown with partner DIOADM OTS at a colorless directionless node

Figure 1-14
COADM OTS shown with partner DIOADM OTS at a colorless directionless node - Flexible Grid
Ready
Figure 1-15
COADM OTS at a colorless directional node
Amplifier OTS configuration

The Amplifier OTS configuration is defined with only one subtype: AMP. There
is no 6500 T-Series Amplifier OTS configuration in this release.
• The AMP OTS subtype is usually built around an amplifier and an Optical
Service Channel (OSC) facility. Many implementations are possible, some
examples of which are given below:
— Example 1 (Figure 1-16 on page 1-18) shows two interconnected AMP
OTSs, each made up of the following equipment:

– up to four DSCMs, as needed. Note that it does not matter if a
given DSCM/pad belongs to one AMP OTS or the other
– one OSC SFP (physically inserted in the SRA, ESAM or SAM)
– zero or one XLA (One OTS includes the XLA and it’s
SRA/ESAM/SAM and the other OTS includes the
SRA/ESAM/SAM with no XLA)
– one SRA, ESAM or SAM
– one OSC SFP (physically inserted in the ESAM or SAM)
– zero or one ESAM or SAM
– one LIM or MLAx
– two OSC SFP (physically inserted in the ESAM or SAM)
– two ESAM or SAM
– two MLAx or XLA

Figure 1-16
Interconnected AMP OTSs example 1
Figure 1-17
Interconnected AMP OTSs example 2 (using SRA/ESAM/SAM/XLA)

Figure 1-18
Figure 1-19

Complementing site topology information

In some cases, specifying the OTS configuration and subtype is not sufficient
to inform the topology database of all the optical connections at a node.
Because they are shared among multiple OTSs, some circuit packs are not
defined as part of an OTS, and their connections must be specified otherwise.
For instance:
• NTK554BA 2xOSC circuit pack or NTK555NA/NB SPAP-2 w/2xOSC
2xSFP circuit pack
— OSC SFPs are inserted in either circuit pack, and it is the OSC
facilities for a given SFP that are assigned independently to each OTS
they serve.
— Ethernet Wayside Channel (WSC) facilities are also linked to a given
OSC SFP facility, and face the same OTS direction as the OSC SFP
facility.
• NTK553PA C-Band 50 GHz 2-port OPM
— At a Line Amp node, the 2-port OPM can monitor the Line B facilities
output power of the West-facing as well as East-facing amplifiers,
which belong to two different Line Amplifier OTSs
— When used together with eCMD44
— When used in a standalone configuration, the 2-port OPM connects to
an arbitrary monitor port whose location is not accounted for by OTS
provisioning
• In CDC applications and CDA with CCMD12 direct attach applications, the
FIM and CCMD are shared equipment by nature and as such do not
belong to any OTS in particular. Their connectivity to the other equipment
at a node is established through TID sequence provisioning rather than
OTS provisioning. In some CDA configurations manual provisioning may
be required.
Photonic layer directionality

Regardless of the directionality of the channels supported by Optical
Systems, the underlying photonic layer architecture requires bidirectional
control of per-channel power. This is done by DOC via automatic per-channel
power control and optimization.
The ability for topology to properly build itself rests on a reliable data
communication foundation and proper convention for signal flow. In 6500, the
convention is known as Tx Path IDentifier (Tx Path ID).
Tx Path IDentifier
A solid data communications foundation allows the optical system topology to
be constructed using the concept of Tx Path ID.

The direction between OTSs within an Optical System, and between Optical
Systems is defined using the Tx Path IDentifier (Tx Path ID) parameter. The
Tx Path ID is:
• an integer number;
• it must be consistently odd or even for a particular direction in an Optical
System;
• it is provisioned on a per OTS basis.
— In the case of a DIA OTS which may be connected to multiple
backbone ROADM OTSs, and a COADM OTS, which may be
connected to a partner DIA OTS, the Tx Path ID for these latter two
OTS subtypes may not be exclusively tied to one backbone direction
and hence the Tx Path ID value may be chosen independently of the
backbone directions.
— In the case of a COADM OTS used in the CDA configuration, the
COADM OTS is connected directly to a ROADM OTS backbone
direction.
– Setting the COADM OTS Tx Path ID to be odd or even to be
consistent with the ROADM OTS Tx Path ID is recommended due
to the directional nature of the traffic path.
– However, software does allow the Tx Path ID to be chosen
independently of the backbone direction (ROADM OTS Tx
PathID).
Each OTS supporting a Tx Path ID also has an Rx Path ID, automatically

provisioned based on the Tx Path ID. For example:
• if Tx Path ID is 1, Rx Path ID is 2
The following rules apply to Tx Path ID:

• Each OTS in a shelf must have unique Tx and Rx Path IDs. The Path IDs
need only be unique to a shelf, not to a node although it is recommended
that the Tx Path IDs be unique to a node.
• At a Line Amp node, in order to have more simplicity, Tx and Rx Path IDs
are allowed to be provisioned only for one OTS and the paths IDs for the
other OTS are automatically adapted from it. For example, if for OTS 1 the
Tx path ID is provisioned as 1 (and hence Rx path ID as 2), the Tx path ID
for OTS 2 is automatically set to 2 (and hence Rx path ID as 1).
• The Tx Path ID must be an integer between 1 and 254.

An example of Tx Path ID provisioning in branched network is shown in the

illustrations that follow:
• Figure 1-20 shows a system with DOC-controlled OTSs of the Channel
Access (ROADM).
• Figure 1-21 on page 1-23 shows a system with DOC-controlled OTSs of
the Channel Access (ROADM) and Line Amplifier (Amplifier) subtypes.
• Figure 1-22 on page 1-23 shows a ring system containing OTSs of the
Channel Access (ROADM, COADM) and Line Amplifier (Amplifier)
subtypes. This example depicts COADM OTSs in CDA configurations.
• Figure 1-23 on page 1-24 shows a ring system with a linear segment,
containing OTSs of the Channel Access (ROADM, DIA, COADM) and Line
Amplifier (Amplifier) subtypes. OTSs of the Passive subtypes are also
shown, for which the operator can ensure consistency in terms of
directionality as well. Note that the passive layer operates independently
of the DOC-controlled 6500 layer.
Figure 1-20
Tx Path ID example - Channel Access (ROADM)

Figure 1-21
Tx Path ID example - Channel Access (ROADM) & Line Amplifier (Amplifier) OTSs
OTS 2 OTS 2
TX=1 OTS 2
OTS 1 TX=1 TX=1
Rx=2 Rx=2
TX=1 Rx=2
Rx=2
OTS 1 OTS 1
OTS 1 TX=4 TX=2
OTS 3 OTS 1
TX=2 Rx=3 Rx=1
TX=5 TX=4
Rx=1 Rx=6 Rx=3
OTS 1
TX=6
Rx=5
OTS 2
TX=5
Rx=6
OTS 1
TX=8
Rx=7
Legend
= ODD Path ID
= EVEN Path ID
= OSID1
= OSID2
Figure 1-22
Tx PathID example - Channel Access (ROADM, COADM) with CDA and Line Amplifier OTSs

Figure 1-23
Tx PathID example - Channel Access (ROADM, DIA, COADM, Passive) and Line Amplifier
(Amplifier, Passive) OTSs
Photonic Domain
A photonic domain, labeled with an OSID, identifies the boundaries of an
Optical System over which software algorithms perform automatic
per-channel power control and optimization.
A single direction is controlled by one channel access OTS (of the ROADM or
TOADM subtype) that is provisioned to be the Domain Optical Controller
(DOC) for that direction. Accordingly, there are always two DOC facilities in
each DOC-controlled Optical System identified with a single OSID. For further
information, see “Domain Optical Controller (DOC) description” on page 2-10.
The topology of a photonic domain is deemed valid or complete when:

• It has one and only one OTS provisioned as a DOC for the odd Tx Path ID
direction.
• It has one and only one OTS provisioned as a DOC for the even Tx Path ID
direction.
• For photonic domains that have more than 2 channel access OTSs in a
linear configuration, the DOC instance is provisioned at the head-end OTS
(in the traffic direction for a given path).

• For photonic domains that have more than 2 channel access OTSs in a
ring configuration, both DOC instances are provisioned at the same node
(the two DOC instances must have the same Site ID).
• There is an OTS provisioned for all nodes in the Photonic domain and the
OTS provisioning is correct (OSID, Tx Path ID, etc.).
• There are no data communication failures within the direction.
The system informs users about the state of the Photonic domain via:
• The “DOC Invalid Photonic Domain” alarm if the corresponding DOC fails
to collect its topology information (see “Photonic layer topology
applications” on page 1-66).
• The Logs button of the Site Manager DOC application
(Configuration->Photonic Services-> Domain Optical Controller (DOC)
and the Logs button), which provides information about whether the
Optical System topology was successfully built or not at the DOC site (see
“Optical System Topology” on page 1-67).
• The “Overall Status” field of the Site Manager DOC application
(Configuration->Photonic Services->Domain Optical Controller (DOC)).
Optical Section
A 6500 system photonic domain contains one or more optical sections. Single
section photonic domains are preferred. Furthermore, some configurations
like CDA with CCMD12 direct attach and 6500 T-Series support only single
section photonic domains. For more details, refer to “Photonic domain
segmentation” on page 4-43.
• An optical section is the portion of the Photonic domain delimited by two
consecutive channel access (ROADM or TOADM or a combination of the
two) OTSs.
• As such, an optical section in a given direction encompasses one ROADM
or TOADM OTS, called optical section head, and one ROADM or TOADM,
called optical section tail.
• The optical section may or may not include Line Amp OTSs in between the
Channel access OTSs. 6500 T-Series does not support Line Amp OTSs in
between the Channel access OTSs in this release.
Figure 1-24 on page 1-26 shows a typical optical network made of two
interconnected Optical Systems, where ROADM and Line Amp OTSs are
identified along with their respective Tx Path IDs.
Figure 1-25 on page 1-27 summarizes the Optical System, Photonic domain
and Optical section definitions with the Figure 1-24 on page 1-26 network as
a reference.

Figure 1-26 on page 1-28 shows a typical 6500 T-Series optical network made
of five interconnected Optical Systems, where ROADM OTSs are identified
along with their respective Tx Path IDs.
Figure 1-24
Typical optical network
OTS1 OTS2
OSC OSID1 OSID1 OSC
Tx Path ID:4 Tx Path ID:1
OSID1 Even OSID1 Odd

Path ID CMD44 CMD44 Path ID
DOC OTS DOC OTS
OTS3
OSID2
Tx Path ID:5
CMD44
OSC
OSID2 Odd
Path ID
DOC OTS
SITE A
OSC
CMD44
OTS2
OSC
OSID1
Tx Path ID:1 OTS1
OSID1
Tx Path ID:4
SITE D SITE B
OTS2
OSC
OSID1
OTS1 Tx Path ID:1
CMD44
OSID1
Tx Path ID:2
OSC
SITE C
OSID2 Even
OSC
Path ID
DOC OTS
CMD44
OTS3
OSID2
Tx Path ID:8
OTS2 OTS1
OSC OSID1 OSID1 OSC
CMD44 CMD44

Figure 1-25
Optical systems, Photonic domains, and Optical sections from above figure
OTS1
OTS2
OTS1
OTS2
A A
OTS3 OTS3
OTS2 OTS1
D B
OTS1 OTS2
OTS3 OTS3
OTS2
OTS1
OTS2
OTS1
C C
Optical system 1 Optical system 2

(Ring system) (Linear system)
OTS1
OTS2
OTS1
OTS2
A
OTS3
OTS3
OTS2
Odd Path ID Domain
OTS1
Odd
D Even Path ID Domain B Path ID Even
OTS1 OTS2
Domain Path ID
OTS3
Domain
OTS3
OTS2
OTS1
C
OTS2
OTS1
C
Photonic Domains Photonic Domains

in Optical system 1 in Optical system 2
Opt Opt
section 1 section 3
OTS1
OTS2
A
OTS1
OTS2
Opt A
OTS3
OTS3
section 1
OTS1 Opt
Odd Path ID Domain
D B section 1
Even Path ID Domain
OTS2
Opt
section 1
OTS3
Opt
OTS3
section 2
OTS2
OTS1
C
OTS2
OTS1
C
Opt
section 3 Opt
Optical sections in section 2 Optical sections in
Photonic Domains Photonic Domains
in Optical system 1 in Optical system 2

Figure 1-26
Typical optical network with single optical section photonic domains

Photonic layer adjacency

Definition
The 6500 Photonic layer defines the concept of adjacency as a logical
representation of the physical link between two given elements of the optical
network.
Adjacencies are used to build the intra-OTS, inter-OTS, and overall system
topology. Knowledge of such adjacencies is crucial for various OAM&P and
topology applications like:
• DOC
• Network- and Site-Level Alarm Correlation
• Visualization
• Network Channel Topology
• Optical System Topology
• Shelf Wavelength Topology
• Refer to “Photonic layer topology applications” on page 1-66 that
automatically discover and build the nodes and channels maps which
allow automatic optimization.
Different categories of adjacencies exist, and whenever possible, the system
attempts to derive as many adjacencies as possible. For instance, a specific
Photonic circuit pack port can only connect to one and only one other possible
Photonic circuit pack port within an OTS. This adjacency is automatically
derived.
However, in some cases the system cannot determine how the user has
optically interconnected the circuit packs and therefore such adjacencies must
be user-provisioned. For example, a given WSS switch port could be
connected to another WSS as part of an inter-OTS adjacency.
For configurations using FIMs, all adjacencies are either automatically system
derived through the TID sequence method or manually entered depending on
the configuration being used.
In the Site Manager Equipment & Facility Provisioning application,

adjacencies that are derived by the system have a Status of “Derived”, while
user-provisioned adjacencies have a Status of “Unverified”.
Adjacencies (except for TX adjacencies) are defined against a circuit

pack/module output port. When provisioning an adjacency against a specific
circuit pack/module port, the following parameters must be provisioned:
• Adjacency Type: equipment type (for example, CMD) of the equipment
connected to the port for which the adjacency is being provisioned.

• Expected Far End Address: identifies the equipment that connects to the
port for which the adjacency is being provisioned. This equipment is
identified using a format specified by the Expected Far End Address
Format parameter.
• Expected Far End Address Format:
— Default format is TID-Shelf-Slot-Port.
— For the WLAi MOTR/FOTR circuit packs with integrated OPS, the
format is TID-Shelf-Slot- PortLabel (TID-SH-SL-PRTLBL, where the
Label is in xPy format (xPy = 1P1 or 1P2).
— For MPO ports, the format is TID-Shelf-Slot-Port-Subport (default).
Intra-OTS adjacencies
Definition
Intra-OTS adjacencies define how Photonic equipment within an OTS is
optically interconnected. All intra-OTS adjacencies are automatically derived
when basic OTS parameters and the slot sequence for a given OTS type are
provisioned (see “OTS provisioning model” on page 5-4).
Inter-OTS adjacencies
Inter-OTS adjacencies define how Photonic circuit packs equipped in different
OTSs are optically interconnected. These must be manually provisioned.
The 6500 Photonic layer supports the following inter-OTS adjacencies:

Connection between nodes
• Line adjacency (user-provisioned) defines which ports are used to
interconnect the circuit packs between two nodes (see Figure 1-27 on
page 1-32). The system automatically detects the Actual Far End Address
that an output port is connected to since this information is conveyed by
the OSC. However, the Expected Far End Address and Expected Far End
Address Format must be user-provisioned.
Different line adjacencies are listed below:

• LIM Line adjacency: defines which LIM ports are used to interconnect the
LIM circuit packs between two nodes.
• For SRA/ESAM/SAM Line adjacencies: defines which SRA/ESAM/SAM
ports are used to interconnect the SRA/ESAM/SAM circuit packs between
two nodes.
• RLA Line adjacency: defines which RLA ports are used to interconnect the
RLA modules between two nodes. The RLA ports used to interconnect
RLA between two nodes are output port 5 and input port 8.

Connection between ROADM OTSs at a node (does not apply when using FIMs
to interconnect ROADM OTSs
• WSS-WSS adjacency (user-provisioned): defines which WSS switch
ports are used to interconnect WSS circuit packs between two OTSs
within a node (see Figure 1-28 on page 1-33). It is recommended that
WSS Switch 1 (i.e. ports 3 and 4) be used to connect two WSS circuit
packs sharing the same OSID.
• RLA-RLA adjacency (user-provisioned): defines which RLA 5x1 switch
ports are used to interconnect RLA circuit packs between two OTSs within
a node. It is recommended that RLA Switch 1 (i.e. ports 3 and 4) be used
to connect two RLA circuit packs sharing the same OSID.
Connections for the DIA configuration

• WSS-WSS adjacency (user-provisioned): defines which WSS switch
ports are used to interconnect WSS circuit packs between a ROADM OTS
and a DIA OTS (see Figure 1-28 on page 1-33).
Connections for the Colorless Directionless configuration

• LIM-SMD adjacency (user-provisioned) between DIA OTS LIM port 5 and
COADM OTS SMD port 9 (see Figure 1-29 on page 1-34).
• SMD-LIM (user-provisioned) adjacency between COADM OTS SMD port
10 and DIA OTS LIM port 8 (see Figure 1-29 on page 1-34).
Connections for the Colorless Directional node (CDA) using 9x1 WSS or 2x1
WSS (with LIM)
• LIM-WSS adjacency (user-provisioned) between COADM OTS LIM port 5
and ROADM OTS WSS branch port (3,5,7,9,11 or 13) (see Figure 1-30 on
page 1-35).
• WSS-LIM adjacency (user-provisioned) between ROADM OTS WSS
branch port (4,6,8,10,12,or 14) and COADM OTS LIM port 8 (see Figure
1-30 on page 1-35).
Connections for Colorless Directional node (CDA) using 9x1 WSS or 2x1 WSS
(without LIM)
For CDA configurations that use the NTK553KC 2x1 50 GHz WSS in the
COADM OTS, the COADM LIM may not be required in certain cases where
the link design supports the SMD/FlexSMD connection to the lower loss local
add/drop ports 5,6 of the WSS.
• SMD-WSS adjacency (user-provisioned) between COADM OTS SMD
port 10 and ROADM OTS WSS local add/drop port 5.
• WSS-SMD (user-provisioned) adjacency between ROADM OTS WSS
local add/drop port 6 and COADM OTS SMD port 9.

Figure 1-27
Inter-OTS adjacencies (example with channel access ROADM node)

Figure 1-28
Inter-OTS adjacencies (example with channel access ROADM nodes and DIA)

Figure 1-29
Inter-OTS adjacencies (Colorless OADM Example)

Figure 1-30
Inter-OTS adjacencies (CDA Example)

Connection between TOADM OTSs at a node

For symmetrical TOADM configurations (see Figure 1-31 on page 1-37):
• CMD-CMD adjacency (user provisioned): defines the connection between
the upgrade output port 12 of the last 100 GHz SCMD4 at the end of the
cascade in one facing TOADM OTS with the common input port 11 of the
last 100 GHz SCMD4 at the end of the cascade of the other facing TOADM
OTS.
For asymmetrical TOADM configurations (see Figure 1-32 on page 1-38):

• CMD-LIM adjacency (user provisioned): defines the connection between
upgrade output port 12 of the last 100 GHz SCMD4 at the end of the
cascade in one facing TOADM OTS with the LIM Line B input port 6 of the
other facing TOADM OTS which does not have any SCMD4s provisioned.
• LIM-CMD adjacency (user provisioned): defines the connection between
the LIM Line A output port 7 of one facing TOADM OTS without SCMD4s
provisioned, and the last 100 GHz SCMD4 upgrade input port 11 at the
end of the cascade of the other facing TOADM OTS.
For TOADM configurations when neither TOADM OTS has any SCMD4s
provisioned (see Figure 1-33 on page 1-39):
• LIM-LIM adjacency for TOADM (user provisioned): defines the connection
between the LIM Line A output port 7 of one facing TOADM OTS with the
LIM Line B input port 6 of the other facing TOADM OTS.

Figure 1-31
Inter-OTS adjacencies for symmetric TOADM
OTS2
8
5
Line B Out
MLA
PEC: NTK552BA
Line A In
Slot 13
A
B
Mon 2 (A Out)
6500
OSC A Out
(B Out)
Line A Out
Mon 1
OSC B In
6 Line B In
7
3
4
1
2
2x OSC PEC: NTK554BA
OSC1 Out
OSC
1
WS
C3
1 LC
OSC1 In
SCMD4 Ch1 Out
Slot 12
4
OSC2 Out 2 3
OSC
WS
C4
Ch1 In
2
MUX / DEMUX
OSC2 In
2 Ch2 Out LC
Common 6
LC In 5
Slot 14 1 Ch2 In
2 Ch3 Out LC
Common 8
Out
11 7
Upg In Ch3 In
12
Upg Out Ch4 Out LC
10
9
Ch4 In
CMD-CMD ADJACENCY
LC
SCMD4 Ch1 Out
Slot 11
USER PROVISIONED
4
3
Ch1 In
MUX / DEMUX
Ch2 Out LC
Common 6
LC In 5
1 Ch2 In
2 Ch3 Out LC
Common
DSCM and pad placement

8
Out
11 7
Upg In Ch3 In
as per link engineering

12
Upg Out Ch4 Out LC
10
CMD-CMD ADJACENCY
9
Ch4 In
USER PROVISIONED
analysis
Ch4Out
10
DSCM (Optional)
In 9
Upg LC Ch4In
11
Ch3Out Pad (Optional)
MUX / DEMUX
12 8
Out
Upg Common In
7
1 LC Ch3In
2 Ch2Out
LC Common Out 6
5
LC Ch2In
Slot 4
Ch1Out
4
SCMD4 3
LC Ch1In
Ch4Out
10
In 9
11
Upg LC Ch4In
Ch3Out
MUX / DEMUX
12 8
Out
Upg Common In
7
1 LC Ch3In
2 Ch2Out
LC Common Out 6
2x OSC
5
PEC: NTK554BA LC Ch2In
Ch1Out
Slot 3
4
OSC1 Out
OSC
1
WS
3
C3
SCMD4
1
LC Ch1In
1
OSC1 In
OSC2 Out 2
OSC
WS
C4
2
OSC2 In
Slot 1
2
OSC B In 3
4
6
7
1
Mon 2 (A Out)
OSC A Out
Line A Out
Line B In
Mon 1 (B
Out)
6500
B
PEC: NTK552BA
Slot 2
A
OTS1
Line B Out
Line A In
MLA
5
8

Figure 1-32
Release 12.6
WS WS
WS WS
C4 C3
C4 C3
2x OSC
2x OSC

OSC OSC
Slot 14
OSC OSC
Slot 1
2 1
2 1
OSC2 In
OSC1 In
OSC1 Out
PEC: NTK554BA
OSC2 In
OSC1 In
OSC1 Out
PEC: NTK554BA
1
1
2
OSC2 Out 2
1
1
2
OSC2 Out 2
CMD-LIM ADJACENCY
Copyright© 2010-2019 Ciena® Corporation

USER PROVISIONED
MLA 6500 6500 MLA
PEC: NTK552BA Mon 1 (B Mon 1 PEC: NTK552BA
Out) 1 (B Out)
1
2 2
Mon 2 (A Out) Mon 2 (A Out)
Inter-OTS adjacencies for asymmetric TOADM
OSC B In 3
3 OSC B In
4 4
OSC A Out OSC A Out
Line A In Line A Out Line B In Line B Out
8 A 7 6 B 5
5 B 6 7 A 8
Line B Out Line B In Line A Out Line A In
Slot 2 Slot 13
LC
LC
2
1
2
1
11
11
12
12
Upg
Upg
In
In
Out
Out
Upg
Upg
SCMD4
SCMD4
LIM-CMD ADJACENCY
Common In
Common In
Slot 3 Slot 4
Common Out
Common Out
MUX / DEMUX MUX / DEMUX
USER PROVISIONED
Ch1Out
Ch2Out
Ch3Out
Ch4Out
Ch1Out
Ch2Out
Ch3Out
Ch4Out
9
9
3
4
5
6
7
8
3
4
5
6
7
8
10
10
LC Ch1In
LC Ch2In
LC Ch3In
LC Ch4In
LC Ch1In
LC Ch2In
LC Ch3In
LC Ch4In
OTS1 OTS2
DSCM (Optional) DSCM and pad placement

Pad (Optional) analysis
October 2019
NTRN15DA Standard Issue 1
Figure 1-33
Release 12.6
WS WS
WS WS
C4 C3
C4 C3
2x OSC
2x OSC
OSC OSC
Slot 14

OSC OSC
Slot 1
2 1
2 1
OSC2 In
OSC1 In
OSC1 Out
PEC: NTK554BA
OSC2 In
OSC1 In
OSC1 Out
PEC: NTK554BA
1
1
2
OSC2 Out 2
1
1
2
OSC2 Out 2
6500

MLA 6500 MLA
Out) 1 (B Out)
1
2 2
OSC B In 3
3 OSC B In
4 4
OSC A Out OSC A Out
Line A In Line A Out Line B Out
8 A 7 6 Line B In B 5
5 B 6 7 A 8
Slot 2 Slot 13
LIM-LIM ADJACENCY
USER PROVISIONED LIM-LIM ADJACENCY
USER PROVISIONED
Inter-OTS adjacencies for no SCMD4s provisioned in the TOADM OTS
OTS1 OTS2
October 2019
Intra/inter-OTS adjacencies at Line Amp nodes

Intra-OTS and inter-OTS adjacencies at Line Amp nodes are defined as
follows.
For an uncompensated Line Amp node without OPM, refer to:

— Figure 1-34 on page 1-41
• Intra-OTS
— LIM-OSC adjacency (derived) defines interconnection ports between
the LIM circuit pack and the OSC SFP pluggable.
— SRA-XLA (derived): defines interconnection ports between the SRA
circuit pack and the XLA circuit pack in an OTS. These are
automatically provisioned (derived) if the SRA and XLA are part of the
same OTS. The connection between the XLA Line B output port 5 with
the SRA/ESAM/SAM Line B input port 6 of the same AMP OTS.
— ESAM/SAM-XLA/MLAx (derived): defines interconnection ports
between the ESAM/SAM circuit pack and the XLA/MLAx circuit pack
in an OTS. These are automatically provisioned (derived) if the
ESAM/SAM and XLA/MLAx are part of the same OTS. The connection
between the XLA/MLAx Line B output port 5 with the ESAM/SAM Line
B input port 6 of the same AMP OTS.
• Inter-OTS
— LIM-LIM adjacency for AMP OTS (derived): defines the connection
between the LIM Line A output port 7 of one facing AMP OTS with the
LIM Line B input port 6 of the other facing AMP OTS.
— SRA-XLA (derived): defines interconnection ports between the SRA
circuit pack and the XLA circuit pack in different OTSs. The connection
between the XLA Line A output port 7 of one facing AMP OTS with the
SRA Line B input port 6 of the other facing AMP OTS.
— ESAM/SAM-XLA/LIM (derived): defines interconnection ports
between the ESAM/SAM circuit pack and the XLA/LIM circuit pack in
different OTSs. The connection between the XLA/LIM Line A output
port 7 of one facing AMP OTS with the XLA/LIM Line B input port 6 of
the other facing AMP OTS.

Figure 1-34
Intra-OTS and inter-OTS adjacencies at Line Amp node without OPM
Figure 1-35
Intra-OTS and inter-OTS adjacencies at SRA/ESAM/SAM-XLA Line Amp node without OPM

Figure 1-36
Intra-OTS and inter-OTS adjacencies at ESAM/SAM-MLAx Line Amp node without OPM
Figure 1-37
Intra-OTS and inter-OTS adjacencies at ESAM/SAM-XLA-XLA-ESAM/SAM Line Amp node without
OPM
Standalone C-Band 50 GHz 2-port OPM adjacency provisioning

The OPM circuit pack is not provisioned as part of an OTS.
However, OPM adjacency types exist to define the logical connections

between the standalone OPM and:
• LIM/XLA circuit packs monitor ports

• Enhanced CMD44 50 GHz module monitor ports
NTK553PA standalone OPM auto-provisioning at Line Amp nodes

OPM adjacency types exist to define the topology between LIM monitor ports
and OPM input ports.
The NTK553PA Optical Power Monitor (OPM C-Band) 2 Port circuit pack can
be used at 6500 Line Amp nodes to provide per-channel power monitoring
capabilities.
• The OPM can be shared between two LIM circuit packs that are in different
OTSs within the same shelf. For instance, both OPM ports could be used
to monitor the per-channel power exiting the Line B amplifier at each node.
• LIM to OPM adjacencies are auto-provisioned when the OTS is
provisioned or when slot sequencing is completed.
• For SRA/ESAM/SAM-XLA amplifier configurations, the OPM is connected
to the XLA monitor ports.
When there is only one OPM circuit pack equipped in the shelf, the following
adjacencies are auto-provisioned:
• LIM in lower numbered OTS port 1 (Line B MON) to OPM port 1
• LIM in higher numbered OTS port 1 (Line B MON) to OPM port 2
When there are two OPM circuit packs equipped in the shelf, the following
adjacencies are auto-provisioned:
• LIM in lower numbered OTS port 1 (Line B MON) to higher slot number
OPM port 1
• LIM in higher numbered OTS port 1 (Line B MON) to higher slot number
OPM port 2
Attention: The above-mentioned auto-provisioned OPM adjacencies can

be manually changed to be something different if desired.
For adjacency provisioning at uncompensated or compensated Line Amp

nodes with one or two OPMs, refer to Figure 1-38 on page 1-44 and Figure
1-39 on page 1-45 respectively.
Note that in order to delete the OPM equipment, the OPM-LIM adjacencies
must be deleted from the OPM equipment.

Figure 1-38
Intra-OTS and inter-OTS adjacencies at Line Amp node with single OPM

Figure 1-39
Intra-OTS and inter-OTS adjacencies at Line Amp node with two OPMs

NTK553PA standalone OPM using Enhanced CMD44 50 GHz

A standalone OPM circuit pack can be used with Enhanced CMD44 50GHz
modules connected to the CMD44 monitor port. As described in “Standalone
50 GHz 2-port OPM and Enhanced CMD44 50 GHz deployment rules” on
page 4-126, an OPM can only be fibered to 2 CMD44 modules belonging in
the same OTS.
The OPM adjacency type exists to define the topology between CMD44
monitor ports and OPM input ports. The Enhanced CMD44 50 GHz monitor
port (port 92) ADJ facility Expected Far End Address is manually provisioned
to point to the OPM port (port 1 or 2) using the Site Manager
Configuration->Equipment & Facility Provisioning application. The
corresponding adjacency at the OPM port is auto-derived.
Tx/Rx adjacencies
Tx/Rx adjacencies define the transponders that are optically connected to a
Channel Mux/Demux port. They are necessary for higher layer OAM&P
applications. Their provisioning is the first step in provisioning channels, after
OTS provisioning has been completed.
Various Channel Mux/Demux types are available for which Tx/Rx adjacencies
can be provisioned:
• In colored configurations:
— CMD44 (Figure 1-40 on page 1-47)
— SCMD4
— OMD4, OMDF4, OMDF8
— CMD64
— CMD96
• In colorless configurations:
— CCMD12
• In colorless-directionless-contentionless (CDC) configurations:
— CCMD8x16
• In T-Series colorless-directionless-contentionless (CDC) configurations:
— CCMD 16x12
— CCMD 8x4
Tx/Rx adjacencies are user-provisioned.
Tx/Rx adjacency information helps the Network Channel Topology application

create the channel paths through the 6500 Photonic layer (see “Network
Channel Topology” on page 1-68). It also informs the Domain Optical

Controller (DOC, see “Domain Optical Controller (DOC) description” on page

2-10) of specific transponder characteristics (for example, acceptable
transponder optical power levels), such that proper power balancing can take
place.
Tx/Rx adjacency provisioning is necessary for alarm correlation.
Tx/Rx adjacency provisioning is done using the Site Manager Equipment &
Facility Provisioning application by selecting the Channel Mux/Demux
equipment and the specific Channel Mux/Demux port the transponder
connects to. Then selecting either the ADJ-TX facility type for Tx adjacency
provisioning or the ADJ-RX facility type for Rx adjacency provisioning.
Figure 1-40
Tx/Rx adjacencies
2 x OSC PEC: NTK554BA

OSC1 Out 1
WSC OSC
1 1 OSC1 In
1
OSC2 Out 2
WSC OSC
2 2 OSC2 In
2
Loc: 100. 01 Shelf 1 Slot 4
6500 WSS 6500 MLA

PEC: NTK553EA PEC: NTK552BA
Monitor 1 Mon 1 (B Out)
1 1
OPM 2 2
Monitor 2 Mon 2 (A Out)
Switch 1 In OSC B In
3
3
4
4 OSC A Out
Common In
Switch 1 Out
17
Switch 2 In Line B In Line B Out
5
6 B 5
6
Switch 2 Out 7 A 8
Line A Out Line A In
Switch 3 In
7 9:1
8
Switch 3 Out Loc: AA Shelf X Slot Y
Switch 4 In
9
10
Switch 4 Out
1:5
Switch 5 In
11
12
Switch 5 Out 18
Common Out
1X5 w/upgd
13
WSS 100
Switch 6 In
14
Switch 7 In Tx Adjacency (odd numbered ports)
15 (User-provisioned)
Switch 8 In
16
Switch 9 In
Rx Adjacency (even numbered ports)
CMD44 LC (User-provisioned)
Ch 1 In 1
PEC: NTT862AA
2
Ch 1 Out
LC
44 Channel MUX/DEMUX
Ch 2 In 3
LC
90 Common Out 4
Ch 2 Out
89
Common In
LC
Ch 43 In 85
86
Ch 43 Out
LC
Ch 44 In 87
88
Ch 44 Out
Site Manager Photonic Profiles application

The Site Manager Photonic Profiles application allows users to:
• customize a CMD/CCMD for a specific transponder type
— Customizing a CCMD for a specific transponder type is done to ensure
that the CCMD EDFA Maximum Total Output Power limit is not
exceeded for a given Tx/Rx type and to minimize noise funneling
thereby maximizing Tx OSNR.
— Customizing a CMD for a specific transponder type is done when the
CMD is connected to an amplifier and ensures that the Tx power out
of the CMD does not saturate the connecting amplifier and violate
laser safety requirements.

— A CMD/CCMD is customized for a specific transponder type by

specifying the Tx/Rx Photonic Profile in the CCMD LOC facility
“Reference Tx/Rx Type” parameter.
See “CMD Local Optical Control” on page 2-60 for more details.
• create custom ADJ-TX/RX types specifically for foreign transponders. The
attributes specified in a custom profile are identical to those available
when provisioning an individual Tx/Rx adjacency. The customer profile is
identified with a text label, which becomes available to the user as a new
Tx/Rx Adjacency type that you can select while provisioning a Tx
Adjacency at a CMD port. For foreign DWDM interfaces, the Photonic
Profile saves provisioning time during SLAT since the user can simply
provision the label: when applied, all other Tx/Rx adjacency parameters
are automatically provisioned.
Photonic Profile are provisioned on a per TIDc node basis. By default, 15

Tx/Rx Photonic Profiles appear in the Site Manager Photonic Profiles
application which can be edited.
Service and Photonic Layer Interoperability (SPLI)

SPLI is a software feature that enables coordination and communication
between the service layer transponder line-side optics (typically an OTMn or
PTP facility) and a photonic line (typically a CMD). See figure below.
Figure 1-41
SPLI Overview
SPLI-based applications include:

• Adjacency Discovery
• Transponder Information Discovery
• Transponder Provisioning
• Alarm Correlation
• Connection Validation Optical Loopback
• Layer 0 Control Plane (L0CP) notifications reporting optical channel
(OCH) status for restoration

Adjacency Discovery
Setting Far End Address (FEA) on ADJ facility triggers adjacency discovery
between two ADJ facilities on same or different shelves (but with same Site
ID). See figure below.
Applicable configurations are Photonic Line to Service Layer (CMD to

transponder) and Photonic Line to Photonic Line (for example, WSS to WSS,
LIM to LIM).
Different FEA formats are needed to support multiple platforms:

• 6500: TID-SH-SL-PRT
• 5400: TID-BAY-SH-SL-PRT
• 8700: NODENAME-SL-PRT
• Waveserver: NODENAME-SL-PRT
Using FEA, SPLI messages out-of-band from the photonic line to the service
layer in order to form a match.
Once a match is formed with a SPLI-enabled slot/port at the far end, the CMD
shows a discovered FEA that matches the provisioned FEA and additional
SPLI features are enabled.
Figure 1-42
SPLI Adjacency Discovery
Transponder Information Discovery

After a successful match, the photonic line SPLI requests information from the
service layer SPLI. Transponder information is used by SPLI for provisioning
transponder parameters (the SPLI Transponder Provisioning application).
Refer to Figure 1-43. Service layer SPLI replies with the following data:
• Tx/Rx Type:
— Transponder type and modulation scheme. For example, CMD44 (line
system type is Colored) feeding 100GOCLD (NTK539QJ) with WL3e
Modem and QPSK Modulation Scheme results in CMD calculating a
Tx/Rx Type of WL3EMDMQPSKCLD (MDM stands for modem). For
non-coherent transponders, the Tx/Rx Type also includes the
transponder PEC.
• Discovered Far End PEC (only for coherent transponders):

— PEC (6500) or Part # (5400/8700/WS) of the transponder circuit pack.

For example, 6500 100G OCLD would have PEC NTK539QJ.
• Discovered Center Frequency
• Discovered Wavelength
— a value is displayed only if the wavelength is on the 50 GHz ITU grid
• Discovered Transmission Mode (applicable to WLAi only)
— For all other Transmitter Types, the Tx/Rx Type suffices for SPLI to
derive the CMD ADJ-Tx/Rx parameters. For WLAi, this is also the case
for releases prior to Rel. 12.1, but with Rel. 12.1 and higher the
parameters are rather derived from the combination of WLAi Tx/Rx
Type, Transmission Mode and Line System Type.
• Discovered Tx Provisioned Power
• Discovered SPLI Management
• Discovered Tx Power Reduced State
• Discovered Laser Centering
• Discovered Laser Centering Range
• Discovered Tx Minimum Spectral Width
• Discovered Tx Signal Bandwidth 3dB
— For WLAi, obtaining this value from the transponder provides better
accuracy.
• Discovered Tx Signal Bandwidth 10dB
— For WLAi, obtaining this value from the transponder provides better
accuracy.
• Discovered - Path dispersion (WLAi and WLAi w/OPS only)
• Discovered - Link Optimization Mode (LOM) (WLAi and WLAi w/OPS only)
— LOM editing has no validation in PTP, the provisioned value is always
set and sent to the transponder and the transponder accepts or rejects
it
• Discovered - Transmitter Dispersion Mode (WLAi and WLAi w/OPS only)
• Discovered - Transmitter Pre-Compensation Value (WLAi and WLAi
w/OPS only)
Note: All the above parameters cannot be edited using transponder facility
when SPLI-managed. Only if the Provisioned value in the CMD ADJ-TX is
UNKNOWN, can the discovered value be transferred to the provisioned
value

Figure 1-43
SPLI Transponder Information Discovery
Transponder Provisioning
After adjacency and transponder information discovery are complete, SPLI is
able to communicate provisioning parameters to the transponder. See figure
below.
Figure 1-44
SPLI Transponder Provisioning
The provisioning is sent from the photonic line SPLI to the service layer SPLI.
The local OAM software that manages the transponder sends the provisioning
to the transponder.
SPLI sends the following parameters:
• TX wavelength: Transponder’s TX wavelength in nm (fixed grid) or
frequency THz (flexible grid)
— For CMD44, CMD96 and CMD64 the transponder wavelength is set to
the wavelength associated with the CMD port.
— For CCMD12, the transponder wavelength is set to the “resting”
wavelength (i.e., channel 0).
— For CCMD8x16, CCMD 16x12 and CCMD 8x4, the transponder
wavelength is set to the “resting” wavelength (i.e., channel 93 -
1528.77nm).
— Note that when the CMD ADJ-TX facility provisioned far-end address
is set to ‘Null’, SPLI resets the transponder Tx wavelength or
frequency to 0.
• TX Power: Transponder’s TX launch power in dBm

• Line System Type: The type of system configured on the photonic line into
which the modem is transmitting (for example, Colored, Colorless,
Contentionless/CDC, Coherent Select Colored, Coherent Select
Colorless).
• TX Tuning Mode: Transponder’s TX tuning mode (for example, normal or
accelerated). Applies only to colorless and CDC configurations.
• TX Power Reduction: When enabled, transponder’s laser is powered and
tuned but light is blocked from being transmitted. When cross-connection
is provisioned on the photonic line for that wavelength, this parameter is
set to disabled and the transponder’s light transmits. Applies only to
Coherent Select configurations.
• Channel Contention Detection: When enabled, if transponder’s receiver
detects a valid signal and that signal has an unexpected Trail Trace
Indicator (TTI), the modem raises the Channel Contention alarm
condition. This feature allows the system to determine if two modems are
simultaneously transmitting onto the photonic line with the same
wavelength. Applies only to colorless, CDC and Coherent Select
configurations.
• Provisioned Transmission mode (applies to WLAi and WLAi w/OPS
transponders only): The Transmission Mode defines the WLAi line rate. A
change in the Provisioned Transmission mode causes the appropriate
defaults to be populated in the ADJ-Tx and ADJ-Rx facilities.
— An exception is the case where a CCMD Tx power controller is
running. This controller modifies the nominal Tx power to equalize the
Power Spectral Density at the CCMD amp output. If the DOC Care flag
on the ADJ-TX facility is TRUE (which indicates the power is actively
being controlled) then the nominal Tx is left unchanged.
— An ‘Adjacency Mismatch’ alarm is raised if the Provisioned and
Discovered Transmission modes do not match.
• Allocated NMC Spectral Width: This parameter indicates the NMC width
once the Photonic connection is created (parameter is empty until then).
— If a user tries to change the Provisioned Transmission mode when the
channel is already provisioned, the change is only allowed if the
spectral parameters of the new mode are such that it fits within the
current allocated bandwidth.
• Laser Centering Mode
• Provisioned - Path dispersion (applies to WLAi and WLAi w/OPS
transponders only)
— Value provided Link Engineering
— SPLI OPS takes the average of the 2 PATHDISP from the photonic
paths to send to the transponder


• Provisioned - Link Optimization Mode (applies to WLAi and WLAi w/OPS
transponders only)
— SPLI OPS validates the LINKOPTMODE is the same on the two
Photonics paths and raises an Adjacency Mismatch alarm on both
switch ports if not the same
— If Transmission mode is edited and LOM is not explicitly specified,
LOM defaults to UNKNOWN
— SPLI sends Transmission Mode and LOM in pairs so that the
transponder side knows whether the far-end photonic shelf supports
LOM (i.e., pre-Rel. 12.6 or Rel. 12.6).
— When ADJ-TX LOM “Unknown” is sent to the transponder, the
transponder sets the PTP’s provisioned LOM to the default known by
transponder OAM on SP.
• Provisioned - Transmitter Dispersion Mode (applies to WLAi and WLAi
w/OPS transponders only)
— SPLI OPS compares the TXDISPMODE values of the two Photonics
paths and raises an Adjacency Mismatch alarm on both switch ports if
not the same.
• Provisioned - Transmitter Pre-Compensation Value (applies to WLAi and
WLAi w/OPS transponders only)
— SPLI OPS compares the TXPRECOMP values of the two Photonics
paths and raises an Adjacency Mismatch alarm on both switch ports if
not the same.
• Provisioned - Expected Restoration Time (applies to WLAi and WLAi
w/OPS transponders only)
— SPLI OPS sends the maximum EXPRESTIME of the two Photonics
value
— only visible through TL1

— Applicable for future release

SPLI OPS above refers to integrated OPS and external OPS applications for
WLAi.
Mismatch alarms are only raised for Link Optimization Mode, Transmitter
Dispersion Mode and Transmitter Pre-Compensation.
After an upgrade from a previous release to Rel. 12.6, the above ADJ-TX
parameters (Provisioned - Path dispersion/Link Optimization
Mode/Transmitter Dispersion Mode/Transmitter Pre-Compensation Value
default the provisioned value to “UNKNOWN” so that the value can be set to
the value discovered from the transponder provisioned value. The exception
is the “Expected Restoration Time” parameter which is set to 10 secs to match
the value on the transponder (It should be noted that if the parameter is edited
on the transponder before the Photonics is upgraded to Rel. 12.6, the value
will be overwritten).
Photonic Provisioning for WLAi and WLAi w/OPS

• When a WLAi or WLAi w/OPS channel is initially provisioned, the
Transmission mode is provisioned on the WLAi or WLAi w/OPS circuit
pack PTP line facility
• When SPLI is used:
— The CMD/CCMD ADJ-TX facility Expected Far End Address is
provisioned to point to the WLAi or WLAi w/OPS circuit pack PTP line
facility, the CMD/CCMD ADJ-TX facility “Provisioned Transmission
mode”=“Discovered Transmission mode”.
— Transmission mode and line type are used to look up the optical
parameters for the ADJ-TX/ ADJ-RX which include “modulation class”
used for applying a bias.
— After the WLAi or WLAi w/OPS channel has been added, the Link
Optimization Mode, Pre-Comp Mode, Pre-Comp Value, Path
Dispersion are discovered from the transponder and copied to the
provisioned CMD/CCMD ADJ-TX parameters since they were
previously unknown.
• When SPLI is not used, the CMD/CCMD ADJ-TX facility “Provisioned
Transmission mode” parameter must be manually provisioned to match
the Transmission mode setting provisioned on the WLAi or WLAi w/OPS
circuit pack PTP line facility.
• Transmission mode:
— After the WLAi or WLAi w/OPS channel has been added, it is possible
to change the transmission mode.

— The Transmission mode change is done on the CMD/CCMD ADJ-TX

facility by editing the “Provisioned Transmission mode” parameter.
– If SPLI is used, SPLI transfers this new value to the WLAi or WLAi
w/OPS circuit pack PTP line facility.
– If SPLI is not used, you need to manually change the Transmission
mode on the WLAi or WLAi w/OPS circuit pack PTP line facility.
— Transmission mode can be edited while the channel is in-service if the
allocated spectral width is sufficient for the new mode.
– Changing from a 35Gbaud mode to a 56Gbaud mode is blocked
on the photonics side if the allocated spectral width has not been
pre-allocated manually.
— Changing the Transmission mode on the WLAi or WLAi w/OPS circuit
packs is traffic affecting.
– Upshifting the line rate is rejected on the transponder if the client
rate (OTUC) has not been defined large enough. An Adjacency
Mismatch alarm on the CMD is raised as the provisioned would not
match the discovered.
• Link Optimization Mode:
— If LOM is specified on the CMD/CCMD but is unsupported by the
transponder for that specific transmission mode then the provisioning
is accepted by the transponder but rejected at the lower level. In this
case, the transponder raises an alarm highlighting the mismatch.
• Dispersion provisioning:
— The path dispersion is used by the transponder when the Tx Mode is
Auto to determine the correct pre-compensation required.
— When in fixed mode, any change in pre-comp is effective immediately
and impacts traffic.
— If an OPS is being used (either external or integrated) the Tx Mode
should be set to fixed and the TXDISPMODE, TXPRECOMP and
PATHDISP should be provisioned according to link engineering
recommendations.
– This is to ensure optimum switch times.
– SPLI sends the TXPRECOMP value as the average of the two
ports.
– If TXDISPMODE from two ports do not match, SPLI raises an
Adjacency Mismatch alarm with text in the “Additional Information”
to point to the specific reason
– If the TXPRECOMP is provisioned, SPLI sends the average of the
two ports (should be same value). When the TXDISPMODE is
auto, the pre-comp value is ignored.

– If the PATHDISP is provisioned, SPLI sends the average of the two

ports. When the TXDISPMODE is fixed, the path dispersion is
ignored.
Alarm Correlation
Port/Line Fault Suppression. See figure below.
• LOS is detected and raised against photonic line
• Downstream, transponder’s received LOS is suppressed because root
cause is upstream
Figure 1-45
SPLI Alarm Correlation - Port/Line Fault Suppression
Channel Fault Suppression. See figure below.

• Channel fault is detected against channel transmitting into photonic line
• Downstream, transponder’s received LOS is suppressed because root
cause is upstream
Figure 1-46
SPLI Alarm Correlation - Channel Fault Suppression

Virtual alarm correlation. See figure below.

• CMD Common In port does not have a monitor point (optical tap) and so
cannot detect LOS
• All transponders connected to the CMD detect LOS and SPLI propagates
these RX faults back to the photonic line SPLI
• SPLI correlates the Rx faults, realizes that all transponders connected to
the CMD are in fault, and raises a virtual LOS against the CMD Common
In port
• Further, SPLI propagates the port fault condition at the CMD to the service
layer SPLI so that the incoming faults at the transponders are suppressed
(see Port/Line Fault Suppression)
Figure 1-47
SPLI Alarm Correlation - Virtual alarm correlation
Connection Validation Optical Loopback

See figure below.
• As part of connection validation, photonic line software can use SPLI to
request a loopback mode on the transponder.
• Transponder Tx interface transmits with a special wavelength (channel
#93 or #96) and with a special Trail Trace Indicator (TTI).
• If transponder RX interface detects the correct wavelength and TTI and
the power received at the CMD input and the transponder RX interface are
within the specification, the connection validation succeeds.
• This loopback feature only applies to DIA configurations using Flex SMD
or Colorless Directional or Colorless Direct Attach (CDA) using 20x1 WSS
line system types or Colorless, Directionless, Contentionless (CDC) using
20x1 WSS line system types or RLA (for T-Series).
See also “Connection Validation Optical Loopback Test” on page 2-94.

Figure 1-48
SPLI Connection Validation Optical Loopback
SPLI data communications

SPLI can only perform a match between Photonic Line and Service Layer
equipment (CMD to transponder) or between Photonic Line and Photonic Line
equipment (for example, WSS to WSS, LIM to LIM) if the equipment at each
end is provisioned in:
• The same shelf. The shelf must have the following:
— An OSPF Router provisioned
— A Shelf IP provisioned
— An OSPF circuit is provisioned against the Shelf IP
• Different shelves sharing the same non-zero Site ID:
— Case 1: a shelf containing transponders only (no OTS provisioned),
the other shelf having photonic OTS(s) provisioned: TID names are
different but Shelf IDs can be the same.
— Case 2: shelves all have photonic OTSs provisioned. Whether TID
names are the same (TIDc node) or different, Shelf IDs must be
unique.
— The shelves must have a data communications path between them
(typically using ILAN), and which share AR (address resolution)
records using OSPF or DBRS or SLDD.
• Different shelves with different non-zero Site IDs:
— As Rel. 12.6, the Site Group feature allows SPLI matches between
shelves provisioned with different non-zero Site IDs, provided the
other shelf’s Site ID is provisioned in the Site Group of both shelves.
— SPLI matches between shelves that are part of the same Site Group
are also allowed, in addition to shelves sharing the same Site ID
— Case 1: a shelf containing transponders only (no OTS provisioned),
the other shelf having photonic OTS(s) provisioned: TID names are
different and there is no restriction on Shelf IDs.

— The shelves must have a data communications path between them

(typically using ILAN), and which share AR (address resolution)
records using OSPF or DBRS or SLDD.
If the service layer is 8700, the 6500 and 8700 nodes that are interconnected
using 6500 ILAN and 8700 ES1/2 ports. 8700 comms needs to be setup.
Refer to the 8700 Technical Publications.
Using FEA, SPLI messages out-of-band from the photonic line to the service
layer in order to form a match.
• On platforms using AR and OSPF (e.g., 6500), IP address for SPLI
messaging is resolved using TID.
• On platforms that do not support AR (e.g., 8700) or do not have OSPF
enabled (e.g., 6500), the IP address for SPLI messaging is user-set in the
Site Manager Node Information application and the SPLI tab using the
Add button. You first enter the Platform Type (6500, 8700, 5400 or
Waveserver), which automatically sets the Far End Address Format
Prefix, then enter the appropriate Node/TID information, the Shelf/Bay
information (if applicable), the Far End IP Address, and finally the SPLI
Comms Type (LOCAL, UDP or TCP/SSH). For this latter parameter:
— LOCAL denotes same shelf (the far-end as itself). UDP or TCP/SSH
is only applicable to inter-shelf.
— Inter-shelf comms to 6500 only supports TCP/SSH.
– Site IDs between 6500 shelves need to be the same for SPLI to
function between them
– Photonic shelf must have shelf IP provisioned (Shelf IP, COLAN-X
IP and OSPF Router ID must be the same address)
– Transponder shelf does not require to have OSPF circuits or OSPF
router provisioned but the Shelf IP must be provisioned
– IPv4 address for 6500 shelves can be manually provisioned but it
can still be auto-discovered from AR table. If a 6500 shelf is in the
AR table and the manual provisioned IP address is different, then
the IP address in the AR table is used
— Inter-shelf comms to Waveserver or WaveserverAi only supports
TCP/SSH.
— Inter-shelf comms to 8700 only supports TCP/SSH.
— Inter-shelf comms to 5400 supports UDP and TCP/SSH.
– TCP/SSH support is introduced in 5400 Rel. 4.3. For more details,
see Technical Publication 323-1851-160, 6500/5400/8700
Interworking Solution.

• In releases previous to Rel. 11.1, SPLI comms type was UDP only. Now
that inter-shelf comms to 6500 supports UDP and TCP/SSH,
management of SPLI comms protocol is as follows:
— On systems running Rel. 11.1 or higher, establishing an SPLI
connection to a new far-end shelf for the first time will use the
TCP/SSH comms type by default. If the far-end shelf supports UDP
only, manually set UDP when creating the SPLI entry.
— SPLI connections established with pre-Rel. 11.1 software were
necessarily UDP. An upgrade to Rel. 11.1 or higher preserves this.
After the upgrade, newly provisioned expected far-end addresses to a
same, previously connected far-end shelf will continue to have comms
type as UDP. Using the Site Manager Node Information application,
the comms type can be changed to TCP/SSH using the Edit button.
The Site Manager Node Information application and the SPLI tab contains
SPLI information such as Platform Type, number of SPLI matches, SPLI
Comms State and SPLI Comms Type to help troubleshoot SPLI comms
related issues. Note that for shelves upgraded to Rel. 12.6, the Platform Type
will default to ‘Null’.
Attention: Release 12.0 is the final release for CPL ROADM, TOADM or
GOADM nodes and 6500 shelves equipped with SP1.
SPLI interworking support is provided for non-56 GBaud transponders seated

in a Rel. 12.6 transponder shelf (ex: WLAi or WLAi w/OPS 35 Gbaud
transmission modes) and connected to a Photonic shelf running Release 12.0
or Release 12.1.
SPLI interworking support is provided for 56 GBaud transponders seated in a

Rel. 12.6 transponder shelf (ex: WLAi or WLAi w/OPS 56 Gbaud transmission
modes) and connected to a Photonic shelf running Release 12.1.
New non-56 GBaud transponders in future releases are supported by setting

the CMD ADJ-TX facility transponder type to foreign or foreign coherent.
For SPLI to function, the equipment involved must be in-service (IS). If any of
the circuit packs are not physically present, the provisioned slots must not be
equipped with filler circuit packs.
For SPLI behavior when the OPS is used, refer to “SPLI operation when OPS
is used in Optical Channel (OCH) Path Protection applications” on page 1-72.

For further details on SPLI, refer to:

• Technical Publication 323-1851-310/311, Configuration - Provisioning and
Operating
• Technical Publication 6500 Packet-Optical Platform Planning
• Technical Publication 323-1851-301, Administration and Security
• Technical Publication 323-1851-160, 6500/5400/8700 Interworking
Solution
Photonic connections
Photonic connections specify the path of an optical channel between its
ingress and egress endpoints at the node level. Provisioning a complete
end-to-end channel path in an Optical System requires that Photonic
connections be created at the add node, the drop node and any passthrough
node.
At 6500 S/D-Series add/drop nodes, the Photonic connections are between

the Line Interface Module (LIM) (i.e., the amplifier circuit pack or
SRA/ESAM/SAM) or RLA and the channel mux/demux filter. At passthrough
nodes, they are between LIMs or RLAs.
At 6500 T-Series add/drop nodes, the Photonic connections are between the
RLA module and the CCMD 16x12 or CCMD 8x4 module. At 6500 T-Series
passthrough nodes, the Photonic connections are between two RLA modules.
The Optical Bandwidth Manager (OBM) internal software application allows

these Photonic connections to be queried, added or deleted. The Site
Manager Photonic Connections application or the Visualization application
(Site OTS or Photonic View) can be used to perform these actions.
Attention: OBM only runs if the node has been TID consolidated.
Photonic connection attributes

Photonic connections can be viewed using the Site Manager Photonic
connections application (Photonic Connections tab), or the Visualization tool
(Optical Channel tab, provided the “Photonic Network” or “Site OTS” view is
selected). If the node uses fixed grid control and OSRP is not enabled, the
main parameters shown are:
• Circuit ID: mirrors the Circuit Identifier of the corresponding Tx adjacency
• Wavelength

• “From” and “To” endpoints: identify the connection termination points,

using AID format OCH-<shelf>-<slot>-<port>-<wavelength*100>. These
termination points refer to different equipments according to the
configuration:
— For ROADM to ROADM connections, the “From” endpoint always
refers to port 8 of the LIM acting as the node ingress point (Line A In),
while the “To” endpoint always refers to port 5 of the LIM acting as the
node egress point (Line B Out).
— For ROADM to DIA drop connections, the “From” endpoint always
refers to port 8 of the LIM acting as the node ingress point (Line A In),
while the “To” endpoint always refers to port x of the CMD44
wavelength acting as the node egress point (Channel X Out). The add
connection “From” endpoint always refers to port x of the CMD44
wavelength acting as the node ingress point (Channel X In), while the
“To” endpoint always refers to port 5 of the LIM acting as the node
egress point (Line B Out).
— For ROADM to COADM (via DIA) drop connections, the “From”
endpoint always refers to port 8 of the LIM acting as the node ingress
point (Line A In), while the “To” endpoint always refers to port x of the
CCMD12 wavelength acting as the node egress point (Channel
X Out). The add connection “From” endpoint always refers to port x of
the CCMD12 wavelength acting as the node ingress point (Channel
X In), while the “To” endpoint always refers to port 5 of the LIM acting
as the node egress point (Line B Out).
— For ROADM to CCMD8x16 or CCMD12 drop connections, the “From”
endpoint always refers to port 8 of the LIM acting as the node ingress
CCMD wavelength acting as the node egress point (Channel X Out).
— For CCMD8x16 or CCMD12 to ROADM add connections, the “From”
endpoint always refers to port x of the CCMD wavelength acting as the
node ingress point (Channel X In), while the “To” endpoint always
refers to port 5 of the LIM acting as the node egress point (Line B Out).
— For RLA to RLA connections, the “From” endpoint always refers to port
8 of the RLA acting as the node ingress point (Line A In), while the “To”
endpoint always refers to port 5 of the RLA acting as the node egress
point (Line B Out).
— For RLA to CCMD 16x12 or CCMD 8x4 drop connections, the “From”
endpoint always refers to port 8 of the RLA acting as the node ingress
CCMD wavelength acting as the node egress point (Channel X Out).

— For CCMD 16x12 or CCMD 8x4 to RLA add connections, the “From”
endpoint always refers to port x of the CCMD wavelength acting as the
node ingress point (Channel X In), while the “To” endpoint always
refers to port 5 of the RLA acting as the node egress point (Line B
Out).
• Type: specifies if the connection is 1WAY (Unidirectional) or 2WAY
(Bidirectional).
The Site Manager Photonic connections application also has a ‘Media

Channels’ tab showing Media Channel Trail Termination Point (MCTTP)
objects. In fixed grid photonic domains, MCTTPs are derived, i.e. they
auto-provision/auto-delete when Photonic connections are created/deleted.
The following MCTTP attributes are relevant to the remainder of this Guide:
• AID: the MCTTP AID format is MCTTP-<shelf>-<slot>-<port>-<McId>,
with the <shelf>-<slot>-<port> portion representing either the ROADM
OTS LIM Line B output port or Line A input port, and <McId> being equal
to <wavelength*100> in fixed grid applications.
• Capacity Change Mode: identifies the Mode of operation applicable to this
MCTTP when it undergoes an add or delete action (refer to “Modes of
operation for channel capacity changes” on page 2-35).
For a complete description of Photonic Connections and Media Channels

fields, see Technical Publication 323-1851-320.1, Configuration - Bandwidth
and Data Services, Part 1 of 3.
Some conditions must be met for the Photonic Connections application to be

available in Site Manager, at a given shelf:
• All OTSs involved in the Photonic connection have a configuration type of
channel access (CHA) and subtype of ROADM, DIA, or COADM.
• All ROADM OTSs include both a LIM (SLA, MLA, MLA2, MLA2v, MLA3 or
LIM or SRA/ESAM/SAM with XLA circuit pack) and a WSS circuit pack,
the LIM not being a Cascaded LIM.
— When using the NTK553RA RLA, the ROADM OTS includes just the
RLA or the RLA with an SRA, ESAM or SAM
— When using the NTK722AA RLA, the ROADM OTS includes just the
RLA
• All DIA OTSs include a LIM (MLA, MLA2 or MLA3) circuit pack, a CMD44
circuit pack and a WSS circuit pack.
• All COADM OTSs include a CCMD12 and a SMD circuit pack, and the
partner DIA OTS LIM must be the MLA (or MLA2 or MLA3 or XLA) and the
DIA WSS must be the 9x1 50GHz WSS. Note that for planned flexible-grid
applications, Flex SMD 1x8 and Flex WSS 9x1 circuit packs are used in
the COADM and DIA OTS respectively.

• All ROADM (and DIA and COADM if applicable) OTSs belong to the same
TID-consolidated node.
• Connections are reported at channel access nodes of subtype TOADM
but they are derived by the system. They cannot be manually created nor
deleted using the Site Manager Photonic Connections application.
• Derived connections are also reported at channel access nodes with the
ROADM subtype. For instance, if the fine DGFF function is implemented
at a 2-way ROADM whose OTSs are part of the same OSID, connections
are derived for passthrough traffic.
Provisioning
As is the case for adjacencies, there are system-derived and user-provisioned
Photonic connections.
System-derived Photonic connections

The Photonic connections are system-derived when all OTSs that the channel
travels through are in the same Photonic domain. Such connections include:
• Add and drop connections at ROADM OTSs. These connections are
between the LIM and Channel Mux/Demux ports within a single OTS.
They are auto-created by the system when the Channel Mux/Demux
ADJ-TX/ADJ-RX facility Tx/Rx type is set to a value other than “Unknown”
by the user or by SPLI and the OTS Autoroute parameter is set to Enable.
• Add and drop connections at TOADM OTSs. The add/drop connections
are between the LIM and the SCMD4 ports within a single OTS. They are
auto-created by the system when the SCMD4 ADJ-TX/ADJ-RX facility
Tx/Rx type is set to a value other than “Unknown” by the user or by SPLI.
• Passthrough connections between two OTSs that are within a single
optical domain. These connections are between LIM ports in two different
OTSs (both must be ROADM subtype or both must be TOADM subtype).
If the Tx adjacency is provisioned at the add node and the Rx adjacency
is provisioned at the drop node, OBM, based on Network Channel
Topology routing (NCT, see “Network Channel Topology” on page 1-68),
automatically creates a photonic passthrough connection at any
passthrough node if the two OTSs at the passthrough node are within a
single optical domain (i.e., the two OTSs have the same OSID).
Attention: System-derived photonic connections are always unidirectional

connections (1WAY).

User-provisioned Photonic connections

When an optical channel path crosses a Photonic domain boundary, the user
must manually provision the Photonic connection. User-provisioned
connections thus include passthrough connections between two OTSs that
are in different optical domains. They are also required in the following cases:
• DIA configurations without COADM: add and drop connections between
the DIA OTS and the backbone ROADM OTS must be manually
provisioned. These connections are between the ROADM OTS LIM ports
and the DIA OTS CMD44 ports. A pre-requisite is that the Channel
Mux/Demux ADJ-TX/ADJ-RX facility Tx/Rx type be set to a value other
than “Unknown” by the user or by SPLI.
• DIA configurations with COADM: since they can establish optical channel
paths to multiple Photonic domains at the same time, the DIA and COADM
OTSs are not part of any Photonic domain (neither are provisioned with a
DOC OSID). As a result, add and drop connections between the COADM
OTS and the backbone ROADM OTS need to be manually provisioned.
These connections are between the ROADM OTS LIM ports and the
COADM OTS CCMD12 ports. A pre-requisite is that the Channel
Mux/Demux ADJ-TX/ADJ-RX facility Tx/Rx type be set to a value other
than “Unknown” by the user or by SPLI.
• Colorless Directional CDA configurations using 9x1 WSS or 2x1 WSS
which have the COADM OTS directly attached to the ROADM OTS: add
and drop connections between a COADM and backbone ROADM OTS
must be manually provisioned. These connections are between a
backbone ROADM OTS LIM (or SAM/ESAM/SRA) and a COADM OTS
CCMD12 port. They are created after the COADM CCMD12 Tx and/or Rx
adjacency transmitter type is set to a value other than “Unknown” by the
user or by SPLI.
• CDC or CDA configurations using 20x1 WSS: add and drop connections
between the CCMD/CMD and backbone ROADM OTS must be manually
provisioned. These connections are between a backbone ROADM OTS
LIM (or SAM/ESAM/SRA) and a CCMD port. They are created after the
CCMD/CMD Tx and/or Rx adjacency transmitter type is set to a value
other than “Unknown” by the user or by SPLI.
OBM supports the creation of Photonic connections between any two OTSs
located in the same or different shelves provided the OTSs are in the same
TID and have different OSIDs. In Site Manager, manual creation/deletion of
photonic connections can be done:
• via the Photonic connections application (Photonic Connections tab), by
pressing the ‘Add’ button;
• via the Visualization tool (Optical Channel tab, with the “Photonic Network”
or “Site OTS” view selected), by pressing the ‘Add’ button.

Connections can either be created as bidirectional (2WAY) or unidirectional

(1WAY).
Note that when using L0 Control Plane, it is not necessary to manually

provision the photonic connections as described above, as L0 CP takes care
of this provisioning. Refer to Technical Publication NTRN71AA Part 2, Control
Plane Application Guide - Layer 0 (Photonic), for more details.
Photonic layer topology applications

The 6500 Photonic software platform includes several applications tied to
network and channel topology.
There are four topology applications, all supported by a Common Topology

Base application (“Topology collection” on page 1-66):
• Two of them build and maintain an up-to-date map of the OTSs location
and interconnections within an Optical System (“Optical System Topology”
on page 1-67 and “Optical Section Topology” on page 1-67);
• The other two describe channels as they travel from their Optical System
entry point to their exit point (“Network Channel Topology” on page 1-68
and “Shelf Wavelength Topology” on page 1-69).
Topology collection
Common Topology Base application initiates the topology collection when the
DOC OTS is provisioned for a given path (see “Domain Optical Controller
(DOC) description” on page 2-10 for more information about DOC). This data
collection is initiated by sending a message containing the topology
information of the DOC OTS to the next downstream OTS. When a message
is received by the OTS, it appends its topology information and forwards the
message to the next downstream OTS.
Message forwarding stops when there is no downstream neighbor (i.e., linear

topology) or the message has made a full circle and is received by its
originator (i.e., ring topology). The collected information is then organized into
sets of topology data (Network Topology Data and Section Topology Data).
These sets are then distributed to the OTSs in the Photonic domain where
they are used by different topology applications (i.e. Optical Section Topology,
Optical System Topology, or Network Channel Topology).
Common Topology Base data is updated continuously. Updates are also

triggered by an OTS adjacency change between the OTSs, DOC OTS
provisioning change or OTS management data change on any of the OTSs in
the Optical System.

This process is not directly visible through Site Manager or TL1, but its results
are reported by other, visible topology applications as described in the next
sections.
Optical System Topology

Optical System Topology (also known as Network Topology) collects and
maintains an ordered list of nodes in a given Optical System. Optical System
Topology software runs on the OTS that is provisioned to be the DOC OTS for
that direction.
Some information provided by the Optical System Topology application

includes:
• OSID name
• Site ID
• NE name
• Shelf number
• Tx Path ID
• Shelf type (for example, CHA for channel access)
• Topology configuration (e.g., linear or ring)
• Neighbor status (OK or Problem)
• DOC status, if applicable (blank if not a DOC OTS)
• Adjacent neighbors (labeled as First and Second) site ID, TID, shelf
number, Tx Path ID
Although Optical System Topology runs on nodes that contain the OTS
provisioned to be the DOC node, the above information is available at all
nodes that are part of the Optical System to the user via:
• The Site Manager Visualization Photonic Network view application.
• The Site Manager DOC application, which provides information about
whether the Optical System topology was successfully built or not
(through the DOC logs).
• The RTRV-TOPO-OST TL1 command.
Optical Section Topology

Optical Section Topology is a set of data that describes the topology of
channels within a section. Optical Section Topology software runs at every
node that hosts the source of the optical section (Optical Section head). Its
primary function is to create and maintain the accurate view of the wavelength
traveling through the OTSs within the Optical Section.

The only available data to the user with respect to Optical Section Topology is
whether the section topology was successfully built. This is available from the
Site Manager DOC application (through the DOC Logs button).
Network Channel Topology

Network Channel Topology (NCT) is a set of data that describes the topology
of channels within a Photonic domain by determining which equipment is
traversed by a channel from its origin (transmitter) to its destination (receiver).
It is NCT that creates the end-to-end channel topology within a Photonic
domain. Once NCT successfully creates the channel, it appears in the Site
Manager DOC application channel list.
Network Channel Topology software runs on nodes that contain the OTS
provisioned to be the DOC OTS. A Network Channel Topology entity is
created when the DOC OTS is provisioned for a given path and a Tx
adjacency is provisioned.
Some information provided by the Network Channel Topology application

includes:
• Channel circuit identifier: reflects the Circuit identifier provisioned with the
channel’s corresponding Tx adjacency.
• Channel wavelength.
• Channel AID: channel access identifier.
• Source TID-Shelf-TxPathId: indicates the channel’s source location
specified as Target identifier, Shelf number, and Tx Path IDentifier
• Destination(s) TID-shelf Rx Path ID: indicates the channel’s destination(s)
location specified as Target identifier, Shelf number, and Rx Path IDentifier
• NE trail: indicates the NEs traversed by the channel in the Photonic
domain of the selected DOC.
• DOC trail: lists the Photonic domain(s) (identified by their OSID) traversed
by the channel.
The above information is available to the user via:

• The DOC application (Configuration->Photonic Services-> Domain
Optical Controller (DOC)).
• For non-CDC systems, the Site Manager Visualization Photonic Network
view application (Tools->Visualization) which provides the NE trail
graphically. You need to enable Overlay parameters to see highlighted
channels.
• The RTRV-DOC-CH and RTRV-NCT-CH TL1 commands.

Shelf Wavelength Topology

Shelf Wavelength Topology (also called OTS Wavelength Topology) is a set of
data that describes the topology of channels within an OTS. Shelf Wavelength
Topology software runs on every node containing an OTS. Its primary function
is to create and maintain an accurate view of wavelengths traveling through
the circuit packs of the OTS.
Some information provided by the Shelf Wavelength Topology application

includes:
• Status: indicates the health of the wavelength
• DOC care: indicates whether DOC is controlling the network channel
• Port Trail: contains the ordered list of ports (slot, port) that channel is
traversing in the traffic direction within the OTS
• Wavelength Routing: indicates how the wavelength is routed. Possible
values are:
— Add: added at the OTS node
— Drop: dropped at the OTS node
— Passthrough: provisioned on the network and passes through this
OTS
— Unknown: the channel is not provisioned on this OTS node
• Channel Status: indicates the status of the channel. Possible values are:
— Unmanaged: identifies a channel which has a complete topology, but
is not controlled by DOC
— Adding: identifies a channel which is currently undergoing a DOC
addition action
— Deleting: identifies a channel which is currently undergoing a DOC
delete action
— Managed: identifies a channel which is under DOC control
— Failed: identifies a channel for which a previous DOC action has failed
— Not Applicable: identifies a channel for which the state is not applicable
— Not Available: identifies a channel for which the state is not available
or a channel whose topology is not complete
The channel status value is available in Site Manager. The channel status
can be queried for a particular channel, at any and all facilities traversed
by the channel which includes: the transmitter and receiver adjacencies
(RTRV-ADJ-TX/RTRV-ADJ-RX), the shelf wavelength topology
(RTRV-TOPO-SWT), and at Photonic connections (RTRV-CRS-OCH).
When channel status is retrieved using RTRV-CRS-OCH, there are two
channel status values. The From and the To channel status values

represent value of the channel status in the From and To domains. In a

steady state condition, the channel status value should be identical
regardless of where it is queried along the path of the channel.
The above information is available to the user via:
• The Site Manager Shelf Wavelength Topology application
(Configuration->Photonic Services-> Shelf Wavelength Topology).
• The Site Manager Visualization Site OTS view application and the
Visualization OTS Schematic view application (Tools->Visualization). For
non-CDC systems, the OTS Schematic view provides the port trail
graphically (provided the user checks the “Wavelength trace” box in the
“Overlays” dialog and then selects a managed channel from the Shelf
Wavelength Topology tab).
• The RTRV-TOPO-SWT TL1 command.
Optical Protection Switch (OPS) circuit pack topology

The following hardware is available:
• NTK554TA 4xOptical Protection Switch (4xOPS C-Band 1xOPSM2)
Circuit Pack
• NTK576AA 2xOptical Protection Switch Module (OPSM2 C-Band)
OPS applications are described in “Optical protection switching using the OPS
circuit pack” on page 3-158.
From the perspective of topology, the ports of the OPS (refer to Figure 3-89
on page 3-159) have the adjacency types assigned to them as per table
below, depending upon the application used.
Table 1-3
Adjacency type per OPS port adjacency facility
Port Label Port Direction Facility Adjacency Type

#
SW1-1 1 In OPTMON -
2 Out ADJ (UNKNOWN), ADJ-FIBER, ADJ-LINE TX/RX, LINE
SW2-1 3 In OPTMON -
Common 1 5 In ADJ (UNKNOWN), ADJ-TX, ADJ-FIBER TX
6 Out ADJ (UNKNOWN), ADJ-TX, ADJ-FIBER RX, OSCF, DSCM,

CMD, OMDF, BS, FGA

Table 1-3
Adjacency type per OPS port adjacency facility
Port Label Port Direction Facility Adjacency Type

#
SW1-2 7 In OPTMON -
SW2-2 9 In OPTMON -

CMD, OMDF, BS, FGA
SW1-3 13 In OPTMON -

CMD, OMDF, BS, FGA

CMD, OMDF, BS, FGA
Topology provisioning applies to the different OPS applications as follows.
Topology considerations for the client-layer Optical Path Protection application

In this application, the OPS is placed between 6500 transponder client ports
and subtending equipment. The OPS switch port ADJ facility expected far-end
address is provisioned to point to the transponder client port with an
Adjacency Type set to Unknown.

Topology considerations for the Optical Channel (OCH) Path Protection

application
In this application, the OPS is placed between 6500 transponder line ports
and a CMD module.
The OPS is provisioned in the topology under the following conditions:

• When the OPS is connected to a 6500 CMD and the OPS is in the same
shelf as the CMD.
• When the OPS is connected to a 6500 CMD and the OPS is not in the
same shelf as the CMD and transponder but the shelves are TID
consolidated.
The OPS is not provisioned in the topology under the following conditions:
• When the OPS is connected to a 6500 CMD and the OPS is not in the
same shelf as the CMD and transponder and the shelves are not TID
consolidated.
• When the OPS is connected to a CPL CMD. Note: for details on OPS
connections to CPL CMD filters, refer to the CPL technical publications.
Further details regarding topology provisioning are provided in the “Traffic

protection” chapter of Technical Publication 323-1851-315 Configuration -
Protection Switching.
SPLI operation when OPS is used in Optical Channel (OCH) Path Protection
applications
Since SPLI facilitates Tx/Rx interface provisioning, via Tx/Rx adjacency type,
Tx wavelength and Tx power auto-setting, then the placement of the OPS in
an OCH Path Protection application must be considered by SPLI. In this
context, an OPS used with the following CMD modules/circuit packs is
supported by SPLI:
• CMD44, CMD64, sCMD4, OMD4, OMDF4, OMDF8
Attention: OPS use at a Colorless OTS with CCMD12 is supported provided

Transceiver-Triggered OPS protection is used (see “Transceiver-Triggered
OPS protection” on page 3-163).
The OPS SW1/SW2 ports bridge the SPLI requests to/from the COM port. As
part of this, SPLI also ensures that:
• Wavelength, power and OTS type conflict scenarios - in which SW1/SW2
are connected to CMD ports with different wavelengths/power/OTS type -
are managed during adjacency provisioning.
• Editing any of the adjacency properties (wavelength, power or OTS type)
after initial provisioning results in an “Adjacency Mismatch” alarm if that
property is not synchronized between adjacencies to SW1 and SW2.

Software ensures consistency of ADJ-Type provisioning on OPS group ports.

• When the ADJ-TYPE of one port of the OPS group is provisioned,
software validates and enforces the ADJ-TYPE provisioning of remaining
ports. For example, if the ADJ-TYPE of switch 1 port is provisioned as
TX/RX, the switch 2 ADJ type can’t be anything but TX/RX and common
ports as TX and RX.
• If the placement of OPS needs to be changed to support a new different
configuration, ADJ-TYPE on all ports must be set to unknown.
• When adjacency type of port is set to unknown, configuration specific
adjacency object (ADJ-TX, ADJ-RX and ADJ-LINE) provisioning is set to
default.
Software auto-provisions (if enabled) the following once the auto-provision

criteria are validated:
• Tx wavelength, Tx power, OTS type on transponders
• Transponder TX/RX Type on Channel Mux/Demux ports
• OPS insertion losses on ADJ-FIBER as SCL (System Configuration
Loss).
— SCL is a parameter necessary for DOC to take into account the loss
of the OPS module. Refer to “OPS in a DOC-controlled system” on
page 2-20.
The auto-provision criteria is as follows:

• CMD ports wavelength are same
• CMD Tx Nominal powers are same
• OTS types are the same
While initially provisioning, when one of more rules of auto provision criteria
fails, software raises an “Adjacency Mismatch” alarm against both switch
ports and does not auto provision parameters.
Once auto provision is done by software and later, user provisioning causes
one of more rules of auto provision criteria to fail, software raises the
“Adjacency Mismatch” alarm against both switch ports and does not remove
auto provisioning of parameters.
If the OPS is not provisioned in the topology of an OCH Path Protection

application, then the insertion loss of the OPS must still be taken into account
by DOC. See “Operational Considerations if OPS not provisioned in topology
in OCH Path Protection application” on page 2-21.

Topology data communications requirements

Within a node
Topology information exchanges between OTSs at a given node are
performed using any of the following methods:
• 6500 shelf backplane when OTSs are in the same shelf;
• ILAN connection between OTSs at the same node but in different shelves;
• For non-CDC systems, Optical Service Channel (OSC) between OTSs at
same node, referred to as ‘OSC for Shelf Interconnect’ (see “Distributed
ROADM” on page 3-149).
Attention: The data communications protocol must be OSPF.
Between nodes
Inherited from the bidirectional nature of various Layer 1 protocols, topology
data communication messaging between photonic layer nodes is bidirectional
as well, and is based primarily on the Optical Service Channel (OSC). Each
direction is operated independently from the other. Exceptions include:
• Stretched-span applications, where the OSC link budget is exhausted.
Note that stretched-span configurations are not supported on 6500
Raman spans (SRA).
— Although the SRA circuit pack supports its own Telemetry Gain (TG)
communication channel, this channel is solely dedicated to SRA
turn-up and cannot be used for network element communications. For
more detail, refer to “Telemetry Gain (TG) mode” on page 2-78.
It is recommended that there be at least two paths to a photonic layer node for
TCP/IP data communication redundancy:
• Such a requirement can be achieved for the most part via OSC to/from the
node.
• In certain cases, such as stretched-span scenarios, a Layer 1 data
communications path (e.g. OTU or ODU layer GCC) riding over a
wavelength may be needed.
• Higher layer (e.g. Layer 2 or Layer 3 DCN) routing infrastructure is
deployed for EMS OAM&P and may serve as an alternative for remote
nodes.
The establishment of an optical channel path over multiple OSPF networks

requires special handling using DataBase Replication Service (DBRS), or
Site-Level Data Distribution (SLDD). DBRS and SDLL are described
Technical Publication, Data Communications Planning and User Guide.

Photonic Optical Control 2-
This chapter provides a description of the automated photonic optical control

provided by DOC.
Table 2-1
Topic
“Benefits” on page 2-3
“Hierarchical optical control concepts” on page 2-4
— “Overview of optical control within a Photonic domain” on page 2-4
— “Optical control across multiple Photonic domains” on page 2-8
— “DOC Sequencer and ingress Active flag” on page 2-9
“Domain Optical Controller (DOC) description” on page 2-10
— “Types of control algorithms” on page 2-10
— “DOC control of NTK553FB MLA2v VOA Target Loss” on page 2-11
— “DOC control of NTK722AA RLA VOA Target Loss” on page 2-18
— “OPS in a DOC-controlled system” on page 2-20
— “Site Manager DOC application” on page 2-21
“DOC actions” on page 2-30
— “Fault detection, auto-monitoring and fast-poller auto-monitoring cycles” on page 2-30
— “Channel add/delete processes and related DOC functions” on page 2-35
— “DOC actions blocking behaviour summary” on page 2-47
— “Topology application affects on DOC actions” on page 2-50
“Monitoring DOC action status and progress” on page 2-51
— “DOC-specific alarms” on page 2-51
— “DOC faults and troubleshooting” on page 2-53
“Middle Optical Controller (MOC) description” on page 2-57
— “NMCC facility” on page 2-57
— “MOCs in add/drop branches” on page 2-58
“Local Optical Controller (LOC) description” on page 2-59
— “Variable optical attenuators (VOAs)” on page 2-59
— “CMD Local Optical Control” on page 2-60
“Other optical control mechanisms” on page 2-64

2-2 Photonic Optical Control
Table 2-1
Topic
— “Transponder Power Spectral Density” on page 2-64
— “Automatic power reduction (APR)” on page 2-65
— “Automatic Line Shutoff (ALSO)” on page 2-66
— “Control of SRA-based Raman link” on page 2-72
— “Raman safety mechanisms (Pump shutoff, ALSO, APR)” on page 2-81
— “Transient suppression and detection” on page 2-84
“Connection Validation” on page 2-86
— “Connection Validation Cable Trace or Connection Discovery Test” on page 2-86
— “Connection Validation Fiber Loss Measurements Test” on page 2-89
— “Connection Validation Optical Loopback Test” on page 2-94
— “Connection Validation Cable Trace/Connection Discovery Test associated alarms” on page 2-96
— “Connection Validation Fiber Loss Measurements associated alarms” on page 2-97
— “OTDR4 to NTK722AA RLA Connection Validation” on page 2-97
“Dark Section Conditioning” on page 2-98
“Photonic layer alarms” on page 2-103
— “High Received Span Loss and Low Received Span Loss” on page 2-104
— “High Fiber Loss” on page 2-106
— “Connection Validation Fiber Loss Measurements Test” on page 2-107
— “Channel power PMs and alarms for Colorless transponders” on page 2-108
— “Channel Degrade alarm for WSS/RLA NMCC facilities” on page 2-109
— “Crossed Fibers Suspected alarm” on page 2-110
— “Automatic Shutoff Compromised alarm” on page 2-112
— “Channel Opacity Error” on page 2-114
— “Minimum Gain” on page 2-114
— “Low Optical Return Loss” on page 2-114
— “Gauge Threshold Crossing Alert Summary” on page 2-115
— “AMPMON facility alarming on amplifier output” on page 2-115
— “Incomplete Channel Topology” on page 2-115
— “Adjacency Mismatch” on page 2-116
— “OSPF Max Capability Reached” on page 2-117

Table 2-1
Topic
“Alarm correlation” on page 2-117
— “Alarm correlation support at CDC nodes” on page 2-118
— “Alarm Correlation support on the OPS Module” on page 2-118
“Bias Provisioning” on page 2-118
— “Photonic Differential Provisioning” on page 2-119
“Photonic Interworking” on page 2-120
“Bias Provisioning” on page 2-118
— “Interworking of 6500 configurations using DOC with those not using DOC” on page 2-120
— “Considerations regarding nodes running different software releases” on page 2-121
— “6500 T-Series interworking with 6500 S-Series/D-Series” on page 2-121
— “6500 T-Series interworking with CPL” on page 2-122
— “6500 S-Series and D-Series interworking with CPL” on page 2-122
— “6500/CPL node level interworking” on page 2-126
Benefits
The 6500 Photonic optical control algorithm optimizes traffic performance
through a Photonic domain. The algorithm runs on the two Channel access
OTSs provisioned as the Domain Optical Controllers (DOCs) for a given
Optical system. It is founded on the following two principles:
• Minimize the link budget penalty attributable to non-linearities that result
from self-phase modulation (SPM), cross-phase modulation (XPM), and
four-wave mixing (FWM).
• Balance the optical powers, that is, distribute finite available power such
that all wavelengths are treated equitably (the equitability currency being
either power or estimated OSNR).
In addition to these performance related objectives, the optical control

algorithm also aims at simplifying network operation, and thereby reduce
operational expenditures by:
• Providing automatic system optimization and power balancing with the
following benefits:
— automation hides complexity and saves site visits
— no skilled personnel or expensive test equipment required

• Providing autonomous monitoring and adjustment of the system once

steady-state is reached.
• Performing system auto-check for faults to ensure proper system state
prior to taking action.
• Allowing in-service channel addition/deletion.
Hierarchical optical control concepts

Overview of optical control within a Photonic domain
In order to achieve system optimization, the 6500 Photonic platform
incorporates a multi-level optical control hierarchy as shown in the figure
below.
Figure 2-1
Optical control hierarchy
Domain Optical Controller
Section Optical Controller Section Optical Controller
Middle Optical Controller

1 per WSS
Local Optical Local Optical Local Optical Local Optical

Controller Controller Controller Controller
Domain Optical Controller

The Domain Optical Controller (DOC), the highest form of control, seeks to
maximize end-to-end performance across the entire Photonic domain
comprising all OTSs that are visible to the assigned DOC OTS. One DOC
exists for each Photonic domain.
DOC actions all rely on the interaction between DOC and its associated
Section Optical Controllers (SOCs): DOC sends them requests to perform
one or more SOC services, and the SOCs update DOC on the status of the
Optical section they control (see “Section Optical Controller” on page 2-5).

DOC does not request multiple SOCs to perform SOC services in parallel. The
requests are made sequentially and DOC waits for each to complete before
making a request to the next SOC.
DOC is further detailed in the “Domain Optical Controller (DOC) description”

section below. DOC engineering rules can be found under “DOC engineering
rules” on page 4-42.
Section Optical Controller

The Section Optical Controller (SOC), an intermediate level of control, seeks
to optimize the link performance of a section within the Photonic domain. It
sets control targets for MOCs (Middle Optical Controller) and LOCs (Local
Optical Controller) within their sections and implements the bulk of the system
optimization function. One SOC exists per optical section, residing in the
head-end channel access OTS of the section.
Note that as of Rel. 12.1, the SOC no longer controls DIA, DIA/COADM and
COADM OTSs. For these, the channel control is done by a local controller,
which re-initializes the TCA baselines for these configurations.
The SOC is a servant to DOC and only performs actions when requested by
DOC. SOCs require intimate knowledge of the hardware that they are
controlling and how the wavelengths traverse the hardware in their section.
This information is provided by the Optical Section Topology application (see
“Optical System Topology” on page 1-67).
The Section Optical Controller is not explicitly user-visible. Section Topology

Logs can however be viewed by querying the DOC logs.
Middle Optical Controller

The Middle Optical Controller (MOC) is an internal control loop that controls
channel power though a WSS or SMD. A MOC runs independently of the DOC
and SOC, but requires communication to multiple circuit packs at the node
(which is why it is treated as a “middle” controller and not a local controller).
In that sense, MOCs are effectively local optical controllers that operate
autonomously in the middle of mux/demux structures. More details are
provided in “Middle Optical Controller (MOC) description” on page 2-57.
Local Optical Controller

The Local Optical Controllers (LOCs) are localized within a circuit pack and
seeks to maintain a set-point for a given hardware component. Contrary to the
Section Optical Controller (SOC), the LOCs are constantly running and are
maintaining targets that are internal or have been provisioned by the user or
the SOC. Each SOC-controlled LOC is under the control of one and only one
SOC. The LOCs in a Photonic domain are:
• amplifier gain controller

• amplifier tilt controller

• SCMD4 variable optical attenuators (VOAs)
• MLA2v embedded variable optical attenuator (VOA)
• RLA amplifier gain controller
• RLA amplifier tilt controller
• NTK722AA RLA embedded variable optical attenuator (VOA)
• CCMD controller (CCMD12 and CCMD8x16)
• CMD controller (CMD44, CMD96 and CMD64)
LOC is further detailed in the “Local Optical Controller (LOC) description” on

page 2-59.
Figure 2-2 on page 2-7 shows DOC, SOC, MOC and LOC locations in a
network encompassing two Optical Systems, linear and ring (ROADM
channel access and Line Amp nodes are shown).
For TOADM-based channel access nodes, the SCMD4 LOCs (VOAs) are
shown in Figure 2-3 on page 2-8.

Figure 2-2
DOC, SOC, MOC and LOC locations in ROADM-based network
OTS1 OTS2
OSC OSID1 OSID1 OSC
LOC MOC MOC LOC

LOC LOC
Odd Path OSID1 Even OSID1 Odd Odd Path

Opt Section 1 Path ID CMD44 CMD44 Path ID Opt Section 1
SOC OTS DOC OTS DOC OTS SOC OTS
OTS3
OSID2
Tx Path ID:5
CMD44
MOC LOC
OSC
LOC Even Path
OSID2 Odd Opt Section 3
Path ID SOC OTS
DOC OTS
OSC
SITE A Odd Path LOC
Opt Section 1
SOC OTS
CMD44
OTS2
MOC LOC
OSC
OSID1
LOC Tx Path ID:1 OTS1
OSID1
Tx Path ID:4
SITE D SITE B
OTS2
OSC
OSID1
OTS1 Tx Path ID:1
LOC
CMD44
OSID1
Tx Path ID:2 Odd Path
Opt Section 2 MOC LOC
SOC OTS
Even Path
OSC
Opt Section 1
SOC OTS LOC
SITE C OSID2 Even
Path ID
DOC OTS
OSC
LOC
CMD44
MOC LOC
OTS3
OSID2
Tx Path ID:8
OTS2 OTS1
OSC OSID1 OSID1 OSC
LOC MOC MOC LOC

LOC LOC
Odd Path Even Path

Opt Section 3 CMD44 CMD44 Opt Section 2
SOC OTS SOC OTS

Figure 2-3
SCMD4 LOC Locations
Optical control across multiple Photonic domains

Although very efficient at the Photonic domain level, a centralized optical
control architecture would become difficult to implement and cumbersome to
operate on the wider scale of the entire photonic network (i.e., spanning
multiple Photonic domains). A distributed optical control model is thus
implemented to address this scalability issue: each DOC controls the
individual SOCs in their domain and a communication link exists between the
different DOCs to hand-off control information (see figure below).
Figure 2-4
DOC peer-to-peer model
"I am going to do changes that

will impact the power of the
channels that we share"
DOC1 DOC2
"You can proceed with your
required changes"
LOC2 SOC1
SOC2
LOC5 SOC3
LOC2 SOC1
SOC2
LOC5 SOC3
Section Optical Controllers

LOC1
LOC3
LOC4
LOC6
LOC1
LOC3
LOC4
LOC6
Local Optical Controllers

This peer-to-peer model:

• provides a method to add or delete channels across multiple domains
without having the user to manually perform the add or delete action in
each domain
• provides a method to add or delete channels across multiple domains in
the proper order (i.e., prevent adding a channel in a downstream domain
if it is not first added in the upstream domain)
These above two points are addressed by the DOC Sequencer and Channel
Active flag.
DOC Sequencer and ingress Active flag

In order to enable channel addition and deletion across multiple domains in
the proper order, a method is needed to queue additions and deletions in all
domains that a channel passes through, and to communicate between
domains to signal completion and status between domains.
When not using L0 Control Plane

When the OTS “Autoroute” parameter is set to Enable and the OTS “CPS”
parameter is set to Disable, an ingress Active flag exists at the ingress point
in every domain which:
• can be manually user-provisioned when creating Tx adjacency (default is
false) at the end-point
• is automatically propagated to the ingress point in downstream domains
by token passing software
The Active flags are then propagated to the DOC site, where they are used to
queue an addition or deletion in that domain.
When using L0 Control Plane

When the OTS “Autoroute” parameter is set to Disable and the OTS “CPS”
parameter is set to Enable, L0 Control Plane (OSRP) creates each Photonic
connection at all add/drop and intermediate ROADM nodes with
ACTIVE=TRUE and each DOC site uses the local value of ACTIVE from the
local Photonic connection.
Once a channel has been flagged to be added or deleted through the change
of the Active flag, the sequencing of the additions and deletions are
coordinated between domains by DOC Sequencer via a token-passing
method. These tokens indicate that upstream and downstream domains are
in the correct state to allow a local action to proceed, and to let the local
domain know when it is allowed to proceed.

Domain Optical Controller (DOC) description

The Domain Optical Controller (DOC) is responsible for managing the optical
channels traversing its Photonic domain. As such, it incorporates the
necessary advanced optical control features to optimize traffic and maximize
system performance and reach.
Types of control algorithms
As the highest level of control, DOC has full authority on its SOCs and LOCs
to perform the following control tasks:
• Peak power control: on each amplifier, the EDFA gain is set such that no
wavelength exceeds a prescribed peak power target, in order to limit
non-linear effects. This is used on each EDFA facing the fiber-plant.
• Tilt control: an EDFA gain tilt control sets the gain tilt on each amp to
maximize system performance by minimizing accumulation of gain tilt and
ripple across a section.
• Optical control at ROADM nodes:
— WSS control: on each WSS or RLA circuit pack, a per-wavelength
attenuation profile is set (using data collected from amps upstream
and downstream from it) such that propagating channels are equally
penalized by the system, according to the class bias of the channel.
— When using amplifiers in the interior of the mux/demux structure at a
ROADM node, the EDFA gain is automatically set by DOC to achieve
appropriate channel levels. Refer to “SLA-based Drop LIM” on page
3-119 and “SLA/MLA Mux Amp” on page 3-124).
• Optical control at TOADM nodes:
— Under guidance from DOC, the SOC ensures that the measured signal
power at the mux ingress and demux egress eVOA output reaches a
provisioned sectional target.
— The objective is to ensure that the gain spectrum is kept as flat as
possible at the SCMD4 ingress and egress.
— The SOC ensures that the SCMD4 eVOA loss is set in a smooth and
predictable way. An example of this is when adding wavelengths within
a previously unused group. In such a case, when the sectional target
is provided but only a tiny amount of optical power is measured (due
to wavelengths not yet present), the SOC would need to ensure loss
exists as wavelengths are added.
Note that within colorless architectures, optical control for the equipment not
part of the backbone (e.g., DIA OTS, COADM OTS), is not under DOC but is
deferred to MOCs and LOCs (see “Middle Optical Controller (MOC)
description” on page 2-57 and “Local Optical Controller (LOC) description” on
page 2-59).

DOC makes its control decisions based on user input, Optical System
Topology and Network Channel Topology information, and internal status
information (system monitoring result).
DOC Overall status, “Optimal” or “Non Optimal”, summarizes the optimization

states of all its channels. To reach and maintain an Optimal state, DOC
performs a number of actions, some being initiated by the system and others
triggered by the user. Note that by provisioning the appropriate automation
level, some of these user-initiated DOC actions can execute automatically and
thus become system-initiated. The DOC actions include, among others,
monitoring, adding channels, deleting channels, and re-optimizing channels.
They are described in “DOC actions” on page 2-30.
DOC control of NTK553FB MLA2v VOA Target Loss

The NTK553FB MLA2v embedded VOA is an actuator (LOC) with a VOA
target loss controlled by DOC. The VOA target loss hinges on MLA2v VOA
facility user provisionable parameters:
• VOA Reset Required: value can be ‘True’ or ‘False’
• Target Pad: value can be ‘MIN’, or a numeric value obtained via
OnePlanner simulation
“VOA Reset Required” parameter
The “VOA Reset Required” parameter is viewable and editable in the Site
Manager Node Information application, and defaults to ‘True’. When the VOA
facility is created, the VOA facility “VOA Reset Required” parameter inherits
the value from System tab in the Site Manager Node Information application.
The choice of automatic VOA target loss calculation/setting or manual VOA

target loss setting depends on the “VOA Reset Required” parameter setting:
• When the parameter is set to True, the VOA target loss calculation/setting
is automatic and this occurs after either:
— Dark Section Conditioning kicks in, if the MLA2v is in the optical
domain head-end OTS
– Only the Line B VOA is set then. The Line A VOA is set at the
minimal value by default at the facility creation time, and can be
manually adjusted by the user in accordance with the link budget.
— a dark channel add (i.e., first channel add in a photonic domain), if
DSC is not enabled
— a DOC auto monitor cycle
• The automatic VOA target loss calculation and setting is performed once
based on the setting of the VOA facility “VOA Reset Required” parameter

Once the calculation/setting is complete and DOC has successfully set the
VOA target loss, DOC sets the VOA facility “VOA Reset Required” parameter
to False.
The VOA target loss can also be manually user-provisioned. By leaving the
flag set to False, the DOC-set VOA target loss value can be overridden by the
user. Refer to “Manual mode” on page 2-13.
DOC considers a photonic domain to be non-optimal if in the domain there is

an MLA2v VOA facility with the “VOA Reset Required” parameter set to True.
This is checked during a DOC auto monitor cycle.
• If the DOC Automation Mode is Enhanced, a re-optimization is done which
calculates and sets the VOA target loss for MLA2v VOA facilities which
have the “VOA Reset Required” parameter set to True.
• If the DOC Automation Mode is Enhanced Auto Monitor Only, the “DOC
Domain Not Optimized” alarm is raised.
• To trigger a new VOA target loss calculation, the VOA facility “VOA Reset
Required” parameter can be user-set back to True.
DOC fault detection already has fault detection checks for MLA/MLA2/MLA3
circuit packs. For the MLA2v circuit pack an extra check is done:
• If the VOA facility primary state is OOS, a “DOC Action: Fault Detected”
alarm is raised.
• DOC raises a customer visible log pinpointing the MLA2v VOA and
provides the reason for the failure.
The peak power monitor/optimization controls the MLA2v provisioned peak

target power which is referenced at the EDFA output, rather than the VOA
output.
“Target Pad” parameter

The “Target Pad” parameter defines the total loss targeted on the span or
mid-stage. It is viewable and editable in the Site Manager Node Information
application, with a default value of 15 dB. The parameter is normally set by the
user to a numeric value obtained from OnePlanner.
When the VOA facility is created, the VOA facility “Target Pad” parameter
inherits the value from the “Target Pad” parameter in the Node Information
application and the System tab.
When DOC-controlled (automatic mode), the MLA2v VOA target loss is set
dependent on the MLA2v VOA facility “Target Pad” parameter value.
• If the “Target Pad” value is numeric, the VOA target loss is set to achieve
a total loss between adjacent amplifiers equal to the “Target Pad” value.

• If the “Target Pad” value is set to “MIN”, the VOA target loss is set to ensure
that the downstream amplifier’s gain is above its minimum.
• The “Target Pad” parameter range is 1-20 dB
In addition:
• DOC sets the VOA target loss to 1 dB for the Line A VOA (VOA port 7)
when the MLA2v circuit pack is followed by a WSS (ROADM) or channel
demux element (TOADM).
• The MLA2v VOA loss remains at its current value when the MLA2v VOA
facility is placed OOS-MA. In that state, the loss does not change if the
“Target Pad” or “Target Loss” value is changed.
For TCA Baseline Reset behaviour using the MLA2v, refer to “Reset TCA
baselines” on page 2-45.
Manual mode
For applications when it is desired not to have the MLA2v VOA Target loss
automatically set by DOC but to be manually user-provisioned, you must:
• set the MLA2v VOA facility “VOA Reset Required” parameter to False and
• set the “Target Loss” parameter according to the OnePlanner
recommended value
Use of OSC span loss in VOA Target Loss adjustment

The OSC span loss is used for the loss of the fiber span, and is required by
DOC for the VOA target loss calculation and adjustment:
• If there are LIMs between the MLA2v and the downstream amplifier their
loss is included.
• The loss of any DSCM on the line is automatically included in the OSC
span loss measurement.
• When the OSC span loss is unavailable, DOC does not adjust the MLA2v
VOA.
The following examples illustrate the VOA target loss calculation performed by
DOC. These examples reference the example configurations shown in
“MLA2v - EDFA with embedded VOA” on page 3-119:
• Figure 2-5 on page 2-14
Asymmetric AMP OTSs
Uncompensated, AMP OTSs (MLA2v, LIM)
Uncompensated, AMP OTSs, No Padding In Mid-Stage (MLA2v only)


Compensated, ROADM OTS with MLA2v and Cascaded (Interior) LIM
Figure 2-5
MLA2v VOA Target Loss calculation - Example 1

Figure 2-6

Figure 2-7

Figure 2-8
MLA2 VOA Target Loss calculation - Example 4

DOC control of NTK722AA RLA VOA Target Loss

The RLA embedded VOA is an actuator (LOC) with a VOA target loss
controlled by DOC. The VOA target loss, hinges on RLA VOA facility user
provisionable parameters:
• VOA Reset Required: value can be ‘True’ or ‘False’
• Target Pad: value can be ‘MIN’, or a numeric value obtained via
OnePlanner simulation
• Target Peak Power: a numeric value obtained via OnePlanner simulation
“VOA Reset Required” parameter

The “VOA Reset Required” parameter is viewable and editable in the Site
Manager Node Information application, and defaults to ‘True’. When the VOA
facility is created, the VOA facility “VOA Reset Required” parameter inherits
the value from System tab in the Site Manager Node Information application.
The choice of automatic VOA target loss calculation/setting or manual VOA

target loss setting depends on the “VOA Reset Required” parameter setting:
• When the parameter is set to True, the VOA target loss calculation/setting
is automatic and this occurs after either:
— Dark Section Conditioning kicks in
– Only the Line B VOA is set then. The Line A VOA is set at the
minimal value by default at the facility creation time, and can be
manually adjusted by the user in accordance with the link budget.
— a dark channel add (i.e., first channel add in a photonic domain), if
DSC is not enabled
— a DOC auto monitor cycle
• The automatic VOA target loss calculation and setting is performed once
based on the setting of the VOA facility “VOA Reset Required” parameter
Once the calculation/setting is complete and DOC has successfully set the
VOA target loss, DOC sets the VOA facility “VOA Reset Required” parameter
to False.
The VOA target loss can also be manually user-provisioned. By leaving the
flag set to False, the DOC-set VOA target loss value can be overridden by the
user. Refer to “Manual mode” on page 2-19.
DOC considers a photonic domain to be non-optimal if in the domain there is

an RLA VOA facility with the “VOA Reset Required” parameter set to True.
This is checked during a DOC auto monitor cycle.
• If the DOC Automation Mode is Enhanced, a re-optimization is done which
calculates and sets the VOA target loss for RLA VOA facilities which have
the “VOA Reset Required” parameter set to True.

• If the DOC Automation Mode is Enhanced Auto Monitor Only, the “DOC
Domain Not Optimized” alarm is raised.
• To trigger a new VOA target loss calculation, the VOA facility “VOA Reset
Required” parameter can be user-set back to True.
• If the VOA facility primary state is OOS, a “DOC Action: Fault Detected”
alarm is raised.
• DOC raises a customer visible log pinpointing the RLA VOA and provides
the reason for the failure.
The peak power monitor/optimization controls the RLA provisioned peak

target power which is referenced at the output of the EDFA not at the output
of the VOA.
“Target Pad” parameter

The “Target Pad” parameter defines the total loss targeted on the span. It is
viewable and editable in the Site Manager Node Information application, with
a default value of 12 dB. The parameter is normally set by the user to a
numeric value obtained from OnePlanner.
When the VOA facility is created, the VOA facility “Target Pad” parameter
inherits the value from the “Target Pad” parameter in the Node Information
application and the System tab.
When DOC-controlled (automatic mode), the RLA VOA target loss is set
dependent on the RLA VOA facility “Target Pad” parameter value.
• If the “Target Pad” value is numeric, the VOA target loss is set to achieve
a total loss between adjacent amplifiers equal to the “Target Pad” value.
• If the “Target Pad” value is set to “MIN”, the VOA target loss is set to ensure
that the downstream amplifier’s gain is above its minimum.
• The “Target Pad” parameter range is 1-20 dB
In addition, the RLA VOA loss remains at its current value when the RLA VOA
facility is placed OOS-MA. In that state, the loss does not change if the “Target
Pad” or “Target Loss” value is changed.
For TCA Baseline Reset behaviour using the RLA, refer to “Reset TCA
baselines” on page 2-45.
Manual mode
For applications when it is desired not to have the RLA VOA Target loss
automatically set by DOC but to be manually user-provisioned, you must:
• set the RLA VOA facility “VOA Reset Required” parameter to False and

• set the “Target Loss” parameter according to the OnePlanner

recommended value
Use of OSC span loss in VOA Target Loss adjustment

The OSC span loss is used for the loss of the fiber span, and is required by
DOC for the VOA target loss calculation and adjustment. When the OSC span
loss is unavailable, DOC does not adjust the RLA VOA.
The following example illustrates the VOA target loss calculation performed by
DOC.
Figure 2-9
RLA VOA Target Loss calculation
OPS in a DOC-controlled system

Optical Channel (OCH) Path Protection and System Configuration Loss (SCL)
When the OPS is used in OCH Path Protection applications, the OPS
insertion loss must be taken into account between the transponder line
interface and the CMD used.

Consequently, a read-only System Configuration Loss (SCL) parameter is

added to Channel Mux/Demux ADJ-FIBER facility. SPLI populates SCL based
on OPS insertion loss on ADJ-FIBER facilities of CMD TX and RX ports when
the OPS is provisioned in topology:
• SCL on CMD TX port has OPS insertion loss in MUX direction (from
Common In to Switch Out)
• SCL on CMD RX port has OPS insertion loss in DEMUX direction (from
Switch In to Common Out)
The OPS insertion loss is read from calibration data in the OPS CCT.
DOC adds the SCL value to the existing “Excess loss” parameter on the
ADJ-FIBER facility to derive nominal power values at CMD TX and RX ports
Operational Considerations if OPS not provisioned in topology in OCH Path

Protection application
If the OPS is not provisioned in the topology, then:
• The CMD Channel In port Transmitter Type is manually set to be the
transponder type connected to the OPS.
• The OPS insertion loss is provisioned in the CMD ADJ-FIBER facility
“Excess loss” parameter. Excess Loss is provisioned as 1.3 dB for the
CMD RX and 3.5 dB for the CMD TX.
Site Manager DOC application

The DOC facility can be observed and managed from the Site Manager
Configuration -> Photonic Services -> Domain Optical Controller (DOC)
application.
DOC summary parameters (upper pane)

The DOC window upper pane shows the following:
• DOC Identifier: since multiple DOCs can reside in a single 6500 shelf,
each DOC has a unique label or identifier defined as follows:
DOC-<shelf number>-<OTS number>
• Primary State: indicates whether DOC is in service (IS) or out of service
(OOS).
• Overall Status: when no DOC actions are being performed, the DOC
Overall status is either “Optimal” or “Non Optimal”. The status is Optimal
if, and only if, all channels listed as Active: True have a channel condition
of “Optimized” or “In-Service”. When a DOC action has been initiated
(either by the user or by the system), the Overall Status displays the DOC
action being performed (for example, “Performing Fault Detection” or
“Channel Add in Progress”).

• Command Status and Progress: when DOC is executing a command,

whether or not it was user-initiated, these fields allow the monitoring of the
command execution. When applicable, DOC provides its progress to
complete the current command as well as extra detail about the command
progress.
DOC Settings tab parameters

The table below details the parameters associated with DOC settings.
Table 2-2
DOC parameter values and description
Parameter Value Notes

Primary • IS (default) • When in the OOS state, DOC is turned off and system optimization
state • OOS monitoring, system optimization or channel add/delete operations
cannot occur. All DOC related alarms are cleared when DOC is put in the
OOS state.
• Putting DOC in or out of service does not impact traffic on any optimized
channel. Nevertheless, it is not recommended to leave DOC OOS for an
extended period of time as disturbances (either coming from neighbor
DOC actions or from photonic elements) are not monitored and/or
compensated.
• When the DOC primary state changes from OOS to IS, regardless of the
DOC automation mode, a DOC monitor action is invoked right away. For
further details on the DOC monitor routine, refer to “Auto-monitoring and
automatic reoptimization description” on page 2-31.
• The “Domain Optical Controller Disabled” alarm is raised when the DOC
primary state is changed to OOS.
• The DOC channel list is updated even when DOC is in the OOS state.

Table 2-2

Automation • Enhanced • Enhanced: In this mode, every two minutes, DOC monitors the Photonic
mode (default) domain to determine its state of optimization. If DOC detects that
• Enhanced re-optimization is necessary, DOC automatically re-optimizes the
Auto Monitor domain without user intervention. TCA baselines are not reset after the
Only re-optimization, otherwise tracking of degrading systems/hardware
would not be possible. If desired, TCA baselines can be reset using the
• Foreign Line Reset TCA Baselines button in the Site Manager DOC application. After
• Foreign Line a capacity change, automatic re-optimization occurs and TCA baselines
Enhanced are reset.
• Foreign Line • Enhanced Auto Monitor Only: In this mode, every two minutes, DOC
Speed monitors the Photonic domain to determine its state of optimization. If
Enhanced DOC detects that re-optimization is necessary, DOC raises the “DOC
(Note 1) Domain Not Optimized” alarm but does not perform any re-optimization
action. Note that, if desired, the domain can be manually re-optimized
using the Re-optimize button from the Site Manager DOC application
and this does not reset TCA baselines. After a capacity change,
automatic re-optimization occurs and TCA baselines are reset.
• Foreign Line, Foreign Line Enhanced and Foreign Line Speed
Enhanced: These automation modes support the DOC functionality in
submarine applications. For more information refer to the Submarine
Network Application Guide NTRN72AA.
For information on DOC fault-detection and monitoring routines, refer to
“Fault detection, auto-monitoring and fast-poller auto-monitoring cycles”
on page 2-30
Note that Editing the DOC automation mode setting between “Enhanced”
and ‘Enhanced Auto Monitor Only” does not require that the DOC primary
state be put OOS. If the new automation mode is to be edited to Foreign
Line or Foreign Line Enhanced, then DOC needs to be put OOS.

Table 2-2

Auto add • Disabled • When Auto add channels is set to Enabled, DOC automatically attempts
channels • Enabled to add provisioned channels which have their Active parameter set to
(Default) True as soon as Network Channel Topology can build a valid end-to-end
channel in the Photonic domain. The Active parameter can be set to True
(Note 1) by the user when the Tx adjacency is provisioned. When provisioning the
initial channels on a greenfield deployment, it is recommended to set the
Tx adjacency Active parameter to False during initial turn up. For
channels spanning multiple Photonic domains, enabling this parameter
in all these domains allows channel addition to complete end to end
simply by initiating the addition from the head-end DOC: when one
domain is done with the channel addition, a token is passed from its DOC
to the next downstream DOC without user intervention (channel addition
starts in the domain where the Tx ADJ is and progresses towards the
domain containing the Rx ADJ). This process repeats until the tail-end
domain receives the token and completes the channel addition.
• When Auto add channels is set to Disabled, channel adds must be
user-initiated using the Add button in the Site Manager DOC application.
For channels spanning multiple Photonic domains (say N domains),
disabling this parameter means the user has to manually launch the
channel addition in each of the N domains, starting with the domain
where the Tx adjacency is (head-end domain). The user needs to wait
for the operation to complete in one domain before pressing the Add
button in the next downstream domain.
Note: If the OTS Autoroute parameter is set to Enabled, then the auto
channel add functions as mentioned above. If it is set to Disabled, it
overwrites the function and auto channel add functions are disabled and
are instead controlled by L0 Control Plane. For more information if
“Autoroute” is set to Disabled, refer to Technical Publication NTRN71AA,
Control Plane Application Guide - Layer 0 (photonic).
For 6500 T-Series CDC systems, leave the Auto add channels parameter
to default value of Enabled.

Table 2-2

Auto delete • Disabled • When Auto delete channels is set to Enabled, DOC automatically deletes
channels • Enabled channels which have their Active parameter set to False. The Active
(Default) parameter can be set to False by the user by editing the Tx adjacency. It
is recommended that channels be deleted using the DOC application
(Note 1) rather than by setting the Active parameter to False in the Tx adjacency.
For channels spanning multiple Photonic domains, enabling this
parameter allows channel deletion to complete end to end simply by
initiating the deletion from the head-end DOC: when one domain is done
with the channel deletion, a token is passed from its DOC to the next
upstream DOC without user intervention (channel deletion starts in the
domain where the Rx ADJ is and progresses towards the domain
containing the Tx ADJ). This process repeats until the head-end domain
receives the token and completes the channel deletion.
Note: As a safety precaution, “Auto delete channels” cannot be set to
Enabled if the Active parameter of one or more DOC-managed channels
is “False”.
• When Auto delete channels is set to Disabled, channel deletions must be
user-initiated using the Delete button in the Site Manager DOC
application. For channels spanning multiple Photonic domains (say N
domains), disabling this parameter means the user has to manually
launch the channel deletion in each of the N domains, starting with the
domain where the Rx adjacency is (tail-end domain). The user needs to
wait for the operation to complete in one domain before pressing the
Delete button in the next upstream domain.
Note: If the OTS Autoroute parameter is set to Enabled, then the auto
channel delete functions as mentioned above. If it is set to Disabled, it
overwrites the function and auto channel delete functions are disabled and
are instead controlled by L0 Control Plane. For more information if
“Autoroute” is set to Disabled, refer to Technical Publication NTRN71AA,
Control Plane Application Guide - Layer 0 (photonic).
For 6500 T-Series CDC systems, leave the Auto delete channels
parameter to default value of Enabled.
Auto delete • Disabled As of Rel 12.4, this parameter is no longer supported on terrestrial optical
on fault (default) domains. It remains supported on submarine optical domains. For
• Enabled Submarine applications, refer to the Submarine Network Application
Guide NTRN72AA for complete behavior description of this parameter.
Degrade 1 to 120 This parameter can only be set when the “Auto delete on fault” parameter
hold off (default=1) is set to Enabled. It is obsolete as of Rel. 12.4 since “Auto delete on fault”
(minutes) is no longer supported on terrestrial optical domains.

Table 2-2

Note 1: When an OTS is edited and the DOC site parameter is changed from False to True, the DOC
settings default to the following values:
— Automation mode=Enhanced Auto Monitor Only,
— Auto add channels=Disabled
— Auto delete channels=Disabled,
— Auto delete on fault=Disabled.
This is different when compared to the case when the OTS is created which has the following default
DOC settings:
— Automation mode=Enhanced,
— Auto add channels=Enabled,
— Auto delete channels=Enabled,
— Auto delete on fault=Disabled
DOC Channels Tab Information

The DOC application “Channel” list provides a list of channels that are present
in the selected DOC Photonic domain. Most parameters on this tab are
described in “Network Channel Topology” on page 1-68:
DOC trail status

The DOC trail status indicates if a channel path has been completely defined
(“Complete” status) or not (“Incomplete” status). That is, if its Tx and Rx
adjacencies, and Photonic connections if applicable, are all in place in all
Photonic domains the channel traverses.
Domain Routing
The Domain Routing parameter indicates the channel’s routing within the
Photonic Domain. Inactive channels which have a Domain Routing of Add or
Add/Drop can be selected for a DOC Channel add operation.The different
conditions are:
• Add: the photonic domain has a CMD ADJ-TX but no CMD ADJ-RX for
the provisioned channel in this domain. This means that the channel
originates in this domain but terminates in a downstream domain.
• Drop: the photonic domain has a CMD ADJ-RX but no CMD ADJ-TX for
the provisioned channel in this domain. This means that the channel
originates in an upstream domain but terminates in this domain.
• Add-Drop: the photonic domain has a CMD ADJ-TX and a CMD ADJ-RX
for the provisioned channel in this domain. This means that the channel
originates and terminates in this domain.

• Passthrough: the photonic domain has no CMD ADJ-TX and no CMD

ADJ-RX for the provisioned channel in this domain. This means that the
channel originates in an upstream domain and terminates in a
downstream domain.
Per-channel status - Channel Condition and End-to-End Condition

At any time, the status of each channel can be queried to determine its state
of optimization.
The “Channel condition” column provides a real-time status of the Channel

Optimization State (COS) and the channel fault status (CFS). The status also
reflects whether the channels are being added or deleted.
The End-to-End Channel Condition represents a unified Channel Status of all

DOCs through which channel traverses.
Attention: Channels showing an ‘Inactive’ Channel Optimization State have

been provisioned by the user but have not been added in the Photonic
domain. That is, there is no light for that specific wavelength being
propagated through the Photonic domain. The “Channel Control” facility for
all WSS circuit packs in the Photonic domain have their opaque value set to
block, or the SCMD4 ingress VOA facility loss target is set to maximum
attenuation for that specific wavelength. Note that in this latter case, light
from connected transponders to the SCMD4 might still be powerful enough
to be above the amplifier shut-off threshold, even with the VOAs at maximum
attenuation.
Channel Fault Status

The Channel Fault Status (CFS) is similar to a secondary state for the
Channel Optimization State (COS). Together, the COS and CFS represent
an overall channel status, which is displayed in the “Channel Condition”
column in the Site Manager DOC application.
Within a domain if a fault is detected on a managed channel, depending
on the type of fault, the CFS is displayed in Site Manager as “LOS”, “major
degrade”, “minor degrade”, “not controlled” or “fault detected”.
If the channel is unmanaged, the only CFS state that is applicable pertain
to the outcome of the DOC Pre-Check, which would be “Pre-Check Fail”
or “Pre-Check Pass”.
A pre-check fail Channel Fault Status clears when the pre-check is run
again, and remains cleared only if the problem has been resolved.
The table below shows the possible values for CFS.

Table 2-3
CFS parameters
CFS Applies to Description

No Fault Managed channels Fault detection has completed and no faults has been found.
Note: A CFS of “No Fault” is seen over the TL1 interface but not
in Site Manager to avoid screen clutter.
Pre-Check Inactive & Pre-check has run and passed. The channels are still “Inactive”,
Pass Add:Waiting channels in this stage.
Pre-Check Inactive & Pre-check (a subset of fault detection) has run and found a
Fail Add:Waiting channels problem. The channels are still “Inactive”, not “Partially Added”.
LOS Managed channels Fault detection has detected a Loss of Signal (LOS) on a
Channel Mux ingress port for a locally added channel, or the
NLC (Network Level Correlation) point is asserted (hard fault
upstream) and the channel is missing from the OPM output
spectrum for a channel that comes from an upstream photonic
domain.
Fault Managed channels Fault detection routine has completed and a fault is detected on
Detected the channel and DOC raises the “DOC Action: Fault Detected”
alarm for this particular fault. DOC log is also generated to help
troubleshoot the fault.
Not Managed channels Shown if a fault is detected on the channel but DOC does not
Controlled raise the “DOC Action: Fault Detected” alarm for this particular
fault (e.g. an amplifier in APR).
Degrade, Managed channels Shown when channel minor degrade condition is met. The
minor default minor degrade threshold is 3 dB. The “Channel
Degrade” minor, NSA alarm is raised.
Degrade, Managed channels Shown when channel major degrade condition is met. The
major default major degrade threshold is 6 dB. The “Channel
Degrade” minor, NSA alarm is raised.
Waiting for Inactive channels Shown at a CDC or Colorless node, when a channel is added
power with DOC and its measured power is not within 3 dB of the
expected value.
Active
The Active parameter displays the Channel Mux/Demux ADJ-TX Active
parameter when the OTS “Autoroute” parameter is set to Enable or the
channel’s Photonic connection Active parameter when the OTS “Autoroute”
parameter is set to Disable.
• If the Active parameter is True, the channel is automatically added when
DOC Auto add channels parameter is set to Enabled. For a
DOC-managed channel, the Active parameter is True.

Attention: If the Active parameter is changed to False for a DOC-managed

channel and the DOC Auto delete channels parameter is set to Enabled,
then the channel is automatically deleted by DOC.
Active parameter when not using L0 Control Plane

• The Active parameter changes from False to True for a specific channel in
a Photonic domain when one of the following occurs:
— A user changes the Active parameter from False to True for the
channel mux/demux filter channel port ADJ-TX facility
— A user clicks on the Add button from within the Site Manager DOC
application after selecting the wavelength
— The DOC application initiates a channel add after the completion of
the channel add operation in the upstream Photonic domain (case of
a channel spanning multiple Photonic domains). The Auto add
channels parameter must be enabled for this to happen (see “DOC
Settings tab parameters” on page 2-22).
• The Active parameter changes from True to False for a specific channel in
a Photonic domain when one of the following occurs:
— A user changes the Active parameter from True to False for the
channel mux/demux filter channel port ADJ-TX facility
— The DOC application initiates a channel delete after the completion of
the channel delete operation in the downstream Photonic domain
(case of a channel spanning multiple Photonic domains). The Auto
delete channels parameter must be enabled for this to happen (see
“DOC Settings tab parameters” on page 2-22).
Active parameter when using L0 Control Plane

• The Active parameter changes from False to True for a specific channel in
a Photonic domain when L0 Control Plane (OSRP) creates each Photonic
ACTIVE=FALSE.
• The Active parameter changes from True to False for a specific channel in
a Photonic domain L0 Control Plane (OSRP) deletes each Photonic
ACTIVE=TRUE.
Consideration for number of channels that can be added/deleted in one

operation
In field deployments, channels are typically added in an incremental fashion
(e.g. one at a time, or several at a time) to provide transport services upon
demand.

In certain scenarios such as field reconfigurations (during a maintenance

window) or lab testing, there may be a requirement to initiate, via the craft
interface, a channel add or delete of a large number of channels at one time.
As a rule of thumb, if there is a requirement to initiate an add or delete of a
large number of channels in one direction, at one time (> 35), then the
operation usually needs to be performed in two or three steps.
DOC actions
This section provides additional details on various DOC actions.
Fault detection, auto-monitoring and fast-poller auto-monitoring cycles

DOC runs periodic system health checks on its Photonic domain, provided it
is in service (IS) and that the “Invalid Photonic Domain” alarm is not raised.
The following cycles are involved:
• Fault detection
• Auto-monitoring
• Fast-poller auto-monitoring
The periodicity of each of the different cycles is as follows:

• DOC Fault detection routine and DOC auto-monitor run on an interleaved
cycle:
— 1st minute: DOC fault detection
— 2nd minute: DOC fault detection
— 3rd minute: DOC auto-monitor
— 4th minute: DOC fault detection
— 5th minute: DOC fault detection
— 6th minute: DOC auto-monitor
— and so on
• The DOC fast-poller is run every 5 seconds
Fault detection description

The fault detection routine helps to identify potential faults that could fail
subsequent DOC-related actions such as re-optimizations, channel
additions/deletions and Power Audit (SRA calibration). All SOCs are checked
within the Photonic domain, even if one of the SOCs reports a fault.
Here is a summary of continuous automatic fault detection in DOC:

• Runs regardless of the DOC Automation Mode setting. That is, it runs
when DOC automation mode is set to Enhanced, Enhanced Auto Monitor
Only, Foreign Line or Foreign Line Enhanced.

• Checks all DOC in-service channels (Channel Condition of “Optimized” or

“Not Optimized”).
• Checks all “Inactive” channels that have their active flag set to “True”.
• Does not run if there are any partially added/deleted channels in the
domain or if DOC is out-of-service.
• While it runs, the DOC Overall Status shows as “Performing Fault
Detection” and the DOC Command Status shows as “READY”.
• Can be interrupted by other DOC command requests (for example,
Channel Add).
• Raises the “DOC Action: Fault Detected” alarm when it detects a fault.
DOC Channel Fault Status and DOC Logs are used to help troubleshoot
the alarm.
Continuous automatic fault detection also performs the following types of

checks:
• Check that data communications are up between DOC and SOC(s).
• Check the ability to obtain provisioning data and circuit pack data.
• For each channel, check that all required facilities exist.
• For each channel, check for excess loss in the section ingress.
• Check that the WSS controller overall state is “RUNNING” and for each
channel, that the WSS controller channel state is “NORMAL”.
Auto-monitoring and automatic reoptimization description

The auto monitoring cycle assesses whether the current Photonic domain
operating point is optimal by evaluating and comparing the optical
performance of the channels present in the Photonic domain.
DOC monitoring/optimization relies on sectional optical control (SOC)
algorithms which perform adjustments to local optical controller (LOC)
actuators:
• Monitoring via a peak power control algorithm per section:
— This consists of tracking the peak channel power to a provisioned peak
power target at the output of each EDFA in a section.
— The only actuator used during a peak power optimization is the EDFA
gain.
— By doing this, peak power control maximizes the power out of each
amplifier (while respecting the power mask of the device) in a section
to minimize the OSNR impact of a chain of amplifiers and it prevents
individual wavelength power from exceeding the amplifier target peak
power over which optical non-linearities starts to degrade
performance.

— Peak power control uses an estimation of the peak channel power

through a Virtual OSA algorithm.
• Monitoring of the optical spectrum to improve incremental OSNR.
Per-channel incremental OSNR represents the amount of change in the
OSNR of a given channel between the beginning and the end of the
section in dB.
— This consists of measuring the per-channel power spectrum profile at
the end of the optical section by using the OPM data where the OPM
is present.
— If the OPM is not present, e.g. in a section consisting of only TOADM
nodes, an estimate is made.
— The process tries to flatten the spectrum in an effort to flatten the
incremental OSNR over all channels. It may also involve equalization
of channel power levels at various locations.
— The WSS/RLA Network Media Channel Control (NMCC) and/or
SCMD4 VOA facilities are used as the actuators during an incremental
OSNR optimization.
— All the required power and OSNR profiles are estimated through a
Virtual OSA algorithm.
Monitoring depends on the DOC Automation mode setting in the following

manner:
• When DOC Automation mode is set to Enhanced
DOC auto-monitoring cycle monitors the Channel Optimization State
(COS) of all in-service channels in the Photonic domain. If DOC
auto-monitoring determines the Photonic domain to be “Non-Optimal”,
DOC automatically re-optimizes the in-service channels. The process
includes:
— Monitoring actions: during the monitoring process, DOC queries all
SOCs for their optimization status. SOCs determine their optimization
status by checking drift away from the optimal operating point. This
includes checking for drift in the estimated channel peak power of each
amplifier and the drift in the estimated OSNR at the end of each optical
section. If the drift exceeds internally set thresholds in any optical
section, the COS is set to “Not Optimized” for each in-service channel
and the DOC Photonic domain Overall Status is set to “Non-Optimal”.
The “DOC Domain Not Optimized” alarm is raised. Photonic alarms
like “High Received Span Loss” and “High Fiber Loss” along with
Photonic PMs and Photonic PM TCAs can be used to help identify the
cause of the drift. Note that by default, the Photonic PM TCAs are set
to be raised when the current PM reading is ± 6 dB away from the PM
Baseline value.

Monitoring also checks for capacity changes in the Photonic domain.

If a channel addition or deletion was performed since the last cycle, a
domain re-optimization is triggered (see “Channel add” on page 2-36
for more details).
— The re-optimization actions performed by DOC are the same as the
optimization actions performed at the end of the channel add/delete
operation.
— Note that the “DOC Domain Not Optimized” alarm is not raised
between the time that the process determines that the DOC Photonic
domain is “Non-Optimal” and the time that the re-optimization
completes successfully. If the re-optimization process fails, the alarm
is raised.
— Note that the PM TCA Baselines are not reset after the re-optimization.
This is done in an effort to avoid DOC from “tracking” degrading
systems/hardware. If required, you can reset the PM TCA Baselines
using the “Reset TCA Baselines” button in the Site Manager DOC
application.
— Note that the re-optimization is blocked if DOC detects excess loss
through the “fiber pinch” feature (see “DOC fiber pinch detection
feature” on page 2-53 for more details).
• When DOC Automation mode is set to Enhanced Auto Monitor Only
The Enhanced Auto Monitor Only mode operates like the Enhanced mode
except that if the domain is found non-optimal by the DOC auto-monitoring
cycle, no automatic re-optimization occurs. The “DOC Domain Not
Optimized” alarm is raised and the Channel status becomes non-optimal.
Note that editing DOC automation mode between Enhanced and
Enhanced Auto Monitor Only does not require that the DOC primary state
be put OOS.
Fast-poller auto-monitoring description

As indicated earlier, the DOC auto monitor cycle runs every 3 minutes. It
checks both the peak power and incremental OSNR monitors:
• If either or both monitors declare non-optimal status, the domain is
declared non-optimal and an optimization is performed if the DOC
Automation mode is Enhanced.
• A full optimization consists of a peak power optimization followed by an
incremental OSNR optimization. Refer to “Thresholds for full
reoptimization (peak power and incremental OSNR optimization)” on page
2-34.
• DOC holds off auto-monitor triggered optimization for 2 monitor cycles if
fiber pinch comes from upstream.

The DOC fast-poller auto monitor cycle runs every 5 seconds and checks only
the peak power monitor:
• If the peak power monitor declares non-optimal status, the domain is not
declared non-optimal but an optimization is performed if the DOC
Automation mode is Enhanced.
• A peak power-only optimization is done.
The benefit of the fast-poller auto monitor cycle is that the system can more
quickly compensate for excess loss and restore the OSNR to the pre-excess
loss values.
The DOC fast-poller auto monitor cycle also:

• Checks the photonic domain input powers against a stored profile using
the WSS/RLA NMCC facility Reference Input Power Profile.
• Indicates if a channel is degraded via its Channel Fault Status (CFS). A
channel is degraded if its power is less than the (Reference Input Power
Profile value – a user-defined Degrade Threshold value).
• Updates the CFS if a managed channel is found faulted.
• Checks for ‘Partially Added’ channels with CFS ‘Waiting for Power’ that
would now pass the 3 dB power check, to signal DOC to re-attempt the
channel add (this is the behavior under Mode 1).
— If not under Mode 1, it pre-checks DIA, Colorless or CDC ‘Inactive’
channels with a TRUE ADJ-TX Active flag.
Thresholds for full reoptimization (peak power and incremental OSNR

optimization)
DOC decides whether a full (peak power followed by incremental OSNR
based optimization) reoptimization is required based on two main criteria:
• Per-channel power levels change (e.g. in response to fiber pinch):
The highest power channel no longer meets the provisioned peak power
target on the line, or any channel is not within the calculated acceptable
receiver range. This has a threshold of 1.25 dB and triggers a peak power
re-opt assuming the actuators (EDFA gain) have room to adjust. For
instance, it is possible to have a valid design where a preamp is at
maximum gain, but cannot meet the provisioned target by several dB’s;
this will not continually trigger re-opts since the amp is already at
maximum gain.
• Incremental OSNR values change:
Channels traversing a common path need to be within 2.5 dB of each
other in terms of their incremental OSNR, otherwise a re-optimization is
triggered.

Various types of faults or degradations result in not meeting one or both of the
criteria above.
• For instance a span fiber pinch may not affect relative OSNR equalization
(all affected equally), but channels wouldn’t be meeting the peak power
target, so a gain increase would be required.
• A Tx fiber pinch or change in Tx power may not result in failing the first
criteria (if another channel is still meeting the peak power target), but
would affect relative OSNR equalization and would trigger a reoptimization
to primarily adjust WSS/RLA pixel (or SCMD VOA) losses.
• Depending on the degree of the degradation, some or all channels may be
excluded from the re-optimization to avoid impacting other channels when
the degradation is removed (i.e., to limit the amount of overshoot).
Channel add/delete processes and related DOC functions

This section presents the DOC channel add and delete processes and other
DOC functions such as pre-check, manual re-optimization, Reset TCA and
Stop DOC action.
Attention: DOC actions and channel add/delete processes in Submarine

applications are described in the Submarine Networking Application Guide,
NTRN72AA.
Attention: The Add/Delete functions in the DOC application are unavailable

for an OTS with Autoroute disabled, and the corresponding buttons are
grayed out in Site Manager. This is typically the case when using the L0 CP.
You must then use the Sub-Network Connections application to set the
Primary State of SNC, or the Photonic Connections application to set the
Active flag of photonic connection to trigger channel actions as appropriate.
Modes of operation for channel capacity changes

As of Rel. 12.4, it is possible to specify the speed with which the system
performs channel capacity changes. Increasing this speed is especially
beneficial to mesh restoration actions occurring in L0 CP networks, where
large number of channels need to be deleted, de-provisioned, re-provisioned
and re-added along different paths.
Three Modes are available (Mode 1, 2 and 3). Mode 1 is the default Mode and
does not need to be explicitly provisioned, however it only activates provided
certain rules are met (see “Engineering rules related to Mode 1 capacity
change mode” on page 4-149).

Modes 2 and 3 are reserved for networks using L0 CP with mesh restoration,
and as such are not discussed in this Guide (for these Modes, refer to
Technical Publication NTRN71AA.2, Control Plane Application Guide - Layer
0 [Photonic]).
Although they are taken into account by DOC when performing channel
capacity actions, these Modes are not explicit DOC attributes. Mode setting is
visible in the Photonic connections MCTTP object, under the 'Capacity
Change Mode' parameter (see “Photonic connection attributes” on page
1-61).
Channel add
The channel add process can be user-initiated or system-initiated:
• It is user-initiated when the Add button is clicked in the Site Manager DOC
application after selecting a channel or a set of channels.
• It is system-initiated when Auto add channels is enabled, and DOC
detects “Inactive” channels featuring a “TRUE” Active flag. This is normally
the case when using L0 Control Plane.
In either case, the channel addition process adds channels to the Photonic
domain while preserving traffic on the existing channels in the Photonic
domain (if any).
New channels are always ramped up very quickly:

• No pre-check initiated by DOC is done as part of a channel add. For
certain configurations, pre-check can be invoked manually prior to the
channel add (see “DOC manual pre-check” on page 2-43).
• At the node where the new channels originate, for each ROADM
WSS/RLA NMCC facility associated with a channel to add, the Target Loss
is set to the best “fit” value in a single step and the Opaque value is set to
unblock (Opaque=No).
— If the conditions are not met for Mode 1 to be used (refer to
“Engineering rules related to Mode 1 capacity change mode” on page
4-149), then for a DIA, Colorless, CDA or CDC ‘Inactive’ channel, the
DOC fast-poller auto monitor cycle runs an automatic power check
routine if the channel CMD ADJ-TX Active flag is TRUE:
– For Colorless channels, DOC checks COADM OTS SMD “ready”
status. For CDA or CDC channels, DOC checks the expected input
power at the backbone WSS mux input against the real-time
estimated input power.
– If the Inactive channel passes the power check, Channel Fault
Status (CFS) becomes “Add Pending” and the channel starts to
add.

– If the Inactive channel fails the check, CFS becomes “Waiting for
Power” and the channel does not start to add. It will be checked
again automatically in the next fast-poller auto monitor cycle.
Note that DOC does not run this power check if the DOC “Auto add
channels” parameter is disabled.
— Under Mode 1, CFS becomes “Waiting for Power” right away, and the
WSS power controller starts ramping up the channel power if the
measured input power is within 3 dB of the expected input power. If the
3 dB condition on measured power is still not met after 6 minutes, CFS
becomes ‘Partially Added’ and the ‘NMCC Action Failed: Add’ alarm
raises.
Similarly, for each TOADM SCMD4 VOA facility associated with a channel
to add, the target loss is set to the best “fit” value in a single step, and the
loss value decreases from its default value of 15 dB (the VOA range is
20 dB).
• If no channels are present when the add operation is done (initial system
turn-up), and Dark Section Conditioning is not enabled (see “Dark Section
Conditioning” on page 2-98), then the amplifier gains are set and DOC
starts adjusting them along with the WSS controllers to optimize its
domain.
• When the new channels reach power levels estimated good enough for
them to carry error-free traffic (even if they don’t terminate in this photonic
domain), their Channel Optimization State (COS) is displayed as
“In-Service”. TCA baselines are reset.
• For new channels spanning more than one photonic domain:
— If the conditions are not met for Mode 1 to be used (refer to
4-149), then the channel add only starts in a given domain if the
upstream domain reports the channel as ‘In-Service’.
— Under Mode 1, there is no dependency on the upstream domain COS
for the channel add actions to start in a given domain. This means the
WSS controllers all along the channel path work in parallel rather than
in sequence, so the channel add completes faster. In all domains at
once, the CFS becomes “Waiting for Power”. At a ROADM
passthrough, if the measured power by the WSS controller is not
within 3 dB of the expected power level 12 seconds after the upstream
COS is declared ‘In-Service’, the local COS becomes ‘Partially Added’
and the ‘NMCC Action Failed: Add’ alarm raises.
The upstream COS does have an influence over a given domain COS
though:

– If the upstream domain COS is ‘In-Service’, a given domain COS

becomes ‘In-Service’ provided its ROADM WSS controller has
converged. This information is then passed to the downstream
domain.
– If the upstream domain COS is ‘Adding’, a given domain COS
becomes ‘Partially Added’ and this information is passed to the
downstream domain.
– If the upstream domain COS is ‘Partially Added’, a given domain
COS becomes ‘Partially Added’ too to match the upstream domain
COS, even if the given domain ROADM WSS controller has
converged.
This means that over the course of the channel add action, it is likely
to observe transient ‘Partially Added’ COS, which eventually clear
when all domains complete their optimization work.
• When the new channels reach power levels good enough for them to carry
error-free traffic, their Channel Condition and End-to-End Condition are
displayed as “In-Service”. TCA baselines are reset.
After the channels are added and have a Channel Condition of In-Service,
DOC waits two minutes and attempts a background re-optimization aiming at
maximizing the channels available margin. If this re-optimization is:
• Successful: The Channel Condition and End-to-End Condition for the new
channels are displayed as “Optimized”, TCA baselines are reset again and
DOC reverts to the regular auto monitor cycle (see “Fault detection,
auto-monitoring and fast-poller auto-monitoring cycles” on page 2-30).
• Unsuccessful: DOC sets the Channel Condition of any “In-Service”
channel to “Non Optimal”. The optimization is re-attempted every two
minutes until successful.
— DOC restores the Channel Condition of all managed channels from
“Re-optimizing” back to their original Channel Condition if the
re-optimization is aborted.
The following provides additional details on the channel add process:

• Channels to add are not queued, actions are done on all selected
channels
• If a fault is detected during an Add Channel command on a subset of the
selected channels, DOC continues to finish the add action for the
non-faulted channels.
— Channels that fail to add have a Channel Condition of “Partially
Added”.

— DOC re-attempts to add any “Partially Added” channel periodically as

long as the Active flag of the channel remains as “TRUE” and the DOC
Auto add channels parameter is Enabled.
– Under Mode 1, if DOC previously failed to add the channel while it
was in ‘Waiting for power’ and failed the 3 dB power check, DOC
keeps performing the power check every ~ 5 sec (as part of the fast
poller cycle). Then, as soon as the channel passes the power
check, DOC re-attempts the channel add right away. For other
failure reasons (such as OPM in LOS, AMP in shut-off or APR,
etc.), DOC re-attempts the channel add only every 15 minutes, as
these types of fault necessitate more troubleshooting time.
– When not under Mode 1, DOC re-attempts the add every two
minutes.
— You can manually re-add or delete a “Partially Added” channel.
• Channel adds are allowed to interrupt any on-going re-optimization
operation.
• Channel adds are not blocked by DOC overall status or optimization state,
resulting in less time required between channel additions. In other words,
the Photonic Domain does not have to be in an “optimal” state in order to
perform a channel addition, which can thus be performed on a:
— “Non-Optimal” domain
— Domain with partially added or partially deleted channels
— Domain with missing channels or faults
See “DOC actions blocking behaviour summary” on page 2-47 for more
details.
Channel add exception cases

In some channel add scenarios, traffic may not be up until the background
re-optimization completes successfully. Even in these scenarios, new
channels may still carry traffic when the channel add completes successfully
and the Channel Condition is reported as In-Service, but most likely only carry
traffic when the background re-optimization completes successfully and the
Channel Condition is reported as Optimized.
The following describes such channel add scenarios. Note that for the
purposes of the description below, the OADM node input port is defined as a
local add port of an active 6500 channel access OTS used in a terminal or
passthrough/branching configuration:
• Adding a new channel (or channels) on one of the input ports of an OADM
node AND the channel has a lower Differential Provisioning modulation
class than existing channels on that same port. For example, adding a
channel with a -3 dB class bias on the port of a node where existing
channels on that same port have a bias greater than -3 dB. Subsequent

channel additions with that same bias of -3 dB on that same port will not
suffer from this same limitation and the channels will carry traffic when the
Channel Condition is reported as In-Service.
• Adding a new channel (or channels) on one of the input ports of a node
which has no existing channels but there are existing channels on other
ports of that same node AND the new channel is weaker in power
compared to existing channels on the other ports. For example, adding a
passthrough channel at a ROADM/TOADM OTS and existing locally
added channels are stronger power. Subsequent channel additions on this
path will not suffer from this same limitation and the channels will carry
traffic when the Channel Condition is reported as In-Service.
• Adding a new channel (or channels) on a newly added cascaded sCMD of
one of the input ports of a node which has no existing channels but there
are existing channels on other cascaded sCMDs on that same port of that
same node AND the new channel is weaker in power compared to existing
channels of the other cascaded sCMDs. For example, adding a new
sCMD4 to an existing cascaded sCMD4.
Normal channel delete

The channel deletion process deletes channels from the Photonic domain
while preserving traffic on the existing channels in the Photonic domain.
The channel delete process can be user-initiated or system-initiated:

• It is user-initiated when the Delete button is clicked in the Site Manager
DOC application after selecting a channel or a set of channels.
• It is system-initiated when Auto delete channels is enabled, and DOC
detects “Optimized” channels featuring a “FALSE” Active flag. This is
normally the case when using L0 Control Plane.
The channel delete process does the following:

• For each WSS/RLA NMCC facility associated with a channel to delete, the
Target Loss is set to the maximum attenuation value in a single step and
the Opaque value is set to block (Opaque=Yes).
• For each SCMD4 VOA facility associated with a channel to delete, the
target loss is set to the maximum attenuation value in a single step. Even
then though, the amplifiers might not enter their shut-off state, as light from
connected transponders to the SCMD4 might still be powerful enough to
be above the amplifier shut-off threshold.
• For channels spanning more than one photonic domain:
— Whether the conditions for Mode 1 operation are met or not, (refer to
4-149), delete actions are sequenced starting with the tail-end domain
and moving upstream towards the head-end. The overall process is
nevertheless faster under Mode 1.

• After a successful channel deletion, TCA baselines are reset.

— If not using L0 Control Plane, the deleted channels still appear in the
DOC channel list with a Channel Optimization State of ‘Inactive’. To
remove Inactive channels from the DOC channel list, the channel must
be deprovisioned. That is, the CMD ADJ-TX/RX adjacencies must be
modified such that the Transmitter/Receiver type is set to “Unknown”
either manually by you or by SPLI and Photonic connections need to
be deleted at any intermediate ROADM nodes.
— If using L0 Control Plane, Photonic connections are automatically
deleted once the channels reach the ‘Inactive’ state (except for
Permanent SNCs).
After the channels are deleted and have a Channel Optimization State of
‘Inactive’, DOC waits two minutes and attempts a background optimization
aiming at maximizing the remaining channels available margin. If this
optimization is:
• Successful: TCA baselines are reset again and DOC reverts to the regular
auto monitor cycle (see “Fault detection, auto-monitoring and fast-poller
auto-monitoring cycles” on page 2-30).
• Unsuccessful: optimization is re-attempted every two minutes until
successful.
— DOC sets the Channel Condition of any “In-Service” channel to
“Non-optimal” after a failed re-optimization.
— DOC restores the Channel Condition of all managed channels from
“Re-optimizing” back to their original Channel Condition if the
re-optimization is aborted.
The following provides additional details on the channel delete process:

• Channels to delete are not queued, actions are done on all selected
channels.
• If a fault is detected during a Delete Channel command on a subset of the
selected channels, DOC continues to finish the delete action for the
non-faulted channels.
— Channels that fail to delete have a Channel Condition of “Partially
Deleted”
— DOC attempts to delete any “Partially Deleted” channel every two
minutes when DOC Auto delete channels parameter is Enabled
— You can manually delete a “Partially Deleted” channel
• Channel deletes are allowed to interrupt any on-going re-optimization
operation.

• Channel delete are not blocked by DOC overall status or optimization

state, resulting in less time required between channel deletions. In other
words, the Photonic Domain does not have to be in an “optimized” state in
order to perform a channel deletion, which can thus be performed on a:
— “Non-Optimal” domain
— Domain with partially added or partially deleted channels
— Domain with missing channels or faults
See “DOC actions blocking behaviour summary” on page 2-47 for more
details.
Smart delete
In a Smart delete operation, DOC sets the Channel Optimization State of the
channels to be deleted to ‘Inactive’ right away. Then, for each WSS/RLA
NMCC facility associated with a channel to delete, the Opaque value is set to
block (Opaque=Yes) right away, without ramping up the Target Loss to its
maximum attenuation value. Smart delete is used in scenarios where the
deletion process must be completed quickly, for example in a L0 Control Plane
mesh restoration. It is system-initiated, the user cannot manually invoke a
Smart delete.
Delete to dark
Delete to dark occurs when all channels on a section are deleted at once. This
typically occurs in L0 Control Plane mesh restoration scenarios, on the faulted
OSRP Line. Delete to dark proceeds like Smart delete. Following a Delete to
dark action, Dark Section Conditioning kicks in, if enabled (see “Dark Section
Conditioning” on page 2-98).
CRS-initiated delete
This delete process is invoked in L0 Control Plane systems with Mode 2 and
Mode 3 (see “Modes of operation for channel capacity changes” on page
2-35). To free up the photonic connections even faster than Smart delete, the
photonic connections are deleted firsthand and do not wait on DOC to report
the channels as “Inactive”.
Force delete
The purpose of the Force delete is to ensure that channels can be removed
from the system, even under fault scenarios. The Force delete does not ramp
channels down gradually in the same way as the normal delete, and therefore
it may be service-affecting if performed on in-service traffic. The Force Delete
must only be used after a normal delete has been attempted and failed
(resulting in “Partially Deleted” channels).
The most common use of the Force delete is to remove a channel from service
that is faulted due to a failed transponder or Photonic circuit pack. In the case
of a failed transponder, the signal has already been removed from the

spectrum, and therefore the Force delete is effectively non-service-affecting in

this scenario (i.e. the Force Delete will not cause further perturbations to in
service channels).
Note that Force delete does not automatically re-optimize the Photonic
domain after the deletion operation has completed.
Upon successful completion of the Force delete command, the following tasks
must be performed in order to ensure that the optical path is optimized:
• Follow and complete the appropriate standard trouble clearing procedure.
• The DOC Automation mode must be set to “Enhanced” to ensure an
automatic reoptimization occurs. Note: For the “Enhanced with
Auto-Monitor only” mode, an automatic reoptimization only occurs after a
normal channel add or delete.
Attention: Force Delete does not sequence actions across domains like the
normal delete does. Therefore a Force Delete must not be performed unless
the channel has been deleted (either via a normal or Force Delete) in
downstream domains first, so as to not “strand” channels in downstream
domains.
DOC manual pre-check

DOC pre-check quickly informs operators whether or not a channel is likely to
be added successfully without having to physically start the DOC channel add
operation. It is user-initiated by clicking the Pre-check button in the DOC
application. It is done on a per-channel basis and can be run on multiple
channels at the same time. All selected channels are checked up front without
any DOC channel queuing.
Attention: DOC manual pre-check is not supported at CDC or Colorless

nodes. If initiated, it always passes.
The following lists the faults that can be detected by DOC pre-check:
• At channel access ROADM nodes, the transmitters are not plugged in or
incorrectly provisioned (the power into the CMD44 input port is 3 dB more
or 3 dB less than the maximum/typical launch power provisioned for the
CMD44 Tx adjacency).
• At channel access Thin Terminal or TOADM nodes, the transmitters are
not plugged in or the power into the SCMD4 input port is 3 dB more or
3 dB less than the maximum/typical launch power provisioned for the
SCMD4 Tx adjacency).

• At channel access DIA nodes, the transmitters are not plugged in or

incorrectly provisioned (the power into the CMD44 input port is 3 dB more
or 3 dB less than the maximum/typical launch power provisioned for the
CMD44 Tx adjacency).
Attention: Because the Thin Terminal or TOADM node is not deployed with
a local OPM function, there is a possibility that the pre-check passes initially
if transmitters are incorrectly tuned but properly connected to the SCMD4
mux input ports. Similarly for the vice-versa case where the transmitters are
correctly tuned, but connected to the wrong port. The pre-check bases its
decision on the presence of optical power at the ingress VOA tap which does
not distinguish wavelength. A subsequent channel addition action fails once
software realizes an inconsistency in per-channel power levels at
downstream locations.
• Facilities are deleted or out-of-service.

• Facilities are in the incorrect provisioned state (for example, AMPs not
in-service).
• WSS/RLA controller overall status in the checked channel path is not in
the “RUNNING” state.
• The individual WSS/RLA controller channel status in the checked channel
path is in a FAULT state (or equivalently, the NMCC secondary state is
FAF).
• Inability to retrieve data and measurements from all circuit packs from all
sections which the channel traverses.
The DOC pre-check must be user-initiated on selected channels using Site

Manager or TL1.
When performing a pre-check, the following should be noted:

• The pre-check can take between 15 seconds and 5 minutes depending on
how many channels are being pre-checked.
• Performing a manual pre-check temporarily allows light on the system.
Attention: Performing a manual pre-check may cause downstream AMP

facilities to exit shutoff and then return to shutoff once the pre-check is
completed. In this case, toggling alarms appear in the network.
User-initiated re-optimization
Re-optimization is a task where the system performance is optimized in a
non-service-affecting manner. Generally, this optimization tracks aging and
very slow changes in operating conditions. You can initiate a re-optimization

using the Re-Optimize button in the Site Manager DOC application. You can
initiate a manual re-optimization as long as DOC is managing at least one
channel and no other DOC actions are in progress.
The re-optimization actions performed by DOC are the same as the

optimization actions performed following a channel add/delete operation.
Note that the PM TCA Baselines are not reset after the re-optimization. This
is done in an effort to avoid DOC from “tracking” degrading systems/hardware.
If required, the PM TCA Baselines can be user-initiated via the “Reset TCA
Baselines” button in the Site Manager DOC application.
Note that the re-optimization is blocked if DOC detects excess loss through
the “fiber pinch” feature (see “DOC fiber pinch detection feature” on page 2-53
for more details).
Reset TCA baselines

After a DOC capacity change (channel add or channel delete operation), DOC
automatically resets the TCA baselines for all facilities associated with
Optimized channels in the DOC domain.
Using the Reset TCA Baselines button of the Site Manager DOC application,
you can manually reset the TCA Baselines for all facilities associated with
in-service channels in the Photonic domain, with a single mouse click.
Resetting TCA baselines sets the “baseline” value of the facility parameter to
its current untimed value.
For configurations using the NTK552FB MLA2v, the MLA2v VOA facility PM
TCA baselines are reset as part of a channel add/delete operation. They can
also be reset using the “Reset TCA Baselines” button in the Site Manager
DOC application.
For 6500 T-Series CDC configurations, the RLA VOA facility and RLA WSS
Switch In OPTMON facility PM TCA baselines are reset as part of a channel
add/delete operation. They can also be reset using the “Reset TCA Baselines”
button in the Site Manager DOC application.
For Line Amp nodes containing an OPM (see “Photonic Line Amplifier node
with OPM” on page 4-131):
• CHMON PM baselines are reset by DOC after a DOC channel add/delete
operation or using the DOC application “Reset TCA Baselines” command.
• OPM circuit pack OPTMON PM baselines are not reset by DOC. These
should be user-baselined after a channel add/delete operation using the
Site Manager PM application.

For configurations using the NTK552JA SRA, NTK552JT ESAM or

NTK552JN SAM circuit packs:
• DOC resets TCA baselines on the SRA RAMAN facility (Line A In / Line A
Out) and SRA OPTMON facility (Line B In) during channel adds and
deletes, the first re-optimization after a channel capacity change, and
when you reset TCA baselines manually.
• DOC resets TCA baselines on SAM/ESAM OPTMON facilities during
channel add, channel delete, the first re-optimization after a channel
capacity change, and when you reset TCA baselines manually.
• The TCA baseline operation covers ports 6 and 8.
For CDA or CDC configurations deployed in a greenfield scenario:

• DOC resets TCA baselines on WSS 20x1 OPTMON facilities for the
common input, common output, switch input, and OPM ports. There is no
baseline reset for the switch output port OPTMON facility.
• There is no TCA baseline reset for any facility on CCMD8x16 ports or the
CCMD12.
For CDC configurations deployed in a brownfield scenario:

• DOC does not reset TCA baselines for any facility on WSS 20x1 ports.
• There is no TCA baseline reset for any facility on CCMD8x16 ports.
For 6500 T-Series CDC configurations:

• DOC resets TCA baselines on RLA WSS Switch In OPTMON facilities.
• There is no TCA baseline reset for any facility on CCMD 16x12 or CCMD
8x4 ports.
For all CDA or CDC configurations, using the “Reset TCA Baselines” button in
the Site Manager DOC application yields the same results.
Baselines can also be reset on a per-port basis using the Site Manager
Performance->Performance Monitoring application.
Stop DOC action

The Stop DOC action task can be used to abort a channel add, channel delete
or SRA power audit operation. A re-optimization operation cannot be aborted.
After the channel add/delete process is aborted, channels being
added/deleted have a “partially added/partially deleted” COS, while the rest of
the channels have a “Non-Optimal” COS. The “DOC Domain Not Optimized”
alarm is raised. The alarm is not cleared until you issue commands to add or
delete the partially added/partially deleted channels.

Attention: If you stop a manual deletion of optical channels before all the
selected optical channels become “Inactive”, some of the optical channels
will be shown as “Partially Deleted” and some will be shown as
“Non-Optimal”. If the Partially Deleted optical channels are deleted and
re-added, after re-optimizing all the optical channels will be shown as
Optimal. However, the Active parameter for the deleted/added optical
channels will be TRUE but will be FALSE for the optical channels which were
originally selected for deletion but were not deleted. You must manually
change the Active field of these optical channels to TRUE (see the Editing a
Tx adjacency procedure in Technical Publication 323-1851-310,
Configuration - Provisioning and Operating).
DOC actions blocking behaviour summary

Blocking behaviour in capacity change scenarios
DOC can perform different capacity change actions simultaneously within the
same action. For example:
• When DOC receives a request to add channels while it is already adding
some other channels, it proceeds with adding the newly provisioned
channels without interrupting the preceding channel add.
• When DOC receives a request to delete channels while it is already
deleting some other channels, it proceeds with deleting the newly
de-provisioned channels without interrupting the preceding channel
delete.
• DOC also allows channel add and normal channel delete actions to occur
at the same time during the same capacity change cycle.
Table 2-4 lists in details the allowed DOC concurrent actions.

Table 2-4
Allowed concurrent DOC actions
Ongoing action Permitted concurrent actions Handling of concurrent action
Addition of a set of Addition of a new set of channels Process the add right away
channels
Normal delete on an existing set of Process the delete right away
channels
Normal delete on the currently Process the delete right away

adding channels
Smart delete on a new set of Process the delete right away

channels or existing adding
channels
Delete to dark on all existing Process the delete right away

channels
CRS-initiated delete on a new set of Process the delete right away

channels or adding channels
Normal delete of a set of Addition of a new set of channels Process the add right away
channels
Addition of currently deleting Process the add right away
channels
Normal delete on a new set of Process the delete right away

channels

channels or existing deleting
channels

channels

channels

Table 2-4
Allowed concurrent DOC actions (continued)
Smart Delete on a set of Addition of a new set of channels Process the add right away
channels
Re-addition of the existing deleting Complete Smart delete first, then
channels re-add

channels

channels

channels

channels
CRS-initiated delete on a Addition of a new set of channels Process the add right away
set of channels
Re-addition of the existing deleting Complete CRS-initiated delete first,
channels then re-add

channels

channels

channels

channels
Blocking behaviour in fault scenarios

This section details the availability of system functions in fault scenarios:
• If channels are being added to a domain and some of them cannot be
added successfully, only these unsuccessful channels become “Partially
Added”, and the action continues.
• If faulted channels are present in the Photonic domain:
— If all channel access nodes in the photonic domain are ROADM, when
a DOC-controlled channel is found to be faulted, it is dropped from the
DOC control list and DOC channel add/delete or optimization
operations are not blocked (provided the intended operation is not
affected by the fault).

— If at least one channel access node in the photonic domain is TOADM

or GOADM, DOC channel add/delete or optimization operations are
blocked when DOC-controlled channels are faulted within the photonic
domain.
• If the Photonic domain is “Non-Optimal”, channel adds and deletes
(whether user- or system-initiated) are allowed. For the “Enhanced with
Auto-Monitor Only” mode, if the domain is found Non-Optimal by the auto
monitor action, no automatic re-optimization occurs. The “DOC Domain
Not Optimized” alarm is raised and the Channel status becomes
non-optimal.
• If there are Partially Added or Partially Deleted channels in the domain:
— Some automated DOC actions are blocked:
– Re-optimization
– Auto-monitoring
– Fault detection
– Reset TCA
— Automated DOC channel actions are allowed:
– Auto add, Auto delete
— Some user-initiated DOC actions are allowed:
– Add, Delete for any channel (partial or not)
Any channel added in the presence of other partial channels remain in
the “In-Service” state, since automatic or manual re-optimizations
occurring after the Channel Add action do not proceed in the presence
of Partially Added or Partially Deleted channels.
Topology application affects on DOC actions
Provisioning changes or actions that cause topology to rebuild must be
avoided when performing DOC add or delete channel operations.
Attention: It is required that the channel trail topology be modified only after
its end-to-end condition is “Inactive” AND only after all associated
subsequent reoptimizations within any domain along the entire channel path
are completed.
These provisioning changes or actions are:

• provisioning channels (i.e., Tx/Rx adjacency provisioning)
• adding/removing nodes
• adding/removing/editing OTSs
• restarting nodes

• upgrading nodes
• replacing circuit packs
• performing system maintenance
• maintenance actions
Monitoring DOC action status and progress

DOC action status and progress is available from within the Site Manager
DOC application and through DOC related alarms as follows.
DOC-specific alarms
The following alarms are raised during various DOC operations:
• “DOC Action: Channel Add In Progress” alarm: during a channel add
operation, the “DOC Action: Channel Add In Progress” alarm is raised. It
clears when the channel add operation completes successfully or fails. If
the channel add operation fails, the “DOC Action Failed: Add” alarm is
raised. If there were existing in-service channels when the channel add
operation was started and the channel add operation fails, the “DOC
Domain Not Optimized” alarm is also raised.
• “DOC Action: Channel Delete In Progress” alarm: during a channel delete
operation, the “DOC Action: Channel Delete In Progress” alarm is raised.
It clears when the channel delete operation completes successfully or
fails. If the channel delete operation fails, the “DOC Action Failed: Delete”
alarm is raised. If there were existing in-service channels when the
channel delete operation was started and the channel delete operation
fails, the “DOC Domain Not Optimized” alarm is also raised.
Attention: As of Rel. 12.4, the “DOC Action: Channel Add In Progress” and
“DOC Action: Channel Delete In Progress” alarms are not used anymore, as
DOC can potentially be adding and deleting channels within the same DOC
action. Also, the “DOC Action Failed: Add” and “DOC Action Failed: Delete”
alarms are replaced with “NMCC Action Failed: Add” and “NMCC Action
Failed: Delete” alarms respectively.
The 4 deprecated alarms could nevertheless still be seen on systems in a
mixed releases state with some nodes running a release prior to Rel. 12.4,
and in systems running Rel. 12.4 or higher that include multi-section optical
domains.
• “DOC Action Failed: Monitor” alarm: raised after 2 consecutive failed auto
monitors. The alarm is cleared when there is a successful auto monitor or
optimization action, or when there is no longer any managed channels.
This only applies to the Enhanced Auto Monitor Only automation mode.

• “DOC Action Failed: Optimize” alarm: raised after 4 consecutive failed

auto optimizations.
— If there is already an outstanding optimization failure count, an auto
monitor failure feeds into the optimization failure hold off count.
— The hold off count is not increased for a user-initiated optimization or
a peak power-only optimization.
The alarm is cleared when there is a successful auto monitor and the auto
monitor result is optimal, or a successful optimization action (including
peak power-only optimization), or when there is no longer any managed
channels.
• “DOC Domain Not Optimized” alarm: raised if auto monitor declares the
domain is not optimal, with no hold off. It only applies to the Enhanced
Auto Monitor Only automation mode.
The alarm clears when there is a successful full optimization or the domain
is found optimal by auto monitor or there is no managed channel.
• “DOC Action: Fault Detected” alarm: under the Enhanced automation
mode, the alarm is raised after 3 consecutive failed fault detections. Under
the Enhanced Auto Monitor Only automation mode, it is raised after 6
consecutive failed fault detections.
Under both modes, the alarm is cleared when there is a successful fault
detection, auto monitor or optimization action, or when there is no longer
any managed channels.
• “DOC Consecutive Re-Opt Threshold Crossed” alarm: raised when a
re-optimization is taking too long to complete as a result of unstable
powers somewhere in the domain. This could be due to an issue with
hardware or the fiber plant. When the alarm is raised, the DOC Automation
mode is switched from “Enhanced” to “Enhanced Auto Monitor Only”.
To clear the alarm, correct the issue that caused the alarm following
Technical Publication 323-1851-543 Fault Management - Alarm Clearing.
Then perform a manual re-optimization. If the re-optimization completes
successfully, switch the DOC Automation mode back to “Enhanced”.
• “Domain Optical Controller Disabled” alarm: raised when the DOC primary
state is changed to OOS.
• “DOC Power Audit Failed” alarm: this alarm pertains to the power audit
(calibration) of SRAs deployed within an optical section. This alarm is
raised:
— After a power audit has been user-initiated and then the audit is user
aborted using the “Stop DOC Action” command
– DOC logs indicate “Power audit” is aborted

— After a power audit has been user-initiated and the power audit is
blocked or fails:
– The appropriate DOC logs indicate why the power audit failed for
troubleshooting purposes.
– Reasons for failure are described in “DOC event logs during SRA
Power Audit (Calibration)” on page 2-56
— The alarm is cleared after a successful user-initiated power audit or
after a successful channel add action.
For more information about these alarms and how to clear them, refer to
Technical Publication 323-1851-543, Fault Management - Alarm Clearing.
DOC faults and troubleshooting

When a DOC add/delete action fails, the user relies on the "NMCC Action
Failed: Add/Delete" alarm raised at the domain where the action has failed to
debug the failure at the starting point, using outstanding alarm(s) or DOC logs.
DOC maintains logs of previously executed commands along with their
outcomes. DOC and SOC logs are retrievable from the Site Manager DOC
application (Configuration->Photonic Services->Domain Optical Controller
(DOC)) by pressing the “Logs” button. You can use these logs to save and
print topology information in a text format and to troubleshoot DOC alarms.
The DOC Logs button provides up to 50 DOC history logs. If identical DOC
logs are produced consecutively, only the first and last occurrence of the log
are displayed in the log history. Otherwise, each log instance is treated as
unique and recorded in the history.
For more information about these logs, refer to Technical Publication

323-1851-840, Fault Management - Customer Visible Logs.
DOC fiber pinch detection feature

The fiber pinch detection feature is meant to help detect gradual or sudden
unexpected optical power changes on fiber spans. It is based on an algorithm
that, at the beginning of DOC actions, computes the span loss using current
PM readings at both ends of the fiber span, and then compares this current
loss value with a baseline loss value computed using the corresponding
baseline PM values. If the difference between current and baseline values is
higher than a given threshold, called drift threshold, the “DOC Action: Fault
Detected” alarm is raised.
The drift threshold default value is 6 dB. It can be changed by modifying the
ADJ-FIBER Excess Loss parameter on the relevant facility:
• Find the line-facing circuit pack at the transmit end of the span for which
you want to change the drift threshold.

• Edit the ADJ-FIBER facility for the port which has the “LINE” Adjacency
Type to modify the Excess Loss to the desired value.
In an optical domain equipped with gain clamp capable amplifiers on the line,
DOC does not perform the fiber pinch detection. The fiber pinch gets
compensated up to the available amplifier gain margin and is not vulnerable
to overshoots due to the amplifier gain clamp mode (see “EDFA Gain Clamp
mode” on page 2-84).
DOC fiber pinch compensation in a photonic domain section either:

• uses the DOC fiber pinch feature which limits the compensation up to the
ADJ-FIBER facility Drift threshold value (default is 6 dB) and is vulnerable
to overshoots - OR -
• does not use the DOC fiber pinch feature. When the DOC fiber pinch
feature is not used, the fiber pinch gets compensated up to the available
amplifier gain margin and is not vulnerable to overshoots due to the
amplifier gain clamp mode (see “EDFA Gain Clamp mode” on page 2-84).
Software automatically determines not to use the DOC fiber pinch feature if
the section meets ALL the following requirements:
• Every channel access OTS in the section is ROADM
• Every line-facing amplifier in the section is 6500 XLA, MLA2, MLA2v,
MLA3, LIM, RLA or CPL MLA3
• There is no interior/cascaded SLA in the section
• Every shelf in the section has the “High Fiber Loss Alarm Detection”
parameter enabled and has the “High Received Span Loss” detection and
alarm enabled. For details refer to “High Fiber Loss” on page 2-106 and
“High Received Span Loss and Low Received Span Loss” on page 2-104.
When the drift threshold has been exceeded, DOC raises the “DOC Action:
Fault Detected” alarm and DOC-related actions such as channel
add/delete/re-optimization are blocked. Along with this alarm, a
customer-visible log is generated that points the user to the faulty connection.
For more details and troubleshooting information, see Technical Publication
323-1851-840, Fault Management - Customer Visible Logs.
Attention: If the fiber pinch feature is activated during a channel add/delete,

the add/delete stops and channels are left in the “partially add” or “partially
delete” state.

WSS/RLA Reference Input Power Profile

Available on the WSS/RLA NMCC facilities, the Reference Input Power Profile
parameter helps monitor how the channel power changes over time. It
displays a referenced or baselined value for the Derived Input Power
parameter and is used to alarm degraded optical power levels on individual
channels (the alarming is described in “Channel Degrade alarm for WSS/RLA
NMCC facilities” on page 2-109.)
The power profile is system reset after a capacity change (i.e., a channel add
or delete) or can be user-reset using the “Reset Power Profile” button in the
Equipment and Facility Provisioning application. The power profile can also be
manually reset using the “Reset TCA Baselines” button in the DOC
application.
Use of DOC trail to determine incomplete channel trails prior to channel actions
As described in “Topology application affects on DOC actions” on page 2-50,
provisioning changes or actions that cause topology to rebuild must be
avoided when performing DOC add or delete channel operations.
The DOC trail status (refer to “DOC Channels Tab Information” on page 2-26,
is a useful tool which indicates if a channel path has been completely defined
(“Complete” status) or not (“Incomplete” status). In the case where Tx
adjacencies, Rx adjacencies, and/or Photonic connections have not been
provisioned in one or more domains through which a channel traverses, the
DOC trail status indicates “Incomplete”.
are completed.
Prior to any channel addition, the DOC trail status should indicate “Complete”
before the add action is performed. Conversely, any DOC channel deletion
action should be completed end-to-end through all domains, and its
associated DOC trail status must remain “Complete” during this time.
When there are channels that are complete in a domain but not complete
end-to-end (tx to rx), this can lead to DOC actions failing or DOC getting stuck
trying to reoptimize. The work-around is to completely delete or add the
provisioned channel and manually abort the action.

DOC event logs during SRA Power Audit (Calibration)

As described in “Power Audit (Calibration) of SRA circuit pack as part of SRA
turn-up” on page 2-79, if SRA circuit packs are deployed, then a Raman power
audit (calibration) process is run within a DOC domain in any section (SOC)
containing an SRA.
A set of event logs and alarms at the DOC facility level, and at the SRA
RAMAN facility level relate to the power audit (calibration) process.
The following DOC facility event logs are generated during the power audit of
SRA circuit packs within a section. Their timestamps can be observed in the
Site Manager Historical Fault Browser application:
• DOC Power Audit Started
• DOC Power Audit Complete – Pass
• DOC Power Audit Complete – Fail
If a power audit cannot be run due to invalid initial state, the power audit
request is failed. As a consequence, a “DOC Power Audit Failed” alarm is
raised and a customer visible DOC log is generated to troubleshoot the
problem. The following actions can block the power audit:
• Unable to collect topology
• RAMAN or AMP facility primary state is not IS
• OTDR Trace failed on an OTDRCFG facility, and the RAMAN facility is not
ready for calibration
• There is optical line failure in the section
• Cannot close WSS/RLA pixel or set XLA/LIM to ASE mode properly
• RAMAN or AMP facility in shutoff or APR
• SRA circuit pack report calibration failed
• SRA circuit pack time-out or communication failure on calibration
• Fiber type not provisioned on a ADJ-LINE facility in the SRA circuit pack.
May require to provision the OTDRCFG fiber type if meets the
requirements.
From an SRA RAMAN facility perspective:

• The Calibration Flag is set to “NotCalibrated” by default.
• Software raises the SRA RAMAN facility ‘Calibration Required’ alarm on
restarts if the Calibration Flag is “NotCalibrated” (not raised in Manual or
MaxGain modes).

• Upon a successful power audit, DOC sets the calibration flag to

“Calibrated” or “Calibration Not Required”. Software clears the alarm on
Calibration flag change.
Middle Optical Controller (MOC) description

Prior to Rel. 12.0, this controller was referred to as the Channel Control facility
or CHC. Upon creating a 50 GHz WSS/RLA or SMD circuit pack, CHC
facilities would be auto-created, 88 or 96 of them, each corresponding to a
channel on the fixed 88- or 96-channel 50 GHz wavelength grid. As of
Rel. 12.0, some of the CHC functions are deferred to the NMC controller
(NMCC), which is a child facility of the CHC facility.
NMCC facility
In summary:
• In a fixed grid system, there is one NMCC facility for each CHC facility.
• The “new” CHC facility retains the Primary State, Opacity and Switch
Selector from the “old” CHC facility. It also features additional
frequency-related fields dedicated to channel width definition.
• The NMCC facility inherits the power/loss control functions from the “old”
CHC facility. As a consequence, the Channel degrade alarm is raised
against the NMCC facility rather than the CHC facility.
• New NMCC and CHC facilities are created together upon photonic
connections creation (e.g. as part of a channel add), and their numbering
scheme follows an index-based system rather than a system based on the
previous, pre-determined fixed 50 GHz wavelength plan. For example if 3
channels are present on a 9x1 WSS, then only 3 pairs of CHC/NMCC
facilities will be present, new ones being added as channels are added,
with ID numbers starting at 1 and incrementing along.
— The CHC and NMCC AIDs are, respectively:
– CHC-<shelf>-<WSS slot>-<port>-<CHC index>
– NMCC-<shelf>-<WSS slot>-<port>-<CHC index>-<NMC index>
— In-Service CHCs (that is, those that have their Opaque parameter set
to False) are maintained over the upgrade and associated NMCCs are
auto-created (1 per CHC). CHCs with Opaque = True that have an
existing photonic connection (CRS) are recreated. All other CHCs
(that is, those that have Opaque = True without a CRS) are deleted.
– the channel 93 CHC facility (channel used for Connection
Validation, see “Connection Validation” on page 2-86) is deleted
over the upgrade and re-created (with its child NMCC facility) when
Connection Validation resumes after the upgrade (in the demux
direction only).

These changes are made to ease the transition to Flexible grid systems where
bandwidth does not have to be divided in channels of equal width.
MOCs in add/drop branches

When a MOC is in a ROADM OTS in the mux direction, it is controlled by DOC
during link capacity changes or re-optimizations. When it is in a ROADM WSS
demux direction, or in an add/drop branch of equipment, like a DIA WSS or
SMD, it acts independently of any DOC or SOC. Generally speaking, in the
demux direction MOCs contribute (with LOCs) to maintain a power target for
the downstream receivers, while in the mux direction their purpose is to
provide a power equalized spectrum of channels to the downstream ROADM
WSS.
DIA WSS controller

In a DIA WSS, the MOC act as a power controller in the demux direction (there
is no MOC in the mux, or broadcast, direction). It runs in Power mode, and the
target power it controls to depends on the subtending equipment:
• If the subtending equipment is colored (CMD44), it aims at the Rx Nominal
power target.
• If the subtending equipment is colorless (COADM OTS), it tries to achieve
-1.0 dBm per channel at the input of the SMD/Flex SMD in a fixed grid
system, or -5.6 dBm/12.5 GHz in a flexible grid system.
— The DIA WSS controller always runs in 12.5 GHz Resolution
Bandwidth if the WSS equipment is flex capable, regardless of the
domain control modes on the line (i.e., fixed grid or flex grid).
• Gain settings for the DIA OTS amplifier in both directions are not DOC
controlled. They are set and forget provisioned as per OnePlanner report.
Any change on these gain settings are taken into account on the next DOC
action (i.e. capacity change or re-optimization) by the backbone WSS in
the Mux direction and by the DIA OTS WSS and SMD/FlexSMD Controller
in the Demux direction.
SMD controller
Similar to the DIA WSS MOC, the SMD has its own controller which runs
independently of any upstream DOC. Running in Power mode in both mux and
demux directions, the SMD/FlexSMD controller:
• attempts, in the demux direction, to achieve nominal Rx power target for
each channel dropped on a CCMD12.
• attempts, in the mux direction, to achieve a per channel power level of
-14 dBm at the SMD common output, prior to the “downstream” LIM. Such
a fixed target ensures having less than +6 dBm at the LIM EDFA in order
to have optimal noise performance.

• Any attempted manual change of the NMCC target loss on the

SMD/FlexSMD while the NMCC facility is in-service is ignored. A manual
change of the NMCC target loss is properly reflected only when NMCC is
manually put out-of-service (“OOS-MA”).
• Gain settings for the COADM OTS amplifier in both directions are not DOC
controlled. They are set and forget provisioned as per OnePlanner report.
Any change on these gain settings are taken into account on the next DOC
action (i.e. capacity change or re-optimization) by the backbone WSS in
the Mux direction and by the ROADM OTS WSS and SMD/FlexSMD
Controller in the Demux direction.
20x1 WSS demux controller

On the 20x1 WSS, in the demux direction, the controllers for dropped
channels operate in Power mode and attempt to achieve nominal Rx power
target for each channel. For passthrough channels, the demux controllers
operate in Open Loop Loss mode, leaving the WSS on the mux side perform
the control function.
MOCs mode of operation on Flex WSS/SMD variants

Upon upgrading to Rel. 12.1 or higher, MOCs are converted to flexible control
mode if the WSS/SMD is flex capable. Also, CHC (or NMCC if upgrading from
Rel. 12.0) facilities at the WSS or SMD Common Out port (mux path) and
Common In port (demux path) which are in Loss mode are changed to Power
mode or Open Loop Loss mode:
• Facilities at the Common Out port (mux path) of a WSS in a colorless DIA,
colored DIA or colorless DIA direct attach configuration are changed to
Power mode.
• Facilities in other directions/configurations are changed to Open Loop
Loss mode.
Local Optical Controller (LOC) description

Further details about VOA and CMD LOCs are given in the sections below.
Variable optical attenuators (VOAs)

SCMD4
In a SCMD4, the VOA LOCs, located at the ingress mux and egress demux
path group port, are used to set a specific attenuation target for channels
passing through them (see Figure 2-3 on page 2-8).
MLA2v
For Line Amplifier and ROADM configurations supporting the MLA2v circuit
pack, the embedded VOA within the MLA2v circuit pack is used to control the
total span loss or the loss in the mid-stage between amplifiers (for example,
between two MLA2v circuit packs at a line amplifier node or between an
MLA2v and the interior SLA), or to ensure that the downstream amplifier does
not operate at minimum gain.

Note that in a 6500 Photonic-CPL interworking scenario, the MLA2v circuit

pack can be managed by a CPL SOC. This includes the automatic setting of
the VOA.
For further information refer to “DOC control of NTK553FB MLA2v VOA Target
Loss” on page 2-11.
NTK722AA RLA
The embedded VOA within the RLA is used to ensure that the downstream
RLA amplifier does not operate at minimum gain. For further information refer
to “DOC control of NTK722AA RLA VOA Target Loss” on page 2-18.
CMD Local Optical Control

Local controllers exist for both colored and colorless CMDs:
• For colored CMDs (all variants of CMD44 100 GHz, all variants of CMD44
50 GHz, CMD96, CMD64), there is an LOC facility in the Tx direction
(Type = ‘TXMUX’):
— The AID format is LOC-<shelf>-<slot>-1
— This facility is created for all configurations involving colored CMDs
(except TOADM), but is only active in the cases listed in the next
section below.
• For colorless CMDs (CCMD12, CCMD8x16), there are 2 LOC facilities, in
both Tx and Rx directions:
— In the Tx direction (Type = ‘TXMUX’), the AID format is
LOC-<shelf>-<slot>-1.
— In the Rx direction (Type = ‘RXDEMUX’), the AID format is
LOC-<shelf>-<slot>-2.
— These facilities are created for all configurations involving colorless
CMDs (except TOADM).
— In a CCMD8x16, there are 4 Mux EDFAs and 4 Demux EDFAs, but still
there is a single Tx LOC facility and a single Rx LOC facility controlling
them all, plus all channel in/out ports. This also applies when the CXM
is equipped.
TXMUX controller function in colored CMDs

With colored CMDs, the purpose of the LOC is to ensure the per Tx power
coming out of the CMD does not saturate the connecting amplifier and violates
laser safety requirements, especially in configurations where this amplifier is
connected to a FIM, such as:
• CMD44 + BMD2 + Mux EDFA + (FIM1 or FIM4) + WSS 20x1
• (CMD44 or CMD96 or CMD64) + Mux EDFA + (FIM1 or FIM4) + WSS
20x1

• (CMD44 or CMD96 or CMD64) + Mux EDFA + WSS 9x1
TXMUX controller function in colorless CMDs

With colorless CMDs, the purpose of the LOC in the Tx direction is also to
control Tx power values to maintain laser safety requirements, but in addition
to that it provides noise funnel optimized output over the colorless mux
structure.
Noise funneling arises when many transponders equipped with an EDFA at

their output are connected to a colorless CMD, whose Tx input ports are
broadband. Due to path loss variations from the transponder Tx port to the
CCMD output port, broadband noise from one transponder impacts the OSNR
of the other transponders connected to the same CCMD. The path loss
variation can come from patch cord loss variation used between the
transponder Tx port and the CCMD Channel In port, as well as from insertion
loss variation over the CCMD add ports. See figure below.
Figure 2-10
Noise funneling at CCMD12
The CCMD TXMUX Controller is designed to derive the appropriate

transponder target Tx power (displayed as “Target Input Power at CMD” in the
Site Manager CCMD ADJ-TX facility screen) by taking path loss variations into
account so that the impact of noise funneling can be minimized and Tx OSNR
can be maximized.

The derivation is based on the power spectral density (PSD) at the output of
the CCMD, represented by the LOC facility “Auto Maximum Control Power
Output” parameter. The “Auto Maximum Control Power Output” value is
computed by the software.
SPLI is then responsible to set the transponder Tx power based on the derived
“Target Input Power at CMD” value. The transponder Tx power is displayed as
“Actual Tx Power” in the Site Manager ADJ-Tx facility screen. As of Rel. 11.1,
the CMD ADJ-TX “Maximum/typical Launch Power” parameter is renamed
“Actual Tx Power”. The CMD ADJ-TX “Target Input Power at CMD” parameter
only applies to CCMD12 and CCMD8x16. For other CMD variants, this
parameter displays “N/A”.
In order to properly estimate the signal power, information about the

transponder signal bandwidth and shape is required. The LOC facility
‘Reference Signal Bandwidth 3dB (GHz)’ and ‘Reference Signal Bandwidth
10dB (GHz)’ parameters provide this information, which is derived from the
provisioned ‘Reference Tx/Rx Type’.
• By default, at CMD creation, the LOC facility ‘Reference TxRx Type’ uses
Tx/Rx Photonic Profile instance 14, which has the label ‘35GBaud’. All
parameters of this profile are copied to the LOC. The ones shown in Site
Manager when selecting the LOC facility are:
— Reference Signal Bandwidth 3dB (GHz)
— Reference Signal Bandwidth 10dB (GHz)
— Reference Signal Power (dBm)
• The ‘Reference Tx/Rx Type’ can be changed to any of the provisioned
Photonic Profiles, in which transponder Tx and Rx information is stored
(see “Site Manager Photonic Profiles application” on page 1-47). All
parameters of the selected profile are then copied to the LOC.
• The ‘Reference Signal Bandwidth 3dB (GHz)’, ‘Reference Signal
Bandwidth 10 dB (GHz)’, and ‘Reference Signal Power (dBm)’ of the LOC
facility can be edited individually at any time.
— The parameter values cannot be changed to N/A and never display
N/A.
— When the above LOC parameter values are changed, the Tx controller
uses the modified value to calculate the Auto MCPO.
Operational consideration for both the CCMD12 and CCMD8x16 circuit packs
The following considerations apply for CCMD12 and CCM8x16:
• Manual edits of the Tx adjacency ‘Actual Tx Power’ while the LOC is
In-Service are overwritten by LOC. The TXMUX LOC facility has to be put
OOS-MA for any manual adjustments.

• Manual modifications in Mux EDFA or Demux EDFA gain in the CCMD

modules are not supported.
CCMD12 TXMUX controller and TT-OPS

In the Transceiver-Triggered OPS (TT-OPS) configuration, a single transmitter
connects to 2 different CCMD12s via the OPS. The presence of the OPS is
accounted for in the target Tx power calculation: two values are computed
(one for each CCMD12) and the one yielding the lower Tx power is retained
and set by SPLI. In releases prior to 12.1, DOC would perform its power check
at the CCMD12 input using the “Target input power at CMD” value, but, as
DOC was not aware that the transponder Tx could actually be set lower than
it expected (as instructed by SPLI), this could lead to a failed channel add if
its OPS SW Out to CCMD12 Channel In connection was too lossy. As of
Rel. 12.1, SPLI sends the “Discovered Tx Provisioned Power” value from the
transponder line facility to the CMD ADJ-Tx facility so that DOC uses this
value to perform its channel add power check, avoiding the potential issue
described above.
For additional details on TT-OPS, refer to CTP 323-1851-315 Configuration -

RXDEMUX controller function in colorless CMDs

In the Rx direction, the CCMD LOC controller serves two purposes:
• control the Rx power to achieve the Rx nominal power target, while at the
same time ensuring power levels do not saturate the CCMD drop direction
EDFA
• maximize Rx OSNR by taking into account the following:
— transponder nominal Rx level
— transponder Tx SNR bias
— insertion loss from the CCMD drop direction EDFA to transponder Rx
interface (e.g., provisioned excess loss and Sysconfig loss for OPS)
Similar to the way the Auto MCPO parameter is used to automatically

calculate a Tx power target at the output of CCMD in terms of Power Spectral
Density (PSD), the same approach is taken in the demux direction. The Auto
MCPO parameter value is calculated after the CCMD drop EDFA.
CCMD12 embedded EDFAs

The CCMD12 has an embedded EDFA in the add/drop direction. They are not
controlled by the SMD Controller or DOC:
• The gain defaults to 20 dB.
• The gain value is user-provisionable in the range of 17 dB to 23 dB.
However, 20 dB is preferred due to amplifier design flat gain (DFG).

Other optical control mechanisms

Several other automated control mechanisms operate on the 6500 and are
briefly described in this section. They are categorized as follows:
• Transponder Power Spectral Density
• Safety-related: the 6500 Photonic layer includes two main optical power
safety mechanisms that can be invoked depending on the system
operating conditions and the nature of the fault:
— automatic power reduction (APR)
— automatic line shutoff (ALSO)
In addition, implications of other hardware in the above mechanisms are
discussed:
— Tx ALS (LOFEF) for client side DWDM interfaces connected to a
DWDM photonic layer
— Raman (SRA) Safety
• Transient suppression and detection
Transponder Power Spectral Density

As a result of the introduction of coherent transponders, which can have a
wider spectral shape, the Photonic network needs to better understand the
signal’s spectral shape in order to estimate its power level.
The following CMD ADJ-Tx parameters help define a transponder’s power

spectral density:
• TX Minimum Spectral Width (GHz)
— Represents the minimum signal bandwidth that would include the
majority of the signal power + budget for laser aging/drift + laser
control loop tolerance. This parameter is required for future upgrades
to Flex Grid.
• TX Signal Bandwidth 3dB (GHz)
— Represents the 3 dB signal bandwidth, where the measured power
(RBW<4GHz) is expected to be 3 dB lower than the peak center
frequency power.
• TX Signal Bandwidth 10dB (GHz)
— Represents the 10 dB signal bandwidth, where the measured power
(RBW<4GHz) is expected to be 10 dB lower than the peak center
frequency power.
Parameter defaults for these parameters are system-set depending on the

CMD ADJ-TX facility Transmitter Type and do not need to be modified for
Ciena transponders or Foreign transponders. The default values may require
changing for Foreign Coherent transponders.

See figure below and follow these steps to obtain the TX Signal Bandwidth
values for foreign coherent transponders:
• Connect the transponder Tx port into a calibrated optical spectrum
analyzer (OSA)
• Set the Horizontal units of the OSA to be in frequency (e.g., GHz or THz)
and vertical units on a dB logarithmic scale (e.g. dBm)
• Set the OSA resolution bandwidth (RBW) as close to 1 GHz as possible
(RBW must be < 4 GHz)
• Find the peak signal value (in dBm) and then measure the outer signal
bandwidth in GHz which is 3dB below (TX Signal Bandwidth 3dB) and
10dB below (TX Signal Bandwidth 10dB) that value
Figure 2-11
Obtaining TX Signal Bandwidth for foreign coherent transponders
Automatic power reduction (APR)

Overview
Automatic power reduction (APR) is implemented on all EDFA-based and
Raman amplifiers at all points where there is a regulatory requirement for
exposure protection. This also applies to the embedded post-amplifier within
the RLA module.
APR is a software controlled ramp-down and recovery mechanism used to

limit potential exposure to instances of high optical power with a view to
protecting personnel and preventing equipment damage on detection of
breaks or disconnects in the optical line. A regulatory deemed safe level of
optical power is transmitted in the period of optical discontinuity on the line to
facilitate automatic detection of line restoration and recovery to normal state.

For EDFAs, APR kicks in when the measured Optical Return Loss (ORL)
drops below 17 dB. This threshold is not user-provisionable. When APR is
triggered, the amplifier output power drops to +3 dBm, or stays at its current
output power level, whichever level is lower.
APR disabled on Mux AMP

For the SLA/MLA Mux AMP feature (see “SLA/MLA Mux Amp” on page
3-124), the Mux Amp could see an artificially reduced ORL due to the WSS
sending light towards the Mux Amp output.
This could trigger Automatic Power Reduction (APR) on the Mux Amp, thus
reducing the power of in-service channels. Therefore, on the Mux Amp, APR
is disabled. The Mux Amp is consequently categorized as a Hazard Level 1M
device.
The Gain Clamp mode safety mechanism support is extended to the MLA and
SLA. Gain Clamp is used to limit the amp output power in fiber pinch release
scenarios. For information on the EDFA gain clamp mode, refer to “EDFA Gain
Clamp mode” on page 2-84.
Automatic Line Shutoff (ALSO)

Overview
Automatic line shutoff (ALSO) is a safety shutdown mechanism for optically
amplified dense wavelength division multiplexing (DWDM) based fiber optic
communications systems. Any amplifiers that have power levels at or above
eye safe levels are turned down or turned off when a fiber break or
intermediate connector disconnect occurs between two neighboring nodes
where optical power is being fed into both ends of the optical fiber and
generating a hazard on both ends of a fiber break.
ALSO triggers
ALSO is a system-level feature that involves detection of a break or disconnect
at the downstream amplifier and feedback to the upstream node to facilitate
shutdown of the upstream amplifier that is powering into the detected fault.
ALSO declaration is based on 3 criteria that must be flagged by software:
• Shutoff Threshold Crossed (STC): For traffic carrying wavelengths. The
total power of the DWDM channels goes below the STC threshold on the
Line A EDFA Port 8 Input or on the RLA Line A EDFA Port 8 Input.
• Loss of Light (LOL:) In the event 1511 nm or 1517 nm OSC power is no
longer detected at LIM OPTMON port 4 or at RLA OPTMON port 3. In the
case of the Raman also the TG LOL.
• OSC (OC3/STM1) Loss of Frame (LOF): This is a check of the OSC signal
at the Layer 1 level.

When all 3 conditions are active, ALSO is triggered and the “Optical Line Fail”
alarm is raised (note that the OSC LOL and LOF conditions are not alarmed).
The rationale for all three is to not drop traffic due to OSC faults or OSC
pluggable replacements (also, some systems operate without OSC, see
below). Figure 2-12 shows the alarming behavior for unidirectional and
bidirectional fiber cut cases. Refer to Amplifier shutoff states below for details
on possible amplifier states.
The NTK552JA Single Raman Line Amplifier (SRA) circuit pack uses OSC
and TG channels, as described in “Raman safety mechanisms (Pump shutoff,
ALSO, APR)” on page 2-81.
Recovery from ALSO

ALSO recovery (i.e., amplifiers turn back on) requires any of the three
conditions to recover. Under normal circumstances, it is the OSC power or
frame that recovers the amplifier, but to cover systems without OSC, clearing
the STC condition (recovery of C-Band power) also does it.
Amplifier shutoff states

The following details the various amplifier shutoff states:
• Shutoff Threshold Crossed (STC): the pumps turn off due to loss of
C-band power, as measured by the input photo detectors (note that this
can happen for reasons other than fiber disconnects). The amplifier turns
back on when C-band power is detected.
• Optical Line Fail (OLF): in addition to loss of C-band power, the OSC
power and frame are lost. This identifies a fiber disconnect. The amplifier
turns back on when C-band power is detected or OSC power or frame is
detected.
• Out of Service – Manual (OOS-MA): the amplifier has been forced into
shutoff by the user, thus explicitly enabling this state. It is used for
maintenance activities (OOS-MA is not specific to amplifiers, used on
other facilities as well). The amplifier does not raise any alarms in this
state, and it does not turn back on if input power returns, remaining
effectively opaque in this state. Note that input power PMs continue to be
reported – i.e. you can check the input to see if there is power before
re-enabling the amplifier.
• Automatic Shutoff (AS): the shelf processor forces the amplifier into
shutoff. This is used to cut off / block optical power upstream of a fiber cut.
The amplifier does not turn back on if input power returns, remaining
effectively opaque in this state.

ALSO when OSC is absent

When OSC is not provisioned, ALSO is driven only by the STC condition and
depending on the span loss the following manual recovery procedure may be
required to recover the link once the fault has been repaired:
• “ALSO Disabled” parameter has to be set to True on the LIM (EDFA) AMP
facility or LIM OPTMON facility of the line-facing circuit pack. The above
covers each scenario whether the span is bookended by LIM AMP and/or
LIM OPTMON facilities.
• Once the link has been restored, set the “ALSO Disabled” parameter back
to False.

Figure 2-12
ALSO alarming behavior
Alternative ALSO operation

As of Rel. 12.1, another ALSO operating mode is available. This mode is
introduced to avoid the following situation: if the amplifier immediately
downstream of the fiber cut is not put OOS-MA (as instructed in the fiber cut
recovery procedure), and is “woken up” by injecting a signal at its input, for
example a mis-connected external OTDR instrument, this amp can produce
high power spikes affecting channels in the next downstream optical domain.

To counter this, the alarming behavior and recovery conditions are changed:
• The amplifier immediately downstream of the fiber cut is forced into an
Automatic Shutoff (AS) state, which raises the “Automatic Shutoff” alarm
(Figure 2-13). This is functionally equivalent to putting the amplifier in the
OOS-MA state.
• Recovery only occurs when the OSC frame is detected. This ensures no
light can turn the amplifier on but the OSC signal.
Users can decide to use the pre-Rel. 12.1 ALSO mode of operation or this
alternate mode via the OTS “OSC LOF Only” parameter:
• When set to ‘DISABLE’ (default after an upgrade to Rel. 12.6 or greenfield
Rel. 12.6), ALSO recovery occurs when AMP STC or OSC LOL or OSC
LOF clears.
• When set to ENABLE, ALSO recovery only occurs when OSC LOF clears.
Use the Site Manager Photonic Configuration Management application to

provision this parameter.
If you are using this mode and the link does not recover after fiber repair
because of an OSC fault (defective SFP, excessive OSC BER, OSC fiber
disconnect, etc.), you can do the following:
• To recover the link if OSC power is present but no OSC frame:
— Confirm no maintenance activities are being performed (for example,
external OTDR is not connected to the 6500 system).
— Disable the ‘OSC LOF Only’ OTS parameter, which reverts to the
pre-Rel. 12.1 method of checking for any of the three conditions.
— Once the amplifier re-enables (due to detecting OSC power as
opposed to OSC frame) the ‘OSC LOF Only’ OTS parameter can be
re-enabled.
• To recover the link if there is no OSC power, revert to the “no OSC”
procedures where you disable ALSO temporarily to recover (see ALSO
when OSC is absent above).

Figure 2-13
ALSO alarming behavior when in ‘OSC LOF only’ mode
Disabling of Tx ALS
Automatic Laser Shutdown (ALS) may be supported on certain 3rd-party line
Tx DWDM interfaces that may be connected to the 6500 Photonic layer as
foreign wavelengths. The 6500 version of ALS, known as LOFEF (Laser Off
Far-End Failure), is implemented only on client interface ports, for instance on

a 4x10G MUX OCI or 10x10G MUX OCI. However, if these client ports are
equipped with DWDM pluggable units, it is possible that they may be
connected to 6500 Photonic layer systems.
ALS/LOFEF shuts an individual Tx laser off, which removes the power

associated with one wavelength. This is typically in response to hard faults at
L0 (e.g. optical LOS) or L1 (e.g. LOF, AIS, LF).
If the Photonic layer system is amplified, the removal of one or more Tx

wavelengths using ALS/LOFEF may have an impact on the equalization/
optimization of the link. It can also cause a transient, potentially affecting other
channels.
It is important to disable this functionality for interfaces connected to the 6500

Photonic layer, whether 6500 client port DWDM pluggable units with LOFEF
provisioning, or 3rd party interfaces supporting ALS.
Control of SRA-based Raman link

For an overview of the NTK552JA, see “Single Line Raman amplifier (SRA)”
on page 3-128.
The SRA circuit pack displays the state of the Raman facility. The different
states are NORMAL, APR (Automatic Power Reduction) and SHUTOFF.
These are displayed in the Site Manager Equipment & Facility Provisioning
application under the Raman facility and the Raman State parameter.
The TELEMETRY facility (representing the Telemetry Gain channel) is used

for the initial SRA turn-up bounding a dark fiber span. The OTDRCFG facility
is used for OTDR trace execution and reporting (characterization of fiber plant
before channel addition, and after a fiber cut/repair).
Note that the SRA turn-up is done independently of DOC.
The RAMAN facility is used for provisioning of various Raman amplifier

parameters. In particular:
• It controls the Raman gain. The available Raman gain is between 0 and
24 dB, depending upon the fiber type used, span loss and gain mode of
the XLA at the post amplification of the span.
• It performs an automatic calibration procedure, also known as a power
audit, to flatten and optimize the Raman gain based on fiber
characteristics.

Calculation of Raman Gain and relationship between Raman Gain and Target
Power
Several RAMAN facility parameters relate to how Raman gain is calculated by
DOC and provide relevant information about DOC control of SRA hardware:
• Raman Pump Mode: This parameter can be set to AUTO, MANUAL or
MAXGAIN. It is by default set to AUTO unless OnePlanner requires
specific values to be provisioned for the Raman pumps, in which case
MANUAL or MAXGAIN is used.
— If MANUAL, the pump ratio parameters (Pump Ratios 1 through 4) are
set to specific percentage values.
— If MAXGAIN, all pump ratio parameters (Pump Ratios 1 through 4) are
set to their maximum.
— Note that Pump Ratios are currently only set through TL1, and only on
the condition that the Raman Gain Mode is set to ‘Provisioned’
(instead of ‘Recommended’). Furthermore, the total of the percentage
values of all four pump ratios must equal 100%.
• Recommended Gain: This is the Raman gain automatically calculated by
software based on the fiber type, span loss and XLA gain mode of the post
amplification. Values range from 0 (default) to 24 dB.
• Raman Gain Mode: This parameter value has two possible values,
‘Provisioned’ or ‘Recommended’.
— The default is ‘Recommended’, unless the Raman gain needs to be
adjusted or set manually in which case it would need to be set to
‘Provisioned’.
— When set to ‘Provisioned’, the ‘Target Gain’ parameter (default 0 dB,
range 0-24 dB) is user-set (and the provisioned fiber type has no
impact on the Raman Gain).
— The majority of SRA deployments the gain mode will be set to
‘Recommended’ (default), only in certain cases will the gain mode be
set to ‘Provisioned’ and the provisioned gain will be provided by the
link engineering. The Power Audit (calibration) of the SRA must be
done with the correct gain mode set.
• Calibration Flag: The parameter reveals the state of the Raman circuit
pack (i.e., the state of the pumps, and whether calibration (power audit) is
required).
— This parameter takes on one of the following values: Not Calibrated
(default), Calibrated, Recalibration Required, or Calibration Not
Required.
— Only software can set this parameter to ‘Calibrated’.
— If there is a fiber cut, software leaves this parameter at the same state
it was originally (Calibrated or Calibration Not Required).

— If the span loss is greater than 43 dB when the power audit is run,
software sets the parameter to ‘Calibration Not required’.
The relationship between the Raman Gain and the target power is as follows:
• The target power is the maximum power that the SRA pumps are allowed
to provide. This value is used if it is necessary to limit the maximum power
to a specific value, for example 27 dBm (500 mW) rather than the default
30 dBm (1000 mW).
• The target power is the total power that is transmitted out of the Raman
amplifier at any given time.
• The Raman gain is a calculated number to achieve an optimal gain.
— The Raman gain is based on fiber type, span loss and amplifier peak
power. This is referred to as the “recommended” Raman gain.
• The total power produced by the pumps to achieve the Raman gain should
never go beyond the Target power set in the Raman Facility.
Raman gain is calculated based on the following parameters:

• Fiber type parameter:
— The value is set using either the SRA ADJ-LINE facility fiber type or the
SRA OTDRCFG facility fiber type.
— The OTDRCFG facility also displays the Discovered Fiber Type
parameter which indicates the fiber type that was provisioned at the
upstream ADJ-LINE facility.
— The OTDRCFG facility fiber type is used when the span fiber is
different from last 20 km of fiber closest to the Raman amplifier port 8.
The fiber type provisioned has to be the “most” dominant fiber type in
the 20 km of fiber connected to the SRA. See example in table below.
— The correct fiber type is critical and can impact the turn up of a SRA
circuit pack if not provisioned correctly

— If the fiber type is incorrectly provisioned and needs to be changed,

then you need to perform a special procedure (this only applies to
spans with Raman). Contact Ciena.
Table 2-6
Example for fiber type parameter provisioning on SRAs bookending a span
Downstream Total Fiber Distance Upstream SRA Port 5

SRA Port 8 Line A In <------------------------------------------------------------> Line B Out
OTDRCFG Facility Last 20 km of Fiber Remainder of Fiber ADJ-LINE facility

Fiber Type Provisioned Fiber-Type Provisioned
<------------------------> <------------------------------>
Default (Unknown Fiber NDSF NDSF NDSF

Type)
ELEAF ELEAF NDSF
Default (Unknown Fiber ELEAF NDSF NDSF

Type) (5 km) (15 km)
ELEAF ELEAF NDSF NDSF

(15 km) (5 km)
• Span Loss
— In the ADJ-LINE facility, the “Span Loss Source” parameter indicates
which span loss is being read. On Raman spans, the source for
calculating the span loss is always Telemetry Gain since it takes into
account the Raman gain and provides the user with the actual span
loss reading. The OSC signal is affected by the Raman gain and, as a
result, the OSC reported span loss is incorrect.
• Minimum gain of the downstream amplifier
• Amplifier peak power
Raman gain is derived (if the gain is not provisioned) based on fiber type
provisioning and availability of the span loss.
Setting the Provisioned Target Gain to 0 dB

Setting the Provisioned Target Gain to 0 dB allows the SRA to act like an
ESAM, which can be useful in the following scenarios:
• when the user wants to ubiquitously deploy SRA cards on every span, and
only use its Raman pumping capabilities on spans that need it, be it now
or in the future after fiber aging requires it.
• when the span loss is lower then expected, such that Raman gain is not
needed. This allows the turn up to go through.

• in a brownfield scenario if an SRA fails without going into shut-off, and the
link needs to stay functional
— In this case, the user would provision the target gain in the Raman
facility 1 dB less than the recommended value, then re-optimize the
domain. Then keep repeating these 2 steps until the provisioned target
gain is 0 dB. During this process, the downstream XLA increases its
gain until it reaches its limit.
— Once the SRA is replaced then the reverse would be done to bring the
SRA back to the original mode.
When the Provisioned Target Gain is set to 0 dB:

• All four Raman pumps are turned off (note that in Site Manager, the
‘Raman Actual Pump Power (dBm)’ values are displayed as N/A in this
case).
• DOC is able to add/delete channels.
• The “Calibration Required” alarm is cleared, as DOC does not ask for
calibration in this case. The calibration flag remains set to ‘Not calibrated’
though. If the provisioned target gain is set to a number other than 0 dB at
a later time, then the “Calibration Required” alarm is raised.
• As of Rel. 12.6, reconnecting a span triggers OTDR traces but the Go/No-
Go criteria are no longer evaluated, since Raman pumping is not in
function. This allows the Optical Line Fail alarm to clear right away and
EDFAs to turn on without any delay, as has always been the case with the
ESAM.
Details of Raman Gain calculation

Raman gain can initially be calculated by software for cases where gain is
needed before the first channel add, for instance when installers may want to
test the Raman Pumps for continuity and functionality.
Software checks the span loss calculation and then calculates and stores the
recommended gain.
DOC recalculates the recommended gain on every power audit based on

power readings of amplifiers at both ends of the span.
During the calibration/power audit, the amplifier at the beginning of the span
is set in Power mode and DOC can at this time read the power of both EDFAs
at each end of the span and calculate the span loss. This is the first step in the
calibration procedure of the SRA circuit pack and is explained in greater detail
in the subsection that follows.

OnePlanner provides the target peak power, the target gain tilt, Top Offset and
the amplifier gain mode depending on the desired gain (High or Low) for the
XLA EDFAs.
The gain of the SRA circuit pack is automatically set by DOC to optimize
performance of the SRA. The range of the gain value set by DOC on a per
fiber type basis is shown in table below.
Table 2-7
Raman Gain depending on fiber type
Fiber Type Minimum Gain Maximum Gain Minimum Span Loss

[dB] [dB] [dB]
NDSF 6.0 15.0 14
ELEAF 8.0 20.0 16
TW-RS 10.0 24.0 18
TWC, TW+ 10 23 18
LS 10 24 18
DSF 10 24 18
TWReach 10 24 18
LEAF 8 20 16
Teralight 8 20 16
Freelight 8 20 16
PSC 6 14 14
NDSF low 7 19 15
water peak
EX2000 6 15 14
TeraWave ULL 5 13 13
UNKNOWN 6 15 14
(same as NDSF)
Two modes of communication are supported in Raman deployments:
OSC mode
All Raman deployments are within OSC reach, with or without Raman pumps
turned on. Therefore, all OAM&P messaging (e.g. used by applications such
as Topology, DOC, alarms and so forth) use the OSC channel. The OSC
channel is either CWDM 1511 nm or DWDM 1517 nm.

Telemetry Gain (TG) mode

The Telemetry Gain (TG) channel, represented by the TELEMETRY facility, is
necessary for the SRA RAMAN pumps to turn on.
• The TG is used strictly for Raman (i.e., SRA) usage and not for any other
messaging between nodes
• The TG always stays on even if the OSC signal is being used
• The TG uses an amplitude modulated signal at the 1527.22 nm
wavelength
• This channel is also used for OTDR traces, therefore synchronization
between both ends of span is required and is managed by software
• If the upstream hardware transmits TG while the downstream hardware
runs OTDR, then OTDR fails
• The TG channel is operated in the following modes:
— Messaging mode: before Raman pumps are turned on, this TG
channel is used for synchronization between the two nodes to bring up
the Raman pumps.
— Raman gain verification mode: after the Raman pump is initially turned
on, the TG channel measures Raman gain by measuring the TG
channel power at Raman on/off. This is the only method by which the
measurement of Raman gain can occur using the TG channel.
— Monitoring mode: after Raman pumps are deployed, the TG channel
is used for monitoring (the span loss + Raman gain) in real time.
However, the TG channel cannot distinguish the loss/gain that is due
to the transmission fiber or Raman gain.
The process by which the TG communication is established between near-

and far-end SRAs at turn-up is as follows:
• When an SRA is powered up, it transmits regular TG signal with
‘Modulation Mode’ set to “On”.
— The OSC signal is also transmitted at this point.
• If the OSC signal is received, then the span is considered “short” and
software sets the modulation mode to Off on the TG.
— In general, OSC is used if the BER is better than 1E-04 (any worse,
and the risk of OSC OC3/STM1 framing issues arises).
— In the current release, the OSC is always within reach therefore the
‘Modulation Mode’ of the TG is set to Off.
• If OSC is not received or issues with the OSC signal arise, the Modulation
mode on the TG is set to “On”. (Support for this setting is planned for an
upcoming release. Please contact your Ciena account representative for
more information).

• If the TG signal is not received, then a “Telemetry LOS” alarm is raised.
TG Span Loss calculation

The TG Span Loss is calculated as follows:
• TG Span Loss = (upstream TG Tx power - local TG Rx power) + Raman
Gain
— The TG signal is 1527.22 nm (blue edge of the C-Band, just outside
the 6500 C-Band 50 GHz range
— The TG signal is narrower than the OSC signal and offers greater
precision for span loss and OTDR measurements
— The TG signal is always available (except during OTDR trace) and is
not subject to disconnects like OSC SFPs
— A display of the calculated Span Loss value is shown in the Telemetry
facility
— A “High Received Span Loss” alarm is raised based on the delta
between the target and actual readings, including provisioned span
loss margin.
Power Audit (Calibration) of SRA circuit pack as part of SRA turn-up

Prior to adding channels, if the NTK552JA Single Raman Line Amp (SRA)
circuit pack is used in a deployment, the SRAs at both ends of the span must
be turned up. The turn up procedure is described at a high level in “Single
Raman Line Amp (SRA) turn-up procedure” on page 5-30.
As part of the turn-up procedure, the SRA undergoes an automated power

audit (also known as a calibration) procedure to flatten the Raman gain profile
and optimize the Raman gain based on the fiber characteristics.
The Raman gain that can be achieved depends on the following factors:
• Line Fiber Type
• Maximum Raman Gain per fiber type
• Span Loss
• Measured Power at the Line A input of the SRA circuit pack
• XLA gain mode at the post amplification of the span
A power audit is not possible on spans that have a span loss that is greater
than ~43 dB because of the sensitivity of the OPM on the SRA circuit pack.
Therefore, the calibration flag parameter value of the RAMAN facility is set to
“Calibration Not Required”. In these situations, the Raman pumps are set
based on a lookup table embedded in the SRA circuit pack.

The power audit is an automatic procedure controlled by software and runs

from a sectional optical controller (SOC).
• The Raman power audit process is run within a DOC domain in any
section containing SRA hardware.
• When the entire domain (consisting of OTSs of the ROADM and AMP
subtypes only) has no traffic-carrying channel, and the SRA circuit pack
requires the calibration procedure (based on interpreting the status of the
RAMAN facility calibration flag parameter), the system runs a power audit
routine to optimize/flatten the gain for that SRA circuit pack. For instance,
refer to the figure below. In the illustration, only Domain A requires
calibration.
Figure 2-14
SRA Power Audit (Calibration)
The power audit is performed before the first channel add in a domain, and
can be triggered manually or automatically.
• Manual trigger:
— At initial provisioning time, using the Site Manager DOC application
and the “Power Audit” button. Once the Power Audit button is pressed,
the same procedure as per the automatic trigger is followed.
— To run the power audit, all provisioning of circuit packs must be
completed and the optical photonic domain must be valid.
— Any of the following conditions block the manually triggered power
audit command:
– If there are managed channels in the domain
Attention: The power audit is not blocked if there are inactive channels. A
domain must have an Inactive channel going through the SRA to be manually
power-audited.
– Any TOADMs or GOADMs are present in the domain. In this

release, TOADMs and GOADMs cannot be present in the same
domain with SRA/ESAM/SAM-XLA.

– DOC is OOS
– DOC status is not ready
— If there is no SRA circuit pack in the domain, the SOC simply returns
success without any further action.
— If the power audit fails, it is retried 3 times, 1 minute apart. Immediately
after any failed attempt, the “DOC Power Audit Failed” alarm is raised.
• Automatic trigger:
— DOC verifies all SRA circuit packs
— If the state of the RAMAN facility calibration flag parameter is ‘Not
Calibrated’, ‘Recalibration required’ or ‘Calibration not required’, then
prior to the first dark channel add in a domain, the power audit is
initiated automatically.
Whether manually or automatically triggered, as part of the DOC fault

detection routine, software determines whether a power audit can proceed.
• The steps performed by software during the power audit are described in
“SRA Power Audit steps” on page 5-32. This is part of the SRA turn-up
which involves inter-site communication using the TG channel, and hence
fits procedurally within the network SLAT.
• Reasons which would prevent a power audit from being run are described
later in this chapter in “DOC event logs during SRA Power Audit
(Calibration)” on page 2-56.
For engineering rules associated with the SRA power audit calibration
procedure, refer to “DOC Power Audit (Calibration) engineering rules specific
to Raman applications” on page 4-48.
Raman safety mechanisms (Pump shutoff, ALSO, APR)

Raman amplified applications use the NTK552JA Single Raman Line Amp
(SRA) circuit pack. Due to their high power, operation of Raman pumps are
adjusted in response to fault conditions that may occur.
Events that cause Raman pumps to shutoff

Various fault conditions can occur which impact operation of the Raman
pumps within the SRA:
• Events that cause Raman pumps to shut off:
— Back reflection at the pump exceeds threshold (Line A In)
— Raman Shutoff. Does not impact ALSO.
• Telemetry Gain Channel LOS and OSC LOF (Line A In) (Optical Line
Fault)
— Telemetry LOS and OSC LOF raised (ALSO)

— This also triggers the Shelf Processor to automatically shutoff the

EDFAs of the XLA
— An optical line fiber cut also triggers an OTDR trace to be run to
determine the location of the fault on the span
• High reflection on Line A In, APR feature
— This reduces or shuts down the Raman pumps. This event does not
impact ALSO.
— Raman pumps shut off - 100 ms (target)
Raman pump recovery from shutoff

The recovery of Raman pumps from their shutoff state hinges on the following
factors:
• TG channel and OSC enabled and continuity re-established
• TG LOS and OSC LOF conditions are cleared
Raman safety - response to fiber pinch scenario

A fiber pinch within the first 20 km adjacent to the Raman Line A may cause
a reduction in achieved gain. In this scenario, DOC attempts to recover
channel powers by increasing the gain of the downstream XLA. Fiber pinch
recovery is protected by the gain clamp feature on the XLA.
A severe fiber pinch may cause sufficient loss to cause an OSC LOF and TG
LOS condition, in which case ALSO is triggered and the Raman pumps shut
down as if it were a full fiber cut.
An In-Service OTDR trace can be run to locate the fiber pinch location with
Raman pumps turned on and with DOC-managed channels.
Raman safety - Response to fiber cut scenario

If a fiber cut occurs, the Automatic Line Shut Off (ALSO) feature is triggered
for safety reasons.
The following steps occur when a fiber cut is detected and are illustrated in the
figure below:
1- (1A) The fiber cut occurs. This is immediately followed by the detection of
OSC LOF and TG LOS. (1B) Then, the Raman pumps shut off on the SRA
circuit pack.
2- Raman software notifies the Shelf Processor (SP). The SP software shuts
off both EDFAs of the XLA circuit pack.
3- Raman software turns off the Telemetry Gain (TG) channel and then runs
an OTDR trace to determine the fiber cut location. Once the OTDR trace has
been completed, then TG turns back on.

Figure 2-15
SRA safety - Fiber cut and ALSO
Raman safety - Automatic Power Reduction (APR)

Due to a reflective event (e.g. a fiber pinch at a patch-panel in proximity, or an
improper mating of a fiber patchcord causing an air gap at the connector), a
high amount of reflected power is observed at the Line A In (Port 8) pump
output port of the SRA circuit pack. In this circumstance, the TG and OSC
signal may still succeed in transmitting through the reflection point.
As shown in the figure below:

1. The reflective event occurs.
2. The SRA circuit pack reduces the power of the Raman gain to the maximum
power allowed (APR output-power threshold).
In some cases, pumps may be shut off. This would have no impact on ALSO
unless shutting down the pumps cause the OSC LOF and TG signals to
disappear. In the current release, the OSC and the TG always function with or
without Raman pumps turned on.
The following thresholds are applicable:

• APR default threshold: 24 dB
• Output power level when in APR: 17 dBm (50 mW)
For APR recovery, the SRA circuit pack only turns on one Raman pump to be
able to get a valid ORL reading, so that it can then determine when to turn all
of the pumps.

Figure 2-16
SRA Safety - Reflective Event Causing APR
Transient suppression and detection

Fast automatic gain control for fiber cuts
To avoid hits on surviving channels when a large number of wavelengths are
lost suddenly due to a fiber cut, all optical amplifiers in the 6500 and CPL
portfolio are equipped with a fast Automatic Gain Controller (AGC) to filter the
transient effect. The fast AGC maintains the average gain to the same value
during the transient.
In the same manner, the impact on the surviving channels if the broken
connection is repaired (which in the worst case could yield a one wavelength
to maximum wavelength capacity sudden change), is also controlled by the
transient suppression characteristics of the optical amplifiers AGC.
EDFA Gain Clamp mode

An amplifier provisioning mode called ‘Gain Clamp’ mode prevents an
amplifier from suddenly reaching output power values that are too high. This
mechanism serves two purposes:
• Transient control: Gain Clamp eliminates the overshoot following a fiber
pinch release that would occur if the gain was unconstrained. As the
response to pinches (i.e., unexpected excess loss on a fiber) is to increase
amplifier gains to compensate, pinch release would generate an
overshoot if the amplifier maintained the higher-than-optimal gain setting.
Gain Clamp precisely counteracts this effect:
— It runs a fast control loop locally on the amplifier, such that the gain is
rapidly reduced back to the optimal, pre-pinch setting (with the output
power just below the clamp). Relying solely on DOC is not sufficient as
the next DOC auto re-optimization operation would only occur
seconds after the pinch release.
— This allows the system to compensate for arbitrarily large pinches
without worrying about an equal but opposite overshoot.

— The only limit is the available gain margin and existing LOS/Shutoff
thresholds.
— The clamp value is derived from the number of channels present and
the peak channel power target on that amplifier. The Tx bias
(Differential Provisioning) of these signals is also considered. The
actual clamp value is calculated independently for each amplifier and
therefore varies from one amplifier to another, and is re-adjusted
during intentional channel capacity changes (i.e. add or delete).
— In normal operation (non-fault scenario) 6500 amplifiers run in Gain
mode because output power is less than the provisioned clamp value.
This is required for transients.
• Laser safety: Gain Clamp ensures that the output power of any port never
exceeds the laser safety limit. One example is when an amplifier is
connected to a FIM.
Attention: Gain clamp mode can only be disabled using the TL1 ED-DOC
command and the DOCGAINCLAMP parameter. This should only be done
for troubleshooting purposes, or to force a recalculation of the clamp values
after a provisioning change (e.g., amplifier peak power target or differential
provisioning change).
Transient detection and reporting

A signature of power transients can be recorded on various 6500 circuit packs
via ‘Fast’ and/or ‘Slow’ PM tide-marking. ‘Fast’ power tide-marking has a
sampling time of ~10 µs, while this sampling time is ~ 50 ms (or 50 000 µs) for
‘Slow’ power tide-marking. The resulting high and low tide marks are fed into
the PM 15-min, 24-hr, and untimed Min/Max values. This functionality helps
operators troubleshoot power transient events in their network.
For list of 6500 circuit packs supporting tide-marking refer to Technical

Publication 323-1851-520, Fault Management - Performance Monitoring.

Connection Validation
Connection Validation has 3 major components as detailed in the table below.
Table 2-8
Connection Validation components
Connection Validation component Description Supported configurations
Cable Trace or Connection Discovery • Allows software to automatically discover how every MPO cable is • Colorless Directional
Test (system-initiated) connected, determining its point of origin and destination (CDA) configuration
• Enables automated topology verification; uncovers any cabling (CCMD12 directly attached
mistakes, providing real-time feedback to installer to a ROADM OTS)
• CDC
Fiber Loss Measurements Test • Automated process using built-in light sources in ROADM components • Colorless Directional
(system-initiated) (WSS, NTK722AA RLA, CCMD, AMP4, CXM) (CDA) configuration
• Continuously measures the loss of every sub-fiber on every MPO (CCMD12 directly attached
cable connected to the FIM for dark sub-fibers (active fibers are to a ROADM OTS)
checked regardless of this test) • CDC
• Dark sub-fibers needed for future node upgrade are tested via
loopbacks. A sub-fiber is deemed dark when no Photonic connections
(CRS) have their port trails pass through it.
• “High Fiber Loss” alarm is raised against the dark sub-fiber ADJ facility
if the loss is higher than the sub-fiber ADJ facility Fiber Loss Minor
Threshold parameter (1.5 dB default value) with a minor severity
• Fiber Loss Measurement test runs continuously as soon as Photonic
equipment is provisioned, refreshing every ~5 minutes
• Fiber Loss Measurement test can be turned off using the Site
Manager Node Information application and the “Dark Fiber Loss
Measurement” System parameter
Optical Loopback Test • Allows a SPLI-managed Ciena transponder to be self-tested after • Colorless
(user-initiated) being routed through Photonic equipment (for example, CCMD, FIM, • CDC
NTK722AA RLA) and back
• Verifies that transponder is properly connected and functional
OTDR4 to NTK722AA RLA connection • Verifies that the OTDR4 is properly connected and functional • T-Series CDC
validation
(system-initiated)
Cable Trace/Connection Discovery Test runs independently of the Fiber Loss

Measurement Test and cannot be turned off.
Connection Validation test results are available in the Site Manager

Configuration->Photonic Services->Connection Validation application and the
Validation Summary tab. Connection Validation Optical Loopback test can be
user-initiated in the same application using the Optical Loopback tab.
User-initiated tests take priority over system-initiated tests. If the user-initiated

trigger occurs while a system-initiated test is in progress, the manual request
will be queued to be executed after the current automated test finishes.
Connection Validation Cable Trace or Connection Discovery Test

A schematic illustration of low-cost light sources (TOSA’s), Smart Connect
Modules (SCM) and ROSA’s (PD Array) in a typical 6500 T-Series node is
shown in the figure below. Similar architecture is used at non T-Series CDC
nodes.

For the Colorless Directional (CDA) configuration (CCMD12 directly attached

to a ROADM OTS), Smart Connect monitoring is available for all MPO cables
between:
• WSS-WSS connections (for WSS-FIM, FIM-WSS) for both FIM Type 5 and
FIM Type6
• WSS-FIM connections for FIM Type 4
Figure 2-17
Smart Connect Module
Dedicated 1310nm sources generate a signal on a spare sub-fiber (see figure

below) within every MPO terminating at the FIM. The encoded signal uniquely
identifies the point of origin (port/slot/shelf) of each MPO.
Smart Connect Module (SCM) populated in the FIM detects the unique port
ID’s from each MPO cable. This enables system software to automatically
verify/discover node topology. It also provides real-time feedback to the
installer, pinpointing any cabling mistakes, and showing how to correct them.

SCM’s and trace signals do not compromise node performance or reliability.

Trace signals are carried on spare MPO fibers only, completely decoupled
from traffic.
All node operations are available to the user whether the SCM is present or
not.
TOSA signal from CCMD 16x12 or CCMD 8x4 is dropped at AMP4 pluggable
and re-generated going toward the FIM. TOSA in the AMP4 pluggable is
controlled by the CCMD 16x12 or CCMD 8x4.
Figure 2-18
Spare sub-fibers used for Cable Trace
An example is shown in the figure below where an installer has provisioned 8

NTK722AA RLA’s at a node as degrees 1-8 and connected them to a FIM
Type 3.
A cabling mistake has been made for RLA #8, where the 2 MPO cables
connecting ports A and B to FIM Type 3 ports 8A and 8B have been swapped
(i.e., A goes to B, B goes to A).

Within a few seconds, the system software retrieves the port ID information
from the FIM and now can trace every connection to its point of origin. The
“Adjacency Mismatch” alarms are raised against the FIM and the RLA#8
affected ADJ facilities, alerting the installer of the issue.
The Site Manager Equipment & Facility provisioning application and the FIM
and RLA#8 ADJ facility Expected Far End Address and Actual Far End
Address fields are used to indicate the mis-connection.
Once the mis-connection is corrected, the “Adjacency Mismatch” alarms

clear.
Figure 2-19
Cable Trace example
Connection Validation Fiber Loss Measurements Test

The use of MPO cables and connectors implies some challenges with regards
to connection integrity. As many connections made Day 1 are not used until a
later time, situations could arise where an MPO connection, carrying traffic on
some of its fiber strands, is found to be dirty on an unused pair of strands while
attempting to put new traffic through it. Since cleaning a single dirty fiber
strand requires the entire MPO connector to be disconnected, this would
involve taking the traffic down.
Connection Validation circumvents this by performing automated periodic

fiber loss checks at the fiber strand (or sub-fiber) level on all dark sub-fiber
connections. It uses the High Fiber Loss mechanism to perform the loss
calculations and to report connections not falling within the acceptable range,
via the “High Fiber Loss” alarm.

Activation
Connection Validation activates by itself: as equipment is added to the TID
Slot Sequence, software determines automatically which sub-fibers are dark
on this equipment, and adds them to the validation list (a sub-fiber is deemed
dark when no photonic connections (CRS) have their port trails pass through
it). Connection Validation then runs continuously through the validation list.
Active fibers are checked regardless of this Connection Validation test as

described in section “High Fiber Loss” on page 2-106.
The list, and the corresponding pass/fail results summary, can be queried
from the Site Manager Configuration -> Photonic Services->Connection
Validation application and the Validation Summary tab. The loss values are
reported in this application as well as in the ADJ-FIBER facility Fiber Loss field
of the relevant equipment transmitting ports. Note that the reported values
exclude the typical FIM and loopback connector insertion losses (which are
also reported in the ADJ-FIBER facility in the System Configuration Loss
field), so they represent the loss attributed to the sole MPO connections.
Since no power measurement is performed inside the FIM, connections

flagged as lossy require 2 patch cords to be cleaned: the WSS-FIM cable and
the FIM-CCMD cable. If the lossy connection involves a loopback connector,
then both the cable connecting the active equipment to the FIM and the
associated loopback connector require cleaning.
Once a sub-fiber is lit with traffic (CRS present), it is removed from the
validation list and Connection Validation stops running over it. The sub-fiber is
nevertheless still monitored by the High Fiber Loss alarming mechanism,
using light from traffic channels.
Connection Validation can be disabled via the Dark Fiber Loss Measurement
parameter in the Site Manager Configuration -> Node Information application
and the System tab.
The procedures related to Connection Validation can be found in Technical

Publication 323-1851-310/311 Configuration - Provisioning and Operating.
Detailed operation for T-Series CDC node

The light sources in use in the Connection Validation process are the
following:
• In the CCMD 16x12 or CCMD 8x4, a 1510 nm pilot source. If no traffic is
carried in a given direction, Connection Validation sets the Multi-cast
switch (MCS) to switch this 1510 nm pilot source to the CCMD Mux Out
Port. This power is measured at the CCMD AMP4 pluggable output,
travels through the FIM and terminates either:

— On an RLA WSS, and the power is measured at the mux WSS Switch
In port OPTMON facility to compute the loss,
or
— Back at the originating CCMD, the power being returned via an MPO
loopback connector. Power is then measured at the CCMD AMP4
pluggable input for the given direction of transmission, and the loss is
computed.
• Inside the WSS, a loopback amplifier connects the RLA mux WSS output
to the RLA demux WSS input. Connection Validation sets the loopback
amplifier to produce ASE noise. If no traffic is carried on a given demux
switch out port, Connection Validation then sets the demux WSS 1528.77
nm (channel 93) NMCC facility to point from the Loopback Out to this
switch out port. The result is a filtered ASE signal centered on 1528.77
nm, whose power is measured, and transmitted through the FIM to end its
course either:
— At a CCMD 16x12 or CCMD 8x4, where power at the input of the
demux amplifier facility facing the originating RLA WSS is measured,
and loss is computed.
— At another RLA WSS, where the power is measured at the
corresponding mux RLA WSS Switch In port OPTMON facility, and
loss is computed.
— Back at the originating RLA WSS, via an MPO or LC loopback
connector, where the power is measured at the mux WSS Switch In
port OPTMON facility, and loss is computed.
The alarming associated to Connection Validation is based on the Fiber Loss
Minor threshold, following the High Fiber Loss alarming scheme.
Connection Validation supports the following interconnections at a ROADM
node:
• RLA <---> RLA
• RLA to itself via MPO loopback connector
• RLA to itself via LC loopback connector
• RLA <---> AMP4 <---> CCMD 16x12 or CCMD 8x4
• CCMD 16x12 or CCMD 8x4 to itself via MPO loopback connector
(includes AMP4 in path)
Cadence
Connection Validation runs continuously on RLA modules, each RLA running
the loss calculations independently of the other RLAs at the node. On a given
RLA though, since there is only one loopback amplifier acting as light source,
the Switch ports are tested serially.

On CCMD 16x12 or CCMD 8x4 modules, Connection Validation is paused for

3 minutes before being repeated. Each CCMD runs the calculations
independently of the other ones. On a given CCMD, all degrees are exercised
at the same time as they all have their own amplifier.
Overall, Connection Validation can take up to 5 minutes per node to complete.
Detailed operation for S/D-Series CDC node

following:
• In the CCMD8x16 and CXM, each direction has a mux amplifier. If no
traffic is carried in a given direction, Connection Validation sets this
amplifier to produce Amplified Spontaneous Emission (ASE) noise. This
noise power is measured at the amp output, travels through the FIM and
terminates either:
— On a WSS, and the power is measured at the mux WSS Switch In port
OPTMON facility to compute the loss,
or
— Back at the originating CCMD8x16 or CXM, the ASE being returned
via an MPO loopback connector. Power is then measured at the input
of the demux amplifier facility for the given direction of transmission,
and the loss is computed.
• Inside the WSS, a loopback amplifier connects the mux WSS output to the
demux WSS input. Connection Validation sets the loopback amplifier to
produce ASE noise. If no traffic is carried on a given demux switch out
port, Connection Validation then sets the demux WSS 1528.77 nm
(channel 93) NMCC facility to point from the Loopback Out to this switch
out port. The result is a filtered ASE signal centered on 1528.77 nm,
whose power is measured, and transmitted through the FIM to end its
course either:
— At a CCMD8x16 or CXM, where power at the input of the demux
amplifier facility facing the originating WSS is measured, and loss is
computed.
— At another WSS, where the power is measured at the corresponding
mux WSS Switch In port OPTMON facility, and loss is computed.
— Back at the originating WSS, via an MPO or LC loopback connector,
where the power is measured at the mux WSS Switch In port
OPTMON facility, and loss is computed.


node:
• WSS <---> WSS
• WSS to itself via MPO loopback connector
• WSS to itself via LC loopback connector
• WSS <---> CCMD8x16
• WSS <---> CXM
• CCMD8x16 to itself via MPO loopback connector
• CXM to itself via MPO loopback connector
Attention: Connection Validation cannot test the MPO jumper cable

between the CCMD8x16 and CXM, as there is no amplifier feeding it directly
in the mux direction. The mux fiber strands can only be tested when a new,
non-traffic-carrying transmitter is connected to the CCMD8x16 and available
as a light source.
Cadence
Connection Validation runs continuously on WSS circuit packs, each WSS
running the loss calculations independently of the other WSSs at the node. On
a given WSS though, since there is only one loopback amplifier acting as light
source, the 20 Switch ports are tested serially.
On CCMD8x16 circuit packs, Connection Validation is paused for 3 minutes

before being repeated. Each CCMD8x16 runs the calculations independently
of the other ones. On a given CCMD8x16, all degrees are exercised at the
same time as they all have their own amplifier.
Detailed operation for Colorless Directional (CDA) configuration (CCMD12

directly attached to a ROADM OTS)
following:
• Inside the WSS, a loopback amplifier connects the mux WSS output to the
demux WSS input. Connection Validation sets the loopback amplifier to
produce ASE noise. If no traffic is carried on a given demux switch out
port, Connection Validation then sets the demux WSS 1528.77 nm
(channel 93) NMCC facility to point from the Loopback Out to this switch

out port. The result is a filtered ASE signal centered on 1528.77 nm,
whose power is measured, and transmitted through the FIM to end its
course either:
— At another WSS, where the power is measured at the corresponding
mux WSS Switch In port OPTMON facility, and loss is computed.
— Back at the originating WSS, via a MPO or LC loopback connector,
where the power is measured at the mux WSS Switch In port
OPTMON facility, and loss is computed.
node:
• WSS <---> WSS
• WSS to itself via MPO or LC loopback connector
Cadence
Connection Validation runs continuously on WSS circuit packs, each WSS
running the loss calculations independently of the other WSSs at the node. On
a given WSS though, since there is only one loopback amplifier acting as light
source, the 20 Switch ports are tested serially.
Connection Validation Optical Loopback Test

The Optical Loopback test is a user-initiated test that allows a Ciena
SPLI-managed transponder to be self-tested after being routed through
photonic equipment and back (T-Series example shown in Figure 2-20 on
page 2-96). It verifies that the transponder is properly connected and
functional.
The Optical Loopback test can be initiated using the Site Manager
Configuration->Photonic Services->Connection Validation application and the
Optical Loopback tab.
The loopback test creates a Photonic connection of type LPBK to setup the
path from CCMD Tx port to the 20x1 WSS (or DIA configurations using Flex
SMD or RLA for T-Series) and back to CCMD Rx port. The transponder is
tuned to a specific wavelength and used as the light source to light up the
path.
• Since the transponder must be SPLI-managed before starting the test, the
transponder is already tuned to a “resting” wavelength after the SPLI
match occurs channel 0 (0.0nm/0.0THz) for CCMD12 and channel 93
(1528.77nm/196.10THz) for CCMD8x16 and CCMD 16x12).
• For the CCMD12 case:

— Once the optical loopback test is manually started, the transponder

wavelength is tuned to channel 93 (1528.77 nm) or channel 96
(1529.94 nm) if the NTK553GA/GB SMD is in the path
— Once the optical loopback test is manually stopped, the transponder
wavelength is tuned to channel 0 (0.0nm/0.0THz).
• For the CCMD8x16 and CCMD 16x12 case:
— There is no tuning of the transponder wavelength when the optical test
is started or stopped since the transponder is already tuned to the
required channel 93 (1528.77 nm/196.10THz).
When the optical test runs, it performs High Fiber Loss detection and TTI
matching to validate the connectivity in the path.
Transponder Considerations
WLAi (NTK538DZ) which only operates at 56 GBaud only perform High Fiber
Loss detection (no TTI matching validation).
WLAi (NTK538DR/FR) and WLAi w/OPS (NTK538DS/FS):
• The Optical Loopback on the WLAi or WLAi w/OPS sets the transponder
transmission mode to 35GBAUD. When the Optical Loopback test is
completed or canceled SPLI sends a message to the transponder to
return it to its previous provisioned mode.
• For Optical Loopback when the OPS is present (either integrated or
external), a manual switch must be user-initiated prior to the test to ensure
that the receiver is using the correct path.

Figure 2-20
Optical Loopback Test using 20x1 WSS
Optical Loopback Test for foreign transponders

Optical Loopback test for foreign transponders connected to CCMD12 or
CCMD8x16 is supported when used in CDA, CDC or CD Photonic
configurations. Note that:
• The foreign transponder signal’s 3 dB bandwidth must be 37.5 GHz or less
for a valid test to be performed, otherwise it won’t pass through the
loopback path bandwidth.
• The procedure is mostly manual, including the test pass/fail declaration,
whose status can nevertheless be recorded against the ADJ-TX port with
a time stamp.
You can find the full procedure in Technical Publication 323-1851-310.2,

Configuration - Provisioning and Operating, Part 2.
Connection Validation Cable Trace/Connection Discovery Test associated

alarms
The following alarms relate to the Connection Validation Cable
Trace/Connection Discovery test:
• “Adjacency Mismatch”: raised against an MPO ADJ facility when a
non-empty provisioned (or derived) ADJ does not match the discovered
ADJ.

• “Adjacency Far End Not Discovered”: raised against an MPO ADJ facility
if there is a provisioned (or derived) ADJ and no discovered ADJ. This
alarm is not supported for ADJ facilities that have FEA pointing to
themselves (e.g., MPO loopback connector on the port).
• “Cable Trace Compromised”: raised against the FIM if there is an issue
with the SCM whereby hardware discovery is hampered. Raised against
the WSS/RLA/CCMD8x16/CCMD 16x12/AMP4 if there is an issue with
the TOSA functionality.
Connection Validation Fiber Loss Measurements associated alarms
The following alarms relate to the Connection Validation Fiber Loss
Measurements test:
• “Dark Fiber Loss Measurement Disabled”: raised if Connection Validation
is turned off using Site Manager Node Information application and the
“Dark Fiber Loss Measurement” System parameter. Only raised if
photonic equipment is equipped in the shelf.
• “High Fiber Loss”: raised against the dark sub-fiber ADJ facility if the loss
is higher than the sub-fiber ADJ facility Fiber Loss Minor Threshold
parameter (1.5 dB default value, note that the default value changed from
3.0 dB to 1.5 dB starting in Rel. 12.0). The alarm does not clear if the light
source is disconnected. The calculated loss need to be more than 0.5 dB
below the threshold to clear the alarm.
OTDR4 to NTK722AA RLA Connection Validation

The OTDR4 is put into constant Continuous Wave (CW) mode to produce light
and then Connection Validation looks for LOS clearing on the correct RLA
port.
Connection Validation (using CW mode) occurs at the start of the trace

request and is active for a short duration (a few seconds) before the OTDR
trace runs.
If the patch cord is not connected to the correct RLA port, the LOS alarm is
raised on the RLA port 13 OPTMON facility and is latched. It is re-validated on
the next trace request and the alarm is re-evaluated.
The Site Manager Connection Validation application Validation Summary tab

shows the RLA AID with the following info:
• Pass/Fail/Untested (Not Run) status
• Reason for Failure
• Not Applicable (N/A) for Fiber Loss value

Dark Section Conditioning

Dark Section
As outlined in “Optical Section” on page 1-25, an optical section is the portion
of the Photonic domain delimited by two consecutive channel access OTSs.
When an optical section has no managed channel on it, it is called a dark
section. In releases prior to Rel. 12.4, on such a dark section:
• AMP facilities are in shutoff state, with default gain values
• RAMAN facilities are not calibrated
Amplifier gain setting and SRA calibration, also known as ‘section

conditioning’, occur upon addition of the first channel through the section.
Dark Section Conditioning high-level description

As of Rel. 12.4, provided the optical section follows certain rules (see “Dark
Section Condition support” on page 2-100), section conditioning can occur
before the first channel is added. This is called Dark Section Conditioning
(DSC).
In absence of transponder light to perform amplifier gain setting and SRA

calibration, DSC uses low-level optical noise generated by the first amplifier in
the section. The light produced flows downstream to the other amplifiers in the
section, and DSC calculates and sets their gain taking into account measured
power levels and provisioned peak power targets.
Dark Section Conditioning benefits

The benefits of DSC are two-fold:
• DSC speeds up channel add operations, as it performs the same required
operations to condition a dark domain as DOC used to do when
performing the dark channel add action in releases prior to Rel. 12.4.
— This mostly benefits Layer 0 Control Plane applications, decreasing
the restoration time when restoring channels over a dark section.
• DSC allows detection of faults on an unlit line system, as it exposes
failures that would otherwise remain silent until the first channel is added.
Typical faults targeted by this feature are as follows:
— APR (Automatic Power Reduction) on the AMP facilities
— OOS-MA (Out-Of-Service – Manual) conditions on AMP and RAMAN
facilities
— STC (Shutoff Threshold Crossed) conditions on AMP facilities
— Intra-Node High Fiber Loss alarms
— Intra-Node Fiber disconnects
— OPM crossed fibers

— Note that Alarm correlation masks alarms downstream of the fault to

help isolate it
Figure 2-21 shows various conditions that can be highlighted by DSC:

• Location 1:
— AMP facility in shut-off state for line-facing amplifier or interior SLA
("Shutoff Threshold Crossed" alarm raised)
— RAMAN facility OOS for SRA, or AMP facility OOS for line-facing
amplifier or interior SLA (no alarm raised)
— APR condition on line-facing amplifier or interior SLA ("APR Active"
alarm raised)
• Location 2:
— OPM crossed fibers at ROADM or line amp ("Crossed Fibers
Suspected" alarm raised). Detection of this condition is not certain
though (see “Crossed Fibers Suspected alarm” on page 2-110).
— Fiber disconnect between AMP monitor ports and OPM ports ("Loss
of Signal" alarm raised on the OPM OPTMON facility)
— Fiber unexpected loss between AMP monitor ports and OPM ports
(Minor or Major "High Fiber Loss" alarm)
— Note that the above conditions are not applicable to S- and T-Series
RLA as these connections are internal to the circuit pack.
• Location 3:
— Intra-node fiber unexpected loss (Minor or Major "High Fiber Loss"
alarm)
— Intra-node fiber disconnect, raising either:
– A "Shutoff Threshold Crossed" alarm on the next downstream
AMP facility
– A "Loss of Signal" alarm on the next downstream OPTMON facility
— Note that the WSS-WSS checks can only be performed if the WSS has
a broadcast demux structure, allowing light to reach the downstream
WSS without opening a WSS pixel.
• Location 4: Power audit failure. Various conditions can cause the power
audit to fail ("Power Audit Failed" alarm raised).
• Location 5: Photonic card failure, including WSS, AMP, SRA/SAM/ESAM,
etc. ("Circuit Pack Failed" alarm raised)
• Location 6: Fault location beyond DSC fault detection capabilities. This is
due to the fact that this connection is located upstream of the ASE source
used to detect faults. If the installer properly follows the existing CTP nodal
SLAT procedures, this fault should be caught beforehand.

Figure 2-21
Typical faults exposed by Dark Section Conditioning
Dark Section Condition support

DSC support rules are as follows:
• Domains must be single-section ROADM domains (i.e., bookended with
6500 ROADM OTSs)
— S-Series and T-Series domains are supported
— An S-Series domain can include 6500 or CPL line amp sites. CPL line
amp cannot have DRA though.
— No TOADM allowed in the domain
— Ingress ROADM OTS in the domain has at least one EDFA as post
amplifier, meaning WSS + SLA ROADMs are not supported.
• The entire optical domain must be running Rel. 12.4 software or higher.
There is no software backwards compatibility.
• Both fixed grid and flex grid domains are supported.
• DSC works whether Control Plane is enabled or not. If enabled, both L0CP
types are supported: Mesh-Restorable (OSRP Node type of ‘PHOTONIC’)
and Non-Mesh Restorable (OSRP Node Type of ‘L0 Provisioning’).
• Submarine and Foreign Line domains are not supported.
Dark Section Conditioning activation

In greenfield deployments, DSC is enabled by default upon the creation of
ROADM OTS.
In brownfield deployments, after upgrading to R12.4, DSC is enabled

automatically provided the rules above are met, and if the following conditions
are fulfilled:
• DOC Primary state is IS
• DOC Automation mode is not “Foreign Line”, “Foreign Line Enhanced” or
“Foreign Line Speed Enhanced”

• There is no DOC-managed channel in the domain. This condition is met

whenever there is:
— No photonic connection (CRS) provisioned at all at the ingress
ROADM OTS.
— CRS (CRS-NMC or CRS-OCH) are provisioned at ingress ROADM
OTS, but with DOC CARE = FALSE and ACTIVE = FALSE.
Generally speaking, DSC runs on dark sections, and stops running upon
adding a first channel over the section. It re-runs every 30 minutes to
re-evaluate the domain condition, allowing it to react to potential changes in
the domain (span losses, fiber type, etc.).
Table 2-9 summarizes DSC entry and exit cases. Note that manually initiated
"Re-optimize" and "Reset TCA Baseline" actions on a dark section do not
interrupt DSC.
Table 2-9
Dark Section Conditioning exit and entry criteria
DSC stops running when... DSC kicks back in when...
A DOC Add action is requested in the domain A lit section becomes dark again
A user changes the DOC Primary State from IS to A user changes the DOC Primary State from OOS
OOS to IS
A Power Audit action is initiated on a dark SRA A manually requested DOC Power Audit has
link by a manual user request. completed on a dark domain
Note that mistakenly launching a manual Power
Audit on a section without SRA does not interrupt
DSC.
A “DOC Invalid Photonic Domain” alarm is raised A “DOC Invalid Photonic Domain” alarm in the
in the domain domain clears
A user enters the following TL1 command: A user enters the following TL1 command:
ED-DOC::DOC-SHELF-INSTANCE:CTAG::: ED-DOC::DOC-SHELF-INSTANCE:CTAG:::
DOCDSC=DISABLED; DOCDSC=ENABLED;
Note that there is no Site Manager support for this Note that there is no Site Manager support for this
command. command.
Dark Section Conditioning detailed operation and operational considerations

In details, a DSC run consists in the following:
• At the section head-end ROADM Mux WSS, any existing CHC facility is
set to Opaque (except the ones involved in Connection Validation).
• A clean-up routine initializes all PM baselines for AMP and OPTMON
facilities in the domain.

• Auto In-Service (AINS) is disabled on the AMP and OPTMON facilities.

• At the section head-end ROADM OTS, the Line B amplifier facility is
turned into an ASE source:
— The 'ALSO Disabled' parameter is set to TRUE. Note that this does not
affect the existing ALSO functionality, it simply allows the AMP facility
to be put into power mode (see below).
— The 'Automatic Shutoff Disabled' alarm raised as a result of the
previous step is masked. Despite this, ALSO and APR mechanisms
are preserved, and related alarms (OLF, APR Active) would raise
should the condition appear.
— AMP mode is set to 'Power', with an estimated target power
— As there is no signal at the amp input, the 'Input Loss of Signal' alarm
would raise, but it is masked.
— At the same time, the AMP target power is set, using a formula based
on its provisioned target peak power and the loss of the span the amp
sends light into. This target power basically ensures enough light
reaches the next downstream amplifier to make it come out of shutoff
state.
• Working downstream from the head-end amplifier, the rest of the amps are
successively set: the AMP mode is set to 'Gain' or 'GainClamp', with the
AMP target gain set from a formula.
• If there are uncalibrated SRAs on the link, DSC runs Power Audits on each
before resuming the EDFA setup routine described above. This is done in
the same way DOC does it when performing the dark add action in release
prior to Rel. 12.4.
• If there are drop amps or drop LIMs, their gain is set to minimum.
• If there is an MLA2v in a S-Series ingress ROADM OTS, or a T-Series
RLA, DSC performs a VOA calibration operation if the 'VOA Reset
Required' parameter is TRUE on the VOA facility and in the System
Parameters.
At the end of a successful DSC run, the link portrait is thus the following:
• Target gains set on XLA, MLAx, RLA (S/D- and T-Series)
— These EDFAs are in Gain/GainClamp mode, except the Line B facility
in the ingress ROADM OTS, which is in Power mode
• Target power set to maximum value on all clamp-capable AMP facilities in
the domain
• SRAs calibrated
— DSC leaves the SRA Raman gain at the Recommended gain setting,
and FORCESHUTOFF to FALSE

• WSS drop amps and drop LIMs set to their minimum gain, with
FORCESHUTOFF = FALSE
• VOAs calibrated on MLA2v, T-Series RLA
— Only the VOA in the ROADM OTS Line B amplifier facility is calibrated.
The Line A facility VOA in the ROADM OTS is set to its minimal value
by default at the facility creation time.
When a first channel is added over a dark section, the following happens:
• At the head-end ROADM OTS Line B amplifier facility, the Domain Optical
Controller (DOC):
— Sets 'ALSO Disabled' to 'False'
— Unmasks the "Automatic Shutoff Disabled" and "Input Loss of Signal"
alarms
— Calculates the amplifier gain
— Sets the Mode from 'Power' back to 'Gain' or 'GainClamp'
• DOC enables AINS on the facilities that were disabled at the beginning of
the DSC run.
• For the rest of the adjustable facility parameters in the link, DOC uses the
DSC-established values as initial settings.
If DSC has successfully run in a domain, DOC does not have to re-run the
routines listed above when adding the first channel in the domain (dark add
action). However, if DSC fails to run in the domain:
• DOC has to perform these routines in the same way as it does for the dark
add action in releases prior to Rel. 12.4.
• DSC periodically reattempts to run (every 5 seconds).
— If for example there was a fiber cut, after the repair DSC comes back
right after so the repair assessment can be made quickly.
— The Power audit failure case is different. In this case, DSC is
suspended while DOC continuously retries the Power audit, until it
succeeds (following user intervention on the fiber plant). When the
Power audit failure alarm clears, DSC resumes.
• Depending on the specific situation that causes DSC to fail, the OSRP line
could be blocked as a result of the failure.
Finally, note that the OTDR functionality is still available while DSC is running,
i.e. running OTDR traces does not interrupt DSC.
Photonic layer alarms

This section complements but does not substitute for instructions provided in
Technical Publication 323-1851-543, Alarm Clearing.

High Received Span Loss and Low Received Span Loss

The “High Received Span Loss” alarm is raised to indicate there is an
unexpected loss (pinch) in a Photonic span between 6500 Photonic nodes
The alarm is used in the control algorithms and is a requirement to allow for
better fiber pinch compensation (see “DOC fiber pinch detection feature” on
page 2-53).
Overview and calculation

The “High Received Span Loss” alarm helps detect and alarm excess loss in
a span between 6500 Photonic nodes.
The “Low Received Span Loss” alarm helps detect and alarm insufficient loss
in a span between 6500 Photonic nodes.
In the case where DSCM and/or pads are provisioned at the LIM, SRA or
ESAM (or SAM) Line B Output or the LIM, SRA or ESAM (or SAM) Line A
Input, since the DSCM and/or pads are included in the span, they add to the
overall span loss.
These span loss alarm features use the OSC facility span loss calculation
(when LIM, or ESAM or SAMs are used) or the TELEMETRY facility span loss
calculation when the SRA is used.
The following LIM ADJ-LINE facility parameters exist for the Span Loss alarm
feature:
• Span Loss (dB):
— For spans bookended with SRAs, this is the calculated span loss.
Same value reported by the TELEMETRY facility.
• Target Span Loss (dB): Defaults to 0. User provisionable between the
values 0 to 60.
• Span Loss Margin (dB): Defaults to 3. User provisionable between the
values 0 to 10.
• Minimum Span Loss (dB): Defaults to 0. User provisionable between the
values 0 to 60.
The span loss is evaluated every second.
The “High Received Span Loss” alarm is raised when the calculated Span
Loss exceeds the Target Span Loss + Span Loss Margin. The alarm clears
when the calculated Span Loss drops 1 dB below the Target Span Loss +
Span Loss Margin.

The “Low Received Span Loss” alarm is raised when the Span Loss is less
than the Minimum Span Loss - Span Loss Margin. The alarm clears when the
calculated Span Loss is 1 dB greater than the Minimum Span Loss - Span
Loss Margin.
Both alarms are raised against the LIM or RLA equipment (at the tail end of
the span).
Enabling the High Received Span Loss alarm

The “High Received Span Loss” alarm reporting has to be explicitly enabled
for a given span by provisioning a non-zero Target Span Loss in the LIM or
RLA ADJ-LINE facility. By default, the Target Span Loss parameter is set to 0.
Enabling the Low Received Span Loss alarm

The “Low Received Span Loss” alarm reporting has to be explicitly enabled
for a given span by provisioning a non-zero Minimum Span Loss in the LIM or
RLA ADJ-LINE facility. By default, the Minimum Span Loss parameter is set to
0.
OSC span loss readings when pads or DSCMs are in a span

When physically placing a pad at the output of the booster (Line B Out, port
5) or placing a pad or DSCM at the input to the preamp (Line A In, port 8), their
insertion loss is incorporated into the OSC span loss reading (this occurs
whether pads are provisioned using the DSCM equipment type or the excess
loss parameter). For provisioning details, refer to “Provisioning a pad at an
OSC Tx” on page 5-16.
If a pad is provisioned as:

• Excess loss on the upstream LINE (Line B port 5) ADJ-FIBER facility, it is
not subtracted from the OSC span loss calculation shown at the
downstream OSC facility.
• Excess loss on the OSC Tx port ADJ-FIBER facility, it is subtracted from
the downstream OSC facility span loss reading.
The use of a pad at the OSC Tx may be necessary to mitigate non-linearities

depending upon link budget analysis.
TELEMETRY span loss readings when pads or DSCMs are in a span bookended
by SRAs
When physically placing a pad at the output of the SRA (Line B Out, port 5),
its insertion loss is incorporated into the TELEMETRY span loss reading (this
occurs whether pads are provisioned using the DSCM equipment type or the
excess loss parameter). Note that unlike the OSC SFP Tx port, the Telemetry
signal Tx is located internally on the SRA circuit pack, and is not accessible.
Therefore, excess loss cannot be provisioned.

High Fiber Loss

Overview and calculation
The “High Fiber Loss” alarm is raised to indicate there is an unexpected loss
(pinch) in a fiber that interconnects Photonic equipment within a node.
The alarm is used in the control algorithms and is a requirement to allow for
better fiber pinch compensation (see “DOC fiber pinch detection feature” on
page 2-53).
This feature calculates the fiber loss between Photonic equipment at a node
and takes into account any excess loss (like pads) provisioned at the
originating ADJ-FIBER facility as well as any provisioned DSCM/pads. Note
that:
• DSCM/pads are only accounted for at a Line Amp node if provisioned on
Line A Out, not if provisioned on Line A In, Line B In, or Line B Out.
• The DSCM loss used by this feature is derived from the DISP facility
provisioning, INPUTLOSS + OUTPUTLOSS + (AVGLOSS * LENGTH).
The fiber loss is evaluated every second.
The alarm is raised with either a Minor or a Major alarm severity:

• Minor alarm severity if the calculated fiber loss exceeds the
user-provisioned ADJ-FIBER facility Fiber Loss Minor Threshold.
— The possible values for the Fiber Loss Minor Threshold range from
1 to 30 dB with a 0.01 resolution, the default being 1.5 dB.
— The default value changed from 3.0 dB to 1.5 dB starting in Rel. 12.0.
The old default value is preserved over a software upgrade to Rel. 12.0
or higher though: to change the High Fiber Loss Minor threshold for
existing ADJ-FIBER facilities, use the Site Manager
Configuration->Shelf Level View->Facility Browser application. This
application allows you to view the ADJ-FIBER facilities on all shelves
in a TIDC node and to edit the Minor and Major High Fiber Loss
threshold values on all or selected ADJ-FIBER facilities in the list.
Refer to CTP 323-1851-301, Administration and Security for the
procedure to enable and use the Facility Browser application.
• Major alarm severity if the calculated fiber loss exceeds the
user-provisioned ADJ-FIBER facility Fiber Loss Major Threshold.
— The possible values for the Fiber Loss Major Threshold range from
1 to 30 dB with a 0.01 resolution, the default value being 10 dB. The
Major threshold must be at least equal to or greater than the Minor
threshold.

The Site Manager Node Information application and the System tab includes
the High Fiber Loss Minor Threshold (default=1.5 dB) and High Fiber Loss
Major Threshold (default=10.0 dB) parameters which set the ADJ-FIBER
facility thresholds on a nodal basis for any new deployed equipment.
The alarm is cleared when the calculated fiber loss is less than 0.5 dB
compared to the provisioned threshold value. The alarm is raised against the
originating ADJ-FIBER facility and the calculated fiber loss is reported against
the ADJ-FIBER facility.
Attention: When using the High Fiber Loss feature on a connection with a
DSCM, note that the default loss populated in the DSCM equipment is an
average and the actual loss may differ by several dBs. The default loss
should be adjusted to match the actual loss by applying an adjustment equal
to the excess measured loss, at which point the High Fiber Loss alarm will
clear.
Enabling the High Fiber Loss alarm

High Fiber Loss alarming is enabled by setting the “High Fiber Loss Alarm
Detection Alarm” parameter in the Site Manager Node Information application
and the System tab to Enabled (default setting).
You can disable the “High Fiber Loss” alarm on a per-port basis by setting the
appropriate Major or Minor alarm threshold to 0 for that port.
Fiber Loss Detection Disabled alarm

The High Fiber Loss Detection Alarm parameter in the Site Manager Node
Information application (System tab) must be set to Enabled for a shelf
containing a COADM OTS, CD, CDA or CDC equipment. Otherwise, the
“Fiber Loss Detection Disabled” alarm is raised.
• The SMD power controller uses High Fiber Loss Detection for control
purposes.
• If the High Fiber Loss Detection Alarm parameter is disabled, software
doesn’t perform the High Fiber Loss Detection checks and therefore if
there is a pinch, the SMD compensates endlessly and creates an
overshoot when the pinch is released.
Connection Validation Fiber Loss Measurements Test

For details refer to “Connection Validation Fiber Loss Measurements Test” on
page 2-89.

Channel power PMs and alarms for Colorless transponders

Colorless-capable transponders described in “Supported transponders for
colorless and CDC line systems” on page 3-107 have two optical power
detectors on their Rx interface:
• One for channel input power (the channel corresponds to the wavelength
the transmitter is tuned to)
• One for total input power (channel power + amplifier noise). The total input
power corresponds to the sum total of all the wavelengths dropping on the
Colorless Channel Mux/Demux (CCMD) and amplifier noise (ASE).
This reflects on the Site Manager reported parameters and alarms in the
manner described below.
Channel input power

In the Equipment & Facility Provisioning application, the total input power is
reported against the interface facility via the parameter labeled Rx Channel
Actual Power. Correspondingly, the Ranges button displays two parameters -
Rx Channel minimum power and Rx Channel maximum power.
The Performance Monitoring application displays the corresponding facility

PM parameters:
• OPR-OCH
• OPRN-OCH (Normalized Rx optical power)
The following alarms relate to channel input power:

• “Rx Channel Power Out of Range”: raised when the Rx channel power is
outside the Rx channel power thresholds defined in the Site Manager
Equipment & Facility Provisioning application and the facility Ranges
button.
• “Loss Of Channel”: raised when the optical power is below the Loss of
channel threshold.
Total input power

In the Equipment & Facility Provisioning application, the total input power is
reported against the interface facility via the parameter labeled Rx Actual
Power.
The Performance Monitoring application displays the corresponding facility

PM parameters:
• OPR-OTS
• OPRN-OTS (Normalized Rx optical power)

The following alarms relate to total input power:

• “Rx Power Out Of Range”: raised when the total Rx power is outside the
thresholds defined in the Site Manager Equipment & Facility Provisioning
application and the facility Ranges button.
• “Loss Of Signal”: raised when the optical power is below the Loss of signal
threshold and frame loss occurs. Note that the “Loss Of Signal” masks the
“Loss of Channel” alarm.
Channel Degrade alarm for WSS/RLA NMCC facilities
As described in “WSS/RLA Reference Input Power Profile” on page 2-55, the
“Reference Input Power Profile” parameter is defined on a per-NMCC facility
basis.
The parameter is used to raise a Channel Degrade alarm against a WSS/RLA

NMCC facility in the following manner:
• If the Derived Input Power is less than the (Reference Input Power Profile
value - the Minor Degrade Threshold value) then the “Channel Degrade”
minor, NSA alarm is raised.
— This triggers freezing of the WSS/RLA pixels for the affected channels.
— Note that the Channel Fault Status in the DOC application displays
“Degrade, minor” when the degrade condition exists.
— The Minor Degrade Threshold defaults to 3 dB and can be
user-provisioned between 0 to 30 dB using the Site Manager Node
Information application and the Systems tab.
value - the Major Degrade Threshold value) then the “Channel Degrade”
minor, NSA alarm (this is not a typo) is raised.
— This triggers freezing of the WSS/RLA pixels for the affected channels.
— The Channel Fault Status in the DOC application displays “Degrade,
major” when the degrade condition exists.
— The Major Degrade Threshold defaults to 6 dB and can be
Information application and the Systems tab.
Attention: It is strongly recommended that the Minor Degrade and Major

Degrade Thresholds remain at their default values.
The “Alarm Additional info” field shows the affected NMCC wavelength if the
channel is on 50 GHz ITU Reference Bandwidth, otherwise it shows its center
frequency.

Crossed Fibers Suspected alarm

Crossed Fibers Suspected alarm at ROADM node
The alarm is raised at a ROADM node when software “suspects” that the
fibers are crossed between the 2 WSS OPM ports and their associated LIM
monitor ports, whether the WSS is used in the backbone OTS or the DIA
OADM OTS.
The alarm, which is enabled by default, is only detectable when there is a delta
between the measured power level and the expected power level at the OPM
ports. One port will have higher than expected power, the other port will have
lower than expected power.
• The port with higher than expected power raises the “Crossed Fibers
Suspected” alarm if the delta is greater than 3 dB.
• The port with lower than expected power would normally raise the “High
Fiber Loss” alarm (provided the High Fiber Loss Detection parameter is
set to enabled). However, if the “Crossed Fibers Suspected” alarm is
raised, the “High Fiber Loss” alarm is suppressed.
Figure 2-22 on page 2-111 illustrates an example.
The “Cross Fibers Suspected” alarm is not applicable to ROADM nodes using
RLAs since the LIM to OPM interconnections are embedded within the RLA
module.
Crossed Fiber Suspected alarm at Line Amp node

The alarm is also supported at Line Amp nodes equipped with OPMs. The
alarm is only detectable when there is a delta between the measured power
level and the expected power level at the OPM ports.
• One port will have higher than expected power, the other port will have
lower than expected power.
• The port with a higher than expected power raises the “Crossed Fibers
Suspected” alarm if the delta is greater than 3 dB.
• The port with lower than expected power would normally raise the “High
Fiber Loss” alarm (provided the High Fiber Loss Detection parameter is
set to enabled). However, if the “Crossed Fibers Suspected” alarm is
raised, the “High Fiber Loss” alarm is suppressed.
For example, assume that OPM port 1 is expecting -7 dBm and OPM port 2 is
expecting -11 dBm. When the fibers are crossed:
• Port 2 sees 4 dB more power than expected and the “Crossed Fibers
Suspected” alarm is raised.
• Port 1 sees 4 dB less power than expected and raises the “High Fiber
Loss”, which is suppressed.

Figure 2-22
Example of Crossed Fiber alarming on backbone or DIA OTS WSSOPM

Automatic Shutoff Compromised alarm

The “Automatic Shutoff Compromised” alarm ensures that crossed OSC
fibers can be detected at SLAT time prior to the turn up of a link with spans
bookended by RLA, SRA, SAM, or ESAM hardware.
On the SRA, SAM, or ESAM, OSC fibering is normally between

• OSC SFP Tx (Port 2 Tx) -> OSC In (Port 3)
• OSC Out (Port 4) -> OSC SFP Rx (Port 2 Rx)
The alarm is raised:

• When OSC fibers are crossed at a single node (illustrated in Figure 2-23
on page 2-113.)
• When OSC fibers are crossed at both nodes.

Figure 2-23
Crossed OSC fibers at one node - resulting in Automatic Shutoff Compromised alarm

Channel Opacity Error

The “Channel Opacity Error” alarm is raised against a ROADM OTS
WSS/RLA NMCC facility if its Opaque parameter is Yes for a DOC-controlled
channel. The “Alarm Additional info” field shows the affected NMCC
wavelength if the channel is on 50 GHz ITU Reference Bandwidth, otherwise
it shows its center frequency.
Minimum Gain
The “Minimum Gain” alarm is raised against an amplifier or an RLA amplifier
input facility when an amplifier is at its minimum extended range gain setting
and the peak channel power overshoots the provisioned peak power target by
2 dB due to one of the following conditions:
• The actual span loss is less than designed value.
• Wrong pad/DCSM placement at the amplifier node or upstream nodes.
• Faulty pads which results in incorrect padding value (for example, faulty 10
dB pad only yields 5 dB attenuation).
• Improper provisioning of the amplifier or upstream amplifier peak power
targets.
• The MLA2v or NTK722AA RLA VOA has not been optimized by DOC or
has not been provisioned properly if manual provisioning is being used.
This alarm does not apply to drop LIM amplifiers or amplifiers running at fixed
gain. DOC checks for the Minimum Gain condition on each auto-monitor
cycle.
Low Optical Return Loss

The “Low Optical Return Loss” alarm allows an easier identification of optical
reflection issues in photonic layer systems. It is raised when the ORL is worse
than 22 dB. It is raised on the following circuit packs:
• SLA, MLA, MLA2, MLA3 and MLA2v
• SRA/ESAM/SAM and XLA
• ESAM/SAM and MLAx
• RLA
The alarm also indicates the location of the alarm, i.e. where high reflected
power is observed, either at the input or output. The input location applies to
the SRA only.The output location applies to both SRA and 6500 LIM or XLA
(EDFA) circuit packs.
There is no hysteresis for clearing this alarm.

Gauge Threshold Crossing Alert Summary

Raised on T-Series or S-Series (ESAM and SRA) if any of the following
conditions are exceeded for either a short or a long OTDR trace. Thresholds
are defined in PM’s:
• Single point loss threshold
• Single point reflection threshold
• Cumulative loss threshold
• Cumulative reflection threshold
AMPMON facility alarming on amplifier output

The AMPMON facility is on the amplifier output ports of line facing photonics
equipment (MLAx, SLA, XLA, SRA). The purpose of this AMPMON facility is
to address output alarms which are reported against amplifier input ports (port
6 or port 8). The following output alarms are raised against AMPMON facility
(port 5 or 7):
• Automatic Power Reduction Active
• Output Loss of Signal
• Low optical Return Loss at Output
Note: AMPMON facility is a child facility of the corresponding AMP facility and
its primary state always follows the primary state of the parent AMP. The
parent AMP refers to the AMP facility on the input port (port 6 or 8) of the same
Line. The AMPMON facility is auto-created subsequently after the creation of
the parent AMP facility. The AMPMON facility is auto-deleted subsequently
after the deletion of the parent AMP facility.
Incomplete Channel Topology

The “Incomplete Channel Topology” alarm is raised as a warning to highlight
stale or leftover Shelf Wavelength Topology (SWT) provisioning (for example,
orphaned Tx/Rx adjacency or unused cross-connection), which is not part of
a complete NCT channel.
Such leftover provisioning can result in unintended channels being built as a

result of subsequent provisioning actions. For example, an orphaned Rx
adjacency causing a channel to drop unexpectedly.
This warning is raised against an OTS one hour after detecting one or more
wavelengths in that OTS with ROUTING set to ADD, DROP, or
PASSTHROUGH, and COMPLETE set to FALSE.

Adjacency Mismatch
The “Adjacency Mismatch” alarm is raised against an ADJ-LINE facility when
the Expected far-end address parameter of the line adjacency is manually
provisioned, but does not match the discovered address (Actual Far End
Address) listed for the ADJ-LINE facility.
If the provisioned information is correct, mis-fibering can be the cause for this
alarm.
For configurations using MPO cables, an MPO mis-cabling error where the
Adjacency Expected Far End Address does not match the Adjacency Actual
Far End Address and is not NULL, causes the “Adjacency Mismatch” alarm to
be raised on the adjacencies at both ends of the MPO cable.
The alarm is also raised in configurations using MPO cables when:

• the derived adjacencies from the TID slot sequence provisioning on the
FIM do not match the actual MPO cabling to equipment
• after deleting an unused equipment, you leave the MPO cables connected
to the deleted equipment
• after removing the equipment from the TID slot sequence, you leave the
MPO cables connected to the removed equipment
• mis-fibering of the equipment
This alarm is expected on nodes adjacent to nodes undergoing a TID

consolidation reconfiguration. These alarms clear after the inter-shelf
adjacencies are updated with the Node name.
This alarm is raised against an ADJ-TX or ADJ-RX facility when either the
ADJ-TX or ADJ-RX facility has a discovered type that does not match the
transmitter or receiver type.
A change to the discovered type occurs when the expected far-end addresses
that establish the connection between the transponder circuit packs and the
CMD ports have changed or the provisioning on the transponder circuit pack
has changed.
Normally when the ADJ-TX or ADJ-RX facility has Auto Discovered set to
Auto, any change to the discovered type is automatically populated to the
transmitter or receiver type. However, if the change happens while the ADJTX
or the ADJ-RX is managed by DOC (DOC Care is True), a cross-connect
exists, or if the “Synch Provisioned” parameter is false, this auto-population is
not possible and causes a mismatch.

OSPF Max Capability Reached

The “OSPF Max Capability Reached” alarm is raised when a shelf reaches its
maximal capacity of handling the number of OSPF network elements in the
OSPF network. These OSPF network elements may include 6500 and CPL
shelves as well as other OSPF capable equipment.
This alarm provides an early warning indication to prevent the OSPF network
from potential failure.
Alarm correlation
There are two facets to the alarm correlation feature:
• Site Level Alarm Correlation (SLC)
• Network Level Alarm Correlation (NLC)
Once Alarm Correlation is enabled, it automatically enables both Site level

and Network level alarm correlation. One cannot exist without the other. Both
require the system to have full knowledge of topology and connectivity within
the network, including channel routing at OADM nodes.
This alarm correlation parameter is accessible via Site Manager Node

Information application on the System tab, with provisionable values of On
(default) or Off.
For Alarm Correlation to function properly, all shelves at a node must be

TID-consolidated.
Further detail is available in Technical Publication 323-1851-543 Fault

Management - Alarm Clearing. Alarm correlation aids troubleshooting by
raising the alarm at the source and suppressing any downstream alarms. An
overview of these features is provided below:
• The SLC feature reduces the number of alarms reported at each node to
a minimum.
— It does not reduce the number of nodes in a network reporting alarms.
This is done by Network level alarm correlation feature.
— It requires that physical adjacency information be provisioned between
Photonic equipment at a node.
— In order to work all the way down to the service layer, physical
adjacency information needs to be provisioned using the Far End
Address of the transponder Tx/Rx interface, to be used as part of
SPLI.
• Network level alarm correlation builds on the SLC feature.

— SLC masks alarms within a node based on a detected fault. However,

SLC does not share fault information with neighboring nodes in the
network. It also does not track per-channel failures when channels are
muxed and mixed together with non-failed channels.
— Essentially, NLC will do SLC but also addresses the gaps of the SLC
feature based on wavelength topology.
— NLC supports OTS to OTS (intra-node and inter-node) Network Level
Alarm Correlation messaging, and shares and collects channel status
information with neighbors.
Attention: Network Alarm correlation is supported in 6500/CPL

interworking. One of the requirements is that all shelves (no matter the OTS
type provisioned - including TOADM and GOADM) must have TID
consolidation enabled (CPL and 6500).
Alarm correlation support at CDC nodes

As 20x1 WSS/RLA and CCMD8x16/CCMD 16x12/CCMD 8x4 have MPO
ports, a virtual OPTMON facility exists on each MPO port to represent the
combined state of the sub-fiber connections. This way, individual LOS
conditions on the sub-fibers can be consolidated such that the LOS is raised
on the virtual OPTMON, masking the individual LOS alarms on the sub-fibers.
Alarm Correlation support on the OPS Module

The NTK554TA 4xOPS circuit pack and NTK576AA OPS module is supported
by alarm correlation software.
A photonic layer loss of light (LOS) at OPS SW1 In or SW2 In does not result
in an alarm against OPS SW1/SW2 ports if:
• SLC (Site Level Correlation) is enabled and a correlated upstream alarm
within the same node co-exists with the OPS LOS fault.
• NLC (Network Level Correlation) is enabled and a correlated upstream
fault co-exists with the OPS LOS fault.
Bias Provisioning
Bias provisioning refers to the methods by which a given channel power can
be treated differently from the other channels by the control algorithms, in
order to maximize performance. These methods are generally used when
transponders with different transmission characteristics share the same
optical link.

Three such methods are available:

• Photonic Differential Provisioning, applicable to fixed grid and flexible grid
systems;
• Tx SNR Bias, applicable to flexible grid only;
• Media Channel Bias, applicable to flexible grid only.
The first method is described below. The other two are described in
NTRN15DA, Photonic Layer Guide, Part 3 of 3.
Photonic Differential Provisioning

Photonic Differential Provisioning allows groups (or classes) of channels to be
prioritized to achieve a different relative optical signal-to-noise ratio (OSNR) to
other channels. By doing this it allows channels with very different propagation
characteristics (e.g. 2.5G, 10G, 40G, 40G ULH, 100G, 200G, etc.) to be
optimized to different OSNR targets.
Without Differential Provisioning, channels carrying different traffic types are

not distinguished by the amplifiers, and the peak power target that is set must
be a compromise accommodating all types. DOC treats all channels equally,
and attempts to optimize them so that they have the best possible, but equal,
OSNR. In this scenario, performance might be optimal for one particular type,
but at the expense of the other types. With Photonic differential provisioning,
traffic with different transmission characteristics are grouped into different
classes and assigned a bias offset from the peak power target. The peak
power target is then no longer a compromise value but a baseline to select the
best peak power for the various traffic types present.
The bias can be thought of as a target power “tweak”, relative to the overall
provisioned peak power targets. For example, assuming an amplifier has a
peak power target of +3 dBm:
• a class with a bias of 0 dB will be controlled to achieve +3 dBm (for the
peak channel in that class)
• a class with a bias of -5 dB would be controlled to achieve -2 dBm (for the
peak channel in that class)
The user can provision the bias for each of the defined classes using the Site
Manager Configuration -> Photonic Services -> Differential Provisioning
application.
Also note that:
• As part of the Tx adjacency provisioning, a modulation class is assigned
based on Transmitter type
• Automatic class assignment can be overridden, and re-provisioned to a
Custom class

— The user is allowed to change the Modulation Class from the default
entry to any of the custom class entries for any Tx types, whether the
channel is managed or not.
• Transmitter class type is propagated automatically to downstream
domains for optically branched channels
• At each domain boundary, a differential bias may be applied to each class
of channels
— For branched systems, the bias must be manually provisioned in
subsequent downstream domains (otherwise it would default to zero)
— This is required because the bias value (per class) is a function of link
budget (e.g. different fiber types), which may be different from domain
to domain
• Grouping channels with similar characteristics (into classes) and then
provisioning a relative bias per class eliminates the need to provision each
wavelength individually
• There is only one bias value (per class) per domain.
— If the domain contains different fiber types with very different
characteristics, then this may require an average/compromise bias
value
— Alternatively, domains could be segmented to allow a different bias to
be applied
• For Ciena interfaces, bias values are supplied by OnePlanner or OPNET.
• In Fixed Grid mode, the provisionable range is -5 to +5 dB with the
following rule: the bias delta between any two modulation classes cannot
be more than 6 dB.
For more information on the Photonic differential provisioning and related

parameters/procedures, see Technical Publication 323-1851-310/311,
Configuration - Provisioning and Operating.
Photonic Interworking
Interworking of 6500 configurations using DOC with those not using DOC
In general, 6500 configurations using DOC and those that do not use DOC are
by their nature not deployed together in interworking scenarios, since the latter
configurations require manual equalization. No official support is provided by
Ciena in such interworking configurations.
The exception to this is the passive Thin Terminal/Passive Bridge to Backbone

ROADM OTS configurations. Assuming a favorable link engineering analysis,
traffic continuity between the two types of configurations can occur.

Considerations regarding nodes running different software releases

An optical system (or Photonic Domain) consisting of several nodes and an
optical network consisting of several optical systems (or Photonic Domains)
can only have nodes running different releases during a planned software
upgrade of the network.
Release interworking is intended to facilitate software upgrades for large

networks over a reasonable time window. This is not intended as a long term
system configuration.
Refer to the Software Upgrade Procedure for more details.
6500 T-Series interworking with 6500 S-Series/D-Series

The following photonics interworking configurations are supported between
6500 T-Series and 6500 S-Series/D-Series shelves:
• T-Series ROADM interworking with S/D-Series Colorless Direct Attach
(CDA) using WSS Flex C-Band w/OPM 20x1 (NTK553MA) and optional
S/D-Series line amplifier sites (see further down for supported amp sites)
• T-Series ROADM interworking with S/D-Series Colorless Direct Attach
(CDA) using WSS Flex C-Band w/OPM 9x1 (NTK553LA/LB) and optional
S/D-Series line amplifier sites (see further down for supported amp sites)
• T-Series ROADM interworking with T-Series ROADM using following
S/D-Series line amplifier sites (96 channels support):
— MLA3/LIM
— ESAM/XLA/ESAM
— ESAM/MLA3/ESAM
— SRA/XLA/SRA
— SRA/XLA/ESAM
When a T-Series shelf faces an S/D-Series shelf, the following considerations

apply:
• The user must provision channels using L0 provisioning (see “Wavelength
provisioning using L0 Provisioning Control Plane type” on page 5-39).
Same goes for channel deprovisioning.
• OSC Delay Measurement: T-Series displays this as “Delay Measurement”
while pre-Rel. 12.1 S/D-Series displays it as “Round Trip Delay
Measurement”.
— S/D-Series displays this measurement as “Delay Measurement”, like
T-Series. DM in S/D-Series can interwork with DM in T-Series.
• OTDR traces: T-Series displays the information in the OTDRCFG facility
while pre-Rel. 12.1 S/D-Series does it through the Telemetry facility.

— S/D-Series OTDR is managed via the OTDRCFG facility, like T-Series.

OTDR in S/D-Series can interwork with DM in T-Series.
6500 T-Series interworking with CPL

Please contact Ciena for details about 6500 T-Series ROADM node
interworking with CPL Line Amp or ROADM node.
6500 S-Series and D-Series interworking with CPL

See below for list of supported configurations. Note that CPL equipment is
limited to 88 channels. Also, CPL Rel. 12.0 is the final release for CPL channel
access nodes (CPL Line Amp nodes can run releases higher than Rel. 12.0).
However, CPL channel access nodes running Rel. 12.0 do interwork with
6500 nodes running Rel. 12.6.
6500 channel access or 6500 Line Amp node interworking with CPL Line Amp
node
The supported configurations are shown in Figure 2-24 on page 2-126 and
Figure 2-25 on page 2-127. Also, rules using SRA, ESAM, SAM and XLA
hardware are illustrated in Figure 2-35 on page 2-134 and Figure 2-36 on
page 2-135. The supported configurations include:
• 6500 Terminal/ROADM nodes with
— CPL Line Amp nodes
— A mix of 6500 Line Amp nodes and CPL Line Amp nodes
— A mix of 6500 Line Amp nodes and CPL Line Amp nodes with CPL
Raman amplification between CPL Line Amp nodes only
— 6500 ROADM nodes or 6500 Line Amp nodes configured with ESAM
(or SAM) and XLA circuit packs can interwork with CPL Line Amp
nodes that use CPL LIM modules
– The ESAM and SAM OSC SFPs interwork with the DOSC OSC
Tx/Rx interfaces
– SAMs can interface to SAMs, ESAMs or any legacy CPL or 6500
configuration using LIMs (LIM, MLA, MLA2, ML2v, and MLA3)
– ESAMs can interface to ESAMs, SAMs or any legacy CPL or 6500
• 6500 Terminal/TOADM nodes with
— CPL Line Amp nodes
— A mix of 6500 Line Amp nodes and CPL Line Amp nodes
— A mix of 6500 Line Amp nodes and CPL Line Amp nodes with CPL
Raman amplification between CPL Line Amp nodes only

6500 channel access node interworking with CPL channel access node
The supported configurations are shown in:
Also, rules using SRA, ESAM, SAM and XLA hardware are illustrated in
Figure 2-35 on page 2-134 and Figure 2-36 on page 2-135. The supported
configurations include:
• 6500 WSS-based Terminal/ROADM nodes with
— CPL Line Amp nodes and CPL Terminal/ROADM nodes
— 6500 Line Amp nodes and CPL Terminal/ROADM nodes
— 6500 Line Amp nodes, CPL Line Amp nodes and CPL
Terminal/ROADM nodes
— CPL Line Amp nodes and CPL Thin Terminal/TOADM nodes
— 6500 Line Amp nodes and CPL Thin Terminal/TOADM nodes
— 6500 Line Amp nodes, CPL Line Amp nodes and CPL Thin
Terminal/TOADM nodes
— CPL Line Amp nodes and CPL GMD-based Terminal/GOADM nodes
— 6500 Line Amp nodes and CPL GMD-based Terminal/GOADM nodes
— 6500 Line Amp nodes, CPL Line Amp nodes and CPL GMD-based
Terminal/GOADM nodes
• 6500 Thin Terminal/TOADM nodes with
— CPL Line Amp nodes and CPL Terminal/ROADM nodes
— 6500 Line Amp nodes and CPL Terminal/ROADM nodes
Terminal/ROADM nodes
— CPL Line Amp nodes and CPL Terminal/TOADM nodes
— 6500 Line Amp nodes and CPL Terminal/TOADM nodes
Terminal/TOADM nodes
— CPL Line Amp nodes and CPL GMD-based Terminal/GOADM nodes
— 6500 Line Amp nodes and CPL GMD-based Terminal/GOADM nodes

— 6500 Line Amp nodes, CPL Line Amp nodes and CPL GMD-based
Terminal/GOADM nodes
• The following topologies are supported in a 6500/CPL
ROADM/TOADM/GOADM interworking:
— Point-to-Point
— Meshed Ring
— Hubbed Ring
• A CPL ROADM provisioned as a DOC site can control a 6500 Raman
span bookended with SRA circuit packs.
— SRAs must be bookended
— SRAs and XLAs can only be in 6500 shelves
— CPL DRA and 6500 SRA are not supported on the same fiber pair
• 6500 ROADM nodes configured with ESAM (or SAM) and XLA circuit
packs can interwork with CPL ROADM nodes that use LIM modules.
— The ESAM and SAM OSC SFPs interwork with the DOSC/UOSC OSC
Tx/Rx interfaces
— SAMs can interface to SAMs, ESAMs or any legacy CPL or 6500
— ESAMs can interface to ESAMs, SAMs or any legacy CPL or 6500
Linear SPUR (CPL only)

Supported SPUR configurations are shown in Figure 2-30 on page 2-130.
Some facts about SPUR configurations:
• SPUR configuration is supported only in a CPL node and not supported in
a 6500 node.
• SPUR configuration always has to be in a domain boundary.
• A CPL SPUR configuration can be adjacent to a CPL or a 6500 domain.
6500 Photonic interworking with CPL DIA

6500/CPL DIA OADM is supported in a 6500/CPL ROADM interworking
configuration (see Figure 2-32 on page 2-131).
6500 Colorless node interworking with CPL

6500 Colorless configurations can interwork with CPL nodes.
In colorless configurations, a wavelength can be added/dropped at a colored

node and added/dropped at a colorless node provided the wavelength is using
a supported colorless-capable circuit pack (see Figure 2-33 on page 2-132).

6500/CPL photonic interworking operational considerations

The following operational considerations should be noted:
• Alarm correlation is not supported in 6500/CPL interworking.
• Different OnePlanner demand limits exist for the number of domains a
channel can traverse when interworking between 6500 and CPL:
— Homogeneous CPL: 20 Domains
— Homogeneous 6500: 20 Domains
— Mixed 6500/CPL (CPL AMPs): Governed by the 6500 software
release
— Mixed 6500/CPL (CPL ROADM): Governed by the lowest common
denominator based on 6500 and CPL software releases
• The NTK592NVE6 OSC SFP pluggable cannot be used in a 6500 OTS
interworking with a CPL OTS.
• When using the Low Tx Power SFP (NTK592NGE5), span losses from
8.5 dB to 25 dB (measured at 1550 nm) are supported with CPL at one
end and 6500 at the other end. To give an equivalent CPL OSC Tx power
to the Low Tx Power SFP a 7 dB pad must be installed on the CPL OSC
Tx.
— In order for Site Manager to report a correct span loss, any CPL OSC
Tx padding must be provisioned as Excess Loss on the OSC
ADJ-FIBER facility at the CPL node.
• DCN configurations are limited to the ones supported by both 6500 and
CPL. For instance:
— 6500 TL1 Gateway does not support CPL remote network elements
— Private IP (GNE/RNE) comms configuration is not supported in a
6500/CPL interworking configuration
• Foreign wavelengths are supported in an 6500/CPL ROADM/TOADM
interworking.
• 6500 SRA circuit packs cannot be bookended with CPL Raman (DRA)
circuit packs.
Unsupported 6500/CPL photonic interworking configurations

The unsupported configurations are:
• A CPL/6500 TOADM is not supported as a domain boundary for

passthrough traffic. A TOADM can be a DOC only if it is a Terminal node
for interworking to function (see Figure 2-31 on page 2-130).

• When interworking with 6500 and CPL TOADM nodes, note that every
Optical Section in a Photonic Domain must have at least one active circuit
pack (SLA/MLA/MLA2/MLA3/WSS/SCMD4), and hence you cannot
deploy a TOADM Optical Section with LIMs and no SCMD4s on either
end.
6500/CPL node level interworking

6500 and CPL nodes can be mixed within a same TID-consolidated node.
Figure 2-24
6500 Photonics interworking with CPL Line Amp nodes
(Configurations using 6500 ROADM nodes with or without 6500 Line Amp nodes)

Figure 2-25
6500 Photonics interworking with CPL Line Amp nodes
(Configurations using 6500 TOADM nodes with or without 6500 Line Amp nodes)
6500 CHA sites (ROADM and TOADM) with CPL line-amps
OME
R OADM
ROADM TOADM
CPL Line-Amp CPL Line-Amp
2XOSC
DOSC DOSC
SCMD4
2XOSC
WSS
LIM
SP
LIM
SP
LIM LIM
LIM LIM
6500 CHA sites (TOADM) with CPL line-amps

OME
TOADM
TOADM TOADM
CPL Line-Amp CPL Line-Amp
SCMD4
2XOSC
DOSC DOSC
SCMD4
2XOSC
LIM
SP
LIM
SP
LIM LIM
LIM LIM
6500 CHA sites (ROADM and TOADM) with mixture of CPL and 6500 line-amps
OME
R OADM
ROADM Line-Amp TOADM
CPL Line-Amp
2XOSC
DOSC
SCMD4
2XOSC
2XOSC
WSS
LIM
LIM
LIM
LIM
SP
SP
SP
LIM
LIM
6500 CHA sites (TOADM) with mixture of CPL and 6500 line-amps
OME
T OADM
TOADM Line-Amp TOADM
CPL Line-Amp
SCMD4
2XOSC
DOSC
SCMD4
2XOSC
2XOSC
LIM
LIM
LIM
LIM
SP
SP
SP
LIM
LIM
6500 CHA sites (ROADM and TOADM) with CPL line-amp and Raman between CPL sites
OME
R OADM
ROADM CPL Line-Amp/Raman TOADM
CPL Line-Amp/Raman
DOSC DOSC
2XOSC
SCMD4
2XOSC
WSS
LIM
SP
LIM
LIM LIM
SP
LIM Raman amplified span LIM
RAMAN RAMAN
6500 CHA sites (ROADM and TOADM) with CPL line-amps and Raman between
6500 and CPL sites
Line-Amp TOADM
CPL Line-Amp/Raman CPL Line-Amp/Raman
DOSC DOSC
SCMD4
2XOSC
2XOSC
LIM
LIM
LIM
SP
SP
LIM LIM
RAMAN RAMAN
pad
pad
OME
ROADM
ROADM
2XOSC
WSS
LIM
SP
To deploy Raman at an 6500 site, you need to deploy an additional CPL line-
amp site with pads for an additional span. Expect SLA to be deployed on 6500
ROADM, LIM/MLA2/MLA3 deployed on CPL line-amp.
6500 CHA sites (TOADM) with CPL line-amp and Raman between CPL sites
TO ADM CPL Line-Amp/Raman TOADM
CPL Line-Amp/Raman
SCMD4
DOSC DOSC
2XOSC
SCMD4
2XOSC
LIM
SP
LIM
LIM LIM
SP

RAMAN RAMAN
6500 CHA sites (TOADM) with CPL line-amps and Raman between
6500 and CPL sites
Line-Amp TOADM
CPL Line-Amp/Raman CPL Line-Amp/Raman
DOSC DOSC
SCMD4
2XOSC
2XOSC
LIM
LIM
LIM
SP
SP
LIM LIM
RAMAN RAMAN
pad
pad
TOADM
SCMD4
2XOSC
LIM
SP
To deploy Raman at an 6 500 site, you need to deploy an additional CPL line-
amp site with pads for an additional span. Expect SLA to be deployed on 6500
TOADM, LIM/MLA2/MLA3 deployed on CPL line-amp.

Figure 2-26
6500 Photonics ROADM nodes interworking with 6500/CPL Line Amp nodes and CPL ROADM
nodes
Figure 2-27
6500 Photonics ROADM nodes interworking with 6500/CPL Line Amp nodes and CPL TOADM
nodes

Figure 2-28
6500 Photonics TOADM nodes interworking with 6500/CPL Line Amp nodes and CPL ROADM
nodes
Figure 2-29
6500 Photonics TOADM nodes interworking with 6500/CPL Line Amp nodes and CPL TOADM
nodes

Figure 2-30
Supported SPUR configurations
Figure 2-31
Unsupported configuration for 6500/CPL TOADM as domain boundary for passthrough traffic
6500 ROADM CPL TOADM CPL ROADM

DOSC DOSC
2XOSC
WSS
LIM LIM
LM
SP
sCMD4/8 WSS
Domain A (6500/CPL) Domain B (CPL only)
A CPL/6500 TOADM not supported

as a domain boundary for
passthrough traffic. TOADM can be
DOC only if it's a Terminal.
6500 ROADM 6500 TOADM CPL ROADM

DOSC
2XOSC
2XOSC
sCMD4
WSS
LIM
LM
LM
SP
SP
WSS
Domain A (6500 only) Domain B (6500/CPL)

Figure 2-32
6500 Photonics ROADM/TOADM/DIA interworking with CPL ROADM/TOADM/DIA
6500 ROADM CPL TOADM 6500 TOADM CPL ROADM

DOSC DOSC
2XOSC
2XOSC
sCMD4
WSS
LIM
LIM
LIM LIM
SP
SP
sCMD WSS
Any number of CPL/6500 line amp sites (not shown) between

CHA sites as alloed by link budget
6500 ROADM CPL ROADM CPL ROADM 6500 ROADM
DOSC DOSC
2XOSC
2XOSC
WSS
WSS
LIM
SP
LIM
LIM LIM
SP
sCMD WSS
CPL DIA
DOSC
6500 DIA
LIM
WSS
WSS
LIM
SP
CMD44
CMD44

Figure 2-33
COADM and CPL interworking

Figure 2-34
6500 Photonic ROADM/TOADM interworking with CPL GOADM/ROADM/TOADM

Figure 2-35
SAM, ESAM and SRA interworking configurations

Figure 2-36
SAM, ESAM and SRA interworking configurations - example system view


Photonic Applications 3-
This chapter describes the applications that are the foundations of the 6500
Packet-Optical Platform (6500) optical network architecture.
Table 3-1
Topic
“Colored Directional” on page 3-4
— “Overview” on page 3-4
— “Architecture” on page 3-5
— “Metro ROADM” on page 3-8
“Colored Directionless” on page 3-15
— “Unsupported DIA configurations” on page 3-34
“Colorless Directionless” on page 3-34
— “Unsupported COADM OTS configurations” on page 3-37
“Colorless Directional or Colorless Direct Attach (CDA)” on page 3-42
— “Unsupported CDA with COADM direct attach configurations” on page 3-44
“Colorless Directionless, Colored Directionless and Colored Directional using 9x1 WSS” on page 3-51
— “Engineering rules and guidelines” on page 3-53
— “Unsupported Colorless Directionless, Colored Directionless and Colored Directional
configurations” on page 3-54
“Low channel count Colorless Directionless” on page 3-56

3-2 Photonic Applications
Table 3-1
Topics in this chapter (continued)
Topic
— “Unsupported low channel count CD configurations” on page 3-58
“Low channel count Colorless Directionless and Colored Directional using 9x1 WSS” on page 3-61
— “Unsupported low channel count CD configurations” on page 3-63
“Colorless Directional or Colorless Direct Attach (CDA) using 20x1 WSS, FIM Type 4, FIM Type 5 and
FIM Type 6” on page 3-64
— “Architecture using TID Sequence Provisioning” on page 3-65
— “Architecture using Manual Adjacency Provisioning” on page 3-71
— “Unsupported CDA with CCMD12 direct attach configurations” on page 3-74
“Colorless and Colored Direct Attach (CDA) using 20x1 WSS, FIM Type 4, FIM Type 5 and FIM Type 6”
on page 3-74
— “Architecture using TID Sequence Provisioning” on page 3-75
“Colorless Directionless Contentionless (CDC) using 20x1 WSS” on page 3-77
— “Architecture - greenfield deployment” on page 3-78
— “Architecture - brownfield deployment” on page 3-82
— “Unsupported CDC configurations” on page 3-83
“Colorless Directionless Contentionless (CDC) and Colored using 20x1 WSS” on page 3-83
— “Overview CMD44 50 GHz” on page 3-83
— “Architecture CMD44 50 GHz” on page 3-84
— “Overview CMD44 100 GHz” on page 3-84
— “Architecture CMD44 100 GHz” on page 3-84
“T-Series Colorless, Directionless, Contentionless (CDC)” on page 3-85
— “Unsupported CDC configurations” on page 3-97
“SCMD4 based Thin Terminal and Thin OADM (TOADM)” on page 3-97

Table 3-1
Topic
“96-channel support” on page 3-104
— “96 channel operational considerations” on page 3-105
“Supported transponders for colorless and CDC line systems” on page 3-107
“OSC” on page 3-108
— “OSC SFP hardware” on page 3-109
— “OSC SFP carrier hardware” on page 3-110
— “OSC filters embedded in circuit packs” on page 3-110
— “Extra OSC drop filter module used in Raman applications” on page 3-111
— “OSC Span Loss and OSC Span Loss PMs” on page 3-113
— “OSC Span Loss and OSC Span Loss PMs” on page 3-113
— “Wayside Channel (WSC)” on page 3-113
— “OSC Delay Measurement on S/D-Series and T-Series” on page 3-115
“EDFA amplified applications” on page 3-116
— “Shared amplifier node” on page 3-116
— “SLA-based Drop LIM” on page 3-119
— “MLA2v - EDFA with embedded VOA” on page 3-119
— “Compact footprint Line Amp node using SPAP-2 w/ 2xOSC 2xSFP” on page 3-123
— “SLA/MLA Mux Amp” on page 3-124
— “Dual XLA Line Amplifier” on page 3-125
“Raman amplified applications” on page 3-126
— “Raman amplification overview” on page 3-126
— “Single Line Raman amplifier (SRA)” on page 3-128
— “Enhanced Service Access Module (ESAM)” on page 3-131
— “Service Access Module (SAM)” on page 3-133
“Optical Time Domain Reflectometer (OTDR)” on page 3-134
— “OTDR traces” on page 3-135
— “OTDRCFG PMs” on page 3-141
— “OTDR alarming” on page 3-142

Table 3-1
Topic
— “T-Series automatic OTDR examples” on page 3-145
— “Understanding T-Series short traces” on page 3-147
— “Operational considerations for OTDR feature” on page 3-148
“Distributed ROADM” on page 3-149
“Remote CMD44” on page 3-151
“Standalone OPM C-Band 2-Port circuit pack (NTK553PA)” on page 3-154
— “C-Band 2-port OPM with Enhanced CMD44 50 GHz modules” on page 3-154
— “C-Band 2-port OPM at Line Amp nodes” on page 3-155
— “C-Band 2-port OPM connections to LIMs at ROADM and TOADM nodes” on page 3-157
— “2-port OPM as generic spectrum monitoring device” on page 3-157
“Optical protection switching using the OPS circuit pack” on page 3-158
— “OPS protection architecture” on page 3-158
— “OPS provisioning” on page 3-161
— “OPS optical path protection options” on page 3-162
— “Transceiver-Triggered OPS protection” on page 3-163
Colored Directional
Overview
The Colored Directional application is the simplest of the ROADM
configurations and uses Colored mux/demux modules connected to WSS or
NTK553RA RLA circuit packs.
Hardware
The ROADM OTS can be comprised of the following components:
• CMDxx: CMD44 50 GHz Blue, CMD44 50 GHz Red, CMD44 100 GHz,
CMD64 75 GHz
• CMD96: CMD96 50GHz (only applicable to 9x1 WSS configurations)
• BMD2: Only required when using the CMD44 50 GHz Blue and CMD44
50 GHz Red on the same switch port.
• SLA, MLA, MLA2, MLA3, XLA, SRA, ESAM or SAM
• WSS: WSSOPM 100 GHz 2x1, WSSOPM 100 GHz 4x1, WSSOPM
100 GHz 5x1, WSSOPM 50 GHz 2x1 and WSSOPM 50 GHz 9x1

• RLA 5x1
In this release, the RLA 5x1 does not support the following Photonic
applications:
• Remote CMD44
• SLA-based Drop LIM
• Cascaded LIM (Interior SLA)
• SLA/MLA Mux Amp
• Metro ROADM
Architecture
When two or more channel access configurations of the ROADM OTS
subtype are created in a node, interconnections between their RLAs or WSSs
allow for photonic branching applications, which can form linear, ring or mesh
topologies in the photonic layer.
Photonic branching provides the following benefits using ROADM OTSs:

• Savings by the elimination of regenerators at branching locations.
• Wavelengths can be routed along the primary route or to local POPs for
add/drop.
— You can route any wavelength in any direction
— You can perform rapid provisioning and remote reconfiguration
• Allows for future network expansion when you want to connect to other
regional networks also deploying 6500 Photonic Layer
The figure below shows an example for a branching optical path. Note that in
the figure, 44 channels (44ch) applies if using 100 GHz WSS, however 88
channels (88ch) also applies when using 50 GHz WSS and 50 GHz CMD44
modules. 96 channels (96ch) applies when using 9x1 WSS 50GHz and 50
GHz CMD96 module.

Figure 3-1
Photonic branching optical path (example)
Traffic (44 ch) Traffic (44 ch)

Ch 1' incoming Ch 1' is still present
OPM
WSS
WSS Traffic (44 ch)
With Ch 1' is
allowed to
continue
OPM
CMD44 CMD44 WSS controls the

power of each
channel allowed
Traffic (44 ch) Ch 1" is to continue
Ch 1' is locally not added
dropped
6500 supports the following characteristics for Photonic branching:

• Branching is supported with any supported network topology (allowed to
link a point to point to a mesh ring, a hubbed ring to a linear OADM
network, two rings together, etc.).
• Adding branching capability or adding/deleting one branching degree can
be done in service without any traffic interruption. This is independent of
the number of degrees being added/deleted.
• At any given node, branching channels are supported together with
add/drop channels.
• Branching channels path is done without any traffic impact on other
channels; that is, non-service affecting (NSA).
— Branching set-up is created during the channel creation.

— To guarantee the non-service affecting operation, the action must be

performed through DOC.
— Changing the branching set-up is a non-service affecting (NSA)
procedure for other channels present, but service affecting (SA) for the
channels switched (switching channels must be deleted from end to
end and re-added with the new settings).
The following RLA/WSS circuit packs can be provisioned as part of the
ROADM OTS subtype for branching:
Table 3-2
6500 RLA/WSS circuit pack types
PEC Description Width Number of

(# slots) branches
supported
NTK553EA 100 GHz WSS w/OPM C-Band 5x1 (Note 1) 2 5 (Note 2)
NTK553HA 100 GHz WSS w/OPM C-Band 4x1 1 4 (Note 2)
NTK553JA 100 GHz WSS w/OPM C-Band 2x1 2 2 (Note 2, Note 3)
NTK553JB 100 GHz WSS w/OPM C-Band 2x1 1 2 (Note 2, Note 3)
NTK553FA 50GHz WSS w/OPM C-Band 9x1 3 8 (Note 2)
NTK553FC 50 GHz WSS w/OPM C-Band 9x1 2 8 (Note 2)
NTK553LA/LB WSS w/OPM C-Band 9x1 Gridless (Note 4) 2 8 (Note 2)
NTK553KC 50GHz WSS w/OPM C-Band 2x1 3 2 (Note 2, Note 3)
NTK553KA 50GHz WSS w/OPM C-Band 2x1 1 2 (Note 2, Note 3)

Table 3-2
6500 RLA/WSS circuit pack types
PEC Description Width Number of

(# slots) branches
supported
NTK553MA Flex WSS w/OPM C-Band 20x1 2 See Note 5, Note

6 and Note 7
NTK553RA ROADM with Line Amplifier (RLA) C-Band 5x1 2 5 (Note 2)
Note 1: The NTK553EA circuit pack has four upgrade switch input ports for future expansion, which are
currently unused.
Note 2: With 100% local add/drop per degree capability.
Note 3: It is possible to have a branching site with 3 connected 2X1 WSS circuit packs without local
Add/Drop. This is not supported by OnePlanner though, and therefore necessitates a custom design.
Note 4: The NTK553LA/LB is flexible-grid ready, and provides fixed grid functionality on par with the
NTK553FA/FC 50 GHz WSS circuit packs. The NTK553LB variant is architected to support future
flexible grid applications with traffic channels that are greater than 500 GHz.
Note 5: Number of branches supported when used in Colorless Directional (CDA) configuration
(CCMD12 direct attach to ROADM OTS) is 8 (hardware ready to support 10 with 100% local add/drop
per degree and hardware ready to support 15 with 60 channel local add/drop per degree).
Note 6: Number of branches supported when used in Greenfield CDC configuration is 8.
Note 7: Number of branches supported when used in Brownfield CDC configuration is 7.
For further information on the RLA/WSS circuit packs listed above, refer to
Technical Publication 323-1851-102.6 Photonic Circuit Packs and Modules.
For detailed diagrams showing Colored Directional node examples, refer to

“Photonic node engineering and shelf configuration rules” on page 4-48.
This configuration can operate in fixed or flexible grid mode.
This configuration can operate with or without L0 CP/SNC provisioning in fixed

grid mode but must operate with L0 CP/SNC provisioning in flex grid mode.
For which OSRP instance is supported refer to the NTRN71AA, Control Plane
Application Guide - Layer 0 (Photonic).
Metro ROADM
Application space
The Metro ROADM feature enables Ciena to address the Metro DWDM
application space in a more cost-effective manner. This is done using existing
6500 ROADM and 2150/4200 passive modules hardware. The following
benefits are provided:
• ROADM footprint reduction and improved density.
— Using ROADM OTSs provisioned on 7-slot type 2 shelves with
integrated SPAP-2 w/2xOSC 2xSFP

— Reuse of 2110 DSCM family (half-width DSCMs may improve density

in certain applications)
— Small form-factor 2x1 WSS 100 GHz NTK553JB, 4x1 WSS 100 GHz
NTK553HA and 9x1 WSS 50 GHz NTK553FC/LA/LB
• The largest portion of the application space can be addressed via the 2x1
WSS 100 GHz NTK553JB and NTK552AA SLA combination.
— Higher span losses can use the MLA/MLA2/MLA2v/MLA3 variants
• Up to 4-degree branching can be addressed by the 4x1 WSS 100 GHz
NTK553HA.
— If more than 4 degrees are required then a 9x1 WSS 50 GHz is used
• Allows the reuse of 2150/4200 mux/demux filters. The 6500 OMD4 or
2150/4200 OMDF4 provide incremental growth options with minimum day
1 cost.
• DOC support is offered for 6500 OMD4 and 2150/4200 filters in ROADM
OTS subtypes using WSSs indicated above.
The 100 GHz wavelength plan used by the Metro ROADM feature is described
in “C-Band wavelength plans” on page 4-5.
• Up to 44 channels in the 100 GHz grid are possible using 6500 CMD44
modules.
• Up to 40 channels in the 100 GHz grid are possible, using 2150/4200
passive filter (OMDF4, OMDF8, BS5) combinations.
• Up to 36 channels in the 100 GHz grid are possible, using 6500 OMD4
modules (groups 1-9, 4 channels per group).
Careful planning is required when mixing 2150/4200 and 6500 passive 100
GHz filters. The per-wavelength validation feature enables software
prevention of in-use or non-viable (overlapping or skip) channels (see
“Deployment guidelines for mixing 2150/4200 and 6500 100 GHz filters” on
page 4-20).
Supported hardware and passive filter combinations
Hardware supported by the Metro ROADM feature is described below.
Table 3-3
Supported hardware for Metro ROADM configurations
PEC Description
WSS
NTK553JB Wavelength Selective Switch (WSS) 100 GHz w/OPM C-Band 2x1
(single slot-wide variant) circuit pack
NTK553HA Wavelength Selective Switch (WSS) 100 GHz w/OPM C-Band 4x1
(single slot-wide variant) circuit pack

Table 3-3
PEC Description
NTK553FC Wavelength Selective Switch (WSS) 50 GHz w/OPM C-Band 9x1

(double slot-wide variant) circuit pack
NTK553LA/LB Wavelength Selective Switch (WSS) Flex C-Band w/OPM 9x1 circuit pack
(double slot-wide variant)
Channel Mux/Demux
NTT862FA Enhanced 44 Channel Mux/Demux (eCMD44) 100 GHz C-Band module
NTT862AA 44 Channel Mux/Demux (CMD44) 100 GHz C-Band module
NTK504AA-AJ 4 Channel Optical Mux/Demux (OMD4) 100 GHz C-Band modules
B-720-0020-022 to 031 4-channel Optical Mux/Demux Filter (OMDF4) 100 GHz modules
B-720-0022-001 to 005 8 Channel Optical Mux/Demux Filter (OMDF8) 100 GHz modules
B-720-0020-032 CN-BS5, Band Splitter 100GHz C-Band Groups A, B, C, D, E module
Line Interface Module
NTK552AA Single Line Amplifier (SLA C-Band) circuit pack
NTK552BA Midstage Line Amplifier (MLA C-Band) circuit pack
NTK552FA Midstage Line Amplifier 2 (MLA2 C-Band) circuit pack
NTK552FB Midstage Line Amplifier 2 (MLA2 C-Band) with VOA circuit pack
NTK552GA Midstage Line Amplifier 3 (MLA3 C-Band) circuit pack
NTK552DA Line interface Module (LIM C-Band) circuit pack
Optical Service Channel (OSC)
NTK554BA 2xOSC circuit pack
NTK555NA/NB Shelf Processor w/Access Panel (SPAP-2) w/2xOSC 2xSFP circuit pack
NTK592NG (Note 1) OC-3/STM-1 CWDM 1511 nm SFP Module (0-34 dB span)
6500 Family of DSCMs
NTT870Ax (Type 1 NDSF)

NTT870Cx (Type 2 TWRS)
NTT870Ex (Type 3 TWc)
NTT870Gx (Type 5 ELEAF)

Table 3-3
PEC Description
2110 Family of DSCMs
B-955-0003-00x, 166-0203-9xy (NDSF)

B-955-0003-30x, 166-0403-90x (ELEAF)
Note 1: Other OSC SFPs can be used but the NTK592NG low power one is recommended.
Note that the hardware in the table above is primarily for ROADM
configurations using the 2150 family of channel mux/demux filters.
Supported filter combinations

Passive filters are deployed connected to a WSS switch port in Metro ROADM
configurations. The following filter combinations are supported
• BS5 with OMDF8s
• Cascaded OMD4s
• Cascaded OMDF4s
• Cascaded OMDF4s (up to 2) terminated with a CMD44
• Note that the OSCF 4200 OSC Filter is not supported since 6500 LIMs
incorporate this function
The choice of which passive filters to use for adding/dropping channels is
based on a combination of various factors including
• Favorable link budget analysis
• Density
• Scalability/Capacity
• First-in Cost
• Final Cost
High channel count Day 1 (OMDF4 or OMD4 appended with CMD44)
In scenarios with high-channel counts required day 1, the CMD44 100 GHz
module is recommended.
• Capacity: It is the only solution that provides 44 channel capacity
• Density: Best of all solutions (2U within rack)
• Link Budgets: Provides similar insertion loss on each port
• Cost: Lowest first-in cost when large channel count (approximately > 24)
deployed day 1

A filter cascade option also exists to deploy a lower channel count filter day 1,
such as an OMD4 or OMDF4, and then appending a CMD44 module in a day
2 scenario.
• For instance, after OMDF4 or OMD4 deployed initially
• Need to avoid using unavailable wavelengths on CMD44 if already used
on other filter
— Note: Software prevents provisioning wavelengths that are already
provisioned in an OTS (see “Per-wavelength validation feature” on
page 4-24).
Pay as you grow option (OMDF4)
Another filter cascade option is to use OMDF4s incrementally. This provides
the lowest first-in cost together with a ‘Pay as you grow’ cost profile.
• Capacity: Up to 40 channels
• Density Considerations:
— B-310-0142-001 2150 Passive Optical Multiplexer or 174-0040-900
PPC6 needed, each supports six half-width modules
— Need minimum of 2 x PPC6 modules for 40 channels
• Cost: first-in cost includes single OMDF4, thereafter incremental, adding
OMDF4s and PPC6s as necessary
• Link Budgets:
— Cascades should be limited to 4 filters to minimize link budget
impairments
— Cascade can be used on each WSS switch port
• Mixed Configurations also possible
— CMD44 can be added day 2 at the end of a cascade if more channels
are required
— OMDF8 can terminate a cascade as well
Pay as you grow option (BS5 with OMDF8)
Using a BS5 with OMDF8s is another recommended option for “Pay as you
grow” cost profiles.
• Capacity: Up to 40 channels
• Density Considerations:
— B-310-0142-001 2150 Passive Optical Multiplexer or 174-0040-900
PPC6 needed, each supports six half-width modules or 2 half-width
and two full-width modules
— OMDF8 (full-width module, can only occupy sub-slots 1&2 or 4&5)
— BS5 (half-width module)
— Need minimum of 3 x PPC6 modules for 40 channels

• Cost: First-In cost includes BS5 with single OMDF8, thereafter

incremental, adding OMDF8s and PPC6s as necessary
• Link Budgets:
— Need to account for loss through BS5
Metro ROADM operational considerations
The following operational considerations apply to the Metro ROADM feature.
These should be read in conjunction with “Colored Directional 1-way ROADM
Terminal” on page 4-51.
Operational considerations when using OMDF4/8 or OMD4 as CMD:

• TOADMs and ROADMs with OMDF4 or OMDF8 should not be on the
same network because of the different banding of sCMD4 and OMDF4/8
• If the network has ROADMs and TOADMs, ROADMs must use either
CMD44 or OMD4. The OMD4 and SCMD4 wavelength plans are
equivalent (with same skip channels).
• When scaling add/drop count beyond the filter’s capacity:
— If using OMD4 or OMDF4s, requires connection of new 4-channel filter
via upgrade ports (OMD4) or EXPR (OMDF4) ports, or new WSS
switch port
— If using BS5/OMD8s, requires addition of new OMDF8 on available
BS5 group port or new WSS switch port.
— Replacing OMD4/OMDF4/OMDF8/BS5 with a CMD44 will disrupt
unprotected traffic.
• The NTK589xx family of Narrow-band Tunable DWDM XFPs are not
aligned with the OMDF4/8 100 GHz channel plan.
Common equipment considerations for Metro ROADM configurations
From a common equipment and shelf-equipping rules perspective, Metro
ROADM configurations are:
• supported in the following 6500 shelf variants
— 14-slot
– NTK503AxE5, NTK503BxE5, NTK503CxE5,
– NTK503ADE5, NTK503BDE5, NTK503CDE5
– NTK503SA
— 32-slot (NTK603AA, NTK603AB)
— 7-slot (NTK503PA)
— 7-slot Type 2 (NTK503KA)
• Not supported on the NTK503NA/MA 2-slot shelf and the NTK503GA
14-slot Metro Front Electrical

• Supported on NTK503LA 2-slot type 2 shelves only when using the

following WSS variants:
— NTK553HA WSS 100 GHz w/OPM C-Band 4x1
— NTK553JB WSS 100 GHz w/OPM C-Band 2x1
• Do not have any special cooling, special power nor special Shelf
Processor requirements.
• If used, 2150/4200 filters must be equipped in sub-slots of the following
chassis types:
— B-310-0142-001 2150 Passive Optical Multiplexer chassis (6-slot)
— 174-0040-900 6-slot passive photonic chassis
— 174-0064-800 1RU 2150 3-slot chassis
• 2110/4200 DSCMs are equipped in the B-955-0004-002 (1U) DSCM shelf
— B-955-0003-001/2/3/4/5/6 (NDSF)
— 166-0203-90x (x=7,8,9,10,11,12,13,14,15,16,17) (NDSF)
— B-955-0003-302/4/6 (ELEAF)
— 166-0403-908/10/12/14/16/18 (ELEAF)
• 6500 DSCMs are housed in a DSCM drawer (NT0H57LA)
— NTT870AxE5 (Type 1 NDSF)
— NTT870CxE5 (Type 2 TWRS)
— NTT870ExE5 (Type 3 TWc)
— NTT870GxE5 (Type 5 ELEAF)
2110/4200 DCM modules do not support software-inventory capability.

Modules are either half or full-slot width relative to DSCM-shelf width.
• PEC B-955-0004-002 (rack mounted (1U) DSCM shelf). The shelf can
house one full-width DSCM module or two half-width modules.
• 2110/4200 DCM mechanicals are different from 6500 DSCM mechanicals
— Refer to 6500 product documentation for configuration & ordering
information
• 2110/4200 DCMs have LC interfaces while 6500 DSCMs use SC.
— Order the correct patch cords
For more details on common equipment, refer to Technical Publication
323-1851-102.1, Common Equipment.

Colored Directionless
Overview
The Colored Directionless application uses the standard equipment for the
backbone ROADM OTSs with the addition of a single DIA OTS or two DIA
OTSs connected to the backbone ROADM OTSs. This configuration allows
remotely redirecting a channel from a node to another direction as the
bandwidth requirements change, thus simplifying the planning of ROADM
nodes and networks. The DIA OTS is achieved using standard WSS, CMD,
BMD2 and amplifier components to create a directionally-independent access
point:
• In the transmit direction (Tx broadcast), the wavelengths from the CMD
are optically broadcast from each enabled switch (DIA WSS) to each
exiting direction (backbone WSS).
• In the receive direction (Rx select), each wavelength is selected from a
direction by each switch (DIA WSS).
A Colored Directionless add/drop structure supports directional control of 44,

64, 88 or 96 wavelengths, depending on the CMD type (see below). It can
connect to any ROADM OTS made of LC connector-based WSS or 5x1 RLA.
The figure below shows a 5-way ROADM node with one DIA terminal using a
100 GHz WSS.

Figure 3-2
Single DIA with 5-way ROADM
Hardware
The DIA OTS can be comprised of the following components:
• CMDxx:
— 50 GHz channel spacing: CMD44 50 GHz Blue, CMD44 50 GHz Red,
eCMD44 50 GHz Blue and eCMD44 50 GHz Red, or CMD96
— 100 GHz channel spacing: eCMD44 100 GHz
— 75 GHz channel spacing: CMD64

• BMD2: Only required when using the CMD44 50 GHz or eCMD44 50 GHz
• MLA, MLA2, MLA3 or XLA are the only LIMs supported for DIA
configurations
• WSS: WSSOPM 100 GHz 4x1, WSSOPM 100 GHz 5x1, WSSOPM
100 GHz 2x1, WSSOPM 50 GHz 2x1 and WSSOPM 50 GHz 9x1
Architecture
These are the different optical architectures that can be built for the DIA OTS:
• eCMD44 100 GHz -- MLA/MLA2/MLA3 -- WSSOPM 100 GHz 2x1
• CMD44 (Blue and/or Red) -- BMD2 -- MLA/MLA2/MLA3 -- WSSOPM
50 GHz 2x1
• CMD44 (Blue and/or Red) -- BMD2 -- MLA/MLA2/MLA3 -- WSSOPM
50 GHz 9x1
• eCMD44 (Blue and/or Red) -- BMD2 -- MLA/MLA2/MLA3 -- WSSOPM
50 GHz 2x1
• eCMD44 (Blue and/or Red) -- BMD2 -- MLA/MLA2/MLA3 -- WSSOPM
50 GHz 9x1
The number of directions a DIA can connect to depends on the number of DIA
OTSs (1 or 2) and the number of available ports on the backbone WSSs.
DIA node configurations

This section provides examples of typical DIA node configurations:
• Single DIA with 5-way branching, no local add/drop on the backbone
OTSs (see figure below). The DIA in this type of configuration allows you
to:
— Increase the route diversity (have one DIA add/drop at a node but have
the flexibility to send the wavelengths to multiple domains)
— Increase the high available links (allows the wavelength to always have
two valid paths)

Figure 3-3
Single DIA with 5-way branching: WSSOPM 100 GHz 5x1
Backbone OTSs
100
100
100
100
DIA OTS
eCMD 44
100
100
— the same applies for a WSSOPM 2x1 with 1-way branching only. If
local add/drop CMD44 are used on a WSSOPM 2x1 with a single DIA,
then no branching capability is possible.
• Dual DIA with 4-way branching, no local add/drop on the backbone OTSs
(see figure below). The Dual DIA in this type of configuration allows you to:
two valid paths)
— Increase the channel count (can use the same wavelength as active in
two directions)
— Provide redundancy on the functionality of the DIA OTS

Figure 3-4
Dual DIA with 4-way branching: WSSOPM 100 GHz 4x1 or WSSOPM 100 GHz 5x1
DIA1 Backbone OTSs

eCMD 44
100 100
100
100
DIA2
eCMD 44
100 100
— The same applies for a WSSOPM 2x1 with no branching capabilities

since the 2 switches are used for the DIAs
— 8-way Dual DIA OTS configuration is supported with a WSSOPM
50 GHz 9x1. To permit the 8-way branching capabilities, the DIA OTSs
must be connected to switch port 8 and 9 on the backbone WSSs.
• Dual DIA with 3-way branching, local add/drop on the backbone OTSs
(see figure below). The Dual DIA in this type of configuration allows you to:
two valid paths)
— Increase the channel count (can use the same wavelength as active in
two directions)
— Provide redundancy on the functionality of the DIA OTS
— Have a local add/drop specific traffic per domain

Figure 3-5
Dual DIA with 3-way branching and local add/drop: WSSOPM 100 GHz 4x1 or WSSOPM 100 GHz
5x1
DIA1
Backbone OTSs
eCMD 44
100 100
100
DIA2
eCMD 44
100 100
— 6-way Dual DIA OTS configuration is supported with a WSSOPM

50 GHz 9x1. To permit the 6-way branching capabilities, the DIA OTSs
must be connected to any of the switch ports 1 to 7 on the backbone
WSSs and the local add/drop CMD44s must be connected to the
switch port 8 and 9 on the backbone WSSs.

For detailed diagrams showing individual DIA OTSs, refer to:

• DIA OTS with 100 GHz 2x1 WSS, MLA, eCMD44
(see Figure 3-6 on page 3-22)
• DIA OTS with 100 GHz 9x1/1x5 WSS, MLA, eCMD44
• DIA OTS with 100 GHz 4x1 WSS, MLA, eCMD44
• DIA OTS with 50 GHz 2x1 WSS, MLA, BMD2, Red & Blue CMD44s (see
Figure 3-9 on page 3-23)
• DIA OTS with 50 GHz 9x1 WSS, MLA, BMD2, Red & Blue CMD44s (see

• DIA OTS with 50 GHz 9x1 WSS, MLA, BMD2, Red & Blue Enhanced
CMD44, 2-port OPM (see Figure 3-11 on page 3-25)
For detailed diagrams showing single DIA OTSs connected to 2-way ROADM
backbone OTSs refer to:
• Single DIA OTS with 2-way ROADM using 100 GHz 2x1 WSSs (see
• Single DIA OTS with 2-way ROADM using 50 GHz 2x1 WSSs
• Single DIA OTS with 2-way ROADM using 50 GHz 9x1 WSSs
• Single DIA OTS with backbone 2-way ROADM using 50 GHz 9x1 WSSs,
SRA and XLA hardware (see Figure 3-17 on page 3-31)
• Single DIA OTS with backbone 2-way ROADM using 50 GHz 9x1 WSSs,
ESAM and MLAx (MLA/MLA2/MLA3) hardware (see Figure 3-18 on page
3-32)
• Dual DIA OTS connected to 2-way ROADM node made of 5x1 RLAs (see
Figure 3-19 on page 3-33). Note that multiple combinations of the number
of degrees/DIA banks are supported:
— 5-degree ROADM + 1 DIA
— 4-degree ROADM + 2 DIAs
— 3-degree ROADM + 3 DIAs, and so on

Figure 3-6
Example DIA OTS (100 GHz 2x1 WSS, MLA, eCMD44)
DIA OTS
LC Ch 1 In eCMD44 MLA 6500 WSS 100 GHz

1
PEC: NTT862FA PEC: NTK552BA PEC: NTK553JA
2 Mon 1 (B Out)
Ch 1 Out 1
44 Channel MUX / DEMUX
LC Ch 2 In 2 1
Monitor 1
Mon 2 (A Out)
3 Monitor 2 OPM
OSC B In 2
4 3
Ch 2 Out
Common Out LC
90 Pad
Line A In
OSC A Out
Line A Out
4
17
Common In
 1: 2 Switch1 Out
Switch1 In
4
3
89 8 A 7
Common In
LC Ch 43 In Switch2 Out 6
85 5 B 6 Common Out
86
Line B Out Line B In 18 2:1 Switch2 In
5
Ch 43 Out
LC Ch 44 In
87
88
Ch 44 Out
This pad may be required for high

power Service circuit pack Can be MLA (NTK552BA),
transmitters, such as OM5K. Optical MLA2 (NTK552FA) or
Modeler determines whether pad is MLA3 (NTK552GA)
required and pad value.
Figure 3-7
Example DIA OTS (100 GHz 9x1/1x5 WSS, MLA, eCMD44)
DIA OTS WSS 100GHz 6500

PEC: NTK553EA
LC Ch 1 In eCMD44 MLA 6500 1
Monitor 1
1
PEC: NTT862FA PEC: NTK552BA OPM
2
2 Mon 1 (B Out) Monitor 2
Ch 1 Out 1
LC Ch 2 In 2 Switch1 In 3
3 Mon 2 (A Out)
4
OSC B In Switch1 Out
4 3
Ch 2 Out Common In Switch2 In 5
Common Out LC 4 17
OSC A Out
90 Pad 6
Line A In Line A Out Switch2 Out
89 8 A 7
Switch3 In 7
Common In
LC Ch 43 In 8
85 5 B 6 9:1 Switch3 Out
Line B Out Line B In
86 Switch4 In 9
Ch 43 Out
10
LC Switch4 Out

Ch 44 In
87 1: 5 Switch5 In 11
88
Ch 44 Out 12
Switch5 Out

Common Out
power Service circuit pack Can be MLA (NTK552BA), 18

1X5 w/upgd
13
WSS 100
Switch6 In
Modeler determines whether pad is MLA3 (NTK552GA) Switch7 In
14
required and pad value. Switch8 In

15
16
Switch9 In

Figure 3-8
Example DIA OTS (100 GHz 4x1 WSS, MLA, eCMD44)
Figure 3-9
Example DIA OTS (50 GHz 2x1 WSS, MLA, BMD2, Red & Blue CMD44s)
DIA OTS
CMD44 50GHz Blue
PEC: NTT862BA
Slot: 84
1 Ch1 In
1530.33nm
2
Ch1 Out
3 Ch2 In
1530.72nm
4
Ch2 Out
Common Out 90
MLA 6500
WSS 50 GHz
PEC: NTK552BA
Mon 1 (B Out) PEC: NTK553KC
1
Common In 89 BMD2 2
PEC: NTT862DA Mon 2 (A Out) Monitor 1
1
85 Ch43 In OSC B In Monitor 2 OPM
1546.92nm 3 2
86 3 Input 1
Ch43 Out 4
87
88
Ch44 In
1547.32nm
4
Output 1
Common
Out
2
Pad 8
Line A In
A
OSC A Out
Line A Out
7
7
Common In
 1: 2 Switch1 Out
Switch1 In
4
3

Ch44 Out
Input 2
5 Switch2 Out
Common 5 B 6 6
CMD44 50GHz Red 6
Output 2
In
1 Line B Out Line B In
8
Common Out
2:1 Switch2 In
5
PEC: NTT862BB
Slot: 85
1 Ch1 In
1547.72nm
2
Ch1 Out
3 Ch2 In
1548.11nm
4
Ch2 Out This pad may be required for high
Common Out 90
power Service circuit pack Can be MLA (NTK552BA) ,
Common In 89
Modeler determines whether pad is MLA3 (NTK552GA)
85 Ch43 In required and pad value.
1564.68nm
86
Ch43 Out
87 Ch44 In
1565.09nm
88
Ch44 Out

Figure 3-10
Example DIA OTS (50 GHz 9x1 WSS, MLA, BMD2, Red & Blue CMD44s)
DIA OTS
CMD44 50GHz Blue
PEC: NTT862BA
Slot: 84
1 Ch1 In
1530.33nm
2
Ch1 Out WSS 50 GHz
Ch2 In
3
1530.72nm
PEC: NTK553FA
4
Ch2 Out
Common Out 90
MLA 6500 1
Monitor 1
PEC: NTK552BA Monitor 2 OPM

2
Mon 1 (B Out)
1
Common In 89
BMD2 2
Switch1 Out 4
PEC: NTT862DA Mon 2 (A Out) Switch1 In 3
85 Ch43 In OSC B In
3
1546.92nm Switch2 Out 6
WSS 50 GHz
86 Input 1 Common In
Ch43 Out 3 4 21 Switch2 In
Common OSC A Out 5
87 Ch44 In Out
2
1547.32nm Output 1 Line A In Line A Out
9x1
88 4 Pad 8 A 7 Switch3 Out 8

Ch44 Out
Switch3 In 7
Input 2
5 Switch4 Out 10
Common 5 B 6
CMD44 50GHz Red 6
Output 2
In
1 Line B Out Line B In
Switch4 In 9
PEC: NTT862BB
Switch5 Out 12
Slot: 85
1 Ch1 In Switch5 In 11
1547.72nm
2

Ch1 Out Switch6 Out 14
1: 9
3 Ch2 In
Switch6 In 13
1548.11nm
4
Ch2 Out This pad may be required for high Common Out Switch7 Out 16
Common Out 90 power Service circuit pack Can be MLA (NTK552BA), 22

Switch7 In 15

Common In 89
Modeler determines whether pad is MLA3 (NTK552GA) 9:1
Switch8 Out (Drop1) 18
85 Ch43 In required and pad value. Switch8 In (Add1) 17

1564.68nm
86 Switch9 Out (Drop2) 20
Ch43 Out
87 Ch44 In Switch9 In (Add2) 19
1565.09nm
88
Ch44 Out

Figure 3-11
Example DIA OTS (50 GHz 9x1 WSS, MLA, BMD2, Red & Blue eCMD44, 2-port OPM)

Figure 3-12
Release 12.6
Backbone OTS 1 Backbone OTS 2
WSC WSC
WSC WSC 4 3
4 3
2x OSC
2x OSC
OSC OSC
OSC OSC 2 1
2 1
PEC: NTK554BA

OSC2 In
OSC1 In
OSC2 Out
OSC1 Out
PEC: NTK554BA
OSC2 In
OSC1 In
OSC2 Out
OSC1 Out
1
1
2
2
1
1
2
2
WSS 100 GHz WSS 100 GHz
PEC: NTK553JA
PEC: NTK553JA
MLA
PEC: NTK552BA 6500 Monitor 1 MLA
Monitor 1 1
Mon 1 (B Out) 1 OPM Monitor 2 6500 PEC: NTK552BA
1 2
Monitor 2 OPM Mon 1 (B Out)
2 1
2
Mon 2 (A Out)

Switch1 In Common Out 2
OSC B In Switch1 Out 3 18 Mon 2 (A Out)
3 Common In 4
1 : 2
17 Switch1 Out
1 : 2 Switch1 In 4 OSC B In
4 3 3
OSC A Out
4
Line A In Line A Out Switch2 In OSC A Out
8 A 7 5
Switch2 Out 6 Switch2 Out Common In Line B In Line B Out
Common Out 6 17 6 B 5
18 Switch2 In
5
2:1
2:1
5 B 6
7 A 8
Can also be NTK553EA/HA or

Can also be NTK553EA/HA or NTK553JB
NTK553JB
DIA OTS
LC Ch1 In eCMD44 MLA WSS 100 GHz

1 6500
PEC: NTT862FA PEC: NTK552BA PEC: NTK553JA
2 Mon 1 (B Out)
Ch1 Out 1
LC 2 Monitor 1
Ch2 In 1
3 Mon 2 (A Out)
Monitor 2 OPM
OSC B In 2
4 3
Ch2 Out
Common Out LC 4 Switch1 Out
OSC A Out Common In 4
Example - Single DIA OTS with 2-way ROADM (100 GHz 2x1 WSSs)
90 Pad 17 1 : 2
Line A In Line A Out Switch1 In
89 8 3
A 7
Common In
LC Ch 43 In Switch2 Out 6
85 5 B 6 Common Out
Line B Out Line B In 18 Switch2 In
2:1 5
86

Ch 43 Out
LC Ch 44 In
87
88
Ch 44 Out

power Service circuit pack Can also be NTK552FA or Can also be NTK553EA/HA or
transmitters, such as OM5K. Optical NTK552GA NTK553JB
Modeler determines whether pad is
required and pad value.

October 2019
Figure 3-13

WSC WSC
WSC WSC 4 3
4 3
Figure 3-14
2x OSC
Release 12.6
2x OSC
OSC OSC
OSC OSC 2 1
2 1
PEC: NTK554BA
OSC2 In
OSC1 In
OSC2 Out
OSC1 Out
PEC: NTK554BA
OSC2 In
OSC1 In
OSC2 Out
OSC1 Out
1
1
2
2
2
2
1
1
WSS 100GHz WSS 100GHz
6500 6500 PEC: NTK553EA
PEC: NTK553EA
Monitor 1
Monitor 1 1
1
OPM OPM
2

2 Monitor 2
Monitor 2
MLA
6500 3 Switch1 In MLA
PEC: NTK552BA Switch1 In 3
Mon 1 (B Out) 4 6500 PEC: NTK552BA
1 4 Switch1 Out
Switch1 Out Mon 1 (B Out)
2 1
Common In 5 Switch2 In Common In
Mon 2 (A Out) Switch2 In 5 17
17 2
OSC B In 6 6 Mon 2 (A Out)
3 Switch2 Out Switch2 Out
OSC B In
4 Switch3 In 3
OSC A Out Switch3 In 7 7
4
Line A In Line A Out 8 8 OSC A Out
8 A 7 Switch3 Out Switch3 Out
9:1 9:1 Line B In Line B Out
Switch4 In 6 B 5
Switch4 In 9 9
5 6 10 10
B Switch4 Out Switch4 Out
7 A 8
Switch5 In 11 11 Switch5 In 1 : 5 Line A Out Line A In
1 : 5

12 12
Switch5 Out Switch5 Out
Common Out Common Out

18 18
13 13
Switch6 In Switch6 In
14 14
15 15
Switch8 In Switch8 In Example of a Local Add/Drop
WSS 100
WSS 100
16
1X5 w/upgd
16
1X5 w/upgd
Switch9 In Switch9 In CMD44 in one direction
Can also be NTK553HA or

NTK553JA/JB Can also be NTK553HA or
NTK553JA/JB
eCMD44 In 1 Ch LC
1
FA862NTT :PEC
2
Out 1 Ch
DIA OTS WSS 100GHz In 2 Ch LC
PEC: NTK553EA 6500 3
Monitor 1 4
LC Ch 1 In eCMD44 MLA 1 Out 2 Ch
1 6500 OPM LC Common Out
PEC: NTT862FA PEC: NTK552BA 2 90
2 Mon 1 (B Out) Monitor 2
Ch 1 Out 1 89
LC Ch 2 In 2 Switch1 In 3 Common In
3 Mon 2 (A Out) LC
4 In 43 Ch
OSC B In Switch1 Out 85
4 3
Ch 2 Out Common In Switch2 In 5 86
XUMED / XUM lennahC 44
Common Out LC 4 17 Out 43 Ch

Example - Single DIA OTS with 2-way ROADM (100 GHz 9x1/1x5 WSSs)
OSC A Out
90 Pad 6
Line A In Line A Out Switch2 Out In 44 Ch LC
89 8 A 7 87
Switch3 In 7
Common In
LC 88
Ch 43 In 8 Out 44 Ch
85 5 B 6 Switch3 Out
Line B Out Line B In 9:1
86 Switch4 In 9

Ch 43 Out
10
LC Ch 44 In Switch4 Out
87 Switch5 In 11
88
1 : 5
Ch 44 Out 12
Switch5 Out

Common Out These 3 Other switches can be
power Service circuit pack 18
Can also be NTK552FA or fibered to other OTS with 100GHz
transmitters, such as OM5K. Optical 13
NTK552GA Switch6 In WSS ROADM terminals.
Modeler determines whether pad is 14
Switch7 In
required and pad value. 15
Switch8 In
WSS 100
16
1X5 w/upgd
Switch9 In

October 2019
Figure 3-15
Release 12.6
WSC WSC WSC WSC
4 3 4 3
2x OSC
2x OSC
OSC OSC OSC OSC
2 1 2 1
PEC: NTK554BA
PEC: NTK554BA
OSC2 In
OSC1 In
OSC2 In
OSC1 In
OSC2 Out
OSC1 Out
OSC2 Out
OSC1 Out
1
1
2
2
1
1
2
2

MLA WSS 50 GHz WSS 50 GHz MLA
PEC: NTK552BA 6500 PEC: NTK553KC
Slot 1-10 PEC: NTK553KC 6500 PEC: NTK552BA
Mon 1 (B Out) Mon 1 (B Out)
1 1
2 Monitor 1 Monitor 1 2
1 1
Monitor 2 OPM OPM Monitor 2
OSC B In 2 2 OSC B In
3 3
4 Switch1 Out Switch1 In Common Out 4
OSC A Out Common In 4 3 8 OSC A Out
7 1 : 2 1 : 2
Line A In Line A Out Switch1 In Switch1 Out Line B In Line B Out
8 A 7 3 4 6 B 5
Switch2 Out 5 Switch2 In

5 6 6 7 A 8
B Common Out Line A Out Line A In
Line B Out Line B In 8 Switch2 In 6 Switch2 Out Common In
2:1 5 2:1 7

Can also be NTK553FA, Can also be NTK553FA,
NTK553FC, or NTK553LA NTK553FC, or NTK553LA
CMD44 50GHz Blue DIA OTS

PEC: NTT862BA
Slot: 84
1 Ch1 In
1530.33nm
2
Ch1 Out
3 Ch2 In
1530.72nm
4
Ch2 Out
Common Out
MLA WSS 50 GHz
90 6500
PEC: NTK552BA
Mon 1 (B Out) PEC: NTK553KC
Common In 89 1
BMD2 2
PEC: NTT862DA Mon 2 (A Out) Monitor 1
1
85 Ch43 In OSC B In Monitor 2 OPM
1546.92nm 3 2
86 Input 1
3

Ch43 Out 4
Ch44 In Common OSC A Out Switch1 Out
87 2 Common In 4
1547.32nm Output 1 Out 7
4 Line A In Line A Out 1 : 2 Switch1 In
88 Pad 8 A 7 3
Ch44 Out
Input 2 
5 Switch2 Out
Common 5 B 6 6
1 Line B Out Line B In Common Out
CMD44 50GHz Red In 8 Switch2 In
Output 2 2:1 5
6
PEC: NTT862BB
Slot: 85
1 Ch1 In
1547.72nm
2
Ch1 Out
3 Ch2 In
1548.11nm
4 This pad may be required for high
Ch2 Out Can also be NTK552FA or
Common Out 90
power Service circuit pack NTK552GA
transmitters, such as OM5K. Optical
Common In 89
Modeler determines whether pad is
85 Ch43 In required and pad value.
1564.68nm
86

Ch43 Out
87 Ch44 In
1565.09nm
88
Ch44 Out

October 2019
Figure 3-16
NTK553FC, or NTK553LA
Can also be NTK553KC,
1:9
NTK553FC, or NTK553LA
Can also be NTK553KC,
1:9
1:9
Can also be NTK552FA or
NTK552GA

Figure 3-17
Single DIA OTS with 2-way ROADM using 50 GHz 9x1 WSSs, SRA and XLA hardware

Figure 3-18
Single DIA OTS with 2-way ROADM using 50 GHz 9x1 WSSs, ESAM (or SAM) and MLAx hardware

Figure 3-19
Dual DIA OTS with 2-way ROADM using 5x1 RLA

Unsupported DIA configurations

The components listed below are not supported in a DIA OTS and are blocked
by software:
— SCMD4
— DSCM
— CMD44 100 GHz (must be a eCMD44 100 GHz)
— BMD2 with CMD44 100 GHz or eCMD44 100 GHz
— The (1-slot wide) NTK553KA 50 GHz 2x1 WSS w/OPM is only
supported in configurations that use a maximum of 2 OTSs. This
means the NTK553KA cannot be used in a DIA configuration
backbone OTS or DIA OTS.
Colorless Directionless
Overview
Colorless Directionless applications consist of colorless hardware (forming a
COADM OTS) that can be appended to a DIA setup, which itself connects to
one or more backbone ROADM OTS.
Hardware
The COADM OTS uses the following hardware:
• NTK508FA CCMD12 circuit pack
• One of the following SMD circuit packs:
— NTK553GA Selective Mux/Demux (SMD) 50 GHz C-Band 8x1
— NTK553GB Selective Mux/Demux (SMD) Flex C-Band 8x1
The DIA OTS uses the following hardware:

• One of the following LIM circuit packs:
— NTK552BA MLA
— NTK552FA MLA2
— NTK552GA MLA3
— NTK552KA XLA
• One of the following WSS circuit packs:
— NTK553FA 50 GHz WSS 50 GHz w/OPM C-Band 9x1
— NTK553FC 50 GHz WSS w/OPM C-Band 9x1
— NTK553LA/LB 50 GHz WSS w/OPM C-Band 9x1 Gridless
The ROADM OTS uses the following hardware:

• One of the following WSS/RLA circuit packs:


— NTK553RA 5x1 RLA
• LIM circuit pack as defined by OnePlanner (MLA, MLA2, MLA3,
SRA/ESAM/SAM-XLA or ESAM/SAM-MLA3). The RLA can be
complemented by ESAM or SRA.
The CCMD12 functions as a power combiner/splitter with an embedded EDFA

in the ingress and egress direction. In other words, the circuit pack provides
up to 12 channel mux/demux ports without a filter function. The demux filter
function normally provided in the egress direction is now transferred to the
C-Band tunable wavelength-selective transponder interface, which has the
ability to select one of up to 12 different wavelengths incident on the
balanced-PIN receiver.
The NTK553GA/GB SMD provides two independently controlled wavelength

selective switches (WSS) which can select each of the 88 channels when
using NTK553GA or 96 channels when using NTK553GB in the 6500 50 GHz
C-band plan from any of its 8 ports that are connected to individual CCMD12
circuit packs. The SMD can therefore provide blocking of channels on
unselected ports of either the mux or demux path, or per-channel power
adjustment (attenuation) of all DOC-managed channels in either the mux or
demux path whose pixels are unblocked.
The NTK553GB Flex SMD is similar to the NTK553GA SMD but with the
following differences:
• Typical (maximum) power consumption
• 96 channel support
• Flexible-grid capable (to be supported in a future release)
• Technical specification differences
The deployment of the colorless directionless OADM is advantageous in

scenarios where, due to wavelength contention in a network, an operator
decides to remove an existing wavelength and reuse another wavelength. The
benefit is that the change can all be done remotely. With fibering already setup
in advance between colorless transponder interfaces and their associated
CCMD12 ports, an operator no longer needs to re-visit a site to reconnect a
colorless Tx/Rx interface to a new mux/demux coupler port. Along with the
partner DIA OTS, the COADM OTS allows the operator to direct the new
wavelength towards any backbone direction.

The Colorless Directionless configuration relies on existing transponder

hardware:
• Colorless-capable transponders are mandatory for channels
added/dropped at a CCMD12.
An overview of the transponder interfaces offered by Ciena that are
compatible with colorless line systems is provided in “Supported
transponders for colorless and CDC line systems” on page 3-107.
Figure 3-20
COADM OTS detail
For further information on Colorless line system hardware, refer to the

Technical Publications 323-1851-102.6, Photonic Circuit Packs and Modules.
Architecture
Two main types of colorless directionless configurations are supported:
• Single COADM/DIA add/drop bank connected to multiple backbone
ROADM OTSs. A 3-way backbone ROADM OTS node example is shown
in Figure 3-21 on page 3-38.
• Redundant COADM/DIA add/drop banks connected to multiple backbone
ROADM OTSs. When using 9x1 WSS in the ROADM OTSs, up to five
add/drop banks can be connected to multiple backbone ROADM OTSs. A
4-way ROADM node with dual add/drop banks example is shown in Figure
3-22 on page 3-39.

When only using 9x1 WSS for ROADM degrees, up to 8-way ROADM
branching is possible for either single or dual COADM/DIA add/drop bank
configurations indicated above, if connected to the backbone WSS amplified
Switch ports. If connected to the unamplified Switch ports, then the number of
degrees is x, where x = (8 – attached DIA/COADM banks to WSS unamplified
drop ports).
When only using 5x1 RLA for ROADM degrees, up to x degrees are
supported, where x = (6 – attached add/drop banks to RLA).
This configuration can operate in fixed or flexible grid mode.

For detailed diagrams refer to:

• COADM OTS connected to DIA with 1-way ROADM OTS made of 9x1
WSS (Figure 3-23 on page 3-40)
• COADM OTS connected to DIA with 2-way ROADM OTS made of 5x1
RLA (Figure 3-24 on page 3-41)
Additional rules are listed under “Colorless Directionless” on page 4-113.
Unsupported COADM OTS configurations

The following COADM OTS configurations are not supported:
• DSCMs and pads provisioning within the COADM OTS
• Cascaded SMDs
• Remote Colorless OADM, i.e., colorless transponders in a shelf with a
different site ID
— i.e. Colorless transponders cannot be remote. Remote CCMD12 is not
supported.
• Colored transponders on a CCMD12
• Mixing of Colorless OADM configuration (consisting of COADM and DIA
OTS) with another DIA configuration (i.e., DIA OTS only) on a single
backbone WSS, meaning
— The first COADM OTS requires a partner DIA OTS on the backbone
ROADM OTS WSS and this is allowed.
— A second DIA OTS on the same backbone ROADM OTS WSS
providing a DIA-only function only, is not allowed.

Figure 3-21
3-way ROADM node using 9x1 WSS with single COADM/DIA add/drop bank

Figure 3-22
4-way ROADM node using 9x1 WSS with dual COADM/DIA add/drop banks

Figure 3-23
1-way ROADM node with single COADM/DIA add/drop bank example using 9x1 WSS

Figure 3-24
2-way ROADM node with dual COADM/DIA add/drop banks example using 5x1 RLA

Colorless Directional or Colorless Direct Attach (CDA)

Overview
The Colorless Directionless configuration outlined in the previous section is
directionless since the COADM OTS is connected through the DIA OTS to
multiple backbone ROADM OTS directions.
A comparison between a Colorless Directionless OADM and a Colorless

Directional OADM using COADM OTS directly attached to a ROADM OTS is
Hardware
The COADM OTS connects to a backbone ROADM OTS that can use the
following WSS hardware:
• NTK553FA 50GHz WSS w/OPM C-Band 9x1 (3-slots)
• NTK553KC 50GHz WSS w/OPM C-Band 2x1 (3-slots)
• NTK553KA 50GHz WSS w/OPM C-Band 2x1 (1-slot)
• NTK553FC 50GHz WSS w/OPM C-Band 9x1 (2-slots)
• NTK553LA/LB Flex WSS w/OPM C-Band 9x1 (2-slots)
• NTK553RA 5x1 RLA (2 slots)
— The RLA can be complemented by ESAM or SRA.

• NTK508FA 12-Channel Colorless Mux/Demux (CCMD12 C-Band)
• NTK553GA Selective Mux/Demux (SMD) 50 GHz C-Band 8x1 or
NTK553GB Selective Mux/Demux (SMD) Flex C-Band 8x1
• NTK552FA MLA2 or NTK552GA MLA3 or NTK552KA XLA
— Optional, dependent on the link budget design. Use of the LIM
depends upon the ROADM OTS WSS type used.
Attention: When connected to 5x1 RLA, the COADM OTS does not
support a LIM. The SMD connects directly to the RLA.
The CDA with COADM OTS direct attach architecture also relies on existing
amplifier and transponder hardware:
• The ROADM OTS which has the COADM OTS direct attach can use an
XLA with SRA (or ESAM/SAM) combination or a LIM (MLA2 or MLA3) with
or without ESAM/SAM combination. The MLA2 limits the channel count to
88 channels.


added/dropped at a CCMD12. An overview of the transponder interfaces
offered by Ciena that are compatible with colorless line systems is
provided in “Supported transponders for colorless and CDC line systems”
on page 3-107.
Architecture
Using 9x1 WSS in ROADM OTS
For examples of the COADM OTS direct attach to a ROADM OTS equipped
with 9x1 50 GHz WSS or 9x1 Flex WSS, refer to Figure 3-26 on page 3-46
(1-way ROADM Terminal) and Figure 3-27 on page 3-47 (2-way ROADM
node).
• This configuration is Colorless fixed or flex grid, provided it uses the
NTK553GB 8x1 FlexSMD and NTK553LA/LB 9x1 Flex WSS.
• Illustrations show a single COADM OTS connected to a given ROADM
degree, allowing 96 NMCs to be added/dropped. An additional COADM
OTS increases this number to 128 NMCs per degree.
• The maximum number of supported ROADM degrees is 7 (1 local
add/drop, 6 passthrough).
• It is possible to use the ROADM OTS amplified drop ports to connect the
COADM OTS as shown in Figure 3-28 on page 3-48. In this case there is
no need to use an amplifier in the COADM OTS.
— The WSS EDFA drop gain is then automatically set to its minimum
gain to avoid power saturation. The user cannot change this value.
Using 2x1 WSS in ROADM OTS

For an example of the COADM OTS direct attach to a ROADM OTS equipped
with 2x1 50 GHz WSS and existing CMD44 red/blue local add/drop traffic,
refer to Figure 3-29 on page 3-49 (1-way ROADM Terminal).
• This is a Colorless Fixed grid configuration
— An MLA2 or MLA3 is used in the COADM OTS as dictated by the link
design
— The SMD or FlexSMD can be used in the COADM OTS, but the
application is always fixed grid
• The COADM OTS LIM is connected to the NTK553KA 2x1 50 GHz WSS
passthrough ports 3 and 4. These ports have higher insertion loss,
necessitating use of the COADM OTS LIM.
• Local add/drop traffic on the NTK553KA is via ports 5 and 6.
• This is a terminal site configuration only, without passthrough traffic.

For an example of the COADM OTS direct attach to a ROADM OTS equipped
with 2x1 50 GHz WSS as part of a 2-way ROADM site with passthrough traffic,
refer to Figure 3-30 on page 3-50.
• The COADM OTS SMD is connected to NTK553KA 2x1 50 GHz WSS
local add/drop port (ports 5 and 6.)
— The local add/drop port has lower insertion loss, hence the LIM is not
needed in the COADM OTS.
— Express traffic goes through ports 3 and 4.
• This configuration can operate with or without L0 CP/SNC provisioning in
fixed grid mode but must operate with L0 CP/SNC provisioning in flex grid
mode. For which OSRP instance is supported refer to the NTRN71AA,
Control Plane Application Guide - Layer 0 (Photonic).
Using 5x1 RLA in ROADM OTS

For examples of the COADM OTS direct attach to a ROADM OTS equipped
with 5x1 RLA, refer to Figure 3-31 on page 3-51 (2-way ROADM node).
• This configuration is Colorless fixed or flex grid, but regardless of the
control mode, the only supported SMD is the NTK553GB 8x1 FlexSMD.
• The maximum number of supported ROADM degrees is 5 (1 local
add/drop, 4 passthrough).
• The RLA Switch port usage recommendations are as follows:
— Use Switch port 5 to connect the COADM bank;
— Use Switch port 1 to connect the first ROADM degree, then Switch
port 2 to connect the second one, and so on.
Refer to “Colorless Directional or Colorless Direct Attach (CDA)” on page

4-114 for more engineering rules.
Unsupported CDA with COADM direct attach configurations

The following CDA with COADM OTS direct attach configurations are not
supported:
• DSCMs and pads provisioning within COADM OTS
• Remote CCMD12
• Non-coherent transponders on a CCMD12
• COADM OTS directly connected to a backbone 6500 LIM (MLAx)
• COADM OTS directly connected to a CPL ROADM OTS
• Mixing of COADM OTS direct attach with either (a) Colorless OADM
configuration (COADM + DIA OTS) or (b) DIA configuration (DIOADM) on
a single backbone WSS

Figure 3-25
Colorless Directionless OADM compared to Colorless Directional OADM with COADM OTS direct
attach

Figure 3-26
CDA configuration: COADM OTS direct attach to 9x1 WSS based ROADM OTS (1-way node)

Figure 3-27

Figure 3-28
CDA configuration: COADM OTS directly attached to 9x1 WSS amplified ports

Figure 3-29

Figure 3-30

Figure 3-31
CDA configuration: COADM OTS direct attach to 5x1 RLA 2-way ROADM
Colorless Directionless, Colored Directionless and Colored

Directional using 9x1 WSS
Overview
This application mixes 3 different functions: a colorless DIA bank made of DIA
and COADM OTSs provides Colorless Directionless capabilities to the site,
while Colored Directionless and Colored Directional capabilities are fulfilled
via a Colored DIA bank and direct attach CMD44s, respectively. This mix is
likely to arise in a scenario where a photonic configuration, initially Colored
(Directionless and/or Directional), is upgraded with a Colorless DIA bank to
support 56 GBaud transponders.

The Colorless Directionless, Colored Directionless and Colored Directional

uses all the previous configurations but interworking into one configuration to
allow easy flexibility to expand deployed configurations.
Hardware
SRA/ESAM/SAM-XLA or ESAM/SAM-MLA3).
• CMD44 filters for the Colored Directional:
— NTT862BX xCMD44 50GHz (Blue or Red)
— NTT862DA BMD2: Only required when using the xCMD44 50 GHz
Blue and xCMD44 50 GHz Red

• One of the following LIM circuit packs:
— NTK552BA MLA
— NTK552FA MLA2
— NTK552GA MLA3
— NTK552KA XLA
— CMD44: CMD44 50 GHz Blue, CMD44 50 GHz Red
• CMD44 filters for the Colored Directionless:
— NTT862Bx xCMD44 50GHz (Blue or Red)

• NTK508FA CCMD12 circuit pack
• One of the following SMD circuit packs:
— NTK553GA Selective Mux/Demux (SMD) 50 GHz C-Band 8x1

— NTK553GB Selective Mux/Demux (SMD) Flex C-Band 8x1

Architecture
Figure 3-32 on page 3-55 illustrates the configuration. Although a 2-way
ROADM is shown, more degrees are supported in this release (see rules
section below for calculation).
Engineering rules and guidelines

Follow these engineering rules and guidelines when deploying this
configuration:
• This configuration can only operate in flexible grid mode.

— All WSSs and SMDs involved must be flex capable.
• The maximum number of Colorless DIA banks per node is 2.
— You can deploy up to 8 CCMD12s per Colorless DIA bank (96 NMCs).
— The Colorless DIA banks connect to backbone WSS unamplified drop
ports (SW1 through SW7).
— On the DIA WSS, all SW ports are allowed to connect to the backbone
WSS, i.e. amplified or unamplified.
– If amplified, the WSS drop EDFA gain is left at default value (6 dB).
Using the amplified ports on the DIA WSS has an OSNR impact
and is not recommended unless required.
— The amplifier in the bank can be MLA, MLA2, MLA3 or XLA.
Remember though that the MLA and MLA2 have a narrower passband
than MLA3 and XLA.
• The maximum number of Colored DIA banks per node is 2.
— The Colored DIA banks connect to backbone WSS unamplified drop
ports (SW1 through SW7) or amplified drop ports (SW8 and SW9).
– The amplified drop ports can only be used if no CMD44 is
connected to any WSS amplified drop port.
— On the DIA WSS, all SW ports are allowed to connect to the backbone
WSS, i.e. amplified or unamplified.
– If amplified, the WSS drop EDFA gain is left at default value (6 dB).
— The amplifier in the bank can be MLA, MLA2, MLA3 or XLA.
— As the DIA banks and ROADM degrees “compete” for the backbone
WSS unamplified SW ports, the number of degrees supported
depends on the number of banks according to this rule:
Number of degrees = 8 – attached DIA banks to backbone WSS
• CMD equipment must be provisioned in the same shelf as the backbone
WSS it connects to.

• This configuration can operate in fixed or flexible grid mode

Unsupported Colorless Directionless, Colored Directionless and Colored

Directional configurations
The following Colorless Directionless, Colored Directionless and Colored
Directional configurations or features are not supported:
• refer to the Colorless Directionless “Unsupported COADM OTS
configurations” on page 3-37
• refer to the Colored Directionless “Unsupported DIA configurations” on
page 3-34
• WLAi-56 not supported on CMD44 50 GHz Red and Blue modules

Figure 3-32
Colorless Directionless, Colored Directionless and Colored Directional using 9x1 Flex WSS
(2-way ROADM example, with XLA/SRA in ROADM OTSs)

Low channel count Colorless Directionless

Overview
The Colorless Directionless application described in section “Colorless
Directionless” on page 3-34 is designed to support 88 or 96 channels. When
only a few channels are needed, a simplified architecture necessitating less
circuit packs and smaller shelf footprint can be deployed, called the low
channel count Colorless Directionless node configuration.
A comparison between a Colorless Directionless OADM and a low channel

count Colorless Directionless OADM is shown in Figure 3-33 on page 3-58.
The LIM and SMD are removed, so that the directionless function is fulfilled by
the WSS that used to be in the DIA OTS, and the colorless and amplification
functions are fulfilled by the CCMD12 (note that the WSS and CCMD12
forming the add/drop bank are not part of an OTS). This arrangement reduces
the amount of circuit packs at the node, at the expense of a reduction to 12
channels maximum per add/drop bank.
Hardware
• One of the following WSS/RLA circuit packs:
— NTK553RA 5x1 RLA
SRA/ESAM/SAM-XLA or ESAM/SAM-MLA3). The RLA can be
complemented by ESAM or SRA.
The add/drop bank uses the following hardware:

— In this release, the 5x1 RLA cannot be used in the add/drop bank.
• The add/drop bank uses the following hardware:
— NTK508FA 12-Channel Colorless Mux/Demux (CCMD12 C-Band)
Colorless-capable transponders are mandatory for channels added/dropped

at a CCMD12. An overview of the transponder interfaces offered by Ciena that
are compatible with colorless line systems is provided in “Supported
The allowed Shelf Processors are the SP-2 variants NTK555EA, NTK555CA
or NTK555FA.

Architecture
The low channel count Colorless Directionless (CD) node can be a terminal
(Figure 3-34 on page 3-59), a 2-way ROADM node (Figure 3-35 on page 3-60
and Figure 3-36 on page 3-61) or a ROADM node of higher degree (see
calculation further down). Other characteristics are summarized below:
• This configuration can operate in fixed or flexible grid mode.
• Supports up to four Low Channel Count add/drop banks at one site.
• Channels originating at a low channel count CD node can be dropped to
any node configuration.
• Channels originating on any node configuration can be dropped at a low
channel count CD node.
• It is possible to add the WSS + CCMD12 add/drop bank to an existing
system (brownfield deployment).
• The low channel count CD node can be part of a mesh-restorable L0
Control Plane network.
• When only using 9x1 WSS for ROADM degrees:
— Up to x degrees are supported, where x = (8 – attached add/drop
banks to backbone WSS unamplified drop ports)
– The maximum is thus 8, when add/drop banks connect to
backbone WSS amplified drop ports, and no CMD44 connects to
these drop ports.
— Up to four add/drop banks can be deployed.
– For example, a 4-way ROADM node would have each degree
connect to the other 3 degrees, and to each of the 4 add/drop
banks.
• When only using 5x1 RLA for ROADM degrees:
— Up to x degrees are supported, where x = (6 – attached add/drop
banks to RLA)
— Up to four add/drop banks can be deployed.
Refer to “Low channel count Colorless Directionless” on page 4-115 for

additional engineering rules.

Unsupported low channel count CD configurations

The following low channel count CD configurations or features are not
supported:
• Tx Optical Loopback procedure, because of the absence of the SMD and
its loopback capability.
Figure 3-33
Colorless Directionless OADM compared to Low channel count Colorless Directionless

Figure 3-34
Low channel count Colorless Directionless Terminal node (OSC not shown for simplicity)

Figure 3-35
Low channel count Colorless Directionless 2-way ROADM node with two add/drop banks (using
9x1 WSS)

Figure 3-36
Low channel count Colorless Directionless 2-way ROADM node with two add/drop banks (using
5x1 RLA)
Low channel count Colorless Directionless and Colored Directional

using 9x1 WSS
Overview
When only a few channels are needed for protection and other channels are
needed for point-to-point configurations, a simplified architecture
necessitating less circuit packs and smaller shelf footprint can be deployed,
called the Low Channel Count Colorless Directionless and Colored
Directional node configuration.

This configuration is the same as “Low channel count Colorless Directionless”

on page 3-56 with colored directional CMD44 connected to the ROADM
backbone OTSs. This arrangement allows a 12 channels maximum per
add/drop bank on the DIA OTS and up to 88 channels on the local add/drop
CMD44 50GHz filters.
Hardware
SRA/ESAM/SAM-XLA or ESAM/SAM-MLA3).
• CMD44 filters for the Colored Directional:
— NTT862Bx xCMD44 50GHz (Blue or Red)

• The add/drop bank uses the following hardware:
— NTK508FA 12-Channel Colorless Mux/Demux (CCMD12 C-Band)

at a CCMD12. An overview of the transponder interfaces offered by Ciena that
are compatible with colorless line systems is provided in “Supported
Finally, the allowed Shelf Processors are the SP-2 variants NTK555EA,
NTK555CA or NTK555FA.
Architecture
The low channel count Colorless Directionless (CD) node can be a terminal ()
or up to 8-way ROADM node. Refer to Figure 3-37 on page 3-63 for a 2-way
ROADM with a low channel count Colorless Directionless (CD) and colored
directional. Other characteristics are summarized below:
• Refer to the Low Channel Count Colorless Directionless configuration
“Architecture” on page 3-57

• CMD44 50 GHz can be connected to backbone WSS unamplified drop

ports (together with an XLA/MLA3) or to backbone WSS amplified drop
ports.
• The DIA WSS can connect to the backbone WSS unamplified drop ports
or amplified drop ports. The amplified drop ports can only be used if no
CMD44 is connected to any WSS amplified drop port.
Unsupported low channel count CD configurations

The following low channel count CD configurations or features are not
supported:
• Refer to the Low Channel Count Colorless Directionless configure
“Unsupported low channel count CD configurations” on page 3-63
Figure 3-37
Low channel count Colorless Directionless 2-way ROADM node with colored add/drop

Colorless Directional or Colorless Direct Attach (CDA) using 20x1

WSS, FIM Type 4, FIM Type 5 and FIM Type 6
Overview
The CDA with CCMD12 direct attach configuration provides colorless
directional functionality using the 20x1 WSS and CCMD12 circuit packs along
with different types of FIMs (Fiber Interconnect Modules).
Hardware
• NTK553MA WSS 20x1: this WSS is equipped with 20 switch ports.
Compared to other WSSs with fewer switch ports, it also has the
particularity of having a wavelength-selective switch in the demux
direction instead of a passive splitter. This adds selective functions to the
demux direction, essential for the CDA with CCMD12 direct attach
configuration.
• NTK508FA CCMD12: The CCMD12 functions as a power
combiner/splitter with an embedded EDFA in the ingress and egress
direction. In other words, the circuit pack provides up to 12 channel
mux/demux ports without a filter function. The demux filter function
normally provided in the egress direction is now transferred to the C-Band
tunable wavelength-selective transponder interface, which has the ability
to select one of up to 12 different wavelengths incident on the
balanced-PIN receiver.
• NTK504CD/CE/CF Fiber Interconnect Module (FIM): the FIM acts as a
mini patch panel interconnecting all WSSs and CCMD12s present at a
CDA with CCMD12 direct attach node.
— The NTK504CD FIM Type 4 is used to interconnect WSSs to
CCMD12s
— The NTK504CE FIM Type 5 is used to interconnect WSSs for degrees
1-5 and 6-10
— The NTK504CF FIM Type 6 is used to interconnect degrees 1-5 and
6-10
The CDA with CCMD12 direct attach architecture also relies on existing
amplifier and transponder hardware:
• The ROADM OTS which has the CCMD12 direct attach can use an XLA
with SRA (or ESAM/SAM) combination or a MLA3 with or without
ESAM/SAM combination.
added/dropped at a CCMD12.
compatible with colorless line systems is provided in “Supported

Multiple-Fiber Push-On/Pull-Off (MPO) connectors

To reduce the density of optical interconnections within a CDA with CCMD12
direct attach node, multi-strand ports and patchcords are used. The WSS
20x1 ports connecting to the FIM, and conversely the FIM ports connecting to
WSS 20x1 ports are equipped with 12-fiber Mechanical Transfer ferrule MPO
connectors. On the WSS 20x1, 10 of the 12 fiber strands are utilized for
bidirectional traffic.
Architecture using TID Sequence Provisioning

The basic Terminal CDA with CCMD12 direct attach configuration is shown in
Figure 3-38 on page 3-66. The WSS 20x1 Common In/Out ports can connect
to various amplifier configurations as shown in Figure 3-39 on page 3-67.
Ten CCMD12s are shown connected representing 120 flex grid channels or
96 fixed grid channels are supported. Fewer than 10 CCMD12s can be
connected Day 1, more can be added in-service up to a maximum of 10
CCMD12s per degree.
Degrees can be added in-service up to a maximum of 8 in this release. FIM

Type 5 is only required if the node expands to more than 1 degree. FIM Type
6 is only required if the node expands to more than 5 degrees.
This configuration can operate in fixed or flexible grid mode, but must use
L0 CP/SNC provisioning. To check the supported OSRP Node Type, refer to
the NTRN71AA, Control Plane Application Guide - Layer 0 (Photonic).
WSS 20x1 MPO port usage is shown in the table below.
Table 3-4
WSS 20x1 MPO port usage when using TID Sequence
WSS 20x1 MPO port Usage
Switch A - port 5 used if interconnecting with degrees 1-5 via FIM Type 5
Switch B - port 6 used if interconnecting with degrees 6-10 via FIM Type 6
Switch C - port 7 • used for local add/drop channels (up to 5xCCMD12s or 60

channels) via FIM Type 4
• must always connect to FIM Type 4 port 1 or port 3
Switch D - port 8 • used for local add/drop channels (up to 5xCCMD12s or 60

channels) via FIM Type 4
• must always connect to FIM Type 4 port 2 or port 4

Figure 3-38
Basic Terminal CDA with CCMD12 direct attach configuration

Figure 3-39
Amplifier configurations for CDA with CCMD12 direct attach configuration
A single FIM Type 4 can be used for 2 degrees to have full fill add/drop
channels per degree as shown in the figure below. FIM Type 5 is used for
interconnecting degrees 1 and 2.

Figure 3-40
CDA with CCMD12 direct attach - 2-way configuration

Degree expansion past 5 degrees

Degrees 1-5 are interconnected via the first FIM Type 5. Similarly, degrees
6-10 (note: only 8 degees supported in this release) get interconnected via a
second FIM Type 5. Degrees 1-5 and 6-10 are then tied together via the FIM
Type 6. Degrees can be interconnected even when the degrees have no local
add/drops. Refer to the figure below.
Figure 3-41
CDA with CCMD12 direct attach - degree expansion past 5 degrees
A full fill 8-way CDA with CCMD12 direct attach node is shown in the figure
below.

Figure 3-42
CDA with CCMD12 direct attach - 8-way configuration

Architecture using Manual Adjacency Provisioning

When using the TID Sequence for provisioning the configuration is limited on
degrees (max 8 degrees) and CCMD12s (10x) that can be connected. When
using manual adjacency provisioning, the TID Sequence restrictions listed in
Table 3-4 on page 3-65 no longer apply, so that any WSS MPO port can
connect to any FIM type and port. This makes the configuration more modular,
allowing a pay-as-you-grow architecture.
Provisioning
Manual adjacency provisioning is required for greenfield deployments. For
brownfield, TL1 or CLI is required to deprovision the TIDSLOTSEQ instances
on Port C to remove the FIM4 and manually provision the FIM6.
It is recommended to use 20x1 WSS MPO Port 8 (D) for locally added
channels in configurations where the number of degrees is higher than 10
since port 8 (D) has the highest isolation. However, software does not block
any port for add/drop or express traffic.
Many combinations of degrees and add/drop structures are permitted but the
maximum number of degrees is 15. For example:
• a 2-way ROADM node CDA configuration using FIMs Type 4 and Type 5
is shown in Figure 3-43 on page 3-72.
• a 15-way ROADM node CDA configuration using FIMs Type 4, Type 5 and
Type 6 is shown in Figure 3-44 on page 3-73.
• a 20-way ROADM node configuration using FIMs Type 5 and Type 6 is
shown in Figure 3-45 on page 3-74. This configuration has passthrough
traffic only (no add/drop structure).
— ROADM degree groups 1-5, 6-10, 11-15, and 15-20 interconnect via a
FIM5 for intra-group connections, and via a FIM6 for inter-group
connections.
This configuration can operate in fixed or flexible grid mode, but must use
L0 CP/SNC provisioning. To check the supported OSRP Node Type, refer to
the NTRN71AA, Control Plane Application Guide - Layer 0 (Photonic).

Figure 3-43
CDA with CCMD12 direct attach - 2-way configuration using Manual Provisioning

Figure 3-44
CDA with CCMD12 direct attach - 15-way configuration using Manual Provisioning

Figure 3-45
CDA with CCMD12 direct attach - 20-way configuration using Manual Provisioning (no add/drop)
Unsupported CDA with CCMD12 direct attach configurations

The following CDA with CCMD12 direct attach configurations are not
supported:
• Remote CCMD12
• ROADM OTSs equipped with the NTK553MA 20x1 WSS interconnected
to other ROADM OTSs not equipped with NTK553MA 20x1 WSS
• Configurations in which wavelengths originating at a particular shelf
traverse other shelves only to terminate at the originating shelf
Colorless and Colored Direct Attach (CDA) using 20x1 WSS,

FIM Type 4, FIM Type 5 and FIM Type 6
Overview
This application builds on the existing Colorless Direct Attach (CDA) with
CCMD12 direct attach using 20x1 WSS (using FIM Type 4, FIM Type 5 and
FIM Type 6) by adding Red and Blue CMD44 50 GHz, connected to particular
FIM4 ports via a BMD2 and an amplifier.

Architecture using TID Sequence Provisioning

The figure below illustrates the configuration. Although a 2-way ROADM is
shown, up to 15 degrees are supported in this release. While the CCMD12
has embedded amps to overcome the FIM and WSS insertion losses, the
CMD44s and BMD2 must connect to an external amplifier to ensure the
desired Tx and Rx power targets are met. Note that CCMD12 and CMD44s
can coexist in this configuration.
This configuration is only supported when the Colorless Direct Attach is using
TID Sequencing for provisioning.
Refer to “CMD44 direct attach configuration” on page 4-117 for engineering

rules and guidelines applicable to this configuration.

Figure 3-46
CDA with CCMD12 and CMD44s direct attach using 20x1 WSS

Colorless Directionless Contentionless (CDC) using 20x1 WSS

Overview
The Colorless Directionless application described in a previous section
increases flexibility compared to traditional fixed-filter ROADM applications,
but is not contentionless. With a COADM architecture, re-using the same
wavelength as local add/drop requires adding a bank of DIA OTS plus
COADM OTS for each wavelength instance. As banks are added though, the
number of WSS switch ports available for branching decreases. For example,
with a WSS 9x1, a 5-way node could support up to 5 banks, allowing re-use
of wavelengths added/dropped to/from all 5 directions (100% add/drop
capability), while an 8-way node would support only 2 banks for 25% add/drop
capability. To offer high-percentage add/drop capacity with a high number of
degrees, without duplicating equipment banks, requires an architectural
change.
Hardware
The CDC applications solve the contention issue with hardware featuring
more flexible wavelength selection capabilities:
• NTK553MA WSS 20x1: this WSS is equipped with 20 switch ports.
Compared to other WSSs with fewer switch ports, it also has the
particularity of having a wavelength-selective switch in the demux
direction instead of a passive splitter. This adds selective functions to the
demux direction, essential for CDC.
• NTK508HA CCMD8x16: this Colorless Channel Mux/Demux supports 16
channels which can be routed bidirectionally towards any of 8 different
backbone directions via its Multi-Cast Switch (MCS). All Tx and Rx ports
are broadband, i.e. they are deprived of any DWDM filtering function.
Since any CCMD8x16 Tx or Rx port has a straight path to any direction
(instead of following a common trunk like on the DIA + COADM
arrangement), the same CCMD8x16 can have up to 8 instances of the
same wavelength connected to it, each being directed/received to/from a
different direction.
Due to the MCS insertion losses, embedded amplifiers are equipped on
all 8 mux and 8 demux paths inside the CCMD8x16. The basic circuit pack
has the capability to support 4 directions, the other 4 directions needing
the insertion of an NTK576BA C-Band Expansion Module (CXM) into the
CCMD8x16.
• NTK504CA/CB Fiber Interconnect Module (FIM): the FIM acts as a mini
patch panel interconnecting all WSSs and CCMD8x16s present at a CDC
node. The FIM port mapping is fixed, so WSS switch port allocation is not
as flexible as before with the non-CDC configurations.

The FIM comes in two types, Type 1 (NTK504CA) and Type 2

(NTK504CB). The FIM Type 1 must be used in greenfield CDC
deployments. The FIM Type 2 must be used in brownfield CDC
deployments, and in the future will be needed to expand the add/drop
capacity at a CDC node deployed as greenfield.
The CDC architecture also relies on existing amplifier and transponder

hardware:
• For greenfield applications (see “Architecture - greenfield deployment”
below), support for the 96 channel plan limits the supported LIM types to
either XLA (plus SRA/ESAM/SAM) or MLA3. Other LIM types limit the
channel count to 88.
For brownfield applications (see “Architecture - brownfield deployment”
below), only the XLA is supported to connect the WSS 20x1 to the existing
WSS 9x1 Switch port.
added/dropped at a CDC node. Channels transported by other,
non-colorless-capable interfaces can nevertheless be deployed if they
simply pass through the CDC node.
compatible with CDC line systems is provided in “Supported transponders
for colorless and CDC line systems” on page 3-107.

To reduce the density of optical interconnections within a CDC node,
multi-strand ports and patchcords are used. The WSS 20x1 and CCMD8x16
ports connecting to the FIM, and conversely the FIM ports connecting to these
circuit packs are equipped with 12-fiber Mechanical Transfer ferrule MPO
connectors. On the WSS 20x1, 10 of the 12 fiber strands are utilized for
bidirectional traffic, while on the CCMD8x16, 8 of the 12 are used.
For further information on CDC line system hardware, refer to Technical

Publications 323-1851-102.6, Photonic Circuit Packs and Modules.
Mixing CDC and non-CDC nodes

To support CDC applications, a network does not have to be entirely based on
the CDC architecture. CDC nodes can coexist with non-CDC nodes so that
each node is equipped with the best fit configuration.
Architecture - greenfield deployment

The generic CDC node architecture deployed in a greenfield scenario is
illustrated in the figure below. When fully equipped, this node features 8-way
branching with an add/drop capacity of 176 channels. This represents a 25%
add/drop capacity (considering 88 channels). In a future release, upgrades
can increase the capacity to 100%.

At deployment, the node can have fewer degrees and CCMD8x16s, and be
upgraded in service with more degrees and CCMD8x16s later on, as needed.
Figure 3-47
Generic CDC node architecture - greenfield deployment
Connectivity
The WSS switch port usage is as follows:
• 7 ports dedicated to WSS-WSS inter connectivity (through the FIM
Type 1), for a maximum of 8 backbone directions (8-way branching node)
• 11 ports used for CCMD8x16 inter connectivity (through the FIM Type 1),
for a maximum of 176 add/drop channels
• 2 ports dedicated for upgrade, to increase the add/drop capacity in a future
release

Figure 3-48
Mux path signal flow at a 3-way branching CDC node (no CXM in CCMD8x16)
Signal flow in mux direction

The figure above helps better understand the contentionless aspect of CDC
by showing the mux path signal flow:
• Section A: transmitters connected to CCMD8x16 broadband Tx ports
produce light at specific wavelengths, n for OCLDs #1 and #3, and p for
OCLD #2.
• Section B: each Tx port is connected to an 8x1 switch acting as a direction
selector. In this example, OCLDs #1 and #2 have their switches pointing
to ROADM OTS #1. The 16x1 combiner associated to this direction
collects all signals whose switches point in this direction and sends them
down on a common path for amplification before reaching the WSS
belonging to ROADM OTS #1, through the FIM. Because they share a
common path along the way, OCLDs #1 and #2 respective wavelengths
must be different from one another.

On the other hand, OCLD #3, because its directional switch points to
another direction (i.e. ROADM OTS #3), can share the same wavelength
as OCLD #1. This shows the contentionless aspect of the architecture in
the mux direction.
• Section C: at the mux path WSS input, n and p are selected by the WSS
to be sent to the optical line, along with any express wavelength coming
from another backbone direction.
— For a given ROADM OTS WSS, up to 16 channels could come from
the same CCMD8x16, if all the Tx ports’ directional switches are
aligned the same way.
Figure 3-49
Demux path signal flow at a 3-way branching CDC node (no CXM in CCMD8x16)
Signal flow in demux direction

The figure above shows the demux path signal flow:
• Section A: multiple channels enter the node from multiple directions. Each
demux WSS selects which wavelengths to send to other directions
(express channels) and which wavelengths to drop at the node, and to
which CCMD8x16. In this example:

— ROADM OTS #1 receives n (drop) and p (express to OTS #2);

— ROADM OTS #2 receives only p (express to OTS #1);
— ROADM OTS #3 receives n and p (both drop)
• Section B: signals are sent from all demux WSSs to the CCMD8x16
through the FIM. Each backbone receive path is connected to a dedicated
demux path in the CCMD, where the signals are amplified and then
distributed by the 1x16 splitter to all of the 16 Rx 1x8 directional switches.
For each connected receiver, the directional switch is then set according
to the direction the Rx needs to listen to.
• Section C: a receiver listening to a given direction can receive from 1 to 16
channels, according to the number of channels dropped from this
backbone direction. The natural frequency selection of the coherent
receiver is used to select the channel of interest. In this example:
— OCLD #1 is tuned to n but receives only n;
— OCLD #2 is tuned to p and receives both n and p;
— OCLD #3 is tuned to n like OCLD #1, but receives both n and p. This
shows the contentionless aspect of the architecture in the demux
direction.
Architecture - brownfield deployment

The generic CDC node architecture deployed in a brownfield scenario is
illustrated in the figure below. When fully equipped, this node features 7-way
branching with an add/drop capacity of 320 channels. No further upgrade is
possible though, so the add/drop capacity never reaches 100%.
This configuration is meant to offer CDC functions to existing networks

deployed with WSS 9x1. As such, a formal Method of Procedure (MOP) is
required to deploy this configuration.
Connectivity
The WSS switch port usage is as follows:
• WSS 9x1
— 2 ports used for CMD44
— 1 port used for CDC upgrade
— 6 ports dedicated to WSS-WSS inter connectivity, for a maximum of 7
backbone directions (7-way branching node)
• WSS 20x1
— 20 ports used for CCMD8x16 inter connectivity (through the FIM
Type 2), for a maximum of 320 add/drop channels

Figure 3-50
Generic CDC node architecture - brownfield deployment
Unsupported CDC configurations

The following CDC configurations are not supported:
• DSCMs and pads provisioning within CDC node.
• ROADM OTSs equipped with the NTK553MA 20x1 WSS interconnected
to other ROADM OTSs not equipped with NTK553MA 20x1 WSS.
traverse other shelves only to terminate at the originating shelf.
Colorless Directionless Contentionless (CDC) and Colored using

20x1 WSS
Overview CMD44 50 GHz
This application builds on the existing CDC greenfield architecture by adding
Red and Blue CMD44 50 GHz, connected to particular FIM1 ports via a BMD2
and an amplifier.

Architecture CMD44 50 GHz

shown, up to 8 degrees are supported in this release. While the CCMD8x16
CMD44s and BMD2 must connect to an external amplifier to ensure the
desired Tx and Rx power targets are met. Note that CCMD8x16 and CMD44s
can coexist in this configuration.
Refer to “CMD44 50 GHz or 100 GHz direct attach configuration” on page

4-119 for engineering rules and guidelines applicable to this configuration.
Figure 3-51
CDC greenfield with CCMD8x16 and 50 GHz CMD44s direct attach using 20x1 WSS
Overview CMD44 100 GHz

This application builds on the existing CDC greenfield architecture by adding
a CMD44 100 GHz, connected to particular FIM1 ports via an amplifier.
Architecture CMD44 100 GHz

shown, up to 8 degrees are supported in this release. While the CCMD8x16

CMD44 must connect to an external amplifier to ensure the desired Tx and Rx

power targets are met. Note that CCMD8x16 and CMD44s can coexist in this
configuration.
Refer to “CMD44 50 GHz or 100 GHz direct attach configuration” on page

4-119 for engineering rules and guidelines applicable to this configuration.
Figure 3-52
CDC greenfield with CCMD8x16 and 100 GHz CMD44 direct attach using 20x1 WSS
T-Series Colorless, Directionless, Contentionless (CDC)

Overview
Hardware
The 6500 CDC architecture solves the contention issue with hardware
featuring more flexible wavelength selection capabilities:
• NTK722AA RLA 20x1: this RLA is equipped with Twin 20x1 gridless WSS
with an upgrade port. It has the particularity of having a
wavelength-selective switch in the mux and demux direction, essential for
CDC.
• NTK723AA CCMD 16x12: this Colorless Channel Mux/Demux supports
12 channels which can be routed bidirectionally towards any of 16 different
backbone directions via its Multi-Cast Switch (MCS) (although only 8

different backbone directions are supported in this release). All Tx and Rx

ports are broadband, i.e. they are deprived of any DWDM filtering function.
Since any CCMD 16x12 Tx or Rx port has a straight path to any direction,
the same CCMD 16x12 can have up to 12 instances of the same
wavelength connected to it, each being directed/received to/from a
different direction.
Due to the MCS insertion losses, amplifiers are required on all 16 mux and
16 demux paths inside the CCMD 16x12. The amplification is provided by
the NTK720BA AMP4 pluggable modules.
• NTK720CA CCMD 8x4: this Colorless Channel Mux/Demux supports 4
channels which can be routed bidirectionally towards any of 8 different
backbone directions via its Multi-Cast Switch (MCS). All Tx and Rx ports
are broadband, i.e. they are deprived of any DWDM filtering function.
Since any CCMD 8x4 Tx or Rx port has a straight path to any direction,
the same CCMD 8x4 can have up to 4 instances of the same wavelength
connected to it, each being directed/received to/from a different direction.
Due to the MCS insertion losses, amplifiers may or may not be required
(link engineering dependent) on all 8 mux and 8 demux paths inside the
CCMD 8x4. The amplification is provided by the NTK720BA AMP4
pluggable modules.
The CCMD 8x4 is plugged into the NTK721AA MFC (Multi-function
Carrier) 4xSubslot Module.
• NTK504CA/CC Fiber Interconnect Module (FIM): the FIM acts as a mini
patch panel interconnecting all RLAs and CCMDs present at a CDC node.
The FIM port mapping is fixed, so RLA WSS switch port allocation is not
as flexible as before with the non-CDC configurations.
— FIM Type 1 (NTK504CA) and FIM Type 3 (NTK504CC) are used for all
node add/drop architectures supported for T-Series in this release
— FIM Type 1 is the preferred and cost effective FIM type for
configurations with low degree count (less than or equal to 8)
– FIM Type 1 includes 8 quad-port MPO ports for degree (RLA)
interconnect, 11 dual-port MPO ports for Add/Drop (CCMD)
interconnect and several LC ports for expansion purposes (LC
ports not used in this release)
— FIM Type 3 is the preferred FIM type for configurations with high
degree count (less than or equal to 16, although up to 8 degrees are
supported in this release)
– FIM Type 3 includes 20 MPO groups (4 MPO ports per group) for
degree (RLA) or Add/Drop (CCMD) interconnect and several LC
ports for expansion purposes (LC ports not used in this release)

The CDC architecture also relies on specific transponder hardware.

at a CDC node.

compatible with CDC line systems is provided in “Supported transponders for
colorless and CDC line systems” on page 3-107.

To reduce the density of optical interconnections within a CDC node,
multi-strand ports and patchcords are used. The RLA and CCMD ports
connecting to the FIM, and conversely the FIM ports connecting to these
modules are equipped with 12-fiber Mechanical Transfer ferrule MPO
connectors. On the RLA, 10 of the 12 fiber strands are utilized for bidirectional
traffic, while on the CCMD, 8 of the 12 are used.
For further information on CDC line system hardware, refer to Technical

Publication 323-1851-103 6500-T12 Packet-Optical Shelf - Guide.
Architecture
All 6500 T-Series CDC node configurations using the FIM Type 3 must follow
the FIM Type 3 quad-group rule which is software enforced.
As shown in the figure below, there are 5 quad-groups on FIM Type 3: [FG1 –
FG4], [FG5 – FG8], [FG9 – FG12], [FG13 – FG16], [FG17 – FG20]
Figure 3-53
FIM Type 3 quad-group rule
The quad groups inherit either a Degree role or Add/Drop role based on the
first equipment provisioned in any one of the ports of the quad groups.

In the remaining ports of the quad group, there can only ever be equipment
from the same type provisioned. That is, if the role of the group is degrees, it
can only ever have RLAs provisioned in the sequences and vice versa for
CCMD.
4-degree CDC node using FIM Type 3

The 4-degree CDC node using FIM Type 3 is shown in the figure below. It
supports up to 4 degrees and up to 16 CCMD 16x12 modules (192 channels).
In this release, you can in-service upgrade to add more degrees (up to 4) or
CCMD 16x12 modules (up to 16).
In a future release, add/drop in-service upgrade (i.e., greater than 16) and/or
degree in-service upgrade (i.e., greater than 4) can be supported with extra
equipment.
Figure 3-54


The 8-degree CDC node using FIM Type 3 is shown in the figure below. It
supports up to 8 degrees and up to 12 CCMD 16x12 modules (144 channels).
The configuration figure also shows how the optional OTDR4 module is
connected. In this release, the OTDR pluggable must be in the same shelf as
the RLA(s) it is connected to.
In a future release, add/drop in-service upgrade (i.e., greater than 12) and/or
degree in-service upgrade (i.e., greater than 8) can be supported with extra
equipment.
Figure 3-55

8-degree CDC node using FIM Type 1 and CCMD 16x12

A CDC node using FIM Type 1 is shown in the figure below. It supports up to
8 degrees and up to 11 CCMD 16x12 modules (132 channels).
The configuration figure also shows how the optional OTDR4 module is
In a future release, add/drop in-service upgrade (i.e., greater than 11) can be
supported with extra equipment.
Figure 3-56


A CDC node using FIM Type 1 is shown in the figure below. It supports up to
8 degrees and up to 11 CCMD 8x4 modules (44 channels). Each CCMD 8x4
needs 2xAMP4 modules for the full CDC functionality.
Another configuration is shown in Figure 3-58 on page 3-93 where each

CCMD 8x4 is directly connected to the FIM (when link engineering allows).
The configuration figures also show how the optional OTDR4 pluggable is
In a future release, add/drop in-service upgrade (i.e., greater than 11) can be
supported with extra equipment.

Figure 3-57
8-degree CDC node using FIM Type 1 and CCMD 8x4 with AMP4

Figure 3-58
8-degree CDC node using FIM Type 1 and CCMD 8x4 without AMP4

Figure 3-59
Mux path signal flow at a 3-way branching CDC node

Signal flow in mux direction

The figure above helps better understand the contentionless aspect of CDC
by showing the mux path signal flow:
• Section A: transmitters connected to CCMD 16x12 broadband Tx ports
produce light at specific wavelengths, n for Tx #1 and #3, and p for Tx #2.
• Section B: each Tx port is connected to a 16x1 switch acting as a direction
selector. In this example, Tx #1 and #2 have their switches pointing to
ROADM OTS #1. The 12x1 combiner associated to this direction collects
all signals whose switches point in this direction and sends them down on
a common path for amplification before reaching the WSS belonging to
ROADM OTS #1, through the FIM. Because they share a common path
along the way, Tx #1 and #2 respective wavelengths must be different from
one another.
On the other hand, Tx #3, because its directional switch points to another
direction (i.e. ROADM OTS #3), can share the same wavelength as Tx #1.
This shows the contentionless aspect of the architecture in the mux
direction.
• Section C: at the mux path WSS input, n and p are selected by the WSS
to be sent to the optical line, along with any express wavelength coming
from another backbone direction.
— For a given ROADM OTS WSS, up to 12 channels could come from
the same CCMD 16x12, if all the Tx ports’ directional switches are
aligned the same way.

Figure 3-60
Demux path signal flow at a 3-way branching CDC node

Signal flow in demux direction

The figure above shows the demux path signal flow:
• Section A: multiple channels enter the node from multiple directions. Each
demux WSS selects which wavelengths to send to other directions
(express channels) and which wavelengths to drop at the node, and to
which CCMD 16x12. In this example:
— ROADM OTS #1 receives n (drop) and p (express to OTS #2);
— ROADM OTS #2 receives only p (express to OTS #1);
— ROADM OTS #3 receives n and p (both drop)
• Section B: signals are sent from all demux WSSs to the CCMD 16x12
through the FIM. Each backbone receive path is connected to a dedicated
demux path in the CCMD, where the signals are amplified and then
distributed by the 1x12 splitter to all of the 16 Rx 16x1 directional switches.
For each connected receiver, the directional switch is then set according
to the direction the Rx needs to listen to.
• Section C: a receiver listening to a given direction can receive from 1 to 12
channels, according to the number of channels dropped from this
backbone direction. The natural frequency selection of the coherent
receiver is used to select the channel of interest. In this example:
— Rx #1 is tuned to n but receives only n;
— Rx #2 is tuned to p and receives both n and p;
— Rx #3 is tuned to n like Rx #1, but receives both n and p. This shows
the contentionless aspect of the architecture in the demux direction.
Unsupported CDC configurations

The following CDC configurations are not supported:
traverse other shelves only to terminate at the originating shelf.
SCMD4 based Thin Terminal and Thin OADM (TOADM)

Overview
The 100 GHz four-channel serial Channel-Mux-Demux (SCMD4) based Thin
Terminal and Thin Optical Add-Drop Multiplexer (TOADM) feature provides a
cost reduced alternative to standard all-ROADM configurations.
At terminal or OADM nodes where a WSS circuit pack is not required, the
SCMD4 circuit pack is meant to be used in a cascaded configuration at that
node, providing per-channel actuator (eVOA) control and monitoring without a
WSS.

Hardware
The TOADM OTS can be comprised of the following components:
• One LIM circuit pack. Any MLA3, MLA2, MLA, SLA or LIM circuit pack as
per link engineering.
• Or with OTDR Capabilities: ESAM with MLA3, MLA2 or MLA
• Up to 9 NTK508AxE5 4 Channel Mux/Demux (SCMD4) circuit packs
Architecture
An illustration of inter-connections between Photonic equipment is shown for
the 100 GHz SCMD4 based
• Thin Terminal (see Figure 3-61 on page 3-99)
• Symmetric TOADM (see Figure 3-62 on page 3-100)
• Asymmetric TOADM (see Figure 3-63 on page 3-101)
• TOADM without SCMD4s present (see Figure 3-64 on page 3-102)
• TOADM with ESAM/MLA and SCMD4s present (see Figure 3-65 on page
3-103)

Figure 3-61
Thin Terminal example
Ch4 Out
10
9
Ch4 In
Upg In LC
11
MUX / DEMUX
Ch3 Out
12 8
Group Z
Out
Common In
Upg 7
1 Ch3 In
LC
2 Ch2 Out
6
LC Common Out
5
Ch2 In
LC
Ch1 Out
Slot 5
4
3
SCMD4 Ch1 In
LC
Ch4 Out
10
DSCM and pad placement

9
Ch4 In
Upg In LC

11
MUX / DEMUX
Ch3 Out
12 8
Out
Common In
Group Y
Upg 7
1 Ch3 In
LC
2 Ch2 Out
Common Out 6
LC
5
Ch2 In
LC
Ch1 Out
analysis
Slot 4
4
3
Ch1 In
SCMD4 LC
DSCM (Optional)
Ch4 Out
10
Pad (Optional)
9
Ch4 In
11
Upg In LC
MUX / DEMUX
Ch3 Out
12 8
Out
Common In
Group X
Upg 7
1 Ch3 In
LC
2 Ch2 Out
6
LC Common Out
2x OSC PEC: NTK554BA Ch2 In

5
LC
Ch1 Out
Slot 3
4
OSC1 Out
WSC
1
OSC
3
SCMD4 Ch1 In
3
OSC1 In
1 LC
OSC2 Out
WSC
2
OSC
2
4
2
OSC2 In
Slot 1
6
2
3
4
7
1
Mon 1 (B Out)
Mon 2 (A Out)
OSC A Out
Line A Out
OSC B In
Line B In
6500
Slot 2
PEC: NTK552BA
Line B Out
Line A In
MLA
5
8

Figure 3-62
Symmetric TOADM with standalone OPM example

Figure 3-63
Release 12.6
WS WS
WS WS
C4 C3
C4 C3
2x OSC
2x OSC

OSC OSC
Asymmetric TOADM example
Slot 14
OSC OSC
Slot 1
2 1
2 1
OSC2 In
OSC1 In
OSC1 Out
PEC: NTK554BA
OSC2 In
OSC1 In
OSC1 Out
PEC: NTK554BA
1
1
2
OSC2 Out 2
1
1
2
OSC2 Out 2
MLA 6500 6500 MLA
Out) 1 (B Out)
1

2 2
OSC B In 3
3 OSC B In
4 4
OSC A Out OSC A Out
8 A 7 6 B 5
5 B 6 7 A 8
Slot 2 Slot 13
LC
LC
2
1
2
1
11
11
12
12
Upg
Upg
In
In
Out
Out
Upg
Upg
SCMD4
SCMD4
Common In
Common In
Slot 3 Slot 4
Common Out
Common Out
MUX / DEMUX MUX / DEMUX
Ch1Out
Ch2Out
Ch3 In
Ch3Out
Ch4Out
Ch1Out
Ch2Out
Ch3 In
Ch3Out
Ch4Out
9
9
3
4
5
6
7
8
3
4
5
6
7
8
10
10
LC Ch1In
LC Ch2In
LC
LC Ch4In
LC Ch1In
LC Ch2In
LC
LC Ch4In
OTS1 OTS2
Group X Group Y


October 2019
WS WS
WS WS
C4 C3
C4 C3
Figure 3-64
Release 12.6
2x OSC
2x OSC
OSC OSC
Slot 14
OSC OSC
Slot 1
2 1
2 1
OSC2 In
OSC1 In
OSC1 Out
PEC: NTK554BA
OSC2 In
OSC1 In
OSC1 Out
PEC: NTK554BA
1
1
2
OSC2 Out 2
1
1
2
OSC2 Out 2

TOADM without SCMD4s example
MLA 6500 6500 MLA


Out) 1 (B Out)
1
2 2
OSC B In 3
3 OSC B In
4 4
OSC A Out OSC A Out
8 A 7 6 B 5
5 B 6 7 A 8
Slot 2 Slot 13
OTS1 OTS2

October 2019
Figure 3-65
TOADM with ESAM/MLA and SCMD4s example

96-channel support
To support 96 channels, 8 channels (4 channels at either end) are added to
the 88 channel 6500 C-Band plan as shown in the table below.
Table 3-5
96-channel wavelength/frequency plan
Channel number Wavelength (nm) Frequency (THz) New channel for 96
channel support
93 1528.77 196.10 Yes
94 1529.16 196.05 Yes
95 1529.55 196.00 Yes
96 1529.94 195.95 Yes
01-88 1530.33 - 1565.09 195.90 - 191.55 No
89 1565.50 191.50 Yes
90 1565.90 191.45 Yes
91 1566.31 191.40 Yes
92 1566.72 191.35 Yes
96-channel support is hardware (see Table 3-6) and configuration (see Table
3-7 on page 3-105) dependent.
Table 3-6
96 channel compliant hardware
Product Hardware type Hardware ordering code and description
6500 T-Series RLA NTK722AA RLA
CMD NTK723AA CCMD 16x12

NTK720CA CCMD 8x4
NTK720BA AMP4

Table 3-6
96 channel compliant hardware
Product Hardware type Hardware ordering code and description
6500 S-Series and AMP/LIM NTK552GA MLA3

D-Series NTK552KA XLA
NTK552DA LIM
NTK552JA SRA
NTK552JN SAM
NTK552JT ESAM
WSS NTK553MA WSSOPM 1 x 20

NTK553LA WSSOPM 1 x 9 50GHz Flexgrid
NTK553LB WSSOPM 1 x 9 50GHz Flexgrid
RLA NTK553RA RLA
SMD NTK553GB Flex SMD
OPM NTK553PA 2 Port OPM

NTK553PB 2 Port OPM Flexgrid
CMD NTK508HA CCMD8x16

NTK576BA CCMD8x16 CXM
NTK553FA CCMD12
NTT862EA CMD96
OPS NTK554TA OPS

NTK576AA OPS Module
Table 3-7
96 channel compliant configurations
Product Configurations
6500 T-Series CDC
6500 S-Series and Brownfield CDC

D-Series Greenfield CDC
Colorless Directionless with Flex SMD
Colorless Directional with Flex SMD (CDA with COADM direct attach)
Colorless Directional (CDA with CCMD12 direct attach)
Line amp
DGFF
Passthrough ROADM node with CMD44 50GHz attached
Colored Directional using 9x1 WSS with CMD96
Note: All configurations require 96 channel compliant hardware.
96 channel operational considerations

• Channel provisioning (using L0 Control Plane or not) of the extra 8
channels is permitted by software only if all hardware in the path is 96
channel compliant.

— In a node, Photonic connections are prevented from being added if

there is any hardware in the port trail that does not support that
wavelength
— In a Photonic domain, channel topology does not build if any hardware
in the path does not support that wavelength. The “Unsupported
Channel Provisioned” alarm is raised in this case.
• The 8 extra channels are not supported through CPL or TOADM nodes.
• The 8 extra channels cannot pass through a ROADM OTS that has a
100 GHz filter attached (CMD44 or OMDFx).
• Do not add/drop channels 92-95 at a backbone WSS if the backbone WSS
has brownfield CDC or colorless attachment and certain hardware version
CMD44 50GHz attached to any of its switch ports for local add/drop traffic.
This operational consideration only applies for the following hardware
version CMD44 50GHz modules:
— NTT862BA/BB hardware version 06 or lower
— NTT862BC/BD hardware version 04 or lower
• Do not passthrough channels 92-95 at a passthrough ROADM node if the
passthrough node WSSs/RLAs have certain hardware version CMD44
50 GHz attached to any of their switch ports for local add/drop traffic. This
operational consideration only applies for the following hardware version
CMD44 50 GHz modules:
— NTT862BA/BB hardware version 06 or lower
— NTT862BC/BD hardware version 04 or lower
• Connection Validation and Transponder Loopback features use channel
93.
— Channel 93 should be the last channel to be provisioned. L0 Control
Plane automatically ensures this when using implicit wavelength
selection.
— Software prevents Transponder Loopback and Connection Validation
operations if channel 93 is provisioned.
— Software prevents channel 93 provisioning if Transponder Loopback
and Connection Validation operations are in progress.

Supported transponders for colorless and CDC line systems

Supported transponders for colorless and CDC line systems are listed in the
table below.
Table 3-8
Supported transponders for colorless and CDC line systems
Product Transponder type Supported on Supported on
6500 S/D-Series 6500 T-Series CDC
colorless and CDC line systems
line systems
6500 T-Series 2x100G WaveLogic 3n PKT/OTN I/F Yes Yes

5x100G WaveLogic 3n CFP2-ACO PKT/OTN I/F
6500 S/D-Series 100G WaveLogic 3 OCLD Yes Partial (see Note 1)

100G WaveLogic 3e OCLD
Flex2 WaveLogic 3 OCLD
Flex2 WaveLogic 3e OCLD
100G OTR WaveLogic 3e
100G OTR WaveLogic 3n
100G MOTR WaveLogic 3n
WaveLogic Ai or WaveLogic Ai w/OPS
5400 TLSM1-WL3 Yes Partial (see Note 1)

OSLM1-WL3
OSLM-2-Flex3-WL3e
8700 CSLM-200-2 WaveLogic 3n Yes Partial (see Note 1)
Waveserver Waveserver 400G 2+10 bundle which includes Yes Partial (see Note 1)
Waveserver 400G 2xWL3e 10xQSFP+/QSFP28
Waveserver 400G 2+10 EDFA bundle which
includes Waveserver 400G 2xWL3e
10xQSFP+/QSFP28 EDFA
Waveserver Ai
Foreign Must be coherent Yes Yes
Note 1: Supported using Foreign Coherent CMD Tx/Rx Type.
Operational considerations for 6500 Wavelogic 3n:

• In most cases, WL3n wavelengths can be added next to other transponder
types even though the WL3n circuit pack has lower Max. Typical Tx launch
power (-5 dBm).
• Exceptions may occur for DIA systems or for systems using the
NTK553KC Wavelength Selective Switch (WSS) 50 GHz w/OPM C-Band
2x1 circuit pack (triple slot-wide variant). In these exception scenarios,
OnePlanner will fail and Ciena should be contacted for possible
workarounds.

• A possible workaround for the DIA greenfield case is that the Tx launch
power of WL3 wavelengths is reduced to a value closer to the Tx launch
power of WL3n wavelengths. The following steps can be performed on
greenfield applications before adding wavelengths on 6500 or CPL DIA
systems:
— If using SPLI:
– Ciena provides new Tx launch power value for non-WL3n
wavelengths.
– Modify the CMD ADJ-Tx “Actual Tx Power” parameter to the Tx
launch power value provided by Ciena for all non-WL3n
wavelengths.
— If not using SPLI:
– Ciena provides new Tx launch power value for non-WL3n
wavelengths.
– Modify the CMD ADJ-Tx “Actual Tx Power” parameter to the Tx
launch power value provided by Ciena for all non-WL3n
wavelengths.
– Set the “Provisioned Tx Power” parameter to the Tx launch power
value provided by Ciena for all non-WL3n transponders
OSC
This section describes the OSC function and includes:
• An overview of the OSC hardware supported on the 6500 platform,
including:
— Available OSC SFP types
— Circuit packs used to house OSC SFPs
— OSC filters and their location, whether embedded in another circuit
pack or standalone module
• Several valuable software features that make use of the OSC are
described later in this section:
— OSC Span Loss reading
— OSC Span Loss PMs
— Wayside Channel
— OSC-based Delay Measurement (DM) on S/D-Series and T-Series
The OSC channel is used by Photonic applications to carry Ethernet Over

SONET (EOS) service traffic between 6500/CPL nodes.
• OSC carries OAM&P information for features such as alarming, control
and data communications.

• The SFP pluggable ports support an OSC facility at an OC-3/STM-1 rate

of 155 Mbps. The OC-3/STM-1 signal is converted to a wavelength based
on the SFP type used.
OSC SFP hardware
The table below lists the 6500 OSC Tx/Rx CWDM and DWDM SFPs available
for 6500 applications.
The OSC OC-3/STM-1 signal is converted to a wavelength at 1511 nm (for
CWDM SFPs) or 1517 nm (for NTK592NR DWDM SFP) that co-propagates
with the traffic carrying wavelengths.
Table 3-9
Available OSC SFPs and applications
PEC Description Application
NTK592NP OC-3/STM-1 CWDM 1511 nm SFP Module Low Span Loss

(0-15 dB span)
NTK592NB OC-3/STM-1 CWDM 1511 nm SFP Module Medium Span Loss

(10-30 dB span) Not supported on T-Series
NTK592NH OC-3/STM-1 CWDM 1511 nm SFP Module High Span Loss

(20-34 dB span) Not supported on T-Series
NTK592NG OC-3/STM-1 CWDM 1511 nm SFP Module Low Tx Power for non-linear
(0-34 dB span) impairment mitigation on
specific fiber types.
Low Rx Sensitivity
(Low to High Span Loss)
NTK592NV OC-3/STM-1 CWDM 1511 nm SFP Module High Span Loss

(12-42 dB span) Low Rx Sensitivity
(Med to High Span Loss)
NTK592NR OC-3/STM-1 DWDM 1516.9 nm SFP module High Span Loss

(12-44 dB span) Raman application only
Not supported on T-Series

OSC SFP carrier hardware

OSC Tx/Rx SFPs can be equipped in different equipment which act as OSC
SFP carriers.
Table 3-10
6500 hardware used to equip OSC SFPs
PEC Description Width # of SFPs Add/Drop OSC filter

(slots) location
NTK722AA RLA 20x1 1 1 Within

NTK722AA RLA
NTK554BA 2xOSC 1 Within 6500 LIM:

NTK552AA SLA
NTK555NA SPAP-2 with 2xOSC w/ 2XSFP 1 NTK552BA MLA
NTK555NB 2 (Note 1) NTK552DA LIM
NTK552FA MLA2
NTK552FB MLA2v
NTK552GA MLA3
NTK552JA Single Line Raman Amplifier (SRA) 1 1

Within
(Note 2)
NTK552JA SRA
(Note 3)
NTK552JT Enhanced Service Access Module (ESAM) 1 Within NTK552JT

ESAM
1 (Note 3)
NTK554JN Service Access Module (SAM) 1 Within NTK552JN
SAM
Note 1: Up to two OC-3/STM-1 CWDM SFPs can be used as per link budget analysis:
NTK592NP: OC-3/STM-1 CWDM 1511 nm SFP Module (0-15 dB span)
NTK592NB: OC-3/STM-1 CWDM 1511 nm SFP Module (10-30 dB span)
NTK592NH: OC-3/STM-1 CWDM 1511 nm SFP Module (20-34 dB span)
NTK592NG: OC-3/STM-1 CWDM 1511 nm SFP Module (0-34 dB span)
NTK592NV: OC-3/STM-1 CWDM 1511 nm SFP Module (12-42 dB span)
Note 2: The following DWDM SFP is supported on the SRA:

NTK592NR: OC-3/STM-1 DWDM 1516.9 nm SFP module (12-44 dB span)
Drop direction: Also need extra NTK504BA OSC Filter Module.
Note 3: The following OC-3/STM-1 CWDM SFPs can be used on the SRA, SAM or ESAM:
NTK592NG: OC-3/STM-1 CWDM 1511 nm SFP Module (0-34 dB span)
NTK592NV: OC-3/STM-1 CWDM 1511 nm SFP Module (12-42 dB span)
OSC filters embedded in circuit packs

In photonic applications, the OSC channel must be coupled (added) into or
decoupled (dropped) from the transmission fiber using an OSC filter.

OSC filters embedded in 6500 T-Series modules

The 6500 T-Series RLA 20x1 module contains an embedded OSC filter which
can add/drop a CWDM SFP 1511 nm OSC channel.
OSC filters embedded in 6500 LIM circuit packs
6500 Line Interface Module (LIM) circuit packs contain an embedded OSC
filter which can add/drop a CWDM SFP 1511 nm OSC channel. The LIM
PECs are:
— NTK552AA SLA
— NTK552BA MLA
— NTK552DA LIM
— NTK552FA MLA2
— NTK552FB MLA2v
— NTK552GA MLA3
OSC filters embedded in 6500 SRA/ESAM/SAM circuit packs
The SRA, SAM and ESAM circuit packs each contain an embedded OSC filter
capable of add/dropping a CWDM 1511 nm OSC signal.
• Refer to the notes of Table 3-10 on page 3-110 for the CWDM 1511 nm
SFPs supported on the SRA, SAM or ESAM circuit packs.
• The SRA circuit pack also supports a DWDM OSC SFP operating at
1516.9 nm with OSC filter as described in the next section.
Extra OSC drop filter module used in Raman applications

The 1U high NTK504BA OSC Filter Module is used with the SRA circuit pack.
The module is passive but can be inventoried via a Ethernet cable connection
to the shelf Access Panel physical port, or provisioned using a virtual slot.
• The NTK504BA OSC Filter Module is an extra module deployed only in the
OSC drop direction as per the figure below.
— It is used to alleviate non-linear penalties such as for Four Way Mixing
(FWM) in TWRS fiber.
— Does not have any ADJ to provision, not part of any OTS, and can only
be inventoried.
— This NTK592NR SFP must always be used in combination with the SC
Filter Module to reach spans losses of up to 43.4 dB on NDSF/PSC
fiber type and up to 44.5 dB on other fiber types.
— The OSC Filter Module is a narrow external optical filter (<1 nm)
whose passband allows 1516.9 nm.
— The embedded OSC filter on the SRA filter is 15 nm wide. Therefore,
the extra DWDM filter provides better isolation from noise generated
during the Raman amplification process, which in turn gives a better
performance for higher-span systems and when using TWRS fiber.

— The NTK592NR SFP needs to be bookended for proper

communication across the span.
The NTK592NR OSC SFP and NTK504BA OSC Filter should be used in the
following scenarios:
• If the span fiber type is TWRS and the SRA circuit pack is used.
• If the fiber type is something other than TWRS and the OSC CWDM SFP
link budget limits are exhausted.
Figure 3-66
SRA to OSC filter connection
• Refer to Chapter 4 for an example detailed site-level diagram. See

Operational considerations when using OSC SFPs with SRA/SAM/ESAM

The following operational considerations apply:
• The NTK592NR DWDM SFP is only supported on the SRA circuit pack.
• Of the OC-3/STM-1 CWDM 1511 nm SFPs, only the NTK592NG (0-34 dB
span) and NTK592NV (12-42 dB span) variants are currently supported
on the SRA, SAM or ESAM circuit packs, based upon link budget analysis.
• Depending on the fiber type, the OSC channel gains about 3dB when the
Raman pumps are on. Therefore, the OSC span loss reading is not
inaccurate.

• If any padding is required on the OSC Tx SFP, this will be highlighted by

OnePlanner. The padding affects the maximum reach of the SFP.
• OSC reach numbers available through Ciena link design tools or OPNET
for Raman applications may differ from those for non-Raman applications.
These are attributed to differences in system configurations and hardware
insertion losses.
OSC Span Loss and OSC Span Loss PMs
Since the introduction of the 6500 photonic platform, the OSC signal levels
have been used to provide an estimate of the span loss between nodes.
The estimated Span Loss value is presented in the Site Manager Equipment
& Facility Provisioning application under the OSC facility and under the LIM or
SRA/ESAM/SAM or RLA ADJ-LINE facility.
OSC Span Loss Performance Monitoring also is available to help identify how
the span loss changes over time. The following OSC Span Loss PM monitor
types are available:
• SPANLOSS-OCH
• SPANLOSSMAX-OCH
• SPANLOSSMIN-OCH
• SPANLOSSAVG-OCH
Historical data collection is supported for each monitor type mentioned above,
and threshold crossing event notification is supported for the
SPANLOSS-OCH monitor type.
Wayside Channel (WSC)

The wayside access ports on the SRA, SAM, ESAM, RLA, 2xOSC and
SPAP-2 w/2xOSC circuit packs allows the OSC communication infrastructure
to be shared with wayside traffic flows that originate and terminate external to
the line system. As such, the communication infrastructure acts as a pipe to
allow the transfer of these flows between nodes.

The table below shows the WSC-to-OSC port associations used for Ethernet
connectivity.
Table 3-11
WSC-to-OSC port associations for Ethernet connectivity
Circuit pack WSC port Associated OSC port
SRA WSC1 OSC2

SAM
ESAM
NTK722AA T-Series RLA
2xOSC WSC3 OSC1

SPAP2 w/2xOSC WSC4 OSC2
One important characteristic of these flows is that they enter the system
through one wayside port and exit the system through another wayside port.
They are not allowed to terminate at any element within the system. Wayside
ports can be bridged externally through an Ethernet cable to maintain wayside
connectivity between OSC facing directions. Pass-through packets that are
virtual local area network (VLAN) tagged in the following range: 256-4094 are
supported on the wayside channel.
The wayside channel ports can be set to 10Base-T (Half or Full duplex),
100Base-T (Half or Full duplex), or Automatic (in the Site Manager Comms
Setting Management application Interfaces tab, Interface type LAN). The
default setting is Full Duplex 10Base-T for 6500-type shelves, and Automatic
for 6500-T12 shelves. Auto-negotiation automatically senses the speed
(10BT/100BT) and mode (half-/full-duplex) settings of the link. If the
configuration is set to Automatic, the Wayside ports automatically detect the
correct MDI/MDI-X setting to use, so either straight or crossover cables can
be used. If the configuration is not set to automatic, then since the Wayside
ports are MDI-X type use a straight cable to connect to a MDI interface or a
crossover cable to connect to a MDI-X interface.
The Automatic and 100Base-T settings can only be used in conjunction with
traffic policing which ensures that only 40 Mb/s of data is sent over the
wayside channel (note that the rate may vary somewhat depending on the
packet frame size). When the 6500 software detects the traffic rate exceeds
40 Mb/s, wayside traffic is limited to avoid OSC link congestion. OSC link
congestion can cause packet delays, loss on the 6500 internal traffic and
network management traffic, OSC comms loss, failure of optical control (DOC
adjacency failure alarms), and loss of association on network management
systems. To avoid wayside channel limiting, it is recommended to control the
traffic at the traffic sources. This can be done by setting up external traffic

management policies on the routers that are connected to wayside ports. The
traffic management policies need to set the limit of the wayside traffic to be
lower than 40 Mb/s. 6500 automatically terminates the wayside channel rate
limiting and traffic resumes normally when it detects that the wayside channel
traffic rate is lower than 40 Mb/s.
OSC Delay Measurement on S/D-Series and T-Series
Attention: As of Rel. 12.1, the ‘OSC Delay Measurement’ (or DM) replaces
the measurement formerly known as ‘OSC Round Trip Measurement’ (or
RTD), to align with T-Series. Note that DM is automatically enabled after an
upgrade from a previous release only if RTD was enabled prior to the
upgrade.
Delay Measurement (DM) support is available on OSC facilities of the

following circuit packs:
• NTK552JA SRA
• NTK552JT ESAM
• NTK552JN SAM
• NTK554BA 2xOSC
• NTK555NA/NB SPAP-2 w/2xOSC 2xSFP
• 2-Slot Shelf Type 2 NTK503LA embedded OSC
• 7-Slot Shelf Type 2 NTK503KA embedded OSC
• T-Series NTK722AA RLA 20x1
The following is provided:

• DM runs automatically and continuously as long as the OSC facility is
provisioned and the OSC Delay Measurement parameter is set to Enabled
(Default).
— The Site Manager Configuration->Equipment & Facility Provisioning
and the OSC facility provides the “One Way Latency” in microseconds
as well as the “Delay Measurement Distance” in kilometers.
— The “Delay Measurement Distance” is a calculation based on the “One
Way Latency”.
• OSC DM PMs (refreshed every second):
— DMMIN: Delay Measurement Minimum
— DMMAX: Delay Measurement Maximum
— DMAVG: Delay Measurement Average
• OSC DM PM thresholds and Threshold Crossing Alerts (TCAs)

— All threshold parameters must be provisioned by the user for TCAs to

be raised.
Operational considerations for Delay Measurement feature

The following operational considerations apply to this feature:
• Not supported when one (or both) end(s) of the span is a CPL node.
• Measurement starts when the OSC facility is created, after a restart of the
circuit pack housing the OSC SFP, after OSC faults clear or after the DM
feature is enabled.
• The time it takes to get accurate DM values is around 5 minutes.
• No PM baselines are required for DM since “absolute” threshold values
are used.
• Since the PM monitored data is collected and stored on the equipment
carrying the OSC, a restart of this circuit pack erases all PM monitored
data collected to date, which includes all current and history bin data.
— Values are marked invalid until the data is ready.
— Data should be ready within 5 minutes from when restart is complete.
• Since the PM monitored data is collected and stored on the equipment
carrying the OSC, a SP restart or switchover has no affect on the PM data,
including that for DM monitor types. Current and historical PM bins
containing DM monitor data is preserved. The same goes for the CTM on
T-Series.
EDFA amplified applications

Shared amplifier node
Photonic engineering rules stipulate that up to four amplifier OTSs are
supported on a given 7-slot, 14-slot or 32-slot shelf. In typical configurations,
no more than two OTSs would be required for any given DOC domain.
However in certain cases, a second set of OTSs could be used on the same
shelf, for another system.
This rule is valuable as it allows the deployment of minimal footprint to handle

traffic through two independent (physical or logical) bidirectional routes.
Typical applications that would require this are:
• where the intersection of physically-diverse routes occurs (for instance a
north-south axis with an east-west axis);
— two independent DOC domains (OSIDs) overlaid, using the same Line
Amp node (see Figure 3-67 on page 3-117)
• a collapsed (i.e. folded) ring
— fiber conduit is shared by two logically separate paths

— either the same or two independent DOC domains (OSIDs) use the
same Line Amp node (see Figure 3-68 on page 3-118 and Figure 3-69
on page 3-118)
The following lists the operational considerations about this application:
• The user must follow the usual OTS and adjacency provisioning steps
when setting up the Line Amp node, with the exception that the far-end
addresses of all the amps at the far-end ROADM (or TOADM) nodes, as
well as the Line Amp nodes, need to be overwritten manually as the
auto-discovered far-end addresses may be wrong.
Figure 3-67
Shared Line Amp node - intersection of two routes, different OSIDs
Channel Access
Site 1
ROADM
Line Amp Site #2
DOC DOMAIN Channel Access
Site 3
ROADM
WSS LIM LIM LIM

(OSID) #1 LIM WSS
Bidirectional
link #1 1st line amp (2 OTSs)
CMD44 CMD44
Line Amp Site
- shared between two independent routes and DOC domains
- Line Amp site shared by both routes
Tx/Rx Tx/Rx
- 2 OTSs per line amp, 4 total OTS in one line amp NE
LIM LIM
Channel Access ROADM Channel Access ROADM

Site 4 Site 5
WSS LIM LIM WSS
2nd line amp (2 OTSs)

Bidirectional
link #2
DOC
DOMAIN
CMD44
(OSID) #2 CMD44
Tx/Rx Tx/Rx

Figure 3-68
Share Line Amp node - collapsed ring, same OSID
Channel Access – ROADM Line Amp Channel Access – ROADM
Site 1 Site 2 Site 3
DOC DOMAIN
WSS LIM LIM LIM
(OSID) #1 LIM WSS
Bidirectional link #1
1st line amp (2 OTSs)

CMD44 CMD44
Collapsed Ring Application

Tx/Rx - Fiber Conduit shared by Northern and Southern Path Tx/Rx
WSS LIM LIM LIM LIM WSS
CMD44 CMD44
Tx/Rx DOC DOMAIN Tx/Rx
(OSID) #2
Figure 3-69
Shared Line Amp node - collapsed ring, different OSIDs
Channel Access – ROADM Line Amp Channel Access – ROADM
Site 1 Site 2 Site 3
DOC DOMAIN
WSS LIM LIM LIM
(OSID) #1 LIM WSS
1st line amp (2 OTSs)

CMD44 CMD44
Collapsed Ring Application

Tx/Rx - Fiber Conduit shared by Northern and Southern Path Tx/Rx
WSS LIM LIM LIM LIM WSS
CMD44 CMD44
Tx/Rx Tx/Rx

SLA-based Drop LIM

In order to improve the transponder receiver power level, it may be necessary
to include an extra amplifier in the WSS drop path in some network
deployments. This is known as the “Drop LIM” application.
The Drop LIM feature uses the SLA (NTK552AA), connected to supported
WSS circuit packs. Applicable engineering rules and site schematics are
described in “ROADM/Metro ROADM with Drop LIM” on page 4-82.
• Note that the MLA Line A EDFA can be used as a Drop LIM if the MLA Line
B amplifier is used as a Mux Amp function. In this case, the MLA serves a
dual purpose (Drop LIM and Mux Amp). For an overview of the Mux Amp
feature, refer to “SLA/MLA Mux Amp” on page 3-124.
MLA2v - EDFA with embedded VOA
The NTK552FB Midstage Line Amplifier 2 (MLA2 C-Band) w/Variable Optical
Attenuator (VOA) (“MLA2v”) offers similar functionality to the existing
NTK552FAE5 MLA2 circuit pack with the following differences:
• The MLA2v includes a Variable Optical Attenuator at the output of each
amplifier required for applications where attenuation is needed to meet
link budget constraints and pads are not desired.
• The typical power consumption of the MLA2v is slightly higher than that of
the MLA2 owing to the embedded electronically-controlled VOA.
The embedded VOA within the MLA2v circuit pack is used to control the total
span loss or the loss in the mid-stage between amplifiers or to ensure that the
downstream amplifier is not in minimum gain.
• For example, between two MLA2v circuit packs at a Line Amp node or
between an MLA2v and the interior SLA.
The MLA2v VOA attenuation level is provisioned independently from the

amplifier gain. During normal operation, the VOA is closed-loop controlled in
constant attenuation mode.
For further information on the NTK552FB MLA2v circuit pack, refer to the
Technical Publication 323-1851-102.6, Photonic Circuit Packs and Modules.
The NTK552FB is supported in amplifier and ROADM OTSs. Examples of

supported configuration are shown in high-level diagrams below:
• ROADM OTS, Terminal with MLA2v, uncompensated or compensated
• ROADM OTS, Terminal with MLA2v, cascaded (interior) SLA,
uncompensated or compensated (see Figure 3-71 on page 3-121)
• AMP OTSs with MLA2v, uncompensated or compensated (see Figure
3-72 on page 3-122)

• Asymmetric configurations, where the MLA2v is the fiber-plant facing LIM

in a ROADM or AMP OTS on one side of a span, with a fiber-plant facing
LIM module of another type on the other side of the span (see Figure 3-73
on page 3-123)
Operational considerations for use of MLA2 with embedded VOA
The following operational considerations apply when using the NTK552FB
MLA2 with VOA circuit pack.
• The NTK552FB is not supported in TOADM, DIA OADM or COADM OTSs
(not blocked by software).
— The exception to this is if the NTK552FB is used in Coherent Select
applications where the TOADM OTS subtype is used. For more
information, refer to Technical Publication 323-1851-980, WaveLogic
Photonics Coherent Select.
• From an alarms and PM perspective, the MLA2v has the same set of
alarms/PMs as the existing MLA2 circuit pack with the following changes:
— VOA Loss of Signal alarm is raised when the VOA OPOUT PM value
is below the VOA Loss of Signal Threshold.
— AMP Output Loss of Signal suppresses VOA Loss of Signal. By
extension, AMP Shutoff Threshold Crossed suppresses VOA Loss of
Signal.
— A Circuit Pack Fail alarm is raised if the VOA fails. This results in the
amplifier being put in the OOS-AU state. The amplifier and the VOA
remain at the same gain and loss as previously set.
— ORL PM is reported against VOA facility instead of AMP facility.
— When the ORL reading is not valid because the power into the
backward reflective monitor tap is too low and cannot be measured
accurately (i.e. the connection is very clean), the ORL PM reading(s)
report “OOR”. The true ORL reading cannot be determined in this
case.
— This occurs when the reflected power is below a certain threshold (of
at least -36dBm). CHMON PMs report power at the circuit pack output
which is after the VOA. To do so, power data from the EDFA monitor is
taken then scaling is done using VOA loss.
• Equipment reconfiguration is supported for the following cases by first
putting the equipment OOS, editing the Provisioned PEC and returning
the equipment to the IS state:
— MLA/MLA2/MLA3 to MLA2v
— MLA2v to MLA/MLA2/MLA3
— Upon the reconfiguration, LOS threshold values are automatically
updated to the new default values

For further information, refer to Technical Publication 323-1851-545, Fault

Management - Module Replacement.
Figure 3-70
ROADM OTS with line facing MLA2v examples
Figure 3-71
ROADM OTS with line facing MLA2v and cascaded (interior) LIM examples

Figure 3-72
AMP OTSs with line facing MLA2v examples

Figure 3-73
Asymmetric MLA2v configurations
Compact footprint Line Amp node using SPAP-2 w/ 2xOSC 2xSFP

A Line Amp node can be created in reduced footprint configurations using the
NTK555NA/NB SPAP-2 w/2xOSC 2xSFP circuit pack in the following shelf
types:
• NTK503LA 2-slot shelf Type 2
• NTK503KA 7-slot shelf Type 2
For uncompensated line systems, the footprint reduction is more pronounced

since no DSCMs are required. However, when used, DSCMs and pads can be
provisioned in the same places as before.
An example is shown in the figure below.

Figure 3-74
2-slot shelf configured as Line Amp node using SPAP-2 w/ OSC 2xSFP
For additional information on the NTK555NA/NB SPAP-2 w/2xOSC 2xSFP

circuit pack, refer to Technical Publication 323-1851-102.1, Common
Equipment.
SLA/MLA Mux Amp

Overview
Due to the variety of DWDM transponder types available on 6500, 5400 and
8700, the transmit power range between different interfaces can vary.
For DOC control and optimization, this range of signal powers may normally
be addressed by the dynamic range of the WSS circuit packs used in ROADM
based link designs, where the controlled loss is sufficiently set to achieve the
desired launch power into the fiber plant.
However, if DWDM transponder types of a generally lower output power range

are used, the WSS pixel loss dynamic range may be insufficient to achieve a
specific launch power, necessitating amplification in the add direction. The
application that addresses this need is an SLA or MLA based mux amplifier.
Use of Mux Amplifier with WL3n circuit packs

The WL3n circuit packs have no embedded EDFA, and consequently have a
lower launch power than other 100G circuit packs.
• The max power is -5 dBm for WL3n variants, compared to +1 dBm for
other WL3 variants.
• If at the same node WL3n transponders are mixed with other transponder
types with higher launch power, there may be cases where there is not
enough dynamic range on the WSS.
When mixing WL3 and WL3n at the same node, the following strategies can
be used:
• If link budget permits, add WL3n along side existing transponders.
— There is a need to take the dynamic range on the WSS into account.
• Reduce the Tx power of the existing transponders if available OSNR
margin exists.
• Add an amp in a new, dedicated mux path along a different WSS Switch
port. This is referred to as the Mux Amp configuration.

— Involves additional CMD44s, BMD2 and amplifier equipment as

required.
— The amplifier is either an NTK552AA SLA (where the Line A
pre-amplifier is used) or an NTK552BA MLA if a Drop LIM is also
required (where the Line B booster amplifier is used as the WL3n Mux
Amp, paired with the Line A pre-amplifier used for a Drop LIM).
— For an overview of the Drop LIM, application, refer to “SLA-based Drop
LIM” on page 3-119.
• If there are no more available WSS ports for the Mux Amp (for instance,
switch ports are currently in-use for branching), and the Tx power of
existing transponders cannot be reduced, then pad the existing
transponder transmitters.
The above represents the Mux Amp feature used for WL3n interfaces. Refer
to “Operational considerations for 6500 Wavelogic 3n:” on page 3-107 for
details about other strategies.
This Mux Amp for WL3n feature is used primarily in 6500 photonic
applications, in particular brownfield configurations where other transponder
types are already present in the node. Note that:
• When a Mux Amp is required, the WL3n normally necessitates its own
CMD44 module, while other transponders connect to a separate CMD44.
• If another WSS switch port is unavailable for the connection of an
additional CMD44, then use of an existing CMD44 is possible, whereby
the addition of the Mux Amp entails a traffic impacting reconfiguration.
• The WL3n Mux Amp application is not required with CPL due to lower loss
requirements.
The Mux Amp configurations are detailed in “ROADM/Metro ROADM with

Mux Amp” on page 4-103.
Dual XLA Line Amplifier

For links that require addition amplification.
• All dual XLA Line Amp configurations support an optional 2-port OPM for
fault isolation.
• Only SAM/ESAM are supported as line facing circuit packs. (SRA is not
supported)
• Line Amp configurations support dual XLAs where one XLA is provisioned
in one OTS and the other XLA is provisioned in the other OTS.

Figure 3-75
Dual XLA amplifier configuration
Raman amplified applications

Raman amplification overview
A brief description of the physics behind Raman amplification provides the
context for the introduction of the NTK552JA Single Raman Line Amplifier
(SRA) circuit pack.
Raman amplification is achieved through Stimulated Raman Scattering

(SRS), a non-linear optical effect that results when very high power is
transmitted into the core of an optical fiber. At the microscopic level, the fiber
core material absorbs photons, which results in molecular vibrations
(phonons) and the emission of photons (scattering of light) in both the forward
and backward directions. In practice, Raman pumps are used to inject high
power into the fiber core at specific pump wavelengths. The high power pump
signals interact with the fiber medium and amplify traffic-carrying signals.
Raman amplification:
• Achieves optical gain in the transmission fiber itself.
• Is distributed along the transmission line.
• Is compatible with all fiber types.
SRS results in energy from shorter wavelengths transferring to longer

wavelengths (energy is conserved). For this reason, chosen Raman pump
wavelengths are typically shorter (offset by roughly 100 nm) from the C-Band
traffic-carrying wavelengths to which Raman gain is to be applied.
• Raman Gain is provided at essentially any wavelength, depending on the
availability of the pump with the added benefit of low noise figure.

• The effective span loss is reduced to improve noise performance of

transmission line.
• Raman gain improves SNR and reduces nonlinear penalty, as the same
OSNR is achieved with a smaller launch power.
Other Benefits include:

— Improved Bit Error Rate
— Longer span distances
— Increased span counts
— Prevent regeneration of channels
In general, Raman pump wavelengths can be applied in a co (same) or

counter-propagating (reverse or opposite) direction relative to traffic-carrying
wavelengths. For the case of the 6500 SRA circuit pack, the
counter-propagating direction is used.
• The counter-propagating Raman pumps are typically located immediately
prior to the line receiving pre-amplifier (EDFA).
• The optical gain is dependent on the physical attributes of the fiber span
and the SRA pump power.
Raman amplification is intrinsically a low noise gain mechanism, providing

approximately 0-24 dB gain on standard single-mode fiber.
• Note that a 10 dB Raman gain is not the same as a 10 dB span loss
reduction from a link budget perspective. The effective span loss reduction
benefit is much less. The real figure of merit is the system gain
improvement.
Figure 3-76
Counter-propagating Raman gain overview

Single Line Raman amplifier (SRA)

Overview
The NTK552JA SRA circuit pack is a line facing module. It provides 4 Raman
pumps that serve to provide amplification within the fiber plant. The SRA
offers a distributed counter-propagating Raman amplifier solution which can
minimize the impact of long, highly lossy spans in multi-span applications.
The SRA has a built-in OTDR feature which runs traces on the fiber plant to
provide specifications to software so then it can decide upon a set of
Go/No-Go criteria to turn on or not the Raman pumps for safety and
performance reasons. The OTDR feature also runs traces when there is a
fiber cut to locate the fault (see “Overview” on page 3-134).
The SRA circuit pack also has a mode of communication called the Telemetry
Gain (TG) Mode. This mode does not replace the OSC mode, but adds
another communication channel for SRA circuit packs to synchronize their
decision to turn on or not.
The decision to deploy an SRA circuit pack is specific to the link over which
equipment is planned to be deployed. Understanding the network topology,
traffic patterns, expected growth and typical reach requirements is essential
to determine if Raman has value in a network.
Some links may be favorable candidates for a specific Raman application. For
instance, the SRA:
• can reduce network regeneration when deployed on specific long and
lossy spans which are impacting the overall system reach and forcing
regeneration points;
• provides gain across the entire C-band spectrum with the ability to
flatten/adjust the gain profile across the entire spectrum (and also
provides some limited gain to the OSC channel);
• may be required to support longer span lengths in some network
applications.
OnePlanner is used to provide link budget designs for Raman applications

over specific fiber types.

Figure 3-77
SRA overview
SRA circuit pack details

The NTK552JA SRA circuit pack:
• Provides Distributed Raman amplification and OTDR functionality out of
Line A In (Port 8). The Raman pumps are counter-propagating.
• Is always used in conjunction with the XLA (Switchable Line Amplifier)
circuit pack.
• Supports an integrated OSC SFP port with OSC add/drop filters and
add/drop ports. The OSC functionality for SRA configurations is not part
of the regular LIMs (LIM, SLA, MLAx) nor 2xOSC or SPAP2 with 2xOSC
2xSFP circuit packs.
• Is only used in a domain that contains CPL/6500 ROADM nodes and
CPL/6500 Line Amp nodes.
• Follows a calibration process to flatten the gain and optimize the Raman
gain based on fiber characteristics.
— This procedure is software controlled but can be user-initiated, if
required.
• Outputs a maximum power of 1 watt (achieved using 4 pumps totaling
+30 dBm). The following pump wavelengths are used:
— Pump 1 = 1424 nm
— Pump 2 = 1465 nm
— Pump 3 = 1455 nm

— Pump 4 = 1434 nm
• Provides 0-24 dB of Raman gain, depending on the fiber type.
• Is rated Hazard Level 1M, but features Automatic Power Reduction (APR)
capabilities to handle high return loss conditions at the Raman amplifier
output ports (see “Raman safety mechanisms (Pump shutoff, ALSO,
APR)” on page 2-81).
• Provides an integrated OTDR subsystem to evaluate the integrity of the
fiber plant and any interconnections. The OTDR provides measurements
used in a Go/No Go decision tree by the software, to determine if the
Raman pumps can be turned on or should remain off, whether at SLAT or
after a fiber cut has been repaired (see “SRA OTDR Go/No-Go criteria
and decision process” on page 5-26 for full details).
— The OTDR signal (1527.22 nm) is transmitted through the Line A In
port (Port 8).
— For a full description of the OTDR function, refer to “Optical Time
Domain Reflectometer (OTDR)” on page 3-134.
• Has external tap monitor ports at outputs of each line facing direction (Line
A Mon and Line B Mon), which can be used to connect an OSA, if
required.
— The OPM of the node connects to the XLA circuit pack.
SRA OAM&P
From a OAM&P perspective:
• Full topology and DOC support is provided for the SRA.
• Two communication modes are supported and required:
— OSC Mode: an OSC channel using 1511 nm (CWDM) or 1517 nm
(DWDM) is offered. Use of either wavelength depends on the span
loss. Required for DOC and topology to function.
— Telemetry Gain (TG) Mode: A 1527.22 nm telemetry channel is
provided, which is the same channel as the OTDR signal described
above. Software turns TG on and off depending on the function
required. Required to turn on or off Raman pumps.
The SRA Raman pumps are shut off based on the absence of the
Telemetry Gain (TG) and OSC signals.
• The following Total Power PMs are provided:
— Line A RAMAN facility (OPOUT, OPIN, ORLIN, ORLOUT, OPROSC)
— Line B OPTMON facility (OPR)
— OSC OPTMON facility (OPR)
The SRA supports fast PM tide-marking on OSC and line-facing ports.

• Supports Delay measurements on the OSC facilities similar to 2xOSC

circuit pack.
Operational considerations when using SRA

The following operational considerations apply when using the SRA circuit
pack:
• Automatic Line Shut Off (ALSO) is supported provided the OSC is present
and functioning.
— ALSO “automatic recovery” requires that OSC is provisioned and
functional.
• Stretched spans without OSC present are currently not supported for
safety reasons.
• The OSC and the Telemetry Gain channels are always functioning
whether the Raman pumps are on or off.
• The SRA circuit pack must be deployed in both directions of an optical link
- always bookended.
• The SRA is a separate circuit pack which can be replaced without
changing the EDFA (e.g. XLA).
• Line system splicing is not required for SRA deployments (LINE A In Port
8 is connectorized).
• Strict guidelines are required to deploy the SRA circuit pack. The fiber
plant and patch panels must be of a certain quality otherwise the Raman
pumps do not turn on.
• The default primary state of the Raman facility is In-Service (IS).
For additional circuit pack details, refer to Technical Publication

323-1851-102.6, Photonics Equipment. For all facility details on this circuit
pack, refer to Technical Publication 323-1851-310/311, Configuration -
Provisioning and Operating.
Enhanced Service Access Module (ESAM)

ESAM circuit pack details
The NTK552JT ESAM circuit pack:
• Is a line-facing module.
• Provides an Optical Time Domain Reflectometer (OTDR) function to
evaluate the integrity of the span fiber plant and any interconnections (see
“Optical Time Domain Reflectometer (OTDR)” on page 3-134).
• Can be used in conjunction with the XLA (Switchable Line Amplifier) or
MLAx (Mid-stage Line Amplifier) circuit pack.

• Supports an integrated OSC SFP port with OSC add/drop filters and
add/drop ports. The OSC functionality for ESAM configurations is not part
of the regular LIMs (LIM, SLA, MLAx) nor 2xOSC or SPAP2 with 2xOSC
2xSFP circuit packs.
• Is rated Hazard Level 1M.
• Provides an integrated OTDR subsystem to evaluate the integrity of the
fiber plant and any interconnections.
— The OTDR signal (1527.22 nm) is transmitted through the Line A In
port (Port 8).
— For a full description of the OTDR function, refer to “Optical Time
Domain Reflectometer (OTDR)” on page 3-134.
• Has external tap monitor at outputs of each line facing direction (Line A
Mon and Line B Mon).
— These monitor ports may connect to an OSA, if required.
— The OPM of the node is connected to the XLA or MLAx circuit pack.
ESAM OAM&P
• Full topology and DOC support is provided for the ESAM.
— Line A OPTMON facility (OPR)
The ESAM supports fast PM tide-marking on OSC and line-facing ports.
• It also supports Delay measurements on the OSC facilities similar to
2xOSC circuit pack.
Operational considerations when using the ESAM

The following operational considerations apply when using the ESAM circuit
pack:
• The ESAM supports the ALSO mechanism in conjunction with the
XLA/MLAx circuit pack when both are paired within an OTS.
— ALSO “automatic recovery” on the XLA/MLAx only works when OSC
is provisioned. If OSC is not present then manual steps are required.
• The ESAM provides PMs, and Gauge TCA alarms are raised accordingly
(refer to “OTDRCFG facility Gauge Threshold Crossing Alert (TCA) alarm”
on page 3-143). Thresholds are editable at the OTDRCFG facility level,
while Gauge TCA alarms raise and clear based on the OTDRCFG facility
PMs.


pack, refer to Technical Publication 323-1851-310 Configuration - Provisioning
and Operating.
Service Access Module (SAM)

SAM circuit pack details
The NTK552JN SAM circuit pack:
• Is a line-facing module.
• Provides an OSC Tx/Rx and OSC filter function. It is similar to the 6500
NTK552DA C-Band LIM circuit pack, but includes the integrated OSC
function.
• Is rated Hazard Level 1M
• Has external tap monitor at outputs of each line facing direction (Line A
Mon and Line B Mon).
— These monitor ports may connect to an OSA, if required
— The OPM of the node connects to the XLA/MLAx circuit pack
• Can be used in conjunction with the XLA or MLAx circuit pack.
ESAM OAM&P
• Full topology and DOC support is provided for the SAM.
— Line A OPTMON facility (OPR)
The SAM supports fast PM tide-marking on OSC and line-facing ports.
• The SAM supports Delay measurements on the OSC facilities similar to
2xOSC circuit pack.
Operational considerations when using the SAM

The following operational considerations apply when using the SAM circuit
pack:
• The SAM supports the ALSO mechanism in conjunction with the
XLA/MLAx circuit pack when both are paired within an OTS.
— ALSO “automatic recovery” on the XLA/MLAx only works when OSC
is provisioned. If OSC is not present then manual steps are required.


pack, refer to Technical Publication 323-1851-310, Configuration -
Provisioning and Operating.
Optical Time Domain Reflectometer (OTDR)

Overview
OTDR characterization of a fiber plant is used for estimating the fiber length
and overall attenuation within a link, including splice and mated connector
losses. It may also be used to locate faults, such as breaks, and to measure
optical return loss or reflection. The OTDR function is also commonly used for
fault finding on installed systems.
The standard being followed by Ciena for the development of OTDR

functionality is Telcordia GR-196 (Generic Requirements for Optical Time
Domain Reflectometer (OTDR) Type Equipment). GR-196 specifies the
minimum requirements, specifications and methodologies used to perform
OTDR measurements.
The OTDR feature transmits a sequence of optical pulses into the fiber plant.
It recovers a signal that is scattered (via the Rayleigh backscattering
phenomenon) or reflected back from event locations along the fiber.
The OTDR feature provides:

• Installation protection for RAMAN spans:
— Due to the high power on the SRA circuit pack, some caution has to
be placed before any Raman pumps are enabled. Reflection and Loss
events as characterized by OTDR are used in the Go/No-Go decision
process for turning the Raman pumps on (see “SRA OTDR Go/No-Go
criteria and decision process” on page 5-26 for details).
— To avoid damaging connectors and/or fiber plant, the OTDR
characterizes fiber loss and verifies the connectors and splices from
circuit pack equipment through patch panels and the fiber plant. This
ensures the Raman gain is optimal and that there are no high
reflections that could damage connectors or splices.
• Effectiveness:
— OTDR characterization can provide the location of a fiber cut in the
case of a fiber break. This can be done remotely, without the use of an
external test set, and enables the dispatching of a team as quickly as
possible to the location of the fault.
— OTDR characterization is facilitated by the use of viewable OTDR trace
files provided in the Telcordia standard ‘.SOR’ file format.
• A method to capture variations in the fiber plant:

— OTDR traces can be used to capture variations in the fiber plant over
time by comparing Day 1 OTDR traces with current day traces. The
T-Series OTDR feature allows users to tag an OTDR trace as a
baseline trace and raise the “Gauge Threshold Crossing Alert
Summary” alarm when the current trace key events exceed
user-defined thresholds.
OTDR traces
The OTDR output is a trace and the OTDR software analyzes the trace for
discontinuities.
• These are flagged as “events” in terms of type (loss/reflection), distance
and magnitude. Possible events include:
— reflective events
— non-reflective events
— clipped (or saturated) reflective events
• The number of events, and their parameters are not constant over time.
For example, a perfect trace will have zero events, while a pinched fiber
span may suddenly report an event, which could subsequently clear by
itself (or because someone fixed it). A new event could be raised at a new
location.
OTDR traces can be obtained in one of two modes - Automated or Manual:

• Automated OTDR traces are triggered by:
— Single fiber cut
— Recovery from single fiber cut
— Dual fiber cut
— Recovery from dual fiber cut
— Turn up/SLAT
— Circuit pack power up (after circuit pack replacement, re-insertion, or
power cycle/brownout recovery)
To gather information from an OTDR trace in case there is a fiber break
during a software upgrade, currently running or new automatic OTDR
traces are allowed to complete during the upgrade. Only the latest OTDR
trace during upgrade is recorded. The trace is shown as the current trace.
• Manual OTDR traces:
— These traces can be run with no managed channels (Out-of-Service)
or with managed channels (In-Service). See “Operational
considerations for OTDR feature” on page 3-148.
Manual trace requests are rejected during a software upgrade.

For automatic traces, three traces are run in each instance (Office, Short and
Long). This allows the location of the cut and subsequent repair splice to be
determined. For manual traces, either an Office, a Short or a Long trace can
be run. Traces are classified in the following manner:
• S/D-Series: ‘Office’ is <= 8 km, ‘Short’ is <= 32 km, ‘Long’ is > 32 km
• T-Series: ‘Office’ is <= 8 km, ‘Short’ is <= 15km, ‘Long’ is > 15 km
The OTDRCFG facility (for S/D-Series SRA and ESAM and T-Series RLA
circuit packs) contain the following data used to run an OTDR trace:
• Pulse width
• Fiber length
• Acquisition time
Note that automatic OTDR traces on the SRA and ESAM circuit packs use
hard-coded values for these parameters, based on fiber type and distance.
The Site Manager Equipment & Facility Provisioning and Optical Time
Domain Reflectometry applications use pre-defined pulse width and distance
combinations for OTDR traces. This prevents the use of pulse width and
distance combinations that would yield noisy OTDR traces rendering them
unusable. The TL1 interface allows a wider set of OTDR pulse width and
distance combinations.
The OTDR trace short/long pulse width and distance parameter defaults
should not be altered unless more detailed troubleshooting is required to
analyze an event. If the OTDR trace short/long pulse width and distance
parameters are altered for troubleshooting purposes, it is recommended that
these parameters be changed back to the default values after the
troubleshooting has been completed and new traces be run with the default
settings. For T-Series, after the traces have run successfully, the traces should
be baselined.
For S/D-Series SRA and ESAM circuit packs, the OTDR channel is the same
as that used for the Telemetry Gain (TG) channel (1527.22 nm). Traces are
run in the counter-propagating direction only, out of port 8.
For T-Series, the OTDR functionality is provided by connecting the OTDR4

module to the RLA module as shown in Figure 3-78 on page 3-137. One
OTDR4 module can be connected to up to 4 RLA modules providing
bidirectional monitoring for up to 4 degrees. As a result of the OTDR4
hardware design, an OTDR trace can run only on 1 of the 8 individual fiber
spans at a time. Automatic traces have priority over manual traces.

On the OTDR4 module, two OTDR channels are available so that traces can
be run in both co- and counter-propagating directions. The 1625.00 nm
channel is used for the co-propagating trace and the 1527.22 nm channel is
used for the counter-propagating trace (see figure below). Using the default 1
minute acquisition time, it takes at least 16 minutes per OTDR4 module to
cycle through all 4 degrees (4 ports x 2 wavelengths x 2 pulse widths). At the
node level, up to 4 OTDR traces can be run in parallel provided they are
originating on 4 different OTDR4 modules. The shelf stores 32 traces per
OTDR module ([Baseline & current traces] x [short & long traces] x 2
wavelengths x 4 degrees).
Figure 3-78
6500 T-Series OTDR solution
The 6500 hardware includes an internal fiber spool to help resolve faceplate
issues. The SRA or ESAM internal fiber spool length prior to the faceplate
connector is 30 m. The OTDR4 and RLA also have 30 m of internal fiber as
shown in the figure above.
OTDR specifications for S/D-Series (SRA and ESAM) are defined in the table
below.

Table 3-12
OTDR S/D-Series specifications
S/D-Series
Office Trace Short Trace Long Trace

Objective Detection of back Detection of back Measure fiber losses
reflections close to the reflections close to the over the entire span
launch point of the launch point of the
Raman pump, including Raman pump
faceplate connector
Target Range 2km 20km 120km (80km)

(Note 1)
Open end detection resolution 4m 4m 15m

accuracy
Event detection resolution 2m 2m 20m

accuracy
Event Dead Zone (Note 2) 10m (50m) 100m (300m) 4km (10km)
Note 1: Events are detectable at up to 80 km for the long trace. If an open connector exists at longer
distances (high reflection), the event can be detected at up to 120 km.
Note 2: The event dead zone is defined as the distance after a reflection event where any additional
event(s) cannot be resolved. These values are the theoretical values and will be displayed on the trace
properly. The values in the “(x)” are the minimum spacing between events what the Ciena algorithm will
calculate and provide information on the event.

OTDR specifications for T-series (OTDR4) are defined in the table below.
.
Table 3-13
OTDR T-Series specifications
T-Series
Short Trace Long Trace

Objective Detection of back reflections close to the Measure fiber losses over the entire span
faceplate connector
Target Range 20 km 120 km
Open end detection 3 m up to 16 km 12 m up to 120 km

resolution accuracy
Event detection 2 m up to 8 km 12 m up to 120 km

resolution accuracy
Event Dead Zone (Note See Table 3-14 on page 3-140

2)
Note 1: Events are detectable at up to 80 km for the long trace. If an open connector exists at longer
distances (high reflection), the event can be detected at up to 120 km.
Note 2: The event dead zone is defined as the distance after a reflection event where any additional
event(s) cannot be resolved.

The event spacing required for the Ciena algorithm to detect and raise a report
for an OTDR event are defined in the table below.
Table 3-14
OTDR minimum event spacing requirements
Pulse width Minimum Event Spacing (meters)
10 ns 30
30 ns 35
100 ns 50
300 ns 100
1 us 300
3 us 700
10 us 2200
20 us 4400
40 us 10000
Viewing OTDR traces

The Site Manager Optical Time Domain Reflectometer application allows you
to run manual OTDR traces and to download SOR files. The ‘.SOR’ file format
is defined in Telcordia SR-4731 (version 2), Optical Time Domain
Reflectometer (OTDR) Data Format.
The Site Manager OTDR Graph View application allows you to display the
OTDR traces graphically. The application also includes the following
functionalities:
• Ability to display traces stored on the shelf or on your PC
• Panning and zooming capabilities
• Can add 2 markers to be able to select any two points on the graph and
get details
• Loading and removing of multiple SOR files, SOR file details are arranged
as “tabs” that can be switched between
OTDR traces (standards compliant ‘.SOR’ files) stored on a PC file system

can also be accessed with third party viewers. However, it is recommended to
use the Site Manager OTDR Graph Viewer application, because it accounts
for the 30 m internal fiber spool within the 6500 OTDR4, SRA, and ESAM
equipment. The OTDR Graph Viewer application properly offsets the internal
fiber spool so that the 0 meter marker is positioned at the 6500 equipment

faceplate. Third party viewers are not aware of the internal fiber spool and will
not display the faceplate properly and may not provide accurate event
locations.
Attention: The Ciena OTDR event locater may not display properly on the
OTDR graph compared to the actual location of the event. Therefore when
looking at the OTDR Graph viewer, you will notice that the event lines are
about X m away from the actual event, where X depends on the pulse width
being used. Therefore, if using the event log for reporting, double check the
actual location of the event on the OTDR graph using the markers.
Using Photonic Network Capture (PNC), the reflection events (distance and
attenuation) are available via TL1 for current and baseline traces.
OTDRCFG PMs
The following OTDR trace event summary PM data is provided for OTDRCFG
facilities on T-Series RLA 20x1 circuit packs, SRA, and ESAM:
• Event count for short and long traces
• Max. event loss/reflections for short and long traces
• Cumulative event loss/reflections for short and long traces
The PMs are event driven rather than polling based like traditional PMs. They
are collected for Short and Long traces after each OTDR trace completes
(note that as 10ns traces can create false events, they are excluded from any
PM binning). The 15-min, 24-hr and Untimed PM bins are used to track the
data.
Note also the following regarding these PMs:

• Baseline PMs:
— It is recommended to set the baseline PMs using the default Go/No-Go
parameters. Otherwise, a trace executed with other pulse/distance
parameters may raise false Gauge TCA alarms, the comparison being
performed on a different basis.
— If the baseline trace is a clean trace (i.e. no events detected), then no
data is displayed to the user in baseline PMs.
• The Untimed PM bin contains the OTDRCFG trace data PMs for the last
trace, i.e. the Untimed PM bin data is overwritten with the latest data from
the current OTDR trace.
• PM store and return the “current” new and maximum values for each PM
monitor type. The MAX value is the maximum value for the monitor type
from the last shelf restart, or from the last time the Untimed bin was reset.

• The current 15-MIN and current 1-DAY PM bins contains the “current” and
maximum values for the PM monitor types calculated over the interval.
• PMs support OTDRCFG threshold provisioning (see “OTDRCFG facility
Gauge Threshold Crossing Alert (TCA) alarm” below). As usual, this is
supported via updating PM Profiles and assigning a PM profile to a
provisioned OTDRCFG port facility. PM profile modification and threshold
setting survive SP restarts and software upgrades.
• The OTDRCFG PM TCA alarm always compares the Untimed values with
the Baseline values. As a result, if the trace types are taken in different
scenarios (for example, SRA when Raman pumps are IS or OOS), false
OTDRCFG PM TCA alarms may be generated.
For a detailed description of each OTDRCFG PM, refer to Technical

Publication 323-1851-520, Fault Management - Performance Monitoring.
OTDR alarming
OTDRCFG facility ‘Line A Input OTDR High Loss Detected’ and ‘Line A Input
OTDR High Reflection Detected’ alarms
These alarms are only raised on the SRA, against the OTDRCFG facility (the
ESAM and RLA 20x1 instead provide PMs, see “OTDRCFG facility Gauge
Threshold Crossing Alert (TCA) alarm”). Thresholds are editable at the
OTDRCFG facility (see table below for default values and ranges).
For a greenfield deployment, the alarms are evaluated based on the Office
and Short trace results. In a brownfield deployment, only the Short trace
results are considered. In either case, once a baseline is set, Gauge TCA
alarms are raised if there is any loss/reflection event that exceeds the
corresponding threshold compared to the PM baselines. Note that for the
Short trace, an OTDR high loss/reflection detected alarm masks the Gauge
TCA alarms.

Table 3-15
Raman OTDR provisioning thresholds for Go/No-Go criteria
Parameter Provisioning Range [dB] Notes
Min Default Max
Loss Single Event 0.0 0.5 1.5 Maximum value is based on potential damage.
Single loss event is above the fiber loss per km.
Gainers are not part of the Go/No-Go calculations.
Only value that can be validated by Modeling Tool
(see Note1).
Loss All Events 0.0 1.0 3.0 Maximum value is based on performance
degradation. Gainers are part of the Go/No-Go
calculations as Total loss calculation includes both
positive and negative loss events.
Reflection Single -27.0 -33.0 -40.0 Minimum value based on GR-196. Maximum value
Event based on what can be detected and makes sense.
Reflection All -24.0 -27.0 -40.0 Minimum value based on GR-196. Maximum value
Events based on what can be detected and makes sense.
Note 1: For the Office trace, the SRA faceplate connector event has a higher loss threshold than the
provisioned value in the OTDRCFG, since it has to factor in the internal loss of the circuit pack and the
faceplate connector itself. Therefore if the Go/No-Go check has passed then the faceplate event is below
the required threshold value.
OTDRCFG facility Gauge Threshold Crossing Alert (TCA) alarm

Whether on S/D-Series or T-Series, the “Gauge Threshold Crossing Alert
Summary” alarm is raised if any of the following conditions are exceeded for
either short or long trace on the SRA, ESAM and T-Series RLA 20x1 circuit
packs. Thresholds are defined in PMs:
• Single point loss threshold (MAXEVLxx-OTS)
• Single point reflection threshold (MAXEVRxx-OTS)
• Cumulative loss threshold (CUMEVLxx-OTS)
• Cumulative reflection threshold (CUMEVRxx-OTS)
Thresholds are defined in terms of a deviation in dB (or delta) from the

baseline. They can be user-defined (defaults are detailed in Table 3-16 on
page 3-145). Baseline PMs are updated when traces are tagged as baselines.
User needs to make sure the current trace is using the same pulse as baseline
to see correct alarms. A single alarm is raised when any of the above four
parameters exceeds the threshold (in either direction) and clears when all
monitored parameters are below the threshold.
• If the maximum event reflection and cumulative event reflection is below
the respective provisioned “OTDR Reflection Per Event” and “OTDR
Reflection All Events” thresholds for the RLA OTDRCFG facility, then

these events do not feed into the “Gauge Threshold Crossing Alert
Summary” alarm evaluation. This is done to ensure that the alarms are
raised to point to events where user resolution is required. No such
restrictions exist for loss events.
• Information about the Gauge TCA alarm is located under
Faults->Historical Fault Browser. Look for the unit ‘OTDRCFG-SH-SL-PT’,
Severity = ‘Log’, Description = ‘Untimed Threshold Crossing’. The
‘Condition type’ indicates which parameters are triggering the alarm.
• If no OTDRCFG baseline event is currently recorded, then no TCA
evaluation is performed.
• PM TCAs are evaluated against the threshold supported PM parameters
of an OTDRCFG facility:
— following an OTDRCFG trace to an OTDRCFG facility;
— following an OTDRCFG baseline update to an OTDRCFG facility;
— every 15-MIN bin rollover interval time on the hour clock (00, 15, 30,
45);
— following an in-service edit to an OTDRCFG facility OTDR reflection
parameter;
— following a modification to a PM OTDRCFG profile file that is assigned
to an OTDRCFG facility.
• The PM TCA event AO specifies which monitor type has deviated by a
positive or negative delta from its baseline value by the threshold amount
• Once the OTDRCFG PM monitor type has returned within the threshold
range for its set baseline on a subsequent trace, the TCA alert is internally
cleared for the parameter, and is re-armed.
• If all PM threshold parameters for the facility fall within their allowable
range, the accompanying Gauge TCA Summary alarm is also cleared.
• The loss/reflection Gauge TCA alarms do not block traffic recovery nor
DOC functionality.

Table 3-16
OTDR Gauge TCA alarm thresholds
Event Short Trace Long Trace
Gauge Threshold Crossing Gauge Threshold Crossing

Alert Summary alarm Alert Summary alarm
Threshold Threshold
Loss Single 1.0 dB 1.0 dB

PM monitor type = MAXEVLSH and
MAXEVLLG
Loss Cumulative 2.5 dB 2.5 dB

PM monitor type = CUMEVLSH and
CUMEVLLG
Reflection Single 3.0 dB 3.0 dB

PM monitor type = MAXEVRSH and
MAXEVRLG
Reflection Cumulative 3.0 dB 3.0 dB

PM monitor type = CUMEVRSH and
CUMEVRLG
T-Series automatic OTDR examples

Single fiber cut
In this scenario (see figure below), the OTDR modules on both ends of the link
complete any OTDR traces in progress and then switch to the span with the
cut.
• The traces upstream and downstream of the cut are performed in parallel
• The upstream trace is triggered by the Automatic Shutoff (assuming it can
run, i.e., 1527 nm trace isn’t already running on that module)
• The downstream 1625 nm trace is triggered by the Automatic Shutoff and
runs only when the 1527 nm trace has completed
Viewing both traces together helps to isolate the fault. The same traces run
when the fault clears.

Figure 3-79
6500 T-Series OTDR single fiber cut example
Double fiber cut

In this scenario (see figure below), the OTDR modules on both ends of the link
complete any OTDR traces in progress and then switch to the span with the
cut.
• The traces upstream and downstream of the cut are performed in parallel
• The Automatic Shutoff condition will want to trigger a 1625 nm trace, but
can’t because it is pre-empted by the 1527 nm trace
Figure 3-80
6500 T-Series OTDR double fiber cut example - step 1
The 1625 nm traces are triggered when the 1527 nm traces complete (see
figure below).
Viewing both traces together (for each separate span) helps to isolate the
fault. The same traces run when the fault clears.

Figure 3-81
6500 T-Series OTDR double fiber cut example - step 2
Understanding T-Series short traces

See figure below for an example of a 10 ns short trace. See Figure 3-83 on
page 3-148 for an example of a 30 ns short trace.
Figure 3-82
6500 T-Series OTDR 10 ns short trace

Figure 3-83
6500 T-Series OTDR 30 ns short trace
Operational considerations for OTDR feature

The following operational considerations apply to SRA and ESAM OTDR:
• The OTDR function is supported on the SRA and ESAM circuit packs.
• Manual OTDR traces can be run on the SRA and ESAM
— Out-of-Service OTDR (no managed channels):
– SRA and ESAM to locate connector loss or reflection issues
— In-Service OTDR (managed channels):
– SRA: a visual detection of a fiber pinch while the Raman pumps
are on can be performed.
Note 1: Use of the In-Service OTDR feature with the SRA can only be
relied upon for visual inspection. Meaning that with the pumps on, fiber
pinches can be detected with the OTDR graph view.
Note 2: Due to the SRA Raman gain signature, events cannot be relied
upon. SRA In-Service OTDR long traces won’t provide reflective or
loss events. Short traces likely won’t provide such events either.
– ESAM: the detection of span loss changes and loss or reflective
events can be provided.
• During an OTDR trace, the OSC channel stays on. The TG channel turns
off to allow OTDR to use the same channel to perform the trace. Once the
trace is completed, then the TG turns back on.

• The upstream amplifier is ideally shut off for OTDR traces, such as when
determining the fiber cut location. This avoids crosstalk or leakage of
power.
• When fibers of different core sizes are spliced together, the OTDR detects
a large loss. The Mode Field Diameter (MFD) loss is not a real loss but is
a loss as detected by the OTDR trace software and may cause the SRA
Go/No-Go to fail.
— The Go/No-Go algorithm is modified to mitigate however, the OTDR
traces will show the high loss with no adjustment/mitigation.
Distributed ROADM
Normally at a N-way branching node, the shelves containing the N OTSs are
all co-located. In some cases, it may be useful to distribute the OTS shelves
over a larger area while maintaining all the functionality of a branching node.
This is called a distributed ROADM node.
Since the branching node requires the OTS shelves to be TID-consolidated

(see “6500 TID Consolidation” on page 4-141), an alternate method to ILAN
port daisy-chaining is needed. One method makes use of directly
interconnected OSC facilities, whereas each “distributed” shelf is equipped
with additional OSC facilities that communicates with the other distributed
shelves via dedicated fiber pairs as shown in the figures below. An OSPF
circuit is provisioned against these OSC facilities such that routing across the
node can occur similarly to any other ILAN/OSC interface in the photonic
network.
Careful planning of the fiber plant is required. Two fiber pairs are required
between each OTS shelf:
• One fiber pair carries the passthrough DWDM traffic.
• One fiber pair carries the DCN OSC traffic normally carried across the
ILAN 100Base-T.
Engineering guidelines
The following engineering guidelines apply to distributed ROADM nodes:
• The loss between the WSS circuit packs must be less than 3 dB
(approximately 10 km).
• It is recommended to use the NTK592NP SFP for the OSC link between
the distributed shelves. If another SFP type is used (such as
NTK592NB/NH/NG/NV), additional padding between the OSC Rx and Tx
is required.
• There is no need to directly interconnect all of the distributed shelves using
an additional OSC facility. For example, in Figure 3-85 on page 3-151, no
OSC connections exist between the shelves at Site 1 and Site 3.

Communications between these shelves are routed through Site 2.

However, a direct OSC link between Site 1 and Site 3 could be provisioned
for redundancy.
• The OSC facilities used for data communications between the distributed
shelves are not provisioned as belonging to an OTS.
• DOC must be informed of the loss of the fiber pair linking non-co-located
WSS circuit packs. The fiber tail loss must be measured (at 1550 nm) and
provisioned as the excess loss (EXCESSLOSS) parameter of the
ADJ-FIBER facility for both WSS Demux Out ports.
• The RLA 5x1 supports distributed ROADM applications.
• Not supported for CDC ROADM nodes.
Figure 3-84
Distributed ROADM application (2-way branching node)
Shelf 1 Shelf 2
OSC OSC
OSC CMD CMD OSC

OTS1 OTS1

Figure 3-85
Distributed ROADM application (3-way branching node)
Shelf 1 Shelf 2
OSC OSC
OSC CMD CMD OSC

OTS1 OTS1
CMD
OSC
OSC
OTS1 Shelf 3
Remote CMD44
In this application, the remote CMD44 is manually provisioned at the local site
but is physically located at a remote site. This application can be helpful in
situations where the transponder shelves are located away from the 6500
photonic shelves, on a different floor in the same building for example. Only
one fiber pair per direction is needed to link the transponder and photonic
shelves instead of one pair per wavelength per direction. Also, since the
CMD44 is a passive module that can literally “sit on a table” at the remote site,
its allocated footprint is kept very minimal.
The following lists the operational considerations for this application:

• The application is fully supported by DOC.
— DOC must be informed of the loss of the fiber pair linking the WSS and
remote CDM44 (fiber tail). The fiber tail loss must be measured (at
1550 nm). The fiber tail loss must be provisioned as the excess loss
(EXCESSLOSS) parameter using:

– The ADJ-FIBER-TX and ADJ-FIBER-RX facilities of the CMD44

channel ports. (See “Provisioning Extra Loss in ROADM OTS” on
page 5-13).
– For Remote CMD44 applications, refer to “Provisioning Extra Loss
in ROADM OTS” on page 5-13.
• Any remote CMD44 must be manually provisioned as part of the OTS
located at the site of the photonic shelves (“local” site) against one of the
virtual slots (91-99 for 7-slot or 14-slot shelf or 63-82 for a 32-slot).
— No auto-inventory of the remote CMD44 is possible.
• CMD44 TX and Rx adjacencies must be provisioned just as in the case
where the CMD44 is local.
• One fiber pair per remote CMD44 module is required.
• The application supports both the 100 GHz and 50 GHz CMD44 modules
as shown in the figures below.
— no local add/drop with 100 GHz CMD44
– if for a given direction the CMD44 is set to be local (remote), then
no channels can be added/dropped remotely (locally) in that
direction as there can’t be two 100 GHz CMD44 connected to the
same WSS
– tail loss supported depends on the transponder receiver sensitivity.
Typically 2.5 dB (~10 km) when using transponder circuit packs
that have receiver sensitivity of about -16 dBm or 10 dB (~40 km)
when using transponder circuit packs that have receiver sensitivity
of about -25 dBm. Please submit an OPNET request to determine
the exact tail loss supported for your application.
— half-band local add/drop with 50 GHz CMD44
– each direction can have the Red (or Blue) CMD44 physically
located at the local site and the Blue (or Red) physically located at
the remote site
– tail loss supported depends on the transponder receiver sensitivity.
Typically 4 dB (~15 km) when using transponder circuit packs that
have receiver sensitivity of about -16 dBm or 12 dB (~50 km) when
using transponder circuit packs that have receiver sensitivity of
about -25 dBm. Please submit an OPNET request to determine
the exact tail loss supported for your application.
• Data communications to the remote 6500 transponder shelf can be
achieved using a direct DCN connection to the shelf COLAN port or using
the GCC/DCC of a channel.

• SPLI can be used if there is no 6500 Photonic shelf at the remote site. In
this case, it is recommended to provision the transponder shelf with the
same site ID as the shelves at the local site.
• Note that OnePlanner does not support Remote CMD44 applications.
Custom link engineering is required.
Figure 3-86
Remote CMD44 100GHz application
OSC Local site OSC
LIM WSS WSS LIM
CMD44 CMD44
100 GHz 100 GHz
Remote site

Figure 3-87
Remote CMD44 50GHz application
OSC Local site OSC
LIM WSS WSS LIM
Blue Blue
CMD44 CMD44
Red Red
CMD44 CMD44
Remote site
Standalone OPM C-Band 2-Port circuit pack (NTK553PA)

The Optical Power Monitor (OPM C-Band) 2 Port circuit pack (NTK553PAE5)
provides the ability to monitor and report the per-wavelength channel powers
on the 50 GHz ITU grid across the entire C-band.
C-Band 2-port OPM with Enhanced CMD44 50 GHz modules

The standalone OPM circuit pack is used for interconnection to up to two
Enhanced CMD44 50GHz modules:
• Enhanced CMD44 50 GHz C-Band (Blue) (NTT862BCE5)
• Enhanced CMD44 50 GHz C-Band (Red) (NTT862BDE5)
The Enhanced CMD44 50 GHz C-band modules each provide a passive 5%

tap added on the Common Out port. This tap is accessible via the Monitor Out
port (port 92) and can be monitored with either an external OSA or the
Standalone 50 GHz OPM 2-port circuit pack.
Connecting an external OSA to the eCMD44 monitor port provides a check

point for transponder circuit pack Tx powers connected to the eCMD44. If the
transponder circuit pack Tx wavelength and Tx power are properly

provisioned and the transponder is properly fibered to the eCMD44, the

wavelength is visible on the external OSA. The OSA power is approximately
13-15 dB lower than the actual power.
Connecting the NTK553PA 50 GHz OPM 2-port circuit pack to the eCMD44
monitor port provides the same check point and installers can validate
connections between transponders and the eCMD44 without the need to
provision eCMD44 TX/RX adjacencies or add the channel in DOC. It is only
required to ensure the eCMD44 has been provisioned in the OTS and to
provision the eCMD44 Monitor port (port 92) to OPM port (port 1 or 2)
adjacency using Site Manager Configuration->Equipment & Facility
Provisioning application. The corresponding adjacency at the OPM port is
auto-derived.
Power levels are accessible via the CHMON/OPTMON PMs.

• CHMON facilities provide per channel power info and instant graphical
view for all 44 channels, similar to an OSA. The CHMON PM is the
estimated per channel power level at the output of the eCMD44 (Common
Out port). Software automatically accounts for the tap loss, providing a
more accurate reading than an external OSA.
• OPTMON facilities for the Channel In ports provide power info for each
eCMD44 Channel In port and helps debugging Tx power consistency
issues between transponder Tx port and eCMD44 Channel In port. The
OPTMON PM is the estimated channel power level at the input of the
eCMD44 (Channel In port). Software automatically accounts for the tap
loss and the eCMD44 insertion loss, providing a more accurate reading
than an external OSA.
• Additionally, PM software continuously monitors power level of
transponders and the standard tools are available to monitor fluctuations
(ie. PM Trend graphing or Gauge TCA alarms to indicate if the power level
is stable or drifts over time).
C-Band 2-port OPM at Line Amp nodes

capabilities, via CHMON PM’s, for troubleshooting purposes.
The OPM circuit pack provides 2 optical connections to the embedded OPM
to be monitored on demand at any port.
• These 2 optical connections connect to the monitor ports of LIM circuit
packs at a Line Amp node.
• Power measured at OPM is scaled and reported against the LIM circuit
pack port 5 or 7 CHMON facilities.

• The OPM circuit pack also provides 2 output optical connections for user
monitoring of the input ports. These ports can be connected to external
OSA to validate the OPM measured powers (if necessary) via 50% tap
from each monitor port.
— The calibrated loss (~3 dB) from Port 1 to 3 and from Port 2 to 4 is
programmed in the CCT and displayed in Site Manager.
— You can then use the calibrated loss to add up with the external OSA
measurements in order to relate the measured spectra back at the
OPM faceplate.
• CHMON power time-variant data for each port is provided by Site
Manager through the PM and PM graphing applications or can be
retrieved using TL1.
Operational considerations for Line Amp nodes with C-Band 2-port OPM
The following operations considerations apply to 6500 Line amp
configurations with the C-Band 2-port OPM.
• DOC does not use the power monitoring capabilities for optimization
purposes.
• The OPM circuit pack provides updated data for all ports within 1 second.
• The OPM circuit pack provides per channel as well as total band power
monitor capability for each OPM port.
— Per-channel power reporting is achieved through the usual CHMON
facilities.
— CHMON provides per channel power info and instant graphical view
for all 96 channels similar to an OSA at LIM Line B Out port (port 5)
and LIM Line A Out port (port 7).
— The CHMON power values are scaled to these ports by properly
considering the LIM tap loss and OPM circuit pack loss.
— The CHMON power monitor accuracy is +/- 1 dB.
The feature allows the NTK553PA OPM to be connected to available monitor

ports on the following LIM circuit packs including the XLA, MLA3, MLA2,
MLA2v, MLA, SLA and LIM at Line Amp nodes.
For photonic site engineering details, shelf configuration and circuit pack rules
associated with this application, refer to “Photonic Line Amplifier node with
OPM” on page 4-131.

Figure 3-88
NTK553PA C-Band 2-port OPM
C-Band 2-port OPM connections to LIMs at ROADM and TOADM nodes

The NTK553PA 50 GHz OPM C-Band 2-port circuit pack can be provisioned
at ROADM and TOADM nodes. This enables per-channel power monitoring
capabilities, via CHMON PM’s at these nodes for troubleshooting purposes.
• The OPM provides high accuracy readings of Submarine Line Idler Card
(SLIC) and ASE channel holder powers within Submarine Line
Terminating Equipment (SLTE) configurations.
• The standalone OPM is used to connect to the monitor ports of the
wet-plant facing LIM in configurations using standard SLTE (e.g. ROADM
OTS provisioned) or hybrid SLTE (ROADM and TOADM OTSs
provisioned)
For photonic site engineering details, shelf configuration and circuit pack rules
associated with this application, refer to “Standalone 50 GHz 2-port OPM
when connected to available LIM monitor ports at ROADM or TOADM nodes”
on page 4-126.
2-port OPM as generic spectrum monitoring device

The 2-port OPM can also be connected to a monitor port of any type (Ciena
or not) to give a view of a C-Band spectrum. You can either use the NTK553PA
OPM or the NTK553PB Flex OPM in Fixed Grid mode. In both cases:
• Powers are reported through the CHMON PMs against the OPM port
• The same PM bins as existing CHMON PMs (min, max, trending) are
supported, as well as setting of baseline and Gauge TCA events
• OPM spectral bins remain 50 GHz-spaced, centered on the 50 GHz ITU
grid
To monitor channels with a different spacing (i.e. not a multiple of 50 GHz) or

not centered on the ITU grid, use the Flex OPM in Flexible Grid mode. Refer
to the Technical Publication NTRN15DA.3, Photonic Layer Guide, Part 3 for
details.

Provisioning guidelines
The following provisioning guidelines must be followed when setting up this
configuration:
• The OPM used in such a configuration is not part of any slot sequence.
• User needs to provision the OPM port(s) with ‘OPM’ ADJ Type, and with
the Far-End Address pointing to itself.
• A power reading offset can be provisioned via the Excess Loss parameter
associated to the ADJ-FIBER facility type of the target OPM port. This
allows power readings to be compensated for the monitor tap loss to ease
troubleshooting. Ideally the tap loss should be characterized using a light
source.
Optical protection switching using the OPS circuit pack

Overview
The following hardware is available:
• NTK554TA 4xOptical Protection Switch (4xOPS C-Band 1xOPSM2)
circuit pack
• NTK576AA 2xOptical Protection Switch module (OPSM2 C-Band)
This single slot circuit pack provides 1+1 linear unidirectional optical layer
protection similar to what is offered by the ETS (Enhanced Trunk Switch).
However, unlike the ETS which is rack-mounted on its own, the OPS is
inserted in the 6500 shelf, and hence from an OAM&P perspective, is fully
integrated.
The automatic optical protection switch time of the device (Rx selector) is less
than 15 ms. Restoration time of the underlying client service at the higher
layers (e.g. L1, L2) depends on the application and subtending circuit pack(s).

323-1851-102.1, Common Equipment.
OPS protection architecture

OPS L0 protection switching operates in a fashion that is based on the
protection architecture defined in G.873.1 (i.e. 1+1 Linear APS protection at
OTN layer 1).
The OPS circuit pack has 2 fixed optical protection groups and 2 pluggable
protection groups which are mounted on a sub-slot.
• Each group has six unidirectional ports (common, SW1, SW2). Refer to
figure below.

• In the transmit direction, the signal is divided into two optical streams by a
splitter and goes out on both SW1 and SW2 ports.
— This is a standard head-end bridge defined in a 1+1 protection
scheme, where the normal traffic signal is permanently bridged to
protection
• In the receive direction, the SW1 and SW2 Rx signals are selected by an
optical switch based on optical power and provisioned LOS thresholds.
— At the tail-end, the OPS operates as per any 1+1 unidirectional
protection-switching architecture - a Rx selector makes a decision
according to defects and commands received at the tail end
Since the OPS is using a splitter to perform a permanent head-end bridge, no
bidirectional switching is offered by the circuit pack.
— For bidirectional switching to happen, co-ordination between the

head-end bridge and tail-end Rx selector is necessary in order to
ensure that traffic is bridged at the head-end onto only one path (the
same path that the tail-end Rx selector is using), but this is not
currently supported.
Figure 3-89
Optical Protection Switch (OPS)
Loss of DC Power feature

The OPS has a provisionable parameter - “Loss of DC Power” mode - which
provides a consequent action to a loss of DC power. This is described in the
table below.

Table 3-17
OPS response to loss of DC power
Loss of DC Power OPS consequent action if loss of DC power occurs

mode setting
No (Default) Latches at present state
Yes If SW1 is the active switch port before the loss of DC a switch to SW2 occurs
power
If SW2 is the active switch port before the loss of DC no switch occurs
power
• Upon power-up, traffic remains on SW2 until fault conditions are evaluated
(software does not automatically switch traffic to SW1 on power-up).
• This feature is useful only if the 4xOPS is powered independently of the
Protection-side equipment (see Figure 3-90 on page 3-160).
Figure 3-90
OPS response to loss of DC power

OPS provisioning
Site Manager provides a comprehensive set of OPS OAM&P TL1 commands
for provisioning and alarm/event notifications. SNMP commands are also
supported, but only for alarm/event notifications.
Common 6500 alarms and provisioning support is extended to the OPS as

follows:
• The protection groups (FFP) are auto-created when the circuit pack or
circuit pack pluggable are provisioned.
• Switch state depends upon a combination of External (user-defined) and
Automatic (signal-defined) requests.
• Protection group latches to the current state if there is an equipment
failure.
• A request is accepted only if the new request has a higher or equal priority
than the most recently accepted request.
Externally initiated switch commands include:
• Release: User releases switch from any implemented external command
• Lockout of Protection: User wants the switch state to select SW-1 until
released
• Forced switch: User wants the switch to remain in the specified state.
Manual and Automatic switch requests are denied.
• Manual switch: User wants to switch to a specified path if there is no
conflicting Forced Switch or Lockout command or signal failure on the
requested port. May be overwritten by an automatic Signal Fail switch.
Automatic switching behaviour is the result of a Photonic layer signal failure.
In the Signal Fail condition, the OPS automatically switches from failed to valid
path (based upon LOS state, which is declared according to provisioning
optical power threshold), only if there is no conflicting Forced Switch or
Lockout command.
The revertive switching mode is supported on the OPS. If enabled, and a fault
causes the OPS to switch away from the failed path, then:
• The OPS switches back to the original path after the failed path’s LOS has
cleared for x consecutive minutes, where x = provisioned ‘Wait to Restore’
time.
• An external switch request (Manual Switch, Forced Switch, Lockout)
disables revertive switching and discards any scheduled WTR request:
• Subsequent Release does not re-enable revertive switching – it remains
disabled.

Attention: Revertive switching is applicable only to switches caused by

signal failure (SF) on SW1. When enabled, the reversion is from SW2 to SW1
x minutes after the SF fault on SW1 RX clears.
OPS optical path protection options

The optical switch can be placed in different locations to provide path and
equipment protection. The OPS can be used in the various applications
described in the subsections that follow:
• “Client-layer optical path protection and operational considerations” on
page 3-162
• “Optical Channel (OCH) path protection and operational considerations”
on page 3-162
• “Span layer path protection and operational considerations” on page
3-163
For topology related concepts pertaining to the OPS applications mentioned
above, refer to “Optical Protection Switch (OPS) circuit pack topology” on
page 1-70.
Client-layer optical path protection and operational considerations

For the client-layer optical path protection application, the OPS is placed
between 6500 client ports and subtending equipment (see figure below). For
more information, refer to Technical Publication 323-1851-315 Configuration -
Figure 3-91
OPS Client layer optical path protection
Optical Channel (OCH) path protection and operational considerations

For the Optical Channel (OCH) path protection application, the OPS is placed
between 6500 transponder line ports and a CMD, as per figure below. For
more information, refer to Technical Publication 323-1851-315 Configuration -
Protection Switching, and the Traffic protection chapter.

Figure 3-92
OPS Optical Channel (OCH) path protection
Span layer path protection and operational considerations

For the Span layer path protection application, the OPS is placed after a
ROADM OTS, as shown in the example below. Note that the protected span
could be an intermediate span part of a multiple-span link. Other
configurations and more information are provided in Technical Publication
323-1851-315 Configuration - Protection Switching, and the Traffic Protection
chapter.
Figure 3-93
OPS Span layer path protection: ROADM OTS
Transceiver-Triggered OPS protection

In the protection schemes involving the OPS described above, automatic
protection switching is induced when Loss of Signal is detected at a switch
input port, i.e. when the power level at this switch input port falls below a
user-defined threshold level. When used in the Optical Channel (OCH) Path
Protection application (Figure 3-92 on page 3-163), this limits the support to
colored Photonic configurations, as only the presence of a single optical
channel at the OPS SW input guarantees that the loss of the channel would
be unambiguously detected and trigger the desired switch. Therefore,
colorless Photonic configurations, where many channels can potentially come
out of the same Channel Out port and contribute to total power, cannot use
the LOS-based OPS protection scheme as is.

The Transceiver-Triggered OPS mechanism (TT-OPS) aims at extending the

OPS protection capabilities to such colorless Photonic configurations. It does
so by allowing a Transceiver to provide feedback to the OPS, triggering a
receiver fault-based switch even in the presence of multiple channels.
More information on TT-OPS can be found in the Technical Publication

323-1851-315 Configuration - Protection Switching, and 323-1851-102.1,
Common Equipment.

Photonic Engineering Rules 4-
This chapter describes 6500 Packet-Optical Platform (6500) photonic

engineering rules.
Table 4-1
Topic
“Link engineering and capacity” on page 4-3
— “C-Band wavelength plans” on page 4-5
— “100 GHz SCMD4 deployment rules” on page 4-14
— “Deployment guidelines for mixing 2150/4200 and 6500 100 GHz filters” on page 4-20
— “Per-wavelength validation feature” on page 4-24
— “Supported Transmitter/Receiver types for 6500 Photonic layer” on page 4-28
— “Foreign (alien) wavelength use over 6500 Photonic Layer” on page 4-33
“OTS engineering rules” on page 4-34
— “Channel access nodes of ROADM subtype” on page 4-35
— “Line Amp nodes of AMP OTS subtype” on page 4-36
— “Channel access node of TOADM OTS subtype” on page 4-37
— “Channel access node with DIA OTS subtype” on page 4-38
— “Channel access node with Colorless OADM OTS subtype” on page 4-38
— “General slot sequence engineering rules” on page 4-40
— “Slot sequence rules for OTSs using SRA/XLA and ESAM/SAM/XLA/MLAx” on page 4-40
“DOC engineering rules” on page 4-42
— “DOC deployment rules” on page 4-42
— “Photonic domain segmentation” on page 4-43
“DOC Power Audit (Calibration) engineering rules specific to Raman applications” on page 4-48
“Photonic node engineering and shelf configuration rules” on page 4-48
— “General considerations” on page 4-48
— “Wavelength provisioning considerations” on page 4-49
— “Line Adjacency Fiber Type provisioning with mixed fiber types” on page 4-50
— “Extended depth brackets/doors when using attenuator pads” on page 4-50

4-2 Photonic Engineering Rules
Table 4-1
Topic
— “Colored Directional 1-way ROADM Terminal” on page 4-51
— “Colored Directional higher degree (e.g. 2-way, 3-way, up to 8-way) ROADM/Metro ROADM” on
page 4-78
— “ROADM/Metro ROADM with Mux Amp” on page 4-103
— “Dynamic Gain Flattening Filter (DGFF) using 2-way ROADM” on page 4-111
— “Colored Directionless” on page 4-111
— “Colorless Directionless” on page 4-113
— “Colorless Directional or Colorless Direct Attach (CDA)” on page 4-114
— “Low channel count Colorless Directionless” on page 4-115
— “Low channel count Colorless Directionless and Colored Directional using 9x1 WSS” on page
4-116
— “Colorless Directional or Colorless Direct Attach (CDA) using 20x1 WSS, FIM Type 4, FIM Type 5
and FIM Type 6” on page 4-116
— “Colorless, Directionless and Contentionless (CDC)” on page 4-117
— “T-Series Colorless, Directionless and Contentionless (CDC)” on page 4-119
— “OPM engineering rules” on page 4-125
— “Photonic Line Amplifier node” on page 4-127
— “SCMD4 based Thin Terminal or TOADM” on page 4-140
— “6500 TID Consolidation” on page 4-141
— “Shelf ID and Site ID Numbering” on page 4-143
— “Branching engineering rules” on page 4-144
— “Engineering rules related to Mode 1 capacity change mode” on page 4-149

Link engineering and capacity

The following table indicates the maximum channel capacity for the various
OTS configurations offered in the 6500 platform.
Wavelengths must adhere to the ITU G.698.1 narrow 50 GHz and 100 GHz
specification. In the Ciena portfolio, these include 50 GHz and 100 GHz
wavelengths designated to operate on the 6500 Photonic Layer spectral grid
(see “C-Band wavelength plans” on page 4-5).
Table 4-2
Maximum capacity for different OTS subtypes
OTS channel Filter detail Maximum channel

access config capacity
subtype
C-Band L-Band
ROADM Backbone or Metro ROADM with 6500 CMD44 100 GHz 44 -
Metro ROADM, 6500 OMD4 100 GHz 36 -
Metro ROADM, 2150 OMDF4/OMDF8/BS5 40 -
Backbone ROADM with 6500 CMD44 50 GHz 88 -
Backbone ROADM with CCMD12 direct attach (CDA) 96 -
CDC ROADM with CCMD8x16 96 -
T-Series CDC ROADM with CCMD 16x12 96 -
T-Series CDC ROADM with CCMD 8x4 44 -
TOADM SCMD4 cascades 36 -
DIA 6500 CMD44 100 GHz 44 -
6500 CMD44 50 GHz 88 -
COADM 8x1 50 GHz SMD with CCMD12s 88 -
8x1 50 GHz Flex SMD with CCMD12s 96 -
Supported line rates

The 6500 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)
• 2.7 Gbit/s (OTU1)
• 10 Gbit/s (OC192/STM64/10GE WAN PHY)
• 40 Gbit/s (OC768/STM256/OTU3)

• 50 Gb/s (one of two subcarriers for 100G Flex 2 WL3 OCLD OTU4
configured in 2C-BPSK mode)
• 100 Gbit/s (OTU4)
• 200 Gbit/s (OTUC2)
• 10.7, 11.05, 11.09 Gbit/s (OTU2)
• 10.3, 11.1 Gbit/s (10 GE LAN PHY)
• 11.27 Gbits/s (FC-1200)
Reach
Typical system reach is greater than 3000 km without dispersion
compensation and using erbium-doped fiber amplifier (EDFA) technology
covering core, regional, and edge applications.
For more information on system reach under various link budget conditions,
for interfaces such as the WL3 contact your Ciena account representative.
Supported fiber types

The 6500 Photonic layer architecture supports multiple fiber types including:
• Non-Dispersion Shifted Fiber (NDSF)
• Non-Dispersion Shifted Fiber Low Water Peak (NDSF LWP)
• TrueWave Classic
• Lambda Shifted Single Mode Fiber (LS)
• Dispersion Shifted Single Mode Fiber (DSF)
• TrueWave Reduced Slope (TWRS)
• TrueWave Plus (TWP)
• Large Effective Area Fiber (LEAF)
• Enhanced Effective Area Fiber (ELEAF)
• Freelight (FL)
• Allwave (AW)
• Teralight
• Pure Silica Core
• Truewave Reach
• TeraWave ULL
• EX2000

Link design tools

From a link design perspective:
• Ciena OnePlanner must be used to create 6500 link designs. OnePlanner
is part of the Network Design Tools suite.
For applications that fall outside the scope of the above tools, contact your
Ciena account representative to obtain a detailed custom link design through
the Ciena OPNET team.
C-Band wavelength plans

The 6500 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 6500 Photonic layer can support:
• 44 channels on the 100 GHz ITU grid
— See the full wavelength plan in Table 4-3 on page 4-6, applicable to
100 GHz CMD44, 100 GHz SCMD4 and 100 GHz OMD4.
• 88 channels or 96 channels (configuration and hardware dependent) on
the 50 GHz ITU grid
— See the full 88-channel wavelength plan in Table 4-3 on page 4-6,
applicable to 50 GHz CMD44.
— See the full 96-channel wavelength plan in Table 4-4 on page 4-10,
applicable to 50 GHz CMD96 and colorless CMDs (for example,
CCMD12, CCMD8x16, CCMD 16x12 and CCMD 8x4).
• 64 channels on a fixed 75 GHz grid (only deployable in flex grid
applications only)
— See the full 64-channel frequency plan in Table 4-5 on page 4-10,
applicable to the 75 GHz CMD64.
Ciena 6500/5400/8700/Waveserver high-speed interfaces available for use on

6500 colored, colorless and CDC line systems support a tuning range that
encompasses the 6500 photonic layer 96-channel 50 GHz grid range:
• 1528.77 nm (196.10 THz) to 1566.72 nm (191.35 THz)

Attention: The 6500 Photonic layer out-of-band CWDM OSC wavelength is

1511 nm, which is shorter than the blue edge of the 6500 EDFA bandwidth.
Table 4-3
6500 and 2150/4200 filter modules referenced to 6500 C-Band ITU-T 50 GHz
88-channel plan
100 GHz OMDF Part #
100 GHz OMDF Part #

100 GHz Channel #
100 GHz Channel
SCMD4 or OMD4
SCMD4 or OMD4
CMD44 100 GHz
CMD44 100 GHz
PEC and Group

Plan Channel #
CMD44 50 GHz
88 Wavelength
Wavelength
Frequency
4200 4-Ch
4200 8-Ch
100 GHz
Channel
C-Band
C-Band
4200
[THz]
[nm]
PEC
PEC
195.90 1530.33 1 1 1 59
195.85 1530.72 2 N/A N/A N/A
NTK508AAE5 (SCMD4)
NTK504AAE5 (OMD4)
B-720-0020-031
Group A High
195.80 1531.12 3 3 3 58
1531.51 4
Group 1
195.75 N/A N/A N/A
195.70 1531.90 5 5 5 57
195.65 1532.29 6 N/A N/A N/A
B-720-0022-001
195.60 1532.68 7 7 7 56
NTT862FAE5 Enhanced (eCMD44) 100 GHz
Group A
Skip 
NTT862BAE5 CMD44 50 GHz (Blue)
195.55 1533.07 8 N/A N/A N/A

NTT862AAE5 CMD44 100 GHz or
195.50 1533.47 9 9 Skip  55
195.45 1533.86 10 N/A Skip  N/A
B-720-0020-030
Group A Low
195.40 1534.25 11 11 11 54
195.35 1534.64 12 N/A N/A N/A

NTK508ABE5 (SCMD4)
NTK504ABE5 (OMD4)
195.30 1535.04 13 13 13 53
1535.43 14
Group 2
195.25 N/A N/A N/A
195.20 1535.82 15 15 15 52
195.15 1536.22 16 N/A N/A N/A Skip 
195.10 1536.61 17 17 17 51 Skip 
195.05 1537.00 18 N/A N/A N/A Skip 
1537.40 19 Skip 
B-720-0020-029
B-720-0022-002
195.00 19 50
Group B High
Group B
194.95 1537.79 20 N/A Skip  N/A
194.90 1538.19 21 21 21 Grp 3 49

Table 4-3
88-channel plan (continued)
100 GHz OMDF Part #
100 GHz OMDF Part #

100 GHz Channel #
100 GHz Channel
SCMD4 or OMD4
SCMD4 or OMD4
CMD44 100 GHz
CMD44 100 GHz
PEC and Group

Plan Channel #
CMD44 50 GHz
88 Wavelength
Wavelength
Frequency
4200 4-Ch
4200 8-Ch
100 GHz
Channel
C-Band
C-Band
4200
[THz]
[nm]
PEC
PEC
194.85 1538.58 22 N/A N/A N/A
B-720-0020-029
Group B High
NTK508ACE5 (SCMD4)
194.80 1538.98 23 23 23 48
NTK504ACE5 (OMD4)
194.75 1539.37 24 N/A N/A N/A
Group 3
194.70 1539.77 25 25 25 47
194.65 1540.16 26 N/A N/A N/A Skip 
B-720-0022-002
Group B
194.60 1540.56 27 27 27 46
194.55 1540.95 28 N/A N/A N/A
B-720-0020-028
Skip 
Group B Low
194.50 1541.35 29 29 45
194.45 1541.75 30 N/A Skip  N/A
NTT862BAE5 CMD44 50 GHz (Blue)
194.40 1542.14 31 31 31 44
194.35 1542.54 32 N/A N/A N/A

NTK508ADE5 (SCMD4)
NTK504ADE5 (OMD4)
194.30 1542.94 33 33 33 43
1543.33 34 Skip 
Group 4
194.25 N/A N/A N/A
194.20 1543.73 35 35 35 42 Skip 
194.15 1544.13 36 N/A N/A N/A Skip 
194.10 1544.53 37 37 37 41
194.05 1544.92 38 N/A N/A N/A

B-720-0020-027
Group C High
194.00 1545.32 39 39 Skip  40

B-720-0022-003
193.95 1545.72 40 N/A Skip  N/A

Group C
1546.12 41
NTK508AEE5 SCMD4
193.90 41 41 39
NTK504AEE5 OMD4
193.85 1546.52 42 N/A N/A N/A

Group 5
193.80 1546.92 43 43 43 38
193.75 1547.32 44 N/A N/A N/A N/A

Table 4-3
100 GHz OMDF Part #
100 GHz OMDF Part #

100 GHz Channel #
100 GHz Channel
SCMD4 or OMD4
SCMD4 or OMD4
CMD44 100 GHz
CMD44 100 GHz
PEC and Group

Plan Channel #
CMD44 50 GHz
88 Wavelength
Wavelength
Frequency
4200 4-Ch
4200 8-Ch
100 GHz
Channel
C-Band
C-Band
4200
[THz]
[nm]
PEC
PEC
193.70 1547.72 45 45 45 37
NTK508AEE5
NTK504AEE5
1548.11 46
Group 5
193.65 N/A N/A N/A
B-720-0020-026
B-720-0022-003
Group C Low
193.60 1548.51 47 47 47 36
Group C
193.55 1548.91 48 N/A N/A N/A
193.50 1549.32 49 49 Skip  35
193.45 1549.72 50 N/A Skip  N/A
193.40 1550.12 51 51 51 34

193.35 1550.52 52 N/A N/A N/A Skip 
NTK508AFE5 (SCMD4)
NTK504AFE5 (OMD4)
NTT862BBE5 CMD44 50 GHz (Red)
193.30 1550.92 53 53 53 33 Skip 
1551.32 54 Skip 
Group 6
193.25 N/A N/A N/A
193.20 1551.72 55 55 55 32
193.15 1552.12 56 N/A N/A N/A
B-720-0020-025
Group D High
193.10 1552.52 57 57 57 31
193.05 1552.93 58 N/A N/A N/A
193.00 1553.33 59 59 Skip  30
B-720-0022-004
192.95 1553.73 60 N/A Skip  N/A
Group D
192.90 1554.13 61 61 61 29
Skip 
NTK508AGE5 (SCMD4)
192.85 1554.54 62 N/A N/A N/A

NTK504AGE5 (OMD4)
192.80 1554.94 63 63 63 28
Group 7
B-720-0020-024
Group D Low
192.75 1555.34 64 N/A N/A N/A
192.70 1555.75 65 65 65 27
192.65 1556.15 66 N/A N/A N/A
192.60 1556.55 67 67 67 26

Table 4-3
100 GHz OMDF Part #
100 GHz OMDF Part #

100 GHz Channel #
100 GHz Channel
SCMD4 or OMD4
SCMD4 or OMD4
CMD44 100 GHz
CMD44 100 GHz
PEC and Group

Plan Channel #
CMD44 50 GHz
88 Wavelength
Wavelength
Frequency
4200 4-Ch
4200 8-Ch
100 GHz
Channel
C-Band
C-Band
4200
[THz]
[nm]
PEC
PEC
192.55 1556.96 68 N/A N/A N/A
Group
Grp D
Low
D
192.50 1557.36 69 69 Skip  25
192.45 1557.77 70 N/A Skip  N/A Skip 
192.40 1558.17 71 71 71 24 Skip 
192.35 1558.58 72 N/A N/A N/A Skip 
NTK508AHE5 (SCMD4)
NTK504AHE5 (OMD4)
192.30 1558.98 73 73 73 23

1559.39 74
Group 8
192.25 N/A N/A N/A
NTT862BBE5 CMD44 50 GHz (Red)
B-720-0020-023
Group E High
192.20 1559.79 75 75 NTT862AAE5 CMD44 100 GHz or 75 22
192.15 1560.20 76 N/A N/A N/A
192.10 1560.61 77 77 77 21
192.05 1561.01 78 N/A N/A N/A
B-720-0022-005
192.00 1561.42 79 79 Skip  20
Group E
191.95 1561.83 80 N/A Skip  N/A Skip 
191.90 1562.23 81 81 81 19
191.85 1562.64 82 N/A N/A N/A

NTK508AJE5 (SCMD4)
NTK504AJE5 (OMD4)
B-720-0020-022
1563.05 83
Group E Low
191.80 83 83 18
1563.45 84
Group 9
191.75 N/A N/A N/A
191.70 1563.86 85 85 85 17
191.65 1564.27 86 N/A N/A N/A
191.60 1564.68 87 87 87 16
191.55 1565.09 88 N/A N/A N/A Skip 
191.50 1565.50 N/A N/A N/A N/A Skip  N/A Skip 
191.45 1565.90 N/A N/A N/A N/A Skip  N/A N/A

Table 4-4
6500 C-Band ITU-T 50 GHz 96-channel plan
Channel number Wavelength (nm) Frequency (THz)
93 1528.77 196.10
94 1529.16 196.05
95 1529.55 196.00
96 1529.94 195.95
01-88 (see Note 1) 1530.33 - 1565.09 195.90 - 191.55
89 1565.50 191.50
90 1565.90 191.45
91 1566.31 191.40
92 1566.72 191.35
Note 1: For complete listing, refer to Table 4-3 on page 4-6.
Table 4-5
64-channel plan
Channel Frequency Wavelength Channel Frequency Wavelength

number [THz] [nm] number [THz] [nm]
1 196.0875 1528.87 33 193.6875 1547.82
2 196.0125 1529.46 34 193.6125 1548.41
3 195.9375 1530.04 35 193.5375 1549.01
4 195.8625 1530.63 36 193.4625 1549.62
5 195.7875 1531.21 37 193.3875 1550.22
6 195.7125 1531.80 38 193.3125 1550.82
7 195.6375 1532.39 39 193.2375 1551.42
8 195.5625 1532.98 40 193.1625 1552.02
9 195.4875 1533.56 41 193.0875 1552.62
10 195.4125 1534.15 42 193.0125 1553.23
11 195.3375 1534.74 43 192.9375 1553.83
12 195.2625 1535.33 44 192.8625 1554.44

Table 4-5
Channel Frequency Wavelength Channel Frequency Wavelength

number [THz] [nm] number [THz] [nm]
13 195.1875 1535.92 45 192.7875 1555.04
14 195.1125 1536.51 46 192.7125 1555.65
15 195.0375 1537.10 47 192.6375 1556.25
16 194.9625 1537.69 48 192.5625 1556.86
17 194.8875 1538.28 49 192.4875 1557.46
18 194.8125 1538.88 50 192.4125 1558.07
19 194.7375 1539.47 51 192.3375 1558.68
20 194.6625 1540.06 52 192.2625 1559.29
21 194.5875 1540.66 53 192.1875 1559.90
22 194.5125 1541.25 54 192.1125 1560.50
23 194.4375 1541.84 55 192.0375 1561.11
24 194.3625 1542.44 56 191.9625 1561.72
25 194.2875 1543.04 57 191.8875 1562.33
26 194.2125 1543.63 58 191.8125 1562.95
27 194.1375 1544.23 59 191.7375 1563.56
28 194.0625 1544.82 60 191.6625 1564.17
29 193.9875 1545.42 61 191.5875 1564.78
30 193.9125 1546.02 62 191.5125 1565.39
31 193.8375 1546.62 63 191.4375 1566.01
32 193.7625 1547.22 64 191.3625 1566.62
Note: The CMD64 module has its labels in frequency only. Wavelengths are
provided here for reference.

Table 4-6
Unavailable channels for CMD44 or SCMD4/OMD4 combinations
CMD44 Combination Unavailable 50 GHz Channels
CMD44 100 GHz and Total of 22 unavailable channels

CMD44 50 GHz Blue 2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38,4
0,42,44

CMD44 50 GHz Red 46,48, 50,52,54,56,58,60,62,64,66, 68 70,72,74,76,78
80,82,84,86,88

CMD44 50 GHz Blue and 2,4,6,8,10,12,14,16,18,20,22,24,26,28,30,32,34,36,38,4
CMD44 50 GHz Red 0,42,44, 46,48, 50,52,54,56,58,60,62,64,66,68, 70,72,74,
76,78 80,82,84,86,88
SCMD4 or OMD4 with 50 GHz CMD44 Red and Blue - Unavailable 50 GHz channels
[SCMD4 or OMD4 with 100 GHz CMD44 - Unavailable 100 GHz channels]
SCMD4 or OMD4 Group 1 2,4,6,8,9,10

[9]
SCMD4 or OMD4 Group 2 9,10,12,14,16,18,19,20

[9,19]
SCMD4 or OMD4 Group 3 19,20,22,24,26,28,29,30

[19,29]
SCMD4 or OMD4 Group 4 29,30,32,34,36,38,39,40

[29,39]
SCMD4 or OMD4 Group 5 39,40,42,44,46,48,49,50

[39,49]
SCMD4 or OMD4 Group 6 49.50,52,54,56,58,59,60

[49,59]
SCMD4 or OMD4 Group 7 59,60,62,64,66,68,69,70

[59,69]
SCMD4 or OMD4 Group 8 69,70,72,74,76,78,79,80

[69,79]
SCMD4 or OMD4 Group 9 79,80,82,84,86,88

[79]

Deployment guidelines when mixing 50 GHz and 100 GHz nodes

The following engineering guidelines must be considered with mixing 50 GHz
and 100 GHz ROADM channel access nodes in a Photonic network:
1 All WSS/RLA circuit packs must be of the same “grid” at a node.
— “50 GHz node”: mix of 50 GHz WSS (9x1 and 2x1) circuit packs
allowed
— “100 GHz node”: mix of 100 GHz WSS (5x1, 4x1 and 2x1) circuit packs
allowed
— The NTK553RA 5x1 RLA operating in fixed grid mode can interwork
with any 50 GHz WSS variant or any Flex WSS variant except the 20x1
WSS or the T-Series NTK722AA 20x1 RLA. In this release, the
NTK553RA 5x1 RLA cannot interwork with any 100 GHz WSS variant
when the RLA is operating in fixed grid mode. See Part 3 of this
document for NTK553RA 5x1 RLA interworking with other WSS types
when operating in flex grid mode.
2 At a “100 GHz” node, you can only deploy 100 GHz CMD44 modules.
3 At a “50 GHz” node, you can deploy one (or two) 50 GHz CMD44 or one
100 GHz CMD44 (you cannot have a mix of CMD44 50 GHz and CMD44
100 GHz).
4 You cannot have more than one CMD44 module of each type in the same
OTS.
5 You cannot have an even-numbered 50 GHz ITU grid channel (such as
channel #2, #4, #6,…, #88) passing through a 100 GHz node.
Attention: Only guidelines #3 and 4 are enforced by the software.
See figure below for network examples.

Figure 4-1
Mixing 50 GHz and 100 GHz components: network examples
100 GHz SCMD4 deployment rules

General SCMD4 deployment rules
In general, one SCMD4 module is required per 4 wavelength add/drop group
at each node. This translates into
• 1 module per group required at a thin terminal node
• 2 modules per group required at a symmetric TOADM node when the
same group is added/dropped in both facing directions
• 1 module per group required at an asymmetric TOADM node when the
group is added/dropped in one facing direction
SCMD4 combination deployment rules

The use of channel access Thin Terminal TOADM and ROADM nodes within
the same optical network requires careful planning since the 6500 node does
not have a view of SCMD4 modules deployed in the entire network (i.e. there

is no software consistency check at the system level, only at a nodal level) and
therefore software cannot enforce the correct combination rules. These rules
are determined via OnePlanner or OPNET simulation which implements
them.
As mentioned in the prior section, if 50 GHz CMD44s are deployed in the

same optical link as 100 GHz CMD44s, then the 50 GHz spaced channels at
either side of the 100 GHz channels cannot be used. This situation is not
blocked by software nor alarmed. However, if these “illegal” channels were
optimized, it would cause interference on the neighboring 100 GHz channels.
Similar guidelines exist for the case where 100 GHz SCMD4 based Thin
OADMs are deployed with 50 GHz CMD44s (refer to Table 4-6 on page 4-12):
• The skip wavelengths associated with SCMD4 groups cannot be used
— The SCMD4 demux filters out two skip wavelengths at 50 GHz ITU-T
C-Band grid locations on either side of the passband
• For the 50 GHz 88-channel wavelength plan, the skip-wavelength
consideration implies that
— For SCMD4 group 2, 3, 4, 5, 6, 7 and 8, two skip wavelengths on either
side (4 total) of an individual group are filtered out per group used. This
means that 50 GHz grid channels 9, 10, 19, 20, 29, 30, 39, 40, 49, 50,
59, 60, 69, 70, 79 and 80 are not used.
— For SCMD4 group 1, two skip wavelengths (channels 9 and 10) are
filtered out. Note: Group 1 channels [196.00 THz, 1529.55nm] and
[195.95 THz, 1529.94nm] are also filtered out on the shorter (blue)
side of the spectrum, but these are not used by the CMD44 50 GHz
modules in the 88-channel plan.
— For SCMD4 group 9, two skip wavelengths (channels 79 and 80) are
filtered out. Note: Group 9 channels [191.50 THz, 1565.50 nm] and
[191.45 THz,1565.90nm] are also filtered out on the longer (red) side
of the spectrum, but these are not used by the CMD44 50 GHz
— For the 100 GHz 44-channel wavelength plan, the skip-wavelength
consideration is modified from the above to dictate that for SCMD4
group 2, 3, 4, 5, 6, 7 and 8, one (1) skip wavelength on either side (2
total) of an individual group are filtered out per group used. This means
that channels 9,19,29,39,49,59,69,and 79 are not used. Note: Group
1 [196.00 THz, 1529.55nm] and Group 9 [191.50 THz, 1565.50 nm]
channels are filtered out but are not used by CMD44 100 GHz
• The intermediate 50GHz channels associated with a SCMD4 group
cannot be used.

This situation is also not blocked by software. This is because DOC does not
block an optimization of the incorrect channels which could be physically
connected and provisioned at ROADM node add/drop points. However, an
“Incompatible provisioning alarm” is raised on the node where the channels
would be attenuated. If these “illegal” channels were optimized, it would cause
traffic hits on all other in-service channels. In addition, a skip channel
originating from a CMD44/ROADM that would normally be derived as
passthrough at a TOADM raises an inter-OTS “Adjacency Provisioning Error”
alarm.
Consequently, care must be taken to properly plan traffic patterns on 50 GHz

and 100 GHz ITU-T grid locations to ensure that no service disruption occurs.
Several examples illustrate this point. Refer to:

Figure 4-2
Release 12.6
Channel Access ROADM Site A Channel Access TOADM Site Channel Access ROADM Site B
LIM WSS WSS LIM LIM LIM LIM WSS WSS LIM

SCMD4 SCMD4
BMD2 Group 1 Group 1 BMD2
Red Tx/Rx Tx/Rx Red

CMD44 CMD44
West Facing East Facing
Blue Blue
Tx/Rx CMD44 Tx/Rx CMD44
Add/Drop Chs 1,3,5,7
Chs Filtered Out 2,4,6,8,9,10
Tx/Rx Tx/Rx
Lost channels
Available Channel between ROADM-A and ROADM-B
Channel numbers: 2,4,6,8
Channel Numbers 11-88
(i.e., the Group 1 intermediate
50GHz channels)
Channels available between Channels available between Channel numbers: 9,10
ROADM-A and TOADM (West) TOADM (East) ROADM-B and (i.e., the Group 1 skip channels)
1,3,5,7 1,3,5,7
SCMD4 combination deployment rules example - Symmetric TOADM using Group 1
October 2019
Figure 4-3
Release 12.6
Channel Access ROADM Site A Channel Access TOADM Site Channel Access ROADM Site B

SCMD4 SCMD4

Red Tx/Rx Tx/Rx Red

CMD44 CMD44
Blue Blue
Add/Drop Chs 61,63,65,67

Tx/Rx Tx/Rx
Chs Filtered Out 59, 60, 62,64,66,68, 69, 70
Available Channel between ROADM-A and ROADM-B Lost channels

Channel Numbers 1-58, 71-80 Channel numbers: 59,60
(i.e., the Group 6 skip channels)
Channels available between Channels available between (i.e., the Group 7 intermediate
ROADM-A and TOADM (West) TOADM (East) ROADM-B and 50GHz channels)
61,63,65,67 61,63,65,67 Channel numbers: 69,70
SCMD4 combination deployment rules example - Symmetric TOADM using Group 7
October 2019
Figure 4-4
Channel Access TOADM Site
Release 12.6
Channel Access ROADM Site A Channel Access ROADM Site B

SCMD4 SCMD4

Red Tx/Rx Tx/Rx Red
CMD44 CMD44
Blue Blue
Tx/Rx Tx/Rx
Lost channels
Available Channel between ROADM-A and ROADM-B
Channel numbers: 9,10
Channel Numbers 1-8, 21-28, 41-88
Channels available between Channels available between (i.e., the Group 2 intermediate
ROADM-A and TOADM (West) TOADM (East) ROADM-B and 50GHz channels)
11,13,15,17 31,33,35,37 Channel numbers: 19,20
(i.e., the Group 4 intermediate
50GHz channels)
SCMD4 combination deployment rules example - Asymmetric TOADM using Group 2 and 4
October 2019
Deployment guidelines for mixing 2150/4200 and 6500 100 GHz filters
A deployment mix of 6500 100 GHz filter and 2150/4200 100 GHz passive
filters within the same optical network requires careful planning.
Such a mix is possible in Metro ROADM deployments.
Proper planning and link analysis (OnePlanner or OPNET) are necessary to

ensure that non-viable channels are avoided in such scenarios. Software
checking at the equipment level is performed at the wavelength level (see
“Per-wavelength validation feature” on page 4-24).
Attention: The OMD4 should not be mixed with OMDF4/OMDF8/BS5 due

to different wavelength mappings which would result in limiting available
wavelengths.
For example, wavelength contention is possible when

• An OMDF4 is initially deployed at one node, and through the availability of
the EXPR port on the OMDF4 you decide to append the CMD44 later to
expand capacity at the same node.
• A terminal at one end uses OMDF4, OMDF8 and a BS5 module, and at
the other terminal end, a 6500 CMD44 is used.
There are specific overlapping wavelengths which are not viable on individual
2150/4200 100 GHz filters:
• 50 GHz ITU-T grid wavelengths of the 6500 88-channel plan that would be
filtered out by the same passband of the 100 GHz filter, and are not
accessible on such filters.
• Skip channels (50 GHz or 100 GHz) that are located between 4200 filter
sub-groups (e.g. A Low and A High) or between full-groups (e.g. A and B);
they fall outside the passband of the OMDF4, OMDF8 or BS filter
responses.
— These channels cannot be physically accessed using 4200 filter ports.
— The 6500 CMD44 100 GHz module however, has available channel
ports that overlap these skip channels; an attempt to use in a mixed
deployment them would have them experience a severe filter penalty.
• Duplicate wavelengths on 6500 CMD44 and 2150/4200 OMDF4, OMDF8
and BS filters.
— Use of these duplicate wavelengths on the CMD44 is not possible if
already in use through a 2150/4200 filter on the same link, and vice
versa.

Attention: Note that the 6500 channels are labelled with a different channel
# versus the 4200 channel plan as shown in Table 4-3 on page 4-6.
Supported and blocked wavelengths per 2150/4200 Filter Type are shown in
the following tables.
Table 4-7
2150 OMDF4 supported and blocked wavelengths
OMDF4 Channel numbers referenced to 6500 88-channel plan

Group [4200 channel plan]
Ch R/T (or Ch In/ Out) NTWK R/T (or EXPR R/T (or Express In/Out)
Supported Common In/Out) Blocked
Blocked
Group A High 1,3,5,7 2,4,6,8 1,2,3,4,5,6,7,8

[59,58,57,56]
Group A Low 9,11,13,15 8,10,12,14,16 8,9,10,11,12,13,14,15,16,17,18

[55,54,53,52]]
Group B High 19,21,23,25 18,20,22,24,26 16,17,18,19,20,21,22,23,24,25,26

[50,49,48,47]
Group B Low 27,29,31,33 26,28,30,32,34 26,27,28,29,30,31,32,33,34,35,36

[46,45,44,43]
Group C High 37,39,41,43 36,38,40,42,44 34,35,36,37,38,39,40,41,42,43,44

[41,40,39,38]
Group C Low 45,47,49,51 44,46,48,50,52 44,45,46,47,48,49,50,51,52,53,54

[37,36,35,34]
Group D High 55,57,59,61 54,56,58,60,62 52,53,54,55,56,57,58,59,60,61,62

[32,31,30,29]
Group D Low 63,65,67,69 62,64,66,68,70 62,63,64,65,66,67,68,69,70,71,72

[28,27,26,25]
Group E High 73,75,77,79 72,74,76,78,80 70,71,72,73,74,75,76,77,78,79,80

[23,22,21,20]
Group E Low 81,83,85,87 80,82,84,86,88 80,81,82,83,84,85,86,87,88

[19,18,17,16]

Table 4-8
2150 OMDF8 supported and blocked wavelengths
OMDF8 Group Channel numbers referenced to 6500 88-channel plan

[4200 channel plan]
Ch R/T (or Ch In/ Out) Supported NTWK R (or Common In) Blocked
Group A 1,3,5,7,9,11,13,15 2,4,6,8,10,12,14,16

[59,58,57,56, 55,54,53,52]
Group B 19,21,23,25,27,29,31,33 18,20,22,24,26,28,30,32,34

[50,49,48,47,46,45,44,43]
Group C 37,39,41,43,45,47,49,51 36,38,40,42,44,46,48,50,52

[41,40,39,38, 37,36,35,34]
Group D 55,57,59,61,63,65,67,69 54,56,58,60,62,64,66,68,70

[32,31,30,29, 28,27,26,25]
Group E 73,75,77,79,81,83,85,87 72,74,76,78,80,82,84,86,88

[23,22,21,20, 19,18,17,16]
Table 4-9
2150 BS1 supported and blocked wavelengths
Wavelengths referenced to 6500 50 GHz 88-Channel plan numbers
Group Group NTWK R/T EXPR R/T

R/T Supported Wavelengths (or Common (or Express In/Out) Blocked
In/Out) Blocked Wavelengths
Wavelengths
Group A 1,2,3,4,5,6,7,8,9,10,11,12,13, 16 1,2,3,4,5,6,7,8,9,10,11,12,13,14, 15

14, 15
Group B 19,20,21, 22,23,24, 25,26,27, 18,34 16, 17, 18, 19,20,21, 22, 23, 24, 25, 26,
28,29,30, 31,32,33 27, 28, 29, 30, 31,32, 33, 34, 35, 36
Group C 37,38,39, 40,41,42, 43,44,45, 36,52 34, 35, 36, 37, 38, 39, 40,41,42, 43, 44,
46,47,48, 49,50,51 45, 46,47,48, 49,50,51, 52, 53, 54
Group D 55,56,57, 58,59,60, 61,62,63, 54, 70 52, 53, 54, 55, 56,5 7, 58, 59, 60, 61,
64,65,66, 67,68,69 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72
Group E 73,74,75, 76,77,78, 79,80,81, 72,88 70, 71, 72 73, 74, 75, 76, 77, 78, 79, 80,
82,83,84, 85,86,87 81, 82, 83, 84, 85, 86, 87, 88

Table 4-10
Group Group NTWK R/T EXPR R/T

R/T Supported (or Common (or Express In/Out) Blocked
Wavelengths In/Out) Blocked Wavelengths
Wavelengths
Groups A Group A 16, 18,34 1,2,3,4,5,6,7,8,9,10,11,12,13,14, 15,

and B 1,2,3,4,5,6,7,8,9,10,11,12, 16, 17, 18, 19,20,21, 22, 23, 24, 25, 26,
13,14, 15 27, 28, 29, 30, 31,32, 33, 34, 35, 36
Group B
19,20,21, 22,23,24,
25,26,27, 28,29,30, 31,32,33
Groups C Group C 36,52, 54, 70 34, 35, 36, 37, 38, 39, 40,41,42, 43, 44,
and D 37,38,39, 40,41,42, 45, 46,47,48, 49,50,51, 52, 53, 54, 55,
43,44,45, 46,47,48, 49,50,51 56,5 7, 58, 59, 60, 61, 62, 63, 64, 65,
66, 67, 68, 69, 70, 71, 72
Group D
55,56,57, 58,59,60,
61,62,63, 64,65,66, 67,68,69
Table 4-11
Group R/T (In/Out) Supported Wavelengths NTWK R/T (or Common In/Out)
Blocked Wavelengths
Group A 1,2,3,4,5,6,7,8,9,10,11,12, 13,14, 15 16, 18, 34, 72, 88
Group B 19,20,21, 22,23,24, 25,26,27, 28,29,30, 31,32,33
Group E 73,74,75, 76,77,78, 79,80,81, 82,83,84, 85,86,87

Table 4-12
Group A Group B Group C Group D Group E NTWK R/T

R/T Supported R/T Supported R/T Supported R/T Supported R/T Supported (or Common
Wavelengths Wavelengths Wavelengths Wavelengths Wavelengths In/Out)
Blocked
Wavelengths
1,2,3,4,5,6,7,8, 19,20,21, 37,38,39, 55,56,57, 73,74,75, 16,18,34,

9,10,11,12,13, 22,23,24, 40,41,42, 58,59,60, 76,77,78, 36,52,54,
14, 15 25,26,27, 43,44,45, 61,62,63, 79,80,81, 70,72,88
28,29,30, 46,47,48, 64,65,66, 82,83,84,
31,32,33 49,50,51 67,68,69 85,86,87
The supported and blocked wavelengths for the 6500 OMD4 filter types are
shown in the following table.
Table 4-13
6500 OMD4 supported and blocked wavelengths
OMD4 Wavelengths referenced to 6500 50 GHz 88-Channel plan numbers

Group
Ch In/Out Common In/Out Express (Upgrade) In/Out Blocked
Supported Blocked
Group 1 1,3,5,7 2,4,6,8 1,2,3,4,5,6,7,8,9,10
Group 2 11,13,15,17 10,12,14,16,18 8,9,10,11,12,13,14,15,16,17,18,19,20
Group 3 21,23,25,27 20,22,24,26,28 18,19,20,21,22,23,24,25,26,27,28,29,30
Group 4 31,33,35,37 30,32,34,36,38 28,29,30,31,32,33,34,35,36,37,38,39,40
Group 5 41,43,45,47 40,42,44,46,48 38,39,40,41,42,43,44,45,46,47,48,49,50
Group 6 51,53,55,57 50,52,54,56,58 48,49,50,51,52,53,54,55,56,57,58,59,60
Group 7 61,63,65,67 60,62,64,66,68 58,59,60,61,62,63,64,65,66,67,68,69,70
Group 8 71,73,75,77 70,72,74,76,78 68,69,70,71,72,73,74,75,76,77,78,79,80
Group 9 81,83,85,87 80,82,84,86,88 78,79,80,81,82,83,84,85,86,87,88
Per-wavelength validation feature

The per-wavelength validation feature software ensures the prevention of
in-use or non-viable channels.
• Provisioning of a CMD Tx/Rx Adjacency is blocked if the wavelength is
already in service (passthrough or on another CMD in the OTS).

• Provisioning of a CMD Tx/Rx Adjacency is blocked if the wavelength is not

optically viable within the OTS (e.g., due to large filter penalty in skip
channel case or group being filtered out completely due to placement in
sequence).
However, equipment blocking is applied in the following instances:

• Allowing provisioning of the equipment would “filter” out an existing
in-service wavelength. Provisioning equipment in the slot sequence is
blocked.
• Allowing provisioning of the equipment would “filter” out all wavelengths
supported on an existing provisioned equipment. Provisioning of the
equipment is blocked in the Site Manager Equipment & Facility
Provisioning application since no wavelengths are viable.
This is shown in the following figures.
Figure 4-5
Per-wavelength validation example - Site view - Blocked Tx/Rx Adjacency provisioning

Figure 4-6
Per-wavelength validation example - Site view - Blocked equipment provisioning

Figure 4-7
Per-wavelength validation example - System view

Table 4-14
6500 CMD44 100 GHz channels that are duplicates of 4200 OMDF4/OMDF8 channels
OMDF4 OMDF8 Duplicate CMD44 100 GHz Channels on 6500 88-channel plan
[4200 channel plan]
Group A High Group A 1,3,5,7 [59,58,57,56]
Group A Low 9,11,13,15 [55,54,53,52]]
Group B High Group B 19,21,23,25 [50,49,48,47]
Group B Low 27,29,31,33 [46,45,44,43]
Group C High Group C 37,39,41,43 [41,40,39,38]
Group C Low 45,47,49,51 [37,36,35,34]
Group D High Group D 55,57,59,61 [32,31,30,29]
Group D Low 63,65,67,69 [28,27,26,25]
Group E High Group E 73,75,77,79 [23,22,21,20]
Group E Low 81,83,85,87 [19,18,17,16]
Table 4-15
6500 CMD44 100 GHz channels that overlap with 4200 Filter skip channels
OMDF4/OMDF8/BS Groups CMD44 100 GHz Channels on 6500 88-channel plan

[4200 channel plan]
Group A (Group A High and Low) 17 [51]
Group B (Group B High and Low) 17, 35 [51, 42]
Group C (Group C High and Low) 35, 53 [42, 33]
Group D (Group D High and Low) 53, 71 [33, 24]
Group E (Group E High and Low) 71 [24]
Supported Transmitter/Receiver types for 6500 Photonic layer

6500 Photonic layer carries DWDM wavelengths from either Ciena or third
party suppliers.
Transmitter/Receiver types supported by the 6500 Photonic layer are

provisionable as ADJ-TX/RX adjacencies on a given channel mux/demux filter
port. Refer to the Technical Publication 323-1851-310/311, Configuration -
Provisioning and Operating, for all supported Transmitter/Receiver types.
Refer to the OnePlanner User Guide to determine which of these transmitter

types is supported by the OnePlanner link engineering tool.

Non-6500 transponders connected to 6500 S/D-Series photonic layer

Refer to the 323-4001-100, “Waveserver Rx.x User Guide” and 323-4002-100
“Waveserver Ai Rx.x User Guide” for the different Transmitter/Receiver types
to use to connect to the 6500 S/D-Series Photonic layer. Note that the
Transmitter/Receiver type is automatically set when using SPLI.
The following tables show Transmitter/Receiver types to use for 5400 and
8700 that connect to the 6500 S/D-Series Photonic layer. Note that the
Transmitter/Receiver type is automatically set when using SPLI, if supported.
Use the Foreign Coherent Transmitter/Receiver type for 6500 S/D-Series,

5400, 8700 and Waveserver WL3 DWDM interfaces that connect to the 6500
T-Series Photonic layer.
Table 4-16
Tx/Rx types to use for 5400 DWDM interfaces
Ordering code Description Tx/Rx Type
134-5455-900 TSLM-2-DWMD line module Colored Optics-Regional eDC40G Modem 1xOTU3+ C-Band
134-5455-901 TSLM-2-DWMD line module - Colored Optics-ULH,

Enhanced, PMD
134-5465-900 MSLM-40G-ULH line module Colored - Optics-Enhanced

PMD
134-5456-900 TSLM-2-DWMD line module - Colorless Optics-Regional Select from the list below depending on the
Photonic configuration (colored, colorless or
134-5456-901 TSLM-2-DWMD line module - Colorless Optics-ULH, contentionless) the transponder connects to:
Enhanced PMD • eDC40G Wave-Sel Modem 1xOTU3+
C-Band (Colored)
• eDC40G Wave-Sel Modem 1xOTU3+
C-Band (Colorless)
• eDC40G Wave-Sel Modem 1xOTU3+
C-Band (Contentionless)
134-5466-900 OSLM-1-WL3 1X100GW/Integrated DWDM and OTN - Select from the list below depending on the
Regional - WL3 Photonic configuration (colored, colorless or
contentionless) the transponder connects to:
134-5466-901 OSLM-1-WL3 1X100G W/Integrated DWDM and OTN - • WL3 Modem 1xOTU4 C-Band (Colored)
Premium - WL3
• WL3 Modem 1xOTU4 C-Band (Colorless)
134-5466-903 OSLM-1-WL3 1X100G W/Integrated DWDM and OTN - • WL3 Modem 1xOTU4 C-Band
ENH PMD- WL3 (Contentionless)
• WL3 Modem 1xOTU4 C-Band (Coherent
134-5466-904 OSLM-1-WL3 1X100G W/Integrated DWDM and OTN -
Select)
Metro - WL3
134-5466-905 OSLM-1-WL3 1X100G W/Integrated DWDM and OTN -

Submarine- WL3

Table 4-16
134-5550-900 OSLM-2-Flex3-WL3e 2x100G Integrated Flex3 WL3e For QPSK (100G) operation, select from the list
Standard and OTN w/ EDFA NxOTU4 C-Band below depending on the Photonic configuration
(colored, colorless or contentionless) the
134-5550-901 OSLM-2-Flex3-WL3e 2x100G Integrated Flex3 WL3e transponder connects to:
Premium and OTN w/ EDFA NxOTU4 C-Band • WL3e Modem QPSK 1xOTU4 C-Band
(Colored)
134-5550-903 OSLM-2-Flex3-WL3e 2x100G Integrated Flex3 WL3e
Enhanced and OTN w/ EDFA NxOTU4 C-Band • WL3e Modem QPSK 1xOTU4 C-Band
(Colorless)
134-5550-904 OSLM-2-Flex3-WL3e 2x100G Integrated Flex3 WL3e • WL3e Modem QPSK 1xOTU4 C-Band
Basic and OTN w/ EDFA NxOTU4 C-Band (Contentionless)
134-5550-905 OSLM-2-Flex3-WL3e 2x100G Integrated Flex3 WL3e
Submarine and OTN w/ EDFA NxOTU4 C-Band or
For 16QAM (200G) operation, select from the

list below depending on the Photonic
configuration (colored, colorless or
contentionless) the transponder connects to:
• WL3e Modem 16QAM 2xOTU4 C-Band
(Colored)
(Colorless)
(Contentionless)
Table 4-17
154-0405-900 8700 CSLM-200-2 (2) X 100G WaveLogic 3 Nano Select from the list below depending on the
Coherent Module,1 slot width Photonic configuration (colored, colorless,
contentionless or coherent select) the
transponder connects to:
• WL3n Modem Amplified 4ASK 1xOTU4
C-Band (Coloured)
C-Band (Colourless)
C-Band (Contentionless)
C-Band (Coherent Select)
Tx/Rx adjacencies for colored, colorless and contentionless systems

Tx/Rx adjacency provisioning reflect the fact that some transponder variants
can operate on colored, colorless and contentionless Photonic lines with
different Tx/Rx power levels.

Multiple Tx/Rx adjacency types for same DWDM interface PEC on colored
systems
There are some instances in which multiple Tx/Rx adjacency types are
available to be provisioned, for the same service-layer interface PEC
operating on colored photonic systems:
• NTK530xy PEC eDCO10G circuit packs: these interfaces can be
deployed over 6500 photonic systems in one of two modes, which is
highlighted by the choice of adjacency type:
— extended dispersion mode (example: 6500 NGM (eDCO) WT 1x10GE
LAN 1x11.1G (NTK530AB). In this mode, the eDCO10G interface
OTM2 line facility is also set to the same mode in which (a) the
maximum Tx output power is 0 dBm and (b) the system is typically an
uncompensated greenfield deployment.
— extended power mode (example: 6500 NGM (eDCO) WT 1x10GE
LAN 1x11.1G EXT PWR (NTK530AB). In this mode the underlying
eDCO10G interface OTM2 line facility is also set to the same mode in
which (a) the maximum output power is +1.5 dBm and (b) the system
already has in-service channels, is compensated, and is undergoing a
capacity upgrade. The OTM2 facility in this mode takes into account
the existing dispersion provided by DSCMs.
• When the service-layer interface is capable of supporting different
signal-rates, on the line and/or client port DWDM facilities. Ports can use
either fixed-optics or DWDM pluggable modules. The Tx and Rx
Adjacency Type to be chosen manually or set by SPLI is a function of the
client service provisioned. The client signal influences the line or client
DWDM port facility provisionable parameters.
• DWDM port facility provisionable parameters to check for consistency are:
— DWDM client port or DWDM line port facility rate
– 2.5G
– 2.7G
– 4G
– 10.7G
– 11.05G
– 11.09G
– 11.27G
– Note that in most cases, the line facility is provisioned prior to the
client facility, based on the appropriate client-to-line mapping.
— DWDM client port or DWDM line port OTM facility Tx and Rx FEC
format
– RS8

– SCFEC
– Note that some FEC formats (such as PFEC on eDCO10G,
eDC40G, eDC100G interfaces, QFEC on 100G WL3 OCLDs) are
fixed. Others, such as UFEC provisioned on DWDM XFPs inserted
on NTK530PG/PM 2x10G OTR interfaces, is a provisionable
option. In either case, no current Tx/Rx adjacency is distinguished
based on the PFEC, QFEC or UFEC algorithms.
— The client port facility type influences the mapping to the line port. For
instance
– OC192/STM64 -> 10.7G OTM2
– ETH10G -> 10.7G OTM2, 11.05G OTM2, 11.09G OTM2
– OTM2 -> OTM2 (ingress and egress rates the same)
– FC1200 -> 11.09G or 11.27G OTM2
– FLEX (Note that the Protocol parameter for the FLEX facility model
is used to select the client protocol such as FC400, FC800,
FC1200. OC48/STM16, and OTM1). In addition, for circuit packs
such as the NTK532DAE5 OTN Flex MOTR 1xXFP, 8xSFP, ODU0
based encapsulation of lower-rate client signals to OTM1 or OTM2
facilities is provided.
— An example shown below is for the NTK528AA OTSC:
Table 4-18
Example Tx/Rx adjacency provisioning for NTK528AA OTSC
Tx/Rx adjacency type Line Facility, Rate, FEC Client Facility
6500 DWDM Tunable OTSC 1xOC192/STM64 1x10.7G RS8 FEC (NTK528AA) OTM2, 10.7G, RS8 OC192 or STM64
6500 DWDM Tunable OTSC 1x10GE LAN 10.7G RS8 FEC (NTK528AA) OTM2, 10.7G, RS8 ETH10G
6500 DWDM Tunable OTSC 1x10GE LAN 10.7G SCFEC (NTK528AA) OTM2, 10.7G, SCFEC ETH10G
6500 DWDM Tunable OTSC 1xOC192/STM64 1x10.7G SCFEC (NTK528AA) OTM2, 10.7G, SCFEC OC192 or STM64
6500 OTSC Tunable FC1200 11.3G RS8 FEC (NTK528AA) OTM2, 11.27G, RS8 FC1200
6500 OTSC Tunable FC1200 11.3G SCFEC (NTK528AA) OTM2, 11.27G, SCFEC FC1200
6500 OTSC Tunable 1xOTU2 1x10.7G RS8 FEC (NTK528AA) OTM2, 10.7G, RS8 OTM2
6500 OTSC Tunable 1xOTU2 1x10.7G SCFEC (NTK528AA) OTM2, 10.7G, SCFEC OTM2

Table 4-18
Example Tx/Rx adjacency provisioning for NTK528AA OTSC (continued)
Tx/Rx adjacency type Line Facility, Rate, FEC Client Facility
Foreign (alien) wavelength use over 6500 Photonic Layer

Ciena offers foreign source characterization services, path validation services
for characterized sources, and turn-up services (provisioning and test) for
foreign wavelength support over the 6500 Photonic layer. Ciena 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 the table below.
Table 4-19
Minimum transmitter / receiver specifications required for foreign wavelength characterization
Transmitter parameters Receiver parameters
OSNR bias Sensitivity threshold
Line rate Overload threshold
FEC gain Damage threshold
Minimum TX launch power Maximum positive transient
Maximum TX launch power Minimum negative transient
TX wavelength
TX Minimum Spectral Width (GHz) (see Note 1, Note 2)
TX Signal Bandwidth 3dB (GHz) (see Note 1, Note 3, Note 5)
TX Signal Bandwidth 10dB (GHz) (see Note 1, Note 4, Note 5)
Note 1: Only required for foreign coherent transponders.

Note 2: Represents the minimum signal bandwidth that would include the majority of the signal power
+ budget for laser aging/drift + laser control loop tolerance. This parameter is required for future
upgrades to Flex Grid.
Note 3: Represents the 3 dB signal bandwidth, where the measured power (RBW<4GHz) is expected
to be 3 dB lower than the peak center frequency power.
Note 4: Represents the 10 dB signal bandwidth, where the measured power (RBW<4GHz) is expected
to be 10 dB lower than the peak center frequency power.
Note 5: Refer to “Transponder Power Spectral Density” on page 2-64 for more details.

In the Site Manager Configuration -> Equipment/Facility Provisioning screen,

the Tx/Rx adjacency of the 6500 CMD port must be edited to the type labeled
as “Foreign” or “Foreign Coherent”, and the associated CMD Tx/Rx adjacency
parameters modified.
Foreign Coherent CMD Tx/Rx type must be used when coherent

transponders are connected to a 6500 CMD. Foreign CMD Tx/Rx type must
be used when non-coherent transponders are connected to a 6500 CMD.
Parameters that need to be modified to reflect the 3rd party supplier Tx

specifications include:
• Transmitter Type: “Foreign” or “Foreign Coherent”
• Modulation Class: Should be set as a CUSTOM(1-6) class to specify the
Differential Provisioning to be used for the signal. This reflects any
adjustment in dB relative to provisioned EDFA peak power targets
required to be set by DOC, which depends on the underlying modulation
format of the signal and link-engineering analysis.
• TX Minimum Spectral Width (GHz) (only required for foreign coherent)
• TX Signal Bandwidth 3dB (GHz) (only required for foreign coherent)
• TX Signal Bandwidth 10dB (GHz) (only required for foreign coherent)
• Min. Launch Power (dBm)
• Max. Launch Power (dBm)
• Actual Tx Power (dBm)
Similarly, for the Rx adjacency provisioning, the following parameters need to

be modified to reflect the 3rd party supplier Rx specifications.
• Receiver Type: Foreign
• Sensitivity Level (dBm)
• Overload Level (dBm)
• Nominal Level (dBm)
OTS engineering rules

OTS engineering rules are described in this section. The maximum number of
OTSs supported per shelf type is detailed in the tables below. Site Manager
prevents the user from exceeding the maximum total number allowed.
• The maximum number of OTSs per site or per TIDc is 100, where 32 are
allocated for degrees (ROADM OTS).
• A site can have multiple comms-interconnected OTS groups (see Note
below for a definition), but each comms-interconnected OTS group at a
site can have 100 OTSs maximum.

Note: A comms-interconnected OTS group is a group of OTSs which

share TR (Topology Resolution) records. TR records are shared if:
1) all the OTSs in the group are in the same 6500 shelf or
2) some OTSs in the group are in the same shelf and other OTSs in the
group are in different shelves and the shelves have the same OSPF area
or the shelves have different OSPF areas but share TR data, such as
when DBRS is used between OSPF areas.
Channel access nodes of ROADM subtype

Table 4-20
Maximum # of ROADM OTS subtypes per shelf
Shelf Type Maximum # using Maximum # using WSS Maximum # using

WSS 100 GHz circuit 50 GHz or WSS Flex NTK553RA RLA Flex circuit
packs circuit packs pack
7-slot 2 or 3 (Note 3) 3 3
6500-7 3 2 3
packet-optical
14-slot 4 4 (or 3 as per Note 4) 5
32-slot 4 (up to 5 as per Note 6) 4 (up to 8 as per Note 5) 5
Note 1: Only supported using the NTK553HA WSS 100 GHz w/OPM C-Band 4x1 or NTK553JB WSS
100 GHz w/OPM C-Band 2x1 circuit pack.
Note 2: Only supported using the NTK553KA WSS 50 GHz 2x1 circuit pack.
Note 3: 3 OTSs supported only when using the 7-slot Type 2 shelf.
Note 4: Only 3 OTSs supported if WSS type is NTK553FA 50 GHz w/OPM C-Band 9x1circuit pack
(triple slot-wide variant) or NTK553KC 50 GHz w/OPM C-Band 2x1circuit pack (triple slot-wide variant).
Note 5: Up to 8 OTSs are supported in a 32-slot shelf using 2-slot wide NTK553FC or NTK553LA/LB
9x1 Flex WSSs. Up to 7 OTSs can be deployed if 3-slot wide NTK553FA 9x1 50 GHz WSSs are used.
A mix of 2-slot and 3-slot WSSs with greater than 4 OTSs is also an option on a 32-slot shelf.
Note 6: Depending on hardware vintage, up to 5 can be supported. Contact Ciena for more
information.
Table 4-21
Maximum # of ROADM OTS subtypes per T-Series shelf
Shelf Type Maximum # using 20x1 RLA module
T-12 or T-24 8
The following rules also apply:

• The maximum number of OTSs per site per comms-interconnected OTS
group (see note below) is 30. A site can have multiple
comms-interconnected OTS groups. Each comms-interconnected OTS
group at a site can have the 30 OTS maximum.

Note: A comms-interconnected OTS group is a group of OTSs which

share TR (Topology Resolution) records. TR records are shared if:
1) all the OTSs in the group are in the same 6500 shelf or
2) some OTSs in the group are in the same shelf and other OTSs in the
group are in different shelves and the shelves have the same OSPF area
or the shelves have different OSPF areas but share TR data, such as
when DBRS is used between OSPF areas.
• The (1-slot wide) NTK553KA 50 GHz 2x1 WSS w/OPM is only supported
in configurations that use a maximum of 2 OTSs. This means the
NTK553KA cannot be used in 3-way node configurations.
— The 2-way ROADM configuration can be supported in a 7-slot shelf
when using the 1-slot wide NTK553KA. This is not possible using the
3-slot wide NTK553KC.
— A 2-way ROADM configuration in which one OTS uses the 1-slot wide
NTK553KA and the other OTS uses the 3-slot wide NTK553KC is
supported.
• Use of the NTK553FA 3-slot WSS, with more than 4 OTSs in a 32-slot
shelf is allowed by software. However, the shelf configuration does not
physically allow equipment in three of the seven OTSs to be kept together
in the same quadrant. As this requires three of the OTS to be split between
upper and lower shelves and across the cross connect, it is not a preferred
shelf configuration from a fiber management perspective. This situation
can be mitigated by using a mix of 2-slot and 3-slot 9x1 50 GHz WSSs.
• All the equipment forming a non-CDC ROADM OTS must reside in the
same shelf.
• ROADM OTSs belonging to the same OSID are normally equipped in the
same shelf but do not necessarily have to be. They can be equipped in
different shelves provided that the shelves are TID-consolidated.
Line Amp nodes of AMP OTS subtype

Table 4-22
Maximum # of AMP OTS subtypes per shelf
Shelf Type Maximum #
2-slot 4
7-slot 4
6500-7 packet-optical 4
14-slot 4
32-slot 4

The following rule also applies:

• The maximum number of Line Amplifier OTSs per OSID is 2. A shelf could
accommodate 4 Line Amplifier OTSs, if for example 2 of them belong to
OSID A and two others to OSID B.
Channel access node of TOADM OTS subtype

Table 4-23
Maximum # of TOADM OTS subtypes per shelf
2-slot 1 (see Note 1)
7-slot 4
14-slot 4
32-slot 4
Note 1: Only supported using the NTK503LA 2-slot optical Type 2 shelf.

• SCMD4s must be in the same OTS as the LIM and all the equipment
forming the OTS must reside in the same shelf. The line-facing OTSs at a
Thin OADM can be in different shelves.
• The LIM can be an MLA3, MLA2, MLA, SLA or LIM circuit pack or ESAM
with MLAx (MLA3,MLA2, or MLA) if supported by link engineering.
Cascaded LIMs are not supported.
• Up to 9 instances of CMDs can be provisioned in an OTS. Accordingly,
software supports the provisioning of up to 9 cascaded SCMD4s in the
SCMD4 cascade order, but the number may be limited by link engineering.
— Only 1 instance of each SCMD4 group is supported in an OTS
— Note that beyond a certain amount of groups a ROADM solution (2x1
WSS and CMD44) may be financially and operationally preferable
— The cascade can be in any group order but fibering must match the
provisioned cascade order
— No CMD44 is allowed in the cascade
• A Thin OADM with no equipped/provisioned SCMD4s initially is
supported.
— This is similar to a Line Amp node but provisioned as a Channel
access node; ready for an OOS upgrade to OADM node in the future
• Asymmetric Thin OADMs, where one OTS is equipped with SCMD4(s)
and the other OTS is not equipped with SCMD4(s) are also supported.

— This results in SCMD4 upgrade ports being connected to the opposite

side’s LIM/AMP.
Channel access node with DIA OTS subtype

Table 4-24
Maximum # of DIA OTS subtypes per shelf
2-slot N/A
7-slot 2
14-slot 2
32-slot 2

• The maximum number of DIA OTSs per node is 4.
• DIA is only supported at ROADM nodes.
• The equipment forming the DIA OTS must be in the same 6500 shelf.
• The DIA OTS should be in the same shelf as the backbone ROADM OTS
or if this is not possible it must be in a 6500 shelf that is TID-consolidated
with the other shelves containing the backbone ROADM OTSs.
Channel access node with Colorless OADM OTS subtype

A COADM OTS subtype is used in either:
• a Colorless Directionless OADM with the COADM OTS attached to a DIA
OTS which then connects to multiple backbone ROADM OTSs
• a Colorless Directional OADM with the COADM OTS directly attached to
the backbone ROADM OTS
The rules for the maximum number of colorless directionless OADMs on a

shelf are provided in the table below.
Table 4-25
Maximum # of Colorless Directionless OADMs per shelf
2-slot N/A
7-slot N/A

Table 4-25
Maximum # of Colorless Directionless OADMs per shelf
6500-7 packet-optical N/A
14-slot 1 (1 COADM OTS + 1 DIA OTS)
32-slot 2 (2 COADM OTS + 2 DIA OTS)
The following rules apply for colorless directionless OADM nodes:

• The maximum number of supported colorless directionless OADMs per
node is 2.
— DIA and COADM equipment redundancy is provided;
— This type of configuration affords some ability to address wavelength
contention (but is not as scalable as CDC configurations)
• In a colorless directionless OADM:
— the circuit packs forming the DIA OTS must be equipped in the same
6500 shelf
— the circuit packs forming the COADM OTS must be equipped in the
same 6500 shelf
— The DIA and COADM OTS can be located on the same shelf
(slot-space permitting) or different shelves within the same TIDc node.
The rules for the maximum number of colorless directional OADMs in COADM
OTS direct attach configurations are provided in the table below.
Table 4-26
Maximum # of COADM OTS subtypes per shelf using COADM OTS direct attach
2-slot N/A
7-slot N/A
6500-7 packet-optical N/A
14-slot 1
32-slot 2
The following rules apply for colorless directional OADM nodes with COADM
OTS direct attach:
• Maximum number of COADM OTSs per node is 7
• One COADM OTS is deployed per ROADM OTS within the node

• The circuit packs forming the COADM OTS must be equipped in the same
6500 shelf
Note: The COADM OTS can be configured on the same shelf as the
backbone ROADM OTS or a different shelf. For planning, in order to be 96
channel ready in a future release, this would entail 8 x CCMD12 circuit
packs, the Flex SMD/SMD (2-slots) and MLA3 (1-slot), for a total 11 slots
used by the COADM OTS.
The following rules are applicable to both the colorless directionless and
colorless directional COADM OTS direct attach configurations:
• The 6500 shelf which houses the COADM OTS must be equipped with an
SP2 Shelf Processor (NTK555CA/EA/FA)
• The High Fiber Loss Detection Alarm parameter in the Site Manager Node
Information application (System tab) must be set to Enabled for the shelf
containing a COADM OTS. This is required for COADM OTS SMD power
control purposes. Otherwise, the Fiber Loss Detection Disabled alarm is
raised.
General slot sequence engineering rules
A maximum of 40 Slot Sequence instances per OTS is supported:
• 1 Main (required)
• The remaining 39 can be any combination of the different branch types
(Group, Switch or Demux)
Slot sequence rules for OTSs using SRA/XLA and ESAM/SAM/XLA/MLAx
The following engineering rules apply for OTS subtypes which use SRA,
ESAM, SAM with XLA and ESAM, SAM with MLAx:
• SRA/ESAM/SAM are circuit packs that connect to the fiber plant. In
essence they are Line Interface Modules but with their unique circuit pack
type (i.e. SRA, SAM or ESAM respectively). These circuit packs contain
an OSC SFP.
— The OSC facility provisioned in the Basic OTS parameters tab of the
Site Manager Photonic Configuration Management application uses
the SRA/ESAM/SAM OSC facility
• The SRA is supported only if combined with XLA circuit pack
• The ESAM/SAM is supported only if combined with XLA or MLAx
(MLA/MLA2/MLA3) circuit pack
• At a Line Amp node, the XLA connected to an SRA actually serves both
East and West fiber pairs. It needs to be defined in the main slot sequence
of the OTS instance that connects to the XLA Line A facility.

• At a Line Amp node in a 3-slot configuration, the XLA or MLAx connected

to an ESAM/SAM actually serves both East and West fiber pairs. It needs
to be defined in the main slot sequence of the OTS instance that connects
to the XLA/MLAx Line A facility.
• At a Line Amp node in a 4-slot configuration, the XLA/MLAx connected to
an ESAM/SAM actually serves either the East or the West fiber pairs. It
needs to be defined in the main slot sequence of the OTS instance that
connects to the XLA/MLAx Line A facility.
• The SRA/ESAM/SAM OPTMON port 4 facility is set to OOS-MA by
software since the OSC pluggables used with these circuit packs have
better sensitivity than the OPTMON port 4 which could cause the
OPTMON “Loss of Signal” alarm to be raised although the OSC pluggable
is working correctly. Having this facility in the OOS-MA state does not
block any functionality.
• The DSCM/pad placement follows the existing slot sequence rules. The
DSCM/pads are normally within the main sequence and should be placed
around the XLA when needed.
• The same slot sequence rules apply whether the SRA or ESAM or SAM
is used.
OTS slot sequence provisioning must reflect the following connections:

Rule 1: For SRA and XLA within same AMP OTS:
— SRA Line A is connected to XLA Line A
— XLA Line B connected to SRA Line B
Rule 2: For ESAM/SAM and XLA/MLAx within same AMP OTS:
— ESAM/SAM Line A are connected to MLAx Line A
— MLAx Line B connected to ESAM/SAM Line B
Rule 3: For connection between AMP OTSs built with XLA:
— SRA/ESAM/SAM Line A connects to XLA Line B
— XLA Line B connects to SRA/ESAM/SAM Line A
Rule 4: For connection between AMP OTSs built with MLAx using 3
slot configuration:
— ESAM/SAM/LIM Line A connects to MLAx Line B (LIM =
LIM/SLA/MLA/MLA2/MLA3)
— MLAx Line B connects to ESAM/SAM/LIM Line A
Rule 5: For connection between AMP OTSs built with XLA/MLAx
using 4 slot configuration:
— XLA/MLAx Line A connects to XLA/MLAx Line B

— XLA/MLAx Line B connects to XLA/MLAx Line A
DOC engineering rules

DOC deployment rules
In an optical system, there must be two DOC instances, one for each Photonic
domain direction. This applies to both linear and ring systems. For optical
system and Photonic domain definitions, refer to “Network topology
segmentation levels” on page 1-4 and “Photonic Domain” on page 1-24.
The engineering limits for optical sections within a DOC domain, and DOC
domains themselves are as follows:
• Maximum number of optical sections per DOC Photonic domain is 22
• Maximum number of line amplifier nodes in an optical section is 15
• Maximum number of interconnected Photonic domains is only limited by
link budget (no software limits)
• Maximum number of domains traversed in homogeneous 6500 systems is
20 domains
DOC site placement must be considered based on the information that

follows.
DOC placement for single section Photonic domains

In an optical section, there must be two DOC instances, one for each Photonic
domain direction. Also,
• The maximum number of interconnected Photonic domains is only limited
by link budget (no software limits)
• The maximum number of domains a channel can traverse is 20 domains
DOC placement in linear configurations not using single section Photonic

domains
• In a 6500 or mixed 6500/CPL photonic linear configuration, the two DOC
instances must exist at the head end of each Photonic domain
• 6500/CPL TOADM and CPL GOADM nodes cannot be DOC sites if they
have passthrough channels
DOC placement in ring configurations not using single section Photonic

domains
• In a ring configuration with no TOADM nodes, the two DOC instances
must be provisioned at the same node (i.e. the two DOC instances must
have the same Site ID).
• In a ring configuration with a mix of TOADM and ROADM nodes, the two
DOC instances must be provisioned at the same node (i.e. the two DOC
instances must have the same Site ID) and the DOC site cannot be a
TOADM node

• In an all-TOADM ring configuration,

— The two DOC instances must be provisioned at the same node.
— The DOC site must be the TOADM optical seam node. All traffic must
add/drop at this node, with no passthrough traffic and no physical fiber
present between the sCMD upgrade ports. All channels must add/drop
at the DOC sites. No passthrough or even fibered.
— This is a linear as opposed to ring topology, in a ring geography.
DOC rules for DIA or COADM configurations

The following configurations that are connected to backbone ROADM OTSs
do not support provisioning of a DOC facility:
• DIA (i.e. containing DIA OTSs only)
• Colorless OADM (DIA and COADM OTSs)
DOC rules for domains containing Raman (SRA)

The following DOC domain rules exist for distributed Raman amplification
applications:
• The NTK552JA Single Line Raman Amplifier (SRA) circuit pack can only
be used in a domain that contains CPL/6500 ROADM nodes and
CPL/6500 Line AMP nodes
• CPL/6500 TOADM or CPL GOADM nodes are not supported in the same
domain as nodes containing SRA
Photonic domain segmentation

Overview
The Photonic domain segmentation rule is to have a Photonic domain for each
ROADM to ROADM section as shown in the figure below (Note that in the
figure, and others that follow, GOADM refers to a CPL GMD-based OADM
node). Every domain starts and ends with a ROADM, with no other ROADM
in between them (also known as the single section photonic domain).
Although the single section photonic domain is the recommended

segmentation type for reasons given in this section, newer Photonic
configurations such as T-Series, CDA with CCMD12 direct attach and L0
Control Plane mesh restoration must use this Photonic domain segmentation
rule.
Regarding other 6500 node types (discussed in “DOC deployment rules” on

page 4-42):
• For 6500 systems containing all-TOADMs, only one DOC domain is used
since domain boundaries at TOADM OTSs with passthrough channels is
not supported

• For mixed 6500/CPL systems, containing TOADMs and/or GOADMs, only

one DOC domain is used in domains containing a TOADM or GOADM
since domain boundaries at TOADM OTSs (or GOADM OTSs) with
passthrough channels is not supported
OSID rules
Follow these rules when provisioning the OSID on an OTS where DOC is
enabled:
• The OSID can be up to 8 alphanumeric characters, including the
underscore character “_”.
• The OSID must be unique within the network.
Advantages
Photonic domain segmentation provides the following advantages:
• Simplifies the extension/reconfiguration of existing systems
• Removes complex Photonic branching engineering rules
• Enhances consistency of the channel provisioning steps
• Enabling of high-value photonic applications
Figure 4-8
Photonic domain segmentation for each ROADM to ROADM section
DOC functionality in fault scenarios

When using single domain Photonic domain segmentation as shown in the
figure below, faults (e.g., fiber cuts, node failures, Photonic circuit pack failures
or service circuit pack failures) that occur in a ROADM to ROADM section do
not block channel reoptimization operations (nor channel add/delete
operations) in other ROADM to ROADM sections. However, it is blocked for
domains that have GOADM or TOADM sections.

Figure 4-9
Photonic domain segmentation - Enhancement of DOC functionality in fault scenarios
When using multi-domain Photonic domain segmentation as shown in Figure

4-8 on page 4-44, faults that occur in a ROADM to ROADM section do not
block channel reoptimization operations in other ROADM to ROADM sections.
Simplifies the extension/reconfiguration of existing systems

In the case of a system extension using single domain Photonic domain
segmentation as shown in the figure below, the DOC site needs to be moved
to the end of the Photonic domain (in the below example, the DOC site needs
to be moved from Site ID 2 OTS1 to Site ID 3 OTS1). Moving a DOC site
requires reconfiguration steps that are cumbersome and prone to error.
Figure 4-10
System extension using single DOC domain

In the case of a system extension using multi-domain Photonic domain

segmentation as shown in the figure below, there is no need to move the DOC
site as the new system extension has its own DOC site.
Figure 4-11
System extension using multi-domain DOC segmentation
Removes complex Photonic branching engineering rules

When multi-domain Photonic domain segmentation is not used, network
planners need to be aware of complex Photonic branching engineering rules
(see “Branching engineering rules” on page 4-144). These rules are no longer
applicable when using multi-domain Photonic domain segmentation since all
ROADM to ROADM segments are domains.
Enhances consistency of the channel provisioning steps

In the figure below, to provision a Photonic channel between the two
terminals, the user provisions the CMD Tx adjacency at the head-end terminal
and the CMD Rx adjacency at the tail-end terminal and Photonic connections
only at domain boundaries (or between ROADM to ROADM sections that do
not have the same OSID). These Photonic connections do not need to be
user-provisioned between ROADM to ROADM sections that have the same
OSID. In the example, a Photonic connection must be user-provisioned
between OTS1 and OTS2 at Site Y but not between OTS1 and OTS2 at Site
X since the Photonic connection is system derived (by Network Channel
Topology software).

Figure 4-12
Photonic connection provisioning when multi-domain DOC segmentation is not used
When using multi-domain Photonic domain segmentation as shown in Figure

4-8 on page 4-44, having to know whether a Photonic connection needs to be
provisioned or not is no longer required as it is always required between all
ROADM nodes that the wavelength transverses.
In a single DOC domain with multiple sections, to provision a Photonic

channel between the two terminals:
• The user provisions the CMD Tx adjacency at the head-end terminal and
the CMD Rx adjacency at the tail-end terminal
• The Photonic connections at each ROADM node are system derived by
Network Channel Topology software
• For CPL interworking, the Photonic cross connections at GOADM nodes
are system derived by Network Channel Topology software
• Note that there are no Photonic connections at Intermediate Line Amp
(ILA) nodes or Thin OADM (TOADM) nodes
In a system of multiple domains, in which each DOC domain contains only one
section:
• To provision a Photonic channel between the two terminals, user
provisions the CMD Tx adjacency at the head-end terminal and the CMD
Rx adjacency at the tail-end terminal and Photonic connections at each
ROADM node
• For CPL interworking, the Photonic connections at GOADM nodes are
system derived
• Note that there are no Photonic connections at Intermediate Line Amp
(ILA) nodes or Thin OADM (TOADM) nodes
Enabling of high-value photonic applications

Having one DOC domain per section enables various applications that
provide value to the operator:
• Photonic restoration using EMS layer applications such as Packet
Wavelength Service Management (PWSM) within the One Control suite

• Control Plane which provides various tiers of per-channel and trunk-based

protection and re-routing at the photonic layer. Refer to Technical
Publication NTRN71AA Control Plane Application Guide - Layer 0
(photonic) for more information.
DOC Power Audit (Calibration) engineering rules specific to Raman

applications
The following engineering rules apply to the power audit (calibration) process
run within DOC domains containing OTS subtypes with NTK552JA SRA
circuit packs.
The power audit (calibration) process:

• is not permitted when there are DOC controlled (i.e. managed) channels
in the domain;
• performs gain optimization one span at a time and for the entire domain;
• is a one-time operation and is not impacted by any restart, whether warm,
cold or a power cycle of hardware (including brownouts).
As of Rel. 12.4, you don’t need to manually launch the Power Audit process if
Dark Section Conditioning is running on the section, as it is part of the
conditioning (refer to “Dark Section Conditioning” on page 2-98). If Dark
Section Conditioning is not running, then the following applies:
• As a pre-requisite to performing a calibration (power audit) which would
occur prior to a dark channel add, the topology of at least one channel that
would go through any SRA circuit pack within the domain must be
established.
— The channel trail is created using Tx/Rx adjacencies and Photonic
connections, and the channel then appears in the Site Manager DOC
application as “Inactive”.
— This allows DOC to establish a port trail from ingress to egress through
all intermediate modules and circuit packs, thereby identifying any
SRAs in the path that would need calibration (power audit).
For an overview of the SRA, refer to “Single Line Raman amplifier (SRA)” on
page 3-128. For details of the power audit steps, refer to “SRA Power Audit
steps” on page 5-32.
Photonic node engineering and shelf configuration rules

General considerations
The following must be considered when designing a photonic node:
• For the 2-slot, 7-slot, 14-slot or 32-slot shelf, maximum number of
supported shelves at a TIDc node is 36 if primary shelf is equipped with
SP2, and 16 if primary shelf is equipped with SPAP-2.

• More than one TID can exist per node, however all photonic shelves must
be in the same TID (unlike Broadband shelves where the Broadband
shelves can be in different TIDs) to be able to build Photonic connections
between them.
— The above rule is modified for a mixed TOADM and ROADM node
which requires segregation guidelines as follows:
– Photonic connections between TOADMs and ROADMs are not
supported
– The Site IDs of the TOADM and ROADM nodes have to be
different and therefore the TOADM and ROADM channel access
OTS types must be on different shelves
– The TOADM and ROADM nodes should not be under the same
TID
• At a node, it is recommended that shelves housing transponder equipment
and shelves housing the photonic equipment either be TID consolidated
or have data communications setup between them to enable SPLI in order
to take advantage of the many SPLI-enabled features. For more details,
refer to “Service and Photonic Layer Interoperability (SPLI)” on page 1-48.
For more information on slot equipping rules, see Technical Publication

323-1851-151 Planning - Ordering Information and 323-1851-310/311
Configuration - Provisioning and Operating, and/or contact your Ciena
representative.
Wavelength provisioning considerations

Common equipment rules are dependent on the method used to provision
Photonic channels.
Wavelength provisioning can be done using L0 Control Plane (L0 CP) or not
and is configuration dependent (see Table 5-7 on page 5-36). Using L0 CP is
preferred as it simplifies wavelength provisioning through automated
connection management.
There are two supported L0 CP types:

• PHOTONIC
• L0 Provisioning
Both allow for wavelength provisioning and the PHOTONIC L0 CP type also
supports wavelength restoration.

For details on how to enable either L0 CP types, refer to NTRN71AA.2 Control

Plane Application Guide - Layer 0 (Photonic). Since an OSRP instance must
be created on the node primary shelf at each Photonic channel access node,
it is important to note the following hardware requirements:
• The “PHOTONIC” OSRP type can only be created on a 6500 shelf
equipped with two NTK555FA SP2 Dual CPU circuit packs with 1+1
protection (SP redundancy) provisioned
• The “L0 Provisioning” OSRP type can be created on a 6500 shelf
equipped with one SP2 circuit pack (NTK555CA/EA/FA)
Line Adjacency Fiber Type provisioning with mixed fiber types

When provisioning the Fiber Type against a Line Adjacency and the span is
made of different fiber types, the type to be provisioned should be the type that
dominates in the first 20 km. This aligns with OnePlanner, which uses the
dominant fiber in the first 20 km to determine the Target Peak Power.
Extended depth brackets/doors when using attenuator pads

Extended depth brackets/doors are designed to increase the gap between the
faceplate and the door cover to accommodate a 2.25” fiber boot and/or fixed
pad attenuator assuming 1” fiber bend radius. These are recommended for
use in 6500 Photonic layer deployments which use padding on various circuit
pack or modules within a node.
The following kits should be considered, depending upon the scenario.

• Green field front cover extension kits (for new installations):
— NTK509LJ: 6500 14-slot Shelf Bracket Kit, Extended Depth,
Optical/Rear IO shelf, EIA-23“x 5" SB for use with NTK503ADE5 shelf
— NTK609ME: 6500 32-slot Shelf Bracket Kit, Extended Depth, 23” rack,
567 mm centre-to-centre mounting holes, EIA Pitch, 127 mm Setback
for use with NTK603AAE5 shelf
• Upgrade front cover extension kits (for shelves already installed):
— NTK509CY: 6500 14-slot Shelf Front Cover Extension Kit for use with
NTK509CBE6 cover
— NTK509CZ: 6500 14-slot Shelf Front Cover Extension Kit for use with
NTK509CCE6 cover
— NTK609CZ: 6500 32-slot Shelf Front Cover Extension Kit for use with
NTK609CAE6 cover
• 14-slot shelf front cover with extended depth:
— NTK509CD: 6500 14-slot Shelf Front Cover Kit with Extended Depth
for use with NTK503SA shelf
• 14-slot shelf packs-in-place kit:

— NTYY99EG: 6500 14-slot Shelf Packs-in-Place Kit for use with

Extended Depth Brackets and NTK503ADE5 shelf
For further information, refer to Technical Publication 323-1851-151, Planning
- Ordering Information.
Colored Directional 1-way ROADM Terminal

Photonic inter-connections between the different modules at a ROADM
WSS-based Photonic terminal node (1-way ROADMs) are shown in the
following example diagrams:
• 5x1 100 GHz WSS terminal (see Figure 4-13 on page 4-62)
• 9x1 50 GHz WSS terminal with Cascaded LIM (see Figure 4-14 on page
4-63)
• 2x1 50 GHz WSS terminal with BMD2 (see Figure 4-15 on page 4-64)
• 5x1 100 GHz WSS terminal with Drop LIM (see Figure 4-16 on page 4-65)
• 4x1 100 GHz WSS terminal (see Figure 4-17 on page 4-66)
• 9x1 50 GHz WSS terminal with 2-port OPM and Enhanced CMD44 (see
• 9x1 50 GHz WSS terminal with SRA (or ESAM or SAM) and XLA (see
• 9x1 50 GHz WSS terminal with SRA (or ESAM or SAM), XLA and DSCMs
• 9x1 50 GHz WSS terminal with SRA (or ESAM or SAM), XLA, DSCMs,
Cascaded LIM (Interior SLA) (see Figure 4-21 on page 4-70)
• 9x1 50 GHz WSS terminal with ESAM (or SAM) and MLAx, DSCMs,
Cascaded LIM (Interior SLA) (see Figure 4-22 on page 4-71)
• 9x1 50 GHz WSS terminal with MLA3 and CMD96 (see Figure 4-23 on
page 4-72)
• 5x1 RLA terminal (see Figure 4-28 on page 4-77)
• 5x1 RLA terminal with SRA, ESAM or SAM (see Figure 4-29 on page
4-78)
Photonic inter-connections between the different modules at a Metro ROADM

WSS-based Photonic terminal node (1-Way Metro ROADMs) are shown in the
following example diagrams:
• 2x1 100 GHz WSS terminal with CMD44, LIM (see Figure 4-24 on page
4-73)
• 4x1 100 GHz WSS terminal with OMDF4 cascades and LIM (see Figure
4-25 on page 4-74)
• 9x1 50 GHz WSS terminal with OMDF4 cascades and LIM (see Figure
4-26 on page 4-75)

• 4x1 100 GHz WSS terminal with DSCMs and Drop LIM (see Figure 4-28
on page 4-77)
1-way ROADM Terminal - WSS and LIM deployment rules

The following should be considered when planning the deployment of a
WSS-based Terminal node:
• An SLA, MLA, MLA2, MLA2v, MLA3 or LIM circuit pack can be used if link
budgets allow
• Although all WSS types are supported, node planning should consider
whether the Terminal node will evolve into a branch node with more than
two branches or not. If not, a WSS 2x1 is enough, otherwise, a WSS with
a higher branching capacity should be selected.
• The following differences should be noted for the single-slot NTK553KA 50
GHz 2x1 WSS w/OPM circuit pack versus the 3-slot wide NTK553KC 50
GHz 2x1 WSS w/OPM circuit pack:
— The 3-slot wide NTK553KC has 2 switch ports that can be used for
either pass-through traffic or add/drop traffic whereas the 1-slot wide
NTK533KA has 1 dedicated pass-through port and 1 dedicated
add/drop port
— The 3-slot wide NTK553KC has 2 ports labeled as switch ports
whereas the 1-slot wide NTK553KA ports are labeled as Add In/Drop
Out and Switch In/Demux Out
Attention: The NTK553KA WSS add/drop port must be used to connect to

the BMD/CMD44, while the Switch/Demux port must be used to connect to
the other OTS WSS circuit pack within a 2-way ROADM configuration
— When establishing local add/drop traffic with the NTK553KA, the

BMD2 is not mandatory. If there will never be more than 44 channels
and that only half a band can be used, or for lower first installation cost,
a single CMD44 50GHz can be connected directly to the 2X1 WSS
Add In/Drop Out port. Alternatively, for future in-service upgradeability,
the BMD2 needs to be installed day 1 if expansion to greater than 44
channels is anticipated.
— The optical specifications of the 1-slot wide NTK553KA are different
than that of the 3-slot wide NTK553KC and hence it cannot be used as
a direct substitute without using OnePlanner to simulate your
particular application
— Provisioned PEC edit is not supported between the NTK553KA and
NTK553KC WSS types. One cannot be spared with the other.
— The faceplate LC connectors on the 1-slot wide NTK553KA protrude
by an extra 10 mm compared to faceplate LC connectors on the 3-slot
wide NTK553KC. As a result, in order to avoid unacceptable

interference with the shelf front cover, NTTC50++ patch cords

(NTTC50++ patch cords are Corning standard LC strain relief boots)
or approved equivalent must be used. Also, attenuator pads cannot be
mounted on the faceplate of the NTK553KA WSS when the shelf front
cover is installed.
• Note that in order to avoid OPTMON LOS alarms raised against unused
WSS switch ports, the following is recommended:
— Placing terminators on the unused WSS inputs
— Setting the secondary state of unused OPTMON facilities to AINS
1-way ROADM Terminal - WSS and SRA/XLA deployment rules

WSS-based terminal node with SRA and XLA.
• An SRA must always be used in conjunction with an XLA circuit pack at a
ROADM node:
— The XLA is paired with SRA for Raman span (long spans)
Supported ROADM OTS configurations are:

• WSS – XLA – SRA
The SRA is only supported on long spans and is deployed at each end of the
span, in a bookended configuration. The SRA is placed at the line-facing
outgoing direction.
The SRA can be replaced with the ESAM or SAM depending on link budget
and user requirements.
Note that cascaded LIM (interior SLA) configurations are supported with
SRA/XLA based ROADM OTS configurations, as indicated in “ROADM/Metro
ROADM with Cascaded LIM (Interior SLA)” on page 4-81
The table below describes the WSS circuit packs that are supported in
ROADM OTSs with SRA and XLA. For a complete list of WSS circuit packs,
refer to Table 3-2 on page 3-7.
• Note that in order to avoid OPTMON LOS alarms raised against unused
WSS switch ports, the following is recommended:
— Placing terminators on the unused WSS inputs
— Setting the secondary state of unused OPTMON facilities to AINS

Table 4-27
WSS circuit pack types supported in SRA/XLA ROADM configurations
PEC Description Width

(# slots)
NTK553FA 50 GHz WSS w/OPM C-Band 9x1 3
NTK553FC 50 GHz WSS w/OPM C-Band 9x1 2
NTK553LA/LB WSS Flex w/OPM C-Band 9x1 2
NTK553KC 50 GHz WSS w/OPM C-Band 2x1 3
NTK553KA 50 GHz WSS w/OPM C-Band 2x1 1
NTK553EA 100 GHz WSS w/OPM C-Band 5x1 2
NTK553JA 100 GHz WSS w/OPM C-Band 2x1 2
NTK553JB 100 GHz WSS w/OPM C-Band 2x1 1
NTK553HA 100 GHz WSS w/OPM C-Band 4x1 1
NTK553MA WSS Flex C-Band w/OPM 20x1 2
Regarding OSC SFPs and the OSC filter function:

• Of the OC-3/STM-1 CWDM 1511 nm SFPs, only the NTK592NG (0-34 dB
span) and NTK592NV (12-42 dB span) variants are supported on the
SRA/ESAM/SAM circuit packs.
• The NTK592NR OSC SFP and NTK504BA OSC Filter should be used in
the following scenarios:
— If the fiber type of the span is TWRS and the SRA circuit pack is being
used.
— If the fiber type is something other than TWRS and the OSC CWDM
SFP link budget limits are exhausted.
• The NTK592NR OSC DWDM SFP is only supported on the SRA circuit
pack.
1-way ROADM Terminal - WSS and XLA/MLAx with ESAM/SAM deployment
rules
WSS-based terminal node using XLA/MLAx with ESAM/SAM circuit packs.
• An ESAM/SAM circuit pack can be used in conjunction with XLA/MLAx
circuit packs at a ROADM node:
— The XLA/MLAx is paired with an ESAM (short spans and OTDR
feature)
— The XLA/MLAx is paired with a SAM (short spans)

Supported ROADM OTS configurations are:

• WSS – MLAx – ESAM
• WSS – XLA – ESAM
• WSS – MLAx – SAM
• WSS – XLA – SAM
The ESAM circuit pack is only supported on short spans (use the SRA for long
spans) and is always placed at the line-facing outgoing direction. It provides
OTDR functionality when bookended with any circuit pack. The ESAM is
recommended to be used with a minimum fiber distance of 20 km. For spans
less than 20 km, refer to “Operational considerations when using the ESAM”
on page 3-132.
The SAM circuit pack is only supported on short spans (use the SRA for long
spans) and is always placed at the line-facing outgoing direction.
ESAM and SAM circuit packs can either be bookended (ESAM/SAM circuit
packs at each end of the span) or interworking with CPL or 6500 amplifier
circuit packs.
The ESAM or SAM can only be paired with a MLAx (MLA/MLA2/MLA3 -

NTK552BA/FA/GA) variant. It cannot be part of the same OTS with an SLA,
LIM or MLA2v circuit pack.
Refer to the “1-way ROADM Terminal - WSS and SRA/XLA deployment rules”
on page 4-53 for all deployment rules. The only difference is the XLA can
replaced with a MLAx (MLA/MLA2/MLA3) for ESAM or SAM configurations.
1-way ROADM Terminal - general filter considerations:

• The 6500 CMD44 100 GHz, OMD4 100 GHz and 2150 OMDF4, OMDF8
and BS5 100 GHz filters can be used in the ROADM OTS as part of 100
GHz Metro ROADM configurations.
• For ROADM OTSs using SRA/ESAM/SAM with XLA or ESAM/SAM with
MLAx (MLA/MLA2/MLA3), CMD44 and BMD2 are supported.
• CMD96 are supported for 9x1 WSS ROADM OTSs using MLAx or
SRA/ESAM/SAM with XLA or ESAM/SAM with MLAx (MLA/MLA2/MLA3).
• At a node equipped with 100 GHz WSS, you can only deploy 100 GHz
CMD44 modules (Figure 4-13 on page 4-62), 100 GHz OMD4, OMDF4,
OMDF8 and BS5 modules.
• At a node equipped with 50 GHz WSS, a mix of 50 GHz and 100 GHz
filters is possible.
• The duplicate circuit pack support feature allows the same type of filter to
be provisioned more than once in an individual ROADM OTS.

— As described in “ROADM/Metro ROADM with Mux Amp” on page

4-103, the use of a duplicate CMD type with extra Mux Amp may be
required to be connected to a different WSS switch port in 50 GHz or
100 GHz ROADM configurations. This would be necessary to handle
the lower launch power of the WL3n family of DWDM interfaces, when
deployed alongside the WL3 or WL3e family of DWDM interfaces.
• In general, a mux/demux filter (i.e. CMD44, CMD96, OMD4, OMDF4,
OMDF8 or BS5) can be connected to any WSS port, but
— When using the WSS 100 GHz w/OPM 5x1 circuit pack, the filter can
connect to any WSS switch port except SW1 as this port is used to
connect to another WSS circuit pack with the same OSID. It is
recommended to connect the CMD44 to WSS SW5.
— When using the WSS 100 GHz w/OPM 4x1 circuit pack, the filter can
connect to any WSS switch port except SW1 as this port is used to
connect to another WSS circuit pack with the same OSID.
— When using the WSS 100 GHz w/OPM 2x1 circuit pack, the filter must
be connected to WSS SW2.
— When using the WSS 50 GHz w/OPM 9x1 circuit pack and the CMD44
is connected to WSS SW8 and SW9 (Figure 4-14 on page 4-63).
– When using CMD44 50 GHz modules, it is recommended to
connect the CMD44 50 GHz Blue module to WSS SW8 and the
CMD44 50 GHz Red module to WSS SW9.
– When connecting 100 GHz modules to the WSS 50 GHz w/OPM
9x1 circuit pack, it is recommended to connect the CMD44 module
to WSS SW9. Note that the BMD2 is not supported when used with
the WSS 50 GHz w/OPM 9x1.
– A mix of CMD44 50 GHz and 100 GHz modules on a ROADM OTS
is possible. For instance, a blue and red CMD44 50 GHz could be
connected to SW8 and SW9 of a 9x1 50 GHz WSS respectively,
while the 100 GHz CMD44 could be connected to an available
switch port (SW1 to SW7).
— When using the WSS 50 GHz w/OPM 9x1 circuit pack and the CMD96
is connected to WSS SW8 and SW9 (Figure 4-14 on page 4-63).
– When using CMD96 50 GHz modules, it is recommended to
connect the CMD96 50 GHz module to either the WSS SW8 or
SW9.
– If SW8 or SW9 are not available then the CMD96 can be
provisioned with an XLA or MLA3 and connected to any of the
SW1 to SW7 available. XLA/MLA3 mux gain value associated with
CMD are set and forget provided by OnePlanner. Demux gain
value controlled by DOC.

– As a result of low isolation specification between channel ports, the

CMD96 only supports coherent transponders
— When using the WSS 50 GHz w/OPM 2x1 circuit pack, the CMD44
must connect to WSS SW2 (NTK553KC) or WSS Add in /Drop Out
(NTK553KA).
– When using both the red and blue CMD44 50 GHz modules, they
connect to WSS SW2 (NTK553KC) or WSS Add in/Drop Out
(NTK553KA) via a BMD2 module (Figure 4-15 on page 4-64).
– The BMD2 is not mandatory.
– If there will never be more than 44 channels and that only half a
band can be used, the CMD44 50 GHz can be connected directly
to the WSS 50 GHz w/OPM 2x1 circuit pack. However, for future
in-service upgradeability, the BMD2 needs to be installed day 1.
Attention: Unused Transmitters (i.e., not DOC managed) connected to

CMD44 Channel In ports of the CMD44 in the same OTS as the NTK553KA
50 GHz 2x1 WSS should either be disconnected or should be turned off. If a
future upgrade to a two-way node occurs, pass-through channels with the
same wavelength as an unused transmitter may not successfully carry traffic.
1-way ROADM Terminal - switch port usage for the WSS 50 GHz w/OPM 9x1
circuit pack:
• Branching can only be performed on WSS switch ports 1-7. However the
reverse is not true: switch ports 1-7 can have other uses.
• WSS switch ports 8 and 9 can only be used for mux/demux structures.
However the reverse is not true: mux/demux structures can be added on
switch ports 1-7. A mux/demux structure is any of the following: CMD44,
Mux Amp, DIA OTS, DIA OTS+COADM OTS or COADM OTS.
• WSS switch ports 8 and 9 must have compatible uses (either directly
connect CMD or not)
• If the Mux Amp application is used on WSS switch ports 8 and 9 then an
SLA should be used (or alternatively, you shouldn’t cascade the WSS
demux amp and another LIM based amp)
1-way Metro ROADM Terminal - supported 100 GHz filter combinations

For Metro ROADM WSS terminal configurations, the following 100 GHz filter
combinations are supported:
• BS5 with OMDF8s
• Cascaded OMD4s
• Cascaded OMDF4s
• Cascaded OMDF4s (up to 2) terminated with a CMD44

• Different filter types can be deployed at each end of the channel path. For
instance, a channel may be added using a 100 GHz CMD44 at node A and
dropped at a 100 GHz BS5/OMDF8 or OMD4 combination at node B, and
vice-versa.
In the information that follows in this section, 100 GHz filter deployment rules
are listed. To be read in conjunction with Table 4-3 “6500 and 2150/4200 filter
modules referenced to 6500 C-Band ITU-T 50 GHz 88-channel plan” on page
4-6.
1-way Metro ROADM Terminal - OMDF4 deployment rules:

The following rules are applicable to Metro ROADM configurations using
OMDF4s.
• Each 100 GHz OMDF4 filter can add or drop 4 channels
— Available in high (H) and low (L) sub-band variants for each group
(A,B,C,D & E)
— Express ports allow cascades to be connected to WSS switch port
• Unavailable channels (See Table 4-7 on page 4-21):
— Since OMDF4s are 100GHz filters, the 50GHz channels (even
channel numbers) of that subgroup must not appear on the NTWK R
(Common In) port since they will be blocked
— This includes the skip channel between the high and low subgroups
— All skip channels before and after the subgroup will be heavily
attenuated in the express path and will not be viable for traffic
1-way Metro ROADM Terminal - OMDF8 deployment rules:

OMDF8s.
• Each 100 GHz OMDF8 can add/drop 8 channels
• Available for each group (A,B,C,D & E)
• No express ports – i.e. no channels pass through device, so the filter is
intended for use with Band Splitter filters or at the end of a cascade
— Since OMDF8s are 100GHz filters, the 50GHz channels (even
channel numbers) in each group must not appear on the NTWK R
(Common In) port since they will be blocked
— All skip channels before and after the group will be heavily attenuated
in the express path and will not be viable for traffic

1-way Metro ROADM Terminal - BS5 deployment rules:

BS5s.
• Drops all groups (A,B,C,D & E)
• Used in conjunction with OMDF4s and OMDF8s
• Can only be used at the end of a cascade as there are no express ports
Attention: Note that the 2150/4200 BS1, BS2 and BS3 filters are not
currently supported in Metro ROADM configurations.
• For supported and blocked wavelengths, refer to Table 4-12 on page 4-24
1-way Metro ROADM Terminal - OMD4 deployment rules:

• Each 100 GHz OMD4 filter can add or drop 4 channels
• Similar to OMDF4 but uses the same group mapping as the original
6500/CPL100 GHz SCMD4 groups
• OMD4 is housed independent of the 6500 shelf or other chassis/modules
in the rack
• Upgrade (or Express) ports allow cascades to be created
– Since they are 100GHz filters, the 50GHz channels (even channel
numbers) of that group must not appear on the Common In port
– This includes the skip channel between groups
– All skip channels before and after the group will be heavily
attenuated in the express path and will not be viable for traffic.
Attention: The OMD4 should not be mixed with OMDF4/OMDF8/BS5 due

to different wavelength mappings which would result in limiting available
wavelengths.
Attention: If the network has ROADMs and TOADMs, ROADMs must use
either CMD44 or OMD4. The OMD4 and SCMD4 wavelength plans are
equivalent (with same skip channels).
1-way Metro ROADM Terminal - filter scalability

Scalability rules are as follows:
• The maximum number of supported CMDs in an OTS is 10. This includes
OMDF4, OMDF8, OMD4 and CMD44s.
• The maximum number of supported Band Splitters (BS5s) is 5

• The maximum number of supported BMDs is 5

Finally, note that the following hardware is not supported in Metro ROADM
configurations:
— 4200 OSC Filter (OSCF, B-720-0014-003) (CN-51S-00, 1CH CWDM)

- since the LIMs incorporate this function
— 6500 FGA (NTK552BA) - since fixed-gain, and is not DOC controlled
1-way Metro ROADM Terminal - channel padding and intra-OTS padding

For channel padding and intra-OTS padding provisioning refer to “Channel
pad and intra-OTS pad” on page 5-10.
1-way 5x1 RLA Terminal deployment rules:

The following rules are applicable to 5x1 RLA ROADM configurations.
• It is recommended to connect the add/drop modules to SW5
— Software does not block adding the add/drop modules to another
branch though
• When using the NTK592NG or NTK592NV OSC pluggable, the OPTMON
facility on the RLA port 4 is automatically placed OOS-MA. This is
because these pluggables’ receiver sensitivity is lower than the RLA port
4 photodiode sensitivity. Therefore, at these levels the power received on
port 4 is either outside the photodiode range or has a very low accuracy.
Hence, the facility is changed to OOS-MA automatically by software.
• Use Slot sequencing to provision the ROADM OTS. Add the RLA to the
OTS main slot sequence, an action which then generates 5 branch
sequences out of the RLA. Attach the add/drop modules to the branch
sequence corresponding to SW5.
• If you use the SAM, ESAM or SRA:
— Add it to the OTS main slot sequence along with the RLA
— Since the line-facing equipment is SAM/ESAM/SRA, the RLA OSC
OPTMON facilities 3 and 4 are automatically placed OOS-MA, and the
RLA ADJ-LINE facility port 5 is automatically deleted
— Of the OC-3/STM-1 CWDM 1511 nm SFPs, only the NTK592NG (0-34
dB span) and NTK592NV (12-42 dB span) variants are supported on
the SRA/ESAM/SAM circuit packs
— The NTK592NR OSC SFP and NTK504BA OSC Filter should be used
if the fiber type of the span is TWRS and the SRA circuit pack is being
used or if the fiber type is something other than TWRS and the OSC
CWDM SFP link budget limits are exhausted
— The NTK592NR OSC DWDM SFP is only supported on the SRA
circuit pack

• This configuration must operate in flexible grid mode when using CMD64
add/drop modules
• When using CMD44 100GHz modules in fixed grid mode, 56GBaud
signals are not supported.

Figure 4-13
Example 9x1/1x5 100 GHz WSS Terminal node
2 x OSC PEC: NTK554BA OTS1

OSC1 Out 1
WSC OSC
1 1 OSC1 In
1
OSC2 Out 2
WSC OSC
2 2 OSC2 In
2
WSS MLA
PEC: NTK553EA PEC: NTK552BA
Monitor 1 1 Line B Mon
1
OPM 2 2
Line A Mon
Monitor 2
Switch 1 In OSC B In
3
3
4
4 OSC A Out
Common In
Switch 1 Out
17
Switch 2 In Line B In Line B Out
5
6 B 5
6
Switch 2 Out 7 A 8
Switch 3 In
7 9:1
8
Switch 3 Out
Switch 4 In
9
10
Σ
Switch 4 Out
1:5
Switch 5 In
11
12
Switch 5 Out 18
Common Out
1X5 w/upgd
13
WSS 100
Switch 6 In
14
Switch 7 In
15
Switch 8 In
16
Switch 9 In
LC
CMD44 Ch 1 In
PEC: NTT862AA 1
2
Ch 1 Out
LC
Ch 2 In 3
LC
90 Common Out 4
Ch 2 Out
89
Common In
LC
Ch 43 In 85
86
Ch 43 Out
LC
Ch 44 In 87
88
Ch 44 Out

Figure 4-14
Example 9x1 50 GHz WSS Terminal node with cascaded LIM
WSS 50 GHz LC 2xOSC PEC: NTK554BAE5

LC
PEC: NTK553FA 1
OSC1 Out
OSC OSC
OSC2 Out
2
1 1 2 2
OSC1 In OSC2 In
Monitor 1
1 Loc: Shelf: Slot:
OPM Monitor 2
2
MLA
Switch1 In
3 PEC: NTK552BA
Switch1 Out Line B Mon
4 1
Switch2 In 2
5
WSS 50 GHz
Common Out Line A Mon

Switch2 Out 22
6 OSC B In
3
Switch3 Out
9x1
7 4
Switch3 In OSC A Out
8
Line B In Line B Out
Switch4 Out 6 B 5
9
10
Switch4 In 6500 SLA
Switch5 Out PEC: NTK552AA 7
Line A Out
A 8
Line A In
11 Mon 1 (B Out)
Switch5 In 1
12
2
Switch6 In Mon 2 (A Out)
13 1:9 OSC B In
Switch6 Out 3
14
15
Switch7 In Common In
4
OSC A Out
DSCM
Switch7 Out
21 PEC: NTT870Ax
16 Line B In Line B Out
6 5
SC Out In SC
9:1 7 A 8
Switch8 In (Add1) Line A Out Line A In
17
Switch8 Out (Drop1)
18
19
Switch9 In (Add2) Loc:AA Shelf:X Slot:Y
Switch9 Out (Drop2)
20
CMD44 50GHz Red
PEC: NTT862BB
Slot: 0
Ch1 Out
2
CMD44 50GHz Blue 1547.72nm
1
Ch1 In
PEC: NTT862BA

Ch2 Out
Slot: 0 4
1548.11nm
Ch1 Out 3
2 Ch2 In
1530.33nm
1
Ch1 In Common In
89
Ch2 Out 4
1530.72nm
3 Common Out
Ch2 In 90
Common In
89 Ch43 Out
86
1564.68nm
Common Out 85
90 Ch43 In
Ch44 Out
88
1565.09nm
Ch43 Out 87
86 Ch44 In
1546.92nm 85
Ch43 In
Ch44 Out
88
1547.32nm
87
Ch44 In

Figure 4-15
Example 2x1 50 GHz WSS Terminal node (NTK553KA/KC) with BMD2

2xOSC
Figure 4-16
1 OSC1 Out OSC2 Out 2
Release 12.6
OSC OSC
1 OSC1 In 1 2 OSC2 In 2 MLA
Line B Mon
1
2
WSS 100 GHz 5x1 Line A Mon
OSC B In
Monitor 1 3
1
OPM Monitor 2 4
2

OSC A Out
Switch1 In Line B In Line B Out

3 6 B 5
4 Switch1 Out
Common Out Cascaded LIM 7 A 8

18 Line A Out Line A In
1: 5 Mon 1 (B Out)
 1 SLA

2
Mon 2 (A Out)
OSC B In
3
Switch5 In 4
11 5:1 OSC A Out
Common In
12 Switch5 Out 17 Line B In Line B Out
6 5
7 A 8
Example 5x1 100 GHz WSS Terminal node with Drop LIM
Drop LIM SLA

Mon 1 (B Out)
1
2
eCMD44 100 GHz
Mon 2 (A Out) Ch1 In 1
OSC B In
3 Ch1 Out 2
4 Common In
OSC A Out 89
Line A In Line A Out
8 A 7
90 Common Out
Ch44 In 87
5 6
Ch44 Out 88
October 2019
Figure 4-17
Example 4x1 100 GHz WSS Terminal node

Figure 4-18
Example 9x1 50 GHz WSS Terminal node with 2-port OPM and enhanced CMD44 50 GHz

Figure 4-19
Example 9x1 50 GHz WSS Terminal node with SRA (or ESAM or SAM) and XLA

Figure 4-20
Example 9x1 50 GHz WSS Terminal node with SRA (or ESAM or SAM), XLA and DSCMs

Figure 4-21
Example 9x1 50 GHz WSS Terminal node with SRA (or ESAM or SAM), XLA, DSCMs, Cascaded
LIM (Interior SLA)

Figure 4-22
Example 9x1 50 GHz WSS Terminal node with ESAM (or SAM), MLAx, DSCMs, Cascaded LIM
(Interior SLA)

Figure 4-23
Example 9x1 50 GHz WSS Terminal node with MLA3 and CMD96

Figure 4-24
Example 2x1 100 GHz WSS Metro ROADM Terminal node with CMD44, LIM

Figure 4-25
Example 4x1 100 GHz WSS Metro ROADM Terminal node with OMDF4 cascades and LIM

Figure 4-26
Example 9x1 50 GHz WSS Metro Terminal node with 100 GHz OMDF4 cascades, LIM

Figure 4-27
Example 4x1 100 GHz WSS Terminal ROADM node with 100 GHz filters, DSCMs & Drop LIM

Figure 4-28
Example 5x1 RLA Terminal ROADM node

Figure 4-29
Example 5x1 RLA Terminal ROADM node with SRA, ESAM or SAM
Colored Directional higher degree (e.g. 2-way, 3-way, up to 8-way)

ROADM/Metro ROADM
The remotely reconfigurable optical add-drop multiplexer (ROADM) node
provides the ability to remotely and automatically reconfigure optical channels
in either add/drop or passthrough directions.
Example diagrams for the photonic connections between the different

modules at a typical 2-way Photonic ROADM node are shown as follows.
Attention: Depending upon the configuration, a single NTK554BA 2xOSC

circuit pack function can be replaced by the SPAP-2 w/2xOSC 2xSFP circuit
pack on 7-slot type 2 shelves to save slot-space.
• 100 GHz 9x1/1x5 WSS, dual 2xOSC (see Figure 4-30 on page 4-84)

• 100 GHz 9x1/1x5 WSS, cascaded LIM, dual 2xOSC

• 100 GHz 9x1/1x5 WSS, cascaded LIM, single 2xOSC
• 100 GHz 4x1 NTK553HA WSS, single 2xOSC
• 50 GHz 2x1 NTK553KA/KC WSS, BMD2, dual 2xOSC
• 50 GHz 9x1 WSS, dual 2xOSC (see Figure 4-35 on page 4-89)
• 50 GHz 9x1 WSS with SRA (or ESAM or SAM) and XLA (see Figure 4-36
on page 4-90)
• 50 GHz 9x1 WSS with SRA (or ESAM or SAM) and XLA, connected to
existing ROADM OTS containing LIM and 2xOSC (see Figure 4-37 on
page 4-91)
• 50 GHz 9x1 WSS with ESAM (or SAM) and MLAx (MLA/MLA2/MLA3),
connected to existing ROADM OTS containing LIM and 2xOSC (see
• 5x1 RLA (see Figure 4-39 on page 4-93)
• 5x1 RLA with SRA, ESAM or SAM (see Figure 4-40 on page 4-94)
• 50 GHz 9x1 WSS with MLAx (MLA/MLA2/MLA3), connected to CMD96,
to take advantage of the 98 channels the line amplifier on the ROADM has
to be a MLA3 (see Figure 4-41 on page 4-95)
Various 2-way and 3-way Metro ROADM Configurations
• 2-way with 2x1 100 GHz WSS, BS5 & OMDF8s, CMD44, Drop-LIM (see
• 2-way with 4x1 100 GHz WSS, BS5 & OMDF8s, Cascaded LIM (Interior
SLA), DSCM (see Figure 4-43 on page 4-97)
• 2-way with mixed WSSs when new OTS added as part of a system
expansion (see Figure 4-44 on page 4-98)
• 3-way with 4x1 100 GHz WSSs, CMD44s, BS5/OMDF8s, LIMs (see
• 3-way with DIA (see Figure 4-46 on page 4-100):
— Backbone ROADM OTSs using 4x1 100 GHz WSSs, CMD44s,
BS5/OMDF8s, LIMs.
— DIA OTS using 4x1 100 GHz WSSs, eCMD44, LIM

Up to 8-way ROADM configurations:

• 8-way (see Figure 4-47 on page 4-101) deployable on a single 32-slot
shelf
Higher degree ROADM node - 2xOSC circuit pack rules

The maximum number of NTK554BA 2xOSC circuit packs that can be
equipped in a shelf type is as follows:
• Up to two (2) 2xOSC circuit packs in a 7-slot, 6500-7 packet-optical shelf
or 14-slot shelf
• Up to four (4) 2xOSC in a 32-slot shelf
Higher degree ROADM node - WSS and LIM deployment rules
The rules described in “1-way ROADM Terminal - WSS and LIM deployment
rules” on page 4-52 are applicable to higher degree ROADM nodes using the
same hardware.

ROADM node:
• If WSS SW5 is used as a passthrough connection at a ROADM node,
SW5 cannot be used as a passthrough at the ROADM nodes immediately
upstream and downstream.
In addition, for CPL-6500 ROADM interworking,
— If 6500 WSS SW5 is used as a passthrough connection at a 6500
ROADM node, CPL WSS SW3 cannot be used as a passthrough
connection at CPL ROADM nodes immediately upstream and
downstream.
— If CPL WSS SW3 is used as a passthrough connection at a CPL
ROADM node, 6500 WSS SW5 cannot be used as a passthrough
connection at 6500 ROADM nodes immediately upstream and
downstream.
— Note that for CPL-only ring systems, WSS-WSS connections cannot
form a closed loop on SW3. i.e. SW3 cannot be used as for all WSSs
within a CPL ring.
• All WSS circuit packs must be of the same “grid” at the ROADM node, i.e.
all 50 GHz or all 100 GHz with no mixing
Higher degree ROADM nodes - WSS and SRA/XLA deployment rules
The rules described in “1-way ROADM Terminal - WSS and SRA/XLA
deployment rules” on page 4-53 are applicable to higher degree ROADM
nodes using the same hardware.

Higher degree ROADM nodes - WSS and XLA/MLAx with ESAM/SAM

deployment rules
The rules described in “1-way ROADM Terminal - WSS and XLA/MLAx with
ESAM/SAM deployment rules” on page 4-54 are applicable to higher degree
ROADM nodes using the same hardware.
Higher degree ROADM nodes - general filter considerations

The rules described in “1-way ROADM Terminal - general filter
considerations:” on page 4-55 are applicable to higher degree ROADM nodes
using the same hardware.
ROADM/Metro ROADM with Cascaded LIM (Interior SLA)

The combination of a large interior DSCM and/or long spans can trigger the
need for an interior SLA (also called Cascaded LIM). Figure 4-31 on page
4-85 and Figure 4-32 on page 4-86 show some examples for the photonic
connections between the different modules at a typical Photonic ROADM
node with a cascaded LIM.
• Line B of interior SLA is bypassed to minimize loss. The Line B facility
should be put OOS.
• OPM is always connected to the exterior (i.e., line facing) amplifiers.
The MLA2v is also supported in a ROADM OTS when connected to the

interior SLA (cascaded LIM), as shown in the configurations in “MLA2v - EDFA
with embedded VOA” on page 3-119.
All Metro ROADM configurations support the Cascaded LIM (Interior SLA).
Note that:
— The C-Band FGA is not supported as a Cascaded LIM
— The OSCF 4200 OSC Filter (OSCF, B-720-0014-003) (CN-51S-00,
1CH CWDM) - is not supported since 6500 LIMs incorporate this
function
Cascaded LIM (Interior SLA) are supported in ROADM OTSs configured with:
• MLA/MLA2/MLA2/MLA2v hardware
• SRA/ESAM/SAM and XLA hardware
• ESAM/SAM and MLAx (MLA/MLA2/MLA3) hardware
• The cascaded LIM (SLA) is located between the Line A Output of the XLA
or MLAx and the Common Input port of the WSS. The Cascaded LIM is
DOC controlled.
— This is only supported on ROADM nodes.

ROADM/Metro ROADM with Drop LIM

In order to improve the Receiver power level, it may be necessary to include
an extra amplifier in the WSS drop path in some network deployments (see
Figure 4-16).
• The Drop LIM must be an SLA
• Is supported with the WSS circuit packs shown in the table that follows:
Table 4-28
Drop LIM support with WSS circuit pack types
PEC Description WSS Drop LIM Drop LIM support in

width (# support Metro ROADM configs
slots) (non Metro) (N/A = Not Applicable
ROADM since WSS not
configs supported)
NTK553EA 100 GHz WSS w/OPM C-Band 5x1 2 Yes N/A
NTK553HA 100 GHz WSS w/OPM C-Band 4x1 1 Yes Yes
NTK553JA 100 GHz WSS w/OPM C-Band 2x1 2 Yes N/A
NTK553JB 100 GHz WSS w/OPM C-Band 2x1 1 Yes Yes
NTK553FA 50GHz WSS w/OPM C-Band 9x1 3 No Yes, 100 GHz filters only
NTK553FC 50 GHz WSS w/OPM C-Band 9x1 2 No Yes, 100 GHz filters only
NTK553LA/LB 50 GHz WSS w/OPM C-Band 9x1 2 No N/A

Gridless
NTK553KC 50GHz WSS w/OPM C-Band 2x1 3 Yes N/A
NTK553KA 50GHz WSS w/OPM C-Band 2x1 1 Yes (Note 1) N/A
Note 1: Software does not prevent the single-slot 50 GHz 2x1 WSSOPM (NTK553KAE5)
from being provisioned in a Drop LIM configuration as well. However, due to the improved
drop-direction (common-input to switch-output) insertion-loss the circuit pack offers, it would
typically be redundant in such a configuration.
For non Metro-ROADM configurations:

• If a pad is required/installed between the WSS Switch Out port and the
DROP LIM port 8, the pad is provisioned as excess loss on the WSS
Switch Out port ADJ-FIBER facility. OnePlanner determines if a pad is
required.
• Note 1: For the 100 GHz applications it is recommended to use the
eCMD44 when using the Drop LIM since it includes an embedded isolator
to prevent the Drop LIM to enter in APR if a user were to accidentally
misconnect the Tx and RX to the CMD44.

• Note 2: For the 50 GHz applications it is recommended to use the BMD2

which has an embedded isolator to prevent the Drop LIM to enter in APR
if a user were to accidentally misconnect the Tx and RX to the CMD44.
• The DROP LIM OSC A Out port OPTMON facility (OPTMON-<shelf
number>-<slot number>-4) and adjacency are automatically deleted by
software since this facility is not used in this application.
• Note that for the Drop LIM, there are no AMP facility settings to manually
provision. (i.e. Target gain, peak power target or target gain tilt values are
not part of the OnePlanner report that recommends the use of a Drop
LIM). DOC automatically adjusts the AMP facility settings as required.
• With short spans, an SLA or LIM can be used at ROADM nodes instead
of MLA, MLA2 or MLA3 (provided the link budget allows). However, the
LIM cannot be used with the 9x1 50 GHz WSS with passthrough channels.
For Metro ROADM configurations:

• Only one Drop LIM is allowed per WSS switch port, with the exception
being the add/drop ports of the 1 x 9 50GHz WSS which is already
amplified.
• The Drop LIM has to be before all of the filters in the sequence.
• The Drop LIM can be preceded by a DSCM (or pad) – it is never
recommended to provision the Drop LIM before the DSCM.
• Note that the C-Band FGA is not supported as a Drop LIM
• For 100 GHz Metro ROADM deployments, it is recommended that the
Drop LIM is only used with the eCMD44 100GHz.
• Since there are no isolators in the 2150/4200 series of filters any
mis-fibering of channels will result in APR.
— The isolator on the common in of the eCMD44 100GHz prevents this
— Additionally, with the low loss filters, even when no fibering mistakes
are made, the amplifier can still go into APR or raise a Low Optical
Return Loss alarm that could not be cleared if any unused filter ports
are not terminated. A 3dB pad on the output of the Drop LIM would
prevent this if it is desired to use a Drop LIM with the 2150/4200 filters.
Higher degree ROADM nodes - 5x1 RLA deployment rules

The rules described in “1-way 5x1 RLA Terminal deployment rules:” on page
4-60 are applicable to higher degree ROADM nodes using the same
hardware.
The configuration becomes a DGFF if the add/drop modules are not

equipped.

WSC WSC WSC WSC
2 1 2 1
OTS2
Figure 4-30
Release 12.6
OTS1
OSC OSC OSC OSC

2 1 2 1

OSC1 In
OSC1 In
OSC2 Out
OSC2 Out
OSC1 Out
OSC1 Out
OSC2 In
OSC2 In
2
2
1
1
2
2
1
1

MLA WSS WSS MLA
PEC: NTK552BA PEC: NTK553EA PEC: NTK553EA PEC: NTK552BA
Line B Mon Monitor 1 Line B Mon
1 1 Monitor 1 1 1
Line A Mon OPM OPM Line A Mon
2 2 2 2
Monitor 2 Monitor 2
OSC B In Switch 1 In Switch 1 In OSC B In
3 3
3 3
4 4
OSC A Out 4 4 OSC A Out
Common In Common In
Switch 1 Out Switch 1 Out
Line A In Line A Out 17 17
7 Switch 2 In Switch 2 In Line B In Line B Out
8 A 6 B 5

5 5
6 6
5 B 6 Switch 2 Out Switch 2 Out 7 A 8
Switch 3 In Switch 3 In
7 7 9:1
8 8
9 9
10 10
1:5 1:5
Σ Switch 5 In Switch 5 In Σ
11 11
12 12
18 Switch 5 Out Switch 5 Out 18
13 13
14 14
15 15
WSS 100
WSS 100
1X5 w/upgd
1X5 w/upgd
16 16
LC LC
Ch 1 In CMD44 CMD44 Ch 1 In
PEC: NTT862AA PEC: NTT862AA
Ch 1 Out Ch 1 Out
LC LC
Ch 2 In LC LC Ch 2 In
Common Out 2 2 Common Out
Ch 2 Out Ch 2 Out
1 1
Common In Common In
Example 2-way ROADM node (100 GHz 9x1/1x5 WSS, dual 2xOSC circuit packs)
LC LC
Ch 43 In Ch 43 In
Legend
Ch 43 Out Ch 43 Out
LC LC
= DSCM Ch 44 In Ch 44 In
= Attenuator Ch 44 Out Ch 44 Out

-------------------------------------------------------------------------------------------------------------------------------------------------
October 2019
Figure 4-31
OTS1 OTS2
Release 12.6
WSC WSC WSC WSC
2 1 2 1
OSC OSC OSC OSC

2 1 2 1

OSC1 In
OSC1 In

OSC2 Out
OSC2 Out
OSC1 Out
OSC1 Out
OSC2 In
OSC2 In
2
2
1
1
2
2
1
1
MLA SLA WSS WSS MLA

PEC: NTK552BA PEC: NTK552AA PEC: NTK553EA PEC: NTK553EA PEC: NTK552BA
Line B Mon Line B Mon 1 Monitor 1 Monitor 1 1 Line B Mon
1 1 1
Line A Mon Line A Mon OPM OPM Line A Mon
2 2 2 2 2

Monitor 2 Monitor 2
OSC B In OSC B In Switch 1 In Switch 1 In OSC B In
3 3 3
3 3
4 4 4
OSC A Out OSC A Out 4 4 OSC A Out
Common In
Common In Switch 1 Out Switch 1 Out
Line A In Line A Out Line A In Line A Out 17
A 7 7 17 Switch 2 In Switch 2 In Line B In Line B Out
8 8 A 6 B 5
5 5
6 6
5 B 6 5 6 Switch 2 Out Switch 2 Out 7 A 8
Line B Out Line B In Line B Out Line B In Line A Out Line A In
7 7 9:1
9:1
8 8
9 9
10 10
1:5 1:5
11 11
12 12
13 13
14 14
15 15
WSS 100
WSS 100
1X5 w/upgd
1X5 w/upgd
16 16
LC LC
Ch 1 Out Ch 1 Out
LC LC
Ch 2 Out Ch 2 Out
1 1
Common In Common In
LC LC
Ch 43 In Ch 43 In
Legend Ch 43 Out Ch 43 Out
LC LC
Ch 44 Out Ch 44 Out
= Attenuator
-------------------------------------------------------------------------------------------------------------------------------------------------
Example 2-way ROADM node (100 GHz 9x1/1x5 WSS, cascaded LIM, dual 2xOSC circuit packs)
October 2019
Figure 4-32
Release 12.6
WSC WSC
4 3
OTS1
OTS2 OSC OSC
2 1
OSC1 In
OSC2 Out
OSC1 Out
OSC2 In
2
2
1
1

MLA SLA WSS WSS MLA

PEC: NTK552BA PEC: NTK552AA PEC: NTK553EA PEC: NTK553EA PEC: NTK552BA
Line B Mon Line B Mon 1 Monitor 1 Monitor 1 1 Line B Mon
1 1 1
Line A Mon Line A Mon OPM OPM Line A Mon
2 2 2 2 2
Monitor 2 Monitor 2
OSC B In OSC B In Switch 1 In Switch 1 In OSC B In
3 3 3

3 3
4 4 4
OSC A Out OSC A Out 4 4 OSC A Out
Common In
Common In Switch 1 Out Switch 1 Out
Line A In Line A Out Line A In Line A Out 17
7 7 17 Switch 2 In Switch 2 In Line B In Line B Out
8 A 8 A 6 B 5
5 5
6 6
5 B 6 5 6 Switch 2 Out Switch 2 Out 7 A 8
Line B Out Line B In Line B Out Line B In Line A Out Line A In
7 7 9:1
9:1
8 8
9 9
10 10
1:5 1:5
11 11
12 12
13 13
14 14
15 15
WSS 100
WSS 100
1X5 w/upgd
1X5 w/upgd
16 16
LC LC
Ch 1 Out Ch 1 Out
LC LC
Ch 2 Out Ch 2 Out
1 1
Common In Common In
LC LC
Ch 43 In Ch 43 In
Legend Ch 43 Out Ch 43 Out
LC LC
Ch 44 Out Ch 44 Out
= Attenuator
-------------------------------------------------------------------------------------------------------------------------------------------------
Example 2-way ROADM node (100 GHz 9x1/1x5 WSS, cascaded LIM, single 2xOSC circuit pack)
October 2019
Figure 4-33
Example 2-way ROADM node (100 GHz 4x1 NTK553HA WSS, single 2xOSC circuit pack)

Figure 4-34
Example 2-way ROADM (50 GHz 2x1 NTK553KA/KC WSS, BMD-2, dual 2xOSC circuit packs)

Figure 4-35
Release 12.6
2xOSC PEC: NTK554BAE5 2xOSC PEC: NTK554BAE5
LC OSC1 Out
LC LC LC
OSC2 Out OSC1 Out OSC2 Out
1 OSC OSC 2 1 OSC OSC 2
1 1 2 2 1 1 2 2
OSC1 In OSC2 In OSC1 In OSC2 In
Loc: Shelf: Slot: Loc: Shelf: Slot:
WSS 50 GHz WSS 50 GHz

PEC: NTK553FA PEC: NTK553FA MLA
MLA 6500
PEC: NTK552BA PEC: NTK552BA
Mon 1 (B Out) Monitor 1 Monitor 1 Line B Mon
1 1 1 1
Monitor 2 OPM OPM Monitor 2 2
2 2 2
Mon 2 (A Out) Line A Mon
Switch1 Out Switch1 In OSC B In

OSC B In 4 3 3
3
Switch1 In Switch1 Out
4 3 4 4
OSC A Out OSC A Out
Switch2 Out Switch2 In
Line A In Line A Out Common In 6 5 Common Out Line B In Line B Out
8 7 21 CMD44 50GHz Blue CMD44 50GHz Blue 22 6 B 5
A Switch2 In Switch2 Out
5 PEC: NTT862BA 6
PEC: NTT862BA
Slot: 0 Switch3 In
Switch3 Out 7
8 7 A 8
5 6
9x1
B Ch1 Out
9x1

Line B Out Line B In Switch3 In 2 Ch1 In Switch3 Out
7 1 8
1530.33nm 1530.33nm
1 2 Switch4 In
Switch4 Out Ch1 In Ch1 Out 9
WSS 50 GHz
10
WSS 50 GHz
Ch2 Out Ch2 In
Switch4 In 4 3 Switch4 Out
9 1530.72nm 1530.72nm 10
3 4
Ch2 In Ch2 Out Switch5 In
Switch5 Out 11
12
Switch5 In Common In Common Out Switch5 Out
11 89 90 12
Switch6 Out Switch6 In

14 13
Common Out Common In
Switch6 In 90 89 Switch6 Out Σ 1:9
Σ 1:9 13 14
Common Out Switch7 Out Switch7 In Common In

16 Ch43 Out Ch43 In 15 21
22 86 85
Switch7 In 1546.92nm 1546.92nm Switch7 Out
15 85 86 16

Ch43 In Ch43 Out
Ch44 Out Ch44 In
88 87
1547.32nm 1547.32nm 9:1
9:1 87 88
Switch8 Out (Drop1) Ch44 In Ch44 Out Switch8 In (Add1)
18 17
Switch8 In (Add1) 18 Switch8 Out (Drop1)
17
Switch9 Out (Drop2) Switch9 In (Add2)

20 19
Switch9 In (Add2) CMD44 50GHz Red 20 Switch9 Out (Drop2)
19 CMD44 50GHz Red
PEC: NTT862BB PEC: NTT862BB
Slot: 0
Ch1 Out 1 Ch1 In
2
1547.72nm 1547.72nm
1 2
Ch1 In Ch1 Out
Ch2 Out Ch2 In
4 3
1548.11nm 1548.11nm
3 4
Ch2 In Ch2 Out
Common In Common Out

89 90
Common Out Common In

90 89
Ch43 Out 85 Ch43 In

86
1564.68nm 1564.68nm
Example 2-way ROADM node (50 GHz 9x1 WSS, dual 2xOSC circuit packs)

85 86
Ch43 In Ch43 Out

Ch44 Out 87 Ch44 In
88
1565.09nm 1565.09nm
87 88
Ch44 In Ch44 Out
October 2019
Figure 4-36
Example 2-way ROADM using 50 GHz 9x1 WSS with SRA (or SAM or ESAM) and XLA

Figure 4-37
Example 2-way ROADM using 50 GHz 9x1 WSS, SRA (or SAM or ESAM) and XLA added to existing
ROADM OTS with LIM, 2xOSC

Figure 4-38
Example 2-way ROADM using 50 GHz 9x1 WSS, ESAM (or SAM) and MLAx added to existing
ROADM OTS with LIM, 2xOSC

Figure 4-39
Example 2-way ROADM using 5x1 RLA

Figure 4-40
Example 2-way ROADM using 5x1 RLA with SRA, ESAM or SAM

Figure 4-41
Example 2-way ROADM using 50 GHz 9x1 WSS, MLA3 and CMD96

Figure 4-42
2-way Metro ROADM example 1 - Using 2x1 100 GHz WSS, BS5 & OMDF8s, CMD44, Drop-LIM

Figure 4-43
2-way ROADM example 2 - Using 4x1 100 GHz WSS, BS5 & OMDF8s, Cascaded LIM, DSCM

Figure 4-44
2-way ROADM example 3 - using mixed WSSs when new OTS added

Figure 4-45
3-way Metro ROADM example 1 - OTSs using 4x1 100 GHz WSSs, CMD44s, BS5/OMDF8s, LIMs

Figure 4-46
3-way ROADM example 2: With DIA

Figure 4-47
8-way ROADM using 2-slot 9x1 50 GHz WSSs

Figure 4-48
8-way Node - example shelf configuration view using 2-slot wide NTK553FC 9x1 50 GHz WSSs
Figure 4-49
7-way Node - example shelf configuration view using 3-slot wide NTK553FA 9x1 50 GHz WSSs

Figure 4-50
8-way Node - example shelf configuration view using mix of NTK553FA/NTK553FC 9x1 50 GHz
WSSs
ROADM/Metro ROADM with Mux Amp

As described earlier in this document, the SLA or MLA-based Mux Amp may
be warranted by link design requirements to ensure DWDM interfaces with a
lower Tx output power range can be launched with other DWDM Tx types of
a higher Tx output power range. Refer to “SLA/MLA Mux Amp” on page 3-124.
ROADM/Metro ROADM with Mux Amp and WL3n
An important application requiring the use of the Mux Amp is when WL3/WL3e
family of interfaces are mixed with WL3n interfaces.
The main system configurations that would require a mux amplifier in these
scenarios cover 50 GHz and 100 GHz ROADM applications:
• Configurations using NTK553KC 2x1 50 GHz WSS
— Refer to Figure 4-51 on page 4-105 for the configuration that uses the
SLA Line A port 7 and 8 (Line B is not used)
MLA. In this case, the Mux SLA is to be replaced by MLA if a Drop LIM
SLA as is also required.
• Configurations using NTK553HA 1x4 100 GHz WSS

SLA Line A port 7 and 8 (Line B is not used)
MLA. In this case, the Mux SLA is to be replaced by MLA if a Demux
SLA is also required. Furthermore, the CMD44 module has to be the
NTT862FA eCMD44.
• Configurations using NTK553FA/FC/LA 9x1 50 GHz WSS
— The preferred approach if link budget does not allow the addition of the
WL3n alongside other transmitter types is shown in Figure 4-55 on
page 4-109. In this example the OPS is also shown.
In addition:
• For the above main 100 GHz or 50 GHz configuration types, use of the
OPS with WL3n further exacerbates the Tx power delta between WL3n
and WL3/WL3e
• Other configurations could require a mux amp if either the WSS dynamic
range or link budget does not allow for the WL3n to be added to the same
CMD44 module
• Metro ROADM configurations using OMDF4/8 DWDM channel filters
support mux amplifiers as well
In brownfield deployment cases using the above-mentioned WSS types

where there are no available WSS switch ports to add a CMD/BMD/Mux Amp,
an out-of-service reconfiguration would be necessary.
• For instance, if the Mux Amp is added when traffic is already up on the
NTK553KC 2x1 50 GHz WSS using the local add/drop switch port
• If using the NTK553FA/FC/LA 9x1 50 GHz WSS where the Mux Amp is
used on switch port 8 and/or 9, the SLA would be used. If there was a
requirement for a Drop LIM function, this would be covered already by the
EDFA embedded in the WSS already covering the drop direction (an MLA
would not be used). Refer to Figure 4-56 on page 4-110.
• If the link design is valid, the power of existing channels would have to be
lowered. This would also entail reducing Tx adjacency max/max-typical/
nominal values of non-WL3n interfaces, potentially to match those of
WL3n.
Attention: In brownfield deployments where there are no WSS switch ports

available to add additional CMD/BMD equipment, the insertion of the Mux
Amp is a traffic impacting reconfiguration. For a customized method of
procedure to perform this insertion, please contact Ciena Network
Engineering Services.

Figure 4-51
Mux Amp for WL3n: 2x1 50 GHz NTK553KC with SLA

Figure 4-52
Mux Amp for WL3n: 2x1 50 GHz NTK553KC with MLA (includes Drop LIM)

Figure 4-53
Mux Amp for WL3n: 1x4 100 GHz NTK553HA with SLA

Figure 4-54
Mux Amp for WL3n: 1x4 100 GHz NTK553HA with MLA (includes Drop LIM)

Figure 4-55
Mux Amp for WL3n: 9x1 50 GHz NTK553LA/LB with MLA (includes Drop LIM and OPS)

Figure 4-56
Mux Amp for WL3n: 9x1 50 GHz NTK553LA/LB with SLA on existing CMD44

Dynamic Gain Flattening Filter (DGFF) using 2-way ROADM

The dynamic gain flattening filter (DGFF) is a variant of a ROADM node with
all channels glassed through. Link budget analysis dictates the placement of
back-to-back WSSs or RLAs for the purpose of a DGFF function used to
optimize system performance. The DGFF provides a per-wavelength
attenuation profile for control purposes to overcome the accumulation of gain
tilt and ripple in an optical link.
DGFF nodes based on the 20x1 WSS (with FIM1 or FIM5) or the 5x1 RLA are
supported.
For 2-way ROADM OTSs containing SRA/XLA hardware, supported hardware

is identical to that indicated in “1-way ROADM Terminal - WSS and SRA/XLA
deployment rules” on page 4-53, excluding CMD44 filters which would not be
necessary at a DGFF node.
For 2-way ROADM OTSs containing ESAM/SAM and XLA/MLAx hardware,

supported hardware is identical to that indicated in “1-way ROADM Terminal -
WSS and SRA/XLA deployment rules” on page 4-53, excluding CMD44 filters
which would not be necessary at a DGFF node.
Colored Directionless
The following rules apply to the DIA configuration:
• A 7-slot, 14-slot, 32-slot or 6500-7 packet-optical shelf housing the DIA
OTS equipment can only be equipped with the SP2 Shelf Processor
(NTK555CA/EA/FA).
• A 7-slot Type 2 shelf housing the DIA OTS equipment must be equipped
with the SPAP2 OSC w/ 2xSFP (NTK555NA/NB).
• At a node, all equipment part of the DIA OTS must reside in the same
shelf. The DIA OTS equipment can be in the same shelf as the ROADM
OTS equipment or it can be in a different shelf. However, all shelves
containing Photonic equipment (ROADM OTSs and DIA OTSs) must be
TID consolidated.
• The DIA amplifier gain is set to minimum gain at the creation of the DIA
OTS. The DIA amplifier gain must be user-provisioned according to
OnePlanner report.
• The DIA amplifier OPTMON port 4 facility is set to OOS-MA by software
since this facility is not used in the DIA configuration.
• The embedded amplifier within the 50GHz 9x1 WSSOPM circuit pack is
set to minimum gain by software and cannot be user-provisioned.
• A wavelength can only be added/dropped once per direction at a node.

— A wavelength can either be added/dropped to a CMD on the backbone

WSS or the DIA CMD at the same node. Once the channel is
added/dropped at a CMD on the backbone WSS, it is blocked by
software from being added/dropped at a DIA CMD at the same node.
• The DIA WSS can connect to the backbone WSS unamplified drop ports
or amplified drop ports. The amplified drop ports can only be used if no
CMD44 is connected to any WSS amplified drop port.
• When the backbone WSS Switch ports 8 or 9 are used for interconnection
to a DIA OTS WSS, a pad may be required at the DIA OTS WSS Switch
port 8/9 Input and Output ports. OnePlanner determines whether padding
is required. The pad must be user-provisioned as Excess Loss on the
following ADJ-FIBER facilities:
— DIA OTS WSS Switch port 8/9 Output port (i.e., port 18 or 20)
— Each backbone WSS Switch port 8/9 Output port (i.e., port 18 or 20)
• Engineering rules regarding WSS variants that can be used at the DIA
OTS and the Backbone OTS:
— WSS variants with different frequency grid is not permitted
— 50 GHz DIA OTS WSS must be paired with 50 GHz backbone OTS
WSS
— 100 GHz DIA OTS WSS must be paired with 100 GHz backbone OTS
WSS
Attention: Not enforced by software, but enforced by engineering

rules in OnePlanner.
— WSS variants with same frequency grid but different number of ports
is permitted (OnePlanner allows DIA OTS WSS type selection). For
instance:
– 100 GHz 9x1/1x5 (or 100 GHz 4x1) DIA OTS WSS with 100 GHz
2x1 backbone OTS WSS is permitted
– 100 GHz 2x1 DIA OTS WSS and 100 GHz 9x1/1x5 (or 100 GHz
4x1/1x4) backbone OTS WSSs are permitted
Attention: The single-slot NTK553KA 50 GHz 2x1 WSS is currently

only supported in configurations that use a maximum of two OTSs.
This means that the module cannot be used in the DIA configuration
backbone OTS or DIA OTS. Use the NTK553KC 50 GHz 2x1 WSS
instead.
• When only using 5x1 RLA for ROADM degrees,

— the RLA port usage recommendations are as follows:

– Use first available Switch port starting from Switch port 5 then
decrementing to connect the COADM/DIA add/drop banks
incrementing to connect other degrees
– It is not recommended to use amplified ports on the DIA WSS
(SW8, SW9)
— The possible DIA mux/demux structures are:
– BMD2/CMD44 Blue/CMD44 Red
– CMD64
– CMD96
— RLA paired with ESAM/SRA is supported
— In this release, using the RLA in the DIA OTS is not supported
Colorless Directionless
The following rules apply to the Colorless Directionless configuration:
• A 14-slot or 32-slot shelf housing the COADM OTS equipment must be
equipped with the SP2 Shelf Processor (NTK555CA/EA/FA).
• At a node, all equipment part of the COADM OTS must reside in the same
shelf. All equipment part of the DIA OTS must reside in the same shelf.
The DIA OTS, COADM OTS and ROADM OTS equipment can be in the
same shelf or in different shelves. However, all shelves containing ROADM
OTS, DIA OTS and COADM OTS equipment must be TID consolidated.
• From a OAM&P perspective, within the COADM OTS, The LIM (MLAx)
OPTMON Port 4 is set automatically OOS by software since no OSC will
be connected to the amplifier.
• For a list of service circuit packs that can connect to CCMD12 circuit
packs, refer to “Supported transponders for colorless and CDC line
systems” on page 3-107.
• On the DIA WSS, the recommended Switch ports connecting to backbone
WSS or RLA are SW1 through SW7. Using the amplified ports
(SW8-SW9) has an OSNR impact and is not recommended unless
required. In this case the DIA WSS drop EDFA gain is left at default value
(6 dB).
• When only using 9x1 WSS for ROADM degrees, the backbone WSS port
usage recommendations are as follows:
— Use first available Switch port starting from Switch port 9 then

• When only using 5x1 RLA for ROADM degrees, the RLA port usage
recommendations are as follows:
Colorless Directional or Colorless Direct Attach (CDA)

The following rules apply to the CDA configuration with the COADM OTS
directly attached to the ROADM OTS:
• A 14-slot or 32-slot shelf housing the COADM OTS equipment must be
equipped with the SP2 Shelf Processor (NTK555CA/EA/FA).
• At a node, all equipment part of the COADM OTS must reside in the same
shelf. The COADM OTS and ROADM OTS equipment can be in the same
shelf or in different shelves. However, all shelves containing ROADM OTS
and COADM OTS equipment must be TID consolidated.
• The COADM OTS LIM (MLA2/MLA3) has Line B (port 5) pointing to the
backbone fiber plant (through the ROADM WSS/LIM).
— This is the reverse of the Colorless Directionless OADM (DIA +
COADM) case, where the DIA OTS LIM (MLA) Line A (port 7) points
to the backbone fiber plant (through the DIA and ROADM WSS/LIM).
• The COADM OTS cannot be directly connected to ROADM OTS subtypes
that face submarine wet plant as part of Submarine Line Terminating
Equipment (SLTE) configurations. For further information on SLTE
configurations, refer to NTRN72AA Submarine Networking Application
Guide.
• Refer to “96-channel support” on page 3-104 if you require 96 channels
through these configurations.
• If CMD44s are used:
— CMD44 50 GHz Blue and Red are connected to ROADM OTS
amplified drop ports (SW8 and SW9).
— CMD44 equipment must be provisioned in the same shelf as the
backbone WSS it connects to.
• From a OAM&P perspective, within the COADM OTS, The LIM (MLAx)
OPTMON Port 4 is set automatically OOS by software since no OSC will
be connected to the amplifier.
• If using COADM OTS connects to either the RLA or an amplified drop port
of the 9x1 WSS, special provisioning of the COADM OTS MMPO
parameter is required. Refer to Technical Publication 323-1851-221,
Commissioning and Testing for details.

• If using COADM OTS connects to the RLA, support of OPS-protected

channels connected to the CCMD12 (using internal or external OPS) is
subject to link budget. In this case, it is recommended to place the ROADM
and COADM OTSs in the same shelf, to avoid any extra inter-shelf loss.
Low channel count Colorless Directionless

The following rules apply to the low channel count colorless directionless node
configuration:
• For supported hardware, see “Hardware” on page 3-56.
• The WSS and CCMD12 in the add/drop bank must be in the same shelf.
— ROADM OTS equipment and add/drop bank equipment can reside in
separate shelves of a TIDc node though.
• The WSS + CCMD12 add/drop banks must be provisioned using the TID
sequencing method (they are not DIA OTSs), where the WSS acts as
“root” equipment.
• On the add/drop bank WSS, the recommended Switch ports connecting
to backbone WSS or RLA are SW1 through SW7. Using the amplified
ports (SW8-SW9) has an OSNR impact and is not recommended unless
required (for example, when there are 8 backbone degrees). In this case
add/drop bank WSS drop EDFA gain is left at default value (6 dB).
• When only using 9x1 WSS for ROADM degrees:
— On the ROADM OTS WSS (backbone), the allowed Switch ports
connecting to add/drop WSSs are SW1 through SW9, i.e. both
amplified and unamplified drop ports are allowed.
— Backbone WSS port usage recommendations:
– For 8-degree ROADM nodes, use first available Switch port
starting from Switch port 9 then decrementing to connect the
add/drop bank. Otherwise, start with Switch port 7 decrementing.
– Use first available switch port starting from Switch port 1 then
incrementing to connect other degrees.
• When only using 5x1 RLA for ROADM degrees:
— On the RLA, the allowed Switch ports connecting to add/drop WSSs
are SW1 through SW5.
— RLA port usage recommendations:
decrementing to connect the add/drop bank(s).
– Use first available switch port starting from Switch port 1 then
incrementing to connect other degrees.

Low channel count Colorless Directionless and Colored Directional using

9x1 WSS
The following rules apply to the low channel count colorless directionless node
and local colored add/drop configuration:
• For supported hardware, see “Hardware” on page 3-62.
• For rules on the “Low channel count Colorless Directionless” refer to page
4-115.
• DIA WSS connects to backbone WSS unamplified drop ports but can also
connect to backbone WSS amplified drop ports if no CMD44 50GHz is
connected to any WSS amplified drop port
• CMD44 are allowed on the backbone WSS.
• CMD44 (and BMD2/XLA/MLAx) equipment must be provisioned in the
same shelf as the backbone WSS it connects to
— XLA/MLAx gain values associated with CMD are set and forget
provided by OnePlanner
Colorless Directional or Colorless Direct Attach (CDA) using 20x1 WSS,

FIM Type 4, FIM Type 5 and FIM Type 6
The following rules apply to the CDA configuration with CCMD12 directly
attached to the ROADM OTS:
• A 7-slot, 14-slot, 32-slot or 6500-7 packet-optical shelf housing the CDA
equipment must be equipped with the SP2 Shelf Processor
(NTK555CA/EA/FA).
• A 7-slot Type 2 shelf housing the CDA equipment must be equipped with
the SPAP2 OSC w/ 2xSFP (NTK555NA/NB).
Attention: The NTK503KA 7-slot Type 2 shelf with NTK555NA/NB SPAP2

2xOSC 2xSFP hardware does supported an OSRP TIDc primary shelf, only
when the L0 CP application uses a ‘L0 Provisioning’ OSRP Node Type. For
further information on L0 CP common equipment engineering rules, refer to
NTRN71AA.2 Control Plane Application Guide - Layer 0 (Photonic).
• At a node, all the equipment forming the degree/OTS (WSS 20x1 and line
facing amplifier circuit packs) must be equipped in the same shelf.
• The CCMD12s can reside in the same shelf as the degree/OTS equipment
or in a different shelf. The FIMs can reside in the same shelf as the
CCMD12s or degree/OTS equipment or in a different shelf.
• 6500 transponder equipment can be in the same shelf as the degree/OTS
equipment or in the same shelf as the add/drop structure equipment or in
a different shelf. For more details on SPLI functionality refer to “Service
and Photonic Layer Interoperability (SPLI)” on page 1-48.

• All shelves at the node containing the degree/OTS equipment, the FIM
and the add/drop structure equipment must be TID consolidated.
• A Photonic domain containing a CDA with CCMD12 direct attach node
must contain only one optical section.
• Channel provisioning is done using L0 Provisioning Control Plane type. As
a result, the CDA with CCMD12 direct attach configuration can only
interwork with other configurations that use the L0 Provisioning Control
Plane type.
CMD44 direct attach configuration

If using the configuration described in “Colorless and Colored Direct Attach
(CDA) using 20x1 WSS, FIM Type 4, FIM Type 5 and FIM Type 6” on page
3-74, follow these rules and guidelines:
• The CMD44s and BMD2 must connect to one of the two WSS 20x1 high
isolation ports. These are at WSS MPO port D switch port 19 and 20. On
the FIM4, these are at the following LC ports: 26/27, 28/29 for FIM4 MPO
port 2 and 46/47, 48/49 for FIM4 MPO port 4.
• The external amplifier connected to the CMD44s and BMD2 can be MLA3
or XLA.
— The XLA/MLA3 gain values are set and forget values provided by
OnePlanner.
• The CMD44 direct attach equipment (CMDs/BMD2/XLA/MLA3):
— must be provisioned in the same shelf as the backbone WSS it
connects to.
— must be provisioned via TID sequence provisioning by editing the
appropriate FIM4 TIDSLOTSEQ sequence instance to include the
amp and the CMDs/BMD2 slot numbers.
• Up to 9 CCMD12 can connect to a degree if CMD44s are connected to it.
Colorless, Directionless and Contentionless (CDC)

The following rules apply to the CDC configuration:
• Although the NTK553MA WSS Flex C-Band w/OPM 20x1 circuit pack
supports Flexible Grid operation, it operates only in Fixed Grid mode in the
current release.
• A 7-slot, 14-slot, 32-slot or 6500-7 packet-optical shelf housing the CDC
equipment must be equipped with the SP2 Shelf Processor
(NTK555CA/EA/FA).

• A 7-slot Type 2 shelf housing the CDC equipment must be equipped with
the SPAP2 OSC w/ 2xSFP (NTK555NA/NB).
• At a node, the WSS 20x1 and line facing amplifier circuit packs must
reside in the same shelf. The CCMD8x16s can reside in the same shelf as
the WSS 20x1 and line facing amplifier circuit packs or in a different shelf.
The FIM can reside in the same shelf as the CCMD8x16s or the WSS
20x1 and line facing amplifier circuit packs or in a different shelf. However,
all shelves containing CDC Photonic equipment must be TID
consolidated.
• For the XLA used between the WSS 20x1 and the WSS 9x1 in the
brownfield CDC configuration, the XLA amplifier gain must be
user-provisioned according to OnePlanner report.
MPO cable requirements

The MPO cable requirements at a CDC node are as follows:
• Install 4 MPO cables for each WSS:
— One cable from WSS circuit pack Switch A to FIM WSS port A
— One cable from WSS circuit pack Switch B to FIM WSS port B
— One cable from WSS circuit pack Switch C to FIM WSS port C
— One cable from WSS circuit pack Switch D to FIM WSS port D
• If the number of degrees at the node is 4 or less, install 1 MPO cable per
CCMD8x16:
— From CCMD8x16 port 33 to FIM Type 1 CMD port 1A-11A or FIM Type
2 CMD port 1A-20A
• If the number of degrees at the node is greater than 4 or if the number of
degrees is 4 or less with plans to grow in the future: install 3 MPO cables
per CCMD8x16:
— One cable from CCMD8x16 port 33 to FIM Type 1 CMD port 1A-11A
or FIM Type 2 CMD port 1A-20A
— One cable from CCMD8x16 port 34 to CMD port 35
— One cable from CCMD8x16 port 36 to FIM Type 1 CMD port 1B-11B
or FIM Type 2 CMD port 1B-20B

CMD44 50 GHz or 100 GHz direct attach configuration

If using the configuration described in “Colorless Directionless Contentionless
(CDC) and Colored using 20x1 WSS” on page 3-83 or “Colorless
Directionless Contentionless (CDC) and Colored using 20x1 WSS” on page
3-83, follow these rules and guidelines:
• The CMD44 bank must connect to one of the two WSS 20x1 high isolation
ports. These are at WSS MPO port D switch port 19 and 20. On the FIM1,
these are at the following LC ports: 33/34 or 35/36 for degree #1, 37/38 or
39/40 for degree #2, and so on until 61/62 or 63/64 for degree #8.
• The external amplifier connected to the CMD44 bank can be MLA3 or
XLA.
— The XLA/MLA3 gain values are set and forget values provided by
OnePlanner.
• The CMD44 direct attach equipment (CMDs/BMD2/XLA/MLA3 if using
50 GHz, or CMD/XLA/MLA3 if using 100 GHz):
— must be provisioned in the same shelf as the backbone WSS it
connects to.
— must be provisioned via TID sequence provisioning by editing the
appropriate FIM1 TIDSLOTSEQ sequence instance to include the
amp and the CMDs/BMD2 slot numbers.
• Connecting CMD44s to a degree does not change the number of
CCMD8x16 that can connect to the FIM1 (i.e., 11), since CCMD8x16s are
not tied to a particular degree but shared amongst all degrees.
T-Series Colorless, Directionless and Contentionless (CDC)
The following rules apply to the T-Series CDC configuration:
• Although the RLA 20x1 supports Flexible Grid operation, it operates only
in Fixed Grid mode in the current release.
• At a node, the RLA, CCMD 16x12, CCMD 8x4, MFC and FIM do not need
to be equipped in the same shelf. However, all shelves containing CDC
Photonic equipment must be TID consolidated.
• The MFC (Multi-function Carrier) module acts as a carrier for up to 4
pluggable modules. The AMP4, OTDR4 or CCMD 8x4 pluggable modules
can be equipped in an MFC module. The AMP4 and OTDR4 pluggable
modules can also be equipped in the CCMD 16x12 module.
• In this release, the OTDR4 module must be in the same shelf as the
RLA(s) it is connected to.
• A Photonic domain containing a T-Series CDC node must contain only one
optical section.
• For a list of service circuit packs that can connect to CCMD 16x12 and
CCMD 8x4 modules, refer to “Supported transponders for colorless and
CDC line systems” on page 3-107.

The following considerations apply when designing a T-Series CDC photonic

node:
• The following equipment is required at a T-Series CDC node using CCMD
16x12 modules if the number of degrees at the node is less than 5:
— Up to 4 NTK722AA RLA 20x1 modules (one per OTS)
— Up to 16 (if using FIM Type 3) or up to 11 (if using FIM Type 1)
NTK723AA CCMD 16x12 modules
NTK720BA AMP4 pluggable modules (1 per CCMD 16x12)
— One NTK504CA FIM Type 1 or one NTK504CC FIM Type 3
— Up to 16 NTTC97Ax MPO(F)-MPO(F) cables to connect RLA to FIM
(4 x # of degrees)
NTTC97Ax MPO(F)-MPO(F) cables to connect CCMD 16x12 to AMP4
pluggable (1 MPO cable per CCMD 16x12)
NTTC97Ax MPO(F)-MPO(F) cables to connect AMP4 pluggable to
FIM (1 MPO cable per AMP4 pluggable)
• The following equipment is required at a T-Series CDC node using CCMD
16x12 modules if the number of degrees at the node is between 5 and 8:
— Up to 8 NTK722AA RLA 20x1 modules (one per OTS)
NTK723AA CCMD 16x12 modules
NTK720BA AMP4 pluggable modules (2 per CCMD 16x12)
— One NTK504CA FIM Type 1 or one NTK504CC FIM Type 3
— Up to 32 NTTC97Ax MPO(F)-MPO(F) cables to connect RLA to FIM
(4 x # of degrees)
NTTC97Ax MPO(F)-MPO(F) cables to connect CCMD 16x12 to first
AMP4 pluggable (1 MPO cable per CCMD 16x12)
NTTC97Ax MPO(F)-MPO(F) cables to connect first AMP4 pluggable
to FIM (1 MPO cable per AMP4 pluggable)
NTTC97Ax MPO(F)-MPO(F) cables to connect CCMD 16x12 to
second AMP4 pluggable (1 MPO cable per CCMD 16x12)


NTTC97Ax MPO(F)-MPO(F) cables to connect second AMP4
pluggable to FIM (1 MPO cable per AMP4 pluggable)
MPO cable interconnection at a T-Series CDC node using FIM Type 3

MPO cable interconnection at a T-Series CDC node using FIM Type 3 is as
follows:
• Connect degrees (RLA modules) to FIM (shown in Figure 4-57 on page
4-122). For each RLA:
— Connect one MPO cable from RLA Switch A port (port 21) to an RLA
designated FIM Fiber Group port A
— Connect one MPO cable from RLA Switch B port (port 22) to the same
RLA designated FIM Fiber Group port B
— Connect one MPO cable from RLA Switch C port (port 23) to the same
RLA designated FIM Fiber Group port C
— Connect one MPO cable from RLA Switch D port (port 24) to the same
RLA designated FIM Fiber Group port D
• Connect add/drop to FIM (shown in Figure 4-58 on page 4-123).
— If the number of degrees at the node is less than 5. For each CCMD
16x12:
– Connect one MPO cable from CCMD 16x12 Com A port (port 41)
to AMP4 pluggable CCMD port (port 1)
– Connect one MPO cable from AMP4 pluggable Common port (port
41) to a CCMD designated FIM Fiber Group port A
— If the number of degrees at the node is between 5 and 8. For each
CCMD 16x12:
to the first AMP4 pluggable CCMD port (port 1)
– Connect one MPO cable from the first AMP4 pluggable Common
port (port 41) to a CCMD designated FIM Fiber Group port A
– Connect one MPO cable from CCMD 16x12 Com B (port 42) to the
second AMP4 pluggable CCMD port (port 1)
– Connect one MPO cable from the second AMP4 pluggable
Common port (port 41) to the same CCMD designated FIM Fiber
Group port B

Figure 4-57
Connect degrees (RLA modules) to FIM Type 3

Figure 4-58
Connect add/drop (CCMD modules) to FIM Type 3
MPO cable interconnection at a T-Series CDC node using CCMD 16x12 and FIM
Type 1
MPO cable interconnection at a T-Series CDC node using FIM Type 1 is as
follows:
• Connect degrees (RLA modules) to FIM (shown in Figure 4-59 on page
4-124). For each RLA:
— Connect one MPO cable from RLA Switch A port (port 21) to a WSS
designated Group port A
— Connect one MPO cable from RLA Switch B port (port 22) to the same
WSS designated Group port B
— Connect one MPO cable from RLA Switch C port (port 23) to the same
WSS designated Group port C
— Connect one MPO cable from RLA Switch D port (port 24) to the same
WSS designated Group port D
• Connect add/drop to FIM (shown in Figure 4-60 on page 4-125).
— If the number of degrees at the node is less than 5. For each CCMD
16x12:

to AMP4 pluggable CCMD port (port 1)
– Connect one MPO cable from AMP4 pluggable Common port (port
41) to a CCMD designated Group port A
— If the number of degrees at the node is between 5 and 8. For each
CCMD 16x12:
to the first AMP4 pluggable CCMD port (port 1)
– Connect one MPO cable from the first AMP4 pluggable Common
port (port 41) to a CCMD designated Group port A
– Connect one MPO cable from CCMD 16x12 Com B (port 42) to the
second AMP4 pluggable CCMD port (port 1)
– Connect one MPO cable from the second AMP4 pluggable
Common port (port 41) to the same CCMD designated Group port
B
Figure 4-59
Connect degrees (RLA modules) to FIM Type 1

Figure 4-60
Connect add/drop (CCMD modules) to FIM Type 1
OTDR4 interconnection at a T-Series CDC node

The OTRD4 pluggable provides the ability to run OTDR traces for up to 4
degrees. An OTDR4 port connects to an RLA using RLA port 13. Through
ADJ provisioning on port 13 (done using the Site Manager Photonic
Configuration Management application), software determines which OTDR4
module/port the trace request needs to be sent to.
OPM engineering rules

The OPM function is provided:
• At channel access nodes:
— as part of a WSSOPM or RLA circuit pack
— as part of SMD circuit pack
— as part of the NTK553PA C-Band 50 GHz 2-port OPM circuit pack
• At Line Amp nodes
— within the standalone NTK553PA C-Band 50 GHz 2-port OPM circuit
pack that can be connected to LIMs at Line Amp nodes (using
Amplifier OTS subtypes).

The standalone C-Band 50 GHz 2-port OPM circuit pack is not provisioned as
part of any OTS subtype.
Standalone 50 GHz 2-port OPM and Enhanced CMD44 50 GHz deployment rules
The following engineering rules apply to standalone 50 GHZ 2-port OPMs
used with Enhanced CMD44 50 GHz modules.
• A maximum of four (4) 50 GHz OPM 2-port circuit packs are supported per
shelf
• A maximum of one 50 GHz OPM 2-port circuit pack is supported per OTS
• The 50 GHz OPM 2-port circuit pack and the Enhanced CMD44 50 GHz
modules fibered to the OPM must be provisioned in the same shelf
• An OPM can only be fibered to 2 CMD44 modules belonging in the same
OTS. This means an OPM circuit pack cannot be shared between 2
shelves or between 2 CMD44 modules that are in different OTSs.
• Enhanced CMD44 50 GHz modules have to be provisioned in an OTS in
order to have Performance Monitoring support
• The 50 GHz OPM 2-port circuit pack cannot be connected to the monitor
ports of line facing amplifiers
Standalone 50 GHz 2-port OPM when used at Line Amp node

The following rules apply to standalone 50 GHz 2-port OPM when used at a
Line Amp node, shown in Figure 4-65 on page 4-132 and Figure 4-66 on page
4-133:
• The maximum number of 50GHz OPM 2-port circuit packs per shelf is 4
• The 50GHz OPM 2-port circuit pack and LIM circuit pack(s) fibered to the
50GHz OPM 2-port circuit pack must be provisioned in the same shelf
• For fibering between the standalone OPM and LIM:
— A single OPM can be fibered to two different LIM circuit packs that are
in different OTSs. An OPM and each LIM the OPM is fibered to must
reside on the same shelf.
Standalone 50 GHz 2-port OPM when connected to available LIM monitor ports
at ROADM or TOADM nodes
The following rules apply to standalone 50 GHz 2-port OPM when connected
to available LIM ports at TOADM or ROADM nodes.
• Can be connected to available LIM (MLA3, MLA2, MLA2v, MLA, SLA and
LIM) or XLA monitor ports
• OPM values are not used by DOC if provisioned on TOADM configurations
(as is the case for OPMs at Line Amp nodes)
• The maximum number of OPM 2-port circuit packs per shelf is 4
• The maximum number of OPM 2-port circuit packs per OTS is 1

• The OPM 2-port circuit pack and the circuit pack fibered to the OPM 2-port
circuit pack must be provisioned in the same shelf
• An OPM can only be fibered to one circuit pack. This implies an OPM
circuit pack cannot be shared between 2 shelves or between 2 circuit
packs that are in different OTSs
For topology provisioning information for the NTK553PA OPM C-Band 2-port
circuit pack at a ROADM or TOADM node, refer to “Provisioning non-derived
adjacencies” on page 5-17.
An example showing the standalone OPM at a symmetric TOADM node is

Generic OPM engineering rules

The following rules apply to the OPM function.
• The maximum number of OPMs per shelf is a function of the Shelf
Processor type:
– SP2: 16
• SP2 circuit pack PECs include:
— NTK555CA/EA/FA
— NTK555LA (SPAP)
— NTK555NA/NB (SPAP-2 w/2xOSC 2xSFP)
Photonic Line Amplifier node
Examples for the inter-connections between Photonic equipment at typical
uncompensated or compensated Photonic Line Amplifier nodes are shown in:
The dual 2xOSC circuit pack configuration (see Figure 4-63) has the
advantage of redundancy over the single 2xOSC circuit pack configuration
(see Figure 4-62). It prevents data communications isolation for the shelf in
case of a 2xOSC circuit pack failure.
Depending upon the configuration, a single NTK554BA 2xOSC circuit pack

can be replaced by the SPAP-2 w/2xOSC 2xSFP circuit pack on a 2-slot or
7-slot type 2 shelves to save slot-space.

Figure 4-61
Photonic Line Amplifier node (single 2xOSC configuration, uncompensated)
Figure 4-62
Photonic Line Amplifier node (single 2xOSC configuration, compensated)

Figure 4-63
Photonic Line Amplifier node (dual 2xOSC configuration, compensated)
-------------------------------------------------------------------------------------------------------------------------------------------------
WSC WSC WSC WSC

2 1 2 1
OSC OSC OSC OSC

2 1 2 1
OSC2 Out
OSC1 Out
OSC2 Out
OSC1 Out
OSC2 In
OSC1 In
OSC2 In
OSC1 In
2
2
1
1
2
2
1
1
MLA MLA
PEC: NTK552BA PEC: NTK552BA
Line B Mon Line B Mon
1 1
Line A Mon Line A Mon
2 2
OSC B In OSC B In
3 3
4 4
OSC A Out OSC A Out
8 A 7 6 B 5
5 B Line B In
6 7
Line A Out
A 8
Line B Out Line A In
Legend
= DSCM
= Attenuator
OTS1 OTS2

Figure 4-64
Photonic Line Amplifier node (single 2xOSC configuration, MLA2v, compensated)
The following Line Interface Modules are supported at Line Amplifier nodes:
• LIM
• SLA
• MLA/MLA2/MLA2v/MLA3
Systems with Metro ROADM configurations that require Line Amp nodes can
use any of the above circuit packs as well at Line Amp nodes.
Possibilities are:
• MLA-MLA, MLA2-MLA2, MLA3-MLA3, SLA-SLA, MLA3-LIM, MLA2-LIM,
MLA-LIM, SLA-LIM, SLA-MLA3, SLA-MLA2, and SLA-MLA.
• Pads and/or DSCMs may or may not be used depending on what
OnePlanner indicates.
Note that the MLA2v is supported in conjunction with other MLA2v circuit
packs, or LIM types, at a Line Amp node.
• The MLA2v can also face any supported LIM module type located in an
AMP or ROADM OTS at the other side of a span in an asymmetric
configuration.
• For further information, refer to “MLA2v - EDFA with embedded VOA” on
page 3-119.

Photonic Line Amplifier node with OPM

capabilities. Refer to Figure 4-65 on page 4-132 for the case where one OPM
is assigned per OTS LIM. Refer to Figure 4-66 on page 4-133 for the case
where an OPM is shared between LIMs of two Amplifier OTSs.
For information on provisioning the NTK553PA OPM C-Band 2-port circuit

pack at a Line Amplifier node, refer to “Provisioning non-derived adjacencies”
on page 5-17.
For OPM deployment rules, refer to “OPM engineering rules” on page 4-125.

Figure 4-65
Two NTK553PA OPM C-Band 2-port circuit pack at Line Amplifier node

Figure 4-66
NTK553PA OPM sharing between LIMs at Line Amplifier node

Photonic Line Amplifier node with Raman (SRA)/ESAM/SAM, XLA and OPM
A Line Amplifier node using SRA, ESAM, SAM and XLA hardware can be
deployed (see Figure 4-69 on page 4-138).
Such AMP configurations contain 3 line facing circuit packs.

• SRA - XLA – SRA
• SRA - XLA – ESAM/SAM
• ESAM/SAM - XLA – SRA
A standalone OPM is optional at such a node.
The following rules apply:

• An SRA, ESAM or SAM must always be used in conjunction with an XLA
circuit pack. The use of an SRA versus an ESAM or SAM is based on user
requirements:
— The XLA is paired with SRA for Raman span (long spans)
— The XLA is paired with a ESAM/SAM (short spans)
— Cascaded LIM (Interior SLA) configurations are not currently
supported in AMP OTSs configured with SRA/ESAM/SAM and XLA
hardware
• Other rules for the following hardware
— SRA, ESAM, SAM and XLA circuit packs
— OSC SFPs and the OSC filter function
— Common Equipment
are identical with those indicated in “1-way ROADM Terminal - WSS and
SRA/XLA deployment rules” on page 4-53.

Figure 4-67
Uncompensated Photonic Line Amplifier node with SRA (or SAM or ESAM), XLA, standalone OPM

Figure 4-68
Compensated Photonic Line Amplifier node with SRA, XLA and standalone OPM

Photonic Line Amplifier node with ESAM/SAM, MLAx/XLA and OPM

A Line Amplifier node using ESAM, SAM and XLA/MLAx hardware can be
deployed (see Figure 4-69 on page 4-138).
Series of 3 circuit packs:

• ESAM/SAM - MLAx - ESAM/SAM
• ESAM/SAM - MLAx - MLAx
• MLAx - MLAx - ESAM/SAM
• ESAM/SAM - MLAx - LIM
• LIM - MLAx - ESAM/SAM
• ESAM/SAM - XLA - ESAM/SAM (any combination)
Series of 4 circuit packs:

• ESAM/SAM - MLAx - MLAx - ESAM/SAM
• ESAM/SAM - XLA - XLA - ESAM/SAM
A standalone OPM is optional at such a node.
The following rules apply:

• An ESAM or SAM must always be used in conjunction with an MLAx
(MLA/MLA2/MLA3) or XLA circuit pack. The use of an ESAM versus a
SAM is based on user requirements:
— The XLA/MLAx is paired with a ESAM (short spans and OTDR
requirements)
— The XLA/MLAx is paired with a SAM (short spans)
— Cascaded LIM (Interior SLA) configurations are not currently
supported in AMP OTSs configured with ESAM/SAM and XLA/MLAx
hardware.
• Other rules for the following hardware
— ESAM, SAM and XLA, MLAx circuit packs
— OSC SFPs and the OSC filter function
— Common Equipment
are identical with those indicated in “1-way ROADM Terminal - WSS and
SRA/XLA deployment rules” on page 4-53.

Figure 4-69
Uncompensated Photonic Line Amplifier node with ESAM (or SAM), MLAx/XLA, standalone OPM

Figure 4-70
Compensated Photonic Line Amplifier node with ESAM, MLAx and standalone OPM

SCMD4 based Thin Terminal or TOADM

The following rules apply to the SCMD4 based Thin Terminal or TOADM
configuration:
• Regarding TOADM rings - an all-TOADM ring with optical pass through at
all nodes 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, 2 possible solutions are possible:
— (1) At least one TOADM node in the ring must have no optical pass
through connection and no physical fiber present between the sCMD
upgrade ports. This forms an optical seam and prevents the ASE
lasing condition. The two DOC instances for the all-TOADM ring are
provisioned at this TOADM node.
— (2) At least one TOADM node in the ring must instead be a ROADM
node. The ROADM node filters out the ASE and prevents the ASE
lasing condition.
• SCMD4s must be in the same OTS as the LIM or ESAM/MLAx and all the
equipment forming the OTS must reside in the same shelf. The line-facing
OTSs at a Thin OADM can be in different shelves.
• Software supports up to a maximum of 9 cascaded SCMD4s but the
number may be limited by link engineering. Also, beyond a certain amount
of groups a ROADM solution (2x1 WSS and CMD44) may be financially
and operationally preferable.
— The SCMD4s used in the cascade are provisioned in the Configuration
-> Photonic Services -> OTS Management application.
— The SCMD4 cascade order must be user-provisioned via the
Configuration -> Photonic Services -> SCMD Cascade Order
application.
— No CMD44 is allowed in the cascade.
— Only 1 instance of each SCMD4 type is supported in an OTS
— The cascade can be in any group order and fibering must match the
provisioned cascade order
• Capacity upgrade with addition of new groups/SCMD4s at a Thin Terminal
can be done In-Service using the upgrade ports.
• Capacity upgrade with addition of new groups/SCMD4s at a Thin OADM
impacts express traffic as upgrade ports need to be rerouted.
• At a Thin OADM site, channel stitching via channel drop/add ports is not
supported but is hardware-ready to support.
• A Thin OADM with no equipped/provisioned SCMD4s initially is
supported.

— This is like a Line Amp node but provisioned as a Channel access

node; ready for an OOS upgrade to an OADM node in the future
• Asymmetric Thin OADMs, where one OTS is equipped with SCMD4(s)
and the other OTS is not equipped with SCMD4(s) are also supported.
— This results in SCMD4 upgrade ports being connected to the opposite
side’s LIM/AMP.
• Note that every Optical Section in a Photonic Domain must have at least
one active circuit pack (ESAM/SLA/MLA/MLA2/MLA3/SCMD4), and
hence you cannot deploy a TOADM Optical Section with LIMs and no
SCMD4s on either end. The same applies when interworking with 6500
and CPL TOADM sites.
• The VOA PM baselines at the SCMD4 input ports and common output port
are not reset automatically by DOC during a channel delete action, when
deleting the last DOC managed channel traversing these ports. As a
result, you may be left with a standing VOA “Gauge TCA Summary” alarm
after a channel deletion which can only be cleared by manually resetting
the PM baseline using the Site Manager PM application.
• This configuration can only operate in fixed grid mode.
• This configuration cannot be used with L0 CP/SNC provisioning.
6500 TID Consolidation

Overview
Any shelf or all shelves at a node containing Photonic OTS equipment that is
interconnected must be TID-consolidated. TID consolidation allows multiple
shelves at a node to be managed under the same TID, hence reducing the
number of TIDs and nodes requiring management in the network.
Attention: Node refers to co-located shelves that can be daisy-chained via

ILAN ports.
Each shelf shares the same TID, same site ID but has a unique shelf number.
The shelf number is provisioned at commissioning time and is contained in the
AIDs for each shelf. As a result, both TID and shelf are required to target a
shelf of the consolidated group of shelves.
A single shelf, referred to as “primary shelf”, represents the group of

consolidated NEs. The primary shelf is responsible for acting as the recipient
of all TL1 messages in and out of the consolidated group of shelves. The
primary shelf maintains synchronization of all its members for functions such
as time synchronization, new or missing shelves, and security. See figure
below for an example.

For Consolidation node engineering guidelines, refer to Technical Publication

323-1851-301, Administration and Security.
For the OneControl PWSM tool to function, it requires that all channel access
nodes be TIDc (ROADM/TOADM/GOADMs).
Figure 4-71
TID consolidation
Only one TL1 connection required to the site

TL1 session - Telnet, Craft or OMEA
- Connect to 47.134.16.101
- Authenticate the session
- You now have access to both shelves via this one session
by 2 ways:
- specifically targeting a shelf via its AID or
- addressing all shelves in the TID via broadcasting
The Primary shelf and Member shelves
share information internally via the ILAN
ILAN connection.
TID: NEWYORK 6500 NE 6500 NE TID: NEWYORK
SHELF: 1 SHELF: 2
TID-C: Enable TID-C: Enable
Primary: Enable Primary: Disable
IP: 47.134.16.101 IP: 47.134.16.102
Note: Direct login access to a member shelf is supported using challenge-response
It is recommended that all new 6500 Photonic greenfield deployments use TID
consolidation even if the node contains only one shelf (which then must be the
Primary shelf: do not set this lone shelf as a member shelf with TIDc = enable).
Some applications such as the Photonic Connections application (also known
as Optical Bandwidth Management application; OBM) only run on the primary
shelf of a consolidated TID. A valid configuration to enable OBM for a
single-shelf TID is to enable TIDC and designate the single shelf as a primary.
The Site Manager Photonic Connections application is the application that

allows Photonic cross connections to be created between
• LIMs of different ROADM OTSs belonging to different Photonic domains,
which is required for optical branching;
• the LIM of a backbone ROADM OTS with a CMD44 Channel Port of a DIA
OTS if the shelves containing the OTSs are TID-consolidated;
• the LIM of a backbone ROADM OTS with a CCMD12 Channel Port of a
COADM OTS if the shelves are TID-consolidated.

In the case of TOADM facing nodes, OBM automatically derives photonic

connections for pass through connections and for local add/drop channels
provisioned on SCMD4 circuit packs if the shelves are TID-consolidated.
Backbone ROADM OTSs containing SRA, ESAM or SAM can be branched

with other backbone ROADM OTS or DIA OTSs using LIM hardware as part
of the same TIDc node.
• For backbone ROADM OTSs using SRA, ESAM or SAM hardware,
Photonic connection end-points use the SRA/ESAM/SAM line facing
ports:
— between DOC domains (backbone ROADM OTSs)
— between the DIA OTS and SRA/ESAM/SAM based ROADM OTS
• The addition of a member shelf ROADM configuration can be TID
consolidated with existing ROADM configurations and branch traffic
between them.
Even when greenfield deployments do not use optical branching and Photonic
connection provisioning between LIMs belonging to different Photonic
domains, it is recommended that 6500 Photonic greenfield deployments of
WSS-based terminals, RLA-based terminals or SCMD4 based
Thin-Terminals have TID Consolidation enabled. For WSS-based terminals or
RLA-based terminals, this facilitates reconfigurations when optical branching
is required in the future.
Shelf ID and Site ID Numbering

Rules for Site ID and shelf ID numbering within a Site must be met when
deploying photonic OTS equipment and service interfaces. For photonic
network designs, as per One Planner guidance, the Site ID must be unique
across the network, meaning different sites need to use unique Site IDs.
• SPLI specific rules governing how an SPLI match can occur between
photonic layer and service layer equipment within a site are listed in “SPLI
data communications” on page 1-58.
• For photonic shelves, their Shelf IDs are required to be unique in a site.
— For OTSs provisioned on a shelf with the transponders, this is
considered a photonic shelf.
• Transponder shelves can have the same shelf ID as long as their TIDs are
different.
• SPLI considers TID-sh which maps to a unique IP address in the SPLI
table, so as long as the transponder and photonic shelves are in different
TIDs, having the same Shelf IDs is not a problem within a site.

In other words:
• Two shelves connected by ILAN with the same Shelf ID and Site ID but
different TIDs are allowed, but the shelves need to be a transponder shelf
(no OTS) and Photonic shelf (OTS provisioned) respectively
• If two photonic shelves are connected by ILAN (both have OTS
provisioned on them), then the Site ID can be the same but the Shelf ID
needs to be unique. The TID name can either be the same (e.g. for
branching this is required) or not (in this latter case there can be no
photonic link between the shelves). If this rule it not followed a ‘Duplicate
Site ID’ alarm will be raised.
Branching engineering rules

The rules listed in this section are not applicable when using single section
Photonic domain segmentation since all ROADM to ROADM segments are
domains (see “Photonic domain segmentation” on page 4-43).
• All network elements that participate in the branch must first be in a
consolidated TID (see “6500 TID Consolidation” on page 4-141).
• Branching requires one WSS per fiber span addressed (spurs not
supported).
• The same OSID can be present in at most two of the branches. This rule
defines where domains need to be segmented. Figure 4-72 on page 4-146
shows examples of configurations that are not supported because of this
rule.
• Two OSIDs cannot meet (touch or cross) more than twice. If two OSIDs
meet twice, then at least one of those OSIDs must terminate at both
meeting points. Figure 4-73 on page 4-147 shows examples of
configurations that are supported and are not supported because of this
rule.
• A single channel cannot enter or leave the same OSID twice or more.
Specifically the same channel cannot appear within the same DOC
domain more than once unless it originates and terminates in that domain.
Figure 4-74 on page 4-148 shows examples of configurations that are
supported and are not supported because of this rule.
• Branching is available with any supported network topology (for example,
connecting a point to point to a mesh ring, a hubbed ring to a linear OADM
network, or two rings together).
• Adding branching capability or adding a branching dimension can be done
in service without any traffic interruption. A wavelength can be switched
from passthrough to branched or to add/drop without any traffic impact on
other channels.
• Branching can be done on a per channel basis.
• Every branch node provides up to 100% add/drop capability.

• OnePlanner does not allow the unsupported n-way branching

configurations.

Figure 4-72
Branching rules - OSIDs can only be present once or twice at a node

Figure 4-73
Branching rules - If two OSIDs meet twice, at least one of those OSIDs must terminate at both
meeting points

Figure 4-74
Branching rules - a single channel cannot enter or leave the same OSID twice or more

Engineering rules related to Mode 1 capacity change mode

The following rules apply to Mode 1:
• Mode 1 is supported on any 6500 shelf that supports Rel. 12.4 software
or higher. This includes S/D-Series and T-Series shelf types.
• Mode 1 activates by default on a domain provided the following conditions
are met:
— The domain has a single section, with ROADM OTSs as head-end and
tail-end OTSs (no TOADM allowed).
– 6500 and/or CPL line amps are allowed in the section.
— The nodes in the entire domain run Rel. 12.4 or higher.
• If not met (e.g. multi-section domain, presence of TOADM, etc.), DOC
performs channel capacity changes as in releases prior to Rel. 12.4.


Photonic Set-Up Guidelines 5-
This chapter identifies the tasks required to setup an optical system and to
add channels. It also includes tasks for channel capacity changes (i.e. channel
adds and channel deletes).
Table 5-1
Topic
“Greenfield deployment” on page 5-2
— “Commissioning a 6500 shelf equipped with photonic hardware” on page 5-2
— “OTS provisioning model” on page 5-4
— “Provisioning a Photonic node” on page 5-9
— “Provisioning EDFA parameters, Differential Provisioning and Enabling of alarms” on page 5-19
— “Provisioning a T-Series Photonic node” on page 5-21
— “Photonic Site SLAT” on page 5-22
— “Photonic Network SLAT” on page 5-23
— “Wavelength provisioning” on page 5-36
— “Wavelength provisioning not using L0 Control Plane” on page 5-38
— “Wavelength provisioning using L0 Provisioning Control Plane type” on page 5-39
— “Wavelength deprovisioning using L0 Provisioning Control Plane type” on page 5-40
“Modifying an existing Photonic network” on page 5-40
— “Reprovisioning amplifier parameters on an in-service system” on page 5-41
— “Adding wavelengths to an in-service Photonic system” on page 5-42
— “Deleting wavelengths from an in-service Photonic system” on page 5-42
— “Re-routing wavelengths on an in-service Photonic system” on page 5-43
— “Adding a photonic domain to an existing Photonic system” on page 5-43
— “Adding a photonic domain to an existing T-Series Photonic system” on page 5-47
— “Adding a CCMD16x12 or an AMP4 to an existing node” on page 5-48
— “Reconfiguring a ROADM node to include a LIM in the mux/demux path” on page 5-49

5-2 Photonic Set-Up Guidelines
Greenfield deployment
The following gives a high level view of the tasks to be performed in a 6500
Photonics greenfield deployment scenario. References to relevant Technical
Publication sections providing detailed, step-by-step procedures are also
included.
Commissioning a 6500 shelf equipped with photonic hardware

The process for commissioning a 6500 shelf containing photonic (L0)
hardware versus that of broadband or switched-service (L1, L2) hardware is
very similar.
Commissioning sheet and use of NSAT

The Nodal SLAT Assistant Tool (NSAT) or Node Setup application is used to
commission a node which represents an individual physical shelf (2-slot,
7-slot, 14-slot or 32-slot) or multiple shelves (which are TID consolidated).
Each shelf must be commissioned separately. Prior to using the
commissioning tools, the user first types the default craft LAN port IP address
(10.0.0.1) in a browser URL of a PC connected directly to the LAN-15 port on
the CTM, Shelf Processor, SPAP or SPAP-2 w/2xOSC 2xSFP circuit packs
using an Ethernet straight cable. Establishing a connection to the 10.0.0.1 IP
address yields a hyperlink to the commissioning tool, which can be accessed
using default authentication user ID and password.
Based on guidance from the Engineering Documentation Package (EDP), the

user provisions important commissioning information, including the TID, shelf
number, Site ID, and IP data communication parameters for various ports (e.g.
COLAN, ILAN and logical SHELF IP address information). This is necessary
to establish remote-access over the LAN or WAN using TCP/IP routing
infrastructure.
You must refer to procedures in Technical Publication 323-1851-221,

Commissioning and Testing for details on commissioning a 6500 shelf
equipped with Photonic equipment.
For T-Series, you must refer to procedures in Technical Publication

323-1851-103, 6500-T12 Packet-Optical Shelf - Guide for details on
commissioning a 6500 shelf equipped with Photonic equipment.
Auto-provisioning of Photonic equipment

Auto-provisioning is supported on various circuit packs and passive modules
if the shelf Auto Equip parameter is set to Enable for the associated shelf slot.
• 6500 circuit packs are auto-provisioned after insertion in a 6500 shelf.
• 6500 passive equipment (e.g., CMD44, CMD96, CMD64, BMD2, FIM,
OMD4, and DSCMs) are auto-provisioned through connection to an
available external slot on a 6500 shelf Access Panel.

Note that the NTK555NA/NB SPAP-2 w/ 2xOSC 2xSFP circuit pack is used
within the NTK503KA 7-slot type 2 or NTK503LA 2-slot type 2 shelf.
For auto-provisioning of External Slots to occur, the shelf must be equipped

with an Access Panel with connections for external slots.
— For 2-slot shelves
– The 2-slot type 2 shelf (NTK503LA) can be equipped with the
NTK555LA SPAP circuit pack for 3 external slots (83-85) or
NTK555NA/NB SPAP-2 w/ 2xOSC 2xSFP circuit pack for 8
external slots (83-90).
– The 2-slot shelf (NTK503MA DC -variant/ NTK503NA AC-variant)
is integrated with the SPAP + OTN Flex MOTR 8xSFP or
NTK555LA SPAP circuit pack. Connections for 3 external slots
(25-27) are possible.
— For 7-slot shelves
– The 7-slot shelf (NTK503PA) needs to be equipped with the
Access Panel (NTK505PAE5) with connections for 4 external slots
(Slot 83-86) and a Shelf Processor (NTK555CA/EA/FA) that
supports interfacing with external slots.
– The 7-slot optical type 2 shelf (NTK503KA) needs to be equipped
with the NTK555NA/NB SPAP-2 w/ 2xOSC 2xSFP circuit pack.
Connections for 8 external slots (83-90) are possible.
— For a 14-slot shelf, the shelf needs to be equipped with the Access
Panel (NTK505MBE5) with connections for 8 external slots (83-90)
and a Shelf Processor (NTK555CA/EA/FA) that supports interfacing
with external slots.
– In the NTK503SA 6500 Packet-Optical shelf, use of SP2
(NTK555CA/EA/FA) is mandatory.
— For a 32-slot shelf, the shelf needs to be equipped with the Access
Panel (NTK605MAE5) with connections for 12 External Slots (Slot
51-62) and a Shelf Processor (NTK555EA/FA) that supports
interfacing with external slots.
Manual provisioning of passive modules

Manual provisioning of passive modules is supported as follows:
• 6500 passive equipment (e.g., CMD44, CMD64, CMD96, FIM, BMD-2,
OMD4, and DSCMs) can be provisioned using an available virtual slot
Available virtual slots on shelf types

The following virtual slots are available on a per-shelf type basis:
• In a 2-slot shelf:

— For optical type 2 shelves (using NTK555LA SPAP or NTK555NA/NB

SPAP-2 with 2xOSC 2xSFP circuit pack) virtual slots 91-99.
— For 2-slot shelves (NTK503MA/NA) using integrated SP + OTN Flex
MOTR 8xSFP, virtual slots 29-32.
• In a 7-slot (NTK503PA) and 7-slot type 2 (NTK503KA) shelves, virtual
slots 91-99.
• In a 14-slot shelf, virtual slots 91-99.
• In a 32-slot shelf, virtual slots 63-82.
• In a T-12 or T-24 shelf, there is no virtual slot support.
For passive Photonic layer deployments, while manual provisioning of passive

modules is supported using external slots, the preference is to use virtual slots
where available, to avoid exhausting external slots. Note that a “Circuit Pack
Missing” alarm is raised if manual pre-provisioning is performed in an external
slot or 174-0040-900 PPC6 sub-slot, until the equipment is inserted.
TID Consolidation recommendation for greenfield deployments

As discussed in “6500 TID Consolidation” on page 4-141, it is recommended
that all new 6500 Photonic greenfield deployments use TID consolidation
even if the node contains only one shelf.
OTS provisioning model

The OTS provisioning process involves OTS creation from a list of templates,
then defining circuit pack and module interconnections via a process called
slot sequencing. All this is performed via the Site Manager Photonic
Configuration Management application.
Attention: As of Rel. 12.1, the OTS Management application is no longer

available. Existing OTSs created using this application, for which the Slot
Configuration Mode is ‘Provisioned’, are auto-converted to ‘Derived’ mode
(slot sequencing method) after an upgrade to Rel. 12.1 or higher. Editing an
OTS (to add/remove equipment) or creating a new one must be performed
with the Photonic Configuration Management application.
OTS slot sequencing provisioning

OTS slot sequencing defines the interconnections within an OTS. Other
interconnections are managed in the following manner:
• Inter-OTS connections are defined by manually provisioning Far End
Addresses between circuit packs belonging to neighbor OTSs. This is the
case for instance for ROADM to DIA, ROADM to COADM and DIA to
COADM adjacencies.

— An exception is the ROADM to ROADM case, which can be done via

slot sequencing or manually.
• Connections between an OTS and non-OTS equipment within the TIDc
node (e.g. from a ROADM OTS to a FIM) are defined via TID sequencing.
In Technical Publications 323-1851-310, Configuration - Provisioning and

Operating, Part 2 of 2, you can find a table listing the OTS basic parameters,
as well as the procedures related to OTS provisioning. Table 5-2 and Table 5-3
provide information about existing OTS template families and basic OTS
parameters applicable to each.
Table 5-2
OTS Template Families
Template Family Configuration Subtype
ROADM Channel Access ROADM
DIAODM Channel Access DIAODM
COADM Channel Access COADM
TOADM Channel Access TOADM
Line Amplifier Amplifier AMP
Table 5-3
Basic OTS Parameters per Template Family
OTS Parameter Template Family
ROADM TOADM DIOADM COADM Line

Amplifier
OTS Optical   N/A N/A 

system identifier
OTS Tx Path     
Identifier
Rx Label     
Tx Label     
OSC (optional)   N/A N/A 
DOC Site   N/A N/A N/A
Associated OTS   N/A N/A N/A
Provisioned  N/A N/A N/A N/A

Control Mode

Table 5-3
Basic OTS Parameters per Template Family
OTS Parameter Template Family
ROADM TOADM DIOADM COADM Line

Amplifier
Autoroute     N/A
CPS  N/A N/A N/A N/A
Sequence CHC  N/A N/A N/A N/A

Updates
Guardband Width  N/A N/A N/A N/A
Automatic  N/A N/A N/A N/A

Guardband
OSC Required     
OSC OLF Only   N/A N/A 
Amplifier Mate OTS N/A N/A N/A N/A 
Coherent Select N/A  N/A N/A 
Site
Slot sequence concept illustration

The concept of slot sequencing is based on the generic model illustrated in
Figure 5-1 on page 5-8 and is applicable to the ROADM Template Family
(Channel Access Configuration, ROADM OTS Subtype).
Two categories of slot sequences are supported, the Main sequence and the
branch sequences:
• Main sequence: equipment is placed on the main sequence if it cannot be
disconnected without breaking the optical line.
— The main sequence of a ROADM OTS necessarily includes the line
facing amplifier and the WSS/RLA or just the RLA, and can include
other components such as DSCMs or pads, SRA circuit packs, etc.
— The main sequence instance is auto-created upon OTS creation
• Branch sequences: branch sequences are sequences of equipment
hanging off a circuit pack or module assuming a signal-splitting function,
like a WSS, BS5 or BMD2. They further divide in three types, Switch,
Group and Demux:
— Switch: these sequences hang off WSS/RLA Switch ports. Each
Switch sequence has an anchor on the Main sequence (slot/port)

— Group: these sequences hang off BS5 Group A, B, C, D, E ports. Each

Group sequence has an anchor on a Switch Sequence
(slot/subslot/port)
— Demux: Each Demux Sequence has an anchor on the Switch
sequence (from the BMD2) (slot/port)
The Switch and Group sequence instances are also auto-created with
empty sequences. Similar to the Main sequence, equipment positions are
defined by editing each instance.
For either the main or the branch sequences, including the branch types, two
directions are defined:
• “ADD sequence”
• “DROP sequence”
For both the ADD and DROP sequences, the user must specify the order of
circuit pack and module connections by editing them. Each is identified by a
slot number and possibly a sub slot number to guide in the task of creating the
ADD sequence and DROP sequence indexes.
Note that when using Site Manager, bidirectional building blocks (e.g. Channel
Mux/Demux, Band splitters, OSC filter) only need to be filled in the Add or
Drop sequence, and the other sequence (Add or Drop) is automatically
populated. Unidirectional equipment (e.g. DSCM) are filled for each direction
independently.

Figure 5-1
Topology slot sequence model for ROADM OTS subtype

Provisioning a Photonic node

After the shelves at the Photonic node have been commissioned and all
necessary Photonic equipment has been provisioned, the following
provisioning steps are required when setting up a 6500 Photonic shelf:
• Each OTS in the node is provisioned using the Site Manager Photonic
Configuration Management application (see “OTS provisioning model”
on page 5-4).
• Pad and DSCM provisioning (see “Channel pad and intra-OTS pad” on
page 5-10).
• Provisioning Extra Loss in ROADM OTS (see “Provisioning Extra Loss in
ROADM OTS” on page 5-13).
• If DIA OTS, provision a pad for a DIA OTS (see “Provisioning a pad for a
DIA OTS” on page 5-16).
• If Drop LIM configuration, provision a pad for a Drop LIM (see
“Provisioning a pad for a Drop LIM” on page 5-16).
• If pad used on OSC Tx, provision a pad at an OSC Tx (see “Provisioning
a pad at an OSC Tx” on page 5-16).
• Provision non-derived adjacencies (see “Provisioning non-derived
adjacencies” on page 5-17).
• Provision amplifier parameters, Differential Provisioning and enable
Photonic layer alarms (see “Provisioning EDFA parameters, Differential
Provisioning and Enabling of alarms” on page 5-19).
Provisioning Optical Transport Section (OTS) (Basic OTS parameters, Slot

sequence)
Within the Site Manager Configuration->Photonic Services->Photonic
Configuration Management application select the OTS Sequence Tab and
provision the basic OTS parameters after pressing the “Create OTS” button.
Applicability of the various parameters according to template family is given in
Table 5-3 on page 5-5.
Then select the Slot Sequences tab in the lower pane and provision the slot
sequence.
For the CDC configuration:

• Select the TID Sequence tab in the upper pane and provision the
intersecting slot sequence against the appropriate Sequence Identifier to
link the backbone ROADM OTSs to the FIM.
• Edit the Sequence Identifier to link the CCMD8x16s to the FIM.

For the CDA configuration:

link the backbone ROADM OTSs to the FIM Type 4.
• Edit the Sequence Identifier to link the CCMD12s to the FIM Type 4.
For the Low channel count Colorless Directionless OADM:

link the backbone ROADM OTSs to the WSS in the add/drop bank.
• Edit the Sequence Identifier to link the CCMD12s to the WSS in the
add/drop bank.
For the DSCM equipment type, the table below indicates the physical and
virtual slots available for DSCM provisioning, virtual slots for pad provisioning,
and the Shelf Processor and Access Panel PECs required for DSCM
auto-provisioning.
Channel pad and intra-OTS pad

Pad placement at a given circuit pack or module port that is part of an OTS is
obtained from the OnePlanner report.
A distinction is made between channel padding (using the ‘Pad Loss’

parameter) and other extra losses in the channel path between the subtending
line interface and filter channel ports (e.g. patch panel losses) provisioned
with the ‘Excess Loss’ parameter:
• ADJ-FIBER TX:
— Use Pad Loss for pad placed at CMD channel port input. These are for
equalization purposes.
— Use Excess Loss when attenuation is due to patch panel at CMD
channel port input.
— Either pad loss or excess loss is included in the DOC calculations.
• ADJ-FIBER RX:
— On a filter channel output port, ‘Pad Loss’ is assumed to be there to
indicate a pad placed to prevent overload at the Rx, and therefore the
pad loss is not considered in the DOC calculation.
Attention: For pad used to prevent Rx overload, do not set as “Excess loss”
since this would potentially cause a Drop LIM gain increase. When set as
“Pad Loss”, DOC does not take it into account and thus won’t increase the
Drop LIM gain.

— On a filter channel output port, Excess Loss is considered by DOC. It

is used to indicate that there is additional loss (e.g. patch panel) in the
path towards the Rx, and therefore the gain is increased.
Pads within a slot sequence are provisioned in a virtual slot as the DSCM
equipment type using the NPADxxDB PEC, where xx represents a loss value
in dB between 01 and 17 (see Table 5-4 for possible slots).
• you can provision a DSCM anywhere in the drop sequence, including after
the DROP LIM. These DSCMs are taken into account by DOC. So if you
provision the pad as a DSCM Type NPADxxDB, the gain of the drop amp
would be increased to overcome the extra loss.
• Provisioning the pad as DSCM (NPADxxDB) allows it to be viewed in
Visualization.
In Metro ROADM configurations, due to the variability in channel losses

because of the filter structures, attenuator pads may be necessary:
• Between the transponder Tx and the WSS switch input port, to save
dynamic range in the WSS.
• At the transponder Rx, to prevent overload.
• The “Pad Loss” parameter in the ADJ-FIBER-TX facility is used to
provision the deployed channel pad value.
• Note that the “Excess Loss” parameter in the ADJ-FIBER-TX or
ADJ-FIBER-RX facility is used for patch panel losses.
DSCM provisioning
DSCM placement at a given circuit pack or module port that is part of an OTS
is obtained from the OnePlanner report.
6500 DSCM equipment can be connected to an external slot for

auto-provisioning, or 6500/4200/2110 DSCM equipment is manually added
using a shelf virtual slot. DSCM PECs include the following families:
• NTT870yz Type1/2/3/5 C-Band
• 166-0203-09xx Type 1 C-Band
• 166-0403-09xx Type 5 C-Band
• B955-0003-0xx Type 1 C-Band
• B955-0003-3xx Type 5 C-Band
You can provision a DSCM anywhere in the drop sequence, including after the
DROP LIM. These DSCMs are taken into account by DOC and are shown in
visualization. In summary, DSCMs are allowed in the following slot
sequences:
• main
• branch

— switch type (any position)

— group type (any position)
The flexibility of DSCM placement within slot sequences allows applications

where certain channel types can be compensated without affecting other
channels types that do not require compensation. For example: 10G DWDM
XFP channels can be compensated without impacting 40G OCLD channels (if
10G DWDM XFP channels are connected to separate filters).
Note that in Cascaded LIM (interior SLA) or Drop LIM configurations, the
DSCM is provisioned only in the DROP direction of a slot sequence. The ADD
direction entry for the same row in the slot sequence provisioning dialog is left
empty otherwise the validity flag is raised.
Attention: Provisioning a DSCM directly after a Drop LIM may result in

significant link engineering penalties and is not recommended.
Table 5-4
Supported DSCM or pad slots when provisioned as DSCM equipment type
Shelf type Shelf Processor/Access DSCM slot range Pad virtual slot
Panel PECs range
Physical (auto Virtual (manually
provisioned) (manually provisioned)
provisioned)
2-slot PEC N/A since non-FRU: 25-27 29-32 29-32

NTK503MA/NA integrated SP + OTN Flex
MOTR 8xSFP
2-slot type 2 NTK555LA SPAP 83-85 91-99 91-99

NTK503LA
2-slot type 2 NTK555NA/NB SPAP-2 w/ 83-90 91-99 91-99

NTK503LA 2xOSC 2xSFP
7-slot SP: AP: 83-86 91-99 91-99

NTK503PA NTK555AB/ NTK505PA
CA/EA/FA
6500-7 SP: AP: 83-86 91-99 91-99

packet-optical NTK555CA/ NTK505JA
shelf EA/FA
NTK503RA

Table 5-4
Supported DSCM or pad slots when provisioned as DSCM equipment type
Shelf type Shelf Processor/Access DSCM slot range Pad virtual slot
Panel PECs range
Physical (auto Virtual (manually
provisioned) (manually provisioned)
provisioned)
7-slot type 2 NTK555NA/NB SPAP-2 w/ 83-90 91-99 91-99

NTK503KA 2xOSC 2xSFP
14-slot NTK555AB/ NTK505MB 83-90 91-99 91-99

CA/EA/FA
32-slot NTK555FA NTK605MA 51-62 63-82 63-82
Provisioning Extra Loss in ROADM OTS

Extra loss between the WSS/RLA switch port and the CMD44 common port
can be a function of:
• Intra-OTS padding
• Patch panel losses
• Extra fiber distance (e.g. remote CMD44 application)
For the example in the figure below, assume

• A 50 GHz WSS with CMD44 red / CMD44 blue and BMD2 in a remote
CMD44 application
• 1 dB of patch panel losses exists between a transponder and CMD44
channel port
• A 2 dB remote distance loss between the CMD44 50 GHz modules and
the BMD2
• 1 dB of patch panel loss between the remote and near-end node
• In the above scenario, it is required to provision 4 dB of “Excess Loss”
against the individual channel input and channel output ports used on the
CMD44s.

Figure 5-2
Provisioning of Extra Loss in ROADM OTS between WSS and Filter Common port
For the example in the figure below, assume

• A 100 GHz WSS with BS5 and Drop LIM
• 1 dB (0.5 dB + 0.5 dB) of patch panel losses exists between the Drop LIM
and BS5 NTWK port

• A 3 dB pad at the output of the Drop LIM is used to prevent a standard

APR condition when channel filter ports are unterminated. Note that an
APR condition due to mis-fibering can only be prevented if the eCMD44
100 GHz (NTT862FA) is used with the DROP LIM, due to the presence of
an isolator on the CMD44 common input port.
• 1 dB of padding at Tx/Rx interfaces in use at the OMDF8 channel ports
In the above scenario, it is required to provision (0.5+0.5+3) = 4 dB of “Excess

Loss”, and 1 dB of “Pad Loss” against the individual channel input and channel
output ports used on the OMDF8s.
Figure 5-3
Provisioning of Extra Loss in Metro ROADM OTS between WSS and Filter Common Port

The “System Configuration Loss” parameter in the CMD ADJ-FIBER facility is

available for when an OPS is between the CMD and the transponder. DOC
accounts for this loss in the same way that “Excess Loss” is used.
Note that if SPLI is not available, since the “System Configuration Loss”
parameter is not editable, it is necessary to use “Excess Loss” on
ADJ-FIBER-TX and RX.
Provisioning a pad for a DIA OTS

Provisioning of a pad in a DIA OTS is covered below:
• For 100GHz DIA OTS, if a pad is required/installed between the DIA
CMD44 Common Out port (port 90) and the DIA amplifier Line A input
(port 8) (determined by OnePlanner), provision the pad value as Excess
Loss using the Site Manager Configuration->Equipment & Facility
Provisioning application against the CMD44 Common Out port (port 90)
ADJ-FIBER facility.
• For 50GHz DIA OTS, if a pad is required/installed between the DIA BMD2
Common Out port (port 2) and the DIA amplifier Line A input (port 8)
(determined by OnePlanner), provision the pad value as Excess Loss
using the Site Manager Configuration->Equipment & Facility Provisioning
application against the BMD2 Common Out port (port 2) ADJ-FIBER
facility.
• For 50GHz DIA OTS using the 50GHz 9x1 WSS circuit pack, when
backbone WSS switch ports 8 or 9 are used for interconnection to a DIA
OTS WSS, if a pad is required/installed at the DIA OTS WSS switch port
8/9 Input and Output ports (determined by OnePlanner), provision the pad
value as Excess Loss using the Site Manager Configuration->Equipment
& Facility Provisioning application against:
— The DIA OTS WSS switch port 8/9 Output port (port 18/20)
ADJ-FIBER facility
— Each backbone WSS switch port 8/9 Output port (port 18/20)
ADJ-FIBER facility
Provisioning a pad for a Drop LIM

If a pad is installed between the WSS Switch Out port and the DROP LIM port
8, the pad is provisioned as excess loss on the WSS Switch Out port
ADJ-FIBER facility.
Provisioning a pad at an OSC Tx

If a pad is required to reduce the OSC Tx launch power into the fiber plant, so
as to mitigate non-linearities, the pad must be provisioned using the Excess
Loss parameter on the ADJ-FIBER facility for the OSC Tx (P155M) equipment
facing the span. Note that a pad provisioned as excess loss against the OSC
Tx equipment is excluded from the OSC span loss reading.

If the OSC is located on the SRA/ESAM/SAM then the Excess Loss needs to
be provisioned on the ADJ-FIBER facility of the OSC (SH-SL-2).
Provisioning non-derived adjacencies

After completion of DSCMs or pad provisioning within the OTS, other specific
topology information may need to be provisioned manually. This includes:
• Non-derived intra-OTS adjacencies
• Inter-OTS adjacencies
Use this procedure to manually provision adjacencies that are not system
derived following OTS creation.
The list of such adjacencies includes:

• Inter-OTS adjacencies
— Connections between ROADM OTSs
– Does not apply when using FIMs to interconnect ROADM OTSs for
a CDA or CDC using TID sequence format to provision.
pre-defined port assignments.
– When using the CDA in a modular manner which is more flexible
(and can provide up to 15 degrees) then all WSS-FIM Type 4-5-6
will have to be done manually.
— WSS-WSS or RLA-RLA adjacencies between ROADM OTSs and
Connections between TOADM OTSs
– CMD-CMD adjacencies within a TOADM node (between 2 OTSs)
– CMD to LIM and LIM to CMD adjacencies within a TOADM node
(between 2 OTSs)
— Connections between ROADM OTS and DIA OTS for the DIA
configuration
– WSS-WSS adjacencies between a ROADM OTS and DIA OTS
— Connections between ROADM, DIA and COADM OTSs for the
Colorless Directionless configuration
– WSS-WSS adjacencies between a ROADM OTS and DIA OTS
– LIM-SMD adjacency between DIA OTS LIM and COADM OTS
SMD
– SMD-LIM adjacency between COADM OTS SMD and DIA OTS
LIM
— Connections between ROADM and COADM OTSs for the Colorless
Directional node (CDA) with COADM (with LIM) direct attach
configuration

– LIM-WSS adjacency between COADM OTS LIM and ROADM

OTS WSS
– WSS-LIM adjacency between ROADM OTS and COADM OTS
LIM
— Connections between ROADM and COADM OTSs for the Colorless
Directional node (CDA) with COADM (without LIM) direct attach
configuration
– SMD-WSS adjacency between COADM OTS SMD and ROADM
OTS WSS
– WSS-SMD adjacency between ROADM OTS WSS and COADM
OTS SMD
— LIM to LIM connections over a fiber span (known as line adjacency)
— Connections between the CCMD12 the FIM for the CDA is a modular
manner which is more flexible then all CCMD12-FIM Type 4 will have
to be done manually.
• OPM adjacencies when the 2-port OPM NTK553PA/PB circuit pack is
used.
Adjacency provisioning in configurations using the standalone NTK553PA/PB

C-Band 50 GHz 2-port OPM depends on the application. For OPMs
connected to LIMs at Line Amplifier nodes:
• It is possible to provision the LIM monitor port (port 1 or 2) to OPM port
(port 1 or 2) adjacencies manually using the Site Manager
Configuration->Equipment & Facility Provisioning application. The
corresponding adjacency at the OPM port is consequently auto-derived.
• LIM Line B monitor port 1 have their OPM adjacencies automatically
derived as explained in “Intra-OTS and inter-OTS adjacencies at
ESAM/SAM-XLA-XLA-ESAM/SAM Line Amp node without OPM” on page
1-42. These derived OPM adjacency far-end addresses can be manually
edited (overridden) by the user.
• The LIM Line A monitor port 2 OPM adjacencies are manually provisioned
using the Site Manager Configuration->Equipment & Facility Provisioning
application.
For OPMs connected to available LIM monitoring ports at ROADM and

TOADM nodes, in terrestrial applications:
• If the node is a ROADM, adjacencies get derived automatically when the
OTS is built since a WSS contains an OPM. Derived adjacencies need to
be deleted and manually created to point to the standalone OPM circuit
pack.
• The adjacencies have to be created manually to link the OPM to the
monitor ports on LIM circuit packs at TOADM nodes.

• For the configurations of the SRA with XLA and ESAM/SAM with
MLAx/XLA the OPM adjacencies have to be manually created to point to
the XLA.
Adjacency provisioning procedures

For adjacency provisioning, use the ED-ADJ and ED-ADJ-LINE TL1
commands or the Site Manager Equipment & Facility Provisioning application
(accessed via Configuration->Equipment & Facility Provisioning).
Refer to the following procedures for detailed provisioning instructions:

• “Provisioning adjacencies” in Technical Publication 323-1851-221,
Commissioning and Testing
• “Editing facility parameters” in Technical Publication 323-1851-310,
Configuration - Provisioning and Operating
• “SCMD cascading order” in Technical Publication 323-1851-310,
You can also refer to the adjacency provisioning examples in “Provisioning

Examples” on page 6-1
Provisioning EDFA parameters, Differential Provisioning and Enabling of

alarms
The following provisioning items are executed after all OTS topology
(adjacency) information is created:
• Provisioning amplifier parameters
• Differential Provisioning
• Enabling “High Fiber Loss” detection and alarming
• Enabling “High Received Span Loss” detection and alarming
• Enabling “Channel Degrade” alarm on WSS/RLA NMCC facilities
Provisioning amplifier parameters

The “Target Peak Power” and “Target Gain Tilt” parameters need to be
provisioned for each line facing and cascaded (or interior) amplifier in the
ROADM OTS, as per the OnePlanner amplifier report. The XLA amplifier has
extra parameters that need to be provisioned as per the OnePlanner amplifier
report called “Gain Mode” and “TOP Offset”. For a DIA OTS amplifier, the
“Target Gain” parameter must be provisioned as per the OnePlanner amplifier
report. For a Drop LIM, nothing needs to be provisioned, and there is no
recommendation from the OnePlanner amplifier report since the Drop LIM is
DOC controlled.

Attention: For cascaded amplifiers, OPTMON port 4 and OPTMON port 6

must be put in the OOS state. These correspond to Line B ports which are
unused when the SLA is used as a cascaded amplifier.
For provisioning these parameters, use the ED-AMP TL1 command or the Site
Manager Equipment & Facility Provisioning application.
• “Provisioning photonic parameters” in Technical Publication
323-1851-221, Commissioning and Testing
• “Editing facility parameters” in Technical Publication 323-1851-310,
Differential Provisioning
If the OTS is created as a DOC and the EDP/IDP states that Differential
Provisioning must be used, then the modulation class biases need to be
provisioned using the Site Manager Configuration->Photonic
Services->Differential Provisioning application. This step is performed once
during SLAT and done only on the DOC sites. This step can also be performed
when a new modulation class is being added to an existing photonic network.

• “Differential Provisioning” in Technical Publication 323-1851-310,
Configuration - Provisioning and Operating.
Enabling “High Fiber Loss” detection and alarming

The “High Fiber Loss” alarm reporting has to be explicitly enabled for a shelf
by enabling the Site Manager Configuration->Node Information “High Fiber
Loss Detection Alarm” parameter in the System tab. By default, this parameter
is enabled.
• The “High Fiber Loss Detection Alarm” parameter in the Site Manager
Node Information application (System tab) must be set to Enabled for the
shelf containing a COADM OTS.
• If the parameter is left disabled, the “Fiber Loss Detection Disabled” alarm
is raised.
Enabling “High Received Span Loss” detection and alarming

The “High Received Span Loss” alarm reporting has to be explicitly enabled
for a given span by provisioning a non-zero Target Span Loss in the LIM or
SRA/ESAM/SAM ADJ-LINE facility. By default, the Target Span Loss
parameter is set to 0.

High Fiber Loss/High Received Span Loss alarms when using DSCMs/pads
The High Fiber Loss Detection alarm is enabled by default, and covers excess
loss/DSCM equipment provisioned at LIM Line A output (port 7) (refer to “High
Fiber Loss” on page 2-106).
In the case where DSCM or pads are provisioned at the LIM Line B (Booster)
Output (port 5), or LIM Line A (Pre-amp) Input (port 8), since the DSCM/Pad
is in the span, the “High Received Span Loss” alarm applies. The “High
Received Span Loss” alarm uses the LIM ADJ-LINE facility parameters as
described in “High Received Span Loss and Low Received Span Loss” on
page 2-104:
• span loss, which is the OSC span loss reading;
• provisioned non-zero target span loss and
• span loss margin.
OSC Span Loss readings if DSCM or pads are within the span
When provisioning a pad at the output of the booster (Line B Out, port 5) or
pad or DSCM at the input to the preamp (Line A In, port 8), it is incorporated
into the OSC span loss reading. This is indicated in “OSC span loss readings
when pads or DSCMs are in a span” on page 2-105.
Enabling “Channel Degrade” alarm on WSS/RLA NMCC facilities

As described in “Channel Degrade alarm for WSS/RLA NMCC facilities” on
page 2-109, the “Channel Degrade” alarm for WSS/RLA NMCC facilities is
based on calculation, and is raised via the Minor Degrade Threshold:
value - the Minor Degrade Threshold value) then the “Channel Degrade”
alarm is raised.
• The Minor Degrade Threshold setting defaults to 3 dB and can be
Information application and the Systems settings.
Provisioning a T-Series Photonic node

After the shelves at the Photonic node have been commissioned and all
necessary Photonic equipment has been provisioned, the following
provisioning steps are required when setting up a 6500 T-Series Photonic
node (detailed procedures can be found in Technical Publication
323-1851-103, 6500-T12 Packet-Optical Shelf - Guide):
• Provision RLA information
— For each RLA, provision an OSPF circuit against the RLA OSC facility
with Network Area as indicated in the EDP/IDP.
— Provision each RLA module as indicated in the EDP/IDP:

– For the ADJ-LINE Port 5 facility, provision the following

parameters: Fiber Type, Target Span Loss, Expected far end
address format: TID-SH-SL-PRT and Expected far end address
– For the VOA Port 5 facility (Line B), provision the following
parameter: Target Pad, Target Peak Power
– For the AMP Port 5 facility (Line B) provision the following
parameters: Target Peak Power, Target Gain Tilt
– For the AMP Port 8 facility (Line A) provision the following
parameters: Gain Mode, Target Peak Power, Target Gain Tilt, Top
Offset
• Provision the OTS, OTS sequence, and TID sequence
— The Site Manager Photonic Configuration Management application is
used to provision the following basic OTS parameters:
– OTS instance #
– OTS Optical system identifier
– OTS Tx path identifier
– DOC site—set to True
– Autoroute—set to Disable
– CPS—set to Enable
– OSC Required
— The Site Manager Photonic Configuration Management application is
used to identify how all the Photonic equipment is interconnected at
the node.
– Use the OTS Sequence tab within the application to provision the
main equipment in the OTS. The main equipment for 6500 T-Series
is the RLA module.
– Use the TID Sequence tab within the application to provision how
the FIM equipment is connected to the RLA module, the
CCMD16x12 module, the CCMD 8x4 module and the AMP4
pluggable.
– Use the TID Sequence tab within the application to provision how
the OTDR4 module port is connected to the RLA module.
Photonic Site SLAT

Once the Photonic node provisioning has been completed, fibers
interconnecting the Photonic modules within the node can be performed as
per EDP/IDP.
• For detailed procedures, refer to Technical Publication 323-1851-221,
Commissioning and Testing.

• For T-Series detailed procedures, refer to Technical Publication

323-1851-103, 6500-T12 Packet-Optical Shelf - Guide.
Photonic Network SLAT
Network system lineup and testing (SLAT) can only be performed after the
Photonic site testing has been completed for all 6500 sites.
Connecting inter-NE fibers and testing the photonic layer

Once individual photonic sites are tested, they can be connected to one
another.
For connecting inter-NE fibers and testing the photonic layer:

• Refer to the “Connecting inter-NE fibers and testing the photonic layer”
procedure in Technical Publication 323-1851-221, Commissioning and
Testing.
• For T-Series, refer to the “Connecting inter-NE fibers and testing the
photonic layer” procedure in Technical Publication 323-1851-103,
6500-T12 Packet-Optical Shelf - Guide.
Photonic layer testing includes:

• verifying the far-end addresses of line adjacencies
• checking for unexpected alarms
— If Dark Section Conditioning is running, more failures can be exposed
such as intra-site high fiber losses and APR conditions. For the full list,
refer to “Dark Section Conditioning” on page 2-98.
• verifying the span losses
• verifying the OSC BER
• verifying the Optical Return Loss (ORL) on amplifier circuit packs
Fiber plant and connector loss characterization using OTDR

When the inter-NE fibers are connected, OTDR Office, Short and Long traces
are automatically run by the software. A baseline trace is stored automatically
on the network element after the first successful trace.
The traces should be reviewed to verify if they meet your necessary

requirements. If not, actions should be taken to resolve the unacceptable loss
or reflection events and the traces should be re-run manually. Once the trace
is deemed acceptable, it should be baselined. OTDR trace baselines can be
applied to Office, Short and Long traces independently.
For S/D-Series short traces, the “Line A Input OTDR High Loss Detected” or
“Line A Input OTDR High Reflection Detected” alarm can be raised if the
effective loss or reflection thresholds are violated. Prior to Rel. 12.1, the same
alarm is raised even if there are multiple loss/reflection events causing the

failure. As of Rel. 12.1, the alarm is complemented by its associated

“Additional Information” field, which displays the following possible text to help
pinpoint the problem:
• High Loss – Short Trace
• High Reflection – Short Trace
• High Loss – Office Trace
• High Reflection – Office Trace
• Flat Trace – Long Trace
Note that only one of the above defined additional info is displayed. In case of
multiple possible failure messages, the order of precedence is Short trace,
Office trace (if greenfield), and then Long trace:
• Example 1: if the Short trace has a loss issue, then the “OTDR high loss
detected” alarm is raised and the alarm additional info field displays “High
loss - Short trace”.
• Example 2: When flat trace is found, the “OTDR high reflection detected”
alarm is raised and the alarm additional info displays “Flat trace – Long
trace”.
Figure 5-4
OOS OTDR trace example with baseline

Figure 5-5
Short OTDR trace example with Raman On and Raman Off
Figure 5-6
Long OTDR trace example with Raman On and Raman Off

SRA OTDR Go/No-Go criteria and decision process

In releases prior to Rel. 12.1, SRA Short and Long OTDR traces were used
by software to verify if the traces meet the Go/No Go criteria for the Raman
pumps to turn on. As of Rel. 12.1, for greenfield systems, the Office trace is
added so that the Go/No-Go decision is based on 3 traces. The Office trace
focuses on events close to the faceplate that the Short trace could miss. For
brownfield systems, the decision is based on the original 2 traces. Software
tracks which traces are required for Go/No-Go decision. In summary:
• Greenfield: after the 3 traces are run (automatically), software uses results
from all of them to make a decision:
— Office trace results to detect loss/reflection events within the first 2 km
— Short trace results to detect loss/reflection events within the first 20 km
— Long trace results to detect flat trace. Loss and reflection events after
20 km are not considered in the Go/No-Go decision.
• Brownfield: any system upgraded to Rel. 12.6 automatically runs 3 traces,
but only the Short and Long traces results are considered in the Go/No-Go
decision:
— Short trace results to detect loss/reflection events within the first 20 km
— Long trace results to detect flat traces. Loss and reflection events after
20 km are not considered in the Go/No-Go decision.
— The Office trace is not part of this Go/No-Go decision. This is to
prevent traces that previously passed to fail once the system is
upgraded to Rel. 12.6.
The SRA Raman pumps do not turn on if any one of the following conditions
are met after a short (high resolution) OTDR trace is performed (refer also to
the decision tree in Figure 5-7):
• If one reflection event within 20 km of distance has a reflection event
greater than the threshold.
• If the total reflection for 20 km is greater than the threshold (includes
Rayleigh scattering).
• If one of the loss events within 20 km of distance has an effective loss
• If the total accumulated effective loss (excluding fiber loss) for 20 km is
— As of Rel. 12.1, gain events, which can be observed on a mixed fiber
types span at the fiber type change boundary, are included in the total
loss calculation (as negative losses).
The SRA Raman facility provisioning thresholds used for the Go/No-Go
decision process are indicated in Table 3-15 on page 3-143.

Prior to Rel. 12.1, the loss measurements used in the Go/No-Go decision
were compared to the threshold regardless of their location away from the
faceplate, such as (for example) a 2 dB loss at 19 km had the same impact on
the Raman gain compared to a 2 dB loss at 1 km. As of Rel. 12.1, the distance
is taken into account via a weighing method which diminishes the importance
of loss events as distance from the faceplate increases (see example in Table
5-5). This weighed loss is called Effective loss, and is applied to all loss
events. The Total loss criterion in the decision process is likewise defined as
the sum of Effective losses, rather than the sum of the Actual losses. Note that
the OTDR trace result and Site Manager Event log include event actual loss
value (dB) and effective loss value (dB), but in the case of the OTDR trace the
effective loss values are only displayed in the Notes section of the event when
a No-Go decision has been made.
Table 5-5
Effective Loss calculation example
Actual loss Distance Effective loss Pass/Fail at Pass/Fail at

[dB] [km] [dB] Default threshold Max threshold
(0.5 dB) (1.5 dB)
2 0 2 Fail Fail
0.1 1.99 Fail Fail
1 1.87 Fail Fail
5 1.42 Fail Pass (Note 1)
Note 1: If Actual loss was used, this would be a Fail.
Troubleshooting
When a No-Go decision is made, the ‘Notes’ field in the Site Manager ‘Event
Detail’ table indicates what triggered the No-Go decision to help
troubleshooting. The information also appears in the OTDR ‘Graph View’
window, and is stored in the SOR file. Depending on what triggered the No-Go
decision, the field may contain different information, as shown in the figure
below.

Table 5-6
No-Go decision ‘Notes’ field examples
No-Go decision Type ‘Notes’ field information example

triggered by...
Single event Reflection CALC.Refl(dB): -16.62 Single Thres.(dB): -33.00 (Note 1)
Loss CALC.Loss(dB): 7.21 Single Thres.(dB): 0.50 (Note 1)
Cumulative loss or Reflection CALC.Refl(dB):-33.05 Total Thres.(dB): -27.00

reflectance CALC.Refl(dB):-34.15 Total Thres.(dB): -27.00
CALC.Refl(dB):-35.23 Total Thres.(dB): -27.00
CALC.Refl(dB):-34.48 Total Thres.(dB): -27.00
CALC.Refl(dB):-33.06 Total Thres.(dB): -27.00 (Note 2)
Loss CALC.Loss(dB): 0.32 Total Thres.(dB): 1.00

CALC.Loss(dB): 0.27 Total Thres.(dB): 1.00
CALC.Loss(dB): 0.43 Total Thres.(dB): 1.00 (Note 2)
Faceplate event is Event Faceplate EVENT MISSING (Note 3)

missing from Office trace
Long Trace is flat Trace FLAT TRACE (Note 4)
Note 1: Field shows the single event causing the No-Go.

Note 2: Field lists re-evaluated loss/reflectance of all the events which contributed to loss/reflectance
No-Go decision.
Note 3: This event is an artificial event created at faceplate location on the Office trace, to cover the
rare event when the faceplate event can not be detected. For laser safety, a No-Go decision is made.
User is advised to contact Ciena for help. This only applies if the Office Trace is part of the Go/No-Go
decision (i.e., greenfield deployment).
Note 4: In this case an artificial event is created at 120 km. This usually indicates a hardware defect
and user is advised to contact Ciena for help.
For any reflection issue, it is recommended to clean fibers or re-splice the

splices that have not met the specification. It is also recommended to run
another short trace with the pulse duration set to 100 ns or 10 ns and distance
to 8000 m for more precision, especially if patch panels are close together.
Attention: For any loss issues that have not met the specification, then the
Raman Gain may not be achievable, or the optical power may be sufficient
to heat up and damage the fiber.

Figure 5-7
SRA Go/No Go decision tree
Manual Go/No-Go traces

In some cases a fiber pinch fails a Go/No-Go decision. Once the fiber pinch is
cleared, instead of having to re-run individually each of the 3 traces
(greenfield) or 2 traces (brownfield) to get the Go/No-Go decision cleared up,
an option in the OTDR application window allows a bundled launch of all
necessary traces. The option appears in the ‘Trace Type’ pull-down menu as
‘Go/No-Go’. If all events have been cleared up, then the Go decision is given

to turn on the SRA pumps. Note that the option is not available when the
Raman facility associated with the OTDRCFG facility is In-service (Pumps
already ON).
Go/No-Go override
An override TL1 command exists to instruct the SRA to pass the next
Go/No-Go decision regardless of the OTDR trace results. Passing the next
Go/No-Go decision can only be allowed if a Go/No-Go decision has previously
passed. Use of this command should be restricted to cases where traces
originally passed (close to baseline threshold values), but are now failing on a
fiber cut recovery (marginal failure).
Attention: It is not recommended to ignore major losses or reflections as it

may cause risks to the fiber plant, patch panels and equipment.
Note that the command only applies to brownfield deployments (for greenfield,
the Go/No-Go needs to pass as per threshold values provisioned in the
OTDRCFG facility). To ensure the command does not compromise the link
safety:
• It is limited to TL1 only and is password protected. If password is not set,
the override command is rejected.
• Its effect is not permanent, i.e. it needs to be repeated in the future if
another trace fails on the same link.
Single Raman Line Amp (SRA) turn-up procedure

Prior to adding channels, if the NTK552JA Single Raman Line Amp (SRA)
circuit pack is used in a deployment, the SRAs at both ends of a span must be
turned up. The turn-up procedure is described at a high level in the following
steps, with steps 2-5 illustrated in Figure 5-8 on page 5-32.
1 On power up, the circuit pack performs an internal hardware verification
test and then indicates to the Shelf Processor it is ready for provisioning.
2 Once the provisioning is completed, the SRA circuit packs from both sides
start transmitting the telemetry gain (TG) signal.
3 The SRA circuit pack runs a short OTDR trace automatically to verify the
span before deciding to turn on its Raman pumps. For synchronization
purposes, the SRA requests a switch to OTDR mode to the far end.
4 Once acknowledged, both sides turn off the TG signal and run OTDR
traces.
5 Once the OTDR traces are completed, SRAs turn the TG signal back on.
— The SRA circuit packs wait for upstream TG to be received before
moving forward.
— If this was the first successful OTDR trace being run, the trace is set
as the baseline.

— If there are no issues with the trace, then the Raman pumps are in a
position to perform a calibration (power audit) procedure.
6 A calibration (power audit) is done to optimize and flatten the Raman gain
based on the fiber characteristics.
Note that calibration (power audit) is done in one of three scenarios:

— If Dark Section Conditioning is not running, power audit runs
automatically as part of the first channel add operation over a dark
fiber span linked with SRA circuit packs. Pre-requisites to this power
audit are as follows:
– The topology of a channel path that would go through any SRA
circuit pack within the domain must be established. The channel
topology is created using Tx/Rx adjacencies and Photonic
connections, and the channel would appear in the Site Manager
DOC application as “Inactive” (unmanaged). This allows DOC to
establish a port trail from ingress to egress through all intermediate
modules and circuit packs, thereby identifying any SRAs in the
path that would require calibration.
– Each SRA circuit pack has successfully performed its OTDR trace.
– Each SRA RAMAN facility has its calibration flag parameter set to
“Not Calibrated” or “Recalibration Required”.
— If Dark Section Conditioning is running, power audit runs automatically
without waiting on a request for the first channel add. The
pre-requisites are the same as above, except that there is no need for
channel topology information to be present.
— Manually as required, based on user command, within a DOC domain.
When performing a manual power audit, all SRAs within the domain
are calibrated, if their calibration flag is set to either “Not Calibrated” or
“Recalibration Required”. When run over a dark section, a manual
power audit generates a “DOC Power Audit Complete - Pass” log.
Attention: The calibration (power audit) is service affecting. If channels are

present, it does not run.
7 If there are traffic channels, the Raman pumps are turned on. Failure to
meet the target Raman gain is detected by an alarm condition. If there are
no channels, the SRA circuit pack stays in standby mode waiting for the
first channel add.

Figure 5-8
SRA turn-up procedure
For further details on the SRA turn-up, refer to Technical Publication

323-1851-221, Commissioning and Testing.
SRA Power Audit steps

The Raman power audit (calibration) process is run within a DOC domain in
any section containing SRA hardware. As mentioned in “Power Audit
(Calibration) of SRA circuit pack as part of SRA turn-up” on page 2-79, the
power audit can be triggered manually or automatically.
As part of the DOC fault detection routine, software determines whether a

power audit can occur.
• If a power audit cannot be run due to invalid initial state, the power audit
request is failed and a customer visible DOC log is generated. The
following actions can block the power audit:
— Unable to collect topology
— RAMAN or AMP facility primary state is OOS-MA
— OTDR Trace failed on a OTDRCFG facility, and the RAMAN facility is
not ready for calibration
— There is optical line failure in the section (e.g. which causes RAMAN
or AMP facility to shutoff)
— Cannot close WSS/RLA pixel or set XLA/LIM to ASE mode properly
— RAMAN or AMP facility in APR
— SRA card report calibration failed

— SRA card timeout or communication failure on calibration

— Fiber type not provisioned on a RAMAN facility
If a power audit can occur:

1 Software generates an event message indicating the start of the
calibration process. This can be observed in the Historical Event Browser
in Site Manager via the “DOC Power Audit Started” event.
2 The Sectional Optical Controller (SOC) blocks the head-end ROADM
node WSS/RLA pixels (if not blocked already).
3 If Dark Section Conditioning (DSC) is not running, the SOC sets the XLA
Amplifier in Power Mode, producing broadband noise (ASE).
— The XLA amplifier upstream of the SRA is first set to no shutoff (ALSO
disabled = TRUE) mode
— Then the XLA amplifier downstream of the SRA is set to forced shutoff
mode and AMP mode is set to Power (with a Target Power of 20 dBm)
— If the amplifier raises an APR alarm at this point, the SRA circuit pack
is not calibrated.
If DSC is running, the XLA either amplifies ASE coming from the upstream
section head-end amplifier, or, if it acts as the section head-end amplifier,
produces ASE itself to allow the power audit process to occur. Details of
DSC operation can be found under “Dark Section Conditioning detailed
operation and operational considerations” on page 2-101.
For each SRA in the section, the power audit (calibration) process is
performed. It consists in calibrating the RAMAN pumps to achieve the
expected Raman gain for that specific link. When completed:
• If Dark Section Conditioning (DSC) is not running, the XLA AMP facility
parameters are changed back to their original values.
• The “DOC Power Audit Complete - Pass” event log is generated against
the DOC facility at the DOC site. This log is visible in the Site Manager
Historical Fault Browser application. If the power audit fails, the “DOC
Power Audit Complete - Fail” event log is generated and more
troubleshooting information is available in the DOC logs.
Refer to Figure 5-9 on page 5-35 for an illustration of the SRA power audit
process occurring within an example DOC section, in the case where Dark
Section Condition is not running.
The time required to perform the calibration of the SRA circuit pack is typically
on the order of 5 seconds to a maximum of 30 seconds.

If the power audit fails for any reason for a particular SRA, DOC continues to
perform a power audit on any other SRAs in the section, but the overall power
audit is considered failed which would yield the DOC facility “Power Audit
Failed” alarm. Accordingly, DOC fails the channel add action.
The power audit process is only completed once the calibration has been
completed successfully for all SRAs in the section of the domain. Upon
success, the SRA RAMAN facility calibration flag parameter value is set to
“Calibrated” or “Calibration Not Required” for spans greater than 43 dB.
Attention: After a successful calibration, if you provision an operational gain

that’s away from the Raman gain, or perform any edit on the provisioned
gain, there is no guarantee for Raman performance. A similar impact applies
if the fiber type is modified from “Unknown” to a new value on the ADJ-LINE
of the OTDRCFG facility after an SRA has already been calibrated. A
warning message has been added to this facility for such a change. Warning
message is “Modifying this value may impact optimization. After a Fiber
Change, ensure a DOC optimization is performed. For an SRA card, a new
power audit is recommended to guarantee performance.”
For further information on the SRA power audit, refer to Technical Publication
323-1851-310, Configuration - Provisioning and Operating Procedures.

Figure 5-9
Example illustration of SRA Power Audit within DOC domain by SOC (DSC not running)

Wavelength provisioning
Wavelength provisioning can be done using L0 Control Plane (L0 CP) or not
and is configuration dependent. Using L0 CP is preferred as it simplifies
wavelength provisioning through automated connection management.
There are two supported L0 CP types:

• PHOTONIC
• L0 Provisioning
Both allow for wavelength provisioning and the PHOTONIC L0 CP type also
supports wavelength restoration. It is recommended that new fixed grid
Photonic configuration deployments use this L0 channel provisioning model
for the following reasons:
• Easier steps to provision channels
• Better interworking support with flexible grid
• Simpler future migration to flexible grid
For details on how to enable either L0 CP types, refer to NTRN71AA.2 Control

Plane Application Guide - Layer 0 (Photonic).
The following table provides a summary of colored and colorless photonic
configurations supported per OSRP node type, and the Site Manager
application to use for channel provisioning.
Table 5-7
L0 CP (OSRP Node) Type Support per Photonic Configuration and Service Provisioning
Shelf DOC Controlled Configuration Channel provisioning using Site Channel
Type Node Type Manager SNC application provisioning
using Site
L0 CP (OSRP Node) Type Manager DOC
application
L0 CP with Head-End
Mesh Restoration Provisioning (‘L0 [Note 3]
(PHOTONIC) Provisioning’)
[Note 1] [Note 2]
T-Series Colorless CDC No Yes No

Table 5-7
L0 CP (OSRP Node) Type Support per Photonic Configuration and Service Provisioning
Shelf DOC Controlled Configuration Channel provisioning using Site Channel
Type Node Type Manager SNC application provisioning
using Site
L0 CP (OSRP Node) Type Manager DOC
application
L0 CP with Head-End
Mesh Restoration Provisioning (‘L0 [Note 3]
(PHOTONIC) Provisioning’)
[Note 1] [Note 2]
S-Series Colored Directional Supported Supported Supported
Directionless Supported Supported Supported
CPL Directional with 6500 Supported Supported

primary shelf [Note 4]
Not supported
CPL Directionless with 6500 Supported Supported
primary shelf [Note 4]
6500 TOADM Supported
Any CPL node type which Not supported Supported

uses CPL as the primary shelf
[Note 4]
Colorless Directionless Supported Supported Supported
CDC Supported Supported Supported

• with CMD44 50 GHz or
100 GHz direct attach
Low Channel Count CD Supported Supported
CDA with 9x1 WSS or 5x1 Supported

RLA with COADM OTS direct
attach
CDA using 20x1 WSS Supported Not supported

Not supported
• with CCMD12 direct attach
• with CMD44 50 GHz direct
attach
Coherent Select Supported
Note 1: L0 CP enabled with OSRP Node Type = 'PHOTONIC' (supports non-MR SNC, PSNC, MR-SNC,
Non-MR SNCP, MR-SNCP).
Note 2: L0 CP enabled with OSRP Node Type = 'L0 Provisioning', PSNC only.
Note 3: L0 CP / OSRP not enabled.
Note 4: CPL channel access nodes sunset release is Rel. 12.0.

Wavelength provisioning not using L0 Control Plane

Refer to the “Adding optical channels” procedure in Technical Publication
323-1851-221, Commissioning and Testing for detailed procedures on how to
add channels. To add channels using PHOTONIC L0 Control Plane type, refer
to Technical Publication NTRN71AA, Control Plane Application Guide - Layer
0 (Photonic).
Adding channels not using L0 Control Plane includes the following:

• Connecting the transponder DWDM transmitter and receiver to the
Channel Mux/Demux port
— Before connecting the transponder fibers, ensure that transponder
circuit packs are already installed and provisioned. For 6500
transponder circuit pack DWDM provisioning (i.e., parameters such as
Tx wavelength, Tx power), refer to Technical Publication
323-1851-310, Configuration - Provisioning and Operating
Procedures.
Attention: The Tx wavelength and Tx power do not need to be set if the

transponder circuit pack supports Tx wavelength and Tx power
autoprovisioning and SPLI is used to provision the Photonic channel.
• Creating the logical definition for one channel, that is adding its Photonic
connections and adjacencies.
— The appropriate order to provision a channel is to:
– Provision Photonic connections at domain barriers (if any) using
the Site Manager Configuration->Nodal Connections->Photonic
Connections application.
– Provision the CMD Tx adjacency and Rx adjacency against the
CMD where the channel originates and terminates using the Site
Manager Configuration->Equipment & Facility Provisioning
application. Alternately, SPLI can be used to automatically set the
CMD Tx adjacency Transmitter Type and Rx adjacency Receiver
Type.
– (Optional, only required for a DIA, Colorless of CDC
configurations) Provision a Photonic connection between the CMD
Ch In/Ch Out port and the backbone amplifier Line B Out/Line A In
ports using the Site Manager Configuration->Nodal
Connections->Photonic Connections application. For Colorless
and CDC configurations, when the Photonic connection is created,
the wavelength is also user-specified.
– To de-provision the channel preform the reverse once the channel
is not DOC managed.

— In the originating and terminating node DOC location, using the Site
Manager DOC application, verify that the “DOC Trail Status” value
displays “COMPLETE” for the channel you provisioned. This indicates
that Network Channel Topology software is able to build the photonic
channel end-to-end since the provisioning is properly done.
• Provisioning DOC settings in each Photonic domain.
— Review the DOC settings (see “DOC Settings tab parameters” on
page 2-22) to understand the impact of enabling the Auto add
channels parameter.
• In the originating and terminating node DOC location, using the Site
Manager DOC application, click on the Add button to add the channel
through the Photonic system.
Note that for cases where the OSC link budget is exhausted, i.e.
stretched-span applications within a single or multi-span system that is DOC
controlled, the use of an alternate communication path is required (e.g. Line
interface OTM facility GCC with ILAN Ethernet connectivity between service
and photonic shelves at a terminal end or specific DCN configurations). Until
the first channel is added manually, no GCC communication between nodes
at the end of the stretched-span can occur. One the first channel is added,
subsequent automatic DOC channel capacity changes can be performed.
Refer to Technical Publication 323-1851-221, Commissioning and Testing -
Adding the first optical channel to a Stretched Span.
Wavelength provisioning using L0 Provisioning Control Plane type

Wavelength provisioning using L0 Provisioning Control Plane type consists of
the following high level steps. For details, refer to Technical Publication
NTRN71AA, Control Plane Application Guide - Layer 0 (Photonic).
• At the local and remote node, install and provision the transponder circuit
pack. The transponder DWDM provisioning parameters, such as Tx power
and Tx wavelength, will be auto-set in a subsequent step.
• At the local and remote node, connect the transponder DWDM transmitter
and receiver to the CMD Channel In/Out port.
• At the local and remote node, use the Site Manager Equipment & Facility
Provisioning application to select the CMD ADJ-TX facility the transponder
is connected to and set the Expected far end address format to
TID-SH-SL-PRT and the Expected Far End Address to point to the
transponder line-side facility connected to the CMD port.
— As a result of the above, a SPLI match occurs and SPLI auto-sets the
DWDM parameters, such as Tx power and Tx wavelength, on the
transponder DWDM line-side facility.

• At the local and remote node, verify that the CMD ADJ-RX Actual Far End
Address displays the transponder line-side facility connected to the CMD.
Click on the “Use actual Rx address and format” and then click on the OK
button. Verify that the CMD ADJ-RX Actual Far End Address and
Expected Far End Address match.
• If using explicit wavelength routing, provision the Designated Transit List
(DTL0) and the Designated Transit List set (DTLSET0) at either the local
or remote node using the Site Manager Configuration->Routing Profiles
application and the Routes tab (DTL0) and the Routing Lists tab
(DTLSET0). Note that the Site Manager Routing application automatically
creates a DTLSET0 for every DTL0 created, using the same label.
• At the local or remote node, add the SNC (i.e., the optical
channel/wavelength) using the Site Manager
Configuration->Sub-Network Connection application.
— Once the SNC is added, L0 Control Plane (OSRP) creates the
necessary Photonic connections at the local and remote Photonic
ROADM nodes as well as any intermediate Photonic ROADM nodes.
L0 Control Plane then interfaces with DOC in order to add the
wavelength through the Photonic ROADM system.
Wavelength deprovisioning using L0 Provisioning Control Plane type
Wavelength deprovisioning using L0 Provisioning Control Plane type consists
of the following high level steps. For details, refer to Technical Publication
NTRN71AA, Control Plane Application Guide - Layer 0 (Photonic).
• At the node where the SNC was created, edit the SNC Primary state from
IS to OOS state using the Site Manager Configuration->Sub-Network
Connection application.
— Once the SNC is put in the OOS state, L0 Control Plane interfaces with
DOC in order to delete the wavelength from the Photonic ROADM
system. L0 Control Plane then deletes all associated Photonic
connections at the local and remote Photonic ROADM nodes as well
as any intermediate Photonic ROADM nodes.
• At the node where the SNC was created, delete the SNC using the Site
Manager Configuration->Sub-Network Connection application.
Modifying an existing Photonic network
After the initial system installation, it is very likely that the network will undergo
some changes, either in its channel capacity (need to add or delete channels),
or in its topology (e.g. need to add a new branch at a ROADM node, or new
SCMD4 in the cascade at a TOADM node, or add a DIA at a node). This
section focuses on the some of these scenarios by detailing the necessary
procedures to perform.

Reprovisioning amplifier parameters on an in-service system

The reprovisioning of amplifier facility parameters such as EDFA peak power
target or gain tilt values, or DOC facility differential provisioning modulation
class bias values, may be required on in-service systems. This could occur for
instance if changes in the field data voids the initial link simulation data used.
A re-simulation then yields different provisioning values to be implemented on
the field system.
Such provisioning changes go into effect once the next re-optimization occurs
whether manually initiated or automatically initiated. The magnitude of the
total changes for each parameter depends upon the link engineering
simulation result. Although such changes are likely not to cause a traffic hit,
they are not guaranteed to be non-traffic affecting.
For EDFA peak power target and DOC Differential Provisioning changes, the
recommendation in these types of scenarios is to first place DOC in
“Enhanced with Auto-Monitor Only” automation mode.
Then, ensure that small changes are made on all EDFAs in a given
system-wide direction, in no greater than 1 dB increments, with manual
re-optimizations in between, until the total change in dB is achieved for the
given parameter.
For instance, if an EDFA peak power target value needs to be changed by

+1.4 dB on different booster EDFAs throughout the line in a given direction,
then perform the following:
• first adjustment by +1 dB on all booster EDFAs in the domain
• manually re-optimize
• second adjustment by +0.4 dB on all booster EDFAs in the domain
• manually re-optimize
For EDFA gain tilt changes, the recommendation is to perform changes on a

single EDFA at a time, in no greater than 1 dB increments at a time, and
re-optimize each time.

Adding wavelengths to an in-service Photonic system

Adding wavelengths to an in-service system is a built-in function in DOC.
Adding wavelengths does not impact traffic on existing channels. Refer to
“Wavelength provisioning not using L0 Control Plane” on page 5-38 and
“Wavelength provisioning using L0 Provisioning Control Plane type” on page
5-39.
• If new ROADM hardware is required to support a new wavelength, you
must first perform the new hardware installation. For example, see “Adding
a new CMD44 or BMD2” in Technical Publication 323-1851-221,
Commissioning and Testing).
• If new T-Series ROADM hardware is required to support a new
wavelength, you must first perform the new hardware installation. Refer to
“Adding a photonic domain to an existing Photonic system” on page 5-43
and “Adding a CCMD16x12 or an AMP4 to an existing node” on page
5-48.
Deleting wavelengths from an in-service Photonic system
Deleting wavelengths from an in-service system is a built-in function in DOC.
Deleting wavelengths does not impact traffic on existing channels.
• Refer to the “Wavelength addition and deletion” in Technical Publication
323-1851-221, Commissioning and Testing.
• Refer to “Wavelength deprovisioning using L0 Provisioning Control Plane
type” on page 5-40.
Key points to be aware of:

• Do not disconnect any transponder transmitters from the system until the
wavelength has been deleted.
are completed. This is mentioned in “Topology application affects on DOC
actions” on page 2-50 and “Use of DOC trail to determine incomplete
channel trails prior to channel actions” on page 2-55
• Verify that the wavelength being deleted is not the one that has a GCC
(w/OSPF circuit) enabled on it for topology to function (e.g. stretch span).
If it is, it is important to verify that there are other wavelengths with GCC
(w/OSPF circuit) enabled to keep topology functioning correctly.

Re-routing wavelengths on an in-service Photonic system

Re-routing wavelengths involve changing a wavelength’s ingress or egress
point in the network. No specific procedure covers this due to the high number
of potential scenarios. Generally, the way to proceed is to use the existing
procedures to delete the wavelength and add it back with the new routing.
Attention: It is recommended to wait 5 minutes after a topology change

before initiating the wavelength addition to make sure the new topology is
updated accordingly. Otherwise, the wavelength could end up as Partially
Added.
Adding a photonic domain to an existing Photonic system

The following section describes a high-level procedure to add a Photonic
Domain as shown in the figure below.
Attention: The description below only covers the case when both OTSs at
the node where the add occurs are Channel Access (ROADM type,
WSS-based) OTSs.

Figure 5-10
Adding a Photonic Domain
For a single-degree expansion, the required photonic circuit packs that form
part of the new OTS group must be ordered for equipping at their respective
shelves and node. They include:
• OSC SFP
• 2xOSC circuit pack (if existing 2xOSC circuit packs do not have an
available OSC SFP port). Note that the SPAP-2 w/2xOSC 2xSFP circuit
pack is an alternative to the 2xOSC circuit pack which allows the saving of
one slot-space on 7-slot type 2 shelves. If using a SRA/ESAM/SAM then
the OSC will be plugged directly into this circuit pack.
• Line Interface Module(s) (e.g SLA, MLA, MLA2, SRA, ESAM,SAM)
• XLA (if the SRA/ESAM/SAM are being used)
• WSSOPM circuit pack
• CMD44 module(s) (for local add/drop)
• DSCM (if required) and fixed attenuators (if required)

Prerequisites
The following pre-requisites are necessary:
• All nodes involved in the reconfiguration are running the same software
release.
• You must have the latest backup for all nodes involved in the
reconfiguration.
• You must ensure that no DOC channel add or channel delete operation is
in progress.
• You have an up-to-date map of your system.
• If the DOC overall status is not Optimal, follow Technical Publication
procedures to get the DOC Overall status to Optimal. No DOC related
alarms should exist on the system prior to the reconfiguration.
• At the node(s) where the Photonic domain add is being done (Site ID 2
and 3 in the example):
— the new OTS equipment can be equipped in the same shelf as the
existing OTS(s) or in a new shelf. If the new OTS equipment is
equipped in a new shelf, the new shelf must be commissioned and
Nodal SLAT completed and must have the same Site ID and Site
Name (TID) but different Shelf number as the existing shelf(s). The
new shelf must be connected to the existing shelf(s) using the ILAN
ports. The ILAN ports must have data communications parameters
setup. The new shelf must be TID consolidated with the existing
shelf(s).
— if the new OTS equipment will be in the same shelf as an existing
OTS(s), the new OTS must be provisioned with a different OTS
instance number as the existing OTS(s) in the shelf
— the new OTS must have the Optical system identifier set to a different
value than the existing Photonic domain(s) and must have the DOC
site parameter set to True and have valid Tx Path ID such that when
added to the existing Photonic domain(s) meet the Tx Path ID rules
defined in the Photonic Guide (for 6500) or the Planning Guide (for
CPL)
— the required patch cords are installed between the Photonic circuit
packs, including the patch cords that connect the WSS circuit packs in
the existing OTS(s) and the new OTS
• The other nodes part of the new Photonic domain (“Other nodes with
OSID C” in the example):

— must be commissioned and Nodal SLAT completed. If possible, it is

recommended that at least 1 bidirectional channel is added in the new
Photonic domain to validate the Photonic domain. This channel can be
removed before the reconfiguration, if required or it can remain in
place during the reconfiguration.
— must have their OTSs provisioned and the OTSs must have the Optical
system identifier set to a different value than the existing Photonic
domain(s) but equal to the Optical system identifier used at the new
OTS at the node(s) where the Photonic domain add is being done
— must have their OTSs provisioned with the DOC site parameter set to
False
— have OTSs with valid Tx Path ID such that when added to the existing
Photonic domain(s) meet the Tx Path ID rules defined in the Photonic
Guide (for 6500) or the Planning Guide (for CPL)
— have Site IDs that are unique and different than the Site IDs used in
the existing Photonic domain(s)
• Note that when an OTS is edited and the DOC site parameter is changed
from False to True, the DOC settings default to the following values:
– Automation mode=Enhanced Auto Monitor Only
– Auto add channels=Disabled
– Auto delete channels=Disabled
– Auto delete on channel LOS=Disabled.
This is different when compared to the case when the OTS is created
which has the following default DOC settings:
– Automation mode=Enhanced
– Auto add channels=Enabled
– Auto delete channels=Enabled
– Auto delete on channel LOS=Disabled
High-level procedure
The following high-level steps describe the procedure to add a photonic
domain to an existing system:
1 Access the Configuration->Equipment & Facility Provisioning application of

the node where the Photonic domain will be added (Site ID 2 in the example)
and select the WSS equipment and the ADJ Facility Type belonging to new
OTS (OTS3 in the example).
a. Edit the adjacency for the WSS port to point to the existing OTS (OTS 1
in the example) WSS port it is physically connected to. You must provision
the Adjacency Type to be WSS, Expected far end address format to be
TID-SH-SL-PRT and Expected far end address to be the actual
TID-SH-SL-PRT.

b. Repeat this step for each WSS port that connects to other existing OTS
WSS ports, if any (OTS2 in the example).
2 Access the Configuration->Equipment & Facility Provisioning application of
the node where the Photonic domain will be added (Site ID 2 in the example)
and select the WSS equipment and the ADJ Facility Type belonging to an
existing OTS (OTS1 in the example).
a. Edit the adjacency for the WSS port to point to the new OTS (OTS3 in the
example) WSS port it is physically connected to. You must provision the
Adjacency Type to be WSS, Expected far end address format to be
TID-SH-SL-PRT and Expected far end address to be the actual
TID-SH-SL-PRT.
b. Repeat this step for other existing OTSs, if any (OTS2 in the example).
3 If required, repeat the above steps at the other node where the Photonic
domain will be added (Site ID 3 in the example).
4 If the new Photonic domain is in a different OSPF area, DBRS must be
enabled at the node(s) where the Photonic domain was added. For further
information, refer to
— Data communications Planning section within the 6500 Planning
Guide (NTRN10EY.4).
— Technical Publication 323-1851-310 Configuration - Provisioning and
Operating, Part 1 of 2, Communications Management section
Adding a photonic domain to an existing T-Series Photonic system

The following section provides the high-level procedure to add a photonic
domain to an existing T-Series Photonic system that uses CCMD 16x12
modules. For detailed procedure, refer to Technical Publication 323-1851-103,
6500-T12 Packet-Optical Shelf - Guide.
• Provision the RLA equipment you are adding.
• Create the new OTS using the Site Manager Photonic Configuration
Management application.
• Provision the OTS Main slot sequence to point to the RLA module using
the Site Manager Photonic Configuration Management application and
the OTS Sequence tab.
• Add the new RLA equipment to the FIM equipment using the Site Manager
Photonic Configuration Management application and the TID Sequence
tab.
• If, before starting this procedure, the existing node was equipped with four
degrees, add a second AMP4 pluggable in each CCMD16x12 module at
the node (see “Adding a CCMD16x12 or an AMP4 to an existing node” on
page 5-48) and then insert the RLA module equipped with an OSC
pluggable in the slot where the equipment has been provisioned. If, before
starting this procedure, the existing node was not equipped with four
degrees, insert the RLA module equipped with an OSC pluggable in the
slot where the equipment has been provisioned.

• Fiber the OSC pluggable to the RLA and fiber the RLA to the FIM using
MPO cables. For fibering information, refer to the engineering data
specific to the deployment (for example, EDP/IDP or OnePlanner
information).
• Provision the OSC OSPF circuit against the RLA OSC pluggable using the
Site Manager Comms Setting Management application. Use the Network
Area identified in the EDP/IDP.
• Provision the following RLA parameters as per EDP/IDP:
— ADJ-LINE port 5: Fiber Type, Target Span Loss, Expected far end
address format, Expected far end address
— VOA port 5: Target Pad, Target Peak Power
— AMP port 5: Target Peak Power, Target Gain Tilt
— AMP port 8: Gain Mode, Target Peak Power, Target Gain Tilt, TOP
Offset
• Use the Site Manager Configuration->Photonic Services->Connection
Validation application and the Validation Summary tab to verify the Status
field shows “Pass” for the newly added RLA module.
• Repeat the above steps at the other node that terminates the Photonic
domain.
Adding a CCMD16x12 or an AMP4 to an existing node

The following section provides the high-level procedure to add a CCMD 16x12
module or an AMP4 module to an existing node. For detailed procedure, refer
to Technical Publication 323-1851-103, 6500-T12 Packet-Optical Shelf -
Guide.
• Provision the equipment (CCMD16x12 module or AMP4 pluggable) you
are adding.
• Add the new equipment to the FIM equipment using the Site Manager
Photonic Configuration Management application and the TID Sequence
tab. Identify the CCMD16x12 shelf-slot, or the AMP4 shelf-slot-subslot
and its associated CCMD16x12 shelf-slot.
• Insert the equipment in the slot/subslot where the equipment has been
provisioned.
• Fiber the equipment using MPO cables. For fibering information, refer to
the engineering data specific to the deployment (for example, EDP/IDP or
OnePlanner information).
• Use the Site Manager Configuration -> Photonic Services -> Connection
Validation application and the Validation Summary tab to verify that the
Status field shows “Pass” for the newly added CCMD 16x12 and AMP4
pluggable modules.

Reconfiguring a ROADM node to include a LIM in the mux/demux path

Within a ROADM node, insertion of a LIM circuit pack between a WSS switch
port and CMD filter already connected with traffic-carrying wavelengths may
arise. One reason for this is that new DWDM channels are added with different
Tx and/or Rx specifications compared to currently deployed interfaces. A
revised link design may warrant extra amplification in either the drop direction
or add direction, or both. Two cases where this may apply are:
• Drop LIM using an SLA (“SLA-based Drop LIM” on page 3-119)
• Mux Amp using an SLA and/or MLA (“SLA/MLA Mux Amp” on page 3-124)
Prudence must be taken in the insertion of the LIM, since this is a traffic
impacting operations to existing channels.
For a detailed customized method of procedure, please contact Ciena

Network Engineering Services.


Provisioning Examples 6-
This chapter provides examples to help understanding the various

provisioning tasks to be performed when setting up the Photonic network and
its associated channels.
Table 6-1
Topic
“OTS provisioning examples” on page 6-2
— “Channel access OTS (ROADM subtype) - Metro ROADM configuration” on page 6-2
— “Channel access OTS (ROADM subtype) - using SRA with XLA” on page 6-5
— “Amplifier OTS (AMP subtype) - using LIMs” on page 6-8
— “Amplifier OTS (AMP subtype) - using SRA and XLA or ESAM/SAMs and XLA/MLAx” on page 6-10
— “Channel Access OTS (COADM subtype) - CDA with COADM direct attach” on page 6-19
— “Channel access OTS (ROADM subtype) - CDA with CCMD12 direct attach” on page 6-21
— “Channel access OTS (ROADM subtype) - CDC” on page 6-27
— “Channel access OTS (ROADM subtype) - T-Series CDC” on page 6-30
“Inter-OTS and intra-OTS adjacency provisioning examples” on page 6-35
“Wavelength provisioning and deprovisioning examples” on page 6-42
— “Wavelength provisioning example not using L0 Control Plane (linear system, single domain)” on
page 6-42
— “Wavelength deprovisioning example not using L0 Control Plane (linear system, single domain)” on
page 6-43
— “Provisioning a wavelength example using SPLI (not using L0 Control Plane) (multi-domain
system)” on page 6-45
— “Provisioning/deprovisioning wavelengths when a specific wavelength is used multiple times” on
page 6-48
— “Wavelength provisioning example using L0 Provisioning Control Plane type and implicit routing” on
page 6-49
— “Wavelength provisioning example using L0 Provisioning Control Plane type and explicit routing” on
page 6-51
— “Wavelength deprovisioning example using L0 Provisioning Control Plane type” on page 6-52

6-2 Provisioning Examples
OTS provisioning examples

Channel access OTS (ROADM subtype) - Metro ROADM configuration
A ROADM OTS is shown in the figure below. This could be the only OTS in a
1-way Metro ROADM terminal configuration or one of several OTSs in a
multi-degree Metro ROADM configuration.
The example assumes a 7-slot or 14-slot shelf using external slots 83 (PPC6),
84 (CMD44), 85 (DSCM), 86 (PPC6).
Figure 6-1
Channel access OTS (ROADM) example: 1-way Metro ROADM Terminal configuration

Using the Site Manager Photonic Configuration Management application, the

OTS tab is accessed to create basic OTS parameters as shown in the table
below.
Table 6-2
Metro ROADM - Basic OTS parameters within Photonic Configuration Management - OTS tab
Basic OTS Parameter
OTS instance 1
Template Family ROADM

Configuration: Channel access / Subtype: ROADM
OTS Optical system identifier MTLOTT
OTS Tx Path identifier 8
OSC OSC-1-1-1
DOC Site YES
Associated OTS N/A. Leave empty
Autoroute Enable
CPS Disable
Sequence CHC Updates Disable
Gaurdband Width 0
Automatic Guardband Disable
OSC Required True
Once the basic OTS parameters are provisioned, the “Slot Configuration
Mode” parameter is auto-set to “Derived”.
Slot Sequences are filled out in the following order. The values used are
shown in the table that follows:
• After the Main Slot Sequence is autopopulated with empty values, they are
filled with the Add/Drop sequence.
• Two branch sequences of the switch type are created and their values
filled with Add/Drop sequences, representing
— the OMDF4 cascade (terminated by the CMD44) connected to WSS
switch 3
— the BS5 connected to WSS switch 4

• A branch sequence of the group type is created once the BS5 is

provisioned in the switch sequence (switch 4). Add/drop sequence values
are then filled on two BS5 ports, representing the OMDF8 Group A and
Group E connections.
Table 6-3
Metro ROADM OTS - Main and Branch (Switch, Group Type) slot sequence provisioning example
Slot sequence information provided in Site Manager User-provisioned in Slot

Equipment & Facility Provisioning application Sequences tab
Instance Label Slot Sequence Anchor DROP Add

AID AID Sequence Sequence
1 Main SLOTSEQ-1-1-1 N/A DSCM-1-85 -
LIM-1-2 LIM-1-2
WSSOPM-1-3 WSSOPM-1-3
2 Switch 1 Out SLOTSEQ-1-1-2 ADJ-1-3-4 - -
4 Switch 3 Out SLOTSEQ-1-1-4 ADJ-1-3-8 OMDF4-1-83-2 OMDF4-1-83-2
OMDF4-1-83-3 OMDF4-1-83-3
CMD44-1-84 CMD44-1-84
5 Switch 4 Out SLOTSEQ-1-1-5 ADJ-1-3-10 BS-1-83-1 BS-1-83-1
6 GRP A (T) SLOTSEQ-1-1-6 ADJ-1-83-1-4 OMDF8-1-86-1 OMDF8-1-86-1
7 GRP B (T) SLOTSEQ-1-1-7 ADJ-1-83-1-6 - -
8 GRP C (T) SLOTSEQ-1-1-8 ADJ-1-83-1-8 - -
9 GRP D (T) SLOTSEQ-1-1-9 ADJ-1-83-1-10 - -
10 GRP E (T) SLOTSEQ-1-1-10 ADJ-1-83-1-12 OMDF8-1-86-4 OMDF8-1-86-4

Channel access OTS (ROADM subtype) - using SRA with XLA

A ROADM OTS using SRA and XLA circuit packs is shown in the figure below.
This could be the only OTS in a 1-way ROADM terminal configuration or one
of several OTSs in a multi-degree ROADM configuration.
The example assumes dispersion compensation is deployed, with a 7-slot or

14-slot shelf using virtual slots 91 to 94 for DSCMs (pads), 95 (for CMD44 50
GHz Blue) and 96 (for CMD44 50 GHz Red).
Figure 6-2
Channel access (ROADM OTS) example - 1-way ROADM using SRA, XLA and cascaded LIM

below.
Table 6-4
ROADM with SRA/XLA - Basic OTS parameters within Photonic Configuration Management - OTS
tab
Basic OTS Parameter
OTS instance 1

OTS Optical system identifier DOM2

Table 6-4
ROADM with SRA/XLA - Basic OTS parameters within Photonic Configuration Management - OTS
tab
Basic OTS Parameter
OSC OSC-1-5-1
DOC Site YES
Associated OTS N/A. Leave empty
Autoroute Enable (set to Disable for L0 Control Plane

applications)
CPS Disable (set to Enable for L0 Control Plane

applications)
Sequence CHC Updates Disabled
Gaurdband Width 0
Automatic Guardband Disabled
OSC Required True
filled with the Add/Drop sequence.
• Two branch sequences of the switch type are created and their values
filled with Add/Drop sequences, representing
— the CMD44 Blue 50 GHz module
— the CMD44 Red 50 GHz module

Table 6-5
ROADM OTS with SRA/XLA- Main and Branch (Switch) Slot-Sequence Provisioning Example


1 Main SLOTSEQ-1-1-1 N/A SRA-1-5 SRA-1-5
DSCM-1-91 -
DSCM-1-92 -
XLA-1-4 XLA-1-4
DSCM-1-93 -
DSCM-1-94 -
LIM-1-3 -
WSSOPM-1-1 WSSOPM-1-1
Switch 4 Out SLOTSEQ-1-1-5 ADJ-1-1-10 - -
Switch 5 Out SLOTSEQ-1-1-6 ADJ-1-1-12 - -
6 Switch 7 Out SLOTSEQ-1-1-8 ADJ-1-1-16
7 Switch 8 Out SLOTSEQ-1-1-9 ADJ-1-1-18 CMD44-1-95 CMD44-1-95
10 Switch 9 Out SLOTSEQ-1-1-10 ADJ-1-1-20 CMD44-1-96 CMD44-1-96
This example can be followed for all ESAM/SAM and XLA/MLAx

configurations for ROADM OTSs.

Amplifier OTS (AMP subtype) - using LIMs

An amplifier OTS example is shown in the figure below. The slot sequencing
model includes the provisioning of basic OTS parameters as per Table 6-6 on
page 6-9, and the main sequence, as per Table 6-7 on page 6-9 and Table 6-8
on page 6-9
Figure 6-3
Amplifier OTS (AMP) example
After Main Slot Sequence is autopopulated with empty values, they are filled
with the Add/Drop sequence. Note that no branch sequences of any type are
required in the amplifier OTS.

Table 6-6
AMP OTSs - Basic OTS parameters within Photonic Configuration Management - OTS tab
Basic OTS Parameter OTS-1-1 OTS-1-2
Template Family Line Amplifier

Configuration: Amplifier / Subtype: AMP
OTS Optical system identifier LINEAR11 LINEAR11
OTS Tx Path identifier 1 2
OSC OSC-1-15-1 OSC-1-15-2
Amplifier Mate OTS OTS-1-2 OTS-1-1
OSC Required True True
Coherent Select Site No No
Table 6-7
Amplifier - Main slot sequence provisioning example (OTS-1-1 shown)


1 Main SLOTSEQ-1-1-1 N/A LIM-1-1 LIM-1-1
DSCM-1-91-1
Table 6-8



Amplifier OTS (AMP subtype) - using SRA and XLA or ESAM/SAMs and
XLA/MLAx
AMP OTSs with the SRA, ESAM, SAM, XLA and MLAx:
• Require caution in provisioning the basic OTS parameters and their OTS
slot-sequences. Provisioning must reflect the following connections as
indicated in “Slot sequence rules for OTSs using SRA/XLA and
ESAM/SAM/XLA/MLAx” on page 4-40:
Rule 1: For SRA and XLA within same AMP OTS:
— SRA Line A is connected to XLA Line A
— XLA Line B connected to SRA Line B
Rule 2: For ESAM/SAM and XLA/MLAx within same AMP OTS:
— ESAM/SAM Line A are connected to MLAx Line A
— MLAx Line B connected to ESAM/SAM Line B
Rule 3: For connection between AMP OTSs built with XLA:
— SRA/ESAM/SAM Line A connects to XLA Line B
— XLA Line B connects to SRA/ESAM/SAM Line A
slot configuration:
— ESAM/SAM/LIM Line A connects to MLAx Line B (LIM =
LIM/SLA/MLA/MLA2/MLA3)
— MLAx Line B connects to ESAM/SAM/LIM Line A
slot configuration:
— MLAx Line A connects to MLAx Line B
— MLAx Line B connects to MLAx Line A
To illustrate the above as pertaining to OTS and slot-sequence provisioning,
some examples are described in the following pages.
Attention: Note that many other examples are possible, as per the
supported combinations of circuit packs indicated in “Photonic Line Amplifier
node with Raman (SRA)/ESAM/SAM, XLA and OPM” on page 4-134

Example 1
Amplifier OTS example using SRA, ESAM and XLA as shown in the figure
below. In the example, the ESAM and XLA are in the same AMP OTS, and an
individual SRA is in the other AMP OTS.

OTS tab is accessed to create basic OTS parameters as shown in Table 6-9
on page 6-12.
The Main Slot Sequence is initially autopopulated with empty values. They are
then filled with the Add Drop direction entries. Note that no branch sequences
of any type are required in the amplifier OTS.
The slot-sequence provisioning for each AMP OTS is shown in Table 6-10 on
page 6-12 and Table 6-11 on page 6-12.
Figure 6-4
AMP OTS - example 1 using SRA, ESAM and XLA

Table 6-9
AMP OTSs with SRA/ESAM/XLA - Basic OTS parameters within Photonic Configuration
Management - OTS tab

OTS Optical system identifier DOM2 DOM2
OSC OSC-1-1-2 OSC-1-3-2
Table 6-10


Table 6-11


1 Main SLOTSEQ-1-2-1 N/A ESAM-1-3 ESAM-1-3
XLA-1-2 XLA-1-2

Example 2
Amplifier OTS using SRA, ESAM and XLA as shown in the figure below. The
SRA and XLA are shown in the same AMP OTS. An individual ESAM is shown
in the other AMP OTS.
Figure 6-5
AMP OTS - example 2 using SRA, ESAM and XLA
Table 6-12

OTS Optical system identifier RAMAN1 RAMAN1
OSC OSC-1-5-2 OSC-1-7-2

Table 6-12

Table 6-13


XLA-1-6 XLA-1-6
Table 6-14



Example 3
Amplifier OTS using ESAM, MLAx and LIM (3 slot configuration) as shown in
the figure below. The ESAM and MLAx are shown in the same AMP OTS. An
individual LIM is shown in the other AMP OTS.
Figure 6-6
AMP OTS - example 3 using ESAM, MLAx and LIM
Table 6-15
AMP OTSs with ESAM/MLAx and LIM- Basic OTS parameters within Photonic Configuration

OSC OSC-1-2-2 OSC-1-1-1

Table 6-15
AMP OTSs with ESAM/MLAx and LIM- Basic OTS parameters within Photonic Configuration

Table 6-16


MLAx-1-3 MLAx-1-6
DSCM-1-99
Table 6-17


1 Main SLOTSEQ-1-2-1 N/A LIM-1-4 ESAM-1-4
DSCM-1-98
The LIM in this example can be replaced with any other line facing module
(LIM/SLA/MLA/MLA2/MLA2v/MLA3).
The MLAx that is provisioned with the ESAM can only be a MLA, MLA2 or
MLA3 circuit pack.
The ESAM can be replaced with a SAM circuit pack.

Example 4
Amplifier OTS using ESAM and MLAx (4 slot configuration) as shown in the
figure below. The ESAM and MLAx are shown in the same AMP OTS and
another ESAM and MLAx is shown in the other AMP OTS.
Figure 6-7
AMP OTS - example 4 using ESAM and MLAx
Table 6-18
AMP OTSs with ESAM and MLAx - Basic OTS parameters within Photonic Configuration

OSC OSC-1-1-2 OSC-1-4-1

Table 6-18
AMP OTSs with ESAM and MLAx - Basic OTS parameters within Photonic Configuration

Table 6-19


MLAx-1-2 MLAx-1-2
DSCM-1-99
Table 6-20


MLAx-1-3 MLAx-1-3
DSCM-1-98
The MLAx that is provisioned with the ESAM can only be a MLA, MLA2, MLA3
or XLA circuit pack.
The ESAM can be replaced with a SAM circuit pack.

Channel Access OTS (COADM subtype) - CDA with COADM direct attach
A COADM OTS used in a CDA with COADM direct attach configuration is
shown in the figure below.
Figure 6-8
COADM OTS example: CDA with COADM direct attach
Within the Site Manager Photonic Configuration Management application, the

below.
Table 6-21
COADM OTS - Basic OTS parameters within Photonic Configuration Management - OTS tab
Basic OTS Parameter


Table 6-21
COADM OTS - Basic OTS parameters within Photonic Configuration Management - OTS tab
Basic OTS Parameter
Autoroute Disable
OSC Required False
filled with the Add/Drop sequence representing LIM and SMD circuit packs
• One or more branch sequences of the switch type are created and their
values filled with Add/Drop sequences representing CCMD12 circuit
packs
Table 6-22
COADM OTS Main and Branch (Switch) Slot Sequence provisioning example


SMD-1-6 SMD-1-6
2 Switch 1 Out SLOTSEQ-1-2-2 ADJ-1-6-12 CCMD12-1-8 CCMD12-1-8
3 Switch 2 Out SLOTSEQ-1-2-3 ADJ-1-6-14 CCMD12-1-9 CCMD12-1-9
For CDA with COADM direct attach configurations using ROADM OTS
subtypes with 2x1 50 GHz WSS circuit packs, the LIM used in the
main-sequence may or may not be required dependent on the link budget
design.

The COADM OTS main sequence in this case would only contain the SMD but
without the COADM OTS LIM.
In other words, the slot sequence and basic OTS provisioning are similar to
the case outlined above, excluding the LIM.
Channel access OTS (ROADM subtype) - CDA with CCMD12 direct attach
A 6-way CDA with CCMD12 direct attact configurations is shown in the figure
below. In this example:
• OTS-1 and OTS-2 use MLA3, OTS-3 and OTS-4 use MLA3+ESAM and
OTS-5 and OTS-6 use XLA+SRA
• Shelf #1 contains OTS-1/2 and Shelf #2 contains OTS-3/4 and Shelf #3
contains OTS-5/6
• Shelf #1 contains a FIM Type 4, a FIM Type 5 and a FIM Type 6
• Shelf #2 contains a FIM Type 4
• Shelf #3 contains a FIM Type 4 and a FIM Type 5
• Shelf #1 contains 2 CCMD12s

Figure 6-9
Channel access (ROADM OTS) example: 6-way CDA with CCMD12 direct attach

below.

Table 6-23
CDA with CCMD12 direct attach - Basic OTS parameters within Photonic Configuration
Basic OTS Parameter OTS-1-1 OTS-1-2 OTS-2-1 OTS-2-2 OTS-3-1 OTS-3-2

OTS Optical system identifier DOM1 DOM2 DOM3 DOM4 DOM5 DOM6
OTS Tx Path identifier 1 5 9 13 17 21
OSC OSC-1-4-1 OSC-1-8-1 OSC-2-4-1 OSC-2-8-1 OSC-3-4-1 OSC-3-8-1
DOC Site True
Associated OTS N/A (leave empty)
Autoroute Disable
CPS Enable
Gaurdband Width 0
OSC Required True
The OTS Sequence tab within the application is used to provision the main
equipment in the OTS.
In OTS Sequence tab, select the OTS, click on Slot Sequences, select the
Main sequence and the click on Edit Sequence. Add the MLA3/XLA and WSS
in the Add drop sequence. This is done for each OTS as shown in the table
below.
Table 6-24
CDA with CCMD12 direct attach Slot sequence provisioning example
Sequence Identifier Label Anchor AID Drop Sequence Add Sequence
SLOTSEQ-1-1-1 Main N/A 1-3 (MLA3) 1-1 (WSS 20x1)

1-1 (WSS 20x1) 1-3 (MLA3)

1-5 (WSS 20x1) 1-7 (MLA3)

2-1 (WSS 20x1) 2-3 (MLA3)

Table 6-24
CDA with CCMD12 direct attach Slot sequence provisioning example

2-5 (WSS 20x1) 2-7 (MLA3)
SLOTSEQ-3-1-1 Main N/A 3-3 (SRA) 3-1 (WSS 20x1)

3-1 (WSS 20x1) 3-3 (SRA)
SLOTSEQ-3-2-1 Main N/A 3-7 (SRA) 3-5 (WSS 20x1)

3-5 (WSS 20x1) 3-7 (SRA)
The TID Sequence tab within the application is used to provision how the FIM
equipment is connected to the WSSs and CCMD12s.
As you provision the TIDSLOTSEQ instances (see tables below), the

Intersecting Slot Sequence gets populated with the appropriate SLOTSEQ
instances and Intersecting Status becomes Resolved.
Table 6-25
CDA with CCMD12 direct attach FIM Type 4 TID Sequence provisioning example
Sequence Identifier Anchor AID Label Drop Sequence Add Sequence
TIDSLOTSEQ-1-83-1 ADJ-1-83-1 MPO 1-1 1-1
...
TIDSLOTSEQ-1-83-10 ADJ-1-83-10 Out LC 1-13 1-13
...
...

Table 6-25
...
...
...
Table 6-26
...
...
Table 6-27

Table 6-27
...
...

Channel access OTS (ROADM subtype) - CDC

A 2-way CDC node with ROADM OTSs is shown in the figure below.
Figure 6-10
Channel access (ROADM OTS) example: 2-way CDC node

OTS tab is accessed to create basic OTS parameters as shown in the tables
below.
Table 6-28
CDC node - Basic OTS parameters within Photonic Configuration Management - OTS tab
(OTS-1-1)
Basic OTS Parameter


Table 6-28
(OTS-1-1)
Basic OTS Parameter
OSC OSC-1-11-2
DOC Site YES

applications)

applications)
Gaurdband Width 0
OSC Required True
Table 6-29
(OTS-2-1)
Basic OTS Parameter

OSC OSC-1-1-1
DOC Site YES

applications)

applications)

Table 6-29
(OTS-2-1)
Basic OTS Parameter

Gaurdband Width 0
OSC Required True
For each OTS, the Main Slot Sequence auto populates with the values shown
in the tables below. There are no branch sequences created in this case,
because with CDC the subsequent step of TID Sequence provisioning
accounts for the WSS-CCMD and WSS-WSS connections.
Table 6-30
CDC node OTS-1-1 slot sequence provisioning example
SLOTSEQ-1-1-1 Main N/A 1-11,1-12,1-13 1-13,1-12,1-11
Table 6-31
SLOTSEQ-2-1-1 Main N/A 2-2,2-3 2-3,2-2
As you provision the TIDSLOTSEQ instances corresponding to backbone

OTSs (see table below), the Intersecting Slot Sequence gets populated with
the appropriate SLOTSEQ instances and Intersecting Status becomes
Resolved.
Table 6-32
CDC node TID Sequence provisioning example
TIDSLOTSEQ-1-83-1 ADJ-1-83-1 WSS 1 Switch A MPO 2-3 2-3
TIDSLOTSEQ-1-83-5 ADJ-1-83-5 WSS 2 Switch A MPO 1-13 1-13
TIDSLOTSEQ-1-83-9 ADJ-1-83-9 WSS 3 Switch A MPO (empty) (empty)
TIDSLOTSEQ-1-83-13 ADJ-1-83-13 WSS 4 Switch A MPO (empty) (empty)

Table 6-32
...
TIDSLOTSEQ-1-83-65 ADJ-1-83-65 CMD 1 A MPO 2-5 2-5
...
Channel access OTS (ROADM subtype) - T-Series CDC

A 3-way T-Series CDC node with ROADM OTSs is shown in the figure below.
Figure 6-11
Channel access (ROADM OTS) example: 3-way CDC node

OTS tab is accessed to create basic OTS parameters as shown in the tables
below.

Table 6-33
(OTS-1-1)
Basic OTS Parameter

DOC site True
Autoroute Disable
CPS Enable
OSC Required True
Table 6-34
(OTS-1-2)
Basic OTS Parameter

DOC site True
Autoroute Disable
CPS Enable
OSC Required True

Table 6-35
(OTS-1-3)
Basic OTS Parameter

DOC site True
Autoroute Disable
CPS Enable
OSC Required True
The OTS Sequence tab within the application is used to provision the main
equipment in the OTS. The main equipment for 6500 T-Series is the RLA
module.
In OTS Sequence tab, select the OTS-1-1, click on Slot Sequences, select the
Main sequence and the click on Edit Sequence. Add RLA in shelf 1 slot 6 in
the Add drop sequence.
Table 6-36
Sequence Identifier Label Drop Sequence Add Sequence
SLOTSEQ-1-1-1 Main 1-6 1-6
Table 6-37

Table 6-38
The TID Sequence tab within the application is used to provision how the FIM
equipment is connected to the RLA module, the CCMD16x12 module, and the
AMP4 pluggable.
In TID Sequence tab, select the FIM, then perform these actions:
• Select FIM port 1, click on Edit Sequence and add RLA in shelf 1 slot 6 in
• Select FIM port 77, click on Edit Sequence and add AMP4 in shelf 1 slot
2 subslot 3 followed by CCMD in shelf 1 slot 2 in the Add drop sequence.
• Select FIM port 73, click on Edit Sequence and add AMP4 in shelf 1 slot
11 subslot 3 followed by CCMD in shelf 1 slot 11 in the Add drop
sequence.
Resolved.
Table 6-39
Sequence Identifier Anchor Label Drop Sequence Add Sequence
TIDSLOTSEQ-1-71-1 ADJ-1-71-1 1 A MPO 1-6 1-6
TIDSLOTSEQ-1-71-2 ADJ-1-71-2 1 B MPO 1-6 1-6
TIDSLOTSEQ-1-71-3 ADJ-1-71-3 1 C MPO 1-6 1-6
TIDSLOTSEQ-1-71-4 ADJ-1-71-4 1 D MPO 1-6 1-6

Table 6-39
TIDSLOTSEQ-1-71-13 ADJ-1-71-13 4 A MPO (empty) (empty)
TIDSLOTSEQ-1-71-14 ADJ-1-71-14 4 B MPO (empty) (empty)
...
TIDSLOTSEQ-1-71-73 ADJ-1-71-73 19 A MPO 1-11-3,1-11 1-11, 1-11-3
...
...
TIDSLOTSEQ-1-71-77 ADJ-1-71-77 20 A MPO 1-2-3,1-2 1-2, 1-2-3
...
If the node is equipped with the optional OTDR4 module, the TID Sequence
tab within the application is used to provision how the OTDR4 equipment is
connected to the RLA equipment.
In TID Sequence tab, select the OTDR4 in shelf 1, slot 11, subslot 4 and then
perform these actions:
• Select OTDR4 port 1, click on Edit Sequence and add RLA in shelf 1 slot
5 in the Add drop sequence.
Resolved.

Table 6-40
CDC node TID Sequence provisioning example for OTDR4
TIDSLOTSEQ-1-11-4-1 ADJ-1-11-4-1 OTDR 1 1-5 1-5
TIDSLOTSEQ-1-11-4-4 ADJ-1-11-4-4 OTDR 4 (empty) (empty)
Inter-OTS and intra-OTS adjacency provisioning examples

The figure below shows an example of adjacency provisioning using Line Amp
and 2-way ROADM nodes. These examples cover inter-OTS adjacency
provisioning.
Figure 6-12
Adjacency provisioning example
SLA
Adjacency provisioning for SITEA

Provision adjacencies for SITEA as follows (see figure below):
Provision Fiber Type used on the line:
• ED-ADJ-LINE::ADJ-1-2-5:CTAG:::FIBERTYPE=ELEAF;

• ED-ADJ-LINE::ADJ-1-13-5:CTAG:::FIBERTYPE=NDSF;
Provision the LIM-LIM line adjacency:
• ED-ADJ::ADJ-1-2-5:CTAG:::PROVFEADDR=SITEB-1-13-8,PADDRFORM=
TID-SH-SL-PRT;
• ED-ADJ::ADJ-1-13-5:CTAG:::PROVFEADDR=SITEC-1-2-8,PADDRFORM=
TID-SH-SL-PRT;
Provision the WSS-WSS adjacency:
• ED-ADJ::ADJ-1-3-4:CTAG:::ADJTYPE=WSS,PROVFEADDR=SITEA-1-11-
3,PADDRFORM=TID-SH-SL-PRT;
• ED-ADJ::ADJ-1-11-4:CTAG:::ADJTYPE=WSS,PROVFEADDR=SITEA-1-3-
The figure below shows the diagram for SITEA adjacency provisioning.
Figure 6-13
SITEA adjacency provisioning
1: 5 1: 5
Adjacency provisioning for SITEB

Provision adjacencies for SITEB as follows (see figure below):
• ED-ADJ-LINE::ADJ-1-13-5:CTAG:::FIBERTYPE=ELEAF;
Provision the LIM-LIM Line Adjacency:
• ED-ADJ::ADJ-1-2-5:CTAG:::PROVFEADDR=SITEC-1-13-8,PADDRFORM=
TID-SH-SL-PRT;
• ED-ADJ::ADJ-1-13-5:CTAG:::PROVFEADDR=SITEA-1-2-8,PADDRFORM=
TID-SH-SL-PRT;

Provision the WSS-WSS Adjacency:

• ED-ADJ::ADJ-1-3-4:CTAG:::ADJTYPE=WSS,PROVFEADDR=SITEB-1-11-
• ED-ADJ::ADJ-1-11-4:CTAG:::ADJTYPE=WSS,PROVFEADDR=SITEB-1-3-
The figure below shows the diagram for SITEB adjacency provisioning.
Figure 6-14
SITEB adjacency provisioning
1: 5 1: 5
Adjacency provisioning for SITEC

Provision adjacencies for SITEC as follows (see figure below):
Provision the LIM-LIM Line Adjacency:
• ED-ADJ::ADJ-1-2-5:CTAG:::PROVFEADDR=SITEA-1-13-8,PADDRFORM=
TID-SH-SL-PRT;
• ED-ADJ::ADJ-1-13-5:CTAG:::PROVFEADDR=SITEB-1-2-8,PADDRFORM=
TID-SH-SL-PRT;
The figure below shows the diagram for SITEC adjacency provisioning.

Figure 6-15
SITEC adjacency provisioning
Adjacency provisioning at a DIA node

Provision the WSS-WSS adjacencies for SITED between a ROADM
backbone and DIA node (See figure below).
• ED-ADJ::ADJ-1-5-4:CTAG1:::ADJTYPE=WSS,PROVFEADDR=SITED-1-3-
• ED-ADJ::ADJ-1-5-6:CTAG2:::ADJTYPE=WSS,PROVFEADDR=SITED-1-11
-11,PADDRFORM=TID-SH-SL-PRT;

WSC WSC SITED
WSC WSC 4 3
Figure 6-16
SiteD 4 3 Shelf 1
Release 12.6
Shelf 1 Backbone OTS 2
2x OSC
Backbone OTS 1
2x OSC
Slot-14
OSC OSC
Slot-1
OSC OSC 2 1
2 1
PEC: NTK554BA
OSC2 In
OSC1 In
OSC2 Out
OSC1 Out
PEC: NTK554BA
OSC2 In
OSC1 In
OSC2 Out
OSC1 Out
1
1
2
2
2
2
1
1
WSS 100GHz 6500 6500 WSS 100GHz
PEC: NTK553EA PEC: NTK553EA

Slot-3 Slot-11
Monitor 1 Monitor 1
1 1
OPM OPM
2 2
Monitor 2 Monitor 2
MLA 6500
3 Switch1 In 6500 MLA
PEC: NTK552BA Switch1 In 3
Mon 1 (B Out) 4 PEC: NTK552BA
DIA node adjacency provisioning
Slot-2 1 4 Switch1 Out

Switch1 Out Mon 1 (B Out) Slot-13
2 1
Common In 5 Switch2 In Common In
Mon 2 (A Out) Switch2 In 5 17
17 2
OSC B In 6 6 Mon 2 (A Out)
3 Switch2 Out Switch2 Out
OSC B In
4 Switch3 In 3
OSC A Out Switch3 In 7 7
4
Line A In Line A Out 8 8 OSC A Out
8 A 7 Switch3 Out Switch3 Out
9:1 9:1 Line B In Line B Out
Switch4 In 6 B 5
Switch4 In 9 9

5 6 10 10
B Switch4 Out Switch4 Out
1: 5 7 A 8
1: 5 Switch5 In 11 11 Switch5 In  Line A Out Line A In
 12
12 Switch5 Out
Switch5 Out

18 18
13 13
14 14
15 15
WSS 100
WSS 100
16
1X5 w/upgd
16
1X5 w/upgd
eCMD44 In 1 Ch LC
1
PEC:NTT862FA
Slot-83 2
Out 1 Ch
In 2 Ch LC
3
SiteD WSS 100GHz 6500 4
Out 2 Ch
Shelf 1 PEC: NTK553EA LC Common Out
90
Slot-5
DIA OTS 3 Monitor 1 89
MLA 6500 1
OPM Common In
PEC: NTK552BA 2 In 43 Ch LC
Mon 1 (B Out) Monitor 2
LC Slot-7 1 85
Ch 1 In eCMD44
1 2 Switch1 In 3 86
XUMED / XUM lennahC 44
PEC:NTT862FA Mon 2 (A Out) Out 43 Ch

2 Slot-84 4
Ch 1 Out OSC B In Switch1 Out In 44 Ch LC
3
LC 87
Ch 2 In 4 Common In Switch2 In 5
3 OSC A Out 17
88
6 Out 44 Ch
4 Line A In Line A Out Switch2 Out
Ch 2 Out 8 A 7
Common Out LC Pad Switch3 In 7
90
8
89 5 B 6 Switch3 Out
Line B Out Line B In 9:1
Common In Switch4 In 9
LC Ch 43 In 10
85 Switch4 Out
86 1: 5

 Switch5 In 11
Ch 43 Out
12
LC Ch 44 In Switch5 Out
87
88
Ch 44 Out Common Out
18
13
Switch6 In
14
Switch7 In
15
Switch8 In
WSS 100
16
1X5 w/upgd
Switch9 In
October 2019
Adjacency provisioning at a COADM node

In the Colorless OADM node, there are three sets of inter-OTS adjacencies to
provision:
• WSS-WSS adjacencies between backbone ROADM OTSs:
— ED-ADJ::ADJ-1-3-4:CTAG:::ADJTYPE=WSS,PROVFEADDR=OME50
13-1-7-3,PADDRFORM=TID-SH-SL-PRT;
— ED-ADJ::ADJ-1-7-4:CTAG:::ADJTYPE=WSS,PROVFEADDR=OME50
• Adjacencies between the ROADM backbone OTSs and DIA OTS:
— ED-ADJ::ADJ-2-1-4:CTAG1:::ADJTYPE=WSS,PROVFEADDR=OME5
— ED-ADJ::ADJ-2-1-6:CTAG2:::ADJTYPE=WSS,PROVFEADDR=OME5
• Adjacencies between the DIA OTS and COADM OTS (See figure below).
— LIM-SMD adjacency between DIA OTS LIM port 5 and COADM OTS
SMD port 9 in colorless OADM configurations:
– ED-ADJ::ADJ-2-4-5:CTAG3:::ADJTYPE=SMD,PROVFEADDR=OM
E5013-2-5-9,PADDRFORM=TID-SH-SL-PRT;
— SMD-LIM adjacency between COADM OTS SMD port 10 and DIA
OTS LIM port 8 in colorless OADM configurations
– ED-ADJ::ADJ-2-5-10:CTAG4:::ADJTYPE=AMP,PROVFEADDR=OM
E5013-2-4-8,PADDRFORM=TID-SH-SL-PRT;

Figure 6-17
COADM node adjacency provisioning

Wavelength provisioning and deprovisioning examples

Refer to the “Adding optical channels” procedure in Technical Publication
323-1851-221, Commissioning and Testing for detailed procedures on how to
add channels. To add wavelengths using L0 Control Plane, refer to the
NTRN71AA Control Plane Application Guide - Layer 0 (Photonic) and
Technical Publication 323-1851-330, Configuration - Control Plane.
Wavelength provisioning example not using L0 Control Plane (linear
system, single domain)
The following example shows how to provision a bidirectional 1530.33 nm
channel between SITEA and SITEE as shown in figure below.
Figure 6-18
Provisioning a bidirectional 1530.33 nm channel between SITEA and SITEE
Linear Optical System
Direction 1 Photonic Domain

ROADM Site Site ID: 1 Site ID: 2 Line Amp Site ROADM Site ROADM Site ROADM Site
Site ID: 4 Site ID: 5
TID: SITEA TID: SITEB Site ID: 3 TID: SITEE
TID: SITEC TID: SITED
Shelf: 1 Shelf: 1 Shelf: 1 Shelf: 1
Shelf IP: 10.6.17.1 Shelf IP: 10.6.17.2 Shelf: 1 Shelf IP: 10.6.17.5
Shelf IP: 10.6.17.3 Shelf IP: 10.6.17.4
OTS: 2 OTS: 1 OTS: 2

OTS: 1 OTS: 2 OTS: 1 OSID: SYS1
OTS: 1 OTS: 2 OSID: SYS1 OSID: SYS1
2XOSC OSID: SYS1 2XOSC 2XOSC OSID: SYS1 2XOSC 2XOSC OSID: SYS1 2XOSC 2XOSC Tx Path ID: 4
2XOSC
S1-P1 Tx Path ID: 1 S1-P1 OSID: SYS1 S14-P1 OSID: SYS1 Tx Path ID: 4 S14-P1 S1-P1 Tx Path ID: 1 Tx Path ID: 4 S14-P1 S1-P1 Tx Path ID: 1 S14-P1
Tx Path ID: 2 Tx Path ID: 1
MLA MLA MLA MLA MLA MLA MLA MLA
LOC slot 2 slot 13 slot 2 slot 13 LOC LOC slot 2 slot 13 LOC LOC slot 2 slot 13 LOC
DSCM/ WSS WSS
Pad WSS WSS Slot 11-
WSS Slot 11- WSS Slot 11-
LOC LOC LOC LOC Slot 3-4 LOC LOC Slot 3-4 LOC LOC 12
Slot 3-4 DSCM/ 12 12
Pad
MOC MOC MOC MOC MOC Direction 4 MOC

Direction 1 DOC
DOC
Optical Optical Optical Optical Optical
Optical Section #1 Section #2 Section #2 Section #3 Section #3
Section #1 SOC SOC SOC SOC SOC
SOC
CMD44 CMD44 CMD44 CMD44 CMD44
CMD44 Slot 86 Slot 84 Slot 86
Slot 84 Slot 86 Slot 84
Optical Section #1 Optical Section #2 Optical Section #3
Here are the steps you need to follow to provision the channel:
1 At SITEA Shelf 1, use the Site Manager Equipment & Facility Provisioning
application and select the CMD44 in slot 84.
2 Select ADJ-TX from the Facility Type drop-down menu.
3 Select the 1530.33 wavelength from the list and then click on the Edit button. This
opens the ADJ-TX Edit Facility dialog box.
4 In the ADJ-TX Edit Facility dialog box, change the Transmitter type from Unknown
to the correct transponder type that is actually connected to the CMD44. Since
this is a bidirectional channel, the Paired Rx parameter is set to Yes.
5 Shelf Wavelength Topology derives a 1way Photonic connection between the
CMD44 in slot 84 and the LIM in slot 2 and since Paired Rx was set to Yes, it also
derives a 1way Photonic connection between the LIM in slot 2 and the CMD44 in
slot 84. These derived Photonic connections can be viewed using the Site
Manager Photonic Connections application.
6 The trail the channel traverses within the OTS can be viewed using the Site
Manager Shelf Wavelength Topology application or the Site Manager
Visualization application and the OTS Schematic View.
7 At SITEE Shelf 1, use the Site Manager Equipment & Facility Provisioning

10 In the ADJ-TX Edit Facility dialog box, change the Transmitter type from Unknown
to the correct transponder type that is actually connected to the CMD44. Since
this is a bidirectional channel, the Paired Rx parameter is set to Yes.
11 Shelf Wavelength Topology derives a 1way Photonic connection between the
CMD44 in slot 86 and the LIM in slot 13 and since Paired Tx was set to Yes, it also
derives a 1way Photonic connection between the LIM in slot 13 and the CMD44
in slot 86.
12 Since an end-to-end channel has been created for wavelength 1530.33 in the
direction from SITEA to SITEE, Network Channel Topology automatically derives
a 1way Photonic connection between the LIM in slot 13 and the LIM in slot 2 at
SITEC and a 1way Photonic connection between the LIM in slot 13 and the LIM
in slot 2 at SITED. Now since all Photonic connections are in place, NCT creates
the end-to-end 1530.33 nm channel in the direction from SITEA to SITEE. This
channel is now displayed in the Site Manager DOC application at SITEA with a
Channel Condition of “Inactive”. The NE trail of the channel can be viewed using
the NE Trail button within the DOC application. The Site Manager Visualization
Photonic Network view application (Tools->Visualization) can be used to view the
NE trail graphically. The channel is now ready to be added in the SITEA to SITEE
direction using DOC. A channel with a Channel Condition of “Inactive” is said to
be not DOC-managed. Once the channel has been added by DOC, the Channel
Condition and End-to-End Condition changes to “Optimized” and the channel is
said to be DOC-managed.
13 Similarly, since an end-to-end channel can be created for wavelength 1530.33 in
the direction from SITEE to SITEA, Network Channel Topology (NCT)
automatically derives a 1way Photonic connection between the LIM in slot 2 and
the LIM in slot 13 at SITED and a 1way Photonic connection between the LIM in
slot 2 and the LIM in slot 13 at SITEC. Now since all Photonic connections are in
place, NCT creates the end-to-end 1530.33 nm channel in the direction from
SITEE to SITEA. This channel is now displayed in the Site Manager DOC
application at SITEE. The NE trail of the channel can be viewed using the NE Trail
button within the DOC application. The Site Manager Visualization Photonic
Network view application (Tools->Visualization) can be used to view the NE trail
graphically. The channel is now ready to be added in the SITEE to SITEA direction
using DOC. A channel with a Channel Condition of “Inactive” is said to be not
DOC-managed. Once the channel has been added by DOC, the Channel
Condition and End-to-End Condition changes to “Optimized” and the channel is
said to be DOC-managed
Wavelength deprovisioning example not using L0 Control Plane (linear
system, single domain)
The following example shows how to deprovision a bidirectional 1530.33 nm
channel between SITEA and SITEE as shown in figure below.

Figure 6-19
Deprovision a bidirectional 1530.33 nm channel between SITEA and SITEE
Linear Optical System

ROADM Site Site ID: 1 Site ID: 2 Line Amp Site ROADM Site ROADM Site ROADM Site
Site ID: 4 Site ID: 5
TID: SITEA TID: SITEB Site ID: 3 TID: SITEE
TID: SITEC TID: SITED
Shelf: 1 Shelf: 1 Shelf: 1 Shelf: 1
Shelf IP: 10.6.17.1 Shelf IP: 10.6.17.2 Shelf: 1 Shelf IP: 10.6.17.5
Shelf IP: 10.6.17.3 Shelf IP: 10.6.17.4
OTS: 2 OTS: 1 OTS: 2

OTS: 1 OTS: 2 OTS: 1 OSID: SYS1
OTS: 1 OTS: 2 OSID: SYS1 OSID: SYS1
2XOSC OSID: SYS1 2XOSC 2XOSC OSID: SYS1 2XOSC 2XOSC OSID: SYS1 2XOSC 2XOSC Tx Path ID: 4
2XOSC
S1-P1 Tx Path ID: 1 S1-P1 OSID: SYS1 S14-P1 OSID: SYS1 Tx Path ID: 4 S14-P1 S1-P1 Tx Path ID: 1 Tx Path ID: 4 S14-P1 S1-P1 Tx Path ID: 1 S14-P1
Tx Path ID: 2 Tx Path ID: 1
MLA MLA MLA MLA MLA MLA MLA MLA
LOC slot 2 slot 13 slot 2 slot 13 LOC LOC slot 2 slot 13 LOC LOC slot 2 slot 13 LOC
DSCM/ WSS WSS
Pad WSS WSS Slot 11-
WSS Slot 11- WSS Slot 11-
LOC LOC LOC LOC Slot 3-4 LOC LOC Slot 3-4 LOC LOC 12
Slot 3-4 DSCM/ 12 12
Pad
MOC MOC MOC MOC MOC Direction 4 MOC

Direction 1 DOC
DOC
Optical Optical Optical Optical Optical
Optical Section #1 Section #2 Section #2 Section #3 Section #3
Section #1 SOC SOC SOC SOC SOC
SOC
CMD44 CMD44 CMD44 CMD44 CMD44
CMD44 Slot 86 Slot 84 Slot 86
Slot 84 Slot 86 Slot 84
Optical Section #1 Optical Section #2 Optical Section #3
Here are the steps you need to follow to deprovision the channel:
1 At SITEA and SITEE, use DOC to delete the channel. Once deleted, the Channel
Condition and End-to-End Condition for the channel displays “Inactive”.
2 At SITEA Shelf 1, use the Site Manager Equipment & Facility Provisioning
5 In the ADJ-TX Edit Facility dialog box, change the Transmitter type to Unknown.
6 Shelf Wavelength Topology deletes the 1way Photonic connection between the
CMD44 in slot 84 and the LIM in slot 2 and since Paired Rx was set to Yes, it also
deletes the 1way Photonic connection between the LIM in slot 2 and the CMD44
in slot 84. Photonic connections can be viewed using the Site Manager Photonic
Connections application.
7 At SITEE Shelf 1, use the Site Manager Equipment & Facility Provisioning
10 In the ADJ-TX Edit Facility dialog box, change the Transmitter type to Unknown.
11 Shelf Wavelength Topology deletes the 1way Photonic connection between the
CMD44 in slot 86 and the LIM in slot 13 and since Paired Tx was set to Yes, it also
deletes the 1way Photonic connection between the LIM in slot 13 and the CMD44
in slot 86.
12 Since an end-to-end channel can no longer be created for wavelength 1530.33 in
the direction from SITEA to SITEE, Network Channel Topology (NCT)
automatically deletes the 1way Photonic connection between the LIM in slot 13
and the LIM in slot 2 at SITEC and the 1way Photonic connection between the
LIM in slot 13 and the LIM in slot 2 at SITED. This channel is now no longer
displayed in the Site Manager DOC application at SITEA.
13 Similarly, since an end-to-end channel can no longer be created for wavelength
1530.33 in the direction from SITEE to SITEA, Network Channel Topology (NCT)
automatically deletes the 1way Photonic connection between the LIM in slot 2 and
the LIM in slot 13 at SITED and the 1way Photonic connection between the LIM
in slot 2 and the LIM in slot 13 at SITEC. This channel is now no longer displayed
in the Site Manager DOC application at SITEE.

Provisioning a wavelength example using SPLI (not using L0 Control

Plane) (multi-domain system)
The following example shows how to provision a bidirectional channel in a
multi-domain system using the Service and Photonic Layer Interoperability
feature (SPLI). The channel is supported by an OTSC circuit pack whose
wavelength is set to 1557.36 nm and crosses a domain boundary at a 4-way
branching node (see figure below). Note that in this example the OTSC is in
the same shelf as the OTS it connects to, but it could be located in a different
shelf provided this shelf shares the same siteID with the shelf of the OTS.
Assumptions
Prior to undertaking the provisioning steps, it is assumed that the following
tasks have been performed:
• The OTSC circuit packs are inserted in their assigned slots in the 6500
shelves.
• The OTSC circuit pack client XFP is inserted in the circuit pack.
• The OTSC circuit pack line and client facilities have been created.
• The CMD44 has its Auto Discovered field set to “Auto” and the Sync
Provisioned field set to “True” for its 1557.36 Tx adjacency.
• The CMD44 and the OTSC are physically connected.

Figure 6-20
Channel provisioning using SPLI in a multi-domain system
OSID: LINEAR1 OSID: LINEAR2
Slot 84
O
Slot 9 T
S
OME13 C
OME12 OSID: LINEAR1

D
Slot 10
Slot 13
OSID: RING2 OSID: RING2 OSID: RING2 OSID: LINEAR2
Slot 84
O
T D
S Slot 9 OSID: RING2
OME11 C
1 At the 4-way branching node (OME12), using the Site Manager Photonic
Connections application, a bidirectional Photonic connection for 1557.36 nm is
added from the LIM in slot 10 (belonging to OSID “RING2”) to the LIM in slot 13
(belonging to OSID “LINEAR2”)
2 At OME11, use the Site Manager Equipment & Facility Provisioning application
and select the CMD44 in slot 84.
3 Select ADJ-TX from the CMD44 Facility Type drop-down menu.
5 Click on the Edit button and then edit the “Expected far end address format” to
“TID-SH-SL-PRT” and the “Expected far end address” to match the OTMn facility
AID, that is “OME11-1-9-1”.

6 As a result, the CMD44 ADJ-TX facility for 1557.36 nm is now IS, with the OTSC
as the transmitter type.
Attention: SPLI automatically sets the OTSC circuit pack Tx wavelength to

1557.36 nm and also sets the Tx power.
7 Select the ADJ-RX from the CMD44 Facility Type drop-down menu.
opens the ADJ-RX Edit Facility dialog box.
9 Click on the “Use actual far end address and format” checkbox.
10 At OME13, use the Site Manager Equipment & Facility Provisioning application
and select the CMD44 in slot 84.
11 Select ADJ-TX from the CMD44 Facility Type drop-down menu.
13 Click on the Edit button and then edit the “Expected far end address format” to
“TID-SH-SL-PRT” and the “Expected far end address” to match the OTMn facility
AID, that is “OME11-1-9-1”.
14 As a result, the CMD44 ADJ-TX facility for 1557.36 nm is now IS, with the OTSC
as the transmitter type.
Attention: SPLI automatically sets the OTSC circuit pack Tx wavelength to

1557.36 nm and also sets the Tx power.
15 Select the ADJ-RX from the CMD44 Facility Type drop-down menu.
opens the ADJ-RX Edit Facility dialog box.
17 Click on the “Use actual far end address and format” checkbox.
18 The channel is now added using the Site Manager DOC application at OME11
and OME13.

Provisioning/deprovisioning wavelengths when a specific wavelength is

used multiple times
This section only applies for multi-section domains that use Longest path
routing. Routing is identified in the CMD ADJ-TX facility. For greenfield
systems, the routing defaults to Shortest path routing. If your system was
upgraded from releases prior to Rel. 9.0, it could be that the routing is Longest
path routing as that was the default in releases prior to Rel. 9.0.
The following basic rules apply:
• A channel managed by DOC cannot expand or contract. An alarm is
raised when an expansion or contraction is reported by the Topology
application.
• A channel within a domain starts at a Tx adjacency and ends at a Rx
adjacency.
• The Topology application expands existing channels if a new end point is
found before a new start point.
The figure below shows an example.
Figure 6-21
Provisioning/deprovisioning channels when a specific wavelength is used multiple times (ring
system, single domain example)
In this example, the existing channel is 1530.33 nm between points A and B.

The channel is already provisioned and DOC managed. Now you want to
provision another 1530.33 nm channel in a different section of the ring system
between points C and D.
You must follow a specific order when provisioning the new 1530.33 nm
channel. Provision the channel with unpaired TX and RX adjacencies, along
with 1-way Photonic connections at intermediate ROADM passthrough nodes,
from Tx to Rx.

For example, a channel traversing two domains would need to be provisioned

in the following order:
1 TX ADJ in domain 1
2 1-way Photonic connection from domain 1 to domain 2
3 RX ADJ in domain 2
4 Afterwards, do the same but in the opposite direction as follows:
5 TX ADJ in domain 2
6 1-way Photonic connection from domain 2 to domain 1
7 RX ADJ in domain 1
To deprovision the channel from topology, remove the ADJs and Photonic
connections in reverse order, starting from the RX ADJ and working your way
back towards to TX ADJ.
Wavelength provisioning example using L0 Provisioning Control Plane

type and implicit routing
channel using L0 Provisioning Control Plane type and implicit routing between
Site C1 and Site C3 in the example network shown in the figure below.
Figure 6-22
Wavelength provisioning example using L0 Provisioning Control Plane type

• At the Site C1 and Site C3 node, install and provision the transponder
circuit pack. In this example, a WL3n transponder is installed in shelf 21
slot 5. The transponder DWDM provisioning parameters, such as Tx
power and Tx wavelength, will be auto-set in a subsequent step.
• At the Site C1 and Site C3 node, connect the transponder DWDM
transmitter and receiver to a CMD Channel In/Out port. In this example,
connect WL3n transponder shelf 21 slot 5 Tx port to CMD shelf 1 slot 2
port 1 and connect WL3n transponder shelf 21 slot 5 Rx port to CMD shelf
1 slot 2 port 2.
• At the Site C1 and Site C3 node, use the Site Manager Equipment &
Facility Provisioning application to select the CMD ADJ-TX facility the
transponder is connected to (ADJ-1-2-1 in our example) and set the
Expected far end address format to TID-SH-SL-PRT and the Expected Far
End Address to point to the transponder line-side facility (C1-21-5-1 in our
example) connected to the CMD port. As a result of this step, a SPLI
match occurs and SPLI auto-sets the DWDM parameters, such as Tx
power and Tx wavelength, on the transponder DWDM line-side facility.
• At the Site C1 and Site C3 node, verify that the CMD ADJ-RX facility
(ADJ-1-2-2 in our example) Actual Far End Address displays the
transponder line-side facility (C1-21-5-1 in our example) connected to the
CMD. Click on the “Use actual Rx address and format” and then click on
the OK button. Verify that the CMD ADJ-RX Actual Far End Address and
• At the Site C1 or Site C3 node, add the SNC (i.e., optical channel) using
the Site Manager Configuration->Sub-Network Connection application.
— Parameters to enter when adding the SNC0 object include: ID, Label,
Local End Point Node (C1 in our example), Local End Point End point
(ADJ-1-2-1 in our example), Remote End Point Node (C3 in our
example), Remote End Point End point (ADJ-1-2-1 in our example),
Primary State, Wavelength (1530.33 nm in our example), Routing List
(None for implicit routing in our example), Max. Admin Weight (to
constrain implicit route selection - default 0 (no constraint)).
— Once the SNC is added, L0 Control Plane (OSRP) finds the shortest
path for the SNC. The shortest path is defined as follows: If OSRP Link
administrative weights are set to default, then the shortest route is the
minimum # of hops (between source and destination OSRP nodes).
Otherwise, the shortest route is the route with the smallest sum of
OSRP Link administrative weights. In our example, OSRP chooses the
direct path between Site C1 and Site C3.

— L0 Control Plane (OSRP) creates the necessary Photonic connections

at the Site C1 and Site C3 Photonic ROADM nodes. L0 Control Plane
then interfaces with DOC to add the optical channel through the
Photonic ROADM system.
Wavelength provisioning example using L0 Provisioning Control Plane

type and explicit routing
channel using L0 Provisioning Control Plane type and explicit routing between
Site C1 and Site C3, passing through Site E3 and Site C2, in the example
network shown in Figure 6-22 on page 6-49.
• At the Site C1 and Site C3 node, install and provision the transponder
circuit pack. In this example, a WL3n transponder is installed in shelf 21
slot 5. The transponder DWDM provisioning parameters, such as Tx
power and Tx wavelength, will be auto-set in a subsequent step.
• At the Site C1 and Site C3 node, connect the transponder DWDM
transmitter and receiver to a CMD Channel In/Out port. In this example,
connect WL3n transponder shelf 21 slot 5 Tx port to CMD shelf 1 slot 2
port 1 and connect WL3n transponder shelf 21 slot 5 Rx port to CMD shelf
1 slot 2 port 2.
• At the Site C1 and Site C3 node, use the Site Manager Equipment &
Facility Provisioning application to select the CMD ADJ-TX facility the
transponder is connected to (ADJ-1-2-1 in our example) and set the
Expected far end address format to TID-SH-SL-PRT and the Expected Far
End Address to point to the transponder line-side facility (C1-21-5-1 in our
example) connected to the CMD port. As a result of this step, a SPLI
match occurs and SPLI auto-sets the DWDM parameters, such as Tx
power and Tx wavelength, on the transponder DWDM line-side facility.
• At the Site C1 and Site C3 node, verify that the CMD ADJ-RX facility
(ADJ-1-2-2 in our example) Actual Far End Address displays the
transponder line-side facility (C1-21-5-1 in our example) connected to the
CMD. Click on the “Use actual Rx address and format” and then click on
the OK button. Verify that the CMD ADJ-RX Actual Far End Address and
• At the Site C1 or Site C3 node, use the Site Manager
Configuration->Routing Profiles application and the Routes tab (DTL0) to
provision the Designated Transit List (DTL0) defining the C1 to E3 to C2
to C3 route. Note that the Site Manager Routing application automatically
creates a DTLSET0 (in the Routing Lists tab) for the Route (DTL0)
created, using the same label.
• At the Site C1 or Site C3 node, add the SNC (i.e., optical channel) using
the Site Manager Configuration->Sub-Network Connection application.

— Parameters to enter when adding the SNC0 object include: ID, Label,
Local End Point Node (C1 in our example), Local End Point End point
(ADJ-1-2-1 in our example), Remote End Point Node (C3 in our
example), Remote End Point End point (ADJ-1-2-1 in our example),
Primary State, Wavelength (1530.33 nm in our example), Routing List
(select the routing list that was created in an earlier step), Max. Admin
Weight (to constrain implicit route selection - default 0 (no constraint)).
— Once the SNC is added, L0 Control Plane (OSRP) creates the
necessary Photonic connections at the Site C1 and Site C3 Photonic
ROADM nodes as well as any intermediate Photonic ROADM nodes
(E3 and C2 in our example). L0 Control Plane then interfaces with
DOC to add the optical channel through the Photonic ROADM system.
Wavelength deprovisioning example using L0 Provisioning Control Plane

type
The following example shows how to deprovision a bidirectional 1530.33 nm
channel using L0 Provisioning Control Plane type between Site C1 and Site
C3 in the example network shown in Figure 6-22 on page 6-49.
Here are the steps you need to follow to deprovision the channel:
• At the node where the SNC was created, edit the SNC Primary state from
IS to OOS state using the Site Manager Configuration->Sub-Network
Connection application.
— Once the SNC is put in the OOS state, L0 Control Plane interfaces with
DOC in order to delete the optical channel from the Photonic ROADM
system. L0 Control Plane then deletes all associated Photonic
connections at the local and remote Photonic ROADM nodes as well
as any intermediate Photonic ROADM nodes.
• At the node where the SNC was created, delete the SNC using the Site
Manager Configuration->Sub-Network Connection application.

Copyright© 2010-2019 Ciena® Corporation. All rights reserved.
Release 12.6
Publication: NTRN15DA
Document status: Standard
Issue 1
Document release date: October 2019
CONTACT CIENA
For additional information, office locations, and phone numbers, please visit the Ciena
web site at www.ciena.com

NTRN15DA.1 (6500 R12.6 PhotonicLayerGuide) Issue1

Uploaded by

Copyright:

Available Formats

You might also like

NTRN15DA.1 (6500 R12.6 PhotonicLayerGuide) Issue1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NTRN15DA.1 (6500 R12.6 PhotonicLayerGuide) Issue1

Uploaded by

Copyright:

Available Formats

6500 Packet-Optical Platform

Photonic Layer Guide, Part 1 of 3

See Part 2 for the following...

See Part 3 for the following...

NTRN15DA - Standard Issue 1

6500 Packet-Optical Platform Photonic Layer Guide, Part 1 of 3

6500 Packet-Optical Platform Photonic Layer Guide, Part 1 of 3

6500 Packet-Optical Platform Photonic Layer Guide, Part 1 of 3

About this document ix

Topology Fundamentals 1-1

Photonic Optical Control 2-1

6500 Packet-Optical Platform Photonic Layer Guide, Part 1 of 3

Site Manager DOC application 2-21

6500 Packet-Optical Platform Photonic Layer Guide, Part 1 of 3

Bias Provisioning 2-118

Photonic Applications 3-1

6500 Packet-Optical Platform Photonic Layer Guide, Part 1 of 3

FIM Type 4, FIM Type 5 and FIM Type 6 3-74

6500 Packet-Optical Platform Photonic Layer Guide, Part 1 of 3

Operational considerations for OTDR feature 3-148

Photonic Engineering Rules 4-1

6500 Packet-Optical Platform Photonic Layer Guide, Part 1 of 3

Photonic Set-Up Guidelines 5-1

Provisioning Examples 6-1

6500 Packet-Optical Platform Photonic Layer Guide, Part 1 of 3

Inter-OTS and intra-OTS adjacency provisioning examples 6-35

6500 Packet-Optical Platform Photonic Layer Guide, Part 1 of 3

6500 Packet-Optical Platform Photonic Layer Guide, Part 1 of 3

About this document 0

DOC-controlled versus non-DOC-controlled Photonic line systems

6500 Packet-Optical Platform Photonic Layer Guide, Part 1 of 3

– Manual equalization using pads at various locations in the system

The Photonic Layer Guide covers:

New in this release

Key changes in this version of the document pertain to the following:

6500 Packet-Optical Platform Photonic Layer Guide, Part 1 of 3

New 6500 S-Series/D-Series Photonic Hardware

New Photonic Layer applications and software features

Concepts covered in this document

Refer to Technical Publication 323-1851-090, Documentation Roadmap,

6500 Packet-Optical Platform Photonic Layer Guide, Part 1 of 3

6500 Packet-Optical Platform technical publications

Documentation Installation - Administration Fault Management - Common Equipment

SAOS-based Command Fault and MIB

6500 Packet-Optical Platform Photonic Layer Guide, Part 1 of 3

6500 T-Series roadmap:

Planning a Network Installing, Managing and Maintaining and

T-Series Administration Fault Management -

SAOS-based Command Fault and MIB

6500 Packet-Optical Platform Photonic Layer Guide, Part 1 of 3

Document Date Engineer Writer Reason for Change

Issue 1 10/17/2019 JPL JPL First official document release.

6500 Packet-Optical Platform Photonic Layer Guide, Part 1 of 3

This chapter provides a brief overview of the 6500 Packet-Optical Platform

The following table lists the topics in this chapter.

6500 Packet-Optical Platform Photonic Layer Guide, Part 1 of 3

6500 Packet-Optical Platform Photonic Layer Guide, Part 1 of 3

Higher-layer control and OAM&P applications in photonic layer systems are